Re: IETF privacy policy - update

Marshall Eubanks <tme@americafree.tv> Mon, 05 July 2010 18:28 UTC

Return-Path: <tme@americafree.tv>
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 104803A68DD for <ietf@core3.amsl.com>; Mon, 5 Jul 2010 11:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.74
X-Spam-Level:
X-Spam-Status: No, score=-100.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, USER_IN_WHITELIST=-100]
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 28Wp1B7G2vUl for <ietf@core3.amsl.com>; Mon, 5 Jul 2010 11:28:36 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id ECE913A676A for <ietf@ietf.org>; Mon, 5 Jul 2010 11:28:35 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 2E9CC7D181EF; Mon, 5 Jul 2010 14:28:37 -0400 (EDT)
Message-Id: <4B42EB41-0502-4D51-8B43-A3EC30B58643@americafree.tv>
From: Marshall Eubanks <tme@americafree.tv>
To: dcrocker@bbiw.net
In-Reply-To: <4C322170.9040903@dcrocker.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: IETF privacy policy - update
Date: Mon, 5 Jul 2010 14:28:36 -0400
References: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org> <4C322170.9040903@dcrocker.net>
X-Mailer: Apple Mail (2.936)
Cc: 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: Mon, 05 Jul 2010 18:28:37 -0000

<wearing no hats>

On Jul 5, 2010, at 2:16 PM, Dave CROCKER wrote:

>
>
> On 7/5/2010 9:05 AM, Alissa Cooper wrote:
>> In discussing the policy with the IAOC and others, it seems clear  
>> that the RFC
>> model is probably not the best model for maintaining and updating a  
>> document
>> like this.
>
>
> While I could imagine that you are correct, the answer isn't at all  
> clear to me.
>
> Presumably it should represent community consensus and should not  
> change all that often.  And having an archival copy makes sense.  So  
> I'm not understanding why it should not be published as an RFC.
>

I assume (for I do not know) that people are worried about time  
involved in bringing a new RFC to publication.

I don't see why this couldn't be divided in the way that the Trust  
Legal Provisions have been :

- a RFC to set the _goals_ and basic framework of the privacy policy,  
which might change something like every 5 years (or less often if we  
are lucky) and

- an IAOC document for the actual privacy policy itself, which could  
be changed very quickly if (say) lawyers started beating down the doors.

Regards
Marshall




> Please clarify.
>
> Thanks.
>
> d/
>
> ps. I, too, like the idea of having the policy.  I'm only asking  
> about its form.
>
> -- 
>
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>