IETF Logo Mail Archive

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

llorenzin <notifications@github.com> Thu, 24 September 2015 18:33 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 DA5261A6FB2 for <sacm@ietfa.amsl.com>; Thu, 24 Sep 2015 11:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.908
X-Spam-Level:
X-Spam-Status: No, score=-5.908 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_16=1.092, 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 KHsXBGfpedAP for <sacm@ietfa.amsl.com>; Thu, 24 Sep 2015 11:33:12 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E58621A6F66 for <sacm@ietf.org>; Thu, 24 Sep 2015 11:33:11 -0700 (PDT)
Date: Thu, 24 Sep 2015 11:33:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1443119591; bh=VxBeEbfo2rB1EVlBgzwBRHXjAlTaCMi7EIOvE19MLfI=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=G0ukQyFWo+bK8aDl7CxJvKkXNwQKoM/xOLaeIiTqGtSJ4n0ZLsxNYy652IIwgfWhA mWcv7oQ24vHXNHN8tt0YO53PVPCJrzIMq3lIHZtm2UFwfT1LO4QoJFKed1ynYONpxD Y6A6lPbcQFfUg5HzpypwBMZYoqb2H0Wzyzu48Mfk=
From: llorenzin <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/143013446@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_560441e72f3e4_2cce3ff0fb5332bc11419c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: llorenzin
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/9fKeQgvZ6thXIH7Q7MI5eiW0_fo>
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+00a6c4d196bd106cc062ead6a53a672bc9283358516f41e092cf00000001121c03e792a169ce05cd0b75@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: Thu, 24 Sep 2015 18:33:14 -0000

In Prague, Lucy Lynch offered to review the drafts and provide comments on privacy
Dan will send her a reminder and solicit feedback from her.
Authors are soliciting a volunteer to write a privacy considerations section.  (I do not have the experience to do so, and my impression is that Nancy does not have the bandwidth.)
Kathleen offers to assist - can suggest text if it's not there by the time we get to AD review.  Will let us know if it's lacking or will have problems that will hold it up in IESG.
Henk - comments on-list about endpoint identifying attributes will have impact on this section.

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

v2.23.0 | Report a Bug | By Email