< draft-sattler-epp-registry-maintenance-07.txt   draft-sattler-epp-registry-maintenance-08.txt >
Internet Engineering Task Force T. Sattler Internet Engineering Task Force T. Sattler, Editor
Internet-Draft Internet-Draft
Intended status: Standard Track R. Carney Intended status: Standard Track R. Carney
Expires: February 8, 2019 J. Kolker Expires: June 5, 2019 J. Kolker
GoDaddy Inc. GoDaddy Inc.
August 9, 2018 December 6, 2018
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-sattler-epp-registry-maintenance-07 draft-sattler-epp-registry-maintenance-08
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 domain name registry's maintenance notifications.
Name Registries will conduct a maintenance, and for retrieving these
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.
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 February 8, 2019. This Internet-Draft will expire on June 5, 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 27 skipping to change at page 2, line 27
3.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 9 3.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 9
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11
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 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . 18
8.2. Informative References . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 19
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 18 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 19
A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20
A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 20
A.8. Change from 07 to EPPMAINT 00 . . . . . . . . . . . . . . 19 A.8. Change from 07 to EPPMAINT 00 . . . . . . . . . . . . . . 20
A.9. Change from EPPMAINT 00 to EPPMAINT 01 . . . . . . . . . 19 A.9. Change from EPPMAINT 00 to EPPMAINT 01 . . . . . . . . . 20
A.10. Change from EPPMAINT 01 to EPPMAINT 02 . . . . . . . . . 19 A.10. Change from EPPMAINT 01 to EPPMAINT 02 . . . . . . . . . 20
A.11. Change from EPPMAINT 02 to EPPMAINT 03 . . . . . . . . . 19 A.11. Change from EPPMAINT 02 to EPPMAINT 03 . . . . . . . . . 20
A.12. Change from EPPMAINT 03 to EPPMAINT 04 . . . . . . . . . 19 A.12. Change from EPPMAINT 03 to EPPMAINT 04 . . . . . . . . . 20
A.13. Change from EPPMAINT 04 to EPPMAINT 05 . . . . . . . . . 19 A.13. Change from EPPMAINT 04 to EPPMAINT 05 . . . . . . . . . 20
A.14. Change from EPPMAINT 05 to EPPMAINT 06 . . . . . . . . . 19 A.14. Change from EPPMAINT 05 to EPPMAINT 06 . . . . . . . . . 20
A.15. Change from EPPMAINT 06 to EPPMAINT 07 . . . . . . . . . 20 A.15. Change from EPPMAINT 06 to EPPMAINT 07 . . . . . . . . . 21
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 20 A.16. Change from EPPMAINT 07 to EPPMAINT 08 . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
This document describes an Extensible Provision Protocol (EPP) Domain name registries usually conduct maintenances and inform domain
[RFC5730] mapping for the Registry Maintenance Notifications used name registrars via different ways. Given the expansion of the DNS
when Domain Name Registries will conduct a maintenance, and for namespace, it is now desirable to provide a method for EPP servers to
retrieving these information. notify EPP clients as well as a method for EPP clients to query EPP
servers for upcoming maintenances.
This document describes an extension mapping for version 1.0 of the
Extensible Provision Protocol [RFC5730]. This mapping provides a
mechanism by which EPP servers may notify and EPP clients to query
for upcoming maintenances.
1.1. Terminology and Definitions 1.1. Terminology and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119] when document are to be interpreted as described in [RFC2119] when
specified in their uppercase forms. specified in their uppercase forms.
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
skipping to change at page 16, line 32 skipping to change at page 16, line 32
</simpleType> </simpleType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
5. IANA Considerations 5. IANA Considerations
TBD 5.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688].
Registration request for the maintenance namespace:
URI: urn:ietf:params:xml:ns:maintenance-1.0
Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the maintenance schema:
URI: urn:ietf:params:xml:schema:maintenance-1.0
Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry
The following registration of the EPP Extension Registry, described
in [RFC7451], is requested:
Name of Extension: "Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP)"
Document status: Standards Track
Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: IESG, <iesg@ietf.org>
TLDs: Any
IPR Disclosure: None
Status: Active
Notes: None
6. Security Considerations 6. Security Considerations
The mapping extensions described in this document do not provide any The mapping extensions described in this document do not provide any
security services beyond those described by EPP [RFC5730] and security services beyond those described by EPP [RFC5730] and
protocol layers used by EPP. The security considerations described in protocol layers used by EPP. The security considerations described in
these other specifications apply to this specification as well. these other specifications apply to this specification as well.
7. Implementation Status 7. Implementation Status
skipping to change at page 17, line 40 skipping to change at page 18, line 22
Add implementation details once available. Add implementation details once available.
8. References 8. References
8.1. Normative References 8.1. 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, March 1997, Requirement Levels", BCP 14, RFC 2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009, STD 69, RFC 5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
8.2. Informative References 8.2. Informative References
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002, Internet: Timestamps", RFC 3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
skipping to change at page 18, line 14 skipping to change at page 18, line 49
[RFC4122] Leach, P., Mealling, M. and Salz, R., "A Universally [RFC4122] Leach, P., Mealling, M. and Salz, R., "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, July Unique IDentifier (UUID) URN Namespace", RFC 4122, July
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>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[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
skipping to change at page 20, line 9 skipping to change at page 21, line 9
set. set.
A.14. Change from EPPMAINT 05 to EPPMAINT 06 A.14. Change from EPPMAINT 05 to EPPMAINT 06
Added Roger Carney and Jody Kolker as Co-Authors to this draft. Added Roger Carney and Jody Kolker as Co-Authors to this draft.
A.15. Change from EPPMAINT 06 to EPPMAINT 07 A.15. Change from EPPMAINT 06 to EPPMAINT 07
Changed Acknowledgements. Changed Acknowledgements.
A.16. Change from EPPMAINT 07 to EPPMAINT 08
Added IANA consideration section 5.1. and 5.2. Added editor flag
to author. Changed abstract and introduction. Minor formatting
changes.
Appendix B. Acknowledgements Appendix B. Acknowledgements
The authors wish to thank the following persons for their feedback The authors wish to thank the following persons for their feedback
and suggestions (sorted alphabetically by company): and suggestions (sorted alphabetically by company):
* Patrick Mevzek o Patrick Mevzek
* Neal McPherson, 1&1 Internet o Neal McPherson, 1&1 IONOS
* Anthony Eden, DNSimple o Anthony Eden, DNSimple
* Christopher Martens, Donuts o Christopher Martens, Donuts
* Raymond Zylstra, Neustar o Raymond Zylstra, Neustar
* Andreas Huber, united-domains o Andreas Huber, united-domains
* Craig Marchant, VentraIP o Craig Marchant, VentraIP
* James Gould, Verisign o James Gould, Verisign
Authors' Addresses 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 Roger Carney
GoDaddy Inc. GoDaddy Inc.
 End of changes. 15 change blocks. 
42 lines changed or deleted 104 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/