Owen,

On Feb 11, 2014, at 5:12 PM, Owen DeLong <[email protected]> wrote:
>> "The importance of maintaining accurate records in the RIPE database is 
>> recognised as the NCC's principal task. "
>> (well, ok, they spelled recognized wrong :))
> No, they spelled it the way the British do instead of the Americans.

It was, of course, a joke, as suggested by the ":)" characters.

>> Needs testing, in and of itself, is not the issue.  What is at issue is what 
>> ARIN does when a transfer occurs (and they have, do, and will occur) outside 
>> of "justified" need.  As a _registry_, I believe ARIN's role (as with IANA 
>> and all other RIRs) is to maintain accurate records.
> You've made your position clear. The majority of the ARIN community does not 
> appear to agree with you.

For some definition of a particular subset of the "ARIN community", it may be 
true that accuracy of registration information is secondary to imposing policy 
dictates.  I suspect, however, that for the vast majority of actual users of 
registration information that it is NOT the case.

This might be an interesting topic for an ARIN survey.

I'm curious: do you personally believe that accuracy of registration data is 
secondary to imposing policy dictates?

> Can you provide any evidence to support your claim that they "have, do, and 
> will occur outside of justified need"?

Of course not.  

Hint: according to current policy, such use of address space would be grounds 
for ARIN to "revoke" that address space.

I'd be surprised if you actually believe that folks are not fabricating 
justifications to get around the ARIN "justified need" requirements,

Regards,
-drc

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to