References to rfc4395

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
draft-hartke-core-apps
As bcp35
CoRE Applications
Refs Ref'd by
normatively references
draft-op3ft-leaptofrogans-uri-scheme
As bcp35
The 'leaptofrogans' URI Scheme
Refs Ref'd by
Informational normatively references
draft-thomson-http-hx-uri
As bcp35
Identifying HTTP Exchanges with URIs
Refs Ref'd by
normatively references
RFC 4452 The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces
Refs Ref'd by
Informational normatively references
RFC 5050 Bundle Protocol Specification
Refs Ref'd by
Experimental normatively references
RFC 5724 URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS)
Refs Ref'd by
Proposed Standard normatively references
RFC 5724
As bcp35
URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS)
Refs Ref'd by
Proposed Standard normatively references
RFC 5781 The rsync URI Scheme
Refs Ref'd by
Informational normatively references
RFC 5781
As bcp35
The rsync URI Scheme
Refs Ref'd by
Informational normatively references
RFC 6167 URI Scheme for Java(tm) Message Service 1.0
Refs Ref'd by
Informational normatively references
RFC 6167
As bcp35
URI Scheme for Java(tm) Message Service 1.0
Refs Ref'd by
Informational normatively references
RFC 6196 Moving mailserver: URI Scheme to Historic
Refs Ref'd by
Proposed Standard normatively references
RFC 6196
As bcp35
Moving mailserver: URI Scheme to Historic
Refs Ref'd by
Proposed Standard normatively references
RFC 6920 Naming Things with Hashes
Refs Ref'd by
Proposed Standard normatively references
RFC 6920
As bcp35
Naming Things with Hashes
Refs Ref'd by
Proposed Standard normatively references
RFC 6940 REsource LOcation And Discovery (RELOAD) Base Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 6940
As bcp35
REsource LOcation And Discovery (RELOAD) Base Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 7046 A Common API for Transparent Hybrid Multicast
Refs Ref'd by
Experimental normatively references
RFC 7046
As bcp35
A Common API for Transparent Hybrid Multicast
Refs Ref'd by
Experimental normatively references
RFC 7239 Forwarded HTTP Extension
Refs Ref'd by
Proposed Standard normatively references
RFC 7239
As bcp35
Forwarded HTTP Extension
Refs Ref'd by
Proposed Standard normatively references
RFC 7252 The Constrained Application Protocol (CoAP)
Refs Ref'd by
Proposed Standard normatively references
RFC 7252
As bcp35
The Constrained Application Protocol (CoAP)
Refs Ref'd by
Proposed Standard normatively references
RFC 7826 Real-Time Streaming Protocol Version 2.0
Refs Ref'd by
Proposed Standard normatively references
RFC 7826
As bcp35
Real-Time Streaming Protocol Version 2.0
Refs Ref'd by
Proposed Standard normatively references
RFC 8252
As bcp35
OAuth 2.0 for Native Apps
Refs Ref'd by
Best Current Practice normatively references
RFC 8323
As bcp35
CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
Refs Ref'd by
Proposed Standard normatively references
draft-hallambaker-mesh-udf
As bcp35
Mathematical Mesh Part II: Uniform Data Fingerprint.
Refs Ref'd by
informatively references
draft-ietf-httpbis-bcp56bis
As bcp35
Building Protocols with HTTP
Refs Ref'd by
Best Current Practice informatively references
draft-ietf-httpbis-semantics
As bcp35
HTTP Semantics
Refs Ref'd by
informatively references
RFC 3656
As bcp35
The Mailbox Update (MUPDATE) Distributed Mailbox Database Protocol
Refs Ref'd by
Experimental informatively references
RFC 3887
As bcp35
Message Tracking Query Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 3986
As bcp35
Uniform Resource Identifier (URI): Generic Syntax
Refs Ref'd by
Internet Standard informatively references
RFC 4088
As bcp35
Uniform Resource Identifier (URI) Scheme for the Simple Network Management Protocol (SNMP)
Refs Ref'd by
Proposed Standard informatively references
RFC 4501
As bcp35
Domain Name System Uniform Resource Identifiers
Refs Ref'd by
Proposed Standard informatively references
RFC 4622 Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)
Refs Ref'd by
Proposed Standard informatively references
RFC 5092 IMAP URL Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 5122 Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)
Refs Ref'd by
Proposed Standard informatively references
RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice informatively references
RFC 5456 IAX: Inter-Asterisk eXchange Version 2
Refs Ref'd by
Informational informatively references
RFC 5456
As bcp35
IAX: Inter-Asterisk eXchange Version 2
Refs Ref'd by
Informational informatively references
RFC 5538 The 'news' and 'nntp' URI Schemes
Refs Ref'd by
Proposed Standard informatively references
RFC 5538
As bcp35
The 'news' and 'nntp' URI Schemes
Refs Ref'd by
Proposed Standard informatively references
RFC 5870 A Uniform Resource Identifier for Geographic Locations ('geo' URI)
Refs Ref'd by
Proposed Standard informatively references
RFC 5870
As bcp35
A Uniform Resource Identifier for Geographic Locations ('geo' URI)
Refs Ref'd by
Proposed Standard informatively references
RFC 6260 Compressed Bundle Header Encoding (CBHE)
Refs Ref'd by
Experimental informatively references
RFC 6260
As bcp35
Compressed Bundle Header Encoding (CBHE)
Refs Ref'd by
Experimental informatively references
RFC 6270 The 'tn3270' URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 6270
As bcp35
The 'tn3270' URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 6648 Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
Refs Ref'd by
Best Current Practice informatively references
RFC 6648
As bcp35
Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
Refs Ref'd by
Best Current Practice informatively references
RFC 6694 The "about" URI Scheme
Refs Ref'd by
Informational informatively references
RFC 6694
As bcp35
The "about" URI Scheme
Refs Ref'd by
Informational informatively references
RFC 6787 Media Resource Control Protocol Version 2 (MRCPv2)
Refs Ref'd by
Proposed Standard informatively references
RFC 6787
As bcp35
Media Resource Control Protocol Version 2 (MRCPv2)
Refs Ref'd by
Proposed Standard informatively references
RFC 7064 URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 7064
As bcp35
URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 7065 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
Refs Ref'd by
Proposed Standard informatively references
RFC 7065
As bcp35
Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
Refs Ref'd by
Proposed Standard informatively references
RFC 7320 URI Design and Ownership
Refs Ref'd by
Best Current Practice informatively references
RFC 7472
As bcp35
Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 7512 The PKCS #11 URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 7512
As bcp35
The PKCS #11 URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 7565 The 'acct' URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 7565
As bcp35
The 'acct' URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 7595 Guidelines and Registration Procedures for URI Schemes
Refs Ref'd by
Best Current Practice informatively references
RFC 7612
As bcp35
Lightweight Directory Access Protocol (LDAP): Schema for Printer Services
Refs Ref'd by
Informational informatively references
RFC 7869
As bcp35
The "vnc" URI Scheme
Refs Ref'd by
Informational informatively references
RFC 8089
As bcp35
The "file" URI Scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice informatively references
RFC 8126
As bcp35
Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice informatively references
RFC 2718
As bcp35
Guidelines for new URL Schemes
Refs Ref'd by
Informational Reference
RFC 3205
As bcp35
On the use of HTTP as a Substrate
Refs Ref'd by
Best Current Practice Reference
RFC 3305
As bcp35
Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations
Refs Ref'd by
Informational Reference
RFC 3368
As bcp35
The 'go' URI Scheme for the Common Name Resolution Protocol
Refs Ref'd by
Proposed Standard Reference
RFC 3405
As bcp35
Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures
Refs Ref'd by
Best Current Practice Reference
RFC 3617
As bcp35
Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP)
Refs Ref'd by
Informational Reference