Network Working Group                                         M. Wullink
Internet-Draft                                                 SIDN Labs
Intended status: Standards Track                              P. Kowalik
Expires: 24 April 2025                                             DENIC
                                                         21 October 2024


                  EPP XML to RPP JSON conversion rules
                       draft-wullink-rpp-json-00

Abstract

   This document describes the rules for converting The Extensible
   Provisioning Protocol (EPP) [RFC5730] XML based messages to a JSON
   [RFC8259] for use with the RESTful Provisioning Protocol (RPP).

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 24 April 2025.

Copyright Notice

   Copyright (c) 2024 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.





Wullink & Kowalik         Expires 24 April 2025                 [Page 1]

Internet-Draft             XML to JSON for RPP              October 2024


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Conventions Used in This Document . . . . . . . . . . . . . .   4
   4.  XSD Conversion Rules  . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Elements and Attributes . . . . . . . . . . . . . . . . .   5
     4.2.  Simple Types and Enumerations . . . . . . . . . . . . . .   6
     4.3.  Occurrence Constraints  . . . . . . . . . . . . . . . . .   7
     4.4.  Complex Types . . . . . . . . . . . . . . . . . . . . . .   9
     4.5.  Sequences . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.6.  Choices . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.7.  Mixed Content and Special Cases . . . . . . . . . . . . .  11
   5.  XML Conversion Rules  . . . . . . . . . . . . . . . . . . . .  13
     5.1.  Empty . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.2.  Pure text content . . . . . . . . . . . . . . . . . . . .  14
     5.3.  Attributes only . . . . . . . . . . . . . . . . . . . . .  14
     5.4.  Pure text content and attributes  . . . . . . . . . . . .  15
     5.5.  Child elements with different names . . . . . . . . . . .  15
     5.6.  Child elements with identical names . . . . . . . . . . .  16
     5.7.  Child elements and contiguous text  . . . . . . . . . . .  16
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  17
     6.1.  Hello . . . . . . . . . . . . . . . . . . . . . . . . . .  17
     6.2.  Login . . . . . . . . . . . . . . . . . . . . . . . . . .  19
     6.3.  Logout  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     6.4.  Check . . . . . . . . . . . . . . . . . . . . . . . . . .  19
     6.5.  Info  . . . . . . . . . . . . . . . . . . . . . . . . . .  20
     6.6.  Poll  . . . . . . . . . . . . . . . . . . . . . . . . . .  22
     6.7.  Poll Ack  . . . . . . . . . . . . . . . . . . . . . . . .  23
     6.8.  Transfer Query  . . . . . . . . . . . . . . . . . . . . .  24
     6.9.  Create  . . . . . . . . . . . . . . . . . . . . . . . . .  26
     6.10. Delete  . . . . . . . . . . . . . . . . . . . . . . . . .  30
     6.11. Renew . . . . . . . . . . . . . . . . . . . . . . . . . .  30
     6.12. Transfer Request  . . . . . . . . . . . . . . . . . . . .  32
     6.13. Transfer Cancel . . . . . . . . . . . . . . . . . . . . .  33
     6.14. Transfer Reject . . . . . . . . . . . . . . . . . . . . .  34
     6.15. Transfer Approve  . . . . . . . . . . . . . . . . . . . .  34
     6.16. Update  . . . . . . . . . . . . . . . . . . . . . . . . .  34
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  36
   8.  Internationalization Considerations . . . . . . . . . . . . .  36
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  36
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  36
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  37
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  37
     11.2.  Informative References . . . . . . . . . . . . . . . . .  37
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  37




Wullink & Kowalik         Expires 24 April 2025                 [Page 2]

Internet-Draft             XML to JSON for RPP              October 2024


1.  Introduction

   EPP [RFC5730] employs XML to define its protocol interactions, with
   XML Schema Definitions (XSD) serving as the formal schema language to
   outline the structure and validate the conformance of EPP XML
   messages.  These XSDs, integral to the EPP RFCs, ensure that EPP
   messages adhere to the expected syntax and semantic rules.  This
   document describes the rules and methodologies for converting these
   XSDs, to JSON Schema, which serves a similar purpose for JSON
   formatted data.  JSON Schema provides a robust framework for
   describing and validating the structure of JSON data, offering a
   parallel method for enforcing syntactical correctness and logical
   consistency in JSON formatted EPP messages.

   As the domain registration industry evolves towards adopting RESTful
   APIs and other JSON-based interactions, there's a need for analogous
   schema definitions to ensure consistency, validation, and
   interoperability of JSON representations of EPP messages.  This
   document aims to bridge this gap by providing a standardized approach
   to translating the rigorously defined XSDs of EPP into JSON Schema,
   facilitating the use of JSON in the RESTful Provisioning Protocol and
   potential future EPP-related protocols and transports.

   This approach eventually allows for converting valid EPP XML messages
   to the JavaScript Object Notation (JSON) Data Interchange Format
   [RFC8259], for use with EPP.

1.1.  Motivation

   The RESTful Provisioning Protocol (RPP) introduces a new provisiong
   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, coupled with the declining popularity of XML, 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 compared to XML, significantly eases the tasks of writing,
   reading, and maintaining code.  This simplicity is especially
   advantageous for the rapid comprehension and integration of
   provisioning APIs.



Wullink & Kowalik         Expires 24 April 2025                 [Page 3]

Internet-Draft             XML to JSON for RPP              October 2024


   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.  Moreover, JSON parsing is typically faster and more
   straightforward than XML parsing, contributing to improved system
   performance amid frequent interactions between RPP clients and
   servers.

   However, the absence of a standardized 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.  Standardizing 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.

   EPP RFCs - This is a reference to the EPP version 1.0 specifications
   [RFC5730], [RFC5731], [RFC5732] and [RFC5733].

   RESTful Provisioning Protocol - A RESTful protocol for provisiong
   heterogeneous database objects.

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.

4.  XSD Conversion Rules

   This chapter presents rules for converting EPP XSD into JSON Schema.





Wullink & Kowalik         Expires 24 April 2025                 [Page 4]

Internet-Draft             XML to JSON for RPP              October 2024


4.1.  Elements and Attributes

   Rule 1: Elements in XSD must be converted to properties in the JSON
   Schema, preserving names.

   XSD:

   <element name="name" type="eppcom:labelType"/>

   JSON Schema:

   {
     ...
     "properties": {
       "name": {
         "$ref": "#/definitions/labelType"
       }
       ...
     }
   }

   Rule 2: Attributes in XSD must be represented as JSON properties,
   prefixed with "@", retaining original names with the prefix addition.

   XSD:

   <simpleContent>
       <extension base="normalizedString">
       <attribute name="s" type="domain:statusValueType" use="required"/>
       <attribute name="lang" type="language"/>
       </extension>
   </simpleContent>

   JSON Schema

   {
     ...
     "properties": {
       "@s": {
         "$ref": "#/definitions/statusValueType"
       },
       "@lang": {
         "$ref": "#/definitions/language"
       }
       ...
     },
     "required": ["@s"]
   }



Wullink & Kowalik         Expires 24 April 2025                 [Page 5]

Internet-Draft             XML to JSON for RPP              October 2024


4.2.  Simple Types and Enumerations

   Rule 3: Simple types, including elements with only text content, must
   be converted to appropriate JSON types, e.g., xs:string to type:
   string.

   XSD:

   <simpleType name="labelType">
     <restriction base="xs:string" />
   </simpleType>

   JSON Schema:

   {
     "definitions": {
       "labelType": {
         "type": "string"
       }
     }
   }

   Rule 4: Enumerations in XSD must be represented using the enum
   keyword in JSON Schema.

   XSD:

   <simpleType name="trStatusType">
     <restriction base="token">
       <enumeration value="clientApproved"/>
       <enumeration value="clientCancelled"/>
       ...
     </restriction>
   </simpleType>

   JSON Schema:















Wullink & Kowalik         Expires 24 April 2025                 [Page 6]

Internet-Draft             XML to JSON for RPP              October 2024


   {
     "definitions": {
       "trStatusType": {
         "type": "string",
         "enum": [
           "clientApproved",
           "clientCancelled",
           ...
         ]
       }
     }
   }

4.3.  Occurrence Constraints

   Rule 5: Elements with minOccurs: 0 and maxOccurs: 1 should be
   represented as optional properties in the JSON Schema.

   XSD:

     <complexType name="infoType">
       <sequence>
         <element name="authInfo" type="authInfoType" minOccurs="0"/>
         ...
       </sequence>
     </complexType>

   JSON Schema:

   {
     "type": "object",
     "properties": {
       "authInfo": {
         "$ref": "#/definitions/authInfoType"
       }
       ...
     },
     "required": []
   }

   Rule 6: Elements with minOccurs: 1 and maxOccurs: 1 or omitted
   attributes must be represented as mandatory properties in the JSON
   Schema.

   XSD:






Wullink & Kowalik         Expires 24 April 2025                 [Page 7]

Internet-Draft             XML to JSON for RPP              October 2024


   <xs:complexType name="createType">
     <xs:sequence>
       <xs:element name="name" type="xs:string"/>
       ...
     </xs:sequence>
   </xs:complexType>

   JSON Schema:

   {
     "type": "object",
     "properties": {
       "name": {
         "type": "string"
       }
       ...
     },
     "required": ["name"]
   }

   Rule 7: Elements allowing multiple occurrences must be represented as
   JSON arrays, using minItems and maxItems to enforce minOccurs and
   maxOccurs.

   XSD:

     <complexType name="mNameType">
       <sequence>
         <element name="name" type="eppcom:labelType" maxOccurs="10"/>
       </sequence>
     </complexType>

   JSON Schema:

   {
     "type": "object",
     "properties": {
       "name": {
         "type": "array",
         "items": {
           "$ref": "#/definitions/labelType"
         },
         "maxItems" : 10
       }
     }
   }





Wullink & Kowalik         Expires 24 April 2025                 [Page 8]

Internet-Draft             XML to JSON for RPP              October 2024


4.4.  Complex Types

   Rule 8: Complex types in XSD must be converted to JSON objects in the
   JSON Schema, with properties adhering to subsequent rules for
   elements and attributes.  Properties rendered through choice or
   sequence elements included in complex types shall be included in the
   same object definition as opposed to creating a separate object
   level.

   XSD:

     <complexType name="createType">
       <sequence>
         <element name="name" type="eppcom:labelType"/>
         <element name="period" type="domain:periodType" minOccurs="0"/>
         ...
       </sequence>
     </complexType>

   JSON Schema:

   {
       "title": "createType",
       "type": "object",
       "properties": {
           "name": {
               "$ref": "#/definitions/labelType"
           },
           "period": {
               "$ref": "#/definitions/periodType"
           },
           ...
       },
       "required": ["name", ...]
   }

4.5.  Sequences

   Rule 9: Sequences in XSD must be converted to JSON objects in the
   JSON Schema, with each sequence element becoming a property of the
   object.  Cardinality dictated by minOccurs and maxOccurs must be
   applied to determine if an element is represented as optional,
   mandatory, or an array.

   XSD:






Wullink & Kowalik         Expires 24 April 2025                 [Page 9]

Internet-Draft             XML to JSON for RPP              October 2024


     <complexType name="createType">
       <sequence>
         <element name="name" type="eppcom:labelType"/>
         <element name="period" type="domain:periodType" minOccurs="0"/>
         ...
       </sequence>
     </complexType>

   JSON Schema:

   {
       "title": "createType",
       "type": "object",
       "properties": {
           "name": {
               "$ref": "#/definitions/labelType"
           },
           "period": {
               "$ref": "#/definitions/periodType"
           },
           ...
       },
       "required": ["name", ...]
   }

4.6.  Choices

   Rule 10: The choice construct in XSD must be represented in JSON
   Schema using the oneOf keyword, allowing for representation of
   multiple possible structures with only one being valid at a time.
   Each choice property MUST be marked as required to make a clear and
   unambigous distinction between the variants.

   XSD:

   <complexType name="authInfoChgType">
     <choice>
       <element name="pw" type="eppcom:pwAuthInfoType"/>
       <element name="ext" type="eppcom:extAuthInfoType"/>
       ...
     </choice>
   </complexType>

   JSON Schema:







Wullink & Kowalik         Expires 24 April 2025                [Page 10]

Internet-Draft             XML to JSON for RPP              October 2024


   {
     "type": "object",
     "oneOf": [
       {
         "properties": {
           "pw": {
             "$ref": "#/definitions/pwAuthInfoType"
           }
         },
         "required": ["pw"]
       },
       {
         "properties": {
           "ext": {
             "$ref": "#/definitions/extAuthInfoType"
           }
         },
         "required": ["ext"]
       }
       ...
     ]
   }

4.7.  Mixed Content and Special Cases

   Rule 11: Elements with mixed content must be represented as JSON
   objects with #text for text content and properties for each child
   element.  If schema allows for multiple instances of text content the
   #text property should be defined as an array.

   XSD:

     <complexType name="errValueType" mixed="true">
       <sequence>
         <any namespace="##any" processContents="skip"/>
       </sequence>
       <anyAttribute namespace="##any" processContents="skip"/>
     </complexType>

   JSON Schema:











Wullink & Kowalik         Expires 24 April 2025                [Page 11]

Internet-Draft             XML to JSON for RPP              October 2024


   {
     "type": "object",
     "properties": {
       "#text": {
         "type": "array",
         "items": {
           "type": string
         }
       },
       "additionalProperties": true
     }
   }

   Rule 12: Empty elements in XSD or EPP normative text must be
   represented as properties with a null fixed value in the JSON Schema.

   XSD:

   <complexType name="eppType">
       <choice>
         ...
         <element name="hello"/>
         ...
       </choice>
   </complexType>

   JSON Schema:

   {
     "type": "object",
     "oneOf": [
       ...
       {
           "properties": {
               "hello": {
                   "type": "null"
               }
           },
           "required": ["hello"]
       }
       ...
     ]
   }

   Rule 13: Elements with attributes and text content must be
   represented as JSON objects with #text for text and properties for
   each attribute, prefixed with "@".




Wullink & Kowalik         Expires 24 April 2025                [Page 12]

Internet-Draft             XML to JSON for RPP              October 2024


   XSD:

     <complexType name="mixedMsgType" mixed="true">
       <sequence>
         <any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
       </sequence>
       <attribute name="lang" type="language" default="en"/>
     </complexType>

   JSON Schema:

   {
     "type": "object",
     "properties": {
       "#text": {
         "type": "array",
         "items": {
           "type": string
         }
       },
       "@lang": {
           "$ref": "#/definitions/language"
       },
       "additionalProperties": true
     }
   }

TODO: Rules for different flavours of token type (min/max characters etc.)

   TODO: merge the content examples with the rules above?

5.  XML Conversion Rules

   A XML element may exist in one of 7 distinct forms, the sections
   below describe how these forms MUST be translated to valid JSON.

   1.  Empty
   2.  Pure text content
   3.  Attributes only
   4.  Pure text content and attributes
   5.  Child elements with different names
   6.  Child elements with identical names
   7.  Child element(s) and contiguous text

5.1.  Empty

   An empty XML element MUST be mapped to to a key matching the name of
   the element and a null value.



Wullink & Kowalik         Expires 24 April 2025                [Page 13]

Internet-Draft             XML to JSON for RPP              October 2024


   XML:

   <hello/>

   JSON:

   {
       "hello": null
   }

5.2.  Pure text content

   An XML element containing text only MUST be mapped to a key matching
   the name of the element and the text MUST be used for the value

   XML:

   <lang>en</lang>

   JSON:

   {
       "lang": "en"
   }

5.3.  Attributes only

   An XML element containing one or more atributes only, MUST be mapped
   to a JSON object matching the name of the element.  Each XML
   attribute, prefixed using the @ character, MUST be added as a key-
   value pair to the object.

   XML:

   <msgQ count="5" id="12345"/>

   JSON:

   {
       "msgQ": {
           "@count": "5",
           "@id": "12345"
       }
   }







Wullink & Kowalik         Expires 24 April 2025                [Page 14]

Internet-Draft             XML to JSON for RPP              October 2024


5.4.  Pure text content and attributes

   An XML element containing one or more atributes and text content
   only, MUST be mapped to a JSON object matching the name of the
   element.  The text content MUST, prefixed using the string #text,
   MUST be added as a key-value pair to the object.

   XML:

   <msg lang="en">Command completed successfully</msg>

   JSON:

   {
       "msg": {
           "@lang": "en",
           "#text": "Command completed successfully"
       }
   }

5.5.  Child elements with different names

   An XML element containing one or more child elements, where each
   child uses an unique name, MUST be mapped to a JSON object matching
   the name of the element.  Each child element MUST be added as a key-
   value pair to the parent object.

   XML:

   <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>54321-XYZ</svTRID>
   </trID>

   JSON:

   {
       "trID": {
           "clTRID": "ABC-12345",
           "svTRID": "54321-XYZ"
       }
   }









Wullink & Kowalik         Expires 24 April 2025                [Page 15]

Internet-Draft             XML to JSON for RPP              October 2024


5.6.  Child elements with identical names

   An XML element containing multiple child elements, where multiple
   child elements use the same name, MUST be mapped to a JSON object
   containing an array.  The name of the array MUST match the name of
   the non-unique children, each child element MUST be converted to JSON
   and added to the array.

   XML:

   <host>
       <addr>192.0.2.1</addr>
       <addr>192.0.2.2</addr>
   </host>

   JSON:

   {
       "host": {
           "addr": [
               "192.0.2.1",
               "192.0.2.2"
           ]
       }
   }

5.7.  Child elements and contiguous text

   An XML element containing one or more child elements and contiguous
   text, MUST be mapped to a JSON object containing a key-value entry
   for each child element, the text value MUST result in a key named
   #text.

   XML:

   <msg lang="en">
       Credit balance low.
       <limit>100</limit>
       <bal>5</bal>
   </msg>

   JSON:









Wullink & Kowalik         Expires 24 April 2025                [Page 16]

Internet-Draft             XML to JSON for RPP              October 2024


   {
       "msg": {
           "@lang": "en",
           "limit": 100,
           "bal": 5,
           "#text": "Credit balance low."
       }
   }

   When child elements are mixed with multiple text segments, the
   resulting #text key-value entry MUST be an array, containing all text
   segments.

   XML:

   <msg lang="en">
       Credit balance low.
       <limit>100</limit>
       <bal>5</bal>
       Please increase balance.
   </msg>

   JSON:

   {
       "msg": {
           "@lang": "en",
           "limit": 100,
           "bal": 5,
           "#text": ["Credit balance low.", "Please increase balance asap."]
       }
   }

   The rules above are based on the conversion approach found on
   [XMLCOM-WEB]

6.  Examples

   This section lists examples for each of the existing EPP commands
   that are support by RPP.

   TODO: full examples of schema conversion

6.1.  Hello

   The Hello request message does not exist in the context of RPP.

   Example XML response:



Wullink & Kowalik         Expires 24 April 2025                [Page 17]

Internet-Draft             XML to JSON for RPP              October 2024


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <greeting>
           <svID>Example EPP server epp.example.com</svID>
           <svDate>2000-06-08T22:00:00.0Z</svDate>
           <svcMenu>
               <version>1.0</version>
               <lang>en</lang>
               <lang>fr</lang>
               <objURI>urn:ietf:params:xml:ns:obj1</objURI>
               <objURI>urn:ietf:params:xml:ns:obj2</objURI>
               <objURI>urn:ietf:params:xml:ns:obj3</objURI>
               <svcExtension>
                   <extURI>http://custom/obj1ext-1.0</extURI>
               </svcExtension>
           </svcMenu>
           <dcp>
               <access>
                   <all/>
               </access>
               <statement>
                   <purpose>
                       <admin/>
                       <prov/>
                   </purpose>
                   <recipient>
                       <ours/>
                       <public/>
                   </recipient>
                   <retention>
                       <stated/>
                   </retention>
               </statement>
           </dcp>
       </greeting>
   </epp>

   Example JSON response:












Wullink & Kowalik         Expires 24 April 2025                [Page 18]

Internet-Draft             XML to JSON for RPP              October 2024


   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "greeting": {
               "svID": "Example RPP server v1.0",
               "svDate": "2000-06-08T22:00:00.0Z",
               "svcMenu": {
                   "version": "1.0",
                   "lang": [
                       "en",
                       "fr"
                   ]
               },
               "dcp": {
                   "access": {
                       "all": null
                   },
                   "statement": {
                       "purpose": {
                           "admin": null,
                           "prov": null
                       },
                       "recipient": {
                           "ours": null,
                           "public": null
                       },
                       "retention": {
                           "stated": null
                       }
                   }
               }
           }
       }
   }

6.2.  Login

   The Login request and response message are not used for RPP.

6.3.  Logout

   The Logout request and response message are not used for RPP.

6.4.  Check

   The Check request and responses messages are not used for RPP.





Wullink & Kowalik         Expires 24 April 2025                [Page 19]

Internet-Draft             XML to JSON for RPP              October 2024


6.5.  Info

   The Info request message is not used for RPP.

   Example XML Domain Info response:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <resData>
               <domain:infData
                   xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
                   <domain:name>example.com</domain:name>
                   <domain:roid>EXAMPLE1-REP</domain:roid>
                   <domain:status s="ok"/>
                   <domain:registrant>jd1234</domain:registrant>
                   <domain:contact type="admin">sh8013</domain:contact>
                   <domain:contact type="tech">sh8013</domain:contact>
                   <domain:ns>
                       <domain:hostObj>ns1.example.com</domain:hostObj>
                       <domain:hostObj>ns1.example.net</domain:hostObj>
                   </domain:ns>
                   <domain:host>ns1.example.com</domain:host>
                   <domain:host>ns2.example.com</domain:host>
                   <domain:clID>ClientX</domain:clID>
                   <domain:crID>ClientY</domain:crID>
                   <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
                   <domain:upID>ClientX</domain:upID>
                   <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
                   <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
                   <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
                   <domain:authInfo>
                       <domain:pw>2fooBAR</domain:pw>
                   </domain:authInfo>
               </domain:infData>
           </resData>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>54322-XYZ</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON Domain Info response:



Wullink & Kowalik         Expires 24 April 2025                [Page 20]

Internet-Draft             XML to JSON for RPP              October 2024


   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "resData": {
                   "domain:infData": {
                       "@xmlns:domain": "urn:ietf:params:xml:ns:domain-1.0",
                       "domain:name": "example.com",
                       "domain:roid": "EXAMPLE1-REP",
                       "domain:status": {
                           "@s": "ok"
                       },
                       "domain:registrant": "jd1234",
                       "domain:contact": [
                           {
                               "@type": "admin",
                               "#text": "sh8013"
                           },
                           {
                               "@type": "tech",
                               "#text": "sh8013"
                           }
                       ],
                       "domain:ns": {
                           "domain:hostObj": [
                               "ns1.example.com",
                               "ns1.example.net"
                           ]
                       },
                       "domain:host": [
                           "ns1.example.com",
                           "ns2.example.com"
                       ],
                       "domain:clID": "ClientX",
                       "domain:crID": "ClientY",
                       "domain:crDate": "1999-04-03T22:00:00.0Z",
                       "domain:upID": "ClientX",
                       "domain:upDate": "1999-12-03T09:00:00.0Z",
                       "domain:exDate": "2005-04-03T22:00:00.0Z",
                       "domain:trDate": "2000-04-08T09:00:00.0Z",
                       "domain:authInfo": {
                           "domain:pw": "2fooBAR"
                       }
                   }



Wullink & Kowalik         Expires 24 April 2025                [Page 21]

Internet-Draft             XML to JSON for RPP              October 2024


               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "54322-XYZ"
               }
           }
       }
   }

6.6.  Poll

   The Poll request message is not used for RPP.

   Example XML response:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1301">
               <msg>Command completed successfully; ack to dequeue</msg>
           </result>
           <msgQ count="4" id="12346">
               <qDate>2000-06-08T22:10:00.0Z</qDate>
               <msg lang="en">Credit balance low.
                   <limit>100</limit>
                   <bal>5</bal>
               </msg>
           </msgQ>
           <trID>
               <clTRID>ABC-12346</clTRID>
               <svTRID>54321-XYZ</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON response:














Wullink & Kowalik         Expires 24 April 2025                [Page 22]

Internet-Draft             XML to JSON for RPP              October 2024


   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1301",
                   "msg": "Command completed successfully; ack to dequeue"
               },
               "msgQ": {
                   "@count": "4",
                   "@id": "12346",
                   "qDate": "2024-01-15T22:10:00.0Z",
                   "msg": {
                       "@lang": "en",
                       "limit": "100",
                       "bal": "5",
                       "#text": "Credit balance low."
                   }
               },
               "trID": {
                   "clTRID": "ABC-12346",
                   "svTRID": "54321-XYZ"
               }
           }
       }
   }

6.7.  Poll Ack

   The Poll Ack request message is not used for RPP.

   Example XML response:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <msgQ count="0" id="12345"/>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>XYZ-12345</svTRID>
           </trID>
       </response>
   </epp>




Wullink & Kowalik         Expires 24 April 2025                [Page 23]

Internet-Draft             XML to JSON for RPP              October 2024


   Example JSON response:

   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "msgQ": {
                   "@count": "0",
                   "@id": "12345"
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "XYZ-12345"
               }
           }
       }
   }

6.8.  Transfer Query

   The Domain Transfer Query request message is not used for RPP.

   Example XML Domain Transfer Query response:
























Wullink & Kowalik         Expires 24 April 2025                [Page 24]

Internet-Draft             XML to JSON for RPP              October 2024


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <resData>
               <domain:trnData
                   xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
                   <domain:name>example.com</domain:name>
                   <domain:trStatus>pending</domain:trStatus>
                   <domain:reID>ClientX</domain:reID>
                   <domain:reDate>2000-06-06T22:00:00.0Z</domain:reDate>
                   <domain:acID>ClientY</domain:acID>
                   <domain:acDate>2000-06-11T22:00:00.0Z</domain:acDate>
                   <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate>
               </domain:trnData>
           </resData>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>54322-XYZ</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON Domain Transfer Query response:
























Wullink & Kowalik         Expires 24 April 2025                [Page 25]

Internet-Draft             XML to JSON for RPP              October 2024


   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "resData": {
                   "domain:trnData": {
                       "@xmlns:domain": "urn:ietf:params:xml:ns:domain-1.0",
                       "domain:name": "example.com",
                       "domain:trStatus": "pending",
                       "domain:reID": "ClientX",
                       "domain:reDate": "2000-06-06T22:00:00.0Z",
                       "domain:acID": "ClientY",
                       "domain:acDate": "2000-06-11T22:00:00.0Z",
                       "domain:exDate": "2002-09-08T22:00:00.0Z"
                   }
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "54322-XYZ"
               }
           }
       }
   }

6.9.  Create

   Example XML Domain Create request:




















Wullink & Kowalik         Expires 24 April 2025                [Page 26]

Internet-Draft             XML to JSON for RPP              October 2024


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <command>
           <create>
               <domain:create
                   xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
                   <domain:name>example.com</domain:name>
                   <domain:period unit="y">2</domain:period>
                   <domain:ns>
                       <domain:hostObj>ns1.example.net</domain:hostObj>
                       <domain:hostObj>ns2.example.net</domain:hostObj>
                   </domain:ns>
                   <domain:registrant>jd1234</domain:registrant>
                   <domain:contact type="admin">sh8013</domain:contact>
                   <domain:contact type="tech">sh8013</domain:contact>
                   <domain:authInfo>
                       <domain:pw>2fooBAR</domain:pw>
                   </domain:authInfo>
               </domain:create>
           </create>
           <clTRID>ABC-12345</clTRID>
       </command>
   </epp>

   Example JSON Domain Create request:

























Wullink & Kowalik         Expires 24 April 2025                [Page 27]

Internet-Draft             XML to JSON for RPP              October 2024


   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "command": {
               "create": {
                   "domain:create": {
                       "@xmlns:domain": "urn:ietf:params:xml:ns:domain-1.0",
                       "domain:name": "example.com",
                       "domain:period": {
                           "@unit": "y",
                           "#text": "2"
                       },
                       "domain:ns": {
                           "domain:hostObj": [
                               "ns1.example.net",
                               "ns2.example.net"
                           ]
                       },
                       "domain:registrant": "jd1234",
                       "domain:contact": [
                           {
                               "@type": "admin",
                               "#text": "sh8013"
                           },
                           {
                               "@type": "tech",
                               "#text": "sh8013"
                           }
                       ],
                       "domain:authInfo": {
                           "domain:pw": "2fooBAR"
                       }
                   }
               },
               "clTRID": "ABC-12345"
           }
       }
   }

   Example XML Domain Create response:











Wullink & Kowalik         Expires 24 April 2025                [Page 28]

Internet-Draft             XML to JSON for RPP              October 2024


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <resData>
               <domain:creData
                   xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
                   <domain:name>example.com</domain:name>
                   <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
                   <domain:exDate>2001-04-03T22:00:00.0Z</domain:exDate>
               </domain:creData>
           </resData>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>54321-XYZ</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON Domain Create response:

   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "resData": {
                   "domain:creData": {
                       "@xmlns:domain": "urn:ietf:params:xml:ns:domain-1.0",
                       "domain:name": "example.com",
                       "domain:crDate": "1999-04-03T22:00:00.0Z",
                       "domain:exDate": "2001-04-03T22:00:00.0Z"
                   }
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "54321-XYZ"
               }
           }
       }
   }




Wullink & Kowalik         Expires 24 April 2025                [Page 29]

Internet-Draft             XML to JSON for RPP              October 2024


6.10.  Delete

   The Delete request message is not used for RPP.

   Example XML Domain Delete response:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>54321-XYZ</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON Domain Delete response:

   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "54321-XYZ"
               }
           }
       }
   }

6.11.  Renew

   The Renew request message is not used for RPP.

   Example XML Domain Renew response:








Wullink & Kowalik         Expires 24 April 2025                [Page 30]

Internet-Draft             XML to JSON for RPP              October 2024


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <resData>
               <domain:renData
                   xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
                   <domain:name>example.com</domain:name>
                   <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
               </domain:renData>
           </resData>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>54322-XYZ</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON Domain Renew response:

   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "resData": {
                   "domain:renData": {
                       "@xmlns:domain": "urn:ietf:params:xml:ns:domain-1.0",
                       "domain:name": "example.com",
                       "domain:exDate": "2005-04-03T22:00:00.0Z"
                   }
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "54322-XYZ"
               }
           }
       }
   }






Wullink & Kowalik         Expires 24 April 2025                [Page 31]

Internet-Draft             XML to JSON for RPP              October 2024


6.12.  Transfer Request

   The Transfer request message is not used for RPP.

   Example XML Domain Transfer response:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1001">
               <msg>Command completed successfully; action pending</msg>
           </result>
           <resData>
               <domain:trnData
                   xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
                   <domain:name>example.com</domain:name>
                   <domain:trStatus>pending</domain:trStatus>
                   <domain:reID>ClientX</domain:reID>
                   <domain:reDate>2000-06-08T22:00:00.0Z</domain:reDate>
                   <domain:acID>ClientY</domain:acID>
                   <domain:acDate>2000-06-13T22:00:00.0Z</domain:acDate>
                   <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate>
               </domain:trnData>
           </resData>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>54322-XYZ</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON Domain Transfer response:


















Wullink & Kowalik         Expires 24 April 2025                [Page 32]

Internet-Draft             XML to JSON for RPP              October 2024


   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1001",
                   "msg": "Command completed successfully; action pending"
               },
               "resData": {
                   "domain:trnData": {
                       "@xmlns:domain": "urn:ietf:params:xml:ns:domain-1.0",
                       "domain:name": "example.com",
                       "domain:trStatus": "pending",
                       "domain:reID": "ClientX",
                       "domain:reDate": "2000-06-08T22:00:00.0Z",
                       "domain:acID": "ClientY",
                       "domain:acDate": "2000-06-13T22:00:00.0Z",
                       "domain:exDate": "2002-09-08T22:00:00.0Z"
                   }
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "54322-XYZ"
               }
           }
       }
   }

6.13.  Transfer Cancel

   The Transfer Cancel request message is not used for RPP.

   Example XML Domain Cancel Transfer response:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>XYZ-12345</svTRID>
           </trID>
       </response>
   </epp>




Wullink & Kowalik         Expires 24 April 2025                [Page 33]

Internet-Draft             XML to JSON for RPP              October 2024


   Example JSON Domain Cancel Transfer response:

   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "XYZ-12345"
               }
           }
       }
   }

6.14.  Transfer Reject

   The Transfer Reject request message is not used for RPP and the
   response message is the same as for the Transfer Cancel command.

6.15.  Transfer Approve

   The Transfer Approve request message is not used for RPP and the
   response message is the same as for the Transfer Cancel command.

6.16.  Update

   Example XML Domain Update request:




















Wullink & Kowalik         Expires 24 April 2025                [Page 34]

Internet-Draft             XML to JSON for RPP              October 2024


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <command>
           <update>
               <domain:update
                   xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
                   <domain:name>example.com</domain:name>
                   <domain:chg>
                       <domain:registrant>sh8013</domain:registrant>
                       <domain:authInfo>
                           <domain:pw>2BARfoo</domain:pw>
                       </domain:authInfo>
                   </domain:chg>
               </domain:update>
           </update>
           <clTRID>ABC-12345</clTRID>
       </command>
   </epp>

   Example JSON Domain Update request:

   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "command": {
               "update": {
                   "domain:update": {
                       "@xmlns:domain": "urn:ietf:params:xml:ns:domain-1.0",
                       "domain:name": "example.com",
                       "domain:chg": {
                           "domain:registrant": "sh8013",
                           "domain:authInfo": {
                               "domain:pw": "2BARfoo"
                           }
                       }
                   }
               },
               "clTRID": "ABC-12345"
           }
       }
   }

   Example XML Domain Update response:







Wullink & Kowalik         Expires 24 April 2025                [Page 35]

Internet-Draft             XML to JSON for RPP              October 2024


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp
       xmlns="urn:ietf:params:xml:ns:epp-1.0">
       <response>
           <result code="1000">
               <msg>Command completed successfully</msg>
           </result>
           <trID>
               <clTRID>ABC-12345</clTRID>
               <svTRID>XYZ-12345</svTRID>
           </trID>
       </response>
   </epp>

   Example JSON Domain Update response:

   {
       "rpp": {
           "@xmlns": "urn:ietf:params:xml:ns:epp-1.0",
           "response": {
               "result": {
                   "@code": "1000",
                   "msg": "Command completed successfully"
               },
               "trID": {
                   "clTRID": "ABC-12345",
                   "svTRID": "XYZ-12345"
               }
           }
       }
   }

7.  IANA Considerations

   TODO

8.  Internationalization Considerations

   TODO

9.  Security Considerations

   TODO

10.  Acknowledgments

   TODO




Wullink & Kowalik         Expires 24 April 2025                [Page 36]

Internet-Draft             XML to JSON for RPP              October 2024


11.  References

11.1.  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,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC5730]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
              STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
              <https://www.rfc-editor.org/info/rfc5730>.

   [RFC5731]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Domain Name Mapping", STD 69, RFC 5731,
              DOI 10.17487/RFC5731, August 2009,
              <https://www.rfc-editor.org/info/rfc5731>.

   [RFC5732]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
              August 2009, <https://www.rfc-editor.org/info/rfc5732>.

   [RFC5733]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
              August 2009, <https://www.rfc-editor.org/info/rfc5733>.

   [RFC8259]  Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
              Interchange Format", STD 90, RFC 8259,
              DOI 10.17487/RFC8259, December 2017,
              <https://www.rfc-editor.org/info/rfc8259>.

11.2.  Informative References

   [XMLCOM-WEB]
              XML.com, "Converting Between XML and JSON", 2006,
              <https://www.xml.com/pub/a/2006/05/31/converting-between-
              xml-and-json.html>.

Authors' Addresses

   Maarten Wullink
   SIDN Labs
   Email: maarten.wullink@sidn.nl
   URI:   https://sidn.nl/


   Pawel Kowalik
   DENIC



Wullink & Kowalik         Expires 24 April 2025                [Page 37]

Internet-Draft             XML to JSON for RPP              October 2024


   Email: pawel.kowalik@denic.de
   URI:   https://denic.de/

















































Wullink & Kowalik         Expires 24 April 2025                [Page 38]