[http-auth] Last Call: <draft-ietf-httpauth-scram-auth-13.txt> (Salted Challenge Response (SCRAM) HTTP Authentication Mechanism) to Experimental RFC

The IESG <iesg-secretary@ietf.org> Wed, 02 December 2015 16:11 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20151202161101.30230.96879.idtracker@ietfa.amsl.com>
Date: Wed, 02 Dec 2015 08:11:01 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/dYXJ0C20VcI1zM1LK7A4Im2X-BU>
Cc: draft-ietf-httpauth-scram-auth@ietf.org, httpauth-chairs@tools.ietf.org, httpauth-chairs@ietf.org, http-auth@ietf.org, draft-ietf-httpauth-scram-auth-all@tools.ietf.org
Subject: [http-auth] Last Call: <draft-ietf-httpauth-scram-auth-13.txt> (Salted Challenge Response (SCRAM) HTTP Authentication Mechanism) to Experimental RFC
Reply-To: ietf@ietf.org

The IESG has received a request from the Hypertext Transfer Protocol
Authentication WG (httpauth) to consider the following document:
- 'Salted Challenge Response (SCRAM) HTTP Authentication Mechanism'
  <draft-ietf-httpauth-scram-auth-13.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-12-16. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The authentication mechanism most widely deployed and used by
   Internet application protocols is the transmission of clear-text
   passwords over a channel protected by Transport Layer Security (TLS).
   There are some significant security concerns with that mechanism,
   which could be addressed by the use of a challenge response
   authentication mechanism protected by TLS.  Unfortunately, the HTTP
   Digest challenge response mechanism presently on the standards track
   failed widespread deployment, and have had success only in limited
   use.

   This specification describes a family of HTTP authentication
   mechanisms called the Salted Challenge Response Authentication
   Mechanism (SCRAM), which addresses security concerns with HTTP Digest
   and meets the deployability requirements.  When used in combination
   with TLS or an equivalent security layer, a mechanism from this
   family could improve the status-quo for HTTP authentication.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-httpauth-scram-auth/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-httpauth-scram-auth/ballot/


No IPR declarations have been submitted directly on this I-D.

[http-auth] Last Call: <draft-ietf-httpauth-scram… The IESG