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 - January 2013 (ARIN)
2. Draft Policy ARIN-2013-1: Section 8.4 Transfer Enhancement -
posted for discussion (ARIN)
3. Weekly posting summary for [email protected] (Thomas Narten)
----------------------------------------------------------------------
Message: 1
Date: Thu, 31 Jan 2013 18:06:12 -0500
From: ARIN <[email protected]>
To: [email protected]
Subject: [arin-ppml] Advisory Council Meeting Results - January 2013
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 25 January 2013 and made
decisions about proposals and draft policies.
The AC accepted the following proposal as a draft policy. The draft
policy will be posted shortly to the Public Policy Mailing List.
ARIN-prop-183 Section 8.4 Transfer enhancement
The AC recommended the following to the ARIN Board of Trustees for adoption:
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
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, 31 Jan 2013 18:08:02 -0500
From: ARIN <[email protected]>
To: [email protected]
Subject: [arin-ppml] Draft Policy ARIN-2013-1: Section 8.4 Transfer
Enhancement - posted for discussion
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Draft Policy ARIN-2013-1
Section 8.4 Transfer Enhancement
On 25 January 2013 the ARIN Advisory Council (AC) accepted
"ARIN-prop-183 Section 8.4 Transfer Enhancement" as a draft policy.
Draft Policy ARIN-2013-1 is below and can be found at:
https://www.arin.net/policy/proposals/2013_1.html
You are encouraged to discuss the merits and your concerns of Draft
Policy 2013-1 on the Public Policy Mailing List. 2013-1 will also be on
the agenda at the upcoming ARIN Public Policy Consultation at NANOG 57
in Orlando. The AC will evaluate the discussion in order to assess the
conformance of this draft policy with ARIN's Principles of Internet
Number Resource Policy as stated in the PDP. Specifically, these
principles are:
* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community
The AC will document the results of their assessment.
The ARIN Policy Development Process (PDP) can be found at:
https://www.arin.net/policy/pdp.html
Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html
Regards,
Member Services
American Registry for Internet Numbers (ARIN)
## * ##
Draft Policy ARIN-2013-1
Section 8.4 Transfer Enhancement
Date: 31 January 2013
Policy statement:
Modify the following text in Section 8.4
Change all occurrences of "IPv4 number resources" to "IPv4 number
resources and ASNs".
Change all occurrences of "IPv4 address resources" to "IPv4 number
resources and ASNs".
Rationale:
We already allow transfer of ASNs within the ARIN region. The change
will accomplish two things. First there is inconsistent language in 8.4
eg "IPv4 Address" v. "IPv4 Number Resource(s)" and second, it will allow
the transfer of ASNs between RIRs through 8.4 and using the standards we
have already established for IPv4 transfers. For many of the same
reasons that we allow transfer of IP addresses, we should allow
transfers of ASNs and to help insure that idle resources are both
recovered and utilized efficiently and where needed.
------------------------------
Message: 3
Date: Fri, 01 Feb 2013 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 3 messages in the last 7 days.
script run at: Fri Feb 1 00:53:02 EST 2013
Messages | Bytes | Who
--------+------+--------+----------+------------------------
66.67% | 2 | 65.45% | 11436 | [email protected]
33.33% | 1 | 34.55% | 6038 | [email protected]
--------+------+--------+----------+------------------------
100.00% | 3 |100.00% | 17474 | Total
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 92, Issue 1
****************************************
