idnits 2.17.1 draft-ietf-regext-login-security-07.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 (December 6, 2019) is 1601 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 861 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: June 8, 2020 December 6, 2019 7 Login Security Extension for the Extensible Provisioning Protocol (EPP) 8 draft-ietf-regext-login-security-07 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 June 8, 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 . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . 21 82 A.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 21 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 A.9. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 22 87 A.10. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 23 88 A.11. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 23 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 91 1. Introduction 93 This document describes an Extensible Provisioning Protocol (EPP) 94 extension for enhancing the security of the EPP login command in EPP 95 [RFC5730]. The enhancements include supporting longer passwords (or 96 passphrases) than the 16-character maximum and providing a list of 97 security events in the login response. The password (current and 98 new) in EPP [RFC5730] can be overridden by the password included in 99 the extension to extend past the 16-character maximum. The security 100 events supported include: password expiry, client certificate expiry, 101 insecure cipher, insecure TLS protocol, new pasword complexity, login 102 security statistical warning, and a custom event. The attributes 103 supported by the security events include identifying the event type 104 or sub-type, indicating the security level of warning or error, a 105 future or past-due expiration date, the value that resulted in the 106 event, the duration of the statistical event, and a free-form 107 description with an optional language. 109 1.1. Conventions Used in This Document 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 113 "OPTIONAL" in this document are to be interpreted as described in BCP 114 14 [RFC2119] [RFC8174] when, and only when, they appear in all 115 capitals, as shown here. 117 XML is case sensitive. Unless stated otherwise, XML specifications 118 and examples provided in this document MUST be interpreted in the 119 character case presented in order to develop a conforming 120 implementation. 122 In examples, "C:" represents lines sent by a protocol client and "S:" 123 represents lines returned by a protocol server. Indentation and 124 white space in examples are provided only to illustrate element 125 relationships and are not a required feature of this protocol. 127 "loginSec-1.0" is used as an abbreviation for 128 "urn:ietf:params:xml:ns:epp:loginSec-1.0". The XML namespace prefix 129 "loginSec" is used, but implementations MUST NOT depend on it and 130 instead employ a proper namespace-aware XML parser and serializer to 131 interpret and output the XML documents. 133 2. Migrating to Newer Versions of This Extension 135 Servers which implement this extension SHOULD provide a way for 136 clients to progressively update their implementations when a new 137 version of the extension is deployed. 139 Servers SHOULD (for a temporary migration period up to server policy) 140 provide support for older versions of the extension in parallel to 141 the newest version, and allow clients to select their preferred 142 version via the element of the command. 144 If a client requests multiple versions of the extension at login, 145 then, when preparing responses to commands which do not include 146 extension elements, the server SHOULD only include extension elements 147 in the namespace of the newest version of the extension requested by 148 the client. 150 When preparing responses to commands which do include extension 151 elements, the server SHOULD only include extension elements for the 152 extension versions present in the command. 154 3. Object Attributes 156 This extension adds additional elements to [RFC5730] login command 157 and response. Only those new elements are described here. 159 3.1. Event 161 A security event, using the element, represents 162 either a warning or error identified by the server after the client 163 has connected and submitted the login command. There MAY be multiple 164 events returned that provide information for the client to address. 165 The MAY include a free-form description. All of the 166 security events use a consistent set of attributes, where the exact 167 set of applicable attributes is based on the event type. The 168 supported set of element attributes include: 170 "type": A REQUIRED attribute that defines the type of security 171 event. The enumerated list of "type" values includes: 173 "password": Identifies a password expiry event, where the 174 password expires in the future or has expired based on the 175 "exDate" date and time. 176 "certificate": Identifies a client certificate expiry event, 177 where the client certificate will expire at the "exDate" date 178 and time. 179 "cipher": Identifies the use of an insecure or deprecated TLS 180 cipher suite. 181 "tlsProtocol": Identifies the use of an insecure or deprecated 182 TLS protocol. 183 "newPW": The new password does not meet the server password 184 complexity requirements. 185 "stat": Provides a login security statistical warning that MUST 186 set the "name" attribute to the name of the statistic sub- 187 type. 188 "custom": Custom event type that MUST set the "name" attribute 189 with the custom event type name. 191 "name": Used to define a sub-type when the "type" attribute is not 192 "custom" or the full type name when the "type" attribute is 193 "custom". The "name" attribute MUST be set when the "type" 194 attribute is "stat" or "custom". 195 "level": Defines the level of the event as either "warning" for a 196 warning event that needs action, or "error" for an error event 197 that requires immediate action. 198 "exDate": Contains the date and time that a "warning" level has or 199 will become an "error" level. At expiry there MAY be an error to 200 connect or MAY be an error to login. An example is an expired 201 certificate that will result in an error to connect or an expired 202 password that may result in a failed login. 203 "value": Identifies the value that resulted in the login security 204 event. An example is the negotiated insecure cipher suite or the 205 negotiated insecure TLS protocol. 206 "duration": Defines the duration that a statistical event is 207 associated with, ending when the login command was received. The 208 format of the duration is defined by the duration primitive 209 datatype in [W3C.REC-xmlschema-2-20041028]. 210 "lang": Identifies the negotiated language of the free-form 211 description. The default is "en" (English). 213 Example login security event for password expiration, where the 214 current date is 2018-03-25: 216 221 Password expiration soon 222 224 Example login security event for identifying 100 failed logins over 225 the last day, using the "stat" sub-type of "failedLogins": 227 233 Excessive invalid daily logins 234 236 3.2. "[LOGIN-SECURITY]" Password 238 The element MUST override the [RFC5730] element 239 only if the contains the predefined value of "[LOGIN-SECURITY]", 240 which is a constant value for the server to use the 241 element for the password. Similarly, the element 242 MUST override the [RFC5730] element only if the 243 contains the predefined value of "[LOGIN-SECURITY]", which is a 244 constant value for the server to use the element for 245 the new password. The "[LOGIN-SECURITY]" pre-defined string MUST be 246 supported by the server for the client to explicitly indicate to the 247 server whether to use element in place of the [RFC5730] 248 element or to use the in place of the [RFC5730] 249 element. The server MUST NOT allow the client to set the 250 password to the value "[LOGIN-SECURITY]". 252 3.3. Dates and Times 254 Date and time attribute values MUST be represented in Universal 255 Coordinated Time (UTC) using the Gregorian calendar. The extended 256 date-time form using upper case "T" and "Z" characters defined in 257 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 258 values, as XML Schema does not support truncated date-time forms or 259 lower case "T" and "Z" characters. 261 4. EPP Command Mapping 263 A detailed description of the EPP syntax and semantics can be found 264 in the EPP core protocol specification [RFC5730]. 266 4.1. EPP Command 268 This extension defines additional elements to extend the EPP 269 command and response to be used in conjunction with [RFC5730]. 271 The EPP command is used to establish a session with an EPP 272 server. This extension overrides the password that is passed with 273 the [RFC5730] or the element as defined in Section 3.2. 274 A element is sent along with the [RFC5730] 275 command and MUST contain at least one of the following child 276 elements: 278 : OPTIONAL client user agent that identifies the 279 client application software, technology, and operating system 280 used by the server to identify functional or security 281 constraints, current security issues, and potential future 282 functional or security issues for the client. The 283 element MUST contain at least one of the 284 following child elements: 286 : OPTIONAL name of the client application software 287 with version if available, such as the name of the client SDK 288 "EPP SDK 1.0.0". 289 : OPTIONAL technology used for the client 290 software with version if available, such as "Java 11.0.2". 291 : OPTIONAL client operating system used with 292 version if available, such as "x86_64 Mac OS X 10.11.6". 293 : OPTIONAL plain text password that is case sensitive, 294 has a minimum length of 6 characters, and has a maximum length 295 that is up to server policy. All leading and trailing whitespace 296 is removed, and all internal contiguous whitespace that includes 297 #x9 (tab), #xA (linefeed), #xD (carriage return), and #x20 298 (space) is replaced with a single #x20 (space). This element 299 MUST only be used if the [RFC5730] element is set to the 300 "[LOGIN-SECURITY]" value. 301 : OPTIONAL plain text new password that is case 302 sensitive, has a minimum length of 6 characters, and has a 303 maximum length that is up to server policy. All leading and 304 trailing whitespace is removed, and all internal contiguous 305 whitespace that includes #x9 (tab), #xA (linefeed), #xD (carriage 306 return), and #x20 (space) is replaced with a single #x20 (space). 307 This element MUST only be used if the [RFC5730] element 308 is set to the "[LOGIN-SECURITY]" value. 310 It is recommended that the plain text password in the 311 and elements use printable ASCII characters #x20 312 (space) - #x7E (~), with high entropy, such as 128 bits. If non- 313 ASCII characters are supported with the plain text password, then use 314 a standard for passwords with international characters, such as the 315 OpaqueString PRECIS profile in [RFC8265]. 317 Example login command that uses the element instead of 318 the [RFC5730] element to establish the session and includes the 319 element: 321 C: 322 C: 323 C: 324 C: 325 C: ClientX 326 C: [LOGIN-SECURITY] 327 C: 328 C: 1.0 329 C: en 330 C: 331 C: 332 C: urn:ietf:params:xml:ns:obj1 333 C: urn:ietf:params:xml:ns:obj2 334 C: urn:ietf:params:xml:ns:obj3 335 C: 336 C: urn:ietf:params:xml:ns:epp:loginSec-1.0 337 C: 338 C: 339 C: 340 C: 341 C: 344 C: 345 C: EPP SDK 1.0.0 346 C: Java 11.0.2 347 C: x86_64 Mac OS X 10.11.6 348 C: 349 C: this is a long password 350 C: 351 C: 352 C: ABC-12345 353 C: 354 C: 355 Example login command that uses the element instead of 356 the [RFC5730] element to establish the session, and uses the 357 element instead of the [RFC5730] element to 358 set the new password: 360 C: 361 C: 362 C: 363 C: 364 C: ClientX 365 C: [LOGIN-SECURITY] 366 C: [LOGIN-SECURITY] 367 C: 368 C: 1.0 369 C: en 370 C: 371 C: 372 C: urn:ietf:params:xml:ns:obj1 373 C: urn:ietf:params:xml:ns:obj2 374 C: urn:ietf:params:xml:ns:obj3 375 C: 376 C: urn:ietf:params:xml:ns:epp:loginSec-1.0 377 C: 378 C: 379 C: 380 C: 381 C: 384 C: this is a long password 385 C: 386 C: new password that is still long 387 C: 388 C: 389 C: 390 C: ABC-12345 391 C: 392 C: 393 Example login command that uses the [RFC5730] element to 394 establish the session, and uses the element instead 395 of the [RFC5730] element to set the new password: 397 C: 398 C: 399 C: 400 C: 401 C: ClientX 402 C: shortpassword 403 C: [LOGIN-SECURITY] 404 C: 405 C: 1.0 406 C: en 407 C: 408 C: 409 C: urn:ietf:params:xml:ns:obj1 410 C: urn:ietf:params:xml:ns:obj2 411 C: urn:ietf:params:xml:ns:obj3 412 C: 413 C: urn:ietf:params:xml:ns:epp:loginSec-1.0 414 C: 415 C: 416 C: 417 C: 418 C: 421 C: new password that is still long 422 C: 423 C: 424 C: 425 C: ABC-12345 426 C: 427 C: 429 Upon a completed login command (success or failed), the extension 430 MUST be included in the response based on both of the following 431 conditions: 433 Client supports extension: The client supports the extension based 434 on the element of the command. 435 At least one login security event: The server has identified at 436 least one login security event to communicate to the client. 438 The extension to the EPP response uses the 439 element that contains the following child elements: 441 : One or more elements defined in 442 Section 3.1. 444 Example EPP response to a successful login command on 2018-03-25, 445 where the password will expire in a week: 447 S: 448 S: 449 S: 450 S: 451 S: Command completed successfully 452 S: 453 S: 454 S: 457 S: 462 S: Password expiring in a week 463 S: 464 S: 465 S: 466 S: 467 S: ABC-12345 468 S: 54321-XYZ 469 S: 470 S: 471 S: 472 Example EPP response to a failed login command where the password has 473 expired and the new password does not meet the server complexity 474 requirements: 476 S: 477 S: 478 S: 479 S: 480 S: Authentication error 481 S: 482 S: 483 S: 486 S: 490 S: Password has expired 491 S: 492 S: 495 S: New password does not meet complexity requirements 496 S: 497 S: 498 S: 499 S: 500 S: ABC-12345 501 S: 54321-XYZ 502 S: 503 S: 504 S: 506 Example EPP response to a successful login command where there is a 507 set of login security events: 509 S: 510 S: 511 S: 512 S: 513 S: Command completed successfully 514 S: 515 S: 516 S: 519 S: 524 S: Password expiration soon 525 S: 526 S: 530 S: 534 S: Non-PFS Cipher negotiated 535 S: 536 S: 540 S: Insecure TLS protocol negotiated 541 S: 542 S: 548 S: Excessive invalid daily logins 549 S: 550 S: 554 S: A custom login security event occured 555 S: 556 S: 557 S: 558 S: 559 S: ABC-12345 560 S: 54321-XYZ 561 S: 562 S: 563 S: 565 5. Formal Syntax 567 One schema is presented here that is the EPP Login Security Extension 568 schema. 570 The formal syntax presented here is a complete schema representation 571 of the object mapping suitable for automated validation of EPP XML 572 instances. The BEGIN and END tags are not part of the schema; they 573 are used to note the beginning and ending of the schema for URI 574 registration purposes. 576 5.1. Login Security Extension Schema 578 BEGIN 579 580 586 589 590 591 592 Extensible Provisioning Protocol v1.0 593 Login Security Extension Schema. 594 595 596 597 600 601 602 604 606 608 609 610 611 612 614 615 616 617 618 619 621 623 625 626 627 629 631 632 634 635 636 637 639 640 641 644 645 646 647 648 649 650 652 654 656 658 660 663 665 666 667 668 671 672 673 674 675 676 677 678 679 680 681 682 685 686 687 688 689 690 691 694 695 END 697 6. IANA Considerations 699 6.1. XML Namespace 701 This document uses URNs to describe XML namespaces and XML schemas 702 conforming to a registry mechanism described in [RFC3688]. The 703 following URI assignment is requested of IANA: 705 Registration request for the loginSec namespace: 707 URI: urn:ietf:params:xml:ns:epp:loginSec-1.0 708 Registrant Contact: IESG 709 XML: None. Namespace URIs do not represent an XML specification. 711 Registration request for the loginSec XML schema: 713 URI: urn:ietf:params:xml:schema:epp:loginSec-1.0 714 Registrant Contact: IESG 715 XML: See the "Formal Syntax" section of this document. 717 6.2. EPP Extension Registry 719 The EPP extension described in this document should be registered by 720 the IANA in the EPP Extension Registry described in [RFC7451]. The 721 details of the registration are as follows: 723 Name of Extension: "Login Security Extension for the Extensible 724 Provisioning Protocol (EPP)" 726 Document status: Standards Track 728 Reference: (insert reference to RFC version of this document) 730 Registrant Name and Email Address: IESG, 732 TLDs: Any 734 IPR Disclosure: None 736 Status: Active 738 Notes: None 740 7. Implementation Status 742 Note to RFC Editor: Please remove this section and the reference to 743 RFC 7942 [RFC7942] before publication. 745 This section records the status of known implementations of the 746 protocol defined by this specification at the time of posting of this 747 Internet-Draft, and is based on a proposal described in RFC 7942 748 [RFC7942]. The description of implementations in this section is 749 intended to assist the IETF in its decision processes in progressing 750 drafts to RFCs. Please note that the listing of any individual 751 implementation here does not imply endorsement by the IETF. 752 Furthermore, no effort has been spent to verify the information 753 presented here that was supplied by IETF contributors. This is not 754 intended as, and must not be construed to be, a catalog of available 755 implementations or their features. Readers are advised to note that 756 other implementations may exist. 758 According to RFC 7942 [RFC7942], "this will allow reviewers and 759 working groups to assign due consideration to documents that have the 760 benefit of running code, which may serve as evidence of valuable 761 experimentation and feedback that have made the implemented protocols 762 more mature. It is up to the individual working groups to use this 763 information as they see fit". 765 7.1. Verisign EPP SDK 767 Organization: Verisign Inc. 769 Name: Verisign EPP SDK 771 Description: The Verisign EPP SDK includes both a full client 772 implementation and a full server stub implementation of draft-ietf- 773 regext-login-security. 775 Level of maturity: Development 777 Coverage: All aspects of the protocol are implemented. 779 Licensing: GNU Lesser General Public License 781 Contact: jgould@verisign.com 783 URL: https://www.verisign.com/en_US/channel-resources/domain- 784 registry-products/epp-sdks 786 8. Security Considerations 788 The extension leaves the password ( element) and new password 789 ( element) minimum length beyond 6 characters and the maximum 790 length up to sever policy. The server SHOULD enforce minimum and 791 maximum length requirements that are appropriate for their operating 792 environment. One example of a guideline for password length policies 793 can be found in section 5 of NIST Special Publication 800-63B [1]. 795 The client SHOULD NOT decrease the security of a new password by 796 decreasing the length of the current password. For example, a client 797 with a 20 character password set using the extension, should not use 798 the login command in [RFC5730] without using the extension, to set a 799 new password that is less than or equal to 16 characters. 801 The extension provides an extensible list of login security events to 802 inform clients of connection and login warnings and errors. 804 9. Acknowledgements 806 The authors wish to thank the following persons for their feedback 807 and suggestions: 809 o Martin Casanova 810 o Scott Hollenbeck 811 o Barry Leiba 812 o Patrick Mevzek 813 o Joseph Yee 815 10. References 817 10.1. Normative References 819 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 820 Requirement Levels", BCP 14, RFC 2119, 821 DOI 10.17487/RFC2119, March 1997, 822 . 824 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 825 DOI 10.17487/RFC3688, January 2004, 826 . 828 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 829 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 830 . 832 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 833 Code: The Implementation Status Section", BCP 205, 834 RFC 7942, DOI 10.17487/RFC7942, July 2016, 835 . 837 [W3C.REC-xmlschema-2-20041028] 838 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 839 Second Edition", World Wide Web Consortium Recommendation 840 REC-xmlschema-2-20041028, October 2004, 841 . 843 10.2. Informative References 845 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 846 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 847 February 2015, . 849 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 850 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 851 May 2017, . 853 [RFC8265] Saint-Andre, P. and A. Melnikov, "Preparation, 854 Enforcement, and Comparison of Internationalized Strings 855 Representing Usernames and Passwords", RFC 8265, 856 DOI 10.17487/RFC8265, October 2017, 857 . 859 10.3. URIs 861 [1] https://pages.nist.gov/800-63-3/sp800-63b.html 863 Appendix A. Change History 865 [[RFC Editor: Please remove this section.]] 867 A.1. Change from 00 to 01 869 1. Based on the feedback from Patrick Mevzek and a proposal from 870 Scott Hollenbeck, changed the minimum length of the password from 871 8 to 6, revised the description of the password, and added text 872 in the Security Considerations section for the server password 873 length policy. 875 A.2. Change from 01 to 02 877 1. Changed the XML namespace from urn:ietf:params:xml:ns:loginSec- 878 0.3 to urn:ietf:params:xml:ns:epp:loginSec-0.3, and changed the 879 XML schema registration from urn:ietf:params:xml:ns:loginSec-0.3 880 to urn:ietf:params:xml:schema:epp:loginSec-0.3 based on a request 881 from IANA with draft-ietf-regext-allocation-token. 883 A.3. Change from 02 to 03 885 1. Updates based on the review by Patrick Mevzek, that include: 887 1. Fix the inconsistent case for newPW, that required a global 888 change in the draft text and an update to the XML schema to 889 "urn:ietf:params:xml:ns:loginSec-0.3". 890 2. Changed "contains the following child elements" to "MUST 891 contain at least one of the following child elements", 892 section "EPP Command" to ensure that an empty 893 element is not passed. 894 3. Add "The client SHOULD NOT decrease the security of a new 895 password by decreasing the length of the current password." 896 along with an example to the "Security Considerations" 897 section. 899 A.4. Change from 03 to REGEXT 00 901 1. Changed to regext working group draft by changing draft-gould- 902 regext-login-security to draft-ietf-regext-login-security. 904 A.5. Change from REGEXT 00 to REGEXT 01 906 1. Changed the element to be structured with 907 the , , and sub- 908 elements. This was based on the feedback from Martin Casanova. 909 This resulted in the need to change the XML namespace from 910 urn:ietf:params:xml:ns:epp:loginSec-0.3 to 911 urn:ietf:params:xml:ns:epp:loginSec-0.4. 913 A.6. Change from REGEXT 01 to REGEXT 02 915 1. Updated the Implementation Status section from "TBD" to include 916 the Verisign EPP SDK implementation. 918 A.7. Change from REGEXT 02 to REGEXT 03 920 1. Revised the description of the "duration" attribute to clarify 921 that it ends when the login command was received and to clarify 922 the format, based on the feedback from Martin Casanova. 923 2. Revised the sentence 'Upon a completed login command (success or 924 failed), the extension MUST be included in the response based on 925 the following conditions:' to 'Upon a completed login command 926 (success or failed), the extension MUST be included in the 927 response based on both of the following conditions:' based on the 928 feedback from Patrick Mevzek. 929 3. Updates based on the review by Joseph Yee, that include: 931 1. Revised the description of the "name" 932 attribute read 'Used to define a sub-type when the "type" 933 attribute is not "custom" or the full type name when the 934 "type" attribute is "custom"'. The definition of the "stat" 935 type was updated to 'Provides a login security statistical 936 warning that MUST set the "name" attribute to the name of the 937 statistic.' 938 2. Added the following sentence 'The server MUST NOT allow the 939 client to set the password to the value "[LOGIN-SECURITY]".' 940 to address the corner case where the constant is used as the 941 password. 942 3. Revised the description of the element 943 to read 'The element MUST contain at 944 least one of the following child elements:'. 945 4. Revised the description of the to match the 946 child elements that can be passed, by changing "client software" 947 to "client application software" and change "language" to 948 "technology". 949 5. Changed the XML namespace from 950 urn:ietf:params:xml:ns:epp:loginSec-0.4 to 951 urn:ietf:params:xml:ns:epp:loginSec-1.0. 953 A.8. Change from REGEXT 03 to REGEXT 04 955 Updates based on the review by Joseph Yee, that include: 957 1. Update the definition of the "stat" security event type to 958 reference sub-type to match the language for the "name" 959 attribute. 960 2. Added the sentence 'The "name" attribute MUST be set when the 961 "type" attribute is "stat" or "custom".' to the definition of the 962 "name" attribute for clarity. 963 3. Update the definition of the "userAgentType" in the XML schema to 964 require at least one sub-element using a element. 966 A.9. Change from REGEXT 04 to REGEXT 05 968 Updates based on the review by Barry Leiba, that include: 970 1. In section 1.1, updated to use BCP 14 boilerplate and references 971 as defined in RFC 8174. 972 2. In section 1.1, change "REQUIRED" to "required". 973 3. Keep the "Migration to Newer Versions of This Extension" section 974 by removing the note for removal to the RFC Editor. 975 4. In section 3.1, change "MAY be multiple events returned that 976 provides information" to "MAY be multiple events returned that 977 provide information". 978 5. In section 3.1, change "free form" to "free-form". 979 6. In section 3.1, change "The enumerated list of "type" values 980 include:" to "The enumerated list of "type" values includes:". 981 7. In section 3.1, change "Identifies the language of the free-form 982 description if the negotiated language is something other than 983 the default value of "en" (English)." to "Identifies the 984 negotiated language of the free-form description. The default is 985 "en" (English). 986 8. In section 3.1, change example description from "Example login 987 security event for a password expiring in a week:" to "Example 988 login security event for password expiration, where the current 989 date is 2018-03-25:". 990 9. In section 4.1, change "Example EPP response to a successful 991 login command where the password will expire in a week:" to 992 "Example EPP response to a successful login command on 993 2018-03-25, where the password will expire in a week:". 995 A.10. Change from REGEXT 05 to REGEXT 06 997 Updates based on the review by Brian Carpenter, that include: 999 1. In section 1, change the references to RFC 5730 to use links. 1000 2. In section 2, change "(for a temporary migration period)" to 1001 "(for a temporary migration period up to server policy)". 1003 A.11. Change from REGEXT 06 to REGEXT 07 1005 1. Based on feedback from Barry Leiba, added recommendations on the 1006 characters used for the plain text password. Recommended the use 1007 of printable ASCII passwords and if non-ASCII characters are 1008 supported, to use a standard for passwords with international 1009 characters, such as the OpaqueString PRECIS profile in [RFC8265]. 1010 2. Based on the feedback from Carlos Pignataro, added "[[RFC Editor: 1011 Please remove this section.]]" to the "Change History" section. 1013 Authors' Addresses 1015 James Gould 1016 VeriSign, Inc. 1017 12061 Bluemont Way 1018 Reston, VA 20190 1019 US 1021 Email: jgould@verisign.com 1022 URI: http://www.verisign.com 1024 Matthew Pozun 1025 VeriSign, Inc. 1026 12061 Bluemont Way 1027 Reston, VA 20190 1028 US 1030 Email: mpozun@verisign.com 1031 URI: http://www.verisign.com