Requirements for indication of features supported by a SIP proxy
draft-ietf-sipcore-proxy-feature-reqs-03
| Document | Type |
Expired Internet-Draft
(sipcore WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christer Holmberg , Ivo Sedlacek | ||
| Last updated | 2012-06-07 (Latest revision 2011-12-05) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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) "Caller Preferences" extension defined in RFC 3840 provides a mechanism that allows a SIP message to convey information relating to the originator's supported features/ capabilities. This document defines requirements for a mechanism that would allow SIP proxies to convey information relating to the proxy's supported features/capabilities.
Authors
Christer Holmberg
Ivo Sedlacek
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)