Representational State Transfer (REST) for Feature Configuration in Session Initiation Protocol (SIP)
draft-griffin-bliss-rest-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Keith Griffin , Jonathan Rosenberg | ||
| Last updated | 2008-10-27 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
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-griffin-bliss-rest-00.txt
Abstract
In order to provide interoperable implementations of certain Session Initiation Protocol (SIP) based features, such as automated call handling, it is necessary for devices to configure network servers with feature data. An example is a call forwarding number for a call forwarding service. This document introduces the concept of Representational State Transfer (REST) and gives an example of how REST can be used for such configuration.
Authors
Keith Griffin
Jonathan Rosenberg
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)