--- 1/draft-ietf-regext-login-security-08.txt 2020-02-24 06:13:16.110542229 -0800 +++ 2/draft-ietf-regext-login-security-09.txt 2020-02-24 06:13:16.170543764 -0800 @@ -1,18 +1,18 @@ Network Working Group J. Gould Internet-Draft M. Pozun Intended status: Standards Track VeriSign, Inc. -Expires: August 2, 2020 January 30, 2020 +Expires: August 27, 2020 February 24, 2020 Login Security Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-login-security-08 + draft-ietf-regext-login-security-09 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 @@ -26,42 +26,42 @@ 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 August 2, 2020. + This Internet-Draft will expire on August 27, 2020. 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. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 - 2. Migrating to Newer Versions of This Extension . . . . . . . . 3 + 2. Migrating to Newer Versions of This Extension . . . . . . . . 4 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Event . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. "[LOGIN-SECURITY]" Password . . . . . . . . . . . . . . . 6 3.3. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 4.1. EPP Command . . . . . . . . . . . . . . . . . . . 7 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1. Login Security Extension Schema . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 @@ -80,21 +80,22 @@ A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 22 A.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 22 A.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 22 A.6. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 22 A.7. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 22 A.8. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 23 A.9. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 23 A.10. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 24 A.11. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 24 A.12. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 24 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 + A.13. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 26 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 1. Introduction This document describes an Extensible Provisioning Protocol (EPP) extension for enhancing the security of the EPP login command in EPP [RFC5730]. 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 [RFC5730] can be overridden by the password included in the extension to extend past the 16-character maximum. The security @@ -355,26 +356,27 @@ "[LOGIN-SECURITY]" value. : OPTIONAL plain text new 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 MUST only be set if the [RFC5730] element is set to the "[LOGIN-SECURITY]" value. - It is recommended that the plain text password in the + It is RECOMMENDED that the plain text password in the and elements use printable ASCII characters #x20 (space) - #x7E (~), with high entropy, such as 128 bits. If non- ASCII characters are supported with the plain text password, then use - a standard for passwords with international characters, such as the - OpaqueString PRECIS profile in [RFC8265]. + a standard for passwords with international characters; the + OpaqueString PRECIS profile in [RFC8265] is recommended in the + absence of other considerations. Example login command that uses the element instead of the [RFC5730] element to establish the session and includes the element: C: C: C: C: C: ClientX @@ -1165,20 +1167,33 @@ security events to unauthenticated users needs to take into account the security/privacy issues of returning information to potential attackers." to the end of the last paragraph. 14. In section 8, change "minimum length beyond 6 characters" to "minimum length greater than 6 characters". 15. In section 8, add the sentence "The user agent information represents the client system of a system-to-system interface, so the user agent information MUST NOT provide any ability to track individual users or classes of users." +A.13. Change from REGEXT 08 to REGEXT 09 + + 1. Based on feedback from Barry Leiba in responding to Benjamin + Kaduk's discuss item, changed "It is recommended that the plain + text..." to "It is RECOMMENDED that the plain text..." and "If + non-ASCII characters are supported with the plain text password, + then use a standard for passwords with international characters, + such as the OpaqueString PRECIS profile in [RFC8265]." to "If + non-ASCII characters are supported with the plain text password, + then use a standard for passwords with international characters; + the OpaqueString PRECIS profile in [RFC8265] is recommended in + the absence of other considerations." + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisign.com