IETF | RFCs

<!doctype html><html lang="en" class="no-js"><head> <meta charset="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>IETF | RFCs</title><meta name="description" content="RFC documents contain technical specifications and organizational notes for the Internet and are the core output of the IETF."/><meta name="viewport" content="width=device-width,initial-scale=1"/><meta name="twitter:card" content="summary"/><meta name="twitter:site" content="@ietf"/><meta name="twitter:title" content="About RFCs"/><meta name="twitter:description" content="RFC documents contain technical specifications and organizational notes for the Internet and are the core output of the IETF."><meta name="twitter:image" content="/media/images/ietflogotrans.original.png"><meta property="fb:app_id" content="159756941186350"/><meta property="og:type" content="website"/><meta property="og:url" content="/process/rfcs/"/><meta property="og:title" content="About RFCs"/><meta property="og:image" content="/media/images/ietflogotrans.original.png"/><meta property="og:description" content="RFC documents contain technical specifications and organizational notes for the Internet and are the core output of the IETF."/><meta property="og:site_name" content="IETF"/> <link href="https://static.ietf.org/fonts/inter/import.css" rel="stylesheet"/> <script defer="defer" src="/static/dist/main.7d84808b4dfd.js"></script><link href="/static/dist/main.6c3ce2b62208.css" rel="stylesheet"></head><body class="template-standard-page"> <header class="header"> <a href="#content" class="visually-hidden visually-hidden-focusable">Skip to main content</a> <nav class="navbar navbar-expand-lg" aria-label="Main" > <div class="container position-relative"> <button class="navbar-toggler navbar-toggler-light" type="button" data-bs-toggle="collapse" data-bs-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation" > <span class="navbar-toggler-icon text-dark"></span> </button>  <button class="btn btn-link nav-link text-dark ms-3 me-auto d-lg-none" type="button" data-bs-toggle="collapse" data-bs-target="#navbarSearch" aria-controls="navbarSearch" aria-expanded="false" aria-label="Toggle search bar" > <i class="bi bi-search"></i> Search </button> <div class="navbar-brand header__logo-container"> <a class="text-light" href="/"> <img class="header__logo" src="https://static.ietf.org/logos/ietf.svg" alt="IETF logo" /> </a> </div> <div class="collapse navbar-collapse flex-wrap-reverse" id="navbarSupportedContent" > <ul class="navbar-nav col-12 col-xl-auto justify-content-xl-center flex-grow"> <li class="nav-item dropdown position-static"> <button class=" nav-link btn megamenu__toggle text-dark fw-semibold text-uppercase dropdown-toggle pe-1 " id="megamenu-toggle-1" role="button" data-bs-toggle="dropdown" data-bs-auto-close="outside" aria-expanded="false" > About </button> <div class="dropdown-menu megamenu__menu w-100 px-2" aria-labelledby="megamenu-toggle-" > <div class="container py-3"> <div class="row gx-5"> <div class="col-lg-4 d-none d-lg-block"> <div class=""> <p></p> <img src="/media/images/ietf-logo.width-600.jpg" class="w-100 object-fit-cover" /> </div> </div> <div class="col-lg-8"> <h5 class="border-bottom mb-1 pb-1"> <a class="dropdown-item" href="/about/"> About <i class="bi bi-chevron-right"></i> </a> </h5> <ul class="megamenu__linklist"> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Introduction to the IETF</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/about/introduction/"> Introduction to the IETF </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/about/introduction/#participants"> Participants </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/about/introduction/#mission"> Mission </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/about/introduction/#principles"> Principles </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/about/introduction/#work"> The work </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Structure of the IETF</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/about/groups/iesg/"> Internet Engineering Steering Group </a> </li> <li> <a class="dropdown-item" href="/about/groups/iab/"> Internet Architecture Board </a> </li> <li> <a class="dropdown-item" href="/about/groups/irtf/"> Internet Research Task Force </a> </li> <li> <a class="dropdown-item" href="/about/liaisons/"> Liaisons </a> </li> <li> <a class="dropdown-item" href="/about/groups/nomcom/"> Nominating Committee </a> </li> <li> <a class="dropdown-item" href="/about/groups/trust/"> IETF Trust </a> </li> <li> <a class="dropdown-item" href="/about/groups/rfc-editor/"> RFC Editor </a> </li> <li> <a class="dropdown-item" href="/about/groups/ise/"> Independent Submissions Editor </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Legal requests</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/administration/legal-request-procedures/"> Legal request procedures </a> </li> <li> <a class="dropdown-item" href="/administration/legal-requests/"> Legal requests </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Administration</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/administration/overview/"> IETF Administration LLC </a> </li> <li> <a class="dropdown-item" href="/administration/announcements/"> Administrative announcements </a> </li> <li> <a class="dropdown-item" href="/administration/reports/"> Administrative reports </a> </li> <li> <a class="dropdown-item" href="/administration/llc-board/"> IETF Administration LLC Board of Directors </a> </li> <li> <a class="dropdown-item" href="/administration/financial-statements/"> Financial statements </a> </li> <li> <a class="dropdown-item" href="/administration/rfps-and-contracts/"> RFPs and contracts </a> </li> <li> <a class="dropdown-item" href="/administration/policies-procedures/"> Administrative policies and procedures </a> </li> <li> <a class="dropdown-item" href="/transparency/"> IETF LLC transparency report </a> </li> </ul> </div> </div> </div> </div> </li> <li class="nav-item dropdown position-static"> <button class=" nav-link btn megamenu__toggle text-dark fw-semibold text-uppercase dropdown-toggle pe-1 " id="megamenu-toggle-2" role="button" data-bs-toggle="dropdown" data-bs-auto-close="outside" aria-expanded="false" > Technologies </button> <div class="dropdown-menu megamenu__menu w-100 px-2" aria-labelledby="megamenu-toggle-" > <div class="container py-3"> <div class="row gx-5"> <div class="col-lg-4 d-none d-lg-block"> <div class=""> <p>The IETF works on a broad range of networking technologies that provide the foundation for the Internet's growth and evolution.</p> <img src="/media/images/things.width-600.jpg" class="w-100 object-fit-cover" /> </div> </div> <div class="col-lg-8"> <h5 class="border-bottom mb-1 pb-1"> <a class="dropdown-item" href="/technologies/"> Technologies <i class="bi bi-chevron-right"></i> </a> </h5> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/technologies/netmgmt/"> Automated network management </a> </li> <li> <a class="dropdown-item" href="/technologies/iot/"> The Internet of Things </a> </li> <li> <a class="dropdown-item" href="/technologies/transport/"> New transport technology </a> </li> <li> <a class="dropdown-item" href="/technologies/security/"> Security & privacy </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">IETF technologies in action</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/technologies/dns/"> Domain Name System </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">IETF technology groups</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/technologies/areas/"> IETF Areas </a> </li> <li> <a class="dropdown-item" href="/technologies/keywords/"> Working Group keywords </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Recent posts about IETF technologies</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/blog/wimse-working-group/"> WIMSE Working Group: Serious business for cloud computing </a> </li> <li> <a class="dropdown-item" href="/blog/green-wg/"> The new GREEN working group gets ready for an energy efficient Internet </a> </li> <li> <a class="dropdown-item" href="/blog/wit-area/"> New IETF Area focuses on web and transport technologies </a> </li> <li> <a class="dropdown-item" href="/blog/edhoc/"> EDHOC - A new lightweight authenticated key exchange protocol provides improved security with less overhead for Internet-of-Things devices </a> </li> </ul> </div> </div> </div> </div> </li> <li class="nav-item dropdown position-static"> <button class=" nav-link btn megamenu__toggle text-dark fw-semibold text-uppercase dropdown-toggle pe-1 " id="megamenu-toggle-5" role="button" data-bs-toggle="dropdown" data-bs-auto-close="outside" aria-expanded="false" > Meetings </button> <div class="dropdown-menu megamenu__menu w-100 px-2" aria-labelledby="megamenu-toggle-" > <div class="container py-3"> <div class="row gx-5"> <div class="col-lg-4 d-none d-lg-block"> <div class=""> <p>While most IETF work takes place online, meetings and other events such as Hackathons provide in-person opportunities to advance work within the IETF.</p> <img src="/media/images/_MG_4832.width-600.jpg" class="w-100 object-fit-cover" /> </div> </div> <div class="col-lg-8"> <h5 class="border-bottom mb-1 pb-1"> <a class="dropdown-item" href="/meeting/"> Meetings <i class="bi bi-chevron-right"></i> </a> </h5> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/meeting/121/"> IETF 121 Dublin </a> </li> <li> <a class="dropdown-item" href="/meeting/122/"> IETF 122 Bangkok </a> </li> <li> <a class="dropdown-item" href="/meeting/123/"> IETF 123 Madrid </a> </li> <li> <a class="dropdown-item" href="/meeting/upcoming/"> Upcoming meetings </a> </li> <li> <a class="dropdown-item" href="/meeting/past/"> Past meetings </a> </li> <li> <a class="dropdown-item" href="/meeting/interim/"> Interim meetings </a> </li> <li> <a class="dropdown-item" href="/meeting/hackathons/"> IETF Hackathons </a> </li> <li> <a class="dropdown-item" href="/meeting/code-sprint/"> Code Sprint </a> </li> <li> <a class="dropdown-item" href="/meeting/124/"> IETF 124 Montreal </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Participation information</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/meeting/preparation/"> Preparing for an IETF Meeting </a> </li> <li> <a class="dropdown-item" href="/meeting/guide-ietf-meetings/"> Guide to IETF Meetings </a> </li> <li> <a class="dropdown-item" href="/meeting/technology/"> Meeting network and technology </a> </li> <li> <a class="dropdown-item" href="/meeting/new-participants/"> New Participants </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Organizing meetings</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/meeting/planning/"> Meeting planning </a> </li> <li> <a class="dropdown-item" href="/support-us/sponsorship/"> Meeting sponsorship </a> </li> </ul> </div> </div> </div> </div> </li> <li class="nav-item dropdown position-static"> <button class=" nav-link btn megamenu__toggle text-dark fw-semibold text-uppercase dropdown-toggle pe-1 " id="megamenu-toggle-4" role="button" data-bs-toggle="dropdown" data-bs-auto-close="outside" aria-expanded="false" > Process </button> <div class="dropdown-menu megamenu__menu w-100 px-2" aria-labelledby="megamenu-toggle-" > <div class="container py-3"> <div class="row gx-5"> <div class="col-lg-4 d-none d-lg-block"> <div class=""> <p>The IETF is the premier Internet standards organization. It follows open and well-documented processes for setting these standards. Once published, those standards are made freely available.</p> </div> </div> <div class="col-lg-8"> <h5 class="border-bottom mb-1 pb-1"> <a class="dropdown-item" href="/process/"> Process <i class="bi bi-chevron-right"></i> </a> </h5> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/process/process/"> Internet standards process </a> </li> <li> <a class="dropdown-item" href="/process/wgs/"> Guide to IETF Working Groups </a> </li> <li> <a class="dropdown-item" href="/process/bofs/"> Birds of a Feather </a> </li> <li> <a class="dropdown-item" href="/process/iana/"> Protocol registries (IANA) </a> </li> <li> <a class="dropdown-item" href="/process/ipr/"> Intellectual property rights </a> </li> <li> <a class="dropdown-item" href="/process/directorates/"> Directorates and teams </a> </li> <li> <a class="dropdown-item" href="/process/informal/"> The IETF process: an informal guide </a> </li> <li> <a class="dropdown-item" href="/process/new-work/"> Bringing new work to the IETF </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">RFCs</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/process/rfcs/"> About RFCs </a> </li> <li> <a class="dropdown-item" href="/about/groups/rfc-editor/"> RFC Editor </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/process/rfcs/#availability-and-use"> Availability and Use </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/process/rfcs/#formats"> Publication formats </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/process/rfcs/#statuses"> Statuses </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/process/rfcs/#streams"> Publication streams </a> </li> <li> <a class="dropdown-item" href="https://www.ietf.org/process/rfcs/#errata"> Corrections and errata </a> </li> <li> <a class="dropdown-item" href="/process/rfcs/vulnerabilities/"> Reporting protocol vulnerabilities to the IETF </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Standards process details</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/process/process/informational-vs-experimental/"> Choosing between Informational and Experimental Status </a> </li> <li> <a class="dropdown-item" href="/process/process/role-iesg-standards-process/"> The role of the IESG in the Standards process </a> </li> <li> <a class="dropdown-item" href="https://datatracker.ietf.org/group/iesg/appeals/"> Appeals to the IESG </a> </li> <li> <a class="dropdown-item" href="/process/process/iesg-ballots/"> IESG ballot procedures </a> </li> <li> <a class="dropdown-item" href="/process/informal/"> The IETF process: an informal guide </a> </li> </ul> </div> </div> </div> </div> </li> <li class="nav-item dropdown position-static"> <button class=" nav-link btn megamenu__toggle text-dark fw-semibold text-uppercase dropdown-toggle pe-1 " id="megamenu-toggle-3" role="button" data-bs-toggle="dropdown" data-bs-auto-close="outside" aria-expanded="false" > Participate </button> <div class="dropdown-menu megamenu__menu w-100 px-2" aria-labelledby="megamenu-toggle-" > <div class="container py-3"> <div class="row gx-5"> <div class="col-lg-4 d-none d-lg-block"> <div class=""> <p>The global IETF community works together in many different ways to produce high quality, relevant technical documents that influence the way people design, use, and manage the Internet.</p> </div> </div> <div class="col-lg-8"> <h5 class="border-bottom mb-1 pb-1"> <a class="dropdown-item" href="/participate/"> Participate <i class="bi bi-chevron-right"></i> </a> </h5> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/participate/get-started/"> Getting started in the IETF </a> </li> <li> <a class="dropdown-item" href="/participate/ids/"> Internet-Drafts </a> </li> <li> <a class="dropdown-item" href="/participate/ietf-systers/"> IETF Systers </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Tools and services</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/participate/lists/"> Mailing lists </a> </li> <li> <a class="dropdown-item" href="/participate/tools/"> Tools and Services </a> </li> <li> <a class="dropdown-item" href="/about/open-records/"> Open records </a> </li> <li> <a class="dropdown-item" href="https://chairs.ietf.org"> Chairs Resources </a> </li> <li> <a class="dropdown-item" href="https://authors.ietf.org"> I-D Authors Resources </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Participation guides</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/meeting/guide-ietf-meetings/"> Guide to IETF Meetings </a> </li> <li> <a class="dropdown-item" href="/process/wgs/"> Guide to IETF Working Groups </a> </li> <li> <a class="dropdown-item" href="/participate/roles/"> Roles in the IETF </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Key policies</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/about/note-well/"> Note Well - A reminder of IETF policies </a> </li> <li> <a class="dropdown-item" href="https://datatracker.ietf.org/doc/statement-iesg-ietf-anti-harassment-policy-20131103/"> Anti-harassment policy </a> </li> <li> <a class="dropdown-item" href="https://www.rfc-editor.org/info/bcp9"> Internet Standards process (BCP 9) </a> </li> <li> <a class="dropdown-item" href="https://www.rfc-editor.org/info/bcp25"> Working Group processes (BCP 25) </a> </li> <li> <a class="dropdown-item" href="https://www.rfc-editor.org/rfc/rfc7154.html"> Guidelines for conduct (BCP 54) </a> </li> <li> <a class="dropdown-item" href="https://www.rfc-editor.org/rfc/rfc5378.html"> Copyright (BCP 78) </a> </li> <li> <a class="dropdown-item" href="https://www.rfc-editor.org/rfc/rfc8179.html"> Patents, Participation (BCP 79) </a> </li> <li> <a class="dropdown-item" href="/privacy-statement/"> IETF/IRTF/IAB Privacy Statement </a> </li> </ul> </div> </div> </div> </div> </li> <li class="nav-item dropdown position-static"> <button class=" nav-link btn megamenu__toggle text-dark fw-semibold text-uppercase dropdown-toggle pe-1 " id="megamenu-toggle-6" role="button" data-bs-toggle="dropdown" data-bs-auto-close="outside" aria-expanded="false" > Support us </button> <div class="dropdown-menu megamenu__menu w-100 px-2" aria-labelledby="megamenu-toggle-" > <div class="container py-3"> <div class="row gx-5"> <div class="col-lg-4 d-none d-lg-block"> <div class=""> <p>By supporting the IETF today, you are ensuring a free and open Internet exists tomorrow.</p> <img src="/media/images/IMG_15.width-600.jpg" class="w-100 object-fit-cover" /> </div> </div> <div class="col-lg-8"> <h5 class="border-bottom mb-1 pb-1"> <a class="dropdown-item" href="/support-us/"> Support us <i class="bi bi-chevron-right"></i> </a> </h5> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/support-us/why-support/"> Why we need your support </a> </li> <li> <a class="dropdown-item" href="/support-us/donors/"> IETF financial supporters </a> </li> <li> <a class="dropdown-item" href="/support-us/donate-ietf-endowment/"> Donate to the IETF Endowment </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Ways to give</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/support-us/endowment/"> IETF Endowment </a> </li> <li> <a class="dropdown-item" href="/support-us/sponsorship/"> Meeting sponsorship </a> </li> <li> <a class="dropdown-item" href="/support-us/donate/"> Other ways to give </a> </li> <li> <a class="dropdown-item" href="/support-us/technical-foundations/"> Technical foundations for business </a> </li> </ul> <h6 class="mt-3 mb-1 pb-1 border-bottom">Supporting values</h6> <ul class="megamenu__linklist"> <li> <a class="dropdown-item" href="/runningcode/"> Running Code </a> </li> <li> <a class="dropdown-item" href="/sustainability/"> Sustainability </a> </li> <li> <a class="dropdown-item" href="/diversity/"> Diversity and Inclusion </a> </li> <li> <a class="dropdown-item" href="/open-internet/"> Open Internet </a> </li> </ul> </div> </div> </div> </div> </li> </ul> <ul class="navbar-nav col-xl-auto"> <li class=" nav-item " > <a class=" nav-link btn text-dark " href="/blog/" >News & blog</a> </li> <li class="nav-item d-none d-lg-inline-block"> <a href="/search" class="btn text-dark nav-link" role="button" data-bs-toggle="collapse" data-bs-target="#navbarSearch" aria-controls="navbarSearch" aria-expanded="false" aria-label="Toggle search bar" > <i class="bi bi-search"></i> Search </a> </li> </ul> </div> </div> </nav> <div class="collapse" id="navbarSearch"> <div class="container"> <div class="row justify-content-center"> <form class="input-group mt-3 mb-3 col-md-8 col-lg-6" action="/search/" method="get" name="search" > <input id="search" type="search" class="form-control" placeholder="Search" aria-label="Search" name="query" required /> <button type="submit" class="btn btn-primary" aria-label="Submit website search">Go</button> </form> </div> </div> </div> </header> <main id="content"> <div class="bg-white pb-1"> <div class="container"> <nav aria-label="breadcrumbs"> <ol class="breadcrumb bg-transparent pt-3 mb-3 "> <li class="breadcrumb-item"><a class="text-dark" aria-label="Home" href="/"><i class="bi bi-house-door-fill"></i></a></li> <li class="breadcrumb-item "><a class="text-dark" href="/process/">Process</a></li> </ol> </nav> <h1>About RFCs</h1> <p class="lead u-max-text-width">RFCs are the core output of the IETF.</p> <ul class="social"></ul> </div> </div> <div class="bg-white"> <div class="container"> <div class="row g-0 align-items-start justify-content-between"> <div class="col-12 col-lg-8 col-xl-9 pe-lg-3"> <div class="mb-3 pt-3 pt-lg-3 border-top"> <div class=""> <div id="key-info" class="u-max-text-width"> <div class="block-markdown"><ul> <li><a href="#introduction">Introduction</a><br/></li> <li><a href="#series-structure">Structure of the series</a><br/></li> <li><a href="#availability-and-use">Availability and use</a><br/></li> <li><a href="#formats">Publication formats</a><br/></li> <li><a href="#statuses">Statuses</a><br/></li> <li><a href="#streams">Publication streams</a><br/></li> <li><a href="#obsoleting-and-updating">Obsoleting and updating</a><br/></li> <li><a href="#errata">Corrections and errata</a><br/></li> <li><a href="#vulnerabilities">Reporting vulnerabilities in RFCs</a><br/></li> </ul> <h2><a id="introduction">Introduction</a></h2> <p>The IETF publishes its technical documentation as RFCs, an acronym for their historical title <em>Requests for Comments</em>. They describe the Internet's technical foundations, such as addressing, routing, and transport technologies. RFCs also specify protocols like TLS 1.3, QUIC, and WebRTC that are used to deliver services used by billions of people every day, such as real-time collaboration, email, and the domain name system.</p> <p>Software developers, hardware manufacturers, and network operators around the world voluntarily implement and adopt the technical specifications and best practices described by RFCs.</p> <p>The <a href="https://www.rfc-editor.org">RFC Editor</a> website is the authoritative site for RFCs. The <a href="https://datatracker.ietf.org/">IETF Datatracker</a> provides transparency on the process that resulted in the publication of each RFC.</p> <h2><a id="series-structure">Structure of the series</a></h2> <p>RFCs are sequentially numbered, starting with RFC 1 published in 1969 (the RFC series predates the IETF). Today, there are more than 9000 documents in the series. </p> <p>The RFC series has two subseries, STDs and BCPs, with each numbered STD and BCP comprising one or more RFCs. STDs are 'Internet Standard' RFCs, and BCPs are RFCs that describe 'Best Current Practices' for the Internet, some of which are administrative processes for the IETF.</p> <h2><a id="availability-and-use">Availability and use</a></h2> <p>RFCs are freely available to download, copy, publish, display and distribute, in a variety of formats, under a license granted by the <a href="https://trustee.ietf.org">IETF Trust</a>. This license, the <a href="https://trustee.ietf.org/documents/trust-legal-provisions/tlp-5/">Trust Legal Provisions</a>, has some important restrictions, including a prohibition on modification of RFCs outside of the IETF Standards Process.</p> <p>RFCs are not guaranteed to be patent-free and anyone interested in the Intellectual Property Rights (IPR) constraints on a specific document should consult the IETF's <a href="https://datatracker.ietf.org/ipr/">IPR disclosure database</a>, though this is not guaranteed to be a complete record of applicable patents. </p> <h2><a id="formats">Publication formats</a></h2> <p>RFCs are published in the following formats:</p> <ul> <li> <p><strong>HTML</strong>. This is the most flexible format for reading an RFC: the page layout adapts to the window size; if SVG diagrams are supplied, they are displayed; and the text is accompanied by a header showing important metadata, including the details of any RFCs that this RFC updates or obsoletes, and vice versa, as well as indicating the existence of errata and linking to those. For RFCs before RFC 8650, the HTMLised (see below) format is used in place of the HTML. </p> </li> <li> <p><strong>Plain Text</strong>. RFCs were originally produced on typewriters, and a plain text format that looks very similar to those original RFCs is still available. The main limitations of the plain text format are that the metadata cannot change, only ASCII diagrams can be displayed, links in the text are shown as annotations, the line width is fixed so may be difficult to read on a mobile device, and there is no indication of the existence of errata.</p> </li> <li> <p><strong>HTMLised</strong>. This format displays the Plain Text format as an HTML page with working links and the same metadata as the HTML version; however, it shares the rest of the limitations as the plain text format. This format is available for RFCs before RFC 8650.</p> </li> <li> <p><strong>PDF</strong>. This is a PDF of an HTML rendering of the RFC, so it can display any SVG diagrams and it provides working links. However, the metadata is limited. PDFs are the only paginated RFC format.</p> </li> <li> <p><strong>RFCXML</strong>. This is the raw source of RFCs, not a publication format. RFCXML is an XML language fully documented on the <a href="https://authors.ietf.org">I-D Authors Resource Site</a> and has been used as the source format since RFC 8650.</p> </li> </ul> <h2><a id="statuses">Statuses</a></h2> <p>Most RFCs and all new RFCs have one of the following statuses. Statuses may change over time. </p> <ul> <li> <p><strong>Informational</strong>. <code>An "Informational" specification is published for the general information of the Internet community, and does not represent an Internet community consensus or recommendation.</code> <a href="https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2.2">RFC 2026, Section 4.2.2</a></p> </li> <li> <p><strong>Experimental</strong>. <code>The "Experimental" designation typically denotes a specification that is part of some research or development effort. Such a specification is published for the general information of the Internet technical community and as an archival record of the work</code> <a href="https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2.1">RFC 2026, Section 4.2.1</a></p> </li> <li> <p>Standards have one of the following statuses:</p> </li> <li> <p><strong>Proposed Standard (PS)</strong>. The first official stage. Many standards never progress beyond this level. </p> </li> <li> <p><strong>Draft Standard</strong>. An intermediate stage that is no longer used for new standards.</p> </li> <li> <p><strong>Internet Standard</strong>. The final stage, when the standard is shown to be interoperable and widely deployed. </p> </li> <li> <p><strong>Best Current Practice (BCP)</strong>. BCPs have a dual role. One is to document IETF processes as agreed by the IETF community, and the other is explained in <a href="https://www.rfc-editor.org/rfc/rfc2026.html#section-5">RFC 2026, Section 5</a> as: <code>since the Internet itself is composed of networks operated by a great variety of organizations, with diverse goals and rules, good user service requires that the operators and administrators of the Internet follow some common guidelines for policies and operations.</code></p> </li> <li> <p><strong>Historic</strong>. <code>A specification that has been superseded by a more recent specification or is for any other reason considered to be obsolete is assigned to the "Historic" level.</code> <a href="https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2.4">RFC 2026, Section 4.2.4</a></p> </li> <li> <p>RFCs that were published before statuses were introduced (before RFC 1128) are mostly considered to have an <strong>Unknown</strong> status, with a handful having had statuses retroactively applied.</p> </li> </ul> <h2><a id="streams">Publication streams</a></h2> <p>There are five streams that can publish an RFC.</p> <p>The <strong>IETF Stream</strong> is the only stream that can publish standards and by far the largest. All RFCs published in the IETF Stream must have community rough consensus, whatever their status.</p> <p>The <strong><a href="https://datatracker.ietf.org/stream/iab/">IAB Stream</a></strong> and <strong><a href="https://datatracker.ietf.org/stream/irtf/">IRTF Stream</a></strong> can also publish technical and process RFCs related to their role.</p> <p>The Editorial Stream, as described by <a href="https://www.rfc-editor.org/rfc/rfc9280.html">RFC 9280</a> publishes policies governing the RFC Series as a whole.</p> <p>The <strong><a href="https://www.rfc-editor.org/about/independent/">Independent Submissions Stream</a></strong> publishes RFCs that are outside the official processes of the IETF, IAB, and IRTF but are relevant to the Internet community and achieve reasonable levels of technical and editorial quality.</p> <h2><a id="obsoleting-and-updating">Obsoleting and updating</a></h2> <p>An RFC can be entirely obsoleted by a new RFC or have parts of it updated by other RFCs. A new RFC can update parts of multiple RFCs, and can obsolete multiple RFCs.</p> <p>Most of the publication formats note if an RFC has been obsoleted or updated and lists the RFCs responsible.</p> <h2><a id="errata">Corrections and errata</a></h2> <p>With one exception, once an RFC is published, it is never changed, which is why the RFC series is often described as "archival" in nature. The one exception to this rule is if an RFC is rendered incorrectly, such as some text cut off, in which case the specific publication format with the problem may be replaced.</p> <p>If a technical or editorial error in an RFC is reported, an erratum may be created that documents the error and optionally provides a correction. Newly Reported errata are checked and either Verified, Rejected or Held for Document Update. For Technical errata, this decision is made by the appropriate stream-specific party, and for Editorial errata, by the RFC Editor.</p> <p>The RFC Editor site has more details on these <a href="https://www.rfc-editor.org/errata-definitions/">statuses</a> and a <a href="https://www.rfc-editor.org/errata.php">searchable errata database</a>.</p> <p>Verified errata are linked to the RFC, but the RFC is not republished with the errata incorporated. There is ongoing work to provide a good way of displaying an RFC with the errata incorporated.</p> <h2><a id="vulnerabilities">Reporting vulnerabilities in RFCs</a></h2> <p>The IETF recognizes that security vulnerabilities will be discovered in IETF protocols and welcomes their critical evaluation by researchers. If you believe that you have discovered a vulnerability in an IETF protocol then please follow our guidance on <a href="https://www.ietf.org/process/rfcs/vulnerabilities/">how to report vulnerabilities</a>.</p></div> </div> </div> </div> <div class="row g-0 align-items-stretch"> <div class="col-12 col-xl bg-secondary"> <div class="bg-secondary p-5 text-white d-flex flex-column justify-content-center h-100"> <h2 class="h6 text-uppercase mb-3">you might be interested in</h2> <p class="mb-0"> <a class="text-white" href="https://www.rfc-editor.org"> RFC Editor website<i class="bi bi-chevron-right ps-2"></i> </a> </p> <p class="mb-0"> <a class="text-white" href="/blog/how-read-rfc/"> How to Read an RFC<i class="bi bi-chevron-right ps-2"></i> </a> </p> <p class="mb-0"> <a class="text-white" href="https://www.rfc-editor.org/rfc/rfc8700.html"> RFC 8700: Fifty Years of RFCs<i class="bi bi-chevron-right ps-2"></i> </a> </p> <p class="mb-0"> <a class="text-white" href="https://www.rfc-editor.org/rfc/rfc8700.html#name-key-moments-in-rfc-history"> Key moments in RFC History (from RFC 8700)<i class="bi bi-chevron-right ps-2"></i> </a> </p> </div> </div> </div> </div> <nav aria-label="In this section" class="bg-body border col-12 col-lg-4 col-xl-3 p-3 p-lg-5 mb-4"> <h2 class="h5 mb-3"><a class="text-dark" href="/process/">Process</a></h2> <div class="block-paragraph"> <ul class="list-unstyled"> <li class="mb-1"><a class="text-dark" href="/process/process/">Internet standards process</a></li> <li class="mb-1"><a class="text-dark" href="/process/wgs/">Guide to IETF Working Groups</a></li> <li class="mb-1"><a class="text-dark" href="/process/bofs/">Birds of a Feather</a></li> <li class="mb-1"><a class="text-dark" href="/process/iana/">Protocol registries (IANA)</a></li> <li class="mb-1"><a class="text-dark" href="/process/ipr/">Intellectual property rights</a></li> <li class="mb-1"><a class="text-dark" href="/process/directorates/">Directorates and teams</a></li> <li class="mb-1"><a class="text-dark" href="/process/informal/">The IETF process: an informal guide</a></li> <li class="mb-1"><a class="text-dark" href="/process/new-work/">Bringing new work to the IETF</a></li> </ul> </div> </nav> </div> </div> </div> </main> <footer class="bg-dark text-light py-1"> <div class="container my-5"> <div class="row"> <section class="col-lg"> <div class="border-bottom u-border-lg-bottom-0 border-light border-opacity-50"> <h4 class="my-0 py-4 fs-6" role="button" aria-expanded="false"> About <i class="bi bi-chevron-down"></i> </h4> <ul class="list-unstyled opacity-75 d-grid gap-2"> <li class="nav-item"> <a href="/about/introduction/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Introduction to the IETF </a> </li> <li class="nav-item"> <a href="/about/groups/iesg/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Internet Engineering Steering Group </a> </li> <li class="nav-item"> <a href="/administration/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Administration </a> </li> <li class="nav-item"> <a href="/policies/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Privacy and policies </a> </li> <li class="nav-item"> <a href="/contact/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Contact us </a> </li> </ul> </div> </section> <section class="col-lg"> <div class="border-bottom u-border-lg-bottom-0 border-light border-opacity-50"> <h4 class="my-0 py-4 fs-6" role="button" aria-expanded="false"> Technologies <i class="bi bi-chevron-down"></i> </h4> <ul class="list-unstyled opacity-75 d-grid gap-2"> <li class="nav-item"> <a href="/technologies/netmgmt/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Automated network management </a> </li> <li class="nav-item"> <a href="/technologies/iot/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > The Internet of Things </a> </li> <li class="nav-item"> <a href="/technologies/transport/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > New transport technology </a> </li> <li class="nav-item"> <a href="/technologies/security/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Security & privacy </a> </li> <li class="nav-item"> <a href="/technologies/areas/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > IETF Areas </a> </li> </ul> </div> </section> <section class="col-lg"> <div class="border-bottom u-border-lg-bottom-0 border-light border-opacity-50"> <h4 class="my-0 py-4 fs-6" role="button" aria-expanded="false"> Meetings <i class="bi bi-chevron-down"></i> </h4> <ul class="list-unstyled opacity-75 d-grid gap-2"> <li class="nav-item"> <a href="/meeting/upcoming/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Upcoming meetings </a> </li> <li class="nav-item"> <a href="/meeting/past/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Past meetings </a> </li> <li class="nav-item"> <a href="/meeting/hackathons/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > IETF Hackathons </a> </li> <li class="nav-item"> <a href="/meeting/preparation/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Preparing for an IETF Meeting </a> </li> <li class="nav-item"> <a href="/meeting/guide-ietf-meetings/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Guide to IETF Meetings </a> </li> </ul> </div> </section> <section class="col-lg"> <div class="border-bottom u-border-lg-bottom-0 border-light border-opacity-50"> <h4 class="my-0 py-4 fs-6" role="button" aria-expanded="false"> Participate <i class="bi bi-chevron-down"></i> </h4> <ul class="list-unstyled opacity-75 d-grid gap-2"> <li class="nav-item"> <a href="/participate/get-started/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Getting started in the IETF </a> </li> <li class="nav-item"> <a href="/process/wgs/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Guide to IETF Working Groups </a> </li> <li class="nav-item"> <a href="/participate/lists/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Mailing lists </a> </li> </ul> </div> </section> <section class="col-lg"> <div class="border-bottom u-border-lg-bottom-0 border-light border-opacity-50"> <h4 class="my-0 py-4 fs-6" role="button" aria-expanded="false"> Process <i class="bi bi-chevron-down"></i> </h4> <ul class="list-unstyled opacity-75 d-grid gap-2"> <li class="nav-item"> <a href="/process/process/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Internet standards process </a> </li> <li class="nav-item"> <a href="/process/rfcs/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > About RFCs </a> </li> <li class="nav-item"> <a href="/process/new-work/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Bringing new work to the IETF </a> </li> <li class="nav-item"> <a href="/process/process/role-iesg-standards-process/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > The role of the IESG in the Standards process </a> </li> </ul> </div> </section> <section class="col-lg"> <div class="border-bottom u-border-lg-bottom-0 border-light border-opacity-50"> <h4 class="my-0 py-4 fs-6" role="button" aria-expanded="false"> Support us <i class="bi bi-chevron-down"></i> </h4> <ul class="list-unstyled opacity-75 d-grid gap-2"> <li class="nav-item"> <a href="/support-us/why-support/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Why we need your support </a> </li> <li class="nav-item"> <a href="/support-us/sponsorship/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Meeting sponsorship </a> </li> <li class="nav-item"> <a href="/support-us/donate/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > Other ways to give </a> </li> <li class="nav-item"> <a href="/support-us/donors/" class="link-underline-opacity-0 link-light fw-semibold lh-base" > IETF financial supporters </a> </li> </ul> </div> </section> </div> </div> <div class="container my-5"> <div class="d-lg-flex justify-content-between align-items-start lh-1"> <div class="d-flex fs-4 my-5 my-lg-0 ms-n2 my-5 me-3"> <a class="d-block text-light px-2" href="https://www.linkedin.com/company/internet-engineering-task-force/" rel="me" title="LinkedIn"> <i class="bi bi-linkedin"></i> </a> <a class="d-block text-light px-2" href="https://www.twitter.com/ietf" rel="me" title="Twitter"> <i class="bi bi-twitter"></i> </a> <a class="d-block text-light px-2" href="https://www.youtube.com/ietf" rel="me" title="YouTube"> <i class="bi bi-youtube"></i> </a> <a class="d-block text-light px-2" href="https://mastodon.online/@ietf" rel="me" title="Mastodon"> <i class="bi bi-mastodon"></i> </a> <a class="d-block text-light px-2" href="https://github.com/ietf/" rel="me" title="GitHub"> <i class="bi bi-github"></i> </a> </div> <ul class=" row gx-0 column-gap-5 row-gap-3 justify-content-lg-end my-5 my-lg-0 nav opacity-75 "> <li class="nav-item col-auto py-0"> <a href="/administration/overview/" class="nav-link text-light fs-10 p-0"> IETF LLC </a> </li> <li class="nav-item col-auto py-0"> <a href="https://www.rfc-editor.org" class="nav-link text-light fs-10 p-0"> RFC Editor </a> </li> <li class="nav-item col-auto py-0"> <a href="https://www.iana.org" class="nav-link text-light fs-10 p-0"> IANA </a> </li> <li class="nav-item col-auto py-0"> <a href="https://www.iab.org" class="nav-link text-light fs-10 p-0"> IAB </a> </li> <li class="nav-item col-auto py-0"> <a href="https://www.irtf.org" class="nav-link text-light fs-10 p-0"> IRTF </a> </li> <li class="nav-item col-auto py-0"> <a href="https://trustee.ietf.org" class="nav-link text-light fs-10 p-0"> IETF Trust </a> </li> </ul> </div> </div> </footer> <script> [... document.querySelectorAll("footer section")].forEach((section) => { const heading = section.querySelector("h4"); heading.addEventListener("click", () => { const expanded = section.classList.toggle("expanded"); heading.setAttribute("aria-expanded", expanded); }); }); </script> <script>window.staticRoot = "/static/dist/";</script> <script type="text/javascript"> var _paq = window._paq || []; _paq.push(['disableCookies']); _paq.push(['trackPageView']); _paq.push(['enableLinkTracking']); (function() { var u="//analytics.ietf.org/"; _paq.push(['setTrackerUrl', u+'matomo.php']); _paq.push(['setSiteId', 1]); var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0]; g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s); })(); </script> <noscript><p><img src="//analytics.ietf.org/piwik.php?idsite=1" style="border:0;" alt="" /></p></noscript> <script>(function(){function c(){var b=a.contentDocument||a.contentWindow.document;if(b){var d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'8e92eb23f93f823a',t:'MTczMjcxODg5OS4wMDAwMDA='};var a=document.createElement('script');a.nonce='';a.src='/cdn-cgi/challenge-platform/scripts/jsd/main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.style.visibility='hidden';document.body.appendChild(a);if('loading'!==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!==document.readyState&&(document.onreadystatechange=e,c())}}}})();</script></body></html>

CINXE.COM

IETF | RFCs