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

[Dhruv Dhody]

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 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
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

[Pce] Fwd: [IANA #1358857] Re: Early code point allocation for draft-ietf-pce-segment-routing-policy-cp-12

[Dhruv Dhody]

Hi,

This early allocation is completed.

Thanks!
Dhruv

-- Forwarded message -
From: Sabrina Tanamal via RT 
Date: Wed, Feb 14, 2024 at 6:51 AM
Subject: [IANA #1358857] Re: Early code point allocation for
draft-ietf-pce-segment-routing-policy-cp-12
To: 
Cc: , , <
draft-ietf-pce-segment-routing-policy...@ietf.org>


Hi Dhruv and Julien,

We've completed the additional early allocations for this document:

PCEP TLV Type Indicators registry (Section 6.2):

68  COMPUTATION-PRIORITY (TEMPORARY - registered 2024-02-13, expires
2025-02-13)[draft-ietf-pce-segment-routing-policy-cp-14]
69  EXPLICIT-NULL-LABEL-POLICY (TEMPORARY - registered 2024-02-13,
expires 2025-02-13)  [draft-ietf-pce-segment-routing-policy-cp-14]
70  INVALIDATION (TEMPORARY - registered 2024-02-13, expires
2025-02-13)[draft-ietf-pce-segment-routing-policy-cp-14]
71  SRPOLICY-CAPABILITY (TEMPORARY - registered 2024-02-13, expires
2025-02-13) [draft-ietf-pce-segment-routing-policy-cp-14]

PCEP-ERROR Object Error Types and Values registry(Section 6.3):

6   Mandatory Object missing
21: Missing SR Policy Mandatory TLV (TEMPORARY - registered 2024-02-13,
expires 2025-02-13) [draft-ietf-pce-segment-routing-policy-cp-14]

26  Association Error
20: SR Policy Identifers Mismatch (TEMPORARY - registered 2024-02-13,
expires 2025-02-13)   [draft-ietf-pce-segment-routing-policy-cp-14]
21: SR Policy Candidate Path Identifier Mismatch (TEMPORARY - registered
2024-02-13, expires 2025-02-13)
[draft-ietf-pce-segment-routing-policy-cp-14]

TE-PATH-BINDING TLV Flag field registry (Section 6.4):

1   S (Specified-BSID-only) (TEMPORARY - registered 2024-02-13, expires
2025-02-13) [draft-ietf-pce-segment-routing-policy-cp-14]

Please see
https://www.iana.org/assignments/pcep

If the document hasn't been approved for publication by December, we'll
contact you about renewing for another year.

Best regards,

Sabrina Tanamal
Lead IANA Services Specialist

On Tue Feb 13 05:25:39 2024, d...@dhruvdhody.com wrote:
> Hi IANA,
>
> Following the procedure for early allocation as per RFC 7120, we would
> like
> to request early allocation for following code points defined in
>
> https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-
> cp-14.html#section-6.2
>  (TBD1-4)
> https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-
> cp-14.html#section-6.3
>  (TBD6-8)
> https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-
> cp-14.html#section-6.4
>  (TBD9)
>
> An approval from the AD (in cc) can be found in the email chain below.
>
> Note that there was an earlier allocation request where some
> codepoints
> were already allocated by IANA -
> https://mailarchive.ietf.org/arch/msg/pce/8GtjtxNWeA9MxpySx6J7XZKmlUc/
> Thanks!
> Dhruv & Julien
> PCE WG Co-chairs
>
> On Sat, Feb 10, 2024 at 6:37 PM John Scudder  wrote:
>
> > Approved.
> >
> > —John
> >
> > On Feb 10, 2024, at 1:27 AM, Dhruv Dhody  wrote:
> >
> > Hi John,
> >
> > The authors of draft-ietf-pce-segment-routing-policy-cp have
> > requested for
> > the early allocation of the codepoint specified in:
> >
> >
> > https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-
> > policy-cp-14.html#section-6.2
> >  > ietf-pce-segment-routing-policy-cp-14.html*section-
> > 6.2__;Iw!!NEt6yMaO-gk!Fkn1X-
> > qBnJV4EMHZM1CiBGd6i2laMtrXwmVcfGt5pdN7gxvPDWukyX1bs4fVtHgbBpAjD7SXOd4$>
> > (TBD1-4)
> >
> > https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-
> > policy-cp-14.html#section-6.3
> >  > ietf-pce-segment-routing-policy-cp-14.html*section-
> > 6.3__;Iw!!NEt6yMaO-gk!Fkn1X-
> > qBnJV4EMHZM1CiBGd6i2laMtrXwmVcfGt5pdN7gxvPDWukyX1bs4fVtHgbBpAjU9kcsWQ$>
> > (TBD6-8)
> >
> > https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-
> > policy-cp-14.html#section-6.4
> >  > ietf-pce-segment-routing-policy-cp-14.html*section-
> > 6.4__;Iw!!NEt6yMaO-gk!Fkn1X-
> > qBnJV4EMHZM1CiBGd6i2laMtrXwmVcfGt5pdN7gxvPDWukyX1bs4fVtHgbBpAj7X0mWuw$>
> > (TBD9)
> >
> > We polled the WG and there were no objections. According to the
> > chairs’
> > review, the RFC 7120 criteria is met. As per the process in the RFC,
> > we now
> > request your approval before reaching out to the IANA for the early
> > allocation.
> >
> > Thanks!
> >
> > Dhruv & Julien
> >
> > On Wed, Jan 24, 2024 at 11:21 AM Dhruv Dhody 
> > wrote:
> > >
> > > Hi WG,
> > >
> > > We received no objections and thus will be going ahead with the
> > > early
> > allocation process.
> > >
> > > Thanks!
> > > Dhruv & Julien
> > >
> > > On Wed, Jan 10, 2024 at 6:53 PM Dhruv Dhody 
> > > wrote:
> > >>
> > >> Hi WG,
> > >>
> > >> We have received a request from the authors of
> > draft-ietf-pce-segment-routing-policy-cp for an early code point
> > allocation
> > for 

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

[LUIS MIGUEL CONTRERAS MURILLO]

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 
; Fernando Agraz 
; LUIS MIGUEL CONTRERAS MURILLO 
; salvatore.spadaro 

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
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

[Pce] I-D Action: draft-ietf-pce-sr-bidir-path-13.txt

[internet-drafts]

Internet-Draft draft-ietf-pce-sr-bidir-path-13.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) Extensions 
for Associated Bidirectional Segment Routing (SR) Paths
   Authors: Cheng Li
Mach(Guoyi) Chen
Weiqiang Cheng
Rakesh Gandhi
Quan Xiong
   Name:draft-ietf-pce-sr-bidir-path-13.txt
   Pages:   20
   Dates:   2024-02-13

Abstract:

   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.
   Segment routing (SR) leverages the source routing and tunneling
   paradigms.  The Stateful PCEP extensions allow stateful control of
   Segment Routing Traffic Engineering (TE) Paths.  Furthermore, PCEP
   can be used for computing SR TE paths in the network.

   This document defines PCEP extensions for grouping two unidirectional
   SR Paths (one in each direction in the network) into a single
   associated bidirectional SR Path.  The mechanisms defined in this
   document can also be applied using a stateful PCE for both PCE-
   initiated and PCC-initiated LSPs or when using a stateless PCE.

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

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

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

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