idnits 2.17.1 draft-ietf-regext-login-security-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 30, 2019) is 1670 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 842 Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Gould 3 Internet-Draft M. Pozun 4 Intended status: Standards Track VeriSign, Inc. 5 Expires: April 2, 2020 September 30, 2019 7 Login Security Extension for the Extensible Provisioning Protocol (EPP) 8 draft-ietf-regext-login-security-04 10 Abstract 12 The Extensible Provisioning Protocol (EPP) includes a client 13 authentication scheme that is based on a user identifier and 14 password. The structure of the password field is defined by an XML 15 Schema data type that specifies minimum and maximum password length 16 values, but there are no other provisions for password management 17 other than changing the password. This document describes an EPP 18 extension that allows longer passwords to be created and adds 19 additional security features to the EPP login command and response. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on April 2, 2020. 38 Copyright Notice 40 Copyright (c) 2019 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 57 2. Migrating to Newer Versions of This Extension . . . . . . . . 3 58 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 59 3.1. Event . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3.2. "[LOGIN-SECURITY]" Password . . . . . . . . . . . . . . . 5 61 3.3. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 62 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 63 4.1. EPP Command . . . . . . . . . . . . . . . . . . . 6 64 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14 65 5.1. Login Security Extension Schema . . . . . . . . . . . . . 14 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 67 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16 68 6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 69 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 70 7.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 18 71 8. Security Considerations . . . . . . . . . . . . . . . . . . . 18 72 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 73 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 74 10.1. Normative References . . . . . . . . . . . . . . . . . . 19 75 10.2. Informative References . . . . . . . . . . . . . . . . . 19 76 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 20 77 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 20 78 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 20 79 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20 80 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20 81 A.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 20 82 A.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 20 83 A.6. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 21 84 A.7. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 21 85 A.8. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 22 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 88 1. Introduction 90 This document describes an Extensible Provisioning Protocol (EPP) 91 extension for enhancing the security of the EPP login command in EPP 92 RFC 5730. The enhancements include supporting longer passwords (or 93 passphrases) than the 16-character maximum and providing a list of 94 security events in the login response. The password (current and 95 new) in EPP RFC 5730 can be overridden by the password included in 96 the extension to extend past the 16-character maximum. The security 97 events supported include: password expiry, client certificate expiry, 98 insecure cipher, insecure TLS protocol, new pasword complexity, login 99 security statistical warning, and a custom event. The attributes 100 supported by the security events include identifying the event type 101 or sub-type, indicating the security level of warning or error, a 102 future or past-due expiration date, the value that resulted in the 103 event, the duration of the statistical event, and a free-form 104 description with an optional language. 106 1.1. Conventions Used in This Document 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in RFC 2119 [RFC2119]. 112 XML is case sensitive. Unless stated otherwise, XML specifications 113 and examples provided in this document MUST be interpreted in the 114 character case presented in order to develop a conforming 115 implementation. 117 In examples, "C:" represents lines sent by a protocol client and "S:" 118 represents lines returned by a protocol server. Indentation and 119 white space in examples are provided only to illustrate element 120 relationships and are not a REQUIRED feature of this protocol. 122 "loginSec-1.0" is used as an abbreviation for 123 "urn:ietf:params:xml:ns:epp:loginSec-1.0". The XML namespace prefix 124 "loginSec" is used, but implementations MUST NOT depend on it and 125 instead employ a proper namespace-aware XML parser and serializer to 126 interpret and output the XML documents. 128 2. Migrating to Newer Versions of This Extension 130 (Note to RFC Editor: remove this section before publication as an 131 RFC.) 133 Servers which implement this extension SHOULD provide a way for 134 clients to progressively update their implementations when a new 135 version of the extension is deployed. 137 Servers SHOULD (for a temporary migration period) provide support for 138 older versions of the extension in parallel to the newest version, 139 and allow clients to select their preferred version via the 140 element of the command. 142 If a client requests multiple versions of the extension at login, 143 then, when preparing responses to commands which do not include 144 extension elements, the server SHOULD only include extension elements 145 in the namespace of the newest version of the extension requested by 146 the client. 148 When preparing responses to commands which do include extension 149 elements, the server SHOULD only include extension elements for the 150 extension versions present in the command. 152 3. Object Attributes 154 This extension adds additional elements to [RFC5730] login command 155 and response. Only those new elements are described here. 157 3.1. Event 159 A security event, using the element, represents 160 either a warning or error identified by the server after the client 161 has connected and submitted the login command. There MAY be multiple 162 events returned that provides information for the client to address. 163 The MAY include a free form description. All of the 164 security events use a consistent set of attributes, where the exact 165 set of applicable attributes is based on the event type. The 166 supported set of element attributes include: 168 "type": A REQUIRED attribute that defines the type of security 169 event. The enumerated list of "type" values include: 171 "password": Identifies a password expiry event, where the 172 password expires in the future or has expired based on the 173 "exDate" date and time. 174 "certificate": Identifies a client certificate expiry event, 175 where the client certificate will expire at the "exDate" date 176 and time. 177 "cipher": Identifies the use of an insecure or deprecated TLS 178 cipher suite. 179 "tlsProtocol": Identifies the use of an insecure or deprecated 180 TLS protocol. 181 "newPW": The new password does not meet the server password 182 complexity requirements. 183 "stat": Provides a login security statistical warning that MUST 184 set the "name" attribute to the name of the statistic sub- 185 type. 186 "custom": Custom event type that MUST set the "name" attribute 187 with the custom event type name. 188 "name": Used to define a sub-type when the "type" attribute is not 189 "custom" or the full type name when the "type" attribute is 190 "custom". The "name" attribute MUST be set when the "type" 191 attribute is "stat" or "custom". 193 "level": Defines the level of the event as either "warning" for a 194 warning event that needs action, or "error" for an error event 195 that requires immediate action. 196 "exDate": Contains the date and time that a "warning" level has or 197 will become an "error" level. At expiry there MAY be an error to 198 connect or MAY be an error to login. An example is an expired 199 certificate that will result in an error to connect or an expired 200 password that may result in a failed login. 201 "value": Identifies the value that resulted in the login security 202 event. An example is the negotiated insecure cipher suite or the 203 negotiated insecure TLS protocol. 204 "duration": Defines the duration that a statistical event is 205 associated with, ending when the login command was received. The 206 format of the duration is defined by the duration primitive 207 datatype in [W3C.REC-xmlschema-2-20041028]. 208 "lang": Identifies the language of the free form description if the 209 negotiated language is something other than the default value of 210 "en" (English). 212 Example login security event for a password expiring in a week: 214 219 Password expiration soon 220 222 Example login security event for identifying 100 failed logins over 223 the last day, using the "stat" sub-type of "failedLogins": 225 231 Excessive invalid daily logins 232 234 3.2. "[LOGIN-SECURITY]" Password 236 The element MUST override the [RFC5730] element 237 only if the contains the predefined value of "[LOGIN-SECURITY]", 238 which is a constant value for the server to use the 239 element for the password. Similarly, the element 240 MUST override the [RFC5730] element only if the 241 contains the predefined value of "[LOGIN-SECURITY]", which is a 242 constant value for the server to use the element for 243 the new password. The "[LOGIN-SECURITY]" pre-defined string MUST be 244 supported by the server for the client to explicitly indicate to the 245 server whether to use element in place of the [RFC5730] 246 element or to use the in place of the [RFC5730] 247 element. The server MUST NOT allow the client to set the 248 password to the value "[LOGIN-SECURITY]". 250 3.3. Dates and Times 252 Date and time attribute values MUST be represented in Universal 253 Coordinated Time (UTC) using the Gregorian calendar. The extended 254 date-time form using upper case "T" and "Z" characters defined in 255 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 256 values, as XML Schema does not support truncated date-time forms or 257 lower case "T" and "Z" characters. 259 4. EPP Command Mapping 261 A detailed description of the EPP syntax and semantics can be found 262 in the EPP core protocol specification [RFC5730]. 264 4.1. EPP Command 266 This extension defines additional elements to extend the EPP 267 command and response to be used in conjunction with [RFC5730]. 269 The EPP command is used to establish a session with an EPP 270 server. This extension overrides the password that is passed with 271 the [RFC5730] or the element as defined in Section 3.2. 272 A element is sent along with the [RFC5730] 273 command and MUST contain at least one of the following child 274 elements: 276 : OPTIONAL client user agent that identifies the 277 client application software, technology, and operating system 278 used by the server to identify functional or security 279 constraints, current security issues, and potential future 280 functional or security issues for the client. The 281 element MUST contain at least one of the 282 following child elements: 284 : OPTIONAL name of the client application software 285 with version if available, such as the name of the client SDK 286 "EPP SDK 1.0.0". 288 : OPTIONAL technology used for the client 289 software with version if available, such as "Java 11.0.2". 290 : OPTIONAL client operating system used with 291 version if available, such as "x86_64 Mac OS X 10.11.6". 292 : OPTIONAL plain text password that is case sensitive, 293 has a minimum length of 6 characters, and has a maximum length 294 that is up to server policy. All leading and trailing whitespace 295 is removed, and all internal contiguous whitespace that includes 296 #x9 (tab), #xA (linefeed), #xD (carriage return), and #x20 297 (space) is replaced with a single #x20 (space). This element 298 MUST only be used if the [RFC5730] element is set to the 299 "[LOGIN-SECURITY]" value. 300 : OPTIONAL plain text new password that is case 301 sensitive, has a minimum length of 6 characters, and has a 302 maximum length that is up to server policy. All leading and 303 trailing whitespace is removed, and all internal contiguous 304 whitespace that includes #x9 (tab), #xA (linefeed), #xD (carriage 305 return), and #x20 (space) is replaced with a single #x20 (space). 306 This element MUST only be used if the [RFC5730] element 307 is set to the "[LOGIN-SECURITY]" value. 309 Example login command that uses the element instead of 310 the [RFC5730] element to establish the session and includes the 311 element: 313 C: 314 C: 315 C: 316 C: 317 C: ClientX 318 C: [LOGIN-SECURITY] 319 C: 320 C: 1.0 321 C: en 322 C: 323 C: 324 C: urn:ietf:params:xml:ns:obj1 325 C: urn:ietf:params:xml:ns:obj2 326 C: urn:ietf:params:xml:ns:obj3 327 C: 328 C: urn:ietf:params:xml:ns:epp:loginSec-1.0 329 C: 330 C: 331 C: 332 C: 333 C: 336 C: 337 C: EPP SDK 1.0.0 338 C: Java 11.0.2 339 C: x86_64 Mac OS X 10.11.6 340 C: 341 C: this is a long password 342 C: 343 C: 344 C: ABC-12345 345 C: 346 C: 347 Example login command that uses the element instead of 348 the [RFC5730] element to establish the session, and uses the 349 element instead of the [RFC5730] element to 350 set the new password: 352 C: 353 C: 354 C: 355 C: 356 C: ClientX 357 C: [LOGIN-SECURITY] 358 C: [LOGIN-SECURITY] 359 C: 360 C: 1.0 361 C: en 362 C: 363 C: 364 C: urn:ietf:params:xml:ns:obj1 365 C: urn:ietf:params:xml:ns:obj2 366 C: urn:ietf:params:xml:ns:obj3 367 C: 368 C: urn:ietf:params:xml:ns:epp:loginSec-1.0 369 C: 370 C: 371 C: 372 C: 373 C: 376 C: this is a long password 377 C: 378 C: new password that is still long 379 C: 380 C: 381 C: 382 C: ABC-12345 383 C: 384 C: 385 Example login command that uses the [RFC5730] element to 386 establish the session, and uses the element instead 387 of the [RFC5730] element to set the new password: 389 C: 390 C: 391 C: 392 C: 393 C: ClientX 394 C: shortpassword 395 C: [LOGIN-SECURITY] 396 C: 397 C: 1.0 398 C: en 399 C: 400 C: 401 C: urn:ietf:params:xml:ns:obj1 402 C: urn:ietf:params:xml:ns:obj2 403 C: urn:ietf:params:xml:ns:obj3 404 C: 405 C: urn:ietf:params:xml:ns:epp:loginSec-1.0 406 C: 407 C: 408 C: 409 C: 410 C: 413 C: new password that is still long 414 C: 415 C: 416 C: 417 C: ABC-12345 418 C: 419 C: 421 Upon a completed login command (success or failed), the extension 422 MUST be included in the response based on both of the following 423 conditions: 425 Client supports extension: The client supports the extension based 426 on the element of the command. 427 At least one login security event: The server has identified at 428 least one login security event to communicate to the client. 430 The extension to the EPP response uses the 431 element that contains the following child elements: 433 : One or more elements defined in 434 Section 3.1. 436 Example EPP response to a successful login command where the password 437 will expire in a week: 439 S: 440 S: 441 S: 442 S: 443 S: Command completed successfully 444 S: 445 S: 446 S: 449 S: 454 S: Password expiring in a week 455 S: 456 S: 457 S: 458 S: 459 S: ABC-12345 460 S: 54321-XYZ 461 S: 462 S: 463 S: 464 Example EPP response to a failed login command where the password has 465 expired and the new password does not meet the server complexity 466 requirements: 468 S: 469 S: 470 S: 471 S: 472 S: Authentication error 473 S: 474 S: 475 S: 478 S: 482 S: Password has expired 483 S: 484 S: 487 S: New password does not meet complexity requirements 488 S: 489 S: 490 S: 491 S: 492 S: ABC-12345 493 S: 54321-XYZ 494 S: 495 S: 496 S: 498 Example EPP response to a successful login command where there is a 499 set of login security events: 501 S: 502 S: 503 S: 504 S: 505 S: Command completed successfully 506 S: 507 S: 508 S: 511 S: 516 S: Password expiration soon 517 S: 518 S: 522 S: 526 S: Non-PFS Cipher negotiated 527 S: 528 S: 532 S: Insecure TLS protocol negotiated 533 S: 534 S: 540 S: Excessive invalid daily logins 541 S: 542 S: 546 S: A custom login security event occured 547 S: 548 S: 549 S: 550 S: 551 S: ABC-12345 552 S: 54321-XYZ 553 S: 554 S: 555 S: 557 5. Formal Syntax 559 One schema is presented here that is the EPP Login Security Extension 560 schema. 562 The formal syntax presented here is a complete schema representation 563 of the object mapping suitable for automated validation of EPP XML 564 instances. The BEGIN and END tags are not part of the schema; they 565 are used to note the beginning and ending of the schema for URI 566 registration purposes. 568 5.1. Login Security Extension Schema 570 BEGIN 571 572 578 581 582 583 584 Extensible Provisioning Protocol v1.0 585 Login Security Extension Schema. 586 587 588 589 592 593 594 596 598 600 601 602 603 604 606 607 608 609 610 611 613 615 617 618 619 621 623 624 626 627 628 629 631 632 633 636 637 638 639 640 641 642 644 646 648 650 652 655 657 658 659 660 663 664 665 666 667 668 669 670 671 672 673 674 677 678 679 680 681 682 683 686 687 END 689 6. IANA Considerations 691 6.1. XML Namespace 693 This document uses URNs to describe XML namespaces and XML schemas 694 conforming to a registry mechanism described in [RFC3688]. The 695 following URI assignment is requested of IANA: 697 Registration request for the loginSec namespace: 699 URI: urn:ietf:params:xml:ns:epp:loginSec-1.0 700 Registrant Contact: IESG 701 XML: None. Namespace URIs do not represent an XML specification. 703 Registration request for the loginSec XML schema: 705 URI: urn:ietf:params:xml:schema:epp:loginSec-1.0 706 Registrant Contact: IESG 707 XML: See the "Formal Syntax" section of this document. 709 6.2. EPP Extension Registry 711 The EPP extension described in this document should be registered by 712 the IANA in the EPP Extension Registry described in [RFC7451]. The 713 details of the registration are as follows: 715 Name of Extension: "Login Security Extension for the Extensible 716 Provisioning Protocol (EPP)" 718 Document status: Standards Track 720 Reference: (insert reference to RFC version of this document) 722 Registrant Name and Email Address: IESG, 724 TLDs: Any 726 IPR Disclosure: None 728 Status: Active 730 Notes: None 732 7. Implementation Status 734 Note to RFC Editor: Please remove this section and the reference to 735 RFC 7942 [RFC7942] before publication. 737 This section records the status of known implementations of the 738 protocol defined by this specification at the time of posting of this 739 Internet-Draft, and is based on a proposal described in RFC 7942 740 [RFC7942]. The description of implementations in this section is 741 intended to assist the IETF in its decision processes in progressing 742 drafts to RFCs. Please note that the listing of any individual 743 implementation here does not imply endorsement by the IETF. 744 Furthermore, no effort has been spent to verify the information 745 presented here that was supplied by IETF contributors. This is not 746 intended as, and must not be construed to be, a catalog of available 747 implementations or their features. Readers are advised to note that 748 other implementations may exist. 750 According to RFC 7942 [RFC7942], "this will allow reviewers and 751 working groups to assign due consideration to documents that have the 752 benefit of running code, which may serve as evidence of valuable 753 experimentation and feedback that have made the implemented protocols 754 more mature. It is up to the individual working groups to use this 755 information as they see fit". 757 7.1. Verisign EPP SDK 759 Organization: Verisign Inc. 761 Name: Verisign EPP SDK 763 Description: The Verisign EPP SDK includes both a full client 764 implementation and a full server stub implementation of draft-ietf- 765 regext-login-security. 767 Level of maturity: Development 769 Coverage: All aspects of the protocol are implemented. 771 Licensing: GNU Lesser General Public License 773 Contact: jgould@verisign.com 775 URL: https://www.verisign.com/en_US/channel-resources/domain- 776 registry-products/epp-sdks 778 8. Security Considerations 780 The extension leaves the password ( element) and new password 781 ( element) minimum length beyond 6 characters and the maximum 782 length up to sever policy. The server SHOULD enforce minimum and 783 maximum length requirements that are appropriate for their operating 784 environment. One example of a guideline for password length policies 785 can be found in section 5 of NIST Special Publication 800-63B [1]. 787 The client SHOULD NOT decrease the security of a new password by 788 decreasing the length of the current password. For example, a client 789 with a 20 character password set using the extension, should not use 790 the login command in [RFC5730] without using the extension, to set a 791 new password that is less than or equal to 16 characters. 793 The extension provides an extensible list of login security events to 794 inform clients of connection and login warnings and errors. 796 9. Acknowledgements 798 The authors wish to thank the following persons for their feedback 799 and suggestions: 801 o Martin Casanova 802 o Scott Hollenbeck 803 o Patrick Mevzek 804 o Joseph Yee 806 10. References 808 10.1. Normative References 810 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 811 Requirement Levels", BCP 14, RFC 2119, 812 DOI 10.17487/RFC2119, March 1997, 813 . 815 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 816 DOI 10.17487/RFC3688, January 2004, 817 . 819 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 820 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 821 . 823 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 824 Code: The Implementation Status Section", BCP 205, 825 RFC 7942, DOI 10.17487/RFC7942, July 2016, 826 . 828 [W3C.REC-xmlschema-2-20041028] 829 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 830 Second Edition", World Wide Web Consortium Recommendation 831 REC-xmlschema-2-20041028, October 2004, 832 . 834 10.2. Informative References 836 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 837 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 838 February 2015, . 840 10.3. URIs 842 [1] https://pages.nist.gov/800-63-3/sp800-63b.html 844 Appendix A. Change History 846 A.1. Change from 00 to 01 848 1. Based on the feedback from Patrick Mevzek and a proposal from 849 Scott Hollenbeck, changed the minimum length of the password from 850 8 to 6, revised the description of the password, and added text 851 in the Security Considerations section for the server password 852 length policy. 854 A.2. Change from 01 to 02 856 1. Changed the XML namespace from urn:ietf:params:xml:ns:loginSec- 857 0.3 to urn:ietf:params:xml:ns:epp:loginSec-0.3, and changed the 858 XML schema registration from urn:ietf:params:xml:ns:loginSec-0.3 859 to urn:ietf:params:xml:schema:epp:loginSec-0.3 based on a request 860 from IANA with draft-ietf-regext-allocation-token. 862 A.3. Change from 02 to 03 864 1. Updates based on the review by Patrick Mevzek, that include: 866 1. Fix the inconsistent case for newPW, that required a global 867 change in the draft text and an update to the XML schema to 868 "urn:ietf:params:xml:ns:loginSec-0.3". 869 2. Changed "contains the following child elements" to "MUST 870 contain at least one of the following child elements", 871 section "EPP Command" to ensure that an empty 872 element is not passed. 873 3. Add "The client SHOULD NOT decrease the security of a new 874 password by decreasing the length of the current password." 875 along with an example to the "Security Considerations" 876 section. 878 A.4. Change from 03 to REGEXT 00 880 1. Changed to regext working group draft by changing draft-gould- 881 regext-login-security to draft-ietf-regext-login-security. 883 A.5. Change from REGEXT 00 to REGEXT 01 885 1. Changed the element to be structured with 886 the , , and sub- 887 elements. This was based on the feedback from Martin Casanova. 889 This resulted in the need to change the XML namespace from 890 urn:ietf:params:xml:ns:epp:loginSec-0.3 to 891 urn:ietf:params:xml:ns:epp:loginSec-0.4. 893 A.6. Change from REGEXT 01 to REGEXT 02 895 1. Updated the Implementation Status section from "TBD" to include 896 the Verisign EPP SDK implementation. 898 A.7. Change from REGEXT 02 to REGEXT 03 900 1. Revised the description of the "duration" attribute to clarify 901 that it ends when the login command was received and to clarify 902 the format, based on the feedback from Martin Casanova. 903 2. Revised the sentence 'Upon a completed login command (success or 904 failed), the extension MUST be included in the response based on 905 the following conditions:' to 'Upon a completed login command 906 (success or failed), the extension MUST be included in the 907 response based on both of the following conditions:' based on the 908 feedback from Patrick Mevzek. 909 3. Updates based on the review by Joseph Yee, that include: 911 1. Revised the description of the "name" 912 attribute read 'Used to define a sub-type when the "type" 913 attribute is not "custom" or the full type name when the 914 "type" attribute is "custom"'. The definition of the "stat" 915 type was updated to 'Provides a login security statistical 916 warning that MUST set the "name" attribute to the name of the 917 statistic.' 918 2. Added the following sentence 'The server MUST NOT allow the 919 client to set the password to the value "[LOGIN-SECURITY]".' 920 to address the corner case where the constant is used as the 921 password. 922 3. Revised the description of the element 923 to read 'The element MUST contain at 924 least one of the following child elements:'. 925 4. Revised the description of the to match the 926 child elements that can be passed, by changing "client software" 927 to "client application software" and change "language" to 928 "technology". 929 5. Changed the XML namespace from 930 urn:ietf:params:xml:ns:epp:loginSec-0.4 to 931 urn:ietf:params:xml:ns:epp:loginSec-1.0. 933 A.8. Change from REGEXT 03 to REGEXT 04 935 Updates based on the review by Joseph Yee, that include: 937 1. Update the definition of the "stat" security event type to 938 reference sub-type to match the language for the "name" 939 attribute. 940 2. Added the sentence 'The "name" attribute MUST be set when the 941 "type" attribute is "stat" or "custom".' to the definition of the 942 "name" attribute for clarity. 943 3. Update the definition of the "userAgentType" in the XML schema to 944 require at least one sub-element using a element. 946 Authors' Addresses 948 James Gould 949 VeriSign, Inc. 950 12061 Bluemont Way 951 Reston, VA 20190 952 US 954 Email: jgould@verisign.com 955 URI: http://www.verisign.com 957 Matthew Pozun 958 VeriSign, Inc. 959 12061 Bluemont Way 960 Reston, VA 20190 961 US 963 Email: mpozun@verisign.com 964 URI: http://www.verisign.com