<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Bill, </div>
<div><br>
</div>
<div>Thank you for the feedback. My interpretation views the word from the perspective of the RIR responsible for the source resource. In the case of the ARIN region, the "dispute" could be a variance between who is trying to act as the source, and the organization
that ARIN has recorded in WHOIS. The same would apply to resources coming from other regions from the perspective of that region. It could also apply to a case where an organization wanted to act as a source for a block that is registered correctly in WHOIS,
but the resources are tied to a delinquent account.</div>
<div><br>
</div>
<div>I will work on getting staff's opinion on this. </div>
<div>-Dan</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Bill Darte <<a href="mailto:billdarte@gmail.com">billdarte@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Thu, 12 Apr 2012 04:53:07 -0700<br>
<span style="font-weight:bold">To: </span>Microsoft Office User <<a href="mailto:daniel_alexander@cable.comcast.com">daniel_alexander@cable.comcast.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [arin-ppml] ARIN-2012-1: Clarifying requirements for IPv4 transfers<br>
</div>
<div><br>
</div>
Dan,<br>
Thanks for this....<br>
<br>
Areas that are likely to be attacked (probably no too strong a term)....<br>
<br>
The term "dispute".....means what? Where would the dispute be evidenced..in court...on PPML...within/between the RIRs?<br>
Our old "share reciprocal, compatible, needs-based policies" will surely be divisive again.<br>
<br>
<br>
<br>
<div class="gmail_quote">On Wed, Apr 11, 2012 at 8:01 PM, Alexander, Daniel <span dir="ltr">
<<a href="mailto:Daniel_Alexander@cable.comcast.com">Daniel_Alexander@cable.comcast.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Here is the final 2012-1 text for the meeting in Vancouver. I am working<br>
on presentation slides so let me know if you have any feedback or thoughts<br>
that should be clarified during the meeting discussion. This text includes<br>
the word "transfers" in the 12 month restriction window placed on the<br>
source. This change was the result of previous mailing list discussions<br>
and feedback from Staff.<br>
<br>
Thanks,<br>
Dan<br>
<br>
<br>
Final text: 2012-1: Clarifying requirements for IPv4 transfers<br>
<br>
Replace Section 8.3 with<br>
<br>
8.3 Transfers between Specified Recipients within the ARIN Region.<br>
<br>
In addition to transfers under section 8.2, IPv4 numbers resources may be<br>
transferred according to the following conditions.<br>
<br>
Conditions on source of the transfer:<br>
<br>
* The source entity must be the current registered holder of the IPv4<br>
address resources, and not be involved in any dispute as to the status of<br>
those resources.<br>
* The source entity will be ineligible to receive any further IPv4 address<br>
allocations or assignments from ARIN for a period of 12 months after a<br>
transfer approval, or until the exhaustion of ARIN's IPv4 space, whichever<br>
occurs first.<br>
* The source entity must not have received a transfer, allocation, or<br>
assignment of IPv4 number resources from ARIN for the 12 months prior to<br>
the approval of a transfer request. This restriction does not include M&A<br>
transfers.<br>
* The minimum transfer size is a /24<br>
<br>
Conditions on recipient of the transfer:<br>
<br>
* The recipient must demonstrate the need for up to a 24 month supply of<br>
IP address resources under current ARIN policies and sign an RSA.<br>
* The resources transferred will be subject to current ARIN policies.<br>
<br>
<br>
Add Section 8.4 Inter-RIR Transfers to Specified Recipients<br>
<br>
Inter-regional transfers may take place only via RIRs who agree to the<br>
transfer and share reciprocal, compatible, needs-based policies.<br>
<br>
Conditions on source of the transfer:<br>
<br>
* The source entity must be the current rights holder of the IPv4 address<br>
resources recognized by the RIR responsible for the resources, and not be<br>
involved in any dispute as to the status of those resources.<br>
* Source entities outside of the ARIN region must meet any requirements<br>
defined by the RIR where the source entity holds the registration.<br>
* Source entities within the ARIN region will not be eligible to receive<br>
any further IPv4 address allocations or assignments from ARIN for a period<br>
of 12 months after a transfer approval, or until the exhaustion of ARIN's<br>
IPv4 space, whichever occurs first.<br>
* Source entities within the ARIN region must not have received a<br>
transfer, allocation, or assignment of IPv4 number resources from ARIN for<br>
the 12 months prior to the approval of a transfer request. This<br>
restriction does not include M&A transfers.<br>
* The minimum transfer size is a /24.<br>
<br>
<br>
Conditions on recipient of the transfer:<br>
<br>
* The conditions on a recipient outside of the ARIN region will be defined<br>
by the policies of the receiving RIR.<br>
* Recipients within the ARIN region will be subject to current ARIN<br>
policies and sign an RSA for the resources being received.<br>
* Recipients within the ARIN region must demonstrate the need for up to a<br>
24 month supply of IPv4 address space.<br>
* The minimum transfer size is a /24<br>
<br>
<br>
Rationale:<br>
<br>
The original text of this proposal attempted to clarify the requirements<br>
of an IPv4 address transfer while protecting any resources remaining in<br>
the ARIN free pool. This revision is a result of feedback from the mailing<br>
list, ARIN Staff, and discussions with the original author. The one key<br>
point that has been removed from the original text is that a needs based<br>
review remains in place.<br>
<br>
The current text attempts to retain the original concepts of protecting an<br>
ARIN free pool, and incorporating it with the point of bringing resources<br>
under RSA. The resulting text attempts to put safeguards in place on the<br>
practice of paid transfers by creating a black out period for transfers<br>
and requests to the free pool. The text also tries to incorporate<br>
discussions regarding inter-RIR transfers and come up with language that<br>
includes the free pool protections for transfers in and out of the Region.<br>
<br>
Timetable for implementation: immediate.<br>
<br>
<br>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
</blockquote>
</div>
<br>
</span>
</body>
</html>