Input 3rd-Generation Partnership Project (3GPP) Communications Service Identifiers Requirements on the Session Initiation Protocol (SIP)
draft-loreto-sipping-3gpp-ics-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Salvatore Loreto , Stephen Terrill | ||
| Last updated | 2006-06-19 | ||
| 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
The 3rd-Generation Partnership Project (3GPP) is developing the capability to support different communication services on IP Multimedia Subsystem (IMS) as a SIP infrastructure, such as push-to- talk over cellular (PoC), Multimedia Telephony or IMS messaging. As there are different services and is not safe to rely on the expressed media as a means to identify the requested communication service because the media may be used in different communication services, then there is the need to have an unambiguous way of identifying communication services and applications utilizing the logic of communication services as explicitly as possible. In this document, we express the requirements identified by 3GPP to support the identification of communication services and applications on a Session Initiation Protocol (SIP) infrastructure and IMS applications using them.
Authors
Salvatore Loreto
Stephen Terrill
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)