Response Identity in Session Initiation Protocol
draft-cao-sip-response-identity-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Feng Cao | ||
| Last updated | 2006-01-10 | ||
| 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 mechanism for securely providing responder's identity in response message is missing in the current Session Initiation Protocol. Due to different call scenarios, the exact response identity is hard to guess through the existing response message. This draft describes some extensions for providing SIP response identity and two security mechanisms for verifying the integrity of response identity. It does so by defining new header fields as well as one new response code. Furthermore, the issue of how to require the presence of response identity in one SIP dialog is also discussed with one solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)