On Mon, Oct 02, 2017 at 09:58:34PM +0000, Binu Ramakrishnan wrote:
> My preference would be not to cache the policy by the reverse-proxy. Like
> Dan said, the provider can handle more traffic than the proxy, hence I
> think caching is not a requirement.
The provider may not require it, but it is useful for the provider's
customer. You may be too used to the provider's point of view. :-)
> Provider may set appropriate
> Cache-Control HTTP header to prevent caching
> Example:Cache-Control: no-cache, no-store, must-revalidate
I think that's too strict. After all, policies will be cached by
MTAs for weeks or months. So allowing them to be cached for a few
minutes by a reverse proxy makes good sense.
> If caching is desired, then provider may set a Cache-Control policy with
> an short TTL. The proxy may cache the policy until the cache expires.
That'd be the advice I'd like to see in the draft.
--
Viktor.
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
