SIP Security Framework
draft-thomas-sip-sec-framework-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Matt Thomas | ||
Last updated | 2001-07-12 | ||
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 SIP security framework draft defines a range of possible threats that a SIP message in transit might be subject to, a list of require- ments, and provides the raw fodder for an extensible framework to counter many of the threats using various crypto systems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)