owner:rjsparks@nostrum.com resolution_fixed type_defect | by bclaise@cisco.com
The document shepherd set the consensus field to yes (*)
I want to set it back to unknown, but can't. Error message: this field
is required.
See
http://datatracker.ietf.org/doc/draft-ietf-ipfix-data-link-layer-monitoring/edit/consensus/ as an example.
(*) See message from Brian to the WG chairs:
All,
I want to make sure that all the WG chairs are aware of how the
"Consensus" field in the chairs' view of the datatracker is meant to be
used. That flag will be set by the AD once IETF consensus has been
reached on documents submitted for publication. It should not be set by
the document shepherd when there is WG consensus. Please refrain from
the burning temptation to set that field when you request publication of
a document. [Insert humorous smiley face here]
Regards,
Brian
Issue migrated from trac:1150 at 2022-03-04 02:59:24 +0000
owner:rjsparks@nostrum.comresolution_fixedtype_defect| by bclaise@cisco.comThe document shepherd set the consensus field to yes (*)
I want to set it back to unknown, but can't. Error message: this field
is required.
See
http://datatracker.ietf.org/doc/draft-ietf-ipfix-data-link-layer-monitoring/edit/consensus/ as an example.
(*) See message from Brian to the WG chairs:
All,
I want to make sure that all the WG chairs are aware of how the
"Consensus" field in the chairs' view of the datatracker is meant to be
used. That flag will be set by the AD once IETF consensus has been
reached on documents submitted for publication. It should not be set by
the document shepherd when there is WG consensus. Please refrain from
the burning temptation to set that field when you request publication of
a document. [Insert humorous smiley face here]
Regards,
Brian
Issue migrated from trac:1150 at 2022-03-04 02:59:24 +0000