Re: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION] Harmonizat ion Adhoc kickoff
Vladimir - Just to clarify, I did not propose an interim F2F. In
response to suggestions from some folks to consider an interim F2F, I
recommended that we discuss that possibility (one way or another) during
our telecons this week. It is abundantly clear that most folks are not
in favor of an interim F2F and I don't see one occuring without critical
mass.
Regards,
-Prakash
-----Original Message-----
From: owner-stds-802-16@listserv.ieee.org
[mailto:owner-stds-802-16@listserv.ieee.org] On Behalf Of Vladimir
Yanover
Sent: Monday, July 26, 2004 6:39 AM
To: STDS-802-16@listserv.ieee.org
Subject: Re: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION]
Harmonizat ion Adhoc kickoff
Prakash and all,
We in Alvarion also strongly oppose having interim-interim F2F meetings
as it includes sort of discrimination against participants
located far from US and/or having limited resources [time or financial].
Vladimir
-----Original Message-----
From: Itzik Kitroser
To: STDS-802-16@listserv.ieee.org
Sent: 7/22/2004 11:04 PM
Subject: Re: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION]
Harmonization Adhoc kickoff
Parkash,
I'll be happy if we don't rush into deciding on a F2F meeting prior to
the Seoul meeting.
I think that forcing people to yet another cross Atlantic (or cross
Pacific) journey is quite of a burden, both from time and financial
aspects.
The time frame until the next meeting is quite short, and some of us
have also inter-company commitments which might prevent us the overhead
of traveling.
I think that we should manage to do our work in an offline manner, and
unless people are willing to come to Israel, I'm strongly against
interim-interim meeting.
Regards,
Itzik.
-----Original Message-----
From: owner-stds-802-16@LISTSERV.IEEE.ORG
[mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Iyer, Prakash
Sent: Thursday, July 22, 2004 6:18 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION]
Harmonization Adhoc kickoff
Folks - this email is to essentially kick off the new harmonization
adhoc that was chartered at the Portland meeting last week.
As was presented by Brian at the closing plenary, the adhoc will not
focus on PHY issues (those will be discussed within the larger .16e
group). Specific topics that were agreed upon include:
- Support for MBS
- Handover support (cleanup and complete support for handover, building
on the D4 draft which will become available shortly)
- Idle mode and paging support
- Scanning and association related optimizations
- Fixes to SDLs and informative text in annexes to match up with text
changes elsewhere in the .16e spec
Also, Roger will create a new temporary upload directory - link at <
<http://harmony.wirelessman.org> http://harmony.wirelessman.org>. The
server will not be up and running for a couple of days.
I will send out logistics for bi-weekly telecons starting next week.
Propose Mondays at 6 A.M. and Wednesdays at 8 P.M. (both U.S. Pacific
time zone) - if anyone wants to suggest alternate times, please respond
ASAP.
First telecon will be on Monday, July 26th at 6 AM US PDT by default.
I also have the final USR file and will send out a list of contributions
that were rejected or deferred (related to topics above) for us to
consider as a starting point. Given that we have many topics, we will
likely pick a subset of topics for each telecon. We can decide on a
process during our first telecon.
Also, we can decide on a pre-Seoul adhoc F2F over the course of telecons
next week.
Use [HARMONIZATION] in the subject line for emails related to this
adhoc.
Rgds,
-Prakash
This mail passed through mail.alvarion.com
************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************
This mail was sent via mail.alvarion.com
************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************