<?xmlversion="1.0" encoding="US-ASCII"?> <!-- automatically generated by xml2rfc v1.34pre3 on 2009-12-15T11:43:14Z --> <!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <?rfc strict="yes" ?> <?rfc toc="yes"?> <?rfc tocdepth="4"?> <?rfc symrefs="yes"?> <?rfc sortrefs="yes" ?> <?rfc compact="yes" ?> <?rfc subcompact="no" ?>version='1.0' encoding='utf-8'?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" consensus="true" docName="draft-ietf-iasa2-rfc6548bis-02"obsoletes="6548">indexInclude="true" ipr="trust200902" number="8730" obsoletes="6548" prepTime="2020-02-26T18:09:44" scripts="Common,Latin" sortRefs="true" submissionType="IAB" symRefs="true" tocDepth="4" tocInclude="true" xml:lang="en"> <link href="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6548bis-02" rel="prev"/> <link href="https://dx.doi.org/10.17487/rfc8730" rel="alternate"/> <link href="urn:issn:2070-1721" rel="alternate"/> <front><title>Independent<title abbrev="Independent Submission Editor Model">Independent Submission Editor Model</title> <seriesInfo name="RFC" value="8730" stream="IAB"/> <author initials="N." surname="Brownlee" fullname="Nevil Brownlee" role="editor"><organization>The<organization showOnFrontPage="true">The University of Auckland</organization><address><email>n.brownlee@auckland.ac.nz</email></address> </author> <!-- <author surname="IAB" fullname="Internet Architecture Board"> <organization></organization> <address><email>iab@iab.org</email><address> <email>n.brownlee@auckland.ac.nz</email> </address> </author>--><author fullname="Robert M. Hinden" initials="R" surname="Hinden" role="editor"><organization>Check<organization showOnFrontPage="true">Check Point Software</organization> <address> <postal> <street>959 Skyway Road</street><!-- Reorder these if your country does things differently --><city>San Carlos</city> <region>CA</region> <code>94070</code> <country>USA</country> </postal><phone></phone> <facsimile></facsimile><email>bob.hinden@gmail.com</email><!-- uri and facsimile elements may also be added --></address> </author> <datemonth="" year="" /> <keyword>RFC</keyword> <abstract> <t>month="02" year="2020"/> <keyword>ISE</keyword> <keyword>IASA</keyword> <keyword>RSE</keyword> <keyword>LLC</keyword> <keyword>IAB</keyword> <abstract pn="section-abstract"> <t pn="section-abstract-1"> This document describes the function and responsibilities of the RFC Independent Submission Editor (ISE). The Independent Submission stream is one of the stream producers that create draft RFCs, with the ISE as its stream approver. The ISE is overall responsible for activities within the Independent Submission stream, working with draft editors and reviewers, and interacts with the RFC Production Center and Publisher, and the RFC Series Editor (RSE). The ISE is appointed by the IAB, and also interacts with the IETF Administration Limited Liability Company (LLC).</t><t>This<t pn="section-abstract-2">This version obsoletes RFC 6548 to replace all references to theIASAInternet Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0Model.</t> <t>[RFC Editor: Please removestructure.</t> </abstract> <boilerplate> <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1"> <name slugifiedName="name-status-of-this-memo">Status of This Memo</name> <t pn="section-boilerplate.1-1"> This document is not an Internet Standards Track specification; it is published for informational purposes. </t> <t pn="section-boilerplate.1-2"> This document is a product of thefollowing paragraph prior to publication.]</t> <t>The IASA2 WG requestsInternet Architecture Board (IAB) and represents information that the IABpublish this replacementhas deemed valuable to provide forRFC 6548.</t> </abstract> </front> <middle> <section title="Introduction"> <t> <!-- The Independent Submissions Editor roles and responsibilities were documented in "RFC Editor Model (version 1)" <xref target="RFC5620"/>. Inpermanent record. It represents the consensus of thelightInternet Architecture Board (IAB). Documents approved for publication by the IAB are not candidates for any level ofexperience, weInternet Standard; seethat having it there gave riseSection 2 of RFC 7841. </t> <t pn="section-boilerplate.1-3"> Information about the current status of this document, any errata, and how tosome confusionprovide feedback on it may be obtained at <eref target="https://www.rfc-editor.org/info/rfc8730" brackets="none"/>. </t> </section> <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2"> <name slugifiedName="name-copyright-notice">Copyright Notice</name> <t pn="section-boilerplate.2-1"> Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. </t> <t pn="section-boilerplate.2-2"> This document is subject towhereBCP 78 andhow the ISE fits intotheRFC Editor model. To reduce that confusion,IETF Trust's Legal Provisions Relating to IETF Documents (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on theISE material has been moved intodate of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.--></t> </section> </boilerplate> <toc> <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1"> <name slugifiedName="name-table-of-contents">Table of Contents</name> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1"> <li pn="section-toc.1-1.1"> <t keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t> </li> <li pn="section-toc.1-1.2"> <t keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-independent-submission-edit">Independent Submission Editor</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2"> <li pn="section-toc.1-1.2.2.1"> <t keepWithNext="true" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-qualifications">Qualifications</xref></t> </li> <li pn="section-toc.1-1.2.2.2"> <t keepWithNext="true" pn="section-toc.1-1.2.2.2.1"><xref derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-responsibilities">Responsibilities</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.3"> <t keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-independent-submission-edito">Independent Submission Editorial Board</xref></t> </li> <li pn="section-toc.1-1.4"> <t keepWithNext="true" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t> </li> <li pn="section-toc.1-1.5"> <t keepWithNext="true" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2"> <li pn="section-toc.1-1.5.2.1"> <t keepWithNext="true" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t> </li> <li pn="section-toc.1-1.5.2.2"> <t keepWithNext="true" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.6"> <t keepWithNext="true" pn="section-toc.1-1.6.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-iab-members-at-the-time-of-">IAB Members at the Time of Approval</xref></t> </li> <li pn="section-toc.1-1.7"> <t keepWithNext="true" pn="section-toc.1-1.7.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t> </li> <li pn="section-toc.1-1.8"> <t keepWithNext="true" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t> </li> </ul> </section> </toc> </front> <middle> <section numbered="true" toc="include" removeInRFC="false" pn="section-1"> <name slugifiedName="name-introduction">Introduction</name> <t pn="section-1-1"> The RFC Editor Model <xreftarget="I-D.ietf-iasa2-rfc6635bis"/>target="RFC8728" format="default" sectionFormat="of" derivedContent="RFC8728"/> defines a set of streams that produce draft RFCs, which are submitted for publication. This document defines the management function for the Independent Submission stream, specifically the role of Independent Submission Editor (ISE).</t><t><t pn="section-1-2"> The previous version of this document <xref target="RFC6548" format="default" sectionFormat="of" derivedContent="RFC6548"/> is a derivative of <xreftarget="RFC5620"/>, Section 3.2,target="RFC5620" section="3.2" sectionFormat="comma" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5620#section-3.2" derivedContent="RFC5620"/>, and was separated out from <xreftarget="RFC6635"/>.</t> <t>target="RFC6635" format="default" sectionFormat="of" derivedContent="RFC6635"/>.</t> <t pn="section-1-3"> This document updates the Independent Submission Editor Model tobe alignedalign it with the IASA 2.0Modelstructure <xreftarget="I-D.ietf-iasa2-rfc4071bis"/>target="RFC8711" format="default" sectionFormat="of" derivedContent="RFC8711"/> that createsathe IETF Administration Limited Liability Company ("LLC") managed by a board of directors ("LLC Board"). This document obsoletes <xreftarget="RFC6548"/>.target="RFC6548" format="default" sectionFormat="of" derivedContent="RFC6548"/>. </t> </section> <sectiontitle="Independentnumbered="true" toc="include" removeInRFC="false" pn="section-2"> <name slugifiedName="name-independent-submission-edit">Independent SubmissionEditor"> <t>Editor</name> <t pn="section-2-1"> The ISE is an individual who is responsible for the Independent Submission stream of RFCs, as defined by <xreftarget="RFC4844"/>. <!-- The accountability of all RFC Streams Editors is to the body that appoints them -->target="RFC8729" format="default" sectionFormat="of" derivedContent="RFC8729"/>. The Independent Submission stream and the ISE are not under the authority or direction of the RSE or the RFC Series Oversight Committee (RSOC) (see <xreftarget="I-D.ietf-iasa2-rfc6635bis"/>).target="RFC8728" format="default" sectionFormat="of" derivedContent="RFC8728"/>). As noted below, the ISE is appointed by and is responsible directly to the IAB. </t> <sectiontitle="Qualifications"> <t>numbered="true" toc="include" removeInRFC="false" pn="section-2.1"> <name slugifiedName="name-qualifications">Qualifications</name> <t pn="section-2.1-1"> The ISE is a senior position for which the following qualifications are desired:<list style="numbers"> <t>Technical</t> <ol spacing="normal" type="1" start="1" pn="section-2.1-2"> <li pn="section-2.1-2.1" derivedCounter="1.">Technical competence, i.e., broad technical experience and perspective across a wide range of Internet technologies and applications, and also the ability to work effectively with portions of that spectrum in which they have no personalexpertise.</t> <t>Thoroughexpertise.</li> <li pn="section-2.1-2.2" derivedCounter="2.">Thorough familiarity with the RFCseries.</t> <t>Anseries.</li> <li pn="section-2.1-2.3" derivedCounter="3.">An ability to define and constitute advisory and document review arrangements. If those arrangements include an Editorial Board similar to the current one or some equivalent arrangement, the ability to assess the technical competence of potential Editorial Board members (see <xref target="editorial_board"/>).</t> <t>Goodformat="default" sectionFormat="of" derivedContent="Section 3"/>).</li> <li pn="section-2.1-2.4" derivedCounter="4.">Good standing in the technical community, in and beyond theIETF.</t> <t>IETF.</li> <li pn="section-2.1-2.5" derivedCounter="5."> Demonstrated editorial skills, good command of the English language, and demonstrated history of being able to work effectively with technical documents and materials created byothers.</t> <t>Theothers.</li> <li pn="section-2.1-2.6" derivedCounter="6.">The ability to work effectively in a multi-actor environment with divided authority and responsibility similar to that described in <xreftarget="RFC6635"/>. </t> </list> </t>target="RFC6635" format="default" sectionFormat="of" derivedContent="RFC6635"/>. </li> </ol> </section> <sectiontitle="Responsibilities" anchor="Resp"> <t>anchor="Resp" numbered="true" toc="include" removeInRFC="false" pn="section-2.2"> <name slugifiedName="name-responsibilities">Responsibilities</name> <t pn="section-2.2-1"> The ISE is an individual who may have assistants and who is responsible for: </t><t> <list style="numbers"> <t>Maintaining<ol spacing="normal" type="1" start="1" pn="section-2.2-2"> <li pn="section-2.2-2.1" derivedCounter="1.">Maintaining technical quality of the Independent Submissionstream.</t> <t>Reviewing,stream.</li> <li pn="section-2.2-2.2" derivedCounter="2.">Reviewing, approving, and processing IndependentSubmissions.</t> <t>ForwardingSubmissions.</li> <li pn="section-2.2-2.3" derivedCounter="3.">Forwarding draft RFCs in the Independent Submission stream to the RFC ProductionCenter.</t> <t>DefiningCenter.</li> <li pn="section-2.2-2.4" derivedCounter="4.">Defining and developing the scope of the Independent Submission stream as a part of the overall RFC Editor function <xreftarget="RFC6635"/>.</t> <t>Reviewingtarget="RFC6635" format="default" sectionFormat="of" derivedContent="RFC6635"/>.</li> <li pn="section-2.2-2.5" derivedCounter="5.">Reviewing and approving RFC errata for IndependentSubmissions.</t> <t>CoordinatingSubmissions.</li> <li pn="section-2.2-2.6" derivedCounter="6.">Coordinating work and conforming to general RFC Series policies as specified by the IAB andRSE.</t> <t>RSE.</li> <li pn="section-2.2-2.7" derivedCounter="7."> Providing statistics and documentation as requested by the RSE and/orLLC.</t> </list> </t> <t>LLC.</li> </ol> <t pn="section-2.2-3"> The ISE may choose to select individuals to participate in an Advisory Board for assistance in special topics as the ISE deems appropriate. Such an Advisory Board exists at the pleasure of the ISE, and its members serve at the pleasure of the ISE.<!-- The Independent Submission Editor may create and seek support from an advisory board (see <xref target="RFC4846"/>). Such a board would provide advice to the ISE on any aspect of the Independent Stream and its activities. --> </t><t></t> <t pn="section-2.2-4"> The individual with the listed qualifications is selected by the IAB after input has been collected from the community. </t><!-- An approach similar to the one used by the IAB to select an IAOC member every other year as described in <xref target="RFC4333"/> should be used. <t><list> <t>Editors Note: RFC6548 said "An approach similar to the one used by the IAB to select an IAOC member every other year as described in [RFC4333] should be used". This isn't appropriate for the BIS, suggest removing it all together. Is there better text to include?</t> </list></t> --> <t><t pn="section-2.2-5"> While the ISE itself is considered a volunteer function, the IAB considers maintaining the Independent Submission stream part of the IAB's supported activities. Therefore, the LLC should include these costs in the IASA budget. </t> </section> </section> <sectiontitle="Independentanchor="editorial_board" numbered="true" toc="include" removeInRFC="false" pn="section-3"> <name slugifiedName="name-independent-submission-edito">Independent Submission EditorialBoard" anchor="editorial_board"> <t>Board</name> <t pn="section-3-1"> The ISE is supported by an Editorial Board for the review of Independent Submission stream documents. This board is known as the Independent Submission Editorial Board. This volunteer Editorial Board exists at the pleasure of the ISE, and its members serve at the pleasure of the ISE. The existence of this board is simply noted within this model, and additional discussion of such is considered out of scope of this document. </t> </section> <sectiontitle="Security Considerations"> <t>numbered="true" toc="include" removeInRFC="false" pn="section-4"> <name slugifiedName="name-security-considerations">Security Considerations</name> <t pn="section-4-1"> This document has no specific security implications, however the same security considerations as those in <xreftarget="RFC4846"/>target="RFC4846" format="default" sectionFormat="of" derivedContent="RFC4846"/> and <xreftarget="RFC4844"/>target="RFC8729" format="default" sectionFormat="of" derivedContent="RFC8729"/> apply. </t> </section><section title="IAB Members</middle> <back> <references pn="section-5"> <name slugifiedName="name-references">References</name> <references pn="section-5.1"> <name slugifiedName="name-normative-references">Normative References</name> <reference anchor="RFC4846" target="https://www.rfc-editor.org/info/rfc4846" quoteTitle="true" derivedAnchor="RFC4846"> <front> <title>Independent Submissions to the RFC Editor</title> <author initials="J." surname="Klensin" fullname="J. Klensin" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="D." surname="Thaler" fullname="D. Thaler" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2007" month="July"/> <abstract> <t>There is a long-standing tradition in the Internet community, predating the Internet Engineering Task Force (IETF) by many years, of use of the RFC Series to publish materials that are not rooted in the IETF standards process and its review and approval mechanisms. These documents, known as "Independent Submissions", serve a number of important functions for the Internet community, both inside and outside of the community of active IETF participants. This document discusses the Independent Submission model and some reasons why it is important. It then describes editorial and processing norms that can be used for Independent Submissions as the community goes forward into new relationships between the IETF community and its primary technical publisher. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4846"/> <seriesInfo name="DOI" value="10.17487/RFC4846"/> </reference> <reference anchor="RFC6548" target="https://www.rfc-editor.org/info/rfc6548" quoteTitle="true" derivedAnchor="RFC6548"> <front> <title>Independent Submission Editor Model</title> <author initials="N." surname="Brownlee" fullname="N. Brownlee" role="editor"> <organization showOnFrontPage="true"/> </author> <author> <organization showOnFrontPage="true">IAB</organization> </author> <date year="2012" month="June"/> <abstract> <t>This document describes the function and responsibilities of the RFC Independent Submission Editor (ISE). The Independent Submission stream is one of the stream producers that create draft RFCs, with the ISE as its stream approver. The ISE is overall responsible for activities within the Independent Submission stream, working with draft editors and reviewers, and interacts with the RFC Production Center and Publisher, and the RFC Series Editor (RSE). The ISE is appointed by the IAB, and also interacts with the IETF Administrative Oversight Committee (IAOC). This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="6548"/> <seriesInfo name="DOI" value="10.17487/RFC6548"/> </reference> <reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8711" quoteTitle="true" derivedAnchor="RFC8711"> <front> <title>Structure of the IETF Administrative Support Activity, Version 2.0</title> <author initials="B." surname="Haberman"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Hall"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Livingood"> <organization showOnFrontPage="true"/> </author> <date year="2020" month="February"/> </front> <seriesInfo name="BCP" value="101"/> <seriesInfo name="RFC" value="8711"/> <seriesInfo name="DOI" value="10.17487/RFC8711"/> </reference> <reference anchor="RFC8728" target="https://www.rfc-editor.org/info/rfc8728" quoteTitle="true" derivedAnchor="RFC8728"> <front> <title>RFC Editor Model (Version 2)</title> <author initials="O" surname="Kolkman" fullname="Olaf Kolkman" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="J" surname="Halpern" fullname="Joel Halpern" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="R" surname="Hinden" fullname="Robert Hinden" role="editor"> <organization showOnFrontPage="true"/> </author> <date month="February" year="2020"/> </front> <seriesInfo name="RFC" value="8728"/> <seriesInfo name="DOI" value="10.17487/RFC8728"/> </reference> <reference anchor="RFC8729" target="https://www.rfc-editor.org/info/rfc8729" quoteTitle="true" derivedAnchor="RFC8729"> <front> <title>The RFC Series and RFC Editor</title> <author initials="R." surname="Housley" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="L." surname="Daigle" role="editor"> <organization showOnFrontPage="true"/> </author> <date month="February" year="2020"/> </front> <seriesInfo name="RFC" value="8729"/> <seriesInfo name="DOI" value="10.17487/RFC8729"/> </reference> </references> <references pn="section-5.2"> <name slugifiedName="name-informative-references">Informative References</name> <reference anchor="RFC5620" target="https://www.rfc-editor.org/info/rfc5620" quoteTitle="true" derivedAnchor="RFC5620"> <front> <title>RFC Editor Model (Version 1)</title> <author initials="O." surname="Kolkman" fullname="O. Kolkman" role="editor"> <organization showOnFrontPage="true"/> </author> <author> <organization showOnFrontPage="true">IAB</organization> </author> <date year="2009" month="August"/> <abstract> <t>The RFC Editor performs a number of functions that may be carried out by various persons or entities. The RFC Editor model presented in this document divides the responsibilities for the RFC Series into four functions: The RFC Series Editor, the Independent Submission Editor, the RFC Production Center, and the RFC Publisher. It also introduces the RFC Series Advisory Group and an (optional) Independent Submission Stream Editorial Board. The model outlined here is intended to increase flexibility and operational support options, provide for the orderly succession of the RFC Editor, and ensure the continuity of the RFC series, while maintaining RFC quality and timely processing, ensuring document accessibility, reducing costs, and increasing cost transparency. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="5620"/> <seriesInfo name="DOI" value="10.17487/RFC5620"/> </reference> <reference anchor="RFC6635" target="https://www.rfc-editor.org/info/rfc6635" quoteTitle="true" derivedAnchor="RFC6635"> <front> <title>RFC Editor Model (Version 2)</title> <author initials="O." surname="Kolkman" fullname="O. Kolkman" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Halpern" fullname="J. Halpern" role="editor"> <organization showOnFrontPage="true"/> </author> <author> <organization showOnFrontPage="true">IAB</organization> </author> <date year="2012" month="June"/> <abstract> <t>The RFC Editor model described in this document divides the responsibilities for the RFC Series into three functions: the RFC Series Editor, the RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described, as is the relationship between the IETF Administrative Oversight Committee (IAOC) and the RSOC. This document reflects the experience gained with "RFC Editor Model (Version 1)", documented in RFC 5620, and obsoletes that document. This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="6635"/> <seriesInfo name="DOI" value="10.17487/RFC6635"/> </reference> </references> </references> <section numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a"> <name slugifiedName="name-iab-members-at-the-time-of-">IAB Members at the Time ofApproval"> <t>Approval</name> <t pn="section-appendix.a-1"> The IAB members at the time of approval of <xreftarget="RFC6548"/>target="RFC6548" format="default" sectionFormat="of" derivedContent="RFC6548"/> were:Bernard Aboba, Ross Callon, Alissa Cooper, Joel Halpern, Spencer Dawkins, Russ Housley, David Kessens, Olaf Kolkman, Danny McPherson, Jon Peterson, Andrei Robachevsky, Dave Thaler, and Hannes Tschofenig.<contact fullname="Bernard Aboba"/>, <contact fullname="Ross Callon"/>, <contact fullname="Alissa Cooper"/>, <contact fullname="Joel Halpern"/>, <contact fullname="Spencer Dawkins"/>, <contact fullname="Russ Housley"/>, <contact fullname="David Kessens"/>, <contact fullname="Olaf Kolkman"/>, <contact fullname="Danny McPherson"/>, <contact fullname="Jon Peterson"/>, <contact fullname="Andrei Robachevsky"/>, <contact fullname="Dave Thaler"/>, and <contact fullname="Hannes Tschofenig"/>. </t><t>The<t pn="section-appendix.a-2">The IAB members at the time of approval of this document (RFC 8730) were:Jari Arrko, Alissa Cooper, Ted Hardie, Christian Heuitema, Gabriel Montenegro, Erik Nordmark, Mark Nottingham, Melina Shore, Robert Sparks, Jeff Tantsura, Martin Thomson, Brian Trammell, and Suzanne Woolf.<contact fullname="Jari Arkko"/>, <contact fullname="Alissa Cooper"/>, <contact fullname="Stephen Farrell"/>, <contact fullname="Wes Hardaker"/>, <contact fullname="Ted Hardie"/>, <contact fullname="Christian Huitema"/>, <contact fullname="Zhenbin Li"/>, <contact fullname="Erik Nordmark"/>, <contact fullname="Mark Nottingham"/>, <contact fullname="Melinda Shore"/>, <contact fullname="Jeff Tantsura"/>, <contact fullname="Martin Thomson"/>, and <contact fullname="Brian Trammell"/>. </t> </section> <sectiontitle="Acknowledgements"> <t>numbered="false" toc="include" removeInRFC="false" pn="section-appendix.b"> <name slugifiedName="name-acknowledgements">Acknowledgements</name> <t pn="section-appendix.b-1"> Generous thanks toJoel Hapern<contact fullname="Joel Halpern"/> for all his help with this document, and for all his work on <xreftarget="RFC6635"/>).target="RFC6635" format="default" sectionFormat="of" derivedContent="RFC6635"/>. Thanks also to the IAB members, whose comments and suggestions were both welcome and useful. </t><t>Bob Hinden<t pn="section-appendix.b-2"><contact fullname="Bob Hinden"/> served asdocumenteddocument editor for thisversion of this document that alignedRFC to align it with the IASA 2.0model.</t>structure.</t> </section></middle> <back> <references title='Normative References'> <?rfc include="reference.RFC.4846"?> <!-- Independent Submissions --> <?rfc include="reference.RFC.4844"?> <?rfc include="reference.I-D.ietf-iasa2-rfc4071bis.xml"?> <?rfc include="reference.I-D.ietf-iasa2-rfc6635bis.xml"?> <?rfc include="reference.RFC.6548"?> </references> <references title='Informative References'> <!-- <?rfc include="reference.RFC.4333"?> --> <?rfc include="reference.RFC.5620"?> <!-- RFC ED Model (v1) --> <?rfc include="reference.RFC.6635"?> <!-- RFC ED Model (v2) --> </references><sectionanchor="changes" title="Change log [RFC Editor: Please remove]"> <t><list> <?rfc subcompact="no" ?> <t>draft-ietf-iasa2-rfc6548bis-02, 2019-January-7</t> <?rfc subcompact="yes" ?> <t><list style="symbols"> <t>Changed references to point to current IASA 2.0 structure document <xref target="I-D.ietf-iasa2-rfc4071bis"/></t> <t>Added text to Abstract that this document obsoletes RFC 6548.</t> <t>Removed IAB as an author to follow current model for IAB stream documents.</t> <t>Added note to Abstract (to be removed by the RFC Editor) requesting that the IAB publish this document as a replacement for RFC 6548. </t> <t>Editorial changes.</t> </list></t> <?rfc subcompact="no" ?> <?rfc subcompact="no" ?> <t>draft-ietf-iasa2-rfc6548bis-01, 2018-September-11</t> <?rfc subcompact="yes" ?> <t><list style="symbols"> <t>Added paragraph to introduction about purpose of this version of the document, and updated history. Similar changes to the Abstract.</t> <t>Changed occurrences of IETF Administrative Oversight Committee (IAOC) to IETF Administration Limited Liability Company (LLC).</t> <t>Changed occurrences of IAOC to LLC.</t> <t>Added new editor to acknowledgement section.</t> <t>Changed document to obsolete RFC6548.</t> <t>Removed text from <xref target="Resp"/> "An approach similar to the one used by the IAB to select an IAOC member every other year as described in [RFC4333] should be used" because it was no longer appropriate.</t> <t>Added nameanchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c"> <name slugifiedName="name-authors-addresses">Authors' Addresses</name> <author initials="N." surname="Brownlee" fullname="Nevil Brownlee" role="editor"> <organization showOnFrontPage="true">The University ofIAB members at the time this document was approved.</t> <t>Editorial changes.</t> </list></t> <?rfc subcompact="no" ?> <t>draft-ietf-iasa2-rfc6548bis-00, 2018-September-11</t> <?rfc subcompact="no" ?> <?rfc subcompact="yes" ?> <t><list style="symbols"> <t>Original version with only changes from RFC6635 were to convert to ID format and adding new editor to allow submission.</t> </list></t> </list></t> <?rfc subcompact="no" ?>Auckland</organization> <address> <email>n.brownlee@auckland.ac.nz</email> </address> </author> <author fullname="Robert M. Hinden" initials="R" surname="Hinden" role="editor"> <organization showOnFrontPage="true">Check Point Software</organization> <address> <postal> <street>959 Skyway Road</street> <city>San Carlos</city> <region>CA</region> <code>94070</code> <country>USA</country> </postal> <email>bob.hinden@gmail.com</email> </address> </author> </section> </back> </rfc>