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]More specific prefix announce
- Previous message (by thread): [routing-wg]More specific prefix announce
- Next message (by thread): [routing-wg]More specific prefix announce
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Arnold Nipper
arnold.nipper at de-cix.net
Fri Sep 2 14:33:15 CEST 2005
On 02.09.2005 11:12 Michael Hallgren wrote >> It is not disallowed. What's more - it is common practice to >> perform incoming capacity engineering in this way. > > But, IMHO, preferably in a multiple interconnection to a single AS scenario > only (having that AS export the shortest prefix only). > Imho, the AS in questionn should export both the aggregate and the more specifics, but set community no-export to the more specifics ... Arnold -- Arnold Nipper / DE-CIX Management GmbH, the German Internet Exchange e-mail: arnold.nipper at de-cix.net phone/mob: +49 172 265 0958 fax: +49 6224 9259 333 http://www.de-cix.net pgp-fingerprint: e533 5cc5 be27 27ae 04b7 0adc 2603 f8a9 1b59 3bd4
- Previous message (by thread): [routing-wg]More specific prefix announce
- Next message (by thread): [routing-wg]More specific prefix announce
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]