From barka at uchicago.edu  Sun May  2 02:59:26 2021
From: barka at uchicago.edu (Barbora Wichterlova)
Date: Sun, 2 May 2021 01:59:26 -0500
Subject: [arin-ppml] https://figbox.co/
Message-ID: <AC0145A5-B4E9-4965-A166-7EBB87B27A42@uchicago.edu>

Dear All,

I would like to share with the community a promising mentor-mentee platform called Figbox: https://figbox.co/ <https://figbox.co/>. 

Figbox allows junior scholars to find additional mentors willing to provide general advice on the following: thesis topics, experimental designs, publication, and more. It also allows junior scholars the ability to receive double-blind reviews of their working papers before they officially submit to a given journal.

For those who are curious about the benefits of mentoring junior scholars, see: https://figbox.co/benefit/ <https://figbox.co/benefit/>


With best regards,
BW
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20210502/f777cbd7/attachment.htm>

From jcurran at arin.net  Mon May  3 07:35:40 2021
From: jcurran at arin.net (John Curran)
Date: Mon, 3 May 2021 11:35:40 +0000
Subject: [arin-ppml] https://figbox.co/
In-Reply-To: <AC0145A5-B4E9-4965-A166-7EBB87B27A42@uchicago.edu>
References: <AC0145A5-B4E9-4965-A166-7EBB87B27A42@uchicago.edu>
Message-ID: <A96D3D3D-22F5-4B0B-88BC-3BF9B66C958F@arin.net>

Barbora -

The ARIN Mailing List Appropriate Usage Policy (ARIN Mailing List AUP) applies to the PPML Mailing List and requires that posted messages focus on the purpose of list (i.e. ARIN number resource policy development and related activities.)    Furthermore, the AUP specifically forbids use of the ppml mailing list for "Product marketing, business development, or business lead purposes?

I would ask that you keep future postings conformant to the ARIN Mailing List AUP.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers


On 2 May 2021, at 2:59 AM, Barbora Wichterlova <barka at uchicago.edu<mailto:barka at uchicago.edu>> wrote:

Dear All,

I would like to share with the community a promising mentor-mentee platform called Figbox: https://figbox.co/.

Figbox allows junior scholars to find additional mentors willing to provide general advice on the following: thesis topics, experimental designs, publication, and more. It also allows junior scholars the ability to receive double-blind reviews of their working papers before they officially submit to a given journal.

For those who are curious about the benefits of mentoring junior scholars, see: https://figbox.co/benefit/


With best regards,
BW
_______________________________________________
ARIN-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:
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/20210503/f37745d5/attachment.htm>

From info at arin.net  Thu May 20 14:12:31 2021
From: info at arin.net (ARIN)
Date: Thu, 20 May 2021 14:12:31 -0400
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
Message-ID: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>

The following Draft Policy has been revised and retitled:

 

* ARIN-2021-1: ASN Clarifications to Sections 2 and 8

 

Revised text is below and can be found at:

 

https://www.arin.net/participate/policy/drafts/2021_1/

 

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

Senior Policy Analyst

American Registry for Internet Numbers (ARIN)

 

?

Draft Policy ARIN-2021-1: ASN Clarifications to Sections 2 and 8

 

Problem Statement:

 

The community has raised concerns that the current language in Section 8 is not clear regarding ASN-only transactions. There are also some language and reference inconsistencies which should be addressed while adjusting Section 8 and concordant adjustments to Section 2.

 

Policy statement:

 

Add a definition for ASN in Section 2:

 

Section 2.X Autonomous System Number (ASN)

 

An Autonomous System Number (ASN) is a unique identifier which represents a collection of network resources operated under a common routing policy administration, known as an autonomous system.

 

In Section 8.2:

 

Replace

 

?The Internet number resources being transferred as part of an 8.2 transfer will not be subject to a needs-based assessment during the process of the 8.2 transfer.?

 

with

 

?The Internet number resources being transferred as part of a transfer under section 8.2 will not be subject to a needs based assessment during the process of the transfer.?

 

Replace

 

?The recipient must provide evidence that they have acquired the assets that use the resources to be transferred from the current registrant.?

 

with

 

?The recipient must provide evidence that it has acquired the assets that use the resources to be transferred from the current registrant.?

 

Replace

 

?The recipient must show that they have acquired the entire entity which is the current registrant.?

 

with

 

?The recipient must show that it has acquired the entire entity which is the current registrant.?

 

Replace

 

?An organization which serves as the source of an 8.2 IPv4 transfer will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.?

 

with

 

?An organization which serves as the source of an IPv4 transfer under section 8.2 will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.?

 

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.?

 

Replace

 

?Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.?

 

with

 

?Number resources received as the result of a transfer under section 8.2 are out of scope for the purposes of this restriction.?

 

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.?

 

Replace

 

?Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.?

 

with

 

?Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 addresses from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of a section 8.2 transfer are out of scope for the purposes of this restriction.?

 

Add a space between ?Section? and ?4.4? in the fourth bullet under ?Conditions on source of the transfer?

 

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.?

 

In Section 8.5.7:

 

Replace

 

?In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.?

 

with

 

?In lieu of the requirements in sections 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.?

 

Replace

 

?An organization may qualify via 8.5.7 for a total of a /16 equivalent in any 6 month period.?

 

with

 

?An organization may qualify via section 8.5.7 for a total of a /16 equivalent in any 6 month period.?

 

Timetable for implementation: Immediate

 

Anything else:

 

This proposal is intended to be purely editorial in nature

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20210520/eaadfc74/attachment.htm>

From chris at semihuman.com  Thu May 20 14:40:25 2021
From: chris at semihuman.com (Chris Woodfield)
Date: Thu, 20 May 2021 11:40:25 -0700
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
Message-ID: <0CEA7CC6-4119-4DCB-B19F-F76D9E6709EA@semihuman.com>

Hi,

These changes make sense and I am in support. My one question is - am I correct to assume that where the term ?number resources? is replaced with ?addresses?, the intent is to clarify that the clause in question does not apply to ASNs, only address space? And if so, does this result in any potential change in effective policy that would take this out of the editorial realm? 

Thanks,

-Chris

> On May 20, 2021, at 11:12 AM, ARIN <info at arin.net> wrote:
> 
> The following Draft Policy has been revised and retitled:
> * ARIN-2021-1: ASN Clarifications to Sections 2 and 8
>  
> Revised text is below and can be found at:
> https://www.arin.net/participate/policy/drafts/2021_1/ <https://www.arin.net/participate/policy/drafts/2021_1/>
> 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-1: ASN Clarifications to Sections 2 and 8
>  
> Problem Statement:
> The community has raised concerns that the current language in Section 8 is not clear regarding ASN-only transactions. There are also some language and reference inconsistencies which should be addressed while adjusting Section 8 and concordant adjustments to Section 2.
> Policy statement:
> Add a definition for ASN in Section 2:
>  
> Section 2.X Autonomous System Number (ASN)
>  
> An Autonomous System Number (ASN) is a unique identifier which represents a collection of network resources operated under a common routing policy administration, known as an autonomous system.
>  
> In Section 8.2:
>  
> Replace
>  
> ?The Internet number resources being transferred as part of an 8.2 transfer will not be subject to a needs-based assessment during the process of the 8.2 transfer.?
>  
> with
>  
> ?The Internet number resources being transferred as part of a transfer under section 8.2 will not be subject to a needs based assessment during the process of the transfer.?
>  
> Replace
>  
> ?The recipient must provide evidence that they have acquired the assets that use the resources to be transferred from the current registrant.?
>  
> with
>  
> ?The recipient must provide evidence that it has acquired the assets that use the resources to be transferred from the current registrant.?
>  
> Replace
>  
> ?The recipient must show that they have acquired the entire entity which is the current registrant.?
>  
> with
>  
> ?The recipient must show that it has acquired the entire entity which is the current registrant.?
>  
> Replace
>  
> ?An organization which serves as the source of an 8.2 IPv4 transfer will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.?
>  
> with
>  
> ?An organization which serves as the source of an IPv4 transfer under section 8.2 will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.?
>  
> 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.?
>  
> Replace
>  
> ?Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.?
>  
> with
>  
> ?Number resources received as the result of a transfer under section 8.2 are out of scope for the purposes of this restriction.?
>  
> 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.?
>  
> Replace
>  
> ?Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.?
>  
> with
>  
> ?Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 addresses from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of a section 8.2 transfer are out of scope for the purposes of this restriction.?
>  
> Add a space between ?Section? and ?4.4? in the fourth bullet under ?Conditions on source of the transfer?
>  
> 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.?
>  
> In Section 8.5.7:
>  
> Replace
>  
> ?In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.?
>  
> with
>  
> ?In lieu of the requirements in sections 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.?
>  
> Replace
>  
> ?An organization may qualify via 8.5.7 for a total of a /16 equivalent in any 6 month period.?
>  
> with
>  
> ?An organization may qualify via section 8.5.7 for a total of a /16 equivalent in any 6 month period.?
>  
> Timetable for implementation: Immediate
>  
> Anything else:
>  
> This proposal is intended to be purely editorial in nature
>  
> _______________________________________________
> ARIN-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:
> https://lists.arin.net/mailman/listinfo/arin-ppml <https://lists.arin.net/mailman/listinfo/arin-ppml>
> Please contact info at arin.net <mailto: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/20210520/9c7ae0d1/attachment.htm>

From ppml at rsuc.gweep.net  Thu May 20 14:58:57 2021
From: ppml at rsuc.gweep.net (Joe Provo)
Date: Thu, 20 May 2021 14:58:57 -0400
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <0CEA7CC6-4119-4DCB-B19F-F76D9E6709EA@semihuman.com>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
 <0CEA7CC6-4119-4DCB-B19F-F76D9E6709EA@semihuman.com>
Message-ID: <20210520185857.GA72935@gweep.net>

On Thu, May 20, 2021 at 11:40:25AM -0700, Chris Woodfield wrote:
> Hi,
> 
> These changes make sense and I am in support. My one question is
> - am I correct to assume that where the term ???number resources???
> is replaced with ???addresses???, the intent is to clarify that the
> clause in question does not apply to ASNs, only address space? And
> if so, does this result in any potential change in effective policy
> that would take this out of the editorial realm?

The only such changes are where the phrase "IPv4 number resources" 
occurs to align with the preferred expression of "IPv4 addresses". 
Note 8.2 "Internet number resources [...]" remains unchanged, as 
does 8.3 "Number resources [...]" and 8.4 "Number resources received
[...]".

Cheers!

Joe

> 
> > On May 20, 2021, at 11:12 AM, ARIN <info at arin.net> wrote:
> > 
> > The following Draft Policy has been revised and retitled:
> > * ARIN-2021-1: ASN Clarifications to Sections 2 and 8
> >  
> > Revised text is below and can be found at:
> > https://www.arin.net/participate/policy/drafts/2021_1/ <https://www.arin.net/participate/policy/drafts/2021_1/>
> > 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-1: ASN Clarifications to Sections 2 and 8
> >  
> > Problem Statement:
> > The community has raised concerns that the current language in Section 8 is not clear regarding ASN-only transactions. There are also some language and reference inconsistencies which should be addressed while adjusting Section 8 and concordant adjustments to Section 2.
> > Policy statement:
> > Add a definition for ASN in Section 2:
> >  
> > Section 2.X Autonomous System Number (ASN)
> >  
> > An Autonomous System Number (ASN) is a unique identifier which represents a collection of network resources operated under a common routing policy administration, known as an autonomous system.
> >  
> > In Section 8.2:
> >  
> > Replace
> >  
> > ???The Internet number resources being transferred as part of an 8.2 transfer will not be subject to a needs-based assessment during the process of the 8.2 transfer.???
> >  
> > with
> >  
> > ???The Internet number resources being transferred as part of a transfer under section 8.2 will not be subject to a needs based assessment during the process of the transfer.???
> >  
> > Replace
> >  
> > ???The recipient must provide evidence that they have acquired the assets that use the resources to be transferred from the current registrant.???
> >  
> > with
> >  
> > ???The recipient must provide evidence that it has acquired the assets that use the resources to be transferred from the current registrant.???
> >  
> > Replace
> >  
> > ???The recipient must show that they have acquired the entire entity which is the current registrant.???
> >  
> > with
> >  
> > ???The recipient must show that it has acquired the entire entity which is the current registrant.???
> >  
> > Replace
> >  
> > ???An organization which serves as the source of an 8.2 IPv4 transfer will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.???
> >  
> > with
> >  
> > ???An organization which serves as the source of an IPv4 transfer under section 8.2 will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.???
> >  
> > 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.???
> >  
> > Replace
> >  
> > ???Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.???
> >  
> > with
> >  
> > ???Number resources received as the result of a transfer under section 8.2 are out of scope for the purposes of this restriction.???
> >  
> > 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.???
> >  
> > Replace
> >  
> > ???Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.???
> >  
> > with
> >  
> > ???Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 addresses from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of a section 8.2 transfer are out of scope for the purposes of this restriction.???
> >  
> > Add a space between ???Section??? and ???4.4??? in the fourth bullet under ???Conditions on source of the transfer???
> >  
> > 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.???
> >  
> > In Section 8.5.7:
> >  
> > Replace
> >  
> > ???In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.???
> >  
> > with
> >  
> > ???In lieu of the requirements in sections 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.???
> >  
> > Replace
> >  
> > ???An organization may qualify via 8.5.7 for a total of a /16 equivalent in any 6 month period.???
> >  
> > with
> >  
> > ???An organization may qualify via section 8.5.7 for a total of a /16 equivalent in any 6 month period.???
> >  
> > Timetable for implementation: Immediate
> >  
> > Anything else:
> >  
> > This proposal is intended to be purely editorial in nature
> >  
> > _______________________________________________
> > ARIN-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:
> > https://lists.arin.net/mailman/listinfo/arin-ppml <https://lists.arin.net/mailman/listinfo/arin-ppml>
> > Please contact info at arin.net <mailto:info at arin.net> if you experience any issues.
> 

> _______________________________________________
> 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.


-- 
Posted from my personal account - see X-Disclaimer header.
Joe Provo / Gweep / Earthling 


From technologiesmattapally at gmail.com  Thu May 20 15:02:24 2021
From: technologiesmattapally at gmail.com (Mattapally Technologies)
Date: Thu, 20 May 2021 14:02:24 -0500
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <20210520185857.GA72935@gweep.net>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
 <0CEA7CC6-4119-4DCB-B19F-F76D9E6709EA@semihuman.com>
 <20210520185857.GA72935@gweep.net>
Message-ID: <CAE=HndiaB4Adkv1Pc5v5KCy7GFvb4RdQ0KEfYwP3gZKx8vhP3A@mail.gmail.com>

Thanks

On Thursday, May 20, 2021, Joe Provo <ppml at rsuc.gweep.net> wrote:

> On Thu, May 20, 2021 at 11:40:25AM -0700, Chris Woodfield wrote:
> > Hi,
> >
> > These changes make sense and I am in support. My one question is
> > - am I correct to assume that where the term ???number resources???
> > is replaced with ???addresses???, the intent is to clarify that the
> > clause in question does not apply to ASNs, only address space? And
> > if so, does this result in any potential change in effective policy
> > that would take this out of the editorial realm?
>
> The only such changes are where the phrase "IPv4 number resources"
> occurs to align with the preferred expression of "IPv4 addresses".
> Note 8.2 "Internet number resources [...]" remains unchanged, as
> does 8.3 "Number resources [...]" and 8.4 "Number resources received
> [...]".
>
> Cheers!
>
> Joe
>
> >
> > > On May 20, 2021, at 11:12 AM, ARIN <info at arin.net> wrote:
> > >
> > > The following Draft Policy has been revised and retitled:
> > > * ARIN-2021-1: ASN Clarifications to Sections 2 and 8
> > >
> > > Revised text is below and can be found at:
> > > https://www.arin.net/participate/policy/drafts/2021_1/ <
> https://www.arin.net/participate/policy/drafts/2021_1/>
> > > 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-1: ASN Clarifications to Sections 2 and 8
> > >
> > > Problem Statement:
> > > The community has raised concerns that the current language in Section
> 8 is not clear regarding ASN-only transactions. There are also some
> language and reference inconsistencies which should be addressed while
> adjusting Section 8 and concordant adjustments to Section 2.
> > > Policy statement:
> > > Add a definition for ASN in Section 2:
> > >
> > > Section 2.X Autonomous System Number (ASN)
> > >
> > > An Autonomous System Number (ASN) is a unique identifier which
> represents a collection of network resources operated under a common
> routing policy administration, known as an autonomous system.
> > >
> > > In Section 8.2:
> > >
> > > Replace
> > >
> > > ???The Internet number resources being transferred as part of an 8.2
> transfer will not be subject to a needs-based assessment during the process
> of the 8.2 transfer.???
> > >
> > > with
> > >
> > > ???The Internet number resources being transferred as part of a
> transfer under section 8.2 will not be subject to a needs based assessment
> during the process of the transfer.???
> > >
> > > Replace
> > >
> > > ???The recipient must provide evidence that they have acquired the
> assets that use the resources to be transferred from the current
> registrant.???
> > >
> > > with
> > >
> > > ???The recipient must provide evidence that it has acquired the assets
> that use the resources to be transferred from the current registrant.???
> > >
> > > Replace
> > >
> > > ???The recipient must show that they have acquired the entire entity
> which is the current registrant.???
> > >
> > > with
> > >
> > > ???The recipient must show that it has acquired the entire entity
> which is the current registrant.???
> > >
> > > Replace
> > >
> > > ???An organization which serves as the source of an 8.2 IPv4 transfer
> will not be allowed to apply for IPv4 address space under section 4.1.8
> ARIN Waitlist for a period of 36 months following said transfer unless the
> recipient organization remains a subsidiary, parent company, or under
> common ownership with the source organization.???
> > >
> > > with
> > >
> > > ???An organization which serves as the source of an IPv4 transfer
> under section 8.2 will not be allowed to apply for IPv4 address space under
> section 4.1.8 ARIN Waitlist for a period of 36 months following said
> transfer unless the recipient organization remains a subsidiary, parent
> company, or under common ownership with the source organization.???
> > >
> > > 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.???
> > >
> > > Replace
> > >
> > > ???Number resources received as the result of an 8.2 transfer are out
> of scope for the purposes of this restriction.???
> > >
> > > with
> > >
> > > ???Number resources received as the result of a transfer under section
> 8.2 are out of scope for the purposes of this restriction.???
> > >
> > > 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.???
> > >
> > > Replace
> > >
> > > ???Source entities within the ARIN region must not have received a
> transfer, allocation, or assignment of IPv4 number resources from ARIN for
> the 12 months prior to the approval of a transfer request, unless either
> the source or recipient entity owns or controls the other, or both are
> under common ownership or control. Number resources received as the result
> of an 8.2 transfer are out of scope for the purposes of this restriction.???
> > >
> > > with
> > >
> > > ???Source entities within the ARIN region must not have received a
> transfer, allocation, or assignment of IPv4 addresses from ARIN for the 12
> months prior to the approval of a transfer request, unless either the
> source or recipient entity owns or controls the other, or both are under
> common ownership or control. Number resources received as the result of a
> section 8.2 transfer are out of scope for the purposes of this
> restriction.???
> > >
> > > Add a space between ???Section??? and ???4.4??? in the fourth bullet
> under ???Conditions on source of the transfer???
> > >
> > > 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.???
> > >
> > > In Section 8.5.7:
> > >
> > > Replace
> > >
> > > ???In lieu of 8.5.5 and 8.5.6, organizations may qualify for
> additional IPv4 address blocks by demonstrating 80% utilization of their
> currently allocated space.???
> > >
> > > with
> > >
> > > ???In lieu of the requirements in sections 8.5.5 and 8.5.6,
> organizations may qualify for additional IPv4 address blocks by
> demonstrating 80% utilization of their currently allocated space.???
> > >
> > > Replace
> > >
> > > ???An organization may qualify via 8.5.7 for a total of a /16
> equivalent in any 6 month period.???
> > >
> > > with
> > >
> > > ???An organization may qualify via section 8.5.7 for a total of a /16
> equivalent in any 6 month period.???
> > >
> > > Timetable for implementation: Immediate
> > >
> > > Anything else:
> > >
> > > This proposal is intended to be purely editorial in nature
> > >
> > > _______________________________________________
> > > ARIN-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:
> > > https://lists.arin.net/mailman/listinfo/arin-ppml <
> https://lists.arin.net/mailman/listinfo/arin-ppml>
> > > Please contact info at arin.net <mailto:info at arin.net> if you experience
> any issues.
> >
>
> > _______________________________________________
> > 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.
>
>
> --
> Posted from my personal account - see X-Disclaimer header.
> Joe Provo / Gweep / Earthling
> _______________________________________________
> 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/20210520/1819a2da/attachment.htm>

From hannigan at gmail.com  Thu May 20 16:11:54 2021
From: hannigan at gmail.com (Martin Hannigan)
Date: Thu, 20 May 2021 16:11:54 -0400
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <20210520185857.GA72935@gweep.net>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
 <0CEA7CC6-4119-4DCB-B19F-F76D9E6709EA@semihuman.com>
 <20210520185857.GA72935@gweep.net>
Message-ID: <CAMDXq5NhbRZsS5iH-ofcEAy8hZSNGxJNk-wZLSMSe5CK+2WRig@mail.gmail.com>

On Thu, May 20, 2021 at 2:59 PM Joe Provo <ppml at rsuc.gweep.net> wrote:

> On Thu, May 20, 2021 at 11:40:25AM -0700, Chris Woodfield wrote:
> > Hi,
> >
> > These changes make sense and I am in support. My one question is
> > - am I correct to assume that where the term ???number resources???
> > is replaced with ???addresses???, the intent is to clarify that the
> > clause in question does not apply to ASNs, only address space? And
> > if so, does this result in any potential change in effective policy
> > that would take this out of the editorial realm?
>
> The only such changes are where the phrase "IPv4 number resources"
> occurs to align with the preferred expression of "IPv4 addresses".
> Note 8.2 "Internet number resources [...]" remains unchanged, as
> does 8.3 "Number resources [...]" and 8.4 "Number resources received
> [...]".
>


That makes perfect sense to me.

+1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20210520/01fc858c/attachment.htm>

From bill at herrin.us  Thu May 20 17:19:19 2021
From: bill at herrin.us (William Herrin)
Date: Thu, 20 May 2021 14:19:19 -0700
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
Message-ID: <CAP-guGXHasboafTzinA1xi2aVfv8J5X+usr8Bs8W1b8F=70VDA@mail.gmail.com>

On Thu, May 20, 2021 at 11:12 AM ARIN <info at arin.net> wrote:
> * ARIN-2021-1: ASN Clarifications to Sections 2 and 8

Howdy,

Would the proposal authors offer a couple examples where the changed
language clarifies the policy, explaining why the prior policy could
be interpreted to mean something different than the new one?

I see you moved a lot of words around but they seem to me to be the
same words providing the same meanings to the same components of each
sentence.


For "purely editorial" policy changes there are two things I'd
personally like to see in the proposal:

1. A redline version of the impacted policy sections showing the
struck and replaced text so it can be readily understood in context.

2. A change-by-change explanation of what was wrong with the old
version that the new version fixes. Is it poor grammar? A possible
misinterpretation? Esthetically offensive? What specifically does the
change correct? If someone in the community expressed confusion about
what a sentence meant, what did they say and how does the new text
resolve that concern?

Regards,
Bill Herrin

-- 
William Herrin
bill at herrin.us
https://bill.herrin.us/


From anita.nikolich at gmail.com  Thu May 20 21:57:32 2021
From: anita.nikolich at gmail.com (A N)
Date: Thu, 20 May 2021 20:57:32 -0500
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <CAP-guGXHasboafTzinA1xi2aVfv8J5X+usr8Bs8W1b8F=70VDA@mail.gmail.com>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
 <CAP-guGXHasboafTzinA1xi2aVfv8J5X+usr8Bs8W1b8F=70VDA@mail.gmail.com>
Message-ID: <CAJYzV9L5EhnSLZqJVFFW80C=Sv2uF=LaVa-kX8rGe-vn8=KwAw@mail.gmail.com>

Hi Bill -
I'm one of the AC Shepards on this one. This presentation on Day 2 of the
ARIN 47 meetings lays it out with the changes highlighted (please ignore
Section 10.3 as that has been taken out of the draft) but let us know if
there are still questions. See mid way through Day 2 - you can click on the
slide deck: https://www.arin.net/participate/meetings/ARIN47/

Anita


On Thu, May 20, 2021 at 4:20 PM William Herrin <bill at herrin.us> wrote:

> On Thu, May 20, 2021 at 11:12 AM ARIN <info at arin.net> wrote:
> > * ARIN-2021-1: ASN Clarifications to Sections 2 and 8
>
> Howdy,
>
> Would the proposal authors offer a couple examples where the changed
> language clarifies the policy, explaining why the prior policy could
> be interpreted to mean something different than the new one?
>
> I see you moved a lot of words around but they seem to me to be the
> same words providing the same meanings to the same components of each
> sentence.
>
>
> For "purely editorial" policy changes there are two things I'd
> personally like to see in the proposal:
>
> 1. A redline version of the impacted policy sections showing the
> struck and replaced text so it can be readily understood in context.
>
> 2. A change-by-change explanation of what was wrong with the old
> version that the new version fixes. Is it poor grammar? A possible
> misinterpretation? Esthetically offensive? What specifically does the
> change correct? If someone in the community expressed confusion about
> what a sentence meant, what did they say and how does the new text
> resolve that concern?
>
> Regards,
> Bill Herrin
>
> --
> William Herrin
> bill at herrin.us
> https://bill.herrin.us/
> _______________________________________________
> 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/20210520/a491e052/attachment.htm>

From hannigan at gmail.com  Thu May 20 22:00:00 2021
From: hannigan at gmail.com (Martin Hannigan)
Date: Thu, 20 May 2021 22:00:00 -0400
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <CAJYzV9L5EhnSLZqJVFFW80C=Sv2uF=LaVa-kX8rGe-vn8=KwAw@mail.gmail.com>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
 <CAP-guGXHasboafTzinA1xi2aVfv8J5X+usr8Bs8W1b8F=70VDA@mail.gmail.com>
 <CAJYzV9L5EhnSLZqJVFFW80C=Sv2uF=LaVa-kX8rGe-vn8=KwAw@mail.gmail.com>
Message-ID: <CAMDXq5OoyHHSBAgGj3qLewC18e4pNOjdMhL0MBd=N4Qjv0mjiw@mail.gmail.com>

Are the changes for 10.2 abandoned or will they come back to life in a
separate proposal?

Thanks!

-M< (asking for the ASO)



On Thu, May 20, 2021 at 9:57 PM A N <anita.nikolich at gmail.com> wrote:

> Hi Bill -
> I'm one of the AC Shepards on this one. This presentation on Day 2 of the
> ARIN 47 meetings lays it out with the changes highlighted (please ignore
> Section 10.3 as that has been taken out of the draft) but let us know if
> there are still questions. See mid way through Day 2 - you can click on the
> slide deck: https://www.arin.net/participate/meetings/ARIN47/
>
> Anita
>
>
> On Thu, May 20, 2021 at 4:20 PM William Herrin <bill at herrin.us> wrote:
>
>> On Thu, May 20, 2021 at 11:12 AM ARIN <info at arin.net> wrote:
>> > * ARIN-2021-1: ASN Clarifications to Sections 2 and 8
>>
>> Howdy,
>>
>> Would the proposal authors offer a couple examples where the changed
>> language clarifies the policy, explaining why the prior policy could
>> be interpreted to mean something different than the new one?
>>
>> I see you moved a lot of words around but they seem to me to be the
>> same words providing the same meanings to the same components of each
>> sentence.
>>
>>
>> For "purely editorial" policy changes there are two things I'd
>> personally like to see in the proposal:
>>
>> 1. A redline version of the impacted policy sections showing the
>> struck and replaced text so it can be readily understood in context.
>>
>> 2. A change-by-change explanation of what was wrong with the old
>> version that the new version fixes. Is it poor grammar? A possible
>> misinterpretation? Esthetically offensive? What specifically does the
>> change correct? If someone in the community expressed confusion about
>> what a sentence meant, what did they say and how does the new text
>> resolve that concern?
>>
>> Regards,
>> Bill Herrin
>>
>> --
>> William Herrin
>> bill at herrin.us
>> https://bill.herrin.us/
>> _______________________________________________
>> 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.
>>
> _______________________________________________
> 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/20210520/7288a427/attachment.htm>

From anita.nikolich at gmail.com  Thu May 20 22:14:54 2021
From: anita.nikolich at gmail.com (A N)
Date: Thu, 20 May 2021 21:14:54 -0500
Subject: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2021-1: ASN
 Clarifications to Sections 2 and 8
In-Reply-To: <CAMDXq5OoyHHSBAgGj3qLewC18e4pNOjdMhL0MBd=N4Qjv0mjiw@mail.gmail.com>
References: <112AD6F6-EA2D-49F6-90A1-6DA6297A7BAD@arin.net>
 <CAP-guGXHasboafTzinA1xi2aVfv8J5X+usr8Bs8W1b8F=70VDA@mail.gmail.com>
 <CAJYzV9L5EhnSLZqJVFFW80C=Sv2uF=LaVa-kX8rGe-vn8=KwAw@mail.gmail.com>
 <CAMDXq5OoyHHSBAgGj3qLewC18e4pNOjdMhL0MBd=N4Qjv0mjiw@mail.gmail.com>
Message-ID: <CAJYzV9LnSEPWApu5CmVjN8wPpgm4mEEFjzJe7=T8jfrVM-YY2Q@mail.gmail.com>

The changes will *likely* come back to life in a different proposal. This
is still being discussed!

On Thu, May 20, 2021 at 9:00 PM Martin Hannigan <hannigan at gmail.com> wrote:

>
> Are the changes for 10.2 abandoned or will they come back to life in a
> separate proposal?
>
> Thanks!
>
> -M< (asking for the ASO)
>
>
>
> On Thu, May 20, 2021 at 9:57 PM A N <anita.nikolich at gmail.com> wrote:
>
>> Hi Bill -
>> I'm one of the AC Shepards on this one. This presentation on Day 2 of the
>> ARIN 47 meetings lays it out with the changes highlighted (please ignore
>> Section 10.3 as that has been taken out of the draft) but let us know if
>> there are still questions. See mid way through Day 2 - you can click on the
>> slide deck: https://www.arin.net/participate/meetings/ARIN47/
>>
>> Anita
>>
>>
>> On Thu, May 20, 2021 at 4:20 PM William Herrin <bill at herrin.us> wrote:
>>
>>> On Thu, May 20, 2021 at 11:12 AM ARIN <info at arin.net> wrote:
>>> > * ARIN-2021-1: ASN Clarifications to Sections 2 and 8
>>>
>>> Howdy,
>>>
>>> Would the proposal authors offer a couple examples where the changed
>>> language clarifies the policy, explaining why the prior policy could
>>> be interpreted to mean something different than the new one?
>>>
>>> I see you moved a lot of words around but they seem to me to be the
>>> same words providing the same meanings to the same components of each
>>> sentence.
>>>
>>>
>>> For "purely editorial" policy changes there are two things I'd
>>> personally like to see in the proposal:
>>>
>>> 1. A redline version of the impacted policy sections showing the
>>> struck and replaced text so it can be readily understood in context.
>>>
>>> 2. A change-by-change explanation of what was wrong with the old
>>> version that the new version fixes. Is it poor grammar? A possible
>>> misinterpretation? Esthetically offensive? What specifically does the
>>> change correct? If someone in the community expressed confusion about
>>> what a sentence meant, what did they say and how does the new text
>>> resolve that concern?
>>>
>>> Regards,
>>> Bill Herrin
>>>
>>> --
>>> William Herrin
>>> bill at herrin.us
>>> https://bill.herrin.us/
>>> _______________________________________________
>>> 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.
>>>
>> _______________________________________________
>> 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/20210520/7e30ec67/attachment.htm>

From amybpotter at gmail.com  Fri May 21 15:13:18 2021
From: amybpotter at gmail.com (Amy Potter)
Date: Fri, 21 May 2021 15:13:18 -0400
Subject: [arin-ppml] Draft Policy ARIN 2020-10-Requirement to Demonstrate
 Utilization of Reassignments and Reallocations for ISPs Seeking Initial
 Allocation from ARIN
Message-ID: <CAN2rHV9_Xr2oDwxOjZ5+-5Rp5jZGu5mA38E3xDksk5X2C5sF9g@mail.gmail.com>

Hi ppml,

We haven't seen a lot of support for ARIN 2020-10 since it's introduction.
This proposal arose out of a policy experience report, but we've seen very
little said about it from anyone that thinks this is a problem that needs
to be solved or that the current text of NRPM here is negatively impacting
their organization. We've heard from a few members of the community who are
opposed to the proposal, and those who believe the current distinction
between organizations that already have reassignments/reallocations from
their upstreams and organizations with no space at all makes sense.  We'd
like to give the community one last chance to speak out in favor of this
proposal before abandoning it. If you think this is a problem that needs to
be solved, please let us know.

Best,

Amy

***

Draft Policy 2020-10: Requirement to Demonstrate Utilization of
Reassignments and Reallocations for ISPs Seeking Initial Allocation from
ARIN



Problem Statement:



4.2.2 seems to provide an unfair advantage to ISPs without any IP address
holdings - that is, they don?t have any direct assignments or allocations,
nor any reassignments or reallocations from another organization.



If an ISP does already have holdings in the form of reassignments or
reallocations, and they request a /24, or even a /29 as an initial
allocation - they are required to provide utilization data. This slows
their advancement to the waiting list compared to a new ISP without any
holdings at all. An organization without reassignments or reallocations
doesn?t need to provide any justification other than submitting the request
and providing an officer attestation. This expedites their addition to the
waiting list.



Policy Statement:



Replace 4.2.2 with the following:



4.2.2. Initial Allocation to ISPs



All ISP organizations automatically qualify for a /24.These organizations
may qualify for more than a /24 by documenting how the requested allocation
will be utilized within the request size specified in 4.2.4.3.



ISP organizations without direct assignments or allocations from ARIN
qualify for an initial allocation of up to a /22, subject to ARIN?s minimum
allocation size.



Timetable for implementation: Immediate.



Comments:



This proposal was written as the result of a Policy Experience Report.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20210521/9a0375ab/attachment.htm>

From info at arin.net  Tue May 25 14:30:39 2021
From: info at arin.net (ARIN)
Date: Tue, 25 May 2021 14:30:39 -0400
Subject: [arin-ppml] Advisory Council Meeting Results - May 2021
Message-ID: <D7796615-0530-43D1-87EF-A2DB97C00987@arin.net>

In accordance with the Policy Development Process (PDP), the Advisory Council met on 20 May 2021.

 

The AC has advanced the following to the Board of Trustees for review:

 

* ARIN-2020-7: 4.4 gTLD Micro-allocation Clarification

* ARIN-2020-8: Clarify and Update 4.2.1.2 Annual Renewal Fee

 

The AC has classified the following as an Editorial Change (will be posted separately for discussion):

 

* ARIN-2021-1: ASN Clarifications to Sections 2 and 8

 

Per Part One, Section 3.1, paragraph 3 of the PDP:

 

"Changes to policy that are purely editorial and non-substantial in nature are outside the scope of the full Policy Development Process and may only be made with 30 days public notice followed by the concurrence of both the ARIN Advisory Council and ARIN Board of Trustees that the changes are non-substantial in nature."

 

The AC is continuing to work on:

 

Draft Policies:

 

* ARIN-2020-6: Allowance for IPv4 Allocation ?Swap? Transactions via 8.3 Specified Transfers and 8.4 Inter-RIR Transfers

* ARIN-2020-10: Removal of Requirement to Demonstrate Utilization of Reassignments and Reallocations for ISPs Seeking Initial Allocation from ARIN

* ARIN-2021-2: Special Use IPv4 Space Out of Scope for Purposes of Determining Waitlist Eligibility

 

Editorial Changes

 

* ARIN-edit-2020-9: Editorial Clean-up of NRPM Section 4 and Related Provisions

* ARIN-edit-2020-11: Add Textual Description for the Number Resource Hierarchy Image in Section 2

 

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

Senior Policy Analyst

American Registry for Internet Numbers (ARIN)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20210525/0a777ea3/attachment.htm>

From info at arin.net  Tue May 25 14:30:54 2021
From: info at arin.net (ARIN)
Date: Tue, 25 May 2021 14:30:54 -0400
Subject: [arin-ppml] Editorial Change ARIN-edit-2021-1: ASN Clarifications
 to Sections 2 and 8
Message-ID: <F68AAE67-DF34-4EB5-8F81-F5E379AD6D95@arin.net>

On 20 May 2021, the ARIN Advisory Council (AC) classified "ARIN-2021-1: ASN Clarifications to Sections 2 and 8" as an Editorial Change to the Number Resource Policy Manual (NRPM).

 

The text is below and can be found at:

 

https://www.arin.net/participate/policy/drafts/ARIN_edit_2021_1/

 

The process for Editorial Changes is found in Part One, Section 3.1, paragraph 3 of the Policy Development Process (PDP):

 

"Changes to policy that are purely editorial and non-substantial in nature are outside the scope of the full Policy Development Process and may only be made with 30 days public notice followed by the concurrence of both the ARIN Advisory Council and ARIN Board of Trustees that the changes are non-substantial in nature."

 

Your feedback on this Editorial Change is encouraged. The review period will close on 24 June 2021.

 

The Number Resource Policy Manual is available at:

https://www.arin.net/participate/policy/nrpm/

 

The PDP is available at:

https://www.arin.net/participate/policy/pdp/

 

Regards,

 

Sean Hopkins

Senior Policy Analyst

American Registry for Internet Numbers (ARIN)

 

 

 

Editorial Change ARIN-edit-2021-1: ASN Clarifications to Sections 2 and 8

 

Problem Statement:

 

The community has raised concerns that the current language in Section 8 is not clear regarding ASN-only transactions. There are also some language and reference inconsistencies which should be addressed while adjusting Section 8 and concordant adjustments to Section 2.

 

Policy Statement:

 

Add a definition for ASN in Section 2:

 

Section 2.X Autonomous System Number (ASN)

 

An Autonomous System Number (ASN) is a unique identifier which represents a collection of network resources operated under a common routing policy administration, known as an autonomous system.

 

In Section 8.2:

 

Replace

 

?The Internet number resources being transferred as part of an 8.2 transfer will not be subject to a needs-based assessment during the process of the 8.2 transfer.?

 

with

 

?The Internet number resources being transferred as part of a transfer under section 8.2 will not be subject to a needs based assessment during the process of the transfer.?

 

Replace

 

?The recipient must provide evidence that they have acquired the assets that use the resources to be transferred from the current registrant.?

 

with

 

?The recipient must provide evidence that it has acquired the assets that use the resources to be transferred from the current registrant.?

 

Replace

 

?The recipient must show that they have acquired the entire entity which is the current registrant.?

 

with

 

?The recipient must show that it has acquired the entire entity which is the current registrant.?

Replace

 

?An organization which serves as the source of an 8.2 IPv4 transfer will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.?

 

with

 

?An organization which serves as the source of an IPv4 transfer under section 8.2 will not be allowed to apply for IPv4 address space under section 4.1.8 ARIN Waitlist for a period of 36 months following said transfer unless the recipient organization remains a subsidiary, parent company, or under common ownership with the source organization.?

 

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.?

 

Replace

 

?Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.?

 

with

 

?Number resources received as the result of a transfer under section 8.2 are out of scope for the purposes of this restriction.?

 

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.?

 

Replace

 

?Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of an 8.2 transfer are out of scope for the purposes of this restriction.?

 

with

 

?Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 addresses from ARIN for the 12 months prior to the approval of a transfer request, unless either the source or recipient entity owns or controls the other, or both are under common ownership or control. Number resources received as the result of a section 8.2 transfer are out of scope for the purposes of this restriction.?

 

Add a space between ?Section? and ?4.4? in the fourth bullet under ?Conditions on source of the transfer?

 

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.?

 

In Section 8.5.7:

 

Replace

 

?In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.?

 

with

 

?In lieu of the requirements in sections 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.?

 

Replace

 

?An organization may qualify via 8.5.7 for a total of a /16 equivalent in any 6 month period.?

 

with

 

?An organization may qualify via section 8.5.7 for a total of a /16 equivalent in any 6 month period.?

 

Timetable for implementation: Immediate

 

Anything else:

 

This proposal is intended to be purely editorial in nature.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20210525/fba7687a/attachment.htm>