RFC 4693 Experiment Conclusion

The IESG <iesg@ietf.org> Tue, 11 March 2008 14:39 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id C87A43A6E2F; Tue, 11 Mar 2008 07:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id eSIHKxxgDJCy; Tue, 11 Mar 2008 07:39:32 -0700 (PDT)
Received: from core3.amsl.com (localhost []) by core3.amsl.com (Postfix) with ESMTP id 802B228C39B; Tue, 11 Mar 2008 07:39:28 -0700 (PDT)
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 189163A6DD5; Tue, 11 Mar 2008 07:39:24 -0700 (PDT)
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: The IESG <iesg@ietf.org>
Subject: RFC 4693 Experiment Conclusion
Message-Id: <20080311143925.189163A6DD5@core3.amsl.com>
Date: Tue, 11 Mar 2008 07:39:25 -0700
Cc: iaoc@ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

The IETF Operational Notes (IONs) experiment has concluded.  The IESG  
has determined that IONs will not be used in the future.  It is clear  
that the IESG, IAB, and IAOC need the ability to publish documents  
that do not expire and are easily updated.  Information published as  
web pages, including IESG Statements, are sufficient for this  
purpose.  The IESG intends to employ some form of version control so  
that previous versions of IESG Statements will be available on line.

As specified in RFC 4693, the existing ION documents now have the  
same status as any other Web page or file on the IETF servers.   
Accordingly, the IONs that were developed during the experiment will  
be republished as follows:
  + ion-ad-sponsoring will be published as an IESG Statement
  + ion-agenda-and-minutes will be published as a web page
  + ion-discuss-criteria will be published as an IESG Statement
  + ion-ion-format will be discarded
  + ion-ion-store will be discarded
  + ion-procdocs will be published as a web page
  + ion-rfc-2026-in-practice has already been published as an I-D
  + ion-tsv-alt-cc will be published as an IESG Statement

The IESG has also recommended that the following documents be  
republished as IAOC web pages:
  + ion-execd-tasks
  + ion-meeting-network-requirements
  + ion-subpoena

The discussion on the appropriate type of document for the ion-discuss-
criteria will continue.  The decision that this particular ION become
an IESG Statement at this point in time is not intended to forecast the
outcome of this discussion; rather, it is a fulfillment of the statement
in RFC 4693, which says:

   If the IESG decides that the feedback warrants terminating the
   series, the repository will be closed for new documents, and the
   existing ION documents will be returned to having the same status as
   any other Web page or file on the IETF servers -- this situation will
   closely resemble the situation before the experiment started.

Much thanks to the ION authors and the people that provided comments
on the experiment.

On behalf of the IESG,
  Russ Housley

IETF-Announce mailing list