Hello 44Net,

During some previous discussions with you all, we promised that we would share upcoming policies with you prior to adoption. With this in mind, I'm writing to share a couple of policies with you all to review - DNS Subdomain Policy and a new End User License Agreement (EULA) - and to open the floor for discussion and feedback.

Both of these documents have been through some rounds of discussion and feedback with some of the regional coordinators, as well as staff, TAC, and board. It feels like, overall, we've landed in a place that works for all parties, and my hope is that you'll agree.

Each of the policies are attached for review, and some summary information is below.

Thanks for any thoughts / comments. We'll collect and discuss over the next couple of weeks before taking to the Board for final approval and implementation.

73, Rosy

//

Summary: DNS Subdomain policy

Purpose: this policy outlines a standard for DNS subdomains that will help us to clean up our unwieldy database of DNS entries and assigning ownership to the ones still in use.

Important notes: * preferred format is callsign.ampr.org; second-level subdomains permitted * if you were managing a top level subdomain that didn't fit that format prior to the launch of the new Portal, you can claim it and keep using it for now. Caveat: ARDC may revoke access to subdomains like hr.ampr.or, policy.ampr.org, or others that may seem to represent ARDC official hr or policy business. There are some other exceptions like this listed in the policy doc.

//

Summary: EULA

Purpose: replacement of our existing Terms of Service (TOS) - https://www.ardc.net/about/legal/terms-of-service/

Important notes: * Though a bit more legalese in the EULA, there are very few substantive changes from the existing TOS * The main note is: for regional coordinators, gateway operators, or other users who may be assigning IP addresses to a subnet user, and they do not wish to have that user register on the Portal, then they take responsibility for the activities of that user. The goal of this is to give folks a pathway for managing their users as they have been, and accepting that with this responsibility comes some accountability.

//

Again, questions welcome. Thank you for taking the time to review.