draft-ietf-regext-epp-registry-maintenance-03.txt   draft-ietf-regext-epp-registry-maintenance-04.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 29, 2020 J. Kolker Expires: April 22, 2021 J. Kolker
GoDaddy Inc. GoDaddy Inc.
June 30, 2020 October 23, 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-03 draft-ietf-regext-epp-registry-maintenance-04
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 29, 2020. This Internet-Draft will expire on April 22, 2021.
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 26 skipping to change at page 2, line 26
3.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 6 3.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . . . . 17
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 18
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 . . . . . . . . . . . . . . . . . 19
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 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19
A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20
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 4, line 12 skipping to change at page 4, line 12
date-time form using upper case "T" and "Z" characters defined in ISO date-time form using upper case "T" and "Z" characters defined in ISO
8601 [RFC3339] MUST be used to represent date-time values. 8601 [RFC3339] MUST be used to represent date-time values.
2.3. Maintenance Elements 2.3. Maintenance Elements
The <maint:maint> element describes a single registry maintenance The <maint:maint> element describes a single registry maintenance
event during a specific period. This element will be used at EPP event during a specific period. This element will be used at EPP
<poll> messages and to extend the EPP <info> command. <poll> messages and to extend the EPP <info> command.
For creating a new maintenance the attribute <maint:status> MUST be For creating a new maintenance the attribute <maint:status> MUST be
'active', the attribute <maint:crDate> MUST be set and the attribute "active", the attribute <maint:crDate> MUST be set and the attribute
<maint:upDate> SHALL NOT be present. <maint:upDate> SHALL NOT be present.
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 server unique id and SHALL NOT be MUST be present and a server unique id and SHALL NOT be
changed if maintenance is 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 has an element of <maint:name>,
<maint:host> and <maint:impact>. <maint:host> and <maint:impact>.
<maint:name> <maint:name>
MUST be present and indicates the name of the affected system, MUST be present and indicates the name of the affected system,
such as 'EPP', 'WHOIS', 'DNS', 'Portal', etc. such as "EPP", "WHOIS", "DNS", "Portal", etc.
<maint:host> <maint:host>
MUST be present and indicates the affected maintained system MUST be present and indicates the affected maintained system
contains <maint:hostName> or <maint:hostAddr>. contains the hostname and OPTIONAL an IP address.
<maint:hostName>
Hostname SHALL be Punycode according [RFC5891]. Hostname SHALL be Punycode according [RFC5891].
<maint:hostAddr ip="v4">
IPv4 addresses SHALL be dotted-decimal notation. IPv4 addresses SHALL be dotted-decimal notation.
An example of this textual representation is "192.0.2.0". An example of this textual representation is "192.0.2.0".
<maint:hostAddr ip="v6">
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 MUST
either be 'blackout' or 'partial'. either be "full" 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;
the attribute type is REQUIRED and SHOULD either be 'production', the attribute type is REQUIRED and SHOULD either be "production",
'ote', 'staging', 'dev' or 'custom'. And alternatively the "ote", "staging", "dev" or "custom". And alternatively the
attribute name could be used to define a server specific affected attribute name could be used to define a server specific affected
system for example: system for example. In that case name MUST be set:
<maint:environment type="custom" name="marketing"/> <maint:environment type="custom" name="marketing"/>
<maint:start> <maint:start>
SHOULD be present and indicates the start of the maintenance SHOULD 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>
SHOULD be present and indicates the end of the maintenance SHOULD 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>.
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
<maint:reason> <maint:reason>
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 characters. resource.
<maint:tlds> <maint:tlds>
SHOULD be present and contains <maint:tld> elements. SHOULD 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>
SHOULD be present and contains <maint:connection> and SHOULD be present and contains <maint:connection> and
skipping to change at page 6, line 12 skipping to change at page 6, line 12
something that is connection-related, such as a reconnect. The something that is connection-related, such as a reconnect. The
value 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".
<maint:crDate> <maint:crDate>
MUST be present and contains the creation date of the maintenance MUST be present and contains the creation date of the maintenance
according ISO 8601 [RFC3339]. according ISO 8601 [RFC3339].
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
<maint:upDate> <maint:upDate>
MAY be present and contains the updated date of the maintenance MAY be present and contains the updated date of the maintenance
according to ISO 8601 [RFC3339], and if set MUST be equal to or according to ISO 8601 [RFC3339], and if set MUST be equal to or
greater than <main:crDate>. greater than <main:crDate>.
skipping to change at page 6, line 54 skipping to change at page 6, line 54
3.1.2. EPP <transfer> Command 3.1.2. EPP <transfer> Command
Transfer semantics do not apply to maintenance objects, so there is Transfer semantics do not apply to maintenance objects, so there is
no mapping defined for the EPP <transfer> command. no mapping defined for the EPP <transfer> command.
3.1.3. EPP <info> Command 3.1.3. EPP <info> Command
EPP provides the <info> command that is used to retrieve registry EPP provides the <info> command that is used to retrieve registry
maintenance information. In addition to the standard EPP command maintenance information. In addition to the standard EPP command
elements, the <info> command MUST contain a <maint:info> elements, the <info> command MUST contain a <maint:info>
element that identifies the maintenance namespace. The <maint:info> element that identifies the maintenance namespace.
element MUST contain a child element. It is either <maint:id> to
retrieve a specific maintenance notification or <maint:list> to
query all maintenance notifications.
Example <info> command with <maint:id> to get one specific The <maint:info> element MUST contain a child element. It is either
<maint:id> to retrieve a specific maintenance notification or
<maint:list> to query all maintenance notifications.
If a <maint:info> is send with a <maint:id> that does not exist on
the server side, then the result code 2303 MUST be responded.
Please see the defintion of <maint> elements in Section 2.3.
Example <info> command with explicit <maint:id> to get one specific
maintenance: maintenance:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <info> C: <info>
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0"> C: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0">
C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>
C: </maint:info> C: </maint:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Example <info> response for one specific maintenance notification: Example <info> response for one specific maintenance notification,
which was requested with a explicit <maint:id>. In this case, it
provides the all "required" elements and additional elements
<maint:start>, <maint:end>, <maint:detail>, <maint:description>,
<maint:tlds>, <maint:intervention>.
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0"> S: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0">
S: <maint:maint> S: <maint:maint>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6
S: </maint:id> S: </maint:id>
S: <maint:systems> S: <maint:systems>
S: <maint:system> S: <maint:system>
S: <maint:name>EPP</maint:name> S: <maint:name>EPP</maint:name>
S: <maint:host> S: <maint:host>epp.registry.example
S: <maint:hostName>epp.registry.example
S: </maint:hostName>
S: </maint:host> S: </maint:host>
S: <maint:impact>blackout</maint:impact> S: <maint:impact>blackout</maint:impact>
S: </maint:system> S: </maint:system>
S: </maint:systems> S: </maint:systems>
S: <maint:environment type="production"/> S: <maint:environment type="production"/>
S: <maint:start>2017-09-30T06:00:00Z</maint:start> S: <maint:start>2017-09-30T06:00:00Z</maint:start>
S: <maint:end>2017-09-30T14:25:57Z</maint:end> S: <maint:end>2017-09-30T14:25:57Z</maint:end>
S: <maint:reason>planned</maint:reason> S: <maint:reason>planned</maint:reason>
S: <maint:detail> S: <maint:detail>
S: https://www.registry.example/notice?123 S: https://www.registry.example/notice?123
S: </maint:detail> S: </maint:detail>
S: <maint:description>free text</maint:description> S: <maint:description lang="en">free text
S: </maint:description>
S: <maint:tlds> S: <maint:tlds>
S: <maint:tld>example</maint:tld> S: <maint:tld>example</maint:tld>
S: <maint:tld>test</maint:tld> S: <maint:tld>test</maint:tld>
S: </maint:tlds> S: </maint:tlds>
S: <maint:intervention> S: <maint:intervention>
S: <maint:connection>false</maint:connection> S: <maint:connection>false</maint:connection>
S: <maint:implementation>false</maint:implementation> S: <maint:implementation>false</maint:implementation>
S: </maint:intervention> S: </maint:intervention>
S: <maint:status>active</maint:status> S: <maint:status>active</maint:status>
S: <maint:crDate>2017-03-08T22:10:00Z</maint:crDate> S: <maint:crDate>2017-03-08T22:10:00Z</maint:crDate>
skipping to change at page 8, line 42 skipping to change at page 8, line 47
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0"> C: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0">
C: <maint:list/> C: <maint:list/>
C: </maint:info> C: </maint:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Example <info> response querying all maintenances subject to server Example <info> response querying all maintenances subject to server
policy: policy. In this case, all the "required" elements will be returned
and additional <maint:upDate>.
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0"> S: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0">
skipping to change at page 9, line 37 skipping to change at page 9, line 39
S: </response> S: </response>
S:</epp> S:</epp>
3.1.4. EPP <poll> Command 3.1.4. EPP <poll> Command
The EPP <poll> command and response is defined in Section 2.9.2.3 of The EPP <poll> command and response is defined in Section 2.9.2.3 of
[RFC5730]. The Registry Maintenance Notification is included in the [RFC5730]. The Registry Maintenance Notification is included in the
EPP <poll> response of [RFC5730]. EPP <poll> response of [RFC5730].
For the Registry Maintenance Notification, there are three types of For the Registry Maintenance Notification, there are three types of
poll messages. The poll messages apply whenever the domain name poll messages. The poll message applies whenever the domain name
registry creates, updates, or deletes maintenance. In the case of registry creates, updates, or deletes maintenance. In the case of
a Registry Maintenance specific message, a <maint:infData> element a Registry Maintenance specific message, a <maint:infData> element
will be included within the <resData> element of the standard <poll> will be included within the <resData> element of the standard <poll>
response. response.
The <maint:infData> element will include a reference to the The <maint:infData> element will include a reference to the
Registry Maintenance namespace. EPP data contained within the Registry Maintenance namespace. EPP data contained within the
<maint:infData> element is formatted according to the <maint:infData> element is formatted according to the
maintenance-poll schema. maintenance-poll schema.
Please see the defintion of <maint> elements in Section 2.3.
Example <poll> command: Example <poll> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <poll op="req"/> C: <poll op="req"/>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Example <poll> response with the Registry Maintenance poll message: Example <poll> response with the Registry Maintenance poll message:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ count="1" id="12345"> S: <msgQ count="1" id="12345">
S: <qDate>2017-02-08T22:10:00Z</qDate> S: <qDate>2017-02-08T22:10:00Z</qDate>
S: <msg>Registry Maintenance Notification</msg> S: <msg lang="en">Registry Maintenance Notification</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0"> S: xmlns:maint="urn:ietf:params:xml:ns:maintenance-1.0">
S: <maint:maint> S: <maint:maint>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>
S: <maint:systems> S: <maint:systems>
S: <maint:system> S: <maint:system>
S: <maint:name>EPP</maint:name> S: <maint:name>EPP</maint:name>
S: <maint:host> S: <maint:host>epp.registry.example
S: <maint:hostName>epp.registry.example
S: </maint:hostName>
S: </maint:host> S: </maint:host>
S: <maint:impact>blackout</maint:impact> S: <maint:impact>blackout</maint:impact>
S: </maint:system> S: </maint:system>
S: </maint:systems> S: </maint:systems>
S: <maint:environment type="production"/> S: <maint:environment type="production"/>
S: <maint:start>2017-10-30T06:00:00Z</maint:start> S: <maint:start>2017-10-30T06:00:00Z</maint:start>
S: <maint:end>2017-10-30T14:25:57Z</maint:end> S: <maint:end>2017-10-30T14:25:57Z</maint:end>
S: <maint:reason>planned</maint:reason> S: <maint:reason>planned</maint:reason>
S: <maint:detail> S: <maint:detail>
S: https://www.registry.example/notice?123 S: https://www.registry.example/notice?123
skipping to change at page 12, line 51 skipping to change at page 12, line 51
Child elements found in EPP commands. Child elements found in EPP commands.
--> -->
<element name="info" type="maint:infoType"/> <element name="info" type="maint:infoType"/>
<!-- <!--
Child elements of the <info> command. Child elements of the <info> command.
--> -->
<complexType name="infoType"> <complexType name="infoType">
<sequence> <sequence>
<choice> <choice>
<element name="list"> <element name="list"/>
<complexType/>
</element>
<element name="id" type="maint:idType"/> <element name="id" type="maint:idType"/>
</choice> </choice>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Human-readable text may be expresses the maintenance Human-readable text may describe the maintenance
--> -->
<complexType name="idType"> <complexType name="idType">
<simpleContent> <simpleContent>
<extension base="normalizedString"> <extension base="token">
<attribute name="msg" type="token"/> <attribute name="msg" type="token"/>
<attribute name="lang" type="language" default="en"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!--
Info Response element Info Response element
--> -->
<element name="infData" type="maint:infDataType"/> <element name="infData" type="maint:infDataType"/>
<!-- <!--
skipping to change at page 14, line 12 skipping to change at page 14, line 12
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Attributes associated with the maintenance info response Attributes associated with the maintenance info response
--> -->
<complexType name="maintDataType"> <complexType name="maintDataType">
<sequence> <sequence>
<element name="id" type="maint:idType"/> <element name="id" type="maint:idType"/>
<element name="systems" type="maint:systemsType"/> <element name="systems" type="maint:systemsType"/>
<element name="environment" type="maint:envType"/> <element name="environment" type="maint:envType"/>
<element name="start" type="dateTime"/> <element name="start" type="dateTime" minOccurs="0"/>
<element name="end" type="dateTime"/> <element name="end" type="dateTime" minOccurs="0"/>
<element name="reason" type="maint:reasonEnum"/> <element name="reason" type="maint:reasonEnum"/>
<element name="detail" type="token" minOccurs="0"/> <element name="detail" type="anyURI" minOccurs="0"/>
<element name="description" type="maint:descriptionType" <element name="description" type="maint:descriptionType"
minOccurs="0"/> minOccurs="0"/>
<element name="tlds" type="maint:tldsType"/> <element name="tlds" type="maint:tldsType" minOccurs="0"/>
<element name="intervention" type="maint:interventionType"/> <element name="intervention" type="maint:interventionType"
minOccurs="0"/>
<element name="status" type="maint:statusEnum"/> <element name="status" type="maint:statusEnum"/>
<element name="crDate" type="dateTime"/> <element name="crDate" type="dateTime"/>
<element name="upDate" type="dateTime" minOccurs="0"/> <element name="upDate" type="dateTime" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
systems element systems element
--> -->
<complexType name="systemsType"> <complexType name="systemsType">
skipping to change at page 14, line 42 skipping to change at page 14, line 43
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Enumerated list of impacts Enumerated list of impacts
--> -->
<simpleType name="impactEnum"> <simpleType name="impactEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="partial"/> <enumeration value="partial"/>
<enumeration value="blackout"/> <enumeration value="full"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
description element description element
--> -->
<simpleType name="descriptionType"> <complexType name="descriptionType">
<restriction base="string"> <simpleContent>
<maxLength value="1024"/> <extension base="string">
</restriction> <attribute name="lang" type="language" default="en"/>
</simpleType> </extension>
</simpleContent>
</complexType>
<!-- <!--
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="maint:hostAttrType"/> <element name="host" type="maint:addrType"/>
<element name="impact" type="maint:impactEnum"/> <element name="impact" type="maint:impactEnum"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
host element host element
--> -->
<complexType name="hostAttrType"> <complexType name="addrType">
<sequence> <simpleContent>
<element name="hostName" type="eppcom:labelType"/> <extension base="maint:addrStringType">
<element name="hostAddr" type="host:addrType" minOccurs="0"/> <attribute name="ip" type="maint:ipType" default="v4"/>
</sequence> </extension>
</simpleContent>
</complexType> </complexType>
<simpleType name="addrStringType">
<restriction base="token">
<minLength value="3"/>
<maxLength value="45"/>
</restriction>
</simpleType>
<simpleType name="ipType">
<restriction base="token">
<enumeration value="v4"/>
<enumeration value="v6"/>
</restriction>
</simpleType>
<!-- <!--
Enumerated list of environments Enumerated list of environments
--> -->
<simpleType name="envEnum"> <simpleType name="envEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="production"/> <enumeration value="production"/>
<enumeration value="ote"/> <enumeration value="ote"/>
<enumeration value="staging"/> <enumeration value="staging"/>
<enumeration value="dev"/> <enumeration value="dev"/>
<enumeration value="custom"/> <enumeration value="custom"/>
skipping to change at page 20, line 5 skipping to change at page 20, line 5
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 A.5. Change from 02 to 03
Changed maint:connection from MUST to SHOULD. Changed maint:connection from MUST to SHOULD.
A.6. Change from 03 to 04
A lot of clarifications and editoral changes.
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. 46 change blocks. 
70 lines changed or deleted 93 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/