IETF Logo Mail Archive

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

Jim Schaad <notifications@github.com> Sun, 26 July 2015 14:51 UTC

Return-Path: <noreply@github.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 DFC0D1A89C7 for <sacm@ietfa.amsl.com>; Sun, 26 Jul 2015 07:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.241
X-Spam-Level:
X-Spam-Status: No, score=-2.241 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham
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 Uurs_je-_zV9 for <sacm@ietfa.amsl.com>; Sun, 26 Jul 2015 07:51:13 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6688B1A89AA for <sacm@ietf.org>; Sun, 26 Jul 2015 07:51:13 -0700 (PDT)
Date: Sun, 26 Jul 2015 07:51:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1437922272; bh=44lF/YIVrvDPlOyzQT7jbHxFjhYeNi0nkeauMV3CDcc=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=soIcrFDkgQjeGUTpEC5Ry5OYOWdK5R2KTI4gaiW3u735bEq/Kc2qhOT4ohoV3okN5 YCKzgGWL8UJwa6TObsNXHF1VA25AsiwWzVHqPwcxFScMDUxJD+0aFk94qfMCjrw1JM 3Vt+xFy4W0QPJ70WrusvqgrzZNqlik8R4RmNB9Rs=
From: Jim Schaad <notifications@github.com>
To: sacmwg/draft-ietf-sacm-requirements <draft-ietf-sacm-requirements@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-requirements/issues/55@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_55b4f3e08c3de_649a3f987ff1b2b81661fb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: jimsch
X-GitHub-Recipient: sacm
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/LWfEs_8s0pLJ6f5_qbM1h8Rp548>
Subject: [sacm] [draft-ietf-sacm-requirements] Do we need a privacy section (#55)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: sacmwg/draft-ietf-sacm-requirements <reply+00a6c4d1926f41a79ae2a898ecadd84075f786971c5af9c292cf0000000111ccb5e092a169ce05cd0b75@reply.github.com>
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, 26 Jul 2015 14:51:15 -0000

version -09

This is just a question.  The response may be that no change is needed.

Do we need to have a separate privacy question to highlight anything about both general privacy and pervasive monitoring.  This system is, in some respects, a pervasive monitoring system and we might need to highlight this.

---
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/55

v2.23.0 | Report a Bug | By Email