--- 1/draft-ietf-regext-login-security-04.txt 2019-10-29 13:13:09.025026872 -0700 +++ 2/draft-ietf-regext-login-security-05.txt 2019-10-29 13:13:09.069027987 -0700 @@ -1,18 +1,18 @@ Network Working Group J. Gould Internet-Draft M. Pozun Intended status: Standards Track VeriSign, Inc. -Expires: April 2, 2020 September 30, 2019 +Expires: May 1, 2020 October 29, 2019 Login Security Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-login-security-04 + draft-ietf-regext-login-security-05 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,21 +26,21 @@ 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 April 2, 2020. + This Internet-Draft will expire on May 1, 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -76,20 +76,21 @@ 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 A.7. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 21 A.8. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 22 + A.9. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 22 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 @@ -99,44 +100,43 @@ security statistical warning, and a custom event. The attributes supported by the security events include identifying the event type or sub-type, indicating the security level of warning or error, a future or past-due expiration date, the value that resulted in the event, the duration of the statistical event, and a free-form description with an optional language. 1.1. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this - document are to be interpreted as described in RFC 2119 [RFC2119]. + "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 + capitals, as shown here. 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. + relationships and are not a required feature of this protocol. "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 clients to progressively update their implementations when a new version of the extension is deployed. Servers SHOULD (for a temporary migration period) provide support for older versions of the extension in parallel to the newest version, and allow clients to select their preferred version via the element of the command. If a client requests multiple versions of the extension at login, @@ -152,28 +152,28 @@ 3. Object Attributes This extension adds additional elements to [RFC5730] login command and response. Only those new elements are described here. 3.1. Event A security event, using the element, represents either a warning or error identified by the server after the client has connected and submitted the login command. There MAY be multiple - events returned that provides information for the client to address. - The MAY include a free form description. All of the + events returned that provide information for the client to address. + The MAY include a free-form description. All of the security events use a consistent set of attributes, where the exact set of applicable attributes is based on the event type. The supported set of element attributes include: "type": A REQUIRED attribute that defines the type of security - event. The enumerated list of "type" values include: + event. The enumerated list of "type" values includes: "password": Identifies a password expiry event, where the password expires in the future or has expired based on the "exDate" date and time. "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 @@ -198,25 +198,25 @@ connect or MAY be an error to login. An example is 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, 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). + "lang": Identifies the negotiated language of the free-form + description. The default is "en" (English). - Example login security event for a password expiring in a week: + Example login security event for password expiration, where the + current date is 2018-03-25: Password expiration soon Example login security event for identifying 100 failed logins over @@ -426,22 +426,22 @@ 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 - will expire in a week: + Example EPP response to a successful login command on 2018-03-25, + where the password will expire in a week: S: S: S: S: S: Command completed successfully S: S: S: . 10.2. Informative References [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, . + [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, + May 2017, . + 10.3. URIs [1] https://pages.nist.gov/800-63-3/sp800-63b.html Appendix A. Change History A.1. Change from 00 to 01 1. Based on the feedback from Patrick Mevzek and a proposal from Scott Hollenbeck, changed the minimum length of the password from @@ -936,22 +940,50 @@ 1. Update the definition of the "stat" security event type to reference sub-type to match the language for the "name" attribute. 2. Added the sentence 'The "name" attribute MUST be set when the "type" attribute is "stat" or "custom".' to the definition of the "name" attribute for clarity. 3. Update the definition of the "userAgentType" in the XML schema to require at least one sub-element using a element. -Authors' Addresses +A.9. Change from REGEXT 04 to REGEXT 05 + + Updates based on the review by Barry Leiba, that include: + 1. In section 1.1, updated to use BCP 14 boilerplate and references + as defined in RFC 8174. + 2. In section 1.1, change "REQUIRED" to "required". + 3. Keep the "Migration to Newer Versions of This Extension" section + by removing the note for removal to the RFC Editor. + 4. In section 3.1, change "MAY be multiple events returned that + provides information" to "MAY be multiple events returned that + provide information". + 5. In section 3.1, change "free form" to "free-form". + 6. In section 3.1, change "The enumerated list of "type" values + include:" to "The enumerated list of "type" values includes:". + 7. In section 3.1, change "Identifies the language of the free-form + description if the negotiated language is something other than + the default value of "en" (English)." to "Identifies the + negotiated language of the free-form description. The default is + "en" (English). + 8. In section 3.1, change example description from "Example login + security event for a password expiring in a week:" to "Example + login security event for password expiration, where the current + date is 2018-03-25:". + 9. In section 4.1, change "Example EPP response to a successful + login command where the password will expire in a week:" to + "Example EPP response to a successful login command on + 2018-03-25, where the password will expire in a week:". + +Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisign.com Matthew Pozun