[net2-wg] 12/8 Teleconference, 9AM PST

[Kyle Jamieson]

Transcript:

- Introductions
- Phil Levis
- tos2 wg member: goal for tos-2 by 2/10; network protocols wanted:
dissemination, collection
- Kyle, MIT: congestion control
- Rodrigo, Berkeley: BVR point-to-point routing, SP
- Om, USC: routing protocols, unicast routing, multi-sink environments
- Jonathan: Deluge, SP
- Henri, EPFL: MAC layer port to TinyNode

- Scope
- Eventually, Point-to-point & Diffusion
- Starting with collection and dissemination

- Main question: make send/sendDone as starting point, or go with
  sendPool?

  - Jon
  - SP interface: unified interface to exchange MAC, network layers
  - send/sendDone doesn't provide enough information
  - MAC layer information exchange: reliability and urgency
  - Futures: tell link layer how many messages you want to send, when
  you send lots of msgs
  - Implemented on top of MintRoute, Trickle, Synopsis Diffusion
  - (audio breaking up a bit)

  - Phil
  - More complex to program against
  - have to set up futures etc.

  - how easy to know the number of futures an app needs?
  - didn't use futures

  - when are futures useful
  - forwarding packets
  - filtering packets
  - sending more than one packet

  - Henri
  - Can't we just fold futures into one bit (whether you have more)

  - reliability could be an integer value?

  - Moving to Intel teleconference number....

  - Allocation of message pools
  - SP maintains message pools itself?

- Talk about whether this is a good idea from people "not drinking
Berkeley Kool-Aid."
- General thumbs up.

- Who's interested in what...

- Want to nail down specific components & their interactions for each
of collection and dissemination.
- Forming subgroups for each of collection and dissemination.