
From paul.hoffman@vpnc.org  Tue Dec  7 18:37:32 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 0F2C03A6848 for <datatracker-rqmts@core3.amsl.com>; Tue,  7 Dec 2010 18:37:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.427
X-Spam-Level: 
X-Spam-Status: No, score=-101.427 tagged_above=-999 required=5 tests=[AWL=0.619, BAYES_00=-2.599, 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 XOvi5XgB4JRs for <datatracker-rqmts@core3.amsl.com>; Tue,  7 Dec 2010 18:37:30 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 3B84E3A6825 for <datatracker-rqmts@ietf.org>; Tue,  7 Dec 2010 18:37:30 -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 oB82ctET039589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Tue, 7 Dec 2010 19:38:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624081bc9249d506bb8@[10.20.30.150]>
Date: Tue, 7 Dec 2010 18:36:12 -0800
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Publicly-readable and private/anonymous 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, 08 Dec 2010 02:37:32 -0000

Greetings again. It's time to spin up this list again, and a few people have told me that specifying how public lists are publicly-readable and how private/anonymous lists are created and managed will unblock a bunch of other open issues. There was a lot of interest in these topics at the mic in Beijing.

The current text is below. This is just starting text, and it doesn't cover the idea that some private/anonymous lists might have publicly-readable counterparts if the list owner wants.

So, please say what you think should be done here. Do you have a preference between private and anonymous? Do you have ideas for public lists?

To facilitate the discussion, there will be a WebEx-based telechat on Friday, December 17. Information on that comes in the next message. If we have great consensus before the telechat, we can use that time to move on other open issues.

--Paul Hoffman

======================================

2.1.3.  Requirement: Some lists must be able to be private or anonymous

   Seeing a list of drafts that covers multiple areas of interest can
   tell you something about the person who created the list.  For
   example, you might be able to guess that they might be looking for a
   job in a different field by looking at their list of drafts of
   interest.  Of course, anyone can follow individual drafts today
   without having that be exposed; however, following a particular group
   of drafts can reveal information about a person.

   There is a open issue about whether lists should be default be
   private/anonymous or public, and how that default should be manifest
   in the eventual UI for creating lists.

   The first proposed methods that might keep lists private/anonymous
   are:

   o  Private lists might only be available using passwords or some
      other common authentication mechanism.  This would require that
      the Datatracker have a subscription process for users that could
      assign passwords, and a per-user process for adding lists to a
      user account.  (If the current Datatracker username and login
      scheme is used, the interface needs to be improved so that getting
      a new login, and changing one's password, are significantly
      easier.)
   o  Anonymous lists might be assigned random URLs from a very large
      (2^128) namespace, and the user who creates a list does not tell
      others the assigned URL.  This method makes it impossible for
      someone to search the entire set of assigned lists.  Given that
      the URLs for lists are most likely going to be copy-and-pasted
      anyway, having long random strings in the list's URL is not an
      impediment.

2.1.4.  Requirement: It must be easy for IETF leadership and individuals
        to make lists they create publicly-readable

   Private or anonymous lists are fine for individuals, but publicly-
   readable lists can magnify the value to the whole community.  In
   fact, some early commenters on this document emphasized that
   publicly-readable lists will be more valuable to the IETF than
   helping individuals track documents that are only of interest to
   them.

   Probably the easiest method to implement publicly-readable lists is
   to make them read-only aliases for private or anonymous lists.  This
   would allow the list originators to control the contents of the list
   as normal, but also allow anyone to view the results in the
   Datatracker and/or subscribe to notifications.  There may be other
   methods that would also make sense, and this section might change in
   the future.

   Publicly-readable lists should have short URLs that can be
   transcribed without relying on copy-and-paste.  The names in the URLs
   for lists that are associated with IETF activities (initially, the
   lists created by WG chairs and ADs) can be mnemonic, but other public
   lists should have names that are not mnemonic in order to prevent
   name-squatting.

   It is important to note that publicly-readable lists can only be
   changed by the owners.  Allowing many people to change the contents
   of a list would probably lead to lists that are not very useful to
   typical users.

   Proposed later requirements include having the Datatracker list all
   of the publicly-readable lists (or certainly at least the ones
   associated with IETF activities), and having links from WG pages in
   Datatracker to the publicly-readable lists maintained by the WG
   chairs.

From paul.hoffman@vpnc.org  Tue Dec  7 18:37:33 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 45E393A6825 for <datatracker-rqmts@core3.amsl.com>; Tue,  7 Dec 2010 18:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.046
X-Spam-Level: 
X-Spam-Status: No, score=-104.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, 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 2Q3ieEtfeegS for <datatracker-rqmts@core3.amsl.com>; Tue,  7 Dec 2010 18:37:31 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id C4C133A682B for <datatracker-rqmts@ietf.org>; Tue,  7 Dec 2010 18:37:30 -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 oB82ctEV039589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Tue, 7 Dec 2010 19:38:57 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624081cc9249faef9b4@[10.20.30.150]>
Date: Tue, 7 Dec 2010 18:38:45 -0800
To: datatracker-rqmts@ietf.org
From: IETF Secretariat <messenger@webex.com> (by way of Paul Hoffman)
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Meeting invitation: iddtspec BoF Discussion
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, 08 Dec 2010 02:37:33 -0000

IETF Secretariat invites you to attend this online meeting.

Topic: iddtspec BoF Discussion
Date: Friday, December 17, 2010
Time: 8:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 964 770 156
Meeting Password: (This meeting does not require a password.)


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/j.php?ED=149351167&UID=1195259162&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting does not require a password.)
4. Click "Join".

To view in other time zones or languages, please click the link:
https://workgreen.webex.com/workgreen/j.php?ED=149351167&UID=1195259162&ORT=MiM0

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): 1-866-699-3239
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers: https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=149351167&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

Access code:964 770 156

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to <https://workgreen.webex.com/workgreen/mc>https://workgreen.webex.com/workgreen/mc
2. On the left navigation bar, click "Support".

You can contact me at:
amorris@amsl.com
1-510-492-4081

To add this meeting to your calendar program (for example Microsoft Outlook), click this link:
https://workgreen.webex.com/workgreen/j.php?ED=149351167&UID=1195259162&ICS=MI&LD=1&RD=2&ST=1&SHA2=PAMxj3WrOOG0DZ0TbZPOzTaGfbquqHbFt3ucwwqZ-ao=&RT=MiM0

The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://workgreen.webex.com/workgreen/systemdiagnosis.php

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x964770156#

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.

From ietf@augustcellars.com  Tue Dec  7 21:13:19 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 567A13A68D3 for <datatracker-rqmts@core3.amsl.com>; Tue,  7 Dec 2010 21:13:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
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 YtghW7NS6ZZm for <datatracker-rqmts@core3.amsl.com>; Tue,  7 Dec 2010 21:13:18 -0800 (PST)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by core3.amsl.com (Postfix) with ESMTP id 805F23A68C5 for <datatracker-rqmts@ietf.org>; Tue,  7 Dec 2010 21:13:18 -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 BE0006EF58 for <datatracker-rqmts@ietf.org>; Tue,  7 Dec 2010 21:14:36 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <datatracker-rqmts@ietf.org>
Date: Tue, 7 Dec 2010 21:29:26 -0800
Message-ID: <011101cb9698$e18cfd60$a4a6f820$@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: AcuWmG8xIMi0YaQPQ8ehLRDMG8wYWg==
Content-Language: en-us
Subject: [datatracker-rqmts] Filter based on presence of specific sections
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, 08 Dec 2010 05:13:19 -0000

Paul,

I am not sure how this requirement really needs to be specified, but I think
it might be of interest to a number of people including myself.

I would like to be able to filter based on the presence of specific sections
in the document.  I would like to be able to find out if an ASN.1 module
exists in a document, but I am sure that the MIB doctors might want to have
the same type of thing.  It might be useful to somehow know which documents
have "significant" IANA considerations sections.

It might be that filtering based on the presence of specific key words is
sufficient to do this, but only if we really start using some type of
standardized section titles.

Jim



From henrik@levkowetz.com  Wed Dec  8 02:25:22 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 958A03A68F5 for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 02:25:16 -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, 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 bIHJvqG0CjeJ for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 02:25:03 -0800 (PST)
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 8182D3A68BD for <datatracker-rqmts@ietf.org>; Wed,  8 Dec 2010 02:25:01 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:57750 helo=dyn-fg124.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 1PQHDb-0005Fh-2i; Wed, 08 Dec 2010 11:25:56 +0100
Message-ID: <4CFF5D2E.1080507@levkowetz.com>
Date: Wed, 08 Dec 2010 11:25:50 +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: <p0624081bc9249d506bb8@[10.20.30.150]>
In-Reply-To: <p0624081bc9249d506bb8@[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, 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] Publicly-readable and private/anonymous 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, 08 Dec 2010 10:25:22 -0000

Hi Paul,

Looking this over, both specification and implementation of these
notification specifications ('lists') seems to becoming more and
more complex, and I'm not convinced that the complexity buys us a
lot.  The whole issue comes about because of the decision that
people should be able to include another list in their notification
list.

I would like to do away with the whole complexity of this by saying
(at least for this round -- we can always re-open this again when
we have some practical experience with the first implementation) --
by saying that lists can't include other lists, and all lists are
anonymous and unpublished.


Regards,

	Henrik

On 2010-12-08 03:36 Paul Hoffman said:
> Greetings again. It's time to spin up this list again, and a few people have told me that specifying how public lists are publicly-readable and how private/anonymous lists are created and managed will unblock a bunch of other open issues. There was a lot of interest in these topics at the mic in Beijing.
> 
> The current text is below. This is just starting text, and it doesn't cover the idea that some private/anonymous lists might have publicly-readable counterparts if the list owner wants.
> 
> So, please say what you think should be done here. Do you have a preference between private and anonymous? Do you have ideas for public lists?
> 
> To facilitate the discussion, there will be a WebEx-based telechat on Friday, December 17. Information on that comes in the next message. If we have great consensus before the telechat, we can use that time to move on other open issues.
> 
> --Paul Hoffman
> 
> ======================================
> 
> 2.1.3.  Requirement: Some lists must be able to be private or anonymous
> 
>    Seeing a list of drafts that covers multiple areas of interest can
>    tell you something about the person who created the list.  For
>    example, you might be able to guess that they might be looking for a
>    job in a different field by looking at their list of drafts of
>    interest.  Of course, anyone can follow individual drafts today
>    without having that be exposed; however, following a particular group
>    of drafts can reveal information about a person.
> 
>    There is a open issue about whether lists should be default be
>    private/anonymous or public, and how that default should be manifest
>    in the eventual UI for creating lists.
> 
>    The first proposed methods that might keep lists private/anonymous
>    are:
> 
>    o  Private lists might only be available using passwords or some
>       other common authentication mechanism.  This would require that
>       the Datatracker have a subscription process for users that could
>       assign passwords, and a per-user process for adding lists to a
>       user account.  (If the current Datatracker username and login
>       scheme is used, the interface needs to be improved so that getting
>       a new login, and changing one's password, are significantly
>       easier.)
>    o  Anonymous lists might be assigned random URLs from a very large
>       (2^128) namespace, and the user who creates a list does not tell
>       others the assigned URL.  This method makes it impossible for
>       someone to search the entire set of assigned lists.  Given that
>       the URLs for lists are most likely going to be copy-and-pasted
>       anyway, having long random strings in the list's URL is not an
>       impediment.
> 
> 2.1.4.  Requirement: It must be easy for IETF leadership and individuals
>         to make lists they create publicly-readable
> 
>    Private or anonymous lists are fine for individuals, but publicly-
>    readable lists can magnify the value to the whole community.  In
>    fact, some early commenters on this document emphasized that
>    publicly-readable lists will be more valuable to the IETF than
>    helping individuals track documents that are only of interest to
>    them.
> 
>    Probably the easiest method to implement publicly-readable lists is
>    to make them read-only aliases for private or anonymous lists.  This
>    would allow the list originators to control the contents of the list
>    as normal, but also allow anyone to view the results in the
>    Datatracker and/or subscribe to notifications.  There may be other
>    methods that would also make sense, and this section might change in
>    the future.
> 
>    Publicly-readable lists should have short URLs that can be
>    transcribed without relying on copy-and-paste.  The names in the URLs
>    for lists that are associated with IETF activities (initially, the
>    lists created by WG chairs and ADs) can be mnemonic, but other public
>    lists should have names that are not mnemonic in order to prevent
>    name-squatting.
> 
>    It is important to note that publicly-readable lists can only be
>    changed by the owners.  Allowing many people to change the contents
>    of a list would probably lead to lists that are not very useful to
>    typical users.
> 
>    Proposed later requirements include having the Datatracker list all
>    of the publicly-readable lists (or certainly at least the ones
>    associated with IETF activities), and having links from WG pages in
>    Datatracker to the publicly-readable lists maintained by the WG
>    chairs.
> _______________________________________________
> datatracker-rqmts mailing list
> datatracker-rqmts@ietf.org
> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> 

From housley@vigilsec.com  Wed Dec  8 11:07:55 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 7B5FE3A6993 for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 11:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level: 
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=-0.064, 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 GdMsDiM-l37C for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 11:07:52 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 0FBB13A686A for <datatracker-rqmts@ietf.org>; Wed,  8 Dec 2010 11:07:50 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 886E69A47A8; Wed,  8 Dec 2010 14:09:42 -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 9rQttmaY6NvG; Wed,  8 Dec 2010 14:09:04 -0500 (EST)
Received: from [128.31.34.232] (31-34-232.wireless.csail.mit.edu [128.31.34.232]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2BC809A47A6; Wed,  8 Dec 2010 14:09:41 -0500 (EST)
Message-ID: <4CFFD7E2.7060307@vigilsec.com>
Date: Wed, 08 Dec 2010 14:09:22 -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: Henrik Levkowetz <henrik@levkowetz.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]> <4CFF5D2E.1080507@levkowetz.com>
In-Reply-To: <4CFF5D2E.1080507@levkowetz.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous 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, 08 Dec 2010 19:07:55 -0000

Henrik:

I agree that lists of lists is causing more complexity than expected.  I
think that putting it aside for now is a good choice.

I wonder if it would be easier to start with two kinds of lists:
  --  public-and-published
  --  private-and-unpublished

The public-and-published are used to follow the documents associated
with a particular topic.  They have a public owner that has agreed to
add and remove documents as appropriate.  This is like the web page that
shows the possible WG and non-WG mail lists that are available to IETF
participants.

The private-and-unpublished are part of a single user's preferences.
They are not shared, and they are owned by that user.  Each user gets
one and only one of them.

Russ

On 12/8/2010 5:25 AM, Henrik Levkowetz wrote:
> Hi Paul,
> 
> Looking this over, both specification and implementation of these
> notification specifications ('lists') seems to becoming more and
> more complex, and I'm not convinced that the complexity buys us a
> lot.  The whole issue comes about because of the decision that
> people should be able to include another list in their notification
> list.
> 
> I would like to do away with the whole complexity of this by saying
> (at least for this round -- we can always re-open this again when
> we have some practical experience with the first implementation) --
> by saying that lists can't include other lists, and all lists are
> anonymous and unpublished.
> 
> 
> Regards,
> 
> 	Henrik
> 
> On 2010-12-08 03:36 Paul Hoffman said:
>> Greetings again. It's time to spin up this list again, and a few people have told me that specifying how public lists are publicly-readable and how private/anonymous lists are created and managed will unblock a bunch of other open issues. There was a lot of interest in these topics at the mic in Beijing.
>>
>> The current text is below. This is just starting text, and it doesn't cover the idea that some private/anonymous lists might have publicly-readable counterparts if the list owner wants.
>>
>> So, please say what you think should be done here. Do you have a preference between private and anonymous? Do you have ideas for public lists?
>>
>> To facilitate the discussion, there will be a WebEx-based telechat on Friday, December 17. Information on that comes in the next message. If we have great consensus before the telechat, we can use that time to move on other open issues.
>>
>> --Paul Hoffman
>>
>> ======================================
>>
>> 2.1.3.  Requirement: Some lists must be able to be private or anonymous
>>
>>    Seeing a list of drafts that covers multiple areas of interest can
>>    tell you something about the person who created the list.  For
>>    example, you might be able to guess that they might be looking for a
>>    job in a different field by looking at their list of drafts of
>>    interest.  Of course, anyone can follow individual drafts today
>>    without having that be exposed; however, following a particular group
>>    of drafts can reveal information about a person.
>>
>>    There is a open issue about whether lists should be default be
>>    private/anonymous or public, and how that default should be manifest
>>    in the eventual UI for creating lists.
>>
>>    The first proposed methods that might keep lists private/anonymous
>>    are:
>>
>>    o  Private lists might only be available using passwords or some
>>       other common authentication mechanism.  This would require that
>>       the Datatracker have a subscription process for users that could
>>       assign passwords, and a per-user process for adding lists to a
>>       user account.  (If the current Datatracker username and login
>>       scheme is used, the interface needs to be improved so that getting
>>       a new login, and changing one's password, are significantly
>>       easier.)
>>    o  Anonymous lists might be assigned random URLs from a very large
>>       (2^128) namespace, and the user who creates a list does not tell
>>       others the assigned URL.  This method makes it impossible for
>>       someone to search the entire set of assigned lists.  Given that
>>       the URLs for lists are most likely going to be copy-and-pasted
>>       anyway, having long random strings in the list's URL is not an
>>       impediment.
>>
>> 2.1.4.  Requirement: It must be easy for IETF leadership and individuals
>>         to make lists they create publicly-readable
>>
>>    Private or anonymous lists are fine for individuals, but publicly-
>>    readable lists can magnify the value to the whole community.  In
>>    fact, some early commenters on this document emphasized that
>>    publicly-readable lists will be more valuable to the IETF than
>>    helping individuals track documents that are only of interest to
>>    them.
>>
>>    Probably the easiest method to implement publicly-readable lists is
>>    to make them read-only aliases for private or anonymous lists.  This
>>    would allow the list originators to control the contents of the list
>>    as normal, but also allow anyone to view the results in the
>>    Datatracker and/or subscribe to notifications.  There may be other
>>    methods that would also make sense, and this section might change in
>>    the future.
>>
>>    Publicly-readable lists should have short URLs that can be
>>    transcribed without relying on copy-and-paste.  The names in the URLs
>>    for lists that are associated with IETF activities (initially, the
>>    lists created by WG chairs and ADs) can be mnemonic, but other public
>>    lists should have names that are not mnemonic in order to prevent
>>    name-squatting.
>>
>>    It is important to note that publicly-readable lists can only be
>>    changed by the owners.  Allowing many people to change the contents
>>    of a list would probably lead to lists that are not very useful to
>>    typical users.
>>
>>    Proposed later requirements include having the Datatracker list all
>>    of the publicly-readable lists (or certainly at least the ones
>>    associated with IETF activities), and having links from WG pages in
>>    Datatracker to the publicly-readable lists maintained by the WG
>>    chairs.
>> _______________________________________________
>> datatracker-rqmts mailing list
>> datatracker-rqmts@ietf.org
>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>
> _______________________________________________
> datatracker-rqmts mailing list
> datatracker-rqmts@ietf.org
> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> 

From ietf@augustcellars.com  Wed Dec  8 13:59: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 BE95E3A686B for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 13:59:40 -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 lCED2dI0943N for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 13:59:39 -0800 (PST)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by core3.amsl.com (Postfix) with ESMTP id 9A9A63A689F for <datatracker-rqmts@ietf.org>; Wed,  8 Dec 2010 13:59:39 -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 A725C6EF75; Wed,  8 Dec 2010 14:01:06 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Russ Housley'" <housley@vigilsec.com>, "'Henrik Levkowetz'" <henrik@levkowetz.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]>	<4CFF5D2E.1080507@levkowetz.com> <4CFFD7E2.7060307@vigilsec.com>
In-Reply-To: <4CFFD7E2.7060307@vigilsec.com>
Date: Wed, 8 Dec 2010 14:15:59 -0800
Message-ID: <015d01cb9725$7fba21c0$7f2e6540$@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: AQJ260A0gDDsotZc4IfkOuXcUkJNOQFJSwvjAsZA1kySH/f2UA==
Content-Language: en-us
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous	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, 08 Dec 2010 21:59:40 -0000

Russ,

I don't think you really want to restrict me to a single list.  This would
just require that I create multiple logins in order to get multiple lists.

Jim


> -----Original Message-----
> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
> bounces@ietf.org] On Behalf Of Russ Housley
> Sent: Wednesday, December 08, 2010 11:09 AM
> To: Henrik Levkowetz
> Cc: datatracker-rqmts@ietf.org
> Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous
lists
> 
> Henrik:
> 
> I agree that lists of lists is causing more complexity than expected.  I
think that
> putting it aside for now is a good choice.
> 
> I wonder if it would be easier to start with two kinds of lists:
>   --  public-and-published
>   --  private-and-unpublished
> 
> The public-and-published are used to follow the documents associated with
a
> particular topic.  They have a public owner that has agreed to add and
remove
> documents as appropriate.  This is like the web page that shows the
possible
> WG and non-WG mail lists that are available to IETF participants.
> 
> The private-and-unpublished are part of a single user's preferences.
> They are not shared, and they are owned by that user.  Each user gets one
and
> only one of them.
> 
> Russ
> 
> On 12/8/2010 5:25 AM, Henrik Levkowetz wrote:
> > Hi Paul,
> >
> > Looking this over, both specification and implementation of these
> > notification specifications ('lists') seems to becoming more and more
> > complex, and I'm not convinced that the complexity buys us a lot.  The
> > whole issue comes about because of the decision that people should be
> > able to include another list in their notification list.
> >
> > I would like to do away with the whole complexity of this by saying
> > (at least for this round -- we can always re-open this again when we
> > have some practical experience with the first implementation) -- by
> > saying that lists can't include other lists, and all lists are
> > anonymous and unpublished.
> >
> >
> > Regards,
> >
> > 	Henrik
> >
> > On 2010-12-08 03:36 Paul Hoffman said:
> >> Greetings again. It's time to spin up this list again, and a few people
have
> told me that specifying how public lists are publicly-readable and how
> private/anonymous lists are created and managed will unblock a bunch of
> other open issues. There was a lot of interest in these topics at the mic
in
> Beijing.
> >>
> >> The current text is below. This is just starting text, and it doesn't
cover the
> idea that some private/anonymous lists might have publicly-readable
> counterparts if the list owner wants.
> >>
> >> So, please say what you think should be done here. Do you have a
> preference between private and anonymous? Do you have ideas for public
lists?
> >>
> >> To facilitate the discussion, there will be a WebEx-based telechat on
Friday,
> December 17. Information on that comes in the next message. If we have
great
> consensus before the telechat, we can use that time to move on other open
> issues.
> >>
> >> --Paul Hoffman
> >>
> >> ======================================
> >>
> >> 2.1.3.  Requirement: Some lists must be able to be private or
> >> anonymous
> >>
> >>    Seeing a list of drafts that covers multiple areas of interest can
> >>    tell you something about the person who created the list.  For
> >>    example, you might be able to guess that they might be looking for a
> >>    job in a different field by looking at their list of drafts of
> >>    interest.  Of course, anyone can follow individual drafts today
> >>    without having that be exposed; however, following a particular
group
> >>    of drafts can reveal information about a person.
> >>
> >>    There is a open issue about whether lists should be default be
> >>    private/anonymous or public, and how that default should be manifest
> >>    in the eventual UI for creating lists.
> >>
> >>    The first proposed methods that might keep lists private/anonymous
> >>    are:
> >>
> >>    o  Private lists might only be available using passwords or some
> >>       other common authentication mechanism.  This would require that
> >>       the Datatracker have a subscription process for users that could
> >>       assign passwords, and a per-user process for adding lists to a
> >>       user account.  (If the current Datatracker username and login
> >>       scheme is used, the interface needs to be improved so that
getting
> >>       a new login, and changing one's password, are significantly
> >>       easier.)
> >>    o  Anonymous lists might be assigned random URLs from a very large
> >>       (2^128) namespace, and the user who creates a list does not tell
> >>       others the assigned URL.  This method makes it impossible for
> >>       someone to search the entire set of assigned lists.  Given that
> >>       the URLs for lists are most likely going to be copy-and-pasted
> >>       anyway, having long random strings in the list's URL is not an
> >>       impediment.
> >>
> >> 2.1.4.  Requirement: It must be easy for IETF leadership and
individuals
> >>         to make lists they create publicly-readable
> >>
> >>    Private or anonymous lists are fine for individuals, but publicly-
> >>    readable lists can magnify the value to the whole community.  In
> >>    fact, some early commenters on this document emphasized that
> >>    publicly-readable lists will be more valuable to the IETF than
> >>    helping individuals track documents that are only of interest to
> >>    them.
> >>
> >>    Probably the easiest method to implement publicly-readable lists is
> >>    to make them read-only aliases for private or anonymous lists.  This
> >>    would allow the list originators to control the contents of the list
> >>    as normal, but also allow anyone to view the results in the
> >>    Datatracker and/or subscribe to notifications.  There may be other
> >>    methods that would also make sense, and this section might change in
> >>    the future.
> >>
> >>    Publicly-readable lists should have short URLs that can be
> >>    transcribed without relying on copy-and-paste.  The names in the
URLs
> >>    for lists that are associated with IETF activities (initially, the
> >>    lists created by WG chairs and ADs) can be mnemonic, but other
public
> >>    lists should have names that are not mnemonic in order to prevent
> >>    name-squatting.
> >>
> >>    It is important to note that publicly-readable lists can only be
> >>    changed by the owners.  Allowing many people to change the contents
> >>    of a list would probably lead to lists that are not very useful to
> >>    typical users.
> >>
> >>    Proposed later requirements include having the Datatracker list all
> >>    of the publicly-readable lists (or certainly at least the ones
> >>    associated with IETF activities), and having links from WG pages in
> >>    Datatracker to the publicly-readable lists maintained by the WG
> >>    chairs.
> >> _______________________________________________
> >> datatracker-rqmts mailing list
> >> datatracker-rqmts@ietf.org
> >> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> >>
> > _______________________________________________
> > datatracker-rqmts mailing list
> > datatracker-rqmts@ietf.org
> > https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> >
> _______________________________________________
> datatracker-rqmts mailing list
> datatracker-rqmts@ietf.org
> https://www.ietf.org/mailman/listinfo/datatracker-rqmts


From paul.hoffman@vpnc.org  Wed Dec  8 14:13:16 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 8C1CF3A689F for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 14:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.591
X-Spam-Level: 
X-Spam-Status: No, score=-100.591 tagged_above=-999 required=5 tests=[AWL=-0.261, BAYES_05=-1.11, 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 TF98ueZzJBh4 for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 14:13:15 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 85D703A689E for <datatracker-rqmts@ietf.org>; Wed,  8 Dec 2010 14:13:15 -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 oB8MEctj089621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2010 15:14:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240808c925b39e15cb@[10.20.30.150]>
In-Reply-To: <015d01cb9725$7fba21c0$7f2e6540$@augustcellars.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]> <4CFF5D2E.1080507@levkowetz.com>	<4CFFD7E2.7060307@vigilsec.com> <015d01cb9725$7fba21c0$7f2e6540$@augustcellars.com>
Date: Wed, 8 Dec 2010 14:14:37 -0800
To: "Jim Schaad" <ietf@augustcellars.com>, "'Russ Housley'" <housley@vigilsec.com>, "'Henrik Levkowetz'" <henrik@levkowetz.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous 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, 08 Dec 2010 22:13:16 -0000

At 2:15 PM -0800 12/8/10, Jim Schaad wrote:
>I don't think you really want to restrict me to a single list.  This would
>just require that I create multiple logins in order to get multiple lists.

Not necessarily. The design could be "multiple lists per login".

--Paul Hoffman, Director
--VPN Consortium

From housley@vigilsec.com  Wed Dec  8 14:33:29 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 442203A69A4 for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 14:33:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.448
X-Spam-Level: 
X-Spam-Status: No, score=-102.448 tagged_above=-999 required=5 tests=[AWL=-0.076, 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 uSYqA1y8LbzL for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 14:33:28 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id AF6A33A698E for <datatracker-rqmts@ietf.org>; Wed,  8 Dec 2010 14:33:27 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 65FD39A4740; Wed,  8 Dec 2010 17:35:08 -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 oVwd0Bavej7p; Wed,  8 Dec 2010 17:34:41 -0500 (EST)
Received: from [128.31.34.232] (31-34-232.wireless.csail.mit.edu [128.31.34.232]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2821F9A47A6; Wed,  8 Dec 2010 17:35:06 -0500 (EST)
Message-ID: <4D000815.5090707@vigilsec.com>
Date: Wed, 08 Dec 2010 17:35: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: Jim Schaad <ietf@augustcellars.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]>	<4CFF5D2E.1080507@levkowetz.com> <4CFFD7E2.7060307@vigilsec.com> <015d01cb9725$7fba21c0$7f2e6540$@augustcellars.com>
In-Reply-To: <015d01cb9725$7fba21c0$7f2e6540$@augustcellars.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous	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, 08 Dec 2010 22:33:29 -0000

For what gain?  It is the list of documents you want to receive
notifications of changes.

Russ

On 12/8/2010 5:15 PM, Jim Schaad wrote:
> Russ,
> 
> I don't think you really want to restrict me to a single list.  This would
> just require that I create multiple logins in order to get multiple lists.
> 
> Jim
> 
> 
>> -----Original Message-----
>> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
>> bounces@ietf.org] On Behalf Of Russ Housley
>> Sent: Wednesday, December 08, 2010 11:09 AM
>> To: Henrik Levkowetz
>> Cc: datatracker-rqmts@ietf.org
>> Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous
> lists
>>
>> Henrik:
>>
>> I agree that lists of lists is causing more complexity than expected.  I
> think that
>> putting it aside for now is a good choice.
>>
>> I wonder if it would be easier to start with two kinds of lists:
>>   --  public-and-published
>>   --  private-and-unpublished
>>
>> The public-and-published are used to follow the documents associated with
> a
>> particular topic.  They have a public owner that has agreed to add and
> remove
>> documents as appropriate.  This is like the web page that shows the
> possible
>> WG and non-WG mail lists that are available to IETF participants.
>>
>> The private-and-unpublished are part of a single user's preferences.
>> They are not shared, and they are owned by that user.  Each user gets one
> and
>> only one of them.
>>
>> Russ
>>
>> On 12/8/2010 5:25 AM, Henrik Levkowetz wrote:
>>> Hi Paul,
>>>
>>> Looking this over, both specification and implementation of these
>>> notification specifications ('lists') seems to becoming more and more
>>> complex, and I'm not convinced that the complexity buys us a lot.  The
>>> whole issue comes about because of the decision that people should be
>>> able to include another list in their notification list.
>>>
>>> I would like to do away with the whole complexity of this by saying
>>> (at least for this round -- we can always re-open this again when we
>>> have some practical experience with the first implementation) -- by
>>> saying that lists can't include other lists, and all lists are
>>> anonymous and unpublished.
>>>
>>>
>>> Regards,
>>>
>>> 	Henrik
>>>
>>> On 2010-12-08 03:36 Paul Hoffman said:
>>>> Greetings again. It's time to spin up this list again, and a few people
> have
>> told me that specifying how public lists are publicly-readable and how
>> private/anonymous lists are created and managed will unblock a bunch of
>> other open issues. There was a lot of interest in these topics at the mic
> in
>> Beijing.
>>>>
>>>> The current text is below. This is just starting text, and it doesn't
> cover the
>> idea that some private/anonymous lists might have publicly-readable
>> counterparts if the list owner wants.
>>>>
>>>> So, please say what you think should be done here. Do you have a
>> preference between private and anonymous? Do you have ideas for public
> lists?
>>>>
>>>> To facilitate the discussion, there will be a WebEx-based telechat on
> Friday,
>> December 17. Information on that comes in the next message. If we have
> great
>> consensus before the telechat, we can use that time to move on other open
>> issues.
>>>>
>>>> --Paul Hoffman
>>>>
>>>> ======================================
>>>>
>>>> 2.1.3.  Requirement: Some lists must be able to be private or
>>>> anonymous
>>>>
>>>>    Seeing a list of drafts that covers multiple areas of interest can
>>>>    tell you something about the person who created the list.  For
>>>>    example, you might be able to guess that they might be looking for a
>>>>    job in a different field by looking at their list of drafts of
>>>>    interest.  Of course, anyone can follow individual drafts today
>>>>    without having that be exposed; however, following a particular
> group
>>>>    of drafts can reveal information about a person.
>>>>
>>>>    There is a open issue about whether lists should be default be
>>>>    private/anonymous or public, and how that default should be manifest
>>>>    in the eventual UI for creating lists.
>>>>
>>>>    The first proposed methods that might keep lists private/anonymous
>>>>    are:
>>>>
>>>>    o  Private lists might only be available using passwords or some
>>>>       other common authentication mechanism.  This would require that
>>>>       the Datatracker have a subscription process for users that could
>>>>       assign passwords, and a per-user process for adding lists to a
>>>>       user account.  (If the current Datatracker username and login
>>>>       scheme is used, the interface needs to be improved so that
> getting
>>>>       a new login, and changing one's password, are significantly
>>>>       easier.)
>>>>    o  Anonymous lists might be assigned random URLs from a very large
>>>>       (2^128) namespace, and the user who creates a list does not tell
>>>>       others the assigned URL.  This method makes it impossible for
>>>>       someone to search the entire set of assigned lists.  Given that
>>>>       the URLs for lists are most likely going to be copy-and-pasted
>>>>       anyway, having long random strings in the list's URL is not an
>>>>       impediment.
>>>>
>>>> 2.1.4.  Requirement: It must be easy for IETF leadership and
> individuals
>>>>         to make lists they create publicly-readable
>>>>
>>>>    Private or anonymous lists are fine for individuals, but publicly-
>>>>    readable lists can magnify the value to the whole community.  In
>>>>    fact, some early commenters on this document emphasized that
>>>>    publicly-readable lists will be more valuable to the IETF than
>>>>    helping individuals track documents that are only of interest to
>>>>    them.
>>>>
>>>>    Probably the easiest method to implement publicly-readable lists is
>>>>    to make them read-only aliases for private or anonymous lists.  This
>>>>    would allow the list originators to control the contents of the list
>>>>    as normal, but also allow anyone to view the results in the
>>>>    Datatracker and/or subscribe to notifications.  There may be other
>>>>    methods that would also make sense, and this section might change in
>>>>    the future.
>>>>
>>>>    Publicly-readable lists should have short URLs that can be
>>>>    transcribed without relying on copy-and-paste.  The names in the
> URLs
>>>>    for lists that are associated with IETF activities (initially, the
>>>>    lists created by WG chairs and ADs) can be mnemonic, but other
> public
>>>>    lists should have names that are not mnemonic in order to prevent
>>>>    name-squatting.
>>>>
>>>>    It is important to note that publicly-readable lists can only be
>>>>    changed by the owners.  Allowing many people to change the contents
>>>>    of a list would probably lead to lists that are not very useful to
>>>>    typical users.
>>>>
>>>>    Proposed later requirements include having the Datatracker list all
>>>>    of the publicly-readable lists (or certainly at least the ones
>>>>    associated with IETF activities), and having links from WG pages in
>>>>    Datatracker to the publicly-readable lists maintained by the WG
>>>>    chairs.
>>>> _______________________________________________
>>>> datatracker-rqmts mailing list
>>>> datatracker-rqmts@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>>>
>>> _______________________________________________
>>> datatracker-rqmts mailing list
>>> datatracker-rqmts@ietf.org
>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>>
>> _______________________________________________
>> datatracker-rqmts mailing list
>> datatracker-rqmts@ietf.org
>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> 
> 

From ietf@augustcellars.com  Wed Dec  8 23:40:33 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 7ADAB3A67BD for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 23:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.417
X-Spam-Level: 
X-Spam-Status: No, score=-2.417 tagged_above=-999 required=5 tests=[AWL=-0.045, 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 Sgx4CmTb751F for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 23:40:29 -0800 (PST)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by core3.amsl.com (Postfix) with ESMTP id C3B463A6851 for <datatracker-rqmts@ietf.org>; Wed,  8 Dec 2010 23:40: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 EF2C36EF79; Wed,  8 Dec 2010 23:41:57 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Henrik Levkowetz'" <henrik@levkowetz.com>, "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <p0624081bc9249d506bb8@[10.20.30.150]> <4CFF5D2E.1080507@levkowetz.com>
In-Reply-To: <4CFF5D2E.1080507@levkowetz.com>
Date: Wed, 8 Dec 2010 23:56:53 -0800
Message-ID: <017901cb9776$a596ce10$f0c46a30$@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: AQJ260A0gDDsotZc4IfkOuXcUkJNOQFJSwvjkjbIeJA=
Content-Language: en-us
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous	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, 09 Dec 2010 07:40:33 -0000

Henrik,

I can definitely understand the desire to say all lists are non-public to
begin with (and they don't necessarily have good names).  I would like to
discuss more where you see the complexity as come from the ability to do
lists of lists.  I can see various problems that you might be looking at,
but could see different ways of solving the problem which might make things
easier but still keep some of the flexibility of having nested lists.

Problems that I can see:

1.  Looking for loops - This is always a problem and eliminating nesting
does solve this one.

2.  Making included lists "live" - One possible solution to this would be to
just make the computation of my query (i.e. build up the logic) from the
current state of the list I included, without actually letting me know or
doing a dynamic update if the list I include changes.  This makes loop
detection easier since it is done when I save my query, it allows me to
build up my query in pieces (which can be useful) and it allows me to look
at the pieces of my query later which can be nice because a total list which
sends me updates can be made up of smaller lists that I want to use for the
html view.   This does mean that changes made to child lists would not be
reflected up dynamically - although it is possible that the fact it has not
propagated is send out.

3.  The simple act of including a list - If we did a static build of the
query, this would not be any different from allowing me to build a complex
OR/AND statement.  If it is a dynamic query builder then yes it does add
significant complexity.

4.  The UI for managing the multitude of lists is complex.  I don't think
this would be any more complex than the ability to build a decent sized
query along the order of.  Show me "(All Security area documents in IETF
Lass call) OR (All PKIX documents) OR (All docs with "SMIME" in the document
name) OR (all documents written by "Schaad")

5.  Dealing with items that appear multiple times is going to have to be
dealt with if any sort of complex grammar is allowed - so I don't that that
would be an issue that is solved by eliminating embedded lists.

Jim


> -----Original Message-----
> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
> bounces@ietf.org] On Behalf Of Henrik Levkowetz
> Sent: Wednesday, December 08, 2010 2:26 AM
> To: Paul Hoffman
> Cc: datatracker-rqmts@ietf.org
> Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous
lists
> 
> Hi Paul,
> 
> Looking this over, both specification and implementation of these
notification
> specifications ('lists') seems to becoming more and more complex, and I'm
not
> convinced that the complexity buys us a lot.  The whole issue comes about
> because of the decision that people should be able to include another list
in
> their notification list.
> 
> I would like to do away with the whole complexity of this by saying (at
least for
> this round -- we can always re-open this again when we have some practical
> experience with the first implementation) -- by saying that lists can't
include
> other lists, and all lists are anonymous and unpublished.
> 
> 
> Regards,
> 
> 	Henrik
> 
> On 2010-12-08 03:36 Paul Hoffman said:
> > Greetings again. It's time to spin up this list again, and a few people
have told
> me that specifying how public lists are publicly-readable and how
> private/anonymous lists are created and managed will unblock a bunch of
> other open issues. There was a lot of interest in these topics at the mic
in
> Beijing.
> >
> > The current text is below. This is just starting text, and it doesn't
cover the
> idea that some private/anonymous lists might have publicly-readable
> counterparts if the list owner wants.
> >
> > So, please say what you think should be done here. Do you have a
preference
> between private and anonymous? Do you have ideas for public lists?
> >
> > To facilitate the discussion, there will be a WebEx-based telechat on
Friday,
> December 17. Information on that comes in the next message. If we have
great
> consensus before the telechat, we can use that time to move on other open
> issues.
> >
> > --Paul Hoffman
> >
> > ======================================
> >
> > 2.1.3.  Requirement: Some lists must be able to be private or
> > anonymous
> >
> >    Seeing a list of drafts that covers multiple areas of interest can
> >    tell you something about the person who created the list.  For
> >    example, you might be able to guess that they might be looking for a
> >    job in a different field by looking at their list of drafts of
> >    interest.  Of course, anyone can follow individual drafts today
> >    without having that be exposed; however, following a particular group
> >    of drafts can reveal information about a person.
> >
> >    There is a open issue about whether lists should be default be
> >    private/anonymous or public, and how that default should be manifest
> >    in the eventual UI for creating lists.
> >
> >    The first proposed methods that might keep lists private/anonymous
> >    are:
> >
> >    o  Private lists might only be available using passwords or some
> >       other common authentication mechanism.  This would require that
> >       the Datatracker have a subscription process for users that could
> >       assign passwords, and a per-user process for adding lists to a
> >       user account.  (If the current Datatracker username and login
> >       scheme is used, the interface needs to be improved so that getting
> >       a new login, and changing one's password, are significantly
> >       easier.)
> >    o  Anonymous lists might be assigned random URLs from a very large
> >       (2^128) namespace, and the user who creates a list does not tell
> >       others the assigned URL.  This method makes it impossible for
> >       someone to search the entire set of assigned lists.  Given that
> >       the URLs for lists are most likely going to be copy-and-pasted
> >       anyway, having long random strings in the list's URL is not an
> >       impediment.
> >
> > 2.1.4.  Requirement: It must be easy for IETF leadership and individuals
> >         to make lists they create publicly-readable
> >
> >    Private or anonymous lists are fine for individuals, but publicly-
> >    readable lists can magnify the value to the whole community.  In
> >    fact, some early commenters on this document emphasized that
> >    publicly-readable lists will be more valuable to the IETF than
> >    helping individuals track documents that are only of interest to
> >    them.
> >
> >    Probably the easiest method to implement publicly-readable lists is
> >    to make them read-only aliases for private or anonymous lists.  This
> >    would allow the list originators to control the contents of the list
> >    as normal, but also allow anyone to view the results in the
> >    Datatracker and/or subscribe to notifications.  There may be other
> >    methods that would also make sense, and this section might change in
> >    the future.
> >
> >    Publicly-readable lists should have short URLs that can be
> >    transcribed without relying on copy-and-paste.  The names in the URLs
> >    for lists that are associated with IETF activities (initially, the
> >    lists created by WG chairs and ADs) can be mnemonic, but other public
> >    lists should have names that are not mnemonic in order to prevent
> >    name-squatting.
> >
> >    It is important to note that publicly-readable lists can only be
> >    changed by the owners.  Allowing many people to change the contents
> >    of a list would probably lead to lists that are not very useful to
> >    typical users.
> >
> >    Proposed later requirements include having the Datatracker list all
> >    of the publicly-readable lists (or certainly at least the ones
> >    associated with IETF activities), and having links from WG pages in
> >    Datatracker to the publicly-readable lists maintained by the WG
> >    chairs.
> > _______________________________________________
> > datatracker-rqmts mailing list
> > datatracker-rqmts@ietf.org
> > https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> >
> _______________________________________________
> datatracker-rqmts mailing list
> datatracker-rqmts@ietf.org
> https://www.ietf.org/mailman/listinfo/datatracker-rqmts


From ietf@augustcellars.com  Wed Dec  8 23:59:37 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 6D36C3A6A6E for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 23:59:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level: 
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=-0.038,  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 ExoWlhki-3Ky for <datatracker-rqmts@core3.amsl.com>; Wed,  8 Dec 2010 23:59:36 -0800 (PST)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by core3.amsl.com (Postfix) with ESMTP id 595CA3A6A57 for <datatracker-rqmts@ietf.org>; Wed,  8 Dec 2010 23:59:36 -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 5FEBB6EF38; Thu,  9 Dec 2010 00:01:04 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Russ Housley'" <housley@vigilsec.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]>	<4CFF5D2E.1080507@levkowetz.com> <4CFFD7E2.7060307@vigilsec.com> <015d01cb9725$7fba21c0$7f2e6540$@augustcellars.com> <4D000815.5090707@vigilsec.com>
In-Reply-To: <4D000815.5090707@vigilsec.com>
Date: Thu, 9 Dec 2010 00:15:59 -0800
Message-ID: <017b01cb9779$51052600$f30f7200$@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: AQJ260A0gDDsotZc4IfkOuXcUkJNOQFJSwvjAsZA1kwA6z2zYQFuwimRkg3PXHA=
Content-Language: en-us
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous	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, 09 Dec 2010 07:59:37 -0000

Russ,

This is not only a list of documents I want notifications for, but a list of
documents that I want to be able to view status using an HTML view a la the
current data tracker.  Trying to dig through a large number of documents
here would be troublesome, even if a single list was all that provided
notifications to me.

Jim


> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: Wednesday, December 08, 2010 2:35 PM
> To: Jim Schaad
> Cc: datatracker-rqmts@ietf.org
> Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous
lists
> 
> For what gain?  It is the list of documents you want to receive
notifications of
> changes.
> 
> Russ
> 
> On 12/8/2010 5:15 PM, Jim Schaad wrote:
> > Russ,
> >
> > I don't think you really want to restrict me to a single list.  This
> > would just require that I create multiple logins in order to get
multiple lists.
> >
> > Jim
> >
> >
> >> -----Original Message-----
> >> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
> >> bounces@ietf.org] On Behalf Of Russ Housley
> >> Sent: Wednesday, December 08, 2010 11:09 AM
> >> To: Henrik Levkowetz
> >> Cc: datatracker-rqmts@ietf.org
> >> Subject: Re: [datatracker-rqmts] Publicly-readable and
> >> private/anonymous
> > lists
> >>
> >> Henrik:
> >>
> >> I agree that lists of lists is causing more complexity than expected.
> >> I
> > think that
> >> putting it aside for now is a good choice.
> >>
> >> I wonder if it would be easier to start with two kinds of lists:
> >>   --  public-and-published
> >>   --  private-and-unpublished
> >>
> >> The public-and-published are used to follow the documents associated
> >> with
> > a
> >> particular topic.  They have a public owner that has agreed to add
> >> and
> > remove
> >> documents as appropriate.  This is like the web page that shows the
> > possible
> >> WG and non-WG mail lists that are available to IETF participants.
> >>
> >> The private-and-unpublished are part of a single user's preferences.
> >> They are not shared, and they are owned by that user.  Each user gets
> >> one
> > and
> >> only one of them.
> >>
> >> Russ
> >>
> >> On 12/8/2010 5:25 AM, Henrik Levkowetz wrote:
> >>> Hi Paul,
> >>>
> >>> Looking this over, both specification and implementation of these
> >>> notification specifications ('lists') seems to becoming more and
> >>> more complex, and I'm not convinced that the complexity buys us a
> >>> lot.  The whole issue comes about because of the decision that
> >>> people should be able to include another list in their notification
list.
> >>>
> >>> I would like to do away with the whole complexity of this by saying
> >>> (at least for this round -- we can always re-open this again when we
> >>> have some practical experience with the first implementation) -- by
> >>> saying that lists can't include other lists, and all lists are
> >>> anonymous and unpublished.
> >>>
> >>>
> >>> Regards,
> >>>
> >>> 	Henrik
> >>>
> >>> On 2010-12-08 03:36 Paul Hoffman said:
> >>>> Greetings again. It's time to spin up this list again, and a few
> >>>> people
> > have
> >> told me that specifying how public lists are publicly-readable and
> >> how private/anonymous lists are created and managed will unblock a
> >> bunch of other open issues. There was a lot of interest in these
> >> topics at the mic
> > in
> >> Beijing.
> >>>>
> >>>> The current text is below. This is just starting text, and it
> >>>> doesn't
> > cover the
> >> idea that some private/anonymous lists might have publicly-readable
> >> counterparts if the list owner wants.
> >>>>
> >>>> So, please say what you think should be done here. Do you have a
> >> preference between private and anonymous? Do you have ideas for
> >> public
> > lists?
> >>>>
> >>>> To facilitate the discussion, there will be a WebEx-based telechat
> >>>> on
> > Friday,
> >> December 17. Information on that comes in the next message. If we
> >> have
> > great
> >> consensus before the telechat, we can use that time to move on other
> >> open issues.
> >>>>
> >>>> --Paul Hoffman
> >>>>
> >>>> ======================================
> >>>>
> >>>> 2.1.3.  Requirement: Some lists must be able to be private or
> >>>> anonymous
> >>>>
> >>>>    Seeing a list of drafts that covers multiple areas of interest can
> >>>>    tell you something about the person who created the list.  For
> >>>>    example, you might be able to guess that they might be looking for
a
> >>>>    job in a different field by looking at their list of drafts of
> >>>>    interest.  Of course, anyone can follow individual drafts today
> >>>>    without having that be exposed; however, following a particular
> > group
> >>>>    of drafts can reveal information about a person.
> >>>>
> >>>>    There is a open issue about whether lists should be default be
> >>>>    private/anonymous or public, and how that default should be
manifest
> >>>>    in the eventual UI for creating lists.
> >>>>
> >>>>    The first proposed methods that might keep lists private/anonymous
> >>>>    are:
> >>>>
> >>>>    o  Private lists might only be available using passwords or some
> >>>>       other common authentication mechanism.  This would require that
> >>>>       the Datatracker have a subscription process for users that
could
> >>>>       assign passwords, and a per-user process for adding lists to a
> >>>>       user account.  (If the current Datatracker username and login
> >>>>       scheme is used, the interface needs to be improved so that
> > getting
> >>>>       a new login, and changing one's password, are significantly
> >>>>       easier.)
> >>>>    o  Anonymous lists might be assigned random URLs from a very large
> >>>>       (2^128) namespace, and the user who creates a list does not
tell
> >>>>       others the assigned URL.  This method makes it impossible for
> >>>>       someone to search the entire set of assigned lists.  Given that
> >>>>       the URLs for lists are most likely going to be copy-and-pasted
> >>>>       anyway, having long random strings in the list's URL is not an
> >>>>       impediment.
> >>>>
> >>>> 2.1.4.  Requirement: It must be easy for IETF leadership and
> > individuals
> >>>>         to make lists they create publicly-readable
> >>>>
> >>>>    Private or anonymous lists are fine for individuals, but publicly-
> >>>>    readable lists can magnify the value to the whole community.  In
> >>>>    fact, some early commenters on this document emphasized that
> >>>>    publicly-readable lists will be more valuable to the IETF than
> >>>>    helping individuals track documents that are only of interest to
> >>>>    them.
> >>>>
> >>>>    Probably the easiest method to implement publicly-readable lists
is
> >>>>    to make them read-only aliases for private or anonymous lists.
This
> >>>>    would allow the list originators to control the contents of the
list
> >>>>    as normal, but also allow anyone to view the results in the
> >>>>    Datatracker and/or subscribe to notifications.  There may be other
> >>>>    methods that would also make sense, and this section might change
in
> >>>>    the future.
> >>>>
> >>>>    Publicly-readable lists should have short URLs that can be
> >>>>    transcribed without relying on copy-and-paste.  The names in the
> > URLs
> >>>>    for lists that are associated with IETF activities (initially, the
> >>>>    lists created by WG chairs and ADs) can be mnemonic, but other
> > public
> >>>>    lists should have names that are not mnemonic in order to prevent
> >>>>    name-squatting.
> >>>>
> >>>>    It is important to note that publicly-readable lists can only be
> >>>>    changed by the owners.  Allowing many people to change the
contents
> >>>>    of a list would probably lead to lists that are not very useful to
> >>>>    typical users.
> >>>>
> >>>>    Proposed later requirements include having the Datatracker list
all
> >>>>    of the publicly-readable lists (or certainly at least the ones
> >>>>    associated with IETF activities), and having links from WG pages
in
> >>>>    Datatracker to the publicly-readable lists maintained by the WG
> >>>>    chairs.
> >>>> _______________________________________________
> >>>> datatracker-rqmts mailing list
> >>>> datatracker-rqmts@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> >>>>
> >>> _______________________________________________
> >>> datatracker-rqmts mailing list
> >>> datatracker-rqmts@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> >>>
> >> _______________________________________________
> >> datatracker-rqmts mailing list
> >> datatracker-rqmts@ietf.org
> >> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> >
> >


From kivinen@iki.fi  Thu Dec  9 00:57:38 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 1F3CC28C0CF for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 00:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=-0.088, 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 iv-4t5BSFoem for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 00:57:37 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) by core3.amsl.com (Postfix) with ESMTP id 0CABE3A6A99 for <datatracker-rqmts@ietf.org>; Thu,  9 Dec 2010 00:57:36 -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 oB98wvrp029604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2010 10:58:57 +0200 (EET)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.3/8.12.11) id oB98wvR8000362; Thu, 9 Dec 2010 10:58:57 +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: <19712.39505.534340.368737@fireball.kivinen.iki.fi>
Date: Thu, 9 Dec 2010 10:58:57 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4D000815.5090707@vigilsec.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]> <4CFF5D2E.1080507@levkowetz.com> <4CFFD7E2.7060307@vigilsec.com> <015d01cb9725$7fba21c0$7f2e6540$@augustcellars.com> <4D000815.5090707@vigilsec.com>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 19 min
X-Total-Time: 9 min
Cc: Jim Schaad <ietf@augustcellars.com>, datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and	private/anonymous	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, 09 Dec 2010 08:57:38 -0000

Russ Housley writes:
> For what gain?  It is the list of documents you want to receive
> notifications of changes.

I for example do follow some working groups more often (once per week
for groups like ipsecme) and in some working groups I only go through
changes every now and then (usually before ietf meeting). I most
likely do not want to get any email notifications from any of those
lists, but only have a web page where I can go to check what changes
there has been, or what is the current status of the documents on that
list.

I.e. this would be more likely be something like the daily dose of the
IETF, but on the limited set of documents, and different time
interval.

Also I do think list of lists feature is quite important for getting
lists usable. I myself probably do not have time to keep up
maintaining lists of interesting documents myself, so would really
like to be able to reuse list created for example by IPsecME WG chairs
for documents which are interesting for ipsecme wg people. Then I
would like to combine it with some other list from some other wg
chair, and then combine them to one list which contains documents of
interest for me.

If we do not allow list of lists, then I need to combine lists myself,
or more likely I need to go through multiple lists manually. In this
manual process I most likely need to do manual duplicate elimination
too, and this would be done automatically for list of lists (i.e.
documents should appear on the resulting list only once, regardless
from how many different sublist it came out.

Loop detection etc is problem that can be solved. 
-- 
kivinen@iki.fi

From henrik@levkowetz.com  Thu Dec  9 01:49:58 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 9A6563A6AAC for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 01:49:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=-0.101, 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 LDyytQbwRNyr for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 01:49:57 -0800 (PST)
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 15ABF3A6A69 for <datatracker-rqmts@ietf.org>; Thu,  9 Dec 2010 01:49:57 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:55072 helo=dyn-fg124.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 1PQd9Z-0006qV-HM; Thu, 09 Dec 2010 10:51:13 +0100
Message-ID: <4D00A685.1030701@levkowetz.com>
Date: Thu, 09 Dec 2010 10:51:01 +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: Russ Housley <housley@vigilsec.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]> <4CFF5D2E.1080507@levkowetz.com> <4CFFD7E2.7060307@vigilsec.com>
In-Reply-To: <4CFFD7E2.7060307@vigilsec.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5334213389A44BD565386439"
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: housley@vigilsec.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] Publicly-readable and private/anonymous 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, 09 Dec 2010 09:49:58 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5334213389A44BD565386439
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Russ,

On 2010-12-08 20:09 Russ Housley said:
> Henrik:
>=20
> I agree that lists of lists is causing more complexity than expected.  =
I
> think that putting it aside for now is a good choice.
>=20
> I wonder if it would be easier to start with two kinds of lists:
>   --  public-and-published
>   --  private-and-unpublished

> The public-and-published are used to follow the documents associated
> with a particular topic.  They have a public owner that has agreed to
> add and remove documents as appropriate.  This is like the web page tha=
t
> shows the possible WG and non-WG mail lists that are available to IETF
> participants.
>=20
> The private-and-unpublished are part of a single user's preferences.
> They are not shared, and they are owned by that user.  Each user gets
> one and only one of them.

I think this can be made to work in a good way, with little added
complexity; especially if we don't put too much into the specification
about multiple ways to name, hide, and password protect these.

(If we make the key to each list a user-configurable string, chosen when
the list is set up, with a default which is just a freshly generated
random string, the implementation will be the same for both kinds of
list.)


Best,

	Henrik


> Russ
>=20
> On 12/8/2010 5:25 AM, Henrik Levkowetz wrote:
>> Hi Paul,
>>
>> Looking this over, both specification and implementation of these
>> notification specifications ('lists') seems to becoming more and
>> more complex, and I'm not convinced that the complexity buys us a
>> lot.  The whole issue comes about because of the decision that
>> people should be able to include another list in their notification
>> list.
>>
>> I would like to do away with the whole complexity of this by saying
>> (at least for this round -- we can always re-open this again when
>> we have some practical experience with the first implementation) --
>> by saying that lists can't include other lists, and all lists are
>> anonymous and unpublished.
>>
>>
>> Regards,
>>
>> 	Henrik
>>
>> On 2010-12-08 03:36 Paul Hoffman said:
>>> Greetings again. It's time to spin up this list again, and a few peop=
le have told me that specifying how public lists are publicly-readable an=
d how private/anonymous lists are created and managed will unblock a bunc=
h of other open issues. There was a lot of interest in these topics at th=
e mic in Beijing.
>>>
>>> The current text is below. This is just starting text, and it doesn't=
 cover the idea that some private/anonymous lists might have publicly-rea=
dable counterparts if the list owner wants.
>>>
>>> So, please say what you think should be done here. Do you have a pref=
erence between private and anonymous? Do you have ideas for public lists?=

>>>
>>> To facilitate the discussion, there will be a WebEx-based telechat on=
 Friday, December 17. Information on that comes in the next message. If w=
e have great consensus before the telechat, we can use that time to move =
on other open issues.
>>>
>>> --Paul Hoffman
>>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>> 2.1.3.  Requirement: Some lists must be able to be private or anonymo=
us
>>>
>>>    Seeing a list of drafts that covers multiple areas of interest can=

>>>    tell you something about the person who created the list.  For
>>>    example, you might be able to guess that they might be looking for=
 a
>>>    job in a different field by looking at their list of drafts of
>>>    interest.  Of course, anyone can follow individual drafts today
>>>    without having that be exposed; however, following a particular gr=
oup
>>>    of drafts can reveal information about a person.
>>>
>>>    There is a open issue about whether lists should be default be
>>>    private/anonymous or public, and how that default should be manife=
st
>>>    in the eventual UI for creating lists.
>>>
>>>    The first proposed methods that might keep lists private/anonymous=

>>>    are:
>>>
>>>    o  Private lists might only be available using passwords or some
>>>       other common authentication mechanism.  This would require that=

>>>       the Datatracker have a subscription process for users that coul=
d
>>>       assign passwords, and a per-user process for adding lists to a
>>>       user account.  (If the current Datatracker username and login
>>>       scheme is used, the interface needs to be improved so that gett=
ing
>>>       a new login, and changing one's password, are significantly
>>>       easier.)
>>>    o  Anonymous lists might be assigned random URLs from a very large=

>>>       (2^128) namespace, and the user who creates a list does not tel=
l
>>>       others the assigned URL.  This method makes it impossible for
>>>       someone to search the entire set of assigned lists.  Given that=

>>>       the URLs for lists are most likely going to be copy-and-pasted
>>>       anyway, having long random strings in the list's URL is not an
>>>       impediment.
>>>
>>> 2.1.4.  Requirement: It must be easy for IETF leadership and individu=
als
>>>         to make lists they create publicly-readable
>>>
>>>    Private or anonymous lists are fine for individuals, but publicly-=

>>>    readable lists can magnify the value to the whole community.  In
>>>    fact, some early commenters on this document emphasized that
>>>    publicly-readable lists will be more valuable to the IETF than
>>>    helping individuals track documents that are only of interest to
>>>    them.
>>>
>>>    Probably the easiest method to implement publicly-readable lists i=
s
>>>    to make them read-only aliases for private or anonymous lists.  Th=
is
>>>    would allow the list originators to control the contents of the li=
st
>>>    as normal, but also allow anyone to view the results in the
>>>    Datatracker and/or subscribe to notifications.  There may be other=

>>>    methods that would also make sense, and this section might change =
in
>>>    the future.
>>>
>>>    Publicly-readable lists should have short URLs that can be
>>>    transcribed without relying on copy-and-paste.  The names in the U=
RLs
>>>    for lists that are associated with IETF activities (initially, the=

>>>    lists created by WG chairs and ADs) can be mnemonic, but other pub=
lic
>>>    lists should have names that are not mnemonic in order to prevent
>>>    name-squatting.
>>>
>>>    It is important to note that publicly-readable lists can only be
>>>    changed by the owners.  Allowing many people to change the content=
s
>>>    of a list would probably lead to lists that are not very useful to=

>>>    typical users.
>>>
>>>    Proposed later requirements include having the Datatracker list al=
l
>>>    of the publicly-readable lists (or certainly at least the ones
>>>    associated with IETF activities), and having links from WG pages i=
n
>>>    Datatracker to the publicly-readable lists maintained by the WG
>>>    chairs.
>>> _______________________________________________
>>> datatracker-rqmts mailing list
>>> datatracker-rqmts@ietf.org
>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>>
>> _______________________________________________
>> datatracker-rqmts mailing list
>> datatracker-rqmts@ietf.org
>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>
>=20


--------------enig5334213389A44BD565386439
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAk0Apo0ACgkQeVhrtTJkXCPcggCfe5wR9Bd0nf5X9u1lMnrkIEwf
6qYAoOubFRGwx7hRqloUrQsW68pEpMZF
=Im2Y
-----END PGP SIGNATURE-----

--------------enig5334213389A44BD565386439--

From henrik@levkowetz.com  Thu Dec  9 01:55:23 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 06E473A6AB4 for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 01:55:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level: 
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 L2TGiLX2egUS for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 01:55:21 -0800 (PST)
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 651A23A6AA1 for <datatracker-rqmts@ietf.org>; Thu,  9 Dec 2010 01:55:21 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:55122 helo=dyn-fg124.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 1PQdEs-0005dW-Eb; Thu, 09 Dec 2010 10:56:40 +0100
Message-ID: <4D00A7D6.6000500@levkowetz.com>
Date: Thu, 09 Dec 2010 10:56:38 +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: Jim Schaad <ietf@augustcellars.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]> <4CFF5D2E.1080507@levkowetz.com> <017901cb9776$a596ce10$f0c46a30$@augustcellars.com>
In-Reply-To: <017901cb9776$a596ce10$f0c46a30$@augustcellars.com>
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: ietf@augustcellars.com, 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] Publicly-readable and private/anonymous	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, 09 Dec 2010 09:55:23 -0000

Jim,

On 2010-12-09 08:56 Jim Schaad said:
> Henrik,
> 
> I can definitely understand the desire to say all lists are non-public to
> begin with (and they don't necessarily have good names).  I would like to
> discuss more where you see the complexity as come from the ability to do
> lists of lists.  I can see various problems that you might be looking at,
> but could see different ways of solving the problem which might make things
> easier but still keep some of the flexibility of having nested lists.

It's not that these things can't be solved, it's more a matter of both
specification and implementation (*not* just the implementation) of this
particular feature becoming several times more complex for very little gain.

It's better to start out with something which will handle 90% of the needs
and is simple, and then see which itch is most urgent to scratch once that's
in place.


Regards,

	Henrik

> Problems that I can see:
> 
> 1.  Looking for loops - This is always a problem and eliminating nesting
> does solve this one.
> 
> 2.  Making included lists "live" - One possible solution to this would be to
> just make the computation of my query (i.e. build up the logic) from the
> current state of the list I included, without actually letting me know or
> doing a dynamic update if the list I include changes.  This makes loop
> detection easier since it is done when I save my query, it allows me to
> build up my query in pieces (which can be useful) and it allows me to look
> at the pieces of my query later which can be nice because a total list which
> sends me updates can be made up of smaller lists that I want to use for the
> html view.   This does mean that changes made to child lists would not be
> reflected up dynamically - although it is possible that the fact it has not
> propagated is send out.
> 
> 3.  The simple act of including a list - If we did a static build of the
> query, this would not be any different from allowing me to build a complex
> OR/AND statement.  If it is a dynamic query builder then yes it does add
> significant complexity.
> 
> 4.  The UI for managing the multitude of lists is complex.  I don't think
> this would be any more complex than the ability to build a decent sized
> query along the order of.  Show me "(All Security area documents in IETF
> Lass call) OR (All PKIX documents) OR (All docs with "SMIME" in the document
> name) OR (all documents written by "Schaad")
> 
> 5.  Dealing with items that appear multiple times is going to have to be
> dealt with if any sort of complex grammar is allowed - so I don't that that
> would be an issue that is solved by eliminating embedded lists.
> 
> Jim
> 
> 
>> -----Original Message-----
>> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
>> bounces@ietf.org] On Behalf Of Henrik Levkowetz
>> Sent: Wednesday, December 08, 2010 2:26 AM
>> To: Paul Hoffman
>> Cc: datatracker-rqmts@ietf.org
>> Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous
> lists
>>
>> Hi Paul,
>>
>> Looking this over, both specification and implementation of these
> notification
>> specifications ('lists') seems to becoming more and more complex, and I'm
> not
>> convinced that the complexity buys us a lot.  The whole issue comes about
>> because of the decision that people should be able to include another list
> in
>> their notification list.
>>
>> I would like to do away with the whole complexity of this by saying (at
> least for
>> this round -- we can always re-open this again when we have some practical
>> experience with the first implementation) -- by saying that lists can't
> include
>> other lists, and all lists are anonymous and unpublished.
>>
>>
>> Regards,
>>
>> 	Henrik
>>
>> On 2010-12-08 03:36 Paul Hoffman said:
>>> Greetings again. It's time to spin up this list again, and a few people
> have told
>> me that specifying how public lists are publicly-readable and how
>> private/anonymous lists are created and managed will unblock a bunch of
>> other open issues. There was a lot of interest in these topics at the mic
> in
>> Beijing.
>>>
>>> The current text is below. This is just starting text, and it doesn't
> cover the
>> idea that some private/anonymous lists might have publicly-readable
>> counterparts if the list owner wants.
>>>
>>> So, please say what you think should be done here. Do you have a
> preference
>> between private and anonymous? Do you have ideas for public lists?
>>>
>>> To facilitate the discussion, there will be a WebEx-based telechat on
> Friday,
>> December 17. Information on that comes in the next message. If we have
> great
>> consensus before the telechat, we can use that time to move on other open
>> issues.
>>>
>>> --Paul Hoffman
>>>
>>> ======================================
>>>
>>> 2.1.3.  Requirement: Some lists must be able to be private or
>>> anonymous
>>>
>>>    Seeing a list of drafts that covers multiple areas of interest can
>>>    tell you something about the person who created the list.  For
>>>    example, you might be able to guess that they might be looking for a
>>>    job in a different field by looking at their list of drafts of
>>>    interest.  Of course, anyone can follow individual drafts today
>>>    without having that be exposed; however, following a particular group
>>>    of drafts can reveal information about a person.
>>>
>>>    There is a open issue about whether lists should be default be
>>>    private/anonymous or public, and how that default should be manifest
>>>    in the eventual UI for creating lists.
>>>
>>>    The first proposed methods that might keep lists private/anonymous
>>>    are:
>>>
>>>    o  Private lists might only be available using passwords or some
>>>       other common authentication mechanism.  This would require that
>>>       the Datatracker have a subscription process for users that could
>>>       assign passwords, and a per-user process for adding lists to a
>>>       user account.  (If the current Datatracker username and login
>>>       scheme is used, the interface needs to be improved so that getting
>>>       a new login, and changing one's password, are significantly
>>>       easier.)
>>>    o  Anonymous lists might be assigned random URLs from a very large
>>>       (2^128) namespace, and the user who creates a list does not tell
>>>       others the assigned URL.  This method makes it impossible for
>>>       someone to search the entire set of assigned lists.  Given that
>>>       the URLs for lists are most likely going to be copy-and-pasted
>>>       anyway, having long random strings in the list's URL is not an
>>>       impediment.
>>>
>>> 2.1.4.  Requirement: It must be easy for IETF leadership and individuals
>>>         to make lists they create publicly-readable
>>>
>>>    Private or anonymous lists are fine for individuals, but publicly-
>>>    readable lists can magnify the value to the whole community.  In
>>>    fact, some early commenters on this document emphasized that
>>>    publicly-readable lists will be more valuable to the IETF than
>>>    helping individuals track documents that are only of interest to
>>>    them.
>>>
>>>    Probably the easiest method to implement publicly-readable lists is
>>>    to make them read-only aliases for private or anonymous lists.  This
>>>    would allow the list originators to control the contents of the list
>>>    as normal, but also allow anyone to view the results in the
>>>    Datatracker and/or subscribe to notifications.  There may be other
>>>    methods that would also make sense, and this section might change in
>>>    the future.
>>>
>>>    Publicly-readable lists should have short URLs that can be
>>>    transcribed without relying on copy-and-paste.  The names in the URLs
>>>    for lists that are associated with IETF activities (initially, the
>>>    lists created by WG chairs and ADs) can be mnemonic, but other public
>>>    lists should have names that are not mnemonic in order to prevent
>>>    name-squatting.
>>>
>>>    It is important to note that publicly-readable lists can only be
>>>    changed by the owners.  Allowing many people to change the contents
>>>    of a list would probably lead to lists that are not very useful to
>>>    typical users.
>>>
>>>    Proposed later requirements include having the Datatracker list all
>>>    of the publicly-readable lists (or certainly at least the ones
>>>    associated with IETF activities), and having links from WG pages in
>>>    Datatracker to the publicly-readable lists maintained by the WG
>>>    chairs.
>>> _______________________________________________
>>> datatracker-rqmts mailing list
>>> datatracker-rqmts@ietf.org
>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>>
>> _______________________________________________
>> datatracker-rqmts mailing list
>> datatracker-rqmts@ietf.org
>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
> 
> 

From housley@vigilsec.com  Thu Dec  9 06:33:00 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 60BB828C113 for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 06:33:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=-0.084, 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 ks5iNKfSDAd3 for <datatracker-rqmts@core3.amsl.com>; Thu,  9 Dec 2010 06:32:59 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id EB2AB28C0DC for <datatracker-rqmts@ietf.org>; Thu,  9 Dec 2010 06:32:58 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D78989A47BC; Thu,  9 Dec 2010 09:34:27 -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 Oom3+sN48Dm9; Thu,  9 Dec 2010 09:34:06 -0500 (EST)
Received: from [128.31.34.232] (31-34-232.wireless.csail.mit.edu [128.31.34.232]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 921309A4743; Thu,  9 Dec 2010 09:34:26 -0500 (EST)
Message-ID: <4D00E8EF.2060100@vigilsec.com>
Date: Thu, 09 Dec 2010 09:34:23 -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: Jim Schaad <ietf@augustcellars.com>
References: <p0624081bc9249d506bb8@[10.20.30.150]>	<4CFF5D2E.1080507@levkowetz.com> <4CFFD7E2.7060307@vigilsec.com> <015d01cb9725$7fba21c0$7f2e6540$@augustcellars.com> <4D000815.5090707@vigilsec.com> <017b01cb9779$51052600$f30f7200$@augustcellars.com>
In-Reply-To: <017b01cb9779$51052600$f30f7200$@augustcellars.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous	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, 09 Dec 2010 14:33:00 -0000

Jim:

The 'default view' seems like a very different thing, and composing that
from a list of lists seems even more ugly than the current datatracker.

My comment was about the notifications list.  I accept that there is a
need for two different things here.

Russ

On 12/9/2010 3:15 AM, Jim Schaad wrote:
> Russ,
> 
> This is not only a list of documents I want notifications for, but a list of
> documents that I want to be able to view status using an HTML view a la the
> current data tracker.  Trying to dig through a large number of documents
> here would be troublesome, even if a single list was all that provided
> notifications to me.
> 
> Jim
> 
> 
>> -----Original Message-----
>> From: Russ Housley [mailto:housley@vigilsec.com]
>> Sent: Wednesday, December 08, 2010 2:35 PM
>> To: Jim Schaad
>> Cc: datatracker-rqmts@ietf.org
>> Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous
> lists
>>
>> For what gain?  It is the list of documents you want to receive
> notifications of
>> changes.
>>
>> Russ
>>
>> On 12/8/2010 5:15 PM, Jim Schaad wrote:
>>> Russ,
>>>
>>> I don't think you really want to restrict me to a single list.  This
>>> would just require that I create multiple logins in order to get
> multiple lists.
>>>
>>> Jim
>>>
>>>
>>>> -----Original Message-----
>>>> From: datatracker-rqmts-bounces@ietf.org [mailto:datatracker-rqmts-
>>>> bounces@ietf.org] On Behalf Of Russ Housley
>>>> Sent: Wednesday, December 08, 2010 11:09 AM
>>>> To: Henrik Levkowetz
>>>> Cc: datatracker-rqmts@ietf.org
>>>> Subject: Re: [datatracker-rqmts] Publicly-readable and
>>>> private/anonymous
>>> lists
>>>>
>>>> Henrik:
>>>>
>>>> I agree that lists of lists is causing more complexity than expected.
>>>> I
>>> think that
>>>> putting it aside for now is a good choice.
>>>>
>>>> I wonder if it would be easier to start with two kinds of lists:
>>>>   --  public-and-published
>>>>   --  private-and-unpublished
>>>>
>>>> The public-and-published are used to follow the documents associated
>>>> with
>>> a
>>>> particular topic.  They have a public owner that has agreed to add
>>>> and
>>> remove
>>>> documents as appropriate.  This is like the web page that shows the
>>> possible
>>>> WG and non-WG mail lists that are available to IETF participants.
>>>>
>>>> The private-and-unpublished are part of a single user's preferences.
>>>> They are not shared, and they are owned by that user.  Each user gets
>>>> one
>>> and
>>>> only one of them.
>>>>
>>>> Russ
>>>>
>>>> On 12/8/2010 5:25 AM, Henrik Levkowetz wrote:
>>>>> Hi Paul,
>>>>>
>>>>> Looking this over, both specification and implementation of these
>>>>> notification specifications ('lists') seems to becoming more and
>>>>> more complex, and I'm not convinced that the complexity buys us a
>>>>> lot.  The whole issue comes about because of the decision that
>>>>> people should be able to include another list in their notification
> list.
>>>>>
>>>>> I would like to do away with the whole complexity of this by saying
>>>>> (at least for this round -- we can always re-open this again when we
>>>>> have some practical experience with the first implementation) -- by
>>>>> saying that lists can't include other lists, and all lists are
>>>>> anonymous and unpublished.
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> 	Henrik
>>>>>
>>>>> On 2010-12-08 03:36 Paul Hoffman said:
>>>>>> Greetings again. It's time to spin up this list again, and a few
>>>>>> people
>>> have
>>>> told me that specifying how public lists are publicly-readable and
>>>> how private/anonymous lists are created and managed will unblock a
>>>> bunch of other open issues. There was a lot of interest in these
>>>> topics at the mic
>>> in
>>>> Beijing.
>>>>>>
>>>>>> The current text is below. This is just starting text, and it
>>>>>> doesn't
>>> cover the
>>>> idea that some private/anonymous lists might have publicly-readable
>>>> counterparts if the list owner wants.
>>>>>>
>>>>>> So, please say what you think should be done here. Do you have a
>>>> preference between private and anonymous? Do you have ideas for
>>>> public
>>> lists?
>>>>>>
>>>>>> To facilitate the discussion, there will be a WebEx-based telechat
>>>>>> on
>>> Friday,
>>>> December 17. Information on that comes in the next message. If we
>>>> have
>>> great
>>>> consensus before the telechat, we can use that time to move on other
>>>> open issues.
>>>>>>
>>>>>> --Paul Hoffman
>>>>>>
>>>>>> ======================================
>>>>>>
>>>>>> 2.1.3.  Requirement: Some lists must be able to be private or
>>>>>> anonymous
>>>>>>
>>>>>>    Seeing a list of drafts that covers multiple areas of interest can
>>>>>>    tell you something about the person who created the list.  For
>>>>>>    example, you might be able to guess that they might be looking for
> a
>>>>>>    job in a different field by looking at their list of drafts of
>>>>>>    interest.  Of course, anyone can follow individual drafts today
>>>>>>    without having that be exposed; however, following a particular
>>> group
>>>>>>    of drafts can reveal information about a person.
>>>>>>
>>>>>>    There is a open issue about whether lists should be default be
>>>>>>    private/anonymous or public, and how that default should be
> manifest
>>>>>>    in the eventual UI for creating lists.
>>>>>>
>>>>>>    The first proposed methods that might keep lists private/anonymous
>>>>>>    are:
>>>>>>
>>>>>>    o  Private lists might only be available using passwords or some
>>>>>>       other common authentication mechanism.  This would require that
>>>>>>       the Datatracker have a subscription process for users that
> could
>>>>>>       assign passwords, and a per-user process for adding lists to a
>>>>>>       user account.  (If the current Datatracker username and login
>>>>>>       scheme is used, the interface needs to be improved so that
>>> getting
>>>>>>       a new login, and changing one's password, are significantly
>>>>>>       easier.)
>>>>>>    o  Anonymous lists might be assigned random URLs from a very large
>>>>>>       (2^128) namespace, and the user who creates a list does not
> tell
>>>>>>       others the assigned URL.  This method makes it impossible for
>>>>>>       someone to search the entire set of assigned lists.  Given that
>>>>>>       the URLs for lists are most likely going to be copy-and-pasted
>>>>>>       anyway, having long random strings in the list's URL is not an
>>>>>>       impediment.
>>>>>>
>>>>>> 2.1.4.  Requirement: It must be easy for IETF leadership and
>>> individuals
>>>>>>         to make lists they create publicly-readable
>>>>>>
>>>>>>    Private or anonymous lists are fine for individuals, but publicly-
>>>>>>    readable lists can magnify the value to the whole community.  In
>>>>>>    fact, some early commenters on this document emphasized that
>>>>>>    publicly-readable lists will be more valuable to the IETF than
>>>>>>    helping individuals track documents that are only of interest to
>>>>>>    them.
>>>>>>
>>>>>>    Probably the easiest method to implement publicly-readable lists
> is
>>>>>>    to make them read-only aliases for private or anonymous lists.
> This
>>>>>>    would allow the list originators to control the contents of the
> list
>>>>>>    as normal, but also allow anyone to view the results in the
>>>>>>    Datatracker and/or subscribe to notifications.  There may be other
>>>>>>    methods that would also make sense, and this section might change
> in
>>>>>>    the future.
>>>>>>
>>>>>>    Publicly-readable lists should have short URLs that can be
>>>>>>    transcribed without relying on copy-and-paste.  The names in the
>>> URLs
>>>>>>    for lists that are associated with IETF activities (initially, the
>>>>>>    lists created by WG chairs and ADs) can be mnemonic, but other
>>> public
>>>>>>    lists should have names that are not mnemonic in order to prevent
>>>>>>    name-squatting.
>>>>>>
>>>>>>    It is important to note that publicly-readable lists can only be
>>>>>>    changed by the owners.  Allowing many people to change the
> contents
>>>>>>    of a list would probably lead to lists that are not very useful to
>>>>>>    typical users.
>>>>>>
>>>>>>    Proposed later requirements include having the Datatracker list
> all
>>>>>>    of the publicly-readable lists (or certainly at least the ones
>>>>>>    associated with IETF activities), and having links from WG pages
> in
>>>>>>    Datatracker to the publicly-readable lists maintained by the WG
>>>>>>    chairs.
>>>>>> _______________________________________________
>>>>>> datatracker-rqmts mailing list
>>>>>> datatracker-rqmts@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>>>>>
>>>>> _______________________________________________
>>>>> datatracker-rqmts mailing list
>>>>> datatracker-rqmts@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>>>>
>>>> _______________________________________________
>>>> datatracker-rqmts mailing list
>>>> datatracker-rqmts@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/datatracker-rqmts
>>>
>>>
> 
> 

From paul.hoffman@vpnc.org  Mon Dec 13 19:10: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 0AAD628C124 for <datatracker-rqmts@core3.amsl.com>; Mon, 13 Dec 2010 19:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=1.523, BAYES_00=-2.599, GB_I_INVITATION=-2, 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 hGraQ1BzoY5A for <datatracker-rqmts@core3.amsl.com>; Mon, 13 Dec 2010 19:10:47 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 0E75F28C145 for <datatracker-rqmts@ietf.org>; Mon, 13 Dec 2010 19:10:46 -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 oBE3COiL092148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Mon, 13 Dec 2010 20:12:25 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624083ec92c910c3b11@[10.20.30.150]>
Date: Mon, 13 Dec 2010 19:12:22 -0800
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Reminder: Meeting invitation: iddtspec BoF Discussion
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, 14 Dec 2010 03:10:52 -0000

IETF Secretariat invites you to attend this online meeting.

Topic: iddtspec BoF Discussion
Date: Friday, December 17, 2010
Time: 8:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 964 770 156
Meeting Password: (This meeting does not require a password.)


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/j.php?ED=149351167&UID=1195259162&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting does not require a password.)
4. Click "Join".

To view in other time zones or languages, please click the link:
https://workgreen.webex.com/workgreen/j.php?ED=149351167&UID=1195259162&ORT=MiM0

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): 1-866-699-3239
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers: https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=149351167&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

Access code:964 770 156

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to <https://workgreen.webex.com/workgreen/mc>https://workgreen.webex.com/workgreen/mc
2. On the left navigation bar, click "Support".

You can contact me at:
amorris@amsl.com
1-510-492-4081

To add this meeting to your calendar program (for example Microsoft Outlook), click this link:
https://workgreen.webex.com/workgreen/j.php?ED=149351167&UID=1195259162&ICS=MI&LD=1&RD=2&ST=1&SHA2=PAMxj3WrOOG0DZ0TbZPOzTaGfbquqHbFt3ucwwqZ-ao=&RT=MiM0

The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://workgreen.webex.com/workgreen/systemdiagnosis.php

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x964770156#

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.
_______________________________________________
datatracker-rqmts mailing list
datatracker-rqmts@ietf.org
https://www.ietf.org/mailman/listinfo/datatracker-rqmts

--Paul Hoffman, Director
--VPN Consortium

From paul.hoffman@vpnc.org  Mon Dec 13 19:20:27 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 1FE343A6E35 for <datatracker-rqmts@core3.amsl.com>; Mon, 13 Dec 2010 19:20:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.423
X-Spam-Level: 
X-Spam-Status: No, score=-101.423 tagged_above=-999 required=5 tests=[AWL=0.396, 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 IMRJzxyaYlf7 for <datatracker-rqmts@core3.amsl.com>; Mon, 13 Dec 2010 19:20:26 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 5566E3A6D9B for <datatracker-rqmts@ietf.org>; Mon, 13 Dec 2010 19:20:26 -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 oBE3M4Hu092509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Mon, 13 Dec 2010 20:22:05 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624083fc92c911f3fb3@[10.20.30.150]>
In-Reply-To: <p0624081bc9249d506bb8@[10.20.30.150]>
References: <p0624081bc9249d506bb8@[10.20.30.150]>
Date: Mon, 13 Dec 2010 19:22:02 -0800
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [datatracker-rqmts] Publicly-readable and private/anonymous 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: Tue, 14 Dec 2010 03:20:27 -0000

This is a good discussion with lots of different views. After the telecon on Friday (would that be a voice-to-voice or v2v meeting?), I'll probably do an informal poll and see where we get.

As a lead-up, I want to reiterate that we all seem to be talking about having lists be created and edited by one person (for private/anonymous lists) and a very small number of known people for IETF-activity lists such as WGs and areas. What seems to be in question is what to do about the rest of the world being able to read those lists. Of course, IETF-activity lists only exist so that there can be readers, but there are differing views on whether the value of having private/anonymous lists outweighs the costs. A related idea is "not in the first round, but make them available later".

Wearing no hat: I think it is useful for me to be able to see someone else's list, for example when I'm starting up on a new topic that is not just a single WG. As an example, "Dan Wing's view of what is most interesting in v6 transition ideas" would be much more useful to me than "everything in BEHAVE". Also, there might be some good personal lists for topics in closed WGs, such as "Jim's view of ongoing work in S/MIME".

--Paul Hoffman, Director
--VPN Consortium

From housley@vigilsec.com  Fri Dec 17 14:46:28 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 4B61A3A6A09 for <datatracker-rqmts@core3.amsl.com>; Fri, 17 Dec 2010 14:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, 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 kIzzUS1Ku104 for <datatracker-rqmts@core3.amsl.com>; Fri, 17 Dec 2010 14:46:27 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 793893A69B8 for <datatracker-rqmts@ietf.org>; Fri, 17 Dec 2010 14:46:27 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 08DFB9A47B0; Fri, 17 Dec 2010 17:48:28 -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 A93HIe9hRA5m; Fri, 17 Dec 2010 17:48:08 -0500 (EST)
Received: from [192.168.2.110] (pool-96-231-58-190.washdc.fios.verizon.net [96.231.58.190]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 34D009A47A3; Fri, 17 Dec 2010 17:48:27 -0500 (EST)
Message-ID: <4D0BE8BB.7000301@vigilsec.com>
Date: Fri, 17 Dec 2010 17:48:27 -0500
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <1515.198.180.150.230.1288715769.squirrel@mail.smetech.net> <p0624089ac8f5f383565e@[10.20.30.150]>
In-Reply-To: <p0624089ac8f5f383565e@[10.20.30.150]>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: datatracker-rqmts@ietf.org
Subject: Re: [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: Fri, 17 Dec 2010 22:46:28 -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?
> 
> 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?

I am unaware of private information on the wikis.

Russ

From paul.hoffman@vpnc.org  Fri Dec 17 16:06: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 7DB5A3A6A3D for <datatracker-rqmts@core3.amsl.com>; Fri, 17 Dec 2010 16:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.583
X-Spam-Level: 
X-Spam-Status: No, score=-101.583 tagged_above=-999 required=5 tests=[AWL=0.463, BAYES_00=-2.599, 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 FInqEB0BwWzQ for <datatracker-rqmts@core3.amsl.com>; Fri, 17 Dec 2010 16:06:29 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 82F623A6A1B for <datatracker-rqmts@ietf.org>; Fri, 17 Dec 2010 16:06:29 -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 oBI08GuQ016800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Fri, 17 Dec 2010 17:08:17 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240804c931ab1c4abd@[10.20.30.150]>
Date: Fri, 17 Dec 2010 16:08:14 -0800
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Minutes from today's interim meeting
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: Sat, 18 Dec 2010 00:06:30 -0000

Greetings again. The minutes from today's virtual interim meeting are below. I'm comfortable with the conclusions that the small number of us there reached, and will have a new draft out in the next week so we can focus more on some of the other open issues.

As usual, if I close out an issue that someone feels strongly should be reopened because I might have gotten the "rough consensus without being a WG" wrong, let me know.

--Paul Hoffman

================================================

IDDTSPEC interim meeting
2010-12-17, 0800 PST, via WebEx

In attendance:
	Paul Hoffman
	Russ Housley
	Alexa Morris
	Henrik Levkowetz

Russ: define the support needed upfront
	Need to understand the impact on the Secretariat
	Add a backup capability for user setups

Russ: want to be able to create a Datatracker account that does not involve the Secretariat
	Limit Secretariat to assigning privileges to role-based accounts
	Similar to no Secretariat involvement in signing up for a mailing list
	This functionality is not there currently
	Users would still would go to Secretariat for support
		Sent to ietf-action

Question of only one list vs many for individuals
	Russ: Where is the value of multiple lists?
		If you want the same granularity on all of them, only need to have one
		Maybe each piece of a list has a granularity tag, or two lists
		"Show me the state / populate the table" would lead to separate queries
		If they are notify lists, only need one
	Henrik agrees that users only need one
	Henrik: user can choose a list name (default name will be ugly and not guessable)
		If someone announces the name/URL for the Atom feed, others can subscribe
		Don't announce them automatically
		Public should not be able to subscribe to email, but can get Atom
		Russ: lists don't contain contents, but instead the actions that you want
			Henrik: but you need a URL for an Atom feed
				Logging in for Atom would be a hassle
			Russ agrees that handing out the URL for the feed is OK
				Need configuration for "I want email" or not
	Resolution: agree that private lists can have a public feed

	Need reasonable identifiers for drafts, maybe URNs

Accounts
	Russ: Every WG chair has personal account
		Accounts have privileges
			Will have "I am WG chair"
			That privilege will allow you to edit the list for WG
		For individuals, edit this list will be "edit this account's list"
	Notifications
		Russ: maybe an SMS would be needed as an edge case

API discussion
	Russ: pasting into a text window is sufficient
		Mailman uses this for bulk adds
	Henrik: wants a generic format to export information
		Add or replace could both be provided
		Should method be text window or something else: doesn't matter
		Russ: likes text window so the entries could be mailed around
		People will want more detail, such as granularity level
		Maybe use JSON structures
			Can pull out different bits at any level by URL

Lists of lists
	General agreement: much too complicated to do in first version
	Could be done in a later version

Henrik: Make display publicly available as well
	Similar to Atom URL
	Wants to avoid complexity of subscribing to mail streams


From paul.hoffman@vpnc.org  Mon Dec 20 20:37: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 CBD9D3A699F for <datatracker-rqmts@core3.amsl.com>; Mon, 20 Dec 2010 20:37:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.395
X-Spam-Level: 
X-Spam-Status: No, score=-100.395 tagged_above=-999 required=5 tests=[AWL=-0.763, BAYES_40=-0.185, 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 C7296MoZDILl for <datatracker-rqmts@core3.amsl.com>; Mon, 20 Dec 2010 20:37:14 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id DE4843A6997 for <datatracker-rqmts@ietf.org>; Mon, 20 Dec 2010 20:37:14 -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 oBL4d8c9080057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Mon, 20 Dec 2010 21:39:09 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240804c935de243f1b@[10.20.30.150]>
Date: Mon, 20 Dec 2010 20:39:07 -0800
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Draft -03 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: Tue, 21 Dec 2010 04:37:15 -0000

As promised, I have turned in the -03 of the draft, <http://www.ietf.org/internet-drafts/draft-ietf-genarea-datatracker-community-03.txt>. The diffs are large, but here is the summary:

   Made the number of lists per person from "many" to "one".  This was
   done throughout the document, but is particularly apparent in 2.1.2.

   Resolved the "private or anonymous" question by making lists private,
   based on ownership of a Datatracker account.  This primarily affects
   2.1.3, which now also covers the requirement that private lists also
   have a public read-only component.  This change assumes that private
   lists are a requirement.

   Talked more about role-based lists, particularly in 2.1.4, making all
   those lists publicly-readable.

   Got rid of the requirement that lists can dynamically include other
   lists, making 2.1.7 a tombstone.  Also modified 2.2.3 and 2.3.2
   because of this change.

   Added two new open issues ("all drafts referenced by another list"
   and "liaison statements stream").

If everyone (or most everyone) is comfortable with those changes, we can move on to other big issues. Otherwise, let's get the number-of-lists and lists-within-lists issues settled first.

--Paul Hoffman, Director
--VPN Consortium
