CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 17:50:46 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=ByDlnVXv2SRK8NZI48hod5qYZlLCsH0BvHKxBG3AyJw-1760118646-1.0.1.1-RQ1fgjLq9ILksvQDkZ8r_5rnKxJHv5rSvhU0h6Sbh1eIa8k00jb3vDdRGEGm892U.sFATYGOuM0NgCVB64to0uB6CA.ZHGlrjf7u03_7Atw; path=/; expires=Fri, 10-Oct-25 18:20:46 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c7f63aedba5ace-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 7669 » RFC Editor
Search RFCs
RFC 7669
Assigning Digital Object Identifiers to RFCs, October 2015
- File formats:
- Status:
- INFORMATIONAL
- Author:
- J. Levine
- Stream:
- IAB
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7669
Discuss this RFC: Send questions or comments to the mailing list iab@iab.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7669
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us