idnits 2.17.1 draft-ietf-regext-change-poll-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 (January 29, 2018) is 2279 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) ** Obsolete normative reference: RFC 6982 (Obsoleted by RFC 7942) ** Downref: Normative reference to an Informational RFC: RFC 7451 Summary: 2 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: August 2, 2018 Neustar 6 January 29, 2018 8 Change Poll Extension for the Extensible Provisioning Protocol (EPP) 9 draft-ietf-regext-change-poll-07 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 August 2, 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 . . . . . . . . . . . . . . . . . . . 5 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. Normative References . . . . . . . . . . . . . . . . . . . . 23 91 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24 92 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 24 93 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 24 94 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 24 95 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 24 96 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 24 97 A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 24 98 A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 24 99 A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 24 100 A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 24 101 A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25 102 A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 25 103 A.12. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 25 104 A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25 105 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 107 1. Introduction 109 This document describes an extension mapping for version 1.0 of the 110 Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an 111 extension to EPP object mappings like the EPP domain name mapping 112 [RFC5731], is used to notify clients of operations they are not 113 directly involved in, on objects that the client sponsors. It is up 114 to server policy to determine what transform operations and clients 115 to notify. Using this extension, clients can more easily keep their 116 systems in-sync with the objects stored in the server. When a change 117 occurs that a client needs to be notified of, a poll message can be 118 inserted by the server for consumption by the client using the EPP 119 command and response defined in [RFC5730]. The extension 120 supports including a "before" operation poll message and an "after" 121 operation poll message. 123 1.1. Conventions Used in This Document 125 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 126 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 127 document are to be interpreted as described in RFC 2119 [RFC2119]. 129 XML is case sensitive. Unless stated otherwise, XML specifications 130 and examples provided in this document MUST be interpreted in the 131 character case presented in order to develop a conforming 132 implementation. 134 In examples, "C:" represents lines sent by a protocol client and "S:" 135 represents lines returned by a protocol server. Indentation and 136 white space in examples are provided only to illustrate element 137 relationships and are not a REQUIRED feature of this protocol. 139 "changePoll-1.0" is used as an abbreviation for 140 "urn:ietf:params:xml:ns:changePoll-1.0". The XML namespace prefix 141 "changePoll" is used, but implementations MUST NOT depend on it and 142 instead employ a proper namespace-aware XML parser and serializer to 143 interpret and output the XML documents. 145 2. Object Attributes 147 This extension adds additional elements to EPP object mappings like 148 the EPP domain name mapping [RFC5731]. Only those new elements are 149 described here. 151 2.1. Operation 153 An operation consists of any transform operation that impacts objects 154 that the client sponsers and SHOULD be notified of. The 155 element defines the operation. The OPTIONAL 156 "op" attribute is an identifier, represented in the 7-bit US-ASCII 157 character set, that is used to define a sub-operation or the name of 158 a "custom" operation. The enumerated list of 159 values include: 161 "create": Create operation as defined in [RFC5730]. 162 "delete": Delete operation as defined in [RFC5730]. If the delete 163 operation results in an immediate purge of the object, then the 164 "op" attribute MUST be set to "purge". 165 "renew": Renew operation as defined in [RFC5730]. 166 "transfer": Transfer operation as defined in [RFC5730] that MUST set 167 the "op" attribute with one of the possible transfer type values 168 that include "request", "approve", "cancel", or "reject". 169 "update": Update operation as defined in [RFC5730]. 170 "restore": Restore operation as defined in [RFC3915] that MUST set 171 the "op" attribute with one of the possible restore type values 172 that include "request" or "report". 173 "autoRenew": Auto renew operation executed by the server. 174 "autoDelete": Auto delete operation executed by the server. If the 175 "autoDelete" operation results in an immediate purge of the 176 object, then the "op" attribute MUST be set to "purge". 177 "autoPurge": Auto purge operation executed by the server when 178 removing the object after it had the "pendingDelete" status. 179 "custom": Custom operation that MUST set the "op" attribute with the 180 custom operation name. 182 2.2. State 184 The state attribute reflects the state of the object "before" or 185 "after" the operation. The state is defined using the OPTIONAL 186 "state" attribute of the element, with the 187 possible values "before" or "after" and with a default value of 188 "after". The server MAY support both the "before" state and the 189 "after" state of the operation, by using one poll message for the 190 "before" state and one poll message for the "after" state. The 191 "before" state poll message MUST be inserted prior to the "after" 192 state poll message. 194 For operations in Section 2.1 that don't have an "after" state, the 195 server MUST use the "before" state poll message. For example, for 196 the "delete" operation with the "op" attribute set to "purge", or the 197 "autoPurge" operation, the server includes the state of the object 198 prior to being purged in the "before" state poll message. 200 For operations in Section 2.1 that don't have a "before" state, the 201 server MUST use the "after" state poll message. For example, for the 202 "create" operation, the server includes the state of the object after 203 creation in the "after" state poll message. 205 2.3. Who 207 The element defines who executed the operation for 208 audit purposes. The scheme used for the possible set of 209 element values is up to server policy. The server 210 MAY identify the element value based on: 212 "Identifier": Unique user identifier of the user that executed the 213 operation. An example is "ClientX". 214 "Name": Name of the user that executed the operation. An example is 215 "John Doe". 216 "Role": Role of the user that executed operation. An example is 217 "CSR" for a Customer Support Representative or "Batch" for a 218 server batch. 220 2.4. Dates and Times 222 Date and time attribute values MUST be represented in Universal 223 Coordinated Time (UTC) using the Gregorian calendar. The extended 224 date-time form using upper case "T" and "Z" characters defined in 225 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 226 values, as XML Schema does not support truncated date-time forms or 227 lower case "T" and "Z" characters. 229 3. EPP Command Mapping 231 A detailed description of the EPP syntax and semantics can be found 232 in the EPP core protocol specification [RFC5730]. 234 3.1. EPP Query Commands 236 EPP provides three commands to retrieve object information: 237 to determine if an object is known to the server, to retrieve 238 detailed information associated with an object, and to 239 retrieve object transfer status information. 241 3.1.1. EPP Command 243 This extension does not add any elements to the EPP command 244 or response described in the [RFC5730]. 246 3.1.2. EPP Command 248 This extension does not add any elements to the EPP command 249 described in the [RFC5730]. 251 This extension adds operation detail of EPP object mapping operations 252 Section 2.1 to an EPP poll response, as described in [RFC5730], that 253 is an extension of the EPP object mapping info response. Any 254 transform operation to an object defined in an EPP object mapping, by 255 a client other than the sponsoring client, MAY result in extending 256 the response of the object for inserting an EPP poll message 257 with the operation detail. The sponsoring client will then receive 258 the state of the object with operation detail like what, who, when, 259 and why the object was changed. The element 260 contains the operation detail along with an indication of whether the 261 object reflects the state before or after the operation as defined in 262 Section 2.2. The element includes the 263 operation detail with the following child elements: 265 : Transform operation executed on the object 266 as defined in Section 2.1. 267 : Date and time when the operation was executed. 268 : Server transaction identifier of the operation. 269 : Who executed the operation as defined in 270 Section 2.3. 271 : OPTIONAL case identifer associated with the 272 operation. The required "type" attribute defines the type of 273 case. The OPTIONAL "name" attribute is an identifier, 274 represented in the 7-bit US-ASCII character set, that is used to 275 define the name of the "custom" case type. The enumerated list 276 of case types include: 278 udrp: a Uniform Domain-Name Dispute-Resolution Policy (UDRP) 279 case. 280 urs: a Uniform Rapid Suspension (URS) case. 281 custom: A custom case that is defined using the "name" 282 attribute. 283 : OPTIONAL reason for executing the operation. 284 If present, this element contains the server-specific text to 285 help explain the reason the operation was executed. This text 286 MUST be represented in the response language previously 287 negotiated with the client; an OPTIONAL "lang" attribute MAY be 288 present to identify the language if the negotiated value is 289 something other than the default value of "en" (English). 291 Example poll response with the 292 extension for a URS lock transaction on the domain.example domain 293 name, with the "before" state. The "before" state is reflected in 294 the block: 296 S: 297 S: 298 S: 299 S: 300 S: 301 S: Command completed successfully; ack to dequeue 302 S: 303 S: 304 S: 2013-10-22T14:25:57.0Z 305 S: Registry initiated update of domain. 306 S: 307 S: 308 S: 310 S: domain.example 311 S: EXAMPLE1-REP 312 S: 313 S: jd1234 314 S: sh8013 315 S: sh8013 316 S: ClientX 317 S: ClientY 318 S: 2012-04-03T22:00:00.0Z 319 S: 2014-04-03T22:00:00.0Z 320 S: 321 S: 322 S: 323 S: 326 S: update 327 S: 2013-10-22T14:25:57.0Z 328 S: 12345-XYZ 329 S: URS Admin 330 S: urs123 331 S: URS Lock 332 S: 333 S: 334 S: 335 S: ABC-12345 336 S: 54321-XYZ 337 S: 338 S: 339 S: 341 Example poll response with the 342 extension for a URS lock transaction on the domain.example domain 343 name, with the "after" state. The "after" state is reflected in the 344 block: 346 S: 347 S: 348 S: 349 S: 350 S: 351 S: Command completed successfully; ack to dequeue 352 S: 353 S: 354 S: 2013-10-22T14:25:57.0Z 355 S: Registry initiated update of domain. 356 S: 357 S: 358 S: 360 S: domain.example 361 S: EXAMPLE1-REP 362 S: 363 S: 364 S: 365 S: jd1234 366 S: sh8013 367 S: sh8013 368 S: ClientX 369 S: ClientY 370 S: 2012-04-03T22:00:00.0Z 371 S: ClientZ 372 S: 2013-10-22T14:25:57.0Z 373 S: 2014-04-03T22:00:00.0Z 374 S: 375 S: 376 S: 377 S: 380 S: update 381 S: 2013-10-22T14:25:57.0Z 382 S: 12345-XYZ 383 S: URS Admin 384 S: urs123 385 S: URS Lock 386 S: 387 S: 388 S: 389 S: ABC-12345 390 S: 54321-XYZ 391 S: 392 S: 393 S: 394 Example poll response with the 395 extension for a custom "sync" operation on the domain.example domain 396 name, with the default "after" state. The "after" state is reflected 397 in the block: 399 S: 400 S: 401 S: 402 S: 403 S: Command completed successfully; ack to dequeue 404 S: 405 S: 406 S: 2013-10-22T14:25:57.0Z 407 S: Registry initiated Sync of Domain Expiration Date 408 S: 409 S: 410 S: 412 S: domain.example 413 S: EXAMPLE1-REP 414 S: 415 S: jd1234 416 S: sh8013 417 S: sh8013 418 S: ClientX 419 S: ClientY 420 S: 2012-04-03T22:00:00.0Z 421 S: ClientZ 422 S: 2013-10-22T14:25:57.0Z 423 S: 2014-04-03T22:00:00.0Z 424 S: 425 S: 426 S: 427 S: 429 S: custom 430 S: 431 S: 2013-10-22T14:25:57.0Z 432 S: 12345-XYZ 433 S: CSR 434 S: Customer sync request 435 S: 436 S: 437 S: 438 S: 439 S: ABC-12345 440 S: 54321-XYZ 441 S: 442 S: 443 S: 444 Example poll response with the 445 extension for a "delete" operation on the domain.example domain name 446 that is immediately purged, with the default "after" state. The 447 "after" state is reflected in the block: 449 S: 450 S: 451 S: 452 S: 453 S: Command completed successfully; ack to dequeue 454 S: 455 S: 456 S: 2013-10-22T14:25:57.0Z 457 S: Registry initiated delete of 458 S: domain resulting in immediate purge. 459 S: 460 S: 461 S: 463 S: domain.example 464 S: EXAMPLE1-REP 465 S: ClientX 466 S: 467 S: 468 S: 469 S: 471 S: 472 S: delete 473 S: 2013-10-22T14:25:57.0Z 474 S: 12345-XYZ 475 S: ClientZ 476 S: Court order 477 S: 478 S: 479 S: 480 S: ABC-12345 481 S: 54321-XYZ 482 S: 483 S: 484 S: 485 Example poll response with the 486 extension for an "autoPurge" operation on the domain.example domain 487 name that previously had the "pendingDelete" status, with the default 488 "after" state. The "after" state is reflected in the 489 block: 491 S: 492 S: 493 S: 494 S: 495 S: Command completed successfully; ack to dequeue 496 S: 497 S: 498 S: 2013-10-22T14:25:57.0Z 499 S: Registry purged domain with pendingDelete status. 500 S: 501 S: 502 S: 504 S: domain.example 505 S: EXAMPLE1-REP 506 S: ClientX 507 S: 508 S: 509 S: 510 S: 512 S: 513 S: autoPurge 514 S: 2013-10-22T14:25:57.0Z 515 S: 12345-XYZ 516 S: Batch 517 S: 518 S: Past pendingDelete 5 day period 519 S: 520 S: 521 S: 522 S: 523 S: ABC-12345 524 S: 54321-XYZ 525 S: 526 S: 527 S: 528 Example poll response with the 529 extension for an "update" operation on the ns1.domain.example host, 530 with the default "after" state. The "after" state is reflected in 531 the block: 533 S: 534 S: 535 S: 536 S: 537 S: Command completed successfully; ack to dequeue 538 S: 539 S: 540 S: 2013-10-22T14:25:57.0Z 541 S: Registry initiated update of host. 542 S: 543 S: 544 S: 546 S: ns1.domain.example 547 S: NS1_EXAMPLE1-REP 548 S: 549 S: 550 S: 551 S: 192.0.2.2 552 S: 1080:0:0:0:8:800:200C:417A 553 S: ClientX 554 S: ClientY 555 S: 2012-04-03T22:00:00.0Z 556 S: ClientY 557 S: 2013-10-22T14:25:57.0Z 558 S: 559 S: 560 S: 561 S: 563 S: update 564 S: 2013-10-22T14:25:57.0Z 565 S: 12345-XYZ 566 S: ClientZ 567 S: Host Lock 568 S: 569 S: 570 S: 571 S: ABC-12345 572 S: 54321-XYZ 573 S: 574 S: 575 S: 577 3.1.3. EPP Command 579 This extension does not add any elements to the EPP query 580 command or response described in the [RFC5730]. 582 3.2. EPP Transform Commands 584 EPP provides five commands to transform objects: to create 585 an instance of an object, to delete an instance of an 586 object, to extend the validity period of an object, 587 to manage object sponsorship changes, and to 588 change information associated with an object. 590 3.2.1. EPP Command 592 This extension does not add any elements to the EPP command 593 or response described in the [RFC5730]. 595 3.2.2. EPP Command 597 This extension does not add any elements to the EPP command 598 or response described in the [RFC5730]. 600 3.2.3. EPP Command 602 This extension does not add any elements to the EPP command 603 or response described in the [RFC5730]. 605 3.2.4. EPP Command 607 This extension does not add any elements to the EPP 608 command or response described in the [RFC5730]. 610 3.2.5. EPP Command 612 This extension does not add any elements to the EPP command 613 or response described in the [RFC5730]. 615 4. Formal Syntax 617 One schema is presented here that is the EPP Change Poll Extension 618 schema. 620 The formal syntax presented here is a complete schema representation 621 of the object mapping suitable for automated validation of EPP XML 622 instances. The BEGIN and END tags are not part of the schema; they 623 are used to note the beginning and ending of the schema for URI 624 registration purposes. 626 4.1. Change Poll Extension Schema 628 BEGIN 629 630 637 640 641 643 644 645 Extensible Provisioning Protocol v1.0 646 Change Poll Mapping Schema. 647 648 650 653 655 658 659 660 661 662 663 664 666 668 669 671 672 675 676 677 678 679 680 681 682 683 684 685 686 687 688 690 693 694 695 696 697 698 700 703 704 705 706 707 708 709 711 714 715 716 717 719 721 722 723 725 728 729 730 731 732 733 734 736 739 740 741 742 743 744 746 749 750 END 752 5. IANA Considerations 754 5.1. XML Namespace 756 This document uses URNs to describe XML namespaces and XML schemas 757 conforming to a registry mechanism described in [RFC3688]. The 758 following URI assignment is requested of IANA: 760 Registration request for the changePoll namespace: 762 URI: urn:ietf:params:xml:ns:changePoll-1.0 763 Registrant Contact: IESG 764 XML: None. Namespace URIs do not represent an XML specification. 766 Registration request for the changePoll XML schema: 768 URI: urn:ietf:params:xml:ns:changePoll-1.0 769 Registrant Contact: IESG 770 XML: See the "Formal Syntax" section of this document. 772 5.2. EPP Extension Registry 774 The EPP extension described in this document should be registered by 775 the IANA in the EPP Extension Registry described in [RFC7451]. The 776 details of the registration are as follows: 778 Name of Extension: "Change Poll Extension for the Extensible 779 Provisioning Protocol (EPP)" 781 Document status: Standards Track 783 Reference: (insert reference to RFC version of this document) 785 Registrant Name and Email Address: IESG, 787 TLDs: Any 789 IPR Disclosure: None 791 Status: Active 793 Notes: None 795 6. Implementation Status 797 Note to RFC Editor: Please remove this section and the reference to 798 RFC 6982 [RFC6982] before publication. 800 This section records the status of known implementations of the 801 protocol defined by this specification at the time of posting of this 802 Internet-Draft, and is based on a proposal described in RFC 6982 803 [RFC6982]. The description of implementations in this section is 804 intended to assist the IETF in its decision processes in progressing 805 drafts to RFCs. Please note that the listing of any individual 806 implementation here does not imply endorsement by the IETF. 807 Furthermore, no effort has been spent to verify the information 808 presented here that was supplied by IETF contributors. This is not 809 intended as, and must not be construed to be, a catalog of available 810 implementations or their features. Readers are advised to note that 811 other implementations may exist. 813 According to RFC 6982 [RFC6982], "this will allow reviewers and 814 working groups to assign due consideration to documents that have the 815 benefit of running code, which may serve as evidence of valuable 816 experimentation and feedback that have made the implemented protocols 817 more mature. It is up to the individual working groups to use this 818 information as they see fit". 820 6.1. Verisign EPP SDK 822 Organization: Verisign Inc. 824 Name: Verisign EPP SDK 826 Description: The Verisign EPP SDK includes both a full client 827 implementation and a full server stub implementation of draft-ietf- 828 regext-change-poll. 830 Level of maturity: Production 832 Coverage: All aspects of the protocol are implemented. 834 Licensing: GNU Lesser General Public License 836 Contact: jgould@verisign.com 838 URL: https://www.verisign.com/en_US/channel-resources/domain- 839 registry-products/epp-sdks 841 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 843 Organization: Verisign Inc. 845 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 846 System (SRS) 848 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 849 Registry System (SRS) implements the server-side of draft-ietf- 850 regext-change-poll for a variety of Top Level Domains (TLD's). 852 Level of maturity: Production 854 Coverage: The "after" state poll message for an "update" transform 855 operation of a domain name due to server policy. 857 Licensing: Proprietary 859 Contact: jgould@verisign.com 861 6.3. Verisign .COM / .NET SRS 863 Organization: Verisign Inc. 865 Name: Verisign .COM / .NET Shared Registry System (SRS) 867 Description: The Verisign Shared Registry System (SRS) for .COM and 868 .NET implements the server-side of draft-ietf-regext-change-poll. 870 Level of maturity: Production 872 Coverage: The "after" state poll message for an "update" transform 873 operation of a domain name due to server policy. 875 Licensing: Proprietary 877 Contact: jgould@verisign.com 879 6.4. Neustar EPP SDK 881 Organisation: Neustar Inc. 883 Name: Neustar EPP SDK 885 Description: The Neustar EPP SDK includes a full client 886 implementation of draft-ietf-regext-change-poll. 888 Level of maturity: Production 890 Coverage: All client side aspects of the protocol are implemented. 892 Licensing: GNU Lesser General Public License 894 Contact: kal.feher@team.neustar 896 7. Security Considerations 898 The mapping extensions described in this document do not provide any 899 security services beyond those described by EPP [RFC5730] and 900 protocol layers used by EPP. The security considerations described 901 in these other specifications apply to this specification as well. 903 8. Acknowledgements 905 The authors wish to acknowledge the original concept for this draft 906 and the efforts in the initial versions of this draft by Trung Tran 907 and Sharon Wodjenski. 909 Special suggestions that have been incorporated into this document 910 were provided by Scott Hollenbeck, Michael Holloway, and Patrick 911 Mevzek. 913 9. Normative References 915 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 916 Requirement Levels", BCP 14, RFC 2119, 917 DOI 10.17487/RFC2119, March 1997, . 920 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 921 DOI 10.17487/RFC3688, January 2004, . 924 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 925 the Extensible Provisioning Protocol (EPP)", RFC 3915, 926 DOI 10.17487/RFC3915, September 2004, . 929 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 930 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 931 . 933 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 934 Domain Name Mapping", STD 69, RFC 5731, 935 DOI 10.17487/RFC5731, August 2009, . 938 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 939 Code: The Implementation Status Section", RFC 6982, 940 DOI 10.17487/RFC6982, July 2013, . 943 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 944 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 945 February 2015, . 947 [W3C.REC-xmlschema-2-20041028] 948 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 949 Second Edition", World Wide Web Consortium Recommendation 950 REC-xmlschema-2-20041028, October 2004, 951 . 953 Appendix A. Change History 955 A.1. Change from 00 to 01 957 1. Added an optional caseId element that defines the case identifier 958 from UDRP, URS, or custom case, based on feedback from Michael 959 Holloway. 961 A.2. Change from 01 to 02 963 1. Amended XML Namespace section of IANA Considerations, added EPP 964 Extension Registry section. 965 2. Moved Change History to the back section as an Appendix. 967 A.3. Change from 02 to 03 969 1. Fixed "before" state example to use the "before" state value 970 based on feedback from Patrick Mevzek. 972 A.4. Change from 03 to 04 974 1. Updated the authors for the draft. 976 A.5. Change from 04 to 05 978 1. Ping update. 980 A.6. Change from 05 to REGEXT 00 982 1. Changed to regext working group draft by changing draft-gould- 983 change-poll to draft-ietf-regext-change-poll. 985 A.7. Change from REGEXT 00 to REGEXT 01 987 1. Ping update. 989 A.8. Change from REGEXT 01 to REGEXT 02 991 1. Added the Implementation Status section. 993 A.9. Change from REGEXT 02 to REGEXT 03 995 1. Changed Neustar author to Kal Feher. 997 A.10. Change from REGEXT 03 to REGEXT 04 999 1. Added Neustar implementation to the Implementation Status 1000 section. 1002 A.11. Change from REGEXT 04 to REGEXT 05 1004 1. Updates based on feedback from Patrick Mevzek, that include: 1006 1. Added a missing comma to "Using this extension, clients" in 1007 the Introduction section. 1008 2. Modified the description of the "transfer", "restore", and 1009 "custom" operations to include "MUST set the "op" attribute" 1010 language. 1011 3. Rephrased the first sentence of the Who section. 1012 4. Added references to the element in the Who 1013 section. 1014 5. Revise the sentence that describes how the extension extends 1015 the info response in the EPP Command section. 1016 6. Refer to EPP Object Mapping as EPP object mapping throughout 1017 the document. 1018 7. Add a Dates and Times section to the Object Attributes 1019 section. 1021 A.12. Change from REGEXT 05 to REGEXT 06 1023 1. Added the "State" sub-section to the "Object Attributes" section 1024 to describe the expected behavior for the "before" and "after" 1025 states, based on feedback from Patrick Mevzek. 1026 2. Added a colon suffix to each hangText entry to provide better 1027 separation. 1029 A.13. Change from REGEXT 06 to REGEXT 07 1031 1. Updates based on feedback from Scott Hollenbeck, that include: 1033 1. Changed MAY to may in the Abstract. 1034 2. Revised the "IANA Considerations" section to include the 1035 registration of the XML schema. 1036 3. Revised the description of the "name" 1037 attribute and the "changePoll:operation> "op" attribute as 1038 containing 7-bit US-ASCII identifiers for the case type or 1039 the operation type, respectively. 1041 Authors' Addresses 1043 James Gould 1044 VeriSign, Inc. 1045 12061 Bluemont Way 1046 Reston, VA 20190 1047 US 1049 Email: jgould@verisign.com 1050 URI: http://www.verisigninc.com 1052 Kal Feher 1053 Neustar 1054 lvl 8/10 Queens Road 1055 Melbourne, VIC 3004 1056 AU 1058 Email: kal.feher@team.neustar 1059 URI: http://www.neustar.biz