Requirements for SIP Security Mechanism Agreement
draft-uusitalo-sipping-algorithm-agreement-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Jari Arkko | ||
Last updated | 2002-02-15 | ||
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) is an application-layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution and multimedia conferences. SIP has a number of security mechanisms used for hop- by-hop or end-to-end protection. In this document we discuss requirements concerning SIP security mechanism agreement.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)