Network Working Group M. Wullink Internet-Draft SIDN Labs Intended status: Standards Track P. Kowalik Expires: 17 December 2026 DENIC 15 June 2026 JSON for Restful Provisioning Protocol (RPP) draft-wullink-rpp-json-02 Abstract This document defines the rules for representing the RESTful Provisioning Protocol (RPP) data objects, as defined in [I-D.kowalik-rpp-data-objects], using the JavaScript Object Notation (JSON) Data Interchange Format [RFC8259]. It specifies how RPP primitive types, common data types, component objects, resource objects, and associations are mapped to JSON and JSON Schema, and provides normative JSON Schema definitions and worked examples for domain name, contact, and host data objects. 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 17 December 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 Wullink & Kowalik Expires 17 December 2026 [Page 1] Internet-Draft JSON for RPP June 2026 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 . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Conventions Used in This Document . . . . . . . . . . . . . . 5 4. JSON Representation Rules . . . . . . . . . . . . . . . . . . 6 4.1. Primitive Type Mappings . . . . . . . . . . . . . . . . . 6 4.2. Cardinality Rules . . . . . . . . . . . . . . . . . . . . 7 4.3. Mutability Rules . . . . . . . . . . . . . . . . . . . . 8 4.4. Association Rules . . . . . . . . . . . . . . . . . . . . 9 4.4.1. Labelled associations . . . . . . . . . . . . . . . . 9 4.4.2. Aggregation . . . . . . . . . . . . . . . . . . . . . 9 4.4.3. Composition . . . . . . . . . . . . . . . . . . . . . 10 4.4.4. Labelled Aggregation . . . . . . . . . . . . . . . . 11 4.4.5. Dictionary Aggregation . . . . . . . . . . . . . . . 12 4.4.6. Labelled Composition . . . . . . . . . . . . . . . . 13 4.4.7. Dictionary Composition . . . . . . . . . . . . . . . 14 4.5. Object Identifier Rules . . . . . . . . . . . . . . . . . 14 4.6. JSON Schema Definition Rules . . . . . . . . . . . . . . 14 4.6.1. RPP Profiles and Validation . . . . . . . . . . . . . 16 5. JSON Schema Definitions . . . . . . . . . . . . . . . . . . . 16 5.1. Common Data Types Schemas . . . . . . . . . . . . . . . . 16 5.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 16 5.1.2. Client Identifier . . . . . . . . . . . . . . . . . . 17 5.1.3. Phone Number . . . . . . . . . . . . . . . . . . . . 17 5.2. Component Objects Schemas . . . . . . . . . . . . . . . . 17 5.2.1. Period Object . . . . . . . . . . . . . . . . . . . . 17 5.2.2. Provisioning Metadata Object . . . . . . . . . . . . 18 5.2.3. Status Object . . . . . . . . . . . . . . . . . . . . 19 5.2.4. DNS Resource Record Object . . . . . . . . . . . . . 20 5.2.5. DNS Operational Controls Object . . . . . . . . . . . 21 5.2.6. DNS Data Object . . . . . . . . . . . . . . . . . . . 22 5.2.7. Authorisation Information Object . . . . . . . . . . 23 5.2.8. Postal Address Object . . . . . . . . . . . . . . . . 24 5.2.9. Postal Info Object . . . . . . . . . . . . . . . . . 24 5.2.10. Restore Report Object . . . . . . . . . . . . . . . . 25 5.3. Process Object Schemas . . . . . . . . . . . . . . . . . 26 5.3.1. Transfer Process Object . . . . . . . . . . . . . . . 26 5.3.2. Restore Process Object . . . . . . . . . . . . . . . 30 5.4. Domain Name Data Object . . . . . . . . . . . . . . . . . 31 5.5. Contact Data Object . . . . . . . . . . . . . . . . . . . 34 5.6. Host Data Object . . . . . . . . . . . . . . . . . . . . 37 5.7. Organisation Data Object . . . . . . . . . . . . . . . . 38 Wullink & Kowalik Expires 17 December 2026 [Page 2] Internet-Draft JSON for RPP June 2026 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.1. Domain Name . . . . . . . . . . . . . . . . . . . . . . . 39 6.1.1. Create . . . . . . . . . . . . . . . . . . . . . . . 39 6.1.2. Read . . . . . . . . . . . . . . . . . . . . . . . . 40 6.1.3. Update . . . . . . . . . . . . . . . . . . . . . . . 41 6.1.4. Delete . . . . . . . . . . . . . . . . . . . . . . . 42 6.1.5. Renew . . . . . . . . . . . . . . . . . . . . . . . . 42 6.1.6. Transfer Request . . . . . . . . . . . . . . . . . . 43 6.1.7. Transfer Query . . . . . . . . . . . . . . . . . . . 44 6.1.8. Transfer Cancel / Reject / Approve . . . . . . . . . 44 6.1.9. Restore Request . . . . . . . . . . . . . . . . . . . 44 6.1.10. Restore Report . . . . . . . . . . . . . . . . . . . 45 6.1.11. Restore Query . . . . . . . . . . . . . . . . . . . . 46 6.2. Contact . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.2.1. Create . . . . . . . . . . . . . . . . . . . . . . . 46 6.2.2. Read . . . . . . . . . . . . . . . . . . . . . . . . 48 6.2.3. Update . . . . . . . . . . . . . . . . . . . . . . . 49 6.2.4. Delete . . . . . . . . . . . . . . . . . . . . . . . 49 6.2.5. Transfer Request . . . . . . . . . . . . . . . . . . 50 6.2.6. Transfer Query . . . . . . . . . . . . . . . . . . . 50 6.2.7. Transfer Cancel / Reject / Approve . . . . . . . . . 50 6.3. Host . . . . . . . . . . . . . . . . . . . . . . . . . . 51 6.3.1. Create . . . . . . . . . . . . . . . . . . . . . . . 51 6.3.2. Read . . . . . . . . . . . . . . . . . . . . . . . . 52 6.3.3. Update . . . . . . . . . . . . . . . . . . . . . . . 53 6.3.4. Delete . . . . . . . . . . . . . . . . . . . . . . . 54 6.3.5. Restore Request . . . . . . . . . . . . . . . . . . . 54 6.3.6. Restore Report . . . . . . . . . . . . . . . . . . . 55 6.3.7. Restore Query . . . . . . . . . . . . . . . . . . . . 56 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 8. Internationalization Considerations . . . . . . . . . . . . . 56 9. Security Considerations . . . . . . . . . . . . . . . . . . . 56 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 11. Change History . . . . . . . . . . . . . . . . . . . . . . . 57 11.1. Version 01 to 02 . . . . . . . . . . . . . . . . . . . . 57 11.2. Version 00 to 01 . . . . . . . . . . . . . . . . . . . . 57 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 12.1. Normative References . . . . . . . . . . . . . . . . . . 57 12.2. Informative References . . . . . . . . . . . . . . . . . 58 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59 Wullink & Kowalik Expires 17 December 2026 [Page 3] Internet-Draft JSON for RPP June 2026 1. Introduction The RESTful Provisioning Protocol (RPP) defines a set of data objects for managing foundational registry resources including domain names, contacts, and hosts. The data model is defined in [I-D.kowalik-rpp-data-objects] independently of any particular representation format. This document defines the JSON [RFC8259] representation of those data objects. JSON has emerged as the de facto standard data format for modern RESTful APIs. Its widespread adoption across tools, libraries, and developer communities makes it well suited as the primary representation format for RPP. This document provides the normative rules and JSON Schema definitions required for implementations to produce and consume RPP messages in JSON. The separation between the abstract data model and its concrete JSON representation ensures that the protocol's semantic foundation remains stable while enabling the adoption of JSON across diverse deployment environments. 1.1. Motivation The RESTful Provisioning Protocol (RPP) introduces a new provisioning mechanism that aligns more closely with modern cloud infrastructure, enhancing the scalability of server deployments. While RESTful protocols do not mandate a specific media type for resource description, the widespread adoption of JSON in web services has established it as the de facto standard for modern APIs. The increasing availability of tools, software libraries, and a skilled workforce has led several registries to adopt JSON for data exchange within their API ecosystems. Registries supporting JSON can offer a unified API ecosystem that extends beyond domain name and IP address provisioning, maintaining a consistent technology stack, data formats, and developer experience. JSON's syntax, known for its straightforwardness and minimal verbosity, significantly eases the tasks of writing, reading, and maintaining code. This simplicity is especially advantageous for the rapid comprehension and integration of provisioning APIs. The lightweight nature of JSON can result in faster processing and data transfers, a critical aspect in high-volume transaction environments such as domain registration. Enhanced API response times can lead to more efficient domain lookups, registrations, and updates. JSON parsing is typically fast and well-supported by standard libraries, contributing to improved system performance amid frequent interactions between RPP clients and servers. Wullink & Kowalik Expires 17 December 2026 [Page 4] Internet-Draft JSON for RPP June 2026 However, the absence of a standardised JSON format for domain provisioning has led to the emergence of TLD-specific implementations that lack interoperability, increasing the development effort required for integration. Similarly, at the registrar level, the absence of standards has resulted in numerous incompatible API implementations provided to clients and resellers. Standardising a JSON format for domain provisioning within the RPP framework could mitigate these challenges, reducing fragmentation and simplifying integration efforts across the domain registration industry. 2. Terminology In this document the following terminology is used. RPP Data Objects - The abstract data model definitions for domain name, contact, and host resources, as specified in [I-D.kowalik-rpp-data-objects]. RESTful Provisioning Protocol - A RESTful protocol for provisioning heterogeneous database objects. JSON Schema - A vocabulary that allows annotation and validation of JSON documents, as described in [JSON-SCHEMA]. EPP Compatibility Profile - A set of additional constraints defined in [I-D.kowalik-rpp-data-objects] that a server MUST adhere to when supporting both RPP and EPP concurrently. 3. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. JSON is case sensitive. Unless stated otherwise, JSON specifications and examples provided in this document MUST be interpreted in the character case presented. The examples in this document assume that request and response messages are properly formatted JSON documents. Indentation and white space in examples are provided only to illustrate element relationships and for improving readability, and are not REQUIRED features of the protocol. All JSON Schema definitions in this document use JSON Schema draft 2020-12 [JSON-SCHEMA], and where not provided with a $schema keyword, the following default applies: "$schema": "https://json-schema.org/draft/2020-12/schema" Wullink & Kowalik Expires 17 December 2026 [Page 5] Internet-Draft JSON for RPP June 2026 4. JSON Representation Rules This section defines the normative rules for representing the RPP data model in JSON. The data model is specified in [I-D.kowalik-rpp-data-objects], which defines all primitive types, common data types, component objects, resource objects, and associations independently of any concrete representation format. The rules in this section specify how those abstract definitions map to JSON and JSON Schema version 2020-12. 4.1. Primitive Type Mappings RPP primitive types MUST be represented in JSON as follows: +===========+=========+======================================+ | RPP | JSON | Notes | | Primitive | Type | | | Type | | | +===========+=========+======================================+ | String | string | Unicode character sequence | +-----------+---------+--------------------------------------+ | Integer | number | Whole number, positive or negative | +-----------+---------+--------------------------------------+ | Boolean | boolean | true or false | +-----------+---------+--------------------------------------+ | Decimal | string | Base-10 fractional value with exact | | | | representation within a defined | | | | precision. Number is encoded into | | | | string same as "number" in [RFC8259] | | | | without exponent part "ext". | +-----------+---------+--------------------------------------+ | Date | string | Full-date as per [RFC3339], e.g. | | | | "2025-10-27" | +-----------+---------+--------------------------------------+ | Timestamp | string | Date-time in UTC as per [RFC3339], | | | | e.g. "2025-10-27T09:42:51Z" | +-----------+---------+--------------------------------------+ | URL | string | Uniform Resource Locator as per | | | | [RFC1738] | +-----------+---------+--------------------------------------+ | Binary | string | Base64-encoded binary data | +-----------+---------+--------------------------------------+ Table 1 Wullink & Kowalik Expires 17 December 2026 [Page 6] Internet-Draft JSON for RPP June 2026 4.2. Cardinality Rules The cardinality of each data element in the RPP data model MUST be represented as follows in JSON: Rule 1: A data element with cardinality 1 (exactly one) MUST be represented as a JSON property and MUST be present in the containing JSON object. The element MUST be listed under required in the corresponding JSON Schema. { "type": "object", "properties": { "name": { "type": "string" } }, "required": ["name"] } Rule 2: A data element with cardinality 0-1 (zero or one) MUST be represented as an optional JSON property. The element MUST NOT be listed under required in the corresponding JSON Schema. When absent, the element MUST be omitted from the JSON object (not represented as null). { "type": "object", "properties": { "expiryDate": { "type": "string", "format": "date-time" } } } Rule 3: A data element with cardinality 0+ (zero or more) MUST be represented as an optional JSON array. When no values are present, the property MUST be omitted or represented as an empty array. { "type": "object", "properties": { "status": { "type": "array", "items": { "$ref": "#/$defs/status" } } } } Wullink & Kowalik Expires 17 December 2026 [Page 7] Internet-Draft JSON for RPP June 2026 Rule 4: A data element with cardinality 1+ (one or more) MUST be represented as a required JSON array with "minItems": 1 and the element MUST be listed under required in the corresponding JSON Schema. { "type": "object", "properties": { "postalInfo": { "type": "array", "items": { "$ref": "#/$defs/postalInfo"}, "minItems": 1 } }, "required": ["postalInfo"] } 4.3. Mutability Rules Data elements in the RPP data model carry a mutability attribute: create-only, read-only, or read-write. These MUST be represented in JSON Schema as follows: Rule 5: Data elements with mutability read-only MUST be annotated with "readOnly": true in the JSON Schema. Clients MUST NOT include read-only properties in create or update request bodies. Servers MUST ignore any read-only properties provided by a client in a request. { "repositoryId": { "type": "string", "readOnly": true } } Rule 6: Data elements with mutability create-only MUST be annotated with "writeOnly": true in the JSON Schema for request schemas, and excluded from update request schemas. Servers MUST reject requests that attempt to modify a create-only element after object creation. Rule 7: Data elements with mutability read-write have no additional annotation. They MAY appear in both request and response bodies. Wullink & Kowalik Expires 17 December 2026 [Page 8] Internet-Draft JSON for RPP June 2026 4.4. Association Rules The RPP data model defines several association types between objects, the following rules specify their JSON representations. A Aggregation represents a relationship between two independent objects, where one object references another. A Composition represents a parent-child relationship where the child object is embedded within the parent object and cannot exist independently. 4.4.1. Labelled associations Some associations between objects carry a string label that provides additional context for the relationship. The label is not an identifier of the target object, but rather a descriptor of the association itself. Labelled associations can occur in both aggregations and compositions. When representing labelled associations in JSON, the property label MUST be included alongside the reference to the target object. A property with the name object MUST be used to contain the reference to the target object, which can be either limited representation containing at minimum the primary object identifier for aggregations or an embedded object for compositions. 4.4.2. Aggregation An Aggregation[Type] represents a relationship between two independent objects. When the cardinality allows more than one target, it MUST be represented as a JSON array. Each element of the array MUST be the identifier of the referenced object. Rule 8: Aggregation[Type] with cardinality 0+ or 1+ MUST be represented as a JSON array of embedded objects. Each object in the array MUST include the data elements of the referenced object type that are relevant to the context (at minimum the primary identifier field). Other data elements of the referenced object type MAY be included as needed to provide additional context for the client, but are not required. The JSON Schema MUST allow for the presence of these additional fields. Example: domain nameservers (Aggregation[Host Data Object]) in a read response, returning a limited object representation, only cvontaining the primary identifier field hostName: Wullink & Kowalik Expires 17 December 2026 [Page 9] Internet-Draft JSON for RPP June 2026 { "@type": "domainName", "name": "name.example", "nameservers": [ { "@type": "host", "hostName": "ns1.name.example" }, { "@type": "host", "hostName": "ns2.name.example" } ] } 4.4.3. Composition A Composition[Type] represents a parent-child relationship where the child's lifecycle is bound to the parent and the child cannot exist independently of the parent. In JSON, the child object MUST be fully embedded within the parent object. The JSON representation of a composition is the same as that of an aggregation. The distinction between the two is semantic and does not affect the JSON structure. Wullink & Kowalik Expires 17 December 2026 [Page 10] Internet-Draft JSON for RPP June 2026 { "@type": "domainName", "name": "name.example", "nameservers": [ { "@type": "host", "hostName": "ns1.name.example", "provMetadata": { "@type": "provMetadata", "repositoryId": "NS1EXAMPLE-REP", "spClientId": "ClientX" }, "status": [ { "@type": "status", "label": "ok" } ], "dns": { "@type": "dnsData", "records": [ { "@type": "dnsRecord", "name": "@", "type": "ns", "rdata": { "nsdname": "ns1.name.example." } }, { "@type": "dnsRecord", "name": "ns1.name.example.", "type": "a", "rdata": { "address": "192.0.2.1" } } ] } } ] } 4.4.4. Labelled Aggregation A LabelledAggregation[Type] is a relationship between two independent objects where each association carries a string label. Multiple associations with the same label are allowed. Rule 9: LabelledAggregation[Type] with cardinality 0+ MUST be represented as a JSON array of objects. Each object in the array MUST contain a label property (string) alongside the identifier of the referenced object. The object MUST include at least the primary identifier field of the referenced object type. Other data elements of the referenced object type MAY be included as needed to provide additional context for the client, but are not required. The JSON Schema MUST allow for the presence of these additional fields. Wullink & Kowalik Expires 17 December 2026 [Page 11] Internet-Draft JSON for RPP June 2026 Example: domain contacts (LabelledAggregation[Contact Object]): "contacts": [ { "label": "admin", "object": { "@type": "contact", "id": "ABC-8013" } }, { "label": "tech", "object": { "@type": "contact", "id": "ABC-8014" } } ] 4.4.5. Dictionary Aggregation A DictionaryAggregation[Type] is a relationship between two independent objects where each association carries a unique string label that serves as a dictionary key. Rule 10: DictionaryAggregation[Type] MUST be represented as a JSON object where each key is the unique label and the corresponding value is the referenced object, the object MUST include at least the primary identifier field of the referenced object type. Other data elements of the referenced object type MAY be included as needed to provide additional context for the client, but are not required. The JSON Schema MUST allow for the presence of these additional fields. Example: domain contacts keyed by unique role (DictionaryAggregation[Contact Object]): "contacts": { "admin": { "@type": "contact", "id": "ABC-8013" }, "tech": { "@type": "contact", "id": "ABC-8014" } } Wullink & Kowalik Expires 17 December 2026 [Page 12] Internet-Draft JSON for RPP June 2026 4.4.6. Labelled Composition A LabelledComposition[Type] is a parent-child relationship where each embedded child carries a string label. Multiple instances with the same label are allowed. Rule 11: LabelledComposition[Type] with cardinality 0+ MUST be represented as a JSON array of embedded objects. Each object in the array MUST contain a label property alongside the data elements of the composed type. Example: contact postal info (LabelledComposition[Contact Object]): "contacts": [ { "label": "admin", "object": { "@type": "contact", "id": "jd1234", "postalInfo": { "int": { "@type": "postalInfo", "type": "PERSON", "name": "John Doe", "org": "Example Inc.", "blah": "ffo", "addr": { "@type": "postalData", "street": [ "123 Example Dr.", "Suite 100" ], "city": "Dulles", "sp": "VA", "pc": "20166-6503", "cc": "US" } } }, "voice": ["+1.7035555555"], "fax": ["+1.7035555556"], "email": ["jdoe@example.example"] } } ] Wullink & Kowalik Expires 17 December 2026 [Page 13] Internet-Draft JSON for RPP June 2026 4.4.7. Dictionary Composition A DictionaryComposition[Type] is a parent-child relationship where each embedded child carries a unique string label used as a dictionary key. Rule 12: DictionaryComposition[Type] MUST be represented as a JSON object where each key is the unique label and the corresponding value is the fully embedded child object. Example: contact postal info (DictionaryComposition[Postal Info Object]): "addresses": { "int": { "@type": "postalInfo", "type": "PERSON", "name": "John Doe", "addr": { "@type": "postalData", "street": ["123 Example Dr."], "city": "Dulles", "sp": "VA", "pc": "20166-6503", "cc": "US" } }, "loc": { ... } } 4.5. Object Identifier Rules Rule 13: When a resource or component object is referenced by identifier (for example in an aggregation), the identifier MUST be represented as a JSON string using the value of the object's primary identifier data element. Rule 14: When a resource or component object is embedded (as in a composition), all data elements of the object MUST be represented as properties of a JSON object according to the rules of this section. 4.6. JSON Schema Definition Rules Rule 15: Each RPP component object and resource object MUST have a corresponding JSON Schema definition. Object definitions MUST be placed in the $defs keyword of the JSON Schema document. Wullink & Kowalik Expires 17 December 2026 [Page 14] Internet-Draft JSON for RPP June 2026 Rule 16: Identifier fields MUST use "type": "string" in JSON Schema. Rule 17: Enumeration constraints on string fields MUST be expressed using the "enum" keyword in JSON Schema. Example (Transfer Status enum): "trStatus": { "type": "string", "enum": ["pending", "clientApproved", "clientCancelled", "clientRejected", "serverApproved", "serverCancelled"] } Rule 18: Each JSON Schema definition for an RPP object MUST include a "required" array listing all data elements with cardinality 1 or 1+. Rule 19: JSON Schema definitions for extendible RPP objects MUST NOT use "additionalProperties": false or "unevaluatedProperties": false. However, before validation, schemas on every property level MUST be enriched with "unevaluatedProperties": false property to prevent the presence of undeclared properties in JSON instances. JSON Schemas for Object type MAY use "additionalProperties": true to allow for free key definition. Rule 20: Every RPP object representation MUST include a "@type" property whose value is the object's identifier as registered in the IANA RPP Data Object Registry. This property enables identification and allows clients and servers to unambiguously determine the type of an object. The "@type" property MUST be included in the JSON Schema "properties" object for each RPP object definition with a "const" constraint fixing the value to the object's registered identifier. The "@type" property MUST be listed in the "required" array of the corresponding JSON Schema definition. Example (Domain Name Data Object): { "@type": "domainName", "name": "example.example" } Wullink & Kowalik Expires 17 December 2026 [Page 15] Internet-Draft JSON for RPP June 2026 Rule 21: When a transfer request or other operation requires authorization information (e.g., EPP-style authinfo), the client MUST NOT include the authInfo object in the JSON request body. Instead, the client MUST convey the authorization information using the RPP- Authorization HTTP request header as defined in [I-D.wullink-rpp-core]. Servers MUST reject any request that includes an authInfo object in the JSON body with an appropriate error response. 4.6.1. RPP Profiles and Validation RPP profiles, such as the EPP Compatibility Profile defined in [I-D.kowalik-rpp-data-objects], may impose additional constraints on top of the base RPP data model. These additional constraints MUST be enforced by implementations through validation rules that go beyond what can be expressed in JSON Schema. Such validation rules MUST be clearly documented in the profile specification and implemented by both clients and servers when operating under that profile. For example, the EPP Compatibility Profile requires that certain fields be present in specific object types, and that certain identifier fields conform to EPP syntax rules. These constraints cannot be fully captured in JSON Schema and therefore require additional validation logic in implementations. 5. JSON Schema Definitions This section provides normative JSON Schema definitions for RPP component objects and resource objects. All schemas use JSON Schema draft 2020-12 [JSON-SCHEMA]. 5.1. Common Data Types Schemas This section defines shared data types that are based on the primitive data types above and are re-used across multiple data object definitions. 5.1.1. Identifier Identifiers are character strings with a specified minimum length, a specified maximum length, and a specified format outlined in Section 2.8 of [RFC5730]. Identifiers for certain object types MAY have additional constraints imposed either by server policy, object- specific specifications, or both. Wullink & Kowalik Expires 17 December 2026 [Page 16] Internet-Draft JSON for RPP June 2026 5.1.2. Client Identifier Client identifiers are character strings with a specified minimum length, a specified maximum length, and a specified format. Client identifiers use the clIDType syntax described in [RFC5730]. In JSON, a Client Identifier MUST be represented as a string value. { "$defs": { "clientIdentifier": { "type": "string", "minLength": 3, "maxLength": 16, "pattern": "^[a-zA-Z0-9]([-a-zA-Z0-9]*[a-zA-Z0-9])?$" } } } 5.1.3. Phone Number Telephone number syntax is derived from structures defined in [ITU.E164.2005]. Telephone numbers described in this specification are character strings that MUST begin with a plus sign ("+", ASCII value 0x002B), followed by a country code defined in [ITU.E164.2005], followed by a dot (".", ASCII value 0x002E), followed by a sequence of digits representing the telephone number. An optional "x" (ASCII value 0x0078) separator with additional digits representing extension information can be appended to the end of the value. In JSON, a Phone Number MUST be represented as a string value conforming to the pattern described above. { "$defs": { "phoneNumber": { "type": "string", "pattern": "^\\+[0-9]{1,3}\\.[0-9]+( x[0-9]+)?$" } } } 5.2. Component Objects Schemas 5.2.1. Period Object Wullink & Kowalik Expires 17 December 2026 [Page 17] Internet-Draft JSON for RPP June 2026 { "$defs": { "period": { "type": "object", "properties": { "@type": { "type": "string", "const": "period" }, "value": { "type": "integer", "minimum": 1, "maximum": 99 }, "unit": { "type": "string", "enum": ["y", "m"] } }, "required": ["@type", "value", "unit"] } } } 5.2.2. Provisioning Metadata Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * upClientId and upDate MUST NOT be present if the object has never been modified. * trDate MUST NOT be present if the object has never been transferred. * In EPP Compatibility Profile, repositoryId MUST be provided. Wullink & Kowalik Expires 17 December 2026 [Page 18] Internet-Draft JSON for RPP June 2026 { "$defs": { "provMetadata": { "type": "object", "properties": { "@type": { "type": "string", "const": "provMetadata", "readOnly": true }, "repositoryId": { "type": "string", "readOnly": true }, "spClientId": { "$ref": "#/$defs/clientIdentifier", "readOnly": true }, "crClientId": { "$ref": "#/$defs/clientIdentifier", "readOnly": true }, "crDate": { "type": "string", "format": "date-time", "readOnly": true }, "upClientId": { "$ref": "#/$defs/clientIdentifier", "readOnly": true }, "upDate": { "type": "string", "format": "date-time", "readOnly": true }, "trDate": { "type": "string", "format": "date-time", "readOnly": true } }, "required": ["@type", "spClientId"] } } } 5.2.3. Status Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * label MUST use camelCase notation using only ASCII alphabetic characters. Labels set explicitly by the server MUST use the prefix "server"; labels set explicitly by a client MUST use the prefix "client"; all other labels MUST NOT use either prefix. The allowed set of label values depends on the provisioning object type and MAY be extended by extensions. * due: Servers MAY restrict the ability of clients to set or update this value. * When the RGP feature is supported, the following additional status labels MAY appear on objects that support RGP: addPeriod, autoRenewPeriod, renewPeriod, transferPeriod, redemptionPeriod, pendingRestore, rgpPendingDelete. The labels redemptionPeriod, pendingRestore, and rgpPendingDelete MUST only appear alongside the standard pendingDelete status. Wullink & Kowalik Expires 17 December 2026 [Page 19] Internet-Draft JSON for RPP June 2026 { "$defs": { "status": { "type": "object", "properties": { "@type": { "type": "string", "const": "status" }, "label": { "type": "string", "pattern": "^[a-zA-Z]+$" }, "reason": { "type": "string" }, "due": { "type": "string", "format": "date-time" } }, "required": ["@type", "label"] } } } 5.2.4. DNS Resource Record Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * name MUST be a syntactically valid DNS host name in zone file string representation. Both absolute FQDNs (with trailing dot) and relative host names are allowed, as well as the @ symbol representing the domain name itself. * type MUST be a valid string representation of a DNS resource record type as defined in [RFC1035]. Values MUST be converted to lower case. Allowed values MAY be further constrained by server policy. * In EPP Compatibility Profile ([RFC5732]), the following record types MUST be supported: ns, a, and aaaa. With DNSSEC Extension [RFC5910], ds and dnskey MUST additionally be supported. * class, if present, MUST be chosen from Section 3.2.4 (CLASS values) of [RFC1035]. A client SHOULD omit this element; the server MUST assume IN as the default. * The fields within rdata MUST match the expected structure for the given record type (see RDATA structures below). RDATA structures required in EPP Compatibility Profile: * NS records ([RFC1035], Section 3.3.11): nsdname * A records ([RFC1035], Section 3.4.1): address * AAAA records ([RFC3596], Section 2.2): address * DS records ([RFC4034], Section 5, with DNSSEC Extension): keyTag, algorithm, digestType, digest * DNSKEY records ([RFC4034], Section 2, with DNSSEC Extension): flags, protocol, algorithm, publicKey Wullink & Kowalik Expires 17 December 2026 [Page 20] Internet-Draft JSON for RPP June 2026 All rdata property names MUST be written in camelCase and all values MUST use the string data type. { "$defs": { "dnsRecord": { "type": "object", "properties": { "@type": { "type": "string", "const": "dnsRecord" }, "name": { "type": "string" }, "class": { "type": "string" }, "type": { "type": "string" }, "rdata": { "type": "object", "unevaluatedProperties": true } }, "required": ["@type", "name", "type", "rdata"] } } } 5.2.5. DNS Operational Controls Object The DNS Operational Controls Object contains operational control parameters that a client MAY use to influence server-side DNS behaviour for a set of DNS records. A server MAY ignore these values, e.g. for policy reasons. This structure is aligned with [I-D.simmen-rpp-dns-data]. Wullink & Kowalik Expires 17 December 2026 [Page 21] Internet-Draft JSON for RPP June 2026 { "$defs": { "dnsControls": { "type": "object", "properties": { "@type": { "type": "string", "const": "dnsControls" }, "ttl": { "type": "object", "propertyNames": { "pattern": "^[a-z]+$" }, "additionalProperties": { "type": "integer", "minimum": 1 } }, "maxSigLifetime": { "type": "object", "propertyNames": { "pattern": "^[a-z]+$" }, "additionalProperties": { "type": "integer", "minimum": 1 } } }, "required": ["@type"] } } } 5.2.6. DNS Data Object The DNS Data Object is a container for DNS resource records and associated operational controls for a provisioned object. This structure groups DNS records together with control parameters that influence server-side DNS behaviour. It is aligned with [I-D.simmen-rpp-dns-data]. The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * In EPP Compatibility Profile with DNSSEC Extension [RFC5910], records of type ds and dnskey MUST be supported in addition to ns, a, and aaaa. A server MUST support either ds or dnskey or both. If provided with only dnskey, a server MUST calculate the DS record. Wullink & Kowalik Expires 17 December 2026 [Page 22] Internet-Draft JSON for RPP June 2026 { "$defs": { "dnsData": { "type": "object", "properties": { "@type": { "type": "string", "const": "dnsData" }, "records": { "type": "array", "items": { "$ref": "#/$defs/dnsRecord" } }, "controls": { "$ref": "#/$defs/dnsControls" } }, "required": ["@type"] } } } 5.2.7. Authorisation Information Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * method MUST be one of the values registered in the IANA RPP Authorisation Method Registry as defined in [I-D.wullink-rpp-core]. In EPP Compatibility Profile, this value MUST be "authinfo" for standard password-based authorisation. * The Authorisation Information Object is immutable. When authorisation information changes, a new instance MUST be created rather than modifying the existing one. The value of authdata MAY not be returned in read responses, depending on the method and server policy. { "$defs": { "authInfo": { "type": "object", "properties": { "@type": { "type": "string", "const": "authInfo" }, "method": { "type": "string" }, "authdata": { "type": "string" } }, "required": ["@type", "method", "authdata"] } } } Wullink & Kowalik Expires 17 December 2026 [Page 23] Internet-Draft JSON for RPP June 2026 5.2.8. Postal Address Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * cc MUST be a valid two-character country code from [ISO3166-1]. The JSON Schema pattern enforces uppercase alpha-2 format. * In EPP Compatibility Profile, city and cc MUST be provided. { "$defs": { "postalData": { "type": "object", "properties": { "@type": { "type": "string", "const": "postalData" }, "street": { "type": "array", "items": { "type": "string" } }, "city": { "type": "string" }, "sp": { "type": "string" }, "pc": { "type": "string" }, "cc": { "type": "string", "pattern": "^[A-Z]{2}$" } }, "required": ["@type"] } } } 5.2.9. Postal Info Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * name MAY be required by implementations when type is "PERSON". In EPP Compatibility Profile, name MUST be provided. * org MAY be required by implementations when type is "ORG". * In EPP Compatibility Profile, addr MUST be provided. Wullink & Kowalik Expires 17 December 2026 [Page 24] Internet-Draft JSON for RPP June 2026 { "$defs": { "postalInfo": { "type": "object", "properties": { "@type": { "type": "string", "const": "postalInfo" }, "type": { "type": "string", "enum": ["PERSON", "ORG"] }, "name": { "type": "string" }, "org": { "type": "string" }, "addr": { "$ref": "#/$defs/postalData" } }, "required": ["@type"] } } } 5.2.10. Restore Report Object The Restore Report Object contains the redemption grace period restore report submitted by the sponsoring client as required by the RGP process ([RFC3915]). The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * At least one and at most two statements MUST be provided. * restoreTime MAY be omitted when the restore report is submitted inline within the restore request in a single-step process. * In EPP Compatibility Profile, restoreTime MUST be present as defined in [RFC3915]. * In EPP Compatibility Profile, exactly two statements MUST be present as defined in [RFC3915]. Wullink & Kowalik Expires 17 December 2026 [Page 25] Internet-Draft JSON for RPP June 2026 { "$defs": { "restoreReport": { "type": "object", "properties": { "@type": { "type": "string", "const": "restoreReport" }, "preData": { "type": "string" }, "postData": { "type": "string" }, "deleteTime": { "type": "string", "format": "date-time" }, "restoreTime": { "type": "string", "format": "date-time" }, "restoreReason": { "type": "string" }, "statements": { "type": "array", "items": { "type": "string" }, "minItems": 1, "maxItems": 2 }, "other": { "type": "string" } }, "required": ["@type", "statements"] } } } 5.3. Process Object Schemas 5.3.1. Transfer Process Object Create request schema (create-only and read-write properties): Wullink & Kowalik Expires 17 December 2026 [Page 26] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/transferProcess.create", "$defs": { "transferProcess.create": { "type": "object", "oneOf": [ { "properties": { "@type": { "type": "string", "const": "transferProcess"}, "transferDir": { "type": "string", "const": "push" }, "gainingClientId": { "$ref": "#/$defs/clientIdentifier" } }, "required": [ "@type", "transferDir", "gainingClientId" ] }, { "properties": { "@type": { "type": "string", "const": "transferProcess" }, "transferDir": { "type": "string", "const": "pull" } }, "required": [ "@type", "transferDir" ] } ] } } } Create request for Domain Object schema (create-only and read-write properties): Wullink & Kowalik Expires 17 December 2026 [Page 27] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/transferProcess.create.domain", "$defs": { "transferProcess.create.domain": { "allOf": [ { "$ref": "#/$defs/transferProcess.create" }, { "properties": { "transferPeriod": { "$ref": "#/$defs/period" } } } ] } } } Read response schema (read-write and read-only properties): Wullink & Kowalik Expires 17 December 2026 [Page 28] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/transferProcess.read", "$defs": { "transferProcess.read": { "type": "object", "properties": { "@type": { "type": "string", "const": "transferProcess", "readOnly": true }, "trStatus": { "type": "string", "enum": ["pending", "clientApproved", "clientCancelled", "clientRejected", "serverApproved", "serverCancelled"], "readOnly": true }, "transferDir": { "type": "string", "enum": ["pull", "push"], "readOnly": true }, "gainingClientId": { "$ref": "#/$defs/clientIdentifier", "readOnly": true }, "reqClientId": { "$ref": "#/$defs/clientIdentifier", "readOnly": true}, "requestDate": { "type": "string", "format": "date-time", "readOnly": true }, "actClientId": { "$ref": "#/$defs/clientIdentifier", "readOnly": true }, "actionDate": { "type": "string", "format": "date-time", "readOnly": true } }, "required": [ "@type", "transferDir", "trStatus", "reqClientId", "requestDate", "actClientId", "actionDate" ] } } } Read response for Domain Object schema (read-write and read-only properties): Wullink & Kowalik Expires 17 December 2026 [Page 29] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/transferProcess.read.domain", "$defs": { "transferProcess.read.domain": { "allOf": [ { "$ref": "#/$defs/transferProcess.read" }, { "properties": { "expiryDate": { "type": "string", "format": "date-time", "readOnly": true } } } ] } } } 5.3.2. Restore Process Object The Restore Process Object represents the current state of a restore request for an object that has entered the Redemption Grace Period (RGP). It is returned as a response for all restore operations. The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * requestDate MUST NOT be present if no restore request has been submitted yet. * reportDate MUST NOT be present if no restore report has been accepted yet. * reportDueDate MUST NOT be present when restoreStatus is not "pendingRestore". Create request schema (create-only and read-write properties): Wullink & Kowalik Expires 17 December 2026 [Page 30] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/restoreProcess.create", "$defs": { "restoreProcess.create": { "type": "object", "properties": { "@type": { "type": "string", "const": "restoreProcess" }, "restoreReport": { "$ref": "#/$defs/restoreReport" } }, "required": ["@type"] } } } Read response schema (read-write and read-only properties): { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/restoreProcess.read", "$defs": { "restoreProcess.read": { "type": "object", "properties": { "@type": { "type": "string", "const": "restoreProcess", "readOnly": true }, "restoreStatus": { "type": "string", "enum": ["pendingRestore", "restored", "rgpPendingDelete"], "readOnly": true }, "requestDate": { "type": "string", "format": "date-time", "readOnly": true }, "reportDate": { "type": "string", "format": "date-time", "readOnly": true }, "reportDueDate": { "type": "string", "format": "date-time", "readOnly": true } }, "required": ["@type", "restoreStatus"] } } } 5.4. Domain Name Data Object The Domain Name Data Object represents a domain name and its associated provisioning data. The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: Wullink & Kowalik Expires 17 December 2026 [Page 31] Internet-Draft JSON for RPP June 2026 * name MUST be a fully qualified domain name conforming to the syntax described in [RFC1035]. Servers MAY restrict allowable domain names to a specific namespace for which they are authoritative. The implicit trailing dot MUST NOT be included. Create request schema (create-only and read-write properties): { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/domainObject.create", "$defs": { "domainObject.create": { "type": "object", "properties": { "@type": { "type": "string", "const": "domainName" }, "name": { "type": "string", "writeOnly": true }, "registrant": { "$ref": "#/$defs/contactObject.reference" }, "contacts": { "type": "array", "items": { "type": "object", "properties": { "label": { "type": "string" }, "object": { "$ref": "#/$defs/contactObject.reference" } }, "required": ["label", "object"] } }, "nameservers": { "type": "array", "items": { "$ref": "#/$defs/hostObject.reference" } }, "dns": { "$ref": "#/$defs/dnsData" }, "authInfo": { "$ref": "#/$defs/authInfo" }, "period": { "$ref": "#/$defs/period" } }, "required": ["@type", "name"] } } } Read response schema (read-write and read-only properties): Wullink & Kowalik Expires 17 December 2026 [Page 32] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/domainObject.read", "$defs": { "domainObject.read": { "type": "object", "properties": { "@type": { "type": "string", "const": "domainName", "readOnly": true }, "name": { "type": "string", "readOnly": true }, "provMetadata": { "$ref": "#/$defs/provMetadata" }, "status": { "type": "array", "items": { "$ref": "#/$defs/status" }, "readOnly": true }, "registrant": { "$ref": "#/$defs/contactObject.reference" }, "contacts": { "type": "array", "items": { "type": "object", "properties": { "label": { "type": "string" }, "object": { "$ref": "#/$defs/contactObject.reference" } }, "required": ["label", "object"] } }, "nameservers": { "type": "array", "items": { "$ref": "#/$defs/hostObject.reference" } }, "dns": { "$ref": "#/$defs/dnsData" }, "subordinateHosts": { "type": "array", "items": { "$ref": "#/$defs/hostObject.reference" }, "readOnly": true }, "expiryDate": { "type": "string", "format": "date-time", "readOnly": true }, "authInfo": { "$ref": "#/$defs/authInfo" } }, "required": ["@type", "name", "provMetadata"] } } } Reference schema (identifier only): Wullink & Kowalik Expires 17 December 2026 [Page 33] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/domainObject.reference", "$defs": { "domainObject.reference": { "type": "object", "properties": { "@type": { "type": "string", "const": "domainName", "readOnly": true }, "name": { "type": "string", "readOnly": true } }, "required": ["@type", "name"] } } } 5.5. Contact Data Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * postalInfo keys MUST be either "int" (internationalised, all- ASCII) or "loc" (localised, MAY use non-ASCII characters). At most one entry of each key is allowed. Create request schema (create-only and read-write properties): Wullink & Kowalik Expires 17 December 2026 [Page 34] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/contactObject.create", "$defs": { "contactObject.create": { "type": "object", "properties": { "@type": { "type": "string", "const": "contact" }, "id": { "type": "string", "writeOnly": true }, "postalInfo": { "type": "object", "additionalProperties": { "$ref": "#/$defs/postalInfo" }, "minProperties": 1, "maxProperties": 2 }, "voice": { "type": "array", "items": { "$ref": "#/$defs/phoneNumber" } }, "fax": { "type": "array", "items": { "$ref": "#/$defs/phoneNumber" } }, "email": { "type": "array", "items": { "type": "string", "format": "email" } }, "authInfo": { "$ref": "#/$defs/authInfo" }, "disclose": { "type": "object" } }, "required": ["@type", "id", "postalInfo"] } } } Read response schema (read-write and read-only properties): Wullink & Kowalik Expires 17 December 2026 [Page 35] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/contactObject.read", "$defs": { "contactObject.read": { "type": "object", "properties": { "@type": { "type": "string", "const": "contact", "readOnly": true }, "id": { "type": "string", "readOnly": true }, "provMetadata": { "$ref": "#/$defs/provMetadata" }, "status": { "type": "array", "items": { "$ref": "#/$defs/status" }, "readOnly": true }, "postalInfo": { "type": "object", "additionalProperties": { "$ref": "#/$defs/postalInfo" }, "minProperties": 1, "maxProperties": 2 }, "voice": { "type": "array", "items": { "$ref": "#/$defs/phoneNumber" } }, "fax": { "type": "array", "items": { "$ref": "#/$defs/phoneNumber" } }, "email": { "type": "array", "items": { "type": "string", "format": "email" } }, "authInfo": { "$ref": "#/$defs/authInfo" }, "disclose": { "type": "object" } }, "required": ["@type", "id", "provMetadata", "postalInfo"] } } } Reference schema (identifier only): Wullink & Kowalik Expires 17 December 2026 [Page 36] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/contactObject.reference", "$defs": { "contactObject.reference": { "type": "object", "properties": { "@type": { "type": "string", "const": "contact", "readOnly": true }, "id": { "type": "string", "readOnly": true } }, "required": ["@type", "id"] } } } 5.6. Host Data Object The following constraints cannot be expressed in JSON Schema and MUST be enforced by implementations: * hostName MUST be a syntactically valid fully qualified host name. * If the host name is subordinate to a domain for which the server is authoritative, the superordinate domain MUST already exist in the server. Create request schema (create-only and read-write properties): { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/hostObject.create", "$defs": { "hostObject.create": { "type": "object", "properties": { "@type": { "type": "string", "const": "host" }, "hostName": { "type": "string", "format": "hostname" }, "dns": { "$ref": "#/$defs/dnsData" } }, "required": ["@type", "hostName"] } } } Read response schema (read-write and read-only properties): Wullink & Kowalik Expires 17 December 2026 [Page 37] Internet-Draft JSON for RPP June 2026 { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/hostObject.read", "$defs": { "hostObject.read": { "type": "object", "properties": { "@type": { "type": "string", "const": "host", "readOnly": true }, "hostName": { "type": "string", "format": "hostname" }, "provMetadata": { "$ref": "#/$defs/provMetadata" }, "status": { "type": "array", "items": { "$ref": "#/$defs/status" }, "readOnly": true }, "dns": { "$ref": "#/$defs/dnsData" } }, "required": ["@type", "hostName", "provMetadata"] } } } Reference schema (identifier only): { "$schema": "https://json-schema.org/draft/2020-12/schema", "$ref": "#/$defs/hostObject.reference", "$defs": { "hostObject.reference": { "type": "object", "properties": { "@type": { "type": "string", "const": "host", "readOnly": true }, "hostName": { "type": "string", "format": "hostname", "readOnly": true } }, "required": ["@type", "hostName"] } } } 5.7. Organisation Data Object TBD Wullink & Kowalik Expires 17 December 2026 [Page 38] Internet-Draft JSON for RPP June 2026 6. Examples This section provides examples that follow the JSON representation rules and JSON Schema definitions specified in the previous sections. The examples illustrate typical request and response messages for domain name, contact, and host resources. 6.1. Domain Name 6.1.1. Create Example domain create request: { "@type": "domainName", "name": "example.example", "period": { "@type": "period", "value": 2, "unit": "y" }, "nameservers": [ { "@type": "host", "hostName": "ns1.example.example" }, { "@type": "host", "hostName": "ns2.example.example" } ], "registrant": { "@type": "contact", "id": "jd1234" }, "contacts": [ { "label": "admin", "object": { "@type": "contact", "id": "sh8013" } }, { "label": "tech", "object": { "@type": "contact", "id": "sh8013" } } ], "authInfo": { "@type": "authInfo", "method": "authinfo", "authdata": "2fooBAR" } } Example domain create response from a server with RGP support: Wullink & Kowalik Expires 17 December 2026 [Page 39] Internet-Draft JSON for RPP June 2026 { "@type": "domainName", "name": "example.example", "provMetadata": { "@type": "provMetadata", "repositoryId": "EXAMPLE1-REP", "spClientId": "ClientX", "crClientId": "ClientX", "crDate": "1999-04-03T22:00:00.0Z" }, "status": [ { "@type": "status", "label": "ok" }, { "@type": "status", "label": "addPeriod" } ], "expiryDate": "2001-04-03T22:00:00.0Z" } 6.1.2. Read Example domain read response: { "@type": "domainName", "name": "example.example", "provMetadata": { "@type": "provMetadata", "repositoryId": "EXAMPLE1-REP", "spClientId": "ClientX", "crClientId": "ClientY", "crDate": "1999-04-03T22:00:00.0Z", "upClientId": "ClientX", "upDate": "1999-12-03T09:00:00.0Z", "trDate": "2000-04-08T09:00:00.0Z" }, "status": [ { "@type": "status", "label": "ok" } ], "registrant": { "@type": "contact", "id": "jd1234" }, "contacts": [ { "label": "admin", "object": { "@type": "contact", "id": "sh8013" } }, { "label": "tech", "object": { "@type": "contact", "id": "sh8013" } } ], "nameservers": [ { "@type": "host", "hostName": "ns1.example.example" }, { Wullink & Kowalik Expires 17 December 2026 [Page 40] Internet-Draft JSON for RPP June 2026 "@type": "host", "hostName": "ns2.example.example" } ], "subordinateHosts": [ { "@type": "host", "hostName": "ns1.example.example" }, { "@type": "host", "hostName": "ns2.example.example" } ], "expiryDate": "2005-04-03T22:00:00.0Z", "authInfo": { "@type": "authInfo", "method": "authinfo", "authdata": "2fooBAR" } } 6.1.3. Update Example domain update request (read-write properties): { "@type": "domainName", "registrant": { "@type": "contact", "id": "sh8013" }, "authInfo": { "@type": "authInfo", "method": "authinfo", "authdata": "2BARfoo" } } Example domain update response: Wullink & Kowalik Expires 17 December 2026 [Page 41] Internet-Draft JSON for RPP June 2026 { "@type": "domainName", "name": "example.example", "provMetadata": { "@type": "provMetadata", "repositoryId": "EXAMPLE1-REP", "spClientId": "ClientX", "crClientId": "ClientY", "crDate": "1999-04-03T22:00:00.0Z", "upClientId": "ClientX", "upDate": "2000-01-15T09:00:00.0Z" }, "status": [ { "@type": "status", "label": "ok" } ], "registrant": { "@type": "contact", "id": "sh8013" } } 6.1.4. Delete The domain delete operation takes the domain name as the resource identifier in the request. No request body is required. Example domain delete response (minimal, server may return full representation): { "@type": "domainName", "name": "example.example", "provMetadata": { "@type": "provMetadata", "repositoryId": "EXAMPLE1-REP", "spClientId": "ClientX" } } 6.1.5. Renew The renew operation accepts a transient currentExpiryDate parameter for validation and an optional renewalPeriod. Example domain renew request: Wullink & Kowalik Expires 17 December 2026 [Page 42] Internet-Draft JSON for RPP June 2026 { "currentExpiryDate": "2005-04-03T22:00:00.0Z", "renewalPeriod": { "@type": "period", "value": 5, "unit": "y" } } Example domain renew response: { "@type": "domainName", "name": "example.example", "expiryDate": "2010-04-03T22:00:00.0Z" } 6.1.6. Transfer Request Authorization information for the transfer MUST be conveyed using the RPP-Authorization HTTP header (see Rule 21), not in the JSON request body. Example domain transfer request (pull transfer) { "@type": "transferProcess", "transferDir": "pull", "transferPeriod": { "@type": "period", "value": 1, "unit": "y" } } Example domain transfer response (Transfer Process Object): { "@type": "transferProcess", "trStatus": "pending", "transferDir": "pull", "reqClientId": "ClientX", "requestDate": "2000-06-08T22:00:00.0Z", "actClientId": "ClientY", "actionDate": "2000-06-13T22:00:00.0Z", "expiryDate": "2002-09-08T22:00:00.0Z" } Wullink & Kowalik Expires 17 December 2026 [Page 43] Internet-Draft JSON for RPP June 2026 6.1.7. Transfer Query Example domain transfer query response (Transfer Process Object): { "@type": "transferProcess", "trStatus": "pending", "transferDir": "pull", "reqClientId": "ClientX", "requestDate": "2000-06-06T22:00:00.0Z", "actClientId": "ClientY", "actionDate": "2000-06-11T22:00:00.0Z", "expiryDate": "2002-09-08T22:00:00.0Z" } 6.1.8. Transfer Cancel / Reject / Approve Transfer cancel, reject, and approve responses return the Transfer Process Object. The response structure is the same as the Transfer Query response above. The trStatus value reflects the outcome of the operation (e.g. "clientCancelled", "clientRejected", or "clientApproved"). 6.1.9. Restore Request Example domain restore request (without inline report; object transitions to pendingRestore state): { "@type": "restoreProcess" } Example domain restore response (Restore Process Object, server requires a report): { "@type": "restoreProcess", "restoreStatus": "pendingRestore", "requestDate": "2025-01-20T15:30:00.0Z", "reportDueDate": "2025-01-27T15:30:00.0Z" } Example domain restore request with inline restore report (single- step; object restored immediately): Wullink & Kowalik Expires 17 December 2026 [Page 44] Internet-Draft JSON for RPP June 2026 { "@type": "restoreProcess", "restoreReport": { "@type": "restoreReport", "preData": "Domain example.example was registered on 2024-01-15 with registrant jd1234.", "postData": "Domain example.example is being restored with the same registration data.", "deleteTime": "2025-01-10T12:00:00.0Z", "restoreTime": "2025-01-20T15:30:00.0Z", "restoreReason": "Domain deleted in error by client operator.", "statements": [ "The information in this report is true to the best of my knowledge.", "I have a valid reason for restoring this domain name." ] } } Example domain restore response with inline report (Restore Process Object, immediately restored): { "@type": "restoreProcess", "restoreStatus": "restored", "requestDate": "2025-01-20T15:30:00.0Z", "reportDate": "2025-01-20T15:30:00.0Z" } 6.1.10. Restore Report Example domain restore report request: { "@type": "restoreProcess", "restoreReport": { "@type": "restoreReport", "preData": "Domain example.example was registered on 2024-01-15 with registrant jd1234.", "postData": "Domain example.example is being restored with the same registration data.", "deleteTime": "2025-01-10T12:00:00.0Z", "restoreTime": "2025-01-20T15:30:00.0Z", "restoreReason": "Domain deleted in error by client operator.", "statements": [ "The information in this report is true to the best of my knowledge.", "I have a valid reason for restoring this domain name." ] } } Example domain restore report response (Restore Process Object): Wullink & Kowalik Expires 17 December 2026 [Page 45] Internet-Draft JSON for RPP June 2026 { "@type": "restoreProcess", "restoreStatus": "restored", "requestDate": "2025-01-20T15:30:00.0Z", "reportDate": "2025-01-22T09:15:00.0Z" } 6.1.11. Restore Query The Restore Query operation takes no request body (Parameters: None). Example domain restore query response (Restore Process Object, object in pendingRestore state): { "@type": "restoreProcess", "restoreStatus": "pendingRestore", "requestDate": "2025-01-20T15:30:00.0Z", "reportDueDate": "2025-01-27T15:30:00.0Z" } Example domain restore query response (Restore Process Object, object restored): { "@type": "restoreProcess", "restoreStatus": "restored", "requestDate": "2025-01-20T15:30:00.0Z", "reportDate": "2025-01-22T09:15:00.0Z" } 6.2. Contact 6.2.1. Create Example contact create request: Wullink & Kowalik Expires 17 December 2026 [Page 46] Internet-Draft JSON for RPP June 2026 { "@type": "contact", "id": "jd1234", "postalInfo": { "int": { "@type": "postalInfo", "type": "PERSON", "name": "John Doe", "org": "Example Inc.", "addr": { "@type": "postalData", "street": [ "123 Example Dr.", "Suite 100" ], "city": "Dulles", "sp": "VA", "pc": "20166-6503", "cc": "US" } } }, "voice": ["+1.7035555555"], "fax": ["+1.7035555556"], "email": ["jdoe@example.example"], "authInfo": { "@type": "authInfo", "method": "authinfo", "authdata": "2fooBAR" } } Example contact create response: Wullink & Kowalik Expires 17 December 2026 [Page 47] Internet-Draft JSON for RPP June 2026 { "@type": "contact", "id": "jd1234", "provMetadata": { "@type": "provMetadata", "repositoryId": "JD1234-REP", "spClientId": "ClientX", "crClientId": "ClientX", "crDate": "1999-04-03T22:00:00.0Z" }, "status": [ { "@type": "status", "label": "ok" } ], "postalInfo": { "int": { "@type": "postalInfo", "type": "PERSON", "name": "John Doe", "org": "Example Inc.", "addr": { "@type": "postalData", "street": [ "123 Example Dr.", "Suite 100" ], "city": "Dulles", "sp": "VA", "pc": "20166-6503", "cc": "US" } } }, "voice": ["+1.7035555555"], "fax": ["+1.7035555556"], "email": ["jdoe@example.example"] } 6.2.2. Read Example contact read response: Wullink & Kowalik Expires 17 December 2026 [Page 48] Internet-Draft JSON for RPP June 2026 { "@type": "contact", "id": "jd1234", "provMetadata": { "@type": "provMetadata", "repositoryId": "JD1234-REP", "spClientId": "ClientX", "crClientId": "ClientX", "crDate": "1999-04-03T22:00:00.0Z", "upClientId": "ClientX", "upDate": "2000-01-15T09:00:00.0Z" }, "status": [ { "@type": "status", "label": "ok" } ], "postalInfo": { "int": { "@type": "postalInfo", "type": "PERSON", "name": "John Doe", "org": "Example Inc.", "addr": { "@type": "postalData", "street": ["123 Example Dr.", "Suite 100"], "city": "Dulles", "sp": "VA", "pc": "20166-6503", "cc": "US" } } }, "voice": ["+1.7035555555"], "email": ["jdoe@example.example"] } 6.2.3. Update TBD 6.2.4. Delete The contact delete operation takes the contact identifier as the resource identifier. No request body is required. Wullink & Kowalik Expires 17 December 2026 [Page 49] Internet-Draft JSON for RPP June 2026 6.2.5. Transfer Request Authorization information for the transfer MUST be conveyed using the RPP-Authorization HTTP header (see Rule 21), not in the JSON request body. Example contact transfer request (pull transfer) { "@type": "transferProcess", "transferDir": "pull" } Example contact transfer response (Transfer Process Object): { "@type": "transferProcess", "trStatus": "pending", "transferDir": "pull", "reqClientId": "ClientX", "requestDate": "2000-06-08T22:00:00.0Z", "actClientId": "ClientY", "actionDate": "2000-06-13T22:00:00.0Z" } 6.2.6. Transfer Query Example contact transfer query response (Transfer Process Object): { "@type": "transferProcess", "trStatus": "pending", "transferDir": "pull", "reqClientId": "ClientX", "requestDate": "2000-06-06T22:00:00.0Z", "actClientId": "ClientY", "actionDate": "2000-06-11T22:00:00.0Z" } 6.2.7. Transfer Cancel / Reject / Approve Transfer cancel, reject, and approve responses return the Transfer Process Object. The response structure is the same as the Transfer Query response above. The trStatus value reflects the outcome of the operation (e.g. "clientCancelled", "clientRejected", or "clientApproved"). Wullink & Kowalik Expires 17 December 2026 [Page 50] Internet-Draft JSON for RPP June 2026 Note: Unlike domain transfers, contact transfers do not include an expiryDate field in the Transfer Process Object, as contacts do not have registration periods. 6.3. Host 6.3.1. Create Example host create request: { "@type": "host", "hostName": "ns1.example.example", "dns": { "@type": "dnsData", "records": [ { "@type": "dnsRecord", "name": "@", "type": "ns", "rdata": { "nsdname": "ns1.example.example." } }, { "@type": "dnsRecord", "name": "ns1.example.example.", "type": "a", "rdata": { "address": "192.0.2.1" } }, { "@type": "dnsRecord", "name": "ns1.example.example.", "type": "aaaa", "rdata": { "address": "2001:db8::1" } } ] } } Example host create response: Wullink & Kowalik Expires 17 December 2026 [Page 51] Internet-Draft JSON for RPP June 2026 { "@type": "host", "hostName": "ns1.example.example", "provMetadata": { "@type": "provMetadata", "repositoryId": "NS1EXAMPLE-REP", "spClientId": "ClientX", "crClientId": "ClientX", "crDate": "1999-04-03T22:00:00.0Z" }, "status": [ { "@type": "status", "label": "ok" } ], "dns": { "@type": "dnsData", "records": [ { "@type": "dnsRecord", "name": "@", "type": "ns", "rdata": { "nsdname": "ns1.example.example." } }, { "@type": "dnsRecord", "name": "ns1.example.example.", "type": "a", "rdata": { "address": "192.0.2.1" } }, { "@type": "dnsRecord", "name": "ns1.example.example.", "type": "aaaa", "rdata": { "address": "2001:db8::1" } } ] } } 6.3.2. Read Example host read response: Wullink & Kowalik Expires 17 December 2026 [Page 52] Internet-Draft JSON for RPP June 2026 { "@type": "host", "hostName": "ns1.example.example", "provMetadata": { "@type": "provMetadata", "repositoryId": "NS1EXAMPLE-REP", "spClientId": "ClientX", "crClientId": "ClientY", "crDate": "1999-04-03T22:00:00.0Z" }, "status": [ { "@type": "status", "label": "ok" } ], "dns": { "@type": "dnsData", "records": [ { "@type": "dnsRecord", "name": "@", "type": "ns", "rdata": { "nsdname": "ns1.example.example." } }, { "@type": "dnsRecord", "name": "ns1.example.example.", "type": "a", "rdata": { "address": "192.0.2.1" } } ] } } 6.3.3. Update Example host update request: Wullink & Kowalik Expires 17 December 2026 [Page 53] Internet-Draft JSON for RPP June 2026 { "@type": "host", "hostName": "ns1.example.example", "dns": { "@type": "dnsData", "records": [ { "@type": "dnsRecord", "name": "@", "type": "ns", "rdata": { "nsdname": "ns1.example.example." } }, { "@type": "dnsRecord", "name": "ns1.example.example.", "type": "a", "rdata": { "address": "198.51.100.1" } } ] } } 6.3.4. Delete The host delete operation takes the host name as the resource identifier. No request body is required. The server SHOULD reject the request if the host object is associated with any domain name objects. 6.3.5. Restore Request Example host restore request (without inline report; object transitions to pendingRestore state): { "@type": "restoreProcess" } Example host restore request response (Restore Process Object, server requires a report): { "@type": "restoreProcess", "restoreStatus": "pendingRestore", "requestDate": "2025-01-20T15:30:00.0Z", "reportDueDate": "2025-01-27T15:30:00.0Z" } Wullink & Kowalik Expires 17 December 2026 [Page 54] Internet-Draft JSON for RPP June 2026 Example host restore request with inline restore report (single-step; object restored immediately): { "@type": "restoreProcess", "restoreReport": { "@type": "restoreReport", "preData": "Host ns1.example.example was registered on 2024-01-15 by ClientX.", "postData": "Host ns1.example.example is being restored with the same registration data.", "deleteTime": "2025-01-10T12:00:00.0Z", "restoreTime": "2025-01-20T15:30:00.0Z", "restoreReason": "Host deleted in error by client operator.", "statements": [ "The information in this report is true to the best of my knowledge.", "I have a valid reason for restoring this host object." ] } } Example host restore response with inline report (Restore Process Object, immediately restored): { "@type": "restoreProcess", "restoreStatus": "restored", "requestDate": "2025-01-20T15:30:00.0Z", "reportDate": "2025-01-20T15:30:00.0Z" } 6.3.6. Restore Report Example host restore report request: { "@type": "restoreProcess", "restoreReport": { "@type": "restoreReport", "preData": "Host ns1.example.example was registered on 2024-01-15 by ClientX.", "postData": "Host ns1.example.example is being restored with the same registration data.", "deleteTime": "2025-01-10T12:00:00.0Z", "restoreTime": "2025-01-20T15:30:00.0Z", "restoreReason": "Host deleted in error by client operator.", "statements": [ "The information in this report is true to the best of my knowledge.", "I have a valid reason for restoring this host object." ] } } Wullink & Kowalik Expires 17 December 2026 [Page 55] Internet-Draft JSON for RPP June 2026 Example host restore report response (Restore Process Object): { "@type": "restoreProcess", "restoreStatus": "restored", "requestDate": "2025-01-20T15:30:00.0Z", "reportDate": "2025-01-22T09:15:00.0Z" } 6.3.7. Restore Query The Restore Query operation takes no request body (Parameters: None). Example host restore query response (Restore Process Object, object in pendingRestore state): { "@type": "restoreProcess", "restoreStatus": "pendingRestore", "requestDate": "2025-01-20T15:30:00.0Z", "reportDueDate": "2025-01-27T15:30:00.0Z" } Example host restore query response (Restore Process Object, object restored): { "@type": "restoreProcess", "restoreStatus": "restored", "requestDate": "2025-01-20T15:30:00.0Z", "reportDate": "2025-01-22T09:15:00.0Z" } 7. IANA Considerations TODO 8. Internationalization Considerations TODO 9. Security Considerations TODO Wullink & Kowalik Expires 17 December 2026 [Page 56] Internet-Draft JSON for RPP June 2026 10. Acknowledgments TODO 11. Change History 11.1. Version 01 to 02 * Sync JSON schemas and examples with the RPP Data Objects * Added RGP schemas and examples * Adjust rule 19 and all schemas to match it. 11.2. Version 00 to 01 * Updated all examples and schemas to be based on RPP Data Object and no longer on EPP XML schemas. (Issue #15) * Updated labelled and dictionary aggregation rules (Issue #17) * Added required "@type" property to all JSON Schema definitions. (Issue #20) * Updated all example domain names to use the .example TLD. (Issue #26) 12. References 12.1. Normative References [I-D.kowalik-rpp-data-objects] Kowalik, P. and M. Wullink, "RESTful Provisioning Protocol (RPP) Data Objects", Work in Progress, Internet-Draft, draft-kowalik-rpp-data-objects-04, 12 June 2026, . [I-D.wullink-rpp-core] Wullink, M. and P. Kowalik, "RESTful Provisioning Protocol (RPP)", Work in Progress, Internet-Draft, draft-wullink- rpp-core-05, 15 March 2026, . [ISO3166-1] International Organization for Standardization, "Codes for the representation of names of countries and their subdivisions - Part 1: Country code", ISO 3166-1:2020, 2020, . Wullink & Kowalik Expires 17 December 2026 [Page 57] Internet-Draft JSON for RPP June 2026 [ITU.E164.2005] International Telecommunication Union, "The international public telecommunication numbering plan", ITU-T Recommendation E.164, February 2005. [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, November 1987, . [RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, DOI 10.17487/RFC1738, December 1994, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, . [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, DOI 10.17487/RFC3915, September 2004, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, August 2009, . [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", STD 90, RFC 8259, DOI 10.17487/RFC8259, December 2017, . 12.2. Informative References [I-D.simmen-rpp-dns-data] Simmen, C. and P. Kowalik, "DNS data representation for use in RESTful Provisioning Protocol (RPP)", Work in Progress, Internet-Draft, draft-simmen-rpp-dns-data-01, 20 October 2025, . Wullink & Kowalik Expires 17 December 2026 [Page 58] Internet-Draft JSON for RPP June 2026 [JSON-SCHEMA] JSON Schema, "JSON Schema: A Media Type for Describing JSON Documents", 2020, . [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, "DNS Extensions to Support IP Version 6", STD 88, RFC 3596, DOI 10.17487/RFC3596, October 2003, . [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "Resource Records for the DNS Security Extensions", RFC 4034, DOI 10.17487/RFC4034, March 2005, . [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)", RFC 5910, DOI 10.17487/RFC5910, May 2010, . Authors' Addresses Maarten Wullink SIDN Labs Email: maarten.wullink@sidn.nl URI: https://sidn.nl/ Pawel Kowalik DENIC Email: pawel.kowalik@denic.de URI: https://denic.de/ Wullink & Kowalik Expires 17 December 2026 [Page 59]