A Mechanism to Secure SIP Identity headers inserted by Intermediaries
draft-barnes-sipping-sec-inserted-info-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mary Barnes | ||
| Last updated | 2004-12-07 | ||
| 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
This draft discusses a standard mechanism for securing information in SIP requests and responses, inserted by intermediaries, which may be used by other intermediaries or the endpoints as the basis for services. The requirements are based on the need for a general middle-to-middle and middle-to-end security mechanism applicable to both headers and message bodies. This mechanism is optional, however, the use of it enhances the overall security of SIP by ensuring the integrity of the information inserted by an intermediary.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)