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

adammontville <notifications@github.com> Fri, 07 August 2015 11:38 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 90F9C1B2B0A for <sacm@ietfa.amsl.com>; Fri, 7 Aug 2015 04:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.555
X-Spam-Level:
X-Spam-Status: No, score=-3.555 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, 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 XDTO0ePzH2NE for <sacm@ietfa.amsl.com>; Fri, 7 Aug 2015 04:38:44 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C8441B2B07 for <sacm@ietf.org>; Fri, 7 Aug 2015 04:38:44 -0700 (PDT)
Date: Fri, 07 Aug 2015 04:38:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1438947523; bh=dTHmOfKzIRW5TgOSX0CFZRrOtkYTU2BTaHpv5gyXZFQ=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sElWQCg6mkM6DLO+NNshfKbQCBTj28Vw+N5XqTRxCZADvjtOlQ49S379gXo6UYFdd DWGTOXAQY7aoTe6iNDLDvaXpVGBlwLYBH5wSjZx8QaJhuVQAr6nmWj3prdCJLzHijy hn4y0W6kCickWLCXirvkKhtebpZ/K0lX9n0U6AXQ=
From: adammontville <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/128680469@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-requirements/issues/55@github.com>
References: <sacmwg/draft-ietf-sacm-requirements/issues/55@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_55c498c35dcf5_59c93fe1a655329c402017"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: adammontville
X-GitHub-Recipient: sacm
X-GitHub-Reason: comment
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/pXth1xK6FBQxEMxfijVuoHUSdaU>
Cc: 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
Reply-To: sacmwg/draft-ietf-sacm-requirements <reply+00a6c4d1129080622850c5e27de14219f5265ff1c931c67092cf0000000111dc5ac392a169ce05cd0b75@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: Fri, 07 Aug 2015 11:38:46 -0000

I agree that privacy needs to be covered.  

Still, when we talk about *identity* or *identification* in this working group, we're talking about something different than PII data.  As such, there's this other issue for the information model https://github.com/sacmwg/draft-ietf-sacm-information-model/issues/21, which is seeking to get feedback on what a useful term other than identity might be.  The present candidate seems to be *designate*.  So, instead of "identify an endpoint" we would "designate an endpoint" or "collect AVPs from the designated set of endpoints".  

I also wouldn't go so far as to say that we're performing pervasive monitoring in the sense that mainstream media understands the term.  Our scope has always been single-enterprise, and it remains that way.

Again, privacy is important, but I don't think we're talking about PII as much as might be implied by our choice of terms.

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