Re: [datatracker-rqmts] New Requirement

"Jim Schaad" <ietf@augustcellars.com> Tue, 16 November 2010 03:42 UTC

Return-Path: <ietf@augustcellars.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 A11A63A6BD3 for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 19:42:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level:
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[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 vsdbR+qQXCPH for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 19:42:37 -0800 (PST)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by core3.amsl.com (Postfix) with ESMTP id 85E623A6A5B for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 19:42:34 -0800 (PST)
Received: from TITUS (173-8-216-38-Oregon.hfc.comcastbusiness.net [173.8.216.38]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTP id B79BB6A419; Mon, 15 Nov 2010 19:43:16 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Royer Software and Services'" <royersoftwareandservices@gmail.com>, <datatracker-rqmts@ietf.org>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com>
In-Reply-To: <4CE18751.7030002@gmail.com>
Date: Mon, 15 Nov 2010 19:53:13 -0800
Message-ID: <001f01cb8541$cbe593e0$63b0bba0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGmhsIGnND7rj+Y3kZx1QsKT7FjIQKCUTwEk6liTEA=
Content-Language: en-us
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: Tue, 16 Nov 2010 03:42:40 -0000

First, not all drafts that go to the ISE are actually reviewed by just the
IESB.  Many times we will solicit reviewers from the general community.  Now
let's say that <Your favorite evil person> writes a draft and requests the
ISE to publish this document.  We come to you and ask you to review the
document.  You might come back with three different responses:

1.  Sure
2.  Only if my name does not get back to <evil person>
3.  No way.

In cases 2 and 3 we might want to record this information in the data
tracker so that we know who was asked and when they were asked to do
reviews.  This might give me (as a member of the IESB) a clue as to who was
previously asked in the event that somebody does not deliver a review and I
am trying to come up with a replacement.  At present this type of data is so
private it only resides on the ISE's computer and is not available to the
IESB where it might be useful.

Jim


> -----Original Message-----
> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
> bounces@ietf.org] On Behalf Of Royer Software and Services
> Sent: Monday, November 15, 2010 11:18 AM
> To: datatracker-rqmts@ietf.org
> Subject: Re: [datatracker-rqmts] New Requirement
> 
> 
> 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
> _______________________________________________
> datatracker-rqmts mailing list
> datatracker-rqmts@ietf.org
> https://www.ietf.org/mailman/listinfo/datatracker-rqmts