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

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

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

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 propose a method to assign
   DOIs 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 August 9, 2014.

Copyright Notice

   Copyright (c) 2014 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 August 9, 2014                 [Page 1]
Internet-Draft                DOIs for RFCs                February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Structure and resolution of DOIs  . . . . . . . . . . . . . .   2
   3.  DOIs for RFCs . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  The process of assigning DOIs . . . . . . . . . . . . . . . .   3
     4.1.  Getting a DOI prefix  . . . . . . . . . . . . . . . . . .   4
     4.2.  Retroactively assigning DOIs  . . . . . . . . . . . . . .   4
     4.3.  Assigning DOIs to new RFCs  . . . . . . . . . . . . . . .   4
   5.  Informative References  . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

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 accompanied by metadata about the object, such as 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 non-DOI documents.  DOIs with metadata that points
   to the existing free online RFCs would make RFCs easier to find.
   Some scholarly publishers accept DOIs as references in published
   documents, so DOIs would make RFCs easier to cite.

2.  Structure and resolution of DOIs

   DOIs are an application of the handle system defined by RFCs
   [RFC3650], [RFC3651], and [RFC3652].  A DOI for an RFC might be

       10.123456/rfc1234

   The first part of a DOI is the number 10, which means a DOI within
   the handle system, a dot, and a unique number assigned to a
   publisher, in this example 123456.  This part is the DOI prefix.
   Following that is a slash and a text string assigned by the
   publisher, called the DOI suffix.  A reasonable way to assign DOIs

Levine                   Expires August 9, 2014                 [Page 2]
Internet-Draft                DOIs for RFCs                February 2014
Show full document text