Hi Sabrina, Just one nit. Please update "NATIVE IP” to "Native IP” in the "PCECC-CAPABILITY sub-TLV” registry <https://www.iana.org/assignments/pcep/pcep.xhtml#pcecc-capability>.
Old: Bit Name 30 NATIVE IP New: Bit Name 30 Native IP Diff file is here: https://www.rfc-editor.org/authors/rfc9757-diff.html Best regards, RFC Editor/ap > On Mar 11, 2025, at 12:45 PM, Sabrina Tanamal via RT <iana-mat...@iana.org> > wrote: > > Hi Alanna, > > We've updated the registries accordingly. Please see > > https://www.iana.org/assignments/pcep > > Thanks, > Sabrina > > On Mon Mar 10 19:50:52 2025, apal...@staff.rfc-editor.org wrote: >> IANA, >> >> Please update your registries as follows to match the edited document >> at https://www.rfc-editor.org/authors/rfc9757-diff.html. >> >> >> 1) Please update the capitalization of the Name for the following Bit >> in the “PCECC-CAPABILITY sub-TLV” registry >> <https://www.iana.org/assignments/pcep/pcep.xhtml#pcecc-capability>. >> >> Old: >> Bit Name >> 30 NATIVE IP (TEMPORARY - registered 2023-08-14, extension >> registered 2024-07-31, expires 2025-08-14) >> >> New: >> Bit Name >> 30 Native IP >> >> >> 2) Please update the following Error-values in the "PCEP-ERROR Object >> Error Types and Values” registry >> <https://www.iana.org/assignments/pcep/pcep.xhtml#pcep-error-object> >> by adding a serial comma and removing hyphens. >> >> Old: >> Error-Type Meaning Error-value >> 19 Invalid Operation 22: Only one BPI, EPR >> or PPA object can be included in this message >> 29: Attempted >> Native-IP operations when the capability was not advertised >> 30: Unknown >> Native-IP Info >> >> New: >> Error-Type Meaning Error-value >> 19 Invalid Operation 22: Only one BPI, EPR, >> or PPA object can be included in this message >> 29: Attempted >> Native IP operations when the capability was not advertised >> 30: Unknown >> Native IP Info >> >> >> 3) Please update the name of the "CCI Object Flag Field for Native-IP” >> registry <https://www.iana.org/assignments/pcep/pcep.xhtml#cci-object- >> flag-field-native-ip> by removing the hyphen between “Native” and >> “IP”. >> >> Old: >> CCI Object Flag Field for Native-IP >> >> New: >> CCI Object Flag Field for Native IP >> >> >> 4) Please update the commas to hyphens in the "BPI Object Error Code >> Field” registry <https://www.iana.org/assignments/pcep/pcep.xhtml#bpi- >> object-error-code-field>. >> >> Old: >> Value Meaning >> 1 ASes does not match, BGP Session Failure >> 2 Peer IP can't be reached, BGP Session Failure >> >> New: >> Value Meaning >> 1 ASes do not match - BGP Session Failure >> 2 Peer IP can't be reached - BGP Session Failure >> >> >> 5) Please update "(IPnIP)” to be "(IP-in-IP)” in the "BPI Object Flag >> Field” registry <https://www.iana.org/assignments/pcep/pcep.xhtml#bpi- >> object-flag-field>. >> >> Old: >> Bit Meaning >> 7 T (IPnIP) bit >> >> New: >> Bit Meaning >> 7 T (IP-in-IP) bit >> >> >> Thank you, >> RFC Editor/ap >> >>> On Mar 10, 2025, at 12:45 PM, Alanna Paloma <apal...@staff.rfc- >>> editor.org> wrote: >>> >>> Hi Authors and John (AD), >>> >>> With John’s confirmation, we have removed Ren Tan as an author and >>> moved his name to the Contributors section. >>> >>> The files have been posted here (please refresh): >>> https://www.rfc-editor.org/authors/rfc9757.xml >>> https://www.rfc-editor.org/authors/rfc9757.txt >>> https://www.rfc-editor.org/authors/rfc9757.html >>> https://www.rfc-editor.org/authors/rfc9757.pdf >>> >>> The relevant diff files have been posted here: >>> https://www.rfc-editor.org/authors/rfc9757-diff.html (comprehensive >>> diff) >>> https://www.rfc-editor.org/authors/rfc9757-auth48diff.html (AUTH48 >>> changes) >>> https://www.rfc-editor.org/authors/rfc9757-lastdiff.html (htmlwdiff >>> diff between last version and this) >>> https://www.rfc-editor.org/authors/rfc9757-lastrfcdiff.html (rfcdiff >>> between last version and this) >>> >>> For the AUTH48 status of this document, please see: >>> https://www.rfc-editor.org/auth48/rfc9757 >>> >>> We will now ask IANA to update its registry accordingly. After the >>> IANA updates are complete, we will move forward with the publication >>> process. >>> >>> Thank you, >>> RFC Editor/ap >>> >>>> On Mar 10, 2025, at 11:30 AM, John Scudder <j...@juniper.net> wrote: >>>> >>>> Thanks for the follow up. Yes please, since nobody has objected, let >>>> us do that. >>>> >>>> —John >>>> >>>>> On Mar 10, 2025, at 2:21 PM, Alanna Paloma <apal...@staff.rfc- >>>>> editor.org> wrote: >>>>> >>>>> [External Email. Be cautious of content] >>>>> >>>>> >>>>> Hi John, >>>>> >>>>> We are just following up for your confirmation that Ren Tan should >>>>> be moved to the Contributors section. >>>>> >>>>> Thank you, >>>>> RFC Editor/ap >>>>> >>>>>> On Mar 6, 2025, at 4:56 PM, John Scudder <j...@juniper.net> wrote: >>>>>> >>>>>> Thanks for the info, Alanna. >>>>>> >>>>>> Authors — if you have any input for me regarding the most >>>>>> appropriate course of action, please let me know in the next few >>>>>> days. If you would prefer to send me your feedback privately and >>>>>> confidentially, you can do that (but of course you don’t have to). >>>>>> >>>>>> Unless I receive feedback suggesting some other course of action >>>>>> by Monday, I will request Ren Tan to be moved to the contributor >>>>>> section. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> —John >>>>>> >>>>>>>> On Mar 6, 2025, at 7:35 PM, Alanna Paloma <apal...@staff.rfc- >>>>>>>> editor.org> wrote: >>>>>>> John - It seems the authors have been unable to contact Ren Tan >>>>>>> for his approval. As noted in the RFC Editor FAQ >>>>>>> <https://urldefense.com/v3/__https://www.rfc- >>>>>>> editor.org/faq/*missingauthor__;Iw!!NEt6yMaO- >>>>>>> gk!HIjRag8oSVImlK5t9YVeaNwIjEfXdV1w8UiDAK63nov9JK7WijHVn9LzfhqAlcj7fbLS4qxBEPY3unuXuQmrFQE$ >>>>>>>> , we recommend one of the following paths if the author is >>>>>>> unreachable: >>>>> >>> > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
