IETF Logo Mail Archive

[Bier] 回复： BIER rechartering

" 徐小虎(义先) " <xiaohu.xxh@alibaba-inc.com> Wed, 24 January 2018 01:32 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 0000512D890; Tue, 23 Jan 2018 17:32:55 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 5zzPK8vGSFau; Tue, 23 Jan 2018 17:32:53 -0800 (PST)
Received: from out0-250.mail.aliyun.com (out0-250.mail.aliyun.com [140.205.0.250]) (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 D0BD3120047; Tue, 23 Jan 2018 17:32:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1516757568; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=n7cXd+3HaPFAOd8hSgAKZAPh26y081N8TJRjHQnTfko=; b=iYjJWSPzDCWQ8MZ4pznJYZhsG6Hf4MOflAP1bHrOVK+8Th3syCD9W3yweS/C4wZ1X6tQ1bjZT7pL5OqWsp8WJgaIh+RAcUoi5BRvY7b51e7HECtdmFvw8+SYQZGsmyf3VQNF/H3/NOt6vM6Vl52RHZ6mXRQDdw7rqlk4VEWAo4o=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R571e4; CH=green; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03296; MF=xiaohu.xxh@alibaba-inc.com; NM=1; PH=DW; RN=3; SR=0; TI=W4_5166270_DEFAULT_0AC26611_1516757388825_o7001c90r;
Received: from WS-web (xiaohu.xxh@alibaba-inc.com[W4_5166270_DEFAULT_0AC26611_1516757388825_o7001c90r]) by e02c03277.eu6 at Wed, 24 Jan 2018 09:32:46 +0800
Date: Wed, 24 Jan 2018 09:32:46 +0800
From: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
To: "Dolganow, Andrew (Nokia - SG/Singapore)" <andrew.dolganow@nokia.com>, BIER <bier-bounces@ietf.org>
Cc: "bier@ietf.org" <bier@ietf.org>
Reply-To: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
Message-ID: <593e9503-97bd-44a1-917f-e6ee79e72db7.xiaohu.xxh@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent][W4_5166270][DEFAULT][Safari]
MIME-Version: 1.0
References: <CAG4d1rdCysU+qnb=9U9iaZ+UefudWYDmz=mNPSfhDPuWNQQHVw@mail.gmail.com> <B9800CBE-2810-46F9-B802-8823AE769699@nokia.com>, CA+wi2hO112XTHLZuJSsPxZzGhAY1A6RTGDBt-+n6XXc6WXodDw@mail.gmail.com
In-Reply-To: CA+wi2hO112XTHLZuJSsPxZzGhAY1A6RTGDBt-+n6XXc6WXodDw@mail.gmail.com
x-aliyun-mail-creator: W4_5166270_DEFAULT_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTJfMykgQXBwbGVXZWJLaXQvNjAyLjQuOCAoS0hUTUwsIGxpa2UgR2Vja28pIFZlcnNpb24vMTAuMC4zIFNhZmFyaS82MDIuNC44La
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_53567_592e1940_5a67e23e_1a47b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/Kx1wsnU8339jDIwrk9z9NoGXDp8>
Subject: [Bier] 回复： BIER rechartering
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, 24 Jan 2018 01:32:56 -0000

I'm a bit confused about the motivation of the following BIER-IN-IPV6 mechanism. If it's targeted for the hop-by-hop forwarding paradigm, wouldn't the non-MPLS -BIER encapsulation (over Ethernet) be good enough? 
Best regards,Xiaohu------------------------------------------------------------------发件人：Tony Przygienda <tonysietf@gmail.com>发送时间：2018年1月24日(星期三) 09:00收件人："Dolganow, Andrew (Nokia - SG/Singapore)" <andrew.dolganow@nokia.com>抄　送：bier@ietf.org <bier@ietf.org>主　题：Re: [Bier] BIER rechartering


Ad> Can we say “in co-operation with IETF WGs chartered with IGP protocol ownership”  instead of “in cooperation
 with the LSR WG”. DO not want to re-charter in case we change/modify/merge/evolve other WGs.

The BIER-WG is additionally chartered to start Standards Track work on:

  7) BIER in IPv6 :  A mechanism to use BIER natively in IPv6 may be

     standardized if coordinated with the 6MAN WG and with understood

     applicability.  Such functionality may focus on assuming software or

     slow-path support first.Ad> I do not think we should limit unnecessarily the solution or open doors for things that are possible (anything can be done in S/W) but potentially of little value.
 SO if someone brings a proposal for slow-path BIER we will evaluate on usefulness to use case being solved.
https://tools.ietf.org/html/draft-zhang-bier-bierin6-00
 

v2.23.0 | Report a Bug | By Email