
From paul.hoffman@vpnc.org  Mon Nov  1 15:28:08 2010
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 938DA28B56A for <datatracker-rqmts@core3.amsl.com>; Mon,  1 Nov 2010 15:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.313
X-Spam-Level: 
X-Spam-Status: No, score=-100.313 tagged_above=-999 required=5 tests=[AWL=-0.867, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, 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 O+LgQkjv570a for <datatracker-rqmts@core3.amsl.com>; Mon,  1 Nov 2010 15:28:07 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 1375F3A6A6B for <datatracker-rqmts@ietf.org>; Mon,  1 Nov 2010 15:28:04 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA1MS5hb025213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Mon, 1 Nov 2010 15:28:06 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624088ac8f4ef10b46d@[10.20.30.249]>
In-Reply-To: <p06240800c8ecfbb84168@[10.20.30.249]>
References: <p06240800c8ecfbb84168@[10.20.30.249]>
Date: Mon, 1 Nov 2010 15:28:03 -0700
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Slides for the face-to-face BoF next week
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, 01 Nov 2010 22:28:08 -0000

Greetings again. I have uploaded the proposed slides for the BoF to the IETF site; see <http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.

Of course, it would be swell if people wanted to talk about any of the topics in the draft or proposed in the slides before the meeting. :-)

--Paul Hoffman, Director
--VPN Consortium

From sm@resistor.net  Tue Nov  2 08:15:25 2010
Return-Path: <sm@resistor.net>
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 4A47828C12C for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 08:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Ny9rOuEs4V+T for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 08:15:22 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 14BD228C12A for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 08:15:22 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id oA2FEwVD007769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 08:15:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1288710925; x=1288797325; bh=7kluat5cOhVG3ZXS5F87kNVdFFROTEdORXDupZonzeE=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=umyhhDzjJe3vInK97xa61Cks1qi9Eo9w07/8aCgQ8EtK+gw0JL6mKxXdFH1C1oBvn 2QNiS6VW9X5PkVvP1X8QsJ1XVy0xaPfqXhkEFVuwQYvYbzQFctOyLkV5cyRAeJiUEF hh8JCfWT4BKGJLOYvyDCQbUzA4oX4Z6WZDeazOZY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1288710925; x=1288797325; bh=7kluat5cOhVG3ZXS5F87kNVdFFROTEdORXDupZonzeE=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=SobrHhEeM1/eHBRja+nTZodegbtgCDvGCq6fUJIQWqXf6TKKna26NxfwUaokkdjmK qrcNBAlpyEIcmxMoamLNHIC03gjhK7b1T5w6UGXFhcXgdAG2ADEZ42MC9fB/OMxd6n VzyfaPUzim2fXEWG5fgHj4IWFDKMypgnrcmIJ66w=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=W3UMopU0pjZZhCQ5xidnGUCJainsQ83gYOl5AQrwe5/pemMv8bzd5Jz+XrEIRi1uq GZ8UQ3ILNt2C2VwC+CNdvYctROdNBS53bmnrT+aP5MNYIwX97qDfXLOcbkr8ZiJ7COI Db5oyjq78gwhghYkm8ek+6FTMNZv7OkbUD/BuJg=
Message-Id: <6.2.5.6.2.20101102074555.099f1830@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 02 Nov 2010 08:04:13 -0700
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: SM <sm@resistor.net>
In-Reply-To: <p0624088ac8f4ef10b46d@[10.20.30.249]>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 15:15:25 -0000

Hi Paul,
At 15:28 01-11-10, Paul Hoffman wrote:
>Greetings again. I have uploaded the proposed slides for the BoF to 
>the IETF site; see <http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.

On Page 12:

  "Lots of reasons why someone would not
   someone else to know which drafts they are
   following"

Did you forget a word in there?

That page is about "Lists should be able to be private".  Do you 
really want to get into a discussion about privacy?  As the work of 
the IETF is supposed to be open, I suggest letting anyone who is 
"subscribed" to a draft see who else is following it.  Otherwise, 
you'll have to define who should have access to the information.

Regards,
-sm



From paul.hoffman@vpnc.org  Tue Nov  2 08:48:52 2010
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 074703A69DA for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 08:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.983
X-Spam-Level: 
X-Spam-Status: No, score=-99.983 tagged_above=-999 required=5 tests=[AWL=-0.764, 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 1V0GfBm-Isik for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 08:48:51 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id D686D3A69D7 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 08:48:50 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2Fmq71080396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 08:48:54 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240894c8f5dde043db@[10.20.30.150]>
In-Reply-To: <6.2.5.6.2.20101102074555.099f1830@resistor.net>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net>
Date: Tue, 2 Nov 2010 08:36:32 -0700
To: SM <sm@resistor.net>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 15:48:52 -0000

At 8:04 AM -0700 11/2/10, SM wrote:
>Hi Paul,
>At 15:28 01-11-10, Paul Hoffman wrote:
>>Greetings again. I have uploaded the proposed slides for the BoF to the IETF site; see <http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.
>
>On Page 12:
>
> "Lots of reasons why someone would not
>  someone else to know which drafts they are
>  following"
>
>Did you forget a word in there?

Yes; "want". Will fix.

>That page is about "Lists should be able to be private".  Do you really want to get into a discussion about privacy?  As the work of the IETF is supposed to be open, I suggest letting anyone who is "subscribed" to a draft see who else is following it.

That seems a tad radical to me. How do others feel about this?

When you say "who else", do you mean "which other lists include this draft" or "which people who created a list which includes this draft"?

>  Otherwise, you'll have to define who should have access to the information.

Correct: there was an implicit definition (that I can make explicit) of "the person who created the list, whomever that person gives access to, and no one else".

--Paul Hoffman, Director
--VPN Consortium

From fred@cisco.com  Tue Nov  2 09:15:20 2010
Return-Path: <fred@cisco.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 CD0A43A68DB for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.372
X-Spam-Level: 
X-Spam-Status: No, score=-110.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 faBScO+FKzdI for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:15:20 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 099823A6883 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 09:15:20 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFvWz0yrR7Hu/2dsb2JhbAChVnGkW5wNhUUEhFeFfoMI
X-IronPort-AV: E=Sophos;i="4.58,283,1286150400"; d="scan'208";a="376706249"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 02 Nov 2010 16:15:10 +0000
Received: from Freds-Computer.local ([10.21.71.186]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id oA2GF8ro011491; Tue, 2 Nov 2010 16:15:10 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Tue, 02 Nov 2010 09:15:10 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Tue, 02 Nov 2010 09:15:10 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <p0624088ac8f4ef10b46d@[10.20.30.249]>
Date: Tue, 2 Nov 2010 09:15:00 -0700
Message-Id: <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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, 02 Nov 2010 16:15:20 -0000

On Nov 1, 2010, at 3:28 PM, Paul Hoffman wrote:

> Greetings again. I have uploaded the proposed slides for the BoF to =
the IETF site; see =
<http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.
>=20
> Of course, it would be swell if people wanted to talk about any of the =
topics in the draft or proposed in the slides before the meeting. :-)


Thanks for pointing out the slides.

One of the slides wonders what the rule is for identifying drafts =
associated with a working group. As I'm sure you know, there has been a =
convention for a long time in naming: draft-ietf-<wg>-*-nn.txt is a =
working group draft, and draft-<author>-<wg>-*-nn.txt is an individual =
submission to a working group. draft monikers that mention no working =
group are general submissions going nowhere in particular. I'm pretty =
sure that Henrik's existing tool looks for "draft-ietf-<wg>" and =
"anything containing <wg>" for the two areas.

I like the convention; I find it useful. I do go a little crazy with the =
set of people that don't choose to use it, though; I get people posting =
drafts and then wanting to discuss them for several meetings in my WG =
but not follow the convention, which means that I have to manually track =
things. Since a "convention" is not a "rule" (eg, I don't care to be a =
hard-ass about it), I put in the extra work, but there is a part of me =
that would like the tool to be able to remember for me in some sense. =
"documents that follow the convention plus those I add".


Something else the slides note - there could be some pain in various =
forms regarding personal lists. There might be; I'm not sure why anyone =
would want to know what drafts I was tracking (it's not like we have =
drafts about specialized delivery of pornography or etc), but I could =
imagine someone trying to do corporate intelligence by tracking who is =
tracking what drafts. A simple solution would be to keep our private =
lists on our private computers. That might, for example, be a reasonable =
use of a cookie or some kind of local preferences file. If we're keeping =
the list on the machine, I would think that per-user lists would not be =
used in daily processing; they would be compiled into a set of rules of =
the form "if a draft whose name matches /<regex>/ changes, notify =
{list}". Individual draft names are an obvious special case, as are =
/draft-*-<wg>-*.txt/.



From henrik@levkowetz.com  Tue Nov  2 09:26:04 2010
Return-Path: <henrik@levkowetz.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 A94EC3A69D7 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.373
X-Spam-Level: 
X-Spam-Status: No, score=-102.373 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 F9Ke9nNcDPXf for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:26:03 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id A46173A6874 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 09:26:03 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:54082 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PDJdy-0002OX-Dj; Tue, 02 Nov 2010 17:24:45 +0100
Message-ID: <4CD03AFC.7040001@levkowetz.com>
Date: Tue, 02 Nov 2010 17:23:24 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <p06240800c8ecfbb84168@[10.20.30.249]>	<p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net>
In-Reply-To: <6.2.5.6.2.20101102074555.099f1830@resistor.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: sm@resistor.net, paul.hoffman@vpnc.org, datatracker-rqmts@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: datatracker-rqmts@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 16:26:04 -0000

Hi,

On 2010-11-02 16:04 SM said:
> Hi Paul,
> At 15:28 01-11-10, Paul Hoffman wrote:
>> Greetings again. I have uploaded the proposed slides for the BoF to 
>> the IETF site; see <http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.
> 
> On Page 12:
> 
>   "Lots of reasons why someone would not
>    someone else to know which drafts they are
>    following"
> 
> Did you forget a word in there?
> 
> That page is about "Lists should be able to be private".  Do you 
> really want to get into a discussion about privacy?  As the work of 
> the IETF is supposed to be open, I suggest letting anyone who is 
> "subscribed" to a draft see who else is following it.  Otherwise, 
> you'll have to define who should have access to the information.

No, I think that's turned around.  I think it's as wrong to assume that
personal configuration information is public by default.  With the
possibility to create personal configuration information which resides
on the server (something we haven't really had a lot of on the IETF
servers up till now) the assumption should be that that individual
configuration information is private unless the person chooses to make
it public.

This following isn't an exact parallel, but with email, we have a
situation where list email is public, and the whole purpose of list
emails are to reach people publicly; while emails sent to individual
persons outside of a list are not (and should not be) automatically
assumed to be public.  Thus information is only automatically public
when it's explicitly intended to be so.

When you bookmark web pages in your web browser the information is
private, unless you explicitly publish the information.  When you
subscribe to a feed, that information resides in your feed reader
(or in the Google Reader) and it's not public unless you make it
so.

With the possibility to individually configure services provided by
the IETF servers, we should (I think) respect that people don't
necessarily want others to know what they configure.  If they want
people to know, they are free to make the information public, but
we shouldn't force the information to be public.  That would most
likely make these services less valuable than they could be to a lot
of people, and that seems less than optimal to me.


	Henrik

From housley@vigilsec.com  Tue Nov  2 09:35:54 2010
Return-Path: <housley@vigilsec.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 317B43A679C for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, 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 yu+elIzCSGcd for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:35:53 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 71DF53A69C2 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 09:35:53 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 59BF9F24013; Tue,  2 Nov 2010 12:36:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id MnuC83KzWaZ7; Tue,  2 Nov 2010 12:35:54 -0400 (EDT)
Received: from mail.smetech.net (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 5C0509A472E; Tue,  2 Nov 2010 12:36:09 -0400 (EDT)
Received: from 198.180.150.230 (SquirrelMail authenticated user housley@vigilsec.com) by mail.smetech.net with HTTP; Tue, 2 Nov 2010 12:36:09 -0400 (EDT)
Message-ID: <1515.198.180.150.230.1288715769.squirrel@mail.smetech.net>
In-Reply-To: <p0624088ac8f4ef10b46d@[10.20.30.249]>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]>
Date: Tue, 2 Nov 2010 12:36:09 -0400 (EDT)
From: "Russ Housley" <housley@vigilsec.com>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
User-Agent: SquirrelMail/1.4.8-5.el4_8.8
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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, 02 Nov 2010 16:35:54 -0000

> Greetings again. I have uploaded the proposed slides for the BoF to the
> IETF site; see <http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.
>
> Of course, it would be swell if people wanted to talk about any of the
> topics in the draft or proposed in the slides before the meeting. :-)

What legal issues do you see if an account-based system is used?  The
community already uses wikis that require an account.  How is this
different?

Russ


From royersoftwareandservices@gmail.com  Tue Nov  2 09:45:06 2010
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 D51293A69F5 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:45:04 -0700 (PDT)
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 JWRe4tCEYGtr for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:45:03 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id D468A3A69F0 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 09:45:02 -0700 (PDT)
Received: by gya6 with SMTP id 6so4576474gya.31 for <datatracker-rqmts@ietf.org>; Tue, 02 Nov 2010 09:45:07 -0700 (PDT)
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=U90HQ1A4ay0aU6xMpWz6BqIwX8IbI5QtGotPBLESmVg=; b=wbB9V19vR3b7+aewqFqsz8fZHoFy8NOkX5axcuZxKl5iER4Fx6EyatNePhDWDmri2y ZbuZmfweaD/5VbXTLwVbIOHSblGGqbHPx5FDnSVUKz6hERKlbKV0Rv0mLS8H+2tia5Th ua3dUj5GLia4ZsbDp/F+6FTSLvo/DEPmPIfrs=
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=YBUy4TNK88Op6MqezBKkABAt1bpjzyZqnzuXDuC0Beb4vIeP8KRindBwETSlaeNqlD QWglXKu7JaaHoLwQLqUIj8JFZIfoq87BZ/SzLs9DEHiaGgMSXl5PbaIy+mY5FZ+LQ3kV vAsrX5QtLCRwwJvGIeUqHhGkyzrVuhErxwYWY=
Received: by 10.100.111.10 with SMTP id j10mr1020215anc.222.1288716307074; Tue, 02 Nov 2010 09:45:07 -0700 (PDT)
Received: from [192.168.0.58] ([63.227.129.161]) by mx.google.com with ESMTPS id g18sm4221485anh.18.2010.11.02.09.45.05 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Nov 2010 09:45:06 -0700 (PDT)
Message-ID: <4CD04005.90800@gmail.com>
Date: Tue, 02 Nov 2010 10:44:53 -0600
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: <p06240800c8ecfbb84168@[10.20.30.249]>	<p0624088ac8f4ef10b46d@[10.20.30.249]>	<6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]>
In-Reply-To: <p06240894c8f5dde043db@[10.20.30.150]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 16:45:06 -0000

On 11/2/2010 9:36 AM, Paul Hoffman wrote:
> At 8:04 AM -0700 11/2/10, SM wrote:
> That page is about "Lists should be able to be private".  Do you really want to get into a discussion about privacy?  As the work of the IETF is supposed to be open, I suggest letting anyone who is "subscribed" to a draft see who else is following it.
> That seems a tad radical to me. How do others feel about this?

Who cares who watches?  And who cares who watches the watchers?

I have seen well meaning people have meetings and make agreements about 
drafts, then forget and
just assume that the idea was part of the consensus on the list.

I would opt for everything as open as possible. The less secrets the 
IETF has the healthier it will remain
as there will be no dark corners that other can assume contain hidden 
agreements or ideas.

--
Doug - Royer Software and Services

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



From royersoftwareandservices@gmail.com  Tue Nov  2 09:57:38 2010
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 BBF263A69DE for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:57:38 -0700 (PDT)
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 tXGFXI0PU7qC for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 09:57:37 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id ADF8A3A69EC for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 09:57:37 -0700 (PDT)
Received: by ywp6 with SMTP id 6so4612271ywp.31 for <datatracker-rqmts@ietf.org>; Tue, 02 Nov 2010 09:57:42 -0700 (PDT)
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=6XP07SiaUhvpcblBAPLsXbV6Se49upfzbD3FYTA0uqI=; b=UIpDKtDHH5349LS3Yi6I0bxw8WxAzmH8pjdxDHje1kCddKdVwXmfrkhmRdr5/19iMJ 0ERdx0MKsOXqyp7arve4J1zoZKRRGOnaCXYPD3IUSR9hpNRy5JA82n+6UTQ8GVBNJb3J K8G5Y/jjHZAoGxFzqfMsMdOSjIiN0XpQrqybk=
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=sXqJ5fiupbkQJFN1cz+iOJOmus/KpR/MGnga+JS9t0mPkDaho82Ns4ZgekGZRaRarO rnBdJYKL1t/L0h0f/yVqwH+XRm9tE9llYWeJvAfd7xS1dwGbm0SL0Khka9bbP5ILeVGU oQ+7trn0IwMSCTDbIjuK/642FVgjSnCfzeGPA=
Received: by 10.100.239.20 with SMTP id m20mr1024814anh.53.1288717061909; Tue, 02 Nov 2010 09:57:41 -0700 (PDT)
Received: from [192.168.0.58] ([63.227.129.161]) by mx.google.com with ESMTPS id 25sm4233014anq.8.2010.11.02.09.57.38 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Nov 2010 09:57:39 -0700 (PDT)
Message-ID: <4CD042F6.9020302@gmail.com>
Date: Tue, 02 Nov 2010 10:57:26 -0600
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: <p06240800c8ecfbb84168@[10.20.30.249]>	<p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net>
In-Reply-To: <6.2.5.6.2.20101102074555.099f1830@resistor.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 16:57:38 -0000

(1) On page 13 it says:

– If someone forgets their list name, they can just create a new one


How about monthly (or whatever) reminder emails? Like the other lists have.

(2) Maybe I missed it. Should the list creator be able to disable/delete 
the list?

--

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



From paul.hoffman@vpnc.org  Tue Nov  2 10:01:07 2010
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 5571D28C127 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.943
X-Spam-Level: 
X-Spam-Status: No, score=-99.943 tagged_above=-999 required=5 tests=[AWL=-0.497, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, 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 8ye2pGcc9cq4 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:01:06 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 8C69F3A67FD for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:01:06 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2H18bM084791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:01:10 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624089ac8f5f383565e@[10.20.30.150]>
In-Reply-To: <1515.198.180.150.230.1288715769.squirrel@mail.smetech.net>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <1515.198.180.150.230.1288715769.squirrel@mail.smetech.net>
Date: Tue, 2 Nov 2010 10:01:05 -0700
To: "Russ Housley" <housley@vigilsec.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: [datatracker-rqmts] Legal issues
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, 02 Nov 2010 17:01:07 -0000

At 12:36 PM -0400 11/2/10, Russ Housley wrote:
> > Greetings again. I have uploaded the proposed slides for the BoF to the
>> IETF site; see <http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.
>>
>> Of course, it would be swell if people wanted to talk about any of the
>> topics in the draft or proposed in the slides before the meeting. :-)
>
>What legal issues do you see if an account-based system is used?  The
>community already uses wikis that require an account.  How is this
>different?

It is not clear that it is different, but it might be. I don't know of any private information that can be kept on the IETF wikis, but we are talking here about private lists (unless folks agree with SM). If there is private information on the IETF wikis, has anyone asked "the IETF lawyers" about it?

--Paul Hoffman, Director
--VPN Consortium

From paul.hoffman@vpnc.org  Tue Nov  2 10:04:06 2010
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 F14313A69EC for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.747
X-Spam-Level: 
X-Spam-Status: No, score=-99.747 tagged_above=-999 required=5 tests=[AWL=-0.528, 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 jGSLHuPuHHLq for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:04:05 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 49CA43A69DE for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:04:05 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2H47Rc084965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:04:08 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624089bc8f5f4748ec1@[10.20.30.150]>
In-Reply-To: <4CD04005.90800@gmail.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <4CD04005.90800@gmail.com>
Date: Tue, 2 Nov 2010 10:04:06 -0700
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] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 17:04:06 -0000

At 10:44 AM -0600 11/2/10, Royer Software and Services wrote:
>On 11/2/2010 9:36 AM, Paul Hoffman wrote:
>>At 8:04 AM -0700 11/2/10, SM wrote:
>>That page is about "Lists should be able to be private".  Do you really want to get into a discussion about privacy?  As the work of the IETF is supposed to be open, I suggest letting anyone who is "subscribed" to a draft see who else is following it.
>>That seems a tad radical to me. How do others feel about this?
>
>Who cares who watches?  And who cares who watches the watchers?
>
>I have seen well meaning people have meetings and make agreements about drafts, then forget and
>just assume that the idea was part of the consensus on the list.

This as nothing to do with the content of drafts; it is about watching which drafts change over time.

>I would opt for everything as open as possible. The less secrets the IETF has the healthier it will remain
>as there will be no dark corners that other can assume contain hidden agreements or ideas.

I'm deeply confused here. As described in the draft, a list is a personal preference of what to see. There is no "agreement" or "idea" involved. Which part of the draft are you talking about?

--Paul Hoffman, Director
--VPN Consortium

From paul.hoffman@vpnc.org  Tue Nov  2 10:11:03 2010
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 056153A659B for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.972
X-Spam-Level: 
X-Spam-Status: No, score=-100.972 tagged_above=-999 required=5 tests=[AWL=0.847, BAYES_00=-2.599, 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 KxovagzPB3EZ for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:10:59 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 72A6A3A69EF for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:10:55 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2HAwHN085508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:11:00 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624089cc8f5f637f893@[10.20.30.150]>
In-Reply-To: <4CD03AFC.7040001@levkowetz.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <4CD03AFC.7040001@levkowetz.com>
Date: Tue, 2 Nov 2010 10:10:57 -0700
To: Henrik Levkowetz <henrik@levkowetz.com>, SM <sm@resistor.net>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 17:11:03 -0000

At 5:23 PM +0100 11/2/10, Henrik Levkowetz wrote:
>Hi,
>
>On 2010-11-02 16:04 SM said:
>> Hi Paul,
>> At 15:28 01-11-10, Paul Hoffman wrote:
>>> Greetings again. I have uploaded the proposed slides for the BoF to
>>> the IETF site; see <http://www.ietf.org/proceedings/79/slides/iddtspec-0.pdf>.
>>
>> On Page 12:
>>
>>   "Lots of reasons why someone would not
>>    someone else to know which drafts they are
>>    following"
>>
>> Did you forget a word in there?
>>
>> That page is about "Lists should be able to be private".  Do you
>> really want to get into a discussion about privacy?  As the work of
>> the IETF is supposed to be open, I suggest letting anyone who is
>> "subscribed" to a draft see who else is following it.  Otherwise,
>> you'll have to define who should have access to the information.
>
>No, I think that's turned around.  I think it's as wrong to assume that
>personal configuration information is public by default.  With the
>possibility to create personal configuration information which resides
>on the server (something we haven't really had a lot of on the IETF
>servers up till now) the assumption should be that that individual
>configuration information is private unless the person chooses to make
>it public.
>
>This following isn't an exact parallel, but with email, we have a
>situation where list email is public, and the whole purpose of list
>emails are to reach people publicly; while emails sent to individual
>persons outside of a list are not (and should not be) automatically
>assumed to be public.  Thus information is only automatically public
>when it's explicitly intended to be so.
>
>When you bookmark web pages in your web browser the information is
>private, unless you explicitly publish the information.  When you
>subscribe to a feed, that information resides in your feed reader
>(or in the Google Reader) and it's not public unless you make it
>so.
>
>With the possibility to individually configure services provided by
>the IETF servers, we should (I think) respect that people don't
>necessarily want others to know what they configure.  If they want
>people to know, they are free to make the information public, but
>we shouldn't force the information to be public.  That would most
>likely make these services less valuable than they could be to a lot
>of people, and that seems less than optimal to me.

My thinking in the early draft was that "making a list" was akin to "bookmarking a lot of drafts". That is, this is what many people do today anyhow, and the IETF can make this easier. Does the fact that it is the IETF making this easier cause the information to have to be exposed to everyone?

--Paul Hoffman, Director
--VPN Consortium

From paul.hoffman@vpnc.org  Tue Nov  2 10:14:23 2010
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 E44A828C126 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.447
X-Spam-Level: 
X-Spam-Status: No, score=-100.447 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_05=-1.11, HELO_MISMATCH_COM=0.553, 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 PvxUwvie5Pe5 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:14:23 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 3A2583A6885 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:14:23 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2HEP4t085722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:14:26 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624089dc8f5f6f7256e@[10.20.30.150]>
In-Reply-To: <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com>
Date: Tue, 2 Nov 2010 10:14:24 -0700
To: Fred Baker <fred@cisco.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: [datatracker-rqmts] What are WG drafts?
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, 02 Nov 2010 17:14:24 -0000

At 9:15 AM -0700 11/2/10, Fred Baker wrote:
>One of the slides wonders what the rule is for identifying drafts associated with a working group. As I'm sure you know, there has been a convention for a long time in naming: draft-ietf-<wg>-*-nn.txt is a working group draft, and draft-<author>-<wg>-*-nn.txt is an individual submission to a working group. draft monikers that mention no working group are general submissions going nowhere in particular. I'm pretty sure that Henrik's existing tool looks for "draft-ietf-<wg>" and "anything containing <wg>" for the two areas.
>
>I like the convention; I find it useful. I do go a little crazy with the set of people that don't choose to use it, though; I get people posting drafts and then wanting to discuss them for several meetings in my WG but not follow the convention, which means that I have to manually track things. Since a "convention" is not a "rule" (eg, I don't care to be a hard-ass about it), I put in the extra work, but there is a part of me that would like the tool to be able to remember for me in some sense. "documents that follow the convention plus those I add".

Henrik: I believe that some actual WG drafts do not follow the draft-ietf-wgname rule. Is that true? If so, how does the Datatracker know to show them in the WG charter page? Is that done by hand?

--Paul Hoffman, Director
--VPN Consortium

From royersoftwareandservices@gmail.com  Tue Nov  2 10:16:35 2010
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 D6AD328C105 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.726
X-Spam-Level: 
X-Spam-Status: No, score=-1.726 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 4iciSA480pyN for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:16:34 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 535563A69ED for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:16:34 -0700 (PDT)
Received: by gwb15 with SMTP id 15so4634022gwb.31 for <datatracker-rqmts@ietf.org>; Tue, 02 Nov 2010 10:16:38 -0700 (PDT)
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:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=KA6Scz3gDgzkYFTrXfGGu4Qse+2feT7LfER4xb41dqI=; b=OGS7YnsD/+mAlmWhZdG32gwPVNYB/zm8reKenPcvea1jOYbXs9w9BzP8uxZkj6XAql DaPTj+erNd1JHW7OS1TEllqX1oxflj2orN1uMrBNz8W14J7Tze3mnWkMxaCS4o8Oe+w4 TZIaLLYn0KVhO6vQpkKH5BAB3fXM+Lw9ZcyyM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=cl8LLUqpxHgEGJqNebF+IERLJRJO8auq2a1Ke9eG4Skijn/Sb5NXhW6beyc+lMNVxP CYR+7dzH7R00Uj6KH5BacTKZvPTyRX4HXGTwqUe22SJxLZ55bw32K5wX0Y5NOs1evtB7 ZYuUNxpiHGPP3e5VZRUUL2uLJD2A2ToraUkEY=
Received: by 10.100.96.5 with SMTP id t5mr1055624anb.258.1288718198514; Tue, 02 Nov 2010 10:16:38 -0700 (PDT)
Received: from [192.168.0.58] ([63.227.129.161]) by mx.google.com with ESMTPS id t23sm4247599ano.27.2010.11.02.10.16.36 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Nov 2010 10:16:37 -0700 (PDT)
Message-ID: <4CD04769.6090203@gmail.com>
Date: Tue, 02 Nov 2010 11:16:25 -0600
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
CC: datatracker-rqmts@ietf.org
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <4CD04005.90800@gmail.com> <p0624089bc8f5f4748ec1@[10.20.30.150]>
In-Reply-To: <p0624089bc8f5f4748ec1@[10.20.30.150]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 17:16:35 -0000

On 11/2/2010 11:04 AM, Paul Hoffman wrote:
> I'm deeply confused here. As described in the draft, a list is a personal preference of what to see. There is no "agreement" or "idea" involved. Which part of the draft are you talking about?
I thought this thread was about the PDF file, not a draft submitted.

I read that PDF file section as is who is watching the drafts. I did not 
understand it to mean personal preferences.
--

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



From paul.hoffman@vpnc.org  Tue Nov  2 10:18:24 2010
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 0881128C132 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.274
X-Spam-Level: 
X-Spam-Status: No, score=-100.274 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, 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 TV2fDqYOQxoN for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:18:23 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 5B1CB28C131 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:18:23 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2HIPPD085972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:18:27 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624089ec8f5f7774360@[10.20.30.150]>
In-Reply-To: <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com>
Date: Tue, 2 Nov 2010 10:18:24 -0700
To: Fred Baker <fred@cisco.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: [datatracker-rqmts] Lists not kept by the Datatracker
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, 02 Nov 2010 17:18:24 -0000

At 9:15 AM -0700 11/2/10, Fred Baker wrote:
>Something else the slides note - there could be some pain in various forms regarding personal lists. There might be; I'm not sure why anyone would want to know what drafts I was tracking (it's not like we have drafts about specialized delivery of pornography or etc), but I could imagine someone trying to do corporate intelligence by tracking who is tracking what drafts. A simple solution would be to keep our private lists on our private computers. That might, for example, be a reasonable use of a cookie or some kind of local preferences file. If we're keeping the list on the machine, I would think that per-user lists would not be used in daily processing; they would be compiled into a set of rules of the form "if a draft whose name matches /<regex>/ changes, notify {list}". Individual draft names are an obvious special case, as are /draft-*-<wg>-*.txt/.

This is definitely a possibility for the tool. If people don't want to use the tool's list-making (such as if SM and Doug's proposal is accepted and someone has the concern you give above), the tool could have a mode of "give me your list and your preferences in an HTTP request and I'll give you a display like the one I would have done if you kept the list with me". I don't know how we could handle making an Atom feed or mail stream for those folks.

--Paul Hoffman, Director
--VPN Consortium

From paul.hoffman@vpnc.org  Tue Nov  2 10:20:45 2010
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 3DB423A69ED for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.781
X-Spam-Level: 
X-Spam-Status: No, score=-99.781 tagged_above=-999 required=5 tests=[AWL=-0.562, 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 SZalvJvkEIVQ for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:20:44 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 9A4D93A69B6 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:20:44 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2HKkwb086076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:20:47 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624089fc8f5f8e398a5@[10.20.30.150]>
In-Reply-To: <4CD042F6.9020302@gmail.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <4CD042F6.9020302@gmail.com>
Date: Tue, 2 Nov 2010 10:20:45 -0700
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] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 17:20:45 -0000

At 10:57 AM -0600 11/2/10, Royer Software and Services wrote:
>(1) On page 13 it says:
>
>- If someone forgets their list name, they can just create a new one
>
>
>How about monthly (or whatever) reminder emails? Like the other lists have.
>
>(2) Maybe I missed it. Should the list creator be able to disable/delete the list?

Both good points. Added.

--Paul Hoffman, Director
--VPN Consortium

From paul.hoffman@vpnc.org  Tue Nov  2 10:24:44 2010
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 793FA28C0D7 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.73
X-Spam-Level: 
X-Spam-Status: No, score=-99.73 tagged_above=-999 required=5 tests=[AWL=-0.511, 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 n6mq3G7L3BRQ for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:24:43 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id AF97F28C0D9 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:24:43 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2HOidb086271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:24:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p062408a1c8f5f99fc4c6@[10.20.30.150]>
In-Reply-To: <4CD04769.6090203@gmail.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <4CD04005.90800@gmail.com> <p0624089bc8f5f4748ec1@[10.20.30.150]> <4CD04769.6090203@gmail.com>
Date: Tue, 2 Nov 2010 10:24:43 -0700
To: Royer Software and Services <royersoftwareandservices@gmail.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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, 02 Nov 2010 17:24:44 -0000

At 11:16 AM -0600 11/2/10, Royer Software and Services wrote:
>On 11/2/2010 11:04 AM, Paul Hoffman wrote:
>>I'm deeply confused here. As described in the draft, a list is a personal preference of what to see. There is no "agreement" or "idea" involved. Which part of the draft are you talking about?
>I thought this thread was about the PDF file, not a draft submitted.
>
>I read that PDF file section as is who is watching the drafts. I did not understand it to mean personal preferences.

The slides refer to the Internet Draft that is the topic of this BoF listed on slide 2: draft-ietf-genarea-datatracker-community-01.

--Paul Hoffman, Director
--VPN Consortium

From fred@cisco.com  Tue Nov  2 10:28:12 2010
Return-Path: <fred@cisco.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 3E48728C130 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.542
X-Spam-Level: 
X-Spam-Status: No, score=-110.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 Dty-a1-tthP6 for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 10:28:09 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id CC6AA3A69F5 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 10:28:08 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMLmz0yrR7Hu/2dsb2JhbAChWHGkRpwJhUUEhFeFfoMI
X-IronPort-AV: E=Sophos;i="4.58,283,1286150400"; d="scan'208";a="376726914"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 02 Nov 2010 17:28:13 +0000
Received: from Freds-Computer.local (sjc-vpn2-880.cisco.com [10.21.115.112]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id oA2HSBPP000928; Tue, 2 Nov 2010 17:28:13 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Tue, 02 Nov 2010 10:28:13 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Tue, 02 Nov 2010 10:28:13 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <p0624089dc8f5f6f7256e@[10.20.30.150]>
Date: Tue, 2 Nov 2010 10:28:04 -0700
Message-Id: <01391DC2-A8FF-4321-A4D8-6FC9EA8578E9@cisco.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com> <p0624089dc8f5f6f7256e@[10.20.30.150]>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] What are WG drafts?
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, 02 Nov 2010 17:28:12 -0000

On Nov 2, 2010, at 10:14 AM, Paul Hoffman wrote:

> At 9:15 AM -0700 11/2/10, Fred Baker wrote:
>> One of the slides wonders what the rule is for identifying drafts =
associated with a working group. As I'm sure you know, there has been a =
convention for a long time in naming: draft-ietf-<wg>-*-nn.txt is a =
working group draft, and draft-<author>-<wg>-*-nn.txt is an individual =
submission to a working group. draft monikers that mention no working =
group are general submissions going nowhere in particular. I'm pretty =
sure that Henrik's existing tool looks for "draft-ietf-<wg>" and =
"anything containing <wg>" for the two areas.
>>=20
>> I like the convention; I find it useful. I do go a little crazy with =
the set of people that don't choose to use it, though; I get people =
posting drafts and then wanting to discuss them for several meetings in =
my WG but not follow the convention, which means that I have to manually =
track things. Since a "convention" is not a "rule" (eg, I don't care to =
be a hard-ass about it), I put in the extra work, but there is a part of =
me that would like the tool to be able to remember for me in some sense. =
"documents that follow the convention plus those I add".
>=20
> Henrik: I believe that some actual WG drafts do not follow the =
draft-ietf-wgname rule. Is that true? If so, how does the Datatracker =
know to show them in the WG charter page? Is that done by hand?

Drafts that the secretariat understands to be working group drafts =
follow the convention. To test that assertion, pick a working group and =
try filing a draft named draft-ietf-<wg>-*.txt. You will find the =
secretariat contacting the chair for permission to post it.

That doesn't stop chairs from treating individual submissions to the =
working group as if they were working group drafts. I suspect we all do =
that; I know I do for small projects that are within charter but have a =
relatively narrow interest group. Where it gets crazy is people who =
disregard the convention entirely, as the tools have no organizing =
handle. A part of me wants to tell them to get their act together.=

From sm@resistor.net  Tue Nov  2 11:58:52 2010
Return-Path: <sm@resistor.net>
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 71DCC3A6A0A for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 11:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 bYfj6UzB9b6j for <datatracker-rqmts@core3.amsl.com>; Tue,  2 Nov 2010 11:58:49 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id A32493A69D8 for <datatracker-rqmts@ietf.org>; Tue,  2 Nov 2010 11:58:48 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id oA2IwZ5F006324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 11:58:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1288724329; x=1288810729; bh=VaL9lLPIHCHOomk0k7N0LLHT6qiJR5rwpv3Om+/6I30=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=0ii+xcRh5yH/CgMvg07FVY8EQ7ySsephynBt9BYFYc+YvPZ0fP542mcrY5lUyaqP0 p3L+0vsj2BGPyZ6m3a7Gb6dsmEFpYnr2CTgqlZiGLbjHQngqi/74nhxADaScjMI0N1 sHPAIF49VzpNM318I7R7qhxKkR0ZVA0zOSoI8R8w=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1288724329; x=1288810729; bh=VaL9lLPIHCHOomk0k7N0LLHT6qiJR5rwpv3Om+/6I30=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=hiK48EF6GfQof4NXmhno/TF0K8pOS1JeDK+u0I62n8OWbkgswxsvdWRE4aGX39Wu1 gUd9a6JfMwwqeGJh/DwO6nBccmN8apkj5Mrlim9RlvBaQV0YckhnqUHUUefXU71Xpz C90Qq2fIYf4RzWJMRDC/a2FxosZeL3RjftXtGFDU=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=Hj6I3OVdB8C83kB0EXRfQiKZAaagofuh7OQDZqWpsI+kVkjzcAw8Tat6o/pAb3Jri OpeF6JP3zO5DvIvRsvNpuDp4uh+YERHi/pvc3F8k7aN7GzQ/7kuRQvcfTBACx8BjI6K bkOKcE4FVN3xOh5Az0+CWey2P2eWDPc8qaGjnFQ=
Message-Id: <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 02 Nov 2010 11:54:55 -0700
To: datatracker-rqmts@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <p06240894c8f5dde043db@[10.20.30.150]>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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, 02 Nov 2010 18:58:52 -0000

Hello,
At 08:36 02-11-10, Paul Hoffman wrote:
>When you say "who else", do you mean "which other lists include this 
>draft" or "which people who created a list which includes this draft"?

I meant who are the people who created a list which includes this draft.

>Correct: there was an implicit definition (that I can make explicit) 
>of "the person who created the list, whomever that person gives 
>access to, and no one else".

That sounds fine unless we go down the path where the "following" is 
used as a measure of whether there is interest in a proposal.

At 09:15 02-11-10, Fred Baker wrote:
>Something else the slides note - there could be some pain in various 
>forms regarding personal lists. There might be; I'm not sure why 
>anyone would want to know what drafts I was tracking (it's not like 
>we have drafts about specialized delivery of pornography or etc), 
>but I could imagine someone trying to do corporate intelligence by 
>tracking who is tracking what drafts. A simple solution would be to 
>keep our private lists on our private

Yes.

At 09:23 02-11-10, Henrik Levkowetz wrote:
>No, I think that's turned around.  I think it's as wrong to assume that
>personal configuration information is public by default.  With the
>possibility to create personal configuration information which resides
>on the server (something we haven't really had a lot of on the IETF
>servers up till now) the assumption should be that that individual
>configuration information is private unless the person chooses to make
>it public.

If the information is labeled as "personal configuration", it keeps 
out the privacy discussion.

>This following isn't an exact parallel, but with email, we have a
>situation where list email is public, and the whole purpose of list
>emails are to reach people publicly; while emails sent to individual
>persons outside of a list are not (and should not be) automatically
>assumed to be public.  Thus information is only automatically public
>when it's explicitly intended to be so.

I, probably incorrectly, drew a parallel between the current mailing 
lists setup and this feature.

>With the possibility to individually configure services provided by
>the IETF servers, we should (I think) respect that people don't
>necessarily want others to know what they configure.  If they want

Agreed.

At 10:18 02-11-10, Paul Hoffman wrote:
>This is definitely a possibility for the tool. If people don't want 
>to use the tool's list-making (such as if SM and Doug's proposal is 
>accepted and someone has the concern you give above), the tool could 
>have a mode of "give me your list and your preferences in an HTTP 
>request and I'll give you a display like the one I would have done 
>if you kept the list with me". I don't know how we could handle 
>making an Atom feed or mail stream for those folks.

You could remind people that this tool is about letting "people keep 
track of changes in Internet Drafts".  Shared (public) lists could 
then be about tagging drafts by field of interest, e.g WG, drafts on 
v6 transition, etc. and sharing the list for reasons stated on Page 14.

Regards,
-sm 


From yaronf.ietf@gmail.com  Wed Nov  3 00:28:48 2010
Return-Path: <yaronf.ietf@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 BB78A3A6A6A for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 00:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.952
X-Spam-Level: 
X-Spam-Status: No, score=-101.952 tagged_above=-999 required=5 tests=[AWL=0.420, BAYES_00=-2.599, 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 cdDoaiZ9yCRK for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 00:28:47 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 730A93A6A79 for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 00:28:47 -0700 (PDT)
Received: by wyb28 with SMTP id 28so304164wyb.31 for <datatracker-rqmts@ietf.org>; Wed, 03 Nov 2010 00:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=t2GPZPbPwrwpQri7jPUw3P+KtESbLBgY958mfHfw2hc=; b=A5pgDB82Ymi+Ojd2bpoA81nLGKHsFSZyz0QK6fJhoHPI9vyoyYHC0F5DqmpI/f85tM wRmCIu77g2fSWSUHDE17JGjOBcs1LdeIUGKgxvWtTx5L2ufW53btVVeYMgTXB4jZRG5P MdrXn5fKzQwM9y7udVC1bTP/9+ZcXa+4VLVD8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=PCnu9gBefk2srXeHcvrXMUF0se3fFd036c6llzc6PoU6F2BkZaVkLRoozcICZh4MfA 8LTgk61Rl/zoXjAtmj1Xs4VTFucmEVW3rUMUNTIZB2cnOsRo3afYwajIouGxykbAw1CN OPEz2cXecszrREnkYcAqjOmgQOdvgoyezM6Zw=
Received: by 10.227.152.21 with SMTP id e21mr17694145wbw.188.1288769333172; Wed, 03 Nov 2010 00:28:53 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-181-26-165.red.bezeqint.net [79.181.26.165]) by mx.google.com with ESMTPS id i19sm7139727wbe.17.2010.11.03.00.28.50 (version=SSLv3 cipher=RC4-MD5); Wed, 03 Nov 2010 00:28:51 -0700 (PDT)
Message-ID: <4CD10F30.1050705@gmail.com>
Date: Wed, 03 Nov 2010 09:28:48 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; 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: <p06240800c8ecfbb84168@[10.20.30.249]>	<p0624088ac8f4ef10b46d@[10.20.30.249]>	<6.2.5.6.2.20101102074555.099f1830@resistor.net>	<p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net>
In-Reply-To: <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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: Wed, 03 Nov 2010 07:28:48 -0000

Reiterating and possibly clarifying what others have said in the past:

I think about 80% of this project is a waste of IETF resources.

I suggest that we concentrate ONLY on providing very granular Atom feeds 
for draft status changes, Then, we can leave everything else (graphic 
presentation, update periods, privacy, sharing) to the users. People can 
use desktop RSS readers, or the easier but more limited Web-based 
alternatives, e.g. Google Reader.

With the proposal on the table, what we're getting ourselves into is yet 
another enterprise-level Web application, with all that that involves. 
Yes, even Web application security.

Thanks,
	Yaron

From henrik@levkowetz.com  Wed Nov  3 03:27:01 2010
Return-Path: <henrik@levkowetz.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 C10473A68F9 for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 03:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.373
X-Spam-Level: 
X-Spam-Status: No, score=-102.373 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 W5CCikHNxLie for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 03:27:01 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id C3C623A68C4 for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 03:27:00 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:55265 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PDaYA-00057d-32; Wed, 03 Nov 2010 11:26:41 +0100
Message-ID: <4CD138DD.4070701@levkowetz.com>
Date: Wed, 03 Nov 2010 11:26:37 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <4CD03AFC.7040001@levkowetz.com> <p0624089cc8f5f637f893@[10.20.30.150]>
In-Reply-To: <p0624089cc8f5f637f893@[10.20.30.150]>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: paul.hoffman@vpnc.org, sm@resistor.net, datatracker-rqmts@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next  week
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: Wed, 03 Nov 2010 10:27:01 -0000

On 2010-11-02 18:10 Paul Hoffman said:
> At 5:23 PM +0100 11/2/10, Henrik Levkowetz wrote:

...

>> With the possibility to individually configure services provided
>> by the IETF servers, we should (I think) respect that people don't 
>> necessarily want others to know what they configure.  If they want 
>> people to know, they are free to make the information public, but 
>> we shouldn't force the information to be public.  That would most 
>> likely make these services less valuable than they could be to a
>> lot of people, and that seems less than optimal to me.
> 
> My thinking in the early draft was that "making a list" was akin to
> "bookmarking a lot of drafts". That is, this is what many people do
> today anyhow, and the IETF can make this easier. Does the fact that
> it is the IETF making this easier cause the information to have to be
> exposed to everyone?

My thinking is that it does not -- we should not have to expose this
to everyone.  If that wasn't clear from my lengthier exposition...


	Henrik


From henrik@levkowetz.com  Wed Nov  3 03:30:08 2010
Return-Path: <henrik@levkowetz.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 D0B353A68C4 for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 03:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.373
X-Spam-Level: 
X-Spam-Status: No, score=-102.373 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 pvgUi86Y2WHe for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 03:30:08 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id DE2063A677D for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 03:30:07 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:55270 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PDabJ-0001MN-3j; Wed, 03 Nov 2010 11:29:54 +0100
Message-ID: <4CD139A0.2070609@levkowetz.com>
Date: Wed, 03 Nov 2010 11:29:52 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <p06240800c8ecfbb84168@[10.20.30.249]>	<p0624088ac8f4ef10b46d@[10.20.30.249]>	<E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com> <p0624089dc8f5f6f7256e@[10.20.30.150]>
In-Reply-To: <p0624089dc8f5f6f7256e@[10.20.30.150]>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: paul.hoffman@vpnc.org, fred@cisco.com, datatracker-rqmts@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] What are WG drafts?
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: Wed, 03 Nov 2010 10:30:09 -0000

Hi Paul,

On 2010-11-02 18:14 Paul Hoffman said:
> At 9:15 AM -0700 11/2/10, Fred Baker wrote:
>> One of the slides wonders what the rule is for identifying drafts
>> associated with a working group. As I'm sure you know, there has
>> been a convention for a long time in naming:
>> draft-ietf-<wg>-*-nn.txt is a working group draft, and
>> draft-<author>-<wg>-*-nn.txt is an individual submission to a
>> working group. draft monikers that mention no working group are
>> general submissions going nowhere in particular. I'm pretty sure
>> that Henrik's existing tool looks for "draft-ietf-<wg>" and
>> "anything containing <wg>" for the two areas.
>> 
>> I like the convention; I find it useful. I do go a little crazy
>> with the set of people that don't choose to use it, though; I get
>> people posting drafts and then wanting to discuss them for several
>> meetings in my WG but not follow the convention, which means that I
>> have to manually track things. Since a "convention" is not a "rule"
>> (eg, I don't care to be a hard-ass about it), I put in the extra
>> work, but there is a part of me that would like the tool to be able
>> to remember for me in some sense. "documents that follow the
>> convention plus those I add".
> 
> Henrik: I believe that some actual WG drafts do not follow the
> draft-ietf-wgname rule. Is that true? If so, how does the Datatracker
> know to show them in the WG charter page? Is that done by hand?

For WG drafts, the database has explicit data which identifies a draft
as belonging to the WG.  This is independent of the naming convention.
For individual drafts, there is currently no explicit tagging in the
database which tells us that a particular draft is 'related to' a
certain WG.


Best,

	Henrik

From paul.hoffman@vpnc.org  Wed Nov  3 06:57:53 2010
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 2B79728C0E5 for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 06:57:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.66
X-Spam-Level: 
X-Spam-Status: No, score=-99.66 tagged_above=-999 required=5 tests=[AWL=-0.441, 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 NaC6cetyALWq for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 06:57:50 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 45ED928C0E7 for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 06:57:50 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA3DvsdO044627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Nov 2010 06:57:55 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240801c8f719f687b0@[10.20.30.249]>
In-Reply-To: <4CD10F30.1050705@gmail.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <4CD10F30.1050705@gmail.com>
Date: Wed, 3 Nov 2010 06:57:51 -0700
To: Yaron Sheffer <yaronf.ietf@gmail.com>, datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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: Wed, 03 Nov 2010 13:57:53 -0000

At 9:28 AM +0200 11/3/10, Yaron Sheffer wrote:
>Reiterating and possibly clarifying what others have said in the past:
>
>I think about 80% of this project is a waste of IETF resources.
>
>I suggest that we concentrate ONLY on providing very granular Atom feeds for draft status changes, Then, we can leave everything else (graphic presentation, update periods, privacy, sharing) to the users. People can use desktop RSS readers, or the easier but more limited Web-based alternatives, e.g. Google Reader.
>
>With the proposal on the table, what we're getting ourselves into is yet another enterprise-level Web application, with all that that involves. Yes, even Web application security.

A clarifying question: If we have such granular per-draft Atom feeds (which is not at all difficult to create), are you proposing that the user must subscribe to them one-by-one? That is, you see more cost than benefit to making an IETF-hosted tool that would help them select groups of drafts and to keep those groups up-to-date (such as when a new draft is added to a WG)?


--Paul Hoffman, Director
--VPN Consortium

From yaronf.ietf@gmail.com  Wed Nov  3 07:09:14 2010
Return-Path: <yaronf.ietf@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 5E6373A69B3 for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 07:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.036
X-Spam-Level: 
X-Spam-Status: No, score=-102.036 tagged_above=-999 required=5 tests=[AWL=0.336, BAYES_00=-2.599, 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 nsPcJRSBzLgM for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 07:09:13 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 6164D3A69A5 for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 07:09:13 -0700 (PDT)
Received: by fxm9 with SMTP id 9so571747fxm.31 for <datatracker-rqmts@ietf.org>; Wed, 03 Nov 2010 07:09:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=dceKuKKWilJeJh+ewnvXd12ZPESm8ak5dAr6q8FbAQE=; b=YGeyuKDmy8VtRahaDqildH+84CMN3hAmqF0D7jo1yunF0Yyz7YyPryFOaMw9PWuKzX ZR/wvAPRMGvYEfcZhqSbLo6BkUfLn+maxLKkIn+DwfLQ7TACQBbiB0mgEnONfXzGBOsX etro1G90YM87cd9hA2N7DxNQcZeUcULXu4P9g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Z/7BTTu9/4ezwInI50l/quBRBeUDfE96Pz7CHvB6afc7nmnQEfnluAQw+7SfgMpq4Q px2vEYIQ68PrWEyaU0xbK9nuudD5WP/Kz9gkL4RdVOP3Bd5cqSU+YGTOkTYTFG0L2SEv OSbNR7jJKUHu9KDV2e/FNS6PQx70la2ApuQ78=
Received: by 10.223.78.199 with SMTP id m7mr12014468fak.11.1288793359873; Wed, 03 Nov 2010 07:09:19 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-181-26-165.red.bezeqint.net [79.181.26.165]) by mx.google.com with ESMTPS id l23sm3692869fam.43.2010.11.03.07.09.18 (version=SSLv3 cipher=RC4-MD5); Wed, 03 Nov 2010 07:09:19 -0700 (PDT)
Message-ID: <4CD16D0C.8070206@gmail.com>
Date: Wed, 03 Nov 2010 16:09:16 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <4CD10F30.1050705@gmail.com> <p06240801c8f719f687b0@[10.20.30.249]>
In-Reply-To: <p06240801c8f719f687b0@[10.20.30.249]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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: Wed, 03 Nov 2010 14:09:14 -0000

Hi Paul,

I can see two ways of dealing with this issue, there are probably more:

- Make the Atom feeds not only per-draft, but more sophisticated. 
Example feed templates:

* All drafts authored by X
* All drafts of the Y WG (which we already have, BTW)
* All drafts whose name/title includes the term Z.

- Alternatively, we could publish and maintain OPML files for common 
collections, e.g. one per WG. [I know you dislike OPML, but it works for 
me]. But this in an inferior solution because people would have to 
update the OPML file (list of feeds) manually.

Thanks,
	Yaron

On 11/03/2010 03:57 PM, Paul Hoffman wrote:
> At 9:28 AM +0200 11/3/10, Yaron Sheffer wrote:
>> Reiterating and possibly clarifying what others have said in the past:
>>
>> I think about 80% of this project is a waste of IETF resources.
>>
>> I suggest that we concentrate ONLY on providing very granular Atom feeds for draft status changes, Then, we can leave everything else (graphic presentation, update periods, privacy, sharing) to the users. People can use desktop RSS readers, or the easier but more limited Web-based alternatives, e.g. Google Reader.
>>
>> With the proposal on the table, what we're getting ourselves into is yet another enterprise-level Web application, with all that that involves. Yes, even Web application security.
>
> A clarifying question: If we have such granular per-draft Atom feeds (which is not at all difficult to create), are you proposing that the user must subscribe to them one-by-one? That is, you see more cost than benefit to making an IETF-hosted tool that would help them select groups of drafts and to keep those groups up-to-date (such as when a new draft is added to a WG)?
>
>
> --Paul Hoffman, Director
> --VPN Consortium

From paul.hoffman@vpnc.org  Wed Nov  3 07:20:20 2010
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 77F943A69C0 for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 07:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.629
X-Spam-Level: 
X-Spam-Status: No, score=-99.629 tagged_above=-999 required=5 tests=[AWL=-0.410, 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 0rEJ2gtt6Xyz for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 07:20:19 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id A727A3A6ABD for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 07:20:19 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA3EKGa7045978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Nov 2010 07:20:17 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240803c8f71f8ad64b@[10.20.30.150]>
In-Reply-To: <4CD16D0C.8070206@gmail.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <4CD10F30.1050705@gmail.com> <p06240801c8f719f687b0@[10.20.30.249]> <4CD16D0C.8070206@gmail.com>
Date: Wed, 3 Nov 2010 07:20:14 -0700
To: Yaron Sheffer <yaronf.ietf@gmail.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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: Wed, 03 Nov 2010 14:20:20 -0000

At 4:09 PM +0200 11/3/10, Yaron Sheffer wrote:
>Hi Paul,
>
>I can see two ways of dealing with this issue, there are probably more:
>
>- Make the Atom feeds not only per-draft, but more sophisticated. Example feed templates:
>
>* All drafts authored by X
>* All drafts of the Y WG (which we already have, BTW)
>* All drafts whose name/title includes the term Z.
>
>- Alternatively, we could publish and maintain OPML files for common collections, e.g. one per WG. [I know you dislike OPML, but it works for me]. But this in an inferior solution because people would have to update the OPML file (list of feeds) manually.

OK, I'm glad I asked. It sounds like you are in favor of some of the list-creation parts of the draft, but not the "my list is stored on the IETF server" part, and not in favor of "I can see my list displayed on the Datatracker web site" part. Is that a fair summary?

--Paul Hoffman, Director
--VPN Consortium

From yaronf.ietf@gmail.com  Wed Nov  3 07:59:26 2010
Return-Path: <yaronf.ietf@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 C66B628C0ED for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 07:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.092
X-Spam-Level: 
X-Spam-Status: No, score=-102.092 tagged_above=-999 required=5 tests=[AWL=0.280, BAYES_00=-2.599, 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 c0rrSXsYzZJr for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 07:59:25 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id B5E2228C0DF for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 07:59:25 -0700 (PDT)
Received: by gxk7 with SMTP id 7so543941gxk.31 for <datatracker-rqmts@ietf.org>; Wed, 03 Nov 2010 07:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=jxLNWgn0SfZQeQVLHvUjV8kdSKVHYTrNsiPq+hdV7R0=; b=eObsaVI/b8gRw76BpdrYD30dtEggrRa4W24mdCbmSS1mXyy4Ed+PP+aU2hj7Cj3mgl /o6gevK57HVcQtzgBedEranwWW3C0IR1ZeD46Vo1hyOxO2qws/lKTtsidUbmkn32gLcA CeA6wLk27y1VJoFKHETlfZtsn/a8EROnY0Yfc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Zi1r8vrrduovt/rci+EwFfdGZ1hJL5fxveY0pMY6UxFLxdrzT3HryiiiMuWuk4A5kB VK9yIrRv+QHQIqKgkxJS1mtrMQTQ3Vz+b4VopTEiWBVe/EcJGJn66RSd0COMx1JKjODX P27KWY+ZgmfgIleyMh95cTpw7a8AWuTOMh5J8=
Received: by 10.223.78.143 with SMTP id l15mr6893739fak.30.1288796372106; Wed, 03 Nov 2010 07:59:32 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-181-26-165.red.bezeqint.net [79.181.26.165]) by mx.google.com with ESMTPS id n8sm3723818faa.7.2010.11.03.07.59.30 (version=SSLv3 cipher=RC4-MD5); Wed, 03 Nov 2010 07:59:31 -0700 (PDT)
Message-ID: <4CD178D0.3000802@gmail.com>
Date: Wed, 03 Nov 2010 16:59:28 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <4CD10F30.1050705@gmail.com> <p06240801c8f719f687b0@[10.20.30.249]> <4CD16D0C.8070206@gmail.com> <p06240803c8f71f8ad64b@[10.20.30.150]>
In-Reply-To: <p06240803c8f71f8ad64b@[10.20.30.150]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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: Wed, 03 Nov 2010 14:59:26 -0000

Sort of. I think Atom feeds should be the only primitive provided, and 
the user should take it from there. It can be as easy as using Google 
Reader, or you can use a much fancier reader application.

The server should have no notion of lists who are owned by somebody, 
only of anonymous feeds. The draft mentions that feeds should be based 
on lists, but I see no reason to have lists in the first place.

One drawback of this direction is that there will be overlaps (e.g. 
between "documents of the IPsecME WG" and "Documents that have 'ipsec' 
in their title"). Perhaps some feed readers can de-duplicate such cases, 
I haven't seen any that do. Alternatively, we may have a powerful enough 
feed creation mechanism, so that you can specify the union of these two 
feeds as a single feed. Then you can sort/filter the resulting feed on 
the client side if necessary.

Thanks,
	Yaron

On 11/03/2010 04:20 PM, Paul Hoffman wrote:
> At 4:09 PM +0200 11/3/10, Yaron Sheffer wrote:
>> Hi Paul,
>>
>> I can see two ways of dealing with this issue, there are probably more:
>>
>> - Make the Atom feeds not only per-draft, but more sophisticated. Example feed templates:
>>
>> * All drafts authored by X
>> * All drafts of the Y WG (which we already have, BTW)
>> * All drafts whose name/title includes the term Z.
>>
>> - Alternatively, we could publish and maintain OPML files for common collections, e.g. one per WG. [I know you dislike OPML, but it works for me]. But this in an inferior solution because people would have to update the OPML file (list of feeds) manually.
>
> OK, I'm glad I asked. It sounds like you are in favor of some of the list-creation parts of the draft, but not the "my list is stored on the IETF server" part, and not in favor of "I can see my list displayed on the Datatracker web site" part. Is that a fair summary?
>
> --Paul Hoffman, Director
> --VPN Consortium

From paul.hoffman@vpnc.org  Wed Nov  3 09:09:34 2010
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 C49D53A6AC9 for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 09:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.715
X-Spam-Level: 
X-Spam-Status: No, score=-99.715 tagged_above=-999 required=5 tests=[AWL=-0.269, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, 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 EfY2FcnIXWEZ for <datatracker-rqmts@core3.amsl.com>; Wed,  3 Nov 2010 09:09:34 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 176AE3A6AC6 for <datatracker-rqmts@ietf.org>; Wed,  3 Nov 2010 09:09:34 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA3G9cCX052667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Nov 2010 09:09:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624080ac8f7387faf99@[10.20.30.150]>
In-Reply-To: <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net>
Date: Wed, 3 Nov 2010 09:09:37 -0700
To: SM <sm@resistor.net>, datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Privacy of lists
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: Wed, 03 Nov 2010 16:09:34 -0000

Drilling down a bit more.

At 11:54 AM -0700 11/2/10, SM wrote:
>Hello,
>At 08:36 02-11-10, Paul Hoffman wrote:
>>When you say "who else", do you mean "which other lists include this draft" or "which people who created a list which includes this draft"?
>
>I meant who are the people who created a list which includes this draft.

Attempt at summarizing: you want people who use the new tool to have to be authenticated, and anyone can see which of the authenticated people created a list that refers to a draft. Yes?

>>Correct: there was an implicit definition (that I can make explicit) of "the person who created the list, whomever that person gives access to, and no one else".
>
>That sounds fine unless we go down the path where the "following" is used as a measure of whether there is interest in a proposal.

If we don't go down that path (such as I explicitly say in this draft that it cannot be used for such measurements), do you still want the requirement above?

--Paul Hoffman, Director
--VPN Consortium

From barryleiba.mailing.lists@gmail.com  Thu Nov  4 05:45:34 2010
Return-Path: <barryleiba.mailing.lists@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 52D3C3A68A3 for <datatracker-rqmts@core3.amsl.com>; Thu,  4 Nov 2010 05:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.75
X-Spam-Level: 
X-Spam-Status: No, score=-101.75 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 MhrmRdBEbDpB for <datatracker-rqmts@core3.amsl.com>; Thu,  4 Nov 2010 05:45:33 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 847563A6825 for <datatracker-rqmts@ietf.org>; Thu,  4 Nov 2010 05:45:33 -0700 (PDT)
Received: by gwb15 with SMTP id 15so1439273gwb.31 for <datatracker-rqmts@ietf.org>; Thu, 04 Nov 2010 05:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=MZ0I0DjcWDTTef+mKauMOk7R88trYy5KmjruyOXpmSI=; b=PAXjlnRlVirdbM/yfswwaJQRJjU7OwImx003Mpbrum6ir8TxOxHU+jSMTymgLAVjbr 3qqR6TTFAOI+jvsF27DwwHr2BhFmJRmNVcrAvgiuBuuR9AcYobKvxnnn1/AICyX4NGpl D03N0aaD9dCtMbdp2bKtsRsizd/G7wBW3zxV4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=I3HoYhPcWX90mj9Tw4wgikiSDWd3RvN+vjLziPURC+iM8GoRt34NfSDudqO4fhekJ1 VodX5OnJ8tci++MQM6sAKgb/0SjpTgKL6sfVSC3kjOgPc0AFrAfZDs5JNlRMjUm/ONjU e3wcbdqe6qjm99mfhFPeb8shtJqE3+qZYicxU=
MIME-Version: 1.0
Received: by 10.42.171.66 with SMTP id i2mr334258icz.5.1288874742786; Thu, 04 Nov 2010 05:45:42 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.229.200 with HTTP; Thu, 4 Nov 2010 05:45:42 -0700 (PDT)
In-Reply-To: <p0624080ac8f7387faf99@10.20.30.150>
References: <p06240800c8ecfbb84168@10.20.30.249> <p0624088ac8f4ef10b46d@10.20.30.249> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@10.20.30.150> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <p0624080ac8f7387faf99@10.20.30.150>
Date: Thu, 4 Nov 2010 20:45:42 +0800
X-Google-Sender-Auth: MuuPRoCl0FFNGQn5at4Ep3AvqZU
Message-ID: <AANLkTimR9AbARBNtCmdQpQnrvec7eCuG0vU-Y0JXZCn9@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Privacy of lists
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: Thu, 04 Nov 2010 12:45:34 -0000

> Attempt at summarizing: you want people who use the new tool to have
> to be authenticated, and anyone can see which of the authenticated people
> created a list that refers to a draft. Yes?

I'll make it simple here: if it should work this way, I will not use
it.  I'll just keep my own list, and check it twice.

Barry

From sm@resistor.net  Fri Nov  5 01:17:50 2010
Return-Path: <sm@resistor.net>
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 70DC13A6907 for <datatracker-rqmts@core3.amsl.com>; Fri,  5 Nov 2010 01:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.023
X-Spam-Level: 
X-Spam-Status: No, score=-103.023 tagged_above=-999 required=5 tests=[AWL=0.576, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 hm-EoQfFMsjj for <datatracker-rqmts@core3.amsl.com>; Fri,  5 Nov 2010 01:17:48 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id E099F3A6904 for <datatracker-rqmts@ietf.org>; Fri,  5 Nov 2010 01:17:48 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id oA58H8sG027077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Nov 2010 01:17:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1288945079; x=1289031479; bh=JwtlXsEnvS+JzrQJyIuILrbKNmkCZ3YzrZS1cE7pOHY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=Pu3JtHGw4PYwvZOZJhhZ6diRZ+1+82DmhbPcLlaOHHwfhNeYlqI9kyiKcs+aNpKiH it9lLDv0NSNOC6zfFxlI2sTKSAfPNcCeMp2iWuMPjumUI4uoSgNzNDtBPX24USmjOo Je3COad4QxPIiJ874fi/DtK5ejMTXi8LZ8FvpwnU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1288945079; x=1289031479; bh=JwtlXsEnvS+JzrQJyIuILrbKNmkCZ3YzrZS1cE7pOHY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=iCYhL273WqxtdN+QwaKu1Di5Qf3jLE/faiD8AkrDGfI/P8S3WwZOOzGAy5P+AwnfA e7+jMfUHdbWZkx7u8hKmgXc5CoJ3ZHmSR2p4OPxsDV3wH1bPwCqhIBkji7LMSm32Q8 4W+9nx8rq/fdw5ieygXCoPiXE0VEloxXkEdYIclA=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=Vq2EBqM/hR7E/YS8mTXBVtc6LocDl4Tv5ex9xeB6HU9Cc/qRN0feh8P8+JxN57H7v OcIck47bMTw98S0oAr1K6URDyihPG0GmhDLkWJGXdbdURB7zRfhsUOJtJju5dG2VloB X7L3cl5Z5ZFY6TqxF/yIHF49x6BwKqXvJL/pZUQ=
Message-Id: <6.2.5.6.2.20101105005037.0a436570@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 05 Nov 2010 01:16:36 -0700
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: SM <sm@resistor.net>
In-Reply-To: <p0624080ac8f7387faf99@[10.20.30.150]>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <p0624080ac8f7387faf99@[10.20.30.150]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Privacy of lists
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: Fri, 05 Nov 2010 08:17:50 -0000

Hi Paul,
At 09:09 03-11-10, Paul Hoffman wrote:
>Attempt at summarizing: you want people who use the new tool to have 
>to be authenticated, and anyone can see which of the authenticated 
>people created a list that refers to a draft. Yes?

No.  If we go by the arguments put forward by Henrik, this is a 
non-issue.  If these lists works along the same lines as IETF mailing 
list, these lists would have to be open.

>If we don't go down that path (such as I explicitly say in this 
>draft that it cannot be used for such measurements), do you still 
>want the requirement above?

No, I prefer not to use it for such measurements to keep matters simple.

Regards,
-sm 


From paul.hoffman@vpnc.org  Fri Nov  5 15:31:30 2010
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 717213A695E for <datatracker-rqmts@core3.amsl.com>; Fri,  5 Nov 2010 15:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.141
X-Spam-Level: 
X-Spam-Status: No, score=-98.141 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, DATE_IN_FUTURE_12_24=2.189, 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 fG-S8WPzJewx for <datatracker-rqmts@core3.amsl.com>; Fri,  5 Nov 2010 15:31:29 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id BC3983A695D for <datatracker-rqmts@ietf.org>; Fri,  5 Nov 2010 15:31:29 -0700 (PDT)
Received: from [10.20.30.150] ([222.128.202.158]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA5MVdUG019184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Nov 2010 15:31:42 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240829c8fb08d7af68@[10.20.30.150]>
In-Reply-To: <6.2.5.6.2.20101105005037.0a436570@resistor.net>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <p0624080ac8f7387faf99@[10.20.30.150]> <6.2.5.6.2.20101105005037.0a436570@resistor.net>
Date: Sat, 6 Nov 2010 06:31:37 -0700
To: SM <sm@resistor.net>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Privacy of lists
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: Fri, 05 Nov 2010 22:31:30 -0000

At 1:16 AM -0700 11/5/10, SM wrote:
>Hi Paul,
>At 09:09 03-11-10, Paul Hoffman wrote:
>>Attempt at summarizing: you want people who use the new tool to have to be authenticated, and anyone can see which of the authenticated people created a list that refers to a draft. Yes?
>
>No.  If we go by the arguments put forward by Henrik, this is a non-issue.  If these lists works along the same lines as IETF mailing list, these lists would have to be open.

OK, I'll remove this from the presentation then. If you can think of words I can put in the draft to make it clear that these lists-of-drafts are not discussion lists, I can do that.

Of course, if Yaron's preferences are adopted, this will be a non-issue.

--Paul Hoffman, Director
--VPN Consortium

From yaronf.ietf@gmail.com  Sun Nov  7 02:28:34 2010
Return-Path: <yaronf.ietf@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 34A3F3A698A for <datatracker-rqmts@core3.amsl.com>; Sun,  7 Nov 2010 02:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.132
X-Spam-Level: 
X-Spam-Status: No, score=-102.132 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, 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 3FsytIcK1ejI for <datatracker-rqmts@core3.amsl.com>; Sun,  7 Nov 2010 02:28:33 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 351803A6980 for <datatracker-rqmts@ietf.org>; Sun,  7 Nov 2010 02:28:32 -0800 (PST)
Received: by wyb28 with SMTP id 28so4527096wyb.31 for <datatracker-rqmts@ietf.org>; Sun, 07 Nov 2010 02:28:50 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=516OC6rNHhnDEdlp32GxarfGidKEFN3CceAvZ0ODazk=; b=g8fMAzfgZHNj3XVDpn9ksXWOqwdLDdtjplYTEfg7FtzmqER7fwG8wSJaG/xDQgws3R gN+HWHvbzGqIY/3y2DuUGAUwkOFJAQCFq5PNJ4DgUWEIWdJX1lyn9TVsDYTBRB3hBenI n2o1D76+mFeqzX79/VYJ5V5OYL9+Ht2tO/ifY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=IroDsCJE+WuVo4waBYnLu2yOQo+OEpu1LXQp496whouvBkN4PF23b6+H+qfp9FhEvU e3PNlAW7Rw/NLZ6+B+c/mmjv+RGwCeXZtZ/29ZFDKNFkdLZ1L/HmtYE0jSoHooN7R9hK u51oAsbTcsmEYkCWFuBrSIWYHKtgjYAOsNsnA=
Received: by 10.227.145.136 with SMTP id d8mr3962651wbv.172.1289125730429; Sun, 07 Nov 2010 02:28:50 -0800 (PST)
Received: from [10.0.0.2] (bzq-79-181-26-165.red.bezeqint.net [79.181.26.165]) by mx.google.com with ESMTPS id a17sm3063137wbe.18.2010.11.07.02.28.47 (version=SSLv3 cipher=RC4-MD5); Sun, 07 Nov 2010 02:28:48 -0800 (PST)
Message-ID: <4CD67F5D.7050100@gmail.com>
Date: Sun, 07 Nov 2010 12:28:45 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <4CD10F30.1050705@gmail.com> <p06240801c8f719f687b0@[10.20.30.249]> <4CD16D0C.8070206@gmail.com> <p06240803c8f71f8ad64b@[10.20.30.150]> <4CD17860.3080402@gmail.com>
In-Reply-To: <4CD17860.3080402@gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
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: Sun, 07 Nov 2010 10:28:34 -0000

One more data point regarding the RSS/Atom option: in fact some feed 
readers are able to detect duplicates. At least my favorite reader, 
Liferea, can do it: 
http://liferea.blogspot.com/2007/02/item-duplicate-detection.html.

Thanks,
	Yaron

On 11/03/2010 04:57 PM, Yaron Sheffer wrote:
> Sort of. I think Atom feeds should be the only primitive provided, and
> the user should take it from there. It can be as easy as using Google
> Reader, or you can use a much fancier reader application.
>
> The server should have no notion of lists who are owned by somebody,
> only of anonymous feeds. The draft mentions that feeds should be based
> on lists, but I see no reason to have lists in the first place.
>
> One drawback of this direction is that there will be overlaps (e.g.
> between "documents of the IPsecME WG" and "Documents that have 'ipsec'
> in their title"). Perhaps some feed readers can de-duplicate such cases,
> I haven't seen any that do. Alternatively, we may have a powerful enough
> feed creation mecha, so that you can specify the union of these two
> feeds as a single feed.
>
> Thanks,
> Yaron
>
> On 11/03/2010 04:20 PM, Paul Hoffman wrote:
>> At 4:09 PM +0200 11/3/10, Yaron Sheffer wrote:
>>> Hi Paul,
>>>
>>> I can see two ways of dealing with this issue, there are probably more:
>>>
>>> - Make the Atom feeds not only per-draft, but more sophisticated.
>>> Example feed templates:
>>>
>>> * All drafts authored by X
>>> * All drafts of the Y WG (which we already have, BTW)
>>> * All drafts whose name/title includes the term Z.
>>>
>>> - Alternatively, we could publish and maintain OPML files for common
>>> collections, e.g. one per WG. [I know you dislike OPML, but it works
>>> for me]. But this in an inferior solution because people would have
>>> to update the OPML file (list of feeds) manually.
>>
>> OK, I'm glad I asked. It sounds like you are in favor of some of the
>> list-creation parts of the draft, but not the "my list is stored on
>> the IETF server" part, and not in favor of "I can see my list
>> displayed on the Datatracker web site" part. Is that a fair summary?
>>
>> --Paul Hoffman, Director
>> --VPN Consortium

From sm@resistor.net  Sun Nov  7 02:35:24 2010
Return-Path: <sm@resistor.net>
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 B58483A68EC for <datatracker-rqmts@core3.amsl.com>; Sun,  7 Nov 2010 02:35:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.14
X-Spam-Level: 
X-Spam-Status: No, score=-103.14 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 rZouVaGhEjgz for <datatracker-rqmts@core3.amsl.com>; Sun,  7 Nov 2010 02:35:21 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id CDA933A69D4 for <datatracker-rqmts@ietf.org>; Sun,  7 Nov 2010 02:35:14 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id oA7AZ0fq010434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Nov 2010 02:35:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1289126131; x=1289212531; bh=ITZEO6kdSS1evkaYD5QjLY2oYc4S4wQMhuAnd3bOKZA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=pGIPnHvsyNSDHAGzfvASYYlS1lT1dC1om3RFSaaChF3JQM+wzalQonYx8SSJDBc6w oyHyukjWZiugcVzDZ8xq02vb0qftbJF6kIv+BZr6+DGQVsK7EdZcq5n+OIpvDxJ6EG gKIhUD8xypHrGKwwXEDKZ9e8gt9ulRKPkPYu4lCI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1289126131; x=1289212531; bh=ITZEO6kdSS1evkaYD5QjLY2oYc4S4wQMhuAnd3bOKZA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=jKwe1LjguXzb79GCJV49qzg9fB5QWxqqa5lFBqV0JH2dXdT7yxk52bSTdBITopBiH UjKyb5IY4K8DqQtkZ3Ye9O8esvfx7r4O36slwb9V8J2MNP5FS76h9KW7GB8O/fIWwv UHxUUOfdDmzVx7RYr8xtZmECkWpywKykpivuhgNg=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=y1EdJ+Gu79QHWtEWvkdLSh7gC8Gv26ahOKa3ijlJoVPEJq2loXzdj1SSqL0WHQvyu cx0HPLyk7atfaNMOYFUF9Elv0PQMybOpmLxFauDatp7GBWRJ4BQsG23h5OW5YIb1vVY BwksUqrkv5FYjptUAjFTzU3fRBo/DVZFc9fT9Us=
Message-Id: <6.2.5.6.2.20101107013057.0a87ad58@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 07 Nov 2010 02:34:30 -0800
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: SM <sm@resistor.net>
In-Reply-To: <p06240829c8fb08d7af68@[10.20.30.150]>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <6.2.5.6.2.20101102074555.099f1830@resistor.net> <p06240894c8f5dde043db@[10.20.30.150]> <6.2.5.6.2.20101102110842.0a10f7c0@resistor.net> <p0624080ac8f7387faf99@[10.20.30.150]> <6.2.5.6.2.20101105005037.0a436570@resistor.net> <p06240829c8fb08d7af68@[10.20.30.150]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Privacy of lists
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: Sun, 07 Nov 2010 10:35:24 -0000

Hi Paul,
At 06:31 06-11-10, Paul Hoffman wrote:
>OK, I'll remove this from the presentation then. If you can think of 
>words I can put in the draft to make it clear that these 
>lists-of-drafts are not discussion lists, I can do that.

As there is a BoF for the project, I suggest letting people flush 
this out as the argument may still be brought forward even with a rewording.

>Of course, if Yaron's preferences are adopted, this will be a non-issue.

The problem with building such tools is that there are always some 
feature that are good to have.  Yaron's preferences [1] side step the issues.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/datatracker-rqmts/current/msg00020.html 


From paul.hoffman@vpnc.org  Sat Nov 13 20:41:28 2010
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 BE7993A6B3E for <datatracker-rqmts@core3.amsl.com>; Sat, 13 Nov 2010 20:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.167
X-Spam-Level: 
X-Spam-Status: No, score=-100.167 tagged_above=-999 required=5 tests=[AWL=-0.721, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, 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 QEgh9EELUoty for <datatracker-rqmts@core3.amsl.com>; Sat, 13 Nov 2010 20:41:22 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id E879C3A67E5 for <datatracker-rqmts@ietf.org>; Sat, 13 Nov 2010 20:41:21 -0800 (PST)
Received: from [130.129.72.80] (dhcp-4850.meeting.ietf.org [130.129.72.80]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAE4fsVS087802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Sat, 13 Nov 2010 21:41:57 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240823c905180f6461@[130.129.72.80]>
Date: Sun, 14 Nov 2010 12:41:52 +0800
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] BoF minutes posted
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: Sun, 14 Nov 2010 04:41:28 -0000

See <http://www.ietf.org/proceedings/79/minutes/iddtspec.txt>. Please send me any changes needed.

Next step: I put together the -02 draft. That will hopefully be within a week, but there is a lot to add. I say that happily, but with a tad of trepidation.

--Paul Hoffman, Director
--VPN Consortium

From ietf@augustcellars.com  Mon Nov 15 01:07:02 2010
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 9EA813A6C59 for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 01:07:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=-1.299, BAYES_50=0.001]
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 Ta4fwmyqBnDk for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 01:07:01 -0800 (PST)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by core3.amsl.com (Postfix) with ESMTP id D66AA3A6AA8 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 01:07:01 -0800 (PST)
Received: from TITUS (176.120.168.69.static.onlinenw.com [69.168.120.176]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTP id 808E26EF1A for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 01:07:42 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <datatracker-rqmts@ietf.org>
Date: Mon, 15 Nov 2010 01:17:38 -0800
Message-ID: <069201cb84a5$f3600e60$da202b20$@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: AcuEpXqXEaUw4hb4SU27fUsho5XTWA==
Content-Language: en-us
Subject: [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 09:07:02 -0000

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



From royersoftwareandservices@gmail.com  Mon Nov 15 11:17:12 2010
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

From paul.hoffman@vpnc.org  Mon Nov 15 11:30:15 2010
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

From ajs@shinkuro.com  Mon Nov 15 11:38:24 2010
Return-Path: <ajs@shinkuro.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 4CD033A6D07 for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, 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 bqklLTf4el3Z for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:38:23 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id A81963A6D0E for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 11:38:23 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 3CBD31ECB442 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 19:39:05 +0000 (UTC)
Date: Mon, 15 Nov 2010 14:39:02 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: datatracker-rqmts@ietf.org
Message-ID: <20101115193902.GB322@shinkuro.com>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com> <p06240823c9073a421353@[10.20.30.150]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06240823c9073a421353@[10.20.30.150]>
User-Agent: Mutt/1.5.18 (2008-05-17)
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:38:24 -0000

On Mon, Nov 15, 2010 at 11:30:45AM -0800, Paul Hoffman wrote:
> That's not what Jim said. His example was some private data in the Datatracker.

I don't have time for a more detailed comment right now, but do we
really think it a good idea to be adding private data to the
datatracker?  Public systems with private data in them are mostly a
nightmare.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From housley@vigilsec.com  Mon Nov 15 11:45:49 2010
Return-Path: <housley@vigilsec.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 E3FAA28C0EF for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, 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 boM4e9WOty-a for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:45:49 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 3A8CF3A6BB6 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 11:45:49 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 011479A47CA for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 14:46:49 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id fo3lC7zxreTm for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 14:46:12 -0500 (EST)
Received: from [172.30.1.77] (unknown [12.230.88.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 8F7719A47C7 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 14:46:46 -0500 (EST)
Message-ID: <4CE18E2F.2050704@vigilsec.com>
Date: Mon, 15 Nov 2010 14:46:55 -0500
From: Russ Housley <housley@vigilsec.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: <p06240823c905180f6461@[130.129.72.80]>
In-Reply-To: <p06240823c905180f6461@[130.129.72.80]>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [datatracker-rqmts] BoF minutes posted
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:45:50 -0000

Just one comment ...

Slide 3: High-level overview
	Russ Housley: This is very draft focused because the IETF is

Something is missing!  This is not a full sentence.  I think that I said
the current draft is focused on Internet-Drafts.




From paul.hoffman@vpnc.org  Mon Nov 15 11:53:13 2010
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 B679928C0E4 for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.856
X-Spam-Level: 
X-Spam-Status: No, score=-99.856 tagged_above=-999 required=5 tests=[AWL=-0.637, 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 V1BIQD0nG7xx for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 11:53:13 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id D051628C120 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 11:53:10 -0800 (PST)
Received: from [75.101.18.87] (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAFJroCQ082944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Nov 2010 12:53:52 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240800c907401a1c26@[10.20.30.249]>
In-Reply-To: <20101115193902.GB322@shinkuro.com>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com> <p06240823c9073a421353@[10.20.30.150]> <20101115193902.GB322@shinkuro.com>
Date: Mon, 15 Nov 2010 11:53:49 -0800
To: Andrew Sullivan <ajs@shinkuro.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:53:13 -0000

At 2:39 PM -0500 11/15/10, Andrew Sullivan wrote:
>On Mon, Nov 15, 2010 at 11:30:45AM -0800, Paul Hoffman wrote:
>> That's not what Jim said. His example was some private data in the Datatracker.
>
>I don't have time for a more detailed comment right now, but do we
>really think it a good idea to be adding private data to the
>datatracker?  Public systems with private data in them are mostly a
>nightmare.

Henrik can comment more fully about the private data stored in the Datatracker. I'm pretty sure there is a bunch of it for the ISE, for the IESG, and so on.

--Paul Hoffman, Director
--VPN Consortium

From royersoftwareandservices@gmail.com  Mon Nov 15 12:17:32 2010
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 1B24B3A6D14 for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 12:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[AWL=0.044,  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 JepkIh0JWiuB for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 12:17:31 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id B449B3A6D20 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 12:17:29 -0800 (PST)
Received: by gxk27 with SMTP id 27so3665803gxk.31 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 12:18:11 -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=K0zcMF1pxjq2sYngblCDfbopdr4wSNOSNq5Cp9x5M/k=; b=R96Lk7sW2D5jgmmDJlD0HbvzcVXf70uGdhtgbQh4WvG9a1tBUR9ehP6BblIOFrWAQl ZlI4t+QZoWO++A53vpnWDQrGjEqilSeGltxTe1rokNunuHP550OjkXdSHQI5Uwc0yi6A xpAlcoqfN39rOBxS6bo9KvVCZnxMWvMEFypgI=
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=O8tkZeitG3VinfTIkQ8A58/JdHSVgljXMXFAZJWGeQA7V9u6RmiGDmMK1BvpiD8nYF LbPimLnJZSFY9NynZWgmPYVFLvgUEViA04fnRmjKOE0jLpD41Z3+o+HLvigTNmfWXEsl vj9Q1Gaw5UtgMGXL66F6/oPN9uurbBugpCs3U=
Received: by 10.100.171.9 with SMTP id t9mr4503094ane.151.1289852291301; Mon, 15 Nov 2010 12:18:11 -0800 (PST)
Received: from [192.168.0.58] ([63.227.129.161]) by mx.google.com with ESMTPS id g18sm4135069anh.18.2010.11.15.12.18.09 (version=SSLv3 cipher=RC4-MD5); Mon, 15 Nov 2010 12:18:10 -0800 (PST)
Message-ID: <4CE19579.7040002@gmail.com>
Date: Mon, 15 Nov 2010 13:18:01 -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> <4CE18751.7030002@gmail.com> <p06240823c9073a421353@[10.20.30.150]>
In-Reply-To: <p06240823c9073a421353@[10.20.30.150]>
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 20:17:32 -0000

I am not trying to be a pain. I just don't see the need for private. And 
the explanation
given in that post does not convince me that anyone could reach any 
dangerous, invasive,
disruptive, or anything else conclusions by knowing that some people are 
looking at something.

Adding private seems like a lot of access control issues that  can 
break, have some misconfiguration,
or software bug, that would not reveal the same information. With the 
terabytes of data posted on the net (daily?),
it would be easier for an employer to just look at the employees 
activities than to write a tool to
see what drafts there employee is looking at. (re: the example in the 
current draft).

I have read the draft. Who could tell what it meant that  someone is 
looking at stuff?

My point is, what's private mean here?

Would it be private that the draft changed? That some status changed? 
That someone is looking
for keyword 'oops'? What would be private? The drafts are not private. 
The status of a draft
is not private.

The name of the ISE is not private. The names of the IESB members is not 
private. They are
going to review the drafts anyway. So, that is not private.

The title of the draft  is :

     Requirements for Draft Tracking by the IETF Community in the 
Datatracker

Not 'Requirement of the IAB, IETF, IESB, ISE, ...'

So that argument posted does not seem on point - in my opinion.

If it is needed, then it is needed. I have just not seen anyone post a 
reason
that convinces me that it is needed.

I have no plans to pound on this issue. I am trying to understand it.

-Doug


From housley@vigilsec.com  Mon Nov 15 12:29:53 2010
Return-Path: <housley@vigilsec.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 3967E3A6D1A for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 12:29:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level: 
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_00=-2.599, 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 QZ7V-76juOlt for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 12:29:52 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 776F53A6D01 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 12:29:52 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D57789A4742 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 15:30:45 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id jBA9myuVcIDJ for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 15:30:32 -0500 (EST)
Received: from [172.30.1.77] (unknown [12.230.88.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 401509A4740 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 15:30:45 -0500 (EST)
Message-ID: <4CE19885.90401@vigilsec.com>
Date: Mon, 15 Nov 2010 15:31:01 -0500
From: Russ Housley <housley@vigilsec.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>	<4CE18751.7030002@gmail.com> <p06240823c9073a421353@[10.20.30.150]>	<20101115193902.GB322@shinkuro.com> <p06240800c907401a1c26@[10.20.30.249]>
In-Reply-To: <p06240800c907401a1c26@[10.20.30.249]>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
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 20:29:53 -0000

Paul:

>>> That's not what Jim said. His example was some private data in the Datatracker.
>>
>> I don't have time for a more detailed comment right now, but do we
>> really think it a good idea to be adding private data to the
>> datatracker?  Public systems with private data in them are mostly a
>> nightmare.
> 
> Henrik can comment more fully about the private data stored in the Datatracker. I'm pretty sure there is a bunch of it for the ISE, for the IESG, and so on.

The IESG has the ability to mark comments as private, but I have not
seen one in the last six years or more.

I think we should avoid non-public data unless it provides high value.
So, the question is whether private lists are sufficiently valuable.

Russ

From paul.hoffman@vpnc.org  Mon Nov 15 12:36:15 2010
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 49E2D3A6D23 for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 12:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.202
X-Spam-Level: 
X-Spam-Status: No, score=-100.202 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_20=-0.74, 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 OfTJIsWD3wFI for <datatracker-rqmts@core3.amsl.com>; Mon, 15 Nov 2010 12:36:14 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 735C528C0E4 for <datatracker-rqmts@ietf.org>; Mon, 15 Nov 2010 12:36:14 -0800 (PST)
Received: from [75.101.18.87] (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAFKapma085182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Nov 2010 13:36:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240801c90748751174@[75.101.18.87]>
In-Reply-To: <4CE19579.7040002@gmail.com>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com> <p06240823c9073a421353@[10.20.30.150]> <4CE19579.7040002@gmail.com>
Date: Mon, 15 Nov 2010 12:36:50 -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 20:36:15 -0000

At 1:18 PM -0700 11/15/10, Royer Software and Services wrote:
>I am not trying to be a pain. I just don't see the need for private.

Private what? Private data that is already in the Datatracker (as Jim pointed out), or private lists (as are defined in the draft)? This is an important distinction.

>And the explanation
>given in that post does not convince me that anyone could reach any dangerous, invasive,
>disruptive, or anything else conclusions by knowing that some people are looking at something.

Again, that is not what Jim said. Let's try again:

At 1:17 AM -0800 11/15/10, 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.

There is nothing there about "knowing that some people are looking at something".

>Adding private seems like a lot of access control issues that  can break, have some misconfiguration,
>or software bug, that would not reveal the same information. With the terabytes of data posted on the net (daily?),
>it would be easier for an employer to just look at the employees activities than to write a tool to
>see what drafts there employee is looking at. (re: the example in the current draft).

The example in the current draft is not just about an employer looking. If I were looking for a job at XywCorp and created a list of all drafts written by XyzCorp employees, there are plenty of people I would not want to see my list.

>I have read the draft. Who could tell what it meant that  someone is looking at stuff?

I'm sorry, but I can't parse that question.

>My point is, what's private mean here?

See above.

>Would it be private that the draft changed? That some status changed? That someone is looking
>for keyword 'oops'? What would be private? The drafts are not private. The status of a draft
>is not private.

Correct. In the current draft, the *list of drafts* is private unless its creator makes it public. In the current Datatracker, some data is private.

>The name of the ISE is not private. The names of the IESB members is not private. They are
>going to review the drafts anyway. So, that is not private.

No one said it was.

>The title of the draft  is :
>
>    Requirements for Draft Tracking by the IETF Community in the Datatracker
>
>Not 'Requirement of the IAB, IETF, IESB, ISE, ...'

The IAB, IESG, and so on are members of the IETF community.

>So that argument posted does not seem on point - in my opinion.
>
>If it is needed, then it is needed. I have just not seen anyone post a reason
>that convinces me that it is needed.
>
>I have no plans to pound on this issue. I am trying to understand it.

Please re-read Jim's message again in light of my questions to you about what you mean by "private".

--Paul Hoffman, Director
--VPN Consortium

From ietf@augustcellars.com  Mon Nov 15 19:42:40 2010
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


From paul.hoffman@vpnc.org  Sun Nov 21 20:06:57 2010
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 C729B3A6936 for <datatracker-rqmts@core3.amsl.com>; Sun, 21 Nov 2010 20:06:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.944
X-Spam-Level: 
X-Spam-Status: No, score=-99.944 tagged_above=-999 required=5 tests=[AWL=-0.498, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, 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 WS5dJ6kIzHug for <datatracker-rqmts@core3.amsl.com>; Sun, 21 Nov 2010 20:06:57 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 1E7733A6888 for <datatracker-rqmts@ietf.org>; Sun, 21 Nov 2010 20:06:57 -0800 (PST)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAM47ocP090515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Sun, 21 Nov 2010 21:07:51 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240802c90f9c1d813c@[10.20.30.150]>
In-Reply-To: <001f01cb8541$cbe593e0$63b0bba0$@augustcellars.com>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com> <001f01cb8541$cbe593e0$63b0bba0$@augustcellars.com>
Date: Sun, 21 Nov 2010 20:07:48 -0800
To: <datatracker-rqmts@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Community Datatracker draft -02
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, 22 Nov 2010 04:06:57 -0000

Greetings again. As promised, I have made massive revisions (mostly additions) to the draft based on the input at the BoF in Beijing and follow-up discussion. The new draft can be found at <http://www.ietf.org/internet-drafts/draft-ietf-genarea-datatracker-community-02.txt>.

It might have been silly for me to try to track all the changes in Appendix D, but some of y'all might want to check that I hit all the points given during the BoF.

All input is still welcome. At some point soon, I will start some focused threads, but feel free to start your own.

--Paul Hoffman, Director
--VPN Consortium

From ietf@augustcellars.com  Sun Nov 21 23:18:31 2010
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 004963A6A0E for <datatracker-rqmts@core3.amsl.com>; Sun, 21 Nov 2010 23:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, 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 96pY-RcHlQuq for <datatracker-rqmts@core3.amsl.com>; Sun, 21 Nov 2010 23:18:30 -0800 (PST)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by core3.amsl.com (Postfix) with ESMTP id 0D32B3A6952 for <datatracker-rqmts@ietf.org>; Sun, 21 Nov 2010 23:18:29 -0800 (PST)
Received: from TITUS (unknown [207.202.179.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTP id ADE706EF4A; Sun, 21 Nov 2010 23:19:23 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>, <datatracker-rqmts@ietf.org>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com>	<4CE18751.7030002@gmail.com>	<001f01cb8541$cbe593e0$63b0bba0$@augustcellars.com> <p06240802c90f9c1d813c@[10.20.30.150]>
In-Reply-To: <p06240802c90f9c1d813c@[10.20.30.150]>
Date: Sun, 21 Nov 2010 23:32:34 -0800
Message-ID: <003101cb8a17$6faeaaf0$4f0c00d0$@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+Y3kZx1QsKT7FjIQKCUTwEAeo0jB8Cp4rtvZOOYp8A
Content-Language: en-us
Subject: Re: [datatracker-rqmts] Community Datatracker draft -02
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, 22 Nov 2010 07:18:31 -0000

Paul,

Some responses to this document.

1.  Is there perhaps a requirement for some type of mathematics of the
lists?   We currently have unions - i.e. make me a list of lists.  I don't
know that I can think of any good reason to have intersections (i.e. in all
of the following lists), but I can think that the subtraction operation
might be very useful.  I care about everything that this working group does
EXCEPT for the following documents.

2.  In section 2.1.6, I am wondering if I can put a list instead of a
particular RFC or particular draft in some of the locations?  I.e. can I get
a list of all of the drafts/rfcs that are referenced by the drafts/rfcs in
this list?  I can see it as being useful for some type of background
processing.  I.e. I need to figure out which drafts or RFCs I might care
about reading because they relate to the current set of drafts that I am
tracking.

3.  Section 2.2.2 - This section does not match exactly what I remember from
the discussion.  I remember that it should be possible to create an atom
feed that specifies exactly which events are to be sent.  (OK - I see this
in the open issue list.)

4. In Section 2.3.1 - You have a requirement that the display should only
show a single draft once.  Does the same requirement also apply to the atom
and e-mail feeds?

5.  In section 2.3.3 - you talk about having the flag on a draft in a list.
Do you really mean list or view of a list?  What happens if you have
multiple flags because the draft appears in multiple lists?

6.  In appendix B - It might be better to have a set of "pre-defined" lists
that are owned by tools team (or some such group) that contain the set of
good pre-defined lists that people want to see.  Such as: 
  WG - Std track documents
  WG - Non-std track documents
  WG - Agenda documents for next meeting.
  ....

Jim


> -----Original Message-----
> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
> bounces@ietf.org] On Behalf Of Paul Hoffman
> Sent: Sunday, November 21, 2010 8:08 PM
> To: datatracker-rqmts@ietf.org
> Subject: [datatracker-rqmts] Community Datatracker draft -02
> 
> Greetings again. As promised, I have made massive revisions (mostly
additions)
> to the draft based on the input at the BoF in Beijing and follow-up
discussion.
> The new draft can be found at
<http://www.ietf.org/internet-drafts/draft-ietf-
> genarea-datatracker-community-02.txt>.
> 
> It might have been silly for me to try to track all the changes in
Appendix D, but
> some of y'all might want to check that I hit all the points given during
the BoF.
> 
> All input is still welcome. At some point soon, I will start some focused
threads,
> but feel free to start your own.
> 
> --Paul Hoffman, Director
> --VPN Consortium
> _______________________________________________
> datatracker-rqmts mailing list
> datatracker-rqmts@ietf.org
> https://www.ietf.org/mailman/listinfo/datatracker-rqmts


From paul.hoffman@vpnc.org  Mon Nov 22 16:06:38 2010
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 8CBD228C155 for <datatracker-rqmts@core3.amsl.com>; Mon, 22 Nov 2010 16:06:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.861
X-Spam-Level: 
X-Spam-Status: No, score=-99.861 tagged_above=-999 required=5 tests=[AWL=-0.456, BAYES_40=-0.185, 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 KwUungM7s8WA for <datatracker-rqmts@core3.amsl.com>; Mon, 22 Nov 2010 16:06:37 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 791253A68F9 for <datatracker-rqmts@ietf.org>; Mon, 22 Nov 2010 16:06:37 -0800 (PST)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAN07TMD051420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Nov 2010 17:07:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624082fc910b3a4d80c@[10.20.30.150]>
In-Reply-To: <003101cb8a17$6faeaaf0$4f0c00d0$@augustcellars.com>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com> <001f01cb8541$cbe593e0$63b0bba0$@augustcellars.com> <p06240802c90f9c1d813c@[10.20.30.150]> <003101cb8a17$6faeaaf0$4f0c00d0$@augustcellars.com>
Date: Mon, 22 Nov 2010 16:07:28 -0800
To: "Jim Schaad" <ietf@augustcellars.com>, <datatracker-rqmts@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [datatracker-rqmts] Community Datatracker draft -02
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, 23 Nov 2010 00:06:38 -0000

At 11:32 PM -0800 11/21/10, Jim Schaad wrote:
>1.  Is there perhaps a requirement for some type of mathematics of the
>lists?   We currently have unions - i.e. make me a list of lists.  I don't
>know that I can think of any good reason to have intersections (i.e. in all
>of the following lists), but I can think that the subtraction operation
>might be very useful.  I care about everything that this working group does
>EXCEPT for the following documents.

That seems pretty obscure and would have a difficult interface.

>2.  In section 2.1.6, I am wondering if I can put a list instead of a
>particular RFC or particular draft in some of the locations?  I.e. can I get
>a list of all of the drafts/rfcs that are referenced by the drafts/rfcs in
>this list?  I can see it as being useful for some type of background
>processing.  I.e. I need to figure out which drafts or RFCs I might care
>about reading because they relate to the current set of drafts that I am
>tracking.

That, too, seems pretty obscure. What does "relates to" mean in this context?

>3.  Section 2.2.2 - This section does not match exactly what I remember from
>the discussion.  I remember that it should be possible to create an atom
>feed that specifies exactly which events are to be sent.  (OK - I see this
>in the open issue list.)

Right: it is an open issue for display, Atom, and mailing lists. It seems tractable to me, but I want to hear more from the group before adding it.

>4. In Section 2.3.1 - You have a requirement that the display should only
>show a single draft once.  Does the same requirement also apply to the atom
>and e-mail feeds?

Not currently, but it could. Thoughts?

>5.  In section 2.3.3 - you talk about having the flag on a draft in a list.
>Do you really mean list or view of a list?  What happens if you have
>multiple flags because the draft appears in multiple lists?

Good catch. I think I mean in the view of the list. Otherwise, the user would lose information when they put different dates on the draft and the Datatracker only shows them one of the records.

>6.  In appendix B - It might be better to have a set of "pre-defined" lists
>that are owned by tools team (or some such group) that contain the set of
>good pre-defined lists that people want to see.  Such as:
>  WG - Std track documents
>  WG - Non-std track documents
>  WG - Agenda documents for next meeting.
>  ....

Not sure where this goes in Appendix B.

--Paul Hoffman, Director
--VPN Consortium

From ietf@augustcellars.com  Mon Nov 22 17:57:27 2010
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 B320F3A6ABA for <datatracker-rqmts@core3.amsl.com>; Mon, 22 Nov 2010 17:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.429
X-Spam-Level: 
X-Spam-Status: No, score=-2.429 tagged_above=-999 required=5 tests=[AWL=-0.057, 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 et2AAhxNfiOT for <datatracker-rqmts@core3.amsl.com>; Mon, 22 Nov 2010 17:57:26 -0800 (PST)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.173]) by core3.amsl.com (Postfix) with ESMTP id E6D583A6912 for <datatracker-rqmts@ietf.org>; Mon, 22 Nov 2010 17:57:26 -0800 (PST)
Received: from TITUS (unknown [207.202.179.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTP id C24E77B63; Mon, 22 Nov 2010 17:58:20 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>, <datatracker-rqmts@ietf.org>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com> <001f01cb8541$cbe593e0$63b0bba0$@augustcellars.com> <p06240802c90f9c1d813c@[10.20.30.150]> <003101cb8a17$6faeaaf0$4f0c00d0$@augustcellars.com> <p0624082fc910b3a4d80c@[10.20.30.150]>
In-Reply-To: <p0624082fc910b3a4d80c@[10.20.30.150]>
Date: Mon, 22 Nov 2010 18:10:44 -0800
Message-ID: <009501cb8ab3$c3b5ed10$4b21c730$@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+Y3kZx1QsKT7FjIQKCUTwEAeo0jB8Cp4rtvQFW0/97AjJGVDuTc26k8A==
Content-Language: en-us
Subject: Re: [datatracker-rqmts] Community Datatracker draft -02
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, 23 Nov 2010 01:57:27 -0000

> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org]
> Sent: Monday, November 22, 2010 4:07 PM
> To: Jim Schaad; datatracker-rqmts@ietf.org
> Subject: Re: [datatracker-rqmts] Community Datatracker draft -02
> 
> At 11:32 PM -0800 11/21/10, Jim Schaad wrote:
> >1.  Is there perhaps a requirement for some type of mathematics of the
> >lists?   We currently have unions - i.e. make me a list of lists.  I
don't
> >know that I can think of any good reason to have intersections (i.e. in
> >all of the following lists), but I can think that the subtraction
> >operation might be very useful.  I care about everything that this
> >working group does EXCEPT for the following documents.
> 
> That seems pretty obscure and would have a difficult interface.
> 
> >2.  In section 2.1.6, I am wondering if I can put a list instead of a
> >particular RFC or particular draft in some of the locations?  I.e. can
> >I get a list of all of the drafts/rfcs that are referenced by the
> >drafts/rfcs in this list?  I can see it as being useful for some type
> >of background processing.  I.e. I need to figure out which drafts or
> >RFCs I might care about reading because they relate to the current set
> >of drafts that I am tracking.
> 
> That, too, seems pretty obscure. What does "relates to" mean in this
context?

What I was looking at was starting with the statement

   o  All drafts that are referenced by a particular draft

But what I would like to do is to say
   All drafts that are referenced by any draft on list <XXXX>


> 
> >3.  Section 2.2.2 - This section does not match exactly what I remember
> >from the discussion.  I remember that it should be possible to create
> >an atom feed that specifies exactly which events are to be sent.  (OK -
> >I see this in the open issue list.)
> 
> Right: it is an open issue for display, Atom, and mailing lists. It seems
tractable
> to me, but I want to hear more from the group before adding it.
> 
> >4. In Section 2.3.1 - You have a requirement that the display should
> >only show a single draft once.  Does the same requirement also apply to
> >the atom and e-mail feeds?
> 
> Not currently, but it could. Thoughts?

I would like not get the same message multiple times on a single document.
I think this would encourage my SPAM filters to think this is a spam sender.

> 
> >5.  In section 2.3.3 - you talk about having the flag on a draft in a
list.
> >Do you really mean list or view of a list?  What happens if you have
> >multiple flags because the draft appears in multiple lists?
> 
> Good catch. I think I mean in the view of the list. Otherwise, the user
would lose
> information when they put different dates on the draft and the Datatracker
> only shows them one of the records.
> 
> >6.  In appendix B - It might be better to have a set of "pre-defined"
> >lists that are owned by tools team (or some such group) that contain
> >the set of good pre-defined lists that people want to see.  Such as:
> >  WG - Std track documents
> >  WG - Non-std track documents
> >  WG - Agenda documents for next meeting.
> >  ....
> 
> Not sure where this goes in Appendix B.

Ok - I think that this may not go into appendix B, but would be a part of
2.1.6 except for the last item.  The thing that triggered this in my mind
was the comment on scraping agendas for the last bullet in Appendix B

jim
> 
> --Paul Hoffman, Director
> --VPN Consortium


From kivinen@iki.fi  Tue Nov 23 06:00:16 2010
Return-Path: <kivinen@iki.fi>
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 5AC5628C0CE for <datatracker-rqmts@core3.amsl.com>; Tue, 23 Nov 2010 06:00:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_00=-2.599, 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 KNoCxkc7NMgy for <datatracker-rqmts@core3.amsl.com>; Tue, 23 Nov 2010 06:00:15 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) by core3.amsl.com (Postfix) with ESMTP id CF49A3A694D for <datatracker-rqmts@ietf.org>; Tue, 23 Nov 2010 06:00:13 -0800 (PST)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.3/8.14.3) with ESMTP id oANE14Z7016814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2010 16:01:04 +0200 (EET)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.3/8.12.11) id oANE12FR024637; Tue, 23 Nov 2010 16:01:02 +0200 (EET)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19691.51486.796097.922172@fireball.kivinen.iki.fi>
Date: Tue, 23 Nov 2010 16:01:02 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: "Jim Schaad" <ietf@augustcellars.com>
In-Reply-To: <009501cb8ab3$c3b5ed10$4b21c730$@augustcellars.com>
References: <069201cb84a5$f3600e60$da202b20$@augustcellars.com> <4CE18751.7030002@gmail.com> <001f01cb8541$cbe593e0$63b0bba0$@augustcellars.com> <p06240802c90f9c1d813c@[10.20.30.150]> <003101cb8a17$6faeaaf0$4f0c00d0$@augustcellars.com> <p0624082fc910b3a4d80c@[10.20.30.150]> <009501cb8ab3$c3b5ed10$4b21c730$@augustcellars.com>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 9 min
X-Total-Time: 10 min
Cc: datatracker-rqmts@ietf.org, 'Paul Hoffman' <paul.hoffman@vpnc.org>
Subject: Re: [datatracker-rqmts] Community Datatracker draft -02
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, 23 Nov 2010 14:00:16 -0000

> > >1.  Is there perhaps a requirement for some type of mathematics of the
> > >lists?   We currently have unions - i.e. make me a list of lists.  I
> don't
> > >know that I can think of any good reason to have intersections (i.e. in
> > >all of the following lists), but I can think that the subtraction
> > >operation might be very useful.  I care about everything that this
> > >working group does EXCEPT for the following documents.
> > 
> > That seems pretty obscure and would have a difficult interface.

I do not think it is going to be any more obscure than having union of
two lists would be. I.e. if you have a way to take list1 and list2 and
generate new list3 which is union of those two lists, I do not really
see that big difference if there is a way to make new list by
substracting list2 from list1.

User interface could simply be:

	List A: [                         ]
	List B: [                         ]
	Operation: ( ) Union ( ) Intersection ( ) Substraction

Where the lists are list ids (or urls or whetever) and operation is
radiobutton.

Those people who really want to get such lists usually do understand
enough to make use of such features.

In some working groups there charter items which I am not that
interested in, and I would like to create list having drafts in that
WG except those relating charter item x (which would mean it would be
nice to have WG chair keeping up list of drafts per charter item). 
-- 
kivinen@iki.fi
