+1 Bill’s suggested edits below.

> On Jul 28, 2021, at 3:43 PM, William Herrin <[email protected]> wrote:
> 
> On Tue, Jul 27, 2021 at 9:56 AM ARIN <[email protected]> wrote:
>> In Section 8.3.:
>> 
>> Under “Conditions on source of the transfer,” replace “Number resources 
>> received as the result of an 8.2 transfer are out of scope for the purposes 
>> of this restriction” with “This restriction does not include 8.2 transfers.”
> 
> Howdy,
> 
> They both seem about the same to me. The replacement is less clumsy
> than the original but still clumsy. Just throwing out some
> wordsmithing here:
> 
> Current;
> 
> The source entity 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. Number resources received as
> the result of an 8.2 transfer are out of scope for the purposes of
> this restriction.
> 
> Suggested:
> 
> Excluding section 8.2 transfers, the source entity must not have
> received a transfer, allocation, or assignment of IPv4 number
> resources from ARIN during the 12 months prior to the approval of a
> transfer request.
> 
> That seems to me to flow better.
> 
> Regards,
> Bill Herrin
> 
> 
> --
> William Herrin
> [email protected]
> https://bill.herrin.us/
> _______________________________________________
> 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.

Brian Jones
[email protected]



Attachment: signature.asc
Description: Message signed with OpenPGP

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

Reply via email to