The choice of service name for this transport seems unfortunate; having a port number registry with a service in it called 'port' may be witty but seems like a source of future confusion. I notice that IANA currently have a service name of 'pim-port' which seems a better idea and one that I think that this I-D should adopt. Tom Petch ----- Original Message ----- From: "The IESG" <iesg-secretary@xxxxxxxx> To: "IETF-Announce" <ietf-announce@xxxxxxxx> Cc: <pim@xxxxxxxx> Sent: Monday, September 26, 2011 9:40 PM Subject: Last Call: <draft-ietf-pim-port-08.txt> (A Reliable TransportMechanism for PIM) to Experimental RFC > > The IESG has received a request from the Protocol Independent Multicast > WG (pim) to consider the following document: > - 'A Reliable Transport Mechanism for PIM' > <draft-ietf-pim-port-08.txt> as an Experimental RFC > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@xxxxxxxx mailing lists by 2011-10-10. Exceptionally, comments may be > sent to iesg@xxxxxxxx instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > > This document defines a reliable transport mechanism for the PIM > protocol for transmission of Join/Prune messages. This eliminates > the need for periodic Join/Prune message transmission and processing. > The reliable transport mechanism can use either TCP or SCTP as the > transport protocol. > > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-pim-port/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-pim-port/ > > > No IPR declarations have been submitted directly on this I-D. > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf