Re: [Idr] WG Last Call foir draft-ietf-idr-bgp-extended-messages (11/12 to 11/26)

[Job Snijders <[e-mail]>]

On Wed, Nov 15, 2017 at 02:56:01PM +0100, Robert Raszuk wrote:
> I am concerned with the lack of clear description of what router which
> supports extended msg should do when on one side he receives an
> attribute bigger then 4K and not of all it's peers can handle it.
> 
> IMO the below statement is true but a bit too vague:
> 
> "Therefore putting an attribute which can not be decomposed to 4096
> octets or less in an Extended Message is a likely path to routing
> failure."
> 
> And the worst part is that the BGP speaker which in fact generated
> such attribute be it on purpose or by error will not find out that its
> propagation has failed one or N hops away.
> 
> Today when one is trying to inject msg over 4K (say due to a bug) it
> will fail locally, generate syslog etc ... 
> 
> Any comments from authors and WG on that ?

Let's not forget this draft idea has been around since 2011. To prevent
path / routing failures, we'd better get a move on and start deplying.

Kind regards,

Job