Regarding my comments at the mic today... I support the proposal to the extent that it clarifies: - when a reassign simple is permitted - when a reassign detailed is permitted - when a reassign detailed is required - when reallocate is required
I hope that the proposal will seek to limit the over use of reassign detailed through education. I hope that the proposal will not specifically limit when reassign detailed is permitted. I support a new requirement that an ISP must use a reassign detailed when the customer has: - a desire to multi-home - a desire to publish their own abuse, or tech contact - a desire to publish relevant location details or useful comments With the passage of 2018-05, a customer would now need to create an OrgID prior to being able to request a reassign detail. I think that is a sufficiently high bar to limit customers asking for a detailed reassignment when it is not necessary. As written the policy proposal sounds to me like it limits when an ISP is permitted to make a reassign detailed. I am happy to beat up on ISPs that do reassign detail simply to avoid a reassign simple. __Jason On Fri, Jan 25, 2019 at 2:04 PM Alyssa Moore <[email protected]> wrote: > 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 <[email protected]> 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 ([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. > -- _______________________________________________________ Jason Schiller|NetOps|[email protected]|571-266-0006
_______________________________________________ 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.
