[net2-wg] Packet interface

[Kyle Jamieson]

> configure entry for destination A
> send 4 packets to A
> configure entry for destination B
> send 2 packets to B
> 
> there's a tradeoff here between the amount of communication  
> parallelism and the state you allocate (pool entries).

While most sensornet communication is indeed to a single sink, seems
like we're restricting apps' flexibility quite a bit with a one
destination per pool entry policy.  What was the rationale behind not
using per-packet destinations?

Kyle