W3C home > Mailing lists > Public > ietf-discuss@w3.org > February 1999

Re: Application "core protocol" BOF/WG idea

From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
Date: Mon, 01 Feb 1999 17:15:36 -0800
To: Chris Newman <Chris.Newman@innosoft.com>
cc: discuss@apps.ietf.org
Message-ID: <9902011715.aa16600@paris.ics.uci.edu>
>I'd prefer to focus on a single "core protocol" based on the
>connection-based stateful client-server structure that most successful
>IETF application protocols follow.  There are obviously other protocol
>models with which we have far less experience, but most of those _are_
>research problems and thus out-of-scope. 

It has been my experience that an application protocol must match
the interaction style of the application components.  Otherwise, it will
fail to meet the minimal performance requirements of that application
and be replaced by an application protocol that does.  For example,
"stateful" excludes HTTP and any reasonable transfer protocol for
the Web.

I think that it won't be useful to come up with a "core" application
protocol unless those core components can adapt according to multiple
interaction styles and multiple underlying transports.  If that is too
large a scope, then the "common core" being developed must be limited
to a single interaction style.  Besides, if you are going to limit the
core to things occurring in two or more successful IETF protocols, then
the only application being supported is store-and-forward messaging.
I think a "store-and-forward core" is far more likely to be usable by
future protocols than a general application core that only considers
a subset of applications.

....Roy
Received on Monday, 1 February 1999 21:15:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:59 UTC