IETF Logo Mail Archive

Re: [mpls-tp] MPLS over OTN

Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com> Tue, 12 August 2008 17:07 UTC

Return-Path: <owner-ccamp@ops.ietf.org>
X-Original-To: ietfarch-ccamp-archive@core3.amsl.com
Delivered-To: ietfarch-ccamp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 350723A67FE for <ietfarch-ccamp-archive@core3.amsl.com>; Tue, 12 Aug 2008 10:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.802
X-Spam-Level:
X-Spam-Status: No, score=-1.802 tagged_above=-999 required=5 tests=[AWL=-0.307, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_LOW=-1, RDNS_NONE=0.1]
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 NORXYdAiQi26 for <ietfarch-ccamp-archive@core3.amsl.com>; Tue, 12 Aug 2008 10:07:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 613943A6818 for <ccamp-archive@ietf.org>; Tue, 12 Aug 2008 10:07:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1KSxEL-000ML1-4B for ccamp-data@psg.com; Tue, 12 Aug 2008 17:00:21 +0000
Received: from [217.32.164.137] (helo=smtp1.smtp.bt.com) by psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from <benjamin.niven-jenkins@bt.com>) id 1KSxED-000MJz-Fq for ccamp@ops.ietf.org; Tue, 12 Aug 2008 17:00:18 +0000
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.111]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Aug 2008 18:00:10 +0100
Received: from 10.215.40.109 ([10.215.40.109]) by E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via Exchange Front-End Server mail.bt.com ([193.113.197.32]) with Microsoft Exchange Server HTTP-DAV ; Tue, 12 Aug 2008 16:59:52 +0000
User-Agent: Microsoft-Entourage/12.11.0.080522
Date: Tue, 12 Aug 2008 17:59:47 +0100
Subject: Re: [mpls-tp] MPLS over OTN
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: julien.meuric@orange-ftgroup.com, francesco.fondelli@gmail.com, maarten.vissers@huawei.com
CC: ccamp@ops.ietf.org, mpls-tp@ietf.org
Message-ID: <C4C78013.9DBE%benjamin.niven-jenkins@bt.com>
Thread-Topic: [mpls-tp] MPLS over OTN
Thread-Index: Acj2RzhHZYPvGZHKQvSW9uyhF8h+KQAAEiUwAZVUm78=
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02605C591F9@ftrdmel2>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 12 Aug 2008 17:00:10.0635 (UTC) FILETIME=[E1606DB0:01C8FC9C]
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
List-ID: <ccamp.ops.ietf.org>

Catching up on mails...


On 04/08/2008 16:48, "julien.meuric@orange-ftgroup.com"
<julien.meuric@orange-ftgroup.com> wrote:

> Hi Francesco.
> 
> I guess I understand your concern. I believe the original intention was
> to say implicitely "It MUST be possible to operate and configure the
> MPLS-TP data (transport) plane without any IP functionality *in the data
> plane*." My interpretation of these requirements is indeed that they
> apply to the MPLS-TP data plane only, not the MPLS-TP-capable equipment,
> nor the MPLS-TP control plane...

Correct.

> Anyway you're right, this could be confusing and it deserves a small
> rewording.

I have reworded to:
"It MUST be possible to operate and configure the MPLS-TP data (transport)
plane without any IP functionality in the MPLS-TP data plane."

Ben

v2.23.0 | Report a Bug | By Email