Re: [datatracker-rqmts] Slides for the face-to-face BoF next week

Yaron Sheffer <yaronf.ietf@gmail.com> Wed, 03 November 2010 14:09 UTC

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

Hi Paul,

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

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

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

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

Thanks,
	Yaron

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