MPLS over L2TPv3 encap for RFC 2547 VPNs

["W. Mark Townsley" <[e-mail]>]

Based on comments received from the previous IETF meeting, I have split the MPLS 
over L2TPv3 draft into two documents.

draft-townsley-l2tpv3-mpls-01.txt targets mpls, and presents only the MPLS over 
L2TPv3 encapsulation.

draft-townsley-l3vpn-l2tpv3-00.txt targets l3vpn, and discusses the use of MPLS 
over L2TPv3 within the context of RFC2547-Style VPNs.

Yakov also had three specific points raised during both meetings that I promised 
to bring to the list. These follow:

> 1. Why extending BGP for multipoint-to-point L2TP signaling
> is preferred to the existing L2TP signaling (or extending L2TP
> to provide multipoint-to-point signaling) ?

Any sort of point to multipoint manual configuration or signaling may in fact be 
used. However, BGP does seem prudent for what is effectively an extension to 
RFC2547.

> 2. The applicability scope is by no means limited to 2547 - it is
> applicable to any multipoint-to-point application.

Yes, though the scope does not extend beyond reachability information to a given 
PE. The MPLS labels for the VPN routes themselves continue to be distributed by 
the existing mechanisms of RFC2547.

> 3. The security claims have to be reviewed by the Security ADs.

Yes, as with any potential RFC.

Thanks,

- Mark