Requirement for Analysis of SIP Paths
draft-roychowdhury-sipping-pathtrace-reqts-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Arjun Roychowdhury | ||
| Last updated | 2002-08-27 | ||
| 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
There is no defined mechanism today by which SIP proxies can insert path related information in a SIP message that is being routed across a network. As an example, a network administrator may want to trace the path as a SIP message traverses across her network to detect failure points. As another example, a user may want to discover capabilities of servers in the path of a call. Although there is an informal mention of using the OPTIONS method to achieve the latter example [1], there is no defined way to achieve the same today.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)