Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0:j€8Lp€@L>‚MkUTION PROPOSED DB G JU_isBDF@ LM E BQO L!L"A#A$L%!T&&G'(S(,M).M*0L+2L,4 A-5X.:L/YX?^E@`LAeMBiQCoQDsXEuWFyLG}KHKI€MJ€AKCL€EM€YN€ AP€ AQ€ AR€DS€LT€ AU€MVBWDX€LY€ ZZ€"X[€$O\€'A]€*K^ B_€,L` Ba€- AbCc€. BdDeFfAgCh€1@O!@(HBAM3016AUG95@ AAzHH(FG(HH(d}HzA` 'dD7R0"`?08(Jg0HutHǞ`~ <v`JUO/ ?/<0@f&?r0Hn<N!*p.??` p20?RCp2Ho`/ L N^NuNVH $n8. J*g DWD`(6HS`/?HnN ngp` SC ClpLN^NuNVH $n8. J*g j WD`(6HR`/?HnN ngp` RCj opLN^NuNVH0$n J)&RPP6+ J*0L N^NuNVH0,.$n &R-S/+@/.N$JQ4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  ,  X57Vڻ56wI@Gbu0SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDec7{  5/8/2001@ BALLOT NUMBERCHANGE CLAUSE EDITORCOMMENT NUMBER COMMENT TYPEDECISION OF GROUPDOCUMENT NUMBEREDITOR'S ACTIONS EDITOR'S NOTEEDITOR'S QUESTION FIRST NAMEGROUP'S ACTION ITEMS GROUP'S NOTES LAST NAMEMEMBERSHIP TYPEREASON REASON FOR GROUP DECISIONREASON PROPOSEDRECOMMENDATION RESOLUTION BYRESOLUTION OF GROUP O!ABCDEFGHIJKLMNOPQRSTUVWXYZ[EPro 5.0F!2(M1,,./: AM PMYyTtNnFfNALL OTABSP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  ,  ABCDEFGHI J K L M NOPQRSTUVWXYZ[    !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ DADocument NumberB GA Ballot NumberB GA First NameB GA Last NameB GAMembership TypeB GAVoteB GAComment NumberB GA Comment TypeB G AStarting Page NumberB G AStarting Line NumberB G ASectionB G AChangeB G AReasonB GA Clause EditorB GAResolution ProposedB GAReason Proposed $AIEEE 802.16/D2-2001B3`A Layout #1B8$$$$@6A  $,.YesNo/,  , : AM PMB   C  $,.YesNo/,  , : AM PMD   E  $,.YesNo/,  , : AM PMF   G  $,.YesNo/,  , : AM PMH   I  $,.YesNo/,  , : AM PM URESOLUTION PROPOSEDSECTION STARTING LINE NUMBER STARTING PAGE NUMBER VOTE             ,GARecommendationB GA Resolution byB GAResolution of GroupB GADecision of GroupB GAReason for Group DecisionB GA Group's NotesB GAGroup's Action ItemsB GAEditor's ActionsB GA Editor's NoteB GAEditor's QuestionB GAEditor's Action ItemsB G B  "EDITOR'S ACTION ITEMSEDITOR'S ACTIONS EDITOR'S NOTEEDITOR'S QUESTION FIRST NAMEGROUP'S ACTION ITEMS GROUP'S NOTES LAST NAMEMEMBERSHIP TYPEREASON REASON FOR GROUP DECISIONREASON PROPOSEDRECOMMENDATION RESOLUTION BYRESOLUTION OF GROUPBDocument NumberD Ballot NumberF First NameH Last NameJMembership TypeLVoteNComment NumberP Comment TypeRStarting Page NumberTStarting Line NumberVSectionXChangeZReason\ Clause Editor^Resolution Proposed`Reason ProposedbRecommendationd Resolution byfResolution of GrouphDecision of GroupjReason for Group Decisionl Group's NotesnGroup's Action ItemspEditor's Actionsr Editor's NotetEditor's QuestionvEditor's Action Items @BBAl  !"#$%&'()*+,-./012345lB24(((((( ( ( ( ( ( ( ((((( ("($(&(((*(,(.(0(2(((*(,(.(0(2 J   K  $,.YesNo/,  , : AM PML   M  $,.YesNo/,  , : AM PMN   O  $,.YesNo/,  , : AM PMP   Q  $,.YesNo/,  , : AM PMR   S  $,.YesNo/,  , : AM PMT    U  $,.YesNo/,  , : AM PMV   W  $,.YesNo/,  , : AM PMX   Y  $,.YesNo/,  , : AM PMZ   [  $,.YesNo/,  , : AM PM\   ]  $,.YesNo/,  , : AM PM^    _  $,.YesNo/,  , : AM PM`   a  $,.YesNo/,  , : AM PMb   c  $,.YesNo/,  , : AM PMd   e  $,.YesNo/,  , : AM PMf   g  $,.YesNo/,  , : AM PMh    i  $,.YesNo/,  , : AM PMj   k  $,.YesNo/,  , : AM PMl   m  $,.YesNo/,  , : AM PMn   o  $,.YesNo/,  , : AM PMp   q  $,.YesNo/,  , : AM PMr    us  $,.YesNo/,  , : AM PMt   u  $,.YesNo/,  , : AM PMv   A(!'*: ,59<L>EKN^PF]`p b$o CJoseDCostaEMemberG807H Editorial A;Reason for abstaining: I have not had the time to contribute to the development of this standard, but I believe that overall, it does NOT meet the needs of the industry, particularly if it has to support both types of systems, above and below 10 GHz. The standard should be much more IP-centric than what it is now.;SNo specific action requested.TRejectedXf) none neededCKeithDDoucetEMemberG748HTechnical, BindingLProposals for the changes of message formats that support the above comments are included in document number 802.16-3c-01/37 dated March 7, 2001M'Faster to market with matured standard.S047T SupercededXf) none neededCRogerDMarksEMemberG064H EditorialKGlobalL(change "number of PS" to "number of PSs"Mstylistic consistencyQAcceptedRphilTAcceptedXe) doneCRogerDMarksEMemberG065H EditorialKGlobal@ (4         "$&(*,.024(((((( ( ( ( ( ( ( ((((( ("($(&(((*(,(.(0(2(((*(,(.(0(2 F23#456 2    C T U U7$# D&6(#5 8H!:&G"JZ#L6Y$\l%^k&n~'p!}E()*+3,-./*019 Br tc   %2    C T U U7$#@@@A Layout #1A Layout #1B8$$$$@6A  $,.YesNo/,  , : AM PMB   C  $,.YesNo/,  , : AM PMD   E  $,.YesNo/,  , : AM PMF   G  $,.YesNo/,  , : AM PMH   I  $,.YesNo/,  , : AM PM@Lcchange "upstream" to "uplink" and "downstream" to "downlink" include Figures 9 and 10 in the changeMJconsistency with earlier decision, but the old terms crept back in somehowQAcceptedRphilTAcceptedXe) doneCRogerDMarksEMemberG066H EditorialKGlobalL,change "baud rate" to "symbol rate" globallyM"baud rate" is poor language. If "baud" is "symbol rate", then "baud rate" is "symbol rate rate" "symbol rate" is already used in 8.2.3 (five places), 8.2.4.3.1, 8.2.4.3.3.1, 8.2.4.5.4, 11.1.1.1 and Figure 140.QAcceptedRphilTAcceptedXe) doneCRogerDMarksEMemberG067H EditorialKGlobalL+Replace "IEEE " with "P" in running header.MIEEE style requirement.QAcceptedRphilSchange "802" to "P802" instead.TAccepted-ModifiedXe) doneCRogerDMarksG820K3LDefine: Wireless Access: End-user radio connection(s) to core networks. Fixed Wireless Access: Wireless access application in which the location of the SS and the BS are fixed in location. M_Terms used in document. Definitions match those of 802.16.2, which were coordinated with ITU-R.Xe) doneAShould we use the following definitions from 802.16.2? broadband: Having instantaneous bandwidths greater than around 1 MHz and supporting data rates greater than about 1.5 Mbit/s. broadband wireless access (BWA): Wireless access in which the connection(s) capabilities are broadband.CRogerDMarksG821KglobalL-Make sure all Figs and Tables are referencedXi) to do CRogerDMarksG822KglobalL,Make sure all tables have numbers and titlesXi) to do CRogerDMarksG823K3&4LUDeleted from abbreviation and definition lists: PHSR Payload Header Suppression RuleMnot usedXe) done CChetDShiraliEMemberG749HTechnical, BindingLProposals for the changes of message formats that support the above comments are included in document number 802.16-3c-01/37 dated March 7, 2001M'Faster to market with matured standard.S047T SupercededXf) none needed CRogerDMarks EMemberG068H EditorialI0KGlobalL-Change "MAY" to "may" Change "must" to "must"MProper English. QAcceptedRphilS+the second point should be "MUST" to "must"TAccepted-ClarifiedXe) done CRogerDDurandEMemberG523H EditorialI1 AMy only two general concerns are: #1 the wide scope of the document. Too often the document speaks of multiple connections/configurations/modes/FECs/codings as though we need all of them. In truth this will become an interoperability nightmare in the future. The WG needs to try and refine or restrict the number of possibilities as this has gotten out of hand. The complexity of this system will limit the success of the standard. A standard is not deemed successful until you have at least th B*ree competing vendors with interoperability. Generally, members should ask why do we need this? If no one sees a need to increase the number of variables, then don't... #2 Another pass will be needed to define required operating modes/levels from optional and within that a/the default/start mode.PVI am in complete agreement with his comment but there is no specific changes specifiedQRejectedRphilTRejectedXf) none neededCVicenteDQuilezEObserverG494H EditorialI9J49KToCLChange the title of Figure 146 to "Format of the Transmission Convergence Sublayer Packet". It also affects Figure 159 and Figure 168M ConsistencyQAcceptedRphilS0do the requested changes in the figure captions.TAccepted-ClarifiedXe) doneYMadded "Downlink Mode A","Downlink Mode B","Uplink", to distinguish the 3 figsCRonaldDMeyerEMemberG524H EditorialI11J15KTablesL.Change "Auth Rej" to "Authorization Rejection"Mcompleteness and carificationO(also make the change on page 78 line 54. QAccepted-ModifiedRphilSRChange "Auth Rej" to "Authorization Reject". Make the change on page 78, line 54.TAccepted-ModifiedXe) doneCG. JackDGarrisonEMemberG354HTechnical, BindingI13J1KTBDsLResolve the noted TBDsM6How can you vote approval on a document that has TBDs?T SupercededXf) none neededC Chao-ChunDWangEMemberG750HTechnical, BindingI13J4KTDBsLAll TDBs should be deletedM_TBDs are for uncomplete specifications instead there should be references to works in progress.TAccepted-DuplicateXj) awaiting resolutionYOnly remaining TBDs: (1) under "Root Certificate" countryName=US organizationName=TBD organizationalUnitName=TBD commonName=TBDCKenDStanwoodEMemberG034H EditorialI15J23K1.1L.change "application.The" to "application. The"MtypoQAcceptedRphilTAcceptedXe) doneCVicenteDQuilezEObserverG495H EditorialI16J3K1.3L0Add to the Figure 1 the protocol standard 802.1EM*Completeness (802.1E is named in the text)!O0give the action to Ken who can delegate to Andy.QAccepted-ClarifiedRphilTRejectedXf) none neededCRonaldDMeyerEMemberG525H EditorialI16J55K1.3L7delete the "comma" between architecture and environmentM correct typo QAcceptedRphilTAcceptedXe) doneCRogerDMarksEMemberG069HTechnical, Non-bindingI17J10K1.4LAdd a figure which illustrates the scope of, and relationship between, terms like Base Station, Subscriber Station, Basic Connection, Connection, and Service Flow. MAid to understanding.S078T SupercededUaNo specific input was provided. The spirit of the comment will be considered in future comments.Xf) none neededCVicenteDQuilezEObserverG496H EditorialI17J12K1.4L=Expand Figure 2, to incorporate TC (Transmission Convergence)M CompletenessOfask Andy again. The change will also require an additional arrow from the management entity to the TCQAccepted-ClarifiedRphilTRejectedXf) none neededCRogerDMarksEMemberG070H EditorialI17J17K1.4 "LpChange "Service Specific Convergence Sublayers: IP, Ethernet, ATM, etc." to "Packet or ATM Convergence Sublayer"MTo follow current CS structure.O4change "IP, Ethernet, ATM, etc." to "Packet and ATM"QAccepted-ModifiedRphilS,delete "IP, Ethernet, ATM, etc." on line 19.TAccepted-ModifiedXe) doneCRonaldDMeyerEMemberG526H EditorialI17J46K1.4.1 and 1.4.2LText of these sections is missing. Either include descriptive text or delete the sections here and anywhere that references these sectionsMwThe figure provides the needed information, perhaps these sections where text descriptions would appear are not needed.PPno specific recommendation was given. These sections must be dealt with though.QRejectedRphilS035T SupercededXf) none neededCVicenteDQuilezEObserverG497H EditorialI17J46K1.4L;Either delete 1.4.1 and 1.4.2 or fill in these sub-sectionsM ConsistencyQRejectedRphilS035T SupercededXf) none neededCWaltDRoehrEMemberG709H EditorialI17J46K1`4!#*L\Either delete 1.4.1 and 1.4.2 or give them some text or add them to the TBD list on page 13.M@Sections should consist of more than a section number and title.QRejectedRphilS035T SupercededXf) none neededCKenDStanwoodEMemberG035H EditorialI17J46K1.4.1L/delete sections 1.4.1 and 1.4.2 or fill them inMEmpty sectionsQRejectedRphilSdelete sections 1.4.1 and 1.4.2TAccepted-ModifiedXe) doneCWaltDRoehrEMemberG710H EditorialI17J52K2.LAre all of these references "normative". From their titles some (such as lines 28 & 29 [RFC-1633] R. Braden et. al.,"Integrated Services in the Internet Architecture: An Overview", IETF RFC-1633, June 1994.) would appear to be Informative. MJust does not look right.Pno clear change was specified.QRejectedRphilSactionTAccepted-Modified"$nACarl will clean up this section and move the non-Normative references to the bibliography section: The following should not be included in the Normative references list (key given): DOCSIS EN 300 421 EN 301 199 EN 301 210 F.BWA G.114 I.210 J.83 J.116 RFC-1633 RFC-1750 RFC-2210 RFC-2212 RFC-2202 RFC-2205 RFC-2475 RSA2 The following should be added to normative references: [RFC-2104] H. Krawczyk,M. Bellare, R. Canetti "HMAC: Keyed-Hashing for Message Authentication" ,IETF RFC-2104, FebruB^ary 1997 The following should be added to bibliograghy (properly formatted): [SCHNEIER]"Applied Cryptography: Protocols, Algorithms, and Source Code in C, 2nd Edition" by Bruce Schneier. [EN 300 421] is mentionen in the mode A section All references to FIPS-46 or FIPS-46-1 should be to FIPS-46-2 which I think is the current version of FIPS-46.LXe) done#%ACan we get rid of this reference: [RSA1]RSA Laboratories, PKCS #1: RSA Encryption Standard. Version 1.5, November 1993. and just use this one instead: [RSA2]RSA Laboratories, PKCS #1 v2.0: RSA Cryptography Standard, October 1, 1998. {renamed from RSA3}A7The references and bibliography still need a lot of work. They need to be formatted correctly and consistently, ordered, and checked. The references (normative) should be carefully linked to sections of the text. The bibliography items need to be ordered. Those not cited should be moved to the end, or deleted.7CRogerDMarksEMemberG071H EditorialI18J9K2L9Change ""1997-08" to "1997-98" Change "11/112" to "11/12"M6Obvious typos, but entire reference should be checked.QAcceptedRphilTAcceptedXe) doneCRonaldDMeyerEMemberG527H EditorialI18J9K2LChange 11/112" to "11/12" "M Correct typQAcceptedRphilS071T SupercededXf) none neededCRonaldDMeyerEMemberG528H EditorialI18J25K2$&LeInsert the text "(FIPS PUB)" abbreviation after the word "Publications" and before the number "46-2" MWCompeteness to match other references and provide the abbreviation after the first use.QAcceptedRphilTAcceptedXe) done CRonaldDMeyerEMemberG529H EditorialI20J18K2LMInsert the proper date for the RSA Cryptography Standard in place of "xxxxxx"M(Need proper date for referenced standardPwhat is the proper date?RphilSactionTAccepted-ModifiedWCarl will address this commentXe) doneY\Carl will do the hands-on editing for this comment. Stanley provided the info (Oct 1, 1998).!CKenDStanwoodEMemberG498HTechnical, Non-bindingI20J46K3.7 A9Change the definition of connection to: "A unidirectional mapping between BS MAC and SS MAC peers for the purpose of transporting a service flow's traffic. Connections are identified by a CID. All traffic is carried on a connection, even for service flows which implement connectionless protocols, such as IP."9Mclarity%'!TAcceptedXe) done"CRonaldDMeyerEMemberG530H EditorialI20J52K3L!Change the word "be" to "between"M Correct typeQAcceptedRphilTAcceptedXe) done#CWaltDRoehrEMemberG711H EditorialI20J52K3.8Lreplace "be" with "between"M#"be" makes no sense in this contextO550Q SupercededRphilS530TAccepted-DuplicateXe) done$CKenDStanwoodEMemberG036H EditorialI20J54K3.9L!Delete Data Grant Type definitionMEIt's an old term from when DOCSIS had short and long data grant typesQAcceptedRphilTAcceptedXe) done%CWaltDRoehrEMemberG712H EditorialI20J56K3.10LYReplace "downlink" with "in the link that originates at the BS and terminates at the SS."Musing "downlink" in the defination of downlink is circular and does not tell uninformed which is the downlink. I assume you had good reason to NOT just echo the Uplink definition, i.e., "information flow" is important here and not important in "Uplink".QAcceptedRphilS037T SupercededXf) none needed&CKenDStanwoodEMember&(&G037H EditorialI20J58K3.10LFChange definition of downlink to "The direction from the BS to the SS.M)Make consistent with definition of uplinkO712Q SupercededRphilTAcceptedXe) done'CWaltDRoehrEMemberG713H EditorialI21J1K3.13L Change "MAP" in heading to "Map"M/to best of my knowledge map" is not an acronym"P=MAP in all-caps is consistently used throughout the document.QRejectedRphilSUthroughout the document, change "MAP" to "map" except when preceded by "DL-" or "UL-"TAccepted-ModifiedXe) done(CRogerDMarksEMemberG072HTechnical, Non-bindingI21J8K3.15LChange definition of Frame from "A frame is a fixed duration of time, which contains both transmit and receive intervals." to "A structured data sequence of fixed duration used by some physical layers."MFrame should be defined in terms of data structure, not just in terms of time. For example, a frame cannot be "1 ms", although its duration may be 1 ms.')s(SjFollowing the suggested change, add "A frame may contain both an uplink subframe and a downlink subframe."TAccepted-ClarifiedXe) done)CKenDStanwoodEMemberG038H EditorialI21J32K3.21LChange "donwlink" to "downlink"MtypoQAcceptedRphilTAcceptedXe) done*CRogerDMarksEMemberG073H EditorialI21J40K3.23LChange "PS" to "PSs" Change "where N = 2m (m = 0,...7)" to "where N=2^m and m is an integer ranging from 0 through 7" Make same change at page 56, line 44.Mconsistency and precisionQAcceptedRphilTAcceptedXe) done+CVicenteDQuilezEObserverG499H EditorialI21J41K3L=Substitute last part of the sentence to read "N = 0, .. 255" M,Consistency with a previous comment from KenQRejectedRphilTRejectedXf) none needed,CWaltDRoehrEMemberG714H EditorialI21J44K3.24LJ"polling" to "information transmition, including polling and data delivery(*,MI don't believe "polling" includes data delivery. If so, "Polling" should be included in definitions to make explicite this atypical use of word "poll".QAcceptedRphilAbignore the above change, complete the following changes. On page 38, line 23, change the word "to multicast groups" to "on multicast connections". On page 21, line 23, change "Multicast Group" to "Multicast Polling Group." On page 21, line 23, delete "or connections". On page 195, line 6, change "multicast group's traffic" to "multicast connection"bTAccepted-ModifiedXe) doneYA"Multicast Group" and "or connections" were on page 21, line _43_-CVicenteDQuilezEObserverG500H EditorialI21J54K3LChange PSU by PDUMGrammarQAcceptedRphilTAcceptedXe) done.CRogerDMarksEMemberG074HTechnical, Non-bindingI22J4K3LgChange PDU definition to: "A data unit generated by a particular protocol layer for an adjacent layer.")+.MCurrent definition ("A data unit generated by a particular protocol layer for its next lower layer") is inaccurate; data could be sent above or below.Ssee comment 431T SupercededXf) none needed/CStanleyDWangEObserverG431HTechnical, Non-bindingI22J4K3.32 AChange the definition to read "Protocol Data Unit (PDU): The data unit exchanged between peer entities of the same protocol layer. On the downward direction, it is the data unit generated for the next lower layer. On the upward direction, it is the data unit received from the previous lower layer (see Figure 3)." Figure 3 is submitted as a separate contribution (see IEEE 802.16-01/11).M,The original definition is not clear enough.Sfigure 3 to be inserted is not to replace the current figure three. this is a new figure to be inserted after the current figure 2.TAccepted-ClarifiedXe) done0CRogerDMarksEMemberG075HTechnical, Non-bindingI22J7K3.33*,0L(a) Change "A unit of granularity equal to 4 modulation symbols" to "A group of 4 modulation symbols" (b) Change "Physical-Slot" to "Physical Slot" (c) Change "QAM-4" to "QPSK" and "8" to "4"M(a) more precision. A "unit of granularity" is not clearly defined. (b) consistency within document (c) Current PHYs don't support QAM-4.Sby 039T SupercededXf) none needed1CKenDStanwoodEMemberG039HTechnical, Non-bindingI22J7K3.33 A;Change definition of Physical Slot to "A physical layer dependant unit of granularity for allocating bandwidth. For instance in the 10-66 GHz PHY modes a PS is equivalent to 4 modulation symbols. So, in this PHY mode each PS represents 8, 16, or 24 bits (using QAM-4, QAM-16, or QAM-64 modulation, respectively).";M2Make definition independent of the PHY mode used. SAaccept the first sentence that is suggested and discard the rest.TAccepted-ModifiedXe) done2CVladimirDYanoverEMemberG076H EditorialI22J7K3+-2LAdd the definition of PPDU: "PHY Protocol Data Unit (PPDU): A continuous Radio transmission generated by PHY layer. PPDUs are separated by time intervals with no transmission" M)This acronym is used e.g. in section 8.1 OBdo not define PPDU. Instead, remove MSDU. This should be MAC SDUQAccepted-ModifiedRphilSinstead, change all occurances throughout the document from 'PPDU' to 'PHY PDU'. Also remove 'MSDU' from page 24, line 12, and change all other occurances throughout the document from 'MSDU' to 'MAC SDU'.TAccepted-ModifiedXe) done3CRogerDMarksEMemberG077HTechnical, Non-bindingI22J26K3LeChange SDU definition to: "A data unit handed to a particular protocol layer from an adjacent layer."MCurrent definition ("A data unit handed to a particular protocol layer from the layer above it") is inaccurate; data could from above or below.Sby 432T SupercededXf) none needed4CStanleyDWangEObserverG432HTechnical, Non-bindingI22J26K3.38 ,.4 AtChange the definition to read "Service Data Unit (SDU): The data unit exchanged between two adjacent protocol layers. On the downward direction, it is the data unit received from the previous higher layer. On the upward direction, it is the data unit sent to the next higher layer (see Figure 3)." Figure 3 is submitted as a separate contribution (see IEEE 802.16-01/11).tM,The original definition is not clear enough.S.same figure three as presented in comment 431.TAccepted-ClarifiedXe) done5CStanleyDWangEObserverG433HTechnical, Non-bindingI22J26K3.38LNeed to make certain that the usage of "PDU" and "SDU" is consistent throughout the document per definitions of "PDU" and "SDU" in section 3.MThroughout the document, sometimes "PDU" is used in places where "SDU" should have been used (or vice versa). For example, page 28, line 62 should read "resulting PDU" instead of "resulting SDU."TRejectedWGStanley Wang will provide future comments to elaborate on this comment.-/5Xf) none needed6CRonaldDMeyerEMemberG531H EditorialI22J29K3L5Insert the abbreviation "(SF)" after the word "Flow:"MProvide proper abbreviationQAcceptedRphilTAcceptedXe) done7CRonaldDMeyerEMemberG532H EditorialI22J33K3L7Insert the abbreviation (SFC)" after the word "Class:""MProvide proper abbreviationQAcceptedRphilTRejectedU1no accronym is used for this term in the documentXf) none needed8CRonaldDMeyerEMemberG533H EditorialI22J36K3LCWaltDRoehrEMemberG716H EditorialI23J7K3.52L Change "MAP" in heading to "Map"M/to best of my knowledge "map" is not an acronymO713Q SupercededRphilS713T SupercededXf) none needed?CLuisD ContrerasEOtherG434H EditorialI23J14K4LIAdd the following abbreviations: TOS (Type Of Service) VLAN (Virtual LAN)M%Text occurrence of such abbreviationsQAcceptedRphilSIaccept the change, but insert them within the list in alphabetical order.TAccepted-ModifiedXe) done@CRogerDMarksG818I23J14K4 02@ AAdd to abbreviation list: AK: Authorization Key BCC: Block Convolutional Code BE: Best Effort BTC: Block Turbo Code BWA: Broadband Wireless Access C/(I+N): Carrier to (Interference plus Noise) Ratio C/I: Carrier to Interference Ratio C/N: Carrier to Noise Ratio CA: Certification Authority CBC: Cipher Block Chaining CBR: Constant Bit Rate CRC: Cyclic Redundancy Check DHCP: Dynamic Host Configuration Protocol DIX: DEC-Intel-Xerox EDE: encrypt-decrypt-encrypt EIRP: Effective Isotropic RadiatBed Power FEC: Forward Error Correction IGMP: Internet Group Management Protocol ITU: International Telecommunication Union KEK: Key Encryption Key LAN: Local Area Network LFSR: Linear Feedback Shift Registers LMDS: Local Multipoint Distribution Service LSB: Least Significant Bit MAC-CPS: MAC Common Part Sublayer MAN: Metropolitan Area Network MMDS: Multichannel Multipoint Distribution Service MSB: Most Significant Bit PLME: PHY Layer Management Entity PRBS: Pseudo Random Binary Sequence RS13@ C?: Reed Solomon RSSI: Receive Signal Strength Indicator Rx: Reception SFID: Service Flow Identifier SHA: Secure Hash Algorithm TCP: Transmission Control Protocol TOS: Type Of Service Tx: Transmission UDP: User Datagram Protocol nrtPS: Non-Real-Time Polling Service ppm: parts per million rtPS: Real-Time Polling ServiceXe) doneACVicenteDQuilezEObserverG502H EditorialI23J14K4LAdd the following entries to the abbreviation list: CBC Cipher Block Chaining CNIR Carrier to Noise and Interference Ratio RSVP (Resource) ReSerVation ProtocolQAcceptedRphilSnaccept above, but change '(Resource)' to 'Resource', and insert the entries in the list in alphabetical order.TAccepted-ModifiedXe) doneBCKarlD StambaughEMemberG001H EditorialI23J14K4. 246B AAdd the following entries to the abbreviation list: AK Authentication Key BCC Block Convolutional Code BTC Block Turbo Code BWA Broadband Wireless Access CBR Constant Bit Rate CL Convergence Layer CRC Cyclic Redundancy Check DHCP Dynamic Host Configuration Protocol (RFC-2131) DL-MAP Downlink MAP DS Downstream EIRP Effective Isotropic Radiated Power FEC Forward Error Correction KEK Key Encryption Key LFSR Linear Feedback Shift Registers LSB Least Significant Bit MSB Most Significant Bit PLMBE PHY Layer Management Entity PPDU is this PHY Protocol Data Unit? PRBS Pseudo Random Binary Sequence RS Reed Solomon RSSI Receive Signal Strength Indicator SFID Service Flow Identifier TCP/IP Transmission Control Protocol (RFC 793) UDP User Datagram Protocol (RFC 768) UL-MAP Uplink MAP QAcceptedRphil35BAAdd the following entries to the abbreviation list while respecting the alphabetical ordering of the list: AK Authentication Key BCC Block Convolutional Code BTC Block Turbo Code BWA Broadband Wireless Access CBR Constant Bit Rate CRC Cyclic Redundancy Check DHCP Dynamic Host Configuration Protocol EIRP Effective Isotropic Radiated Power FEC Forward Error Correction KEK Key Encryption Key LFSR Linear Feedback Shift Registers LSB Least Significant Bit MSB Most Significant Bit PLME PHY LayerB Management Entity PRBS Pseudo Random Binary Sequence RS Reed Solomon RSSI Receive Signal Strength Indicator TCP Transmission Control Protocol UDP User Datagram Protocol TAccepted-ModifiedXe) doneCCManuelDPozaEOtherG751H EditorialI23J22K4L3Insertion of "CA Certification Authority". MPCA and its meaning is not included in the Abbreviations and acronyms section. TAcceptedXe) doneDCKenDStanwoodEMemberG080H EditorialI23J22K446DL2Add "CA certification authority" to acronym listM)completeness - used on page 77 and beyondQAcceptedRphilS751T SupercededXf) none neededECManuelDPozaEOtherG752H EditorialI23J34K4L6Insertion of "DBTC Downlink Burst Type Change"M@DBTC is not included in the Abbreviations and acronyms section. TRejectedU"This is a message, not an accronymXf) none neededFCKarlD StambaughEMemberG002H EditorialI23J59K4.L3Add '(RFC 2104)' to the end of the HMAC definition.M"add the reference to the standard.QRejectedRphilTRejectedU+all other references are removed from list.Xf) none neededGCRogerDMarksEMemberG081HTechnical, Non-bindingI24K4L;Add to the definition list: Rx: Reception Tx: TransmissionMMissing definitions.TAcceptedXe) doneY1to acronym list, not definition list, as intendedHCManuelDPozaEOtherG753H EditorialI24J7K4L8Insertion of "MCA Multicast Polling Assignment"M6MCA is not included in Abbreviations and acronyms listTRejected57HU"this is a message, not an accronymXf) none neededICRogerDMarksEMemberG082H EditorialI24J35K4LiChange "Physical Media Dependant" to "Physical Medium Dependent". Make this change globally in the draft.M(1) "Dependent" is spelled incorrectly. (2) Singular "medium" is more appropriate and is consistent with the term "medium access control".QAcceptedRphilTAcceptedXe) doneJCKarlD StambaughEMemberG003H EditorialI24J45K4.LHMove 'Rx/Tx' so that it is in the right-hand column before 'Transition' MRTG is the appreviation.QAcceptedRphilTAcceptedXf) none neededY/superceded (RTG deleted by another comment)KCKenDStanwoodEMemberG040H EditorialI24J45K4L4Move "Rx/Tx" to Right column with "Transmission Gap"M5The acronym "RTG" stands for "Rx/Tx Transmission Gap"O003Q SupercededRphilS003T SupercededXf) none neededLCRonaldDMeyerEMemberG535H EditorialI24J46K468wLLhChange line 46 from "RTG Rx/Tx Transmission Gap" to read "RTG Rx /Tx Transmission Gap"M Correct typoS003T SupercededXf) none neededMCManuelDPozaEOtherG754H EditorialI24J49K4L- Insertion of "SBC SS Basic Capability"M=SBC is not included in the Abbreviations and acronyms sectionTRejectedUmessage name, not accronymXf) none neededNCManuelDPozaEOtherG755H EditorialI24J56K4LEInsertion of "SSCS Service Specific Convergence Sublayer"M?SSCS is not included in the Abbreviations and acronyms section TAcceptedXe) doneOCManuelDPozaEOtherG756H EditorialI25J23K5 79O AInsertion of the following text: "The SSCS resides on top of the 802.16 MAC-CPS layer. The SSCS performs the following functions, utilizing the services of the MAC layer: a) Classificiation of the higher layer protocol PDU into the appropriate Connection b) Suppression of payload header information (optional) c) Delivery of the resulting SDU to the MAC-SAP associated with the Service Flow for transport to the peer MAC-SAP d) Receipt of the PDU from the peer M-SABP. e) Rebuilding of any suppressed payload header information (optional) The sending SSCS is responsible for delivering the SDU to the MAC SAP. The MAC is responsible for delivery of the SDU to peer MAC SAP in accordance with the QoS, fragmentation, concatenation and other transport functions associated with a particular connection's service flow characteristics. The receiving SSCS is responsible for accepting the SDU from the peer MAC-SAP and delivering it to a higher-layer entity.8:O C The packet convergence layer is used for transport for all packet-based protocols such as IP, PPP and Ethernet 802.3." If this change is done, the text placed between page 28, line 55 and page 29, line 12 should be deleted. MThe same general functions can be defined for all SSCS. In the current version of the standard, these functions are only enumerated at the beginning of the Packet Convergence Sublayer. " S435T SupercededXf) none neededPCStanleyDWangEObserverG435HTechnical, Non-bindingI25J23K5 9;P AOn page 25, line 23 insert the following paragraphs and fix all cross-references in the paragraphs: The Service Specific Convergence Sublayer (CS) resides on top of the MAC Commpn Part Sublayer (CPS) and utilizes the services provided by MAC-CPS via MAC-CPS SAP (see Figure 2). The CS performs the following functions: accepting higher-layer PDUs from the higher-layer, performing classification of higher-layer PDUs, processing (if required) the higher-layer PDUs based on the classificatB*ion, delivering CS PDUs to the appropriate MAC-CPS SAP, and receiving CS PDUs from the peer entity. Currently, two Convergence Sublayers are specified, ATM CS and Packet CS. Other Convergence Sublayers may be specified in the future. The ATM CS offers services to a higher-layer protocol using MFNeed a general description of "Service Specific Convergence Sublayer."S@accept the suggested text except for the last sentence fragment.TAccepted-ModifiedXe) doneQCRogerDMarksEMember:<QG083H EditorialI25J31K5.1L!Change "MAC-CPS SAP" to "MAC SAP"Mconsistency with Figure 2QAcceptedR Ken StanwoodTAcceptedXe) doneYchanged globallyRCBruceDCurrivanEMemberG717HTechnical, BindingI26J10K5.1.3LInsert more complete information on payload header suppression for ATM. Extended header should be included, as, for example, in DOCSIS. MHExisting definition of payload header suppression with ATM is ambiguous.TRejectedUkThe ATM convergence sublayer does not use extended headers. Please refer to sections 5.1.3.1 and 5.1.3.2.Xf) none neededSCTomDKolzeEObserverG718HTechnical, Non-bindingI26J10K5.1.3LThere is insufficient discussion/elucidation of the operation of payload header suppression for ATM; no flow charts or illustrative examples. These need to be created, as in the pacekt convergence section, for example. M5The payload header suppression with ATM is ambiguous.;=SAOn page 26, line 22, add the following to the end of the paragraph: "Whether or not payload header suppression is applied to an ATM connection is signaled in the DSA-REG message at the connection's creation. Similarly, the VPI (for VP-switched connections) or the VPI/VCI (for VC-switched connections) is also signaled in the classifier settings of the DSA-REQ message at connection creation."TAccepted-ModifiedXe) doneTCAntonisDKarvelasEOtherG375HTechnical, Non-bindingI26J27K5.1.3.1LThe PTI and CLP bits of the O/H field already exist in the MAC Header as CPT and PDE bits. You must give reasons for the existence of these bits in the O/H filed of Figure 3. AI believe that in the case of packing (multiple ATM cells after the MAC Header) we need these bits in order to keep the PTI and CLP information for each ATM cell. But if we don't support packing these bits are out of use since they exist in the MAC Header. ONo change here.<>TPsThere are other comments regarding the MAC Header that supercede this comment, requiring no change to this section.Q SupercededR Ken StanwoodSby comment 047T SupercededV mac headerXf) none neededUCAntonisDKarvelasEOtherG382HTechnical, Non-bindingI26J55K5.1.3.2LThe PTI and CLP bits of the O/H field already exist in the MAC Header as CPT and PDE bits. You must give reasons for the existence of these bits in the O/H filed of Figure 4. AI believe that in the case of packing (multiple ATM cells after the MAC Header) we need these bits in order to keep the PTI and CLP information for each ATM cell. But if we don't support packing these bits are out of use since they exist in the MAC Header. ONo change to this sectionPsThere are other comments regarding the MAC Header that supercede this comment, requiring no change to this section.Q SupercededR ken StanwoodSby comment 047T SupercededV mac headerXf) none neededVCWaltDRoehrEMemberG719H EditorialI28J19=?VK5.1.4.2L%Replace "Both ends" with "Either end"M)Do not need both ends to initiate a call.TAcceptedXe) doneWCPaulDThompsonEMemberG369H EditorialI28J42K5.1.4.2L Add "the" before "provisioning"MProper EnglishQAcceptedR Ken StanwoodTAcceptedXe) doneXCPaulDThompsonEMemberG376HTechnical, Non-bindingI28J44K5.1.4.2L/Change "should provisions" to "shall provision"M^Editorial correction plus the use of "should" seems too soft for an Interoperability Standard.QAcceptedR Ken StanwoodTAcceptedXe) doneYCPaulDThompsonEMemberG383H EditorialI28J53K5.2LBMake the title of this Section match an explicit block in Figure 2MUIf one goes to Figure 2, it is confusing which part is being discusses in Section 5.2PI propose to change the title of the Section to "Packet Service Specific Concergence Sublayer" and change also Figure 2 , so that under "Service Specific Convergence Sublayer" we include "ATM Cells/Packet (i.e. Ethernet, IP,..)"QAcceptedR V. QuilezT Superceded>@YXf) none neededZCKarlD StambaughEMemberG004H EditorialI28J55K5.2Lchange 'Layer (CL)' to 'Sublayer (CS)'. For consistancy, also change throughout the document the CL acronym to CS and the word layer to sublayer as appropriate. MiTo make this section consistent with the word sublayer in the title and also consistent with section 5.1.QAcceptedR V. QuilezTAcceptedXe) doneYYIs MAC a layer or sublayer? We are not consistent. I did not attempt to fix this problem.[CRogerDMarksEMemberG084H EditorialI28J62K5.2LqIn (c), change MAC-SAP to MAC SAP (and globally in draft) In (d), change M-SAP to MAC SAP (and globally in draft)Mconsistency with Figure 2QAcceptedR V. QuilezTAcceptedXe) done\CVicenteDQuilezEObserverG503H EditorialI28J62K5.2LChange SDU by CS PDUMClarity, consistencyQAcceptedR V. QuilezTAcceptedXe) done]CVicenteDQuilezEObserverG504H EditorialI28J64K5.2LChange PDU by CS PDUMClarityQAcceptedR V. QuilezTAcceptedXe) done^CVicenteDQuilez?A^EObserverG505H EditorialI29J3K5.2L1Change SDU by MAC SDU through 5.2 (lines 1 to 12)MClarity, consistencyQAcceptedR V. QuilezTAcceptedXe) done_CRogerDMarksEMemberG085H EditorialI29J10K5.2Lchange "Ethernet 802.3" to "IEEE 802.3 Ethernet" make change globally also change "Ethernet/IEEE 802.3" to "IEEE 802.3 Ethernet" globally also precede all "802" with "IEEE" (e.g., p. 16, lines 40, 43, 44, 46, 53) also expand "Std" as "Standard"M more formalPEthernet and IEEE 802.3 are not quite the same. Thus both must be cited (i.e. Ethernet/IEEE 802.3) Accept the two last suggestionsQAccepted-ModifiedR V. QuilezSchange "Ethernet 802.3" to "IEEE 802.3/Ethernet" make change globally also change "Ethernet/IEEE 802.3" to "IEEE 802.3/Ethernet" globally also precede all "802" with "IEEE" (e.g., p. 16, lines 40, 43, 44, 46, 53) also expand "Std" as "Standard"TAccepted-ModifiedXe) done`CManuelDPozaEOtherG536H EditorialI29J13K5.2.1@B`L5Insertion of a definition of the size of PHSI field. MBThere is no indication of the size of PHSI field in section 5.2.1.OgroupQAcceptedR V. QuilezS>on page 29, line 17, change "an Payload" to "an 8-bit Payload"TAccepted-ModifiedXe) doneaCVicenteDQuilezEObserverG506H EditorialI29J13K5.2.1L-Change SDU by MAC SDU through 5.2.1 and 5.2.2MClarity, consistencyQAcceptedR V. QuilezXe) donebCVicenteDQuilezEObserverG507H EditorialI29J15K5.2.1LChange Figure 17 by Figure 8QAccepted-DuplicateR V. QuilezXe) donecCStanleyDWangEObserverG436H EditorialI29J16K5.2.1LKChange "Figure 17" to "Figure 8" and fix the corresponding cross-reference.MTypoQAcceptedR V. QuilezXe) donedCKarlD StambaughEMemberG005H EditorialI29J17K5.2.1L"change 'an Payload' to 'a Payload'MgrammarQAcceptedR V. QuilezXf) none neededY supercededeCRogerDMarksEMemberG086H EditorialI29J18K5.2.1LQchange "MAC-SDU" to "MSDU" same change in line 29 same change on page 32, line 44ACeMconsistency within draft Note: "MAC SDU" and "MSDU" are both used in the draft. We should be consistent. I prefer "MAC SDU" everywhere, eliminating MSDU from acronym list.P>In line with Rogers preference, lets use MAC SDU (and alike)QAccepted-ModifiedR V. QuilezXe) doneYsuperceded by MAC SDU changefCWaltDRoehrEMemberG720H EditorialI29J18K5.2.1LChange "other" to "others"MgrammarXf) none neededYsee 006gCKarlD StambaughEMemberG006H EditorialI29J18K5.2.1L+change 'other map' to 'other protocols map'MgrammarQAcceptedR V. QuilezXe) donehCRogerDMarksEMemberG087HTechnical, Non-bindingI29J19K5.2.1LMchange "the frame" to "the PDU" make same change in Lines 22 and 38, Page 33M.No need to refer to frames in the MAC section.PLOK for page 29. I did not find anything related in Page 33, lines 22 and 38QAccepted-ModifiedR V. QuilezTAcceptedXe) doneiCKarlD StambaughEMemberG007H EditorialI29J19K5.2.1L'delete the word 'in' before 'the index'MgrammarBDiQAcceptedR V. QuilezXf) none neededYsee 437jCStanleyDWangEObserverG437H EditorialI29J19K5.2.1LChange the sensence starting "Otherwise . . ." to read "Otherwise, the value in the index identifies the rules for suppression."MTypoQAcceptedR V. QuilezXe) donekCStanleyDWangEObserverG438H EditorialI29J50K5.2.2LCChange "a SDU" to "an SDU" (same change for the next line as well).MTypo.P "a MAC SDU"QAccepted-ModifiedR V. QuilezXe) donelC FranciscoD EscrihuelaEOtherG439H EditorialI29J53K5.2.2LCDelete from "This is the process facilitates .." the words "is the"MImprove comprehensionof textQAcceptedR V. QuilezXe) donemCManuelDPozaEOtherG757H EditorialI29J57K5.2.2LChange "specifc" by "specific"MCorrection of a misprintXe) donenCKarlD StambaughEMemberG008H EditorialI29J59K5.2.2Ldelete 'with' after 'SAP'MgrammarQAcceptedR V. QuilezXe) doneoCKenDStanwoodEMemberG041H EditorialI29J59K5.2.2L"Change "SAP with for" to "SAP for"MtypoCEoQAccepted-DuplicateR V. QuilezXe) donepCYigalDLeibaEMemberG721H EditorialI30J47K 6.2.2.2.2LChange 'Reserved' to 'Gap'M)Consistency with the sentence at line 42.S)on page 60, line 37, do the change above.TAccepted-ModifiedXe) doneqCStanleyDWangEObserverG440H EditorialI31J12K5.2.2LChange "CL" in the figure to "CS" (same change for page 31, line 41). The same change shall be made throughout the entire document.MWTypo. Should be "CS" for Convergence Sublayer instead of "CL" for "Convergence Layer."QAccepted-DuplicateR V. QuilezXe) donerCKenDStanwoodEMemberG042HTechnical, Non-bindingI32J17K5.2.3LDelete "registration message,"MWThe classification table parameters do not appear in the registration message anymore. QAcceptedR V. QuilezTAcceptedXe) donesCStanleyDWangEObserverG441H EditorialI32J20K5.2.3LJChange "a SS" to "an SS" and make the same change throughout the document.M4This is a comment left out from IEEE 802.16/D1-2001.QAcceptedR V. QuilezDFsXe) donetCYigalDLeibaEMemberG722HTechnical, BindingI32J33K5.2.3L3Delete reference to higher layer policy mechanisms. A6The paragraph describes a case where a packet is assigned to a particular service class name or priority combination by an upper layer policy mechanism. No explanation is provided for how the information of this assignment is to be communicated across the air interface, and this might effect interoperability.6Sremove entire paragraphTAccepted-ModifiedU&it does not add value to the documentXe) doneuCYigalDLeibaEMemberG723HTechnical, BindingI32J50K5.2.4LvAdd a sentence that says that change of PHS rule is not allowed when that PHS is beign used by some active connection.MThe paragraph mentions a case where payload header suppression rule is dynamicaly changed. No information is provided on how this change is synchronized over the air interface, so that traffic that uses the PHS rule is not disrupted.TAccepted-ModifiedEGuWICarl Eklund will provide some text to clarify the document on this topic.Xg) pass off to other editorvCManuelDPozaEOtherG537H EditorialI32J59K5.2.4LChange "..verify or not verify the payload before suppressing it" by "..verify or not verify the payload header before suppressing it"M8As it is now, it seems that all the payload is verified.QAcceptedR V. QuilezXe) donewCManuelDPozaEOtherG758H EditorialI32J59K5.2.4L`Change "PHS has a PHSV option.." by "PHS has a Payload Header Suppression Valid (PHSV) option.."MGPHSV acronym is introduced in the standard without previous definition Xe) donexCManuelDPozaEOtherG759H EditorialI32J59K5.2.4LiChange "PHS also has a PHSM option.." by "PHS has also a Payload Header Suppression Mask (PHSM) option.."M?PHSM is introduced in the standard without previous definition Xe) doneyCManuelDPozaEOtherG760H EditorialI32J65K5.2.4FHyLmChange "..specify the PHSF and PHSS" by "..specify the PHSF and the Payload Header Suppression Size (PHSS)".MYPHSS is introduced in the standard without previous definition. Insert a missing "the".Xe) donezC FranciscoD EscrihuelaEOtherG442H EditorialI33J12K5.2.4.1LRChange "Upstream Suppression Field" by "Upstream Payload Header Suppression Field"MWPacket Header Suppression Field has a formal definition but Suppression Fields does notOgroupP"Comment refers to Page 33, line 22QAcceptedR V. QuilezSlignore above and change "Upstream Suppression Field" by "Uplink Payload Header Suppression Field" on line 22TAccepted-ModifiedXe) done{CManuelDPozaEOtherG639H EditorialI33J19K5.2.4.1L+Change "PHSS, and PHSV" by "PHSS and PHSV".MDeletion of extra comma. Xf) none neededYgrammar OK as is|CRogerDMarksG819I33J40K5.2.4.1L/Page 33 line 40: change "uplink" to "downlink" Xe) doneYcorrection added by Editor}CKenDStanwoodEMemberG443HTechnical, Non-bindingI33J47GI}K5.2.4.1L-"Stacking" of PHS methods should be allowed. M\If a protocol is carried over another protocol, PHS rules for each layer should be allowed. PIf "stacking" is accepted, we need an explicit, new text to describe such "stacking" operation. An alternative for this was described in Glenss Sater contribution IEEE 802.16c-00/18, (i.e. for VoiP). Lets discuss this point at Hilton HeadQAccepted-ModifiedR V. QuilezTRejectedXf) none needed~C FranciscoD EscrihuelaEOtherG444HTechnical, Non-bindingI34J18K5.2.4.1LChange figure 11. From the box verify? (line 18) the "no" exit should go to the box "suppress with PHSM. Set PHSI to index". The box in line 24 "Verify with PHSF" should include the text "Verify with PHSF together with PHSM". MMThe proposed changes are in accordance to the textual description in page 33.PBSee page 376, clause 11.4.18.2.7.5, regarding the PHSV descriptionQAcceptedR V. QuilezTAcceptedXe) doneCVicenteDQuilezEObserverG508H EditorialI34J31HJwK5.2.4.1LChange SAP by CS SAPMClarityQAcceptedR V. QuilezXe) doneYSSCS SAP€CVicenteDQuilezEObserverG509H EditorialI34J53K5.2.4.1LChange SAP by MAC SAPMClarityQAccepted-DuplicateR V. QuilezXe) done€CYigalDLeibaEMemberG724HTechnical, BindingI35J54K5.2.4.2LpChange sentence to read "PHS Rules are created with DSA, or DSC messages, or by the management entity (SNMP.)"""MEAllow setting of PHS rules through the standard management interface.TRejectedUAlthough the rules setting are not set by the management plane, the DSA and DSC messages that do set the rules may be stimulated via management plane signaling. The DSA and DSC messages ensure that the rules are set up both at the BS and the SS.Xf) none needed€CKenDStanwoodEMemberG445HTechnical, Non-bindingI36J39K5.2.5LCVLAN needs to be separated out better, as a separate specific part.IK~€MIt needs to be clear what portion of a CS is used by a service flow. For instance, secondary management connections need not implement the VLAN portion of the Ethernet CS, but there is no clear distinction.PpNothing is said so far concerning VLANs. I agree VLANs deserves an specific part (which is empty at the moment)QAccepted-ModifiedR V. QuilezTAccepted-ModifiedU2needs to be addressed, but requires some research.WSushil Mehta, sushil.mehta@lmco.com, Carl Eklund and possibly others will research the topic to provide a more detailed resolution.Xa) awaiting missing input€C Chao-ChunDWangEMemberG761HTechnical, BindingI36J41K5.2.5.1L%Delete sections 5.2.5.1. and 5.2.6.3.MThe PHS limitations that are placed in the specification are too strict and against sprit of header suppression. They cause around 30% overhead in VoIP application.SactionTAccepted-ModifiedJL€ACarl will fix these sections: In figure 14 change PHSI to be PHSI=0 Add "without Header Suppression" to caption Add new figure captioned "IEEE 802.3/Ethernet CS PDU format withHeader Suppression" content is a picture of a compressed Ethernet Cs PDU Looking like ------------------------------------------------------- | PHSI /= 0 | Header suppressed IEEE 802.3/Ethernet PDU| ------------------------------------------------------- where "/=" is the inequality symbol Add the following Btext to 5.2.6: "This section applies when IP [RFC-791],[RFC-2460] is carried over the FBWA network." Change "IP Packet" box of figure 15 to: ----------------------- | PHSI = 0 | IP packet| ----------------------- Add "without Header Suppression" to caption Change section intro to "The IEEE 802.3/Ethernet PDUs are mapped to MAC SDUs according to Figure 15 (when header suppression is not applied) or Figure 16 (with header suppression)" Add new figure entitled "IP CS PDU format IEEE 80KM€C2.3/Ethernet CS PDU format with Header Suppression" content is : ------------------------------------------ | PHSI /= 0 | Header suppressed IP packet| ------------------------------------------ Change section intro to "The format of the IP CS PDU must be as shown in Figure 17 (when header suppression is not applied) or Figure 18 (with header suppression)" Delete section 5.2.6.3^Xe) done€CVicenteDQuilezEObserverG510H EditorialI36J48K5.2.5.1LDelete "Packet PDU1"MClarityQAcceptedR V. QuilezXe) done€C FranciscoD EscrihuelaEOtherG446HTechnical, Non-bindingI36J55K5.2.5.1LChange figure 14 to include another field between "user data" and "CRC". The new field is called "padding field" and its size varies between 0 and 46 bits.MThe changed figure aggrees the formal definition of ethernet packet which requires a minimum length of 64 bits even when the user data field has 0 bits of length.QAcceptedR V. QuilezTAcceptedXe) done€CVicenteDQuilezLNi€EObserverG511H EditorialI37J14K5.2.5.3LDelete or fill in this sectionM Consistency OgroupPBIt would be better to fill in this section (rather than delete it)QAcceptedR V. QuilezTRejectedXf) none needed€C FranciscoD EscrihuelaEOtherG447H EditorialI37J53K5.2.6.2LNChange the text to "Payload header suppression must be disabled for the IP CL"MImprove comprehensionOgroupQAcceptedR V. QuilezT SupercededXf) none needed€CKenDStanwoodEMemberG043HTechnical, Non-bindingI37J53K5.2.6.3L^Need to mention that IP PHS will instead be standards based and mention the specific standard.MSCurrent statement fails to capture the agreement that was made at the last meeting.QAcceptedR V. QuilezS)The necessary text will be provided asap.TAccepted-ClarifiedWKCarl Eklund will provide necessary text for the resolution of this comment.Xf) none neededMP€YCompleted by this line of Comment 761: Add the following text to 5.2.6: "This section applies when IP [RFC-791],[RFC-2460] is carried over the FBWA network." € CVicenteDQuilezEObserverG512H EditorialI37J57K5.2.6.4LDelete or fill in this sectionM Consistency OgroupPBetter fill in than delete it.QAcceptedR V. QuilezTRejectedXf) none needed€ CKeithDDoucetEMemberG762HTechnical, BindingI38J1K6LUse DOCSIS 1.1 QoS.MDCompatibility with other products, mainly VoIP and management tools.TRejectedUQcurrent QoS originated from DOCSIS. It was then enhanced to meet 802.16's needs.Xf) none needed€ CKeithDDoucetEMemberG763HTechnical, BindingI38J1K6L@Timing mechanisms should be defined and adapted for an OFDM PHY. L?P{BUUX  $,.YesNo/,  , : AM PM HelveticaGenevaTimes New RomanMonaco NQ]€ AzOFDM PHY is required by customers to support reliable and efficient operation in NLOS environment. The proposed timing scheme is designed for single carrier where the data is spread only on the time domain. For OFDM it is required to define exactly the time reference of the time related messages. It is required to define an efficient mechanism for the initial ranging on OFDM.zTRejectedUwIf an OFDM PHY is added in the future, the timing mechanism will be defined in the particular PHY section at that time.Xf) none needed€ CChetDShiraliEMemberG764HTechnical, BindingI38J1K6LUse DOCSIS 1.1 QoS.MDCompatibility with other products, mainly VoIP and management tools.S762T SupercededXf) none needed€ CChetDShiraliEMemberG765HTechnical, BindingI38J1K6L@Timing mechanisms should be defined and adapted for an OFDM PHY. PR€ A~OFDM PHY is required by customers to support reliable and efficient operation in the NLOS environment. The proposed timing scheme is designed for single carrier where the data is spread only on the time domain. For OFDM it is required to define exactly the time reference of the time related messages. It is required to define an efficient mechanism for the initial ranging on OFDM.~S763T SupercededXf) none needed€CKenDStanwoodEMemberG044H EditorialI38J13K6L*change "that divides" to "that may divide"M>The statement is true for TDD systems but not for FDD systems.Xe) done€CVicenteDQuilezEObserverG513H EditorialI38J30K6LChange mechanism by mechanismsMgrammarXe) done€CPaulDThompsonEMemberG390H EditorialI38J30K6L"Change "mechanism" to "mechanisms"MProper English.Xe) done€CRogerDMarksEMemberG088HTechnical, Non-bindingI38J44K6 QS€ AChange: "These connections are provisioned when an SS is installed in the system, and set up over the air at SS registration to provide a reference against which to request bandwidth." to "Service flows may be provisioned when an SS is installed in the system. Shortly after SS registration, connections are associated with these service flows (one connection per service flow) to provide a reference against which to request bandwidth."M4New language suggested by Ken Stanwood upon request.QAcceptedRCarlTAcceptedXe) done€CRogerDMarksEMemberG089H EditorialI38J60K6LChange "Once connections are established they must be maintained." to "Connections, once established, may require active maintainance." MPDraft sentence could be interpreted to mean that connections _must_ remain open.Xe) done€CRogerDMarksEMemberG090HTechnical, Non-bindingI39J2K6Ldelete "across frames"M$no need to discuss frames in the MACQAcceptedRCarlTAcceptedXe) done€CStanleyRT€DWangEObserverG448H EditorialI39J64K6.1.1LfChange "convergence layer" to "convergence sublayer" and make the same change throughout the document.MaPer Figure 2 on page 17, "convergence" is a "sublayer" of MAC layer instead of a layer by itself.QAcceptedR Ken StanwoodXe) done€CVicenteDQuilezEObserverG514H EditorialI40J13K6.1.1LVIn Figure 16, change Convergence Layer by Convergence Sublayer and MAC by MAC SublayerMClarityQAcceptedR Ken StanwoodXe) done€CYigalDLeibaEMemberG725H EditorialI40J59K 6.1.1.1.2LRemove 'SDU length'MAppears again in line 64.QAcceptedR Ken StanwoodXe) done€CVladimirDYanoverEMemberG515HTechnical, Non-bindingI40J65K 6.1.1.1.2LESee 802.16.1c-01/16, "Partial Payload Addressing Function" section MNTo provide less MAC overhead to the small size SDUs addressed to different SSsTRejectedU"as per discussion with TG3 and TG4Xf) none needed€CVicenteDQuilezEObserverG516H EditorialI41J12K 6.1.1.1.2SU€LdDelete the last sentence starting with "other values.." or provide an annex (presently not existing)M ConsistencyQAcceptedR Ken StanwoodXj) awaiting resolution€CWaltDRoehrEMemberG726H EditorialI41J26K 6.1.1.1.2L,Insert paragraph break after "Service Flow."MLooks like para break got lost somehow (no space after period). All other parameters get their own para; no reason to slight encryption.QAcceptedR Ken StanwoodXe) done€CVladimirDYanoverEMemberG517HTechnical, Non-bindingI41J30K 6.1.1.1.2LAdd the following text: "Packing on/off indicator's "on" value means that the connection will carry only constant length SDUs which will be packed into MAC messages as partial payloads. " TV€ AThe Packing on/off indicator meaning is not specified in the original text. This comment contains also some technical issue: it states that invocation of the packing fucntion for variable length SDUs is not a property of connection (but a tentative decision to be made on per-MPDU basis). Note also at 6.2.3.3 "Packing makes use of the connection attribute indicating whether the connection carries fixed or variable length packets"SInstead of the proposed text above, insert the following text. "Packing on/off indicator's "on" value means that packing is allowed for the connection."TAccepted-ModifiedXe) done€CWaltDRoehrEMemberG727HTechnical, Non-bindingI42J25K 6.1.1.2.2 A"The encryption and CRC flags are not delivered with the.indication primitive since they will have already been acted on by lower layers, to decrypt the data or to check a CRC, before the MSDU is passed up to the convergence sublayer." to reflect where this "acted on" is specified.UWM€MI was not able to find any location in the remaineder of the spec thathandled the security and CRC parameters and negotiation of agreed values.Sreplace 'MSDU' in the above text with 'MAC SDU'. Add a CRC Mechanism section on page 106, line 43. A flowchart to clarify the use of CRC will also be added to page 102.TAccepted-ModifiedU ACarl Eklund will provide text for the new section. He will also provide the flowchart. Carl's changes: On page 49 l. 11-13 Change sentences 'Each PDU... convergence sublayer.' to read 'Each PDU shall begin with a fixed length Generic MAC Header. The header may be followed by the Payload of the MAC PDU. If present the Payload shall consist of zero or more subheaders, and zero or more MAC SDUs and/or fragments therof.' Move 6.2.2.1 Conventions under 6.2.3 (to be 6.2.3.1) Move paragraph VX€Bon page 49 l.18 to section 6.2.3.1 Conventions Move section 6.2.2.1.1 (Encryption of ...) to be after 6.2.3.3.2.1 Promote the section from H5 to H4 Delete section 6.2.3.2.1 Encryption in the presence of fragmentation Add section 'CRC calculation' between section 'Encryption...' and 'Concatenation..' reading 'A service flow may require that it be carried on a connection in MAC PDUs with CRCs added. In this case a CRC as defined in < reference to IS0/IEC 8802-3> shaCll be included in each MAC PDU with HT=0 i.e. request PDUs will be unprotected. The CRC shall cover the Generic MAC Header and the Payload of the MAC PDU. The CRC shall be calculated after encryption i.e. the CRC protects the Generic Header and the ciphered Payload.' Replace p49 lines 34 and 35 with 'A MAC PDU may contain a CRC as desrcibed in . Change title 6.2.3. To 'Construction and transmission of MAC PDUs' Add text under 6.2.3 The construction oWY€D&f a MAC PDU is illustrated in figure. Xe) doneAQuestions addressed by Carl, who revised the edit. Questions were: In moving paragraph on page 49 l.18 to later, do we cause confusion by postponing the explanatory note ("In the figures, the bits are numbered starting from the Most-Significant-Bit with the Most-Significant- Bit being number 0.") I didn't know where to add section 'CRC calculation'. Didn't understand "between section 'Encryption...' and 'Concatenation.'" I put it just before Encryption of MAC layer PDUs. Impossible to aBdd reference to 11.4.12.24 as requested since that section was deleted by Comment 347. Therefore, referred to 11.4.12.17 instead.o€CVicenteDQuilezEObserverF Comments onlyG808H EditorialI42J43K 6.1.1.2.4L7Replace "request originated" by "request is originated"MGrammarXe) done€CVicenteDQuilezEObserverF Comments onlyG809H EditorialI43J30K 6.1.1.3.4XZ%€LReplace "the SS MAC layer" by "the MAC sublayer" Replace "MAC layer" by "MAC sublayer" in page 45, line 25 Replace "MAC layer" by "MAC entity" in page 46, line 9M ConsistencyXe) done€CVicenteDQuilezEObserverF Comments onlyG810H EditorialI46J55K 6.1.1.10.2LoReplace "convergence layer" by "convergence sublayer" Do the same in page 47, line 26 Again in page 47, line 42M ConsistencyXf) none neededY duplicate€CVicenteDQuilezEObserverF Comments onlyG811H EditorialI47J20K 6.1.1.10.2L#Replace "encryption" by "encrypted"MGrammarXe) done€ C Juan CarlosDZunigaEMemberG654H EditorialI47J57K 6.1.1.11.2Ldelete "discard-eligible flag,"M[If comment regarding document "IEEE 802.16.1-01/22" gets accepted, this is no longer neededQAcceptedR Ken StanwoodXj) awaiting resolutionY[€ ZWhat about in MAC_DATA.request? Also, this sentence there: "The discard-eligible flag specifies whether the MAC SDU should be preferentially discarded in the event of link congestion and consequent buffer overflow."€!CYigalDLeibaEMemberG728H EditorialI47J60K 6.1.1.11.2L$Remove 'Encryption flag' parameter. MWThe 'Encryption flag' parameter, is associated with the CID and not with specific SDUs.QAcceptedR Ken StanwoodXf) none neededY duplicate€"CRogerDMarksEMemberG091HTechnical, Non-bindingI48J6K 6.1.1.11.2LRemove reference to frames in "The reception status parameter indicates transmission success or failure for those frames received via the MAC_DATA.indication."M'MAC should not be talking about frames.OChange "frames" to "PDUs".PWThe use of frames here was not in the PHY sense, but in the DOCSIS sense, meaning PDUs.QAccepted-ModifiedR Ken StanwoodS\use proposed resolution and on page 48, line 7, delete the sentence starting with "ERROR..."TAccepted-ClarifiedZ\€"Xe) done€#CKenDStanwoodEMemberG045HTechnical, Non-bindingI48J22K6.1LAAdd the contents of 802161c-01_09 as a new section numbered 6.1.2MVClarification of the relationship between MAC Service primitives and the DSx messages.PfThis was agreed to verbally at the editorial session in December, but never made it into the document.QAcceptedR Ken StanwoodTAcceptedXe) doneA Captions: MAC SAP Event and MAC Event Sequence for Convergence Sublayer Stimulated Connection Creation, MAC SAP Event and MAC Event Sequence for Convergence Sublayer Stimulated Connection Change, MAC SAP Event and MAC Event Sequence for Convergence Sublayer Stimulated Connection Deletion [ Figures should be in FrameMaker.€$CAntonisDKarvelasEOtherG395HTechnical, Non-bindingI48J41K6.2.1LEThe Table 2 doesn't contain the information that the text refers to. MThe standard must have a Table that specifies which MAC Management Messages are transferred on which of the Basic and Primary connections.[]€$OAdd crossref to Table 3QAccepted-ClarifiedRCarlSuse proposed resolutionTAccepted-ClarifiedXe) done€%CVicenteDQuilezEObserverF Comments onlyG812H EditorialI48J41K6.2.1LReplace Table 2 by Table 3Xf) none needed€&CAntonisDKarvelasEOtherG401HTechnical, Non-bindingI48J44K6.2.1LIn the case which the system supports only ATM services, why to have to implement the Ethernet Convergence Sublayer simultanesly with the ATM Convergence Sublayer ? MI believe that we can use the ATM layer as a transport layer for the SNMP,DCHP, TFTP messages in order not to have to implement the Ethernet Convergence Sublayer.ONo specific change proposedQRejectedRCarlTRejectedU-this would introduce interoperability issues.Xf) none needed€'CRogerDMarksEMemberG092H EditorialI48J45K6.2.1LHchange "Ethernet Convergence Sublayer" to "Packet Convergence Sublayer" M0There is no "Ethernet Convergence Sublayer" now.\^€'AfReplace sentence "The secondary ..." begining on line 44 with "These messages are carried in Ethernet packets as specified in . The packets must be classified and assigned to be carried over the Secondary Management Connection based on the Ethernet source address in the Uplink and Ethernet destination address in the Downlink."fTAccepted-ModifiedXe) done€(CKenDStanwoodEMemberG046HTechnical, Non-bindingI48J45K6.2.1LgTo the end of the last sentence of paragraph add "using the SS's 48-bit MAC address as the classifier"MEWe agreed upon this as the classifier, but it is not stated anywhere.Q SupercededRCarlSby comment 092T SupercededXf) none needed€)CVicenteDQuilezEObserverF Comments onlyG813H EditorialI49J10K6.2.2LXReplace "Each PDU is preceded by" by "Each PDU starts with" The same in page 49, line 37MMAC header is part of MAC PDUXf) none neededY duplicate€*CKarlD StambaughEMemberG009HTechnical, Non-bindingI49J19]_F€*K6.2.2 A7Change 'Most-Significant-Bit being number 0' to 'Least-Significant-Bit being number 0'. All of the following message format figures that have the bits labeled above the message fields also have to be changed to reflect this (bit 15 on the left and bit 0 of the right). These include Figure 18-20, 23-28, 30-58.7 AThis section defines the MSB to bit 0 and the above listed figures all label the left side of the fields as being bit 0. However, elsewhere in the document are many other figures that imply that bit 0 is on the right side of fields and is labeled as bit 0. One example is Figure 28 (page 64). The bit array index shows [31:16] and [15:0], which by the numerical order seems to place bit 31 on the left. There are many other field definitions that are the same as this. This is EXTREMELY confusi^`€* BCng. Most people are used to bit #0 to be the LSB. This is actually stated on page 349, line 34 for another field definition. We need to be consistant in this ordering throughout the document. There are many figures to change, but many of them would have to change anyway if we decide that bit 0 must be the MSB everywhere.1PWe need a consensus here.QAccepted-ClarifiedR V. QuilezS_Delete sentence on line 19 beginning with 'In the figures...' Replace the figures with tables.TAccepted-ModifiedW$Sergio Licardie will provide tables.Xe) doneZs there an ordering problem with the two remaining message figures (Generic MAC Header Format and Bandwidth Request Header Format)?€+CLuisD ContrerasEOtherG449H EditorialI49J34K6.2.2L.Insertion of a comma between 'CRC' and 'every'M Text clarityQAcceptedR V. QuilezXf) none neededY superceded€,CKeithDDoucetEMemberG766HTechnical, BindingI49J37K6.2.2_a}€,LChange the generic header format to DOCSIS 1.1 header. Extended header is required (as defined in DOCSIS). Change HCS to 16 bits. AAs per IEEE 802.16 decisions, this draft is used for both MMDS and LMDS applications. Most of the MMDS target market and some of the LMDS target markets are residential/SOHO where, low cost is an important feature and the applications are IP centric. Low cost will be achieved by using existing technology as DOCSIS and the header should be based on IP environment, not on connection oriented environment that is not typical to residential/SOHO appplications. Time to market will be achieved by`b€, B making use of a matured standard with existing products as DOCSIS (including DOCSIS based wireless products). It is important to support applications such as VoIP, QoS, link layer encryption. Using IP centric protocol is critical for this and using DOCSIS based protocol will enable the use of existing products. Without an extended header it is almost impossible to make future improvements to the standard with backward compatibility. CRC of 8 bits is not enough, especially for non line ofC sight applications.S047T SupercededXf) none needed€-CChetDShiraliEMemberG767HTechnical, BindingI49J37K6.2.2LChange the generic header format to DOCSIS 1.1 header. Extended header is required (as defined in DOCSIS). Change HCS to 16 bits. ac€- AAs per IEEE 802.16 decisions, this draft is used for both MMDS and LMDS applications. Most of the MMDS target market and some of the LMDS target markets are residential/SOHO, where low cost is an important feature and the applications are IP centric. Low cost will be achieved by using existing technology as DOCSIS and the header should be based on IP environment, not on connection oriented environment that is not typical to residential/SOHO appplications. Time to market will be achieved byB making use of a matured standard with existing products as DOCSIS (including DOCSIS based wireless products). It is important to support applications such as VoIP, QoS, link layer encryption. Using IP centric protocol is critical for this and using DOCSIS based protocol will enable the use of existing products. Without an extended header it is almost impossible to make future improvements to the standard with backward compatibility. CRC of 8 bits is not enough, especially for non line ofbd€- C sight applications. S047T SupercededXf) none needed€.CKenDStanwoodEMemberG047HTechnical, Non-bindingI49J37K6.2.2 A1. On page 49, line 37 - change "three" to "two", change "two are" to "is a", change "precede" to "precedes". 2. On page 49, lines 45-51 - delete the two paragraphs. 3. On page 49, line 53 - add "The generic header is shown in Figure xxx" 4. On page 50, replace Figure 18 with Figure A from 802616c-01_10. 5. On page 50, delete Figure 19. 6. On page 51, line 1 - move the first paragraph to page 53, line 26, and add the sentence "The Grant Management sub-header is shown in Figure xxx. ce€. BUse the Grant Management portion of the original Figure 18 as a new following this paragraph, titled "Grant Management Sub-Header Format" 7. On page 51, line 6 - delete the first sentence of the paragraph. 8. On page 51, line 13 - replace Figure 20 with Figure B from 802616c-01_10. 9. On page 51, line 34 - replace "PDU" with "Bandwidth Request" 10. On page 51, line 45 - replace "EC, EKS, and reserved fields" with "HT, EC, and EKS fields" 11. On page 52, line 15 - in length column, replaCce "15" with "16" 12. On page 52, line 46 - in description column, change "modulo 16" to "modulo 8" 13. On page 52, line 47 - in length column, change "4" to "3" 14. On page 52, line 51 - delete the Grant Management row 15. On page 53, line 21 - delete the PSP row 16. On page 53, line 21 - add a row. The contents of the name column should be "Type". The contents of the length column should be "8". The contents of the Description column should be: 00000b = normal payload, no sub-headersdf€. D or special interpretation 00001b = Grant Management sub-header present (UL only, code may be reused for some DL only purpose) 00010b = packing sub-header present 00011b = both grant management and packing sub-headers present (UL only, code may be reused for some DL only purpose) 00100b = Fragmentation sub-header present (not needed simultaneously with packing sub-header) 00101b = Fragmentation and grant management sub-headers present (UL only, code may be reused for some DL only purpose) E 17. On page 53, line 25, before the text moved in step (6) above, add "The fragmentation sub-header is shown in Figure xxx". Add Figure C from 802161c-01_10. Take the (modified) FC and FSN rows from table 1 and make a new table titled "Fragmentation Control Sub-header Fields" 18. On page 53, line 27 change the title of table 2 to "Grant Management Sub-header Fields" 19. On page 53, line 51 add line "If both the Fragmentation and Grant Management sub-headers are present, the Fragmentateg€. Fion sub-header shall come first. All per PDU sub-headers (e.g., Fragmentation, Grant Management) shall always come before the first per SDU sub-header (e.g., Packing).  OMPNew MAC header resulting from discussions with TG3 and TG4 after ottawa session.QAcceptedR V. QuilezAadd a leading '0' to the type field definitions. The type for bandwidth requests are '000000' for incremental and '000001' for aggregate. Also, replace item 16 with the contents of 802161c-01_10r1.doc Figures are also superceded by those in 802161c-01_10r1.TAccepted-ModifiedUUas per concensus between TG1 MAC, TG3 and TG4 the morning of Tuesday, March 13, 2001.Xe) donefh€.AMade the MAC Header Type Length 6 bits (instructions said 8, but this seems to be wrong) Set EC=1 in Bandwidth Request Header Format figure, to match text (though 10r1 said EC=0) Used "LEN" instead of "Length" and "Type" instead of "Payload Type" in figure, since these are the field names At line 41, page 51, added item (e): "The types for bandwidth requests are '000000' for incremental and '000001' for aggregate." Made these changes, as given in 10r1: On page 52,line 12,delete the ARB field. On page 53,line 18,delete the PDE field Additional changes per Stanley Wang: Here is what I proposed to do (all line and page numbers refer to 802.16/D3r0): 1. Line 42, page 50, the EC field shall be forced to be 0. 2. Line 2, page 51, change the line to read "b) The EC field shall be set to 0...." 3. Line 10, page 51, change the beginning of the line to read "HT and EC fields." 4. Line 39, page 51, change to "0=Payload is not encrypted" 5. Line 40, page 51, change to "1=Payload gi€.Cais encrypted" 6. Line 44, page 51, change to read "... the Encryption Control field is set to 1." and delete the last sentence. 7. Line 37, page 102, change to read "A value of 1 indicates the payload is encrypted and ..." 8. Line 38, page 102, change to read "A value of 0 indicates the payload is not encrypted." and delete the reset of the sentence. =@A* 33  *€/CKenDStanwoodEMemberG048H EditorialI49J37K6.2.2LChange "Message" to "PDU"MclarityQAcceptedR V. QuilezXe) doneY"and changed "precedes" to "begins"€0CHuanchunDYeEMemberG655HTechnical, BindingI50J38K6.2.2LdPlease referred to contribution IEEE 802.16.1c-01/21 for the proposed changes on MAC header formats.S047T SupercededXf) none needed€1CLuisD ContrerasEOtherG450H EditorialI51J2K6.2.2LSubstitution of '..based upon the type of connection..' by '..based upon the type of upstream scheduling service for the connection..'M Text accuracyhlb€1OgroupQAcceptedR V. QuilezSignore above and Substitute '..based upon the type of connection..' by '..based upon the type of uplink scheduling service for the connection..'TAccepted-ModifiedXe) done€2CSubirDVarmaEMemberG656HTechnical, Non-bindingI51J12K6.2.2LWReplace Figure 20 in IEEE 802.16/D2-2001 by Figure 1 in TG1 Contribution 802161c-01 18. ACurrently the 802.16 MAC protocol allows for two types of MAC headers, which are distinguished by the Header Type (HT) field. When HT = 1, then the MAC Header is used for Bandwidth Request packets, which are special packets containing the header only, with no payload. Currently the protocol does not define any other packet which shares this characteristic. The addition of ARQ functionality into the MAC protocol, leads to the situation in which there are additional MAC packets required in upEXEDITOR'S ACTION ITEMS RESOLUTION PROPOSED DB G JU_isBDF@ @LM E BQO L!L"A#A$L%!T&&G'(S(,M).M*0L+2L,4 A-5X.:L/YX?^E@`LAeMBiQCoQDsXEuWFyLG}KHKI€MJ€AKCL€EM€YN€ AP€ AQ€ AR€DS€LT€ AU€MVBWDX€LY€ ZZ€"X[€$O\€'A]€*K^ B_€,L` Ba€- AbCc€. BdDeFfAgCh€1Oi€2 BlDm€5Zn€8n€8< L@O!@im€2 Bplink direction, which share similar properties with the Bandwidth Request packets, i.e., they are defined using the header alone with no payload. A specific instance of such a packet is the Uplink ACK packet (which acks downstream data packets). It is necessary to have a separate Uplink ACK packet (in addition to piggybacked uplink ACKs), for the following reasons: For the case in which there is no uplink data, it is not possible to piggyback uplink ACKs When the uplink ACK is sent piggybCacked, then it is forced to use the same burst profile as uplink data, which may not be the most robust one. In order to make sure that the ACK always makes it to the BS, even in a degraded channel (in order to have any utility as a feedback mechanism), it is preferable to use a more robust burst profile for uplink ACKs as compared to uplink data. This makes necassary that the uplink ACK be sent as a separate burst. It is possible to slightly modify the Bandwidth Request packet, in order tln€2 Do define the uplink ACK packet, as shown in Figure 1. There is a 4 bit Type field that can be used to identify other kind of control packets. Thus Bandwidth Requests and Uplink Acks can be assigned different Types.S047T SupercededXf) none needed€3CRogerDMarksEMemberG093H EditorialI51J20K3LReplace "Security associations also exist be keying material and CIDs." with "Security associations also exist between keying material and CIDs."MtypoXe) done€4CVicenteDQuilezEObserverF Comments onlyG814H EditorialI51J36K6.2.2LReplace "7 bytes" by "6 bytes"M6Consistency with new header format, as proposed by KenXe) doneZ#Why didn't Ken change this himself?€5CVicenteDQuilezEObserverF Comments onlyG815H EditorialI52J6K6.2.2LIntroduce text to reference Table 1 (the older text has been proposed to be deleted) Delete Rows CSI and CPT (these fileds are not existing in the new headers proposed)M ConsistencyXj) awaiting resolutionmo€5Z)Delete the CSI and CPT rows as requested?€6CRogerDMarksEMemberG094H EditorialI52J28K6.2.2LChange "MAC CPS" to "MAC-CPS"Mconsistency with rest of draftPGTo keep consistency with agreed rule (i.e. MAC XXX rather than MAC-XXX)QRejectedR V. QuilezXe) done€7CKenDStanwoodEMemberG049HTechnical, Non-bindingI52J46K6.2.2 AIn description column, change "current fragment" to "current SDU fragment" Delete the second sentence of the description (begins "The initial"). To the end of the third sentence, add "including unfragmented SDUs" Delete the last line of the description (begins "When fragmentation") MContinuing to update the fragmentation sequence number even across unfragmented SDUs makes the protocol much more robust against problems caused by losing SDUs or SDU fragments.QAcceptedR V. QuilezTAcceptedXe) done€8CLuisD ContrerasEOtherG451H EditorialI53J17K6.2.2nq€8LrSuggestion: to change acronym PDE currently standing for 'Packet Discard Eligibility' to 'PDU Discard Eligibility' AIAccuracy about what the acronym is referring to. The PDE field marks a certain PDU for discard eligibility. A packet could consists of several PDUs. If the PDE field marks a packet discard eligibility, a procedure has to be defined regarding of e.g. marking all the MPDUs forming the packet, or marking just the first MPDU, etc. IOgroupQAcceptedR V. QuilezT SupercededXf) none needed€9CJacobD JorgensenEMemberG657HTechnical, BindingI53J17K6.2.2.2L,Change as per submission IEEE 802.16.1-01/22M See aboveS047T SupercededXf) none needed€:CKenDStanwoodEMemberG050HTechnical, Non-bindingI53J40K6.2.2LChange the length of PBR field to 16. In the text (hopefully moved from page 51, line 1) change the description of the field to be 2 bytes. Change the Grant management Figure to show 2 bytes.j€8Lo€:Mq€=Mr€@ As€A AtCuEvBwDx€B Ay€C Az€EQ{€G A| B}€I A~€KR€O AC€PA€RL€TP€VM€XL€[L€^ ACX€aQ€d A€e A€fP€iY€l A AACEB€oP€r ABDBDFHJLNPRTVXZ\^`€vX€|H€~L€M€R€H€H€E€K€K€I€L€E€L€M€L€M€L€T€R€ A€ A€L€M€H€M€M€J B A€D€ BACE€M€L€S€L€P€C€M€M€L€L€H€M€ B€Lor€:MjIf the piggyback request is an optional sub-header, it should be made large enough to properly do its job.QAcceptedR V. QuilezTAcceptedXe) doneYChanged Grant Management (GM) field to two bytes in text and in figure. In the case of UGS and UGS with activity detection, I marked all the extra bits as "reserved".€;CKenDStanwoodEMemberG051H EditorialI54J1K 6.2.2.1.1LChange Figure 21 to show an optional CRC at the end that is NOT included in the encryption. Also flip the brace so it delineates the paylod that is encrypted rather than the text.MclarityQAcceptedR V. QuilezXe) doneZIs it right now?€Change "MAC header" to "MAC header, including any sub-headers"MclarityQAcceptedR V. QuilezTRejectedXf) none needed€=CKeithDDoucetEMemberG768HTechnical, BindingI54J44K6.2.2.2L5Use IEEE 802.2 format to pack MAC management messagesqs€=M1. Required for IP centric protocol (see comment 1). 2. Following other mature standards and products - other IEEE 802 standards and DOCSISTRejectedUcontradicts MAC paradigmXf) none needed€>CChetDShiraliEMemberG769HTechnical, BindingI54J44K6.2.2.2L5Use IEEE 802.2 format to pack MAC management messagesM1. Required for IP centric protocol (see comment 1). 2. Following other mature standards and products - other IEEE 802 standards and DOCSIS. 3. Simplify the implementation by using the same format for data and MAC management messagesS768T SupercededXf) none needed€?CStanleyDWangEObserverG538HTechnical, Non-bindingI55J4K6.2.2.2LQChange the wording for the first field in the fugure to read "Generic MAC Header"MtIf the new MAC header format is accepted, there is no longer any difference between uplink and downlink MAC headers.QAcceptedR V. QuilezTAcceptedXe) done€@CSergioDLicardieEMemberG658HTechnical, Non-bindingI56J6K6.2.2.2 rt€@ ATable 3 MAC Management Messages includes 2 messages DCC-REQ and DCC-RSP that are not described in detail in the following sections. We need to add their detailed descriptions in sections 6.2.2.2.19 and 6.2.2.2.20 and renumber the following sections starting withs Multicast Polling Assignment Request with 6.2.2.2.21 and on or delete the messages from the table if they do not apply any more.MAOmission of detailed description for two MAC Management Messages.SJdo the reordering as specified but leave the description for future study.TAccepted-ModifiedXe) done€ACStanleyDWangEObserverG539HTechnical, Non-bindingI56J22K6.2.2.2 su€A AAdd a new row (a new message type) on page 56, line 22: "% 28 % CLK-CMP % SS network clock comparison % Broadcast % Change the row currently on page 56, line 22 to read "% 29-255 % % Reserved for future use % %" Add a new row (a new global value) to Table 67 on page 309, line 29: "% BS % CLK-CMP Interval % Time between transmission of CLK-CMP messages % 50 % 50 % 50 %" Add a new section, section 6.2.2.2.28 on page 102, line 35 as the follows: 6.2.2.2.2B8 Clock Comparison (CLK-CMP) Message In network systems with service flows carrying information that requires the SSs to reconstruct their network clock signals (e.g., DS1 and DS3), CLK-CMP messages shall be periodically broadcasted by the BS. If provisioned to do so, the BS shall generate one CLK-CMP message at every periodic interval defined in Table 67 according to the format shown in Figure XX. (Note for the editor: please insert Figure 1 from document IEEE 802.16.1c-01/15 here and tv€A Creplace the correct Figure number in the previous line.) CLK-CMP messages shall include the following parameters: 8-bit Sequence Number This value shall be incremented by one (modulo the field size, 256) by the BS whenever a new CLK-CMP message is generated. This parameter is used to detect packet losses. 8-bit Clock Comparison Value This value shall be the difference (modulo the field size, 256) between the following two reference clock signals: (1) a 10 MHz reference clock locked Dto the symbol clock of the air link (such as a GPS reference used to generate the symbol clock), and (2) an 8.192 MHz reference clock locked to the network clock. Duplicated Sequence Number This value is a duplication of the value in (1) for error detection of undetected and uncorrected bit errors. All CLK-CMP messages received with errors shall be discarded and handled as if the messages were lost. Duplicated Clock Comparison Value This value is a duplication of the value in (2) foruw€A E error detection of undetected and uncorrected bit errors. All CLK-CMP messages received with errors shall be discarded and handled as if the messages were lost. [MFor the transport of existing hierarchical signals, such as DS1 and DS3, timing jitter performance is very important. Currently, the specification has no mechanism to do so.QAcceptedR V. QuilezS2modify text to allow for multiple clocks to exist.TAccepted-ModifiedAStanley Wang will generate text to be inserted.: Add a new row (a new message type) on page 56, line 22: "| 28 | CLK-CMP | SS network clock comparison | Broadcast | Change the row currently on page 56, line 22 to read "| 29-255 | | Reserved for future use | |" Add a new row (a new global value) to Table 67 on page 309, line 29: "| BS | CLK-CMP Interval | Time between transmission of CLK-CMP messages | 50 | 50 | 50 |" Add a new section, section 6.2.2.2.28 (vx€ABor whatever the subsection number is) on page 102, line 35 as the follows (please use proper figure number): 6.2.2.2.28 Clock Comparison (CLK-CMP) Message In network systems with service flows carrying information that requires the SSs to reconstruct their network clock signals (e.g., DS1 and DS3), CLK-CMP messages shall be periodically broadcasted by the BS. If provisioned to do so, the BS shall generate one CLK-CMP message at every periodic interval defined in Table 67 according to theC format shown in Figure 1. CLK-CMP messages shall include the following parameters where Clock ID, Sequence Number and Clock Comparison Value shall be repeated for each clock signal: Clock Count This 8-bit value shall be the number of CCVs included in the CLK-CMP message. Clock ID This 8-bit value shall be the unique identifier for each clock signal from which the CCVs are generated by the BS. Sequence Number This 8-bit value shall be incremented by one (modulo the field size, 256wy€AD) by the BS whenever a new CLK-CMP message is generated. This parameter is used to detect packet losses. Clock Comparison Value This 8-bit value shall be the difference (modulo the field size, 256) between the following two reference clock signals: (1) a 10 MHz reference clock locked to the symbol clock of the air link (such as a GPS reference used to generate the symbol clock), and (2) an 8.192 MHz reference clock locked to the network clock. Xe) doneZcWhat are the time units in "Time between transmission of CLK-CMP messages | 50 | 50 | 50 |"?€BCKeithDDoucetEMemberG770HTechnical, BindingI56J28K6.2.2.2.1-2, 11.1.1-2LDCD and UCD messages should be adapted to support OFDM PHY and adaptive modulation. It is required to configure the OFDM parameters in these messages. The messages should enable the definition of multiple profiles for each usage code (DIUC/ UIUC) . xz€B A+These messages are designed for single carrier. PHY layer for the 802.16.3 (this draft is for both 802.16.1 and 802.16.3) has not been selected yet but OFDM and adaptive modulation are required by the customers to support reliable and efficient operation in the Non Line of Sight (NLOS) environment.+TRejectedUeThese messages are based on TLVs and so can support this in the future when an OFDM PHY is supported.Xf) none needed€CCChetDShiraliEMemberG771HTechnical, BindingI56J28K6.2.2.2.1-2, 11.1.1-2LDCD and UCD messages should be adapted to support OFDM PHY and adaptive modulation. It is required to configure the OFDM parameters in these messages. The messages should enable the definition of multiple profiles for each usage code (DIUC/ UIUC) . y{€C A+These messages are designed for single carrier. PHY layer for the 802.16.3 (this draft is for both 802.16.1 and 802.16.3) has not been selected yet but OFDM and adaptive modulation are required by the customers to support reliable and efficient operation in the Non Line of Sight (NLOS) environment.+S770T SupercededXf) none needed€DCManuelDPozaEOtherG640H EditorialI56J35K 6.2.2.2.1L?Insertion of dashes or bullets in the enumeration of parameters A Throughout all section 6.2.2.2 (MAC message types), most bullets are missed in the enumeration of the MAC messages parameters. In some cases (see by instance, page 97, line 41), in the same parameter list, some parameters are preceded by a dash and the rest are not.  T SupercededXf) none needed€ECKenDStanwoodEMemberG053HTechnical, Non-bindingI56J44K 6.2.2.2.1L%Change the valid range of T to 0-255.MeA lot of people have complained about T being a power of 2, and there is no good reason for it to be.z||€EQAcceptedR V. QuilezTRejectedUJpower of 2 is considered as adequate and has a much lower cost in hardwareXf) none needed€FCAntonisDKarvelasEOtherG407HTechnical, Non-bindingI56J49K 6.2.2.2.1L/The Downlink Channel ID does not need to exist.MIThe SS already knows Downlink Channel ID from the DCD Management message.QAcceptedR V. QuilezSon page 56, delete lines 49 to 52. on page 57, line 41 change the first sentence to read "To provide for flexibility, the remaining message parameters shall be encoded in ..."TAccepted-ClarifiedXe) done€GCStanleyDWangEObserverG540HTechnical, Non-bindingI57J2K 6.2.2.2.1 {}€G ARedraw the following figures to reflect the proposed new MAC header (if the proposed change is accepted): Figure 23 on page 57, Figure 25 on page 59, Figure 27 on page 62, Figure 28 on page 64, Figure 31 on page 69, Figure 33 on page 72, Figure 36 on page 75, and Figure 53 on page 98. Specifically, shift all bytes after the "Generic MAC Header" either one-byte to the left or one-byte up. ACurrent MAC header is 7 bytes long (an odd number) for downlink messages and 8 bytes long (an even number) for uplink messages. If the proposed new MAC header is accepted, the new MAC header will be 6 bytes long for both doenlink and uplink messages. The figures listed above need to be re-dwarn to refect that all downlink messages have an even number (instead of an odd number) of bytes for "Generic MAC Header." Note that the following figures will be removed by other comments: Figure 38 on|~8€G B page 84, Figure 40 on page 86, Figure 42 on page 88, Figure 44 on page 90, Figure 46 on page 91, Figure 48 on page 93, Figure 50 on page 95, and Figure 52 on page 97.QAcceptedR V. QuilezS047T SupercededXf) none needed€HCVicenteDQuilezEObserverF Comments onlyG816H EditorialI57J4K 6.2.2.2.1LDelete "(Downlink)" . Do the same in Figures 25, 27, 28, 31, 33, 36, 40, 42, 44, 46, 48, 50, 52, 53 Delete "(Uplink)" in figures 30, 32, 34, 35, 39, 41, 54, 55, 56 MIf the proposals for new headers are accepted, the terms (Downlink) and (Uplink) need to be deleted at the top of these mentioned figuresXe) doneYomade global change of "Generic MAC Header (Uplink)" and "Generic MAC Header (Downlink)" to "Generic MAC Header"€ICStanleyDWangEObserverG541HTechnical, Non-bindingI57J5K 6.2.2.2.1 }€I ADelete either " (Downlink)" or " (Uplink)" from the first row of the following figures after "Generic MAC Header": Figure 23 on page 57, Figure 25 on page 59, Figure 27 on page 62, Figure 28 on page 64, Figure 30 on page 68, Figure 31 on page 69, Figure 32 on page 70, Figure 33 on page 72, Figure 34 on page 73, Figure 35 on page 74, Figure 36 on page 75, Figure 53 on page 98, Figure 54 on page 98, Figure 55 on page 99, Figure 56 on page 100, Figure 57 on page 101, and Figure 58 on page 102B.MtIf the new MAC header format is accepted, there is no longer any difference between uplink and downlink MAC headers.QAcceptedR V. QuilezS047T SupercededXf) none needed€JCCarlDEklundEMemberG659H EditorialI57J43K 6.2.2.2.1L5Add after (T