[regext] regext - Requested sessions have been scheduled for IETF 120
Dear Antoin Verschuren, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. regext Session 1 (1:00 requested) Monday, 22 July 2024, Session IV 1730-1830 America/Vancouver Room Name: Georgia B [Breakout 4] (size: 140) - regext Session 2 (2:00 requested) Wednesday, 24 July 2024, Session II 1300-1500 America/Vancouver Room Name: Plaza B [Breakout 3] (size: 120) - iCalendar: https://datatracker.ietf.org/meeting/120/sessions/regext.ics Request Information: - Working Group Name: Registration Protocols Extensions Area Name: Applications and Real-Time Area Session Requester: Antoin Verschuren Number of Sessions: 2 Length of Session(s): Number of Attendees: 50 Conflicts to Avoid: Participants who must be present: Resources Requested: Special Requests: - ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
[regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03
+1 From: James Galvin Sent: 24 June 2024 15:26 To: REGEXT Working Group Subject: [regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03 The Chairs have decided to extend this WGLC last call for two weeks, one more week from the date of this message. There has only been on indication of support and two different threads discussing some minor changes. We would like these discussion to resolve and for there to be more indications of support for this document. Please indicate your support or no objection for the publication of this document by replying to this message on list (a simple “+1” is sufficient). If any working group member has questions regarding the publication of this document please respond on the list with your concerns by close of business everywhere, Monday, 1 July 2024. Thanks, Antoin and Jim On 3 Jun 2024, at 10:56, James Galvin wrote: > The document editors have indicated that the following document is ready for > submission to the IESG to be considered for publication as a Best Current > Practice: > > Best Practices for Deletion of Domain and Host Objects in the Extensible > Provisioning Protocol (EPP) > https://datatracker.ietf.org/doc/draft-ietf-regext-epp-delete-bcp/03/ > > Please indicate your support or no objection for the publication of this > document by replying to this message on list (a simple “+1” is sufficient). > > If any working group member has questions regarding the publication of this > document please respond on the list with your concerns by close of business > everywhere, Monday, 17 June 2024. > > If there are no objections the document will be submitted to the IESG. > > The Document Shepherd for this document is Andy Newton. > > Thanks, > > Antoin and Jim > REGEXT WG Co-Chairs ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
[regext] I-D Action: draft-ietf-regext-epp-delete-bcp-05.txt
Internet-Draft draft-ietf-regext-epp-delete-bcp-05.txt is now available. It is a work item of the Registration Protocols Extensions (REGEXT) WG of the IETF. Title: Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP) Authors: Scott Hollenbeck William Carroll Gautam Akiwate Name:draft-ietf-regext-epp-delete-bcp-05.txt Pages: 22 Dates: 2024-06-28 Abstract: The Extensible Provisioning Protocol (EPP) includes commands for clients to delete domain and host objects, both of which are used to publish information in the Domain Name System (DNS). EPP also includes guidance for deletions that is intended to avoid DNS resolution disruptions and maintain data consistency. However, operational relationships between objects can make that guidance difficult to implement. Some EPP clients have developed operational practices to delete those objects that have unintended impacts on DNS resolution and security. This document describes best current practices and proposes new potential practices to delete domain and host objects that reduce the risk of DNS resolution failure and maintain client-server data consistency. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-epp-delete-bcp/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-regext-epp-delete-bcp-05.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-epp-delete-bcp-05 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
