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

"Zafar Ali (zali)" <zali@cisco.com> Thu, 20 February 2014 20:25 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 86B6B1A026A for <ccamp@ietfa.amsl.com>; Thu, 20 Feb 2014 12:25:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level:
X-Spam-Status: No, score=-10.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, 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 5WCWN-7H9D4A for <ccamp@ietfa.amsl.com>; Thu, 20 Feb 2014 12:25:53 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id C32131A021E for <ccamp@ietf.org>; Thu, 20 Feb 2014 12:25:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9493; q=dns/txt; s=iport; t=1392927949; x=1394137549; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=4PsZyEgN3uU8jYAMaaKP8VLpMfgO6ZC6ve/tum2VyzQ=; b=X+K/KlHsSngAQ0PYuEgWNN3gb4h76VlIOORCNlEuI3mPgL1og5Du62vk MWIvhka6vZkv766B3ZTy+BLIUPQiP9Qr7wzYZqKd4+n2Qw5jLMnXzCSMs zBUAoYAhTETYb6Yzy6iXr1jb7axuDZbYQq9ELlRiZ0ZXwstymNniWe9nB 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4FAJZkBlOtJXG//2dsb2JhbABZgkJEOFe3OYhWgREWdIIlAQEBBAEBAWsJAgwGAQgRAwECKCgGCxQIAQgCBA4Fh3EDEQ3GIg2HVBeMT4IEDQQGAQaEMgSWRIFsgTKLLIVGgW+BPoIq
X-IronPort-AV: E=Sophos; i="4.97,514,1389744000"; d="scan'208,217"; a="21990854"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by alln-iport-5.cisco.com with ESMTP; 20 Feb 2014 20:25:48 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1KKPmU7025243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Feb 2014 20:25:48 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.212]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Thu, 20 Feb 2014 14:25:48 -0600
From: "Zafar Ali (zali)" <zali@cisco.com>
To: 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//sPuA
Date: Thu, 20 Feb 2014 20:25:47 +0000
Message-ID: <CF2BCDA4.9B87D%zali@cisco.com>
In-Reply-To: <CADOd8-vjzUM4OgYQKq=NE2h_uBkd+s2WwWjWMrhVRo=oubv3qA@mail.gmail.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.86.245.20]
Content-Type: multipart/alternative; boundary="_000_CF2BCDA49B87Dzaliciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/_ZqmlZPM2KLYMSqzwNW3xV0RImU
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: Thu, 20 Feb 2014 20:25:55 -0000

Hi Cyril-

RFC5553 mentions:


" 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."


How any of this justifies the following statement:

"1: Added a section describing how the Path Key resolution works, and it demonstrates that the proposed method can work in both the scenario with PCE, as well as WITHOUT PCE."

Thanks

Regards … Zafar

From: Cyril Margaria <cyril.margaria@gmail.com<mailto:cyril.margaria@gmail.com>>
Date: Thursday, February 20, 2014 3:11 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

Hi Zafar,

The document follows the same procedure as RFC5553.
PKS resolution using PCE is one possible implementation, the processing node may use other mechanism (section 3.1 of RFC5553 describes some of them).

One possible implementation being "The LSR can use the information in the PKS to index a CPS previously supplied to it by the PCE that originated the PKS."

This can cover a number of mechanisms including configuration using management system.

I hope this clarifies the statement.

Best Regards,
Cyril.



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

-----Original Message-----
From: "Zhangxian   (Xian)" <zhang.xian@huawei.com<mailto:zhang.xian@huawei.com>>
Date: Friday, February 14, 2014 8:50 PM
To: "ccamp@ietf.org<mailto:ccamp@ietf.org>" <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: [CCAMP] FW: New Version Notification for
draft-zhang-ccamp-route-exclusion-pathkey-01.txt

>1: Added a section describing how the Path Key resolution works, and it
>demonstrates that the proposed method can work in both the scenario with
>PCE, as well as WITHOUT PCE.
>

Hi Xian:

When an ERO expanding node hits exclude Path Key(EXRS), it still needs to
lookup the path associated with the Path Key. So how do you achieve Path
Key lookup WITHOUT PCE?

More comments later,

Thanks

Regards...Zafar

_______________________________________________
CCAMP mailing list
CCAMP@ietf.org<mailto:CCAMP@ietf.org>
https://www.ietf.org/mailman/listinfo/ccamp