Geoff, I think you are voting for my option (1): retract draft and amend.
Correct?
--Sandy
On Thu, 9 Jun 2011, Geoff Huston wrote:
On 08/06/2011, at 5:56 PM, Randy Bush wrote:
Perhaps, but the issue you allude to is more about calling out routing
intention in each and every RFC that requests a reservation or special
use allocation from IANA.
not really. it's about the mess that is about to be made by (from the
document)
If IANA is directed to issue additional RPKI objects in future, this
document will be revised and a new version issued.
and before it is even published, a new version is needed. this is a
problem. we have a standard way of solving this problem, and iana
registry.
+1
In my opinion, it would be better to amend this doc to direct the IANA to set
up a registry and then use the registry update processes to make amendments as
and when required as distinct from pumping out -bis -bis bis etc etc cruft in
the RFCs
I firmly believe that the document structure is sound for what is
required for the timely deployment of RPKI.
-1
Geoff
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr