Re: Spam in the IETF's name?

"RL 'Bob' Morgan" <rlmorgan@washington.edu> Thu, 20 October 2005 15:40 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EScWr-0004c1-Is; Thu, 20 Oct 2005 11:40:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EScWp-0004bw-AB for ietf@megatron.ietf.org; Thu, 20 Oct 2005 11:40:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24175 for <ietf@ietf.org>; Thu, 20 Oct 2005 11:40:18 -0400 (EDT)
Received: from mxout3.cac.washington.edu ([140.142.32.166]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EScil-0006Dd-Uj for ietf@ietf.org; Thu, 20 Oct 2005 11:52:49 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9KFeL3e031113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Oct 2005 08:40:22 -0700
X-Auth-Received: from [192.168.1.104] (c-67-170-101-104.hsd1.wa.comcast.net [67.170.101.104]) (authenticated authid=rlmorgan) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9KFeIEh017656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Oct 2005 08:40:21 -0700
Date: Thu, 20 Oct 2005 08:40:32 -0700
From: RL 'Bob' Morgan <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@perf.cac.washington.edu
To: Harald Tveit Alvestrand <harald@alvestrand.no>
In-Reply-To: <8C1D3011ABF32F7AEB3D8477@svartdal.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.63.0510200840130.32699@perf.cac.washington.edu>
References: <ECB22632E1E1FAD19E47FFAB@B50854F0A9192E8EC6CDA126> <43576C59.1090802@zurich.ibm.com> <1115CFE58B1D40A44FA946E8@scan.jck.com> <4357B321.6010906@zurich.ibm.com> <8C1D3011ABF32F7AEB3D8477@svartdal.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: IETF <ietf@ietf.org>
Subject: Re: Spam in the IETF's name?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Thu, 20 Oct 2005, Harald Tveit Alvestrand wrote:

> That's what got me upset over that aspect; if it had started out "I and 
> a few other friends have this great idea that we're pushing in the IETF, 
> and we want to meet to talk about it", I'd only have been upset about 
> the method, not the content.

It seems to me the actual IETF involvement here (and I got the invitation 
too, more than once) is that the list is hosted @ietf.org.  I wasn't aware 
that IETF hosted lists for discussion of things that might become WGs.  I 
see from https://datatracker.ietf.org/public/nwg_list.cgi that in fact 
there are quite a few, including this one.  But I also see that such 
things require AD approval.  So presumably the dix@ietf.org initiators 
submitted something to the apps-area ADs to support this list creation. 
It might have been nice for this invitation to have included this material 
and to have mentioned this step, in the interest of making clear the 
status of the activity.

   - RL "Bob"


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