idnits 2.17.1 draft-ietf-apex-presence-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3343 5 Title: The Application Exchange (APEX) Presence Service 6 Author(s): M. Rose, G. Klyne, D. Crocker 7 Status: Experimental 8 Date: April 2003 9 Mailbox: mrose@dbc.mtview.ca.us, 10 gk@ninebynine.org, dcrocker@brandenburg.com 11 Pages: 23 12 Characters: 42043 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-apex-presence-06.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3343.txt 19 This memo describes the Application Exchange (APEX) presence service, 20 addressed as the well-known endpoint "apex=presence". The presence 21 service is used to manage presence information for APEX endpoints. 23 This memo defines an Experimental Protocol for the Internet community. 24 It does not specify an Internet standard of any kind. Discussion and 25 suggestions for improvement are requested. Distribution of this memo 26 is unlimited. 28 This announcement is sent to the IETF list and the RFC-DIST list. 29 Requests to be added to or deleted from the IETF distribution list 30 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 31 added to or deleted from the RFC-DIST distribution list should 32 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 34 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 35 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 36 help: ways_to_get_rfcs. For example: 38 To: rfc-info@RFC-EDITOR.ORG 39 Subject: getting rfcs 41 help: ways_to_get_rfcs 43 Requests for special distribution should be addressed to either the 44 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 45 specifically noted otherwise on the RFC itself, all RFCs are for 46 unlimited distribution.echo 47 Submissions for Requests for Comments should be sent to 48 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 49 Authors, for further information.