Diff: rfc9167xml2.original.xml

	rfc9167xml2.original.xml	rfc9167.xml

	<?xml version='1.0' encoding='utf-8'?>	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
	<!ENTITY W3C.REC-html5-20141028 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibx
	ml4/reference.W3C.REC-html5-20141028.xml">
	<!ENTITY W3C.REC-xml11-20060816 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibx
	ml4/reference.W3C.REC-xml11-20060816.xml">
	<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.2119.xml">
	<!ENTITY RFC3339 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.3339.xml">
	<!ENTITY RFC3986 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.3986.xml">
	<!ENTITY RFC5730 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.5730.xml">
	<!ENTITY RFC5891 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.5891.xml">
	<!ENTITY RFC7942 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.7942.xml">
	<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.8174.xml">
	<!ENTITY RFC9038 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.9038.xml">
	<!ENTITY RFC3688 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.3688.xml">
	<!ENTITY RFC7451 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
	C.7451.xml">
	]>
	<rfc submissionType="IETF" docName="draft-ietf-regext-epp-registry-maintenance-1
	9" 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"?>
	<front>
	<title abbrev="Registry Maintenance Notification for th">Registry Mainten
	ance Notification for the Extensible Provisioning Protocol (EPP)</title>
	<author initials="T." surname="Sattler" fullname="Tobias Sattler">
	<organization></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>
	<region>AZ</region>
	<code>85260</code>
	<country>USA</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>
	<region>AZ</region>
	<code>85260</code>
	<country>USA</country>
	</postal>
	<email>jkolker@godaddy.com</email>
	<uri>https://www.godaddy.com</uri>
	</address>
	</author>


	<date year="2021" month="October"/>	<!DOCTYPE rfc [
		<!ENTITY nbsp " ">
		<!ENTITY zwsp "">
		<!ENTITY nbhy "‑">
		<!ENTITY wj "⁠">
		]>


	<!-- [rfced] Please insert any keywords (beyond those that appear in	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="
	the title) for use on https://www.rfc-editor.org/search. -->	std" consensus="true" docName="draft-ietf-regext-epp-registry-maintenance-19" nu
		mber="9167" ipr="trust200902" obsoletes="" updates="" xml:lang="en" symRefs="tru
		e" sortRefs="true" tocInclude="true" version="3">


	<keyword>example</keyword>	<front>
		<title abbrev="EPP Registry Maintenance">Registry Maintenance Notification f
		or the Extensible Provisioning Protocol (EPP)</title>
		<seriesInfo name="RFC" value="9167"/>
		<author initials="T." surname="Sattler" fullname="Tobias Sattler">
		<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>2155 E GoDaddy Way</street>
		<city>Tempe</city>
		<region>AZ</region>
		<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>2155 E GoDaddy Way
		</street>
		<city>Tempe</city>
		<region>AZ</region>
		<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="December"/>


	<abstract><t>	<abstract>
		<t>
	This document describes an Extensible Provisioning Protocol (EPP)	This document describes an Extensible Provisioning Protocol (EPP)

	extension called "Registry Maintenance Notification", used by EPP	extension called "Registry Maintenance Notification", which is used by EPP
	servers to notify EPP clients and allow EPP clients to query EPP	servers to notify EPP clients and allow EPP clients to query EPP
	servers regarding maintenance events.</t>	servers regarding maintenance events.</t>

		</abstract>
	</abstract>	</front>
	</front>	<middle>
		<section anchor="sect-1" numbered="true" toc="default">
	<middle>	<name>Introduction</name>
	<section title="Introduction" anchor="sect-1"><t>	<t>
	The Extensible Provisioning Protocol (EPP), as defined in <xref target="RFC57	The Extensible Provisioning Protocol (EPP), as defined in <xref target="RFC57
	30"/>,	30" format="default"/>,
	is a protocol whose original motivation is to provide a standard	is a protocol whose original motivation is to provide a standard
	Internet domain name registration protocol for use between registries	Internet domain name registration protocol for use between registries
	and registrars.</t>	and registrars.</t>

		<t>
	<t>
	Registries routinely update systems to ensure a higher quality of	Registries routinely update systems to ensure a higher quality of
	service, implement new services, or upgrade protocols to the latest	service, implement new services, or upgrade protocols to the latest
	standards. These updates are pushed to various registry environments	standards. These updates are pushed to various registry environments
	during time frames communicated to registrars as "maintenance events". Mainte nance events may require making services unavailable	during time frames communicated to registrars as "maintenance events". Mainte nance events may require making services unavailable
	for some limited time while the upgrade happens. Registries usually	for some limited time while the upgrade happens. Registries usually
	inform registrars about maintenance events in various formats, none	inform registrars about maintenance events in various formats, none
	of which are standardized between registries.</t>	of which are standardized between registries.</t>

		<t>
	<t>
	The DNS namespace expansion has led to many additional registries	The DNS namespace expansion has led to many additional registries
	that registrars must interact with, adding more maintenance events	that registrars must interact with, adding more maintenance events
	and formats. It is now desirable to provide an efficient approach to	and formats. It is now desirable to provide an efficient approach to
	notify registrars.</t>	notify registrars.</t>

		<t>
	<t>
	This document describes an extension mapping for version 1.0 of the	This document describes an extension mapping for version 1.0 of the
	EPP to provide a mechanism by which EPP servers may notify EPP	EPP to provide a mechanism by which EPP servers may notify EPP
	clients of and allow EPP clients to query EPP servers on upcoming	clients of and allow EPP clients to query EPP servers on upcoming
	maintenance events.</t>	maintenance events.</t>

		<section anchor="sect-1.1" numbered="true" toc="default">
		<name>Terminology and Definitions</name>


	<section title="Terminology and Definitions" anchor="sect-1.1"><t>	<t>
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",	The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and	IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
	"OPTIONAL" in this document are to be interpreted as described in	NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
	BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when,	RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
	they appear in all	"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
	capitals, as shown here.</t>	be interpreted as
		described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/>
		when, and only when, they appear in all capitals, as shown here.
		</t>


	<t>	<t>
	XML <xref target="W3C.REC-xml11-20060816"/> is case-sensitive. Unless stated	XML <xref target="W3C.REC-xml-20081126" format="default"/> is case sensitive.
	otherwise, XML specification and examples provided in this document	Unless stated
	MUST be interpreted in the character case presented in order to	otherwise, XML specifications and examples provided in this document
		<bcp14>MUST</bcp14> be interpreted in the character case presented in order t
		o
	develop a conforming implementation.</t>	develop a conforming implementation.</t>

		<t>
	<t>	The XML namespace prefix "maint" is used for the namespace
	"maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: maintenan	"urn:ietf:params:xml:ns:epp:maintenance-1.0", but implementations
	ce-1.0". The XML namespace prefix "maint" is used, but	<bcp14>MUST NOT</bcp14> depend on it and instead employ a proper
	implementations MUST NOT depend on it. Instead, they are to employ a	namespace-aware XML parser and serializer to interpret and output the
	proper namespace-aware XML parser and serializer to interpret and	XML documents.
	output the XML documents.</t>	</t>
		<t>
	<t>
	"ote" is an abbreviation for "Operational Test and Evaluation".</t>	"ote" is an abbreviation for "Operational Test and Evaluation".</t>

		<t>
	<t>	In examples, "C:" represents lines sent by a protocol client, and "S:"
	In examples, "C:" represents lines sent by a protocol client, and	represents lines returned by a protocol server. Indentation and white space
	"S:" represents lines returned by a protocol server. Indentation and	in examples are provided only to illustrate element relationships and are
	white space in examples are provided only to illustrate element	not a required feature of this protocol.</t>
	relationships and are not a required feature of this protocol.</t>	</section>
		</section>
	</section>	<section anchor="sect-2" numbered="true" toc="default">
		<name>Migrating to Newer Versions of This Extension</name>
	</section>	<t>
		Servers that implement this extension <bcp14>SHOULD</bcp14> provide a way for
	<section title="Migrating to Newer Versions of This Extension" anchor="se
	ct-2"><t>
	Servers that implement this extension SHOULD provide a way for
	clients to progressively update their implementations when a new	clients to progressively update their implementations when a new
	version of the extension is deployed. A newer version of the	version of the extension is deployed. A newer version of the
	extension is expected to use an XML namespace with a higher version	extension is expected to use an XML namespace with a higher version
	number than the prior versions.</t>	number than the prior versions.</t>

		<t>
	<t>	Servers <bcp14>SHOULD</bcp14> (for a temporary migration period up to server
	Servers SHOULD (for a temporary migration period up to server policy)	policy)
	provide support for older versions of the extension in parallel to	provide support for older versions of the extension in parallel to
	the newest version and allow clients to execute their preferred	the newest version and allow clients to execute their preferred
	version of the <info> command based on the maintenance <objURI>	version of the <info> command based on the maintenance <objURI>
	elements of the server <greeting>. The version of the maintenance	elements of the server <greeting>. The version of the maintenance

	<info> response MUST match the version of the maintenance <info>	<info> response <bcp14>MUST</bcp14> match the version of the maintenanc e <info>
	command executed by the server.</t>	command executed by the server.</t>

		<t>
	<t>	Servers <bcp14>MUST</bcp14> return a Registry Maintenance Notification poll
	Servers MUST return a Registry Maintenance Notification poll message	message matching the newest negotiated version of the maintenance
	matching the newest negotiated version of the maintenance extension,	extension, based on an intersection of the maintenance <objURI>
	based on an intersection of the maintenance <objURI> elements in the	elements in the server <greeting> and the client <login>
	server <greeting> and the client <login> command. If the intersec	command. If the intersection of the maintenance <objURI> elements of
	tion	the server <greeting> and the client <login> command results in
	of the maintenance <objURI> elements of the server <greeting> and	an empty set, the server <bcp14>MUST</bcp14> return the newest version of
	the	the Registry Maintenance Notification poll message supported by the server
	client <login> command results in an empty set, the server MUST	based on "Usage with Poll-Message EPP Responses" in <xref target="RFC9038"
	return the newest version of the Registry Maintenance Notification	sectionFormat="of" section="6" format="default"/>.</t>
	poll message supported by the server based on "Usage with Poll-Message EPP Re	</section>
	sponses" in Section 6 of <xref target="RFC9038"/>.</t>	<section anchor="sect-3" numbered="true" toc="default">
		<name>Object Attributes</name>
	</section>	<section anchor="sect-3.1" numbered="true" toc="default">
		<name>Internationalized Domain Names</name>
	<section title="Object Attributes" anchor="sect-3"><section title="Intern	<t>
	ationalized Domain Names" anchor="sect-3.1"><t>	Names of affected hosts <bcp14>MUST</bcp14> be provided in A-label form, acco
	Names of affected hosts MUST be provided in A-label form, according	rding
	to <xref target="RFC5891"/>.</t>	to <xref target="RFC5891" format="default"/>.</t>
		</section>
	</section>	<section anchor="sect-3.2" numbered="true" toc="default">
		<name>Dates and Times</name>
	<section title="Dates and Times" anchor="sect-3.2"><t>	<t>
	All date and time attribute values MUST be expressed in Universal	All date and time attribute values <bcp14>MUST</bcp14> be expressed in Univer
		sal
	Coordinated Time (UTC) using the Gregorian calendar. The date-time	Coordinated Time (UTC) using the Gregorian calendar. The date-time

	format defined as "date-time" in <xref target="RFC3339"/>, with time-offset="	format defined as "date-time" in <xref target="RFC3339" format="default"/>, w
	Z",	ith time-offset="Z",
	MUST be used.</t>	<bcp14>MUST</bcp14> be used.</t>
		</section>
	</section>	<section anchor="sect-3.3" numbered="true" toc="default">
		<name>Maintenance Elements</name>
	<section title="Maintenance Elements" anchor="sect-3.3"><t>	<t>
	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> command and response, and <poll> response.</t>	item EPP <info> command and response as well as in a <poll> respo
		nse.</t>
	<t>	<t>
	If an element is not marked as optional, it is mandatory.</t>	If an element is not marked as optional, it is mandatory.</t>

		<dl newline="true" spacing="normal" indent="3">
		<dt><maint:id></dt>
		<dd>


	<t><list style="hanging" hangIndent="3"><t hangText="<maint:id>">	The server-unique identifier for the maintenance event with the
	<vspace blankLines="0"/>	<bcp14>OPTIONAL</bcp14> "name" attribute that includes a
	The server unique identifier for the maintenance event with the	human-readable name of the event. The server-unique identifier
	OPTIONAL "name" attribute that includes a human-readable name of	<bcp14>SHALL NOT</bcp14> be changed if the event is updated or
	the event. The server unique identifier SHALL NOT be changed if	deleted. When the "name" attribute is set, the
	the event is updated or deleted. When the "name" attribute is set,	<bcp14>OPTIONAL</bcp14> "lang" attribute, per the language structure
	the OPTIONAL "lang" attribute MAY be present to identify the	in <xref target="RFC5646"/>, <bcp14>MAY</bcp14> be present to
	language if the negotiated value is something other than the	identify the language if the negotiated value is something other
	default value of "en" (English).	than the default value of "en" (English).
	</t>


	<t hangText="<maint:type>">	</dd>
	<vspace blankLines="0"/>	<dt><maint:type></dt>
	Zero or more OPTIONAL types of the maintenance event, with the	<dd>
		Zero or more <bcp14>OPTIONAL</bcp14> types of the maintenance event, with
		the
	possible set of values defined by server policy, such as	possible set of values defined by server policy, such as
	"Routine Maintenance", "Software Update", "Software Upgrade", or	"Routine Maintenance", "Software Update", "Software Upgrade", or

	"Extended Outage". The OPTIONAL "lang" attribute MAY be present to	"Extended Outage". The <bcp14>OPTIONAL</bcp14> "lang" attribute <bcp14>MAY </bcp14> be present to
	identify the language if the negotiated value is something other	identify the language if the negotiated value is something other
	than the default value of "en" (English).	than the default value of "en" (English).

	</t>	</dd>
		<dt><maint:pollType></dt>
	<t hangText="<maint:pollType>">	<dd>
	<vspace blankLines="0"/>	The <bcp14>OPTIONAL</bcp14> <maint:pollType> element for a Registry
	The OPTIONAL <maint:pollType> element for a Registry Maintenance	Maintenance
	Notification poll message; values MUST either be "create",	Notification poll message; values <bcp14>MUST</bcp14> be "create",
	"update", "delete", "courtesy", or "end". For the "create" and	"update", "delete", "courtesy", or "end". For the "create" and
	"update" types, the server includes the state of the maintenance	"update" types, the server includes the state of the maintenance
	event after the creation or update. For the "delete" type, the	event after the creation or update. For the "delete" type, the
	server includes the state of the event before the delete. The	server includes the state of the event before the delete. The
	"courtesy" provides a reminder of an event, and the "end" provides	"courtesy" provides a reminder of an event, and the "end" provides
	a notification of the end of the event without updating the	a notification of the end of the event without updating the
	maintenance object and includes the latest state of the event.	maintenance object and includes the latest state of the event.

	This element MUST be present only for poll messages.	This element <bcp14>MUST</bcp14> be present only for poll messages.
	</t>	</dd>
		<dt><maint:systems></dt>
	<t hangText="<maint:systems>">	<dd>
	<vspace blankLines="0"/>	<t>
	One or more <maint:system> elements that are affected by the	One or more <maint:system> elements that are affected by the
	maintenance event.	maintenance event.


	<list style="hanging" hangIndent="3"><t hangText="<maint:system>">	</t>
	<vspace blankLines="0"/>	<dl newline="true" spacing="normal" indent="3">
		<dt><maint:system></dt>
		<dd>
		<t>
	The <maint:system> element contains the following child	The <maint:system> element contains the following child
	elements:	elements:


	<list style="hanging" hangIndent="3"><t hangText="<maint:name>">	</t>
	<vspace blankLines="0"/>	<dl newline="true" spacing="normal" indent="3">
		<dt><maint:name></dt>
		<dd>
	The name of the affected system, such as "EPP", "WHOIS",	The name of the affected system, such as "EPP", "WHOIS",
	"DNS", "Portal", "RDAP", etc.	"DNS", "Portal", "RDAP", etc.

	</t>	</dd>
		<dt><maint:host></dt>
	<t hangText="<maint:host>">	<dd>
	<vspace blankLines="0"/>	The <bcp14>OPTIONAL</bcp14> affected maintained system's hostname, whic
	The OPTIONAL affected maintained system's hostname, which	h
	SHALL be in A-label form, according to <xref target="RFC5891"/>.</t>	<bcp14>SHALL</bcp14> be in A-label form, according to <xref target="RFC
		5891" format="default"/>.</dd>
	<t hangText="<maint:impact>">	<dt><maint:impact></dt>
	<vspace blankLines="0"/>	<dd>
	The impact level; the values MUST either be "full",	The impact level; the values <bcp14>MUST</bcp14> be "full",
	"partial", or "none". If access is expected to be	"partial", or "none". If access is expected to be intermittently
	intermittently unavailable, it is "partial". If access is	unavailable, it is "partial". If access is expected to be completely
	expected to be completely unavailable, it is "full". If	unavailable, it is "full". If access is not affected, it is "none".
	access is not affected, it is "none".	</dd>
	</t>	</dl>
		</dd>
	</list>	</dl>
	</t>	</dd>
		</dl>
	</list>
	</t>

	</list>
	</t>

	<t><list style="hanging" hangIndent="3"><t hangText="<maint:environmen
	t>">
	<vspace blankLines="0"/>
	The type of the affected system; the attribute "type" is REQUIRED
	and MUST either be "production", "ote", "staging", "dev" or
	"custom". For extensibility, the <maint:environment> element
	includes the OPTIONAL "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>">	<dl newline="true" spacing="normal" indent="3">
	<vspace blankLines="0"/>	<dt><maint:environment></dt>
		<dd>
		The type of the affected system; the attribute "type" is
		<bcp14>REQUIRED</bcp14> and <bcp14>MUST</bcp14> be
		"production", "ote", "staging", "dev", or "custom". For extensibility,
		the <maint:environment> element includes the
		<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"/>.
		</dd>
		<dt><maint:start></dt>
		<dd>
	The date and time of the start of the maintenance event.	The date and time of the start of the maintenance event.

	</t>	</dd>
		<dt><maint:end></dt>
	<t hangText="<maint:end>">	<dd>
	<vspace blankLines="0"/>
	The date and time of the end of the maintenance event. The	The date and time of the end of the maintenance event. The

	<maint:end> element MUST be greater than the <maint:start>	<maint:end> element <bcp14>MUST</bcp14> be greater than the <main t:start>
	element.	element.

	</t>	</dd>
		<dt><maint:reason></dt>
	<t hangText="<maint:reason>">	<dd>
	<vspace blankLines="0"/>	The reason behind the maintenance event; the values <bcp14>MUST</bcp1
	The reason behind the maintenance event; the values MUST either be	4> be either
	"planned" or "emergency".	"planned" or "emergency".
	</t>	</dd>
		<dt><maint:detail></dt>
	<t hangText="<maint:detail>">	<dd>
	<vspace blankLines="0"/>	The <bcp14>OPTIONAL</bcp14> URI to the detailed maintenance event descrip
	The OPTIONAL URI to the detailed maintenance event description,	tion,
	formatted according to <xref target="RFC3986"/>.	formatted according to <xref target="RFC3986" format="default"/>.
	</t>	</dd>
		<dt><maint:description></dt>
	<t hangText="<maint:description>">	<dd>
	<vspace blankLines="0"/>	Zero or more <bcp14>OPTIONAL</bcp14> free-form descriptions of the mainte
	Zero or more OPTIONAL free-form descriptions of the maintenance	nance
	event, usable without creating and traversing an external resource	event, usable without creating and traversing an external resource

	as defined by the <maint:detail> element. The OPTIONAL "lang"	as defined by the <maint:detail> element. The <bcp14>OPTIONAL</bcp14
	attribute MAY be present to identify the language if the	> "lang"
		attribute <bcp14>MAY</bcp14> be present to identify the language if the
	negotiated value is something other than the default value of "en"	negotiated value is something other than the default value of "en"

	(English). The OPTIONAL "type" attribute MAY be present to	(English). The <bcp14>OPTIONAL</bcp14> "type" attribute <bcp14>MAY</bcp14>
	identify the format of the description. It MUST either be "plain"	be present to
	for plain text or "html" for HTML text that is defined in	identify the format of the description. It <bcp14>MUST</bcp14> be either "
	<xref target="W3C.REC-html5-20141028"/> and XML-escaped, with a default va	plain"
	lue of	for plain text or "html" for HTML text, as defined in
		<xref target="HTML5" format="default"/>, and XML-escaped, with a default v
		alue of
	"plain".	"plain".

	</t>	</dd>
		<dt><maint:tlds></dt>
	<t hangText="<maint:tlds>">	<dd>
	<vspace blankLines="0"/>	<t>
	The OPTIONAL <maint:tlds> element contains one or more <maint:tl	The <bcp14>OPTIONAL</bcp14> <maint:tlds> element contains one or mo
	d>	re <maint:tld>
	child elements. If the <maint:tlds> is not present, the entire	child elements. If the <maint:tlds> is not present, the entire
	system is affected.	system is affected.

	<list style="hanging" hangIndent="3"><t hangText="<maint:tld>">	</t>
	<vspace blankLines="0"/>	<dl newline="true" spacing="normal" indent="3">
	The affected top-level domain or registry zone, which SHALL be	<dt><maint:tld></dt>
	in A-label form, according to <xref target="RFC5891"/>.	<dd>
	</t>	The affected top-level domain or registry zone, which <bcp14>SHALL</bcp14
		> be
	</list>	in A-label form, according to <xref target="RFC5891" format="default"/>
	</t>	.
		</dd>
	<t><list style="hanging" hangIndent="3"><t hangText="<maint:interventi	</dl>
	on>">	</dd>
	<vspace blankLines="0"/>	<dt/>
	The OPTIONAL <maint:intervention> element contains the following	<dd>
		<dl newline="true" spacing="normal" indent="3">
		<dt><maint:intervention></dt>
		<dd>
		<t>
		The <bcp14>OPTIONAL</bcp14> <maint:intervention> element contains t
		he following
	child elements:	child elements:

	<list style="hanging" hangIndent="3"><t hangText="<maint:connection&gt	</t>
	;">	<dl newline="true" spacing="normal" indent="3">
	<vspace blankLines="0"/>	<dt><maint:connection></dt>
	The value SHALL be boolean and indicates if a client needs to	<dd>
	perform a connection-related action, such as a reconnect. The	The value <bcp14>SHALL</bcp14> be boolean and indicates if a client
	attribute should only be used as a flag to indicate connections	needs to perform a connection-related action such as a reconnect. The
	will be affected. Servers SHOULD include a description of how	attribute should only be used as a flag to indicate connections will
	the connections are affected in the <maint:description> element	be affected. Servers <bcp14>SHOULD</bcp14> include a description of
	or use the <maint:detail> element above.	how the connections are affected in the <maint:description>
	</t>	element or use the <maint:detail> element above.
		</dd>
	<t hangText="<maint:implementation>">	<dt><maint:implementation></dt>
	<vspace blankLines="0"/>	<dd>
	The value SHALL be boolean and indicates if a client needs to	The value <bcp14>SHALL</bcp14> be boolean and indicates if a client
	perform an implementation-related action, such as a code	needs to perform an implementation-related action such as a code
	change. The attribute should only be used as a flag to indicate	change. The attribute should only be used as a flag to indicate
	implementation will be affected. Servers SHOULD include a	implementation will be affected. Servers <bcp14>SHOULD</bcp14> include
	description of how the implementation is affected in the	a description of how the implementation is affected in the
	<maint:description> element or use the <maint:detail> eleme	<maint:description> element or use the <maint:detail>
	nt	element above.
	above.	</dd>
	</t>	</dl>
		</dd>
	</list>	<dt><maint:crDate></dt>
	</t>	<dd>

	<t hangText="<maint:crDate>">
	<vspace blankLines="0"/>
	The date and time of the maintenance object creation.	The date and time of the maintenance object creation.

	</t>	</dd>
		<dt><maint:upDate></dt>
	<t hangText="<maint:upDate>">	<dd>
	<vspace blankLines="0"/>	The <bcp14>OPTIONAL</bcp14> date and time of the most recent maintenance
	The OPTIONAL date and time of the most recent maintenance object	object
	modification. This element MUST NOT be present if the maintenance	modification. This element <bcp14>MUST NOT</bcp14> be present if the maint
		enance
	object has never been modified.	object has never been modified.

	</t>	</dd>
		</dl>
	</list>	</dd>
	</t>	</dl>
		</section>
	</list>	</section>
	</t>	<section anchor="sect-4" numbered="true" toc="default">
		<name>EPP Command Mapping</name>
	</section>	<t>
		A detailed description of the EPP syntax and semantics can be found in the
	</section>	EPP core protocol specification <xref target="RFC5730"
		format="default"/>. The command mappings described here are specifically
	<section title="EPP Command Mapping" anchor="sect-4"><t>	used to notify registrars of registry maintenance events and object
	A detailed description of the EPP syntax and semantics can be found	mapping.</t>
	in the EPP core protocol specification <xref target="RFC5730"/>. The command	<section anchor="sect-4.1" numbered="true" toc="default">
	mappings described here are specifically used to notify registrars of	<name>EPP Query Commands</name>
	registry maintenance events and object mapping.</t>

	<section title="EPP Query Commands" anchor="sect-4.1"><t>
	EPP <xref target="RFC5730"/> provides three commands to retrieve object infor
	mation:
	<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>	<t>

	This extension does not add any elements to EPP <check> and	EPP <xref target="RFC5730" format="default"/> provides three commands to
	<transfer> commands or responses.</t>	retrieve object information: <check> to determine if an object is
		known to the server, <info> to retrieve detailed information
	<section title="EPP <info> Command" anchor="sect-4.1.1"><t>	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>
		<section anchor="sect-4.1.1" numbered="true" toc="default">
		<name>EPP <info> Command</name>
		<t>
	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,
	elements, the <info> command MUST contain a <maint:info>	the <info> command <bcp14>MUST</bcp14> contain a <maint:info>
	element that identifies the maintenance namespace.</t>	element that identifies the maintenance namespace.</t>

		<t>
		The <maint:info> element <bcp14>MUST</bcp14> contain a child
		element. It is either the <maint:id> child element, described in
		<xref target="sect-4.1.1.1" format="default"/>, to query for a specific
		maintenance item or the <maint:list> child element, described in
		<xref target="sect-4.1.1.2" format="default"/>, to query all maintenance
		items.</t>
		<section anchor="sect-4.1.1.1" numbered="true" toc="default">
		<name>Info Maintenance 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 <xref target="sect-3.3"
		format="default"/>. If the maintenance identifier does not exist, the
		server <bcp14>MUST</bcp14> return an EPP error result code of 2303 ("Object
		does not exist") <xref target="RFC5730" format="default"/>.</t> <t> The
		following is an example of retrieving a specific maintenance item in an
		<info> command.</t>


	<t>	<sourcecode><![CDATA[
	The <maint:info> element MUST contain a child element. It is either
	the <maint:id> child element, described in <xref target="sect-4.1.1.1"/
	>, to query
	for a specific maintenance item or the <maint:list> child element,
	described in <xref target="sect-4.1.1.2"/>, to query all maintenance items.</
	t>

	<section title="Info Maintenance Item" anchor="sect-4.1.1.1"><t>
	The information regarding a specific maintenance item can be
	retrieved by using the <info> command with the <maint:info> eleme
	nt
	and the <maint:id> child element, defined in <xref target="sect-3.3"/>.
	If the
	maintenance identifier does not exist, the server MUST return an EPP
	error result code of 2303 ("Object does not exist") <xref target="RFC5730"/>.
	</t>

	<t>
	Example to retrieve a specific maintenance item in an <info> command.</
	t>

	<figure><artwork><![CDATA[
	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-1.0">	C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0">
	C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>	C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>
	C: </maint:info>	C: </maint:info>
	C: </info>	C: </info>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>	C:</epp>

	]]></artwork>	]]></sourcecode>
	</figure>	<t>
	<t>
	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 th at	<resData> element <bcp14>MUST</bcp14> 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 <xref target="sect-3.3"/>.	contains the <maint:item> element defined in <xref target="sect-3.3" fo
	</t>	rmat="default"/>.</t>
		<t>
	<t>	The following is an example of returning a specific maintenance item in an &l
	Example of returning a specific maintenance item in an <info>	t;info>
	response.</t>	response.</t>

		<sourcecode><![CDATA[
	<figure><artwork><![CDATA[
	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-1.0">	S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0">
	S: <maint:item>	S: <maint:item>

	skipping to change at line 492 ¶	skipping to change at line 470 ¶
	S: <maint:crDate>2021-11-08T22:10:00Z</maint:crDate>	S: <maint:crDate>2021-11-08T22:10:00Z</maint:crDate>
	S: </maint:item>	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>

	]]></artwork>	]]></sourcecode>
	</figure>	</section>
	</section>	<section anchor="sect-4.1.1.2" numbered="true" toc="default">
		<name>Info Maintenance List</name>
	<section title="Info Maintenance List" anchor="sect-4.1.1.2"><t>	<t>
	The information for a list of maintenance items can be retrieved by	The information for a list of maintenance items can be retrieved by using
	using the <info> command with the <maint:info> element and the em	the <info> command with the <maint:info> element and the empty
	pty
	<maint:list> child element. Server policy determines if completed	<maint:list> child element. Server policy determines if completed
	maintenance events will be included in the list of maintenance items.</t>	maintenance events will be included in the list of maintenance items.</t>

		<t> The following is an example of retrieving the list of maintenance items
	<t>	in an <info> command.</t>
	Example to retrieve the list of maintenance items in an <info>	<sourcecode><![CDATA[
	command.</t>

	<figure><artwork><![CDATA[
	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-1.0">	C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0">
	C: <maint:list/>	C: <maint:list/>
	C: </maint:info>	C: </maint:info>
	C: </info>	C: </info>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>	C:</epp>

	]]></artwork>	]]></sourcecode>
	</figure>	<t>
	<t>
	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 <bcp14>MUST</bcp14> 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:</t>	contains the following child elements:</t>

		<ul empty="true" spacing="normal">
	<t><list style="empty" hangIndent="3">	<li>
	<t><list style="hanging" hangIndent="3"><t hangText="<maint:id>">	<dl newline="true" spacing="normal" indent="3">
	<vspace blankLines="0"/>	<dt><maint:id></dt>
	The <maint:id> element defined in <xref target="sect-3.3"/>.	<dd>
	</t>	The <maint:id> element defined in <xref target="sect-3.3" format="d
		efault"/>.
	<t hangText="<maint:start>">	</dd>
	<vspace blankLines="0"/>	<dt><maint:start></dt>
	The <maint:start> element defined in <xref target="sect-3.3"/>.	<dd>
	</t>	The <maint:start> element defined in <xref target="sect-3.3" format
		="default"/>.
	<t hangText="<maint:end>">	</dd>
	<vspace blankLines="0"/>	<dt><maint:end></dt>
	The <maint:end> element defined in <xref target="sect-3.3"/>.	<dd>
	</t>	The <maint:end> element defined in <xref target="sect-3.3" format="
		default"/>.
	<t hangText="<maint:crDate>">	</dd>
	<vspace blankLines="0"/>	<dt><maint:crDate></dt>
	The <maint:crDate> element defined in <xref target="sect-3.3"/>.	<dd>
	</t>	The <maint:crDate> element defined in <xref target="sect-3.3" forma
		t="default"/>.
	<t hangText="<maint:upDate>">	</dd>
	<vspace blankLines="0"/>	<dt><maint:upDate></dt>
	The OPTIONAL <maint:upDate> element defined in <xref target="sect-3	<dd>
	.3"/>.	The <bcp14>OPTIONAL</bcp14> <maint:upDate> element defined in <xref
	</t>	target="sect-3.3" format="default"/>.
		</dd>
	</list>	</dl>
	</t>	</li>
		</ul>
	</list>	<t> The following is an example of returning the list of
	</t>	maintenance items in an <info> response.</t>
		<sourcecode><![CDATA[
	<t>
	Example of returning the list of maintenance items in an <info>
	response.</t>

	<figure><artwork><![CDATA[
	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-1.0">	S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0">
	S: <maint:list>	S: <maint:list>

	skipping to change at line 600 ¶	skipping to change at line 565 ¶
	S: </maint:listItem>	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>

	]]></artwork>	]]></sourcecode>
	</figure>	</section>
	</section>	</section>
		<section anchor="sect-4.1.2" numbered="true" toc="default">
	</section>	<name>EPP <poll> Command</name>
		<t>
	<section title="EPP <poll> Command" anchor="sect-4.1.2"><t>	The EPP <poll> command and response are defined in <xref
	The EPP <poll> command and response are defined in Section 2.9.2.3 of	target="RFC5730" sectionFormat="of" section="2.9.2.3"
	<xref target="RFC5730"/>. The Registry Maintenance Notification is included i	format="default"/>. The Registry Maintenance Notification is included in
	n the	the EPP <poll> response in <xref target="RFC5730"
	EPP <poll> response of <xref target="RFC5730"/>.</t>	format="default"/>.</t>


	<t>	<t>
	There are five types of poll messages for the Registry Maintenance	There are five types of poll messages for the Registry Maintenance

	Notification, defined by the <maint:pollType> element in <xref target="	Notification, defined by the <maint:pollType> element in <xref
	sect-3.3"/>.	target="sect-3.3" format="default"/>. A poll message might be generated
	A poll message might be generated when a maintenance event is	when a maintenance event is created, updated, or deleted. A courtesy poll
	created, updated, or deleted. A courtesy poll message can be sent as	message can be sent as a reminder of an upcoming maintenance event. An end
	a reminder of an upcoming maintenance event. An end poll message can	poll message can be sent when the maintenance event is completed. In the
	be sent when the maintenance event is completed. In the case of a	case of a message specific to Registry Maintenance, a <maint:infData>
	Registry Maintenance specific message, a <maint:infData> element,	element that identifies the maintenance namespace will be included within
	that identifies the maintenance namespace will be included within
	the <resData> element of the standard <poll> response. The	the <resData> element of the standard <poll> response. The

	<maint:infData> element contains the <maint:item> element defined	<maint:infData> element contains the <maint:item> element
	in	defined in <xref target="sect-3.3" format="default"/>.</t> <t> The
	<xref target="sect-3.3"/>.</t>	following is an example of a <poll> command:</t>
		<sourcecode><![CDATA[
	<t>
	Example <poll> command:</t>

	<figure><artwork><![CDATA[
	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>

		]]></sourcecode>


	Example <poll> response:	<t>
		Example <poll> response:
		</t>


		<sourcecode><![CDATA[
	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>2021-11-08T22:10:00Z</qDate>	S: <qDate>2021-11-08T22:10:00Z</qDate>
	S: <msg lang="en">Registry Maintenance Notification</msg>	S: <msg lang="en">Registry Maintenance Notification</msg>
	S: </msgQ>	S: </msgQ>

	skipping to change at line 687 ¶	skipping to change at line 654 ¶
	S: <maint:crDate>2021-11-08T22:10:00Z</maint:crDate>	S: <maint:crDate>2021-11-08T22:10:00Z</maint:crDate>
	S: </maint:item>	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>

	]]></artwork>	]]></sourcecode>
	</figure>	</section>
	</section>	</section>
		<section anchor="sect-4.2" numbered="true" toc="default">
	</section>	<name>EPP Transform Commands</name>
		<t>
	<section title="EPP Transform Commands" anchor="sect-4.2"><t>
	EPP provides five commands to transform objects: <create> to create	EPP provides five commands to transform objects: <create> to create
	an instance of an object, <delete> to delete an instance of an	an instance of an object, <delete> to delete an instance of an
	object, <renew> to extend the validity period of an object,	object, <renew> to extend the validity period of an object,
	<transfer> to manage object sponsorship changes, and <update> to	<transfer> to manage object sponsorship changes, and <update> to
	change information associated with an object.</t>	change information associated with an object.</t>


	<t>	<t>
	This extension does not add any elements to the EPP <create>,	This extension does not add any elements to the EPP <create>,

	<delete>, <renew>, <transfer>, and <update>.</t>	<delete>, <renew>, <transfer>, and <update> commands.
		</t>
	</section>	</section>
		</section>
	</section>	<section anchor="sect-5" numbered="true" toc="default">
		<name>Formal Syntax</name>
	<section title="Formal Syntax" anchor="sect-5"><t>	<t>
	The EPP Registry Maintenance Notification schema is presented here.</t>	The EPP Registry Maintenance Notification schema is presented here.</t>

		<t>The formal syntax is a complete schema representation of
	<t>The formal syntax presented here is a complete schema representation of
	the object mapping suitable for automated validation of EPP XML	the object mapping suitable for automated validation of EPP XML
	instances. The <CODE BEGINS> and <CODE ENDS> tags are not part	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	of the schema; they are used to note the beginning and end of the schema
	for URI registration purposes.</t>	for URI registration purposes.</t>

		<section anchor="sect-5.1" numbered="true" toc="default">
	<section title="Registry Maintenance Notification EPP Mapping Schema" anc	<name>Registry Maintenance Notification EPP Mapping Schema</name>
	hor="sect-5.1"><figure><artwork><![CDATA[	<sourcecode type="xml" markers="true"><![CDATA[
	<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-1.0"	maintenance-1.0"
	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-1.0"	xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-1.0"
	xmlns="https://www.w3.org/2001/XMLSchema"	xmlns="https://www.w3.org/2001/XMLSchema"
	elementFormDefault="qualified">	elementFormDefault="qualified">
	<!--	<!--
	Import common element types	Import common element types

	skipping to change at line 948 ¶	skipping to change at line 912 ¶
	<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>
	<!--	<!--
	End of schema.	End of schema.
	-->	-->
	</schema>	</schema>

	<CODE ENDS>	]]></sourcecode>
	]]></artwork>	</section>
	</figure>	</section>
	</section>	<section anchor="sect-6" numbered="true" toc="default">
		<name>IANA Considerations</name>
	</section>	<section anchor="sect-6.1" numbered="true" toc="default">
		<name>XML Namespace</name>
	<section title="IANA Considerations" anchor="sect-6"><section title="XML	<t>
	Namespace" anchor="sect-6.1"><t>
	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 <xref target="RFC3688"/>.</t>	conforming to a registry mechanism defined in <xref target="RFC3688" format="
		default"/>.</t>
	<t>Registration request for the maintenance namespace:	<t>The following entry has been registered as an XML namespace:
	<list>	</t>
	<t>URI: urn:ietf:params:xml:ns:epp:maintenance-1.0</t>
	<t>Registrant Contact: IESG</t>
	<t> XML: None. Namespace URIs do not represent an XML specification.
	</t>
	</list>
	</t>

	<t>Registration request for the maintenance schema:
	<list>
	<t>URI: urn:ietf:params:xml:schema:epp:maintenance-1.0</t>
	<t>Registrant Contact: IESG</t>
	<t>XML: See the "Formal Syntax" section of this document.</t>
	</list>
	</t>

	</section>

	<section title="EPP Extension Registry" anchor="sect-6.2"><t>
	The following registration of the EPP Extension Registry, described
	in <xref target="RFC7451"/>, is requested:</t>

	<t>
	Name of Extension: Registry Maintenance Notification for the
	Extensible Provisioning Protocol (EPP)</t>

	<t>
	Document status: Standards Track</t>

	<t>
	Reference: (insert the reference to RFC version of this document)</t>

	<t>
	Registrant Name and Email Address: IESG <iesg@ietf.org></t>

	<t>
	TLDs: Any</t>

	<t>
	IPR Disclosure: None</t>

	<t>
	Status: Active</t>

	<t>
	Notes: None</t>

	</section>

	</section>

	<section title="Security Considerations" anchor="sect-7"><t>
	The security considerations of <xref target="RFC5730"/> apply in this documen
	t.
	Additionally, a server MUST only provide maintenance information to
	clients that are authorized. Suppose a client queries a maintenance
	identifier that it is not authorized to access per <xref target="sect-4.1.1.1
	"/>
	"Info Maintenance Item". In that case, the server SHOULD return an
	EPP error result code of 2201 ("Authorization error") or 2303
	("Object does not exist") <xref target="RFC5730"/>. The list of top-level dom
	ains or
	registry zones returned in the "Info Maintenance Item" response
	SHOULD 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 runnin
	g code, which may serve as evidence of valuable experimentation and feedback tha
	t have made the implemented protocols more mature. It is up to the individual wo
	rking 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>
	<references title="Informative References">
	&RFC3688;
	&RFC7451;
	</references>
	<section title="Change History" anchor="sect-a"><section title="Change fr
	om draft-sattler-epp-poll-maintenance-response to draft-sattler-epp-registry-mai
	ntenance" 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 dra
	ft-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>	<dl spacing="compact">
	Editorial changes. Changed XML namespace and schema from 0.1 to 0.2.	<dt>URI:
	Added pollType to reflect create, update, or delete maintenance poll	</dt>
	messages.</t>	<dd>urn:ietf:params:xml:ns:epp:maintenance-1.0
		</dd>


	</section>	<dt>Registrant Contact:
		</dt>
		<dd>IESG
		</dd>


	<section title="Change from 08 to 09" anchor="sect-a.11"><t>	<dt>XML:
	Editorial changes. Added new section "Migrating to Newer Versions of This Ext	</dt>
	ension".</t>	<dd>None. Namespace URIs do not represent an XML specification.
		</dd>


	</section>	</dl>


	<section title="Change from 09 to 10" anchor="sect-a.12"><t>	<t>The following entry has been registered to the XML maintenance schema:
	Editorial changes. Renamed "msg" to "name". Added "courtesy" and	</t>
	"end" to pollType.</t>


	</section>	<dl spacing="compact">


	<section title="Change from 10 to 11" anchor="sect-a.13"><t>	<dt>URI:
	Editorial changes. Added mime type to description.</t>	</dt>
		<dd>urn:ietf:params:xml:schema:epp:maintenance-1.0
		</dd>


	</section>	<dt>Registrant Contact:
		</dt>
		<dd>IESG
		</dd>


	<section title="Change from 11 to 12" anchor="sect-a.14"><t>	<dt>XML:
	Editorial changes. Changed XML namespace from 0.2 to 0.3.</t>	</dt>
		<dd>See the <xref target="sect-5" format="none">"Formal Syntax"</xref>
		section of this document.
		</dd>
		</dl>
		</section>
		<section anchor="sect-6.2" numbered="true" toc="default">
		<name>EPP Extension Registry</name>
		<t>
		The following entry has been added to the "Extensions for the Extensible Prov
		isioning Protocol (EPP)" registry, described
		in <xref target="RFC7451" format="default"/>:</t>


	</section>	<dl spacing="compact">


	<section title="Change from 12 to 13" anchor="sect-a.15"><t>	<dt>Name of Extension:
	Editorial changes. Added TANGO Registry Services to <xref target="sect-8"/>.	</dt>
	Added	<dd>Registry Maintenance Notification for the Extensible Provisioning Proto
	Michael Bauland to acknowledgments. Added "none" to <maint:impact>.</t>	col (EPP)
		</dd>


	</section>	<dt>Document status:
		</dt>
		<dd>Standards Track
		</dd>


	<section title="Change from 13 to 14" anchor="sect-a.16"><t>	<dt>Reference:
	Accepted in WGLC. Changed XML namespace from 0.3 to 1.0.</t>	</dt>
		<dd>RFC 9167
		</dd>


	</section>	<dt>Registrant Name and Email Address:
		</dt>
		<dd>IESG <iesg@ietf.org>
		</dd>


	<section title="Change from 14 to 15" anchor="sect-a.17"><t>	<dt>TLDs:
	Editorial changes, added feedback from the document shepherd.</t>	</dt>
		<dd>Any
		</dd>


	</section>	<dt>IPR Disclosure:
		</dt>
		<dd>None
		</dd>


	<section title="Change from 15 to 16" anchor="sect-a.18"><t>	<dt>Status:
	Editorial changes, added feedback from area director.</t>	</dt>
		<dd>Active
		</dd>


	</section>	<dt>Notes:
		</dt>
		<dd>None
		</dd>
		</dl>
		</section>
		</section>
		<section anchor="sect-7" numbered="true" toc="default">
		<name>Security Considerations</name>
		<t>
		The security considerations of <xref target="RFC5730" format="default"/>
		apply in this document. Additionally, a server <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 <xref target="sect-4.1.1.1" format="default"/>, "Info Maintenance
		Item". In that case, the server <bcp14>SHOULD</bcp14> return an EPP error
		result code of 2201 ("Authorization error") or 2303 ("Object does not
		exist") <xref target="RFC5730" format="default"/>. The list of top-level
		domains or registry zones returned in the "Info Maintenance Item" response
		<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="Change from 16 to 17" anchor="sect-a.19"><t>	</middle>
	Editorial changes, added last call feedback. Changed schema URI	<back>
	to urn:ietf:params:xml:schema:epp:maintenance-1.0. Changed dates in	<references>
	examples to more recent dates.</t>	<name>References</name>
		<references>
		<name>Normative References</name>


	</section>	<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>


	<section title="Change from 17 to 18" anchor="sect-a.20"><t>	<reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2008/
	Editorial changes.</t>	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 S
		perberg-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>


	</section>	<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.R
		FC.3339.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.3986.xml"/>


	<section title="Change from 18 to 19" anchor="sect-a.21"><t>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/refe
	Editorial changes.</t>	rence.RFC.5646.xml"/>


	</section>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
		C.5730.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.5891.xml"/>


	</section>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.8174.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.9038.xml"/>
		</references>
		<references>
		<name>Informative References</name>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.3688.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.7451.xml"/>
		</references>
		</references>


	<section title="Acknowledgments" numbered="no" anchor="acknowledgments"><	<section numbered="false" anchor="acknowledgments" toc="default">
	t>	<name>Acknowledgments</name>
		<t>
	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, Michael Bauland, Patrick Mevzek,	and suggestions: <contact fullname="James Gould"/>, <contact fullname="Michae
	Quoc-Anh Pham, Raymond Zylstra, Christopher Martens, Anthony Eden,	l Bauland"/>, <contact fullname="Patrick Mevzek"/>,
	Neal McPherson, Craig Marchant, and Andreas Huber.</t>	<contact fullname="Quoc-Anh Pham"/>, <contact fullname="Raymond Zylstra"/>, <
		contact fullname="Christopher Martens"/>, <contact fullname="Anthony Eden"/>,
	</section>	<contact fullname="Neal McPherson"/>, <contact fullname="Craig Marchant"/>, a
		nd <contact fullname="Andreas Huber"/>.</t>
	</back>	</section>


	</rfc>	</back>
		</rfc>

End of changes. 95 change blocks.
	787 lines changed or deleted	631 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/