[arin-ppml] Draft Policy ARIN-2020-5: Clarify and Update Requirements for Allocations to Downstream Customers

Kat Hunter takokat81 at gmail.com
Thu Jul 16 11:39:38 EDT 2020


Good morning all- We are looking to see if the following changes will
impact ISPs or any impacted parties. This is intended to correct a
reference to a deprecated RFC, however, sometimes business operations do
not update their policies/procedures and we would not want to see
businesses impacted in a detrimental manner due to the new proposed
language. We would like to hear both positive and negative feedback for
this policy. Thanks in advance.

4.2.3.4.1 Existing text:
Reassignment and reallocation information for prior allocations must show
that each
customer meets the 80% utilization criteria and must be available via SWIP
/ a distributed service which meets the standards set forth in section 3.2
prior to your issuing them additional space.

4.2.3.4.1 New text (added new first sentence in paragraph):
A downstream customer requesting address space from an upstream ISP must
document a plan to the allocating ISP for their utilization to conform to
Section 4.3.3. Reassignment and reallocation information for prior
allocations must show that each customer meets the 80% utilization criteria
and must be available via SWIP / a distributed service which meets the
standards set forth in section 3.2 prior to your issuing them additional
space.

4.2.3.6 Original Text:
Under normal circumstances an ISP is required to determine the prefix size
of their reassignment to a downstream customer according to the guidelines
set forth in RFC 2050. Specifically, a downstream customer justifies their
reassignment by demonstrating they have an immediate requirement for 25% of
the IP addresses being assigned, and that they have a plan to utilize 50%
of their assignment within one year of its receipt. This policy allows a
downstream customer’s multihoming requirement to serve as justification for
a /24 reassignment from their upstream ISP, regardless of host
requirements. Downstream customers must provide contact information for all
of their upstream providers to the ISP from whom they are requesting a /24.
The ISP will then verify the customer’s multihoming requirement and may
assign the customer a /24, based on this policy. Customers may receive a
/24 from only one of their upstream providers under this policy without
providing additional justification. ISPs may demonstrate they have made an
assignment to a downstream customer under this policy by supplying ARIN
with the information they collected from the customer, as described above,
or by identifying the AS number of the customer. This information may be
requested by ARIN staff when reviewing an ISP’s utilization during their
request for additional IP addresses space.

4.3.2.6 New Text, replacing old:
If a downstream customer has a requirement to multihome, that requirement
alone will serve as justification for a /24 allocation. Downstream
customers must provide contact information for all of their upstream
providers to the ISP from whom they are requesting a /24, and utilize BGP
as the routing protocol between the customer and the ISP. Customers may
receive a /24 from only one of their upstream providers under this policy
without providing additional justification. ISPs may demonstrate they have
made an assignment to a downstream customer under this policy by supplying
ARIN with the information they collected from the customer, as described
above, or by identifying the AS number of the customer.

-Kat Hunter

On Tue, Jun 23, 2020 at 1:42 PM ARIN <info at arin.net> wrote:

> On 18 June 2020, the ARIN Advisory Council (AC) accepted "ARIN-prop-288:
> Clarify and Update Requirements for Allocations to Downstream Customers"
> as a Draft Policy.
>
> Draft Policy ARIN-2020-5 is below and can be found at:
>
> https://www.arin.net/participate/policy/drafts/2020_5/
>
> 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/participate/policy/pdp/
>
> Draft Policies and Proposals under discussion can be found at:
> https://www.arin.net/participate/policy/drafts/
>
> Regards,
>
> Sean Hopkins
> Policy Analyst
> American Registry for Internet Numbers (ARIN)
>
>
>
> Draft Policy ARIN-2020-5: Clarify and Update Requirements for
> Allocations to Downstream Customers
>
> Problem Statement:
>
> A recent Policy Experience Report demonstrated the fact that the
> existing Section 4.2.3.6 references RFC2050, which is obsolete, and is
> not synchronized with utilization requirements carried in Section 4.3.3,
> specifically the utilization rate.
>
> Policy Statement:
>
> Given that RFC7020, which supercedes RFC2050, no longer carries specific
> utilization requirements for downstream customers of ISPs, its reference
> may be removed from Section 4.2.3.6, instead referencing 4.3.3
> (currently, 50% utilization within 24 months) to harmonize the
> utilization requirements of both ISPs and their downstream customers.
>
> Removing these references from Section 4.2.3.6 will simplify the
> language of that section.
>
> Replace sections 4.2.3.4.1 and sections 4.2.3.6 with the following text:
>
> 4.2.3.4.1. Utilization
>
> A downstream customer requesting address space from an upstream ISP must
> document a plan to the allocating ISP for their utilization to conform
> to Section 4.3.3. Reassignment and reallocation information for prior
> allocations must show that each customer meets the 80% utilization
> criteria and must be available via SWIP / a distributed service which
> meets the standards set forth in section 3.2 prior to your issuing them
> additional space.
>
> 4.2.3.6. Reassignments to Multihomed Downstream Customers
>
> If a downstream customer has a requirement to multihome, that
> requirement alone will serve as justification for a /24 allocation.
> Downstream customers must provide contact information for all of their
> upstream providers to the ISP from whom they are requesting a /24, and
> utilize BGP as the routing protocol between the customer and the ISP.
> Customers may receive a /24 from only one of their upstream providers
> under this policy without providing additional justification. ISPs may
> demonstrate they have made an assignment to a downstream customer under
> this policy by supplying ARIN with the information they collected from
> the customer, as described above, or by identifying the AS number of the
> customer.
>
> Timetable for implementation: Immediate
>
>
> _______________________________________________
> ARIN-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:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20200716/0677c14e/attachment.htm>


More information about the ARIN-PPML mailing list