draft-ietf-regext-epp-rdap-status-mapping-00.txt   draft-ietf-regext-epp-rdap-status-mapping-01.txt 
Network Working Group J. Gould Network Working Group J. Gould
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Informational June 10, 2016 Intended status: Standards Track July 5, 2016
Expires: December 12, 2016 Expires: January 6, 2017
Extensible Provisioning Protocol (EPP) and Registration Data Access Extensible Provisioning Protocol (EPP) and Registration Data Access
Protocol (RDAP) Status Mapping Protocol (RDAP) Status Mapping
draft-ietf-regext-epp-rdap-status-mapping-00 draft-ietf-regext-epp-rdap-status-mapping-01
Abstract Abstract
This document describes the mapping of the Extensible Provisioning This document describes the mapping of the Extensible Provisioning
Protocol (EPP) statuses with the statuses registered for use in the Protocol (EPP) statuses with the statuses registered for use in the
Registration Data Access Protocol (RDAP). This document identifies Registration Data Access Protocol (RDAP). This document identifies
gaps in the mapping, and registers RDAP statuses to fill the gaps to gaps in the mapping, and registers RDAP statuses to fill the gaps to
ensure that all of the EPP RFC statuses are supported in RDAP. ensure that all of the EPP RFC statuses are supported in RDAP.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 December 12, 2016. This Internet-Draft will expire on January 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 2 1.1. Conventions Used in This Document . . . . . . . . . . . . 2
2. EPP to RDAP Status Mapping . . . . . . . . . . . . . . . . . 3 2. EPP to RDAP Status Mapping . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
3.1. JSON Values Registry . . . . . . . . . . . . . . . . . . 5 3.1. JSON Values Registry . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. Normative References . . . . . . . . . . . . . . . . . . . . 9 5. Normative References . . . . . . . . . . . . . . . . . . . . 9
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 10 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 10
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 10 Appendix B. Change History . . . . . . . . . . . . . . . . . . . 10
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 10 B.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 10
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10 B.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 10
A.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 10 B.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 B.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 11
B.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
This document maps the statuses defined in the Extensible This document maps the statuses defined in the Extensible
Provisioning Protocol (EPP) RFCs to the list of statuses registered Provisioning Protocol (EPP) RFCs to the list of statuses registered
for use in the Registration Data Access Protocol (RDAP), in the RDAP for use in the Registration Data Access Protocol (RDAP), in the RDAP
JSON Values Registry [rdap-json-values]. JSON Values Registry [rdap-json-values].
The RDAP JSON Values Registry is described in section 10.2 of The RDAP JSON Values Registry is described in section 10.2 of
[RFC7483] and is available in the RDAP JSON Values Registry [RFC7483] and is available in the RDAP JSON Values Registry
skipping to change at page 6, line 8 skipping to change at page 6, line 8
The following values should be registered by the IANA in the RDAP The following values should be registered by the IANA in the RDAP
JSON Values Registry described in [RFC7483]: JSON Values Registry described in [RFC7483]:
Value: add period Value: add period
Type: status Type: status
Description: For DNR that indicates if the object is deleted by the Description: For DNR that indicates if the object is deleted by the
registrar during this period, the registry provides a credit to the registrar during this period, the registry provides a credit to the
registrar for the cost of the registration. registrar for the cost of the registration.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: auto renew period Value: auto renew period
Type: status Type: status
Description: For DNR that indicates if the object is deleted by the Description: For DNR that indicates if the object is deleted by the
registrar during this period, the registry provides a credit to the registrar during this period, the registry provides a credit to the
registrar for the cost of the auto renewal. registrar for the cost of the auto renewal.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: client delete prohibited Value: client delete prohibited
Type: status Type: status
Description: For DNR that indicates the client requested that Description: For DNR that indicates the client requested that
requests to delete the object MUST be rejected. requests to delete the object MUST be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: client hold Value: client hold
Type: status Type: status
Description: For DNR that indicates the client requested that the DNS Description: For DNR that indicates the client requested that the DNS
delegation information MUST NOT be published for the object. delegation information MUST NOT be published for the object.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: client renew prohibited Value: client renew prohibited
Type: status Type: status
Description: For DNR that indicates the client requested that Description: For DNR that indicates the client requested that
requests to renew the object MUST be rejected. requests to renew the object MUST be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: client transfer prohibited Value: client transfer prohibited
Type: status Type: status
Description: For DNR that indicates the client requested that Description: For DNR that indicates the client requested that
requests to transfer the object MUST be rejected. requests to transfer the object MUST be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: client update prohibited Value: client update prohibited
Type: status Type: status
Description: For DNR that indicates the client requested that Description: For DNR that indicates the client requested that
requests to update the object (other than to remove this status) MUST requests to update the object (other than to remove this status) MUST
be rejected. be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: pending restore Value: pending restore
Type: status Type: status
Description: For DNR that indicates a object is in the process of Description: For DNR that indicates a object is in the process of
being restored after being in the redemptionPeriod state. being restored after being in the redemptionPeriod state.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: redemption period Value: redemption period
Type: status Type: status
Description: For DNR that indicates a delete has been received, but Description: For DNR that indicates a delete has been received, but
the object has not yet been purged because an opportunity exists to the object has not yet been purged because an opportunity exists to
restore the object and abort the deletion process. restore the object and abort the deletion process.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: iesg@ietf.org
Registrant Contact Information: epp-registry@verisign.com
Value: renew period Value: renew period
Type: status Type: status
Description: For DNR that indicates if the object is deleted by the Description: For DNR that indicates if the object is deleted by the
registrar during this period, the registry provides a credit to the registrar during this period, the registry provides a credit to the
registrar for the cost of the renewal. registrar for the cost of the renewal.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: server delete prohibited Value: server delete prohibited
Type: status Type: status
Description: For DNR that indicates the server set the status so that Description: For DNR that indicates the server set the status so that
requests to delete the object MUST be rejected. requests to delete the object MUST be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: server renew prohibited Value: server renew prohibited
Type: status Type: status
Description: For DNR that indicates the server set the status so that Description: For DNR that indicates the server set the status so that
requests to renew the object MUST be rejected. requests to renew the object MUST be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: server transfer prohibited Value: server transfer prohibited
Type: status Type: status
Description: For DNR that indicates the server set the status so that Description: For DNR that indicates the server set the status so that
requests to transfer the object MUST be rejected. requests to transfer the object MUST be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: server update prohibited Value: server update prohibited
Type: status Type: status
Description: For DNR that indicates the server set the status so that Description: For DNR that indicates the server set the status so that
requests to update the object (other than to remove this status) MUST requests to update the object (other than to remove this status) MUST
be rejected. be rejected.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: server hold Value: server hold
Type: status Type: status
Description: For DNR that indicates the server set the status so that Description: For DNR that indicates the server set the status so that
DNS delegation information MUST NOT be published for the object. DNS delegation information MUST NOT be published for the object.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
Value: transfer period Value: transfer period
Type: status Type: status
Description: For DNR that indicates if the domain name is deleted by Description: For DNR that indicates if the domain name is deleted by
the registrar during this period, the registry provides a credit to the registrar during this period, the registry provides a credit to
the registrar for the cost of the transfer. the registrar for the cost of the transfer.
Registrant Name: VeriSign Inc. Registrant Name: IESG
Registrant Contact Information: epp-registry@verisign.com Registrant Contact Information: iesg@ietf.org
4. Security Considerations 4. Security Considerations
The mapping described in this document do not provide any security The status values described in this document can be subject to
services beyond those described by RDAP [RFC7483]. server-side information disclosure policies that restrict display of
the values to authorized clients. Implementers may wish to review
[RFC7481] for a description of the RDAP security services that can be
used to implement information disclosure policies.
5. Normative References 5. 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.
[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
the Extensible Provisioning Protocol (EPP)", RFC 3915, the Extensible Provisioning Protocol (EPP)", RFC 3915,
September 2004. September 2004.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, August 2009. Domain Name Mapping", STD 69, RFC 5731, August 2009.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, August 2009. Host Mapping", STD 69, RFC 5732, August 2009.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, August 2009. Contact Mapping", STD 69, RFC 5733, August 2009.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the
Registration Data Access Protocol (RDAP)", RFC 7481, DOI
10.17487/RFC7481, March 2015,
<http://www.rfc-editor.org/info/rfc7481>.
[RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the [RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", RFC 7483, March Registration Data Access Protocol (RDAP)", RFC 7483, March
2015. 2015.
[rdap-json-values] [rdap-json-values]
"RDAP JSON Values Registry", "RDAP JSON Values Registry",
<https://www.iana.org/assignments/rdap-json-values/rdap- <https://www.iana.org/assignments/rdap-json-values/rdap-
json-values.xhtml>. json-values.xhtml>.
Appendix A. Change History Appendix A. Acknowledgements
A.1. Change from 00 to 01 Suggestions that have been incorporated into this document were
provided by Andrew Newton, Scott Hollenbeck, Jim Galvin, and Gustavo
Lozano.
Appendix B. Change History
B.1. Change from 00 to 01
1. Changed the mapping of "linked" to "associated" and removed the 1. Changed the mapping of "linked" to "associated" and removed the
registration of "linked", based on feedback from Andrew Newton on registration of "linked", based on feedback from Andrew Newton on
the weirds mailing list. the weirds mailing list.
A.2. Change from 01 to 02 B.2. Change from 01 to 02
1. Ping update. 1. Ping update.
A.3. Change from 02 to 03 B.3. Change from 02 to 03
1. Ping update. 1. Ping update.
A.4. Change from 03 to REGEXT 00 B.4. Change from 03 to REGEXT 00
1. Changed to regext working group draft by changing draft-gould- 1. Changed to regext working group draft by changing draft-gould-
epp-rdap-status-mapping to draft-ietf-regext-epp-rdap-status- epp-rdap-status-mapping to draft-ietf-regext-epp-rdap-status-
mapping. mapping.
B.5. Change from REGEXT 00 to REGEXT 01
1. Updated based on regext mailing feedback from Scott Hollenbeck
that included updating the registrant for the registration of the
new statuses to IESG and iesg@ietf.org, and revising the security
section. Changed to standards track based on suggestion by Jim
Galvin and support from Gustavo Lozano on the regext mailing
list.
Author's Address Author's Address
James Gould James Gould
VeriSign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US US
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisigninc.com URI: http://www.verisigninc.com
 End of changes. 44 change blocks. 
50 lines changed or deleted 75 lines changed or added

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