References from draft-hildebrand-webdav-notify
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 78 |
References Referenced by |
informatively references | ||
draft-dusseault-http-patch |
PATCH Method for HTTP
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-webdav-rfc2518bis |
HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-xmpp-core |
Extensible Messaging and Presence Protocol (XMPP): Core
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2518 |
HTTP Extensions for Distributed Authoring -- WEBDAV
References Referenced by |
Proposed Standard | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
RFC 2821 |
Simple Mail Transfer Protocol
References Referenced by |
Proposed Standard | informatively references | |
RFC 3284 |
The VCDIFF Generic Differencing and Compression Data Format
References Referenced by |
Proposed Standard | informatively references | |
RFC 3548 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Informational | normatively references | |
RFC 3667 |
IETF Rights in Contributions
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3668 |
Intellectual Property Rights in IETF Technology
References Referenced by |
Best Current Practice | Possible Reference |