Hi list,
Looking to the rechartering list I found out that this one does not
contempt the later suggestion made by Ron Strich regarding a high level
architecture document describing the overall 6LoWPAN architecture, as
those that appear in v6ops WG.
I also agree with Phil regarding the main problems to be addressed, but
I feel that Service Discovery can also represent an important role, in PANs.
Tiago Camilo
Philip Levis wrote:
On Feb 6, 2007, at 7:14 AM, Geoff Mulligan wrote:
Folks,
We have reached a milestone. We have submitted the Problem Statement
document and the Format Document to our AD for publication. We have
completed the original charter of the WG.
Mark will review the documents and then submit them for IETF LC (2
weeks) and then IESG review and discussion, which will hopefully happen
on the IESG telechat on March 8th.
So now it is very important that we finalize our thoughts about
rechartering the Working Group for new work, should we want to take on
new work.
Some of the items that people have indicated interest in working on:
Neighbor Discovery and Secure Neighbor Discovery (proposed standard)
Stateful header compression (informational)
6lowpan applications (informational)
mesh routing (proposed standard)
Security analysis (informational)
Moving forward, I think that mesh routing is the most important
problem. But neighbor discovery and bootstrapping are prerequisites
for mesh routing, so I think that we need to tackle them first.
Phil
_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan
_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan
