What happened to the stds-802-16 subject header?
Itzik, all,
For some reason the 802.16 reflector traffic is no longer adding the
stds-802-16 header in the subject line. I agree with Itzik that this
makes it difficult to filter the traffic, and defeats the sorting rules
in mail handlers. If the server can be adjusted to add a suitable
subject header the 802.16 traffic won't be as subject to deletion by
spam filters, etc., in many of our in-boxes.
Cheers,
Eric Jacobsen
Minister of Algorithms
Intel Corporation
-----Original Message-----
From: owner-stds-802-16@listserv.ieee.org
[mailto:owner-stds-802-16@listserv.ieee.org] On Behalf Of Itzik Kitroser
Sent: Monday, March 22, 2004 12:15 PM
To: STDS-802-16@listserv.ieee.org
Subject:
Marianna,
Can you please make the discussion on the open reflector,
with a designated mail header, such that non-interesting
people can filter it out.
I believe that, as was done in other ad hocs, such open
process will reach more people, which does not know in the
moment if they are interested or not, but may be, according
to the progress of the work.
In addition, it will be easier to avoid maintaining big
address lists, which may be increased with addition of others.
Regards,
Itzik.
> -----Original Message-----
> From: owner-stds-802-16@listserv.ieee.org
> [mailto:owner-stds-802-16@listserv.ieee.org]On Behalf Of
Marianna
> Goldhammer
> Sent: Monday, March 22, 2004 18:37
> To: STDS-802-16@listserv.ieee.org
> Subject:
>
>
> Dear Colleagues,
>
> At the closing Plenary of IEEE 802.16 Session #30, we have
> decided to set up an Ad-Hoc correspondence group for
> study of co-existence in below 11GHz LE (License Exempt)
> bands and make a recommendation to the WG, at May 802.16
> meeting.
>
> I would propose, as charter for this group:
>
> 1. Identification of scenarios in which interference
between cells
> can cause disruption in service; will be taken into
account both
> "access providers" installations and private networks;
>
> 2. Identification of techniques which may mitigate the
problem,
> such as dynamic frequency selection, time co-ordination,
> creation of interference free periods, etc;
>
> 3. Identification of minimum set of interoperability
requirements that
> will reduce the service disruption problems.
>
> I would propose to adopt as parameters for this study, to
be agreed
> by the Ah-hoc group:
>
> - Operating frequency: 5.8GHz, under FCC UNII rules;
> - System architecture: P-MP;
> - BST antennae: omni, sectorial;
> - SS antennae: omni, directional;
> - Behaviour under interference: according to radio
parameters specified
> in 802.16-REVd.
>
> - Co-ordination assumptions:
> - none
> - frame duration and start time synch
> - Rx/Tx duty cycle alignment
> - air protocol
> -etc.
>
> In order to kick-off this activity, please let me know if
you wish
> to participate. I will create a special e-mail list.
>
> Regards,
>
> Marianna
>
> Chair - IEEE 802.16 Ad-hoc for LE Co-existence
>
>
>
> Marianna Goldhammer
> Director - Strategic Technologies
>
> Alvarion, Ltd.
> 10 years of wireless expertise
>
> 21 HaBarzel Street
> P.O.Box 13139, Tel Aviv 61131, Israel
> Tel: (972)- 3 -6456241/6262
> Fax: (972) -3 -6456204
>
> Email: marianna.goldhammer@alvarion.com
>
> www.alvarion.com
>
>
>
>
> Marianna Goldhammer
> Director - Strategic Technologies
>
> Alvarion, Ltd.
> 10 years of wireless expertise
>
> 21 HaBarzel Street
> P.O.Box 13139, Tel Aviv 61131, Israel
> Tel: (972)- 3 -6456241/6262
> Fax: (972) -3 -6456204
>
> Email: marianna.goldhammer@alvarion.com
>
> www.alvarion.com
>
>
> 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.
>
**************************************************************
****
> ******************
>
>
> 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.
>
**************************************************************
****
> ******************
>