draft-ietf-regext-epp-registry-maintenance-11.txt   draft-ietf-regext-epp-registry-maintenance-12.txt 
Internet Engineering Task Force (IETF) T. Sattler Internet Engineering Task Force (IETF) T. Sattler
Internet-Draft Internet-Draft
Intended status: Standards Track R. Carney Intended status: Standards Track R. Carney
Expires: June 30, 2021 J. Kolker Expires: June 30, 2021 J. Kolker
GoDaddy Inc. GoDaddy Inc.
February 19, 2021 March 27, 2021
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-registry-maintenance-11 draft-ietf-regext-epp-registry-maintenance-12
Abstract Abstract
This document describes an Extensible Provision Protocol (EPP) This document describes an Extensible Provision Protocol (EPP)
mapping for registry's maintenance notifications. mapping for registry's maintenance notifications.
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
skipping to change at page 2, line 54 skipping to change at page 2, line 54
A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20
A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20
A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20
A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20
A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20
A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 21 A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 21
A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 21 A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 21
A.11. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 21 A.11. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 21
A.12. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 21 A.12. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 21
A.13. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 21 A.13. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 21
A.14. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 21
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
Registries usually conduct maintenances and inform registrars in Registries usually conduct maintenances and inform registrars in
different ways. Given the DNS namespace expansion, it is now different ways. Given the DNS namespace expansion, it is now
desirable to provide methods for EPP servers to notify EPP clients desirable to provide methods for EPP servers to notify EPP clients
and EPP clients to query EPP servers for upcoming maintenances. and EPP clients to query EPP servers for upcoming maintenances.
skipping to change at page 3, line 30 skipping to change at page 3, line 30
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
moreover, examples provided in this document MUST be interpreted in moreover, examples provided in this document MUST be interpreted in
the character case presented to develop a conforming implementation. the character case presented to develop a conforming implementation.
"maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:
maintenance-0.2". The XML namespace prefix "maint" is used, but maintenance-0.3". The XML namespace prefix "maint" is used, but
implementations MUST NOT depend on it and instead employ a proper implementations MUST NOT depend on it and instead employ a proper
namespace-aware XML parser and serializer to interpret and output namespace-aware XML parser and serializer to interpret and output
the XML documents. the XML documents.
In examples, "C:" represents lines sent by a protocol client and In examples, "C:" represents lines sent by a protocol client and
"S:" represents lines returned by a protocol server. Indentation and "S:" represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element white space in examples are provided only to illustrate element
relationships and are not a REQUIRED feature of this protocol. relationships and are not a REQUIRED feature of this protocol.
2. Migrating to Newer Versions of This Extension 2. Migrating to Newer Versions of This Extension
skipping to change at page 12, line 44 skipping to change at page 12, line 44
of the object mapping suitable for automated validation of EPP XML of the object mapping suitable for automated validation of EPP XML
instances. The <CODE BEGINS> and <CODE ENDS> tags are not part of instances. The <CODE BEGINS> and <CODE ENDS> tags are not part of
the schema; they are used to note the beginning and end of the the schema; they are used to note the beginning and end of the
schema for URI registration purposes. schema for URI registration purposes.
5.1. Registry Maintenance EPP Mapping Schema 5.1. Registry Maintenance EPP Mapping Schema
<CODE BEGINS> <CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:epp: <schema targetNamespace="urn:ietf:params:xml:ns:epp:
maintenance-0.2" maintenance-0.3"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3" xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
skipping to change at page 19, line 28 skipping to change at page 19, line 28
URL: https://registry.godaddy URL: https://registry.godaddy
9. References 9. References
9.1. Normative References 9.1. Normative References
[I.D.draft-ietf-regext-unhandled-namespaces] [I.D.draft-ietf-regext-unhandled-namespaces]
Gould, J. and Casanova, M., "Extensible Provisioning Gould, J. and Casanova, M., "Extensible Provisioning
Protocol (EPP) Unhandled Namespaces", Protocol (EPP) Unhandled Namespaces",
<https://datatracker.ietf.org/doc/draft-ietf-regext- <https://datatracker.ietf.org/doc/draft-ietf-regext-
unhandled-namespaces/> (work in progress), December 2020. unhandled-namespaces/> (work in progress), February 2021.
[W3C-HTML5] Hickson, I., Berjon, R., Faulkner, S., Leithead, T., [W3C-HTML5] Hickson, I., Berjon, R., Faulkner, S., Leithead, T.,
Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5",
W3C Recommendation REC-html5-20141028, October 2014, W3C Recommendation REC-html5-20141028, October 2014,
<http://www.w3.org/TR/2014/REC-html5-20141028/>. <http://www.w3.org/TR/2014/REC-html5-20141028/>.
Latest version available at <http://www.w3.org/TR/html5/>. Latest version available at <http://www.w3.org/TR/html5/>.
[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,
skipping to change at page 22, line 5 skipping to change at page 21, line 35
A.12. Change from 09 to 10 A.12. Change from 09 to 10
Editoral changes. Renamed "msg" to "name". Added "courtesy" and "end" Editoral changes. Renamed "msg" to "name". Added "courtesy" and "end"
to pollType. to pollType.
A.13. Change from 10 to 11 A.13. Change from 10 to 11
Editoral changes. Added mime type to description. Editoral changes. Added mime type to description.
A.14. Change from 11 to 12
Editoral changes. Changed XML namespace from 0.2 to 0.3.
Acknowledgments Acknowledgments
The authors wish to thank the following persons for their feedback The authors wish to thank the following persons for their feedback
and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond
Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig
Marchant, and Andreas Huber. Marchant, and Andreas Huber.
Authors' Addresses Authors' Addresses
Tobias Sattler Tobias Sattler
 End of changes. 7 change blocks. 
5 lines changed or deleted 10 lines changed or added

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