Assigning Digital Object Identifiers to RFCs
draft-levine-doi-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Author | John Levine | ||
| Last updated | 2014-02-06 (latest revision 2014-01-10) | ||
| Replaced by | RFC 7669 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-iab-doi | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-levine-doi-00.txt
https://www.ietf.org/archive/id/draft-levine-doi-00.txt
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
John Levine (standards@taugh.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)