Send ARIN-PPML mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.arin.net/mailman/listinfo/arin-ppml
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-PPML digest..."
Today's Topics:
1. Advisory Council Meeting Results - December 2012 (ARIN)
2. LAST CALL - Draft Policy ARIN-2012-6: Revising Section 4.4
C/I Reserved Pool Size (ARIN)
3. LAST CALL - Draft Policy ARIN-2012-8: Aligning 8.2 and 8.3
Transfer Policy (ARIN)
4. Weekly posting summary for [email protected] (Thomas Narten)
----------------------------------------------------------------------
Message: 1
Date: Thu, 27 Dec 2012 14:16:08 -0500
From: ARIN <[email protected]>
To: [email protected]
Subject: [arin-ppml] Advisory Council Meeting Results - December 2012
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
In accordance with the ARIN Policy Development Process, the ARIN
Advisory Council (AC) held a meeting on 20 December 2012 and made
decisions about draft policies and proposals.
The AC moved the following draft policies to last call (they will be
posted separately to last call):
ARIN-2012-6: Revising Section 4.4 C/I Reserved Pool Size
ARIN-2012-8: Aligning 8.2 and 8.3 Transfer Policy
The AC is continuing to work on the following:
ARIN-2012-2: IPv6 Subsequent Allocations Utilization Requirement
ARIN-prop-182 Update Residential Customer Definition to not exclude
wireless as Residential Service
ARIN-prop-183 Section 8.4 Transfer enhancement
Draft Policy and Proposal texts are available 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
Regards,
Communications and Member Services
American Registry for Internet Numbers (ARIN)
------------------------------
Message: 2
Date: Thu, 27 Dec 2012 14:18:01 -0500
From: ARIN <[email protected]>
To: [email protected]
Subject: [arin-ppml] LAST CALL - Draft Policy ARIN-2012-6: Revising
Section 4.4 C/I Reserved Pool Size
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
The ARIN Advisory Council (AC) met on 20 December 2012 and decided to
send the following draft policy to last call:
Draft Policy ARIN-2012-6: Revising Section 4.4 C/I Reserved Pool Size
The AC revised the text after the ARIN XXX Public Policy Meeting and
asked for an updated staff assessment of the revised text. The
assessment is available at:
https://www.arin.net/policy/archive/2012_6_staff_assessment.html
Feedback is encouraged during the last call period. All comments should
be provided to the Public Policy Mailing List. Last call for 2012-6 will
expire on 15 January 2013. After last call the AC will conduct their
last call review.
The draft policy text is below and available at:
https://www.arin.net/policy/proposals/
The ARIN Policy Development Process is available at:
https://www.arin.net/policy/pdp.html
Regards,
Communications and Member Services
American Registry for Internet Numbers (ARIN)
## * ##
Draft Policy ARIN-2012-6
Revising Section 4.4 C/I Reserved Pool Size
Date: 27 December 2012
Policy statement:
4.4. Micro-allocation ARIN will make IPv4 micro-allocations to critical
infrastructure providers of the Internet, including public exchange
points, core DNS service providers (e.g. ICANN-sanctioned root and ccTLD
operators) as well as the RIRs and IANA. These allocations will be no
smaller than a /24. Multiple allocations may be granted in certain
situations.
Exchange point allocations MUST be allocated from specific blocks
reserved only for this purpose. All other micro-allocations WILL be
allocated out of other blocks reserved for micro-allocation purposes.
ARIN will make a list of these blocks publicly available.
Exchange point operators must provide justification for the allocation,
including: connection policy, location, other participants (minimum of
two total), ASN, and contact information. ISPs and other organizations
receiving these micro-allocations will be charged under the ISP fee
schedule, while end-users will be charged under the fee schedule for
end-users. This policy does not preclude exchange point operators from
requesting address space under other policies.
ARIN will place an equivalent of a /16 of IPv4 address space in a
reserve for Critical Infrastructure, as defined in section 4.4. If at
the end of the policy term there is unused address space remaining in
this pool, ARIN staff is authorized to utilize this space in a manner
consistent with community expectations.
ICANN-sanctioned gTLD operators may justify up to the equivalent of an
IPv4 /23 block for each authorized new gTLD, allocated from the free
pool or received via transfer, but not from the above reservation. This
limit of a /23 equivalent per gTLD does not apply to gTLD allocations
made under previous policy.
Rationale:
Additional ICANN-sanctioned DNS infrastructure is being added to the
Internet and in quantities greater than anticipated when the micro
allocation proposal was written and adopted.
The original CI pool was created to serve new IXP and new CI
requirements. The pending need is estimated to be over 1000 new gTLD
range, which may exhaust the current /16 reservation before the ARIN
free pool is exhausted. Once the current /16 reservation is exhausted,
CI providers would no longer be eligible to receive address space,
either via the general free pool or via transfer.
The original proposal dealt with this by expanding the reservation to a
/15 and allowing CI to draw from the free pool instead of the
reservation until it gets down to a /8. The consensus coming out of the
Dallas meeting seems to be that this is an inadequate solution. As the
new expanded gTLD demand will obliterate any reasonable reservation,
leaving no resources for the other IXP and CI demands that the original
reservation was intended to serve. It is therefore, not possible to
services them both out of a common reservation.
In order to ensure continued access to IPv4 number resources by new IXP
and DNS operators alike, the AC is modifying the proposal going into
last call to allow gTLD operators to continue to qualify for micro
allocations from the general free pool or via transfer only, and leaving
one /16 reserved for IXP, root, and ccTLD DNS operators.
As a result of the close examination of the CI policy brought about by
this proposal, the AC has identified a number of issues in the original
policy text that should be addressed. However, the AC is intentionally
minimizing the overall changes to this proposal as much as possible for
last call in keeping with the spirit of the PDP. The AC intends to make
future proposals to deal with these other concerns. The current proposal
addresses issues of some urgency and we did not want to delay it to
another policy cycle as a result.
------------------------------
Message: 3
Date: Thu, 27 Dec 2012 14:18:21 -0500
From: ARIN <[email protected]>
To: [email protected]
Subject: [arin-ppml] LAST CALL - Draft Policy ARIN-2012-8: Aligning
8.2 and 8.3 Transfer Policy
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
The ARIN Advisory Council (AC) met on 20 December 2012 and decided to
send the following draft policy to last call:
Draft Policy ARIN-2012-8: Aligning 8.2 and 8.3 Transfer Policy
The AC revised the text after the ARIN XXX Public Policy Meeting and
asked for an updated staff assessment of the revised text. The
assessment is available at:
https://www.arin.net/policy/archive/2012_8_staff_assessment.html
Feedback is encouraged during the last call period. All comments should
be provided to the Public Policy Mailing List. Last call for 2012-8 will
expire on 15 January 2013. After last call the AC will conduct their
last call review.
The draft policy text is below and available at:
https://www.arin.net/policy/proposals/
The ARIN Policy Development Process is available at:
https://www.arin.net/policy/pdp.html
Regards,
Communications and Member Services
American Registry for Internet Numbers (ARIN)
## * ##
Draft Policy ARIN-2012-8
Aligning 8.2 and 8.3 Transfer Policy
Date: 27 December 2012
Policy statement:
Replace the first paragraph of section 8.2 with the following (second
paragraph remains unchanged):
ARIN will consider requests for the transfer of number resources in the
case of mergers and acquisitions under the following conditions:
* The new entity must provide evidence that they have acquired assets
that use the resources to be transferred from the current
registrant. ARIN will maintain an up-to-date list of acceptable
types of documentation.
* The current registrant must not be involved in any dispute as to the
status of the resources to be transferred.
* The new entity must sign an RSA covering all resources to be
transferred.
* The resources to be transferred will be subject to ARIN policies.
* The minimum transfer size is the smaller of the original allocation
size or the applicable minimum allocation size in current policy.
Rationale:
The base intent here is to lower confusion, raise clarity, and level the
bar between 8.2 and 8.3 transfers. M&A transfers are distinct from
specified transfers and not all of the same rules can apply - but many
can and should. Therefor this policy change explicitly adds requirements
which do not exist in 8.2 policy text today: Source must be the
undisputed current registered holder, recipient must sign an RSA (and is
subject to policy), and /24 minimum for IPv4, /48 for IPv6.
Changes following discussion at the ARIN XXX public policy meeting: 1)
Changed the first bullet. This was an area for objections because it did
not allow chain of custody transfers, so now instead of saying that the
purchased company must be the current registrant holder it simply says
that there can not be any dispute as to who the registered holder is. 2)
Removed the " such that their continued need is justified" text from the
second bullet, this was another area of debate at the meeting and
justification is already covered in paragraph 2 of 8.2 (which remains
unchanged). 3) Swapped the first two bullets. 4) Added "covering all
transferred resources" to the RSA bullet, for clarity. 5) Swapped the
third and fourth bullets. 3) Altered the IPv4 minimum allocation to
bring it in line with 4.10 resources and any future exceptions.
Changes following PPML discussion in November 2012: a) 'used' was
changed back to 'use' in the first bullet to prevent a backdoor around
specified transfers leveraging asset liquidation. b) The third bullet
was shortened for clarity (removed the word 'current' before 'policy')
c) The minimum transfer sizes are now pinned to policy rather than hard-set.
Timetable for implementation: immediate
------------------------------
Message: 4
Date: Fri, 28 Dec 2012 00:53:02 -0500
From: Thomas Narten <[email protected]>
To: [email protected]
Subject: [arin-ppml] Weekly posting summary for [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Total of 5 messages in the last 7 days.
script run at: Fri Dec 28 00:53:02 EST 2012
Messages | Bytes | Who
--------+------+--------+----------+------------------------
80.00% | 4 | 81.57% | 26952 | [email protected]
20.00% | 1 | 18.43% | 6090 | [email protected]
--------+------+--------+----------+------------------------
100.00% | 5 |100.00% | 33042 | Total
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 90, Issue 10
*****************************************
