The SIP Proxy-Supported header field
draft-hoeneisen-sip-proxy-supported-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bernie Hoeneisen | ||
| Last updated | 2001-07-13 | ||
| 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 Session Initiation Protocol (SIP) provides a mechanism that allows a User Agent Client (UAC) to request that a particular protocol extension has to be used to process the request. The User Agent Server (UAS) declines the request if it does not support the extension. Recently also means have been defined for the User Agent Server (UAS) to determine which extensions are supported by the User Agent Client (UAC). Furthermore there are also means for requiring proxy servers to understand certain features.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)