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

dromasca <notifications@github.com> Tue, 29 September 2015 08:16 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 D8B611A21BE for <sacm@ietfa.amsl.com>; Tue, 29 Sep 2015 01:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 485MOiuTeWkO for <sacm@ietfa.amsl.com>; Tue, 29 Sep 2015 01:16:02 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext7.iad.github.net [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E3E41A21BC for <sacm@ietf.org>; Tue, 29 Sep 2015 01:16:02 -0700 (PDT)
Date: Tue, 29 Sep 2015 01:16:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1443514561; bh=90/TqIY9cFIHCSbK8dYi9ODvuvuoNCrgGhlAz1nYz10=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GZISMBpQO5l9dYeWeH8fQuGxMY2e8Kyx1VosZYxaIB1yi4PQPrQOjIp5gWJGqWlda Ht7gfcmWZAVT7Bpd6J4fEjd5Z0AfaN9yzO/L6yxmAMaxFasidWjrl7lBQiKasjrIrZ 6r0O4XrwDYJo1mYZxpd784Nz1mKqgWRslfuPEtwI=
From: dromasca <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/143981529@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_560a48c1545b2_46ac3fd8f117f2a04688d5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dromasca
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/BwmpaBkYSdZIQDuHAu54-pXYp6A>
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+00a6c4d1a8d8ccf16022e40b8c3724708d162d422582fb8d92cf0000000112220ac192a169ce05cd0b75@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: Tue, 29 Sep 2015 08:16:14 -0000

Hi,

This looks good, but I have a clarification question. What does ‘filtering requirements at the data model MUST be applied’ mean? We already have OP-005 which states that ‘The query operation MUST support filtering’. Why do we need another capitalized MUST? Or do we have something else in mind?

Thanks and Regards,

Dan


From: Nancy [mailto:notifications@github.com]
Sent: Tuesday, September 29, 2015 12:50 AM
To: sacmwg/draft-ietf-sacm-requirements
Subject: Re: [draft-ietf-sacm-requirements] Do we need a privacy section (#55)


Wow, this has been a good discussion. Given that this is a requirements draft, I'm not sure how much information we need to provide (RFC 6973 is a good base to recommend). So here is a proposed new section to address some of this (please comment so that I can place into the next version):

5.2. Privacy Considerations
SACM information may contain sensitive information about the target
endpoint as well as revealing identity information of the producer or
consumer of such information. Similarly, as part of the SACM
discovery mechanism, the advertised capabilities (and roles, e.g.
SACM components enabled) by the endpoint may be construed as private
information. There may be applications as well as business and
regulatory practicess that require that aspects of such information
be hidden from any parties that do not need to know it.

Data confidentiality can provide some level of privacy but may fall
short where unecessary data is still transmitted. In those cases,
filtering requirements at the data model MUST be applied to ensure
that such data is not disclosed. [RFC6973] provides guidelines for
which SACM protocols and information and data models should follow.

Comments? - Nancy

—
Reply to this email directly or view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sacmwg_draft-2Dietf-2Dsacm-2Drequirements_issues_55-23issuecomment-2D143883721&d=BQMCaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=hrq1G9WeSgCouO44QrxIXe1nGJpwyhNtHF8RM-QqEcA&s=rfaqlB3q6Mk05_NupcV1d66o8iCrCN_1qMRshljzO3c&e=>.


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