From wgchairs-admin@ietf.org  Thu Apr  1 18:00:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06421
	for <wgchairs-archive@lists.ietf.org>; Thu, 1 Apr 2004 18:00:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B994W-0005kL-EV; Thu, 01 Apr 2004 15:45:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B95hG-0001Y8-AX
	for wgchairs@optimus.ietf.org; Thu, 01 Apr 2004 12:09:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16649
	for <wgchairs@ietf.org>; Thu, 1 Apr 2004 10:28:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B946z-00065r-00
	for wgchairs@ietf.org; Thu, 01 Apr 2004 10:28:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9463-0005zG-00
	for wgchairs@ietf.org; Thu, 01 Apr 2004 10:27:12 -0500
Received: from ns.cnri.reston.va.us ([132.151.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B945G-0005vE-00; Thu, 01 Apr 2004 10:26:22 -0500
Received: from rbunch.cnri.reston.va.us ([132.151.2.53])
	by ns.cnri.reston.va.us with esmtp (Exim 4.20)
	id 1B945A-0006oy-Fr; Thu, 01 Apr 2004 10:26:16 -0500
Message-Id: <6.0.0.9.2.20040401102339.02c49228@odin>
X-Sender: rbunch@odin
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.9 (Beta)
X-Priority: 1 (Highest)
Date: Thu, 01 Apr 2004 10:26:08 -0500
To: wgchairs@ietf.org, bofchairs@ietf.org
From: Rebecca Bunch <rbunch@foretec.com>
Subject: "Call for Input to the 59th IETF Meeting Proceedings"
Cc: harald@alvestrand.no, "Barbara B. Fuller" <bfuller@foretec.com>,
        iesg@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_12045009==.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE,X_PRIORITY_HIGH autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

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

***This message is for all Working Groups and BoFs that met at IETF 59th 
Seoul, Korea. ***

Dear Working Group and BoF Chairs:

The deadline for submission of minutes and presentation slides for 
inclusion in the proceedings of the 59th IETF Meeting is Friday, April 2, 
2004 at 17:00 ET.  Please send all materials to proceedings@ietf.org by 
that time.  Any materials received after that time will not be 
included.  Please note that submission of minutes is mandatory, while 
submission of presentation slides is optional.

Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.  Minutes 
submitted in plain text will be reformatted by the Secretariat.  Therefore, 
if you are concerned about preserving the formatting of your minutes, then 
please submit them in HTML.

Presentation slides may be submitted in any of the following formats:

.TXT Plain text (Unix/Mac/Dos)
.DOC MS Word Document (v95 - 2000)
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6)
.PPT MS PowerPoint (v95 - 2000)

When submitting slides for multiple presentations, please indicate the 
order that the presentations should appear in the proceedings.


Seventy-six (76) working groups and BoFs met at IETF 59.  As of today 15 
have not yet submitted any materials, 10 has submitted minutes but no 
slides, and 3 have submitted slides but no minutes.

As of 10:24am, April 1st, 2004:
The following have not submitted ANY materials:
apparea, calsch, disman, dna, dnsop, geopriv, iea, iiri, ldapbis, manet, 
mip4, mip6, mmusic, pmtud, sasl

The following have submitted slides only:
ippm, krb-wg, marid, nemo, netconf, newtrk, pki4ipsec, rmonmib, saag, tsvwg

The following have submitted minutes only:
grow, mboned, mpls
If your group is listed above and you submitted materials, please contact 
me ASAP.

The current status of the proceedings, including the list of groups in each 
category, is available at:

http://www.ietf.org/proceedings/04mar/index.html

If you have already submitted materials, then we encourage you to review 
them on line and send any corrections to proceedings@ietf.org.

Thank you in advance for your cooperation.

The IETF Secretariat

Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071
Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071 
--=====================_12045009==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
***This message is for all Working Groups and BoFs that met at IETF 59th
Seoul, Korea. ***<br><br>
Dear Working Group and BoF Chairs:<br><br>
The deadline for submission of minutes and presentation slides for
inclusion in the proceedings of the 59th IETF Meeting is <b>Friday, April
2, 2004 at 17:00 ET</b>.&nbsp; Please send all materials to
proceedings@ietf.org by that time.&nbsp; Any materials received after
that time will not be included.&nbsp; Please note that submission of
minutes is mandatory, while submission of presentation slides is
optional.<br><br>
Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.&nbsp;
Minutes submitted in plain text will be reformatted by the
Secretariat.&nbsp; Therefore, if you are concerned about preserving the
formatting of your minutes, then please submit them in HTML.<br><br>
Presentation slides may be submitted in any of the following
formats:<br>
&nbsp;<br>
.TXT Plain text (Unix/Mac/Dos) <br>
.DOC MS Word Document (v95 - 2000) <br>
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6) <br>
.PPT MS PowerPoint (v95 - 2000)<br><br>
When submitting slides for multiple presentations, please indicate the
order that the presentations should appear in the proceedings.<br><br>
<br>
Seventy-six (76) working groups and BoFs met at IETF 59.&nbsp; As of
today <b>15</b> have not yet submitted any materials, <b>10 </b>has
submitted minutes but no slides, and <b>3</b> have submitted slides but
no minutes. <br><br>
As of 10:24am, April 1st, 2004:
<dl>
<dd><b>The following have not submitted ANY materials:
<dd>apparea, calsch, disman, dna, dnsop, geopriv, iea, iiri, ldapbis,
manet, mip4, mip6, mmusic, pmtud, sasl<br><br>

<dd>The following have submitted slides only:
<dd>ippm, krb-wg, marid, nemo, netconf, newtrk, pki4ipsec, rmonmib, saag,
tsvwg<br><br>

<dd>The following have submitted minutes only:
<dd>grow, mboned, mpls</b>
</dl>If your group is listed above and you submitted materials, please
contact me ASAP.<br><br>
The current status of the proceedings, including the list of groups in
each category, is available at:<br><br>
<font color="#0000FF"><u><a href="http://www.ietf.org/proceedings/04mar/index.html" eudora="autourl">http://www.ietf.org/proceedings/04mar/index.html<br><br>
</a></u></font>If you have already submitted materials, then we encourage
you to review them on line and send any corrections to
proceedings@ietf.org.<br><br>
Thank you in advance for your cooperation.<br><br>
The IETF Secretariat <br>
<x-sigsep><p></x-sigsep>
Rebecca F. Bunch<br>
Foretec Seminars, Inc.<br>
1895 Preston White Dr.<br>
Suite 100<br>
Reston, VA&nbsp; 20191<br>
703-620-9053, x5365<br>
703-620-9071 </body>
<br>
<div>Rebecca F. Bunch</div>
<div>Foretec Seminars, Inc.</div>
<div>1895 Preston White Dr.</div>
<div>Suite 100</div>
<div>Reston, VA&nbsp; 20191</div>
<div>703-620-9053, x5365</div>
703-620-9071
</html>

--=====================_12045009==.ALT--




From wgchairs-admin@ietf.org  Fri Apr  2 10:56:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15246
	for <wgchairs-archive@lists.ietf.org>; Fri, 2 Apr 2004 10:56:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9Nwq-0006Ei-PR; Fri, 02 Apr 2004 07:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9Kq1-0005YE-PC
	for wgchairs@optimus.ietf.org; Fri, 02 Apr 2004 04:19:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00694
	for <wgchairs@ietf.org>; Fri, 2 Apr 2004 04:19:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Kpy-000083-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 04:19:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9Kp4-00000A-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 04:18:46 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Ko9-0007Z5-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 04:17:49 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i329HK627254
	for <wgchairs@ietf.org>; Fri, 2 Apr 2004 12:17:20 +0300
Date: Fri, 2 Apr 2004 12:17:20 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: wgchairs@ietf.org
Subject: I-D tracker automatic reminders
Message-ID: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

Hi,

I raised this issue in IETF59 WG chairs' training, but I think it 
might be useful to discuss it with a wider audience as well.

I think it would be useful for I-D tracker to send "reminders" of open
issues to the responsible person(s) after a document stays too long in
a state, when by the process, it should have moved into a new state.
(What could constitute "too long" varies by the state, but could be
1-4 weeks for example.)

For example, if a document stays too long in states:
 - AD evaluation or Expert Review, remind the AD
 - Publication Requested, remind the AD
 - Last Call Requested, remind the secretariat
 - In Last Call, after the last call has long since expired, remind 
the AD and WG chairs
 - Waiting for AD go-ahead, remind the AD
 - IESG evaluation, remind the AD
 - Defer, remind the secretariat [[ this should not be possible ]]
 - DNP - Waiting for AD note, remind the AD
 - DNP - Announcemnt to be sent, remind the secretariat
 - Approved - "", remind the secretariat
 - Different AD -followup, revised ID needed etc. states -- remind AD, 
   and WG chairs

Obviously, in most cases, "remind the AD" really means "remind the AD
to remind other people to hurry up" -- but in these cases, the AD may
be the only responsible person visible to the tracker, so there really
isn't anyone else to remind here :)

It might be nice to be able to track the RFC-editor process (esp. if
IANA causes blockage, or some normative refs cause trouble), but one
might argue that that's beyond the scope of I-D tracker even if
important.

Actually, as I think more information can't hurt, all of these
reminders could be sent to some kind of mail alias, including at least
the AD and WG chairs.

Other thoughts?  Is too many "reminders" or messages about document
progress (or lack thereof) too bothersome?

Personally, I'd find these important as more often than not, someone 
(whether AD, WG chair, document editor, ....) forgets to pursue 
something and the ball gets dropped until someone reminds that the 
document should be moving forward.. :-)

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From wgchairs-admin@ietf.org  Fri Apr  2 16:36:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01991
	for <wgchairs-archive@lists.ietf.org>; Fri, 2 Apr 2004 16:36:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9WKZ-00058b-Bh; Fri, 02 Apr 2004 16:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9TNo-0004nV-06
	for wgchairs@optimus.ietf.org; Fri, 02 Apr 2004 13:27:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22173
	for <wgchairs@ietf.org>; Fri, 2 Apr 2004 13:27:09 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9TNl-0001nq-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 13:27:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9TMz-0001gY-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 13:26:22 -0500
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9TMa-0001Xe-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 13:25:56 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i32IPlF27917;
	Fri, 2 Apr 2004 21:25:47 +0300 (EET DST)
X-Scanned: Fri, 2 Apr 2004 21:25:42 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i32IPgEx024029;
	Fri, 2 Apr 2004 21:25:42 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00x3GK68; Fri, 02 Apr 2004 21:25:41 EEST
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i32IPes22337;
	Fri, 2 Apr 2004 21:25:40 +0300 (EET DST)
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Fri, 2 Apr 2004 21:25:34 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Fri, 2 Apr 2004 21:25:35 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D tracker automatic reminders
Date: Fri, 2 Apr 2004 21:25:34 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143BAB4@esebe023.ntc.nokia.com>
Thread-Topic: I-D tracker automatic reminders
Thread-Index: AcQYyyd5ZMt4LtivTBGdEfVa3NbKgwAFIyPw
To: <pekkas@netcore.fi>, <wgchairs@ietf.org>
X-OriginalArrivalTime: 02 Apr 2004 18:25:35.0468 (UTC) FILETIME=[E3F822C0:01C418DF]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Pekka,

I completely agree with you.  This would be a really good thing to do.

John

> -----Original Message-----
> From: wgchairs-admin@ietf.org=20
> [mailto:wgchairs-admin@ietf.org]On Behalf
> Of ext Pekka Savola
> Sent: 02 April, 2004 12:17
> To: wgchairs@ietf.org
> Subject: I-D tracker automatic reminders
>=20
>=20
> Hi,
>=20
> I raised this issue in IETF59 WG chairs' training, but I think it=20
> might be useful to discuss it with a wider audience as well.
>=20
> I think it would be useful for I-D tracker to send "reminders" of open
> issues to the responsible person(s) after a document stays too long in
> a state, when by the process, it should have moved into a new state.
> (What could constitute "too long" varies by the state, but could be
> 1-4 weeks for example.)
>=20
> For example, if a document stays too long in states:
>  - AD evaluation or Expert Review, remind the AD
>  - Publication Requested, remind the AD
>  - Last Call Requested, remind the secretariat
>  - In Last Call, after the last call has long since expired, remind=20
> the AD and WG chairs
>  - Waiting for AD go-ahead, remind the AD
>  - IESG evaluation, remind the AD
>  - Defer, remind the secretariat [[ this should not be possible ]]
>  - DNP - Waiting for AD note, remind the AD
>  - DNP - Announcemnt to be sent, remind the secretariat
>  - Approved - "", remind the secretariat
>  - Different AD -followup, revised ID needed etc. states --=20
> remind AD,=20
>    and WG chairs
>=20
> Obviously, in most cases, "remind the AD" really means "remind the AD
> to remind other people to hurry up" -- but in these cases, the AD may
> be the only responsible person visible to the tracker, so there really
> isn't anyone else to remind here :)
>=20
> It might be nice to be able to track the RFC-editor process (esp. if
> IANA causes blockage, or some normative refs cause trouble), but one
> might argue that that's beyond the scope of I-D tracker even if
> important.
>=20
> Actually, as I think more information can't hurt, all of these
> reminders could be sent to some kind of mail alias, including at least
> the AD and WG chairs.
>=20
> Other thoughts?  Is too many "reminders" or messages about document
> progress (or lack thereof) too bothersome?
>=20
> Personally, I'd find these important as more often than not, someone=20
> (whether AD, WG chair, document editor, ....) forgets to pursue=20
> something and the ball gets dropped until someone reminds that the=20
> document should be moving forward.. :-)
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>=20
>=20
>=20



From wgchairs-admin@ietf.org  Fri Apr  2 16:38:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02373
	for <wgchairs-archive@lists.ietf.org>; Fri, 2 Apr 2004 16:38:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9UTP-0007Wy-QX; Fri, 02 Apr 2004 14:37:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9RHu-0001aV-9U
	for wgchairs@optimus.ietf.org; Fri, 02 Apr 2004 11:12:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16509
	for <wgchairs@ietf.org>; Fri, 2 Apr 2004 11:12:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RHt-00061t-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 11:12:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9RGw-0005tu-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 11:11:58 -0500
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RG0-0005fj-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 11:11:00 -0500
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i32GARgb000499;
	Fri, 2 Apr 2004 08:10:27 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.10/Submit) id i32GARva000498;
	Fri, 2 Apr 2004 08:10:27 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 2 Apr 2004 08:10:27 -0800
From: David Meyer <dmm@1-4-5.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: wgchairs@ietf.org
Subject: Re: I-D tracker automatic reminders
Message-ID: <20040402161027.GA396@1-4-5.net>
References: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>


	Pekka,

>> I raised this issue in IETF59 WG chairs' training, but I think it 
>> might be useful to discuss it with a wider audience as well.
>> 
>> I think it would be useful for I-D tracker to send "reminders" of open
>> issues to the responsible person(s) after a document stays too long in
>> a state, when by the process, it should have moved into a new state.
>> (What could constitute "too long" varies by the state, but could be
>> 1-4 weeks for example.)
>> 
>> For example, if a document stays too long in states:
>>  - AD evaluation or Expert Review, remind the AD
>>  - Publication Requested, remind the AD
>>  - Last Call Requested, remind the secretariat
>>  - In Last Call, after the last call has long since expired, remind 
>> the AD and WG chairs
>>  - Waiting for AD go-ahead, remind the AD
>>  - IESG evaluation, remind the AD
>>  - Defer, remind the secretariat [[ this should not be possible ]]
>>  - DNP - Waiting for AD note, remind the AD
>>  - DNP - Announcemnt to be sent, remind the secretariat
>>  - Approved - "", remind the secretariat
>>  - Different AD -followup, revised ID needed etc. states -- remind AD, 
>>    and WG chairs
>> 
>> Obviously, in most cases, "remind the AD" really means "remind the AD
>> to remind other people to hurry up" -- but in these cases, the AD may
>> be the only responsible person visible to the tracker, so there really
>> isn't anyone else to remind here :)
>> 
>> It might be nice to be able to track the RFC-editor process (esp. if
>> IANA causes blockage, or some normative refs cause trouble), but one
>> might argue that that's beyond the scope of I-D tracker even if
>> important.
>> 
>> Actually, as I think more information can't hurt, all of these
>> reminders could be sent to some kind of mail alias, including at least
>> the AD and WG chairs.
>> 
>> Other thoughts?  Is too many "reminders" or messages about document
>> progress (or lack thereof) too bothersome?
>> 
>> Personally, I'd find these important as more often than not, someone 
>> (whether AD, WG chair, document editor, ....) forgets to pursue 
>> something and the ball gets dropped until someone reminds that the 
>> document should be moving forward.. :-)

	Interestingly, we (the proto-team) are looking at various
	pilot projects that are designed to address parts of what
	you describe above. One of these pilot projects has as
	its objective to allow the WG chair to do much of what is
	being call "shepherding" (shepherding covers much of what
	you describe above; see draft-ietf-proto-shepherding-00.txt). 

	Some of our initial ideas for a pilot project that seeks
	to most closely address your issues is documented in 
	draft-ietf-proto-wgchair-discuss-pilot-00.txt.

	As always, your comments greatly appreciated.

	Dave




From wgchairs-admin@ietf.org  Fri Apr  2 17:09:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06779
	for <wgchairs-archive@lists.ietf.org>; Fri, 2 Apr 2004 17:09:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9VyI-0004mH-7M; Fri, 02 Apr 2004 16:13:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9SWR-0000pw-S5
	for wgchairs@optimus.ietf.org; Fri, 02 Apr 2004 12:32:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20164
	for <wgchairs@ietf.org>; Fri, 2 Apr 2004 12:32:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9SWQ-00023T-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 12:32:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9SVT-0001vB-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 12:31:04 -0500
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9SUd-0001o4-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 12:30:11 -0500
Received: from h-68-164-157-250.snvacaid.dynamic.covad.net ([68.164.157.250] helo=oemcomputer)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B9SUd-0001nL-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 09:30:11 -0800
Message-ID: <002a01c418d8$90aa50e0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <wgchairs@ietf.org>
References: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi>
Subject: Re: I-D tracker automatic reminders
Date: Fri, 2 Apr 2004 09:33:08 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

Hi -

> From: "Pekka Savola" <pekkas@netcore.fi>
> To: <wgchairs@ietf.org>
> Sent: Friday, April 02, 2004 1:17 AM
> Subject: I-D tracker automatic reminders
...
> I think it would be useful for I-D tracker to send "reminders" of open
> issues to the responsible person(s) after a document stays too long in
> a state, when by the process, it should have moved into a new state.
> (What could constitute "too long" varies by the state, but could be
> 1-4 weeks for example.)
...

As a reviewer and WG chair, I'd find this useful.

Randy





From wgchairs-admin@ietf.org  Fri Apr  2 18:10:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11768
	for <wgchairs-archive@lists.ietf.org>; Fri, 2 Apr 2004 18:10:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9XiB-00069q-Sa; Fri, 02 Apr 2004 18:04:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9Xh4-0005ko-9W
	for wgchairs@optimus.ietf.org; Fri, 02 Apr 2004 18:03:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11038
	for <wgchairs@ietf.org>; Fri, 2 Apr 2004 18:03:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Xgv-000648-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 18:03:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9Xfv-0005vk-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 18:02:12 -0500
Received: from ns.cnri.reston.va.us ([132.151.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Xf0-0005p8-00; Fri, 02 Apr 2004 18:01:14 -0500
Received: from rbunch.cnri.reston.va.us ([132.151.2.53])
	by ns.cnri.reston.va.us with esmtp (Exim 4.20)
	id 1B9Xeb-0006Td-8x; Fri, 02 Apr 2004 18:00:49 -0500
Message-Id: <6.0.0.9.2.20040402175312.02c83ff8@odin>
X-Sender: rbunch@odin
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.9 (Beta)
Date: Fri, 02 Apr 2004 18:00:23 -0500
To: wgchairs@ietf.org, bofchairs@ietf.org
From: Rebecca Bunch <rbunch@foretec.com>
Subject: "Call for Input to the 59th IETF Meeting Proceedings"
Cc: harald@alvestrand.no, "Barbara B. Fuller" <bfuller@foretec.com>,
        iesg@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_37621536==.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

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

***This message is for all Working Groups and BoFs that met at IETF 59th 
Seoul, Korea. ***

Dear Working Group and BoF Chairs:

The deadline for submission of minutes and presentation slides for 
inclusion in the proceedings of the 59th IETF Meeting was Friday, April 2, 
2004 at 17:00 ET.   I will be accepting comments, changes and corrections 
until Friday, April 16, 2004 at 15:00 ET.

If I made a mistake in presentation order, minutes aren't showing up 
correctly, or anything else, please contact me directly at rbunch@forete.com.

Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.  Minutes 
submitted in plain text will be reformatted by the Secretariat.  Therefore, 
if you are concerned about preserving the formatting of your minutes, then 
please submit them in HTML.

Presentation slides may be submitted in any of the following formats:

.TXT Plain text (Unix/Mac/Dos)
.DOC MS Word Document (v95 - 2000)
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6)
.PPT MS PowerPoint (v95 - 2000)

When submitting slides for multiple presentations, please indicate the 
order that the presentations should appear in the proceedings.


Seventy-six (76) working groups and BoFs met at IETF 59.  As of today 4 
have not yet submitted any materials, 6 has submitted minutes but no 
slides, and 1 have submitted slides but no minutes. The current status of 
the proceedings, including the list of groups in each category, is 
available at:

http://www.ietf.org/proceedings/04mar/index.html

As of Friday, April 2nd, 2004 @ 18:00 ET the following groups:

Slides but no minutes
marid

Minutes but no slides
calsch (not expecting any slides), grow, iiri, mboned, pmtud, sasl

Have submitted nothing:
apparea, dnsop, iea, manet


If you have already submitted materials, then we encourage you to review 
them on line and send any corrections to proceedings@ietf.org.

Thank you in advance for your cooperation.

The IETF Secretariat

Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071
Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071 
--=====================_37621536==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
***This message is for all Working Groups and BoFs that met at IETF 59th
Seoul, Korea. ***<br><br>
Dear Working Group and BoF Chairs:<br><br>
The deadline for submission of minutes and presentation slides for
inclusion in the proceedings of the 59th IETF Meeting <b>was</b> Friday,
April 2, 2004 at 17:00 ET.&nbsp;&nbsp; I will be accepting comments,
changes and corrections until <b>Friday, April 16, 2004 at 15:00
ET.</b>&nbsp; <br><br>
If I made a mistake in presentation order, minutes aren't showing up
correctly, or anything else, please contact me directly at
rbunch@forete.com.<br><br>
Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.&nbsp;
Minutes submitted in plain text will be reformatted by the
Secretariat.&nbsp; Therefore, if you are concerned about preserving the
formatting of your minutes, then please submit them in HTML.<br><br>
Presentation slides may be submitted in any of the following
formats:<br>
&nbsp;<br>
.TXT Plain text (Unix/Mac/Dos) <br>
.DOC MS Word Document (v95 - 2000) <br>
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6) <br>
.PPT MS PowerPoint (v95 - 2000)<br><br>
When submitting slides for multiple presentations, please indicate the
order that the presentations should appear in the proceedings.<br><br>
<br>
Seventy-six (76) working groups and BoFs met at IETF 59.&nbsp; As of
today <b>4</b> have not yet submitted any materials, <b>6 </b>has
submitted minutes but no slides, and <b>1 </b>have submitted slides but
no minutes. The current status of the proceedings, including the list of
groups in each category, is available at:<br><br>
<font color="#0000FF"><u><a href="http://www.ietf.org/proceedings/04mar/index.html" eudora="autourl">http://www.ietf.org/proceedings/04mar/index.html<br><br>
</a></u></font>As of Friday, April 2nd, 2004 @ 18:00 ET the following
groups:<br><br>
Slides but no minutes<br>
marid<br><br>
Minutes but no slides<br>
calsch (not expecting any slides), grow, iiri, mboned, pmtud,
sasl<br><br>
Have submitted nothing:<br>
apparea, dnsop, iea, manet<br><br>
<br>
If you have already submitted materials, then we encourage you to review
them on line and send any corrections to proceedings@ietf.org.<br><br>
Thank you in advance for your cooperation.<br><br>
The IETF Secretariat <br>
<x-sigsep><p></x-sigsep>
Rebecca F. Bunch<br>
Foretec Seminars, Inc.<br>
1895 Preston White Dr.<br>
Suite 100<br>
Reston, VA&nbsp; 20191<br>
703-620-9053, x5365<br>
703-620-9071 </body>
<br>
<div>Rebecca F. Bunch</div>
<div>Foretec Seminars, Inc.</div>
<div>1895 Preston White Dr.</div>
<div>Suite 100</div>
<div>Reston, VA&nbsp; 20191</div>
<div>703-620-9053, x5365</div>
703-620-9071
</html>

--=====================_37621536==.ALT--




From wgchairs-admin@ietf.org  Fri Apr  2 20:55:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18039
	for <wgchairs-archive@lists.ietf.org>; Fri, 2 Apr 2004 20:55:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9aNA-0001qE-PK; Fri, 02 Apr 2004 20:55:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9aMX-0001dx-Mz
	for wgchairs@optimus.ietf.org; Fri, 02 Apr 2004 20:54:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18023
	for <wgchairs@ietf.org>; Fri, 2 Apr 2004 20:54:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9aMV-0005Vg-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 20:54:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9aLX-0005P2-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 20:53:19 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9aLQ-0005Ib-00
	for wgchairs@ietf.org; Fri, 02 Apr 2004 20:53:12 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 8F93B61B91; Sat,  3 Apr 2004 03:52:42 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
 by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 04082-04; Sat,  3 Apr 2004 03:52:41 +0200 (CEST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 8F46461B8E; Sat,  3 Apr 2004 03:52:40 +0200 (CEST)
Date: Fri, 02 Apr 2004 17:16:02 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Pekka Savola <pekkas@netcore.fi>, wgchairs@ietf.org
Subject: Re: I-D tracker automatic reminders
Message-ID: <986474204.1080926162@localhost>
In-Reply-To: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi>
References: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Pekka,

query: for each document, there is a list of people who get warned about 
state changes.

Do you (and others) think that this list should also be warned about state 
non-changes?

Since a lot of our "stuck" documents are in state "new I-D needed", and the 
CC list often includes the document editors, it could be useful to remind 
them that the document is not going forward....

(as per current procedure, when a document is entered into the tracker, the 
field is supposed to be populated with the address-of-record for the WG 
chairs and the document editors. We haven't tried to add that info to all 
documents currently in the pipeline....)

                          Harald

--On 2. april 2004 12:17 +0300 Pekka Savola <pekkas@netcore.fi> wrote:

> Hi,
>
> I raised this issue in IETF59 WG chairs' training, but I think it
> might be useful to discuss it with a wider audience as well.
>
> I think it would be useful for I-D tracker to send "reminders" of open
> issues to the responsible person(s) after a document stays too long in
> a state, when by the process, it should have moved into a new state.
> (What could constitute "too long" varies by the state, but could be
> 1-4 weeks for example.)
>
> For example, if a document stays too long in states:
>  - AD evaluation or Expert Review, remind the AD
>  - Publication Requested, remind the AD
>  - Last Call Requested, remind the secretariat
>  - In Last Call, after the last call has long since expired, remind
> the AD and WG chairs
>  - Waiting for AD go-ahead, remind the AD
>  - IESG evaluation, remind the AD
>  - Defer, remind the secretariat [[ this should not be possible ]]
>  - DNP - Waiting for AD note, remind the AD
>  - DNP - Announcemnt to be sent, remind the secretariat
>  - Approved - "", remind the secretariat
>  - Different AD -followup, revised ID needed etc. states -- remind AD,
>    and WG chairs
>
> Obviously, in most cases, "remind the AD" really means "remind the AD
> to remind other people to hurry up" -- but in these cases, the AD may
> be the only responsible person visible to the tracker, so there really
> isn't anyone else to remind here :)
>
> It might be nice to be able to track the RFC-editor process (esp. if
> IANA causes blockage, or some normative refs cause trouble), but one
> might argue that that's beyond the scope of I-D tracker even if
> important.
>
> Actually, as I think more information can't hurt, all of these
> reminders could be sent to some kind of mail alias, including at least
> the AD and WG chairs.
>
> Other thoughts?  Is too many "reminders" or messages about document
> progress (or lack thereof) too bothersome?
>
> Personally, I'd find these important as more often than not, someone
> (whether AD, WG chair, document editor, ....) forgets to pursue
> something and the ball gets dropped until someone reminds that the
> document should be moving forward.. :-)
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>
>
>
>
>







From wgchairs-admin@ietf.org  Sat Apr  3 00:16:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24045
	for <wgchairs-archive@lists.ietf.org>; Sat, 3 Apr 2004 00:16:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9dVj-0004Rb-WD; Sat, 03 Apr 2004 00:16:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9dV9-00044C-RQ
	for wgchairs@optimus.ietf.org; Sat, 03 Apr 2004 00:15:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24018
	for <wgchairs@ietf.org>; Sat, 3 Apr 2004 00:15:23 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9dV6-0007IT-00
	for wgchairs@ietf.org; Sat, 03 Apr 2004 00:15:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9dU7-0007BN-00
	for wgchairs@ietf.org; Sat, 03 Apr 2004 00:14:24 -0500
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9dTB-000741-00
	for wgchairs@ietf.org; Sat, 03 Apr 2004 00:13:25 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i335DLF18718;
	Sat, 3 Apr 2004 08:13:21 +0300 (EET DST)
X-Scanned: Sat, 3 Apr 2004 08:13:16 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i335DGC8027721;
	Sat, 3 Apr 2004 08:13:16 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00NOzzJ9; Sat, 03 Apr 2004 08:13:15 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i335DEs24039;
	Sat, 3 Apr 2004 08:13:14 +0300 (EET DST)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Sat, 3 Apr 2004 08:13:13 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D tracker automatic reminders
Date: Sat, 3 Apr 2004 08:13:13 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143BAB6@esebe023.ntc.nokia.com>
Thread-Topic: I-D tracker automatic reminders
Thread-Index: AcQZHsVAWEx0VzDuROK5tjYAKgiLzwAGvZFg
To: <harald@alvestrand.no>, <pekkas@netcore.fi>, <wgchairs@ietf.org>
X-OriginalArrivalTime: 03 Apr 2004 05:13:13.0575 (UTC) FILETIME=[5D34B770:01C4193A]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi Harald,

> query: for each document, there is a list of people who get=20
> warned about state changes.
>=20
> Do you (and others) think that this list should also be=20
> warned about state non-changes?
>=20
> Since a lot of our "stuck" documents are in state "new I-D needed", =
and the=20
> CC list often includes the document editors, it could be useful to =
remind=20
> them that the document is not going forward....

I, for one, do think this is needed.  There are far too many steps in =
the
process (in my opinion) to remember them without a decent tracking =
system.
I imagine that most of us multitask a lot of multitasking, so sometimes
we need a reminder (a time-out, if you will) about expected action so =
that
things don't get stuck. =20

John



From wgchairs-admin@ietf.org  Mon Apr  5 10:10:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02034
	for <wgchairs-archive@lists.ietf.org>; Mon, 5 Apr 2004 10:10:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAUmg-000199-6j; Mon, 05 Apr 2004 10:09:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAUmG-00016J-Q8
	for wgchairs@optimus.ietf.org; Mon, 05 Apr 2004 10:08: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 KAA01945
	for <wgchairs@ietf.org>; Mon, 5 Apr 2004 10:08:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAUmE-00029a-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 10:08:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAUlL-00022R-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 10:07:44 -0400
Received: from drummondgroup.com ([161.58.166.198])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAUkl-0001vJ-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 10:07:07 -0400
Received: from DGIServer1 (68.189.209.147.sbi.ftwrth.tx.charter.com [68.189.209.147] (may be forged))
	by drummondgroup.com (8.12.11/8.11.6) with ESMTP id i35E712q004582;
	Mon, 5 Apr 2004 08:07:05 -0600 (MDT)
Message-Id: <200404051407.i35E712q004582@drummondgroup.com>
From: "Rik Drummond" <rvd2@drummondgroup.com>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        "'Pekka Savola'" <pekkas@netcore.fi>, <wgchairs@ietf.org>
Subject: RE: I-D tracker automatic reminders
Date: Mon, 5 Apr 2004 09:06:55 -0500
Organization: Drummond Group Inc
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <986474204.1080926162@localhost>
Thread-Index: AcQZHrPURNMSxl3KREmp5jvUYzzaigB+G4GQ
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I think warning WG Chairs and editors about state non-changes would be very
helpful. Rik 

-----Original Message-----
From: wgchairs-admin@ietf.org [mailto:wgchairs-admin@ietf.org] On Behalf Of
Harald Tveit Alvestrand
Sent: Friday, April 02, 2004 7:16 PM
To: Pekka Savola; wgchairs@ietf.org
Subject: Re: I-D tracker automatic reminders

Pekka,

query: for each document, there is a list of people who get warned about
state changes.

Do you (and others) think that this list should also be warned about state
non-changes?

Since a lot of our "stuck" documents are in state "new I-D needed", and the
CC list often includes the document editors, it could be useful to remind
them that the document is not going forward....

(as per current procedure, when a document is entered into the tracker, the
field is supposed to be populated with the address-of-record for the WG
chairs and the document editors. We haven't tried to add that info to all
documents currently in the pipeline....)

                          Harald

--On 2. april 2004 12:17 +0300 Pekka Savola <pekkas@netcore.fi> wrote:

> Hi,
>
> I raised this issue in IETF59 WG chairs' training, but I think it 
> might be useful to discuss it with a wider audience as well.
>
> I think it would be useful for I-D tracker to send "reminders" of open 
> issues to the responsible person(s) after a document stays too long in 
> a state, when by the process, it should have moved into a new state.
> (What could constitute "too long" varies by the state, but could be
> 1-4 weeks for example.)
>
> For example, if a document stays too long in states:
>  - AD evaluation or Expert Review, remind the AD
>  - Publication Requested, remind the AD
>  - Last Call Requested, remind the secretariat
>  - In Last Call, after the last call has long since expired, remind 
> the AD and WG chairs
>  - Waiting for AD go-ahead, remind the AD
>  - IESG evaluation, remind the AD
>  - Defer, remind the secretariat [[ this should not be possible ]]
>  - DNP - Waiting for AD note, remind the AD
>  - DNP - Announcemnt to be sent, remind the secretariat
>  - Approved - "", remind the secretariat
>  - Different AD -followup, revised ID needed etc. states -- remind AD,
>    and WG chairs
>
> Obviously, in most cases, "remind the AD" really means "remind the AD 
> to remind other people to hurry up" -- but in these cases, the AD may 
> be the only responsible person visible to the tracker, so there really 
> isn't anyone else to remind here :)
>
> It might be nice to be able to track the RFC-editor process (esp. if 
> IANA causes blockage, or some normative refs cause trouble), but one 
> might argue that that's beyond the scope of I-D tracker even if 
> important.
>
> Actually, as I think more information can't hurt, all of these 
> reminders could be sent to some kind of mail alias, including at least 
> the AD and WG chairs.
>
> Other thoughts?  Is too many "reminders" or messages about document 
> progress (or lack thereof) too bothersome?
>
> Personally, I'd find these important as more often than not, someone 
> (whether AD, WG chair, document editor, ....) forgets to pursue 
> something and the ball gets dropped until someone reminds that the 
> document should be moving forward.. :-)
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>
>
>
>
>









From wgchairs-admin@ietf.org  Mon Apr  5 11:30:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07237
	for <wgchairs-archive@lists.ietf.org>; Mon, 5 Apr 2004 11:30:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAW2Y-0006Hs-7N; Mon, 05 Apr 2004 11:29:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAVXA-0005xO-IB
	for wgchairs@optimus.ietf.org; Mon, 05 Apr 2004 10:57:08 -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 KAA05564
	for <wgchairs@ietf.org>; Mon, 5 Apr 2004 10:56:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAVWl-000166-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 10:56:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAVVo-0000xr-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 10:55:44 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAVV5-0000mg-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 10:54:59 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i35EsMu27524;
	Mon, 5 Apr 2004 17:54:22 +0300
Date: Mon, 5 Apr 2004 17:54:22 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: wgchairs@ietf.org
Subject: Re: I-D tracker automatic reminders
In-Reply-To: <986474204.1080926162@localhost>
Message-ID: <Pine.LNX.4.44.0404051753120.27502-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

On Fri, 2 Apr 2004, Harald Tveit Alvestrand wrote:
> query: for each document, there is a list of people who get warned about 
> state changes.
> 
> Do you (and others) think that this list should also be warned about state 
> non-changes?

Yes.

> Since a lot of our "stuck" documents are in state "new I-D needed", and the 
> CC list often includes the document editors, it could be useful to remind 
> them that the document is not going forward....
> 
> (as per current procedure, when a document is entered into the tracker, the 
> field is supposed to be populated with the address-of-record for the WG 
> chairs and the document editors. We haven't tried to add that info to all 
> documents currently in the pipeline....)

Also, these often are *not* updated.  So, I think that would have to 
become more or less de-facto policy as well (or better yet, automated 
somehow).

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings





From wgchairs-admin@ietf.org  Mon Apr  5 21:40:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02512
	for <wgchairs-archive@lists.ietf.org>; Mon, 5 Apr 2004 21:40:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAfZO-0001ho-1m; Mon, 05 Apr 2004 21:40:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAfYo-0001Vp-GV
	for wgchairs@optimus.ietf.org; Mon, 05 Apr 2004 21:39:30 -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 VAA02300
	for <wgchairs@ietf.org>; Mon, 5 Apr 2004 21:39:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAfYl-00044s-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 21:39:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAf51-0000yM-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 21:08:43 -0400
Received: from mail-dark.research.att.com ([192.20.225.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAejI-0005qh-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 20:46:16 -0400
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103])
	by mail-dark.research.att.com (Postfix) with ESMTP id 82C3DE80DC;
	Mon,  5 Apr 2004 20:45:47 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by mail-green.research.att.com (Postfix) with ESMTP id 6D33FF3B4E;
	Mon,  5 Apr 2004 20:45:47 -0400 (EDT)
Received: (from fenner@localhost)
	by windsor.research.att.com (8.11.6+Sun/8.8.5) id i360jl512654;
	Mon, 5 Apr 2004 17:45:47 -0700 (PDT)
Message-Id: <200404060045.i360jl512654@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: harald@alvestrand.no
Subject: Re: I-D tracker automatic reminders
Cc: wgchairs@ietf.org
References: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi> <986474204.1080926162@localhost>
Date: Mon, 5 Apr 2004 17:45:46 -0800
From: Bill Fenner <fenner@research.att.com>
Versions: dmail (solaris) 2.6d/makemail 2.10
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>


>Since a lot of our "stuck" documents are in state "new I-D needed", and the 
>CC list often includes the document editors, it could be useful to remind 
>them that the document is not going forward....

My concern is that automatic reminders could increase friction for
problematic documents.  A chair that is frustrated by an unresponsive
document editor is not going to be helped by getting a reminder every 2
weeks that the update is still pending.  Perhaps I'm not looking at it
the right way, but I expect that unless we deploy an incredibly flexible
(and complex) system, the frustration at unwanted reminders will be
greater than the benefit of useful ones.

  Bill



From wgchairs-admin@ietf.org  Mon Apr  5 22:57:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09815
	for <wgchairs-archive@lists.ietf.org>; Mon, 5 Apr 2004 22:57:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAglp-000333-0f; Mon, 05 Apr 2004 22:57:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAglL-0002t8-Cc
	for wgchairs@optimus.ietf.org; Mon, 05 Apr 2004 22:56:31 -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 WAA09731
	for <wgchairs@ietf.org>; Mon, 5 Apr 2004 22:56:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAglH-0005uE-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 22:56:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAgQQ-00036F-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 22:34:55 -0400
Received: from swan.mail.pas.earthlink.net ([207.217.120.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAfy8-000012-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 22:05:41 -0400
Received: from h-68-164-78-136.snvacaid.dynamic.covad.net ([68.164.78.136] helo=oemcomputer)
	by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1BAfy7-0003a0-00
	for wgchairs@ietf.org; Mon, 05 Apr 2004 19:05:40 -0700
Message-ID: <003301c41b7c$1835f320$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <wgchairs@ietf.org>
References: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi> <986474204.1080926162@localhost> <200404060045.i360jl512654@windsor.research.att.com>
Subject: Re: I-D tracker automatic reminders
Date: Mon, 5 Apr 2004 19:08:46 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

Hi -

> From: "Bill Fenner" <fenner@research.att.com>
> To: <harald@alvestrand.no>
> Cc: <wgchairs@ietf.org>
> Sent: Monday, April 05, 2004 6:45 PM
> Subject: Re: I-D tracker automatic reminders
...
> My concern is that automatic reminders could increase friction for
> problematic documents.  A chair that is frustrated by an unresponsive
> document editor is not going to be helped by getting a reminder every 2
> weeks that the update is still pending.  Perhaps I'm not looking at it
> the right way, but I expect that unless we deploy an incredibly flexible
> (and complex) system, the frustration at unwanted reminders will be
> greater than the benefit of useful ones.
...

One way to over-engineer this is to permit whoever "has the token"
to populate a "promised completion time" field, distinct from the
"suggested completion time" populated by "the process".  Once
the later of the two times has passed, the reminders could start.

However, when faced with an unresponsive editor, I'd welcome an
email every two weeks.  It'd remind me that I as a WG chair need to
do something.  In those potentially confrontational situations, my
own tendency is to hide in a corner and hope the problem goes away.
The reminder would help me maintain my resolve.

Randy





From wgchairs-admin@ietf.org  Tue Apr  6 02:26:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10905
	for <wgchairs-archive@lists.ietf.org>; Tue, 6 Apr 2004 02:26:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAk27-0002GI-Es; Tue, 06 Apr 2004 02:26:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAk1P-00021u-NE
	for wgchairs@optimus.ietf.org; Tue, 06 Apr 2004 02:25:19 -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 CAA10617
	for <wgchairs@ietf.org>; Tue, 6 Apr 2004 02:25:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAk1L-0006Jg-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 02:25:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAjpz-0004IA-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 02:13:32 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAjOj-0001HQ-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 01:45:21 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i365iei10591;
	Tue, 6 Apr 2004 08:44:40 +0300
Date: Tue, 6 Apr 2004 08:44:40 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Bill Fenner <fenner@research.att.com>
cc: harald@alvestrand.no, <wgchairs@ietf.org>
Subject: Re: I-D tracker automatic reminders
In-Reply-To: <200404060045.i360jl512654@windsor.research.att.com>
Message-ID: <Pine.LNX.4.44.0404060837090.10243-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

On Mon, 5 Apr 2004, Bill Fenner wrote:
> My concern is that automatic reminders could increase friction for
> problematic documents.  A chair that is frustrated by an unresponsive
> document editor is not going to be helped by getting a reminder every 2
> weeks that the update is still pending.  Perhaps I'm not looking at it
> the right way, but I expect that unless we deploy an incredibly flexible
> (and complex) system, the frustration at unwanted reminders will be
> greater than the benefit of useful ones.

I can certainly see this, having been in this specific situation.

The message needs appropriate tune. 

Not:

 "Why aren't these documents progressing?!!? It's your responsibility 
  to make sure they move along!!!"

But rather for example:

 "Could you try prodding the appropriate parties to make sure the 
  revisions are in progress.  Thanks!"

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From wgchairs-admin@ietf.org  Tue Apr  6 11:57:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29640
	for <wgchairs-archive@lists.ietf.org>; Tue, 6 Apr 2004 11:57:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAswi-0000yH-MR; Tue, 06 Apr 2004 11:57:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAswQ-0000vY-Mm
	for wgchairs@optimus.ietf.org; Tue, 06 Apr 2004 11:56:46 -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 LAA29476
	for <wgchairs@ietf.org>; Tue, 6 Apr 2004 11:56:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAswP-0003qv-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 11:56:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAsGd-0007Mg-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 11:13:35 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BArvU-0003aR-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 10:51:44 -0400
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i36Eptra028704
	for <wgchairs@ietf.org>; Tue, 6 Apr 2004 07:51:55 -0700 (MST)
Received: from ma19exm01.e6.bcs.mot.com (ma19exm01.e6.bcs.mot.com [10.14.33.5])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i36EoT6u025287
	for <wgchairs@ietf.org>; Tue, 6 Apr 2004 09:51:10 -0500
Received: by ma19exm01.e6.bcs.mot.com with Internet Mail Service (5.5.2657.2)
	id <F5615XMJ>; Tue, 6 Apr 2004 10:50:29 -0400
Message-ID: <62173B970AE0A044AED8723C3BCF23810408B396@ma19exm01.e6.bcs.mot.com>
From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
To: wgchairs@ietf.org
Subject: RE: I-D tracker automatic reminders
Date: Tue, 6 Apr 2004 10:50:23 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.2)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

 ~exponential backoff?

Donald

-----Original Message-----
From: wgchairs-admin@ietf.org [mailto:wgchairs-admin@ietf.org] On Behalf Of Pekka Savola
Sent: Tuesday, April 06, 2004 1:45 AM
To: Bill Fenner
Cc: harald@alvestrand.no; wgchairs@ietf.org
Subject: Re: I-D tracker automatic reminders


On Mon, 5 Apr 2004, Bill Fenner wrote:
> My concern is that automatic reminders could increase friction for
> problematic documents.  A chair that is frustrated by an unresponsive
> document editor is not going to be helped by getting a reminder every 2
> weeks that the update is still pending.  Perhaps I'm not looking at it
> the right way, but I expect that unless we deploy an incredibly flexible
> (and complex) system, the frustration at unwanted reminders will be
> greater than the benefit of useful ones.

I can certainly see this, having been in this specific situation.

The message needs appropriate tune. 

Not:

 "Why aren't these documents progressing?!!? It's your responsibility 
  to make sure they move along!!!"

But rather for example:

 "Could you try prodding the appropriate parties to make sure the 
  revisions are in progress.  Thanks!"

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From wgchairs-admin@ietf.org  Tue Apr  6 14:39:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15709
	for <wgchairs-archive@lists.ietf.org>; Tue, 6 Apr 2004 14:39:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAvT8-0002Il-Dz; Tue, 06 Apr 2004 14:38:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAvEZ-0003ub-6r
	for wgchairs@optimus.ietf.org; Tue, 06 Apr 2004 14:23: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 OAA14144
	for <wgchairs@ietf.org>; Tue, 6 Apr 2004 14:23:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAvEO-0004bQ-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 14:23:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAvBa-00041w-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 14:20:35 -0400
Received: from thrintun.hactrn.net ([66.92.66.67])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAv5v-0003T3-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 14:14:43 -0400
Received: from thrintun.hactrn.net (localhost [IPv6:::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 55CB718D7
	for <wgchairs@ietf.org>; Tue,  6 Apr 2004 14:14:13 -0400 (EDT)
Date: Tue, 06 Apr 2004 14:14:13 -0400
From: Rob Austein <sra@hactrn.net>
To: wgchairs@ietf.org
Subject: Re: I-D tracker automatic reminders
In-Reply-To: <62173B970AE0A044AED8723C3BCF23810408B396@ma19exm01.e6.bcs.mot.com>
References: <62173B970AE0A044AED8723C3BCF23810408B396@ma19exm01.e6.bcs.mot.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20040406181413.55CB718D7@thrintun.hactrn.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

At Tue, 6 Apr 2004 10:50:23 -0400, Eastlake III Donald-LDE wrote:
> 
>  ~exponential backoff?

capped.



From wgchairs-admin@ietf.org  Tue Apr  6 18:19:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06073
	for <wgchairs-archive@lists.ietf.org>; Tue, 6 Apr 2004 18:19:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAyuL-0001ww-Nn; Tue, 06 Apr 2004 18:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAyuE-0001sX-Ui
	for wgchairs@optimus.ietf.org; Tue, 06 Apr 2004 18:18:54 -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 SAA05986
	for <wgchairs@ietf.org>; Tue, 6 Apr 2004 18:18:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAyuB-0003V8-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 18:18:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAyBJ-0004ZA-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 17:32:31 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAxCN-0005fl-00
	for wgchairs@ietf.org; Tue, 06 Apr 2004 16:29:31 -0400
Received: from pun.isi.edu (pun.isi.edu [128.9.160.150])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i36KSWN12648;
	Tue, 6 Apr 2004 13:28:32 -0700 (PDT)
Received: from pun.isi.edu (localhost [127.0.0.1])
	by pun.isi.edu (8.12.10/8.12.10) with ESMTP id i36KSfBZ091889;
	Tue, 6 Apr 2004 13:28:41 -0700 (PDT)
	(envelope-from faber@pun.isi.edu)
Received: (from faber@localhost)
	by pun.isi.edu (8.12.10/8.12.10/Submit) id i36KSeuc091888;
	Tue, 6 Apr 2004 13:28:40 -0700 (PDT)
	(envelope-from faber)
Date: Tue, 6 Apr 2004 13:28:40 -0700
From: Ted Faber <faber@ISI.EDU>
To: Bill Fenner <fenner@research.att.com>
Cc: harald@alvestrand.no, wgchairs@ietf.org
Subject: Re: I-D tracker automatic reminders
Message-ID: <20040406202840.GD91315@pun.isi.edu>
References: <Pine.LNX.4.44.0404021158380.27033-100000@netcore.fi> <986474204.1080926162@localhost> <200404060045.i360jl512654@windsor.research.att.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ZJcv+A0YCCLh2VIg"
Content-Disposition: inline
In-Reply-To: <200404060045.i360jl512654@windsor.research.att.com>
User-Agent: Mutt/1.4.2.1i
X-url: http://www.isi.edu/~faber
X-ISI-4-28-6-MailScanner: Found to be clean
X-MailScanner-From: faber@isi.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>


--ZJcv+A0YCCLh2VIg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Apr 05, 2004 at 05:45:46PM -0800, Bill Fenner wrote:
> 
> >Since a lot of our "stuck" documents are in state "new I-D needed", and the 
> >CC list often includes the document editors, it could be useful to remind 
> >them that the document is not going forward....
> 
> My concern is that automatic reminders could increase friction for
> problematic documents.  A chair that is frustrated by an unresponsive
> document editor is not going to be helped by getting a reminder every 2
> weeks that the update is still pending.  Perhaps I'm not looking at it
> the right way, but I expect that unless we deploy an incredibly flexible
> (and complex) system, the frustration at unwanted reminders will be
> greater than the benefit of useful ones.

Ummmm, doesn't procmail (or similar) handle this problem?  I don't think
you need to replicate that power in the I-D tracker.

-- 
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG 

--ZJcv+A0YCCLh2VIg
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD4DBQFAcxL4aUz3f+Zf+XsRAu1gAJYo8zHpCubWnWbsQSDwyH6Yzla4AJ4o+wFe
D+sZIS1wZWYgDrSCrzfJyQ==
=7npx
-----END PGP SIGNATURE-----

--ZJcv+A0YCCLh2VIg--



From wgchairs-admin@ietf.org  Wed Apr  7 14:48:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26457
	for <wgchairs-archive@lists.ietf.org>; Wed, 7 Apr 2004 14:48:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BBI5r-0003wV-2j; Wed, 07 Apr 2004 14:48:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BBI40-0003BS-1M
	for wgchairs@optimus.ietf.org; Wed, 07 Apr 2004 14:46:16 -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 OAA25660
	for <wgchairs@ietf.org>; Wed, 7 Apr 2004 14:46:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBI3r-0004mq-00
	for wgchairs@ietf.org; Wed, 07 Apr 2004 14:46:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BBH8y-0004E1-00
	for wgchairs@ietf.org; Wed, 07 Apr 2004 13:47:22 -0400
Received: from ns.cnri.reston.va.us ([132.151.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBGCs-00030B-00; Wed, 07 Apr 2004 12:47:18 -0400
Received: from rbunch.cnri.reston.va.us ([132.151.2.53])
	by ns.cnri.reston.va.us with esmtp (Exim 4.20)
	id 1BBGCT-0003aO-5A; Wed, 07 Apr 2004 12:46:53 -0400
Message-Id: <6.0.0.9.2.20040407124115.02c10c28@odin>
X-Sender: rbunch@odin
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.9 (Beta)
X-Priority: 1 (Highest)
Date: Wed, 07 Apr 2004 12:46:19 -0400
To: wgchairs@ietf.org, bofchairs@ietf.org
From: Rebecca Bunch <rbunch@foretec.com>
Subject: LAST Call for Input to the 59th IETF Meeting Proceedings"
Cc: harald@alvestrand.no, "Barbara B. Fuller" <bfuller@foretec.com>,
        iesg@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_17541022==.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE,X_PRIORITY_HIGH autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

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

***This message is for all Working Groups and BoFs that met at IETF 59th 
Seoul, Korea. ***

Dear Working Group and BoF Chairs:

The deadline for submission of minutes and presentation slides for 
inclusion in the proceedings of the 59th IETF Meeting was Friday, April 2, 
2004 at 17:00 ET.   I will be accepting comments, changes and corrections 
until Friday, April 16, 2004 at 15:00 ET.

If you have not yet submitted slides or minutes, I have extended the 
deadline until Friday, April 9, 2004 at 15:00 ET.

As of Wednesday, April 7, 2004:

The following groups have not yet submitted any materials:
apparea, dnsop, iea, manet

The following haven't submitted minutes:
mmusic, marid


If I made a mistake in presentation order, minutes aren't showing up 
correctly, or anything else, please contact me directly at rbunch@forete.com.

Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.  Minutes 
submitted in plain text will be reformatted by the Secretariat.  Therefore, 
if you are concerned about preserving the formatting of your minutes, then 
please submit them in HTML.

Presentation slides may be submitted in any of the following formats:

.TXT Plain text (Unix/Mac/Dos)
.DOC MS Word Document (v95 - 2000)
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6)
.PPT MS PowerPoint (v95 - 2000)

When submitting slides for multiple presentations, please indicate the 
order that the presentations should appear in the proceedings.

The current status of the proceedings, including the list of groups in each 
category, is available at:

http://www.ietf.org/proceedings/04mar/index.html

If you have already submitted materials, then we encourage you to review 
them on line and send any corrections to proceedings@ietf.org.

Thank you in advance for your cooperation.

The IETF Secretariat


Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071 
--=====================_17541022==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
***This message is for all Working Groups and BoFs that met at IETF 59th
Seoul, Korea. ***<br><br>
Dear Working Group and BoF Chairs:<br><br>
The deadline for submission of minutes and presentation slides for
inclusion in the proceedings of the 59th IETF Meeting <b>was</b> Friday,
April 2, 2004 at 17:00 ET.&nbsp;&nbsp; I will be accepting comments,
changes and corrections until <b>Friday, April 16, 2004 at 15:00
ET.</b>&nbsp; <br><br>
If you have not yet submitted slides or minutes, I have extended the
deadline until <b>Friday, April 9, 2004 at 15:00 ET</b>.<br><br>
As of Wednesday, April 7, 2004: <br><br>
The following groups have not yet submitted any materials:<br>
apparea, dnsop, iea, manet<br><br>
The following haven't submitted minutes:<br>
mmusic, marid<br><br>
<br>
If I made a mistake in presentation order, minutes aren't showing up
correctly, or anything else, please contact me directly at
rbunch@forete.com.<br><br>
Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.&nbsp;
Minutes submitted in plain text will be reformatted by the
Secretariat.&nbsp; Therefore, if you are concerned about preserving the
formatting of your minutes, then please submit them in HTML.<br><br>
Presentation slides may be submitted in any of the following
formats:<br>
&nbsp;<br>
.TXT Plain text (Unix/Mac/Dos) <br>
.DOC MS Word Document (v95 - 2000) <br>
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6) <br>
.PPT MS PowerPoint (v95 - 2000)<br><br>
When submitting slides for multiple presentations, please indicate the
order that the presentations should appear in the proceedings.<br><br>
The current status of the proceedings, including the list of groups in
each category, is available at:<br><br>
<font color="#0000FF"><u><a href="http://www.ietf.org/proceedings/04mar/index.html" eudora="autourl">http://www.ietf.org/proceedings/04mar/index.html<br><br>
</a></u></font>If you have already submitted materials, then we encourage
you to review them on line and send any corrections to
proceedings@ietf.org.<br><br>
Thank you in advance for your cooperation.<br><br>
The IETF Secretariat <br><br>
<x-sigsep><p></x-sigsep>
Rebecca F. Bunch<br>
Foretec Seminars, Inc.<br>
1895 Preston White Dr.<br>
Suite 100<br>
Reston, VA&nbsp; 20191<br>
703-620-9053, x5365<br>
703-620-9071</body>
</html>

--=====================_17541022==.ALT--




From wgchairs-admin@ietf.org  Mon Apr 12 18:23:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19981
	for <wgchairs-archive@lists.ietf.org>; Mon, 12 Apr 2004 18:23:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BD9pV-00011t-D7; Mon, 12 Apr 2004 18:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BD9pN-00010o-2A
	for wgchairs@optimus.ietf.org; Mon, 12 Apr 2004 18:22: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 SAA19918
	for <wgchairs@ietf.org>; Mon, 12 Apr 2004 18:22:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BD9pI-0007SU-00
	for wgchairs@ietf.org; Mon, 12 Apr 2004 18:22:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BD9LU-0005Tp-00
	for wgchairs@ietf.org; Mon, 12 Apr 2004 17:52:01 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BD8pz-0003Rs-00
	for wgchairs@ietf.org; Mon, 12 Apr 2004 17:19:28 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 6727C61B9D
	for <wgchairs@ietf.org>; Mon, 12 Apr 2004 23:18:49 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
 by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 02228-08 for <wgchairs@ietf.org>;
 Mon, 12 Apr 2004 23:18:48 +0200 (CEST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 8DA2F61A93
	for <wgchairs@ietf.org>; Mon, 12 Apr 2004 23:18:47 +0200 (CEST)
Date: Mon, 12 Apr 2004 14:13:12 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: wgchairs@ietf.org
Subject: Some documents you should know about.....
Message-ID: <430275092.1081779192@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

there's a couple of documents being discussed that the WG chairs should 
know about, because they may affect how *your* WG behaves, and what you can 
do to help it get work done.....

draft-hardie-alt-consensus, being discussed on solutions@alvestrand.no, 
talks about mechanisms to "unstick" decisions where a WG agrees that a 
choice needs to be made, but is deadlocked on which choice it should be.

draft-dawkins-newtrk-wgs, being discussed on newtrk@lists.uoregon.edu (the 
NEWTRK WG list), talks about a new document designation called "Working 
Group Snapshot", that is somewhat more "important" than an I-D, but not as 
final as a PS.
draft-rousskov-newtrk-id-state proposes another mechanism for some of the 
same purposes.

Also, of course, draft-ietf-proto-* are descriptions of experiments that 
the PROTO team is starting to enable the IETF (and you!) to get work done 
more easily; feedback is always welcome!

                   Harald







From wgchairs-admin@ietf.org  Wed Apr 14 13:22:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08235
	for <wgchairs-archive@lists.ietf.org>; Wed, 14 Apr 2004 13:22:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDnxZ-00007C-0j; Wed, 14 Apr 2004 13:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDnXV-00020u-Cc
	for wgchairs@optimus.ietf.org; Wed, 14 Apr 2004 12:47: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 MAA05315
	for <wgchairs@ietf.org>; Wed, 14 Apr 2004 12:47:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDnXT-00066E-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 12:47:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDnWd-00064L-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 12:46:13 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDnVv-00062E-00; Wed, 14 Apr 2004 12:45:27 -0400
Received: from dsl092-109-027.nyc2.dsl.speakeasy.net ([66.92.109.27] helo=thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:RC4-SHA:128)  (Exim 3.35 #1 (Debian))
	id 1BDnVp-00037J-00; Wed, 14 Apr 2004 12:45:21 -0400
Received: from tytso by thunk.org with local (Exim 4.31)
	id 1BDnVo-0002yw-CC; Wed, 14 Apr 2004 12:45:20 -0400
Date: Wed, 14 Apr 2004 12:45:20 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: wgchairs@ietf.org, gcunning@foretec.com
Cc: yohba@tari.toshiba.com, postmaster@hotmail.com, postmaster@ietf.org
Subject: IETF mailing lists use lots of received lines?
Message-ID: <20040414164520.GB11004@thunk.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="l76fUT7nc3MelDdI"
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
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/>.
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-7.9 required=5.0 tests=AWL,HABEAS_SWE autolearn=no 
	version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>


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

We are in the midst of transitioning the IPSEC mailing list to
ipsec@ietf.org, and we seem to have run into an interesting problem.
The IETF mailing list system seems to use a large number of
intervening hops:

Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22])
        by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id i3EDUosM018893;
        Wed, 14 Apr 2004 09:30:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
        by optimus.ietf.org with esmtp (Exim 4.20)
        id 1BDkL7-0005ld-6v; Wed, 14 Apr 2004 09:22:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
        by optimus.ietf.org with esmtp (Exim 4.20)
        id 1BDkHl-0004qq-LQ
        for ipsec@optimus.ietf.org; Wed, 14 Apr 2004 09:18:37 -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 JAA23122
        for <ipsec@ietf.org>; Wed, 14 Apr 2004 09:18:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
        by ietf-mx with esmtp (Exim 4.12)
        id 1BDkHk-0002Ew-00
        for ipsec@ietf.org; Wed, 14 Apr 2004 09:18:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
        id 1BDkGr-00028Q-00
        for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:41 -0400

When this is combined with systems whose internal mailers use a
largish number of hops in order to transit out of their intranet,
through their firewall, and to the outside world (see below for one
example), the net result trips anti-looping schemese.  

For example, hotmail.com will bounce any mail message that contains
more than 10 Received: lines.  Given that the IETF mail system is
adding a minimum of six Received: lines, it doesn't take much more to
trip hotmail's anti-looping mechanism.  Surely Toshiba is somewhat
extreme that outgoing mail messages will go through nine (9!!!)
mailers before reaching the outside world, but the net result is that
people who are using hotmail will be losing some number of messages
sent to the ipsec@ietf.org mailing list.

Is this something that can be fixed on the ietf.org side, perhaps by
filtering out or transmuting some of the internal the IETF-added
Received: lines to "X-Received:"?  That way the information is still
there for debugging purposes, but it won't trip relatively naive
anti-looping mechanisms, such as those currently in use at hotmail.

Also, has any other wg chairs who have their mailing lists homed at
ietf.org noticed this?  If I had been automatically filter bounce
messages that come from virii, I might not have noticed this bounce
message.  Fortunately this was during a transition, so I was paying
close attention in order to assure that everything was going smoothly,
or it might have gotten filtered out and flushed.

Finally, folks at Toshiba might want to be warned that they may also
want to do similar filtering.  Given that Toshiba is adding nine
levels of Received: headers, and hotmail apparently bounces any
messages with more than 10, my guess is that some number of messages
from Toshiba may not be reaching their intended recipients.

						- Ted


Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
        by ietf-mx with esmtp (Exim 4.12)
        id 1BDkGP-00021d-00
        for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
        by inet-tsb.toshiba.co.jp  with ESMTP id i3EDH8gH029360;
        Wed, 14 Apr 2004 22:17:08 +0900 (JST)
Received: (from root@localhost)
        by tsb-wall.toshiba.co.jp  id i3EDH8Rc001649;
        Wed, 14 Apr 2004 22:17:08 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA01648 ; Wed, 14 Apr2004 22:17:08 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp
        id WAA04448; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id WAA12933; Wed, 14 Apr 2004 22:17:07
+0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
        by tsb-sgw2.toshiba.co.jp  with ESMTP id i3EDH6a3001756;
        Wed, 14 Apr 2004 22:17:06 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HW500AM7WWFL6@tsbpo1.po.toshiba.co.jp>; Wed,
 14 Apr 2004 22:17:05 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BDY7v-0003eB-00; Tue, 13 Apr 2004 17:19:39 -0700

--l76fUT7nc3MelDdI
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <ipsec-admin@ietf.org>
Received: from po14.mit.edu (po14.mit.edu [18.7.21.72])
	by po14.mit.edu (Cyrus v2.1.5) with LMTP; Wed, 14 Apr 2004 09:57:55 -0400
X-Sieve: CMU Sieve 2.2
Received: from fort-point-station.mit.edu by po14.mit.edu (8.12.4/4.7) id i3EDvrM8021698; Wed, 14 Apr 2004 09:57:54 -0400 (EDT)
Received: from optimus.ietf.org (datatracker.ietf.org [132.151.6.22])
	by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id i3EDvrsM016595
	for <tytso@mit.edu>; Wed, 14 Apr 2004 09:57:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDkfO-0002vT-2g
	for tytso@mit.edu; Wed, 14 Apr 2004 09:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDkUR-0007Vh-6Y
	for ipsec-admin@optimus.ietf.org; Wed, 14 Apr 2004 09:31:43 -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 JAA23704
	for <ipsec-admin@ietf.org>; Wed, 14 Apr 2004 09:31:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDkUP-00044E-00
	for ipsec-admin@ietf.org; Wed, 14 Apr 2004 09:31:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDkTh-0003vL-00
	for ipsec-admin@ietf.org; Wed, 14 Apr 2004 09:30:58 -0400
Received: from mc10-s16.bay6.hotmail.com ([65.54.165.90] helo=mc10-s16.hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDkSh-0003aC-00
	for ipsec-admin@ietf.org; Wed, 14 Apr 2004 09:29:55 -0400
From: postmaster@mail.hotmail.com
To: ipsec-admin@ietf.org
Date: Wed, 14 Apr 2004 06:29:25 -0700
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="9B095B5ADSN=_01C4219D0E68DF340002AEBEmc10?s16.hotmail"
Message-ID: <V1C0rNDRK00005252@mc10-s16.hotmail.com>
Subject: Delivery Status Notification (Failure)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,FORGED_HOTMAIL_RCVD,
	NO_REAL_NAME autolearn=no version=2.60
Sender: ipsec-owner@ietf.org
Errors-To: ipsec-owner@ietf.org
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
	<mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Id: IP Security <ipsec.ietf.org>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
	<mailto:ipsec-request@ietf.org?subject=subscribe>
X-Spam-Score: -4.24
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)

This is a MIME-formatted message.  
Portions of this message may be unreadable without a MIME-capable mail program.

--9B095B5ADSN=_01C4219D0E68DF340002AEBEmc10?s16.hotmail
Content-Type: text/plain; charset=unicode-1-1-utf-7

This is an automatically generated Delivery Status Notification.

Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.

       jack_xiao99@hotmail.com
       bob_arthurs@hotmail.com
       ietf_davidchen@hotmail.com
       yichang_lin@hotmail.com
       gerardo_mg@hotmail.com
       yondho@hotmail.com
       stjedi@msn.com
       ryounglove1@msn.com




--9B095B5ADSN=_01C4219D0E68DF340002AEBEmc10?s16.hotmail
Content-Type: message/delivery-status

Reporting-MTA: dns;mc10-s16.hotmail.com
Received-From-MTA: dns;mc10-f37.hotmail.com
Arrival-Date: Wed, 14 Apr 2004 06:29:25 -0700

Original-Recipient: 
Final-Recipient: rfc822;jack_xiao99@hotmail.com
Action: failed
Status: 4.4.6

Original-Recipient: 
Final-Recipient: rfc822;bob_arthurs@hotmail.com
Action: failed
Status: 4.4.6

Original-Recipient: 
Final-Recipient: rfc822;ietf_davidchen@hotmail.com
Action: failed
Status: 4.4.6

Original-Recipient: 
Final-Recipient: rfc822;yichang_lin@hotmail.com
Action: failed
Status: 4.4.6

Original-Recipient: 
Final-Recipient: rfc822;gerardo_mg@hotmail.com
Action: failed
Status: 4.4.6

Original-Recipient: 
Final-Recipient: rfc822;yondho@hotmail.com
Action: failed
Status: 4.4.6

Original-Recipient: 
Final-Recipient: rfc822;stjedi@msn.com
Action: failed
Status: 4.4.6

Original-Recipient: 
Final-Recipient: rfc822;ryounglove1@msn.com
Action: failed
Status: 4.4.6

--9B095B5ADSN=_01C4219D0E68DF340002AEBEmc10?s16.hotmail
Content-Type: message/rfc822

Received: from mc10-f37.hotmail.com ([65.54.166.173]) by mc10-s16.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824);
	 Wed, 14 Apr 2004 06:29:25 -0700
Received: from optimus.ietf.org ([132.151.6.22]) by mc10-f37.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824);
	 Wed, 14 Apr 2004 06:27:13 -0700
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDkL6-0005lX-Q5; Wed, 14 Apr 2004 09:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDkHl-0004qq-LQ
	for ipsec@optimus.ietf.org; Wed, 14 Apr 2004 09:18:37 -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 JAA23122
	for <ipsec@ietf.org>; Wed, 14 Apr 2004 09:18:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDkHk-0002Ew-00
	for ipsec@ietf.org; Wed, 14 Apr 2004 09:18:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDkGr-00028Q-00
	for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:41 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDkGP-00021d-00
	for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i3EDH8gH029360;
	Wed, 14 Apr 2004 22:17:08 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i3EDH8Rc001649;
	Wed, 14 Apr 2004 22:17:08 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA01648 ; Wed, 14 Apr 2004 22:17:08 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA04448; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id WAA12933; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw2.toshiba.co.jp  with ESMTP id i3EDH6a3001756;
	Wed, 14 Apr 2004 22:17:06 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HW500AM7WWFL6@tsbpo1.po.toshiba.co.jp>; Wed,
 14 Apr 2004 22:17:05 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BDY7v-0003eB-00; Tue, 13 Apr 2004 17:19:39 -0700
Date: Tue, 13 Apr 2004 17:19:39 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Ipsec] ipsec on WLAN
In-reply-to: <001101c421fc$cde9bfe0$2101a8c0@cappone>
To: Giacomo Pisano <giacpis@aliceposta.it>
Cc: yo2lux <lux@wplink.net>, ipsec@ietf.org
Message-id: <20040414001939.GN11313@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <012c01c421ee$9b83dda0$2101a8c0@cappone>
 <002101c421f8$58105d50$040aa8c0@yo2lux>
 <001101c421fc$cde9bfe0$2101a8c0@cappone>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,DATE_IN_PAST_12_24 
	autolearn=no version=2.60
Sender: ipsec-admin@ietf.org
Errors-To: ipsec-admin@ietf.org
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
	<mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Id: IP Security <ipsec.ietf.org>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
	<mailto:ipsec-request@ietf.org?subject=subscribe>
Return-Path: ipsec-admin@ietf.org
X-OriginalArrivalTime: 14 Apr 2004 13:27:16.0681 (UTC) FILETIME=[346AFB90:01C42224]

An IPsec usage in WLAN is being discussed in the PANA WG.  
There are several drafts related to the usage:

draft-ietf-pana-ipsec-02.txt
draft-ohba-pana-framework-00.txt

Regards,

Yoshihiro Ohba


On Wed, Apr 14, 2004 at 10:45:13AM +0200, Giacomo Pisano wrote:
> I have one client (possibly Windows) one AP and a server (possibly Windows).......do you think it's possible to make the server act as a getway for the LAN?? I need to build an IPSec Tunnel between the wi-fi client and the server. The server then has to relay the data on the LAN and viceversa.
> 
> What I'm trying to secure is just the radio link
> 
> ----- Original Message ----- 
>   From: yo2lux 
>   To: Giacomo Pisano ; ipsec@ietf.org 
>   Sent: Wednesday, April 14, 2004 10:13 AM
>   Subject: Re: [Ipsec] ipsec on WLAN
> 
> 
>   you want to make an IPSec between OpenBSD and Windows ? 
>     ----- Original Message ----- 
>     From: Giacomo Pisano 
>     To: ipsec@ietf.org 
>     Sent: Wednesday, April 14, 2004 10:03 AM
>     Subject: [Ipsec] ipsec on WLAN
> 
> 
>     Hi, I'm a novice but i'm trying to make IPSec work on WLAN in order to use level3 security instead of level2. Has anyone of you tried to do the same?? I don't have any idea of what to do!
> 
>     TNX
> 

_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec


--9B095B5ADSN=_01C4219D0E68DF340002AEBEmc10?s16.hotmail--


--l76fUT7nc3MelDdI--



From wgchairs-admin@ietf.org  Wed Apr 14 13:59:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11260
	for <wgchairs-archive@lists.ietf.org>; Wed, 14 Apr 2004 13:59:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDoPf-0000ev-Af; Wed, 14 Apr 2004 13:43:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDoHH-000655-OC
	for wgchairs@optimus.ietf.org; Wed, 14 Apr 2004 13:34:23 -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 NAA09335
	for <wgchairs@ietf.org>; Wed, 14 Apr 2004 13:34:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDoHF-0002fu-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 13:34:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDoGO-0002aB-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 13:33:29 -0400
Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDoFN-0002On-00; Wed, 14 Apr 2004 13:32:25 -0400
Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102])
	by mail-white.research.att.com (Postfix) with ESMTP id 9F08066409C;
	Wed, 14 Apr 2004 13:31:51 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by mail-blue.research.att.com (Postfix) with ESMTP id 91A09F3A87;
	Wed, 14 Apr 2004 13:31:51 -0400 (EDT)
Received: (from fenner@localhost)
	by windsor.research.att.com (8.11.6+Sun/8.8.5) id i3EHVoV20308;
	Wed, 14 Apr 2004 10:31:50 -0700 (PDT)
Message-Id: <200404141731.i3EHVoV20308@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: tytso@mit.edu
Subject: Re: IETF mailing lists use lots of received lines?
Cc: wgchairs@ietf.org, gcunning@foretec.com, yohba@tari.toshiba.com,
        postmaster@hotmail.com, postmaster@ietf.org
Date: Wed, 14 Apr 2004 10:31:49 -0700
From: Bill Fenner <fenner@research.att.com>
Versions: dmail (solaris) 2.6d/makemail 2.10
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>


Wouldn't it be more effective to ask hotmail to follow the SHOULD advice
in RFC 2821 and set their loop threshold to 100?

I've found the individual ietf.org Received: headers invaluable recently
in determining where inside ietf.org some delays were occurring; if they
were not available after the message was forwarded outside ietf.org this
task would have been much more difficult.

  Bill



From wgchairs-admin@ietf.org  Wed Apr 14 14:18:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12491
	for <wgchairs-archive@lists.ietf.org>; Wed, 14 Apr 2004 14:18:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDoky-0006ji-BI; Wed, 14 Apr 2004 14:05:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDoaR-0002oh-E7
	for wgchairs@optimus.ietf.org; Wed, 14 Apr 2004 13:54:11 -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 NAA11083
	for <wgchairs@ietf.org>; Wed, 14 Apr 2004 13:54:08 -0400 (EDT)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDoaO-0003zP-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 13:54:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDoZW-0003wc-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 13:53:15 -0400
Received: from maho3msx2.isus.emc.com ([128.221.11.32] helo=MAHO3MSX2.corp.emc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDoYj-0003q5-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 13:52:25 -0400
Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <H9P66MDQ>; Wed, 14 Apr 2004 13:51:55 -0400
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A5884@corpmx14.us.dg.com>
To: tytso@mit.edu, wgchairs@ietf.org, gcunning@foretec.com
Subject: RE: IETF mailing lists use lots of received lines?
Date: Wed, 14 Apr 2004 13:51:48 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

Ted,

I've seen this on the rddp mailing list, but only with
a corporate site that apparently added this limit check at
some point after the list was up and functioning.

Pointed email to both the postmaster and affected recipients
at the site about what was going on and why seemed to cause
it to get fixed.  I'm not sure this "tail" would be enough to
wag the hotmail "dog" though ...

--David

> -----Original Message-----
> From: Theodore Ts'o [mailto:tytso@mit.edu] 
> Sent: Wednesday, April 14, 2004 12:45 PM
> To: wgchairs@ietf.org; gcunning@foretec.com
> Cc: yohba@tari.toshiba.com; postmaster@hotmail.com; 
> postmaster@ietf.org
> Subject: IETF mailing lists use lots of received lines?
> 
> 
> We are in the midst of transitioning the IPSEC mailing list to
> ipsec@ietf.org, and we seem to have run into an interesting problem.
> The IETF mailing list system seems to use a large number of
> intervening hops:
> 
> Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22])
>         by fort-point-station.mit.edu (8.12.4/8.9.2) with 
> ESMTP id i3EDUosM018893;
>         Wed, 14 Apr 2004 09:30:51 -0400 (EDT)
> Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
>         by optimus.ietf.org with esmtp (Exim 4.20)
>         id 1BDkL7-0005ld-6v; Wed, 14 Apr 2004 09:22:05 -0400
> Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
>         by optimus.ietf.org with esmtp (Exim 4.20)
>         id 1BDkHl-0004qq-LQ
>         for ipsec@optimus.ietf.org; Wed, 14 Apr 2004 09:18:37 -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 JAA23122
>         for <ipsec@ietf.org>; Wed, 14 Apr 2004 09:18:34 -0400 (EDT)
> Received: from ietf-mx ([132.151.6.1])
>         by ietf-mx with esmtp (Exim 4.12)
>         id 1BDkHk-0002Ew-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:18:36 -0400
> Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
>         id 1BDkGr-00028Q-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:41 -0400
> 
> When this is combined with systems whose internal mailers use a
> largish number of hops in order to transit out of their intranet,
> through their firewall, and to the outside world (see below for one
> example), the net result trips anti-looping schemese.  
> 
> For example, hotmail.com will bounce any mail message that contains
> more than 10 Received: lines.  Given that the IETF mail system is
> adding a minimum of six Received: lines, it doesn't take much more to
> trip hotmail's anti-looping mechanism.  Surely Toshiba is somewhat
> extreme that outgoing mail messages will go through nine (9!!!)
> mailers before reaching the outside world, but the net result is that
> people who are using hotmail will be losing some number of messages
> sent to the ipsec@ietf.org mailing list.
> 
> Is this something that can be fixed on the ietf.org side, perhaps by
> filtering out or transmuting some of the internal the IETF-added
> Received: lines to "X-Received:"?  That way the information is still
> there for debugging purposes, but it won't trip relatively naive
> anti-looping mechanisms, such as those currently in use at hotmail.
> 
> Also, has any other wg chairs who have their mailing lists homed at
> ietf.org noticed this?  If I had been automatically filter bounce
> messages that come from virii, I might not have noticed this bounce
> message.  Fortunately this was during a transition, so I was paying
> close attention in order to assure that everything was going smoothly,
> or it might have gotten filtered out and flushed.
> 
> Finally, folks at Toshiba might want to be warned that they may also
> want to do similar filtering.  Given that Toshiba is adding nine
> levels of Received: headers, and hotmail apparently bounces any
> messages with more than 10, my guess is that some number of messages
> from Toshiba may not be reaching their intended recipients.
> 
> 						- Ted
> 
> 
> Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
>         by ietf-mx with esmtp (Exim 4.12)
>         id 1BDkGP-00021d-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:13 -0400
> Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
>         by inet-tsb.toshiba.co.jp  with ESMTP id i3EDH8gH029360;
>         Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: (from root@localhost)
>         by tsb-wall.toshiba.co.jp  id i3EDH8Rc001649;
>         Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: from tis2 [133.199.160.66] by 
> tsb-wall.toshiba.co.jp with SMTP id YAA01648 ; Wed, 14 
> Apr2004 22:17:08 +0900
> Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp
>         id WAA04448; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
> Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id 
> WAA12933; Wed, 14 Apr 2004 22:17:07
> +0900 (JST)
> Received: from tsbpo1.po.toshiba.co.jp
>         by tsb-sgw2.toshiba.co.jp  with ESMTP id i3EDH6a3001756;
>         Wed, 14 Apr 2004 22:17:06 +0900 (JST)
> Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
>  (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
>  with ESMTP id <0HW500AM7WWFL6@tsbpo1.po.toshiba.co.jp>; Wed,
>  14 Apr 2004 22:17:05 +0900 (JST)
> Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
>  id 1BDY7v-0003eB-00; Tue, 13 Apr 2004 17:19:39 -0700
> 



From wgchairs-admin@ietf.org  Wed Apr 14 14:27:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12993
	for <wgchairs-archive@lists.ietf.org>; Wed, 14 Apr 2004 14:27:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDoub-0000iq-0V; Wed, 14 Apr 2004 14:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDjof-0006tu-7d
	for wgchairs@optimus.ietf.org; Wed, 14 Apr 2004 08:48:33 -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 IAA21621
	for <wgchairs@ietf.org>; Wed, 14 Apr 2004 08:48:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDjod-0005qH-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 08:48:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDjnf-0005e8-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 08:47:31 -0400
Received: from aaryn.lunarpages.com ([216.193.194.222])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDjmg-0005RT-00; Wed, 14 Apr 2004 08:46:30 -0400
Received: from h87.s239.netsol.com ([216.168.239.87] helo=dul1shollenbl1)
	by aaryn.lunarpages.com with asmtp (TLSv1:RC4-MD5:128)
	(Exim 4.24)
	id 1BDjmq-00088C-Hq; Wed, 14 Apr 2004 05:46:40 -0700
From: "Scott Hollenbeck" <sah@428cobrajet.net>
To: <iesg@ietf.org>, <iab@ietf.org>, <wgchairs@ietf.org>
Subject: XML Directorate Reconstruction
Date: Wed, 14 Apr 2004 08:46:26 -0400
Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF02E0F344@vsvapostal8.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - aaryn.lunarpages.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - 428cobrajet.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Ted Hardie and I are in the process of reconstructing the IETF Applications
Area XML Directorate.  The Directorate will be used for two primary
purposes:

1. To assist the Applications Area Directors (Ted and me) in matters
pertaining to the use of XML in IETF protocol specifications, and

2. To assist the IETF community, especially working group chairs and
document authors, in reviewing documents that use XML to specify protocols
or protocol elements.

The directorate can be reached by sending a note to the xml-dir@ietf.org
mailing list.  Anyone can send a message to this list, but membership is
closed.  An open list for discussion of XML use in IETF protocols,
ietf-xml-use@imc.org [1], is also available.

Members of the Directorate:

Tim Bray
Ned Freed
Graham Klyne
Andy Newton
Marshall Rose
Phil Shafer

-Scott-

[1]
http://www.imc.org/ietf-xml-use/index.html




From wgchairs-admin@ietf.org  Wed Apr 14 14:28:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13064
	for <wgchairs-archive@lists.ietf.org>; Wed, 14 Apr 2004 14:28:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDoub-0000jB-9h; Wed, 14 Apr 2004 14:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDnm5-0006HJ-5E
	for wgchairs@optimus.ietf.org; Wed, 14 Apr 2004 13:02: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 NAA06533
	for <wgchairs@ietf.org>; Wed, 14 Apr 2004 13:02:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDnm3-0007dC-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 13:02:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDnl8-0007XR-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 13:01:11 -0400
Received: from [132.151.15.110] (helo=foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDnkK-0007Pl-00; Wed, 14 Apr 2004 13:00:20 -0400
Received: from [10.27.5.114] (helo=[10.27.5.114])
	by foretec.com with esmtp (Exim 4.30)
	id 1BDnii-00008S-FL; Wed, 14 Apr 2004 12:58:40 -0400
Subject: Re: IETF mailing lists use lots of received lines?
From: Brett Thorson <bthorson@foretec.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: wgchairs@ietf.org, gcunning@foretec.com, yohba@tari.toshiba.com,
        postmaster@hotmail.com, postmaster@ietf.org
In-Reply-To: <20040414164520.GB11004@thunk.org>
References: <20040414164520.GB11004@thunk.org>
Content-Type: text/plain
Message-Id: <1081962020.5533.5.camel@thor.cnri.reston.va.us>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 14 Apr 2004 13:00:20 -0400
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

The server migration that I am in the middle of performing (some steps
being spam, majordomo migration, etc) should address these issues.

--Brett

On Wed, 2004-04-14 at 12:45, Theodore Ts'o wrote:
> We are in the midst of transitioning the IPSEC mailing list to
> ipsec@ietf.org, and we seem to have run into an interesting problem.
> The IETF mailing list system seems to use a large number of
> intervening hops:
> 
> Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22])
>         by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id i3EDUosM018893;
>         Wed, 14 Apr 2004 09:30:51 -0400 (EDT)
> Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
>         by optimus.ietf.org with esmtp (Exim 4.20)
>         id 1BDkL7-0005ld-6v; Wed, 14 Apr 2004 09:22:05 -0400
> Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
>         by optimus.ietf.org with esmtp (Exim 4.20)
>         id 1BDkHl-0004qq-LQ
>         for ipsec@optimus.ietf.org; Wed, 14 Apr 2004 09:18:37 -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 JAA23122
>         for <ipsec@ietf.org>; Wed, 14 Apr 2004 09:18:34 -0400 (EDT)
> Received: from ietf-mx ([132.151.6.1])
>         by ietf-mx with esmtp (Exim 4.12)
>         id 1BDkHk-0002Ew-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:18:36 -0400
> Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
>         id 1BDkGr-00028Q-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:41 -0400
> 
> When this is combined with systems whose internal mailers use a
> largish number of hops in order to transit out of their intranet,
> through their firewall, and to the outside world (see below for one
> example), the net result trips anti-looping schemese.  
> 
> For example, hotmail.com will bounce any mail message that contains
> more than 10 Received: lines.  Given that the IETF mail system is
> adding a minimum of six Received: lines, it doesn't take much more to
> trip hotmail's anti-looping mechanism.  Surely Toshiba is somewhat
> extreme that outgoing mail messages will go through nine (9!!!)
> mailers before reaching the outside world, but the net result is that
> people who are using hotmail will be losing some number of messages
> sent to the ipsec@ietf.org mailing list.
> 
> Is this something that can be fixed on the ietf.org side, perhaps by
> filtering out or transmuting some of the internal the IETF-added
> Received: lines to "X-Received:"?  That way the information is still
> there for debugging purposes, but it won't trip relatively naive
> anti-looping mechanisms, such as those currently in use at hotmail.
> 
> Also, has any other wg chairs who have their mailing lists homed at
> ietf.org noticed this?  If I had been automatically filter bounce
> messages that come from virii, I might not have noticed this bounce
> message.  Fortunately this was during a transition, so I was paying
> close attention in order to assure that everything was going smoothly,
> or it might have gotten filtered out and flushed.
> 
> Finally, folks at Toshiba might want to be warned that they may also
> want to do similar filtering.  Given that Toshiba is adding nine
> levels of Received: headers, and hotmail apparently bounces any
> messages with more than 10, my guess is that some number of messages
> from Toshiba may not be reaching their intended recipients.
> 
> 						- Ted
> 
> 
> Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
>         by ietf-mx with esmtp (Exim 4.12)
>         id 1BDkGP-00021d-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:13 -0400
> Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
>         by inet-tsb.toshiba.co.jp  with ESMTP id i3EDH8gH029360;
>         Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: (from root@localhost)
>         by tsb-wall.toshiba.co.jp  id i3EDH8Rc001649;
>         Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA01648 ; Wed, 14 Apr2004 22:17:08 +0900
> Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp
>         id WAA04448; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
> Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id WAA12933; Wed, 14 Apr 2004 22:17:07
> +0900 (JST)
> Received: from tsbpo1.po.toshiba.co.jp
>         by tsb-sgw2.toshiba.co.jp  with ESMTP id i3EDH6a3001756;
>         Wed, 14 Apr 2004 22:17:06 +0900 (JST)
> Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
>  (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
>  with ESMTP id <0HW500AM7WWFL6@tsbpo1.po.toshiba.co.jp>; Wed,
>  14 Apr 2004 22:17:05 +0900 (JST)
> Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
>  id 1BDY7v-0003eB-00; Tue, 13 Apr 2004 17:19:39 -0700
> 
> ______________________________________________________________________
> 
> From: postmaster@mail.hotmail.com
> To: ipsec-admin@ietf.org
> Subject: Delivery Status Notification (Failure)
> Date: 14 Apr 2004 06:29:25 -0700
> 
> This is an automatically generated Delivery Status Notification.
> 
> Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
> 
>        jack_xiao99@hotmail.com
>        bob_arthurs@hotmail.com
>        ietf_davidchen@hotmail.com
>        yichang_lin@hotmail.com
>        gerardo_mg@hotmail.com
>        yondho@hotmail.com
>        stjedi@msn.com
>        ryounglove1@msn.com
> 
> 
> 
> 
> ______________________________________________________________________
> 
> Reporting-MTA: dns;mc10-s16.hotmail.com
> Received-From-MTA: dns;mc10-f37.hotmail.com
> Arrival-Date: Wed, 14 Apr 2004 06:29:25 -0700
> 
> Original-Recipient: 
> Final-Recipient: rfc822;jack_xiao99@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient: 
> Final-Recipient: rfc822;bob_arthurs@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient: 
> Final-Recipient: rfc822;ietf_davidchen@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient: 
> Final-Recipient: rfc822;yichang_lin@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient: 
> Final-Recipient: rfc822;gerardo_mg@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient: 
> Final-Recipient: rfc822;yondho@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient: 
> Final-Recipient: rfc822;stjedi@msn.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient: 
> Final-Recipient: rfc822;ryounglove1@msn.com
> Action: failed
> Status: 4.4.6
> 
> ______________________________________________________________________
> 
> From: Yoshihiro Ohba <yohba@tari.toshiba.com>
> To: Giacomo Pisano <giacpis@aliceposta.it>
> Cc: yo2lux <lux@wplink.net>, ipsec@ietf.org
> Subject: Re: [Ipsec] ipsec on WLAN
> Date: 13 Apr 2004 17:19:39 -0700
> 
> Received: from mc10-f37.hotmail.com ([65.54.166.173]) by mc10-s16.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824);
> 	 Wed, 14 Apr 2004 06:29:25 -0700
> Received: from optimus.ietf.org ([132.151.6.22]) by mc10-f37.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824);
> 	 Wed, 14 Apr 2004 06:27:13 -0700
> Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
> 	by optimus.ietf.org with esmtp (Exim 4.20)
> 	id 1BDkL6-0005lX-Q5; Wed, 14 Apr 2004 09:22:04 -0400
> Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
> 	by optimus.ietf.org with esmtp (Exim 4.20)
> 	id 1BDkHl-0004qq-LQ
> 	for ipsec@optimus.ietf.org; Wed, 14 Apr 2004 09:18:37 -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 JAA23122
> 	for <ipsec@ietf.org>; Wed, 14 Apr 2004 09:18:34 -0400 (EDT)
> Received: from ietf-mx ([132.151.6.1])
> 	by ietf-mx with esmtp (Exim 4.12)
> 	id 1BDkHk-0002Ew-00
> 	for ipsec@ietf.org; Wed, 14 Apr 2004 09:18:36 -0400
> Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
> 	id 1BDkGr-00028Q-00
> 	for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:41 -0400
> Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
> 	by ietf-mx with esmtp (Exim 4.12)
> 	id 1BDkGP-00021d-00
> 	for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:13 -0400
> Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
> 	by inet-tsb.toshiba.co.jp  with ESMTP id i3EDH8gH029360;
> 	Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: (from root@localhost)
> 	by tsb-wall.toshiba.co.jp  id i3EDH8Rc001649;
> 	Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA01648 ; Wed, 14 Apr 2004 22:17:08 +0900
> Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
> 	id WAA04448; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
> Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id WAA12933; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
> Received: from tsbpo1.po.toshiba.co.jp 
> 	by tsb-sgw2.toshiba.co.jp  with ESMTP id i3EDH6a3001756;
> 	Wed, 14 Apr 2004 22:17:06 +0900 (JST)
> Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
>  (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
>  with ESMTP id <0HW500AM7WWFL6@tsbpo1.po.toshiba.co.jp>; Wed,
>  14 Apr 2004 22:17:05 +0900 (JST)
> Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
>  id 1BDY7v-0003eB-00; Tue, 13 Apr 2004 17:19:39 -0700
> Date: Tue, 13 Apr 2004 17:19:39 -0700
> From: Yoshihiro Ohba <yohba@tari.toshiba.com>
> Subject: Re: [Ipsec] ipsec on WLAN
> In-reply-to: <001101c421fc$cde9bfe0$2101a8c0@cappone>
> To: Giacomo Pisano <giacpis@aliceposta.it>
> Cc: yo2lux <lux@wplink.net>, ipsec@ietf.org
> Message-id: <20040414001939.GN11313@steelhead>
> MIME-version: 1.0
> Content-type: text/plain; charset=iso-2022-jp
> Content-disposition: inline
> User-Agent: Mutt/1.5.5.1+cvs20040105i
> References: <012c01c421ee$9b83dda0$2101a8c0@cappone>
>  <002101c421f8$58105d50$040aa8c0@yo2lux>
>  <001101c421fc$cde9bfe0$2101a8c0@cappone>
> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
> 	ietf-mx.ietf.org
> X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,DATE_IN_PAST_12_24 
> 	autolearn=no version=2.60
> Sender: ipsec-admin@ietf.org
> Errors-To: ipsec-admin@ietf.org
> X-BeenThere: ipsec@ietf.org
> X-Mailman-Version: 2.0.12
> Precedence: bulk
> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
> 	<mailto:ipsec-request@ietf.org?subject=unsubscribe>
> List-Id: IP Security <ipsec.ietf.org>
> List-Post: <mailto:ipsec@ietf.org>
> List-Help: <mailto:ipsec-request@ietf.org?subject=help>
> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
> 	<mailto:ipsec-request@ietf.org?subject=subscribe>
> Return-Path: ipsec-admin@ietf.org
> X-OriginalArrivalTime: 14 Apr 2004 13:27:16.0681 (UTC) FILETIME=[346AFB90:01C42224]
> 
> An IPsec usage in WLAN is being discussed in the PANA WG.  
> There are several drafts related to the usage:
> 
> draft-ietf-pana-ipsec-02.txt
> draft-ohba-pana-framework-00.txt
> 
> Regards,
> 
> Yoshihiro Ohba
> 
> 
> On Wed, Apr 14, 2004 at 10:45:13AM +0200, Giacomo Pisano wrote:
> > I have one client (possibly Windows) one AP and a server (possibly Windows).......do you think it's possible to make the server act as a getway for the LAN?? I need to build an IPSec Tunnel between the wi-fi client and the server. The server then has to relay the data on the LAN and viceversa.
> > 
> > What I'm trying to secure is just the radio link
> > 
> > ----- Original Message ----- 
> >   From: yo2lux 
> >   To: Giacomo Pisano ; ipsec@ietf.org 
> >   Sent: Wednesday, April 14, 2004 10:13 AM
> >   Subject: Re: [Ipsec] ipsec on WLAN
> > 
> > 
> >   you want to make an IPSec between OpenBSD and Windows ? 
> >     ----- Original Message ----- 
> >     From: Giacomo Pisano 
> >     To: ipsec@ietf.org 
> >     Sent: Wednesday, April 14, 2004 10:03 AM
> >     Subject: [Ipsec] ipsec on WLAN
> > 
> > 
> >     Hi, I'm a novice but i'm trying to make IPSec work on WLAN in order to use level3 security instead of level2. Has anyone of you tried to do the same?? I don't have any idea of what to do!
> > 
> >     TNX
> > 
> 
> _______________________________________________
> Ipsec mailing list
> Ipsec@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipsec
> 




From wgchairs-admin@ietf.org  Wed Apr 14 14:46:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14186
	for <wgchairs-archive@lists.ietf.org>; Wed, 14 Apr 2004 14:46:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDpC2-0005ta-Fg; Wed, 14 Apr 2004 14:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDp0d-0002ve-Ag
	for wgchairs@optimus.ietf.org; Wed, 14 Apr 2004 14:21:15 -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 OAA12717
	for <wgchairs@ietf.org>; Wed, 14 Apr 2004 14:21:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDp0a-0005oq-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 14:21:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDozl-0005m0-00
	for wgchairs@ietf.org; Wed, 14 Apr 2004 14:20:22 -0400
Received: from hermes.ctd.anl.gov ([130.202.113.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDozQ-0005ih-00; Wed, 14 Apr 2004 14:20:00 -0400
Received: from hermes.ctd.anl.gov (localhost [127.0.0.1])
	by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id NAA12497;
	Wed, 14 Apr 2004 13:19:29 -0500 (CDT)
Received: from anl.gov (atalanta.ctd.anl.gov [146.137.194.4])
	by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id NAA12488;
	Wed, 14 Apr 2004 13:19:28 -0500 (CDT)
Message-ID: <407D80B3.4B834F8F@anl.gov>
Date: Wed, 14 Apr 2004 13:19:31 -0500
From: "Douglas E. Engert" <deengert@anl.gov>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Theodore Ts'o" <tytso@mit.edu>
CC: wgchairs@ietf.org, gcunning@foretec.com, yohba@tari.toshiba.com,
        postmaster@hotmail.com, postmaster@ietf.org
Subject: Re: IETF mailing lists use lots of received lines?
References: <20040414164520.GB11004@thunk.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



This is not an IETF specific problem. With the introduction of SPAM 
and virus scanners at senders, mail lists and receiving sites, 25 is 
much more realistic.  

We have seen a similar problem on the ietf-krb list, when mail 
coming from internal Microsoft addresses to the mailing list was sent
to some sites using Exchange.  The older Exchange systems had a hop 
count of 15. We had seen a recommendation for Microsoft to raise the 
hop count to 25, and most sites appear to have done this. 

Theodore Ts'o wrote:
> 
> We are in the midst of transitioning the IPSEC mailing list to
> ipsec@ietf.org, and we seem to have run into an interesting problem.
> The IETF mailing list system seems to use a large number of
> intervening hops:
> 
> Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22])
>         by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id i3EDUosM018893;
>         Wed, 14 Apr 2004 09:30:51 -0400 (EDT)
> Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
>         by optimus.ietf.org with esmtp (Exim 4.20)
>         id 1BDkL7-0005ld-6v; Wed, 14 Apr 2004 09:22:05 -0400
> Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
>         by optimus.ietf.org with esmtp (Exim 4.20)
>         id 1BDkHl-0004qq-LQ
>         for ipsec@optimus.ietf.org; Wed, 14 Apr 2004 09:18:37 -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 JAA23122
>         for <ipsec@ietf.org>; Wed, 14 Apr 2004 09:18:34 -0400 (EDT)
> Received: from ietf-mx ([132.151.6.1])
>         by ietf-mx with esmtp (Exim 4.12)
>         id 1BDkHk-0002Ew-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:18:36 -0400
> Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
>         id 1BDkGr-00028Q-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:41 -0400
> 
> When this is combined with systems whose internal mailers use a
> largish number of hops in order to transit out of their intranet,
> through their firewall, and to the outside world (see below for one
> example), the net result trips anti-looping schemese.
> 
> For example, hotmail.com will bounce any mail message that contains
> more than 10 Received: lines.  Given that the IETF mail system is
> adding a minimum of six Received: lines, it doesn't take much more to
> trip hotmail's anti-looping mechanism.  Surely Toshiba is somewhat
> extreme that outgoing mail messages will go through nine (9!!!)
> mailers before reaching the outside world, but the net result is that
> people who are using hotmail will be losing some number of messages
> sent to the ipsec@ietf.org mailing list.
> 
> Is this something that can be fixed on the ietf.org side, perhaps by
> filtering out or transmuting some of the internal the IETF-added
> Received: lines to "X-Received:"?  That way the information is still
> there for debugging purposes, but it won't trip relatively naive
> anti-looping mechanisms, such as those currently in use at hotmail.
> 
> Also, has any other wg chairs who have their mailing lists homed at
> ietf.org noticed this?  If I had been automatically filter bounce
> messages that come from virii, I might not have noticed this bounce
> message.  Fortunately this was during a transition, so I was paying
> close attention in order to assure that everything was going smoothly,
> or it might have gotten filtered out and flushed.
> 
> Finally, folks at Toshiba might want to be warned that they may also
> want to do similar filtering.  Given that Toshiba is adding nine
> levels of Received: headers, and hotmail apparently bounces any
> messages with more than 10, my guess is that some number of messages
> from Toshiba may not be reaching their intended recipients.
> 
>                                                 - Ted
> 
> Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
>         by ietf-mx with esmtp (Exim 4.12)
>         id 1BDkGP-00021d-00
>         for ipsec@ietf.org; Wed, 14 Apr 2004 09:17:13 -0400
> Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
>         by inet-tsb.toshiba.co.jp  with ESMTP id i3EDH8gH029360;
>         Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: (from root@localhost)
>         by tsb-wall.toshiba.co.jp  id i3EDH8Rc001649;
>         Wed, 14 Apr 2004 22:17:08 +0900 (JST)
> Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA01648 ; Wed, 14 Apr2004 22:17:08 +0900
> Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp
>         id WAA04448; Wed, 14 Apr 2004 22:17:07 +0900 (JST)
> Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id WAA12933; Wed, 14 Apr 2004 22:17:07
> +0900 (JST)
> Received: from tsbpo1.po.toshiba.co.jp
>         by tsb-sgw2.toshiba.co.jp  with ESMTP id i3EDH6a3001756;
>         Wed, 14 Apr 2004 22:17:06 +0900 (JST)
> Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
>  (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
>  with ESMTP id <0HW500AM7WWFL6@tsbpo1.po.toshiba.co.jp>; Wed,
>  14 Apr 2004 22:17:05 +0900 (JST)
> Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
>  id 1BDY7v-0003eB-00; Tue, 13 Apr 2004 17:19:39 -0700
> 
>   ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> Subject: Delivery Status Notification (Failure)
> Date: Wed, 14 Apr 2004 06:29:25 -0700
> From: postmaster@mail.hotmail.com
> To: ipsec-admin@ietf.org
> 
> This is an automatically generated Delivery Status Notification.
> 
> Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
> 
>        jack_xiao99@hotmail.com
>        bob_arthurs@hotmail.com
>        ietf_davidchen@hotmail.com
>        yichang_lin@hotmail.com
>        gerardo_mg@hotmail.com
>        yondho@hotmail.com
>        stjedi@msn.com
>        ryounglove1@msn.com
> 
>   ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Reporting-MTA: dns;mc10-s16.hotmail.com
> Received-From-MTA: dns;mc10-f37.hotmail.com
> Arrival-Date: Wed, 14 Apr 2004 06:29:25 -0700
> 
> Original-Recipient:
> Final-Recipient: rfc822;jack_xiao99@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient:
> Final-Recipient: rfc822;bob_arthurs@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient:
> Final-Recipient: rfc822;ietf_davidchen@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient:
> Final-Recipient: rfc822;yichang_lin@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient:
> Final-Recipient: rfc822;gerardo_mg@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient:
> Final-Recipient: rfc822;yondho@hotmail.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient:
> Final-Recipient: rfc822;stjedi@msn.com
> Action: failed
> Status: 4.4.6
> 
> Original-Recipient:
> Final-Recipient: rfc822;ryounglove1@msn.com
> Action: failed
> Status: 4.4.6
> 
>   ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> Subject: Re: [Ipsec] ipsec on WLAN
> Date: Tue, 13 Apr 2004 17:19:39 -0700
> From: Yoshihiro Ohba <yohba@tari.toshiba.com>
> To: Giacomo Pisano <giacpis@aliceposta.it>
> CC: yo2lux <lux@wplink.net>, ipsec@ietf.org
> References: <012c01c421ee$9b83dda0$2101a8c0@cappone>
>      <002101c421f8$58105d50$040aa8c0@yo2lux>
>      <001101c421fc$cde9bfe0$2101a8c0@cappone>
> 
> An IPsec usage in WLAN is being discussed in the PANA WG.
> There are several drafts related to the usage:
> 
> draft-ietf-pana-ipsec-02.txt
> draft-ohba-pana-framework-00.txt
> 
> Regards,
> 
> Yoshihiro Ohba
> 
> On Wed, Apr 14, 2004 at 10:45:13AM +0200, Giacomo Pisano wrote:
> > I have one client (possibly Windows) one AP and a server (possibly Windows).......do you think it's possible to make the server act as a getway for the LAN?? I need to build an IPSec Tunnel between the wi-fi client and the server. The server then has to relay the data on the LAN and viceversa.
> >
> > What I'm trying to secure is just the radio link
> >
> > ----- Original Message -----
> >   From: yo2lux
> >   To: Giacomo Pisano ; ipsec@ietf.org
> >   Sent: Wednesday, April 14, 2004 10:13 AM
> >   Subject: Re: [Ipsec] ipsec on WLAN
> >
> >
> >   you want to make an IPSec between OpenBSD and Windows ?
> >     ----- Original Message -----
> >     From: Giacomo Pisano
> >     To: ipsec@ietf.org
> >     Sent: Wednesday, April 14, 2004 10:03 AM
> >     Subject: [Ipsec] ipsec on WLAN
> >
> >
> >     Hi, I'm a novice but i'm trying to make IPSec work on WLAN in order to use level3 security instead of level2. Has anyone of you tried to do the same?? I don't have any idea of what to do!
> >
> >     TNX
> >
> 
> _______________________________________________
> Ipsec mailing list
> Ipsec@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipsec

-- 

 Douglas E. Engert  <DEEngert@anl.gov>
 Argonne National Laboratory
 9700 South Cass Avenue
 Argonne, Illinois  60439 
 (630) 252-5444



From wgchairs-admin@ietf.org  Fri Apr 16 13:41:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23729
	for <wgchairs-archive@lists.ietf.org>; Fri, 16 Apr 2004 13:41:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BEX7G-0000CK-Fm; Fri, 16 Apr 2004 13:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BEX0l-0006G0-0u
	for wgchairs@optimus.ietf.org; Fri, 16 Apr 2004 13:20:19 -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 NAA22780
	for <wgchairs@ietf.org>; Fri, 16 Apr 2004 13:20:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BEX0i-0005cc-Qt
	for wgchairs@ietf.org; Fri, 16 Apr 2004 13:20:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BEWzm-0005Z7-00
	for wgchairs@ietf.org; Fri, 16 Apr 2004 13:19:19 -0400
Received: from ns.cnri.reston.va.us ([132.151.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BEWz5-0005WE-00; Fri, 16 Apr 2004 13:18:35 -0400
Received: from rbunch.cnri.reston.va.us ([132.151.2.53])
	by ns.cnri.reston.va.us with esmtp (Exim 4.20)
	id 1BEWz5-0003H0-92; Fri, 16 Apr 2004 13:18:35 -0400
Message-Id: <6.0.0.9.2.20040416131740.02be9ee8@odin>
X-Sender: rbunch@odin
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.9 (Beta)
X-Priority: 1 (Highest)
Date: Fri, 16 Apr 2004 13:18:33 -0400
To: wgchairs@ietf.org, bofchairs@ietf.org
From: Rebecca Bunch <rbunch@foretec.com>
Subject: "LAST Call for Input to the 59th IETF Meeting Proceedings"
Cc: harald@alvestrand.no, "Barbara B. Fuller" <bfuller@foretec.com>,
        iesg@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_2624824==.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE,X_PRIORITY_HIGH autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

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

***This message is for all Working Groups and BoFs that met at IETF 59th 
Seoul, Korea. ***

Dear Working Group and BoF Chairs:

The FINAL deadline for submission of minutes and presentation slides for 
inclusion in the proceedings of the 59th IETF Meeting is today Friday, 
April 16, 2004 at 17:00 ET.  Please send all materials to 
proceedings@ietf.org by that time.  Any materials received after that time 
will not be included.  Please note that submission of minutes is mandatory, 
while submission of presentation slides is optional.

Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.  Minutes 
submitted in plain text will be reformatted by the Secretariat.  Therefore, 
if you are concerned about preserving the formatting of your minutes, then 
please submit them in HTML.

Presentation slides may be submitted in any of the following formats:

.TXT Plain text (Unix/Mac/Dos)
.DOC MS Word Document (v95 - 2000)
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6)
.PPT MS PowerPoint (v95 - 2000)

When submitting slides for multiple presentations, please indicate the 
order that the presentations should appear in the proceedings.


http://www.ietf.org/proceedings/04mar/index.html

If you have already submitted materials, then we encourage you to review 
them on line and send any corrections to proceedings@ietf.org.

Thank you in advance for your cooperation.

The IETF Secretariat

Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071
Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071 
--=====================_2624824==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
***This message is for all Working Groups and BoFs that met at IETF 59th
Seoul, Korea. ***<br><br>
Dear Working Group and BoF Chairs:<br><br>
The FINAL deadline for submission of minutes and presentation slides for
inclusion in the proceedings of the 59th IETF Meeting is today Friday,
April 16, 2004 at 17:00 ET.&nbsp; Please send all materials to
proceedings@ietf.org by that time.&nbsp; Any materials received after
that time will not be included.&nbsp; Please note that submission of
minutes is mandatory, while submission of presentation slides is
optional.<br><br>
Minutes may be submitted in plain text (Unix/Mac/Dos) or in HTML.&nbsp;
Minutes submitted in plain text will be reformatted by the
Secretariat.&nbsp; Therefore, if you are concerned about preserving the
formatting of your minutes, then please submit them in HTML.<br><br>
Presentation slides may be submitted in any of the following
formats:<br>
&nbsp;<br>
.TXT Plain text (Unix/Mac/Dos) <br>
.DOC MS Word Document (v95 - 2000) <br>
.PDF Adobe Portable Document Format (Acrobat 3, 4, 5, 6) <br>
.PPT MS PowerPoint (v95 - 2000)<br><br>
When submitting slides for multiple presentations, please indicate the
order that the presentations should appear in the proceedings.<br><br>
<br>
<font color="#0000FF"><u><a href="http://www.ietf.org/proceedings/04mar/index.html" eudora="autourl">http://www.ietf.org/proceedings/04mar/index.html<br><br>
</a></u></font>If you have already submitted materials, then we encourage
you to review them on line and send any corrections to
proceedings@ietf.org.<br><br>
Thank you in advance for your cooperation.<br><br>
The IETF Secretariat <br>
<x-sigsep><p></x-sigsep>
Rebecca F. Bunch<br>
Foretec Seminars, Inc.<br>
1895 Preston White Dr.<br>
Suite 100<br>
Reston, VA&nbsp; 20191<br>
703-620-9053, x5365<br>
703-620-9071 </body>
<br>
<div>Rebecca F. Bunch</div>
<div>Foretec Seminars, Inc.</div>
<div>1895 Preston White Dr.</div>
<div>Suite 100</div>
<div>Reston, VA&nbsp; 20191</div>
<div>703-620-9053, x5365</div>
703-620-9071
</html>

--=====================_2624824==.ALT--




From wgchairs-admin@ietf.org  Wed Apr 28 17:14:59 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22231
	for <wgchairs-archive@lists.ietf.org>; Wed, 28 Apr 2004 17:14:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIvSP-00081C-Ey; Wed, 28 Apr 2004 16:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIur8-0003JV-LW
	for wgchairs@optimus.ietf.org; Wed, 28 Apr 2004 15:36:30 -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 PAA11528
	for <wgchairs@ietf.org>; Wed, 28 Apr 2004 15:36:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BIur5-00020C-Ru
	for wgchairs@ietf.org; Wed, 28 Apr 2004 15:36:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIuq7-0001wX-00
	for wgchairs@ietf.org; Wed, 28 Apr 2004 15:35:28 -0400
Received: from ns.cnri.reston.va.us ([132.151.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIupG-0001tr-00; Wed, 28 Apr 2004 15:34:34 -0400
Received: from rbunch.cnri.reston.va.us ([132.151.2.53])
	by ns.cnri.reston.va.us with esmtp (Exim 4.20)
	id 1BIupH-0005tf-SX; Wed, 28 Apr 2004 15:34:35 -0400
Message-Id: <6.0.0.9.2.20040428153231.02c07e60@odin>
X-Sender: rbunch@odin
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.9 (Beta)
Date: Wed, 28 Apr 2004 15:34:34 -0400
To: wgchairs@ietf.org, bofchairs@ietf.org
From: Rebecca Bunch <rbunch@foretec.com>
Subject: "59th IETF Web Based Meeting Proceedings"
Cc: harald@alvestrand.no, "Barbara B. Fuller" <bfuller@foretec.com>,
        iesg@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_7279327==.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: wgchairs-admin@ietf.org
Errors-To: wgchairs-admin@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>

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

***This message is for all Working Groups and BoFs that met at IETF 59th 
Seoul, Korea. ***

Dear Working Group and BoF Chairs:

The IETF 59 Web proceedings are now posted.

http://www.ietf.org/proceedings/04mar/index.html

Please go and check the site out to confirm that everything looks like it 
is suppose to.

I will be closing comments and corrections to this site on Thursday, May 6, 
at 16:00 EST.

The IETF Secretariat

Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071
Rebecca F. Bunch
Foretec Seminars, Inc.
1895 Preston White Dr.
Suite 100
Reston, VA  20191
703-620-9053, x5365
703-620-9071 
--=====================_7279327==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
***This message is for all Working Groups and BoFs that met at IETF 59th
Seoul, Korea. ***<br><br>
Dear Working Group and BoF Chairs:<br><br>
The IETF 59 Web proceedings are now posted.<br><br>
<font color="#0000FF"><u><a href="http://www.ietf.org/proceedings/04mar/index.html" eudora="autourl">http://www.ietf.org/proceedings/04mar/index.html<br><br>
</a></u></font>Please go and check the site out to confirm that
everything looks like it is suppose to.<br><br>
I will be closing comments and corrections to this site on Thursday, May
6, at 16:00 EST.<br><br>
The IETF Secretariat <br>
<x-sigsep><p></x-sigsep>
Rebecca F. Bunch<br>
Foretec Seminars, Inc.<br>
1895 Preston White Dr.<br>
Suite 100<br>
Reston, VA&nbsp; 20191<br>
703-620-9053, x5365<br>
703-620-9071 </body>
<br>
<div>Rebecca F. Bunch</div>
<div>Foretec Seminars, Inc.</div>
<div>1895 Preston White Dr.</div>
<div>Suite 100</div>
<div>Reston, VA&nbsp; 20191</div>
<div>703-620-9053, x5365</div>
703-620-9071
</html>

--=====================_7279327==.ALT--




