Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Usages for Setting Presence Authorization
draft-ietf-simple-xcap-auth-usage-01
| Document | Type |
Replaced Internet-Draft
(simple WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Jonathan Rosenberg | ||
| Last updated | 2004-07-23 (Latest revision 2003-10-29) | ||
| Replaced by | draft-ietf-simple-presence-rules | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-simple-presence-rules | |
| 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
This document describes three usages of the Extensible Markup Language (XML) Configuration Access Protocol (XCAP) that allow a client to provide authorization decisions regarding watchers of their presence. The first of these usages, called permission-statements, contains statements about what permissions are to be granted to watchers of presence. The second of these usages, called compound-permissions, allows a client to define new permissions as combinations of other defined permissions. The third usage, called supported-permissions, allows a client to determine what permissions are understood by the provider.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)