Re: [mpls-tp] Proposed liaison to ITU-T on G.8110
"BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com> Tue, 29 June 2010 11:40 UTC
Return-Path: <italo.busi@alcatel-lucent.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 57AF33A6AD6 for <mpls-tp@core3.amsl.com>;
Tue, 29 Jun 2010 04:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.784
X-Spam-Level:
X-Spam-Status: No, score=-4.784 tagged_above=-999 required=5 tests=[AWL=1.464,
BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 CCEo13juyYck for
<mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 04:40:23 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by
core3.amsl.com (Postfix) with ESMTP id 12D253A6ADF for <mpls-tp@ietf.org>;
Tue, 29 Jun 2010 04:40:18 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com
(FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr
(8.14.3/8.14.3/ICT) with ESMTP id o5TBVZhG005324 (version=TLSv1/SSLv3
cipher=RC4-MD5 bits=128 verify=NOT); Tue, 29 Jun 2010 13:40:19 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.40]) by
FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi;
Tue, 29 Jun 2010 13:39:49 +0200
From: "BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>,
"alan.mcguire@bt.com" <alan.mcguire@bt.com>,
"stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 29 Jun 2010 13:39:48 +0200
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsW6VBy3ocYboP/SwegUUzYhsJtbwAcCKyAAAABC9AABa1pEAABMt/wAADJbCAAAbjR4A==
Message-ID: <15740615FC9674499FBCE797B011623F0B6E9C90@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
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>
<077E41CFFD002C4CAB7DFA4386A53264024B23EE@DEMUEXC014.nsn-intra.net>
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A53264024B23EE@DEMUEXC014.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_15740615FC9674499FBCE797B011623F0B6E9C90FRMRSSXCHMBSB1d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "mpls-tp@ietf.org" <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 11:40:25 -0000
Nurit, thanks for your reply. See in line marked with [ib] Italo ________________________________ From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.com] Sent: martedì 29 giugno 2010 12.51 To: BUSI, ITALO (ITALO); alan.mcguire@bt.com; stbryant@cisco.com Cc: mpls-tp@ietf.org Subject: RE: [mpls-tp] Proposed liaison to ITU-T on G.8110 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> [ib] The TTL processing in MPLS-TP is either identical to the TTL processing in MPLS or it is different. If it is identical, G.8110.1 should model it exactly in the same way as G.8110. A request to define a different model in G.8110.1 means to me that the TTL processing in MPLS-TP is different than in MPLS. Am I missing something? 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> [ib] As said below, the ITU-T model for all the extensions to MPLS architecture defined by IETF after the approval G.8110 and relevent to MPLS-TP has been described in G.8110.1. G.8110.1 refers to G.8110 for the aspects that are were defined by MPLS at that time and still applicable to MPLS-TP (e.g., TTL processing). 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> [ib] G.8110.1 models the TTL processing in exactly the same way as G.8110. If the TTL processing in the same between MPLS-TP and MPLS, I think this is the right way to do. If this is not the case, I would like to understand what are the differences. 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>>
- [mpls-tp] Proposed liaison to ITU-T on G.8110 Stewart Bryant
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Varma, Eve L (Eve)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Andrew G. Malis
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 David Sinicrope
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 David Allan I
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Weingarten, Yaacov (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 BUSI, ITALO (ITALO)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 alan.mcguire
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 neil.2.harrison
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 BUSI, ITALO (ITALO)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 BUSI, ITALO (ITALO)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 neil.2.harrison
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Luca Martini