Hey,

This document seems uncontroversially historic. Changing the status to match 
reality seems sensible.


Joe

> On 18 Dec 2025, at 14:00, [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]> 
> Envoyé : mercredi 17 décembre 2025 09:57
> À : [email protected]
> Cc : BOUCADAIR Mohamed INNOV/NET <[email protected]>; 
> [email protected]; [email protected]; [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
> 
> --------------------------------------
> Status: Verified
> Type: Technical
> 
> Reported by: Peter Briggs <[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]
> To unsubscribe send an email to [email protected]

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to