<?xmlversion='1.0' encoding='utf-8'?>version="1.0" encoding="UTF-8"?> <!DOCTYPE rfcSYSTEM "rfc2629.dtd"[ <!ENTITYW3C.REC-html5-20141028 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml4/reference.W3C.REC-html5-20141028.xml"> <!ENTITY W3C.REC-xml11-20060816 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml4/reference.W3C.REC-xml11-20060816.xml"> <!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> <!ENTITY RFC3339 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"> <!ENTITY RFC3986 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"> <!ENTITY RFC5730 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5730.xml"> <!ENTITY RFC5891 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5891.xml"> <!ENTITY RFC7942 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7942.xml"> <!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">nbsp " "> <!ENTITYRFC9038 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9038.xml">zwsp "​"> <!ENTITYRFC3688 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml">nbhy "‑"> <!ENTITYRFC7451 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7451.xml">wj "⁠"> ]> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF"docName="draft-ietf-regext-epp-registry-maintenance-19"category="std"ipr="trust200902"> <!-- Generated by id2xml 1.5.0 on 2021-10-20T00:36:29Z --> <?rfc strict="yes"?> <?rfc compact="yes"?> <?rfc subcompact="no"?> <?rfc symrefs="yes"?> <?rfc sortrefs="no"?> <?rfc text-list-symbols="o*+-"?> <?rfc toc="yes"?>consensus="true" docName="draft-ietf-regext-epp-registry-maintenance-19" number="9167" ipr="trust200902" obsoletes="" updates="" xml:lang="en" symRefs="true" sortRefs="true" tocInclude="true" version="3"> <front> <titleabbrev="Registry Maintenance Notification for th">Registryabbrev="EPP Registry Maintenance">Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)</title> <seriesInfo name="RFC" value="9167"/> <author initials="T." surname="Sattler" fullname="Tobias Sattler"><organization></organization> <address><email>mail@tobiassattler.com</email><organization/> <address> <email>mail@tobiassattler.com</email> <uri>https://tobiassattler.com</uri> </address> </author> <author initials="R." surname="Carney" fullname="Roger Carney"> <organization>GoDaddy Inc.</organization> <address> <postal><street>14455 N. Hayden Rd. #219</street> <city>Scottsdale</city><street>2155 E GoDaddy Way</street> <city>Tempe</city> <region>AZ</region><code>85260</code> <country>USA</country><code>85284</code> <country>United States of America</country> </postal> <email>rcarney@godaddy.com</email> <uri>https://www.godaddy.com</uri> </address> </author> <author initials="J." surname="Kolker" fullname="Jody Kolker"> <organization>GoDaddy Inc.</organization> <address> <postal><street>14455 N. Hayden Rd. #219</street> <city>Scottsdale</city><street>2155 E GoDaddy Way </street> <city>Tempe</city> <region>AZ</region><code>85260</code> <country>USA</country><code>85284</code> <country>United States of America</country> </postal> <email>jkolker@godaddy.com</email> <uri>https://www.godaddy.com</uri> </address> </author> <date year="2021"month="October"/> <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> <keyword>example</keyword> <abstract><t>month="December"/> <abstract> <t> This document describes an Extensible Provisioning Protocol (EPP) extension called "Registry Maintenance Notification", which is used by EPP servers to notify EPP clients and allow EPP clients to query EPP servers regarding maintenance events.</t> </abstract> </front> <middle> <sectiontitle="Introduction" anchor="sect-1"><t>anchor="sect-1" numbered="true" toc="default"> <name>Introduction</name> <t> The Extensible Provisioning Protocol (EPP), as defined in <xreftarget="RFC5730"/>,target="RFC5730" format="default"/>, is a protocol whose original motivation is to provide a standard Internet domain name registration protocol for use between registries and registrars.</t> <t> Registries routinely update systems to ensure a higher quality of service, implement new services, or upgrade protocols to the latest standards. These updates are pushed to various registry environments during time frames communicated to registrars as "maintenance events". Maintenance events may require making services unavailable for some limited time while the upgrade happens. Registries usually inform registrars about maintenance events in various formats, none of which are standardized between registries.</t> <t> The DNS namespace expansion has led to many additional registries that registrars must interact with, adding more maintenance events and formats. It is now desirable to provide an efficient approach to notify registrars.</t> <t> This document describes an extension mapping for version 1.0 of the EPP to provide a mechanism by which EPP servers may notify EPP clients of and allow EPP clients to query EPP servers on upcoming maintenance events.</t> <sectiontitle="Terminologyanchor="sect-1.1" numbered="true" toc="default"> <name>Terminology andDefinitions" anchor="sect-1.1"><t>Definitions</name> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t>here. </t> <t> XML <xreftarget="W3C.REC-xml11-20060816"/>target="W3C.REC-xml-20081126" format="default"/> iscase-sensitive.case sensitive. Unless stated otherwise, XMLspecificationspecifications and examples provided in this documentMUST<bcp14>MUST</bcp14> be interpreted in the character case presented in order to develop a conforming implementation.</t> <t>"maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: maintenance-1.0".The XML namespace prefix "maint" isused,used for the namespace "urn:ietf:params:xml:ns:epp:maintenance-1.0", but implementationsMUST NOT<bcp14>MUST NOT</bcp14> depend onit. Instead, they are toit and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XMLdocuments.</t>documents. </t> <t> "ote" is an abbreviation for "Operational Test and Evaluation".</t> <t> In examples, "C:" represents lines sent by a protocol client, and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a required feature of this protocol.</t> </section> </section> <sectiontitle="Migratinganchor="sect-2" numbered="true" toc="default"> <name>Migrating to Newer Versions of ThisExtension" anchor="sect-2"><t>Extension</name> <t> Servers that implement this extensionSHOULD<bcp14>SHOULD</bcp14> provide a way for clients to progressively update their implementations when a new version of the extension is deployed. A newer version of the extension is expected to use an XML namespace with a higher version number than the prior versions.</t> <t> ServersSHOULD<bcp14>SHOULD</bcp14> (for a temporary migration period up to server policy) provide support for older versions of the extension in parallel to the newest version and allow clients to execute their preferred version of the <info> command based on the maintenance <objURI> elements of the server <greeting>. The version of the maintenance <info> responseMUST<bcp14>MUST</bcp14> match the version of the maintenance <info> command executed by the server.</t> <t> ServersMUST<bcp14>MUST</bcp14> return a Registry Maintenance Notification poll message matching the newest negotiated version of the maintenance extension, based on an intersection of the maintenance <objURI> elements in the server <greeting> and the client <login> command. If the intersection of the maintenance <objURI> elements of the server <greeting> and the client <login> command results in an empty set, the serverMUST<bcp14>MUST</bcp14> return the newest version of the Registry Maintenance Notification poll message supported by the server based on "Usage with Poll-Message EPP Responses" inSection 6 of<xreftarget="RFC9038"/>.</t> </section> <section title="Object Attributes" anchor="sect-3"><section title="Internationalizedtarget="RFC9038" sectionFormat="of" section="6" format="default"/>.</t> </section> <section anchor="sect-3" numbered="true" toc="default"> <name>Object Attributes</name> <section anchor="sect-3.1" numbered="true" toc="default"> <name>Internationalized DomainNames" anchor="sect-3.1"><t>Names</name> <t> Names of affected hostsMUST<bcp14>MUST</bcp14> be provided in A-label form, according to <xreftarget="RFC5891"/>.</t>target="RFC5891" format="default"/>.</t> </section> <sectiontitle="Datesanchor="sect-3.2" numbered="true" toc="default"> <name>Dates andTimes" anchor="sect-3.2"><t>Times</name> <t> All date and time attribute valuesMUST<bcp14>MUST</bcp14> be expressed in Universal Coordinated Time (UTC) using the Gregorian calendar. The date-time format defined as "date-time" in <xreftarget="RFC3339"/>,target="RFC3339" format="default"/>, with time-offset="Z",MUST<bcp14>MUST</bcp14> be used.</t> </section> <sectiontitle="Maintenance Elements" anchor="sect-3.3"><t>anchor="sect-3.3" numbered="true" toc="default"> <name>Maintenance Elements</name> <t> The <maint:item> element describes a single registry maintenance event during a specific period. This element is used in a maintenance item EPP <info> command andresponse, andresponse as well as in a <poll> response.</t> <t> If an element is not marked as optional, it is mandatory.</t><t><list style="hanging" hangIndent="3"><t hangText="<maint:id>"> <vspace blankLines="0"/><dl newline="true" spacing="normal" indent="3"> <dt><maint:id></dt> <dd> Theserver uniqueserver-unique identifier for the maintenance event with theOPTIONAL<bcp14>OPTIONAL</bcp14> "name" attribute that includes a human-readable name of the event. Theserver uniqueserver-unique identifierSHALL NOT<bcp14>SHALL NOT</bcp14> be changed if the event is updated or deleted. When the "name" attribute is set, theOPTIONAL<bcp14>OPTIONAL</bcp14> "lang"attribute MAYattribute, per the language structure in <xref target="RFC5646"/>, <bcp14>MAY</bcp14> be present to identify the language if the negotiated value is something other than the default value of "en" (English).</t> <t hangText="<maint:type>"> <vspace blankLines="0"/></dd> <dt><maint:type></dt> <dd> Zero or moreOPTIONAL<bcp14>OPTIONAL</bcp14> types of the maintenance event, with the possible set of values defined by server policy, such as "Routine Maintenance", "Software Update", "Software Upgrade", or "Extended Outage". TheOPTIONAL<bcp14>OPTIONAL</bcp14> "lang" attributeMAY<bcp14>MAY</bcp14> be present to identify the language if the negotiated value is something other than the default value of "en" (English).</t> <t hangText="<maint:pollType>"> <vspace blankLines="0"/></dd> <dt><maint:pollType></dt> <dd> TheOPTIONAL<bcp14>OPTIONAL</bcp14> <maint:pollType> element for a Registry Maintenance Notification poll message; valuesMUST either<bcp14>MUST</bcp14> be "create", "update", "delete", "courtesy", or "end". For the "create" and "update" types, the server includes the state of the maintenance event after the creation or update. For the "delete" type, the server includes the state of the event before the delete. The "courtesy" provides a reminder of an event, and the "end" provides a notification of the end of the event without updating the maintenance object and includes the latest state of the event. This elementMUST<bcp14>MUST</bcp14> be present only for poll messages.</t> <t hangText="<maint:systems>"> <vspace blankLines="0"/></dd> <dt><maint:systems></dt> <dd> <t> One or more <maint:system> elements that are affected by the maintenance event.<list style="hanging" hangIndent="3"><t hangText="<maint:system>"> <vspace blankLines="0"/></t> <dl newline="true" spacing="normal" indent="3"> <dt><maint:system></dt> <dd> <t> The <maint:system> element contains the following child elements:<list style="hanging" hangIndent="3"><t hangText="<maint:name>"> <vspace blankLines="0"/></t> <dl newline="true" spacing="normal" indent="3"> <dt><maint:name></dt> <dd> The name of the affected system, such as "EPP", "WHOIS", "DNS", "Portal", "RDAP", etc.</t> <t hangText="<maint:host>"> <vspace blankLines="0"/></dd> <dt><maint:host></dt> <dd> TheOPTIONAL<bcp14>OPTIONAL</bcp14> affected maintained system's hostname, whichSHALL<bcp14>SHALL</bcp14> be in A-label form, according to <xreftarget="RFC5891"/>.</t> <t hangText="<maint:impact>"> <vspace blankLines="0"/>target="RFC5891" format="default"/>.</dd> <dt><maint:impact></dt> <dd> The impact level; the valuesMUST either<bcp14>MUST</bcp14> be "full", "partial", or "none". If access is expected to be intermittently unavailable, it is "partial". If access is expected to be completely unavailable, it is "full". If access is not affected, it is "none".</t> </list> </t> </list> </t> </list> </t> <t><list style="hanging" hangIndent="3"><t hangText="<maint:environment>"> <vspace blankLines="0"/></dd> </dl> </dd> </dl> </dd> </dl> <dl newline="true" spacing="normal" indent="3"> <dt><maint:environment></dt> <dd> The type of the affected system; the attribute "type" isREQUIRED<bcp14>REQUIRED</bcp14> andMUST either<bcp14>MUST</bcp14> be "production", "ote", "staging","dev""dev", or "custom". For extensibility, the <maint:environment> element includes theOPTIONAL<bcp14>OPTIONAL</bcp14> "name" attribute that can define the name of the custom environment when the <maint:environment> 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"/> </t> <t hangText="<maint:start>"> <vspace blankLines="0"/>name="marketing"/>. </dd> <dt><maint:start></dt> <dd> The date and time of the start of the maintenance event.</t> <t hangText="<maint:end>"> <vspace blankLines="0"/></dd> <dt><maint:end></dt> <dd> The date and time of the end of the maintenance event. The <maint:end> elementMUST<bcp14>MUST</bcp14> be greater than the <maint:start> element.</t> <t hangText="<maint:reason>"> <vspace blankLines="0"/></dd> <dt><maint:reason></dt> <dd> The reason behind the maintenance event; the valuesMUST either<bcp14>MUST</bcp14> be either "planned" or "emergency".</t> <t hangText="<maint:detail>"> <vspace blankLines="0"/></dd> <dt><maint:detail></dt> <dd> TheOPTIONAL<bcp14>OPTIONAL</bcp14> URI to the detailed maintenance event description, formatted according to <xreftarget="RFC3986"/>. </t> <t hangText="<maint:description>"> <vspace blankLines="0"/>target="RFC3986" format="default"/>. </dd> <dt><maint:description></dt> <dd> Zero or moreOPTIONAL<bcp14>OPTIONAL</bcp14> free-form descriptions of the maintenance event, usable without creating and traversing an external resource as defined by the <maint:detail> element. TheOPTIONAL<bcp14>OPTIONAL</bcp14> "lang" attributeMAY<bcp14>MAY</bcp14> be present to identify the language if the negotiated value is something other than the default value of "en" (English). TheOPTIONAL<bcp14>OPTIONAL</bcp14> "type" attributeMAY<bcp14>MAY</bcp14> be present to identify the format of the description. ItMUST either<bcp14>MUST</bcp14> be either "plain" for plain text or "html" for HTMLtext that istext, as defined in <xreftarget="W3C.REC-html5-20141028"/>target="HTML5" format="default"/>, and XML-escaped, with a default value of "plain".</t> <t hangText="<maint:tlds>"> <vspace blankLines="0"/></dd> <dt><maint:tlds></dt> <dd> <t> TheOPTIONAL<bcp14>OPTIONAL</bcp14> <maint:tlds> element contains one or more <maint:tld> child elements. If the <maint:tlds> is not present, the entire system is affected.<list style="hanging" hangIndent="3"><t hangText="<maint:tld>"> <vspace blankLines="0"/></t> <dl newline="true" spacing="normal" indent="3"> <dt><maint:tld></dt> <dd> The affected top-level domain or registry zone, whichSHALL<bcp14>SHALL</bcp14> be in A-label form, according to <xreftarget="RFC5891"/>. </t> </list> </t> <t><list style="hanging" hangIndent="3"><t hangText="<maint:intervention>"> <vspace blankLines="0"/>target="RFC5891" format="default"/>. </dd> </dl> </dd> <dt/> <dd> <dl newline="true" spacing="normal" indent="3"> <dt><maint:intervention></dt> <dd> <t> TheOPTIONAL<bcp14>OPTIONAL</bcp14> <maint:intervention> element contains the following child elements:<list style="hanging" hangIndent="3"><t hangText="<maint:connection>"> <vspace blankLines="0"/></t> <dl newline="true" spacing="normal" indent="3"> <dt><maint:connection></dt> <dd> The valueSHALL<bcp14>SHALL</bcp14> be boolean and indicates if a client needs to perform a connection-relatedaction,action such as a reconnect. The attribute should only be used as a flag to indicate connections will be affected. ServersSHOULD<bcp14>SHOULD</bcp14> include a description of how the connections are affected in the <maint:description> element or use the <maint:detail> element above.</t> <t hangText="<maint:implementation>"> <vspace blankLines="0"/></dd> <dt><maint:implementation></dt> <dd> The valueSHALL<bcp14>SHALL</bcp14> be boolean and indicates if a client needs to perform an implementation-relatedaction,action such as a code change. The attribute should only be used as a flag to indicate implementation will be affected. ServersSHOULD<bcp14>SHOULD</bcp14> include a description of how the implementation is affected in the <maint:description> element or use the <maint:detail> element above.</t> </list> </t> <t hangText="<maint:crDate>"> <vspace blankLines="0"/></dd> </dl> </dd> <dt><maint:crDate></dt> <dd> The date and time of the maintenance object creation.</t> <t hangText="<maint:upDate>"> <vspace blankLines="0"/></dd> <dt><maint:upDate></dt> <dd> TheOPTIONAL<bcp14>OPTIONAL</bcp14> date and time of the most recent maintenance object modification. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the maintenance object has never been modified.</t> </list> </t> </list> </t></dd> </dl> </dd> </dl> </section> </section> <sectiontitle="EPPanchor="sect-4" numbered="true" toc="default"> <name>EPP CommandMapping" anchor="sect-4"><t>Mapping</name> <t> A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification <xreftarget="RFC5730"/>.target="RFC5730" format="default"/>. The command mappings described here are specifically used to notify registrars of registry maintenance events and object mapping.</t> <sectiontitle="EPPanchor="sect-4.1" numbered="true" toc="default"> <name>EPP QueryCommands" anchor="sect-4.1"><t>Commands</name> <t> EPP <xreftarget="RFC5730"/>target="RFC5730" format="default"/> provides three commands to retrieve object information: <check> to determine if an object is known to the server, <info> to retrieve detailed information associated with an object, and <transfer> to retrieve object transfer status information.</t> <t> This extension does not add any elements to EPP <check> and <transfer> commands or responses.</t> <sectiontitle="EPPanchor="sect-4.1.1" numbered="true" toc="default"> <name>EPP <info>Command" anchor="sect-4.1.1"><t>Command</name> <t> EPP provides the <info> command that is used to retrieve registry maintenance information. In addition to the standard EPP command elements, the <info> commandMUST<bcp14>MUST</bcp14> contain a <maint:info> element that identifies the maintenance namespace.</t> <t> The <maint:info> elementMUST<bcp14>MUST</bcp14> contain a child element. It is either the <maint:id> child element, described in <xreftarget="sect-4.1.1.1"/>,target="sect-4.1.1.1" format="default"/>, to query for a specific maintenance item or the <maint:list> child element, described in <xreftarget="sect-4.1.1.2"/>,target="sect-4.1.1.2" format="default"/>, to query all maintenance items.</t> <sectiontitle="Infoanchor="sect-4.1.1.1" numbered="true" toc="default"> <name>Info MaintenanceItem" anchor="sect-4.1.1.1"><t>Item</name> <t> The information regarding a specific maintenance item can be retrieved by using the <info> command with the <maint:info> element and the <maint:id> child element, defined in <xreftarget="sect-3.3"/>.target="sect-3.3" format="default"/>. If the maintenance identifier does not exist, the serverMUST<bcp14>MUST</bcp14> return an EPP error result code of 2303 ("Object does not exist") <xreftarget="RFC5730"/>.</t>target="RFC5730" format="default"/>.</t> <t>Example to retrieveThe following is an example of retrieving a specific maintenance item in an <info> command.</t><figure><artwork><![CDATA[<sourcecode><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <info> C: <maint:info C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0"> C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> C: </maint:info> C: </info> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>]]></artwork> </figure>]]></sourcecode> <t> When an <info> command has been processed successfully, the EPP <resData> elementMUST<bcp14>MUST</bcp14> contain a child <maint:infData> element that identifies the maintenance namespace. The <maint:infData> element contains the <maint:item> element defined in <xreftarget="sect-3.3"/>.</t>target="sect-3.3" format="default"/>.</t> <t>ExampleThe following is an example of returning a specific maintenance item in an <info> response.</t><figure><artwork><![CDATA[<sourcecode><![CDATA[ S:<?xml version="1.0" encoding="UTF-8"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <resData> S: <maint:infData S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0"> S: <maint:item> S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: </maint:id> S: <maint:type lang="en">Routine Maintenance</maint:type> S: <maint:systems> S: <maint:system> S: <maint:name>EPP</maint:name> S: <maint:host>epp.registry.example S: </maint:host> S: <maint:impact>full</maint:impact> S: </maint:system> S: </maint:systems> S: <maint:environment type="production"/> S: <maint:start>2021-12-30T06:00:00Z</maint:start> S: <maint:end>2021-12-30T07:00:00Z</maint:end> S: <maint:reason>planned</maint:reason> S: <maint:detail> S: https://www.registry.example/notice?123 S: </maint:detail> S: <maint:description lang="en">free-text S: </maint:description> S: <maint:description lang="de">Freitext S: </maint:description> S: <maint:tlds> S: <maint:tld>example</maint:tld> S: <maint:tld>test</maint:tld> S: </maint:tlds> S: <maint:intervention> S: <maint:connection>false</maint:connection> S: <maint:implementation>false</maint:implementation> S: </maint:intervention> S: <maint:crDate>2021-11-08T22:10:00Z</maint:crDate> S: </maint:item> S: </maint:infData> S: </resData> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S:</epp>]]></artwork> </figure>]]></sourcecode> </section> <sectiontitle="Infoanchor="sect-4.1.1.2" numbered="true" toc="default"> <name>Info MaintenanceList" anchor="sect-4.1.1.2"><t>List</name> <t> The information for a list of maintenance items can be retrieved by using the <info> command with the <maint:info> element and the empty <maint:list> child element. Server policy determines if completed maintenance events will be included in the list of maintenance items.</t> <t>Example to retrieveThe following is an example of retrieving the list of maintenance items in an <info> command.</t><figure><artwork><![CDATA[<sourcecode><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <info> C: <maint:info C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0"> C: <maint:list/> C: </maint:info> C: </info> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>]]></artwork> </figure>]]></sourcecode> <t> When an <info> command has been processed successfully, the EPP <resData> elementMUST<bcp14>MUST</bcp14> contain a child <maint:infData> element that identifies the maintenance namespace. The <maint:infData> element contains the <maint:list> element with zero or more <maint:listItem> child elements. The <maint:listItem> element contains the following child elements:</t><t><list style="empty" hangIndent="3"> <t><list style="hanging" hangIndent="3"><t hangText="<maint:id>"> <vspace blankLines="0"/><ul empty="true" spacing="normal"> <li> <dl newline="true" spacing="normal" indent="3"> <dt><maint:id></dt> <dd> The <maint:id> element defined in <xreftarget="sect-3.3"/>. </t> <t hangText="<maint:start>"> <vspace blankLines="0"/>target="sect-3.3" format="default"/>. </dd> <dt><maint:start></dt> <dd> The <maint:start> element defined in <xreftarget="sect-3.3"/>. </t> <t hangText="<maint:end>"> <vspace blankLines="0"/>target="sect-3.3" format="default"/>. </dd> <dt><maint:end></dt> <dd> The <maint:end> element defined in <xreftarget="sect-3.3"/>. </t> <t hangText="<maint:crDate>"> <vspace blankLines="0"/>target="sect-3.3" format="default"/>. </dd> <dt><maint:crDate></dt> <dd> The <maint:crDate> element defined in <xreftarget="sect-3.3"/>. </t> <t hangText="<maint:upDate>"> <vspace blankLines="0"/>target="sect-3.3" format="default"/>. </dd> <dt><maint:upDate></dt> <dd> TheOPTIONAL<bcp14>OPTIONAL</bcp14> <maint:upDate> element defined in <xreftarget="sect-3.3"/>. </t> </list> </t> </list> </t>target="sect-3.3" format="default"/>. </dd> </dl> </li> </ul> <t>ExampleThe following is an example of returning the list of maintenance items in an <info> response.</t><figure><artwork><![CDATA[<sourcecode><![CDATA[ S:<?xml version="1.0" encoding="UTF-8"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <resData> S: <maint:infData S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0"> S: <maint:list> S: <maint:listItem> S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: </maint:id> S: <maint:start>2021-12-30T06:00:00Z</maint:start> S: <maint:end>2021-12-30T07:00:00Z</maint:end> S: <maint:crDate>2021-11-08T22:10:00Z</maint:crDate> S: </maint:listItem> S: <maint:listItem> S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f S: </maint:id> S: <maint:start>2021-12-15T04:30:00Z</maint:start> S: <maint:end>2021-12-15T05:30:00Z</maint:end> S: <maint:crDate>2021-11-08T22:11:00Z</maint:crDate> S: <maint:upDate>2021-11-17T15:00:00Z</maint:upDate> S: </maint:listItem> S: </maint:list> S: </maint:infData> S: </resData> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S:</epp>]]></artwork> </figure>]]></sourcecode> </section> </section> <sectiontitle="EPPanchor="sect-4.1.2" numbered="true" toc="default"> <name>EPP <poll>Command" anchor="sect-4.1.2"><t>Command</name> <t> The EPP <poll> command and response are defined inSection 2.9.2.3 of<xreftarget="RFC5730"/>.target="RFC5730" sectionFormat="of" section="2.9.2.3" format="default"/>. The Registry Maintenance Notification is included in the EPP <poll> responseofin <xreftarget="RFC5730"/>.</t>target="RFC5730" format="default"/>.</t> <t> There are five types of poll messages for the Registry Maintenance Notification, defined by the <maint:pollType> element in <xreftarget="sect-3.3"/>.target="sect-3.3" format="default"/>. A poll message might be generated when a maintenance event is created, updated, or deleted. A courtesy poll message can be sent as a reminder of an upcoming maintenance event. An end poll message can be sent when the maintenance event is completed. In the case of aRegistry Maintenancemessage specificmessage,to Registry Maintenance, a <maint:infData>element,element that identifies the maintenance namespace will be included within the <resData> element of the standard <poll> response. The <maint:infData> element contains the <maint:item> element defined in <xreftarget="sect-3.3"/>.</t>target="sect-3.3" format="default"/>.</t> <t>ExampleThe following is an example of a <poll> command:</t><figure><artwork><![CDATA[<sourcecode><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <poll op="req"/> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp> ]]></sourcecode> <t> Example<poll><poll> response: </t> <sourcecode><![CDATA[ S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1301"> S: <msg>Command completed successfully; ack to dequeue</msg> S: </result> S: <msgQ count="1" id="12345"> S: <qDate>2021-11-08T22:10:00Z</qDate> S: <msg lang="en">Registry Maintenance Notification</msg> S: </msgQ> S: <resData> S: <maint:infData S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0"> S: <maint:item> S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> S: <maint:pollType>create</maint:pollType> S: <maint:systems> S: <maint:system> S: <maint:name>EPP</maint:name> S: <maint:host>epp.registry.example S: </maint:host> S: <maint:impact>full</maint:impact> S: </maint:system> S: </maint:systems> S: <maint:environment type="production"/> S: <maint:start>2021-12-30T06:00:00Z</maint:start> S: <maint:end>2021-12-30T07:00:00Z</maint:end> S: <maint:reason>planned</maint:reason> S: <maint:detail> S: https://www.registry.example/notice?123 S: </maint:detail> S: <maint:tlds> S: <maint:tld>example</maint:tld> S: <maint:tld>test</maint:tld> S: </maint:tlds> S: <maint:intervention> S: <maint:connection>false</maint:connection> S: <maint:implementation>false</maint:implementation> S: </maint:intervention> S: <maint:crDate>2021-11-08T22:10:00Z</maint:crDate> S: </maint:item> S: </maint:infData> S: </resData> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S:</epp>]]></artwork> </figure>]]></sourcecode> </section> </section> <sectiontitle="EPPanchor="sect-4.2" numbered="true" toc="default"> <name>EPP TransformCommands" anchor="sect-4.2"><t>Commands</name> <t> EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object.</t> <t> This extension does not add any elements to the EPP <create>, <delete>, <renew>, <transfer>, and<update>.</t><update> commands.</t> </section> </section> <sectiontitle="Formal Syntax" anchor="sect-5"><t>anchor="sect-5" numbered="true" toc="default"> <name>Formal Syntax</name> <t> The EPP Registry Maintenance Notification schema is presented here.</t> <t>The formal syntaxpresented hereis a complete schema representation of the object mapping suitable for automated validation of EPP XML 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 schema for URI registration purposes.</t> <sectiontitle="Registryanchor="sect-5.1" numbered="true" toc="default"> <name>Registry Maintenance Notification EPP MappingSchema" anchor="sect-5.1"><figure><artwork><![CDATA[ <CODE BEGINS>Schema</name> <sourcecode type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="urn:ietf:params:xml:ns:epp: maintenance-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0" xmlns="https://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types --> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0"/> <annotation> <documentation> Extensible Provisioning Protocol v1.0 Registry Maintenance Notification Mapping Schema. </documentation> </annotation> <!-- Child elements found in EPP commands. --> <element name="info" type="maint:infoType"/> <!-- Child elements of the <info> command. --> <complexType name="infoType"> <sequence> <choice> <element name="list"/> <element name="id" type="maint:idType"/> </choice> </sequence> </complexType> <!-- Human-readable text may describe the maintenance --> <complexType name="idType"> <simpleContent> <extension base="token"> <attribute name="name" type="token"/> <attribute name="lang" type="language" default="en"/> </extension> </simpleContent> </complexType> <!-- Info Response element --> <element name="infData" type="maint:infDataType"/> <!-- <info> response elements. --> <complexType name="infDataType"> <choice> <element name="list" type="maint:listDataType"/> <element name="item" type="maint:maintDataType"/> </choice> </complexType> <!-- Attributes associated with the list info response --> <complexType name="listDataType"> <sequence> <element name="listItem" type="maint:maintItemType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> <!-- Attributes associated with the list item info response --> <complexType name="maintItemType"> <sequence> <element name="id" type="maint:idType"/> <element name="start" type="dateTime"/> <element name="end" type="dateTime"/> <element name="crDate" type="dateTime"/> <element name="upDate" type="dateTime" minOccurs="0"/> </sequence> </complexType> <!-- Attributes associated with the maintenance info response --> <complexType name="maintDataType"> <sequence> <element name="id" type="maint:idType"/> <element name="type" type="maint:typeType" minOccurs="0" maxOccurs="unbounded"/> <element name="pollType" type="maint:pollType" minOccurs="0"/> <element name="systems" type="maint:systemsType"/> <element name="environment" type="maint:envType"/> <element name="start" type="dateTime"/> <element name="end" type="dateTime"/> <element name="reason" type="maint:reasonEnum"/> <element name="detail" type="anyURI" minOccurs="0"/> <element name="description" type="maint:descriptionType" minOccurs="0" maxOccurs="unbounded"/> <element name="tlds" type="maint:tldsType" minOccurs="0"/> <element name="intervention" type="maint:interventionType" minOccurs="0"/> <element name="crDate" type="dateTime"/> <element name="upDate" type="dateTime" minOccurs="0"/> </sequence> </complexType> <!-- systems element --> <complexType name="systemsType"> <sequence> <element name="system" type="maint:systemType" maxOccurs="unbounded"/> </sequence> </complexType> <!-- Enumerated list of poll types --> <simpleType name="pollType"> <restriction base="token"> <enumeration value="create"/> <enumeration value="update"/> <enumeration value="delete"/> <enumeration value="courtesy"/> <enumeration value="end"/> </restriction> </simpleType> <!-- Enumerated list of impacts --> <simpleType name="impactEnum"> <restriction base="token"> <enumeration value="none"/> <enumeration value="partial"/> <enumeration value="full"/> </restriction> </simpleType> <!-- description element --> <complexType name="descriptionType"> <simpleContent> <extension base="string"> <attribute name="lang" type="language" default="en"/> <attribute name="type" type="maint:descEnum" default="plain" /> </extension> </simpleContent> </complexType> <!-- Enumerated list of description mime types --> <simpleType name="descEnum"> <restriction base="token"> <enumeration value="plain"/> <enumeration value="html"/> </restriction> </simpleType> <!-- type element --> <complexType name="typeType"> <simpleContent> <extension base="string"> <attribute name="lang" type="language" default="en"/> </extension> </simpleContent> </complexType> <!-- system element --> <complexType name="systemType"> <sequence> <element name="name" type="token"/> <element name="host" type="eppcom:labelType" minOccurs="0"/> <element name="impact" type="maint:impactEnum"/> </sequence> </complexType> <!-- Enumerated list of environments --> <simpleType name="envEnum"> <restriction base="token"> <enumeration value="production"/> <enumeration value="ote"/> <enumeration value="staging"/> <enumeration value="dev"/> <enumeration value="custom"/> </restriction> </simpleType> <!-- environment element --> <complexType name="envType"> <simpleContent> <extension base="token"> <attribute name="type" type="maint:envEnum" use="required"/> <attribute name="name" type="token" use="optional"/> </extension> </simpleContent> </complexType> <!-- Enumerated list of reasons --> <simpleType name="reasonEnum"> <restriction base="token"> <enumeration value="planned"/> <enumeration value="emergency"/> </restriction> </simpleType> <!-- tlds element --> <complexType name="tldsType"> <sequence> <element name="tld" type="eppcom:labelType" maxOccurs="unbounded"/> </sequence> </complexType> <!-- intervention element --> <complexType name="interventionType"> <sequence> <element name="connection" type="boolean"/> <element name="implementation" type="boolean"/> </sequence> </complexType> <!-- End of schema. --> </schema><CODE ENDS> ]]></artwork> </figure>]]></sourcecode> </section> </section> <sectiontitle="IANA Considerations" anchor="sect-6"><section title="XML Namespace" anchor="sect-6.1"><t>anchor="sect-6" numbered="true" toc="default"> <name>IANA Considerations</name> <section anchor="sect-6.1" numbered="true" toc="default"> <name>XML Namespace</name> <t> This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism defined in <xreftarget="RFC3688"/>.</t> <t>Registration request for the maintenancetarget="RFC3688" format="default"/>.</t> <t>The following entry has been registered as an XML namespace:<list> <t>URI: urn:ietf:params:xml:ns:epp:maintenance-1.0</t> <t>Registrant</t> <dl spacing="compact"> <dt>URI: </dt> <dd>urn:ietf:params:xml:ns:epp:maintenance-1.0 </dd> <dt>Registrant Contact:IESG</t> <t> XML: None.</dt> <dd>IESG </dd> <dt>XML: </dt> <dd>None. Namespace URIs do not represent an XMLspecification.</t> </list> </t> <t>Registration request forspecification. </dd> </dl> <t>The following entry has been registered to the XML maintenance schema:<list> <t>URI: urn:ietf:params:xml:schema:epp:maintenance-1.0</t> <t>Registrant</t> <dl spacing="compact"> <dt>URI: </dt> <dd>urn:ietf:params:xml:schema:epp:maintenance-1.0 </dd> <dt>Registrant Contact:IESG</t> <t>XML: See</dt> <dd>IESG </dd> <dt>XML: </dt> <dd>See the"Formal Syntax"<xref target="sect-5" format="none">"Formal Syntax"</xref> section of thisdocument.</t> </list> </t>document. </dd> </dl> </section> <sectiontitle="EPPanchor="sect-6.2" numbered="true" toc="default"> <name>EPP ExtensionRegistry" anchor="sect-6.2"><t>Registry</name> <t> The followingregistration ofentry has been added to theEPP Extension Registry,"Extensions for the Extensible Provisioning Protocol (EPP)" registry, described in <xreftarget="RFC7451"/>, is requested:</t> <t> Nametarget="RFC7451" format="default"/>:</t> <dl spacing="compact"> <dt>Name of Extension:Registry</dt> <dd>Registry Maintenance Notification for the Extensible Provisioning Protocol(EPP)</t> <t> Document(EPP) </dd> <dt>Document status:Standards Track</t> <t> Reference: (insert the reference to RFC version of this document)</t> <t> Registrant</dt> <dd>Standards Track </dd> <dt>Reference: </dt> <dd>RFC 9167 </dd> <dt>Registrant Name and Email Address:IESG <iesg@ietf.org></t> <t> TLDs: Any</t> <t> IPR</dt> <dd>IESG <iesg@ietf.org> </dd> <dt>TLDs: </dt> <dd>Any </dd> <dt>IPR Disclosure:None</t> <t> Status: Active</t> <t> Notes: None</t></dt> <dd>None </dd> <dt>Status: </dt> <dd>Active </dd> <dt>Notes: </dt> <dd>None </dd> </dl> </section> </section> <sectiontitle="Security Considerations" anchor="sect-7"><t>anchor="sect-7" numbered="true" toc="default"> <name>Security Considerations</name> <t> The security considerations of <xreftarget="RFC5730"/>target="RFC5730" format="default"/> apply in this document. Additionally, a serverMUST<bcp14>MUST</bcp14> only provide maintenance information to clients that are authorized. Suppose a client queries a maintenance identifier that it is not authorized to access per <xreftarget="sect-4.1.1.1"/>target="sect-4.1.1.1" format="default"/>, "Info Maintenance Item". In that case, the serverSHOULD<bcp14>SHOULD</bcp14> return an EPP error result code of 2201 ("Authorization error") or 2303 ("Object does not exist") <xreftarget="RFC5730"/>.target="RFC5730" format="default"/>. The list of top-level domains or registry zones returned in the "Info Maintenance Item" responseSHOULD<bcp14>SHOULD</bcp14> be filtered based on the top-level domains or registry zones for which the client is authorized. Authorization of poll messages is done at the time of poll message insertion and not at the time of poll message consumption.</t> </section><section title="Implementation Status" anchor="sect-8"><t> Note to RFC Editor: Please remove this section and the reference to <xref target="RFC7942"/> before publication.</t> <t> This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in <xref target="RFC7942"/>. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.</t> <t> According to <xref target="RFC7942"/>, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".</t> <section title="GoDaddy Registry" anchor="sect-8.1"><t> Organization: GoDaddy Registry</t> <t> Name: GoDaddy Registry</t> <t> Description: GoDaddy Registry provides maintenance notifications to their registrars.</t> <t> Level of maturity: Production</t> <t> Coverage: All aspects of the protocol according to the draft version 2 are implemented with further updates to come.</t> <t> Licensing: Proprietary</t> <t> Contact: quoc@registry.godaddy</t> <t> URL: <eref target="https://registry.godaddy"/> </t> </section> <section title="TANGO Registry Services" anchor="sect-8.2"><t> Name: TANGO Registry Services</t> <t> Description: TANGO Registry Services provides maintenance notifications to their registrars.</t> <t> Level of maturity: Beta</t> <t> Coverage: All aspects of the protocol according to the draft version 12 are implemented with further updates to come.</t> <t> Licensing: Proprietary</t> <t> Contact: Michael.Bauland@knipp.de</t> <t> URL: <eref target="https://tango-rs.com"/> </t> </section> </section></middle> <back><references title="Normative References"> &W3C.REC-html5-20141028; &W3C.REC-xml11-20060816; &RFC2119; &RFC3339; &RFC3986; &RFC5730; &RFC5891; &RFC7942; &RFC8174; &RFC9038;<references> <name>References</name> <references> <name>Normative References</name> <reference anchor="HTML5" target='https://html.spec.whatwg.org/multipage/'> <front> <title>HTML - Living Standard</title> <author> <organization>WHATWG</organization> </author> <date month='December' year='2021' /> </front> </reference> <reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2008/REC-xml-20081126" quoteTitle="true" derivedAnchor="W3C.REC-xml-20081126"> <front> <title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title> <author initials="T." surname="Bray" fullname="Tim Bray"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Paoli" fullname="Jean Paoli"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Sperberg-McQueen" fullname="Michael Sperberg-McQueen"> <organization showOnFrontPage="true"/> </author> <author initials="E." surname="Maler" fullname="Eve Maler"> <organization showOnFrontPage="true"/> </author> <author initials="F." surname="Yergeau" fullname="Francois Yergeau"> <organization showOnFrontPage="true"/> </author> <date month="November" year="2008"/> </front> <refcontent>World Wide Web Consortium Recommendation REC-xml-20081126</refcontent> </reference> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5730.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5891.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9038.xml"/> </references> <references> <name>Informative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7451.xml"/> </references><references title="Informative References"> &RFC3688; &RFC7451;</references> <sectiontitle="Change History" anchor="sect-a"><section title="Change from draft-sattler-epp-poll-maintenance-response to draft-sattler-epp-registry-maintenance" anchor="sect-a.1"><t> Updated to be EPP based instead of JSON document.</t> </section> <section title="Change from draft-sattler-epp-registry-maintenance to draft-ietf-regext-epp-registry-maintenance" anchor="sect-a.2"><t> Adopted by the REGEXT working group.</t> </section> <section title="Change from 00 to 01" anchor="sect-a.3"><t> Clarified maint:description and maint:environment. Changed maint:description from complexType to simpleType. Fixed typo. Added acknowledgment.</t> </section> <section title="Change from 01 to 02" anchor="sect-a.4"><t> Update language from Domain Name Registry to Registry. Clarified XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host to contain hostName and hostAddr. Changed maint:tlds from MUST to SHOULD. Fixed maint:status in Schema. Changed UUID to a server unique id.</t> </section> <section title="Change from 02 to 03" anchor="sect-a.5"><t> Changed maint:connection from MUST to SHOULD.</t> </section> <section title="Change from 03 to 04" anchor="sect-a.6"><t> A lot of clarifications and editorial changes.</t> </section> <section title="Change from 04 to 05" anchor="sect-a.7"><t> 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.</t> </section> <section title="Change from 05 to 06" anchor="sect-a.8"><t> Changed dates in examples to more recent dates. Renamed Query Maintenance Item and List to Info Maintenance Item and List. Removed blackout in favor of full. Added GoDaddy Registry implementation.</t> </section> <section title="Change from 06 to 07" anchor="sect-a.9"><t> Removed IP addresses for <maint:host>. Editorial changes.</t> </section> <section title="Change from 07 to 08" anchor="sect-a.10"><t> Editorial changes. Changed XML namespace and schema from 0.1 to 0.2. Added pollType to reflect create, update, or delete maintenance poll messages.</t> </section> <section title="Change from 08 to 09" anchor="sect-a.11"><t> Editorial changes. Added new section "Migrating to Newer Versions of This Extension".</t> </section> <section title="Change from 09 to 10" anchor="sect-a.12"><t> Editorial changes. Renamed "msg" to "name". Added "courtesy" and "end" to pollType.</t> </section> <section title="Change from 10 to 11" anchor="sect-a.13"><t> Editorial changes. Added mime type to description.</t> </section> <section title="Change from 11 to 12" anchor="sect-a.14"><t> Editorial changes. Changed XML namespace from 0.2 to 0.3.</t> </section> <section title="Change from 12 to 13" anchor="sect-a.15"><t> Editorial changes. Added TANGO Registry Services to <xref target="sect-8"/>. Added Michael Bauland to acknowledgments. Added "none" to <maint:impact>.</t> </section> <section title="Change from 13 to 14" anchor="sect-a.16"><t> Accepted in WGLC. Changed XML namespace from 0.3 to 1.0.</t> </section> <section title="Change from 14 to 15" anchor="sect-a.17"><t> Editorial changes, added feedback from the document shepherd.</t> </section> <section title="Change from 15 to 16" anchor="sect-a.18"><t> Editorial changes, added feedback from area director.</t> </section> <section title="Change from 16 to 17" anchor="sect-a.19"><t> Editorial changes, added last call feedback. Changed schema URI to urn:ietf:params:xml:schema:epp:maintenance-1.0. Changed dates in examples to more recent dates.</t> </section> <section title="Change from 17 to 18" anchor="sect-a.20"><t> Editorial changes.</t> </section> <section title="Change from 18 to 19" anchor="sect-a.21"><t> Editorial changes.</t> </section> </section> <section title="Acknowledgments" numbered="no" anchor="acknowledgments"><t>numbered="false" anchor="acknowledgments" toc="default"> <name>Acknowledgments</name> <t> The authors wish to thank the following persons for their feedback and suggestions:James Gould, Michael Bauland, Patrick Mevzek, Quoc-Anh Pham, Raymond Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig Marchant, and Andreas Huber.</t><contact fullname="James Gould"/>, <contact fullname="Michael Bauland"/>, <contact fullname="Patrick Mevzek"/>, <contact fullname="Quoc-Anh Pham"/>, <contact fullname="Raymond Zylstra"/>, <contact fullname="Christopher Martens"/>, <contact fullname="Anthony Eden"/>, <contact fullname="Neal McPherson"/>, <contact fullname="Craig Marchant"/>, and <contact fullname="Andreas Huber"/>.</t> </section> </back> </rfc>