Hi Jim,

I support adoption of these documents, and am willing to contribute, review, 
and act as a document shepherd (for either, or both if no-one else volunteers).
G.

> On 3 Feb 2025, at 14:05, James Galvin <gal...@elistx.com> 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://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-yao-regext-epp-quic/__;!!PtGJab4!7l2B5IiUp353vA2e00T0VkAQDSDa-xTIBXlJP4tG24zwhuGx517uHT3uwAcfeDdqQanhG0kZj0PRr0GtHdUOfVo$
>  [datatracker[.]ietf[.]org]
> 
> Extensible Provisioning Protocol (EPP) Transport over HTTPS
> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-loffredo-regext-epp-over-http/__;!!PtGJab4!7l2B5IiUp353vA2e00T0VkAQDSDa-xTIBXlJP4tG24zwhuGx517uHT3uwAcfeDdqQanhG0kZj0PRr0Gt_9i_Zv8$
>  [datatracker[.]ietf[.]org]
> 
> 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

--
Gavin Brown
Principal Engineer, Global Domains & Strategy
Internet Corporation for Assigned Names and Numbers (ICANN)

https://www.icann.org

_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org

Reply via email to