Last Call: <draft-eggert-bcp45bis-07.txt> (IETF Discussion List Charter) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Mon, 10 January 2022 14:36 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-eggert-bcp45bis-07.txt> (IETF Discussion List Charter) to Best Current Practice
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-eggert-bcp45bis@ietf.org, rwilton@cisco.com, ietf@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <164182536443.26752.763615095887134371@ietfa.amsl.com>
Date: Mon, 10 Jan 2022 06:36:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/6rkVEiHRSDnYJUTXlbg0ZvSl7Sc>

Responsible AD note: I have asked for a second 4 week last call on this AD sponsored document for two reasons:
(1) I should have included ietf@ietf.org in the original last call notice because this mailing list is directly affected by this proposed BCP. Please note, as per the Reply-To, any last-call discussion should happen on last-call@ietf.org and not be automatically copied on ietf@ietf.org.
(2) Based on the last call feedback received, there have been some moderate changes to the draft during the last call process (between -06 and -07) and a second last call gives the community an opportunity to review and comment on those changes, and to ensure that there is community consensus to publish.

The IESG has received a request from an individual submitter to consider the
following document: - 'IETF Discussion List Charter'
<draft-eggert-bcp45bis-07.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-02-07. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract

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.

This document obsoletes RFC3005.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/

No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-eggert-bcp45bis-07.txt> (IETF D… The IESG