Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 6
- Abstract
- IETF procedures generally require that a standards track RFC may not have a normative reference to another standards track document at a lower maturity level or to a non standards track specification (other than specifications from other standards bodies). For example, a standards track document may not have a normative reference to an informational RFC. Exceptions to this rule are sometimes needed as the IETF uses informational RFCs to describe non-IETF standards or IETF-specific modes of use of such standards. This document clarifies and updates the procedure used in these circumstances. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
- Publication Date
- 2005-01-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC3967- Link
- https://doi.org/10.17487/RFC3967
- Author(s)
- Randy BushDr. Thomas Narten
Latest version of IETF RFC 3967
Document Versions — IETF RFC 3967
-
▶ IETF RFC 3967 (2005-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2026 [Active*]
Bibliographic Reference(s)
- IETF RFC 1321 [Active*]
- IETF RFC 1818 [Active*]
- IETF RFC 2104 [Active, Amended*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3967.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3967, Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level. Available at https://doi.org/10.17487/RFC3967
Snippet:
IETF RFC 3967, Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level. Available at https://doi.org/10.17487/RFC3967
HTML (ISO 690 compliant)
Preview:
IETF RFC 3967, Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level. Available at https://doi.org/10.17487/RFC3967
Snippet:
<span class="citation"><cite>IETF RFC 3967</cite>, Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level. Available at <a href="https://doi.org/10.17487/RFC3967" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3967</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3967, Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level
doi: 10.17487/RFC3967
url: https://doi.org/10.17487/RFC3967
doi: 10.17487/RFC3967
url: https://doi.org/10.17487/RFC3967
Snippet:
<li> <cite id="bib-rfc3967">IETF RFC 3967</cite>, Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level <span class="doi">10.17487/RFC3967</span> </li>
Referenced By
- IETF RFC 4844 [Superseded*]
- IETF RFC 4897 [Active*]