This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
Heads up: Long AS-sets announced in the next few days
- Previous message (by thread): Heads up: Long AS-sets announced in the next few days
- Next message (by thread): Heads up: Long AS-sets announced in the next few days
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurt Erik Lindqvist
kurtis at kurtis.pp.se
Thu Mar 3 10:53:12 CET 2005
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2005-03-03, at 10.27, Geoff Huston wrote: > >> On 2005-03-02, at 19.38, James A. T. Rice wrote: >> >> > This seems to suggest that you are just picking ASns at random to >> > inject into the paths, and that you don't have a set of ASs which >> you >> > have the assignees permission to use. >> >> Would't this then actually equate to resource hijacking along the >> lines >> of prefix hijacking? Who will be the first to hit the RIRs? > > Isn't this a case of illustrating how easy it is to tell lies in BGP > today? I don't > see what hitting the RIRs has do to with this. The problem appears to > be more > basic than that - its just too easy to tell lies in BGP and get the > lies propagated > globally. Well agreed. And that is an important point in itself. The reference to the RIRs was me trying to be ironic as when we have prefix hijacks that seems to be reported to the RIRs. - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.1 iQA/AwUBQibejKarNKXTPFCVEQKO6ACeIzkX5j04JA3RK3Y48fSsXM0DMLEAoM+k 6+j6phNoiKSg5Qai2CNSloLa =TWvV -----END PGP SIGNATURE-----
- Previous message (by thread): Heads up: Long AS-sets announced in the next few days
- Next message (by thread): Heads up: Long AS-sets announced in the next few days
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]