RE: stds-802-16-tg4: Mesh questions and discussion
From: mika.kasslin@nokia.com
To: stds-802-16-tg4@ieee.org
Subject: RE: stds-802-16-tg4: Mesh questions and discussion
Date: Mon, 15 Oct 2001 13:43:04 +0300
Baruch, all,
Here my answers to your questions:
1) That's our intention.
Even though the mesh mode is and shall be optional one it should be enough
to
implement a mesh mode compliant device to be standard compliant. How to do
that? A simple solution would be to list all the messages a mesh compliant
device
has to "understand" and all the rest are optional ones. As the result we
would have
slightly different lists of messages that apply to PMP and mesh modes. Hope
this
is okay.
2) In the current document we have described all the required information
that is
needed by a SS to "enter" a network. Here network entry actually just means
that
a node is synchronized to the network and can transmit some very limited set
of
management frames to e.g. register to the network.
The 802.16ab-01/01r2 document defines both MSH-NCFG and MSH-NENT messages
as well as the details of their transmission timing. All that information
allows one
to implement a SS that may enter a network and start procedures related to
registration and authentication. At this stage, a SS is not capable of
perform any
real scheduled transmissions. For that we may have to have an additional
functionality
standardized.
One possibility is to standardize a downloading mechanism that could be used
to
download "networking algorithms" you ask for from a neighboring SS or from
the
BS. No real difference in these two options, the former is somewhat better
from radio
perspective while the latter doesn't mandate all the SSs to have the
"uploading"
functionality.
Any comments on this?
Best Regards,
Mika
-----Original Message-----
From: ext Baruch Buskila [mailto:baruchb@waveip.com]
Sent: 10 October, 2001 12:08
To: Kasslin Mika (NRC/Helsinki); 'stds-802-16-tg4@ieee.org'
Subject: RE: stds-802-16-tg4: Mesh questions and discussion
Hi Mika,
There are two issues that remain open regarding the MESH Mode.
1) If an equipment implement ONLY the MESH mode, is it
standard comply.
2) What is the mechanism in which a SS can enter a
network operating in the MESH mode without having the networking algorithms,
which are not includes in the document.
I believe that these two issues need to be addressed in the document.
Regards
Baruch
_____
Baruch Buskila
WaveIP
Tel : 972.4.9937333
Mobil: 972.53.324149
Email: baruchb@waveip.com < <mailto:baruchb@waveip.com>
mailto:baruchb@waveip.com>
_____
==-----Original Message-----
==From: owner-stds-802-16-tg4@majordomo.ieee.org
==[ mailto:owner-stds-802-16-tg4@majordomo.ieee.org
<mailto:owner-stds-802-16-tg4@majordomo.ieee.org> ]On Behalf Of
==mika.kasslin@nokia.com
==Sent: Tue 09 October 2001 16:19
==To: stds-802-16-tg4@ieee.org
==Subject: stds-802-16-tg4: Mesh questions and discussion
==
==
==
==Hi all,
==
==In the Denver meeting I promised to initiate a discussion
==about mesh mode
==to resolve any related open questions. This message is to start that
==discussion
==so please come up with any concerns or questions related to
==the mesh mode
==specified in the working document 802.16ab-01/01r2.
==Please send all those questions as well as replies to this
==reflector so that
==
==everybody can follow and participate the discussion. Let's
==have a lively and
==fruitful discussion even before the first deadline for the
==comments Friday
==next
==week.
==
==Best Regards,
== Mika
==
==++++++++++++++++++++++++++++++++++++++++++++
==Mika Kasslin
==Nokia Research Center, Finland
==Phone +358-718036294
==Mobile +358-50-4836294
==Fax +358-718036856
==++++++++++++++++++++++++++++++++++++++++++++
==
==
------_=_NextPart_001_01C15566.2B403B0B
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE></TITLE>
<META content="MSHTML 5.00.3105.105" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>Baruch, all,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>Here
my answers to your questions:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>1)
That's our intention. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>Even
though the mesh mode is and shall be optional one </SPAN></FONT><FONT
color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>it should be
enough to </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>implement a mesh mode compliant device to be standard
</SPAN></FONT><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>compliant. How to do </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>that?
A simple solution would be to list all the messages </SPAN></FONT><FONT
color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>a mesh compliant
device </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>has to
"understand" and all the rest are optional ones. </SPAN></FONT><FONT
color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>As the result we
would have</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>slightly different lists of messages that apply to PMP
and mesh modes. Hope this</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>is
okay.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>2) In
the current document we have described all the required information that
is</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>needed
by a SS to "enter" a network. Here network entry actually just means
that</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>a node
is synchronized to the network and can transmit some very limited set
of</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>management frames to e.g. register to the network.
</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>The
802.16ab-01/01r2 document defines both </SPAN></FONT><FONT color=#0000ff
face=Arial size=2><SPAN class=250004209-15102001>MSH-NCFG and MSH-NENT messages
</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>as
well as the details of their transmission </SPAN></FONT><FONT color=#0000ff
face=Arial size=2><SPAN class=250004209-15102001>timing. All that information
allows one </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>to
implement a SS that may enter a network</SPAN></FONT><FONT color=#0000ff
face=Arial size=2><SPAN class=250004209-15102001> and start procedures related
to </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>registration and authentication. At this stage, a
SS is not capable of perform any </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>real
scheduled transmissions. For that we may have to have an additional
functionality</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>standardized. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>One
possibility is to standardize a downloading mechanism that could be used to
</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>download "networking algorithms" you ask for from a
neighboring SS or from the </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>BS. No
real difference in these two options, the former is somewhat better from
radio</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>perspective while the latter doesn't mandate all the
SSs to have the "uploading" </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001>functionality. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>Any
comments on this?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=250004209-15102001>Best
Regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001> Mika</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=250004209-15102001></SPAN></FONT><FONT color=#0000ff face=Arial
size=2><SPAN class=250004209-15102001> </SPAN></FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px;
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> ext Baruch Buskila
[mailto:baruchb@waveip.com]<BR><B>Sent:</B> 10 October, 2001
12:08<BR><B>To:</B> Kasslin Mika (NRC/Helsinki);
'stds-802-16-tg4@ieee.org'<BR><B>Subject:</B> RE: stds-802-16-tg4: Mesh
questions and discussion<BR><BR></DIV></FONT>
<P><FONT size=2><FONT size=3>Hi Mika,<BR><BR>There are two issues that
remain open regarding the MESH
Mode.<BR><BR>
1) If an
equipment implement ONLY the MESH mode, is it standard
comply.<BR>
2)
What is
the mechanism in which a SS can enter a network operating in the MESH mode
without having the networking algorithms, which are not includes in the
document.<BR><BR>I believe that these two issues need to be addressed in the
document.<BR><BR>Regards<BR><BR>Baruch<BR>
<HR>
<BR>Baruch Buskila<BR>WaveIP<BR>Tel :
972.4.9937333<BR>Mobil: 972.53.324149<BR>Email: baruchb@waveip.com
<</FONT><A href="mailto:baruchb@waveip.com";><FONT
size=3>mailto:baruchb@waveip.com</FONT></A><FONT size=3>><BR></FONT><BR>
<HR>
<BR><BR>==-----Original Message-----<BR>==From:
owner-stds-802-16-tg4@majordomo.ieee.org<BR>==[<A
href="mailto:owner-stds-802-16-tg4@majordomo.ieee.org";>mailto:owner-stds-802-16-tg4@majordomo.ieee.org</A>]On
Behalf Of<BR>==mika.kasslin@nokia.com<BR>==Sent: Tue 09 October 2001
16:19<BR>==To: stds-802-16-tg4@ieee.org<BR>==Subject: stds-802-16-tg4: Mesh
questions and discussion<BR>==<BR>==<BR>==<BR>==Hi all,<BR>==<BR>==In the
Denver meeting I promised to initiate a discussion<BR>==about mesh
mode<BR>==to resolve any related open questions. This message is to start
that<BR>==discussion<BR>==so please come up with any concerns or questions
related to<BR>==the mesh mode<BR>==specified in the working document
802.16ab-01/01r2.<BR>==Please send all those questions as well as replies to
this<BR>==reflector so that<BR>==<BR>==everybody can follow and participate
the discussion. Let's<BR>==have a lively and<BR>==fruitful discussion even
before the first deadline for the<BR>==comments
Friday<BR>==next<BR>==week.<BR>==<BR>==Best
Regards,<BR>==
Mika<BR>==<BR>==++++++++++++++++++++++++++++++++++++++++++++<BR>==Mika
Kasslin<BR>==Nokia Research Center, Finland<BR>==Phone
+358-718036294<BR>==Mobile +358-50-4836294<BR>==Fax
+358-718036856<BR>==++++++++++++++++++++++++++++++++++++++++++++<BR>==<BR>==</FONT>
<P></P></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C15566.2B403B0B--