idnits 2.17.1 draft-lozano-rdap-nameservers-sharing-name-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Jun 13, 2018) is 2144 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 7482 (Obsoleted by RFC 9082) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track Jun 13, 2018 5 Expires: December 15, 2018 7 Nameserver objects sharing the same name, support for the Registration 8 Data Access Protocol (RDAP) 9 draft-lozano-rdap-nameservers-sharing-name-02 11 Abstract 13 This document describes a Registration Data Access Protocol (RDAP) 14 extension that may be used to retrieve the registration information 15 of a particular nameserver object sharing the name with other 16 nameserver objects. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on December 15, 2018. 35 Copyright Notice 37 Copyright (c) 2018 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 3. RDAP Conformance object . . . . . . . . . . . . . . . . . . . 2 55 4. Signaling the existence of nameservers sharing the same name 3 56 5. Nameserver search by nameserver name . . . . . . . . . . . . 4 57 6. Nameserver-by-handle path segment specification . . . . . . . 6 58 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 59 8. Change History . . . . . . . . . . . . . . . . . . . . . . . 6 60 8.1. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 6 61 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 62 10. Security Considerations . . . . . . . . . . . . . . . . . . . 7 63 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 64 11.1. Normative References . . . . . . . . . . . . . . . . . . 7 65 11.2. Informative References . . . . . . . . . . . . . . . . . 7 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 68 1. Introduction 70 The RDAP protocol described in RFCs 7480-7484 supports nameserver 71 object lookup based on the name of the nameserver (see section 3.1.4 72 of [RFC7482]), therefore it may not be possible to retrieve the 73 registration information of a particular nameserver object sharing 74 the name with other nameserver objects. 76 This document describes a Registration Data Access Protocol (RDAP) 77 extension that may be used to retrieve the registration information 78 of a particular nameserver object sharing the name with other 79 nameserver objects. 81 This specification is intended to be used by Domain Name Registries 82 (DNRs) that support the coexistence of multiple external hosts (see 83 [RFC5732]) sharing the same name in the repository. 85 2. Terminology 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in [RFC2119]. 91 3. RDAP Conformance object 93 A server that conforms to this specification MUST include the string 94 literal "rdap_nameservers_sharing_name" in the "rdapConformance" 95 member of the topmost JSON object of all responses provided by the 96 server. 98 An example of a rdapConformance data structure including this 99 extension: 101 "rdapConformance" : 102 [ 103 "rdap_level_0", 104 "rdap_nameservers_sharing_name" 105 ] 107 4. Signaling the existence of nameservers sharing the same name 109 A server that conforms to this specification MUST include a "links" 110 member in a nameserver object, if a different nameserver object in 111 the central repository shares the same name. 113 The "links" array MUST include a "rel" of "collection", "type" of 114 "application/rdap+json", and a "href" pointing to a nameserver search 115 method by nameserver name. 117 The following is an example of a nameserver object that includes a 118 links member in order to signal the existence of other nameserver 119 objects sharing the same name. 121 { 122 "objectClassName" : "nameserver", 123 "handle" : "ROID123", 124 "ldhName" : "ns1.foo.test", 125 "status" : [ "active" ], 126 "ipAddresses" : 127 { 128 "v4": [ "192.0.2.1", "192.0.2.2" ], 129 "v6": [ "2001:db8::123" ] 130 }, 131 "links" : 132 [ 133 { 134 "value" : "https://example.com/rdap/nameserver/ns1.foo.test", 135 "rel" : "collection", 136 "href" : "https://example.com/rdap/nameservers?name=ns1.foo.test", 137 "type" : "application/rdap+json" 138 } 139 ], 140 "events" : 141 [ 142 { 143 "eventAction" : "registration", 144 "eventDate" : "1990-12-31T23:59:59Z" 145 }, 146 { 147 "eventAction" : "last changed", 148 "eventDate" : "1991-12-31T23:59:59Z", 149 "eventActor" : "joe@example.com" 150 } 151 ] 152 } 154 5. Nameserver search by nameserver name 156 An RDAP service that conforms to this specification MUST support 157 nameserver search by nameserver name as described in section 3.2.2. 158 of [RFC7482]. 160 The following is an elided example of a response to a 161 /nameservers?name search for a nameserver sharing the name with 162 another nameserver object in the central repository. 164 { 165 "rdapConformance" : 166 [ 167 "rdap_level_0", 168 "rdap_nameservers_sharing_name" 169 ], 170 ... 171 "nameserverSearchResults" : 172 [ 173 { 174 "objectClassName" : "nameserver", 175 "handle" : "ROID123", 176 "ldhName" : "ns1.foo.test", 177 "entities" : 178 [ 179 { 180 "objectClassName" : "entity", 181 "handle" : "Rr1", 182 "roles" : [ "registrar" ], 183 ... 184 }, 185 ... 186 ], 187 ... 188 }, 189 { 190 "objectClassName" : "nameserver", 191 "handle" : "ROID321", 192 "ldhName" : "ns1.foo.test", 193 "entities" : 194 [ 195 { 196 "objectClassName" : "entity", 197 "handle" : "Rr2", 198 "roles" : [ "registrar" ], 199 ... 200 }, 201 ... 202 ], 203 ... 204 } 205 ] 206 } 208 6. Nameserver-by-handle path segment specification 210 A server that conforms to this specification MUST support lookup 211 queries of nameserver objects by the handle of the nameserver using 212 the custom path "nameserver_handle". The custom path 213 "nameserver_handle" adhere to the extensibility mechanism described 214 in Section 5 of [RFC7482]. 216 The appropriated structure for a response to a "nameserver_handle" 217 lookup query is the same as the structure used for a response to a 218 nameserver lookup query defined in section 3.1.4 of [RFC7482]. 220 Syntax: nameserver_handle/ 222 The parameter represents a nameserver identifier whose 223 syntax is specific to the registration provider. 225 The following URL would be used to find information for the 226 nameserver associated with handle ROID123: 228 https://example.com/rdap/nameserver_handle/ROID123 230 7. Acknowledgements 232 TBD. 234 8. Change History 236 [[RFC Editor: Please remove this section.]] 238 8.1. Version 02 240 1. Ping update. 242 9. IANA Considerations 244 The following values have been registered in the IANA RDAP Extensions 245 registry: 247 Extension identifier: rdap_nameservers_sharing_name 248 Registry operator: N/A 249 Specification: draft-lozano-rdap-nameservers-sharing-name 250 Contact: See Author's Address section in the specification 251 Intended Usage: This document describes a Registration Data Access 252 Protocol (RDAP) extension that may be used to retrieve the 253 registration information of a particular nameserver object sharing 254 the name with other nameserver objects. 256 10. Security Considerations 258 The RDAP extension described in this document do not provide any 259 security services beyond those described by RDAP (see RFCs 260 7480-7484), and protocol layers used by RDAP. The security 261 considerations described in these other specifications apply to this 262 specification as well. 264 11. References 266 11.1. Normative References 268 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 269 Requirement Levels", BCP 14, RFC 2119, 270 DOI 10.17487/RFC2119, March 1997, 271 . 273 [RFC7482] Newton, A. and S. Hollenbeck, "Registration Data Access 274 Protocol (RDAP) Query Format", RFC 7482, 275 DOI 10.17487/RFC7482, March 2015, 276 . 278 11.2. Informative References 280 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 281 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 282 August 2009, . 284 Author's Address 286 Gustavo Lozano 287 ICANN 288 12025 Waterfront Drive, Suite 300 289 Los Angeles 90292 290 US 292 Phone: +1.3103015800 293 Email: gustavo.lozano@icann.org