idnits 2.17.1 draft-ietf-regext-change-poll-08.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 (May 16, 2018) is 2171 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Gould 3 Internet-Draft VeriSign, Inc. 4 Intended status: Standards Track K. Feher 5 Expires: November 17, 2018 Neustar 6 May 16, 2018 8 Change Poll Extension for the Extensible Provisioning Protocol (EPP) 9 draft-ietf-regext-change-poll-08 11 Abstract 13 This document describes an Extensible Provisioning Protocol (EPP) 14 extension for notifying clients of operations on client sponsored 15 objects that were not initiated by the client through EPP. These 16 operations may include contractual or policy requirements including 17 but not limited to regular batch processes, customer support actions, 18 Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid 19 Suspension (URS) actions, court directed actions, and bulk updates 20 based on customer requests. Since the client is not directly 21 involved or knowledgable of these operations, the extension is used 22 along with an EPP object mapping to provide the resulting state of 23 the post-operation object, and optionally a pre-operation object, 24 with the operation meta-data of what, when, who, and why. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on November 17, 2018. 43 Copyright Notice 45 Copyright (c) 2018 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 62 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 63 2.1. Operation . . . . . . . . . . . . . . . . . . . . . . . . 4 64 2.2. State . . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 2.3. Who . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 5 67 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 68 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 69 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 6 70 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 6 71 3.1.3. EPP Command . . . . . . . . . . . . . . . 16 72 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16 73 3.2.1. EPP Command . . . . . . . . . . . . . . . . 16 74 3.2.2. EPP Command . . . . . . . . . . . . . . . . 16 75 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 16 76 3.2.4. EPP Command . . . . . . . . . . . . . . . 16 77 3.2.5. EPP Command . . . . . . . . . . . . . . . . 16 78 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16 79 4.1. Change Poll Extension Schema . . . . . . . . . . . . . . 17 80 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 81 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 19 82 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 20 83 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 84 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 21 85 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 21 86 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 22 87 6.4. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 22 88 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 89 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 90 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 91 9.1. Normative References . . . . . . . . . . . . . . . . . . 23 92 9.2. Informative References . . . . . . . . . . . . . . . . . 23 93 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24 94 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 24 95 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 24 96 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 24 97 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 24 98 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 24 99 A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 24 100 A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 24 101 A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 24 102 A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 24 103 A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25 104 A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 25 105 A.12. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 25 106 A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25 107 A.14. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 26 108 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 110 1. Introduction 112 This document describes an extension mapping for version 1.0 of the 113 Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an 114 extension to EPP object mappings like the EPP domain name mapping 115 [RFC5731], is used to notify clients of operations they are not 116 directly involved in, on objects that the client sponsors. It is up 117 to server policy to determine what transform operations and clients 118 to notify. Using this extension, clients can more easily keep their 119 systems in-sync with the objects stored in the server. When a change 120 occurs that a client needs to be notified of, a poll message can be 121 inserted by the server for consumption by the client using the EPP 122 command and response defined in [RFC5730]. The extension 123 supports including a "before" operation poll message and an "after" 124 operation poll message. 126 1.1. Conventions Used in This Document 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 130 document are to be interpreted as described in RFC 2119 [RFC2119]. 132 XML is case sensitive. Unless stated otherwise, XML specifications 133 and examples provided in this document MUST be interpreted in the 134 character case presented in order to develop a conforming 135 implementation. 137 In examples, "C:" represents lines sent by a protocol client and "S:" 138 represents lines returned by a protocol server. Indentation and 139 white space in examples are provided only to illustrate element 140 relationships and are not a REQUIRED feature of this protocol. 142 "changePoll-1.0" is used as an abbreviation for 143 "urn:ietf:params:xml:ns:changePoll-1.0". The XML namespace prefix 144 "changePoll" is used, but implementations MUST NOT depend on it and 145 instead employ a proper namespace-aware XML parser and serializer to 146 interpret and output the XML documents. 148 2. Object Attributes 150 This extension adds additional elements to EPP object mappings like 151 the EPP domain name mapping [RFC5731]. Only those new elements are 152 described here. 154 2.1. Operation 156 An operation consists of any transform operation that impacts objects 157 that the client sponsers and SHOULD be notified of. The 158 element defines the operation. The OPTIONAL 159 "op" attribute is an identifier, represented in the 7-bit US-ASCII 160 character set, that is used to define a sub-operation or the name of 161 a "custom" operation. The enumerated list of 162 values include: 164 "create": Create operation as defined in [RFC5730]. 165 "delete": Delete operation as defined in [RFC5730]. If the delete 166 operation results in an immediate purge of the object, then the 167 "op" attribute MUST be set to "purge". 168 "renew": Renew operation as defined in [RFC5730]. 169 "transfer": Transfer operation as defined in [RFC5730] that MUST set 170 the "op" attribute with one of the possible transfer type values 171 that include "request", "approve", "cancel", or "reject". 172 "update": Update operation as defined in [RFC5730]. 173 "restore": Restore operation as defined in [RFC3915] that MUST set 174 the "op" attribute with one of the possible restore type values 175 that include "request" or "report". 176 "autoRenew": Auto renew operation executed by the server. 177 "autoDelete": Auto delete operation executed by the server. If the 178 "autoDelete" operation results in an immediate purge of the 179 object, then the "op" attribute MUST be set to "purge". 180 "autoPurge": Auto purge operation executed by the server when 181 removing the object after it had the "pendingDelete" status. 182 "custom": Custom operation that MUST set the "op" attribute with the 183 custom operation name. 185 2.2. State 187 The state attribute reflects the state of the object "before" or 188 "after" the operation. The state is defined using the OPTIONAL 189 "state" attribute of the element, with the 190 possible values "before" or "after" and with a default value of 191 "after". The server MAY support both the "before" state and the 192 "after" state of the operation, by using one poll message for the 193 "before" state and one poll message for the "after" state. The 194 "before" state poll message MUST be inserted prior to the "after" 195 state poll message. 197 For operations in Section 2.1 that don't have an "after" state, the 198 server MUST use the "before" state poll message. For example, for 199 the "delete" operation with the "op" attribute set to "purge", or the 200 "autoPurge" operation, the server includes the state of the object 201 prior to being purged in the "before" state poll message. 203 For operations in Section 2.1 that don't have a "before" state, the 204 server MUST use the "after" state poll message. For example, for the 205 "create" operation, the server includes the state of the object after 206 creation in the "after" state poll message. 208 2.3. Who 210 The element defines who executed the operation for 211 audit purposes. The scheme used for the possible set of 212 element values is up to server policy. The server 213 MAY identify the element value based on: 215 "Identifier": Unique user identifier of the user that executed the 216 operation. An example is "ClientX". 217 "Name": Name of the user that executed the operation. An example is 218 "John Doe". 219 "Role": Role of the user that executed operation. An example is 220 "CSR" for a Customer Support Representative or "Batch" for a 221 server batch. 223 2.4. Dates and Times 225 Date and time attribute values MUST be represented in Universal 226 Coordinated Time (UTC) using the Gregorian calendar. The extended 227 date-time form using upper case "T" and "Z" characters defined in 228 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 229 values, as XML Schema does not support truncated date-time forms or 230 lower case "T" and "Z" characters. 232 3. EPP Command Mapping 234 A detailed description of the EPP syntax and semantics can be found 235 in the EPP core protocol specification [RFC5730]. 237 3.1. EPP Query Commands 239 EPP provides three commands to retrieve object information: 240 to determine if an object is known to the server, to retrieve 241 detailed information associated with an object, and to 242 retrieve object transfer status information. 244 3.1.1. EPP Command 246 This extension does not add any elements to the EPP command 247 or response described in the [RFC5730]. 249 3.1.2. EPP Command 251 This extension does not add any elements to the EPP command 252 described in the [RFC5730]. 254 This extension adds operation detail of EPP object mapping operations 255 Section 2.1 to an EPP poll response, as described in [RFC5730], that 256 is an extension of the EPP object mapping info response. Any 257 transform operation to an object defined in an EPP object mapping, by 258 a client other than the sponsoring client, MAY result in extending 259 the response of the object for inserting an EPP poll message 260 with the operation detail. The sponsoring client will then receive 261 the state of the object with operation detail like what, who, when, 262 and why the object was changed. The element 263 contains the operation detail along with an indication of whether the 264 object reflects the state before or after the operation as defined in 265 Section 2.2. The element includes the 266 operation detail with the following child elements: 268 : Transform operation executed on the object 269 as defined in Section 2.1. 270 : Date and time when the operation was executed. 271 : Server transaction identifier of the operation. 272 : Who executed the operation as defined in 273 Section 2.3. 274 : OPTIONAL case identifer associated with the 275 operation. The required "type" attribute defines the type of 276 case. The OPTIONAL "name" attribute is an identifier, 277 represented in the 7-bit US-ASCII character set, that is used to 278 define the name of the "custom" case type. The enumerated list 279 of case types include: 281 udrp: a Uniform Domain-Name Dispute-Resolution Policy (UDRP) 282 case. 283 urs: a Uniform Rapid Suspension (URS) case. 285 custom: A custom case that is defined using the "name" 286 attribute. 287 : OPTIONAL reason for executing the operation. 288 If present, this element contains the server-specific text to 289 help explain the reason the operation was executed. This text 290 MUST be represented in the response language previously 291 negotiated with the client; an OPTIONAL "lang" attribute MAY be 292 present to identify the language if the negotiated value is 293 something other than the default value of "en" (English). 295 Example poll response with the 296 extension for a URS lock transaction on the domain.example domain 297 name, with the "before" state. The "before" state is reflected in 298 the block: 300 S: 301 S: 302 S: 303 S: 304 S: 305 S: Command completed successfully; ack to dequeue 306 S: 307 S: 308 S: 2013-10-22T14:25:57.0Z 309 S: Registry initiated update of domain. 310 S: 311 S: 312 S: 314 S: domain.example 315 S: EXAMPLE1-REP 316 S: 317 S: jd1234 318 S: sh8013 319 S: sh8013 320 S: ClientX 321 S: ClientY 322 S: 2012-04-03T22:00:00.0Z 323 S: 2014-04-03T22:00:00.0Z 324 S: 325 S: 326 S: 327 S: 330 S: update 331 S: 2013-10-22T14:25:57.0Z 332 S: 12345-XYZ 333 S: URS Admin 334 S: urs123 335 S: URS Lock 336 S: 337 S: 338 S: 339 S: ABC-12345 340 S: 54321-XYZ 341 S: 342 S: 343 S: 345 Example poll response with the 346 extension for a URS lock transaction on the domain.example domain 347 name, with the "after" state. The "after" state is reflected in the 348 block: 350 S: 351 S: 352 S: 353 S: 354 S: 355 S: Command completed successfully; ack to dequeue 356 S: 357 S: 358 S: 2013-10-22T14:25:57.0Z 359 S: Registry initiated update of domain. 360 S: 361 S: 362 S: 364 S: domain.example 365 S: EXAMPLE1-REP 366 S: 367 S: 368 S: 369 S: jd1234 370 S: sh8013 371 S: sh8013 372 S: ClientX 373 S: ClientY 374 S: 2012-04-03T22:00:00.0Z 375 S: ClientZ 376 S: 2013-10-22T14:25:57.0Z 377 S: 2014-04-03T22:00:00.0Z 378 S: 379 S: 380 S: 381 S: 384 S: update 385 S: 2013-10-22T14:25:57.0Z 386 S: 12345-XYZ 387 S: URS Admin 388 S: urs123 389 S: URS Lock 390 S: 391 S: 392 S: 393 S: ABC-12345 394 S: 54321-XYZ 395 S: 396 S: 397 S: 398 Example poll response with the 399 extension for a custom "sync" operation on the domain.example domain 400 name, with the default "after" state. The "after" state is reflected 401 in the block: 403 S: 404 S: 405 S: 406 S: 407 S: Command completed successfully; ack to dequeue 408 S: 409 S: 410 S: 2013-10-22T14:25:57.0Z 411 S: Registry initiated Sync of Domain Expiration Date 412 S: 413 S: 414 S: 416 S: domain.example 417 S: EXAMPLE1-REP 418 S: 419 S: jd1234 420 S: sh8013 421 S: sh8013 422 S: ClientX 423 S: ClientY 424 S: 2012-04-03T22:00:00.0Z 425 S: ClientZ 426 S: 2013-10-22T14:25:57.0Z 427 S: 2014-04-03T22:00:00.0Z 428 S: 429 S: 430 S: 431 S: 433 S: custom 434 S: 435 S: 2013-10-22T14:25:57.0Z 436 S: 12345-XYZ 437 S: CSR 438 S: Customer sync request 439 S: 440 S: 441 S: 442 S: 443 S: ABC-12345 444 S: 54321-XYZ 445 S: 446 S: 447 S: 448 Example poll response with the 449 extension for a "delete" operation on the domain.example domain name 450 that is immediately purged, with the default "after" state. The 451 "after" state is reflected in the block: 453 S: 454 S: 455 S: 456 S: 457 S: Command completed successfully; ack to dequeue 458 S: 459 S: 460 S: 2013-10-22T14:25:57.0Z 461 S: Registry initiated delete of 462 S: domain resulting in immediate purge. 463 S: 464 S: 465 S: 467 S: domain.example 468 S: EXAMPLE1-REP 469 S: ClientX 470 S: 471 S: 472 S: 473 S: 475 S: 476 S: delete 477 S: 2013-10-22T14:25:57.0Z 478 S: 12345-XYZ 479 S: ClientZ 480 S: Court order 481 S: 482 S: 483 S: 484 S: ABC-12345 485 S: 54321-XYZ 486 S: 487 S: 488 S: 489 Example poll response with the 490 extension for an "autoPurge" operation on the domain.example domain 491 name that previously had the "pendingDelete" status, with the default 492 "after" state. The "after" state is reflected in the 493 block: 495 S: 496 S: 497 S: 498 S: 499 S: Command completed successfully; ack to dequeue 500 S: 501 S: 502 S: 2013-10-22T14:25:57.0Z 503 S: Registry purged domain with pendingDelete status. 504 S: 505 S: 506 S: 508 S: domain.example 509 S: EXAMPLE1-REP 510 S: ClientX 511 S: 512 S: 513 S: 514 S: 516 S: 517 S: autoPurge 518 S: 2013-10-22T14:25:57.0Z 519 S: 12345-XYZ 520 S: Batch 521 S: 522 S: Past pendingDelete 5 day period 523 S: 524 S: 525 S: 526 S: 527 S: ABC-12345 528 S: 54321-XYZ 529 S: 530 S: 531 S: 532 Example poll response with the 533 extension for an "update" operation on the ns1.domain.example host, 534 with the default "after" state. The "after" state is reflected in 535 the block: 537 S: 538 S: 539 S: 540 S: 541 S: Command completed successfully; ack to dequeue 542 S: 543 S: 544 S: 2013-10-22T14:25:57.0Z 545 S: Registry initiated update of host. 546 S: 547 S: 548 S: 550 S: ns1.domain.example 551 S: NS1_EXAMPLE1-REP 552 S: 553 S: 554 S: 555 S: 192.0.2.2 556 S: 1080:0:0:0:8:800:200C:417A 557 S: ClientX 558 S: ClientY 559 S: 2012-04-03T22:00:00.0Z 560 S: ClientY 561 S: 2013-10-22T14:25:57.0Z 562 S: 563 S: 564 S: 565 S: 567 S: update 568 S: 2013-10-22T14:25:57.0Z 569 S: 12345-XYZ 570 S: ClientZ 571 S: Host Lock 572 S: 573 S: 574 S: 575 S: ABC-12345 576 S: 54321-XYZ 577 S: 578 S: 579 S: 581 3.1.3. EPP Command 583 This extension does not add any elements to the EPP query 584 command or response described in the [RFC5730]. 586 3.2. EPP Transform Commands 588 EPP provides five commands to transform objects: to create 589 an instance of an object, to delete an instance of an 590 object, to extend the validity period of an object, 591 to manage object sponsorship changes, and to 592 change information associated with an object. 594 3.2.1. EPP Command 596 This extension does not add any elements to the EPP command 597 or response described in the [RFC5730]. 599 3.2.2. EPP Command 601 This extension does not add any elements to the EPP command 602 or response described in the [RFC5730]. 604 3.2.3. EPP Command 606 This extension does not add any elements to the EPP command 607 or response described in the [RFC5730]. 609 3.2.4. EPP Command 611 This extension does not add any elements to the EPP 612 command or response described in the [RFC5730]. 614 3.2.5. EPP Command 616 This extension does not add any elements to the EPP command 617 or response described in the [RFC5730]. 619 4. Formal Syntax 621 One schema is presented here that is the EPP Change Poll Extension 622 schema. 624 The formal syntax presented here is a complete schema representation 625 of the object mapping suitable for automated validation of EPP XML 626 instances. The BEGIN and END tags are not part of the schema; they 627 are used to note the beginning and ending of the schema for URI 628 registration purposes. 630 4.1. Change Poll Extension Schema 632 BEGIN 633 634 641 644 645 647 648 649 Extensible Provisioning Protocol v1.0 650 Change Poll Mapping Schema. 651 652 654 657 659 662 663 664 665 666 667 668 670 672 673 675 676 679 680 681 682 683 684 685 686 687 688 689 690 691 692 694 697 698 699 700 701 702 704 707 708 709 710 711 712 713 715 718 719 720 721 723 725 726 727 729 732 733 734 735 736 737 738 740 743 744 745 746 747 748 750 753 754 END 756 5. IANA Considerations 758 5.1. XML Namespace 760 This document uses URNs to describe XML namespaces and XML schemas 761 conforming to a registry mechanism described in [RFC3688]. The 762 following URI assignment is requested of IANA: 764 Registration request for the changePoll namespace: 766 URI: urn:ietf:params:xml:ns:changePoll-1.0 767 Registrant Contact: IESG 768 XML: None. Namespace URIs do not represent an XML specification. 770 Registration request for the changePoll XML schema: 772 URI: urn:ietf:params:xml:ns:changePoll-1.0 773 Registrant Contact: IESG 774 XML: See the "Formal Syntax" section of this document. 776 5.2. EPP Extension Registry 778 The EPP extension described in this document should be registered by 779 the IANA in the EPP Extension Registry described in [RFC7451]. The 780 details of the registration are as follows: 782 Name of Extension: "Change Poll Extension for the Extensible 783 Provisioning Protocol (EPP)" 785 Document status: Standards Track 787 Reference: (insert reference to RFC version of this document) 789 Registrant Name and Email Address: IESG, 791 TLDs: Any 793 IPR Disclosure: None 795 Status: Active 797 Notes: None 799 6. Implementation Status 801 Note to RFC Editor: Please remove this section and the reference to 802 RFC 7942 [RFC7942] before publication. 804 This section records the status of known implementations of the 805 protocol defined by this specification at the time of posting of this 806 Internet-Draft, and is based on a proposal described in RFC 7942 807 [RFC7942]. The description of implementations in this section is 808 intended to assist the IETF in its decision processes in progressing 809 drafts to RFCs. Please note that the listing of any individual 810 implementation here does not imply endorsement by the IETF. 811 Furthermore, no effort has been spent to verify the information 812 presented here that was supplied by IETF contributors. This is not 813 intended as, and must not be construed to be, a catalog of available 814 implementations or their features. Readers are advised to note that 815 other implementations may exist. 817 According to RFC 7942 [RFC7942], "this will allow reviewers and 818 working groups to assign due consideration to documents that have the 819 benefit of running code, which may serve as evidence of valuable 820 experimentation and feedback that have made the implemented protocols 821 more mature. It is up to the individual working groups to use this 822 information as they see fit". 824 6.1. Verisign EPP SDK 826 Organization: Verisign Inc. 828 Name: Verisign EPP SDK 830 Description: The Verisign EPP SDK includes both a full client 831 implementation and a full server stub implementation of draft-ietf- 832 regext-change-poll. 834 Level of maturity: Production 836 Coverage: All aspects of the protocol are implemented. 838 Licensing: GNU Lesser General Public License 840 Contact: jgould@verisign.com 842 URL: https://www.verisign.com/en_US/channel-resources/domain- 843 registry-products/epp-sdks 845 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 847 Organization: Verisign Inc. 849 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 850 System (SRS) 852 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 853 Registry System (SRS) implements the server-side of draft-ietf- 854 regext-change-poll for a variety of Top Level Domains (TLD's). 856 Level of maturity: Production 858 Coverage: The "after" state poll message for an "update" transform 859 operation of a domain name due to server policy. 861 Licensing: Proprietary 863 Contact: jgould@verisign.com 865 6.3. Verisign .COM / .NET SRS 867 Organization: Verisign Inc. 869 Name: Verisign .COM / .NET Shared Registry System (SRS) 871 Description: The Verisign Shared Registry System (SRS) for .COM and 872 .NET implements the server-side of draft-ietf-regext-change-poll. 874 Level of maturity: Production 876 Coverage: The "after" state poll message for an "update" transform 877 operation of a domain name due to server policy. 879 Licensing: Proprietary 881 Contact: jgould@verisign.com 883 6.4. Neustar EPP SDK 885 Organisation: Neustar Inc. 887 Name: Neustar EPP SDK 889 Description: The Neustar EPP SDK includes a full client 890 implementation of draft-ietf-regext-change-poll. 892 Level of maturity: Production 894 Coverage: All client side aspects of the protocol are implemented. 896 Licensing: GNU Lesser General Public License 898 Contact: quoc-anh.np@team.neustar 900 7. Security Considerations 902 The mapping extensions described in this document do not provide any 903 security services beyond those described by EPP [RFC5730] and 904 protocol layers used by EPP. The security considerations described 905 in these other specifications apply to this specification as well. 907 8. Acknowledgements 909 The authors wish to acknowledge the original concept for this draft 910 and the efforts in the initial versions of this draft by Trung Tran 911 and Sharon Wodjenski. 913 Special suggestions that have been incorporated into this document 914 were provided by Scott Hollenbeck, Michael Holloway, and Patrick 915 Mevzek. 917 9. References 919 9.1. Normative References 921 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 922 Requirement Levels", BCP 14, RFC 2119, 923 DOI 10.17487/RFC2119, March 1997, . 926 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 927 DOI 10.17487/RFC3688, January 2004, . 930 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 931 the Extensible Provisioning Protocol (EPP)", RFC 3915, 932 DOI 10.17487/RFC3915, September 2004, . 935 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 936 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 937 . 939 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 940 Domain Name Mapping", STD 69, RFC 5731, 941 DOI 10.17487/RFC5731, August 2009, . 944 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 945 Code: The Implementation Status Section", BCP 205, 946 RFC 7942, DOI 10.17487/RFC7942, July 2016, 947 . 949 [W3C.REC-xmlschema-2-20041028] 950 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 951 Second Edition", World Wide Web Consortium Recommendation 952 REC-xmlschema-2-20041028, October 2004, 953 . 955 9.2. Informative References 957 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 958 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 959 February 2015, . 961 Appendix A. Change History 963 A.1. Change from 00 to 01 965 1. Added an optional caseId element that defines the case identifier 966 from UDRP, URS, or custom case, based on feedback from Michael 967 Holloway. 969 A.2. Change from 01 to 02 971 1. Amended XML Namespace section of IANA Considerations, added EPP 972 Extension Registry section. 973 2. Moved Change History to the back section as an Appendix. 975 A.3. Change from 02 to 03 977 1. Fixed "before" state example to use the "before" state value 978 based on feedback from Patrick Mevzek. 980 A.4. Change from 03 to 04 982 1. Updated the authors for the draft. 984 A.5. Change from 04 to 05 986 1. Ping update. 988 A.6. Change from 05 to REGEXT 00 990 1. Changed to regext working group draft by changing draft-gould- 991 change-poll to draft-ietf-regext-change-poll. 993 A.7. Change from REGEXT 00 to REGEXT 01 995 1. Ping update. 997 A.8. Change from REGEXT 01 to REGEXT 02 999 1. Added the Implementation Status section. 1001 A.9. Change from REGEXT 02 to REGEXT 03 1003 1. Changed Neustar author to Kal Feher. 1005 A.10. Change from REGEXT 03 to REGEXT 04 1007 1. Added Neustar implementation to the Implementation Status 1008 section. 1010 A.11. Change from REGEXT 04 to REGEXT 05 1012 1. Updates based on feedback from Patrick Mevzek, that include: 1014 1. Added a missing comma to "Using this extension, clients" in 1015 the Introduction section. 1016 2. Modified the description of the "transfer", "restore", and 1017 "custom" operations to include "MUST set the "op" attribute" 1018 language. 1019 3. Rephrased the first sentence of the Who section. 1020 4. Added references to the element in the Who 1021 section. 1022 5. Revise the sentence that describes how the extension extends 1023 the info response in the EPP Command section. 1024 6. Refer to EPP Object Mapping as EPP object mapping throughout 1025 the document. 1026 7. Add a Dates and Times section to the Object Attributes 1027 section. 1029 A.12. Change from REGEXT 05 to REGEXT 06 1031 1. Added the "State" sub-section to the "Object Attributes" section 1032 to describe the expected behavior for the "before" and "after" 1033 states, based on feedback from Patrick Mevzek. 1034 2. Added a colon suffix to each hangText entry to provide better 1035 separation. 1037 A.13. Change from REGEXT 06 to REGEXT 07 1039 1. Updates based on feedback from Scott Hollenbeck, that include: 1041 1. Changed MAY to may in the Abstract. 1042 2. Revised the "IANA Considerations" section to include the 1043 registration of the XML schema. 1044 3. Revised the description of the "name" 1045 attribute and the "changePoll:operation> "op" attribute as 1046 containing 7-bit US-ASCII identifiers for the case type or 1047 the operation type, respectively. 1049 A.14. Change from REGEXT 07 to REGEXT 08 1051 1. Updated obsoleted RFC 6982 to RFC 7942. 1052 2. Moved RFC 7451 to an informational reference based on a check 1053 done by the Idnits Tool. 1054 3. Changed Kal Feher's contact e-mail address. 1055 4. Changed Neustar's Implementation Status contact e-mail address. 1057 Authors' Addresses 1059 James Gould 1060 VeriSign, Inc. 1061 12061 Bluemont Way 1062 Reston, VA 20190 1063 US 1065 Email: jgould@verisign.com 1066 URI: http://www.verisigninc.com 1068 Kal Feher 1069 Neustar 1070 lvl 8/10 Queens Road 1071 Melbourne, VIC 3004 1072 AU 1074 Email: ietf@feherfamily.org 1075 URI: http://www.neustar.biz