Re: [datatracker-rqmts] New Requirement

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 15 November 2010 19:30 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: datatracker-rqmts@core3.amsl.com
Delivered-To: datatracker-rqmts@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD3973A6D08 for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.907
X-Spam-Level:
X-Spam-Status: No, score=-99.907 tagged_above=-999 required=5 tests=[AWL=-0.688, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7y+uwuqm2VbS for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:30:15 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id BB2CD3A6D05 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 11:30:08 -0800 (PST)
Received: from [10.20.30.150] (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAFJUkIt081853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Nov 2010 12:30:48 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240823c9073a421353@[10.20.30.150]>
In-Reply-To: <4CE18751.7030002@gmail.com>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com>
Date: Mon, 15 Nov 2010 11:30:45 -0800
To: Royer Software and Services <royersoftwareandservices@gmail.com>, datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [datatracker-rqmts] New Requirement
X-BeenThere: datatracker-rqmts@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <datatracker-rqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/datatracker-rqmts>
List-Post: <mailto:datatracker-rqmts@ietf.org>
List-Help: <mailto:datatracker-rqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Nov 2010 19:30:15 -0000

>On 11/15/2010 2:17 AM, Jim Schaad wrote:
>>I believe that there may be situations where one wishes to create lists
>>based on data that is private.  In this case either the list must not be
>>able to be made public or it must be restricted based on the same
>>constraints as the data.
>>
>>An example of where this might occur is called for.
>>
>>The ISE might desire to add a field to the data tracker listing the set of
>>people who either have or have been asked to review a document.  This field
>>is restricted to the ISE and the IESB.  If these people create a list based
>>on the existence of a name in this field then it could be considered to be
>>restricted to a small set of people.

At 12:17 PM -0700 11/15/10, Royer Software and Services wrote:
>Why would it be a secret as to who viewed, read, or reviewed public documents?

That's not what Jim said. His example was some private data in the Datatracker.

--Paul Hoffman, Director
--VPN Consortium