[Bier] FW: New Version Notification for draft-xie-bier-6man-encapsulation-02.txt
Xiejingrong <xiejingrong@huawei.com> Mon, 10 September 2018 07:57 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 B49E1130E2E for <bier@ietfa.amsl.com>; Mon, 10 Sep 2018 00:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 w6rXFgeRLVUa for <bier@ietfa.amsl.com>; Mon, 10 Sep 2018 00:57:06 -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 AF08E12008A for <bier@ietf.org>; Mon, 10 Sep 2018 00:57:06 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 571D58F14FD34 for <bier@ietf.org>; Mon, 10 Sep 2018 08:57:03 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.399.0; Mon, 10 Sep 2018 08:57:04 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.129]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0399.000; Mon, 10 Sep 2018 15:56:55 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: "bier@ietf.org" <bier@ietf.org>
Thread-Topic: New Version Notification for draft-xie-bier-6man-encapsulation-02.txt
Thread-Index: AQHUQdLkU8Nf0oN8yUWIZGV791qs3qTpKxag
Date: Mon, 10 Sep 2018 07:56:54 +0000
Message-ID: <16253F7987E4F346823E305D08F9115A99AE8B8D@nkgeml514-mbs.china.huawei.com>
References: <153579270345.20821.16669021473549267095.idtracker@ietfa.amsl.com>
In-Reply-To: <153579270345.20821.16669021473549267095.idtracker@ietfa.amsl.com>
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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/8dFodv9n-fsqx38a_B2NW1dFL7o>
Subject: [Bier] FW: New Version Notification for draft-xie-bier-6man-encapsulation-02.txt
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, 10 Sep 2018 07:57:09 -0000
Hi folks, I found some of the interesting discussion and drafts about BIER IPv6 encapsulation in the mail-list. (1) encap BIER information in IPv6 128-bit addresses. (2) encap BIER header and BIER payload as IPv6 payload for slow path processing. (3) encap BIER header in some IPv6 extension header. When the first method was discussed in Sep 2016, there was a suggestion to provide a method of using IPv6 extension header for comparison. Well I think this draft provided one... https://www.ietf.org/mail-archive/web/bier/current/msg00986.html Again there were some 'requirements' mentioned by this thread, and this draft seemed to match them well... https://www.ietf.org/mail-archive/web/bier/current/msg00991.html "it shouldn't require hop-by-hop modification of the IP destination address field, and it shouldn't require the BFRs to inspect layer 4, and it shouldn't require changes to layer 4, and it shouldn't allow a multicast address to be put in the IP source address field, and it shouldn't assume that bits never get set incorrectly, and it shouldn't require changes in source address filtering procedures. In addition, it should be possible to use it to support the entire BIER architecture" Comments and discussions are very welcomed. Thanks Jingrong