Re: [STDS-802-11-ARC] GLK ESS?

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

All,

Mark thank you for pulling this information together.

One editorial comment regarding your text from clause 4.3.5.1 – REVmd D5.0 has the reference pointing to 4.3.28, not 4.3.27 as show below.

I agree that there is no such thing as a GLK DSS and that GLK does not use the DS concept for mobility. As you know, GLK operation provides a means of establishing an 801.11 link from one IEEE 802.1Q bridge port to another IEEE 802.1Q bridge port by mapping the 802.11 MAC SAPs via GLK convergence functions (shim layers) to the ISS SAPs of the bridge (I’ve used plurals here because there two of each entity, one on each end of the link), defining a point to point link. Mobility for devices operating with GLK links is not within the scope of the 802.11 specification, as mobility of GLK links are managed (if supported at all) by the ability of the associated IEEE 802.1Q bridged network and the associated GLK convergence function (shim layer) to support port mobility (mobility being the process of allowing a link to be moved (re-mapped) from one IEEE 802.1 bridge port to another bridge port with in the same bridge or bridged LAN and changing the bridge routing to support the continuous delivery of packets to the new (re-mapped) location “transparently”).

This said – here are some initial thoughts (additional discussion and review are required before any action should be taken):

I agree we do not need to worry about GLK in our changes related to ESSs or HESS definitions/descriptions as these are not GLK concepts.
I think we should add additional text to clarify that while the concept of BSS does apply to GLK, ESS and DS do not apply. I don’t think the statement in 4.3.5.1 is adequate.
Also, there are currently some statements in 4.3.28 and 4.5.3 that should be reviewed (I’m not sure if these issues should be fixed as part of the definition correction of ESS.):

In 4.3.28.3.4 it states: “… the concept of the DS in a non-GLK ESS is replaced by the other components of the IEEE 802.1Q network.) (260.61) [“non-GLK” should be deleted]
In 4.5.3.2 mobility types are defined – the types defined apply to non-GLK, but there is no discussion of GLK mobility types or which of the defined types apply to GLK – this should probably be fixed but will probably require a text proposal (contribution).
4.5.3.3 Association seems to have a minor problem that it states: “Association is one of the services in the DSS.” (268.19) While this is a true statement it makes no mention of association for GLK which is described later in the section (268.29) and seems to me to not allow for association with out a DSS, which is not true as association is allowed with in a BSS and does not require an ESS. [Replace: “Association is one of the services in the DSS.” With: “Maintaining a list of APs and their associated STAs is one of the services in the DSS.”]
4.5.3.4 Reassociation also has the same minor problem that it states: “Reassociation is one of the services in the DSS.“ [Replace: “Reassociation is one of the services in the DSS” With: “Maintaining a list of APs and their associated STAs is one of the services in the DSS.”]
Note in clause 4.5.3.4 (269.17) there is a description of mobility for GLK.
4.5.3.5 Disassociation also has the same minor problem that it states: “Disassociation is one of the services in the DSS.” [Replace: “Disassociation is one of the services in the DSS” With: “Maintaining a list of APs and their associated STAs is one of the services in the DSS.”]

I support the idea of changing “ESS with a DS” to simply be “ESS”
Also is there anything we to address regarding “ESS Link” as part of the ESS definition fix?
Lastly, there are some interesting uses of ESS in clause 12 which may need review. e.g., can a STA be a member of an ESS and can a STA associate with an ESS.

Regards,

Joseph Levy

From: *** 802.11 Architecture Standing Committee *** <STDS-802-11-ARC@xxxxxxxxxxxxxxxxx> On Behalf Of Mark Hamilton
Sent: Monday, January 11, 2021 8:03 PM
To: STDS-802-11-ARC@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-ARC] GLK ESS?

--- This message came from the IEEE 802.11 ARC Reflector ---

External Mail

All,

I wasn’t sure if we really got to the bottom of Jouni’s questions about how our proposed changes to ESS and HESS definitions/description (in 11-20/0177, to be liaised to REVme) relate to GLK operation. I found the following in 802.11ak, that I thought solved the problem for us (4.3.5.1):

The architectural component used to interconnect infrastructure

BSSs is the DS for non-general link (non-GLK) operation. The DS and extended service set (ESS) are

mechanisms for expanding connectivity for non-GLK operation. For GLK operation, an IEEE 802.1Q

bridge might be used to form an extended network (see 4.3.27).

Hopefully, that’s helpful, as I believe it means we don’t have to worry about GLK in our changes.

If anybody think we should still add a NOTE (or something similar) near the ESS definition, please respond to this reflector. (Personally, I think that is beyond our intent of “fixing” the ESS definition, but it could be argued we’re clarifying things, “while we’re at it”.)

That said, I agree with Jouni that there is an occurrence of “ESS with a DS” in 802.11ak (and now in REVmd), in 4.5.3.4:

The reassociation service is invoked to “move” a current association of a non-AP STA from one AP to

another. In an ESS with a DS, the reassociation service informs the DS of the current mapping between AP

and STA as the STA moves from BSS to BSS within the ESS.

I agree that this is redundant, and should just be “In an ESS, the reassociation service…” Do we want to suggest fixing that in our liaison (“while we’re at it”), or leave that for a REVme comment?

Mark

To unsubscribe from the STDS-802-11-ARC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-ARC&A=1