{"text_format":"1","workbook":"xlsx","n_sheets":3,"sheets":["Title","Comments","References"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Title","index":0,"n_rows":15,"n_cols":3,"rows_kept":15,"cut":false,"hidden":false,"merged":[[28,1,28,4],[26,1,26,4],[30,1,31,4]]}
[null,"IEEE P802.11 Wireless LANs"]
[null,"Submission"]
["Designator:","doc.: IEEE 802.11-23/1423r0"]
["Venue Date:","August 2023"]
["First Author:","Joseph Levy, InterDigital"]
[]
["Subject:","Draft comments on 802-REVc D1_1 for discussion"]
["Full Date:","2023-8-28"]
["Author(s):","Name(s)","Joseph Levy"]
[null,"Affiliation","InterDigital, Inc."]
[null,"Address","111 W 33rd Street, New York, NY, 10120, USA"]
[null,"Phone: ","+1.631.4139"]
[null,"Fax: "]
[null,"email: ","jslevy@ieee.org"]
["Abstract:"]

{"sheet":"Comments","index":1,"n_rows":30,"n_cols":7,"rows_kept":30,"cut":false,"hidden":false,"merged":[[0,0,0,6],[3,0,3,6],[1,0,1,3],[2,0,2,3]]}
["Task Force Review and Working Group Ballot comment input form"]
["First name",null,null,null,"Surname\nThis heading contains additional text so that it contains more than 255 characters.  This is to ensure that the import to the Microsoft Access database uses the correct format so that subsequent fields are not truncated to 255 characters.  Version 6.2 of the MyBallot tool has been modified to look for this truncation and issue a warning if it happens.","Affiliation\nThis heading contains additional text so that it contains more than 255 characters.  This is to ensure that the import to the Microsoft Access database uses the correct format so that subsequent fields are not truncated to 255 characters.  Version 6.2 of the MyBallot tool has been modified to look for this truncation and issue a warning if it happens."]
[]
["Click on column headers for help"]
["Category","Page","Sub-clause","Line #","Comment","Proposed Change","Must Be Satisfied"]
["Technical",23,"1.1",19,"The statement: \"A specification for the identification of public, private, and standard protocols is included.\" seems out of place and not coupled to scope of this standard.  \nAlso the changes made to the scope, are not in line with the current scope of the PAR are these changes even allowed?\nFrom the PAR:\nScope of proposed standard: This standard contains descriptions of the IEEE 802(R) standards published by the IEEE for frame-based data networks as well as a reference model (RM) for protocol standards. A specification for the identification of public, private, and standard protocols is included.\nChange to scope of proposed standard: This standard contains descriptions of the IEEE 802(R) standards published by the IEEE for frame-based data networks as well as a reference model (RM) for protocol standards. The IEEE 802 architecture is defined, and a A specification for the identification of public, private, and standard protocols is included.","Suggest merging this statement with the preceding sentence. \"This standard contains descriptions of the IEEE 802® standards published by the IEEE for frame-based data networks, provides a reference model (RM) for protocol standards, and specifies the identification of public, private, and standard protocols.\"\nNote: if changes are made to the scope, the PAR must be revised.\nor\nreverting to the Scope provided in the PAR."]
["Technical",23,"1.2",24,"etc., was added to the list of network types, I assume because there are other types beside LAN, MAN, PAN, RAN. However, using etc. is a poor way of doing this.","Suggest changing the sentence to read: \"This standard serves as the foundation for the family of IEEE 802 standards published by IEEE for networking, including but not limited to local area networks (LANs), metropolitan area networks (MANs), personal area networks (PANs), and regional area networks (RANs).\""]
[null,25,"3.1",17,"The definition of EtherType does not state where it is used/can be found. e.g., in the MAC header or MSDU header. Should this be fixed?"]
["Technical",25,"3.1",27,"IEEE 802 network definition is removed.\nAre we ok with no definition?"]
["Technical",26,"3.1",28,"The definition of repeater - uses the phrase \"interconnect segments of the physical communications media\" - this seems very 802.3 based, would a more general definition be preferred or are we ok with the WM being a physical communications media?"]
["Editorial",27,"3.2",15,"DLL should follow DCN in the list.","Switch the list order for DLL and DCN."]
["Editorial",27,"3.2",39,"Address Block Large, Address Block Medium and Address Block Small - should all be all lower case.","Fix the case."]
["Editorial",27,"3.2",5,"The use of capitalization in clause 3.2 seems to be inconstant in the \"definitions\". Also the use of Acronyms and abbreviations in the \"definitions\" is inconsistent.  Note: the SA Style Manual uses lower case, and expands any acronyms or abbreviations.","Align the style with the IEEE SA Standards Style Manual."]
["Technical",30,"4.1",4,"Why is this a \"however\" statement?  This makes no sense.  This only makes sense if the preceding sentences say the scope provides PHYs and DLLs, which it does not.","Suggest Delete \"However, the scope of IEEE 802 standards is not limited to the physical layers (PHYs) and data link layers (DLLs).\""]
["Technical",30,"4.1",12,"New sentences describing scheduled frame transmission were added. This sentence states that the scheduled timing is \"network wide\", I don't think this is true for 802.11 as the timing is BSS based. Is change required to generalize or make this text more specific?"]
["Technical ",30,"4.1",40,"Layer 3 is not introduced or defined in this standard, though it is referenced in Annex B (informative) - B.5 (84.6). Either more context should be provided or a different defined term used. ","Suggest: \"Additionally, it is common to interconnect individual networks and bridged networks at protocol layers above the DLL in the protocol stack (e.g., devices called routers). The specification of interconnections at these higher layers in the protocol stack is outside the scope of IEEE 802 standards.\""]
["Technical",31,"4.1",33,"What does added the phrase \", which is typically a constantly changing environment\" add to this sentence.","delete: \", which is typically a constantly changing environment\" add to this sentence\""]
["Technical",31,"4.1",33,"The phrase \"that are inherent to using wireless medium\" is awkward, consider improving the wording.","Suggest: \"that are inherent to wireless transmission mediums\""]
["Editorial",31,"4.1",32,"Missing article ","Change: \"solutions address challenges\" \nTo: \"solutions address the challenges\""]
["Technical",42,"5.3.2.6",22,"This paragraph could use some clarification. My understanding is that TSN may support applications with the need for guaranteed data transport with low and bounded latency, low and bounded delay variation, and extremely low packet loss.  Also promises future development should not included in an IEEE specification. ","Suggest the paragraph should read: \"TSN features provide network protocols and mechanisms for use by applications that need guaranteed data transport with low and bounded latency, low and bounded delay variation, and extremely low packet loss is data streams. The TSN features are add-ons to the generic set of networking protocols and mechanisms to allow networks to support both TSN traffic streams as well as other traffic. Some TSN features are provided in:\""]
["Editorial",42,"5.3.2.6",30,"Reference [B1], [B6] in the main text are not correct, also on page 46 line 3 [B2] and [B4] are not correct. It seems that many of the [Bx] references are not correct.  Also if the document is to be referenced by a [Bx] it should not be listed in all it's detail next to the reference. ","Correct the [Bx] references."]
["Editorial",43,"5.3.2.7",6,"What is meant by: \"…. a series of standards and Bridging enhancements ….\".  802.1 provides standards that provide bridging enhancement for data center networking (DCN)","Change: \"The IEEE 802.1 Working Group provides a series of standards and Bridging enhancements for data center networking (DCN).\"\nTo:  \"The IEEE 802.1 Working Group develops standards that provide bridging enhancements for data center networking (DCN).\""]
["Editorial",null,null,null,"Capitalization of  Bridge to mean 802.1Q bridge.  This is very poor way to differentiate between a generic bridge and a 802.1Q compliant bridge.  There are issues when Bridge is at the beginning of a sentence (as both uses will use a capital B).  This also makes the standard less readable, and prone to errors as checking which \"bridge\" is intended can be difficult. ","Replace all capital \"B\" bridges with \"IEEE 802.1Q bridge\", or clarify that a .1Q bridge is a compliant IEEE 802.1Q bridge."]
["Technical",46,"6.2",19,"An error performance statement for wireless is added.  But, the statement says no guarantee of service can be given.  This is a strange statement as wireless is regularly used for services that require \"guarantees\" e.g. voice, video, and gaming. Should this statement be revised?"]
["Technical",48,"7.2.2",1,"Is 802.11 ok with the SNMP and NETCONF being the two examples of general-purpose management protocols? "]
["Technical",49,"8.2.1",30,"The note could be clearer that other non-802 might use MAC address as specified in this standard.","Change the note to read:\n\"NOTE—Other network standards that are not IEEE 802 standards might use MAC addresses that are compliant with this standard.\""]
["Technical",53,"8.4.2",30,"When SLAP is used it should ensure the unique assignment of local MAC addresses, to enable the unique assignment.","Change: \"enable\" to \"ensure\""]
["Technical",78,"B.2",12,"The term portal is introduced, but it is not defined.  Is this an issue?","define portal or provide reference to 802.11."]
["Editorial",77,"B.1",4,"There is a typo in the foot note, \"no\" should be \"now\".","Should read \"...which is now part of the current …\""]
["Editorial",79,"B.2",4,"Missing article ","Should read \"...which is now part of the current …\"… for APs, the distribution system and a portal.\""]

{"sheet":"References","index":2,"n_rows":1,"n_cols":1,"rows_kept":1,"cut":false,"hidden":false,"merged":[]}
["References:"]