Re: RE: About IS-IS as the PE/CE Protocol in BGP/MPLS VPNs (43834 bytes)

[lidefeng <[e-mail]>]

I read the L3vpn wg charter, I didn't find any statement that ISIS as a pe-ce routing protocol for BGP/MPLS VPN, just like it didn't explictly state that OSPF as a pe-ce routing protocol for BGP/MPLS VPN, and draft-ietf-l3vpn-ospf-2547-01.txt
is a WG draft, and there is no explict statement of including PE-PE GRE or IP in BGP/MPLS IP VPNs in L3VPN wg charter, and draft-ietf-l3vpn-gre-ip-2547-02.txt is a wg draft too, what's more, now that this topic is out of scope of l3vpn wg charter, how come this draft was arranged for presentation? 

And IS-IS is deployed in some scenarios, such as some enterprise network, and when two such enterprise networks would like to access service provider to apply BGP/MPLS VPN service between this two sites, if use IS-IS as PE-CE routing protocol, it will be much easier for these enterprise networks customer to transition from the previous network without changing the routing protocol in the original network.

In some service providers, the IS-IS is prefered for its advantage in its compatibility between IPv4 and IPv6 so as to transit their VPN easily, as I mentioned in my last e-mail, IS-ISv6 can be supported easily by adding two TLVs to IS-ISv4, however, if OSPFv2 is deployed as CE-PE routing, when VPN customer hope to transit customer network from IPv4 to IPv6, then he would deploy OSPFv3 in their network, as OSPFv3 is not compatible with OSPFv2, in fact, they may be looked upon as two different routing protocol, so this transition will bring some impact to cutomer's network. In this regard, some service provider would prefer IS-IS as CE-PE routing protocol in BGP/MPLS VPN.

In other words, IS-IS as the PE-CE routing protocol give the service provider an alternative to choose the PE-CE routing protocol, though is not an indispensable choice, it just provide guide line for service provider when he choose IS-IS as PE-CE routing protocol, and its goal is to be progressed into an informational RFC, not a standard track RFC which demand the complete abservation. So why not accept this subject in L3VPN WG charter?

As draft-sheng will address the problem when IS-IS is used as PE-CE routing protocol, and there are some requirements from some service providers in some scenarios. so I hope chairs can reconsider to make the progress to this draft.


 





	


 




>Defeng,
>
>Currently, the L3VPN WG charter does not include ISIS as a PE-CE routing
>protocol. However, I would like to open the mailing list to discussion.
>
>Is there a compelling reason to deploy ISIS as a PE-CE routing protocol, as
>opposed to BGP or OSPF? Also, I would like to determine whether there is
>broad WG interest in this work.
>
>                                              Ron
>
>
>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]] 
>> On Behalf Of lidefeng
>> Sent: Thursday, September 02, 2004 5:13 AM
>> To: [e-mail]; Ronald Bonica; Ross Callon
>> Cc: [e-mail]
>> Subject: About IS-IS as the PE/CE Protocol in BGP/MPLS VPNs 
>> (43834 bytes)
>> 
>> 
>> Dear Chairmen,
>> 
>> At 57th IETF meeting, I made the presentation for 
>> draft-sheng-ppvpn-isis-bgp-mpls-00.txt at PPVPN wg meeting 
>> and proposed the draft about "IS-IS as the PE/CE Protocol in 
>> BGP/MPLS VPNs" as work group draft, now PPVPN wg is divided 
>> into L3VPN and L2VPN, at the same time, draft "OSPF as the 
>> PE/CE Protocol in BGP/MPLS VPNs " is progressed as L3VPN wg, 
>> and IS-IS as an alternate IGP in SP's network and 
>> enterprise's network has its advantages over OSPF, especially 
>> in IPv6 and Traffic Engineering scenarios(OSPFv3 can't be 
>> compatibility with OSPFv2，while IS-ISv6 can be updated from 
>> IS-ISv4 by TLV extensiona), and IS-IS gained its wide 
>> deployment gradually.
>> 
>> So I hope L3VPN wg consider to progress 
>> draft-sheng-ppvpn-isis-bgp-mpls-00.txt as WG draft, and it's 
>> goal is to become an informational RFC.
>> 
>> As to the technical problem might exist in it, comments are welcomed.
>> 
>> Regards
>> 
>> Defeng Li
>> Huawei Technologies
>> 
>> 
>> 
>
>.