IETF Stream Documents Require IETF Rough Consensus
draft-halpern-gendispatch-consensusinformational-04

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: draft-halpern-gendispatch-consensusinformational@ietf.org, The IESG <iesg@ietf.org>, rfc-editor@rfc-editor.org, caw@heapingbits.net, alissa@cooperw.in
Subject: Protocol Action: 'IETF Stream Documents Require IETF Rough Consensus' to Best Current Practice (draft-halpern-gendispatch-consensusinformational-04.txt)

The IESG has approved the following document:
- 'IETF Stream Documents Require IETF Rough Consensus'
  (draft-halpern-gendispatch-consensusinformational-04.txt) as Best Current
  Practice

This document has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG contact person is Alissa Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-halpern-gendispatch-consensusinformational/

Ballot Text

Technical Summary: 

This document updates RFC 2026 to prohibit the IETF from publishing any document, e.g., Informational or Experimental, without rough consensus.

Working Group Summary 

Yes, it was considered in GENDISPATCH, wherein participants urged this document towards AD sponsorship. There are no controversial points about this document.

Document Quality

Quality is fine.

Personnel

Christopher Wood is the document shepherd. Alissa Cooper is the responsible AD.

RFC Editor Note

RFC Editor Note

In the abstract please change "This document proposes" to "This document requires"