For the historical record, I did want to clarify that only the “epp-over-http” doc had 5 indications of support. The “app-over-quic” document only had 4 indications of support.
The objection noted was that the benefits of the addition of Quic as a transport are not clear, and that if there are to be two standard transports we should indicate how one decides to choose one over the other. The chairs believe this an important technical question that should be as part of reviewing both documents. The working group can decide during discussion to only advance one document or to make sure that both documents indicate the advantages of their respective protocol. These documents are adopted by the working group. Thanks, Antoin and Jim On 24 Feb 2025, at 8:47, James Galvin wrote: > As there have not been any objections and with 5 indications of support these > two documents are now adopted by the working group. > > The respective authors are asked to please upload a “-00” version of their > document that is the same as the current version of the individual document. > The pre-approved name for the documents are as follows: > > draft-yao-regext-epp-quic/ ==> draft-ietf-regext-epp-quic > > draft-loffredo-regext-epp-over-http/ ==> draft-ietf-regext-epp-https > (please note the “s” on “http”) > > Both documents are in need of a document shepherd. If you’d like to > volunteer please let the Chairs know. > > Following our process of new documents getting the next available milestone, > the milestone for both these documents will be September 2025. Note that > documents progress according to the interest and energy of the authors and > the working group. > > Thanks, > > Antoin and Jim > > > > On 3 Feb 2025, at 9:05, James Galvin wrote: > >> Continuing our potential adoption of new documents, as previously discussed >> the next two documents will be taken together. The suggestion is to advance >> them together, although if these are adopted the working group can choose to >> advance them separately. >> >> This is a formal adoption request for both: >> >> Extensible Provisioning Protocol (EPP) Transport over QUIC >> https://datatracker.ietf.org/doc/draft-yao-regext-epp-quic/ >> >> Extensible Provisioning Protocol (EPP) Transport over HTTPS >> https://datatracker.ietf.org/doc/draft-loffredo-regext-epp-over-http/ >> >> Please review these drafts to see if you think they are suitable for >> adoption by REGEXT and reply to this message on the list, clearly stating >> your view. Optionally indicate if you are willing to contribute text, >> review text, or be a document shepherd. >> >> This Call For Adoption will close on Sunday, 16 February 2025. >> >> If there are no objections, the chairs will consider these documents adopted. >> >> Thanks, >> >> Your REGEXT co-chairs Antoin and Jim _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
