Re: Proposed IETF Privacy Policy for Review
"Scott O. Bradner" <sob@sobco.com> Wed, 16 March 2016 20:12 UTC
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6026712D6DA for <ietf@ietfa.amsl.com>; Wed, 16 Mar 2016 13:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level:
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWcluofjAL3I for <ietf@ietfa.amsl.com>; Wed, 16 Mar 2016 13:12:25 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0242612D6DC for <ietf@ietf.org>; Wed, 16 Mar 2016 13:12:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 33B4018DEBB6; Wed, 16 Mar 2016 16:12:24 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9lois5X92l28; Wed, 16 Mar 2016 16:12:22 -0400 (EDT)
Received: from [10.0.1.16] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 7385D18DEBA7; Wed, 16 Mar 2016 16:12:22 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Proposed IETF Privacy Policy for Review
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <DE878486-1E9E-46F3-8AE8-6D211E39D419@sobco.com>
Date: Wed, 16 Mar 2016 16:12:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <085072B2-5BD9-45BE-8085-1A334B106F1D@sobco.com>
References: <20160316173701.25701.qmail@ary.lan> <DE878486-1E9E-46F3-8AE8-6D211E39D419@sobco.com>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pXDjyDmN-Wb2yJbKTh5GglUg5zc>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 16 Mar 2016 20:12:26 -0000
in addition “it is the right thing to do” Scott > On Mar 16, 2016, at 4:08 PM, Scott O. Bradner <sob@sobco.com> wrote: > > IETF Secretariat > c/o Association Management Solutions, LLC (AMS) > 48377 Fremont Blvd., Suite 117 > Fremont, California 94538 > >> On Mar 16, 2016, at 1:37 PM, John Levine <johnl@taugh.com> wrote: >> >>> but, even if we clearly say “we never do that” we still need to have the section since >>> California law says that we need to have such an ability for people to ask (its also the kind of thing that the EU >>> wants to see) >> >> Why is California law relevant? The IETF's legal bits are in Virgina >> or maybe D.C., not California. >> >> R's, >> John >> >> >> >
- Re: [IAB] Proposed IETF Privacy Policy for Review Eggert, Lars
- Re: Proposed IETF Privacy Policy for Review Martin Vigoureux
- Re: Proposed IETF Privacy Policy for Review JORDI PALET MARTINEZ
- Re: Proposed IETF Privacy Policy for Review Scott Bradner
- Re: Proposed IETF Privacy Policy for Review JORDI PALET MARTINEZ
- Re: Proposed IETF Privacy Policy for Review John Levine
- Re: Proposed IETF Privacy Policy for Review Scott O. Bradner
- RE: Proposed IETF Privacy Policy for Review Adrian Farrel
- Re: Proposed IETF Privacy Policy for Review Adam Roach
- Re: Proposed IETF Privacy Policy for Review Scott O. Bradner
- Re: Proposed IETF Privacy Policy for Review Scott O. Bradner
- Re: [IAOC] [IAB] Proposed IETF Privacy Policy for… Scott O. Bradner
- Re: [IAOC] [IAB] Proposed IETF Privacy Policy for… Scott O. Bradner
- Re: [IAOC] [IAB] Proposed IETF Privacy Policy for… Eggert, Lars
- Re: Proposed IETF Privacy Policy for Review Stephen Farrell
- Re: Proposed IETF Privacy Policy for Review Stephane Bortzmeyer
- Re: [IAB] Proposed IETF Privacy Policy for Review Paul Wouters
- Re: [IAB] Proposed IETF Privacy Policy for Review Scott Bradner
- Re: [IAB] Proposed IETF Privacy Policy for Review Paul Wouters
- Re: [IAOC] [IAB] Proposed IETF Privacy Policy for… Scott Bradner
- Re: [IAOC] [IAB] Proposed IETF Privacy Policy for… Scott Bradner
- Re: [IAOC] [IAB] Proposed IETF Privacy Policy for… Paul Wouters
- Proposed IETF Privacy Policy for Review IETF Administrative Director
- Re: [IAB] Proposed IETF Privacy Policy for Review John Levine
- Re: Proposed IETF Privacy Policy for Review Adam Roach
- Re: Proposed IETF Privacy Policy for Review S Moonesamy
- Re: Proposed IETF Privacy Policy for Review S Moonesamy
- Re: Proposed IETF Privacy Policy for Review Scott O. Bradner
- RE: Proposed IETF Privacy Policy for Review Adrian Farrel
- Re: Proposed IETF Privacy Policy for Review Tobias Gondrom
- Re: Proposed IETF Privacy Policy for Review Alissa Cooper
- Re: Proposed IETF Privacy Policy for Review S Moonesamy
- Re: Proposed IETF Privacy Policy for Review Scott O. Bradner
- Re: Proposed IETF Privacy Policy for Review S Moonesamy
- Re: Proposed IETF Privacy Policy for Review S Moonesamy
- Re: Proposed IETF Privacy Policy for Review Dave Crocker
- Re: [IAOC] Proposed IETF Privacy Policy for Review Scott O. Bradner
- Re: Proposed IETF Privacy Policy for Review Doug Royer