Requirements for Header Integrity Protection for the Session Initiation Protocol (SIP)
draft-schubert-sipping-header-integrity-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Shida Schubert | ||
| Last updated | 2006-10-18 | ||
| 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 document lays out a set of requirements related to integrity protection over the headers for the Session Initiation Protocol (SIP). While mechanism such as SIP-Identity and S/MIME may be used to provide integrity protection between the end-points, it can not provide integrity protections over some of the headers which may benefit from having an integrity protection.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)