Re: [CCAMP] draft-ali-ccamp-lsp-inquiry-00

"Zafar Ali (zali)" <> Wed, 31 July 2013 00:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3B35911E8139 for <>; Tue, 30 Jul 2013 17:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JPbT0NFRgEfr for <>; Tue, 30 Jul 2013 17:16:41 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F146C21E80AE for <>; Tue, 30 Jul 2013 17:16:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=52976; q=dns/txt; s=iport; t=1375229798; x=1376439398; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=eqQxlesIFloZ0dwX3L5Qxr8MJWN8zIwqoTLqjt07fhU=; b=NrTsUX94/wQ8V8uzLf5wrQK+GkQfz2ffR3CvhjXgmEr8mHlzCZPRbTta 0KVtTTCtHvuynN0MY82G63JJyZpK10BlqzopelKLT9a6H7qYKEHBpBxAA GuTz7/Dd+bTlRoP5bcsW5xS3tt0t1EoPlQXELWYqU0WwV15z8RXhZQjUt w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAA5X+FGtJXG8/2dsb2JhbABbgkJENVC+GIEfFnSCJAEBAQQtXgEIDgMDAQEBCxYBBjkUCQgBAQQBEggRh3e4bo9NIBcBgxhxA6krgxSCKg
X-IronPort-AV: E=Sophos; i="4.89,782,1367971200"; d="scan'208,217"; a="241356209"
Received: from ([]) by with ESMTP; 31 Jul 2013 00:16:37 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id r6V0Gbib030650 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 Jul 2013 00:16:37 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Tue, 30 Jul 2013 19:16:37 -0500
From: "Zafar Ali (zali)" <>
To: Khuzema Pithewan <>, "CCAMP (" <>
Thread-Topic: [CCAMP] draft-ali-ccamp-lsp-inquiry-00
Date: Wed, 31 Jul 2013 00:16:36 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B6585D85A128FD47857D0FD58D8120D30E9F3BDCxmbrcdx14ciscoc_"
MIME-Version: 1.0
Subject: Re: [CCAMP] draft-ali-ccamp-lsp-inquiry-00
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 31 Jul 2013 00:16:47 -0000

Hi Khuzema:

For signaling inquiry LSP with resource locking, we are using the Pre-Planned LSP flag as-is as defined in RFC6001. Given this, we are defining a new flag when inquiry LSP needs to be signal without resource locking.


Regards … Zafar

From: Khuzema Pithewan <<>>
Date: Tuesday, July 30, 2013 5:45 PM
To: zali <<>>, "<>" <<>>
Subject: RE: [CCAMP] draft-ali-ccamp-lsp-inquiry-00

Well.. not really.

You are defining new bits for LSP_ATTRIBUTES for resource locking… aren’t you?

Instead of doing that, you can define bits in ADMIN_STATUS and save new LSP life cycle management, which would be quite cumbersome.


From: Zafar Ali (zali) []
Sent: Tuesday, July 30, 2013 10:08 PM
To: Khuzema Pithewan; CCAMP (<>)
Subject: Re: [CCAMP] draft-ali-ccamp-lsp-inquiry-00


The point is to reuse what already exists. The Pre-Planned LSP flag in the Attribute Flags TLV of LSP_ATTRIBUTES object is already defined in [RFC5420] and is a glove fit.


Regards … Zafar

From: Khuzema Pithewan <<>>
Date: Tuesday, July 30, 2013 1:40 PM
To: Khuzema Pithewan <<>>, "<>" <<>>
Subject: Re: [CCAMP] draft-ali-ccamp-lsp-inquiry-00

Another point I spoke about in the meeting ..

Why can’t we extend Admin Status object to signal resource locking, checking for re-optimization. Since this operation is typically done in maintenance window by Admin, it may make sense to use Admin Status Object. Moreover, we have lots of bits available/undefined in Admin Status object.

This will save network element to manage life of additional LSP and control plane failure related issues attached to the additional LSP.