IETF Logo Mail Archive

mpls-tp Dual stack DCN? (was [mpls-tp] MPLS over OTN)

"Diego Caviglia" <diego.caviglia@ericsson.com> Tue, 05 August 2008 07:52 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 E225A3A695A for <ietfarch-ccamp-archive@core3.amsl.com>; Tue, 5 Aug 2008 00:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.215
X-Spam-Level:
X-Spam-Status: No, score=-5.215 tagged_above=-999 required=5 tests=[AWL=-0.517, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, 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 SQom0SMc809P for <ietfarch-ccamp-archive@core3.amsl.com>; Tue, 5 Aug 2008 00:52:06 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DD75C3A6B81 for <ccamp-archive@ietf.org>; Tue, 5 Aug 2008 00:52:05 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1KQHAq-0005cd-UV for ccamp-data@psg.com; Tue, 05 Aug 2008 07:41:40 +0000
Received: from [193.180.251.60] (helo=mailgw3.ericsson.se) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <diego.caviglia@ericsson.com>) id 1KQHAl-0005bd-H6 for ccamp@ops.ietf.org; Tue, 05 Aug 2008 07:41:38 +0000
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 5CF3C20C39; Tue, 5 Aug 2008 09:41:32 +0200 (CEST)
X-AuditID: c1b4fb3c-ad099bb00000193b-ba-489803bed35a
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 698C420BD0; Tue, 5 Aug 2008 09:39:42 +0200 (CEST)
Received: from esealmw110.eemea.ericsson.se ([153.88.200.78]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Aug 2008 09:38:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: mpls-tp Dual stack DCN? (was [mpls-tp] MPLS over OTN)
Date: Tue, 05 Aug 2008 09:38:04 +0200
Message-ID: <0428AC48A879ED46A94F39D5665DF684019D92D9@esealmw110.eemea.ericsson.se>
In-Reply-To: <022e01c8f65d$cce76f90$63466297@vim.tlt.alcatel.it>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: mpls-tp Dual stack DCN? (was [mpls-tp] MPLS over OTN)
Thread-Index: Acj2SyOUHLaTSfOxR92M5/JXYSVBKwAEb4AwABvnXaA=
From: Diego Caviglia <diego.caviglia@ericsson.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: 05 Aug 2008 07:38:46.0952 (UTC) FILETIME=[4B720A80:01C8F6CE]
X-Brightmail-Tracker: AAAAAA==
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
List-ID: <ccamp.ops.ietf.org>

Hi all,
       So we are at the point where we agreed that Ip forwarding is not needed in the data plane nevertheless Ip is needed for sure for GMPLS protocols (if used).

Now in this thread we mentioned several times the DCN, are there any requirement about the protocol to be used for the DCN? Do we think that the DCN should support both OSI and Ip?

Given that we are in IETF I think the answer is that the DCN and configuration protocol must be Ip based, but may be could be useful state that somewhere; I agree that draft-gray-mpls-tp-nm-req-00.txt is the right place.

BR

Diego


> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
> Of Italo Busi
> Sent: lunedì 4 agosto 2008 20.14
> 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