Semantic Description of SIMPLE List Manipulation Operations
draft-isomaki-simple-list-man-sem-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Markus Isomaki | ||
| Last updated | 2002-11-01 | ||
| 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
In SIMPLE based presence and messaging applications, it is necessary for the user to be able to configure a number of pieces of information. One of the most common types of information is a list of URIs. List management is useful outside the scope of SIMPLE as well, for instance in conferencing. There are many reasons why it would be beneficial to manage the lists in a similar fashion regardless of the application. Before the selection of the actual protocol(s) to manage the lists there is a need to describe their semantics on an abstract level. This document proposes the semantics for SIMPLE list manipulation protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)