draft-ietf-iasa2-rfc4844-bis-01.txt   draft-ietf-iasa2-rfc4844-bis-02.txt 
Network Working Group R. Housley, Ed. Network Working Group R. Housley, Ed.
Internet-Draft Vigil Security Internet-Draft Vigil Security
Obsoletes: 4844 (if approved) L. Daigle, Ed. Obsoletes: 4844 (if approved) L. Daigle, Ed.
Intended status: Informational Thinking Cat Intended status: Informational Thinking Cat
Expires: June 9, 2019 December 6, 2018 Expires: October 17, 2019 April 15, 2019
The RFC Series and RFC Editor The RFC Series and RFC Editor
draft-ietf-iasa2-rfc4844-bis-01 draft-ietf-iasa2-rfc4844-bis-02
Abstract Abstract
This document describes the framework for an RFC Series and an RFC This document describes the framework for an RFC Series and an RFC
Editor function that incorporate the principles of organized Editor function that incorporate the principles of organized
community involvement and accountability that has become necessary as community involvement and accountability that has become necessary as
the Internet technical community has grown, thereby enabling the RFC the Internet technical community has grown, thereby enabling the RFC
Series to continue to fulfill its mandate. Series to continue to fulfill its mandate.
Cover Note: Cover Note:
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 9, 2019. This Internet-Draft will expire on October 17, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 8 skipping to change at page 3, line 8
4.4.2. Operational Implementation . . . . . . . . . . . . . 11 4.4.2. Operational Implementation . . . . . . . . . . . . . 11
4.4.3. Process Change . . . . . . . . . . . . . . . . . . . 11 4.4.3. Process Change . . . . . . . . . . . . . . . . . . . 11
4.4.4. Existing Process Documents . . . . . . . . . . . . . 11 4.4.4. Existing Process Documents . . . . . . . . . . . . . 11
5. RFC Streams . . . . . . . . . . . . . . . . . . . . . . . . . 11 5. RFC Streams . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. RFC Approval Processes . . . . . . . . . . . . . . . . . 12 5.1. RFC Approval Processes . . . . . . . . . . . . . . . . . 12
5.1.1. IETF Document Stream . . . . . . . . . . . . . . . . 12 5.1.1. IETF Document Stream . . . . . . . . . . . . . . . . 12
5.1.2. IAB Document Stream . . . . . . . . . . . . . . . . . 12 5.1.2. IAB Document Stream . . . . . . . . . . . . . . . . . 12
5.1.3. IRTF Document Stream . . . . . . . . . . . . . . . . 12 5.1.3. IRTF Document Stream . . . . . . . . . . . . . . . . 12
5.1.4. Independent Submission Stream . . . . . . . . . . . . 13 5.1.4. Independent Submission Stream . . . . . . . . . . . . 13
5.2. RFC Technical Publication Requirements . . . . . . . . . 13 5.2. RFC Technical Publication Requirements . . . . . . . . . 13
5.2.1. IETF Documents . . . . . . . . . . . . . . . . . . . 13 5.2.1. IETF Documents . . . . . . . . . . . . . . . . . . . 14
5.2.2. IAB Documents . . . . . . . . . . . . . . . . . . . . 14 5.2.2. IAB Documents . . . . . . . . . . . . . . . . . . . . 14
5.2.3. IRTF Documents . . . . . . . . . . . . . . . . . . . 14 5.2.3. IRTF Documents . . . . . . . . . . . . . . . . . . . 14
5.2.4. Independent Submissions . . . . . . . . . . . . . . . 14 5.2.4. Independent Submissions . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. Changes Since RFC4844 . . . . . . . . . . . . . . . . . . . . 15 7. Changes Since RFC4844 . . . . . . . . . . . . . . . . . . . . 15
8. Informative References . . . . . . . . . . . . . . . . . . . 15 8. Informative References . . . . . . . . . . . . . . . . . . . 15
Appendix A. A Retrospective of IAB Charters and RFC Editor . . . 18 Appendix A. A Retrospective of IAB Charters and RFC Editor . . . 18
A.1. 1992 . . . . . . . . . . . . . . . . . . . . . . . . . . 18 A.1. 1992 . . . . . . . . . . . . . . . . . . . . . . . . . . 18
A.2. 1994 . . . . . . . . . . . . . . . . . . . . . . . . . . 18 A.2. 1994 . . . . . . . . . . . . . . . . . . . . . . . . . . 18
A.3. 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . 19 A.3. 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . 19
skipping to change at page 13, line 24 skipping to change at page 13, line 24
defined to provide review and (possible) approval of documents that defined to provide review and (possible) approval of documents that
are outside the scope of the streams identified above. are outside the scope of the streams identified above.
Generally speaking, approval of documents in this stream falls under Generally speaking, approval of documents in this stream falls under
the purview of the RFC Editor, and the RFC Editor seeks input to its the purview of the RFC Editor, and the RFC Editor seeks input to its
review from the IESG. review from the IESG.
The process for reviewing and approving documents in the Independent The process for reviewing and approving documents in the Independent
Submission stream is defined by Submission stream is defined by
o Procedures for Rights Handling in the RFC Independent Submission
Stream [RFC5744],
o Independent Submission Editor Model [I-D.ietf-iasa2-rfc6548bis],
o Independent Submissions to the RFC Editor [RFC4846], o Independent Submissions to the RFC Editor [RFC4846],
o The IESG and RFC Editor Documents: Procedures [RFC3932]. o The IESG and RFC Editor Documents: Procedures [RFC3932].
5.2. RFC Technical Publication Requirements 5.2. RFC Technical Publication Requirements
The Internet engineering and research community has not only grown, The Internet engineering and research community has not only grown,
it has become more diverse, and sometimes more demanding. The IETF, it has become more diverse, and sometimes more demanding. The IETF,
as a standards-developing organization, has publication requirements as a standards-developing organization, has publication requirements
that extend beyond those of an academic journal. The IAB does not that extend beyond those of an academic journal. The IAB does not
skipping to change at page 14, line 29 skipping to change at page 14, line 33
The IRTF has identified applicable requirements in [RFC5743] for its The IRTF has identified applicable requirements in [RFC5743] for its
stream. stream.
If the IRTF elects to define other requirements, they should deviate If the IRTF elects to define other requirements, they should deviate
minimally from those (in an effort to keep the collective technical minimally from those (in an effort to keep the collective technical
publication requirements reasonably managed by one technical publication requirements reasonably managed by one technical
publisher). publisher).
5.2.4. Independent Submissions 5.2.4. Independent Submissions
Procedures and processes for the Independent Stream are described in
[RFC4846] and [I-D.ietf-iasa2-rfc6548bis].
Although they were developed for the IETF standards process, the RFC Although they were developed for the IETF standards process, the RFC
Editor has identified applicable requirements in [RFC4714] for the Editor has identified applicable requirements in [RFC4714] for the
independent submissions stream. In addition, procedures related to independent submissions stream. In addition, procedures related to
IPR for the independent submissions stream are captured in [RFC5744]. IPR for the independent submissions stream are captured in [RFC5744].
If the RFC Editor elects to define other requirements, they should If the RFC Editor elects to define other requirements, they should
deviate minimally from those (in an effort to keep the collective deviate minimally from those (in an effort to keep the collective
technical publication requirements reasonably managed by one technical publication requirements reasonably managed by one
technical publisher). technical publisher).
skipping to change at page 15, line 25 skipping to change at page 15, line 29
Minor editorial changes were made to reflect 10 years of using the Minor editorial changes were made to reflect 10 years of using the
framework provided in RFC 4884. For example, RFC 4844 said, "... framework provided in RFC 4884. For example, RFC 4844 said, "...
this document sets out a revised framework ...", and it is now more this document sets out a revised framework ...", and it is now more
appropriate to say, "... this document sets out the framework ...". appropriate to say, "... this document sets out the framework ...".
8. Informative References 8. Informative References
[I-D.ietf-iasa2-rfc4071bis] [I-D.ietf-iasa2-rfc4071bis]
Haberman, B., Hall, J., and J. Livingood, "Structure of Haberman, B., Hall, J., and J. Livingood, "Structure of
the IETF Administrative Support Activity, Version 2.0", the IETF Administrative Support Activity, Version 2.0",
draft-ietf-iasa2-rfc4071bis-00 (work in progress), draft-ietf-iasa2-rfc4071bis-11 (work in progress), April
December 2018. 2019.
[I-D.ietf-iasa2-rfc6548bis]
Brownlee, N. and R. Hinden, "Independent Submission Editor
Model", draft-ietf-iasa2-rfc6548bis-02 (work in progress),
January 2019.
[RFC1358] Chapin, L., "Charter of the Internet Architecture Board [RFC1358] Chapin, L., "Charter of the Internet Architecture Board
(IAB)", RFC 1358, DOI 10.17487/RFC1358, August 1992, (IAB)", RFC 1358, DOI 10.17487/RFC1358, August 1992,
<https://www.rfc-editor.org/info/rfc1358>. <https://www.rfc-editor.org/info/rfc1358>.
[RFC1601] Huitema, C., "Charter of the Internet Architecture Board [RFC1601] Huitema, C., "Charter of the Internet Architecture Board
(IAB)", RFC 1601, DOI 10.17487/RFC1601, March 1994, (IAB)", RFC 1601, DOI 10.17487/RFC1601, March 1994,
<https://www.rfc-editor.org/info/rfc1601>. <https://www.rfc-editor.org/info/rfc1601>.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
 End of changes. 8 change blocks. 
7 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/