Smb1 Authentication Architectures Steven M. Bellovin [email protected] smb.
5/30/2000 1 The liveaddressbook: Telephone Calls with Presence Allen Milewski & Tom Smith...
-
date post
18-Dec-2015 -
Category
Documents
-
view
221 -
download
0
Transcript of 5/30/2000 1 The liveaddressbook: Telephone Calls with Presence Allen Milewski & Tom Smith...
5/30/20001
The live•addressbook:Telephone Calls with Presence
Allen Milewski & Tom [email protected] / [email protected]
5/30/20002
• Location • Availability• Anything needed to negotiate the conversation
• Identification of Caller• Topic of Call• Eagerness to Talk /Excitedness • Mood• Friendliness• Urgency of Content• Estimated Length of Call• Apology (e.g. the hour)•.
Live addressbook:Personal Presence Is:
[linguistic context]
5/30/20003
•How Much Information ?(Informativeness vs Privacy)
•How to keep Information Up-to-date ? (Overhead vs Control)
•How to Convey the Information ?(Publish/Subscribe vs Situated Negotiation)
Live addressbook Personal Presence– Design Issues
5/30/20004
Helps control telephone calls/teleconferences:• from anywhere, with any telephone• via wireless PDA or desktop browser• from Personal Presence Listings:
– current reach number– availability– personal message
Telephone caller’s lack information about the people they want to call => unwanted interruptions and missed connections
What problem does it solve?
Live addressbook
What is the live addressbook?
5/30/20005
Click2Dial Server
Phone network
Presence Server
Called PartiesCalling Party
Live AB Server
Wireless PDA Desktop Browser
AT&T Pocketnet Service
“Instant Messaging / Buddy” technology
Web-based conferencing technology
Live addressbook
5/30/20006
Reducing the Overhead of Being Available Web Page
Preparing for talkHome
Updated: 1hr.23 min ago
5/30/20007
• Ubiquitous, Multiple-Device Access• Hint-Based Coaxing
Wireless PDA
Desktop Browser
Telephone
Liveupdate-PC
Reducing the Overhead of Being Available
Overhead Reduction Methods
5/30/20009
• Ubiquitous, Multiple-Device Access• Hint-Based Coaxing- user is “coaxed” to change Personal Presence Info when: logging on from the PC
at a location different than the “current” location connecting from the Mobile PDA and a different location is “current” starts typing on a PC (with liveupate-pc) and another location is “current”
Reducing the Overhead of Being Available
Overhead Reduction Methods
5/30/200010
Live addressbook:A small-scale trial
Three Workgroups:
• Group E -remotely located with much moving
-“high-tech” developers, designers collaborating on a single system
weekly, scheduled teleconferences
-heavy use of email and Instant Messaging
•Group P-co-located with frequent travel
-range of job functions and technology abilities.
-heavy use of telephone & email, not IM
Had Palm/Pocketnet PDA equipment
•Group M-remotely located, but less collaboration
- manager/employee relationship
5/30/200011
Design Insights•How Much Information ?(Informativeness vs Privacy)
Personal Location and Availability Information are both useful for telephone communication.
• Telephone “buddy lists” can peacefully co-exist with standard personal phonebooks
•How to keep Information Up-to-date ? (Overhead vs Control)
Users will attempt to keep Personal Presence Information current, especially if the overhead is low.
Support for communication and Presence updates through multiple access methods is useful.
Mixing auto-detection and manual updating is a useful (and low-risk) overhead reduction strategy.
Personal Availability Information is much more difficult to keep current than Location.
5/30/200012
Design Insights
• How to Convey the Information ? (Publish/Subscribe vs Situated Negotiation)
Publish/Subscribe works well for Location Information
Situated negotiation of Availability may be superior to the “publish/subscribe” model.