[Bier] 回复: Call for adoption: draft-wijnandsxu-bier-non-mpls-bift-encoding-01
" 徐小虎(义先) " <xiaohu.xxh@alibaba-inc.com> Wed, 28 February 2018 02:33 UTC
Return-Path: <xiaohu.xxh@alibaba-inc.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 2B931126CE8; Tue, 27 Feb 2018 18:33:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alibaba-inc.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 ZNgiaY7xe6iq; Tue, 27 Feb 2018 18:33:38 -0800 (PST)
Received: from out0-157.mail.aliyun.com (out0-157.mail.aliyun.com [140.205.0.157]) (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 304111241F5; Tue, 27 Feb 2018 18:33:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1519785211; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=A40ws9eRINLQPGwZsuvcpXS42L/1jO9Ncr8jbwdvEgg=; b=mkWjfbYROcvQ4syZ1jvqi1YHm4mJuqHDZBld9mTyA5bRVhtX1f3C8IpNoO/KyISOKS7Dobfs22nRIGyrBKXriJiKQjMalG9Pqh9zIHbVIwwK76O4RaAnkLH5Kquz7p3GMOsgMee4nddDzCGTjjZFo23SdB/1OeDTAtKBGzNHm4U=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R751e4; CH=green; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e01e01534; MF=xiaohu.xxh@alibaba-inc.com; NM=1; PH=DW; RN=4; SR=0; TI=W4_5181003_DEFAULT_0AC26465_1519784547194_o7001c1271j;
Received: from WS-web (xiaohu.xxh@alibaba-inc.com[W4_5181003_DEFAULT_0AC26465_1519784547194_o7001c1271j]) by e02c03269.eu6 at Wed, 28 Feb 2018 10:33:26 +0800
Date: Wed, 28 Feb 2018 10:33:26 +0800
From: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
To: IJsbrand Wijnands <ice@cisco.com>, BIER <bier-bounces@ietf.org>
Cc: gjshep <gjshep@gmail.com>, BIER WG <bier@ietf.org>
Reply-To: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
Message-ID: <708bd042-361b-47f6-a2dc-ce1214acab11.xiaohu.xxh@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent revision 948139][W4_5181003][DEFAULT][Safari]
MIME-Version: 1.0
References: <CABFReBrfrJU9u=ugG6Fs2dmZ+5vSs5pxySajfv9B7yvPuDW+hQ@mail.gmail.com> <938789da-1902-1a0e-98af-b2476204be62@juniper.net> <2B0FFBC1-FB91-4A6C-9800-69401C76B095@cisco.com> <d853e377-20a6-2bff-c959-ca16fcc12fad@juniper.net> <2B084F68-4854-4534-9F7D-A13A78E360E6@cisco.com>, <b82b8855-a363-ecfd-6622-1b12fecd8a87@juniper.net>
In-Reply-To: <b82b8855-a363-ecfd-6622-1b12fecd8a87@juniper.net>
x-aliyun-mail-creator: W4_5181003_DEFAULT_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTJfMykgQXBwbGVXZWJLaXQvNjAyLjQuOCAoS0hUTUwsIGxpa2UgR2Vja28pIFZlcnNpb24vMTAuMC4zIFNhZmFyaS82MDIuNC44La
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_90902_489c6940_5a9614f6_19c27f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/ANd3jVuUKXUllnqDjqb4jSR3bhM>
Subject: [Bier] 回复: Call for adoption: draft-wijnandsxu-bier-non-mpls-bift-encoding-01
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: Wed, 28 Feb 2018 02:33:41 -0000
Hi Eric, Thanks for your comments first of all. It's true that BFR-prefixes and BSLs would have to be provisioned. However, wouldn't it be better to automatically generate the BIFT-ids if possible? Best regards,Xiaohu ------------------------------------------------------------------发件人:Eric C Rosen <erosen@juniper.net>发送时间:2018年2月28日(星期三) 04:35收件人:IJsbrand Wijnands <ice@cisco.com>抄 送:gjshep <gjshep@gmail.com>; BIER WG <bier@ietf.org>主 题:Re: [Bier] Call for adoption: draft-wijnandsxu-bier-non-mpls-bift-encoding-01 What you're showing below is not a multi-vendor interoperability issue, it's a provisioning issue. The BIFT-id is only one of several parameters that need to be provisioned, and if the provisioning system cannot manage the BIFT-ids, it's hard to see how it can manage the provisioning of the BFR-prefixes and BSLs. To me, this seems a minor problem when compared to the possibility of an implementation that only works when the BIFT-id is constructed according to the algorithm of this draft. On 2/27/2018 12:59 PM, IJsbrand Wijnands wrote: > Eric, > > Maybe a configuration example helps: > > Consider the below configuration: > > router bier > encapsulation non-mpls bsl 256 > sub-domain 1 > source loopback 0 > bift-id auto > ! > ! > ! > > I would think that such configuration is the minimum required on every BIER router (unless there are default that don’t need to be required) independent of the vendor. > > Based on the above we can generate a BIFT-id following the draft proposal. Two different vendors having BIER configured will be interoperable because they generate the same BIFT-id, without having to configure it. > > It is also possible to configure: > > router bier > encapsulation non-mpls bsl 256 > sub-domain 1 > source loopback 0 > bift-id 10000 > ! > ! > ! > > Now the operator needs to manage value ‘10000’ and make sure its configure on every router the same. > > Thx, > > Ice. > > >> On 27 Feb 2018, at 18:46, Eric C Rosen <erosen@juniper.net> wrote: >> >> On 2/27/2018 12:25 PM, IJsbrand Wijnands wrote: >>> If we want to be interoperable among different vendors, I think it is good to have this documented. >> This is the sort of statement that really worries me. What is the interoperability issue? As long as a vendor allows the assignment of BIFT-ids, interoperability should be possible without the need for any particular suggested way of constructing the BIFT-ids. >> >> I'm not sure we can say both that the draft is informational, and that it is needed for multi-vendor interoperability. >> _______________________________________________ BIER mailing list BIER@ietf.org https://www.ietf.org/mailman/listinfo/bier
- [Bier] Call for adoption: draft-wijnandsxu-bier-n… Greg Shepherd
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Xiejingrong
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… zhang.zheng
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Bidgoli, Hooman (Nokia - CA/Ottawa)
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Jeffrey (Zhaohui) Zhang
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Jeff Tantsura
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Senthil Dhanaraj
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… xiong.quan
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Nagendra Kumar Nainar (naikumar)
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Eric C Rosen
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Tony Przygienda
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… IJsbrand Wijnands
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Eric C Rosen
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… IJsbrand Wijnands
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Greg Mirsky
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… IJsbrand Wijnands
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Eric C Rosen
- [Bier] 回复: Call for adoption: draft-wijnandsxu-bi… 徐小虎(义先)
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… IJsbrand Wijnands
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Eric C Rosen
- Re: [Bier] 回复: Call for adoption: draft-wijnandsx… Eric C Rosen
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… IJsbrand Wijnands
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Tony Przygienda
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Tony Przygienda
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… 徐小虎(义先)
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Tony Przygienda
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Tony Przygienda
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Tony Przygienda
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… zhang.zheng
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… Tony Przygienda
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… zhang.zheng
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… Toerless Eckert
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… Tony Przygienda
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… Toerless Eckert
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… Tony Przygienda
- Re: [Bier] Call for adoption:draft-wijnandsxu-bie… Toerless Eckert
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Nabeel Cocker
- Re: [Bier] Call for adoption: draft-wijnandsxu-bi… Greg Shepherd