Hi WG,
This is a reminder for agenda items for our Bangkok IETF 122 meeting.
So far we only have one request for draft-brown-rdap-referrals.
Is there no-one that wants to advance their documents? We have 3 hours to fill.
Please request your slot as the cut-off date for our agenda is this Wednesda
Internet-Draft draft-ietf-regext-rdap-jscontact-20.txt is now available. It is
a work item of the Registration Protocols Extensions (REGEXT) WG of the IETF.
Title: Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
Authors: Mario Loffredo
Gavin Brown
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 respons
Paul,
Thank you for reviewing and the helpful comments. I've added responses inline
below with [WAC].
Bill
On 3/2/25, 8:18 PM, "Paul Wouters via Datatracker" mailto:nore...@ietf.org>> wrote:
Caution: This email originated from outside the organization. Do not click
links or open attachments un
Internet-Draft draft-ietf-regext-rdap-rir-search-15.txt is now available. It
is a work item of the Registration Protocols Extensions (REGEXT) WG of the
IETF.
Title: Registration Data Access Protocol (RDAP) Regional Internet Registry
(RIR) Search
Authors: Tom Harrison
Jasdip Si
Hi Scott,
Thanks for your reply.
My comment about the intended status as mainly to check whether this was
discussed because it is really unclear to me what is the most suitable intended
status for this I-D. But, as you wrote ` The WG had the same debate. We
eventually decided that BCP status w
> -Original Message-
> From: Éric Vyncke via Datatracker
> Sent: Thursday, February 27, 2025 7:38 AM
> To: The IESG
> Cc: draft-ietf-regext-epp-delete-...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org; a...@hxr.us; a...@hxr.us; d...@fl1ger.de
> Subject: [EXTERNAL] Éric Vyncke's No O
