Re: [mpls-tp] Proposed liaison to ITU-T on G.8110

"Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> Tue, 29 June 2010 10:52 UTC

Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C7F33A67D9 for <mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 03:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.165
X-Spam-Level:
X-Spam-Status: No, score=-2.165 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ClWe3NJQheSd for <mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 03:52:40 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id D595F3A680E for <mpls-tp@ietf.org>; Tue, 29 Jun 2010 03:52:39 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o5TApFSw026121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 29 Jun 2010 12:51:15 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o5TApEQT014709; Tue, 29 Jun 2010 12:51:14 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 29 Jun 2010 12:51:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB1778.FE87B4FD"
Date: Tue, 29 Jun 2010 12:51:13 +0200
Message-ID: <077E41CFFD002C4CAB7DFA4386A53264024B23EE@DEMUEXC014.nsn-intra.net>
In-Reply-To: <15740615FC9674499FBCE797B011623F0B6E9C59@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsW6VBy3ocYboP/SwegUUzYhsJtbwAcCKyAAAABC9AABa1pEAABMt/wAADJbCA=
References: <4C28DF03.7020103@cisco.com><15740615FC9674499FBCE797B011623F0B6E9B0D@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <4CC2173AA6BF374C984F501B7453AAD198CB07F305@EMV66-UKRD.domain1.systemhost.net> <077E41CFFD002C4CAB7DFA4386A53264024B2373@DEMUEXC014.nsn-intra.net> <15740615FC9674499FBCE797B011623F0B6E9C59@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com>, <alan.mcguire@bt.com>, <stbryant@cisco.com>
X-OriginalArrivalTime: 29 Jun 2010 10:51:14.0844 (UTC) FILETIME=[FECB45C0:01CB1778]
Cc: mpls-tp@ietf.org
Subject: Re: [mpls-tp] Proposed liaison to ITU-T on G.8110
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2010 10:52:42 -0000

Hi Italo,

Please see inline.

Best regards,

Nurit

 

-----Original Message-----
From: ext BUSI, ITALO (ITALO) [mailto:italo.busi@alcatel-lucent.com] 
Sent: Tuesday, June 29, 2010 1:34 PM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); alan.mcguire@bt.com; stbryant@cisco.com
Cc: mpls-tp@ietf.org
Subject: RE: [mpls-tp] Proposed liaison to ITU-T on G.8110

 

Nurit,

 

I have already raised some specific questions for clarification about your last point.

 

What has been changed in MPLS TTL processing in the last 5 years? 

 

<Nurit> This was a general comment, not specific related to TTL. \<Nurit> 

 

Why do you think TTL processing in MPLS-TP is different from TTL processing in MPLS? What are actually these differences?

 

<Nurit> I do not think I have said it. \<Nurit>

 

I recall I raised a specific question during the last Q12/15 meeting to check whether the TTL processing in MPLS-TP is the same as in MPLS. All those present at that meeting (including ISOC representatives) agreed that the TTL processing is the same.

If this answer that I got at the meeting is incorrect, I would appreciate to understand why.

 

I do not buy the argument that G.8110 is five years old. RFC 3031 is nine years old but this is not precluding us to make normative reference to it.

<Nurit> Sure, but a lot of work has been done since then on MPLS architecture as documented in other documents. Is it the same in the ITU-T? do we have additional documents on MPLS architecture? \<Nurit> 

 

During the development of G.8110.1 a lot of care has been taken by the editor and technical contributors to reuse the functional model of G.8110 when appropriate and to develop extensions to this model where needed.

<Nurit> I am sure. Still we have the concern on the modeling of TTL as a CI. Please refer to my main points in the mail. AM I wrong? \<Nurit>

 

I would appreciate if you can point to a specific technical item that has not been properly captured in this work.

 

Italo

 

 

________________________________

 

      From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.com] 

      Sent: martedì 29 giugno 2010 12.09

      To: alan.mcguire@bt.com; BUSI, ITALO (ITALO); stbryant@cisco.com

      Cc: mpls-tp@ietf.org

      Subject: RE: [mpls-tp] Proposed liaison to ITU-T on G.8110

      

      

 

      Hi,

 

      It is correct that the CI is transferred on a "network connection" which is formed by a series of contiguous "link connections" and/or "subnetwork connections" between "termination connection points". We should fix the proposed liaison accordingly! 

 

      Still the concern is valid. 

 

      G.805 refers to the generation (at the source), transport and termination (at the sink) of CI (in the context of a layer network), and also to the interworking of CI of one layer network with the CI another layer, but not to the processing of the CI at each transport entity or port along the network connection. 

 

      Therefore I support the liaison with the correction of TCPs and not APs.

 

      I think also that the fact that G.8110 (which is used as a normative reference) has not been updated since 2005, raises more concerns. MPLS was worked out since 2005 and there is a need to understand the gaps and check consistencies, etc. 

 

      Best regards,

 

      Nurit

 

       

 

      <<Snipped>>