Re: [Bier] New Version Notification for draft-ietf-bier-ipv6-requirements-01.txt

Xiejingrong <xiejingrong@huawei.com> Mon, 01 July 2019 09:25 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 46287120059 for <bier@ietfa.amsl.com>; Mon, 1 Jul 2019 02:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 C8W5d0hGlGMO for <bier@ietfa.amsl.com>; Mon, 1 Jul 2019 02:25:29 -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 31639120052 for <bier@ietf.org>; Mon, 1 Jul 2019 02:25:29 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 563F28DBF3A830A4B7E2 for <bier@ietf.org>; Mon, 1 Jul 2019 10:25:27 +0100 (IST)
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 1 Jul 2019 10:25:26 +0100
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 1 Jul 2019 10:25:26 +0100
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml705-chm.china.huawei.com (10.201.108.54) 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 Jul 2019 10:25:26 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0415.000; Mon, 1 Jul 2019 17:25:06 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: Senthil Dhanaraj <senthil.dhanaraj@huawei.com>, Mike McBride <michael.mcbride@futurewei.com>, Rajiv Asati <rajiva@cisco.com>
CC: BIER WG <bier@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-bier-ipv6-requirements-01.txt
Thread-Index: AQHVL+3wBtHWhE+YnEmpWEbqgVTYfaa1e/2w
Date: Mon, 01 Jul 2019 09:25:06 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB8D8BF8@nkgeml514-mbx.china.huawei.com>
References: <156197269793.5671.6999339510931673806.idtracker@ietfa.amsl.com>
In-Reply-To: <156197269793.5671.6999339510931673806.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/_nYqoyMb44vrtbmcyMZGG7O17Ws>
Subject: Re: [Bier] New Version Notification for draft-ietf-bier-ipv6-requirements-01.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, 01 Jul 2019 09:25:31 -0000

Hi 
I submitted -01 rev of this draft in xml file.
Main change in this version:
Add text in "4.2. Hop by hop DA modification", "4.5. Incorrect bits", "4.7. BIER architecture support", and "4.8. Keep it simple", remove the "Multicast DA" in picture of 5.3 
Per the discussion in ietf104, the mail I posted in the list before about using IPv6 unicast DA, and the modification of the BIERv6 documents.

Authors please update whatever you want and whatever nits you may found.

Thanks
Jingrong

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 01, 2019 5:18 PM
To: Senthil Dhanaraj <senthil.dhanaraj@huawei.com>; Xiejingrong <xiejingrong@huawei.com>; Mike McBride <michael.mcbride@futurewei.com>; Rajiv Asati <rajiva@cisco.com>
Subject: New Version Notification for draft-ietf-bier-ipv6-requirements-01.txt


A new version of I-D, draft-ietf-bier-ipv6-requirements-01.txt
has been successfully submitted by Jingrong Xie and posted to the IETF repository.

Name:		draft-ietf-bier-ipv6-requirements
Revision:	01
Title:		BIER IPv6 Requirements
Document date:	2019-07-01
Group:		bier
Pages:		13
URL:            https://www.ietf.org/internet-drafts/draft-ietf-bier-ipv6-requirements-01.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-bier-ipv6-requirements/
Htmlized:       https://tools.ietf.org/html/draft-ietf-bier-ipv6-requirements-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-bier-ipv6-requirements
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-ipv6-requirements-01

Abstract:
   The BIER WG has a charter item to work on mechanisms which use BIER
   natively in IPv6.  This document is intended to help the WG with this
   effort by specifying requirements for transporting packets, with Bit
   Index Explicit Replication (BIER) headers, in an IPv6 environment.
   There will be a need to send IPv6 payloads, to multiple IPv6
   destinations, using BIER.  There have been several proposed solutions
   in this area.  But there hasn't been a document which describes the
   problem and lists the requirements.  The goal of this document is to
   describe the BIER IPv6 requirements and summarize the pro's and con's
   of the proposed solutions.

                                                                                  


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