[Bier] FW: New Version Notification for draft-xie-bier-ipv6-encapsulation-07.txt

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Mon, 29 June 2020 09:33 UTC

Return-Path: <gengxuesong@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 14A943A0CED for <bier@ietfa.amsl.com>; Mon, 29 Jun 2020 02:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 uX_srmlkxtrn for <bier@ietfa.amsl.com>; Mon, 29 Jun 2020 02:33:12 -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 F0E723A0C01 for <bier@ietf.org>; Mon, 29 Jun 2020 02:33:11 -0700 (PDT)
Received: from lhreml739-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id A183378F46310A191C5F for <bier@ietf.org>; Mon, 29 Jun 2020 10:33:10 +0100 (IST)
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by lhreml739-chm.china.huawei.com (10.201.108.189) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 29 Jun 2020 10:33:09 +0100
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by nkgeml707-chm.china.huawei.com (10.98.57.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Mon, 29 Jun 2020 17:33:07 +0800
Received: from dggeme752-chm.china.huawei.com ([10.6.80.76]) by dggeme752-chm.china.huawei.com ([10.6.80.76]) with mapi id 15.01.1913.007; Mon, 29 Jun 2020 17:33:07 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: BIER WG <bier@ietf.org>
CC: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>
Thread-Topic: New Version Notification for draft-xie-bier-ipv6-encapsulation-07.txt
Thread-Index: AQHWTfbfj4rHV+oOC0mpeIBa+InnOKjvVEzA
Date: Mon, 29 Jun 2020 09:33:06 +0000
Message-ID: <699bffef4a454af6b4b525f85b1f07b8@huawei.com>
References: <159342255926.11093.10241301749765762117@ietfa.amsl.com>
In-Reply-To: <159342255926.11093.10241301749765762117@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.108.203.157]
Content-Type: multipart/alternative; boundary="_000_699bffef4a454af6b4b525f85b1f07b8huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/oOgJMMSoKm9MEwL8scurziZ3ni0>
Subject: [Bier] FW: New Version Notification for draft-xie-bier-ipv6-encapsulation-07.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, 29 Jun 2020 09:33:14 -0000

Hi BIER WG,



There have been a lot of discussions in BIER WG about BIERv6 and we have received a lot of useful comments from WG.

In this version, we updated the draft based on these comments. Here are some progress:

1.      A main concern about BIERv6 is the use of BIER proto field and IPv6 next header when considering BIERv6-OAM functioning.

We think this update addressed this problem, using IPv6 next header solely in BIERv6, and thus makes the solution far more clear.

2.      Another concern is security. We’ve improve the security considerations since rev-04. In this version , we has added more descriptions.

3.      IPv6 issues will be fully discussed in 6MAN hopefully.

Please let us know if the above change solve your problem. And any other comments are welcome.



Best Regards

Xuesong



> -----Original Message-----

> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]

> Sent: Monday, June 29, 2020 5:23 PM

> To: Mike McBride <mmcbride7@gmail.com>; Yongqing Zhu

> <zhuyq8@chinatelecom.cn>; Zhuangzhuang Qin

> <qinzhuangzhuang@chinaunicom.cn>; Senthil Dhanaraj

> <senthil.dhanaraj@huawei.com>; Gengxuesong (Geng Xuesong)

> <gengxuesong@huawei.com>; Xiejingrong (Jingrong)

> <xiejingrong@huawei.com>; Liang Geng <gengliang@chinamobile.com>;

> MooChang Shin <himzzang@lguplus.co.kr>; Rajiv Asati <rajiva@cisco.com>

> Subject: New Version Notification for draft-xie-bier-ipv6-encapsulation-07.txt

>

>

> A new version of I-D, draft-xie-bier-ipv6-encapsulation-07.txt

> has been successfully submitted by Xuesong Geng and posted to the IETF

> repository.

>

> Name:            draft-xie-bier-ipv6-encapsulation

> Revision:        07

> Title:               Encapsulation for BIER in Non-MPLS IPv6 Networks

> Document date:   2020-06-29

> Group:            Individual Submission

> Pages:            19

> URL:

> https://www.ietf.org/internet-drafts/draft-xie-bier-ipv6-encapsulation-07.txt

> Status:

> https://datatracker.ietf.org/doc/draft-xie-bier-ipv6-encapsulation/

> Htmlized:

> https://tools.ietf.org/html/draft-xie-bier-ipv6-encapsulation-07

> Htmlized:

> https://datatracker.ietf.org/doc/html/draft-xie-bier-ipv6-encapsulation

> Diff:

> https://www.ietf.org/rfcdiff?url2=draft-xie-bier-ipv6-encapsulation-07

>

> Abstract:

>    This document proposes a BIER IPv6 (BIERv6) encapsulation for Non-

>    MPLS IPv6 Networks using the IPv6 Destination Option extension

>    header.  This document updates RFC 8296.

>

>

>

>

>

> Please note that it may take a couple of minutes from the time of submission

> until the htmlized version and diff are available at tools.ietf.org.

>

> The IETF Secretariat

>