References from RFC 2072
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 12 |
References Referenced by |
Reference | ||
| RFC 1332 |
The PPP Internet Protocol Control Protocol (IPCP)
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 1518 |
An Architecture for IP Address Allocation with CIDR
References Referenced by |
Historic | Possible Reference | |
| RFC 1597 |
Address Allocation for Private Internets
References Referenced by |
Informational | Possible Reference | |
| RFC 1631 |
The IP Network Address Translator (NAT)
References Referenced by |
Informational | Reference | |
| RFC 1701 |
Generic Routing Encapsulation (GRE)
References Referenced by |
Informational | Possible Reference | |
| RFC 1812 |
Requirements for IP Version 4 Routers
References Referenced by |
Proposed Standard | Reference | |
| RFC 1879 |
Class A Subnet Experiment Results and Recommendations
References Referenced by |
Informational | Possible Reference | |
| RFC 1897 |
IPv6 Testing Address Allocation
References Referenced by |
Experimental | Possible Reference | |
| RFC 1900 |
Renumbering Needs Work
References Referenced by |
Informational | Reference | |
| RFC 1918 |
Address Allocation for Private Internets
References Referenced by |
Best Current Practice | Reference | |
| RFC 2058 |
Remote Authentication Dial In User Service (RADIUS)
References Referenced by |
Proposed Standard | Reference | |
| RFC 2071 |
Network Renumbering Overview: Why would I want it and what is it anyway?
References Referenced by |
Informational | Reference |