Re: [Pce] New Version Notification for draft-ietf-pce-segment-routing-ipv6-17.txt

Cheng Li <c.l@huawei.com> Wed, 28 June 2023 02:50 UTC

Return-Path: <c.l@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 3DE2CC15106F for <pce@ietfa.amsl.com>; Tue, 27 Jun 2023 19:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 5TYeDpJZ3Xhr for <pce@ietfa.amsl.com>; Tue, 27 Jun 2023 19:50:09 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8AAC14CE5E for <pce@ietf.org>; Tue, 27 Jun 2023 19:50:08 -0700 (PDT)
Received: from lhrpeml500002.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4QrQw91h6tz67GCV for <pce@ietf.org>; Wed, 28 Jun 2023 10:47:05 +0800 (CST)
Received: from canpemm100007.china.huawei.com (7.192.105.181) by lhrpeml500002.china.huawei.com (7.191.160.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Wed, 28 Jun 2023 03:50:00 +0100
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by canpemm100007.china.huawei.com (7.192.105.181) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Wed, 28 Jun 2023 10:49:58 +0800
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2507.027; Wed, 28 Jun 2023 10:49:57 +0800
From: Cheng Li <c.l@huawei.com>
To: Cheng Li <c.l=40huawei.com@dmarc.ietf.org>, "pce@ietf.org" <pce@ietf.org>, Mahendra Negi <mahend.ietf@gmail.com>, Mahendra Singh Negi <mahend.ietf@gmail.com>, Mike Koldychev <mkoldych@cisco.com>, Prejeeth Kaladharan <prejeeth@rtbrick.com>, Siva Sivabalan <msiva282@gmail.com>, Yongqing Zhu <zhuyq8@chinatelecom.cn>, Ketan Talaulikar <ketant.ietf@gmail.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "yingzhen.ietf@gmail.com" <yingzhen.ietf@gmail.com>, "chen.ran@zte.com.cn" <chen.ran@zte.com.cn>
Thread-Topic: New Version Notification for draft-ietf-pce-segment-routing-ipv6-17.txt
Thread-Index: AQHZqWhZ/8Lc0yNwNUKN1+I9ZuaDiK+ffpWQgAAENjA=
Date: Wed, 28 Jun 2023 02:49:57 +0000
Message-ID: <e520c5eab3474d83a17b40d254d8a229@huawei.com>
References: <168791934036.16054.13801100118111170751@ietfa.amsl.com> <fd30d55d778b4c10a8b9bc5fb966da87@huawei.com>
In-Reply-To: <fd30d55d778b4c10a8b9bc5fb966da87@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.50.76.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/1Je5oKqII2rpsTKNLhC4CZ44KVE>
Subject: Re: [Pce] New Version Notification for draft-ietf-pce-segment-routing-ipv6-17.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: Wed, 28 Jun 2023 02:50:10 -0000

Hi PCE,
(The previous email was sent too fast, fixed some syntax errors and resend)

This update addressed the comments from Adrian, Ran Chen and Yingzhen. Many thanks to their valuable comments[1], please review and confirm, thanks!
This update also tries to address the comments from Ketan. We believe that we have addressed the editorial comments from Ketan[1]. 

Till now, we may have two reserved comments to be addressed:
1. IANA allocation of SRv6-ERO(From Adrian): Should we create a new registry for SR/SRv6?  or allocate them from the RSVP parameters registry? Comments are welcome.
2. X-flag(From Ketan): is the X-flag needed? If not, why? if we decide to delete it, we need to know from the WG that if anyone has implemented it, and how can we handle the compatibility problem.

Comments and feedbacks are appreciated.

Respect,
Cheng


[1]. https://github.com/muzixing/IETF-PCEP-SRV6/issues

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of Cheng Li
Sent: Wednesday, June 28, 2023 10:42 AM
To: pce@ietf.org; Mahendra Negi <mahend.ietf@gmail.com>; Mahendra Singh Negi <mahend.ietf@gmail.com>; Mike Koldychev <mkoldych@cisco.com>; Prejeeth Kaladharan <prejeeth@rtbrick.com>; Siva Sivabalan <msiva282@gmail.com>; Yongqing Zhu <zhuyq8@chinatelecom.cn>; Ketan Talaulikar <ketant.ietf@gmail.com>; adrian@olddog.co.uk; yingzhen.ietf@gmail.com; chen.ran@zte.com.cn
Subject: Re: [Pce] New Version Notification for draft-ietf-pce-segment-routing-ipv6-17.txt

Hi PCE,

This update addressed the comments from Adrian, Ran Chen and Yingzhen. Many thanks to their valuable comments[1], please review and confirm, thanks!
This update also try to address the comments from Ketan. We believe that we have addressed the editorial from Ketan[1]. 

Till now, we may have two reserved comments to be addressed:

1. IANA allocation of SRv6-ERO(From Adrian): Should we create a new registry for SR/SRv6 or allocate in from the RSVP parameters registry? Comments are welcome.
2. X-flag(From Ketan): is the X-flag needed? If not, why? if we decide to delete it, we need to know from the WG that if anyone has implemented it, and how can we handle the compatibility problem.

Comments and feedback are appreciated.

Respect,
Cheng


[1]. https://github.com/muzixing/IETF-PCEP-SRV6/issues


-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: Wednesday, June 28, 2023 10:29 AM
To: Cheng Li <c.l@huawei.com>; Cheng Li <c.l@huawei.com>; Mahendra Negi <mahend.ietf@gmail.com>; Mahendra Singh Negi <mahend.ietf@gmail.com>; Mike Koldychev <mkoldych@cisco.com>; Prejeeth Kaladharan <prejeeth@rtbrick.com>; Siva Sivabalan <msiva282@gmail.com>; Yongqing Zhu <zhuyq8@chinatelecom.cn>
Subject: New Version Notification for draft-ietf-pce-segment-routing-ipv6-17.txt


A new version of I-D, draft-ietf-pce-segment-routing-ipv6-17.txt
has been successfully submitted by Cheng Li(Editor) and posted to the IETF repository.

Name:		draft-ietf-pce-segment-routing-ipv6
Revision:	17
Title:		Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing leveraging the IPv6 dataplane
Document date:	2023-06-28
Group:		pce
Pages:		26
URL:            https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-ipv6-17.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing-ipv6/
Html:           https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-ipv6-17.html
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-ipv6
Diff:           https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-segment-routing-ipv6-17

Abstract:
   Segment Routing (SR) can be used to steer packets through an IPv6 or
   MPLS network using the source routing paradigm.  SR enables any head-
   end node to select any path without relying on a hop-by-hop signaling
   technique (e.g., LDP or RSVP-TE).

   A Segment Routed Path can be derived from a variety of mechanisms,
   including an IGP Shortest Path Tree (SPT), explicit configuration, or
   a PCE.

   Since SR can be applied to both MPLS and IPv6 forwarding planes, a
   PCE should be able to compute SR-Path for both MPLS and IPv6
   forwarding planes.  The PCEP extension and mechanisms to support SR-
   MPLS have been defined.  This document describes the extensions
   required for SR support for IPv6 data plane in the Path Computation
   Element communication Protocol(PCEP).

                                                                                  


The IETF Secretariat



_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce