From ietf-nomcom-errors@lists.elistx.com Tue Aug  3 14:25:00 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1V00002UZ3KM@elistx.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Tue,
 03 Aug 2004 14:21:03 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1V00001UZ2KL@elistx.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 03 Aug 2004 14:21:02 -0400 (EDT)
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1V00002UZ2K6@elistx.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Tue, 03 Aug 2004 14:21:02 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1V00001UYZK4@elistx.com> for ietf-nomcom@lists.elistx.com; Tue,
 03 Aug 2004 14:20:59 -0400 (EDT)
Received: from localhost (one.elistx.com [209.116.252.130])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1V00055UYZD2@elistx.com>
 for ietf-nomcom@lists.elistx.com; Tue, 03 Aug 2004 14:20:59 -0400 (EDT)
Date: Tue, 03 Aug 2004 14:20:01 -0400 (EDT)
From: James M Galvin <galvin@elistx.com>
Subject: BCP 10, RFC 3777 on IAB and IESG Selection, Confirmation,
 and Recall Process: Operation of the Nominating and Recall Committees (fwd)
To: ietf-nomcom@lists.elistx.com
Message-id: <Pine.BSF.4.43.0408031419420.5338-220000@three.elistx.com>
Content-id: <Pine.BSF.4.43.0408031419421.5338@three.elistx.com>
MIME-version: 1.0
Content-type: MULTIPART/Mixed; BOUNDARY=NextPart
X-Virus-Scanned-At: eList eXpress <http://www.elistx.com/>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


--NextPart
Content-id: <Pine.BSF.4.43.0408031419422.5338@three.elistx.com>
Content-type: TEXT/PLAIN; CHARSET=US-ASCII



---------- Forwarded message ----------
Date: Wed, 16 Jun 2004 13:30:20 -0700
From: rfc-editor@rfc-editor.org
To: IETF-Announce:  ;
Cc: ietf-nomcom@lists.elistx.com, rfc-editor@rfc-editor.org
Subject: BCP 10, RFC 3777 on IAB and IESG Selection, Confirmation,
     and Recall Process: Operation of the Nominating and Recall Committees


A new Request for Comments is now available in online RFC libraries.


        BCP 10
        RFC 3777

        Title:      IAB and IESG Selection, Confirmation, and Recall
                    Process: Operation of the Nominating and Recall
                    Committees
        Author(s):  J. Galvin, Ed.
        Status:     Best Current Practice
        Date:       June 2004
        Mailbox:    galvin+ietf@elistx.com
        Pages:      34
        Characters: 76395
        Obsoletes:  2727
        SeeAlso:    BCP 10

        I-D Tag:    draft-ietf-nomcom-rfc2727bis-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3777.txt


The process by which the members of the IAB and IESG are selected,
confirmed, and recalled is specified.  This document is a
self-consistent, organized compilation of the process as it was known
at the time of publication.

This document is a product of the Operation of the IESG/IAB
Nominating and Recall Committees Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

--NextPart
Content-description: 
Content-id: <Pine.BSF.4.43.0408031419423.5338@three.elistx.com>
Content-type: MULTIPART/ALTERNATIVE; BOUNDARY=OtherAccess


--NextPart
Content-description: 
Content-id: <Pine.BSF.4.43.0408031419426.5338@three.elistx.com>
Content-type: TEXT/PLAIN; CHARSET=us-ascii

_______________________________________________

IETF-Announce mailing list

IETF-Announce@ietf.org

https://www1.ietf.org/mailman/listinfo/ietf-announce


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

--NextPart--
Content-id: <Pine.BSF.4.43.0408031419424.5338@three.elistx.com>
Content-type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="RFC-INFO@RFC-EDITOR.ORG"

Content-id: <Pine.BSF.4.43.0408031419425.5338@three.elistx.com>
Content-type: MESSAGE/EXTERNAL-BODY; NAME="rfc3777.txt"; SITE="ftp.isi.edu"; ACCESS-TYPE=anon-ftp; DIRECTORY=in-notes


From ietf-nomcom-errors@lists.elistx.com Tue Aug  3 14:25:07 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1V00002V14OO@elistx.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Tue,
 03 Aug 2004 14:22:16 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1V00001V13ON@elistx.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 03 Aug 2004 14:22:15 -0400 (EDT)
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1V00002V13OH@elistx.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Tue, 03 Aug 2004 14:22:15 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1V00001V13OG@elistx.com> for ietf-nomcom@lists.elistx.com; Tue,
 03 Aug 2004 14:22:15 -0400 (EDT)
Received: from localhost (one.elistx.com [209.116.252.130])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1V0006RV12D2@elistx.com>
 for ietf-nomcom@lists.elistx.com; Tue, 03 Aug 2004 14:22:15 -0400 (EDT)
Date: Tue, 03 Aug 2004 14:21:16 -0400 (EDT)
From: James M Galvin <galvin@elistx.com>
Subject: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
To: ietf-nomcom@lists.elistx.com
Message-id: <Pine.BSF.4.43.0408031420380.5338-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>



---------- Forwarded message ----------
Date: Tue, 03 Aug 2004 13:45:03 -0400
From: The IESG <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Cc: ietf-nomcom@lists.elistx.com, Avri Doria <avri@acm.org>
Subject: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
    Nominating and Recall Committees (nomcom)

The Operation of the IESG/IAB Nominating and Recall Committees (nomcom) working
group in the General Area has concluded.

The IESG contact person is Harald Alvestrand.

The mailing list will be closed.

+++

With the publication of RFC 3777, "IAB and IESG Selection, Confirmation,
and Recall Process: Operation of the Nominating and Recall Committees", the
work of the NOMCOM working group is finished.

On behalf of the community, this AD wishes to thank the group members, the
editor and the working group chair for their many hours of hard work and
dedication to a task well completed.

Thank you!

Harald Alvestrand


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Tue Aug  3 14:45:01 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1V00202VUNH1@elistx.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Tue,
 03 Aug 2004 14:39:59 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1V00201VUNH0@elistx.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 03 Aug 2004 14:39:59 -0400 (EDT)
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1V00202VUNGU@elistx.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Tue, 03 Aug 2004 14:39:59 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1V00201VUMGT@elistx.com> for ietf-nomcom@lists.elistx.com; Tue,
 03 Aug 2004 14:39:58 -0400 (EDT)
Received: from localhost (one.elistx.com [209.116.252.130])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1V001AXVULG0@elistx.com>
 for ietf-nomcom@lists.elistx.com; Tue, 03 Aug 2004 14:39:58 -0400 (EDT)
Date: Tue, 03 Aug 2004 14:38:59 -0400 (EDT)
From: James M Galvin <galvin@elistx.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
In-reply-to: <Pine.BSF.4.43.0408031420380.5338-100000@three.elistx.com>
To: ietf-nomcom@lists.elistx.com
Message-id: <Pine.BSF.4.43.0408031425360.5338-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

With the conclusion of the working group, I will be closing down the
mailing list.

I'll wait a week to do this since this is the week of the IETF, just in
case anyone has any last minute comments or questions.

The archive will remain available essentially indefinitely.

Jim


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Tue Aug  3 17:05:06 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1W00C022K5K8@elistx.com>
 (original mail from brc@zurich.ibm.com); Tue, 03 Aug 2004 17:04:53 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1W00C012K4K7@elistx.com> for ietf-nomcom@lists.elistx.com; Tue,
 03 Aug 2004 17:04:52 -0400 (EDT)
Received: from mtagate4.de.ibm.com (mtagate4.de.ibm.com [195.212.29.153])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1W00BAC2K3NB@elistx.com>
 for ietf-nomcom@lists.elistx.com; Tue, 03 Aug 2004 17:04:52 -0400 (EDT)
Received: from d12nrmr1507.megacenter.de.ibm.com
 (d12nrmr1507.megacenter.de.ibm.com [9.149.167.1])
 by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id i73L4d69077788	for
 <ietf-nomcom@lists.elistx.com>; Tue, 03 Aug 2004 21:04:39 +0000 (GMT)
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
 by d12nrmr1507.megacenter.de.ibm.com (8.12.10/NCO/VER6.6)
 with ESMTP id i73L4dGi063964	for <ietf-nomcom@lists.elistx.com>; Tue,
 03 Aug 2004 23:04:39 +0200
Received: from zurich.ibm.com (sig-9-145-228-220.de.ibm.com [9.145.228.220])
 by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id XAA77968	for
 <ietf-nomcom@lists.elistx.com>; Tue, 03 Aug 2004 23:04:38 +0200
Date: Tue, 03 Aug 2004 23:04:36 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: BCP 10, RFC 3777 on IAB and IESG Selection, Confirmation,
 and Recall Process: Operation of the Nominating and Recall Committees (fwd)
In-reply-to: <Pine.BSF.4.43.0408031419420.5338-220000@three.elistx.com>
To: ietf-nomcom@lists.elistx.com
Message-id: <410FFDE4.9060906@zurich.ibm.com>
Organization: IBM
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
X-Accept-Language: en, fr, de
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
 Gecko/20040113
References: <Pine.BSF.4.43.0408031419420.5338-220000@three.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Although the RFC is published and the WG officially closed,
I have to mention a hole that we accidentally left. It wasn't
possible to mention this before today, to avoid interfering
with the active process.

The RFC says:

>    5.  The Internet Society President appoints the Chair, who must meet
>        the same requirements for membership in the nominating committee
>        as a voting volunteer.

We say nothing about how the ISOC President picks the Nomcom Chair.
In the past, ISOC had a VP for Standards and the ISOC President asked
this VP for advice. Today, ISOC has no VP for Standards, but does have
IETF appointees on its Board. I happen to know that this year there
was some confusion about where the ISOC President should seek advice
about names to put on the short list. Since the members of the
IESG and IAB have an interest in the outcome of the Nomcom, it seems
clear that they shouldn't be the unique source of advice.

Whenever we do RFC 3777bis, we probably need to add a few words
clarifying that the ISOC President takes advice where s/he sees fit.

The same would apply to the appointment of an arbiter and to the
chair of a recall committee.

     Brian


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Tue Aug  3 17:15:01 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1W00C022NEUJ@elistx.com>
 (original mail from brc@zurich.ibm.com); Tue, 03 Aug 2004 17:06:50 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1W00C012NDUH@elistx.com> for ietf-nomcom@lists.elistx.com; Tue,
 03 Aug 2004 17:06:49 -0400 (EDT)
Received: from mtagate2.de.ibm.com (mtagate2.de.ibm.com [195.212.29.151])
 by elistx.com (PMDF V6.0-025 #44856)
 with ESMTP id <0I1W00BBH2NCNB@elistx.com>; Tue,
 03 Aug 2004 17:06:49 -0400 (EDT)
Received: from d12nrmr1607.megacenter.de.ibm.com
 (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
 by mtagate2.de.ibm.com (8.12.10/8.12.10) with ESMTP id i73L6agB035862; Tue,
 03 Aug 2004 21:06:36 +0000 (GMT)
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
 by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.6)
 with ESMTP id i73L6Zit186382; Tue, 03 Aug 2004 23:06:35 +0200
Received: from zurich.ibm.com (sig-9-145-228-220.de.ibm.com [9.145.228.220])
 by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id XAA87634; Tue,
 03 Aug 2004 23:06:34 +0200
Date: Tue, 03 Aug 2004 23:06:32 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
In-reply-to: <Pine.BSF.4.43.0408031425360.5338-100000@three.elistx.com>
To: James M Galvin <galvin@elistx.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <410FFE58.4060303@zurich.ibm.com>
Organization: IBM
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
X-Accept-Language: en, fr, de
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
 Gecko/20040113
References: <Pine.BSF.4.43.0408031425360.5338-100000@three.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Why? The normal convention is to keep the mailing list open
in case issues come up that might justify new activity.

(As I'm afraid one already did.)

    Brian

James M Galvin wrote:
> With the conclusion of the working group, I will be closing down the
> mailing list.
> 
> I'll wait a week to do this since this is the week of the IETF, just in
> case anyone has any last minute comments or questions.
> 
> The archive will remain available essentially indefinitely.
> 
> Jim
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.elistx.com/subscribe>
> 

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Tue Aug  3 22:05:07 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1W00C02GE7TX@elistx.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Tue,
 03 Aug 2004 22:03:43 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1W00C01GE6TW@elistx.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 03 Aug 2004 22:03:43 -0400 (EDT)
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1W00C02GE6TQ@elistx.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Tue, 03 Aug 2004 22:03:42 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1W00C01GE6TO@elistx.com> for ietf-nomcom@lists.elistx.com; Tue,
 03 Aug 2004 22:03:42 -0400 (EDT)
Received: from localhost (one.elistx.com [209.116.252.130])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1W009JSGE5NO@elistx.com>
 for ietf-nomcom@lists.elistx.com; Tue, 03 Aug 2004 22:03:42 -0400 (EDT)
Date: Tue, 03 Aug 2004 22:02:42 -0400 (EDT)
From: James M Galvin <galvin@elistx.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
In-reply-to: <410FFE58.4060303@zurich.ibm.com>
To: Brian E Carpenter <brc@zurich.ibm.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <Pine.BSF.4.43.0408032148570.5837-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

I didn't make the decision to close down the list, although I agree with
it.  My primary reason for agreeing with it is related to hosting the
list.  The list address is one of the single greatest magnets for spam
on my server.  It ranks right up there with every other IETF list I
host.  I'm sure others who host IETF lists have similar statistics.


Setting that aside, the list associated with every other NOMCOM revision
has closed when that work was completed, i.e., when the working group
closed.  Personally, I like this model.

When a working group closes it's mailing list should end also.  The
purpose of the list is to support the work of the working group.
Without a working group there's no one in charge of the list.  And in
today's email environment that's just unacceptable.

If a standard needs a "deployment" mailing list then let someone sponsor
it, i.e., be in charge of it and arrange for it to get hosted.  It is
consistent with my model for someone to volunteer to be in charge of an
existing list and voluteer to keep it active.  Absent that, no working
group, no list.

Just my opinion of course.


As to what to do with "new" issues that come up, perhaps that is a
problem that needs to be considered in a larger context.  One suggestion
is to check with the author and see if that person is keeping track.

Perhaps the IETF needs a "tool" for collecting suggestions/comments
about its documents so they can be considered during its next revision.
A blog might be good for this.

Jim







On Tue, 3 Aug 2004, Brian E Carpenter wrote:

    Date: Tue, 03 Aug 2004 23:06:32 +0200
    From: Brian E Carpenter <brc@zurich.ibm.com>
    To: James M Galvin <galvin@elistx.com>
    Cc: ietf-nomcom@lists.elistx.com
    Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the
        IESG/IAB Nominating and Recall Committees (nomcom) (fwd)

    Why? The normal convention is to keep the mailing list open
    in case issues come up that might justify new activity.

    (As I'm afraid one already did.)

        Brian

    James M Galvin wrote:
    > With the conclusion of the working group, I will be closing down the
    > mailing list.
    >
    > I'll wait a week to do this since this is the week of the IETF, just in
    > case anyone has any last minute comments or questions.
    >
    > The archive will remain available essentially indefinitely.
    >
    > Jim


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Wed Aug  4 01:25:01 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1W00102PK2A3@elistx.com>
 (original mail from jwkckid1@ix.netcom.com); Wed,
 04 Aug 2004 01:21:38 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1W00101PK2A1@elistx.com> for ietf-nomcom@lists.elistx.com; Wed,
 04 Aug 2004 01:21:38 -0400 (EDT)
Received: from tisch.mail.mindspring.net
 (tisch.mail.mindspring.net [207.69.200.157])
 by elistx.com (PMDF V6.0-025 #44856)
 with ESMTP id <0I1W00IO9PK1O4@elistx.com>; Wed,
 04 Aug 2004 01:21:38 -0400 (EDT)
Received: from 1cust205.tnt36.dfw9.da.uu.net
 ([67.234.81.205] helo=ix.netcom.com)	by tisch.mail.mindspring.net with esmtp
 (Exim 3.33 #1)	id 1BsEDO-0006oI-00; Wed, 04 Aug 2004 01:21:26 -0400
Date: Wed, 04 Aug 2004 00:08:51 -0700
From: Jeff Williams <jwkckid1@ix.netcom.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
To: James M Galvin <galvin@elistx.com>
Cc: Brian E Carpenter <brc@zurich.ibm.com>, ietf-nomcom@lists.elistx.com
Message-id: <41108B81.9A2D1238@ix.netcom.com>
Organization: INEGroup Spokesman
MIME-version: 1.0
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
Content-type: text/plain; charset=us-ascii
References: <Pine.BSF.4.43.0408032148570.5837-100000@three.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

James and all,

  If the IETF or you would consider implementing Spf correctly, the
spam would be greatly reduced.

James M Galvin wrote:

> I didn't make the decision to close down the list, although I agree with
> it.  My primary reason for agreeing with it is related to hosting the
> list.  The list address is one of the single greatest magnets for spam
> on my server.  It ranks right up there with every other IETF list I
> host.  I'm sure others who host IETF lists have similar statistics.
>
> Setting that aside, the list associated with every other NOMCOM revision
> has closed when that work was completed, i.e., when the working group
> closed.  Personally, I like this model.
>
> When a working group closes it's mailing list should end also.  The
> purpose of the list is to support the work of the working group.
> Without a working group there's no one in charge of the list.  And in
> today's email environment that's just unacceptable.
>
> If a standard needs a "deployment" mailing list then let someone sponsor
> it, i.e., be in charge of it and arrange for it to get hosted.  It is
> consistent with my model for someone to volunteer to be in charge of an
> existing list and voluteer to keep it active.  Absent that, no working
> group, no list.
>
> Just my opinion of course.
>
> As to what to do with "new" issues that come up, perhaps that is a
> problem that needs to be considered in a larger context.  One suggestion
> is to check with the author and see if that person is keeping track.
>
> Perhaps the IETF needs a "tool" for collecting suggestions/comments
> about its documents so they can be considered during its next revision.
> A blog might be good for this.
>
> Jim
>
> On Tue, 3 Aug 2004, Brian E Carpenter wrote:
>
>     Date: Tue, 03 Aug 2004 23:06:32 +0200
>     From: Brian E Carpenter <brc@zurich.ibm.com>
>     To: James M Galvin <galvin@elistx.com>
>     Cc: ietf-nomcom@lists.elistx.com
>     Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the
>         IESG/IAB Nominating and Recall Committees (nomcom) (fwd)
>
>     Why? The normal convention is to keep the mailing list open
>     in case issues come up that might justify new activity.
>
>     (As I'm afraid one already did.)
>
>         Brian
>
>     James M Galvin wrote:
>     > With the conclusion of the working group, I will be closing down the
>     > mailing list.
>     >
>     > I'll wait a week to do this since this is the week of the IETF, just in
>     > case anyone has any last minute comments or questions.
>     >
>     > The archive will remain available essentially indefinitely.
>     >
>     > Jim
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.elistx.com/subscribe>

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard

"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing  (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security
IDNS. div. of Information Network Eng.  INEG. INC.
E-Mail jwkckid1@ix.netcom.com
 Registered Email addr with the USPS
Contact Number: 214-244-4827



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Wed Aug  4 08:55:08 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1X00F02AACIC@elistx.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Wed,
 04 Aug 2004 08:49:24 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1X00F01AABIB@elistx.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Wed, 04 Aug 2004 08:49:23 -0400 (EDT)
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1X00F02AABI5@elistx.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Wed, 04 Aug 2004 08:49:23 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1X00F01AAAI4@elistx.com> for ietf-nomcom@lists.elistx.com; Wed,
 04 Aug 2004 08:49:22 -0400 (EDT)
Received: from localhost (one.elistx.com [209.116.252.130])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1X00E4XAA9IX@elistx.com>
 for ietf-nomcom@lists.elistx.com; Wed, 04 Aug 2004 08:49:22 -0400 (EDT)
Date: Wed, 04 Aug 2004 08:48:20 -0400 (EDT)
From: James M Galvin <galvin@elistx.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
In-reply-to: <41108B81.9A2D1238@ix.netcom.com>
To: ietf-nomcom@lists.elistx.com
Message-id: <Pine.BSF.4.43.0408040844250.6506-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Well, I disagree, but this is not the place to debate the merits of
SPF or any other spam reducing tool.

Jim



On Wed, 4 Aug 2004, Jeff Williams wrote:

    Date: Wed, 04 Aug 2004 00:08:51 -0700
    From: Jeff Williams <jwkckid1@ix.netcom.com>
    To: James M Galvin <galvin@elistx.com>
    Cc: Brian E Carpenter <brc@zurich.ibm.com>, ietf-nomcom@lists.elistx.com
    Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the
        IESG/IAB Nominating and Recall Committees (nomcom) (fwd)

    James and all,

      If the IETF or you would consider implementing Spf correctly, the
    spam would be greatly reduced.


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Wed Aug  4 12:35:10 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1X00E02KDFLL@elistx.com>
 (original mail from brc@zurich.ibm.com); Wed, 04 Aug 2004 12:27:15 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1X00E01KDELJ@elistx.com> for ietf-nomcom@lists.elistx.com; Wed,
 04 Aug 2004 12:27:14 -0400 (EDT)
Received: from mtagate4.de.ibm.com (mtagate4.de.ibm.com [195.212.29.153])
 by elistx.com (PMDF V6.0-025 #44856)
 with ESMTP id <0I1X00D2IKDDTX@elistx.com>; Wed,
 04 Aug 2004 12:27:14 -0400 (EDT)
Received: from d12nrmr1607.megacenter.de.ibm.com
 (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
 by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id i74GR269121398; Wed,
 04 Aug 2004 16:27:02 +0000 (GMT)
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
 by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.6)
 with ESMTP id i74GR10k188632; Wed, 04 Aug 2004 18:27:01 +0200
Received: from zurich.ibm.com (sig-9-145-228-27.de.ibm.com [9.145.228.27])
 by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id SAA51688; Wed,
 04 Aug 2004 18:26:59 +0200
Date: Wed, 04 Aug 2004 18:26:57 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
In-reply-to: <Pine.BSF.4.43.0408032148570.5837-100000@three.elistx.com>
To: James M Galvin <galvin@elistx.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <41110E51.7030801@zurich.ibm.com>
Organization: IBM
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
X-Accept-Language: en, fr, de
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
 Gecko/20040113
References: <Pine.BSF.4.43.0408032148570.5837-100000@three.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Jim,

Firstly I'm very sensitive to the spam magnet issue. In fact, when
the diffserv WG closed down, we killed its list for exactly that
reason, *but* activated a new list for continued discussion.

I don't see why nomcom is different from a technical topic - there
will inevitably be (hopefully minor) issues. But there is no
reason I would ever think to go to look at a web log just in case
something had been posted.

This isn't my call, but I believe the inevitable result will be
that any issues end up being debated on ietf@ietf.org, which
I don't think is optimal.

And I do think this needs to be clarified in IETF WG procedures,
but that is not a debate for this soon-to-be-ex-list.

      Brian

James M Galvin wrote:
> I didn't make the decision to close down the list, although I agree with
> it.  My primary reason for agreeing with it is related to hosting the
> list.  The list address is one of the single greatest magnets for spam
> on my server.  It ranks right up there with every other IETF list I
> host.  I'm sure others who host IETF lists have similar statistics.
> 
> 
> Setting that aside, the list associated with every other NOMCOM revision
> has closed when that work was completed, i.e., when the working group
> closed.  Personally, I like this model.
> 
> When a working group closes it's mailing list should end also.  The
> purpose of the list is to support the work of the working group.
> Without a working group there's no one in charge of the list.  And in
> today's email environment that's just unacceptable.
> 
> If a standard needs a "deployment" mailing list then let someone sponsor
> it, i.e., be in charge of it and arrange for it to get hosted.  It is
> consistent with my model for someone to volunteer to be in charge of an
> existing list and voluteer to keep it active.  Absent that, no working
> group, no list.
> 
> Just my opinion of course.
> 
> 
> As to what to do with "new" issues that come up, perhaps that is a
> problem that needs to be considered in a larger context.  One suggestion
> is to check with the author and see if that person is keeping track.
> 
> Perhaps the IETF needs a "tool" for collecting suggestions/comments
> about its documents so they can be considered during its next revision.
> A blog might be good for this.
> 
> Jim
> 
> 
> 
> 
> 
> 
> 
> On Tue, 3 Aug 2004, Brian E Carpenter wrote:
> 
>     Date: Tue, 03 Aug 2004 23:06:32 +0200
>     From: Brian E Carpenter <brc@zurich.ibm.com>
>     To: James M Galvin <galvin@elistx.com>
>     Cc: ietf-nomcom@lists.elistx.com
>     Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the
>         IESG/IAB Nominating and Recall Committees (nomcom) (fwd)
> 
>     Why? The normal convention is to keep the mailing list open
>     in case issues come up that might justify new activity.
> 
>     (As I'm afraid one already did.)
> 
>         Brian
> 
>     James M Galvin wrote:
>     > With the conclusion of the working group, I will be closing down the
>     > mailing list.
>     >
>     > I'll wait a week to do this since this is the week of the IETF, just in
>     > case anyone has any last minute comments or questions.
>     >
>     > The archive will remain available essentially indefinitely.
>     >
>     > Jim
> 

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Wed Aug  4 18:05:00 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1X00D02ZYR5D@elistx.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Wed,
 04 Aug 2004 18:04:03 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1X00D01ZYR5C@elistx.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Wed, 04 Aug 2004 18:04:03 -0400 (EDT)
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1X00D02ZYR56@elistx.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Wed, 04 Aug 2004 18:04:03 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1X00D01ZYQ54@elistx.com> for ietf-nomcom@lists.elistx.com; Wed,
 04 Aug 2004 18:04:02 -0400 (EDT)
Received: from localhost (one.elistx.com [209.116.252.130])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1X00CBXZYQF4@elistx.com>
 for ietf-nomcom@lists.elistx.com; Wed, 04 Aug 2004 18:04:02 -0400 (EDT)
Date: Wed, 04 Aug 2004 18:03:00 -0400 (EDT)
From: James M Galvin <galvin@elistx.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
In-reply-to: <41110E51.7030801@zurich.ibm.com>
To: Brian E Carpenter <brc@zurich.ibm.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <Pine.BSF.4.43.0408041756480.6964-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


On Wed, 4 Aug 2004, Brian E Carpenter wrote:

    Firstly I'm very sensitive to the spam magnet issue. In fact, when
    the diffserv WG closed down, we killed its list for exactly that
    reason, *but* activated a new list for continued discussion.

How is the pointer to this new list managed?  A working group's list is
normally referenced in its charter.  Even when it closes the old charter
is around or at least references to the old list are "around".

How does one make the "community" aware of the new list?

I am willing to keep the list active or provide a "new" list, if that's
what folks want to do.  I'm offering so we can see if folks want to
speak up in favor of it.  So far, I'm not sensing a "consensus" of
opposition to closing the list, although that's really for the Chair to
say.

Jim


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Wed Aug  4 19:25:14 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1Y00I023CRGB@elistx.com>
 (original mail from avri@acm.org); Wed, 04 Aug 2004 19:17:15 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1Y00I013CRGA@elistx.com> for ietf-nomcom@lists.elistx.com; Wed,
 04 Aug 2004 19:17:15 -0400 (EDT)
Received: from report.tla-group.com (tla.crepundia.net [194.71.127.149])
 by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0I1Y00HGV3CQTE@elistx.com>
 for ietf-nomcom@lists.elistx.com; Wed, 04 Aug 2004 19:17:15 -0400 (EDT)
Received: from [127.0.0.1] (report.tla-group.com [194.71.127.149])
 by report.tla-group.com (8.12.4/8.12.4) with ESMTP id i74N43ep027474	for
 <ietf-nomcom@lists.elistx.com>; Thu, 05 Aug 2004 01:04:08 +0200
Date: Wed, 04 Aug 2004 16:16:44 -0700
From: avri@acm.org
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
In-reply-to: <Pine.BSF.4.43.0408041756480.6964-100000@three.elistx.com>
To: ietf-nomcom@lists.elistx.com
Message-id: <59C0363C-E66C-11D8-B3D0-000393CC2112@acm.org>
MIME-version: 1.0 (Apple Message framework v618)
X-Mailer: Apple Mail (2.618)
Content-type: text/plain; format=flowed; charset=US-ASCII
References: <Pine.BSF.4.43.0408041756480.6964-100000@three.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


On 4 aug 2004, at 15.03, James M Galvin wrote:

>
> I am willing to keep the list active or provide a "new" list, if that's
> what folks want to do.  I'm offering so we can see if folks want to
> speak up in favor of it.  So far, I'm not sensing a "consensus" of
> opposition to closing the list, although that's really for the Chair to
> say.

I assume you mean the "General Area AD to say."  The group no longer 
exists and thus no longer has a chair only and ex-chair.  The General 
Area Ad has requested the list be closed and I expect any decision to 
keep it open would be his decision as well.

As an individual who is very interested in NomCom I have no objection 
to there being a list for ongoing discussions and would join such a 
list.  I would even be willing to help administer such a list.

As chair, I had to curtail discussions, because of the charter, of 
radical changes one could have suggested to the IETF process for 
picking its leadership even though I knew there were those who had such 
an interest.  As an individual I think it might be interesting to have 
a space where radical revisions could be discussed by those who desired 
to do so.

a.

PS. As the ex-chair I thank everyone on this list for their 
participation in the WG.  I enjoyed working with all.


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Thu Aug  5 02:15:02 2004
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com
 (PMDF V6.0-025 #44856) id <0I1Y00102MNP3E@elistx.com>
 (original mail from jwkckid1@ix.netcom.com); Thu,
 05 Aug 2004 02:14:13 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856)
 id <0I1Y00101MNN3B@elistx.com> for ietf-nomcom@lists.elistx.com; Thu,
 05 Aug 2004 02:14:12 -0400 (EDT)
Received: from barry.mail.mindspring.net
 (barry.mail.mindspring.net [207.69.200.25])
 by elistx.com (PMDF V6.0-025 #44856)
 with ESMTP id <0I1Y00KE6MNIA0@elistx.com>; Thu,
 05 Aug 2004 02:14:11 -0400 (EDT)
Received: from 1cust121.tnt36.dfw9.da.uu.net
 ([67.234.81.121] helo=ix.netcom.com)	by barry.mail.mindspring.net with esmtp
 (Exim 3.33 #1)	id 1BsbVh-0005Ss-00; Thu, 05 Aug 2004 02:13:54 -0400
Date: Thu, 05 Aug 2004 01:01:16 -0700
From: Jeff Williams <jwkckid1@ix.netcom.com>
Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the IESG/IAB
 Nominating and Recall Committees (nomcom) (fwd)
To: James M Galvin <galvin@elistx.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <4111E94A.21B889D6@ix.netcom.com>
Organization: INEGroup Spokesman
MIME-version: 1.0
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
Content-type: text/plain; charset=us-ascii
References: <Pine.BSF.4.43.0408040844250.6506-100000@three.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Jim and all,

  I wasn't offering a debate, only stating a good suggestion.  Of course
other methods could be deployed...  SPF merits speak for themselves
and are well known...  Hence your right no need for discussion of them
here.  Solving the "Spam Magnet" aspect of this or any replacement
forum for this one IS.  Hence my suggestion in the first place...

James M Galvin wrote:

> Well, I disagree, but this is not the place to debate the merits of
> SPF or any other spam reducing tool.
>
> Jim
>
> On Wed, 4 Aug 2004, Jeff Williams wrote:
>
>     Date: Wed, 04 Aug 2004 00:08:51 -0700
>     From: Jeff Williams <jwkckid1@ix.netcom.com>
>     To: James M Galvin <galvin@elistx.com>
>     Cc: Brian E Carpenter <brc@zurich.ibm.com>, ietf-nomcom@lists.elistx.com
>     Subject: Re: UPDATED: WG Action: Conclusion of The Operation of the
>         IESG/IAB Nominating and Recall Committees (nomcom) (fwd)
>
>     James and all,
>
>       If the IETF or you would consider implementing Spf correctly, the
>     spam would be greatly reduced.
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.elistx.com/subscribe>

Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard

"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing  (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security
IDNS. div. of Information Network Eng.  INEG. INC.
E-Mail jwkckid1@ix.netcom.com
 Registered Email addr with the USPS
Contact Number: 214-244-4827



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/subscribe>
