[regext] New Version Notification for draft-loffredo-regext-epp-over-http-04.txt

Hi All, I just posted a new version of the EoH draft, 04. Changes are to more accurately distinguish EPP connections and sessions from HTTP connections and sessions. This has arisen from lessons learned in gaining some implementation experience. https://datatracker.ietf.org/doc/draft-loffredo-

Re: [regext] CALL FOR ADOPTION: draft-gould-regext-rdap-versioning draft-newton-regext-rdap-extensions draft-newton-regext-rdap-x-media-type

+1 --Dan On 2/7/24, 9:58 AM, "regext on behalf of Jody Kolker" mailto:regext-boun...@ietf.org> on behalf of jkolker=40godaddy@dmarc.ietf.org > wrote: Caution: This email originated from outside the organization. Do not click links or open attachments

Re: [regext] CALL FOR ADOPTION: draft-jasdips-regext-rdap-geofeed

+1 --Dan On 11/20/23, 3:12 PM, "regext on behalf of kowa...@denic.de " mailto:regext-boun...@ietf.org> on behalf of kowa...@denic.de > wrote: I support adoption and I am willing to review. Pawel Am 20.11.23 um 15:36 schrieb Antoin Verschu

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

Re: [regext] New Version Notification for draft-newton-regext-rdap-extensions-00.txt

Cross-posting under the correct thread. Sorry for the churn. --Dan From: regext on behalf of "Keathley, Daniel" Date: Thursday, July 20, 2023 at 3:33 PM To: "a...@hxr.us" , "Gould, James" Cc: "regext@ietf.org" Subject: [EXTERNAL] Re: [regext] Ne

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

Hi Andy, This draft has been quite helpful for me. As you say, in several instances you simply parrot what is already present in existing RFCs; this illustrates just how well-hidden the references are in those documents. Pulling them into a focused, consolidated draft helps frame the bigger pic

Re: [regext] WGLC: draft-ietf-rdap-openid-22

+1 --Dan On 6/26/23, 11:14 AM, "regext on behalf of Hollenbeck, Scott" mailto:regext-boun...@ietf.org> on behalf of shollenbeck=40verisign@dmarc.ietf.org > wrote: Caution: This email originated from outside the organization. Do not click links or o

Re: [regext] WGLC: draft-ietf-regext-rdap-redacted-11

+1 --Dan On 4/24/23, 1:37 PM, "regext on behalf of Pawel Kowalik" mailto:regext-boun...@ietf.org> on behalf of kowa...@denic.de > wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sen

Re: [regext] [Ext] Re: draft-ietf-regext-epp-eai Path Forward

+1, I support a cardinality of one. --Dan From: regext on behalf of Gustavo Lozano Ibarra Date: Thursday, March 2, 2023 at 11:00 AM To: Jody Kolker , Rick Wilhelm , Roger D Carney , "regext@ietf.org" Subject: [EXTERNAL] Re: [regext] [Ext] Re: draft-ietf-regext-epp-eai Path Forward +1, I s

Re: [regext] Call for agenda items IETF 116

Hi Jim, Antoin, I'd like to request a 5-10 minute slot to introduce the RDAP versioning extension (draft-gould-regext-rdap-versioning). I will be attending virtually. Let me know if you need any further information. Thanks, --Dan On 2/13/23, 9:18 AM, "regext on behalf of Antoin Verschuren"

Re: [regext] Review of draft-ietf-regext-rdap-redacted-09

+1 for option 1. --Dan On 12/13/22, 9:31 AM, "regext on behalf of Andrew Newton" wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. I think Jody captured my thoug