Skip to Content.
Sympa Menu

wg-pic - [Fwd: eyeBeam/pals discussion notes from 3/15/05]

Subject: Presence and IntComm WG

List archive

[Fwd: eyeBeam/pals discussion notes from 3/15/05]


Chronological Thread 
  • From: Jamey Hicks <>
  • To: PIC working group <>
  • Subject: [Fwd: eyeBeam/pals discussion notes from 3/15/05]
  • Date: Thu, 17 Mar 2005 16:40:45 -0500


Here are Candace's notes on a concall Candace, Bruce Gray and I had this week regarding Eyebeam and Pals.

Jamey

--- Begin Message ---
  • From: Candace Holman <>
  • To: Jamey Hicks <>,
  • Cc: , Ben Teitelbaum <>
  • Subject: eyeBeam/pals discussion notes from 3/15/05
  • Date: Thu, 17 Mar 2005 13:35:20 -0500
Hi all,

I've attached the notes I took at the conference call regarding eyeBeam and pals interoperability. There are some great points listed, and very cutting-edge discussion on presence interoperability requirements. Jamey offered to address some of these at the PIC WG call today, which I cannot attend today.
I've listed the 8 issues as a summary of the attachment.

ISSUE 1: a further requirements doc is needed for client/server interoperability regarding multiple services per person. Neither eyebeam nor pals has fully implemented the new requirements. We should come up with the issues/questions as a first step toward interoperability.

ISSUE 2: need a further discussion on relating a person attribute to a human. How will the client and server take care of this?

ISSUE 3: Both presence client and presence server should be able to have some configurable options regarding the consolidation of conflicting PUBLISH messages. The choices are: merge, server keep unique copies and client determine which is relevant, update on new, update if higher priority, update if there is no sticky-rule regarding previous updates. How can we communicate the configuration options? How do we resolve an additional conflict between the user and server configurations? Who wins?

ISSUE 4: Need to pre-populate a resource-list in pals

ISSUE 5: Incorporate the new client presence-rules from Rosenberg's i-d. Are they the same as privacy rules?

ISSUE 6: Is someone available to install https on pals, and/or also modify the pa config file to add the config file change to make the routing be based on presence rather than registration state? This would support the message store and delivery on arrival.

ISSUE 7: Identity and authentication of identity.

ISSUE 8: MSRP (session oriented instant messaging)

Regards,

=====================================================================
Candace Holman
617-384-6665

Harvard University Information Systems
60 Oxford Street
Cambridge, MA 02138

Attachment: eyeBeamPAMinutes 031505.doc
Description: Binary data


--- End Message ---


  • [Fwd: eyeBeam/pals discussion notes from 3/15/05], Jamey Hicks, 03/17/2005

Archive powered by MHonArc 2.6.16.

Top of Page