Assigning Digital Object Identifiers to RFCs
draft-levine-doi-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | John R. Levine | ||
| Last updated | 2014-02-06 (Latest revision 2014-01-10) | ||
| Replaced by | draft-iab-doi | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-iab-doi | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)