Hi,
to be fully compliant with the rdap-extensions draft and avoid further
discussions about using bare extension identifiers, this new version
includes the following changes:
- jscontact is used instead of jscard as extension identifier
- jscontact_card is used instead of jscard as response extension
I apologize if the .it implementation is not still aligned to this
version, I'll do it ASAP.
Best,
Mario
-------- Messaggio Inoltrato --------
Oggetto: New Version Notification for
draft-ietf-regext-rdap-jscontact-20.txt
Data: Mon, 03 Mar 2025 01:12:20 -0800
Mittente: internet-dra...@ietf.org
A: Gavin Brown <gavin.br...@icann.org>, Mario Loffredo
<mario.loffr...@iit.cnr.it>
A new version of Internet-Draft draft-ietf-regext-rdap-jscontact-20.txt has
been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-ietf-regext-rdap-jscontact
Revision: 20
Title: Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
Date: 2025-03-03
Group: regext
Pages: 27
URL: https://www.ietf.org/archive/id/draft-ietf-regext-rdap-jscontact-20.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-20
Abstract:
This document describes an RDAP extension which represents entity
contact information in JSON responses using JSContact.
The IETF Secretariat
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
