HI Jody -
I believe that the .US domain ownership/delegation remains with the US
Government and that GoDaddy's role is only as a contracted registrar and
operator. Assuming that's true, the contract and operational document
for .US is subject to change or update by the US, as is the contracted
for registrar/operator over a period of time. The appropriate place to
do a "Here's what the .US domain is" is probably not the IETF nor the
RFC series, but some where in webspace under the NTIA's control.
That said, if the NTIA wanted GoDaddy to ghost write a document on their
behalf describing the current model, it might be a useful Informational
contribution via the ISE along the lines of other "here's how we do it"
documents the RFC series has published over the years, but it would be a
GoDaddy and/or NTIA document published by the ISE, and not an IETF
document. I would expect such document to require approval of the
NTIA's COTR or CO.
Tl;dr - updating this document should not be a work item for DNSOP or
any other IETF WG. The old document SHOULD be obsoleted because the
management of the .US domain is no longer in the hands of the IANA or
original NIC and is controlling on no one.
Mike
On 2/19/2026 13:18, Jody Kolker wrote:
RFC 1480 describes a namespace that is still running. Every .US
locality registration, the city-and-state structure under .US, exists
because an operator built and maintains it according to that document.
GoDaddy Registry is that operator today.
We don't object to RFC 1480 becoming Historic. The document is 30
years old and reads like it. But the namespace it specifies is not 30
years old in the way that matters: it is live, it resolves queries,
and registrants depend on it. The normal sequence is to write the
replacement first and let it obsolete the predecessor. Reversing that
order means the only document describing an active namespace carries a
label that says it's obsolete, while the namespace itself keeps
running. That's a mismatch we'd rather avoid.
We are willing to contribute to a successor document that captures how
the .US locality space actually works now. We'd rather do that work
before the status change, not after.
Thanks,
Jody Kolker
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
