Internet Engineering Task Force G. Lozano Internet-Draft ICANN Intended status: Standards Track April 22, 2016 Expires: October 24, 2016 Nameserver objects sharing the same name, support for the Registration Data Access Protocol (RDAP) draft-lozano-rdap-nameservers-sharing-name-01 Abstract This document describes a Registration Data Access Protocol (RDAP) extension that may be used to retrieve the registration information of a particular nameserver object sharing the name with other nameserver objects. 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 October 24, 2016. Copyright Notice Copyright (c) 2016 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 October 24, 2016 [Page 1] Internet-Draft rdap-nameservers-sharing-name April 2016 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. RDAP Conformance object . . . . . . . . . . . . . . . . . . . 2 4. Signaling the existence of nameservers sharing the same name 3 5. Nameserver search by nameserver name . . . . . . . . . . . . 4 6. Nameserver-by-handle path segment specification . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction The RDAP protocol described in RFCs 7480-7484 supports nameserver object lookup based on the name of the nameserver (see section 3.1.4 of [RFC7482]), therefore it may not be possible to retrieve the registration information of a particular nameserver object sharing the name with other nameserver objects. This document describes a Registration Data Access Protocol (RDAP) extension that may be used to retrieve the registration information of a particular nameserver object sharing the name with other nameserver objects. This specification is intended to be used by Domain Name Registries (DNRs) that support the coexistence of multiple external hosts (see [RFC5732]) sharing the same name in the repository. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. RDAP Conformance object A server that conforms to this specification MUST include the string literal "rdap_nameservers_sharing_name" in the "rdapConformance" member of the topmost JSON object of all responses provided by the server. An example of a rdapConformance data structure including this extension: Lozano Expires October 24, 2016 [Page 2] Internet-Draft rdap-nameservers-sharing-name April 2016 "rdapConformance" : [ "rdap_level_0", "rdap_nameservers_sharing_name" ] 4. Signaling the existence of nameservers sharing the same name A server that conforms to this specification MUST include a "links" member in a nameserver object, if a different nameserver object in the central repository shares the same name. The "links" array MUST include a "rel" of "collection", "type" of "application/rdap+json", and a "href" pointing to a nameserver search method by nameserver name. The following is an example of a nameserver object that includes a links member in order to signal the existence of other nameserver objects sharing the same name. Lozano Expires October 24, 2016 [Page 3] Internet-Draft rdap-nameservers-sharing-name April 2016 { "objectClassName" : "nameserver", "handle" : "ROID123", "ldhName" : "ns1.foo.test", "status" : [ "active" ], "ipAddresses" : { "v4": [ "192.0.2.1", "192.0.2.2" ], "v6": [ "2001:db8::123" ] }, "links" : [ { "value" : "https://example.com/rdap/nameserver/ns1.foo.test", "rel" : "collection", "href" : "https://example.com/rdap/nameservers?name=ns1.foo.test", "type" : "application/rdap+json" } ], "events" : [ { "eventAction" : "registration", "eventDate" : "1990-12-31T23:59:59Z" }, { "eventAction" : "last changed", "eventDate" : "1991-12-31T23:59:59Z", "eventActor" : "joe@example.com" } ] } 5. Nameserver search by nameserver name An RDAP service that conforms to this specification MUST support nameserver search by nameserver name as described in section 3.2.2. of [RFC7482]. The following is an elided example of a response to a /nameservers?name search for a nameserver sharing the name with another nameserver object in the central repository. Lozano Expires October 24, 2016 [Page 4] Internet-Draft rdap-nameservers-sharing-name April 2016 { "rdapConformance" : [ "rdap_level_0", "rdap_nameservers_sharing_name" ], ... "nameserverSearchResults" : [ { "objectClassName" : "nameserver", "handle" : "ROID123", "ldhName" : "ns1.foo.test", "entities" : [ { "objectClassName" : "entity", "handle" : "Rr1", "roles" : [ "registrar" ], ... }, ... ], ... }, { "objectClassName" : "nameserver", "handle" : "ROID321", "ldhName" : "ns1.foo.test", "entities" : [ { "objectClassName" : "entity", "handle" : "Rr2", "roles" : [ "registrar" ], ... }, ... ], ... } ] } Lozano Expires October 24, 2016 [Page 5] Internet-Draft rdap-nameservers-sharing-name April 2016 6. Nameserver-by-handle path segment specification A server that conforms to this specification MUST support lookup queries of nameserver objects by the handle of the nameserver using the custom path "nameserver_handle". The custom path "nameserver_handle" adhere to the extensibility mechanism described in Section 5 of [RFC7482]. The appropriated structure for a response to a "nameserver_handle" lookup query is the same as the structure used for a response to a nameserver lookup query defined in section 3.1.4 of [RFC7482]. Syntax: nameserver_handle/ The parameter represents a nameserver identifier whose syntax is specific to the registration provider. The following URL would be used to find information for the nameserver associated with handle ROID123: https://example.com/rdap/nameserver_handle/ROID123 7. Acknowledgements TBD. 8. IANA Considerations The following values have been registered in the IANA RDAP Extensions registry: Extension identifier: rdap_nameservers_sharing_name Registry operator: N/A Specification: draft-lozano-rdap-nameservers-sharing-name Contact: See Author's Address section in the specification Intended Usage: This document describes a Registration Data Access Protocol (RDAP) extension that may be used to retrieve the registration information of a particular nameserver object sharing the name with other nameserver objects. 9. Security Considerations The RDAP extension described in this document do not provide any security services beyond those described by RDAP (see RFCs 7480-7484), and protocol layers used by RDAP. The security considerations described in these other specifications apply to this specification as well. Lozano Expires October 24, 2016 [Page 6] Internet-Draft rdap-nameservers-sharing-name April 2016 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC7482] Newton, A. and S. Hollenbeck, "Registration Data Access Protocol (RDAP) Query Format", RFC 7482, DOI 10.17487/RFC7482, March 2015, . 10.2. Informative References [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, August 2009, . 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 October 24, 2016 [Page 7]