[Pce] one clarification comment on draft-ananthakrishnan-pce-stateful-path-protection-01

"Zhangxian (Xian)" <zhang.xian@huawei.com> Wed, 06 April 2016 17:55 UTC

Return-Path: <zhang.xian@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BC212D18B for <pce@ietfa.amsl.com>; Wed, 6 Apr 2016 10:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.229
X-Spam-Level:
X-Spam-Status: No, score=-4.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, WEIRD_PORT=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 SPM9OQSfkhij for <pce@ietfa.amsl.com>; Wed, 6 Apr 2016 10:55:40 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EADAD12D0E1 for <pce@ietf.org>; Wed, 6 Apr 2016 10:55:39 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CGY68505; Wed, 06 Apr 2016 17:55:38 +0000 (GMT)
Received: from SZXEMA412-HUB.china.huawei.com (10.82.72.71) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Apr 2016 18:55:37 +0100
Received: from SZXEMA512-MBS.china.huawei.com ([169.254.8.211]) by SZXEMA412-HUB.china.huawei.com ([10.82.72.71]) with mapi id 14.03.0235.001; Thu, 7 Apr 2016 01:55:33 +0800
From: "Zhangxian (Xian)" <zhang.xian@huawei.com>
To: "hari@packetdesign.com" <hari@packetdesign.com>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: one clarification comment on draft-ananthakrishnan-pce-stateful-path-protection-01
Thread-Index: AQHRkC18Y1QB79UneUKkGgOlYiBOqg==
Date: Wed, 06 Apr 2016 17:55:33 +0000
Message-ID: <C636AF2FA540124E9B9ACB5A6BECCE6B7DEA2041@SZXEMA512-MBS.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.212.196.30]
Content-Type: multipart/alternative; boundary="_000_C636AF2FA540124E9B9ACB5A6BECCE6B7DEA2041SZXEMA512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.57054D9A.0061, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.8.211, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 79b87c77ef6d810aa9d6ea1241955f1b
Archived-At: <http://mailarchive.ietf.org/arch/msg/pce/jTSe4PJQh1PQeU8VzbneXvU79E0>
Subject: [Pce] one clarification comment on draft-ananthakrishnan-pce-stateful-path-protection-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 17:55:42 -0000

Hi,



     I think this is a useful draft to cover the missing piece of using stateful PCE for LSP recovery, taking advantage of the base PCEP ASSOCIATION draft.



    I have a minor comment on the Standby(S) bit introduced by the new TLV. Is it the same as the Secondary (S) bit defined in RFC4872 or not?



Regards,

Xian



________________________________
发件人: Pce [pce-bounces@ietf.org] 代表 Dhruv Dhody [dhruv.ietf@gmail.com]
发送时间: 2016年4月7日 1:01
收件人: pce@ietf.org
主题: [Pce] Etherpad


Hi,

Help out with notes at -

http://etherpad.tools.ietf.org:9000/p/notes-ietf-95-pce?useMonospaceFont=true

People raising question/presenters, please check.

Thanks!
Dhruv