Re: [core] draft-hartke-core-stateless

> -----Original Message-----
> From: core <core-bounces@ietf.org> On Behalf Of Klaus Hartke
> Sent: Wednesday, September 12, 2018 1:35 AM
> To: 'Core' <core@ietf.org>
> Subject: Re: [core] draft-hartke-core-stateless
> 
> Christian Amsüss wrote:
> > > But proxies also generate responses themselves, e.g., from cached
> > > responses or in case of errors (5.02, 5.04). We don't want clients
> > > to receive the extended token from another client or no extended
> > > token at all when a proxy does not support the option.
> >
> > As long as the option is part of the cache key, any cached response
> > would need to have a matching request Extended-Token and thus would
> > have a matching response Extended-Token as well.
> 
> I don't think it's very desirable to require tokens to match when serving a
> cached response.
> 
> And there's still the other half of the problem: An unaware proxy won't include
> the option in responses it generates itself.

Reiterate -

For an unaware proxy having the item as part of the cached key prevents it from generating responses itself.

Text which says that aware proxies can omit the option from the cached key allows them to generate responses out of the cache and they will know that they need to process and return the option.

Jim

> 
> Klaus
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core