]> VeriSign, Inc.

12061 Bluemont Way Reston VA 20190 US jgould@verisign.com http://www.verisign.com

VeriSign, Inc.

12061 Bluemont Way Reston VA 20190 US mpozun@verisign.com http://www.verisign.com

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.

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 events supported include: password expiry, client certificate expiry, insecure cipher, insecure TLS protocol, new pasword complexity, login 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.

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. 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" 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.

(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 <svcExtension> element of the <login> command. If a client requests multiple versions of the extension at login, then, when preparing responses to commands which do not include extension elements, the server SHOULD only include extension elements in the namespace of the newest version of the extension requested by the client. When preparing responses to commands which do include extension elements, the server SHOULD only include extension elements for the extension versions present in the command.

This extension adds additional elements to login command and response. Only those new elements are described here.

A security event, using the <loginSec:event> 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 <loginSec:event> 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 <loginSec:event> element attributes include: A REQUIRED attribute that defines the type of security event. The enumerated list of "type" values include: Identifies a password expiry event, where the password expires in the future or has expired based on the "exDate" date and time. Identifies a client certificate expiry event, where the client certificate will expire at the "exDate" date and time. Identifies the use of an insecure or deprecated TLS cipher suite. Identifies the use of an insecure or deprecated TLS protocol. The new password does not meet the server password complexity requirements. Provides a login security statistical warning that MUST set the "name" of the statistic. Custom event type that MUST set the "name" attribute with the custom event type name. Used to define a sub-type or the type name when the "type" attribute is "custom". 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. 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 password that may result in a failed login. Identifies the value that resulted in the login security event. An example is the negotiated insecure cipher suite or the negotiated insecure TLS protocol. Defines the duration that a statistical event is associated with. 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: Password expiration soon ]]>

Example login security event for identifying 100 failed logins over the last day, using the "stat" sub-type of "failedLogins": Excessive invalid daily logins ]]>

The <loginSec:pw> element MUST override the <pw> element only if the <pw> contains the predefined value of "[LOGIN-SECURITY]", which is a constant value for the server to use the <loginSec:pw> element for the password. Similarly, the <loginSec:newPW> element MUST override the <newPW> element only if the <newPW> contains the predefined value of "[LOGIN-SECURITY]", which is a constant value for the server to use the <loginSec:newPW> 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 <loginSec:pw> element in place of the <pw> element or to use the <loginSec:newPW> in place of the <newPW> element.

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 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.

A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification .

This extension defines additional elements to extend the EPP <login> command and response to be used in conjunction with . The EPP <login> command is used to establish a session with an EPP server. This extension overrides the password that is passed with the <pw> or the <newPW> element as defined in . A <loginSec:loginSec> element is sent along with the <login> 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 <loginSec:userAgent> element contains 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 MUST only be used if the <pw> element is set to the "[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 used if the <newPW> element is set to the "[LOGIN-SECURITY]" value.

Example login command that uses the <loginSec:pw> element instead of the <pw> element to establish the session and includes the <loginSec:userAgent> element: C: C: C: C: ClientX 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: C: C: C: C: 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: C:]]>

Example login command that uses the <loginSec:pw> element instead of the <pw> element to establish the session, and uses the <loginSec:newPW> element instead of the <newPW> element to set the new password: C: C: C: C: ClientX C: [LOGIN-SECURITY] 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: C: C: C: C: 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 <pw> element to establish the session, and uses the <loginSec:newPW> element instead of the <newPW> element to set the new password: C: C: C: C: ClientX C: shortpassword 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: C: C: C: C: 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: client supports the extension based on the <svcExtension> element of the <login> command. The server has identified at least one login security event to communicate to the client. The extension to the EPP response uses the <loginSec:loginSecData> element that contains the following child elements: One or more <loginSec:event> elements defined in .

Example EPP response to a successful login command where the password will expire in a week: S: S: S: S: Command completed successfully S: S: S: S: S: Password expiring in a week S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S:]]>

Example EPP response to a failed login command where the password has expired and the new password does not meet the server complexity requirements: S: S: S: S: Authentication error S: S: S: S: S: Password has expired S: S: S: New password does not meet complexity requirements S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S:]]>

Example EPP response to a successful login command where there is a set of login security events: S: S: S: S: Command completed successfully S: S: S: S: S: Password expiration soon S: S: S: S: Non-PFS Cipher negotiated S: S: S: Insecure TLS protocol negotiated S: S: S: Excessive invalid daily logins S: S: S: A custom login security event occured S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S:]]>

One schema is presented here that is the EPP Login Security Extension schema. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes.

Extensible Provisioning Protocol v1.0 Login Security Extension Schema. END]]>

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . The following URI assignment is requested of IANA: Registration request for the loginSec namespace: URI: urn:ietf:params:xml:ns:epp:loginSec-0.4 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 Registrant Contact: IESG XML: See the "Formal Syntax" section of this document.

The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in . The details of the registration are as follows: Name of Extension: "Login Security Extension for the Extensible Provisioning Protocol (EPP)" Document status: Standards Track Reference: (insert reference to RFC version of this document) Registrant Name and Email Address: IESG, <iesg@ietf.org> TLDs: Any IPR Disclosure: None Status: Active Notes: None

Note to RFC Editor: Please remove this section and the reference to RFC 7942 before publication. TBD

The extension leaves the password (<pw> element) and new password (<newPW> element) minimum length beyond 6 characters and the maximum length up to sever policy. The server SHOULD enforce minimum and maximum length requirements that are appropriate for their operating environment. One example of a guideline for password length policies can be found in section 5 of NIST Special Publication 800-63B. The client SHOULD NOT decrease the security of a new password by decreasing the length of the current password. For example, a client with a 20 character password set using the extension, should not use the login command in without using the extension, to set a new password that is less than or equal to 16 characters. The extension provides an extensible list of login security events to inform clients of connection and login warnings and errors.

The authors wish to thank the following persons for their feedback and suggestions: Martin Casanova Scott Hollenbeck Patrick Mevzek

&RFC2119; &RFC3688; &RFC5730; &RFC7942; &W3C.REC-xmlschema-2-20041028; &RFC7451;

Based on the feedback from Patrick Mevzek and a proposal from Scott Hollenbeck, changed the minimum length of the password from 8 to 6, revised the description of the password, and added text in the Security Considerations section for the server password length policy.

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.

Updates based on the review by Patrick Mevzek, that include: 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". Changed "contains the following child elements" to "MUST contain at least one of the following child elements", section "EPP <login> Command" to ensure that an empty <loginSec:loginSec> element is not passed. 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.

Changed to regext working group draft by changing draft-gould-regext-login-security to draft-ietf-regext-login-security.

Changed the <loginSec:userAgent> element to be structured with the <loginSec:app>, <loginSec:tech>, and <loginSec:os> 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.