From owner-wgchairs@ietf.org  Thu Jan  2 03:06:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00778
	for <wgchairs-archive@lists.ietf.org>; Thu, 2 Jan 2003 03:06:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18U0Qa-0006Ed-00
	for wgchairs-list@ran.ietf.org; Thu, 02 Jan 2003 03:10:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18U0Q1-0006ED-00
	for wgchairs@ran.ietf.org; Thu, 02 Jan 2003 03:09:33 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00753
	for <wgchairs@ietf.org>; Thu, 2 Jan 2003 03:02:22 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 04D3B622AD; Thu,  2 Jan 2003 09:05:31 +0100 (CET)
Date: Thu, 02 Jan 2003 08:55:21 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: tony@tndh.net
Cc: wgchairs@ietf.org
Subject: Complex topics (RE: Formalizing Design Teams)
Message-ID: <3651933272.1041497721@localhost>
In-Reply-To: <00fe01c2a880$39fe42c0$83fb220a@eagleswings>
References:  <00fe01c2a880$39fe42c0$83fb220a@eagleswings>
X-Mailer: Mulberry/2.2.1 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Happy new year everyone!
I just wanted to pick up on this thread from before Christmas....

it seems that we have different sets of problems:

- they're small, isolated, and we understand how to solve them: a short 
focused IETF WG is the most likely answer
- we don't understand how to attack the problem: an IRTF WG, or "waiting 
until the research is done", may be the answer
- we aren't sure how to solve the problem, or don't know how big the 
problem is, or we're not sure how it interacts with other things: We tend 
to create some mechanism that doesn't quite fit with our defined structure.

The mechanisms include long-lived WGs (IPv6), ad-hoc or new areas (SNMP, 
SubIP, IPv6), WG "clusters" (LDAPEXT/LDAPBIS/LDUP, DNSEXT/DNSOPS, 
SIP/SIPPING/SIMPLE), non-area directorates (Wireless, DNS) and more.

We the IETF might want to think about whether we want to have formal 
constructs that fit better into this space than "areas" or "WGs".

But then again, this discussion probably belongs on problem-statement; 
wgchairs is not an open list....

                    Harald

--On 20. desember 2002 15:33 -0800 Tony Hain <tony@tndh.net> wrote:

>> > we may decide initially that a temporary area is required
>> > to establish a level of focus across a range of groups. Over
>> time that
>> > will evolve to a point where a complex WG is sufficient to
>> maintain the
>> > necessary focus on the critical architectural issues.
>>
>> Isn't that supposed to be an IRTF working group?
>
> Not necessarily. If all we are ever going to take on in the IETF are
> small incremental changes, short-term narrow-focus groups are
> appropriate. If we need to make significant changes like replacing the
> predominate protocol at a given layer, that isn't going to happen
> quickly, and no it is not research. What it means is that the breadth of
> the problem space is not well understood by the majority of the
> participants. Just figuring out what people need to have spelled out
> takes time.





From owner-wgchairs@ietf.org  Thu Jan  2 10:10:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05940
	for <wgchairs-archive@lists.ietf.org>; Thu, 2 Jan 2003 10:10:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18U74t-0001Xv-00
	for wgchairs-list@ran.ietf.org; Thu, 02 Jan 2003 10:16:11 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18U742-0001XS-00
	for wgchairs@ran.ietf.org; Thu, 02 Jan 2003 10:15:18 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05905
	for <wgchairs@ietf.org>; Thu, 2 Jan 2003 10:08:08 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Complex topics (RE: Formalizing Design Teams)
Date: Thu, 2 Jan 2003 09:11:20 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F51030D4@mail.cynetanetworks.com>
Thread-Topic: Complex topics (RE: Formalizing Design Teams)
Thread-Index: AcKyNkEAeHGsSNoLSJS1Jm2eCMpfDQAOc2Bw
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: <wgchairs@ietf.org>
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA05940

Hi, Harald,

There's at least one other "complexity" floating around - problems that we understand most of, but we need to think more about some underlying aspect (often, but not always, of infrastructure) - security, congestion control aspects of application protocols, and per-connection router state being recent examples I'm wrestling with.

We've come up with security maevens and MIB doctors, and this helps us think about some edges of the problem domain, but we haven't solved all the problems yet (PWE3 was placed in TSV just because of the potential for transport-level disaster - putting working groups in TSV probably isn't the general solution!)

Spencer

p.s. will you be moving this thread to the problem statement list?

> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no]
> Sent: Thursday, January 02, 2003 1:55 AM
> To: tony@tndh.net
> Cc: wgchairs@ietf.org
> Subject: Complex topics (RE: Formalizing Design Teams)
> 
> 
> Happy new year everyone!
> I just wanted to pick up on this thread from before Christmas....
> 
> it seems that we have different sets of problems:
> 
> - they're small, isolated, and we understand how to solve 
> them: a short 
> focused IETF WG is the most likely answer
> - we don't understand how to attack the problem: an IRTF WG, 
> or "waiting 
> until the research is done", may be the answer
> - we aren't sure how to solve the problem, or don't know how big the 
> problem is, or we're not sure how it interacts with other 
> things: We tend 
> to create some mechanism that doesn't quite fit with our 
> defined structure.
> 
> The mechanisms include long-lived WGs (IPv6), ad-hoc or new 
> areas (SNMP, 
> SubIP, IPv6), WG "clusters" (LDAPEXT/LDAPBIS/LDUP, DNSEXT/DNSOPS, 
> SIP/SIPPING/SIMPLE), non-area directorates (Wireless, DNS) and more.
> 
> We the IETF might want to think about whether we want to have formal 
> constructs that fit better into this space than "areas" or "WGs".
> 
> But then again, this discussion probably belongs on 
> problem-statement; 
> wgchairs is not an open list....
> 
>                     Harald
> 
> --On 20. desember 2002 15:33 -0800 Tony Hain <tony@tndh.net> wrote:
> 
> >> > we may decide initially that a temporary area is required
> >> > to establish a level of focus across a range of groups. Over
> >> time that
> >> > will evolve to a point where a complex WG is sufficient to
> >> maintain the
> >> > necessary focus on the critical architectural issues.
> >>
> >> Isn't that supposed to be an IRTF working group?
> >
> > Not necessarily. If all we are ever going to take on in the IETF are
> > small incremental changes, short-term narrow-focus groups are
> > appropriate. If we need to make significant changes like 
> replacing the
> > predominate protocol at a given layer, that isn't going to happen
> > quickly, and no it is not research. What it means is that 
> the breadth of
> > the problem space is not well understood by the majority of the
> > participants. Just figuring out what people need to have spelled out
> > takes time.
> 
> 
> 
> 



From owner-wgchairs@ietf.org  Sat Jan  4 09:37:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11320
	for <wgchairs-archive@lists.ietf.org>; Sat, 4 Jan 2003 09:37:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UpW4-0003qd-00
	for wgchairs-list@ran.ietf.org; Sat, 04 Jan 2003 09:43:12 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UpVu-0003pm-00
	for wgchairs@ran.ietf.org; Sat, 04 Jan 2003 09:43:02 -0500
Received: from sj-msg-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11229
	for <wgchairs@ietf.org>; Sat, 4 Jan 2003 09:35:24 -0500 (EST)
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id h04Ecgfm001725
	for <wgchairs@ietf.org>; Sat, 4 Jan 2003 06:38:42 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABU43162;
	Sat, 4 Jan 2003 06:38:35 -0800 (PST)
Message-Id: <200301041438.ABU43162@mira-sjc5-c.cisco.com>
To: wgchairs@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Bugzilla
Date: Sat, 04 Jan 2003 09:38:35 -0500
Sender: owner-wgchairs@ietf.org
Precedence: bulk

For those of you who've used bugzilla for tracking WG
issues, what do you think of it?  What did you like,
dislike, etc.?  What categories and so on did you use?
Could you send the URLs so I could take a look at them?

Thanks,

Melinda



From owner-wgchairs@ietf.org  Sat Jan  4 10:45:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12487
	for <wgchairs-archive@lists.ietf.org>; Sat, 4 Jan 2003 10:45:04 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UqZu-00052E-00
	for wgchairs-list@ran.ietf.org; Sat, 04 Jan 2003 10:51:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UqYz-000519-00
	for wgchairs@ran.ietf.org; Sat, 04 Jan 2003 10:50:18 -0500
Received: from mail-blue.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12449
	for <wgchairs@ietf.org>; Sat, 4 Jan 2003 10:42:38 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id AABE84CF18; Sat,  4 Jan 2003 10:45:51 -0500 (EST)
Received: from berkshire.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id KAA07840;
	Sat, 4 Jan 2003 10:45:51 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 8E3837B4D; Sat,  4 Jan 2003 10:45:50 -0500 (EST)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Melinda Shore <mshore@cisco.com>
Cc: wgchairs@ietf.org
Subject: Re: Bugzilla 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 04 Jan 2003 10:45:50 -0500
Message-Id: <20030104154550.8E3837B4D@berkshire.research.att.com>
Sender: owner-wgchairs@ietf.org
Precedence: bulk

In message <200301041438.ABU43162@mira-sjc5-c.cisco.com>, Melinda Shore writes:
>For those of you who've used bugzilla for tracking WG
>issues, what do you think of it?  What did you like,
>dislike, etc.?  What categories and so on did you use?
>Could you send the URLs so I could take a look at them?
>
Apart from its technical merits, note that Bugzilla has been the 
subject of repeated security alerts.  Whoever is running such a server 
will need to maintain it very actively.

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-wgchairs@ietf.org  Sat Jan  4 11:36:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13151
	for <wgchairs-archive@lists.ietf.org>; Sat, 4 Jan 2003 11:36:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UrNF-0005sA-00
	for wgchairs-list@ran.ietf.org; Sat, 04 Jan 2003 11:42:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UrMb-0005r9-00
	for wgchairs@ran.ietf.org; Sat, 04 Jan 2003 11:41:33 -0500
Received: from internaut.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13128
	for <wgchairs@ietf.org>; Sat, 4 Jan 2003 11:33:52 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.10.2/8.10.2) with ESMTP id h04FS6w02829;
	Sat, 4 Jan 2003 07:28:06 -0800
Date: Sat, 4 Jan 2003 07:28:06 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: "Steven M. Bellovin" <smb@research.att.com>
cc: Melinda Shore <mshore@cisco.com>, <wgchairs@ietf.org>
Subject: Re: Bugzilla 
In-Reply-To: <20030104154550.8E3837B4D@berkshire.research.att.com>
Message-ID: <Pine.LNX.4.44.0301040715230.2096-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-wgchairs@ietf.org
Precedence: bulk

At IETF 53, there was a WG chair meeting on this subject, and some
discussion of the merits of various programs including Bugzilla and RT.
My understanding was that RT had fewer security issues than Bugzilla.
As I recall, RT also has nicer reporting facilities.

In discussion, it appears that there was no program that precisely met the
needs of the IETF, including:

a. Ability to make sure that all Issue discussions also appeared on
the WG mailing list. Most programs require addition of a facility to
enter Issues from a Web form that can both be entered into the Issue
db as well as being sent to the WG mailing list. Trying to parse Issue
mail directly from the WG mailing list seems like a losing proposition.

b. Ability to automatically link the entry in the Issue db to the WG
thread on the topic. This requires integration between the Issue tracking program and
the mailman mailing list manager.

c. Ability to assign varying levels of privilege to WG chairs, editors,
and participants, according to the draft involved. Programs like Bugzilla
don't support that level of access control granularity.

d. Customized reports that can summarize Issue status to the appropriate
individuals (AD, WG Chair, WG list) in a way that is meaningful. For
example, one might imagine a monthly report providing status on the
incoming and resolved issues, current disposition of the Issues (fixed,
rejected, pending), etc.





From owner-wgchairs@ietf.org  Sat Jan  4 11:37:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13188
	for <wgchairs-archive@lists.ietf.org>; Sat, 4 Jan 2003 11:37:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UrNG-0005sG-00
	for wgchairs-list@ran.ietf.org; Sat, 04 Jan 2003 11:42:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UrMv-0005rB-00
	for wgchairs@ran.ietf.org; Sat, 04 Jan 2003 11:41:53 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13133
	for <wgchairs@ietf.org>; Sat, 4 Jan 2003 11:34:14 -0500 (EST)
Received: from dynamicsoft.com ([63.113.46.143])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id h04GbTYH025251;
	Sat, 4 Jan 2003 11:37:29 -0500 (EST)
Message-ID: <3E170DC6.7010005@dynamicsoft.com>
Date: Sat, 04 Jan 2003 11:37:26 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Melinda Shore <mshore@cisco.com>
CC: wgchairs@ietf.org
Subject: Re: Bugzilla
References: <200301041438.ABU43162@mira-sjc5-c.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

We've been using it to track the sip documents.

Personally, I have found it invaluable. There is no way we would have 
been able to get the documents completed without it. You can check it 
out at:

http://www.sipwg.org

-Jonathan R.

Melinda Shore wrote:
> For those of you who've used bugzilla for tracking WG
> issues, what do you think of it?  What did you like,
> dislike, etc.?  What categories and so on did you use?
> Could you send the URLs so I could take a look at them?
> 
> Thanks,
> 
> Melinda
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com




From owner-wgchairs@ietf.org  Sat Jan  4 12:17:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13654
	for <wgchairs-archive@lists.ietf.org>; Sat, 4 Jan 2003 12:17:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Us0x-0006cM-00
	for wgchairs-list@ran.ietf.org; Sat, 04 Jan 2003 12:23:15 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Us0D-0006b9-01
	for wgchairs@ran.ietf.org; Sat, 04 Jan 2003 12:22:29 -0500
Received: from www.egenconsulting.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13635;
	Sat, 4 Jan 2003 12:14:50 -0500 (EST)
From: pregen@egenconsulting.com
To: Melinda Shore <mshore@cisco.com>
Cc: owner-wgchairs@ietf.org, wgchairs@ietf.org
Subject: Re: Bugzilla
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF7713FC5B.F520CF97-ON85256CA4.005EE4D4@egenconsulting.com>
Date: Sat, 4 Jan 2003 12:18:05 -0500
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.9a |January 7, 2002) at
 01/04/2003 12:18:03 PM,
	Serialize complete at 01/04/2003 12:18:03 PM
Content-Type: text/plain; charset="us-ascii"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

CALSCH looked at it a bit but decided it was cumbersome to use.  I don't 
think it was an exhausive "look see" though.  I actually want to look at 
it again.  However, we're working on a lot less documents than many of the 
groups.  I think volume needs to be considered when looking at these 
products.  While it may be overkill for our group - it's probably worth 
the overhead for others.
___________________
Patricia Egen Consulting
www.egenconsulting.com
423-875-2652




Melinda Shore <mshore@cisco.com>
Sent by: owner-wgchairs@ietf.org
01/04/2003 09:38

 
        To:     wgchairs@ietf.org
        cc: 
        Subject:        Bugzilla


For those of you who've used bugzilla for tracking WG
issues, what do you think of it?  What did you like,
dislike, etc.?  What categories and so on did you use?
Could you send the URLs so I could take a look at them?

Thanks,

Melinda







From owner-wgchairs@ietf.org  Mon Jan  6 09:53:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04574
	for <wgchairs-archive@lists.ietf.org>; Mon, 6 Jan 2003 09:53:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VYij-0000iB-00
	for wgchairs-list@ran.ietf.org; Mon, 06 Jan 2003 09:59:17 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VYiM-0000hA-00
	for wgchairs@ran.ietf.org; Mon, 06 Jan 2003 09:58:54 -0500
Received: from tux.w3.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04515
	for <wgchairs@ietf.org>; Mon, 6 Jan 2003 09:50:46 -0500 (EST)
Received: from localhost (IDENT:root@tux.w3.org [18.29.0.27])
	by tux.w3.org (8.9.3/8.9.3) with ESMTP id JAA12536;
	Mon, 6 Jan 2003 09:53:48 -0500
From: Joseph Reagle <reagle@w3.org>
Organization: W3C
To: Bernard Aboba <aboba@internaut.com>,
        "Steven M. Bellovin" <smb@research.att.com>
Subject: Re: Bugzilla
Date: Mon, 6 Jan 2003 09:53:47 -0500
User-Agent: KMail/1.5
Cc: <wgchairs@ietf.org>, chairs@w3.org
References: <Pine.LNX.4.44.0301040715230.2096-100000@internaut.com>
In-Reply-To: <Pine.LNX.4.44.0301040715230.2096-100000@internaut.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200301060953.47031.reagle@w3.org>
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Saturday 04 January 2003 10:28, Bernard Aboba wrote:
> At IETF 53, there was a WG chair meeting on this subject, and some
> discussion of the merits of various programs including Bugzilla and RT.
> My understanding was that RT had fewer security issues than Bugzilla.
> As I recall, RT also has nicer reporting facilities.

We've been having similar discussions for a few years at the W3C as well:
  http://lists.w3.org/Archives/Public/www-qa-wg/2001Dec/0027.html
  http://lists.w3.org/Archives/Public/www-qa-wg/2001Dec/0020.html
  http://hades.mn.aptest.com/cgi-bin/voyager-issues
  http://www.w3.org/2002/12/open-issues.php3

(And I'm sure there are others.) I've yet to use any tools myself, though 
Dom's "poorman's tracking" (the last link) seems rather nifty. Does anyone 
at W3C remember the status of our tools discussions? 



From owner-wgchairs@ietf.org  Mon Jan  6 11:16:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06291
	for <wgchairs-archive@lists.ietf.org>; Mon, 6 Jan 2003 11:16:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Va0J-0006vq-00
	for wgchairs-list@ran.ietf.org; Mon, 06 Jan 2003 11:21:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VZzO-0006uQ-00
	for wgchairs@ran.ietf.org; Mon, 06 Jan 2003 11:20:34 -0500
Received: from d12lmsgate-2.de.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06233
	for <wgchairs@ietf.org>; Mon, 6 Jan 2003 11:12:25 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-2.de.ibm.com (8.12.3/8.12.3) with ESMTP id h06GFcv4026078
	for <wgchairs@ietf.org>; Mon, 6 Jan 2003 17:15:38 +0100
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id h06GFbqb120856
	for <wgchairs@ietf.org>; Mon, 6 Jan 2003 17:15:38 +0100
Received: from dhcp23-27.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03)
          id AA28576 from <brian@hursley.ibm.com>; Mon, 6 Jan 2003 17:15:37 +0100
Message-Id: <3E19AB85.AA1A7701@hursley.ibm.com>
Date: Mon, 06 Jan 2003 17:15:01 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Directorates (was: Formalizing design teams)
References: <5.1.0.14.2.20021221062507.0461fa28@mail.windriver.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Margaret Wasserman wrote:
>...
> 
> >And what was "IPng directorate", which also gets some hits?
> 
> The IPng (or IPv6) directorate was a cross-area group of people
> with expertise in IPv6.  Although there is still a mailing list
> for this group, it has not been active in several years.

To be precise, the IPNG Directorate existed in 1993/1994 and was
set up by Scott Bradner and Allison Mankin, who were appointed
as temporary IPNG Area Directors in order to form the consensus
about which of the rival proposals for IPNG to choose. See RFC 1752.

The IPv6 Directorate was set up by Thomas Narten a few years ago to help
him as the AD responsible for IPv6. As Margaret says, it hasn't been
active for a while.

The IPv6 Forum also has a technical directorate.

  Brian



From owner-wgchairs@ietf.org  Tue Jan  7 12:32:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21741
	for <wgchairs-archive@lists.ietf.org>; Tue, 7 Jan 2003 12:32:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vwzc-0000NR-00
	for wgchairs-list@ran.ietf.org; Tue, 07 Jan 2003 11:54:20 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VwDs-0005xH-00
	for wgchairs@ran.ietf.org; Tue, 07 Jan 2003 11:05:01 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18973;
	Tue, 7 Jan 2003 10:54:00 -0500 (EST)
Message-Id: <200301071554.KAA18973@ietf.org>
To: wgchairs@ietf.org, bofchairs@ietf.org
From: agenda@ietf.org
cc: iesg@ietf.org, dinaras@ietf.org
Subject: 56th IETF WG/BOF Scheduling
Date: Tue, 07 Jan 2003 10:54:00 -0500
Sender: owner-wgchairs@ietf.org
Precedence: bulk

56th IETF in San Francisco, CA 
Meeting Dates: March 16-21, 2003

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

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

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

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

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

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

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

IETF Chair 
Harald Alvestrand <Harald@Alvestrand.no>

Applications Area (app) 
Patrik Faltstrom <paf@cisco.com> 
Ned Freed <ned.freed@mrochek.com>

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

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

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

Security Area (sec) 
Jeffrey Schiller <jis@mit.edu> 
Steve Bellovin <smb@research.att.com>

Sub-IP Area (sub) 
Scott Bradner <sob@harvard.edu>
Bert Wijnen <bwijnen@lucent.com>

Transport Area (tsv) 
Scott Bradner <sob@harvard.edu>
Allison Mankin <mankin@psg.com>

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

Figures from the 55th IETF, Atlanta, GA 
aaa 127
adslmib 10
apparea 146
atommib 10
avt 141
bmwg 21
calsch 25
ccamp 158
crisp 39
dccp 93
dhc 112
dnsext 167
dnsop 153
eap 199
entmib 24
enum 78
fax+vpim 23
forces 70
geopriv 44
gsec 67
gsmp 34
idr 179
idwg 33
ieprep 128
imapext 14
impp 77
inch 37
ipcdn 22
ipfix 49
ipo 66
ipoib 21
ippm 74
ipr 118
ips 96
ipsec 222
ipseckey 118
ipsp 88
iptel 103
krb-wg 63
l2tpext 27
ldapbis 33
ldup 31
lemonade 85
magma 119
manet 167
mboned 101
midcom 149
mmusic 88
mobileip 192
mpls 207
msec 96
nemo 186
nfsv4 17
nomcom 44
nsis 276
opes 59
ospf 76
pana 246
pim 78
pkix 97
ppvpn 211
provreg 46
psamp 61
ptomaine 84
pwe3 156
rddp 59
rmonmib 35
rmt 48
rohc 34
rpsec 150
rserpool 24
rtgarea 118
saag 163
sacred 23
seamoby 84
secsh 36
send 64
simple 139
sip 161
sipping 220
smime 38
sming 35
speechsc 47
spirits 22
sub-ip 88
syslog 40
tewg 115
tls 61
trade 10
trigtran 149
tsvwg 203
udlr 33
v6ops 261
webdav 29 
xmpp 125
zerouter 223 









From owner-wgchairs@ietf.org  Mon Jan 13 05:15:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06801
	for <wgchairs-archive@lists.ietf.org>; Mon, 13 Jan 2003 05:15:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y1eP-0005FI-00
	for wgchairs-list@ran.ietf.org; Mon, 13 Jan 2003 05:17:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y1dQ-0005EF-00
	for wgchairs@ran.ietf.org; Mon, 13 Jan 2003 05:16:00 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06723
	for <wgchairs@ietf.org>; Mon, 13 Jan 2003 05:11:59 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h0DAEM013101
	for <wgchairs@ietf.org>; Mon, 13 Jan 2003 12:14:22 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5fc3dfca82ac158f21083@esvir01nok.ntc.nokia.com> for <wgchairs@ietf.org>;
 Mon, 13 Jan 2003 12:15:16 +0200
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 13 Jan 2003 12:15:16 +0200
Received: from esebe006.NOE.Nokia.com ([172.21.138.46]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 13 Jan 2003 12:15:12 +0200
Received: from esebe022.NOE.Nokia.com ([172.21.138.113]) by esebe006.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 13 Jan 2003 12:15:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Correct address to send Interim Meeting Announcements
Date: Mon, 13 Jan 2003 12:15:09 +0200
Message-ID: <A16A3EE4D4CA124FADC7987B1AC89FE440EA20@esebe022.ntc.nokia.com>
Thread-Topic: Input solicited: IETF problem pinpointing at the plenary?
Thread-Index: AcJ/4GyB/KsWx787SQSGIG+6p6a4TA7DBlkw
To: <wgchairs@ietf.org>
X-OriginalArrivalTime: 13 Jan 2003 10:15:12.0520 (UTC) FILETIME=[A8B3D080:01C2BAEC]
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA06801

Hi all,

I thought I found the right address to send the announcement of an interim meeting,
but it doesn't seem to work.  Anyone have the right address?

Thanks,
John



From owner-wgchairs@ietf.org  Mon Jan 13 05:53:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07512
	for <wgchairs-archive@lists.ietf.org>; Mon, 13 Jan 2003 05:53:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y2G8-0005tG-00
	for wgchairs-list@ran.ietf.org; Mon, 13 Jan 2003 05:56:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y2Fz-0005sd-00
	for wgchairs@ran.ietf.org; Mon, 13 Jan 2003 05:55:51 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07480
	for <wgchairs@ietf.org>; Mon, 13 Jan 2003 05:51:50 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 868F562595; Mon, 13 Jan 2003 11:55:09 +0100 (CET)
Date: Mon, 13 Jan 2003 11:55:09 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: john.loughney@nokia.com, wgchairs@ietf.org
Subject: Re: Correct address to send Interim Meeting Announcements
Message-ID: <129250000.1042455309@askvoll.hjemme.alvestrand.no>
In-Reply-To: <A16A3EE4D4CA124FADC7987B1AC89FE440EA20@esebe022.ntc.nokia.com>
References:  <A16A3EE4D4CA124FADC7987B1AC89FE440EA20@esebe022.ntc.nokia.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

if you send the request for a publication to iesg-secretary@ietf.org, it 
will generally happen (or at least be tracked, so that I can tell what 
happened to it!).
Remember to tell the iesg-secretary what headers (including the From: 
field) to put on the message.

I don't remember seeing a "right" address for this function.

                    Harald

--On mandag, januar 13, 2003 12:15:09 +0200 john.loughney@nokia.com wrote:

> Hi all,
>
> I thought I found the right address to send the announcement of an
> interim meeting, but it doesn't seem to work.  Anyone have the right
> address?
>
> Thanks,
> John
>
>





From owner-wgchairs@ietf.org  Mon Jan 13 10:54:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14744
	for <wgchairs-archive@lists.ietf.org>; Mon, 13 Jan 2003 10:54:22 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6wl-0000BC-00
	for wgchairs-list@ran.ietf.org; Mon, 13 Jan 2003 10:56:19 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y6pS-0006ao-00
	for wgchairs@ran.ietf.org; Mon, 13 Jan 2003 10:48:46 -0500
Received: from rip.psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13999
	for <wgchairs@ietf.org>; Mon, 13 Jan 2003 10:44:42 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=rip.psg.com)
	by rip.psg.com with esmtp (Exim 4.10)
	id 18Y6oh-000HYm-00; Mon, 13 Jan 2003 07:47:59 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: john.loughney@nokia.com
Cc: <wgchairs@ietf.org>
Subject: Re: Correct address to send Interim Meeting Announcements
References: <A16A3EE4D4CA124FADC7987B1AC89FE440EA20@esebe022.ntc.nokia.com>
Message-Id: <E18Y6oh-000HYm-00@rip.psg.com>
Date: Mon, 13 Jan 2003 07:47:59 -0800
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I thought I found the right address to send the announcement of an interim
> meeting, but it doesn't seem to work.

it usually takes the relevant area director to poke successfully.

randy




From owner-wgchairs@ietf.org  Mon Jan 13 12:01:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16729
	for <wgchairs-archive@lists.ietf.org>; Mon, 13 Jan 2003 12:01:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y80R-0003ci-00
	for wgchairs-list@ran.ietf.org; Mon, 13 Jan 2003 12:04:11 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y7zR-0003bB-00
	for wgchairs@ran.ietf.org; Mon, 13 Jan 2003 12:03:09 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16667
	for <wgchairs@ietf.org>; Mon, 13 Jan 2003 11:59:04 -0500 (EST)
Received: from localhost
	([127.0.0.1] helo=psg.com ident=mankin)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18Y7yc-0007DP-00; Mon, 13 Jan 2003 09:02:18 -0800
To: john.loughney@nokia.com
cc: wgchairs@ietf.org
Subject: Re: Correct address to send Interim Meeting Announcements 
In-Reply-To: Message from john.loughney@nokia.com 
   of "Mon, 13 Jan 2003 12:15:09 +0200." <A16A3EE4D4CA124FADC7987B1AC89FE440EA20@esebe022.ntc.nokia.com> 
Date: Mon, 13 Jan 2003 09:02:18 -0800
From: Allison Mankin <mankin@psg.com>
Message-Id: <E18Y7yc-0007DP-00@psg.com>
Sender: owner-wgchairs@ietf.org
Precedence: bulk

As Randy said, there usually has to be a post-email prod from the AD,
but also this is another of the cases where there isn't good
clear information where to send the email (iesg-secretary, asking
them to send out mail on ietf-announce) or what happens then.

It should get clarified.  Sorry.

Allison 



From owner-wgchairs@ietf.org  Mon Jan 20 12:15:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24475
	for <wgchairs-archive@lists.ietf.org>; Mon, 20 Jan 2003 12:15:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18afZd-0001Gp-00
	for wgchairs-list@ran.ietf.org; Mon, 20 Jan 2003 12:19:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18afZK-0001Er-00
	for wgchairs@ran.ietf.org; Mon, 20 Jan 2003 12:18:42 -0500
Received: from dinaras.cnri.reston.va.us (host-4-249.cnri.reston.va.us [10.27.4.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24371;
	Mon, 20 Jan 2003 12:11:57 -0500 (EST)
Message-Id: <5.1.0.14.2.20030120121422.02706e50@odin>
X-Sender: dinaras@odin
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 20 Jan 2003 12:15:53 -0500
To: iesg@ietf.org, wgchairs@ietf.org, bofchairs@ietf.org
From: Dinara Suleymanova <dinaras@ietf.org>
Subject: 56th IETF Meeting - Groups scheduled as of Today
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-wgchairs@ietf.org
Precedence: bulk

56th IETF Meeting - Groups scheduled as of January 20th.
+++

APPLICATION
(fax) Internet Fax WG
(ldapbis) LDAP (v3) Revision WG
(simple) SIP for Instant Messaging and Presence Leveraging Extensions WG
(trade) Internet Open Trading Protocol WG

INTERNET
(dhc) Dynamic Host Configuration WG
(ipv6) IP Version 6 Working Group WG
(magma) Multicast & Anycast Group Membership WG

OPERATION and MANAGEMENT
(mboned) MBONE Deployment WG
(rmonmib) Remote Network Monitoring WG
(v6ops) IPv6 Operations WG

ROUTING
(forces) Forwarding and Control Element Separation WG
(ospf) Open Shortest Path First IGP WG
(vrrp) Virtual Router Redundancy Protocol WG

SECURITY
(msec) Multicast Security WG
(pkix) Public-Key Infrastructure (X.509) WG
(sasl) Simple Authentication and Security Layer WG
(smime) S/MIME Mail Security WG

SUB-IP
(ccamp) Common Control and Measurement Plane WG
(tewg) Internet Traffic Engineering WG

TRANSPORT
(dccp) Datagram Congestion Control Protocol WG
(enum) Telephone Number Mapping WG
(ieprep) Internet Emergency Preparedness WG
(pwe3) Pseudo Wire Emulation Edge to Edge WG






From owner-wgchairs@ietf.org  Wed Jan 22 11:57:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00917
	for <wgchairs-archive@lists.ietf.org>; Wed, 22 Jan 2003 11:57:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bOFJ-00042o-00
	for wgchairs-list@ran.ietf.org; Wed, 22 Jan 2003 12:01:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bOF0-000413-00
	for wgchairs@ran.ietf.org; Wed, 22 Jan 2003 12:00:42 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00439;
	Wed, 22 Jan 2003 11:45:21 -0500 (EST)
Message-Id: <200301221645.LAA00439@ietf.org>
To: wgchairs@ietf.org, bofchairs@ietf.org
From: agenda@ietf.org
cc: iesg@ietf.org
Subject: 56th IETF Meeting Scheduling - Draft Agenda
Date: Wed, 22 Jan 2003 11:45:21 -0500
Sender: owner-wgchairs@ietf.org
Precedence: bulk


Please see the Draft of the 56th IETF Meeting as of today, January 22nd.
We are ready to post it tomorrow. Send us your comments if you have them.
This time we have no Tuesday Late Evening Session but we have a Friday Morning Session.
Thanks.

+++

Draft Agenda of the Fifty-sixth IETF
March 16-21, 2002
SUNDAY, March 16, 2003
1000-1700 IEPG Meeting - 
1200-1900 Registration -
1300-1330 Newcomer's Orientation -
1330-1400 IETF Standards Process Orientation -
1500-1700 Security Tutorial - 
1700-1900 Welcome Reception - 

MONDAY, March 17, 2003
0800-1930 IETF Registration -  
0800-0900 Continental Breakfast  
0900-1130 Morning Sessions 
APP	apparea 	Applications Open Area Meeting 
INT	dhc	Dynamic Host Configuration WG
SUB	ccamp	Common Control and Measurement Plane WG
		
1130-1300 Break 
1300-1500 Afternoon Sessions I
APP	trade	Internet Open Trading Protocol WG
INT	pana	Protocol for carrying Authentication for Network Access WG
OPS	mboned	MBONE Deployment WG
OPS	rmonmib	Remote Network Monitoring WG
RTG	ospf	Open Shortest Path First IGP WG
TSV	enum	Telephone Number Mapping WG

1500-1530 Break (Refreshments provided) - 
1530-1730 Afternoon Sessions II
APP	simple	SIP for Instant Messaging and Presence Leveraging Extensions WG
INT	eap	Extensible Authentication Protocol WG
TSV	rserpool	Reliable Server Pooling WG
	
1730-1930 Break
1930-2200 Evening Sessions
INT	ipv6	IP Version 6 Working Group WG
RTG	idr	Inter-Domain Routing WG
TSV	ieprep	Internet Emergency Preparedness WG

TUESDAY, March 18, 2003
0800-1700 IETF Registration - 
0800-0900 Continental Breakfast - 
0900-1130 Morning Sessions
RTG	rpsec	Routing Protocol Security Requirements WG
SEC	msec	Multicast Security WG
TSV	avt	Audio/Video Transport WG

1130-1300 Break
1300-1400 Afternoon Sessions I
APP	fax	Internet Fax WG
OPS	entmib	Entity MIB WG
SEC	smime	S/MIME Mail Security WG
	
1415-1515 Afternoon Sessions II
RTG	forces	Forwarding and Control Element Separation WG
	
1515-1545 Break (Refreshments provided) - 
1545-1645 Afternoon Sessions III

1700-1800 Afternoon Sessions IV

WEDNESDAY, March 19, 2003
0800-1700 IETF Registration - 
0800-0900 Continental Breakfast - 
0900-1130 Morning Sessions
APP	calsch	Calendaring and Scheduling WG
OPS	v6ops	IPv6 Operations WG
SUB	ppvpn	Provider Provisioned Virtual Private Networks WG

1130-1300 Break

1300-1500 Afternoon Sessions I	
INT	magma	Multicast & Anycast Group Membership WG
TSV	avt	Audio/Video Transport WG

1500-1530 Break (Refreshments provided) - 
1530-1730	Afternoon Sessions II
SUB	tewg	Internet Traffic Engineering WG
		
1730-1930 Break
1930-2200 Open Plenary - 
 
2230	Late Night Session

PGP Key Signing 

THURSDAY, March 20, 2003
0800-1700 IETF Registration - 
0800-0900 Continental Breakfast - 
0900-1130 Morning Sessions	
APP	ldapbis	LDAP (v3) Revision WG
INT	ipv6	IP Version 6 Working Group WG
SEC	ipsec	IP Security Protocol WG
TSV	dccp	Datagram Congestion Control Protocol WG
	
1130-1300 Break
1300-1500 Afternoon Sessions I
INT	eap	Extensible Authentication Protocol WG
SEC	sasl	Simple Authentication and Security Layer WG
	
1500-1530 Break (Refreshments provided) - 
1530-1730 Afternoon Sessions II
RTG	vrrp	Virtual Router Redundancy Protocol WG
TSV	nfsv4	Network File System Version 4 WG

1730-1930 Break
1930-2200 Open Plenary - 

Friday, March 21, 2003
0800-1700 IETF Registration - 
0800-0900 Continental Breakfast - 
0900-1130 Morning Sessions	
SEC	pkix	Public-Key Infrastructure (X.509) WG
TSV	pwe3	Pseudo Wire Emulation Edge to Edge WG




From owner-wgchairs@ietf.org  Mon Jan 27 13:51:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22665
	for <wgchairs-archive@lists.ietf.org>; Mon, 27 Jan 2003 13:51:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dERN-0001Qn-00
	for wgchairs-list@ran.ietf.org; Mon, 27 Jan 2003 13:57:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dAPV-00088M-00
	for wgchairs@ran.ietf.org; Mon, 27 Jan 2003 09:38:53 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16433
	for <wgchairs@ietf.org>; Mon, 27 Jan 2003 09:31:24 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h0REYpKV029825;
	Mon, 27 Jan 2003 15:34:51 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id DW961BCL; Mon, 27 Jan 2003 15:34:51 +0100
Received: from lmf.ericsson.se (sealwa04-198.sw.ericsson.se [130.100.249.198])
	by hendrix.lmf.ericsson.se (8.12.6/8.12.6/lmf-2.1-jcs) with ESMTP id h0REYlH7023517;
	Mon, 27 Jan 2003 16:34:49 +0200 (EET)
Message-ID: <3E354398.BF1D5575@lmf.ericsson.se>
Date: Mon, 27 Jan 2003 16:35:04 +0200
X-Sybari-Trust: cf2ec215 9ffcebbb c096fb41 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: wgchairs@ietf.org
CC: Dean Willis <dwillis@softarmor.com>
Subject: Authentication and email
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

what happened finally with Dean's proposal of implementing security (at
least authentication and authorization) in the IETF mailing lists?

At present, IETF's SPAM filters take the From field of any incoming
message, and if the address belongs to a subscriber, they let the
message thru. However, in the last days, many SPAM messages received by
the SIPPING and SIP mailing lists tried to use real subscriber's email
addresses in the From field.

It is true that sometimes their guess is wrong. For example, today we
received a mail from "camarillo@ericsson.com". If they had used
"gonzalo.camarillo@ericsson.com" instead, the message would have passed
all our filters.

Maybe it is time to reconsider Dean's proposal, before spammers get a
little cleverer.

Gonzalo





From owner-wgchairs@ietf.org  Tue Jan 28 02:24:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17981
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 02:24:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dQC1-0003P6-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 02:30:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dQBB-0003Ns-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 02:29:09 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17940
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 02:21:29 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2BE68622AC; Tue, 28 Jan 2003 08:24:59 +0100 (CET)
Date: Mon, 27 Jan 2003 20:26:29 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>, wgchairs@ietf.org
Cc: Dean Willis <dwillis@softarmor.com>
Subject: Re: Authentication and email
Message-ID: <611987020.1043699189@localhost>
In-Reply-To: <3E354398.BF1D5575@lmf.ericsson.se>
References:  <3E354398.BF1D5575@lmf.ericsson.se>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

checking:

were those SPAM mails, or were those VIRUS mails?
we know that this has been a problem with virii, but so far, I haven't seen 
spammers using this deliberately.

                 Harald

--On 27. januar 2003 16:35 +0200 Gonzalo Camarillo 
<Gonzalo.Camarillo@lmf.ericsson.se> wrote:

> Folks,
>
> what happened finally with Dean's proposal of implementing security (at
> least authentication and authorization) in the IETF mailing lists?
>
> At present, IETF's SPAM filters take the From field of any incoming
> message, and if the address belongs to a subscriber, they let the
> message thru. However, in the last days, many SPAM messages received by
> the SIPPING and SIP mailing lists tried to use real subscriber's email
> addresses in the From field.
>
> It is true that sometimes their guess is wrong. For example, today we
> received a mail from "camarillo@ericsson.com". If they had used
> "gonzalo.camarillo@ericsson.com" instead, the message would have passed
> all our filters.
>
> Maybe it is time to reconsider Dean's proposal, before spammers get a
> little cleverer.
>
> Gonzalo
>
>
>
>
>





From owner-wgchairs@ietf.org  Tue Jan 28 02:33:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18214
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 02:33:33 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dQLo-00046l-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 02:40:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dQLK-00045R-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 02:39:38 -0500
Received: from mailman.packetdesign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18186
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 02:31:58 -0500 (EST)
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.6/8.12.3) with ESMTP id h0S7ZOXj092707;
	Mon, 27 Jan 2003 23:35:25 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 27 Jan 2003 23:52:49 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: wgchairs@ietf.org
Subject: Re: Authentication and email
In-Reply-To: <611987020.1043699189@localhost>
Message-ID: <20030127234908.T3196-100000@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-wgchairs@ietf.org
Precedence: bulk

On Mon, 27 Jan 2003, Harald Tveit Alvestrand wrote:

> checking:
>
> were those SPAM mails, or were those VIRUS mails?
> we know that this has been a problem with virii, but so far, I haven't seen
> spammers using this deliberately.

That's been our experience on the AVT list.  We set a 25K length limit
to block the virii.

                                                        -- Steve




From owner-wgchairs@ietf.org  Tue Jan 28 09:15:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26281
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 09:15:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dWck-0006Zw-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 09:22:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dWZq-0006PS-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 09:19:02 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26167
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 09:11:18 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 44FCD622AD; Tue, 28 Jan 2003 15:14:47 +0100 (CET)
Date: Tue, 28 Jan 2003 13:52:39 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: wgchairs@ietf.org, Dean Willis <dwillis@softarmor.com>
Subject: Re: Authentication and email
Message-ID: <674756478.1043761959@localhost>
In-Reply-To: <3E3674FA.202781D7@lmf.ericsson.se>
References: <3E354398.BF1D5575@lmf.ericsson.se>
 <611987020.1043699189@localhost> <3E3674FA.202781D7@lmf.ericsson.se>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 28. januar 2003 14:18 +0200 Gonzalo Camarillo 
<Gonzalo.Camarillo@lmf.ericsson.se> wrote:

> They looked like SPAM mails to me. But in any event... does that matter?
>
> Are we going to wait until they *are* SPAM mails and they *have* email
> addresses of real subscribers before we make something?

far from it - the secretariat is testing out some antispam software even as 
we speak, and plans to make that service available to IETF-based lists.
BUT - ALL antispam software I've seen has false positives. This means that 
imposing antispam controls on mailing lists will mena that SOME postings 
that include things like LOTS OF YELLING will be delayed significantly in 
the process. (yes, the secretariat plans to do manual scanning of the 
caught spam to check for the false positives).

So it's not a free lunch.

                         Harald



From owner-wgchairs@ietf.org  Tue Jan 28 09:40:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26722
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 09:40:28 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dX0y-0008Es-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 09:47:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dX07-0008Az-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 09:46:11 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26698
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 09:38:28 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: FW: RFC bandwith, packet size and latency
Date: Tue, 28 Jan 2003 08:41:57 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F55C3727@mail.cynetanetworks.com>
Thread-Topic: RFC bandwith, packet size and latency
Thread-Index: AcLGeUcZ6IWeooGbSoWKqonNAlTZMAAYRAHA
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: "Wgchairs Mailing List (E-mail)" <wgchairs@ietf.org>
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA26722

This posting just appeared on the problem-statement mailing list. It seems to confirm that there's actually a disadvantage to renaming an I-D when it's accepted as a working group deliverable (makes it harder to track how long things take in the IETF).

Have we ever identified an ADVANTAGE?

In the working group chair training sessions, Steve Coya just says that "working group deliverable" isn't based on the name of the draft (it's a separate field in the database). He doesn't encourage or discourage the name changes.

Henning also points out the difficulty this creates for IPR searches and suggests that the RFC Editor could tie the versions together. This solves the IPR problem if you get as far as an RFC...

Any thoughts on whether renaming drafts is worth the effort?

Spencer

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Monday, January 27, 2003 8:57 PM
> To: Harald Tveit Alvestrand; problem-statement@alvestrand.no
> Subject: RFC bandwith, packet size and latency
> 
> 
> I've gathered some additional data on the RFC publication process and 
> imported the data into EDAS (a publication management system that I 
> wrote). The results are at 
> http://www.cs.columbia.edu/~hgs/internet/rfc.shtml
> 
> The results differ slightly from the earlier ones since I was able to 
> match additional RFCs by their I-D tag. However, the basic 
> gist is the 
> same and the trend has taken a large tick upwards in 2002: 
> the average 
> delay for RFCs published in 2002 was 2 years and 2 months. 
> (The maximum 
> was 5 years and 2 months!) As discussed in more detail on the 
> web page, 
> this estimate is likely low, since there seems to be an increasing 
> tendency in some working groups to let a draft go through a number of 
> draft-personal stages before becoming draft-ietf-wg. If the draft 
> changed its title during that time, I cannot match it and thus only 
> measure the time from draft-ietf.
> 
> As others have pointed out, it's amazing how painful 
> gathering this data 
> is. Since everything is in more-or-less random text format, with 
> occasional changes, parsing is prone to errors. I did a few sanity 
> checks, but this is a good project for a forensical statistician.
> 
> Also, in recent years, even the IMR is incomplete in its I-D list, so 
> that I have no data on a number of -00 records. This explains some of 
> missing data points (where the number of published RFCs is 
> much larger 
> than the number of measured RFCs).
> 
> It would be trivial for the RFC editor to gather the "first 
> draft" time 
> from the authors. (This would also be helpful for IPR issues.)
> 
> If somebody wants to play with the data, let me know and I 
> can give them 
> SQL access. (No, not Microsoft SQL...)
> 
> Henning
> 
> 



From owner-wgchairs@ietf.org  Tue Jan 28 10:05:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27270
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 10:05:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dXPA-0001g6-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 10:12:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dXOn-0001cX-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 10:11:41 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27255
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 10:03:58 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id KAA23435;
	Tue, 28 Jan 2003 10:07:23 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.1.45) with SMTP id M2003012810072304046
 ; Tue, 28 Jan 2003 10:07:23 -0500
Message-Id: <5.1.1.5.2.20030128100740.02f5cfb0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 28 Jan 2003 10:09:25 -0500
To: Stephen Casner <casner@acm.org>,
        Harald Tveit Alvestrand <harald@alvestrand.no>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: Authentication and email
Cc: wgchairs@ietf.org
In-Reply-To: <20030127234908.T3196-100000@oak.packetdesign.com>
References: <611987020.1043699189@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

Recent experience on the MANET list (around Atlanta timeframe) was virii also..
-joe

At 11:52 PM 1/27/2003 -0800, Stephen Casner wrote:
>On Mon, 27 Jan 2003, Harald Tveit Alvestrand wrote:
>
>> checking:
>>
>> were those SPAM mails, or were those VIRUS mails?
>> we know that this has been a problem with virii, but so far, I haven't seen
>> spammers using this deliberately.
>
>That's been our experience on the AVT list.  We set a 25K length limit
>to block the virii.
>
>                                                        -- Steve





From owner-wgchairs@ietf.org  Tue Jan 28 11:25:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29826
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 11:25:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dYeZ-0006Oj-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 11:32:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dYeE-0006LQ-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 11:31:42 -0500
Received: from d12lmsgate-3.de.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29767
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 11:23:57 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-3.de.ibm.com (8.12.3/8.12.3) with ESMTP id h0SGRK13033196;
	Tue, 28 Jan 2003 17:27:21 +0100
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id h0SG0Snr080184;
	Tue, 28 Jan 2003 17:00:28 +0100
Received: from dhcp23-27.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03)
          id AA27318 from <brian@hursley.ibm.com>; Tue, 28 Jan 2003 17:00:26 +0100
Message-Id: <3E36A8EF.C16029F@hursley.ibm.com>
Date: Tue, 28 Jan 2003 16:59:43 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: Spencer Dawkins <sdawkins@cynetanetworks.com>
Cc: "Wgchairs Mailing List (E-mail)" <wgchairs@ietf.org>
Subject: Re: FW: RFC bandwith, packet size and latency
References: <9255B6CD76A88943A3062F7D4E6432F55C3727@mail.cynetanetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'm a very strong proponent of the naming convention.

Speaking as a member of the IETF at large:
It's the main criterion I use to decide whether to read a draft
that's in a peripheral area of interest for me. During the weeks
before an IETF, it's a life-saver.

Speaking as a WG chair:
It's a useful management tool and a very effective filter for
off-charter or non-consensual darfts.

Henning's statistics are fascinating, by the way.

   Brian

Spencer Dawkins wrote:
> 
> This posting just appeared on the problem-statement mailing list. It seems to confirm that there's actually a disadvantage to renaming an I-D when it's accepted as a working group deliverable (makes it harder to track how long things take in the IETF).
> 
> Have we ever identified an ADVANTAGE?
> 
> In the working group chair training sessions, Steve Coya just says that "working group deliverable" isn't based on the name of the draft (it's a separate field in the database). He doesn't encourage or discourage the name changes.
> 
> Henning also points out the difficulty this creates for IPR searches and suggests that the RFC Editor could tie the versions together. This solves the IPR problem if you get as far as an RFC...
> 
> Any thoughts on whether renaming drafts is worth the effort?
> 
> Spencer
> 
> > -----Original Message-----
> > From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> > Sent: Monday, January 27, 2003 8:57 PM
> > To: Harald Tveit Alvestrand; problem-statement@alvestrand.no
> > Subject: RFC bandwith, packet size and latency
> >
> >
> > I've gathered some additional data on the RFC publication process and
> > imported the data into EDAS (a publication management system that I
> > wrote). The results are at
> > http://www.cs.columbia.edu/~hgs/internet/rfc.shtml
> >
> > The results differ slightly from the earlier ones since I was able to
> > match additional RFCs by their I-D tag. However, the basic
> > gist is the
> > same and the trend has taken a large tick upwards in 2002:
> > the average
> > delay for RFCs published in 2002 was 2 years and 2 months.
> > (The maximum
> > was 5 years and 2 months!) As discussed in more detail on the
> > web page,
> > this estimate is likely low, since there seems to be an increasing
> > tendency in some working groups to let a draft go through a number of
> > draft-personal stages before becoming draft-ietf-wg. If the draft
> > changed its title during that time, I cannot match it and thus only
> > measure the time from draft-ietf.
> >
> > As others have pointed out, it's amazing how painful
> > gathering this data
> > is. Since everything is in more-or-less random text format, with
> > occasional changes, parsing is prone to errors. I did a few sanity
> > checks, but this is a good project for a forensical statistician.
> >
> > Also, in recent years, even the IMR is incomplete in its I-D list, so
> > that I have no data on a number of -00 records. This explains some of
> > missing data points (where the number of published RFCs is
> > much larger
> > than the number of measured RFCs).
> >
> > It would be trivial for the RFC editor to gather the "first
> > draft" time
> > from the authors. (This would also be helpful for IPR issues.)
> >
> > If somebody wants to play with the data, let me know and I
> > can give them
> > SQL access. (No, not Microsoft SQL...)
> >
> > Henning



From owner-wgchairs@ietf.org  Tue Jan 28 12:28:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01647
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 12:28:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dZdW-0001Qk-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 12:35:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dZcW-0001LA-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 12:34:00 -0500
Received: from mailman.packetdesign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01582
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 12:26:12 -0500 (EST)
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.6/8.12.3) with ESMTP id h0SHTXXj002434;
	Tue, 28 Jan 2003 09:29:34 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Tue, 28 Jan 2003 09:47:03 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: wgchairs@ietf.org
Subject: Re: Authentication and email
In-Reply-To: <674756478.1043761959@localhost>
Message-ID: <20030128094510.G3306-100000@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-wgchairs@ietf.org
Precedence: bulk

On Tue, 28 Jan 2003, Harald Tveit Alvestrand wrote:

> (yes, the secretariat plans to do manual scanning of the
> caught spam to check for the false positives).

I presume that is just for the ietf list (and others for which the
secretariat is the admin) but that wg lists would go in the mailman
hold queue like current non-subscriber mail?

                                                        -- Steve




From owner-wgchairs@ietf.org  Tue Jan 28 13:56:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03616
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 13:56:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dazm-0007ro-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 14:02:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dazG-0007ot-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 14:01:34 -0500
Received: from tigger (scoya.cnri.reston.va.us [10.27.5.106])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03582;
	Tue, 28 Jan 2003 13:53:42 -0500 (EST)
Date: Tue, 28 Jan 2003 13:54:12 -0500 (Eastern Standard Time)
From: Steve Coya <scoya@ietf.org>
To: Stephen Casner <casner@acm.org>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, wgchairs@ietf.org
Subject: Re: Authentication and email
In-Reply-To: <20030128094510.G3306-100000@oak.packetdesign.com>
Message-ID: <Pine.WNT.3.96.1030128134552.1260C-100000@tigger>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-wgchairs@ietf.org
Precedence: bulk


I believe this will be for ALL email lists maintained at IETF.ORG


On Tue, 28 Jan 2003, Stephen Casner wrote:

>>On Tue, 28 Jan 2003, Harald Tveit Alvestrand wrote:
>>
>>> (yes, the secretariat plans to do manual scanning of the
>>> caught spam to check for the false positives).
>>
>>I presume that is just for the ietf list (and others for which the
>>secretariat is the admin) but that wg lists would go in the mailman
>>hold queue like current non-subscriber mail?
>>
>>                                                        -- Steve
>>
>>
>>




From owner-wgchairs@ietf.org  Tue Jan 28 14:28:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04512
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 14:28:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dbVf-00017v-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 14:35:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dbUi-00014p-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 14:34:04 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04442
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 14:26:17 -0500 (EST)
Received: from ABIERMAN-W2K.cisco.com (sjc-vpn2-316.cisco.com [10.21.113.60])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h0SJTdB7013845;
	Tue, 28 Jan 2003 11:29:39 -0800 (PST)
Message-Id: <4.3.2.7.2.20030128112143.0f736e88@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 28 Jan 2003 11:26:02 -0800
To: Stephen Casner <casner@acm.org>
From: Andy Bierman <abierman@cisco.com>
Subject: Re: Authentication and email
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, wgchairs@ietf.org
In-Reply-To: <20030128094510.G3306-100000@oak.packetdesign.com>
References: <674756478.1043761959@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

At 09:47 AM 1/28/2003 -0800, Stephen Casner wrote:
>On Tue, 28 Jan 2003, Harald Tveit Alvestrand wrote:
>
>> (yes, the secretariat plans to do manual scanning of the
>> caught spam to check for the false positives).
>
>I presume that is just for the ietf list (and others for which the
>secretariat is the admin) but that wg lists would go in the mailman
>hold queue like current non-subscriber mail?

Can we change this policy slightly?
There are some emails that are so obviously SPAM, that they should
just be dropped instead of put in the hold queue.  Mail identified
to contain executables (virii) can also be dropped.

The WEB interface to manage the hold queue requires lots of 
frequent manual intervention.  In the 2 mailing lists I run,
the ratio of junk to legitimate WG mail is about 500:1.


>                                                        -- Steve

Andy




From owner-wgchairs@ietf.org  Tue Jan 28 16:14:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07776
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 16:14:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dd9F-0007Cy-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 16:20:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dd8d-0007B7-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 16:19:23 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07721;
	Tue, 28 Jan 2003 16:11:35 -0500 (EST)
Received: from roam.psg.com ([147.28.4.2])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18dd4R-000CAm-00; Tue, 28 Jan 2003 13:15:03 -0800
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.12)
	id 18dd4P-0001k2-00; Tue, 28 Jan 2003 13:15:01 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Steve Coya <scoya@ietf.org>
Cc: Stephen Casner <casner@acm.org>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, wgchairs@ietf.org
Subject: Re: Authentication and email
References: <20030128094510.G3306-100000@oak.packetdesign.com>
	<Pine.WNT.3.96.1030128134552.1260C-100000@tigger>
Message-Id: <E18dd4P-0001k2-00@roam.psg.com>
Date: Tue, 28 Jan 2003 13:15:01 -0800
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I believe this will be for ALL email lists maintained at IETF.ORG

that will require ~ one fte




From owner-wgchairs@ietf.org  Tue Jan 28 16:20:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08081
	for <wgchairs-archive@lists.ietf.org>; Tue, 28 Jan 2003 16:20:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ddG3-0007ZZ-00
	for wgchairs-list@ran.ietf.org; Tue, 28 Jan 2003 16:27:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ddFq-0007Wj-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 16:26:50 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08013
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 16:19:02 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: FW: RFC bandwith, packet size and latency
Date: Tue, 28 Jan 2003 15:22:30 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F543BAA8@mail.cynetanetworks.com>
Thread-Topic: FW: RFC bandwith, packet size and latency
Thread-Index: AcLG6iTBuy9XqRcvRbW88MC4kSdaQwAKK+zA
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: "Wgchairs Mailing List (E-mail)" <wgchairs@ietf.org>
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA08081

OK, let me ask it the other way - is there any working group that DOESN'T rename drafts when they're taken on as working group deliverables?

This is being left up to WG chair preference - if there's a widespread expectation that you can recognize working group deliverables by name, we should probably stop telling people that you can't tell by the name (true advice, but not helpful if it leads to confusion).

Of course, if everyone is already doing this, no confusion results - it's just that I've been telling people "no need to rename", trying to be nice to the I-D keepers!

Spencer

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian@hursley.ibm.com]
> Sent: Tuesday, January 28, 2003 10:00 AM
> To: Spencer Dawkins
> Cc: Wgchairs Mailing List (E-mail)
> Subject: Re: FW: RFC bandwith, packet size and latency
> 
> 
> I'm a very strong proponent of the naming convention.
> 
> Speaking as a member of the IETF at large:
> It's the main criterion I use to decide whether to read a draft
> that's in a peripheral area of interest for me. During the weeks
> before an IETF, it's a life-saver.
> 
> Speaking as a WG chair:
> It's a useful management tool and a very effective filter for
> off-charter or non-consensual darfts.
> 
> Henning's statistics are fascinating, by the way.
> 
>    Brian
> > 



From owner-wgchairs@ietf.org  Wed Jan 29 16:47:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01092
	for <wgchairs-archive@lists.ietf.org>; Wed, 29 Jan 2003 16:47:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e08l-0001n0-00
	for wgchairs-list@ran.ietf.org; Wed, 29 Jan 2003 16:53:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dUkb-0002DS-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 07:22:01 -0500
Received: from imr1.ericy.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23174
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 07:14:19 -0500 (EST)
Received: from mr6.exu.ericsson.se (mr6u3.ericy.com [208.237.135.123])
	by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id h0SCHhd08082;
	Tue, 28 Jan 2003 06:17:44 -0600 (CST)
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by mr6.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id h0SCHhD19049;
	Tue, 28 Jan 2003 06:17:43 -0600 (CST)
Received: from lmf.ericsson.se (sealwa04-253.sw.ericsson.se [130.100.249.253]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id CV6XSNTP; Tue, 28 Jan 2003 06:17:41 -0600
Message-ID: <3E3674FA.202781D7@lmf.ericsson.se>
Date: Tue, 28 Jan 2003 14:18:02 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: wgchairs@ietf.org, Dean Willis <dwillis@softarmor.com>
Subject: Re: Authentication and email
References: <3E354398.BF1D5575@lmf.ericsson.se> <611987020.1043699189@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

They looked like SPAM mails to me. But in any event... does that matter?

Are we going to wait until they *are* SPAM mails and they *have* email
addresses of real subscribers before we make something?

Gonzalo

Harald Tveit Alvestrand wrote:
>
> checking:
>
> were those SPAM mails, or were those VIRUS mails?
> we know that this has been a problem with virii, but so far, I haven't seen
> spammers using this deliberately.
>
>                  Harald
>
> --On 27. januar 2003 16:35 +0200 Gonzalo Camarillo
> <Gonzalo.Camarillo@lmf.ericsson.se> wrote:
>
> > Folks,
> >
> > what happened finally with Dean's proposal of implementing security (at
> > least authentication and authorization) in the IETF mailing lists?
> >
> > At present, IETF's SPAM filters take the From field of any incoming
> > message, and if the address belongs to a subscriber, they let the
> > message thru. However, in the last days, many SPAM messages received by
> > the SIPPING and SIP mailing lists tried to use real subscriber's email
> > addresses in the From field.
> >
> > It is true that sometimes their guess is wrong. For example, today we
> > received a mail from "camarillo@ericsson.com". If they had used
> > "gonzalo.camarillo@ericsson.com" instead, the message would have passed
> > all our filters.
> >
> > Maybe it is time to reconsider Dean's proposal, before spammers get a
> > little cleverer.
> >
> > Gonzalo
> >
> >
> >
> >
> >





From owner-wgchairs@ietf.org  Wed Jan 29 16:47:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01110
	for <wgchairs-archive@lists.ietf.org>; Wed, 29 Jan 2003 16:47:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e08l-0001mj-00
	for wgchairs-list@ran.ietf.org; Wed, 29 Jan 2003 16:53:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dSMo-0000F0-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 04:49:18 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19904
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 04:41:38 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id BF6797946; Tue, 28 Jan 2003 01:45:05 -0800 (PST)
Date: Tue, 28 Jan 2003 04:39:39 -0500
Subject: Re: Authentication and email
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: wgchairs@ietf.org
To: Harald Alvestrand <harald@alvestrand.no>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <20030127234908.T3196-100000@oak.packetdesign.com>
Message-Id: <6C0816A4-32A4-11D7-BA74-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Mon, 27 Jan 2003, Harald Tveit Alvestrand wrote:
> checking:
>
> were those SPAM mails, or were those VIRUS mails?
> we know that this has been a problem with virii, but so far, I haven't
> seen
> spammers using this deliberately.

Harald,

There definitely have been many non-virus spam messages sent out using
forgeries of one of my email addresses as the claimed source in the
From: line of the mail headers.  I have also seen non-virus spam
forgeries
using other IETF folks' mail address as the alleged source in the
From: line.

It is pretty clear that at least one spammer is using online archives
of IETF mailing lists as a place to grab From: information for their
header forgeries.  Sigh.

Ran






From owner-wgchairs@ietf.org  Wed Jan 29 16:48:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01149
	for <wgchairs-archive@lists.ietf.org>; Wed, 29 Jan 2003 16:48:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e08l-0001n6-00
	for wgchairs-list@ran.ietf.org; Wed, 29 Jan 2003 16:53:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dXWl-0002D0-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 10:19:55 -0500
Received: from imr1.ericy.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27441
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 10:12:12 -0500 (EST)
Received: from mr6.exu.ericsson.se (mr6u3.ericy.com [208.237.135.123])
	by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id h0SFFed16255;
	Tue, 28 Jan 2003 09:15:40 -0600 (CST)
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by mr6.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id h0SFFeZ04774;
	Tue, 28 Jan 2003 09:15:40 -0600 (CST)
Received: from lmf.ericsson.se (sealwa04-253.sw.ericsson.se [130.100.249.253]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id CV6XTDDP; Tue, 28 Jan 2003 09:15:38 -0600
Message-ID: <3E369EAE.80761DAC@lmf.ericsson.se>
Date: Tue, 28 Jan 2003 17:15:58 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: wgchairs@ietf.org, Dean Willis <dwillis@softarmor.com>
Subject: Re: Authentication and email
References: <3E354398.BF1D5575@lmf.ericsson.se>
	 <611987020.1043699189@localhost> <3E3674FA.202781D7@lmf.ericsson.se> <674756478.1043761959@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Agreed. Having advanced anti-spam filters is great.

> So it's not a free lunch.

Well, I have to manually scan all the mails caught by the current filter
today anyway, so for me, the new filters come with no extra price.

But the issue Dean was bringing up was a different one. Just by chance,
Dean and I are attending a 3GPP-IETF workshop in San Francisco this
week, representing the SIPish working groups. We are telling those 3GPP
guys why all of their billion memory-limited terminals have to implement
S/MIME (they were quite opposed to that in the beginning), and how great
are self-signed certificates used in an SSH-like fashion... we also
explained them that if the SIP spec says that you MUST implement TLS and
S/MIME, they really MUST implement them.

And after giving them those speeches, we come back "home" to the IETF
and say that email security is undoable for our mailing lists for some
reason... it seems that MUSTs, SHOULDs and security considerations
sections do not apply to us ;o)

Gonzalo



Harald Tveit Alvestrand wrote:
>
> --On 28. januar 2003 14:18 +0200 Gonzalo Camarillo
> <Gonzalo.Camarillo@lmf.ericsson.se> wrote:
>
> > They looked like SPAM mails to me. But in any event... does that matter?
> >
> > Are we going to wait until they *are* SPAM mails and they *have* email
> > addresses of real subscribers before we make something?
>
> far from it - the secretariat is testing out some antispam software even as
> we speak, and plans to make that service available to IETF-based lists.
> BUT - ALL antispam software I've seen has false positives. This means that
> imposing antispam controls on mailing lists will mena that SOME postings
> that include things like LOTS OF YELLING will be delayed significantly in
> the process. (yes, the secretariat plans to do manual scanning of the
> caught spam to check for the false positives).
>
> So it's not a free lunch.
>
>                          Harald

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo





From owner-wgchairs@ietf.org  Wed Jan 29 16:49:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01212
	for <wgchairs-archive@lists.ietf.org>; Wed, 29 Jan 2003 16:49:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e08m-0001nC-00
	for wgchairs-list@ran.ietf.org; Wed, 29 Jan 2003 16:53:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18db9t-0008Qj-00
	for wgchairs@ran.ietf.org; Tue, 28 Jan 2003 14:12:33 -0500
Received: from bdsl.greycouncil.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03886
	for <wgchairs@ietf.org>; Tue, 28 Jan 2003 14:04:44 -0500 (EST)
Received: from txdwillis (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.greycouncil.com (8.12.5/8.12.5) with ESMTP id h0SJ86Lc004386;
	Tue, 28 Jan 2003 13:08:06 -0600
From: "Dean Willis" <dwillis@dynamicsoft.com>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        <wgchairs@ietf.org>
Cc: "'Dean Willis'" <dwillis@softarmor.com>
Subject: RE: Authentication and email
Date: Tue, 28 Jan 2003 13:07:33 -0600
Message-ID: <003101c2c700$8cd82c60$450a0a0a@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <611987020.1043699189@localhost>
Importance: Normal
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA01212

Harald asked:
> checking:
> 
> were those SPAM mails, or were those VIRUS mails?
> we know that this has been a problem with virii, but so far, 
> I haven't seen 
> spammers using this deliberately.
> 

I didn't look at the message. Here's the notification I got from mailman. It
LOOKS like spam, based on contect and subject.

--------------------
As list administrator, your authorization is requested for the following
mailing list posting:

    List:    Sip@ietf.org
    From:    camarillo@ericsson.com
    Subject: Eager to see you
    Reason:  Post by non-member to a members-only list

At your convenience, visit:

    https://www1.ietf.org/mailman/admindb/sip
        
to approve or deny the request.
---------------------

Incidentally, I am running a vanilla Spam Assassin configuration on my
inbox. I get about three false positives a week on legitimate SIP, SIPPING,
or sip-implementors posts, usually from real people using email relays on a
black-hole list. I'm filtering off around 300 spams a day, which is about
50% of my mail volume. 

Spammers are getting smarter, and I don't believe that heuristic detection
mechanisms are going to hold up much longer. I KNOW how to break the current
defense mechanisms we use, and that means its only a matter of time before
the spamettes figure it out too.

--
Dean






From owner-wgchairs@ietf.org  Wed Jan 29 16:53:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01316
	for <wgchairs-archive@lists.ietf.org>; Wed, 29 Jan 2003 16:53:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e08m-0001nI-00
	for wgchairs-list@ran.ietf.org; Wed, 29 Jan 2003 16:53:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18do6E-0000Ng-00
	for wgchairs@ran.ietf.org; Wed, 29 Jan 2003 04:01:38 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13668
	for <wgchairs@ietf.org>; Wed, 29 Jan 2003 03:53:41 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (esealnt612.al.sw.ericsson.se [153.88.254.71])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h0T8vCAv023913;
	Wed, 29 Jan 2003 09:57:13 +0100 (MET)
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55)
	id <DW0BQTJF>; Wed, 29 Jan 2003 09:57:12 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E32520@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Brian E Carpenter'" <brian@hursley.ibm.com>,
        Spencer Dawkins
	 <sdawkins@cynetanetworks.com>
Cc: "Wgchairs Mailing List (E-mail)" <wgchairs@ietf.org>
Subject: RE: FW: RFC bandwith, packet size and latency
Date: Wed, 29 Jan 2003 09:55:19 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

I agree with Brian that the naming convention is a very
useful tool for indicating document status. What we could
do is to provide some kind of references in drafts that
were created based on other drafts. That would just be
one minor check for us to do at the time we create a new
WG document.

/L-E


> -----Original Message-----
> From: Brian E Carpenter [mailto:brian@hursley.ibm.com]
> Sent: den 28 januari 2003 17:00
> To: Spencer Dawkins
> Cc: Wgchairs Mailing List (E-mail)
> Subject: Re: FW: RFC bandwith, packet size and latency
>
>
> I'm a very strong proponent of the naming convention.
>
> Speaking as a member of the IETF at large:
> It's the main criterion I use to decide whether to read a draft
> that's in a peripheral area of interest for me. During the weeks
> before an IETF, it's a life-saver.
>
> Speaking as a WG chair:
> It's a useful management tool and a very effective filter for
> off-charter or non-consensual darfts.
>
> Henning's statistics are fascinating, by the way.
>
>    Brian
>
> Spencer Dawkins wrote:
> >
> > This posting just appeared on the problem-statement mailing
> list. It seems to confirm that there's actually a
> disadvantage to renaming an I-D when it's accepted as a
> working group deliverable (makes it harder to track how long
> things take in the IETF).
> >
> > Have we ever identified an ADVANTAGE?
> >
> > In the working group chair training sessions, Steve Coya
> just says that "working group deliverable" isn't based on the
> name of the draft (it's a separate field in the database). He
> doesn't encourage or discourage the name changes.
> >
> > Henning also points out the difficulty this creates for IPR
> searches and suggests that the RFC Editor could tie the
> versions together. This solves the IPR problem if you get as
> far as an RFC...
> >
> > Any thoughts on whether renaming drafts is worth the effort?
> >
> > Spencer





From owner-wgchairs@ietf.org  Wed Jan 29 17:06:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01901
	for <wgchairs-archive@lists.ietf.org>; Wed, 29 Jan 2003 17:06:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e0S5-0003HW-00
	for wgchairs-list@ran.ietf.org; Wed, 29 Jan 2003 17:13:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e0Rw-0003Fb-01
	for wgchairs@ran.ietf.org; Wed, 29 Jan 2003 17:12:52 -0500
Received: from www.egenconsulting.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01861;
	Wed, 29 Jan 2003 17:04:48 -0500 (EST)
From: pregen@egenconsulting.com
To: RJ Atkinson <rja@extremenetworks.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, owner-wgchairs@ietf.org,
        wgchairs@ietf.org
Subject: Re: Authentication and email
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF3C77263E.497E56AD-ON85256CBD.0079922C@egenconsulting.com>
Date: Wed, 29 Jan 2003 17:08:19 -0500
X-MIMETrack: Serialize by Router on Notes1/Egen Consulting/01(Release 5.0.9a |January 7, 2002) at
 01/29/2003 05:08:22 PM,
	Serialize complete at 01/29/2003 05:08:22 PM
Content-Type: text/plain; charset="us-ascii"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

Same here. I have noticed an increase in spam using my ietf listing




RJ Atkinson <rja@extremenetworks.com>
Sent by: owner-wgchairs@ietf.org
01/28/2003 04:39

 
        To:     Harald Alvestrand <harald@alvestrand.no>
        cc:     wgchairs@ietf.org
        Subject:        Re: Authentication and email



On Mon, 27 Jan 2003, Harald Tveit Alvestrand wrote:
> checking:
>
> were those SPAM mails, or were those VIRUS mails?
> we know that this has been a problem with virii, but so far, I haven't
> seen
> spammers using this deliberately.

Harald,

There definitely have been many non-virus spam messages sent out using
forgeries of one of my email addresses as the claimed source in the
From: line of the mail headers.  I have also seen non-virus spam
forgeries
using other IETF folks' mail address as the alleged source in the
From: line.

It is pretty clear that at least one spammer is using online archives
of IETF mailing lists as a place to grab From: information for their
header forgeries.  Sigh.

Ran











From owner-wgchairs@ietf.org  Wed Jan 29 18:02:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02885
	for <wgchairs-archive@lists.ietf.org>; Wed, 29 Jan 2003 18:02:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e1KH-0004oU-00
	for wgchairs-list@ran.ietf.org; Wed, 29 Jan 2003 18:09:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e1Jg-0004mZ-00
	for wgchairs@ran.ietf.org; Wed, 29 Jan 2003 18:08:24 -0500
Received: from above.proper.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02825
	for <wgchairs@ietf.org>; Wed, 29 Jan 2003 18:00:21 -0500 (EST)
Received: from [165.227.249.18] (165-227-249-18.client.dsl.net [165.227.249.18])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id h0TN3mo05496
	for <wgchairs@ietf.org>; Wed, 29 Jan 2003 15:03:48 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p05210218ba5e0b8736e8@[165.227.249.18]>
In-Reply-To: <003101c2c700$8cd82c60$450a0a0a@txdwillis>
References: <003101c2c700$8cd82c60$450a0a0a@txdwillis>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Wed, 29 Jan 2003 14:54:57 -0800
To: <wgchairs@ietf.org>
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: RE: Authentication and email
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

At 1:07 PM -0600 1/28/03, Dean Willis wrote:
>I didn't look at the message. Here's the notification I got from mailman. It
>LOOKS like spam, based on contect and subject.
>
>--------------------
>As list administrator, your authorization is requested for the following
>mailing list posting:
>
>     List:    Sip@ietf.org
>     From:    camarillo@ericsson.com
>     Subject: Eager to see you
>     Reason:  Post by non-member to a members-only list

That's a virus, not spam. If you looked in the message, you would 
have seen a 132K executable payload (well, executable on some 
machines...)

--Paul Hoffman, Director
--VPN Consortium



From owner-wgchairs@ietf.org  Thu Jan 30 09:18:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29153
	for <wgchairs-archive@lists.ietf.org>; Thu, 30 Jan 2003 09:18:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eFbt-0006Li-00
	for wgchairs-list@ran.ietf.org; Thu, 30 Jan 2003 09:24:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eFVz-00065l-00
	for wgchairs@ran.ietf.org; Thu, 30 Jan 2003 09:18:03 -0500
Received: from c000.snv.cp.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA28961
	for <wgchairs@ietf.org>; Thu, 30 Jan 2003 09:09:50 -0500 (EST)
Received: (cpmta 1445 invoked from network); 30 Jan 2003 06:13:21 -0800
Received: from 24.147.218.40 (HELO dmitton.mitton.com)
  by smtp.mitton.com (209.228.32.71) with SMTP; 30 Jan 2003 06:13:21 -0800
X-Sent: 30 Jan 2003 14:13:21 GMT
Message-Id: <5.2.0.9.2.20030130091348.04436a20@getmail.mitton.com>
X-Sender: david@getmail.mitton.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 30 Jan 2003 09:16:23 -0500
To: wgchairs@ietf.org
From: David Mitton <david@mitton.com>
Subject: Re: Authentication and email
In-Reply-To: <6C0816A4-32A4-11D7-BA74-00039357A82A@extremenetworks.com>
References: <20030127234908.T3196-100000@oak.packetdesign.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-wgchairs@ietf.org
Precedence: bulk

On 1/28/2003 04:39 AM -0500, RJ Atkinson wrote:

>On Mon, 27 Jan 2003, Harald Tveit Alvestrand wrote:
>>checking:
>>
>>were those SPAM mails, or were those VIRUS mails?
>>we know that this has been a problem with virii, but so far, I haven't
>>seen
>>spammers using this deliberately.
>
>Harald,
>
>There definitely have been many non-virus spam messages sent out using
>forgeries of one of my email addresses as the claimed source in the
>From: line of the mail headers.  I have also seen non-virus spam
>forgeries
>using other IETF folks' mail address as the alleged source in the
>From: line.
>
>It is pretty clear that at least one spammer is using online archives
>of IETF mailing lists as a place to grab From: information for their
>header forgeries.  Sigh.
>
>Ran

I'll point out that mailing list archives is just one place.

The RFCs and Drafts themselves also expose your email addresses in the 
Authors sections.

Dave.
---
Yes, it's happened to me too. 





From owner-wgchairs@ietf.org  Fri Jan 31 04:25:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01924
	for <wgchairs-archive@lists.ietf.org>; Fri, 31 Jan 2003 04:25:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eXQh-0004QO-00
	for wgchairs-list@ran.ietf.org; Fri, 31 Jan 2003 04:25:47 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eXPv-0004OS-00
	for wgchairs@ran.ietf.org; Fri, 31 Jan 2003 04:24:59 -0500
Received: from d12lmsgate-4.de.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01896
	for <wgchairs@ietf.org>; Fri, 31 Jan 2003 04:21:11 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-4.de.ibm.com (8.12.3/8.12.3) with ESMTP id h0SG0tuk116614;
	Tue, 28 Jan 2003 17:09:54 +0100
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id h0SG0Snr080184;
	Tue, 28 Jan 2003 17:00:28 +0100
Received: from dhcp23-27.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03)
          id AA27318 from <brian@hursley.ibm.com>; Tue, 28 Jan 2003 17:00:26 +0100
Message-Id: <3E36A8EF.C16029F@hursley.ibm.com>
Date: Tue, 28 Jan 2003 16:59:43 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: Spencer Dawkins <sdawkins@cynetanetworks.com>
Cc: "Wgchairs Mailing List (E-mail)" <wgchairs@ietf.org>
Subject: Re: FW: RFC bandwith, packet size and latency
References: <9255B6CD76A88943A3062F7D4E6432F55C3727@mail.cynetanetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'm a very strong proponent of the naming convention.

Speaking as a member of the IETF at large:
It's the main criterion I use to decide whether to read a draft
that's in a peripheral area of interest for me. During the weeks
before an IETF, it's a life-saver.

Speaking as a WG chair:
It's a useful management tool and a very effective filter for
off-charter or non-consensual darfts.

Henning's statistics are fascinating, by the way.

   Brian

Spencer Dawkins wrote:
> 
> This posting just appeared on the problem-statement mailing list. It seems to confirm that there's actually a disadvantage to renaming an I-D when it's accepted as a working group deliverable (makes it harder to track how long things take in the IETF).
> 
> Have we ever identified an ADVANTAGE?
> 
> In the working group chair training sessions, Steve Coya just says that "working group deliverable" isn't based on the name of the draft (it's a separate field in the database). He doesn't encourage or discourage the name changes.
> 
> Henning also points out the difficulty this creates for IPR searches and suggests that the RFC Editor could tie the versions together. This solves the IPR problem if you get as far as an RFC...
> 
> Any thoughts on whether renaming drafts is worth the effort?
> 
> Spencer
> 
> > -----Original Message-----
> > From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> > Sent: Monday, January 27, 2003 8:57 PM
> > To: Harald Tveit Alvestrand; problem-statement@alvestrand.no
> > Subject: RFC bandwith, packet size and latency
> >
> >
> > I've gathered some additional data on the RFC publication process and
> > imported the data into EDAS (a publication management system that I
> > wrote). The results are at
> > http://www.cs.columbia.edu/~hgs/internet/rfc.shtml
> >
> > The results differ slightly from the earlier ones since I was able to
> > match additional RFCs by their I-D tag. However, the basic
> > gist is the
> > same and the trend has taken a large tick upwards in 2002:
> > the average
> > delay for RFCs published in 2002 was 2 years and 2 months.
> > (The maximum
> > was 5 years and 2 months!) As discussed in more detail on the
> > web page,
> > this estimate is likely low, since there seems to be an increasing
> > tendency in some working groups to let a draft go through a number of
> > draft-personal stages before becoming draft-ietf-wg. If the draft
> > changed its title during that time, I cannot match it and thus only
> > measure the time from draft-ietf.
> >
> > As others have pointed out, it's amazing how painful
> > gathering this data
> > is. Since everything is in more-or-less random text format, with
> > occasional changes, parsing is prone to errors. I did a few sanity
> > checks, but this is a good project for a forensical statistician.
> >
> > Also, in recent years, even the IMR is incomplete in its I-D list, so
> > that I have no data on a number of -00 records. This explains some of
> > missing data points (where the number of published RFCs is
> > much larger
> > than the number of measured RFCs).
> >
> > It would be trivial for the RFC editor to gather the "first
> > draft" time
> > from the authors. (This would also be helpful for IPR issues.)
> >
> > If somebody wants to play with the data, let me know and I
> > can give them
> > SQL access. (No, not Microsoft SQL...)
> >
> > Henning



From owner-wgchairs@ietf.org  Fri Jan 31 11:12:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10971
	for <wgchairs-archive@lists.ietf.org>; Fri, 31 Jan 2003 11:12:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18edov-000587-00
	for wgchairs-list@ran.ietf.org; Fri, 31 Jan 2003 11:15:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18edny-000567-00
	for wgchairs@ran.ietf.org; Fri, 31 Jan 2003 11:14:14 -0500
Received: from dinaras.cnri.reston.va.us (host-4-249.cnri.reston.va.us [10.27.4.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10859;
	Fri, 31 Jan 2003 11:09:18 -0500 (EST)
Message-Id: <5.1.0.14.2.20030131111300.021feec0@odin>
X-Sender: dinaras@odin
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 31 Jan 2003 11:13:57 -0500
To: wgchairs@ietf.org, bofchairs@ietf.org
From: Dinara Suleymanova <dinaras@ietf.org>
Subject: 56th IETF WG & BOF Scheduling
Cc: iesg@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-wgchairs@ietf.org
Precedence: bulk

56th IETF in San Francisco, CA
Meeting Dates: March 16-21, 2003

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

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

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

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

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

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

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

IETF Chair
Harald Alvestrand <Harald@Alvestrand.no>

Applications Area (app)
Patrik Faltstrom <paf@cisco.com>
Ned Freed <ned.freed@mrochek.com>

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

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

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

Security Area (sec)
Jeffrey Schiller <jis@mit.edu>
Steve Bellovin <smb@research.att.com>

Sub-IP Area (sub)
Scott Bradner <sob@harvard.edu>
Bert Wijnen <bwijnen@lucent.com>

Transport Area (tsv)
Scott Bradner <sob@harvard.edu>
Allison Mankin <mankin@psg.com>

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

Figures from the 55th IETF, Atlanta, GAaaa 127
adslmib 10
apparea 146
atommib 10
avt 141
bmwg 21
calsch 25
ccamp 158
crisp 39
dccp 93
dhc 112
dnsext 167
dnsop 153
eap 199
entmib 24
enum 78
fax+vpim 23
forces 70
geopriv 44
gsec 67
gsmp 34
idr 179
idwg 33
ieprep 128
imapext 14
impp 77
inch 37
ipcdn 22
ipfix 49
ipo 66
ipoib 21
ippm 74
ipr 118
ips 96
ipsec 222
ipseckey 118
ipsp 88
iptel 103
krb-wg 63
l2tpext 27
ldapbis 33
ldup 31
lemonade 85
magma 119
manet 167
mboned 101
midcom 149
mmusic 88
mobileip 192
mpls 207
msec 96
nemo 186
nfsv4 17
nomcom 44
nsis 276
opes 59
ospf 76
pana 246
pim 78
pkix 97
ppvpn 211
provreg 46
psamp 61
ptomaine 84
pwe3 156
rddp 59
rmonmib 35
rmt 48
rohc 34
rpsec 150
rserpool 24
rtgarea 118
saag 163
sacred 23
seamoby 84
secsh 36
send 64
simple 139
sip 161
sipping 220
smime 38
sming 35
speechsc 47
spirits 22
sub-ip 88
syslog 40
tewg 115
tls 61
trade 10
trigtran 149
tsvwg 203
udlr 33
v6ops 261
webdav 29
xmpp 125
zerouter 223









From owner-wgchairs@ietf.org  Fri Jan 31 12:12:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12343
	for <wgchairs-archive@lists.ietf.org>; Fri, 31 Jan 2003 12:12:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eel0-0008HB-00
	for wgchairs-list@ran.ietf.org; Fri, 31 Jan 2003 12:15:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e1Je-0004mX-00
	for wgchairs@ran.ietf.org; Wed, 29 Jan 2003 18:08:22 -0500
Received: from above.proper.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02821
	for <wgchairs@ietf.org>; Wed, 29 Jan 2003 18:00:19 -0500 (EST)
Received: from [165.227.249.18] (165-227-249-18.client.dsl.net [165.227.249.18])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id h0TN3ko05490
	for <wgchairs@ietf.org>; Wed, 29 Jan 2003 15:03:46 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210219ba5e0c696c00@[165.227.249.18]>
In-Reply-To: <3E369EAE.80761DAC@lmf.ericsson.se>
References: <3E354398.BF1D5575@lmf.ericsson.se>
 <611987020.1043699189@localhost> <3E3674FA.202781D7@lmf.ericsson.se>
 <674756478.1043761959@localhost> <3E369EAE.80761DAC@lmf.ericsson.se>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Wed, 29 Jan 2003 15:02:54 -0800
To: wgchairs@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: Authentication and email
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-wgchairs@ietf.org
Precedence: bulk

At 5:15 PM +0200 1/28/03, Gonzalo Camarillo wrote:
>And after giving them those speeches, we come back "home" to the IETF
>and say that email security is undoable for our mailing lists for some
>reason... it seems that MUSTs, SHOULDs and security considerations
>sections do not apply to us ;o)

This is an absurd argument. The security you are trying to achieve in
3GPP is completely unrelated to spam prevention.

I assume that anyone who is advocating using S/MIME or PGP for
spam-reduction has never used either protocol on a daily basis for
mail filtering. And I say this as one of the strongest public
proponents of those protocols. S/MIME and PGP are used for
authenticating the content of the messages, not for authenticating
the sender. If that doesn't make sense to you, please go read the
protocols: they're all on standards track and have been for many
years. Summaries and links to the RFCs can be found at
<http://www.imc.org/smime-pgpmime.html>.

--Paul Hoffman, Director
--Internet Mail Consortium





From owner-wgchairs@ietf.org  Fri Jan 31 12:57:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13770
	for <wgchairs-archive@lists.ietf.org>; Fri, 31 Jan 2003 12:57:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18efSX-0001Hm-00
	for wgchairs-list@ran.ietf.org; Fri, 31 Jan 2003 13:00:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18efRm-0001GL-00
	for wgchairs@ran.ietf.org; Fri, 31 Jan 2003 12:59:26 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13733
	for <wgchairs@ietf.org>; Fri, 31 Jan 2003 12:55:37 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9FFE7621B8; Fri, 31 Jan 2003 18:59:09 +0100 (CET)
Date: Fri, 31 Jan 2003 09:35:09 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Spencer Dawkins <sdawkins@cynetanetworks.com>,
        "Wgchairs Mailing List (E-mail)" <wgchairs@ietf.org>
Subject: Re: FW: RFC bandwith, packet size and latency
Message-ID: <950906160.1044005709@localhost>
In-Reply-To: <9255B6CD76A88943A3062F7D4E6432F55C3727@mail.cynetanetworks.com>
References:  <9255B6CD76A88943A3062F7D4E6432F55C3727@mail.cynetanetworks.com>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

not relevant to what the posting is about:

note that Henning's statistics are for the time of the whole IETF process - 
from the posting of internet-draft -00 to the publication of the finished 
RFC.

This doesn't tell us anything about how long the WG, the IESG or the RFC 
Editor spends on the document - it's the sum of all those times.

                      Harald

--On 28. januar 2003 08:41 -0600 Spencer Dawkins 
<sdawkins@cynetanetworks.com> wrote:

> This posting just appeared on the problem-statement mailing list. It
> seems to confirm that there's actually a disadvantage to renaming an I-D
> when it's accepted as a working group deliverable (makes it harder to
> track how long things take in the IETF).





From owner-wgchairs@ietf.org  Fri Jan 31 12:59:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13946
	for <wgchairs-archive@lists.ietf.org>; Fri, 31 Jan 2003 12:59:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18efUU-0001Nu-00
	for wgchairs-list@ran.ietf.org; Fri, 31 Jan 2003 13:02:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18efTu-0001Lv-00
	for wgchairs@ran.ietf.org; Fri, 31 Jan 2003 13:01:38 -0500
Received: from fridge.docomolabs-usa.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13792
	for <wgchairs@ietf.org>; Fri, 31 Jan 2003 12:57:48 -0500 (EST)
Message-ID: <00ce01c2c952$8c86a210$1d6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <wgchairs@ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
References: <3E354398.BF1D5575@lmf.ericsson.se> <611987020.1043699189@localhost> <3E3674FA.202781D7@lmf.ericsson.se> <674756478.1043761959@localhost> <3E369EAE.80761DAC@lmf.ericsson.se> <p05210219ba5e0c696c00@[165.227.249.18]>
Subject: Re: Authentication and email
Date: Fri, 31 Jan 2003 09:59:50 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-wgchairs@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> At 5:15 PM +0200 1/28/03, Gonzalo Camarillo wrote:
> >And after giving them those speeches, we come back "home" to the IETF
> >and say that email security is undoable for our mailing lists for some
> >reason... it seems that MUSTs, SHOULDs and security considerations
> >sections do not apply to us ;o)
>
> This is an absurd argument. The security you are trying to achieve in
> 3GPP is completely unrelated to spam prevention.
>
>

I would more characterize it as a category error.

IMHO, spam reduction has more to do with economics. As long as sending millions
of unsolicited emails is cheap, the arms race between spam filters and spammers
will continue.

As evidence in a similar area, compare the volume of junk mail received by
people in Europe compared to the US. Postal rates in Germany are about 3 to 5
times what they are in the US for the equivalent class and distance. My
brother-in-law, who lives in Nuerenberg, receives almost no junk mail. In
contrast, I was receiving on the average about 10 credit card solicitations a
week last fall, in addition to assorted other garbage. Over the holidays, the
volume of credit card solicitations went to zero, but it has gone back up to 3
this week.

However, I don't think there is a clean technical solution to this problem, like
"use PGP" or "use S/MIME".

                jak




