[regext] Re: Charter question (was Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http)

["Gould, James" <[e-mail]>]

Andy,

We covered this previously, that based on the language of Section 2.1 of RFC 5730, EPP transports is a form of extension.  The reason that it's not covered in RFC 3735 is because a transport is not a packet protocol extension mechanism.  No recharter is necessary.  

-- 

JG 



James Gould
Fellow Engineer
[e-mail] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[e-mail]>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/> 




On 2/11/25, 12:26 PM, "Andrew Newton (andy)" <[e-mail] <mailto:[e-mail]>> 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. 


Hi all,


The work of REGEXT is to define extensions for EPP and RDAP, hence the
"EXT" in the name. With regards to the adoption calls for I-Ds
specifying new transports to EPP, where does this fall within the
charter? It has been stated that transports are EPP extensions, but
that argument cuts against the current RFCs. RFC 5730
discusses transports in section 2.1, separate from protocol extensions
in Section 2.7. And RFC 3735 lists 4 types of EPP extensions, none
being transports, and includes the sentence "EPP extensions MUST be
specified in XML."


As there does appear to be energy in the group to work on new EPP
transports, would the group be willing to recharter
to include the scope of I-Ds under discussion?


-andy
soon-to-be ART AD


On Mon, Feb 3, 2025 at 9:06 AM James Galvin <[e-mail] <mailto:[e-mail]>> 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://secure-web.cisco.com/1c59u1lmDw6RI4UB1TVeifmofsNfqJhC2A_M3xsYtEZ5JsQJv08encnJGXRU-FXYnWnXFfw2JK9TzjYx-CU6Qa5bHFLQlZBBwmesPeVFJ5uLsMGnk2JRhOtgGWWSst5ZWPeTkDj7qf2LHvxBDZgavZ0o6bEOBzR1vFSAX2Bd5b5vkZYQJP9W6f5txjar7lr8d0f3ZPZYjZOAWuViO5Beq2uPPNutJKWkOS47j_ajGrEOAztEcf7BYkdepLqMvHANkNpq0ago_aWjEAryUEuijSb_hh6rYtZ_MCJUCp-TyRKs/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-yao-regext-epp-quic%2F <https://secure-web.cisco.com/1c59u1lmDw6RI4UB1TVeifmofsNfqJhC2A_M3xsYtEZ5JsQJv08encnJGXRU-FXYnWnXFfw2JK9TzjYx-CU6Qa5bHFLQlZBBwmesPeVFJ5uLsMGnk2JRhOtgGWWSst5ZWPeTkDj7qf2LHvxBDZgavZ0o6bEOBzR1vFSAX2Bd5b5vkZYQJP9W6f5txjar7lr8d0f3ZPZYjZOAWuViO5Beq2uPPNutJKWkOS47j_ajGrEOAztEcf7BYkdepLqMvHANkNpq0ago_aWjEAryUEuijSb_hh6rYtZ_MCJUCp-TyRKs/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-yao-regext-epp-quic%2F>
>
> Extensible Provisioning Protocol (EPP) Transport over HTTPS
> https://secure-web.cisco.com/1y4Xvukc-z3Y2QbeUERbntI6wevzMhPXdlU59ZvgNSAfO8SLCA3q965rwxvQ1gFW8WTWrf3X-8Hixtuq5TFgKuoH47X-vOk-SXvL4R-Ibs1N6k1_OT8i1UUj_lBdcl83YRR6GOw0OOlIldlilkUg_LerYkuJK2ILTvrvjqrBBJu1A5KlstQxFHcKmd5ueM2PEKu5vljPNl8ze9KqeGddJz-zG6_iVXsOMKZDi-VNzOGj6sCCUgofGwLCivD4JLQtloOFZz-K46D8jkLM_H54cLp3mubPVrrDrt-m1e1bjfa0/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-loffredo-regext-epp-over-http%2F <https://secure-web.cisco.com/1y4Xvukc-z3Y2QbeUERbntI6wevzMhPXdlU59ZvgNSAfO8SLCA3q965rwxvQ1gFW8WTWrf3X-8Hixtuq5TFgKuoH47X-vOk-SXvL4R-Ibs1N6k1_OT8i1UUj_lBdcl83YRR6GOw0OOlIldlilkUg_LerYkuJK2ILTvrvjqrBBJu1A5KlstQxFHcKmd5ueM2PEKu5vljPNl8ze9KqeGddJz-zG6_iVXsOMKZDi-VNzOGj6sCCUgofGwLCivD4JLQtloOFZz-K46D8jkLM_H54cLp3mubPVrrDrt-m1e1bjfa0/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-loffredo-regext-epp-over-http%2F>
>
> 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 -- [e-mail] <mailto:[e-mail]>
> To unsubscribe send an email to [e-mail] <mailto:[e-mail]>


_______________________________________________
regext mailing list -- [e-mail] <mailto:[e-mail]>
To unsubscribe send an email to [e-mail] <mailto:[e-mail]>