I was asked to post the following proposed resolution of CID 477 to
the reflector:
|
Identifiers |
Comment |
Proposed change |
|
CID 477 Mark RISON |
It is not clear what an "entity" is |
Change "peer entity" to "peer STA" (x86) |
Discussion:
We have PHY, MAC, management, 802.1X, FST, sublayer, port access, multi-band and relay entities, but the peer entities in Clause 6 are just peer STAs.
Proposed changes:
Change “peer entity” to “peer STA” at the following locations:
|
Page |
Line |
Subclause |
Context |
|
406 |
13 |
6.3.14.2.1 Function |
a
peer entity. 6.3.14.2.2 Semantics of the service primitive The primitive parameters are as |
|
407 |
4 |
6.3.14.2.3 When generated |
a
peer entity to initiate one or more measurements. 6.3.14.2.4 Effect of receipt On |
|
410 |
27 |
6.3.16.2.3 When generated |
a
peer entity to report the results of measuring one or more channels. 6.3.16.2.4 |
|
410 |
41 |
6.3.16.3.1 Function |
a
peer entity. This management report is either a response to an |
|
413 |
33 |
6.3.17.3.1 Function |
a
peer entity. 6.3.17.3.2 Semantics of the service primitive The primitive parameters are as |
|
416 |
34 |
6.3.18.2.3 When generated |
a
peer entity to request that entity to report transmit power and link |
|
451 |
42 |
6.3.29.3.1 Function |
a
peer entity. 6.3.29.3.2 Semantics of the service primitive The primitive parameters are as |
|
457 |
52 |
6.3.32.2.3 When generated |
peer entity to request that entity to report transmit
power and |
|
506 |
6 |
6.3.48.2.1 Function |
a
peer entity. 6.3.48.2.2 Semantics of the service primitive The primitive parameters are as |
|
506 |
41 |
6.3.48.2.3 When generated |
a
peer entity to initiate one or more transactions. 6.3.48.2.4 Effect of receipt On receipt |
|
508 |
18 |
6.3.49.2.3 When generated |
a
peer entity to report the results of one or more transactions. 6.3.49.2.4 Effect |
|
508 |
33 |
6.3.49.3.1 Function |
a
peer entity. 6.3.49.3.2 Semantics of the service primitive The primitive parameters are |
|
511 |
6 |
6.3.51.2.1 Function |
a
peer entity. 6.3.51.2.2 Semantics of the service primitive The primitive parameters are as |
|
511 |
42 |
6.3.51.2.3 When generated |
a
peer entity to initiate one or more diagnostic transactions. 6.3.51.2.4 Effect of receipt On |
|
512 |
61 |
6.3.52.1.3 When generated |
a
peer entity to report the results of one or more diagnostic transactions. Name |
|
513 |
28 |
6.3.52.2.1 Function |
a
peer entity. 6.3.52.2.2 Semantics of the service primitive The primitive parameters are as |
|
514 |
49 |
6.3.53.2.1 Function |
a
peer entity. 6.3.53.2.2 Semantics of the service primitive The primitive parameters are as |
|
515 |
22 |
6.3.53.2.3 When generated |
peer entity to convey location configuration information.
6.3.53.2.4 Effect of receipt On receipt |
|
517 |
15 |
6.3.53.5.1 Function |
a
peer entity, in response to a Location Configuration Request frame. 6.3.53.5.2 Semantics of |
|
517 |
52 |
6.3.53.5.3 When generated |
peer entity to convey location configuration information.
6.3.53.5.4 Effect of receipt On receipt |
|
518 |
33 |
6.3.54.2.1 Function |
a
peer entity. 6.3.54.2.2 Semantics of the service primitive The primitive parameters are as |
|
519 |
15 |
6.3.54.2.3 When generated |
a
peer entity to help convey location information. 6.3.54.2.4 Effect of receipt On receipt |
|
520 |
58 |
6.3.55.2.1 Function |
a
peer entity. Figure 6-16—Timing measurement primitives and timestamps capture MLME |
|
521 |
26 |
6.3.55.2.3 When generated |
peer entity. 6.3.55.2.4 Effect of receipt On receipt
of this primitive, the MLME |
|
522 |
15 |
6.3.55.4.1 Function |
a
peer entity. 6.3.55.4.2 Semantics of the service primitive The primitive parameters are as |
|
523 |
14 |
6.3.55.4.3 When generated |
a
peer entity. 6.3.55.4.4 Effect of receipt On receipt of this primitive, the MLME |
|
526 |
47 |
6.3.56.2.1 Function |
a
peer entity. 6.3.56.2.2 Semantics of the service primitive The primitive parameters are as |
|
527 |
50 |
6.3.56.2.3 When generated |
a
peer entity. 6.3.56.2.4 Effect of receipt On receipt of this primitive, the MLME |
|
529 |
10 |
6.3.56.4.1 Function |
a
peer entity. 6.3.56.4.2 Semantics of the service primitive The primitive parameters are as |
|
530 |
33 |
6.3.56.4.3 When generated |
a
peer entity. 6.3.56.4.4 Effect of receipt On receipt of this primitive, the MLME |
|
545 |
41 |
6.3.58.5.3 When generated |
a
peer entity to convey FMS information. 6.3.58.5.4 Effect of receipt On receipt of |
|
546 |
45 |
6.3.59.2.1 Function |
a
peer entity. 6.3.59.2.2 Semantics of the service primitive The primitive parameters are as |
|
547 |
32 |
6.3.59.2.3 When generated |
peer entity. 6.3.59.2.4 Effect of receipt On receipt
of this primitive, the MLME |
|
548 |
51 |
6.3.60.2.1 Function |
a
peer entity, in response to a Collocated Interference Request frame. 6.3.60.2.2 Semantics of |
|
549 |
23 |
6.3.60.2.3 When generated |
peer entity to convey collocated interference information.
6.3.60.2.4 Effect of receipt On receipt |
|
556 |
42 |
6.3.62.4.1 Function |
a
peer entity, in response to a WNM Sleep Mode Request frame. 6.3.62.4.2 Semantics |
|
556 |
62 |
6.3.62.4.3 When generated |
a
peer entity to convey WNM sleep mode information. Name
Type Valid range |
|
575 |
53 |
6.3.67.2.1 Function |
a
peer entity. 6.3.67.2.2 Semantics of the service primitive The primitive parameters are as |
|
576 |
27 |
6.3.67.2.3 When generated |
a
peer entity to initiate a WNM notification. 6.3.67.2.4 Effect of receipt On receipt |
|
578 |
3 |
6.3.68.1.3 When generated |
a
peer entity to report the results of the WNM notification. 6.3.68.1.4 Effect |
|
578 |
18 |
6.3.68.2.1 Function |
a
peer entity. 6.3.68.2.2 Semantics of the service primitive The primitive parameters are as |
|
595 |
58 |
6.3.74.2.3 When generated |
a
peer entity to request the adjustment of the peer entity’s TBTT. Name |
|
595 |
59 |
6.3.74.2.3 When generated |
the
peer entity’s TBTT. Name
Type Valid range |
|
617 |
33 |
6.3.80.2.3 When generated |
specified
peer entity. 6.3.80.2.4 Effect of receipt On receipt of this primitive, the MLME |
|
618 |
53 |
6.3.81.2.1 Function |
a
peer entity. 6.3.81.2.2 Semantics of the service primitive The primitive parameters are |
|
619 |
24 |
6.3.81.2.3 When generated |
a
peer entity to communicate QMF policy information. 6.3.81.2.4 Effect of receipt On receipt of |
|
619 |
39 |
6.3.81.3.1 Function |
a
peer entity. 6.3.81.3.2 Semantics of the service primitive The primitive parameters are as |
|
620 |
26 |
6.3.81.3.3 When generated |
a
peer entity. 6.3.81.3.4 Effect of receipt The SME is notified of the receipt |
|
620 |
58 |
6.3.81.4.3 When generated |
a
peer entity. 6.3.81.4.4 Effect of receipt On receipt of this primitive, the MLME |
|
622 |
16 |
6.3.81.6.1 Function |
a
peer entity. 6.3.81.6.2 Semantics of the service primitive The primitive parameters are as |
|
622 |
51 |
6.3.81.6.3 When generated |
a
peer entity. 6.3.81.6.4 Effect of receipt On receipt of this primitive, the parameters |
|
623 |
6 |
6.3.81.7.1 Function |
a
peer entity, in response to a QMF Policy Change frame. 6.3.81.7.2 Semantics of |
|
623 |
41 |
6.3.81.7.3 When generated |
a
peer entity to convey the results of the QMF policy change procedure. 6.3.81.7.4 |
|
635 |
53 |
6.3.84.4.1 Function |
a
peer entity. 6.3.84.4.2 Semantics of the service primitive The primitive parameters are |
|
639 |
35 |
6.3.85.4.1 Function |
a
peer entity. 6.3.85.4.2 Semantics of the service primitive The primitive parameters are |
|
642 |
6 |
6.3.86.3.1 Function |
a
peer entity. 6.3.86.3.2 Semantics of the service primitive The primitive parameters are |
|
676 |
30 |
6.3.96.2.1 Function |
a
peer entity. 6.3.96.2.2 Semantics of the service primitive The primitive parameters are |
|
677 |
4 |
6.3.96.2.3 When generated |
the
peer entity. 6.3.96.2.4 Effect of receipt On receipt of this primitive, the MLME |
|
677 |
50 |
6.3.96.3.2 Semantics of the service primitive |
the
peer entity. ENABLEMENT_DENIED is used to indicate denial due to restriction |
|
678 |
7 |
6.3.96.3.3 When generated |
the
peer entity or when an unspecified failure occurs. 6.3.96.3.4 Effect of receipt On receipt |
|
678 |
21 |
6.3.96.4.1 Function |
a
peer entity. 6.3.96.4.2 Semantics of the service primitive The primitive parameters are |
|
678 |
38 |
6.3.96.4.2 Semantics of the service primitive |
the
peer entity from which a GDD Enablement Request frame was received. |
|
679 |
6 |
6.3.96.5.1 Function |
the
peer entity. 6.3.96.5.2 Semantics of the service primitive MLME-GDDENABLEMENT.response |
|
679 |
52 |
6.3.96.5.3 When generated |
peer entity. 6.3.96.5.4 Effect of receipt On receipt
of this primitive, the |
|
679 |
22 |
6.3.96.5.2 Semantics of the service primitive |
the
peer entity from which a GDD Enablement Request frame was received.
DialogToken |
|
679 |
37 |
6.3.96.5.2 Semantics of the service primitive |
the
peer entity. ENABLEMENT_DENIED is used to indicate denial due to restriction |
|
683 |
32 |
6.3.97.5.3 When generated |
the
peer entity. 6.3.97.5.4 Effect of receipt On receipt of this primitive, the MLME |
|
693 |
52 |
6.3.102.5.3 When generated |
a
peer entity to convey AID assignment information. 6.3.102.5.4 Effect of receipt On |
|
702 |
29 |
6.3.107.5.3 When generated |
a
peer entity to convey TWT assignment information. 6.3.107.5.4 Effect of receipt On receipt |
|
708 |
29 |
6.3.110.5.3 When generated |
a
peer entity to convey Header Compression information. 6.3.110.5.4 Effect of receipt On receipt |
|
710 |
14 |
6.3.112.2.1 Function |
a
peer entity. 6.3.112.2.2 Semantics of the service primitive The primitive parameters are |
|
710 |
48 |
6.3.112.2.3 When generated |
the
peer entity. 6.3.112.2.4 Effect of receipt On receipt of this primitive, the MLME |
|
710 |
54 |
6.3.112.2.4 Effect of receipt |
the
peer entity. Name
Type Valid range |
|
711 |
37 |
6.3.112.3.3 When generated |
the
peer entity. 6.3.112.3.4 Effect of receipt On receipt of this primitive, the SME |
|
711 |
50 |
6.3.112.4.1 Function |
a
peer entity. 6.3.112.4.2 Semantics of the service primitive The primitive parameters are |
|
712 |
64 |
6.3.112.5.3 When generated |
a
peer entity to convey control response MCS negotiation information. Name
Type |
|
713 |
4 |
6.3.112.5.4 Effect of receipt |
the
peer entity indicated by the
PeerSTAAddress parameter. 6.3.113 S1G relay (de)activation 6.3.113.1 General The |
|
713 |
20 |
6.3.113.2.1 Function |
a
peer entity. 6.3.113.2.2 Semantics of the service primitive The primitive parameters are |
|
713 |
45 |
6.3.113.2.3 When generated |
the
peer entity. 6.3.113.2.4 Effect of receipt On receipt of this primitive, the MLME |
|
713 |
52 |
6.3.113.2.4 Effect of receipt |
the
peer entity. 6.3.113.3 MLME-S1GRELAYACTIVATE.confirm 6.3.113.3.1 Function This primitive reports the result of a relay |
|
714 |
26 |
6.3.113.3.3 When generated |
the
peer entity. 6.3.113.3.4 Effect of receipt On receipt of this primitive, the SME |
|
714 |
39 |
6.3.113.4.1 Function |
a
peer entity. 6.3.113.4.2 Semantics of the service primitive The primitive parameters are |
|
715 |
39 |
6.3.113.5.3 When generated |
a
peer entity to convey relay activation information. 6.3.113.5.4 Effect of receipt On receipt |
|
715 |
46 |
6.3.113.5.4 Effect of receipt |
the
peer entity indicated by the
PeerSTAAddress parameter. 6.3.114 DCS procedure 6.3.114.1 General This
subclause |
Proposed resolution:
REVISED
Make the changes shown under “Proposed changes” for CID 477 in <this document>, which identify the specific locations where “peer entity” is to be changed to “peer STA”.
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601
ROYAUME UNI WWW:
http://www.samsung.com/uk
To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1