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

"BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com> Tue, 29 June 2010 07:04 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 458F93A68B2 for <mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 00:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 C5iEaY4CWQDt for <mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 00:04:49 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 295DD3A67AE for <mpls-tp@ietf.org>; Tue, 29 Jun 2010 00:04:48 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o5T73cIo002913 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 29 Jun 2010 09:04:29 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.40]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Tue, 29 Jun 2010 09:04:23 +0200
From: "BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 29 Jun 2010 09:04:21 +0200
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsW6VBy3ocYboP/SwegUUzYhsJtbwAcCKyA
Message-ID: <15740615FC9674499FBCE797B011623F0B6E9B0D@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <4C28DF03.7020103@cisco.com>
In-Reply-To: <4C28DF03.7020103@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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 07:04:50 -0000

Stewart,

could you please explain why the TTL processing in MPLS-TP is different from TTL processing in MPLS?

Alternatively, what changes in MPLS TTL processing have been defined in the last 5 years that caused the TTL processing model of G.8110 to be no longer accurate?

Thanks, Italo 

> -----Original Message-----
> From: mpls-tp-bounces@ietf.org 
> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: lunedì 28 giugno 2010 19.42
> To: mpls-tp@ietf.org
> Subject: [mpls-tp] Proposed liaison to ITU-T on G.8110
> 
> 
> Several people have pointed out a discrepancy in the model 
> for MPLS as documented in G.8110. Since this formal model 
> plays a major role in the ITU-T MPLS-TP G.8110.1 
> specification, the error should to be corrected before publication.
> 
> I therefore propose that we send the following liaison to the ITU-T.
> 
> - Stewart
> 
> ===============
> 
> To: ITU-T WP3/15
> From: IETF
> 
> Dear Dr. Trowbridge,
> 
> We note that G.8110 is referenced as a normative reference 
> from the draft text of the revision of G.8110.1. We also note 
> that G.8110 is now five years old, and has received no 
> contributions for update over that period. G.8110 has been 
> described as "not covering all of MPLS and certainly not what 
> has happened in the last five years."
> 
> We believe that G.8110.1 should document MPLS-TP accurately. 
> It is important, therefore, that where the model for MPLS-TP 
> differs from that described in G.8110, the correct model be 
> developed and documented in G.8110.1.
> 
> We would like to draw your attention in specifically to 
> Section 6.2.2 of G.8110 (and, in particular, Figures 1 and 2) 
> that says that the Time-To-Live (TTL) field of an MPLS header 
> is part of the Characteristic Information (CI) of an MPLS_CI 
> traffic unit. We note that according to G.805, the CI is 
> supposed to be delivered end-to-end between MPLS APs without 
> modification or inspection. But the function of a TTL in an 
> MPLS-TP network is to be decremented at each hop along the 
> path, and to be inspected at each hop and tested against 
> zero. Thus, in the model for MPLS-TP, the TTL should not form 
> part of the CI.
> 
> We request that G.8110.1 be updated to include this revision 
> to the model. This might most easily be achieved by 
> augmenting the references to G.8110 with updated figures 
> based on those in G.8110 along with appropriate text 
> explaining the differences in the model such that
> G.8110.1 correctly captures the model for MPLS-TP.
> 
> ==========
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>