Providing guidance for Session Initiation Protocol (SIP) services
draft-ligot-bliss-sip-services-guide-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Arnaud Ligot , Thomas Froment | ||
| Last updated | 2008-07-11 (Latest revision 2008-02-22) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-ligot-bliss-sip-services-guide-02.txt
Abstract
Implementing Session Initiation Protocol (SIP) advanced features and services requires to use numerous specifications. Today, for each service in the scope of BLISS, one can already find references to many possible specifications which do not cover the same things. Some of them are primitive operations, requirements or call flow examples, some have a scope larger than the others, or can not be compared at the same level. Very often, architecture hypothesis are hidden behind the same service name, either assuming that an intermediary; like an application server, has an active role in the service, or, as opposed, assuming a pure end-to-end model where only endpoint implementations are involved. The goal of this document is not to present the best solutions or give recommendations; but to give an overview of every standard specification related to these services, centralizing and categorizing them as input to the working group.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)