draft-ietf-regext-change-poll-11.txt   draft-ietf-regext-change-poll-12.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: June 13, 2019 Neustar Expires: July 8, 2019 Neustar
December 10, 2018 January 4, 2019
Change Poll Extension for the Extensible Provisioning Protocol (EPP) Change Poll Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-change-poll-11 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 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
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 June 13, 2019. This Internet-Draft will expire on July 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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 (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
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 . . . . . . . . . . . . . . . . . . . . . 5 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . 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
skipping to change at page 3, line 19 skipping to change at page 3, line 19
A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 25 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
A.16. Change from REGEXT 09 to REGEXT 10 . . . . . . . . . . . 26 A.16. Change from REGEXT 09 to REGEXT 10 . . . . . . . . . . . 26
A.17. Change from REGEXT 10 to REGEXT 11 . . . . . . . . . . . 27 A.17. Change from REGEXT 10 to REGEXT 11 . . . . . . . . . . . 27
A.18. Change from REGEXT 11 to REGEXT 12 . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 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
skipping to change at page 5, line 31 skipping to change at page 5, line 35
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. The scheme used for the possible set of audit purposes. It is a freeform value that is strictly meant for
<changePoll:who> element values is up to server policy. The server audit purposes and not meant to drive client-side logic. The scheme
MAY identify the <changePoll:who> element value based on: used for the possible set of <changePoll:who> element values is up to
server policy. The server MAY identify the <changePoll:who> element
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
skipping to change at page 27, line 25 skipping to change at page 27, line 25
1. Updates based on the review by Benjamin Kaduk, that include: 1. Updates based on the review by Benjamin Kaduk, that include:
1. Change references of "The enumerated list ... include:" to 1. Change references of "The enumerated list ... include:" to
"The enumerated list ... is:". "The enumerated list ... is:".
2. In section 2.2, explicitly state what the message is inserted 2. In section 2.2, explicitly state what the message is inserted
into, with the change of "... MUST be inserted prior to ..." into, with the change of "... MUST be inserted prior to ..."
to "... MUST be inserted into the message queue prior to to "... MUST be inserted into the message queue prior to
...". ...".
A.18. Change from REGEXT 11 to REGEXT 12
1. Added clarification for the <changePoll:who> element based on the
feedback from Benjamin Kaduk.
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.verisign.com URI: http://www.verisign.com
 End of changes. 8 change blocks. 
9 lines changed or deleted 17 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/