Re: [Bier] Request For Comments on BIER IPv6 work and documents -- RE: Questions regarding <draft-zhang-bier-bierin6-03>
Xiejingrong <xiejingrong@huawei.com> Wed, 17 July 2019 22:45 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 AB977120044; Wed, 17 Jul 2019 15:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 BuTZ3bNyrQU1; Wed, 17 Jul 2019 15:45:13 -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 198431200F9; Wed, 17 Jul 2019 15:45:13 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5117C8DB40A85DD8EA79; Wed, 17 Jul 2019 23:45:11 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 17 Jul 2019 23:45:10 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.142]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0439.000; Thu, 18 Jul 2019 06:44:52 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: BIER WG <bier@ietf.org>, "bier-chairs@ietf.org" <bier-chairs@ietf.org>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>
CC: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, "draft-zhang-bier-bierin6@ietf.org" <draft-zhang-bier-bierin6@ietf.org>
Thread-Topic: Request For Comments on BIER IPv6 work and documents -- RE: Questions regarding <draft-zhang-bier-bierin6-03>
Thread-Index: AdU32uDY4M7XOGV+QemdVnyRKAdECwFFhA24
Date: Wed, 17 Jul 2019 22:44:52 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB8F2B2B@nkgeml514-mbs.china.huawei.com>
References: <16253F7987E4F346823E305D08F9115AAB8DD007@nkgeml514-mbx.china.huawei.com>
In-Reply-To: <16253F7987E4F346823E305D08F9115AAB8DD007@nkgeml514-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.124.93.24]
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115AAB8F2B2Bnkgeml514mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/VBjywLaqz9l2ssya1ho52N_Y3ZY>
Subject: Re: [Bier] Request For Comments on BIER IPv6 work and documents -- RE: Questions regarding <draft-zhang-bier-bierin6-03>
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: Wed, 17 Jul 2019 22:45:16 -0000
Repost. ________________________________ From: BIER [bier-bounces@ietf.org] on behalf of Xiejingrong [xiejingrong@huawei.com] Sent: Thursday, July 11, 2019 19:29 To: BIER WG; bier-chairs@ietf.org; aretana.ietf@gmail.com Cc: Jeffrey (Zhaohui) Zhang; draft-zhang-bier-bierin6@ietf.org Subject: [Bier] Request For Comments on BIER IPv6 work and documents -- RE: Questions regarding <draft-zhang-bier-bierin6-03> Dear BIER WG: I would prefer very much the comments on the maillist about BIER IPv6. I think it is the way we improve and progress documents, and improve the work of BIER WG. There have been quite a number of BIERv6 drafts, and the WG had make it clear to work on "BIER natively in IPv6" in charter. Also there have been a work achievement of BIERv6-requirements WG document since ietf104. Also from this thread before, and from the recent BIER sessions, BIER'es have shown enthusiasm on BIER IPv6: a) ipv6 tunnel between non-adjacent BFRs b) situations even between adjacent BFRs. Also as the stated by Toerless in inetf104: We need to wait for the result in SRv6 arch and encap work as they consider 8200 requirements during review. It applicable to hear as well. I think it is more clear now, since the SRv6 SRH had LC, the SRv6 Network Programming had adopted, the SRv6-via-ISIS had adopted, and many SRv6 deployments or implementations or ongoing implementations. Request the WG to initiate the discussions/questions/comparisons on the following BIERv6 documents: https://datatracker.ietf.org/doc/draft-ietf-bier-ipv6-requirements/ https://datatracker.ietf.org/doc/draft-xie-bier-ipv6-encapsulation/ https://datatracker.ietf.org/doc/draft-xie-bier-ipv6-isis-extension/ https://datatracker.ietf.org/doc/draft-xie-bier-ipv6-mvpn/ https://datatracker.ietf.org/doc/draft-geng-bier-ipv6-inter-domain/ https://datatracker.ietf.org/doc/draft-zhang-bier-bierin6/ I guess you have many comments/suggestions/questions/comparisons. Do you ? There had been 2* 40 minutes talk at Bankok and Prague BIER sessions! Appreciate very much for your comments/suggestions/questions/comparisons! Appreciate very much for the guidance from Chairs and the AD! Thanks, Jingrong
- [Bier] Request For Comments on BIER IPv6 work and… Xiejingrong
- Re: [Bier] Request For Comments on BIER IPv6 work… Xiejingrong