RFC4959 SASL-IR #45

Closed
opened 2023-12-29 17:31:39 +00:00 by quentin · 1 comment
Owner

To date, the Internet Message Access Protocol (IMAP) has used a
Simple Authentication and Security Layer (SASL) profile which always
required at least one complete round trip for an authentication, as
it did not support an initial client response argument. This
additional round trip at the beginning of the session is undesirable,
especially when round-trip costs are high.

This document defines an extension to IMAP which allows clients and
servers to avoid this round trip by allowing an initial client
response argument to the IMAP AUTHENTICATE command.

https://www.rfc-editor.org/rfc/rfc4959.html

imap_codec support: maybe
https://docs.rs/imap-types/latest/imap_types/response/enum.Capability.html#variant.SaslIr

maybe incompatible with the way we encrypt data...

> To date, the Internet Message Access Protocol (IMAP) has used a Simple Authentication and Security Layer (SASL) profile which always required at least one complete round trip for an authentication, as it did not support an initial client response argument. This additional round trip at the beginning of the session is undesirable, especially when round-trip costs are high. > This document defines an extension to IMAP which allows clients and servers to avoid this round trip by allowing an initial client response argument to the IMAP AUTHENTICATE command. https://www.rfc-editor.org/rfc/rfc4959.html imap_codec support: maybe https://docs.rs/imap-types/latest/imap_types/response/enum.Capability.html#variant.SaslIr maybe incompatible with the way we encrypt data...
quentin added the
cat
feature
prio
low
blocked
vendor
labels 2023-12-29 17:31:39 +00:00
quentin added this to the IMAP4REV2 project 2023-12-29 17:31:39 +00:00
quentin removed the
blocked
vendor
label 2023-12-29 17:39:01 +00:00
quentin added the
blocked
design
label 2023-12-29 17:59:49 +00:00
Author
Owner

closing for now.

closing for now.
Sign in to join this conversation.
No description provided.