draft-ietf-regext-epp-registry-maintenance-04.txt   draft-ietf-regext-epp-registry-maintenance-05.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: April 22, 2021 J. Kolker Expires: June 30, 2021 J. Kolker
GoDaddy Inc. GoDaddy Inc.
October 23, 2020 December 1, 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-04 draft-ietf-regext-epp-registry-maintenance-05
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 April 22, 2021. This Internet-Draft will expire on June 30, 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 17 skipping to change at page 2, line 17
1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Internationalized Domain Names . . . . . . . . . . . . . 3 2.1. Internationalized Domain Names . . . . . . . . . . . . . 3
2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3 2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3
2.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4 2.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6
3.1.2. EPP <transfer> Command . . . . . . . . . . . . . . . 6 3.1.2. EPP <transfer> Command . . . . . . . . . . . . . . . 6
3.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 6 3.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 6
3.1.3.1. Query Maintenance Item . . . . . . . . . . . . . . 7
3.1.3.2. Query Maintenance List . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . . . . 17 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
skipping to change at page 2, line 43 skipping to change at page 2, line 45
8.2. Informative References . . . . . . . . . . . . . . . . . 19 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 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20
A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 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 3, line 29 skipping to change at page 3, line 29
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
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: "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:
maintenance-1.0". The XML namespace prefix "maint" is used, but maintenance-0.1". 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. Object Attributes 2. Object Attributes
2.1. Internationalized Domain Names 2.1. Internationalized Domain Names
Names of affected hosts MUST be provided in Punycode according to Names of affected hosts MUST be provided as A-label according to
[RFC5891]. [RFC5891].
2.2. Dates and Times 2.2. Dates and Times
All dates and times attribute values MUST be expressed in Universal All dates and times attribute values MUST be expressed in Universal
Coordinated Time (UTC) using the Gregorian calendar. The extended Coordinated Time (UTC) using the Gregorian calendar. The extended
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:item> 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:crDate> MUST be
"active", the attribute <maint:crDate> MUST be set and the attribute 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
"active", the attributes <maint:crDate> and <maint:upDate> MUST be
set.
For deleting a maintenance the attribute <maint:status> MUST be For updating a maintenance the attributes <maint:crDate> and
"inactive", and the attributes <maint:crDate> and <maint:upDate> MUST <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
skipping to change at page 4, line 45 skipping to change at page 4, line 39
MUST be present at least once and has 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 the hostname and OPTIONAL an IP address. contains the hostname and OPTIONAL an IP address.
Hostname SHALL be Punycode according [RFC5891]. Hostname SHALL be A-label according [RFC5891].
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".
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 MUST MUST be present and contains the impact level; values MUST
either be "full" or "partial". either be "full" or "partial".
skipping to change at page 5, line 46 skipping to change at page 5, line 46
<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. 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]. A-label format 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>
SHOULD be present and indicates if a client needs to do MUST be present and indicates if a client needs to do
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>
MUST be present and indicates the status of the maintenance.
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>.
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
skipping to change at page 7, line 9 skipping to change at page 7, line 5
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. element that identifies the maintenance namespace.
The <maint:info> element MUST contain a child element. It is either The <maint:info> element MUST contain a child element. It is either
<maint:id> to retrieve a specific maintenance notification or <maint:id> to retrieve a specific maintenance notification or
<maint:list> to query all maintenance notifications. <maint:list> to query all maintenance notifications.
3.1.3.1. Query one maintenance item
If a <maint:info> is send with a <maint:id> that does not exist on 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. the server side, then the result code 2303 MUST be responded.
Please see the defintion of <maint> elements in Section 2.3. Please see the defintion of <maint> elements in Section 2.3.
Example <info> command with explicit <maint:id> to get one specific 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:epp:maintenance-0.1">
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 which was requested with a explicit <maint:id>. In this case, it
provides the all "required" elements and additional elements provides the all "required" elements and additional elements
skipping to change at page 7, line 44 skipping to change at page 7, line 42
<maint:tlds>, <maint:intervention>. <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:epp:maintenance-0.1">
S: <maint:maint> S: <maint:item>
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>epp.registry.example S: <maint:host>epp.registry.example
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>
skipping to change at page 8, line 18 skipping to change at page 8, line 18
S: <maint:description lang="en">free text S: <maint:description lang="en">free text
S: </maint:description> 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:crDate>2017-03-08T22:10:00Z</maint:crDate> S: <maint:crDate>2017-03-08T22:10:00Z</maint:crDate>
S: </maint:maint> S: </maint:item>
S: </maint:infData> S: </maint:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
3.1.3.2. Query maintenance list
Example <info> command with <maint:list> to query all maintenances Example <info> command with <maint:list> to query all maintenances
subject to server policy: subject to server policy:
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:epp:maintenance-0.1">
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. In this case, all the "required" elements will be returned policy. In this case, all the "required" elements will be returned
and additional <maint:upDate>. 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:epp:maintenance-0.1">
S: <maint:list> S: <maint:list>
S: <maint:maint> S: <maint:listItem>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6
S: </maint:id> S: </maint:id>
S: <maint:start>2017-04-30T06:00:00Z</maint:start> S: <maint:start>2017-04-30T06:00:00Z</maint:start>
S: <maint:end>2017-04-30T07:00:00Z</maint:end> S: <maint:end>2017-04-30T07:00:00Z</maint:end>
S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate> S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate>
S: </maint:maint> S: </maint:listItem>
S: <maint:maint> S: <maint:listItem>
S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f
S: </maint:id> S: </maint:id>
S: <maint:start>2017-06-15T04:30:00Z</maint:start> S: <maint:start>2017-06-15T04:30:00Z</maint:start>
S: <maint:end>2017-06-15T05:30:00Z</maint:end> S: <maint:end>2017-06-15T05:30:00Z</maint:end>
S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate> S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate>
S: <maint:upDate>2017-03-08T20:11:00Z</maint:upDate> S: <maint:upDate>2017-03-08T20:11:00Z</maint:upDate>
S: </maint:maint> S: </maint:listItem>
S: </maint:list> S: </maint:list>
S: </maint:infData> S: </maint:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
skipping to change at page 10, line 29 skipping to change at page 10, line 29
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 lang="en">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:epp:maintenance-0.1">
S: <maint:maint> S: <maint:item>
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>epp.registry.example S: <maint:host>epp.registry.example
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"/>
skipping to change at page 11, line 4 skipping to change at page 11, line 4
S: https://www.registry.example/notice?123 S: https://www.registry.example/notice?123
S: </maint:detail> S: </maint:detail>
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:crDate>2017-02-08T22:10:00Z</maint:crDate> S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate>
S: </maint:maint> S: </maint:item>
S: </maint:infData> S: </maint:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
3.2. EPP Transform Commands 3.2. EPP Transform Commands
skipping to change at page 12, line 20 skipping to change at page 12, line 20
The formal syntax presented here is a complete schema representation The formal syntax presented here is a complete schema representation
of the object mapping suitable for automated validation of EPP XML of the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they instances. The BEGIN and END tags are not part of the schema; they
are used to note the beginning and end of the schema for URI are used to note the beginning and end of the schema for URI
registration purposes. registration purposes.
4.1. Registry Maintenance EPP Mapping Schema 4.1. Registry Maintenance EPP Mapping Schema
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:maintenance-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:epp:
maintenance-0.1"
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:maintenance-1.0" xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"
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"/>
<annotation> <annotation>
skipping to change at page 13, line 27 skipping to change at page 13, line 27
Info Response element Info Response element
--> -->
<element name="infData" type="maint:infDataType"/> <element name="infData" type="maint:infDataType"/>
<!-- <!--
<info> response elements. <info> response elements.
--> -->
<complexType name="infDataType"> <complexType name="infDataType">
<choice> <choice>
<element name="list" type="maint:listDataType"/> <element name="list" type="maint:listDataType"/>
<element name="maint" type="maint:maintDataType"/> <element name="item" type="maint:maintDataType"/>
</choice> </choice>
</complexType> </complexType>
<!-- <!--
Attributes associated with the list info response Attributes associated with the list info response
--> -->
<complexType name="listDataType"> <complexType name="listDataType">
<sequence> <sequence>
<element name="maint" type="maint:maintItemType" <element name="listItem" type="maint:maintItemType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Attributes associated with the list item info response Attributes associated with the list item info response
--> -->
<complexType name="maintItemType"> <complexType name="maintItemType">
<sequence> <sequence>
<element name="id" type="maint:idType"/> <element name="id" type="maint:idType"/>
skipping to change at page 14, line 21 skipping to change at page 14, line 21
<element name="environment" type="maint:envType"/> <element name="environment" type="maint:envType"/>
<element name="start" type="dateTime" minOccurs="0"/> <element name="start" type="dateTime" minOccurs="0"/>
<element name="end" type="dateTime" minOccurs="0"/> <element name="end" type="dateTime" minOccurs="0"/>
<element name="reason" type="maint:reasonEnum"/> <element name="reason" type="maint:reasonEnum"/>
<element name="detail" type="anyURI" 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" minOccurs="0"/> <element name="tlds" type="maint:tldsType" minOccurs="0"/>
<element name="intervention" type="maint:interventionType" <element name="intervention" type="maint:interventionType"
minOccurs="0"/> minOccurs="0"/>
<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">
<sequence> <sequence>
skipping to change at page 16, line 45 skipping to change at page 17, line 4
<!-- <!--
intervention element intervention element
--> -->
<complexType name="interventionType"> <complexType name="interventionType">
<sequence> <sequence>
<element name="connection" type="boolean"/> <element name="connection" type="boolean"/>
<element name="implementation" type="boolean"/> <element name="implementation" type="boolean"/>
</sequence> </sequence>
</complexType> </complexType>
<!--
Enumerated list of statuses
-->
<simpleType name="statusEnum">
<restriction base="token">
<enumeration value="active"/>
<enumeration value="inactive"/>
</restriction>
</simpleType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace 5.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism defined in [RFC3688]. conforming to a registry mechanism defined in [RFC3688].
Registration request for the maintenance namespace: Registration request for the maintenance namespace:
URI: urn:ietf:params:xml:ns:maintenance-1.0 URI: urn:ietf:params:xml:ns:epp:maintenance-0.1
Registrant Contact: IESG Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the maintenance schema: Registration request for the maintenance schema:
URI: urn:ietf:params:xml:schema:maintenance-1.0 URI: urn:ietf:params:xml:schema:maintenance-1.0
Registrant Contact: IESG Registrant Contact: IESG
skipping to change at page 20, line 9 skipping to change at page 20, line 9
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.6. Change from 03 to 04
A lot of clarifications and editoral changes. A lot of clarifications and editoral changes.
A.7. Change from 04 to 05
Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to
urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed <maint:status>.
Clarified <maint:info> for retrieving maintenance items and the list.
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. 37 change blocks. 
56 lines changed or deleted 47 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/