40 likes | 184 Vues
This document outlines the current status and initiatives of the PIM Working Group, including updates on various drafts such as draft-ietf-pim-pop-count-04 and others. It highlights the group's focus on developing extensions for multicast support in L2 and L3 VPNs, managing existing MIB modules, and addressing errata to advance RFC 4601 to Draft Standard. The charter emphasizes the working group's commitment to improving PIM and its related protocols while considering new proposals for updates and extensions.
E N D
pim wgquebec city Agenda bashing, document status Mike/Stig draft-ietf-pim-pop-count-04 Stig Venaas 4601 update Jeffrey Zhang draft-hou-pim-ecmp-01 Heidi Ou draft-bhatia-zhang-pim-auth-extension-00 Dacheng Zhang draft-brigm-deterministicrp-00 Michael Brig draft-wijnands-pim-neighbor-reduction-02 Ice Wijnands
Active: draft-ietf-pim-pop-count-04 IESG Processing: draft-ietf-pim-hello-intid-01 draft-ietf-pim-mtid-08 draft-ietf-pim-port-07 Published this year: RFC6226rpmapping RFC6116 registry
Charter New: “If L2VPN or L3VPNWGs determine that support for multicast in L2VPNs and/or L3VPNs requires extensions to PIM, then such extensions will be developed within the PIM WG.” “The working group has produced MIB modules for PIM in RFC 5060 and RFC5240. 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.”
Charter New (con’t): “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.”