Hi all, Thank you all for the feedback.
I updated the charter to add the item proposed by Mario (see below). I tweaked the text so that the new bullet grafts well with the preamble of that bullet list. The updated text can be seen here: https://datatracker.ietf.org/doc/charter-ietf-regext/. Cheers, Med > -----Message d'origine----- > De : James Galvin <[email protected]> > Envoyé : lundi 1 juin 2026 17:07 > À : REGEXT WG <[email protected]> > Objet : [regext] Re: RECHARTERING of REGEXT > > > This is a reminder for the working group to review the proposed > charter revision. Currently, we have 4 indications of support. > > The deadline for this review is Friday, 5 June 2026. > > one change has been proposed: To add a bullet to the Work Scope as > follows: "Best practices for the deployment and operation of EPP > and RDAP, including recommendations for security, scalability, and > interoperability." > > If there are no objections this will be included. > > Are there any other questions or suggestions to consider? Please > reply on the list if you have any concerns. > > Thanks, > > Jorge, Antoin, Jim > > > On 22 May 2026, at 10:30, James Galvin wrote: > > > This message begins a two week period for the Working Group to > review a proposed new charter. > > > > As you know, we have both a new Area and a new Area Director for > our working group as of IETF125. Mohamed Boucadair has previously > introduced himself and our new area: Operations and Management > Area (ops). > > > > As part of this move it is being proposed to update our charter. > After reviewing the work we have been doing and looking forward to > work that may come our way, as well as alignment with our new > area, on behalf of the IESG Med is proposing the following charter > for our consideration: > > > > > https://fra01.safelinks.protection.outlook.com/?url=https%3A > %2F%2Fgithub.com%2FIETF-OPS- > AD%2FCharters%2Fblob%2Fmain%2Fregext.md&data=05%7C02%7Cmohamed.bou > cadair%40orange.com%7Cc53b6c0d47ef42ed96eb08debff0adb2%7C90c7a20af > 34b40bfbc48b9253b6f5d20%7C0%7C0%7C639159237599710605%7CUnknown%7CT > WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4 > zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Iav%2FIon > aiAv8k%2F7W8VDdaqg8mgWrWrHGkjmOaSy5oBI%3D&reserved=0 > > > > The goal is to have this revised charter in place before > IETF126. We have a pretty tight schedule in order to achieve > this, which looks like this: > > > > - 22/05: Begin WG Review of Proposed Charter > > - 05/06: Consolidate the final version to place in the IESG > Telechat of 2026-06-18 > > - 18/06: IESG internal review + release required revisions to > address IESG comments > > - * IETF Community review > > - 02/07: IESG final review > > > > Our working group review begins now and will be open for 2 > weeks, until Friday, 5 June. > > > > Please review this proposed charter and bring any questions or > comments you have to the mailing list. > > > > Thanks in advance for your prompt review and consideration! > > > > Antoin, Jorge, and Jim > > _______________________________________________ > regext mailing list -- [email protected] > To unsubscribe send an email to [email protected] ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
