sandy-ise-new.txt		sandy-draft-ise.txt
	An Overview of Publishing RFCs Via The Independent Submissions Process		Draft – ISE Process
			The Independent Submission Stream allows RFC publication for some documents that
			are outside the official processes of the IETF, IAB, and IRTF but are relevant
			to the Internet community and achieve reasonable levels of technical and editori
			al quality. RFC 8730, “Independent Submission Editor Model”, as updated by RFC 9
			280, describes the roles of
			the Independent Submissions Editor (ISE) and
			the Independent Submissions Editorial Board, which provides review for the I
			SE.
			The Independent Submissions Editor (ISE) is currently Eliot Lear, who can be rea
			ched at rfc-ise@rfc-editor.org.
			An Overview of Publishing RFCs via the Independent Submissions Process
	Introduction		Introduction
	Not all RFCs are published through the IETF. Some are published as independent submissions. These documents do not require, nor do they carry, community conse nsus, and they are not standards or best practices.
	What sort of documents are independent submissions?		Not all RFCs are published through the IETF. Some are published as independent s
	The independent series covers a number of classes of submissions, including disc		ubmissions. These documents do not require, nor do they carry, community consens
	ussions of technologies, options, or experience with protocols; humor; documenta		us, and they are not standards or best practices.
	tion of vendor-specific protocols, introduction of new ideas that may not yet be		The following figure depicts the different streams that feed into the RFC Series
	ripe for standardization; critiques of the IETF process; and a few other areas.		.
	The current independent submissions editor looks at document through the lens of
	three questions:		alt> A description of the different streams that feed into the RFC series. Once
	1. Does this specification improve interoperability?		initially approved for publication, they are processed by the RFC Production Cen
	2. Does this document provide a path for continuous improvement of the Inter		ter, and then go on to be published.
	net?
	3. Does this document provide the community some levity?		What sort of documents are independent submissions?
			What are some examples of RFCs published through the Independent Stream that
			hit at least one of those points?
			What other criteria are there for Independent Stream RFCs?
			What if a document isn’t appropriate as an independent submission?
			What about Intellectual Property Rights (IPR)?
			What’s the process?
			How does one submit a draft for consideration as an independent submission R
			FC?
			At what stage is a document?
			Who makes decisions about independent submissions?
			Who reviews submissions?
			Where can reviews be found?
			What is IETF Conflict Review?
			How is a decision made?
			What happens if a work is declined?
			Can an Independent Submission be changed once it is published as an RFC?
			What is the Conflict of Interest Policy?
			More questions?
			What sort of documents are independent submissions?
			The Independent Stream covers a number of classes of submissions, including disc
			ussions of technologies, options, or experience with protocols; humor; documenta
			tion of vendor-specific protocols; introduction of new ideas that may not yet be
			ripe for standardization; critiques of the IETF process; and a few other areas.
			The current Independent Submissions Editor looks at a document through the lens
			of three questions:
			Does this specification improve interoperability?
			Does this document contribute to continuous improvement of the Internet?
			Does this document provide the community some levity?
	Not every submission needs to hit all three points.		Not every submission needs to hit all three points.
	What are some examples of RFCs published through the independent series that hit
	s at least one of those points?
	• RFC 9446 provides us a retrospective on ten years after the Snowden revel
	ations, how the community reacted, what was accomplished, and what could be done
	better.
	• RFC 9518 talks about Internet centralization, its impact, and what, if an
	ything, can be done about it.
	• RFC 9405 discusses sarcasm h AI systems; and was written in part by ChatG
	PT.
	• RFC 9383 specifies the SPAKE2+ augmented password-authenticated key excha
	nge (PAKE) protocol.
	What other criteria are there for independent series RFCs?
	Documents must be well written, appropriate for the readership of the RFC series
	. They must not present either security or operational risks to the Internet, a
	nd they must adhere to any IANA rules for code point allocation, and in general
	may not create new IANA registries. Internal implementation descriptions are ge
	nerally not accepted, nor are foundational formats upon which standards are expe
	cted to be built.
	What if a document isn’t appropriate as an independent submission?
	If a document is not appropriate as an independent submission, the independent s
	ubmissions editor will attempt to assist the authors to find a more appropriate
	home. That could be the IETF, the IRTF, some other standards organization, a blo
	g, or an academic publication.
	Intellectual Property Rights (IPR)
	An independent RFC should generally provide an open license to implement and dep
	loy some or all of the technology described in the document. As RFC 4846 states
	, text from independent submissions should be made available to be reused for an
	y purpose.
	What’s the Process?
	Everything begins with an Internet-Draft. You can use the same tooling that is		What are some examples of RFCs published through the Independent Stream that
	used by the IETF to create and publish it onto the datatracker. See authors.iet		hit at least one of those points?
	f.org for more information about authoring tools.
			RFC 9446 provides us a retrospective on ten years after the Snowden reve
			lations, how the community reacted, what was accomplished, and what could be don
			e better.
			RFC 9518 talks about Internet centralization, its impact, and what, if a
			nything, can be done about it.
			RFC 9405 discusses sarcasm in AI systems, and was written in part by Cha
			tGPT.
			RFC 9383 specifies the SPAKE2+ augmented password-authenticated key exch
			ange (PAKE) protocol.
			What other criteria are there for Independent Stream RFCs?
			Documents must be well written, understandable, and appropriate for the readersh
			ip of the RFC series. They must not present security or operational risks to the
			Internet, and they must adhere to any IANA rules for code point allocation, and
			in general may not create new IANA registries. Internal implementation descript
			ions are generally not accepted, nor are foundational formats upon which standar
			ds are expected to be built.
			What if a document isn’t appropriate as an independent submission?
			If a document is not appropriate as an independent submission, the Independent S
			ubmissions Editor will attempt to assist the authors to find a more appropriate
			home. That could be the IETF, the IRTF, some other standards organization, a blo
			g, or an academic publication.
			What about Intellectual Property Rights (IPR)?
			An independent RFC should generally provide an open license to implement and dep
			loy some or all of the technology described in the document; text from that docu
			ment is available to be reused for any purpose.
			What’s the process?
			alt> The publication pipeline: steps include submission, initial evaluation, doc
			ument updates, commissioned reviews, ISE review, more document updates, IESG con
			flict review, more document updates, publication request, to the RPC and final e
			dits (AUTH48).
			Everything begins with an Internet-Draft. You can use the same tooling that is u
			sed by the IETF to create and publish it onto the Datatracker. See authors.ietf.
			org for more information about authoring tools.
	The rest of the process is summarized as follows:		The rest of the process is summarized as follows:
	1. Submit a draft
	2. Fill out the independent submissions template		Submit a draft
	3. Submit the template to the independent submissions editor		Fill out the independent submissions template
	4. Initial ISE review		Submit the template to the Independent Submissions Editor
	5. Commissioned reviews		Initial ISE review
	6. Follow-up ISE review		Commissioned reviews
	7. IETF Conflict Review		Follow-up ISE review
	8. Follow-up ISE review		IETF Conflict Review
	9. Initial publication decision		Follow-up ISE review
	10. Submission to the RFC Production Center (RPC)		Initial publication decision
	11. AUTH48		Submission to the RFC Production Center (RPC)
	12. Publication		AUTH48
	It’s important to note that many drafts do not make it passed Step 4, and that e		Publication
	very step after submission may be iterated or repeated. For instance, if extern
	al review indicates that substantial amounts of work is needed, authors are expe		It’s important to note that many drafts do not make it past Step 4, and that eve
	cted to improve the document in discussions with reviewers and the independent s		ry step after submission may be iterated or repeated. For instance, if external
	ubmissions editor.		review indicates that substantial amounts of work are needed, authors are expect
	How does one submit a draft for consideration as an independent submission RFC?		ed to improve the document in discussions with reviewers and the Independent Sub
			missions Editor.
			How does one submit a draft for consideration as an independent submission R
			FC?
	To be considered for publishing as an RFC, a document must first be posted onlin e as an Internet-Draft. (The exception is a document that is submitted for consi deration as an April 1st RFC.) See I-D Author Resources for guidance on posting an Internet-Draft.		To be considered for publishing as an RFC, a document must first be posted onlin e as an Internet-Draft. (The exception is a document that is submitted for consi deration as an April 1st RFC.) See I-D Author Resources for guidance on posting an Internet-Draft.
	After posting the document as an Internet-Draft, the author should send an email message to the ISE: rfc-ise@rfc-editor.org. This message should include the fol lowing information:		After posting the document as an Internet-Draft, the author should send an email message to the ISE: rfc-ise@rfc-editor.org. This message should include the fol lowing information:
	• The file name of the published Internet-Draft that is being submitted.
	• The desired category (Informational or Experimental).
	• A summary of related discussion of this document, if any, that has occurr
	ed in an IETF working group or in the IESG.
	• An assertion that no IANA allocation in the document requires IETF Review
	or Standards Action. See RFC 8126 for a definition of these terms and RFC 8726
	for more information about how IANA requests are handled for Independent Submiss
	ion Stream documents.
	• A statement describing the purpose, intended audience, merits, and signif
	icance of the document.
	• An acknowledgment that the IPR rules of RFCs 4846 and 5744 apply, and tha
	t unless the authors state otherwise, permission is granted to produce derivativ
	e works, in whole or in part, as stated in those RFCs.
	• Suggestions for one or more competent and independent potential reviewers
	for the document, including contact information. This can speed the review and
	approval process.
	The ISE uses the IETF Datatracker through all stages of Independent Submission S
	tream document handling. The Datatracker page for a given draft shows its ISE st
	ate. RFC 6322 provides descriptions of these states. In addition, a complete lis
	t showing the ISE state for all documents in the Independent Submission Stream i
	s available here.
	At what stage is a document?
	Information about the current state of an independent submission can be found on
	the datatracker page for that draft.
	Note that a document can sometimes appear to go “backwards” in the process. Thi		The file name of the published Internet-Draft that is being submitted.
	s is not unusual, indicates that either additional reviews require more work on		The desired category (Informational or Experimental).
	someone’s part.		A summary of related discussion of this document, if any, that has occur
	Who makes decisions about independent submissions?		red in an IETF working group or in the IESG.
	The independent submissions editor is responsible for making decisions about eac		An assertion that no IANA allocation in the document requires IETF Revie
	h submission, in accordance with the guidance set forth in RFC 4846. The indepe		w or Standards Action. See RFC 8126 for a definition of these terms and RFC 8726
	ndent submissions editor is appointed by the Internet Architecture Board (IAB),		for more information about how IANA requests are handled for Independent Submis
	and serves at their pleasure. Anyone may send comments to the IAB about the ind		sion Stream documents.
	ependent submissions editor.		A statement describing the purpose, intended audience, merits, and signi
	The independent submissions editor is ably assisted by the Independent Submissio		ficance of the document.
	ns Editorial Board (ISEB).		An acknowledgment that the IPR rules of RFCs 4846 and 5744 apply, and th
	Who reviews submissions?		at unless the authors state otherwise, permission is granted to produce derivati
	The independent submissions editor seeks review of the work through individuals		ve works, in whole or in part, as stated in those RFCs.
	who are knowledgeable about the topic discussed in the draft. Authors are encou		Suggestions for one or more competent and independent potential reviewer
	raged to submit suggestions, but some reviews will be conducted outside of that		s for the document, including contact information. This can speed the review and
	list. The ISE often relies on the Independent Submissions Editorial Board (ISEB		approval process.
	) to provide reviews. In addition, the ISE welcomes comments from anyone on a d
	raft that is being considered by the independent submissions editor.
	Where can reviews be found?
	Unless they have been submitted anonymously, reviews are provided to authors, an
	d will be provided to others upon request.
	What is IETF Conflict Review		The ISE uses the IETF Datatracker through all stages of Independent Submission S
	In general, submissions should not conflict with IETF work or established best p		tream document handling. The Datatracker page for a given draft shows its ISE st
	ractices. RFC 5742 provides the IESG the opportunity to comment about whether t		ate. RFC 6322 provides descriptions of these states. In addition, a complete lis
	his is the case. Most of the time a document will not get to the stage of the I		t showing the ISE state for all documents in the Independent Submission Stream i
	ESG even being consulted if such a conflict is likely. If the IESG determines t		s available in the Datatracker.
	hat there is a conflict of some form, the ISE will attempt to work with authors
	and the IESG to resolve it satisfactorily.		At what stage is a document?
	How is a publication decision made?
	The Independent Submissions Editor takes into account the preponderance of revie		Information about the current state of an independent submission can be found on
	ws as well as the IESG’s input in making a publication determination as to wheth		the Datatracker page for that draft.
	er the document can be published. If a document is not suitable for publication
	, in some cases, this may be rectified with additional work by the authors. In		alt> Snapshot of a Datatracker entry for an Internet-Draft that shows the docume
	other cases, the publication decision is final.		nt’s state.
	The independent submissions editor reserves the right to not publish any work up
	until the point that it has been released as an RFC.		Note that a document can sometimes appear to go “backwards” in the process. This
	What happens if a work is declined?		is not unusual, indicating that either additional reviews require more work on
	Authors may seek further review of their work, either by the independent submiss		someone’s part.
	ions editor or by the IAB. The IAB may choose to review a document or not. If
	it does, then the IAB will advise the independent submissions editor as to their		Who makes decisions about independent submissions?
	views. In all cases, the independent submissions editor makes the final decisi
	on.		The Independent Submissions Editor is responsible for making decisions about eac
	Can an Independent Submission be changed once it is published as an RFC?		h submission, in accordance with the guidance set forth in RFC 4846. The Indepen
	No. RFCs are, for the most part, immutable. However, anyone may submit an erra		dent Submissions Editor is appointed by the Internet Architecture Board (IAB), a
	tum about any RFC, and those that are accepted will be noted on the RFC Editor w		nd serves at their pleasure. Anyone may send comments to the IAB about the Indep
	eb page.		endent Submissions Editor.
	What is the Conflict of Interest Policy?
	From time to time, the Independent Submissions Editor may have a conflict of int		The Independent Submissions Editor is ably assisted by the Independent Submissio
	erest, or the appearance of a conflict of interest, with regard to a particular		ns Editorial Board.
	draft. This can occur for a number of reasons, including when submissions are re
	ceived from people who are employed by the ISE’s employer or its competitors. Su		Who reviews submissions?
	ch relationships in and of themselves may not lead to variance in the editorial
	process, but they must be disclosed.		The Independent Submissions Editor seeks review of the work through individuals
	When the ISE believes that there may be a conflict of interest, or if authors or		who are knowledgeable about the topic discussed in the draft. Authors are encour
	others believe that there is a conflict of interest, the matter will be referre		aged to submit suggestions, but some reviews will be conducted outside of that l
	d to the Independent Submissions Editorial Board. They will advise the ISE as to		ist. The ISE often relies on the Independent Submissions Editorial Board to prov
	what should happen at the various stages of the publication process. The ISE wi		ide reviews. In addition, the ISE welcomes comments from anyone on a draft that
	ll inform the community and authors of such conflicts, and any actions to be tak		is being considered by the Independent Submissions Editor.
	en as a result.
	More questions?		Where can reviews be found?
	We are happy to answer any questions you might have. Contact us here.
			Unless they have been submitted anonymously, reviews are provided to authors and
			will be provided to others upon request.
			alt> Snapshot of the Datatracker entry for a draft that shows reviews.
			What is IETF Conflict Review?
			In general, submissions should not conflict with IETF work or established best p
			ractices. RFC 5742 provides the IESG the opportunity to comment about whether th
			is is the case. Most of the time, a document will not get to the stage of the IE
			SG even being consulted if such a conflict is likely. If the IESG determines tha
			t there is a conflict of some form, the ISE will attempt to work with authors an
			d the IESG to resolve it satisfactorily.
			How is a decision made?
			The Independent Submissions Editor takes into account the preponderance of revie
			ws, as well as the IESG’s input, in making a publication determination as to whe
			ther the document can be published. If it cannot, in some cases, this may be rec
			tified with additional work by the authors. In other cases, the publication deci
			sion is final.
			The Independent Submissions Editor reserves the right to not publish any work up
			until the point that it has been released as an RFC.
			What happens if a work is declined?
			Authors may seek further review of their work, either by the Independent Submiss
			ions Editor or by the IAB, who may choose to review a document or not. If it doe
			s, then the IAB will advise the Independent Submissions Editor as to their views
			. In all cases, the Independent Submissions Editor makes the final decision.
			Can an Independent Submission be changed once it is published as an RFC?
			No. RFCs are immutable. However, anyone may submit an erratum about any RFC, and
			those that are accepted will be noted on the RFC Editor web page.
			What is the Conflict of Interest Policy?
			From time to time, the Independent Submissions Editor may have a conflict of int
			erest, or the appearance of a conflict of interest, with regard to a particular
			draft. This can occur for a number of reasons, for example, a document submitted
			by an author that is employed by the same employer as the ISE or one of its com
			petitors. Such relationships in and of themselves may not lead to variance in th
			e editorial process, but they must be disclosed.
			When the ISE believes that there may be a conflict of interest, or if authors or
			others believe that there may be a conflict of interest, the matter will be ref
			erred to the Independent Submissions Editorial Board. They will advise the ISE a
			s to what should happen at the various stages of the publication process. The IS
			E will inform the community and authors of such conflicts, and any actions to be
			taken as a result.
			More questions?
			We are happy to answer any questions you might have. Contact us here.
End of changes. 10 change blocks.
	108 lines changed or deleted		145 lines changed or added
This html diff was produced by rfcdiff 1.48.