References to draft-ietf-mhsds-routdirectory
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 3795
As rfc1801 |
Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
References Referenced by |
Informational | Possible Reference | |
RFC 1802
As rfc1801 |
Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing
References Referenced by |
Informational | Reference | |
RFC 1836
As rfc1801 |
Representing the O/R Address hierarchy in the X.500 Directory Information Tree
References Referenced by |
Experimental | Reference | |
RFC 1837
As rfc1801 |
Representing Tables and Subtrees in the X.500 Directory
References Referenced by |
Experimental | Reference | |
RFC 1838
As rfc1801 |
Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses
References Referenced by |
Experimental | Reference | |
RFC 2116
As rfc1801 |
X.500 Implementations Catalog-96
References Referenced by |
Informational | Reference | |
RFC 2164
As rfc1801 |
Use of an X.500/LDAP directory to support MIXER address mapping
References Referenced by |
Proposed Standard | Reference | |
RFC 2293
As rfc1801 |
Representing Tables and Subtrees in the X.500 Directory
References Referenced by |
Proposed Standard | Reference | |
RFC 2294
As rfc1801 |
Representing the O/R Address hierarchy in the X.500 Directory Information Tree
References Referenced by |
Proposed Standard | Reference |