draft-ietf-regext-change-poll-12.txt   rfc8590.txt 
Network Working Group J. Gould Internet Engineering Task Force (IETF) J. Gould
Internet-Draft VeriSign, Inc. Request for Comments: 8590 VeriSign, Inc.
Intended status: Standards Track K. Feher Category: Standards Track K. Feher
Expires: July 8, 2019 Neustar ISSN: 2070-1721 Neustar
January 4, 2019 May 2019
Change Poll Extension for the Extensible Provisioning Protocol (EPP) Change Poll Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-change-poll-12
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension for notifying clients of operations on client-sponsored extension for notifying clients of operations on client-sponsored
objects that were not initiated by the client through EPP. These objects that were not initiated by the client through EPP. These
operations may include contractual or policy requirements including operations may include contractual or policy requirements including,
but not limited to regular batch processes, customer support actions, but not limited to, regular batch processes, customer support
Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid actions, Uniform Domain-Name Dispute-Resolution Policy (UDRP) or
Suspension (URS) actions, court-directed actions, and bulk updates Uniform Rapid Suspension (URS) actions, court-directed actions, and
based on customer requests. Since the client is not directly bulk updates based on customer requests. Since the client is not
involved or knowledgable of these operations, the extension is used directly involved or knowledgable of these operations, the extension
along with an EPP object mapping to provide the resulting state of is used along with an EPP object mapping to provide the resulting
the post-operation object, and optionally a pre-operation object, state of the postoperation object, and optionally a preoperation
with the operation meta-data of what, when, who, and why. object, with the operation metadata of what, when, who, and why.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on July 8, 2019. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8590.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Operation . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Operation . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. State . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. State . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Who . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Who . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 5
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6
3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 6 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 6
3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 16 3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 14
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 14
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 14
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 16 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 14
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 16 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 14
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 16 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 14
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 16 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 14
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1. Change Poll Extension Schema . . . . . . . . . . . . . . 17 4.1. Change Poll Extension Schema . . . . . . . . . . . . . . 15
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 19 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 20 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19
6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 21 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 21 7.1. Normative References . . . . . . . . . . . . . . . . . . 19
6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 22 7.2. Informative References . . . . . . . . . . . . . . . . . 20
6.4. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 22 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20
7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.1. Normative References . . . . . . . . . . . . . . . . . . 23
9.2. Informative References . . . . . . . . . . . . . . . . . 24
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 24
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 24
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 24
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 24
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 24
A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 24
A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 24
A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 25
A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 25
A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25
A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 25
A.12. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 25
A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25
A.14. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 26
A.15. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 26
A.16. Change from REGEXT 09 to REGEXT 10 . . . . . . . . . . . 26
A.17. Change from REGEXT 10 to REGEXT 11 . . . . . . . . . . . 27
A.18. Change from REGEXT 11 to REGEXT 12 . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an
extension to EPP object mappings like the EPP domain name mapping extension to EPP object mappings like the EPP domain name mapping
[RFC5731], is used to notify clients of operations they are not [RFC5731], is used to notify clients of operations they are not
directly involved in, on objects that the client sponsors. It is up directly involved in, on objects that the client sponsors. It is up
to server policy to determine what transform operations and clients 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 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 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 inserted by the server for consumption by the client using the EPP
<poll> command and response defined in [RFC5730]. The extension <poll> command and response defined in [RFC5730]. The extension
supports including a "before" operation poll message and an "after" supports including a "before" operation poll message and an "after"
operation poll message. The extension only extends the EPP <poll> operation poll message. The extension only extends the EPP <poll>
response in [RFC5730] and does not extend the EPP <poll> command. response in [RFC5730] and does not extend the EPP <poll> command.
Please refer to [RFC5730] for information and examples of the EPP Please refer to [RFC5730] for information and examples of the EPP
<poll> command. <poll> command.
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented in order to develop a conforming character case presented in order to develop a conforming
implementation. implementation.
In examples, "C:" represents lines sent by a protocol client and "S:" In examples, "C:" represents lines sent by a protocol client, and
represents lines returned by a protocol server. Indentation and "S:" represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element white space in examples are provided only to illustrate element
relationships and are not a REQUIRED feature of this protocol. relationships and are not a REQUIRED feature of this protocol.
The XML namespace prefix "changePoll" is used for the namespace The XML namespace prefix "changePoll" is used for the namespace
"urn:ietf:params:xml:ns:changePoll-1.0", but implementations MUST NOT "urn:ietf:params:xml:ns:changePoll-1.0", but implementations MUST NOT
depend on it and instead employ a proper namespace-aware XML parser depend on it; instead, they should employ a proper namespace-aware
and serializer to interpret and output the XML documents. XML parser and serializer to interpret and output the XML documents.
2. Object Attributes 2. Object Attributes
This extension adds additional elements to EPP object mappings like This extension adds additional elements to EPP object mappings like
the EPP domain name mapping [RFC5731]. Only those new elements are the EPP domain name mapping [RFC5731]. Only those new elements are
described here. described here.
2.1. Operation 2.1. Operation
An operation consists of any transform operation that impacts objects An operation consists of any transform operation that impacts objects
that the client sponsers and should be notified of. The that the client sponsors and should be notified of. The
<changePoll:operation> element defines the operation. The OPTIONAL <changePoll:operation> element defines the operation. The OPTIONAL
"op" attribute is an identifier, represented in the 7-bit US-ASCII "op" attribute is an identifier, represented in the 7-bit US-ASCII
character set defined in [RFC0020], that is used to define a sub- character set defined in [RFC20], that is used to define a sub-
operation or the name of a "custom" operation. The enumerated list operation or the name of a "custom" operation. The enumerated list
of <changePoll:operation> values is: of <changePoll:operation> values is:
"create": Create operation as defined in [RFC5730]. "create": Create operation as defined in [RFC5730].
"delete": Delete operation as defined in [RFC5730]. If the delete "delete": Delete operation as defined in [RFC5730]. If the delete
operation results in an immediate purge of the object, then the operation results in an immediate purge of the object, then the
"op" attribute MUST be set to "purge". "op" attribute MUST be set to "purge".
"renew": Renew operation as defined in [RFC5730]. "renew": Renew operation as defined in [RFC5730].
"transfer": Transfer operation as defined in [RFC5730] that MUST set "transfer": Transfer operation as defined in [RFC5730] that MUST set
the "op" attribute with one of the possible transfer type values the "op" attribute with one of the possible transfer-type values;
that include "request", "approve", "cancel", or "reject". these include "request", "approve", "cancel", or "reject".
"update": Update operation as defined in [RFC5730]. "update": Update operation as defined in [RFC5730].
"restore": Restore operation as defined in [RFC3915] that MUST set "restore": Restore operation as defined in [RFC3915] that MUST set
the "op" attribute with one of the possible restore type values the "op" attribute with one of the possible restore-type values;
that include "request" or "report". these include "request" or "report".
"autoRenew": Auto renew operation executed by the server. "autoRenew": Auto renew operation executed by the server.
"autoDelete": Auto delete operation executed by the server. If the "autoDelete": Auto delete operation executed by the server. If the
"autoDelete" operation results in an immediate purge of the "autoDelete" operation results in an immediate purge of the
object, then the "op" attribute MUST be set to "purge". object, then the "op" attribute MUST be set to "purge".
"autoPurge": Auto purge operation executed by the server when "autoPurge": Auto purge operation executed by the server when
removing the object after it had the "pendingDelete" status. removing the object after it has had the status "pendingDelete".
"custom": Custom operation that MUST set the "op" attribute with the "custom": Custom operation that MUST set the "op" attribute with the
custom operation name. The custom operations supported is up to custom operation name. The custom operations supported are up to
server policy. server policy.
2.2. State 2.2. State
The state attribute reflects the state of the object "before" or The state attribute reflects the state of the object "before" or
"after" the operation. The state is defined using the OPTIONAL "after" the operation. The state is defined using the OPTIONAL
"state" attribute of the <changePoll:changeData> element, with the "state" attribute of the <changePoll:changeData> element, with the
possible values "before" or "after" and with a default value of possible values "before" or "after" and a default value of "after".
"after". The server MAY support both the "before" state and the The server MAY support both the "before" state and the "after" state
"after" state of the operation, by using one poll message for the of the operation by using one poll message for the "before" state and
"before" state and one poll message for the "after" state. The one poll message for the "after" state. The "before" state poll
"before" state poll message MUST be inserted into the message queue message MUST be inserted into the message queue prior to the "after"
prior to the "after" state poll message. state poll message.
For operations in Section 2.1 that don't have an "after" state, the For operations in Section 2.1 that don't have an "after" state, the
server MUST use the "before" state poll message. For example, for server MUST use the "before" state poll message. For example, for
the "delete" operation with the "op" attribute set to "purge", or the the "delete" operation with the "op" attribute set to "purge", or the
"autoPurge" operation, the server includes the state of the object "autoPurge" operation, the server includes the state of the object
prior to being purged in the "before" state poll message. prior to being purged in the "before" state poll message.
For operations in Section 2.1 that don't have a "before" state, the For operations in Section 2.1 that don't have a "before" state, the
server MUST use the "after" state poll message. For example, for the server MUST use the "after" state poll message. For example, for the
"create" operation, the server includes the state of the object after "create" operation, the server includes the state of the object after
creation in the "after" state poll message. creation in the "after" state poll message.
2.3. Who 2.3. Who
The <changePoll:who> element defines who executed the operation for The <changePoll:who> element defines who executed the operation, for
audit purposes. It is a freeform value that is strictly meant for audit purposes. It is a free-form value that is meant strictly for
audit purposes and not meant to drive client-side logic. The scheme audit purposes and not to drive client-side logic. The scheme used
used for the possible set of <changePoll:who> element values is up to for the possible set of <changePoll:who> element values is up to
server policy. The server MAY identify the <changePoll:who> element server policy. The server MAY identify the <changePoll:who> element
value based on: value based on:
"Identifier": Unique user identifier of the user that executed the "Identifier": Unique user identifier of the user that executed the
operation. An example is "ClientX". operation. An example is "ClientX".
"Name": Name of the user that executed the operation. An example is "Name": Name of the user that executed the operation. An example is
"John Doe". "John Doe".
"Role": Role of the user that executed operation. An example is "Role": Role of the user that executed operation. An example is
"CSR" for a Customer Support Representative or "Batch" for a "CSR" for a Customer Support Representative or "Batch" for a
server batch. server batch.
2.4. Dates and Times 2.4. Dates and Times
Date and time attribute values MUST be represented in Universal Date and time attribute values MUST be represented in Universal
Coordinated Time (UTC) using the Gregorian calendar. The extended Coordinated Time (UTC) using the Gregorian calendar. The extended
date-time form using upper case "T" and "Z" characters defined in date-time form using uppercase "T" and "Z" characters defined in
[W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time
values, as XML Schema does not support truncated date-time forms or values, as XML Schema does not support truncated date-time forms or
lower case "T" and "Z" characters. lowercase "T" and "Z" characters.
3. EPP Command Mapping 3. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. in the EPP core protocol specification [RFC5730].
3.1. EPP Query Commands 3.1. EPP Query Commands
EPP provides three commands to retrieve object information: <check> EPP provides three commands to retrieve object information: <check>
to determine if an object is known to the server, <info> to retrieve to determine if an object is known to the server, <info> to retrieve
detailed information associated with an object, and <transfer> to detailed information associated with an object, and <transfer> to
retrieve object transfer status information. retrieve object-transfer status information.
3.1.1. EPP <check> Command 3.1.1. EPP <check> Command
This extension does not add any elements to the EPP <check> command This extension does not add any elements to the EPP <check> command
or <check> response described in the [RFC5730]. or <check> response described in [RFC5730].
3.1.2. EPP <info> Command 3.1.2. EPP <info> Command
This extension does not add any elements to the EPP <info> command This extension does not add any elements to the EPP <info> command
described in the [RFC5730]. described in [RFC5730].
This extension adds operation detail of EPP object mapping operations This extension adds operational detail of EPP object-mapping
Section 2.1 to an EPP poll response, as described in [RFC5730]. The operations (Section 2.1) to an EPP poll response, as described in
extension is an extension of the EPP object mapping info response. [RFC5730]. It is an extension of the EPP object-mapping info
Any transform operation to an object defined in an EPP object mapping response. Any transform operation to an object defined in an EPP
by a client other than the sponsoring client MAY result in extending object mapping by a client other than the sponsoring client MAY
the <info> response of the object for inserting an EPP poll message result in extending the <info> response of the object for inserting
with the operation detail. The sponsoring client will then receive an EPP poll message with the operation detail. The sponsoring client
the state of the object with operation detail like what, who, when, will then receive the state of the object with operation detail like
and why the object was changed. The <changePoll:changeData> element what, who, when, and why the object was changed. The
contains the operation detail along with an indication of whether the <changePoll:changeData> element contains the operation detail along
object reflects the state before or after the operation as defined in with an indication of whether the object reflects the state before or
Section 2.2. The <changePoll:changeData> element includes the after the operation as defined in Section 2.2. The
operation detail with the following child elements: <changePoll:changeData> element includes the operation detail with
the following child elements:
<changePoll:operation>: Transform operation executed on the object <changePoll:operation>: Transform operation executed on the object,
as defined in Section 2.1. as defined in Section 2.1.
<changePoll:date>: Date and time when the operation was executed. <changePoll:date>: Date and time when the operation was executed.
<changePoll:svTRID>: Server transaction identifier of the operation. <changePoll:svTRID>: Server transaction identifier of the operation.
<changePoll:who>: Who executed the operation as defined in
<changePoll:who>: Who executed the operation, as defined in
Section 2.3. Section 2.3.
<changePoll:caseId>: OPTIONAL case identifer associated with the
<changePoll:caseId>: OPTIONAL case identifier associated with the
operation. The required "type" attribute defines the type of operation. The required "type" attribute defines the type of
case. The OPTIONAL "name" attribute is an identifier, case. The OPTIONAL "name" attribute is an identifier,
represented in the 7-bit US-ASCII character set defined in represented in the 7-bit US-ASCII character set defined in
[RFC0020], that is used to define the name of the "custom" case [RFC20], that is used to define the name of the "custom" case
type. The enumerated list of case types is: type. The enumerated list of case types is:
udrp: a Uniform Domain-Name Dispute-Resolution Policy (UDRP) udrp: A Uniform Domain-Name Dispute-Resolution Policy (UDRP)
case. case.
urs: a Uniform Rapid Suspension (URS) case.
urs: A Uniform Rapid Suspension (URS) case.
custom: A custom case that is defined using the "name" custom: A custom case that is defined using the "name"
attribute. attribute.
<changePoll:reason>: OPTIONAL reason for executing the operation. <changePoll:reason>: OPTIONAL reason for executing the operation.
If present, this element contains the server-specific text to If present, this element contains the server-specific text to
help explain the reason the operation was executed. This text help explain the reason the operation was executed. This text
MUST be represented in the response language previously MUST be represented in the response language previously
negotiated with the client; an OPTIONAL "lang" attribute MAY be negotiated with the client; an OPTIONAL "lang" attribute MAY be
present to identify the language if the negotiated value is present to identify the language if the negotiated value is
something other than the default value of "en" (English). something other than the default value of "en" (English).
Example poll <info> response with the <changePoll:changeData> The following is an example poll <info> response with the
extension for a URS lock transaction on the domain.example domain <changePoll:changeData> extension for a URS lock transaction on the
name, with the "before" state. The "before" state is reflected in domain.example domain name, with the "before" state. The "before"
the <resData> block: state is reflected in the <resData> block:
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg lang="en-US"> S: <msg lang="en-US">
S: Command completed successfully; ack to dequeue</msg> S: Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ id="201" count="1"> S: <msgQ id="201" count="1">
S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <qDate>2013-10-22T14:25:57.0Z</qDate>
skipping to change at page 8, line 50 skipping to change at page 8, line 32
S: <changePoll:reason>URS Lock</changePoll:reason> S: <changePoll:reason>URS Lock</changePoll:reason>
S: </changePoll:changeData> S: </changePoll:changeData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Example poll <info> response with the <changePoll:changeData> The following is an example poll <info> response with the
extension for a URS lock transaction on the domain.example domain <changePoll:changeData> extension for a URS lock transaction on the
name, with the "after" state. The "after" state is reflected in the domain.example domain name, with the "after" state. The "after"
<resData> block: state is reflected in the <resData> block:
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg lang="en-US"> S: <msg lang="en-US">
S: Command completed successfully; ack to dequeue</msg> S: Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ id="202" count="1"> S: <msgQ id="202" count="1">
S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <qDate>2013-10-22T14:25:57.0Z</qDate>
skipping to change at page 11, line 4 skipping to change at page 9, line 37
S: <changePoll:caseId type="urs">urs123</changePoll:caseId> S: <changePoll:caseId type="urs">urs123</changePoll:caseId>
S: <changePoll:reason>URS Lock</changePoll:reason> S: <changePoll:reason>URS Lock</changePoll:reason>
S: </changePoll:changeData> S: </changePoll:changeData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Example poll <info> response with the <changePoll:changeData>
extension for a custom "sync" operation on the domain.example domain The following is an example poll <info> response with the
name, with the default "after" state. The "after" state is reflected <changePoll:changeData> extension for a custom "sync" operation on
in the <resData> block: the domain.example domain name, with the default "after" state. The
"after" state is reflected in the <resData> block:
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ id="201" count="1"> S: <msgQ id="201" count="1">
S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <qDate>2013-10-22T14:25:57.0Z</qDate>
S: <msg>Registry initiated Sync of Domain Expiration Date</msg> S: <msg>Registry initiated Sync of Domain Expiration Date</msg>
skipping to change at page 13, line 4 skipping to change at page 11, line 4
S: <changePoll:reason lang="en">Customer sync request S: <changePoll:reason lang="en">Customer sync request
S: </changePoll:reason> S: </changePoll:reason>
S: </changePoll:changeData> S: </changePoll:changeData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Example poll <info> response with the <changePoll:changeData> The following is an example poll <info> response with the
extension for a "delete" operation on the domain.example domain name <changePoll:changeData> extension for a "delete" operation on the
that is immediately purged, with the "before" state. The "before" domain.example domain name that is immediately purged, with the
state is reflected in the <resData> block: "before" state. The "before" state is reflected in the <resData>
block:
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ id="200" count="1"> S: <msgQ id="200" count="1">
S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <qDate>2013-10-22T14:25:57.0Z</qDate>
S: <msg>Registry initiated delete of S: <msg>Registry initiated delete of
skipping to change at page 14, line 4 skipping to change at page 12, line 4
S: <changePoll:reason>Court order S: <changePoll:reason>Court order
S: </changePoll:reason> S: </changePoll:reason>
S: </changePoll:changeData> S: </changePoll:changeData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Example poll <info> response with the <changePoll:changeData> The following is an example poll <info> response with the
extension for an "autoPurge" operation on the domain.example domain <changePoll:changeData> extension for an "autoPurge" operation on the
name that previously had the "pendingDelete" status, with the domain.example domain name that previously had the "pendingDelete"
"before" state. The "before" state is reflected in the <resData> status, with the "before" state. The "before" state is reflected in
block: the <resData> block:
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue S: <msg>Command completed successfully; ack to dequeue
S: </msg> S: </msg>
S: </result> S: </result>
S: <msgQ id="200" count="1"> S: <msgQ id="200" count="1">
S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <qDate>2013-10-22T14:25:57.0Z</qDate>
S: <msg>Registry purged domain with pendingDelete status. S: <msg>Registry purged domain with pendingDelete status.
S: </msg> S: </msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <domain:infData S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name> S: <domain:name>domain.example</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid> S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="pendingDelete"/>
S: <domain:clID>ClientX</domain:clID> S: <domain:clID>ClientX</domain:clID>
S: </domain:infData> S: </domain:infData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <changePoll:changeData S: <changePoll:changeData
S: xmlns:changePoll="urn:ietf:params:xml:ns:changePoll-1.0" S: xmlns:changePoll="urn:ietf:params:xml:ns:changePoll-1.0"
S: state="before"> S: state="before">
S: <changePoll:operation>autoPurge S: <changePoll:operation>autoPurge
S: </changePoll:operation> S: </changePoll:operation>
S: <changePoll:date>2013-10-22T14:25:57.0Z S: <changePoll:date>2013-10-22T14:25:57.0Z
skipping to change at page 15, line 4 skipping to change at page 13, line 6
S: <changePoll:reason>Past pendingDelete 5 day period S: <changePoll:reason>Past pendingDelete 5 day period
S: </changePoll:reason> S: </changePoll:reason>
S: </changePoll:changeData> S: </changePoll:changeData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Example poll <info> response with the <changePoll:changeData>
extension for an "update" operation on the ns1.domain.example host, The following is an example poll <info> response with the
with the default "after" state. The "after" state is reflected in <changePoll:changeData> extension for an "update" operation on the
the <resData> block: ns1.domain.example host, with the default "after" state. The "after"
state is reflected in the <resData> block:
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ id="201" count="1"> S: <msgQ id="201" count="1">
S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <qDate>2013-10-22T14:25:57.0Z</qDate>
S: <msg>Registry initiated update of host.</msg> S: <msg>Registry initiated update of host.</msg>
skipping to change at page 16, line 15 skipping to change at page 14, line 18
3.1.3. EPP <transfer> Command 3.1.3. EPP <transfer> Command
This extension does not add any elements to the EPP <transfer> query This extension does not add any elements to the EPP <transfer> query
command or <transfer> response described in the [RFC5730]. command or <transfer> response described in the [RFC5730].
3.2. EPP Transform Commands 3.2. EPP Transform Commands
EPP provides five commands to transform objects: <create> to create EPP provides five commands to transform objects: <create> to create
an instance of an object, <delete> to delete an instance of an an instance of an object, <delete> to delete an instance of an
object, <renew> to extend the validity period of an object, object, <renew> to extend the validity period of an object,
<transfer> to manage object sponsorship changes, and <update> to <transfer> to manage object-sponsorship changes, and <update> to
change information associated with an object. change information associated with an object.
3.2.1. EPP <create> Command 3.2.1. EPP <create> Command
This extension does not add any elements to the EPP <create> command This extension does not add any elements to the EPP <create> command
or <create> response described in the [RFC5730]. or <create> response described in [RFC5730].
3.2.2. EPP <delete> Command 3.2.2. EPP <delete> Command
This extension does not add any elements to the EPP <delete> command This extension does not add any elements to the EPP <delete> command
or <delete> response described in the [RFC5730]. or <delete> response described in [RFC5730].
3.2.3. EPP <renew> Command 3.2.3. EPP <renew> Command
This extension does not add any elements to the EPP <renew> command This extension does not add any elements to the EPP <renew> command
or <renew> response described in the [RFC5730]. or <renew> response described in [RFC5730].
3.2.4. EPP <transfer> Command 3.2.4. EPP <transfer> Command
This extension does not add any elements to the EPP <transfer> This extension does not add any elements to the EPP <transfer>
command or <transfer> response described in the [RFC5730]. command or <transfer> response described in [RFC5730].
3.2.5. EPP <update> Command 3.2.5. EPP <update> Command
This extension does not add any elements to the EPP <update> command This extension does not add any elements to the EPP <update> command
or <update> response described in the [RFC5730]. or <update> response described in [RFC5730].
4. Formal Syntax 4. Formal Syntax
One schema is presented here that is the EPP Change Poll Extension One schema is presented here: the EPP Change Poll Extension schema.
schema.
The formal syntax presented here is a complete schema representation The formal syntax presented here is a complete schema representation
of the object mapping suitable for automated validation of EPP XML of the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they instances. The BEGIN and END tags are not part of the schema; they
are used to note the beginning and ending of the schema for URI are used to note the beginning and ending of the schema for URI
registration purposes. registration purposes.
4.1. Change Poll Extension Schema 4.1. Change Poll Extension Schema
BEGIN BEGIN
skipping to change at page 18, line 23 skipping to change at page 16, line 33
<enumeration value="update"/> <enumeration value="update"/>
<enumeration value="restore"/> <enumeration value="restore"/>
<enumeration value="autoRenew"/> <enumeration value="autoRenew"/>
<enumeration value="autoDelete"/> <enumeration value="autoDelete"/>
<enumeration value="autoPurge"/> <enumeration value="autoPurge"/>
<enumeration value="custom"/> <enumeration value="custom"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
Enumerated of state of the object in the poll message. Enumerated state of the object in the poll message.
--> -->
<simpleType name="stateType"> <simpleType name="stateType">
<restriction base="token"> <restriction base="token">
<enumeration value="before"/> <enumeration value="before"/>
<enumeration value="after"/> <enumeration value="after"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
Transform operation type Transform operation type
skipping to change at page 19, line 42 skipping to change at page 18, line 11
--> -->
</schema> </schema>
END END
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace 5.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. The conforming to a registry mechanism described in [RFC3688]. The
following URI assignment is requested of IANA: following URI assignment has been made by IANA:
Registration request for the changePoll namespace: Registration for the changePoll namespace:
URI: urn:ietf:params:xml:ns:changePoll-1.0 URI: urn:ietf:params:xml:ns:changePoll-1.0
Registrant Contact: IESG Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the changePoll XML schema: Registration for the changePoll XML schema:
URI: urn:ietf:params:xml:ns:changePoll-1.0 URI: urn:ietf:params:xml:ns:changePoll-1.0
Registrant Contact: IESG Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry 5.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document has been registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the Extensions for the "Extensible Provisioning Protocol
details of the registration are as follows: (EPP)" registry described in [RFC7451]. The details of the
registration are as follows:
Name of Extension: "Change Poll Extension for the Extensible Name of Extension: Change Poll Extension for the Extensible
Provisioning Protocol (EPP)" Provisioning Protocol (EPP)
Document status: Standards Track Document Status: Standards Track
Reference: (insert reference to RFC version of this document) Reference: RFC 8590
Registrant Name and Email Address: IESG, <iesg@ietf.org> Registrant Name and Email Address: IESG <iesg@ietf.org>
TLDs: Any TLDs: Any
IPR Disclosure: None IPR Disclosure: None
Status: Active Status: Active
Notes: None Notes: None
6. Implementation Status 6. Security Considerations
Note to RFC Editor: Please remove this section and the reference to
RFC 7942 [RFC7942] before publication.
This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC 7942
[RFC7942]. The description of implementations in this section is
intended to assist the IETF in its decision processes in progressing
drafts to RFCs. Please note that the listing of any individual
implementation here does not imply endorsement by the IETF.
Furthermore, no effort has been spent to verify the information
presented here that was supplied by IETF contributors. This is not
intended as, and must not be construed to be, a catalog of available
implementations or their features. Readers are advised to note that
other implementations may exist.
According to RFC 7942 [RFC7942], "this will allow reviewers and
working groups to assign due consideration to documents that have the
benefit of running code, which may serve as evidence of valuable
experimentation and feedback that have made the implemented protocols
more mature. It is up to the individual working groups to use this
information as they see fit".
6.1. Verisign EPP SDK
Organization: Verisign Inc.
Name: Verisign EPP SDK
Description: The Verisign EPP SDK includes both a full client
implementation and a full server stub implementation of draft-ietf-
regext-change-poll.
Level of maturity: Production
Coverage: All aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License
Contact: jgould@verisign.com
URL: https://www.verisign.com/en_US/channel-resources/domain-
registry-products/epp-sdks
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS
Organization: Verisign Inc.
Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry
System (SRS)
Description: The Verisign Consolidated Top Level Domain (CTLD) Shared
Registry System (SRS) implements the server-side of draft-ietf-
regext-change-poll for a variety of Top Level Domains (TLD's).
Level of maturity: Production
Coverage: The "after" state poll message for an "update" transform
operation of a domain name due to server policy.
Licensing: Proprietary
Contact: jgould@verisign.com
6.3. Verisign .COM / .NET SRS
Organization: Verisign Inc.
Name: Verisign .COM / .NET Shared Registry System (SRS)
Description: The Verisign Shared Registry System (SRS) for .COM and
.NET implements the server-side of draft-ietf-regext-change-poll.
Level of maturity: Production
Coverage: The "after" state poll message for an "update" transform
operation of a domain name due to server policy.
Licensing: Proprietary
Contact: jgould@verisign.com
6.4. Neustar EPP SDK
Organisation: Neustar Inc.
Name: Neustar EPP SDK
Description: The Neustar EPP SDK includes a full client
implementation of draft-ietf-regext-change-poll.
Level of maturity: Production
Coverage: All client side aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License
Contact: quoc-anh.np@team.neustar
7. Security Considerations
The mapping extensions described in this document do not provide any The mapping extensions described in this document do not provide any
security services beyond those described by EPP [RFC5730] and security services beyond those described by EPP [RFC5730] and
protocol layers used by EPP. The security considerations described protocol layers used by EPP. The security considerations described
in these other specifications apply to this specification as well. in these other specifications apply to this specification as well.
8. Acknowledgements 7. References
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 Scott Hollenbeck, Michael Holloway, and Patrick
Mevzek.
9. References
9.1. Normative References 7.1. Normative References
[RFC0020] Cerf, V., "ASCII format for network interchange", STD 80, [RFC20] Cerf, V., "ASCII format for network interchange", STD 80,
RFC 20, DOI 10.17487/RFC0020, October 1969, RFC 20, DOI 10.17487/RFC0020, October 1969,
<https://www.rfc-editor.org/info/rfc20>. <https://www.rfc-editor.org/info/rfc20>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997,
editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004,
editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
the Extensible Provisioning Protocol (EPP)", RFC 3915, the Extensible Provisioning Protocol (EPP)", RFC 3915,
DOI 10.17487/RFC3915, September 2004, <https://www.rfc- DOI 10.17487/RFC3915, September 2004,
editor.org/info/rfc3915>. <https://www.rfc-editor.org/info/rfc3915>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009, <https://www.rfc- DOI 10.17487/RFC5731, August 2009,
editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
Code: The Implementation Status Section", BCP 205, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
RFC 7942, DOI 10.17487/RFC7942, July 2016, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
<https://www.rfc-editor.org/info/rfc7942>.
[W3C.REC-xmlschema-2-20041028] [W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Second Edition", World Wide Web Consortium Recommendation Second Edition", World Wide Web Consortium Recommendation
REC-xmlschema-2-20041028, October 2004, REC-xmlschema-2-20041028, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
9.2. Informative References 7.2. Informative References
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC Acknowledgments
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
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
1. Amended XML Namespace section of IANA Considerations, added EPP
Extension Registry section.
2. Moved Change History to the back section as an Appendix.
A.3. Change from 02 to 03
1. Fixed "before" state example to use the "before" state value
based on feedback from Patrick Mevzek.
A.4. Change from 03 to 04
1. Updated the authors for the draft.
A.5. Change from 04 to 05
1. Ping update.
A.6. Change from 05 to REGEXT 00
1. Changed to regext working group draft by changing draft-gould-
change-poll to draft-ietf-regext-change-poll.
A.7. Change from REGEXT 00 to REGEXT 01
1. Ping update.
A.8. Change from REGEXT 01 to REGEXT 02
1. Added the Implementation Status section.
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 <changePoll:who> element in the Who
section.
5. Revise the sentence that describes how the extension extends
the info response in the EPP <info> 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.
A.12. Change from REGEXT 05 to REGEXT 06
1. Added the "State" sub-section to the "Object Attributes" section
to describe the expected behavior for the "before" and "after"
states, based on feedback from Patrick Mevzek.
2. Added a colon suffix to each hangText entry to provide better
separation.
A.13. Change from REGEXT 06 to REGEXT 07
1. Updates based on feedback from Scott Hollenbeck, that include:
1. Changed MAY to may in the Abstract.
2. Revised the "IANA Considerations" section to include the
registration of the XML schema.
3. Revised the description of the <changePoll:caseId> "name"
attribute and the "changePoll:operation> "op" attribute as
containing 7-bit US-ASCII identifiers for the case type or
the operation type, respectively.
A.14. Change from REGEXT 07 to REGEXT 08
1. Updated obsoleted RFC 6982 to RFC 7942.
2. Moved RFC 7451 to an informational reference based on a check
done by the Idnits Tool.
3. Changed Kal Feher's contact e-mail address.
4. Changed Neustar's Implementation Status contact e-mail address.
A.15. Change from REGEXT 08 to REGEXT 09
1. Fixed Section 1.1 (Conventions) to contain the updated language
(e.g. "NOT RECOMMENDED", RFC 8174, BCP 14), based on feedback
from the Document Shepherd.
A.16. Change from REGEXT 09 to REGEXT 10
1. Updates based on the AD review by Adam Roach, that include:
1. Fix the "purge" and "autoPurge" examples to use the
normative "before" state instead of the default "after"
state.
2. Added the sentences "The extension only extends the EPP
<poll> response in [RFC5730] and does not extend the EPP
<poll> command. Please refer to [RFC5730] for information
and examples of the EPP <poll> command." in the
"Introduction" to clarify what is extended and reference
[RFC5730] for the EPP <poll> command.
3. Added missing hyphens to "client-sponsored" and "court-
directed".
4. Removed "changePoll-1.0" is used as an abbreviation for
"urn:ietf:params:xml:ns:changePoll-1.0" and replaced the
paragraph based on what was done in draft-ietf-regext-
allocation-token.
5. Changed normative "SHOULD" to non-normative "should" in "An
operation consists of any transform operation that impacts
objects that the client sponsers and should be notified of."
6. Added normative reference to [RFC0020] to define "7-bit US-
ASCII".
7. Added the sentence "The custom operations supported is up to
server policy." to the description of the "custom"
operation.
8. Broke up the "This extension adds operation detail..."
sentence into two seperate sentences to address the "does"
and the "is" seperately.
9. Removed the commas from "Any transform operation to an
object..." sentence.
10. Changed to use an IPv6 address from the documentation-only
prefix "2001:DB8::/32" in RFC 3849. The IPv6 address
2001:db8:0:0:1:0:0:1 was used.
A.17. Change from REGEXT 10 to REGEXT 11
1. Updates based on the review by Benjamin Kaduk, that include:
1. Change references of "The enumerated list ... include:" to
"The enumerated list ... is:".
2. In section 2.2, explicitly state what the message is inserted
into, with the change of "... MUST be inserted prior to ..."
to "... MUST be inserted into the message queue prior to
...".
A.18. Change from REGEXT 11 to REGEXT 12 The authors wish to acknowledge the original concept for this
document and the efforts in the initial versions of this document by
Trung Tran and Sharon Wodjenski.
1. Added clarification for the <changePoll:who> element based on the Special suggestions that have been incorporated into this document
feedback from Benjamin Kaduk. were provided by Scott Hollenbeck, Michael Holloway, and Patrick
Mevzek.
Authors' Addresses Authors' Addresses
James Gould James Gould
VeriSign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US United States of America
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisign.com URI: http://www.verisign.com
Kal Feher Kal Feher
Neustar Neustar
lvl 8/10 Queens Road lvl 8/10 Queens Road
Melbourne, VIC 3004 Melbourne, VIC 3004
AU Australia
Email: ietf@feherfamily.org Email: ietf@feherfamily.org
URI: http://www.neustar.biz URI: http://www.neustar.biz
 End of changes. 84 change blocks. 
454 lines changed or deleted 190 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/