idnits 2.17.1 draft-lozano-rdap-nameservers-sharing-name-03.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 (Dec 17, 2018) is 1956 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 Dec 17, 2018 5 Expires: June 20, 2019 7 Nameserver objects sharing the same name, support for the Registration 8 Data Access Protocol (RDAP) 9 draft-lozano-rdap-nameservers-sharing-name-03 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 June 20, 2019. 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 8.2. Version 03 . . . . . . . . . . . . . . . . . . . . . . . 6 62 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 63 10. Security Considerations . . . . . . . . . . . . . . . . . . . 7 64 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 65 11.1. Normative References . . . . . . . . . . . . . . . . . . 7 66 11.2. Informative References . . . . . . . . . . . . . . . . . 7 67 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 69 1. Introduction 71 The RDAP protocol described in RFCs 7480-7484 supports nameserver 72 object lookup based on the name of the nameserver (see section 3.1.4 73 of [RFC7482]), therefore it may not be possible to retrieve the 74 registration information of a particular nameserver object sharing 75 the name with other nameserver objects. 77 This document describes a Registration Data Access Protocol (RDAP) 78 extension that may be used to retrieve the registration information 79 of a particular nameserver object sharing the name with other 80 nameserver objects. 82 This specification is intended to be used by Domain Name Registries 83 (DNRs) that support the coexistence of multiple external hosts (see 84 [RFC5732]) sharing the same name in the repository. 86 2. Terminology 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in [RFC2119]. 92 3. RDAP Conformance object 94 A server that conforms to this specification MUST include the string 95 literal "rdap_nameservers_sharing_name" in the "rdapConformance" 96 member of the topmost JSON object of all responses provided by the 97 server. 99 An example of a rdapConformance data structure including this 100 extension: 102 "rdapConformance" : 103 [ 104 "rdap_level_0", 105 "rdap_nameservers_sharing_name" 106 ] 108 4. Signaling the existence of nameservers sharing the same name 110 A server that conforms to this specification MUST include a "links" 111 member in a nameserver object, if a different nameserver object in 112 the central repository shares the same name. 114 The "links" array MUST include a "rel" of "collection", "type" of 115 "application/rdap+json", and a "href" pointing to a nameserver search 116 method by nameserver name. 118 The following is an example of a nameserver object that includes a 119 links member in order to signal the existence of other nameserver 120 objects sharing the same name. 122 { 123 "objectClassName" : "nameserver", 124 "handle" : "ROID123", 125 "ldhName" : "ns1.foo.test", 126 "status" : [ "active" ], 127 "ipAddresses" : 128 { 129 "v4": [ "192.0.2.1", "192.0.2.2" ], 130 "v6": [ "2001:db8::123" ] 131 }, 132 "links" : 133 [ 134 { 135 "value" : "https://example.com/rdap/nameserver/ns1.foo.test", 136 "rel" : "collection", 137 "href" : "https://example.com/rdap/nameservers?name=ns1.foo.test", 138 "type" : "application/rdap+json" 139 } 140 ], 141 "events" : 142 [ 143 { 144 "eventAction" : "registration", 145 "eventDate" : "1990-12-31T23:59:59Z" 146 }, 147 { 148 "eventAction" : "last changed", 149 "eventDate" : "1991-12-31T23:59:59Z", 150 "eventActor" : "joe@example.com" 151 } 152 ] 153 } 155 5. Nameserver search by nameserver name 157 An RDAP service that conforms to this specification MUST support 158 nameserver search by nameserver name as described in section 3.2.2. 159 of [RFC7482]. 161 The following is an elided example of a response to a 162 /nameservers?name search for a nameserver sharing the name with 163 another nameserver object in the central repository. 165 { 166 "rdapConformance" : 167 [ 168 "rdap_level_0", 169 "rdap_nameservers_sharing_name" 170 ], 171 ... 172 "nameserverSearchResults" : 173 [ 174 { 175 "objectClassName" : "nameserver", 176 "handle" : "ROID123", 177 "ldhName" : "ns1.foo.test", 178 "entities" : 179 [ 180 { 181 "objectClassName" : "entity", 182 "handle" : "Rr1", 183 "roles" : [ "registrar" ], 184 ... 185 }, 186 ... 187 ], 188 ... 189 }, 190 { 191 "objectClassName" : "nameserver", 192 "handle" : "ROID321", 193 "ldhName" : "ns1.foo.test", 194 "entities" : 195 [ 196 { 197 "objectClassName" : "entity", 198 "handle" : "Rr2", 199 "roles" : [ "registrar" ], 200 ... 201 }, 202 ... 203 ], 204 ... 205 } 206 ] 207 } 209 6. Nameserver-by-handle path segment specification 211 A server that conforms to this specification MUST support lookup 212 queries of nameserver objects by the handle of the nameserver using 213 the custom path "nameserver_handle". The custom path 214 "nameserver_handle" adhere to the extensibility mechanism described 215 in Section 5 of [RFC7482]. 217 The appropriated structure for a response to a "nameserver_handle" 218 lookup query is the same as the structure used for a response to a 219 nameserver lookup query defined in section 3.1.4 of [RFC7482]. 221 Syntax: nameserver_handle/ 223 The parameter represents a nameserver identifier whose 224 syntax is specific to the registration provider. 226 The following URL would be used to find information for the 227 nameserver associated with handle ROID123: 229 https://example.com/rdap/nameserver_handle/ROID123 231 7. Acknowledgements 233 TBD. 235 8. Change History 237 [[RFC Editor: Please remove this section.]] 239 8.1. Version 02 241 1. Ping update. 243 8.2. Version 03 245 1. Ping update. 247 9. IANA Considerations 249 The following values have been registered in the IANA RDAP Extensions 250 registry: 252 Extension identifier: rdap_nameservers_sharing_name 253 Registry operator: N/A 254 Specification: draft-lozano-rdap-nameservers-sharing-name 255 Contact: See Author's Address section in the specification 256 Intended Usage: This document describes a Registration Data Access 257 Protocol (RDAP) extension that may be used to retrieve the 258 registration information of a particular nameserver object sharing 259 the name with other nameserver objects. 261 10. Security Considerations 263 The RDAP extension described in this document do not provide any 264 security services beyond those described by RDAP (see RFCs 265 7480-7484), and protocol layers used by RDAP. The security 266 considerations described in these other specifications apply to this 267 specification as well. 269 11. References 271 11.1. Normative References 273 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 274 Requirement Levels", BCP 14, RFC 2119, 275 DOI 10.17487/RFC2119, March 1997, 276 . 278 [RFC7482] Newton, A. and S. Hollenbeck, "Registration Data Access 279 Protocol (RDAP) Query Format", RFC 7482, 280 DOI 10.17487/RFC7482, March 2015, 281 . 283 11.2. Informative References 285 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 286 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 287 August 2009, . 289 Author's Address 291 Gustavo Lozano 292 ICANN 293 12025 Waterfront Drive, Suite 300 294 Los Angeles 90292 295 US 297 Phone: +1.3103015800 298 Email: gustavo.lozano@icann.org