| Internet-Draft | 8717update | March 2025 |
| Salz | Expires 4 September 2025 | [Page] |
RFC 8717 updated several RFCs pertaining to the organization of the IETF to use the term "Managing Director, IETF Secretariat" (MDS). As that term does not accurately reflect the organization or roles of the IETF staff, the MDS term is no longer relevant. This document removes mention of particular staff roles, and instead updates the source documents so that the job to done, and who the responsible entity is (generally, the IETF LLC) are described.¶
This note is to be removed before publishing as an RFC.¶
Source for this draft and an issue tracker can be found at https://github.com/richsalz/draft-8717-update.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 4 September 2025.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
[RFC8717] updated several RFCs pertaining to the organization of the IETF to use the term "Managing Director, IETF Secretariat" (MDS). As that term does not accurately reflect the organization or roles of the IETF staff, the MDS term is no longer relevant. This document removes mention of particular staff roles, and instead updates the source documents so that the job to done, and who the responsible entity is (generally, the IETF LLC) are described.¶
This document updates [RFC3710], [RFC3929], [RFC4633], and [RFC6702].¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCPÂ 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
[RFC8717], Section 2 explained that [RFC2606] did not need to be updated because [RFC8179] removed the need for it. While the same section of RFC 8717 provided an update to [RFC2028], that has similarly been overtaken by events in that it was obsoleted by [RFC9281], and Section 3 of RFC 9281 does not need revising.¶
Further, the IETF is in the "consideration" stage of forming a working group to update [RFC2418]; for discussion, see the mailing list. An online document proposing changes to RFC 2418 to comply with this document are available.¶
The following sub-sections make the specific changes for each RFC and therefore this document completely replaces Section 2 of RFC 8717.¶
[RFC3710], Section 2 describes the composition of the IESG. This section is updated to replace the original text that twice mentions "IETF Executive Director" with "a member of the IETF staff as specified by the IETF LLC."¶
RFC 3929, an Experimental RFC, proposes a number of methods to resolve a deadlock when an IETF Working Group is unable to come to a decision.¶
[RFC3929], Section 4.1.1 says that volunteers should send their names to the IETF Executive Directory, who should use [RFC3797] to choose if their is an excess of volunteers. As the IESG is responsible for the standards process, this task should be fulfilled by someone they announce.¶
Similarly, in [RFC3929], Section 4.3 an alternate method is described. Again, the text is changed so that the IESG announces who will perform that task.¶
[RFC4633], Section 1 says that the IETF Executive Director is empowered to restrict posting to the IETF discussion list.¶
This document updates RFC 4633 to remove that ability.¶
[RFC6702], Section 5 says that WG Chairs and Area Directors are encouraged to ask the IETF Executive Directory to contact those who submitted an early intellectual property disclosure and request an update.¶
This document updates RFC 6702 to say that the IETF LLC, or their designee, should be contacted.¶
This document has no security considerations.¶
This document has no IANA actions.¶
Just me.¶