idnits 2.17.1 draft-blanchet-weirds-bootstrap-autonomous-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 : ---------------------------------------------------------------------------- == There are 5 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 21, 2013) is 3839 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-06 == Outdated reference: A later version (-18) exists of draft-ietf-weirds-rdap-query-07 == Outdated reference: A later version (-15) exists of draft-ietf-weirds-using-http-07 Summary: 0 errors (**), 0 flaws (~~), 6 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 October 21, 2013 5 Expires: April 24, 2014 7 Finding the Authoritative Registration Data (RDAP) Server 8 draft-blanchet-weirds-bootstrap-autonomous-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. 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 April 24, 2014. 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 . . . . . . . . . . . . . . . . . . . . 3 53 3. Internet Numbers Registry . . . . . . . . . . . . . . . . . . 3 54 3.1. IPv4 Address Space . . . . . . . . . . . . . . . . . . . 3 55 3.2. IPv6 Address Space . . . . . . . . . . . . . . . . . . . 4 56 3.3. Autonomous Systems . . . . . . . . . . . . . . . . . . . 4 57 4. Nameserver . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6. SRV Records Processing . . . . . . . . . . . . . . . . . . . 4 60 7. Querying to the Authoritative Server . . . . . . . . . . . . 4 61 8. Deployment Considerations . . . . . . . . . . . . . . . . . . 5 62 9. Assumptions and Limitations . . . . . . . . . . . . . . . . . 5 63 10. Security Considerations . . . . . . . . . . . . . . . . . . . 5 64 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 65 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 66 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 13.1. Normative References . . . . . . . . . . . . . . . . . . 5 68 13.2. Informative References . . . . . . . . . . . . . . . . . 6 69 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 71 1. Introduction 73 Querying and retrieving registration data from registries are defined 74 in the Registration Data Access Protocol(RDAP)[I-D.ietf-weirds-rdap- 75 query][I-D.ietf-weirds-using-http][I-D.ietf-weirds-json-response]. 76 These documents do not specify where to send the queries. This 77 document specifies a method to find which server is authoritative to 78 answer queries for the requested scope. 80 (author note: should it have some text on various possibilities that 81 have been discussed, such as IETF84...?) 83 This document proposes two different mechanisms depending on the type 84 of the queried object. 86 For IP addresses and autonomous system numbers, the method uses a 87 Number Resource Organization(NRO) managed registry of allocations. 89 For domain names, the method uses a well-known label in the top of 90 the registry. 92 Both use the same DNS resource record(RR) which is used to locate the 93 RDAP server. The processing of the RR is discussed later in this 94 document. It should be noted that the document currently uses SRV as 95 an example and it is underspecified. When the concensus is reached 96 on the method and the RR, the draft will be updated accordingly with 97 the appropriate details. 99 2. Domain Name Registry 101 The domain names authoritative registration data servers are found by 102 extracting the tld part of the queried domain name and then querying 103 _rdap._tcp.tld with a DNS resource record of type SRV [RFC2782]. 105 For example, a RDAP query for example.com generates a DNS SRV query 106 to _rdap._tcp.com. 108 IDN labels are in their A-label form[RFC5891]. 110 3. Internet Numbers Registry 112 The authoritative source is a file[NROFILE] containing the 113 allocations of IP addresses and Autonomous System (AS) numbers for 114 all (currently five) Regional Internet Registries(RIR). It is 115 compiled and maintained by the Number Resource Organization(NRO). 116 The current format is a list of rows, where each column is separated 117 by "|" (ASCII 0x7c). The third column contains the type of the 118 object and the fourth column contains the value of the object. The 119 current format does not list the URL of the RDAP server related to 120 the queried resource. However, it has been said that it can be 121 augmented to provide that information. 123 The file is currently large(19Moctets, 300K lines) and should not be 124 queried by clients every time. The average number of lines changed 125 every day is currelty around 100. However, there are days when 95K 126 lines were changed. The file should be cached and regularly updated. 127 (author note: more to discuss on the updating/caching). 129 3.1. IPv4 Address Space 131 The IPv4 address space authoritative registration data servers are 132 found in the file by looking for the type "ipv4" (currently in 3rd 133 column) and doing a longest match on the queried prefix. The column 134 X (not currently available) provides the fully-qualified domain 135 name(FQDN) of the RDAP server for that prefix. 137 For example, a query for 192.9.200.0/24 looks for the longest match 138 prefix in the file and then fetch the fully-qualified domain 139 name(FQDN) of that prefix, for example: rdap.rirexample.net. A DNS 140 SRV record is then queried for the FQDN. 142 3.2. IPv6 Address Space 144 The IPv6 address space authoritative registration data servers are 145 found in the file by looking for the type "ipv6" (currently in 3rd 146 column) and doing a longest match on the queried prefix. The column 147 X (not currently available) provides the fully-qualified domain 148 name(FQDN) of the RDAP server for that prefix. 150 For example, a query for 2001:db8::/32 looks for the longest match 151 prefix in the file and then fetch the fully-qualified domain 152 name(FQDN) of that prefix, for example: rdap.rirexample.net. A DNS 153 SRV record is then queried on the FQDN. 155 3.3. Autonomous Systems 157 The Autonomous Systems (AS) authoritative registration data servers 158 are found in the file by looking for the type "asn" (currently in 3rd 159 column) and doing an exact match on the queried number. The column X 160 (not currently available) provides the fully-qualified domain 161 name(FQDN) of the RDAP server for that AS. 163 For example, a query for AS 65411 looks for the exact match AS in the 164 file and then fetch the fully-qualified domain name(FQDN) of that 165 prefix, for example: rdap.rirexample.net. A DNS SRV record is then 166 queried on the FQDN. 168 4. Nameserver 170 TBD 172 5. Entity 174 TBD 176 6. SRV Records Processing 178 TBD. The other RR choices are: A, AAAA, CNAME, NAPTR. See 179 discussion in IETF87 for details. 181 7. Querying to the Authoritative Server 182 After finding the authoritative server IP address, the client 183 connects using the appropriate transport and application protocol to 184 do the RDAP query[I-D.ietf-weirds-rdap-query]. 186 8. Deployment Considerations 188 Caching and Updating considerations (TBD) 190 RDAP server operators may use various techniques such as 191 anycast[RFC4786] to manage the load on their servers. 193 9. Assumptions and Limitations 195 This specification assumes that the NRO is the authoritative source 196 of the IPv4, IPv6 and AS numbers allocations, and that it keeps the 197 file updated. 199 This specification only provides a method to find RDAP servers for 200 two-labels domain names. 202 10. Security Considerations 204 TBD 206 11. IANA Considerations 208 none at the moment. 210 12. Acknowledgements 212 The weirds working group had multiple discussions on this topic, 213 including a session during IETF 84 and 87. The ideas in this draft 214 were proposed during the IETF 87 weirds session by (TBD). 216 13. References 218 13.1. Normative References 220 [I-D.ietf-weirds-json-response] 221 Newton, A. and S. Hollenbeck, "JSON Responses for the 222 Registration Data Access Protocol (RDAP)", draft-ietf- 223 weirds-json-response-06 (work in progress), October 2013. 225 [I-D.ietf-weirds-rdap-query] 226 Newton, A. and S. Hollenbeck, "Registration Data Access 227 Protocol Query Format", draft-ietf-weirds-rdap-query-07 228 (work in progress), October 2013. 230 [I-D.ietf-weirds-using-http] 231 Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the 232 Registration Data Access Protocol (RDAP)", draft-ietf- 233 weirds-using-http-07 (work in progress), July 2013. 235 [NROFILE] Number Resource Organization(NRO), ., "TBD", , . 239 [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for 240 specifying the location of services (DNS SRV)", RFC 2782, 241 February 2000. 243 [RFC5891] Klensin, J., "Internationalized Domain Names in 244 Applications (IDNA): Protocol", RFC 5891, August 2010. 246 13.2. Informative References 248 [RFC4786] Abley, J. and K. Lindqvist, "Operation of Anycast 249 Services", BCP 126, RFC 4786, December 2006. 251 Author's Address 253 Marc Blanchet 254 Viagenie 255 246 Aberdeen 256 Quebec, QC G1R 2E1 257 Canada 259 Email: Marc.Blanchet@viagenie.ca 260 URI: http://www.viagenie.ca