[arin-ppml] ARIN-prop-133: No Volunteer Services on Behalf of Unaffiliated Address Blocks
On Mon, Feb 14, 2011 at 4:21 PM, Matthew Kaufman <matthew at matthew.at> wrote:
> On 2/14/2011 1:18 PM, Jeffrey Lyon wrote:
>> On Mon, Feb 14, 2011 at 4:15 PM, Matthew Kaufman<matthew at matthew.at>
>>> Opposed. Making Whois information about legacy blocks invisible removes
>>> ability for individuals and organizations to continue to "self-police"
>>> of this space. As an example, if I am an ISP with a customer who claims
>>> hold a legacy block and who wants it routed, where do I verify that if
>>> the whois database? It similarly interferes with any future transfer
>>> by making it impossible to do even the most rudimentary check on the
>>> seller's claims.
>>> Matthew Kaufman
>>> You are receiving this message because you are subscribed to
>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> Please contact info at arin.net if you experience any issues.
>> ARIN would provide referral WHOIS. Couldn't you just use this information?
> Referral to what?
> Someone who's had a legacy class C since 1992 comes to you and says "hi, I
> moved and am now your customer, I'd like you to route this block to me". Who
> has a listing for that address if this policy takes effect?
> Note that "tell the customer to go sign an LRSA first" isn't an acceptable
> answer either, as many holders have many reasons (some no doubt even
> legitimate) for not signing the LRSA.
> Matthew Kaufman
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
It seems like the intent is that they would create their own RWHOIS?
Jeffrey Lyon, Leadership Team
jeffrey.lyon at blacklotus.net | http://www.blacklotus.net
Black Lotus Communications - AS32421
First and Leading in DDoS Protection Solutions