[94003] in North American Network Operators' Group
Re: RIS [Re: AS41961 not seen in many networks]
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Fri Jan 5 12:48:05 2007
Date: Fri, 05 Jan 2007 17:46:23 +0000
From: Jeroen Massar <jeroen@unfix.org>
To: Randy Bush <randy@psg.com>
Cc: Pekka Savola <pekkas@netcore.fi>,
Sebastian Rusek <SRusek@axit.pl>, nanog@merit.edu
In-Reply-To: <17822.36050.114662.484794@roam.psg.com>
Errors-To: owner-nanog@merit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE1F4160FB9EEE4B5D4AFA991
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Randy Bush wrote:
>> Well, the undocumented fact is that RIS does not accept multi-hop BGP =
>> peerings, which may somewhat limit its coverage.
>=20
> this is a good thing. as multi-hop bgp is very fragile, measurements
> go borkville just when you want them the most.
While that is true, it does help in the cases when there is connectivity
between the two BGP speakers in question. For instance GRH would not
have been possible if it was not for multihop-bgp. Indeed when
connectivity breaks, it is useless, but most of the time it works and
then it is great to have.
A better requirement for RIS could be that it would be advised to be
present at an IX and peer there, otherwise offer the option of
multihop-bgp so that people who are not too-well connected can also
contribute to it. The ones present at the IX's are also the ones which
will cause multihop to break when the IX or they themselves go down, the
remote participants are most likely smaller players thus them going down
and going off the system doesn't really hurt a lot, except them.
Greets,
Jeroen
--------------enigE1F4160FB9EEE4B5D4AFA991
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/
iHUEARECADUFAkWeju8uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I2QhAKCIkQssmsQM8lHb4ybLzawFhzCv
ZgCcCpxUKbMZPZ8yORJlTTRC0t/htLY=
=0n4c
-----END PGP SIGNATURE-----
--------------enigE1F4160FB9EEE4B5D4AFA991--
