TBD R. Salz
Internet-Draft Akamai Technologies
Updates: 3710, 3929, 4633, 6702, 9281 (if 1 April 2025
approved)
Intended status: Best Current Practice
Expires: 3 October 2025
Update to RFC 8717: IETF Administrative Terminology
draft-rsalz-8717-update-01
Abstract
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 be done, and who the responsible
entity is, are described.
Discussion Venues
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.
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.
Salz Expires 3 October 2025 [Page 1]
Internet-Draft 8717update April 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
3. Updates Being Made . . . . . . . . . . . . . . . . . . . . . 3
3.1. Changes to RFC 3710 . . . . . . . . . . . . . . . . . . . 3
3.2. Changes to RFC 3929 . . . . . . . . . . . . . . . . . . . 4
3.3. Changes to RFC 4633 . . . . . . . . . . . . . . . . . . . 4
3.4. Changes to RFC 6702 . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
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.
Salz Expires 3 October 2025 [Page 2]
Internet-Draft 8717update April 2025
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 (https://mailman3.ietf.org/mailman3/lists/procon.ietf.org/). An
online document proposing changes to RFC 2418 to comply with this
document (https://github.com/richsalz/draft-rsalz-2418bis/pull/14)
are available.
The following sub-sections make the specific changes for each RFC and
therefore this document completely replaces Section 2 of RFC 8717.
3.1. Changes to RFC 3710
[RFC3710], Section 2 describes the composition of the IESG and
mentions the IETF Executive Director twice.
The first mention:
The Internet Architecture Board (IAB) Chair and the IETF Executive
Director, as ex-officio members of the IESG.
Is replaced with the following text:
The Internet Architecture Board (IAB) Chair and the IETF Executive
Director or their designee, as ex-officio members of the IESG.
The second mention:
The IETF Executive Director is the person charged with running the
IETF Secretariat.
is deleted.
Salz Expires 3 October 2025 [Page 3]
Internet-Draft 8717update April 2025
3.2. Changes to RFC 3929
[RFC3929] is an Experimental RFC published in 2004. This document
changes its status to Historic.
3.3. Changes to RFC 4633
[RFC4633] is an Experimental RFC published in 2006. This document
changes its status to Historic.
3.4. Changes to RFC 6702
[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 specifies an email address to be used for that
purpose:
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
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
[RFC3710] Alvestrand, H., "An IESG charter", RFC 3710,
DOI 10.17487/RFC3710, February 2004,
<https://www.rfc-editor.org/rfc/rfc3710>.
Salz Expires 3 October 2025 [Page 4]
Internet-Draft 8717update April 2025
[RFC3929] Hardie, T., "Alternative Decision Making Processes for
Consensus-Blocked Decisions in the IETF", RFC 3929,
DOI 10.17487/RFC3929, October 2004,
<https://www.rfc-editor.org/rfc/rfc3929>.
[RFC4633] Hartman, S., "Experiment in Long-Term Suspensions From
Internet Engineering Task Force (IETF) Mailing Lists",
RFC 4633, DOI 10.17487/RFC4633, August 2006,
<https://www.rfc-editor.org/rfc/rfc4633>.
[RFC6702] Polk, T. and P. Saint-Andre, "Promoting Compliance with
Intellectual Property Rights (IPR) Disclosure Rules",
RFC 6702, DOI 10.17487/RFC6702, August 2012,
<https://www.rfc-editor.org/rfc/rfc6702>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8717] Klensin, J., Ed., "IETF Administrative Support Activity
2.0: Consolidated Updates to IETF Administrative
Terminology", BCP 101, RFC 8717, DOI 10.17487/RFC8717,
February 2020, <https://www.rfc-editor.org/rfc/rfc8717>.
6.2. Informative References
[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in
the IETF Standards Process", RFC 2028,
DOI 10.17487/RFC2028, October 1996,
<https://www.rfc-editor.org/rfc/rfc2028>.
[RFC2418] Bradner, S., "IETF Working Group Guidelines and
Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418,
September 1998, <https://www.rfc-editor.org/rfc/rfc2418>.
[RFC2606] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS
Names", BCP 32, RFC 2606, DOI 10.17487/RFC2606, June 1999,
<https://www.rfc-editor.org/rfc/rfc2606>.
[RFC8179] Bradner, S. and J. Contreras, "Intellectual Property
Rights in IETF Technology", BCP 79, RFC 8179,
DOI 10.17487/RFC8179, May 2017,
<https://www.rfc-editor.org/rfc/rfc8179>.
[RFC9281] Salz, R., "Entities Involved in the IETF Standards
Process", BCP 11, RFC 9281, DOI 10.17487/RFC9281, June
2022, <https://www.rfc-editor.org/rfc/rfc9281>.
Salz Expires 3 October 2025 [Page 5]
Internet-Draft 8717update April 2025
Acknowledgments
Just me.
Author's Address
Rich Salz
Akamai Technologies
Email: rsalz@akamai.com
Salz Expires 3 October 2025 [Page 6]