Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4FDF6EDA.9040106@blindcreek.com>
Date: Mon, 18 Jun 2012 20:30:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDF35520-218C-437F-B76A-405051DDA0F2@tzi.org>
References: <CAP+sJUdhZPXx9SxcrzSTovG85FuGh2WB=V1faUzyhyFs+Dw8Kg@mail.gmail.com>
 <6E4B70E6-C3BD-41A9-ADD4-A77A1F8C07DD@tzi.org>
 <4FDF6EDA.9040106@blindcreek.com>
To: "Benjamin A. Rolfe" <ben@blindcreek.com>
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] Does the 6lowpan WG want to close?
Precedence: list

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=FC=DFe, Carsten