- From: Ludin, Stephen <sludin@akamai.com>
- Date: Thu, 26 Jul 2012 13:26:58 -0500
- To: "Eric J. Bowman" <eric@bisonsystems.net>, Mark Nottingham <mnot@mnot.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 7/25/12 12:36 PM, "Eric J. Bowman" <eric@bisonsystems.net> wrote: >Mark Nottingham wrote: >> >> The resulting specification(s) are expected to be meet these goals >> for common existing deployments of HTTP; in particular, Web browsing >> (desktop and mobile), Web serving (at a variety of scales), and >> intermediation (by proxies, corporate firewalls, "reverse" proxies >> and Content Delivery Networks). >> > >Please change "CDNs" to "caches" to avoid confusion over whether we're >talking about a new architectural style. "Caches" can include CDNs, >but CDNs does not include the shared-cache architecture which got the >Web where it is. > >-Eric > If we want to refine Mark's text that then equating a CDN to a cache is not accurate. Today's CDNs do cache, but they more importantly provide acceleration, optimized routing, security, edge logic, content assembly, and content modification just to name a few. Rather than open that can of worms, I think keeping CNDs in the proposed straw-man text would be better. Alternatively, we drop the parenthetical list and just go with 'intermediation'. -stephen
Received on Thursday, 26 July 2012 18:27:37 UTC