draft-ietf-iasa2-rfc6635bis-01.txt   draft-ietf-iasa2-rfc6635bis-02.txt 
Network Working Group O. Kolkman, Ed. Network Working Group O. Kolkman, Ed.
Internet-Draft Internet-Draft
Obsoletes: 6635 (if approved) J. Halpern, Ed. Obsoletes: 6635 (if approved) J. Halpern, Ed.
Intended status: Informational Ericsson Intended status: Informational Ericsson
Expires: February 25, 2019 IAB Expires: July 7, 2019 IAB
R. Hinden, Ed. R. Hinden, Ed.
Check Point Software Check Point Software
August 24, 2018 January 3, 2019
RFC Editor Model (Version 2) RFC Editor Model (Version 2)
draft-ietf-iasa2-rfc6635bis-01 draft-ietf-iasa2-rfc6635bis-02
Abstract Abstract
The RFC Editor model described in this document divides the The RFC Editor model described in this document divides the
responsibilities for the RFC Series into three functions: the RFC responsibilities for the RFC Series into three functions: the RFC
Series Editor, the RFC Production Center, and the RFC Publisher. Series Editor, the RFC Production Center, and the RFC Publisher.
Internet Architecture Board (IAB) oversight via the RFC Series Internet Architecture Board (IAB) oversight via the RFC Series
Oversight Committee (RSOC) is described, as is the relationship Oversight Committee (RSOC) is described, as is the relationship
between the IETF Administration Limited Liability Company and the between the IETF Administration Limited Liability Company and the
RSOC. This document reflects the experience gained with "RFC Editor RSOC. This document reflects the experience gained with "RFC Editor
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 February 25, 2019. This Internet-Draft will expire on July 7, 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 12 skipping to change at page 3, line 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1. Normative References . . . . . . . . . . . . . . . . . . 21 9.1. Normative References . . . . . . . . . . . . . . . . . . 21
9.2. Informative References . . . . . . . . . . . . . . . . . 22 9.2. Informative References . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
This document reflects the experience gained with "RFC Editor Model This document reflects the experience gained with "RFC Editor Model
(Version 1)", documented in [RFC5620], and updates the RFC Editor (Version 1)", documented in [RFC5620], and updates the RFC Editor
Model (Version 2) to be aligned with the new IASA 2.0 Model Model (Version 2) to be aligned with the new IASA 2.0 Model
[I-D.ietf-iasa2-struct] that creates a IETF Administration Limited [I-D.ietf-iasa2-rfc4071bis] that creates a IETF Administration
Liability Company ("LLC") managed by a board of directors ("LLC Limited Liability Company ("LLC") managed by a board of directors
Board"). As part of the IASA 2.0 Model the Internet Administrative ("LLC Board"). As part of the IASA 2.0 Model the Internet
Oversight Committee (IAOC) is eliminated, and its oversight and Administrative Oversight Committee (IAOC) is eliminated, and its
advising functions transferred to the new LLC. This document oversight and advising functions transferred to the new LLC. This
obsoletes [RFC6635] to replace all references to the IASA and related document obsoletes [RFC6635] to replace all references to the IASA
structures with those defined by the IASA 2.0 Model. and related structures with those defined by the IASA 2.0 Model.
The IAB, on behalf of the Internet technical community, is concerned The IAB, on behalf of the Internet technical community, is concerned
with ensuring the continuity of the RFC Series, orderly RFC Editor with ensuring the continuity of the RFC Series, orderly RFC Editor
succession, RFC quality, and RFC document accessibility. The IAB is succession, RFC quality, and RFC document accessibility. The IAB is
also sensitive to the concerns of the LLC about providing the also sensitive to the concerns of the LLC about providing the
necessary services in a cost-effective and efficient manner. necessary services in a cost-effective and efficient manner.
The contemporary RFC Editor model [RFC5620] was first approved in The contemporary RFC Editor model [RFC5620] was first approved in
October 2008, and our understanding of the model has evolved with our October 2008, and our understanding of the model has evolved with our
experience since. During the implementation of version 1 of the experience since. During the implementation of version 1 of the
skipping to change at page 15, line 45 skipping to change at page 15, line 45
The LLC will appoint an individual to serve as its liaison to the The LLC will appoint an individual to serve as its liaison to the
RSOC. The RSE and the LLC Liaison will serve as non-voting ex RSOC. The RSE and the LLC Liaison will serve as non-voting ex
officio members of the RSOC. Either or both can be excluded from its officio members of the RSOC. Either or both can be excluded from its
discussions if necessary. discussions if necessary.
4. Administrative Implementation 4. Administrative Implementation
The exact implementation of the administrative and contractual The exact implementation of the administrative and contractual
activities described here are a responsibility of the IETF activities described here are a responsibility of the IETF
Administration Limited Liability Company [I-D.ietf-iasa2-struct] in Administration Limited Liability Company [I-D.ietf-iasa2-rfc4071bis]
cooperation with the RFC Series Editor. The authority structure is in cooperation with the RFC Series Editor. The authority structure
described in Figure 2 below. is described in Figure 2 below.
+----------------+ +----------------+ +----------------+ +----------------+
| | | | | | | |
| IAB | | LLC | | IAB | | LLC |
| | | | | | | |
+==========+-----+ +-+--------------+ +==========+-----+ +-+--------------+
| | . | | .
| RSOC | . | RSOC | .
| | . | | .
+----+-----+ . +----+-----+ .
skipping to change at page 17, line 35 skipping to change at page 17, line 35
o The Selection Committee may select an RFC Publisher either through o The Selection Committee may select an RFC Publisher either through
the LLC RFP process or, at the Committee's option, the Committee the LLC RFP process or, at the Committee's option, the Committee
may select the IETF Secretariat to provide RFC Publisher services, may select the IETF Secretariat to provide RFC Publisher services,
subject to negotiations in accordance with the LLC procedures. subject to negotiations in accordance with the LLC procedures.
4.2. Budget 4.2. Budget
The expenses discussed in this document are not new expenses. They The expenses discussed in this document are not new expenses. They
have been and remain part of the IETF Administration Limited have been and remain part of the IETF Administration Limited
Liability Company [I-D.ietf-iasa2-struct] budget. Liability Company [I-D.ietf-iasa2-rfc4071bis] budget.
The RFC Series portion of the LLC budget shall include entries for The RFC Series portion of the LLC budget shall include entries for
the RSOC, RSE, RFC Production Center, and the RFC Publisher. The LLC the RSOC, RSE, RFC Production Center, and the RFC Publisher. The LLC
budget shall also include entries for the streams, including the budget shall also include entries for the streams, including the
independent stream. independent stream.
The LLC has the responsibility to approve the total RFC Editor budget The LLC has the responsibility to approve the total RFC Editor budget
(and the authority to deny it). The RSE must work within the LLC (and the authority to deny it). The RSE must work within the LLC
budgetary process. budgetary process.
skipping to change at page 19, line 19 skipping to change at page 19, line 19
formal resolution by the RSOC with confirmation by the IAB in its formal resolution by the RSOC with confirmation by the IAB in its
oversight capacity. oversight capacity.
IAB and community discussion of any patterns of disputes are expected IAB and community discussion of any patterns of disputes are expected
to inform future changes to RFC Series policies, including possible to inform future changes to RFC Series policies, including possible
updates to this document. updates to this document.
4.4. Issues with Contractual Impact 4.4. Issues with Contractual Impact
If a disagreement or decision has immediate or future contractual If a disagreement or decision has immediate or future contractual
consequences, it falls under [I-D.ietf-iasa2-struct]; thus, the RSE consequences, it falls under [I-D.ietf-iasa2-rfc4071bis]; thus, the
must identify the issue and provide his or her advice to the LLC; RSE must identify the issue and provide his or her advice to the LLC;
additionally, if the RSOC has provided advice, forward that advice as additionally, if the RSOC has provided advice, forward that advice as
well. The LLC must notify the RSOC and IAB regarding the action it well. The LLC must notify the RSOC and IAB regarding the action it
concludes is required to resolve the issue based on its applicable concludes is required to resolve the issue based on its applicable
procedures and provisions in the relevant contracts. procedures and provisions in the relevant contracts.
5. IANA Considerations 5. IANA Considerations
This document defines several functions within the overall RFC Editor This document defines several functions within the overall RFC Editor
structure, and it places the responsibility for coordination of structure, and it places the responsibility for coordination of
registry value assignments with the RFC Production Center. The LLC registry value assignments with the RFC Production Center. The LLC
skipping to change at page 20, line 44 skipping to change at page 20, line 44
Thaler, and Hannes Tschofenig. In addition, at the time of approval, Thaler, and Hannes Tschofenig. In addition, at the time of approval,
the IAB included two ex officio members: Mary Barnes who was serving the IAB included two ex officio members: Mary Barnes who was serving
as the IAB Executive Director, and Lars Eggert, who was serving as as the IAB Executive Director, and Lars Eggert, who was serving as
the IRTF Chair. the IRTF Chair.
Bob Hinden served as documented editor for this version of this Bob Hinden served as documented editor for this version of this
document that aligned it with the IASA 2.0 model. document that aligned it with the IASA 2.0 model.
8. Change log [RFC Editor: Please remove] 8. Change log [RFC Editor: Please remove]
draft-ietf-iasa2-rfc6635bis-01, 2018-August-23 draft-ietf-iasa2-rfc6635bis-02, 2019-January-3
* Changed references to point to current IASA 2.0 structure
document [I-D.ietf-iasa2-rfc4071bis]
draft-ietf-iasa2-rfc6635bis-01, 2018-August-23
* Changed to Obsolete RFC6635 from Update. * Changed to Obsolete RFC6635 from Update.
* Changed remaining occurrences of Board. * Changed remaining occurrences of Board.
* Changed IETF Administration Limited Liability Corporation to * Changed IETF Administration Limited Liability Corporation to
IETF Administration Limited Liability Company. IETF Administration Limited Liability Company.
* Editorial Changes. * Editorial Changes.
draft-ietf-iasa2-rfc6635bis-00, 2018-August-22 draft-ietf-iasa2-rfc6635bis-00, 2018-August-22
* Working Group draft. * Working Group draft.
* Removed remaining references to RFC4071. * Removed remaining references to RFC4071.
skipping to change at page 21, line 32 skipping to change at page 21, line 37
draft-hinden-iasa2-rfc6635bis-00, 2018-August-6 draft-hinden-iasa2-rfc6635bis-00, 2018-August-6
* Original version with only changes from RFC6635 were to convert * Original version with only changes from RFC6635 were to convert
to ID format. to ID format.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-iasa2-struct] [I-D.ietf-iasa2-rfc4071bis]
Haberman, B., Hall, J., and J. Livingood, "Proposed Haberman, B., Hall, J., and J. Livingood, "Structure of
Structure of the IETF Administrative Support Activity the IETF Administrative Support Activity, Version 2.0",
(IASA), Version 2.0", draft-ietf-iasa2-struct-05 (work in draft-ietf-iasa2-rfc4071bis-03 (work in progress),
progress), August 2018. December 2018.
[RFC2850] Internet Architecture Board and B. Carpenter, Ed., [RFC2850] Internet Architecture Board and B. Carpenter, Ed.,
"Charter of the Internet Architecture Board (IAB)", BCP "Charter of the Internet Architecture Board (IAB)", BCP
39, RFC 2850, DOI 10.17487/RFC2850, May 2000, 39, RFC 2850, DOI 10.17487/RFC2850, May 2000,
<https://www.rfc-editor.org/info/rfc2850>. <https://www.rfc-editor.org/info/rfc2850>.
[RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC [RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC
Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844,
July 2007, <https://www.rfc-editor.org/info/rfc4844>. July 2007, <https://www.rfc-editor.org/info/rfc4844>.
 End of changes. 12 change blocks. 
24 lines changed or deleted 28 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/