RE: 802.21 Teleconference: L2 Requirements for 802.11
Dear all,
I´m sending these comments on behlaf of a colleague, Jouni Korhonen.
The .11u requirement d15M2 could be useful if adopted in .21 (in some form) for IPv4 deployments? More specifically for the following case:
When a STA does a L2 handover, STA's L3 might learn
this through some cross layer event mechanism. However,
the STA has no knowledge if it MUST reconfigure
its L3 IP settings (e.g. in the case when the IPv4
subnetwork changes). It should be noted that the STA
does not have to do anything if there is no need to
reconfigure L3 IP settings -- attempting L3
reconfiguration (e.g. using DHCP) every time just to be
sure is not really an elegant solution. So to help the
STA in rapid decision making the original idea of .11u
requirement d15M2 would be essential.
FYI: current best practices and problems for IPv4 case are
more or less described in IETF DNA WG's
draft-ietf-dhc-dna-ipv4-15.
The above is also applicable to IPv6 but used mechanisms
and details of problems are slightly different -- at L3.
Best regards,
Lars
> -----Original Message-----
> From: stds-802-21@LISTSERV.IEEE.ORG
> [mailto:stds-802-21@LISTSERV.IEEE.ORG] On Behalf Of Soohong
> Daniel Park
> Sent: den 17 augusti 2005 09:50
> To: Gupta, Vivek G; STDS-802-21@LISTSERV.IEEE.ORG
> Subject: Re: 802.21 Teleconference: L2 Requirements for 802.11
>
> Vivek, thanks your good initiative and here is my suggested amendment.
>
> 802.11u decided its in-scope requirements during last meeting and one
> requirement was away from them.
>
> ==========================
> From 11-05-0279-15-000u
>
> - Reference: REQ d15M2
> - Requirement:
> 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.
> - Notes (informative):
> 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.Note: It is
> recognized that the suggested requirement class is extremely
> controversial,
> and it is expected that the motion to accept this requirement will be
> subject to a motion to amend.
> - Requirement Class: Out of scope-To be forwarded to .21 and 11r
> ==========================
>
> I am opening this requirement to be included into the 802.21 spec.
>
> All comment is highly welcome.
>
>
> Regards,
>
> Daniel (Soohong Daniel Park)
> Mobile Platform Lab., SAMSUNG Electronics.
>