draft-ietf-regext-epp-registry-maintenance-05.txt   draft-ietf-regext-epp-registry-maintenance-06.txt 
Internet Engineering Task Force (IETF) T. Sattler Internet Engineering Task Force (IETF) T. Sattler
Internet-Draft Internet-Draft
Intended status: Standards Track R. Carney Intended status: Standards Track R. Carney
Expires: June 30, 2021 J. Kolker Expires: June 30, 2021 J. Kolker
GoDaddy Inc. GoDaddy Inc.
December 1, 2020 December 8, 2020
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-registry-maintenance-05 draft-ietf-regext-epp-registry-maintenance-06
Abstract Abstract
This document describes an Extensible Provision Protocol (EPP) This document describes an Extensible Provision Protocol (EPP)
mapping for registry's maintenance notifications. mapping for registry's maintenance notifications.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Internationalized Domain Names . . . . . . . . . . . . . 3 2.1. Internationalized Domain Names . . . . . . . . . . . . . 3
2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3 2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3
2.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4 2.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6
3.1.2. EPP <transfer> Command . . . . . . . . . . . . . . . 6 3.1.2. EPP <transfer> Command . . . . . . . . . . . . . . . 6
3.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 6 3.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 6
3.1.3.1. Query Maintenance Item . . . . . . . . . . . . . . 7 3.1.3.1. Info Maintenance Item . . . . . . . . . . . . . . . 6
3.1.3.2. Query Maintenance List . . . . . . . . . . . . . . 8 3.1.3.2. Info Maintenance List . . . . . . . . . . . . . . . 8
3.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 9 3.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 9
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 11 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 11
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 11 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 11
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12 4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 18
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 7.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19
A.1. Change from draft-sattler-epp-poll-maintenance-response to A.1. Change from draft-sattler-epp-poll-maintenance-response to
draft-sattler-epp-registry-maintenance . . . . . . . . . 19 draft-sattler-epp-registry-maintenance . . . . . . . . . 19
A.2. Change from draft-sattler-epp-registry-maintenance to A.2. Change from draft-sattler-epp-registry-maintenance to
draft-ietf-regext-epp-registry-maintenance . . . . . . . 19 draft-ietf-regext-epp-registry-maintenance . . . . . . . 19
A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19
A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20
A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20
A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20
A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
Registries usually conduct maintenances and inform registrars in Registries usually conduct maintenances and inform registrars in
different ways. Given the expansion of the DNS namespace, it is now different ways. Given the expansion of the DNS namespace, it is now
desirable to provide a method for EPP servers to notify EPP clients desirable to provide a method for EPP servers to notify EPP clients
as well as a method for EPP clients to query EPP servers for upcoming as well as a method for EPP clients to query EPP servers for upcoming
maintenances. maintenances.
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
skipping to change at page 4, line 8 skipping to change at page 4, line 8
2.2. Dates and Times 2.2. Dates and Times
All dates and times attribute values MUST be expressed in Universal All dates and times attribute values MUST be expressed in Universal
Coordinated Time (UTC) using the Gregorian calendar. The extended Coordinated Time (UTC) using the Gregorian calendar. The extended
date-time form using upper case "T" and "Z" characters defined in ISO date-time form using upper case "T" and "Z" characters defined in ISO
8601 [RFC3339] MUST be used to represent date-time values. 8601 [RFC3339] MUST be used to represent date-time values.
2.3. Maintenance Elements 2.3. Maintenance Elements
The <maint:item> element describes a single registry maintenance The <maint:item> element describes a single registry maintenance
event during a specific period. This element will be used at EPP event during a specific period. This element is used in a maintenance
<poll> messages and to extend the EPP <info> command. item EPP <info> response and <poll> message.
For creating a new maintenance the attribute <maint:crDate> MUST be For creating a new maintenance the attribute <maint:crDate> MUST be
set and the attribute <maint:upDate> SHALL NOT be present. set and the attribute <maint:upDate> SHALL NOT be present.
For updating a maintenance the attributes <maint:crDate> and For updating a maintenance the attributes <maint:crDate> and
<maint:upDate> MUST be set. <maint:upDate> MUST be set.
<maint:id> <maint:id>
MUST be present and a server unique id and SHALL NOT be MUST be present and a server unique id and SHALL NOT be
changed if maintenance is updated or deleted. A human-readable changed if maintenance is updated or deleted. A human-readable
skipping to change at page 6, line 53 skipping to change at page 6, line 43
no mapping defined for the EPP <transfer> command. no mapping defined for the EPP <transfer> command.
3.1.3. EPP <info> Command 3.1.3. EPP <info> Command
EPP provides the <info> command that is used to retrieve registry EPP provides the <info> command that is used to retrieve registry
maintenance information. In addition to the standard EPP command maintenance information. In addition to the standard EPP command
elements, the <info> command MUST contain a <maint:info> elements, the <info> command MUST contain a <maint:info>
element that identifies the maintenance namespace. element that identifies the maintenance namespace.
The <maint:info> element MUST contain a child element. It is either The <maint:info> element MUST contain a child element. It is either
<maint:id> to retrieve a specific maintenance notification or <maint:id> to retrieve a specific maintenance item or
<maint:list> to query all maintenance notifications. <maint:list> to query all maintenance items.
3.1.3.1. Query one maintenance item 3.1.3.1. Info Maintenance Item
If a <maint:info> is send with a <maint:id> that does not exist on The information on a specific Maintenance Item can be retrieved by
the server side, then the result code 2303 MUST be responded. using <info> command with the element <maint:info> and the child
element <maint:id>.
Please see the defintion of <maint> elements in Section 2.3. If a <maint:info> is sent with a <maint:id> that does not exist on
the server side, then the result code 2303 MUST be responded.
Example <info> command with explicit <maint:id> to get one specific Example to retrieve a specific maintenance item in an <info> command.
maintenance:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <info> C: <info>
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"> C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1">
C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>
C: </maint:info> C: </maint:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Example <info> response for one specific maintenance notification, When an <info> command has been processed successfully, the EPP
which was requested with a explicit <maint:id>. In this case, it <resData> element MUST contain a child <maint:infData> element that
provides the all "required" elements and additional elements identifies the maintenance namespace. The <maint:infData> element
<maint:start>, <maint:end>, <maint:detail>, <maint:description>, contains the <maint:item> element defined in Section 2.3.
<maint:tlds>, <maint:intervention>.
Example of returning a specific maintenance item in an <info>
response.
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1">
S: <maint:item> S: <maint:item>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6
S: </maint:id> S: </maint:id>
S: <maint:systems> S: <maint:systems>
S: <maint:system> S: <maint:system>
S: <maint:name>EPP</maint:name> S: <maint:name>EPP</maint:name>
S: <maint:host>epp.registry.example S: <maint:host>epp.registry.example
S: </maint:host> S: </maint:host>
S: <maint:impact>blackout</maint:impact> S: <maint:impact>full</maint:impact>
S: </maint:system> S: </maint:system>
S: </maint:systems> S: </maint:systems>
S: <maint:environment type="production"/> S: <maint:environment type="production"/>
S: <maint:start>2017-09-30T06:00:00Z</maint:start> S: <maint:start>2020-09-30T06:00:00Z</maint:start>
S: <maint:end>2017-09-30T14:25:57Z</maint:end> S: <maint:end>2020-09-30T14:25:57Z</maint:end>
S: <maint:reason>planned</maint:reason> S: <maint:reason>planned</maint:reason>
S: <maint:detail> S: <maint:detail>
S: https://www.registry.example/notice?123 S: https://www.registry.example/notice?123
S: </maint:detail> S: </maint:detail>
S: <maint:description lang="en">free text S: <maint:description lang="en">free text
S: </maint:description> S: </maint:description>
S: <maint:tlds> S: <maint:tlds>
S: <maint:tld>example</maint:tld> S: <maint:tld>example</maint:tld>
S: <maint:tld>test</maint:tld> S: <maint:tld>test</maint:tld>
S: </maint:tlds> S: </maint:tlds>
S: <maint:intervention> S: <maint:intervention>
S: <maint:connection>false</maint:connection> S: <maint:connection>false</maint:connection>
S: <maint:implementation>false</maint:implementation> S: <maint:implementation>false</maint:implementation>
S: </maint:intervention> S: </maint:intervention>
S: <maint:crDate>2017-03-08T22:10:00Z</maint:crDate> S: <maint:crDate>2020-03-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>
3.1.3.2. Query maintenance list 3.1.3.2. Info Maintenance List
Example <info> command with <maint:list> to query all maintenances The Info Maintenance List can be retrieved by using the <info>
subject to server policy: command and the element <maint:info> with the child element
<maint:list/>. Server policy determines if previous maintenances will
be listed in the <maint:list>.
Example to retrieve the maintenance list in an <info> command.
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <info> C: <info>
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"> C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1">
C: <maint:list/> C: <maint:list/>
C: </maint:info> C: </maint:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <maint:infData> element
that identifies the maintenance namespace. The <maint:infData>
element contains the <maint:list> element a list of <maint:listItem>
elements. The <maint:listItem> element contains the following child
elements:
<maint:id>: <maint:id> defined in Section 2.3.
<maint:start>: <maint:start> defined in Section 2.3.
<maint:end>: <maint:end> defined in Section 2.3.
<maint:crDate>: <maint:crDate> defined in Section 2.3.
<maint:upDate>: OPTIONAL <maint:upDate> defined in Section 2.3.
Example <info> response querying all maintenances subject to server Example of returning the maintenance list in an <info> response.
policy. In this case, all the "required" elements will be returned
and additional <maint:upDate>.
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1">
S: <maint:list> S: <maint:list>
S: <maint:listItem> S: <maint:listItem>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6
S: </maint:id> S: </maint:id>
S: <maint:start>2017-04-30T06:00:00Z</maint:start> S: <maint:start>2020-04-30T06:00:00Z</maint:start>
S: <maint:end>2017-04-30T07:00:00Z</maint:end> S: <maint:end>2020-04-30T07:00:00Z</maint:end>
S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate> S: <maint:crDate>2020-02-08T22:10:00Z</maint:crDate>
S: </maint:listItem> S: </maint:listItem>
S: <maint:listItem> S: <maint:listItem>
S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f
S: </maint:id> S: </maint:id>
S: <maint:start>2017-06-15T04:30:00Z</maint:start> S: <maint:start>2020-06-15T04:30:00Z</maint:start>
S: <maint:end>2017-06-15T05:30:00Z</maint:end> S: <maint:end>2020-06-15T05:30:00Z</maint:end>
S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate> S: <maint:crDate>2020-02-08T22:10:00Z</maint:crDate>
S: <maint:upDate>2017-03-08T20:11:00Z</maint:upDate> S: <maint:upDate>2020-03-08T20:11:00Z</maint:upDate>
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>
skipping to change at page 10, line 24 skipping to change at page 10, line 38
Example <poll> response with the Registry Maintenance poll message: Example <poll> response with the Registry Maintenance poll message:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ count="1" id="12345"> S: <msgQ count="1" id="12345">
S: <qDate>2017-02-08T22:10:00Z</qDate> S: <qDate>2020-10-08T22:10:00Z</qDate>
S: <msg lang="en">Registry Maintenance Notification</msg> S: <msg lang="en">Registry Maintenance Notification</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.1">
S: <maint:item> S: <maint:item>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>
S: <maint:systems> S: <maint:systems>
S: <maint:system> S: <maint:system>
S: <maint:name>EPP</maint:name> S: <maint:name>EPP</maint:name>
S: <maint:host>epp.registry.example S: <maint:host>epp.registry.example
S: </maint:host> S: </maint:host>
S: <maint:impact>blackout</maint:impact> S: <maint:impact>full</maint:impact>
S: </maint:system> S: </maint:system>
S: </maint:systems> S: </maint:systems>
S: <maint:environment type="production"/> S: <maint:environment type="production"/>
S: <maint:start>2017-10-30T06:00:00Z</maint:start> S: <maint:start>2020-10-30T06:00:00Z</maint:start>
S: <maint:end>2017-10-30T14:25:57Z</maint:end> S: <maint:end>2020-10-30T14:25:57Z</maint:end>
S: <maint:reason>planned</maint:reason> S: <maint:reason>planned</maint:reason>
S: <maint:detail> S: <maint:detail>
S: https://www.registry.example/notice?123 S: https://www.registry.example/notice?123
S: </maint:detail> S: </maint:detail>
S: <maint:tlds> S: <maint:tlds>
S: <maint:tld>example</maint:tld> S: <maint:tld>example</maint:tld>
S: <maint:tld>test</maint:tld> S: <maint:tld>test</maint:tld>
S: </maint:tlds> S: </maint:tlds>
S: <maint:intervention> S: <maint:intervention>
S: <maint:connection>false</maint:connection> S: <maint:connection>false</maint:connection>
S: <maint:implementation>false</maint:implementation> S: <maint:implementation>false</maint:implementation>
S: </maint:intervention> S: </maint:intervention>
S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate> S: <maint:crDate>2020-02-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>
skipping to change at page 18, line 37 skipping to change at page 18, line 37
features. Readers are advised to note that other implementations may features. Readers are advised to note that other implementations may
exist. exist.
According to [RFC7942], "this will allow reviewers and working groups According to [RFC7942], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature. It and feedback that have made the implemented protocols more mature. It
is up to the individual working groups to use this information as is up to the individual working groups to use this information as
they see fit". they see fit".
Add implementation details once available. 7.1. GoDaddy Registry
Organization: GoDaddy Registry
Name: GoDaddy Registry
Description: GoDaddy Registry provides maintenance notifications to
their registrars.
Level of maturity: Production
Coverage: All aspects of the protocol according to the draft version
2 are implemented with further updates to come.
Licensing: Proprietary
Contact: quoc@registry.godaddy
URL: https://registry.godaddy
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997, Requirement Levels", BCP 14, RFC 2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
skipping to change at page 20, line 15 skipping to change at page 20, line 33
A.6. Change from 03 to 04 A.6. Change from 03 to 04
A lot of clarifications and editoral changes. A lot of clarifications and editoral changes.
A.7. Change from 04 to 05 A.7. Change from 04 to 05
Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 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>. urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed <maint:status>.
Clarified <maint:info> for retrieving maintenance items and the list. Clarified <maint:info> for retrieving maintenance items and the list.
A.8. Change from 05 to 06
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.
Acknowledgments Acknowledgments
The authors wish to thank the following individuals for their The authors wish to thank the following individuals for their
feedback and suggestions (sorted alphabetically by company): feedback and suggestions (sorted alphabetically by company):
o Patrick Mevzek o Patrick Mevzek
o Neal McPherson, 1&1 IONOS
o Anthony Eden, DNSimple o Anthony Eden, DNSimple
o Christopher Martens, Donuts o Christopher Martens, Donuts
o Quoc-Anh Pham, Neustar o Quoc-Anh Pham, GoDaddy Registry
o Raymond Zylstra, Neustar o Raymond Zylstra, GoDaddy Registry
o Neal McPherson, IONOS
o Andreas Huber, united-domains o Andreas Huber, united-domains
o Craig Marchant, VentraIP o Craig Marchant, VentraIP
o James Gould, Verisign o James Gould, Verisign
Authors' Addresses Authors' Addresses
Tobias Sattler Tobias Sattler
Email: tobias.sattler@me.com Email: tobias.sattler@me.com
URI: https://tobiassattler.com URI: https://tobiassattler.com
 End of changes. 30 change blocks. 
51 lines changed or deleted 93 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/