Hi Greg, Joel and all,
Thanks for your discussion on the MPLS mailing list as following link shown~
https://mailarchive.ietf.org/arch/msg/mpls/e3CI8xeDN1OTu5FgAIB6tI_yRaY/
Allow me to take the discussion to PCE. As per RFC9545 and
draft-ietf-spring-srv6-path-segment, a path segment can identify
Hi Nagendra,
Sorry for delayed response - I completely missed this mail somehow.
Please see my responses inline
Thanks a lot,
Samuel
-Original Message-
From: Nagendra Nainar via Datatracker
Sent: Thursday, August 22, 2024 7:56 PM
To: ops-...@ietf.org
Cc: draft-ietf-pce-sid-algo@i
Hi all,
Since we have consensus, let's move forward with this simple fix to [1],
as agreed with the IESG. This message starts a 2-week WG last call for
draft-ietf-pce-iana-update-01 [2]. Please share your support or comments
on the PCE mailing list by Friday September 20.
Thank you,
Julien
These references appear useful. There is however one aspect that I am
missing. It may well be my own mistake, rather than a problem in the
draft. The usage of the sr path segment relies on the tail of the path
being able to recognize the path segment label. I am not familiar with
any usage
Thanks Julien.
This is good and speedy progress (proof, if any were needed , that the IETF does not need to take multiple years to make simple changes).
As a co-author, I am content with the text and think it is ready to move forward.