Hi all, Let me first thank you all for sharing thoughts, useful background, and suggestions. Here is my proposal to move forward.
# Doing nothing is not a good option Some of you suggested to do nothing, but I don't think that's a good approach here. Other bodies are responsible for policy matters related to this domain. It is our responsibility to clean up a bit our documentation to reflect current practice. # Need for consistency The reasoning for tagging 1480 as Historic does apply for a other documents: * RFC 1031: MILNET NAME DOMAIN TRANSITION * RFC 1956: Registration in the MIL Domain * RFC 2146: U.S. Government Internet Domain Names Note that there is this one, but I don't it has the same issues as the ones above: * RFC 2053: The AM (Armenia) Domain As Kim said, we need to be consistent in how we handle those. # Clearly describe what are the implications of tagging the document(s) as Historic Mike provided a blob to explain how this should be interpreted. That explanation is good base to build on. # How to proceed? How tagging the document as "Historic" should be interpreted (including indication of any operational considerations) can be included as part of the "status change". However, that administrative document lives in the Datatracker and is not a standalone document that can be referred to, etc. I understand that this might not be visible. For the sake of better awareness, it is preferrable to have an I-D that tags the document as Historic. The document will provide background, how the change should be interpreted, and a discussion why there are no sensitive operational implications. The I-D can be progressed as AD-sponsored or be adopted here in DNSOP. This is thus a call for volunteers to edit a short I-D. Please note that if we don't have volunteers (by IETF#125), the backup will be to proceed with the status change. Please consider volunteering if you don't like that ;-) Thank you. Cheers, Med > -----Message d'origine----- > De : [email protected] <[email protected]> > Envoyé : jeudi 18 décembre 2025 14:01 > À : dnsop <[email protected]> > Cc : Paul Wouters <[email protected]> > Objet : [DNSOP] Moving RFC1480 (The US Domain) to Historic > > 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Ferrata%2Feid8674&data=05%7C02%7Cmohamed.boucadair%40o > range.com%7C1bb622cbb01c43a2dffc08de3e35a913%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C639016597367025129%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=aAq%2FsGSZmEupJ7Udm > EbPrErODcyZTXPuR%2F1p15TdYWc%3D&reserved=0 > > -------------------------------------- > 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] ____________________________________________________________________________________________________________ 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]
