draft-ietf-regext-epp-registry-maintenance-00.txt   draft-ietf-regext-epp-registry-maintenance-01.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: August 14, 2020 J. Kolker Expires: November 7, 2020 J. Kolker
GoDaddy Inc. GoDaddy Inc.
February 15, 2020 May 8, 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-00 draft-ietf-regext-epp-registry-maintenance-01
Abstract Abstract
This document describes an Extensible Provision Protocol (EPP) This document describes an Extensible Provision Protocol (EPP)
mapping for domain name registry's maintenance notifications. mapping for domain name 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 August 14, 2020. This Internet-Draft will expire on November 7, 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 39 skipping to change at page 2, line 39
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
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
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
Domain name registries usually conduct maintenances and inform domain Domain name registries usually conduct maintenances and inform domain
name registrars in different ways. Given the expansion of the DNS name registrars in different ways. Given the expansion of the DNS
namespace, it is now desirable to provide a method for EPP servers to namespace, it is now desirable to provide a method for EPP servers to
notify EPP clients as well as a method for EPP clients to query EPP notify EPP clients as well as a method for EPP clients to query EPP
servers for upcoming maintenances. servers for upcoming maintenances.
skipping to change at page 4, line 25 skipping to change at page 4, line 25
For updating a maintenance the attribute <maint:status> MUST be For updating a maintenance the attribute <maint:status> MUST be
'active', the attributes <maint:crDate> and <maint:upDate> MUST be 'active', the attributes <maint:crDate> and <maint:upDate> MUST be
set. set.
For deleting a maintenance the attribute <maint:status> MUST be For deleting a maintenance the attribute <maint:status> MUST be
'inactive', and the attributes <maint:crDate> and <maint:upDate> MUST 'inactive', and the attributes <maint:crDate> and <maint:upDate> MUST
be set. be set.
<maint:id> <maint:id>
MUST be present and a UUID according [RFC4122] and SHALL NOT be MUST be present and a UUID according [RFC4122] and SHALL NOT be
changed if maintenance got updated or deleted. A human-readable changed if maintenance is updated or deleted. A human-readable
description of the maintenance is identified via an OPTIONAL description of the maintenance is identified via an OPTIONAL
"msg" attribute. "msg" attribute.
<maint:systems> <maint:systems>
MUST be present and contains one or more <maint:system> elements. MUST be present and contains one or more <maint:system> elements.
The server SHOULD NOT list systems which are not affected by the The server SHOULD NOT list systems which are not affected by the
maintenance. maintenance.
<maint:system> <maint:system>
MUST be present at least once and is an element of <maint:name>, MUST be present at least once and is an element of <maint:name>,
skipping to change at page 5, line 11 skipping to change at page 5, line 11
IPv6 addresses SHALL be according [RFC5952]. IPv6 addresses SHALL be according [RFC5952].
An example of this textual representation is An example of this textual representation is
"2001:db8::1:0:0:1". "2001:db8::1:0:0:1".
<maint:impact> <maint:impact>
MUST be present and contains the impact level; values SHOULD MUST be present and contains the impact level; values SHOULD
either be 'blackout' or 'partial'. either be 'blackout' or 'partial'.
<maint:environment> <maint:environment>
MUST be present and indicates the type of the affected system; MUST be present and indicates the type of the affected system;
values SHOULD either be 'production', 'ote', 'staging' or 'dev'. the attribute type is REQUIRED and SHOULD either be 'production',
'ote', 'staging', 'dev' or 'custom'. And alternatively the
attribute name could be used to define a server specific affected
system for example:
<maint:environment type="custom" name="marketing"/>
<maint:start> <maint:start>
MUST be present and indicates the start of the maintenance MUST be present and indicates the start of the maintenance
according ISO 8601 [RFC3339]. according ISO 8601 [RFC3339].
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
<maint:end> <maint:end>
MUST be present and indicates the end of the maintenance MUST be present and indicates the end of the maintenance
according to ISO 8601 [RFC3339], and MUST be equal to or greater according to ISO 8601 [RFC3339], and MUST be equal to or greater
than <maint:start>. than <maint:start>.
skipping to change at page 5, line 35 skipping to change at page 5, line 39
MUST be present and contains the reason behind the maintenance; MUST be present and contains the reason behind the maintenance;
values SHOULD either be 'planned' or 'emergency'. values SHOULD either be 'planned' or 'emergency'.
<maint:detail> <maint:detail>
MAY be present and contains URI to detailed maintenance MAY be present and contains URI to detailed maintenance
description. description.
<maint:description> <maint:description>
MAY be present and provides a freeform description of the MAY be present and provides a freeform description of the
maintenance without having to create and traverse an external maintenance without having to create and traverse an external
resource. The maximum length MUST NOT exceed 1024 bit. resource. The maximum length MUST NOT exceed 1024 characters.
<maint:tlds> <maint:tlds>
MUST be present and contains <maint:tld> elements. MUST be present and contains <maint:tld> elements.
<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>
MUST be present and contains <maint:connection> and MUST be present and contains <maint:connection> and
skipping to change at page 14, line 49 skipping to change at page 14, line 49
<simpleType name="impactEnum"> <simpleType name="impactEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="partial"/> <enumeration value="partial"/>
<enumeration value="blackout"/> <enumeration value="blackout"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
description element description element
--> -->
<complexType name="descriptionType"> <simpleType name="descriptionType">
<restriction base="string"> <restriction base="string">
<maxLength value="1024"/> <maxLength value="1024"/>
</restriction> </restriction>
</complexType> </simpleType>
<!-- <!--
system element system element
--> -->
<complexType name="systemType"> <complexType name="systemType">
<sequence> <sequence>
<element name="name" type="token"/> <element name="name" type="token"/>
<element name="host" type="token"/> <element name="host" type="token"/>
<element name="impact" type="maint:impactEnum"/> <element name="impact" type="maint:impactEnum"/>
</sequence> </sequence>
skipping to change at page 19, line 12 skipping to change at page 19, line 12
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 draft-sattler-epp-poll-maintenance-response to A.1. Change from draft-sattler-epp-poll-maintenance-response to
draft-sattler-epp-registry-maintenance draft-sattler-epp-registry-maintenance
Updated to be EPP based instead of JSON document. Updated to be EPP based instead of JSON document.
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 draft-ietf-regext-epp-registry-maintenance
Adopted by the REGEXT working group. Adopted by the REGEXT working group.
A.3. Change from 00 to 01
Clarified maint:description and maint:environment. Changed
maint:description from complexType to simpleType. Fixed typo.
Added acknowledgment.
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 Raymond Zylstra, Neustar o Raymond Zylstra, Neustar
o Andreas Huber, united-domains o Andreas Huber, united-domains
o Craig Marchant, VentraIP o Craig Marchant, VentraIP
o 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
 End of changes. 13 change blocks. 
10 lines changed or deleted 22 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/