Technical Summary
This document creates a simple incremental mechanism to provide
reliable PIM message delivery in PIM version 2 for use with PIM
Sparse-Mode (including Source-Specific Multicast) and Bidirectional
PIM.
The reliable transport mechanism will be used for Join-Prune message
transmission only, and can use either TCP or SCTP as the transport
protocol.
Working Group Summary
WG progress was smooth with a large number of comments from
many people helping to form the document.
Document Quality
This is an Experimental document. At least one implementation
exists.
Personnel
Mike McBride (mmcbride7@gmail.com) is the Document Shepherd.
Adrian Farrel (adrian@olddog.co.uk) is the Responsible AD
RFC Editor Note
End of 3.1:
OLD:
TCP Connection ID AFI: The AFI value to describe the address-family
of the address of the TCP Connection ID field. When this field is
0, a mechanism outside the scope of this document is used to
obtain the addresses used to establish the TCP connection.
NEW:
TCP Connection ID AFI: The AFI value to describe the address-family
of the address of the TCP Connection ID field. Note that this
value does not need to match the address-family of the PIM Hello
message that carries it. When this field is 0, a mechanism
outside the scope of this document is used to obtain the
addresses used to establish the TCP connection.
End of 3.2:
OLD:
SCTP Connection ID AFI: The AFI value to describe the address-
family of the address of the SCTP Connection ID field. When this
field is 0, a mechanism outside the scope of this document is used
to obtain the addresses used to establish the SCTP connection.
NEW:
SCTP Connection ID AFI: The AFI value to describe the address-
family of the address of the SCTP Connection ID field. Note that
this value does not need to match the address-family of the PIM
Hello message that carries it. When this field is 0, a mechanism
outside the scope of this document is used to obtain the
addresses used to establish the SCTP connection.