[Pce] Request for WG adoption of draft-li-pce-sr-bidir-path-06.txt

"Chengli (Cheng Li)" <chengli13@huawei.com> Mon, 19 August 2019 14:07 UTC

Return-Path: <chengli13@huawei.com>
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 4C147120045; Mon, 19 Aug 2019 07:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 lMizBKupJIRn; Mon, 19 Aug 2019 07:07:31 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 258E812006A; Mon, 19 Aug 2019 07:07:31 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 834518DD9E3C60365DA1; Mon, 19 Aug 2019 15:07:29 +0100 (IST)
Received: from lhreml704-chm.china.huawei.com (10.201.108.53) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 19 Aug 2019 15:07:29 +0100
Received: from lhreml704-chm.china.huawei.com (10.201.108.53) by lhreml704-chm.china.huawei.com (10.201.108.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 19 Aug 2019 15:07:29 +0100
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml704-chm.china.huawei.com (10.201.108.53) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Mon, 19 Aug 2019 15:07:28 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.7]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0439.000; Mon, 19 Aug 2019 22:07:17 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: "pce@ietf.org" <pce@ietf.org>, pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Request for WG adoption of draft-li-pce-sr-bidir-path-06.txt
Thread-Index: AdVWlyHwGzqQFTruStOvaAwbCF/Eyg==
Date: Mon, 19 Aug 2019 14:07:16 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB02685C1E@dggeml529-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.185.75]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/TjquWvrA1OcCG-VonIK9o_LUAZg>
Subject: [Pce] Request for WG adoption of draft-li-pce-sr-bidir-path-06.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 19 Aug 2019 14:07:34 -0000

Hi WG and Chairs,

We just updated the draft-li-pce-sr-bidir-path.  Major modifications:

    * add Implementation Status
    * move SRv6 related text to appendix
    * add Manageability Considerations

Since the text is mature in this draft, we would like to ask for WG adoption for this draft (Though it has been waiting in WG adoption queue for a while.^-^)

If possible, we would like to request IANA early allocation for helping implementation. 

Comments are welcome! 

Many thanks,
Cheng


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, August 19, 2019 9:51 PM
To: Rakesh Gandhi <rgandhi@cisco.com>; Quan Xiong <xiong.quan@zte.com.cn>; Weiqiang Cheng <chengweiqiang@chinamobile.com>; Mach Chen <mach.chen@huawei.com>; Dongjie (Jimmy) <jie.dong@huawei.com>; Mach Chen <mach.chen@huawei.com>; Chengli (Cheng Li) <chengli13@huawei.com>; Lizhenbin <lizhenbin@huawei.com>
Subject: New Version Notification for draft-li-pce-sr-bidir-path-06.txt


A new version of I-D, draft-li-pce-sr-bidir-path-06.txt has been successfully submitted by Cheng Li and posted to the IETF repository.

Name:		draft-li-pce-sr-bidir-path
Revision:	06
Title:		PCEP Extensions for Associated Bidirectional Segment Routing (SR) Paths
Document date:	2019-08-19
Group:		Individual Submission
Pages:		16
URL:            https://www.ietf.org/internet-drafts/draft-li-pce-sr-bidir-path-06.txt
Status:         https://datatracker.ietf.org/doc/draft-li-pce-sr-bidir-path/
Htmlized:       https://tools.ietf.org/html/draft-li-pce-sr-bidir-path-06
Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-pce-sr-bidir-path
Diff:           https://www.ietf.org/rfcdiff?url2=draft-li-pce-sr-bidir-path-06

Abstract:
   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.
   The Stateful PCE extensions allow stateful control of Multiprotocol
   Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
   (LSPs) using PCEP.  Furthermore, PCEP can be used for computing paths
   in Segment Routing (SR) TE networks.

   This document defines PCEP extensions for grouping two reverse
   unidirectional SR Paths into an Associated Bidirectional SR Path when
   using a Stateful PCE for both PCE-Initiated and PCC-Initiated LSPs as
   well as when using a Stateless PCE.

                                                                                  


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