Re: [Idr] Mail regarding draft-ietf-idr-segment-routing-te-policy

"Susan Hares" <shares@ndzh.com> Tue, 30 April 2019 17:00 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89EF21202ED for <idr@ietfa.amsl.com>; Tue, 30 Apr 2019 10:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level:
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 lkUeqBP4zQus for <idr@ietfa.amsl.com>; Tue, 30 Apr 2019 10:00:20 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37F1312008D for <idr@ietf.org>; Tue, 30 Apr 2019 10:00:20 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.176.248.72;
From: "Susan Hares" <shares@ndzh.com>
To: "'Chaitanya Varma'" <chaitanya.varma@ipinfusion.com>, <idr@ietf.org>
Cc: "'Gurusiddesh Nidasesi'" <gurusiddesh.nidasesi@ipinfusion.com>
References: <993db9e45983acc9769af61bf786a6d6@mail.gmail.com>
In-Reply-To: <993db9e45983acc9769af61bf786a6d6@mail.gmail.com>
Date: Tue, 30 Apr 2019 13:00:17 -0400
Message-ID: <005401d4ff76$309baec0$91d30c40$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0055_01D4FF54.A98F65F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIa5cXhmTfnf6w64SOQeTlHmLhQWaXJICbQ
Content-Language: en-us
X-Antivirus: AVG (VPS 190430-4, 04/30/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/h-bhK8GGmGYb8BKwfLjJs2Iillw>
Subject: Re: [Idr] Mail regarding draft-ietf-idr-segment-routing-te-policy
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Apr 2019 17:00:21 -0000

Stefano, Clarence, Dhanendra, Paul Eric, and Steve: 

 

I would appreciate if you would take time to answer this query. 

 

Thank you – Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Chaitanya Varma
Sent: Tuesday, April 30, 2019 4:04 AM
To: idr@ietf.org
Cc: Gurusiddesh Nidasesi
Subject: [Idr] Mail regarding draft-ietf-idr-segment-routing-te-policy

 

Hi, 

 

I have couple of queries from the below draft. 

 

https://tools.ietf.org/html/draft-ietf-idr-segment-routing-te-policy-05

 

  “ Typically, a controller defines the set of policies and advertise

   them to policy head-end routers (typically ingress routers).” 

 

How do we communicate SR policies from controller? Is it through BGP-SR session or PCEP session.

a. If it is through PCEP session what happens if the PCC is non-headend? 

b. If it is through BGP-SR what is the role for PCEP between PCE and PCC?

  “ Moreover, one or more route-target SHOULD be attached to the

   advertisement”

How Route-target should be attached to a SR-NLRI update? 

Is it done through local configuration or picked up based on some dynamic parameter?

   

Appreciate if you can help here.

 

 

Regards,

Chaitanya

 


..