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

Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com> Thu, 11 December 2008 20:03 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 21E3B3A6C68; Thu, 11 Dec 2008 12:03:43 -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 A7CAF3A6A98 for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 12:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.532
X-Spam-Level:
X-Spam-Status: No, score=-1.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
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 vy-7X90m50Vr for <mpls-interop@core3.amsl.com>; Thu, 11 Dec 2008 12:03:41 -0800 (PST)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by core3.amsl.com (Postfix) with ESMTP id 132B43A6C6B for <mpls-interop@ietf.org>; Thu, 11 Dec 2008 12:03:30 -0800 (PST)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.111]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Dec 2008 20:03:21 +0000
Received: from 217.32.164.184 ([217.32.164.184]) by E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via Exchange Front-End Server mail.bt.com ([193.113.197.28]) with Microsoft Exchange Server HTTP-DAV ; Thu, 11 Dec 2008 20:03:21 +0000
User-Agent: Microsoft-Entourage/12.14.0.081024
Date: Thu, 11 Dec 2008 20:03:13 +0000
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: "Malis, Andrew G. (Andy)" <andrew.g.malis@verizon.com>, Adrian Farrel <adrian@olddog.co.uk>, "Drake, John E" <John.E.Drake2@boeing.com>, <mpls-interop@ietf.org>
Message-ID: <C5672281.F3E7%benjamin.niven-jenkins@bt.com>
Thread-Topic: [Mpls-interop] MPLS over MPLS-TP
Thread-Index: AclbfJC1yxFkbGGYTbuRnPmiqs13rQAFWwLwAARXiwcAADH0oAAJ1yjT
In-Reply-To: <01F652C8CDBE7D4EB7ED860698C6D97332DA7F@FHDP1LUMXCV24.us.one.verizon.com>
Mime-version: 1.0
X-OriginalArrivalTime: 11 Dec 2008 20:03:21.0783 (UTC) FILETIME=[84984470:01C95BCB]
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

Andy,


On 11/12/2008 15:31, "Malis, Andrew G. (Andy)" <andrew.g.malis@verizon.com>
wrote:
> AM> The intention would be that the MPLS-TP EOS bit would only be
> encountered at boundary the MPLS-TP network, and the payload would
> delivered to the client to do with as it desires (and expects), whether
> it's IP to forward, MPLS to switch using router-allocated labels, PW
> contents, or something else entirely. To the client, there should be no
> difference (at some layer of abstraction above the interface details)
> between using MPLS-TP for transport and POS or GFP encapsulation for
> transport.

Yes, but my concern is that IP & MPLS may well be 'recognised' in the
network core and if something happened (e.g. Erroneous label pop) to expose
them they could be forwarded natively in error.  Other traffic types are
unlikely to have this happen as the network core is unlikely to support
natively forwarding them.

Ben

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