keyword_sprint resolution_fixed type_enhancement | by resnick@episteme.net
The Consensus field indicates whether the document will get the consensus template during the RFC Editor process. For IETF documents, this is determined by the IESG during document approval. Furthermore, for IETF documents, it is always the case that documents that are on the Standards Track or BCP are consensus documents. Two suggested changes:
-
Move the Consensus field out of the shepherd section and into the IESG section for IETF documents (along with IESG State, Responsible AD, etc.). I presume there is an equivalent area for non-IETF-stream documents. The same should be done there.
-
Fix the Consensus field to "Yes" if the document state gets set to "Proposed Standard", "Internet Standard", or "BCP". If the document changes from one of these to "Informational", "Experimental", or "Historic", make it editable and set the state to "Unknown".
Issue migrated from trac:1560 at 2022-03-04 03:57:42 +0000
keyword_sprintresolution_fixedtype_enhancement| by resnick@episteme.netThe Consensus field indicates whether the document will get the consensus template during the RFC Editor process. For IETF documents, this is determined by the IESG during document approval. Furthermore, for IETF documents, it is always the case that documents that are on the Standards Track or BCP are consensus documents. Two suggested changes:
Move the Consensus field out of the shepherd section and into the IESG section for IETF documents (along with IESG State, Responsible AD, etc.). I presume there is an equivalent area for non-IETF-stream documents. The same should be done there.
Fix the Consensus field to "Yes" if the document state gets set to "Proposed Standard", "Internet Standard", or "BCP". If the document changes from one of these to "Informational", "Experimental", or "Historic", make it editable and set the state to "Unknown".
Issue migrated from trac:1560 at 2022-03-04 03:57:42 +0000