IESG Deliberations on Routing and Addressing
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 22
- Abstract
- This memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture, and it provides a brief background of the ROAD group and related activities in the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard.
- Publication Date
- 1992-11-01
- Status Note
- Informational
- DOI
10.17487/RFC1380- Link
- https://doi.org/10.17487/RFC1380
- Author(s)
- Phillip G. GrossPhilip Almquist
- Keyword(s)
- ROAD
Latest version of IETF RFC 1380
Document Versions — IETF RFC 1380
-
▶ IETF RFC 1380 (1992-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1380.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 1380, IESG Deliberations on Routing and Addressing. Available at https://doi.org/10.17487/RFC1380
Snippet:
IETF RFC 1380, IESG Deliberations on Routing and Addressing. Available at https://doi.org/10.17487/RFC1380
HTML (ISO 690 compliant)
Preview:
IETF RFC 1380, IESG Deliberations on Routing and Addressing. Available at https://doi.org/10.17487/RFC1380
Snippet:
<span class="citation"><cite>IETF RFC 1380</cite>, IESG Deliberations on Routing and Addressing. Available at <a href="https://doi.org/10.17487/RFC1380" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1380</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1380, IESG Deliberations on Routing and Addressing
doi: 10.17487/RFC1380
url: https://doi.org/10.17487/RFC1380
doi: 10.17487/RFC1380
url: https://doi.org/10.17487/RFC1380
Snippet:
<li> <cite id="bib-rfc1380">IETF RFC 1380</cite>, IESG Deliberations on Routing and Addressing <span class="doi">10.17487/RFC1380</span> </li>
Referenced By
- IETF RFC 1726 [Active*]
- IETF RFC 2101 [Active*]
- IETF RFC 4632 [Active*]