Hi,
I have just submitted version -27.
This revision incorporates the latest review comments and updates the
document to RFC 10050.
The authors wish to draw particular attention to the following
considerations supporting the requirement that an RDAP entity object
must not include both vcardArray and jscontact_card:
- The two members are alternative representations of the same contact
information. jscontact_card is intended to provide the same information
as vcardArray; it is not an additional, independent set of contact data.
- Returning both representations would duplicate information and
unnecessarily increase response size and processing costs, especially
for responses containing multiple entities.
- Two representations in the same response could become inconsistent.
Although jCard and JSContact convey substantially the same information,
differences could arise through implementation errors or updates applied
to only one representation. Clients would then have no rule for deciding
which value to use.
- Returning exactly one representation is consistent with the principles
of content negotiation through the RDAP media-type parameters in the
Accept header.
- Backward compatibility does not require both members in one response.
vcardArray is optional under RFC 9083, while jscontact_card is an RDAP
response extension whose presence is explicitly requested by clients and
signaled by the "jscontact" conformance identifier. The response
therefore remains compliant with RFC 9083 when only jscontact_card
is provided. Furthermore, the response remains compatible with existing
RDAP profiles and with their potential evolution towards the deprecation
of jCard.
That said, the authors believe that the draft is now ready for WGLC.
Best,
Mario
-------- Messaggio Inoltrato --------
Oggetto: New Version Notification for
draft-ietf-regext-rdap-jscontact-27.txt
Data: Mon, 05 Oct 2026 08:55:57 -0700
Mittente: [email protected]
A: Gavin Brown <[email protected]>, Mario Loffredo
<[email protected]>
A new version of Internet-Draft draft-ietf-regext-rdap-jscontact-27.txt has
been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-ietf-regext-rdap-jscontact
Revision: 27
Title: Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
Date: 2026-10-05
Group: regext
Pages: 39
URL: https://www.ietf.org/archive/id/draft-ietf-regext-rdap-jscontact-27.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-jscontact/
HTMLized:
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-jscontact
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-jscontact-27
Abstract:
This document describes an RDAP extension which represents entity
contact information in JSON responses using JSContact.
The IETF Secretariat
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
