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

Luca Martini <lmartini@cisco.com> Tue, 29 June 2010 15:54 UTC

Return-Path: <lmartini@cisco.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 3F9AF3A68BB for <mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 08:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.576
X-Spam-Level:
X-Spam-Status: No, score=-0.576 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_SORBS_WEB=0.619]
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 jOsxBBBCrZKP for <mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 08:54:53 -0700 (PDT)
Received: from napoleon.monoski.com (napoleon.monoski.com [67.41.208.110]) by core3.amsl.com (Postfix) with ESMTP id E52FF3A6B98 for <mpls-tp@ietf.org>; Tue, 29 Jun 2010 08:54:52 -0700 (PDT)
Received: from seven.monoski.com ([114.251.14.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id o5TFsdKE009718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jun 2010 09:54:42 -0600 (MDT)
Message-ID: <4C29B764.7020500@cisco.com>
Date: Tue, 29 Jun 2010 03:05:40 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090812)
MIME-Version: 1.0
To: David Sinicrope <david.sinicrope@ericsson.com>
References: <C84E914D.60E0C%david.sinicrope@ericsson.com>
In-Reply-To: <C84E914D.60E0C%david.sinicrope@ericsson.com>
Content-Type: multipart/alternative; boundary="------------060407020403030600010500"
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 15:54:54 -0000

Yes,
Thanks for catching the problem.
Luca


David Sinicrope wrote:
> Agreed.
> Dave
>
>
> On 6/28/10 5:20 PM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>
> Stewart,
>
> That seems like a very reasonable liaison.
>
> Cheers,
> Andy
>
> On Mon, Jun 28, 2010 at 1:42 PM, Stewart Bryant <stbryant@cisco.com> wrote:
>   
>> 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
>>
>>     
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>