I am very disappointed. I don't expect anyone to go and fix ARIN.
I am simply posting to express myself.
nevertheless i hope that you will help fix ARIN if it's broken. but
in this case i think what's broken is bigger than ARIN. the community
badly needs a way to allocate addresses, which as in your example, are
unlikely to appear in the global routing table (sometimes called "DFZ").
these addresses should have whois, in-addr, and so on, so that they can
be used in "ubiquitous manet"'s and ad-hoc wireless. given that the
internet core can't handle growth of PI, and no large internet entity
in their right mind would use PA, it is past time to end what i call
"the tyrrany of the core".
http://sa.vix.com/~vixie/ula-global.txt has my thoughts on this, which
i've appropriated without permission from hinden, huston, and narten
and inaccurately failed to remove their names from (since none of them
supports the proposal). in fact, nobody in the ietf intelligensia
supports the proposal. the showstopped is that this appears to many as
an end-run around PI, and the fear is that there's no way to prevent it
from all getting routed anyway. while that's not an unreasonable fear,
i'm alone in considering it a manageable risk. there's also a problem
in that the only way to get new address policy through to the RIRs is
now the global RIR policy process -- it's not a matter of IAB telling
IANA what to do like in the old days.
so while i harken to your concern that "IPv6 will never fly", i think
that the reasons for it are much larger than whatever part you think
ARIN could do differently. but as to that part, please listen to sam
weiler who spoke the truth as i know it when he said:
It is remarkably easy to get involved with the ARIN public policy
procecss and submit a proposal to change its v6 assignment policies. I
encourage you to do so.
-- Sam
paul
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf