SDP codepoints for gateway control
draft-schwarz-mmusic-sdp-for-gw-05
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Albrecht Schwarz , Christian Groves | ||
| Last updated | 2016-11-14 (latest revision 2016-05-02) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-schwarz-mmusic-sdp-for-gw-05.txt
Abstract
SDP is used in many signalling protocols at call control level (such as SAP, SIP, BICC), bearer control level (such as RTSP, IPBCP) and gateway control level (such as H.248/MEGACO, MGCP). Scope of this RFC is related to gateway control specific SDP usage. Gateway control protocols do NOT usually define and introduce any new SDP parameters, however, gateway control protocols need specific SDP parameter values in addition to those defined at call or bearer control level. Such SDP codepoints are collected by this RFC with the purpose of registration with IANA.
Authors
Albrecht Schwarz
(albrecht.schwarz@nokia.com)
Christian Groves
(Christian.Groves@nteczone.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)