draft-ietf-regext-change-poll-10.txt   draft-ietf-regext-change-poll-11.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 25, 2019 Neustar Expires: June 13, 2019 Neustar
October 22, 2018 December 10, 2018
Change Poll Extension for the Extensible Provisioning Protocol (EPP) Change Poll Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-change-poll-10 draft-ietf-regext-change-poll-11
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 April 25, 2019. This Internet-Draft will expire on June 13, 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 3, line 18 skipping to change at page 3, line 18
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 . . . . . . . . . . . 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
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 4, line 29 skipping to change at page 4, line 29
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 defined in [RFC0020], that is used to define a sub- character set defined in [RFC0020], 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 include: 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". that include "request", "approve", "cancel", or "reject".
"update": Update operation as defined in [RFC5730]. "update": Update operation as defined in [RFC5730].
skipping to change at page 5, line 14 skipping to change at page 5, line 14
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
"before" state poll message MUST be inserted prior to the "after" "before" state poll message MUST be inserted into the message queue
state poll message. prior to the "after" 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
skipping to change at page 6, line 52 skipping to change at page 6, line 52
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 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 [RFC0020], that is used to define the name of the "custom" case
type. The enumerated list of case types include: 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
skipping to change at page 27, line 14 skipping to change at page 27, line 14
8. Broke up the "This extension adds operation detail..." 8. Broke up the "This extension adds operation detail..."
sentence into two seperate sentences to address the "does" sentence into two seperate sentences to address the "does"
and the "is" seperately. and the "is" seperately.
9. Removed the commas from "Any transform operation to an 9. Removed the commas from "Any transform operation to an
object..." sentence. object..." sentence.
10. Changed to use an IPv6 address from the documentation-only 10. Changed to use an IPv6 address from the documentation-only
prefix "2001:DB8::/32" in RFC 3849. The IPv6 address prefix "2001:DB8::/32" in RFC 3849. The IPv6 address
2001:db8:0:0:1:0:0:1 was used. 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
...".
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.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 AU
Email: ietf@feherfamily.org Email: ietf@feherfamily.org
URI: http://www.neustar.biz URI: http://www.neustar.biz
 End of changes. 9 change blocks. 
9 lines changed or deleted 21 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/