24 Jun
2015
24 Jun
'15
9:19 a.m.
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