Re: [mpls] [Teas] FW: New Version Notification for draft-ietf-mpls-residence-time-05.txt

Gregory Mirsky <gregory.mirsky@ericsson.com> Wed, 16 March 2016 14:15 UTC

Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA3012D591; Wed, 16 Mar 2016 07:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkTbmpN_ppoC; Wed, 16 Mar 2016 07:15:27 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E743812D590; Wed, 16 Mar 2016 07:15:26 -0700 (PDT)
X-AuditID: c618062d-f79216d00000767f-8c-56e9654d04f4
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 45.90.30335.D4569E65; Wed, 16 Mar 2016 14:53:18 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0248.002; Wed, 16 Mar 2016 10:15:24 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Lou Berger <lberger@labn.net>, Loa Andersson <loa@pi.nu>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: [Teas] FW: New Version Notification for draft-ietf-mpls-residence-time-05.txt
Thread-Index: AQHRfv7AabajoYyQ8ESTiHRUKGeJAJ9a/5YwgABc5ID//77vIIABKK6A///XwlA=
Date: Wed, 16 Mar 2016 14:15:24 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF11221A0DE4E@eusaamb103.ericsson.se>
References: <20160315210754.7666.49708.idtracker@ietfa.amsl.com> <7347100B5761DC41A166AC17F22DF11221A0D437@eusaamb103.ericsson.se> <56E88F6B.8010506@labn.net> <7347100B5761DC41A166AC17F22DF11221A0D5AC@eusaamb103.ericsson.se> <56E951B5.2050803@labn.net>
In-Reply-To: <56E951B5.2050803@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyuXSPn65f6sswg3/3BS06mt+yWPybO4fZ Yt3lU2wWt5auZLVo/bGDxYHVY8mSn0weHzY1s3nMmt7GFsAcxWWTkpqTWZZapG+XwJWx+ONd 9oLbphXr9v5kbmB8q97FyMkhIWAi8e35IxYIW0ziwr31bF2MXBxCAkcYJU5/WMME4SxnlDh+ 5QozSBWbgJHEi4097CC2iECuxK21V1hBbGYBG4mjx4+CTRIWiJF49KoRqiZW4tyLuYwQtp9E 1/GHYHEWAVWJB6emgdm8Ar4Sc87fZIVY1sIkcWHhIbChnAIaEkd/PWICsRmBzvt+ag0TxDJx iVtP5jNBnC0gsWTPeWYIW1Ti5eN/rBC2ksTH3/PZIep1JBbs/sQGYWtLLFv4mhlisaDEyZlP WCYwis1CMnYWkpZZSFpmIWlZwMiyipGjtLggJzfdyGATIzCijkmw6e5gvD/d8xCjAAejEg/v hugXYUKsiWXFlbmHGCU4mJVEeL0yX4YJ8aYkVlalFuXHF5XmpBYfYpTmYFES513/9nKYkEB6 YklqdmpqQWoRTJaJg1OqgXF+wawN3b7covpT1hWHpHgV6IU3GM8pKBYoc37/MP7gmYaK4tds zZ9yhB60/DzZ+/1Q5bpTnQI1Qswc6yz/rnmRLDbXltVu6XmmkgR9pR/x60JadFL/rEuWrhQ9 yPDFaSbb5Ao7SdfqbyvfL/36Y8XTP/cPVHN+MV9jYBp2cd/LL56vVYJq+JRYijMSDbWYi4oT AeECoemkAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/uRhDsm9sRQ7b-vhUlAE-C0ODiqI>
Cc: "mpls@ietf.org" <mpls@ietf.org>, TEAS WG <teas@ietf.org>
Subject: Re: [mpls] [Teas] FW: New Version Notification for draft-ietf-mpls-residence-time-05.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2016 14:15:30 -0000

Hi Lou,
thank you for the detailed explanation of the case. I agree that there could be other ways to handle it from what been described in the document. If a node ID of the first node in the RTM_SET TLV is not found in the RRO list, then the TTL will be set to 255 and packet will not be processed by intermediate RTM-capable nodes but arrive at LSP egress LSR. Thus not all RTM capable nodes will be accounted for in the Scratch Pad but still some nodes may. I'll add some text to highlight this case.

	Regards,
		Greg

-----Original Message-----
From: Lou Berger [mailto:lberger@labn.net] 
Sent: Wednesday, March 16, 2016 5:30 AM
To: Gregory Mirsky; Loa Andersson; mpls-chairs@ietf.org
Cc: mpls@ietf.org; TEAS WG
Subject: Re: [Teas] FW: New Version Notification for draft-ietf-mpls-residence-time-05.txt

Greg,

Thanks for the response.  See below.

On March 15, 2016 6:56:34 PM Gregory Mirsky <gregory.mirsky@ericsson.com> wrote:

> Hi Lou,
>
> thank you for the most detailed comments. Please find my notes in-line 
> tagged GIM>>.
>
>  
>
>                 Regards,
>
>                                 Greg
>
>  
>
> -----Original Message-----
> From: Lou Berger [mailto:lberger@labn.net]
> Sent: Tuesday, March 15, 2016 3:41 PM
> To: Gregory Mirsky; Loa Andersson; mpls-chairs@ietf.org
> Cc: mpls@ietf.org; TEAS WG
> Subject: Re: [Teas] FW: New Version Notification for 
> draft-ietf-mpls-residence-time-05.txt
>
>  
>
>  
>
> Greg,
>
>  
>
> On 3/15/2016 5:13 PM, Gregory Mirsky wrote:
>
> > Hi,
>
> > this version primarily addresses comments related to the proposed
> extensions to RSVP-TE and operation of the control plane in support of 
> Residence Time Measurement. Would appreciate the confirmation from Lou.
>
>  
>
> I don't think I saw a response to:
>
> > I think this doesn't always work, e.g., when RRO is modified due to
>
> > policy or limited due to size constraints.  This has to be addressed. 
>
> > I can see how to easily detect this situation, but not how to get 
> > the
>
> > number of non-supporting hops.  I guess it's always possible to play
>
> > ttl comparison games, but that's pretty ugly too.  Any thoughts?
>
> GIM>> The following text in Section 4.7 intended to handle the
> situation you've described:
>
>    If the node cannot find matching ID in RRO,
>
>    then it MUST try to use ID of the next node in the RTM_SET until it
>
>    finds the match or reaches the end of RTM_SET TLV.  If match have
>
>    been found, then the calculated value is used by the node as TTL
>
>    value in outgoing label to reach the next RTM capable node on the
>
>    LSP.  Otherwise, the TTL value MUST be set to 255.
>
> In essence, the node tries to locate the closest to it downstream 
> RTM-capable node. Otherwise, it sets TTL to 255 so that the RTM 
> packets arrive at egress LER.
>

So this doesn't cover the case where there are holes in the RRO -- which I think then translates to RTM black holes.  Also not covered is what happens during Resv processing if there is no room (or a policy) against adding local information.

Perhaps it would just be better to add a section that explicitly states that the defined mechanism only works  in cases where full RRO is supported (i.e., where RRO is not limited due to size constraints or otherwise impacted due to policy)? -- not saying I like this, I just think it fills the open gaps in the spec - but at the price of limiting applicability.  I haven't spent too much time thinking about this so there may be a better solution out there.

Lou

>  
>
> Parts of Sections 4.6 and 4.7 are a bit rough and could stand a reread 
> and editorial pass.
>
> GIM>> I'm trying.
>
>  
>
> Section 4.7 says PathErr messages are sent in response to Resv 
> processing error.  This is clearly wrong.
>
> GIM>> Great catch! I'm ready to update to ResvErr in -06.
>
>  
>
> Lou
>
>  
>
> > Authors always welcome comments and questions about RTM.
>
> > 
>
> >             Regards,
>
> >                             Greg
>
> > 
>
> > -----Original Message-----
>
> > From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
> [mailto:internet-drafts@ietf.org]
>
> > Sent: Tuesday, March 15, 2016 2:08 PM
>
> > To: Alexander Vainshtein; Gregory Mirsky; Stefano Ruffini; John 
> > Drake;
>
> > Sasha Vainshtein; Eric Gray; Stewart Bryant; Eric Gray
>
> > Subject: New Version Notification for
>
> > draft-ietf-mpls-residence-time-05.txt
>
> > 
>
> > 
>
> > A new version of I-D, draft-ietf-mpls-residence-time-05.txt
>
> > has been successfully submitted by Greg Mirsky and posted to the
> IETF repository.
>
> > 
>
> > Name:                               draft-ietf-mpls-residence-time
>
> > Revision:          05
>
> > Title:                  Residence Time Measurement in MPLS network
>
> > Document date:           2016-03-15
>
> > Group:                              mpls
>
> > Pages:                               26
>
> > URL:           
> https://www.ietf.org/internet-drafts/draft-ietf-mpls-residence-time-05
> .txt
>
> > Status:        
> https://datatracker.ietf.org/doc/draft-ietf-mpls-residence-time/
>
> > Htmlized:      
> https://tools.ietf.org/html/draft-ietf-mpls-residence-time-05
>
> > Diff:          
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-residence-time-05
>
> > 
>
> > Abstract:
>
> >    This document specifies G-ACh based Residence Time Measurement 
> > and
>
> >    how it can be used by time synchronization protocols being
>
> >    transported over MPLS domain.
>
> > 
>
> >    Residence time is the variable part of propagation delay of 
> > timing
>
> >    and synchronization messages and knowing what this delay is for 
> > each
>
> >    message allows for a more accurate determination of the delay to 
> > be
>
> >    taken into account in applying the value included in a PTP event
>
> >    message.
>
> > 
>
> >                                                                                  
>
>
> > 
>
> > 
>
> > Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at 
> tools.ietf.org.
>
> > 
>
> > The IETF Secretariat
>
> > 
>
> > _______________________________________________
>
> > Teas mailing list
>
> > Teas@ietf.org <mailto:Teas@ietf.org>
>
> > https://www.ietf.org/mailman/listinfo/teas
>
> > 
>
>  
>
>  
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org <mailto:Teas%40ietf.org> 
> https://www.ietf.org/mailman/listinfo/teas
>