--- 1/draft-ietf-regext-rfc7484bis-02.txt	2021-03-29 08:13:46.828792833 -0700
+++ 2/draft-ietf-regext-rfc7484bis-03.txt	2021-03-29 08:13:46.872793929 -0700
@@ -1,19 +1,19 @@
 
 Network Working Group                                        M. Blanchet
 Internet-Draft                                                  Viagenie
-Obsoletes: 7484 (if approved)                             March 19, 2021
+Obsoletes: 7484 (if approved)                             March 29, 2021
 Intended status: Standards Track
-Expires: September 20, 2021
+Expires: September 30, 2021
 
        Finding the Authoritative Registration Data (RDAP) Service
-                    draft-ietf-regext-rfc7484bis-02
+                    draft-ietf-regext-rfc7484bis-03
 
 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 September 20, 2021.
+   This Internet-Draft will expire on September 30, 2021.
 
 Copyright Notice
 
    Copyright (c) 2021 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
@@ -361,21 +361,22 @@
 
 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.  A single AS number is represented as a range of two identical
-   AS numbers.
+   AS numbers.  AS numbers are represented as 'asplain' as defined in
+   [RFC5396].
 
    {
        "version": "1.0",
        "publication": "2024-01-07T10:11:12Z",
        "description": "RDAP Bootstrap file for example registries.",
        "services": [
          [
            ["64496-64496"],
            [
              "https://rir3.example.com/myrdap/"
@@ -735,20 +734,25 @@
 
    [RFC4291]  Hinden, R. and S. Deering, "IP Version 6 Addressing
               Architecture", RFC 4291, DOI 10.17487/RFC4291, February
               2006, <https://www.rfc-editor.org/info/rfc4291>.
 
    [RFC4632]  Fuller, V. and T. Li, "Classless Inter-domain Routing
               (CIDR): The Internet Address Assignment and Aggregation
               Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August
               2006, <https://www.rfc-editor.org/info/rfc4632>.
 
+   [RFC5396]  Huston, G. and G. Michaelson, "Textual Representation of
+              Autonomous System (AS) Numbers", RFC 5396,
+              DOI 10.17487/RFC5396, December 2008,
+              <https://www.rfc-editor.org/info/rfc5396>.
+
    [RFC5890]  Klensin, J., "Internationalized Domain Names for
               Applications (IDNA): Definitions and Document Framework",
               RFC 5890, DOI 10.17487/RFC5890, August 2010,
               <https://www.rfc-editor.org/info/rfc5890>.
 
    [RFC7258]  Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
               Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May
               2014, <https://www.rfc-editor.org/info/rfc7258>.
 
    [RFC8259]  Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
@@ -780,27 +784,27 @@
    [RFC7071]  Borenstein, N. and M. Kucherawy, "A Media Type for
               Reputation Interchange", RFC 7071, DOI 10.17487/RFC7071,
               November 2013, <https://www.rfc-editor.org/info/rfc7071>.
 
    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
               RFC 7234, DOI 10.17487/RFC7234, June 2014,
               <https://www.rfc-editor.org/info/rfc7234>.
 
    [RFC7480]  Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the
-              Registration Data Access Protocol (RDAP)", RFC 7480,
-              DOI 10.17487/RFC7480, March 2015,
+              Registration Data Access Protocol (RDAP)", STD 95,
+              RFC 7480, DOI 10.17487/RFC7480, March 2015,
               <https://www.rfc-editor.org/info/rfc7480>.
 
    [RFC7481]  Hollenbeck, S. and N. Kong, "Security Services for the
-              Registration Data Access Protocol (RDAP)", RFC 7481,
-              DOI 10.17487/RFC7481, March 2015,
+              Registration Data Access Protocol (RDAP)", STD 95,
+              RFC 7481, DOI 10.17487/RFC7481, March 2015,
               <https://www.rfc-editor.org/info/rfc7481>.
 
    [RFC7482]  Newton, A. and S. Hollenbeck, "Registration Data Access
               Protocol (RDAP) Query Format", RFC 7482,
               DOI 10.17487/RFC7482, March 2015,
               <https://www.rfc-editor.org/info/rfc7482>.
 
    [RFC7483]  Newton, A. and S. Hollenbeck, "JSON Responses for the
               Registration Data Access Protocol (RDAP)", RFC 7483,
               DOI 10.17487/RFC7483, March 2015,