On Apr 2, 2013, at 2:36 AM, Saku Ytti wrote: > - External VPN forwarder at page 12 appears not to support QinQ, should it?
The document describes the behavior of the end-system and the external Forwarder. In my mind, the scenario where Q-in-Q (or other L2 encap) is used between the end-system and the Forwarder because of additional L2 hops should not need to be explicitly described. > > - Draft seems IPv4 centric, with static /32 often appearing, while > IPv6 support is explicitly mentioned. Searching thought the document /32 seems to appear in examples. If you don't mind pointing out explicitly where you believe the text should be corrected, i would appreciated (private email is ok). > > - Draft mentions GRE and MPLS supported, but most examples speak as if > it's always GRE encapsulated. MPLS over GRE or MPLS over UDP are used currently. MPLS over ethernet directly would require the end-system to participate in the IGP and have LDP enabled which is not to my knowledge a practical scenario. > It's not clear to me how VPN forwarder would connect via MPLS to a > P or PE node, where would IGP label come. > Or should end-system route server<->PE have OptB? (Would also give > label security, so VPN forwarder would not need to be fully trusted) The route-server is not on the forwarding path. The data-center gateway typically implements option B (or IBGP plus next-hop self) and stitches the MPLS-over-GRE LSP segment (internal to the DC) with an MPLS over L2 LSP segment outside the data-center, in scenarios where the service is delivered to a WAN L3VPN. > > > > On 2 April 2013 01:46, <[email protected]> wrote: >> >> 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 : BGP-signaled end-system IP/VPNs. >> Author(s) : Pedro Marques >> Luyuan Fang >> Ping Pan >> Amit Shukla >> Maria Napierala >> Nabil Bitar >> Filename : draft-ietf-l3vpn-end-system-01.txt >> Pages : 21 >> Date : 2013-04-01 >> >> Abstract: >> This document describes a solution in which the control plane >> protocol specified in BGP/MPLS IP VPNs [RFC4364] is used to provide a >> Virtual Network service to end-systems. These end-systems may be >> used to provide network services or may directly host end-to-end >> applications. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-l3vpn-end-system >> >> There's also a htmlized version available at: >> http://tools.ietf.org/html/draft-ietf-l3vpn-end-system-01 >> >> A diff from the previous version is available at: >> http://www.ietf.org/rfcdiff?url2=draft-ietf-l3vpn-end-system-01 >> >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> > > > > -- > ++ytti
