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

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Fri, 21 February 2014 16:29 UTC

Return-Path: <sajassi@cisco.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 A68261A048B for <l2vpn@ietfa.amsl.com>; Fri, 21 Feb 2014 08:29:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level:
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 Vg5m0UxdFEZB for <l2vpn@ietfa.amsl.com>; Fri, 21 Feb 2014 08:29:28 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 93DA21A0466 for <l2vpn@ietf.org>; Fri, 21 Feb 2014 08:29:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4081; q=dns/txt; s=iport; t=1393000165; x=1394209765; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=Km2OcEaM06FuJsPUkCzEZstdvrLWMj/7S6F7XlX+J1o=; b=IHILMQDqSZLvAfs3A8Gp2Qkr/rzNWr+aHyjcvwW8tNnPOggi6URmQiSZ aOjUzYhgVyL+L7A/o4kM6V2MjFHFAC6oM75NPS8Z6RrbxcFY4Knnsliks BmID8ZN5hqgEkBrToTs3oTonsq8WM27XGkURvFO/FNqOShbW6WW6CYvWB k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFAA9+B1OtJV2c/2dsb2JhbABagmUhO1EGwD2BDhZ0giUBAQEEAQEBNzQXBgEIEQMBAQENEgkuCxQJCAEBBAESCRKHagEHBcthF445LQUGhDIEmDSBMosxhUSDLYIq
X-IronPort-AV: E=Sophos;i="4.97,520,1389744000"; d="scan'208";a="22212949"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-6.cisco.com with ESMTP; 21 Feb 2014 16:29:24 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s1LGTOPl026202 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Feb 2014 16:29:24 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Fri, 21 Feb 2014 10:29:23 -0600
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "UTTARO, JAMES" <ju1738@att.com>, 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/H9yqftdSB2s9awjRmSgCwAFtv5AAAQUXAAAAm4ggA==
Date: Fri, 21 Feb 2014 16:29:23 +0000
Message-ID: <CF2CBDEB.C0731%sajassi@cisco.com>
In-Reply-To: <CF2CBC6B.49244%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.21.69.231]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A0E7235E8B38CF479BEBDA67399C610B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/_V50M7ofORiOnhPfrfwE9uLRW1Q
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 16:29:30 -0000

Two points:

1) First vlan-aware bundle service is already supported in EVPN and per
Jim's suggestion "why not simply use EVPN".

2) Second, there is already a draft published about a year and half ago to
address this issue for VPLS :-)
http://tools.ietf.org/id/draft-cai-l2vpn-vpls-vlan-aware-bundling-00.txt

Cheers,
Ali



On 2/21/14 8:19 AM, "Jeff Tantsura" <jeff.tantsura@ericsson.com> wrote:

>I fully subscribe to Jim's point of view.
>
>Cheers,
>Jeff
>
>
>-----Original Message-----
>From: <UTTARO>, JAMES <ju1738@att.com>
>Date: Friday, February 21, 2014 3:27 AM
>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"
>
>>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
>>
>