[Idr] Adoption of draft-l3vpn-legacy-rtc-00 as IDR WG document?

Yes/Support

My comments coming from a large service provider regarding the adoption of draft-l3vpn-legacy-rtc-00 as IDR WG document are the following:

- We need support for the legacy PE draft since a large number of PEs in many service provider networks will never be able to support RFC 4684 since the code upgrade of these legacy PEs is not an option due to multiple reasons such as end-of-life scenarios or costly hardware upgrades.
- As a representative of a large service provider, our comment is that our provisioning systems are highly automated and should easily be able to make the provisioning changes needed to specify RT membership information on the legacy PEs during the VRF configuration with no additional risk to our customer traffic.
- The VPNV4/VPNV6 RRs in our network are considered core infrastructure devices that should NOT be exposed to daily provisioning activity that the manual addition of filters to the core RR would require.

Luis Tomotaki
Verizon PIP
Senior Engineer - Network Planning

On Nov 16, 2011, at 5:04 PM, "John Scudder" <jgs at juniper.net> wrote:

> Folks,
>
> We have received a request from the authors to adopt draft-l3vpn-legacy-rtc-00 as an IDR WG document.  Please send your comments to the list.  The deadline for comments is December 5, 2011 at noon EST.
>
> Thanks,
>
> --John
> _______________________________________________
> Idr mailing list
> Idr at ietf.org
> https://www.ietf.org/mailman/listinfo/idr