Protocol Independent Multicast (pim)

Last Modified: 2008-08-21

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

Chair(s):

  • Mike McBride <mmcbride@cisco.com>

  • Stig Venaas <venaas@uninett.no>

    Routing Area Director(s):

  • Ross Callon <rcallon@juniper.net>
  • David Ward <dward@cisco.com>

    Routing Area Advisor:

  • David Ward <dward@cisco.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
    Dec 2007  Submit the BSR spec as a Proposed Standard to the IESG
    Dec 2007  Submit the BSR MIB as a Proposed Standard to the IESG
    Mar 2008  Submit a more reliable pim solution (refresh reduction) to the IESG
    Mar 2008  Submit a generic TLV PIM Join Attribute PS draft to the IESG
    Mar 2008  Submit RPF Vector (use of PIM Join Attribute) as PS to the IESG
    Mar 2008  Submit a way to authenticate PIM link local messages as PS to the IESG
    Mar 2008  Submit an Informational PIM last hop threats document to the IESG

    Internet-Drafts:

    The RPF Vector TLV (17375 bytes)
    Authentication and Confidentiality in PIM-SM Link-local Messages (48410 bytes)
    Population Count Extensions to PIM (25310 bytes)
    A Reliable Transport Mechanism for PIM (51380 bytes)
    PIM Group-to-RP Mapping (21351 bytes)

    Request For Comments:

    Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised) (RFC 3973) (136708 bytes)
    Anycast-RP Using Protocol Independent Multicast (PIM) (RFC 4610) (22490 bytes)
    Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised) (RFC 4601) (340632 bytes) obsoletes RFC 2362
    Protocol Independent Multicast - Sparse Mode (PIM-SM) IETF Proposed Standard Requirements Analysis (RFC 4602) (15310 bytes)
    Bi-directional Protocol Independent Multicast (BIDIR-PIM) (RFC 5015) (96431 bytes)
    Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM) (RFC 5059) (100749 bytes)
    Protocol Independent Multicast MIB (RFC 5060) (170123 bytes)
    Protocol Independent Multicast (PIM) Bootstrap Router MIB (RFC 5240) (42636 bytes)
    Host Threats to Protocol Independent Multicast (PIM) (RFC 5294) (26525 bytes)
    The Protocol Independent Multicast (PIM) Join Attribute Format (RFC 5384) (22330 bytes)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.