Retargeting and Security in SIP: A Framework and Requirements
draft-peterson-sipping-retarget-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jon Peterson | ||
| Last updated | 2005-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
Retargeting, the alteration by intermediaries of the destination of a Session Initiation Protocol (SIP) request, is a common practice performed during the routing of a call. Some forms of retargeting, however, give rise to security problems and potential functional gaps in SIP. This document provides a general framework for discussion of the security problems relating to retargeting, and gives requirements for mechanisms that might overcome these problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)