Hi Luis, On Mon, Feb 26, 2024 at 11:59 PM LUIS MIGUEL CONTRERAS MURILLO < [email protected]> 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 <[email protected]> > *Enviado el:* miércoles, 14 de febrero de 2024 5:42 > *Para:* LUIS MIGUEL CONTRERAS MURILLO < > [email protected]> > *CC:* [email protected] > *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 < > [email protected]> 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: [email protected] <[email protected]> > Enviado el: martes, 13 de febrero de 2024 20:22 > Para: LUIS MIGUEL CONTRERAS MURILLO < > [email protected]>; Fernando Agraz < > [email protected]>; LUIS MIGUEL CONTRERAS MURILLO < > [email protected]>; salvatore.spadaro < > [email protected]> > 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 senhoria o destinatário > indicado, fica notificado de que a leitura, utilização, divulgação e/ou > cópia sem autorização pode estar proibida em virtude da legislação vigente. > Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique > imediatamente por esta mesma via e proceda a sua destruição > _______________________________________________ > Pce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/pce > > > ------------------------------ > > 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 senhoria o destinatário > indicado, fica notificado de que a leitura, utilização, divulgação e/ou > cópia sem autorização pode estar proibida em virtude da legislação vigente. > Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique > imediatamente por esta mesma via e proceda a sua destruição > _______________________________________________ > Pce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/pce >
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
