draft-ietf-httpbis-targeted-cache-control-03.txt   draft-ietf-httpbis-targeted-cache-control-latest.txt 
HTTP Working Group S. Ludin HTTP Working Group S. Ludin
Internet-Draft Akamai Internet-Draft Akamai
Intended status: Standards Track M. Nottingham Intended status: Standards Track M. Nottingham
Expires: July 8, 2022 Fastly Expires: July 18, 2022 Fastly
Y. Wu Y. Wu
Cloudflare Cloudflare
January 4, 2022 January 14, 2022
Targeted HTTP Cache Control Targeted HTTP Cache Control
draft-ietf-httpbis-targeted-cache-control-03 draft-ietf-httpbis-targeted-cache-control-latest
Abstract Abstract
This specification defines a convention for HTTP response header This specification defines a convention for HTTP response header
fields that allow cache directives to be targeted at specific caches fields that allow cache directives to be targeted at specific caches
or classes of caches. It also defines one such header field, or classes of caches. It also defines one such header field,
targeted at Content Delivery Network (CDN) caches. targeted at Content Delivery Network (CDN) caches.
About This Document About This Document
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 8, 2022. This Internet-Draft will expire on July 18, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 8, line 4 skipping to change at page 8, line 4
4. IANA Considerations 4. IANA Considerations
Please register the following entry in the Hypertext Transfer Please register the following entry in the Hypertext Transfer
Protocol (HTTP) Field Name Registry defined by [HTTP]: Protocol (HTTP) Field Name Registry defined by [HTTP]:
o Field Name: CDN-Cache-Control o Field Name: CDN-Cache-Control
o Status: permanent o Status: permanent
o Specification Document: [this document] o Specification Document: [this document]
o Comments: Cache-Control directives targeted at Content Delivery o Comments: Cache directives targeted at Content Delivery Networks
Networks
5. Security Considerations 5. Security Considerations
The security considerations of HTTP caching [HTTP-CACHING] apply. The security considerations of HTTP caching [HTTP-CACHING] apply.
The ability to carry multiple caching policies on a response can The ability to carry multiple caching policies on a response can
result in confusion about how a response will be cached in different result in confusion about how a response will be cached in different
systems, if not used carefully. This might result in unintentional systems, if not used carefully. This might result in unintentional
reuse of responses with sensitive information. reuse of responses with sensitive information.
 End of changes. 5 change blocks. 
6 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/