Re: IETF privacy policy - update

SM <sm@resistor.net> Mon, 05 July 2010 19:10 UTC

Return-Path: <sm@resistor.net>
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 457233A6987 for <ietf@core3.amsl.com>; Mon, 5 Jul 2010 12:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 w-4QSGvOnznI for <ietf@core3.amsl.com>; Mon, 5 Jul 2010 12:09:59 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 94C7B3A67F0 for <ietf@ietf.org>; Mon, 5 Jul 2010 12:09:59 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o65J9UE4004347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Jul 2010 12:09:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1278356981; x=1278443381; bh=SQioZiT4YY9YbtzmS1GTDcRJz9MnTxN9QMm3wBz7i+A=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=Bs5c30hXrnZlXG0oAw6rbZ4WDCg4WDcpMVvgWHpctcXctx032udJQ8dQlyCo1Vnl8 spWTspyu4bZqPkne6lKy//9H68Bzs9hPD+5vbdxWzaxtS6C23qG3doTtAS8AJFVoMe P08B/aOlvJHKEk0V+rC0aK/R/z8hEa/hhzNqu1CQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1278356981; x=1278443381; bh=SQioZiT4YY9YbtzmS1GTDcRJz9MnTxN9QMm3wBz7i+A=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=rxNmvk6MX5iXrYzXuOUA+1KM3YOBkDtJ5PjnI9gJkIAyhYeB1Vdn4ExlLzq2VCB0Y RPw6noUCoSQyjCrHBXwHNbuFtzkjJGDxHfRIKFlo3MCb82sQ/UH2F1cxmCRUUT9gND 2IuecsOKTFPlxwW24O5Ihoa5XLnRVGHrBKqES+EI=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=tK6O7WV0Hpf4Qkf1/B1ugunpOQ4iMjCeK+T66W8aMkNzu+M5NjShP2HWHKlW8l+o8 B/LrLtQNhZr6Gs+KB+TPFGczAksVTRCBP4waMZZup5uqq1hfRCfZ1Umw7KkCvtAuLjk 8zKrt69RJCynq3JGs8RADY1ydGDeMhOW88p0KUA=
Message-Id: <6.2.5.6.2.20100705114909.0c5f1838@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 05 Jul 2010 12:08:14 -0700
To: Alissa Cooper <acooper@cdt.org>
From: SM <sm@resistor.net>
Subject: Re: IETF privacy policy - update
In-Reply-To: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org>
References: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: Mon, 05 Jul 2010 19:10:02 -0000

Hi Alissa,
At 09:05 05-07-10, Alissa Cooper wrote:
>A few months ago I drew up a strawman proposal for a public-facing
>IETF privacy policy 
>(http://www.ietf.org/id/draft-cooper-privacy-policy-00.txt ). I've 
>submitted an update based on feedback received: 
>http://www.ietf.org/id/draft-cooper-privacy-policy-01.txt
>
>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. It is more likely to fall within the
>scope of the IAOC and/or the Trust. In order for the IAOC to consider
>taking this on and devoting resources to figuring out what its format
>should be, they need to hear from the community that a public-facing
>privacy policy is something that the community wants. So I have two
>requests for those with any interest in this:

A BCP represents community consensus.  I don't see how using the RFC 
publication is not the best model for maintaining and updating a document.

According to BCP 101:

   "The IETF undertakes its technical activities as an ongoing, open,
    consensus-based process."

   "The IETF Administrative Support Activity (IASA) provides the
    administrative structure required to support the IETF standards
    process and to support the IETF's technical activities."

   "The IAOC determines what IETF administrative functions are to be
    performed, and how or where they should be performed (whether
    internally within the IASA or by outside organizations), so as to
    maintain an optimal balance of functional performance and cost of
    each such function.  The IAOC should document all such decisions, and
    the justification for them, for review by the community."

I doubt that it is up to the IAOC to determine whether there is 
consensus on a privacy policy as it is a policy and not an 
administrative matter.

According to BCP 78:

   "The IETF Trust was recently formed to act as the administrative
    custodian of all copyrights and other intellectual property rights
    relating to the IETF Standards Process that had previously been held
    by ISOC and the Corporation for National Research Initiatives (CNRI)"

If you want community support, ask for the I-D to be published as a 
RFC by putting in a request to the IETF Chair.

Regards,
-sm