[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: stds-802-16: Published: Development Plan for 802.16.3 Air Int erface Standard
I propose to do it at the next session, by inviting contributions regarding
suitability of the dot1 MAC for dot3 systems.
In this way you will receive a complete image of this complex problem.
It will be useful for you to look at:
which is the dot3 FRD, as before meeting 8 (last published).
From: Phil Guillemette [mailto:PGuillemette@spacebridge.com]
Sent: Monday, July 31, 2000 6:08 PM
To: 'Marianna Goldhammer'; Roger B. Marks; email@example.com
Subject: RE: stds-802-16: Published: Development Plan for 802.16.3 Air Int
It is interesting to hear that there are weaknesses in the current 802.16.1
MAC that will not allow it to address an 802.16.3 system. In order to
prevent these shortcomings from hurting the MACs operation in an 802.16.1
system, could you please provide further detail as to what they are? I
think that it would be safe to say that your help to find any potential
problems with the MAC would be greatly appreciated by the entire 802.16.1
MAC Task Group.
Acting Vice Chair, IEEE 802.16.1 MAC Task Group
From: Marianna Goldhammer [mailto:firstname.lastname@example.org]
Sent: Monday, July 31, 2000 10:08 AM
To: Roger B. Marks; email@example.com
Subject: RE: stds-802-16: Published: Development Plan for 802.16.3 Air
Int erface Standard
I have read the 802.16.1 MAC document and I have serious doubts that it is
to dot3 FRD. On the other side, this MAC successfully fulfils its
Trying to modify it in order to support dot3 requirements will actually stop
project. According to my opinion, the two groups are focused on different
with different bandwidth availability, that require different MACs. It will
one year to dot3 group to agree on MAC mechanisms, and you can expect some
them as being antagonist to the dot1 MAC mechanisms and philosophy.
Please consider to focus 802.16.1 MAC drafting process to the "above 10GHz"
only. It was a difficult process to reach this stage of the unified MAC
will be very risky to invite the negative votes of many of the dot3 members.
I have no doubts that the dot3 group will try to adopt the 802.16.1 positive
part of its work.
From: Roger B. Marks [mailto:firstname.lastname@example.org]
Sent: Friday, July 28, 2000 11:45 PM
Subject: stds-802-16: Published: Development Plan for 802.16.3 Air Interface
Title: Development Plan for 802.16.3 Air Interface Standard -
Task Group Revision
Document Number: IEEE 802.16.3-00/03r2
I feel the need to comment on this one, because I think this plan is
too slow. With people breathing down our necks in this area, I don't
think we have the luxury of waiting until next March to hear our
first proposals. If this standard is going to make an impact, we need
to get going. I think that TG3 should be looking at PHY proposals
this November, or January at the latest.
On the MAC side, remember that everyone in 802.16 is going to be
balloting on 802.16.1. There is every opportunity to make sure that
this MAC fits all of our needs. Once it does, TG3 can focus on
driving to a PHY draft.