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

David Allan I <david.i.allan@ericsson.com> Mon, 28 June 2010 23:48 UTC

Return-Path: <david.i.allan@ericsson.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 E234A3A6935 for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 16:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level:
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, 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 G1TENuikmZ0l for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 16:48:21 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 5AF3D3A68AC for <mpls-tp@ietf.org>; Mon, 28 Jun 2010 16:48:21 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o5SNu5Iw014035; Mon, 28 Jun 2010 18:56:14 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.39]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Mon, 28 Jun 2010 19:48:18 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Mon, 28 Jun 2010 19:46:04 -0400
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsW6WMhIdXTwK5+SlKiLaLs5ZD73wAMqxiA
Message-ID: <60C093A41B5E45409A19D42CF7786DFD518156D2BF@EUSAACMS0703.eamcs.ericsson.se>
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
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 23:48:24 -0000

Support...

D 

-----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