[regext] Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http

2025-02-04 Thread kowalik
A clear +1 for adoption of DoH. For DoQ I share the opinions expressed in the room in IETF 119 session, that benefits from adding this transport are not clear, so I don't think we should spend cycles on this draft until this is better answered. Adding this new transport on a Standard track wou

[regext] Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http

2025-02-04 Thread Mario Loffredo
I support adoption of draft-yao-regext-epp-quic. As the author of draft-loffredo-regext-epp-over-http, don't believe my vote in favor can count :-) Mario Il 03/02/2025 15:05, James Galvin ha scritto: Continuing our potential adoption of new documents, as previously discussed the next two do

[regext] Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http

2025-02-04 Thread kowa...@denic.de
Hi Jim, Got it. Is it a problem to solve or solution looking for a problem? Kind regards, Pawel On 04.02.25 14:38, Gould, James wrote: Pawel, I will mirror what I stated at the IETF 119 session, that there are economies of scale to have both EoH and EoQ progress at the same time. Based on

[regext] Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http

2025-02-04 Thread Gould, James
Pawel, I would state that it’s providing an additional option for server and client implementers based on the advantages and disadvantages of each of the transports. EoT has worked well for many years, EoH provides enhanced Cloud capabilities, and EoQ provides some interesting security and pe

[regext] Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http

2025-02-04 Thread Gould, James
Pawel, I will mirror what I stated at the IETF 119 session, that there are economies of scale to have both EoH and EoQ progress at the same time. Based on my implementation experience with EoQ, it has security and functional advantages over EoT. Specifically, the encryption is setup ahead of

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

2025-02-04 Thread Antoin Verschuren
Hi all, This call for adoption closed yesterday. We have 4 people that support and no rejections, with 2 people raising concerns, so the chairs consider this document adopted with remarks. We will adopt the document so work can start, but the chairs want the authors to know that we will evaluat

[regext] Secdir last call review of draft-ietf-regext-rdap-rir-search-14

2025-02-04 Thread Russ Housley via Datatracker
Reviewer: Russ Housley Review result: Ready I reviewed this document as part of the Security Directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Security Area Directors. Document authors, document edi

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

2025-02-04 Thread Jasdip Singh
Hi Antoin, Jim, Scott Hollenbeck has graciously agreed to be the document shepherd for this draft. :) Jasdip From: Jasdip Singh Date: Tuesday, February 4, 2025 at 12:51 PM To: Antoin Verschuren , regext Subject: [regext] Re: CALL FOR ADOPTION: draft-jasdips-regext-rdap-rpki Hi Antoin, Jim,

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

2025-02-04 Thread Jasdip Singh
Hi Antoin, Jim, Version 00 of this draft has now been submitted. Good idea to have the RPKI experts also review it. We’d next look for the document shepherd. :) Thanks, Jasdip From: Antoin Verschuren Date: Tuesday, February 4, 2025 at 11:57 AM To: regext Subject: [regext] Re: CALL FOR ADOPTI