[arin-ppml] SWIPs & IPv6

The parameters for ARIN's operations should be broader than "the minimum required by law." 

One of the most interesting debates in this community was the meeting discussion of Policy Proposal 2005-2: Directory Services Overhaul.
It seemed that as we began the topic during the meeting, the community was leaning toward privacy.  We had input from some members of our community, who are also members of several governments' agencies, which I think persuaded the community.

That was almost five years ago, and certainly opinions may change.  Debate is good; informed debate is even better.   So, take ten minutes to read the minutes from ARIN XV on 2005-2.


From: Milton L Mueller <mueller at>
To: John Curran <jcurran at>; Chris Engel <cengel at>
Cc: "arin-ppml at" <arin-ppml at>
Sent: Fri, December 4, 2009 10:55:43 AM
Subject: Re: [arin-ppml] SWIPs & IPv6

This is precisely what I fear. An expansive definition of the RIRs role can easily make them enforcement arms of the copyright industry . RIRs should serve a very narrow purpose and any additional loading of functions onto them must come from laws enacted by representative legislators subject t constitutional constraints, not by little bands of engineers trying to be "helpful" 
From: arin-ppml-bounces at [arin-ppml-bounces at] On Behalf Of John Curran [jcurran at]

Chris - There's several reasons that have been cited in the past for having to know the holder of a block, and while that includes the law enforcement angle, there's also abuse & copyright mitigation, operational attack response, and end-to-end network problem diagnosis.  I haven't been running a network personally in a few years, so I don't know the extent to which these are still valid but mention them for consideration.

You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at
Unsubscribe or manage your mailing list subscription at:
Please contact info at if you experience any issues.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>