IETF Logo Mail Archive

[Mpls-interop] MPLS over MPLS-TP

Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com> Wed, 10 December 2008 22:40 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 C9D883A683D; Wed, 10 Dec 2008 14:40:50 -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 9EFEF3A683D for <mpls-interop@core3.amsl.com>; Wed, 10 Dec 2008 14:40:49 -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 iZ76-OYmiN7Y for <mpls-interop@core3.amsl.com>; Wed, 10 Dec 2008 14:40:49 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id AD3193A6973 for <mpls-interop@ietf.org>; Wed, 10 Dec 2008 14:40:48 -0800 (PST)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.111]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 10 Dec 2008 22:40:39 +0000
Received: from 217.32.164.172 ([217.32.164.172]) by E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via Exchange Front-End Server mail.bt.com ([193.113.197.26]) with Microsoft Exchange Server HTTP-DAV ; Wed, 10 Dec 2008 22:40:39 +0000
User-Agent: Microsoft-Entourage/12.14.0.081024
Date: Wed, 10 Dec 2008 22:40:38 +0000
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: <mpls-interop@ietf.org>
Message-ID: <C565F5E6.F2C5%benjamin.niven-jenkins@bt.com>
Thread-Topic: MPLS over MPLS-TP
Thread-Index: AclbGFKaGGhxsocFx0ysGuEoM9LmMA==
In-Reply-To: <49392C0B.4090202@chello.nl>
Mime-version: 1.0
X-OriginalArrivalTime: 10 Dec 2008 22:40:40.0078 (UTC) FILETIME=[53D80AE0:01C95B18]
Subject: [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

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

v2.8.7 | Report a Bug | By Email