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

"Drake, John E" <John.E.Drake2@boeing.com> Thu, 11 December 2008 14:59 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 AF9453A6782; Thu, 11 Dec 2008 06:59:24 -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 272693A6C19 for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 06:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level:
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 o2JznQUFv7ns for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 06:59:22 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 455313A6782 for <mpls-interop@ietf.org>; Thu, 11 Dec 2008 06:59:22 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id mBBEwmkG025780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Dec 2008 06:58:49 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id mBBEwmbF010895; Thu, 11 Dec 2008 06:58:48 -0800 (PST)
Received: from xch-swbh-11.sw.nos.boeing.com (xch-swbh-11.sw.nos.boeing.com [129.172.192.157]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id mBBEwm2i010888; Thu, 11 Dec 2008 06:58:48 -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 06:58:48 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 11 Dec 2008 06:58:47 -0800
Message-ID: <51661468CBD1354294533DA79E85955A0153752E@XCH-SW-5V2.sw.nos.boeing.com>
In-Reply-To: <01F652C8CDBE7D4EB7ED860698C6D97332DA50@FHDP1LUMXCV24.us.one.verizon.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mpls-interop] MPLS over MPLS-TP
Thread-Index: AclbfJC1yxFkbGGYTbuRnPmiqs13rQAFWwLwAANkyCA=
References: <49392C0B.4090202@chello.nl><C565F5E6.F2C5%benjamin.niven-jenkins@bt.com><51661468CBD1354294533DA79E85955A01537442@XCH-SW-5V2.sw.nos.boeing.com> <EBDD51571B3544C482232351C09FAA37@your029b8cecfe> <01F652C8CDBE7D4EB7ED860698C6D97332DA50@FHDP1LUMXCV24.us.one.verizon.com>
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: "Malis, Andrew G. (Andy)" <andrew.g.malis@verizon.com>, "Adrian Farrel" <adrian@olddog.co.uk>, "Ben Niven-Jenkins" <benjamin.niven-jenkins@bt.com>, <mpls-interop@ietf.org>
X-OriginalArrivalTime: 11 Dec 2008 14:58:48.0220 (UTC) FILETIME=[F8B3D5C0:01C95BA0]
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

Snipped, comment inline 

>1. What is the service provided by an MPLS-TP network?
>Is it (as described in some documents) the provision of 
>pseudowires over an MPLS transport network?
>Or is it the provision of services (including pseudowires) 
>over an MPLS transport network?
>
>AM> My preference is the latter - it should be more general than just
>the provisioning of pseudowires (even if we have IP and MPLS 
>pseudowires). A PW is an instance of a label in the stack, and 
>what can be transported over MPLS-TP shouldn't be limited to 
>just that instance.

JD:  I agree

>
>3. If there is demarcation as suggested in point 2, what is 
>the best way to provide demarcation?
>a. Encode as a PW with the end of stack set and a PW header 
>according to the appropriate PW encoding type.
>b. Simply use the end of stack bit to say that we have reached 
>the bottom of the MPLS-TP label stack.
>(The alternative clearly being that the label stack runs 
>through from the client label stack to the server label stack.)
>
>AM> I prefer b, for simplicity and generality of what can be carried
>over MPLS-TP. Thus we could have a label stack with two EOS bits set. 
>
>AM> Also, regarding the possible misconfiguration discussed in question
>2, this could happen with PW labels as easily as with non-PW 
>labels, so requiring PWs to be used with MPLS-TP is no 
>panacea. Rather, this sort of misconfiguration needs to be 
>detected using OAM and other MPLS-TP layer management mechanisms.

JD:  I agree with your point about PW labels, but doesn't the same point
apply to the label stack with two EOS bits?  Viz, having the EOS bit set
will not prevent an implementation from messing up the stack in
arbitrary and capricious ways.

Isn't another alternative to just have the MPLS TP network be completely
agnostic to the contents of its payloads, as a server layer is supposed
to be?
In that case, the payload could in fact be an MPLS payload with its own
stack.

>
>Cheers,
>Andy
>
>
_______________________________________________
Mpls-interop mailing list
Mpls-interop@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-interop