draft-sajassi-l2vpn-vpls-bridge-interop-03?

"Vach Kompella" <vach.kompella@alcatel.com> Thu, 20 July 2006 21:12 UTC

From: Vach Kompella <vach.kompella@alcatel.com>
To: anilr@accton.com, l2vpn@ietf.org
Date: Thu, 20 Jul 2006 14:10:52 -0700
Message-ID: <080501c6ac40$fc3a2030$cab816ac@eng.timetra.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
In-reply-to: <OF2EAAECAE.62531690-ON852571B1.00704B1B@accton.com>
Importance: Normal
Cc:
Subject: draft-sajassi-l2vpn-vpls-bridge-interop-03?
Precedence: list
Errors-To: l2vpn-bounces@ietf.org

Hi Anil,

I assume the draft you are referring to is
draft-sajassi-l2vpn-vpls-bridge-interop-03.

Thanks for your comments.  Please see below for clarifications on the
purpose of this draft.

-Vach 

> -----Original Message-----
> From: anilr@accton.com [mailto:anilr@accton.com] 
> Sent: Thursday, July 20, 2006 1:40 PM
> To: l2vpn@ietf.org
> Subject: Re: Draft minutes of L2VPN WG meeting @ IETF 66 
> (Montreal, Quebec,Canada)
> 
> 
> 
> This document discusses interoperability issues with 
> standards-based customer bridging which likely needs to be 
> resolved for different vendors equipment to work together. It 
> would be a useful WG document.
> 
> Is it intended as an informational or standard document?

It is not a standards track document.  It will be an informational
document.

> 
> I would note that it appears to be a work in progress. 

All working group documents are still work-in-progress.

> Mention is made of several interoperability issues which are 
> not addressed one way or another, e.g. how should various 
> "slow" 802 protocols be dealt with? The answer may be 
> different for different existing protocols, and may be 
> different for unrecognized protocols.

This draft will only capture the issues, and may also include the
complexities of the problems such as those you mention, but will not
present solutions for them.

> 
> In addition, reference is made to non-standard mechanisms, 
> one example being a partial-mesh method that is not part of 
> the base VPLS architecture. I would suggest such issues be 
> resolved before putting them in a WG document, i.e, either 
> bring partial meshing into VPLS or remove reference to it.

The draft attempts to capture the ways in which a VPLS is not a perfect
emulation of ethernet bridging.  Solutions that are presented for these
issues do not invalidate the status of this draft, since it refers to
the basic VPLS solutions.  The partial mesh issue, for example, is noted
as a potential issue for VPLS, and is hence a perfect candidate for
inclusion in this draft.

> 
> Regards,
> Anil
> 
>

Draft minutes of L2VPN WG meeting @ IETF 66 (Mont… Shane Amante
Re: Draft minutes of L2VPN WG meeting @ IETF 66 (… Thomas D. Nadeau
Re: Draft minutes of L2VPN WG meeting @ IETF 66 (… anilr
draft-sajassi-l2vpn-vpls-bridge-interop-03? Vach Kompella