[pim] [IANA #1446138] Early review: draft-ietf-pim-rfc 8059-9798bis-00 (IETF 125)
"Amanda Baber via RT" <[email protected]> Thu, 12 Mar 2026 01:12:51 +0000
| Newsgroups | gmane.ietf.pim |
|---|---|
| Message-ID | <[email protected]> |
Dear Authors, Before the IETF meeting, we check working group agendas for documents with IANA-related issues. We have notes about this document: https://datatracker.ietf.org/doc/html/draft-ietf-pim-rfc8059-9798bis-00 I see that the IANA Considerations section from RFC 8059 has been carried over here. I just want to confirm that it’s correct for this document to serve as the new reference for the RFC 8059 registry and registrations. From what we’ve seen, this generally happens when a document is obsoleted, but not necessarily when it’s just being updated. I have no insight into this case, though. What I would say is that it’s confusing to read that “IANA is asked to assign” values that we’ve already assigned. It would be better to say that IANA is asked to update the references for the following registrations and registry created by RFC 8059 to point to this document, and update the language in the next two paragraphs to indicate that these actions are complete. There's a discussion of "bis" document language in draft-ietf-ianabis-rfc8126bis-01, Section 8 that might be useful here. The reference to “Two new PIM Join/Prune attribute types” (carried over from RFC 8059) is also a little confusing in that the registry the assignments come from is called “PIM Join Attribute Types,” not “PIM Join/Prune Attribute Types.” The fact that the next paragraph creates a “PIM Join/Prune Transport Types” registry makes it sound like the “Prune” in “Join/Prune attribute types” could have been a copy/paste error. This is something we should've caught before 8059 was published. 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. You can also request another review at any time by contacting us at [email protected]. For more information about IANA Considerations section requirements, please see https://www.iana.org/help/protocol-registration Best regards, Amanda Baber IANA _______________________________________________ pim mailing list -- [email protected] To unsubscribe send an email to [email protected]