Re: [APPS-REVIEW] Names to Nomcom

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 22 October 2008 16:03 UTC

Return-Path: <apps-review-bounces@ietf.org>
X-Original-To: apps-review-archive@optimus.ietf.org
Delivered-To: ietfarch-apps-review-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AEE028C144; Wed, 22 Oct 2008 09:03:00 -0700 (PDT)
X-Original-To: apps-review@core3.amsl.com
Delivered-To: apps-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E5AD28C144 for <apps-review@core3.amsl.com>; Wed, 22 Oct 2008 09:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level:
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgfgHHFK+3Us for <apps-review@core3.amsl.com>; Wed, 22 Oct 2008 09:02:55 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id B50C43A6BAC for <apps-review@ietf.org>; Wed, 22 Oct 2008 09:02:54 -0700 (PDT)
Received: from [172.16.2.186] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <SP9O-AAJ3X6P@rufus.isode.com>; Wed, 22 Oct 2008 17:04:08 +0100
Message-ID: <48FF4EE5.5000205@isode.com>
Date: Wed, 22 Oct 2008 17:03:49 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Eric Burger <eburger@standardstrack.com>
References: <B1AF1484-C022-4787-BDAD-8BF02DD04A19@standardstrack.com>
In-Reply-To: <B1AF1484-C022-4787-BDAD-8BF02DD04A19@standardstrack.com>
MIME-Version: 1.0
Cc: apps-review@ietf.org
Subject: Re: [APPS-REVIEW] Names to Nomcom
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Applications Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/apps-review>
List-Post: <mailto:apps-review@ietf.org>
List-Help: <mailto:apps-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: apps-review-bounces@ietf.org
Errors-To: apps-review-bounces@ietf.org

Eric Burger wrote:

> Nomcom has the mail list. I did not realize nomcom had special super- 
> secret IETF dispensation for warrant-less secret information  
> disclosure. Ooops - sorry I let folks know they are subject to  
> investigation by Nomcom. Sorry again - that was  a U.S.-centric  
> political statement ;-)
>
> I guess nomcom has special investigative powers that are not well  
> publicized. I couldn't find the section analogous to the Patriot 
> Act's  secret data capture provisions in RFC 3777...
>
> I suppose we should amend "Note Well" to include "Subscribing to an  
> IETF mail list may subject your e-mail address for IETF-only internal  
> use, beyond the mail list you have subscribed to. Trust us - it is 
> for  your own benefit. Really."
>
> IMHO, this particular use really is for our benefit, but I'm 
> massively  worried about the slippery slope we're sliding down.

I agree with you. It is better to explicitly ask people.

Regarding my original reply in this thread: I think I now understand why 
you've sent out the message that started this thread, but it could have 
been clearer on why you were asking for this information.

> Regards,
> Your way too paranoid for his own good list manager,
> Eric


_______________________________________________
APPS-REVIEW mailing list
APPS-REVIEW@ietf.org
https://www.ietf.org/mailman/listinfo/apps-review