Securing REFER - Options discussed at IETF53
draft-sparks-sip-sec-options-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Robert Sparks | ||
Last updated | 2002-04-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 memo documents and expands on the discussion on securing REFER at the IETF53 SIP meeting. It explores several possible solution mechanisms with rough discussion of the pros and cons of each. This memo proposes futher development of an S/MIME based solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)