draft-ietf-apex-presence-03.txt   draft-ietf-apex-presence-04.txt 
Network Working Group M. Rose Network Working Group M. Rose
Internet-Draft Invisible Worlds, Inc. Internet-Draft Invisible Worlds, Inc.
Expires: October 30, 2001 G. Klyne Expires: January 7, 2002 G. Klyne
Baltimore Technologies Baltimore Technologies
D. Crocker D. Crocker
Brandenburg Consulting Brandenburg Consulting
July 9, 2001
The APEX Presence Service The APEX Presence Service
draft-ietf-apex-presence-03 draft-ietf-apex-presence-04
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 33 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 October 30, 2001. This Internet-Draft will expire on January 7, 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-02 . . . . . . . . . . . 31 B.1 Changes from draft-ietf-apex-presence-03 . . . . . . . . . . . 31
B.2 Changes from draft-ietf-apex-presence-01 . . . . . . . . . . . 31 B.2 Changes from draft-ietf-apex-presence-02 . . . . . . . . . . . 31
B.3 Changes from draft-ietf-apex-presence-00 . . . . . . . . . . . 31 B.3 Changes from draft-ietf-apex-presence-01 . . . . . . . . . . . 31
B.4 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 22 skipping to change at page 5, line 22
| | -- data -------> | | | | -- data -------> | |
| appl. | | relay | | appl. | | relay |
| | <--------- ok -- | | | | <--------- ok -- | |
+-------+ +-------+ +-------+ +-------+
C: <data content='#Content'> C: <data content='#Content'>
<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='14 May 2000 13:30:00 -0800'> timeStamp='2000-05-14T13:30:00-08:00'>
<presence publisher='fred@example.com' <presence publisher='fred@example.com'
lastUpdate='14 May 2000 13:02:00 -0800' 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='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>
skipping to change at page 8, line 18 skipping to change at page 8, line 18
| | <------- data -- | | | | <------- data -- | |
| relay | | pres. | | relay | | pres. |
| | -- ok ---------> | svc. | | | -- ok ---------> | svc. |
+-------+ +-------+ +-------+ +-------+
C: <data content='#Content'> C: <data content='#Content'>
<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='14 May 2000 13:30:00 -0800'> timeStamp='2000-05-14T13:30:00-08:00'>
<presence publisher='fred@example.com' <presence publisher='fred@example.com'
lastUpdate='14 May 2000 13:02:00 -0800' 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='14 May 2000 14:02:00 -0800' />
</presence> </presence>
</publish> </publish>
</data-content> </data-content>
</data> </data>
S: <ok /> S: <ok />
skipping to change at page 23, line 34 skipping to change at page 23, line 34
o if a subscription is being reported, the "duration" attribute o if a subscription is being reported, the "duration" attribute
specifies the requested duration of the subscription. specifies the requested duration of the subscription.
No reply is sent by the receiving endpoint. No reply is sent by the receiving endpoint.
4.7 The Reply Operation 4.7 The Reply Operation
While processing operations, the service may respond with a "reply" While processing operations, the service may respond with a "reply"
element. Consult Sections 10.2 and 6.1.2 of [1], respectively, for element. Consult Sections 10.2 and 6.1.2 of [1], respectively, for
the syntax and semantics of the reply operation. the definition and an exposition of the syntax of the reply element.
5. Registration: The Presence Service 5. Registration: The Presence Service
Well-Known Endpoint: apex=presence Well-Known Endpoint: apex=presence
Syntax of Messages Exchanged: c.f., Section 6 Syntax of Messages Exchanged: c.f., Section 6
Sequence of Messages Exchanged: c.f., Section 4 Sequence of Messages Exchanged: c.f., Section 4
Access Control Tokens: presence:subscribe, presence:watch, Access Control Tokens: presence:subscribe, presence:watch,
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 [1]'s Section 11 for a discussion of security issues. Consult [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-03 (work in progress), June 2001. Core", draft-ietf-apex-core-04 (work in progress), July 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-05 (work in progress), June 2001. draft-ietf-apex-access-06 (work in progress), July 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-02 B.1 Changes from draft-ietf-apex-presence-03
o The new date-time format referenced in the core document is now
used for the timestamp data-type.
o The relationship of the "reply" element to the core document was
clarified.
B.2 Changes from draft-ietf-apex-presence-02
o Re-organization previous version for consistency. o Re-organization previous version for consistency.
B.2 Changes from draft-ietf-apex-presence-01 B.3 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.3 Changes from draft-ietf-apex-presence-00 B.4 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. 15 change blocks. 
16 lines changed or deleted 27 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/