Architecture and Design Principles of the Session Initiation Protocol (SIP)
draft-rosenberg-sipping-sip-arch-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Henning Schulzrinne , Jonathan Rosenberg | ||
| Last updated | 2005-07-20 | ||
| 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 Session Initiation Protocol (SIP) and its many extensions and supporting technologies define a solution for multimedia communications on the Internet. Much of the design and architecture for SIP is based on a key set of architectural principles which, while commonly discussed on mailing lists and other forums, have not been explicitly captured. This document seeks to rectify that gap by outlining the key set of architectural and design principles underlying SIP.
Authors
Henning Schulzrinne
Jonathan Rosenberg
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)