[Bier] Request comments on draft-chen-pce-bier-10
chen.ran@zte.com.cn Tue, 28 February 2023 08:07 UTC
Return-Path: <chen.ran@zte.com.cn>
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 8CDA7C14CF1D; Tue, 28 Feb 2023 00:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 KzwG1b82Aavh; Tue, 28 Feb 2023 00:07:07 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE7D0C14F72F; Tue, 28 Feb 2023 00:07:06 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4PQqhl2d0Gz8R048; Tue, 28 Feb 2023 16:07:03 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4PQqh91tbQz501TM; Tue, 28 Feb 2023 16:06:33 +0800 (CST)
Received: from njy2app04.zte.com.cn ([10.40.12.64]) by mse-fl1.zte.com.cn with SMTP id 31S85qNi096067; Tue, 28 Feb 2023 16:06:17 +0800 (+08) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njy2app03[null]) by mapi (Zmail) with MAPI id mid203; Tue, 28 Feb 2023 16:06:20 +0800 (CST)
Date: Tue, 28 Feb 2023 16:06:20 +0800
X-Zmail-TransId: 2afb63fdb5fc21831700
X-Mailer: Zmail v1.0
Message-ID: <202302281606202219021@zte.com.cn>
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: bier@ietf.org, bier-chairs@ietf.org
Cc: draft-chen-pce-bier@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 31S85qNi096067
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.137.novalocal with ID 63FDB627.001 by FangMail milter!
X-FangMail-Envelope: 1677571623/4PQqhl2d0Gz8R048/63FDB627.001/192.168.251.13/[192.168.251.13]/mxct.zte.com.cn/<chen.ran@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 63FDB627.001/4PQqhl2d0Gz8R048
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/ODl-OeHyMiaqCZ62CbMi1Rna8ls>
Subject: [Bier] Request comments on draft-chen-pce-bier-10
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 28 Feb 2023 08:07:11 -0000
Hi Chairs and WG, We have updated https://datatracker.ietf.org/doc/draft-chen-pce-bier/ based on the comments from IETF meeting. Any comments are welcome. The current PCE-BIER related drafts are as follows： https://datatracker.ietf.org/doc/draft-chen-pce-bier/: This document specifies extensions to the Path Computation Element Protocol (PCEP) that allow a PCE to compute and initiate the path for the BIER-TE. This draft mainly focuses on the path calculation of BIER-TE and The controller distributes a BIER-TE path to the BFIR via protocol extensions like the PCEP [https://datatracker.ietf.org/doc/draft-chen-pce-bier/ ] or BGP BIER-TE[https://datatracker.ietf.org/doc/draft-ietf-idr-bier-te-path/] .The two functions are used for the communication between controller and BFIR. https://datatracker.ietf.org/doc/draft-chen-pce-pcep-extension-pce-controller-bier/: https://datatracker.ietf.org/doc/draft-chen-pce-controller-bier-te/: These two drafts focus on the central controller scenario,specify a new mechanism where PCE allocates the BIER/BIER-TE information centrally and uses PCEP to distribute them to all nodes (include BFR, BFIR and BFER), for example the BFR-ID allocation, the download of BIFT, then PCC generate a "Bit Index Forwarding Table"(BIFT). These functions are used for the situation which there is no IGP running in the BIER domain. Of course, we can also directly distribute BIFT through the YANG model[see BIER YANG and BIER-TE YANG]. Since there are many southbound interface protocols, we would like to write an informational draft to introduce the relationship between these drafts and how to use.