[CCAMP] The description of Path Key retaining time in RFC5553

"Zhangxian (Xian)" <zhang.xian@huawei.com> Thu, 07 November 2013 19:24 UTC

Return-Path: <zhang.xian@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17D311E8282 for <ccamp@ietfa.amsl.com>; Thu, 7 Nov 2013 11:24:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.307
X-Spam-Level:
X-Spam-Status: No, score=-6.307 tagged_above=-999 required=5 tests=[AWL=0.292, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rdOtgiQj32M6 for <ccamp@ietfa.amsl.com>; Thu, 7 Nov 2013 11:24:33 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 05D3E11E8281 for <ccamp@ietf.org>; Thu, 7 Nov 2013 11:24:32 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAA47672; Thu, 07 Nov 2013 19:24:32 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 7 Nov 2013 19:23:49 +0000
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 7 Nov 2013 19:24:31 +0000
Received: from SZXEML510-MBX.china.huawei.com ([169.254.3.140]) by szxeml418-hub.china.huawei.com ([10.82.67.157]) with mapi id 14.03.0158.001; Fri, 8 Nov 2013 03:24:27 +0800
From: "Zhangxian (Xian)" <zhang.xian@huawei.com>
To: "zali@cisco.com" <zali@cisco.com>
Thread-Topic: The description of Path Key retaining time in RFC5553
Thread-Index: AQHO2+75nyh5MwjjqEemfNXW9E7a+A==
Date: Thu, 07 Nov 2013 19:24:26 +0000
Message-ID: <C636AF2FA540124E9B9ACB5A6BECCE6B263E040B@szxeml510-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.150.242]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: [CCAMP] The description of Path Key retaining time in RFC5553
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 19:24:38 -0000

Hi, all,

  The following is the piece of information that i mentioned already require retaining the Path key information for the lifetime of LSP. 

Section 3.2 from RFC5553
"
.......
On a Path message, the PKS SHOULD identify the LSR replacing the CPS and provide a Path Key that can be used to expand  the path segment.  In the latter case, the Path Key and its expansion SHOULD be retained by the LSR that performs the substitution for at least the lifetime of the LSP.  In both cases, the expansion of the PKS SHOULD be made available to diagnostic tools under the control of local policy.
"

My understanding of the stateful PCE (from PCE WG) is to have LSP-DB documenting information such as the identifiers (the 5-tuple), route, bw information etc. So I do not think our extensions defined in http://tools.ietf.org/html/draft-zhang-ccamp-route-exclusion-pathkey-00 incur any new additional requirements. Please review our draft and let us know what you think.

Cheers,
Xian