Responsibility Change for the RFC Series
draft-rosen-rfcefdp-update-2026-02

[Ballot comment]
Thank you for the work done in this document.

Thanks to Wassim who did the INT directorate review at:
https://datatracker.ietf.org/doc/review-rosen-rfcefdp-update-2026-01-intdir-lc-haddad-2022-02-22/

(Same typo identified by Rob Wilton).

Regards

-éric

[Ballot comment]
In light of the distinction being made between "RFC Editor Function" and
"RFC Series Editor" (and, for that matter, "RFC Series Consulting Editor")
in draft-iab-rfcefdp-rfced-model, do we want to say that responsibility for
the RFC Series is no longer the responsibility of either of those entities,
as opposed to leaving it ambiguous?

[Ballot discuss]
Thanks for the effort here. I am putting a discuss as I agree with TSVART review by Bernard Aboba  about normative ref to iab-rfcefdp-rfced-model. That will be downref as well.

[Ballot comment]
(1) It should be indicated somewhere that this document should be part of BCP 9.  I prefer an RFC Editor Note in the ballot/IESG Writeup.  I did notice that the header includes "Updates:...BCP 9", but (trying not to get into the meaning of "updates") only RFCs should be listed there.

(2) The reference to draft-iab-rfcefdp-rfced-model should be Normative because it must be read to understand the change being made.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has reviewed draft-rosen-rfcefdp-update-2026-01, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
Lead IANA Services Specialist

The following Last Call announcement was sent out (ends 2022-03-07):

From: The IESG
To: IETF-Announce
CC: draft-rosen-rfcefdp-update-2026@ietf.org, lars@eggert.org
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (RFC Series Responsibility Change) to Best Current Practice


The IESG has received a request from an individual submitter to consider the
following document: - 'RFC Series Responsibility Change'
  as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-03-07. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  In RFCXXXX [RFC Editor, please replace with the RFC resulting from
  draft-iab-rfcefdp-rfced-model], responsibility for the RFC series
  moved to the RFC Series Working Group and the RFC Series Approval
  Board.  This document updates RFC2026 to recognize this change.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-rosen-rfcefdp-update-2026/



No IPR declarations have been submitted directly on this I-D.