RTC Provisioning Requirements
draft-houri-speermint-usecase-presence-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Avshalom Houri | ||
| Last updated | 2006-10-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 document describes several use cases for peering between two or more communities that provide real time communications services and presence and IM in particular. The communities create a peering relationship between themselves thus enabling their users to collaborate with users on other communities. The target of the document is to help understanding the requirements for peering between domains with regard to real time services
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)