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/db-wg@ripe.net/
[db-wg] out of region routing in the RIPE Database
- Previous message (by thread): [db-wg] out of region routing in the RIPE Database
- Next message (by thread): [db-wg] out of region routing in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Fri Aug 11 03:13:22 CEST 2017
> That has proven to never really be an issue. When a network upstream > of another network says they don't support additional databases for > IRR, so far that has always proven to actually mean they've never > needed to think about supporting multiple databases, and never had the > demand to do the work to change that. > > In other words, it's not that they *can't* support other > databases. It's that they never have, and it's just the "way things > have been done". It's always ended up that they *can* support multiple > databases if asked to. when negotiating with a prospective peer, i would rather not add "you will have to change operational practice and code for this to work." randy
- Previous message (by thread): [db-wg] out of region routing in the RIPE Database
- Next message (by thread): [db-wg] out of region routing in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]