Re: [mpls-tp] Proposed liaison to ITU-T on G.8110
<alan.mcguire@bt.com> Tue, 29 June 2010 07:37 UTC
Return-Path: <alan.mcguire@bt.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 3D85C3A67C2 for <mpls-tp@core3.amsl.com>;
Tue, 29 Jun 2010 00:37:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.691
X-Spam-Level:
X-Spam-Status: No, score=0.691 tagged_above=-999 required=5 tests=[AWL=0.322,
BAYES_40=-0.185, HELO_MISMATCH_COM=0.553]
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 I8Wh2awPSgwK for
<mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 00:37:00 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp63.intersmtp.COM [62.239.224.236]) by
core3.amsl.com (Postfix) with ESMTP id 710323A67AE for <mpls-tp@ietf.org>;
Tue, 29 Jun 2010 00:36:59 -0700 (PDT)
Received: from EVMHT66-UKRD.domain1.systemhost.net (10.36.3.103) by
RDW083A007ED63.smtp-e3.hygiene.service (10.187.98.12) with Microsoft SMTP
Server (TLS) id 8.1.436.0; Tue, 29 Jun 2010 08:37:13 +0100
Received: from emv66-ukrd.domain1.systemhost.net ([169.254.1.232]) by
EVMHT66-UKRD.domain1.systemhost.net ([10.36.3.103]) with mapi;
Tue, 29 Jun 2010 08:37:08 +0100
From: <alan.mcguire@bt.com>
To: <italo.busi@alcatel-lucent.com>, <stbryant@cisco.com>
Date: Tue, 29 Jun 2010 08:37:07 +0100
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsW6VBy3ocYboP/SwegUUzYhsJtbwAcCKyAAAABC9A=
Message-ID: <4CC2173AA6BF374C984F501B7453AAD198CB07F305@EMV66-UKRD.domain1.systemhost.net>
References: <4C28DF03.7020103@cisco.com>
<15740615FC9674499FBCE797B011623F0B6E9B0D@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
In-Reply-To: <15740615FC9674499FBCE797B011623F0B6E9B0D@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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:37:01 -0000
Stewart, Whilst I don't agree with your proposed liaison I'd like to make a suggestion. Your statement that " We note that according to G.805, the CI is supposed to be delivered end-to-end between MPLS APs without modification or inspection" is incorrect by definition. CI information is transferred between Termination Connection Points (TCPs) and not between AP's. Indeed the point of the source termination function is to add information to adapted information which traverses the AP and thus to generate CI and the corresponding sink processes information. This is quite clear from G.805 and is also well described in Sexton and Reid. I would therefore suggest you correct your liaison. Regarding the model for TTL, I am sure that Q12 will be happy to explain the reasoning behind the way it was constructed and how the TTL value is decremented on a per hop basis. But perhaps it might be more appropriate to ask for an explanation of how the model works before assuming that it is wrong. Best regards Alan > -----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 > > We note that according to G.805, the CI is > supposed to be delivered end-to-end between MPLS APs without > modification or inspection > 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] Proposed liaison to ITU-T on G.8110 Stewart Bryant
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Varma, Eve L (Eve)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Andrew G. Malis
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 David Sinicrope
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 David Allan I
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Weingarten, Yaacov (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 BUSI, ITALO (ITALO)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 alan.mcguire
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 neil.2.harrison
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 BUSI, ITALO (ITALO)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 BUSI, ITALO (ITALO)
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 neil.2.harrison
- Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 Luca Martini