Analysis: HTTP Authentication for SIP
draft-khartabil-sip-auth-analysis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hisham Khartabil | ||
| Last updated | 2004-02-05 | ||
| 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 stateless, challenge-based mechanism for authentication that is based on authentication in HTTP. RFC 3261 fails to indicate the behaviour of SIP intermediaries and User Agents in certain scenarios. This documents presents such scenarios, analysis the currently available text, and where possible, offers a solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)