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

Aijun Wang <wangaijun@tsinghua.org.cn> Tue, 28 June 2022 07:05 UTC

Return-Path: <wangaijun@tsinghua.org.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 7BD05C15948E for <idr@ietfa.amsl.com>; Tue, 28 Jun 2022 00:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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, 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 0q5rMZ1ivqmg for <idr@ietfa.amsl.com>; Tue, 28 Jun 2022 00:05:34 -0700 (PDT)
Received: from mail-m17638.qiye.163.com (mail-m17638.qiye.163.com [59.111.176.38]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 488AAC147930 for <idr@ietf.org>; Tue, 28 Jun 2022 00:05:32 -0700 (PDT)
Received: from DESKTOP2IOH5QC (unknown [219.142.69.75]) by mail-m17638.qiye.163.com (Hmail) with ESMTPA id 4F7361C0119; Tue, 28 Jun 2022 15:05:30 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Susan Hares' <shares@ndzh.com>, idr@ietf.org
References: <BYAPR08MB487248371C3A44A690DDDEB7B3B29@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB487248371C3A44A690DDDEB7B3B29@BYAPR08MB4872.namprd08.prod.outlook.com>
Date: Tue, 28 Jun 2022 15:05:29 +0800
Message-ID: <008c01d88abd$7352ae00$59f80a00$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008D_01D88B00.81785F00"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQEaIovmdRT1S5WVVVz4KIsZDtglNq7hNJBw
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVlCTkNKVkgYHUsaHkJLTEtKGVUTARMWGhIXJB QOD1lXWRgSC1lBWUlKQlVKT0lVTUJVTE5ZV1kWGg8SFR0UWUFZT0tIVUpKS0hKTFVLWQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6PSI6KRw*Aj0zODBII00PIxMU F0IKFEpVSlVKTU5NSEJCQkhLQ0lDVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQUpKSUxLNwY+
X-HM-Tid: 0a81a921241bd993kuws4f7361c0119
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/KfwDj6lEBC9N7zogRoyRY73itNQ>
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: Tue, 28 Jun 2022 07:05:36 -0000

Yes/Support

 

It is necessary for the deployment of BIER-TE path information via BGP.

 

Best Regards

 

Aijun Wang

China Telecom

 

From: idr-bounces@ietf.org <idr-bounces@ietf.org> On Behalf Of Susan Hares
Sent: Thursday, June 23, 2022 12:05 AM
To: idr@ietf.org
Subject: [Idr] WG adoption call for draft-chen-idr-bier-te-path-04.txt
(6/22/2022 to 7/6/2022

 

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