[129135] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Did your BGP crash today?

daemon@ATHENA.MIT.EDU (Mike Gatti)
Fri Aug 27 16:07:49 2010

From: Mike Gatti <ekim.ittag@gmail.com>
In-Reply-To: <4C781312.3010903@otd.com>
Date: Fri, 27 Aug 2010 16:07:36 -0400
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

where's the change management process in all of this.=20
basically now we are going to starting changing things that can=20
potentially have an adverse affect on users without letting anyone know
before hand .... Interesting concept.

On Aug 27, 2010, at 3:33 PM, Dave Israel wrote:

>=20
> On 8/27/2010 3:22 PM, Jared Mauch wrote:
>> When you are processing something, it's sometimes hard to tell if =
something
>> just was mis-parsed (as I think the case is here with the =
"missing-2-bytes")
>> vs just getting garbage.  Perhaps there should be some way to =
"re-sync" when
>> you are having this problem, or a parallel "keepalive" path similar =
to
>> MACA/MCAS/MIDCAS/TCAS between the devices to talk when something bad =
is
>> happening.
>=20
> I know it wasn't there originally, and isn't mandatory now, but there =
is
> an MD5 hash that can be added to the packet.  If the TCP hash checks
> out, then you know the packet wasn't garbled, and just contained
> information you didn't grok.  That seems like enough evidence to be =
able
> to shrug and toss the packet without dropping the session.
>=20
> -Dave
>=20
>=20
>=20

=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D
Mike Gatti =20
ekim.ittag@gmail.com
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D





home help back first fref pref prev next nref lref last post