Hi all,
Version 12 submitted (please see attached mail).
Changes included:
1. Addressed feedback from IANA
2. Addressed comments from Peng Shaofu (Thanks for review).
Renaming of Bandwidth metric addressed in version 11 and as Dhruv stated in his
previous message – reserving 255 value may require wider discussion.
Thanks a lot for comments to Adrian and Tom as well.
Regards,
Samuel
From: Dhruv Dhody <[email protected]>
Sent: Tuesday, July 23, 2024 4:02 PM
To: [email protected]
Cc: pce-chairs <[email protected]>; [email protected]
Subject: Re: Early code point allocation for draft-ietf-pce-sid-algo-10
Hi WG,
We will be going ahead with the early allocation. Authors have posted the -11
version - https://www.ietf.org/archive/id/draft-ietf-pce-sid-algo-11.html
The authors are planning to make another update based on the feedback from IANA.
A point was made to mark 255 as reserved but this practice needs broader
discussion and preferably a consistent approach across registries.
Thanks!
Dhruv & Julien
On Sat, Jun 22, 2024 at 1:41 AM Dhruv Dhody
<[email protected]<mailto:[email protected]>> wrote:
Hi WG,
We have received a request from the authors of draft-ietf-pce-sid-algo for an
early code point allocation for the codepoints listed in -
https://www.ietf.org/archive/id/draft-ietf-pce-sid-algo-10.html#table-7
These are the codepoints for the latest changes made to align with
draft-ietf-lsr-flex-algo-bw-con as per -
https://mailarchive.ietf.org/arch/msg/pce/U2AIec7Vk9LomZM-LlvhxGywQgA/
The chairs would like to know if there are any objections to adding these new
metric types and keeping a range aside for user defined metrics.
Further, RFC 7120 requires one to meet the following criteria to proceed:
b. The format, semantics, processing, and other rules related to
handling the protocol entities defined by the code points
(henceforth called "specifications") must be adequately described
in an Internet-Draft.
c. The specifications of these code points must be stable; i.e., if
there is a change, implementations based on the earlier and later
specifications must be seamlessly interoperable.
If anyone believes that the draft does not meet these criteria or believes that
early allocation is not appropriate for any other reason, please send an email
to the PCE mailing list explaining why. If the chairs hear no objections by
Monday, July 8th, we will kick off the early allocation request.
Note that there was an earlier allocation request where some codepoints were
already allocated by IANA -
https://mailarchive.ietf.org/arch/msg/pce/8jv4slxI_K3p4qqUPRlAjSgScOA/
Thanks!
Dhruv & Julien
--- Begin Message ---
A new version of Internet-Draft draft-ietf-pce-sid-algo-12.txt has been
successfully submitted by Samuel Sidor and posted to the
IETF repository.
Name: draft-ietf-pce-sid-algo
Revision: 12
Title: Carrying SR-Algorithm information in PCE-based Networks.
Date: 2024-07-23
Group: pce
Pages: 22
URL: https://www.ietf.org/archive/id/draft-ietf-pce-sid-algo-12.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-pce-sid-algo/
HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-pce-sid-algo
Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-sid-algo-12
Abstract:
The SR-Algorithm associated with a Segment-ID (SID) defines the path
computation algorithm used by Interior Gateway Protocols (IGPs).
This information is available to controllers such as the Path
Computation Element (PCE) via topology learning. This document
proposes an approach for informing headend routers regarding the SR-
Algorithm associated with each SID used in PCE-computed paths, as
well as signalling a specific SR-Algorithm as a constraint to the
PCE.
The IETF Secretariat
--- End Message ---
_______________________________________________
Pce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
