Assigning Digital Object Identifiers to RFCs
draft-iab-doi-03

The information below is for an old version of the document
Document Type Active Internet-Draft
Last updated 2015-05-28
Replaces draft-levine-doi
Stream IAB
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream IAB state Active IAB Document
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                          J. Levine
Internet-Draft                                      Taughannock Networks
Intended status: Informational                              May 28, 2015
Expires: November 29, 2015

              Assigning Digital Object Identifiers to RFCs
                            draft-iab-doi-03

Abstract

   The Digital Object Identifier (DOI) is a widely used system that
   assigns unique identifiers to digital documents that can be queried
   and managed in a consistent fashion.  We describe the way that DOIs
   are assigned to past and future RFCs.

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 http://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 November 29, 2015.

Copyright Notice

   Copyright (c) 2015 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
   (http://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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Levine                  Expires November 29, 2015               [Page 1]
Internet-Draft                DOIs for RFCs                     May 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Structure and resolution of DOIs  . . . . . . . . . . . . . .   3
   3.  DOIs for RFCs . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  The process of assigning DOIs . . . . . . . . . . . . . . . .   4
     4.1.  Getting a DOI prefix  . . . . . . . . . . . . . . . . . .   4
     4.2.  Retroactively assigning DOIs  . . . . . . . . . . . . . .   4
     4.3.  Assigning DOIs to new RFCs  . . . . . . . . . . . . . . .   5
     4.4.  Use of DOIs in RFCs . . . . . . . . . . . . . . . . . . .   5
   5.  Informative References  . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   6
     A.1.  Changes from -03 to -04 . . . . . . . . . . . . . . . . .   6
     A.2.  Changes from -02 to -03 . . . . . . . . . . . . . . . . .   6
     A.3.  Changes from -01 to -02 . . . . . . . . . . . . . . . . .   6
     A.4.  Changes from -00 to -01 . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Digital Object Identifier (DOI) is a widely used system that
   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 [ISO-DOI] 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 DOI
   system also provides many features not relevant to RFCs, such as the
   ability to update the metadata after the DOI is assigned, and for
   organizations to maintain local caches of metadata, e.g., a
   university or corporate library that tracks its copies of purchased
   documents so subsequent users don't buy them again.

   The wide use of DOIs suggests that even though RFCs can be downloaded
   directly from the IETF for free, organizations that use DOIs can have
   trouble locating documents that don't have DOIs.  DOIs with metadata
   that points to the existing free online RFCs would make RFCs easier
   to find and use.  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.  Hence DOIs
   would make RFCs easier to cite.

   The benefits of DOIs apply equally to documents from all of the RFC
   submission streams, so all RFCs are assigned DOIs.

Levine                  Expires November 29, 2015               [Page 2]
Internet-Draft                DOIs for RFCs                     May 2015

2.  Structure and resolution of DOIs
Show full document text