[arin-ppml] ARIN-prop-136 Services Opt-out Allowed for Unaffiliated Address Blocks

Owen DeLong owen at delong.com
Thu Feb 24 18:36:38 EST 2011


I keep hearing this, but, it remains to be seen whether that is actually true or mere fantasy.

Fact: transfers which take place outside of the ARIN policy framework, there are a number
of risks:

	1.	ARIN will likely de-register any space transferred outside of policy as this is
		a clear violation of the terms under which the space was registered (even if
		it is legacy space) and the registration is, thus, void.

	2.	Once ARIN has deregistered such space, it will likely be registered to another
		organization within the ARIN policy framework and under RSA.

	3.	Many ISPs will likely be unwilling to route addresses which are not listed
		in the ARIN database as belonging to the entity requesting the route. This
		is not under the direct control of ARIN or the policy process, so, the extent
		of this is unknown and unpredictable, but, it is most certainly a risk being
		taken by any business transferring resources outside of policy.

Milton is right... Prop 136 is not an attack on legacy holders. It is an attack on the
ARIN community and our bottom up consensus driven policy process purporting
to be conducted on behalf of legacy holders.

Owen

On Feb 24, 2011, at 3:25 PM, Milton L Mueller wrote:

> There is a real problem to solve. I am surprised you cannot see it. As ipv4 addresses become scarcer and more valuable while the need for them continues for at least a decade, and a transfer market develops, the economic stakes associated with legacy holdings and transfers rise considerably. It's quite likely that many of these transfers will take place outside of ARIN's framework due to the unwillingness of market participants to subject themselves to ARIN's peculiar methods. If legacy holders don't have an explicit right to opt out, and use alternative, compatible registration services, then the "untraceable mess" Tony Hain warned us about will develop. {Reference: "Proposal insanity"]
> 
> --MM
> 
>> -----Original Message-----
>> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
>> Behalf Of Frank Bulk
>> Sent: Thursday, February 24, 2011 12:38 AM
>> To: arin-ppml at arin.net
>> Subject: Re: [arin-ppml] ARIN-prop-136 Services Opt-out Allowed for
>> Unaffiliated Address Blocks
>> 
>> Unless someone demonstrates that there is a pressing issue or problem, I
>> am opposed to this proposal.  I understand that legacy address holders
>> may be unrepresented in the policy development process, so others will
>> have to pipe up if they can help clarifiy.
>> 
>> This is not the first proposal by Mr. Schliesser where the cart seems to
>> be before the horse.  Let's not create or modify policies unless there's
>> a real problem to solve or a great opportunity.
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
>> Behalf Of ARIN
>> Sent: Wednesday, February 23, 2011 7:48 PM
>> To: arin-ppml at arin.net
>> Subject: [arin-ppml] ARIN-prop-136 Services Opt-out Allowed for
>> Unaffiliated Address Blocks
>> 
>> ARIN-prop-136: Services Opt-out Allowed for Unaffiliated Address Blocks
>> 
>> ARIN acknowledges receipt of the policy proposal that can be found
>> below.
>> 
>> The ARIN Advisory Council (AC) will review the proposal at their next
>> regularly scheduled meeting (if the period before the next regularly
>> scheduled meeting is less than 10 days, then the period may be extended
>> to the subsequent regularly scheduled meeting). The AC will decide how
>> to utilize the proposal and announce the decision to the PPML.
>> 
>> The AC invites everyone to comment on the proposal on the PPML,
>> particularly their support or non-support and the reasoning behind their
>> opinion. Such participation contributes to a thorough vetting and
>> provides important guidance to the AC in their deliberations.
>> 
>> Draft Policies and Proposals under discussion can be found at:
>> https://www.arin.net/policy/proposals/index.html
>> 
>> The ARIN Policy Development Process can be found at:
>> https://www.arin.net/policy/pdp.html
>> 
>> Mailing list subscription information can be found
>> at: https://www.arin.net/mailing_lists/
>> 
>> Regards,
>> 
>> Communications and Member Services
>> American Registry for Internet Numbers (ARIN)
>> 
>> 
>> ## * ##
>> 
>> 
>> ARIN-prop-136: Services Opt-out Allowed for Unaffiliated Address Blocks
>> 
>> Proposal Originator:  Benson Schliesser
>> 
>> Proposal Version:  1
>> 
>> Date:  23 Feb 2011
>> 
>> Proposal type:  New
>> 
>> Policy term:  Permanent
>> 
>> Policy statement:
>> 
>> Add the following to the NRPM:
>> 
>> 13.  Unaffiliated Address Blocks
>> 
>> 13.x. Opt-out Allowed
>> 
>> ARIN provides IP address registry services to all IP address holders in
>> the ARIN region, for all IP address resources that are not registered by
>> another RIR, regardless of whether any given address holder has entered
>> into a services agreement.  However, ARIN will cease providing any
>> registry services for specific IP address resources in the event that
>> the legitimate address holder of an unaffiliated address block, that is
>> an address block that is not covered by an ongoing services agreement,
>> chooses to opt-out of receiving any or all registry services from ARIN.
>> 
>> 13.x.1. Requirements for Whois Opt-out
>> 
>> In order for an opt-out request for Whois directory services to be
>> valid, the legitimate address holder must agree to provide a replacement
>> directory service reflecting operationally accurate allocation and
>> assignment information for the specified IP number resources.  ARIN will
>> create generic placeholder entries in the ARIN Whois directory for all
>> IP number resources that are removed due to opt-out, and each
>> placeholder entry will include a reference and/or RWhois referral to the
>> replacement directory service.
>> 
>> 
>> Rationale:
>> 
>> This proposal does not seek to replace ARIN-prop-133 but is offered as
>> an exclusive alternative for consideration by the ARIN community, in
>> order to address concerns that it would unfairly harm legacy address
>> holders and/or cause unnecessary damage to the Whois database.
>> 
>> Policy Background:
>> 
>> This policy attempts to clarify the relationship that ARIN has with
>> legacy address holders.
>> 
>> Specifically, this policy recognizes that absent an agreement such as
>> the RSA or LRSA there is no formal relationship with legacy address
>> holders.  At present, however, ARIN continues to provide services to
>> these organizations.  This is done without compensation and potentially
>> in opposition to the legacy address holders' wishes.  As a result of
>> this behavior ARIN has created an illusion of implied authority that
>> exposes ARIN to unacceptable levels of liability, is hindering the
>> development of an open address market (driving it "underground"), and is
>> putting the operational stability of the Internet at risk.  As new
>> services such as RPKI are contemplated this situation becomes even more
>> critical.
>> 
>> This policy assumes the tacit consent of all address holders in the ARIN
>> region, to receive ARIN registry services and to be governed by ARIN
>> policy, but allows for legitimate address holders of unaffiliated
>> address blocks to explicitly opt-out of any and/or all services.  This
>> approach would allow ARIN to continue providing volunteer services to
>> any member of the legacy community as long as this service was not
>> contrary to their wishes.  Further, it would allow legacy address
>> holders to opt-out of some services such as Whois while continuing to
>> receive other services such as in-addr DNS reverse mapping.
>> 
>> In the event that a legacy address holder does opt-out of Whois
>> directory services under this policy, ARIN would require the address
>> holder to provide a replacement directory service and would continue to
>> provide a Whois pointer (such as a RWhois referral) to that service.  As
>> a result, the integrity of the distributed Whois database would remain
>> intact and be improved.
>> 
>> Timetable for implementation:  Immediately
>> 
>> 
>> 
>> _______________________________________________
>> PPML
>> 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:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>> 
>> _______________________________________________
>> PPML
>> 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:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
> _______________________________________________
> PPML
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.




More information about the ARIN-PPML mailing list