IETF Logo Mail Archive

Re: [babel] Summary of my comments about Sandy's talk

zhang.zheng@zte.com.cn Fri, 18 November 2016 14:25 UTC

Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45ADF129576 for <babel@ietfa.amsl.com>; Fri, 18 Nov 2016 06:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.357
X-Spam-Level:
X-Spam-Status: No, score=-104.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_24_48=1.34, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kHDT7UsUFc8 for <babel@ietfa.amsl.com>; Fri, 18 Nov 2016 06:25:43 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 356B312941C for <babel@ietf.org>; Fri, 18 Nov 2016 06:25:39 -0800 (PST)
Received: from out1.zte.com.cn (unknown [192.168.168.120]) by Websense Email Security Gateway with ESMTP id 3CAD65F700258 for <babel@ietf.org>; Fri, 18 Nov 2016 22:25:33 +0800 (CST)
X-MAILFROM: <zhang.zheng@zte.com.cn>
X-RCPTTO: <prz@juniper.net>
X-FROMIP: 10.30.3.20
X-SEG-Scaned: 1
X-Received: unknown,10.30.3.20,20161118213607
Received: from unknown (HELO mse01.zte.com.cn) (10.30.3.20) by localhost with SMTP; 18 Nov 2016 13:36:07 -0000
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id uAIDaZOe008861; Fri, 18 Nov 2016 21:36:35 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
In-Reply-To: <87r369jrh4.wl-jch@irif.fr>
References: <87r369jrh4.wl-jch@irif.fr>
To: Juliusz Chroboczek <jch@irif.fr>
MIME-Version: 1.0
X-KeepSent: 2471F4B6:4D9C0D43-4825806F:0045BA6B; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
Message-ID: <OF2471F4B6.4D9C0D43-ON4825806F.0045BA6B-4825806C.00376616@zte.com.cn>
From: zhang.zheng@zte.com.cn
Date: Thu, 17 Nov 2016 12:30:56 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2016-11-18 21:36:35, Serialize complete at 2016-11-18 21:36:35
Content-Type: multipart/alternative; boundary="=_alternative 003766144825806C_="
X-MAIL: mse01.zte.com.cn uAIDaZOe008861
X-HQIP: 127.0.0.1
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/oGd1HJY81AeoKvBgtgd8pADUCbk>
Cc: prz@juniper.net, babel@ietf.org
Subject: Re: [babel] Summary of my comments about Sandy's talk
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2016 14:25:46 -0000

Hi Juliusz,

    Thank you very much for your comments, and appreciate for 
your confirmation about the draft.
    About the function of TLV advertisement that may influence 
the Babel advertising format, it is great that you have a 
solution to carry the feature bits. Maybe we can work together 
about the detail. 
    For the semantics of format, I will detail it in the next 
version. Once the way of advertisement changes, the corresponding
format may also be updated.
    For the BIER forwarding, the next-hop is one of the most 
important factor. So the prefix that associate with BIER info 
is used to calculate the corresponding next-hop.
    For the prototype, in fact we are doing the BIER prototype, 
but the work about Babel extension for BIER has not yet been 
started. I think we may have more discussion about it. 
    Thanks a lot. :)

Best Regards,
Sandy


Juliusz Chroboczek <jch@irif.fr> 写于 2016-11-18 下午 01:18:31:

> Juliusz Chroboczek <jch@irif.fr> 
> 2016-11-18 下午 01:18
> 
> 收件人
> 
> babel@ietf.org, 
> 
> 抄送
> 
> zhang.zheng@zte.com.cn, prz@juniper.net
> 
> 主题
> 
> Summary of my comments about Sandy's talk
> 
> I'd be thrilled to work on BIER in Babel.  Babel claims that it is
> a flexible protocol, and getting BIER to work in Babel would be an
> opportunity to prove this claim.
> 
> I do however have some concerns about 
draft-zhang-bier-babel-extensions-00.
> First, the encoding does not fit Babel's extension mechanism for two 
reasons:
> it speaks about a transitive, optional sub-TLV, and Babel does not have
> these bits.  Depending on the intended semantics, this extension should 
be
> encoded either as a sub-TLV of the Update TLV, as a sub-TLV of the
> Router-Id TLV, as a new TLV, or as an Update TLV with a new AE.  I 
believe
> I have an opinion, but I'm not sure.
> 
> Second, this version of the draft only speaks about the packet format --
> it doesn't describe the semantics of the data, it doesn't say what an
> implementation actually does with the extra data.  I'm going to do some
> reading about BIER (Pierre, fancy a beer at some point?), but I'd
> appreciate some references.
> 
> (Side note: what requirements does BIER make on the topology?  Are
> non-transitive (meshy) links fine?)
> 
> Finally, I think this work only makes sense if people are serious about
> building a prototype.  I'll be glad to help.
> 
> -- Juliusz

v2.23.0 | Report a Bug | By Email