1 / 3

PIM WG

PIM WG. -draft-ietf-pim-bidir Bill -draft-ietf-pim-mib-v2 Bill -draft-ietf-pim-sm-bsr Stig -draft-ietf-pim-bsr-mib Mike -draft-ietf-pim-join-attributes Arjen -draft-ietf-pim-rpf-vector Arjen -draft-ietf-pim-lasthop-threats Pekka

lyle
Download Presentation

PIM WG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PIM WG -draft-ietf-pim-bidir Bill -draft-ietf-pim-mib-v2 Bill -draft-ietf-pim-sm-bsr Stig -draft-ietf-pim-bsr-mib Mike -draft-ietf-pim-join-attributes Arjen -draft-ietf-pim-rpf-vector Arjen -draft-ietf-pim-lasthop-threats Pekka -draft-ietf-pim-sm-linklocal Mike -rechartering/milestones/future work Mike

  2. 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 could involve reliability, resiliency, scalability, management, and security. The PIM WG will also 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 PIM-BIDIR and BSR may also be necessary. The working group will continue to specify the MIBs 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. The working group will determine if a Version 3 of PIM is required.

  3. Goals and Milestones: Mar 2007 Ratify new WG charter and milestones Jul 2007 Submit the BSR spec as a Proposed Standard Jul 2007 Submit the BSR MIB as a Proposed Standard Nov 2007 Propose a more reliable pim solution which includes refresh reduction Nov 2007 Submit a generic TLV PIM Join Attribute as PS Nov 2007 Submit RPF Vector as a Proposed Standard Nov 2007 Submit a mechanism to authenticate PIM link local messages as PS Nov 2007 Submit an Informational PIM last hop threats doc

More Related