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

David Sinicrope <david.sinicrope@ericsson.com> Mon, 28 June 2010 21:50 UTC

Return-Path: <david.sinicrope@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 11F8328C10F for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 14:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.949
X-Spam-Level:
X-Spam-Status: No, score=-4.949 tagged_above=-999 required=5 tests=[AWL=1.650, 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 Rn91NRfsrUkf for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 14:50:12 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id AE4DC3A6A01 for <mpls-tp@ietf.org>; Mon, 28 Jun 2010 14:50:11 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o5SLvnn3002257; Mon, 28 Jun 2010 16:58:03 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.39]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Mon, 28 Jun 2010 17:50:08 -0400
From: David Sinicrope <david.sinicrope@ericsson.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Stewart Bryant <stbryant@cisco.com>
Date: Mon, 28 Jun 2010 17:50:05 -0400
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsXB9j5caQZszu4Rd2qfk49gO0hsQABAU1B
Message-ID: <C84E914D.60E0C%david.sinicrope@ericsson.com>
In-Reply-To: <AANLkTinXv8B1bqYSRww1nDyrDVrWsKWfAi8OtBzoOQt0@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
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
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: Mon, 28 Jun 2010 21:50:21 -0000

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