Add Northwest Nexus delegated locality domains in Washington State

[pwbriggs]

Superseded by #2724

Add 23 delegated locality domains in Washington State maintained by Northwest Nexus, Inc.

Important: I have not yet received any endorsement from Northwest Nexus on this change. This PR should be considered a draft until I finish discussing contact emails and DNS validation.

Public Suffix List (PSL) Submission

Checklist of required steps

• Description of Organization

• Robust Reason for PSL Inclusion

• DNS verification via dig

• (Not applicable) Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _psl TXT record in place in the respective zone(s).

Submitter affirms the following:

• We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)

• I, @pwbriggs, initially learned about the PSL while researching why Cloudflare would not allow me to set up a DNS zone for my personal domain, briggs.seattle.wa.us. However, I am now more concerned with improving cross-site isolation across these 23 locality domains than with getting a personal Cloudflare zone.
• While researching the potential impact and willingness for seattle.wa.us to be added, at least one administrator mentioned to me (@pwbriggs) that they would be interested in this PSL entry to avoid any potential future issues with Let's Encrypt rate limits. Again, this is a benefit supporting my desire for these PSL entries, but it is not my primary objective in requesting them.

• This request was not submitted with the objective of working around other third-party limits.

[TODO: DOES THIS APPLY? IF SO, NW NEXUS NEEDS TO DO THIS:]

• The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, and responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.

• The Guidelines were carefully read and understood, and this request conforms to them (to the best of my knowledge).
• The submission follows the guidelines on formatting and sorting.

This submissions does not follow the sorting guidelines, nor does the entire .us domain section. This is because the sorting guidelines make the list more confusing, not less, in the context of 50 state prefixes. I have added the Northwest Nexus section next to the similar Merit Network entry for a similar case in Michigan.

• A role-based email address has been used and this inbox is actively monitored with a response time of no more than 30 days.

Abuse Contact:

[TODO: DOES THIS APPLY IN THIS CASE? NW NEXUS DOES NOT RUN ANY SITE AT E.G. HTTPS://SEATTLE.WA.US/—THIS IS NOT A "PRIVATE" SECTION PSL ENTRY]

• Abuse contact information (email or web form) is available and easily accessible.

  URL where abuse contact or abuse reporting form can be found:

---

For PRIVATE section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.

To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.

PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.

(Link: about propagation/expectations)

• Yes, I understand. I could break my organization's website cookies and cause other issues, and the rollback timing is acceptable. Proceed anyways.

---

Description of Organization

Northwest Nexus, Inc., dba NuOz Corporation, is a technology services company in the greater Seattle area in Washington State. It is the RFC 1480 § 3.3 delegated organization managing 23 locality domains under .wa.us.

I, @pwbriggs, am a resident of Seattle and operator of briggs.seattle.wa.us, which is affected by this change.

Organization Website: https://nwnexus.net/ or https://nuoz.com/

Reason for PSL Inclusion

Although the RFC 1480 specification for the .us domain is no longer in effect, some companies, including Northwest Nexus / NuOz, continue to distribute 4LD locality domains in accordance with the RFC to independent entities. This means the 3LD localities are eTLD's. Therefore, it is accurate for these suffixes to be added to the PSL.

I, @pwbriggs, am facilitating the addition of these entries to improve cross-site isolation for my own domain and for locality domains operated by others in Washington.

Number of users this request is being made to serve:

In accordance with RFC 1480 § 3.3.1., delegated .us domains deeper than 3rd-level are not included in the WHOIS database. I, @pwbriggs, have not requested Northwest Nexus to provide statistics about the number of registrations in each locality. However, I have done some research personally to gauge the impact of the seattle.wa.us entry specifically. Examples of users affected by this change include the administrators and viewers/clients of https://frederick.seattle.wa.us/, https://sleepless.seattle.wa.us, https://kevin.wallace.seattle.wa.us, https://social.seattle.wa.us/, and briggs.seattle.wa.us, in addition any services run on those domains, and within the other 22 locality domains delegated to NuOz. Notably, https://social.seattle.wa.us/ is a Mastodon instance with 100+ users (which in turn federates posts to the broader Mastodon network).

Since I have not enumerated all registrations in the Seattle locality, nor researched other localities that this PR affects, I am not comfortable claiming a specific number of users affected. If I had to guess, I'd say >30 web sites and >500 end-users affected.

DNS Verification

DNS verification records are not yet in place.

[dnsguru]

@pwbriggs please re-locate these in the #PRIVATE section between NorthFlank and Noticeable

[dnsguru]

@pwbriggs or if they are going to list as Nuoz,
between nsupdate.info and O3O.Foundation

[dnsguru]

The abuse contact at Nuoz.net or nwnexus.net would suffice as the abuse contact portion of the entry

[pwbriggs]

Oh I was under the impression this went together with the other locality domains under the "ICANN" section. for example, ann-arbor.mi.us is operated by Merit Networks and is a locality domain just like seattle.wa.us. You brought up in #2719 (comment) that the .us domain is no longer regulated by RFC 1480 (though some delegates, like Merit and Nexus, still abide by them). Should I move Merit Network to PRIVATE section as well?