References to BCP 56
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-gupta-httpbis-per-resource-events
As rfc9205 |
Per Resource Events
References Referenced by |
informatively references | ||
draft-ietf-alto-new-transport
As rfc9205 |
The ALTO Transport Information Publication Service
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-teep-otrp-over-http
As rfc9205 |
HTTP Transport for Trusted Execution Environment Provisioning: Agent Initiated Communication
References Referenced by |
Proposed Standard | informatively references | |
draft-lehmann-idmefv2-https-transport |
Transport of Incident Detection Message Exchange Format version 2 (IDMEFv2) Messages over HTTPS
References Referenced by |
informatively references | ||
RFC 3983 |
Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)
References Referenced by |
Proposed Standard | informatively references | |
RFC 5383 |
Deployment Considerations for Lemonade-Compliant Mobile Email
References Referenced by |
Best Current Practice | informatively references | |
RFC 4743 |
Using NETCONF over the Simple Object Access Protocol (SOAP)
References Referenced by |
Historic | Possible Reference | |
RFC 6046 |
Transport of Real-time Inter-network Defense (RID) Messages
References Referenced by |
Informational | Possible Reference | |
RFC 6546 |
Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 3234 |
Middleboxes: Taxonomy and Issues
References Referenced by |
Informational | Reference |