[Bier] Clarification regarding label-range-size in draft-ietf-bier-ospf-bier-extensions-10
Senthil Dhanaraj <senthil.dhanaraj@huawei.com> Mon, 29 January 2018 09:22 UTC
Return-Path: <senthil.dhanaraj@huawei.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A08B12D969 for <bier@ietfa.amsl.com>; Mon, 29 Jan 2018 01:22:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 1sZrLGF1_YRo for <bier@ietfa.amsl.com>; Mon, 29 Jan 2018 01:22:45 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02FA412D951 for <bier@ietf.org>; Mon, 29 Jan 2018 01:22:44 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 50A49576E9569 for <bier@ietf.org>; Mon, 29 Jan 2018 09:22:40 +0000 (GMT)
Received: from BLREML703-CAH.china.huawei.com (10.20.4.172) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 29 Jan 2018 09:22:41 +0000
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.219]) by blreml703-cah.china.huawei.com ([::1]) with mapi id 14.03.0361.001; Mon, 29 Jan 2018 14:52:37 +0530
From: Senthil Dhanaraj <senthil.dhanaraj@huawei.com>
To: "bier@ietf.org" <bier@ietf.org>
Thread-Topic: Clarification regarding label-range-size in draft-ietf-bier-ospf-bier-extensions-10
Thread-Index: AdOY4l3btImwIKEWSQ2TZsFgObiBCAAAAp6Q
Date: Mon, 29 Jan 2018 09:22:37 +0000
Message-ID: <9778B23E32FB2745BEA3BE037F185DC4A5BA0BA2@BLREML503-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.148.65]
Content-Type: multipart/alternative; boundary="_000_9778B23E32FB2745BEA3BE037F185DC4A5BA0BA2BLREML503MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/ebbNFeYGnbDbtvKGxhKJZSQUfhk>
Subject: [Bier] Clarification regarding label-range-size in draft-ietf-bier-ospf-bier-extensions-10
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jan 2018 09:22:48 -0000
Dear Authors of draft-ietf-bier-ospf-bier-extensions-10, A clarification required regarding the ¡°label-range-size¡± field in BIER MPLS Sub TLV. Kindly check. RFC 8279 (Section 3) A BFR MUST support SI values in the range [0,15] and MAY support SI values in the range [0,255]. ("Supporting the values in a given range" means, in this context, that any value in the given range is legal and will be properly interpreted.) Note that for a given BitStringLength, the total number of BFR-ids that can be represented is the product of the BitStringLength and the number of supported SIs. For example, if a deployment uses (in a given sub-domain) a BitStringLength of 64 and supports 256 SIs, that deployment can only support 16384 BFR-ids in that sub-domain. Even a deployment that supports 256 SIs will not be able to support 65,535 BFR-ids unless it // [SEN1] uses a BitStringLength of at least 256. [SEN1] In general, the assumption is that, Max BFR-Ids supported = [bsl * NumOfSI] (ofcourse in the range [1 ¨C 65535]) draft-ietf-bier-ospf-bier-extensions-10 (Section 2.2) The BIER MPLS Encapsulation Sub-TLV has the following format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Lbl Range Size | Label Range Base | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |BS Len | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The "label range" is the set of labels beginning with the label range base and ending with ((label range base)+(label range size)- // [SEN2] 1). A unique label range is allocated for each BitStream length and Sub-domain-ID. These labels are used for BIER forwarding as described in [I-D.ietf-bier-architecture] and [I-D.ietf-bier-mpls-encapsulation]. The size of the label range is determined by the number of Set Identifiers (SI) (section 1 of [I-D.ietf-bier-architecture]) that are used in the network. Each SI maps to a single label in the label range. The first label is for SI=0, the second label is for SI=1, etc. [SEN2] Max ¡°label range size¡± = 255 ¡°label-end¡± = ¡°label range base¡± + 255 ¨C 1 Which means, we can support only 255 SIs, never 256 SIs ? 255 (SIs) * 256 (bsl) = 65280 BFR¡¯s. How about modifying the rule as below ? 1. Allow 0 as valid value for ¡°label range size¡± 2. ¡°label-end¡± = ¡°label range base¡± + ¡°label range size¡± Thanks, Senthil »ªÎª¼¼ÊõÓÐÏÞ¹«Ë¾ Huawei Technologies Co., Ltd. [Company_logo] ________________________________ ±¾Óʼþ¼°Æ丽¼þº¬ÓлªÎª¹«Ë¾µÄ±£ÃÜÐÅÏ¢£¬½öÏÞÓÚ·¢Ë͸øÉÏÃæµØÖ·ÖÐÁгöµÄ¸öÈË»òȺ×é¡£½û Ö¹ÈκÎÆäËûÈËÒÔÈκÎÐÎʽʹÓ㨰üÀ¨µ«²»ÏÞÓÚÈ«²¿»ò²¿·ÖµØй¶¡¢¸´ÖÆ¡¢»òÉ¢·¢£©±¾ÓʼþÖÐ µÄÐÅÏ¢¡£Èç¹ûÄú´íÊÕÁ˱¾Óʼþ£¬ÇëÄúÁ¢¼´µç»°»òÓʼþ֪ͨ·¢¼þÈ˲¢É¾³ý±¾Óʼþ£¡ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
- [Bier] Clarification regarding label-range-size i… Senthil Dhanaraj
- Re: [Bier] Clarification regarding label-range-si… Peter Psenak
- Re: [Bier] Clarification regarding label-range-si… Senthil Dhanaraj
- Re: [Bier] Clarification regarding label-range-si… Peter Psenak
- Re: [Bier] Clarification regarding label-range-si… Senthil Dhanaraj
- Re: [Bier] Clarification regarding label-range-si… IJsbrand Wijnands
- Re: [Bier] Clarification regarding label-range-si… Xiejingrong
- Re: [Bier] Clarification regarding label-range-si… Peter Psenak
- Re: [Bier] Clarification regarding label-range-si… Xiejingrong
- Re: [Bier] Clarification regarding label-range-si… Peter Psenak
- Re: [Bier] Clarification regarding label-range-si… Peter Psenak
- Re: [Bier] Clarification regarding label-range-si… Xiejingrong
- Re: [Bier] Clarification regarding label-range-si… Tony Przygienda
- Re: [Bier] Clarification regarding label-range-si… Senthil Dhanaraj
- Re: [Bier] Clarification regarding label-range-si… IJsbrand Wijnands (iwijnand)
- Re: [Bier] Clarification regarding label-range-si… Nagendra Kumar Nainar (naikumar)
- Re: [Bier] Clarification regarding label-range-si… Tony Przygienda
- Re: [Bier] Clarification regarding label-range-si… Les Ginsberg (ginsberg)
- Re: [Bier] Clarification regarding label-range-si… Alia Atlas