IETF Logo Mail Archive

RE: [mpls-tp] MPLS over OTN

"Lam, Hing-Kam \(Kam\)" <hklam@alcatel-lucent.com> Mon, 04 August 2008 18:36 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 5858E3A6BD6 for <ietfarch-ccamp-archive@core3.amsl.com>; Mon, 4 Aug 2008 11:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.547
X-Spam-Level:
X-Spam-Status: No, score=-1.547 tagged_above=-999 required=5 tests=[AWL=-1.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 X09SCgwEnFaJ for <ietfarch-ccamp-archive@core3.amsl.com>; Mon, 4 Aug 2008 11:36:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6127A3A6824 for <ccamp-archive@ietf.org>; Mon, 4 Aug 2008 11:36:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1KQ4qH-000ADf-4K for ccamp-data@psg.com; Mon, 04 Aug 2008 18:31:37 +0000
Received: from [135.245.0.35] (helo=ihemail2.lucent.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <hklam@alcatel-lucent.com>) id 1KQ4qD-000AD2-9t for ccamp@ops.ietf.org; Mon, 04 Aug 2008 18:31:35 +0000
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m74IVOo9014890; Mon, 4 Aug 2008 13:31:25 -0500 (CDT)
Received: from ILEXC2U03.ndc.lucent.com ([135.3.39.11]) by ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Aug 2008 13:31:24 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls-tp] MPLS over OTN
Date: Mon, 04 Aug 2008 13:31:24 -0500
Message-ID: <A37753B7B7A3134F9366EE6B4052F43B01DB9F04@ILEXC2U03.ndc.lucent.com>
In-Reply-To: <022e01c8f65d$cce76f90$63466297@vim.tlt.alcatel.it>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls-tp] MPLS over OTN
Thread-Index: Acj2SyOUHLaTSfOxR92M5/JXYSVBKwAEb4AwAACvwtA=
References: <7c923b5e0808040600j6b470e5bjbfd17b306533fcb6@mail.gmail.com><006501c8f63e$56490390$8902a8c0@china.huawei.com><7c923b5e0808040831w757b6a76xfed5fc18bf7a11f8@mail.gmail.com><7DBAFEC6A76F3E42817DF1EBE64CB02605C591F9@ftrdmel2><7c923b5e0808040859u58a0d2d0k31c30bd28a49e3a1@mail.gmail.com> <022e01c8f65d$cce76f90$63466297@vim.tlt.alcatel.it>
From: "Lam, Hing-Kam (Kam)" <hklam@alcatel-lucent.com>
To: Italo Busi <italo.busi@alcatel-lucent.it>, Francesco Fondelli <francesco.fondelli@gmail.com>, julien.meuric@orange-ftgroup.com
Cc: ccamp@ops.ietf.org, mpls-tp@ietf.org
X-OriginalArrivalTime: 04 Aug 2008 18:31:24.0674 (UTC) FILETIME=[4CDA7E20:01C8F660]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
List-ID: <ccamp.ops.ietf.org>

Dear all,

Julien's proposed rephrase is good.

By the way, DCN requirements (more specifically Management Communication
Network (MCN) requirements) are already described in
draft-gray-mpls-tp-nm-req-00.txt. Of course comments for improvement are
always welcome.

Regards,
Kam

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
Behalf Of Italo Busi
Sent: Monday, August 04, 2008 2:14 PM
To: 'Francesco Fondelli'; julien.meuric@orange-ftgroup.com
Cc: ccamp@ops.ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] MPLS over OTN

I think that Julien's proposed rephrase better describes the requirement
so I
support it.

It is worth noticing that in case of static configuration and OSI based
DCN, the
MPLS-TP data (transport) plane is actually configured without any IP
functionality.

However I think that DCN requirements should be described in
draft-gray-mpls-tp-nm-req-00.txt.

For the scope of draft-jenkins-mpls-mpls-tp-requirements-00.txt, I think
that it
is more appropriate to rephrase the requirement as proposed by Julien.

Italo

> -----Original Message-----
> From: mpls-tp-bounces@ietf.org 
> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Francesco Fondelli
> Sent: Monday, August 04, 2008 6:00 PM
> To: julien.meuric@orange-ftgroup.com
> Cc: ccamp@ops.ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls-tp] MPLS over OTN
> 
> On Mon, Aug 4, 2008 at 5:48 PM,  
> <julien.meuric@orange-ftgroup.com> wrote:
> > Hi Francesco.
> 
> Hi Julien,
> 
> > 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...
> >
> > Anyway you're right, this could be confusing and it deserves a small
> > rewording.
> 
> Nice, thanks a lot.
> 
> > Regards,
> >
> > Julien
> 
> Ciao
> FF
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> 

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

v2.23.0 | Report a Bug | By Email