Origin/Access Content Peering for HTTP
draft-rzewski-oacp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Niel Robertson , Phillip Rzewski , Joe Bai | ||
| Last updated | 2000-11-17 | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 goal of 'content peering' is to logically connect content-based networks together to allow content providers increased control of content presentation in remote networks and to receive detailed information on the utilization of their content. The Origin/Access Content Peering (OACP) implementation provides a scalable mechanism for content providers to originate this control and also to receive utilization data.
Authors
Niel Robertson
Phillip Rzewski
Joe Bai
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)