draft-ietf-apex-presence-04.txt   draft-ietf-apex-presence-05.txt 
Network Working Group M. Rose Network Working Group M. Rose
Internet-Draft Invisible Worlds, Inc. Internet-Draft Invisible Worlds, Inc.
Expires: January 7, 2002 G. Klyne Expires: February 12, 2002 G. Klyne
Baltimore Technologies Baltimore Technologies
D. Crocker D. Crocker
Brandenburg Consulting Brandenburg Consulting
July 9, 2001 August 14, 2001
The APEX Presence Service The APEX Presence Service
draft-ietf-apex-presence-04 draft-ietf-apex-presence-05
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.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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://www.ietf.org/ietf/1id-abstracts.txt. http://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 January 7, 2002. This Internet-Draft will expire on February 12, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). 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.
skipping to change at page 2, line 28 skipping to change at page 2, line 28
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-03 . . . . . . . . . . . 31 B.1 Changes from draft-ietf-apex-presence-04 . . . . . . . . . . . 31
B.2 Changes from draft-ietf-apex-presence-02 . . . . . . . . . . . 31 B.2 Changes from draft-ietf-apex-presence-03 . . . . . . . . . . . 31
B.3 Changes from draft-ietf-apex-presence-01 . . . . . . . . . . . 31 B.3 Changes from draft-ietf-apex-presence-02 . . . . . . . . . . . 31
B.4 Changes from draft-ietf-apex-presence-00 . . . . . . . . . . . 31 B.4 Changes from draft-ietf-apex-presence-01 . . . . . . . . . . . 31
B.5 Changes from draft-ietf-apex-presence-00 . . . . . . . . . . . 31
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 32 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 32
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
skipping to change at page 5, line 28 skipping to change at page 5, line 28
<originator identity='fred@example.com' /> <originator identity='fred@example.com' />
<recipient identity='apex=presence@example.com' /> <recipient identity='apex=presence@example.com' />
<data-content Name='Content'> <data-content Name='Content'>
<publish publisher='fred@example.com' transID='1' <publish publisher='fred@example.com' transID='1'
timeStamp='2000-05-14T13:30:00-08:00'> timeStamp='2000-05-14T13:30:00-08:00'>
<presence publisher='fred@example.com' <presence publisher='fred@example.com'
lastUpdate='2000-05-14T13:02:00-08:00' lastUpdate='2000-05-14T13:02:00-08:00'
publisherInfo='http://www.example.com/fred/'> publisherInfo='http://www.example.com/fred/'>
<tuple <tuple
destination='apex:fred/appl=im@example.com' destination='apex:fred/appl=im@example.com'
availableUntil='14 May 2000 14:02:00 -0800' /> availableUntil='2000-05-14T14:02:00-08:00' />
<tuple destination='mailto:fred@flintstone.com' <tuple destination='mailto:fred@flintstone.com'
availableUntil='31 Dec 2525 23:59:59 -0800' /> availableUntil='2525-12-31T23:59:59-08:00' />
</presence> </presence>
</publish> </publish>
</data-content> </data-content>
</data> </data>
S: <ok /> S: <ok />
Note that this example uses the "subaddress" convention specified in Note that this example uses the "subaddress" convention specified in
Section 2.2 of [1] (e.g., "fred/appl=im") to denote multiplexing of Section 2.2 of [1] (e.g., "fred/appl=im") to denote multiplexing of
traffic for a particular endpoint. Of course, popular applications traffic for a particular endpoint. Of course, popular applications
may have their own URI method assigned to them (e.g., may have their own URI method assigned to them (e.g.,
skipping to change at page 8, line 24 skipping to change at page 8, line 24
<originator identity='apex=presence@example.com' /> <originator identity='apex=presence@example.com' />
<recipient identity='wilma@example.com' /> <recipient identity='wilma@example.com' />
<data-content Name='Content'> <data-content Name='Content'>
<publish publisher='fred@example.com' transID='100' <publish publisher='fred@example.com' transID='100'
timeStamp='2000-05-14T13:30:00-08:00'> timeStamp='2000-05-14T13:30:00-08:00'>
<presence publisher='fred@example.com' <presence publisher='fred@example.com'
lastUpdate='2000-05-14T13:02:00-08:00' lastUpdate='2000-05-14T13:02:00-08:00'
publisherInfo='http://www.example.com/fred/'> publisherInfo='http://www.example.com/fred/'>
<tuple <tuple
destination='apex:fred/appl=im@example.com' destination='apex:fred/appl=im@example.com'
availableUntil='14 May 2000 14:02:00 -0800' /> availableUntil='2000-05-14T14:02:00-08:00' />
</presence> </presence>
</publish> </publish>
</data-content> </data-content>
</data> </data>
S: <ok /> S: <ok />
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
skipping to change at page 25, line 13 skipping to change at page 25, line 13
memo memo
6. The Presence Service DTD 6. The Presence Service DTD
<!-- <!--
DTD for the APEX presence service, as of 2001-05-08 DTD for the APEX presence service, as of 2001-05-08
Refer to this DTD as: Refer to this DTD as:
<!ENTITY % APEXPRESENCE PUBLIC "-//IETF//DTD APEX PRESENCE//EN" <!ENTITY % APEXPRESENCE PUBLIC "-//IETF//DTD APEX PRESENCE//EN"
"http://xml.resource.org/profiles/APEX/apex-presence.dtd"> "">
%APEXPRESENCE; %APEXPRESENCE;
--> -->
<!ENTITY % APEXCORE PUBLIC "-//IETF//DTD APEX CORE//EN" <!ENTITY % APEXCORE PUBLIC "-//IETF//DTD APEX CORE//EN" "">
"http://xml.resource.org/profiles/APEX/apex-core.dtd">
%APEXCORE; %APEXCORE;
<!-- <!--
Synopsis of the APEX presence service Synopsis of the APEX presence service
service WKE: apex=presence service WKE: apex=presence
message exchanges: message exchanges:
consumer initiates service replies consumer initiates service replies
skipping to change at page 27, line 22 skipping to change at page 27, line 22
publisherInfo publisherInfo
%URI; ""> %URI; "">
<!ELEMENT tuple (capability*)> <!ELEMENT tuple (capability*)>
<!ATTLIST tuple <!ATTLIST tuple
destination %URI; #REQUIRED destination %URI; #REQUIRED
availableUntil availableUntil
%TIMESTAMP; #REQUIRED %TIMESTAMP; #REQUIRED
tupleInfo %URI; ""> tupleInfo %URI; "">
<!-- e.g., baseline='rfc2533' --> <!-- e.g., baseline='urn:ietf:rfc:rfc2533' -->
<!ELEMENT capability (#PCDATA)> <!ELEMENT capability (#PCDATA)>
<!ATTLIST capability <!ATTLIST capability
baseline NMTOKEN #REQUIRED> baseline %URI #REQUIRED>
7. Security Considerations 7. Security Considerations
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
disclose location information. If this information is considered
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-04 (work in progress), July 2001. Core", draft-ietf-apex-core-05 (work in progress), August 2001.
[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-06 (work in progress), July 2001. draft-ietf-apex-access-07 (work in progress), August 2001.
Authors' Addresses Authors' Addresses
Marshall T. Rose Marshall T. Rose
Invisible Worlds, Inc. Invisible Worlds, Inc.
131 Stony Circle 131 Stony Circle
Suite 500 Suite 500
Santa Rosa, CA 95401 Santa Rosa, CA 95401
US US
skipping to change at page 31, line 7 skipping to change at page 31, line 7
EMail: dcrocker@brandenburg.com EMail: dcrocker@brandenburg.com
URI: http://www.brandenburg.com/ URI: http://www.brandenburg.com/
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
B.1 Changes from draft-ietf-apex-presence-03 Note to RFC editor: please remove this entire appendix, and the
corresponding entries in the table of contents, prior to publication.
B.1 Changes from draft-ietf-apex-presence-04
o Corrected three typos.
o Removed the reference to "xml.resource.org" in the DTD.
o Changed the syntax of the "baseline" attribute to URI, to allow
for distributed registration of possible values.
o Added timezone warning to the "Security Considerations" section.
B.2 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.2 Changes from draft-ietf-apex-presence-02 B.3 Changes from draft-ietf-apex-presence-02
o Re-organization previous version for consistency. o Re-organization previous version for consistency.
B.3 Changes from draft-ietf-apex-presence-01 B.4 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.4 Changes from draft-ietf-apex-presence-00 B.5 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 (2001). 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
 End of changes. 19 change blocks. 
22 lines changed or deleted 40 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/