datatracker.ietf.org
Sign in
Version 5.6.3.p2, 2014-09-29
Report a bug

Protocol Independent Multicast (pim)

Group
Name: Protocol Independent Multicast
Acronym:pim
Area:Routing Area (rtg)
State: Active
Charter: charter-ietf-pim-07 (Approved)
Personnel
Chairs: Stig Venaas <stig@venaas.com>
Mike McBride <mmcbride7@gmail.com>
Area Director: Alia Atlas <akatlas@gmail.com>
Tech Advisor: Brian Haberman <brian@innovationslab.net>
Mailing List
Address:pim@ietf.org
To Subscribe:https://www.ietf.org/mailman/listinfo/pim/
Archive:http://www.ietf.org/mail-archive/web/pim/
Jabber Chat
Room Address: xmpp:pim@jabber.ietf.org
Logs: http://jabber.ietf.org/logs/pim/

Charter for 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.

If L2VPN or L3VPN WGs determine that support for multicast in L2VPNs
and/or L3VPNs requires extensions to PIM, then such extensions will 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 has produced MIB modules for PIM in RFC 5060 and
RFC 5240. The working group currently has no plans to do further work
on management for PIM. If proposals are brought forward to update or
extend the existing MIB modules or to develop YANG modules, the working
group will be rechartered.

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 primarily works on extensions to PIM, but may take on
work related to IGMP/MLD.

There is a significant number of errata that need to be addressed in
order to advance RFC4601 to Draft Standard. The PIM WG will correct the
errata, as necessary, and update RFC4601.

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

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. Submission 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
Done
First WG version of udated RFC 4601
Done
Submit a more reliable PIM solution (refresh reduction) to the IESG
Done
Submit a population count extension to PIM to the IESG
Dec 2011
Submit update of RFC 4601 to IESG for advancement to Draft Standard