IANA Considerations for Remote Procedure Call (RPC) Network Identifiers and Universal Address Formats
RFC 5665
Yes
No Objection
Note: This ballot was opened for revision 06 and is now closed.
Lars Eggert Yes
(Chris Newman; former steering group member) No Objection
(Cullen Jennings; former steering group member) No Objection
(Dan Romascanu; former steering group member) No Objection
(David Ward; former steering group member) No Objection
(Lisa Dusseault; former steering group member) No Objection
I don't understand why this document has both registered netids and constants. That seems redundant to me.
(Magnus Westerlund; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Pasi Eronen; former steering group member) (was Discuss) No Objection
(Ron Bonica; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Tim Polk; former steering group member) No Objection
In sections 4.1 and 4.2, the registrant provides a value of TBD1 in the registration request, and IANA substitutes the assigned value for TBD1. This is very clear but isn't quite right if a single document requests multiple registrations. In that case, the provided values would also include TBD2, ..., TBDx. To be honest, I'm not sure if any readers would actually be confused and I can't think of a better way to write the text myself. If an obvious solution comes to the author, that would be great. Otherwise, there is probably no harm in proceeding as is.