Transmitting Subscriber Identification in iCAP
draft-beck-opes-icap-subid-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Andre Beck , Markus Hofmann | ||
| Last updated | 2001-11-02 | ||
| 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 Internet Content Adaptation Protocol (iCAP) [1] provides simple, object-based content vectoring for HTTP services. For some services, the iCAP server needs to identify the source of the encapsulated HTTP message. This document specifies user-defined header extensions of iCAP, which allow the iCAP client to include the IP address and possibly a subscriber ID of the source of the encapsulated HTTP message.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)