IETF Logo Mail Archive

Re: [Mpls-interop] MPLS over MPLS-TP

"Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> Thu, 11 December 2008 19:17 UTC

Return-Path: <mpls-interop-bounces@ietf.org>
X-Original-To: mpls-interop-archive@ietf.org
Delivered-To: ietfarch-mpls-interop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58BF93A67D2; Thu, 11 Dec 2008 11:17:04 -0800 (PST)
X-Original-To: mpls-interop@core3.amsl.com
Delivered-To: mpls-interop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 885223A688A for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 11:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.804
X-Spam-Level:
X-Spam-Status: No, score=-5.804 tagged_above=-999 required=5 tests=[AWL=0.795, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JKUjXQTmYp2u for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 11:17:02 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 6E5A43A67D2 for <mpls-interop@ietf.org>; Thu, 11 Dec 2008 11:17:02 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id mBBJGp3J009546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 11 Dec 2008 20:16:51 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id mBBJGpjB004676; Thu, 11 Dec 2008 20:16:51 +0100
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Dec 2008 20:16:51 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 11 Dec 2008 20:16:50 +0100
Message-ID: <43284B5A95E36B4AB4A91EBA4E0FC31E010631E9@DEMUEXC030.nsn-intra.net>
In-Reply-To: <51661468CBD1354294533DA79E85955A015375C0@XCH-SW-5V2.sw.nos.boeing.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mpls-interop] MPLS over MPLS-TP
Thread-Index: AclbGFKaGGhxsocFx0ysGuEoM9LmMAAmK2cgAAAT9yAAAN7LAA==
References: <49392C0B.4090202@chello.nl><C565F5E6.F2C5%benjamin.niven-jenkins@bt.com> <43284B5A95E36B4AB4A91EBA4E0FC31E010631AC@DEMUEXC030.nsn-intra.net> <51661468CBD1354294533DA79E85955A015375C0@XCH-SW-5V2.sw.nos.boeing.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Drake, John E" <John.E.Drake2@boeing.com>, "ext Ben Niven-Jenkins" <benjamin.niven-jenkins@bt.com>, <mpls-interop@ietf.org>
X-OriginalArrivalTime: 11 Dec 2008 19:16:51.0201 (UTC) FILETIME=[05473F10:01C95BC5]
Subject: Re: [Mpls-interop] MPLS over MPLS-TP
X-BeenThere: mpls-interop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF MPLS Interoperability Design Team <mpls-interop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls-interop>
List-Post: <mailto:mpls-interop@ietf.org>
List-Help: <mailto:mpls-interop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-interop-bounces@ietf.org
Errors-To: mpls-interop-bounces@ietf.org

Well there is a difference, named control word. Also for OAM, with or
with out GALs.

-----Original Message-----
From: ext Drake, John E [mailto:John.E.Drake2@boeing.com] 
Sent: Thursday, December 11, 2008 19:02
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); ext Ben Niven-Jenkins;
mpls-interop@ietf.org
Subject: RE: [Mpls-interop] MPLS over MPLS-TP

 

>-----Original Message-----
>From: Sprecher, Nurit (NSN - IL/Hod HaSharon) 
>[mailto:nurit.sprecher@nsn.com] 
>Sent: Thursday, December 11, 2008 8:55 AM
>To: ext Ben Niven-Jenkins; mpls-interop@ietf.org
>Subject: Re: [Mpls-interop] MPLS over MPLS-TP
>
>The first option also allows you to have better trouble 
>shooting in case of a problem (thanks to the clear separation).

JD:  Regardless of whether you have MPLS TP/PW/MPLS *or* MPLS TP/MPLS,
you will have two label stacks.  The only difference is whether the last
label in the provider's stack is an PW label *or* an MPLS label.  This
was the point in Andy's first e-mail, which as I read it, said that
there was nothing magic about that label being a PW label.
 
>
>-----Original Message-----
>From: mpls-interop-bounces@ietf.org
>[mailto:mpls-interop-bounces@ietf.org] On Behalf Of ext Ben 
>Niven-Jenkins
>Sent: Thursday, December 11, 2008 00:41
>To: mpls-interop@ietf.org
>Subject: [Mpls-interop] MPLS over MPLS-TP
>
>Colleagues,
>
>What's the current view of how to support MPLS over MPLS-TP?
>
>Do we put a PW in the middle (like draft-bryant) or do we just 
>use the label stack and have MPLS directly over MPLS-TP?
>
>Advantage of the first is that it gives layer separation (e.g. 
>If the two layers are operated by different parties), 
>advantage of the second is it's probably a bit simpler.
>
>Do the drafts we have say anything about the MPLS over MPLS-TP case?
>Same
>for IP over MPLS-TP?
>
>Thanks
>Ben
>
>_______________________________________________
>Mpls-interop mailing list
>Mpls-interop@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls-interop
>_______________________________________________
>Mpls-interop mailing list
>Mpls-interop@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls-interop
>
_______________________________________________
Mpls-interop mailing list
Mpls-interop@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-interop

v2.8.7 | Report a Bug | By Email