References to rfc883
This is an experimental product. 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.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 3467 |
Role of the Domain Name System (DNS) Refs Ref'd by |
Informational | normatively references | |
| draft-lewis-domain-names |
RFC Origins of Domain Names Refs Ref'd by |
Informational | informatively references | |
| RFC 6950 |
Architectural Considerations on Application Features in the DNS Refs Ref'd by |
Informational | informatively references | |
| RFC 8244 |
Special-Use Domain Names Problem Statement Refs Ref'd by |
Informational | informatively references | |
| RFC 8324 |
DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look? Refs Ref'd by |
Informational | informatively references | |
| RFC 1010 |
Assigned numbers Refs Ref'd by |
Historic | Possible Reference | |
| RFC 1012 |
Bibliography of Request For Comments 1 through 999 Refs Ref'd by |
Informational | Possible Reference | |
| RFC 1033 |
Domain Administrators Operations Guide Refs Ref'd by |
Unknown | Possible Reference | |
| RFC 1034 |
Domain names - concepts and facilities Refs Ref'd by |
Internet Standard | Possible Reference | Possible Downref |
| RFC 1035 |
Domain names - implementation and specification Refs Ref'd by |
Internet Standard | Possible Reference | Possible Downref |
| RFC 1099 |
Request for Comments Summary: RFC Numbers 1000-1099 Refs Ref'd by |
Informational | Possible Reference | |
| RFC 1175 |
FYI on where to start: A bibliography of internetworking information Refs Ref'd by |
Informational | Possible Reference | |
| RFC 881 |
Domain names plan and schedule Refs Ref'd by |
Unknown | Possible Reference | |
| RFC 882 |
Domain names: Concepts and facilities Refs Ref'd by |
Unknown | Possible Reference | |
| RFC 955 |
Towards a transport service for transaction processing applications Refs Ref'd by |
Unknown | Possible Reference | |
| RFC 960 |
Assigned numbers Refs Ref'd by |
Historic | Possible Reference | |
| RFC 980 |
Protocol document order information Refs Ref'd by |
Unknown | Possible Reference | |
| RFC 990 |
Assigned numbers Refs Ref'd by |
Historic | Possible Reference | |
| RFC 999 |
Requests For Comments summary notes: 900-999 Refs Ref'd by |
Unknown | Possible Reference | |
| RFC 1001 |
Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods Refs Ref'd by |
Internet Standard | Reference | Possible Downref |
| RFC 1002 |
Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications Refs Ref'd by |
Internet Standard | Reference | Possible Downref |
| RFC 1048 |
BOOTP vendor information extensions Refs Ref'd by |
Unknown | Reference | |
| RFC 1101 |
DNS encoding of network names and other types Refs Ref'd by |
Unknown | Reference | |
| RFC 897 |
Domain name system implementation schedule Refs Ref'd by |
Unknown | Reference | |
| RFC 915 |
Network mail path service Refs Ref'd by |
Unknown | Reference | |
| RFC 920 |
Domain requirements Refs Ref'd by |
Unknown | Reference | |
| RFC 921 |
Domain name system implementation schedule - revised Refs Ref'd by |
Unknown | Reference | |
| RFC 973 |
Domain system changes and observations Refs Ref'd by |
Unknown | Reference |