rfc8730xml2.original.xml		rfc8730.xml
	<?xml version="1.0" encoding="US-ASCII"?>		<?xml version='1.0' encoding='utf-8'?>
	<!-- automatically generated by xml2rfc v1.34pre3 on 2009-12-15T11:43:14Z -->		<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" cons
	<!DOCTYPE rfc SYSTEM "rfc2629.dtd">		ensus="true" docName="draft-ietf-iasa2-rfc6548bis-02" indexInclude="true" ipr="t
			rust200902" number="8730" obsoletes="6548" prepTime="2020-02-26T18:09:44" script
	<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>		s="Common,Latin" sortRefs="true" submissionType="IAB" symRefs="true" tocDepth="4
	<?rfc strict="yes" ?>		" tocInclude="true" xml:lang="en">
	<?rfc toc="yes"?>		<link href="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6548bis-02" r
	<?rfc tocdepth="4"?>		el="prev"/>
	<?rfc symrefs="yes"?>		<link href="https://dx.doi.org/10.17487/rfc8730" rel="alternate"/>
	<?rfc sortrefs="yes" ?>		<link href="urn:issn:2070-1721" rel="alternate"/>
	<?rfc compact="yes" ?>		<front>
	<?rfc subcompact="no" ?>		<title abbrev="Independent Submission Editor Model">Independent Submission E
	<rfc category="info" docName="draft-ietf-iasa2-rfc6548bis-02"		ditor Model</title>
	obsoletes="6548">		<seriesInfo name="RFC" value="8730" stream="IAB"/>
			<author initials="N." surname="Brownlee" fullname="Nevil Brownlee" role="edi
	<front>		tor">
			<organization showOnFrontPage="true">The University of Auckland</organizat
	<title>Independent Submission Editor Model</title>		ion>
			<address>
	<author initials="N." surname="Brownlee" fullname="Nevil Brownlee" role="edito		<email>n.brownlee@auckland.ac.nz</email>
	r">		</address>
	<organization>The University of Auckland</organization>		</author>
	<address><email>n.brownlee@auckland.ac.nz</email></address>		<author fullname="Robert M. Hinden" initials="R" surname="Hinden" role="edit
	</author>		or">
			<organization showOnFrontPage="true">Check Point Software</organization>
	<!--
	<author surname="IAB" fullname="Internet Architecture Board">
	<organization></organization>
	<address><email>iab@iab.org</email>
	</address>
	</author>
	<author fullname="Robert M. Hinden" initials="R"
	surname="Hinden"
	role="editor">
	<organization>Check Point Software</organization>
	<address>		<address>
	<postal>		<postal>
	<street>959 Skyway Road</street>		<street>959 Skyway Road</street>
	<!-- Reorder these if your country does things differently -->
	<city>San Carlos</city>		<city>San Carlos</city>
	<region>CA</region>		<region>CA</region>
	<code>94070</code>		<code>94070</code>
	<country>USA</country>		<country>USA</country>
	</postal>		</postal>
	<phone></phone>
	<facsimile></facsimile>
	<email>bob.hinden@gmail.com</email>		<email>bob.hinden@gmail.com</email>
	<!-- uri and facsimile elements may also be added -->
	</address>		</address>
	</author>		</author>
			<date month="02" year="2020"/>
	<date month="" year="" />		<keyword>ISE</keyword>
			<keyword>IASA</keyword>
	<keyword>RFC</keyword>		<keyword>RSE</keyword>
	<abstract>		<keyword>LLC</keyword>
	<t>		<keyword>IAB</keyword>
			<abstract pn="section-abstract">
			<t pn="section-abstract-1">
	This document describes the function and responsibilities		This document describes the function and responsibilities
	of the RFC Independent Submission Editor (ISE).		of the RFC Independent Submission Editor (ISE).
	The Independent Submission stream is one of the stream producers		The Independent Submission stream is one of the stream producers
	that create draft RFCs,		that create draft RFCs,
	with the ISE as its stream approver.		with the ISE as its stream approver.
	The ISE is overall responsible for activities within		The ISE is overall responsible for activities within
	the Independent Submission stream, working with draft editors and		the Independent Submission stream, working with draft editors and
	reviewers, and interacts with the RFC Production Center		reviewers, and interacts with the RFC Production Center
	and Publisher, and the RFC Series Editor (RSE).		and Publisher, and the RFC Series Editor (RSE).
	The ISE is appointed by the IAB, and also interacts		The ISE is appointed by the IAB, and also interacts
	with the		with the
	IETF Administration Limited Liability Company (LLC).</t>		IETF Administration Limited Liability Company (LLC).</t>
			<t pn="section-abstract-2">This version obsoletes RFC 6548 to replace all
	<t>This version obsoletes RFC 6548 to replace all references to the		references to the
	IASA and related structures with those defined by the IASA 2.0		Internet Administrative Support Activity (IASA) and related structures wit
	Model.</t>		h those defined by the IASA 2.0
			structure.</t>
	<t>[RFC Editor: Please remove the following paragraph prior to		</abstract>
	publication.]</t>		<boilerplate>
			<section anchor="status-of-memo" numbered="false" removeInRFC="false" toc=
	<t>The IASA2 WG requests that the IAB publish this replacement		"exclude" pn="section-boilerplate.1">
	for RFC 6548.</t>		<name slugifiedName="name-status-of-this-memo">Status of This Memo</name
			>
	</abstract>		<t pn="section-boilerplate.1-1">
	</front>		This document is not an Internet Standards Track specification; it i
			s
	<middle>		published for informational purposes.
	<section title="Introduction">		</t>
	<t>		<t pn="section-boilerplate.1-2">
	<!--		This document is a product of the Internet Architecture Board
	The Independent Submissions Editor roles and responsibilities		(IAB) and represents information that the IAB has deemed valuable
	were documented in "RFC Editor Model (version 1)"		to provide for permanent record. It represents the consensus of the
	<xref target="RFC5620"/>.		Internet
	In the light of experience, we see that having it there gave		Architecture Board (IAB). Documents approved for publication
	rise to some confusion as to where and how the ISE fits into		by the IAB are not candidates for any level of Internet Standard; se
	the RFC Editor model.		e
	To reduce that confusion, the ISE material has been moved		Section 2 of RFC 7841.
	into this document.		</t>
			<t pn="section-boilerplate.1-3">
			Information about the current status of this document, any
			errata, and how to provide feedback on it may be obtained at
			<eref target="https://www.rfc-editor.org/info/rfc8730" brackets="non
			e"/>.
			</t>
			</section>
			<section anchor="copyright" numbered="false" removeInRFC="false" toc="excl
			ude" 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 to BCP 78 and the IETF Trust's Legal
			Provisions Relating to IETF Documents
			(<eref target="https://trustee.ietf.org/license-info" brackets="none
			"/>) in effect on the date 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" p
			n="section-toc.1">
			<name slugifiedName="name-table-of-contents">Table of Contents</name>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-to
			c.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 derivedCon
			tent="" format="title" sectionFormat="of" target="name-introduction">Introductio
			n</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 derivedCon
			tent="" format="title" sectionFormat="of" target="name-independent-submission-ed
			it">Independent Submission Editor</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-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 derive
			dContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-qualification
			s">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 derive
			dContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-responsibilit
			ies">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 derivedCon
			tent="" format="title" sectionFormat="of" target="name-independent-submission-ed
			ito">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 derivedCon
			tent="" 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 derivedCon
			tent="" format="title" sectionFormat="of" target="name-references">References</x
			ref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-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 derive
			dContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-normative-ref
			erences">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 derive
			dContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-informative-r
			eferences">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 derivedC
			ontent="" 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 derivedC
			ontent="" format="title" sectionFormat="of" target="name-acknowledgements">Ackno
			wledgements</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 derivedC
			ontent="" format="title" sectionFormat="of" target="name-authors-addresses">Auth
			ors' 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		The RFC Editor Model
	<xref target="I-D.ietf-iasa2-rfc6635bis"/>		<xref target="RFC8728" format="default" sectionFormat="of" derivedContent= "RFC8728"/>
	defines a set of streams that produce draft RFCs, which are		defines a set of streams that produce draft RFCs, which are
	submitted for publication. This document defines the management		submitted for publication. This document defines the management
	function for the Independent Submission stream, specifically the		function for the Independent Submission stream, specifically the
	role of Independent Submission Editor (ISE).</t>		role of Independent Submission Editor (ISE).</t>
			<t pn="section-1-2">
	<t>		The previous version of this
	The previous version of this document is a derivative of <xref		document <xref target="RFC6548" format="default" sectionFormat="of" derive
	target="RFC5620"/>, Section 3.2, and was separated out from <xref		dContent="RFC6548"/> is a derivative of
	target="RFC6635"/>.</t>		<xref target="RFC5620" section="3.2" sectionFormat="comma" format="default
			" derivedLink="https://rfc-editor.org/rfc/rfc5620#section-3.2" derivedContent="R
	<t>		FC5620"/>,
	This document updates the Independent Submission Editor Model to be		and was separated out from <xref target="RFC6635" format="default" section
	aligned with IASA 2.0 Model <xref target="I-D.ietf-iasa2-rfc4071bis"/>		Format="of" derivedContent="RFC6635"/>.</t>
	that creates a IETF Administration Limited Liability Company		<t pn="section-1-3">
			This document updates the Independent Submission Editor Model to
			align it with the IASA 2.0 structure <xref target="RFC8711" format="defaul
			t" sectionFormat="of" derivedContent="RFC8711"/>
			that creates the IETF Administration Limited Liability Company
	("LLC") managed by a board of directors ("LLC Board").		("LLC") managed by a board of directors ("LLC Board").
	This document obsoletes <xref target="RFC6548"/>.		This document obsoletes <xref target="RFC6548" format="default" sectionFor
			mat="of" derivedContent="RFC6548"/>.
	</t>
	</section>
	<section title="Independent Submission Editor">		</t>
	<t>		</section>
			<section numbered="true" toc="include" removeInRFC="false" pn="section-2">
			<name slugifiedName="name-independent-submission-edit">Independent Submiss
			ion Editor</name>
			<t pn="section-2-1">
	The ISE is		The ISE is
	an individual who is responsible for the		an individual who is responsible for the
	Independent Submission stream of RFCs, as defined by		Independent Submission stream of RFCs, as defined by
	<xref target="RFC4844"/>.		<xref target="RFC8729" format="default" sectionFormat="of" derivedContent=
	<!-- The accountability of all RFC Streams Editors is to the		"RFC8729"/>.
	body that appoints them -->
	The Independent Submission stream and the		The Independent Submission stream and the
	ISE are not under the authority or		ISE are not under the authority or
	direction of the RSE or the RFC Series Oversight Committee (RSOC)		direction of the RSE or the RFC Series Oversight Committee (RSOC)
	(see <xref target="I-D.ietf-iasa2-rfc6635bis"/>).		(see <xref target="RFC8728" format="default" sectionFormat="of" derivedCon tent="RFC8728"/>).
	As noted below, the ISE is appointed by and is responsible		As noted below, the ISE is appointed by and is responsible
	directly to the IAB.		directly to the IAB.
	</t>		</t>
			<section numbered="true" toc="include" removeInRFC="false" pn="section-2.1
	<section title="Qualifications">		">
	<t>		<name slugifiedName="name-qualifications">Qualifications</name>
			<t pn="section-2.1-1">
	The ISE is a senior position for		The ISE is a senior position for
	which the following qualifications are desired:		which the following qualifications are desired:
	<list style="numbers">		</t>
	<t>Technical competence, i.e., broad technical experience		<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		and perspective across a wide range of Internet
	technologies and applications, and also the		technologies and applications, and also the
	ability to work effectively with portions of that spectrum		ability to work effectively with portions of that spectrum
	in which they have no personal expertise.</t>		in which they have no personal expertise.</li>
	<t>Thorough familiarity with the RFC series.</t>		<li pn="section-2.1-2.2" derivedCounter="2.">Thorough familiarity with
	<t>An ability to define and constitute advisory and		the RFC series.</li>
			<li pn="section-2.1-2.3" derivedCounter="3.">An ability to define and
			constitute advisory and
	document review arrangements. If those arrangements		document review arrangements. If those arrangements
	include an Editorial Board similar to the current one or		include an Editorial Board similar to the current one or
	some equivalent arrangement, the ability to assess the		some equivalent arrangement, the ability to assess the
	technical competence of potential Editorial Board members		technical competence of potential Editorial Board members
	(see <xref target="editorial_board" />).</t>		(see <xref target="editorial_board" format="default" sectionFormat="
	<t>Good standing in the technical community, in and beyond		of" derivedContent="Section 3"/>).</li>
	the IETF.</t>		<li pn="section-2.1-2.4" derivedCounter="4.">Good standing in the tech
	<t> Demonstrated editorial skills, good command of the		nical community, in and beyond
			the IETF.</li>
			<li pn="section-2.1-2.5" derivedCounter="5."> Demonstrated editorial s
			kills, good command of the
	English language, and demonstrated history of being able		English language, and demonstrated history of being able
	to work effectively with technical documents and materials		to work effectively with technical documents and materials
	created by others.</t>		created by others.</li>
	<t>The ability to work effectively in a multi-actor		<li pn="section-2.1-2.6" derivedCounter="6.">The ability to work effec
			tively in a multi-actor
	environment with divided authority and responsibility		environment with divided authority and responsibility
	similar to that described in		similar to that described in
	<xref target="RFC6635"/>.		<xref target="RFC6635" format="default" sectionFormat="of" derivedCo
	</t>		ntent="RFC6635"/>.
	</list>		</li>
	</t>		</ol>
	</section>		</section>
			<section anchor="Resp" numbered="true" toc="include" removeInRFC="false" p
	<section title="Responsibilities" anchor="Resp">		n="section-2.2">
	<t>		<name slugifiedName="name-responsibilities">Responsibilities</name>
			<t pn="section-2.2-1">
	The ISE is an individual who may		The ISE is an individual who may
	have assistants and who is responsible for:		have assistants and who is responsible for:
	</t>		</t>
	<t>		<ol spacing="normal" type="1" start="1" pn="section-2.2-2">
	<list style="numbers">		<li pn="section-2.2-2.1" derivedCounter="1.">Maintaining technical qua
	<t>Maintaining technical quality of the Independent Submission		lity of the Independent Submission
	stream.</t>		stream.</li>
	<t>Reviewing, approving, and processing Independent Submissions.</t>		<li pn="section-2.2-2.2" derivedCounter="2.">Reviewing, approving, and
	<t>Forwarding draft RFCs in the Independent Submission stream		processing Independent Submissions.</li>
	to the RFC Production Center.</t>		<li pn="section-2.2-2.3" derivedCounter="3.">Forwarding draft RFCs in
	<t>Defining and developing the scope of the Independent Submission		the Independent Submission stream
			to the RFC Production Center.</li>
			<li pn="section-2.2-2.4" derivedCounter="4.">Defining and developing t
			he scope of the Independent Submission
	stream as a part of the overall RFC Editor function		stream as a part of the overall RFC Editor function
	<xref target="RFC6635"/>.</t>		<xref target="RFC6635" format="default" sectionFormat="of" derivedCo
	<t>Reviewing and approving RFC errata for Independent Submissions.</t>		ntent="RFC6635"/>.</li>
	<t>Coordinating work and conforming to general RFC Series		<li pn="section-2.2-2.5" derivedCounter="5.">Reviewing and approving R
	policies as specified by the IAB and RSE.</t>		FC errata for Independent Submissions.</li>
	<t> Providing statistics and documentation as requested by the		<li pn="section-2.2-2.6" derivedCounter="6.">Coordinating work and con
	RSE and/or LLC.</t>		forming to general RFC Series
	</list>		policies as specified by the IAB and RSE.</li>
	</t>		<li pn="section-2.2-2.7" derivedCounter="7."> Providing statistics and
	<t>		documentation as requested by the
			RSE and/or LLC.</li>
			</ol>
			<t pn="section-2.2-3">
	The ISE may choose to select individuals to participate in		The ISE may choose to select individuals to participate in
	an Advisory Board for assistance in special topics as the		an Advisory Board for assistance in special topics as the
	ISE deems appropriate. Such an Advisory Board exists		ISE deems appropriate. Such an Advisory Board exists
	at the pleasure of the ISE, and its members serve at the		at the pleasure of the ISE, and its members serve at the
	pleasure of the ISE.		pleasure of the ISE.
	<!-- The Independent Submission Editor may create and seek support		</t>
	from an advisory board (see <xref target="RFC4846"/>).		<t pn="section-2.2-4">
	Such a board would provide advice to the ISE on any aspect
	of the Independent Stream and its activities. -->
	</t><t>
	The individual with the listed qualifications is		The individual with the listed qualifications is
	selected by the IAB after input has been collected from the		selected by the IAB after input has been collected from the
	community.		community.
	</t>		</t>
			<t pn="section-2.2-5">
	<!--
	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 th
	e 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>
	While the ISE itself is considered a volunteer function, the		While the ISE itself is considered a volunteer function, the
	IAB considers maintaining the Independent Submission stream		IAB considers maintaining the Independent Submission stream
	part of the IAB's supported activities. Therefore, the LLC		part of the IAB's supported activities. Therefore, the LLC
	should include these costs in the IASA budget.		should include these costs in the IASA budget.
	</t>		</t>
			</section>
	</section>		</section>
	</section>		<section anchor="editorial_board" numbered="true" toc="include" removeInRFC=
			"false" pn="section-3">
	<section title="Independent Submission Editorial Board"		<name slugifiedName="name-independent-submission-edito">Independent Submis
	anchor="editorial_board">		sion Editorial Board</name>
	<t>		<t pn="section-3-1">
	The ISE is supported by an Editorial		The ISE is supported by an Editorial
	Board for the review of Independent Submission stream documents.		Board for the review of Independent Submission stream documents.
	This board is known as the Independent Submission Editorial		This board is known as the Independent Submission Editorial
	Board. This volunteer Editorial Board exists at the pleasure of		Board. This volunteer Editorial Board exists at the pleasure of
	the ISE, and its members		the ISE, and its members
	serve at the pleasure of the ISE. The existence of this board is		serve at the pleasure of the ISE. The existence of this board is
	simply noted within this model, and additional discussion of		simply noted within this model, and additional discussion of
	such is considered out of scope of this document.		such is considered out of scope of this document.
	</t>		</t>
	</section>		</section>
			<section numbered="true" toc="include" removeInRFC="false" pn="section-4">
	<section title="Security Considerations">		<name slugifiedName="name-security-considerations">Security Considerations
	<t>		</name>
			<t pn="section-4-1">
	This document has no specific security implications, however the		This document has no specific security implications, however the
	same security considerations as those in <xref target="RFC4846"/> and <xref		same security considerations as those in <xref target="RFC4846" format="default"
	target="RFC4844"/> apply.		sectionFormat="of" derivedContent="RFC4846"/>
			and <xref target="RFC8729" format="default" sectionFormat="of" derivedContent="R
			FC8729"/> apply.
	</t>		</t>
	</section>		</section>
	<section title="IAB Members at the Time of Approval">		</middle>
			<back>
	<t> The IAB members at the time of approval of <xref		<references pn="section-5">
	target="RFC6548"/> were: Bernard Aboba, Ross Callon, Alissa Cooper,		<name slugifiedName="name-references">References</name>
	Joel Halpern, Spencer Dawkins, Russ Housley, David Kessens, Olaf		<references pn="section-5.1">
	Kolkman, Danny McPherson, Jon Peterson, Andrei Robachevsky, Dave		<name slugifiedName="name-normative-references">Normative References</na
	Thaler, and Hannes Tschofenig.		me>
	</t>		<reference anchor="RFC4846" target="https://www.rfc-editor.org/info/rfc4
			846" quoteTitle="true" derivedAnchor="RFC4846">
	<t>The IAB members at the time of approval of this document were:		<front>
	Jari Arrko, Alissa Cooper, Ted Hardie, Christian Heuitema, Gabriel		<title>Independent Submissions to the RFC Editor</title>
	Montenegro, Erik Nordmark, Mark Nottingham, Melina Shore, Robert		<author initials="J." surname="Klensin" fullname="J. Klensin" role="
	Sparks, Jeff Tantsura, Martin Thomson, Brian Trammell, and Suzanne		editor">
	Woolf.		<organization showOnFrontPage="true"/>
	</t>		</author>
			<author initials="D." surname="Thaler" fullname="D. Thaler" role="ed
	</section>		itor">
			<organization showOnFrontPage="true"/>
	<section title="Acknowledgements">		</author>
	<t>		<date year="2007" month="July"/>
	Generous thanks to Joel Hapern for all his help with this document,		<abstract>
	and for all his work on <xref target="RFC6635"/>).		<t>There is a long-standing tradition in the Internet community, p
			redating 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 proce
			ss and its review and approval mechanisms. These documents, known as "Independen
			t Submissions", serve a number of important functions for the Internet community
			, both inside and outside of the community of active IETF participants. This do
			cument discusses the Independent Submission model and some reasons why it is imp
			ortant. It then describes editorial and processing norms that can be used for I
			ndependent Submissions as the community goes forward into new relationships betw
			een 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/rfc6
			548" 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 th
			e 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 I
			SE is appointed by the IAB, and also interacts with the IETF Administrative Over
			sight Committee (IAOC). This document is not an Internet Standards Track speci
			fication; 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/rfc8
			711" quoteTitle="true" derivedAnchor="RFC8711">
			<front>
			<title>Structure of the IETF Administrative Support Activity, Versio
			n 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/rfc8
			728" 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/rfc8
			729" 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/rfc5
			620" 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 carri
			ed out by various persons or entities. The RFC Editor model presented in this d
			ocument 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 a
			n (optional) Independent Submission Stream Editorial Board. The model outlined
			here is intended to increase flexibility and operational support options, provid
			e for the orderly succession of the RFC Editor, and ensure the continuity of the
			RFC series, while maintaining RFC quality and timely processing, ensuring docum
			ent 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/rfc6
			635" 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 res
			ponsibilities for the RFC Series into three functions: the RFC Series Editor, th
			e RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB
			) oversight via the RFC Series Oversight Committee (RSOC) is described, as is th
			e relationship between the IETF Administrative Oversight Committee (IAOC) and th
			e RSOC. This document reflects the experience gained with "RFC Editor Model (Ve
			rsion 1)", documented in RFC 5620, and obsoletes that document. This document i
			s not an Internet Standards Track specification; it is published for informatio
			nal 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-appe
			ndix.a">
			<name slugifiedName="name-iab-members-at-the-time-of-">IAB Members at the
			Time of Approval</name>
			<t pn="section-appendix.a-1"> The IAB members at the time of approval of
			<xref target="RFC6548" format="default" sectionFormat="of" derivedContent="R
			FC6548"/> were: <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 McPherso
			n"/>, <contact fullname="Jon Peterson"/>, <contact fullname="Andrei Robachev
			sky"/>, <contact fullname="Dave Thaler"/>, and <contact fullname="Hannes Tsc
			hofenig"/>.
			</t>
			<t pn="section-appendix.a-2">The IAB members at the time of approval of th
			is document (RFC 8730) were:
			<contact fullname="Jari Arkko"/>, <contact fullname="Alissa Cooper"/>,
			<contact fullname="Stephen Farrell"/>, <contact fullname="Wes Hardaker"/>, <c
			ontact 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>
			<section numbered="false" toc="include" removeInRFC="false" pn="section-appe
			ndix.b">
			<name slugifiedName="name-acknowledgements">Acknowledgements</name>
			<t pn="section-appendix.b-1">
			Generous thanks to <contact fullname="Joel Halpern"/> for all his help wit
			h this document,
			and for all his work on <xref target="RFC6635" format="default" sectionFor
			mat="of" derivedContent="RFC6635"/>.
	Thanks also to the IAB members, whose comments and suggestions		Thanks also to the IAB members, whose comments and suggestions
	were both welcome and useful.		were both welcome and useful.
	</t>		</t>
			<t pn="section-appendix.b-2"><contact fullname="Bob Hinden"/> served as do
	<t>Bob Hinden served as documented editor for this version of this document		cument editor for this RFC to
	that aligned it with the IASA 2.0 model.</t>		align it with the IASA 2.0 structure.</t>
			</section>
	</section>		<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc
			="include" pn="section-appendix.c">
	</middle>		<name slugifiedName="name-authors-addresses">Authors' Addresses</name>
			<author initials="N." surname="Brownlee" fullname="Nevil Brownlee" role="e
	<back>		ditor">
	<references title='Normative References'>		<organization showOnFrontPage="true">The University of Auckland</organiz
			ation>
	<?rfc include="reference.RFC.4846"?> <!-- Independent Submissions -->		<address>
			<email>n.brownlee@auckland.ac.nz</email>
	<?rfc include="reference.RFC.4844"?>		</address>
			</author>
	<?rfc include="reference.I-D.ietf-iasa2-rfc4071bis.xml"?>		<author fullname="Robert M. Hinden" initials="R" surname="Hinden" role="ed
			itor">
	<?rfc include="reference.I-D.ietf-iasa2-rfc6635bis.xml"?>		<organization showOnFrontPage="true">Check Point Software</organization>
			<address>
	<?rfc include="reference.RFC.6548"?>		<postal>
			<street>959 Skyway Road</street>
	</references>		<city>San Carlos</city>
			<region>CA</region>
	<references title='Informative References'>		<code>94070</code>
			<country>USA</country>
	<!--		</postal>
	<?rfc include="reference.RFC.4333"?>		<email>bob.hinden@gmail.com</email>
			</address>
	<?rfc include="reference.RFC.5620"?> <!-- RFC ED Model (v1) -->		</author>
			</section>
	<?rfc include="reference.RFC.6635"?> <!-- RFC ED Model (v2) -->		</back>
	</references>
	<section anchor="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 name of IAB 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" ?>
	</section>
	</back>
	</rfc>		</rfc>
End of changes. 28 change blocks.
	312 lines changed or deleted		534 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/