Requirements for indication of features supported by a SIP proxy
draft-ietf-sipcore-proxy-feature-reqs-03
| Document | Type | Expired Internet-Draft (sipcore WG) | |
|---|---|---|---|
| Last updated | 2012-06-07 (latest revision 2011-12-05) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document (wg milestone: May 2012 - WGLC on requirements... ) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-sipcore-proxy-feature-reqs-03.txt
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
(christer.holmberg@ericsson.com)
Ivo Sedlacek
(ivo.sedlacek@ericsson.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)