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/
[routing-wg] Annoucing supernets in BGP?
- Previous message (by thread): [routing-wg] Annoucing supernets in BGP?
- Next message (by thread): [routing-wg] Fwd: Re: Annoucing supernets in BGP?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Thu Sep 13 12:18:49 CEST 2012
Florian Weimer wrote: > * Michael Markstaller: > > >>Is it good/best practice for Swisscom to announce 80/5 into BGP ? > > > IIRC, Swisscom does this so that its customers can use routers which > are not capable of processing the original DFZ, and still have some > redundancy. The advertisements should not leak to the general > Internet. ...whatever the merits of such a setup may be, imho at least minimal precautions SHOULD be applied, e.g. attaching a "no-export" tag? > If the prefixes end up in RIS, this could come from leakage > by a Swisscom customer (and another upstream which doesn't filter > properly), or a misconfigured BGP peering for the RIS data feed. Wilfried
- Previous message (by thread): [routing-wg] Annoucing supernets in BGP?
- Next message (by thread): [routing-wg] Fwd: Re: Annoucing supernets in BGP?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]