Re: [regext] Re-chartering REGEXT?

Thanks George. I agree.

-andy

On Mon, Apr 15, 2024 at 4:14 PM George Michaelson <ggm@algebras.org> wrote:
>
> I don't think the new protocol is just a new transport *LAYER* but I
> also do support re-charter to include consideration of this protocol
> suite.
>
> My reasoning is that we're the people who are going to wind up having
> to talk about it. Of course it's irritating from a perspective of RDAP
> and EPP proponents to see more work jammed into this WG and I actually
> generally dislike charter extension, but the context is clear:
>
> The protocol is in the registry-registrar and client-registrar
> interaction space we work on.
>
> G
>
> On Tue, Apr 16, 2024 at 3:37 AM Gould, James
> <jgould=40verisign.com@dmarc.ietf.org> wrote:
> >
> > Andy,
> >
> > REPP is not a transport, but a new provisioning protocol that is not supported in the existing charter.  If you believe REPP is a transport, please describe how it complies with section 2.1 of RFC 5730.
> >
> > Thanks,
> >
> > --
> >
> > JG
> >
> >
> >
> > James Gould
> > Fellow Engineer
> > jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>
> >
> > 703-948-3271
> > 12061 Bluemont Way
> > Reston, VA 20190
> >
> > Verisign.com <http://verisigninc.com/>
> >
> >
> >
> >
> > On 4/15/24, 1:20 PM, "regext on behalf of Andrew Newton (andy)" <regext-bounces@ietf.org <mailto:regext-bounces@ietf.org> on behalf of andy@hxr.us <mailto:andy@hxr.us>> 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.
> >
> >
> > Maarten,
> >
> >
> > I think proposing some charter text is a good idea.
> >
> >
> > And I support this if the charter is to be used to exclude some
> > proposals for EPP transports but not others, as has been argued.
> >
> >
> > -andy
> >
> >
> > On Thu, Apr 11, 2024 at 11:59 PM Maarten Wullink
> > <maarten.wullink=40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org>> wrote:
> > >
> > > Hello everyone,
> > >
> > > The REGEXT WG charter seems to be limited to only allow work on EPP extensions?
> > >
> > > The WG preliminary consensus is that updating the charter for new transports (requires RFC5730, sec 2.1 compliance) is not required.
> > > Because a new transport is regarded as a type of extension, so for anything else we would need to update the charter?
> > >
> > > This means there is no defined process anywhere, currently, for EPP related work, such as RESTful EPP (or anything else that is not a extension),
> > > which according to some in this WG is not a transport but something else.
> > >
> > > RESTful EPP does not require modification of the EPP RFCs, it does include support for alternative data representations such as JSON.
> > >
> > > The participants of this WG are the experts in this area, and the right people to also work on improvements and/or enhancements of the EPP protocol and new work such as RESTful EPP.
> > >
> > > Therefore, I propose that we expand the charter of this WG to also include the above-mentioned activities e.g. not strictly limiting the WG to extensions only.
> > >
> > > I’m willing to help in updating the charter if this something we agree on doing.
> > >
> > > Best,
> > >
> > > Maarten
> > >
> > > ------
> > > ps:
> > >
> > > The previous version of the charter included text, that did allow work on more than extensions only:
> > >
> > > “The working group may also, in consultation with its responsible area
> > > director, take on work related to the operation of Internet identifier
> > > registries, beyond the EPP and RDAP protocols.”
> > >
> > > See: https://secure-web.cisco.com/1pZ9xY4B2hhezD1LASpYU9C9QLU_I8ijwDhrAONiX2WujSy1_vkXH6R3dC-XOs3hs8GhnjSqn4hoIrURMcauciMp2aW9yObvXrtcQfNn5y39QAI_y_nrDueqrchdGrckElb2y8uY6jnSOVocfgGUy3JGWGYYRDY4eaaVGYW4p0HCiWXl_U-V5l_hWGXcSEavgzX-crhYmdNvhH-u2THur7He9dDY47ixzEm4kaOgHenXF4Mjj6Xw63FB7TA6StLsEn1cH4ZzXrkRso6sqhMOPIxW0M12SiAp3Az1rqdgYd_E/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-regext%2F01-00%2F <https://secure-web.cisco.com/1pZ9xY4B2hhezD1LASpYU9C9QLU_I8ijwDhrAONiX2WujSy1_vkXH6R3dC-XOs3hs8GhnjSqn4hoIrURMcauciMp2aW9yObvXrtcQfNn5y39QAI_y_nrDueqrchdGrckElb2y8uY6jnSOVocfgGUy3JGWGYYRDY4eaaVGYW4p0HCiWXl_U-V5l_hWGXcSEavgzX-crhYmdNvhH-u2THur7He9dDY47ixzEm4kaOgHenXF4Mjj6Xw63FB7TA6StLsEn1cH4ZzXrkRso6sqhMOPIxW0M12SiAp3Az1rqdgYd_E/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-regext%2F01-00%2F>
> > >
> > > This was modified for the current charter, but still not very specific and may allow for work on RESTful EPP?
> > >
> > > "The working group may also take on work to develop specifications that
> > > describe the following types of information exchanged between entities
> > > involved in Internet identifier registration that are using the RDAP or
> > > EPP protocols:
> > > • Uniform representation formats for publishing local policy or
> > > configuration options regarding EPP and RDAP use.
> > > • Data formats for files exchanged between registration entities that
> > > need insertion in or extraction from EPP or RDAP.
> > > • Technical guidance for registration processes that are supported by
> > > EPP or RDAP.”
> > >
> > >
> > > _______________________________________________
> > > regext mailing list
> > > regext@ietf.org <mailto:regext@ietf.org>
> > > https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
> >
> >
> > _______________________________________________
> > regext mailing list
> > regext@ietf.org <mailto:regext@ietf.org>
> > https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
> >
> >
> >
> > _______________________________________________
> > regext mailing list
> > regext@ietf.org
> > https://www.ietf.org/mailman/listinfo/regext
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext