[Search] [pdf|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 rfc3343                      Experimental
A new Request for Comments is now available in online RFC libraries.


        RFC 3343

        Title:      The Application Exchange (APEX) Presence Service
        Author(s):  M. Rose, G. Klyne, D. Crocker
        Status:     Experimental
        Date:       April 2003
        Mailbox:    mrose@dbc.mtview.ca.us,
                    gk@ninebynine.org, dcrocker@brandenburg.com
        Pages:      23
        Characters: 42043
        Updates/Obsoletes/SeeAlso: None

        I-D Tag:    draft-ietf-apex-presence-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3343.txt


This memo describes the Application Exchange (APEX) presence service,
addressed as the well-known endpoint "apex=presence".  The presence
service is used to manage presence information for APEX endpoints.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.