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

"Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com> Mon, 28 June 2010 19:35 UTC

Return-Path: <eve.varma@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 73F3128C102 for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 12:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level:
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
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 NcmWEVemXeyb for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 12:35:41 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 13AC73A6960 for <mpls-tp@ietf.org>; Mon, 28 Jun 2010 12:35:41 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o5SJZngt026228 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jun 2010 14:35:49 -0500 (CDT)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o5SJZnQI001030; Mon, 28 Jun 2010 14:35:49 -0500
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.127]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Mon, 28 Jun 2010 14:35:49 -0500
From: "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Mon, 28 Jun 2010 14:35:47 -0500
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsW6U4bv6S9mbsWSEOGh0rabo9VSQADmXKg
Message-ID: <84208699E388BB4B83AD8BEA84A04AC724FA1EE54D@USNAVSXCHMBSA3.ndc.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
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: Mon, 28 Jun 2010 19:35:42 -0000

Hi Stewart,

I'd suggest addressing the liaison to Malcolm Betts, since any work on the modeling would take place in Q12/15 (and could be handled, as needed, during the October Q12/15 meeting in Shanghai).

Cheers,
Eve

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Stewart Bryant
Sent: Monday, June 28, 2010 1:42 PM
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