Re: [Bier] Comments on draft-ietf-bier-bier-yang
Xiejingrong <xiejingrong@huawei.com> Mon, 01 April 2019 10:10 UTC
Return-Path: <xiejingrong@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 64F9D120075; Mon, 1 Apr 2019 03:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 aoe6g3aDAXcR; Mon, 1 Apr 2019 03:10:33 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 691741200E3; Mon, 1 Apr 2019 03:10:32 -0700 (PDT)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 3EFCB66972598A15DFA8; Mon, 1 Apr 2019 11:10:30 +0100 (IST)
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 1 Apr 2019 11:10:29 +0100
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 1 Apr 2019 11:10:29 +0100
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Mon, 1 Apr 2019 11:10:28 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0415.000; Mon, 1 Apr 2019 18:10:19 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: "chen.ran@zte.com.cn" <chen.ran@zte.com.cn>
CC: "bier@ietf.org" <bier@ietf.org>, "draft-ietf-bier-bier-yang@ietf.org" <draft-ietf-bier-bier-yang@ietf.org>
Thread-Topic: Re: [Bier] Comments on draft-ietf-bier-bier-yang
Thread-Index: AQHUJnMQPgoFuiu7LkeDTadk4LelJ6TjI4ShgUVg8tA=
Date: Mon, 01 Apr 2019 10:10:18 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB872447@nkgeml514-mbx.china.huawei.com>
References: 16253F7987E4F346823E305D08F9115A99ABD1D3@nkgeml514-mbs.china.huawei.com, CF67507D-A18D-485E-9947-70964B4C660D <201809061603576337769@zte.com.cn>
In-Reply-To: <201809061603576337769@zte.com.cn>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.217.214]
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115AAB872447nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/KrydfTydrw_doQBF-6WO_VP3G_s>
Subject: Re: [Bier] Comments on draft-ietf-bier-bier-yang
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Apr 2019 10:10:35 -0000
Hi Chen Ran, [Ran] "load-balance-number"?Do you means the maximum number of ECMP paths? OSPF YANG data model has defined it .In my opinion, it is neccesarry to define this item here. [XJR1]: Yes I found the load-balance(max-ecmp) configuration in OSPF-yang and ISIS-yang, but I think they are different things, and there should be a load-balance-number for BIER specifically: (1) A BFR may not support BIER ECMP forwarding, while unicast ECMP is supported. (2) There may be different number of paths to different BFERs, for example BFER2/BFER2 may have 3/5 paths separately on a BFR, and this BFR may want a special load-balance-number 15 for better balancing. [XJR2]: Second question: Is it allowed for both IPv4-encapsulation and IPv6-encapsulation being under a single Sub-domain ? augment /rt:routing: +--rw bier | +--rw bier-global | +--rw sub-domain* [sub-domain-id] | +--rw sub-domain-id sub-domain-id | +--rw underlay-protocol-type? underlay-protocol-type | +--rw mt-id? mt-id | +--rw bfr-id? bfr-id | +--rw bitstringlength? bsl | +--rw igp-algorithm? ipa | +--rw bier-algorithm? bar | +--rw af | +--rw ipv4* [bitstringlength bier-mpls-label-base] | | +--rw bitstringlength uint16 | | +--rw bier-mpls-label-base rt-types:mpls-label | | +--rw max-si? max-si | +--rw ipv6* [bitstringlength bier-mpls-label-base] | +--rw bitstrin+--glength uint16 | +--rw bier-mpls-label-base rt-types:mpls-label | +--rw max-si? max-si | The RFC8279 said, a BIER sub-domain must be associated with a single routing underlay (see below). I would understand IPv4 and IPv6 as different underlay. If multiple routing underlays are used in a single BIER domain, each BIER sub-domain MUST be associated with a single routing underlay (though multiple sub-domains may be associated with the same routing underlay). [XJR3]: Third question, maybe for the BIER WG. It may also be helpful to discuss and conclude, if it is allowed for both BIER-MPLS encapsulation and BIER-Ethernet encapsulation being under a single sub-domain? I feel it unnecessary since one can use different BIER Sub-domains carrying different encapsulations, and thus an MVPN service using BIER doesn’t have to specify the encapsulation-type. From: chen.ran@zte.com.cn [mailto:chen.ran@zte.com.cn] Sent: Thursday, September 06, 2018 4:04 PM To: Xiejingrong <xiejingrong@huawei.com> Cc: bier@ietf.org; draft-ietf-bier-bier-yang@ietf.org Subject: Re: Re: [Bier] Comments on draft-ietf-bier-bier-yang Hi jinrong, Thanks for your review. Please see inline... Regards. Ran 原始邮件 发件人:Xiejingrong <xiejingrong@huawei.com<mailto:xiejingrong@huawei.com>> 收件人:BIER WG <bier@ietf.org<mailto:bier@ietf.org>> 抄送人:draft-ietf-bier-bier-yang@ietf.org<mailto:draft-ietf-bier-bier-yang@ietf.org> <draft-ietf-bier-bier-yang@ietf.org<mailto:draft-ietf-bier-bier-yang@ietf.org>> 日 期 :2018年07月28日 21:01 主 题 :Re: [Bier] Comments on draft-ietf-bier-bier-yang _______________________________________________ BIER mailing list BIER@ietf.org<mailto:BIER@ietf.org> https://www.ietf.org/mailman/listinfo/bier some more comments: 1. one sub-domain should allow miltiple {BSL and the according label block}s as encapsulations, see the igp sub-sub-TLV. [Ran] We will add them ,and will add the enternet and IPv6 encapsulation type. 2. should the igp-type change to underlay-protocol-type to allow bgp? [Ran ]will add it. From:Xiejingrong To:BIER WG, Cc:draft-ietf-bier-bier-yang@ietf.org, Date:2018-07-28 20:36:25 Subject:[Bier] Comments on draft-ietf-bier-bier-yang Hi folks, I have the following comments and on draft-ietf-bier-bier-yang. --should the bier load-balance-number/ipa/bar be added to rt:routing/bier-global/sub-domain (like below)? I think they are some basic items. [Ran] "load-balance-number"?Do you means the maximum number of ECMP paths? OSPF YANG data model has defined it .In my opinion, it is neccesarry to define this item here. For the ipa/bar will be added to rt:routing/bier-global/sub-domain. augment /rt:routing: +--rw bier | +--rw bier-global | +--rw encapsulation-type? identityref | +--rw bitstringlength? bsl | +--rw bfr-id? bfr-id | +--rw ipv4-bfr-prefix? inet:ipv4-prefix | +--rw ipv6-bfr-prefix? inet:ipv6-prefix | +--rw sub-domain* [sub-domain-id] | +--rw sub-domain-id sub-domain-id | +--rw igp-type? igp-type | +--rw mt-id? mt-id | +--rw bfr-id? bfr-id | +--rw bitstringlength? bsl | +--rw multi-bift-number? load-balance-number | +--rw igp-algorithm? ipa | +--rw bier-algorithm? bar --should the bier-mpls-label-range-size be changed to ‘max si’ or not ? The type is uint8 and thus seems having to change the meaning. [Ran] Sure. Thanks Jingrong
- [Bier] Comments on draft-ietf-bier-bier-yang Xiejingrong
- Re: [Bier] Comments on draft-ietf-bier-bier-yang Xiejingrong
- Re: [Bier] Comments on draft-ietf-bier-bier-yang chen.ran
- Re: [Bier] Comments on draft-ietf-bier-bier-yang Xiejingrong
- Re: [Bier] Comments on draft-ietf-bier-bier-yang Senthil Dhanaraj
- Re: [Bier] Comments on draft-ietf-bier-bier-yang zhang.zheng
- Re: [Bier] Comments on draft-ietf-bier-bier-yang Senthil Dhanaraj
- Re: [Bier] Comments on draft-ietf-bier-bier-yang Xiejingrong
- Re: [Bier] Comments on draft-ietf-bier-bier-yang zhang.zheng
- Re: [Bier] Comments on draft-ietf-bier-bier-yang zhang.zheng
- Re: [Bier] Comments on draft-ietf-bier-bier-yang Senthil Dhanaraj
- Re: [Bier] Comments on draft-ietf-bier-bier-yang zhang.zheng
- Re: [Bier] Comments on draft-ietf-bier-bier-yang Senthil Dhanaraj
- Re: [Bier] Comments on draft-ietf-bier-bier-yang zhang.zheng