<?xml version="1.0"encoding="US-ASCII"?>encoding="UTF-8"?> <!DOCTYPE rfc SYSTEM"rfc2629.dtd" [ <!-- One method to get references from the online citation libraries. There has to be one entity for each item to be referenced. An alternate method (rfc include) is described in the references. --> <!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"> <!ENTITY RFC3688 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml"> <!ENTITY RFC5234 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml"> <!ENTITY RFC5730 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5730.xml"> <!ENTITY RFC7451 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7451.xml"> <!ENTITY RFC7942 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7942.xml"> <!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml"> <!ENTITY RFC8265 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8265.xml"> <!ENTITY W3C.REC-xmlschema-2-20041028 PUBLIC '' 'http://xml2rfc.ietf.org/public/rfc/bibxml4/reference.W3C.REC-xmlschema-2-20041028.xml'>]> <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> <!-- used by XSLT processors --> <!-- For a complete list and description of processing instructions (PIs), please see http://xml.resource.org/authoring/README.html. --> <!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use. (Here they are set differently than their defaults in xml2rfc v1.32) --> <?rfc strict="yes" ?> <!-- give errors regarding ID-nits and DTD validation --> <!-- control the table of contents (ToC) --> <?rfc toc="yes"?> <!-- generate a ToC --> <?rfc tocdepth="4"?> <!-- the number of levels of subsections in ToC. default: 3 --> <!-- control references --> <?rfc symrefs="yes"?> <!-- use symbolic references tags, i.e, [RFC2119] instead of [1] --> <?rfc sortrefs="yes" ?> <!-- sort the reference entries alphabetically --> <!-- control vertical white space (using these PIs as follows is recommended by the RFC Editor) --> <?rfc compact="yes" ?> <!-- do not start each main section on a new page --> <?rfc subcompact="yes"?> <!-- keep one blank line between list items --> <?rfc comments="yes" ?> <!-- show cref output --> <?rfc inline="yes" ?> <!-- inline cref output --> <!-- end of list of popular I-D processing instructions -->"rfc2629-xhtml.ent"> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="std" consensus="true" docName="draft-ietf-regext-login-security-10"ipr="trust200902">number="8807" ipr="trust200902" obsoletes="" updates="" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true" sortRefs="true" version="3"> <!--category values: std, bcp, info, exp, and historic ipr values: full3667, noModification3667, noDerivatives3667 you can add the attributes updates="NNNN" and obsoletes="NNNN" they will automatically be output with "(if approved)"xml2rfc v2v3 conversion 2.40.1 --> <!-- ***** FRONT MATTER ***** --> <front> <titleabbrev="loginSec">abbrev="Login Security Extension for the EPP"> Login Security Extension for the Extensible Provisioning Protocol (EPP)</title> <seriesInfo name="RFC" value="8807"/> <author fullname="James Gould"initials="J.G"initials="J." surname="Gould"> <organization>VeriSign, Inc.</organization> <address> <postal> <street>12061 Bluemont Way</street> <city>Reston</city> <region>VA</region> <code>20190</code><country>US</country><country>United States of America</country> </postal> <email>jgould@verisign.com</email> <uri>http://www.verisign.com</uri> </address> </author> <author fullname="Matthew Pozun"initials="M.P"initials="M." surname="Pozun"> <organization>VeriSign, Inc.</organization> <address> <postal> <street>12061 Bluemont Way</street> <city>Reston</city> <region>VA</region> <code>20190</code><country>US</country><country>United States of America</country> </postal> <email>mpozun@verisign.com</email> <uri>http://www.verisign.com</uri> </address> </author> <dateday="26" month="February"month="August" year="2020"/> <abstract> <t>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.</t> </abstract> </front> <middle> <sectiontitle="Introduction">numbered="true" toc="default"> <name>Introduction</name> <t>This document describes an Extensible Provisioning Protocol (EPP) extension for enhancing the security of the EPP login command in EPP <xreftarget="RFC5730"/>.target="RFC5730" format="default"/>. EPP <xreftarget="RFC5730"/>target="RFC5730" format="default"/> includes a maximum password length of 16characters thatcharacters, which inhibits implementing stronger password security policies with higher entropy. 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 <xreftarget="RFC5730"/>target="RFC5730" format="default"/> can be overridden by the password included in the extension to extend past the 16-character maximum. The security events supportedinclude:include password expiry, client certificate expiry, insecure cipher, insecure TLS protocol, new password complexity, login security statistical warning, and a custom event. The attributes supported by the security events includeidentifying thean identified event type orsub-type, indicating thea subtype, an indicated 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.</t> <sectiontitle="Conventionsnumbered="true" toc="default"> <name>Conventions Used in ThisDocument"> <t>TheDocument</name> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t>here. </t> <t>XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this documentMUST<bcp14>MUST</bcp14> be interpreted in the character case presented in order to develop a conforming implementation.</t> <t>In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server.IndentationIn examples, indentation andwhite space in exampleswhitespace are provided only to illustrate element relationships and are not a required feature of thisprotocol. </t>protocol.</t> <t>"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 implementationsMUST NOT<bcp14>MUST NOT</bcp14> depend onit and insteadit. Instead, they are to employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.</t> <t>"whitespace" is defined by the XMLschemaSchema whiteSpacedatatypedata type in <xreftarget="W3C.REC-xmlschema-2-20041028"/>,target="W3C.REC-xmlschema-2-20041028" format="default"/>, which only includes the ASCII whitespace characters #x9 (tab), #xA (linefeed), #xD (carriage return), and #x20 (space).</t> </section> </section> <sectiontitle="Migratingnumbered="true" toc="default"> <name>Migrating to Newer Versions of ThisExtension">Extension</name> <t>Serverswhichthat implement this extensionSHOULD<bcp14>SHOULD</bcp14> provide a way for clients to progressively update their implementations when a new version of the extension is deployed. A newer version of the extension is expected to use an XML namespace with a higher version number than the prior versions.</t> <t>ServersSHOULD<bcp14>SHOULD</bcp14> (for a temporary migration period up to server policy) provide support for older versions of the extension in parallel to the newestversion,version and allow clients to select their preferred version via the <svcExtension> element of the <login> command.</t> <t>If a client requests multiple versions of the extension at login, then, when preparing responses to commandswhichthat do not include extension elements, the serverSHOULD<bcp14>SHOULD</bcp14> only include extension elements in the namespace of the newest version of the extension requested by the client.</t> <t>When preparing responses to commandswhichthat do include extension elements, the serverSHOULD<bcp14>SHOULD</bcp14> only include extension elements for the extension versions present in the command.</t> </section> <section anchor="attrs"title="Object Attributes">numbered="true" toc="default"> <name>Object Attributes</name> <t>This extension adds additional elements to <xreftarget="RFC5730"/>target="RFC5730" format="default"/> login command and response. Only those new elements are described here.</t> <section anchor="event"title="Event">numbered="true" toc="default"> <name>Event</name> <t>A securityevent,event using the <loginSec:event>element,element represents either a warning or error identified by the server after the client has connected and submitted the login command. The <loginSec:event> element is contained in a list of one or more elements in the <loginSec:loginSecData> element, so thereMAY<bcp14>MAY</bcp14> be multiple events returned that provide information for the client to address. The <loginSec:event>MAY<bcp14>MAY</bcp14> 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:</t><t><list hangIndent="4" style="hanging"> <t hangText=""type":">A REQUIRED<dl newline="false" indent="4"> <dt>"type":</dt> <dd>A <bcp14>REQUIRED</bcp14> attribute that defines the type of security event. The enumerated list of"type""type" valuesincludes:</t> <t><list hangIndent="4" style="hanging"> <t hangText=""password":">Identifiesincludes:</dd> <dt/> <dd> <dl newline="false" indent="4"> <dt>"password":</dt> <dd>Identifies a password expiryevent,event where the password expires in the future or has expired based on the "exDate" date and time. The "exDate" attributeMUST<bcp14>MUST</bcp14> be set with the password expiry date andtime.</t> <t hangText=""certificate":">Identifiestime.</dd> <dt>"certificate":</dt> <dd>Identifies a client certificate expiryevent,event where the client certificate will expire at the "exDate" date and time. The "exDate" attributeMUST<bcp14>MUST</bcp14> be set with the certificate expiry date andtime.</t> <t hangText=""cipher":">Identifiestime.</dd> <dt>"cipher":</dt> <dd>Identifies the use of an insecure or deprecated TLS cipher suite. The "name" attributeMUST<bcp14>MUST</bcp14> be set with the name of the cipher suite, which is free-form and is not expected to be parsed and automatically addressed by the client. An example of cipher suite names can be found in the TLS Cipher Suites of the <ereftarget="https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4">Transporttarget="https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4">"Transport Layer Security (TLS)Parameters IANA Registry</eref>. </t> <t hangText=""tlsProtocol":">IdentifiesParameters" registry</eref>.</dd> <dt>"tlsProtocol":</dt> <dd>Identifies the use of an insecure or deprecated TLS protocol. The "name" attributeMUST<bcp14>MUST</bcp14> be set with the name of the TLS protocol, which is free-form and is not expected to be parsed and automatically addressed by theclient.</t> <t hangText=""newPW":">Theclient.</dd> <dt>"newPW":</dt> <dd>The new password does not meet the server password complexityrequirements.</t> <t hangText=""stat":">Providesrequirements.</dd> <dt>"stat":</dt> <dd>Provides a login security statistical warning thatMUST<bcp14>MUST</bcp14> set the "name" attribute to the name of the statisticsub-type.</t> <t hangText=""custom":">Customsubtype.</dd> <dt>"custom":</dt> <dd>Custom event type thatMUST<bcp14>MUST</bcp14> set the "name" attribute with the custom event typename.</t> </list></t> <t hangText=""name":">Usedname.</dd> </dl> </dd> <dt>"name":</dt> <dd>Used to define asub-typesubtype when the "type" attribute is not "custom" or the full type name when the "type" attribute is "custom". The "name" attributeMUST<bcp14>MUST</bcp14> be set when the "type" attribute is "stat" or "custom". The possible set of "name" values, by event type, can bediscovered / negotiateddiscovered/negotiated out of band to EPP or using a separate EPP extension designed to provide server policy information to theclient.</t> <t hangText=""level":">Definesclient.</dd> <dt>"level":</dt> <dd>Defines the level of the event as either "warning" for a warning event that needsaction,action or "error" for an error event that requires immediateaction.</t> <t hangText=""exDate":">Containsaction.</dd> <dt>"exDate":</dt> <dd>Contains the date and time that a "warning" level has or will become an "error" level. Atexpiryexpiry, thereMAY<bcp14>MAY</bcp14> be a connection failure orMAY<bcp14>MAY</bcp14> be a login failure. An example is an expired certification that will result in a connection failure or an expired password that may result in a loginfailure.</t> <t hangText=""value":">Identifiesfailure.</dd> <dt>"value":</dt> <dd>Identifies the value that resulted in the login security event. An example is the negotiated insecure cipher suite or the negotiated insecure TLSprotocol.</t> <t hangText=""duration":">Definesprotocol.</dd> <dt>"duration":</dt> <dd>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 primitivedatatypedata type insectionSection 3.2.6 of <xreftarget="W3C.REC-xmlschema-2-20041028"/>.</t> <t hangText=""lang":">Identifiestarget="W3C.REC-xmlschema-2-20041028" format="default"/>.</dd> <dt>"lang":</dt> <dd>Identifies the negotiated language of the free-form description. The format of the language is defined by the language primitivedatatypedata type insectionSection 3.3.3 of <xreftarget="W3C.REC-xmlschema-2-20041028"/>.target="W3C.REC-xmlschema-2-20041028" format="default"/>. The default is "en"(English).</t> </list></t> <figure> <preamble>Example(English).</dd> </dl> <t>Example login security event for password expiration, where the current date is2020-03-25:</preamble> <artwork><![CDATA[2020-03-25:</t> <sourcecode type="xml"><![CDATA[ <loginSec:event type="password" level="warning" exDate="2020-04-01T22:00:00.0Z" lang="en"> Password expiration soon</loginSec:event>]]></artwork> </figure> <figure> <preamble>Example</loginSec:event> ]]></sourcecode> <t>Example login security event for identifying 100 failed logins over the last day, using the "stat"sub-typesubtype of"failedLogins":</preamble> <artwork><![CDATA["failedLogins":</t> <sourcecode type="xml"><![CDATA[ <loginSec:event type="stat" name="failedLogins" level="warning" value="100" duration="P1D"> Excessive invalid daily logins</loginSec:event>]]></artwork> </figure></loginSec:event> ]]></sourcecode> </section> <section anchor="loginSecurityPassword"title=""[LOGIN-SECURITY]" Password">numbered="true" toc="default"> <name>"[LOGIN-SECURITY]" Password</name> <t>When the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <pw> element contains the predefined value of "[LOGIN-SECURITY]", the <loginSec:pw> element overrides the <pw> element, which is a constant value for the server to use the <loginSec:pw> element for the password. Similarly, when the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <newPw> element contains the predefined value of "[LOGIN-SECURITY]", the <loginSec:newPw> element overrides the <newPw> element, which is a constant value for the server to use the <loginSec:newPW> element for the new password. The "[LOGIN-SECURITY]"pre-definedpredefined stringMUST<bcp14>MUST</bcp14> be supported by the server for the client to explicitly indicate to the server whether to use <loginSec:pw> element in place of the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <pw> element or to use the <loginSec:newPW> in place of the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <newPW> element. The serverMUST NOT<bcp14>MUST NOT</bcp14> allow the client to set the password to the value "[LOGIN-SECURITY]".</t> </section> <section anchor="datestimes"title="Datesnumbered="true" toc="default"> <name>Dates andTimes">Times</name> <t>Date and time attribute valuesMUST<bcp14>MUST</bcp14> 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 <xreftarget="W3C.REC-xmlschema-2-20041028"/> MUSTtarget="W3C.REC-xmlschema-2-20041028" format="default"/> <bcp14>MUST</bcp14> be used to represent date-time values, as XML Schema does not support truncated date-time forms or lower case "T" and "Z" characters.</t> </section> </section> <section anchor="commands"title="EPPnumbered="true" toc="default"> <name>EPP CommandMapping">Mapping</name> <t>A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification <xreftarget="RFC5730"/>.</t>target="RFC5730" format="default"/>.</t> <section anchor="loginCommand"title="EPPnumbered="true" toc="default"> <name>EPP <login>Command">Command</name> <t>This extension defines additional elements to extend the EPP <login> command and response to be used in conjunction with <xreftarget="RFC5730"/>.</t>target="RFC5730" format="default"/>.</t> <t>The EPP <login> command is used to establish a session with an EPP server. This extension overrides the password that is passed with the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <pw> or the <newPW>elementelement, as defined in <xreftarget="loginSecurityPassword"/>.target="loginSecurityPassword" format="default"/>. A <loginSec:loginSec> element is sent along with the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <login> command andMUST<bcp14>MUST</bcp14> contain at least one of the following child elements:</t><t><list hangIndent="4" style="hanging"> <t hangText="<loginSec:userAgent>:">OPTIONAL<dl newline="false" indent="4"> <dt><loginSec:userAgent>:</dt> <dd><bcp14>OPTIONAL</bcp14> clientuser agentuser-agent information that identifies the 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 server may use the information for real-time identification and client notification of security issues, such as keying off of the client application software for executing security rule checks. The server may capture the information to identify future security policy issues, such as deprecating or removing TLS cipher suites or TLS protocols. The <loginSec:userAgent> elementMUST<bcp14>MUST</bcp14> contain at least one of the following childelements:</t> <t><list hangIndent="4" style="hanging"> <t hangText="<loginSec:app>:">OPTIONALelements:</dd> <dt/> <dd> <dl newline="false" indent="4"> <dt><loginSec:app>:</dt> <dd> <t><bcp14>OPTIONAL</bcp14> name of the client application software with version if available, such as the name of the client SDK "EPP SDK 1.0.0". The <loginSec:app> element value can be created by appending the version number to the name of the application software, such as the<xref target="RFC5234">AugmentedAugmented Backus-Naur Form (ABNF)grammar</xref> format: <list> <t>appgrammar <xref target="RFC5234" format="default"></xref> format:</t> <sourcecode type="abnf"> app = name SPversion</t> <t>nameversion name =1*VCHAR</t> <t>version1*VCHAR version =1*VCHAR</t> </list> </t> <t hangText="<loginSec:tech>:">OPTIONAL1*VCHAR </sourcecode> </dd> <dt><loginSec:tech>:</dt> <dd> <t><bcp14>OPTIONAL</bcp14> technology used for the client software with version if available, such as "Vendor Java 11.0.6". The <loginSec:tech> element value can be created by including the technology vendor, technology name, and technology version, such as the<xref target="RFC5234">AugmentedAugmented Backus-Naur Form (ABNF)grammar</xref> format: <list> <t>techgrammar <xref target="RFC5234" format="default"></xref> format:</t> <sourcecode type="abnf"> tech = vendor SP name SPversion</t> <t>vendorversion vendor =1*VCHAR</t> <t>name1*VCHAR name =1*VCHAR</t> <t>version1*VCHAR version =1*VCHAR</t> </list></t> <t hangText="<loginSec:os>:">OPTIONAL1*VCHAR </sourcecode> </dd> <dt><loginSec:os>:</dt> <dd> <t><bcp14>OPTIONAL</bcp14> client operating system used with version if available, such as "x86_64 Mac OS X 10.15.2". The <loginSec:os> element value can be created by including the operating system architecture, operating system name, and operating system version, such as the<xref target="RFC5234">AugmentedAugmented Backus-Naur Form (ABNF)grammar</xref> format: <list> <t>osgrammar <xref target="RFC5234" format="default"></xref> format:</t> <sourcecode type="abnf"> os = arch SP name SPversion</t> <t>archversion arch =1*VCHAR</t> <t>name1*VCHAR name =1*VCHAR</t> <t>version1*VCHAR version =1*VCHAR</t> </list></t> </list></t> <t hangText="<loginSec:pw>:">OPTIONAL1*VCHAR </sourcecode> </dd> </dl> </dd> <dt><loginSec:pw>:</dt> <dd><bcp14>OPTIONAL</bcp14> 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 elementMUST<bcp14>MUST</bcp14> only be set if the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <pw> element is set to the "[LOGIN-SECURITY]"value.</t> <t hangText="<loginSec:newPW>:">OPTIONALvalue.</dd> <dt><loginSec:newPW>:</dt> <dd><bcp14>OPTIONAL</bcp14> 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 elementMUST<bcp14>MUST</bcp14> only be set if the <xreftarget="RFC5730"/>target="RFC5730" format="default"/> <newPW> element is set to the "[LOGIN-SECURITY]"value.</t> </list></t>value.</dd> </dl> <t>It isRECOMMENDED<bcp14>RECOMMENDED</bcp14> that the plain text password in the <loginSec:pw> and <loginSec:newPw> 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; the OpaqueString PRECIS profile in <xreftarget="RFC8265"/>target="RFC8265" format="default"/> is recommended in the absence of other considerations.</t><figure> <preamble>Example<t>Example login command that uses the <loginSec:pw> element instead of the<xref target="RFC5730"/><pw> element (<xref target="RFC5730" format="default"/>) to establish the session and includes the <loginSec:userAgent>element:</preamble> <artwork><![CDATA[element:</t> <sourcecode type=""><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <login> C: <clID>ClientX</clID> C: <pw>[LOGIN-SECURITY]</pw> C: <options> C: <version>1.0</version> C: <lang>en</lang> C: </options> C: <svcs> C: <objURI>urn:ietf:params:xml:ns:obj1</objURI> C: <objURI>urn:ietf:params:xml:ns:obj2</objURI> C: <objURI>urn:ietf:params:xml:ns:obj3</objURI> C: <svcExtension> C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-1.0</extURI> C: </svcExtension> C: </svcs> C: </login> C: <extension> C: <loginSec:loginSec C: xmlns:loginSec= C: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> C: <loginSec:userAgent> C: <loginSec:app>EPP SDK 1.0.0</loginSec:app> C: <loginSec:tech>Vendor Java 11.0.6</loginSec:tech> C: <loginSec:os>x86_64 Mac OS X 10.15.2</loginSec:os> C: </loginSec:userAgent> C: <loginSec:pw>this is a long password</loginSec:pw> C: </loginSec:loginSec> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command>C:</epp>]]></artwork> </figure> <figure> <preamble>ExampleC:</epp> ]]></sourcecode> <t>Example login command that uses the <loginSec:pw> element instead of the<xref target="RFC5730"/><pw> element (<xref target="RFC5730" format="default"/>) to establish thesession,session and that uses the <loginSec:newPW> element instead of the<xref target="RFC5730"/><newPW> element (<xref target="RFC5730" format="default"/>) to set the newpassword:</preamble> <artwork><![CDATA[password:</t> <sourcecode type=""><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <login> C: <clID>ClientX</clID> C: <pw>[LOGIN-SECURITY]</pw> C: <newPW>[LOGIN-SECURITY]</newPW> C: <options> C: <version>1.0</version> C: <lang>en</lang> C: </options> C: <svcs> C: <objURI>urn:ietf:params:xml:ns:obj1</objURI> C: <objURI>urn:ietf:params:xml:ns:obj2</objURI> C: <objURI>urn:ietf:params:xml:ns:obj3</objURI> C: <svcExtension> C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-1.0</extURI> C: </svcExtension> C: </svcs> C: </login> C: <extension> C: <loginSec:loginSec C: xmlns:loginSec= C: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> C: <loginSec:pw>this is a long password C: </loginSec:pw> C: <loginSec:newPW>new password that is still long C: </loginSec:newPW> C: </loginSec:loginSec> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command>C:</epp>]]></artwork> </figure> <figure> <preamble>ExampleC:</epp> ]]></sourcecode> <t>Example login command that uses the<xref target="RFC5730"/><pw> element (<xref target="RFC5730" format="default"/>) to establish thesession,session and that uses the <loginSec:newPW> element instead of the<xref target="RFC5730"/><newPW> element (<xref target="RFC5730" format="default"/>) to set the newpassword:</preamble> <artwork><![CDATA[password:</t> <sourcecode type=""><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <login> C: <clID>ClientX</clID> C: <pw>shortpassword</pw> C: <newPW>[LOGIN-SECURITY]</newPW> C: <options> C: <version>1.0</version> C: <lang>en</lang> C: </options> C: <svcs> C: <objURI>urn:ietf:params:xml:ns:obj1</objURI> C: <objURI>urn:ietf:params:xml:ns:obj2</objURI> C: <objURI>urn:ietf:params:xml:ns:obj3</objURI> C: <svcExtension> C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-1.0</extURI> C: </svcExtension> C: </svcs> C: </login> C: <extension> C: <loginSec:loginSec C: xmlns:loginSec= C: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> C: <loginSec:newPW>new password that is still long C: </loginSec:newPW> C: </loginSec:loginSec> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command>C:</epp>]]></artwork> </figure>C:</epp> ]]></sourcecode> <t>Upon a completed login command (success or failed), the extensionMUST<bcp14>MUST</bcp14> be included in the response when both of the following conditions hold:</t><t><list hangIndent="4" style="hanging"> <t hangText="Client<dl newline="false" indent="4"> <dt>Client supportsextension:"> Theextension:</dt> <dd>The client supports the extension based on the <svcExtension> element of the <login>command.</t> <t hangText="Atcommand.</dd> <dt>At least one login securityevent:"> Theevent:</dt> <dd>The server has identified at least one login security event to communicate to theclient.</t> </list></t>client.</dd> </dl> <t>The extension to the EPP response uses the <loginSec:loginSecData> element that contains the following child elements:</t><t><list hangIndent="4" style="hanging"> <t hangText="<loginSec:event>:">One<dl newline="false" indent="4"> <dt><loginSec:event>:</dt> <dd>One or more <loginSec:event> elements defined in <xreftarget="event"/>.</t> </list></t> <figure> <preamble>Exampletarget="event" format="default"/>.</dd> </dl> <t>Example EPP response to a successful login command on 2020-03-25, where the password will expire in aweek:</preamble> <artwork><![CDATA[week:</t> <sourcecode type=""><![CDATA[ S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <extension> S: <loginSec:loginSecData S: xmlns:loginSec= S: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> S: <loginSec:event S: type="password" S: level="warning" S: exDate="2020-04-01T22:00:00.0Z" S: lang="en"> S: Password expiring in a week S: </loginSec:event> S: </loginSec:loginSecData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response>S:</epp>]]></artwork> </figure> <figure> <preamble>ExampleS:</epp> ]]></sourcecode> <t>Example EPP response to a failed login command where the password has expired and the new password does not meet the server complexityrequirements:</preamble> <artwork><![CDATA[requirements:</t> <sourcecode type=""><![CDATA[ S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="2200"> S: <msg>Authentication error</msg> S: </result> S: <extension> S: <loginSec:loginSecData S: xmlns:loginSec= S: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> S: <loginSec:event S: type="password" S: level="error" S: exDate="2020-03-24T22:00:00.0Z"> S: Password has expired S: </loginSec:event> S: <loginSec:event S: type="newPW" S: level="error"> S: New password does not meet complexity requirements S: </loginSec:event> S: </loginSec:loginSecData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response>S:</epp>]]></artwork> </figure> <figure> <preamble>ExampleS:</epp> ]]></sourcecode> <t>Example EPP response to a successful login command where there is a set of login securityevents:</preamble> <artwork><![CDATA[events:</t> <sourcecode type=""><![CDATA[ S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <extension> S: <loginSec:loginSecData S: xmlns:loginSec= S: "urn:ietf:params:xml:ns:epp:loginSec-1.0"> S: <loginSec:event S: type="password" S: level="warning" S: exDate="2020-04-01T22:00:00.0Z" S: lang="en"> S: Password expiration soon S: </loginSec:event> S: <loginSec:event S: type="certificate" S: level="warning" S: exDate="2020-04-02T22:00:00.0Z"/> S: <loginSec:event S: type="cipher" S: level="warning" S: value="TLS_RSA_WITH_AES_128_CBC_SHA"> S: Non-PFS Cipher negotiated S: </loginSec:event> S: <loginSec:event S: type="tlsProtocol" S: level="warning" S: value="TLSv1.0"> S: Insecure TLS protocol negotiated S: </loginSec:event> S: <loginSec:event S: type="stat" S: name="failedLogins" S: level="warning" S: value="100" S: duration="P1D"> S: Excessive invalid daily logins S: </loginSec:event> S: <loginSec:event S: type="custom" S: name="myCustomEvent" S: level="warning"> S: A custom login security eventoccuredoccurred S: </loginSec:event> S: </loginSec:loginSecData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response>S:</epp>]]></artwork> </figure>S:</epp> ]]></sourcecode> </section> <!-- end LOGIN command --> </section> <!-- EPP command mapping --> <section anchor="syntax"title="Formal Syntax">numbered="true" toc="default"> <name>Formal Syntax</name> <t>The EPP Login Security Extension schema is presented here.</t> <t>The formal syntaxpresentedshown here is a complete XMLschemaSchema representation of the object mapping suitable for automated validation of EPP XML instances. TheBEGIN<CODE BEGINS> andEND<CODE ENDS> tags are not part of the XMLschema;Schema; they are used to note the beginning and ending of the XMLschemaSchema for URI registration purposes.</t> <sectiontitle="Loginnumbered="true" toc="default"> <name>Login Security ExtensionSchema"> <figure> <artwork><![CDATA[ BEGINSchema</name> <sourcecode type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:loginSec="urn:ietf:params:xml:ns:epp:loginSec-1.0" targetNamespace="urn:ietf:params:xml:ns:epp:loginSec-1.0" elementFormDefault="qualified"> <!-- Import common element types. --> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:epp-1.0" /> <annotation> <documentation>Extensible Provisioning Protocol v1.0 Login Security Extension Schema.</documentation> </annotation> <!-- Login command extension elements --> <element name="loginSec" type="loginSec:loginSecType" /> <!-- Attributes associated with the login command extension. --> <complexType name="loginSecType"> <sequence> <element name="userAgent" type="loginSec:userAgentType" minOccurs="0" /> <element name="pw" type="loginSec:pwType" minOccurs="0" /> <element name="newPW" type="loginSec:pwType" minOccurs="0" /> </sequence> </complexType> <simpleType name="pwType"> <restriction base="token"> <minLength value="6" /> </restriction> </simpleType> <complexType name="userAgentType"> <choice> <sequence> <element name="app" type="token" /> <element name="tech" type="token" minOccurs="0" /> <element name="os" type="token" minOccurs="0" /> </sequence> <sequence> <element name="tech" type="token" /> <element name="os" type="token" minOccurs="0" /> </sequence> <element name="os" type="token" /> </choice> </complexType> <!-- Login response extension elements --> <element name="loginSecData" type="loginSec:loginSecDataType" /> <complexType name="loginSecDataType"> <sequence> <element name="event" type="loginSec:eventType" minOccurs="1" maxOccurs="unbounded" /> </sequence> </complexType> <!-- Security event element --> <complexType name="eventType"> <simpleContent> <extension base="normalizedString"> <attribute name="type" type="loginSec:typeEnum" use="required" /> <attribute name="name" type="token" /> <attribute name="level" type="loginSec:levelEnum" use="required" /> <attribute name="exDate" type="dateTime" /> <attribute name="value" type="token" /> <attribute name="duration" type="duration" /> <attribute name="lang" type="language" default="en" /> </extension> </simpleContent> </complexType> <!-- Enumerated list of event types, with extensibility via "custom". --> <simpleType name="typeEnum"> <restriction base="token"> <enumeration value="password" /> <enumeration value="certificate" /> <enumeration value="cipher" /> <enumeration value="tlsProtocol" /> <enumeration value="newPW" /> <enumeration value="stat" /> <enumeration value="custom" /> </restriction> </simpleType> <!-- Enumerated list of levels. --> <simpleType name="levelEnum"> <restriction base="token"> <enumeration value="warning" /> <enumeration value="error" /> </restriction> </simpleType> <!-- End of schema. --> </schema>END]]></artwork> </figure>]]></sourcecode> </section> </section> <section anchor="IANA"title="IANA Considerations">numbered="true" toc="default"> <name>IANA Considerations</name> <section anchor="IANA-XML-Namespace"title="XML Namespace"> <t> Thisnumbered="true" toc="default"> <name>XML Namespace</name> <t>This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in <xreftarget="RFC3688"/>.target="RFC3688" format="default"/>. The following URI assignmentis requested of IANA: </t>has been made by IANA:</t> <t>Registration request for the loginSec namespace:</t><t><list> <t>URI: urn:ietf:params:xml:ns:epp:loginSec-1.0</t> <t>Registrant Contact: IESG</t> <t>XML: None.<dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:epp:loginSec-1.0</dd> <dt>Registrant Contact:</dt> <dd>IESG</dd> <dt>XML:</dt> <dd>None. Namespace URIs do not represent an XMLspecification.</t> </list></t>specification.</dd> </dl> <t>Registration request for the loginSec XMLschema:</t> <t><list> <t>URI: urn:ietf:params:xml:schema:epp:loginSec-1.0</t> <t>Registrant Contact: IESG</t> <t>XML: SeeSchema:</t> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:schema:epp:loginSec-1.0</dd> <dt>Registrant Contact:</dt> <dd>IESG</dd> <dt>XML:</dt> <dd>See the "Formal Syntax" section of thisdocument.</t> </list></t>document.</dd> </dl> </section> <section anchor="EPP-Extension-Registry"title="EPPnumbered="true" toc="default"> <name>EPP ExtensionRegistry"> <t> TheRegistry</name> <t>The EPP extension described in this documentshould behas been registered bytheIANA in theEPP Extension Registry"Extensions for the Extensible Provisioning Protocol (EPP)" registry described in <xreftarget="RFC7451"/>.target="RFC7451" format="default"/>. The details of the registration are asfollows: </t> <t> Namefollows:</t> <dl newline="false" spacing="compact"> <dt>Name ofExtension: "LoginExtension:</dt> <dd>"Login Security Extension for the Extensible Provisioning Protocol(EPP)" </t> <t> Document status: Standards Track </t> <t> Reference: (insert reference to RFC version of this document) </t> <t> Registrant(EPP)"</dd> <dt>Document status:</dt> <dd>Standards Track</dd> <dt>Reference:</dt> <dd>RFC 8807</dd> <dt>Registrant Name and EmailAddress: IESG, <iesg@ietf.org> </t> <t> TLDs: Any </t> <t> IPR Disclosure: None </t> <t> Status: Active </t> <t> Notes: None </t> </section> </section> <section anchor="Implementation" title="Implementation Status"> <t>Note to RFC Editor: Please remove this section and the reference to <xref target="RFC7942">RFC 7942</xref> before publication.</t> <t>This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in <xref target="RFC7942">RFC 7942</xref>. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.</t> <t>According to <xref target="RFC7942">RFC 7942</xref>, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".</t> <section title="Verisign EPP SDK"> <t>Organization: Verisign Inc.</t> <t>Name: Verisign EPP SDK</t> <t>Description: The Verisign EPP SDK includes both a full client implementation and a full server stub implementation of draft-ietf-regext-login-security.</t> <t>Level of maturity: Development</t> <t>Coverage: All aspects of the protocol are implemented.</t> <t>Licensing: GNU Lesser General Public License</t> <t>Contact: jgould@verisign.com</t> <t>URL: https://www.verisign.com/en_US/channel-resources/domain-registry-products/epp-sdks</t>Address:</dt> <dd>IESG, <iesg@ietf.org></dd> <dt>Top-Level Domains(TLDs):</dt> <dd>Any</dd> <dt>IPR Disclosure:</dt> <dd>None</dd> <dt>Status:</dt> <dd>Active</dd> <dt>Notes:</dt> <dd>None</dd> </dl> </section> </section> <section anchor="Security"title="Security Considerations">numbered="true" toc="default"> <name>Security Considerations</name> <t>TheSecurity Considerationssecurity considerations of <xreftarget="RFC5730"/>target="RFC5730" format="default"/> apply in this document, and this document enhances these considerations.</t> <t>The extension leaves the password (<pw> element) and new password (<newPW> element) minimum length greater than 6 characters and the maximum length up to server policy. The serverSHOULD<bcp14>SHOULD</bcp14> 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 insectionSection 5 of <eref target="https://pages.nist.gov/800-63-3/sp800-63b.html">NIST Special Publication 800-63B</eref>.</t> <t>The clientSHOULD NOT<bcp14>SHOULD NOT</bcp14> decrease the security of a new password by decreasing the length of the current password. For example, a client with a20 character20-character password set using theextension,extension should not use the login command in <xreftarget="RFC5730"/>target="RFC5730" format="default"/> without using theextension,extension to set a new password that is less than or equal to 16 characters.</t> <t>The extension provides an extensible list of login security events to inform clients of connection and login warnings and errors. The server returning of security events to unauthenticated users needs to take into account the security/privacy issues of returning information to potential attackers.</t> <t>Theuser agentuser-agent information represents the client system of a system-to-system interface, so theuser agentuser-agent informationMUST NOT<bcp14>MUST NOT</bcp14> provide any ability to track individual users or classes of users.</t> </section> </middle> <!-- *****BACK MATTER ***** --> <back> <references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5730.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <reference anchor="W3C.REC-xmlschema-2-20041028" target="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.REC-xmlschema-2-20041028.xml"> <front> <title>XML Schema Part 2: Datatypes Second Edition</title> <seriesInfo name="W3C Recommendation" value="REC-xmlschema-2-20041028"/> <author initials="P." surname="Biron" fullname="Paul V. Biron"> <organization/> </author> <author initials="A." surname="Malhotra" fullname="Ashok Malhotra"> <organization/> </author> <date month="October" year="2004"/> </front> </reference> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/> </references> <references> <name>Informative References</name> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7451.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8265.xml"/> </references> </references> <section anchor="Acknowledgements"title="Acknowledgements">numbered="false" toc="default"> <name>Acknowledgements</name> <t>The authors wish to thank the following persons for their feedback andsuggestions:</t> <t><list style="symbols"> <t>Martin Casanova</t> <t>Scott Hollenbeck</t> <t>Barry Leiba</t> <t>Patrick Mevzek</t> <t>Joseph Yee</t> </list></t> </section> </middle> <!-- *****BACK MATTER ***** --> <back> <!-- References split into informative and normative --> <!-- There are 2 ways to insert reference entries from the citation libraries: 1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown) 2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml") Both are cited textually in the same manner: by using xref elements. If you use the PI option, xml2rfc will, by default, try to find included files in the same directory as the including file. You can also define the XML_LIBRARY environment variable with a value containing a set of directories to search. These can be either in the local filing system or remote ones accessed by http (http://domain/dir/... ).--> <references title="Normative References"> &RFC2119; &RFC3688; &RFC5730; &RFC7942; &RFC8174; &W3C.REC-xmlschema-2-20041028; </references> <references title="Informative References"> &RFC5234; &RFC7451; &RFC8265; </references> <section title="Change History"> <t>[[RFC Editor: Please remove this section.]]</t> <section title="Change from 00 to 01" anchor="change-00-to-01"> <t><list style="numbers"> <t>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.</t> </list></t> </section> <section title="Change from 01 to 02" anchor="change-01-to-02"> <t><list style="numbers"> <t>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.</t> </list></t> </section> <section title="Change from 02 to 03" anchor="change-02-to-03"> <t><list style="numbers"> <t>Updates based on the review by Patrick Mevzek, that include: <list style="numbers"> <t>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".</t> <t>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.</t> <t>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.</t> </list> </t> </list></t> </section> <section title="Change from 03 to REGEXT 00" anchor="change-03-to-WG00"> <t><list style="numbers"> <t>Changed to regext working group draft by changing draft-gould-regext-login-security to draft-ietf-regext-login-security.</t> </list></t> </section> <section title="Change from REGEXT 00 to REGEXT 01" anchor="change-WG00-to-WG01"> <t><list style="numbers"> <t>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.</t> </list></t> </section> <section title="Change from REGEXT 01 to REGEXT 02" anchor="change-WG01-to-WG02"> <t><list style="numbers"> <t>Updated the Implementation Status section from "TBD" to include the Verisign EPP SDK implementation.</t> </list></t> </section> <section title="Change from REGEXT 02 to REGEXT 03" anchor="change-WG02-to-WG03"> <t><list style="numbers"> <t>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.</t> <t>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.</t> <t>Updates based on the review by Joseph Yee, that include: <list style="numbers"> <t>Revised the description of the <loginSec:event> "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.'</t> <t>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.</t> <t>Revised the description of the <loginSec:userAgent> element to read 'The <loginSec:userAgent> element MUST contain at least one of the following child elements:'.</t> </list> </t> <t>Revised the description of the <loginSec:userAgent> to match the child elements that can be passed, by changing "client software" to "client application software" and change "language" to "technology".</t> <t>Changed the XML namespace from urn:ietf:params:xml:ns:epp:loginSec-0.4 to urn:ietf:params:xml:ns:epp:loginSec-1.0.</t> </list></t> </section> <section title="Change from REGEXT 03 to REGEXT 04" anchor="change-WG03-to-WG04"> <t>Updates based on the review by Joseph Yee, that include: <list style="numbers"> <t>Update the definition of the "stat" security event type to reference sub-type to match the language for the "name" attribute.</t> <t>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.</t> <t>Update the definition of the "userAgentType" in the XML schema to require at least one sub-element using a <choice> element.</t> </list> </t> </section> <section title="Change from REGEXT 04 to REGEXT 05" anchor="change-WG04-to-WG05"> <t>Updates based on the review by Barry Leiba, that include: <list style="numbers"> <t>In section 1.1, updated to use BCP 14 boilerplate and references as defined in RFC 8174.</t> <t>In section 1.1, change "REQUIRED" to "required".</t> <t>Keep the "Migration to Newer Versions of This Extension" section by removing the note for removal to the RFC Editor.</t> <t>In section 3.1, change "MAY be multiple events returned that provides information" to "MAY be multiple events returned that provide information".</t> <t>In section 3.1, change "free form" to "free-form".</t> <t>In section 3.1, change "The enumerated list of "type" values include:" to "The enumerated list of "type" values includes:".</t> <t>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).</t> <t>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:".</t> <t>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:".</t> </list> </t> </section> <section title="Change from REGEXT 05 to REGEXT 06" anchor="change-WG05-to-WG06"> <t>Updates based on the review by Brian Carpenter, that include: <list style="numbers"> <t>In section 1, change the references to RFC 5730 to use links.</t> <t>In section 2, change "(for a temporary migration period)" to "(for a temporary migration period up to server policy)".</t> </list> </t> </section> <section title="Change from REGEXT 06 to REGEXT 07" anchor="change-WG06-to-WG07"> <t><list style="numbers"> <t>Updates based on feedback from Barry Leiba, added recommendations on the characters used for the plain text password. Recommended the use of printable ASCII passwords and if non-ASCII characters are supported, to use a standard for passwords with international characters, such as the OpaqueString PRECIS profile in <xref target="RFC8265"/>.</t> <t>Based on the feedback from Carlos Pignataro, added "[[RFC Editor: Please remove this section.]]" to the "Change History" section.</t> </list></t> </section> <section title="Change from REGEXT 07 to REGEXT 08" anchor="change-WG07-to-WG08"> <t><list style="numbers"> <t>Based on feedback from Eric Vyncke during the IESG review, changed <xref target="RFC8174"/> from the informative references into the normative references.</t> <t>Based on feedback from Alissa Cooper during the IESG review, changed the sentence "One schema is presented here that is the EPP Login Security Extension schema." in section 5 to "The EPP Login Security Extension schema is presented here.".</t> <t>Changed "sever policy" to "server policy" in section 8.</t> <t>Updates based on feedback from Roman Danyliw during the IESG review: <list style="numbers"> <t>Changed "pasword" to "password" in section 1.</t> <t>In section 3.1, added a reference to section 3.3.3 of <xref target="W3C.REC-xmlschema-2-20041028"/> for the format of the "lang" attribute. Added the corresponding section (3.2.6) for the "duration" attribute.</t> <t>Added the "XML" prefix for each reference to "schema" in the introduction of section 5.</t> <t>Added the leading sentence "The Security Considerations of <xref target="RFC5730"/> apply in this document, and this document enhances these considerations." to section 8.</t> <t>Added the sentence 'The possible set of "name" values, by event type, can be discovered / negotiated out of band to EPP or using a separate EPP extension designed to provide server policy information to the client.' to the description of the "name" attribute.</t> <t>Added a description of how to create the <loginSec:app>, <loginSec:tech>, and <loginSec:os> values using ABNF.</t> </list> </t> <t>Updates based on feedback from Alexey Melnikov during the IESG review: <list style="numbers"> <t>Added a description of "whitespace" to section 1.1.</t> <t>Added a description of the usage of the user agent information in section 4.1.</t> </list> </t> <t>Updates based on feedback from Benjamin Kaduk during the IESG review: <list style="numbers"> <t>Added "A newer version of the extension is expected to use an XML namespace with a higher version number than the prior versions." to the first paragraph of section 2.</t> <t>In section 3.1, replace the sentence "There MAY be multiple events returned that provide information for the client to address." with "The <loginSec:event> element is contained in a list of one or more elements in the <loginSec:loginSecData> element, so there MAY be multiple events returned that provide information for the client to address."</t> <t>In section 3.1, for the "exDate" attribute, replace the sentence "At expiry there MAY be an error to connect or MAY be an error to login." with "At expiry there MAY be a connection failure or MAY be a login failure." and a similar change to the following sentence.</t> <t>In section 3.1, replace the description of the "cipher" type and the "tlsProtocol" type.</t> <t>In section 3.1, add a sentence that the "exDate" attribute MUST be set for the "password" type and the "certificate" type.</t> <t>Updates the dates by replacing 2018 with 2020.</t> <t>In section 3.2, update the MUST override sentences for the <loginSec:pw> and the <loginSec:newPw> elements.</t> <t>In section 4.1, update "OPTIONAL client user agent" with "OPTIONAL client user agent information" for the description of the <loginSec:userAgent> element.</t> <t>In section 4.1, replace "MUST only be used" to "MUST only be set" for the <loginSec:pw> and <loginSec:newPw> elements.</t> <t>Updated references of "x86_64 Mac OS X 10.11.6" to "x86_64 Mac OS X 10.15.2".</t> <t>In section 4.1, replace "MUST be included in the response based on both of the following conditions" with "MUST be included in the response when both of the following conditions hold".</t> <t>In section 4.1, update the "exDate" for the "password" security event error to be "2020-03-24T22:00:00.0Z" so that it's prior to the date 2020-03-25 reference previously.</t> <t>In section 8, add the sentence "The server returning of 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.</t> <t>In section 8, change "minimum length beyond 6 characters" to "minimum length greater than 6 characters".</t> <t>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."</t> </list> </t> </list></t> </section> <section title="Change from REGEXT 08 to REGEXT 09" anchor="change-WG08-to-WG08"> <t><list style="numbers"> <t>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."</t> </list></t> </section> <section title="Change from REGEXT 09 to REGEXT 10" anchor="change-WG09-to-WG10"> <t><list style="numbers"> <t>Based on feedback from Benjamin Kaduk, added the sentence "EPP <xref target="RFC5730"/> includes a maximum password length of 16 characters that inhibits implementing stronger password security policies with higher entropy." to the Introduction.</t> </list></t> </section>suggestions: <contact fullname="Martin Casanova"/>, <contact fullname="Scott Hollenbeck"/>, <contact fullname="Barry Leiba"/>, <contact fullname="Patrick Mevzek"/>, and <contact fullname="Joseph Yee"/>.</t> </section> </back><!-- vim: set ts=2 sw=2 expandtab: --></rfc>