I also support these changes. On Fri, Nov 20, 2020 at 12:23 PM Chris Woodfield <[email protected]> wrote:
> FD: This policy is a work produce of the AC’s Policy Experience Report > working group, which I currently chair. > > Taking my AC/WG chair hat off, I am in support of the updated language, > with the caveat that the following assumptions can be relied upon: > > 1. The added language cannot be interpreted to place additional conditions > on legacy resource holders that do not exist today. I’m interpreting the > reference to resources “allocated and assigned under these policies” as > implicitly excluding legacy resource holders, but please correct me if that > assumption is incorrect. > I believe that is the intent of the language. Since legacy resources were allocated prior to the creation of ARIN, they weren't "allocated or assigned under these policies." On the other hand, just to be clear, the lack of a formal written agreement for legacy resource holders doesn't necessarily imply there is no agreement at all. There are lots of things in the world done by informal agreements, for example, a handshake agreement. > 2. The term “Registration Services Agreement” is used generically, and is > inclusive of RSA and LRSA agreements, or other future agreements ARIN may > have with resource holders. > I believe that is the intent as well. However, I think the issue of future agreements is an important point that might be worth adding to the text. How about something like this; This, or future, agreements cover the terms, rights, responsibilities, and conditions of service; failure to adhere to the RSA may result in revocation of number resources. Thanks Thanks, > > -C > > On Nov 20, 2020, at 9:55 AM, ARIN <[email protected]> wrote: > > The following Draft Policy has been revised: > > * ARIN-2020-8: Clarify and Update 4.2.1.2 Annual Renewal Fee > > Revised text is below and can be found at: > > https://www.arin.net/participate/policy/drafts/2020_8/ > > 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 > Policy Analyst > American Registry for Internet Numbers (ARIN) > > > > > Draft Policy ARIN-2020-8: Clarify and Update 4.2.1.2 Annual Renewal Fee > > Problem Statement: > > The January 2020 Policy Experience Report highlighted that the existing > language in Section 4.2.1.2 "Annual Renewal" references fees. Fees are not > considered a member qualification criteria. Since fees aren't referenced > elsewhere in community policy, the wording was reviewed by the PEG. > > Policy Statement: > > Given that the Registration Services Agreement (RSA) already contains > language regarding fees, the AC Shepherds recommend to eliminate 4.2.1.2. > entirely and add: > > 2.X Registration Services Agreement (RSA) > > Number resources allocated or assigned by ARIN under these policies are > subject to a Registration Services Agreement (RSA) between ARIN and the > resource holder. This agreement covers terms, rights, responsibilities and > conditions of service; failure to adhere to the RSA may result in > revocation of number resources. > > Comments: > > The AC’s understanding is that community policy should not include > language referring to fees, as such language is already present in the > Registration Services Agreement (RSA) > > Registration Services has informed us that "Section 4.2.1.2. contains > language detailing fee due dates, encouraging on-time payments, and > mentions potential revocations. It also contains a reference to web > documentation that has evolved significantly since this policy was > implemented, and may continue to do so. Essentially the entire section is > made of language that is already in the Registration Services Agreement, > and is generally fee-focused, making it outside normal scope for Internet > number resource policy." > > Timetable for Implementation: Immediate > > Anything Else: Community input since adopting draft has informed this > direction. The 2.X placeholder is used as this seems like it might be > foundational enough to not be 2.17 but the Shepherds would rather not upset > current indexing arbitrarily. > _______________________________________________ > 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. > -- =============================================== David Farmer 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]). 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.
