Re: IETF privacy policy - update

Melinda Shore <shore@arsc.edu> Wed, 07 July 2010 19:00 UTC

Return-Path: <shore@arsc.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 336C33A68F6 for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 12:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 CdAR+R0C3Vnd for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 12:00:04 -0700 (PDT)
Received: from arsc.edu (mail1.arsc.edu [IPv6:2001:480:150:75::229]) by core3.amsl.com (Postfix) with ESMTP id 244653A6876 for <ietf@ietf.org>; Wed, 7 Jul 2010 12:00:02 -0700 (PDT)
Received: from viking-e0.arsc.edu (viking-e0.arsc.edu [IPv6:2001:480:150:75:223:32ff:feda:4a52]) by arsc.edu (20090828.ARSC) with ESMTP id o67IxbgX017704; Wed, 7 Jul 2010 10:59:37 -0800 (AKDT)
Subject: Re: IETF privacy policy - update
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Melinda Shore <shore@arsc.edu>
In-Reply-To: <573C3FFA-B8CA-4B71-9128-07863DF1CF2B@muada.com>
Date: Wed, 07 Jul 2010 10:59:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <64B16C25-EF01-41D5-940B-750A6018AB9F@arsc.edu>
References: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org> <8FBEA0C7-9B80-4860-AFAE-FB5A19E660EF@muada.com> <4C33A406.1090801@bogus.com> <BBDFC939-2109-41BB-B4E1-BE2CEE43B8CA@muada.com> <9C72FA78-C9C2-4719-9BFD-112ABEFA7117@cdt.org> <56522CF0-088B-4027-AF45-A6075A7EA666@muada.com> <51D591B3-1954-47A6-A40A-7DCE6DDD5CF0@cdt.org> <A68985E3-A34B-47AB-A6A2-E6718E505652@muada.com> <B75D4F49-2361-4706-A24A-D5E7026EE58D@cdt.org> <573C3FFA-B8CA-4B71-9128-07863DF1CF2B@muada.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
X-Mailer: Apple Mail (2.1081)
X-CanIt-Geo: No geolocation information available for 2001:480:150:75:223:32ff:feda:4a52
X-CanItPRO-Stream: default
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . com) on IPv6:2001:480:150:75::167
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 19:00:05 -0000

On Jul 7, 2010, at 8:57 AM, Iljitsch van Beijnum wrote:
> In the meantime, BGP and HTTP, to name just two of the protocols without which the internet and the web wouldn't exist, still don't have standard status.

I think I'd probably argue that the context has changed.  It
wasn't *that* long ago that there were publicly-available 
systems with no root password that everybody knew about, too.

But anyway, I don't think it's at all clear to me that navel-
gazing is impeding progress on BGP or HTTP.  I think it's 
possible that more navel-gazing may be called for, actually,
to solve problems like this.  

I think there has been a sufficiently large number of ridiculous
legal threats thrown around to suggest that getting policies
nailed down and written up isn't a bad idea.

Melinda