Presence Use Cases

1
Presence Use Cases

• draft-houri-speermint-usecase-presence-00
• Avshalom Houri IBM
• Edwin Aoki AOL LLC
• Sriram Parameswar - Microsoft

2
Presence

• Presence is a key enabler for many services
  including voice
• Peering domains will need presence in order to
  have a better enablement
• Deployments of domain to domain presence and IM
  systems already exist

3
Real Time Collaboration

• Media streaming is not the only service that will
  be done in domain peering
• Real time collaboration services as instant
  messaging, N-way chat, file transfer,
  collaborative editing and more are as important
  and media streaming
• Most of these services need presence as a basis

4
Presence Use Cases

• Presence subscription A user subscribes to
  another user on another domain
• Resource list subscription A user subscribes to
  a list of users on another domain while using a
  single URL as the resource list identifier

5
Real Time Collaboration Use Cases

• Page mode messaging
• Session mode messaging
• File transfer Transferring a file from a user
  at one domain to a user in another domain
• N-way chat A text based chat that is conducted
  between users from multiple domains
• Application sharing Enable seeing and working
  on the same application together
• Many more to come

6
Generic Requirements

• Connectivity learn connectivity settings
  including NAT/FW
• Security Making sure that the connection is
  authenticated, encrypted etc.
• Services Discovery of services available on the
  other side
• Overload control - Making sure that the other
  domains are not overloading each other
• Federation of domains (AKA clearing house) as
  defined in SPEERMINT terminology draft should be
  enabled for presence and real time collaboration
  services

7
Specific Requirements

• Mapping of presence documents Domains may have
  different statuses for user (e.g. busy, in a
  meeting), in some cases there is a need for a
  mapping function of these statuses and other
  presence information between the domains
• Mapping of users A domain may support users in
  multiple domain names, when a domain connects to
  many domains there is a need to know how to map
  user URIs to specific domains
• Consolidates subscriptions (future) Enable
  consolidated subscription between domains while
  retaining privacy of users

8
Conclusions

• Presence and real time collaboration services
  should be recognized as a first class citizen in
  the SPEERMINT peering model
• Many requirements may be covered by the VOIP
  oriented requirements but awareness to the
  additional needs of presence and real time
  collaboration is essential