Re: [CCAMP] FW: New Version Notification for draft-zhang-ccamp-route-exclusion-pathkey-01.txt

"Zafar Ali (zali)" <zali@cisco.com> Fri, 21 February 2014 04:20 UTC

Return-Path: <zali@cisco.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660931A03F0 for <ccamp@ietfa.amsl.com>; Thu, 20 Feb 2014 20:20:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level:
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 e8Co1PtCoRt1 for <ccamp@ietfa.amsl.com>; Thu, 20 Feb 2014 20:20:53 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D67BD1A03F2 for <ccamp@ietf.org>; Thu, 20 Feb 2014 20:20:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=31021; q=dns/txt; s=iport; t=1392956449; x=1394166049; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=ut0+rozso0OOWLxQQdYFZRQ+VrnKK2dW06n58ScEq2E=; b=m30BVR5yG2YZ3DwqUOvElxV4ZfzRXOnq1cgf20EO1UEHl4MzWtx9tr07 dbIaHfsqaHoDJ8rT5VfoKPtigx5l1qBjnNimCuA83v664KpSkFHzfSK8v HgKwrGCT1j2NzwPLHcv/pZcuxEpuQ5jFd+7qjuNN9bqIFxJImaCjxCC4M g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtEFADXTBlOtJV2c/2dsb2JhbABZgkJEOFeDArQ+iFYYdhZ0giUBAQEEIwpKAhIBBgIRAwEBASEHAwIEHxEUCAEIAgQBDQUbh1YDEQ2QA5t/mVANh1YXjE+CBBEGAYJvgUkElkSBbIEyiyyFRoFvgT6CKg
X-IronPort-AV: E=Sophos; i="4.97,516,1389744000"; d="scan'208,217"; a="305349658"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 21 Feb 2014 04:20:48 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s1L4KlxJ002246 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Feb 2014 04:20:47 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.212]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Thu, 20 Feb 2014 22:20:47 -0600
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "Zhangxian (Xian)" <zhang.xian@huawei.com>, Cyril Margaria <cyril.margaria@gmail.com>
Thread-Topic: [CCAMP] FW: New Version Notification for draft-zhang-ccamp-route-exclusion-pathkey-01.txt
Thread-Index: AQHPKU2JCZBTfzFjP0WAW8oQDHTmA5q0SJCwgAo5FwCAAIAuAP//sPuAgABZxwD//7OxgIAAWyUA//++iIAACsTHgAAEzVmA///hAYA=
Date: Fri, 21 Feb 2014 04:20:47 +0000
Message-ID: <CF2C3A79.9BB0C%zali@cisco.com>
In-Reply-To: <C636AF2FA540124E9B9ACB5A6BECCE6B301FE7A2@SZXEMA512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.82.236.216]
Content-Type: multipart/alternative; boundary="_000_CF2C3A799BB0Czaliciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/3Ta831J17fcCMN8n_nOE_jMmdwE
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] FW: New Version Notification for draft-zhang-ccamp-route-exclusion-pathkey-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 21 Feb 2014 04:20:56 -0000

Hi:

Please see in-line.

Thanks

Regards … Zafar

From: "Zhangxian (Xian)" <zhang.xian@huawei.com<mailto:zhang.xian@huawei.com>>
Date: Thursday, February 20, 2014 8:14 PM
To: Cyril Margaria <cyril.margaria@gmail.com<mailto:cyril.margaria@gmail.com>>, zali <zali@cisco.com<mailto:zali@cisco.com>>
Cc: "ccamp@ietf.org<mailto:ccamp@ietf.org>" <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: RE: [CCAMP] FW: New Version Notification for draft-zhang-ccamp-route-exclusion-pathkey-01.txt

Cyril has made it pretty clear. I just want to add that,  the function needed for draft-zhang-ccamp-route-exclusion-pathkey is to resolve path key.  So as long as mechanisms can fulfill this, it works.

Yes, if you have a proprietary solution, it will work for you. I asked pointers to a standard based solution non-PCE solution where path key resolution is defined – as this is what you are claiming. I am happy if you soften your claim.

Definitely using a PCE is a good and obvious example which is included in the draft, but it is NOT the only mechanism, as explained in the updated draft text quoted below.

Regards,
Xian

From: Cyril Margaria [mailto:cyril.margaria@gmail.com]
Sent: 2014年2月21日 6:57
To: Zafar Ali (zali)
Cc: Zhangxian (Xian); ccamp@ietf.org<mailto:ccamp@ietf.org>
Subject: Re: [CCAMP] FW: New Version Notification for draft-zhang-ccamp-route-exclusion-pathkey-01.txt

Hi Zafar,
This is described in the section 2.2
"
If it cannot decode the PKS, the error handling procedure defined in Section 3.1 of [RFC5553]<http://tools.ietf.org/html/rfc5553#section-3.1> is not changed by this document.
This mechanism can work with all the PKS resolution mechanism, as detailed in [RFC5553] section 3.1<http://tools.ietf.org/html/rfc5553#section-3.1>.

Quoting relevant text from [RFC5553] section 3.1<http://tools.ietf.org/html/rfc5553#section-3.1>..


     Resolution of the PKS MAY take any of the following forms or use
     some other technique subject to local policy and network
     implementation.

     o The LSR can use the PCE-ID contained in the PKS to contact the
       identified PCE using PCEP [RFC5440<http://tools.ietf.org/html/rfc5440>] and request that the PKS be
       expanded.

     o The LSR can contact any PCE using PCEP [RFC5440<http://tools.ietf.org/html/rfc5440>] to request that
       the PKS be expanded, relying on cooperation between the PCEs.

     o The LSR can use the information in the PKS to index a CPS
       previously supplied to it by the PCE that originated the PKS.

All these methods are pointing to a PCE based solution.


A PCE, co-located or not, may be used to resolve the PKS, but the node (i.e., a Label Switcher Router(LSR)) can also use the PKS information to index a Path Segment previously supplied to it by the entity that originated the PKS, for example the LSR that inserted the PKS in the RRO or a management system.

How this communication between LSR generating the Path key and LSR seeking Path info happens? If you are only referring to to co-located PCE, then scope comes back to a PCE based solution.


"

The document could also state :

PKS resolution MAY take any of the forms described in RFC5553 section 3.1. In addition the LSR


can also use the PKS information to index a Path Segment previously supplied to it by the entity
that originated the PKS. This can be, for example, the LSR that inserted the PKS in the RRO or a

   management system.

See above.




Would that answer your question?






On 20 February 2014 23:45, Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>> wrote:

From: Cyril Margaria <cyril.margaria@gmail.com<mailto:cyril.margaria@gmail.com>>
Date: Thursday, February 20, 2014 4:43 PM

To: zali <zali@cisco.com<mailto:zali@cisco.com>>
Cc: "Zhangxian (Xian)" <zhang.xian@huawei.com<mailto:zhang.xian@huawei.com>>, "ccamp@ietf.org<mailto:ccamp@ietf.org>" <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: Re: [CCAMP] FW: New Version Notification for draft-zhang-ccamp-route-exclusion-pathkey-01.txt

The document does propose a simple set of extension that works (but are not restricted to, nor require) with another standard IETF protocol, namely PCEP.

Can you please qualify this statement? Without PCE (PCEP) this solution does not work.

Thanks

Regards… Zafar