Assigning Experimental and Testing Numbers Considered Useful
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 7
- Abstract
- When experimenting with or extending protocols, it is often necessary to use some sort of protocol number or constant in order to actually test or experiment with the new function, even when testing in a closed environment. For example, to test a new DHCP option, one needs an option number to identify the new function. This document recommends that when writing IANA Considerations sections, authors should consider assigning a small range of numbers for experimentation purposes that implementers can use when testing protocol extensions or other new features. This document reserves some ranges of numbers for experimentation purposes in specific protocols where the need to support experimentation has been identified.
- Publication Date
- 2004-01-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC3692- Link
- https://doi.org/10.17487/RFC3692
- Author(s)
- Dr. Thomas Narten
- Keyword(s)
- IANA
Latest version of IETF RFC 3692
Document Versions — IETF RFC 3692
-
▶ IETF RFC 3692 (2004-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2434 [Superseded*]
- IETF RFC 2780 [Active*]
Bibliographic Reference(s)
- IETF RFC 791 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3692.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 3692, Assigning Experimental and Testing Numbers Considered Useful. Available at https://doi.org/10.17487/RFC3692
Snippet:
IETF RFC 3692, Assigning Experimental and Testing Numbers Considered Useful. Available at https://doi.org/10.17487/RFC3692
HTML (ISO 690 compliant)
Preview:
IETF RFC 3692, Assigning Experimental and Testing Numbers Considered Useful. Available at https://doi.org/10.17487/RFC3692
Snippet:
<span class="citation"><cite>IETF RFC 3692</cite>, Assigning Experimental and Testing Numbers Considered Useful. Available at <a href="https://doi.org/10.17487/RFC3692" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3692</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3692, Assigning Experimental and Testing Numbers Considered Useful
doi: 10.17487/RFC3692
url: https://doi.org/10.17487/RFC3692
doi: 10.17487/RFC3692
url: https://doi.org/10.17487/RFC3692
Snippet:
<li> <cite id="bib-rfc3692">IETF RFC 3692</cite>, Assigning Experimental and Testing Numbers Considered Useful <span class="doi">10.17487/RFC3692</span> </li>
Referenced By
- IETF RFC 3748 [Active*]
- IETF RFC 4340 [Active*]
- IETF RFC 4341 [Active*]
- IETF RFC 4342 [Active*]
- IETF RFC 4581 [Active*]
- IETF RFC 4727 [Active*]
- IETF RFC 5191 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5494 [Active*]
- IETF RFC 5586 [Active*]
- IETF RFC 5719 [Superseded*]
- IETF RFC 5872 [Active*]
- IETF RFC 5971 [Active*]
- IETF RFC 6335 [Active*]
- IETF RFC 6424 [Superseded*]
- IETF RFC 6495 [Active*]
- IETF RFC 6648 [Active*]
- IETF RFC 6709 [Active*]
- IETF RFC 6994 [Active*]
- IETF RFC 7045 [Active*]
- IETF RFC 7153 [Active*]
- IETF RFC 8126 [Active*]
- IETF RFC 9184 [Active*]
- IETF RFC 9868 [Active*]