--- 1/draft-ietf-regext-login-security-02.txt 2019-08-05 08:13:07.512995046 -0700 +++ 2/draft-ietf-regext-login-security-03.txt 2019-08-05 08:13:07.556996159 -0700 @@ -1,55 +1,55 @@ Network Working Group J. Gould Internet-Draft M. Pozun Intended status: Standards Track VeriSign, Inc. -Expires: December 27, 2019 June 25, 2019 +Expires: February 6, 2020 August 5, 2019 Login Security Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-login-security-02 + draft-ietf-regext-login-security-03 Abstract The Extensible Provisioning Protocol (EPP) includes a client authentication scheme that is based on a user identifier and password. The structure of the password field is defined by an XML Schema data type that specifies minimum and maximum password length values, but there are no other provisions for password management other than changing the password. This document describes an EPP extension that allows longer passwords to be created and adds additional security features to the EPP login command and response. 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 http://datatracker.ietf.org/drafts/current/. + 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 December 27, 2019. + This Internet-Draft will expire on February 6, 2020. Copyright Notice Copyright (c) 2019 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 - (http://trustee.ietf.org/license-info) in effect on the date of + (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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 @@ -66,29 +66,30 @@ 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16 6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 7.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 18 8. Security Considerations . . . . . . . . . . . . . . . . . . . 18 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 10.1. Normative References . . . . . . . . . . . . . . . . . . 19 10.2. Informative References . . . . . . . . . . . . . . . . . 19 - 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 19 + 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 20 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 20 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20 A.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 20 A.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 20 A.6. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 21 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 + A.7. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 21 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 1. Introduction This document describes an Extensible Provisioning Protocol (EPP) extension for enhancing the security of the EPP login command in EPP RFC 5730. The enhancements include supporting longer passwords (or passphrases) than the 16-character maximum and providing a list of security events in the login response. The password (current and new) in EPP RFC 5730 can be overridden by the password included in the extension to extend past the 16-character maximum. The security @@ -110,22 +111,22 @@ XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol. - "loginSec-0.4" is used as an abbreviation for - "urn:ietf:params:xml:ns:epp:loginSec-0.4". The XML namespace prefix + "loginSec-1.0" is used as an abbreviation for + "urn:ietf:params:xml:ns:epp:loginSec-1.0". The XML namespace prefix "loginSec" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. 2. Migrating to Newer Versions of This Extension (Note to RFC Editor: remove this section before publication as an RFC.) Servers which implement this extension SHOULD provide a way for @@ -172,38 +173,42 @@ "certificate": Identifies a client certificate expiry event, where the client certificate will expire at the "exDate" date and time. "cipher": Identifies the use of an insecure or deprecated TLS cipher suite. "tlsProtocol": Identifies the use of an insecure or deprecated TLS protocol. "newPW": The new password does not meet the server password complexity requirements. "stat": Provides a login security statistical warning that MUST - set the "name" of the statistic. + set the "name" attribute to the name of the statistic. "custom": Custom event type that MUST set the "name" attribute with the custom event type name. - "name": Used to define a sub-type or the type name when the "type" - attribute is "custom". + "name": Used to define a sub-type when the "type" attribute is not + "custom" or the full type name when the "type" attribute is + "custom". + "level": Defines the level of the event as either "warning" for a warning event that needs action, or "error" for an error event that requires immediate action. "exDate": Contains the date and time that a "warning" level has or will become an "error" level. At expiry there MAY be an error to connect or MAY be an error to login. An example is an expired - certificate that will result in a error to connect or an expired + certificate that will result in an error to connect or an expired password that may result in a failed login. "value": Identifies the value that resulted in the login security event. An example is the negotiated insecure cipher suite or the negotiated insecure TLS protocol. "duration": Defines the duration that a statistical event is - associated with. + associated with, ending when the login command was received. The + format of the duration is defined by the duration primitive + datatype in [W3C.REC-xmlschema-2-20041028]. "lang": Identifies the language of the free form description if the negotiated language is something other than the default value of "en" (English). Example login security event for a password expiring in a week: contains the predefined value of "[LOGIN-SECURITY]", which is a constant value for the server to use the element for the password. Similarly, the element MUST override the [RFC5730] element only if the contains the predefined value of "[LOGIN-SECURITY]", which is a constant value for the server to use the element for the new password. The "[LOGIN-SECURITY]" pre-defined string MUST be supported by the server for the client to explicitly indicate to the server whether to use element in place of the [RFC5730] element or to use the in place of the [RFC5730] - element. + element. The server MUST NOT allow the client to set the + password to the value "[LOGIN-SECURITY]". 3.3. Dates and Times Date and time attribute values MUST be represented in Universal Coordinated Time (UTC) using the Gregorian calendar. The extended date-time form using upper case "T" and "Z" characters defined in [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time values, as XML Schema does not support truncated date-time forms or lower case "T" and "Z" characters. @@ -258,29 +264,31 @@ command and response to be used in conjunction with [RFC5730]. The EPP command is used to establish a session with an EPP server. This extension overrides the password that is passed with the [RFC5730] or the element as defined in Section 3.2. A element is sent along with the [RFC5730] command and MUST contain at least one of the following child elements: : OPTIONAL client user agent that identifies the - client software, language, and operating system used by the - server to identify functional or security constraints, current - security issues, and potential future functional or security - issues for the client. The element contains - the following child elements: + client application software, technology, and operating system + used by the server to identify functional or security + constraints, current security issues, and potential future + functional or security issues for the client. The + element MUST contain at least one of the + following child elements: : OPTIONAL name of the client application software with version if available, such as the name of the client SDK "EPP SDK 1.0.0". + : OPTIONAL technology used for the client software with version if available, such as "Java 11.0.2". : OPTIONAL client operating system used with version if available, such as "x86_64 Mac OS X 10.11.6". : OPTIONAL plain text password that is case sensitive, has a minimum length of 6 characters, and has a maximum length that is up to server policy. All leading and trailing whitespace is removed, and all internal contiguous whitespace that includes #x9 (tab), #xA (linefeed), #xD (carriage return), and #x20 (space) is replaced with a single #x20 (space). This element @@ -307,28 +315,28 @@ C: [LOGIN-SECURITY] C: C: 1.0 C: en C: C: C: urn:ietf:params:xml:ns:obj1 C: urn:ietf:params:xml:ns:obj2 C: urn:ietf:params:xml:ns:obj3 C: - C: urn:ietf:params:xml:ns:epp:loginSec-0.4 + C: urn:ietf:params:xml:ns:epp:loginSec-1.0 C: C: C: C: C: + C: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> C: C: EPP SDK 1.0.0 C: Java 11.0.2 C: x86_64 Mac OS X 10.11.6 C: C: this is a long password C: C: C: ABC-12345 C: @@ -347,28 +355,28 @@ C: [LOGIN-SECURITY] C: C: 1.0 C: en C: C: C: urn:ietf:params:xml:ns:obj1 C: urn:ietf:params:xml:ns:obj2 C: urn:ietf:params:xml:ns:obj3 C: - C: urn:ietf:params:xml:ns:epp:loginSec-0.4 + C: urn:ietf:params:xml:ns:epp:loginSec-1.0 C: C: C: C: C: + C: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> C: this is a long password C: C: new password that is still long C: C: C: C: ABC-12345 C: C: Example login command that uses the [RFC5730] element to @@ -384,41 +392,42 @@ C: [LOGIN-SECURITY] C: C: 1.0 C: en C: C: C: urn:ietf:params:xml:ns:obj1 C: urn:ietf:params:xml:ns:obj2 C: urn:ietf:params:xml:ns:obj3 C: - C: urn:ietf:params:xml:ns:epp:loginSec-0.4 + C: urn:ietf:params:xml:ns:epp:loginSec-1.0 C: C: C: C: C: + C: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> C: new password that is still long C: C: C: C: ABC-12345 C: C: Upon a completed login command (success or failed), the extension - MUST be included in the response based on the following conditions: + MUST be included in the response based on both of the following + conditions: - Client supports extension: client supports the extension based on - the element of the command. + Client supports extension: The client supports the extension based + on the element of the command. At least one login security event: The server has identified at least one login security event to communicate to the client. The extension to the EPP response uses the element that contains the following child elements: : One or more elements defined in Section 3.1. Example EPP response to a successful login command where the password @@ -426,21 +435,21 @@ S: S: S: S: S: Command completed successfully S: S: S: + S: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> S: S: Password expiring in a week S: S: S: S: @@ -455,21 +464,21 @@ S: S: S: S: S: Authentication error S: S: S: + S: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> S: S: Password has expired S: S: S: New password does not meet complexity requirements @@ -488,21 +497,21 @@ S: S: S: S: S: Command completed successfully S: S: S: + S: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> S: S: Password expiration soon S: S: Extensible Provisioning Protocol v1.0 @@ -677,27 +686,27 @@ 6. IANA Considerations 6.1. XML Namespace This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. The following URI assignment is requested of IANA: Registration request for the loginSec namespace: - URI: urn:ietf:params:xml:ns:epp:loginSec-0.4 + URI: urn:ietf:params:xml:ns:epp:loginSec-1.0 Registrant Contact: IESG XML: None. Namespace URIs do not represent an XML specification. Registration request for the loginSec XML schema: - URI: urn:ietf:params:xml:schema:epp:loginSec-0.4 + URI: urn:ietf:params:xml:schema:epp:loginSec-1.0 Registrant Contact: IESG XML: See the "Formal Syntax" section of this document. 6.2. EPP Extension Registry The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in [RFC7451]. The details of the registration are as follows: Name of Extension: "Login Security Extension for the Extensible @@ -782,33 +791,34 @@ inform clients of connection and login warnings and errors. 9. Acknowledgements The authors wish to thank the following persons for their feedback and suggestions: o Martin Casanova o Scott Hollenbeck o Patrick Mevzek + o Joseph Yee 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, - DOI 10.17487/RFC2119, March 1997, . + DOI 10.17487/RFC2119, March 1997, + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - DOI 10.17487/RFC3688, January 2004, . + DOI 10.17487/RFC3688, January 2004, + . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, July 2016, . @@ -841,51 +851,88 @@ A.2. Change from 01 to 02 1. Changed the XML namespace from urn:ietf:params:xml:ns:loginSec- 0.3 to urn:ietf:params:xml:ns:epp:loginSec-0.3, and changed the XML schema registration from urn:ietf:params:xml:ns:loginSec-0.3 to urn:ietf:params:xml:schema:epp:loginSec-0.3 based on a request from IANA with draft-ietf-regext-allocation-token. A.3. Change from 02 to 03 - Updates based on the review by Patrick Mevzek, that include: + 1. Updates based on the review by Patrick Mevzek, that include: 1. Fix the inconsistent case for newPW, that required a global change in the draft text and an update to the XML schema to "urn:ietf:params:xml:ns:loginSec-0.3". - 2. Changed "contains the following child elements" to "MUST contain - at least one of the following child elements", section "EPP - Command" to ensure that an empty - element is not passed. + 2. Changed "contains the following child elements" to "MUST + contain at least one of the following child elements", + section "EPP Command" to ensure that an empty + element is not passed. 3. Add "The client SHOULD NOT decrease the security of a new - password by decreasing the length of the current password." along - with an example to the "Security Considerations" section. + password by decreasing the length of the current password." + along with an example to the "Security Considerations" + section. A.4. Change from 03 to REGEXT 00 - Changed to regext working group draft by changing draft-gould-regext- - login-security to draft-ietf-regext-login-security. + 1. Changed to regext working group draft by changing draft-gould- + regext-login-security to draft-ietf-regext-login-security. A.5. Change from REGEXT 00 to REGEXT 01 - Changed the element to be structured with the - , , and sub-elements. - This was based on the feedback from Martin Casanova. This resulted - in the need to change the XML namespace from + 1. Changed the element to be structured with + the , , and sub- + elements. This was based on the feedback from Martin Casanova. + + This resulted in the need to change the XML namespace from urn:ietf:params:xml:ns:epp:loginSec-0.3 to urn:ietf:params:xml:ns:epp:loginSec-0.4. A.6. Change from REGEXT 01 to REGEXT 02 - Updated the Implementation Status section from "TBD" to include the - Verisign EPP SDK implementation. + 1. Updated the Implementation Status section from "TBD" to include + the Verisign EPP SDK implementation. + +A.7. Change from REGEXT 02 to REGEXT 03 + + 1. Revised the description of the "duration" attribute to clarify + that it ends when the login command was received and to clarify + the format, based on the feedback from Martin Casanova. + 2. Revised the sentence 'Upon a completed login command (success or + failed), the extension MUST be included in the response based on + the following conditions:' to 'Upon a completed login command + (success or failed), the extension MUST be included in the + response based on both of the following conditions:' based on the + feedback from Patrick Mevzek. + 3. Updates based on the review by Joseph Yee, that include: + + 1. Revised the description of the "name" + attribute read 'Used to define a sub-type when the "type" + attribute is not "custom" or the full type name when the + "type" attribute is "custom"'. The definition of the "stat" + type was updated to 'Provides a login security statistical + warning that MUST set the "name" attribute to the name of the + statistic.' + 2. Added the following sentence 'The server MUST NOT allow the + client to set the password to the value "[LOGIN-SECURITY]".' + to address the corner case where the constant is used as the + password. + 3. Revised the description of the element + to read 'The element MUST contain at + least one of the following child elements:'. + 4. Revised the description of the to match the + child elements that can be passed, by changing "client software" + to "client application software" and change "language" to + "technology". + 5. Changed the XML namespace from + urn:ietf:params:xml:ns:epp:loginSec-0.4 to + urn:ietf:params:xml:ns:epp:loginSec-1.0. Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com