>Date: Fri, 12 Jan 2001 11:27:56 -0800
>From: Mark Nottingham <mnot@akamai.com>
>To: Scott Brim <sbrim@cisco.com>
>Cc: webi@lists.equinix.com
>Subject: Re: Proposed charter
>User-Agent: Mutt/1.2.5i
>Sender: owner-webi@equinix.com
>
>
>Very valid point.
>
>I'll take this as a suggestion to strip out the two sections
>detailing the approaches to the work items, and reduce them to
>bare-bones work items (letting the motivation above put a general
>scope on the problem). If anyone has a suggestion for more
>substantial content here that doesn't presuppose the requirements too
>much, please send something ASAP.
>
>The only catch is that I don't know if we can roadmap the delivery of
>anything past the requirements doc if we don't have an understanding
>of what needs to be delivered.
>
>Also, note that the names for the work items are tentative - they're
>just there so we have something to refer to. I imagine that we'll
>finialize those once we get the requirements solidified.
>
>Cheers,
>
>
>
>
>On Fri, Jan 12, 2001 at 02:09:40PM -0500, Scott Brim wrote:
> > Just one question ...
> >
> > On 11 Jan 2001 at 18:16 -0800, Mark Nottingham apparently wrote:
> > > 1) Gather requirements for, and specify, a Resource Update Protocol,
> > > consisting of:
> > >
> > > a) A framework containing:
> > >
> > > 1. A channel mechanism with associated channel advertisement,
> > > description subscription and reliability functions,
> > >
> > > 2. A message format for the channel payload, and
> > >
> > > 3. A scalable delivery model for messages.
> > >
> > > b) Specification of a Web Resource Invalidation Protocol as a
> > > payload for this framework, and optionally other appropriate
> > > payloads, as determined by the requirements.
> >
> > Could we possibly back up one step and treat channel mechanisms as a
> > possible solution instead of a given? I mean, let's start with the real
> > requirements. If you believe channels have already been justified
> > somewhere, could you point me to that RFC? Channels imply basic
> > assumptions about how intermediaries relate to their content sources.
> >
> > ...Scott
>
>--
>Mark Nottingham, Research Scientist
>Akamai Technologies (San Mateo, CA)
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:30 MST