Hi all,
just submitted a new version of draft-loffredo-regext-epp-over-http.
Here in the following the most relevant updates:
1. Has been made fully compliant with RFC 5730
2. Aligns with the structure and makeup of EPP over TCP (EoT) in RFC 5734
3. Fully pluggable transport for EPP with EoT
Hi Marc,
I’ll share a version of the bootstrap file in a few weeks, once the host is
globally reachable.
Thanks,
James
From: Marc Blanchet
Date: Tuesday, February 20, 2024 at 6:40 AM
To: James Mitchell
Cc: "regext@ietf.org"
Subject: [Ext] Re: [regext] Adding the DNS root to the bootstrap
Internet-Draft draft-ietf-regext-epp-delete-bcp-00.txt is now available. It is
a work item of the Registration Protocols Extensions (REGEXT) WG of the IETF.
Title: Best Practices for Deletion of Domain and Host Objects in the
Extensible Provisioning Protocol (EPP)
Authors: Scott
From: regext On Behalf Of Jasdip Singh
Sent: Tuesday, February 20, 2024 12:51 PM
To: Hollenbeck, Scott ; a...@hxr.us
Cc: i...@antoin.nl; mario.loffr...@iit.cnr.it; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WG LAST CALL draft-ietf-regext-rdap-rir-search
Caution: This email originated
Hello Andy, Scott,
Let’s take a specific example from the RIR search draft (a specification with
multiple extension identifiers defined) to test-drive these options. Say, an IP
network search response:
{
"rdapConformance": [ "rdap_level_0", "rirSearch1",
Andy, I agree that that's an incorrect interpretation. Content is part of the
response, too, and as such it has to be included when the response is
constructed/formed/assembled/whatever.
Scott
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Tuesday, February 20, 2024 12:23
"construction of the response" can be interpreted strictly to mean
only the JSON structure of the response. IMHO, that is an incorrect
interpretation nor does it track with RDAP as it is used because
profile extensions such as the ICANN and NRO extensions also dictate
content not just structure.
I don’t understand the confusion regarding the text in 9083. It might not
include BCP 14 key words, but I believe the intention is clear. Looking at the
two sentences:
“A response to a "help" request will include identifiers for all of the
specifications supported by the server.”
*will
> Le 19 févr. 2024 à 20:28, James Mitchell a écrit :
>
> Hi all,
>
> IANA is planning to add the DNS root to the RDAP DNS bootstrap file. We do
> not yet have a date for this change and are currently looking to understand
> potential impact to RDAP clients.
>
Hi James,
Thanks for
