Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0 t|@u€@NTER  DB G JU_isACE@ ABWN A!C"E#[$ O% L&A'C(E)G*I+K,M-O.Q/N0U1O2S3@4A5C6A7A8C9A:A;C%G?*O@BA,JB.AC0JD1AE2NFBGDH4NI6AJBKDL7BM9ANBODPFQBSR<AT?EUAOVEVWINXKJYNAZO@[RA\T]A^SA_VA`BaXObYUc\Jd^OebJfAgdFhfOikJjmNkpNlsFmtAnuAovNpxYr@@q!@.HBAM3016AUG95@ AAzHH(FG(HH(d}HzA#'dDu*0HS@Jjg$?*/ 0*r?HjNBgO `/ 0*r?HjNO HnBgJGg\.rgR jf=n`0+H F2(HҀ0* HЁ=@0*HT=@0.HS??.?.?.JGg\.rgR jf=n`0+H F2(HҀ0* HЁ=@0*HT=@0.HS??.?.?.Jjgx0*rg jf=n`0+H F2(HҀ0* HЁ=@ F0H2*H Ё2*HT=ANRJgD FQ4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  ,  X5vX(VX`V0X`X`0SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDecul3   7/24/2001@ BALLOTNUMBERCHANGE COMMENT DATE COMMENT NUMBER COMMENT TYPE COMMENTARY VERSION DOCNUMBER EXPORTDATE FIRST NAME LAST NAMEMEMBERSHIP TYPEREASONSECTION STARTING LINE NUMBER STARTING PAGE NUMBER              q!ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]EPro 5.0F!2(M1,,./: AM PMYyTtNnFfP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  ,  ABCDEFGHI J K L M NOPQRSTUVWXYZ[\]    !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ 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 #1B1$$$$@: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%468HHHHHH H H H H H H HHHHH H"H$H&H(HH H"H$H&H(@ 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/21ERogerFMarksGMemberH001J 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".P710VAcceptedZk) done[Made many changes. Each change in Comment 2 was followed by a change here. In addition, several figures and table which already had numbers and titles were not previously referenced in the text.B 2001/07/21ERogerFMarksGMemberH002J 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".P711VAcceptedZk) done@ QH*H,H.H0H2H4H6H8 v        "$&(*,.02468HHHHHH H H H H H H HHHHH H"H$H&H(HH H"H$H&H( 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 #1B1$$$$@:A  $,.YesNo/,  , : AM PMB   C  $,.YesNo/,  , : AM PMD   E  $,.YesNo/,  , : AM PMF   G  $,.YesNo/,  , : AM PMH   I  $,.YesNo/,  , : AM PMB 2001/07/21ERogerFMarksGMemberH003JTechnical, 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/25A1. 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 fragments@$AMade made changes to carry out this task. Completed it, with the exception of TLVs in Subclauses 11.2, 11.3, and 11.4. These have many simple tables that are currentlyt without number or title. It seems reasonable to leave out the numbers on these tables. See Commment 318. B 2001/07/21ERogerFMarksGMemberH004J 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.P714VAcceptedZl) none needed[Couldn't solve the problem, but I expanded the margins and the line breaks went away, so the problem has gone underground for now.B 2001/07/21ERogerFMarksGMemberH005JTechnical, 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-DuplicateZl) none neededB 2001/07/21ERogerFMarksGMemberH006J EditorialK19L57MLoF@=B 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 tChe 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. Zl) none needed  @!NQDelete 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 TablesP716VAcceptedZk) doneB 2001/07/21ERogerFMarksGMemberH007JTechnical, 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.P718 "AOn page 27, line 32, replace the sentence starting "This standard includes a " with "This standard is structured to contain a variety of physical layers, each suited to a particular operational environment." On page 27, line 53, add: "1.2.1 10-66 GHz Bands The 10-66 GHz bands provide a physical environment where line of sight (LOS) is required, but multipath is minimized. The channels used in this physical environment are typically large. For example, 25 or 28 MHz wide channels wouldB be typical. With raw data rates in excess of 120 Mbps, this environment is well suited for point to multipoint access serving applications from small office/home office (SOHO) through medium to large office applications. 1.2.2 2-11 GHz Licensed Bands For future study. 1.2.3 2-11 GHz Unlicensed Bands For future study." On page 27, line 62 add "Note that as an access standard, 802.16 is different from the other 802 standards in that its purpose is to carry those other standards, bridg!#Cing the gap between the end user and a host network such as the Internet. From the unique perspective of 802.16, the other 802 standards may be viewed as application data." On page 29, line 16, delete the last sentence. On page 29, line 21, reduce the "Scope of Standard" dashed box to only encompass the Data/Control Plane. On page 29, line 53 add: "The MAC layer is made up of 3 sublayers. The Service Specific Convergence Sublayers (CS) provide any transformation or mapping of applicaDtion data, received through the CS-SAP, into MAC SDUs received by the MAC Common Part through the MAC-SAP. This includes classifying application SDUs and associating them to the proper MAC service flow and connection ID. It may also include such functions as payload header suppression (PHS). The internal format of the CS payload is unique to the CS, and the MAC Common Part is not required to understand the format of or parse any information from the CS payload. The Mac Common Part provi"$Edes the core MAC functionality of system access, bandwidth allocation, connection establishment and connection maintenance. It receives data from the various CS, through the MAC-SAP, classified to particular MAC connections. QoS is applied to the transmission and scheduling of data over the physical layer. The MAC also contains the provisions for security, which are treated as a separate sublayer within the MAC. The security sublayer provides authentication, secure key exchange, and enFJcryption. Data, physical layer control, and statistics are transferred between the MAC Common Part and the Physical Layer via the PHY SAP. The PHY is specific to the frequency range and application being supported by an instance of an 802.16 system. The various physical layers supported are described in detail in section 8."  @Af      !  5  fVAccepted-ModifiedZk) done#%[Made editorial revisions.B 2001/07/21ERogerFMarksGMemberH008J 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".P719VAcceptedZi) to do[Harmonized style of references. Deleted or redundant references. Located uncited references; moved to informative bibliography or, in some cases, deleted them. B 2001/07/21ERogerFMarksGMemberH009J EditorialK31L31M3A7Add 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.7$& OThese 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-ClarifiedZk) done[2Deleted hyphen in "time-division" for consistency. B 2001/07/21EStanleyFWangGObserverH010J EditorialK35L18NBARQ stands for "Automatic Repeat Request" instead of "Retransmit" P662U5Replace the list of acronyms with file "comment10.fm"VAccepted-ModifiedZk) done B 2001/07/21EStanleyFWangGObserverH011J EditorialK35L65M4N7Add the following acronym: "ECB Electronic Code Book"OUsed on page 227P330V SupercededZl) none needed B 2001/07/21EStanleyFWangGObserverH012J EditorialK36L52M4N4Add the following acronym: "OID Object Identifier"OUsed on page 230P331V SupercededZl) none needed B 2001/07/21EStanleyFWangGObserverH013J EditorialK37%' L62M4N$The last 3 acronyms are out of orderO out of orderP332Uby 10VAccepted-DuplicateZl) none neededB 2001/07/21EKenFStanwoodH014J EditorialK38L16M5N*Change "specified:the" to "specified: the"O space missingP498QCERAcceptedVAcceptedZk) doneB 2001/07/21EStanleyFWangGObserverH015J EditorialK38L56M5.1.2.1N*Change "QoS" to "Quality of Service (QoS)'OUsing "QoS" for the first time.P333QCERAcceptedV SupercededZl) none neededB 2001/07/21EStanleyFWangGObserverH016J 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 TlThe suggested fix does not address the entire problem. Also we have defined all header is our table format. &(A replace 5.1.2-5.1.4.2 with the file "comment16.fm" , which reads: Data/Control Plane PDU formats The ATM CS PDU shall consist of an ATM CS PDU Header, defined in Table 1, and the ATM CS PDU Payload. The ATM CS PDU Payload shall be equal to the ATM cell payload. The ATM CS PDU is illustrated in Figure 1. ATM CS PDU Header Syntax Size Notes ATM_CS_PDU_Header (){ if (no PHS) { ATM_Header 40 bits The full ATM cell header } else if (VP switched) { PTI 3 bits From the ATM cell header BCLP 1 bit From the ATM cell header reserved 4 bits VCI 16 bits From the ATM cell header } else (VC switched) { PTI 3 bits From the ATM cell header CLP 1 bit From the ATM cell header reserved 4 bits } } Classification An ATM connection, which is uniquely identified by a pair of values of Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI), may be either Virtual Path (VP) switched or Virtual Channel (VC) switched. In VP switched mode, all VCIs within one single inco')Cming VPI are automatically mapped to that of an outgoing VPI. In VC switched mode, input VPI/VCI values are individually mapped to output VPI/VCI values. Thus, when performing PHS, ATM CS must be able to differentiate these two types of connections and perform the suppression accordingly. A classifier is a set of matching criteria applied to each ATM cell entering the ATM CS. It consists of some ATM cell matching criteria, such as VPI and VCI, and a reference to a CID. If an ATM cell matchDes the specified matching criteria, it is delivered to the MAC SAP for delivery on the connection identified by the CID. Virtual path switched mode For VP switched mode, the VPI field, 12 bits for a Network to Network Interface (NNI) and 8 bits for a User to Network Interface (UNI), is mapped to the 16-bit CID for the MAC connection on which it is transported. Since the Quality of Service (QoS) and Category of service parameters for the connection are set at connection establishment, this (*Emapping of VPI to CID guarantees the correct handling of the traffic by the MAC sublayer. Virtual channel switched mode For VC switched mode, the VPI and VCI fields, 28 bits total for an NNI and 24 bits total for a UNI, are mapped to the 16-bit CID for the MAC connection on which it is transported. Since the QoS and Category of service parameters for the connection are set at connection establishment, this mapping of VPI and VCI to CID guarantees the correct handling of the traffic by the FMAC sublayer. Note that the full range of VPI/VCI combinations (up to 228 for NNI and 224 for UNI) cannot be simultaneously supported in this mode. Payload Header Suppression In Payload Header Suppression, a repetitive portion of the payload headers of the CS SDUs is suppressed by the sending entity and restored by the receiving entity. On the downlink, the sending entity is the ATM CS on the BS and the receiving entity is the ATM CS on the SS. On the uplink, the sending entity is the ATM )+GCS on the SS and the receiving entity is the ATM CS on the BS. To further save bandwidth, multiple ATM cells (with or without PHS) which share the same CID should be allowed to be packed and carried by a single MAC-CPS PDU. Note that when PHS is turned off, no part of any ATM cell header including Header Error Check (HEC) field shall be suppressed. This provides an option for protecting the integrity of the cell header. Whether or not payload header suppression is applied to an ATM connectHion is signaled in the DSA-REQ message at the connections creation. Similarly, the VPI (for VP-switched connections) or the VPI/VCI (for VC-switched connections) is also signaled in the classifier settings of the DSA-REQ message at connection creation. PHS for virtual path switched ATM connections In VP switched mode, the VPI is mapped to a CID. This allows the disposal of the remainder of the ATM cell header except for the VCI, Payload Type Indicator (PTI), and Cell Loss Priority (CLP) f*,Iields. These fields shall be encapsulated in the CS PDU Header. Figure 2 shows a CS PDU containing a single VP-switched ATM cell with the cell header suppressed and the format of the ATM CS PDU Header for VP-switched ATM connections. PHS for virtual channel switched ATM connections In VC switched mode, the VPI/VCI combination is mapped to a CID. This allows the disposal of the remainder of the ATM cell header except for the PTI and CLP fields. These fields shall be encapsulated in the CS JPDU Header. Figure 3 shows a CS PDU containing a single VC-switched ATM cell with the cell header suppressed and the format of the ATM CS PDU Header for VC-switched ATM connections. Signaling procedure ATM interfaces support three types of connections, Switched Virtual Connection (SVC), Permanent Virtual Connection (PVC), and Soft Permanent Virtual Connection (soft PVC). SVCs are established and terminated dynamically on demand by the use of signaling. The word permanent signifies that t+-Khe connection is established administratively. Although both PVC and soft PVC are established administratively, PVCs are established by provisioning process and soft PVCs are established by the use of signaling. ATM networks use Common Channel Signaling (CCS), where signaling messages are carried over a connection completely independent of user connections and where one signaling channel can carry signaling messages for a number of user connections. Per non-associated signaling defined in LATM UNI 4.0 (see [ATM96b]), by default, the signaling channel on VPI=0 controls all VPs on the same physical interface. In other words, except when the optional Proxy Signaling capability (see Annex 2 of [ATM96b]) or when the optional Virtual UNI capability (see Annex 8 of [ATM96b]) is used, the signaling channel is identified by VPI=0 and VCI=5. Note that this specification does not support Associated Signaling (specified in ATM UNI 3.1, [ATM94]), where VCI=5 of each VP is used as the sig,.Mnaling channel for all VCs on the same VP. In addition, this specification does not support either Proxy Signaling or Virtual UNI. To establish an SVC, it is the responsibility of the calling party to initiate the signaling procedure by issuing the appropriate signaling messages. Either end can establish or release the SVC. Details on how to use these signaling messages are available in [ATM96b]. It shall be the responsibility of the implementation of the BS to map ATM signaling messages Nto corresponding MAC-CPS service primitives. To establish a soft PVC, the network management system provisions one end of the soft PVC with the address identifying the egress ATM interface of the ATM network. The calling end has the responsibility for establishing and releasing the connection. It is also the responsibility of the calling party (if necessary) to re-establish the connection in case of switching system or link failure. It shall be the responsibility of the implementation of t-/Ohe BS to map ATM signaling messages to corresponding MAC-CPS service primitives. On the downlink direction, the signaling starts at an end-user of the ATM backhaul network that implements an ATM UNI and terminates at the BS that shall implement either an ATM UNI or an ATM NNI. The signaling may be mapped by an InterWorking Function (IWF) and extended to some user network on the SS-side. On the uplink direction, the signaling starts at the ATM interface of the BS and ends at the ATM UNI oPf an end-user. In addition, the signaling may be originated by an end-user of some user network and mapped by the IWF. Note that mapping of data units carried by the air link shall be limited to only cell-level convergence (0.0.1.2). If required by a user network, other levels of mappings (e.g., the convergence of, say, an Ethernet packet to ATM cells) shall be handled by the user networks IWF exclusively. During the provisioning process, each SS joining the IEEE 802.16 system shall r.0Q equest a dedicated CID as the signaling connection corresponding to the CCS connection used by ATM networks. Any CID provisioned for this purpose shall not be dynamically changed or terminated. Each IEEE 802.16 system shall provision a set of CIDs for this purpose. VAccepted-ModifiedZk) doneB 2001/07/21EAntonisFKarvelasH017J 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}VRejectedZl) none neededB 2001/07/21ECarlFEklundH018J EditorialK42L27N$p42 l 27.5; remove the extra periodP626VAcceptedZk) doneB 2001/07/21ERogerFMarksGMemberH019JTechnical, Non-bindingK42L41M 6.1.1.2.4/1N{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-ClarifiedZk) done[Rdeleted ", and enters the CID into approproriate algorithms". Did not delete "..."B 2001/07/21EVladimirFYanoverH020JTechnical, 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)02~UReplace "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-ModifiedZk) doneB 2001/07/21EVladimirFYanoverH021JTechnical, 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."X13OChanging "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-ModifiedZk) doneB 2001/07/21EVladimirFYanoverH022J 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-ClarifiedZk) doneB 2001/07/21EVladimirFYanoverH023J 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 StanwoodRAccepted24SeOrdering of logical interface has no impact, so if no one objects, we should use Vladimir's ordering.VAcceptedZk) doneB 2001/07/21EVladimirFYanoverH024J 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 StanwoodRAcceptedVAcceptedZk) doneB 2001/07/21EVladimirFYanoverH025J 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 StanwoodRAcceptedVAcceptedZk) done35B 2001/07/21EVladimirFYanoverH026JTechnical, Non-bindingK63L47M6.2.1NPRemove "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 . 46AOn page 331 line 46 add new section H4 IP Version This field indicates the version of IP used on the Secondary Management Connection. Type |Length |Value | Scope | 5.9 |1 |bit#0: 4 |REG-REQ, REG-RSP | | |bit#1: 6 | | | |bits #3-7: reserved, shall be set to zero | | On page 63 lines 47-51 change "These messages ... in the Downlink" to read "These messages are carried in IP packets as specified in . The packets shall be assigned to the SecondaryB Management Connection based on the full IP source address in the Uplink and the full IP destination address in the Downlink." On page 144 line 27 insert new section H5 under registration "IP version negotiation" The SS may include the IP Version < ref to TLV added above> parameter in the REG-REQ to indicate which versions of IP it supports on the Secondary Management Connection. The present in the REG-REQ, the BS shall include the IP version parameter < ref to TLV added above> in the R57CEG-RSP to command the SS to use the version of IP, indicated by the parameter, on the Secondary Management Connection . The BS shall command the use exactly one of the IP versions supported by the SS. The omission of the IP version parameter in the REG-REQ shall be interpreted as IPv4 support only. Consquently the mission of the IP version parameter in the REG-RSP shall be interpreted as command to use IPv4 on the secondary management connection. VAccepted-ModifiedZk) doneB 2001/07/21EVladimirFYanoverH027J EditorialK67L6M 6.2.2.1.1NDelete the following text fragments from the Table 3 For type = 0x03 "code may be reused for some DL only purpose" For type = 0x04 "(not needed simultaneously with packing sub-header)" For type = 0x05 "code may be reused for some DL only purpose"OJThese are comments for the developers of the standard, not for the readersP65568AReplace p 67 lines 1-25 with contents of file "comment027.fm" , which reads: The allowed values for the Type field are listed in Table 1 and Table 2. Downlink Type encoding Type Description 0x00 No sub-headers present 0x01 Reserved 0x02 Packing sub-header present 0x03 Reserved 0x04 Fragmentation sub-header present 0x05-0x3F Reserved Uplink Type encoding Type Description 0x00 No sub-headers present 0x01 Grant Management sub-header present 0x02 Packing sub-header present 0x03 Both Grant ManBagement and Packing sub-headers present 0x04 Fragmentation sub-header present 0x05 Fragmentation and grant management sub-headers present 0x06-0x3F ReservedVAccepted-ModifiedZk) doneB 2001/07/21EKenFStanwoodH028J 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.P499VRejectedZl) none neededB 2001/07/21EKenFStanwoodH029JTechnical, Non-bindingK68L3M 6.2.2.1.279AOn 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 th8:+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.9;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-ModifiedZk) doneA In this sentence on p 54 l 42: "The scheduling service type is one of the following: continuing grant, continuing grant with activity detection, real-time variable rate, non-real-time variable rate, and best effort.", removed "continuing grant with activity detection" B 2001/07/21ERogerFMarksGMemberH030J EditorialK68L37M6.2.2.2N/Delete 6.2.2.2 and renumber following sections.ORedundant with 6.2.2.3.P722UDelete lines 49-56VAccepted-ModifiedZk) doneB 2001/07/21EKenFStanwoodH031JTechnical, 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.P500VAcceptedZk) done B 2001/07/21EKen=? FStanwoodH032JTechnical, 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.P501VAcceptedZk) done!B 2001/07/21ECarlFEklundH033J EditorialK68L47M6.2.2.2N"Change 'Ifpresent' to 'If present'P607VAcceptedZk) done"B 2001/07/21EKenFStanwoodH034J EditorialK68L47M6.2.2.2N"Change "Ifpresent" to "If present"OMissing space.P502VAccepted-DuplicateZl) none needed#B 2001/07/21EKenFStanwoodH035J 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.P504VRejectedZl) none needed$B 2001/07/21ECarlFEklundH036J EditorialK71L6M 6.2.2.3.3N'Change word 'illustrated ' to 'defined'OThe table defines the formatP620VAcceptedZk) done%B 2001/07/21EStanleyFWang>@%GObserverH037J EditorialK71L19M 6.2.2.3.3N#Change "MAC SDU Length" to "Length"O$Field name shall be spelled exactly.P335VAcceptedZk) done&B 2001/07/21ECarlFEklundH038J EditorialK71L50M6.2.2.4NChange '.MAC' to 'MAC'OSounds too much like '.NET'P619VAcceptedZk) done'B 2001/07/21EKenFStanwoodH039J EditorialK71L50M6.2.2.4NChange ".MAC" to "MAC"O Extra period.P505VAccepted-DuplicateZl) none needed(B 2001/07/21EStanleyFWangGObserverH040J EditorialK71L50M6.2.2.4NChange ".MAC" to "MAC"OTypoP336VAccepted-DuplicateZl) none needed)B 2001/07/21EKenFStanwoodH041J 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.Zk) done*B 2001/07/21EKenFStanwoodH042JTechnical, Non-bindingK72L4M6.2.2.4NRemove "(optonal)".?A*OFor MAC Management messages, the payload is not optional like it is for CS messages. It must have at least the message type code.P507AOn 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 fragmen@B*Bted 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 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-ModifiedZk) done[7Used upppercase for MSB and LSB to match rest of draft.+B 2001/07/21ECarlFEklundH043J EditorialK73L42M 6.2.2.4.1 NTChange 'modulo the field size' to 'modulo 256' Make same change on page 75 line 56 P621VAcceptedZk) done,B 2001/07/21EKenFStanwoodH044AC,J 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."OClarityP508VAcceptedZk) done-B 2001/07/21EStanleyFWangGObserverH045J 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.P337UhDelete line 21 Append lines 22-25 to line 15. In the appended text change 'Length field' to 'LEN field'VAccepted-ClarifiedZk) done.B 2001/07/21EStanleyFWangGObserverH046JTechnical, Non-bindingK76L30M 6.2.2.4.3BD.A/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, add 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 overheadZk) done/B 2001/07/21EKenFStanwoodH047J EditorialK76L56M 6.2.2.4.3AOn 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.P509VAcceptedZk) done0B 2001/07/21EAntonisFKarvelasH048CE0J 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-ModifiedZk) done1B 2001/07/21EAntonisFKarvelasH049JTechnical, Non-bindingK80L6M 6.2.2.4.6NaInsert a new field : "Uplink operational burst profile : the SS uplink operational burst profile"DF1AIt 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.Zk) done2B 2001/07/21EAntonisFKarvelasH050JTechnical (was Editorial)K80L47M 6.2.2.4.7EG+2NRemove 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 includFH2Be 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" {DSA-REQ} p 92 l. 52 change "is" to "contains" p 94 l. 7-10 change*3 "-Digest" to " Tuple" {DSA-RSP} p 94 l. 8 change "is" to "contains" p 95 l. 25-28 change*3 "-Digest" to " Tuple" {DSA-ACK} p 95 l. 26 change "is" to "contains" p 96 l. 20-23 change*3 "-Digest" to " Tuple" {DSC-REQ} p 96 l. 21 change "is" to "contains" p 97 l. 27-30 change*3 "-Digest" to " Tuple" {DSC-RSP} p 97 l. 29 change "is" to "contains" p 98 l.GI2D 25-27 change*3 "-Digest" to " Tuple" {DSC-ACK} p 98 l. 26 change "is" to "contains" p 99 l. 16-19 change*3 "-Digest" to " Tuple" {DSD-REQ} p 99 l. 18 change "is" to "contains" pp 100 l. 3-6 change*3 "-Digest" to " Tuple" {DSD-RSP} p 100 l. 4 change "is" to "contains"VAccepted-ModifiedW6Authentication and key exchange are mandatory featuresZk) done[This got a little hairy, what with previous changes to the same sections. I think it came out OK, but some of the additions may be better off slightly relocated.3B 2001/07/21EAntonisFKarvelasH051J 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. P464VAcceptedZk) done4B 2001/07/21EVladimirFYanoverH052JTechnical, Non-bindingK81L29M 6.2.2.4.8HJ24NChange "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-DuplicateZl) none needed5B 2001/07/21ECarlFEklundH053JTechnical, 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.P609VAcceptedZk) done6B 2001/07/21EAntonisFKarvelasH054JTechnical, Non-bindingK81L43M 6.2.2.4.8NAInsert the sentence "Network Access Control Object (see 11.4.3)".IK6AAt 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.P468AOn page 73 line 29 Change "De-register" to "De/Re-register" On page 141 line 20 delete "and the Network Access Control Object 11.4.3" On page 327-328 delete section 11.4.3 On page 106 replace line 50 through page 107 line 30 with contents of file "comment054.fm", which reads: De/re-register Command (DREG-CMD) Message The De/re-register Command Message shall be transmitted by the BS on an SSs Basic CID to force the SS to change its access state. Upon receiving a DREG-CMD the SS shall JL6Btake the action indicated by the action code. The MAC Management Message type for this message is given in Table 11. The format of the message is shown in Table 1. De-register Command (DREG-CMD) Message Format Syntax Size Notes DREG-CMD_Message_Format() { Generic_MAC_Header() 48 bits Management Message Type = 29 8 bits Action Code 8 bits TLV encoded parameters variable } The Action Code values and the corresponding actions are specified in Table 2. Action Codes anCd Actions Action Code Action 0x00 SS shall leave the current channel and attempt to access another channel 0x01 SS shall listen to the current channel but shall not transmit until a RES-CMD message is received 0x02 SS shall listen to the current channel but only transmit on the Basic, Primary Management and Secondary Management connections 0x03 SS shall return to normal operation and may transmit on any of its active connections 0x04-0xFF Reserved The following TLV encoded parameters shaKM6Dll be present: HMAC DigestVAccepted-ModifiedZk) done[Also changed "De-register" to "De/Re-register" in caption of Table 55 Regarding {On page 73 line 29 Change "De-register" to "De/Re-register"}: the line is 20; the Type is 29. 7B 2001/07/21EAntonisFKarvelasH055JTechnical, 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 LN7Bit 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-ClarifiedZk) done[SRe: Page 335 line 24 Delete "REG-ACK," : already deleted by some previous comment 8B 2001/07/21ECarlFEklundH056JTechnical, Non-bindingK82L4M 6.2.2.4.9NDelete line 'It confirms....'O-SF QoS parameters are not known at this time.P610V SupercededZl) none needed9B 2001/07/21EKenFStanwoodH057JTechnical, Non-bindingK84L33M 6.2.2.4.10MO_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 messagesP510A1. On page 84, delete lines 33-37. 2. On page 84, line 39, change "16-255" to "13-255" 3. On page 84, line 49, change "is an Authorization Request, Key Request or SA Map Request" to "is an Authorization Request or Key Request" 4. On page 85, line 1 delete the subsentence starting "a particular Security Association..." 5. On page 85, delete lines 13-16 6. On page 90 delete line 36 through page 91, line 47 (i.e., delete sections 6.2.2.4.10.10, 6.2.2.4.10.11, and 6.2.2.4.10.12). 7. On page 20NP9B1, line 6, change the first sentence to "The actual mapping is achieved by including the SAID of an existing SA in the DSA-xxx messages together with the CID." 8. On page 217, line 31, replace section 7.3 with the file "section73.fm" {see below} 9. On page 303, delete lines 39-45. 10. On page 313, line 42, change "SA-Query" to "Reserve" 11. On page 313, line 44, change "SA-Query-Type" to "Reserve" 12. One page 317, delete lines 33-36. 13. On page 322, delete line 29 through page 323 line 1C3 (i.e., sections 11.2.20 and 11.2.21). 14. On page 324, delete line 54 through page 325 line 12 15. On page 348, line 34, add two new rows: "| 14 | reject-not-authorized-for-the-requested-SAID |" and "| 15 | reject-fail-to-establish-the-requested-SA |" section73.fm: Dynamic SAs Creation and Mapping Dynamic Security Associations are SAs that a BS establishes and eliminates dynamically in response to the enabling or disabling of specific downlink service flows. SSs learn the mapping of a pOQ9Darticular privacy-enabled service flow to that flows dynamically assigned SA through the exchange of DSx messages. Dynamic SA Creation with DSA With BS-initiated dynamic service creations, a BS may dynamically create an SA and pass the new SAID to an SS in a DSA-REQ message. With SS-initiated dynamic service creations, a BS may dynamically create an SA and pass the new SAID to an SS in a DSA-RSP message. Dynamic SA Creation with DSC SAs can also be dynamically created with DSC messages. WEith BS-initiated dynamic service modifications, a BS may dynamically create an SA and pass the new SAID to an SS in a DSC-REQ message. With SS-initiated dynamic service modifications, a BS may dynamically create an SA and pass the new SAID to an SS in a DSC-RSP message. In both cases, the service flow shall be deactivated first and activated after the changes are completed. Dynamic Mapping of SA When creating a new service flow, an SS may request an existing SA be used by passing the SAIDPS9F of the SA in a DSA-REQ or DSC-REQ message. The BS checks the SSs authorization for the requested SA and generates appropriate response using a DSA-RSP or DSC-RSP message correspondingly. With BS-initiated dynamic service creations, a BS may also map a new service flow to an existing SA that is supported by a specific SS. The SAID of the SA shall be communicated to the SS in a DSA-REQ or DSC-REQ message. ?@A#      %  &  Y  Z      B  C  d  e                        D  E STv9VAccepted-ModifiedZk) done:B 2001/07/21EStanleyFWangGObserverH058J 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-ModifiedZk) done;B 2001/07/21EStanleyFWangGObserverH059J EditorialK84L54M 6.2.2.4.10N%Change "may be set" to "shall be set"OThis is not an option.P340VAcceptedZk) doneB 2001/07/21EStanleyFWangGObserverH062J EditorialK85L26M 6.2.2.4.10N$Change "Packet formats" to "Formats"OThey are not packets.P343VAcceptedZk) done?B 2001/07/21TV?ERogerFMarksGMemberH063J 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 2459Zk) done@B 2001/07/21EStanleyFWangGObserverH064J 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.P344VAcceptedZk) doneAB 2001/07/21EStanleyFWangGObserverH065J EditorialK86L34M 6.2.2.4.10.2NHChange the Contents column to read "Authorization Key's active lifetime"UWAOOtherwise 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. P345VAcceptedZk) doneBB 2001/07/21EStanleyFWangGObserverH066J EditorialK86L54M 6.2.2.4.10.3NGChange the title of the Table to read "Authorization Reject Attributes"OTypoP346VAcceptedZk) doneCB 2001/07/21ECarlFEklundH067JTechnical, Non-bindingK87L17M 6.2.2.4.10.4N1Delete row with 'SS Identification' from table 28O.The SS Identification is done based on the CIDP611VAcceptedZk) doneDB 2001/07/21EKenFStanwoodH068JTechnical, Non-bindingK87L18M 6.2.2.4.10.4NDelete line 18.O$SS Identifier no longer needed here.P511VAccepted-DuplicateZl) none neededEB 2001/07/21EStanleyFWangGObserverH069JTechnical, Non-bindingK87L18M 6.2.2.4.10.4N-Delete the entire row for "SS-Identification"OUsing CID instead of SS-ID.P347VXEVAccepted-DuplicateZl) none neededFB 2001/07/21EStanleyFWangGObserverH070J 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 SupercededZl) none neededGB 2001/07/21ECarlFEklundH071JTechnical, Non-bindingK90L53M 6.2.2.4.10.10N1Delete row with 'SS Identification' from table 34O,The SS Identification TLVs have been removedP612V SupercededZl) none neededHB 2001/07/21EKenFStanwoodH072JTechnical, 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 SupercededZl) none neededIB 2001/07/21EKenFStanwoodH073JTechnical, Non-bindingK92L47M 6.2.2.4.11WYINOn 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 CompletenessP513UOn 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-ClarifiedZk) doneJB 2001/07/21EAntonisFKarvelasH074JTechnical, 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).P491VAcceptedZk) doneKB 2001/07/21EKenFStanwoodH075XZKJTechnical, 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-DuplicateZl) none neededLB 2001/07/21EKenFStanwoodH076JTechnical, Non-bindingK93L9M 6.2.2.4.11.2NOn page 93, line 9 add "BS-initiated DSA-Requests shall also include the SA-Descriptor for the service flow." On page 94, line 18 add "The BS's DSA-response shall also include the SA-Descriptor for the service flow."OAgreed to last meetingP515VAcceptedZk) doneMB 2001/07/21ECarlFEklundH077J EditorialK105L46M46N,Change 'registration respone' to 'SBC-RSP' OCut'n'paste bugP613VAcceptedZk) doneNB 2001/07/21EAntonisFKarvelasH078J EditorialK107L34M 6.2.2.4.30Y[NAChange 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-initBOn page 107, line 34: Dynamic Service Message Received messagePB 2001/07/21EKenFStanwoodH080J EditorialK108L41M 6.2.2.4.32NYOn page 108, line 41 change "CLPLT" to "CPLT" On page 108, line 49 change "CPLT" to "RSP"OTyposP517VAcceptedZk) doneQB 2001/07/21EKenFStanwoodH081J EditorialK110L60M6.2.3.4NChange "merge" to "pack"OnThis is the packing section, not the merging section. Let's not add a new term with subtly different meaning.P518Q Ken StanwoodRAcceptedVAcceptedZk) doneRB 2001/07/21ECarlFEklundH082JTechnical, Non-bindingK111L3M 6.2.3.4.1[]RAReplace paragraph 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. The SDUs are packed into the payolad of the MAC PDU without Packing SubB-headers. This is illustrated in . If the MAC SDU size equals n bytes, the receiveing side can unpack the MAC PDU payload as the size of it will be k*n, where k is the number of MAC SDUs packed into the PDU. "OKCurrent text is wrong as the length of the header is included in LEN 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.\^`RTtThe 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-ModifiedZk) done]_RAEdited to: "For connections that are indicated, by the Fixed-Length vs. Variable-Length SDU indicator (11.4.8.23), to carry fixed-length MAC SDUs, the packing procedure described in this section may be used. In this case, the Request/Transmission Policy (11.4.8.16) shall be set to allow packing and prohibit fragmentation, and the SDU size (11.4.8.24) shall be included in DSA-REQ message when establishing the connection."SB 2001/07/21EStanleyFWangGObserverH083J EditorialK111L18M 6.2.3.4.1N\Change the first field to read "n*k+6" instead of "n*6" and make the same change on line 28.O@The LEN field includes the size of MAC header, which is 6 bytes.P349Q Ken StanwoodRAccepted-ModifiedSAlso make the change on line 8.^`gSAOn 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-ModifiedZk) doneTB 2001/07/21EStanleyFWangGObserverH084J EditorialK113L40M6.2.3.6NChange "Recall" to "Note"OIt hasn't be discussed before.P350Q Ken StanwoodRAcceptedVAcceptedZk) doneUB 2001/07/21ECarlFEklundH085JTechnical, 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 StanwoodRAcceptedVAcceptedZk) doneVB 2001/07/21EVladimirFYanoverH086JTechnical, Non-bindingK115L1M6.2.5_aVADelete 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."AAs 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 capacity`bVB* 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 SupercededZl) none neededWB 2001/07/21ECarlFEklundH087JTechnical, Non-bindingK115L4N"Delete sentence ' The active ....'OWe have no active grants fieldP624Q Ken StanwoodRAcceptedS$Duplicate of a piece of comment 029.V SupercededZl) none neededXB 2001/07/21EKenFStanwoodH088J EditorialK115L39M6.2.5.3NzDelete the sentence in parenthesis starting "The BS can detect..." Through the word "However," of the following sentence.acXODebatable 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 SupercededZl) none neededYB 2001/07/21EAntonisFKarvelasH089JTechnical, Non-bindingK117L22M6.2.6.1NLI believe that the GPC mode must be removed because it offers no advantage. AThe GPC mode spends much bandwidth in the downlink when we have a large number of connections because the BS must send resource allocations for each connection. Also the use of a SS local scheduler is useful because it knows the real -time needs of each connection so it can more efficiently allocate the bandwidth to the individual connections. Also the deletion of the GPC mode will help the interoperability.P481QCESkDiscuss with group {While I agree with Antonis, we should discuss this with TG3/TG4 first. -Ken Stanwood}bdYU|Replace the paragraph starting on line 31 " Systems using the 10-66 GHz PHY defined in section 8.2 shall use GPSS mode." VAccepted-ModifiedZk) doneZB 2001/07/21EKenFStanwoodH090J EditorialK117L26M6.2.6.1NNchange "UL maps and more intelligent" to "UL maps and allows more intelligent"OgrammarP520QCERAcceptedVAcceptedZk) done[B 2001/07/21ERogerFMarksGMemberH091JTechnical, Non-bindingK118L1M6.2.6.2A'Check to see whether this resolution from LB#3 (applied to D2) was correctly implemented: On page 111, lines 4-35 replace the upper right 2 boxes and 3 decision diamonds in Figure 65 (after implementation of comment 739) with the same portion of Figure 66 (after implementation of comment 521).'@A* 33[  *O?To confirm completeness of resolution of Comment 790 from LB#3.P724Q Ken StanwoodR SupercededS!The figure appears to be correct.V SupercededZl) none needed\B 2001/07/21ERogerFMarksGMemberH092ce\J 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. Zl) none needed]B 2001/07/21EKenFStanwoodH093J EditorialK125L10M6.2.7.2N+Redraw Figures 40 and 111 in frame maker. O'They don't print correctly on some PCs.P521VAcceptedZk) done[^These were already FrameMaker drawings. Changed color to shades of gray; maybe that will help.^B 2001/07/21ERogerFMarksGMemberH094J 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."df^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-ModifiedZk) done_B 2001/07/21EKenFStanwoodH095JTechnical, Non-bindingK127L7M 6.2.7.5.3.1NOn page 127, delete lines 7-9.O4Priority Request multicast CIDs don't exist anymore.P522VAcceptedZk) done`B 2001/07/21EKenFStanwoodH096JTechnical, Non-bindingK127L43M 6.2.7.5.3.5NDelete 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.P523VAcceptedZk) doneaB 2001/07/21EKenFStanwoodH097J EditorialK129L54M6.2.8N7Change "dependent of the CID" to "dependent on the CID"OgrammarP524VAcceptedZk) donebB 2001/07/21ECarlFEklundH098egbJTechnical, 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 inB 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.' P614fhbAOn 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-ModifiedZk) donecB 2001/07/21EKenFStanwoodH099JTechnical, Non-bindingK130L31M6.2.8N@On page 130, delete lines 31-34. On page 300, delete lines 56-59OdThe decision to discard a PDU MUST be QoS and priority dependant, not arbitrarily set at 16 retries.P525VRejectedZl) none neededdB 2001/07/21EAntonisgidFKarvelasH100J 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 FramemakerVAcceptedZk) done[ Should be re-drawn in FrameMakereB 2001/07/21EAntonisFKarvelasH101J 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.P466VAcceptedZk) done[Left "ID" at the end.fB 2001/07/21EAntonisFKarvelasH102J EditorialK137L43M6.2.9.5NChange the sentence "store Basic Connection ID & adjust other parameters" as "recognize own MAC Address, store Basic Connection ID & adjust other parameters" in Figure 50.hjfOThe 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.P467VAcceptedZk) donegB 2001/07/21EKenFStanwoodH103JTechnical, Non-bindingK141L11M6.2.9.8N&Delete "unless explicitly told not to"OFAgreed last meeting that we always do authentication and key exchange.P526VAcceptedZk) donehB 2001/07/21EKenFStanwoodH104J EditorialK141L18M6.2.9.9N+Change "manageable.To" to "manageable. To" O missing spaceP527VAcceptedZl) none needed[ done in 105iB 2001/07/21EStanleyFWangGObserverH105J EditorialK141L18M6.2.9.9N$Change "ageable.To" to "ageable. To"OMissing space.P351VAcceptedZk) donejB 2001/07/21EKenFStanwoodH106JTechnical, Non-bindingK142L26M6.2.9.9NMLast state should now be "Establish IP Connectivity" instead of "Operational"O3Previously, we changed the order of initialization.P528VAcceptedZk) donekB 2001/07/21EKenFStanwoodH107ikkJ EditorialK146L38M6.2.10N&Change "(re-range)\." to "(re-range)."OtypoP529Q Ken StanwoodRAcceptedVAcceptedZk) donelB 2001/07/21ERogerFMarksGMemberH108JTechnical, 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-ClarifiedZk) donemB 2001/07/21EKenFStanwoodH109J EditorialK148L49M6.2.10.1jlvmNOn 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 StanwoodRAcceptedVAcceptedZk) donenB 2001/07/21ECarlFEklundH110JTechnical, Non-bindingK151L25M6.2.11N?Insert section from IEEE 802.16.1c-01/33 between 6.2.10 6.2.11OIssue needs to be clarifiedP625UPUse 802.16.1c-01_33r1.fm VAccepted-ModifiedZk) doneoB 2001/07/21EKenFStanwoodH111JTechnical, 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.P531VRejectedZl) none neededpB 2001/07/21EVladimirFYanoverH112J EditorialK155L4M6.2.11.3kmpNFigure 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)P657U2Change "0,N" to read "0,1" in figure 66 on line 6 VAccepted-ClarifiedZk) doneqB 2001/07/21EKenFStanwoodH113JTechnical, 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.P532VAcceptedZk) donerB 2001/07/21EKenFStanwoodH114JTechnical, 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.P533VAcceptedZk) donesB 2001/07/21EAntonislntsFKarvelasH115J 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.P496Upage 158 line 26-31 Delete "This is the case.... " through the end of the paragraph. Merge the remaining sentence with the next paragraphVAccepted-ClarifiedZk) donetB 2001/07/21EKenFStanwoodH116JTechnical, 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.P534motAReplace 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-ModifiedZk) doneuB 2001/07/21EVladimirFYanoverH117JTechnical, Non-bindingK159L33M 6.2.11.7.1N[Change the direction of the last three messages at the Figure 67Registration Message Flow AFigure 67 "Registration Message Flow "(p 159) illustrates the BS as the initiator of the DSA transactions for static SF's while in the section 6.2.9.12.1 "Service Flow Setup" p 145 line 53 we find: "After privacy is initialized, or after registration if privacy is disabled, the SS shall send DSA-REQ messages to the BS for to set up connections for the service flows listed in the configuration file. The BS shall respond with the DSA-RSP message"P659npuAOn 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-ModifiedZk) donevB 2001/07/21EAntonisFKarvelasH118J EditorialK159L35M 6.2.11.7.1orWvNChange 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 SupercededZl) none neededwB 2001/07/21EKenFStanwoodH119JTechnical, 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.P535VAcceptedZk) donexB 2001/07/21EKenFStanwoodH120JTechnical, 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-Modified>Pl3BUUX  $,.YesNo/,  , : AM PM HelveticaGenevaTimes New RomanArial psxYKen and Stanley to provide new diagrams Figure72.fm, Figure73.fm, Figure74.fm, Figure75.fm provided Figures 78, 79, and 83 :Carl will edit in framemaker. [provided]Zk) doneyB 2001/07/21EKenFStanwoodH121J EditorialK168L12M 6.2.11.8.2NChange "DSA-RSP" to "DSC-RSP"OtypoP537V SupercededZl) none neededzB 2001/07/21EKenFStanwoodH122J 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.P538VAcceptedZk) done{B 2001/07/21EAntonisFKarvelasH123J EditorialK174L17M 6.2.11.8.3.3N3Change the "Send RNG-RSP (abort)" to "Send DSA-REQ"OErroneous text.P492VAcceptedZk) done|rv|B 2001/07/21EKenFStanwoodH124J EditorialK174L18M 6.2.11.8.3.3N%Change "RNG-RSP (abort)" to "DSA-REQ"Ocut and paste errorP539VAccepted-DuplicateZl) none needed}B 2001/07/21EKenFStanwoodH125J EditorialK182L34M 6.2.11.8.4N$Change "connections" tp "connection"O[gramar, the article "a" makes the noun singular with multiple mutually-exclusive adjectivesP540VAcceptedZk) done~B 2001/07/21EKenFStanwoodH126J 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 typoP541uEXCOUNTER  DB G JU_isACE@ @ABWN A!C"E#[$ O% L&A'C(E)G*I+K,M-O.Q/N0U1O2S3@4A5C6A7A8C9A:A;C%G?*O@BA,JB.AC0JD1AE2NFBGDH4NI6AJBKDL7BM9ANBODPFQBSR<AT?EUAOVEVWINXKJYNAZO@[RA\T]A^SA_VA`BaXObYUc\Jd^OebJfAgdFhfOikJjmNkpNlsFmtAnuAovNpxYrr@@q!@t|Bs~Uv€Ow€Ox€Ny€ Rz€K{W|€F}€A~€A€B€R€!K€&K€*L€/H€2V€6OBDFHJLNPRTVXZA€9A€The right Timer here is the T14 not the T12 based on Table105.P494VAccepted-DuplicateZl) none needed€B 2001/07/21EStanleyFWangGObserverH128J EditorialK199L38M7.1.1N$Change "MAC sublayer" to "MAC layer"vx7€O.Change should have been made per comment #966.P352QCERAcceptedVRejectedZl) none needed€B 2001/07/21EStanleyFWangGObserverH129J EditorialK199L55M7.1.2NFChange "; i.e.," to ", i.e.," make the same change on page 200 line 1.OTypoP353QCERAcceptedVAcceptedZk) done[second change superceded by 131€B 2001/07/21EStanleyFWangGObserverH130J 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.P354QCERAcceptedVRejectedZl) none needed€B 2001/07/21EStanleyFWangGObserverH131JTechnical, 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."wy€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.P355QCERAcceptedVAcceptedZk) done€B 2001/07/21EStanleyFWangGObserverH132JTechnical, 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)P356QCERAcceptedVAcceptedZk) done€B 2001/07/21EStanleyFWangGObserverH133J EditorialK200L37M7.1.3N&Change "multiple SS" to "multiple SSs"OTypoP357QCERAcceptedVAcceptedZk) done€B 2001/07/21EStanleyFWangGObserverH134J EditorialK200L44M7.1.3NChange "an SAID" to "SAIDs"OTypoP358QCERAcceptedVAcceptedZk) done€B 2001/07/21EStanleyFWangGObserverH135J EditorialK200L48M7.1.3xz€NChange "must be" to "shall be"OTypoP359QCERAcceptedVAcceptedZk) done€B 2001/07/21EStanleyFWangGObserverH136J 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 ClarificationP360QCERAcceptedVAcceptedZk) done€ B 2001/07/21EStanleyFWangGObserverH137J EditorialK201L7M7.1.4NOChange "in section (Table 7.3)" to "in Section 7.3" and fix the cross-referenceOTypoP361QCERAcceptedU57V SupercededZl) none needed€ B 2001/07/21EStanleyFWangGObserverH138J EditorialK201L8M7.1.4N"Change "PrimarySA" to "Primary SA"OMissing space.P362QCERAcceptedVAcceptedZk) done€ B 2001/07/21EStanleyFWangGObserverH139J 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.P363QCEy{€ RAcceptedUDelete lines 20-26 VAccepted-ModifiedZk) done€ B 2001/07/21EStanleyFWangGObserverH140J EditorialK201L28M7.2.2NOChange the title of the section to capitalize the first character of each word.OTypoP364QCERAcceptedVAcceptedZk) done[5OK for now; must change back later due to IEEE style.€ B 2001/07/21EStanleyFWangGObserverH141J 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 hierarchyVRejectedZl) none needed€B 2001/07/21EStanleyFWangGObserverH142JTechnical, Non-bindingK202L19M7.2.2N,Change "will determine" to "shall determine"OThis is not an option.P366QCERAcceptedVAcceptedZk) done€B 2001/07/21EVladimirFYanoverH143JTechnical, Non-bindingz|€K202L19M7.2.2N