[129203] in North American Network Operators' Group
Re: Complain to your vendors (was Re: Did your BGP crash today?)
daemon@ATHENA.MIT.EDU (Paul Ferguson)
Sun Aug 29 03:40:20 2010
In-Reply-To: <20100829073529.GA9681@skywalker.creative.net.au>
Date: Sun, 29 Aug 2010 00:40:11 -0700
From: Paul Ferguson <fergdawgster@gmail.com>
To: Adrian Chadd <adrian@creative.net.au>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Aug 29, 2010 at 12:35 AM, Adrian Chadd <adrian@creative.net.au>
wrote:
> Guys/girls/furry-creatures-from-!Earth,
>
> Complaining on nanog-ml is likely to only achieve personal stress relief.
>
> This is something you should bring up with your vendor. Say that you'll
> move vendors if they don't start making "better" BGP implementations and
> adding the features you guys want. Make the list of "better" features
> open, public, and actively solicit alternatives. Follow up on your
> threat. This is your business bottom line after all.
>
> Don't just use it as a reason to get lower prices from your current
> vendor and then continue complaining when dumb crap like this occurs.
>
> It would be great if vendor(s) participated in a public interoperability
> test suite where researchers could test their stuff against it before
> unleashing it on the public internet. I'd love to see something public
> -and- cross institutional, -and- include access to things like CRS-level
> equipment.
>
> Go on, I dare you. :)
>
Maybe the NANOG conference committee (or whatever its called) could get a
couple of major router vendor gerbils to come to the next NANOG and talk to
this issue?
Maybe?
Okay, I give up.
- - ferg
-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.5.3 (Build 5003)
wj8DBQFMeg7Uq1pz9mNUZTMRAtLzAJwNzJMf4YwjP9C42CFANvESJCVoDQCg9trZ
lS5Wd5kpH27JBLKkDhibIOg=3D
=3DfdTs
-----END PGP SIGNATURE-----
--=20
"Fergie", a.k.a. Paul Ferguson
=A0Engineering Architecture for the Internet
=A0fergdawgster(at)gmail.com
=A0ferg's tech blog: http://fergdawg.blogspot.com/
