draft-ietf-regext-login-security-00.txt   draft-ietf-regext-login-security-01.txt 
Network Working Group J. Gould Network Working Group J. Gould
Internet-Draft M. Pozun Internet-Draft M. Pozun
Intended status: Standards Track VeriSign, Inc. Intended status: Standards Track VeriSign, Inc.
Expires: August 5, 2019 February 1, 2019 Expires: October 11, 2019 April 9, 2019
Login Security Extension for the Extensible Provisioning Protocol (EPP) Login Security Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-login-security-00 draft-ietf-regext-login-security-01
Abstract Abstract
The Extensible Provisioning Protocol (EPP) includes a client The Extensible Provisioning Protocol (EPP) includes a client
authentication scheme that is based on a user identifier and authentication scheme that is based on a user identifier and
password. The structure of the password field is defined by an XML password. The structure of the password field is defined by an XML
Schema data type that specifies minimum and maximum password length Schema data type that specifies minimum and maximum password length
values, but there are no other provisions for password management values, but there are no other provisions for password management
other than changing the password. This document describes an EPP other than changing the password. This document describes an EPP
extension that allows longer passwords to be created and adds extension that allows longer passwords to be created and adds
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 5, 2019. This Internet-Draft will expire on October 11, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 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 . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Event . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Event . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. "[LOGIN-SECURITY]" Password . . . . . . . . . . . . . . . 5 3.2. "[LOGIN-SECURITY]" Password . . . . . . . . . . . . . . . 5
3.3. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 3.3. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6
4.1. EPP <login> Command . . . . . . . . . . . . . . . . . . . 6 4.1. EPP <login> Command . . . . . . . . . . . . . . . . . . . 6
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1. Login Security Extension Schema . . . . . . . . . . . . . 13 5.1. Login Security Extension Schema . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 15 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16
6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16 6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 16 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
8. Security Considerations . . . . . . . . . . . . . . . . . . . 16 8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . 17 10.2. Informative References . . . . . . . . . . . . . . . . . 18
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19
A.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 18 A.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 A.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension for enhancing the security of the EPP login command in EPP extension for enhancing the security of the EPP login command in EPP
RFC 5730. The enhancements include supporting longer passwords (or RFC 5730. The enhancements include supporting longer passwords (or
passphrases) than the 16-character maximum and providing a list of passphrases) than the 16-character maximum and providing a list of
security events in the login response. The password (current and security events in the login response. The password (current and
new) in EPP RFC 5730 can be overridden by the password included in new) in EPP RFC 5730 can be overridden by the password included in
the extension to extend past the 16-character maximum. The security the extension to extend past the 16-character maximum. The security
skipping to change at page 3, line 24 skipping to change at page 3, line 25
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented in order to develop a conforming character case presented in order to develop a conforming
implementation. implementation.
In examples, "C:" represents lines sent by a protocol client and "S:" In examples, "C:" represents lines sent by a protocol client and "S:"
represents lines returned by a protocol server. Indentation and represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element 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-0.3" is used as an abbreviation for "loginSec-0.4" is used as an abbreviation for
"urn:ietf:params:xml:ns:epp:loginSec-0.3". The XML namespace prefix "urn:ietf:params:xml:ns:epp:loginSec-0.4". The XML namespace prefix
"loginSec" is used, but implementations MUST NOT depend on it and "loginSec" is used, but implementations MUST NOT depend on it and
instead employ a proper namespace-aware XML parser and serializer to instead employ a proper namespace-aware XML parser and serializer to
interpret and output the XML documents. interpret and output the XML documents.
2. Migrating to Newer Versions of This Extension 2. Migrating to Newer Versions of This Extension
(Note to RFC Editor: remove this section before publication as an (Note to RFC Editor: remove this section before publication as an
RFC.) RFC.)
Servers which implement this extension SHOULD provide a way for Servers which implement this extension SHOULD provide a way for
skipping to change at page 6, line 32 skipping to change at page 6, line 32
command and response to be used in conjunction with [RFC5730]. command and response to be used in conjunction with [RFC5730].
The EPP <login> command is used to establish a session with an EPP The EPP <login> command is used to establish a session with an EPP
server. This extension overrides the password that is passed with server. This extension overrides the password that is passed with
the [RFC5730] <pw> or the <newPW> element as defined in Section 3.2. the [RFC5730] <pw> or the <newPW> element as defined in Section 3.2.
A <loginSec:loginSec> element is sent along with the [RFC5730] A <loginSec:loginSec> element is sent along with the [RFC5730]
<login> command and MUST contain at least one of the following child <login> command and MUST contain at least one of the following child
elements: elements:
<loginSec:userAgent>: OPTIONAL client user agent that identifies the <loginSec:userAgent>: OPTIONAL client user agent that identifies the
client software and platform used by the server to identify client software, language, and operating system used by the
functional or security constraints, current security issues, and server to identify functional or security constraints, current
potential future functional or security issues for the client. security issues, and potential future functional or security
issues for the client. The <loginSec:userAgent> element contains
the following child elements:
<loginSec:app>: OPTIONAL name of the client application software
with version if available, such as the name of the client SDK
"EPP SDK 1.0.0".
<loginSec:tech>: OPTIONAL technology used for the client
software with version if available, such as "Java 11.0.2".
<loginSec:os>: OPTIONAL client operating system used with
version if available, such as "x86_64 Mac OS X 10.11.6".
<loginSec:pw>: OPTIONAL plain text password that is case sensitive, <loginSec:pw>: OPTIONAL plain text password that is case sensitive,
has a minimum length of 6 characters, and has a maximum length has a minimum length of 6 characters, and has a maximum length
that is up to server policy. All leading and trailing whitespace that is up to server policy. All leading and trailing whitespace
is removed, and all internal contiguous whitespace that includes is removed, and all internal contiguous whitespace that includes
#x9 (tab), #xA (linefeed), #xD (carriage return), and #x20 #x9 (tab), #xA (linefeed), #xD (carriage return), and #x20
(space) is replaced with a single #x20 (space). This element (space) is replaced with a single #x20 (space). This element
MUST only be used if the [RFC5730] <pw> element is set to the MUST only be used if the [RFC5730] <pw> element is set to the
"[LOGIN-SECURITY]" value. "[LOGIN-SECURITY]" value.
<loginSec:newPW>: OPTIONAL plain text new password that is case <loginSec:newPW>: OPTIONAL plain text new password that is case
sensitive, has a minimum length of 6 characters, and has a sensitive, has a minimum length of 6 characters, and has a
skipping to change at page 7, line 24 skipping to change at page 8, line 24
C: <pw>[LOGIN-SECURITY]</pw> C: <pw>[LOGIN-SECURITY]</pw>
C: <options> C: <options>
C: <version>1.0</version> C: <version>1.0</version>
C: <lang>en</lang> C: <lang>en</lang>
C: </options> C: </options>
C: <svcs> C: <svcs>
C: <objURI>urn:ietf:params:xml:ns:obj1</objURI> 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:obj2</objURI>
C: <objURI>urn:ietf:params:xml:ns:obj3</objURI> C: <objURI>urn:ietf:params:xml:ns:obj3</objURI>
C: <svcExtension> C: <svcExtension>
C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-0.3</extURI> C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-0.4</extURI>
C: </svcExtension> C: </svcExtension>
C: </svcs> C: </svcs>
C: </login> C: </login>
C: <extension> C: <extension>
C: <loginSec:loginSec C: <loginSec:loginSec
C: xmlns:loginSec= C: xmlns:loginSec=
C: "urn:ietf:params:xml:ns:epp:loginSec-0.3"> C: "urn:ietf:params:xml:ns:epp:loginSec-0.4">
C: <loginSec:userAgent>EPP SDK/1.0.0 C: <loginSec:userAgent>
C: (Java 1.7.0_15; x86_64 Mac OS X 10.11.6) C: <loginSec:app>EPP SDK 1.0.0</loginSec:app>
C: <loginSec:tech>Java 11.0.2</loginSec:tech>
C: <loginSec:os>x86_64 Mac OS X 10.11.6</loginSec:os>
C: </loginSec:userAgent> C: </loginSec:userAgent>
C: <loginSec:pw>this is a long password</loginSec:pw> C: <loginSec:pw>this is a long password</loginSec:pw>
C: </loginSec:loginSec> C: </loginSec:loginSec>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Example login command that uses the <loginSec:pw> element instead of Example login command that uses the <loginSec:pw> element instead of
the [RFC5730] <pw> element to establish the session, and uses the the [RFC5730] <pw> element to establish the session, and uses the
<loginSec:newPW> element instead of the [RFC5730] <newPW> element to <loginSec:newPW> element instead of the [RFC5730] <newPW> element to
skipping to change at page 8, line 25 skipping to change at page 9, line 25
C: <newPW>[LOGIN-SECURITY]</newPW> C: <newPW>[LOGIN-SECURITY]</newPW>
C: <options> C: <options>
C: <version>1.0</version> C: <version>1.0</version>
C: <lang>en</lang> C: <lang>en</lang>
C: </options> C: </options>
C: <svcs> C: <svcs>
C: <objURI>urn:ietf:params:xml:ns:obj1</objURI> 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:obj2</objURI>
C: <objURI>urn:ietf:params:xml:ns:obj3</objURI> C: <objURI>urn:ietf:params:xml:ns:obj3</objURI>
C: <svcExtension> C: <svcExtension>
C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-0.3</extURI> C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-0.4</extURI>
C: </svcExtension> C: </svcExtension>
C: </svcs> C: </svcs>
C: </login> C: </login>
C: <extension> C: <extension>
C: <loginSec:loginSec C: <loginSec:loginSec
C: xmlns:loginSec= C: xmlns:loginSec=
C: "urn:ietf:params:xml:ns:epp:loginSec-0.3"> C: "urn:ietf:params:xml:ns:epp:loginSec-0.4">
C: <loginSec:pw>this is a long password C: <loginSec:pw>this is a long password
C: </loginSec:pw> C: </loginSec:pw>
C: <loginSec:newPW>new password that is still long C: <loginSec:newPW>new password that is still long
C: </loginSec:newPW> C: </loginSec:newPW>
C: </loginSec:loginSec> C: </loginSec:loginSec>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Example login command that uses the [RFC5730] <pw> element to Example login command that uses the [RFC5730] <pw> element to
skipping to change at page 9, line 24 skipping to change at page 10, line 24
C: <newPW>[LOGIN-SECURITY]</newPW> C: <newPW>[LOGIN-SECURITY]</newPW>
C: <options> C: <options>
C: <version>1.0</version> C: <version>1.0</version>
C: <lang>en</lang> C: <lang>en</lang>
C: </options> C: </options>
C: <svcs> C: <svcs>
C: <objURI>urn:ietf:params:xml:ns:obj1</objURI> 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:obj2</objURI>
C: <objURI>urn:ietf:params:xml:ns:obj3</objURI> C: <objURI>urn:ietf:params:xml:ns:obj3</objURI>
C: <svcExtension> C: <svcExtension>
C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-0.3</extURI> C: <extURI>urn:ietf:params:xml:ns:epp:loginSec-0.4</extURI>
C: </svcExtension> C: </svcExtension>
C: </svcs> C: </svcs>
C: </login> C: </login>
C: <extension> C: <extension>
C: <loginSec:loginSec C: <loginSec:loginSec
C: xmlns:loginSec= C: xmlns:loginSec=
C: "urn:ietf:params:xml:ns:epp:loginSec-0.3"> C: "urn:ietf:params:xml:ns:epp:loginSec-0.4">
C: <loginSec:newPW>new password that is still long C: <loginSec:newPW>new password that is still long
C: </loginSec:newPW> C: </loginSec:newPW>
C: </loginSec:loginSec> C: </loginSec:loginSec>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Upon a completed login command (success or failed), the extension Upon a completed login command (success or failed), the extension
MUST be included in the response based on the following conditions: MUST be included in the response based on the following conditions:
skipping to change at page 10, line 20 skipping to change at page 11, line 20
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <loginSec:loginSecData S: <loginSec:loginSecData
S: xmlns:loginSec= S: xmlns:loginSec=
S: "urn:ietf:params:xml:ns:epp:loginSec-0.3"> S: "urn:ietf:params:xml:ns:epp:loginSec-0.4">
S: <loginSec:event S: <loginSec:event
S: type="password" S: type="password"
S: level="warning" S: level="warning"
S: exDate="2018-04-01T22:00:00.0Z" S: exDate="2018-04-01T22:00:00.0Z"
S: lang="en"> S: lang="en">
S: Password expiring in a week S: Password expiring in a week
S: </loginSec:event> S: </loginSec:event>
S: </loginSec:loginSecData> S: </loginSec:loginSecData>
S: </extension> S: </extension>
S: <trID> S: <trID>
skipping to change at page 11, line 17 skipping to change at page 12, line 17
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="2200"> S: <result code="2200">
S: <msg>Authentication error</msg> S: <msg>Authentication error</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <loginSec:loginSecData S: <loginSec:loginSecData
S: xmlns:loginSec= S: xmlns:loginSec=
S: "urn:ietf:params:xml:ns:epp:loginSec-0.3"> S: "urn:ietf:params:xml:ns:epp:loginSec-0.4">
S: <loginSec:event S: <loginSec:event
S: type="password" S: type="password"
S: level="error" S: level="error"
S: exDate="2018-03-26T22:00:00.0Z"> S: exDate="2018-03-26T22:00:00.0Z">
S: Password has expired S: Password has expired
S: </loginSec:event> S: </loginSec:event>
S: <loginSec:event S: <loginSec:event
S: type="newPW" S: type="newPW"
S: level="error"> S: level="error">
S: New password does not meet complexity requirements S: New password does not meet complexity requirements
skipping to change at page 11, line 50 skipping to change at page 12, line 50
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <loginSec:loginSecData S: <loginSec:loginSecData
S: xmlns:loginSec= S: xmlns:loginSec=
S: "urn:ietf:params:xml:ns:epp:loginSec-0.3"> S: "urn:ietf:params:xml:ns:epp:loginSec-0.4">
S: <loginSec:event S: <loginSec:event
S: type="password" S: type="password"
S: level="warning" S: level="warning"
S: exDate="2018-04-01T22:00:00.0Z" S: exDate="2018-04-01T22:00:00.0Z"
S: lang="en"> S: lang="en">
S: Password expiration soon S: Password expiration soon
S: </loginSec:event> S: </loginSec:event>
S: <loginSec:event S: <loginSec:event
S: type="certificate" S: type="certificate"
S: level="warning" S: level="warning"
skipping to change at page 13, line 20 skipping to change at page 14, line 20
The formal syntax presented here is a complete schema representation The formal syntax presented here is a complete schema representation
of the object mapping suitable for automated validation of EPP XML of the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they 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 are used to note the beginning and ending of the schema for URI
registration purposes. registration purposes.
5.1. Login Security Extension Schema 5.1. Login Security Extension Schema
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:epp:loginSec-0.3" <schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
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-0.3" xmlns:loginSec="urn:ietf:params:xml:ns:epp:loginSec-0.4"
xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ietf:params:xml:ns:epp:loginSec-0.4"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0" />
<annotation> <annotation>
<documentation> <documentation>Extensible Provisioning Protocol v1.0
Extensible Provisioning Protocol v1.0 Login Security Extension Schema.</documentation>
Login Security Extension Schema. </annotation>
</documentation>
</annotation>
<!-- login command extension elements --> <!-- Login command extension elements -->
<element name="loginSec" type="loginSec:loginSecType"/> <element name="loginSec" type="loginSec:loginSecType" />
<!-- <!--
Attributes associated with the login command extension. Attributes associated with the login command extension.
--> -->
<complexType name="loginSecType"> <complexType name="loginSecType">
<sequence> <sequence>
<element name="userAgent" type="token" <element name="userAgent"
minOccurs="0"/> type="loginSec:userAgentType" minOccurs="0" />
<element name="pw" type="loginSec:pwType" <element name="pw"
minOccurs="0"/> type="loginSec:pwType" minOccurs="0" />
<element name="newPW"
<element name="newPW" type="loginSec:pwType" type="loginSec:pwType" minOccurs="0" />
minOccurs="0"/>
</sequence> </sequence>
</complexType>
</complexType>
<simpleType name="pwType"> <simpleType name="pwType">
<restriction base="token"> <restriction base="token">
<minLength value="6"/> <minLength value="6" />
</restriction> </restriction>
</simpleType> </simpleType>
<!-- login response extension elements --> <complexType name="userAgentType">
<element name="loginSecData" type="loginSec:loginSecDataType"/> <sequence>
<element name="app"
type="token" minOccurs="0" />
<element name="tech"
type="token" minOccurs="0" />
<element name="os"
type="token" minOccurs="0" />
</sequence>
</complexType>
<!-- <!-- Login response extension elements -->
Attributes associated with the change. <element name="loginSecData"
--> type="loginSec:loginSecDataType" />
<complexType name="loginSecDataType"> <complexType name="loginSecDataType">
<sequence> <sequence>
<element name="event" type="loginSec:eventType" <element name="event"
minOccurs="1" maxOccurs="unbounded"/> type="loginSec:eventType"
</sequence> minOccurs="1" maxOccurs="unbounded" />
</complexType> </sequence>
</complexType>
<complexType name="eventType"> <!-- Security event element -->
<simpleContent> <complexType name="eventType">
<extension base="normalizedString"> <simpleContent>
<attribute name="type" <extension base="normalizedString">
type="loginSec:typeEnum" use="required"/> <attribute name="type"
<attribute name="name" type="token"/> type="loginSec:typeEnum" use="required" />
<attribute name="level" <attribute name="name"
type="loginSec:levelEnum" use="required"/> type="token" />
<attribute name="exDate" type="dateTime"/> <attribute name="level"
<attribute name="value" type="token"/> type="loginSec:levelEnum" use="required" />
<attribute name="duration" <attribute name="exDate"
type="duration"/> type="dateTime" />
<attribute name="lang" <attribute name="value"
type="language" default="en"/> type="token" />
</extension> <attribute name="duration"
</simpleContent> type="duration" />
</complexType> <attribute name="lang"
type="language" default="en" />
<!-- </extension>
</simpleContent>
</complexType>
<!--
Enumerated list of event types, with extensibility via "custom". Enumerated list of event types, with extensibility via "custom".
--> -->
<simpleType name="typeEnum"> <simpleType name="typeEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="password"/> <enumeration value="password" />
<enumeration value="certificate"/> <enumeration value="certificate" />
<enumeration value="cipher"/> <enumeration value="cipher" />
<enumeration value="tlsProtocol"/> <enumeration value="tlsProtocol" />
<enumeration value="newPW"/> <enumeration value="newPW" />
<enumeration value="stat"/> <enumeration value="stat" />
<enumeration value="custom"/> <enumeration value="custom" />
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
Enumerated list of levels. Enumerated list of levels.
--> -->
<simpleType name="levelEnum"> <simpleType name="levelEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="warning"/> <enumeration value="warning" />
<enumeration value="error"/> <enumeration value="error" />
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
6. IANA Considerations 6. IANA Considerations
6.1. XML Namespace 6.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. The conforming to a registry mechanism described in [RFC3688]. The
following URI assignment is requested of IANA: following URI assignment is requested of IANA:
Registration request for the loginSec namespace: Registration request for the loginSec namespace:
URI: urn:ietf:params:xml:ns:epp:loginSec-0.3 URI: urn:ietf:params:xml:ns:epp:loginSec-0.4
Registrant Contact: IESG Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the loginSec XML schema: Registration request for the loginSec XML schema:
URI: urn:ietf:params:xml:schema:epp:loginSec-0.3 URI: urn:ietf:params:xml:schema:epp:loginSec-0.4
Registrant Contact: IESG Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
6.2. EPP Extension Registry 6.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: details of the registration are as follows:
Name of Extension: "Login Security Extension for the Extensible Name of Extension: "Login Security Extension for the Extensible
skipping to change at page 17, line 10 skipping to change at page 18, line 15
new password that is less than or equal to 16 characters. new password that is less than or equal to 16 characters.
The extension provides an extensible list of login security events to The extension provides an extensible list of login security events to
inform clients of connection and login warnings and errors. inform clients of connection and login warnings and errors.
9. Acknowledgements 9. Acknowledgements
The authors wish to thank the following persons for their feedback The authors wish to thank the following persons for their feedback
and suggestions: and suggestions:
o Patrick Mevzek o Martin Casanova
o Scott Hollenbeck o Scott Hollenbeck
o Patrick Mevzek
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>. editor.org/info/rfc2119>.
skipping to change at page 18, line 43 skipping to change at page 19, line 47
element is not passed. element is not passed.
3. Add "The client SHOULD NOT decrease the security of a new 3. Add "The client SHOULD NOT decrease the security of a new
password by decreasing the length of the current password." along password by decreasing the length of the current password." along
with an example to the "Security Considerations" section. with an example to the "Security Considerations" section.
A.4. Change from 03 to REGEXT 00 A.4. Change from 03 to REGEXT 00
Changed to regext working group draft by changing draft-gould-regext- Changed to regext working group draft by changing draft-gould-regext-
login-security to draft-ietf-regext-login-security. login-security to draft-ietf-regext-login-security.
A.5. Change from REGEXT 00 to REGEXT 01
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.
Authors' Addresses Authors' Addresses
James Gould James Gould
VeriSign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US US
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisign.com URI: http://www.verisign.com
 End of changes. 37 change blocks. 
116 lines changed or deleted 150 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/