draft-ietf-regext-change-poll-06.txt   draft-ietf-regext-change-poll-07.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: July 9, 2018 Neustar Expires: August 2, 2018 Neustar
January 5, 2018 January 29, 2018
Change Poll Extension for the Extensible Provisioning Protocol (EPP) Change Poll Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-change-poll-06 draft-ietf-regext-change-poll-07
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
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 July 9, 2018. This Internet-Draft will expire on August 2, 2018.
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 43 skipping to change at page 2, line 43
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
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1. Change Poll Extension Schema . . . . . . . . . . . . . . 17 4.1. Change Poll Extension Schema . . . . . . . . . . . . . . 17
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 19 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 19
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 . . . . . . . . . . . . . . . . 21 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. Normative References . . . . . . . . . . . . . . . . . . . . 23 9. Normative References . . . . . . . . . . . . . . . . . . . . 23
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 23 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 23 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 . . . . . . . . . . . 24
A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 24 A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 24
A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 24 A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25
A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 24 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
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
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
skipping to change at page 4, line 16 skipping to change at page 4, line 16
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 used to define a sub-operation or the name of a "op" attribute is an identifier, represented in the 7-bit US-ASCII
"custom" operation. The enumerated list of <changePoll:operation> character set, that is used to define a sub-operation or the name of
a "custom" operation. The enumerated list of <changePoll:operation>
values include: 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".
skipping to change at page 6, line 37 skipping to change at page 6, line 37
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 with an enumerated list of case types including: case. The OPTIONAL "name" attribute is an identifier,
represented in the 7-bit US-ASCII character set, that is used to
define the name of the "custom" case 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
skipping to change at page 19, line 44 skipping to change at page 19, line 44
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 is requested of IANA:
URI: urn:ietf:params:xml:ns:changePoll-1.0 Registration request for the changePoll namespace:
Registrant Contact: See the "Author's Address" section of this URI: urn:ietf:params:xml:ns:changePoll-1.0
document. Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification.
XML: See the "Formal Syntax" section of this document. Registration request for the changePoll XML schema:
URI: urn:ietf:params:xml:ns:changePoll-1.0
Registrant Contact: IESG
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 should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: 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)"
skipping to change at page 22, line 47 skipping to change at page 23, line 6
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 8. Acknowledgements
The authors wish to acknowledge the original concept for this draft 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 the efforts in the initial versions of this draft by Trung Tran
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 Michael Holloway and Patrick Mevzek. were provided by Scott Hollenbeck, Michael Holloway, and Patrick
Mevzek.
9. Normative References 9. Normative References
[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-
skipping to change at page 25, line 26 skipping to change at page 25, line 37
section. section.
A.12. Change from REGEXT 05 to REGEXT 06 A.12. Change from REGEXT 05 to REGEXT 06
1. Added the "State" sub-section to the "Object Attributes" section 1. Added the "State" sub-section to the "Object Attributes" section
to describe the expected behavior for the "before" and "after" to describe the expected behavior for the "before" and "after"
states, based on feedback from Patrick Mevzek. states, based on feedback from Patrick Mevzek.
2. Added a colon suffix to each hangText entry to provide better 2. Added a colon suffix to each hangText entry to provide better
separation. 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.
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. 15 change blocks. 
19 lines changed or deleted 42 lines changed or added

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