Re: Ask for comments on "draft-zhang-l2vpn-vpls-bd-tagging-01.txt"

[Jeff Tantsura <[e-mail]>]

I fully subscribe to Jim's point of view.

Cheers,
Jeff


-----Original Message-----
From: <UTTARO>, JAMES <[e-mail]>
Date: Friday, February 21, 2014 3:27 AM
To: Mingui Zhang <[e-mail]>om>, "[e-mail]"
<[e-mail]>
Subject: RE: Ask for comments on "draft-zhang-l2vpn-vpls-bd-tagging-01.txt"

>The assumption being that the majority of customer are building more than
>a two or three point VPLS domain.. My experience does not indicate that
>VPLS is a service that supports many endpoints per VPLS VPN. Anyway why
>not simply use EVPN for this purpose? There are no PWs,  traffic
>traverses the same LSPs used for any other service.
>
>Jim Uttaro
>
>-----Original Message-----
>From: L2vpn [mailto:[e-mail]] On Behalf Of Mingui Zhang
>Sent: Friday, February 21, 2014 3:39 AM
>To: [e-mail]
>Subject: Ask for comments on "draft-zhang-l2vpn-vpls-bd-tagging-01.txt"
>
>Hi,
>
>Service providers are facing a heavy provisioning overhead in VPLS since
>a mass of PWs need to be maintained. If PEs can use Customer VLAN ID as a
>service discriminator in VPLS, the required number of PWs will be greatly
>reduced. Therefore, the provision overhead can be significantly relieved.
>
>Authors compose the draft to justify the solutions on recognizing
>Customer VLAN IDs in VPLS. We wish to receive your comments and
>suggestions. 
>
>Thanks,
>Mingui
>
>>-----Original Message-----
>>From: I-D-Announce [mailto:[e-mail]] On Behalf Of
>>[e-mail]
>>Sent: Friday, February 14, 2014 5:10 PM
>>To: [e-mail]
>>Subject: I-D Action: draft-zhang-l2vpn-vpls-bd-tagging-01.txt
>>
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts
>>directories.
>>
>>
>>        Title           : Tagging Customer Bridge Domains in VPLS
>>        Authors         : Mingui Zhang
>>                          Bin Wang
>>                          Liang Xia
>>                          Jie Hu
>>	Filename        : draft-zhang-l2vpn-vpls-bd-tagging-01.txt
>>	Pages           : 8
>>	Date            : 2014-02-14
>>
>>Abstract:
>>   This document proposes to use Customer VLAN ID as a identifier for
>>   traffic isolation in Virtual Private LAN Service (VPLS). In this way,
>>   multiple bridge domains of customers can share a single VPLS instance
>>   while their traffic are separated. With this proposal, Service
>>   Providers can be relieved from the heavy provisioning overhead of
>>   large number of pseudowires in the environment where a mass of bridge
>>   domains need be connected.
>>
>>
>>The IETF datatracker status page for this draft is:
>>https://datatracker.ietf.org/doc/draft-zhang-l2vpn-vpls-bd-tagging/
>>
>>There's also a htmlized version available at:
>>http://tools.ietf.org/html/draft-zhang-l2vpn-vpls-bd-tagging-01
>>
>>A diff from the previous version is available at:
>>http://www.ietf.org/rfcdiff?url2=draft-zhang-l2vpn-vpls-bd-tagging-01
>>
>>
>>Please note that it may take a couple of minutes from the time of
>>submission until the htmlized version and diff are available at
>>tools.ietf.org.
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>I-D-Announce mailing list
>>[e-mail]
>>https://www.ietf.org/mailman/listinfo/i-d-announce
>>Internet-Draft directories: http://www.ietf.org/shadow.html or
>>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>