RE: [802.21] IEEE 802.11u requirement for IEEE 802.21
Vivek,
these are indeed part of the solution. Please see below.
Stefano
> -----Original Message-----
> From: ext Gupta, Vivek G [mailto:vivek.g.gupta@intel.com]
> Sent: Sunday, November 06, 2005 11:31
> To: Faccin Stefano (Nokia-NRC/Dallas); stephen.mccann@ROKE.CO.UK;
> STDS-802-21@listserv.ieee.org
> Subject: RE: [802.21] IEEE 802.11u requirement for IEEE 802.21
>
>
>
> Yes this is an important requirement that needs to be addressed. There
> are several comments already in place in current draft to this affect.
>
> 1] Currently Link Up indication includes info about IPAddressRenewal
> (not sure if this info can be provided in all/most cases so this needs
> to be made optional at best). It can also include info about
> new subnet
> address for newly selected PoA (though one may argue about
> availability
> of subnet address from link layer triggers).
[Stefano] yes, and TGu requirement was meant to address that for 802.11 specifically. The TGu requirement in this case refers to the ability to provide such indication by the 802.11 link layer. Perhaps the question becomes: does 802.11 link layer need to do anything to provide such info?
>
> 2] LinkGoingDown indication includes MacAddress of next
> prospective PoA
> as an optional parameter. If that information is available then using
> RARP one can find IP address of prospective PoA and determine if there
> will be a change in IP address.
>
> 3] Information service tries to provide subnet information
> for different
> PoAs as part of Media Independent Neighbor maps. This could help in
> figuring out PoA layout and determining a priori possible impact on
> change in IP address due to specific PoA selection.
>
> Not sure if these are adequate so other solutions welcome as well.
> Best Regards,
> -Vivek
>
> > -----Original Message-----
> > From: stds-802-21@ieee.org [mailto:stds-802-21@ieee.org] On
> Behalf Of
> > stefano.faccin@nokia.com
> > Sent: Thursday, November 03, 2005 3:52 PM
> > To: stephen.mccann@ROKE.CO.UK; STDS-802-21@listserv.ieee.org
> > Subject: RE: [802.21] IEEE 802.11u requirement for IEEE 802.21
> >
> > Stephen,
> > thanks for the e-mail. I think this is a very important requirement,
> since
> > the functionality is needed as it was indicated in the various
> > presentations that lead to have the requirement inserted in in TGu.
> This
> > is definitely a feature that caters for handoff, and I think that
> 802.21
> > can help with this.
> >
> > Stefano
> >
> > > -----Original Message-----
> > > From: ext McCann, Stephen [mailto:stephen.mccann@ROKE.CO.UK]
> > > Sent: Thursday, November 03, 2005 10:13
> > > To: STDS-802-21@listserv.ieee.org
> > > Subject: [802.21] IEEE 802.11u requirement for IEEE 802.21
> > >
> > >
> > > Dear all,
> > > During the September 2005 meeting, IEEE 802.11u decided that
> > > one of the IEEE 802.11u requirements should be forwarded to IEEE
> > > 802.21 and I, errr, sort of forgot to do this after the meeting.
> > >
> > > So here is the requirement, which I hope we can discuss at the
> > > joint IEEE 802.11u/IEEE 802.21 meeting.
> > >
> > > "Define functionality by which APs can provide information which
> > > will enable a STA to determine whether or not roaming to
> a candidate
> > > AP would require re-configuration (automatic or manual) of layer
> > > 3 networking"
> > >
> > > There you go. Some extra notes which are associated with this
> > > requirement are:
> > >
> > > "This could be achieved by the APs advertising either information
> > > about the L3 routers accessible through them (ARID) or by
> > > identifying the ESS to which the AP is connected. However other
> > > solutions are not precluded."
> > >
> > > Kind regards
> > >
> > > Stephen
> > >
>