Re: [Pce] New Version Notification for draft-chen-pce-bier-10.txt
chen.ran@zte.com.cn Tue, 28 February 2023 08:01 UTC
Return-Path: <chen.ran@zte.com.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90DF5C14F72F; Tue, 28 Feb 2023 00:01:40 -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 bwZMnZxezMoE; Tue, 28 Feb 2023 00:01:39 -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 5EC5EC15152D; Tue, 28 Feb 2023 00:01:37 -0800 (PST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (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 4PQqZN6yfzz8R044; Tue, 28 Feb 2023 16:01:32 +0800 (CST)
Received: from njy2app02.zte.com.cn ([10.40.13.116]) by mse-fl2.zte.com.cn with SMTP id 31S81La7000766; Tue, 28 Feb 2023 16:01:21 +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:01:23 +0800 (CST)
Date: Tue, 28 Feb 2023 16:01:23 +0800
X-Zmail-TransId: 2afb63fdb4d3fffffffff1224408
X-Mailer: Zmail v1.0
Message-ID: <202302281601234588846@zte.com.cn>
In-Reply-To: <167755278027.37748.4997815843860097953@ietfa.amsl.com>
References: 167755278027.37748.4997815843860097953@ietfa.amsl.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: pce-chairs@ietf.org, pce@ietf.org
Cc: draft-chen-pce-bier@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 31S81La7000766
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.137.novalocal with ID 63FDB4DC.002 by FangMail milter!
X-FangMail-Envelope: 1677571292/4PQqZN6yfzz8R044/63FDB4DC.002/10.5.228.133/[10.5.228.133]/mse-fl2.zte.com.cn/<chen.ran@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 63FDB4DC.002/4PQqZN6yfzz8R044
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/5FDJrUtnJgUqCNMKXZLqwJ4eI_k>
Subject: Re: [Pce] New Version Notification for draft-chen-pce-bier-10.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2023 08:01:40 -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(include PCE, BGP, BGP-LS, YANG), we would like to write an informational draft to introduce the relationship between these drafts and how to use. Original From: internet-drafts@ietf.org <internet-drafts@ietf.org> To: Aijun Wang <wangaj3@chinatelecom.cn>;Fengwei Qin <qinfengwei@chinamobile.com>;Huaimo Chen <huaimo.chen@futurewei.com>;陈然00080434;Senthil Dhanaraj <senthil.dhanaraj.ietf@gmail.com>;张征00007940; Date: 2023年02月28日 10:53 Subject: New Version Notification for draft-chen-pce-bier-10.txt A new version of I-D, draft-chen-pce-bier-10.txt has been successfully submitted by Ran Chen and posted to the IETF repository. Name: draft-chen-pce-bier Revision: 10 Title: PCEP Extensions for BIER-TE Document date: 2023-02-28 Group: Individual Submission Pages: 16 URL: https://www.ietf.org/archive/id/draft-chen-pce-bier-10.txt Status: https://datatracker.ietf.org/doc/draft-chen-pce-bier/ Htmlized: https://datatracker.ietf.org/doc/html/draft-chen-pce-bier Diff: https://author-tools.ietf.org/iddiff?url2=draft-chen-pce-bier-10 Abstract: Bit Index Explicit Replication (BIER)-TE shares architecture and packet formats with BIER as described in [RFC8279]. BIER-TE forwards and replicates packets based on a BitString in the packet header, but every BitPosition of the BitString of a BIER-TE packet indicates one or more adjacencies as described in [RFC9262]. BIER-TE Path can be derived from a Path Computation Element (PCE). 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. The IETF Secretariat