1. L3VPN WG IETF 78 30/07/2010 09:00-11:30 Chairs: Marshall Eubanks Danny McPherson Ben Niven-Jenkins

2. 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 3979 RFC 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. http://www.ietf.org/about/note-well.html

3. Agenda WG Status Page: http://tools.ietf.org/wg/l3vpnhttp://tools.ietf.org/wg/l3vpn Administration – Blue sheets – Scribe/Jabber Jabber room: l3vpn@jabber.ietf.orgl3vpn@jabber.ietf.org WG Status, Re-charter Update (20 minutes) Leaf discovery mechanism for mLDP based P2MP/MP2MP LSP – Lizhong Jin (10 minutes) – http://tools.ietf.org/html/draft-jin-mpls-mldp-leaf-discovery-01 http://tools.ietf.org/html/draft-jin-mpls-mldp-leaf-discovery-01 IPv4 and IPv6 Infrastructure Addresses in MCAST-VPN Routes – Eric Rosen/Rahul Aggarwal) (10 minutes) – http://tools.ietf.org/html/draft-rosen-l3vpn-mvpn-infra-addrs-00 http://tools.ietf.org/html/draft-rosen-l3vpn-mvpn-infra-addrs-00

4. WG Status RFC Editors’ queue – draft-ietf-l3vpn-2547bis-mcast-bgp Ref to draft-ietf-l3vpn-2547bis-mcast (In RFC Ed Queue) – draft-ietf-l3vpn-2547bis-mcast Ref to draft-ietf-l3vpn-2547bis-mcast-bgp (In RFC Ed Queue) Ref to draft-ietf-mpls-ldp-p2mp (Active) Ref to draft-ietf-mpls-rsvp-te-no-php-oob-mapping (Active) – draft-ietf-l3vpn-mvpn-considerations Ref to draft-ietf-l3vpn-2547bis-mcast (In RFC Ed Queue) Ref to draft-ietf-l3vpn-2547bis-mcast-bgp (In RFC Ed Queue) Active drafts – draft-ietf-l3vpn-acceptown-community – draft-ietf-l3vpn-ibgp Consensus to change Intended status to PS & request an early IANA allocation. – draft-ietf-l3vpn-mvpn-spmsi-joins In WG LC (ends 5 th August) – draft-ietf-l3vpn-ospfv3-pece

5. New Charter & Milestones Consensus to update Description of Working Group (Charter) to: This working group is responsible for defining, specifying and extending BGP/MPLS IP VPNs solutions (based on RFC4364 and RFC4659) for supporting provider-provisioned Layer-3 (routed) Virtual Private Networks (L3VPNs). The WG will continue to extend and enhance RFC4364 and RFC4659 based solutions so that these solutions can be used to provide IPv4, IPv6, and MPLS services including multicast. The following VPN deployment scenarios will be considered by the WG: 1. Single service provider (SP)/single AS: VPN sites attached to the network of a single provider within the scope of a single AS. 2. Single SP/multiple AS'es: VPN sites attached to the network of a single provider consisting of multiple AS'es. 3. Cooperating SPs: VPN sites attached to networks of different providers that cooperate with each other to provide VPN service. As part of this effort the WG will work on the following tasks: 1. Additional requirements and framework for Layer 3 VPNs. 2. Solution documents, including applicability statements. 3. MIB definitions. 4. Security mechanisms. As a general rule, the WG will not create new protocols, but will extend existing protocols to provide the necessary L3VPN functionality. Protocol extensions that provide L3VPN functionality will be reviewed by both the L3VPN WG and by the WG responsible for the protocol being extended. The WG will continue to extend and enhance the Multicast over BGP/MPLS VPN solution. http://www.niven-jenkins.co.uk/L3VPN/New-L3VPN-Charter-01.txt

6. Proposed Milestones Oct 2010 – Submit MVPNv6 using PIM & S-PMSIs specification to IESG as PS (draft-ietf-l3vpn-mvpn-spmsi-joins). Nov 2010 – Submit MVPN infrastructure address encoding document to IESG for publication as PS (draft-rosen-l3vpn- mvpn-infra-addrs) May 2011 – Submit S-PMSI A-D route Wildcard selection specification to IESG as PS (draft-rosen-l3vpn-mvpn-wildcards & draft-rekhter-mvpn-wildcard-spmsi) Nov 2011 – Submit MVPN Extranet specification to IESG as PS (draft-raggarwa-l3vpn-bgp-mvpn-extranet & draft-rosen- l3vpn-mvpn-extranet) TBD – Submit specification for fast failover in (M)VPN to IESG as TBD (draft-morin-l3vpn-mvpn-fast-failover) – Submit specification for using Internal BGP as PE-CE protocol to IESG as PS (draft-ietf-l3vpn-ibgp) – Submit specification for modifying Route Targets by BGP Route Reflectors including when the VRFs are on the same PEs as PS (draft-ietf-l3vpn-acceptown-community) Sep 2011 – Submit specification of using Bi-directional P-tunnels for MVPN to IESG as PS (draft-rosen-l3vpn-mvpn-bidir) Nov 2011 – Submit specification for using PE-PE PIM in the absence of MI-PMSI to IESG as PS (draft-rosen-l3vpn-mvpn- mspmsi)