[Idr] Re: draft-ietf-idr-sr-te-policy-attr - code point squatting

[[e-mail]]

Sue,

Thanks for your email.

The codepoints I was referring to have a registration procedure of "Specification Required", with a registry defined in 2022. So not dependent on RFC9830.

>   The authors had numbers for testing only.  It was not to be deployed.
>     But the temptation to use it always great.

Absolutely.
So to avoid temptation, authors should just not pick value that IANA has not allocated. Ever. Simple & effective.

If there is a need of a codepoint for testing, we should define experimental code points. For all our registries.

Anyhow, "Note that Internet-Drafts should not include a specific value of a
   code point until IANA has completed the early allocation for this
   value. >
https://datatracker.ietf.org/doc/html/rfc7120#section-3.1


  *   2) This draft waited on -04 (published last November) for WG LC for early allocation.

This draft was squatting on the codepoint since individual version 00 and it was squatting on code points at WG adoption time. https://datatracker.ietf.org/doc/html/draft-peng-idr-segment-routing-te-policy-attr-11#name-segment-types

Thank you for working on fixing things.
--Bruno

From: Susan Hares <[e-mail]>
Sent: Thursday, March 19, 2026 5:11 PM
To: DECRAENE Bruno INNOV/NET <[e-mail]>; [e-mail]
Cc: idr@ietf. org <[e-mail]>; idr-chairs <[e-mail]>
Subject: RE: draft-ietf-idr-sr-te-policy-attr - code point squatting


https://wiki.ietf.org/group/idr/Early-Allocation-Status

Bruno -

Part of this is my problem, I've been quietly trying to fix it.

1) All these allocations waited for the publication of RFC9830
     We thought RFC9830 would be published sooner, and the registry would be available for Early allocation.
     So, I made a bad decision. I put the assignments on the IDR wiki. Adrian told me we would have problems.
     We do.  And it is my fault.

Wiki: https://wiki.ietf.org/group/idr/Early-Allocation-Status

     The authors had numbers for testing only.  It was not to be deployed.
     But the temptation to use it always great.

2) This draft waited on -04 (published last November) for WG LC for early allocation.
So, the best thing for this draft is for me to start an Early Allocation WG LC for this draft.
I will do that tonight before I sleep.

It is also a good time to remind the authors of the following drafts
1) draft-ietf-idr-sr-policy-path-segment
2) draft-ietf-idr-sr-policy-metric
3) draft-ietf-idr-sr-policy-path-mtu
4) draft-ietf-idr-sr-te-policy-attr

That you should not use the values on the following page in products:
https://wiki.ietf.org/e/en/group/idr/Early-Allocation-Status

Instead, you should work with me to get an official "Early Allocation" number from IANA.

Sorry for the mess,
Sue Hares



Sue


From: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Sent: Thursday, March 19, 2026 12:49 AM
To: [e-mail]<mailto:[e-mail]>
Cc: idr@ietf. org <[e-mail]<mailto:[e-mail]>>; idr-chairs <[e-mail]<mailto:[e-mail]>>
Subject: draft-ietf-idr-sr-te-policy-attr - code point squatting

Hi authors,

This WG document seems to squat on code points.

https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-te-policy-attr#section-4.1<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dietf-2Didr-2Dsr-2Dte-2Dpolicy-2Dattr-23section-2D4.1&d=DwMFAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=rEoy_H4r-c4UNUr3jSF-7Q&m=wpt9j5EQ5pjYr4SYvCLahLYdfruxflN85CaUxgcH1qniSziSvMlBmQkxSFAIAMum&s=MgPwyoPRrI9MopztCrUORD4aBrvnNN9oPycAk08i5yk&e=>
https://www.iana.org/assignments/segment-routing/segment-routing.xhtml#segment-types<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_assignments_segment-2Drouting_segment-2Drouting.xhtml-23segment-2Dtypes&d=DwMFAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=rEoy_H4r-c4UNUr3jSF-7Q&m=wpt9j5EQ5pjYr4SYvCLahLYdfruxflN85CaUxgcH1qniSziSvMlBmQkxSFAIAMum&s=JLZHbqqP5Qm2Vmoarxiwr9NF3B-9vZ-PaEuaVemST18&e=>

If so, in order for us to improve,

-            Could you elaborate on the reason for squatting?

-            Could you suggest incentive for authors not to squat on code points ?

Thank you
--Bruno



____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.