+grow/sidrops

Please note that while the bulk of the work for the draft, "don't use as-sets" 
has long been a BCP, this draft makes recommendation for how aggregation is 
done and the AS_PATH as used for RPKI purposes.  Your operational scrutiny is 
appreciated in this last call.

-- Jeff


> Begin forwarded message:
> 
> From: Susan Hares <sha...@ndzh.com>
> Subject: [Idr] WG LC for draft-ietf-idr-deprecate-as-set-confed-set-14 (7/8 
> to 7/
> Date: July 8, 2024 at 9:35:43 PM EDT
> To: "i...@ietf.org" <i...@ietf.org>
> 
> This begins a 2 week WG LC for
> draft-ietf-idr-deprecate-as-set-confed-set-14.txt
> https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/ 
> <https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/>
>  
> All authors should respond to this email with an IPR statement.
>  
> Here is a short summary of why this document is:
>  
>    BCP 172 (i.e., RFC 6472) recommends not using AS_SET and
>    AS_CONFED_SET AS_PATH segment types in the Border Gateway Protocol
>    (BGP).  This document advances that recommendation to a standards
>    requirement in BGP; it proscribes the use of the AS_SET and
>    AS_CONFED_SET path segment types in the AS_PATH. 
>  
> FYI the verb proscribe means:
> forbid, especially by law.
> denounce or condemn.
>  
> It is a complex English word, but it fits the document.
> One similar word is “prohibit”.
>  
> Questions to consider in your comments:
>  
> Is now the time to proscribe AS_SETs and
> AS-CONF_SET path segments types in AS_PATH?
>  
> Is the document clear and ready for standardization?
>  
>     Both Keyur and I wrote shepherd reports,
>     so we’ll post a joint shepherd report.
>  
>     Our comments focus on the clarity of the document.
>  
> Does this help BGP security in the network?
>  
>  
> Cheers, Sue 
>  
>  
>  
> _______________________________________________
> Idr mailing list -- i...@ietf.org <mailto:i...@ietf.org>
> To unsubscribe send an email to idr-le...@ietf.org <mailto:idr-le...@ietf.org>
_______________________________________________
GROW mailing list -- grow@ietf.org
To unsubscribe send an email to grow-le...@ietf.org

Reply via email to