ALTO Caching
draft-madhavan-alto-caching-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Sreekanth Madhavan , Nandiraju Ravishankar | ||
| Last updated | 2013-02-02 (Latest revision 2012-08-01) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The specification of the ALTO protocol uses map based approaches assuming that the information provided is static for a longer period of time. The purpose of this memo is to provide a mechanism where ALTO clients cache the map information and the servers provide the expiration time for invalidation.
Authors
Sreekanth Madhavan
Nandiraju Ravishankar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)