stds-802-16-tg3: RE: stds-802-16-mac: Suggested Agenda Items for the TG3/TG4 MAC Discussions
I suggest an additional agenda item: How to get the new contributions
submitted to this meeting into the draft.
According to Subir's published rules, no new materials were to be included
in the first draft. But it appears that the rules are not followed and some
people managed to get new contributions into the first draft. Therefore, for
the sake of fairness, we should consider all the new contributions for the
From: Vladimir Yanover [mailto:firstname.lastname@example.org]
Sent: Saturday, May 12, 2001 9:54 AM
To: 802. 16 Reflector (E-mail); 802.16 MAC Reflector (E-mail); 802.16 TG3
reflector (E-mail); 802.16 TG4 reflector (E-mail)
Cc: Roger B. Marks (E-mail); Brian G. Kiernan (E-mail); Durga Satapathy
(E-mail); Subir (E-mail); Ken Peirce (E-mail)
Subject: stds-802-16-mac: Suggested Agenda Items for the TG3/TG4 MAC
Let me suggest several topics to be discussed by TG3/TG4 MAC Groups at the
1. Reconsider the Table of Contents of the TG3 MAC Document
It should become a part of the whole 802.16 standard document, the topics of
TG3 MAC Document
that are changes to certain sections of TG1 MAC have to get the
2. Develop a baseline text for the ARQ topic.
At the moment there are few proposals on the table. May be the authors will
find a way to integrate them.
The only alternative is to start the selection process.
Some of proposals are very close, for example, proposals of BreezeCOM and
3. Develop a baseline text for the Packing as we need it for TG3
It starts to be clear that the existing structure of MAPs/headers is too
restrictive to provide VoIP services
with low overhead.
4. Develop a baseline text for the PHY dependent MAC definitions (what we
call "MAC-PHY interface)
Subir submitted a good example of such text for SC PHY: framing, MAP
messages, mini-slots etc.
The existing TG1 MAC contains such definitions in the general form (that by
the way is not suitable for
OFDM PHY). We have to take a look at these definitions and to decide what is
the better way of organization
of TG3 / TG4 material. For example, we may decide that this part of the TG1
text is not generic enough and
to suggest removing their text from the general part of MAC so that every
group will write its own version.
5. I would suggest discussing additional subjects that might be included
into the TG3 MAC Document:
It seems that the definitions for QoS support in TG1 MAC (imported from
DOCSIS with virtually no changes)
are partially not sufficient and partially too restrictive for such
applications like Internet services provided through
the wireless network.
b) Simplification of Network entry procedure for TG3 SSs
Today the Network Entry process consists of several steps that include IP
On one hand, it is out of the scope of the MAC protocol. On the other hand,
it requres implementation of IP stack at
SS that might be restrictive for the low-end SSs.
Dr. Vladimir Yanover
21 A Habarzel St. Ramat - Hahayal Tel - Aviv 69710
P.O. Box 13139, Tel-Aviv 61131, Israel