[Pce] Request for WG adoption of draft-li-pce-sr-path-segment-08

"Chengli (Cheng Li)" <chengli13@huawei.com> Mon, 19 August 2019 14:05 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 6B80A12006A; Mon, 19 Aug 2019 07:05:11 -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 jqORkKglvwPx; Mon, 19 Aug 2019 07:05:08 -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 802BF120105; Mon, 19 Aug 2019 07:05:08 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 0058929C7BB2818ED61D; Mon, 19 Aug 2019 15:05:06 +0100 (IST)
Received: from lhreml715-chm.china.huawei.com (10.201.108.66) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 19 Aug 2019 15:05:05 +0100
Received: from lhreml715-chm.china.huawei.com (10.201.108.66) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 19 Aug 2019 15:05:05 +0100
Received: from DGGEML423-HUB.china.huawei.com (10.1.199.40) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Mon, 19 Aug 2019 15:05:05 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.7]) by dggeml423-hub.china.huawei.com ([10.1.199.40]) with mapi id 14.03.0439.000; Mon, 19 Aug 2019 22:04:55 +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-path-segment-08
Thread-Index: AdVWlsx26ZvuiL8vQSO1TJb1TFuV4g==
Date: Mon, 19 Aug 2019 14:04:55 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB02684C0B@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/ICPLaqdUgFcqu6eoILIr62CDIns>
Subject: [Pce] Request for WG adoption of draft-li-pce-sr-path-segment-08
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:05:11 -0000

Hi WG and Chairs,

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

    * add Implementation Status
    * move SRv6 related text to appendix
    * add Security Considerations
    * 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:54 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-path-segment-08.txt


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

Name:		draft-li-pce-sr-path-segment
Revision:	08
Title:		Path Computation Element Communication Protocol (PCEP) Extension for Path Segment in Segment Routing (SR)
Document date:	2019-08-19
Group:		Individual Submission
Pages:		26
URL:            https://www.ietf.org/internet-drafts/draft-li-pce-sr-path-segment-08.txt
Status:         https://datatracker.ietf.org/doc/draft-li-pce-sr-path-segment/
Htmlized:       https://tools.ietf.org/html/draft-li-pce-sr-path-segment-08
Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-pce-sr-path-segment
Diff:           https://www.ietf.org/rfcdiff?url2=draft-li-pce-sr-path-segment-08

Abstract:
   The Path Computation Element (PCE) provides path computation
   functions in support of traffic engineering in Multiprotocol Label
   Switching (MPLS) and Generalized MPLS (GMPLS) networks.

   The Source Packet Routing in Networking (SPRING) architecture
   describes how Segment Routing (SR) can be used to steer packets
   through an IPv6 or MPLS network using the source routing paradigm.  A
   Segment Routed Path can be derived from a variety of mechanisms,
   including an IGP Shortest Path Tree (SPT), explicit configuration, or
   a Path Computation Element (PCE).

   Path identification is needed for several use cases such as
   performance measurement in Segment Routing (SR) network.  This
   document specifies extensions to the Path Computation Element
   Communication Protocol (PCEP) to support requesting, replying,
   reporting and updating the Path Segment ID (Path SID) between PCEP
   speakers.

                                                                                  


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