Request Header Integrity in SIP and HTTP Digest using
Predictive Nonces
draft-rosenberg-sip-http-pnonce-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jonathan Rosenberg | ||
| Last updated | 2001-06-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
The HTTP Digest algorithm, specified in RFC 2617, allows for authentication of a request, along with integrity checks over the method, request URI, and optionally, the body. HTTP Digest is the primary client authentication mechanism used by SIP. However, Digest does not provide for integrity checks over several key SIP headers, including the To, From, Call-ID and Contact headers. We define a mechanism for supporting integrity over these headers, using a new algorithm we call predictive nonces. The mechanism requires no changes in clients, and no protocol changes. It requires only a change in the way the nonce is computed by servers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)