RFC 2779 (rfc2779) - Page 3 of 26
Instant Messaging / Presence Protocol Requirements
Alternative Format: Original Text Document
RFC 2779 Instant Messaging/Presence Protocol February 2000
1. Terminology
The following terms are defined in [RFC 2778] and are used with those
definitions in this document:
ACCESS RULES
CLOSED
FETCHER
INSTANT INBOX
INSTANT MESSAGE
NOTIFICATION
OPEN
POLLER
PRESENCE INFORMATION
PRESENCE SERVICE
PRESENTITY
PRINCIPAL
PROXY
SERVER
STATUS
SUBSCRIBER
SUBSCRIPTION
WATCHER
The terms MUST and SHOULD are used in the following sense while
specifying requirements:
MUST: A proposed solution will have to meet this requirement.
SHOULD: A proposed solution may choose not to meet this requirement.
Note that this usage of MUST and SHOULD differs from that of RFC
2119.
Additionally, the following terms are used in this document and
defined here:
ADMINISTRATOR: A PRINCIPAL with authority over local computer and
network resources, who manages local DOMAINS or FIREWALLS. For
security and other purposes, an ADMINISTRATOR often needs or wants to
impose restrictions on network usage based on traffic type, content,
volume, or endpoints. A PRINCIPAL's ADMINISTRATOR has authority over
some or all of that PRINCIPAL's computer and network resources.
DOMAIN: A portion of a NAMESPACE.
ENTITY: Any of PRESENTITY, SUBSCRIBER, FETCHER, POLLER, or WATCHER
(all defined in [RFC 2778]).
Day, et al. Informational