Example call flows using SIP security mechanisms
draft-jennings-sip-sec-flows-03
| Document | Type |
Replaced Internet-Draft
(individual in tsv area)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cullen Fluffy Jennings , Kumiko Ono | ||
| Last updated | 2015-10-14 (Latest revision 2005-07-18) | ||
| Replaced by | draft-ietf-sipping-sec-flows | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sipping-sec-flows | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Allison J. Mankin | ||
| Send notices to | housley@vigilsec.com, rsparks@nostrum.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document shows call flows demonstrating the use of SIPS, TLS, and S/MIME in SIP. This draft provides information that helps implementers build interoperable SIP software. It is purely informational. To help facilitate interoperability testing, it includes certificates used in the example call flows and a CA certificate to create certificates for testing. This work is being discussed on the sip@ietf.org mailing list.
Authors
Cullen Fluffy Jennings
Kumiko Ono
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)