…ndations for use of TLS by Electronic Mail Access Protocols", Work in Progress, draft-moore- email-tls-00, October 2013. [MTA-STS] Margolis, D., Risher, M., Ramakrishnan, B., Brotman, A., and J. Jones, "SMTP MTA Strict Transport Security (MTA-STS)", Work in Progress, draft-ietf-u…
…ndations for use of TLS by Electronic Mail Access Protocols", Work in Progress, draft-moore- email-tls-00 , October 2013. [ MTA-STS ] Margolis, D., Risher, M., Ramakrishnan, B., Brotman, A., and J. Jones, "SMTP MTA Strict Transport Security (MTA-STS)", Work in Progress, draft-iet…
…) Errata IPR Obsoletes RFC 5246 RFC 5077 RFC 6961 Updates RFC 5705 RFC 6066 Was draft-ietf-tls-tls13 tls WG Author Eric Rescorla 2020-03-07 RFC stream Internet Engineering Task Force (IETF) Formats txt html pdf htmlized w/errata bibtex Additional resources Mailing list discussion…
…2818 RFC 7694 RFC 7232 RFC 7615 RFC 7230 RFC 7235 RFC 7231 Updates RFC 3864 Was draft-ietf-httpbis-semantics httpbis WG Authors Roy T. Fielding Mark Nottingham Julian Reschke 2022-11-01 RFC stream Internet Engineering Task Force (IETF) Formats txt html xml pdf htmlized w/errata b…
…Note This note is to be removed before publishing as an RFC. Discussion of this draft takes place on the HTTP working group mailing list (ietf-http-wg@w3.org), which is archived at Working Group information can be found at ; source code and issues list for this draft can be found…
…dary string incorrectly. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges", which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media …
…y string incorrectly. 3. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges", which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media …
…dary string incorrectly. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges" which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media t…
…dary string incorrectly. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges" which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media t…
…dary string incorrectly. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges" which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media t…
…dary string incorrectly. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges" which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media t…
…dary string incorrectly. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges" which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media t…
…dary string incorrectly. A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of "multipart/x-byteranges" which is almost (but not quite) compatible with this type. Despite the name, the "multipart/byteranges" media t…
…ed Standard June 2022 View errata Report errata Obsoletes RFC 8740 RFC 7540 Was draft-ietf-httpbis-http2bis httpbis WG Select version 00 01 02 03 04 05 06 07 RFC 9113 Compare versions Authors Martin Thomson Cory Benfield Email authors RFC stream Other formats txt html xml pdf w/e…
…ammell "Manageability of the QUIC Transport Protocol" Work in Progress Internet-Draft, draft-ietf-quic-manageability-11 21 April 2021 [RANDOM] Eastlake 3rd, D. Schiller, J. , and S. Crocker "Randomness Requirements for Security" BCP 106 RFC 4086 DOI 10.17487/RFC4086 June 2005 [RF…