I'm not an expert on 802.15.7, although I did read the draft when it was balloting. It doesn't exactly "re-use" the802.15.4 MAC it seems fair to say it borrows substantially ;-). I'm not really sure what might be going on outside of 802.15 with respect to higher layer adaptations, implementations, conformance procedures, certification, etc. A quick look at
https://mentor.ieee.org/802.15/documents?is_group=0007
will give you some idea who contributed which is often a clue as to who cares the most ;-).

There has been quite a lot of activity in 802.15 over the last few years, with a lot of it focused on 802.15.4. There are now 3 published amendments which add a variety of new PHYs to choose from, and a lot of added MAC capabilities (I would think 802.15.4e-2012 would be of interest to many on this group). While no specification or advice is given in the standard regarding IP implementations, knowledge that many people are and will be running IP layers on top of 15.4 definitely has influenced the work of recent task groups.

I too am interested in how visible light can be used to form mesh topologies, but haven't done much more than wonder - can't wait to hear more informed opinions!

Hope that helps some.

B




On Jun 18, 2012, at 20:09, Benjamin A. Rolfe wrote:

http://standards.ieee.org/about/get/802/802.15.html
There are no ongoing projects to amend 802.15.7 at this time.
Thanks Ben.

So is there any other activity for getting IP going on top of Li-Fi?

A quick check seems to indicate:
-- as this re-uses 802.15.4's MAC, they'd need something like our dispatch 
scheme.
-- fragmentation is needed for PHY 1 (PHY frame size limited to 1023 B), not 
for the higher ones.
-- HC would probably help with the slower PHY 1, not so much with the faster 
ones.

Which of the PHYs is actually real?

Whether the 6LoWPAN network model (and thus 6LoWPAN-ND) fits is not clear to me 
-- much of Li-Fi's use will be unidirectional, as a fill-in for some other 
connectivity, and there will be a lot of star topology usage (see page 6).  
Mesh forwarding (route-over/-under) usage appears less obvious to me.

Of course, the most important question is whether there are people interested 
in doing the work.
If there is energy and a clear objective, we will find a way to make this 
happen (in whatever WG the IETF chooses to do this).

Grüße, Carsten



_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan

Reply via email to