draft-ietf-regext-epp-registry-maintenance-09.txt   draft-ietf-regext-epp-registry-maintenance-10.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 29, 2020 January 13, 2021
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-registry-maintenance-09 draft-ietf-regext-epp-registry-maintenance-10
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 1, line 34 skipping to change at page 1, line 34
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress". material or to cite them other than as "work in progress".
This Internet-Draft will expire on June 30, 2021. This Internet-Draft will expire on June 30, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
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. Migrating to Newer Versions of This Extension . . . . . . . . 3 2. Migrating to Newer Versions of This Extension . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Internationalized Domain Names . . . . . . . . . . . . . 4 3.1. Internationalized Domain Names . . . . . . . . . . . . . 4
3.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 4 3.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 4
3.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4 3.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6 4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 6
4.1.2. EPP <transfer> Command . . . . . . . . . . . . . . . 6 4.1.2. EPP <transfer> Command . . . . . . . . . . . . . . . 6
4.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 6 4.1.3. EPP <info> Command . . . . . . . . . . . . . . . . . 7
4.1.3.1. Info Maintenance Item . . . . . . . . . . . . . . . 7 4.1.3.1. Info Maintenance Item . . . . . . . . . . . . . . . 7
4.1.3.2. Info Maintenance List . . . . . . . . . . . . . . . 8 4.1.3.2. Info Maintenance List . . . . . . . . . . . . . . . 8
4.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 8 4.1.4. EPP <poll> Command . . . . . . . . . . . . . . . . . 10
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11 4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 11 4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 11
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 11 4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 12
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11 4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 12
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11 4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 12
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12 5.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17
6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16 6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18
8.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 17 8.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 18
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.1. Normative References . . . . . . . . . . . . . . . . . . 18 9.1. Normative References . . . . . . . . . . . . . . . . . . 19
9.2. Informative References . . . . . . . . . . . . . . . . . 18 9.2. Informative References . . . . . . . . . . . . . . . . . 20
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 20
A.1. Change from draft-sattler-epp-poll-maintenance-response to A.1. Change from draft-sattler-epp-poll-maintenance-response to
draft-sattler-epp-registry-maintenance . . . . . . . . . 18 draft-sattler-epp-registry-maintenance . . . . . . . . . 20
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 . . . . . . . 20
A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 20
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 . . . . . . . . . . . . . . . . . . 19 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20
A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 19 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20
A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20
A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19 A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 21
A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 19 A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 21
A.11. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 19 A.11. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 21
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 19 A.12. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
Registries usually conduct maintenances and inform registrars in Registries usually conduct maintenances and inform registrars in
different ways. Given the DNS namespace expansion, it is now different ways. Given the DNS namespace expansion, it is now
desirable to provide methods for EPP servers to notify EPP clients desirable to provide methods for EPP servers to notify EPP clients
and EPP clients to query EPP servers for upcoming maintenances. and EPP clients to query EPP servers for upcoming maintenances.
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provision Protocol [RFC5730]. This mapping provides a Extensible Provision Protocol [RFC5730]. This mapping provides a
skipping to change at page 4, line 32 skipping to change at page 4, line 32
8601 [RFC3339] MUST be used to represent date-time values. 8601 [RFC3339] MUST be used to represent date-time values.
3.3. Maintenance Elements 3.3. Maintenance Elements
The <maint:item> element describes a single registry maintenance The <maint:item> element describes a single registry maintenance
event during a specific period. This element is used in a maintenance event during a specific period. This element is used in a maintenance
item EPP <info> response and <poll> message. item EPP <info> response and <poll> message.
<maint:id> <maint:id>
The server unique identifier for the maintenance with the OPTIONAL The server unique identifier for the maintenance with the OPTIONAL
"msg" attribute that includes a human-readable description of the "name" attribute that includes a human-readable name of the
maintenance. The server unique identifier SHALL NOT be changed if maintenance. The server unique identifier SHALL NOT be changed if
the maintenance is updated or deleted. When the "msg" attribute is the maintenance is updated or deleted. When the "name" attribute
set, the OPTIONAL "lang" attribute MAY be present to identify the is set, the OPTIONAL "lang" attribute MAY be present to identify
language if the negotiated value is something other than the the language if the negotiated value is something other than the
default value of "en" (English). default value of "en" (English).
<maint:type>
The OPTIONAL type of the maintenance that has the possible set of
values defined by server policy.
<maint:pollType> <maint:pollType>
The OPTIONAL <maint:pollType> element for a Registry Maintenance The OPTIONAL <maint:pollType> element for a Registry Maintenance
Notification poll message; values MUST either be "create", Notification poll message; values MUST either be "create",
"update", or "delete". For the "create" and "update" types, the "update", "delete", "courtesy", or "end". For the "create" and
server includes the state of the maintenance after the create or "update" types, the server includes the state of the maintenance
update. For the "delete" type, the server includes the state after the create or update. For the "delete" type, the server
of the maintenance prior to the delete. This element MUST be includes the state of the maintenance prior to the delete. The
present only for poll messages. "courtesy" provides a reminder of a maintenance and the "end"
provides a notification of the end of the maintenance without
updating the maintenance object and includes the latest state of
the maintenance. This element MUST be present only for poll
messages.
<maint:systems> <maint:systems>
One or more <maint:system> elements that are affected by the One or more <maint:system> elements that are affected by the
maintenance. maintenance.
<maint:system> <maint:system>
The <maint:system> element contains the following child The <maint:system> element contains the following child
elements: elements:
<maint:name> <maint:name>
skipping to change at page 6, line 55 skipping to change at page 7, line 13
no mapping defined for the EPP <transfer> command. no mapping defined for the EPP <transfer> command.
4.1.3. EPP <info> Command 4.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> child element, described in Section 4.1.3.1, to query for the <maint:id> child element, described in Section 4.1.3.1, to query
a specific maintenance item or <maint:list> child element, described for a specific maintenance item or the <maint:list> child element,
in Section 4.1.3.2, to query all maintenance items. described in Section 4.1.3.2, to query all maintenance items.
4.1.3.1. Info Maintenance Item 4.1.3.1. Info Maintenance Item
The information on a specific maintenance item can be retrieved by The information on a specific maintenance item can be retrieved by
using the <info> command with the <maint:info> element and the using the <info> command with the <maint:info> element and the
<maint:id> child element, defined in Section 3.3. If the maintenance <maint:id> child element, defined in Section 3.3. If the maintenance
identifier does not exist, the server MUST return an EPP error result identifier does not exist, the server MUST return an EPP error result
code of 2303 [RFC5730]. code of 2303 [RFC5730].
Example to retrieve a specific maintenance item in an <info> command. Example to retrieve a specific maintenance item in an <info> command.
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <info> C: <info>
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2"> C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3">
C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> C: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>
C: </maint:info> C: </maint:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <maint:infData> element that <resData> element MUST contain a child <maint:infData> element that
skipping to change at page 7, line 45 skipping to change at page 7, line 57
response. response.
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3">
S: <maint:item> S: <maint:item>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6
S: </maint:id> S: </maint:id>
S: <maint:systems> S: <maint:systems>
S: <maint:system> S: <maint:system>
S: <maint:name>EPP</maint:name> S: <maint:name>EPP</maint:name>
S: <maint:host>epp.registry.example S: <maint:host>epp.registry.example
S: </maint:host> S: </maint:host>
S: <maint:impact>full</maint:impact> S: <maint:impact>full</maint:impact>
S: </maint:system> S: </maint:system>
skipping to change at page 8, line 43 skipping to change at page 8, line 56
<maint:list> child element. Server policy determines if previous <maint:list> child element. Server policy determines if previous
maintenances will be included in the list of maintenance items. maintenances will be included in the list of maintenance items.
Example to retrieve the maintenance list in an <info> command. Example to retrieve the maintenance list in an <info> command.
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <info> C: <info>
C: <maint:info C: <maint:info
C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2"> C: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3">
C: <maint:list/> C: <maint:list/>
C: </maint:info> C: </maint:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <maint:infData> element <resData> element MUST contain a child <maint:infData> element
that identifies the maintenance namespace. The <maint:infData> that identifies the maintenance namespace. The <maint:infData>
skipping to change at page 9, line 27 skipping to change at page 9, line 42
Example of returning the maintenance list in an <info> response. Example of returning the maintenance list in an <info> response.
S:<?xml version="1.0" encoding="UTF-8"?> S:<?xml version="1.0" encoding="UTF-8"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3">
S: <maint:list> S: <maint:list>
S: <maint:listItem> S: <maint:listItem>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6 S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6
S: </maint:id> S: </maint:id>
S: <maint:start>2020-12-30T06:00:00Z</maint:start> S: <maint:start>2020-12-30T06:00:00Z</maint:start>
S: <maint:end>2020-12-30T07:00:00Z</maint:end> S: <maint:end>2020-12-30T07:00:00Z</maint:end>
S: <maint:crDate>2020-09-08T22:10:00Z</maint:crDate> S: <maint:crDate>2020-09-08T22:10:00Z</maint:crDate>
S: </maint:listItem> S: </maint:listItem>
S: <maint:listItem> S: <maint:listItem>
S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f S: <maint:id>91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f
skipping to change at page 10, line 37 skipping to change at page 10, line 53
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ count="1" id="12345"> S: <msgQ count="1" id="12345">
S: <qDate>2020-10-08T22:10:00Z</qDate> S: <qDate>2020-10-08T22:10:00Z</qDate>
S: <msg lang="en">Registry Maintenance Notification</msg> S: <msg lang="en">Registry Maintenance Notification</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <maint:infData S: <maint:infData
S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2"> S: xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3">
S: <maint:item> S: <maint:item>
S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id> S: <maint:id>2e6df9b0-4092-4491-bcc8-9fb2166dcee6</maint:id>
S: <maint:pollType>create</maint:pollType> S: <maint:pollType>create</maint:pollType>
S: <maint:systems> S: <maint:systems>
S: <maint:system> S: <maint:system>
S: <maint:name>EPP</maint:name> S: <maint:name>EPP</maint:name>
S: <maint:host>epp.registry.example S: <maint:host>epp.registry.example
S: </maint:host> S: </maint:host>
S: <maint:impact>full</maint:impact> S: <maint:impact>full</maint:impact>
S: </maint:system> S: </maint:system>
skipping to change at page 12, line 13 skipping to change at page 12, line 37
schema for URI registration purposes. schema for URI registration purposes.
5.1. Registry Maintenance EPP Mapping Schema 5.1. Registry Maintenance EPP Mapping Schema
<CODE BEGINS> <CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:epp: <schema targetNamespace="urn:ietf:params:xml:ns:epp:
maintenance-0.2" maintenance-0.2"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.2" xmlns:maint="urn:ietf:params:xml:ns:epp:maintenance-0.3"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Extensible Provisioning Protocol v1.0 Extensible Provisioning Protocol v1.0
skipping to change at page 12, line 48 skipping to change at page 13, line 21
<element name="id" type="maint:idType"/> <element name="id" type="maint:idType"/>
</choice> </choice>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Human-readable text may describe the maintenance Human-readable text may describe the maintenance
--> -->
<complexType name="idType"> <complexType name="idType">
<simpleContent> <simpleContent>
<extension base="token"> <extension base="token">
<attribute name="msg" type="token"/> <attribute name="name" type="token"/>
<attribute name="lang" type="language" default="en"/> <attribute name="lang" type="language" default="en"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!--
Info Response element Info Response element
--> -->
<element name="infData" type="maint:infDataType"/> <element name="infData" type="maint:infDataType"/>
<!-- <!--
<info> response elements. <info> response elements.
skipping to change at page 13, line 40 skipping to change at page 14, line 22
<element name="crDate" type="dateTime"/> <element name="crDate" type="dateTime"/>
<element name="upDate" type="dateTime" minOccurs="0"/> <element name="upDate" type="dateTime" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Attributes associated with the maintenance info response Attributes associated with the maintenance info response
--> -->
<complexType name="maintDataType"> <complexType name="maintDataType">
<sequence> <sequence>
<element name="id" type="maint:idType"/> <element name="id" type="maint:idType"/>
<element name="type" type="maint:typeType" minOccurs="0"/>
<element name="pollType" type="maint:pollType" minOccurs="0"/> <element name="pollType" type="maint:pollType" minOccurs="0"/>
<element name="systems" type="maint:systemsType"/> <element name="systems" type="maint:systemsType"/>
<element name="environment" type="maint:envType"/> <element name="environment" type="maint:envType"/>
<element name="start" type="dateTime"/> <element name="start" type="dateTime"/>
<element name="end" type="dateTime"/> <element name="end" type="dateTime"/>
<element name="reason" type="maint:reasonEnum"/> <element name="reason" type="maint:reasonEnum"/>
<element name="detail" type="anyURI" minOccurs="0"/> <element name="detail" type="anyURI" minOccurs="0"/>
<element name="description" type="maint:descriptionType" <element name="description" type="maint:descriptionType"
minOccurs="0"/> minOccurs="0"/>
<element name="tlds" type="maint:tldsType" minOccurs="0"/> <element name="tlds" type="maint:tldsType" minOccurs="0"/>
skipping to change at page 14, line 21 skipping to change at page 15, line 12
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Enumerated list of poll types Enumerated list of poll types
--> -->
<simpleType name="pollType"> <simpleType name="pollType">
<restriction base="token"> <restriction base="token">
<enumeration value="create"/> <enumeration value="create"/>
<enumeration value="update"/> <enumeration value="update"/>
<enumeration value="delete"/> <enumeration value="delete"/>
<enumeration value="courtesy"/>
<enumeration value="end"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
Enumerated list of impacts Enumerated list of impacts
--> -->
<simpleType name="impactEnum"> <simpleType name="impactEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="partial"/> <enumeration value="partial"/>
<enumeration value="full"/> <enumeration value="full"/>
</restriction> </restriction>
skipping to change at page 14, line 43 skipping to change at page 15, line 36
description element description element
--> -->
<complexType name="descriptionType"> <complexType name="descriptionType">
<simpleContent> <simpleContent>
<extension base="string"> <extension base="string">
<attribute name="lang" type="language" default="en"/> <attribute name="lang" type="language" default="en"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!--
type element
-->
<complexType name="typeType">
<simpleContent>
<extension base="string">
<attribute name="lang" type="language" default="en"/>
</extension>
</simpleContent>
</complexType>
<!--
system element system element
--> -->
<complexType name="systemType"> <complexType name="systemType">
<sequence> <sequence>
<element name="name" type="token"/> <element name="name" type="token"/>
<element name="host" type="eppcom:labelType"/> <element name="host" type="eppcom:labelType"/>
<element name="impact" type="maint:impactEnum"/> <element name="impact" type="maint:impactEnum"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
skipping to change at page 16, line 14 skipping to change at page 17, line 19
6. IANA Considerations 6. IANA Considerations
6.1. XML Namespace 6.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism defined in [RFC3688]. conforming to a registry mechanism defined in [RFC3688].
Registration request for the maintenance namespace: Registration request for the maintenance namespace:
URI: urn:ietf:params:xml:ns:epp:maintenance-0.2 URI: urn:ietf:params:xml:ns:epp:maintenance-0.3
Registrant Contact: IESG Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the maintenance schema: Registration request for the maintenance schema:
URI: urn:ietf:params:xml:schema:maintenance-0.2 URI: urn:ietf:params:xml:schema:maintenance-0.3
Registrant Contact: IESG Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
6.2. EPP Extension Registry 6.2. EPP Extension Registry
The following registration of the EPP Extension Registry, described The following registration of the EPP Extension Registry, described
in [RFC7451], is requested: in [RFC7451], is requested:
skipping to change at page 16, line 52 skipping to change at page 18, line 20
TLDs: Any TLDs: Any
IPR Disclosure: None IPR Disclosure: None
Status: Active Status: Active
Notes: None Notes: None
7. Security Considerations 7. Security Considerations
The mapping extensions described in this document do not provide any A server MUST only provide maintenance information for clients that
security services beyond those specified by EPP [RFC5730] and are authorized. If a client queries for a maintenance identifier, per
protocol layers used by EPP. The security considerations described in Section 4.1.3.1 "Info Maintenance Item", that it is not authorized to
these other specifications apply to this specification as well. access, the server MUST return an EPP error result code of 2201
[RFC5730]. The list of top-level domains or registry zones returned
in the "Info Maintenance Item" response SHOULD be filtered based on
the top-level domains or registry zones 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.
8. Implementation Status 8. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
[RFC7942] before publication. [RFC7942] before publication.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC7942]. Internet-Draft, and is based on a proposal described in [RFC7942].
The description of implementations in this section is intended to The description of implementations in this section is intended to
skipping to change at page 18, line 9 skipping to change at page 19, line 24
Licensing: Proprietary Licensing: Proprietary
Contact: quoc@registry.godaddy Contact: quoc@registry.godaddy
URL: https://registry.godaddy URL: https://registry.godaddy
9. References 9. References
9.1. Normative References 9.1. Normative References
[I.D.draft-ietf-regext-unhandled-namespaces]
Gould, J. and Casanova, M., "Extensible Provisioning
Protocol (EPP) Unhandled Namespaces",
<https://datatracker.ietf.org/doc/draft-ietf-regext-
unhandled-namespaces/> (work in progress), December 2020.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[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 18, line 42 skipping to change at page 20, line 11
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References 9.2. Informative References
[I.D.draft-ietf-regext-unhandled-namespaces]
Gould, J. and Casanova, M., "Extensible Provisioning
Protocol (EPP) Unhandled Namespaces",
<https://datatracker.ietf.org/doc/draft-ietf-regext-
unhandled-namespaces/> (work in progress), December 2020.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
Appendix A. Change History Appendix A. Change History
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 draft-sattler-epp-registry-maintenance
Updated to be EPP based instead of JSON document. Updated to be EPP based instead of JSON document.
skipping to change at page 20, line 5 skipping to change at page 21, line 26
Editoral changes. Changed XML namespace and schema from 0.1 to 0.2. Editoral changes. Changed XML namespace and schema from 0.1 to 0.2.
Added pollType to reflect create, update, or delete maintenance poll Added pollType to reflect create, update, or delete maintenance poll
messages. messages.
A.11. Change from 08 to 09 A.11. Change from 08 to 09
Editoral changes. Added new section "Migrating to Newer Versions of Editoral changes. Added new section "Migrating to Newer Versions of
This Extension". This Extension".
A.12. Change from 09 to 10
Editoral changes. Renamed "msg" to "name". Added "courtesy" and "end"
to pollType.
Acknowledgments Acknowledgments
The authors wish to thank the following persons for their feedback The authors wish to thank the following persons for their feedback
and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond
Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig
Marchant, and Andreas Huber. Marchant, and Andreas Huber.
Authors' Addresses Authors' Addresses
Tobias Sattler Tobias Sattler
 End of changes. 30 change blocks. 
63 lines changed or deleted 95 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/