RE: [802-11TGU] IEEE 802.21 .11 requirements teleconference
Hello Richard,
We shall have another 802.11 requirements related telecon next week as
well. Shall send out the details in few days.
As for Neighbor reports both 802.11 and 802.16 currently define Neighbor
Reports and Neighbor maps. These reports give added information about
link layer parameters that help in appropriate selection of different
points of attachment (AP/BS).
802.21 is trying to provide Media Independent Neighbor Reports which not
only provide general information about access networks and
characteristics of different PoAs but also other information that may
help from handover perspective (e.g. network operator info, cost related
info, services available through access network/PoA etc.). The general
format of these Media Independent reports would be common across
different networks and 802.21 would not try to replicate/duplicate
information already provided directly by different access networks.
Also these Media independent Neighbor Reports can be retrieved from
802.21 information server using any radio. Thus if you are connected
only using WiMax radio, it may be possible to get information about a
close by WiFi hotspot without powering on your WiFi radio. From that
perspective it helps to have these Media Independent Neighbor Reports on
802.21 server. The reports could be retrieved either at L2 or at L3, but
many of us feel L3 may be more appropriate for such retrieval.
We are looking very closely at both .11k Neighbor Reports and also at
802.16 Neighbor Graphs/advertisements to capture the best from work
that's already been done. In the process if we do come across any IEs or
other amendments that apply more directly to different access networks
we would like to work with you to and make appropriate suggestions.
Best Regards,
-Vivek
> -----Original Message-----
> From: owner-stds-802-11-tgu@ieee.org [mailto:owner-stds-802-11-
> tgu@ieee.org] On Behalf Of Paine, Richard H
> Sent: Thursday, November 03, 2005 9:13 AM
> To: McCann, Stephen; STDS-802-11-TGU@listserv.ieee.org
> Subject: RE: [802-11TGU] IEEE 802.21 .11 requirements teleconference
>
> --- This message came from the IEEE 802.11 Task Group U Technical
> Reflector ---
>
> My apologies for missing the meeting altogether. I was setting up a
> demo and got delayed due to power outages in the Pacific Northwest
last
> night. There will be a relationship between 802.21 and 802.11k. Most
> specifically, the Neighbor Report in 11k enables a STA (in either an
AP
> or a client) to understand its 802.11 neighbors and potential roaming
> partners and perhaps the Neighbor Report should be a model for the
other
> networks .21 needs to address. Draft 3.0 of the 11k specification is
> the latest draft and contains the information to review for the 11k
> requirements.
>
> Richard H. Paine
> Success is getting what you want, happiness is liking what you get!
> Cell: 206-854-8199
> IPPhone: 425-373-8964
> Email: richard.h.paine@boeing.com
>
>
> -----Original Message-----
> From: McCann, Stephen [mailto:stephen.mccann@ROKE.CO.UK]
> Sent: Thursday, November 03, 2005 8:27 AM
> To: STDS-802-11-TGU@listserv.ieee.org
> Subject: [802-11TGU] IEEE 802.21 .11 requirements teleconference
>
> --- This message came from the IEEE 802.11 Task Group U Technical
> Reflector ---
>
> Dear all,
> Initially apologies that I escaped from this meeting after the
> first hour, as I had to be somewhere else.
>
> I think at the moment there are two documents related to the .11u/.21
> relationship:
>
> * 21-05-350-04 : as discussed into today's teleconference
> * The liaison letter from .11 to .21 containing the .11u requirements
> document 11-05-822r3 [Is there a .21 number for this, by the way?]
>
> I think it's worth stating at this point, that the liaison letter
> provides you, in .21, with the opportunity to comment on all the .11u
> requirements and to send .11u, comments and feedback.
>
> Within .11u it is understood that they will wait until they have
> received comments from the liaisons, prior to starting any formal
steps
> (such as letter ballots etc).
>
> Hence, I would prefer not to use the joint IEEE 802.11u/IEEE 802.21
> session in Vancouver to discuss all of the .11u requirements. I think
we
> should concentrate on the main ones which will allow .21 support
within
> .11 technology. We need to be focussed and not be sidetracked by
issues
> such as effects on battery life.
>
> Kind regards
>
> Stephen
>
>
________________________________________________________________________
> _______
>
> IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your
> request to this CLOSED reflector. We use this valuable tool to
> communicate on the issues at hand.
>
> SELF SERVICE OPTION:
> Point your Browser to -
> http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGU and then
> amend your subscription on the form provided. If you require removal
> from the reflector press the LEAVE button.
>
> Further information can be found at:
> http://www.ieee802.org/11/Email_Subscribe.html
>
________________________________________________________________________
> _______
>
>
________________________________________________________________________
__
> _____
>
> IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your
> request to this CLOSED reflector. We use this valuable tool to
communicate
> on the issues at hand.
>
> SELF SERVICE OPTION:
> Point your Browser to -
http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-
> 802-11-TGU and then amend your subscription on the form provided. If
you
> require removal from the reflector press the LEAVE button.
>
> Further information can be found at:
> http://www.ieee802.org/11/Email_Subscribe.html
>
________________________________________________________________________
__
> _____