draft-ietf-apex-presence-05.txt   draft-ietf-apex-presence-06.txt 
Network Working Group M. Rose Network Working Group M. Rose
Internet-Draft Invisible Worlds, Inc. Internet-Draft Dover Beach Consulting, Inc.
Expires: February 12, 2002 G. Klyne Expires: July 15, 2002 G. Klyne
Baltimore Technologies MIMEsweeper Group
D. Crocker D. Crocker
Brandenburg Consulting Brandenburg Consulting
August 14, 2001 January 14, 2002
The APEX Presence Service The APEX Presence Service
draft-ietf-apex-presence-05 draft-ietf-apex-presence-06
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at http://
http://www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 12, 2002. This Internet-Draft will expire on July 15, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This memo describes the APEX presence service, addressed as the well- This memo describes the APEX presence service, addressed as the well-
known endpoint "apex=presence". The presence service is used to known endpoint "apex=presence". The presence service is used to
manage presence information for APEX endpoints. manage presence information for APEX endpoints.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Management of Presence Information . . . . . . . . . . . . . . 4 2. Use and Management of Presence Information . . . . . . . . . . 4
2.1 Update of Presence Information . . . . . . . . . . . . . . . . 5 2.1 Update of Presence Information . . . . . . . . . . . . . . . . 5
2.2 Distribution of Presence Information . . . . . . . . . . . . . 7 2.2 Distribution of Presence Information . . . . . . . . . . . . . 7
2.3 Distribution of Watcher Information . . . . . . . . . . . . . 10 2.3 Distribution of Watcher Information . . . . . . . . . . . . . 10
3. Format of Presence Entries . . . . . . . . . . . . . . . . . . 13 3. Format of Presence Entries . . . . . . . . . . . . . . . . . . 13
4. The Presence Service . . . . . . . . . . . . . . . . . . . . . 14 4. The Presence Service . . . . . . . . . . . . . . . . . . . . . 14
4.1 Use of XML and MIME . . . . . . . . . . . . . . . . . . . . . 15 4.1 Use of XML and MIME . . . . . . . . . . . . . . . . . . . . . 15
4.2 The Subscribe Operation . . . . . . . . . . . . . . . . . . . 16 4.2 The Subscribe Operation . . . . . . . . . . . . . . . . . . . 16
4.3 The Watch Operation . . . . . . . . . . . . . . . . . . . . . 18 4.3 The Watch Operation . . . . . . . . . . . . . . . . . . . . . 18
4.4 The Publish Operation . . . . . . . . . . . . . . . . . . . . 20 4.4 The Publish Operation . . . . . . . . . . . . . . . . . . . . 20
4.5 The Terminate Operation . . . . . . . . . . . . . . . . . . . 22 4.5 The Terminate Operation . . . . . . . . . . . . . . . . . . . 22
4.6 The Notify Operation . . . . . . . . . . . . . . . . . . . . . 23 4.6 The Notify Operation . . . . . . . . . . . . . . . . . . . . . 23
4.7 The Reply Operation . . . . . . . . . . . . . . . . . . . . . 23 4.7 The Reply Operation . . . . . . . . . . . . . . . . . . . . . 23
5. Registration: The Presence Service . . . . . . . . . . . . . . 24 5. Registration: The Presence Service . . . . . . . . . . . . . . 24
6. The Presence Service DTD . . . . . . . . . . . . . . . . . . . 25 6. The Presence Service DTD . . . . . . . . . . . . . . . . . . . 25
7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Security Considerations . . . . . . . . . . . . . . . . . . . 28
References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 29
A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
B. Revision History . . . . . . . . . . . . . . . . . . . . . . . 31 B. Revision History . . . . . . . . . . . . . . . . . . . . . . . 31
B.1 Changes from draft-ietf-apex-presence-04 . . . . . . . . . . . 31 B.1 Changes from draft-ietf-apex-presence-05 . . . . . . . . . . . 31
B.2 Changes from draft-ietf-apex-presence-03 . . . . . . . . . . . 31 B.2 Changes from draft-ietf-apex-presence-04 . . . . . . . . . . . 31
B.3 Changes from draft-ietf-apex-presence-02 . . . . . . . . . . . 31 B.3 Changes from draft-ietf-apex-presence-03 . . . . . . . . . . . 31
B.4 Changes from draft-ietf-apex-presence-01 . . . . . . . . . . . 31 B.4 Changes from draft-ietf-apex-presence-02 . . . . . . . . . . . 31
B.5 Changes from draft-ietf-apex-presence-00 . . . . . . . . . . . 31 B.5 Changes from draft-ietf-apex-presence-01 . . . . . . . . . . . 31
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 32 B.6 Changes from draft-ietf-apex-presence-00 . . . . . . . . . . . 32
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
This memo describes a presence service that is built upon the APEX This memo describes a presence service that is built upon the APEX
[1] "relaying mesh". The APEX presence service is used to manage [1] "relaying mesh". The APEX presence service is used to manage
presence information for APEX endpoints. presence information for APEX endpoints.
APEX, at its core, provides a best-effort datagram service. Within APEX, at its core, provides a best-effort datagram service. Within
an administrative domain, all relays must be able to handle messages an administrative domain, all relays must be able to handle messages
for any endpoint within that domain. APEX services are logically for any endpoint within that domain. APEX services are logically
skipping to change at page 4, line 5 skipping to change at page 4, line 5
APEX applications communicate with the presence service by exchanging APEX applications communicate with the presence service by exchanging
data with the well-known endpoint "apex=presence" in the data with the well-known endpoint "apex=presence" in the
corresponding administrative domain, e.g., corresponding administrative domain, e.g.,
"apex=presence@example.com" is the endpoint associated with the "apex=presence@example.com" is the endpoint associated with the
presence service in the "example.com" administrative domain. presence service in the "example.com" administrative domain.
Note that within a single administrative domain, the presence service Note that within a single administrative domain, the presence service
makes use of the APEX access [3] service in order to determine if an makes use of the APEX access [3] service in order to determine if an
originator is allowed to view or manage presence information. originator is allowed to view or manage presence information.
2. Management of Presence Information 2. Use and Management of Presence Information
Management of presence information falls into three categories: Management of presence information falls into three categories:
o applications may update the presence information associated with o applications may update the presence information associated with
an endpoint; an endpoint;
o applications may subscribe to receive presence information o applications may subscribe to receive presence information
associated with an endpoint; and, associated with an endpoint; and,
o applications may find out who is subscribed to receive presence o applications may find out who is subscribed to receive presence
skipping to change at page 8, line 40 skipping to change at page 8, line 40
Subsequently, for up to the specified "duration", the service sends Subsequently, for up to the specified "duration", the service sends
new publish operations whenever there are any changes to the new publish operations whenever there are any changes to the
endpoint's presence information. If the "duration" is zero-valued, a endpoint's presence information. If the "duration" is zero-valued, a
one time poll of the presence information is achieved; otherwise, at one time poll of the presence information is achieved; otherwise, at
the end of the "duration", a terminate operation is sent. the end of the "duration", a terminate operation is sent.
Note that Step 5 of Section 4.4 requires that the "lastUpdate" Note that Step 5 of Section 4.4 requires that the "lastUpdate"
attribute of a presence entry be supplied in order to update that attribute of a presence entry be supplied in order to update that
entry; accordingly, applications must successfully retrieve an entry; accordingly, applications must successfully retrieve an
publish entry prior to trying to update that entry. This is usually presence entry prior to trying to update that entry. This is usually
accomplished by subscribing with a zero-valued duration. accomplished by subscribing with a zero-valued duration.
(Regardless, administrators should ensure that applications
authorized to update a precense entry are also authorized to retrieve
that entry.)
Either the subscriber or the service may cancel a subscription by Either the subscriber or the service may cancel a subscription by
sending a terminate operation, e.g., sending a terminate operation, e.g.,
+-------+ +-------+ +-------+ +-------+
| | -- data -------> | | | | -- data -------> | |
| appl. | | relay | | appl. | | relay |
| | <--------- ok -- | | | | <--------- ok -- | |
+-------+ +-------+ +-------+ +-------+
C: <data content='#Content'> C: <data content='#Content'>
skipping to change at page 29, line 8 skipping to change at page 29, line 8
Consult [1]'s Section 11 for a discussion of security issues. Consult [1]'s Section 11 for a discussion of security issues.
In addition, timestamps issued by the the presence service may In addition, timestamps issued by the the presence service may
disclose location information. If this information is considered disclose location information. If this information is considered
sensistive, the special timezone value "-00:00" may be used. sensistive, the special timezone value "-00:00" may be used.
References References
[1] Rose, M., Klyne, G. and D. Crocker, "The Application Exchange [1] Rose, M., Klyne, G. and D. Crocker, "The Application Exchange
Core", draft-ietf-apex-core-05 (work in progress), August 2001. Core", draft-ietf-apex-core-06 (work in progress), January 2002.
[2] Rose, M., "The Blocks Extensible Exchange Protocol Core", RFC [2] Rose, M., "The Blocks Extensible Exchange Protocol Core", RFC
3080, March 2001. 3080, March 2001.
[3] Rose, M., Klyne, G. and D. Crocker, "The APEX Access Service", [3] Rose, M., Klyne, G. and D. Crocker, "The APEX Access Service",
draft-ietf-apex-access-07 (work in progress), August 2001. draft-ietf-apex-access-08 (work in progress), January 2002.
Authors' Addresses Authors' Addresses
Marshall T. Rose Marshall T. Rose
Invisible Worlds, Inc. Dover Beach Consulting, Inc.
131 Stony Circle POB 255268
Suite 500 Sacramento, CA 95865-5268
Santa Rosa, CA 95401
US US
Phone: +1 707 578 2350 Phone: +1 916 483 8878
EMail: mrose@invisible.net EMail: mrose@dbc.mtview.ca.us
URI: http://invisible.net/
Graham Klyne Graham Klyne
Baltimore Technologies MIMEsweeper Group
1310 Waterside 1310 Waterside
Arlington Business Park Arlington Business Park
Theale, Reading RG7 4SA Theale, Reading RG7 4SA
UK UK
Phone: +44 118 903 8000 Phone: +44 118 903 8000
EMail: gk@acm.org EMail: Graham.Klyne@MIMEsweeper.com
David H. Crocker David H. Crocker
Brandenburg Consulting Brandenburg Consulting
675 Spruce Drive 675 Spruce Drive
Sunnyvale, CA 94086 Sunnyvale, CA 94086
US US
Phone: +1 408 246 8253 Phone: +1 408 246 8253
EMail: dcrocker@brandenburg.com EMail: dcrocker@brandenburg.com
URI: http://www.brandenburg.com/ URI: http://www.brandenburg.com/
skipping to change at page 31, line 10 skipping to change at page 31, line 10
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors gratefully acknowledge the contributions of: Neil Cook, The authors gratefully acknowledge the contributions of: Neil Cook,
Eric Dixon, Darren New, Scott Pead, and Bob Wyman. Eric Dixon, Darren New, Scott Pead, and Bob Wyman.
Appendix B. Revision History Appendix B. Revision History
Note to RFC editor: please remove this entire appendix, and the Note to RFC editor: please remove this entire appendix, and the
corresponding entries in the table of contents, prior to publication. corresponding entries in the table of contents, prior to publication.
B.1 Changes from draft-ietf-apex-presence-04 B.1 Changes from draft-ietf-apex-presence-05
o Add parenthetical comment regarding correct setting of permissions
in order to update an entry.
B.2 Changes from draft-ietf-apex-presence-04
o Corrected three typos. o Corrected three typos.
o Removed the reference to "xml.resource.org" in the DTD. o Removed the reference to "xml.resource.org" in the DTD.
o Changed the syntax of the "baseline" attribute to URI, to allow o Changed the syntax of the "baseline" attribute to URI, to allow
for distributed registration of possible values. for distributed registration of possible values.
o Added timezone warning to the "Security Considerations" section. o Added timezone warning to the "Security Considerations" section.
B.2 Changes from draft-ietf-apex-presence-03 B.3 Changes from draft-ietf-apex-presence-03
o The new date-time format referenced in the core document is now o The new date-time format referenced in the core document is now
used for the timestamp data-type. used for the timestamp data-type.
o The relationship of the "reply" element to the core document was o The relationship of the "reply" element to the core document was
clarified. clarified.
B.3 Changes from draft-ietf-apex-presence-02 B.4 Changes from draft-ietf-apex-presence-02
o Re-organization previous version for consistency. o Re-organization previous version for consistency.
B.4 Changes from draft-ietf-apex-presence-01 B.5 Changes from draft-ietf-apex-presence-01
o Grammar error in Security Considerations. o Grammar error in Security Considerations.
o Extraneous sentence in Step 6.2 of Section 4.3. o Extraneous sentence in Step 6.2 of Section 4.3.
o Notifications are now sent when a subscription is terminated. o Notifications are now sent when a subscription is terminated.
B.5 Changes from draft-ietf-apex-presence-00 B.6 Changes from draft-ietf-apex-presence-00
o Change "subaddress" convention from RFC 2846 to APEX's custom o Change "subaddress" convention from RFC 2846 to APEX's custom
ABNF. ABNF.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 23 change blocks. 
36 lines changed or deleted 42 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/