References to RFC 2732
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 3510 |
Internet Printing Protocol/1.1: IPP URL Scheme
References Referenced by |
Proposed Standard | normatively references | |
RFC 3720 |
Internet Small Computer Systems Interface (iSCSI)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3875 |
The Common Gateway Interface (CGI) Version 1.1
References Referenced by |
Informational | normatively references | |
RFC 3981 |
IRIS: The Internet Registry Information Service (IRIS) Core Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 4173 |
Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) Protocol
References Referenced by |
Proposed Standard | normatively references | |
draft-schinazi-httpbis-link-local-uri-bcp |
Best Practices for Link-Local Connectivity in URI-Based Protocols
References Referenced by |
informatively references | ||
RFC 3419 |
Textual Conventions for Transport Addresses
References Referenced by |
Proposed Standard | informatively references | |
RFC 3721 |
Internet Small Computer Systems Interface (iSCSI) Naming and Discovery
References Referenced by |
Informational | informatively references | |
RFC 3722 |
String Profile for Internet Small Computer Systems Interface (iSCSI) Names
References Referenced by |
Proposed Standard | informatively references | |
RFC 3795 |
Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
References Referenced by |
Informational | informatively references | |
RFC 3931 |
Layer Two Tunneling Protocol - Version 3 (L2TPv3)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | informatively references | |
RFC 4007 |
IPv6 Scoped Address Architecture
References Referenced by |
Proposed Standard | informatively references | |
RFC 4038 |
Application Aspects of IPv6 Transition
References Referenced by |
Informational | informatively references | |
RFC 4516 |
Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator
References Referenced by |
Proposed Standard | informatively references | |
RFC 3236 |
The 'application/xhtml+xml' Media Type
References Referenced by |
Informational | Possible Reference | |
RFC 3794 |
Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents
References Referenced by |
Informational | Possible Reference | |
RFC 3075 |
XML-Signature Syntax and Processing
References Referenced by |
Proposed Standard | Reference | |
RFC 3111 |
Service Location Protocol Modifications for IPv6
References Referenced by |
Proposed Standard | Reference | |
RFC 3266 |
Support for IPv6 in Session Description Protocol (SDP)
References Referenced by |
Proposed Standard | Reference | |
RFC 3275 |
(Extensible Markup Language) XML-Signature Syntax and Processing
References Referenced by |
Draft Standard | Reference | |
RFC 3529 |
Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)
References Referenced by |
Experimental | Reference | |
RFC 3617 |
Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP)
References Referenced by |
Informational | Reference |