Document Action: 'IETF Operational Notes' (RFC 4693) to Historic RFC
IESG Secretary <iesg-secretary@ietf.org> Wed, 31 August 2011 19:15 UTC
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 476A921F8F23; Wed, 31 Aug 2011 12:15:23 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Document Action: 'IETF Operational Notes' (RFC 4693) to Historic RFC
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110831191523.476A921F8F23@ietfa.amsl.com>
Date: Wed, 31 Aug 2011 12:15:23 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:15:23 -0000
The IESG has approved the following document: - 'IETF Operational Notes' RFC 4693 as a Historic RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Russ Housley. A URL of this RFC is: https://datatracker.ietf.org/doc/rfc4693/ Technical Summary This document describes a new document series (IONs) intended for use as a repository for IETF operations documents, which should be more ephemeral than RFCs, but more referenceable than internet-drafts, and with more clear handling procedures than a random Web page. It proposes to establish this series as an RFC 3933 process experiment. Working Group Summary During IETF Last Call, concern was expressed that ION documents must not be used to change matters of IETF process that require IETF consensus. This experiment doesn't change the IESG's authority, but it creates a systematic way to document procedural decisions. Text was added to clarify that IONs cannot override BCPs. The disposition of ION documents if the experiment is deemed a failure was clarified, as were other points questioned during Last Call. Finally, the IESG needs to affirm its support for the experiment. Protocol Quality Reviewed by Brian Carpenter
- Document Action: 'IETF Operational Notes' (RFC 46… IESG Secretary