draft-sattler-epp-registry-maintenance-04.txt   draft-sattler-epp-registry-maintenance-05.txt 
Internet Engineering Task Force T. Sattler Internet Engineering Task Force T. Sattler
Internet-Draft March 23, 2018 Internet-Draft March 29, 2018
Intended status: Standard Track Intended status: Standard Track
Expires: September 22, 2018 Expires: September 28, 2018
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-sattler-epp-registry-maintenance-04 draft-sattler-epp-registry-maintenance-05
Abstract Abstract
This document describes an Extensible Provision Protocol (EPP) This document describes an Extensible Provision Protocol (EPP)
mapping for the Registry Maintenance Notifications used when Domain mapping for the Registry Maintenance Notifications used when Domain
Name Registries will conduct a maintenance, and for retrieving these Name Registries will conduct a maintenance, and for retrieving these
information. information.
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.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
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 September 22, 2018. This Internet-Draft will expire on September 28, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 2, line 45 skipping to change at page 2, line 45
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 18 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 18
A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19
A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19
A.8. Change from 07 to EPPMAINT 00 . . . . . . . . . . . . . . 19 A.8. Change from 07 to EPPMAINT 00 . . . . . . . . . . . . . . 19
A.9. Change from EPPMAINT 00 to EPPMAINT 01 . . . . . . . . . 19 A.9. Change from EPPMAINT 00 to EPPMAINT 01 . . . . . . . . . 19
A.10. Change from EPPMAINT 01 to EPPMAINT 02 . . . . . . . . . 19 A.10. Change from EPPMAINT 01 to EPPMAINT 02 . . . . . . . . . 19
A.11. Change from EPPMAINT 02 to EPPMAINT 03 . . . . . . . . . 19 A.11. Change from EPPMAINT 02 to EPPMAINT 03 . . . . . . . . . 19
A.12. Change from EPPMAINT 03 to EPPMAINT 04 . . . . . . . . . 19 A.12. Change from EPPMAINT 03 to EPPMAINT 04 . . . . . . . . . 19
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 20 A.13. Change from EPPMAINT 04 to EPPMAINT 05 . . . . . . . . . 19
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 20 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This document describes an Extensible Provision Protocol (EPP) This document describes an Extensible Provision Protocol (EPP)
[RFC5730] mapping for the Registry Maintenance Notifications used [RFC5730] mapping for the Registry Maintenance Notifications used
when Domain Name Registries will conduct a maintenance, and for when Domain Name Registries will conduct a maintenance, and for
retrieving these information. retrieving these information.
1.1. Terminology and Definitions 1.1. Terminology and Definitions
skipping to change at page 5, line 20 skipping to change at page 5, line 20
MUST be present and indicates the type of the affected system; MUST be present and indicates the type of the affected system;
values SHOULD either be 'production', 'ote', 'staging' or 'dev' values SHOULD either be 'production', 'ote', 'staging' or 'dev'
<maint:start> <maint:start>
MUST be present and indicates the start of the maintenance MUST be present and indicates the start of the maintenance
according ISO 8601 [RFC3339] according ISO 8601 [RFC3339]
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
<maint:end> <maint:end>
MUST be present and indicates the end of the maintenance MUST be present and indicates the end of the maintenance
according ISO 8601 [RFC3339] according ISO 8601 [RFC3339], and MUST be equal to or greater
than <maint:start>
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
<maint:reason> <maint:reason>
MUST be present and contains the reason behind the maintenance; MUST be present and contains the reason behind the maintenance;
values SHOULD either be 'planned' or 'emergency' values SHOULD either be 'planned' or 'emergency'
<maint:detail> <maint:detail>
MAY be present and contains URI to detailed maintenance MAY be present and contains URI to detailed maintenance
description description
skipping to change at page 6, line 16 skipping to change at page 6, line 16
MUST be present and indicates the status of the maintenance. MUST be present and indicates the status of the maintenance.
The value SHALL be either 'active' or 'inactive' The value SHALL be either 'active' or 'inactive'
<maint:crDate> <maint:crDate>
MUST be present and contains the creation date of the maintenance MUST be present and contains the creation date of the maintenance
according ISO 8601 [RFC3339] according ISO 8601 [RFC3339]
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
<maint:upDate> <maint:upDate>
MAY be present and contains the updated date of the maintenance MAY be present and contains the updated date of the maintenance
according ISO 8601 [RFC3339]. according ISO 8601 [RFC3339], and if set MUST be equal to or
greater than <main:crDate>
Format: YYYY-MM-DDThh:mm:ssTZ Format: YYYY-MM-DDThh:mm:ssTZ
3. EPP Command Mapping 3. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. The command in the EPP core protocol specification [RFC5730]. The command
mappings described here are specifically for the use to notify of mappings described here are specifically for the use to notify of
Registry Maintenances and Registry Maintenance object mapping. Registry Maintenances and Registry Maintenance object mapping.
3.1. EPP Query Commands 3.1. EPP Query Commands
skipping to change at page 7, line 43 skipping to change at page 7, line 43
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</maint:host> S: <maint:host>epp.registry.example</maint:host>
S: <maint:impact>blackout</maint:impact> S: <maint:impact>blackout</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-04-30T06:00:00Z</maint:start> S: <maint:start>2017-09-30T06:00:00Z</maint:start>
S: <maint:end>2013-10-22T14:25:57Z</maint:end> S: <maint:end>2017-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>free text</maint:description> S: <maint:description>free text</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:status>active</maint:status> S: <maint:status>active</maint:status>
S: <maint:crDate>2017-02-08T22:10:00Z</maint:crDate> S: <maint:crDate>2017-03-08T22:10:00Z</maint:crDate>
S: </maint:maint> S: </maint:maint>
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 40 skipping to change at page 10, line 40
S: <maint:maint> S: <maint:maint>
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</maint:host> S: <maint:host>epp.registry.example</maint:host>
S: <maint:impact>blackout</maint:impact> S: <maint:impact>blackout</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-04-30T06:00:00Z</maint:start> S: <maint:start>2017-10-30T06:00:00Z</maint:start>
S: <maint:end>2013-10-22T14:25:57Z</maint:end> S: <maint:end>2017-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>
skipping to change at page 20, line 5 skipping to change at page 19, line 47
Changed reference from RFC3492 to RFC5891. Fixed minor typos. Changed reference from RFC3492 to RFC5891. Fixed minor typos.
Added <maint:description> for a freeform maintenance description Added <maint:description> for a freeform maintenance description
with a maximum length of 1024. Added optional "msg" attribute to with a maximum length of 1024. Added optional "msg" attribute to
<maint:id> and <maint:maint>. <maint:id> and <maint:maint>.
A.12. Change from EPPMAINT 03 to EPPMAINT 04 A.12. Change from EPPMAINT 03 to EPPMAINT 04
Fixed minor typos and added one acknowledgement. Fixed minor typos and added one acknowledgement.
A.13. Change from EPPMAINT 04 to EPPMAINT 05
Added missing whitespace. Fixed dates in examples. Added
clarification that <maint:end> must be equal to or greater than
<maint:start>, same applies for <maint:upDate> and <maint:crDate> if
set.
Appendix B. Acknowledgements Appendix B. Acknowledgements
The author wishes to thank the following persons for their feedback The author wishes to thank the following persons for their feedback
and suggestions (sorted alphabetically by company): and suggestions (sorted alphabetically by company):
* Neal McPherson of 1&1 Internet * Neal McPherson of 1&1 Internet
* Anthony Eden of DNSimple * Anthony Eden of DNSimple
* Christopher Martens of Donuts * Christopher Martens of Donuts
* Jody Kolker and Roger Carney of GoDaddy * Jody Kolker and Roger Carney of GoDaddy
* Raymond Zylstra of Neustar * Raymond Zylstra of Neustar
 End of changes. 11 change blocks. 
12 lines changed or deleted 22 lines changed or added

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