References from draft-stirbu-widex-beep
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| BCP 56 |
References Referenced by |
informatively references | ||
| BCP 78 |
References Referenced by |
informatively references | ||
| draft-ietf-widex-requirements |
Widget Description Exchange Service (WIDEX) Requirements
References Referenced by |
Informational | normatively references | |
| draft-stirbu-widex-framework |
Widget Description Exchange Service (WIDEX) Framework
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2246 |
The TLS Protocol Version 1.0
References Referenced by |
Historic | normatively references | |
| RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax
References Referenced by |
Draft Standard | normatively references | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | informatively references | |
| RFC 3023 |
XML Media Types
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3080 |
The Blocks Extensible Exchange Protocol Core
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3081 |
Mapping the BEEP Core onto TCP
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3205 |
On the use of HTTP as a Substrate
References Referenced by |
Best Current Practice | informatively references |