Independent Submission A. Writer Request for Comments: 0009 RFC.EE Project Category: Informational April 2026 ISSN: 2070-1721 Using the RFC.EE Editor: A Reader's Guide Abstract This document is the reader's guide to the RFC.EE web application. It describes the public-facing features: browsing the index, filtering by category, searching the full text, and switching between HTML, plain-text, and PDF output formats. A. Writer Informational [Page 1] RFC 0009 Using RFC.EE April 2026 Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of an independent submission. It has been approved for publication by the RFC Editor, but is not a candidate for any level of Internet Standard; see Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc0009. 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. A. Writer Informational [Page 2] RFC 0009 Using RFC.EE April 2026 Table of Contents Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. The Homepage . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Browsing by Category . . . . . . . . . . . . . . . . . . . . . 4 4. Searching . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Output Formats . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Anchor Links . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6 A. Writer Informational [Page 3] RFC 0009 Using RFC.EE April 2026 1. Introduction A reader arriving at the site sees a homepage with a large search field, a strip of statistics, a row of category tiles, a grid of recently published documents, and a full index. The goal is to let the reader find an RFC in under ten seconds and start reading it. 2. The Homepage The homepage is organized into five sections: o A hero band with the primary search field. Focus falls into the search field automatically on page load. o A four-column statistics strip: published RFCs, distinct authors, categories, and total block count across all published documents. o A row of five category tiles: Standards Track, Best Current Practice, Informational, Experimental, and Historic. Each tile shows the number of documents in its category and links to the filtered index. o A grid of Recently Published cards, each carrying the RFC number, the title, the author, the month of publication, and a short abstract preview. o The full index table, sorted by RFC number, with an inline filter bar for finer-grained queries. 3. Browsing by Category A click on any category tile or top-bar link navigates to a filtered index showing only documents in that category. The filter banner replaces the hero on filtered views, showing the category name and the number of results. A. Writer Informational [Page 4] RFC 0009 Using RFC.EE April 2026 4. Searching The search field accepts any of: an RFC number, a word from the title, the name of an author, or any word from the body of any document. Matches in the body are shown as small italic snippets below the title in the results table, with the matched term highlighted. Search and category filters can be combined: a query of "protocol" combined with the Informational tile returns only informational documents that mention the word "protocol". 5. Output Formats Every RFC is available in three formats. The HTML form is the default; it displays the document with the running headers, page footers, and anchor links used in the canonical RFC style. The plain-text form is obtained by appending &format=txt to the URL; it is a 72-column file with form-feed page breaks, suitable for piping through pr(1) or less(1). The PDF form is obtained with &format=pdf; it is a letter-sized document rendered in Courier at 10 points. 6. Anchor Links The HTML output gives every heading a stable anchor id. A reader can copy a link to any section and share it; the linked reader will jump directly to that section. References are also anchored, so in-text citations like [RFC2119] link to their bibliographic entry. A. Writer Informational [Page 5] RFC 0009 Using RFC.EE April 2026 7. Security Considerations The reader interface is read-only and does not carry a session cookie. Browsing the site does not expose the reader to any authentication state. Operators SHOULD serve the site over HTTPS so that readers cannot be monitored on the network. 8. References [RFC0008] A. Writer, "Authoring an RFC with the RFC.EE Editor", RFC 0008, March 2026 9. Author's Address A. Writer RFC.EE Project Email: writer@example.org A. Writer Informational [Page 6]