draft-ietf-regext-epp-registry-maintenance-02.txt   draft-ietf-regext-epp-registry-maintenance-03.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: December 16, 2020 J. Kolker Expires: December 29, 2020 J. Kolker
GoDaddy Inc. GoDaddy Inc.
June 17, 2020 June 30, 2020
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-registry-maintenance-02 draft-ietf-regext-epp-registry-maintenance-03
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
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 December 16, 2020. This Internet-Draft will expire on December 29, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 41 skipping to change at page 2, line 41
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . 18 8.1. Normative References . . . . . . . . . . . . . . . . . . 18
8.2. Informative References . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19
A.1. Change from draft-sattler-epp-poll-maintenance-response to A.1. Change from draft-sattler-epp-poll-maintenance-response to
draft-sattler-epp-registry-maintenance . . . . . . . . . 19 draft-sattler-epp-registry-maintenance . . . . . . . . . 19
A.2. Change from draft-sattler-epp-registry-maintenance to A.2. Change from draft-sattler-epp-registry-maintenance to
draft-ietf-regext-epp-registry-maintenance . . . . . . . 19 draft-ietf-regext-epp-registry-maintenance . . . . . . . 19
A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19
A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19
A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
Registries usually conduct maintenances and inform registrars in Registries usually conduct maintenances and inform registrars in
different ways. Given the expansion of the DNS namespace, it is now different ways. Given the expansion of the DNS namespace, it is now
desirable to provide a method for EPP servers to notify EPP clients desirable to provide a method for EPP servers to notify EPP clients
as well as a method for EPP clients to query EPP servers for upcoming as well as a method for EPP clients to query EPP servers for upcoming
maintenances. maintenances.
skipping to change at page 5, line 53 skipping to change at page 5, line 53
<maint:tld> <maint:tld>
MUST be present and contains the affected top-level domain. MUST be present and contains the affected top-level domain.
Punycode encoded according to [RFC5891]. Punycode encoded according to [RFC5891].
<maint:intervention> <maint:intervention>
SHOULD be present and contains <maint:connection> and SHOULD be present and contains <maint:connection> and
<maint:implementation>. <maint:implementation>.
<maint:connection> <maint:connection>
MUST be present and indicates if a client needs to do something SHOULD be present and indicates if a client needs to do
that is connection-related, such as a reconnect. The value something that is connection-related, such as a reconnect. The
SHALL be boolean. value SHALL be boolean.
<maint:implementation> <maint:implementation>
MUST be present and indicates if a client needs to do something MUST be present and indicates if a client needs to do something
that is implementation-related, such as a code change. The that is implementation-related, such as a code change. The
value SHALL be boolean. value SHALL be boolean.
<maint:status> <maint:status>
MUST be present and indicates the status of the maintenance. MUST be present and indicates the status of the maintenance.
The value SHALL be either 'active' or 'inactive'. The value SHALL be either 'active' or 'inactive'.
skipping to change at page 20, line 5 skipping to change at page 19, line 31
Added acknowledgment. Added acknowledgment.
A.4. Change from 01 to 02 A.4. Change from 01 to 02
Update language from Domain Name Registry to Registry. Clarified Update language from Domain Name Registry to Registry. Clarified
XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host
to contain hostName and hostAddr. Changed maint:tlds from MUST to to contain hostName and hostAddr. Changed maint:tlds from MUST to
SHOULD. Fixed maint:status in Schema. Changed UUID to a server SHOULD. Fixed maint:status in Schema. Changed UUID to a server
unique id. unique id.
A.5. Change from 02 to 03
Changed maint:connection from MUST to SHOULD.
Acknowledgments Acknowledgments
The authors wish to thank the following individuals for their The authors wish to thank the following individuals for their
feedback and suggestions (sorted alphabetically by company): feedback and suggestions (sorted alphabetically by company):
o Patrick Mevzek o Patrick Mevzek
o Neal McPherson, 1&1 IONOS o Neal McPherson, 1&1 IONOS
o Anthony Eden, DNSimple o Anthony Eden, DNSimple
o Christopher Martens, Donuts o Christopher Martens, Donuts
o Quoc-Anh Pham, Neustar o Quoc-Anh Pham, Neustar
 End of changes. 7 change blocks. 
7 lines changed or deleted 12 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/