If this bis document had a longer set of IANA Considerations, we might have different advice, but in this case, we would recommend updating the section to read as follows:
For the following URI in the "IETF XML Registry" [RFC3688], IANA has updated the reference field to refer to this document:
URI: urn:ietf:params:xml:ns:yang:ietf-layer0-types
Registrant Contact: The IESG
XML: N/A; the requested URI is an XML namespace.
This document also adds an updated YANG module to the "YANG Module
Names" registry [RFC7950]:
Name: ietf-layer0-types
Namespace: urn:ietf:params:xml:ns:yang:ietf-layer0-types
Prefix: l0-types
Reference: this document
When a document is obsoleted, the action for us is usually to update the original registration's reference field (unless the registration is being deprecated/obsoleted). The YANG Module Names registry is unusual in that we'll actually leave the current registration alone and instead make a second registration that links to the new version of the module and has the new document as its reference.
If you have any questions, just let us know. If you'd like to talk in person, you can find us next to the RFC Editor's table from Monday through Thursday.
If at any time you'd like an early review for any document, just send us a message at iana@iana.org.
Dear Authors,
Before the IETF meeting, we check documents listed on working group agendas for IANA-related issues. We have a couple of notes about this document:
https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-rfc9093-bis
If this bis document had a longer set of IANA Considerations, we might have different advice, but in this case, we would recommend updating the section to read as follows:
For the following URI in the "IETF XML Registry" [RFC3688], IANA has updated the reference field to refer to this document:
This document also adds an updated YANG module to the "YANG Module Names" registry [RFC7950]:
When a document is obsoleted, the action for us is usually to update the original registration's reference field (unless the registration is being deprecated/obsoleted). The YANG Module Names registry is unusual in that we'll actually leave the current registration alone and instead make a second registration that links to the new version of the module and has the new document as its reference.
If you have any questions, just let us know. If you'd like to talk in person, you can find us next to the RFC Editor's table from Monday through Thursday.
If at any time you'd like an early review for any document, just send us a message at iana@iana.org.
Best regards,
Amanda Baber IANA Operations Manager