| Internet-Draft | JSContact Profile for RPP | July 2026 |
| Wullink & Kowalik | Expires 7 January 2027 | [Page] |
This document defines a JSContact usage profile, conforming to the rules described in [I-D.ietf-calext-jscontact-profiles], for the RESTful Provisioning Protocol (RPP). The JSContact Profile for RPP specifies how the JSContact format defined in [RFC9982] can be used as a standardized representation of contact information within RPP operations, enabling interoperability and consistency across RPP implementations that manage contact data.¶
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 7 January 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
JSContact [RFC9982] is a flexible, JSON-based format for representing contact information. Its flexibility allows the same data to be expressed in multiple valid ways, which can hinder interoperability in a provisioning context where data must be stored and interpreted consistently.¶
This document defines a JSContact usage profile for the RESTful Provisioning Protocol (RPP), restricting the set of JSContact constructs that RPP clients and servers are required to support when provisioning contact information.¶
The Registration Data Access Protocol (RDAP) [RFC9083] provides read-only access to registration data managed by RPP. Both protocols use JSContact for contact representation, but with profiles suited to their respective roles.¶
The RDAP JSContact profile [I-D.ietf-regext-rdap-jscontact] defines the constructs used when serving registration data to read-only consumers. The RPP profile, defined in this document, is a subset of these constructs. All JSContact constructs permitted by the RPP profile can be used for RDAP.¶
The converse does not hold. RDAP supports additional JSContact constructs that are useful in the read-only context of RDAP responses but that may hinder interoperability. These constructs are not present in RPP requests and responses.¶
In this document, the following terminology is used.¶
RESTful Provisioning Protocol or RPP - The protocol described in this document.¶
URL - A Uniform Resource Locator as defined in [RFC3986].¶
RPP client - An HTTP user agent performing an RPP request.¶
RPP server - An HTTP server responsible for processing requests and returning results in any supported media type.¶
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].¶
Since JSContact is a generalized representation of contact data, many of its capabilities are not optimized for interoperable use in RPP payloads. This document therefore defines a usage profile for JSContact that simplifies implementation for both RPP clients and RPP servers.¶
The JSContact profile for RPP is compliant with the rules described in [I-D.ietf-calext-jscontact-profiles]. The profile properties are formally listed in Section 4.1.12. All types mentioned in this section refer to the JSContact specification [RFC9982].¶
The Card "kind" member value MUST be "individual" (default) or "org" to represent an individual or an organization, respectively.¶
The Card "language" member SHOULD be set when localizations are specified (i.e., when the "localizations" member is present and non-null).¶
The Card "name" member MUST include only the "full" member and MUST NOT include the "components" member.¶
The Organization type MUST include only the "org" member.¶
The Address type MUST only use the "components" member.¶
The AddressComponent MUST include only the "kind" and "value" members. The "kind" member value MUST only use "name", "locality", "region", or "postcode".¶
When both an internationalized and a localized version of an address are used, the localized version MUST be placed in the localizations map keyed by an appropriate [BCP47] language tag.¶
The Phone type MUST include the "number" member and MAY include the "features" member. When the "features" member is present, its values MUST be "voice" or "fax". When the "features" member is absent, the phone number is assumed to be a voice number.¶
The Link type MUST include the "uri" member and MAY include the "kind" member. When the "kind" member is present, its value MUST be "contact".¶
A JSContact map key MUST comply with the Id type definition in [RFC9553]. RPP implementations MUST use the following predefined keys:¶
When internationalized and localized versions of an organization, postal address, or email exist, the internationalized version MUST be included under the predefined map key, while the localized version MUST be placed in the "localizations" map as described in Section 4.1.11.¶
If present, localized variants of name, organization, postal address, and email MUST be added to the "localizations" map. RPP implementations MUST expand all localizations, meaning a nested PatchObject key of the form "{key1}/{key2}/.../{keyN}" MUST NOT be used.¶
The number of provided localizations MUST NOT exceed the number of languages supported by the RPP server. The language of each localization MUST be indicated by a [BCP47] language tag as the key in the "localizations" map.¶
The following example of a Card includes a localized version of the postal address:¶
{
"@type": "Card",
"version": "2.0",
"language": "en",
"name": {
"full": "Joe User"
},
"organizations": {
"org": { "name": "Example Org" }
},
"addresses": {
"addr": {
"components": [
{ "kind": "name", "value": "Main Street 1" },
{ "kind": "locality", "value": "Ludwigshafen am Rhein" },
{ "kind": "region", "value": "Rhineland-Palatinate" },
{ "kind": "postcode", "value": "67067" }
],
"countryCode": "DE"
}
},
"localizations": {
"de": {
"addresses": {
"addr": {
"components": [
{ "kind": "name", "value": "Hauptstraße 1" },
{ "kind": "locality", "value": "Ludwigshafen am Rhein" },
{ "kind": "region", "value": "Rheinland-Pfalz" },
{ "kind": "postcode", "value": "67067" }
],
"countryCode": "DE"
}
}
}
}
}
The properties of the JSContact profile for RPP registered in the JSContact Profile registry as described in Section 5.1 are:¶
| Property | Context | Restricted | Restricted Enum |¶
| Attributes | Values | ||
|---|---|---|---|
| language | Card | ||
| kind | Card | individual, org | |
| name | Card | ||
| full | Name | mandatory | |
| organizations | Card | ||
| name | Organization | ||
| addresses | Card | ||
| full | Address | ||
| countryCode | Address | ||
| components | Address | ||
| kind | AddressComponent | name, locality, region, postcode | |
| value | AddressComponent | ||
| emails | Card | ||
| address | EmailAddress | ||
| phones | Card | ||
| features | Phone | voice, fax | |
| number | Phone | ||
| links | Card | ||
| kind | Link | contact | |
| uri | Link | ||
| localizations | Card | yes |
Client validation MUST return an error if any JSContact properties other than those listed above are present.¶
IANA is requested to register the following entry in the "JSContact Profile" registry [I-D.ietf-calext-jscontact-profiles]:¶
Name: rpp Profile Version: 1.0 Reference: This document¶
TODO¶
TODO¶