References from RFC 3397
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 11 | References Referenced by | informatively references | ||
| BCP 14 | References Referenced by | normatively references | ||
| RFC 1035 | Domain names - implementation and specification References Referenced by | Internet Standard | normatively references | |
| RFC 1535 | A Security Problem and Proposed Correction With Widely Deployed DNS Software References Referenced by | Informational | informatively references | |
| RFC 1536 | Common DNS Implementation Errors and Suggested Fixes References Referenced by | Informational | normatively references | Downref |
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 2131 | Dynamic Host Configuration Protocol References Referenced by | Draft Standard | normatively references | |
| RFC 2132 | DHCP Options and BOOTP Vendor Extensions References Referenced by | Draft Standard | informatively references | |
| RFC 2535 | Domain Name System Security Extensions References Referenced by | Proposed Standard | informatively references | |
| RFC 2937 | The Name Service Search Option for DHCP References Referenced by | Proposed Standard | informatively references | |
| RFC 3118 | Authentication for DHCP Messages References Referenced by | Proposed Standard | normatively references | |
| RFC 3396 | Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4) References Referenced by | Proposed Standard | normatively references | |
| STD 13 | References Referenced by | normatively references |