IETF Logo Mail Archive

Re: [Idr] WG adoption call for draft-chen-idr-bier-te-path-04.txt (6/22/2022 to 7/6/2022

chen.ran@zte.com.cn Fri, 24 June 2022 03:13 UTC

Return-Path: <chen.ran@zte.com.cn>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7249FC157B34 for <idr@ietfa.amsl.com>; Thu, 23 Jun 2022 20:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tWXVdXsIJjRq for <idr@ietfa.amsl.com>; Thu, 23 Jun 2022 20:13:40 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC715C14CF12 for <idr@ietf.org>; Thu, 23 Jun 2022 20:13:39 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4LThz5580Cz4xVnQ; Fri, 24 Jun 2022 11:13:37 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 25O3DQBl081300; Fri, 24 Jun 2022 11:13:26 +0800 (GMT-8) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Fri, 24 Jun 2022 11:13:26 +0800 (CST)
Date: Fri, 24 Jun 2022 11:13:26 +0800
X-Zmail-TransId: 2afb62b52bd6ffffffffb0fd7d80
X-Mailer: Zmail v1.0
Message-ID: <202206241113267593988@zte.com.cn>
In-Reply-To: <BYAPR08MB487248371C3A44A690DDDEB7B3B29@BYAPR08MB4872.namprd08.prod.outlook.com>
References: BYAPR08MB487248371C3A44A690DDDEB7B3B29@BYAPR08MB4872.namprd08.prod.outlook.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: shares@ndzh.com, idr@ietf.org
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl1.zte.com.cn 25O3DQBl081300
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 62B52BE1.000 by FangMail milter!
X-FangMail-Envelope: 1656040417/4LThz5580Cz4xVnQ/62B52BE1.000/10.30.14.238/[10.30.14.238]/mse-fl1.zte.com.cn/<chen.ran@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 62B52BE1.000/4LThz5580Cz4xVnQ
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/56A-ScPvNH8FNq2L-lUrhUHOEoQ>
Subject: Re: [Idr] WG adoption call for draft-chen-idr-bier-te-path-04.txt (6/22/2022 to 7/6/2022
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2022 03:13:43 -0000

Hi WG,
I Support the adoption of this draft. 

Thanks,
Ran

------------------原始邮件------------------
发件人：SusanHares
收件人：idr@ietf.org;
日 期 ：2022年06月23日 00:05
主 题 ：[Idr] WG adoption call for draft-chen-idr-bier-te-path-04.txt (6/22/2022 to 7/6/2022
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

This begins a 2 week Adoption call (6/22/2022 to 7/6/2022)
for draft-chen-idr-bier-te-path-04.txt
(https://datatracker.ietf.org/doc/draft-chen-idr-bier-te-path/).
This draft provides extensions to BGP to distribute BIER
(bit replication traffic/tree) data via BGP using a
new NLRI (AFI = IPv4 or IPv6, new SAFI) and
new options for the Tunnel Encapsulation Attribute (TEA).
The NLRI includes an RD + Bier Domain tunnel identifier.
In your comments, please consider if this draft:
1) Does this draft specify appropriate BGP mechanisms for
a controller to distribute bier information?
2) Does this mechanism correctly integrates into
a) the BIER architecture (draft-ietf-bier-te-arch) and
b) Multicast VPNs (BESS)?
3) Will this technology aid the deployment of
Bier multicast forwarding in operational networks?
Cheers, Sue

v2.23.0 | Report a Bug | By Email