That would be the simplest solution. Open to suggestions though... -andy On 5/27/26 7:03 PM, Scott Hollenbeck wrote: > I see your point. What if "shall be grounded in operational experience from > at least two independent deployments and" is removed? > > Scott > >> -----Original Message----- >> From: Andy Newton <[email protected]> >> Sent: Wednesday, May 27, 2026 6:35 PM >> To: Scott Hollenbeck <[email protected]>; 'Mario Loffredo' >> <[email protected]>; [email protected] >> Subject: Re: [regext] Re: RECHARTERING of REGEXT >> >> Does the last sentence set too high of a bar? Because I don't think RFC9874 >> would have been in charter if that had been in affect. Not that I disagree >> with >> the general direction of basing docs on real-world experience, but I also >> think >> something like RFC9874 would be necessary to do regardless. >> >> Also, I don't know how to relate "deployments" to RDAP clients. Does this >> preclude the group writing BCPs on RDAP clients? >> >> -andy, as an individual >> >> On 5/27/26 7:23 AM, Scott Hollenbeck wrote: >>> I like Mario’s suggestion. Such documents aren’t extensions, but they’re >> directly related to operating EPP and RDAP. +1 with that text included. >>> >>> >>> >>> Scott >>> >>> >>> >>> *From:*Mario Loffredo <[email protected]> >>> *Sent:* Monday, May 25, 2026 11:53 AM >>> *To:* [email protected] >>> *Subject:* [regext] Re: RECHARTERING of REGEXT >>> >>> >>> >>> Hi, >>> >>> I have some doubts about the sentence "This includes, *but is not limited >> to:*". >>> >>> On the one hand, it leaves room for the adoption of documents that >> address topics not mentioned in the charter, but which are then deemed >> relevant by working group members. >>> >>> On the other hand, a loosely defined scope could lead to big discussions >> about documents that address topics that some members consider out-of- >> scope, while others do not. Such discussions have sometimes stalled the >> WG's activity and the document development process for months. >>> >>> Honestly, I can't decide what is best. :-( >>> >>> In any case, I would add the following to the bulleted list in the "Scope of >> Work" section: >>> >>> "/Best practices for the deployment and operation of EPP and RDAP, >> including recommendations for security, scalability, and interoperability. >> Such documents shall be grounded in operational experience from at least >> two independent deployments and may be published on the Informational or >> BCP track as appropriate./" >>> >>> >>> >>> Best, >>> >>> Mario >>> >>> >>> >>> >>> >>> Il 22/05/2026 16:30, James Galvin ha scritto: >>> >>> 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://github.com/IETF-OPS-AD/Charters/blob/main/regext.md >> <https://github.com/IETF-OPS-AD/Charters/blob/main/regext.md> >>> >>> >>> >>> 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] <mailto:[email protected]> >>> >>> To unsubscribe send an email to [email protected] <mailto:regext- >> [email protected]> >>> >>> -- >>> >>> Dott. Mario Loffredo >>> >>> Senior Technologist >>> >>> Technological Unit “Digital Innovation” >>> >>> Institute of Informatics and Telematics (IIT) >>> >>> National Research Council (CNR) >>> >>> Address: Via G. Moruzzi 1, I-56124 PISA, Italy >>> >>> Phone: +39.0503153497 >>> >>> Web: http://www.iit.cnr.it/mario.loffredo >> <http://www.iit.cnr.it/mario.loffredo> >>> >>> >>> _______________________________________________ >>> regext mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
