Re: CE-based VPLS

Kireeti Kompella <kireeti@juniper.net> Sun, 20 July 2003 23:40 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01078 for <l2vpn-archive@odin.ietf.org>; Sun, 20 Jul 2003 19:40:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eNmp-0005uw-Q1 for l2vpn-archive@odin.ietf.org; Sun, 20 Jul 2003 19:40:15 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6KNeFcZ022742 for l2vpn-archive@odin.ietf.org; Sun, 20 Jul 2003 19:40:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eNmp-0005uj-LZ for l2vpn-web-archive@optimus.ietf.org; Sun, 20 Jul 2003 19:40:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01067 for <l2vpn-web-archive@ietf.org>; Sun, 20 Jul 2003 19:40:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eNmo-0005w4-00 for l2vpn-web-archive@ietf.org; Sun, 20 Jul 2003 19:40:14 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19eNmi-0005vu-00 for l2vpn-web-archive@ietf.org; Sun, 20 Jul 2003 19:40:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eNmb-0005tY-Ic; Sun, 20 Jul 2003 19:40:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eNlo-0005sr-CA for l2vpn@optimus.ietf.org; Sun, 20 Jul 2003 19:39:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01058 for <l2vpn@ietf.org>; Sun, 20 Jul 2003 19:39:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eNlm-0005vk-00 for l2vpn@ietf.org; Sun, 20 Jul 2003 19:39:10 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net) by ietf-mx with esmtp (Exim 4.12) id 19eNlb-0005vO-00 for l2vpn@ietf.org; Sun, 20 Jul 2003 19:38:59 -0400
Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h6KNc4u74905; Sun, 20 Jul 2003 16:38:04 -0700 (PDT) (envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost) by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h6KNc4D29021; Sun, 20 Jul 2003 16:38:04 -0700 (PDT) (envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Sun, 20 Jul 2003 16:38:04 -0700
From: Kireeti Kompella <kireeti@juniper.net>
To: Cheng-Yin Lee <Cheng-Yin.Lee@alcatel.com>
cc: l2vpn@ietf.org
Subject: Re: CE-based VPLS
In-Reply-To: <3F16F8A9.8126E8C1@alcatel.com>
Message-ID: <20030720155356.A28944@kummer.juniper.net>
References: <3F16F8A9.8126E8C1@alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: l2vpn-admin@ietf.org
Errors-To: l2vpn-admin@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l2vpn.ietf.org>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>

Hi Cheng-Lin,

On Thu, 17 Jul 2003, Cheng-Yin Lee wrote:

> The L2VPN charter states
> "The WG is responsible for standardization of the following solutions:
> 1. Virtual Private LAN Service (VPLS)--L2 service that emulates LAN
>   across an IP and an MPLS-enabled IP network, allowing standard
>   Ethernet devices communicate with each other as if they were
>   connected to a common LAN segment.
> ...
> "
>
> This is the service that CE-based VPLS (where CE is provisioned by
> provider) provides.

It would be interesting (but ultimately irrelevant) to understand how
you made the leap from "service that emulates LAN" to "CE-based VPLS
... where CE is provisioned by provider".  The charter does not say who
provisions the VPLS, although since L2VPN emerged from PPVPN, it seems
logical that the provider provisions it.  Furthermore, the charter
doesn't mention "CE-based".

If by "CE", you mean (as in rfc2547bis) a device owned, operated and
managed by the customer, then "CE provisioned by the provider" is an
oxymoron.  If you mean something else, it would be useful to define it;
and furthermore, to read the decoupled VPLS and the H-VPLS drafts.

> So I think CE-based VPLS is within the scope of the L2VPN
> charter (unless the charter is changed to explicitly exclude CE-based
> VPLS).

The parenthetical statement is not a bad idea.  Chairs?  ADs?

> I believe the following drafts do not currently allow standard Ethernet
> devices to communicate with each other as if they were connected to a
> common LAN segment:
> http://www.ietf.org/internet-drafts/draft-ietf-ppvpn-vpls-ldp-00.txt
> http://www.ietf.org/internet-drafts/draft-ietf-ppvpn-vpls-bgp-00.txt
> http://www.ietf.org/internet-drafts/draft-radoaca-ppvpn-gvpls-02.txt
> http://www.ietf.org/internet-drafts/draft-shah-ppvpn-ipls-02.txt

There is an existence proof that most (if not all) of the above _do_
in fact allow standard Ethernet devices to communicate with each other
as if they were on a LAN.  So, your belief does not jive with reality.
Step into any number of vendor or provider labs for proof.

If there are corner cases where the "VPLS" in the above drafts fails
to emulate a LAN perfectly, please communicate that to the group.
This would be productive, and help the group understand whether the
failure was systemic or the artifact of particular implementations,
and thus guide further standards development.

Kireeti.