Historical note:
This document and its predecessor were written at a time where the .US
domain was undelegated - e.g. it was still under the control of the
IANA/US DOD. Registrations were done under the general contract for
the NIC (at SRI at the time). The NIC needed specific guidance on what
names and nameforms were acceptable. This document and it's predecessor
mostly made public guidance the NIC already had.
At some point between when this document was written and about 1998,
delegation of the .US domain moved to the US Department of Commerce/NTIA
- but with ISI (where IANA lived) still doing the zone management. Over
the next few years, NTIA (with public input) put its own stamp on what
could be registered in that domain.
I'm fine moving it to historical - probably along with RFC1956 (.MIL)
and RFC2146 (.GOV) as these are all now explicitly delegated to
different organizations. Hmm.. maybe 1031 as well.
To answer Warren's question - no - these applied up to the time the
delegations took place. It's possible some of this is incorporated by
reference in the contract, but that's OK as we're only changing our
status, not theirs.
Mike -
ps - I owned the NIC contract (for DOD DDN Program Office) 85-89 and was
on the Federal Network Council 92-96 and had a hand in writing most of
these policy documents.
On 12/18/2025 13:00, Warren Kumari wrote:
I'm assuming that this will be coordinated with Registry Services / GD ?
It is baked into contract language, etc…
W
On Thu, Dec 18, 2025 at 8:00 AM, <[email protected]> wrote:
Hi all,
The processing of the errata below triggered a discussion with
Paul about moving this RFC to historic.
The RFC was foundational at early days, but it obviously includes
historical data and does not reflect current practices for this
domain, let alone that this is handled by national bodies.
Unless I'm hearing good reasons to not tag the document as
Historic, I will be starting a status change process early next year.
Thank you.
Cheers,
Med
-----Message d'origine-----
De : RFC Errata System <[email protected]
<mailto:[email protected]>> Envoyé : mercredi 17 décembre
2025 09:57
À : [email protected]
<mailto:[email protected]>
Cc : BOUCADAIR Mohamed INNOV/NET <[email protected]
<mailto:[email protected]>>; [email protected]
<mailto:[email protected]>; [email protected] <mailto:[email protected]>;
[email protected] <mailto:[email protected]>
Objet : [Errata Verified] RFC1480 (8674)
The following errata report has been verified for RFC1480, "The US
Domain".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8674
<https://www.rfc-editor.org/errata/eid8674>
--------------------------------------
Status: Verified
Type: Technical
Reported by: Peter Briggs <[email protected]
<mailto:[email protected]>> Date Reported:
2025-12-10
Verified by: Mohamed BOUCADAIR (IESG)
Section: APPENDIX-I
Original Text
-------------
APPENDIX-I: US DOMAIN NAMES BNF
================================
<us-domain-name> ::= <us-name><dot><us>
<us-name> ::= <state-name><dot><state-code> |
<fed-name><dot><fed>
<dni-name><dot><dni>
<state-code> ::= <the two-letter code of a state from the zip code
directory>
Corrected Text
--------------
APPENDIX-I: US DOMAIN NAMES BNF
================================
<us-domain-name> ::= <us-name><dot><us>
<us-name> ::= <state-name><dot><state-code> |
<fed-name><dot><fed> |
<dni-name><dot><dni>
<state-code> ::= <the two-letter code of a state from the zip code
directory>
Notes
-----
Missing a pipe after <fed-name><dot><fed>
--------------------------------------
RFC1480 (no draft string recorded)
--------------------------------------
Title : The US Domain
Publication Date : June 1993
Author(s) : A. Cooper, J. Postel
Category : INFORMATIONAL
Source : Legacy
Stream : IETF
Verifying Party : IESG
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc pas etre
diffuses, exploites ou copies sans autorisation. Si vous avez recu
ce message par erreur, veuillez le signaler a l'expediteur et le
detruire ainsi que les pieces jointes. Les messages electroniques
etant susceptibles d'alteration, Orange decline toute
responsabilite si ce message a ete altere, deforme ou falsifie.
Merci.
This message and its attachments may contain confidential or
privileged information that may be protected by law; they should
not be distributed, used or copied without authorisation. If you
have received this email in error, please notify the sender and
delete this message and its attachments. As emails may be altered,
Orange is not liable for messages that have been modified, changed
or falsified. Thank you.
_______________________________________________
DNSOP mailing list -- [email protected] <mailto:[email protected]>
To unsubscribe send an email to [email protected]
<mailto:[email protected]>
_______________________________________________
DNSOP mailing list [email protected]
To unsubscribe send an email [email protected]
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
