[147140] in North American Network Operators' Group
Re: bgp update destroying transit on redback routers ?
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Fri Dec 2 16:07:27 2011
In-Reply-To: <20111202143554.GA66539@snar.spb.ru>
Date: Fri, 2 Dec 2011 16:06:31 -0500
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Alexandre Snarskii <snar@snar.spb.ru>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, Dec 2, 2011 at 9:35 AM, Alexandre Snarskii <snar@snar.spb.ru> wrote:
> This draft says that
...note it's a DRAFT, not a STANDARD...
>
> If a BGP speaker receives a route which has an AS number of zero in the
> AS_PATH (or AS4_PATH) attribute, it SHOULD be logged and treated as a
> WITHDRAW. This same behavior applies to routes containing zero as the
> Aggregator or AS4 Aggregator.
>
> but observed behaviour was more like following:
>
> If a BGP speaker receives [bad route] it MUST close session immediately
> with NOTIFICATION Error Code 'Update Message Error' and subcode 'Error with
> optional attribute'.
hence this old behavor
