RE: draft-sajassi-l2vpn-vpls-bridge-interop-03?
"Ali Sajassi \(sajassi\)" <sajassi@cisco.com> Tue, 25 July 2006 23:19 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5WBH-0003Gd-3V; Tue, 25 Jul 2006 19:19:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5WBF-0003Et-HR for l2vpn@ietf.org; Tue, 25 Jul 2006 19:19:13 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5WBD-0007V0-6V for l2vpn@ietf.org; Tue, 25 Jul 2006 19:19:13 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 25 Jul 2006 16:19:10 -0700
X-IronPort-AV: i="4.07,181,1151910000"; d="scan'208"; a="1841757497:sNHT24821714"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6PNJAi1022296; Tue, 25 Jul 2006 16:19:10 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k6PNJA2F024611; Tue, 25 Jul 2006 16:19:10 -0700 (PDT)
Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Jul 2006 16:19:09 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Jul 2006 16:19:08 -0700
Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB01DC33E5@xmb-sjc-21e.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-sajassi-l2vpn-vpls-bridge-interop-03?
Thread-Index: AcawGKkdoAKx7UiTTCifqsxv5SVQ/AAJRDPw
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: anilr@accton.com, Vach Kompella <vach.kompella@alcatel.com>
X-OriginalArrivalTime: 25 Jul 2006 23:19:10.0074 (UTC) FILETIME=[BBBCB5A0:01C6B040]
DKIM-Signature: a=rsa-sha1; q=dns; l=677; t=1153869550; x=1154733550; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sajassi@cisco.com; z=From:=22Ali=20Sajassi=20\(sajassi\)=22=20<sajassi@cisco.com> |Subject:RE=3A=20draft-sajassi-l2vpn-vpls-bridge-interop-03?; X=v=3Dcisco.com=3B=20h=3D5U+Ua0D9Y2AetWy67AyM8iLfJAQ=3D; b=HJNCcnUGbNk14eYgpZEoEZfRMU2IuUHWLeo/JJ4prZrH04sX4I9plY4CkdMyBU1IKsaEY2Zr ESbTP7a+mKuudIJzvCj5lcCZffTW3U97W/kQ/hM/NPDGqwCLwdQp/Ogr;
Authentication-Results: sj-dkim-1.cisco.com; header.From=sajassi@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: l2vpn@ietf.org
Subject: RE: draft-sajassi-l2vpn-vpls-bridge-interop-03?
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l2vpn-bounces@ietf.org
Anil, > 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. Please refer to section 4.2 of the draft that talks about how different customer bridge protocols should be handled by the PE using the 802.1ad bridge module as the front-end model for interfacing with customer interfaces. The idea in here is to show how some of the IEEE work can be leveraged to address some of these bridge interoperability issues. -Ali
- Re: draft-sajassi-l2vpn-vpls-bridge-interop-03? anilr
- RE: draft-sajassi-l2vpn-vpls-bridge-interop-03? Ali Sajassi (sajassi)