draft-sattler-epp-registry-maintenance-05.txt   draft-sattler-epp-registry-maintenance-06.txt 
Internet Engineering Task Force T. Sattler Internet Engineering Task Force T. Sattler
Internet-Draft March 29, 2018 Internet-Draft
Intended status: Standard Track Intended status: Standard Track R. Carney
Expires: September 28, 2018 Expires: January 18, 2019 J. Kolker
GoDaddy Inc.
July 19, 2018
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-sattler-epp-registry-maintenance-05 draft-sattler-epp-registry-maintenance-06
Abstract Abstract
This document describes an Extensible Provision Protocol (EPP) This document describes an Extensible Provision Protocol (EPP)
mapping for the Registry Maintenance Notifications used when Domain mapping for the Registry Maintenance Notifications used when Domain
Name Registries will conduct a maintenance, and for retrieving these Name Registries will conduct a maintenance, and for retrieving these
information. information.
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 31 skipping to change at page 1, line 33
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 September 28, 2018. This Internet-Draft will expire on January 18, 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
(https://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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 11 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 11
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 11 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 11
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12 4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 18 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 18
A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19
A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19
A.8. Change from 07 to EPPMAINT 00 . . . . . . . . . . . . . . 19 A.8. Change from 07 to EPPMAINT 00 . . . . . . . . . . . . . . 19
A.9. Change from EPPMAINT 00 to EPPMAINT 01 . . . . . . . . . 19 A.9. Change from EPPMAINT 00 to EPPMAINT 01 . . . . . . . . . 19
A.10. Change from EPPMAINT 01 to EPPMAINT 02 . . . . . . . . . 19 A.10. Change from EPPMAINT 01 to EPPMAINT 02 . . . . . . . . . 19
A.11. Change from EPPMAINT 02 to EPPMAINT 03 . . . . . . . . . 19 A.11. Change from EPPMAINT 02 to EPPMAINT 03 . . . . . . . . . 19
A.12. Change from EPPMAINT 03 to EPPMAINT 04 . . . . . . . . . 19 A.12. Change from EPPMAINT 03 to EPPMAINT 04 . . . . . . . . . 19
A.13. Change from EPPMAINT 04 to EPPMAINT 05 . . . . . . . . . 19 A.13. Change from EPPMAINT 04 to EPPMAINT 05 . . . . . . . . . 19
A.14. Change from EPPMAINT 05 to EPPMAINT 06 . . . . . . . . . 19
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 20 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This document describes an Extensible Provision Protocol (EPP) This document describes an Extensible Provision Protocol (EPP)
[RFC5730] mapping for the Registry Maintenance Notifications used [RFC5730] mapping for the Registry Maintenance Notifications used
when Domain Name Registries will conduct a maintenance, and for when Domain Name Registries will conduct a maintenance, and for
retrieving these information. retrieving these information.
1.1. Terminology and Definitions 1.1. Terminology and Definitions
skipping to change at page 18, line 17 skipping to change at page 18, line 17
2015, 2015,
<https://www.rfc-editor.org/info/rfc4122>. <https://www.rfc-editor.org/info/rfc4122>.
[RFC5952] Kawamura, S. and Kawashima, M., "A Recommendation for IPv6 [RFC5952] Kawamura, S. and Kawashima, M., "A Recommendation for IPv6
Address Text Representation", RFC 5952, August 2010, Address Text Representation", RFC 5952, August 2010,
<https://www.rfc-editor.org/info/rfc5952>. <https://www.rfc-editor.org/info/rfc5952>.
[RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of
Running Code: The Implementation Status Section", RFC Running Code: The Implementation Status Section", RFC
7942, July 2016, 7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942> <https://www.rfc-editor.org/info/rfc7942>.
Appendix A. Change History Appendix A. Change History
A.1. Change from 00 to 01 A.1. Change from 00 to 01
Removed JSON Schema. Clarified unique id with UUID. Added Common Data Removed JSON Schema. Clarified unique id with UUID. Added Common Data
Structures for better explanation. Fixed EPP poll response example. Structures for better explanation. Fixed EPP poll response example.
Added und fixed References. Added und fixed References.
A.2. Change from 01 to 02 A.2. Change from 01 to 02
skipping to change at page 20, line 5 skipping to change at page 19, line 54
Fixed minor typos and added one acknowledgement. Fixed minor typos and added one acknowledgement.
A.13. Change from EPPMAINT 04 to EPPMAINT 05 A.13. Change from EPPMAINT 04 to EPPMAINT 05
Added missing whitespace. Fixed dates in examples. Added Added missing whitespace. Fixed dates in examples. Added
clarification that <maint:end> must be equal to or greater than clarification that <maint:end> must be equal to or greater than
<maint:start>, same applies for <maint:upDate> and <maint:crDate> if <maint:start>, same applies for <maint:upDate> and <maint:crDate> if
set. set.
Appendix B. Acknowledgements A.14. Change from EPPMAINT 05 to EPPMAINT 06
The author wishes to thank the following persons for their feedback Added Roger Carney and Jody Kolker as Co-Authors to this draft.
Appendix B. Acknowledgements
The authors wish to thank the following persons for their feedback
and suggestions (sorted alphabetically by company): and suggestions (sorted alphabetically by company):
* Neal McPherson of 1&1 Internet * Neal McPherson, 1&1 Internet
* Anthony Eden of DNSimple * Anthony Eden, DNSimple
* Christopher Martens of Donuts * Christopher Martens, Donuts
* Jody Kolker and Roger Carney of GoDaddy * Raymond Zylstra, Neustar
* Raymond Zylstra of Neustar * Patrick Mevzek, Uniregistry
* Patrick Mevzek of Uniregistry * Andreas Huber, united-domains
* Andreas Huber of united-domains * Craig Marchant, VentraIP
* Craig Marchant of VentraIP * James Gould, Verisign
* James Gould of Verisign
Author's Address Authors' Addresses
Tobias Sattler Tobias Sattler
Email: tobias.sattler@me.com Email: tobias.sattler@me.com
URI: https://tobiassattler.com URI: https://tobiassattler.com
Roger Carney
GoDaddy Inc.
14455 N. Hayden Rd. #219
Scottsdale, AZ 85260
US
Email: rcarney@godaddy.com
URI: http://www.godaddy.com
Jody Kolker
GoDaddy Inc.
14455 N. Hayden Rd. #219
Scottsdale, AZ 85260
US
Email: jkolker@godaddy.com
URI: http://www.godaddy.com
 End of changes. 12 change blocks. 
21 lines changed or deleted 27 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/