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

"Drake, John E" <John.E.Drake2@boeing.com> Wed, 10 December 2008 22:49 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 D1E733A6983; Wed, 10 Dec 2008 14:49:02 -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 9122C28C1EA for <mpls-interop@core3.amsl.com>; Wed, 10 Dec 2008 14:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level:
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[AWL=0.062, 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 RbAe-liM3l8i for <mpls-interop@core3.amsl.com>; Wed, 10 Dec 2008 14:49:00 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id A488F3A6983 for <mpls-interop@ietf.org>; Wed, 10 Dec 2008 14:49:00 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id mBAMmkfO007847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 10 Dec 2008 14:48:49 -0800 (PST)
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 mBAMmk73027949; Wed, 10 Dec 2008 14:48:46 -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 mBAMmetv027708; Wed, 10 Dec 2008 14:48:46 -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); Wed, 10 Dec 2008 14:48:40 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 10 Dec 2008 14:48:39 -0800
Message-ID: <51661468CBD1354294533DA79E85955A01537442@XCH-SW-5V2.sw.nos.boeing.com>
In-Reply-To: <C565F5E6.F2C5%benjamin.niven-jenkins@bt.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mpls-interop] MPLS over MPLS-TP
Thread-Index: AclbGFKaGGhxsocFx0ysGuEoM9LmMAAAGzpQ
References: <49392C0B.4090202@chello.nl> <C565F5E6.F2C5%benjamin.niven-jenkins@bt.com>
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: "Ben Niven-Jenkins" <benjamin.niven-jenkins@bt.com>, <mpls-interop@ietf.org>
X-OriginalArrivalTime: 10 Dec 2008 22:48:40.0876 (UTC) FILETIME=[726BFEC0:01C95B19]
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

 

>-----Original Message-----
>From: Ben Niven-Jenkins [mailto:benjamin.niven-jenkins@bt.com] 
>Sent: Wednesday, December 10, 2008 2:41 PM
>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?

JD:  I always thought this was a terrible idea.  Since MPLS-TP is a
particular MPLS profile and since we said that the MPLS dataplane
wouldn't be touched, I think we would either add entries to the stack
(MPLS), or place an IP packet after the stack (IP).

>
>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