--- 1/draft-ietf-regext-change-poll-04.txt 2018-01-02 07:14:07.498420125 -0800 +++ 2/draft-ietf-regext-change-poll-05.txt 2018-01-02 07:14:07.698424868 -0800 @@ -1,19 +1,19 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track K. Feher -Expires: April 21, 2018 Neustar - October 18, 2017 +Expires: July 6, 2018 Neustar + January 2, 2018 Change Poll Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-change-poll-04 + draft-ietf-regext-change-poll-05 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension for notifying clients of operations on client sponsored objects that were not initiated by the client through EPP. These operations MAY include contractual or policy requirements including but not limited to regular batch processes, customer support actions, Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid Suspension (URS) actions, court directed actions, and bulk updates @@ -31,44 +31,45 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 21, 2018. + This Internet-Draft will expire on July 6, 2018. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Operation . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Who . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 2.3. Dates and Times . . . . . . . . . . . . . . . . . . . . . 5 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 5 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 5 3.1.3. EPP Command . . . . . . . . . . . . . . . 15 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15 3.2.1. EPP Command . . . . . . . . . . . . . . . . 15 3.2.2. EPP Command . . . . . . . . . . . . . . . . 15 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 15 3.2.4. EPP Command . . . . . . . . . . . . . . . 15 @@ -81,40 +82,41 @@ 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 20 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 20 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 20 6.4. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 21 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 9. Normative References . . . . . . . . . . . . . . . . . . . . 22 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 22 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 22 - A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 22 + A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 23 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 23 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 23 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 23 A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 23 A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 23 A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 23 A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 23 A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 23 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 + A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 23 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an extension to EPP object mappings like the EPP domain name mapping [RFC5731], is used to notify clients of operations they are not directly involved in, on objects that the client sponsors. It is up to server policy to determine what transform operations and clients - to notify. Using this extension clients can more easily keep their + to notify. Using this extension, clients can more easily keep their systems in-sync with the objects stored in the server. When a change occurs that a client needs to be notified of, a poll message can be inserted by the server for consumption by the client using the EPP command and response defined in [RFC5730]. The extension supports including a "before" operation poll message and an "after" operation poll message. 1.1. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", @@ -150,52 +152,61 @@ element defines the operation. The OPTIONAL "op" attribute is used to define a sub-operation or the name of a "custom" operation. The enumerated list of values include: "create" Create operation as defined in [RFC5730]. "delete" Delete operation as defined in [RFC5730]. If the delete operation results in an immediate purge of the object, then the "op" attribute MUST be set to "purge". "renew" Renew operation as defined in [RFC5730]. - "transfer" Transfer operation as defined in [RFC5730] with the - OPTIONAL "op" attribute defining the transfer type with the - possible values of "request", "approve", "cancel", and "reject". + "transfer" Transfer operation as defined in [RFC5730] that MUST set + the "op" attribute with one of the possible transfer type values + that include "request", "approve", "cancel", or "reject". "update" Update operation as defined in [RFC5730]. - "restore" Restore operation as defined in [RFC3915] with the - OPTIONAL "op" attribute defining the restore type with the - possible values of "request" and "report". + "restore" Restore operation as defined in [RFC3915] that MUST set + the "op" attribute with one of the possible restore type values + that include "request" or "report". "autoRenew" Auto renew operation executed by the server. "autoDelete" Auto delete operation executed by the server. If the "autoDelete" operation results in an immediate purge of the object, then the "op" attribute MUST be set to "purge". "autoPurge" Auto purge operation executed by the server when removing the object after it had the "pendingDelete" status. - "custom" Custom operation that uses the "op" attribute to define the + "custom" Custom operation that MUST set the "op" attribute with the custom operation name. 2.2. Who - Who defines who executed the operation for audit purposes, and is - represented using the element. The scheme used for - the possible set of Who values is up to server policy. The server - MAY identify Who based on: + The element defines who executed the operation for + audit purposes. The scheme used for the possible set of + element values is up to server policy. The server + MAY identify the element value based on: "Identifier" Unique user identifier of the user that executed the operation. An example is "ClientX". "Name" Name of the user that executed the operation. An example is "John Doe". "Role" Role of the user that executed operation. An example is "CSR" for a Customer Support Representative or "Batch" for a server batch. +2.3. Dates and Times + + Date and time attribute values MUST be represented in Universal + Coordinated Time (UTC) using the Gregorian calendar. The extended + date-time form using upper case "T" and "Z" characters defined in + [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time + values, as XML Schema does not support truncated date-time forms or + lower case "T" and "Z" characters. + 3. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. 3.1. EPP Query Commands EPP provides three commands to retrieve object information: to determine if an object is known to the server, to retrieve detailed information associated with an object, and to @@ -204,40 +215,41 @@ 3.1.1. EPP Command This extension does not add any elements to the EPP command or response described in the [RFC5730]. 3.1.2. EPP Command This extension does not add any elements to the EPP command described in the [RFC5730]. - This extension adds transaction detail of the operations to the EPP - poll response, as described in [RFC5730], of an EPP Object - Mapping like [RFC5731]. Any transform operation to an object defined - in an EPP Object Mapping, by a client other than the sponsoring - client, MAY result in extending the response of the object for - inserting an EPP poll message with the operation detail. The - sponsoring client will then receive the state of the object with - operation detail like what, who, when, and why the object was - changed. The element contains the operation - detail along with an indication of whether the object reflects the - state before or after the operation, using the OPTIONAL "state" - attribute, with the possible values of "before" or "after", and with - a default value of "after". The "state" attribute describes the - state of the response data or block returned in the poll - response. The server MAY support providing the "before" state and - "after" state to the operation, by using one poll message for the - "before" state and one poll message for the "after" state. When - using the "before" state poll message, it MUST be inserted prior to - the "after" state poll message. The element - includes the operation detail with the following child elements: + This extension adds operation detail of EPP object mapping operations + Section 2.1 to an EPP poll response, as described in [RFC5730], that + is an extension of the EPP object mapping info response. Any + transform operation to an object defined in an EPP object mapping, by + a client other than the sponsoring client, MAY result in extending + the response of the object for inserting an EPP poll message + with the operation detail. The sponsoring client will then receive + the state of the object with operation detail like what, who, when, + and why the object was changed. The element + contains the operation detail along with an indication of whether the + object reflects the state before or after the operation, using the + OPTIONAL "state" attribute, with the possible values of "before" or + "after", and with a default value of "after". The "state" attribute + describes the state of the response data or block returned + in the poll response. The server MAY support providing the "before" + state and "after" state to the operation, by using one poll message + for the "before" state and one poll message for the "after" state. + When using the "before" state poll message, it MUST be inserted prior + to the "after" state poll message. The + element includes the operation detail with the following child + elements: Transform operation executed on the object as defined in Section 2.1. Date and time when the operation was executed. Server transaction identifier of the operation. Who executed the operation as defined in Section 2.2. OPTIONAL case identifer associated with the operation. The required "type" attribute defines the type of case with an enumerated list of case types including: @@ -860,21 +872,21 @@ protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. 8. Acknowledgements The authors wish to acknowledge the original concept for this draft and the efforts in the initial versions of this draft by Trung Tran and Sharon Wodjenski. Special suggestions that have been incorporated into this document - were provided by Michael Holloway. + were provided by Michael Holloway and Patrick Mevzek. 9. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, . + [W3C.REC-xmlschema-2-20041028] + Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes + Second Edition", World Wide Web Consortium Recommendation + REC-xmlschema-2-20041028, October 2004, + . + Appendix A. Change History A.1. Change from 00 to 01 1. Added an optional caseId element that defines the case identifier from UDRP, URS, or custom case, based on feedback from Michael Holloway. A.2. Change from 01 to 02 @@ -945,20 +963,40 @@ A.9. Change from REGEXT 02 to REGEXT 03 1. Changed Neustar author to Kal Feher. A.10. Change from REGEXT 03 to REGEXT 04 1. Added Neustar implementation to the Implementation Status section. +A.11. Change from REGEXT 04 to REGEXT 05 + + 1. Updates based on feedback from Patrick Mevzek, that include: + + 1. Added a missing comma to "Using this extension, clients" in + the Introduction section. + + 2. Modified the description of the "transfer", "restore", and + "custom" operations to include "MUST set the "op" attribute" + language. + 3. Rephrased the first sentence of the Who section. + 4. Added references to the element in the Who + section. + 5. Revise the sentence that describes how the extension extends + the info response in the EPP Command section. + 6. Refer to EPP Object Mapping as EPP object mapping throughout + the document. + 7. Add a Dates and Times section to the Object Attributes + section. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com