From owner-wgchairs@ietf.org  Tue Apr  1 14:28:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09360
	for <wgchairs-archive@lists.ietf.org>; Tue, 1 Apr 2003 14:28:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Rea-00042s-00
	for wgchairs-list@ran.ietf.org; Tue, 01 Apr 2003 14:42:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Rdy-0003yt-00
	for wgchairs@ran.ietf.org; Tue, 01 Apr 2003 14:42:02 -0500
Received: from mail.wrs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09130
	for <wgchairs@ietf.org>; Tue, 1 Apr 2003 14:25:21 -0500 (EST)
Received: from IDLEWYLDE.windriver.com ([147.11.233.34])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA20590;
	Tue, 1 Apr 2003 11:27:26 -0800 (PST)
Message-Id: <5.1.0.14.2.20030401133600.049a8e88@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 01 Apr 2003 14:17:56 -0500
To: wgchairs@ietf.org, wgchairs-training@ops.ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Subject: Summary of WG Chairs Training Discussion
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-wgchairs@ietf.org
Precedence: bulk


Hi All,

I've attached a summary of the WG chairs training discussion
session that was held over lunch on Wednesday, March 19th at
the SF IETF meeting.  This has been reassembled from my
cryptic notes.  If I've missed anything important, please
speak up.

Further discussion of this topic and follow-up from the meeting
will take place on the wgchairs-training mailing list:

List: wgchairs-training@ops.ietf.org
Subscribe: majordomo@ops.ietf.org
Body: "subscribe wgchairs-training" (no quotes)
Archive: http://ops.ietf.org/lists/wgchairs-training/

Thanks,
Margaret


----

WG Chairs Training Discussion
Wednesday, March 19th, 2003
IETF 56, San Francisco, CA
=============================

AGENDA:

- Overview of the Current WG Chairs Training Program and Resources
- Open Discussion of our Training and Resource Needs
- Discuss Options to Improve our Training Programs and Resources
- Solicit Volunteers for a Design Team

MEETING PREPARATION:

Before the meeting, people were asked to familiarize themselves
with our current training materials and resources.

Training Materials:
http://psg.com/~mrw/WGChairs_Training_Mar03.ppt

WG Chairs Web Page:
http://www.ietf.org/IESG/wgchairs.html

MEETING NOTES:

The meeting started with a very short introductory presentation by
Margaret Wasserman, which can be found at:

http://www.psg.com/~mrw/WG_Chairs_Training_Discussion_Mar03.ppt

This was followed by a very active, open discussion regarding
WG chairs training and resource needs, which segued into a
discussion of how best to meet those needs.

There was general consensus that the formal introductory training
sessions are useful and should be continued.  The materials need
to be updated to reflect feedback on the list, and to focus more
on the role/responsibilities of chairs and on the decision making
process/skills.  "Administrivia" should be reduced to a reference
to the WG chairs web site.  There should also be more information
on milestones, miltestone updates, etc.  It was agreed that
Margaret Wasserman and Jeff Schiller would continue to work on
these materials, based on group input.

There was discussion of whether the introductory training should
be held earlier in the week (Sunday morning?) to allow all WG
chairs to attend before their first session.  It was noted that
we already include BOF chairs.  There were some suggestions that
the training should be mandatory and/or IESG members should
encourage new chairs to attend.

We discussed a formal mentoring program for new chairs, where
an experienced chair would be assigned to help a new chair through
the first few meetings.  This is sometimes accomplished by having
and experienced person and an inexperienced person co-chair a
group, but additional support may be needed when an inexperienced
person is chairing a group alone, or with another inexperienced
person.  Agreed to organize a list of volunteers, to be tapped by
the IESG if they feel that mentors are needed.

There was a discussion of the need for trained/qualified editors.
There was general consensus that some sort of training or
qualification process would be good for editors, but we didn't
reach any agreement regarding the particulars.

The WG Chairs mailing list is an underused resource.  We discussed
how to encourage people to send mail to the list when they have
process questions or issues running their group.

We identified a need for tools support in two key areas:

         - Issue/action item tracking.
         - Document sharing, versioning and change control.

We discussed the benefits of a WG chairs FAQ, and Derek Atkins
took the action item to assemble a FAQ for publication on the
WG chairs web page.

We then discussed training sessions for experienced WG chairs.
There was general consensus that ongoing training would be
useful, including both:

         - Formal training on timely or interesting topics.
         - Open sessions to discuss problems and potential
                 solutions, perhaps with a specified topic
                 per session.

Potential topics for ongoing formal training include:

         - IPR policies and how to deal with them.
         - Tools for issue/action item tracking.
         - Tools for document sharing & change control.
         - John Cleese "Meetings, Bloody Meetings" video.
         - Decision making/process skills.

Potential topics for discussion include:

         - Requirements documents -- What are they?  What
                 works, what doesn't?
         - How to manage our mailing lists?
         - How to deal with problem people?

It was agreed that this session was useful, both for understanding
our training needs and to help forge a community of WG chairs.  It
was also agreed that Margaret Wasserman would investigate how/when/if
we can hold sessions for experienced chairs at future IETF meetings.

We did not explicitly form a design team during the meeting,
but people interested in continuing this discussion were asked
to join the wgchairs-training mailing list.













From owner-wgchairs@ietf.org  Fri Apr  4 13:52:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02467
	for <wgchairs-archive@lists.ietf.org>; Fri, 4 Apr 2003 13:52:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191WTS-0000v1-00
	for wgchairs-list@ran.ietf.org; Fri, 04 Apr 2003 14:03:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191WT2-0000r5-00
	for wgchairs@ran.ietf.org; Fri, 04 Apr 2003 14:03:12 -0500
Received: from nit.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02358
	for <wgchairs@ietf.org>; Fri, 4 Apr 2003 13:45:47 -0500 (EST)
Received: (from falk@localhost)
	by nit.isi.edu (8.11.6/8.11.6) id h34ImHL29888
	for wgchairs@ietf.org; Fri, 4 Apr 2003 10:48:17 -0800
Date: Fri, 4 Apr 2003 10:48:17 -0800
From: Aaron Falk <falk@isi.edu>
To: wgchairs@ietf.org
Subject: How large are IETF mailing lists?
Message-ID: <20030404184817.GA24046@isi.edu>
Mail-Followup-To: wgchairs@ietf.org
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="k1lZvvs/B4yU6o8G"
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: owner-wgchairs@ietf.org
Precedence: bulk


--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi-

There was a thread a few weeks ago where the topic of mailing list
sizes came up and it occurred to me that no one really has a good idea
of the typical size of IETF mailing lists.  So, I asked the working
group chairs to send me the size of their lists.  I also received some
list sizes from helpful folks who host mailing lists, not the least of
which was Brett at Fortec who submitted info for all the ietf.org
lists.  Some of the information I received was for the same lists and
if they differed I selected the smaller list as some folks were able
to subtract inactive subscriptions.

Caveats to consider when looking at this data include:

  - There are inactive/broken subscriptions included in some counts,
    anecdotally this can be as much as 20% of the total.

  - Some subscriptions are lists themselves, hiding an unknown number
    of readers.

  - Not all wgs are listed here. I only listed what I receieved.

  - Some lists here are not working groups, some are expired working
    groups.  I've included the notes that I've received.

This is cleaned up data with no analysis.  Draw your own conclusions.
I'm including the data twice, sorted by size and by listname.  

Enjoy,

--aaron
--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=sizebysize

ietf-announce	       4000 (approx)
diffserv	       2285
ietf		       1950 (approx)
sip		       1840  
mobileip	       1797
manet		       1757
pkix		       1263
sipping		       1154
tewg		       1047
tcpsat		       1040 (dead wg)
beep			979
routing-discussion	950
megaco			879
idr			771
avt			766
sigtran			760
impp			760
policy			757
pwe3			734
ccamp			674
tsvwg			656
aaa			625
ippm			603
dhcwg			595
enum			587   
namedroppers		586
seamoby			561
apex			559
nsis			531
l2tpext			525
nemo			518
isis-wg			518
midcom			516
ipsp			498
v6ops			497
pilc			495
rmt			492
asrg			489
pim			488
smime			483
ldapext			475
rmonmib			462
ssm			459
ipsra			427
ipp			413
tls		        409
cfrg			400   
nat			389
idn			381     
bgmp			365
ediint			358
bmwg			358
imrg			357
diffserv-interest	357
mmusic			351
iporpr			346
multi6			333
forces			331
raven			323
openpgp			323
rpsec			314
rohc			307
cdn			307
calsched		297
ipcdn			295
ietf-geopriv		293
magma			280
ipfix			270
provreg			266
simple			265
rap			264
dccp			263
fax			255
rps			253
opes			252
nfsv4			245
ldup			241
ipoverib		240
ieprep			239
gsmp			232  
disman			231
gsmp			230
vrrp			228
krb-wg			216
ipr-wg			212
iptel			204
speechsc		193
sacred			192
rserpool		188
rddp			181
ietf-822	        179 
agentx			178
sasl			176
ietf-mixer		176 (WG long dead, list still available but not active)
ifmib			167
ietf-madman		167 (WG dead, list still available but not active)
pwot.now.pwe3		163
malloc			163
eos			160
entmib			158
discuss			158
psamp			153
sming			146
imapext			146
ietf-charsets		141 (charsets review list, not a WG list)
ietf-censored		141
hubmib			140
kink			139
dcp			139
problem-statement	131
inch			130
nasreq			118
msgtrk		        114
bridge-mib		110
adslmib			108
ietf-apps-tls	         96
itu+ietf		 94
trigtran		 88 
bridge			 85
mipcharter		 74
isis-update		 69
lemonade		 59
new-work		 57
directory		 54
ans-research		 54
ipseckey		 32
uri-review		 25
w3c-policy		 23
56crew			 23
messaging		 22
urn-nid			 21
iesg			 21
web			 20
iesg-only		 19
rtg-dir			 17
iab			 17
rip			 14
stun			 11
research-funding	 10
sipping-emergency	  8
rir-ietf		  6
grip			  4
media-feature-tags	  3
intersecs		  2
cats			  1
is-is			  0
booger			  0

--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=size

56crew			 23
aaa			625
adslmib			108
agentx			178
ans-research		 54
apex			559
asrg			489
avt			766
beep			979
bgmp			365
bmwg			358
booger			  0
bridge			 85
bridge-mib		110
calsched		297
cats			  1
ccamp			674
cdn			307
cfrg			400   
dccp			263
dcp			139
dhcwg			595
diffserv	       2285
diffserv-interest	357
directory		 54
discuss			158
disman			231
ediint			358
entmib			158
enum			587   
eos			160
fax			255
forces			331
grip			  4
gsmp			230
gsmp			232  
hubmib			140
iab			 17
idn			381     
idr			771
ieprep			239
iesg			 21
iesg-only		 19
ietf		       1950 (approx)
ietf-822	        179 
ietf-announce	       4000 (approx)
ietf-apps-tls	         96
ietf-censored		141
ietf-charsets		141 (charsets review list, not a WG list)
ietf-geopriv		293
ietf-madman		167 (WG dead, list still available but not active)
ietf-mixer		176 (WG long dead, list still available but not active)
ifmib			167
imapext			146
impp			760
imrg			357
inch			130
intersecs		  2
ipcdn			295
ipfix			270
iporpr			346
ipoverib		240
ipp			413
ippm			603
ipr-wg			212
ipseckey		 32
ipsp			498
ipsra			427
iptel			204
is-is			  0
isis-update		 69
isis-wg			518
itu+ietf		 94
kink			139
krb-wg			216
l2tpext			525
ldapext			475
ldup			241
lemonade		 59
magma			280
malloc			163
manet		       1757
media-feature-tags	  3
megaco			879
messaging		 22
midcom			516
mipcharter		 74
mmusic			351
mobileip	       1797
msgtrk		        114
multi6			333
namedroppers		586
nasreq			118
nat			389
nemo			518
new-work		 57
nfsv4			245
nsis			531
openpgp			323
opes			252
pilc			495
pim			488
pkix		       1263
policy			757
problem-statement	131
provreg			266
psamp			153
pwe3			734
pwot.now.pwe3		163
rap			264
raven			323
rddp			181
research-funding	 10
rip			 14
rir-ietf		  6
rmonmib			462
rmt			492
rohc			307
routing-discussion	950
rps			253
rpsec			314
rserpool		188
rtg-dir			 17
sacred			192
sasl			176
seamoby			561
sigtran			760
simple			265
sip		       1840  
sipping		       1154
sipping-emergency	  8
smime			483
sming			146
speechsc		193
ssm			459
stun			 11
tcpsat		       1040 (dead wg)
tewg		       1047
tls		        409
trigtran		 88 
tsvwg			656
uri-review		 25
urn-nid			 21
v6ops			497
vrrp			228
w3c-policy		 23
web			 20

--k1lZvvs/B4yU6o8G--



From owner-wgchairs@ietf.org  Fri Apr  4 14:00:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02816
	for <wgchairs-archive@lists.ietf.org>; Fri, 4 Apr 2003 14:00:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Wg4-0001jq-00
	for wgchairs-list@ran.ietf.org; Fri, 04 Apr 2003 14:16:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191Wf2-0001dr-00
	for wgchairs@ran.ietf.org; Fri, 04 Apr 2003 14:15:36 -0500
Received: from mail.wrs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02720
	for <wgchairs@ietf.org>; Fri, 4 Apr 2003 13:58:13 -0500 (EST)
Received: from IDLEWYLDE.windriver.com ([147.11.233.6])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA20213;
	Fri, 4 Apr 2003 11:00:10 -0800 (PST)
Message-Id: <5.1.0.14.2.20030404135734.03cad040@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 04 Apr 2003 13:58:05 -0500
To: Aaron Falk <falk@isi.edu>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: How large are IETF mailing lists?
Cc: wgchairs@ietf.org
In-Reply-To: <20030404184817.GA24046@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-wgchairs@ietf.org
Precedence: bulk


Hi Aaron,

I'm sorry, I got the information for the IPv6 list and then
forgot to send it to you...  We have 1811 subscribers.

Margaret


At 10:48 AM 4/4/2003 -0800, Aaron Falk wrote:
>Hi-
>
>There was a thread a few weeks ago where the topic of mailing list
>sizes came up and it occurred to me that no one really has a good idea
>of the typical size of IETF mailing lists.  So, I asked the working
>group chairs to send me the size of their lists.  I also received some
>list sizes from helpful folks who host mailing lists, not the least of
>which was Brett at Fortec who submitted info for all the ietf.org
>lists.  Some of the information I received was for the same lists and
>if they differed I selected the smaller list as some folks were able
>to subtract inactive subscriptions.
>
>Caveats to consider when looking at this data include:
>
>   - There are inactive/broken subscriptions included in some counts,
>     anecdotally this can be as much as 20% of the total.
>
>   - Some subscriptions are lists themselves, hiding an unknown number
>     of readers.
>
>   - Not all wgs are listed here. I only listed what I receieved.
>
>   - Some lists here are not working groups, some are expired working
>     groups.  I've included the notes that I've received.
>
>This is cleaned up data with no analysis.  Draw your own conclusions.
>I'm including the data twice, sorted by size and by listname.
>
>Enjoy,
>
>--aaron





From owner-wgchairs@ietf.org  Fri Apr  4 14:07:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03009
	for <wgchairs-archive@lists.ietf.org>; Fri, 4 Apr 2003 14:07:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Wmp-0002E4-00
	for wgchairs-list@ran.ietf.org; Fri, 04 Apr 2003 14:23:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191WmN-0002AT-00
	for wgchairs@ran.ietf.org; Fri, 04 Apr 2003 14:23:11 -0500
Received: from above.proper.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02961
	for <wgchairs@ietf.org>; Fri, 4 Apr 2003 14:05:48 -0500 (EST)
Received: from [66.125.125.92] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	by above.proper.com (8.12.9/8.11.6) with ESMTP id h34J8CJR024668
	for <wgchairs@ietf.org>; Fri, 4 Apr 2003 11:08:14 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p05210663bab387f9c59f@[66.125.125.92]>
In-Reply-To: <20030404184817.GA24046@isi.edu>
References: <20030404184817.GA24046@isi.edu>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Fri, 4 Apr 2003 11:07:45 -0800
To: wgchairs@ietf.org
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: Re: How large are IETF mailing lists?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

At 10:48 AM -0800 4/4/03, Aaron Falk wrote:
>Draw your own conclusions.

I dare anyone to draw a conclusion from the fact that diffserv is 
larger than the combination of ietf and ietf-censored.


--Paul Hoffman, Director
--VPN Consortium



From owner-wgchairs@ietf.org  Fri Apr  4 14:57:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04876
	for <wgchairs-archive@lists.ietf.org>; Fri, 4 Apr 2003 14:57:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191XZC-00073l-00
	for wgchairs-list@ran.ietf.org; Fri, 04 Apr 2003 15:13:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191XVc-0006fR-00
	for wgchairs@ran.ietf.org; Fri, 04 Apr 2003 15:09:56 -0500
Received: from motgate3.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04788
	for <wgchairs@ietf.org>; Fri, 4 Apr 2003 14:52:32 -0500 (EST)
Received: from mothost.mot.com (mothost.mot.com [129.188.137.101])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h34Js6YN014813
	for <wgchairs@ietf.org>; Fri, 4 Apr 2003 12:54:06 -0700 (MST)
Received: [from ma07exm01.dma.isg.mot.com (ma07exm01.dma.isg.mot.com [150.21.2.102]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id MAA15870 for <wgchairs@ietf.org>; Fri, 4 Apr 2003 12:54:25 -0700 (MST)]
Received: by ma07exm01.dma.isg.mot.com with Internet Mail Service (5.5.2656.59)
	id <HNFXBXD8>; Fri, 4 Apr 2003 14:54:11 -0500
Message-ID: <19CD0E423FC1D611893500508B6F0B9C90E547@ma07exm01.dma.isg.mot.com>
From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
To: "'wgchairs@ietf.org'" <wgchairs@ietf.org>
Subject: RE: How large are IETF mailing lists?
Date: Fri, 4 Apr 2003 14:54:10 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Sender: owner-wgchairs@ietf.org
Precedence: bulk

On thing you can safely conclude is that IETF working groups differ
very widely in the size of their mailing lists. I think this is true
of most other aspects of WGs. This is one reason why I'm always
suspicious of rules which narrow the procedural alternatives available
to working groups. They are not all the same and they need the
flexibility to work in a variety of styles.

Donald

PS: The TRADE WG mailing list has 162 entries.

-----Original Message-----
From: Aaron Falk [mailto:falk@isi.edu]
Sent: Friday, April 04, 2003 1:48 PM
To: wgchairs@ietf.org
Subject: How large are IETF mailing lists?

Hi-

There was a thread a few weeks ago where the topic of mailing list
sizes came up and it occurred to me that no one really has a good idea
of the typical size of IETF mailing lists.  So, I asked the working
group chairs to send me the size of their lists.  I also received some
list sizes from helpful folks who host mailing lists, not the least of
which was Brett at Fortec who submitted info for all the ietf.org
lists.  Some of the information I received was for the same lists and
if they differed I selected the smaller list as some folks were able
to subtract inactive subscriptions.

Caveats to consider when looking at this data include:

  - There are inactive/broken subscriptions included in some counts,
    anecdotally this can be as much as 20% of the total.

  - Some subscriptions are lists themselves, hiding an unknown number
    of readers.

  - Not all wgs are listed here. I only listed what I receieved.

  - Some lists here are not working groups, some are expired working
    groups.  I've included the notes that I've received.

This is cleaned up data with no analysis.  Draw your own conclusions.
I'm including the data twice, sorted by size and by listname.  

Enjoy,

--aaron



From owner-wgchairs@ietf.org  Fri Apr  4 16:02:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08056
	for <wgchairs-archive@lists.ietf.org>; Fri, 4 Apr 2003 16:02:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191YXC-0002ik-00
	for wgchairs-list@ran.ietf.org; Fri, 04 Apr 2003 16:15:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191YWs-0002er-00
	for wgchairs@ran.ietf.org; Fri, 04 Apr 2003 16:15:18 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07966
	for <wgchairs@ietf.org>; Fri, 4 Apr 2003 15:57:53 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id CA4E46256F; Fri,  4 Apr 2003 23:00:22 +0200 (CEST)
Date: Fri, 04 Apr 2003 23:00:22 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Aaron Falk <falk@isi.edu>, wgchairs@ietf.org
Subject: Re: How large are IETF mailing lists?
Message-ID: <436240000.1049490022@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030404184817.GA24046@isi.edu>
References:  <20030404184817.GA24046@isi.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thanks for collecting this data!

note on the tailend...

--On fredag, april 04, 2003 10:48:17 -0800 Aaron Falk <falk@isi.edu> wrote:

> new-work		 57 not a WG
> directory		 54 not a WG, an apps "tech area" list
> ans-research		 54
> ipseckey		 32
> uri-review		 25 not a WG, an apps "tech area" list
> w3c-policy		 23 not a WG
> 56crew	         23 not a WG
> messaging		 22
> urn-nid	         21 not a WG
> iesg			 21 not a WG
> web			 20
> iesg-only		 19 not a WG
> rtg-dir	         17 not a WG
> iab			 17 not a WG
> rip			 14
> stun			 11
> research-funding	 10 not a WG
> sipping-emergency	  8
> rir-ietf		  6 not a WG
> grip			  4
> media-feature-tags	  3
> intersecs		  2
> cats			  1
> is-is			  0
> booger	          0

Except for ipseckey, the smallest WG lists seem to be 50+.......




From owner-wgchairs@ietf.org  Mon Apr  7 06:22:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13847
	for <wgchairs-archive@lists.ietf.org>; Mon, 7 Apr 2003 06:22:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 192U0N-0006IR-00
	for wgchairs-list@ran.ietf.org; Mon, 07 Apr 2003 06:37:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 192Tzj-0006IA-00
	for wgchairs@ran.ietf.org; Mon, 07 Apr 2003 06:36:55 -0400
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13814
	for <wgchairs@ietf.org>; Mon, 7 Apr 2003 06:18:53 -0400 (EDT)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 491556223F
	for <wgchairs@ietf.org>; Mon,  7 Apr 2003 12:21:24 +0200 (CEST)
Date: Mon, 07 Apr 2003 12:21:24 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: wgchairs@ietf.org
Subject: Changing procedure for milestone reminders
Message-ID: <547120000.1049710884@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
as part of ongoing operations at the secretariat, we'll be changing the 
procedures for sending out reminders of overdue WG milestones.

(We'll hopefully also get more adept at handling the change requests 
promptly and accurately!)

Currently, we're proposing to send out reminders of ALL overdue milestones 
once every 2 months, rather than the "one or two areas every month" that 
has been previously practiced.

I don't think this should create any great new overhead for the WG chairs, 
but comments are (as always) welcome.

Your comments?

                Harald




From owner-wgchairs@ietf.org  Mon Apr  7 16:41:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05385
	for <wgchairs-archive@lists.ietf.org>; Mon, 7 Apr 2003 16:41:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 192deS-0003ew-00
	for wgchairs-list@ran.ietf.org; Mon, 07 Apr 2003 16:55:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 192VSK-0005jS-00
	for wgchairs@ran.ietf.org; Mon, 07 Apr 2003 08:10:32 -0400
Received: from web10904.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA17714
	for <wgchairs@ietf.org>; Mon, 7 Apr 2003 07:52:29 -0400 (EDT)
Message-ID: <20030407115501.38494.qmail@web10904.mail.yahoo.com>
Received: from [12.237.229.250] by web10904.mail.yahoo.com via HTTP; Mon, 07 Apr 2003 04:55:01 PDT
Date: Mon, 7 Apr 2003 04:55:01 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: Changing procedure for milestone reminders
To: wgchairs@ietf.org
In-Reply-To: <547120000.1049710884@askvoll.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-wgchairs@ietf.org
Precedence: bulk

Dear Harald,

A more consistent "noticing" seems much more effective. I didn't
know that the algorithm was "one or two areas every month", and
had just assumed it was completely random.

Spencer

--- Harald Tveit Alvestrand <harald@alvestrand.no> wrote:
>
> Currently, we're proposing to send out reminders of ALL
> overdue milestones
> once every 2 months, rather than the "one or two areas every
> month" that
> has been previously practiced.
>
> I don't think this should create any great new overhead for
> the WG chairs,
> but comments are (as always) welcome.
>
> Your comments?
>
>                 Harald





From owner-wgchairs@ietf.org  Mon Apr  7 22:35:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14636
	for <wgchairs-archive@lists.ietf.org>; Mon, 7 Apr 2003 22:35:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 192jCy-0008RK-00
	for wgchairs-list@ran.ietf.org; Mon, 07 Apr 2003 22:51:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 192jCa-0008QM-00
	for wgchairs@ran.ietf.org; Mon, 07 Apr 2003 22:51:12 -0400
Received: from pacific-carrier-annex.mit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14616
	for <wgchairs@ietf.org>; Mon, 7 Apr 2003 22:32:55 -0400 (EDT)
Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])
	by pacific-carrier-annex.mit.edu (8.12.4/8.9.2) with ESMTP id h382ZSFt016716
	for <wgchairs@ietf.org>; Mon, 7 Apr 2003 22:35:28 -0400 (EDT)
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by central-city-carrier-station.mit.edu (8.12.4/8.9.2) with ESMTP id h382ZRtG001584
	for <wgchairs@ietf.org>; Mon, 7 Apr 2003 22:35:27 -0400 (EDT)
Received: from kikki.mit.edu (KIKKI.MIT.EDU [18.18.1.142])
	)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id h382ZRU8003536
	for <wgchairs@ietf.org>; Mon, 7 Apr 2003 22:35:27 -0400 (EDT)
Received: (from warlord@localhost) by kikki.mit.edu (8.9.3p2)
	id WAA15392; Mon, 7 Apr 2003 22:35:27 -0400 (EDT)
To: wgchairs@ietf.org
From: Derek Atkins <derek@ihtfp.com>
Subject: WG Chairs FAQ is up
Date: 07 Apr 2003 22:35:27 -0400
Message-ID: <sjmznn1zpg0.fsf@kikki.mit.edu>
Lines: 14
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-wgchairs@ietf.org
Precedence: bulk

FYI,

The first draft of the FAQ I agreed to maintain is up at the IETF
Website.  Comments are welcome (and encouraged).  In particular,
feel free to send me additional questions (and their answers), or
corrections..

Enjoy!

-derek
-- 
       Derek Atkins
       Computer and Internet Security Consultant
       derek@ihtfp.com             www.ihtfp.com



From owner-wgchairs@ietf.org  Tue Apr  8 04:51:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02730
	for <wgchairs-archive@lists.ietf.org>; Tue, 8 Apr 2003 04:51:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 192p5n-00010u-00
	for wgchairs-list@ran.ietf.org; Tue, 08 Apr 2003 05:08:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 192p5l-00010g-00
	for wgchairs@ran.ietf.org; Tue, 08 Apr 2003 05:08:33 -0400
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02710
	for <wgchairs@ietf.org>; Tue, 8 Apr 2003 04:50:13 -0400 (EDT)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 46731621B3; Tue,  8 Apr 2003 10:52:46 +0200 (CEST)
Date: Tue, 08 Apr 2003 10:52:46 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Derek Atkins <derek@ihtfp.com>, wgchairs@ietf.org
Subject: Re: WG Chairs FAQ is up
Message-ID: <635490000.1049791966@askvoll.hjemme.alvestrand.no>
In-Reply-To: <sjmznn1zpg0.fsf@kikki.mit.edu>
References:  <sjmznn1zpg0.fsf@kikki.mit.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The URL is

http://www.ietf.org/IESG/faq.html

this may change, since it's not an IESG-maintained document....

              Harald

--On mandag, april 07, 2003 22:35:27 -0400 Derek Atkins <derek@ihtfp.com> 
wrote:

> FYI,
>
> The first draft of the FAQ I agreed to maintain is up at the IETF
> Website.  Comments are welcome (and encouraged).  In particular,
> feel free to send me additional questions (and their answers), or
> corrections..
>
> Enjoy!
>
> -derek
> --
>        Derek Atkins
>        Computer and Internet Security Consultant
>        derek@ihtfp.com             www.ihtfp.com
>
>





From owner-wgchairs@ietf.org  Wed Apr  9 14:28:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08756
	for <wgchairs-archive@lists.ietf.org>; Wed, 9 Apr 2003 14:28:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193KYn-000079-00
	for wgchairs-list@ran.ietf.org; Wed, 09 Apr 2003 14:44:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193KY9-00005Q-00
	for wgchairs@ran.ietf.org; Wed, 09 Apr 2003 14:43:57 -0400
Received: from edison.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08620
	for <wgchairs@ietf.org>; Wed, 9 Apr 2003 14:25:21 -0400 (EDT)
Received: from BYFRASER-W2K5.cisco.com (dhcp-171-71-119-17.cisco.com [171.71.119.17]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA04646 for <wgchairs@ietf.org>; Wed, 9 Apr 2003 11:27:52 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030409112042.030bdaf0@mira-sjc5-4.cisco.com>
X-Sender: byfraser@mira-sjc5-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 09 Apr 2003 11:24:43 -0700
To: wgchairs@ietf.org
From: Barbara Fraser <byfraser@cisco.com>
Subject: deadline for submissions
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_86208521==_.ALT"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

--=====================_86208521==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

I just noticed that there are two different deadlines documented on the 
IETF web site.

http://www.ietf.org/meetings/cutoff_dates_56.html has the following:

April 14, Monday - Proceedings submission cutoff date by 17:00 ET

But, http://www.ietf.org/proceedings/03mar/index.html says that the cutoff 
date is the 11th, not the 14th.


Barb
--=====================_86208521==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
I just noticed that there are two different deadlines documented on the
IETF web site. <br>
<br>
<font size=3><a href="http://www.ietf.org/meetings/cutoff_dates_56.html" eudora="autourl">http://www.ietf.org/meetings/cutoff_dates_56.html</a>
has the following:<br>
<br>
April 14, Monday - Proceedings submission cutoff date by 17:00 ET<br>
<br>
But, <a href="http://www.ietf.org/proceedings/03mar/index.html" eudora="autourl">http://www.ietf.org/proceedings/03mar/index.html</a> says that the cutoff date is the 11th, not the 14th.<br>
<br>
<br>
Barb</font></html>

--=====================_86208521==_.ALT--




From owner-wgchairs@ietf.org  Thu Apr 10 03:58:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11021
	for <wgchairs-archive@lists.ietf.org>; Thu, 10 Apr 2003 03:58:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193XDc-0004AV-00
	for wgchairs-list@ran.ietf.org; Thu, 10 Apr 2003 04:15:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193XCu-0004A1-00
	for wgchairs@ran.ietf.org; Thu, 10 Apr 2003 04:14:52 -0400
Received: from patan.sun.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10963
	for <wgchairs@ietf.org>; Thu, 10 Apr 2003 03:56:07 -0400 (EDT)
Received: from hs-ehdb03-01.Germany.Sun.COM ([129.157.142.201])
	by patan.sun.com (8.9.3p2+Sun/8.9.3) with ESMTP id BAA03429;
	Thu, 10 Apr 2003 01:58:40 -0600 (MDT)
Received: from field (field [129.157.142.146])
	by hs-ehdb03-01.Germany.Sun.COM (8.11.6+Sun/8.11.6/ENSMAIL,v2.2) with SMTP id h3A7wcl04913;
	Thu, 10 Apr 2003 09:58:38 +0200 (MEST)
Date: Thu, 10 Apr 2003 09:58:37 +0200 (CEST)
From: Erik Guttman <Erik.Guttman@Sun.COM>
X-Sender: erikg@field
To: Barbara Fraser <byfraser@cisco.com>
cc: wgchairs@ietf.org
Subject: Re: deadline for submissions
In-Reply-To: <4.3.2.7.2.20030409112042.030bdaf0@mira-sjc5-4.cisco.com>
Message-ID: <Pine.SOL.3.96.1030410095749.16645A-100000@field>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-wgchairs@ietf.org
Precedence: bulk


Barbara,

What file from which date (time frame or better - IETF #) did you want
me to scrounge out of my archives?

Erik

._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._.
 E r i k   G u t t m a n                        
 N1 Installation and Provisioning     
 Sun Microsystems                               cell: +49 172 865 5497




From owner-wgchairs@ietf.org  Thu Apr 10 14:16:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29146
	for <wgchairs-archive@lists.ietf.org>; Thu, 10 Apr 2003 14:16:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193gpo-0004ya-00
	for wgchairs-list@ran.ietf.org; Thu, 10 Apr 2003 14:31:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193gp3-0004xa-00
	for wgchairs@ran.ietf.org; Thu, 10 Apr 2003 14:30:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29024;
	Thu, 10 Apr 2003 14:12:02 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 193gGi-0003GH-00; Thu, 10 Apr 2003 13:55:24 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 193gGi-0003G7-00; Thu, 10 Apr 2003 13:55:24 -0400
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3AIE3B0028075;
	Thu, 10 Apr 2003 14:14:03 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-192.cisco.com [161.44.149.192]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA24445; Thu, 10 Apr 2003 14:14:02 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030410141238.064c0d70@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 10 Apr 2003 14:14:02 -0400
To: ietf-secretary@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: deadline for submissions
Cc: wgchairs@ietf.org
In-Reply-To: <4.3.2.7.2.20030409112042.030bdaf0@mira-sjc5-4.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

Is the proceedings cutoff 1700ET Friday, 4/11 or 1700ET Monday, 4/14, or ???

- Ralph

At 11:24 AM 4/9/2003 -0700, Barbara Fraser wrote:
>I just noticed that there are two different deadlines documented on the IETF web site. 
>
>http://www.ietf.org/meetings/cutoff_dates_56.html has the following:
>
>April 14, Monday - Proceedings submission cutoff date by 17:00 ET
>
>But, http://www.ietf.org/proceedings/03mar/index.html says that the cutoff date is the 11th, not the 14th.
>
>
>Barb 




From owner-wgchairs@ietf.org  Thu Apr 10 15:03:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01291
	for <wgchairs-archive@lists.ietf.org>; Thu, 10 Apr 2003 15:03:55 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193hc9-00023V-00
	for wgchairs-list@ran.ietf.org; Thu, 10 Apr 2003 15:21:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193hbd-0001WD-00
	for wgchairs@ran.ietf.org; Thu, 10 Apr 2003 15:21:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01188
	for <wgchairs@ietf.org>; Thu, 10 Apr 2003 15:02:13 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 193h3H-0003b9-00
	for wgchairs@ietf.org; Thu, 10 Apr 2003 14:45:35 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 193h3H-0003b0-00
	for wgchairs@ietf.org; Thu, 10 Apr 2003 14:45:35 -0400
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3AJ4GB0014176
	for <wgchairs@ietf.org>; Thu, 10 Apr 2003 15:04:17 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-192.cisco.com [161.44.149.192]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id PAA29297 for <wgchairs@ietf.org>; Thu, 10 Apr 2003 15:04:16 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030410150411.064c0d70@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 10 Apr 2003 15:04:17 -0400
To: wgchairs@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Fwd: Re: [ietf-action #1535] deadline for submissions
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

FYI...

>Date: Thu, 10 Apr 2003 14:59:31 -0400
>From: "Jacob Munoz" <jmunoz@ietf.org>
>To: rdroms@cisco.com
>Subject: Re: [ietf-action #1535] deadline for submissions
>
>Your request #1535 was resolved by jmunoz:
>
>The true deadline for proceedings submissions is Monday the 
>14th.  Officially the cutoff is at 17:00pmEST, however if the 
>document is submitted any time that day, it will be accepted and 
>included in the CDrom.
>
>Thank you
>IETF Proceedings Administrator




From owner-wgchairs@ietf.org  Fri Apr 11 14:46:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24358
	for <wgchairs-archive@lists.ietf.org>; Fri, 11 Apr 2003 14:46:30 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1943nK-0004oq-00
	for wgchairs-list@ran.ietf.org; Fri, 11 Apr 2003 15:02:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1943nG-0004mj-00
	for wgchairs@ran.ietf.org; Fri, 11 Apr 2003 15:02:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24276;
	Fri, 11 Apr 2003 14:43:28 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1943XI-0004t0-00; Fri, 11 Apr 2003 14:46:04 -0400
Received: from mgw-dax2.ext.nokia.com ([63.78.179.217])
	by ietf-mx with esmtp (Exim 4.12)
	id 1943XI-0004sx-00; Fri, 11 Apr 2003 14:46:04 -0400
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3BIk3b09230;
	Fri, 11 Apr 2003 13:46:03 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6189627e18ac12f25703c@davir04nok.americas.nokia.com>;
 Fri, 11 Apr 2003 13:46:01 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 11 Apr 2003 13:45:01 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: deadline for submissions
Date: Fri, 11 Apr 2003 13:45:00 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44017532D7@daebe007.americas.nokia.com>
Thread-Topic: deadline for submissions
Thread-Index: AcL/jauxdWwlTsD8Sz6dAiV1v34J+wAzLRiQ
To: <rdroms@cisco.com>, <ietf-secretary@ietf.org>
Cc: <wgchairs@ietf.org>
X-OriginalArrivalTime: 11 Apr 2003 18:45:01.0200 (UTC) FILETIME=[7553F900:01C3005A]
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA24358


I believe it is Monday.

-bp

> 
> Is the proceedings cutoff 1700ET Friday, 4/11 or 1700ET 
> Monday, 4/14, or ???
> 
> - Ralph
> 
> At 11:24 AM 4/9/2003 -0700, Barbara Fraser wrote:
> >I just noticed that there are two different deadlines 
> documented on the IETF web site. 
> >
> >http://www.ietf.org/meetings/cutoff_dates_56.html has the following:
> >
> >April 14, Monday - Proceedings submission cutoff date by 17:00 ET
> >
> >But, http://www.ietf.org/proceedings/03mar/index.html says 
> that the cutoff date is the 11th, not the 14th.
> >
> >
> >Barb 
> 
> 
> 



From owner-wgchairs@ietf.org  Fri Apr 11 15:36:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26705
	for <wgchairs-archive@lists.ietf.org>; Fri, 11 Apr 2003 15:36:44 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1944be-0005q7-00
	for wgchairs-list@ran.ietf.org; Fri, 11 Apr 2003 15:54:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1943g5-0004XJ-00
	for wgchairs@ran.ietf.org; Fri, 11 Apr 2003 14:55:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24091;
	Fri, 11 Apr 2003 14:36:01 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1943Q5-0004qg-00; Fri, 11 Apr 2003 14:38:37 -0400
Received: from ns.cnri.reston.va.us ([132.151.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1943Q5-0004qd-00; Fri, 11 Apr 2003 14:38:37 -0400
Received: from cnri-7-167.cnri.reston.va.us ([132.151.7.167] helo=ietf.org)
	by ns.cnri.reston.va.us with esmtp (Exim 4.12)
	id 1943Q4-0000fq-00; Fri, 11 Apr 2003 14:38:36 -0400
Message-ID: <3E970C29.5040000@ietf.org>
Date: Fri, 11 Apr 2003 14:40:41 -0400
From: IETF Proceedings Administrator <minutes@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: wgchairs@ietf.org, bofchairs@ietf.org
Subject: IETF 56 Proceedings Submission Cutoff Date MON, APR 14th
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This message is for all group chairs who met at the 56th IETF in San
Francisco.

Please make sure all of your meeting materials have been submitted and
are listed at:
www.ietf.org/proceedings/03mar

If you group is not listed or materials are missing, please contact
minutes@ietf.org.

The cutoff date for all material submissions is Monday April 14ht (last
weekend to finish).

Thank you,
IETF Proceedings Administrator






From owner-wgchairs@ietf.org  Mon Apr 14 13:02:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12125
	for <wgchairs-archive@lists.ietf.org>; Mon, 14 Apr 2003 13:02:47 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1957dF-0003N4-00
	for wgchairs-list@ran.ietf.org; Mon, 14 Apr 2003 13:20:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1957aT-0003JF-00
	for wgchairs@ran.ietf.org; Mon, 14 Apr 2003 13:17:45 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11951;
	Mon, 14 Apr 2003 12:57:55 -0400 (EDT)
Message-Id: <200304141657.MAA11951@ietf.org>
From: agenda@ietf.org
To: wgchairs@ietf.org, bofchairs@ietf.org
Cc: iesg@ietf.org, dinaras@ietf.org
Subject: 57th IETF WG/BOF Scheduling
Date: Mon, 14 Apr 2003 12:57:55 -0400
Sender: owner-wgchairs@ietf.org
Precedence: bulk

57th IETF in Vienna, Austria 
Meeting Dates: July 13-18, 2003

We will be taking scheduling requests for ALL Working Groups and BOFs starting today. 
The cut-off for requesting a slot is Friday, June 20 at 17:00 ET. 
The agenda for the Working Group is due by Tuesday, July 8 at 12:00 ET, 
please submit the agenda to: agenda@ietf.org. 

1. ALL scheduling requests must be sent to: agenda@ietf.org with a copy to 
the appropriate Area Director(s).

2. BOFs will not be scheduled unless the Area Director(s) approved request 
is accompanied by a BOF FULL NAME AND ACRONYM, AREA, CHAIRS NAME(s) (given 
together with e-mail address(es)), AN AGENDA AND FULL DESCRIPTION. 
(Please read the BOF Procedure at ftp://ftp.ietf.org/ietf/1bof-procedures.txt 
before requesting a slot for a BOF.)

3. WORKING GROUPs will be allowed a maximum of TWO slots (second slot has to be 
approved by AD). If your WG will need more, please let us know.
Additional slots will be available after agenda scheduling has closed 
(June 20 at 17:00 ET) and with approval from the AREA DIRECTOR(s) 
if there is any possibility to do this. Should you need some 
information for your WG session scheduling send us questions or visit the IETF 
Working Group guidelines at http://www.ietf.org/rfc/rfc2418.txt.

4. You MUST provide the following information before the meeting will be scheduled:
  a. Working Group or BOF full name with acronym in brackets: 
  b. AREA under which Working Group or BOF appears:
  c. CONFLICTS you wish to avoid, please be as specific as possible:
  d. Expected Attendance (figures from the 56th IETF are at the end of this message):
  e. Special requests (i.e. multicast):
  f. Number of slots:
  g. Length of slot: 
   - 1 hour 
   - 2 hours 
   - 2 1/2 hours

=================================================

For your convenience please find here the list of the AREA Directors with 
their e-mail addresses:

IETF Chair 
Harald Alvestrand <Harald@Alvestrand.no>

Applications Area (app) 
Ted Hardie <hardie@qualcomm.com> 
Ned Freed <ned.freed@mrochek.com>

Internet Area (int) 
Thomas Narten <narten@us.ibm.com> 
Erik Nordmark <erik.nordmark@sun.com>

Operations & Management Area (ops) 
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>

Routing Area (rtg) 
Bill Fenner <fenner@research.att.com> 
Alex Zinin <zinin@psg.com>

Security Area (sec) 
Steve Bellovin <smb@research.att.com>
Russ Housley <housley@vigilsec.com>

Sub-IP Area (sub) 
Alex Zinin <zinin@psg.com >
Bert Wijnen <bwijnen@lucent.com>

Transport Area (tsv) 
Allison Mankin <mankin@psg.com>
Jon Peterson <jon.peterson@neustar.biz>

=================================================

Figures from the 56th IETF, San Francisco, CA 

6bonebof 151
aaa 94
avt 132
bmwg 75
calsch 25
crisp 55
dccp 81
defcon 105
dhc 92
disman 29
dnsext 170
dnsop 149
eap 220
entmib 14
enum 112
fax 15
forces 99
grow 120
gsmp 17
idr 166
ieprep 107
inch 16
ipcdn 12
ipfix 67
ipoib 18
ippm 79
ipr 106
ips 59
ipsec 183
ipseckey 60
ipsp 91
iptel 112
ipv6 435
isis 120
itrace 35
krb-wg 53
ldapbis 24
ldup 26
lemonade 65
magma 75
manet 98
mboned 87
midcom 150
mmusic 108
mobileip 198
mpls 110
mpls 91
msec 49
nemo 79
netconf 235
nfsv4 21
nsiim 197
nsis 208
opes 33
opsarea 141
ospf 154
pads 120
pana 137
pim 73
pkix 76
plpmtud 68
ppvpn 238
problem 129
provreg 27
psamp 42
pwe3 147
rddp 40
rddp 68
rmonmib 27
rmt 96
rohc 26
rpsec 165
rserpool 32
rtgarea 135
saag 125
sasl 61
seamoby 59
send 132
simple 145
sip 129
sip 87
sipping 58
smime 64
speechsc 49
spirits 31
syslog 40
tewg 89
trade 10
tsvwg 166
uribof 42
v6ops 183
vrrp 22
webdav 23
xmpp 106











From owner-wgchairs@ietf.org  Tue Apr 15 10:20:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29157
	for <wgchairs-archive@lists.ietf.org>; Tue, 15 Apr 2003 10:20:29 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 195Ra4-00028c-00
	for wgchairs-list@ran.ietf.org; Tue, 15 Apr 2003 10:38:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 195QYc-0000wb-00
	for wgchairs@ran.ietf.org; Tue, 15 Apr 2003 09:33:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26504;
	Tue, 15 Apr 2003 09:13:03 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195QHg-0002X9-00; Tue, 15 Apr 2003 09:15:36 -0400
Received: from stork.mail.pas.earthlink.net ([207.217.120.188])
	by ietf-mx with esmtp (Exim 4.12)
	id 195QHf-0002X6-00; Tue, 15 Apr 2003 09:15:35 -0400
Received: from pcp802197pcs.nrockv01.md.comcast.net ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by stork.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)
	id 195QHk-00061N-00; Tue, 15 Apr 2003 06:15:41 -0700
Message-Id: <5.1.0.14.2.20030415090400.0402e7c0@pop.mindspring.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 15 Apr 2003 09:15:22 -0400
To: iab@ietf.org, iesg@ietf.org, wgchairs@ietf.org
From: Michael StJohns <mstjohns@mindspring.com>
Subject: ICANN Board  Candidate Search
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_48945119==_.ALT"
X-ELNK-Trace: 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d9a4a3e95dce6c318e4b432e22c76aab4350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Sender: owner-wgchairs@ietf.org
Precedence: bulk

--=====================_48945119==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

OK - as the designated IETF sacrificial lamb to the ICANN nomcom I need
your help.  The ICANN is looking for more than a few good men and women to
volunteer to be considered for membership on the ICANN board.  I'm looking
to you folks to come up with some names for the lions.  I've pasted in the
announcement that was sent to the IETF list on the 7th of April. If you've
got some ideas on candidates, you can either send them to me at
mstjohns@mindspring.com and I'll forward them to the nomcom,
or  (preferred) you can send them to the nomcom.submissions@icann.org list.

Thanks - Mike





We, the ICANN Nominating Committee (NomCom), have just posted our Formal
Call for Recommendations and Statements of Interest for the ICANN
positions NomCom will select. Please see
http://www.icann.org/committees/nom-comm/formal-call-05apr03.htm This
information has also been distributed via the ICANN Announce list.
We would like to send a special invitation to the members of the IETF to
submit as individuals their recommendations and statements of interest for
the positions NomCom will fill. The success of this new Nominating
Committee process depends on the active participation of members of the
Internet community, and we are eager to encourage your attention to this
opportunity.
Our timeline is short because our goal is to be able to seat the New Board
and NomCom-selected members of the GNSO Council and Interim ALAC at the
conclusion of the Montreal ICANN meeting June 22-26, 2003.
We believe you will find in the posted Formal Call the information needed
about NomCom, about the positions to be filled, the eligibility and
criteria that apply, the review process, and how to respond to this
invitation. But we do understand that questions will arise and we would
like to engage directly with IETF members in our recruiting. NomCom is
therefore offering to participate in teleconferences organized by groups
such as the IETF to help launch the Nominating Process. If you would like
me and some of the NomCom members to participate in one of your
teleconferences, please contact me via email.
NomCom will be posting Frequently Asked Questions with their answers on the
NomCom web page http://www.icann.org/committees/nom-comm/ and invites
comments via email to nomcom.comments@icann.org

We encourage all those interested in this new Nominating Committee process
to visit our webpage and to subscribe to nomcom.announce-request@icann.org
to receive notice of news from the Committee.
Let me also express my thanks for the excellent participation Mike St.Johns
has provided in the work of the Nominating Committee.

We look forward to hearing from you and your colleagues in the IETF.

Linda Wilson, Chair of the ICANN Nominating Committee

--=====================_48945119==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
OK - as the designated IETF sacrificial lamb to the ICANN nomcom I need
your help.&nbsp; The ICANN is looking for more than a few good men and
women to volunteer to be considered for membership on the ICANN
board.&nbsp; I'm looking to you folks to come up with some names for the
lions.&nbsp; I've pasted in the announcement that was sent to the IETF
list on the 7th of April. If you've got some ideas on candidates, you can
either send them to me at mstjohns@mindspring.com and I'll forward them
to the nomcom, or&nbsp; (preferred) you can send them to the
nomcom.submissions@icann.org list.&nbsp; <br><br>
Thanks - Mike<br><br>
<br><br>
<br><br>
We, the ICANN Nominating Committee (NomCom), have just posted our Formal
<br>
Call for Recommendations and Statements of Interest for the ICANN <br>
positions NomCom will select. Please see <br>
<font color="#0000FF"><u><a href="http://www.icann.org/committees/nom-comm/formal-call-05apr03.htm" eudora="autourl">http://www.icann.org/committees/nom-comm/formal-call-05apr03.htm</a></u></font>
This <br>
information has also been distributed via the ICANN Announce list. <br>
We would like to send a special invitation to the members of the IETF to <br>
submit as individuals their recommendations and statements of interest for <br>
the positions NomCom will fill. The success of this new Nominating <br>
Committee process depends on the active participation of members of the <br>
Internet community, and we are eager to encourage your attention to this <br>
opportunity. <br>
Our timeline is short because our goal is to be able to seat the New Board <br>
and NomCom-selected members of the GNSO Council and Interim ALAC at the <br>
conclusion of the Montreal ICANN meeting June 22-26, 2003. <br>
We believe you will find in the posted Formal Call the information needed <br>
about NomCom, about the positions to be filled, the eligibility and <br>
criteria that apply, the review process, and how to respond to this <br>
invitation. But we do understand that questions will arise and we would <br>
like to engage directly with IETF members in our recruiting. NomCom is <br>
therefore offering to participate in teleconferences organized by groups <br>
such as the IETF to help launch the Nominating Process. If you would like <br>
me and some of the NomCom members to participate in one of your <br>
teleconferences, please contact me via email. <br>
NomCom will be posting Frequently Asked Questions with their answers on the <br>
NomCom web page <a href="http://www.icann.org/committees/nom-comm/" eudora="autourl"><font color="#0000FF"><u>http://www.icann.org/committees/nom-comm/</a></u></font> and invites <br>
comments via email to nomcom.comments@icann.org<br><br>
We encourage all those interested in this new Nominating Committee process <br>
to visit our webpage and to subscribe to nomcom.announce-request@icann.org <br>
to receive notice of news from the Committee. <br>
Let me also express my thanks for the excellent participation Mike St.Johns <br>
has provided in the work of the Nominating Committee.<br><br>
We look forward to hearing from you and your colleagues in the IETF.<br><br>
Linda Wilson, Chair of the ICANN Nominating Committee<br>
</html>

--=====================_48945119==_.ALT--






From owner-wgchairs@ietf.org  Mon Apr 21 14:59:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26238
	for <wgchairs-archive@lists.ietf.org>; Mon, 21 Apr 2003 14:59:11 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197goM-0002Vm-00
	for wgchairs-list@ran.ietf.org; Mon, 21 Apr 2003 15:18:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197gnV-0002Rg-00
	for wgchairs@ran.ietf.org; Mon, 21 Apr 2003 15:17:49 -0400
Received: from dinaras.cnri.reston.va.us (host-4-253.cnri.reston.va.us [10.27.4.253])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26135;
	Mon, 21 Apr 2003 14:56:15 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030421145753.026accb0@odin>
X-Sender: dinaras@odin
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 21 Apr 2003 15:02:19 -0400
To: wgchairs@ietf.org, bofchairs@ietf.org
From: Dinara Suleymanova <dinaras@ietf.org>
Subject: 57th IETF WG/BOF Scheduling - Overhead Projector Request
Cc: iesg@ietf.org, Marcia Beaulieu <mbeaulie@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-wgchairs@ietf.org
Precedence: bulk

We will not supply an overhead projectors in the rooms at the 57th IETF 
Meeting
UNLESS it is specifically requested. So please mention "it" in your common 
request.

Thanks.

Dinara Suleymanova






From owner-wgchairs@ietf.org  Wed Apr 23 14:23:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29096
	for <wgchairs-archive@lists.ietf.org>; Wed, 23 Apr 2003 14:23:02 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198PDZ-0001mx-00
	for wgchairs-list@ran.ietf.org; Wed, 23 Apr 2003 14:43:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198PCz-0001ii-00
	for wgchairs@ran.ietf.org; Wed, 23 Apr 2003 14:43:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28985
	for <wgchairs@ietf.org>; Wed, 23 Apr 2003 14:21:03 -0400 (EDT)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Otv-000682-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 14:23:23 -0400
Received: from mgw-dax2.ext.nokia.com ([63.78.179.217])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Otu-00067y-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 14:23:22 -0400
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3NINlb15996
	for <wgchairs@ietf.org>; Wed, 23 Apr 2003 13:23:47 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T61c71a707cac12f25703c@davir04nok.americas.nokia.com> for <wgchairs@ietf.org>;
 Wed, 23 Apr 2003 13:23:46 -0500
Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 23 Apr 2003 11:23:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Checking I-Ds for nits.
Date: Wed, 23 Apr 2003 13:23:07 -0500
Message-ID: <8D260779A766FB4A9C1739A476F84FA42AC5A6@daebe009.americas.nokia.com>
Thread-Topic: ICANN Board  Candidate Search
Thread-Index: AcMDWpH9HBOi+W07QBm5sqWWZGOY2QGamFsw
To: <wgchairs@ietf.org>
X-OriginalArrivalTime: 23 Apr 2003 18:23:11.0280 (UTC) FILETIME=[65830B00:01C309C5]
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA29096

Hi All,

How do people make sure that the draft submitted to the WG are compliant to ID nits on this page ?
http://www.ietf.org/ID-nits.html

Is there any tool available to help in doing this ??

regards
Mukesh



From owner-wgchairs@ietf.org  Wed Apr 23 14:39:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29928
	for <wgchairs-archive@lists.ietf.org>; Wed, 23 Apr 2003 14:39:49 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198PU3-0003To-00
	for wgchairs-list@ran.ietf.org; Wed, 23 Apr 2003 15:00:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198PT2-00031Y-00
	for wgchairs@ran.ietf.org; Wed, 23 Apr 2003 14:59:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29774
	for <wgchairs@ietf.org>; Wed, 23 Apr 2003 14:37:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198P9x-0006Fc-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 14:39:57 -0400
Received: from www.route-explorer.net ([65.192.41.10] helo=mailman.packetdesign.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198P9x-0006FF-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 14:39:57 -0400
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id h3NIdnvW087058;
	Wed, 23 Apr 2003 11:39:49 -0700 (PDT)
	(envelope-from casner@acm.org)
Date: Wed, 23 Apr 2003 11:39:49 -0700 (PDT)
From: Stephen Casner <casner@acm.org>
To: Mukesh.Gupta@nokia.com
cc: wgchairs@ietf.org
Subject: Re: Checking I-Ds for nits.
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42AC5A6@daebe009.americas.nokia.com>
Message-ID: <20030423113822.H71348-200000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-178515613-1051123189=:71348"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-178515613-1051123189=:71348
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 23 Apr 2003 Mukesh.Gupta@nokia.com wrote:

> How do people make sure that the draft submitted to the WG are compliant to ID nits on this page ?
> http://www.ietf.org/ID-nits.html
>
> Is there any tool available to help in doing this ??

I have a simple awk script that checks the formatting aspects.  It
does not check any of the content nits.  I've attached it.

                                                        -- Steve

--0-178515613-1051123189=:71348
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; name="checkpage.awk"
Content-ID: <20030423113949.K71348@ash.packetdesign.com>
Content-Description: 
Content-Disposition: attachment; filename="checkpage.awk"
Content-Transfer-Encoding: BASE64

IyEvdXNyL2Jpbi9hd2sgLWYNCiMNCiMgY2hlY2sgcGFnaW5hdGlvbiBvZiBJ
bnRlcm5ldC1EcmFmdHMNCiMNCiMgQCgjKSAkSWQkDQoNCkJFR0lOIHsNCiMg
ICAgbGluZWxpbSA9IDY4Ow0KIyAgICBjaGFybGltID0gODA7DQogICAgbGlu
ZWxpbSA9IDU4Ow0KICAgIGNoYXJsaW0gPSA3MjsNCiAgICBsaW5lcyA9IDA7
DQogICAgbG9uZ3BhZ2VzID0gMDsNCiAgICBiYWRmb3JtZmVlZHMgPSAwOw0K
ICAgIG1heGxpbmVzID0gMDsNCiAgICBtYXhjaGFycyA9IDA7DQogICAgbG9u
Z2xpbmVzID0gMDsNCiAgICBtc2NoYXJzID0gMDsNCiAgICBiYWRjaGFycyA9
IDA7DQp9DQoNCnsNCiAgICBwcmVmZWVkID0gMDsNCiAgICBwb3N0ZmVlZCA9
IDA7DQogICAgbGluZSA9IGdlbnN1YigvXHIkLywgIiIsICJnIik7DQp9DQoN
Ci9eDC8gew0KICAgIHByZWZlZWQgPSAxOw0KICAgIGlmIChsZW5ndGgobGlu
ZSkgIT0gMSkgew0KCSsrYmFkZm9ybWZlZWRzOw0KICAgIH0NCn0NCg0KLwwk
LyB7DQogICAgcG9zdGZlZWQgPSAxOw0KICAgIGlmIChsZW5ndGgobGluZSkg
IT0gMSkgew0KCSsrYmFkZm9ybWZlZWRzOw0KICAgIH0NCn0NCg0KL1teAS1+
XS8gew0KICAgICsrYmFkY2hhcnM7DQogICAgcHJpbnQgIkJhZCBjaGFycyBh
dCIsIE5SOw0KfQ0KDQp7DQogICAgbXNjaGFycyArPSBnc3ViKC+RLywgIici
KTsNCiAgICBtc2NoYXJzICs9IGdzdWIoL5IvLCAiJyIpOw0KICAgIG1zY2hh
cnMgKz0gZ3N1Yigvky8sICJcIiIpOw0KICAgIG1zY2hhcnMgKz0gZ3N1Yigv
lC8sICJcIiIpOw0KICAgIG1zY2hhcnMgKz0gZ3N1Yigvli8sICItIik7DQog
ICAgaWYgKGxlbmd0aChsaW5lKSA+IGNoYXJsaW0pIHsNCgkrK2xvbmdsaW5l
czsNCglpZiAobGVuZ3RoKGdlbnN1YigvICokLywgIiIsICJnIiwgbGluZSkp
ID4gY2hhcmxpbSkgew0KCSAgICBwcmludCAiTG9uZyBsaW5lIGF0IiwgTlIs
ICJ3aXRoIiwgbGVuZ3RoKGxpbmUpLCAiY2hhcnMiOw0KCX0gZWxzZSB7DQoJ
ICAgIHByaW50ICJMb25nIGxpbmUgYXQiLCBOUiwgIndpdGgiLCBsZW5ndGgo
bGluZSksICJjaGFycywgb25seSBzcGFjZXMgZXh0cmEiOw0KCX0NCglpZiAo
bGVuZ3RoKGxpbmUpID4gbWF4Y2hhcnMpIHsNCgkgICAgbWF4Y2hhcnMgPSBs
ZW5ndGgobGluZSk7DQoJfQ0KICAgIH0NCiAgICBpZiAoKGxpbmVzIDwgbGlu
ZWxpbSkgfHwgKChwb3N0ZmVlZCA9PSAxKSAmJiAocHJlZmVlZCA9PSAwKSkp
IHsNCgkrK2xpbmVzOw0KCWlmIChwcmVmZWVkID09IDEpIGxpbmVzID0gMTsN
CglpZiAocG9zdGZlZWQgPT0gMSkgbGluZXMgPSAwOw0KICAgIH0gZWxzZSB7
ICMgKGxpbmVzID49IGxpbmVsaW0pICYmICgocG9zdGZlZWQgPT0gMCkgfHwg
KHByZWZlZWQgPT0gMSkpDQoJaWYgKHByZWZlZWQgPT0gMCkgeyAgIyA9PiAo
cG9zdGZlZWQgPT0gMCkpDQoJICAgIGlmIChsaW5lcyA9PSBsaW5lbGltKSB7
DQoJCSsrbG9uZ3BhZ2VzOw0KCQlwcmludCAiTG9uZyBwYWdlIGF0IiwgTlI7
DQoJICAgIH0NCgkgICAgKytsaW5lczsNCgkgICAgaWYgKGxpbmVzID4gbWF4
bGluZXMpIG1heGxpbmVzID0gbGluZXM7DQoJfSBlbHNlIHsNCgkgICAgbGlu
ZXMgPSAwOw0KCSAgICBpZiAocG9zdGZlZWQgPT0gMCkgbGluZXMgPSAxOw0K
CX0NCglibGFua3MgPSAwOw0KICAgIH0NCn0NCg0KRU5EIHsNCiAgICBpZiAo
bXNjaGFycykgew0KCXByaW50IEZJTEVOQU1FICI6IiwgbXNjaGFycywgInN0
dXBpZCBxdW90ZXMvZGFzaGVzIGNoYXJhY3RlcnMiOw0KICAgIH0NCiAgICBp
ZiAoYmFkY2hhcnMpIHsNCglwcmludCBGSUxFTkFNRSAiOiIsIGJhZGNoYXJz
LCAibGluZXMgY29udGFpbmluZyBub24tVVMtQVNDSUkgY2hhcmFjdGVycyI7
DQogICAgfQ0KICAgIGlmIChsb25nbGluZXMpIHsNCglwcmludCBGSUxFTkFN
RSAiOiIsIGxvbmdsaW5lcywgImxpbmVzIGxvbmdlciB0aGFuIiwgY2hhcmxp
bSwgImNoYXJhY3RlcnMsIG1heCIsIG1heGNoYXJzOw0KICAgIH0NCiAgICBp
ZiAobG9uZ3BhZ2VzKSB7DQoJcHJpbnQgRklMRU5BTUUgIjoiLCBsb25ncGFn
ZXMsICJwYWdlcyBsb25nZXIgdGhhbiIsIGxpbmVsaW0sICJsaW5lcywgbWF4
IiwgbWF4bGluZXMsICJsaW5lcyI7DQogICAgfQ0KICAgIGlmIChiYWRmb3Jt
ZmVlZHMpIHsNCglwcmludCBGSUxFTkFNRSAiOiIsIGJhZGZvcm1mZWVkcywg
ImZvcm1mZWVkcyBub3Qgb24gYSBsaW5lIGJ5IHRoZW1zZWx2ZXMiOw0KICAg
IH0NCiAgICBpZiAobG9uZ2xpbmVzIHx8IGxvbmdwYWdlcykgew0KCWV4aXQo
MSk7DQogICAgfQ0KfQ0K
--0-178515613-1051123189=:71348--



From owner-wgchairs@ietf.org  Wed Apr 23 17:02:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07203
	for <wgchairs-archive@lists.ietf.org>; Wed, 23 Apr 2003 17:02:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198RiQ-0007MD-00
	for wgchairs-list@ran.ietf.org; Wed, 23 Apr 2003 17:23:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198Rfs-0006ov-00
	for wgchairs@ran.ietf.org; Wed, 23 Apr 2003 17:21:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07094
	for <wgchairs@ietf.org>; Wed, 23 Apr 2003 16:59:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198RMm-0007TT-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 17:01:20 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=shego.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 198RMl-0007TQ-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 17:01:20 -0400
Received: from shego.dbc.mtview.ca.us (localhost [127.0.0.1])
	by shego.dbc.mtview.ca.us (8.12.6/8.12.6) with SMTP id h3NL1hXk005400;
	Wed, 23 Apr 2003 14:01:44 -0700 (PDT)
Date: Wed, 23 Apr 2003 14:01:43 -0700
From: Marshall Rose <mrose+mtr.ietf@dbc.mtview.ca.us>
To: Mukesh.Gupta@nokia.com
Cc: wgchairs@ietf.org
Subject: Re: Checking I-Ds for nits.
Message-Id: <20030423140143.4bc587ca.mrose+mtr.ietf@dbc.mtview.ca.us>
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42AC5A6@daebe009.americas.nokia.com>
References: <8D260779A766FB4A9C1739A476F84FA42AC5A6@daebe009.americas.nokia.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Hi All,
> 
> How do people make sure that the draft submitted to the WG are compliant to ID
> nits on this page ? http://www.ietf.org/ID-nits.html
> 
> Is there any tool available to help in doing this ??

ideally, it would be nice if there was an automated service to do something like
this (kind of like the mib-checker from a decade ago... is that still running?)

alternatively, you can write your I-Ds in XML according to the rules in rfc 2629
and use an automated processor to generate the text, cf.,
http://xml.resource.org/

/mtr



From owner-wgchairs@ietf.org  Wed Apr 23 18:00:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09701
	for <wgchairs-archive@lists.ietf.org>; Wed, 23 Apr 2003 18:00:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Scu-0004mB-00
	for wgchairs-list@ran.ietf.org; Wed, 23 Apr 2003 18:22:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198SVA-0004Fw-00
	for wgchairs@ran.ietf.org; Wed, 23 Apr 2003 18:14:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09486
	for <wgchairs@ietf.org>; Wed, 23 Apr 2003 17:51:59 -0400 (EDT)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SC3-0000Bs-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 17:54:20 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SC3-0000Bp-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 17:54:19 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3NLsi725423
	for <wgchairs@ietf.org>; Thu, 24 Apr 2003 00:54:44 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T61c993081eac158f25c2c@esvir05nok.ntc.nokia.com>;
 Thu, 24 Apr 2003 00:54:43 +0300
Received: from daebh001.NOE.Nokia.com ([172.18.242.231]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 24 Apr 2003 00:54:43 +0300
Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 23 Apr 2003 14:54:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Checking I-Ds for nits.
Date: Wed, 23 Apr 2003 16:54:41 -0500
Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABCC6@daebe009.americas.nokia.com>
Thread-Topic: Checking I-Ds for nits.
Thread-Index: AcMJ25W+6gh9xrDHQQuhH25ZDDZzcAABlndg
To: <mrose+mtr.ietf@dbc.mtview.ca.us>
Cc: <wgchairs@ietf.org>
X-OriginalArrivalTime: 23 Apr 2003 21:54:42.0440 (UTC) FILETIME=[F2086080:01C309E2]
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA09701

I think, most of the newcomers start with microsoft word which probably is the worst choice :-(

Do we ask the contributors to submit just the txt file or also the xml/rtf etc file too ? If the author submits the txt file, how should chair make sure that all the ID-nits requirements are met before the chair submits the draft to IESG ?

Checking the formatting manually doesn't seem like a viable choice.

> -----Original Message-----
> From: ext Marshall Rose [mailto:mrose+mtr.ietf@dbc.mtview.ca.us]
> Sent: Wednesday, April 23, 2003 2:02 PM
> To: Gupta Mukesh (IPRG/MtView)
> Cc: wgchairs@ietf.org
> Subject: Re: Checking I-Ds for nits.
> 
> 
> > Hi All,
> > 
> > How do people make sure that the draft submitted to the WG 
> are compliant to ID
> > nits on this page ? http://www.ietf.org/ID-nits.html
> > 
> > Is there any tool available to help in doing this ??
> 
> ideally, it would be nice if there was an automated service 
> to do something like
> this (kind of like the mib-checker from a decade ago... is 
> that still running?)
> 
> alternatively, you can write your I-Ds in XML according to 
> the rules in rfc 2629
> and use an automated processor to generate the text, cf.,
> http://xml.resource.org/
> 
> /mtr
> 



From owner-wgchairs@ietf.org  Wed Apr 23 18:10:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10827
	for <wgchairs-archive@lists.ietf.org>; Wed, 23 Apr 2003 18:10:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198SkD-00014L-00
	for wgchairs-list@ran.ietf.org; Wed, 23 Apr 2003 18:29:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198SiJ-0000C2-00
	for wgchairs@ran.ietf.org; Wed, 23 Apr 2003 18:27:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10160
	for <wgchairs@ietf.org>; Wed, 23 Apr 2003 18:05:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SPC-0000HV-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 18:07:54 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=shego.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 198SPC-0000HS-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 18:07:54 -0400
Received: from shego.dbc.mtview.ca.us (localhost [127.0.0.1])
	by shego.dbc.mtview.ca.us (8.12.6/8.12.6) with SMTP id h3NM8DXk005618;
	Wed, 23 Apr 2003 15:08:14 -0700 (PDT)
Date: Wed, 23 Apr 2003 15:08:11 -0700
From: Marshall Rose <mrose+mtr.ietf@dbc.mtview.ca.us>
To: <Mukesh.Gupta@nokia.com>
Cc: wgchairs@ietf.org
Subject: Re: Checking I-Ds for nits.
Message-Id: <20030423150811.69576489.mrose+mtr.ietf@dbc.mtview.ca.us>
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42ABCC6@daebe009.americas.nokia.com>
References: <8D260779A766FB4A9C1739A476F84FA42ABCC6@daebe009.americas.nokia.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I think, most of the newcomers start with microsoft word which probably is the
> worst choice :-(
> 
> Do we ask the contributors to submit just the txt file or also the xml/rtf etc
> file too ? If the author submits the txt file, how should chair make sure that
> all the ID-nits requirements are met before the chair submits the draft to
> IESG ?
i think that internet-drafts@ietf.org will accept the .xml file along with the
.txt file. but there's no need to submit both. just submit the .txt...


> Checking the formatting manually doesn't seem like a viable choice.

well, that's pretty much the way it ends up getting done, either by the
secretariat, an AD, or, ultimately, the RFC editor...

/mtr



From owner-wgchairs@ietf.org  Wed Apr 23 18:51:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12529
	for <wgchairs-archive@lists.ietf.org>; Wed, 23 Apr 2003 18:51:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198TL4-0007Df-00
	for wgchairs-list@ran.ietf.org; Wed, 23 Apr 2003 19:07:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198TJV-00077P-00
	for wgchairs@ran.ietf.org; Wed, 23 Apr 2003 19:06:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12401
	for <wgchairs@ietf.org>; Wed, 23 Apr 2003 18:44:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198T0N-0000ZC-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 18:46:19 -0400
Received: from tux.w3.org ([18.29.0.27] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 198T0N-0000Z9-00
	for wgchairs@ietf.org; Wed, 23 Apr 2003 18:46:19 -0400
Received: from localhost (IDENT:root@tux.w3.org [18.29.0.27])
	by tux.w3.org (8.12.9/8.12.9) with ESMTP id h3NMkhsi020827;
	Wed, 23 Apr 2003 18:46:43 -0400
From: Joseph Reagle <reagle@w3.org>
Organization: W3C
To: Mukesh.Gupta@nokia.com, <mrose+mtr.ietf@dbc.mtview.ca.us>
Subject: Re: Checking I-Ds for nits.
Date: Wed, 23 Apr 2003 18:46:41 -0400
User-Agent: KMail/1.5.1
Cc: <wgchairs@ietf.org>
References: <8D260779A766FB4A9C1739A476F84FA42ABCC6@daebe009.americas.nokia.com>
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42ABCC6@daebe009.americas.nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200304231846.42101.reagle@w3.org>
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wednesday 23 April 2003 17:54, Mukesh.Gupta@nokia.com wrote:
> Do we ask the contributors to submit just the txt file or also the
> xml/rtf etc file too ?

If you are using XML, then it's not to hard to write an XSLT that can check 
for a number of things. The W3C's RFC rules are "pubrules" and there's an 
XSLT that checks most of those rules:
	http://www.w3.org/2001/07/pubrules-form




From owner-wgchairs@ietf.org  Fri Apr 25 07:43:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03591
	for <wgchairs-archive@lists.ietf.org>; Fri, 25 Apr 2003 07:43:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1991vW-0004P2-00
	for wgchairs-list@ran.ietf.org; Fri, 25 Apr 2003 08:03:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198ntC-0007Hn-00
	for wgchairs@ran.ietf.org; Thu, 24 Apr 2003 17:04:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02365
	for <wgchairs@ietf.org>; Thu, 24 Apr 2003 16:41:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198nZq-00018v-00
	for wgchairs@ietf.org; Thu, 24 Apr 2003 16:44:18 -0400
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198nZp-00018H-00
	for wgchairs@ietf.org; Thu, 24 Apr 2003 16:44:17 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3OKiD701396
	for <wgchairs@ietf.org>; Thu, 24 Apr 2003 16:44:14 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R19YT5N>; Thu, 24 Apr 2003 22:44:13 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155016A3ADF@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Marshall Rose <mrose+mtr.ietf@dbc.mtview.ca.us>, Mukesh.Gupta@nokia.com
Cc: wgchairs@ietf.org
Subject: RE: Checking I-Ds for nits.
Date: Thu, 24 Apr 2003 22:44:10 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-wgchairs@ietf.org
Precedence: bulk

Inline

> -----Original Message-----
> From: Marshall Rose [mailto:mrose+mtr.ietf@dbc.mtview.ca.us]
> Sent: woensdag 23 april 2003 23:02
> To: Mukesh.Gupta@nokia.com
> Cc: wgchairs@ietf.org
> Subject: Re: Checking I-Ds for nits.
>
>
> > Hi All,
> >
> > How do people make sure that the draft submitted to the WG
> are compliant to ID
> > nits on this page ? http://www.ietf.org/ID-nits.html
> >
> > Is there any tool available to help in doing this ??
>
> ideally, it would be nice if there was an automated service
> to do something like this (kind of like the mib-checker from
> a decade ago... is that still running?)
>
Not sure if it is still running. But if it were, would it be using
current SMI rules and current SMI documents to check against?

There is a new one at: smilint@ibr.cs.tu-bs.de

Send email with the "Subject: help" to <smilint@ibr.cs.tu-bs.de>
to get help information.

>
> alternatively, you can write your I-Ds in XML according to
> the rules in rfc 2629 and use an automated processor to
> generate the text, cf.,
> http://xml.resource.org/
>
I have used it, and I can testify that it helps a lot with being
compliant with many of the nits. Not all, but many.

Bert
> /mtr
>





From owner-wgchairs@ietf.org  Fri Apr 25 19:32:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27555
	for <wgchairs-archive@lists.ietf.org>; Fri, 25 Apr 2003 19:32:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199Cyk-0004B0-00
	for wgchairs-list@ran.ietf.org; Fri, 25 Apr 2003 19:51:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199CyB-000498-00
	for wgchairs@ran.ietf.org; Fri, 25 Apr 2003 19:51:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27472
	for <wgchairs@ietf.org>; Fri, 25 Apr 2003 19:29:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199CfK-0004N1-00
	for wgchairs@ietf.org; Fri, 25 Apr 2003 19:31:38 -0400
Received: from osmtp1.electric.net ([216.129.90.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 199CfJ-0004Mu-00
	for wgchairs@ietf.org; Fri, 25 Apr 2003 19:31:37 -0400
Received: from [166.154.131.248] (helo=EGRodriguez)
	by osmtp1.electric.net with asmtp (Exim 4.10)
	id 199Cf7-0003GV-0W; Fri, 25 Apr 2003 16:31:26 -0700
From: "Elizabeth Rodriguez" <ElizabethRodriguez@ieee.org>
To: <Mukesh.Gupta@nokia.com>, <mrose+mtr.ietf@dbc.mtview.ca.us>
Cc: <wgchairs@ietf.org>
Subject: RE: Checking I-Ds for nits.
Date: Fri, 25 Apr 2003 16:29:50 -0700
Keywords: IETF-Chairs
Message-ID: <007601c30b82$ae8cc160$f8839aa6@EGRodriguez>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42ABCC6@daebe009.americas.nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA27555

I have found this to be the case as well (use MS Word).
Unfortunately, as of about a month or so ago, I reviewed the currently
available MS Word template and it is itself full of nits.

I have not found any good automated way of checking for nits.
I have a few tools I have developed (very rudimentary perl) which checks for
#columns, ending -, etc. but for the most part need to review manually
before sending to the ADs.

EGR
-----Original Message-----
From: owner-wgchairs@ietf.org [mailto:owner-wgchairs@ietf.org] On Behalf Of
Mukesh.Gupta@nokia.com
Sent: Wednesday, April 23, 2003 2:55 PM
To: mrose+mtr.ietf@dbc.mtview.ca.us
Cc: wgchairs@ietf.org
Subject: RE: Checking I-Ds for nits.

 
I think, most of the newcomers start with microsoft word which probably is
the worst choice :-(

Do we ask the contributors to submit just the txt file or also the xml/rtf
etc file too ? If the author submits the txt file, how should chair make
sure that all the ID-nits requirements are met before the chair submits the
draft to IESG ?

Checking the formatting manually doesn't seem like a viable choice.

> -----Original Message-----
> From: ext Marshall Rose [mailto:mrose+mtr.ietf@dbc.mtview.ca.us]
> Sent: Wednesday, April 23, 2003 2:02 PM
> To: Gupta Mukesh (IPRG/MtView)
> Cc: wgchairs@ietf.org
> Subject: Re: Checking I-Ds for nits.
> 
> 
> > Hi All,
> > 
> > How do people make sure that the draft submitted to the WG 
> are compliant to ID
> > nits on this page ? http://www.ietf.org/ID-nits.html
> > 
> > Is there any tool available to help in doing this ??
> 
> ideally, it would be nice if there was an automated service 
> to do something like
> this (kind of like the mib-checker from a decade ago... is 
> that still running?)
> 
> alternatively, you can write your I-Ds in XML according to 
> the rules in rfc 2629
> and use an automated processor to generate the text, cf.,
> http://xml.resource.org/
> 
> /mtr
> 






From owner-wgchairs@ietf.org  Tue Apr 29 15:49:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08279
	for <wgchairs-archive@lists.ietf.org>; Tue, 29 Apr 2003 15:49:17 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AaYj-0008Mx-00
	for wgchairs-list@ran.ietf.org; Tue, 29 Apr 2003 15:14:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AaBX-0001RA-00
	for wgchairs@ran.ietf.org; Tue, 29 Apr 2003 14:50:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05269
	for <wgchairs@ietf.org>; Tue, 29 Apr 2003 14:47:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AaAm-00071P-00
	for wgchairs@ietf.org; Tue, 29 Apr 2003 14:49:48 -0400
Received: from [12.25.1.120] (helo=ctron-dnm.enterasys.com ident=firewall-user)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AaAm-00071L-00
	for wgchairs@ietf.org; Tue, 29 Apr 2003 14:49:48 -0400
Received: (from uucp@localhost)
	by ctron-dnm.enterasys.com (8.8.7/8.8.7) id PAA20494
	for <wgchairs@ietf.org>; Tue, 29 Apr 2003 15:03:48 -0400 (EDT)
Received: from unknown(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1)
	id xma020365; Tue, 29 Apr 03 15:02:45 -0400
Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2.ets.enterasys.com with InterScan Messaging Security Suite for SMTP; Tue, 29 Apr 2003 14:50:16 -0400
Received: from nhrocmbx1.enterasys.com ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 29 Apr 2003 14:50:16 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C30E80.2CB767F0"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: FW: Simple Times announcement
Date: Tue, 29 Apr 2003 14:50:16 -0400
Message-ID: <6D745637A7E0F94DA070743C55CDA9BA6031CC@NHROCMBX1.ets.enterasys.com>
Thread-Topic: Simple Times announcement
Thread-Index: AcMOMhV/z01i/4qrQ+K8BAYRVAsaiwATPbuQAAA8TlA=
From: "Harrington, David" <dbh@enterasys.com>
To: <wgchairs@ietf.org>
X-OriginalArrivalTime: 29 Apr 2003 18:50:16.0663 (UTC) FILETIME=[2CCB4E70:01C30E80]
Sender: owner-wgchairs@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C30E80.2CB767F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
Hi,=20

A  new issue of the Simple Times is available. This is the SNMP related =
newsletter. If you think your WG might be interested, please distribute =
the announcement to your WG mailing list.

dbh=20
---=20
David Harrington          =20
dbh@enterasys.com         =20
co-chair, IETF SNMPv3 WG=20


---------------------------------------------------=20
Latest issue of the Simple-Times=20

Since there are quite some people who do not regularly visit the=20
Simple-Times website ( http://www.simple-times.org/), we would like to=20
announce that the latest version is from December 2002 and contains=20
articles on:=20
- IAB Network Management Workshop=20
    By Ran Atkinson, Extreme Networks=20
- GetBulk Worth Fixing=20
    By Marek Malowidzki, Military Communication Institute=20
- Net-SNMP: Old Wine in a New Wineskin?=20
    By Wes Hardaker, Network Associates, Dave Shield,=20
    Liverpool University=20
- Evaluating MIB II (RFC1213) Implementations=20
    By Henrik E. Holland, Remco van de Meent, Aiko Pras,=20
    University of Twente=20
- The Story Behind the SNMP Vulnerabilities=20
   By Tiina Havana, Ari Takanen, OUSPG=20

Juergen Schoenwaelder & Aiko Pras=20


------_=_NextPart_001_01C30E80.2CB767F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>FW: Simple Times announcement</TITLE>

<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
size=3D2>Hi,</FONT>=20
</DIV>
<P><FONT size=3D2>A&nbsp; new issue of the Simple Times is available. =
This is the=20
SNMP related newsletter. If you think your WG might be interested, =
please=20
distribute the announcement to your WG mailing list.</FONT></P>
<P><FONT size=3D2>dbh</FONT> <BR><FONT size=3D2>---</FONT> <BR><FONT =
size=3D2>David=20
Harrington&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</FONT><BR><FONT=20
size=3D2>dbh@enterasys.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
</FONT><BR><FONT size=3D2>co-chair, IETF SNMPv3 WG</FONT> </P><BR>
<P><FONT =
size=3D2>---------------------------------------------------</FONT>=20
<BR><FONT size=3D2>Latest issue of the Simple-Times</FONT> </P>
<P><FONT size=3D2>Since there are quite some people who do not regularly =
visit=20
the</FONT> <BR><FONT size=3D2>Simple-Times website (<A=20
href=3D"http://www.simple-times.org/">http://www.simple-times.org/</A>), =
we would=20
like to</FONT> <BR><FONT size=3D2>announce that the latest version is =
from=20
December 2002 and contains</FONT> <BR><FONT size=3D2>articles on:</FONT> =
<BR><FONT=20
size=3D2>- IAB Network Management Workshop</FONT> <BR><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp; By Ran Atkinson, Extreme Networks</FONT> =
<BR><FONT=20
size=3D2>- GetBulk Worth Fixing</FONT> <BR><FONT =
size=3D2>&nbsp;&nbsp;&nbsp; By=20
Marek Malowidzki, Military Communication Institute</FONT> <BR><FONT =
size=3D2>-=20
Net-SNMP: Old Wine in a New Wineskin?</FONT> <BR><FONT =
size=3D2>&nbsp;&nbsp;&nbsp;=20
By Wes Hardaker, Network Associates, Dave Shield,</FONT> <BR><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp; Liverpool University</FONT> <BR><FONT =
size=3D2>-=20
Evaluating MIB II (RFC1213) Implementations</FONT> <BR><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp; By Henrik E. Holland, Remco van de Meent, =
Aiko=20
Pras,</FONT> <BR><FONT size=3D2>&nbsp;&nbsp;&nbsp; University of =
Twente</FONT>=20
<BR><FONT size=3D2>- The Story Behind the SNMP Vulnerabilities</FONT> =
<BR><FONT=20
size=3D2>&nbsp;&nbsp; By Tiina Havana, Ari Takanen, OUSPG</FONT> </P>
<P><FONT size=3D2>Juergen Schoenwaelder &amp; Aiko Pras</FONT> =
</P></BODY></HTML>

------_=_NextPart_001_01C30E80.2CB767F0--



