Information Utility Breakout

1
Information Utility Breakout

• Randy Katz, Facilitator

2
Faculty Interest Crosscuts

• Preference Capture and Management
• Specify --gt Observe (Sensor Capture) --gt Adapt
• Declarative specifications
• Model building and checking
• Security monitoring
• Track activities
• System state, location, sensor inputs (cameras,
  smart dust)
• Store persistently, statistically aggregate,
  learn behaviors
• Privacy issues
• Common (loose) schema of information being
  collected
• Interchange format XML?
• Lowest common denominator ontology

3
Project Cross Cuts

• Project-wide service model needed
• Ninja strongly typed
• Functional/performance match?
• Common framework for negotiation among entities
  in the architecture
• Security, assurance, performance protocols
• Verify given policy that specification is correct
• Need for persistent storage
• Naming, consistency model, transactional model
• Discussions between ODS and Steam DBMS
• Explore space of policies
• Simulation vs. prototype implementation

4
Project Cross-Cuts

• Security/Privacy
• Explicit implicit data collection on an
  enormous scale
• Crypto/authentication solved problems
• Key management/UI for policy specification hard
  problems
• e.g., self-spy tool what can others find out
  about you?
• Opportunity for user-centered design
• Common trust model

5
Recommendations

• Too early to develop milestones
• Need more brainstorming time continue Friday
  afternoon faculty discussions over port, invite
  some grad students
• Develop global milestones by end of summer
• Milestones on top of Ninja, iStore, DLIB, Smart
  Dust, ...
• Role of System Architect/Integrator
• Hijack System Seminar in Fall
• 45 minute speculative talk
• 45 minute discussion
• CS 294 Class Post-PC and Beyond?
• Tutorials on existing building blocks (Ninja
  services, apps, etc.)
• Students get credit and make progress on research
• Retreat Model
• Mini-retreats group by group, once per year as a
  big group?