Re: [datatracker-rqmts] New Requirement

Royer Software and Services <royersoftwareandservices@gmail.com> Mon, 15 November 2010 19:17 UTC

Return-Path: <royersoftwareandservices@gmail.com>
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 AB8DB3A6BFB for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level:
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 yA3skZnJKtdL for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:17:05 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 8422A3A6C7C for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 11:17:05 -0800 (PST)
Received: by gwb10 with SMTP id 10so3100335gwb.31 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 11:17:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=f4zX3rTSdH6Npy74ES+smUrGMMlGcgOGg2jJ4FP0y+U=; b=Q2bO3GOLiGUkSD+w3CfRMkRJcR/JVVc7Hv+vAx37PxzAjHtVgdiDjRS8EIRkHp9mej 9tzt5d2euF6G6WOE5C7L3pAW9m7VMeA5nRa3c/tCplGOc3VVXOPgIr7ciC/zE0KkUtdJ qMpS3iHy1CgTQYO6E21zrrbGNiYpd1pvWBskE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Rz87znXAwBhR2BlejGpT5vR97Z18M7dXWM7CVe3IMlTpPL7jluBSibWymcC4Qb3RXV DBfa3mgZjCMteJ/hH01z79RjX5BlQkodf3BbS0RYuUnGZuM2Nkl+CtU6WeErJ8dNWqXt GL2iAvaygjZZZeLgBhWqrMoAGI2tu8sZa3tIY=
Received: by 10.100.47.1 with SMTP id u1mr4454950anu.113.1289848667131; Mon, 15 Nov 2010 11:17:47 -0800 (PST)
Received: from [192.168.0.58] ([63.227.129.161]) by mx.google.com with ESMTPS id b22sm4082150anb.35.2010.11.15.11.17.44 (version=SSLv3 cipher=RC4-MD5); Mon, 15 Nov 2010 11:17:45 -0800 (PST)
Message-ID: <4CE18751.7030002@gmail.com>
Date: Mon, 15 Nov 2010 12:17:37 -0700
From: Royer Software and Services <royersoftwareandservices@gmail.com>
Organization: http://Project-Contracting.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: datatracker-rqmts@ietf.org
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com>
In-Reply-To: <069201cb84a5$f3600e60$da202b20$@augustcellars.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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:17:12 -0000

Why would it be a secret as to who viewed, read, or reviewed public 
documents?

And how would anyone know that 'some-random-list-name' was an official
review directed by the ISE or IESB by X, Y, and  Z @somedomains ?

Royer Software and Services
http://Project-Contracting.com
(208) 806-1358 / (714) 989-6135


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.
>
> Jim