IETF 65 charter discussion
During the 6lowpan interim meeting in January 2006, the working group discussed possible topics for a future rechartering of 6lowpan.
The following text, which is an edited version of the scope present in the current 6lowpan charter, is based on available information from that meeting and feedback on the mailing list.
Please feel free to add your topics.
--- start of scope ---
Scope of 6lowpan:
Produce "Optimization of the Adhoc Routing Protocol for 6lowpans" to apply an existing MANET Protocol to LoWPANs.
Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" to define how to apply the existing Neighbor Discovery protocol in a 6lowpan.
Produce "IPv6 over Low Power WPAN Security Analysis" to define the assumptions for a security model for 6lowpan. This includes analysis of threats, identify types of devices and define the levels of trust between these devices.
Produce "6lowpan Co-existence with other Networks" to define how to co-exist with other networks. This includes analysis of how to survive interference caused by IEEE 802.11 based networks, and investigate how to recognize and co-exist with other networks based on IEEE 802.15.4.
Produce "Service Discovery Protocol for 6LoWPAN" to define how to discover, control and maintain services provided by 6lowpan devices.
Produce "Scalability of 6LoWPAN" to define a routing protocol for the lare number of devices which is expected to be deployed in 6LoWPAN while considering the limited capabilities of the devices (low power, limited memory space, and small packet size).
Produce "Interoperability of 6LoWPAN" to define the gateway Architecture between 6LoWPAN and external IPv6 networks.
As such, the working group may also work on informational documents for mobility issues and naming service for mesh layer.
The working group will reuse existing specifications whenever reasonable and possible.
The working group will also serve as a venue for ongoing discussions on other topics related to the more complete list outlined above. Additional related milestones may be added in the future via a rechartering operation.
Note: As may be obvious from its official name above, this particular working group will not work on IPv4 over IEEE 802.15.4 specifications. Given the limitations of the target devices, dual-stack deployments are not practical. Because of its higher potential for header compression, its support for the huge number of devices expected and of cleanly built-in features such as address autoconfiguration, IPv6 is the exclusive focus of the working group.
--- end of scope ---