SCRAM-SHA-512 and SCRAM-SHA-512-PLUS Simple Authentication and Security Layer (SASL) Mechanisms
draft-melnikov-scram-sha-512-01
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Alexey Melnikov
|
|
Last updated |
|
2020-11-18
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group A. Melnikov, Ed.
Internet-Draft Isode Ltd
Intended status: Standards Track November 18, 2020
Expires: May 22, 2021
SCRAM-SHA-512 and SCRAM-SHA-512-PLUS Simple Authentication and Security
Layer (SASL) Mechanisms
draft-melnikov-scram-sha-512-01
Abstract
This document registers the Simple Authentication and Security Layer
(SASL) mechanisms SCRAM-SHA-512 and SCRAM-SHA-512-PLUS.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 22, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Melnikov Expires May 22, 2021 [Page 1]
Internet-Draft SASL SCRAM-SHA-512/SCRAM-SHA-512-PLUS November 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Key Word Definitions . . . . . . . . . . . . . . . . . . . . 2
3. SCRAM-SHA-512 and SCRAM-SHA-512-PLUS . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
This document registers the SASL [RFC4422] mechanisms SCRAM-SHA-512
and SCRAM-SHA-512-PLUS. SHA-512 has stronger security properties
than SHA-1, and it is expected that SCRAM mechanisms based on it will
have greater predicted longevity than the SCRAM mechanisms based on
SHA-1.
2. Key Word Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
3. SCRAM-SHA-512 and SCRAM-SHA-512-PLUS
The SCRAM-SHA-512 and SCRAM-SHA-512-PLUS SASL mechanisms are defined
in the same way that SCRAM-SHA-1 and SCRAM-SHA-1-PLUS are defined in
[RFC5802], except that the hash function for HMAC() and H() uses
SHA-512 instead of SHA-1 [RFC6234].
For the SCRAM-SHA-512 and SCRAM-SHA-512-PLUS SASL mechanisms, the
hash iteration-count announced by a server SHOULD be at least 10000.
The GSS-API mechanism OID for SCRAM-SHA-512 is 1.3.6.1.5.5.<TBD> (see
Section 5).
This is a simple example of a SCRAM-SHA-512 authentication exchange
when the client doesn't support channel bindings. The username
'user' and password 'pencil' are being used.
[[TBD: Add an example]]
Melnikov Expires May 22, 2021 [Page 2]
Internet-Draft SASL SCRAM-SHA-512/SCRAM-SHA-512-PLUS November 2020
4. Security Considerations
The security considerations from [RFC5802] still apply.
To be secure, either SCRAM-SHA-512-PLUS and SCRAM-SHA-1-PLUS MUST be
used over a TLS channel that has had the session hash extension
[RFC7627] negotiated, or session resumption MUST NOT have been used.
When using SCRAM over TLS 1.2 [RFC5246], the "tls-unique" channel
binding is still the default channel binding to use (see Section 6.1
of [RFC5802]), assuming the above conditions are satisfied. As "tls-
unique" channel binding is not defined for TLS 1.3 [RFC8446], when
using SCRAM over TLS 1.3, the "tls-exporter" channel binding
Show full document text