Communications Hub F2F Minutes 2007-08-08

From MemberWiki

Jump to: navigation, search

Contents

Conference Call on August 8th 2007

  • Wednesday August 8th 2007 6pm ET/3pm PT

Agenda:

  • Quick overview of Face to Face meeting in San Francisco;
    • comms hub scope
    • api to provide
    • security implications
  • Proposal and discussion around CommunicationHub Task Force organization structure going forward

Attendees:

  • Coach Wei
  • Krishna Shankar
  • Ric Smith
  • Howard Weingram
  • ?

Minutes:

OAH 1.1: significant overlap between OAH and Comms

Comms mission:

  • Extend to inter-sandbox communication (between frames)
  • Might cover client-server, might then cover client-client

Hub has API and refrerence implementation

  • connection: conn, disc, status
  • messaging: pub, sub, batching messages
  • hub verson/etc.
  • access control: pub/sub name access rights for sandboxes

2 parts of Comm Hub

  • APIs
  • Providers (different impls)

Comments

  • Rick: Firefox 3 - multiplexing will be less of an issue on Firefox.
  •  ??: Support for client side vs server side
  • Krishna Shankar: PEP, PXP, etc.
  • KS: do we expect to specify policy definition language?
  • Howard:
    • intent now is that at least at first we specify APIs for checking access rights, not implementations for checking them or languages for specifying them.
    • APIs should be independent even of whether the information is stored at client or server side.
    • In this specification, simplicity is key. If too complex, then it will be improperly used or implemented & result will be less security.
    • Hope we can use topic namespaces, grant pub and sub access to specified [wildcarded] topic name spaces in order to keep permissions app-level and simple.
    • Also simplicity = low barrier to entry for developers.
  • Coach: initial permission = "nothing is permitted", all must be granted[correction: this should be "nothing is granted by default"].
  • KS:
    • Simplicity is good. Simple interface, programming model.
    • Trust framework, etc.
    • Do need to make sure enough security primitives so as not to oversimplify
    • Can also put scaffolding in to hide the complexity.

Interoperability / Comms Merger

Strong overlap between missions The stuff we're talking about in Comm Hub will become agenda for Interoperability

HW: concurs Rick: concurs KS: concurs. make sure to close out all items and move it over. Coach: will make formal proposal. Merge CHTF into Interoperability.

This TF is lightweight org designed to investigate this topic.

Mission complete.

Thank you for your contributions, everyone.

Retrieved from "/member/wiki/Communications_Hub_F2F_Minutes_2007-08-08"