Re: OPES charter proposal again.
Dave Crocker <dhc2@dcrocker.net> Wed, 04 July 2001 07:40 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01994 for ietf-outbound.10@ietf.org; Wed, 4 Jul 2001 03:40:02 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@songbird.com [208.184.79.7]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01921 for <ietf@ietf.org>; Wed, 4 Jul 2001 03:33:48 -0400 (EDT)
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112]) by joy.songbird.com (8.9.3/8.9.3) with ESMTP id AAA27764; Wed, 4 Jul 2001 00:34:31 -0700
Message-Id: <5.1.0.14.2.20010704002140.036d0ce0@dcrocker.net>
X-Sender: dhc2@dcrocker.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 04 Jul 2001 00:36:03 -0700
To: ietf-openproxy@IMC.ORG, ietf@ietf.org
From: Dave Crocker <dhc2@dcrocker.net>
Subject: Re: OPES charter proposal again.
In-Reply-To: <200107040603.XAA08197@shell9.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Loop: ietf@ietf.org
At 11:03 PM 7/3/2001, James P. Salsman wrote: >I hope that the latest attempt at the OPES charter is resoundingly >rejected by the IESG. The key task statement in the opening paragraph of the draft proposal is: "define application-level protocols enabling such intermediaries to incorporate services that operate on messages transported by HTTP and RTP/RTSP." "Incorporate services" is vague. Or rather, it says nothing useful. The opening paragraph of a charter is to be widely distributed, to help people decide what a working group is doing and whether it is relevant to one's own work. The current proposal language is frankly a Rorschach for anyone with any HTTP-related activity that might involve an intermediary. Later language in the draft do not assuage this fear: "protocols to be defined provide a framework for integrating a wide range of services". Specifics (or even examples) are not provided. Honest. In spite of considerable experience writing and reading IETF charters, I can not tell what problem is to be solved, never mind how. d/ Addendum #1: Either as an minor irritation, or as a major demonstration of deception -- and I can't quite decide which -- the iCAP web page <http://www.i-cap.org/> uses the IETF logo in a fashion that can easily be taken to imply IETF endorsement for <http://search.ietf.org/internet-drafts/draft-elson-opes-icap-01.txt>. Addendum #2: Isn't an implied promise to integrate HTTP and RTP/RTSP rather ambitious? ---------- Dave Crocker <mailto:dcrocker@brandenburg.com> Brandenburg InternetWorking <http://www.brandenburg.com> tel +1.408.246.8253; fax +1.408.273.6464
- OPES charter proposal again. Lloyd Wood
- Re: OPES charter proposal again. Paul Hoffman / IMC
- Re: OPES charter proposal again. Michael W. Condry
- Re: OPES charter proposal again. Brian E Carpenter
- Re: OPES charter proposal again. Michael W. Condry
- Re: OPES charter proposal again. James P. Salsman
- Re: OPES charter proposal again. Dave Crocker
- Re: OPES charter proposal again. Michael W. Condry
- Re: OPES charter proposal again. Michael W. Condry
- Re: OPES charter proposal again. Micah Beck
- RE: OPES charter proposal again. Tomlinson, Gary
- Re: OPES charter proposal again. Lee Rafalow
- Re: OPES charter proposal again. Brian E Carpenter
- Re: OPES charter proposal again. Michael W. Condry
- RE: OPES charter proposal again. Ian Cooper
- Re: OPES charter proposal again. Lloyd Wood