RPIDS -- Rich Presence Information Data Format for Presence Based on the Session Initiation Protocol (SIP)
draft-ietf-simple-rpids-01
| Document | Type |
Replaced Internet-Draft
(simple WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Henning Schulzrinne | ||
| Last updated | 2003-07-02 (Latest revision 2003-06-24) | ||
| Replaced by | RFC 4480 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-simple-rpid | |
| Consensus boilerplate | Unknown | ||
| 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 Rich Presence Information Data Format for the Session Initiation Protocol (SIP) (RPIDS) adds elements to the Presence Information Data Format (PIDF) that provide additional information about the presentity and its contacts. This information can be translated into call routing behavior or be delivered to watchers. The information is designed so that much of it can be derived automatically, e.g., from calendar files or user activity.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)