Internet DRAFT - draft-lozano-rdap-gtld-whois-additional-events
draft-lozano-rdap-gtld-whois-additional-events
Internet Engineering Task Force G. Lozano
Internet-Draft ICANN
Intended status: Informational October 04, 2015
Expires: April 6, 2016
Additional RDAP events to support the gTLD Whois output
draft-lozano-rdap-gtld-whois-additional-events-00
Abstract
This document adds two event action types to the IANA RDAP JSON
Values registry, defined in [RFC7483], which are required to map two
fields from the gTLD Whois output into the RDAP response.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 6, 2016.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Lozano Expires April 6, 2016 [Page 1]
Internet-Draft RDAP events for gTLD Whois October 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Event Actions registration . . . . . . . . . . . . . . . . . 3
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
6.1. Normative References . . . . . . . . . . . . . . . . . . 3
6.2. Informative References . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
Generic TLDs (gTLDs) Domain Name Registries and Registrars operating
according to an agreement with the Internet Corporation for Assigned
Names and Numbers (ICANN), which includes a clause to implement a
successor protocol to WHOIS [RFC3912], are required to deploy the
Registration Data Access Protocol (RDAP) described in RFCs 7480-7484.
Registries and registrars are required to provide at least the same
fields as in the Whois service.
Registrars operating according to the ICANN Registrar Accreditation
Agreement 2013 (see [RAA2013] are required to provide the "Registrar
Registration Expiration Date" that shows the expiration date of the
domain name within the registrar system. There is no event action
defined in the RDAP base RFCs that could be used to map this field.
Registries and registrars regularly use a database (i.e. RDDS
database) synchronized from the Shared Registry System (SRS) database
to provide the Registration Data Directory Services (e.g. WHOIS and
RDAP). Registries operating according to an ICANN Base Registry
Agreement (see [Base_RA]), Registrars operating under the ICANN
Registrar Accreditation Agreement 2013 (see [RAA2013], and Registries
operating according to other ICANN Registry Agreements are required
to provide the date and time that the object instance in the RDDS
database was last synchronized from the SRS database. There is no
event action defined in the RDAP base RFCs that could be used to map
this field.
This document adds two event action types to the IANA RDAP JSON
Values registry, defined in [RFC7483], which are required to map two
fields from the gTLD Whois output into the RDAP response.
Lozano Expires April 6, 2016 [Page 2]
Internet-Draft RDAP events for gTLD Whois October 2015
2. Event Actions registration
The following values have been registered in the IANA RDAP JSON
Values registry:
Value: last update of RDAP database
Type: event action
Description: An action noting when the information in the object
instance in the RDAP database was last synchronized from the
authoritative database (e.g. registry database).
Registrant Name: ICANN
Registrant Contact Information: tech-services@icann.org
Value: registrar expiration
Type: event action
Description: An action noting the expiration date of the object in
the registrar system.
Registrant Name: ICANN
Registrant Contact Information: tech-services@icann.org
3. Acknowledgements
TBD.
4. IANA Considerations
This document adds two event action types to the IANA RDAP JSON
Values registry, the description of the event types can be found in
Section 2.
5. Security Considerations
This document adds two event action types to the IANA RDAP JSON
Values registry. No additional security considerations are required.
6. References
6.1. Normative References
[RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", RFC 7483,
DOI 10.17487/RFC7483, March 2015,
<http://www.rfc-editor.org/info/rfc7483>.
Lozano Expires April 6, 2016 [Page 3]
Internet-Draft RDAP events for gTLD Whois October 2015
6.2. Informative References
[Base_RA] ICANN, "Base Registry Agreement", January 2014,
<http://newgtlds.icann.org/sites/default/files/agreements/
agreement-approved-09jan14-en.pdf>.
[RAA2013] ICANN, "2013 Registrar Accreditation Agreement", September
2013, <https://www.icann.org/resources/pages/approved-
with-specs-2013-09-17-en>.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
DOI 10.17487/RFC3912, September 2004,
<http://www.rfc-editor.org/info/rfc3912>.
Author's Address
Gustavo Lozano
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles 90292
US
Phone: +1.3103015800
Email: gustavo.lozano@icann.org
Lozano Expires April 6, 2016 [Page 4]
