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] Temporary origins
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Wed Jun 24 09:19:27 CEST 2015
>>> We need to allow for more than one AS to be authorised to announce >>> an origin for a prefix, even though we expect only one originator to >>> announce normally. >> >> the use case that is critical for me here is that a non-bgp prefix >> owner may wish to switch upstram providers. both upstream ASs need to >> be authorized at the same time in order to move make before break. > > Already today the RIPE database supports this, you can create multiple > route-objects covering the same prefix but with different "origin:" > values. been aware of this for a couple of decades. my point was that, if snash is gonna write specs, and moas is the main motivation, it is the wrong main motivation. randy
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]