[sacm] GitHub Issue Tracking: 2015-08-07

"Adam W. Montville" <adam.w.montville@gmail.com> Fri, 07 August 2015 11:30 UTC

Return-Path: <adam.w.montville@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 44ADA1A8943 for <sacm@ietfa.amsl.com>; Fri, 7 Aug 2015 04:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_MESSAGE=0.001, 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 g2E4-In5ed2s for <sacm@ietfa.amsl.com>; Fri, 7 Aug 2015 04:30:32 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (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 3BC041A8793 for <sacm@ietf.org>; Fri, 7 Aug 2015 04:30:32 -0700 (PDT)
Received: by obnw1 with SMTP id w1so76715704obn.3 for <sacm@ietf.org>; Fri, 07 Aug 2015 04:30:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=yKCxD5xGy9AwJLXSupaeE0fhptJ7l68qZUEpd3F+CSY=; b=c4RItfWjuvU77m/hi3M/YSUDOtzDfrUJ906gCiQV25S9XW8i3ruSG3LijWxBFk4koM WRVr/lOv56g1eqYWywE3NNrnsBMoekNprCI1uKCEIuYs5iEiRp0M0zMbxYCHkREtu4tu Mcf7sldD7FEv9oDD6/zi7bpUttuSxRZuWpSTBEtk4iK0TL4TVeNWa0boMm1EmoWXPisa KoQfTL0qdBVTVs8WRlv5rDAyZIECUslphmoxlkjvgih5S8IbSBhHpzTpoQgpRveTqOa1 rKTTuKVJsXVwcY0esOSLSvJ22WOSgSHrGSJfxSMYGG0omR16bsRntwgj8VvyUaTrpRPL eP2A==
X-Received: by 10.60.177.195 with SMTP id cs3mr6107232oec.37.1438947031675; Fri, 07 Aug 2015 04:30:31 -0700 (PDT)
Received: from adams-mac-mini.attlocal.net ([2602:306:3406:4830:9512:e84:4e1a:9f7f]) by smtp.gmail.com with ESMTPSA id f3sm5910009obm.18.2015.08.07.04.30.29 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Aug 2015 04:30:30 -0700 (PDT)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1D30795B-3AAF-40D1-8FB6-23CEBA312BCD"
Message-Id: <E9EFE38C-D65C-42A1-9EB9-A383BD242068@gmail.com>
Date: Fri, 07 Aug 2015 06:30:25 -0500
To: "<sacm@ietf.org>" <sacm@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/2vnnI1U9dAMhUEA82T8_a-DL74Q>
Subject: [sacm] GitHub Issue Tracking: 2015-08-07
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: Fri, 07 Aug 2015 11:30:34 -0000

Hi.

I’ve updated our GitHub issue tracking here: https://tools.ietf.org/wg/sacm/trac/wiki/SacmGitHubIssueStats <https://tools.ietf.org/wg/sacm/trac/wiki/SacmGitHubIssueStats>.  There are four outstanding issues [1][2][3][4] for the Requirements draft, which we were hoping to get into WGLC soon.  

It seems that [1] requires a few other reviewers.  If you have five minutes, please review the following text taken from the Requirements draft and comment on [1]:

DM-006  Provider Identification: The interfaces and actions in the
    data model MUST include the ability to identify data from a specific
    provider.  For example, a SACM consumer should be able to request
    all data to come from a specific provider (e.g.  Provider A) as
    there can be a larger set of providers.

[2] and [3] appear to be nits for the draft authors to fix.

[4] poses a question about whether the Requirements draft should address privacy considerations.  If you have a minute, please review the thread at [4] and opine.  If you’re further inclined, offer some suggestions for improvement (i.e. provide text, even if it’s just a start at something).

Thanks for your time today - hope you all have a great weekend!

Adam


[1] https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/59 <https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/59>
[2] https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/58 <https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/58>
[3] https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/57 <https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/57>
[4] https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/55 <https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/55>