References to RFC 1835
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 4450 |
Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents
References Referenced by |
Informational | normatively references | |
RFC 2967 |
TISDAG - Technical Infrastructure for Swedish Directory Access Gateways
References Referenced by |
Informational | Possible Reference | |
RFC 3650 |
Handle System Overview
References Referenced by |
Informational | Possible Reference | |
RFC 3795 |
Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
References Referenced by |
Informational | Possible Reference | |
RFC 1913 |
Architecture of the Whois++ Index Service
References Referenced by |
Historic | Reference | |
RFC 1914 |
How to Interact with a Whois++ Mesh
References Referenced by |
Historic | Reference | |
RFC 2345 |
Domain Names and Company Name Retrieval
References Referenced by |
Experimental | Reference | |
RFC 2425 |
A MIME Content-Type for Directory Information
References Referenced by |
Proposed Standard | Reference | |
RFC 2957 |
The application/whoispp-query Content-Type
References Referenced by |
Informational | Reference | |
RFC 2958 |
The application/whoispp-response Content-type
References Referenced by |
Informational | Reference | |
RFC 2969 |
Wide Area Directory Deployment - Experiences from TISDAG
References Referenced by |
Informational | Reference | |
RFC 3013 |
Recommended Internet Service Provider Security Services and Procedures
References Referenced by |
Best Current Practice | Reference |