Re: [mpls-tp] Proposed liaison to ITU-T on G.8110
<neil.2.harrison@bt.com> Tue, 29 June 2010 10:04 UTC
Return-Path: <neil.2.harrison@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 1C2D63A67D9 for <mpls-tp@core3.amsl.com>;
Tue, 29 Jun 2010 03:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=-0.650,
BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1]
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 fm68qC5KLiSm for
<mpls-tp@core3.amsl.com>; Tue, 29 Jun 2010 03:04:04 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by
core3.amsl.com (Postfix) with ESMTP id 3DB5C3A67B8 for <mpls-tp@ietf.org>;
Tue, 29 Jun 2010 03:04:03 -0700 (PDT)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.107]) by
smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);
Tue, 29 Jun 2010 11:04:13 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Jun 2010 11:03:15 +0100
Message-ID: <2ECAA42C79676B42AEBAC11229CA7D0C0606C3A6@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <4CC2173AA6BF374C984F501B7453AAD198CB07F305@EMV66-UKRD.domain1.systemhost.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls-tp] Proposed liaison to ITU-T on G.8110
Thread-Index: AcsW6VBy3ocYboP/SwegUUzYhsJtbwAcCKyAAAABC9AABD8TgA==
From: <neil.2.harrison@bt.com>
To: <alan.mcguire@bt.com>, <italo.busi@alcatel-lucent.com>,
<stbryant@cisco.com>
X-OriginalArrivalTime: 29 Jun 2010 10:04:13.0094 (UTC)
FILETIME=[6CE66460:01CB1772]
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 10:04:06 -0000
I agree with Alan that one should ask Q12 why they used a specific approach for the modelling of TTL in MPLS. However, one has to observe that in a co-ps mode transport network based on proper connections then a TTL function is unnecessary....so asking whether we are accurately modelling something that is just plain wrong is a rather strange thing to focus on (and I'll wager this is why it has a strange handling model in G.8110). Perhaps Stewart's mail is the catalyst to ask the question why we simply don't null the TLL function in MPLS-TP? Aside=> We can't appeal to an argument that 'it's a profile of MPLS' because MPLS-TP is creating a new layer co-ps mode network technology since it adds new functional behaviours not found in any existing spin of MPLS (eg logically OOB CP, new addressing types, new OAM) in addition to reusing as much of the existing MPLS specification as it can......even inappropriate bits unfortunately....which is the case we have here. regards, Neil > -----Original Message----- > From: mpls-tp-bounces@ietf.org > [mailto:mpls-tp-bounces@ietf.org] On Behalf Of alan.mcguire@bt.com > Sent: 29 June 2010 08:37 > To: italo.busi@alcatel-lucent.com; stbryant@cisco.com > Cc: mpls-tp@ietf.org > Subject: Re: [mpls-tp] Proposed liaison to ITU-T on G.8110 > > 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 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