idnits 2.17.1 draft-hansen-scram-sha256-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 85: '... SHOULD announce a hash iteration-co...' RFC 2119 keyword, line 122: '... SHOULD announce...' RFC 2119 keyword, line 123: '...ciated OID: IANA SHOULD assign a GSS-A...' RFC 2119 keyword, line 133: '...s of this family MUST be explicitly re...' RFC 2119 keyword, line 134: '... the "IETF Review" [RFC5226] registration procedure. Reviews MUST...' (1 more instance...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 24, 2014) is 3536 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 218 -- Looks like a reference, but probably isn't: '2' on line 220 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Kitten T. Hansen 3 Internet-Draft AT&T Laboratories 4 Updates: 5802 (if approved) July 24, 2014 5 Intended status: Informational 6 Expires: January 25, 2015 8 SCRAM-SHA-256 and SCRAM-SHA-256-PLUS SASL Mechanisms 9 draft-hansen-scram-sha256-01 11 Abstract 13 This document registers the SASL mechanisms SCRAM-SHA-256 and SCRAM- 14 SHA-256-PLUS. It also updates RFC 5802 in minor ways. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 25, 2015. 33 Copyright Notice 35 Copyright (c) 2014 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. SCRAM-SHA-256 and SCRAM-SHA-256-PLUS . . . . . . . . . . . . 2 52 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 55 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 56 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 57 6.2. Informative References . . . . . . . . . . . . . . . . . 5 58 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 61 1. Introduction 63 This document registers the SASL mechanisms SCRAM-SHA-256 and SCRAM- 64 SHA-256-PLUS. 66 The registration form for the SCRAM family of algorithms is also 67 updated. 69 Note: this paragraph may be removed before publication. 70 This document was written because [RFC5802] requires that new SASL 71 mechanisms in the SCRAM family be subject to IETF review. This 72 document is being discussed in the KITTEN working group (see the 73 kitten@ietf.org [1] mailing list). It was pursued further because of 74 a desire for its use within a document being discussed in the HTTP- 75 AUTH working group (see the httpauth@ietf.org [2] mailing list). 77 2. SCRAM-SHA-256 and SCRAM-SHA-256-PLUS 79 The SCRAM-SHA-256 and SCRAM-SHA-256-PLUS SASL mechanism are defined 80 in the same way that SCRAM-SHA-1 and SCRAM-SHA-1-PLUS are defined in 81 [RFC5802], except that the hash function for HMAC() and H() uses 82 SHA-256 instead of SHA-1 [RFC6234]. 84 For the SCRAM-SHA-256/SCRAM-SHA-256-PLUS SASL mechanisms, servers 85 SHOULD announce a hash iteration-count of at least 4096. 86 !!!!!!!!!!!!!!!! Note that the appropriate value to specify here 87 needs to be discussed further. !!!!!!!!!!!!!!!! 89 The GSS-API mechanism OID for SCRAM-SHA-256 is TBD1 (see Section 4). 91 This is a simple example of a SCRAM-SHA-256 authentication exchange 92 when the client doesn't support channel bindings (username 'user' and 93 password 'pencil' are used): 95 C: n,,n=user,r=rOprNGfwEbeRWgbNEkqO 96 S: r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0, 97 s=W22ZaJ0SNY7soEsUEjb6gQ==,i=4096 99 C: c=biws,r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0, 100 p=dHzbZapWIk4jUhN+Ute9ytag9zjfMHgsqmmiz7AndVQ= 102 S: v=6rriTRBi23WpRR/wtup+mMhUZUn/dB5nLTJRsjl95G4= 104 3. Security Considerations 106 The security considerations from [RFC5802] still apply. 108 4. IANA Considerations 110 The IANA registry for the SCRAM family of SASL mechanisms is updated 111 as follows. This revised form adds two new fields: Minimum 112 iteration-count and Associated OID. In addition, the email address 113 for reviews has been updated. 115 To: iana@iana.org 116 Subject: Registration of a new SASL family SCRAM 118 SASL mechanism name (or prefix for the family): SCRAM-* 119 Security considerations: Section 7 of [RFC5802] 120 Published specification (optional, recommended): RFCXXXX 121 Minimum iteration-count: The minimum iteration-count that servers 122 SHOULD announce 123 Associated OID: IANA SHOULD assign a GSS-API mechanism OID for 124 this mechanism from the iso.org.dod.internet.security.mechanisms 125 prefix (see the "SMI Security for Mechanism Codes" registry). 126 Only one OID needs to be assigned for a SCRAM-* and SCRAM-*-PLUS 127 pair. The same OID should be assigned to both entries in the 128 registry. 129 Person & email address to contact for further information: IETF 130 KITTEN WG kitten@ietf.org 131 Intended usage: COMMON 132 Owner/Change controller: IESG iesg@ietf.org 133 Note: Members of this family MUST be explicitly registered using 134 the "IETF Review" [RFC5226] registration procedure. Reviews MUST 135 be requested on the KITTEN mailing list kitten@ietf.org (or a 136 successor designated by the responsible Security AD). 137 !!!!!!!!!!!!!!!! Can we change this to expert review? 138 !!!!!!!!!!!!!!!! 140 Note to future SCRAM-mechanism designers: each new SCRAM-SASL 141 mechanism MUST be explicitly registered with IANA and MUST comply 142 with SCRAM-mechanism naming convention defined in Section 4 of 143 [RFC5802]. 145 The following values are to be added to the existing registries for 146 SASL SCRAM-SHA-1 and SCRAM-SHA-1-PLUS: 148 Minimum iteration-count: 4096 149 OID: 1.3.6.1.5.5.14 (from [RFC5802]) 151 The following new SASL SCRAM mechanisms are added: 153 IANA has added the following entries to the SASL Mechanism 154 registry established by [RFC4422]: 156 To: iana@iana.org 157 Subject: Registration of a new SASL mechanism SCRAM-SHA-256 159 SASL mechanism name (or prefix for the family): SCRAM-SHA-256 160 Security considerations: Section Section 3 of RFCXXXX 161 Published specification (optional, recommended): RFCXXXX 162 Minimum iteration-count: 4096 163 OID: TBD1 164 Person & email address to contact for further information: IETF 165 KITTEN WG kitten@ietf.org 166 Intended usage: COMMON 167 Owner/Change controller: IESG iesg@ietf.org 168 Note: 170 To: iana@iana.org 171 Subject: Registration of a new SASL mechanism SCRAM-SHA-256-PLUS 173 SASL mechanism name (or prefix for the family): SCRAM-SHA-256-PLUS 174 Security considerations: Section Section 3 of RFCXXXX 175 Published specification (optional, recommended): RFCXXXX 176 Minimum iteration-count: 4096 177 OID: TBD1 178 Person & email address to contact for further information: IETF 179 KITTEN WG kitten@ietf.org 180 Intended usage: COMMON 181 Owner/Change controller: IESG iesg@ietf.org 182 Note: 184 [This note may be removed on publication.] IANA needs to assign the 185 GSS-API mechanism OID TBD1 listed above from the 186 iso.org.dod.internet.security.mechanisms prefix (see the "SMI 187 Security for Mechanism Codes" registry). 189 5. Acknowledgements 191 This document benefited from discussions on the KITTEN WG mailing 192 list. The author would like to specially thank Russ Albery, Dave 193 Cridland, Shawn Emery, Simon Josefsson, and Alexey Melnikov for their 194 comments on this topic. 196 6. References 198 6.1. Normative References 200 [RFC5802] Newman, C., Menon-Sen, A., Melnikov, A., and N. Williams, 201 "Salted Challenge Response Authentication Mechanism 202 (SCRAM) SASL and GSS-API Mechanisms", RFC 5802, July 2010. 204 [RFC6234] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms 205 (SHA and SHA-based HMAC and HKDF)", RFC 6234, May 2011. 207 6.2. Informative References 209 [RFC4422] Melnikov, A. and K. Zeilenga, "Simple Authentication and 210 Security Layer (SASL)", RFC 4422, June 2006. 212 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 213 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 214 May 2008. 216 6.3. URIs 218 [1] mailto:kitten@ietf.org 220 [2] mailto:httpauth@ietf.org 222 Author's Address 224 Tony Hansen 225 AT&T Laboratories 226 200 Laurel Ave. South 227 Middletown, NJ 07748 228 USA 230 Email: tony+scramsha256@maillennium.att.com