draft-ietf-regext-change-poll-09.txt   draft-ietf-regext-change-poll-10.txt 
Network Working Group J. Gould Network Working Group J. Gould
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Standards Track K. Feher Intended status: Standards Track K. Feher
Expires: April 7, 2019 Neustar Expires: April 25, 2019 Neustar
October 4, 2018 October 22, 2018
Change Poll Extension for the Extensible Provisioning Protocol (EPP) Change Poll Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-change-poll-09 draft-ietf-regext-change-poll-10
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 actions,
Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid
Suspension (URS) actions, court directed actions, and bulk updates Suspension (URS) actions, court-directed actions, and bulk updates
based on customer requests. Since the client is not directly based on customer requests. Since the client is not directly
involved or knowledgable of these operations, the extension is used involved or knowledgable of these operations, the extension is used
along with an EPP object mapping to provide the resulting state of along with an EPP object mapping to provide the resulting state of
the post-operation object, and optionally a pre-operation object, the post-operation object, and optionally a pre-operation object,
with the operation meta-data of what, when, who, and why. with the operation meta-data 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 Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 7, 2019. This Internet-Draft will expire on April 25, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 (http://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
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. State . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Who . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Who . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 5 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 5
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . 16
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 16 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 16
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 16 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 16
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 16 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 16
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 16 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 16
skipping to change at page 2, line 49 skipping to change at page 2, line 49
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 20 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 20
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 20
6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 21 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 21
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 21 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 21
6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 22 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 22
6.4. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 22 6.4. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.1. Normative References . . . . . . . . . . . . . . . . . . 23 9.1. Normative References . . . . . . . . . . . . . . . . . . 23
9.2. Informative References . . . . . . . . . . . . . . . . . 23 9.2. Informative References . . . . . . . . . . . . . . . . . 24
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 24 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 24
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 24 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 24
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 24 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 24
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 24 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 24
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 24 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 24
A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 24 A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 24
A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 24 A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 24
A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 24 A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 25
A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 25 A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 25
A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25 A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25
A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 25 A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 25
A.12. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 25 A.12. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 25
A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25 A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25
A.14. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 26 A.14. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 26
A.15. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 26 A.15. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 A.16. Change from REGEXT 09 to REGEXT 10 . . . . . . . . . . . 26
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. operation poll message. 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.
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 BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 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 "S:"
represents lines returned by a protocol server. Indentation and 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.
"changePoll-1.0" is used as an abbreviation for The XML namespace prefix "changePoll" is used for the namespace
"urn:ietf:params:xml:ns:changePoll-1.0". The XML namespace prefix "urn:ietf:params:xml:ns:changePoll-1.0", but implementations MUST NOT
"changePoll" is used, but implementations MUST NOT depend on it and depend on it and instead employ a proper namespace-aware XML parser
instead employ a proper namespace-aware XML parser and serializer to and serializer to interpret and output the XML documents.
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 sponsers 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, that is used to define a sub-operation or the name of character set defined in [RFC0020], that is used to define a sub-
a "custom" operation. The enumerated list of <changePoll:operation> operation or the name of a "custom" operation. The enumerated list
values include: of <changePoll:operation> values include:
"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". that 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". that 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 had the "pendingDelete" status.
"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. custom operation name. The custom operations supported is up to
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 with a default value of
"after". The server MAY support both the "before" state and the "after". The server MAY support both the "before" state and the
"after" state of the operation, by using one poll message for the "after" state of the operation, by using one poll message for the
"before" state and one poll message for the "after" state. The "before" state and one poll message for the "after" state. The
skipping to change at page 6, line 23 skipping to change at page 6, line 28
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 the [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 the [RFC5730].
This extension adds operation detail of EPP object mapping operations This extension adds operation detail of EPP object mapping operations
Section 2.1 to an EPP poll response, as described in [RFC5730], that Section 2.1 to an EPP poll response, as described in [RFC5730]. The
is an extension of the EPP object mapping info response. Any extension is an extension of the EPP object mapping info response.
transform operation to an object defined in an EPP object mapping, by Any transform operation to an object defined in an EPP object mapping
a client other than the sponsoring client, MAY result in extending by a client other than the sponsoring client MAY result in extending
the <info> response of the object for inserting an EPP poll message the <info> response of the object for inserting an EPP poll message
with the operation detail. The sponsoring client will then receive with the operation detail. The sponsoring client will then receive
the state of the object with operation detail like what, who, when, the state of the object with operation detail like what, who, when,
and why the object was changed. The <changePoll:changeData> element and why the object was changed. The <changePoll:changeData> element
contains the operation detail along with an indication of whether the contains the operation detail along with an indication of whether the
object reflects the state before or after the operation as defined in object reflects the state before or after the operation as defined in
Section 2.2. The <changePoll:changeData> element includes the Section 2.2. The <changePoll:changeData> element includes the
operation detail with the following child elements: 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 identifer 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, that is used to represented in the 7-bit US-ASCII character set defined in
define the name of the "custom" case type. The enumerated list [RFC0020], that is used to define the name of the "custom" case
of case types include: type. The enumerated list of case types include:
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).
skipping to change at page 13, line 6 skipping to change at page 13, line 6
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> Example poll <info> response with the <changePoll:changeData>
extension for a "delete" operation on the domain.example domain name extension for a "delete" operation on the domain.example domain name
that is immediately purged, with the default "after" state. The that is immediately purged, with the "before" state. The "before"
"after" state is reflected in 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>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
S: domain resulting in immediate purge.</msg> S: domain resulting in immediate purge.</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: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: <changePoll:operation op="purge"> S: state="before">
S: delete</changePoll:operation> S: <changePoll:operation op="purge">delete
S: <changePoll:date>2013-10-22T14:25:57.0Z</changePoll:date> S: </changePoll:operation>
S: <changePoll:svTRID>12345-XYZ</changePoll:svTRID> S: <changePoll:date>2013-10-22T14:25:57.0Z
S: <changePoll:who>ClientZ</changePoll:who> S: </changePoll:date>
S: <changePoll:reason>Court order</changePoll:reason> S: <changePoll:svTRID>12345-XYZ
S: </changePoll:changeData> S: </changePoll:svTRID>
S: </extension> S: <changePoll:who>ClientZ
S: <trID> S: </changePoll:who>
S: <clTRID>ABC-12345</clTRID> S: <changePoll:reason>Court order
S: <svTRID>54321-XYZ</svTRID> S: </changePoll:reason>
S: </trID> S: </changePoll:changeData>
S: </response> S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp> S:</epp>
Example poll <info> response with the <changePoll:changeData> Example poll <info> response with the <changePoll:changeData>
extension for an "autoPurge" operation on the domain.example domain extension for an "autoPurge" operation on the domain.example domain
name that previously had the "pendingDelete" status, with the default name that previously had the "pendingDelete" status, with the
"after" state. The "after" state is reflected in the <resData> "before" state. The "before" state is reflected in the <resData>
block: 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
S: </result> S: </msg>
S: <msgQ id="200" count="1"> S: </result>
S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <msgQ id="200" count="1">
S: <msg>Registry purged domain with pendingDelete status.</msg> S: <qDate>2013-10-22T14:25:57.0Z</qDate>
S: </msgQ> S: <msg>Registry purged domain with pendingDelete status.
S: <resData> S: </msg>
S: <domain:infData S: </msgQ>
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <resData>
S: <domain:name>domain.example</domain:name> S: <domain:infData
S: <domain:roid>EXAMPLE1-REP</domain:roid> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:clID>ClientX</domain:clID> S: <domain:name>domain.example</domain:name>
S: </domain:infData> S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: </resData> S: <domain:clID>ClientX</domain:clID>
S: <extension> S: </domain:infData>
S: <changePoll:changeData S: </resData>
S: xmlns:changePoll="urn:ietf:params:xml:ns:changePoll-1.0"> S: <extension>
S: <changePoll:operation> S: <changePoll:changeData
S: autoPurge</changePoll:operation> S: xmlns:changePoll="urn:ietf:params:xml:ns:changePoll-1.0"
S: <changePoll:date>2013-10-22T14:25:57.0Z</changePoll:date> S: state="before">
S: <changePoll:svTRID>12345-XYZ</changePoll:svTRID> S: <changePoll:operation>autoPurge
S: <changePoll:who>Batch</changePoll:who> S: </changePoll:operation>
S: <changePoll:reason> S: <changePoll:date>2013-10-22T14:25:57.0Z
S: Past pendingDelete 5 day period S: </changePoll:date>
S: </changePoll:reason> S: <changePoll:svTRID>12345-XYZ
S: </changePoll:changeData> S: </changePoll:svTRID>
S: </extension> S: <changePoll:who>Batch
S: <trID> S: </changePoll:who>
S: <clTRID>ABC-12345</clTRID> S: <changePoll:reason>Past pendingDelete 5 day period
S: <svTRID>54321-XYZ</svTRID> S: </changePoll:reason>
S: </trID> S: </changePoll:changeData>
S: </response> S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp> S:</epp>
Example poll <info> response with the <changePoll:changeData> Example poll <info> response with the <changePoll:changeData>
extension for an "update" operation on the ns1.domain.example host, extension for an "update" operation on the ns1.domain.example host,
with the default "after" state. The "after" state is reflected in with the default "after" state. The "after" state is reflected in
the <resData> 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">
skipping to change at page 15, line 28 skipping to change at page 15, line 28
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <host:infData S: <host:infData
S: xmlns:host="urn:ietf:params:xml:ns:host-1.0"> S: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
S: <host:name>ns1.domain.example</host:name> S: <host:name>ns1.domain.example</host:name>
S: <host:roid>NS1_EXAMPLE1-REP</host:roid> S: <host:roid>NS1_EXAMPLE1-REP</host:roid>
S: <host:status s="linked"/> S: <host:status s="linked"/>
S: <host:status s="serverUpdateProhibited"/> S: <host:status s="serverUpdateProhibited"/>
S: <host:status s="serverDeleteProhibited"/> S: <host:status s="serverDeleteProhibited"/>
S: <host:addr ip="v4">192.0.2.2</host:addr> S: <host:addr ip="v4">192.0.2.2</host:addr>
S: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr> S: <host:addr ip="v6">2001:db8:0:0:1:0:0:1</host:addr>
S: <host:clID>ClientX</host:clID> S: <host:clID>ClientX</host:clID>
S: <host:crID>ClientY</host:crID> S: <host:crID>ClientY</host:crID>
S: <host:crDate>2012-04-03T22:00:00.0Z</host:crDate> S: <host:crDate>2012-04-03T22:00:00.0Z</host:crDate>
S: <host:upID>ClientY</host:upID> S: <host:upID>ClientY</host:upID>
S: <host:upDate>2013-10-22T14:25:57.0Z</host:upDate> S: <host:upDate>2013-10-22T14:25:57.0Z</host:upDate>
S: </host:infData> S: </host: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">
skipping to change at page 23, line 13 skipping to change at page 23, line 13
and Sharon Wodjenski. and Sharon Wodjenski.
Special suggestions that have been incorporated into this document Special suggestions that have been incorporated into this document
were provided by Scott Hollenbeck, Michael Holloway, and Patrick were provided by Scott Hollenbeck, Michael Holloway, and Patrick
Mevzek. Mevzek.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC0020] Cerf, V., "ASCII format for network interchange", STD 80,
RFC 20, DOI 10.17487/RFC0020, October 1969,
<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, <https://www.rfc-
editor.org/info/rfc2119>. 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, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
skipping to change at page 26, line 19 skipping to change at page 26, line 24
done by the Idnits Tool. done by the Idnits Tool.
3. Changed Kal Feher's contact e-mail address. 3. Changed Kal Feher's contact e-mail address.
4. Changed Neustar's Implementation Status contact e-mail address. 4. Changed Neustar's Implementation Status contact e-mail address.
A.15. Change from REGEXT 08 to REGEXT 09 A.15. Change from REGEXT 08 to REGEXT 09
1. Fixed Section 1.1 (Conventions) to contain the updated language 1. Fixed Section 1.1 (Conventions) to contain the updated language
(e.g. "NOT RECOMMENDED", RFC 8174, BCP 14), based on feedback (e.g. "NOT RECOMMENDED", RFC 8174, BCP 14), based on feedback
from the Document Shepherd. 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.
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 US
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisigninc.com URI: http://www.verisigninc.com
 End of changes. 26 change blocks. 
101 lines changed or deleted 155 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/