[rfc-dist] RFC 4959 on IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Sep 21 15:21:03 PDT 2007


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4959

        Title:      IMAP Extension for Simple Authentication 
                    and Security Layer (SASL) Initial Client 
                    Response 
        Author:     R. Siemborski, A. Gulbrandsen
        Status:     Standards Track
        Date:       September 2007
        Mailbox:    robsiemb at google.com, 
                    arnt at oryx.com
        Pages:      7
        Characters: 12284
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-siemborski-imap-sasl-initial-response-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4959.txt

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.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list