Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Pengshuping (Peng Shuping)]

Hi Adrian, all, 

We have updated this draft and hoped that we have resolved your comments. Thank 
you! 
https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-extension-pce-controller-srv6-01
 

Here is the diff for your convenience. 
https://author-tools.ietf.org/iddiff?url1=draft-ietf-pce-pcep-extension-pce-controller-srv6-00=draft-ietf-pce-pcep-extension-pce-controller-srv6-01=--html
 

Best Regards,
Shuping 


> -Original Message-
> From: Adrian Farrel [mailto:adr...@olddog.co.uk]
> Sent: Wednesday, January 18, 2023 4:20 AM
> To: pce@ietf.org
> Cc: julien.meu...@orange.com;
> draft-dhody-pce-pcep-extension-pce-controller-s...@ietf.org
> Subject: Re: [Pce] WG Adoption of
> draft-dhody-pce-pcep-extension-pce-controller-srv6
> 
> Hi,
> 
> Tl;dr  I support the adoption of this draft.
> 
> As a co-author of RFC 8283, I take an interest in this work and the wider
> applicability of PCECC. I've also been interested in how SID allocation is
> coordinated, and this seems like a reasonable solution.
> 
> Given that we have procedures and protocol extensions for PCECC with
> SR-MPLS, it seems pragmatic to also have them for SRv6.
> 
> Some comments and nits below, none of which needs to be actioned before
> adoption.
> 
> Best,
> Adrian
> 
> ===
> 
> Abstract
> 
> Suggest a paragraph break before "This document"
> 
> ---
> 
> Abstract
> 
> You nicely introduce PCE and PCECC, but don't introduce SR. There is,
> perhaps, a sentence or two in the Introduction you could borrow...
> 
> 
>Segment Routing (SR) technology leverages the source routing and
>tunneling paradigms.  Each path is specified as a set of "segments"
>encoded in the header of each packet as a list of Segment Identifiers
>(SIDs).
> 
> You'd then tidy up the subsequent text since there is no need to expand the
> abbreviations twice.
> 
> ---
> 
> Abstract
> 
> s/SDN and/SDN/
> s/in the for /in the/
> 
> ---
> 
> 1.
> 
> Although PCEP is expanded in the Abstract, you need to expand it on first use
> in the main body of text.
> 
> ---
> 
> 1.
> 
> s/introduction to SR/introduction to the SR/ a/[RFC8665] ,/[RFC8665],/
> 
> ---
> 
> 1.
> OLD
>[RFC8283] introduces the architecture for PCE as a central controller
> NEW
>[RFC8283] introduces the architecture for PCE as a central controller
>(PCECC)
> END
> 
> ---
> 
> 1.
> 
>It relies on a
>series of forwarding instructions being placed in the header of a
>packet.  The list of segments forming the path is called the Segment
>List and is encoded in the packet header.
> 
> You say "in the packet header" twice.
> 
> ---
> 
> 1.
> 
>PCECC may further use PCEP for SR SID (Segment Identifier) allocation
>and distribution to all the SR nodes with some benefits.
> 
> Hmmm. Not sure PCEP is use for allocation. Maybe it is open for
> interpretation, but possibly...
> 
>The PCECC may perform centralized allocation of SR Segment
>Identifiers (SIDs) and use PCEP to distribute them to the SR nodes.
> 
> ---
> 
> 1.
> 
>[I-D.ietf-pce-pcep-extension-pce-controller-sr] specifies the
>procedures and PCEP extensions when a PCE-based controller is also
>responsible for configuring the forwarding actions on the routers
>(SR-MPLS SID distribution), in addition to computing the paths for
>packet flows in a segment routing network and telling the edge
>routers what instructions to attach to packets as they enter the
>network.  This document extends this to include SRv6 SID distribution
>as well.
> 
> Big question first. I know the history that led us to have one I-D for SR-MPLS
> and one for SRv6. The question is whether we still need to have that, or we
> should adopt this document and them move for a merger so that the is just
> one draft for PCECC-SR. I assume that the philosophy of the PCEP extensions
> are the same, and that it is just the encoding of SIDs that differs. (See also
> the end of Section 3.)
> 
> And then, a rewrite for clarity...
> 
>A PCE-based central controller may be responsible for computing the
>paths for packet flows in an MPLS Segment Routing (SR-MPLS) network
>and for telling the edge routers what instructions to attach to
>packets as they enter the network.  [I-D.ietf-pce-pcep-extension-pce-
>controller-sr] specifies the procedures and PCEP extensions when a
>PCE-based controller is additionally responsible for configuring the
>forwarding actions on routers in an SR-MPLS network (i.e., for SR-
>MPLS SID distribution).  This document extends those pro

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[julien.meuric]

Hi all,

We have a decent level of support and no voice against. Consequently, 
let's adopt this I-D as a new PCE work item.


Thanks,

Julien


On 16/01/2023 19:00, julien.meu...@orange.com wrote:

Hi all,

This e-mail starts an adoption poll for 
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you 
consider this I-D is ready to become a PCE WG item?


Please respond to the PCE list, including rationale if you believe the 
WG should not adopt it.


Thanks,

Julien


[1] 
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/




smime.p7s
Description: S/MIME Cryptographic Signature
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Lizhenbin]

Hi All,
I support the adoption of the draft as the co-author.

Best Regards,
Zhenbin (Robin)





李振斌 Li Zhenbin
Mobile: +86-13651017745/+968-91797068
Email: lizhen...@huawei.com

发件人：julien.meuric 
收件人：pce 
时 间：2023-01-17 02:02:13
主 题：[Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
consider this I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the
WG should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/


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

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Huaimo Chen]

Hi Everyone,

I read the draft and support its adoption.

Best Regards,
Huaimo

From: Pce  on behalf of Gyan Mishra 

Sent: Thursday, February 2, 2023 9:21 PM
To: julien.meu...@orange.com 
Cc: pce@ietf.org 
Subject: Re: [Pce] WG Adoption of 
draft-dhody-pce-pcep-extension-pce-controller-srv6

I support WG adoption of PCEP PCECC centralized controller extension for SRv6.

Thanks

Gyan

On Mon, Jan 16, 2023 at 1:00 PM 
mailto:julien.meu...@orange.com>> wrote:
Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
consider this I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the
WG should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-dhody-pce-pcep-extension-pce-controller-srv6%2F=05%7C01%7Chuaimo.chen%40futurewei.com%7Ccf65ca388bf74c71d35b08db058d713a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109877301915044%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=XTPgZdQZBoE%2FEzF17PvFIOAsDpequGEA7IgJ9W8sMww%3D=0>


___
Pce mailing list
Pce@ietf.org<mailto:Pce@ietf.org>
https://www.ietf.org/mailman/listinfo/pce<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fpce=05%7C01%7Chuaimo.chen%40futurewei.com%7Ccf65ca388bf74c71d35b08db058d713a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109877301915044%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=yl4BN0nPwmr9rUP3sWyY4URjLO%2BAgmpzbl%2BuNne0eOk%3D=0>
--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F=05%7C01%7Chuaimo.chen%40futurewei.com%7Ccf65ca388bf74c71d35b08db058d713a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109877301915044%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rwfAmOxtTUyfvR6XmgVVq993TJjfsUKMFf%2Fy5JXZfmA%3D=0>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>

M 301 502-1347


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

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Gyan Mishra]

I support WG adoption of PCEP PCECC centralized controller extension for
SRv6.

Thanks

Gyan

On Mon, Jan 16, 2023 at 1:00 PM  wrote:

> Hi all,
>
> This e-mail starts an adoption poll for
> draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
> consider this I-D is ready to become a PCE WG item?
>
> Please respond to the PCE list, including rationale if you believe the
> WG should not adopt it.
>
> Thanks,
>
> Julien
>
>
> [1]
>
> https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/
>
>
> ___
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
-- 



*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mis...@verizon.com *



*M 301 502-1347*
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Zhoulei]

Hi Pce WG,

From my perspective, support adoption of the following draft as PCE WG item.

It is good for WG to consider the PCECC solution for Segment Routing over IPv6 
(SRv6) Segment
Identifier (SID) Allocation and Distribution.

BR
Lei Zhou

-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of julien.meu...@orange.com
Sent: Tuesday, January 17, 2023 2:00 AM
To: pce@ietf.org
Subject: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you consider this 
I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the WG 
should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/


-
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from New H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email immediately and delete it!
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Chengli]

Same here. Finally, we get this important work here for adopting. I support the 
adoption.

Thanks,
Cheng


From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of Boris Khasanov
Sent: Wednesday, January 25, 2023 4:37 AM
To: julien.meu...@orange.com<mailto:julien.meu...@orange.com>; 
pce@ietf.org<mailto:pce@ietf.org>
Subject: Re: [Pce] WG Adoption of 
draft-dhody-pce-pcep-extension-pce-controller-srv6

Hi Julien and all,

Support this work as the very important part of overall PCECC architecture  as 
well as SRv6 development.

SY,
Boris

16.01.2023, 21:00, "julien.meu...@orange.com<mailto:julien.meu...@orange.com>" 
mailto:julien.meu...@orange.com>>:

Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
consider this I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the
WG should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/
,

___
Pce mailing list
Pce@ietf.org<mailto:Pce@ietf.org>
https://www.ietf.org/mailman/listinfo/pce
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[??????????????????????-????]

Hi All,

I’ve read this document and think it is useful , thus I support its adoption.

Best regards,
Pang Ran.

From: julien.meu...@orange.com<mailto:julien.meu...@orange.com>
Date: 2023-01-17 02:00
To: pce@ietf.org<mailto:pce@ietf.org>
Subject: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6
Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
consider this I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the
WG should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/


如果您错误接收了该邮件，请通过电子邮件立即通知我们。请回复邮件到 
hqs-s...@chinaunicom.cn，即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received 
this email in error please notify us immediately by e-mail. Please reply to 
hqs-s...@chinaunicom.cn ,you can unsubscribe from this mail. We will 
immediately remove your information from send catalogue of our.
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[wangmin...@chinamobile.com]

Hi Julien and WG,

Yes,  it is actually for the adoption of 
draft-dhody-pce-pcep-extension-pce-controller-srv6.   Sorry for intrude into 
the other thread. :)


16.01.2023, 21:00, "julien.meu...@orange.com" :
Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
consider this I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the
WG should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/
,
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


-
王敏学/ Wang Minxue
中国移动通信研究院 基础网络技术研究所 / China Mobile Research Institute
地址: 北京市西城区宣武门西大街32号创新大厦,100053
电话: 010-15801696688-33202
传真：010-63601087
Email: wangmin...@chinamobile.com
-
 
From: julien.meu...@orange.com
Date: 2023-01-24 22:25
To: wangmin...@chinamobile.com
CC: pce@ietf.org
Subject: Re: [Pce] Scoping Items from draft-koldychev-pce-operational
Hi Minxue,

For the record, we guess you intended to respond to the thread about the 
adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6. :-)

Thanks,

Dhruv & Julien


On 24/01/2023 03:27, wangmin...@chinamobile.com wrote:
Hi Chair and WG,

 I support the adopting of this work. This document seems a reasonable solution 
for SRv6 computing and allocation with PCE based control.


-
王敏学/ Wang Minxue
中国移动通信研究院 基础网络技术研究所 / China Mobile Research Institute
地址: 北京市西城区宣武门西大街32号创新大厦,100053
电话: 010-15801696688-33202
传真：010-63601087
Email: wangmin...@chinamobile.com
-
 
From: julien.meu...@orange.com
Date: 2023-01-17 00:57
To: pce@ietf.org
Subject: Re: [Pce] Scoping Items from draft-koldychev-pce-operational
Dear PCE WG,
 
This issue has been opened for while. Thank you to those who took time 
to share their views.
 
We acknowledge that having a single document may be likely to reduce the 
initial paperwork (at least until the I-D starts to be reviewed by 
people outside the PCE WG). However, as stated by Adrian, the line 
between updates and clarifications "must not be blurry", all the more as 
the standard track piece of work may update some RFCs. This must be true 
both for us, as a WG, and for future reader of the documents, especially 
if they are not familiar with IETF way of working when it comes to 
multi-status document content.
 
As a result, let's follow John's guidelines, voiced during the London 
meeting, and split the I-D into 2 documents with focused status. 
Starting from there, we'll be able to move forward.
 
Thank you,
 
Dhruv & Julien
 
 
On 29/09/2022 10:37, julien.meu...@orange.com wrote:
> Dear PCE WG,
>
> Let's follow up on the discussion started during IETF 114 about 
> draft-koldychev-pce-operational [1]. The I-D currently tackles 
> different issues about PCEP, some of them being informational, some 
> other updating existing PCEP specifications. Among the options we 
> discussed to proceed with this work, 2 remain:
> 1. Keep a single draft, but clearly separate the two types of content;
> 2. Break it up into 2 drafts.
>
> We'd like to hear the WG's opinion whether you prefer:
> a- a single standard track I-D, with both content types sharing fate 
> until publication?
> b- a clarification I-D on informational track + an I-D updating PCEP 
> on standard track (possibly progressing at different paces)?
>
> Please share your feedback using the PCE mailing list.
>
> Thanks,
>
> Dhruv & Julien
>
>
> [1] https://datatracker.ietf.org/doc/draft-koldychev-pce-operational/
>
>
>
> ___
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
 
 
 
 
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

_
Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.
This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Boris Khasanov]

Hi Julien and all, Support this work as the very important part of overall PCECC architecture  as well as SRv6 development. SY,Boris 16.01.2023, 21:00, "julien.meu...@orange.com" :Hi all,This e-mail starts an adoption poll fordraft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do youconsider this I-D is ready to become a PCE WG item?Please respond to the PCE list, including rationale if you believe theWG should not adopt it.Thanks,Julien[1]https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/,___Pce mailing listPce@ietf.orghttps://www.ietf.org/mailman/listinfo/pce___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Stefano Previdi]

Hi, 

I support the adoption of this draft since it's part of the whole SRv6 work.

Thanks.
s.

> -Original Message-
> From: Pce  <mailto:pce-boun...@ietf.org;> On 
> Behalf Of julien.meu...@orange.com <mailto:julien.meu...@orange.com>
> Sent: 16 January 2023 18:00
> To: pce@ietf.org <mailto:pce@ietf.org>
> Subject: [Pce] WG Adoption of 
> draft-dhody-pce-pcep-extension-pce-controller-srv6
> 
> Hi all,
> 
> This e-mail starts an adoption poll for 
> draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you 
> consider this I-D is ready to become a PCE WG item?
> 
> Please respond to the PCE list, including rationale if you believe the 
> WG should not adopt it.
> 
> Thanks,
> 
> Julien

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

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Adrian Farrel]

| TBD1 | SR-MPLS (S-bit) | This document |

---

7.3

   If the sum of
   all four sizes advertised in the SID Structure is larger than 128
   bits, the corresponding SRv6 SID MUST be considered invalid and a
   PCErr message with Error-Type = 10 ("Reception of an invalid object")
   and Error-Value = TBD ("Invalid SRv6 SID Structure") is returned.

draft-ietf-pce-segment-routing-ipv6 has already assigned the value 37.
Further, I think you need to make it clear that the behavior you are
describing is already specified elsewhere. So...

NEW
   According to [I-D.ietf-pce-segment-routing-ipv6], if the sum of
   all four sizes advertised in the SID Structure is larger than 128
   bits, the corresponding SRv6 SID is considered invalid and a
   PCErr message with Error-Type = 10 ("Reception of an invalid object")
   and Error-Value = 37 ("Invalid SRv6 SID Structure") is returned.
END

---

8.

You reference RFC 7525, but that was obsoleted by RFC 9325.

I suspect that all you need to do is make an update to the new
reference.

---

9.5

I think I agree with what you have written, but I wonder what happens
if PCECC is used per this document at the same time that IGP-based
mechanisms are used. Is there a conflict? How is that resolved? Does
management play a part?

---

10.2

The CCI Object Type value has been assigned (see RFC 9050). You can 
replace "TBD" with "44".

---

Through-out...

It *might* be worth renumbering the TBDs to take care of the fact that
there is no TBD2.

-Original Message-
From: Pce  On Behalf Of julien.meu...@orange.com
Sent: 16 January 2023 18:00
To: pce@ietf.org
Subject: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

Hi all,

This e-mail starts an adoption poll for 
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you 
consider this I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the 
WG should not adopt it.

Thanks,

Julien


[1] 
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/



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

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[zhenlin....@hotmail.com]

Hi Chair and WG,

This is zhenlin Tan from China Telecom.  I support the WG adoption of this 
work. This document specifies useful procedures and PCEP extensions when a 
PCE-based controller is also responsible for computing the paths in the SRv6 
network.



Zhenlin Tan  
China Telecom Research Institute,Guangzhou,China
Work Email: tan...@chinatelecom.cn
Mobile: (86)15603005002
 
From: julien.meu...@orange.com
Date: 2023-01-17 02:00
To: pce@ietf.org
Subject: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6
Hi all,
 
This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
consider this I-D is ready to become a PCE WG item?
 
Please respond to the PCE list, including rationale if you believe the
WG should not adopt it.
 
Thanks,
 
Julien
 
 
[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/
 
 
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Gengxuesong (Geng Xuesong)]

Hi Julien and WG,

This document specifies PCEP extension for SRv6 with PCECC.
Support WG adoption as co-author.

Best
Xuesong

> -Original Message-
> From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of
> julien.meu...@orange.com
> Sent: Tuesday, January 17, 2023 2:00 AM
> To: pce@ietf.org
> Subject: [Pce] WG Adoption of
> draft-dhody-pce-pcep-extension-pce-controller-srv6
> 
> Hi all,
> 
> This e-mail starts an adoption poll for
> draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you consider 
> this
> I-D is ready to become a PCE WG item?
> 
> Please respond to the PCE list, including rationale if you believe the WG 
> should
> not adopt it.
> 
> Thanks,
> 
> Julien
> 
> 
> [1]
> https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller
> -srv6/
> 

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

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Liang Felix]

Dear Chairs

How are you doing?

This is Felix from China Telecom.

From my own perspective, I think this document has specified useful procedures 
and PCEP extensions when a PCE-based controller is also responsible for 
computing the explicit forwarding paths in the SRv6 network.
So I support the WG adoption of this work.


___ 
Best Regards! 
梁筱斌 Felix Liang 
IP Network Architect 

Network Technology Research Dept, Research Institute of China Telecom Co., Ltd 
109 West Zhongshan Avenue, Tianhe District, Guangzhou 510630, CN 
O: +86 20 3863 9179 
C: +86 189 2956 4809 
F: +86 20 3863 9572 

Email: liang...@chinatelecom.cn , 
felix.liang.1...@hotmail.com  





On 1/17/23, 02:00, "Pce on behalf of julien.meu...@orange.com 
" mailto:pce-boun...@ietf.org> on behalf of julien.meu...@orange.com 
> wrote:


Hi all,


This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you
consider this I-D is ready to become a PCE WG item?


Please respond to the PCE list, including rationale if you believe the
WG should not adopt it.


Thanks,


Julien




[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/
 








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

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Tanren]

Hi all,

I have read the document and find PCECC for SRv6 is useful. I support the WG 
adoption of the document.

Tan

-邮件原件-
发件人: Pce [mailto:pce-boun...@ietf.org] 代表 julien.meu...@orange.com
发送时间: 2023年1月17日 2:00
收件人: pce@ietf.org
主题: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you consider this 
I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the WG 
should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/


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

Re: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[Pengshuping (Peng Shuping)]

Hi, 

Thanks to the Chairs for starting this call. 

This draft has been updated according to the feedback collected through email 
exchanges and presentations. 

As a co-author of this work, I support the WG adoption of it. 

Thank you! 

Best Regards, 
Shuping 


-Original Message-
From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of julien.meu...@orange.com
Sent: Tuesday, January 17, 2023 2:00 AM
To: pce@ietf.org
Subject: [Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

Hi all,

This e-mail starts an adoption poll for
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you consider this 
I-D is ready to become a PCE WG item?

Please respond to the PCE list, including rationale if you believe the WG 
should not adopt it.

Thanks,

Julien


[1]
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/


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

[Pce] WG Adoption of draft-dhody-pce-pcep-extension-pce-controller-srv6

[julien.meuric]

Hi all,

This e-mail starts an adoption poll for 
draft-dhody-pce-pcep-extension-pce-controller-srv6-10 [1]. Do you 
consider this I-D is ready to become a PCE WG item?


Please respond to the PCE list, including rationale if you believe the 
WG should not adopt it.


Thanks,

Julien


[1] 
https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/





smime.p7s
Description: S/MIME Cryptographic Signature
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce