Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0j€@pkER  DB G JU_isACE@ ACJ A E N!A"N#@$F%B&D'B( N)&M*,N+/A,1A-3N.6K/7A09A1=O2AO3FN4JJ5MN6NO7RA8SO9VA:XK;ZN<]N=`O>bB?eO@jFAmKBqJCtADuEzFF~JH€NI€NJ€ EK€OL€KM€NN€AO€NP€#OQ€)BR€.PS€3NT€8GU€g0*rg.p.?Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  ,  X5 `(V`VX`X`~?0 `(0SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDecsT٘   6/19/2001@ BALLOTNUMBERCHANGE COMMENT DATE COMMENT NUMBER COMMENT TYPE COMMENTARY VERSION DOCNUMBER EXPORTDATE FIRST NAME LAST NAMEMEMBERSHIP TYPEREASONSECTION STARTING LINE NUMBER STARTING PAGE NUMBER              G!ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]EPro 5.0F!2(M1,,./: AM PMYyTtNnFfP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  ,  ABCDEFGHI J K L M NOPQRSTUVWXYZ[\]    !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ D ACommentary VersionB GA ExportDateB GA BallotNumberB GA DocNumberB GA First NameB GA Last NameB GAMembership TypeB GAComment NumberB G A Comment DateB G A Comment TypeB G AStarting Page NumberB G AStarting Line NumberB G ASectionB GAChangeB GAReasonB GACounter *A1.1C3aDIEEE 802.16-01/30r0`A Layout #1Bh$$$$@:A  $,.YesNo/,  , : AM PMB   C  $,.YesNo/,  , : AM PMD   E  $,.YesNo/,  , : AM PMF   G  $,.YesNo/,  , : AM PMH   I  $,.YesNo/,  , : AM PM _ [COUNTERDECISION OF GROUP DOCNUMBEREDITOR'S ACTION ITEMSEDITOR'S ACTIONS EDITOR'S NOTEEDITOR'S QUESTION EXPORTDATE FIRST NAMEGROUP'S ACTION ITEMS GROUP'S NOTES LAST NAMEMEMBERSHIP TYPEREASONREASON FOR GROUP DECISIONREASON PROPOSEDRECOMMENDATION RESOLUTION BYRESOLUTION OF GROUPRESOLUTION PROPOSEDSECTION STARTING LINE NUMBER STARTING PAGE NUMBER               GA Resolution byB GARecommendationB GAResolution ProposedB GAReason ProposedB 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 BCommentary VersionD ExportDateF BallotNumberH DocNumberJ First NameL Last NameNMembership TypePComment NumberR Comment DateT Comment TypeVStarting Page NumberXStarting Line NumberZSection\Change^Reason`Counterb Resolution bydRecommendationfResolution ProposedhReason ProposedjResolution of GrouplDecision of GroupnReason for Group Decisionp Group's NotesrGroup's Action ItemstEditor's Actionsv Editor's NotexEditor's QuestionzEditor's Action Items @BBAt  !"#$%&'()*+,-./0123456789tB%468        "$&( "$&(@ 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    s  $,.YesNo/,  , : AM PMt   u  $,.YesNo/,  , : AM PMv   w  $,.YesNo/,  , : AM PMx   y  $,.YesNo/,  , : AM PMz   B 2001/06/19ERogerFMarksGMemberH001J EditorialMglobalN-Make sure all Figs and Tables are referencedOThis change was accepted in Comment 821 of Letter Ballot #3, but change was not implemented and comment was marked "defer to next round".P710B 2001/06/19ERogerFMarksGMemberH002J EditorialMglobalN-Make sure all tables have numbers and titles.OThis change was accepted in Comment 821 of Letter Ballot #3, but change was not implemented and comment was marked "defer to next round".P711B 2001/06/19ERogerFMarksGMemberH003JTechnical, Non-bindingN{Note: the comment applies to D2. It is Subbu Ponnuswamy's Comment 1046 from LB#3 and was not previously considered.} Change as per submission IEEE 802.16.1-01/25@ Q*,.02468 v        "$&(*,.02468        "$&( "$&( E()*+!,-./301F23*45967# 8 9: T 2 C     TU$U#D&6(S5 8H!:6G"JZ#L&Y$\l%^k&n~'p#} A('*:,B9<L>8KN^PB]`p bEo Br tF  $ % 3 2@@@A Layout #1A Layout #1Bh$$$$@:A  $,.YesNo/,  , : AM PMB   C  $,.YesNo/,  , : AM PMD   E  $,.YesNo/,  , : AM PMF   G  $,.YesNo/,  , : AM PMH   I  $,.YesNo/,  , : AM PMB 2001/06/19ERogerFMarksGMemberH004J EditorialK7L18MToCNModify Table of Contents format to improve look when long section titles cause a line break. See List of Figures and List of Tables for a better method.O1The current method looks bad and is hard to read.P714B 2001/06/19ERogerFMarksGMemberH005JTechnical, Non-bindingK17L11M1.4N{Note: the comment applies to D2. It is Scott Marin's Comment 1050 from LB#3 and was not previously considered.} At a minimum, insert new sentence, "Figure 2 shows the 802.16 protocol layering."OFigure 2 is not introduced or explained. The explanation of Figure 2 is an excellent opportunity to introduced several acronyms noted in the figure. P715B 2001/06/19ERogerFMarksGMemberH006J EditorialK19L57MLoFNQDelete initial spaces before titles of some figures and tables (e.g., Figure 41).OMThis causes the alignment to be off in the List of Figures and List of TablesP716B 2001/06/19ERogerFMarksGMemberH007@A1. The number of bits is not consistent throughout the document: Figures 18 and 19 on page 20 and Table 1 on page 52, specify a 4-bit FSN. Figure 61 on page 104 indicate a 3-bit FSN field. 2. 3/4-bit FSN limits the maximum number of fragments (hence number of MPDUs) per-MSDU to 8/16. This may not be sufficient for some systems that may want to support smaller MPDUs. 3. A per-packet FSN is not required for reassembly. Since two FC bits can unambiguously indicate the first and last fragmentsB of an MSDU, a per-connection MPDU-Sequence number (MPDU-SN) works well for re-assembly. 4. Per-packet FSN causes ambiguity in re-assembly. This is especially true if multiple MPDUs of the same connection are transmitted in the same frame. In general, the ambiguity exists if the last X consecutive fragments of packet (P) and the first (Total # fragments in P - X) consecutive fragments of packet (P + 1) of the same connection are lost. It has been proposed by TG1 (in Session 12) to make tAChe 3-bit FSN as a running count, as opposed to a per-packet FSN. This could still result in ambiguity, if eight consecutive MPDUs are lost. Though it may seem unlikely, this is still possible, e.g., all eight MPDUs are sent in the same frame during a fade. @A 33P712 @}JTechnical, Non-bindingK27L28M1AtRevise Overview: *Purpose should explain the unique role and application of this standard. *IEEE 802 Architectural Conformance should explain the unique role of 802.16 in the 802 family and explain its differences from other 802 networks. *Reference Model should be corrected to correctly show the scope of the standard. It should also be used to illustrate applications.tO)To make the standard more understandable.P718B 2001/06/19ERogerFMarksGMemberH008J EditorialK29L61M2NReview normative reference list for editorial corrections to harmonize the style with IEEE conventions. Also, check for correct cross-references in text.O~Editorial. Cross-references were mentioned in Comment 367 of Letter Ballot #3; this comment was marked "defer to next round".P719 B 2001/06/19ERogerFMarksGMemberH009J EditorialK31L31M3  A7Add definitions: frequency division duplex (FDD): A duplex scheme in which uplink and downlink transmissions use different frequencies but are typically simultaneous. time-division duplex (TDD): A duplex scheme where uplink and downlink transmissions occur at different times but may share the same frequency.7OThese are important terms. The definitions are those of 802.16.2/D3-2001. Note that, according to these definitions, half-duplex FDD is both FDD and TDD. This is appropriate, since the separation is in both time and frequency.P720 B 2001/06/19EStanleyFWangGObserverH010J EditorialK35L18NBARQ stands for "Automatic Repeat Request" instead of "Retransmit" P662 B 2001/06/19EStanleyFWangGObserverH011J EditorialK35L65M4N7Add the following acronym: "ECB Electronic Code Book"OUsed on page 227P330 B 2001/06/19EStanleyFWangGObserverH012J EditorialK36L52M4N4Add the following acronym: "OID Object Identifier"OUsed on page 230P331 B 2001/06/19! EStanleyFWangGObserverH013J EditorialK37L62M4N$The last 3 acronyms are out of orderO out of orderP332B 2001/06/19EKenFStanwoodH014J EditorialK38L16M5N*Change "specified:the" to "specified: the"O space missingP498B 2001/06/19EStanleyFWangGObserverH015J EditorialK38L56M5.1.2.1N*Change "QoS" to "Quality of Service (QoS)'OUsing "QoS" for the first time.P333B 2001/06/19EStanleyFWangGObserverH016J EditorialK39L34M5.1.3.1NOChange "7 bytes" to "6 bytes" Make the same change for page 40, line 4 as well.ONew MAC header has 6 bytes.P334B 2001/06/19EAntonisFKarvelasH017J EditorialK41L2M5.1.4.2NIt would be useful to include a protocol reference model that will describe where the ATM UNI (ATM NNI) and the IWF exists for the BS and the SS.OTo help reader.P463B 2001/06/19ECarlFEklundH018J EditorialK42L27N$p42 l 27.5; remove the extra periodP626B 2001/06/19ERogerFMarksGMemberH019JTechnical, Non-bindingK42L41M 6.1.1.2.4 "N{Note: the comment applies to D2. It is Scott Marin's Comment 1057 from LB#3 and was not previously considered.} After "appropriate agorithms" insert, e.g. [state an appropriate agoriithm].OWhat does "appropriate algorithms" mean? The text is very vague. Perhaps text should be added that states an example of one appropriate algorithm.P721B 2001/06/19EVladimirFYanoverH020JTechnical, Non-bindingK43L12M5.2.2N7Delete the "ingress Classifier" from figures 10 and 11.OThere is no definition of this term in the text. The only remark is that it is "Vendor specific", no operations with this entity are assumed so this is out of the scope of the Air Interface Standard.P647B 2001/06/19EVladimirFYanoverH021JTechnical, Non-bindingK44L35M5.2.3!#AChange "If a Classifier is found in which all parameters match the packet, the Classifier shall forward the packet to the corresponding Connection. If no Classifier is found in which all parameters match the packet then the packet is delivered under vendor or operator specific conditions." to the following text "If a Classifier is found in which all parameters match the packet, the Classifier shall copy the packet to the corresponding Connection. If no Classifier is found in which alBjl parameters match the packet then the packet is delivered under vendor or operator specific conditions."XOChanging "forward" to "copy" allows to clarify the situation when the packet has to be delivered to several destinations (broadcast or multicast)P649B 2001/06/19EVladimirFYanoverH022J EditorialK54L25M 6.1.1.1.2N3Change "service type" to "scheduling service type"O"This is the exact term from 6.2.5 P651B 2001/06/19EVladimirFYanoverH023J EditorialK54L37M 6.1.1.1.2"$N`Swap "sequence number" and "ARQ parameters" Same about their specification at page 55, line 10 OfIt is logical for the sequence number to appear at the last place, afer all the connection parameters P653B 2001/06/19EVladimirFYanoverH024J EditorialK54L50M 6.1.1.1.2N@Change "The traffic parameters" to "The service flow parameters"O2According to the list of the primitive parameters P650B 2001/06/19EVladimirFYanoverH025J EditorialK54L58M 6.1.1.1.2AbChange "The length indicator specifies whether the SDUs on the Service Flow are fixed-length or variable-length." to "Packing on/off indicator,specifies whether packing may be applied to the MAC SDUs on this connection The Fixed-length or variable-length SDU indicator specifies whether the SDUs on the Service Flow are fixed-length or variable-length."bOPacking on/off indicator specification was missed. There is "Fixed-length or variable-length SDU indicator ", not "length indicator" in the list of parameters. P652#%B 2001/06/19EVladimirFYanoverH026JTechnical, Non-bindingK63L47M6.2.1NSRemove "These messages are carried in Ethernet packets as specified in 5.2.5.1." AThis sentence seems requesting from 802.16 conformant system to carry messages of IP based management protocol in Ethernet format. Such a request is too restrictive because a system not necessarily has an Ethernet interface between Convergence Sublayer and upper layers. The messages of DHCP, TFTP, SNMP might travel in the Internet end to end without a single transformation into the Ethernet format.P654B 2001/06/19EVladimirFYanoverH027J EditorialK67L6M 6.2.2.1.1NDelete the following text fragments from the Table 3 For type = 0x03 "code may be reused for some DL only purpose" For type = 0x04 "(not needed simultaneously with packing sub-header)" For type = 0x05 "code may be reused for some DL only purpose"OJThese are comments for the developers of the standard, not for the readersP655B 2001/06/19EKen$&FStanwoodH028J EditorialK67L11M 6.2.2.1.1NSAdd "(UL only, code may be reused for some DL only purpose)" in description column.O+Clarity. Consistency with lines 15 and 20.P499B 2001/06/19EKenFStanwoodH029JTechnical, Non-bindingK68L3M 6.2.2.1.2AOn page 68, line 3, add the line "f) UGS and UGS/AD connections may use the bandwidth request type code "000010" which requests a change to the active Maximum Sustained Traffic Rate, bounded by the admitted Maximum Sustained Traffic Rate." On page 68, line 21 add the qualifier "Type = 000000 or 000001" in the Description field below the line "Bandwidth Request" On page 68, after line 22 add "Type = 000010 The requested active Maximum Sustained Traffic Rate in kbits per second" On page %'B70, line 8, change "UGS" to "UGS || USG/AD". On page 70, Delete lines17-24. on page 70, Delete lines 41-44. On page 115, line 1 change "grants per Nominal Grant Interval" to "bandwidth" On page 115, line 1 change "Grants Per Interval" to "Maximum Sustained Traffic Rate" On page 115, line 4 delete the last sentence of the paragraph. On page 115, line 48, change "Nominal Grant Interval, the Tolerated Grant Jitter" to "Maximum Sustained Traffic Rate" On page 115, line 51, change "grants in thCe first (and/or second) grant interval" to "bandwidth" On page 115, line 53, change "a total of one grant for each grant interval" to "total bandwidth as if the allocation started" On page 115, line 54, delete from ",plus one additional" through the end of the next sentence. On page 115, line 60 to page 116, line 5 replace the entire paragraph with "The Grant Management subheader is used as in the UGS case. On page 157, lines 45-57 replace all 6 occurrances of "Grants Per Interval" with "M&(+D$aximum Sustained Traffic Rate" On page 157, lines 49, 51, and 56 replace all 3 occurrances of "one" with "to that required for one higher layer flow" On page 157, line 56 replace "four" with "to that required for four higher layer flows" On page 343, delete line 21 through page 345, line 15.AThe whole "grants per interval" concept is a hokey way to accomplish what real communications systems accomplish by setting peak rates. We already have the concept of peak rate in the "Maximum Sustained Traffic Rate" parameter. Everything sorrounding grants per interval is redundant with other more traditional QoS parameters we already have. There is nothing you can do with the grants per interval scheme that you can't do with the traditional scheme. In fact, the grants per interval sc')Bheme starts breaking down as the link gets loaded. Additionally, page 157 already explains how to use teh DCD messages to expand and contract UGS and UGS/AD without the grants per interval in the GM. If quicker turn around tme is needed, we should add a special type code for the Bandwidth Request Header that, rather than asking for a discrete amount of bandwidth asks for a change in the active Maximum Sustained Traffic Rate (bounded of course by the admitted).P503B 2001/06/19ERogerFMarksGMemberH030J EditorialK68L37M6.2.2.2N/Delete 6.2.2.2 and renumber following sections.ORedundant with 6.2.2.3.P722B 2001/06/19EKenFStanwoodH031JTechnical, Non-bindingK68L43M6.2.2.2N,Change "Fragmentation" to "Grant Management"OPer Figure 28 on page 109, the Grant Management subheader is pre-pended after the Fragmentation subheader is already attached to the SDU.P500 B 2001/06/19EKenFStanwoodH032JTechnical, Non-bindingK68L45M6.2.2.2(* NAdd the sentence: "The Packing subheader and the Fragmentation subheader are mutually exclusive and shall not both be present within the same MAC PDU."O%Clarity. This is implied in Table 3.P501!B 2001/06/19ECarlFEklundH033J EditorialK68L47M6.2.2.2N"Change 'Ifpresent' to 'If present'P607"B 2001/06/19EKenFStanwoodH034J EditorialK68L47M6.2.2.2N"Change "Ifpresent" to "If present"OMissing space.P502#B 2001/06/19EKenFStanwoodH035J EditorialK70L48M 6.2.2.3.2NGAt the end of line 48 add "Piggy-Back Requests are always incremental."OWClarity. This is stated later in the document, but it would help if it were here, too.P504$B 2001/06/19ECarlFEklundH036J EditorialK71L6M 6.2.2.3.3N'Change word 'illustrated ' to 'defined'OThe table defines the formatP620%B 2001/06/19EStanleyFWangGObserverH037J EditorialK71L19M 6.2.2.3.3N#Change "MAC SDU Length" to "Length"O$Field name shall be spelled exactly.P335&B 2001/06/19ECarlFEklundH038J EditorialK71L50)+&M6.2.2.4NChange '.MAC' to 'MAC'OSounds too much like '.NET'P619'B 2001/06/19EKenFStanwoodH039J EditorialK71L50M6.2.2.4NChange ".MAC" to "MAC"O Extra period.P505(B 2001/06/19EStanleyFWangGObserverH040J EditorialK71L50M6.2.2.4NChange ".MAC" to "MAC"OTypoP336)B 2001/06/19EKenFStanwoodH041J EditorialK71L55M6.2.2.4N?Delete the sentence starting "The internal format of the CS..."OaThis section does not talk about convergence sublayer messages, so the statement is out of place.P506*B 2001/06/19EKenFStanwoodH042JTechnical, Non-bindingK72L4M6.2.2.4NRemove "(optonal)".OFor MAC Management messages, the payload is not optional like it is for CS messages. It must have at least the message type code.P507+B 2001/06/19ECarlFEklundH043J EditorialK73L42M 6.2.2.4.1 NTChange 'modulo the field size' to 'modulo 256' Make same change on page 75 line 56 P621,B 2001/06/19EKenFStanwoodH044J EditorialK75L12M 6.2.2.4.1*,,NOn page 75 line 12 and again on page 76, line 12 add the following sentence: "Burst Descriptor contents are defined separately for each PHY mode in section 8."OClarityP508-B 2001/06/19EStanleyFWangGObserverH045J EditorialK76L21M 6.2.2.4.3NDelete the line "Length" and move the next 3 lines to the end of line 15. Before moving the 3 lines, change (on line 22) "Length field" to "LEN field"O&"Length" is not a parameter of DL-MAP.P337.B 2001/06/19EStanleyFWangGObserverH046JTechnical, Non-bindingK76L30M 6.2.2.4.3A/Add the following parameter: "DCD Count Matchs the value of the Configuration Change COunt of the DCD, which describes the burst parameters that apply to this map." Boldface the first line. Also on line 49, ass the following corresponding parameter to the table: "| DCD Count | 8 bits | |" /O/DCD Count is needed for sychronization purpose.P338/B 2001/06/19EKenFStanwoodH047J EditorialK76L56M 6.2.2.4.3+-/AOn page 76, line 56 properly indent "DL_MAP..." On page 76, line 56 add "Variable" to the Size column On page 76, line 56 add "See corresponding PHY spec." to the Notes column On page 76, line 57 add a row with "}" to cloe out line 55 On page 77, line 29 properly indent "UL_MAP..."O5Correct typo in Table 14. Consistency with Table 15.P5090B 2001/06/19EAntonisFKarvelasH048J EditorialK79L17M 6.2.2.4.6NReplace the "The RNG-RSP Message shall be transmitted using the burst profile in the UL-MAP, " with the "The RNG-RSP Message shall be transmitted using the burst profile in the DL-MAP, "OThe RNG-RSP message is sent by the BS in the downlink, so it uses the burst profile in the DL-MAP message, not the UL-MAP message.P4751B 2001/06/19EAntonisFKarvelasH049JTechnical, Non-bindingK80L6M 6.2.2.4.6NaInsert a new field : "Uplink operational burst profile : the SS uplink operational burst profile",.t1AIt is not described in the standard the process by which the SS selects its uplink operational burst profile. I believe that the ranging process can be used by BS to assign the SS its uplink operational burst profile. Specifically the BS, based on measurements from the physical layer when it receives the RNG-REQ message from the SS, can decide what would be the better uplink operational burst profile for the SS.P4832B 2001/06/19EAntonisFKarvelasH050J EditorialK80L47M 6.2.2.4.7NRemove the HMAC Digest field.ABased on section "11.4.12 HMAC-Digest" the scope of the HMAC Digest doesn't include the REG-REQ message. Generally it is not clear in the standard what the SS is responsible to do as concern as the authentication in the case the SS doesn't support privacy.P4863B 2001/06/19EAntonisFKarvelasH051J EditorialK81L28M 6.2.2.4.8-/3NReplace the sentence "The CID in the Generic MAC Header is the Basic CID for this SS." with "The CID in the Generic MAC Header is the Primary Management CID for this SS."OGThe REG-RSP message uses the Primary Management CID based on Table 11. P4644B 2001/06/19EVladimirFYanoverH052JTechnical, Non-bindingK81L29M 6.2.2.4.8NChange "The CID in the Generic MAC Header is the Basic CID for this SS" to "The CID in the Generic MAC Header is the Primary Management CID for this SS"OmThis is inconsistent with Table 11-MAC Management Messages - where REG-RSP is sent on Primary Management CID.P6585B 2001/06/19ECarlFEklundH053JTechnical, Non-bindingK81L34M 6.2.2.4.7N`Change '1=Authentication Failure' to '1=Message authentication failure' . Delete '2=CoS Failure'OThe SS is already authenticated at registration time. Since SFs are nbo longer included in the REG-REQ there is no basis for CoS failure whatever it means.P6096B 2001/06/19EAntonisFKarvelasH054JTechnical, Non-binding.06K81L43M 6.2.2.4.8NAInsert the sentence "Network Access Control Object (see 11.4.3)".AAt section "6.2.9.9 Registration" the standard says that "The REG-RSP message shall include the Secondary Management CID and the Network Access Control Object 11.4.3." but the Network Access Control Object is not included in the definition of the RNG-RSP message.P4687B 2001/06/19EAntonisFKarvelasH055JTechnical, Non-bindingK82L1M 6.2.2.4.9NUThe REG-ACK message doesn't serve a specific goal and must removed from the standard./17AThe REG-ACK message was essential in the IEEE 802.16.1/D1 - 2000 version of the standard when the REG-REQ message from the SS included the Uplink and Downlink Service Flow Configuration Setting. But now during the Registration process the SS doesn't send the Service Flow Encodings, so the text "A Registration Acknowledge message shall be transmitted by the SS in response to a REG-RSP from the BS. It confirms acceptance by the SS of the QoS parameters of the flow as reported by the BS in Bit REG-RSP." is invalid for the current version of the standard because the REG-RSP doesn't contain QoS parameters of the SS's service flows. |P4858B 2001/06/19ECarlFEklundH056JTechnical, Non-bindingK82L4M 6.2.2.4.9NDelete line 'It confirms....'O-SF QoS parameters are not known at this time.P6109B 2001/06/19EKenFStanwoodH057JTechnical, Non-bindingK84L33M 6.2.2.4.10029AOn page 84, delete lines 33-37. On page 85, line 1 delete the subsentence starting "a particular Security Association..." On page 85, delete lines 13-16 On page 90 delete line 36 through page 91, line 47. On page 324, delete line 54 through page 325 line 12OPThe PKM MAP messages are no longer needed now that the SA is in the DSA messagesP510:B 2001/06/19EStanleyFWangGObserverH058J EditorialK84L47M 6.2.2.4.10NChange "e.g.," to "i.e.,"OThis is not an example.P339;B 2001/06/19EStanleyFWangGObserverH059J EditorialK84L54M 6.2.2.4.10N%Change "may be set" to "shall be set"OThis is not an option.P340B 2001/06/19EStanleyFWangGObserverH062J EditorialK85L26M 6.2.2.4.10N$Change "Packet formats" to "Formats"OThey are not packets.P343?B 2001/06/19ERogerFMarksGMemberH063J EditorialK85L57M 6.2.2.4.10.1NlAdd reference for X.509 at first use; possibly also in later usage. Is [RFC-2459] the appropriate reference?O"Need to tell people what X.509 is.P723@B 2001/06/19EStanleyFWangGObserverH064J EditorialK86L2M 6.2.2.4.10.1NChange the last sentence of the paragraph to read "This includes the data encryption and data authentication algorithms the SS supports."O:Avoid unnecessary modifications of the spec in the future.P344AB 2001/06/19EStanleyFWangGObserverH065J EditorialK86L34M 6.2.2.4.10.2NHChange the Contents column to read "Authorization Key's active lifetime"24AOOtherwise it can be confused with "Authorization Key Lifetime" which is a BS system parameter defined in Table 106. Active lifetime is a better description of the meaning of the parameter, which specifies the lifetime the AK remains active. P345BB 2001/06/19EStanleyFWangGObserverH066J EditorialK86L54M 6.2.2.4.10.3NGChange the title of the Table to read "Authorization Reject Attributes"OTypoP346CB 2001/06/19ECarlFEklundH067JTechnical, Non-bindingK87L17M 6.2.2.4.10.4N1Delete row with 'SS Identification' from table 28O.The SS Identification is done based on the CIDP611DB 2001/06/19EKenFStanwoodH068JTechnical, Non-bindingK87L18M 6.2.2.4.10.4NDelete line 18.O$SS Identifier no longer needed here.P511EB 2001/06/19EStanleyFWangGObserverH069JTechnical, Non-bindingK87L18M 6.2.2.4.10.4N-Delete the entire row for "SS-Identification"OUsing CID instead of SS-ID.P347FB 2001/06/19EStanleyFWangGObserverH070J EditorialK90L39M 6.2.2.4.10.1035FNChange "Section c)" to "Section 7.3.3" and fix the cross-reference. Make the same change on page 90 line 63 and page 91 line 25.OTypo.P348GB 2001/06/19ECarlFEklundH071JTechnical, Non-bindingK90L53M 6.2.2.4.10.10N1Delete row with 'SS Identification' from table 34O,The SS Identification TLVs have been removedP612HB 2001/06/19EKenFStanwoodH072JTechnical, Non-bindingK90L53M 6.2.2.4.10.10NIf the PKM MAP messages are kept: On page 90, delete line 53. On page 90, line 55 delete "downlink" On page 91, line 12 delete "downlink"OISS-identification no longer needed. Messages are valid for UL flows, too.P512IB 2001/06/19EKenFStanwoodH073JTechnical, Non-bindingK92L47M 6.2.2.4.11NOn page 92, line 47; on page 93, line 57; and on page 97, line 14 add: "Convergence Sulayer Parameter Encodings (see 11.4.16) Specification of the Service Flow's convergence sublayer specific parameters" O CompletenessP513JB 2001/06/19EAntonisFKarvelasH07446JJTechnical, Non-bindingK93L3M 6.2.2.4.11.2NReplace the sentence : "BS-initiated DSA-Requests for Uplink Service Flows shall also include a Connection ID." with the following : "BS-initiated DSA-Requests shall also include a Connection ID."OThe SS needs the CID not only for Uplnik Service Flows but also for Downlink Service Flows (to search in the downlink for MAC PDUs that belongs to its downlink service flows).P491KB 2001/06/19EKenFStanwoodH075JTechnical, Non-bindingK93L3M 6.2.2.4.11.2N"On page 90, line 3 delete "Uplink"O.The BS provides a CID for DL connections, too.P514LB 2001/06/19EKenFStanwoodH076JTechnical, Non-bindingK93L9M 6.2.2.4.11.2NOn page 93, line 9 add "BS-initiated DSA-Requests shall also include the SA-Descriptor for the service flow." On page 94, line 18 add "The BS's DSA-response shall also include the SA-Descriptor for the service flow."OAgreed to last meetingP515MB 2001/06/19ECarlFEklundH077J EditorialK105L46M4657MN,Change 'registration respone' to 'SBC-RSP' OCut'n'paste bugP613NB 2001/06/19EAntonisFKarvelasH078J EditorialK107L34M 6.2.2.4.30AChange the text : "The Dynamic Service Addition Received Message shall be generated by the BS in response to an SS-initiated DSx-REQ to inform the SS that the BS has received the DSx-REQ message in a more timely manner than provided by the DSx-RSP message, which may only be transmitted after the DSx-REQ is authenticated. The format of the DSx-RVD shall be as shown in Table 56." to : "The Dynamic Service Addition/Change Received Message shall be generated by the BS in response to an SS-initB , to carry fixed length MAC SDUs the packing procedure described in this section may be used. In this case the Request/Transmission Policy shall be set to allow packing and prohibit fragmentation and the SDU size shall be included in DSA-REQ message when establishing the connection. The SDUs are packed into the payolad of the MAC PDU without Packing SubB-headers. This is illustrated in . If the MAC SDU size equals n bytes, the receiveing side can unpack the MAC PDU payload as the size of it will be k*n, where k is the number of MAC SDUs packed into the PDU. "OKCurrent text is wrong as the length of the header is included in LEN fieldP622SB 2001/06/19EStanleyFWangGObserverH083J EditorialK111L18M 6.2.3.4.1N\Change the first field to read "n*k+6" instead of "n*6" and make the same change on line 28.8:SO@The LEN field includes the size of MAC header, which is 6 bytes.P349TB 2001/06/19EStanleyFWangGObserverH084J EditorialK113L40M6.2.3.6NChange "Recall" to "Note"OIt hasn't be discussed before.P350UB 2001/06/19ECarlFEklundH085JTechnical, Non-bindingK114L52M6.2.5.1NChange 'The key service information elements are ' to read 'The Unsolicited grant service shall be specified using the following parameters: ' O"The current wording is too vague. P623VB 2001/06/19EVladimirFYanoverH086JTechnical, Non-bindingK115L1M6.2.5ADelete the whole paragraph "The BS shall not allocate ... with UGS service" Delete the whole paragraph that from line 51 to line 57 p.115 "In USG-AD service ... a DSC command" Delete the following text, line 23 p. 116: "Minimum Reserved Traffic Rate, Maximum Sustained Traffic Rate", "Traffic Priority." Delete the following text, line 35 p. 116: "Minimum Reserved Traffic Rate, Maximum Sustained Traffic Rate", "Traffic Priority."9;VAAs a general approach, Air Interface Standard specifies MAC signaling (including the signaling related to the capacity request/allocation) but does NOT specify algorithms/policy of the capacity allocation. The section 6.2.5 describes "basic uplink service flow scheduling services". These are services provided for the scheduling itself, not for the data transfer. When BS allocates capacity for the Reservation Request expected from SS, - it is scheduling service. When BS allocates capacityB* for the data transfer - it is data transfer service. So any prescription on how BS decides on allocation of grants should be deleted from the text. Minimum Reserved Traffic Rate, Maximum Sustained Traffic Rate, Traffic Priority.are the parameters of data delivery, not of the scheduling process.P656WB 2001/06/19ECarlFEklundH087JTechnical, Non-bindingK115L4N"Delete sentence ' The active ....'OWe have no active grants fieldP624XB 2001/06/19EKenFStanwoodH088J Editorial:<XK115L39M6.2.5.3NzDelete the sentence in parenthesis starting "The BS can detect..." Through the word "However," of the following sentence.ODebatable whether the first sentence is true. Since it's informative and the second sentence says what we need to say, it's best to delete the first sentence.P519YB 2001/06/19EAntonisFKarvelasH089JTechnical, Non-bindingK117L22M6.2.6.1NLI believe that the GPC mode must be removed because it offers no advantage. AThe GPC mode spends much bandwidth in the downlink when we have a large number of connections because the BS must send resource allocations for each connection. Also the use of a SS local scheduler is useful because it knows the real -time needs of each connection so it can more efficiently allocate the bandwidth to the individual connections. Also the deletion of the GPC mode will help the interoperability.P481ZB 2001/06/19EKenFStanwoodH090J EditorialK117L26M6.2.6.1;=ZNNchange "UL maps and more intelligent" to "UL maps and allows more intelligent"OgrammarP520[B 2001/06/19ERogerFMarksGMemberH091JTechnical, Non-bindingK118L1M6.2.6.2A'Check to see whether this resolution from LB#3 (applied to D2) was correctly implemented: On page 111, lines 4-35 replace the upper right 2 boxes and 3 decision diamonds in Figure 65 (after implementation of comment 739) with the same portion of Figure 66 (after implementation of comment 521).'@A* 33[  *O?To confirm completeness of resolution of Comment 790 from LB#3.P724\B 2001/06/19ERogerFMarksGMemberH092J EditorialK124L62M6.2.7.2NAdd to end of paragraph: "Note that operation with half-duplex terminals is both FDD and TDD, since the uplink and downlink transmissions are separated in both time and frequency."O#Clarification of a confusing point.P725]B 2001/06/19EKenFStanwoodH093J EditorialK125L10M6.2.7.2<>]N+Redraw Figures 40 and 111 in frame maker. O'They don't print correctly on some PCs.P521^B 2001/06/19ERogerFMarksGMemberH094J EditorialK125L62M6.2.7.3NChange "In the case of TDD, the uplink and downlink transmissions share the same frequency, but are separated in time. " to Change "In the case of TDD, the uplink and downlink transmissions occur at different times but may share the same frequency."OCompatibility with definition of TDD proposed here and used in 802.16.2/D3-2001 ("A duplex scheme where uplink and downlink transmissions occur at different times but may share the same frequency.")P726_B 2001/06/19EKenFStanwoodH095JTechnical, Non-bindingK127L7M 6.2.7.5.3.1NOn page 127, delete lines 7-9.O4Priority Request multicast CIDs don't exist anymore.P522`B 2001/06/19EKenFStanwoodH096JTechnical, Non-bindingK127L43M 6.2.7.5.3.5NDelete lines 43-47=?O`OPer the UIUC definitions in the PHY section, the Expansion IE doesn't exist, and if it did, its existance would be PHY dependant.P523aB 2001/06/19EKenFStanwoodH097J EditorialK129L54M6.2.8N7Change "dependent of the CID" to "dependent on the CID"OgrammarP524bB 2001/06/19ECarlFEklundH098JTechnical, Non-bindingK130L24M6.2.8AOn page 130 line 24 Replace the sentence 'The SS determines ... ' with 'The SS shall consider the contention transmission lost if no grant has been given in the stipulated number of UL-MAPs or within the time in which they were to be received.' On page 122 line 40 Replace sentence ' If the BS... ' to 'The SS shall assume that the transmission has been unsuccessful if no grant has been received in the number of subsequent UL-MAP messages specified by the parameter < reference new entry in>@bB table 11.1.1.1>. Note that with a frame based PHY with UL-MAPs occurring at predetermined instants errenous UL-MAPs may be counted towards this number.' P614cB 2001/06/19EKenFStanwoodH099JTechnical, Non-bindingK130L31M6.2.8N@On page 130, delete lines 31-34. On page 300, delete lines 56-59OdThe decision to discard a PDU MUST be QoS and priority dependant, not arbitrarily set at 16 retries.P525dB 2001/06/19EAntonisFKarvelasH100J EditorialK134L56M6.2.9.3NVReplace the box title "Establish IP Connectivity" with "Negotiate Basic Capabilities".OThe Figure 48 must agree with Figure 47. The Figure 47 shows that after ranging the SS executes the "Negotiate Basic Capabilities" process.P465eB 2001/06/19EAntonisFKarvelasH101J EditorialK137L38M6.2.9.5NChange the sentence "allocate Basic, Primary Management, and Secondary Management Connection" as "allocate Basic and Primary Management Connection" in Figure 50.?AeOeThe Secondary Management CID is given to the SS with the REG-RSP message and not the RNG-RSP message.P466fB 2001/06/19EAntonisFKarvelasH102J EditorialK137L43M6.2.9.5NChange the sentence "store Basic Connection ID & adjust other parameters" as "recognize own MAC Address, store Basic Connection ID & adjust other parameters" in Figure 50.OThe SS recognizes the first RNG-RSP from the BS (that is own RNG-RSP message) using the SS MAC Address field of the RNG-RSP message. This information will help the reader.P467gB 2001/06/19EKenFStanwoodH103JTechnical, Non-bindingK141L11M6.2.9.8N&Delete "unless explicitly told not to"OFAgreed last meeting that we always do authentication and key exchange.P526hB 2001/06/19EKenFStanwoodH104J EditorialK141L18M6.2.9.9N+Change "manageable.To" to "manageable. To" O missing spaceP527iB 2001/06/19EStanleyFWangGObserverH105J EditorialK141L18M6.2.9.9N$Change "ageable.To" to "ageable. To"OMissing space.P351jB 2001/06/19EKen@BjFStanwoodH106JTechnical, Non-bindingK142L26M6.2.9.9NMLast state should now be "Establish IP Connectivity" instead of "Operational"O3Previously, we changed the order of initialization.P528kB 2001/06/19EKenFStanwoodH107J EditorialK146L38M6.2.10N&Change "(re-range)\." to "(re-range)."OtypoP529lB 2001/06/19ERogerFMarksGMemberH108JTechnical, Non-bindingK148L1M6.2.10A4In the periodic ranging process, insert into Figure 60 the case in which SS is already at its maximum (minimum) power and is not able to further increase (decrease) it. The SS should then use the "Ranging Anomalies" field in its ranging request by setting bit #0 (#1). Reflect this change in Figure 51 also.4OThis change was accepted in Comment 553 of Letter Ballot #3, but change was not implemented and comment was marked "defer to next round". Cited Reason: In order to avoid dead locks the SS must inform the BS when it has reached its limits.P713mB 2001/06/19EKenFStanwoodH109J EditorialACmK148L49M6.2.10.1NOn page 148, line 49 change "available,and" to "available, and" On page 148, line 51 change "downlink,the" to "downlink, the" On page 148, line 52 change "methods,the" to "methods, the"Omissing spacesP530nB 2001/06/19ECarlFEklundH110JTechnical, Non-bindingK151L25M6.2.11N?Insert section from IEEE 802.16.1c-01/33 between 6.2.10 6.2.11OIssue needs to be clarifiedP625oB 2001/06/19EKenFStanwoodH111JTechnical, Non-bindingK154L8M6.2.11.3NWhy is the authorized parameter set not known by the SS? We should communicate it somehow or we may get a lot of DSC messages from an SS that continuously get rejected.P531pB 2001/06/19EVladimirFYanoverH112J EditorialK155L4M6.2.11.3NFigure 66 seems containing a statement that N connections may correspond to one Service Flow. This should be clarified. (The author's opinion is that Service Flow should be defined as something associated with either 0 or 1 connection)P657qB 2001/06/19EKenFStanwoodH113BDqJTechnical, Non-bindingK156L32M6.2.11.5NOn page 156, line 32 delete "receives all registration messages" On page 156, line 42 delete "not only receives all registration messages, but"OFThe information in question is no longer in the registration messages.P532rB 2001/06/19EKenFStanwoodH114JTechnical, Non-bindingK157L22M 6.2.11.6.1NOn page 157, line 22 delete the sentence starting ""The BS may deactivate..." On page 157, line 28 delete the sentence starting ""The BS may deactivate..."OBThese sentences are not true. Services can be deleted at ay time.P533sB 2001/06/19EAntonisFKarvelasH115J EditorialK158L29M 6.2.11.6.3NThe standard says that : "These Service Flows are established at registration time and shall be authenticated by the BS MIC." but the BS MIC doesn't exist somewhere else in the standard.OTo remove ambiguity.P496tB 2001/06/19EKenFStanwoodH116JTechnical, Non-bindingK158L42M 6.2.11.7.1CEtA$Replace the last 3 sentences of the paragraph with "When this is complete, the BS passes service flow encodings to the SS in multiple DSA-REQ messages. The SS replies with DSA-RSP messages. The BS sends DSA-ACK messages to complete service flow initialization. This is shown in Figure 67."$O5The existing text had the old push from the SS model.P534uB 2001/06/19EVladimirFYanoverH117JTechnical, Non-bindingK159L33M 6.2.11.7.1N[Change the direction of the last three messages at the Figure 67Registration Message Flow AFigure 67 "Registration Message Flow "(p 159) illustrates the BS as the initiator of the DSA transactions for static SF's while in the section 6.2.9.12.1 "Service Flow Setup" p 145 line 53 we find: "After privacy is initialized, or after registration if privacy is disabled, the SS shall send DSA-REQ messages to the BS for to set up connections for the service flows listed in the configuration file. The BS shall respond with the DSA-RSP message"DFuP659vB 2001/06/19EAntonisFKarvelasH118J EditorialK159L35M 6.2.11.7.1NChange the direction arrows of DSA-REQ(mult), DSA-RSP(mult) and DSA-ACK(mult). The DSA-REQ(mult) is from SS to BS, the DSA-RSP(mult) is from BS to SS and the DSA-ACK(mult) is from SS to BS.OIn static operation the SS passes the configuration information received from the provisioning server to the BS in multiple DSA-REQ messages.P487wB 2001/06/19EKenFStanwoodH119JTechnical, Non-bindingK160L1M 6.2.11.7.1N%Delet lines 1-21. delete lines 28-30.O]This information is no longer in the Config File, and the config file is described elsewhere.P535xB 2001/06/19EKenFStanwoodH120JTechnical, Non-bindingK166L1M 6.2.11.8.2NxWe need to add the sending and receiving of the DSX-RVD message to Figures 72, 73, 74, and 75. Also to Figures 79 and 83OThey are incomplete.P536yB 2001/06/19EKenFStanwoodH121J EditorialK168L12M 6.2.11.8.2NChange "DSA-RSP" to "DSC-RSP"OtypoP537zB 2001/06/19EKenEHzFStanwoodH122J EditorialK172L10M 6.2.11.8.3.1AxOn page 172, after line 10 add the line "Set Timers T7 and T14" on the SS side. On page 172, line 13 change "if" to "is" On page 172, after line 28 add the line "Timer T7 Stops" on the SS side. On page 172, line 39 change "can happen prior" to "happens prior" On page 173, after line 18 add "Set Timer T7" to BS side On page 173, after line 27 add "Timer T7 Stops" to BS side.xOClarity, completness and typos.P538{B 2001/06/19EAntonisFKarvelasH123J EditorialK174L17M 6.2.11.8.3.3N3Change the "Send RNG-RSP (abort)" to "Send DSA-REQ"OErroneous text.P492|B 2001/06/19EKenFStanwoodH124J EditorialK174L18M 6.2.11.8.3.3N%Change "RNG-RSP (abort)" to "DSA-REQ"Ocut and paste errorP539}B 2001/06/19EKenFStanwoodH125J EditorialK182L34M 6.2.11.8.4N$Change "connections" tp "connection"O[gramar, the article "a" makes the noun singular with multiple mutually-exclusive adjectivesP540~B 2001/06/19EKenFStanwoodH1265PT٘BUUX  $,.YesNo/,  , : AM PM HelveticaGenevaTimes New Roman FI~J EditorialK183L12M 6.2.11.8.4.1AOn page 183, after line 12 add the line "Set Timers T7 and T14" on SS side On page 183, line 14 change "T12" to "T14" On page 183, after line 22 add the line "Timer T7 Stops" to the SS side On page 184, after line 11 add the line "Set Timer T7 " on BS side On page 184, after line 18 add the line "Timer T7 Stops " on BS side On page 185, add the seting of T14 in SS case On page 186, add the reception of DSX-RVD in the SS case. On page 190 add the sending of DSX-RVD in the BS case.OCompleteness and fix typoP541B 2001/06/19EAntonisFKarvelasH127J EditorialK183L14M 6.2.11.8.4.1N2Change the "Timer T12 Stops" to "Timer T14 Stops".O>The right Timer here is the T14 not the T12 based on Table105.P494€B 2001/06/19EStanleyFWangGObserverH128J EditorialK199L38M7.1.1N$Change "MAC sublayer" to "MAC layer"O.Change should have been made per comment #966.P352€B 2001/06/19EStanleyFWangGObserverH129J EditorialK199L55M7.1.2HJv€NFChange "; i.e.," to ", i.e.," make the same change on page 200 line 1.OTypoP353€B 2001/06/19EStanleyFWangGObserverH130J EditorialK199L57M7.1.2NZChange "secret (i.e., an Authorization Key)" to "secret, i.e., an Authorization Key (AK),"O6To establish the abbriviation to be used on next page.P354€B 2001/06/19EStanleyFWangGObserverH131JTechnical, Non-bindingK200L1M7.1.2NDelete "other identifying information; i.e.," and ", manufacturer ID and serial number" so that the beginning of the line reads "with SS MAC address."OSerial number is being removed from X.509 certificate (see line 7 page 232). Manufacturer ID is optional and is not included in X.509 (see 7.6.1.6). Note SS certificate is signed by the manufacturer so that the manufacturer's ID is implied.P355€B 2001/06/19EStanleyFWangGObserverH132JTechnical, Non-bindingK200L37M7.1.3IK€NChange "traffic flows" to "service flows" and make the same change throughout the document including "traffic flow" to "service flow"O8"service flow" is the correct term (see definition 3.40)P356€B 2001/06/19EStanleyFWangGObserverH133J EditorialK200L37M7.1.3N&Change "multiple SS" to "multiple SSs"OTypoP357€B 2001/06/19EStanleyFWangGObserverH134J EditorialK200L44M7.1.3NChange "an SAID" to "SAIDs"OTypoP358€B 2001/06/19EStanleyFWangGObserverH135J EditorialK200L48M7.1.3NChange "must be" to "shall be"OTypoP359€B 2001/06/19EStanleyFWangGObserverH136J EditorialK200L57M7.1.3NChange the sentence to read "Should the current keying material expire before a new set of keying material is received, the SS shall perform network entry as described in 6.2.9."O ClarificationP360€ B 2001/06/19EStanleyFWangGObserverH137J EditorialK201L7M7.1.4NOChange "in section (Table 7.3)" to "in Section 7.3" and fix the cross-referenceOTypoP361€ B 2001/06/19JL€ EStanleyFWangGObserverH138J EditorialK201L8M7.1.4N"Change "PrimarySA" to "Primary SA"OMissing space.P362€ B 2001/06/19EStanleyFWangGObserverH139J EditorialK201L26M7.2.1NeChange the last sentence to read "The rest of this Section provides an overview of the PKM protocol."O:This section provides more than just the two state models.P363€ B 2001/06/19EStanleyFWangGObserverH140J EditorialK201L28M7.2.2NOChange the title of the section to capitalize the first character of each word.OTypoP364€ B 2001/06/19EStanleyFWangGObserverH141J EditorialK201L28M7.2.2NChange the section from H3 to H4, i.e., 7.2.1.1. Correspondingly, change current "7.2.3" to "7.2.1.2"; change current "7.2.3.1" to "7.2.1.3"; and change "current "7.2.4" to "7.2.1.4" As a result, current "7.2.5" should become "7.2.2"OIncorrect section hierarchy.P365€B 2001/06/19EStanleyFWangGObserverH142JTechnical, Non-bindingK202L19M7.2.2N,Change "will determine" to "shall determine"KM€OThis is not an option.P366€B 2001/06/19EVladimirFYanoverH143JTechnical, Non-bindingK202L19M7.2.2NB 2001/06/19EStanleyFWangGObserverH190J EditorialK224L11M7.4.2N"Change "SS uses" to "SS shall use"Orequired to do.P412€?B 2001/06/19EStanleyFWangGObserverH191J EditorialK224L18M7.4.2N;Change the end of the line to read "newer" instead of "new"OtypoP413€@B 2001/06/19EStanleyFWangGObserverH192JTechnical, Non-bindingK224L23M7.4.2A Change starting "an SS attempts..." until the end of the paragraph to read "an SS shall request a new set of traffic keying material a configurable amount of time, TEK Grace Time (see points (x) and (y) in Figure 104), before the SS's latest TEK is scheduled to expire. O clarificationP414€AB 2001/06/19EStanleyFWangGObserverVX€AH193JTechnical, Non-bindingK225L20M7.4.2NSChange "AKx Residual Lifetime" to "AKx Active Lifetime" (3 occurences on this page)OCAK Residual Lifetime was proposed but was rejected everywhere else.P415€BB 2001/06/19EStanleyFWangGObserverH194JTechnical, Non-bindingK226L25M7.4.2NUChange "TEKx Residual Lifetime" to "TEKx Active Lifetime" (5 occurences on this page)ODTEK Residual Lifetime was proposed but was rejected everywhere else.P328€CB 2001/06/19EStanleyFWangGObserverH195J EditorialK227L3M7.5N+Change "the protocol" to "the PKM protocol"O ClarificationP416€DB 2001/06/19EStanleyFWangGObserverH196J EditorialK227L4M7.5N(Change "must support" to "shall support"O ClarificationP417€EB 2001/06/19EStanleyFWangGObserverH197J EditorialK227L8M7.5.1N-Change "Data encryption" to "Data Encryption"OCapitalizationP418€FB 2001/06/19EStanleyFWangGObserverH198J EditorialK227L12M7.5.1N$Change "US Data" to "US 56-bit Data"WY€FO+option 0x01 is specifically for 56-bit DES.P419€GB 2001/06/19EStanleyFWangGObserverH199JTechnical, Non-bindingK227L15M7.5.1AChange the paragraph to read as follows: The CBC IV shall be calculated as follows: in the downlink, the CBC shall be initialized with the Exclusive-OR (XOR) of (1) the IV parameter included in the TEK keying information, and (2) the content of the PHY Synchronization field of the latest DL-MAP. In the uplink, the CBC shall be initialized with the XOR of (1) the IV parameter included in the TEK keying information, and (2) the content of the PHY Synchronization field of the DL-MAP that is BJin effect when the UL-MAP for the uplink transmission is created/received.8XZ€GAyWith XOR, modulo 2^64 is not needed, since the IV parameter is always the same length as the block length of cipher, i.e., 64 bits for Suite 0x01. With ripple carry, a 64-bit parallel adder requires 100-200 times longer than XOR (even in HW). While XOR provides different 24 least significant bits, ADD provides different 25 least significant bits. The improvement is minimum.yP420€HB 2001/06/19EStanleyFWangGObserverH200J EditorialK227L27M7.5.1N6Change "ECB mode" to "Electronic Code Book (ECB) mode"OUsing ECB for the first time.P421€IB 2001/06/19EStanleyFWangGObserverH201J EditorialK227L29M7.5.1NLine 29, change "exclusive ored" to "XORed" Line 31, change "exclusive ORs" to "XORs" Line 37, change "exclusive ORed" to "XORed" Line 64, change "EXORing" to "XORing" Line 65, change "EXOR" to "XOR" Also add "XOR Exclusive OR" to line 62 page 37.O clarificationP422€JB 2001/06/19EStanleyFWangGObserverH202J EditorialK227L40M7.5.1Y[€JNChange TEKwith" to "TEK with"O missing spaceP423€KB 2001/06/19EStanleyFWangGObserverH203J EditorialK227L43M7.5.1NChange "TEK Exchange Algorithm" to "TEK Encryption Algorithm" Make the same change on (1) line 15 page 320, and (2) line 41 page 320.OGThis TLV specifies the encryption algorithm instead exchange algorithm.P424€LB 2001/06/19EStanleyFWangGObserverH204J EditorialK228L6M7.5.3N1Remove the word "and" after the word "HMAC_KEY_D"OTypoP425€MB 2001/06/19EStanleyFWangGObserverH205J EditorialK228L8M7.5.3N8Change "7.5.4" to "7.5.4.3" and fix the cross-reference.OPrecise referenceP426€NB 2001/06/19EStanleyFWangGObserverH206J EditorialK228L17M7.5.4NKChange the reference from [RFC-1750] to [B64] and fix the cross-reference. O+informative references are referred by [B#]P427€OB 2001/06/19EStanleyFWangGObserverH207J EditorialK228L25M7.5.4.1N>Add the word "byte" to read "of each byte is a parity bit...."OTypoP428€PB 2001/06/19EStanleyZ\!€PFWangGObserverH208JTechnical, Non-bindingK228L28M7.5.4.1NDelete the paragraph.OShould follow the standard.P429€QB 2001/06/19EStanleyFWangGObserverH209J EditorialK228L49M7.5.4.2N*Change "key material" to "keying material"OTypoP430€RB 2001/06/19EStanleyFWangGObserverH210J EditorialK229L6M7.5.5N7Change the beginning of the line to read "PKM protocol"O clarificationP431€SB 2001/06/19EStanleyFWangGObserverH211J EditorialK229L15M7.5.6NChange the paragraph to read "The PKM protocol employs the RSA Signature Algorithm [RSA2] with SHA-1 [FIPS-186] for all three of its certificate types, root certificate, manufacturer certificate, and SS certificate."O clarificationP432€TB 2001/06/19EStanleyFWangGObserverH212JTechnical, Non-bindingK229L27M7.6[]€TAAdd the following subsection 7.6.1 under section 7.6 and renumber the rest of the subsections. 7.6.1 Certificate Architecture The PKM protocol includes three types of certificates, root certificate, manufacturer certificate, and SS certificate. The IEEE 802 shall serve as the root CA, which issues certificates to IEEE 802.16 equipment manufacturers. The manufacturer CAs issue certificates to their SSs. Protocols for requesting certificates from a manufacturer CA and distributing the resulBCting certificates to its SSs shall be internal to the manufacturer.1O clarificationP433€UB 2001/06/19EStanleyFWangGObserverH213JTechnical, Non-bindingK230L13M7.6.1NADelete "and CRLs" from the line. Make the same change on line 45.OShould Certificate Revocation List (CRL) be used, clearer instruction MUST be given as how it is used. CRL is described in RFC2459.P434€VB 2001/06/19EStanleyFWangGObserverH214J EditorialK230L21M7.6.1.1\^€VN:Change "must " to "shall" Make the same change on line 45.OtypoP435€WB 2001/06/19EStanleyFWangGObserverH215JTechnical, Non-bindingK230L38M7.6.1.2N>Delete the last sentence of the paragraph starting on line 38.O&The SS serial number is being removed.P436€XB 2001/06/19EStanleyFWangGObserverH216J EditorialK230L47M7.6.1.3N)Change "OID" to "Object Identifier (OID)"OUsing it for the first time.P437€YB 2001/06/19ERogerFMarksGMemberH217JTechnical, Non-bindingK231L17M 8.2.1.1.1N{Note: the comment applies to D2. It is Scott Marin's Comment 1075 from LB#3 and was not previously considered.} Insert text, "????"A_Define "(204,188) Reed-Solomon" and "GF(256)". While the terms are commonly used, they need precise definition in the 802.16 standards. Isn't 204 the length of the frame in bits and 188 number of payload bits per frame?. Doesn't GF stand for Gal[oire] Field and shouldn't it be in the abreviation list in section 4? If so, insert the appropriate text.]_€Y_P727€ZB 2001/06/19ERogerFMarksGMemberH218JTechnical, Non-bindingK231L25M 8.2.1.1.1N{Note: the comment applies to D2. It is Scott Marin's Comment 1076 from LB#3 and was not previously considered.} At end of the sentence insert text, ",defined in section 8.2.4.4.1.8" or ",defined later."OProvided reader with a forward reference text that precisely defines the transfer function for a "root-raised cosine" function and the rool-off factor.P728€[B 2001/06/19EStanleyFWangGObserverH219JTechnical, Non-bindingK231L33M 7.6.1.4.1NAChange the 3 "TBD" to "IEEE802", "FBWA", and "IEEE802.16 Root CA"OTBDsP438€\B 2001/06/19EStanleyFWangGObserverH220I 2001-06-14JTechnical, Non-bindingK231L49M 7.6.1.4.2NCChange the "XX" to "SS" MAke the same change on line 55 and line 58OTBDsP439€]B 2001/06/19EStanleyFWangGObserverH221JTechnical, BindingK231L51M 7.6.1.4.2N+Change "Root Certificate Authority" to "CA"OIt is not the root.P440€^B 2001/06/19EStanley^`€^FWangGObserverH222J EditorialK231L55M 7.6.1.4.2N2Change "shall be included" to "shall be included."O Missing "."P441€_B 2001/06/19EStanleyFWangGObserverH223J EditorialK231L57M 7.6.1.4.2NRAdd "." to the end of the line and remove the "." from the beginning of next line.OTypoP442€`B 2001/06/19EStanleyFWangGObserverH224JTechnical, Non-bindingK232L7M 7.6.1.4.3NDelete line 7 on page 232 Replace lines 10-23 with "The MAC address shall be the SS's MAC address." and merge this line into one paragraph with line 25. Delete the word "two" from line 31 page 232. O]Remove the optional SS serial number, since SS MAC address can be used to uniquely ID the SS.P443€aB 2001/06/19EStanleyFWangGObserverH225J EditorialK232L38M7.6.1.5N*Change RSA public key" to "RSA-Public-Key"O6This is an attribute name and MUST be spelled exactly.P444€bB 2001/06/19EStanleyFWangGObserverH226JTechnical, Non-bindingK233L2M7.6.1.7_a€bArAdd the following paragraph: The extensions defined for X.509 V3 certificates provide methods for associating additional attributes with users of public keys and for managing the certification hierarchy. All three types of the PKM certificates are not required to include any extensions, but may include extensions as described in this section and defined in [RFC2459].rO clarificationP445€cB 2001/06/19EStanleyFWangGObserverH227J EditorialK233L35M7.6.2N,Change "generation.The" to "generation. The"O missing spaceP446€dB 2001/06/19EStanleyFWangGObserverH228J EditorialK233L41M7.6.2NDelete the word "modem's"OunneededP447€eB 2001/06/19EPaulFThompsonGMemberH229J EditorialK248L54M8.2.1.1NThis relates to original Comment 384. I recommend that the text currently in paragraph 8.2.1.1 be included in paragraph 8.2.1 and that paragraphs 8.2.1.1.1 and 8.2.1.1.2 be renumbered as 8.2.1.1.and 8.2.1.2, respectively.`b€eO2There is a Section 8.2.1.1 but no Section 8.2.1.2 P675€fB 2001/06/19EJayFKleinH230J EditorialK250L4N"Refer to figure 111 and not to 110OMistakeP666€gB 2001/06/19EAntonisFKarvelasH231J EditorialK250L5M 8.2.2.1.1NNThe Figure 110 doesn't show the case where the downlink carrier is continuous.OTo correct the errored link.P469€hB 2001/06/19EKenFStanwoodH232J EditorialK250L5M 8.2.2.1.1N#Change "Figure 110" to "Figure 111"OReferring to wrong figureP497€iB 2001/06/19EPaulFThompsonGMemberH233JTechnical, BindingK250L13M 8.2.2.1.1NThis relates to the resolution of original Comment 403. I don't agree that the Comment is superceeded by Comment 573 because I can't find any FDD Frequency Plan in the new document. OjI believe that an Interoperability Standard should have at least one FDD Frequency Plan which is mandatoryP676€jB 2001/06/19ERogerFMarksGMemberH234JTechnical, Non-bindingK250L47 A 8.2.2.1.2 @A  ac€jNIn "where a PS is defined as four consecutive modulation symbol times", change "symbol times" to "symbols" Definitions belong in Clause 3. Can this one be moved there?O3A PS is a chunk of symbols, not a duration of time.P729€kB 2001/06/19EKenFStanwoodH235J EditorialK251L53M 8.2.2.1.3N-Change "aretransmitted" to "are transmitted" OtypoP542€lB 2001/06/19ELarsFLindhH236JTechnical, Non-bindingK251L60M 8.2.2.1.3NChange the sentence: "The downlink MAP indicates the number of PSs allocated to ..." to "The downlink MAP indicates the starting position of a burst. OJThe downlink MAP does not indicate length it indicates starting positions.P634€mB 2001/06/19EKenFStanwoodH237JTechnical, Non-bindingK251L60M 8.2.2.1.3bd€mAReplace the section starting with the sentence "The downlink map..." and ending "..remaining after integral FEC blocks are allocated." with: The downlink map indicates the number of PSs, i (which must be an integer), allocated to a particular burst and also indicates the burst type (modulation and FEC). Let n denote the minimum number of PSs required for one FEC block of the given burst profile (note that n is not necessarily an integer). Then i=kn+j+q, where k is the number of integrBal FEC blocks that fit in the burst and j is the number of PSs occupied by the largest possible shortened codeword (not necessarily an integer), and q (always 0 or a fraction) is the number of PSs occupied by pad bits inserted at the end of the burst to guarantee that i is an integer. If the "Fixed Codeword Operation" is being used (see section 8.2.4.4.4.1), then j is always 0. Note that a codeword can end partway through a modulation symbol as well as partway through a PS. When this oceo€mCccurs, the next codeword should start immediately, with no pad bits inserted. At the end of the burst (when there is no "next codeword"), then q*(# bits/symbol)*4 pad bits are added (if required) to complete the PS allocated in the downlink map. Note that pad bits may be required with or without shortening being used. Also, redraw figures 113 and 114 to show explicitly that the codewords do not necessarily occupy and integer number of modulation symbols or PSs, and also show explicitlyDi a field of length "q" containing pad bits at the end of the burst to result in an integer number of PSs.3df€mAThe current specification is unclear what should be done in the case that a codeword ends within a physical slot, or a modulation symbol. The discussion on page 251, lines 61-65 defines a variable 'n' which denotes the "minimum number of PSs required for one FEC block of the given burst profile." Although it does not explicitly say so, the discussion and figures 113 and 114 imply that 'n' is an integer. This is not nessesarily true, in fact a codeword is may not even end on a symbolB boundary. For example, suppose a Reed-Solomon +inner parity code with K=21, R=14 is used with 16 QAM modulation. Each codeword occupies 78.75 modulation symbols (i.e. 78 symbols + 3 bits of the 79th symbol) and 19.6875 physical slots. Similar cases can occur with 64 QAM when using the Reed-Solomon code. Several possibilities exist: (1) Immediately start the next codeword within the same modulation symbol (2) Restrict the allowed codewords to those that occupy an integer number of seg€mCymbols (or even PSs) (3) Pad the remaining bits in the modulation symbol, then start the next codeword on the following symbol. The proposal above assumes #1 is chosen.P603€nB 2001/06/19EKenFStanwoodH238J EditorialK252L58M8.2.2.2NOn page 252, line 58 change "station registration" to "initial access" On page 253, line 7 change "Registration" to "Initial Maintenance"OThis is not where "registration" happens. This is where initial system access happens. The official name (from the UIUC definitions) of these slots is Initial Station Maintenance intervals.P543€oB 2001/06/19EKenFStanwoodH239J EditorialK252L64M8.2.2.2NAdd a sentence "Note that any of these burst classes may or may not be present in any given frame, and may occur in any order and any quantity (limited by number of available PS) within the frame at the discretion of the BS uplink scheduler."OOClarity. The pircture shows 1 case out of an enormous number of possibilities.P544€pB 2001/06/19fh€pEJayFKleinH240J EditorialK253L41N*delete the "will" s in "...will both will"OgrammarP667€qB 2001/06/19EJayFKleinH241J EditorialK253L50NJThere is a missing reference and should be "in 8.2.2.1.3 or 8.2.4.4.4.4." OClarityP668€rB 2001/06/19EKenFStanwoodH242JTechnical, Non-bindingK254L8M8.2.3.1NOn page 254 line 8; page 254 line 29; page 254 line 51; page 255 line 31; and page 255, line 56 change "1 to 40" to "16 to 40".OTThis section is not discussing all possible PHYs for 802.16, just the 10-66 GHz PHY.P545€sB 2001/06/19EKenFStanwoodH243J EditorialK254L31M8.2.3.2NChange "0-12" to "1-13"OTo match the DIUC table.P546€tB 2001/06/19EKenFStanwoodH244JTechnical, Non-bindingK254L39M8.2.3.2N(Delete lines 39-40. Delete lines 61-62. O5This particular PHY no longer has a frameless option.P547€uB 2001/06/19ERogerFMarksGMemberH245JTechnical, Non-bindingK254L60M8.2.3.3gi€uNFix the Remark. It reads "if both start and end of active region in frame are zero this should be interpreted as frameless operation. A start active region greater than zero indicates half-duplex (i.e., TDD or FDD) operation."O Confusing.P730€vB 2001/06/19EKenFStanwoodH246JTechnical, Non-bindingK255L8M8.2.3.4N[On page 255, line 8 change "quarter" to "eighth" On page 311, line 11 change "1/4" to "1/8"OBetter resolution will better enable QAM-64 operation on the uplink, and the field in the RNG-RES message is already sized large enough to accomodate 1/8 symbol resolution.P548€wB 2001/06/19EKenFStanwoodH247J EditorialK257L2M 8.2.4.2.1NCDelete the phrase "when the downlink physical layer is implemented"OmIf we don't implement the PHY, the rest is moot. I think this is a typo resulting for removal of PHY mode A.P550€xB 2001/06/19EKenFStanwoodH248J EditorialK257L28M 8.2.4.2.1NKAdd "in the remainder of the downlink subframe" to the end of the sentence.hl€xO9To make it clear where the SS is looking for MAC headers.P549€yB 2001/06/19EJayFKleinH249J EditorialK258L46N Replace "all SS" with "all SSs" OGrammarP669€zB 2001/06/19EKenFStanwoodH250J EditorialK260L24M 8.2.4.2.4N"Change "1(DIUC=0)" to "1 (DIUC=0)"O missing spaceP551€{B 2001/06/19EAntonisFKarvelasH251JTechnical, Non-bindingK260L27M 8.2.4.2.4NlThe standard must report the PHY characteristics (modulation, FEC) of the Gap Downlink Burst Type (DIUC=14).OThe standard says that the Gap Downlink Burst Type (DIUC=14) shall not be defined in the DCD message because it is well-known, but there are not anywhere in the standard the characteristics (Modulation, FEC) of this DIUC.P471€|B 2001/06/19EKenFStanwoodH252J EditorialK260L30M 8.2.4.2.4NAdd the Paragraph "The End of DL-MAP Burst Type (DIUC=15) indicates the first PS after the end of the DL subframe. It is well known andshall not be included in the DCD message."pEXCOUNTER  DB G JU_isACE@ @ACJ A E N!A"N#@$F%B&D'B( N)&M*,N+/A,1A-3N.6K/7A09A1=O2AO3FN4JJ5MN6NO7RA8SO9VA:XK;ZN<]N=`O>bB?eO@jFAmKBqJCtADuEzFF~JH€NI€NJ€ EK€OL€KM€NN€AO€NP€#OQ€)BR€.PS€3NT€8GU€