1 / 4

pim wg quebec city

pim wg quebec city. Agenda bashing, document status Mike/Stig d raft-ietf-pim-pop-count-04 Stig Venaas 4601 update Jeffrey Zhang draft-hou-pim- ecmp -01 Heidi Ou

kasie
Download Presentation

pim wg quebec city

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 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

  2. 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

  3. 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.”

  4. 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.”

More Related