--- 1/draft-ietf-regext-rfc7484bis-05.txt 2022-01-28 20:13:10.402281028 -0800 +++ 2/draft-ietf-regext-rfc7484bis-06.txt 2022-01-28 20:13:10.438281935 -0800 @@ -1,19 +1,19 @@ Network Working Group M. Blanchet Internet-Draft Viagenie -Obsoletes: 7484 (if approved) 25 January 2022 +Obsoletes: 7484 (if approved) 28 January 2022 Intended status: Standards Track -Expires: 29 July 2022 +Expires: 1 August 2022 Finding the Authoritative Registration Data (RDAP) Service - draft-ietf-regext-rfc7484bis-05 + draft-ietf-regext-rfc7484bis-06 Abstract This document specifies a method to find which Registration Data Access Protocol (RDAP) server is authoritative to answer queries for a requested scope, such as domain names, IP addresses, or Autonomous System numbers. This document obsoletes RFC7484. Status of This Memo @@ -23,21 +23,21 @@ 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 https://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 29 July 2022. + This Internet-Draft will expire on 1 August 2022. Copyright Notice Copyright (c) 2022 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 (https://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 @@ -55,25 +55,25 @@ 5. Bootstrap Service Registries for Internet Numbers . . . . . . 6 5.1. Bootstrap Service Registry for IPv4 Address Space . . . . 6 5.2. Bootstrap Service Registry for IPv6 Address Space . . . . 7 5.3. Bootstrap Service Registry for AS Number Space . . . . . 9 6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 10 8. Deployment and Implementation Considerations . . . . . . . . 10 9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 11 10. Formal Definition . . . . . . . . . . . . . . . . . . . . . . 11 10.1. Imported JSON Terms . . . . . . . . . . . . . . . . . . 11 - 10.2. Registry Syntax . . . . . . . . . . . . . . . . . . . . 12 + 10.2. Registry Syntax . . . . . . . . . . . . . . . . . . . . 11 11. Security Considerations . . . . . . . . . . . . . . . . . . . 12 - 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 13 + 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 12 12.1. RDAP Browser Mobile Application . . . . . . . . . . . . 13 - 12.2. ICANN Lookup Web Application . . . . . . . . . . . . . . 14 + 12.2. ICANN Lookup Web Application . . . . . . . . . . . . . . 13 12.3. ARIN Implementation . . . . . . . . . . . . . . . . . . 14 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 13.1. Bootstrap Service Registry for IPv4 Address Space . . . 16 13.2. Bootstrap Service Registry for IPv6 Address Space . . . 16 13.3. Bootstrap Service Registry for AS Number Space . . . . . 16 13.4. Bootstrap Service Registry for Domain Name Space . . . . 16 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 14.1. Normative References . . . . . . . . . . . . . . . . . . 16 14.2. Informative References . . . . . . . . . . . . . . . . . 17 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 19 @@ -359,27 +359,28 @@ the base URL to complete the query. The complete query is, therefore, "https://example.net/rdaprir2/ip/2001:db8:1000::/48". If the target RDAP server does not answer, the client can then use another URL prefix from the array. 5.3. Bootstrap Service Registry for AS Number Space The JSON output of this registry contains Autonomous Systems number ranges entries, grouped by base RDAP URLs, as shown in this example. The Entry Array is an array containing the list of AS number ranges - served by the base RDAP URLs found in the second element. The array - always contains two AS numbers represented in decimal format that - represents the range of AS numbers between the two elements of the - array, where values are in increasing order (e.g. 100-200, not - 200-100). A single AS number is represented as a range of two - identical AS numbers. AS numbers are represented as 'asplain' as - defined in [RFC5396]. Ranges MUST NOT overlap. + served by the base RDAP URLs found in the second element. Each + element of the array contains two AS numbers represented in decimal + format, separated by a hyphen, that represents the range of AS + numbers between the two AS numbers (inclusive), where values are in + increasing order (e.g. 100-200, not 200-100). A single AS number is + represented as a range of two identical AS numbers. AS numbers are + represented as 'asplain' as defined in [RFC5396]. Ranges MUST NOT + overlap. { "version": "1.0", "publication": "2024-01-07T10:11:12Z", "description": "RDAP Bootstrap file for example registries.", "services": [ [ ["64496-64496"], [ "https://rir3.example.com/myrdap/" @@ -526,22 +529,21 @@ uri * service-uri: a STRING 11. Security Considerations By providing a bootstrap method to find RDAP servers, this document helps to ensure that the end users will get the RDAP data from an authoritative source, instead of from rogue sources. The method has the same security properties as the RDAP protocols themselves. The - transport used to access the registries can be more secure by using - TLS [RFC8446], which IANA supports. + transport used to access the registries uses TLS [RFC8446]. Additional considerations on using RDAP are described in [RFC7481]. 12. Implementation Status NOTE: Please remove this section and the reference to RFC 7942 prior to publication as an RFC. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this @@ -619,21 +621,23 @@ Contact Information: info@arin.net Information Last Updated: Nov 2020 13. IANA Considerations IANA has created the RDAP Bootstrap Services Registries, listed below, and made them available as JSON objects. The contents of these registries are described in Section 3, Section 4, and - Section 5, with the formal syntax specified in Section 10. + Section 5, with the formal syntax specified in Section 10. The + registries MUST be accessible only through HTTPS (TLS [RFC8446]) + transport. The process for adding or updating entries in these registries differs from the normal IANA registry processes: these registries are generated from the data, processes, and policies maintained by IANA in their allocation registries ([ipv4reg], [ipv6reg], [asreg], and [domainreg]), with the addition of new RDAP server information. IANA updates RDAP Bootstrap Services Registries entries from the allocation registries as those registries are updated. @@ -847,28 +851,29 @@ Harrison, Naoki Kambe, Alexander Mayrhofer, Edward Lewis, Pete Resnick, Alessandro Vesely, Bert Greevenbosch, Barry Leiba, Jari Arkko, Kathleen Moriaty, Stephen Farrell, Richard Barnes, and Jean- Francois Tremblay have provided input and suggestions to this document. Guillaume Leclanche was a coauthor of this document for some revisions; his support is therein acknowledged and greatly appreciated. The section on formal definition was inspired by Section 6.2 of [RFC7071]. This new version got comments and suggestions from: Gavin Brown, Patrick Mevzek, John Levine, Jasdip Singh, George Michaelson, Scott Hollenbeck, Russ Housley, Joel - Halpern, Lars Eggert, Benjamin Kaduk, Scott Kelly. Errata of RFC7484 - were submitted by Pieter Vandepitte and were applied to this version. + Halpern, Lars Eggert, Benjamin Kaduk, Scott Kelly, Eric Vyncke, John + Scudder, Erik Kline, Robert Wilton. Errata of RFC7484 were submitted + by Pieter Vandepitte and were applied to this version. Changes since RFC7484 There are no substantive changes except for updates to the implementation status and minor clarifications. This update is primarily to meet the requirements for moving to Internet Standard. Author's Address + Marc Blanchet Viagenie 246 Aberdeen Quebec QC G1R 2E1 Canada - Email: Marc.Blanchet@viagenie.ca URI: https://viagenie.ca