Net2WG/Notes/20090529

From TinyOS Wiki
Revision as of 22:55, 31 July 2012 by Gnawali (talk | contribs) (New page: ---------- = Meeting Notes for 5/29/2009 = ---------- = Agenda = ---------- * Message buffer and link layer interfaces = Participants = ---------- * Om, USC * Jorge, Berkeley * Steph...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Meeting Notes for 5/29/2009


Agenda


* Message buffer and link layer interfaces

Participants


* Om, USC
* Jorge, Berkeley
* Stephen, Berkeley
* Martin, Crossbow
* Mike, JHU
* Razvan, JHU


Discussion Notes


Message buffers

May 29th 2009

Participants: - Om, USC - StephStephenen, Berkeley - Jorge, Berkeley - Martin, Crossbow - Mike, JHU - Razvan, JHU

Agenda: - Message abstraction - Anything else

Discussion notes:

Om: One thing we need is the link layer source address.

[... about message from Miklos from May 29 with the 3 interface alternatives ...]

Om: Option 3 does seems to offer access to the source address.

Razvan: So does option 1.

Om: Let's see how things are in CTP for example. The packet is received by the LinkEstimator which needs to find the source address. It will be on call for that.

Om: It seems that the change for the existing protocols are minimal.

Mike: Something about options 3: the address size is picked at compile time. This is now what we discussed last time.

Om: True. Back to Deluge. Razvan, how does Deluge changes?

Razvan: Not much but for option 1 for example I'll need to know which one of the two calls send calls (send16 or send 64) I'll have to use.

Om: That should make a bigger difference for something like IP. Or do you want Deluge to work in a network in which you have both 16 and 64 bit addresses.

Razvan: This depends on what type of dynamics we want to allow.

Om: Stephen, let me ask you this: in blip do you support uncompressed addresses?

Stephen: No, at the moment.

Razvan: Is blip using simultaneously 16 and 64 bit addresses?

Stephen: Yes, it's important to have both. Each interface has two interfaces. Once is configure, each node is multihomed. When you turn on a node is using the unique 64 bit address and then switches to 16 bit later on.

Razvan: So you can use them interchangeably once their are set up.

Stephen: Yeah.

Om: So option 3 is not really an option. Right?

Stephen: True. Other people will want the ability to use both 16 and 64 bit addresses.

Om: This is similar with having multiple radios.

Razvan: It's not exactly the same. When you have two addresses in the same network you can talk to other nodes using either of them. When you have two radios you will probably have on one interface a different set of nodes than on the other.

Om: Let's look at option 1 and 2.

[...]

Om: about the release schedule: the code need to be tested by something other than you. The summer is a good time because there might be some students I can ask to do it.

[... discussion with Martin about support for blip out of tree, support for Iris and Imote2 and support for windows. The discussion is very well summarized in this [[1]].]