- External VPN forwarder at page 12 appears not to support QinQ, should it?
- Draft seems IPv4 centric, with static /32 often appearing, while IPv6 support is explicitly mentioned. - Draft mentions GRE and MPLS supported, but most examples speak as if it's always GRE encapsulated. 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) 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
