draft-ietf-apex-presence-00.txt   draft-ietf-apex-presence-01.txt 
Network Working Group M. Rose Network Working Group M. Rose
Internet-Draft Invisible Worlds, Inc. Internet-Draft Invisible Worlds, Inc.
Expires: August 2, 2001 G. Klyne Expires: November 5, 2001 G. Klyne
Baltimore Technologies Baltimore Technologies
D. Crocker D. Crocker
Brandenburg Consulting Brandenburg Consulting
February 2001 May 7, 2001
The APEX Presence Service The APEX Presence Service
draft-ietf-apex-presence-00 draft-ietf-apex-presence-01
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 August 2, 2001. This Internet-Draft will expire on November 5, 2001.
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 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . . . . . . . 31 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
B. Changes from IMXP . . . . . . . . . . . . . . . . . . . . . . 32 B. Changes from draft-ietf-apex-presence-00 . . . . . . . . . . . 31
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 33 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
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 5, line 36 skipping to change at page 5, line 36
destination='apex:fred/appl=im@example.com' destination='apex:fred/appl=im@example.com'
availableUntil='14 May 2000 14:02:00 -0800' /> availableUntil='14 May 2000 14:02:00 -0800' />
<tuple destination='mailto:fred@flintstone.com' <tuple destination='mailto:fred@flintstone.com'
availableUntil='31 Dec 2525 23:59:59 -0800' /> availableUntil='31 Dec 2525 23:59:59 -0800' />
</presence> </presence>
</publish> </publish>
</data-content> </data-content>
</data> </data>
S: <ok /> S: <ok />
Note that this example uses the subaddress-specification convention Note that this example uses the "subaddress" convention specified in
of RFC 2846 [4] (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.,
"im:fred@example.com"). "im:fred@example.com").
The service immediately responds with a reply operation containing The service immediately responds with a reply operation containing
the same transaction-identifier, e.g., the same transaction-identifier, e.g.,
+-------+ +-------+ +-------+ +-------+
| | <------- data -- | | | | <------- data -- | |
| relay | | pres. | | relay | | pres. |
skipping to change at page 29, line 8 skipping to change at page 29, line 8
<!ATTLIST capability <!ATTLIST capability
baseline NMTOKEN #REQUIRED> baseline NMTOKEN #REQUIRED>
7. Security Considerations 7. Security Considerations
Consult Section [1]'s Section 11 for a discussion of security issues. Consult Section [1]'s Section 11 for a discussion of security issues.
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-00 (work in progress), February Core", draft-ietf-apex-core-01 (work in progress), May 2001.
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-00 (work in progress), December 2000. draft-ietf-apex-access-01 (work in progress), May 2001.
[4] Allocchio, C., "GSTN Address Element Extensions in E-mail
Services", RFC 2846, June 2000.
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
Phone: +1 707 578 2350 Phone: +1 707 578 2350
EMail: mrose@invisible.net EMail: mrose@invisible.net
URI: http://invisible.net/ URI: http://invisible.net/
Graham Klyne Graham Klyne
Baltimore Technologies Baltimore Technologies
1220 Parkview 1310 Waterside
Arlington Business Park Arlington Business Park
Theale, Reading RG7 4SA Theale, Reading RG7 4SA
UK UK
Phone: +44 118 930 1300 Phone: +44 118 903 8000
EMail: gk@acm.org EMail: gk@acm.org
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 32, line 5 skipping to change at page 31, line 5
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/
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, and Scott Pead. Eric Dixon, Darren New, and Scott Pead.
Appendix B. Changes from IMXP Appendix B. Changes from draft-ietf-apex-presence-00
o s/IMXP/APEX/g
o Clarify the notion of co-residence for APEX services.
o Change data's originator from an attribute to an element.
o CPIM mapping moved to another document. o Change "subaddress" convention from RFC 2846 to APEX's custom
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
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
 End of changes. 13 change blocks. 
25 lines changed or deleted 17 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/