Re: [mpls] comment on draft-ietf-mpls-residence-time

Gregory Mirsky <> Tue, 02 February 2016 01:36 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 021F41A1B8C; Mon, 1 Feb 2016 17:36:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id j0EgcTKWrcCR; Mon, 1 Feb 2016 17:35:58 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 607AD1A1B8A; Mon, 1 Feb 2016 17:35:57 -0800 (PST)
X-AuditID: c618062d-f79d16d000001b1c-51-56b004e8aed9
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 33.C1.06940.8E400B65; Tue, 2 Feb 2016 02:22:48 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0248.002; Mon, 1 Feb 2016 20:35:56 -0500
From: Gregory Mirsky <>
To: Lou Berger <>, "" <>, "" <>, TEAS WG <>, "CCAMP (" <>
Thread-Topic: comment on draft-ietf-mpls-residence-time
Thread-Index: AQHRXDT5bSUNiSX6T0W7JnL+kOquQJ8X+cqA
Date: Tue, 02 Feb 2016 01:35:55 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyuXRPgu4Llg1hBo+nKFo8mXODxeLwhVPs Fh3Nb1ksbi1dyWrR+mMHiwOrx5IlP5k8PmxqZgtgiuKySUnNySxLLdK3S+DKuLY7qOAOd8Xe fT/ZGhi3cHcxcnJICJhINLxcywJhi0lcuLeerYuRi0NI4AijxPwlb1hBEkICyxglnh3MAbHZ BIwkXmzsYQcpEhG4zyix6egyJpCEsICZROOH3YwgtoiAucSLpt1MELaRxMOWrWwgNouAisSF B9PB4rwCvhLdmyDqhQTUJV7sOQRkc3BwCmhI7LypBxJmBDro+6k1YOXMAuISt57MZ4I4VEBi yZ7zzBC2qMTLx/9YIWwliTmvrzGDjGEW0JRYv0sfolVRYkr3Q3aIrYISJ2c+YZnAKDoLydRZ CB2zkHTMQtKxgJFlFSNHaXFBTm66kcEmRmCUHJNg093BeH+65yFGAQ5GJR5eg9Xrw4RYE8uK K3MPMUpwMCuJ8K58DxTiTUmsrEotyo8vKs1JLT7EKM3BoiTOu9QBKCWQnliSmp2aWpBaBJNl 4uCUamA0t5+fnhDb+rDn5bSyjL1PLBg9txb4P8j4ln/A9Vr2JCZeY87ueXwyW0Jant04GbZt ztxcT9kVqg8K+kKSeHMlBHOmcX4L+1U+/fetK3GHd58rXTjL/L7LLMmfp22UvbtOXpo8Z8XU /79P3a0VrLx4guel1QHGmbwbuvLOdBw9Ny1G9aPM1CMblFiKMxINtZiLihMBzA+qYI4CAAA=
Archived-At: <>
Subject: Re: [mpls] comment on draft-ietf-mpls-residence-time
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Feb 2016 01:36:00 -0000

Hi Lou,
thank you for your thoughtful recommendation. I agree that we can use LSP_ATTRIBUTES [RFC5420]. I'll prepare update and share with you, MPLS, TEAS , and CCAMP WGs. 


-----Original Message-----
From: Lou Berger [] 
Sent: Sunday, January 31, 2016 6:38 AM
Subject: comment on draft-ietf-mpls-residence-time

	I see you propose defining a new RSVP object class that has application specific scope.  As I'm sure you know the RSVP class-number space is really small so it's best to avoid allocating new object classes whenever possible.  I believe there is an existing object class that you can use for your purposes -- the LSP_ATTRIBUTES object.

Have you considered carrying RTM Hops in 1 (or three,  depending on if you want sub-tlvs or not) new RTM Attribute TLV (or TLVs)?

If not, I think it is worth exploring the viability of this approach or any other approach that doesn't require the allocation of a new class-num.

(As contributor and TEAS co-chair)