RFC 7669 - Assigning Digital Object Identifiers to RFCs

<!DOCTYPE html> <html data-bs-theme="auto" lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title> RFC 7669 - Assigning Digital Object Identifiers to RFCs </title> <meta name="viewport" content="width=device-width, initial-scale=1"> <link href="https://static.ietf.org/fonts/inter/import.css" rel="stylesheet"> <link href="https://static.ietf.org/fonts/noto-sans-mono/import.css" rel="stylesheet"> <link rel="stylesheet" href="https://static.ietf.org/dt/12.28.2/ietf/css/document_html_referenced.css"> <script type="module" crossorigin="" src="https://static.ietf.org/dt/12.28.2/assets/embedded-e653257c.js"></script> <link href="https://static.ietf.org/dt/12.28.2/assets/create-pinia-singleton-091c62b7.js" type="text/javascript" crossorigin="anonymous" rel="modulepreload" as="script" /> <link href="https://static.ietf.org/dt/12.28.2/assets/Scrollbar-7de50899.js" type="text/javascript" crossorigin="anonymous" rel="modulepreload" as="script" /> <script src="https://static.ietf.org/dt/12.28.2/ietf/js/document_html.js"></script> <script src="https://static.ietf.org/dt/12.28.2/ietf/js/theme.js"></script> <link rel="alternate" type="application/atom+xml" title="Document changes" href="/feed/document-changes/rfc7669/"> <meta name="description" content="Assigning Digital Object Identifiers to RFCs (RFC 7669, )" > <link rel="apple-touch-icon" sizes="180x180" href="https://static.ietf.org/dt/12.28.2/ietf/images/ietf-logo-nor-180.png"> <link rel="icon" sizes="32x32" href="https://static.ietf.org/dt/12.28.2/ietf/images/ietf-logo-nor-32.png"> <link rel="icon" sizes="16x16" href="https://static.ietf.org/dt/12.28.2/ietf/images/ietf-logo-nor-16.png"> <link rel="manifest" href="/site.webmanifest"> <link rel="mask-icon" href="https://static.ietf.org/dt/12.28.2/ietf/images/ietf-logo-nor-mask.svg" color="#ffffff"> <meta name="msapplication-TileColor" content="#ffffff"> <meta name="theme-color" content="#ffffff"> <meta property="og:title" content="RFC 7669: Assigning Digital Object Identifiers to RFCs"> <meta property="og:url" content="https://datatracker.ietf.org/doc/html/rfc7669"> <link rel="canonical" href="https://datatracker.ietf.org/doc/html/rfc7669"> <meta property="og:site_name" content="IETF Datatracker"> <meta property="og:description" content="This document describes the way that Digital Object Identifiers (DOIs) are assigned to past and future RFCs. The DOI is a widely used system that assigns unique identifiers to digital documents that can be queried and managed in a consistent fashion."> <meta property="og:type" content="article"> <meta property="og:image" content="https://static.ietf.org/dt/12.28.2/ietf/images/iab-logo-card.png"> <meta property="og:image:alt" content="Logo of the IAB"> <meta property="article:section" content="IRTF - Internet Architecture Board"> <meta property="og:image:type" content="image/png"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="630"> <meta name="twitter:card" content="summary_large_image"> <meta property="article:author" content="John R. Levine"> <style> .diff-form .select2-selection__rendered { direction: rtl; text-align: left; } </style> </head> <body> <noscript><iframe class="status" title="Site status" src="/status/latest"></iframe></noscript> <div class="vue-embed" data-component="Status"></div> <div class="btn-toolbar sidebar-toolbar position-fixed top-0 end-0 m-2 m-lg-3 d-print-none"> <div class="dropdown"> <button class="btn btn-outline-secondary btn-sm me-1 dropdown-toggle d-flex align-items-center" id="bd-theme" type="button" aria-expanded="false" data-bs-toggle="dropdown" aria-label="Toggle theme"> <i class="theme-icon-active bi bi-circle-half"></i> </button> <ul class="dropdown-menu" aria-labelledby="bd-theme"> <li> <button type="button" class="dropdown-item d-flex align-items-center" data-bs-theme-value="light" aria-pressed="false"> <i class="me-2 opacity-50 theme-icon bi bi-sun-fill"></i> Light<i class="bi bi-check2 ms-auto d-none"></i> </button> </li> <li> <button type="button" class="dropdown-item d-flex align-items-center" data-bs-theme-value="dark" aria-pressed="false"> <i class="me-2 opacity-50 theme-icon bi bi-moon-stars-fill"></i> Dark<i class="bi bi-check2 ms-auto d-none"></i> </button> </li> <li> <button type="button" class="dropdown-item d-flex align-items-center active" data-bs-theme-value="auto" aria-pressed="true"> <i class="me-2 opacity-50 theme-icon bi bi-circle-half"></i> Auto<i class="bi bi-check2 ms-auto d-none"></i> </button> </li> </ul> </div> <button class="btn btn-outline-secondary btn-sm sidebar-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#sidebar" aria-expanded="true" aria-controls="sidebar" aria-label="Toggle metadata sidebar" title="Toggle metadata sidebar"> <i class="bi bi-arrow-bar-left sidebar-shown"></i> <i class="bi bi-arrow-bar-right sidebar-collapsed"></i> </button> </div> <nav class="navbar bg-light-subtle px-1 fixed-top d-print-none d-md-none"> <a class="nav-link ps-1" href="/doc/rfc7669/"> RFC 7669 <br class="d-sm-none"> <span class="ms-sm-3 badge rounded-pill badge-inf"> Informational </span> </a> <button class="navbar-toggler p-1" type="button" data-bs-toggle="collapse" data-bs-target="#docinfo-collapse" aria-controls="docinfo-collapse" aria-expanded="false" aria-label="Show document information"> <span class="navbar-toggler-icon small"></span> </button> <div class="navbar-nav navbar-nav-scroll overscroll-none collapse pt-1" id="docinfo-collapse"> <div class="bg-light-subtle p-0"> <table class="table table-sm table-borderless small"> <tbody class="meta align-top"> <tr> <th scope="row"></th> <th scope="row">Title</th> <td class="edit"></td> <td>Assigning Digital Object Identifiers to RFCs</td> </tr> </tbody> <tbody class="meta align-top "> <tr> <th scope="row">Document</th> <th scope="row">Document type</th> <td class="edit"></td> <td> <span class="text-success">RFC - Informational </span> <br>October 2015 <br> <a class="btn btn-sm btn-warning" title="Click to report an error in the document." href="https://www.rfc-editor.org/errata.php#reportnew" target="_blank"> Report errata </a> <div> Was <a href="/doc/draft-iab-doi/05/">draft-iab-doi</a> (<a href="/group/iab/about/">iab</a>) </div> <div class="alert alert-warning small p-2 mt-2" role="alert"> This RFC was published on the Internet Architecture Board (IAB) stream. This RFC is <strong>not endorsed by the IETF</strong> and has <strong>no formal standing</strong> in the <a href="/doc/rfc2026/">IETF standards process</a>. </div> </td> </tr> <tr> <td></td> <th scope="row">Select version</th> <td class="edit"></td> <td> <ul class="revision-list pagination pagination-sm text-center flex-wrap my-0"> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-00" rel="nofollow"> 00 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-01" rel="nofollow"> 01 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-02" rel="nofollow"> 02 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-03" rel="nofollow"> 03 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-04" rel="nofollow"> 04 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-05" rel="nofollow"> 05 </a> </li> <li class="page-item rfc active"> <a class="page-link" href="/doc/html/rfc7669"> RFC 7669 </a> </li> </ul> </td> </tr> <tr> <td></td> <th scope="row">Compare versions</th> <td class="edit"></td> <td> <form class="form-horizontal diff-form" action="https://author-tools.ietf.org/iddiff" method="get" target="_blank"> <select class="form-select form-select-sm mb-1 select2-field" data-max-entries="1" data-width="resolve" data-allow-clear="false" data-minimum-input-length="0" aria-label="From revision" name="url1"> <option value="rfc7669"> RFC 7669 </option> <option value="draft-iab-doi-05" selected> draft-iab-doi-05 </option> <option value="draft-iab-doi-04"> draft-iab-doi-04 </option> <option value="draft-iab-doi-03"> draft-iab-doi-03 </option> <option value="draft-iab-doi-02"> draft-iab-doi-02 </option> <option value="draft-iab-doi-01"> draft-iab-doi-01 </option> <option value="draft-iab-doi-00"> draft-iab-doi-00 </option> </select> <select class="form-select form-select-sm mb-1 select2-field" data-max-entries="1" data-width="resolve" data-allow-clear="false" data-minimum-input-length="0" aria-label="To revision" name="url2"> <option value="rfc7669" selected> RFC 7669 </option> <option value="draft-iab-doi-05"> draft-iab-doi-05 </option> <option value="draft-iab-doi-04"> draft-iab-doi-04 </option> <option value="draft-iab-doi-03"> draft-iab-doi-03 </option> <option value="draft-iab-doi-02"> draft-iab-doi-02 </option> <option value="draft-iab-doi-01"> draft-iab-doi-01 </option> <option value="draft-iab-doi-00"> draft-iab-doi-00 </option> </select> <button type="submit" class="btn btn-primary btn-sm" value="--html" name="difftype"> Side-by-side </button> <button type="submit" class="btn btn-primary btn-sm" value="--hwdiff" name="difftype"> Inline </button> </form> </td> </tr> <tr> <td></td> <th scope="row">Author</th> <td class="edit"> </td> <td> <span ><a title="Datatracker profile of John R. Levine" href="/person/ietf@johnlevine.com" >John R. Levine</a> <a href="mailto:ietf%40johnlevine.com" aria-label="Compose email to ietf@johnlevine.com" title="Compose email to ietf@johnlevine.com"> <i class="bi bi-envelope"></i></a></span> <br> <a class="btn btn-primary btn-sm mt-1" href="mailto:rfc7669@ietf.org?subject=rfc7669" title="Send email to the document authors">Email authors</a> </td> </tr> <tr> <td></td> <th scope="row"> RFC stream </th> <td class="edit"> </td> <td > <a href="/stream/iab/"> <img alt="IAB Logo" class="d-lm-none w-25 mt-1" src="https://static.ietf.org/dt/12.28.2/ietf/images/iab-logo-white.svg" > <img alt="IAB Logo" class="d-dm-none w-25 mt-1" src="https://static.ietf.org/dt/12.28.2/ietf/images/iab-logo.svg" > </a> </td> </tr> <tr> <td></td> <th scope="row"> Other formats </th> <td class="edit"> </td> <td> <div class="buttonlist"> <a class="btn btn-primary btn-sm" target="_blank" href="https://www.rfc-editor.org/rfc/rfc7669.txt"> <i class="bi bi-file-text"></i> txt </a> <a class="btn btn-primary btn-sm" target="_blank" href="https://www.rfc-editor.org/rfc/rfc7669.html"> <i class="bi bi-file-code"></i> html </a> <a class="btn btn-primary btn-sm" download="rfc7669.pdf" target="_blank" href="https://www.rfc-editor.org/rfc/pdfrfc/rfc7669.txt.pdf"> <i class="bi bi-file-pdf"></i> pdf </a> <a class="btn btn-primary btn-sm" target="_blank" href="/doc/rfc7669/bibtex/"> <i class="bi bi-file-ruled"></i> bibtex </a> </div> </td> </tr> </tbody> <tr> <th scope="row"></th> <th scope="row"></th> <td class="edit"></td> <td> <a class="btn btn-sm btn-warning mb-3" target="_blank" href="https://github.com/ietf-tools/datatracker/issues/new/choose"> Report a bug <i class="bi bi-bug"></i> </a> </td> </tr> </table> </div> </div> </nav> <div class="row g-0"> <div class="col-md-9 d-flex justify-content-center lh-sm" data-bs-spy="scroll" data-bs-target="#toc-nav" data-bs-smooth-scroll="true" tabindex="0" id="content"> <div class="rfcmarkup"> <br class="noprint">  <div class="rfcmarkup"><pre>Internet Architecture Board (IAB) J. Levine Request for Comments: 7669 Taughannock Networks Category: Informational October 2015 ISSN: 2070-1721 <span class="h1">Assigning Digital Object Identifiers to RFCs</span> Abstract This document describes the way that Digital Object Identifiers (DOIs) are assigned to past and future RFCs. The DOI is a widely used system that assigns unique identifiers to digital documents that can be queried and managed in a consistent fashion. 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 the Internet Architecture Board (IAB) and represents information that the IAB has deemed valuable to provide for permanent record. It represents the consensus of the Internet Architecture Board (IAB). Documents approved for publication by the IAB are not a candidate for any level of Internet Standard; see <a href="/doc/html/rfc5741#section-2">Section 2 of RFC 5741</a>. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at <a href="http://www.rfc-editor.org/info/rfc7669">http://www.rfc-editor.org/info/rfc7669</a>. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to <a href="/doc/html/bcp78">BCP 78</a> and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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. <span class="grey">Levine Informational [Page 1]</span></pre> <hr class='noprint'/><pre class='newpage'><span id="page-2" ></span> <span class="grey"><a href="/doc/html/rfc7669">RFC 7669</a> DOIs for RFCs October 2015</span> Table of Contents <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> <a href="#section-2">2</a>. Structure and Resolution of DOIs . . . . . . . . . . . . . . <a href="#page-3">3</a> <a href="#section-3">3</a>. DOIs for RFCs . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> <a href="#section-4">4</a>. The Process of Assigning DOIs . . . . . . . . . . . . . . . . <a href="#page-4">4</a> <a href="#section-4.1">4.1</a>. Getting a DOI Prefix . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> <a href="#section-4.2">4.2</a>. Retroactively Assigning DOIs . . . . . . . . . . . . . . <a href="#page-5">5</a> <a href="#section-4.3">4.3</a>. Assigning DOIs to New RFCs . . . . . . . . . . . . . . . <a href="#page-5">5</a> <a href="#section-4.4">4.4</a>. Use of DOIs in RFCs . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> <a href="#section-4.5">4.5</a>. Possible Future Work . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> <a href="#section-5">5</a>. Internationalization . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> <a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> <a href="#section-7">7</a>. Informative References . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> IAB Members at the Time of Approval . . . . . . . . . . . . . . . <a href="#page-7">7</a> Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> The Digital Object Identifier (DOI) system assigns unique identifiers to digital documents that can be queried and managed in a consistent fashion. The structure of DOIs is defined by ISO 26324:2012 [<a href="#ref-ISO-DOI" title=""ISO 26324:2012 Information and documentation -- Digital object identifier system"">ISO-DOI</a>] and is implemented by a group of registration agencies coordinated by the International DOI Foundation. Each DOI is associated with bibliographic metadata about the object, including one or more URIs where the object can be found. The metadata is stored in a public database with entries retrieved via HTTP. DOIs are widely used by publishers and consumers of technical journals and other technical material published online. Page 15 of [<a href="#ref-CITABILITY">CITABILITY</a>] indicates that (note that citations have been omitted): Typical web addresses are unreliable for locating online resources, because they can move, change or disappear entirely. But persistent identifiers are fixed, with an infrastructure that allows for the location of the item to be updated. The result is that the identifier can provide persistent access to the data. DataCite provides such a service, and DOIs (used by DataCite) were by far the identifier most commonly mentioned by interviewees, closely followed by Handles (on which the DOI system is built). There was a keen preference for DOIs from interviewees because this is a system already used and understood by publishers for traditional publications and so the barrier to uptake would presumably be lower than for an entirely novel system. <span class="grey">Levine Informational [Page 2]</span></pre> <hr class='noprint'/><pre class='newpage'><span id="page-3" ></span> <span class="grey"><a href="/doc/html/rfc7669">RFC 7669</a> DOIs for RFCs October 2015</span> Some scholarly publishers accept DOIs as references in published documents, and some versions of BibTeX can automatically retrieve the bibliographic data for a DOI and format it. DOIs may have other advantages, such as making it easier to find the free online versions of RFCs rather than paywalled copies when following references or using some document indexes. The benefits of DOIs apply equally to documents from all of the RFC submission streams, so all RFCs are assigned DOIs. <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Structure and Resolution of DOIs</span> DOIs are an application of the Handle System defined by RFCs [<a href="/doc/html/rfc3650" title=""Handle System Overview"">RFC3650</a>], [<a href="/doc/html/rfc3651" title=""Handle System Namespace and Service Definition"">RFC3651</a>], and [<a href="/doc/html/rfc3652" title=""Handle System Protocol (ver 2.1) Specification"">RFC3652</a>]. For example, a DOI for an RFC might be as follows: 10.17487/rfc1149 The first part of a DOI is the number 10, which means a DOI within the Handle System, followed by a dot and a unique number assigned to a publisher, in this case 17487. This part is the DOI prefix. Following that is a slash and a text string assigned by the publisher, called the DOI suffix. DOIs are treated as opaque identifiers. The DOI suffixes assigned to RFCs are currently based on the "doc-id" field of the RFC index in XML (rfc-index.xml), but the suffix of future RFCs might be based on something else if circumstances change. Hence, the reliable way to find the DOI for an RFC is not to guess, but to look it up in the RFC index or on the RFC Editor website <<a href="https://www.rfc-editor.org/">https://www.rfc-editor.org/</a>>. RFC references created from entries in the usual bibxml libraries will have DOIs included automatically. Although the Handle System has its own protocol described in [<a href="/doc/html/rfc3652" title=""Handle System Protocol (ver 2.1) Specification"">RFC3652</a>], the usual way to look up a DOI is to use web lookup. A proposed "doi:" URN was never widely implemented, so the standard way to look up a DOI is to use the public HTTP proxy at <<a href="https://dx.doi.org">https://dx.doi.org</a>>. The example DOI above could be looked up at: <a href="https://dx.doi.org/10.17487/rfc1149">https://dx.doi.org/10.17487/rfc1149</a> Whenever a publisher assigns a DOI, it provides the bibliographic metadata for the object (henceforth called a document, since that is what they are in this context) to its registration agency that then makes it available to clients that look up DOIs. The document's metadata is typically uploaded to the registration agency in XML using an HTTP-based API. Users or publishing software can retrieve <span class="grey">Levine Informational [Page 3]</span></pre> <hr class='noprint'/><pre class='newpage'><span id="page-4" ></span> <span class="grey"><a href="/doc/html/rfc7669">RFC 7669</a> DOIs for RFCs October 2015</span> the metadata by fetching the DOI's URL and using standard HTTP content negotiation to request application/citeproc+json, application/rdf+xml, or other bibliographic formats. Publishers have considerable flexibility as to what resides at the URI(s) to which a DOI refers. Sometimes it's the document itself, while for commercial publishers it's typically a page with the abstract, bibliographic information, and some way to buy the actual document. Because some RFCs are in multiple formats (e.g., Postscript and text), an appropriate URI is that of the RFC Editor's info page that has the document's abstract and links to the document(s) in various formats. Hence, the URI above, when fetched via an HTTP request that accepts text/html, redirects to: <a href="https://www.rfc-editor.org/info/rfc1149">https://www.rfc-editor.org/info/rfc1149</a> More information on the structure and use of DOIs is in the DOI Handbook [<a href="#ref-DOI-HB" title=""DOI Handbook"">DOI-HB</a>]. <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. DOIs for RFCs</span> With DOIs assigned to each RFC, it is useful to include DOI information in the XML bibliography as a "seriesInfo" item, so that rendering engines can display it if desired. Online databases and indexes that include RFCs should be updated to include the DOI, e.g., the ACM Digital Library. (A practical advantage of this is that the DOI would link directly to the RFC Editor, rather than perhaps to a copy of an RFC behind a paywall.) Since RFCs are immutable, existing RFCs still don't mention their own DOIs within the RFCs themselves, but putting their DOIs into indexes would provide value. <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The Process of Assigning DOIs</span> There are three phases to assigning DOIs to RFCs: getting a DOI prefix, retroactively assigning DOIs to existing documents, and updating the publication process to assign DOIs as new RFCs are published. <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Getting a DOI Prefix</span> There are ten registration agencies [<a href="#ref-DOI-RA" title=""DOI Registration Agencies"">DOI-RA</a>] that assign DOI prefixes. Most of them serve specialized audiences or limited geographic areas, but there are a few that handle scholarly and technical materials. All registration agencies charge for DOIs to defray the cost of maintaining the metadata databases. <span class="grey">Levine Informational [Page 4]</span></pre> <hr class='noprint'/><pre class='newpage'><span id="page-5" ></span> <span class="grey"><a href="/doc/html/rfc7669">RFC 7669</a> DOIs for RFCs October 2015</span> The RFC Editor chose CrossRef, an agency widely used by journal publishers. The prices associated with CrossRef membership are on the order of $660.00 per year for membership, deposit fees of $0.15 cents per document for a bulk upload of the backfile (the existing RFCs), and $1.00 per document to deposit them as they are published. The RFC Editor's DOI prefix is 10.17487. <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Retroactively Assigning DOIs</span> Other than paying the deposit fees, assigning DOIs to all of the existing RFCs was primarily a software problem. The RFC Production Center's internal database was updated to include a DOI field for each RFC, the schema for rfc-index.xml was updated to include a DOI field, and the scripts that create the XML and text indexes were updated to include the DOI for each RFC. A specialized DOI submission script extracted the metadata for all of the RFCs from the XML index and submitted it to the registration agency using the agency's online API. <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Assigning DOIs to New RFCs</span> As RFCs are published, the publication software assigns a DOI to each new RFC. The submission script extracts the metadata for new RFCs from the XML index and submits the information for new RFCs to the registration agency. <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Use of DOIs in RFCs</span> The DOI agency requests that documents that are assigned DOIs in turn include DOIs when possible when referring to other organizations' documents. DOIs can be listed using the existing seriesInfo field in the xml2rfc reference entity, and authors are requested provide DOIs for non-RFC documents when possible. The RFC Production Center might add missing DOIs when it's easy to do so, e.g., when the same reference with a DOI has appeared in a prior RFC, or a quick online search finds the DOI. Where the citation libraries include DOIs, the output (references created from those citation libraries) will include DOIs. The RFC Style Guide [<a href="#ref-RFC-STYLE">RFC-STYLE</a>] has been updated to describe the rules for including DOIs in the References sections of RFCs. <span class="grey">Levine Informational [Page 5]</span></pre> <hr class='noprint'/><pre class='newpage'><span id="page-6" ></span> <span class="grey"><a href="/doc/html/rfc7669">RFC 7669</a> DOIs for RFCs October 2015</span> <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Possible Future Work</span> Since it is usually possible to retrieve the bibliographic information for a document from its DOI (as BibTeX can do, described above), it might also be worth adding this feature to xml2rfc, so a reference with only a DOI could be automatically fetched and expanded. <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Internationalization</span> Adding DOIs presents no new internationalization issues. Since DOIs are opaque, the characters used in any particular DOI are unimportant beyond ensuring that they can be represented where needed. The Handle System says they are UTF-8-encoded Unicode, but in practice all DOIs appear to use only printable ASCII characters. The metadata for each RFC is uploaded as UTF-8-encoded XML. <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> The DOI system adds a new way to locate RFCs and a bibliographic database containing a description of each RFC. The existing locations and bibliographic info are essentially unchanged, so there is no new dependency on the DOI system. Were CrossRef or the DOI database to suffer a security breach, it is hypothetically possible that users would be directed to locations other than the RFC Editor's web site or would retrieve incorrect bibliographic data, but the actual RFCs would remain intact. <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Informative References</span> [<a id="ref-CITABILITY">CITABILITY</a>] Kotarski, R., Reilly, S., Schrimpf, S., Smit, E., and K. Walshe, "Report on best practices for citability of data and on evolving roles in scholarly communication", 2012, <<a href="http://www.stm-assoc.org/2012_07_10_STM_Research_Data_Group_Data_Citation_and_Evolving_Roles_ODE_Report.pdf">http://www.stm-assoc.org/2012_07_10_STM_Research_Data_</a> <a href="http://www.stm-assoc.org/2012_07_10_STM_Research_Data_Group_Data_Citation_and_Evolving_Roles_ODE_Report.pdf">Group_Data_Citation_and_Evolving_Roles_ODE_Report.pdf</a>>. [<a id="ref-DOI-HB">DOI-HB</a>] International DOI Foundation, "DOI Handbook", DOI 10.1000/182, April 2012, <<a href="https://www.doi.org/hb.html">http://www.doi.org/hb.html</a>>. [<a id="ref-DOI-RA">DOI-RA</a>] International DOI Foundation, "DOI Registration Agencies", July 2015, <<a href="https://www.doi.org/registration_agencies.html">http://www.doi.org/registration_agencies.html</a>>. <span class="grey">Levine Informational [Page 6]</span></pre> <hr class='noprint'/><pre class='newpage'><span id="page-7" ></span> <span class="grey"><a href="/doc/html/rfc7669">RFC 7669</a> DOIs for RFCs October 2015</span> [<a id="ref-ISO-DOI">ISO-DOI</a>] International Organization for Standardization (ISO), "ISO 26324:2012 Information and documentation -- Digital object identifier system", June 2012, <<a href="http://www.iso.org/iso/catalogue_detail?csnumber=43506">http://www.iso.org/iso/catalogue_detail?csnumber=43506</a>>. [<a id="ref-RFC-STYLE">RFC-STYLE</a>] RFC Editor, "RFC Editor Style Guide", <<a href="https://www.rfc-editor.org/styleguide/">https://www.rfc-editor.org/styleguide/</a>>. [<a id="ref-RFC3650">RFC3650</a>] Sun, S., Lannom, L., and B. Boesch, "Handle System Overview", <a href="/doc/html/rfc3650">RFC 3650</a>, DOI 10.17487/RFC3650, November 2003, <<a href="http://www.rfc-editor.org/info/rfc3650">http://www.rfc-editor.org/info/rfc3650</a>>. [<a id="ref-RFC3651">RFC3651</a>] Sun, S., Reilly, S., and L. Lannom, "Handle System Namespace and Service Definition", <a href="/doc/html/rfc3651">RFC 3651</a>, DOI 10.17487/RFC3651, November 2003, <<a href="http://www.rfc-editor.org/info/rfc3651">http://www.rfc-editor.org/info/rfc3651</a>>. [<a id="ref-RFC3652">RFC3652</a>] Sun, S., Reilly, S., Lannom, L., and J. Petrone, "Handle System Protocol (ver 2.1) Specification", <a href="/doc/html/rfc3652">RFC 3652</a>, DOI 10.17487/RFC3652, November 2003, <<a href="http://www.rfc-editor.org/info/rfc3652">http://www.rfc-editor.org/info/rfc3652</a>>. IAB Members at the Time of Approval Jari Arkko (IETF Chair) Mary Barnes Marc Blanchet Ralph Droms Ted Hardie Joe Hildebrand Russ Housley Erik Nordmark Robert Sparks Andrew Sullivan (IAB Chair) Dave Thaler Brian Trammell Suzanne Woolf <span class="grey">Levine Informational [Page 7]</span></pre> <hr class='noprint'/><pre class='newpage'><span id="page-8" ></span> <span class="grey"><a href="/doc/html/rfc7669">RFC 7669</a> DOIs for RFCs October 2015</span> Author's Address John Levine Taughannock Networks PO Box 727 Trumansburg, NY 14886 Phone: +1 831 480 2300 Email: standards@taugh.com URI: <a href="http://jl.ly">http://jl.ly</a> Levine Informational [Page 8] </pre></div> </div> </div> <div class="d-print-none col-md-3 bg-light-subtle collapse show" id="sidebar"> <div class="position-fixed border-start sidebar overflow-scroll overscroll-none no-scrollbar"> <div class="d-flex flex-column vh-100 pt-2 pt-lg-3 ps-3 pl-md-2 pl-lg-3"> <div> <a class="btn btn-primary btn-sm" href="/doc/rfc7669/">Datatracker</a> <p class="fw-bold pt-2"> RFC 7669 <br> <span class="text-success">RFC - Informational </span> </p> </div> <ul class="nav nav-tabs nav-fill small me-2" role="tablist"> <li class="nav-item" role="presentation" title="Document information"> <button class="nav-link px-2" id="docinfo-tab" data-bs-toggle="tab" data-bs-target="#docinfo-tab-pane" type="button" role="tab" aria-controls="docinfo-tab-pane" aria-selected="true"> <i class="bi bi-info-circle"></i><span class="d-none d-md-block d-xl-inline ms-xl-1">Info</span> </button> </li> <li class="nav-item" role="presentation" title="Table of contents"> <button class="nav-link px-2" id="toc-tab" data-bs-toggle="tab" data-bs-target="#toc-tab-pane" type="button" role="tab" aria-controls="toc-tab-pane" aria-selected="false"> <i class="bi bi-list-ol"></i><span class="d-none d-md-block d-xl-inline ms-xl-1">Contents</span> </button> </li> <li class="nav-item" role="presentation" title="Preferences"> <button class="nav-link px-2" id="pref-tab" data-bs-toggle="tab" data-bs-target="#pref-tab-pane" type="button" role="tab" aria-controls="pref-tab-pane" aria-selected="false"> <i class="bi bi-gear"></i><span class="d-none d-md-block d-xl-inline ms-xl-1">Prefs</span> </button> </li> </ul> <div class="overflow-auto tab-content pt-2 me-2"> <div class="tab-pane" id="docinfo-tab-pane" role="tabpanel" aria-labelledby="docinfo-tab" tabindex="0"> <table class="table table-sm table-borderless"> <tbody class="meta align-top "> <tr> <th scope="row">Document</th> <th scope="row">Document type</th> <td class="edit"></td> <td> <span class="text-success">RFC - Informational </span> <br>October 2015 <br> <a class="btn btn-sm btn-warning" title="Click to report an error in the document." href="https://www.rfc-editor.org/errata.php#reportnew" target="_blank"> Report errata </a> <div> Was <a href="/doc/draft-iab-doi/05/">draft-iab-doi</a> (<a href="/group/iab/about/">iab</a>) </div> <div class="alert alert-warning small p-2 mt-2" role="alert"> This RFC was published on the Internet Architecture Board (IAB) stream. This RFC is <strong>not endorsed by the IETF</strong> and has <strong>no formal standing</strong> in the <a href="/doc/rfc2026/">IETF standards process</a>. </div> </td> </tr> <tr> <td></td> <th scope="row">Select version</th> <td class="edit"></td> <td> <ul class="revision-list pagination pagination-sm text-center flex-wrap my-0"> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-00" rel="nofollow"> 00 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-01" rel="nofollow"> 01 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-02" rel="nofollow"> 02 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-03" rel="nofollow"> 03 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-04" rel="nofollow"> 04 </a> </li> <li class="page-item"> <a class="page-link" href="/doc/html/draft-iab-doi-05" rel="nofollow"> 05 </a> </li> <li class="page-item rfc active"> <a class="page-link" href="/doc/html/rfc7669"> RFC 7669 </a> </li> </ul> </td> </tr> <tr> <td></td> <th scope="row">Compare versions</th> <td class="edit"></td> <td> <form class="form-horizontal diff-form" action="https://author-tools.ietf.org/iddiff" method="get" target="_blank"> <select class="form-select form-select-sm mb-1 select2-field" data-max-entries="1" data-width="resolve" data-allow-clear="false" data-minimum-input-length="0" aria-label="From revision" name="url1"> <option value="rfc7669"> RFC 7669 </option> <option value="draft-iab-doi-05" selected> draft-iab-doi-05 </option> <option value="draft-iab-doi-04"> draft-iab-doi-04 </option> <option value="draft-iab-doi-03"> draft-iab-doi-03 </option> <option value="draft-iab-doi-02"> draft-iab-doi-02 </option> <option value="draft-iab-doi-01"> draft-iab-doi-01 </option> <option value="draft-iab-doi-00"> draft-iab-doi-00 </option> </select> <select class="form-select form-select-sm mb-1 select2-field" data-max-entries="1" data-width="resolve" data-allow-clear="false" data-minimum-input-length="0" aria-label="To revision" name="url2"> <option value="rfc7669" selected> RFC 7669 </option> <option value="draft-iab-doi-05"> draft-iab-doi-05 </option> <option value="draft-iab-doi-04"> draft-iab-doi-04 </option> <option value="draft-iab-doi-03"> draft-iab-doi-03 </option> <option value="draft-iab-doi-02"> draft-iab-doi-02 </option> <option value="draft-iab-doi-01"> draft-iab-doi-01 </option> <option value="draft-iab-doi-00"> draft-iab-doi-00 </option> </select> <button type="submit" class="btn btn-primary btn-sm" value="--html" name="difftype"> Side-by-side </button> <button type="submit" class="btn btn-primary btn-sm" value="--hwdiff" name="difftype"> Inline </button> </form> </td> </tr> <tr> <td></td> <th scope="row">Author</th> <td class="edit"> </td> <td> <span ><a title="Datatracker profile of John R. Levine" href="/person/ietf@johnlevine.com" >John R. Levine</a> <a href="mailto:ietf%40johnlevine.com" aria-label="Compose email to ietf@johnlevine.com" title="Compose email to ietf@johnlevine.com"> <i class="bi bi-envelope"></i></a></span> <br> <a class="btn btn-primary btn-sm mt-1" href="mailto:rfc7669@ietf.org?subject=rfc7669" title="Send email to the document authors">Email authors</a> </td> </tr> <tr> <td></td> <th scope="row"> RFC stream </th> <td class="edit"> </td> <td > <a href="/stream/iab/"> <img alt="IAB Logo" class="d-lm-none w-25 mt-1" src="https://static.ietf.org/dt/12.28.2/ietf/images/iab-logo-white.svg" > <img alt="IAB Logo" class="d-dm-none w-25 mt-1" src="https://static.ietf.org/dt/12.28.2/ietf/images/iab-logo.svg" > </a> </td> </tr> <tr> <td></td> <th scope="row"> Other formats </th> <td class="edit"> </td> <td> <div class="buttonlist"> <a class="btn btn-primary btn-sm" target="_blank" href="https://www.rfc-editor.org/rfc/rfc7669.txt"> <i class="bi bi-file-text"></i> txt </a> <a class="btn btn-primary btn-sm" target="_blank" href="https://www.rfc-editor.org/rfc/rfc7669.html"> <i class="bi bi-file-code"></i> html </a> <a class="btn btn-primary btn-sm" download="rfc7669.pdf" target="_blank" href="https://www.rfc-editor.org/rfc/pdfrfc/rfc7669.txt.pdf"> <i class="bi bi-file-pdf"></i> pdf </a> <a class="btn btn-primary btn-sm" target="_blank" href="/doc/rfc7669/bibtex/"> <i class="bi bi-file-ruled"></i> bibtex </a> </div> </td> </tr> </tbody> </table> <a class="btn btn-sm btn-warning mb-3" target="_blank" href="https://github.com/ietf-tools/datatracker/issues/new/choose"> Report a datatracker bug <i class="bi bi-bug"></i> </a> </div> <div class="tab-pane mb-5" id="toc-tab-pane" role="tabpanel" aria-labelledby="toc-tab" tabindex="0"> <nav class="nav nav-pills flex-column small" id="toc-nav"> </nav> </div> <div class="tab-pane mb-5 small" id="pref-tab-pane" role="tabpanel" aria-labelledby="pref-tab" tabindex="0"> <label class="form-label fw-bold mb-2">Show sidebar by default</label> <div class="btn-group-vertical btn-group-sm d-flex" role="group"> <input type="radio" class="btn-check" name="sidebar" id="on-radio"> <label class="btn btn-outline-primary" for="on-radio">Yes</label> <input type="radio" class="btn-check" name="sidebar" id="off-radio"> <label class="btn btn-outline-primary" for="off-radio">No</label> </div> <label class="form-label fw-bold mt-4 mb-2">Tab to show by default</label> <div class="btn-group-vertical btn-group-sm d-flex" role="group"> <input type="radio" class="btn-check" name="deftab" id="docinfo-radio"> <label class="btn btn-outline-primary" for="docinfo-radio"> <i class="bi bi-info-circle me-1"></i>Info </label> <input type="radio" class="btn-check" name="deftab" id="toc-radio"> <label class="btn btn-outline-primary" for="toc-radio"> <i class="bi bi-list-ol me-1"></i>Contents </label> </div> <label class="form-label fw-bold mt-4 mb-2">HTMLization configuration</label> <div class="btn-group-vertical btn-group-sm d-flex" role="group"> <input type="radio" class="btn-check" name="htmlconf" id="txt-radio"> <label class="btn btn-outline-primary" for="txt-radio" title="This is the traditional HTMLization method."> <i class="bi bi-badge-sd me-1"></i>HTMLize the plaintext </label> <input type="radio" class="btn-check" name="htmlconf" id="html-radio"> <label class="btn btn-outline-primary" for="html-radio" title="This is the modern HTMLization method."> <i class="bi bi-badge-hd me-1"></i>Plaintextify the HTML </label> </div> <label class="form-label fw-bold mt-4 mb-2" for="ptsize">Maximum font size</label> <input type="range" class="form-range" min="7" max="16" id="ptsize" oninput="ptdemo.value = ptsize.value"> <label class="form-label fw-bold mt-4 mb-2">Page dependencies</label> <div class="btn-group-vertical btn-group-sm d-flex" role="group"> <input type="radio" class="btn-check" name="pagedeps" id="inline-radio"> <label class="btn btn-outline-primary" for="inline-radio" title="Generate larger, standalone web pages that do not require network access to render."> <i class="bi bi-box me-1"></i>Inline </label> <input type="radio" class="btn-check" name="pagedeps" id="reference-radio"> <label class="btn btn-outline-primary" for="reference-radio" title="Generate regular web pages that require network access to render."> <i class="bi bi-link-45deg me-1"></i>Reference </label> </div> <label class="form-label fw-bold mt-4 mb-2">Citation links</label> <div class="btn-group-vertical btn-group-sm d-flex" role="group"> <input type="radio" class="btn-check" name="reflinks" id="refsection-radio"> <label class="btn btn-outline-primary" for="refsection-radio" title="Citation links go to the reference section."> <i class="bi bi-arrow-clockwise"></i> Go to reference section </label> <input type="radio" class="btn-check" name="reflinks" id="citation-radio"> <label class="btn btn-outline-primary" for="citation-radio" title="Citation links go directly to the cited document."> <i class="bi bi-link-45deg me-1"></i>Go to linked document </label> </div> </div> </div> </div> </div> </div> </div> <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', 7]); 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=7" 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:'8e9113e9bc0b9fbc',t:'MTczMjY5OTU5OC4wMDAwMDA='};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

RFC 7669 - Assigning Digital Object Identifiers to RFCs