General Area open meeting (AD and session chair: Brian Carpenter)

Friday morning

09:00 Welcome, and introduction (Brian Carpenter)
09:10 IESG structure and charter*. (John Leslie)
09:40 WG Procedures**. (Margaret Wasserman)
10:10 Mailing list management procedures***. (Jim Galvin) 
      draft-galvin-maillists-00
10:40 Any other business, draft status      
      draft-alvestrand-ipod
      draft-klensin-norm-ref
      draft-narten-iana-considerations-rfc2434bis
      draft-narten-successful-bof
      draft-carpenter-ietf-disputes
      draft-carpenter-protocol-extensions
      others?
11:30 end

Note- discussion of this agenda can take place on ietf@ietf.org list.

============================
* IESG structure and charter
============================ 

RFC 3710 sets out an IESG Charter discussing the role and composition
of the Internet Engineering Steering Group (IESG), and touches on a few
procedural issues. However, it was intentionally published as an
Informational RFC to fill a known gap, without the overhead and formality
of a BCP.

Since RFC 3710 was published, the IESG has been asked to take on other
functions, notably to conduct IETF Process Experiments as outlined in
RFC 3933. Also, experience with RFC 3683 has shown "Revoking Posting
Rights" can be a significant drain. It now seems appropriate to refine and
adapt RFC 3710.
 
We believe it would be best to have a Charter representing IETF consensus,
published as a BCP. We propose to hold a mini-BoF in Montreal, and start
such a process.

It is not our intention to change the role, composition, or procedures of
the IESG: merely to document such portions of the role and composition of
the IESG as seem reasonably stable, leaving any matters of procedures for
another document.

We will propose a design-team approach, with private communication among
the team members and a public list to which drafts will be published and
anyone may post. Team members will attempt to respond to any comments that
bear on inaccuracies, inconsistencies, or clarity of documentation; but
may not always respond to suggestions for changes in the role, composition,
or procedures.

The design team should be chosen by the current IESG Chair, and should have
a roughly equal balance of former IESG members and persons who have not
served on the IESG. The team will communicate with current IESG members
before publishing each draft.

Proposed deliverables of the design team:
* Listing tasks that currently gate on the IESG;
* Documenting current time requirements of IESG members for these tasks;
* Identifying tasks which may not remain long-term IESG tasks;
* Identifying tasks which might be handled by IASA;
* Presenting an updated charter documenting the long-term-stable role and
  composition of the IESG for consideration as a BCP.

Agenda for the mini-BoF:
 1 minute    Agenda-bashing 
 4 minutes   Explain the proposal
 4+ minutes  Discussion: What belongs in the IESG Charter
 5+ minutes  Discussion: What belongs in a Design-Team charter
 1 minute    Hum: whether to proceed.

================
** WG Procedures
================

DESCRIPTION

  The IETF's Working Group procedures (BCP 25, RFC 2418) were
  published in 1998 and real procedures in many Working Groups have
  evolved beyond it, and it should be updated.  Also, there appears to
  be significant variation in how work is conducted in different
  Working Groups.

  In order to make sure that input is received from a number of WGs
  and points of view, a survey of WG procedures has been undertaken.
  This survey will be used in order to generate a summary of practical
  problems encountered in interpreting and implementing RFC 2418, and
  a summary of informal practices that have proved successful.

  The purpose of the mini-BOF is to review the status of the survey
  including results if available, present known issues with RFC 2485,
  discuss them, and plan next steps.

AGENDA

  - Background information.

  - Present as much of the survey results as available.

  - Discuss.

  - Known issues with RFC 2418.

  - Plan next steps.

======================================
*** Mailing list management procedures
======================================

INTRODUCTION

Charter is to develop a structure for managing IETF mailing lists. A document with a
proposed concept and some draft principles was distributed as an I-D to get the
discussion started.

The proposed process for progressing this work is to use the General Area open meetings
for discussion as needed, i.e., do not create a working group.  We will use a mailing
list for all substantive discussions.  One question to the room is whether or not a
working group is needed.

Goal is for a final draft document ready for IETF Last Call by Third IETF 2006.

AGENDA

A. Brief overview of document and concept

  Clarifying questions only.

B. Questions to the room

B.1. Is this an important work item for the IETF, independent of how you feel about 
the work being presented.  We should ask for those who object to the work item to 
speak first.

B.2. Does the outline presented represent a good starting point? We should ask for 
those who substantially object to the outline to speak first.

B.3. Do you agree we can progress this work using just a mailing list and the 
General Area open meeting?


ALL THOSE IN FAVOR HUM (i.e., all those opposed please speak up).

--