I support this edit, for same reasons others have mentioned.
If I’m recalling yesterday’s presentation correctly, it was ARIN Staff and
Legal, not the AC, that determined that this language could not be implemented
an editorial change, so that’s not up for debate here.
One possible adjustment that I’d like to suggest is that the term “IPv4 and/or
ASN resources” seems a bit awkward, given how many times it appears in the
section. Perhaps we could add a new section that incorporates David’s suggested
language, but also handles the clarification of the definition of number
resources in a single place, scoped to Section 8.
So, a new Section 8.1.1, which I’d propose would be named “Definitions”, could
read as follows:
All references to “number resources" in this section, unless stated
otherwise, refer to IPv4 addresses and/or ASN resources.
When number resources of multiple types, including IPv6 resources, are
transferred, each resource type is considered separately and independently,
both for any conditions on their transferability and the application of any
restrictions following a transfer.
Following this, the other edits to Section 8 in the proposal can simply be
changed to “number resources” to suit.
Opinions?
-C
> On Oct 21, 2021, at 11:23 AM, Martin Hannigan <[email protected]> wrote:
>
>
> I agree with Owen re: the editorial nature of the changes. However, I support
> it moving forward. I don't support the Farmer suggestion. That is possibly a
> material change that should undergo the rigors of "the process" on its own.
>
> Warm regards,
>
> -M<
>
>
>
>
>
> On Thu, Oct 21, 2021 at 11:33 AM Owen DeLong via ARIN-PPML
> <[email protected] <mailto:[email protected]>> wrote:
> I support this amendment.
>
> Owen
>
>
>> On Oct 20, 2021, at 12:45 , David Farmer via ARIN-PPML <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> I support this proposal as currently written.
>>
>> However, regarding Kevin Blumberg's comment at the ARIN 48 discussion of
>> this policy earlier today; How about adding a paragraph like the following
>> to section 8.1, Principles;
>>
>> When number resources of multiple types, IPv4, IPv6, and/or ASNs, are
>> transferred, each resource type is considered separately and independently,
>> both for any conditions on their transferability and the application of any
>> restrictions following a transfer.
>>
>> Something like this added to Section 8.1, Principles, along with the already
>> proposed changes should eliminate any possibility of confusion in this
>> regard.
>>
>> Thanks
>>
>> On Tue, Aug 24, 2021 at 7:52 AM ARIN <[email protected] <mailto:[email protected]>>
>> wrote:
>> On 19 August 2021, the ARIN Advisory Council (AC) accepted "ARIN-prop-299:
>> Clarifications to Sections 8.3, 8.4 and 8.5.6" as a Draft Policy.
>>
>>
>>
>> Draft Policy ARIN-2021-4 is below and can be found at:
>>
>>
>>
>> https://www.arin.net/participate/policy/drafts/2021_4/
>> <https://www.arin.net/participate/policy/drafts/2021_4/>
>>
>>
>> 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/
>> <https://www.arin.net/participate/policy/pdp/>
>>
>>
>> Draft Policies and Proposals under discussion can be found at:
>>
>> https://www.arin.net/participate/policy/drafts/
>> <https://www.arin.net/participate/policy/drafts/>
>>
>>
>> Regards,
>>
>>
>>
>> Sean Hopkins
>>
>> Senior Policy Analyst
>>
>> American Registry for Internet Numbers (ARIN)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Draft Policy ARIN-2021-4: Clarifications to Sections 8.3, 8.4 and 8.5.6
>>
>>
>> Problem Statement:
>>
>>
>>
>> The current language in Sections 8.3 and 8.4 is not clear regarding ASN-only
>> transactions as well as the term “number resources”. The current language in
>> Section 8.5.7 is not clear with regard to additional IPv4 space.
>>
>>
>>
>> Policy statement:
>>
>>
>>
>> In Section 8.3:
>>
>>
>>
>> Replace
>>
>>
>>
>> “In addition to transfers under section 8.2, IPv4 numbers resources and ASNs
>> may be transferred according to the following conditions.”
>>
>>
>>
>> with
>>
>>
>>
>> “In addition to transfers under section 8.2, IPv4 address and/or ASN
>> resources may be transferred according to the following conditions.”
>>
>>
>>
>> Replace
>>
>>
>>
>> “The source entity must be the current registered holder of the IPv4 address
>> resources, and not be involved in any dispute as to the status of those
>> resources.”
>>
>>
>>
>> with
>>
>>
>>
>> “The source entity must be the current registered holder of the IPv4 address
>> and/or ASN resources, and not be involved in any dispute as to the status of
>> those resources.”
>>
>>
>>
>> In Section 8.4:
>>
>>
>>
>> Replace
>>
>>
>>
>> “Inter-regional transfers of IPv4 number resources and ASNs may take place
>> only via RIRs who agree to the transfer and share reciprocal, compatible
>> needs-based policies.”
>>
>>
>>
>> with
>>
>>
>>
>> “Inter-regional transfers of IPv4 addresses and/or ASN resources may take
>> place only via RIRs who agree to the transfer and share reciprocal,
>> compatible needs-based policies.”
>>
>>
>>
>> Replace
>>
>>
>>
>> “The source entity must be the current rights holder of the IPv4 address
>> resources recognized by the RIR responsible for the resources, and not be
>> involved in any dispute as to the status of those resources.”
>>
>>
>>
>> with
>>
>>
>>
>> “The source entity must be the current rights holder of the IPv4 address
>> and/or ASN resources recognized by the RIR responsible for the resources,
>> and not be involved in any dispute as to the status of those resources.”
>>
>>
>>
>> In Section 8.5.6:
>>
>>
>>
>> Replace
>>
>>
>>
>> “Organizations with direct assignments or allocations from ARIN must have
>> efficiently utilized at least 50% of their cumulative IPv4 address blocks in
>> order to receive additional space. This includes all space reassigned to
>> their customers.”
>>
>>
>>
>> with
>>
>>
>>
>> “Organizations with direct assignments or allocations from ARIN must have
>> efficiently utilized at least 50% of their cumulative IPv4 address blocks in
>> order to receive additional IPv4 space. This includes all IPv4 space
>> reassigned to their customers.”
>>
>>
>>
>> Comments:
>>
>>
>>
>> These changes were originally included in ARIN-edit-2021-1. Staff and Legal
>> review of ARIN-edit-2021-1 on June 14, 2021 indicated that some changes were
>> not editorial in nature. The editorial changes went forward in
>> ARIN-edit-2021-1 and the non-editorial changes are included here.
>>
>>
>>
>> Timetable for implementation: Immediate
>>
>>
>>
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected]
>> <mailto:[email protected]>).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-ppml
>> <https://lists.arin.net/mailman/listinfo/arin-ppml>
>> Please contact [email protected] <mailto:[email protected]> if you experience any
>> issues.
>>
>>
>> --
>> ===============================================
>> David Farmer Email:[email protected]
>> <mailto:email%[email protected]>
>> 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
>> ===============================================
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected]
>> <mailto:[email protected]>).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-ppml
>> <https://lists.arin.net/mailman/listinfo/arin-ppml>
>> Please contact [email protected] <mailto:[email protected]> if you experience any
>> issues.
>
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]
> <mailto:[email protected]>).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> <https://lists.arin.net/mailman/listinfo/arin-ppml>
> Please contact [email protected] <mailto:[email protected]> if you experience any
> issues.
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
