[arin-ppml] Draft Policy ARIN-2018-6: Clarify Reassignment Requirements in 4.2.3.7.1

Andrew Dul andrew.dul at quark.net
Fri Jan 25 15:34:58 EST 2019


The intent of this draft policy is not to make lines 7-12 of the simple 
reassignment optional.  The intent is to clarify to the community that a 
detailed reassignment record is not required for most reassignments.

Andrew

On 1/25/2019 12:00 PM, Roberts, Orin wrote:
>
> Please clarify.
>
> This proposal is making lines _7 to 12_ on the template 
> optional/obsolete for all Simple Reassignment SWIPs?
>
> https://www.arin.net/resources/request/reassignments.html
>
> Template: ARIN-REASSIGN-SIMPLE-5.1
> **  As of April 2018
> **  Detailed instructions are located below the template.
> 00. API Key:
> 01. Registration Action (N,M, or R):
> 02. Network Name:
> 03. IP Address and Prefix or Range:
> 04. Origin AS:
> 05. Private (Yes or No):
> 06. Customer Name:
> 07. Customer Address:
> 07. Customer Address:
> 08. Customer City:
> 09. Customer State/Province:
> 10. Customer Postal Code:
> 11. Customer Country Code:
> 12. Public Comments:
> END OF TEMPLATE
>
> cid:image001.jpg at 01C9B448.7DFDA670
>
> 	
>
> **
>
> *Orin Roberts - JNCIA, CCNA, ITILv3*
> *IP PROVISIONING*
>
> *Bell Canada***
>
> 	
>
> *'****905.614.9338** | *** **oroberts at bell.ca* <http://www.bell.ca/>
>
> *From:*ARIN-PPML <arin-ppml-bounces at arin.net> *On Behalf Of *Alyssa Moore
> *Sent:* January-25-19 2:04 PM
> *To:* arin-ppml at arin.net
> *Subject:* Re: [arin-ppml] Draft Policy ARIN-2018-6: Clarify 
> Reassignment Requirements in 4.2.3.7.1
>
> Helloooo PPML,
>
> It's been a couple weeks since there's been any action here, but it's 
> time to shake off the winter and think about some policy! Woo!
>
> This proposal has to do with clarifying the language and requirements 
> around reassignments. Please take a look and let your AC know if you 
> think we're on the right track or not.
>
> Cheers,
> AM
>
> On Tue, Nov 20, 2018 at 3:55 PM ARIN <info at arin.net 
> <mailto:info at arin.net>> wrote:
>
>     On 15 November 2018 the ARIN Advisory Council (AC) accepted
>     "ARIN-prop-258: Clarify Reassignment Requirements in 4.2.3.7.1" as a
>     Draft Policy.
>
>     Draft Policy ARIN-2018-6 is below and can be found at:
>     https://www.arin.net/policy/proposals/2018_6.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-2018-6: Clarify Reassignment Requirements in
>     4.2.3.7.1
>
>     Problem Statement:
>
>     Current NRMP section “Reassignment and Reallocation Information” is
>     being interpreted by some organizations to require a “detailed
>     reassignment” for all customers.  Under the current reassignment
>     schema,
>     only a “detailed reassignment or reallocation” contains fields for
>     “organizational information”.
>
>     This policy intends to simplify the reassignment requirements by
>     noting
>     that only a customer’s name is required.  Thus a “simple
>     reassignment”
>     can be used for most reassignments.
>
>     Policy Statement:
>
>     Replace section 4.2.3.7.1 with the following:
>
>     4.2.3.7.1. Reassignment and Reallocation Information
>
>     Each IPv4 reassignment or reallocation containing a /29 or more
>     addresses shall be registered via a directory services system which
>     meets the standards set forth in section 3.2.
>
>     Reassignment registrations must include each customer name, except
>     where
>     specifically exempted by this policy.  Reassignment registrations
>     shall
>     only include point of contact (POC) information if either: (1)
>     requested
>     by the customer; or (2) the reassigned block is intended to be routed
>     and announced outside of the provider's network.
>
>     Reallocation registrations must contain the customer’s
>     organization name
>     and appropriate point of contact (POC) information.
>
>     Comments:
>
>     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
>     <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 <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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190125/175fd4fa/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2491 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190125/175fd4fa/attachment-0002.jpg>


More information about the ARIN-PPML mailing list