WG adoption poll - draft-zzhang-l3vpn-mvpn-bidir-ingress-replication-01
Hello working group, This email starts a two-week poll on adopting draft-zzhang-l3vpn-mvpn-bidir-ingress-replication-01 [1]. Please send comments to the list and state if you support adoption or not (in the latter case, please also state the reasons). This poll runs until January the 22nd. Coincidentally, we are also polling for knowledge of any IPR that applies to this draft, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email whether or not you are aware of any relevant IPR. The draft will not be adopted until a response has been received from each author and contributor. If you are on the L3VPN WG mailing list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you, Martin Thomas l3vpn chairs [1] http://tools.ietf.org/html/draft-zzhang-l3vpn-mvpn-bidir-ingress-replication
I-D Action: draft-ietf-l3vpn-mvpn-bidir-07.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF. Title : MVPN: Using Bidirectional P-Tunnels Authors : Eric C. Rosen IJsbrand Wijnands Yiqun Cai Arjen Boers Filename: draft-ietf-l3vpn-mvpn-bidir-07.txt Pages : 32 Date: 2014-01-08 Abstract: A set of prior RFCs specify procedures for supporting multicast in BGP/MPLS IP VPNs. These procedures allow customer multicast data to travel across a service provider's backbone network through a set of multicast tunnels. The tunnels are advertised in certain BGP multicast auto-discovery routes, by means of a BGP attribute known as the Provider Multicast Service Interface (PMSI) Tunnel attribute. Encodings have been defined that allow the PMSI Tunnel attribute to identify bidirectional (multipoint-to-multipoint) multicast distribution trees. However, the prior RFCs do not provide all the necessary procedures for using bidirectional tunnels to support multicast VPNs. This document updates RFCs 6513 and 6625 by specifying those procedures. In particular, it specifies the procedures for assigning customer multicast flows (unidirectional or bidirectional) to specific bidirectional tunnels in the provider backbone, for advertising such assignments, and for determining which flows have been assigned to which tunnels. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-l3vpn-mvpn-bidir/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-l3vpn-mvpn-bidir-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-l3vpn-mvpn-bidir-07 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
