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 ]
Daniel Shaw
daniel at afrinic.net
Fri Aug 11 07:44:43 CEST 2017
On 11/08/2017, 05:14, Randy Bush via db-wg typed: > >> >> 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." That is a good point. I would also rather not, generally. And that is the basis of my original fears around this something like a year ago. What I found in practise (so far) has been that when stated not as "you will *have* to change operations", but as "would it be possible for you to change operations for me?", the answer has usually been "Ok". I have to be honest, that was a surprise. - Daniel
- 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 ]