Hi All,

I support the adoption of this document and have the following comments
(not blocking adoption) for the consideration of the authors & the WG.

1) While the algorithm was originally introduced for Prefix-SID in RFC8402,
it has since been also extended to cover Adjacency SID. I hope the text in
the draft can reflect that better. Also, some reference to IGP flex-algo
would be helpful since that is perhaps one of the key drivers for this work.

2) I would suggest using the "A" flag in the capabilities for Algorithm
than the currently used "S".

3) For the ERO encoding, we seem to be getting into problematic territory
as also indicated by Andrew. I would suggest that the ordering of optional
fields strictly follow the order in which flags are being introduced (i.e.
their bit position). This way, we at least don't get into random scenarios.
I am not sure if the ordering in the ASCII art is considered normative. In
the future, it would be best if we follow pure TLV/sub-TLV based encoding
at all times - i.e. always introduce capabilities for sub-TLVs even though
there might be none foreseen at the time of defining a new TLV.

4) For the LSPA Object, I presume the L (loose) flag is actually indicating
a "non-strict" adherence to the algo constraint. Somehow the "loose" term
may give a different impression. There is the preference for an algo and
then a strict requirement for an algo to be followed (e.g. for flex-algo).
Also, some clarity on the use of Adj-SIDs that don't have an associated
algo with them would be helpful.

Thanks,
Ketan



On Fri, Feb 4, 2022 at 10:45 PM Dhruv Dhody <[email protected]> wrote:

> Hi WG,
>
> This email begins the WG adoption poll for draft-tokar-pce-sid-algo-05.
>
> https://datatracker.ietf.org/doc/draft-tokar-pce-sid-algo/
>
> Should this draft be adopted by the PCE WG? Please state your reasons -
> Why / Why not? What needs to be fixed before or after adoption? Are you
> willing to work on this draft? Review comments should be posted to the list.
>
> Please respond by Monday 21st Feb 2022.
>
> Have a great weekend.
>
> Thanks!
> Dhruv & Julien
> _______________________________________________
> Pce mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/pce
>
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce

Reply via email to