Hi all, The new charter is now active. Thank you all for the inputs provided as part of this process.
Cheers, Med > -----Message d'origine----- > De : The IESG <[email protected]> > Envoyé : jeudi 2 juillet 2026 18:29 > À : IETF-Announce <[email protected]> > Cc : The IESG <[email protected]>; [email protected]; > [email protected] > Objet : [iesg] WG Action: Rechartered Registration Protocols > Extensions (regext) > > > The Registration Protocols Extensions (regext) WG in the > Operations and Management Area of the IETF has been rechartered. > For additional information, please contact the Area Directors or > the WG Chairs. > > Registration Protocols Extensions (regext) > ------------------------------------------------------------------ > Current status: Active WG > > Chairs: > James Galvin <[email protected]> > Antoin Verschuren <[email protected]> > Jorge Cano <[email protected]> > > Assigned Area Director: > Mohamed Boucadair <[email protected]> > > Operations and Management Area Directors: > Mahesh Jethanandani <[email protected]> > Mohamed Boucadair <[email protected]> > > Mailing list: > Address: [email protected] > To subscribe: > > Charter: > > The Extensible Provisioning Protocol (EPP, STD 69) is an > application-layer client-server protocol for the provisioning and > management of objects stored in a shared central repository. The > Registration Data Access Protocol (RDAP, STD 95) is a protocol for > retrieving registration data and metadata from both Domain Name > Registries (DNRs) and Regional Internet Registries (RIRs). > > The Registration Protocols Extensions Working Group (REGEXT WG) is > responsible for maintenance and operations of both EPP and RDAP. > Also, REGEXT provides practitioners, domain registries and > registrars, number resources registries, and other interested > parties who wish to share operational experience, challenges, and > lessons learned, a venue to engage in discussions around the > operational requirements of EPP and RDAP deployments. > > ## Work Scope > > The WG is responsible for specifying updates and extensions to > these protocols (Standards Track or Experimental), documenting > operational issues and specifying mitigations to those > (Informational/Best Current Practice/Standards Track), providing > guidance for defining extensions (Informational or Best Current > Practice), and elaborating deployment recommendations > (Informational or Best Current Practice). Also, the WG is > responsible for maintenance of the registration procedures for the > EPP and RDAP IANA registries. > > Additionally, the WG will publish documents addressing > interoperability issues related to EPP and RDAP. This includes, in > particular: > > * Data formats for exchanges between registration entities that > need insertion or extraction using EPP or extraction using RDAP > (Standards Track or Experimental). * New application transport > mappings for EPP following relevant and appropriate IETF standards > to address operational gaps for which at least one domain registry > and at least one domain registrar have made a commitment to deploy > (Standards Track or Experimental). * Best practices for the > deployment and operation of EPP and RDAP, including security and > scalability considerations (Informational or Best Current > Practice). > > The WG is responsible for the maintenance of RFC 3735 (Guidelines > for Extending the Extensible Provisioning Protocol (EPP)), > including progressing it from Informational to Best Current > Practice. > > ## Liaison and Coordination > > The WG will follow existing BCPs (mainly BCP 56 on Building > Protocols with > HTTP) and will seek advice from the WIT area on HTTP and transport > matters, in particular. Likewise, the WG will solicit feedback > from other relevant WGs (e.g., DNSOP and SIDROPS) as needed. > > The WG will discuss revisions of EPP and RDAP registration > procedures with past and current Designated Experts for such > registries to take into account their experience. > ____________________________________________________________________________________________________________ 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]
