RVP Schemas
draft-dusseault-rvp-schema-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lisa M. Dusseault , Jeff Bone | ||
| Last updated | 1998-03-16 | ||
| 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 RVP protocol [2] can be used to query properties of objects, subscribe to certain kinds of events, and send instant messages to objects. These objects are often users, but there are other classes of objects as well. A schema needs to be defined which applies to all kinds of RVP objects, as well as more detailed schemas for the most commonly used objects, users and groups. The required properties for all RVP objects include common name (Cn), schema type and access control list. The required properties for a user object, which represents a single human user of the system, include status, status message, email address and directory server address. The required properties for a group object, which represents a list of objects which may be messaged all at once by messaging this group, include member- count and owner.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)