idnits 2.17.00 (12 Aug 2021) /tmp/idnits45043/draft-rosen-rfcefdp-update-2026-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The abstract seems to contain references ([I-D.iab-RFCefdp-rfced-model]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document date (10 March 2022) is 65 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-13) exists of draft-iab-rfcefdp-rfced-model-12 ** Downref: Normative reference to an Informational draft: draft-iab-rfcefdp-rfced-model (ref. 'I-D.iab-rfcefdp-rfced-model') Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Rosen 3 Internet-Draft 10 March 2022 4 Updates: RFC2026 (if approved) (if approved) 5 Intended status: Best Current Practice 6 Expires: 11 September 2022 8 RFC Series Responsibility Change 9 draft-rosen-rfcefdp-update-2026-02 11 Abstract 13 In [I-D.iab-rfcefdp-rfced-model], responsibility for the RFC series 14 moved to the RFC Series Working Group and the RFC Series Approval 15 Board. It is no longer the responsibility of the RFC Editor and the 16 role of the IAB in the RFC Series is altered. Accordingly, in 17 RFC2026 Section 2.1, the sentence "RFC publication is the direct 18 responsibility of the RFC Editor, under the general direction of the 19 IAB" is deleted. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on 11 September 2022. 38 Copyright Notice 40 Copyright (c) 2022 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 45 license-info) in effect on the date of publication of this document. 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. Code Components 48 extracted from this document must include Revised BSD License text as 49 described in Section 4.e of the Trust Legal Provisions and are 50 provided without warranty as described in the Revised BSD License. 52 Table of Contents 54 1. Responsibility Change . . . . . . . . . . . . . . . . . . . . 2 55 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 56 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 57 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 2 58 4.1. Normative References . . . . . . . . . . . . . . . . . . 2 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1. Responsibility Change 63 In [I-D.iab-rfcefdp-rfced-model], responsibility for the RFC series 64 moved to the RFC Series Working Group and the RFC Series Approval 65 Board. It is no longer the responsibility of the RFC Editor and the 66 role of the IAB in the RFC Series is altered. Accordingly, in 67 [RFC2026] Section 2.1, the sentence "RFC publication is the direct 68 responsibility of the RFC Editor, under the general direction of the 69 IAB" is deleted. 71 2. IANA Considerations 73 This memo includes no request to IANA. 75 3. Security Considerations 77 This document presents no security considerations. 79 4. References 81 4.1. Normative References 83 [I-D.iab-rfcefdp-rfced-model] 84 Saint-Andre, P., "RFC Editor Model (Version 3)", Work in 85 Progress, Internet-Draft, draft-iab-rfcefdp-rfced-model- 86 12, 4 March 2022, . 89 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 90 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 91 . 93 Author's Address 95 Brian Rosen 96 470 Conrad Dr 97 Mars, PA 16046 98 United States of America 99 Email: br@brianrosen.net