Third Party Authorization in the Session Initiation Protocol
draft-lawrence-sip-3rd-party-authorization-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Scott Lawrence | ||
| Last updated | 2009-05-03 | ||
| 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 describes some circumstances that are common in SIP deployments which lack a rigorous authorization model, and points out some ways in which this has resulted in poor security characteristics. The purpose of this document is to stimulate discussion of the identified problem and proposed requirements for any solution. Comments are solicited, and should be directed to the DISPATCH working group list at 'dispatch@ietf.org'.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)