idnits 2.17.1 draft-ietf-regext-change-poll-09.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 (October 4, 2018) is 2028 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: April 7, 2019 Neustar 6 October 4, 2018 8 Change Poll Extension for the Extensible Provisioning Protocol (EPP) 9 draft-ietf-regext-change-poll-09 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 April 7, 2019. 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 . . . . . . . . . . . 25 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 A.15. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 26 109 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 111 1. Introduction 113 This document describes an extension mapping for version 1.0 of the 114 Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an 115 extension to EPP object mappings like the EPP domain name mapping 116 [RFC5731], is used to notify clients of operations they are not 117 directly involved in, on objects that the client sponsors. It is up 118 to server policy to determine what transform operations and clients 119 to notify. Using this extension, clients can more easily keep their 120 systems in-sync with the objects stored in the server. When a change 121 occurs that a client needs to be notified of, a poll message can be 122 inserted by the server for consumption by the client using the EPP 123 command and response defined in [RFC5730]. The extension 124 supports including a "before" operation poll message and an "after" 125 operation poll message. 127 1.1. Conventions Used in This Document 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 131 "OPTIONAL" in this document are to be interpreted as described in BCP 132 14 [RFC2119] [RFC8174] when, and only when, they appear in all 133 capitals, as shown here. 135 XML is case sensitive. Unless stated otherwise, XML specifications 136 and examples provided in this document MUST be interpreted in the 137 character case presented in order to develop a conforming 138 implementation. 140 In examples, "C:" represents lines sent by a protocol client and "S:" 141 represents lines returned by a protocol server. Indentation and 142 white space in examples are provided only to illustrate element 143 relationships and are not a REQUIRED feature of this protocol. 145 "changePoll-1.0" is used as an abbreviation for 146 "urn:ietf:params:xml:ns:changePoll-1.0". The XML namespace prefix 147 "changePoll" is used, but implementations MUST NOT depend on it and 148 instead employ a proper namespace-aware XML parser and serializer to 149 interpret and output the XML documents. 151 2. Object Attributes 153 This extension adds additional elements to EPP object mappings like 154 the EPP domain name mapping [RFC5731]. Only those new elements are 155 described here. 157 2.1. Operation 159 An operation consists of any transform operation that impacts objects 160 that the client sponsers and SHOULD be notified of. The 161 element defines the operation. The OPTIONAL 162 "op" attribute is an identifier, represented in the 7-bit US-ASCII 163 character set, that is used to define a sub-operation or the name of 164 a "custom" operation. The enumerated list of 165 values include: 167 "create": Create operation as defined in [RFC5730]. 168 "delete": Delete operation as defined in [RFC5730]. If the delete 169 operation results in an immediate purge of the object, then the 170 "op" attribute MUST be set to "purge". 171 "renew": Renew operation as defined in [RFC5730]. 172 "transfer": Transfer operation as defined in [RFC5730] that MUST set 173 the "op" attribute with one of the possible transfer type values 174 that include "request", "approve", "cancel", or "reject". 175 "update": Update operation as defined in [RFC5730]. 176 "restore": Restore operation as defined in [RFC3915] that MUST set 177 the "op" attribute with one of the possible restore type values 178 that include "request" or "report". 179 "autoRenew": Auto renew operation executed by the server. 180 "autoDelete": Auto delete operation executed by the server. If the 181 "autoDelete" operation results in an immediate purge of the 182 object, then the "op" attribute MUST be set to "purge". 183 "autoPurge": Auto purge operation executed by the server when 184 removing the object after it had the "pendingDelete" status. 185 "custom": Custom operation that MUST set the "op" attribute with the 186 custom operation name. 188 2.2. State 190 The state attribute reflects the state of the object "before" or 191 "after" the operation. The state is defined using the OPTIONAL 192 "state" attribute of the element, with the 193 possible values "before" or "after" and with a default value of 194 "after". The server MAY support both the "before" state and the 195 "after" state of the operation, by using one poll message for the 196 "before" state and one poll message for the "after" state. The 197 "before" state poll message MUST be inserted prior to the "after" 198 state poll message. 200 For operations in Section 2.1 that don't have an "after" state, the 201 server MUST use the "before" state poll message. For example, for 202 the "delete" operation with the "op" attribute set to "purge", or the 203 "autoPurge" operation, the server includes the state of the object 204 prior to being purged in the "before" state poll message. 206 For operations in Section 2.1 that don't have a "before" state, the 207 server MUST use the "after" state poll message. For example, for the 208 "create" operation, the server includes the state of the object after 209 creation in the "after" state poll message. 211 2.3. Who 213 The element defines who executed the operation for 214 audit purposes. The scheme used for the possible set of 215 element values is up to server policy. The server 216 MAY identify the element value based on: 218 "Identifier": Unique user identifier of the user that executed the 219 operation. An example is "ClientX". 220 "Name": Name of the user that executed the operation. An example is 221 "John Doe". 222 "Role": Role of the user that executed operation. An example is 223 "CSR" for a Customer Support Representative or "Batch" for a 224 server batch. 226 2.4. Dates and Times 228 Date and time attribute values MUST be represented in Universal 229 Coordinated Time (UTC) using the Gregorian calendar. The extended 230 date-time form using upper case "T" and "Z" characters defined in 231 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 232 values, as XML Schema does not support truncated date-time forms or 233 lower case "T" and "Z" characters. 235 3. EPP Command Mapping 237 A detailed description of the EPP syntax and semantics can be found 238 in the EPP core protocol specification [RFC5730]. 240 3.1. EPP Query Commands 242 EPP provides three commands to retrieve object information: 243 to determine if an object is known to the server, to retrieve 244 detailed information associated with an object, and to 245 retrieve object transfer status information. 247 3.1.1. EPP Command 249 This extension does not add any elements to the EPP command 250 or response described in the [RFC5730]. 252 3.1.2. EPP Command 254 This extension does not add any elements to the EPP command 255 described in the [RFC5730]. 257 This extension adds operation detail of EPP object mapping operations 258 Section 2.1 to an EPP poll response, as described in [RFC5730], that 259 is an extension of the EPP object mapping info response. Any 260 transform operation to an object defined in an EPP object mapping, by 261 a client other than the sponsoring client, MAY result in extending 262 the response of the object for inserting an EPP poll message 263 with the operation detail. The sponsoring client will then receive 264 the state of the object with operation detail like what, who, when, 265 and why the object was changed. The element 266 contains the operation detail along with an indication of whether the 267 object reflects the state before or after the operation as defined in 268 Section 2.2. The element includes the 269 operation detail with the following child elements: 271 : Transform operation executed on the object 272 as defined in Section 2.1. 273 : Date and time when the operation was executed. 274 : Server transaction identifier of the operation. 275 : Who executed the operation as defined in 276 Section 2.3. 277 : OPTIONAL case identifer associated with the 278 operation. The required "type" attribute defines the type of 279 case. The OPTIONAL "name" attribute is an identifier, 280 represented in the 7-bit US-ASCII character set, that is used to 281 define the name of the "custom" case type. The enumerated list 282 of case types include: 284 udrp: a Uniform Domain-Name Dispute-Resolution Policy (UDRP) 285 case. 286 urs: a Uniform Rapid Suspension (URS) case. 288 custom: A custom case that is defined using the "name" 289 attribute. 290 : OPTIONAL reason for executing the operation. 291 If present, this element contains the server-specific text to 292 help explain the reason the operation was executed. This text 293 MUST be represented in the response language previously 294 negotiated with the client; an OPTIONAL "lang" attribute MAY be 295 present to identify the language if the negotiated value is 296 something other than the default value of "en" (English). 298 Example poll response with the 299 extension for a URS lock transaction on the domain.example domain 300 name, with the "before" state. The "before" state is reflected in 301 the block: 303 S: 304 S: 305 S: 306 S: 307 S: 308 S: Command completed successfully; ack to dequeue 309 S: 310 S: 311 S: 2013-10-22T14:25:57.0Z 312 S: Registry initiated update of domain. 313 S: 314 S: 315 S: 317 S: domain.example 318 S: EXAMPLE1-REP 319 S: 320 S: jd1234 321 S: sh8013 322 S: sh8013 323 S: ClientX 324 S: ClientY 325 S: 2012-04-03T22:00:00.0Z 326 S: 2014-04-03T22:00:00.0Z 327 S: 328 S: 329 S: 330 S: 333 S: update 334 S: 2013-10-22T14:25:57.0Z 335 S: 12345-XYZ 336 S: URS Admin 337 S: urs123 338 S: URS Lock 339 S: 340 S: 341 S: 342 S: ABC-12345 343 S: 54321-XYZ 344 S: 345 S: 346 S: 348 Example poll response with the 349 extension for a URS lock transaction on the domain.example domain 350 name, with the "after" state. The "after" state is reflected in the 351 block: 353 S: 354 S: 355 S: 356 S: 357 S: 358 S: Command completed successfully; ack to dequeue 359 S: 360 S: 361 S: 2013-10-22T14:25:57.0Z 362 S: Registry initiated update of domain. 363 S: 364 S: 365 S: 367 S: domain.example 368 S: EXAMPLE1-REP 369 S: 370 S: 371 S: 372 S: jd1234 373 S: sh8013 374 S: sh8013 375 S: ClientX 376 S: ClientY 377 S: 2012-04-03T22:00:00.0Z 378 S: ClientZ 379 S: 2013-10-22T14:25:57.0Z 380 S: 2014-04-03T22:00:00.0Z 381 S: 382 S: 383 S: 384 S: 387 S: update 388 S: 2013-10-22T14:25:57.0Z 389 S: 12345-XYZ 390 S: URS Admin 391 S: urs123 392 S: URS Lock 393 S: 394 S: 395 S: 396 S: ABC-12345 397 S: 54321-XYZ 398 S: 399 S: 400 S: 401 Example poll response with the 402 extension for a custom "sync" operation on the domain.example domain 403 name, with the default "after" state. The "after" state is reflected 404 in the block: 406 S: 407 S: 408 S: 409 S: 410 S: Command completed successfully; ack to dequeue 411 S: 412 S: 413 S: 2013-10-22T14:25:57.0Z 414 S: Registry initiated Sync of Domain Expiration Date 415 S: 416 S: 417 S: 419 S: domain.example 420 S: EXAMPLE1-REP 421 S: 422 S: jd1234 423 S: sh8013 424 S: sh8013 425 S: ClientX 426 S: ClientY 427 S: 2012-04-03T22:00:00.0Z 428 S: ClientZ 429 S: 2013-10-22T14:25:57.0Z 430 S: 2014-04-03T22:00:00.0Z 431 S: 432 S: 433 S: 434 S: 436 S: custom 437 S: 438 S: 2013-10-22T14:25:57.0Z 439 S: 12345-XYZ 440 S: CSR 441 S: Customer sync request 442 S: 443 S: 444 S: 445 S: 446 S: ABC-12345 447 S: 54321-XYZ 448 S: 449 S: 450 S: 451 Example poll response with the 452 extension for a "delete" operation on the domain.example domain name 453 that is immediately purged, with the default "after" state. The 454 "after" state is reflected in the block: 456 S: 457 S: 458 S: 459 S: 460 S: Command completed successfully; ack to dequeue 461 S: 462 S: 463 S: 2013-10-22T14:25:57.0Z 464 S: Registry initiated delete of 465 S: domain resulting in immediate purge. 466 S: 467 S: 468 S: 470 S: domain.example 471 S: EXAMPLE1-REP 472 S: ClientX 473 S: 474 S: 475 S: 476 S: 478 S: 479 S: delete 480 S: 2013-10-22T14:25:57.0Z 481 S: 12345-XYZ 482 S: ClientZ 483 S: Court order 484 S: 485 S: 486 S: 487 S: ABC-12345 488 S: 54321-XYZ 489 S: 490 S: 491 S: 492 Example poll response with the 493 extension for an "autoPurge" operation on the domain.example domain 494 name that previously had the "pendingDelete" status, with the default 495 "after" state. The "after" state is reflected in the 496 block: 498 S: 499 S: 500 S: 501 S: 502 S: Command completed successfully; ack to dequeue 503 S: 504 S: 505 S: 2013-10-22T14:25:57.0Z 506 S: Registry purged domain with pendingDelete status. 507 S: 508 S: 509 S: 511 S: domain.example 512 S: EXAMPLE1-REP 513 S: ClientX 514 S: 515 S: 516 S: 517 S: 519 S: 520 S: autoPurge 521 S: 2013-10-22T14:25:57.0Z 522 S: 12345-XYZ 523 S: Batch 524 S: 525 S: Past pendingDelete 5 day period 526 S: 527 S: 528 S: 529 S: 530 S: ABC-12345 531 S: 54321-XYZ 532 S: 533 S: 534 S: 535 Example poll response with the 536 extension for an "update" operation on the ns1.domain.example host, 537 with the default "after" state. The "after" state is reflected in 538 the block: 540 S: 541 S: 542 S: 543 S: 544 S: Command completed successfully; ack to dequeue 545 S: 546 S: 547 S: 2013-10-22T14:25:57.0Z 548 S: Registry initiated update of host. 549 S: 550 S: 551 S: 553 S: ns1.domain.example 554 S: NS1_EXAMPLE1-REP 555 S: 556 S: 557 S: 558 S: 192.0.2.2 559 S: 1080:0:0:0:8:800:200C:417A 560 S: ClientX 561 S: ClientY 562 S: 2012-04-03T22:00:00.0Z 563 S: ClientY 564 S: 2013-10-22T14:25:57.0Z 565 S: 566 S: 567 S: 568 S: 570 S: update 571 S: 2013-10-22T14:25:57.0Z 572 S: 12345-XYZ 573 S: ClientZ 574 S: Host Lock 575 S: 576 S: 577 S: 578 S: ABC-12345 579 S: 54321-XYZ 580 S: 581 S: 582 S: 584 3.1.3. EPP Command 586 This extension does not add any elements to the EPP query 587 command or response described in the [RFC5730]. 589 3.2. EPP Transform Commands 591 EPP provides five commands to transform objects: to create 592 an instance of an object, to delete an instance of an 593 object, to extend the validity period of an object, 594 to manage object sponsorship changes, and to 595 change information associated with an object. 597 3.2.1. EPP Command 599 This extension does not add any elements to the EPP command 600 or response described in the [RFC5730]. 602 3.2.2. EPP Command 604 This extension does not add any elements to the EPP command 605 or response described in the [RFC5730]. 607 3.2.3. EPP Command 609 This extension does not add any elements to the EPP command 610 or response described in the [RFC5730]. 612 3.2.4. EPP Command 614 This extension does not add any elements to the EPP 615 command or response described in the [RFC5730]. 617 3.2.5. EPP Command 619 This extension does not add any elements to the EPP command 620 or response described in the [RFC5730]. 622 4. Formal Syntax 624 One schema is presented here that is the EPP Change Poll Extension 625 schema. 627 The formal syntax presented here is a complete schema representation 628 of the object mapping suitable for automated validation of EPP XML 629 instances. The BEGIN and END tags are not part of the schema; they 630 are used to note the beginning and ending of the schema for URI 631 registration purposes. 633 4.1. Change Poll Extension Schema 635 BEGIN 636 637 644 647 648 650 651 652 Extensible Provisioning Protocol v1.0 653 Change Poll Mapping Schema. 654 655 657 660 662 665 666 667 668 669 670 671 673 675 676 678 679 682 683 684 685 686 687 688 689 690 691 692 693 694 695 697 700 701 702 703 704 705 707 710 711 712 713 714 715 716 718 721 722 723 724 726 728 729 730 732 735 736 737 738 739 740 741 743 746 747 748 749 750 751 753 756 757 END 759 5. IANA Considerations 761 5.1. XML Namespace 763 This document uses URNs to describe XML namespaces and XML schemas 764 conforming to a registry mechanism described in [RFC3688]. The 765 following URI assignment is requested of IANA: 767 Registration request for the changePoll namespace: 769 URI: urn:ietf:params:xml:ns:changePoll-1.0 770 Registrant Contact: IESG 771 XML: None. Namespace URIs do not represent an XML specification. 773 Registration request for the changePoll XML schema: 775 URI: urn:ietf:params:xml:ns:changePoll-1.0 776 Registrant Contact: IESG 777 XML: See the "Formal Syntax" section of this document. 779 5.2. EPP Extension Registry 781 The EPP extension described in this document should be registered by 782 the IANA in the EPP Extension Registry described in [RFC7451]. The 783 details of the registration are as follows: 785 Name of Extension: "Change Poll Extension for the Extensible 786 Provisioning Protocol (EPP)" 788 Document status: Standards Track 790 Reference: (insert reference to RFC version of this document) 792 Registrant Name and Email Address: IESG, 794 TLDs: Any 796 IPR Disclosure: None 798 Status: Active 800 Notes: None 802 6. Implementation Status 804 Note to RFC Editor: Please remove this section and the reference to 805 RFC 7942 [RFC7942] before publication. 807 This section records the status of known implementations of the 808 protocol defined by this specification at the time of posting of this 809 Internet-Draft, and is based on a proposal described in RFC 7942 810 [RFC7942]. The description of implementations in this section is 811 intended to assist the IETF in its decision processes in progressing 812 drafts to RFCs. Please note that the listing of any individual 813 implementation here does not imply endorsement by the IETF. 814 Furthermore, no effort has been spent to verify the information 815 presented here that was supplied by IETF contributors. This is not 816 intended as, and must not be construed to be, a catalog of available 817 implementations or their features. Readers are advised to note that 818 other implementations may exist. 820 According to RFC 7942 [RFC7942], "this will allow reviewers and 821 working groups to assign due consideration to documents that have the 822 benefit of running code, which may serve as evidence of valuable 823 experimentation and feedback that have made the implemented protocols 824 more mature. It is up to the individual working groups to use this 825 information as they see fit". 827 6.1. Verisign EPP SDK 829 Organization: Verisign Inc. 831 Name: Verisign EPP SDK 833 Description: The Verisign EPP SDK includes both a full client 834 implementation and a full server stub implementation of draft-ietf- 835 regext-change-poll. 837 Level of maturity: Production 839 Coverage: All aspects of the protocol are implemented. 841 Licensing: GNU Lesser General Public License 843 Contact: jgould@verisign.com 845 URL: https://www.verisign.com/en_US/channel-resources/domain- 846 registry-products/epp-sdks 848 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 850 Organization: Verisign Inc. 852 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 853 System (SRS) 855 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 856 Registry System (SRS) implements the server-side of draft-ietf- 857 regext-change-poll for a variety of Top Level Domains (TLD's). 859 Level of maturity: Production 861 Coverage: The "after" state poll message for an "update" transform 862 operation of a domain name due to server policy. 864 Licensing: Proprietary 866 Contact: jgould@verisign.com 868 6.3. Verisign .COM / .NET SRS 870 Organization: Verisign Inc. 872 Name: Verisign .COM / .NET Shared Registry System (SRS) 874 Description: The Verisign Shared Registry System (SRS) for .COM and 875 .NET implements the server-side of draft-ietf-regext-change-poll. 877 Level of maturity: Production 879 Coverage: The "after" state poll message for an "update" transform 880 operation of a domain name due to server policy. 882 Licensing: Proprietary 884 Contact: jgould@verisign.com 886 6.4. Neustar EPP SDK 888 Organisation: Neustar Inc. 890 Name: Neustar EPP SDK 892 Description: The Neustar EPP SDK includes a full client 893 implementation of draft-ietf-regext-change-poll. 895 Level of maturity: Production 897 Coverage: All client side aspects of the protocol are implemented. 899 Licensing: GNU Lesser General Public License 901 Contact: quoc-anh.np@team.neustar 903 7. Security Considerations 905 The mapping extensions described in this document do not provide any 906 security services beyond those described by EPP [RFC5730] and 907 protocol layers used by EPP. The security considerations described 908 in these other specifications apply to this specification as well. 910 8. Acknowledgements 912 The authors wish to acknowledge the original concept for this draft 913 and the efforts in the initial versions of this draft by Trung Tran 914 and Sharon Wodjenski. 916 Special suggestions that have been incorporated into this document 917 were provided by Scott Hollenbeck, Michael Holloway, and Patrick 918 Mevzek. 920 9. References 922 9.1. Normative References 924 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 925 Requirement Levels", BCP 14, RFC 2119, 926 DOI 10.17487/RFC2119, March 1997, . 929 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 930 DOI 10.17487/RFC3688, January 2004, . 933 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 934 the Extensible Provisioning Protocol (EPP)", RFC 3915, 935 DOI 10.17487/RFC3915, September 2004, . 938 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 939 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 940 . 942 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 943 Domain Name Mapping", STD 69, RFC 5731, 944 DOI 10.17487/RFC5731, August 2009, . 947 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 948 Code: The Implementation Status Section", BCP 205, 949 RFC 7942, DOI 10.17487/RFC7942, July 2016, 950 . 952 [W3C.REC-xmlschema-2-20041028] 953 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 954 Second Edition", World Wide Web Consortium Recommendation 955 REC-xmlschema-2-20041028, October 2004, 956 . 958 9.2. Informative References 960 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 961 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 962 February 2015, . 964 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 965 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 966 May 2017, . 968 Appendix A. Change History 970 A.1. Change from 00 to 01 972 1. Added an optional caseId element that defines the case identifier 973 from UDRP, URS, or custom case, based on feedback from Michael 974 Holloway. 976 A.2. Change from 01 to 02 978 1. Amended XML Namespace section of IANA Considerations, added EPP 979 Extension Registry section. 980 2. Moved Change History to the back section as an Appendix. 982 A.3. Change from 02 to 03 984 1. Fixed "before" state example to use the "before" state value 985 based on feedback from Patrick Mevzek. 987 A.4. Change from 03 to 04 989 1. Updated the authors for the draft. 991 A.5. Change from 04 to 05 993 1. Ping update. 995 A.6. Change from 05 to REGEXT 00 997 1. Changed to regext working group draft by changing draft-gould- 998 change-poll to draft-ietf-regext-change-poll. 1000 A.7. Change from REGEXT 00 to REGEXT 01 1002 1. Ping update. 1004 A.8. Change from REGEXT 01 to REGEXT 02 1006 1. Added the Implementation Status section. 1008 A.9. Change from REGEXT 02 to REGEXT 03 1010 1. Changed Neustar author to Kal Feher. 1012 A.10. Change from REGEXT 03 to REGEXT 04 1014 1. Added Neustar implementation to the Implementation Status 1015 section. 1017 A.11. Change from REGEXT 04 to REGEXT 05 1019 1. Updates based on feedback from Patrick Mevzek, that include: 1021 1. Added a missing comma to "Using this extension, clients" in 1022 the Introduction section. 1023 2. Modified the description of the "transfer", "restore", and 1024 "custom" operations to include "MUST set the "op" attribute" 1025 language. 1026 3. Rephrased the first sentence of the Who section. 1027 4. Added references to the element in the Who 1028 section. 1029 5. Revise the sentence that describes how the extension extends 1030 the info response in the EPP Command section. 1031 6. Refer to EPP Object Mapping as EPP object mapping throughout 1032 the document. 1033 7. Add a Dates and Times section to the Object Attributes 1034 section. 1036 A.12. Change from REGEXT 05 to REGEXT 06 1038 1. Added the "State" sub-section to the "Object Attributes" section 1039 to describe the expected behavior for the "before" and "after" 1040 states, based on feedback from Patrick Mevzek. 1041 2. Added a colon suffix to each hangText entry to provide better 1042 separation. 1044 A.13. Change from REGEXT 06 to REGEXT 07 1046 1. Updates based on feedback from Scott Hollenbeck, that include: 1048 1. Changed MAY to may in the Abstract. 1049 2. Revised the "IANA Considerations" section to include the 1050 registration of the XML schema. 1051 3. Revised the description of the "name" 1052 attribute and the "changePoll:operation> "op" attribute as 1053 containing 7-bit US-ASCII identifiers for the case type or 1054 the operation type, respectively. 1056 A.14. Change from REGEXT 07 to REGEXT 08 1058 1. Updated obsoleted RFC 6982 to RFC 7942. 1059 2. Moved RFC 7451 to an informational reference based on a check 1060 done by the Idnits Tool. 1061 3. Changed Kal Feher's contact e-mail address. 1062 4. Changed Neustar's Implementation Status contact e-mail address. 1064 A.15. Change from REGEXT 08 to REGEXT 09 1066 1. Fixed Section 1.1 (Conventions) to contain the updated language 1067 (e.g. "NOT RECOMMENDED", RFC 8174, BCP 14), based on feedback 1068 from the Document Shepherd. 1070 Authors' Addresses 1072 James Gould 1073 VeriSign, Inc. 1074 12061 Bluemont Way 1075 Reston, VA 20190 1076 US 1078 Email: jgould@verisign.com 1079 URI: http://www.verisigninc.com 1081 Kal Feher 1082 Neustar 1083 lvl 8/10 Queens Road 1084 Melbourne, VIC 3004 1085 AU 1087 Email: ietf@feherfamily.org 1088 URI: http://www.neustar.biz