References from rfc3495
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 14 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 1035 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | Possible Reference | |
| RFC 1510 |
The Kerberos Network Authentication Service (V5)
References Referenced by |
Historic | normatively references | Downref |
| RFC 2131 |
Dynamic Host Configuration Protocol
References Referenced by |
Draft Standard | normatively references | |
| RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 3118 |
Authentication for DHCP Messages
References Referenced by |
Proposed Standard | informatively references | |
| RFC 3396 |
Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)
References Referenced by |
Proposed Standard | normatively references | |
| STD 1 |
Internet Official Protocol Standards
References Referenced by |
Historic | Possible Reference | Possible Downref |
| STD 13 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | normatively references |