[decade] Remote Get Object Message

["Woundy, Richard" <[e-mail]>]

Folks,

In Thursday's session, we discussed how to implement the Remote Get Object message. One proposal is to use HTTP Post with a new X-DECADE-ORIGIN header; another proposal is to define a new HTTP message. See slide 3 of <http://www.ietf.org/proceedings/83/slides/slides-83-decade-4.pdf<http://www.ietf.org/proceedings/83/slides/slides-83-decade-4.pdf<>> and <http://tools.ietf.org/html/draft-wang-decade-drp-03#section-8<http://tools.ietf.org/html/draft-wang-decade-drp-03#section-8>>>.

My thought (as an individual contributor, not as co-chair) is to use existing HTTP Get headers and leverage the base functionality of an HTTP caching proxy in DECADE. The local "DECADE" server would act as a caching proxy (with additional functionality of course) in order to reach the remote "DECADE" server, and cache the contents of the reply in the "DECADE" storage. I have a "non-transparent proxy" behavior in mind, per the definition of "proxy" in RFC 2616 (http://tools.ietf.org/html/rfc2616#section-1.3). Also see <http://tools.ietf.org/html/rfc2616#section-13>, <http://tools.ietf.org/html/rfc3040>, and perhaps <http://tools.ietf.org/html/rfc3143> as well.

Did we fully explore this possibility? As a co-chair, I can assure you that it would be much better to leverage existing protocols and standards, versus inventing new ones.

-- Rich