L2VPN WG Meeting IETF 79 Beijing, China

Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: –The IETF plenary session –The IESG, or any member thereof on behalf of the IESG –Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices –Any IETF working group or portion thereof –The IAB or any member thereof on behalf of the IAB –The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).RFC 5378RFC 3979RFC 4879 Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details.RFC 5378RFC 3979 A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

3 Document Status (1) In RFC-Editor Queue –draft-ietf-l2vpn-signaling-08 Over 4 years held on Norm. Reference to draft-ietf-pwe3- segmented-pw IESG EVALUATION: –draft-ietf-l2vpn-vpls-bridge-interop-06 – IESG Telechat on 18 th November –draft-ietf-l2vpn-oam-req-frmk-11 – AD follow-up

4 Document Status (2) ARP-MED & IPLS: –draft-ietf-l2vpn-arp-mediation has minor changes to v6 handling from -13 Himanshu has now published -15 to fix editorial issues Nabil will act as document shepherd –draft-ietf-l2vpn-ipls-09 Himanshu will publish an update “Real Soon Now” MIB: –draft-ietf-l2vpn-vpls-mib-04 Passed WG Last Call, then expired. Giles now shepherding –draft-kkoushik-snmp-context-map-mib-02 Plan is to refresh before next IETF

Document Status (3) Multicast –VPLS: draft-ietf-l2vpn-mcast addresses Wim’s comments -08 makes LDP P2MP LSP support a MUST Nabil issuing last call –VPMS: draft-ietf-l2vpn-vpms-frmwk-requirements-03 draft-raggarwa-l2vpn-p2mp-pw-03 5

6 Document Status (4) Service Convergence / Multi-homing: –draft-ietf-l2vpn-vpls-ldp-mac-opt-03 Being presented today –draft-ietf-l2vpn-vpls-macflush-ld-00 Was draft-pwkok-l2vpn-vpls-macflush-ld-01 Giles to approve as WG draft –draft-ietf-l2vpn-vpls-multihoming-02 2 revisions since last IETF Will be presented in Prague

7 Document Status (5) Scalability –draft-ietf-l2vpn-pbb-vpls-pe-model-02 Being presented here in Beijing –draft-ietf-l2vpn-pbb-vpls-bridge-interop-00 Expired –Ali and Florin plan to review both drafts and request WG last call post-IETF

Potential Merger of L2/L3VPN History –Originally PPVPN included L2VPN work –Split in two (L2/L3VPN) due to amount of work Present –Busy in L2VPN but not in L3VPN –Various potential new work areas for L2VPN Future –Data centre space may require L2/L3 mix? –Recombine working groups, or re-charter L2VPN and make L3VPN mailing list only?

Re-charter of L2VPN Two work areas seem to merit discussion –E-Tree –MAC VPN We have a huge backlog of current work –10 active Working Group drafts –15 outstanding milestones Can we please fix the backlog first?