Re: [Idr] Working Group adoption call for draft-previdi-idr-segment-routing-te-policy (6/15 to 6/29/2017)

[stefano previdi <[e-mail]>]

Gunter,

I think you should read draft-filsfils-spring-segment-routing-policy. It will give you a better understanding on what a SR policy is and why having different ways to signal it it’s a _good_ thing.

Thanks for the support.
s.


> On Jun 20, 2017, at 6:46 PM, Van De Velde, Gunter (Nokia - BE/Antwerp) <[e-mail]> wrote:
> 
> Hi Sue, John,
>  
> Support, the idea is one of many others to serve the same goal to distribute TE policies, however using BGP based signalling this time.
>  
> Not sure to which solution the future implementations will converge towards at the end, but this method of using BGP SR signalling seems reasonable pragmatic approach with few potential interesting use-case scenarios. My worry is regarding its value in few years from now and that we might be wasting IDR cycles. But I do think that it’s a pragmatic thing to work on now, assuming it does not take years for it to get through the IETF process.
>  
> G/
>  
>  
>  
>  
> From: Idr <[e-mail]> on behalf of Susan Hares <[e-mail]>
> Date: Friday, 16 June 2017 at 03:44
> To: "[e-mail]" <[e-mail]>
> Cc: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>
> Subject: [Idr] Working Group adoption call for draft-previdi-idr-segment-routing-te-policy (6/15 to 6/29/2017)
>  
> IDR WG:  
>  
> This begins a 2 week WG adoption call for draft-previdi-idr-segment-routing-te-policy (6/15/2017 to 6/29/2017)   You can obtain the draft at:
> https://datatracker.ietf.org/doc/draft-previdi-idr-segment-routing-te-policy/
>  
> Please note there is an IPR claim on this draft.  If you are interested in this area, but do not wish to accept this draft due to its IPR – please indicate this in your response to the this WG adoption call.   
>  
> Sue and John