My comments on
the initial preliminary draft document are added in the attached file using track
changes. I will try to add more stuffs in Section 3. Suggested Amendments.
For suggested amendments
section, I think if we can provide .16g with suggested text change from the 16g
baseline document (80216g-04_03r3), then it would be easier for .16g people to
make decision, modifications and changes.
Somebody has
to submit specific text changes in order for 16g people to make changes in
their document.
Any opinion on
this?
BR,
- Ronny
From:
Gupta, Vivek G
[mailto:vivek.g.gupta@INTEL.COM]
Sent: Tuesday, August 09, 2005 8:11 PM
To: STDS-802-21@listserv.ieee.org
Subject: Re: [802.21] 802.21
Teleconference: L2 Requirements for 802.16 and 802.3
Please find attached an
initial preliminary draft document which tries to capture some of the
requirements and also has suggested amendments for the 802.16g specification.
Our goal should be to continually refine this document and capture all possible
requirements and also include suggested amendments for 802.16g spec.
Please take a look at the
current 802.16g specification as well.
We shall also try to
cover Junghoon’s contribution in the teleconference.
Best Regards
-Vivek
From:
Junghoon Jee [mailto:jhjee@etri.re.kr]
Sent: Monday, August 08, 2005 7:51 PM
To: Gupta,
Vivek G; STDS-802-21@LISTSERV.IEEE.ORG
Subject: RE: [802.21] 802.21
Teleconference: L2 Requirements for 802.16 and 802.3
Hi Vivek
and ALL,
Here is an attempt to correlate IEEE802.16e's MAC
management frames to the link layer events which are described in the .21
Draft
related with the previous contribution,
21-05-0317-00-0000.
There is an update by mapping IEEE 802.16e's MAC
management fame, MOB_HO-IND to Link Handoff Imminent event in .21 Draft.
Even though .21 WG's work should be focused on the MIH
service not specific link layer,
I think that this kind of consideration is required
with the following reasons.
MIH event service can efficiently support seamless
handover when MIH event can happen synchronously with link specific link layer
events.
Therefore, we need to identify the relationship
between the MIH event's occurring point and the specific timing points
where specific L2 frames are transferred.
If we have available time in this teleconference, then
I would like to discuss about this all of you through the 802.16 considerations
part.
Regards,
Junghoon
From:
Gupta, Vivek G
[mailto:vivek.g.gupta@INTEL.COM]
Sent: Monday, August 08, 2005 11:43 PM
To: STDS-802-21@LISTSERV.IEEE.ORG
Subject: [802.21] 802.21
Teleconference: L2 Requirements for 802.16 and 802.3
The next 802.21 telecon on L2
Requirements for .3/.16 will be held as per below.
Please plan on joining us then.
Agenda:
L2/L3 transport general
considerations: 30 mins
802.16
considerations:
60 mins
802.3 considerations:
30 min
Date: August 9,
2005, 10:00 AM
EST
Phone:
916-356-2663, Bridge: 3, Passcode: 1149557
Lines: 25
Best Regards
-Vivek
-----Original Message-----
From: owner-stds-802-21@ieee.org [mailto:owner-stds-802-21@ieee.org] On Behalf
Of Ajay Rajkumar
Sent: Friday, July 22, 2005 5:36
PM
To: STDS-802-21@listserv.ieee.org
Subject: Teleconference schedule for the next two months
Hi Everyone,
We just concluded the July Plenary. As announced
during the closing, four
Adhoc's were created. Following is their
teleconference schedule for the
next two months.
L2 Requirements for .11
August 16, 2005; 10-12 noon EST
September 6, 2005; 7-9 pm EST
L2 Requirements for .3/.16
August 9, 2005; 10-12 noon EST**
August 30, 2005; 7-9 pm EST
Higher layer Requirements for IETF
July 26 , 2005; 9-11 am EST
July 28 , 2005; 9-11 pm EST
August 16, 2005; 9-11am EST
September 8, 2005; 9-11am EST
Liaison package development for 3GPP and 3GPP2
August 11, 2005; 9-11 am EST
August 18, 2005; 9-11 pm EST
August 25, 2005; 9-11 am EST
September 1, 2005; 9-11 pm EST
The bridge numbers would be announced closer to the
actual dates of the
teleconference.
** Please note that during the August 9, 2005
teleconference from 10-12
noon, EST time would be devoted to a general
discussion on L2/L3 transport.
This may be of interest to all participants of other
.21 Adhoc's and steer
the course of discussion in other adhoc's as well.
Best Regards,
-ajay
Ajay Rajkumar
Chair, IEEE 802.21 WG