Instant Message and Presence Transfer Protocols
draft-hudson-impp-transfer-proposal-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Greg Hudson | ||
| Last updated | 2000-05-04 | ||
| 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
This document specifies transfer protocols for instant messages and presence information. The Presence Information Transfer Protocol (PITP) allows clients to set presence information for presentities they control and to request presence information from other presentities. The Instant Message Transfer Protocol (IMTP) allows clients to send and receive instant messages. Both protocols can also be used to relay instant message and presence requests between servers as necessary. These protocols are specified in the same document because they have very similar structure. However, they are two logically separate protocols. Sections specific to one or the other protocol will be recognizeable by a leading 'PITP' or 'IMTP'.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)