Skip to main content

IETF Discussion List Charter
draft-eggert-bcp45bis-08

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: The IESG <iesg@ietf.org>, draft-eggert-bcp45bis@ietf.org, rfc-editor@rfc-editor.org, rwilton@cisco.com
Subject: Protocol Action: 'IETF Discussion List Charter' to Best Current Practice (draft-eggert-bcp45bis-08.txt)

The IESG has approved the following document:
- 'IETF Discussion List Charter'
  (draft-eggert-bcp45bis-08.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 Robert Wilton.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/


Ballot Text

Technical Summary

   The Internet Engineering Task Force (IETF) discussion mailing list
   furthers the development and specification of Internet technology
   through the general discussion of topics for which no dedicated
   mailing lists exists.  As this is the most general IETF mailing list,
   considerable latitude is allowed, but there are posts and topics that
   are unsuitable for this mailing list.

Working Group Summary

   This document was discussed in GENDISPATCH and then AD sponsored.
   There was discussion and improvements to the document both on the
   GENDISPATCH mailing list and during IETF LC.  I failed to explicitly cc
   ietf@ietf.org during the first IETF LC, so held a second last call on a
   updated version of the document that incorporated the review
   comments from the first review and received no further comments. 

Document Quality

   The document is short, easy to read, and well written, only covering
   IETF processes.  I believe that the document accurately describes
   the current expectations for subscribers of the main IETF mailing
   list.  The document has rough consensus.

Personnel

   Doc Shepherd and responsible AD for this document is Robert Wilton.

RFC Editor Note