Network Working Group J. Abley Internet-Draft Cloudflare Intended status: Informational 19 March 2026 Expires: 20 September 2026 Declaring RFC 1480 to be Historic draft-jabley-rfc1480-to-historic-latest Abstract RFC 1480, published in June 1993, described the original structure and related policies for the .US top-level domain, the country-code top-level domain assigned to the United States of America. While significant parts of RFC 1480 continue to be relevant at the time of writing, including the geographic namespace structure and the roles of Delegated Managers, the document as a whole contains many operational and policy details that have been superseded. In order to make it clear that RFC 1480 represents a part of the Internet's historical record and is no longer a complete reference for operational or policy matters, this document reclassifies RFC 1480 as Historic. About This Document This note is to be removed before publishing as an RFC. The latest revision of this draft can be found at https://ableyjoe.github.io/draft-jabley-rfc1480-to-historic/draft- jabley-rfc1480-to-historic.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft- jabley-rfc1480-to-historic/. Source for this draft and an issue tracker can be found at https://github.com/ableyjoe/draft-jabley-rfc1480-to-historic. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 20 September 2026. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Table of Contents 1. Introduction 2. Current Responsibility for the .US Top-Level Domain 3. IANA Considerations 4. References 4.1. Normative References 4.2. Informative References Acknowledgments Author's Address 1. Introduction [RFC1480], published in June 1993, described the original structure and related policies for the .US top-level domain, the country-code top-level domain assigned to the United States of America. While significant parts of [RFC1480] continue to be relevant at the time of writing, including the geographic namespace structure and the roles of Delegated Managers, the document as a whole contains many operational and policy details that have been superseded. In order to make it clear that [RFC1480] now represents a part of the Internet's historical record and is no longer a complete reference for operational or policy matters, this document reclassifies [RFC1480] as Historic. 2. Current Responsibility for the .US Top-Level Domain The U.S. Department of Commerce holds responsibility for the US Top- Level Domain. At the time of writing, Registry Services, LLC manages the .US top- level domain on behalf of the U.S. Department of Commerce. Current policies and governance of the .US top-level domain, including the hierarchical, locality-based namespace described in RFC 1480, can be found at [usTLD]. 3. IANA Considerations This document has no IANA actions. 4. References 4.1. Normative References [RFC1480] Cooper, A. and J. Postel, "The US Domain", RFC 1480, DOI 10.17487/RFC1480, June 1993, . 4.2. Informative References [usTLD] "usTLD Policies and Governance", 19 March 2026, . Acknowledgments Your name here, etc. Author's Address Joe Abley Cloudflare Email: jabley@cloudflare.com