[arin-ppml] update section 203 proposal

[Rudolph Daniel]

John
Ripe605 made a recall from memory of discussions on the ppml probably
around the time I started participating on the list.
I simply have not made the time to dig back in the archives to refresh my
memory....I do remember a lengthy community discussion about legacy holders
and keeping resources within the region....of course things have changed
since then and I have been listening attentively to the recent exchanges
about inter RIR transfers....which I suspect may continue to evolve after
runout whilst the transition to ipv6 remains slower than we would all
ideally like to see....but there is a suggestion that the reassignments
ecosystem needs some kind of ongoing monitoring mechanism.

Rudi Daniel
(information technologist)
784 430 9235
 On Feb 23, 2014, at 11:50 AM, Rudolph Daniel <rudi.daniel at gmail.com>
wrote:

This may seem a stupid question, but since we now want to accept that
accuracy is a principle task of registries, what measure are we to use as
an acceptable measure of an accurate 'whois' or at the macro level, ' an
accurate registry service' ?......% of legacy holders participating on the
registry?

It's actually a fairly complicated question, since there are many legacy
holder who already
participate in the registry and update their resources (e.g. abuse contact,
DNS servers)
without any formal contractual relationship with ARIN.  In any case,
individual legacy holders
are unlikely to be the major contributor of inaccuracy in the registry when
compared to those
parties who fail to update the registry with their reassignment information
(despite the
requirement to do so per NRPM 4.2.3.7.)

 We do know that many folks are quite good about making updates before they
request
more IPv4 space, but that's unlikely to be a significant motivator for much
longer...

 FYI,
/John

 John Curran
President and CEO
ARIN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20140224/06a61a7c/attachment.htm>