[regext] Publication has been requested for draft-ietf-regext-rdap-openid-23

James Galvin has requested publication of draft-ietf-regext-rdap-openid-23 as Proposed Standard on behalf of the REGEXT working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-openid/ ___ regext ma

[regext] Milestones changed for regext WG

Changed milestone "Submit for publication "Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect"", resolved as "Done". URL: https://datatracker.ietf.org/wg/regext/about/ ___ regext mailing list regext@ietf.org h

[regext] Publication has been requested for draft-ietf-regext-rdap-redacted-13

James Galvin has requested publication of draft-ietf-regext-rdap-redacted-13 as Proposed Standard on behalf of the REGEXT working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-redacted/ ___ regex

[regext] Milestones changed for regext WG

Changed milestone "Submit for publication "Redacted Fields in the Registration Data Access Protocol (RDAP) Response"", resolved as "Done". URL: https://datatracker.ietf.org/wg/regext/about/ ___ regext mailing list regext@ietf.org https://www.ietf.org/ma

Re: [regext] Fwd: New Version Notification for draft-newton-regext-rdap-x-media-type-00.txt

> The only problem is that RDAP is specifically intended to use the > features of HTTP. See Section 3 of RFC 7480. RDAP also currently > defines the use of HTTP headers, as do many REST protocols. In fact, > the idea behind RDAP-X is not novel as it was inspired by the W3C's > ActivityPub protocol