idnits 2.17.1 draft-blanchet-weirds-bootstrap-ianaregistries-00.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 : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 161: '...stries. Clients SHOULD not fetch ever...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: This method relies on the fact that RDAP clients are fetching the IANA XML registries. Clients SHOULD not fetch every time the XML files. Clients should rely on HTTP headers to verify if the registry has changed since last time it was fetched. -- The document date (June 05, 2013) is 3970 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-14) exists of draft-ietf-weirds-json-response-03 == Outdated reference: A later version (-18) exists of draft-ietf-weirds-rdap-query-04 == Outdated reference: A later version (-15) exists of draft-ietf-weirds-using-http-05 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Blanchet 3 Internet-Draft Viagenie 4 Intended status: Informational June 05, 2013 5 Expires: December 07, 2013 7 Finding the Authoritative Registration Data (RDAP) Service 8 draft-blanchet-weirds-bootstrap-ianaregistries-00.txt 10 Abstract 12 This document specifies a method to find which Registration Data 13 Access Protocol (RDAP) server is authoritative to answer queries for 14 a requested scope, such as domain names, IP addresses or Autonomous 15 System numbers, using data available in IANA registries. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on December 07, 2013. 34 Copyright Notice 36 Copyright (c) 2013 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Domain Name Registry . . . . . . . . . . . . . . . . . . . . 2 53 3. Internet Numbers Registry . . . . . . . . . . . . . . . . . . 3 54 3.1. IPv4 Address Space . . . . . . . . . . . . . . . . . . . 3 55 3.2. IPv6 Address Space . . . . . . . . . . . . . . . . . . . 3 56 3.3. Autonomous Systems . . . . . . . . . . . . . . . . . . . 3 57 4. Nameserver . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 4 60 7. Deployment Considerations . . . . . . . . . . . . . . . . . . 4 61 8. Security Considerations . . . . . . . . . . . . . . . . . . . 4 62 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 63 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 64 11. Normative References . . . . . . . . . . . . . . . . . . . . 5 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 67 1. Introduction 69 Querying and retrieving registration data from registries are defined 70 in the Registration Data Access Protocol(RDAP)[I-D.ietf-weirds-rdap- 71 query][I-D.ietf-weirds-using-http][I-D.ietf-weirds-json-response]. 72 These documents do not specify where to send the queries. This 73 document specifies a method to find which server is authoritative to 74 answer queries for the requested scope. 76 (author note: should it have some text on various possibilities that 77 have been discussed, such as IETF84...?) 79 The proposed mechanism is based on that allocation data for domain 80 names and IP addresses are maintained by IANA, are publicly available 81 and are in a structured format. The mechanism assumes some data 82 structure within these registries and request IANA to modify these 83 registries for the specific purpose of RDAP use. An RDAP client 84 fetches the registries, extract the data and then do a match with the 85 query data to find the authoritative registration data server and 86 appropriate query base URL. 88 2. Domain Name Registry 90 The domain names authoritative registration data service is found by 91 doing the longest match of the target domain name with the values of 92 the Domain column in the IANA Domain Name registry[domainreg]. The 93 value of the "RDAP URL" column is the base RDAP url as described in 94 [I-D.ietf-weirds-rdap-query]. 96 For example, a RDAP query for example.com matches the .com entry in 97 the Domain column of the registry. The RDAP server URL for this 98 address is located in the corresponding "RDAP URL" column for that 99 entry, which could be http://rdap.example.org/rdap. 101 3. Internet Numbers Registry 103 3.1. IPv4 Address Space 105 The IPv4 address space authoritative registration data service is 106 found by doing a longest match of the target address with the values 107 of the Prefix column in the IANA IPv4 address space 108 registry[ipv4reg]. The value of the "RDAP URL" column is the base 109 RDAP url as described in [I-D.ietf-weirds-rdap-query]. 111 For example, a query for "192.0.2.0/24" matches the "192/8" entry in 112 the Prefix column of the registry. The RDAP server URL for this 113 address is located in the corresponding "RDAP URL" column for that 114 entry, which could be http://rdap.example.org/rdap. 116 3.2. IPv6 Address Space 118 The IPv6 address space authoritative registration data service is 119 found by doing a longest match of the target address with the values 120 of the Prefix column in the IANA IPv6 address space 121 registry[ipv6reg]. The value of the "RDAP URL" column is the base 122 RDAP url as described in [I-D.ietf-weirds-rdap-query]. 124 For example, a query for "2001:db8::/32" matches the "2001/16" entry 125 in the Prefix column of the registry. The RDAP server URL for this 126 address is located in the corresponding "RDAP URL" column for that 127 entry, which could be http://rdap.example.org/rdap. 129 3.3. Autonomous Systems 131 The Autonomous Systems (AS) authoritative registration data service 132 is found by identifying the range in which the target Autonomous 133 System is with the values of the Number column in the IANA Autonomous 134 Systems (AS) Numbers registry[asreg]. The value of the "RDAP URL" 135 column is the base RDAP url as described in 136 [I-D.ietf-weirds-rdap-query]. 138 For example, a query for AS 65411 matches the "64512-65534" entry in 139 the Number column of the registry. The RDAP server URL for this 140 address is located in the corresponding "RDAP URL" column for that 141 entry, which could be http://rdap.example.org/rdap. 143 4. Nameserver 145 TBD 147 5. Entity 149 TBD 151 6. Non-existent Entries or RDAP URL Values 153 The registries may not contain the requested value or the RDAP URL 154 value may be empty. In these cases, there is no known RDAP server 155 for that requested value and the client should provide an appropriate 156 error message to the user. 158 7. Deployment Considerations 160 This method relies on the fact that RDAP clients are fetching the 161 IANA XML registries. Clients SHOULD not fetch every time the XML 162 files. Clients should rely on HTTP headers to verify if the registry 163 has changed since last time it was fetched. 165 IANA should make sure that the service of those registries is able to 166 cope with a larger demand and should take appropriate measures such 167 as caching and load balancing. 169 This specification makes no assumption on how the authorities of 170 registration data may work together on sharing their information for 171 a common service. 173 8. Security Considerations 175 TBD 177 9. IANA Considerations 179 IANA is requested to do the following: 181 o Add the "RDAP URL" column to the IPv4 Address Space, IPv6 Address 182 Space and Autonomous Systems Numbers registries. The same 183 entities who are registrants for these spaces are entitled to 184 provide the RDAP URL value for their respective space. 186 o Create a new registry of domain names with the following columns: 187 Domain and RDAP URL. The content should be initially populated by 188 an extract of the Root zone database. A change happens in the 189 database may trigger a change in that new registry. The same 190 entities who are registrants for the root zone database entries 191 are entitled to provide the RDAP URL value for their domain. IANA 192 shall update its procedures to include the provisioning of these 193 values. 195 o author note: more details needed 197 10. Acknowledgements 199 The weirds working group had multiple discussions on this topic, 200 including a session during IETF 84. All the people involved in these 201 discussions are herin acknowledged. XXX have provided input and 202 suggestions to this document. 204 11. Normative References 206 [I-D.ietf-weirds-json-response] 207 Newton, A. and S. Hollenbeck, "JSON Responses for the 208 Registration Data Access Protocol (RDAP)", draft-ietf- 209 weirds-json-response-03 (work in progress), April 2013. 211 [I-D.ietf-weirds-rdap-query] 212 Newton, A. and S. Hollenbeck, "Registration Data Access 213 Protocol Lookup Format", draft-ietf-weirds-rdap-query-04 214 (work in progress), April 2013. 216 [I-D.ietf-weirds-using-http] 217 Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the 218 Registration Data Access Protocol (RDAP)", draft-ietf- 219 weirds-using-http-05 (work in progress), May 2013. 221 [asreg] Internet Assigned Numbers Authority(IANA), ., "Autonomous 222 System (AS) Numbers", , . 225 [domainreg] 226 Internet Assigned Numbers Authority(IANA), ., "TBD", , 227 . 229 [ipv4reg] Internet Assigned Numbers Authority(IANA), ., "IPv4 230 Address Space", , . 233 [ipv6reg] Internet Assigned Numbers Authority(IANA), ., "IPv6 Global 234 Unicast Address Assignments", , . 238 Author's Address 240 Marc Blanchet 241 Viagenie 242 246 Aberdeen 243 Quebec, QC G1R 2E1 244 Canada 246 Email: Marc.Blanchet@viagenie.ca 247 URI: http://www.viagenie.ca