RE: Ask for comments on "draft-zhang-l2vpn-vpls-bd-tagging-01.txt"
"UTTARO, JAMES" <ju1738@att.com> Fri, 21 February 2014 11:27 UTC
Return-Path: <ju1738@att.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com
(Postfix) with ESMTP id CED701A0519 for <l2vpn@ietfa.amsl.com>;
Fri, 21 Feb 2014 03:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No,
score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyVk-9amuHPX for
<l2vpn@ietfa.amsl.com>; Fri, 21 Feb 2014 03:27:49 -0800 (PST)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com
[209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 81E401A04E9 for
<l2vpn@ietf.org>; Fri, 21 Feb 2014 03:27:49 -0800 (PST)
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by
nbfkord-smmo06.seg.att.com(mxl_mta-7.2.1-0) with ESMTP id
23837035.2b8702429940.2413577.00-2434.6805441.nbfkord-smmo06.seg.att.com
(envelope-from <ju1738@att.com>); Fri, 21 Feb 2014 11:27:46 +0000 (UTC)
X-MXL-Hash: 5307383219f05476-5cb545bc0d69232b1db9410ef44f0a2c66bcd8f8
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by
nbfkord-smmo06.seg.att.com(mxl_mta-7.2.1-0) over TLS secured channel with
ESMTP id 72837035.0.2413536.00-2336.6805316.nbfkord-smmo06.seg.att.com
(envelope-from <ju1738@att.com>); Fri, 21 Feb 2014 11:27:37 +0000 (UTC)
X-MXL-Hash: 530738296405ab08-b70666d7fab26169d24731d9a3fbf4c39bef5ffe
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by
alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s1LBRYgB025876;
Fri, 21 Feb 2014 06:27:34 -0500
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by
alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s1LBRRfS025844
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 21 Feb 2014 06:27:30 -0500
Received: from MISOUT7MSGHUB9B.ITServices.sbc.com
(MISOUT7MSGHUB9B.itservices.sbc.com [144.151.223.72]) by mlpi408.sfdc.sbc.com
(RSA Interceptor); Fri, 21 Feb 2014 11:27:20 GMT
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by
MISOUT7MSGHUB9B.ITServices.sbc.com ([144.151.223.72]) with mapi id
14.03.0174.001; Fri, 21 Feb 2014 06:27:20 -0500
From: "UTTARO, JAMES" <ju1738@att.com>
To: Mingui Zhang <zhangmingui@huawei.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: RE: Ask for comments on "draft-zhang-l2vpn-vpls-bd-tagging-01.txt"
Thread-Topic: Ask for comments on "draft-zhang-l2vpn-vpls-bd-tagging-01.txt"
Thread-Index: Ac8u4Gqu/H9yqftdSB2s9awjRmSgCwAFtv5A
Date: Fri, 21 Feb 2014 11:27:19 +0000
Message-ID: <B17A6910EEDD1F45980687268941550F0634CADE@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <4552F0907735844E9204A62BBDD325E73369FFF1@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E73369FFF1@nkgeml508-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.138.223]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=OL2QK1mB c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a]
X-AnalysisOut: [=4WijGsFk-CkA:10 a=ofMgfj31e3cA:10 a=F4jEe0iCTpwA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R]
X-AnalysisOut: [AAAA:8 a=8UtOOl-MPwsA:10 a=48vgC7mUAAAA:8 a=C3X6C57q9iJrDW]
X-AnalysisOut: [cCum8A:9 a=CjuIK1q_8ugA:10 a=jM_x9b4JT8QA:10 a=lZB815dzVvQ]
X-AnalysisOut: [A:10 a=8y2B7u0mA38moT9-:21 a=EesadEb-C9qjkY5j:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <ju1738@att.com>
X-SOURCE-IP: [144.160.229.24]
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/ZqRTEdZK35mDBoi697iaG_IAVfA
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>,
<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
<mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 11:27:52 -0000
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:l2vpn-bounces@ietf.org] On Behalf Of Mingui Zhang Sent: Friday, February 21, 2014 3:39 AM To: l2vpn@ietf.org 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:i-d-announce-bounces@ietf.org] On Behalf Of >internet-drafts@ietf.org >Sent: Friday, February 14, 2014 5:10 PM >To: i-d-announce@ietf.org >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 >I-D-Announce@ietf.org >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
- Ask for comments on "draft-zhang-l2vpn-vpls-bd-ta… Mingui Zhang
- RE: Ask for comments on "draft-zhang-l2vpn-vpls-b… UTTARO, JAMES
- Re: Ask for comments on "draft-zhang-l2vpn-vpls-b… Jeff Tantsura
- Re: Ask for comments on "draft-zhang-l2vpn-vpls-b… Ali Sajassi (sajassi)
- RE: Ask for comments on "draft-zhang-l2vpn-vpls-b… Mingui Zhang