draft-ietf-regext-epp-registry-maintenance-07.txt   draft-ietf-regext-epp-registry-maintenance-08.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.
December 11, 2020 December 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-07 draft-ietf-regext-epp-registry-maintenance-08
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 12 skipping to change at page 2, line 12
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . . . 5 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5 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. Info Maintenance Item . . . . . . . . . . . . . . . 6 3.1.3.1. Info Maintenance Item . . . . . . . . . . . . . . . 6
3.1.3.2. Info Maintenance List . . . . . . . . . . . . . . . 8 3.1.3.2. Info Maintenance List . . . . . . . . . . . . . . . 8
3.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 9 3.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 9
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . . . . . . . . . 11 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 11 4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
7.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 17 7.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . 18
8.2. Informative References . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18
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 . . . . . . . . . 18 draft-sattler-epp-registry-maintenance . . . . . . . . . 18
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 . . . . . . . 18 draft-ietf-regext-epp-registry-maintenance . . . . . . . 18
A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19
A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18 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 . . . . . . . . . . . . . . . . . . 19 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 19
A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 19 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 19
A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19
A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19 A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19
A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 19
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 19 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
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.
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provision Protocol [RFC5730]. This mapping provides a Extensible Provision Protocol [RFC5730]. This mapping provides a
mechanism by which EPP servers may notify and EPP clients to query mechanism by which EPP servers may notify and EPP clients to query
upcoming maintenances. upcoming maintenances.
1.1. Terminology and Definitions 1.1. Terminology and Definitions
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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119] when "OPTIONAL" in this document are to be interpreted as described in
specified in their uppercase forms. BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals 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.1". The XML namespace prefix "maint" is used, but maintenance-0.2". 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 only illustrate element relationships and are white space in examples are provided only to illustrate element
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 as A-label according to Names of affected hosts MUST be provided as an 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:item> element describes a single registry maintenance The <maint:item> element describes a single registry maintenance
event during a specific period. This element is used in a maintenance event during a specific period. This element is used in a maintenance
item EPP <info> response and <poll> message. item EPP <info> response and <poll> message.
<maint:id> <maint:id>
Server unique identifier for the maintenance with an OPTIONAL "msg" The server unique identifier for the maintenance with the OPTIONAL
attribute that includes a human-readable description of the "msg" attribute that includes a human-readable description of the
maintenance. The server unique identifier SHALL NOT be changed if maintenance. The server unique identifier SHALL NOT be changed if
the maintenance is updated or deleted. When the "msg" attribute is the maintenance is updated or deleted. When the "msg" attribute is
set, an OPTIONAL "lang" attribute MAY be present to identify the set, the OPTIONAL "lang" attribute MAY be present to identify the
language if the negotiated value is something other than the language if the negotiated value is something other than the
default value of "en" (English). default value of "en" (English).
<maint:pollType>
The OPTIONAL <maint:pollType> for a Registry Maintenance
Notification poll message; values MUST either be "create",
"update", or "delete". For the "create" and "update" types, the
server includes the state of the maintenance after the create or
update. For the "delete" type, the server includes the state
of the maintenance prior to the delete. This element MUST be
present only for poll messages.
<maint:systems> <maint:systems>
Indicates one or more <maint:system> elements that are affected by One or more <maint:system> elements that are affected by the
the maintenance. maintenance.
<maint:system> <maint:system>
The <maint:system> element contains the following child The <maint:system> element contains the following child
elements: elements:
<maint:name> <maint:name>
Indicates the name of the affected system, such as "EPP", The name of the affected system, such as "EPP", "WHOIS",
"WHOIS", "DNS", "Portal", etc. "DNS", "Portal", etc.
<maint:host> <maint:host>
Indicates the affected maintained system contains the hostname, The affected maintained system contains the hostname, which
which SHALL be A-label according [RFC5891]. SHALL be an A-label according to [RFC5891].
<maint:impact> <maint:impact>
Indicates the impact level; values MUST either be "full" or The impact level; the values MUST either be "full" or
"partial". "partial".
<maint:environment> <maint:environment>
Indicates the type of the affected system; the attribute type is The type of the affected system; the attribute "type" is
REQUIRED and SHOULD either be "production", "ote", "staging", REQUIRED and MUST either be "production", "ote", "staging",
"dev" or "custom". And alternatively, the attribute name could be "dev" or "custom". For extensibility, the <maint:environment>
used to define a server specific affected system, for example. In element includes the OPTIONAL "name" attribute that can define
that case, name MUST be set: the name of the custom environment when the <maint:environment>
<maint:environment type="custom" name="marketing"/> element "type" attribute has the "custom" value. For example,
for the custom "marketing" environment, the <maint:environment>
element should be:
<maint:environment type="custom" name="marketing"/>
<maint:start> <maint:start>
Indicates the date and time of the start of the maintenance. The date and time of the start of the maintenance.
<maint:end> <maint:end>
Indicates the date and time of the end of the maintenance. The The date and time of the end of the maintenance. The
<maint:end> element MUST be equal or greater than the <maint:end> element MUST be equal to or greater than the
<maint:start> element. <maint:start> element.
<maint:reason> <maint:reason>
Indicates the reason behind the maintenance; values SHOULD either The reason behind the maintenance; the values MUST either be
be "planned" or "emergency". "planned" or "emergency".
<maint:detail> <maint:detail>
Contains URI to detailed maintenance description. The OPTIONAL URI to detailed maintenance description.
<maint:description> <maint:description>
A freeform description of the maintenance without having to The OPTIONAL free-form description of the maintenance without
create and traverse an external resource defined by the having to create and traverse an external resource defined by
<maint:detail> element. An OPTIONAL "lang" attribute MAY be the <maint:detail> element. The OPTIONAL "lang" attribute MAY
present to identify the language if the negotiated value is be present to identify the language if the negotiated value is
something other than the default value of "en" (English). something other than the default value of "en" (English).
<maint:tlds> <maint:tlds>
The <maint:tlds> element contains the following child element: The OPTIONAL <maint:tlds> element contains one or more
<maint:tld> child elements.
<maint:tld> <maint:tld>
Contains the affected top-level domain, which SHALL be A-label The affected top-level domain or registry zone, which SHALL
according [RFC5891]. be an A-label according to [RFC5891].
<maint:intervention> <maint:intervention>
The <maint:intervention> element contains the following child The OPTIONAL <maint:intervention> element contains the
elements: following child elements:
<maint:connection> <maint:connection>
The value SHALL be boolean and indicates if a client needs to The value SHALL be boolean and indicates if a client needs
do something that is connection-related, such as a reconnect. to do something that is connection-related, such as a
reconnect.
<maint:implementation> <maint:implementation>
The value SHALL be boolean and indicates if a client needs to The value SHALL be boolean and indicates if a client needs
do something that is implementation-related, such as a code to do something that is implementation-related, such as a
change. code change.
<maint:crDate> <maint:crDate>
Indicates the date and time of the maintenance object creation. The date and time of the maintenance object creation.
<maint:upDate> <maint:upDate>
Indicates the date and time of the most recent maintenance object The OPTIONAL date and time of the most recent maintenance
modification. This element MUST NOT be present if the maintenance object modification. This element MUST NOT be present if the
object has never been modified. maintenance object has never been modified.
3. EPP Command Mapping 3. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. The command in the EPP core protocol specification [RFC5730]. The command
mappings described here are specifically for the use to notify of mappings described here are specifically for the use to notify of
Registry Maintenances and Registry Maintenance object mapping. Registry Maintenances and Registry Maintenance object mapping.
3.1. EPP Query Commands 3.1. EPP Query Commands
skipping to change at page 6, line 42 skipping to change at page 7, line 10
identifier does not exist, the server MUST return an EPP error result identifier does not exist, the server MUST return an EPP error result
code of 2303 [RFC5730]. code of 2303 [RFC5730].
Example to retrieve a specific maintenance item in an <info> command. Example to retrieve a specific maintenance item in an <info> 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: <info> C: <info>
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"> C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2">
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>
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <maint:infData> element that <resData> element MUST contain a child <maint:infData> element that
identifies the maintenance namespace. The <maint:infData> element identifies the maintenance namespace. The <maint:infData> element
contains the <maint:item> element defined in Section 2.3. contains the <maint:item> element defined in Section 2.3.
Example of returning a specific maintenance item in an <info> Example of returning a specific maintenance item in an <info>
response. response.
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>
skipping to change at page 7, line 13 skipping to change at page 7, line 35
response. response.
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:epp:maintenance-0.1"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2">
S: <maint:item> 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>full</maint:impact> S: <maint:impact>full</maint:impact>
S: </maint:system> S: </maint:system>
skipping to change at page 8, line 19 skipping to change at page 8, line 33
<maint:list> child element. Server policy determines if previous <maint:list> child element. Server policy determines if previous
maintenances will be included in the list of maintenance items. maintenances will be included in the list of maintenance items.
Example to retrieve the maintenance list in an <info> command. Example to retrieve the maintenance list in an <info> 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: <info> C: <info>
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"> C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2">
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>
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <maint:infData> element <resData> element MUST contain a child <maint:infData> element
that identifies the maintenance namespace. The <maint:infData> that identifies the maintenance namespace. The <maint:infData>
element contains the <maint:list> element with zero or more element contains the <maint:list> element with zero or more
<maint:listItem> child elements. The <maint:listItem> element <maint:listItem> child elements. The <maint:listItem> element
contains the following child elements: contains the following child elements:
<maint:id>: <maint:id> defined in Section 2.3.
<maint:start>: <maint:start> defined in Section 2.3. <maint:id>
<maint:end>: <maint:end> defined in Section 2.3. The <maint:id> defined in Section 2.3.
<maint:crDate>: <maint:crDate> defined in Section 2.3.
<maint:upDate>: OPTIONAL <maint:upDate> defined in Section 2.3. <maint:start>
The <maint:start> defined in Section 2.3.
<maint:end>
The <maint:end> defined in Section 2.3.
<maint:crDate>
The <maint:crDate> defined in Section 2.3.
<maint:upDate>
The OPTIONAL <maint:upDate> defined in Section 2.3.
Example of returning the maintenance list in an <info> response. Example of returning the maintenance list in an <info> response.
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:epp:maintenance-0.1"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2">
S: <maint:list> S: <maint:list>
S: <maint:listItem> 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>2020-12-30T06:00:00Z</maint:start> S: <maint:start>2020-12-30T06:00:00Z</maint:start>
S: <maint:end>2020-12-30T07:00:00Z</maint:end> S: <maint:end>2020-12-30T07:00:00Z</maint:end>
S: <maint:crDate>2020-09-08T22:10:00Z</maint:crDate> S: <maint:crDate>2020-09-08T22:10:00Z</maint:crDate>
S: </maint:listItem> S: </maint:listItem>
S: <maint:listItem> S: <maint:listItem>
S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f
skipping to change at page 9, line 29 skipping to change at page 9, line 52
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. A poll message applies when a maintenance is created, poll messages, defined by the <maint:pollType> element in Section
updated, or deleted. In the case of a Registry Maintenance specific 2.3. A poll message applies when a maintenance is created, updated,
message, a <maint:infData> element will be included within the or deleted. In the case of a Registry Maintenance specific message,
<resData> element of the standard <poll> response. The a <maint:infData> element will be included within the <resData>
<maint:infData> element contains the <maint:item> element defined element of the standard <poll> response. The <maint:infData> element
in Section 2.3. contains the <maint:item> element defined 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:
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>2020-10-08T22:10:00Z</qDate> S: <qDate>2020-10-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:epp:maintenance-0.1"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2">
S: <maint:item> 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:pollType>create</maint:pollType>
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>full</maint:impact> S: <maint:impact>full</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>2020-12-30T06:00:00Z</maint:start> S: <maint:start>2020-12-30T06:00:00Z</maint:start>
skipping to change at page 11, line 40 skipping to change at page 12, line 5
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.
4.1. Registry Maintenance EPP Mapping Schema 4.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.1" maintenance-0.2"
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.1" xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2"
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>
<documentation> <documentation>
Extensible Provisioning Protocol v1.0 Extensible Provisioning Protocol v1.0
skipping to change at page 13, line 10 skipping to change at page 13, line 28
<element name="listItem" 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"/>
<element name="start" type="dateTime" minOccurs="0"/> <element name="start" type="dateTime"/>
<element name="end" type="dateTime" minOccurs="0"/> <element name="end" type="dateTime"/>
<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>
<!-- <!--
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="pollType" type="maint:pollType" minOccurs="0"/>
<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" minOccurs="0"/> <element name="start" type="dateTime"/>
<element name="end" type="dateTime" minOccurs="0"/> <element name="end" type="dateTime"/>
<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="crDate" type="dateTime"/> <element name="crDate" type="dateTime"/>
<element name="upDate" type="dateTime" minOccurs="0"/> <element name="upDate" type="dateTime" minOccurs="0"/>
</sequence> </sequence>
skipping to change at page 13, line 47 skipping to change at page 14, line 14
<!-- <!--
systems element systems element
--> -->
<complexType name="systemsType"> <complexType name="systemsType">
<sequence> <sequence>
<element name="system" type="maint:systemType" <element name="system" type="maint:systemType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Enumerated list of poll types
-->
<simpleType name="pollType">
<restriction base="token">
<enumeration value="create"/>
<enumeration value="update"/>
<enumeration value="delete"/>
</restriction>
</simpleType>
<!--
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="full"/> <enumeration value="full"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
description element description element
skipping to change at page 14, line 20 skipping to change at page 14, line 48
<attribute name="lang" type="language" default="en"/> <attribute name="lang" type="language" default="en"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </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:addrType"/> <element name="host" type="eppcom:labelType"/>
<element name="impact" type="maint:impactEnum"/> <element name="impact" type="maint:impactEnum"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
host element
-->
<complexType name="addrType">
<simpleContent>
<extension base="maint:addrStringType"/>
</simpleContent>
</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"/>
</restriction> </restriction>
skipping to change at page 16, line 14 skipping to change at page 16, line 14
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:epp:maintenance-0.1 URI: urn:ietf:params:xml:ns:epp:maintenance-0.2
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-0.2
Registrant Contact: IESG Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry 5.2. EPP Extension Registry
The following registration of the EPP Extension Registry, described The following registration of the EPP Extension Registry, described
in [RFC7451], is requested: in [RFC7451], is requested:
skipping to change at page 18, line 13 skipping to change at page 18, line 21
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009, STD 69, RFC 5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002, Internet: Timestamps", RFC 3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC5891] Klensin, J., "Internationalized Domain Names in [RFC5891] Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", RFC 5891, August 2010, Applications (IDNA): Protocol", RFC 5891, August 2010,
<https://www.rfc-editor.org/info/rfc5891>. <https://www.rfc-editor.org/info/rfc5891>.
skipping to change at page 19, line 29 skipping to change at page 19, line 43
A.8. Change from 05 to 06 A.8. Change from 05 to 06
Changed dates in examples to more recent dates. Renamed Query Changed dates in examples to more recent dates. Renamed Query
Maintenance Item and List to Info Maintenance Item and List. Removed Maintenance Item and List to Info Maintenance Item and List. Removed
blackout in favor of full. Added GoDaddy Registry implementation. blackout in favor of full. Added GoDaddy Registry implementation.
A.9. Change from 06 to 07 A.9. Change from 06 to 07
Removed IP addresses for <maint:host>. Editoral changes. Removed IP addresses for <maint:host>. Editoral changes.
A.10. Change from 07 to 08
Editoral changes. Changed XML namespace and schema from 0.1 to 0.2.
Added pollType to reflect create, update, or delete maintenance poll
messages.
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. 55 change blocks. 
132 lines changed or deleted 161 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/