[Idr] Re: [Core] draft-haas-idr-bgp-attribute-escape-04 - WG Adoption call (6/2 to 6/16/2026).

[Job Snijders <[e-mail]>]

I support WG adoption of draft-haas-idr-bgp-attribute-escape-04

Kind regards,

Job

On Tue, Jun 02, 2026 at 11:19:21PM +0000, Susan Hares wrote:
> This begins a 2-week WG adoption call for draft-haas-idr-bgp-attribute-escape-04.txt (6/2/2026 to 6/16/2026).
> 
> The author should respond to this email with an IPR statement.
> 
> WG Members - please comment on this adoption, and in your comments mention "support or no support.
> 
> A few things from the abstract may be helpful in your reading of this draft:
> 
> 1) This is an informational draft.
> 2) The focus is "optional transitive attributes" for BGP that "escape" inadvertently beyond intended scope
> 3) Jeff Haas feels this will help writers of new drafts correctly use these optional transitive attributes.
> 
> Cheerily, Sue Hares
> (Shepherd)
> 
> -----------
> 
> Excerpts from Abstract text:
> 
>    A significant part of the success of [RFC4271] BGP is
>    due to its ability to incrementally add new features to its Path
>    Attributes when they are marked "optional transitive".
>    Implementations that are ignorant of a feature for an unknown Path
>    Attribute that are so marked will propagate BGP routes with such
>    attributes.
> 
>    Unfortunately, this blind propagation of unknown Path Attributes may
>    happen for features that are intended to be used in a limited scope.
>    When such Path Attributes inadvertently are carried beyond that
>    scope, it can lead to things such as unintended disclosure of
>    sensitive information, or cause improper routing.  In their worst
>    cases, such propagation may be for malformed Path Attributes and lead
>    to BGP session resets or crashes.
> 
>    This document calls such inadvertent propagation of BGP Path
>    Attributes, "attribute escape".  This document further describes some
>    of the scenarios that leads to this behavior and makes
>    recommendations on practices that may limit its impact.
> 

> _______________________________________________
> Idr mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]