This Evening's Technical plenary: RFC Editor Model
IAB Chair <iab-chair@ietf.org> Wed, 30 July 2008 12:48 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3BD33A688B; Wed, 30 Jul 2008 05:48:07 -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 73F123A6B60; Wed, 30 Jul 2008 05:48:02 -0700 (PDT)
From: IAB Chair <iab-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: This Evening's Technical plenary: RFC Editor Model
Mime-Version: 1.0
Message-Id: <20080730124803.73F123A6B60@core3.amsl.com>
Date: Wed, 30 Jul 2008 05:48:03 -0700
Cc: RFC Interests <rfc-interest@rfc-editor.org>, iab@iab.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
Colleagues, A few words about the plenary tonight. The technical plenary will open with the Host presentation and will feature a note from Eamon Ryan the Irish Minister for Communications, Energy and Natural Resources. During the IAB chair report there will be a pointer to work the IAB is doing on defining a model for the RFC Editor function. See http://www.iab.org/documents/resources/RFC-Editor-Model.html, and the discussion on the RFC-Interest list[1]. There is to little time to go into details, questions, and discussion tonight. Besides the discussion has an impact beyond the IETF interests. Therefore Russ will be asking the IETF to provide feedback on the model during the Thursday plenary. Russ will enumerate those questions below. Finally, and orthogonal to this issue, we may find ourselves running out of time for open-microphone this evening. If that happens the IAB will make itself available for questions tomorrow. --Olaf Kolkman IAB chair In my role as IETF Chair, I need to represent the IETF's view of the proposed RFC Editor model to the IAB. So, during the Thursday plenary there are several questions that need to be addressed: 1. What additional information, if any, is needed to form an opinion? 2. Are there any critical roles missing from the proposed RFC Editor model? 3. Are viable alternatives for the selection of the various roles, especially the RFC Editor and the Independent Stream Approver roles, in the proposed RFC Editor model missing? -- Russ Housley IETF Chair [1] http://mailman.rfc-editor.org/pipermail/rfc-interest/2008-May/000581.html _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce