Re: [Pce] RV: New Version Notification for draft-contreras-pce-pam-02.txt

[LUIS MIGUEL CONTRERAS MURILLO]

Thanks Dhruv!

Noted, we will continue with the analysis, my expectation is to report the 
progress at IETF 119 so I can provide more info about the analysis

Thanks again,

Luis

De: Dhruv Dhody 
Enviado el: martes, 27 de febrero de 2024 6:17
Para: LUIS MIGUEL CONTRERAS MURILLO 
CC: Dhruv Dhody ; pce@ietf.org
Asunto: Re: [Pce] RV: New Version Notification for 
draft-contreras-pce-pam-02.txt

Hi Luis,

On Mon, Feb 26, 2024 at 11:59 PM LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
 wrote:
Hi Dhruv,

Sorry for my late response.

In version -01 we proposed a new METRIC Object-type within the existing 
object-class, but after internal analysis we decided to propose a new object in 
this version -02. We think is much cleaner approach and allows to re-use 
attributes already defined. Probably easier as well to parse and facilitate 
backward compatibility with existing implementations.


I am not sure I agree that the approach is much cleaner, but those can be 
subjective. Just looking at the number of PCEP objects that have different 
object-types at https://www.iana.org/assignments/pcep/pcep.xhtml#pcep-objects , 
it feels this is the established practice for PCEP extensions and 
implementations already does the encoding/decoding for lot of PCEP objects.

Regarding the potential impacts in terms of RBNF grammar. Do you have any 
pointer or clue for better understanding such kind of impacts on the Routing 
Backus-Naur Form?


The impact is just that you need to update the RBNF for every PCEP message that 
can carry this new object whereas in case of using an existing object you
just get it for free :)

An example can be seen at recent objects added CCI, BU in RFC9050 and RFC8233 
respectively.

Thanks!
Dhruv


Thanks in advance,

Best regards

Luis

De: Dhruv Dhody mailto:d...@dhruvdhody.com>>
Enviado el: miércoles, 14 de febrero de 2024 5:42
Para: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
CC: pce@ietf.org
Asunto: Re: [Pce] RV: New Version Notification for 
draft-contreras-pce-pam-02.txt

H Luis, WG,

Did you consider defining a new METRIC Object-type (within the existing 
object-class 6) called Precision instead of defining a brand new object with 
new object-class/object-type?

If we choose to define just a new object-type, it has an added advantage of 
keeping the RBNF grammar cleaner and we dont need to extend it.

Thoughts?

Thanks!
Dhruv

On Wed, Feb 14, 2024 at 12:57 AM LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
 wrote:
Dear all,

We have just updated draft-contreras-pce-pam in the following way:

- we have changed the approach moving from extending existing METRIC object to 
proposing a new PRECISION METRIC object. The reason for that is we consider it 
as a cleaner approach, also allowing clearer structure.

- we have also addressed the question raised by Dhruv (as chair) at IETF 118 
about the convenience of including some example.

- editorial clean-up.

With this we think all the comments in IETF 118 have been addressed.

Any further comment / suggestion is more than welcome.

Best regards

Luis



-Mensaje original-
De: internet-dra...@ietf.org 
mailto:internet-dra...@ietf.org>>
Enviado el: martes, 13 de febrero de 2024 20:22
Para: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>;
 Fernando Agraz mailto:fernando.ag...@upc.edu>>; LUIS 
MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>;
 salvatore.spadaro mailto:salvatore.spad...@upc.edu>>
Asunto: New Version Notification for draft-contreras-pce-pam-02.txt

A new version of Internet-Draft draft-contreras-pce-pam-02.txt has been 
successfully submitted by Luis M. Contreras and posted to the IETF repository.

Name: draft-contreras-pce-pam
Revision: 02
Title:Path Computation Based on Precision Availability Metrics
Date: 2024-02-13
Group:Individual Submission
Pages:14
URL:  https://www.ietf.org/archive/id/draft-contreras-pce-pam-02.txt
Status:   https://datatracker.ietf.org/doc/draft-contreras-pce-pam/
HTMLized: https://datatracker.ietf.org/doc/html/draft-contreras-pce-pam
Diff: https://author-tools.ietf.org/iddiff?url2=draft-contreras-pce-pam-02

Abstract:

   The Path Computation Element (PCE) is able of determining paths
   according to constraints expressed in the form of metrics.  The value
   of the metric can be signaled as a bound or maximum, meaning that
   path metric must be less than or equal such value.  While this can be
   sufficient for certain services, some others can require the
   utilization of Precision Availability Metrics (PAM).  This document
   defines a new object, namely the PRECISION METRIC object, to be used
   for path calculation or selection for networking services with
   performance requirements expressed as Service Level Objectives (SLO)
   using PAM.



T

Re: [Pce] RV: New Version Notification for draft-contreras-pce-pam-02.txt

[Dhruv Dhody]

Hi Luis,

On Mon, Feb 26, 2024 at 11:59 PM LUIS MIGUEL CONTRERAS MURILLO <
luismiguel.contrerasmuri...@telefonica.com> wrote:

> Hi Dhruv,
>
>
>
> Sorry for my late response.
>
>
>
> In version -01 we proposed a new METRIC Object-type within the existing
> object-class, but after internal analysis we decided to propose a new
> object in this version -02. We think is much cleaner approach and allows to
> re-use attributes already defined. Probably easier as well to parse and
> facilitate backward compatibility with existing implementations.
>
>
>

I am not sure I agree that the approach is much cleaner, but those can be
subjective. Just looking at the number of PCEP objects that have different
object-types at
https://www.iana.org/assignments/pcep/pcep.xhtml#pcep-objects , it feels
this is the established practice for PCEP extensions and implementations
already does the encoding/decoding for lot of PCEP objects.


> Regarding the potential impacts in terms of RBNF grammar. Do you have any
> pointer or clue for better understanding such kind of impacts on the
> Routing Backus-Naur Form?
>
>
>

The impact is just that you need to update the RBNF for every PCEP message
that can carry this new object whereas in case of using an existing object
you
just get it for free :)

An example can be seen at recent objects added CCI, BU in RFC9050 and
RFC8233 respectively.

Thanks!
Dhruv



> Thanks in advance,
>
>
>
> Best regards
>
>
>
> Luis
>
>
>
> *De:* Dhruv Dhody 
> *Enviado el:* miércoles, 14 de febrero de 2024 5:42
> *Para:* LUIS MIGUEL CONTRERAS MURILLO <
> luismiguel.contrerasmuri...@telefonica.com>
> *CC:* pce@ietf.org
> *Asunto:* Re: [Pce] RV: New Version Notification for
> draft-contreras-pce-pam-02.txt
>
>
>
> H Luis, WG,
>
>
>
> Did you consider defining a new METRIC Object-type (within the existing
> object-class 6) called Precision instead of defining a brand new object
> with new object-class/object-type?
>
>
>
> If we choose to define just a new object-type, it has an added advantage
> of keeping the RBNF grammar cleaner and we dont need to extend it.
>
>
>
> Thoughts?
>
>
>
> Thanks!
>
> Dhruv
>
>
>
> On Wed, Feb 14, 2024 at 12:57 AM LUIS MIGUEL CONTRERAS MURILLO <
> luismiguel.contrerasmuri...@telefonica.com> wrote:
>
> Dear all,
>
> We have just updated draft-contreras-pce-pam in the following way:
>
> - we have changed the approach moving from extending existing METRIC
> object to proposing a new PRECISION METRIC object. The reason for that is
> we consider it as a cleaner approach, also allowing clearer structure.
>
> - we have also addressed the question raised by Dhruv (as chair) at IETF
> 118 about the convenience of including some example.
>
> - editorial clean-up.
>
> With this we think all the comments in IETF 118 have been addressed.
>
> Any further comment / suggestion is more than welcome.
>
> Best regards
>
> Luis
>
>
>
> -Mensaje original-
> De: internet-dra...@ietf.org 
> Enviado el: martes, 13 de febrero de 2024 20:22
> Para: LUIS MIGUEL CONTRERAS MURILLO <
> luismiguel.contrerasmuri...@telefonica.com>; Fernando Agraz <
> fernando.ag...@upc.edu>; LUIS MIGUEL CONTRERAS MURILLO <
> luismiguel.contrerasmuri...@telefonica.com>; salvatore.spadaro <
> salvatore.spad...@upc.edu>
> Asunto: New Version Notification for draft-contreras-pce-pam-02.txt
>
> A new version of Internet-Draft draft-contreras-pce-pam-02.txt has been
> successfully submitted by Luis M. Contreras and posted to the IETF
> repository.
>
> Name: draft-contreras-pce-pam
> Revision: 02
> Title:Path Computation Based on Precision Availability Metrics
> Date: 2024-02-13
> Group:Individual Submission
> Pages:14
> URL:  https://www.ietf.org/archive/id/draft-contreras-pce-pam-02.txt
> Status:   https://datatracker.ietf.org/doc/draft-contreras-pce-pam/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-contreras-pce-pam
> Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-contreras-pce-pam-02
>
> Abstract:
>
>The Path Computation Element (PCE) is able of determining paths
>according to constraints expressed in the form of metrics.  The value
>of the metric can be signaled as a bound or maximum, meaning that
>path metric must be less than or equal such value.  While this can be
>sufficient for certain services, some others can require the
>utilization of Precision Availability Metrics (PAM).  This document
>defines a new object, namely the PRECISION METRIC object, to be used
>for path calculation or selection for networking services with
>performance requirements expressed as Service Level Objectives (SLO)
>using PAM.
>
>
>
> The IETF Secretariat
>
>
>
> 
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lect

Re: [Pce] RV: New Version Notification for draft-contreras-pce-pam-02.txt

[LUIS MIGUEL CONTRERAS MURILLO]

Hi Dhruv,

Sorry for my late response.

In version -01 we proposed a new METRIC Object-type within the existing 
object-class, but after internal analysis we decided to propose a new object in 
this version -02. We think is much cleaner approach and allows to re-use 
attributes already defined. Probably easier as well to parse and facilitate 
backward compatibility with existing implementations.

Regarding the potential impacts in terms of RBNF grammar. Do you have any 
pointer or clue for better understanding such kind of impacts on the Routing 
Backus-Naur Form?

Thanks in advance,

Best regards

Luis

De: Dhruv Dhody 
Enviado el: miércoles, 14 de febrero de 2024 5:42
Para: LUIS MIGUEL CONTRERAS MURILLO 
CC: pce@ietf.org
Asunto: Re: [Pce] RV: New Version Notification for 
draft-contreras-pce-pam-02.txt

H Luis, WG,

Did you consider defining a new METRIC Object-type (within the existing 
object-class 6) called Precision instead of defining a brand new object with 
new object-class/object-type?

If we choose to define just a new object-type, it has an added advantage of 
keeping the RBNF grammar cleaner and we dont need to extend it.

Thoughts?

Thanks!
Dhruv

On Wed, Feb 14, 2024 at 12:57 AM LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
 wrote:
Dear all,

We have just updated draft-contreras-pce-pam in the following way:

- we have changed the approach moving from extending existing METRIC object to 
proposing a new PRECISION METRIC object. The reason for that is we consider it 
as a cleaner approach, also allowing clearer structure.

- we have also addressed the question raised by Dhruv (as chair) at IETF 118 
about the convenience of including some example.

- editorial clean-up.

With this we think all the comments in IETF 118 have been addressed.

Any further comment / suggestion is more than welcome.

Best regards

Luis



-Mensaje original-
De: internet-dra...@ietf.org 
mailto:internet-dra...@ietf.org>>
Enviado el: martes, 13 de febrero de 2024 20:22
Para: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>;
 Fernando Agraz mailto:fernando.ag...@upc.edu>>; LUIS 
MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>;
 salvatore.spadaro mailto:salvatore.spad...@upc.edu>>
Asunto: New Version Notification for draft-contreras-pce-pam-02.txt

A new version of Internet-Draft draft-contreras-pce-pam-02.txt has been 
successfully submitted by Luis M. Contreras and posted to the IETF repository.

Name: draft-contreras-pce-pam
Revision: 02
Title:Path Computation Based on Precision Availability Metrics
Date: 2024-02-13
Group:Individual Submission
Pages:14
URL:  https://www.ietf.org/archive/id/draft-contreras-pce-pam-02.txt
Status:   https://datatracker.ietf.org/doc/draft-contreras-pce-pam/
HTMLized: https://datatracker.ietf.org/doc/html/draft-contreras-pce-pam
Diff: https://author-tools.ietf.org/iddiff?url2=draft-contreras-pce-pam-02

Abstract:

   The Path Computation Element (PCE) is able of determining paths
   according to constraints expressed in the form of metrics.  The value
   of the metric can be signaled as a bound or maximum, meaning that
   path metric must be less than or equal such value.  While this can be
   sufficient for certain services, some others can require the
   utilization of Precision Availability Metrics (PAM).  This document
   defines a new object, namely the PRECISION METRIC object, to be used
   for path calculation or selection for networking services with
   performance requirements expressed as Service Level Objectives (SLO)
   using PAM.



The IETF Secretariat





Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede 
contener información privilegiada o confidencial y es para uso exclusivo de la 
persona o entidad de destino. Si no es usted. el destinatario indicado, queda 
notificado de que la lectura, utilización, divulgación y/o copia sin 
autorización puede estar prohibida en virtud de la legislación vigente. Si ha 
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente 
por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged 
information intended only for the use of the individual or entity named above. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this transmission in error, do not 
read it. Please immediately reply to the sender that you have received this 
communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode 
conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa 
ou entidade de destino. Se não é vossa senhor

Re: [Pce] IPR poll for draft-ietf-pce-stateful-pce-optional

[slitkows.ietf]

Hi,

 

I’m not aware about any IPR related to this document

 

 

From: Andrew Stone (Nokia)  
Sent: Wednesday, February 21, 2024 6:56 PM
To: pce@ietf.org; pce-cha...@ietf.org; Cheng Li ; zhenghaomian 
; slitkows.i...@gmail.com
Subject: IPR poll for draft-ietf-pce-stateful-pce-optional

 

Hi Authors,

 

In preparation for WGLC on this draft, we'd like all authors and contributors 
to confirm on the list that they are in compliance with IETF IPR rules.

 

Please respond (copying the mailing list) to say one of:

 

- I am not aware of any IPR applicable to this draft that should be disclosed 
in accordance with IETF IPR rules.

 

- I am aware of the IPR applicable to this draft, and it has already been 
disclosed to the IETF.

 

- I am aware of IPR applicable to this draft, but that has not yet been 
disclosed to the IETF. I will work to ensure that it will be disclosed in a 
timely manner.

 

Thanks,

Andrew

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

[Pce] I-D Action: draft-ietf-pce-circuit-style-pcep-extensions-04.txt

[internet-drafts]

Internet-Draft draft-ietf-pce-circuit-style-pcep-extensions-04.txt is now
available. It is a work item of the Path Computation Element (PCE) WG of the
IETF.

   Title:   PCEP extensions for Circuit Style Policies
   Authors: Samuel Sidor
Praveen Maheshwari
Andrew Stone
Luay Jalil
Shuping Peng
   Name:draft-ietf-pce-circuit-style-pcep-extensions-04.txt
   Pages:   13
   Dates:   2024-02-26

Abstract:

   This document proposes a set of extensions for Path Computation
   Element Communication Protocol (PCEP) for Circuit Style Policies -
   Segment-Routing Policy designed to satisfy requirements for
   connection-oriented transport services.  New TLV is introduced to
   control path recomputation and new flag to add ability to request
   path with strict hops only.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-circuit-style-pcep-extensions/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-pce-circuit-style-pcep-extensions-04.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-circuit-style-pcep-extensions-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


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

[Pce] I-D Action: draft-ietf-pce-sr-path-segment-09.txt

[internet-drafts]

Internet-Draft draft-ietf-pce-sr-path-segment-09.txt is now available. It is a
work item of the Path Computation Element (PCE) WG of the IETF.

   Title:   Path Computation Element Communication Protocol (PCEP) Extension 
for Path Segment in Segment Routing (SR)
   Authors: Cheng Li
Mach(Guoyi) Chen
Weiqiang Cheng
Rakesh Gandhi
Quan Xiong
   Name:draft-ietf-pce-sr-path-segment-09.txt
   Pages:   26
   Dates:   2024-02-26

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.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-sr-path-segment/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-path-segment-09

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-sr-path-segment-09

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


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