Internet Engineering Task Force

Protocol Independent Multicast (pim)

Last Modified: 2010-10-15

Additional information is available at tools.ietf.org/wg/pim

Chair(s):

Routing Area Director(s):

Routing Area Advisor:

Adrian Farrel <adrian.farrel@huawei.com>

Mailing Lists:

General Discussion: pim@ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/pim/
Archive: http://www.ietf.org/mail-archive/web/pim/index.html

Description of Working Group:

The Protocol Independent Multicast (PIM) Working Group has completed
the standardization of PIM with RFC 4601. The WG has determined there
is additional work to be accomplished and is chartered to standardize
extensions to RFC 4601 - Protocol Independent Multicast Version 2 -
Sparse Mode. These PIM extensions will involve reliability, resiliency,
scalability, management, and security.

The PIM WG will consider implications of VPN service on PIM when it's a
component of that service or when PIM interfaces with that service at a
VPN edge. If L2VPN or L3VPN WGs determine that support for multicast in
L2VPNs and/or L3VPNs requires extensions to PIM, then such extensions
could be developed within the PIM WG.

Additional work on the PIM-BIDIR and BSR drafts may also be necessary
by the WG as these drafts progress through Standards Track.

The working group will continue to specify the MIB modules required for
PIM and its enhancements.

The PIM WG will further enhance RFC4601 as an even more scalable,
efficient and robust multicast routing protocol, which is capable of
supporting thousands of groups, different types of multicast
applications, and all major underlying layer-2 subnetwork technologies.
We will accomplish these enhancements by submitting drafts, to the
IESG, involving reliable pim, pim join attributes and pim
authentication.

The working group will initiate a new re-chartering effort if it is
determined that a Version 3 of PIM is required.

Goals and Milestones:

Done		Hold the first Working Group meeting and discuss the charter and the state of progress on the chartered items.
Done		Update the PIM-DM version 2 Internet-draft. Go to WG last call. Submision to IESG for considerations as proposed standard.
Done		Resubmit the latest PIM-SM version 2 specification to IESG for consideration as a proposed standard RFC
Done		Submit PIM-SM Applicability Statements
Done		Submit PIMv2 MIB to IESG for consideration as proposed standard.
Done		Submit updated PIM-SM and PIM-DM internet-drafts, clarifying any inconsistencies or ambiguities in the previous drafts.
Done		Submit PIM-SM version 2 and PIM-DM version 2 specifications to IESG for consideration as Draft Standards.
Done		Submit PIMv2 MIB to IESG for consideration as draft standard.
Done		Ratify new WG charter and milestones
Done		Submit the BSR spec as a Proposed Standard to the IESG
Done		Submit the BSR MIB as a Proposed Standard to the IESG
Done		Submit a generic TLV PIM Join Attribute PS draft to the IESG
Done		Submit RPF Vector (use of PIM Join Attribute) as PS to the IESG
Done		Submit a way to authenticate PIM link local messages as PS to the IESG
Done		Submit an Informational PIM last hop threats document to the IESG
Dec 2010		Submit a more reliable pim solution (refresh reduction) to the IESG

Internet-Drafts:

Population Count Extensions to PIM (29840 bytes)
A Reliable Transport Mechanism for PIM (60662 bytes)
PIM Group-to-RP Mapping (25513 bytes)
PIM Multi-Topology ID (MT-ID) Join-Attribute (20646 bytes)
A Registry for PIM Message Types (8581 bytes)

Request For Comments: