Regarding the use of a brief description in the registry itself as the
"Specification" in "Specification Required": I missed it this time, but we ran
into this same question with draft-ietf-calext-jscalendar-21, and FWIW, Barry
Leiba recommended to the author that the registration procedure be c
pecifically meant to encompass non-RFC
documentation (see Section 4 of RFC 8126 for registration procedure
definitions), but no problem at all with including it.
Thanks,
Amanda
On 8/24/23, 9:18 AM, "iesg on behalf of Mario Loffredo" wrote:
Hi Amanda,
Il 23/08/2023
Hi Andy,
Thanks for catching this. The RDAP JSON Values entry for "administrative" is
now spelled correctly:
https://www.iana.org/assignments/rdap-json-values
Best regards,
Amanda Baber
Lead IANA Services Specialist
On Fri Jan 19 21:17:00 2018, a...@hxr.us wrote:
> Hello,
>
Dear Bernhard,
Thank you for catching this. The typo has been corrected:
https://www.iana.org/assignments/rdap-json-values
Best regards,
Amanda Baber
Lead IANA Services Specialist
On Wed Feb 14 12:34:22 2018, rep.dot@gmail.com wrote:
> On 23 January 2018 at 20:32, Amanda Baber via RT
nfirm that this change is OK?
https://datatracker.ietf.org/doc/html/draft-ietf-regext-epp-eai-27
thanks,
Amanda Baber
IANA Operations Manager
On Tue Jan 28 12:01:13 2025, gavin.br...@icann.org wrote:
> Hi David,
>
> As requested by Scott, I have reviewed the registration request in
>