Re: [Idr] [Bier] I-D Action: draft-ietf-bier-bgp-ls-bier-ext-00.txt
Greg Mirsky <gregimirsky@gmail.com> Tue, 11 April 2017 20:29 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2B6C129513; Tue, 11 Apr 2017 13:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GcnK7hy1lGyr; Tue, 11 Apr 2017 13:29:28 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 421EE127601; Tue, 11 Apr 2017 13:29:25 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id b187so10458346oif.0; Tue, 11 Apr 2017 13:29:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ek5sa5RZUO849yVKGF3xDNpPLyNBo+qyQLh8Gn3hmp8=; b=iGns2kmGr5FE/hYDdhRYVpSaeLuiuUDTV1pomt4Qv0UoVL4WUeI7vo96bPuVTB6n2u pcuB1VLIad0C6xaNLJRCKrsxJI72vyicfgLU9x/pErVJq1HdZ+62HRD955CGHdfEfiz7 5oegwU/LlCdE4ko43Uy3RzQBll1m8tn39IdnT56h/viAzYQ/JoJt60wb07ud+NjucREP cP6qnmQ/NEctxaIpRGOKS/vxxh6EMy0520yfBm64/OYdWIs48mYIhpIjCV2rvEHIlstd 9j/1QGHujHOsc/J08ek8APzd84vXyUaJZnSZHQVRUH+p4dBYnM5sRKri0+wV8gCJVShX lLDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ek5sa5RZUO849yVKGF3xDNpPLyNBo+qyQLh8Gn3hmp8=; b=m6qTL3xddcnz/HMvcEgBGbONSOkmj/aiKh3tXMPo1GTRKv3CqXQ/BhGdPh9L1R9MOq zZCfBdalYirBxXJgpdICDlzf17H2Ghp4CMn52SghXrMsW8JvctbBr/4HpdYOPs6NcCh4 Xce4Ll5AargU/vJpMekkGCXZ8+yYyRWj0h5xNYMa0lXUNavOs/zlge2gn9fDA2SXftxZ 8q77IU8owBqe/56MW9O+673lzNs26UHhavZ32o2Sr+DQ2hQPu6pqxj/LI2ZO92XhXT4s pD7PdfbwCXk5cX8RWd7g8uZZ2FSRvWXikuP4M4cKqMFr9xmik0eR5vXNgBdCa88iaPj5 bZMg==
X-Gm-Message-State: AN3rC/6Uc5agC7rTYsb/vaL5ZLnxbN5V14JnAYh+JmtBpjoQkphLbd9VUkc+K5oWRKizTwEFb9ghRqbwPQ5cDw==
X-Received: by 10.157.42.82 with SMTP id t76mr8762747ota.40.1491942564517; Tue, 11 Apr 2017 13:29:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.39.165 with HTTP; Tue, 11 Apr 2017 13:29:24 -0700 (PDT)
In-Reply-To: <201704071044279565138@zte.com.cn>
References: <201704071044279565138@zte.com.cn>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 11 Apr 2017 13:29:24 -0700
Message-ID: <CA+RyBmUPbBbcgp_OfKNjnKqfeE7EaPw6WDy54wmiAxzHdFya+w@mail.gmail.com>
To: chen.ran@zte.com.cn, draft-ietf-bier-bgp-ls-bier-ext@ietf.org
Cc: bier@ietf.org, idr@ietf.org
Content-Type: multipart/alternative; boundary="001a113d09de955d1f054ce9f23e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/wm-ScycoNsF6ojDYzOrXR6xLZek>
Subject: Re: [Idr] [Bier] I-D Action: draft-ietf-bier-bgp-ls-bier-ext-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 20:29:31 -0000
Hi Ran, Authors, thank you for the very good and timely work. Please kindly consider my notes to the draft: - section 3.1 - for consistency of format definition add Type with reference to the appropriate sub-section in IANA Considerations; - add definition of the value in Length field, e.g. "equals number of octets of the Value field"; - you may describe the Reserved field and note that is MUST be set to 0 on transmit and ignored on receipt; - I think that meaning and use of subdomain-id and MT-ID need more discussion. E.g., how these id's assigned, managed? What they signify? - how the value of BSL field defined? Is it the same as Len field in the BIER Header (Section 3 in draft-ietf-bier-mpls-encapsulation)? You may add the reference to encaps draft. - I think that Set Identifier (SI) should be included in the BIER TLV. According to Section 3 of the BIER Architecture document, SI value may be in the [0, 255] range. Then one octet seems sufficient for SI field. - I'd suggest to keep format to four octet alignment and add reserved field after the BFR-id field. - Section 3.1.1 - you can add reference to the sub-section in IANA Considerations for Type field; - add definition of the value of Length field; - is 255 range sufficient for Label Range advertisement?Is it because SI is limited to 255? Would be helpful to clarify; - would BS Length in the sub-TLV be the same as BSL field in the BIER TLV? Regards, Greg On Thu, Apr 6, 2017 at 7:44 PM, <chen.ran@zte.com.cn> wrote: > Hello all, > > We would like to request comments on the draft > > https://datatracker.ietf.org/doc/html/draft-ietf-bier-bgp-ls-bier-ext > > > We would really appreciate any comments and questions about the draft. > > > Best Regards. > > Ran > > > 原始邮件 > *发件人:* <internet-drafts@ietf.org>; > *收件人:* <i-d-announce@ietf.org>; > *抄送人:* <bier@ietf.org>; > *日 期 :*2017年01月19日 00:26 > *主 题 :**[Bier] I-D Action: draft-ietf-bier-bgp-ls-bier-ext-00.txt* > > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Bit Indexed Explicit > Replication of the IETF. > > Title : BGP Link-State extensions for BIER > Authors : Ran Chen > Zheng Zhang > Vengada Prasad Govindan > IJsbrand Wijnands > Filename : draft-ietf-bier-bgp-ls-bier-ext-00.txt > Pages : 8 > Date : 2017-01-10 > > Abstract: > Bit Index Explicit Replication (BIER) is an architecture that > provides optimal multicast forwarding through a "BIER domain" without > requiring intermediate routers to maintain any multicast related per- > flow state. BIER also does not require any explicit tree-building > protocol for its operation. A multicast data packet enters a BIER > domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the > BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). > The BFIR router adds a BIER header to the packet. The BIER header > contains a bitstring in which each bit represents exactly one BFER to > forward the packet to. The set of BFERs to which the multicast > packet needs to be forwarded is expressed by setting the bits that > correspond to those routers in the BIER header. > > This document specifies extensions to the BGP Link-state address- > family in order to advertising BIER information. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-bier-bgp-ls-bier-ext/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-bier-bgp-ls-bier-ext-00 > > > Please note that it may take a couple of minutes from the > time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > BIER mailing list > BIER@ietf.org > https://www.ietf.org/mailman/listinfo/bier > > > > > _______________________________________________ > BIER mailing list > BIER@ietf.org > https://www.ietf.org/mailman/listinfo/bier > >