References from draft-maes-lemonade-tcp-challenged-environments
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 78 |
References Referenced by |
Reference | ||
| draft-ietf-lemonade-deployments |
Deployment Considerations for Lemonade-Compliant Mobile Email
References Referenced by |
Best Current Practice | Reference | |
| draft-luotonen-web-proxy-tunneling |
Tunneling TCP based protocols through Web proxy servers
References Referenced by |
Reference | ||
| RFC 2088 |
IMAP4 non-synchronizing literals
References Referenced by |
Proposed Standard | Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Reference | |
| RFC 2442 |
The Batch SMTP Media Type
References Referenced by |
Informational | Reference | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | Reference | |
| RFC 2817 |
Upgrading to TLS Within HTTP/1.1
References Referenced by |
Proposed Standard | Reference | |
| RFC 3205 |
On the use of HTTP as a Substrate
References Referenced by |
Best Current Practice | Reference | |
| RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | Reference |