"The RPF Vector TLV", IJsbrand Wijnands, 20-Oct-08. ( bytes)

This document describes a use of the PIM Join Attribute as defined in draft-ietf-pim-join-attributes [I-D.ietf-pim-join-attributes] which enables PIM to build multicast trees through an MPLS-enabled network, even if that network's IGP does not have a route to the source of the tree.

"Authentication and Confidentiality in PIM-SM Link-local Messages", William Atwood, Salekul Islam, Maziar Siami, 3-Nov-08. ( bytes)

RFC 4601 mandates the use of IPsec to ensure authentication of the link-local messages in the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing protocol. This document specifies mechanisms to authenticate the PIM-SM link local messages using the IP security (IPsec) Authentication Header (AH) or Encapsulating Security Payload (ESP). It specifies optional mechanisms to provide confidentiality using the ESP. Manual keying is specified as the mandatory and default group key management solution. To deal with issues of scalability and security that exist with manual keying, an optional automated group key management mechanism is specified.

"Population Count Extensions to PIM", Dino Farinacci, Greg Shepherd, 28-Jul-08. ( bytes)

This specification defines a method for providing multicast distribution-tree accounting data for billing and debugging. Simple extensions to the PIM protocol allow a rough approximation of tree- based data in a scalable fashion.

"A Reliable Transport Mechanism for PIM", Dino Farinacci, IJsbrand Wijnands, Apoorva Karan, A Boers, Maria Napierala, 22-Aug-08. ( bytes)

This draft describes how a reliable transport mechanism can be used by the PIM protocol to optimize CPU and bandwidth resource utilization by eliminating periodic Join/Prune message transmission. This draft proposes a modular extension to PIM to use either the TCP or SCTP transport protocol.

"PIM Group-to-RP Mapping", Bharat Joshi, Andy Kessler, David McWalter, 21-Oct-08. ( bytes)

Each PIM-SM router in a PIM Domain which supports ASM maintains Group-to-RP mappings which are used to identify a RP for a specific multicast group. PIM-SM has defined an algorithm to choose a RP from the Group-to-RP mappings learned using various mechanisms. This algorithm does not allow administrator to override a specific Group- to-RP mapping with the static Group-to-RP mapping which an administrator would want to use. This algorithm also does not consider the PIM mode and the mechanism through which a Group-to-RP mapping was learned. The intention of this document is to suggest a standard algorithm to deterministically choose between several group-to-rp mappings for a specific group. This document first explains the requirements to extend the Group-to-RP mapping algorithm and then proposes the new algorithm.

Return to Internet-Draft directory.

Return to IETF home page.