Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0m€KRsnUNTER  DB G JU_isACE@ ACE A V T!N"U#O$S%F&N'A(C)A*A+C,E-!L.'V/*A0C1-U2/A31N42B5B6D75B86A97B:9A;<AGJ?IU@LNANBBQOCRODSNEVBFAGWJHYAI[AJ]OK`NLbBMcNNfNOjOPmNQpPRsUSuNTAUvNVzEW}PY€FZ€O[€V\€ J]€A^€M_€R`€Na€Eb€Ec€!Rd€'He€*Vf€1Eg€4Nh€6Ai€7Kj€:Ok€@@@X!@.HBAM3016AUG95@ AAzHH(FG(HH(d}HzA'dDs? 0J@WD K* KIL 8N^NuNVH $n8. 6.J*g j*JfYO/?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ DACommentary 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.2C3aDIEEE 802.16-01/30r1`A Layout #1B$$$$@: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%468XXXXXX X X X X X X XXXXX X"X$X&X(XX X"X$X&X(@ 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/07/13ERogerFMarksGMemberH001J 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".P710VAcceptedB 2001/07/13ERogerFMarksGMemberH002J 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".P711VAcceptedB 2001/07/13ERogerFMarksGMemberH003JTechnical, 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@ QX*X,X.X0X2X4X6X8 v        "$&(*,.02468XXXXXX X X X X X X XXXXX X"X$X&X(XX X"X$X&X( 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 #1B$$$$@:A  $,.YesNo/,  , : AM PMB   C  $,.YesNo/,  , : AM PMD   E  $,.YesNo/,  , : AM PMF   G  $,.YesNo/,  , : AM PMH   I  $,.YesNo/,  , : AM PMB 2001/07/13ERogerFMarksGMemberH004J 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.P714VAcceptedB 2001/07/13ERogerFMarksGMemberH005JTechnical, 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. P715U#7VAccepted-DuplicateB 2001/07/13ERogerFMarksGMemberH006J 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 TablesP716VAcceptedB 2001/07/13A1. 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 tJChe 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 33P712VRejectedWPoint #1 has been fixed previously Point #2 : The number of fragments is not limited to 8. Point #3&4 The fragmentation is per connection. Exactly 8 fragments has to be lost and it is wasteful to send multiple fragments of a packet in the same frame.  @ERogerFMarksGMemberH007JTechnical, 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.P718VAccepted-ModifiedYKen to provide suggestionB 2001/07/13ERogerFMarksGMemberH008J 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".P719VAccepted B 2001/07/13ERogerFMarksGMemberH009J 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.P720U;Definitions are ok. The note on half-duplex is not correctVAccepted-Clarified B 2001/07/13EStanleyFWangGObserverH010J EditorialK35L18NBARQ stands for "Automatic Repeat Request" instead of "Retransmit" P662U5Replace the list of acronyms with file "comment10.fm"VAccepted-Modified B 2001/07/13EStanleyFWangGObserverH011J EditorialK35L65M4N7Add the following acronym: "ECB Electronic Code Book"OUsed on page 227P330! V Superceded B 2001/07/13EStanleyFWangGObserverH012J EditorialK36L52M4N4Add the following acronym: "OID Object Identifier"OUsed on page 230P331V Superceded B 2001/07/13EStanleyFWangGObserverH013J EditorialK37L62M4N$The last 3 acronyms are out of orderO out of orderP332Uby 10VAccepted-DuplicateB 2001/07/13EKenFStanwoodH014J EditorialK38L16M5N*Change "specified:the" to "specified: the"O space missingP498QCERAcceptedVAcceptedB 2001/07/13EStanleyFWangGObserverH015J EditorialK38L56M5.1.2.1N*Change "QoS" to "Quality of Service (QoS)'OUsing "QoS" for the first time.P333QCERAcceptedV SupercededB 2001/07/13EStanleyFWangGObserverH016J 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.P334QCERAccepted-ModifiedSvRemove field sizes as they are not important here. Change "Overhead" "ATM CL header" Add definition for ATM CL-header "RTlThe suggested fix does not address the entire problem. Also we have defined all header is our table format. U5 replace 5.1.2-5.1.4.2 with the file "comment16.fm" VAccepted-ModifiedB 2001/07/13EAntonisFKarvelasH017J 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.P463QCERRejectedSNo specific input was offered. Editor agrees that figure might add clarity {Once upon a time we had such a diagram, but it caused so much controversy we got rid of it. Do we introduce it again? -Ken Stanwood}VRejectedB 2001/07/13ECarlFEklundH018J EditorialK42L27N$p42 l 27.5; remove the extra periodP626VAcceptedB 2001/07/13ERogerFMarksGMemberH019JTechnical, 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.P721UQOn page 56 line 11 delete "..., and enters the CID into approproriate algorithms"VAccepted-ClarifiedB 2001/07/13EVladimirFYanoverH020JTechnical, 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.P647QCERAccepted-ModifiedS\Also remove the text "IEEE 802.3/Ethernet CS" from figures 11 and 10 (four instances in all)"$uUReplace "Ingress classifier (....) " with "Reconstitution (e.g. undo PHS)" Also remove the text "IEEE 802.3/Ethernet CS " from figures 11 and 10 (4 instances in all)VAccepted-ModifiedB 2001/07/13EVladimirFYanoverH021JTechnical, Non-bindingK44L35M5.2.3AChange "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."X#%OChanging "forward" to "copy" allows to clarify the situation when the packet has to be delivered to several destinations (broadcast or multicast)P649QCERAccepted-ModifiedS.Change to "... corresponding Connection(s). " U`Keep the original wording but change "corresponding connection" to "corresponding connection(s)"VAccepted-ModifiedB 2001/07/13EVladimirFYanoverH022J EditorialK54L25M 6.1.1.1.2N3Change "service type" to "scheduling service type"O"This is the exact term from 6.2.5 P651Q Ken StanwoodRAccepted-ClarifiedSAlso change on line 42Uas per recommendationVAccepted-ClarifiedB 2001/07/13EVladimirFYanoverH023J EditorialK54L37M 6.1.1.1.2N`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 P653Q Ken StanwoodRAccepted$&SeOrdering of logical interface has no impact, so if no one objects, we should use Vladimir's ordering.VAcceptedB 2001/07/13EVladimirFYanoverH024J EditorialK54L50M 6.1.1.1.2N@Change "The traffic parameters" to "The service flow parameters"O2According to the list of the primitive parameters P650Q Ken StanwoodRAcceptedVAcceptedB 2001/07/13EVladimirFYanoverH025J 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. P652Q Ken StanwoodRAcceptedVAcceptedB 2001/07/13EVladimir%'FYanoverH026JTechnical, 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.P654QCERAccepted-ClarifiedSDiscuss in groupT'Mandating Ethernet seems unnecessary . VAccepted-ModifiedYCarl provides the inputB 2001/07/13EVladimirFYanoverH027J EditorialK67L6M 6.2.2.1.1&(NDelete 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 readersP655U>Replace p 67 lines 1-25 with contents of file "comment027.fm" VAccepted-ModifiedB 2001/07/13EKenFStanwoodH028J 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.P499VRejectedB 2001/07/13EKenFStanwoodH029JTechnical, Non-bindingK68L3M 6.2.2.1.2')AOn 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 th(*+Ce 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 "MD$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 scBheme 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).P503*,AOn page 37, delete line 50 On page 70, Delete lines17-24. on page 70, Delete lines 41-44. On page 114, delete lines 17. On page 114, line 36, delete "Unsolicited Grant Service with Activity Detection (UGS/AD)," 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, delete lines 28 through page 116, liBne 6. On page 157, lines 45-57 replace with "For example, if an upper layer service were using unsolicited grant service, and the addition of upper-layer flows could be adequately provided by increasing the Maximum Sustained Traffic Rate QoS parameter, then the following might be used. When the first higher layer flow is pending, the SS issues a DSA-REQ with the admitted Maximum Sustained Traffic Rate parameter equal to that required for one higher layer flow, and the active Maximum Susta+-Cined Traffic Rate parameter equal zero. Later when the higher layer flow becomes active, it issues a DSC-REQ with the instance of the active Maximum Sustained Traffic Rate parameter equal to to that required for one higher layer flow. Admission control was performed at the time of the reservation, so the later DSC-REQ, having the active parameters within the range of the previous reservation, is guaranteed to succeed. Subsequent higher layer flows would be handled in the same way. If thereD were three higher layer flows establishing connections, with one flow already active, the Service Flow would have admitted Maximum Sustained Traffic Rate equal to that required for four higher layer flows, and active Maximum Sustained Traffic Rate equal to that required for one higher layer flow." On page 304, line 33 add a level 4 section titled "Tolerated Poll Jitter" with body text " For the 10-66 GHz PHY, the minimum value of the Tolerated Poll Jitter (see section 11.4.11.18) shall be,.E 3000 usec. On page 341, line 53, changes the meaning of value 5 to "reserved". On page 342, line 33, delete "UGS-AD," On page 343, delete line 21 through page 345, line 15. iVAccepted-ModifiedB 2001/07/13ERogerFMarksGMemberH030J EditorialK68L37M6.2.2.2N/Delete 6.2.2.2 and renumber following sections.ORedundant with 6.2.2.3.P722UDelete lines 49-56VAccepted-ModifiedB 2001/07/13EKenFStanwoodH031JTechnical, 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.P500VAccepted B 2001/07/13EKenFStanwoodH032JTechnical, Non-bindingK68L45M6.2.2.2NAdd 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.P501VAccepted!B 2001/07/13ECarlFEklundH033J EditorialK68-/!L47M6.2.2.2N"Change 'Ifpresent' to 'If present'P607VAccepted"B 2001/07/13EKenFStanwoodH034J EditorialK68L47M6.2.2.2N"Change "Ifpresent" to "If present"OMissing space.P502VAccepted-Duplicate#B 2001/07/13EKenFStanwoodH035J 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.P504VRejected$B 2001/07/13ECarlFEklundH036J EditorialK71L6M 6.2.2.3.3N'Change word 'illustrated ' to 'defined'OThe table defines the formatP620VAccepted%B 2001/07/13EStanleyFWangGObserverH037J EditorialK71L19M 6.2.2.3.3N#Change "MAC SDU Length" to "Length"O$Field name shall be spelled exactly.P335VAccepted&B 2001/07/13ECarlFEklundH038J EditorialK71L50M6.2.2.4NChange '.MAC' to 'MAC'OSounds too much like '.NET'P619VAccepted'B 2001/07/13EKenFStanwoodH039J EditorialK71L50M6.2.2.4NChange ".MAC" to "MAC"O Extra period.P505.0'VAccepted-Duplicate(B 2001/07/13EStanleyFWangGObserverH040J EditorialK71L50M6.2.2.4NChange ".MAC" to "MAC"OTypoP336VAccepted-Duplicate)B 2001/07/13EKenFStanwoodH041J 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.P506VAcceptedW)Sentence is true but truely out of place.*B 2001/07/13EKenFStanwoodH042JTechnical, 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/1*AOn page 64 line 15 change "Message" to "MAC PDU" On page 72 delete everything on lines 2-11 from the figure 27. On page 71 line 53 - 55 replace first three sentences with " A set of MAC Management Messages are defined. These messages shall be carried in the Payload of the MAC PDU. All MAC Management Messages begin with a Management Message Type field and may contain additional fields. MAC Management Messages on the Basic, Broadcast and Initial Ranging connections shall neither be fragmenBted nor packed. MAC Management Messages on the Primary Management Connection may be packed and/or fragmented. " On page 66 line 5 change "0" to "msb" rotated 90 degrees On page 66 line 5 delete "8" On page 66 line 5 change "15" to "lsb" rotated 90 degrees On page 67 line 35 change "0" to "msb" rotated 90 degrees On page 67 line 35 delete "8" On page 67 line 35 change "15" to "lsb" rotated 90 degrees On page 64 line 30 at the left hand side of the diagram insert "MSB" rotated 90 02*Cdegrees On page 64 line 30 at the right hand side of the diagram insert "LSB" rotated 90 degrees Starting on page 74 delete the Generic_MAC_Header() row from table 12 through 20 , 22,23, 37-58. VAccepted-Modified+B 2001/07/13ECarlFEklundH043J EditorialK73L42M 6.2.2.4.1 NTChange 'modulo the field size' to 'modulo 256' Make same change on page 75 line 56 P621VAccepted,B 2001/07/13EKenFStanwoodH044J EditorialK75L12M 6.2.2.4.1NOn 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."OClarityP508VAccepted-B 2001/07/13EStanleyFWangGObserverH045J 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.P33713-UhDelete line 21 Append lines 22-25 to line 15. In the appended text change 'Length field' to 'LEN field'VAccepted-Clarified.B 2001/07/13EStanleyFWangGObserverH046JTechnical, 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.P338ULDo the proposed change Also on line 31 and 50 Change '64 bit' with '48 bit'VAccepted-ModifiedW+Necessity and the desire to reduce overhead/B 2001/07/13EKenFStanwoodH047J EditorialK76L56M 6.2.2.4.324/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.P509VAccepted0B 2001/07/13EAntonisFKarvelasH048J 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.P475ULDo suggested change but also change "The RNG-RSP" to "The initial RNG-RSP" VAccepted-Modified1B 2001/07/13EAntonisFKarvelasH049JTechnical, Non-bindingK80L6M 6.2.2.4.6351NaInsert a new field : "Uplink operational burst profile : the SS uplink operational burst profile"AIt 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.P483A\Do not do the suggested change but: On page 80 line 6 change "Granted downlink burst type" to "Downlink Operational Burst Profile" and make it boldface On page 311 line 43 change "Granted downlink burst type" to "Downlink Operational Burst Profile" On page 311 line 45 change "the DIUC to be used" to "the least robust DIUC that may be used" \VAccepted-ModifiedWKThe BS controls the operational UIUC by mandating it in th UL-MAP message.246}2B 2001/07/13EAntonisFKarvelasH050JTechnical (was Editorial)K80L47M 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.P486ADon't do what is requested but instead p. 104 line 23 Add a row to table 51"TLV encoded information | variable| |" p. 104 on line 26 add text " The RES-CMD shall include the following parameters encoded as TLV tuples: HMAC Tuple (see 11.4.12) The HMAC Tuple shall be the last attribute in the message. " Make HMAC Tuple boldface p. 107 line 25 replace row in table 55 with "TLV encoded information | variable| |" p. 107 on line 30 add text " The DREG-CMD shall includ572Be the following parameters encoded as TLV tuples: HMAC Tuple (see 11.4.12) The HMAC Tuple shall be the last attribute in the message. " Make HMAC Tuple boldface p. 108 line 27 Add a row to table 57 "TLV encoded information | variable| |" p. 108 on line 36 add text " The TFTP-CPLT shall include the following parameters encoded as TLV tuples: HMAC Tuple (see 11.4.12) The HMAC Tuple shall be the last attribute in the message " Make HMACC Tuple boldface p 92 l. 50-53 change*3 "-Digest" to " Tuple" p 92 l. 52 change "is" to "contains" p 94 l. 7-10 change*3 "-Digest" to " Tuple" p 94 l. 8 change "is" to "contains" p 95 l. 25-28 change*3 "-Digest" to " Tuple" p 95 l. 26 change "is" to "contains" p 96 l. 20-23 change*3 "-Digest" to " Tuple" p 96 l. 21 change "is" to "contains" p 97 l. 27-30 change*3 "-Digest" to " Tuple" p 97 l. 29 change "is" to "contains" p 98 l. 25-27 change*3 "-Digest" to " Tuple" p 98 l. 26 682Dchange "is" to "contains" p 99 l. 16-19 change*3 "-Digest" to " Tuple" p 99 l. 18 change "is" to "contains" pp 100 l. 3-6 change*3 "-Digest" to " Tuple" p 100 l. 4 change "is" to "contains" VAccepted-ModifiedW6Authentication and key exchange are mandatory features3B 2001/07/13EAntonisFKarvelasH051J EditorialK81L28M 6.2.2.4.8NReplace 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. P464VAccepted4B 2001/07/13EVladimirFYanoverH052JTechnical, 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.P658VAccepted-Duplicate5795B 2001/07/13ECarlFEklundH053JTechnical, 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.P609VAccepted6B 2001/07/13EAntonisFKarvelasH054JTechnical, Non-bindingK81L43M 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.P4688:6A On page 73 line 29 Change "De-register" to "De/Re-register" On page 106 replace line 50 through page 107 line 30 with contents of file "comment054.fm" On page 327-328 delete section 11.4.3 On page 141 line 20 delete "and the Network Access Control Object 11.4.3"  VAccepted-Modified7B 2001/07/13EAntonisFKarvelasH055JTechnical, Non-bindingK82L1M 6.2.2.4.9NUThe REG-ACK message doesn't serve a specific goal and must removed from the standard.AThe 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 9;f7Bit 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. |P485APage 72 line 42 change line "8 | REG-ACK | Registration acknowledge |Primary management|" to "8| | reserved | |" Delete on page 82 section 6.2.2.4.9 and it's contents Replace page 141 line 35 through 144 line 27 with contents of file "comment 55.fm" Page 159 line 13 remove "Registration ACK " from figure together with arrow. Page 302 delete lines 33-35 (timeout for REG-ACK") Page 335 line 24 Delete "REG-ACK," VAccepted-Clarified8B 2001/07/13ECarlFEklundH056JTechnical, Non-bindingK82L4M 6.2.2.4.9NDelete line 'It confirms....'O-SF QoS parameters are not known at this time.P610V Superceded9B 2001/07/13EKenFStanwoodH057JTechnical, Non-bindingK84L33M 6.2.2.4.10:<9AOn 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 messagesP510VAccepted-Modified:B 2001/07/13EStanleyFWangGObserverH058J EditorialK84L47M 6.2.2.4.10NChange "e.g.," to "i.e.,"OThis is not an example.P339UXPage 84 line 47 change " The SS shall ... )" to "The SS shall increment (modulo 256) " VAccepted-Modified;B 2001/07/13EStanleyFWangGObserverH059J EditorialK84L54M 6.2.2.4.10N%Change "may be set" to "shall be set"OThis is not an option.P340VAcceptedB 2001/07/13EStanleyFWangGObserverH062J EditorialK85L26M 6.2.2.4.10N$Change "Packet formats" to "Formats"OThey are not packets.P343VAccepted?B 2001/07/13ERogerFMarksGMemberH063<>?J 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.P723UAdd reference to section 7.6 VAccepted-ClarifiedWDSection 7.6 section desribes the certificate and references RFC 2459@B 2001/07/13EStanleyFWangGObserverH064J 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.P344VAcceptedAB 2001/07/13EStanleyFWangGObserverH065J EditorialK86L34M 6.2.2.4.10.2NHChange the Contents column to read "Authorization Key's active lifetime"OOtherwise 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. P345=?AVAcceptedBB 2001/07/13EStanleyFWangGObserverH066J EditorialK86L54M 6.2.2.4.10.3NGChange the title of the Table to read "Authorization Reject Attributes"OTypoP346VAcceptedCB 2001/07/13ECarlFEklundH067JTechnical, Non-bindingK87L17M 6.2.2.4.10.4N1Delete row with 'SS Identification' from table 28O.The SS Identification is done based on the CIDP611VAcceptedDB 2001/07/13EKenFStanwoodH068JTechnical, Non-bindingK87L18M 6.2.2.4.10.4NDelete line 18.O$SS Identifier no longer needed here.P511VAccepted-DuplicateEB 2001/07/13EStanleyFWangGObserverH069JTechnical, Non-bindingK87L18M 6.2.2.4.10.4N-Delete the entire row for "SS-Identification"OUsing CID instead of SS-ID.P347VAccepted-DuplicateFB 2001/07/13EStanleyFWangGObserverH070J EditorialK90L39M 6.2.2.4.10.10NChange "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.P348V SupercededGB 2001/07/13ECarlFEklundH071>@GJTechnical, Non-bindingK90L53M 6.2.2.4.10.10N1Delete row with 'SS Identification' from table 34O,The SS Identification TLVs have been removedP612V SupercededHB 2001/07/13EKenFStanwoodH072JTechnical, 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.P512V SupercededIB 2001/07/13EKenFStanwoodH073JTechnical, 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 CompletenessP513?AIUOn page 92, line 47; on page 93, line 57; and on page 97, line 14 add: "Convergence Sublayer Parameter Encodings (see 11.4.16) Specification of the Service Flow's convergence sublayer specific parameters" VAccepted-ClarifiedJB 2001/07/13EAntonisFKarvelasH074JTechnical, 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).P491VAcceptedKB 2001/07/13EKenFStanwoodH075JTechnical, 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.P514VAccepted-DuplicateLB 2001/07/13EKenFStanwoodH076JTechnical, Non-bindingK93L9M 6.2.2.4.11.2@BLNOn 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 meetingP515VAcceptedMB 2001/07/13ECarlFEklundH077J EditorialK105L46M46N,Change 'registration respone' to 'SBC-RSP' OCut'n'paste bugP613VAcceptedNB 2001/07/13EAntonisFKarvelasH078J 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-initACNB , 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. "CEROKCurrent text is wrong as the length of the header is included in LEN fieldP622Q Ken StanwoodRAccepted-ModifiedSInsert the above paragraph in front of the one that currently exists, rather than replacing it. Let comment 083 take care of length issue.TtThe above text adds good information, but does not replace valuable (once corrected) text in the existing paragraph.AReplace first 2 sentences (lines 3-6) with "For connections that are indicated, by the parameter , 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. " VAccepted-ModifiedSB 2001/07/13EStanleyFWangGObserverH083J EditorialK111L18M 6.2.3.4.1DFSN\Change the first field to read "n*k+6" instead of "n*6" and make the same change on line 28.O@The LEN field includes the size of MAC header, which is 6 bytes.P349Q Ken StanwoodRAccepted-ModifiedSAlso make the change on line 8.AOn line 8 change "k*n" to "n*k+j" and "...into the MAC PDU" and "...into the MAC PDU and j is the size of the MAC header and any prepended MAC Sub-headers. " line 18 Change the first field to read "n*k+j" instead of "n*k" and make the same change on line 28.VAccepted-ModifiedTB 2001/07/13EStanleyFWangGObserverH084J EditorialK113L40M6.2.3.6NChange "Recall" to "Note"OIt hasn't be discussed before.P350Q Ken StanwoodRAcceptedVAcceptedUB 2001/07/13ECarlFEklundH085JTechnical, 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. P623Q Ken StanwoodRAcceptedVAcceptedVEGVB 2001/07/13EVladimirFYanoverH086JTechnical, 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."FHVAAs 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.P656Q Ken StanwoodR SupercededSsI recommend that the first two items be superceded by comments 029 and 087. The last two items should be rejected.V SupercededWB 2001/07/13ECarlFEklundH087GIWJTechnical, Non-bindingK115L4N"Delete sentence ' The active ....'OWe have no active grants fieldP624Q Ken StanwoodRAcceptedS$Duplicate of a piece of comment 029.V SupercededXB 2001/07/13EKenFStanwoodH088J EditorialK115L39M6.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.P519Q Ken StanwoodRAcceptedV SupercededYB 2001/07/13EAntonisFKarvelasH089JTechnical, Non-bindingK117L22M6.2.6.1NLI believe that the GPC mode must be removed because it offers no advantage. HJYAThe 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.P481QCESkDiscuss with group {While I agree with Antonis, we should discuss this with TG3/TG4 first. -Ken Stanwood}U|Replace the paragraph starting on line 31 " Systems using the 10-66 GHz PHY defined in section 8.2 shall use GPSS mode." VAccepted-ModifiedZB 2001/07/13EKenFStanwoodH090J EditorialK117L26M6.2.6.1NNchange "UL maps and more intelligent" to "UL maps and allows more intelligent"OgrammarP520QCERAcceptedVAccepted[B 2001/07/13ERogerFMarksGMemberH091JTechnical, Non-bindingK118L1M6.2.6.2IK[A'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.P724Q Ken StanwoodR SupercededS!The figure appears to be correct.V Superceded\B 2001/07/13ERogerFMarksGMemberH092J 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.P725VRejectedW6In the case of half duplex FDD the link is still FDD. ]B 2001/07/13EKenFStanwoodH093J EditorialK125L10M6.2.7.2N+Redraw Figures 40 and 111 in frame maker. JL]O'They don't print correctly on some PCs.P521VAccepted^B 2001/07/13ERogerFMarksGMemberH094J 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.")P726UChange to "In the case of TDD, the uplink and downlink transmissions occur at different times and usually share the same frequency."VAccepted-Modified_B 2001/07/13EKenFStanwoodH095JTechnical, Non-bindingK127L7M 6.2.7.5.3.1NOn page 127, delete lines 7-9.O4Priority Request multicast CIDs don't exist anymore.P522VAccepted`B 2001/07/13EKenFStanwoodH096JTechnical, Non-bindingK127L43M 6.2.7.5.3.5KMw`NDelete lines 43-47OPer the UIUC definitions in the PHY section, the Expansion IE doesn't exist, and if it did, its existance would be PHY dependant.P523VAcceptedaB 2001/07/13EKenFStanwoodH097J EditorialK129L54M6.2.8N7Change "dependent of the CID" to "dependent on the CID"OgrammarP524VAcceptedbB 2001/07/13ECarlFEklundH098JTechnical, 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 inLNbB 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.' P614AOn 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 Random Access Timeout. Note that with a frame based PHY with UL-MAPs occurring at predetermined instants errenous UL-MAPs may be counted towards this number.' VAccepted-ModifiedcB 2001/07/13EKenFStanwoodH099JTechnical, Non-bindingK130L31M6.2.8MOcN@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.P525VRejecteddB 2001/07/13EAntonisFKarvelasH100J 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.P465U1Should also be redrawn/reimported into FramemakerVAcceptedeB 2001/07/13EAntonisFKarvelasH101J EditorialK137L38M6.2.9.5NChange the sentence "allocate Basic, Primary Management, and Secondary Management Connection" as "allocate Basic and Primary Management Connection" in Figure 50.OeThe Secondary Management CID is given to the SS with the REG-RSP message and not the RNG-RSP message.P466VAcceptedfB 2001/07/13EAntonisFKarvelasH102J EditorialK137L43M6.2.9.5NPfNChange 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.P467VAcceptedgB 2001/07/13EKenFStanwoodH103JTechnical, Non-bindingK141L11M6.2.9.8N&Delete "unless explicitly told not to"OFAgreed last meeting that we always do authentication and key exchange.P526VAcceptedhB 2001/07/13EKenFStanwoodH104J EditorialK141L18M6.2.9.9N+Change "manageable.To" to "manageable. To" O missing spaceP527VAcceptediB 2001/07/13EStanleyFWangGObserverH105J EditorialK141L18M6.2.9.9N$Change "ageable.To" to "ageable. To"OMissing space.P351VAcceptedjB 2001/07/13EKenFStanwoodH106JTechnical, Non-bindingK142L26M6.2.9.9NMLast state should now be "Establish IP Connectivity" instead of "Operational"OQjO3Previously, we changed the order of initialization.P528VAcceptedkB 2001/07/13EKenFStanwoodH107J EditorialK146L38M6.2.10N&Change "(re-range)\." to "(re-range)."OtypoP529Q Ken StanwoodRAcceptedVAcceptedlB 2001/07/13ERogerFMarksGMemberH108JTechnical, 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.P713Q Ken StanwoodRAcceptedUfigure60.fm figure51.fmVAccepted-ClarifiedmB 2001/07/13EKenFStanwoodH109J EditorialK148L49M6.2.10.1PRmNOn 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 spacesP530Q Ken StanwoodRAcceptedVAcceptednB 2001/07/13ECarlFEklundH110JTechnical, Non-bindingK151L25M6.2.11N?Insert section from IEEE 802.16.1c-01/33 between 6.2.10 6.2.11OIssue needs to be clarifiedP625VAccepted-ModifiedoB 2001/07/13EKenFStanwoodH111JTechnical, 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.P531VRejectedpB 2001/07/13EVladimirFYanoverH112J 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)QSpP657U2Change "0,N" to read "0,1" in figure 66 on line 6 VAccepted-ClarifiedqB 2001/07/13EKenFStanwoodH113JTechnical, 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.P532VAcceptedrB 2001/07/13EKenFStanwoodH114JTechnical, 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.P533VAcceptedsB 2001/07/13EAntonisFKarvelasH115J 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.P496RTsUpage 158 line 26-31 Delete "This is the case.... " through the end of the paragraph. Merge the remaining sentence with the next paragraphVAccepted-ClarifiedtB 2001/07/13EKenFStanwoodH116JTechnical, Non-bindingK158L42M 6.2.11.7.1A$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.P534AReplace 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 to complete service flow initialization. This is shown in Figure 67."VAccepted-ModifieduB 2001/07/13EVladimirFYanoverH117JTechnical, Non-bindingK159L33M 6.2.11.7.1SU:uN[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"P659TVuAOn page 145, line 51 change "Service Flow Setup" to "Establish Provisioned Connections" and reduce the header level to H3. On page 145, change lines 53 through 56 to say. After the transfer of operational parameters, the BS shall send DSA-REQ messages to the BS to set up connections for pre-provisioned service flows belonging to the SS. The SS responds with DSA-RSP messages. This is described further in section 6.2.11.7.1. On page 145, delete line 58 through page 146, line 3. On page B<146, move lines 4-16 to page 138, line 10. On page 146, delete lines 17-27. On page 159, line 48, change "Registration Message Flow" to Provisioned Connection Establishment Message Flow" On page 160, line 51. Between the DSA-Request and DSA-Response arrows, add an arrow from the BS to the SS labeled "RSX-RVD" *VAccepted-ModifiedvB 2001/07/13EAntonisFKarvelasH118J EditorialK159L35M 6.2.11.7.1UWvNChange 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.P487V SupercededwB 2001/07/13EKenFStanwoodH119JTechnical, 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.P535VAcceptedxB 2001/07/13EKenFStanwoodH120JTechnical, 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.P536VAccepted-ModifiedY(Ken and Stanley to provide new diagrams yB 2001/07/13EKenFStanwoodH121J EditorialK168L12M 6.2.11.8.2NChange "DSA-RSP" to "DSC-RSP"OtypoP537V SupercededzB 2001/07/13VYzEKenFStanwoodH122J 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.P538VAccepted{B 2001/07/13EAntonisFKarvelasH123J EditorialK174L17M 6.2.11.8.3.3N3Change the "Send RNG-RSP (abort)" to "Send DSA-REQ"OErroneous text.P492VAccepted|B 2001/07/13EKenFStanwoodH124J EditorialK174L18M 6.2.11.8.3.3N%Change "RNG-RSP (abort)" to "DSA-REQ"Ocut and paste errorP539VAccepted-Duplicate}B 2001/07/13EKenFStanwoodH125J EditorialK182L34M 6.2.11.8.4N$Change "connections" tp "connection"O[gramar, the article "a" makes the noun singular with multiple mutually-exclusive adjectives5PtlOBUUX  $,.YesNo/,  , : AM PM HelveticaGenevaTimes New Roman WZ}P540VAccepted~B 2001/07/13EKenFStanwoodH126J 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 typoP541UaDo changes as specified on pages 183 &184 New figures will be provided for pages 185, 186 and 190VAccepted-ModifiedYCarl will provide new figuresB 2001/07/13EAntonisFKarvelasH127J 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.P494VAccepted-Duplicate€B 2001/07/13EStanleyY[C€FWangGObserverH128J EditorialK199L38M7.1.1N$Change "MAC sublayer" to "MAC layer"O.Change should have been made per comment #966.P352QCERAcceptedVRejected€B 2001/07/13EStanleyFWangGObserverH129J EditorialK199L55M7.1.2NFChange "; i.e.," to ", i.e.," make the same change on page 200 line 1.OTypoP353QCERAcceptedVAccepted€B 2001/07/13EStanleyFWangGObserverH130J 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.P354QCERAcceptedVRejected€B 2001/07/13EStanleyFWangGObserverH131JTechnical, 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."Z\€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.P355QCERAcceptedVAccepted€B 2001/07/13EStanleyFWangGObserverH132JTechnical, Non-bindingK200L37M7.1.3NChange "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)P356QCERAcceptedVAccepted€B 2001/07/13EStanleyFWangGObserverH133J EditorialK200L37M7.1.3N&Change "multiple SS" to "multiple SSs"OTypoP357QCERAcceptedVAccepted€B 2001/07/13EStanleyFWangGObserverH134J EditorialK200L44M7.1.3NChange "an SAID" to "SAIDs"OTypoP358QCERAcceptedVAccepted€B 2001/07/13EStanleyFWangGObserverH135J EditorialK200L48M7.1.3NChange "must be" to "shall be"OTypoP359QCERAccepted[]€VAccepted€B 2001/07/13EStanleyFWangGObserverH136J 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 ClarificationP360QCERAcceptedVAccepted€ B 2001/07/13EStanleyFWangGObserverH137J EditorialK201L7M7.1.4NOChange "in section (Table 7.3)" to "in Section 7.3" and fix the cross-referenceOTypoP361QCERAcceptedU57V Superceded€ B 2001/07/13EStanleyFWangGObserverH138J EditorialK201L8M7.1.4N"Change "PrimarySA" to "Primary SA"OMissing space.P362QCERAcceptedVAccepted€ B 2001/07/13EStanleyFWangGObserverH139J 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.P363QCERAcceptedUDelete lines 20-26 VAccepted-Modified€ B 2001/07/13EStanleyFWangGObserverH140\^€ J EditorialK201L28M7.2.2NOChange the title of the section to capitalize the first character of each word.OTypoP364QCERAcceptedVAccepted€ B 2001/07/13EStanleyFWangGObserverH141J 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.P365QCERRejectedT/I see nothing wronfg with the current hierarchyVRejected€B 2001/07/13EStanleyFWangGObserverH142JTechnical, Non-bindingK202L19M7.2.2N,Change "will determine" to "shall determine"OThis is not an option.P366QCERAcceptedVAccepted€B 2001/07/13EVladimirFYanoverH143JTechnical, Non-bindingK202L19M7.2.2NB 2001/07/13EStanleyFWangGObserverH190J EditorialK224L11M7.4.2N"Change "SS uses" to "SS shall use"Orequired to do.P412QCERAcceptedV Superceded€?B 2001/07/13EStanleyFWangGObserverH191J EditorialK224L18M7.4.2N;Change the end of the line to read "newer" instead of "new"OtypoP413QCERRejectedV Superceded€@ko€@B 2001/07/13EStanleyFWangGObserverH192JTechnical, 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 clarificationP414QCERAcceptedV Superceded€AB 2001/07/13EStanleyFWangGObserverH193JTechnical, 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.P415QCERAcceptedV Superceded€BB 2001/07/13EStanleyFWangGObserverH194JTechnical, 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.P328QCERAcceptedV Superceded€CB 2001/07/13EStanleyFWangGObserverH195sEXCOUNTER  DB G JU_isACE@ @ACE A V T!N"U#O$S%F&N'A(C)A*A+C,E-!L.'V/*A0C1-U2/A31N42B5B6D75B86A97B:9A;<AGJ?IU@LNANBBQOCRODSNEVBFAGWJHYAI[AJ]OK`NLbBMcNNfNOjOPmNQpPRsUSuNTAUvNVzEW}PY€FZ€O[€V\€ J]€A^€M_€R`€Na€Eb€Ec€!Rd€'He€*Vf€1Eg€4Nh€6Ai€7Kj€:Ok€@Bl€CJo€GApVq€Kq€Ks5@ @X!@lp€CJ EditorialK227L3M7.5N+Change "the protocol" to "the PKM protocol"O ClarificationP416QCERAcceptedVAccepted€DB 2001/07/13EStanleyFWangGObserverH196J EditorialK227L4M7.5N(Change "must support" to "shall support"O ClarificationP417QCERAcceptedVAccepted€EB 2001/07/13EStanleyFWangGObserverH197J EditorialK227L8M7.5.1N-Change "Data encryption" to "Data Encryption"OCapitalizationP418QCERAcceptedVAccepted€FB 2001/07/13EStanleyFWangGObserverH198J EditorialK227L12M7.5.1N$Change "US Data" to "US 56-bit Data"O+option 0x01 is specifically for 56-bit DES.P419QCERRejectedVRejected€GB 2001/07/13EStanleyFWangGObserverH199JTechnical, Non-bindingK227L15M7.5.1oq€GAChange 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.8AyWith 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.yP420QCERAcceptedpr€GVAccepted€HB 2001/07/13EStanleyFWangGObserverH200J EditorialK227L27M7.5.1N6Change "ECB mode" to "Electronic Code Book (ECB) mode"OUsing ECB for the first time.P421QCERAcceptedVAccepted€IB 2001/07/13EStanleyFWangGObserverH201J 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 clarificationP422QCERAcceptedVAccepted€JB 2001/07/13EStanleyFWangGObserverH202J EditorialK227L40M7.5.1NChange TEKwith" to "TEK with"O missing spaceP423QCERAcceptedVAccepted€KB 2001/07/13EStanleyFWangGObserverH203J 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.P424QCEqt€KRAcceptedVAccepted€LB 2001/07/13EStanleyFWangGObserverH204J EditorialK228L6M7.5.3N1Remove the word "and" after the word "HMAC_KEY_D"OTypoP425QCERAcceptedVAccepted€MB 2001/07/13EStanleyFWangGObserverH205J EditorialK228L8M7.5.3N8Change "7.5.4" to "7.5.4.3" and fix the cross-reference.OPrecise referenceP426QCERAcceptedVAccepted€NB 2001/07/13EStanleyFWangGObserverH206J EditorialK228L17M7.5.4NKChange the reference from [RFC-1750] to [B64] and fix the cross-reference. O+informative references are referred by [B#]P427QCERAcceptedUPChange the reference from "[RFC-1750]" to "[B64]" and fix the cross-reference. VAccepted-ClarifiedWKReference tag is incorrect. Document is listed in Bibliography with tag B64€OB 2001/07/13EStanleyFWangGObserverH207J EditorialK228L25M7.5.4.1N>Add the word "byte" to read "of each byte is a parity bit...."OTypoP428QCERAcceptedU)change "of each is" to "of each byte is" VAccepted-Clarified€PB 2001/07/13EStanleymn€KRr€PFt€SNu€TTv€XNw€ZNx€\Sy€`Nz€b{€fV|€iA}€jA~€mACACB€nN€oA€sP€vU€{N€}N€FB€O€HB€A€AA€O€AB€N€A€E€BAC€V€A€AB€A€A€JA€O€U€AA€E€A€J€AA€N€A€AA€U€A€A€U€A€N€MB€N€K€A€N€AB€V€N€V€J€N€N€J€A€B€O€N€AA€A€U€O€Vru€PFWangGObserverH208JTechnical, Non-bindingK228L28M7.5.4.1NDelete the paragraph.OShould follow the standard.P429QCERRejectedTThis has been discussed before and also been rejected at that time. Requireing parity complicates unnecessarily the system and adds nothing to it. Intactness of keys is already assured by the HMAC digest. VRejected€QB 2001/07/13EStanleyFWangGObserverH209J EditorialK228L49M7.5.4.2N*Change "key material" to "keying material"OTypoP430QCERAcceptedUDo above change and page 228 on line 32, 37, 49 change "3DES" "3-DES" other occurrences to change it p.227 l.41 , p 320 l. 48, l.59 & 60 VAccepted-Modified€RB 2001/07/13EStanleyFWangGObserverH210J EditorialK229L6M7.5.5N7Change the beginning of the line to read "PKM protocol"O clarificationP431QCERAcceptedVAccepted€SB 2001/07/13EStanleyFWangGObserverH211J EditorialK229L15M7.5.6tv€SNChange 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 clarificationP432QCERAcceptedUby 212V Superceded€TB 2001/07/13EStanleyFWangGObserverH212JTechnical, Non-bindingK229L27M7.6AAdd 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 clarificationP433QCESRaise issue in plenary.uw€TT7We cannot take this decicsion without asking 802 first.VAccepted-Modified€UB 2001/07/13EStanleyFWangGObserverH213JTechnical, 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.P434QCERAccepted-DuplicateT@CRLs are essential for any PKI infrastructure to work properly. VAcceptedW>The handling of CRLs is outside of the scope of this document.€VB 2001/07/13EStanleyFWangGObserverH214J EditorialK230L21M7.6.1.1N:Change "must " to "shall" Make the same change on line 45.OtypoP435QCERAcceptedVAccepted€WB 2001/07/13EStanleyFWangGObserverH215JTechnical, Non-bindingK230L38M7.6.1.2N>Delete the last sentence of the paragraph starting on line 38.O&The SS serial number is being removed.P436QCERAcceptedVAccepted€XB 2001/07/13EStanleyFWangGObserverH216J EditorialK230L47M7.6.1.3vx€XN)Change "OID" to "Object Identifier (OID)"OUsing it for the first time.P437QCERAcceptedVAccepted€YB 2001/07/13ERogerFMarksGMemberH217JTechnical, 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._P727U)Add GF (Galois Field) to the acronym listVAccepted-ModifiedW?The comment itself is obsolete as refers to a deleted paragraph€ZB 2001/07/13ERogerFMarksGMemberH218JTechnical, Non-bindingK231L25M 8.2.1.1.1wy€ZN{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.P728VRejectedWThe comment itself is obsolete as refers to a deleted section. Although similar information is mentioned in 8.2.1.1.1 and 8.2.1.1.2 the spirit of the text in these sections is introductury only.€[B 2001/07/13EStanleyFWangGObserverH219JTechnical, Non-bindingK231L33M 7.6.1.4.1NAChange the 3 "TBD" to "IEEE802", "FBWA", and "IEEE802.16 Root CA"OTBDsP438QCESDiscuss jointly with TG3-4V Superceded€\B 2001/07/13EStanleyFWangGObserverH220I 2001-06-14JTechnical, Non-bindingK231L49M 7.6.1.4.2NCChange the "XX" to "SS" MAke the same change on line 55 and line 58OTBDsP439QCERAccepted-ModifiedxzP€\SChange 'XX' to ' WirelessMAN 'UJChange 'XX' to ' WirelessMAN ' Make the same change on line 55 and line 58VAccepted-Modified€]B 2001/07/13EStanleyFWangGObserverH221JTechnical, BindingK231L51M 7.6.1.4.2N+Change "Root Certificate Authority" to "CA"OIt is not the root.P440QCERAcceptedUDChange "Root Certificate Authority" to " "VAccepted-Modified€^B 2001/07/13EStanleyFWangGObserverH222J EditorialK231L55M 7.6.1.4.2N2Change "shall be included" to "shall be included."O Missing "."P441QCERAcceptedVAccepted€_B 2001/07/13EStanleyFWangGObserverH223J EditorialK231L57M 7.6.1.4.2NRAdd "." to the end of the line and remove the "." from the beginning of next line.OTypoP442QCERAcceptedVAccepted€`B 2001/07/13EStanleyFWangGObserverH224JTechnical, Non-bindingK232L7M 7.6.1.4.3y{€`NDelete 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.P443QCERAcceptedVAccepted€aB 2001/07/13EStanleyFWangGObserverH225J EditorialK232L38M7.6.1.5N*Change RSA public key" to "RSA-Public-Key"O6This is an attribute name and MUST be spelled exactly.P444UDelete line 38VAccepted-Modified€bB 2001/07/13EStanleyFWangGObserverH226JTechnical, Non-bindingK233L2M7.6.1.7ArAdd 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].z|€brO clarificationP445QCERRejectedTIImplies additional options. We are only interested in a subset of RFC2459UXDon't add the paragraph suggested but on p.233 line 8 change "shouldshould" to "should".VAccepted-Modified€cB 2001/07/13EStanleyFWangGObserverH227J EditorialK233L35M7.6.2N,Change "generation.The" to "generation. The"O missing spaceP446QCERAcceptedVAccepted€dB 2001/07/13EStanleyFWangGObserverH228J EditorialK233L41M7.6.2NDelete the word "modem's"OunneededP447QCERAcceptedVAccepted€eB 2001/07/13EPaulFThompsonGMemberH229J 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.O2There is a Section 8.2.1.1 but no Section 8.2.1.2 P675VAccepted€fB 2001/07/13EJayFKleinH230J EditorialK250L4N"Refer to figure 111 and not to 110OMistakeP666{} €fVAccepted€gB 2001/07/13EAntonisFKarvelasH231J EditorialK250L5M 8.2.2.1.1NNThe Figure 110 doesn't show the case where the downlink carrier is continuous.OTo correct the errored link.P469USee comment 230V Superceded€hB 2001/07/13EKenFStanwoodH232J EditorialK250L5M 8.2.2.1.1N#Change "Figure 110" to "Figure 111"OReferring to wrong figureP497USee comment 230V Superceded€iB 2001/07/13EPaulFThompsonGMemberH233JTechnical, 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|~€iAAdd the following text after line 63 on page 288: "Although specific channel bandwidths are recommended by this standard it is acknowlegeded that a specific frequency plan is desirable yet due to the wide variations in country specific regulations no single plan can acommodate all cases. For example the 24.5-26.5 GHz band in Europe is regulated by CEPT dictating specific duplex spacing and rasters. This plan does not match a similar available spectrum allocation in North America."VAccepted-Modified€jB 2001/07/13ERogerFMarksGMemberH234JTechnical, Non-bindingK250L47 A 8.2.2.1.2 @A  NIn "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}€jAgRemove the sentence in line 47 (starting with "The frame..." and ending with "symbol times") Append a new sentence on pg 248 line 57 to the overview section: "The downlink and uplink employ fixed duration frames which are divided each into an integer number of physical slots (PS), where the duration of a PS accomodates four consecutive modulation symbols."gVAccepted-Modified€kB 2001/07/13EKenFStanwoodH235J EditorialK251L53M 8.2.2.1.3N-Change "aretransmitted" to "are transmitted" OtypoP542VAccepted€lB 2001/07/13ELarsFLindhH236JTechnical, 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.P634USee 237V Superceded€mB 2001/07/13EKenFStanwoodH237JTechnical, Non-bindingK251L60M 8.2.2.1.3~€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 oo€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.3€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 s€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.P603AChange the text to: The number of PSs, i (which must be an integer), allocated to a particular burst can be calculated from the downlink MAP (which indicates starting positions of bursts) where 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 integral FEC blocks that fit in the burst and j is the number €mBof 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 occurs, the next codeword should start immediately, with C*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. figures to be modified by Jay.VAccepted-Modified€nB 2001/07/13EKenFStanwoodH238J EditorialK252L58M8.2.2.2(€nNOn 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.P543U9Editor please note that 2nd comment relates to figure 115VAccepted€oB 2001/07/13EKenFStanwoodH239J 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€oAUse Ken's text with a slight modification: "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 PSs) within the frame at the discretion of the BS uplink scheduler."VAccepted-Modified€pB 2001/07/13EJayFKleinH240J EditorialK253L41N*delete the "will" s in "...will both will"OgrammarP667VAccepted€qB 2001/07/13EJayFKleinH241J EditorialK253L50NJThere is a missing reference and should be "in 8.2.2.1.3 or 8.2.4.4.4.4." OClarityP668VAccepted€rB 2001/07/13EKenFStanwoodH242JTechnical, 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.P545VAccepted€sB 2001/07/13EKenFStanwoodH243J EditorialK254L31M8.2.3.2NChange "0-12" to "1-13"OTo match the DIUC table.€sP546VAccepted€tB 2001/07/13EKenFStanwoodH244JTechnical, Non-bindingK254L39M8.2.3.2N(Delete lines 39-40. Delete lines 61-62. O5This particular PHY no longer has a frameless option.P547VAccepted€uB 2001/07/13ERogerFMarksGMemberH245JTechnical, Non-bindingK254L60M8.2.3.3NFix 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.P730U9See 244. Remark has been deleted for this particular PHY V Superceded€vB 2001/07/13EKenFStanwoodH246JTechnical, 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€vUsThe evidence needed for proving the point that better resolution will better enable 64QAM on the uplink is missing.VRejected€wB 2001/07/13EKenFStanwoodH247J 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.P550VAccepted€xB 2001/07/13EKenFStanwoodH248J EditorialK257L28M 8.2.4.2.1NKAdd "in the remainder of the downlink subframe" to the end of the sentence.O9To make it clear where the SS is looking for MAC headers.P549VAccepted€yB 2001/07/13EJayFKleinH249J EditorialK258L46N Replace "all SS" with "all SSs" OGrammarP669VAccepted€zB 2001/07/13EKenFStanwoodH250J EditorialK260L24M 8.2.4.2.4N"Change "1(DIUC=0)" to "1 (DIUC=0)"O missing spaceP551VAccepted€{B 2001/07/13EAntonisFKarvelasH251JTechnical, Non-bindingK260L27M 8.2.4.2.4€{NlThe 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.P471U3Gap=Silence meaning no additional parameters neededVRejected€|B 2001/07/13EKenFStanwoodH252J 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."O.Completeness in defining the predefined DIUCs.P552USlightly modify (missing space...): "The End of DL-MAP Burst Type (DIUC=15) indicates the first PS after the end of the DL subframe. It is well known and shall not be included in the DCD message."VAccepted-Modified€}B 2001/07/13EKenFStanwoodH253J EditorialK261L1M 8.2.4.2.5€}NDelete "For PHY Type = {0,1},"OThese are all the PHY types.P553UChange "For PHY Type = {0, 1}, a number of information elements as defined as in Table 76 ..." to "The information elements as defined in Table 76 ..." VAccepted-Modified€~B 2001/07/13EKenFStanwoodH254J EditorialK261L1M 8.2.4.2.5NYChange "Base Station ID field" to "Number of DL-MAP Elements filed of the DL-MAP message"OCorrectness and clarityP554VAccepted€B 2001/07/13EAntonisFKarvelasH255J EditorialK263L51M 8.2.4.4.1NeThe DIUC numbers for Gap, End of Map and Extended DIUC in Table 79 must agree with those in Table 74.O3There are different DIUC numbers in the two Tables.P472USee 256V Superceded€B 2001/07/13EKenFStanwoodH256J EditorialK263L51M 8.2.4.4.1NOn page 263, line 51 add a row containing "13 | reserved" On page 263, line 52 change "13" to "14" On page 263, line 53 change "14" to "15" On page 263, delete the row at line 56OConsistence with Table 74P555VAccepted€B 2001/07/13EKenP€FStanwoodH257J EditorialK263L61M 8.2.4.4.2NChange "exits" to "exist"OgrammarP556AChange the following: "Since there exists some optional modulation and FEC schemes that can be implemented at the subscriber station, there must exist some method for identifying the capability to the base station (i.e., including the highest order modulation supported, the optional FEC coding schemes supported, interleaving type supported, and the minimum shortened last codeword length supported). This information shall be communicated to the base station during the subscriber registratio€Bn period." to "Since there are optional modulation and FEC schemes that can be implemented at the subscriber station, a method for identifying the capability to the base station is required (i.e., including the highest order modulation supported, the optional FEC coding schemes supported, interleaving type supported, and the minimum shortened last codeword length supported). This information shall be communicated to the base station during the subscriber registration period." VAccepted-Modified€B 2001/07/13EKenFStanwoodH258JTechnical, Non-bindingK263L64M 8.2.4.4.2N$Delete "interleaving type supported"O&This PHY does not support interleavingP557VAccepted€B 2001/07/13ELarsFLindhH259JTechnical, Non-bindingK264L15M 8.2.4.4.3NIn order to clarify input data ordering, and initialisation update figure 120. Also delete the enable function which is not relevant in the figure and update the text in the figure. New figure is submitted in 802.16.1c-01/31. €OClearificationP630VAccepted€B 2001/07/13EKenFStanwoodH260J EditorialK265L7M 8.2.4.4.4NNChange "The coding rate is 2/3." to "The coding rate of the inner BCC is 2/3."OClarityP558VAccepted€B 2001/07/13EAntonisFKarvelasH261JTechnical, Non-bindingK265L11M 8.2.4.4.4NwThe standard must have an example or reference for using the parity code for error correction employing a soft decoder.OTo remove ambiguity.P473UsIt is important to define clearly the encoder structure. The decoder can be proprietary and differ between vendors.VRejected€B 2001/07/13EKenFStanwoodH262J EditorialK265L44M 8.2.4.4.4.1NbShould page 265 line 44, page 266 line 21, page 285 line 1 and page 285 line 20 be header level 7?P559U`This seems to be an IEEE pure editorial issue - number of levels allowed in a standard document.VRejected€B 2001/07/13EKenFStanwoodH263J EditorialK265L46M 8.2.4.4.4.1N%Change "in the same" to "is the same"OtypoP560VAccepted€B 2001/07/13ELarsFLindh€H264JTechnical, Non-bindingK266L1M 8.2.4.4.4.1AInsert the word randomized in the sentence in order to clarify this fact. The sentence will then read: "When a number of randomized MAC messages .. " On Line 6 delete A2 On line 7 Change A3 to: "RS encode the K bytes and append the R parity bytes On Line 8 Change A4 to: "Serialize the bytes and transmit them to the inner coder or the modulator MSB first. Make the same corrections for the Shortened Lats Codeword Operation on page 267ARandomization is defined in a previous section. It can be very confusing to mention randomization here because the reader can get impression that it should be performed twice. It also extremely important in every serialization operation to indicate which bit is to be transmitted first. The encoding procedure for the fixed codeword operation can produce long sequencies of unrandomized constant data which effectively will transmit a sinewave. When this is long it might be a problem for theL€P631AInsert the word randomized in the sentence in order to clarify this fact. The sentence will then read: "When a number of randomized MAC messages .. " On Line 6 delete A2 and renumber accordingly On line 7 Change A3 to: "RS encode the K bytes and append the R parity bytes On Line 8 Change A4 to: "Serialize the bytes and transmit them to the inner coder or the modulator MSB first. Make the same corrections for the Shortened Last Codeword Operation on page 267VAccepted-Modified€B 2001/07/13EKenFStanwoodH265J EditorialK266L41M 8.2.4.4.4.1NdOn page 266 line 41 and line 47, and on page 273, line 1, the "hex" in "FFhex" should be subscriptedO$consistency with rest of PHY sectionP561VAccepted€B 2001/07/13EKenFStanwoodH266JTechnical, Non-bindingK267L13M 8.2.4.4.4.1NEliminate lines 13-22.€B equalizator. €ALine 13 states.."When the number of bytes (M) entering the FEC process is greater than or equal to K bytes,..", but the preface to this (p266, lines 52-56) describe how to deal with the full codewords, so, M will never be greater or equal to K. It appears that these lines were cut-and-pasted from p266, lines 14-19, but they do not make sense in the context of the description at the bottom of p266. Another possible resolution is to change the paragraph at the bottom of page 266.P604U(1) Delete line 1 on page 267 (2) Delete steps A1 and A2 (lines 4,5 page 267) and renumber following steps accordingly (3) Change language in A4 according to comment 264 (4) Delete lines 12 to 22 page 267 VAccepted-Modified€B 2001/07/13EKenFStanwoodH267JTechnical, Non-bindingK267L34M 8.2.4.4.4.2NrAdd a sentence: A system is only required to implement the decoder for the type 2 inner code for QPSK modulation.|€AA trellis decoder to decode this code for 16 QAM and 64 QAM is quite complex. However, since the inner code is fairly low-rate, it is not likely to be useful for a higher order modulation format. This code is primarily to provide a very robust link using QPSK. Since the current specification requires 16 QAM on the downlink, and no exception is mentioned, it implies that a system must implement a decoder for the convolutional code using 16 QAM. Similarly, if a manufacturer chooses to iBqmplement 64 QAM, the spec could be interpreted to mean that the trellis decoder must be implemented for 64 QAM. _P600€AThe group would like to restrict the use of the type 2 code with QPSK only. This means that the code cannot be used in combination with 16QAM or 64QAM. Furthermore for clarity it is emphasized that QPSK is not required to use this code in all cases except in the case of the control channel (DIUC=0) where it is mandated that QPSK shall use a type 2 code. Editor is required to come up with correct "standard wording" (i.e., "shall").VAccepted-Modified€B 2001/07/13ELarsFLindhH268JTechnical, Non-bindingK267L45M 8.2.4.4.4.2NNInsert a figure explaining the BCC. The figure is submitted in 802161c-01_31. P635UAdd a figure (using Lars's input) after table 81 (page 267). Insert the following text (before the figure): "In figure XXX, the exact encoding parity equations are described."VAccepted€B 2001/07/13EKenFStanwoodH269JTechnical, Non-bindingK272L45M 8.2.4.4.5N9Add a row containing "BCC Code Type | 1 | (24,16)"5€O8For completeness and consistency with section 8.2.4.2.3.P562VAccepted€B 2001/07/13EKenFStanwoodH270JTechnical, Non-bindingK272L48M 8.2.4.4.5NTOn lines 48 and 50, change "Manufacturer specific" to "Deployment scenario specific"OsThese thresholds cannot be manufacturer specific since there is 1 value that must be used for all SSs on a channel.P563VAccepted€B 2001/07/13EKenFStanwoodH271J EditorialK272L59M 8.2.4.4.6N,Change "initializatioin" to "initialization"OspellingP564VAccepted€B 2001/07/13EKenFStanwoodH272JTechnical, Non-bindingK272L62M 8.2.4.4.6NChange "could be" to "shall be"OIt must be a single burst.P565VAccepted€B 2001/07/13EKenFStanwoodH273JTechnical, Non-bindingK273L13M 8.2.4.4.7NCEliminate sentence starting with "The CAZAC sequence is rotated..."r€AeTables 88 and 89 already define the required I and Q values. The sentence in question seems to confuse the issue by implying that the preamble sequence should be rotated 45 degrees from the I and Q values defined in tables 88 and 89. Another way of clarifying would be to state "The CAZAC sequence is rotated +45 degrees (as shown in tables 88 and 89)..."eP605AChange the text in lines 7-16 to the following: Table 87 through Table 89 define the preambles for the different downlink burst types. These preambles are based upon CAZAC (constant amplitude zero auto-correlation) sequences [B52]. The original sequences are rotated +45 degrees and transmitted so that the constellation points of the preamble coincide with the outmost constellation points of the modulation scheme in use. The frame start preamble is always at the first part of a downlink fr€Bame and consists of a 32 symbol preamble (Burst Preamble 1), which is generated by repeating twice a CAZAC sequence of length 16 symbols. In the case of the TDMA mode on a downlink, user bursts are transmitted with a shortened preamble of 16 symbols (Burst Preamble 2), which is generated with a single length 16 CAZAC sequence. Change the text on page 286 line 48-52 to: The preamble is based upon an integer number of repetitions of the following length 16 CAZAC sequence (constant amplituC\de zero auto-correlation) sequence [B52]. The original sequence is rotated +45 degrees and transmitted so that the constellation points of the preamble coincide with the outmost constellation points of the modulation scheme in use. Table 98 defines the bit sequence for the base preamble. The number of repititions is defined by the base station. 8VAccepted-Modified€B 2001/07/13EKenFStanwoodH274JTechnical, Non-bindingK280L54M 8.2.4.4.10€NAdd a subsection: 8.2.4.4.10 Spectral Inversion. The transmitted downlink signal must compensate for any spectral inversion in the transmit radio, such that there is no inversion at the antenna port.AThe spectrum of the signal may be inverted depending on the details of the up conversion within the radio. This comment proposes that the downlink signal compensate for the inversion if the radio design causes it. This can be done simply by interchanging the "I" and "Q" signals in the baseband processing. Without this requirement, the SS would need to determine the spectral inversion of the received signal during the registration process.P602USee 275V Superceded€B 2001/07/13ELarsFLindhH275JTechnical, Non-bindingK280L60M 8.2.4.4.9NInsert a section defining the modulated signal as S(t) = I(t)cos(2pifct) - Q(t)sin(2pifct) where I(t) and Q(t) are the filtered baseband signals and fc is the carrier frequency. P636€AAdd a subsection: 8.2.4.4.10 Spectral Inversion. The transmitted downlink signal must compensate for any spectral inversion in the transmit radio, such that there is no inversion at the antenna port as defined by the following equation: S(t) = I(t)cos(2pifct) - Q(t)sin(2pifct) where I(t) and Q(t) are the filtered baseband signals, S(t) is the transmitted signal at the antenna port and fc is the carrier frequency. Editor please note that "pi" actualy means the mathematical constant 3.1B&4... and fc should be subscripted VAccepted-Modified€B 2001/07/13ELarsFLindhH276JTechnical, Non-bindingK281L10M 8.2.4.4.10NGIn the case of BCC inner code the information byte length must be even P632UInsert on pg. 265 line 8 (after "The coding rate is 2/3."): Note: The number of information bytes must be even in this case. Insert on pg. 267 line 45: The number of information bytes must be even as the BCC code operates on byte pairs.VAccepted-Modified€B 2001/07/135€EKenFStanwoodH277JTechnical, Non-bindingK282L50M8.2.5.3N;delete the sentence that begins "Consequently the first..."OThis is not at all necessary.P566U5Remove the short sentence only ending with "...of 0."VAccepted-Clarified€B 2001/07/13EAntonisFKarvelasH278JTechnical, Non-bindingK283L36M8.2.5.3ABased on Table 96, which describes the Uplink Map Information Elements, there is the Request IE, which can have as Connection ID either the Basic CID of the SS or the specific traffic CID of the SS (polling is done on either an SS or connection basis). But for each entry (UIUC) of the Table 96 there is a specific burst descriptor, which describes the physical characteristics (modulation, FEC) of this UIUC. This means that all the SSs must send the Bandwidth Request header with a specific m€Bodulation/FEC that is described from the corresponding burst descriptor of the UIUC=1 (Request IE). But the last conflicts with the section 6.2.6.4.1, figure 37 that says that the SS sends the unicast Bandwidth Request header using the operational burst profile. The standard must explicitly notes the following: When the BS executes unicast polling then the polled SS sends a Bandwidth Request header along with data, using the operational burst profile of the SS and not the burst descriptorC of the Request IE (UIUC=1). When the BS executes broadcast or multicast polling then the SSs send the Bandwidth Request headers in the BW Request contention slots region using the burst descriptor of the UIUC=1 (Request IE). OTo remove ambiguity.P482€A On page 117, line 44 add the following paragraph: "A GPC SS may use Request IEs that are broadcast, directed at a multicast polling group it is a member of, or directed at a unicast connection ID that represents a service flow belonging to that SS. In all cases, the Request IE burst profile is used, even if the BS is capable of receiving the SS with a more efficient burst profile. To take advantage of a more efficient burst profile, the SS should transmit in a Data Grant IE directed at Ba unicast connection ID that represents a service flow belonging to that SS. Because of this, unicast polling of a GPC SS would normally be done by allocating a Data Grant IE directed at a unicast connection ID that represents a service flow belonging to that SS. Also note that in a a Data Grant IE directed at a unicast connection ID that represents a service flow belonging to a GPC SS, the SS shall only make bandwidth requests for the indicated connection." On page 118, line 62 add the€C following paragraph: "A GPSS SS may use Request IEs that are broadcast, directed at a multicast polling group it is a member of, or directed at its Basic connection ID. In all cases, the Request IE burst profile is used, even if the BS is capable of receiving the SS with a more efficient burst profile. To take advantage of a more efficient burst profile, the SS should transmit in a Data Grant IE directed at its Basic CID. Because of this, unicast polling of a GPSS SS would normally be Ddone by allocating a Data Grant IE directed at its Basic CID. Also note that in a Data Grant IE directed at its Basic CID, the SS may make bandwidth requests for any of its connections." VAccepted-Modified€B 2001/07/13EKenFStanwoodH279J EditorialK283L49M8.2.5.3N;On lines 49, 52, 55, and 57 add a space before "assignment"OtypoP567VAccepted€B 2001/07/13EKenFStanwoodH280J EditorialK283L65M8.2.5.3NChange "any" to "NA"O,Consistency with the first row of the table.P568/€VAccepted€B 2001/07/13EAntonisFKarvelasH281JTechnical, Non-bindingK284L2M8.2.5.4AoInsert the following text : "For Bandwidth Requests transmitted in the Bandwidth Request Contention Slots the Uplink Transmission Convergence (TC) Sublayer doesn't need to have the TC pointer byte because the Bandwidth Request header is only 6 bytes which is the minimum information block length for the Reed Solomon. So it fits exactly to one Reed Solomon codeword."oOTo save uplink bandwidth .P480UThe bandwidth savings is small (1 or 2 bytes per frame = 1-2/5000 PSs) compared to some (minor) complexity handling this special case.VRejected€B 2001/07/13EKenFStanwoodH282JTechnical, Non-bindingK286L50M 8.2.5.5.3NJEliminate the sentence starting with .. "The CAZAC sequence is rotated..."€ANTable 98 already defines the required I and Q values. The sentence in question seems to confuse the issue by implying that the preamble sequence should be rotated 45 degrees from the I and Q values defined in table 98. Another way of clarifying would be to state "The CAZAC sequence is rotated +45 degrees (as shown in table 98)..."NP606USee 273V Superceded€B 2001/07/13EKenFStanwoodH283J EditorialK286L52M 8.2.5.5.3N'Change "modulation" to "the modulation"OgrammarP569VAccepted€B 2001/07/13EKenFStanwoodH284JTechnical, Non-bindingK287L56M 8.2.5.5.6NAdd a subsection: 8.2.5.5.6 Spectral Inversion. The transmitted uplink signal must compensate for any spectral inversion in the transmit radio, such that there is no inversion at the antenna port.€AThe spectrum of the signal may be inverted depending on the details of the up conversion within the radio. This comment proposes that the uplink signal compensate for the inversion if the radio design causes it. This can be done simply by interchanging the "I" and "Q" signals in the baseband processing. Without this requirement, the BS (which could be listening to SSs from several different vendors) would need to determine the spectral inversion on a burst-by-burst basis.P601Add a subsection: 8.2.5.5.6 Spectral Inversion. The transmitted uplink signal must compensate for any spectral inversion in the transmit radio, such that there is no inversion at the antenna port as defined by the following equation: S(t) = I(t)cos(2pifct) - Q(t)sin(2pifct) where I(t) and Q(t) are the filtered baseband signals, S(t) is the transmitted signal at the antenna port and fc is the carrier frequency. Editor please note that "pi" actualy means the mathematical constant 3.14...!€B" and fc should be subscripted VAccepted-Modified€B 2001/07/13ELarsFLindhH285JTechnical, Non-bindingK288L10M 8.2.5.5.6NGIn the case of BCC inner code the information byte length must be even P633USee 276V Superceded€B 2001/07/13EAntonisFKarvelasH286JTechnical, Non-bindingK288L28M 8.2.5.5.6A5If the final decision is the Transmission Convergence sublayer to be selectable on/off for the SS transmit, then you must somewhere define this parameter. A proper place is the 11.1.1.2 UCD Burst Profile Encodings table, so you must add a new entry : Transmission Convergence sublayer / 0=enabled, 1=disabled 5OThe Transmission Convergence sublayer can be enabled/disabled but there is not defined in the standard the parameter that controls that.P474Z€A(1) Delete table entry on page 288 line 28, "Transmission Convergence Sub layer" (2) On page 262, line 32, replace "is segmented" with "shall be segmented" (3) On page 262, line 34, replace "pointer byte is added" with "pointer byte shall be added" (4) Delete contents of section 8.2.5.4 and replace with "The uplink transmission convergence sub-layer operation shall be identical to the downlink transmission convergence sub-layer operation as described in section 8.2.4.3 ."VAccepted-Modified€B 2001/07/13EAntonisFKarvelasH287JTechnical, Non-bindingK288L28M 8.2.5.5.6€ABased on Table 99 the Transmission convergence sublayer can be selectable on/off. I believe that the Transmission convergence sublayer must not be an optional Uplink Physical Layer parameter for the following reasons: * It helps the receiving BS MAC layer to identify the beginning of each MAC PDU * In any case the SS transmitter needs to have a mechanism to segment the uplink payload into blocks of data designed to fit into the proper codeword size BIf the final decision is the Transmission convergence sublayer to be selectable on/off, then the Tranmsission convergence capability must be a parameter of the SS Capabilities Encoding. Specifically in this case insert a new section "11.4.5.2.5 10-66 GHz PHY SS Uplink Transmission convergence sublayer" that will define for each SS if it supports or not the Transmission convergence sublayer.wOTo remove ambiguity.P484USee 286V Superceded€B 2001/07/13EAllanFKleinH288€JTechnical, BindingK288L57M8.2.6NAdd additional channelization options to address 10.5 GHz applications. 7 MHz and 3.5 MHz should be included as they are frequently used by products already operating in this frequency band. AChannel sizes of 20 MHz and greater are not viable for typical frequency allocations at 10.5 GHz, where the overall 150 MHz band is sub-divided for use among many different operators- typically in tranches of 30 MHz. Since the standard is supposed to address applications from 10-66 GHz, at least one of the mandatory channelizations should be suitable for 10. 5 GHz applications. The specific channelizations and baud rates were submitted as comments to letter ballot # 3.P663n€AThe fact that the 802.16 (TG1) standard addresses 10-66 GHz does not mean that ANY spectrum oppurtunity could be used for LMDS-like services (i.e., 20 MHz vs. 500 MHz). The example given by the comment is more suitable for the 802.16a (TG3) case which addresses such spectrum oppurtunities in a better way. The fact that 10 GHz is a lower limit to 802.16 (TG1) is more of propagation aspects and suitability of the PHY. Furthermore, please note the actual language of section 8.2.6 : "...otheBr combinations of channel size, symbol rate, roll-off factor, and frame duration could be made, but interoperability will not be guaranteed in these cases." VRejected€B 2001/07/13EPaulFThompsonGMemberH289JTechnical, BindingK289L32M8.2.7.3NnReference original Comment 412. Change the word "should" to "shall" on this Line and also on Lines 33 and 37.€OAn Interoperability Standard must be explicit about a minimum set of requirements. If, as it was said in the resolution of Comment 412, Power Control is a "core part of the PHY," then the use of "shall" seems appropriate.P677Ar(1) On line 33 replace "should" with "shall" (2) On line 37 replace the sentence "The power control algorithm..." with the following: "A power control algorithm shall be designed to support power attenuation due to distance loss or power fluctuations at rates of at most 10 dB/second with depths of at least 40 dB. The exact algorithm implementation is vendor specific."rVAccepted-Modified€B 2001/07/13EKenFStanwoodH290JTechnical, Non-bindingK289L48M8.2.8NUChange " in the vicinity of 24 to 31 GHz" to "in the frequency range of 24 to 31 GHz"OThe word "vicinity" is ambiguous. If the intent is to provide some margin in the frequency range, it should be stated explicitly, for example "20 to 35 GHz".P598€UUChange " in the vicinity of 24 to 31 GHz" to "in the frequency range of 24 to 32 GHz"VAccepted-ModifiedWiAgree with Ken's observation yet extend the upper limit to 32 GHz covering a potential ETSI related band.€B 2001/07/13EKenFStanwoodH291JTechnical, Non-bindingK290L8M8.2.8NAdd the following text to the "Tx Symbol Timing Accuracy" section: The Tx symbol timing accuracy shall be within +/- 15 ppm of its nominal value (including aging and temperature variations).OProvides a bound on the symbol timing error that the SS receiver has to deal with since the symbol clock on the SS has to be locked to the BS symbol clock. P596VAccepted€B 2001/07/13EJayFKleinH292JTechnical, Non-bindingK290L24[€AFIn Table-101 and Table-102 (line 61...), the column entry corresponding to Modulation accuracy must be changed to numbers reflecting similar operating BER. For example: 20% (QPSK) , 6.7% (QAM-16), 2.9% (QAM-64) - Ideal Receiver without Equalizer 10% (QPSK), 3.3% (QAM-16), 1.5% (QAM-64) - Ideal Receiver with Equalizer FOThe current EVM numbers in the spec are inconsistent (i.e they do not lead to the same raw BER for different constellations). Also, they do not distinguish between equalizable and non-equalizable impairments (see other comment from the submitter) P665€AAccept the recommend change with the following numbers and remarks: 12% (QPSK) , 6% (16QAM), 2% (64QAM) (Note: Measured with an Ideal Receiver without Equalizer, all transmitter impairments included) 10% (QPSK), 3% (16QAM), 1.5% (64QAM) (Note: Measured with an Ideal Receiver with an Equalizer, linear distortion removed) Note: Tracking loop bandwidth is assumed to be between 1% to 5% optimized per phase noise characteristics. The tracking loop bandwidth is defined in the following way. BA lowpass filter with unity gain at DC and frequency response H(f), has a tracking loop (noise) bandwidth (BL), defined as the integral of | H(f)| squared from 0 to the sampling frequency. The output power of white noise passed through an ideal brick wall filter of bandwidth BL will be identical to that of white noise passed through any lowpass filter with the same tracking loop (noise) bandwidth. Editor note: The "L" in BL should be subscripted VAccepted-Modified€B 2001/07/13€ELarsFLindhH293JTechnical, Non-bindingK290L24M8.2.8N}Change EVM values to 12% QPSK 6% 16-QAM 2% 64-QAM assuming a receiver tracking loop bandwidth of 5% of the symbol rate P643USee 292V Superceded€B 2001/07/13ERogerFMarksGMemberH294JTechnical, Non-bindingK290L33M8.2.8NClarify ambiguity in "at least 28 dBW/MBaud". The phrase suggests that dB should scale linearly with symbol rate, but you really mean that the absolute power does.O Ambiguity.P731UReplace "at least 28 dBW/MBaud (i.e., 15 dBW = 15 dBm for 20 MBaud) (measured at antenna port)" with "at least -15 dBm (measured at antenna port)"VAccepted-Modified€B 2001/07/13EAntonisFKarvelasH295JTechnical, Non-bindingK290L49M8.2.8€AIn Table 102 the standard says about the Tx burst timing accuracy that "Must implement corrections to burst timing with an accuracy of +/- 0.25 of a symbol and a resolution of +/- 0.125 of a symbol." But the RNG-RSP message from BS has a Tx timing offset adjustment which is a signed 32-bit, units of ? symbols. What is the purpose of the above resolution of +/- 0.125 of a symbol? OTo remove ambiguity.P476AReplace "Must implement corrections to burst timing with an accuracy of +/- 0.25 of a symbol and a resolution of +/- 0.125 of a symbol." with "Must implement corrections to burst timing in steps of +/- 0.25 of a symbol with step accuracy of +/- 0.125 of a symbol"VAccepted-Modified€B 2001/07/13ELarsFLindhH296JTechnical, Non-bindingK290L61M8.2.8N}Change EVM values to 12% QPSK 6% 16-QAM 2% 64-QAM assuming a receiver tracking loop bandwidth of 5% of the symbol rate P644USee 292V Superceded€B 2001/07/13EKenFStanwoodH297€JTechnical, Non-bindingK291L15M8.2.8NCChange "64-QAM: -76 + 10log 10 (B)" to "64-QAM: -74 + 10log 10 (B)"A&For QPSK and 16-QAM the threshold difference between 1E-3 and 1E-6 is 4 dB, for 64-QAM it is shown as 3 dB. Since 64-QAM is more sensitive to impairment, it needs an extra 1 dB between 1E-3 and 1E-6 compared to QPSK and 16-QAM. Starting with 1E-3 @ -79, adding (4+1) gives -74 as shown above.&P599VAccepted€B 2001/07/13ELarsFLindhH298JTechnical, Non-bindingK291L22M8.2.8NBChange Maximum Transition time from Tx to Rx and Rx to Tx to 20us.O2 us is difficult to achieve for half-duplex terminals. It is not a critical value for terminals can always be scheduled to not receive data immediately before transmitting. P640UFChange numbers to "2 uSec (TDD), 20 uSec (FDD, Half-duplex terminal)" VAccepted-Modified€B 2001/07/13EKenFStanwoodH299JTechnical, Non-bindingK291L25M8.2.8R€AAdd the following note: The interfering source shall be a continuous like modulated signal. The spectral mask of the interfering signal will depend on local regulatory requirements. For example, where ETSI regulations apply, the 1st and 2nd adjacent interference test shall be performed with the interfering signal conforming to the ETSI Type C spectral mask. In cases where alternative masks are permitted, the interfering signal shall conform to the ETSI Type B spectral mask. OLTo clarify the nature of the interfering signal and its spectral occupancy. P597€AAdd the following note to the end of table 103 (with reference to 1st adj. channel interference and 2nd adj. channle interference items in the table): Note: The interfering source shall be a continuous, same modulation as the interfered signal. The spectral mask of the interfering signal will depend on local regulatory requirements. For example, where ETSI regulations apply, the 1st and 2nd adjacent interference test shall be performed with the interfering signal conforming to the ETSIB Type C spectral mask. In cases where alternative masks are permitted, the interfering signal shall conform to the ETSI Type B spectral mask. VAccepted-Modified€B 2001/07/13EKenFStanwoodH300J EditorialK292L3M 8.2.8.1.1N#Change "defined No" to defined. No"Omissing periodP570VAccepted€B 2001/07/13ERogerFMarksGMemberH301JTechnical, Non-bindingK292L12M8.28.1.1€NDefine "Tap Number, "Tap Delay, and "Tap Amplitude" by providing a reference to a model which makes use of these parameters or a set of equations that illustrated their meaning.O0These terms are useless unless they are defined.P732AZAdd the following after table 104: The channel model can be expressed as: H(jw) = C1*exp(-j*wT1)+C2*exp(-j*wT2)+C3*exp(-j*wT3)+... where C1,C2,C3... are tap amplitudes (complex) and T1,T2,T3... are tap delays Furthermore, add to the end of line 6: For example, if B=20 MBaud the resulting tap delays in table 104 will be 0, 20 and 40 nSec.ZVAccepted€B 2001/07/13EPaulFThompsonGMemberH302JTechnical, BindingK293L32M 8.2.8.2.2NThis Comment relates to original Comment 426. I agree with the resolution of this comment, but the specific text described in the resolution (about the 802.16.2 mask) did not get into the document.€ASection 1.2 states: "This Standard is intended to enable...deployment of..interoperable multivendor broadband wireless access products." This is really the whole justification for the existence of the TG1 Standards effort. I believe that the Standard should take a position on the minimum mask that is acceptable for interoperability purposes and I believe that an appropriate mask is the one receommended by Coexistence considerations.P678UyIn Session #13 it was identified that the reference to the TG2 draft is wrong as it is not applicable as a channel mask. VRejected€B 2001/07/13EJayFKleinH303JTechnical, Non-bindingK293L62€AAfter line 62, add the following lines: To quantify Tx performance, EVM is measured under the following conditions: 1). Ideal Receiver, without equalizer, with a PLL of noise bandwidth 1% of the baud rate. 2). Ideal Receiver, with equalizer, with a PLL of noise bandwidth 1 % of the baud rate Add a definition of Noise Bandwidth. A lowpass filter with unity gain at DC and frequency response H(f), has a noise bandwidth (BL), defined as the integral of | H(f)| squared from 0 to the samplinBg frequency. The output power of white noise passed through an ideal brick wall filter of bandwidth BL will be identical to that of white noise passed through any lowpass filter with the same noise bandwidth. Furthermore, the measurement period should not include a preamble. ]€AfReason: In order to guarantee interoperability, the Transmitter impairments need to be specified in an non ambiguous way. The changes above measure: 1. Tx impairments due to filtering errors - which can be removed by equalization 2. Tx impairments due to self noise The PLL is specified to ensure that phase noise does not distort the EVM measurements. fP664USee 292V SupercededWThe group felt that the preamble portion in the transmission is a small part of a 1/4 of a frame and won't influence the EVM measurment.€B 2001/07/13EKenFStanwoodH304J EditorialK294L38M 8.2.8.2.3NFloating and Figure numbering is messed up here. Figure 134 should come after Figures 130 and 133. There are ghost Figures 131 and 132 that don't appear, but affect the Figure numbering and appear in the table of contents as titleless figures.P5711€URelocate figure 134 nearby section 8.2.8.2.3 As figures 131 and 132 are missing please renumber figures 134, 129, 130, 133 accordingly (by this order) VAccepted-Modified€B 2001/07/13EJayFKleinH305J EditorialK294L40N8Renumber figure 134 and move nearby to section 8.2.8.2.3OClarityP670USee 304V Superceded€B 2001/07/13ERogerFMarksGMemberH306J EditorialK294L57M 8.2.8.2.3NnFix order of figures in the range 129-134. Renumber to the range 129-132 (131 and 132 are not currently used)OCorrect editorial error.P733USee 304V Superceded€B 2001/07/13EAntonisFKarvelasH307JTechnical, Non-bindingK298L7M9.2.2NAdd a new line : f) Service Flow Encodings (except Service Flow Identifier and Connection Identifier) (see 11.4.11) g) Convergence Sublayer Parameter Encodings (see 11.4.16) €A The Configuration File has the Service Flow Encodings as referred to the scope of the Service Flow Encodings. Also has the Convergence Sublayer Parameter Encodings as referred in section 11.4.16 : "Configuration files will contain parameter information used by the convergence sublayers." P490VRejectedWzService flow info is not included in config file. The config file will be removed from the scope of service flow encodings€B 2001/07/13ECarlFEklundH308JTechnical, Non-bindingK300L22M10.1€AAdd a rows | BS | UCD Transition| The time the BS must wait after repeating a UCD message with an incremented Configuration Change Count before issuing a UL-MAP message referring to burst descriptors defined in that UCD message| 2ms | | | | BS | DCD Transition| The time the BS must wait after repeating a DCD message with an incremented Configuration Change Count before issuing a DL-MAP message referring to burst descriptors defined in that DCD message| 2ms | | | P615VAccepted€B 2001/07/13EKenFStanwoodH309J EditorialK300L24M10.1NVTo the description in the Maximum Value column, add "beyond the Allocation Start Time"OclarityP572VAccepted€B 2001/07/13ECarlFEklundH310J EditorialK301L7M10.1Nline 7 Delete word 'Minimum' in time reference column. line 14 Delete word 'maximum' in time reference column. Move value 30s from Minimum value column to Maximum value columnO!Current wording is very confusingP608c€U6Do portion for line 7 Comment on line 14 superceeded. VAccepted-Modified€B 2001/07/13EKenFStanwoodH311JTechnical, Non-bindingK301L14M10.1AOn page 301, line 14 change the name of "SS Configuration" to "T13" On page 301, line 14 change the time Refernce field to read " The maximum time allowed for an SS, following receipt of a REG-RSP message to send a TFTP-CPLT message to the BS." On page 301, line 14 change the Minimum and defalut columns to "15 min" On page 302, line 28 change "REG-REQ" to "SBC-REQ" On page 302, line 24 change the Minimum and Default columns to "300 ms"€AWhen we changed the order of initialization we added SS Configuration whch is really a timer, but did not rectify it with the old timer T9 whose purpose was to ensure an SS didn't get stuck forever trying to TFTP its config file. The 15 min that T9 had was to allow for many retries. The 30 seconds is too short. Now the SBC follows ranging, not config file download and registration, so T9 must be much shorter.P573AOn page 301, line 14 change the name of "SS Configuration" to "T13" On page 301, line 14 change the time Refernce field to read " The time allowed for an SS, following receipt of a REG-RSP message to send a TFTP-CPLT message to the BS." On page 301, line 14 change the Minimum and defalut columns to "15 min" On page 302, line 28 change "REG-REQ" to "SBC-REQ" On page 302, line 24 change the Minimum and Default columns to "300 ms"VAccepted-Modified€B 2001/07/13EKenFStanwoodH312J EditorialK301L20M10.1€NwPut the Timers in numerical order, and group them together. In particular change the order of T12 and T14 on page 302.OClarityP574VAccepted€B 2001/07/13EAntonisFKarvelasH313J EditorialK302L39M10.1NEChange the "Wait for RSX-RVD Timeout " to "Wait for DSX-RVD Timeout".OErroneous text.P493VAccepted€B 2001/07/13EStanleyFWangGObserverH314JTechnical, Non-bindingK303L24M10.2N}Change the values for Authorization Grace Time to "3 hr (10,800 s)" and "3 days (259,200 s)" minimum value and default value.AnKey Request messges are used to imply the receiving of a new AK. Authorization Grace Time MUST be long enough (significantly longer than TEK Grace Time) to guarantee at least one Key Request message is sent. Otherwise, the older AK may expire before the newer one is acknowledged, which leaves the SS without authorization and will be forced to redo network entry.nP448VRejected€B 2001/07/13ERogerFMarksGMemberH315JTechnical, Non-bindingK303L28X ‚ÂĂłƂǂȂɂʂ˂̂͂΂ςЂт҂ӂԂՂւׂ؂قڂۂ܂݂ނ߂ႀ₀む䂀傀悀炀肀邀ꂀ낀삀킀€M 8.2.8.2.1.2N{Note: the comment applies to D2. It is Scott Marin's Comment 1077 from LB#3 and was not previously considered.} Delete para 8.2.3.2.1.1 and 8.2.3.2.1.2 or change "30" to "42" in 8.2.8.2.1.2.AConsider deleting or changing the limit. The limit serves no useful purpose in the 802.16 spec and can be deleted (if deleted then also consider deleting para 8.2.3.2.1.1). Alternatively, the limit should be replaced with text referring the reader to the applicable regulatory authority and the 802.16 co-existence practice. Finally, it the group still feels that a specific limit is necessary, then I recommend a limit of +42 dBW/MHz which matches the US FCC limit for 28 GHz LMDS subscriber t€Berminals (CFR47 101.113 see note 9 in table). If the group still insists that a limit of +30 dBW/MHz be used then, I recommend that +30 dBW/MHz be a limit for clear-sky condistions and that up to +42 dBW/MHz be permitted under faded conditions. Note, current technology of 1 watt amplifiers and 42 dB Gain antennas for T1 links about 1MHz wide can easily produce an EIRP spectral density of +42 dBW/MHz, which subtantially exceeds the proposed limit of 30 dBW/MHz. Reducing the link margin by 1C2 dB (42 - 30) has a big impact on coverage area especially in rain zones with high rain rates. Note that +42 dBW/MHz is normally used only in faded conditions and that SSs normally operate at much lower EIRP levels during clear sky conditions.P734UESeveral discussions in previous sessions have dealt with this issue. VRejected€B 2001/07/13EStanleyFWangGObserverH316JTechnical, Non-bindingK303L47M10.2€NzDelete lines 47-52 and the 1st sentence of the paragraph starting line 54. Also delete the word "recommended" on line 56.O0No more table for recommened operational ranges.P449VAccepted€B 2001/07/13ERogerFMarksGMemberH317JTechnical, Non-bindingK304L30 A10.3.1.1@A  AChange: "A Physical Slot (PS) is defined as the time to equal the duration of 4 modulation symbols at the symbol rate of the downlink transmission." to "A Physical Slot (PS) is defined as four consecutive modulation symbols." Definitions belong in Clause 3. Can this one be moved there?O3A PS is a chunk of symbols, not a duration of time.P735UZDo NOT make the above change Instead make page 33 line 35 change "granularity" to "time"VAccepted-ModifiedWPS is a PHY dependent unit of time. As such the actual defintion is in the PHY section. 'unit of granularity' is a truely wierd redundant concept.€B 2001/07/13ERogerFMarksGMemberH318J Editorial_€K306L5M11N1Give numbers and captions to tables in Clause 11.O}The whole TLV section has a lot of un-numbered, un-captioned tables that are not referenced in the text. This gets confusing.P736VAcceptedWKeep the editor busy ; ) €B 2001/07/13ELarsFLindhH319JTechnical, Non-bindingK306L16M11.1.1.1NXChange "Uplink center frequency (KHz)" to Uplink center frequency in units of 250 KHz.OThe resolution of 1 KHz is too tight taken into account the channel spacing. A resolution of 250 KHz is easier and chepaer to achieve yet provides the necessary resolution for this application. P641€AInstead change the following: (1) On. p 304, line 33: add new H4 section labeled "Uplink Center Frequency". Contents: "The uplink center frequency shall be a multiple of 250 kHz." (2) On. p 304, line 33: add new H4 section labeled "Symbol Rate". Contents: "The symbol rate shall be in the range 10-32 MBaud, in increments of 100 kBaud" (3) On. p 306, line 12: replace value field with "Symbol rate in increments of 10 kBaud". (4) Pg. 306 ln 19 and ln 23 change "TDD" to "TDD and half-duplexB FDD" VAccepted-ModifiedW+Some systems might need a fine granularity.€B 2001/07/13ECarlFEklundH320JTechnical, Non-bindingK306L34M11.1.1.1NwAdd row to table | Random Access Time-out |9| 1| Number of UL-MAPs to receive before random access is attempted again|ORThis parameter is needed to impose some kind of order to the random access scheme.P627VAccepted€B 2001/07/13EMoritzF HarteneckH321J EditorialK307L15M11.1.1.2€NMRemove '(Not Used if scrambler is off)' from Scrambler Seed Value descriptionOxI did not find any reference to the possibility to switch the scrambler off so this comment is misleading and confusing.P462VAccepted€B 2001/07/13ELarsFLindhH322JTechnical, Non-bindingK307L22M11.1.1.2AInsert one row in the UCD Burst Profile table defining a relative signal level for the profile. The relative signal level parameter shall define the amplitude of the corner constellation point for the modulation used. Name Type Length Value Relative Signal Level 18 1 0-255€ADepending on the uplink power control strategy the BS may want to maintain different relative power levels for the different modulation and coding schemes. As the power control algorithm is not standardized the SS has no means of knowing the preferred relative power levels for the BS. It is therefore proposed that the relative power level are communicated in the UCD Burst Profile message. This procedure avoids an iterative power correction after a burst profile change.P639AAdd to the table of section 11.1.1.1 the following entry: Name: Power adjustment rule Type: 9 Length: 1 Value: 0=Preserve Peak, 1=Preserve Mean Power; Describes the power adjustment rule when performing a transition from one burst profile to another Furthermore, on page 287 ln. 45 add a new sentence after "... 8.2.4.4.8.": In changing from one burst profile to another the power adjustment rule can be one of 2 choices: (1) Maintaining same constellation peaks (2) Maintaining same m€Bnean power. The power adjustment rule is configurable through UCD Channel Encoding parameters (table 11.1.1.1).\VAccepted-Modified€B 2001/07/13ELarsFLindhH323JTechnical, Non-bindingK308L12M11.1.2.1N7Change "BS Transmit Power" to "BS transmit rms-Power" OClarification P645U;Change "BS Transmit Power" to "BS Transmit Power (average)"VAccepted-Modified€B 2001/07/13EAntonisFKarvelasH324J EditorialK308L17M11.1.2.1NCRemove the Continuous FDD from the Table entry "Downlink PHY type".ODThe Continuous FDD refers to old PHY Mode A which doesn't exist now.P470V Superceded€B 2001/07/13ELarsFLindhH325JTechnical, Non-bindingK308L17M11.1.2.1NVDownlink PHY type 1 = Burst FDD 2 = TDDP638UOn line 17 delete "(.... )"VAccepted-Modified€B 2001/07/13EKenFStanwoodH326J EditorialK308L17M11.1.2.1N Delete the parenthetical remark.OFThe PHY Type codes are PHY specific and should not be elaborated here.P575€V Superceded€B 2001/07/13ELarsFLindhH327JTechnical, Non-bindingK311L36M11.1.4N*Change "in KHz" to "in units of 250 KHz" OThe resolution of 1 KHz is too tight taken into account the channel spacing. A resolution of 250 KHz is easier and chepaer to achieve yet provides the necessary resolution for this application.P642UInstead: On. p 304, line 33: add new H4 section labeled "Downlink Center Frequency". Contents: "The downlink center frequency shall be a multiple of 250 kHz." VAccepted-ModifiedY$PHY group to provide the new section€B 2001/07/13EKenFStanwoodH328J EditorialK311L41M11.1.4N?Add "(not used with PHYs that do not have channelized uplinks)"OclarityP576VAccepted€B 2001/07/13EStanleyFWangGObserverH329JTechnical, Non-bindingK313L6M11.2€NRestore type 2 (Manufacturer-ID) and type 4 (RSA-Public-Key) from version D3d2 (see Table 114 of D3d2). Also restore the actual sections that define these two aatributes, i.e., 11.2.2 and 11.2.4 of D3d2 (see pages 341 and 341 of D3d2).OWe need type 4 for SS certificate (see line 38 page 232) and type 2 for all vendor-defined attributes (see line 3 page 318). So, we need to restore type 2 and type 4. P450UDon't do the requested change. Instead delete section 11.2.11 page 318. Also on page 313 delete lines 49-52 on line 47 change "126" to "255"VAccepted-Modified€B 2001/07/13EStanleyFWangGObserverH330J EditorialK313L9M11.2NChange "AUTH-KEY" to "AUTH-Key"O6Must match the name used, say for example, on page 86.P451VAccepted€B 2001/07/13EStanleyFWangGObserverH331J EditorialK316L3M11.2.7NDelete "(SAID)"OtypoP452VAccepted€B 2001/07/13EStanleyFWangGObserverH332J EditorialK316L48M11.2.9N4Change "HMAC-Digest attribute" to "CBC-IV attribute"OtypoP453€VAccepted€B 2001/07/13EStanleyFWangGObserverH333J EditorialK318L12M11.2.11N@Change the length field to ">= 4" and delete "1-byte error code"O43-byte manufacturer ID and >= 1 byte vender-defined.P454V Superceded€B 2001/07/13EStanleyFWangGObserverH334J EditorialK319L11M11.2.14NChange the length to >= 4.O1>= 3 bytes for suite list and 1 byte for version.P455VRejected€B 2001/07/13EStanleyFWangGObserverH335J EditorialK320L53M11.2.15NChange "Suit" to "Suits"OtypoP456UChange "Suite" to "Suites"VAccepted-Modified€B 2001/07/13EStanleyFWangGObserverH336J EditorialK321L1M11.2.16NDelete "Supported-"Osee Table 110 type 21.P457VAccepted€B 2001/07/13EStanleyFWangGObserverH337J EditorialK321L3M11.2.16N?Change "Cryptographic Suite" to "supported Cryptographic-Suite"O ClarificationP458U^Change "list of Cryptographic Suite parameters " to "list of supported Cryptographic-Suites "VAccepted-Modified€B 2001/07/13EStanleyFWangGObserverH338€J EditorialK321L9M11.2.16NChange "6*n" to "3*n"O$3 bytes for each suite (see 11.2.15)P459VRejected€B 2001/07/13EStanleyFWangGObserverH339J EditorialK321L49M11.2.18NChange the length field to "6"O<2 bytes for SAID, 1 byte for SA-Type, and 3 bytes for Suite.P460VRejected€B 2001/07/13EStanleyFWangGObserverH340J EditorialK322L40M11.2.20NChange the lenght field to 3O$1 byte for type and 2 bytes for CID.P461VRejected€B 2001/07/13EKenFStanwoodH341J EditorialK326L27M11.3.4NDThe referenced paragraph does not exist. Add the correct reference.P577UOn line 25-26 delete "(....)"VAccepted-Modified€B 2001/07/13EKenFStanwoodH342JTechnical, Non-bindingK327L5M11.3.5N`Is 255 large enough? Does this limit us to MIBs <256 bytes or just to MIB fields of <256 bytes?P578€B 2001/07/13EAntonisFKarvelasH343JTechnical, Non-bindingK327L35M11.4.1[€NAt this point the standard says that the Downlink Frequency Configuration Setting is used in the REG-REQ message. But at the section 6.2.2.4.7 Registration Request (REG-REQ) Message there is not any reference to the above parameter. AGenerally the standard doesn't give a clear picture about the source of the Downlink Frequency Configuration Setting. Is it stored in the SS? Or is it a parameter that the SS gets from the provisioning server using TFTP ? If the second apply then the scope column of section 11.4.1 must not have as scope the REG-REQ message because the SS gets the configuration file from the provisioning server (TFTP process) after completing the registration process (REG-REQ, REG-RSP). P477UDelete section 11.4.1 VAccepted-Modified€B 2001/07/13EAntonisFKarvelasH344JTechnical, Non-bindingK327L52M11.4.2€NAt this point the standard says that the Uplink Channel ID Configuration Setting is used in the REG-REQ message. But at the section 6.2.2.4.7 Registration Request (REG-REQ) Message there is not any reference to the above parameter. AGenerally the standard doesn't give a clear picture about the source of Uplink Channel ID Configuration Setting. Is it stored in the SS ? Or is it a parameter that the SS gets from the provisioning server using TFTP ? If the second apply then the scope column of section 11.4.2 must not have as scope the REG-REQ message because the SS gets the configuration file from the provisioning server (TFTP process) after completing the registration process (REG-REQ, REG-RSP). P478U Delete 11.4.2VAccepted-Modified€B 2001/07/13EKenFStanwoodH345JTechnical, Non-bindingK327L54M11.4.1N_Add the sentence "This TLV shall not be used with PHYs that do not support channelized uplinks"P579V Superceded€B 2001/07/13EKenFStanwoodH346€JTechnical, Non-bindingK328L15M11.4.3Nreplace starting with "including" on line 15 through line 25 with "limited to sending/receiving management traffic on its basic, primary, and secondary management channels."OUThe way its written now, an SS could use a data transport channel to TFTP files, etc.P580V Superceded€B 2001/07/13EAntonisFKarvelasH347J EditorialK328L30M11.4.4NRemove the section 11.4.4 .OyThis section must be deleted because it belongs to the SS Capabilities Encoding which are referred to in section 11.4.5 .P479VAcceptedW5Safe delete as funtionality can be handled by SBC RSP€B 2001/07/13ELarsFLindhH348JTechnical, Non-bindingK328L36M11.4.5€AThe duplex characteristics for a terminal must be included in the SS Capabilities Encodings. Type Length Value 5.12.7 1 bit#0: FDD full-duplex bit#1: FDD half-duplex bit#2: TDD bits#3-7 reservedP637A4Replace 11.4.5.6 with file "new section 11_4_5_6.fm"4@A 33VAccepted-Modified€B 2001/07/13EKenFStanwoodH349JTechnical, Non-bindingK331L37M11.4.5.5N+Add the sentence "Only one bit may be set."O,These ara mutually exclusive modes in an SS.P581V Superceded€B 2001/07/13EKenFStanwoodH350JTechnical, Non-bindingK333L30M 11.4.11.1NDelete lines 30-45OThis existed only in the SSs config file to reference flows that had not been assigned a SFID yet. Those flows are no longer in the config file.P582VAccepted€€B 2001/07/13EAntonisFKarvelasH351JTechnical, Non-bindingK334L21M 11.4.11.3NNRemove the "Configuration File" from the scope of Connection Identifier (CID).OYThe CID is given to the SS by the BS and it doesn't exist in the SS's Configuration File.P488UDo the above. Also do it on line 37. Do it also on p336 l. 47 p337 l. 50 p338 l. 42 p339 l. 7 ,l. 25, l. 53 p340 l. 21, l. 42 p341 l. 12, l. 30 ,l. 48 p342 l.20, l.39, p.343 l. 12 p.345 l. 30 ,l. 38 p346 l. 12VAccepted-Modified€B 2001/07/13EAntonisFKarvelasH352J EditorialK335L24M 11.4.11.5AReplace the sentence : "Multiple Service Flow Error Parameter Sets may appear in a REG-RSP, DSA-RSP, DSC-RSP, REG-ACK, DSA-ACK or DSC-ACK message, since multiple Service Flow parameters may be in error." with the following : "Multiple Service Flow Error Parameter Sets may appear in a DSA-RSP, DSC-RSP, DSA-ACK or DSC-ACK message, since multiple Service Flow parameters may be in error."€O`The Service Flow Encodings are not any more used in the Registration process (REG-REQ, REG-RSP).P489U-Do the above and delete "REG-REQ," on line 29VAccepted€B 2001/07/13ECarlFEklundH353J EditorialK338L22M 11.4.11.8.1N$Delete sentence ' For an uplink...' ONo more deferred grantsP616VAccepted€B 2001/07/13EKenFStanwoodH354JTechnical, Non-bindingK338L27M 11.4.11.8.1NCAdd "or discard non-conforming packets" to the end of the sentence.OJStandard option for handling the situation in real communications systems.P583VAccepted€B 2001/07/13EKenFStanwoodH355J EditorialK339L53M 11.4.11.10N/Put "R (in bits per second)" in the value fieldO3completness, consistency with other rate parametersP584VAccepted€B 2001/07/13EKenFStanwoodH356J EditorialK340L22M 11.4.11.11N"Put "B (bytes)" in the Value fieldO3completness, consistency with other size parametersP585VAccepted€B 2001/07/13ECarlFEklundH357J EditorialK342L41M 11.4.11.17€N,Change 'Bit#1....' to read 'Bit#1-Reserved'O'No more Priority request opportunities.P617VAccepted€B 2001/07/13EKenFStanwoodH358J EditorialK343L343M 11.4.11.19NDIf this section is not deleted, put "B (bytes)" in the value column.O3completness, consistency with other size parametersP586V Superceded€B 2001/07/13EKenFStanwoodH359JTechnical, Non-bindingK345L8M 11.4.11.22NMIf this section is not deleted, change the length to "2" and delete "(0-127)"ONAs currently stated, this is insufficient for defining meaningful CBR traffic.P587V Superceded€B 2001/07/13EStanleyFWangGObserverH360JTechnical, Non-bindingK346L17M 11.4.11.26€AComment #1017 from LB #3 need to be implemented. It said: Insert new section H4 reading 'Target SAID' reading The target SAID parameter indicates the SAID that the service flow being set up shall be mapped onto. This parameter may only be used together with the Service Flow Identifier . |Type | Length| Value | Scope | | 24.26 | 2 | SAID BHonto which SF is mapped| DSA-REQ (BS initiated), DSA-RSP (SS initiated)|6O2It was marked "accepted" and "done" but no change.P329€AOn page 346 line 17 Insert new section H4 reading 'Target SAID' reading The target SAID parameter indicates the SAID that the service flow being set up shall be mapped onto. This parameter may only be used together with the Service Flow Identifier . |Type | Length| Value | Scope | | [24/25].26 | 2 | SAID onto which SF is mapped| DSA-REQ (B&BS initiated), DSA-RSP (SS initiated)|VAccepted-Modified€B 2001/07/13EKenFStanwoodH361JTechnical, Non-bindingK348L39M11.4.16€AOn line 39 break the paragraph into 2 paragraphs after the word "sublayers". To the end of the first paragraph add the sentence "The following TLV defines the convergence sublayer to be used for a service flow." After the new sentence, add a TLV table with the type field set to "99.0", the length field set to "1", and the value field identical to the value field of the table at line 47.O^Otherwise a connection's CS is merely implied by its other TLVs rather than explicitly stated.P588VAccepted€B 2001/07/13EKenFStanwoodH362J EditorialK348L39M11.4.16N.Change "Configuration files" to "DSx messages"O1This information is no longer in the config file.P589VAccepted€B 2001/07/13ECarlFEklundH363J EditorialK348L56M 11.4.16.1NMake the layout of the section consistent with other section defining TLVs e.g. make the tap separated tables properly formatted tablesP618€UMake the layout of the section consistent with other section defining TLVs e.g. make the tab separated tables properly formatted tablesVAccepted-Modified€B 2001/07/13EKenFStanwoodH364JTechnical, Non-bindingK349L1M 11.4.16.1.1NDelete lines 1 through 23OThese parameters are no in the config file or regsitration message and are redundant with the exact same TLVs in sections 11.4.16.1.6 and 11.4.16.1.10.1P590VAccepted€B 2001/07/13EKenFStanwoodH365JTechnical, Non-bindingK349L24M 11.4.16.1.1.3NfMove page 349, lines 24-39 to page 350, line 10. On page 349, line 36, change "99.1.28" to "99.1.5.1"O6This is an SS capability, not a config file parameter.P591UgOn page 349, line 36, change "99.1.28" to "99.1.5.1" Move page 349, lines 24-39 to page 350, line 10. VAccepted-Clarified€B 2001/07/13EKenFStanwoodH366JTechnical, Non-bindingK350L13M 11.4.16.1.3.2NhChange the sentence to "If the value field is a 1, the SS supports Packet CS payload header supression."€OdBy definition of where this TLV is defined, it is describing an SS capability, not making a request.P592VAccepted€B 2001/07/13EKenFStanwoodH367JTechnical, Non-bindingK351L3M 11.4.16.1.7.1NDelete lines 3-12.OSince the classifier no longer is in the config file, the classifier reference is unnecessary. The BS returns the classifier identifier in the DSA-REQ or DSA-RSP message.P593VAccepted€B 2001/07/13EKenFStanwoodH368JTechnical, Non-bindingK357L53M11.4.16.1.10.2N3Delete page 357, line 53 through page 358, line 30.O_These are redundant with previously defined TLVs. There is no need to re-specify them for PHS.P594VAccepted€B 2001/07/13EKenFStanwoodH369JTechnical, Non-bindingK358L23M11.4.16.1.10.5N]If this section is not deleted, delete the last sentence, including the parenthetical remark.OThis is an old DOCSIS rule. We don't have prmary downlink service flows, and even if we did, we wouldn't associate all PHS rules with them and only them.P595€V Superceded€B 2001/07/13ERogerFMarksGMemberH370J EditorialK363L44M13NReview Bibliography 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".P737VAccepted€B 2001/07/13ERogerFMarksGMemberH371J EditorialK363L44M13N$Add [I.530], [I.452] to bibliograhy.OCited on p. 292 (lines 47 &57)P738VAccepted