References to RFC 3081
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 3620 |
The TUNNEL Profile
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3983 |
Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4324 |
Calendar Access Protocol (CAP)
References Referenced by |
Experimental | normatively references | |
| RFC 4744 |
Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)
References Referenced by |
Historic | normatively references | |
| RFC 3760 |
Securely Available Credentials (SACRED) - Credential Server Framework
References Referenced by |
Informational | informatively references | |
| RFC 5573 |
Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP)
References Referenced by |
Experimental | informatively references | |
| RFC 3795 |
Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
References Referenced by |
Informational | Possible Reference | |
| RFC 3080 |
The Blocks Extensible Exchange Protocol Core
References Referenced by |
Proposed Standard | Reference | |
| RFC 3117 |
On the Design of Application Protocols
References Referenced by |
Informational | Reference | |
| RFC 3195 |
Reliable Delivery for syslog
References Referenced by |
Proposed Standard | Reference |