Update to RFC 8717: IETF Administrative Terminology

Status of This Memo

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 3 October 2025.¶

Copyright Notice

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.¶

Table of Contents

1. Introduction

[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, are described.¶

This document updates [RFC3710] and [RFC6702]. It also changes the status of [RFC3929] and [RFC4633] to Historic.¶

2. Conventions and Definitions

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.¶

3. Updates Being Made

[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.¶

The Internet Architecture Board (IAB) Chair and the IETF Executive
Director, as ex-officio members of the IESG.

The Internet Architecture Board (IAB) Chair and the IETF Executive
Director or their designee, as ex-officio members of the IESG.

The IETF Executive Director is the person charged with running the
IETF Secretariat.

To help prevent early IPR disclosures from becoming stale
or incomplete, at important junctures in the standardization process
(e.g., at working group adoption, before Working Group Last Call, and
before IETF Last Call) WG chairs and ADs are encouraged to request
that the Executive Director of the IETF contact those who submitted
early IPR disclosures about updating their disclosures by
sending email to XXX@ietf.org.

4. Security Considerations

This document has no security considerations.¶

5. IANA Considerations

This document has no IANA actions.¶

6. References

Acknowledgments

Just me.¶

Author's Address