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

"Drake, John E" <John.E.Drake2@boeing.com> Thu, 11 December 2008 19:23 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 8FCCE3A67DD; Thu, 11 Dec 2008 11:23:17 -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 346023A67FC for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 11:23:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level:
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.056, 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 o-dOzV2E3shm for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 11:23:15 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 51A983A67DD for <mpls-interop@ietf.org>; Thu, 11 Dec 2008 11:23:15 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id mBBJMrDv016107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 11 Dec 2008 13:22:59 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id mBBJMrKf009119; Thu, 11 Dec 2008 11:22:53 -0800 (PST)
Received: from xch-swbh-11.sw.nos.boeing.com (xch-swbh-11.sw.nos.boeing.com [129.172.192.157]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id mBBJMrdc009104; Thu, 11 Dec 2008 11:22:53 -0800 (PST)
Received: from XCH-SW-5V2.sw.nos.boeing.com ([129.172.193.50]) by xch-swbh-11.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Dec 2008 11:22:53 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 11 Dec 2008 11:22:51 -0800
Message-ID: <51661468CBD1354294533DA79E85955A0153768C@XCH-SW-5V2.sw.nos.boeing.com>
In-Reply-To: <43284B5A95E36B4AB4A91EBA4E0FC31E010631E9@DEMUEXC030.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mpls-interop] MPLS over MPLS-TP
Thread-Index: AclbGFKaGGhxsocFx0ysGuEoM9LmMAAmK2cgAAAT9yAAAN7LAAAEMfpQ
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> <43284B5A95E36B4AB4A91EBA4E0FC31E010631E9@DEMUEXC030.nsn-intra.net>
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "ext Ben Niven-Jenkins" <benjamin.niven-jenkins@bt.com>, <mpls-interop@ietf.org>
X-OriginalArrivalTime: 11 Dec 2008 19:22:53.0052 (UTC) FILETIME=[DCF553C0: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

Both the provider and the customer can independently run OAM, each using
their own label stack.   

>-----Original Message-----
>From: Sprecher, Nurit (NSN - IL/Hod HaSharon) 
>[mailto:nurit.sprecher@nsn.com] 
>Sent: Thursday, December 11, 2008 11:17 AM
>To: Drake, John E; ext Ben Niven-Jenkins; mpls-interop@ietf.org
>Subject: RE: [Mpls-interop] MPLS over MPLS-TP
>
>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