Re: [sacm] [draft-ietf-sacm-requirements] Do we need a privacy section (#55)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Sun, 09 August 2015 13:02 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECBA1B2CCA for <sacm@ietfa.amsl.com>; Sun, 9 Aug 2015 06:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.37
X-Spam-Level:
X-Spam-Status: No, score=-0.37 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=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 Nvr37qkTeB27 for <sacm@ietfa.amsl.com>; Sun, 9 Aug 2015 06:02:10 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9FB71B2CC4 for <sacm@ietf.org>; Sun, 9 Aug 2015 06:02:09 -0700 (PDT)
Received: by qgeg42 with SMTP id g42so65720219qge.1 for <sacm@ietf.org>; Sun, 09 Aug 2015 06:02:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PH2W8cP8j6mpNCmG/KcQKBirXiNbwRt6lf6EW3kotqw=; b=DaK9Cv7hIanO5mlXow26Nsiv5Jq1+mi8U6O5k++IncQ8LyXSsx9tl3be4oRVhkK0AT NyORF3H6I6dFWmvboXUntD9x8tNGdsvg16LXjk0xQQyAsECHhQofzB5C5mtu8/HDUoC+ xYpywUkbIrpKeZxhkpKzirJYc5hCUhB2IG4WTjeEwJbEkaUTWfKMmyRbv7+cTvTSxm8v EmaC15R3dDZarSlDnhiYq9KiyZAb2vvaU2ICGz/zUsm9MuH8TVI68VBYmddCt1hAsva3 8ASmIgqpWjapXGcgVsbqNKz1jwl9r1vw5xwSyuMwT09/EmMa8Z6bZ57HszuGIFytY6jq Y/fw==
X-Received: by 10.140.237.73 with SMTP id i70mr31337561qhc.102.1439125329147; Sun, 09 Aug 2015 06:02:09 -0700 (PDT)
Received: from [192.168.1.4] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by smtp.gmail.com with ESMTPSA id a50sm1782977qga.39.2015.08.09.06.02.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Aug 2015 06:02:08 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-7A1099F6-1147-4A86-84DE-D57F9259DF2D"
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <sacmwg/draft-ietf-sacm-requirements/issues/55/128838977@github.com>
Date: Sun, 09 Aug 2015 09:02:07 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <777759E9-E0ED-4562-9EE0-9FA3354640D4@gmail.com>
References: <sacmwg/draft-ietf-sacm-requirements/issues/55@github.com> <sacmwg/draft-ietf-sacm-requirements/issues/55/128838977@github.com>
To: sacmwg/draft-ietf-sacm-requirements <reply+00a6c4d14bbfd36e4f73e33ad0dde968da8a378b1ae0e21392cf0000000111dce73992a169ce05cd0b75@reply.github.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/PZNIV2CHyzcc7Tz4u7Kj9vxOAJc>
Cc: sacmwg/draft-ietf-sacm-requirements <draft-ietf-sacm-requirements@noreply.github.com>, sacm <sacm@ietf.org>
Subject: Re: [sacm] [draft-ietf-sacm-requirements] Do we need a privacy section (#55)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Aug 2015 13:02:11 -0000

I had another thought after I sent my last message that should be helpful as you develop language prior to IETF last call.  Make sure the privacy considerations are not country specific.  The IETF references will help with that.  If you use NIST's, you'll also need to look at guidance from other countries, and that can get tricky.

Thanks,
Kathleen 

Sent from my iPhone

> On Aug 7, 2015, at 5:38 PM, Jim Schaad <notifications@github.com> wrote:
> 
> Adam,
> 
> While it is true that we are focused on the single enterprise systems. I will be shocked if there are not third parties that will offer to do the monitoring on my behalf. This means that they are going to have to ability to look not only at the systems and users in my enterprise, but potentially compare them against systems and users in other enterprises.
> 
> Also, although we are looking at single enterprise systems, my ISP is a single enterprise and can do the monitoring against me and anybody in my enterprise.
> 
> —
> Reply to this email directly or view it on GitHub.
> 
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm