[arin-ppml] Draft Policy 2017-4 Post ARIN 40

Rudolph Daniel rudi.daniel at gmail.com
Tue Nov 21 18:29:38 EST 2017


I support the motion as written.
RD


On 21 Nov 2017 18:43, <arin-ppml-request at arin.net> wrote:

Send ARIN-PPML mailing list submissions to
        arin-ppml at arin.net

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
        arin-ppml-request at arin.net

You can reach the person managing the list at
        arin-ppml-owner at arin.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-PPML digest..."


Today's Topics:

   1. Re: Post-ARIN-40 updates to 2017-4 (Mike Burns)
   2. Advisory Council Meeting Results - November 2017 (ARIN)
   3. Draft Policy ARIN-2017-9: Clarification of Initial Block Size
      for IPv4 ISP Transfers (ARIN)
   4. Draft Policy ARIN-2017-10: Repeal of Immediate Need for IPv4
      Address Space (NRPM Section 4.2.1.6) (ARIN)
   5. Draft Policy ARIN-2017-11: Reallocation and Reassignment
      Language Cleanup (ARIN)


----------------------------------------------------------------------

Message: 1
Date: Fri, 17 Nov 2017 10:43:46 -0500
From: "Mike Burns" <mike at iptrading.com>
To: "'David Farmer'" <farmer at umn.edu>, "'Rob Seastrom'"
        <rs-lists at seastrom.com>
Cc: <ppml at arin.net>
Subject: Re: [arin-ppml] Post-ARIN-40 updates to 2017-4
Message-ID: <004a01d35fba$db358570$91a09050$@iptrading.com>
Content-Type: text/plain; charset="utf-8"

I support as written for the reasons David describes.





From: ARIN-PPML [mailto:arin-ppml-bounces at arin.net] On Behalf Of David
Farmer
Sent: Friday, November 17, 2017 10:27 AM
To: Rob Seastrom <rs-lists at seastrom.com>
Cc: arin-ppml at arin.net <ppml at arin.net>
Subject: Re: [arin-ppml] Post-ARIN-40 updates to 2017-4



I support this policy as written.



The current reciprocity requirement does not recognize that the vast
majority of IPv4 transfers are out of the ARIN region and the vast majority
of the supply of IPv4 resources available for transfer exist within the
ARIN region. Finally there are legitimate operational reasons that
companies within the ARIN region need to transfer resources to themselves
or their foreign subsidiaries in other regions regardless of reciprocal
transfer policies being available.



Thank you for simplifying the text.





On Fri, Nov 17, 2017 at 7:12 AM, Rob Seastrom <rs-lists at seastrom.com
<mailto:rs-lists at seastrom.com> > wrote:


Dear Colleagues,

Based on feedback received at the ARIN-40 conference, the AC Shepherds have
updated Draft Policy 2017-4 - "Remove bidirectional requirement for
inter-RIR transfers".

The proposal in its entirety is below.  We seek feedback and comment.


2017-4 - Remove bidirectional requirement for inter-RIR transfers

Problem Statement:
ARIN?s inter-RIR transfer policy is functionally one-way, so the assertion
of a reciprocal two-way requirement is gratuitous.

Policy statement:
Add the following sentence after the first sentence of NRPM 8.4:
Inter-RIR transfers may take place only via RIRs who agree to the transfer
and share compatible, needs-based policies.

Timetable for implementation: Immediate.


_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net <mailto:
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 <mailto:info at arin.net>  if you experience any
issues.







--

===============================================
David Farmer               Email:farmer at umn.edu <mailto:
Email%3Afarmer at umn.edu>
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.arin.net/pipermail/arin-ppml/
attachments/20171117/b3cdc371/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 21 Nov 2017 17:37:31 -0500
From: ARIN <info at arin.net>
To: arin-ppml at arin.net
Subject: [arin-ppml] Advisory Council Meeting Results - November 2017
Message-ID: <90ca93ea-ba77-0fc6-538d-c788ce02590f at arin.net>
Content-Type: text/plain; charset=utf-8; format=flowed

In accordance with the Policy Development Process (PDP), the Advisory
Council (AC) met on 16 November 2017.

The AC has advanced the following Proposals to Draft Policy status (each
will be posted for discussion):

* ARIN-prop-244: Clarification of initial block size for IPv4 ISP transfers

* ARIN-prop-245: Repeal of Immediate Need for IPv4 Address Space (NRPM
Section 4.2.1.6)

* ARIN-prop-246: Reallocation and Reassignment Language Cleanup

* ARIN-prop-247: Require New POC Validation Upon Reassignment

* ARIN-prop-248: Remove ARIN Review Requirements for Large IPv4
Reassignments/Reallocations

The AC advances Proposals to Draft Policy status once they are found to
be within the scope of the PDP, and contain a clear problem statement
and suggested changes to Internet number resource policy text.

The AC has sent the following to the Board of Trustees for adoption
consideration:

* Recommended Draft Policy ARIN-2017-5: Improved IPv6 Registration
Requirements

The AC provided the following statement:

"After a successful conclusion of the Last Call period, the ARIN AC is
forwarding Recommended Draft Policy ARIN-2017-5: Improved IPv6
Registration Requirements to the ARIN Board with a request for adoption.
Based on the consensus of the community at ARIN 40, the policy text was
adjusted going into Last Call. While a minority dissent during Last Call
period was in favor of the original text, the AC is of the view that the
community thoroughly discussed that matter both at ARIN 40 and on PPML,
and the consensus of the community supports the change in the text."

The AC is continuing to work on:

* ARIN-2017-3: Update to NPRM 3.6: Annual Whois POC Validation
* ARIN-2017-4: Remove Bidirectional Requirement for Inter-RIR Transfers
* ARIN-2017-8: Amend the Definition of Community Network

The 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,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)


------------------------------

Message: 3
Date: Tue, 21 Nov 2017 17:40:39 -0500
From: ARIN <info at arin.net>
To: arin-ppml at arin.net
Subject: [arin-ppml] Draft Policy ARIN-2017-9: Clarification of
        Initial Block Size for IPv4 ISP Transfers
Message-ID: <652abd11-68d7-900e-7776-b97b2311ea05 at arin.net>
Content-Type: text/plain; charset=utf-8; format=flowed

On 16 November 2017, the ARIN Advisory Council (AC) advanced
"ARIN-prop-244: Clarification of Initial Block Size for IPv4 ISP
Transfers" to Draft Policy status.

Draft Policy ARIN-2017-9 is below and can be found at:
https://www.arin.net/policy/proposals/2017_9.html

You are encouraged to discuss all Draft Policies on PPML. 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 Policy Development Process (PDP). Specifically, these
principles are:

* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community

The 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,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)



Draft Policy ARIN-2017-9: Clarification of Initial Block Size for IPv4
ISP Transfers

Problem Statement:

It was noted at the ARIN 40 Policy Experience Report, that there is an
inconsistency in the initial block size for ISPs. Section 4.2.2 notes
that the initial ISP block size should be /21 whereas the initial block
size in 8.5.4 is noted as "minimum transfer size" which is effectively a
/24. The intent of the new 8.5.4 was to match the previous policy. This
policy is intended to clarify this issue. It was noted that ARIN staff
current operational practice is to allow ISPs an initial /21 for Section
8 transfers.

Policy statement:

Add the following to 8.5.4

ISP organizations without direct assignments or allocations from ARIN
qualify for an initial allocation of up to a /21.

Comments:

a. Timetable for implementation: Immediate


------------------------------

Message: 4
Date: Tue, 21 Nov 2017 17:42:02 -0500
From: ARIN <info at arin.net>
To: arin-ppml at arin.net
Subject: [arin-ppml] Draft Policy ARIN-2017-10: Repeal of Immediate
        Need for IPv4 Address Space (NRPM Section 4.2.1.6)
Message-ID: <0ea280c3-adf7-1ee3-422f-5bd39b75a31c at arin.net>
Content-Type: text/plain; charset=utf-8; format=flowed

On 16 November 2017, the ARIN Advisory Council (AC) advanced
"ARIN-prop-245: Repeal of Immediate Need for IPv4 Address Space (NRPM
Section 4.2.1.6)" to Draft Policy status.

Draft Policy ARIN-2017-10 is below and can be found at:
https://www.arin.net/policy/proposals/2017_10.html

You are encouraged to discuss all Draft Policies on PPML. 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 Policy Development Process (PDP). Specifically, these
principles are:

* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community

The 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,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)



Draft Policy ARIN-2017-10: Repeal of Immediate Need for IPv4 Address
Space (NRPM Section 4.2.1.6)

Problem Statement:

Section 4.2.1.6 of the ARIN Numbering Resource Policy Manual (NRPM)
provides that an ISP having an immediate need for IPv4 address space
that will be utilized within thirty days of a request may obtain a block
of IPv4 address space of the size specified in section 4.2.1.6 from ARIN
on an exceptional basis. However, as noted in the ARIN 40 Policy
Experience Report, since IPv4 exhaustion, obtaining IPv4 addresses in
this manner is no longer possible as a practical matter. Instead an ISP
must join the waiting list and wait until it reaches the front of the
queue to obtain any IPv4 address space, however long that may take. In
effect, section 4.2.1.6 is non-operative. Accordingly, its continued
presence in the NRPM is misleading and confusing.

Policy statement:

Section 4.2.1.6 of the NRPM is hereby repealed and section number
4.2.1.6 is hereby retired.

Comments:

a. Timetable for implementation: Immediate

b. Comments: Given the constraints created by the exhaustion of IPv4
addresses, this proposal does not require any changes in the current
ARIN practices for the allocation of IPv4 address space.


------------------------------

Message: 5
Date: Tue, 21 Nov 2017 17:43:05 -0500
From: ARIN <info at arin.net>
To: arin-ppml at arin.net
Subject: [arin-ppml] Draft Policy ARIN-2017-11: Reallocation and
        Reassignment Language Cleanup
Message-ID: <98d17d2f-c3f8-f395-77a2-6493f7d36452 at arin.net>
Content-Type: text/plain; charset=utf-8; format=flowed

On 16 November 2017, the ARIN Advisory Council (AC) advanced
"ARIN-prop-246: Reallocation and Reassignment Language Cleanup" to Draft
Policy status.

Draft Policy ARIN-2017-11 is below and can be found at:
https://www.arin.net/policy/proposals/2017_11.html

You are encouraged to discuss all Draft Policies on PPML. 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 Policy Development Process (PDP). Specifically, these
principles are:

* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community

The 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,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)



Draft Policy ARIN-2017-11: Reallocation and Reassignment Language Cleanup

Problem Statement:

The current text of NRPM uses the terms ?reallocate? and ?reassign? in
ways that are both internally inconsistent within NRPM and inconsistent
with the definitions of Reassignments and Reallocations as fields within
the ARIN database. Frequently the term ?reassignment? or ?reassign? is
used in NRPM as an umbrella term for both reallocations and
reassignments. As a result, someone familiar with the ARIN Whois
database, but unfamiliar with history of particular portions of NRPM and
their intended meaning may interpret certain NRPM requirements as
applying only to reassignments and not to reallocations. This is
particularly problematic when it comes to SWIP requirements and the
requirement to record reallocations and reassignments with ARIN, which
under current text could be read to only apply to reassignments.

Policy Statement:

Make the following changes to the definitions in Section 2.5

Current text:

2.5. Allocate and Assign

A distinction is made between address allocation and address assignment,
i.e., ISPs are "allocated" address space as described herein, while
end-users are "assigned" address space.

Allocate - To allocate means to distribute address space to IRs for the
purpose of subsequent distribution by them.

Assign - To assign means to delegate address space to an ISP or
end-user, for specific use within the Internet infrastructure they
operate. Assignments must only be made for specific purposes documented
by specific organizations and are not to be sub-assigned to other parties.

Proposed Editorial Change:

2.5 Allocation, Assignment, Reallocation, Reassignment

Allocation - Address space delegated to an organization directly by ARIN
for the purpose of subsequent distribution by the recipient organization
to other parties.

Assignment - Address space delegated to an organization directly by ARIN
for the exclusive use of the recipient organization.

Reallocation - Address space sub-delegated to an organization by an
upstream provider for the purpose of subsequent distribution by the
recipient organization to other parties.

Reassignment - Address space  sub-delegated to an organization by an
upstream provider for the exclusive use of the recipient organization.

Make the following editorial changes to section 4.2:

Current text:

4.2.1.1. Purpose

ARIN allocates blocks of IP addresses to ISPs for the purpose of
reassigning that space to their customers.

Proposed Editorial Change:

4.2.1.1. Purpose

ARIN allocates blocks of IP addresses to ISPs for the purpose of
reassigning and reallocating that space to their customers.

Current text:

4.2.3. Reassigning Address Space to Customers

Proposed Editorial Change:

4.2.3. Reassigning and Reallocating Address Space to Customers

Current Text:

4.2.3.1. Efficient utilization

ISPs are required to apply a utilization efficiency criterion in
providing address space to their customers. To this end, ISPs should
have documented justification available for each reassignment. ARIN may
request this justification at any time. If justification is not
provided, future receipt of allocations may be impacted.

Proposed Editorial Change:

4.2.3.1. Efficient utilization

ISPs are required to apply a utilization efficiency criterion in
providing address space to their customers. To this end, ISPs should
have documented justification available for each reassignment and
reallocation. ARIN may request this justification at any time. If
justification is not provided, future receipt of allocations may be
impacted.

Current text:

4.2.3.4. Downstream customer adherence

ISPs must require their downstream customers to adhere to the following
criteria:

4.2.3.4.1. Utilization

Reassignment information for prior allocations must show that each
customer meets the 80% utilization criteria and must be available via
SWIP / RWhois prior to your issuing them additional space.

Proposed Editorial Changes:

4.2.3.4. Downstream customer adherence

ISPs must require their downstream customers to adhere to the following
criteria:

4.2.3.4.1. Utilization

Reassignment and reallocation information for prior allocations must
show that each customer meets the 80% utilization criteria and must be
available via SWIP / RWhois prior to your issuing them additional space.

Current text:

4.2.3.5. ARIN approval of reassignments/reallocations

4.2.3.5.1. /18

All extra-large ISPs making reassignments of a /18 or larger to a
customer must first have these reassignments reviewed and approved by ARIN.

4.2.3.5.2. /19

Small to large ISPs making customer reassignments of a /19 or larger
must first seek ARIN's approval.

Proposed Editorial Changes:

4.2.3.5. ARIN approval of reassignments/reallocations

4.2.3.5.1. /18

All extra-large ISPs making reassignments or reallocations of a /18 or
larger to a customer must first have these reassignments or
reallocations reviewed and approved by ARIN.

4.2.3.5.2. /19

Small to large ISPs making customer reassignments or reallocations of a
/19 or larger must first seek ARIN's approval.

Current text:

4.2.3.7.1. Reassignment Information

Each IPv4 assignment containing a /29 or more addresses shall be
registered in the WHOIS directory via SWIP or a distributed service
which meets the standards set forth in section 3.2. Reassignment
registrations shall include each client's organizational information,
except where specifically exempted by this policy.

Proposed Editorial Changes:

4.2.3.7.1. Reassignment and Reallocation Information

Each IPv4 reassignment or reallocation containing a /29 or more
addresses shall be registered in the WHOIS directory via SWIP or a
distributed service which meets the standards set forth in section 3.2.
Reassignment and reallocation registrations shall include each client's
organizational information, except where specifically exempted by this
policy.

Current text:

4.2.3.7.2.Assignments visible within 7 days

All assignments shall be made visible as required in section 4.2.3.7.1
within seven calendar days of assignment.

Proposed Editorial Changes:

4.2.3.7.2.Reassignments and Reallocations visible within 7 days

All reassignments and reallocations shall be made visible as required in
section 4.2.3.7.1 within seven calendar days of reassignment or
reallocation.

Current text:

4.2.4. ISP Additional Requests

4.2.4.1. Utilization percentage (80%)

ISPs must have efficiently utilized all allocations, in aggregate, to at
least 80% and at least 50% of every allocation in order to receive
additional space. This includes all space reassigned to their customers.

Proposed Editorial Changes:

4.2.4. ISP Additional Requests

4.2.4.1. Utilization percentage (80%)

ISPs must have efficiently utilized all allocations, in aggregate, to at
least 80% and at least 50% of every allocation in order to receive
additional space. This includes all space reassigned or reallocated to
their customers.

Make the following editorial changes to section 6 to clarify language
regarding current practices and requirements for reallocations and
reassignments, and specifically to clarify that recording reallocation
information is required where current language is ambiguous:

Current text:

6.5.2.1(e) Initial Allocations to LIRs, Size

For purposes of the calculation in (c), an LIR which has subordinate
LIRs shall make such allocations according to the same policies and
criteria as ARIN. In such a case, the prefixes necessary for such an
allocation should be treated as fully utilized in determining the block
sizing for the parent LIR. LIRs which do not receive resources directly
from ARIN will not be able to make such allocations to subordinate LIRs
and subordinate LIRs which need more than a /32 shall apply directly to
ARIN.

Proposed Editorial Changes:

6.5.2.1(e) Initial Allocations to LIRs, Size

For purposes of the calculation in (c), an LIR which has subordinate
LIRs shall make such reallocations according to the same policies and
criteria as ARIN. In such a case, the prefixes necessary for such a
reallocation should be treated as fully utilized in determining the
block sizing for the parent LIR. LIRs which do not receive resources
directly from ARIN will not be able to make such reallocations to
subordinate LIRs and subordinate LIRs which need more than a /32 shall
apply directly to ARIN.

Current text:

6.5.2.2. Qualifications

An organization qualifies for an allocation under this policy if they
meet any of the following criteria:

a. Have a previously justified IPv4 ISP allocation from ARIN or one of
its predecessor registries or can qualify for an IPv4 ISP allocation
under current criteria.

b. Are currently multihomed for IPv6 or will immediately become
multihomed for IPv6 using a valid assigned global AS number.

In either case, they will be making reassignments from allocation(s)
under this policy to other organizations.

Provide ARIN a reasonable technical justification indicating why an
allocation is necessary. Justification must include the intended
purposes for the allocation and describe the network infrastructure the
allocation will be used to support. Justification must also include a
plan detailing anticipated assignments to other organizations or
customers for one, two and five year periods, with a minimum of 50
assignments within 5 years.

Proposed Editorial Changes:

6.5.2.2. Qualifications

An organization qualifies for an allocation under this policy if they
meet any of the following criteria:

a. Have a previously justified IPv4 ISP allocation from ARIN or one of
its predecessor registries or can qualify for an IPv4 ISP allocation
under current criteria.

b. Are currently multihomed for IPv6 or will immediately become
multihomed for IPv6 using a valid assigned global AS number.

In either case, they will be making reassignments or reallocations from
allocation(s) under this policy to other organizations.

Provide ARIN a reasonable technical justification indicating why an
allocation is necessary. Justification must include the intended
purposes for the allocation and describe the network infrastructure the
allocation will be used to support. Justification must also include a
plan detailing anticipated reassignments and reallocations to other
organizations or customers for one, two and five year periods, with a
minimum of 50 assignments within 5 years.

Current text:

6.5.4. Assignments from LIRs/ISPs

Assignments to end users shall be governed by the same practices adopted
by the community in section 6.5.8 except that the requirements in
6.5.8.1 do not apply.

Proposed Editorial Changes:

6.5.4. Reassignments from LIRs/ISPs

Reassignments to end users shall be governed by the same practices
adopted by the community in section 6.5.8 except that the requirements
in 6.5.8.1 do not apply.

Current text:

6.5.4.1. Assignment to operator's infrastructure

An LIR may assign up to a /48 per PoP as well as up to an additional /48
globally for its own infrastructure.

Proposed Editorial Changes:

6.5.4.1. Reassignment to operator's infrastructure

An LIR may reassign up to a /48 per PoP as well as up to an additional
/48 globally for its own infrastructure.

Current text:

6.5.5. Registration

ISPs are required to demonstrate efficient use of IP address space
allocations by providing appropriate documentation, including but not
limited to assignment histories, showing their efficient use.

Proposed Editorial Changes:

6.5.5. Registration

ISPs are required to demonstrate efficient use of IP address space
allocations by providing appropriate documentation, including but not
limited to reassignment and reallocation histories, showing their
efficient use.

Current text:

6.5.5.1. Reassignment information

Each static IPv6 assignment containing a /64 or more addresses shall be
registered in the WHOIS directory via SWIP or a distributed service
which meets the standards set forth in section 3.2. Reassignment
registrations shall include each client's organizational information,
except where specifically exempted by this policy.

Proposed Editorial Changes:

6.5.5.1. Reassignment information

Each static IPv6 reassignment or reallocation containing a /64 or more
addresses shall be registered in the WHOIS directory via SWIP or a
distributed service which meets the standards set forth in section 3.2.
Reassignment and reallocation registrations shall include each client's
organizational information, except where specifically exempted by this
policy.

Current text:

6.5.5.2. Assignments visible within 7 days

All assignments shall be made visible as required in section 4.2.3.7.1
within seven calendar days of assignment

Proposed Editorial Changes:

6.5.5.2. Reassignments and Reallocations visible within 7 days

All reassignments and reallocations shall be made visible as required in
section 4.2.3.7.1 within seven calendar days of reassignment or
reallocation.


------------------------------

Subject: Digest Footer

_______________________________________________
ARIN-PPML mailing list
ARIN-PPML at arin.net
http://lists.arin.net/mailman/listinfo/arin-ppml

------------------------------

End of ARIN-PPML Digest, Vol 149, Issue 5
*****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20171121/22e35bab/attachment.html>


More information about the ARIN-PPML mailing list