draft-sattler-epp-registry-maintenance-03.txt   draft-sattler-epp-registry-maintenance-04.txt 
Internet Engineering Task Force T. Sattler Internet Engineering Task Force T. Sattler
Internet-Draft March 18, 2018 Internet-Draft March 23, 2018
Intended status: Standard Track Intended status: Standard Track
Expires: September 17, 2018 Expires: September 22, 2018
Registry Maintenance Notifications for the Registry Maintenance Notifications for the
Extensible Provisioning Protocol (EPP) Extensible Provisioning Protocol (EPP)
draft-sattler-epp-registry-maintenance-03 draft-sattler-epp-registry-maintenance-04
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 17, 2018. This Internet-Draft will expire on September 22, 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 44 skipping to change at page 2, line 44
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18
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
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 20 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.
skipping to change at page 4, line 20 skipping to change at page 4, line 20
For creating a new maintenance the attribute <maint:status> MUST be For creating a new maintenance the attribute <maint:status> MUST be
'active', the attribute <maint:crDate> MUST be set and the attribute 'active', the attribute <maint:crDate> MUST be set and the attribute
<maint:upDate> SHALL NOT be present. <maint:upDate> SHALL NOT be present.
For updating a maintenance the attribute <maint:status> MUST be For updating a maintenance the attribute <maint:status> MUST be
'active', the attributes <maint:crDate> and <maint:upDate> MUST be 'active', the attributes <maint:crDate> and <maint:upDate> MUST be
set. set.
For deleting a maintenance the attribute <maint:status> MUST be For deleting a maintenance the attribute <maint:status> MUST be
'inactive' the attributes <maint:crDate> and <maint:upDate> MUST be 'inactive', and the attributes <maint:crDate> and <maint:upDate> MUST
set. be set.
<maint:id> <maint:id>
MUST be present and an UUID according [RFC4122], SHALL NOT be MUST be present and an UUID according [RFC4122] and SHALL NOT be
changed if maintenance got updated or deleted. A human-readable changed if maintenance got updated or deleted. A human-readable
description of the maintenance is identified via an OPTIONAL description of the maintenance is identified via an OPTIONAL
"msg" attribute. "msg" attribute.
<maint:systems> <maint:systems>
MUST be present and contains one or more <maint:system> elements. MUST be present and contains one or more <maint:system> elements.
The server SHOULD NOT list systems which are not affected by the The server SHOULD NOT list systems which are not affected by the
maintenance. maintenance.
<maint:system> <maint:system>
skipping to change at page 5, line 34 skipping to change at page 5, line 34
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
<maint:description> <maint:description>
MAY be present and provides a freeform description of the MAY be present and provides a freeform description of the
maintenance without having to create and traverse an external maintenance without having to create and traverse an external
resource. The maximum length SHOULD NOT exceed 1024 bit. resource. The maximum length MUST NOT exceed 1024 bit.
<maint:tlds> <maint:tlds>
MUST be present and contains <maint:tld> elements MUST be present and contains <maint:tld> elements
<maint:tld> <maint:tld>
MUST be present and contains the affected top-level domain. MUST be present and contains the affected top-level domain.
Punycode encoded according [RFC5891] Punycode encoded according [RFC5891]
<maint:intervention> <maint:intervention>
MUST be present and contains <maint:connection> and MUST be present and contains <maint:connection> and
<maint:implementation> <maint:implementation>
<maint:connection> <maint:connection>
MUST be present and indicates if a client needs to do something MUST be present and indicates if a client needs to do something
that is connection related, such as a reconnect. The value that is connection related, such as a reconnect. The value
SHALL boolean. SHALL boolean.
<maint:implementation> <maint:implementation>
MUST be present and indicates if a client needs to do something MUST be present and indicates if a client needs to do something
that is implementation related, such as a code changes. The that is implementation related, such as a code change. The
value SHALL be boolean. value SHALL be boolean.
<maint:status> <maint:status>
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
skipping to change at page 19, line 36 skipping to change at page 19, line 36
Fixed typos and added missing change log text for EPPMAINT 00. Fixed typos and added missing change log text for EPPMAINT 00.
Added BEGIN and END flag to XML schema. Removed Character Encoding Added BEGIN and END flag to XML schema. Removed Character Encoding
Section. Fixed indentation in Section 2.3. Section. Fixed indentation in Section 2.3.
A.10. Change from EPPMAINT 01 to EPPMAINT 02 A.10. Change from EPPMAINT 01 to EPPMAINT 02
Changed the element <maint:remark> to <maint:detail>. Fixed Changed the element <maint:remark> to <maint:detail>. Fixed
indentation in Section 4.1. Cleaned up whitespaces. indentation in Section 4.1. Cleaned up whitespaces.
A.11. Change from EPPMAINT 02 to EPPMAINT03 A.11. Change from EPPMAINT 02 to EPPMAINT 03
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
Fixed minor typos and added one acknowledgement.
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
* 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
* Patrick Mevzek of Uniregistry * Patrick Mevzek of Uniregistry
* Andreas Huber of united-domains * Andreas Huber of united-domains
* Craig Marchant of VentraIP * Craig Marchant of VentraIP
* James Gould of Verisign * James Gould of Verisign
Author's Address Author's Address
 End of changes. 12 change blocks. 
10 lines changed or deleted 16 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/