Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)

I know, I am very late with my support. I was unable to read the latest version of the document till now. 

I fully support the adoption (this happened already I know).

However, one thing I want to mention:

The technology described in the document is not really related to BGP Flowspec and even the title has been changed in the meantime:

	from
	BGP FlowSpec Extensions for Routing Policy Distribution (RPD) (-00)
	to
	BGP Extensions for Routing Policy Distribution (RPD) (-05)

I recommend using a different working-title for the draft as well (currently draft-li-idr-flowspec-rpd / draft-ietf-idr-flowspec-rpd) to avoid confusion with other flowspec related work in IDR (ie. draft-ietf-idr-bgp-rpd-00)

Cheers Christoph

-- 
Christoph Loibl
[email protected] | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at



> On 14.10.2019, at 21:18, Susan Hares <[email protected]> wrote:
> 
> This begins a 2 week WG adoption call for draft-li-idr-flowspec-rpd-05.txt 
> (10/14 to 10/28/2019).  You can access the draft at: 
>  
> https://datatracker.ietf.org/doc/draft-li-idr-flowspec-rpd/
>  
> In your discussion regarding this draft consider if:
>  
> 1)      Passing extended policy in BGP  is useful,
> 2)      Passing policy in wide community atom is a technical sound mechanism,
> 3)      A deployment need exists for this technology. 
>  
>  
> Susan Hares
> Co-chair and shepherd 
> _______________________________________________
> Idr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr