Address Allocation for Private Internets
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 9
- Abstract
- This document describes address allocation for private internets. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
- Publication Date
- 1996-02-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC1918- Link
- https://doi.org/10.17487/RFC1918
- Author(s)
- Yakov RekhterRobert MoskowitzDaniel KarrenbergGeert Jan de GrootEliot Lear
- Keyword(s)
- TCP/IP, Networks
Latest version of IETF RFC 1918
Document Versions — IETF RFC 1918
-
▶ IETF RFC 1918 (1996-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- RFC6761 — RFC6761 EXTERNAL
Bibliographic Reference(s)
- IETF RFC 1466 [Superseded*]
- IETF RFC 1518 [Active*]
- IETF RFC 1519 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1918.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 1918, Address Allocation for Private Internets. Available at https://doi.org/10.17487/RFC1918
Snippet:
IETF RFC 1918, Address Allocation for Private Internets. Available at https://doi.org/10.17487/RFC1918
HTML (ISO 690 compliant)
Preview:
IETF RFC 1918, Address Allocation for Private Internets. Available at https://doi.org/10.17487/RFC1918
Snippet:
<span class="citation"><cite>IETF RFC 1918</cite>, Address Allocation for Private Internets. Available at <a href="https://doi.org/10.17487/RFC1918" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1918</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1918, Address Allocation for Private Internets
doi: 10.17487/RFC1918
url: https://doi.org/10.17487/RFC1918
doi: 10.17487/RFC1918
url: https://doi.org/10.17487/RFC1918
Snippet:
<li> <cite id="bib-rfc1918">IETF RFC 1918</cite>, Address Allocation for Private Internets <span class="doi">10.17487/RFC1918</span> </li>
Referenced By
- Strategies to Protect Time Transfer in ST 2059-2 PTP Networks [Active]
- A Multipronged Approach to Effectively Secure SMPTE ST 2059 Time Transfer [Active]
- Strategies for Securing ST 2059-2 PTP Networks [Active]
- IETF RFC 2050 [Superseded*]
- IETF RFC 2071 [Active*]
- IETF RFC 2072 [Active*]
- IETF RFC 2101 [Active*]
- IETF RFC 2260 [Active*]
- IETF RFC 2267 [Superseded*]
- IETF RFC 2529 [Active*]
- IETF RFC 2661 [Active*]
- IETF RFC 2663 [Active*]
- IETF RFC 2694 [Active*]
- IETF RFC 2709 [Active*]
- IETF RFC 2764 [Active*]
- IETF RFC 2767 [Superseded*]
- IETF RFC 2775 [Active*]
- IETF RFC 2827 [Active*]
- IETF RFC 2893 [Superseded*]
- IETF RFC 2993 [Active*]
- IETF RFC 3013 [Active*]
- IETF RFC 3022 [Active*]
- IETF RFC 3024 [Active*]
- IETF RFC 3027 [Active*]
- IETF RFC 3056 [Active*]
- IETF RFC 3102 [Active*]
- IETF RFC 3103 [Active*]
- IETF RFC 3330 [Superseded*]
- IETF RFC 3456 [Active*]
- IETF RFC 3484 [Superseded*]
- IETF RFC 3550 [Active*]
- IETF RFC 3809 [Active*]
- IETF RFC 3871 [Active*]
- IETF RFC 3879 [Active*]
- IETF RFC 3927 [Active*]
- IETF RFC 4008 [Superseded*]
- IETF RFC 4031 [Active*]
- IETF RFC 4110 [Active*]
- IETF RFC 4111 [Active*]
- IETF RFC 4116 [Active*]
- IETF RFC 4365 [Active*]
- IETF RFC 4436 [Active*]
- IETF RFC 4710 [Active*]
- IETF RFC 4727 [Active*]
- IETF RFC 5766 [Superseded*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6269 [Active*]
- IETF RFC 6724 [Active*]
- IETF RFC 7624 [Active*]
- IETF RFC 7752 [Superseded*]
- IETF RFC 9000 [Active*]