Yes True 1 False No Objection True 2 False Discuss True 3 True Block True 3 True Abstain True 4 False Recuse True 5 False No Record True 6 False Conflicts with True 0 Conflicts with (secondary) True 0 Conflicts with (tertiary) True 0 Obsoletes True 0 Updates True 0 Replaces True 0 conflict reviews True 0 Stream state should change True 0 IANA coordination RFC-Editor/IANA Registration Coordination True 0 Holding for references Holding for normative reference True 0 Missing references Awaiting missing normative reference True 0 Has errata True 0 Review by RFC Editor True 0 Via RFC Editor True 0 Approved in minute True 0 Shepherd Needed True 0 Waiting for Dependency on Other Document True 0 IESG Review Completed True 0 Point Raised - writeup needed IESG discussions on the document have raised some issues that need to be brought to the attention of the authors/WG, but those issues have not been written down yet. (It is common for discussions during a telechat to result in such situations. An AD may raise a possible issue during a telechat and only decide as a result of that discussion whether the issue is worth formally writing up and bringing to the attention of the authors/WG). A document stays in the "Point Raised - Writeup Needed" state until *ALL* IESG comments that have been raised have been documented. True 1 Awaiting Expert Review/Resolution of Issues Raised True 1 Editor Needed True 1 AD Followup A generic substate indicating that the shepherding AD has the action item to determine appropriate next steps. In particular, the appropriate steps (and the corresponding next state or substate) depend entirely on the nature of the issues that were raised and can only be decided with active involvement of the shepherding AD. Examples include: - if another AD raises an issue, the shepherding AD may first iterate with the other AD to get a better understanding of the exact issue. Or, the shepherding AD may attempt to argue that the issue is not serious enough to bring to the attention of the authors/WG. - if a documented issue is forwarded to a WG, some further iteration may be needed before it can be determined whether a new revision is needed or whether the WG response to an issue clarifies the issue sufficiently. - when a new revision appears, the shepherding AD will first look at the changes to determine whether they believe all outstanding issues have been raised satisfactorily, prior to asking the ADs who raised the original issues to verify the changes. True 2 Awaiting External Review/Resolution of Issues Raised True 2 Waiting for Partner Feedback True 2 External Party The document is awaiting review or input from an external party (i.e, someone other than the shepherding AD, the authors, or the WG). See the "note" field for more details on who has the action. True 3 Awaiting Merge with Other Document True 3 Awaiting Reviews True 3 Author or Editor Needed True 4 Document Shepherd Followup True 4 Revised ID Needed An updated ID is needed to address the issues that have been raised. True 5 Waiting for Referenced Document True 5 Waiting for Referencing Document True 6 Revised I-D Needed - Issue raised by WGLC True 7 Revised I-D Needed - Issue raised by AD True 8 Revised I-D Needed - Issue raised by IESG True 9 Doc Shepherd Follow-up Underway True 10 Other - see Comment Log True 11 Charter True 0 Agenda True 0 Minutes True 0 Slides True 0 Draft True 0 Liaison Attachment True 0 Maturity Change True 0 Conflict Review True 0 No True 0 Yes True 0 Abstain True 0 Block True 0 No record True 0 BOF True 0 Proposed True 0 Active True 0 Dormant True 0 Concluded True 0 Unknown True 0 IETF True 0 Area True 0 AG Area group True 0 WG Working group True 0 RG Research group True 0 Team True 0 Individual True 0 SDO Standards organization True 0 IRTF True 0 Proposed Standard True 1 Draft Standard False 2 Internet Standard True 3 Best Current Practice True 4 Informational True 5 Experimental True 6 Historic True 7 For action True 1 For comment True 2 For information True 3 In response True 4 IETF True 0 Interim True 0 Area Director True 0 Incoming Area Director True 0 Chair True 0 Editor True 0 Secretary True 0 Tech Advisor True 0 Executive Director True 0 Administrative Director True 0 Liaison Manager True 0 Authorized Individual True 0 Delegate True 0 Waiting for Scheduling True 0 Waiting for Approval True 0 Approved True 0 Scheduled True 0 Canceled True 0 Disapproved True 0 Not meeting True 0 Deleted True 0 Internet Standard True 0 Draft Standard False 0 Proposed Standard True 0 Informational True 0 Experimental True 0 Best Current Practice True 0 Historic True 0 Unknown True 0 IETF IETF stream True 1 ISE Independent Submission Editor stream True 2 IRTF Independent Submission Editor stream True 3 IAB IAB stream True 4 Legacy Legacy stream True 5 Other True 0 Session True 0 Break True 0 Registration True 0 Plenary True 0 State IESG state IANA state RFC Editor state IETF state IRTF state ISE state IAB state State State State State State Conflict Review State agenda active Active True 1 agenda deleted Deleted True 2 charter notrev Not currently under review True The proposed charter is not being considered at this time. A proposed charter will remain in this state until an AD moves it to Informal IESG review. 0 charter infrev Informal IESG review True This is the initial state when an AD proposes a new charter. The normal next state is Internal review if the idea is accepted, or Not currently under review if the idea is abandoned. 0 charter intrev Internal review True The IESG and IAB are reviewing the early draft of the charter; this is the initial IESG and IAB review. The usual next state is External review if the idea is adopted, or Informal IESG review if the IESG decides the idea needs more work, or Not currently under review is the idea is abandoned 0 charter extrev External review True The IETF community and possibly other standards development organizations (SDOs) are reviewing the proposed charter. The usual next state is IESG review, although it might move to Not currently under review is the idea is abandoned during the external review. 0 charter iesgrev IESG review True The IESG is reviewing the discussion from the external review of the proposed charter. The usual next state is Approved, or Not currently under review if the idea is abandoned. 0 charter approved Approved True The charter is approved by the IESG. 0 conflrev needshep Needs Shepherd True A conflict review has been requested, but a shepherding AD has not yet been assigned 1 conflrev adrev AD Review True The sponsoring AD is reviewing the document and preparing a proposed response 2 conflrev iesgeval IESG Evaluation True The IESG is considering the proposed conflict review response 3 conflrev defer IESG Evaluation - Defer True The evaluation of the proposed conflict review response has been deferred to the next telechat 4 conflrev appr-reqnopub-pend Approved Request to Not Publish - announcement to be sent True The IESG has approved the conflict review response (a request to not publish), but the secretariat has not yet sent the response 5 conflrev appr-noprob-pend Approved No Problem - announcement to be sent True The IESG has approved the conflict review response, but the secretariat has not yet sent the response 6 conflrev appr-reqnopub-sent Approved Request to Not Publish - announcement sent True The secretariat has delivered the IESG's approved conflict review response (a request to not publish) to the requester 7 conflrev appr-noprob-sent Approved No Problem - announcement sent True The secretariat has delivered the IESG's approved conflict review response to the requester 8 conflrev withdraw Withdrawn True The request for conflict review was withdrawn 9 conflrev dead Dead True The conflict review has been abandoned 10 draft active Active True 1 draft expired Expired True 2 draft rfc RFC True 3 draft repl Replaced True 4 draft auth-rm Withdrawn by Submitter True 5 draft ietf-rm Withdrawn by IETF True 6 draft-iesg pub-req Publication Requested True A formal request has been made to advance/publish the document, following the procedures in Section 7.5 of RFC 2418. The request could be from a WG chair, from an individual through the RFC Editor, etc. (The Secretariat (iesg-secretary@ietf.org) is copied on these requests to ensure that the request makes it into the ID tracker.) A document in this state has not (yet) been reviewed by an AD nor has any official action been taken on it yet (other than to note that its publication has been requested. 10 draft-iesg ad-eval AD Evaluation True A specific AD (e.g., the Area Advisor for the WG) has begun reviewing the document to verify that it is ready for advancement. The shepherding AD is responsible for doing any necessary review before starting an IETF Last Call or sending the document directly to the IESG as a whole. 11 draft-iesg review-e Expert Review True An AD sometimes asks for an external review by an outside party as part of evaluating whether a document is ready for advancement. MIBs, for example, are reviewed by the "MIB doctors". Other types of reviews may also be requested (e.g., security, operations impact, etc.). Documents stay in this state until the review is complete and possibly until the issues raised in the review are addressed. See the "note" field for specific details on the nature of the review. 12 draft-iesg lc-req Last Call Requested True The AD has requested that the Secretariat start an IETF Last Call, but the the actual Last Call message has not been sent yet. 15 draft-iesg lc In Last Call True The document is currently waiting for IETF Last Call to complete. Last Calls for WG documents typically last 2 weeks, those for individual submissions last 4 weeks. 16 draft-iesg writeupw Waiting for Writeup True Before a standards-track or BCP document is formally considered by the entire IESG, the AD must write up a protocol action. The protocol action is included in the approval message that the Secretariat sends out when the document is approved for publication as an RFC. 18 draft-iesg goaheadw Waiting for AD Go-Ahead True As a result of the IETF Last Call, comments may need to be responded to and a revision of the ID may be needed as well. The AD is responsible for verifying that all Last Call comments have been adequately addressed and that the (possibly revised) document is in the ID directory and ready for consideration by the IESG as a whole. 19 draft-iesg iesg-eva IESG Evaluation True The document is now (finally!) being formally reviewed by the entire IESG. Documents are discussed in email or during a bi-weekly IESG telechat. In this phase, each AD reviews the document and airs any issues they may have. Unresolvable issues are documented as "discuss" comments that can be forwarded to the authors/WG. See the description of substates for additional details about the current state of the IESG discussion. 20 draft-iesg defer IESG Evaluation - Defer True During a telechat, one or more ADs requested an additional 2 weeks to review the document. A defer is designed to be an exception mechanism, and can only be invoked once, the first time the document comes up for discussion during a telechat. 21 draft-iesg approved Approved-announcement to be sent True The IESG has approved the document for publication, but the Secretariat has not yet sent out on official approval message. 27 draft-iesg ann Approved-announcement sent True The IESG has approved the document for publication, and the Secretariat has sent out the official approval message to the RFC editor. 30 draft-iesg rfcqueue RFC Ed Queue True The document is in the RFC editor Queue (as confirmed by http://www.rfc-editor.org/queue.html). 31 draft-iesg pub RFC Published True The ID has been published as an RFC. 32 draft-iesg nopubadw DNP-waiting for AD note True Do Not Publish: The IESG recommends against publishing the document, but the writeup explaining its reasoning has not yet been produced. DNPs apply primarily to individual submissions received through the RFC editor. See the "note" field for more details on who has the action item. 33 draft-iesg nopubanw DNP-announcement to be sent True The IESG recommends against publishing the document, the writeup explaining its reasoning has been produced, but the Secretariat has not yet sent out the official "do not publish" recommendation message. 34 draft-iesg watching AD is watching True An AD is aware of the document and has chosen to place the document in a separate state in order to keep a closer eye on it (for whatever reason). Documents in this state are still not being actively tracked in the sense that no formal request has been made to publish or advance the document. The sole difference between this state and "I-D Exists" is that an AD has chosen to put it in a separate state, to make it easier to keep track of (for the AD's own reasons). 42 draft-iesg dead Dead True Document is "dead" and is no longer being tracked. (E.g., it has been replaced by another document with a different name, it has been withdrawn, etc.) 99 draft-rfceditor auth AUTH True Awaiting author action 0 draft-rfceditor auth48 AUTH48 True Awaiting final author approval 0 draft-rfceditor edit EDIT True Approved by the stream manager (e.g., IESG, IAB, IRSG, ISE), awaiting processing and publishing 0 draft-rfceditor iana-crd IANA True RFC-Editor/IANA Registration Coordination 0 draft-rfceditor iesg IESG True Holding for IESG action 0 draft-rfceditor isr ISR True Independent Submission Review by the ISE 0 draft-rfceditor isr-auth ISR-AUTH True Independent Submission awaiting author update, or in discussion between author and ISE 0 draft-rfceditor ref REF True Holding for normative reference 0 draft-rfceditor rfc-edit RFC-EDITOR True Awaiting final RFC Editor review before AUTH48 0 draft-rfceditor timeout TO True Time-out period during which the IESG reviews document for conflict/concurrence with other IETF working group work 0 draft-rfceditor missref MISSREF True Awaiting missing normative reference 0 draft-stream-iab candidat Candidate IAB Document True A document being considered for the IAB stream. 1 draft-stream-iab active Active IAB Document True This document has been adopted by the IAB and is being actively developed. 2 draft-stream-iab parked Parked IAB Document True This document has lost its author or editor, is waiting for another document to be written, or cannot currently be worked on by the IAB for some other reason. Annotations probably explain why this document is parked. 3 draft-stream-iab review-i IAB Review True This document is awaiting the IAB itself to come to internal consensus. 4 draft-stream-iab review-c Community Review True This document has completed internal consensus within the IAB and is now under community review. 5 draft-stream-iab approved Approved by IAB, To Be Sent to RFC Editor True The consideration of this document is complete, but it has not yet been sent to the RFC Editor for publication (although that is going to happen soon). 6 draft-stream-iab diff-org Sent to a Different Organization for Publication True The IAB does not expect to publish the document itself, but has passed it on to a different organization that might continue work on the document. The expectation is that the other organization will eventually publish the document. 7 draft-stream-iab rfc-edit Sent to the RFC Editor True The IAB processing of this document is complete and it has been sent to the RFC Editor for publication. The document may be in the RFC Editor's queue, or it may have been published as an RFC; this state doesn't distinguish between different states occurring after the document has left the IAB. 8 draft-stream-iab pub Published RFC True The document has been published as an RFC. 9 draft-stream-iab dead Dead IAB Document True This document was an active IAB document, but for some reason it is no longer being pursued for the IAB stream. It is possible that the document might be revived later, possibly in another stream. 10 draft-stream-ietf c-adopt Call For Adoption By WG Issued True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.1" target="_blank">4.2.1. Call for Adoption by WG Issued</a> The "Call for Adoption by WG Issued" state should be used to indicate when an I-D is being considered for adoption by an IETF WG. An I-D that is in this state is actively being considered for adoption and has not yet achieved consensus, preference, or selection in the WG. This state may be used to describe an I-D that someone has asked a WG to consider for adoption, if the WG Chair has agreed with the request. This state may also be used to identify an I-D that a WG Chair asked an author to write specifically for consideration as a candidate WG item [WGDTSPEC], and/or an I-D that is listed as a 'candidate draft' in the WG's charter. Under normal conditions, it should not be possible for an I-D to be in the "Call for Adoption by WG Issued" state in more than one working group at the same time. This said, it is not uncommon for authors to "shop" their I-Ds to more than one WG at a time, with the hope of getting their documents adopted somewhere. After this state is implemented in the Datatracker, an I-D that is in the "Call for Adoption by WG Issued" state will not be able to be "shopped" to any other WG without the consent of the WG Chairs and the responsible ADs impacted by the shopping. Note that Figure 1 includes an arc leading from this state to outside of the WG state machine. This illustrates that some I-Ds that are considered do not get adopted as WG drafts. An I-D that is not adopted as a WG draft will transition out of the WG state machine and revert back to having no stream-specific state; however, the status change history log of the I-D will record that the I-D was previously in the "Call for Adoption by WG Issued" state. 1 draft-stream-ietf adopt-wg Adopted by a WG True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.2" target="_blank">4.2.2. Adopted by a WG</a> The "Adopted by a WG" state describes an individual submission I-D that an IETF WG has agreed to adopt as one of its WG drafts. WG Chairs who use this state will be able to clearly indicate when their WGs adopt individual submission I-Ds. This will facilitate the Datatracker's ability to correctly capture "Replaces" information for WG drafts and correct "Replaced by" information for individual submission I-Ds that have been replaced by WG drafts. This state is needed because the Datatracker uses the filename of an I-D as a key to search its database for status information about the I-D, and because the filename of a WG I-D is supposed to be different from the filename of an individual submission I-D. The filename of an individual submission I-D will typically be formatted as 'draft-author-wgname-topic-nn'. The filename of a WG document is supposed to be formatted as 'draft- ietf-wgname-topic-nn'. An individual I-D that is adopted by a WG may take weeks or months to be resubmitted by the author as a new (version-00) WG draft. If the "Adopted by a WG" state is not used, the Datatracker has no way to determine that an I-D has been adopted until a new version of the I-D is submitted to the WG by the author and until the I-D is approved for posting by a WG Chair. 2 draft-stream-ietf info Adopted for WG Info Only True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.3" target="_blank">4.2.3. Adopted for WG Info Only</a> The "Adopted for WG Info Only" state describes a document that contains useful information for the WG that adopted it, but the document is not intended to be published as an RFC. The WG will not actively develop the contents of the I-D or progress it for publication as an RFC. The only purpose of the I-D is to provide information for internal use by the WG. 3 draft-stream-ietf wg-doc WG Document True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.4" target="_blank">4.2.4. WG Document</a> The "WG Document" state describes an I-D that has been adopted by an IETF WG and is being actively developed. A WG Chair may transition an I-D into the "WG Document" state at any time as long as the I-D is not being considered or developed in any other WG. Alternatively, WG Chairs may rely upon new functionality to be added to the Datatracker to automatically move version-00 drafts into the "WG Document" state as described in Section 4.1. Under normal conditions, it should not be possible for an I-D to be in the "WG Document" state in more than one WG at a time. This said, I-Ds may be transferred from one WG to another with the consent of the WG Chairs and the responsible ADs. 4 draft-stream-ietf parked Parked WG Document True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.5" target="_blank">4.2.5. Parked WG Document</a> A "Parked WG Document" is an I-D that has lost its author or editor, is waiting for another document to be written or for a review to be completed, or cannot be progressed by the working group for some other reason. Some of the annotation tags described in Section 4.3 may be used in conjunction with this state to indicate why an I-D has been parked, and/or what may need to happen for the I-D to be un-parked. Parking a WG draft will not prevent it from expiring; however, this state can be used to indicate why the I-D has stopped progressing in the WG. A "Parked WG Document" that is not expired may be transferred from one WG to another with the consent of the WG Chairs and the responsible ADs. 5 draft-stream-ietf dead Dead WG Document True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.6" target="_blank">4.2.6. Dead WG Document</a> A "Dead WG Document" is an I-D that has been abandoned. Note that 'Dead' is not always a final state for a WG I-D. If consensus is subsequently achieved, a "Dead WG Document" may be resurrected. A "Dead WG Document" that is not resurrected will eventually expire. Note that an I-D that is declared to be "Dead" in one WG and that is not expired may be transferred to a non-dead state in another WG with the consent of the WG Chairs and the responsible ADs. 6 draft-stream-ietf wg-lc In WG Last Call True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.7" target="_blank">4.2.7. In WG Last Call</a> A document "In WG Last Call" is an I-D for which a WG Last Call (WGLC) has been issued and is in progress. Note that conducting a WGLC is an optional part of the IETF WG process, per Section 7.4 of RFC 2418 [RFC2418]. If a WG Chair decides to conduct a WGLC on an I-D, the "In WG Last Call" state can be used to track the progress of the WGLC. The Chair may configure the Datatracker to send a WGLC message to one or more mailing lists when the Chair moves the I-D into this state. The WG Chair may also be able to select a different set of mailing lists for a different document undergoing a WGLC; some documents may deserve coordination with other WGs. A WG I-D in this state should remain "In WG Last Call" until the WG Chair moves it to another state. The WG Chair may configure the Datatracker to send an e-mail after a specified period of time to remind or 'nudge' the Chair to conclude the WGLC and to determine the next state for the document. It is possible for one WGLC to lead into another WGLC for the same document. For example, an I-D that completed a WGLC as an "Informational" document may need another WGLC if a decision is taken to convert the I-D into a Standards Track document. 7 draft-stream-ietf chair-w Waiting for WG Chair Go-Ahead True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.8" target="_blank">4.2.8. Waiting for WG Chair Go-Ahead</a> A WG Chair may wish to place an I-D that receives a lot of comments during a WGLC into the "Waiting for WG Chair Go-Ahead" state. This state describes an I-D that has undergone a WGLC; however, the Chair is not yet ready to call consensus on the document. If comments from the WGLC need to be responded to, or a revision to the I-D is needed, the Chair may place an I-D into this state until all of the WGLC comments are adequately addressed and the (possibly revised) document is in the I-D repository. 8 draft-stream-ietf writeupw WG Consensus: Waiting for Write-Up True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.9" target="_blank">4.2.9. WG Consensus: Waiting for Writeup</a> A document in the "WG Consensus: Waiting for Writeup" state has essentially completed its development within the working group, and is nearly ready to be sent to the IESG for publication. The last thing to be done is the preparation of a protocol writeup by a Document Shepherd. The IESG requires that a document shepherd writeup be completed before publication of the I-D is requested. The IETF document shepherding process and the role of a WG Document Shepherd is described in RFC 4858 [RFC4858] A WG Chair may call consensus on an I-D without a formal WGLC and transition an I-D that was in the "WG Document" state directly into this state. The name of this state includes the words "Waiting for Writeup" because a good document shepherd writeup takes time to prepare. 9 draft-stream-ietf sub-pub Submitted to IESG for Publication True <a href="http://tools.ietf.org/html/rfc6174#section-4.2.10" target="_blank">4.2.10. Submitted to IESG for Publication</a> This state describes a WG document that has been submitted to the IESG for publication and that has not been sent back to the working group for revision. An I-D in this state may be under review by the IESG, it may have been approved and be in the RFC Editor's queue, or it may have been published as an RFC. Other possibilities exist too. The document may be "Dead" (in the IESG state machine) or in a "Do Not Publish" state. 10 draft-stream-irtf candidat Candidate RG Document True This document is under consideration in an RG for becoming an IRTF document. A document in this state does not imply any RG consensus and does not imply any precedence or selection. It's simply a way to indicate that somebody has asked for a document to be considered for adoption by an RG. 1 draft-stream-irtf active Active RG Document True This document has been adopted by the RG and is being actively developed. 2 draft-stream-irtf parked Parked RG Document True This document has lost its author or editor, is waiting for another document to be written, or cannot currently be worked on by the RG for some other reason. 3 draft-stream-irtf rg-lc In RG Last Call True The document is in its final review in the RG. 4 draft-stream-irtf sheph-w Waiting for Document Shepherd True IRTF documents have document shepherds who help RG documents through the process after the RG has finished with the document. 5 draft-stream-irtf chair-w Waiting for IRTF Chair True The IRTF Chair is meant to be performing some task such as sending a request for IESG Review. 6 draft-stream-irtf irsg-w Awaiting IRSG Reviews True The document shepherd has taken the document to the IRSG and solicited reviews from one or more IRSG members. 7 draft-stream-irtf irsgpoll In IRSG Poll True The IRSG is taking a poll on whether or not the document is ready to be published. 8 draft-stream-irtf iesg-rev In IESG Review True The IRSG has asked the IESG to do a review of the document, as described in RFC5742. 9 draft-stream-irtf rfc-edit Sent to the RFC Editor True The RG processing of this document is complete and it has been sent to the RFC Editor for publication. The document may be in the RFC Editor's queue, or it may have been published as an RFC; this state doesn't distinguish between different states occurring after the document has left the RG. 10 draft-stream-irtf pub Published RFC True The document has been published as an RFC. 11 draft-stream-irtf iesghold Document on Hold Based On IESG Request True The IESG has requested that the document be held pending further review, as specified in RFC 5742, and the IRTF has agreed to such a hold. 12 draft-stream-irtf dead Dead IRTF Document True This document was an active IRTF document, but for some reason it is no longer being pursued for the IRTF stream. It is possible that the document might be revived later, possibly in another stream. 13 draft-stream-ise receive Submission Received True The draft has been sent to the ISE with a request for publication. 1 draft-stream-ise find-rev Finding Reviewers True The ISE is finding initial reviewers for the document. 2 draft-stream-ise ise-rev In ISE Review True The ISE is actively working on the document. 3 draft-stream-ise need-res Response to Review Needed True One or more reviews have been sent to the author, and the ISE is awaiting response. 4 draft-stream-ise iesg-rev In IESG Review True The ISE has asked the IESG to do a review of the document, as described in RFC5742. 5 draft-stream-ise rfc-edit Sent to the RFC Editor True The ISE processing of this document is complete and it has been sent to the RFC Editor for publication. The document may be in the RFC Editor's queue, or it may have been published as an RFC; this state doesn't distinguish between different states occurring after the document has left the ISE. 6 draft-stream-ise pub Published RFC True The document has been published as an RFC. 7 draft-stream-ise dead No Longer In Independent Submission Stream True This document was actively considered in the Independent Submission stream, but the ISE chose not to publish it. It is possible that the document might be revived later. A document in this state may have a comment explaining the reasoning of the ISE (such as if the document was going to move to a different stream). 8 draft-stream-ise iesghold Document on Hold Based On IESG Request True The IESG has requested that the document be held pending further review, as specified in RFC 5742, and the ISE has agreed to such a hold. 9 minutes active Active True 1 minutes deleted Deleted True 2 slides active Active True 1 slides deleted Deleted True 2 conflrev conflrev Approve Is this the correct conflict review response? True 0 charter r-extrev Ready for external review Is this charter ready for external review? True 1 draft approve Approve True 1 charter r-wo-ext Ready w/o external review Is this charter ready for external review? Is this charter ready for approval without external review? True 2 charter approve Approve Do we approve of this charter? True 3