Network Working Group A. Newton Internet-Draft ICANN Intended status: Standards Track 9 February 2026 Expires: 13 August 2026 RDAP Simple Values draft-newton-rdap-simple-values-latest Abstract This document defines an extension for the Registration Data Access Protocol to express simple values for scenarios where specific data is needed, but the format of the data is not complicated enough to require a specific extension for that data. About This Document This note is to be removed before publishing as an RFC. The latest revision of this draft can be found at https://anewton1998.github.io/draft-newton-rdap-simple-values/draft- newton-rdap-simple-values.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-newton-rdap- simple-values/. Source for this draft and an issue tracker can be found at https://github.com/anewton1998/draft-newton-rdap-simple-values. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 13 August 2026. Copyright Notice Copyright (c) 2026 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 and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction 2. Conventions and Definitions 3. Simple Value Data 4. Security Considerations 5. IANA Considerations 6. Normative References Acknowledgments Author's Address 1. Introduction The Registration Data Access Protocol (RDAP) defines a core set of data types for Domain Name Registries (DNRs) and Internet Number Resource Registries (INRRs) as defined in [RFC9083]. When a registry needs to express data not found in [RFC9083], an RDAP extension must be used for the expression of that data. However, RDAP extensions require changes to client software to be useful by most users. For scenarios in which the data is not complex, this can be overly burdensome. This RDAP extension defines a method for the expression of simple values that is reusable across multiple use cases. 2. Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. Simple Value Data This RDAP extension defines a JSON object of the following form: "simpleValues_data" : [ { "name" : "example", "value" : "the data", "scope" : "some scope", "links" : [ ... (links from RFC 9083) ] } ] This JSON object contains an array of name/value JSON objects, each with the following members: * "name" - a string containing the registered name of the value. * "value" - depending on the registration of the name, this is one of the following data types: - a JSON boolean - a JSON number - a JSON string - an array of JSON booleans - an array of JSON numbers - an array of JSON strings * "scope" - an OPTIONAL string to distinguish a specific use of the value. * "links" - as defined in [RFC9083]. Each object of the array MUST only appear once per combination of "name" and "scope". As "scope" is optional, an object of the array without a scope MUST only appear once with a "name". The "simpleValues_data" object MUST only appear at the top-level of an RDAP object class instance. The following is an example of an RDAP "ip network" object with a "simpleValues_data" object: { "rdapConformance" : [ "rdap_level_0", "simpleValues" ], "objectClassName" : "ip network", "handle" : "203.0.113.0 - 203.0.113.255", "ipVersion" : "v4", "startAddress" : "203.0.113.0", "endAddress" : "203.0.113.255", "simpleValue_data" : [ { "name" : "ip announce auth key pem", "value" : [ "---BEGIN KEY---", "349390202000020", "---END KEY---" ], "scope" : "cloud provider alpha" }, { "name" : "ip announce auth key pem", "value" : [ "---BEGIN KEY---", "abcdefghijklmno", "---END KEY---" ], "scope" : "cloud provider gamma" }, ] } 4. Security Considerations TODO Security 5. IANA Considerations TODO: Registery "simpleValues" RDAP extension identifier. 6. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the Registration Data Access Protocol (RDAP)", STD 95, RFC 9083, DOI 10.17487/RFC9083, June 2021, . Acknowledgments TODO acknowledge. Author's Address Andy Newton ICANN Email: andy@hxr.us