[Idr] Fw:New Version Notification for draft-lp-idr-sr-path-protection-00.txt
liu.yao71@zte.com.cn Mon, 09 November 2020 03:28 UTC
Return-Path: <liu.yao71@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 9A81C3A1136 for <idr@ietfa.amsl.com>; Sun, 8 Nov 2020 19:28:59 -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_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 JPvYPKrJ32Xi for <idr@ietfa.amsl.com>; Sun, 8 Nov 2020 19:28:55 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 2E3533A1138 for <idr@ietf.org>; Sun, 8 Nov 2020 19:28:55 -0800 (PST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 7CFE1ABC5532419B8415 for <idr@ietf.org>; Mon, 9 Nov 2020 11:28:48 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse-fl2.zte.com.cn with SMTP id 0A93QQr0010751 for <idr@ietf.org>; Mon, 9 Nov 2020 11:26:26 +0800 (GMT-8) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid203; Mon, 9 Nov 2020 11:26:26 +0800 (CST)
Date: Mon, 09 Nov 2020 11:26:26 +0800
X-Zmail-TransId: 2af95fa8b6e2fdf9d948
X-Mailer: Zmail v1.0
Message-ID: <202011091126263167997@zte.com.cn>
References: 160267462160.31341.15130628848407750786@ietfa.amsl.com
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: idr@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 0A93QQr0010751
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/om2evxvPqHggpyx3srxiDeSX1i8>
Subject: [Idr] Fw:New Version Notification for draft-lp-idr-sr-path-protection-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Nov 2020 03:29:00 -0000
Dear WG, We have posted a new draft describing extensions of BGP in order to provide path protection within a candidate path when delivering SR policy. Comments, suggestions and questions are more than welcome. Thanks, Yao 原始邮件 发件人:internet-drafts@ietf.org 收件人:彭少富10053815;刘尧00165286;彭少富10053815; 日 期 :2020年10月14日 19:23 主 题 :New Version Notification for draft-lp-idr-sr-path-protection-00.txt A new version of I-D, draft-lp-idr-sr-path-protection-00.txt has been successfully submitted by Liu Yao and posted to the IETF repository. Name: draft-lp-idr-sr-path-protection Revision: 00 Title: BGP extensions of SR policy for path protection Document date: 2020-10-14 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/archive/id/draft-lp-idr-sr-path-protection-00.txt Status: https://datatracker.ietf.org/doc/draft-lp-idr-sr-path-protection/ Htmlized: https://datatracker.ietf.org/doc/html/draft-lp-idr-sr-path-protection Htmlized: https://tools.ietf.org/html/draft-lp-idr-sr-path-protection-00 Abstract: This document proposes extensions of BGP in order to provide path protection within a candidate path when delivering SR policy. And it also extends BGP-LS to provide some extra information of the segment list in a candidate path in the advertisement. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat