[db-wg] Temporary origins

Thanks for comments.  My interest was to continue the discussion that 
Job hosted at RIPE70, and to get to some guidelines for those that need 
to exploit temporary redirection with BGP; whether customers or 
providers of services.

Job, thanks for your observation that  "the RIPE database supports this, 
you can create multiple route-objects covering the same prefix but with 
different "origin:" values.".  Randy states agreement.
However, this does conflict with some other Internet documents, like 
BCP-6.  That can only be confusing and may inhibit global consensus.  If 
IETF BCP documents are inaccurate then the RIPE community has some 
responsibility to point it out.

The dual authorisation that RIPE requires on a ROUTE object seems an 
unnecessary hurdle, and gives rise to the cross-border concern that Job 
raised in the BoF.

The consensus from RPKI seems to be that the inetnum maintainer has the 
authority to grant ROA.
I do not know the history of why RIPE asks for AS maintainer also.  Is 
there still some good reason?  (If so, I am puzzled that it does not 
apply to RPKI, but that is a separate discussion).
Removing the AS maintainer from the route object Creation authorisation 
seems to solve the cross-region problem.
Are there reasons not to do this?
Job mentioned that RaDB seems to have neither authorisation requirement, 
so creating a global view of the IRR is challenging without policy 
agreement leading to trust on these things.

Summary:
1/ ask IETF to update BCP-6.  Is this something RIPE NCC should do?
2/ discuss why AS maintainer authorisation is required for RIPE ROUTE 
object Creation.

I subsequently read the article by Den Is  May 2015, which comments that 
there is no written policy for IRR.

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20150624/daff63a4/attachment.html>