Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.05)@0inding@cthenormativereferencesectionisblank@@00allowedtheconcatenationoftheseparat@@0coincide@entity@inserttheworddownlinkbeforemodeaandotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijkQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJ>@ Cj%7.hal e-iJ.hj -Ek. l`l -mFxrogermarkspQmarksprogermarksBRmarksBrogermarksTmarksrogermarks@Umarks@roger marksmarksroger marks( i marks!(!roger  marks"0#q#marks$"0$ marks( i marks!(!roger  marks"0#q#marks$"0$DTDT €Editor's NotesEditor's Questions and Concerns€AEditor's Action Items€A€A€A Starting Line #€A Section€A  Fig/Table# @BA1BAj  !"#$%&'()*+,-./0234567j^_ `2a4bc d ijkmn.p+v"wx#y'{)€%€0€€€€1€€6leiOwang' *  wang * leiP wang wang ' leiQ wang VYwang VleiRwangwang YleiSwang wang leiTwang@nh&`wanghleiUwang b@3.1.1@*4.1.5.1@.4.1.6@&4.2.4@(4.5@+ @ @ @ @7@@VQ"‚f@U*Ã&P@K @J @K 9@AOKA/A0@@A-A.@A,A-Cancel@A*A+@@A* ;X( `Before importing, Find the records eligible for proposals by this Clause Editor. Only these records will be affected by the import. ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoQ:ASort by RecommenderE'` iDT_DT`DTDTDTQÃY0?ÃY@@ÃYPAÃY`BÃYpCÃYDÃYEÃYFÃZGÃZ HÃZ0IÃZ@JÃZPKÃZ`LÃZpMÃZNÃZOÃZPÃaQÃa RÃa0SÃa@TÃaPUÃa`ZBUUX  w  $,.YesNo/,  , : AM PMf  HelveticaGenevaVerdanaTimesMonacoTimes New RomanArialCourierSymbol Courier New@ A PICT,alisNAMEMSPCFPTHA9Macintosh HD:Desktop Folder:Ballot#2:802.16.2 Ballot Data9MSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataalisC-`@@XA Comment List@@*AAbout Commentary@@PACreate Comment@@fACreate and Submit Ballot@@AGlobal Field Setup@@ AEditor's Layout@@AComment List for Printing@@ AComment List for Projection@@ACommentary Version@@@AReply Comment Layout@@ ASubmit Reply Comments   A Comment ListB J  vor/ 11 against wRejected{l) none needed 2001/10/24»ETG3/4 MAC group^Technical, Bindinga6.2.XbFAdd new ARQ text found in document 80216abc_01/75 to the WG document. d339g2541wAccepted{k) done 2001/10/24 2001/09/11¼E TG3/4 MAC^Technical, Bindinga6.2.xb'Add a standalone NACK feedback message.d340g2542vneed accepted textwDeferred{l) none needed 2001/10/24 2001/09/13½E TG3/4 MAC^Technical, Bindinga6.2.xb Add RNR feedback message for ARQd341g2543vneed accepted text 2001/09/13D$aGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #{ Document #Report # B A € € € €€ €   G!MKe!MKG*fQjugD€QASDocument under Review€XAYLetter Balllot Number€^A_VoteaGlobal Field Setpb // etpb // etpb // etpb // tpb // b // b // d Setpb // Setpb // tpb // Setpb // b // ld Setpb // d(2) Save Data to Filee(3) Email Data Fileail Data File54 RB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMnD a w n w  $,.YesNo/,  , : AM PMo  w p w  $,.YesNo/,  , : AM PMq  w r w  $,.YesNo/,  , : AM PMs  w t w  $,.YesNo/,  , : AM PMu  w z w  $,.YesNo/,  , : AM PM{  w  D^"M1,,./: AM PMYyTtNnFfNALL OFMPRP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , AXLS Sheet1X5CMY m]oApFfWyHCB-wang., .lei]} A1FPTH=RPTH NAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9NFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9OFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A10FPTHXRPTHNAMEMSPCMSPCA2NAMEANumberLastFirst.USRRPTHANumberLastFirst.USRA19uFPTH^RPTHNAMEMSPCMSPCA2NAMEANumber_Lastname_FirstnameRPTHANumber_Lastname_Firstname ot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisVDEF(LISTLISTVDEF(LISTLIST(:K?@MRS Y!^"CAStartup scriptEQADelete Empty RecordsE@ @b*QA Show VotesE@@H-Already voted; submitting additional commentsQASort by Page/LineE'` _DT`DTDTDTQASort by Comment OriginatorE'` DTDT_DT`DTQADelete All RecordsE@ @b*QADelete Abstain CommentsE@ @HAbstain for other reasonsQAShow Editor's ProblemsE @'`@n* _DT`DTDTDTQASort by Comment #E '` dDTQ8 €Bied in recommending rejection on grounds of incompleteness or lack of a specific change request. (3) When you are finished entering replies, look under Scripts and choose "Find Marked Records". This will find the records for which you checked the "Marked" box. (4) Put your name in the "Recommendation by" field of each reply {for a quick method, see Appendix below.} (5) Under Scripts, choose "Export Clause Editor's Proposals". Choose the file type "FileMaker Pro Runtime Files". Enter a Cfile name of the form "BallotNumber_LastName_Firstname.USR", where "Name" is your name. (6) Email the exported file as an attachment to: --------------- Appendix: Using "Replace" in Commentary You can replace everything in a particular field over a batch of records. For example, clause editors might not want to type their name in the the "Recommendation by" field each time. Here is a solution to the problem illustrating the use of "Replace": *Finish entering your data. *Find the bacAEditor's LayoutB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMYesNo/,  , : AM PM Dp=u Av 2 72w27+-f3%:EAFAGA' Submitted by:€QASDocument under Review:UFirst (Given) NameVLast (Family) NameWBallot Group Membership Status:€XAY#Letter Ballot Number or Ballot Code€ZA[ email address€\A] telephone€^A_Vote:`(1) Create Comments€aAHCreate and Submit Working Group Ballot or IEEE Balloting Center CommentsH@AR  33& * Rg2*t {EQFAImport CommentsENALL OTABS# ` ABCDEFGdH^I_J`KaLbMcNOPQRgSiTjUkVmWnXpYvZw[x\y]{^_`abcde f g hijklmnoQGA Email fileE)?@ @A owner-stds-802-16@majordomo.ieee.org The comment file name should include the Letter Ballot Number and  ABCDEFGHIJK^L_M`NaObPcQ 456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ހށނރބޅކއވމފދތލގޏސޑޒޓޔޕޖޗޘޙޚޛޜޝޞޟޠޡޢޣޤޥަާިީުޫެޭޮޯްޱ޲޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ 'f€aA Create and Submit Reply Comments @A*  33*€APLEASE FOLLOW THESE INSTRUCTIONS EXACTLY OR EXPECT TO HAVE YOUR INPUT IGNORED. (1) Read the comments. You will probably find this easiest if you use the "Comment List" layout. You can choose it from the upper left corner of this window, or you can use this push button: (2) When you want to respond to a comment, check the "Marked" box at the top of that record. Then fill out the following fields: Recommendation: Proposed Resolution: Reason for Recommendation: You are fully justifing the buttons:€gng the buttons:€gng the buttons:€gg the buttons:€gicking the buttons:€gicking the buttons:€gowing steps by clicking the buttons:€ging the buttons:€gg the buttons:€ging the buttons:€ge buttons:€gbmit Ballot Filef9Proceed with the following steps by clicking the buttons:€gO+ A#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# cBl#[  bl[##KK##;;# Bmv#+  @iv+# >j# Dkv# 8w5 €\]Page€^A_Line€`A aSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A &'()+ €A €A €A€ARecommendation@@ByProposed ResolutionReasonSee reply details€A Fig/Table# BNA^  !"#$%*,-./0123^^_`u EDE^ "Technical, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, BindingG OKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !""Technical, Binding" comments are permitted only with the vote "Disapprove". You may submit comments of type "Technical, Non-binding". Please correct and try again.H) W()=0 W ABCDEFGHIJK^L_M`NaObPcQlEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf7# w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM     w  $,.YesNo/,  , : AM PMw w  $,.YesNo/,  , : AM PMf"$  w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PMf w $,.YesNo/,  , : AM PMf3IC dd5BDe5Bf#= q w $,.YesNo/,  , : AM PM     w $,.YesNo/,  , : AM PM          w  3  $,.YesNo/,  , : AM PM   {cTZbo|h[++ \_l)]l+ ^`l$)g_.?nAEditor's QuestionB GpA Editor's NoteB GvAResolution of GroupB GH vwADecision of GroupB GxAReason for Group DecisionB GyA Group's NotesB G{AEditor's ActionsB G€AGroup's Action ItemsB G€AEditor's Action ItemsB G€AVoterFirstNameB G€A VoterLastNameB G€A VoterEmailB G€A VoterPhoneB G€A VoterStatusG€A VoterStatus3m  ^ 3 $,.YesNo/,  , : AM PM_   `3 a d3 e3 f  3 g  3 t  3 u   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PM#39 XX+ASubmit Reply CommentsB  a   w   w $,.YesNo/,  , : AM PMf w w Aa#8 F mM5ft GM5ftM5ftGOC`E 7OC`EOC`E7 W   W   W    ÑÒÓÔÕÖרÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷{xBKA Enter commentEQMAImport Global DataENALL # @ A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcdefghijklmnopqQNAExport CommentsE:NALL OFMPR$@` ABCDEFGdH^I_J`KaLbMcNQkUmVnWpXvYwZx[y\{]^_`abcdefgh`DTDTDT A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcde0ZAmurakami@abadvanced@assignment@degradation@mechanisms@`options@wremovethedistinctionbetweenuplinkanddownlink@sreplaceitwithphase1numberschangedto3.0mbpsfor1.25@+the802.20macdesignshallspecifymechanismsetc@~toavailablewithinlessthan25ms@hc11@average@doesn't@example@insertbasedafter802.20document04-44thiscorrectsther@Aon@recommend@thetextinc802.20-04-44issomewhatdifferentinthissect@uplink@5where@j95@Tindicate@seecommenttoinitialcommentinthissection@k@Sagreed@order@supportforbroadcast/multicastserviceshasbeenwell-explo@thisappearstobearequirementonoperatorsof802.20-base@rpractice@tsuggested@Athistextisinformativebecauseitreferstotheend-to-end@yky@ geunnecessa@o@;u@QAAExport Full RecordsEOFMPR$@` ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^QCAAbout CommentaryEDQEAExport Vote & CommentsE6NALL OFMPRV D@]W@gFD@ @D@  ] W@ g F E@D@]W@gFFD@F$@`V0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsical, Bindinghh' Cw# ,v # 0x #  2y # s 2 @BBA0 0^_`ab c dijkmvwxy€€€             XXXX$XXXX2 X  X  X X& X'X(X)XXXXXXXX!X jv   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   h stanwood# >S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM(s%jAResolution ProposedB GkAReason ProposedB GmARecommendationB Gnndation 1B Gn1O RR 3  $,.YesNo/,  , : AM PMU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW w $,.YesNo/,  , : AM PMX w $,.YesNo/,  , : AM PM)@B@2@Ig@-g߀@0߷@&@di @ @@9P;;;P;;P;bleisnotreferencedinthetextnorhasitanymeani@dthetermburstprofileisdefinedinthestandardasdefinit@toclarifydocument@d@B@2A@@@cJ@c@M @ @3P;@3P; @3P; @3P;7WNWWWYWbWdWeWhWWWWWWWWWWWWWW)W/W5W8W=W>WBWDW`WhWmWWWWWW?WgapWWWW WW#W$W%WgenerateWgenerated4W6WWWWgeneratingWgenericWgetOWWWgetridofdashthisisaproblemallthroughoutsection6.2OV4/ RM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMBkS-X bWmkwj,AvCgE@!Sl€`zrAPFQKRPSUTZUBN@VhA~@M@LZ<>C @@@FIH@JQ3^&vmBD€QdnaD@Xbm{ACEe@EJoQTYB@X|CE@€ JOTYAC@XbmwBD@a@EJOU[B@|J& JQ 3 $,.YesNo/,  , : AM PMS   U   V   W   X 3 $,.YesNo/,  , : AM PMY   Z 3 $,.YesNo/,  , : AM PM[   \ 3 $,.YesNo/,  , : AM PM]   ]   No/,  , : AM PM]   1 RG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMw+#,v# 0x#  2 Ma bc dijkmvwxy!€€$€2'&()% @@@B s@A 3  $,.YesNo/,  , : AM PM77777777 7 7  7  7  7 7 7777777777771xy{€€€€€j77777777 7 7  7  7  7 7 7777777777771        Y7 ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   6" i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv    €Dtch of records in which you want to replace a field. *In browse mode, and put the cursor in the "Recommendation by" field. *Under "Records", choose "Replace". *Choose "Replace with calculated result". *In the box, write, in quotation marks, your name. Click "OK". *Click "Replace". @Af  ww    ww  ww  wwfSet up an email message for meGo to "Comment List" layout BnA€ (4^Technical, Binding_11`5a4.1.1d1g4188iTjwThis section and numbers has been reviewed and voted by the working group. Suggest not to touch the text at this time!mRejected-Duplicate 2004/07/025^Technical, Binding_11`5a4.1.1d2g4189i&Naguib, Sutivong, Tomcik, Yallapragadabeen reviewed and voted by the working group. Suggest not to change the text at this time.mRejected; @g@@b@bPI3Import Full RecordsExport Full Records Enter commentExport Vote & Comments Email file Startup script Delete Empty RecordsDelete Abstain CommentsDelete All Records Show VotesShow All Records in OrderSort by Comment #Sort by Page/LineSort by Comment OriginatorSort by RecommenderShow Editor's Problems Assign Editors#Mark Found Records%Unmark Found Records'Find Marked Records)Import Ballot Comments+Export Comments-Import Comments/ Export Clause Editor's Proposals1 Import Clause Editor's Proposals3Export Group Resolutions5Import Group Resolutions7Export Editor's Input9Import Editor's Input:Import Global Data< Help WebLink>WirelessMAN WebLink@Export IEEE XMLCOpen Reply Comment FileEAbout Commentary<AKEG  7   :UVWQNF89=>>9=>9gP:@K79@<E Q@ Q*E@uD QFGB{K@(MNxS@W@ZC[E\G]I^K_M`OaQbScUeW  A} !LISTAqVDEFEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEfterW=WcWWWallWalleviatebWallocationbWalphaWalsoWWWalternativeWalternativesWalthoughWbWalwaysbWanWareadWasWWcWWatW(WOWattributesWbandWbandsdWbandwidth(WbaseWbeWWW(WbWcWWbelowbWcWWerL> `Z   [w \ ]  ^ w  $,.YesNo/,  , : AM PMew h 3  $,.YesNo/,  , : AM PMi   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   ,  , : AM PMd   $ ANU#OV#V+X^5)SY{cTZbo|h[ +' \_l) ]D+b ^`l$)C_B+``al)a,maTbc -6cI dd De ]f)aTgvhYi< A_.^ -^; Pbj0=bi.  _l -d @/Tcj4A6XZB% K%[%K% %\%0E>]^% 7%e%D€B G€ AEmail ToB G€ A Email SubjectB G€ AEmail ccB G€A BallotNumberB G€A DocNumberB G€ACommentary VersionB G€A ExportDateB AbG€A Comment DateB G€ACommentary Version NotesB G€ACommentary Version DateB G€AMarkB G€A XML OutputB  B  " 0000000 87654321 "& & &""&""& ""&b&"" F€A Comment Type€ASuggested Remedy€ A Starting Page Number€ACommentXCreate CommentZDocument[Create another Comment\Create/Submit Ballot]In WG Ballot, "Binding" comnents are those which form the basis of a "Disapprove" vote. IEEE Balloting Center processes all Technical comments identically.€^AeShow All Comments€hAiSection€jAk Fig/Table#€lAmStarting Line # B?A6 6^_`abc€` a b cdX)*+,-.X()*+,-.X,-.XXolutionARecommendation byCRecommendation:EReason for RecommendationHEditor's QuestionsKEditor's Action ItemsN Group's Notes @B=Aayman@aymanarakjim@qdan@eshwar@hari@joanne@marc@@ganti@tomcik@hpark@gtomcik@yuza@2memberB^binding!)"editoria@editorial@technical@߫technicalbinding@ &technicalnon-binding@_@‚(@`p@‚*@k‚4@a4.1.11@Q4.1.2@|4.1.7@b@1addacaptioninline4table4-2blockassignmentsizes@18@ 2@2-1@+3-1@\4insertnewsubsection4.2.1.3radioreceiver@h5/1.25@802.20-based@afddanfdd@{amethodthatwillprovidemessageintegrityacrosstheair@account@oaddadefinitionforsimpleip@ addthe802.20systemshallprovidetheabilitytoefficient@addthefollowingtextinline28@baddthespecificreferenceinsection5and/orinafootnote@C2@ BD VOTEREMAILpDs`jA.nA%€B?€A€CC@======6_BdD`@4AFF*KL)QaA0@./////./////qq@@jAqcA%jBDkBZq@<jUq@q@qcMq@qcjqHBq@l_qkCq@qbAjBqjAfkAgq@vqcqboq@Pq@Giq@qPqjA q@qbq@abAqcr@Or=^6r@GprB@jA|rE@N^HrHPqrR@rSbjrT@jSril1rt@'r@Irl4r@bAjB[kA\ 2002-04-15Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15  w  $,.YesNo/,  , : AM PM  w AaBSn DyRoxp zqr srtyuB+zy*{QbSzaq@Hg@@PB s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMXY!€aACommentary Version@A* ww  ww*}Commentary Version # Version NotesCommentary Version Date B A€€€888r ysrtyuB+zw*{EV|GIU}n~pI~YjR[7iaGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #fFJ I 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK w  $,.YesNo/,  , : AM PMA%x  Yx% ^%  _l%@ l`l@% j%0  al0% cl%  bl@GY^6i7w"#$A=CEw€\€a@5BG4M1R/YOAC+'@€BD8, consequtive in time, of a preamble and data subchannels. --------------------------------------------- 8.3.6.3.5.2.3 should be handed to a clause-editor to be entirely rewritten. ItC needs substantial additional information on how to do this type of rotation in TDD, and it shouldn't use the word frame for allocations. How it will fit under the MAC etc.. (i.e. it needs definition on how this shifted superframe structure fits in with TX/RX boundaries)cH3  @BBA^_`abc€XXXXXXXXACreate and Submit BallotB    E 3 $,.YesNo/,  , : AM PMF 3 $,.YesNo/,  , : AM PMG 3 $,.YesNo/,  , : AM PM'   ^AAssign EditorsE 5 4 3 2 1 0 / . -  ,  *  )  (  ' & % $ "    !Q7AShow All Records in OrderE '` dDTQ8A Export Clause Editor's ProposalsE OFMPR$@` ABCdD^EiFmGjHkQ9A Import Clause Editor's ProposalsE NALL OTABSW@# `BBXXXXYYYYZZYYZZp` "Guillemette" GuillemetteQAAssign Editor 11E@[@!r@a11.@a11.@!r@a11.@802.16.1/D1-2000Q`"11"^52_ 8.2.1.2.5n'tuWdownstreamuWexistuW6M<?ACreate CommentB    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM   X , : AM PM      ~LA+Commentary: The IEEE 802.16 Comment ManagerA*by Roger Marks *@A> ww ) ww> AICreate and Submit Working Group Ballot or IEEE Balloting Center CommentsI@AR  33& + RN#Version: <<ACIABB>> (<<ACIABG>>)OView Comment ListA5For help, see 5@A> ww 4 ww>Xhttp://WirelessMAN.org B A   €€A>  ww    ww>AGo To Create Vote Page@A> ww  ww>UV sBl# #@  al@# cl#J  blJ# Bmv#:  @iv:# sj{#* Dkv*# 8w#,Cjv# 0x#  2y # 2# 6{#r Inr# qp# b LF 8w#/,v/# 0/ Y w $,.YesNo/,  , : AM PMZ w $,.YesNo/,  , : AM PM[ w  $,.YesNo/,  , : AM PMabcd€€€€€€€€€€€€rQ RA 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMPR RF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMx+!  2y! 4z! 6QS RK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3 $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMRT RP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMT 3 $,.YesNo/,  , : AM PMSU RU  w $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY 3 $,.YesNo/,  , : AM PMTN OZ 3  $,.YesNo/,  , : AM PM[  3  $,.YesNo/,  , : AM PMA#[ [#  # d# # #! #!#: #:#` `# ^#  _l#  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€              5 / 1  3       6  $"  & , ) +-*,6{7TypeReason k b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PM-dG | w  $,.YesNo/,  , : AM PM}  w ~ w  $,.YesNo/,  , : AM PM  w  w  $,.YesNo/,  , : AM PM  w A^a):|+=9}R~T=b=NR?+M^ance'd303 2001/08/28G6AReply Comment LayoutB U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]     [A, HH HH*<*G!!!!!!!!1111111111 11 11 11 9999 99999999BBBBBBBBJJJJJJJJJJJJRRRRRRRRRRZZZZZZZZZZZZ ZZ!cccc"cc#cc$cc%kkkk&kkkk'kk(kk)kk*kk+ssss,ssss-ss.ss/ssB0{{{{1{{{{2{{3{{456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmZ\ Cnopqr!!s11tBBuRRvccwssxyz{|}~D[] Ek0>nk&8n]n]n!=700UnUnUfa&fH!1fQ!H,bH,Hn\X8FU7=nXnH7%fQH 7k=8HnX10kHbHHgfn=\HX7X8HHf\]?no`_`_`_`_`_`_`_`_`_`_`_`_`_`B]n` [    `    `    `n&0n4WUfZ _ZZZ._ Z)$')d)$')d\^ G)')$h#`` ) )B)y}_ Z ' ' Dyy3sy~[_  )  ) B|uv7~qu|t_Z ( ( Brz}rs9|pr}up|_ ` ) ) Bzprypq~<yppy~pps`_ ' ' @rpp{upp|?vppuvpzZ[ ) ) Ezpt}rppyAsppr}~pr_ _ ' 'Bqp|ypvB~qpyxpz[ ` ) ) BHxpvups@|ptqpr_ Z # #@qp~}rpq~Iypq|ypz_ _E BEB`E BEBmE 'BEBmxpvyp|SX&&Xvpqpr` [  A Z Zqpy8=SHHspzZ _  @  `  `xpv,5^kn~qpr_ [[  _Z`l[  __Yo[ 6__[oqpqrpsbfS=X|pvzpy_ _ ' ) Bxpq}wpq}=]_ IXU7Uyp{zqppq`_ ) ' Bqppq}~p{=TW\fvpr}qppxZ [ ' ) DwppsspxfgT0spw}qpq`  _  '  'A~ppszpu08]n%7~qpp~}qpxZ _ BBEBm BBEBm 'BBEBmvpsppsHQH|ps}qq` [ `  ` _~psvq}Dyz~sx_ _  Z  Z [Jvu|{9to_Z_o__[Z__[^o__[Z__[^o_[^Z_`Z^o~v }~o_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`m`                                                                             @lBB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB^` K@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@B_ fXX]XfkJ78H7k=aXH 007U!,7kX8HXU7TT8X7TX77XXXf77`QHU8bk1TnaXfgWU77L7%7XX\ n17&7nbT] Xb!78=HUUXWUTX7 X7TY07=\7Xk Q%QX777b]1n=5n7H8Q!8nn_a M7!Qn=!H% 7TX,XfUXn,7,a bHb7jn &HU\TX$WT878gnn8H W8L7AUXHn8nH,H88N 7X&78=;XT%X7=7&0&0n, n!7HX00T(TXfnn777 H8& X7T7778n XTX778Tbkb H=X!`b O=T TXM*HU7T7&Q= 7Tn7%UW& XTX.7,n7&H%H8,X7gn7 TXT7A78nXH&=TXf7&Q7 PXTX 8n7]&]n7TX8jUQ TXU=n7\gn3n7XHUk=7,+U XTWUH87nn3X8WU77f78 TXUn= 7ac QU7U78&QQ XUX bfb7==nX17!8717W177&7nUT TWTH8fX&k8UUn7771 XUX77j&W7 WX bR8nH7 TXT\7&XUkH8U U77TX XTXn%88=&gC!\7 WX 77nXTUnfXTagWUTgWUTi)())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())(be S))())RZ                                                    B'S66SmB3BmK63BmVEBBPE.R8|o" *e VK S) i )}=}t<  K o  e   '~tFxy}qx ZV V)Pe2 6V R `vs|zWX!Q{ps}qq  <JR 3` )  A~psuTq}84n]H5}qpp}}qpx  ) _e Z ' o xpsppr5dngspw}qpqm  l <. Vqps~yptk]gX=upqzpy  I: . i J  B )3Sxppq}spwU7fU7xp{zpr V _  Z` l  ;   6qppq}}p{W=ef]{puzpz o  oZ  `2  "  `xpX $%       !ACommentary VersionB ( a w hh h h h h  h hhhhhhhhh!hh$XX,XXXX)X+X5X3c Uq}wpq}nf]1&}qpr 6  <`  ' _m N  */B 6qpqqpsH7Q78spz  lZZ ) `6   ' @_ xpuUQFupqpr V  `_  Z F  ) B qpxLxpr}zpz B ') Io  `P  " B xpwzqp{Q{puqpr BB' B e39 *@ qp~}spq}S}qppqyxpz@;)Bm e 'B  VzpvvpsQspps}qpsE '' R) Zi m   B; rp}zqppuUuppvvp|S  _6IN3_ )`EBmO '_ zpt}sppxQxpqz~ppt `R V)*NO @BYm  B 6rpp|vpp{P{ps}vp|6  ;  oB  E@` 3_zpszqq}L}qv|t oV NEBBZ m <rz}ssCtz~oI)"Ie6)6_cBB@@B@__@BlBB@l<)-V|vui [ w  $,.YesNo/,  , : AM PMA#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# c^_#  _l#  `l#m  av CgTgvh ivTjxivPk#TlPm&3Tn{&h3Po pDw6YTqp&3`Pr nTsj{tTuivcPvXTwmvPxTykvq~l6V~%AAbout CommentaryB\   A wB w I N w  $,.YesNo/,  , : AM PMO W  $,.YesNo/,  , : AM PMX $,.YesNo/,  , : AM PMPMPMPMPMPMPM   $,.YesNo/,  , : AM PM  w ` D .orgl>.;tf ZU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMk, w  3 $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz   {   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     rksa_2Wj m   n 3 $,.YesNo/,  , : AM PMo   p  w $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   '   B@\[)!r S // €TA€UA€VA€WA€XA YType€ZA[Suggested Remedy€\A ]Starting Page #€^A _Starting Line #€`AaSection€bAcComment€dAe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yA=AB=AB[Ab  !"#$%&'()*+,-./012345b& v   $,.YesNo/,  , : AM PMww   3 A0@*E0:@F {G0Z=' QkS%26U%92VLWiyl XU%92VLWiyl XXXXXX T BcAJ  !"#$J €€€ € €€ €      AGlobal Field SetupB   €€€ € €€ €           " # J  3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMs; VOTEREMAILVOTERFIRSTNAME VOTERLASTNAME VOTERMEMBERID VOTERPHONE VOTERSTATUS XML OUTPUT^abcgijkmnpvwxy{_`d    d  ^_`abcgimjkvwxy{p n!"#$%&'()*+ , - ./AMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line Number E !LISTAa) awaiting resolution b) awaiting missing input c) instructions unclear d) confer with resolution group e) editor disagrees f) pass off to other editor g) didn't have time h) defer to next round i) to do j) in progress - k) done l) none neededVDEFA((A!1>VDEF(LISTLISTAEditorial Technical, Non-binding Technical, Binding Technical (was Editorial) Editorial (was Technical) Technical, Satisfied (was Binding)VDEFA((A!VDEF(LISTLISTAMarkedVDEFA((A Comment TypeBMembership TypeCVoteDRecommendationFEditor's ActionsGComment Type/GroupHMarked`AFMRLFMRLAbb7AFMRLFMRLAdBFind DuplicatesC ReplyComments`lP <zReason for Recommendation{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes8Note: Group may also edit and export Comment Type above.€ADocument under Review:€ABallot Number:€A  Comment Date€A€A  Fig/Table# @BA5BAj  !"#$%&'()*+,-./0123467j^_ ` a bcdi"j k&m$n)pvwxy,{€€+€1€/€3€5€€6@@XB s@p.D/A First NameB GA Last NameB GAMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line NumberB GaASectionB GbAChangeB GcAReasonB GdAComment NumberB GM9999gACounterB GL4938iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. ,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl#.  .#  al# bl# 8w#,v#  2y# 2#v 6{v# In#f qC>pf# L WE@@MarkedQYAExport IEEE XMLEOTABS D[@!d$@`@A14[p 0 h[[ [[ /0 h[p / AQ^AOpen Reply Comment FileE ! FMPRQ'`QdDTQAzHHddE(HH(d'`zA'dE7*`'`+ dDTQ] w  $,.YesNo/,  , : AM PM  UU? €Ad?2     _` a ^@"7 c>gt;Z<lt;Z b>gt;Z<lt;Zd W2&&Zgt;>Zlt;<Z:GC€A VoterMemberIDB G€A ReportNumberB G€A FigTabNumberB GPRequirements Document v13Q2JimRagsdale Ericsson.commm.comom.com Youssefmirmike@arraycomm.com+1 202 669-400606066ot 802.20 SRD V13, comment cycle #2-7344mAComment List for PrintingB J  S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM X 3  $,.YesNo/,  , : AM PMY   \ 3  $,.YesNo/,  , : AM PM]   ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   $,.YesNo/,  , : AM PMa   a   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   l 3  $,.YesNo/,  , : AM PMl 3  $,.YesNo/,  , : AM PM Hm   n 3 $,.YesNo/,  , : AM PMo   p  3 $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   H{   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     esNo/,  , : AM PM       esNo/,  , : AM PM         3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM    C iTkTlGTPmn{Tn{ng{Po pw~Tqpn{_PrP{T|DnP}T~5ETy(5P#3"$1"2$L63C#0 AS T3C|U#3}C<V#3ACWDGW#X^H_UYGpW \_lHUn]GW ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$Tgvhz@@ B s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM xe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes€ADocument under Review:€ABallot Number:€A Comment Date€A€A  Fig/Table# BA(B$AP  !"#$%&')*P^_` a b dnpvwy {€€€$€"€&€(€€))f1234f01234f1234f1234f/@@ B s@A 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM$,.YesNo/,  , : AM PMo RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM MaSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uA vRecommendation by€wA xRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A Fig/Table# BAN  !"#$%&N^_`a bc dijkmvwxy!€€$€%%f1234f1234f1234f1234f1234f-./01234fo ZQ 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM T 3 $,.YesNo/,  , : AM PMU  3 $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PM OY 3 $,.YesNo/,  , : AM PMZ 3  $,.YesNo/,  , : AM PMA#x  x#  #h #h# ##X #X# # d# ^ #k  _lk#  `  @BBA* *^_` a b dnpvw y{€€€€€€           XX(X$X"XXXX& X X X X  X)X X XXX XXXXXIn # u L u#  @BBA( ( DmvkPx QdTykv zX{cTyKXPTwbk_+j)€UA€VA€XAYType€ZA [Suggested Remedy€\A]Page€^A_Line€`A ~PmRbapwcTsjtbTuiv4PvCTw A#x x#  #; d;# ##+ #+# ## #9  _l9#  `l# B#t  alt# ^# cl#  bl# Bmv#  @iv# >j#v Dkvv# 8w#f, EJG?W]IV<fS // €TA€UA€VA€WA€XA YType€\A ] Starting Page€^A _ Starting Line€`AaSection€bAcSuggested Remedy€dA  ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$Tgvh| AS T3C|U#3}C<V#3ACWDFoVX^HBUlY=TZbe[EmU \_BlHUh]WTbcHU3c3IC dd5BDe5Bf 0""/1"L1 B+``al)a,aTbc -6cI dd De ]fccTgvUbhT[biCHcTjxPkcTl~PmRbapwcTsjtbTuiv4PvCTw X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   ANU#OV#V+X^5)SYcTZbh[ +( \_l) ]I+g ^`l*)I_|  3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM       3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM QEy*PGTT{GiTPW^TpGT]PanPodTnn{P|/TFJEU `lHUEUalHdUEKUiHUF _<TR_P*OT   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    C3C#0aTjR_R_TivR]_PR_XTmvRz_P#D$wTkvTvTxP_<TR_P*OT  3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM       3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM3C S // €TA€UA€VA€WA€XAYType€ZA[Suggested Remedy€\A ]Starting Page #€bAcComment€dAe Comment #fComment submitted by:€ADocument under Review:€ABallot Number:€A  Comment Date€AProposed Resolution€ARecommendation by€ARecommendation:Resolution of GroupDecision of Group:€A€AReason for Recommendation8Note: Group may also edit and export Comment Type above.€A€A&Reason for Group's Decision/Resolution€AGroup's Action Items€A Group's Notes€AEditor's Actions€A Line #€`A aSection€bA cChange€dA ^w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM      esNo/,  , : AM PM       esNo/,  , : AM PM     @@B s@A 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM$,.YesNo/,  , : AM PM RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM RJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3 $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PM RO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM RT 3 $,.YesNo/,  , : AM PMU  w $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PM Y 3 $,.YesNo/,  , : AM PMZ 3  $,.YesNo/,  , : AM PM[  3  $,.YesNo/,  , : AM PM #=# ##- #-#_ ^_#  _l#  `l#m  a Hm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv   $,.YesNo/,  , : AM PMv   v   $,.YesNo/,  , : AM PMv   v   X1XXXX XXX X X  X2 X6 X4XX XXXXXXX"X#X'X%X)X+X.X0AComment List for ProjectionB   U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMSUAMark Found RecordsE[@!@A0"1jP l+  jP l_ jP m0*@ @@A lAABB l*"Marked"MarkedQVAUnmark Found RecordsE[@!@A$1jP l+  jP l_ jP m0*@ @@A lAABB l*""keQWAFind Marked RecordsAzHHHV E(HH(d'`zA'd b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMx(S@A :http://WirelessMAN.orgdocs/Commentary.htmlQ X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   e W y}zy kUa55nn!b,!n]bfHX7X8T=\=ngfGH\H\&&Tn=78f8QQ!f,8Qnbn=7X7U]nH&7]HQg0Hn,!]k&!XnbnXX88 7=n\n ]n7&fn7%g, @! %K 0Ձ9uNOOkA9O FPTH9RPTHalisNAMEMSPCMSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataI-5j:Aj,EjIN`PiSkXkZjB'[@_jejjkpkAmujxi|kjmރbjޅm ވcA g ދcAgލcAgސ^ޒcA#g"ޕcA'g&ޘj(ޚ-ޞ`1ޡi3ޣj6ޥbA9g8ާc=ީjA?>ެjDްGI޳cM޵bO޶jP޹bAWgV޺bBYDZc[gX޻ia޽cgbAlgk^rjtFyxEcBgBmcg^cAgcAgbAcBgcgj^bAgcAgbBgmbBn rd(2) Save Data to Filee(3) Submit Ballot Filef9Proceed with the following steps by clicking the buttons:€gAFile name must follow format: BallotNumber_Lastname_Firstname.USR (Extension is .USR) File format choice must be: FileMakerPro or FileMakerPro Runtime@AR  33  V  33r  R€tAWORKING GROUP BALLOT: Send email to: using the subject line: Make sure to: Attach file created in (2) Send manually if this button does not work.@Az    33%  &  33M  h  33z€uA €vA wShow All Comments€A@IEEE SPONSOR BALLOT: Upload using IEEE Balloting Center web form@@A*    33* not work.@work.@   337  R  33f3 ABCDEFG^H_I`JaKbLcMdNgOiPjQkRmSnTpUvVwWxXyY{Z[\]^_`a b c defghijklmnoklmnouMember ballot@wirelessman.org IEEE 802.16 Letter BallotBallot 2 802.20 Requirements Document V13C 2002-04-15 Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15ed "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new #* @Ftom0<߶߸߹ߺ1.1݃ރ߃ghi߻߼߽߾߿1.2jƒÃăŃ1.3AɃ=ǃȃɃʃ˃̃2KLWXowޗ̓΃σЃу҃ӃԃՃփ2.2MNDL׃؃كڃۃ܃݃ރ߃203.1dxޘޙEPQ|4.1.7r{ި˃4.1.7.1intu~ށނވޒީޫެޭޮޯްޱ޲޳4.1.8S޴4.1.94.2޺4.2.2޻4.2.3fpvމޓ޼޽̃Ӄ4.2.4޾4.2.6[|޿4.3qƒ4.44.4.1ހƃǃ4.5.1Z4.5.27;DFJVbj}ދޕՃ4.5.36:CGT\^aފޔԃ4.5.48+81 45 943 61021.55€A1.55: Added "Fig/Table Number" field Deleted XML file output option. 1.54: Added "Technical, Satisfied (was Binding)" to value list Comment Type/Group. 1.53: in Reply Comment layout, reduced display to three replies 1.52: *Changed instruction on saving files to specify .USR instead of .fp5 *Fixed bug that wouldn't allow exporting a ballot with no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create andB Submit Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new 85jiThis text has been reviewed and voted by the working group. Suggest not to change the text at this time.mRejected 2004/07/026^Technical, Binding_20`7a4.5.3d8g4190iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/027^Technical, Binding_19`34a4.5.2d9g4191iNaguib, Sutivong, Tomicikj%Same as comment 273 - Reject comment mRejected-Duplicate 2004/07/028^Technical, Binding_20`15a4.5.4d10g4192iNaguib, Sutivong, Tomcikj#Same as comment 97 - Reject CommentmRejected-Duplicate 2004/07/029^Technical, Binding_11`5a4.1.1d11g4193i&Naguib, Sutivong, Tomcik, YallapragadajQThis is a duplicate. See comment 1 submitted by Todd Chauvin. Same discussion. mRejected-Duplicate 2004/07/02:^Technical, Binding_20`7a4.5.3d18g4194iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate,: 2004/07/02;^Technical, Binding_19`34a4.5.2d19g4195iNaguib, Sutivong, Tomcikj$Same as comment 273 - Reject commentmRejected-Duplicate 2004/07/02<^Technical, Binding_20`15a4.5.4d20g4196iNaguib, Sutivong, Tomcikj#Same as comment 97 - Reject CommentmRejected-Duplicate 2004/07/02=^Technical, Non-binding_12`17a4.1.4d31g4197iNaguib, Sutivong, Tomcikj0Disagree, this is not implied in line 21/page 11mRejected 2004/07/02>_12`20a4.1.5d33g4198 2004/07/02?^ Editorial_23`5a5d40g4199i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/02@^Technical, Binding_16`15a4.1.10d51g4200i&Naguib, Tomcik, Sutivong, YallapragadajVWould like to see the previous definition and review before commiting on this comment.mRejected 2004/07/02A^Technical, Binding_?`6a1.3d71g4201iNaguib, Sutivong, Tomcik`isutivong5W6W7W8W9W:W;W<W=W?W@WAWBWCWDWEWFWGWHWIWJWKWLWNWOWPWQWRWSWTWUWVWWWXWYW]W^W_W`WaWbWcWdWeWfW߀W߁W߂W߃W߄W߅W߆W߇W߈W߉WߊWߋWߌWߍWߎWߏWߐWߑWߒWߓWߔWߕWߖWߗWߘWߙWߚWߛWߜWߝWߞWߟWߠWߡWߢWߣWߤWߥWߦWߧWߨWߩWߪW߫W߬W߭W߮W߯W߰W߱W߲W߳WߴWߵWtomcik5W6W8W9W:W;W<W=W?W@WAWBWCWDWEWGWHWIWJWKWLWNWOWPWQWRWSWUWVWWWXWYW]W^W_W`WaWcWdWeWfW߀W߁W߂W߃W߄W߅W߆W߇W߈W߉WߊWߋWߌWߍWߎWߏWߐWߑWߒWߓWߔWߕWߖWߗWW{jchange5WIWLWUW[W]WeWyWޘWަWWLW߶WWWzWWWchangeallthehookstospecificfeaturesUVchangehardtobreakbeforemakeVchangeincludingbutnotlimitedtotosuchas[VchangemusttoareޘVchangesofttomakebeforebreakandVchangethesentencetoreadtheaishallgracefullyreduceozVchangetitletorequirementsforieee802.20radiointerface߶Vchangetoshallspecifyitisameta-requirementonthespecVchangetothe802.20systemsmustbeshallsupportthedesigVchangetowillspecifyVmWnWsWtW|WށWނWރWކWއWމWލWަWެWޯWޱWWWWWWWWWWcommentsވWިWcommiting@WcommonalityWcommunicationsZWcompatibleހWcomputedgWconditionsޥWconsistenteWconstrainedgWconstraintWOWPWfromKWQWIW,Ej"Same as comment 97- Reject CommentmRejected-Duplicate 2004/07/02F^Technical, Binding_21`9a4.5.2d88g4206iNaguib, Sutivong, Tomickj$Same as comment 273 - Reject commentmRejected-Duplicate 2004/07/02G^Technical, Binding_21`17a4.5.3d89g4207iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/02H^Technical, Binding_21`25a4.5.4d90g4208iNaguib, Sutivong, Tomcikj dup of 157mRejected-Duplicate 2004/07/02I^Technical, Binding_11`5a4.1.1d91g4209i&Naguib, Sutivong, Tomcik, YallapragadajATable 4-1 contains values that have been debated and approved by the working group. For the technology to be significantly better than available, it is necessary to let the previous stand. Do not change the text, since it has been discussed and voted by the WG.k-Text has been debated and approved by the WG.mRejected 2004/07/024-1jnot4W5W=WIWLWQW[W]WgWޘWޣWާWީW޳W޶W޹WWW߀W߄W߈WߙWߣWWWWWWWWWnotnecessarytoremovefragmentstartingwithforthepreseV4WW߹WoccurZWoccurringZWofHWOWZWyWWރWޣWޤWޥWާWިWީWެW޺WWWWW WLW߄W߉WߙWߝWߞWߣWߴW߽WWWWWW3WKWNWSWvWWWWWofflineWofingvWokޘWޡWަWާW޲WWMWokexceptdellsshouldbecellsVokifoption4isselectedhoweveripreferoption3޲VoldZWon@WWWZWރWޡWިW޺WWWWW߀W߄W߉WߋWߔW߯WWFWvWzWWonceޣWoneWWzWވWާWޮW WoneoptionneedstobepickedratherthanonlyeliminatingޮV maccepted?Mdo{ބޅފތޗޙޚޛޜޝޞޟޠޢުޫޭް޲޴޵޸޻޼޾޿ƃǃȃɃʃ˃̃݃ރ߃ #&-.<=?ABDEIJNQSTVXYZ[\]^_`abcdehjkl|}߃߆߇ߊߋߐߑߒߕߗߚߛߜߢߤߥߦߧߨߩ߲߫߬߭߰߸ߺ߻߼ƒÃƃǃȃɃʃ˃̓΃σ҃׃  $%&./@ABCDIMPXimru~ಃೃഃൃใໃྃÃǃ˃̃҃ӃՃփ׃ AkseeAWkWlWmWnWsWtWށWނWރW WW*W2W3WqWWWWWW WWW%W&WAWGWnWxWyWWWWWWWWWWWWWWWWWWWWWWentonthissection2V3VseemyoriginalcommentރVseepreviousreplycomment*Vseereasonsforcomment2lVseereasonsforreplytocomment1kVseereasonsproposedforcomment3mVseereplyinrecord101tocomment31VVseereplyinrecord111tocomment3%V&Vseereplyinrecord139tocomment72AVseereplyinrecord143tocomment135whichwastodeletetGVseereplyinrecord181tocomment140nVseereplyinrecord194tocomment150xVyVseereplyinrecord206tocomment95VVVVVVVVVVVVseereplyinrecord223tocomment62VVkforAWNWiWkWlWmWrWuWwW|WހW WߎWWWWWWWWW W WW W!W"W#W*W.W1W2W3W4W5W=W`WaWeWkWpWtWvWWWWWWframevWfranklyWfreeWfromvWWWW߽WWWW WWWfull߶W*WfunctionalWWWfunctionalityWfurther߷WWWWWmimoSWmimoisamultiantennatechnologythatcanbeusedhoweveriSVminimumfWmobilefWhWmoreLWUWXWmorespecificlanguageUVmuchfWmultiantennaSWnativeKWnotSWYWofAWKWNWYWhWoneSWonlyAWSWoptionfWoption2ispreferabletotherecommenderswhile5microseconfVorKWYWotherKWhWoverKWXWpageAWparhWparagraphAWKWparticipantsNWenkasAWKWhWiWuW|WހWWW߷W߽WWWWWWWW*W>W?WpWWWWWWWaspects߶WWassignments*WWWWassociatedWassumes*WassumptionsWassurance!Wassured4WatހWWWWWW!W*W4WpWWattacksWauthentication Wavailable!W*W4WWWaverage3W=WavoidWb/s/hz/sectorAWback%WbadWbandWbandsqWbandwidth7W"W*W1W?WwWWisW#W4W5WbeAWKWSWYWfWhWjWpWvW|W}WހWWWWW%W7WKWߎW߷WWWWWWWWWWWWWW W WWW!W*W.W1W2W3W4W?WeWoWqWvWwWWWbecause߷WWWpWqWIJ^Technical, Non-binding_19`34a4.5.2d96g4210iNaguib, Sutivong, Tomcikj%See suggested remedy for comment 250mAccepted-Modified 2004/07/02K^Technical, Binding_7`7a2d106g4211iNaguib, Sutivong, Tomcikj*Remove "IP-based" from the first sentence.kAgreed that this paragraph should be informative. Suggest removing explicit reference to IP-based, since other types of traffic, such as "ethernet" or a native voice service could be carried over the future technology.mAccepted-Modified 2004/07/02L^ Editorial_7`15a2d107g4212iNaguib, Sutivong, TomcikjpAccept the paragraph with the following change: replace "including, but not limited to" with the term "such as"kVRecommended change makes this section more readable, and reduces the "legal-ese" some.mAccepted-Modified 2004/07/02M^Technical, Non-binding_8`14a2.2d110g4213mAccepted 2004/07/02N^Technical, Binding_8jrejectthecommentAVrelay߽WrelevantޘWWߩWrelevantreferencesorinformationneedtobeprovidedtospߩVmovalofsectioncanonlyfutherconfusionindefiningqosߞVremoveKWTWߔWߙWremoveip-basedfromthefirstsentenceKVremovethelastsentenceoftheproposedremedyߙVremovingSWreplaceLWWreplacetextforthesectionwiththebasestationshouldprVreplynWsWtWށWނWލWޯWޱWWWWWWWWWreportingWreportsWrequestUWrequireWrequiredQWrequirementgWW߄W߉WߎWߟWߠWߡWrequirementsNWޘW߀WߓWߔWߙWߞWߩWrequiresާWWߓWrequiresfurtherdiscussionVrequirmentWrequirmentsWresolutioniWkWlWrWuWިWߣWresourcesLWresultsWretainwWWretaintelematicswVV6nVtVcUWlW;/inaguibsutivongtomcikyallapragada5V9V?VBVIVPVߎVߏVߐVߑVߒVߓVߔVߕVߖVߗVߘVߙVߚVߛVߜVߞVߟVߠVߡVߢVߣVߤVߥVߦVߧVߨVߩVߪV߫V߬V߭V߮V߯V߰V߱V߳VߴVߵVnaguibsutivongtomcikyallapragadanaguibsutivongtomcikya߲Vnaguibsutivongtomicik7VnaguibsutivongtomickFVTVbVnaguibtomciksutivongyallapragada@VraoߝWraoyallaprnaguibsutivongtomcikyallapragadaagadaߝVN`14a2.2d114g4214iNaguib, Sutivong, TomcikjAdd a reference to 3GPP2's BCMCS Stage 1 document here as follows: "802.20 Broadcast/Multicast support shall meet all requirements as captured in http://www.3gpp2.com/Public_html/specs/S.R0030-A_v1.0_012004.pdf . "kSupport for Broadcast/Multicast Services has been well-explored in 3GPP2. This document contains high-level requirements agreed by a consensus of industry participants.mAccepted-Clarified 2004/07/02O^Technical, Non-binding_9`16a3.1.1d122g4215iNaguib, Sutivong, TomcikjA"Partitioning" is used here to stress that the border between MAC and PHY are well defined. However the way it is written gives the impression that this is the name of a particular model. Maybe we should suggest a rewording for the sentence that was stress the border between MAC and PHYmAccepted-Modified 2004/07/02P^Technical, Binding_11`21a4.1.1d127g4216ted-Clarified 2004/07/02+ aDTୃ4.5.1:XYஃ௃ః4.5.1.1Z[\]ృಃೃഃ4.5.27;DFJVbj}ދޕՃڃ^qൃඃසฃใ຃ໃ༃གྷ4.5.36:CGT\^aފޔԃۃ_`rzྃ࿃ƒÃăŃƃ!4.5.48WBWDWRWtWWWWWWWWWWWW W WWWWWWWWWWWWށkSee reply to comment #6mRejected-Duplicate 2004/07/02ނ^Technical, Binding_14`16a4.1.7.1d281g4266iAnna TeejSee reply to comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/02nnel. This handoff is characterized by commencing communications with a new base station on the same frequency before terminating communications with the old base station." "Hard Handoff: A handoff characterized by a temporary disconnection of the Traffic Channel. Hard handoffs occur when the moBbile station is transferred between disjoint "Active Sets", the frequency assignment changes, or the mobile station is directed from the Traffic Channel to another wireless system." 2004/07/02[^ Editoriald224g4227Active Sets", the frequency assignment changes, or the mobile station is directed from the Traffic Channel to another wireless system." 2004/07/02[^ Editoriald224g4227mAccepted-Modified 2004/07/02p(jcontainsIWcontentޤWcontextWcontinuousWcontributionRWiW~Wcontrol޷W WWcornerWcorrect޶WcostWcouldPWީW޷Wcoupled߈WcoverageߣWW3WwWcriteriaPWgWzWWcryptographic Wcurrent߀W߷WWWWWWWWWW WcuurentWdan޵Wdan'sެW޶WdataQWީW W߀W߉WߣWWW3WvWwWzWWWWdateWde-allocatingW@WPWZWWdefinitionsWdefintion޵WdegradationPWdegradeQWdelayߎWߟWߠWߡW߳WߵWdelaysWdeleteQWWdeletingޡWdellsWdenseߝWdependޡWިWdepends߉WdeploymentqWWdescriptiveޘWdesignWߙWdesignedgWޘWWdetailed޳WߓWdeterminedޤWdiff-servީWdifferentQWWߞWߴWdifferentiated~WހWejvChange values to be consistent with 2 b/s/Hz downlink and 1 b/s/Hz Uplink, Spectral Efficiencies, as adopted by the WGmAccepted-Modified 2004/07/02f_18`12a4.2.3d289g4238iNaguib, Sutivong, TomcikjAdopt Option 2. kOption 2 is preferable to the recommenders; while 5microsecond delay spread is the minimum that a proposal should be able to handle, proposers should plan that actual delay spreads in a mobile environment can be much larger.mRejected 2004/07/02004/07/02be 2004/07/02`^Technical, Bindingd276g4232iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02a^Technical, Bindingd283g4233iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/02beject CommentmRejected-Duplicate 2004/07/02bngd283g4233iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/02bd284g4234 2004/07/02kreadabilitylessjargon[VreadableLWreal-time|WrealistcallyWrealisticWW$Wreality WrealizeWreason#W3WjWreasonable$WreasonsiWkWlWmWuWrecommendationoWrecommendedLWrecommendedchangemakesthissectionmorereadableandreduLVrecommendersfWrecordWWWWWWW%W&WAWGW_WnWxWyWWWWWWWWWWWWWWWWWWWWWWreducesLWredundancyWredundantWWWWWW WrequestedWrequireWW߽WrequiredWWWrequirementAWhWvWWߎWWWWWWWWWW WWrequirementsNWhWiWpWrWuWWߥW߷W߻W߾WWWWWWWWrestހWWreviewedWWwdÃ9@azƃ!Ã9PbÃ9`c{Ã9pd|Ã9}<Ã9e~=Ã9fdQj157HWWWW180kW190ߣW194yW1xev-do߀W21/page=W220hWmW224|W2475~W250JWxW2597~W2598~W2737W;WDWFWVWbW3pWsWvW~WެW޽W1W3.1gW39ޯWޱW3gpp2NW3gpp2'sNW4~WއW޲W޳W4-1IW4.1.7ިW4.4.1ިW5~W6nWtW~WށWނW802.20NWQWxWހWWW802.20-basedLW978W<WEW_WcWa9WNWOWPWTWWWZWgWqWޣWާWީW޵W޷W޺WWWWWWW WHWUWableWabout޶WacceptLWކWaccepttheparagraphwiththefollowingchangereplaceincluLVacceptwithmodificationassuggestedinmycommentކVacceptableދWޣWWacceptedެW߀Waccess޷WWaccomodateqWaccordanceަWacrossQWWactiveZWaddNWPWYW/Dg^Technical, Binding_11`5a4.1.1d1g4239iAnna TeejOption 2 is preferable to the recommenders; while 5microsecond delay spread is the minimum that a proposal should be able to handle, proposers should plan that actual delay spreads in a mobile environment can be much larger.mRejected 2004/07/02g^Technical, Binding_11`5a4.1.1d1g4239iAnna Teej able to handle, proposers should plan that actual delay spreads in a mobile environment can be much larger.mRejected 2004/07/02g^Technical, Binding_11`5a4.1.1d1g4239iAnna Teejle environment can be much larger.mRejected 2004/07/02g^Technical, Binding_11`5a4.1.1d1g4239iAnna Teejds in a mobile environment can be much larger.mRejected 2004/07/02g^Technical, Binding_11`5a4.1.1d1g4239iAnna Teejeads in a mobile environment can be much larger.mRejected 2004/07/02g^Technical, Binding_11`5a4.1.1d1g4239iAnna Teej4/07/02O&^technicalbinding4V5V6V7V8V9V:V;V<V@VAVBVCVDVEVFVGVHVIVKVNVPVTVUVVVWVXVYVZV\V]V^V_V`VaVbVcVgVhViVjVkVlVmVnVpVqVrVsVtVuVvVxVzV{V|V}V~VVހVށVނVރVބVޅVކVއVވVމVފVދVތVލVގVޏVސVޑVޒVޓVޔVޕVޖVޘVާVޮVޯVޱV޳V޴V޵V޶V޷V޸V޹V޺V޻V޼V޽V޾V޿VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V V V VVVVVVVVVVVVVVVVV1miAnna TeejPlease see Comment #220k$See reasons proposed for comment #3.mRejected-Duplicate 2004/07/02n^Technical, Binding_14`16a4.1.7.1d16g4246iAnna TeejSee reply to comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/02o^ Editorial_7`3a2d21g4247iAnna TeemAccepted 2004/07/022-1p^Technical, Binding_17`16a4.2.3d59g4248iAnna TeejAdopt Option 3. kAJWith the other requirements defined in the individual sections of the SRD, it should be sufficiently clear that the system - including base stations' and mobile terminals' performance should meet all those requirements. This section is supposed to specify the type of channel environments under which the system needs to operate. Jm Superceded 2004/07/02q^Technical, Binding_18`35a4.3d65g4249iAnna Tee004/07/02 0߀jA The requirements on the DL and UL peak user data rates as stated in option 2 are too weak and should not be accepted. Current systems such as WCDMA and 1xEV-DO provide significantly higher peak user data rates and are much more in line with what's proposed in option 1. mRejected 2004/07/02߁^Technical, Binding_12`22a4.1.5.1d13g4521iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02߂^Technical, Binding_14`2a4.1.6d37g4522iNaguib, Sutivong, Tomcikj"Why is 0.9 chosen? Please clarify.mRejected 2004/07/02߃^Technical, Binding_16`29a4.1.11.2d55g4523iNaguib, Sutivong, TomcikjAgreed.mAccepted 2004/07/02߄^Technical, Binding_?`13a4.1.6d72g4524iNaguib, Sutivong, Tomcikj better than existing mobile cellular standards; 2) data rate requirements of the applications as listed in section 2. tmRejected 2004/07/02PrktheyYWWWWWWtheyareconsistenttherequirementappropriatelyappearsasVW WWW2W3W:WqW߶W߷W߾WWWWWWWWWWWWWWWWWWW WWW!W#W*W.W4W>WEWGWVWWWYW^W_WeWpWqWvWWWthisappearstobearequirementonoperatorsof802.20-baseVthisisaduplicateseeinitialreplycommentqVthisisanimportantmeta-requirementwhichhasbeenthesubVthisismoredetailedthanneededforthissectionVthisismoredetailedthanwhatisneededinthissectionVthisisnotarequirementontheairinterfacebutisinstea^VthisisnotaneditorialcorrectionasitallowsthestandarpVthisproposedrequirementismoredetailedthannecessaryweVthisprovidesmoredetailthanwhatisneededinthisdocumeVWkpeakhW*W3W=WperWW*W.WperformWperformancepWWWWW2WpWwWWWperformanceofthemobilestationsisalsodependentontheVphaseWphases1WphyWNWphy/rfWphysWphysical|W߾WpicoWplaceWWplacedWplanfWpleaseiWuWpleaserefertocomment216c802.20-04-55forthereasonswhiVuVpluseWpolicyWpossibilityWpossibleAWWpotentiallyEWpotentiallyonlyminimaldelayisexplainedbytheparenthetEVpowerwWWpractice WpracticessWpredictWpreferWWW!W"W'W(WSWfWkWZWWroption3butcanlivewithoption2SVpreferotherproposedsolutionsVpreferthesolutioninmycommentsVprefertodeletethesectionorretainoption3ZVpreferableXWfWߎWpreference.W1WVWWWkfutureKWWWW4WWgwWWW߽WWgalWgaming߽WgetWWgive*WgivenYWW#W*W=WvWgo&WWgoalWgoodWWgracefullyWgroupWWhandlefWhandoff|Whandoffs߷WWhappyWhard߷WharmonizeWharmonizewithothercommentsVhasIWNW]WހWWW*WWWWhaverWWWWEWWWheader WhelpsWhence"W#WWhighAWWWhigh-levelNWhigherWWWNWhope3Whow߷WWWWWWWWWWhoweWion2!VfVipreferoption2tooption1"Vipreferoption3'V(VipreferthecommentofdangaltofixthisVieeejW}WietfrWifWWimmediatelyWimpliedހWimplies|WimportantWWimproveߥWimultaneous%WWs^\knecessaryiWuWހWWWW3WWneedWW WWWWneedtosortouthigherlayerissuesegtheuseofrsvpfroVneededWWWW?WfWjWsWWneedspWKWWWWWWneedstobemergdwithothercommentsKVnegotiationNWKWNWYWhWjWpWwW}WހWWWWWWWW WonrW|WW WW2W3WoneSWWWonlyAWSWWoperatepWoptionfWrW!W"W'W(Woption2ispreferabletotherecommenderswhile5microseconfVoption3referstoanexpiredietfdraftforlatencyanderrrVorKWYWwW|WWWorderހWoriginalރWotherKWhWiWpWuWWWW WWFWoutWoutdoorvWoverKWXWownWpageAWparhWparagraphAWKWހWparticipantsNW2~ߗ 2004/07/02ߘ^Technical, Binding_18`33a4.3d64g4544i&Naguib, Sutivong, Tomcik, YallapragadajtSection 4.1.2 has already dealt with this aspect sufficiently and has been voted for approval by the working group. mRejected 2004/07/02ߙ^Technical, Binding_19`19a4.4d67g4545i&Naguib, Sutivong, Tomcik, YallapragadajARemove the last sentence of the proposed remedy. " The 802.20 MAC design shall support both FDD and TDD modes. It will take into account the architectual requirements of section 3.1.1 as well as the need for flexible, future proof design that would readily accommodate changes in the PHY layer as well as in upper layer. To the extent that performance is not taxed significantly, the MAC should abstract general purpose functionalities and keep the number of PHY-specific optimized functions tB o a minimum."rceded 2004/07/02Hjseesuggestedremedyforcomment250JVselected޲WselectionvWselectivityߩWsemanticWsender/recipient޹WsentWߖWsentoutatprescribedperiodicitiesaswellasߖVsentenceKWOWQWހWޘWޡWWWߖWߙW߽WWWWWjWnWxWzWWWWWWWsentencesWsentnceWseparateNWserviceީWWWWWWWservices~WހWLWWWWsessionWsessionsFWsetWsetsZWߞWߴWseveralNWshallNWxWWހWޘWWWLWߙWߝWWWWW WW3WFWNWvWwWzWWWWWWWWWWW WHWLWMWUW߀W߄WߋWߙWߪW2Wshoulddeleteandsystemarchitectureinbothlines3and132Vshown3WsideWsightWsignalWsignalingWWKWk216iWuW22WWWW22-23AW223WW224|W237WWWW243W247W3mWrWsW'W(WSW W%W&WZW31WWW35W3gpp2NW4.2.3W44WWWW5AW*W58W5microsecondfW6nWtWށWނW62WW68WWWW72AW802jW}W802.20hWiWrWuWހW߶W߽W߾WWWWWWWWWWWW"W*W2WpWWWWW802.20cannotplacerequirementsonapplicationsthatareabV802.20doesnotspecifyafullsystemonlythemac/phyaspec߶V802.20-basedW83 W90!W95WWWWWWWWWWWWWWWW WW!W*W2W4W5W=W>W?WEWNW^W`WaWeWjWkWoWpWqWtWuj:Please refer to C802.20-04-55 for the proposed resolution.kPlease refer to Comment #216 & C802.20-04-55 for the reasons why error rate and latency requirements are necessary for 802.20, as in many other wireless standards. mRejected 2004/07/02v^Technical, Binding_17`29a4.2.3d95g4254iAnna TeejAdopt option 3 as is.kThe last sentence is a requirement to ensure that an active call will not be dropped when the user walks into a building from the outdoor, and vice versa.mRejected 2004/07/02w^ Editorial_7`15a2d107g4255iAnna Teejretain: "Telematics".kA=Telematics include a wide range of applications for vehicular users. This may include some of the applications that are already listed, and some additional applications specific for the vehicular users, e.g., for emergency situation after an airbag is deployed, or, for vehicle maintenance related applications etc. =mAccepted-Modified 2004/07/02x4ߙksThe last sentence of the "suggested remedy" may not entirely describe the intent of the remainder of the paragraph.mAccepted-Modified 2004/07/02ߚ^Technical, Binding_19`4a4.4.1d68g4546i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/02ߛ^Technical, Binding_19`4a4.4.1d69g4547i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/02ߜ^Technical, Binding_19`4a4.4.1d70g4548i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/02ߝ^Technical, Binding_?`18a4.2.3d74g4549i6Rao YallaprNaguib, Sutivong, Tomcik, YallapragadaagadajaModify the first part of line 8 (for Option 2) as follows: "The system shall work in dense...."mAccepted-Modified 2004/07/02ߞ^Technical, Binding_14`16a4.1.7.1d80g4550i&Naguib, Sutivong, Tomcik, Yallapragadaj$kthepeakuserdataratemainlyreflectsthemaximumcapabilihVtheproposedrevisionchangesthemeaningfromwhatwasinte VtheproposedtextcouldbeinterpretedasthesupportofpicVtheproposedtextisfromtheparandalreadyappearsintheVtheproposedtextisinappropriateforarequirementsdocumetVthesecondpartoftheproposedremedyestablishesrequiremeVthespectralefficiencyrequirementisill-definedandoverlVthestandardcanonlybebasedonthetechnologyavailablea4VorkinggrouphasnotadoptedapolicyofdevelopingacVthenW.WtheoreticalWthereWWW߷WW W!W#WthereisnoexplanationoftheproblemVthereisnoreasongiveninthecommentaboutwhyoption2i#Vthereshouldbeconsistencybetweentheheaderandtheconte VtherebyWthereforeWWthese WߥWW"WthesechangesimproveclarityoftherequirementsߥV%kterminalspWterminolgy WterminologyWWterminologyalreadyincorporatedintoappendixaVtestableWWWtextIWXW]W|WWW߷W߻WWWWWWWWWWWWWWWWW5W>WIWNWWWiWkWqWtWuWWWWWWWWWWWWtexthasbeendebatedandapprovedbythewgIV]VtextisinformativeandusefulVtextseemsacceptableuVWKWLWSW]WfWhWiWjWpWrWuWvWwW|W}WހWWWWWWWWW$W%W7W:WGWNWߙWߥW߶W߷W߸W߻W߽W߾WWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWW7jtheseYWdW3WthesewerepreviouslyapprovedbyworkinggroupvotedVtheyFWthis4W5W9W=W@WOWTWZW]WyWރWވWޘWޣWޤWެW޶W޺WWWWWW WHWUW߄W߉WߓWߘWߪW߳WWW3WWWWWWthisisaduplicatecommentseereplytoinitialcommentVthisisaduplicatecommentseereplytooriginalcommentVdvotedbytheworkinggroups5VthroughputyWtime4W5W]Wto4W5W@WIWLWNWOWPWQWTWUWVWWWYWZW[W]WeWgWiWnWqWrWsWtWuWxWyWހWށWނWޘWޡWtodd9WtopicZWtouch4WtrafficZWtransferredZWtransmissionsyWtransmittingZWtxt~Wtypo{WunderstandingޣWupxWuplinkeWupperyWuseRWWuseoption2injointcontributionRVfjpleaserefertocontributionc802.20-04-55fortheproposediVpleaseseecomment220hVmVplenaryߓWpluralize WpointyWpoliciesWpollingWpopulationWpossibleZW޹WWWpowerwWWWprecludeWWWprecludingWprefer޲W޽WWWprefertodeletethesectionVpreferenceWpreferenceistodeletethesectionVpreferentialFWpreferredOWpreferrenceެWprescribedWߖWpresentWpreservationWpreserveWprevious@WIWWWpreviouslydWprincipleWprintsWprioryWprobabilistic߄WprobabilityMWprobabilityisokbutnumbershouldbeasproposedinmycomMVmendTWrecommendsރWreducedgWreferiWrWuWreferenceNWPWreferenced~Wreject6W7W8W:W;W<WAWCWDWEWFWGWVW^W_WaWbWcWx^Technical, Binding_9`7a3.1d118g4256iAnna Teej5The 802.20 AI shall support mobility up to 250 km/h. mAccepted-Clarified 2004/07/02y^ Editorial_11`7a4.1.1d125g4257iAnna TeejAdopt this remedy with the following modifications: (i) Specify which measurement point in the upper layer, e.g., MSAP; ii) change "throughput" to "goodput" to avoid the inclusion of error transmissions. mAccepted-Modified 2004/07/02z^Technical, Binding_13`5a4.1.5.1d130g4258iAnna TeejSpecify an alternative fairness criteria, e.g., the one used in the evaluation criteria methodology or any other appropriate ones. 2004/07/02{^Technical, Binding_14`9a4.1.7d136g4259iAnna Teej8Adopt the suggested remedy with typo fixed: "individual"mAccepted 2004/07/02|^Technical, Binding_18`24a4.2.6d152g4260iAnna Teej,See Comment # 224 for the alternative text.d118g4256 2004/07/02jreview@WߓWreviewed4W5W]WreviseWWrevisesentencetoreadthe802.20standardshallspecifyaVrevisesentencetoreadthe802.20standardshallsupportenVrewordingOWrfWߓWvWrfc~WrightWroute߽Wsame6W7W8W9W:W;W<WCWDWEWFWGWQWZW^W_WaWbWcWߣW2WNW\WpossibledefinitionisbZVsameascomment155rejectcomment6V:VCVGV^VaVsameascomment273rejectcomment7V;VDVFVbVsameascomment97rejectcomment8V<VEV_VcVscalableqWscenariosWschemesߣWscreenWsecondޘW߽Wsection4WTW]WgWWރWWWߓWߔWߘWߙWߞWߪW߯WߴWsection4.1.2hasalreadydealtwiththisaspectsufficientlߘVsection4.1.3alreadyspecifiestheairequirementsonfddaߔV߯VsectorWktelematicsincludeawiderangeofapplicationsforvehiculawVtemplatesNWtenseWWtermWterminalWW WpW|kThis section implies some near real-time measurement on the physical link which are essential for link adaptation or handoff pruposes. The section should be kept with modifications to the text as proposed in comment # 224 .mRejected 2004/07/02}^Technical, Binding_20a4.5.2d158g4261iAnna TeejKeep option 2 ktTo be consistent with the architecture of IEEE 802 standards, and to allow better flexibility in service variations.mRejected 2004/07/02~^Technical, Binding_14`22a4.1.7.1d179g4262iAnna TeejArThe text for Option 1 was proposed in January's meeting in the contribution: C802.20-04-18r1. The referenced documents are listed as follows: 3. RFC 2475, "An Architecture for Differentiated Services" 4. RFC 2598, "An Expedited Forwarding PHB" 5. RFC 2597, "Assured Forwarding PHB Group" 6. http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-classes-01.txt rmAccepted-Clarified 2004/07/02#jnameOWnature߄WnecessaryIWWneedQWWWޤW޶W޹WWߙWߞWߩWߴWneededWneedsޥWޮW޺WWKWOW߉WߎWߟWߠWߡW߳WߵWWWneedsadditionalclarificationVneedsfurtheridscussionOVneedstobemergdwithothercommentsKVnegotiateNWnegotiatedNWneigboringWneitherWnetworkހW Wnetworks߽WWnewZW޵WJWnoWnoiseWnon-lineWnon-secure޷WnorWjmsapyWmtsWmuch߀Wmulti-antennalWmulticastLWWmultilpierޥWmultiplayerWmultipleWWmustޘWWmutually߈WmyރWކWވWމWަWWW!WMWn3޲WNjimplied=WQWimply޷WimportantWimportedWimpressionOWimprovement Win=WNWRWZWgWqWyWzW~WކWއWވWމWޘWަW޺WWWWMW߀W߄WߙWߝWߞWߣWߴW߹WWWWWWW0W2W3WJWLWNWOWRWSWTWUW[W\W]WbWcWdWkWwWyW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWin-bandWinabilityWincludeޣWW WwWWWincludingLW[WހWWinclusionyWincomplete߉WincreasevWzWincreasingߣWwWindependent3WީWެW޲W޳W޶W޷W޺WWWWWWWWW WMW߂W߄W߉WߙWߣWis/wasޘWissue WWjadoptthisremedywiththefollowingmodificationsispecifyyVadoptedeWWadoptingKWaffectWaggregateWagreeLWagreetoeitherdeletethesectionortousethetextinrecLVagreedW߃߆߇ߊߋWߧW߭agreed802.20-basedsystemsshouldbeatleastonparwithoߋVagreedthewordmoderateisvagueߧVagreedtoinprincipleVaixWߔWߣW߯WW3WvWwWzWWWWWWairހWWWWWWallNWUW߄WWFWNWWWallocatedWWallocatingWallocationwWallow޹WWallowedWallowsWalongWWWWand/or߽WanotherBWZWanotherduplicateBVantennaWanyzWWWߓWappear߹WappearsޥWapplicableWapplicationsWapply WappropriatezWߣWapprovalߘWapprovedIWdWarbitraryޥWarchitectualߙWW^Technical, Binding_16`10a4.1.9d185g4263iAnna TeejReplace text for the section with: "The base station should provide antenna diversity, but the standard shall neither require nor preclude the use of antenna diversity at the mobile stations."kClarified textmAccepted-Modified 2004/07/02ހ^Technical, Binding_19`8a4.4.1d240g4264iAnna TeejKeep the first sentence: "The 802.20 air interface shall support the IETF Differentiated Services (DS) Architecture to be compatible with other IP network standards including IP mobile standards. " kA The first sentence has already implied the rest of the paragraph. In order to better support end-to-end QoS, it would be necessary to take into consideration the mechanism for QoS support at the IP network layer, as 802.20 is an IP-based wireless access link standard.  mRejected 2004/07/02ށ^Technical, Binding_14`16a4.1.7.1d271g4265iAnna TeejSee reply to comment #6EjfrequencyZWWߔW߯WfromKWQWZWWWWWWNWWftpWfullWWfunctionalitiesߙWfunctionsߙW>kinAWNWYWfWhWiWjWpWuW|W}WހWWW W:W߷W߻WWWWWWWWWWWWWWWWWWWWWWWW"W#W%W&W*W1W=W?WAWEWGWIWWWYW_WiWnWqWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWntentߙWinterfaceWWWWWWinterfacesWinternallyWinteroperabilityWinterpretedWWintovWހWintroductionWipXWrWހWWip-basedKWހWisAWSWXWfWpWrWvWwWހWWWWWWW:WqWߎW߷W߾WWWWWWWWWWWWWWWWWWWWWWe?#kbeenIWNW]WWbeingW%WWW"WWWbelieveW߽WWW WWeWWbenefitWbenefitsWbestAW WsWbetterhWjW}WހW߶W߸WW3Wbettertomaintainconsistencythroughoutthedocument߸Vbetween߽WWW W=WpWbeyondWW4WWblock7WW*WWWWbooktWboth WpWWWWWbroadbandWbroadcastWbroadcast/multicastNWbsWbuildingvWburstyWbutSWWWWWW W1W^WoWWbyIWNW]WWWWW!W3WEWWWbydeletingthistextitcouldbeinterpretedthatthespectVpWW W7WclarifiedWWclarifiedtextVclarifyingWclarityߥWWclassWclassesWclassified߷WclearpWrWWWWcommonWUcjdirectedZWdirectlyWdisagree=Wdisagreethisisnotimpliedinline21/page11=Vdiscard޼Wdiscardoption1޼VdisclosureWdisconnectionZWdiscuss޶WdiscussedIWgWdiscussion9WWߓWdisjointZWdispositionޤWdisruptionWWdistinguishNWdiversityWdividedWdl߀WdoIWTWޘW޳WdocumentNWPWW߹WWdocumentation޺Wdocuments~WWdoesޣWޥW߳WWdoneWWdownlinkeWߣW3WvWwWzWdownloadWdownloadingWdsހWdue߄WdupHWdupof157HVduplicate9WBWޕWWߏWduplicatewithcomment7ߏVdynamicWegWyWzWޮW߽WWWFWNWe-mailWeach޺WWNWearliergWeditor޵Weditorial WeffectiveWeffectivenessWefficiencieseWefficiencygWߣWWwWsedެWg~WCރEToddFChauvinGMember^Technical, Binding_11`5a4.1.1comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/02ރEToddFChauvinGMember^Technical, Binding_11`5a4.1.1comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/02ރEToddFChauvinGMember^Technical, Binding_11`5a4.1.1er support end-to-end QoS, it would be necessary to take into consideration the mechanism for QoS support at the IP network layer, as 802.20 is an IP-based wireless access link standard.  mRejected 2004/07/02ށ^Technical, Bindingd271g4265iAnna TeejSee reply to comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/02ނ^Technical, Bindingd281g4266iAnna TeejSee reply to comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/02ރEToddFChauvinGMember^Technical, Binding_11`5a4.1.1r^Technical, Binding_11`5a4.1.1g4267 2004/07/02߳^Technical, Binding_17`29a4.2.3d272g4571i&Naguib, Sutivong, Tomcik, YallapragadajYThe requirement for minimum delay spread needs to be specified. Option 2 does this well.mRejected 2004/07/02ߴ^Technical, Binding_14`16a4.1.7.1d281g4572i&Naguib, Sutivong, Tomcik, YallapragadajARemoval of section can only futher confusion in defining QoS requirements and in evaluating the performance of QoS for various proposals. Need to have requirements to be able to have specify different packet flows different sets of attributes for different types of traffic. @A* 33  33*mRejected 2004/07/02ߵ^Technical, Binding_17`29a4.2.3d282g4573i&Naguib, Sutivong, Tomcik, Yallapragadaj>The requirement for minimum delay spread needs to be specifiedmRejected 2004/07/02߶EEshwarF Pittampalli^ Editorial_0`0a0u^technicalnon-binding=VJVMVOVQVRVޚVޡVޢVަVީVVVVVVVVVVVVVVVV\V]V^VaV߻VVVVVVVVVVV VVVV>VBVDVRVtVVVVVVVVVVVV V VVVVV_<߶߸߹ߺ Ƀʃ˃̃߾ăǃɃʃ@K`݃ރ߃=ghij߻߼߽߿ƒÃŃƃȃ˃̃KLWowޗ̓΃σЃу҃ӃԃփMNXdޘDELPQ|Ճ׃؃كڃۃ܃݃ރ߃҃‚(ޘޡ‚)ޛޥ‚*ޤީ‚1ޢޣ‚2ޫ‚3ޅކއޏސޑެσЃksupportforbroadcast/multicastserviceshasbeenwell-exploNVsupportedWWWWWsupportsWWsupposedpWsystemhWpWW W߶W߽WW!W*W2W3W=W?WpWWsystems߶WWWW*WWtableAWW*Wtable1-1isincludedforinformationonlyseeexanationinAVtakeހWtakenWtakingWtargets*Wtbe*Wtbeperuserpeakdatarateisdependentonthespecificair*VtbrseWtddWWWtechnical4W5WtechniqueswWtechnologiesAWW!WtechnologyKWSWW!W4WtelecommunicationsWtelematicswWWksupportforbroadcast/multicastserviceshasbeenwell-explo@telematicsincludeawiderangeofapplicationsforvehicula@terminals@than@the@N:thecommentdoesn'tdescribeaproblemwiththecurrenttext@thecurrenttextisusefulforfurtherclarifyingthescope@thepeakuserdataratemainlyreflectsthemaximumcapabili@thesuggestedremedyisincorrectthisdocumentprovidesthe@they@things@Pthissectionimpliessomenearreal-timemeasurementonthe@thoughthisisnotatestableperformancerequirementitis@Atobeconsistentwiththearchitectureofieee802standards@understand@-weneedtogettoarealisticsetofqosclassesthatcanre@were@with@m@accepted-clarified@#accepted-modified@rejected#rejected-duplicate@superceded@€marked-kwithAWhWjWpW|W}WWWWW W)WFWKWNWSWWWWWWWWWWW W WW5W?WMWNWPWeWWWWWwiththeotherrequirementsdefinedintheindividualsectiopVwithin߽W^WwithoutWeWword:WWwordedWwordingWWworkW4WworkingWWwouldހW7WWWWWWWwrittenWWyetWރbSpecify 2 bits/sec/Hz/sector as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved. cAThis requirement specifies stringent spectral efficiencies without explicitly clarifying the conditions under which it should be achieved. For example, because cell size is not constrained by the requirements, the spectral efficiencies could be achieved with very small cells. Or, for example, operation at 120km/hr is very different depending on the environment - certainly we are not interested in operation at 120km/hr in an urban setting, yet the requirement could be interpreted that it iBs applicable under all channel conditions. The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.d1g2252iKlerer 2004/07/02 ރjaSee my comment on this section taht recommends we stay with the PAR value of 1 bits/sec/Hz/sectorkSee my original commentmRejected 2004/07/02MarkedބEToddFChauvin^Technical, Binding_11`5a4.1.1b5Remove the distinction between uplink and downlink. c The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.d2g2253iKlerermAccepted 2004/07/02MarkedޅEToddFChauvin^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2cA3Option 1 peak rates result in a large user data rate peak to average ratio of the order of 10:1 and will rarely be seen in practice (see C802-20-04-33r1). We should therefore not artificially limit proposals to large peak data rates whose sole purpose is specs-manship and will rarely be seen in practice. 3d3g2254iKlerer 2004/07/021^0bspectralރWލWޢWޣWޥWWWWWWWWLWkWtWWWWWWWWWWWWWWW*WwWWWWWWWspectrumWWWWWspeed޽WWWWFWWWWWWWWspeedsWWWFWWWWWWspreadWWspreads޽WWWspurious޺WqWWsserviceWWsslWWstability޺WqWWތWލWގWޖWޗWޙWޚWޛWޟWޡWޢWޣWޤWޥWާWުWޫW޳W޴W޵W޶W޷W޸W޹W޺Wthese޺WthisރWވWލWޒWޥW޳W޵WthroughތWޖWthusޣWާWtoރWލWޘWޜWޞWޠWޢWޤWަWާW޲W޴W޸W޹W޺Wtoavailablewithinlessthan25msަVtopic޳WtrafficީW޲W޹Wtransmitter޺WWcitރWލWޚWޮW޺WWWWWWW4W>W@WCWGWMWOWRW^W_WbWfWkWtW߾WWWWWWWWW W.W0W1W2W3W4W5WDWHWVWeWfWqWtWzW{WWWWWWWWWWWWWW WWWWWWitisbettertospecifythesystempeakdataratesinsteado3VlatencyވWޒW޳WWWCWlaterGWlayerވWފWދWޒWޔWޕWWWWWWWWWWW5WXWlayers]WleastGWleaving(WlessWlet'sTWlikeWWW_WlikelyWWlimitޅWޏWWlimitationWlineޠWޡWެWޮWޯWޱW޼WWW,W@WiWline6isduplexingschemesޠVlinearityNWTWlinearlyާWlinesޘWްWW0WD|cuplinkރWބWލWގWWWW@WkWlWtWuWWWWWWWWWWWWWzWWWWWWWWWW Wupon޵WWupperWWWWurbanރWލWWAWkWtWWWWWWWWWWWW<WAWQW_W߸WWWusefulޮWTWuselessޮWuserޅWފWޏWޔWWWWWWW&WGWOWgWmWrWvWzW߿Wuser's>WusersWusingWusually_Wv12fWv13fWvagueޚWWWWvagueqosneedmorespecifityVvalueWWvariousCWWvaryUWversion޵WversusރWބWލWގWWWkWlWtWuWWWWWWWveryރWލWWWWCWFWkWtWWWWWviaLWWvideoGW@ kconsensusNWconsequential0WSW_Wconsequentialsinceacceptingthiscommentrequiredacceptin_Vconsequentialtopreviousreply0VSVconsiderationހWkWconsistency߸WW WWconsistenthWjW}W)WWWWW WWconsistentwithrfc)VconsistentwiththeparVconsistentlyWconstantWconstitutesWcontainsNWcontents Wcontext:WcontigousWcontiguous:Wcontiguousisdefinitleynottherightwordinthiscontext:VcontinousWcontinuousWcontinuousisthecorrectwordthishastodowithmaintainiVcontradictoryoWcontributioneWcontributionc802.20-04/55wasincompletewithmanytbrsplueVcwWethernetKWexanationAWexistingAWhWexpiredrWexplanationWexplicitKWextensiveWfeatureWfirstAWހW%WfixWflexibilityjW}WflowWfocusrW ޅmAccepted 2004/07/02MarkedކEToddFChauvin^Technical, Binding_12`22a4.1.5.1b#Remove option 1 and adopt option 2cfThe concept of bandwidth must be clarified given that we are not requiring specific channel bandwidthsd4g2255iKlererj3Accept with modification as suggested in my commentmAccepted-Modified 2004/07/02MarkedއEToddFChauvin^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d5g2256iKlererjAs in comment 4mAccepted-Modified 2004/07/02MarkedވEToddFChauvin^Technical, Binding_14`16a4.1.7.1bRemove this section. cg4272 2004/07/02uFctheconceptofbandwidthmustbeclarifiedgiventhatweareކVސVVnVwV%V(V,V7V:VVVtheconceptoftwophasesisill-definedއVޑVVoVxV&V)V-V8V;VVVtheconstraintsonthetimeinwhichachannelneedstobeaAVVn802standardneedtoberelabޛVVthelineisconfusingandneeedtoberewrittenitseenstha@Vthemaximumchanneldelayspreadcouldbemuchhigherthan5JVtheparametersandmetricscannotbeproperlydefinedbeforeVthephrasescaleslinearlywithsystembandwidthisinadequaާV?VthephraseshallbedesignedinamannerthatdoesisnotaZVthephysicallayerprovidesetcnotclear5VtheqosrequirementsinthedocumenttodayegdiffservflexiވVޒVVVtherequirementaspreviouslywrittenallowsbroadcastviauLVVtherequirementsshallconformtotheparifnottheparneeV߻V ވg2257iKlererjHEither this option or the one specified in my comments will work for me.mAccepted-Clarified 2004/07/02MarkedމEToddFChauvin^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d7g2258iKlererjSee modification in my commentmAccepted-Modified 2004/07/02MarkedފEToddFChauvin^Technical, Binding_20`7a4.5.3bRemove sectioncThis is a feature of the user terminal and backend infrastructure and is irrelevant at the MAC/PHY layer. In addition, the need for high priority should be captured within QOS frameworkd8g2259iKlerermAccepted 2004/07/02MarkedދEToddFChauvin^Technical, Binding_19`34a4.5.2bRemove Section cg4275 2004/07/02  GވcAThe QoS requirements in the document today eg. DiffServ, flexible ARQ schemes, etc., can be used to create QoS profiles that meet the needs of the applications several years from now when .20 is first implemented. Furthermore, our PAR specifically says that we are designing a system optimized for IP-data transport. That means the 802.20 air interface will handle applications over TCP and UDP that in turn require low error rates and low latency. In addition the current requirements documBW Wdense1WAWWWdependEWWdependingރWލWWJWUWkWtWWWWWWWWdependsW0WdeployWdeployedEWWdeploymentWdeploymentsވWޒWWWLWPWQW\WgWhWdescribedWCWeWwWWdescriptionW(W.WbWދg2260iKlererj&Making it optional would be acceptablemAccepted-Modified 2004/07/02MarkedތEToddFChauvin^Technical, Binding_20`15a4.5.4bReplace requirement with "The air interface shall support the collection of metrics so that a network operator can effectively monitor the performance of the 802.20 air interfaces through various MIBs."cbAll options are overly detailed with respect to specific statistics that need to be accumulated. d10g2261iKlerermAccepted 2004/07/02MarkedލEJohnFChenGMember^Technical, Binding_11`5a4.1.1bSpecify 2 bits/sec/Hz/sector as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved. cg4277 2004/07/02  ދcAAdvocating a specific mechanism for separation of traffic does not allow 802.20 to maintain a network agnostic approach. This can be accomplished in many ways allowing use of 802.1q tagging, PPP or MPLS across the air interface without specifically mandating any particular technology at layer 2 Eg. 802.16 defines a convergence sublayer when VLAN frames are to be carried over the air interface without mandating 802.1 q at layer 2d9cconvergenceދWޕWWWqWWWWWWWWWconveyW0Wconveys6WW WconvincingWcooperative$WFWWcouldރWލWWCWEWJWaWkWtWWWWWWWAWcoupling4WcoveredWWcovergae޵WWcpe_Wcpeseemsliketheincorrecttermhereitisusuallyusedin_VcreateވWޒWWWcreatesWDWcriteriaWcurrentވWޒWޥW޽WWWW.WGWW*W.W4WcurrentoptionshaveinternalinconsistenciesneedtoharmonޥV*Vcurrently.WWcurrentlyknownattackscurrentattackswereunknowntopast.VVcustomer'sUWcy WdGW4WdataޅWޏWީWޯWޱWWWWW W(W)W*W@WGWRWmWvW}W~W W!W$W'W+W.W0W2W3W4W6W9W<W=WgcagnosticދWޕWWWqWWWWWWWWWagreed޵WWaiWW@WXW`WaWWzWWWWWWairވWދWޒWޕW޳WWWWWWWWLWVW]W^W`WaWcWqWWWWLWPWQW[W\WgWhWtWWWWWWWWWWWWWWWWWWWWWairinterfacesupporttoenablenotclearVVallރWތWލWޖWުW޳W޺W޽WWWWWWWAWkWsWtW{WWWWWW.W1W2W[W]WnWqWWWWWWWWWWWWWWWWWWWWWanރWލWޛWޡWީW޵WWWWWW7WAWFWGWLWXWkWtWanalysis.WWLb0.9ާWMW?WHW03/45r1ުWWW03/47r1ުWWW1ޅWކWއWޏWސWޑWޙWޛWޟWޤWޥW޺WWWWWWWWWWW W!WmWnWoWvWwWxWWWWWWWW W!W"W$W%W&W'W(W)W*W+W,W-W.W1W2W3W6W7W8W9W:W;W^WqWWWWWWWWWW1addacaptionatthebottomofpage10underthefiguresޛVVtheheadingofsection4.1.5todataratesdownlinkޤV1deletethetableޥV1line2-3ismodifiedtothesepeakdataratetargetsareiV1.2ޥW1.25!WGW1.5!W~W1.6GW10ޛWWGWW10-8W100ާWWWW10e-1W10e-8W11ޞW12ޥWW!W128kbpsW13W13-16WW15ިW޵W17ޘWޡWWW*5fbreplacerequirementwiththeairinterfaceshallsupporttheތVޖVVVsV{VVVVVVVVVreplaceshouldwithmayVVreplacethewordshouldwithmay,VoVreplacethewordwillonline26withshall0VyVreplacethissentencewiththisdocumentprovides/definesth߾VWWWWWWW$W'WrequirementsޢWިW޺W޽WWWWWWWWW)WrequirementsworkWreservationWresolvingWresourceWWresourcesWrespectWrespectivey!Wresponse޺Wrestore޵Wrestorethedefinitionandputiteitherinthissectionin޵VrestrictWresultsWrewording޷Wrf޺WrfcWrmޛWroleWWrouteWroutedWroutingWrsvpWrules޺WsafelyWsafety޺WsameWsar޺WsatisfiesWsatisfyWW&WsatisfyingWލg2252iKlererjSee reply comment 1mRejected 2004/07/02MarkedގEJohnFChen^Technical, Binding_11`5a4.1.1b5Remove the distinction between uplink and downlink. c The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.d12g2253iKlerermAccepted-Duplicate 2004/07/02MarkedޏEJohnFChen^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2cA3Option 1 peak rates result in a large user data rate peak to average ratio of the order of 10:1 and will rarely be seen in practice (see C802-20-04-33r1). We should therefore not artificially limit proposals to large peak data rates whose sole purpose is specs-manship and will rarely be seen in practice. 3d13g2254iKlerermAccepted-Duplicate 2004/07/02MarkedސEJohnFCheng4280 2004/07/02 ލcAThis requirement specifies stringent spectral efficiencies without explicitly clarifying the conditions under which it should be achieved. For example, because cell size is not constrained by the requirements, the spectral efficiencies could be achieved with very small cells. Or, for example, operation at 120km/hr is very different depending on the environment - certainly we are not interested in operation at 120km/hr in an urban setting, yet the requirement could be interpreted that it iBs applicable under all channel conditions. The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.d11cvlanދWޕWWWqWWWWWWWWWvoip$WFWvsWMWNWwMWwantުWWWwas޵WW\WfWW0W5WMWWWWwayLWWwaysދWޕWWWqWWWWWWWWWWweރWޅWކWވWލWޏWސWޒWުWWWWWWW<WBWOWRWUWWW^WkWmWnWtWvWwW߸WWWWWWW$W%W'W(W+W,W6W7W9W:WLWPWQW\WfWgWhW{WWWWWWWWWWWWWWWWWWWWWWWW2WDWMWwhatisapartitioningmodelVVwhattheheckistelematicsVVwhateverWWwhenވWދWޒWޕWWWWWBWqWLWPWQWWcrfވWޒW޺WWWLWPWQW\WgWhWqWWWWrfcsUWWWright:WWWrlGWYW4WWWWrt޳W[WcrecommendވWޒWWWWUWWLWPWQW\WgWhWWWWWWWdundancyinline30theaishallbedesignedVredundantޡWW#Wredundantsecondsemtencelines4-6VreferިWCWreferenceޜWޫWެWޭWGWreferencedުWWdWeWrefined޷Wreflect޸WWreflecttheproposalforcommonmacincontributionc802.20-VrefrenceެWregardWregardingWWWrelabeledޛWrelationshipTWrelativeWWrelativelyGWreleaseGWrelevancyKWrelevantުWWW]W^WremovalUWremovePWiWWWremovetextstartingatline7iiVVremovethesentencestartingwiththe802.20andreplacewitPVremovethetextstartingwithhowthesystemVremovedfWremoving^WrenumberedޛWrephrasing޶WreplacePWreplacedWrepresentativeWrepresentsfW#!ސ^Technical, Binding_12`22a4.1.5.1b#Remove option 1 and adopt option 2cfThe concept of bandwidth must be clarified given that we are not requiring specific channel bandwidthsd14g2255iKlerermAccepted-Duplicate 2004/07/02MarkedޑEJohnFChen^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d15g2256iKlerermAccepted-Duplicate 2004/07/02MarkedޒEJohnFChen^Technical, Binding_14`16a4.1.7.1bRemove this section. cg4282 2004/07/02 +b2ރWޅWކWއWލWޏWސWޑWޙWޛWޜWޟWޤWޥWޮW޺WWWWWWWWWWW WWW W!W"WKWSWkWmWnWoWtWvWwWxWWWWWWWWWWWWW W!W"W#W$W%W&W'W(W)W*W+W,W-W.W/W1W2W6W7W8W9W:W;WVW^W_WqWWWWWWWWWWWWWWWWWWWW2alternatetextforthissectionޥV*V2insertnewsubsection4.2.1.1general޺VqVVeffectivelyތWޖWefficiencyރWލWevaluationރWލWfigureޗWޙWinޘWintegratedޗWinterfaceތWޖWinterfacesތWޖWisރWލWlinesޘWmbwaޗWޙWmetricsތWޖWmibsތWޖWmonitorތWޖWmustޘWWcarqވWޒWWWLWPWQW\WgWhWWWartificiallyޅWޏWWmWvW$W'W+W6W9WWWasޛWޡWެWޮW޷W޺WWWWWW=WAWCWFWGWLWXWZWWWWWW WWWWW4W@WTWVW]WeWqWtWWWWWWWWWWWWWassured(WatރWފWދWލWޔWޕW޴W޵WWWWWWWWWWWW+W,WGWXW]WiWkWqWrWtWzWWWWWWWWWWWWW0W1W4Watsomeearlierversionofthesrdtherewasanagreedupon޵VVattacks.W>W WWattendingaWattributeީWRWauthentication WauthorizationWWauthorizedWWavailableBWGW4WAWW {5bperformanceތWޖW޺W޻W޽WWWWWWWWWWsW{WWW^W_WqWuWvWWWWWWWWWWWWWWWWWperiodWWWpermitW WW^WpersonalWWWperspectiveWphaseW!W"W1WphbsWWphyWWWWW W߽WWWWNWWWphy-specificWWWWWphy/macW+WWkW1.1general޺Vprotect޹Wprotection޹WprotocolޛW޶Wprovide޹WWWprovisions޶Wpublic޺WpurposeWpurposesާWput޵WqosޥWqualityWquantitative޽Wradiation޺Wradio޺WWrange޺WrateޣWޥWީWޯWޱWratesޤW޴W޽WWreadޢWreadilyWreceiver޺Wrecipient޹WreferenceޛWޫW޵WreferencesުW#'ޒg2257iKlerermAccepted-Duplicate 2004/07/02MarkedޓEJohnFChen^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d17g2258iKlerermAccepted-Duplicate 2004/07/02MarkedޔEJohnFChen^Technical, Binding_20`7a4.5.3bRemove sectioncThis is a feature of the user terminal and backend infrastructure and is irrelevant at the MAC/PHY layer. In addition, the need for high priority should be captured within QOS frameworkd18g2259iKlerermAccepted-Duplicate 2004/07/02MarkedޕEJohnFChen^Technical, Binding_19`34a4.5.2bRemove Section cg4285 2004/07/02" HޒcAThe QoS requirements in the document today eg. DiffServ, flexible ARQ schemes, etc., can be used to create QoS profiles that meet the needs of the applications several years from now when .20 is first implemented. Furthermore, our PAR specifically says that we are designing a system optimized for IP-data transport. That means the 802.20 air interface will handle applications over TCP and UDP that in turn require low error rates and low latency. In addition the current requirements documBޣ‚Eޤ ‚Fޥ*‚Gަ>‚Hާ߂?‚IިJ‚JީR‚Q?ުԃ‚RޫS‚SެT‚TޭU‚UޮV‚VޯߐW‚WްX‚XޱߑY‚Y޲Z‚Z޳[‚a޴ߒi‚g޺ߓ‚h޻‚i޼‚jp޽‚q޾ߔ‚r޿ߕ‚sߖ‚tߗ‚uƒߘ‚vq‚wă‚xŃߙ‚yƃߚ‚zǃߛ‚ȃߜ‚AɃ‚ʃ߄@‚r˃K‚̃ߝ‚B̓‚΃‚sσ߅+‚Ѓ,‚у-‚t҃ߞ\‚Ӄߟ‚C‚D‚E‚׃.‚؃L‚كߠ‚F‚G‚H‚I‚/‚A‚u]‚vߡ‚J‚݃߻coptionsތWޖWޥW޽WWWsW{W*W/W]WWWWWWWWWWWWWWorރWދWލWޕWިWުW޼WWWWWW W4W;W<W@WRWTWUWVWYWaWkWqWtW߷W߸WWWWWWWW.WAWJWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWorderޅWޏWWWCWmWvWWW$W'W+W6W9WeWWWorganizedKWWormanceWWperhaps޶WperiodWphaseWphasesއWޑWWphraseާWphy/mac޴WphysicalWplacedޞW޺Wportion޳WpossibleވWޒWWWpotentiallyަWpotentiallyconfusingtextަVpower޻WpppދWޕWWW'({ޕg2260iKlererj DuplicatemAccepted-Modified 2004/07/02MarkedޖEJohnFChen^Technical, Binding_20`15a4.5.4bReplace requirement with "The air interface shall support the collection of metrics so that a network operator can effectively monitor the performance of the 802.20 air interfaces through various MIBs."cbAll options are overly detailed with respect to specific statistics that need to be accumulated. d20g2261iKlerermAccepted-Duplicate 2004/07/02MarkedޗEDanFGalGMember^ Editorial_7`3a2bCAdd "Figure 2-1. The Vision of Integrated MBWA" under the figure.cMissing "Figure 2-1" captiond21g2342iKlerermAccepted 2004/07/02 2004/06/01Marked2-1ޘEDanFGalGMember^Technical, Binding_8`17a3.1b(Change "must" in lines 17, 18 to "shall"c!Inadequate "must" in lines 17, 18d22g2344iKlerer 2004/07/02"& ޕcAAdvocating a specific mechanism for separation of traffic does not allow 802.20 to maintain a network agnostic approach. This can be accomplished in many ways allowing use of 802.1q tagging, PPP or MPLS across the air interface without specifically mandating any particular technology at layer 2 Eg. 802.16 defines a convergence sublayer when VLAN frames are to be carried over the air interface without mandating 802.1 q at layer 2d19&-ޘjChange "must" to "are". This is descriptive text, if the system meets the requirements what it is/was designed to do is not relevant. The "shall" in the second sentence is ok .mAccepted-Modified 2004/07/02 2004/06/01MarkedޙEDanFGalGMember^ Editorial_9`3a3.1b1. Add "Figure 3-1. Service Attributes of MBWA Systems" 2. Add appropriate text in section 3.1. Proposed text -add a sentence at the end of line 19: "Some desirable service attributes of MBWA systems are shown in figure 3-1." c!Missing caption under the figure.d23g2362iKlerermAccepted 2004/07/02 2004/06/01Marked3-1ޚEDanFGalGMember^Technical, Non-binding_9`13a3.1.1brAdd "applicable" after "other". The changed text would be: "in conjunction with other applicable 802 standards..."cttext is: "in conjunction with other 802 standards...". It is too broad to and vague to invoke "other 802 standards" d24g2363iKlerermAccepted 2004/07/02 2004/06/01lbnetworkތWޖW޿WWWWWWWW9WVWsW{WWWWWWWWWWWWWWWWWWWWWWnetworksecurityinmbwasystemsshallprotecttheservicepVVnetwork-basedWWnetworksWW߽WWW޻W޾WoneޟW޻WWWWWoperating޺W޻Woperations޽WoperatorތWޖWWWoppositeWoptimal޻Woptimized޻WWWoptionޅWކWއWމWޏWސWޑWޓWޥWޮW޽WWWWWWWWWoption3ޥVoptionalWor޵W޹W޽W޾WWoriginalޛWotherޚWWotherwise޹WoutWoutdoor޽WpageޛWޞWpar޽WWparametersޥWpart޶W޺WWparticularWpartsWpeakޤWޥWWpedestrianޥW޽WperޣWperform޽WijitIWOWQWދWޘWޣWޥWާWީW޵WWWWUWߙWWWWWWitisacceptabletohavesoftrequirmentsthatarenotdirecVitwouldbeoktoclarifythatlinearlymeansafactorof1ާVitsWituSWjanuary's~WjitterNWjointRWjulyߓWkeepjW}WހWߙWkeepoption2jV}Vkeepthefirstsentencethe802.20airinterfaceshallsuppoހVkeepingWkeptWWkeyWkmgWkm/hxWkm/hrWlaodingޥWlastߖWߙWlatency߄WlayeryWWߙWWWWlayersWWleastߋWlegal޹WletIWlevelWlevelsWlicensedWlike@Wlimit߄WlimitationsWlimitedLW[WWline=W߀WߝWWJWlinearlyާWlines2Wro/picoWmaintainQW߷W߹W߾W߿WWWWWWWWWWWWW WV\kb2-1ޗWWW2-3WW.W2W2.0ޥW*W2.5GW4WW20GW4WW2001W_W23ޞWW25ަWMW>WHW250޽WWFWWWWW2597WW2598WW25msWW260WyW28޻WuWW3މWޓWޛWޟWޤWޥWާW޺WWWWWWJWpWyWWWW W*W?WKW]W_WqW|W}WWWWWWWWWWW3insertnewsubsection4.2.1.2radiotransmitter޺VqVVWޫWaddasentenceonline3thescalingfactortobeassumedfoާVaddapplicableafterotherthechangedtextwouldbeinconjޚVaddfigure2-1thevisionofintegratedmbwaunderthefigurޗVaddnewtextinline15seeadditionalrequirementsinsectiިVaddthefollowingsentencethustheaggregatedatarateperޣVWaiޟWoshallޘVchangedޚW_bendޙWޢWWWBWWWWWWWWend-stationsޛWWend-to-end޶WWWWMWend-userWW WWW^WenforceMWenforcementWWenoughW_WensureWWWWentireޡW޴WWWiWWWentryޣWޥWW*Wenvirnomental޺WqWWenvironmentWWvWWenvironmental޻WuWWenvironmentsWWequipment޺WqWWerrorWWWWWNW^W_WvWWWWesWWestablishedjWWetc޴W޶W޺WWWWWiWqWWWWevaluationރWލWާWWkWtWWWWWW?WWWWWWevenW$WBWFW Wevery޺WqWWexactlyWWertrafficclasseswithdifferentީVinsertdatarateafterwithdifferentޯVޱV(1ޚMarkedޛEDanFGalGMember^ Editorial_9`18a3.1.1bA 1. Add a caption at the bottom of page 10 (under the figures). 2. Delete the current "Figure 3.1" and "Figure 2" captions as well as the original "Figure 1 - IEEE 802 RM for End-Stations...." caption. 3. Insert a new caption: "Figure 3-2. IEEE 802 Layer 1 & 2 Protocol Reference Model" ctThe figures (1 & 2) copied from an 802 standard need to be relabeled and renumbered so as to flow with section 3.1.1d25g2364iKlerermAccepted 2004/07/02 2004/06/01MarkedޜEDanFGalGMember^ Editorial_10`1a3.1.1b"Change " Figure 2" to "Figure 3-2"c Incorrect reference to Figure 2.d26g2365iKlerermAccepted 2004/07/02 2004/06/01MarkedޝEDanFGalGMember^ Editorial_11`10a4.1.1b%Insert a space character after "(Hz)"c%Insert a space character after "(Hz)"d27g2366iKlerermAccepted 2004/07/02 2004/06/01MarkedޞEDanFGalGMember_12g4294 2004/07/02>cstatisticsތWޖWWWsW{WWWWWWWWWstatusWstdCWeWstraightforwardމWޓWWWpWyW|W}WWWWWWWރWލWWkWtWWWWWWstyle<W߸WlWsubWW.W2Wsub-section޸W޺W WqWsublayerދWޕWWWqWsubmissionsW1WsubmittedުWsubmittersWsubnetXWsubsectionWsuburbanAWsuccinctgW߿WsuchޮWWCWWVWeWsuggest޷WW Wsuggested޺WqWsupportވWޒWWWWWWWWWW'W3W4WCWGWLWWW[W^WWWWWWWWW4WLWPWQW\WaWeWgWhWsupportnon-lineofsightambiguousVVsupportingGW4WsupportsGW4WsureWsustainedWW| LbdesirableޙWWWdesiredWWWWdetail޺WqWWdetailedWjWWWdetermineރWލWWkWtWWWWWWWWWWWdeterminedMWdevelopWdeveloped޺WqWWdeviceWWWWWWWdevices޺WWWqWWdifferentީWޯWޱWWW$WFWWBWFWRWWWYW^WW WdifferentiatedWWNWWdifferingWNWdiffferentWdiffservWWingޠWWduplicated޹WdurationWduringWeWWWWWWWWWWW We-mailWeachWWWWeapWeffective޴WWeffectivelyތWޖWWWeffectiveness޻WefficienciesWefficiencyރWލWޢWޣWޥWWWWWWefficientWefficientlyWeffortWLbcharacterޝWWWcharacteristic޲WZWcharacteristics޺WWWqWWchooseWWWWclarification4WWclarificationisneeded4VVclarifyWWbWWWWWclarifythisrequirementormakethesentenceaninformativebVVclass޺WWW(W^W_WbWqWWclassesީW޲WWWWWRWZW^WWWWclassicW^WclassificationW_WclearlyWWcloselyWWcodedWWcodingWwWcoexistence޺WqWWcollectionތWޖWWWWsW{WWWWWWWWWWWWcomment WWcommercialWWsWcommitmentsWWWNWcommonWWWWWcommunicatesW߽Wcommunication޺WqWcommunications޻WuWcompatibleWWcomplementedWWW-3ޞ`1a4.1.1b+Move Table 4-1 caption to page 11, line 23.c9The "Table 4-1" caption should be placed above the table.d28g2367iKlerermAccepted 2004/07/02 2004/06/01MarkedޟEDanFGalGMember^ Editorial_12`4a4.1.2b1. Add a caption in line 4: "Table 4-2. Block Assignment Sizes" 2. Change line 3 as follows: " The AI shall support deployment in at least one of the block assignment sizes listed in Table 4-2."cMissing table captiond29g2368iKlerermAccepted 2004/07/02 2004/06/01MarkedޠEDanFGalGMember^ Editorial_12`6a4.1.2b)change to: "duplexing schemes (FDD/TDD)"cline 6 is "Duplexing schemes"d30g2369iKlerermAccepted 2004/07/02 2004/06/01MarkedޡEDanFGalGMember^Technical, Non-binding_12`17a4.1.4bJDelete the entire sentence that spans lines 17, 18: " As an example...".c[The sentence "As an example, ..." is redundant. Has the same meaning as line 21 in page 11.d31g2370 2004/07/02ZwbairތWޖWWWWWW WWWTWsW{W߽W߾WWWMWWWWWWWWWWWWWWWair-interfaceWWall޽WWWWWWWW$WWWBWFWNW^WWWWWWWW Walleviating>W WallocationWW/WwWxWWallowރWލWWWkWtWWWWWWWWWWWWallowsWWWalong޺WWW^WqWWWalso޺WWWWWWNW_WqWWWaltered޹WWalternateޥW޺W*WqWWalternativelyWWWWWWalternativelydefinespeedrequirementsformobilityclearlyVVWWWWWWWW WWW*W4W@WCWMW^W_WjWpWW16rޡiKlererjtWill depend on what happens to the text on page 11. If the sentence on page 11 stays then deleting the example is okmAccepted-Modified 2004/07/02 2004/06/01MarkedޢEDanFGalGMember^Technical, Non-binding_12`20a4.1.5bappend to the end of the sentence: " requirements of section 4.1.1". so that the sentence should read: "...consistent with the spectral efficiency requirements of section 4.1.1."c0The text of section 4.1.5 is not specific enoughd32g2371iKlerermAccepted 2004/07/02 2004/06/01MarkedޣEDanFGalGMember_12`20a4.1.5bAdd the following sentence: "Thus, the aggregate data rate per sector shall be calculated by multiplying the spectral efficiency entry from Table 4-1 by the specified channel bandwidth. "cBNeed to clarify what "consistent with spectral efficiency" means.d33g2372iKlerer 2004/07/02cthereforeޅWޏWWmWvW$W'W+W/W6W9WWWWtheseެWWWWCWGWRW]WaWWWWW4WTWeW{WWWWWWW4W.WwWWWthingWthings3WthisރWފWދWލWޔWޕW޷W޺WWWWWWWWWWWWWWW$W4W7WAWGWNWOWQWRWTWUWVWXW\W]W^W`WaWbWcWdWeWhWjWkWqWrWtWzW߾WWWWWWWWWWWW W W.W/W0W1W4WFWIWfWqWtW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWcuplink@usage@Duseful@version@vlan@wesupportoption1removingthissectionitdoesnotseemr@when\whenever@ijoanne'joannewilson@joannewlson@klerer@%/naguib@;naguibsutivongtomcikyallapragada@sutivong@t@tomicik@wlson@r6j1changetoreadieee802.20-basedsystemsshallsupportbro@d157@2@97@addareferenceto3gpp2'sbcmcsstage1documenthereasfo@adoptthisremedywiththefollowingmodificationsispecify@already@architecture@W@WAWBWCWEWFWGWMWNWOWTWWWXWYWZW[W\W]W_W`WbWcWdWeWhWkWmWoWpWrWtWvWxWyWzW߾WWWWWWWWWWWWWWinaguib5W6W7W8W9W:W;W<W=W?W@WAWBWCWDWEWFWGWHWIWJWKWLWNWOWPWQWRWSWTWUWVWWWXWYW]W^W_W`WaWbWcWdWeWfW߀W߁W߂W߃W߄W߅W߆W߇W߈W߉WߊWߋWߌWߍWߎWߏWߐWߑWߒWߓWߔWߕWߖWߗWߘWߙWߚWߛWߜWߞWߟWߠWߡWߢWߣWߤWߥWߦWߧWߨWߩWߪW߫W߬W߭W߮W߯W߰W߱W߲W߳WߴWߵWnaguibsutivongtomcik6V8V:V;V<V=VAVCVDVEVGVHVJVKVLVNVOVQVRVSVUVVVWVXVYV]V^V_V`VaVcVdVeVfV߀V߁V߂V߃V߄V߅V߆V߇V߈V߉VߊVߋVߌVߍVjarchitecture~WހWW2W3WareOWgW~WޘWީWWW߀W߄W߈WߓW3WFWvWWarrangementsߔW߯Was6W7W8W:W;W<WCWDWEWFWGWLWNWZW[W^W_WaWbWcWeWgWvW~WކWއWީWWMWUW߀W߄W߉WߖWߙWߝW߹W߾W߿WWWWWWKWNWSW\WjWnWvWWWWWWWasincomment4އVasperreplytorecord223comment62weproposetodeletesVaspectߘWassignmentZWWassociateNWassociatedWWassured~Wat4W5WQW]WWWWHW߄WߋWߓWߖWNWWWWattributeީWattributesީWߞWߴWWaudioWNWauthentication WautomaticvWavailableIWaverage߉WW3WctorރWborderOWbroadcastWLW8?ާckThe phrase "scales linearly with system bandwidth" is inadequate. The scaling factor needs to be specified.d37g2376iKlererjnIt would be ok to clarify that "linearly" means a factor of 1. A factor not equal to one requires explanation.mRejected 2004/07/02 2004/06/01MarkedިEDanFGalGMember^ Editorial_14`15a4.1.7bGAdd new text in line 15: "See additional requirements in section 4.4.1"cZNeed to consolidate with or refer to section 4.4.1 that discusses additional requirements.d38g2377iKlererjJWill depend on resolution of other comments pertainiong to 4.4.1 and 4.1.7mAccepted-Clarified 2004/07/02 2004/06/01MarkedީEDanFGalGMember^Technical, Non-binding_14`19a4.1.7.1bA=insert "bit rate," after ".. traffic classes with different" =@A> 33  33>c:add an important attribute of traffic classes - data rate.d39g2378iKlererj 2004/07/02?D~ީ 2004/07/02 2004/06/01MarkedުEDanFGalGMember^ Editorial_23`5a5bEDelete the two listed contribution references (03/45r1 and 03/47r1) .cOnly the PAR and the 5-criteria documents should be referenced here, or we may want to add ALL the other relevant contributions that were submitted since May 2003 ?! d40g2379iKlerermAccepted 2004/07/02 2004/06/01MarkedޫEDanFGalGMember^ Editorial_14`21a4.1.7.1b +ީjA I believe bit rate, though an inportant service attribute, is not a QoS attribute as used here. It is an attribute of the data stream and the data streams attribute are subject to the QoS attributes. It could get quite unwieldy to use diff-serv to indicate bit rate.  mRejected{bintegratedޗWWWintegrity޸W޹WWW WW WWWWintendedbW|WWWintent`WWWinter&WOWinter-frequencyWinter-workWW WWWTWsW{W߽W߾WinterfacesތWޖWWWWWsW{W߽Wintermodulation޺WinternallyWinteroperable߾Winteroperate޺WinteroperationWinterruptionWintetrest޺WintoޤW޺WWWintolerantWintra&WipWWWWW9WVWXW[W\WiW߽WWWip-basedWWip-data߾WipsecWipv4WWWWWipv6WWWWWisރWލWޥWާWWWWWWWWWWWWWWWWWWWW'W+W/W4W=WAWFWbWiWkWtWߺW߽WWWWWWWVU*conlytheparandthe5-criteriadocumentsshouldbereferencުVVVopen-ended7WW Woperate WWoperationރWލWWWkWtWWWWWWWWWWWWoperationalWoperatorsWopinionWoppositeW0WoptimalCWeWoptimallyCWeWoptimizedވWޒWWWLWPWQW\WgWhWWWoptionޅWމWޏWޓWޯWޱW޲W޳W޼W޽WWWWW"W(WKWOWSW^WmWpWvWyW#W$W'W+W.W/W6W9WWWYWZW[W]WbWfW|W}W~WWWWWWWWWWWWWWWWWWVoption2providesdescriptionforonlybesteffortdataleav(Voption3issimplestraightforwardandwelldefinedމVޓVVVpVyVoption-1޼WoptionalWXW)^binding4W5W6W7W8W9W:W;W<W@WAWBWCWDWEWFWGWHWIWKWNWPWTWUWVWWWXWYWZW\W]W^W_W`WaWbWcWgWhWiWjWkWlWmWnWpWqWrWsWtWuWvWxWzW{W|W}W~WWހWށWނWރWބWޅWކWއWވWމWފWދWތWލWގWޏWސWޑWޒWޓWޔWޕWޖWޘWާWޮWޯWޱW޳W޴W޵W޶W޷W޸W޹W޺W޻W޼W޽W޾W޿WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWWWWWWW WbH|baddthespecificreferenceinsection5and/orinafootnoteޫVSVadditionalިW޺WJWqWWaddressWWWaddressedWWaddressesWWaddressingWWadjacent޺WqWWadoptޅWކWއWމWޏWސWޑWޓWWWWWWHWIWJWKWSWfWmWnWoWpWvWwWxWyW$W%W&W'W(W)W+W,W-W5W6W7W8W9W:W;WmWnWpWtW|W}WWWWWWWWWWWWWWWWinormodificationasfollowssystemsSVVadoptoption3މVޓVVVJVpVyV|V}VVVVadoptthec802.20-04-44textforthissectionnVadopttheproposedtextinthejointcontributionc802.20-04HVIVmVpVadoptthetextinsection4.1.5.1ofc802.20-04-44withthefV5VadoptedWW>IެjuThis is part of Option 1 text. I expressed preferrence for option 3. If Option 1 is accepted I support Dan's comment.mRejected 2004/07/02 2004/06/02MarkedޭEDanFGalGMember^ Editorial_14`31a4.1.7.1b delete "[7]"cOrphan reference [7]d43g2401iKlerermAccepted 2004/07/02 2004/06/02MarkedޮEDanFGalGMember^Technical, Binding_14`38a4.1.7.1bDelete option 2.ctext such as in line 38 - "it may be useful to consider" is not recommended for use in a requirements document as it is quite useless.d44g2402iKlererj@One option needs to b e picked rather than only eliminating one.mAccepted-Modified 2004/07/02 2004/06/02MarkedޯEDanFGalGMember^Technical, Binding_15`4a4.1.7.1b.insert "data rate," after "...with different"c+In Option 3, line 4, missing "data rate," d45g2403iKlererjSee reply to comment 39mRejected-Duplicate 2004/07/02 2004/06/02MarkedްEDanFGalg4312 2004/07/02c,jfactQWfactorާWfadingWfairnesszWfastWfddߔWߙW߯WWfeatureTWfeaturesUWfigureWWfileWfinalޤWfirmwareWfirstKWހWߝW߽WWWWfixed{WflexibleߙWfloorWflowNWflowsߞWߴWNWfollowingLWyWWߣW߽WWWWfollowsNWZW~WߖWߝWforIWJWOWPWgWiWkWlWrWuW|W~WWވWެW޹WWWW߄WߎWߘWߙWߝWߞWߟWߠWߡWߣWߩW߳WߴWߵW߶W3WFWNWOWvWwWWWWWWWWWformsWforwardߓWforwarding~WfragmentWframevWzWfrequenciesWjoneszWonlygWޥWޮW WߞWߴWWWWopenߓWWoperatingWoperationsWoperator WoperatorsWopposedKWoppositeWoptimalWoptimizationWoptimizedߙWvWWalދWorZWzWވWޣWޥWUWorg/internet-drafts~WoriginalWotherzWހWިWWKWߋWothersWotherwiseQWޥWoutQWWߋWߖWpageޡWWparރWߋWparagraphLWparametersWparaphrase޷WWparetial޶WpartެWparticularOWWpartitioningOWpartitioningisusedheretostressthattheborderbetweenOVpdfNWpeak߀WpedQWperformancegWߙWperiodicitiesߖWpertainiongިWphb~WphyOWߙWphy-specificߙWphysicalWpickedޮWpico-cellsgWpleasehWiWmWrWuW߂W߈Wpleaserefertoc802.20-04-55fortheproposedresolutionrVuV@cinadequateޘWާW޻WW?WuWWinadequatedetailofpowercontrolrequirementsneedmoresp޻VuVVinadequatemustinlines1718ޘVVinappropriate޿WWWWWWinappropriatetext802.20protocolsVVVinclude WWincludedfW5Wincomplete&WOWinconsistenciesޥW*WincorrectޜWެWWYW_W߶WWTWWWWWWincorrectlinenumberreferenceinline22aftersection4.4ެVTVincorrectreferencetofigure2ޜVVVincorrecttitleV߶Vincrease?W@WWzWincreasedAWWindefensible>W WindividualsfW5WtWformativeWWWRWUWaWWWDW{WinformativeandnottestableVVinfrastructureފWޔWWWrWzWinsertޝWQWgWjW߿WWWWinsertaspacecharacterafterhzޝVVjseereplytocomment39ޯVޱVseereplytocomment6nVtVށVނVseereplytoinitialcommentVVVseereplytopreviouscommentVseereplytorecord201tocomment58VDMްGMember^ Editorial_15`9a4.1.7.1bsubstitute with a proper table.c2distorted table-like columns in lines 9 through 25d46g2404iKlerermAccepted 2004/07/02 2004/06/02MarkedޱEDanFGalGMember^Technical, Binding_15`27a4.1.7.1b.insert "data rate," after "...with different"c,In Option 4, line 27, missing "data rate," d47g2405iKlererjSee reply to comment 39mRejected-Duplicate 2004/07/02 2004/06/02Marked޲EDanFGalGMember^ Editorial_15`30a4.1.7.1b5change "Traffic classes" to: "Service Characteristic"cFIn the table of Option 4, confusing column heading - "Traffic classes"d48g2406iKlererj6OK if option 4 is selected. However I prefer optio n3.mAccepted 2004/07/02 2004/06/02Marked޳EDanFGalGMember^Technical, Binding_15`30a4.1.7.1bBHarmonize with the appropriate 802.20 contributions on this topic.g4315 2004/07/02IccolumnsްWXWWcombination WWcommaWWWW?WߺW߼WWWWcommaismissingbeforeandinliststhroughthedocumentgeVVcommas WcommentWW2WW_WWWcommercialsWcommitmentsWcommonWWcompellingW1WcompetingW1WcompetitiveW1WcompleteW9WWWWcomplexityWWcompliantWcomplicatesރWބWލWގWWWkWlWtWuWWWWWWWWWWWWWWWWWWWW WWWconformW߻Wconfuses߾WconfusingަW޲WW@WAWbWconfusingunnecessarysentenceVconjunctionޚWWconsensusfWconsequentlyWconsiderޮWconsideredXWconsistentޣW-WconsolidateިWconstrainedރWލWWkWtWWWWWWWdobtwoުWWWWWubiquitousEW|WWWul!WGW"W4WWunauthorizedW W W?WWWWW޽WWWWGWkWtWWWWWWWWWunitWunnoticeable޽Wunprotected WupWWWBWWupdatesWupgradeWuplinkބWގWޤWWWW W@WlWuW~WWWWWWuploadingWWupperWWWurban1Wurbanoutdoor-indoorAWuse޷W<WDWIWLW߸WWW Wusemobileterminalandbasestationonlyandnootherabbre<V߸Vusereplytocomment87 Vusetheproposedversioninthejointcontributionc802.20-0DVVused޺WWWWuserޤWޥW޹W޽WWWWWWWWWW WWWW W&W@WFWGW}W~WWWWW0(bchangetrafficclassestoservicecharacteristic޲VZVchangewillbetoisonlines12anddeletewillonline13VVchangedޚW!WW"WchangesWWWchannelޣWޥWާW޺WWWWWWW7WGWMWTWfWWW*W.W2W3W4W5W?W@WAWHWqWWWWWWWWWWWW WWchannelization޺WqWWchannelsWWWBW.W2WWWWIO[޳c1. All the entries of the table under Option 4 should be specified for the Air Interface portion of the system. 2. Need to distinguish between Realtime (RT) and non-Relatime (NRT) traffic types and specify corresponding maximum tolerable Latency figures.d49g2407iKlererjAI do not support option 4. Also detailed remedy is not specified.mRejected 2004/07/02 2004/06/02Marked޴EDanFGalGMember^Technical, Binding_16`6a4.1.8bProposed change of the entire sentence in line 6: "The AI shall support advanced antenna techniques, at the Base Station and/or Mobile Station, so as to achieve higher effective data rates, ..." etc.c9The term "Interconnectivity at the PHY/MAC" is not clear.d50g2408iKlerermAccepted 2004/07/02 2004/06/03Marked޵EDanFGalGMember^Technical, Binding_16`15a4.1.10g4317 2004/07/02ZibassignmentޟWWWWassociateWNWassociated޻WWW^W_WuWWassociationWassumeWWassumedާWNWiWW?WIWassuredWWatޙWޛWޟW޴W޺W޽WWWWWWWWW+W3WHWIWMWiW߽WWWWWWWWHWNW_WiWkWmWpWqWWWWWWWWWWWWattachedlWattacksW W>WW WWattainableޥW*WattainedWWattemptingWWattributesޙW޽WWWWW^WWWWaudioWWWNWaudio/videoW_WauthenticationWW W WauthorizationMWauthorizationsMWauthorizedWWWWautomaticvWavailabilityWWWޠVchangetotheaishallprovideprovideprivacyandmessagei޹VMP~޵bRestore the definition and put it either in this section (in line 15) or in the Terminology (Appendix A) with a reference in line 15, such as "see definition in Appendix A, Terminology" cAt some earlier version of the SRD, there was an agreed upon text that defined "Covergae Enhancing Technologies". That text needs to be restored to provide the necessary clarification.d51g2409iKlererj^Given that we have a new editor - Dan should locate the defintion and supply it to the editor.mAccepted 2004/07/02 2004/06/03Marked޶EDanFGalGMember^Technical, Binding_16`23a4.1.11bProposed modified text: "The security provisions of IEEE 802.20 should be part of an end-to-end solution that includes highre protocol layers..." etc.chNot clear what is meant by "partial solution". Perhaps rephrasing of the sentence would improve clarity.d52g2410iKlerer 2004/07/02OW޶jgWe need to discuss what is paretial about this solution, I am not sure Dan's interpretation is correct.mAccepted-Modified 2004/07/02 2004/06/03Marked޷EDanFGalGMember^Technical, Binding_16`27a4.1.11.1bUProposed rewording: "The AI's secure access control shall use cryptographic methods.cThe scope of this requirement needs to be refined. As worded, may suggest that the entire access control protocol must be encrypted.d53g2411iKlererjeThe suggested paraphrase could be interpreted to imply that ther is also a non-secure access control.mRejected 2004/07/02 2004/06/04Marked޸EDanFGalGMember^Technical, Binding_16`29a4.1.11.2bAChange the heading of 4.1.1.2 to: "Privacy and Message Integrity"cHThe sub-section heading does not reflect the Integrity part of the text.d54g2412iKlerermAccepted 2004/07/02 2004/06/04Marked޹EDanFGalGMember^Technical, Binding_16`29a4.1.11.2bg4321 2004/07/02|a4.1.11޶> 4.1.11.1޷ 4.1.11.2޸޹ ߃ 4.1.11.3 4.1.11.4 4.1.11.5-.ޠ4.1.34.1.4ޡF4.1.5ޢޣޤ !"4.1.5.1ޅކއޏސޑޥσЃу׃Gfmnovwx}~4.1.6ަާʃ#$%MN4.1.7ި˃؃&4.1.7.1ވޒީޫެޭޮޯްޱ޲޳҃'()*CO4.1.8޴+H4.1.9,I4.2޺4.2.1 4.2.2޻/0@R4.2.3މޓ޼޽̃Ӄك123AJSpy4.2.4޾44.2.6޿54.3ƒÃ67BT4.44.4.1ƃǃȃ89UV4.5W4.5.1:XY4.5.1.1Z[\]4.5.2ދޕՃڃ^q4.5.3ފޔԃۃ_`rz4.5.4ތޖփ܃Kas{4.7bc5ުdejweneedtostandardizeonatermshoulddecidewhichoneWVwesuggestmodifyingthelastsentenceasfollowsߖVweak߀WwebWNWwellOWW߄WߖWߙW߳WWWWweredWwgIWeWwhatޘWޡW޶W޺Wwhat's߀WwhenZWwhetherWwhichWWgWyWWWWWwhileZWߓWNWWwhileweareopentoaddingrfrequirementstothissectionߓVessZW߄WwithLWTWZWeWyW{WWހWރWކWަW޺WWWWKWUW߀WߋWߏWwithin߄WworkވWworking4W5WIW]WdWwould@WދWާWwouldliketoseethepreviousdefinitionandreviewbefore@VwrittenOWwrongWwronglyQWwwwNW~Wk1AWhWkW"W1-1AW1.25 W1.3AWhW100%W1bpsW2fWhWlWW!W"WSWfWߎWk141@216@a@Kability@bactual@0adopted@Pagreeifthefirstrequirementismetthesecondoneisirre@ebeen@c802.20-04-55@?clearer@communications@consensus@control@@coupling@dan@Udefining@detailed@;disagreeweshouldbeabletoevaluateproposalsthatmaysc@documentTdoes@!editorial@editorialandtrivial@}except@for@future@however@iprefermyownproposal@himplemented@in@intheoverviewofthisdocumentitstatesthatforthepurp@>intent@ is=issue@9issues@larger@limits@meta-requirement@modifications@snecessary@network@^noneedtolimitthehowproponentsproposetosupportthis@ not@@notatallclearwhattextfromc802.20-04/44isbeingpropo@number@offs@goperate@statements@D|jtodd9Wtoo߀WtopicZWtotalyWtouch4WtrafficZW WߞWߴWWW3WNWZWtransmissionsyWtransmittingZWtreatment Wtxt~WtypesߞWߴWtypo{WubiquitousWul߀WunauthorizedWWunder߄WunderstandingޣWunwieldyީWupxWupdatingWuplinkeWߣW3WuploadingWupperyWߙWuseRWWީWWW1WLWߣW߽WWWWWWusecommonterminolgyacrossdocumentVusedefinitionsfromareferencedindustrysourceaddadopteVuseofthewordwillisnotappropriatesuggestthefollowinߣVuseoption2injointcontributionRVuseoption31Vuseprotocolinlayers1and2Vusereplyinrecord80tocomment212VVusethefollowinginthisdocumentthetermsystemspectralVusethefollowingtextVusethetextofthefirstsentenceofthesuggestedremedyr߽V.A conރWލW޾WWWWWW-W0W@WDWEWGWJWOWUWVWXWYWZW`WaWkWtWWWWWWWWWWW0W1W4WAWfWyWzWWWWWWWWWWWWWWWWWWWWWWWWWWWonafairandnon-discriminatoryisnotconsistentwithansi-VVoneWWEWW.W2Woneofthefactorsthatwoulddetermineif802.20couldbeuEVVonlyވWޒWުWWWWW#W(W6W.W2WEWLWPWQW\WbWgWhWWWWWWWW WWY޹g2413iKlererjxI believe we need to allow for legal intercept. So the notification to the sender/recipient may not always be possible.mAccepted-Modified 2004/07/02 2004/06/04Marked޺EDanFGalGMember^Technical, Binding_17`16a4.2bA1. Change the heading of 4.2.1 to: "RF Requirements" 2. Insert new subsection 4.2.1.1 - "General" 3. Insert new subsection 4.2.1.2 - "Radio Transmitter" 4. Insert new subsection 4.2.1.3 - "Radio Receiver" Proposed text for section 4.2.1.1 - General --------------------------------------------------------- "The RF part of the IEEE 802.20 physical layer shall be specified in a manner and level of detail consistent with similar public wireless land mobile communication service standards. Ming4322 2004/07/02PV ޹bAChange to: "The AI shall provide provide privacy and message integrity protection for both signalling messages and user data traffic. Appropriate methods shall be employed to protect the individual user's identity and messages from be altered, duplicated or otherwise compromised. Indication to both the sender and recipient of the altered message/data should be given by the system. c`Language is not that of a requirement, especially the usage of "will" instead of "shall/should".d55[a޺g2414iKlererjvThis is a meta-requirment on what each proposal needs to supply in the way of documentation, but I can live with that.mAccepted-Clarified 2004/07/02 2004/06/04Marked޻EDanFGalGMember^Technical, Binding_17`28a4.2.2bAAdd the following text in line 28: " Both base station and mobile station should employ transmit power control mechanisms and exchange control and monitoring information required to achieve optimal performance while keeping the environmental noise floor as low as possible on the one hand and helping the MS preserve its battery power. The number of transmit Power levels as well as the associated control messaging should be optimized for cost effectiveness and performance. Mobile stations'Bv operating states should include sleep-mode and in general should minimize their idle communications to the minimum. "dcQInadequate detail of Power Control requirements. Need more specific requirements.d57g2415 2004/07/02VZ ޺bBimum performance specification shall be defined in the standard, such that equipment certification tests could be developed and be used to verify that multi-vendor compliant equipment would interoperate as well as meet applicable regulatory rules and coexistence requirements. Band-classes should be defined for specific global and local frequency bands of intetrest. These band-classes should define the channelization of the band along with specific RF characteristics such as transmitter maCximum power, receiver sensitivity, antenna gain and height limits, etc. See more detail in the sub-sections that follow. Transmitter emission masks (due to modiulation) as well as spurious emission limits should be specified for every band class, taking into account the specific regulatory emission limits as well as RF coexistence (intereference avoidance) requirements. For mobile, hand-held devices, additional radiation safety rules shall also apply, such as the FCC's SAR requirements. "Y[ ޺bD Proposed text for section 4.2.1.2 - Radio Transmitter ----------------------------------------------------------------------- "The transmitter performance specifications shall include, but not will not be limited to, occupied channel bandwidth, required channel spacing, maximum and average transmit power, EIRP, modulation characteristics, intermodulation distortion (IMD) limits, spurious emission limits , frequency accuracy and stability under the range of specified operating envirnomenEtal conditions. " Proposed text for section 4.2.1.3 - Radio Receiver -------------------------------------------------------------------- "The receiver performance specifications shall include, but not be limited to, channel bandwidth and spacing, sensitivity at specified SNR, adjacent channel selectivity, alternate channel blocking, spurious emissions, spurious response, frequency accuracy and stability under the range of specified operating envirnomental conditions. " ZX޺cThis section is lacking in RF requirements. It is suggested that all RF requirenments be placed in section 4.2.1 and its new sub-section as proposed below.d56+hUb3-1ޙWWW3-2ޛWޜWWWW3.0!W"W3.1ޙWޛWWWW3.1.1WWW3.5߾W3289WW33WWW3456ެWWTW_W35W360ާW?W3gpp2OWfW4ޟW޺W޽WWOWW_WfWqWWWW1.25ާW6޴W7ޭW802ޚWޛW802.20ތWޖW޳W޶W޺WaތWޖWޙWޛWޝWޟWޤWޥWަWާWޫWްW޵W޺Waccess޷Waccount޺Waccuracy޺Wachieve޴W޻WachievedރWލWaddޗWޙWޚWޛWޟWޣWާWިWޫW޻Waddasentenceonline3thescalingfactortobeassumedfoާVaddapplicableafterotherthechangedtextwouldbeinconjޚVaddfigure2-1thevisionofintegratedmbwaunderthefigurޗVaddnewtextinline15seeadditionalrequirementsinsectiިVaddthefollowingsentencethustheaggregatedatarateperޣVbregulatory޺WqWWrelativeWWrelayW߽WrelevantWreliabilityWWjWwWremoveބWޅWކWއWވWފWދWގWޏWސWޑWޒWޔWޕWWWWWWWWWWWRWVWZW[W^W`WaWlWmWnWoWuWvWwWxWzWWWWWW$W%W&W'W(W)W+W,W-W6W7W8W9W:W;WLWPWQW\WhW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!WVVmVnVoVvVwVxV$V%V&V'V(V)V+V,V-V6V7V8V9V:V;VremovesectionފVދVޔVޕVVVVV^VzVVVVVVVVVV^bstandard޺W޽WWWWWWW WWWHWIWhW߶WWWWWWMW^WmWpWqWWWWWWWWWWWWstandardsޚW޺WWWW9WWWqWWWWWWstandards-basediWWstartWWstartingVWXW[WWWWWstateWXWWAWWWstatedW_Wstates޻WbWuWWWstation޴W޻W޿WWWW<WIW_W߸W߽WWW WMWiWpWuWWWWWWWtion޺W~WsubsetWWWsubstituteްWsubstitutewithapropertableްVsuburban1WAWsuccinctiWWsuchޥW޵W޺W޽WWWWWWWWWWWWWWsuggestWsuggestthatwedeleteitorreplacewiththefollowingVW,'bexampleޡWޥWWWWWW*W^WjWWexcessW WGW~W!W0W3W4W=WWWexperience޽WextentWexternalWWfacilitateWWfactorާWfactoredޥWfading޽WfarWfcc's޺Wfdd޾WWWWfdd/tddޠWfigureޗWޙWޛWޜWWWfiguresޛWfileWfirmwareWflexibleWWfloor޻WflowWWflowsWfollow޺WfollowingޣW޻WWWWfollowsޟWWWWfollwingWfootnoteޫWforޛWޥWާW޹W޺W޻WWWWWWWWWWWWWWWWWWWWWWWWWforthepurposeofthisdocumentan802.20systemconstituteVforwardingWWfreeWfrequency޺WWfromޣWޤW޹W޽WWWWWWW WWWmbscalingާWGW4W?WWscalingtheabovepeakdataratesinthereferencecasebyaGV4VVscenarios2WEW}WW<WWschemesޠWWWWWscopeMWscreenWWިWޫW޵W޺WWWWWWWWWWWOWRW^W_W`WaWfWiWqWrWzWWsectorޣWWWsectorsWsecure޷Wsecurity޶WWseeިW޵W޺Wselectivity޺Wsender޹WsensitiveWsensitivity޺WsentWsentenceޙWޡWޢWޣWާW޴WWWWWW8WQWVWXWYW]WbWgWiWjW߾W߿WWWseparateWserial WserverWWserver-clientWWserviceޙWޥW޲W޺W޽WWWWWWW WW>WservicesWWWDWLWWsession޽WWsessionsާWWW$WWXg޻iKlerermAccepted 2004/07/02 2004/06/07Marked޼EDanFGalGMember^Technical, Binding_18a4.2.3c^Option 1: Page 18, line 4 - the "(TBR)" needs to be defined or else discard option-1 entirely.d58g2416iKlererjDiscard option 1.mAccepted 2004/07/02 2004/06/04Marked޽EDanFGalGMember^Technical, Binding_17`16a4.2.3bAProposed Option 4: "Mobile stations shall perform well (quantitative requirements should be specified in the 802.20 standard) under all mobility modes; from pedestrian to 250 Km/hr vehicular speed (as defined in the 802.20 PAR). Key performance attributes that affect the user experience such as data rates, fading, loss of session, call disruption, inability to get service altogether should be kept to an unnoticeable degradation level. This requirement should apply to both outdoor, indoor B]and outdoor (BS) to indoor (MS) operations at delay spreads of 5 micro-seconds or greater." Kg4325 2004/07/02C9baddthefollowingtextinline28޻VuVV_?jbmechanisms޻WWW8WDWLWWWuWWWWWW We/data޹Wmessages޹WW Wmessaging޻WWmetW$WmethodWmethods޷W޹WmetricsތWޖWWWW5WmhzޥWާW!WmibWmibsތWޖWWWmicro-seconds޽WmimoWminimalWminimize޻Wminimum޺W޻WWWmitigateWmixWmmobileWmobile޴W޺W޻W޽WWWWWWWWWWW WWWWWWmobilestationsshallperformwellquantitativerequirements޽VmobilityޥW޽WWWWWWmode޾WmodelޛWWWmoderate*Wmodes޽WWWmodificationWmodifiedޤW޶WWmodiulation޺Wmodulation޺WWmonitorތWޖWWWWWmonitoring޻WWWWmore޺WWmoveޞWޤWWgKubtoavailablewithinlessthan25msަV>VtooWtopic޳W[WtrafficީW޲W޹WWWWWWWW W WW(W?WWWWWWW.W2W3WDWNWRWZW^W_WbWWW WtransitionsbWWtranslatedWWWtransmissionWWtransmit޺W޻WWWWWqWuWWWWtransmittedWWtransmitter޺WqWWtransport߾WtransportingW߽WtreatmentW$WWFWtrueW0W3WtuneWWAY,bidle޻WcWuWWWieeeޛW޶W޺WWWDWLWjW߶WWWWWW_WqWWietfWWietf-specifiedWWWifWWWWW$WNWW.W2WBWFWIWWW WWimd޺WqWimplementWimplementationW߽Wimplementations޾WWWimprovecWimprovedWWinޘWޙWޚWޟWޤWިWޫW޴W޵W޺W޻W޽WWWWWWWWWWWWWWWWWWWWW W$W1W8W@WAWCWDWEWGWHWIWPWRWZW_WcWfW|W~W߽W߾WWWWWWWWWWWWWWWWWWW W!W.W0W2W3W4W5W=WAWFWJWNWSW^W_WeWiWmWpWqWuWwW:cmplsދWޕWWWqWWWWWWWWWmsWYW@WWWWmt WWWWWmuchWJW~WW=WWmultilWmultianntenalWmulticastWWWWWWmulticastauthorizationandsecurityrequirementsneedtobeVVmultipathsWWmultipleWWW1WmultiplenamesformtagenericglobalcommentVVmultiplephasesareabadideaatthisstageearlyinrequirV1VmustކWސWޘW޷WWWWWWWnWwWWWWW W%W(W,W.W7W:WWWWWWmutually4WWnamesWWnat]WWWnearlyW1WneccessaryWW.W2Wnecessary޵WWGWW1W3W4WWWW߸WWWWWWWW W*WneedclarificationtothetextHVIVal޽c9All current three options need improvement. Add Option 4.d59g2417iKlererjI still prefer option 3mRejected 2004/07/02 2004/06/04Marked޾EDanFGalGMember^Technical, Binding_18a4.2.4bOAdd on line 19: "Implementations may support either mode (FDD or TDD) or both."c%Add a clarification on implementationd60g2418iKlerermAccepted 2004/07/02 2004/06/04Marked޿EDanFGalGMember^Technical, Binding_18`25a4.2.6b"Change "network" to "Base Station"c)The term "network" is inappropriate here.d61g2419iKlerermAccepted 2004/07/02 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18`25a4.2.6bg4328 2004/07/02\Qb4insertnewsubsection4.2.1.3radioreceiver޺VqVV4-1ޞWޣWޥWWWW*W4-2ޟWW4-33W4.1.1ޢWW4.1.1.2޸W W4.1.5ޤW W4.1.5.1ޤWfW W5W4.1.5.2ޤW W4.1.6}W<W4.1.6.1}W<W4.1.6.2~W=W4.1.7WW4.2.1޺WqWtWW4.2.1.1޺WqWW4.2.1.2޺WqWW4.2.1.3޺WqWW4.2.5W4.4.1ިWWJW_W5ޥWާWޫW޽WW!WGWW"W*W4W?WSWWWWތWޖW޳W޶W޺W޽WWWWWWWWWWWWWWWWWWWWWWWW WWWWWWEWHWLWhWjWsW{W|W}W߶W߽WWWWWWWWWWWWWWWWWWWWWW802.20'sWNbavailableަWWBWMWTWW>WAWHWWWWWaverageޤW޺WWW W~WW W!W/W0W3W=WqWWavialableWWavoidance޺WqWWb/s/hz/sectorWWWbackboneWband޺WqWWband-classes޺WqWWbands޺W߾WqWWbandwidthޣWޥW޺WWW/W7WGWNWWW*W4WIWqWwWxWWW WWeobject=VVbasisW WW=WWWWWbattery޻WcWbeޚWޣWޥWާW޶W޹W޺W޻W޽WWWWWWWWWWWWWWWWWWW W W WWWWWW W$W>W?WBWEWIWLWZWbWgW~W߿WWWWWWWWWWWWW WWWWWVcaddaclarificationonimplementation޾VVVaddanewsubsection4.4.2macdesignandperformancerequirVVVaddanimportantattributeoftrafficclassesdatarateީVRVVaddcommaafterstandardV߼Vadded?WWaddingWWWadditionވWފWޒWޔWWWWWLWrWzWWLWPWQW\WgWhWWWWWWWWWWW!WWadjectiveAWWadoptވWޒWWWW1WLWPWQW\WgWhWadopted|WWadoptedchangeswerenotmade|VVadvertisedWWadvocatingދWޕWWWqWWWWWWWadvocatingaspecificmechanismforseparationoftrafficdoދVޕVVVqVVVVVVVafterޝWެWWWQW߼WWW1WTWagainst W>W WWaggressiveW1Wlrg2420iKlererjAUse the following text: The physical layer measurements shall include the measurement of such parameters as are important and relevant to the particular RF technology employed. Such measurments and associated reports may include: signal strength and signal quality (C/I) measurements and reporting to the opposite side of the air link, measures of neigboring cells' signal strength and monitoring of their broadcast channels (if applicable), measures and reports of error rates, measures and rBkeports of access delays and call interruptions, measures and reports of effective throughput (good-put), provide any other measurement needed for handoff support , maintenance and quality of service monitoring. Measurements results may need to be sent out at a prescribed (in the 802.20 standard) frequency as well as stored internally for offline processing. " YmAccepted-Modified 2004/07/02 2004/06/04MarkedEDanFGalGMemberg4329 2004/07/02gk 7bAChaneg the entire sentence as follows" The physical layer measurements shall include, but not limited to: signal strength and signal quality (C/I) measurements and reporting to the opposite side of the air link, measure neigboring cells' signals and monitor their broadcast channels (if applicable), measure and report error rates, measure and report access delays and call interruption, measure and report effective throughput (good-put), provide any other measurement needed for handoff suppoBrt , maintenance and quality of service monitoring. Measurements results may need to be sent out at prescribed (in the 802.20 standard) a frequency as well as stored internally for offline processing. " c^The sentence "The Physical layer provides..." is vague and not using proper engineering terms.d620btheir޻WWWWuWWWWthenOWfWthereWWWthese޺WWWWgW߻W߿W.W2W3WqWWtheserequirementsareconsistentshallcomplywiththeparV߻VtheyWBWTWWWWthinkWWWthisރWވWލWޒWޥW޳W޵W޽WWWWWWWWWWWWWW$W8WXW]W_WaWbWdWeWgWiWjWkWtW߽W߾W߿WWWWWWWWWWWWWWWW*W0W3WAWBWFWLWPWQW[W\W]WgWhWnWWWWWWWWWWWWWWWWWWWWW W WWWWWWWaishouldenablemobileVthissentenceshallreadtheserequirementsshallbeconsistgV߿Vfbcertification޺WqWWchanceWWchanegWWWchanegtheentiresentenceasfollowsthephysicallayermeaVVVchangeޘWޜWޟWޠWޤWަW޲W޴W޸W޹W޺W޿WWWWWWWWWWWWW>WLWMWNWWWXW[W_WcWhWiW|W}W~W߶WߺWWWWWWWWWWWWWW W WWWW W.W3W<W=W>WAWHWIWZWiWqWWWWWWWWWWWWWWWWWWWWWissection_VchangedetailedtofunctionalVVchangefigure2tofigure3-2ޜVVchangefrom802.20tosystemrequirementsforieeestandardV߶Vchangelayertoiso/osilayersVVchangeline6shallreadforthe802.20packetmobilewirelehVV  baccount޺WWqWWWWaccountingWWaccuracy޺WqWWachieve޴W޻WiWuWWachievedރWލWWWkWtWWWWWWWWWWWWacrossW WWWactiveWWWWW@WWactivitiesWWactivityWNWadaptationWwWWadaptiveW/WwWxWaddޗWޙWޚWޛWޟWޣWާWިWޫW޻W޾WWWWWWWWW WOW\W}WWWWWWWWWWWWWW<W?WJWNSWfWuWWWWWWWWWWWWWintegratedmbwaunderthefigurޗVVaddnewtextinline15seeadditionalrequirementsinsectiިVaddonline19implementationsmaysupporteithermodefddo޾VaddperiodatendofsentenceVVcprovidesWWW(W5W.W2WbWWWWprovision>W Wprovisioning`WWpublic-WWpublishedW1WpurposeޅWޏWWmWvW$W'W+W6W9WWWputsWqދWޕWWWqWWWWWWWWWqosވWފWޒWޔWWWWWWWW&WOWrWzWLWMWNWOWPWQW\W_WfWgWhWWWWWWWWWWWWW!Wquantitative)WcWquantityMWNWHWIWquiteޮWVW$W'W+W.W0W2W6W9WLWPWQWRWratesޅWވWޏWޒWWWWWWGWRWmWvW}W~W$W'W+W.W2W3W4W6W9W<W=WLWPWQWratherW]WWratioޅWޏWWmWvW$W'W+W6W9WjmaybeOWmbwaWWWmeވWmeaningWmeansާWWmeasurementyWWmeasurementsWmeasuresWmeasurmentsWmechanismvWmechanismsLWWmeetNWmeeting~WmeetingsgWmeetsޘWmergdKWmergeWmergewithcommentsfromothersVmessageWmessagesWWmessagingWWmetFWmeta-requirementWmeta-requirment޺Wmethod WmethodologyzWmethodsWghtQWmimoSWjWnWmineWmineprintswithpagenumbersVminimumߎWߙWߟWߠWߡW߳WߵWmobileZWWހW߶W߽WW WNWWmobilityxWޥWmodelOWmoderateߧWmodesߙWmodificationކWމWW3WmodificationsyWmodifyޥWߝWWmodifythefirstpartofline8foroption2asfollowsߝVmodifyingߖWmodulationߣWwWmonitoringWmore W߀WߓWmoveߓWmsHWkt^Technical, Binding_18`30a4.3bDelete the sentence. c6Redundancy in line 30 - "The AI shall be designed ..."d63g2422iKlerer mAccepted 2004/07/02 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18`33a4.3bAdd a new sentence before "Channel bandwidths..." in line 33: The 802.20 standard shall specify which channel bandwidths would be mandatory and which would be optional".cMNeed to state that some channel BWs should be mandatory and others optional. d64g2423iKlerermRejected 2004/07/02 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18`35a4.3bChange the sentence as follows: " The 802.20 standard should be kept up to date with future advancements in radio technology and availability of spectrum that would be suitable for deployment of wider channel bandwidths."cW@WLWRW[W`WaWbWcWkWmWrWtWvWzWߺWWWWWWWWWWWWW WWWWW$W'W+W1W3W6W9W[WlWzW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!WshouldimpliesarequiredfeaturewhichisnottrueVVshowUWaWWWWshowsKWWsightWWsignificantlyWsimilarCWGW4WeWWstageWstandardޛWWstandardsޚWWstateWstatementWstatementsWstatesWY8cneedtoconsolidatewithorrefertosection4.4.1thatdiscިVJVneedtodistinguishintra-uservsinter-userqosrequirementVNVneedtostatethatsomechannelbwsshouldbemandatoryandVVVneedtosupportnon-burstytrafficaswellburstycaseisclVVneededWWWWWWWneedsވWޒWާW޵W޷W޼WWWWW?WOW߻WWW W1W?WAWLWPWQW\WfWgWhWnW~WWWWWneeed@WzWnegative2WWneither WWnetworkދWޕW޿WWWWW9WOWVWXW]WqWWWfWWWWWWWWWWWWWWWWWWWWW.WSWTWaWWWnoideawhatthissectionistryingtosayVnon-burstyWWnon-discriminatory-WWnon-lineWWWXjthemeaningofthecuurentsentenceisadesignconstrainttVthemultilpierof1.2needsexplanationotherwiseitappearsޥVtheproposedtermsclosedcoupledlooselycoupledmutuallyc߈VthereferencelisthasnotbeenkeptuptodateitshouldeiVtherequirementforminimumdelayspreadneedsspecificationߠV߄Vtherequirementsonthedlandulpeakuserdataratesasst߀Vthesectionandtexthavebeenreviewedandvotedbythewor]Vthesentenceshouldthenbetheieee802.20standardformstVthestandardshouldprovideascalablesolutiontoaccomodatqVthesuggestedparaphrasecouldbeinterpretedtoimplythat޷VthesystemshallworkindenseߝVthetextchangeisokifthevalueischangedinaccordanceަVthetextforoption1wasproposedinjanuary'smeetingint~VtheirWthenޡWWther޷WthereWWߋWthereisnothingwrongwiththepresenttextVy 2004/07/02 2004/06/04MarkedEDanFGalGMember^Technical, Binding_19`4a4.4.1bDchange to: "The 802.20 MAC design shall specify mechanisms ..." etc.c(inappropriate text "802.20 protocols..."d68g2430iKlererj-There is nothing wrong with the present text.mAccepted 2004/07/02 2004/06/04MarkedEDanFGalGMember^Technical, Binding_19`4a4.4.1b+Add after "(QOS)": "control and monitoring"c&vague "...(QoS)" - need more specifityd69g2431iKlerermAccepted 2004/07/02 2004/06/04MarkedEDanFGalGMember^Technical, Binding_19`4a4.4.1bsuggest that we delete it or replace with the following: "The MAC's QoS provisions shall allow flexible and reconfigurable implementations that would facilitate Service Providers' applications which require provisioning of users' QoS capabilities. " c%redundant second semtence (lines 4-6)d70g2432iKlerermAccepted 2004/07/02 2004/06/04Markedg4337 2004/07/02tx*FGalGMember^Technical, Binding_19`19a4.4bAInitial text for this new sub-section: " The 802.20 MAC design shall support both FDD and TDD modes. It will take into account the architectual requirements of section 3.1.1 as well as the need for flexible, future proof design that would readily accommodate changes in the PHY layer as well as in upper layer. To the extent that performance is not taxed significantly, the MAC should abstract general purpose functionalities and keep the number of PHY-specific optimized functions to a minimumBj. Such functions would have a role similar to that of device drivers in personal computer architectures."XcFAdd a new subsection "4.4.2 - MAC Design and Performance Requirements"d67g2426iKlererjSee reply to previous commentmRejectedbsignificantlyWWWWWsimilar޺WWqWWWWsimple[W\WWWWsimultaneousާWWW?Wsince=WWsiteWsizeWWWWsizesޟWWWjWsleep-mode޻WuWWsnr޺WqWWsoތWޖWޢW޴WWWWsW{WWiWWWWWWWWWWn޶WWIWWWpWsolutionsWWsomeޙWWWWW.W2WWspaceޝWWspacing޺WqWspansޡWWspecificޫW޺WWWWWSWqWspecification޺W߾WqWspecifications޺WqWspecifiedޣWޥW޺W޽WW?WEWWWWW*WqWWspecifyރWލWWWWWW5W7W8WkWtWWWWWWWWWWWWWWWWWW!bphysical޺WWWW߽W߾W_WqWWWWWpickWWpickoption3VVpicoEWWpicocellsPWWpleaseWWpleaseclarifywhatexactlyistherequirementVVpluralWpointiWWpoliciesWMWWpolicy-basedMWportionWWpossible޻WWW WWW_WuWWpossiblyWpotentiallyW#WWEWpotocolWpotocolinlayers1and2Vpower޺W޻WWcWqWuWwWWWWWpppWWpractice WrWpracticepractices VrVpracticesW WWrWsWprecludeWWIWWpWWtextforsection4.2.1.1general޺Vprotect޹WWW Wprotected Wprotection޹W WprotocolޛW޶WWWWWprotocolsWWprovide޹WWWWWWWW W WW/GbdesignedWWZWWWWdesignsWW'rbthe802.20macdesignshallspecifymechanismsetcVVVthe802.20maclayerprotocolsshallprovidemechanismsfortVVthe802.20standardshallalsoaddressestheneedsoflogicaVVthe802.20systemshallprovidethemacandphycapabilitiesVNVthe802.20systemshallsupportnon-lineofsightoutdoorto}V<VhallbeisoptimizedforVtheaishallprovideallthehookstoenabletheprovisioninVtheaishallsupportdifferentmodesofspeeds250km/hitiFVtheaishallsupportsVthelineshouldread?Vthemaclayershouldbeabletocontrol100simultaneousactVthesentenceshouldreadthe802.20-basedsystemsshallprovQVthesentenceshouldreadthisdocumentestablishedthedetaijVthesystemshallsupportanarbitrarysetvarietyoftrafficVthesystemshallmustsupportbothipv4andipv6Vthesystemwillshallprovideappropriatemacandphycapabi VtheftW+h=bthe802.20macdesignshallspecifymechanismsetc@}the802.20systemsmustbespecifiedtoenableubiquitousmo@theaishallsupportdifferentmodesofspeeds250km/hiti@0their@mthissectionshouldreadthe802.20aishouldenablemobile@those@~time@togc11@120km/hr@2-1@5-criteria@802.20mechanismsnotclear@aߺasimpleeditorialchangetoelinateunneededwordsinthef@able@addaclarificationonimplementation@jagnostic@allcurrentthreeoptionsneedimprovementaddoption4@and@anntenna@architecture@arq@ average@awk@bad@based@`beLbearer@break@_bws@scall@Nchangearetoshallbeandinsertapprovedbeforepar@clarifyawkdefinition@columns@Jcomponents@Iconstruction@convergence@defined@design@does dPbcost޻WuWWcould޺W>WbW WqWWWcoupledWWcoupled/looselyWWcoverageWWWEW}WWW0W3W<WwWލWWcryptographic޷WcurrentޛWޤWWcurrentlyW.WdataޣWޤWޥWޯWޱW޴W޹W޽WWWWWWWWWW W WWWWWW W)W@WdatagramWdateWdecidingWdecoupledWdefine޺WWWWWW%W)W*W+W;WdefineanactiveuserasonewhocangetaccesstoabearerVdefinecontrolcapacity%Vdefinemoderate*Vdefinerequirementsfordelayanddatarateloss)Vdefinesofthandoffandhardhandoff;Vdefinewhatisinterconnectivityatthephy/mac+Vdefined޺W޽WWWWWWdefinition޵WWdefinitioninthisdocumentthetermsystemspectralefficieV^bsuitableWWWsumWW.W2WsupportތWޖWޟW޴W޾WWWWWWWWWWWWWWWWWWWWWWW2W3WDWEWFWGWHWLWWWXWbWsW{W}WWWWWWWWWWWWWWWW3W4W<WKWMW^W_WiWmWvWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsupportoption2forperformanceundermobilityanddelayspVVsupportoption3asfaraslatencyrequirementsareconcerneVKVsupportedާWWWWW?W^WWsupportsWWWWsustainedWWWWswitchWWWWWWWWWWWWWxEHariFGantiGMember^Technical, Binding_Technical, Binding`6a1.3bKeep the desired minimum spectral efficiency figure of 1 b/s/Hz/sector; however, specify the conditions under which this spectral efficiency is to be attained.cA1. Spectral Efficiency (page 6 - Table 1.1 and page 12 - Table 4.1): Table 1.1 states that the system should have sustained spectral efficiency of 1 b/s/Hz/cell whereas Table 4.1 states that the downlink spectral efficiency should be 2.0 b/s/Hz/sector at 3 kmph and 1.5 b/s/Hz/sector at 120 kmph. As for the uplink, Table 4.1 lowers these numbers to 1.0 and 0.75 b/s/Hz/sector respectively. These numbers have little meaning in the absence of the channel conditions under which the system is ing4337 2004/07/02 2004/07/02MarkedEHariFGantiGMember^Technical, Binding_Technical, Binding`13a4.1.6bRDefine an active user as one who can get access to a bearer channel within 100 ms.cThere are hardly any applications that require bearer access time as low as 25 ms. Consequently, setting the access time requirement to be 25 ms is likely to be perceived as too restrictive.d72gThere are hardly any applications that require bearer access time as low as 25 ms. Consequently, setting the access time requirement to be 25 ms is likely to be perceived as too restrictive.iKlerermAccepted 2004/07/02MarkedEHariFGantiGMember^Technical, Binding_Technical, Binding`15a4.1.7b>Support option 3 as far as latency requirements are concerned.d73iKlerermAccepted 2004/07/02MarkedEHariFGantiGMember^Technical, Binding_Technical, Binding`18a4.2.3bCSupport Option 2 for "Performance under Mobility and Delay Spread."d74iKlerer 2004/07/02 UcBGtended to achieve them. Even the specification of the speed of the mobile terminal does not fully characterize the channel conditions. (Additional parameters such as the number of multipaths, their relative strengths and delays, specular components, etc. would be needed for a complete specification of the channel conditions.)5d71gA1. Spectral Efficiency (page 6 - Table 1.1 and page 12 - Table 4.1): Table 1.1 states that the system should have sustained spectral efficiency of 1 b/s/Hz/cell whereas Table 4.1 states that the downlink spectral efficiency should be 2.0 b/s/Hz/sector at 3 kmph and 1.5 b/s/Hz/sector at 120 kmph. As for the uplink, Table 4.1 lowers these numbers to 1.0 and 0.75 b/s/Hz/sector respectively. These numbers have little meaning in the absence of the channel conditions under which the system is in pgBGtended to achieve them. Even the specification of the speed of the mobile terminal does not fully characterize the channel conditions. (Additional parameters such as the number of multipaths, their relative strengths and delays, specular components, etc. would be needed for a complete specification of the channel conditions.)5iKlerermAccepted:bkeeping޻WuWWkept޽WWWWWWkey޽WWWkm/hWFWWWkm/hr޽WWWland޺WqWWlastBWWlatencyWWWWWKW^W_WlayerޛW޺WWWWWWWWW߽WWWWWWMW_WqWWWWWWWWlayer-3iWWlayerprotocolsWWlayers޶WWWW߾WWWWW^WlayerstheW߽Wlead-inbWWleastޟWW3WMW߽WWHWWlengthW_WlessަWWWMWW>WAWHW_WWlessen>W Wmac'sWmac/phyWmaintenanceWmanagementWmandatoryWmanner޺Wmasks޺WmaximumޥW޺WWmay޾WWWWWWWWmbsޥWmbwaޗWޙWmeasureWmeasurementWmeasurementsW3~csystemވWޒWާW޳WWWWWWW W WWW1W2W3WAWMWW߾WWWWWW.W0W2W3W?WHWLWPWQW[W\WgWhWwWWWWWWWWWsystemmustworkunderthevariousenvironmentsofamacro/mVVsystemsWWLWWWWWWtMWtableޞWޟW޲W޳WW!W=WWWWWW"WZW[Wtable4-2ambiguous!V"Vtable4.1specifiesadownlinkspectralefficiencyof2.0b/VWW WWtechnologyދWޕWWWWEWGWqWWteeth'WtelematicsWWtellsOWtendެWtenseWWterm޴W޿W\W_WterminalފWޔWWWW<WrWzW߸WWterminalsW$WWtermsWW4WWWWWWWWWWT4TctherearehardlyanyapplicationsthatrequirebeareraccessV@VV€- €marked˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~߶߷߸߹ߺ߻߼߽߾߿ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃mAccepted 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_11`5a4.1.1bSpecify 2 bits/sec/Hz/sector as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved. cAThis requirement specifies stringent spectral efficiencies without explicitly clarifying the conditions under which it should be achieved. For example, because cell size is not constrained by the requirements, the spectral efficiencies could be achieved with very small cells. Or, for example, operation at 120km/hr is very different depending on the environment - certainly we are not interested in operation at 120km/hr in an urban setting, yet the requirement could be interpreted that it iBs applicable under all channel conditions. The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.g2683iKlererjSee reply to initial comment.mRejected-Duplicate 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_11`5a4.1.1b5Remove the distinction between uplink and downlink. c The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.d76g2684mAccepted-Duplicate 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2cA3Option 1 peak rates result in a large user data rate peak to average ratio of the order of 10:1 and will rarely be seen in practice (see C802-20-04-33r1). We should therefore not artificially limit proposals to large peak data rates whose sole purpose is specs-manship and will rarely be seen in practice. 3d77g2685mAccepted-Duplicate 2004/07/02MarkedEMarcFGoldburgg4344 2004/07/02 cd75 ?cexplicitlyރWލWWkWtWWWWWWWWWWWextensibleW7W_WW WextensiveWextractWfactorާW?WfactorsEWWfair-WWfairnessW0WfastbWWfdd4WWfdmaWW.W2WfeatureފWޔWWWWrWzWWWWWWWWWW!WfewWW.W2WfigureޗWޙWޜWWWWWWWWWfiguresޛW޳WW[WfillOWfWfinalWWfinalizedWWfirstވWޒWWWLWPWQW\WgWhWWWfixed_WWWflexibleވWޒWWWWLWPWQW\W_WgWhWWWWWWWinoption3line4missingdatarateޯVinoption4line27missingdatarateޱVinthetableofoption4confusingcolumnheadingtrafficcl޲Vmsupercededp+,/04589>@PRWgis{ۃ܃݃ރ߃€markedރބޅކއވމފދތލގޏސޑޒޓޔޕޖޗޘޙޚޛޜޝޞޟޠޡޢޣޤޥަާިީުޫެޭޮޯްޱ޲޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃɃ)^Technical, Binding_12`22a4.1.5.1b#Remove option 1 and adopt option 2cfThe concept of bandwidth must be clarified given that we are not requiring specific channel bandwidthsd78g2686iKlerermAccepted-Duplicate 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d79g2687iKlerermAccepted-Duplicate 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_14`16a4.1.7.1bRemove this section. cg4346 2004/07/02k`‚4޶:MbHஃу‚5[|ަXߣ>w‚6H޿܃'/05ߕߖߪ߫axyʃ‚7Z$;Yc߷Fః҃‚8ޱ޷ߑ Y‚9޻u‚:Rvމޓ޸޹ӃJZpy߃ߎߏߟߡ߳ߵ B|}ృӃ߃ ‚A޲޳?[\ߗZ[ಃೃ‚BޭU‚C]ഃ‚Dƒ6ߘ߰ ‚E7;DJbjދޕՃ^qൃඃසใໃ༃གྷ‚FqÃ7BTࠃ ‚H(b‚IޮV3.1.1ޚޛޜă4.1.1ރބލގޝޞ̓΃kltu4.1.1.11.2?4.1.10޵g2688iKlererj.See comment to initial comment in this sectionmAccepted-Duplicate 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d81g2689iKlerermAccepted-Duplicate 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_20`7a4.5.3bRemove sectioncThis is a feature of the user terminal and backend infrastructure and is irrelevant at the MAC/PHY layer. In addition, the need for high priority should be captured within QOS frameworkd82g2690iKlerermAccepted-Duplicate 2004/07/02MarkedEMarcFGoldburg^Technical, Binding_19`34a4.5.2bRemove Section cg4349 2004/07/02 HcAThe QoS requirements in the document today eg. DiffServ, flexible ARQ schemes, etc., can be used to create QoS profiles that meet the needs of the applications several years from now when .20 is first implemented. Furthermore, our PAR specifically says that we are designing a system optimized for IP-data transport. That means the 802.20 air interface will handle applications over TCP and UDP that in turn require low error rates and low latency. In addition the current requirements documBW W WprobabalisticMWHWWޒWWWpromotecWproperWgW߿WproperlyWproposalWWWW.WproposalsރWބWޅWލWގWޏWWWWWkWlWmWtWuWvWWWWWWWWWWW$W'W+W6W9Wproposed޺WproposingWprotection WWprotocol޷WW Wprotocolinlayer1and2VprotocolsWproveWprovide޵WW)WWWWprovidersaWg2215iKlererji prefer option 2mRejected 2004/07/02 2004/06/08MarkedEKazuhiroFMurakamiGMember^Technical, Binding_15`16a4.1.7bRemove this section. cAThe QoS requirements in the document today eg. DiffServ, flexible ARQ schemes, etc., can be used to create QoS profiles that meet the needs of the applications several years from now when .20 is first implemented. Furthermore, our PAR specifically says that we are designing a system optimized for IP-data transport. That means the 802.20 air interface will handle applications over TCP and UDP that in turn require low error rates and low latency. In addition the current requirements documB?@AB߸Ń˃ lznisely݃ރ߃ murakami׃؃كڃۃyuzamemberރލޗޘޙޚޛޜޝޞޟޠޡޢޣޤޥަާިީުޫެޭޮޯްޱ޲޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃɃʃ˃̃׃؃كڃۃjocableWW@W.W2WzWaboutWWaboveޞWWabsenceWWacceptableWacceptanceWaccess޷WWMW W@WHWWaccomplishedދWޕWWWqWWWWWWWWWaccountingWWaccumulatedތWޖWWWsW{WWWWWWWWWachievableWachieveWRWcWW{WWachievedރWލWWkWtWWWWWWWWWWWacrossދWޕWWWqWWWWWWWWWactualWadaptive/WxWadaptivebandwidthallocationnotclear/VxVaddީWުW޽W޾WWWWhW߹W߼WWRWWWWWWWWWWWg2218iKlererj8this is a duplicate comment see reply to initial commentmAccepted-Modified 2004/07/02 2004/06/08MarkedEKazuhiroFMurakamiGMember^Technical, Binding_19`8a4.2.3bAdopt Option 3 c:"Option 3 is simple, straightforward, and well defined. " d87g2219iKlererjSee reply on initial commentmAccepted-Duplicate 2004/07/02 2004/06/08MarkedEKazuhiroFMurakamiGMember^Technical, Binding_21`9a4.5.2bRemove Section cAAdvocating a specific mechanism for separation of traffic does not allow 802.20 to maintain a network agnostic approach. This can be accomplished in many ways allowing use of 802.1q tagging, PPP or MPLS across the air interface without specifically mandating any particular technology at layer 2 Eg. 802.16 defines a convergence sublayer when VLAN frames are to be carried over the air interface without mandating 802.1 q at layer 2d88g2220iKlerer 2004/07/02 c*d862]cgetW.WgivenކWސWWYWnWwW%W(W,W7W:WWWWWglobalWWW߹WߺWWWglobaladdpagenumbersV߹VVglobalieshouldalwaysbefollowedbyacommaVߺVgoal WWgoesUWWWgoodtWgradually@WzWުW޿WhighފWޔWWWhomeWhowererWhzޝWiWietfWifWWill-definedއWޑWWimplementation޾WimplementedވWޒWWWimportantީWWimprove޶Wimprovement޽WinރWޅWވWފWދWލWޏWޒWޔWޕWޘWޚWޡWެWޮWޯWްWޱW޲W޺WWWWWWWWWWWWWWWWinoption3line4missingdatarateޯVinoption4line27missingdatarateޱVinthetableofoption4confusingcolumnheadingtrafficcl޲V9cunderރWވWލWޒWޙW޳WWWWWkWtWWWWWWWWWLWPWQW[W\WgWhWWWWWWWWWWunderstoodNWIWunderwayWunicastLWWuniqueWunknown.WWunlikeWunmeasurableWWunncessaryWWunnecessarilyރWބWލWގWWWWkWlWtWuWWWWWWWWWWWWWWWWWWWWW WunnecessaryWWBWDW W WunnecessaryinformativesentencecreatesmoreproblemsthatVDV VunneededBWWuntestableWWWWupGW4WWupgradesWWTc11ޡWW12WW12.32GW4WW120WWW carchitectureWW.W2WMWareރWކWވWދWތWލWސWޒWޕWޖWWWWWWWWWWWWWWWWW$W0W4WGW]WaWgWkWnWqWsWtWwW{W߿WWWWWWWWWW%W(W,W.W1W3W4W7W:W@WAWFWLWPWQW\W]WgWhWwWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWargumentsWaround W^technicalWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWWWWWWW W!W"W#W$W%W&W'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;WCWGWLWMWNWOWRWSWTWUWVWWWXWYW[W\W]W^W`WaWbWcWdWeWfWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W߀W߁W߂W߃W߄W߅W߆W߇W߈W߉WߊWߋWߌWߍWߎWߏWߐWߑWߒWߓWߔWߕWߖWߗWߘWߙWߚWߛWߜWߝWߞWߟWߠWߡWߢWߣWߤWߥWߦWߧWߨWߩWߪWj$See reply comment to initial commentmAccepted-Duplicate 2004/07/02 2004/06/08MarkedEKazuhiroFMurakamiGMember^Technical, Binding_21`17a4.5.3bRemove sectioncThis is a feature of the user terminal and backend infrastructure and is irrelevant at the MAC/PHY layer. In addition, the need for high priority should be captured within QOS frameworkd89g2221iKlerermAccepted-Duplicate 2004/07/02 2004/06/08MarkedEKazuhiroFMurakamiGMember^Technical, Binding_21`25a4.5.4bReplace requirement with "The air interface shall support the collection of metrics so that a network operator can effectively monitor the performance of the 802.20 air interfaces through various MIBs.cbAll options are overly detailed with respect to specific statistics that need to be accumulated. d90g2222iKlererjSee reply to initial commentmAccepted-Duplicate 2004/07/02 2004/06/08MarkedEDougFKniselyg4357 2004/07/02^Technical, Non-binding_5`4a1.1bA>These requirements are consistent shall comply with the PAR...>@AR  33  33"  33/  33RcQThe requirements shall conform to the PAR. If not, the PAR needs to be modified.d98g2212iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_5`6a1.1cadd comma after "standard"d99g2213iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_5`7a1.1bg4359 2004/07/02>^technical4W5W6W7W8W9W:W;W<W=W@WAWBWCWDWEWFWGWHWIWJWKWMWNWOWPWQWRWTWUWVWWWXWYWZW\W]W^W_W`WaWbWcWgWhWiWjWkWlWmWnWpWqWrWsWtWuWvWxWzW{W|W}W~WWހWށWނWރWބWޅWކWއWވWމWފWދWތWލWގWޏWސWޑWޒWޓWޔWޕWޖWޘWޚWޡWޢWަWާWީWޮWޯWޱW޳W޴W޵W޶W޷W޸W޹W޺W޻W޼W޽W޾W޿WWWWWWWWWWWWWWWWWWWWWWWWWWcthescopeofthisrequirementneedstoberefinedasworded޷V VthesentenceasanexampleisredundanthasthesamemeaningޡVVthesentencebeginningwiththe802.20isnotclearVVthesentencebeginningwiththisdocumentisnotclearinde߾VthesentencethephysicallayerprovidesisvagueandnotusVVVtheseparationofdownlinkversusuplinkspectralefficiencyބVގVVlVuVVVVVVVVVV Vthesub-sectionheadingdoesnotreflecttheintegritypart޸V Vthesystemisexpectedtoworkindensenotclearandalsoh1VVthesystemshallnotnegativecomment2VVthesystemshallsupport95notclear3VVthetable4-1captionshouldbeplacedabovethetableޞVVtheterminterconnectivityatthephy/macisnotclear޴ViVthetermnetworkisinappropriatehere޿VVVinginarequirementsdocumentweaWVd‚ރ߼Ã!߃߽Ã! Ã!0Ã!@ȃÃ!PÃ!`Ã!pKÃ!LwÃ!׃Ã!߹Ã"MÃ" Ã"0NÃ"`Ã"pÃ"Ã"xÃ"Ã#ߺÃ# Ã#0OÃ#@Ã#PÃ#`yÃ#pÃ#PÃ#Ã#QÃ$z߆Ã$ Ã$0Ã$@RÃ$PÃ$`Ã$p{߇Ã$Ã$ߢÃ$Ã%SÃ% Ã%@Ã%P Ã%` Ã%p Ã% Ã% Ã&ߣÃ& ߤÃ&0|Ã&@ߥÃ&PÃ&`TÃ&pÃ&UÃ&V}Ã&߶Ã'߾Ã' Ã'0Ã'@Ã'PWÃ'`Ã'pÃ'XÃ'Ã'Ã(Y߈Ã( Ã(0 ߉Ã(@!Ã(P"Ã(`#Ã(p$Ã(%ߊÃ(&Ã(~Ã)'Ã) (Ã)0)ߦÃ)@*ߧÃ)P+Ã)`,ߨÃ)p-Ã).Ã)ߩ:g2214iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_5`12a1.2b$Change "detailed" to "functional". cJThis document does not specify detailed requirements (whatever those are).d101g2215iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_5`15a1.2b"change "layer" to "ISO/OSI layers"c6Grammar and clarify what "layer" system is being used.d102g2216iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_5`20a1.3bChange "bases" to "basis"c wrong wordd103g2217iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_7`5a2b"work, home, and mobile"cg4363 2004/07/02 bAFor the purpose of this document, an "802.20 system" constitutes consists of an 802.20 Medium Access Control (MAC) and Physical Layer (PHY) implementation in which at least one Mmobile station communicates with a base station via a radio air interface, and the interfaces to external networks., for the purpose of transporting IP packets through the MAC and PHY protocol layersThe purpose of the 802.20 system is to route and/or relay packets (e.g., IP packets) between the external networks anBd the mobile stations. @Aj  335  33@  33A @ 33M  33W @ 33n  33w @ 33  33  33 @ 33  33$ @ 33%  33&  33'  33y @ 33  33jcAwkward sentenced100bpurposesާW?WpushWWput޵WWqosޥWWWWWWWWW&WOWVWWW*WMWNWOW^W_WfWWWWWWWqqualityWWqualitative'WaWqualityWWWWquality-of-serviceWWquantitative޽W'WaWWWWWquantitativerequirementisrequiredinsteadofqualitative'VaVquotedWDWHWIWW_WmWpWr$WFWradiation޺WqWWradio޺WWWW߽WWAWqWWWWWrand-WWrange޺WW^WqWWrangesWrateޣWޥWީWޯWޱWWWWWWW)WFWWW*W.W2W3WNWRWWWYW^W_WcWvWwWWQWWW[WcWgWhWjW߿WWWWWWW WWAWHWIWKbwithinަWWWWWW>W@WDWMWNWW WwithoutWWwlineAWWword,W0WfW5WoWyWwordsWBW.WlWWworkW$W1WAWSWWWFWWWWWworkhomeandmobileVVwouldޚWޥWާW޺WWWWWW*W?WqWWWWWWWWWxWWߺW_WxxxOWfWzeroW_Wc0.75WWW04-44QWW1ޅWޏWޛW޳W޼WWWWWWW^WmWvWWWWWWW$W'W+W.W/W1W6W9W[W~WWWWWW1alltheentriesofthetableunderoption4shouldbespec޳V[VAW1.5WGWWW4W10,W10:1ޅWޏWWmWvW$W'W+W6W9W10msވWޒWWWLWPWQW){bnewޛWިW޺WWWW}W~WW<W=WJWqWWWWWWWnatory-Wnon-lineW}WWnon-line-of-sightEWWnot޺WWWWWWWWW WWEWIWߺWWWWWnoteWWWWWnumberޤWާW޻WW WWWWnumbers!Woa&mWobject=WWoccupied޺WoctetWofތWޖWޗWޙWޛWޟWޢWޤWޥWަWާW޴W޶W޸W޹W޺W޻W޽WWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWW W'W>W@WDWFWGWIWLWMWOWPWfWsW{W}W~W߽W߾WWWWWWWWWWWWWWWWWWWAbgWWWWWWWWW WW|W߽WWWWWWWWMWNW^WjWWWgain޺WqWWgamesW_WgamingWWgatheringWWgeneral޺W޻WWqWuWWWWWget޽WW@WWWWghz߾WgivenޥW޹WWWW$WWW*WFWNWWglobal޺WqWWgloballyWߺWgloballychangeiexwhichisnotcommatoiexVߺVgood-putWWWgracefulW@WWvWzWWgracefullyWWWFWWWWWWWgraphicalWWgreaterާW޽WW0W3W?WWWhalt>W Whand޻WuWWhand-held޺WqWWhandoffW;WXW߷WWWWWhandoffsWhard;W߷WWWidentifier WidentifyWidentity޹W WcthisisafeatureoftheuserterminalandbackendinfrastruފVޔVVVrVzVVVVVVVVV!Vthisisstatedelsewheresection4.1.3itisaduplicatedreVVthisparagraphgoesintogreatdetailonwhatietfrfcstouUVVVthisparameterisunderstoodtobeascalablequantityhowevNVIVthisrequirementaswrittenplacesmayrequirementsonthemXVVthisrequirementspecifiesstringentspectralefficiencieswރVލVVkVtVVVVVVVVVVVthissectiondoesn'tbelonginthisdocumenteitherdeleteoRV{Vthissectionislackinginrfrequirementsitissuggestedt޺VqVVthissectionseemstobeadiscussionovertheairservicep`VVthissectionseemstohave3optionshoweveroption3doesnVnotwelldefinedinthisdocumentand\VWWun-meetableWunachievableWg2218iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_7`5a2bDelete "should" on line 5cW@WAWBWCWDWEWFWGWHWIWJWKWLWNWOWPWQWRWSWUWVWWWXWYWZW[W]W^W_W`WaWbWcWdWeWgWhW$cworkWW1WAWOWWWWWfWWWWWworkingdWeWWWWWworstW0WwouldވWޒW޶WWWWWWEWGWWWWWWW0W4WLWPWQW\WgWhWWWWWWWwritingWWwrittenLWXWWtWWWwrongWWWwrongwordVVVxxxOWfWyearsވWޒWWWGW4WLWPWQW\WgWhWWWWyetރWލWWkWtWWWWWWWWWWWd 4gރ05ބ@hޅ߀$Pކ%`އ&piވPމߎ|6ފ7jދ‚!8ތ‚"9kލ‚#lގ‚$mޏ߁'‚%ސ(‚&ޑ)‚'nޒQ‚(ޓߏ}g2220iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_7`15a2bAApplications: The AI shall support applications that conform to open standards and protocols. This allows applications including, but not limited to, full screen video, full graphical web browsing, e-mail, file uploading and downloading without size limitations (e.g., FTP), streaming video and streaming audio, IP Multicast, Telematics, Location based services, VPN connections, VoIP, instant messaging and on- line multiplayer gaming. @A.  33  33  33  33  33 @ 33  33 @ 33  33 @ 33  33  33   33J  33V  33.c9Wording, grammar, clarity What the heck is "Telematics?"d107g2221iKlererjretain - Telematics 2004/07/02 bBomplexity and quality-of-service management. Applications that require the user device to assume the role of a server, in a server-client model, may can be supported as well. @AV  33$  33,  33- @ 330  33~  33  33 @ 33  33  33-  336  33? @ 33B  33  33 @ 33  33VcAEntire paragraph should be informative, not normative. These are marketing statements and are untestable at a minimum. Also, statements like "shall be designed to provide best-in-class" would require a pedantic definition of what technologies define "class." Claims that 802.20 is better than "other systems targeted for wide-area mobile operation" are un-meetable and unnecessarily inflammatory.d106iUboperations޽WWWoperatorތWޖWWWWWWsW{WMW^WWWWWWWWWWWoperatorsWWoppositeWWWoptimal޻WuWWoptimizeWWoptimized޻WWWW߾WWWuWvWWWWoptionޅWކWއWމWޏWސWޑWޓWޥWޮW޽WWWWWWWWWWW"WJWKWOWSWmWnWoWpWvWwWxWyWW#W$W%W&W'W(W)W*W+W,W-W.W/W1W3W6W7W8W9W:W;WKWVW]WfW|W}WWWWWWWWWWWWWWWWWWWWWtion3Voption1preferredthe802.1qsectionshouldbedroppedVVoption3ޥV*VoptionalWWWoptionallyXWWWmbsystemޥW޹WWWWWWWWWWWWWW WWWWW W1W2W3WAWDWEWLWNWPWSWWW}W~W߶W߽WWWWWWWWWWWWWW!W*W.W0W2W3W<W=WDWIWMWNW^WwWWWWWWWWWWWW WWsystemsޙWWWWWDWEWLWQWXW|W߶W߾WWWWWWWWWWWWWޟWޣWޥWްW=WfWWWWWW*W3W5WXWtaggingWtakeWWtaking޺WWWqWtargetWWWWtargetedWWtargetsWWW.W2W3W_WtaxedWWtbdLWWtbrOWfWtdd޾WWWWWCWWWtechnicalW centireparagraphshouldbeinformativenotnormativetheseaVVentirely޼W~WWentries޳W[WenvironmentރWލWWJWkWtWWWWWW]WWWWWWWenvironmentsWWWequalW0WequipmentUW`WaWtWWWWWWerrorވWޒWWWCWLWPWQW\WeWgWhWWWespecially޹WWessentialWWetcވWޒWWWW5W<WRWUW߸WWLWPWQW\WgWhW{WWWWWWevaluatingW1WevaluationW.WevenWWW.WevidenceWexactWmAccepted-Modified 2004/07/02MarkedEDougFKnisely^ Editorial_8`14a2.2bAdd period at end of sentence.c"Missing period at end of sentence.d108g2222iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_0`0a0cGlobal: Add page numbers!d109g2223iKlererjMine prints with page numbersmAccepted-Clarified 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_8`14a2.2bABroadcast Service - the ability to transmit a packet of information (e.g., an IP broadcast datagram) to all mobile terminals within an 802.20 system or a portion of an 802.20 system. Note that a particular mobile terminal may choose to receive or ignore individual information packets that are delivered via the broadcast service. Multicast Service - the ability to transmit a packet of information (e.g., an IP multicast datagram) to a subset of all mobile terminals within an 802.20 system g4369 2004/07/02bapplicationstheaishallsupportapplicationsthatconformVVapply޺W޽WqWWWWapproachOWfWappropriateޙWޥW޳W޹WW WWWW*W[W_WvWWWtectureWarchitectualWarchitectureWWWEWPWiW|WWWWWarchitecturesWareޙWWWWWWWWWWWWW$W5W8WNWXWiW|W߻WWWWWWWWWareasW1WWarrivedWarrivingWasރWލWޛWޟWޡWޥW޴W޵W޺W޻W޽WWWWWWWWWWWWWWWWWW WW?W@WAWBWCWDWHWIWMWNWRWSWTWbWkWtWWWWWWWWWWWWWWWWWWW*W$bassignment@Navailable@ibandwidths@bexbearer@bottom@ibursty@XcapabililitesHWcapabilities@certification@nchangeavailablewithadelayoflessthan25ms@fchangemitigateagainsttomitigatedenialofservicemitiga@Hchangetoduplexingschemesfdd/tdd@changetrafficclassestoservicecharacteristic@Lcharacter@0columns@complexity@conferencing@consisting@cost@cpe@Pcryptographic@datagram@nrposeofthisdocumentan802.20systemconstitute@|from%ftp@g@hardware@Aidle@eincorporated@ integrated@@iso/osi@:keeping@level@low@3mechanisms@cmedium@?mobilestationsshallperformwellquantitativerequirements@Omovetable4-1captiontopage11line23@mt@nearnecessary@network@)new@offline@ioperations@Lg2224iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Binding_8`14a2.2bA^Add "The 802.20 system shall support the ability to restrict the delivery of multicast information to mobile terminals that are authorized to receive the multicast information. The 802.20 system shall support the ability to preclude mobile terminals from receiving multicast information for which the mobile terminals are not authorized to receive."^cGMulticast authorization and security requirements need to be specified.d111g2225iKlererjI believe instead of precluding from "receiving" it is probably precluding from "decoding". Promiscuous terminals can recive any address but may not be able to decode.mAccepted-Modified 2004/07/02MarkedEDougFKnisely^Technical, Binding_8`14a2.2g4371 2004/07/02 JbBor a portion of an 802.20 system. The multicast target for a multicast information packet is identified by a multicast address. Each mobile terminal can choose to receive and deliver multicast information packets based on the desired multicast address(es).c*Define "broadcast and multicast services".d110-0gbbAgdFgm`b^bAgkbBgbBgbBgbBg bA bA cbACgbAgmcAg@)bF"!b$!c(%^.(c1,F4/63c87E=<cF@mICcAMgLFERgQGcAVgUJF\g[Ld`g_yBbaO^hPcjSEoUbpWctYbx[cz^a}aEcfchck^kn_qcAgtbuEwb{E}c߆^ߍ^ߓjߘjߚ%d_Oxޙޚޛ‚!ޜă‚"459BIP]`gklyރބލގޝ̓΃kltu׃؃كڃ уFGfmnovwx $%&'()+,-/3456789:;ۃ܃݃‚$ޥަ !"#$M}~!"#*012<=>ABEFH ‚%ވޒާިީޫެޭޮ҃׃%&'(CN.?CDGIJMNOPQRSTUV\]^_`abeghރ ‚&ޯްޱ޲޳؃)*OLWXYZ[cdfl2caverageޅWޏWWW WmWvW}W~W!W$W'W+W0W3W6W9W<W=WWWaverageuseddatagreaterisnotinexcessofexistingtechn V!VaverageuserdatarateisnotdefinedanddependsonthenumV0VavoidWWastandmulticasttrafficefVbeރWޅWކWވWފWދWތWލWޏWސWޒWޔWޕWޖWޛWޞWާWުWޮW޳W޵W޷W޺W޼WWWWWWWWWWWWWWWWWWWWWWWWbearerWbecauseރWލWWbeforeWbeingWbelow޺Wbest-in-classWbetterWbetweenރWބWލWގW޳WWWbillableWbillingWbindingWbroadޚWbroadcastWWbroadcast/multicastWWWbroadcast/multicastservicemustbebillablewhilethisismVburstyWbutWjibelievebitratethoughaninportantserviceattributeisީVibelieveinsteadofprecludingfromreceivingitisprobablVibelieveweneedtoallowforlegalinterceptsothenotifi޹VicnlivewiththisifitbecomesashouldorinformativeasUVidonotsupportoption4alsodetailedremedyisnotspecif޳Vipreferoption2Vistillpreferoption3޽VidleWWidscussionOWieeeWLW߶Wietf~WހWifQWޘWޡWަWެW޲WWUWWFWWifwedeletethatsentenceweneedtomakeitclearsomehowQViiyWimageWimplementWimplementationWbAdd "The 802.20 system shall support the delivery of multicast traffic that is addressed using IPv4 and IPv6 broadcast and multicast addressing. "cFBCMC must support IETF IP broadcast and multicast traffic efficiently.d112g2226iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Binding_8`14a2.2bAdd "The 802.20 system shall support interoperation with external networks that utilize IETF-specified broadcast/multicast routing protocols for both IPv4 and IPv6 (e.g., IGMP)."cR802.20 systems should work effectively with broadcast/multicast backbone networks.d113g2227iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Binding_8`14a2.2bg4373 2004/07/02g2228iKlererj$OK except "dells" should be "cells"mAccepted-Modified 2004/07/02MarkedEDougFKnisely^Technical, Binding_8`14a2.2bAAdd "The 802.20 system shall provide the ability to support the efficient gathering of accounting information consisting of which mobile terminals are receiving which broadcast/multicast information streams and when the terminals start and terminate the monitoring activities."cBroadcast/multicast service must be billable. While this is most likely an upper layer issue for the most part, MAC layer support is likely to be needed in order to support billing and accounting in an efficient manner.d115g2229iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_9`4a3.1bA"The AI shall supports..."@Af  33  33   33 @ 33  33fc Not testable; not a requirement.g4375 2004/07/02 bAAdd "The 802.20 system shall provide the ability to efficiently identify when broadcast or multicast streams of information need to be transmitted from particular cells or sectors (i.e., when there are authorized mobile terminals present that are attempting to receive those information streams). The 802.20 system shall provide the ability to disable the transmission of broadcast or multicast streams of information in particular dells or sectors when those information streams are not needeB{d (e.g., when there are no authorized mobile terminals present that are attempting to receive those information streams)." icAEWireless broadcast/multicast services need the ability to turn particular streams of information in specific cells or sectors on a dynamic basis based on the presence of mobile terminals that desire and are authorized to receive the specific streams of information. Air interface support for these capabilities is essential.Ed114xibbearerWWMWW@WAWHWWWbecomeBWTWWWbecomes=WWbeforeWWWWWWWbeginningWWbehaviorsWWbeing5W8WWW Wbelow߾WbestޥWWWWWWW*W_WsWWbest-in-classWWbetweenބWގWWWWXWbWlWuW߽WWWWWWMWNWWWWWWW WbitީWWNWRWWbits/sec/hzkWtWWWWWbits/sec/hz/sectorރWލWWWWWWWWblockޟWWWWblocking޺WqWWbootpWWbootstrapWWboth޹W޻W޽W޾WWWWWW&W2WHWWWWW WWOWmWuWwWWWWWWWWWWWWWWWbs޽WHWtes bbaddthe802.20systemshallprovidetheabilitytoefficientVVaddthe802.20systemshallprovidetheabilitytosupporttVVaddthe802.20systemshallsupportinteroperationwithexteVVVaddthe802.20systemshallsupporttheabilitytorestrictVVaddthe802.20systemshallsupportthedeliveryofmulticasVVaddthefollowingsentencethustheaggregatedatarateperޣVVqcandރWބWޅWވWމWފWލWގWޏWޒWޓWޔWޚWޛWޤWުW޳W޺WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW$W(W)W-W0W1W4W<W>W@WAWCWGWOWPWVWWWXWZW[W\W`WbWdWeWgWkWlWmWpWrWtWuWvWyWzW}W~W߸W߿WWWWWWWWWWWWWWWWWWWWWWWWWWW W WWW W$W'W+W.W/W0W1W2W3W4W6W9W<W=WFWLWMWPWQW[W\W_WbWcWeWfWgWhWqWtWyWzW|W}WWWWWWWWWWWWW%uHcorphanޫWޭWSWUWorphanreference7ޭVUVorphanreferenceitu2thereisnoreference2ޫVSVotasp`WWotherޚWުWWW W,W-W0W9W<WCWTW߸WWWWW1WeWoWyWWWWWWWWWAWoverވWދWޒWޕWWWWW`WqWoverallWWoverlyތWޖWWWsW{Wp&pWpacketވWޒWWWhWWpageޡW޼WWW߹WWpaidOWparވWޒWުWWWWWCWgW߻W߿WWparagraphWUWWparameterWWKWNWparametersW WWWparsWpart޸WW`WW Wpartial޶W6WWparticularދWޕWWWWWcWqWWpartitioningWWparts,Wpast.WpeakޅWޏWWWWGWmWvW}W~Wd116g2230iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_9`6a3.1bDelete "bursty ".c`Need to support non-bursty traffic as well. Bursty case is clearly covered by rest of sentence.d117g2231iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Binding_9`7a3.1byDelete "The 802.20 AI shall support high-speed mobility." Alternatively, define speed requirements for mobility clearly.cNot defined; untestable.d118g2232iKlerermRejected 2004/07/02MarkedEDougFKnisely^ Editorial_9`12a3.1.1bBChange "will be" to "is" on lines 12 and delete "will" on line 13.c%Change future tense to present tense.d119g2233iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_0`0a0b; globally change "i.e." to "i.e., x"c7Global: "i.e." should always be followed by a comma. d120g2234iKlerermAccepted 2004/07/02MarkedEDougcnon-relatime޳W[Wnon-requirementWnon-requirementsWnon-testableWnorWwWnormativeWWW W WWWWWWWWWWWWWWWWWWWWWWWWWWnotarequirementimmediatelyobviousandaddsnovalueVnotasentenceVnotanexampleasadvertisednotrelevanttotherequirementVnotclearwhatismeantbypartialsolutionperhapsrephrasi޶VnotdefineduntestableVnottestableVnottestablenotarequirementVnowވWޒWWWnrt޳WnumberެWWWnumbersެWWWobviousWofރWބWޅWކWއWވWފWދWލWގWޏWސWޑWޒWޔWޕWޢWޤWީW޲W޳W޵W޶W޷W޸W޹W޻WWWWWWWWWWWWWWWWWWWWWEcgrammarWWWWgrammarandclarifywhatlayersystemisbeingusedVVgrammical=WWgrammicalproblem=VVgreatUWWW;WhardlyWharmonizeޥWhasޡW'W1WhaveޥWW4Wheading޲W޸WheadingsޤWheckWhereުW޿WhighފWޔWWWhomeWhowWWhowererWhte<WhzޝWiWWideaWidentifying WietfWifWWWWW4WiffWill-definedއWޑWWimmediatelyWimplementation޾WimplementedވWޒWWWWimpliesWimportantީWWWimprove޶Wimprovement޽WinރWޅWވWފWދWލWޏWޒWޔWޕWޘWޚWޡWެWޮWޯWްWޱW޲W޺WWWWWWWWWWWWWWWWWW WWW W1W4W<Wg2236iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_9`16a3.1.1bDelete "partitioning"cwhat is a "partitioning model?"d122g2237iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_9`18a3.1.1bAThe 802.20 standard shall also addresses the needs of logical link control and how and when the 802.2 LLC functionality is used. @Af  33  33  33&  33(  33fcInformative and not testable.d123g2238iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_10`2a3.1.1b#change "shall clarify" to "specify"co1. Not a requirements; not testable. 2. We don't clarify (and the figure doesn't clarify much either, FWIW).d124g2239iKlererjXchange to "shall specify". It is a meta-requirement on the specification to be produced. 2004/07/02bFKnisely^ Editorial_9`14a3.1.1b#change "PPP, MPLS" to "PPP or MPLS"cGrammard121mAccepted-Modified 2004/07/02MarkedEDougFKnisely^ Editorial_11`7a4.1.1bAODefinition: In this document, the term "System Spectral Efficiency" is defined in the context of a full block assignment deployment and is, thus, calculated as the average aggregate upper layer throughput per sector (bps/sector), divided by the spectrum block assignment size (in Hz)( taking out excluding all PHY/MAC layer overhead). O@A   33  33  33  33  33  33  33  33(  331  33>  33D  33cClarify AWK definition.d125g2240iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_11`16a4.1.1bchange "QoS' to "QoS,"c Missing commad126g2241iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Binding_11g4386 2004/07/02Ec2-1ޗWWW2.0WWW20ވWޒWWW>W WLWPWQW\WgWhWWW2003ުWWW21ޡWW22ެWTW25ްWW0W@WXWyWWW260WyW27ޱWYW3މWޓWޯWWWWWpWyWWWWWW]W|W}WWWWWWWWW3.08GW4WW3.1.1ޛWW30WWW31-34W3456ެWTW`W35WWWWYWZW[W]WfW~WW4optionsarespecifiedallbutoption3imposetrade-offbu]V4-1ޞWW4-2!W"W4-6W4.1WWW4.1.1ޥW*W4.1.5ޢWޤWW W4.1.5.1ޤWfW W5W4.1.7W4.1.9<W߸W4.2.1޺WqW4.4.1ިWެWJWTW`W4.4.2W5WGWJWSW4W5microsecondsseemstobeareasonableminimumrequirementSVRjchangevaluestobeconsistentwith2b/s/hzdownlinkand1eVchangedަWchangesZWߙWchannelZWqWޣWޥW߄W߉W3W WchannelsWcharacterizedZWchauvin9WchooseWchosen߂WclarificationYWW߉WclarifyާW߂W߈WclassesWclassifiedWWclosed߈WcnUWcodingߣWwWcom/publicNWcommencingZWcomment6W7W8W9W:W;W<W@WAWCWDWEWFWGWJWVWZW^W_WaWbWcWhWkWlWmWnWsWtW|WށWނWރWކWއWމWލWަWެWޯWޱWWWWWWWWWWWMWUWߏWߣWWW0WLWOWRWTWUW[W\W]WbWcWdWkWyW|W}WWWWWWWWWWWWWWWWWWWWWWWWWnbdegradation޽WWWWWWdegradeWWWWWWWWdegradesFWWdelayަW޽WWWWWW$W)WMWW>WAWFWHWNW^W_WcWWWWWdelayaWWdelaysWWWWWdeleteޛWޡWޥWުWެWޭWޮWWWWWWWWWWWWWWWWWW!W"W#W.WBWRWUWYW]WdWeWqWrWWWWWWWWWWWWW"W#W*W.W/W0W1WBWDWEWTWUWVW]W_WgW{WWWWWWWWWWWWWWWWWWWWW W WWWWWWWWetepotentiallyonly#VdeletesectionorremoverequirementsandpreserveasininfRV`21a4.1.1bDelete "The spectral efficiency at higher speeds than those shown should degrade gracefully." Alternatively define graceful degradation (but I don't think this is necessary or readily doable).c Not testable.d127g2242iKlererjYIt is acceptable to have "soft" requirments that are not directly testable but intuitive.mRejected 2004/07/02MarkedEDougFKnisely^Technical, Binding_12`5a4.1.2bDelete "The individual 802.20 technology proposals may optimize their MAC and PHY designs for specific bandwidth and Duplexing schemes."c9Not a requirement; immediately obvious and adds no value.d128g2243iKlererkThis is an important meta-requirement which has been the subject of extensive discussion and is not immediately obvious as there have been other proposals that require common MAC/PHY across duplexing schemes.mRejected 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_12`17a4.1.4g4388 2004/07/02)ybnecessaryWWWWneedWWWWWW`WWWWWneedmoreexplanation`VneededWW4WWWWWWneedsWWWneedsthepluralVnegotiateWWNW^WnegotiatedWWMWNWWnegotiationWWneigboringWWWLbtelematicsWWtelnetW_WtemplatesWNWtems<W߸WtermWWterminalWWWWW WWW<W߸WWWWW WWMWNW^WWWW$WcWWWWWWBWFWterminateWWterminology޵WWtermsWtests޺WtextޙWޚWޤWޥWިW޶W޺W޻WWWWHWIWOWPWfW~WWWWWWWW W*W/W5W=WAWJWthanަWާWWWWWWMWTWWWWW>W?WAWHWthatތWޖWޡWޢW޶W޺W޽WWWWWWWWWWWWWWWWWWWWWWWDWFWLWZWiWsW{WWWWWWWWWWWWWWWWWWWskmeta-requirementWmhz W*WmimoSWmimoisamultiantennatechnologythatcanbeusedhoweveriSVminimalEWminimumfWߎWmis-readingWmissingWWYWmitigate Wmitigateagainstisacceptableterminolgyseecomment141an VmobilefWhWpW W߽WWW WpWWWWmodeWWmodelWmodesWmodificationWmomentary߷WmoreLWUWXWW%WWWWWWWWW WW$WEWmoreaccurateVmoreaccuratelyexpressestheapplicationsthatshouldbesuVmoredetailthanrequiredforthisdocumentifwegodownthVmorespecificlanguageUVmost/WWWmostpreferredoptionofall/VmovingWmuchfWtWWWmulti-antennajWmultiantennaSWmultipleWWmultipliersGWmyރWW2W3WkW.WnativeKWnaturetWnear|WbdDelete "As an example, data rates gracefully degrade from pedestrian speeds to high speed mobility."cUNot an example as advertised. Not relevant to the requirement, thus adding no value.d129g2244iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Binding_13`5a4.1.5.1bDelete "Average user data rates in a loaded system shall be in excess of 512Kbps downlink and 128Kbps uplink. This shall be true for 90% of the cell coverage or greater."cAAverage user data rate is not defined and depends on the number of users. At best, it would be equal to the total system capacity divided by the number of users in the system; at worst, it is contradictory to the spectral efficiency requirements and would be unachievable for any representative number of users. If this statement was meant to convey a fairness requirements, it does just the opposite.d130g2245iKlerermAccepted 2004/07/02MarkedEDougFKniselyg4390 2004/07/023cawkWWawkwardW߽WWvWawkwardsentenceV߽VawkwardwordingvVb<W߸Wb/s/hz/cellWWb/s/hz/sectorWWWbackboneWWWbackendފWޔWWWrWzWWWWWWWWW!WbasedonthestandardsandproductstimeframethetechnologGVbasesW=WbasisWbcmcWbcmcmustsupportietfipbroadcastandmulticasttrafficefVbeރWޅWކWވWފWދWތWލWޏWސWޒWޔWޕWޖWޛWޞWާWުWޮW޳W޵W޷W޺W޼WWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW,W>W?W@WEWGWJWLWMWNWOWSWTWZW`WaWbWgWkWmWnWqWrWsWtWvWwWWScrequireވWޒWWWWWW@WLWPWQW\WgWhWWWWrequiredWWWrequirementރWބWލWގW޷W޹WWWWWWWW W WWWW$W'W7WDWGWLWSWVWWWXWZW[WbWcWgWkWlWtWuW߿WWWWWWWWWWWWWWW WWWWWWW4W@WFWaWtWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWW WespectތWޖWWWsW{WrespectivelyWGWrestWrestored޵WrestrictވWޒWWWrestrictiveWrestructureޤWresultޅWޏWWmWvWresultsGWretainTWrevisedWrewordZWrewritten@W^Technical, Binding_13`7a4.1.5.1bDelete Phase 1 columns. Delete Phase 2 headings. I.e., Phase 2 requirements as shown should be the requirements for 802.20. Delete Option 2.cAMultiple phases are a bad idea at this stage (early in requirements). The requirements should focus on the real market requirements driven by carrier needs and competitive realities (i.e., other competing technologies). If after evaluating all technology submissions it is necessary to adopt a phased approach, the requirements can be revised IFF there is a compelling reason that the requirements cannot be met. Phase 1 requirements are below the capabilities of published, implemented stanBHdards and are not nearly aggressive enough for the 802.20 market window.6d131g2246iKlererjSee my commentsk "an FDD" "or TDD" => "or a TDD"cClarifyd134g2249iKlerermAccepted 2004/07/02MarkedEDougFKnisely^Technical, Non-binding_14`5a4.1.6btDelete "Note: Depending on traffic mix within a cell the control capacity may not be the limiting system parameter."cjUnnecessary informative sentence creates more problems that it solves (e.g., what is "control capacity?").d135g2250iKlerer 2004/07/02 bAThe MAC layer should be able to control >100 simultaneous active sessions per sector. An active session is a time duration during which a user can receive and/or transmit data with potentially only minimal delaya short delay (i.e. in the absence of service level controlsconstraints such as, e.g. delays caused by the need to satisfy QoS commitments to other usersconstraints). In this state the user should have a radio bearer channel available with a delay of less than 25ms. Note that certBain applications will have to be given preferential treatment with respect to delay in order to satisfy QoS requirementswork, e.g. VoIP. y@A.  33  33  33  33  33  33#  33)  33*  33O  33m  33x  33N  33f  33j  33.cClarify wording.d132kwereWwgIW]WpWWWwhatWWWWWW WW"W4WvWWWWwhenvWwherehWwhetherW߷W=WwhichpW|WWWW WGW^WqWtWWWWwhilefWwhyiWuWWW#W3WwidewWwiderWwillvWW4WWWWwirelessiWrWuWހWWWW,kIt is important to realize that the theoretical capacity indicated by the number of sessions that can be controlled may not be achievable e.g., if users require high throughput relative to the channel capacity.mRejected 2004/07/02MarkedEDougFKnisely^Technical, Binding_14`9a4.1.7bAAdd: "The 802.20 system shall provide the MAC and PHY capabilities to satisfy link-level QoS requirements by resolving system resource demand conflicts between all mobile terminals while still satisfying the negotiated QoS commitments for each individual terminal. A given user may be using several applications with differing QoS requirements at the same time (e.g., web browing while also participating in a video conferencing activity with separate audio and video streams of information)g4395 2004/07/02g2252iKlererj Needs additional clarification. kAIt should be possible to have a single QoS class that applies to an aggregate flow that may actually be multiple applications. In other cases there are multiple streams each with its own QoS class. Tying QoS to a stream should work whether it is from one user or more. mAccepted-Modified 2004/07/02MarkedEDougFKnisely^Technical, Binding_14`19a4.1.7.1bAThe system shall support an arbitrary set variety of traffic classes that are defined by the system operator in terms of classic QoS attributes (e.g., data rate, latency, packet error rate, and delay variation). with different latency and packet error rates performance, in order to meet the end-user QoS requirements for the various applications, for example, as recommended by ITU [2]. The 802.20 standard shall support the ability to negotiate the traffic class associated with each packet g4396 2004/07/02 pbB. The 802.20 system shall provide the MAC and PHY capabilities to distinguish various packet flows from the same mobile terminal or user and provide differentiated QoS delivery to satisfy the QoS requirement for each packet flow. The 802.20 system shall provide the ability to negotiate the traffic flow templates that define the various packet flows within a user's IP traffic and to associate those packet flows with the QoS requirements for each flow (i.e., QoS parameters such as delay, C#bit rate, error rate, and jitter)."c?Need to distinguish intra-user vs. inter-user QoS requirements.d137eg2253iKlererjRequires further discussionkWe need to get to a realistic set of QoS classes that can realistcally be supported. Data rate from 1bps to system capacity does not seem to be something that can easily be supported with a realistic number of streams.mRejected 2004/07/02MarkedEDougFKnisely^Technical, Binding_14`21a4.1.7.1bADelete "Based on the classification of traffic in accordance with the QoS architecture as described in Section 4.4.1 [3,4,5,6], appropriate latency and packet error rate performance targets can be associated with each class. To support the Expedited Forwarding traffic class, the latency should be as low as possible while the corresponding packet error rate should be low enough to support real-time conversational audio/video applications, and near zero for error intolerant, delay sensitiveg4397 2004/07/02 bBflow, for each user, and for each mobile terminal. The 802.20 standard shall permit the set of traffic classes to be defined by the system operator in terms of classic QoS attributes (along with the range of values that : - data rate (1 bps to maximum data rate supported by the MAC/PHY), - latency (delivery delay) (10 ms to 10 seconds), - packet error rate (after all corrections provided by the MAC/PHY layers) (10E-8 to 10E-1), and - delay variation (jitter) (10 ms to 10 seconds). @A   33  33)  33*  332  33D  33  33   33\  33i  33  33cClarify traffic classes...d138 zbshortWWshouldޢW޶W޹W޺W޻W޽WWWWWWWWWWWW,W?W@WIWNWQWWWjWWWWWWWWWW WWW1WAWIW_WoWpWqWuWzWWWWWWWWWWWWWWWWWWshouldread Vshow`WWshownޙWWWWW1W3WWWsideWWWsidesWsightW}WW<WsignalWWWWWWsignalingW W W?WWWWWsignalling޹WWsignalsWWWSbvehicular޽WWWWWWverify޺WqWWversionDWWveryWWviaWW߽WWvideoWWWNWvisionޗWWWvoipWWWWvpnWWw$WFWweWWwebWWWNWwellޛW޺W޻W޽WWWWW W?WWWWWWqWuWWWWWWWWWwhatW+W/W5W8WWkWxWWW WwhenWWWWWWwhenever WWwhichރWލWWWWWWWWWWWIWkWtWߺW߽WWWWWWWWWWpWWWWWWWWWWwhile޻WWWLWWNW_WuWWwhoW@WWwholesaleW WW0W?WaWWWWWWqWwWyWWJWcclarifyawkdefinitionVVclarifynetworksecurityrequirementsVVclarifyrequirementswrtlinklayervsend-to-endqosandMVclarifytrafficclassesV^VclarifywordingVVclarify/changeWWWclarifyingރWލWWkWtWWWWWWWWWWWclarity޶WW<W?WjW߸WWWWWclassWWWWclassesީW޲WWW(WCWOWRWZW^W_WbWeWfWWWclear޴W޶WWWW%W/W1W3W4W5W8W;W߷W߾WWWWWGW`WiWxWWWWWWW WWclearerWclearlyWWclose4WWclosestOWfWcolumn޲WZW-kweneedtogettoarealisticsetofqosclassesthatcanreVweneedtomaintainsomesenseofrealityinnumberswethro VweshouldkeepmorespecifictextwethinkshallsupportvoiXVwell4WWwell-exploredNWg2254iKlererk#Prefer the solution in my commen tsmRejected 2004/07/02MarkedEDougFKnisely^ Editorial_16`8a4.1.8bAFuser capacity, cell sizes and reliability. As an example, e.g., MIMO."F@Af  33)  338  339  33?  33fcNot a sentence.d140g2255iKlerermAccepted 2004/07/02MarkedEDougFKnisely^ Editorial_16`19a4.1.11bANetwork security in MBWA systems shall protect the service provider from theft of service, shall ensure the user's privacy, and shall mitigate against denial of service attacks. Provision shall be made for authentication of both the base station, and the mobile terminal, and the end-user for to ensure privacy, and for data integrity consistent with the best current commercial practices. 802.20 security is expected to be a partial solution, complemented by end-to-end solutions at higher prog4399 2004/07/02 QbB data applications such as Telnet, interactive games. For the Best Effort traffic class, the packet error rate performance should comply with the requirement as stated in IEEE Std. 802 -2001 [7], quoted as follows: "The probability that a MAC Service Data Unit (MSDU) is not delivered correctly at an MSAP due to the operation of the Physical layer and the MAC protocol, SHALL be less than 8 x 10-8 per octet of MSDU length."]" Also, Delete options 2, 3, and 4.caText replaced with previous comment (proposing more extensible and flexible QoS traffic classes).d139 bnearW_Wz,beirp޺WqWWeither޵W޾W WWWWWelectronic WWemission޺WqWWemissions޺WqWWemploy޻WWuWWWemployed޹WWenableWWEWWWWMWWenablersWWencryption W WWWencryptionacrosstheairinterfacetoprotectuserdatatra VVbmtWWWWmultilWmulticombineswithotherwordsisusuallyattachedtothenlVmulti-vendor޺WqWWmulticastWWWWWDWLWWWWWWWWmultiplayerWWmultiplebWWmultiplyingޣWޥWW*WmustޘWEWaWWWWmutlipleHWmWmutuallyWWnear,[blevel޺W޽WWWqWWWWWlevels޻WuWWtionsWWlimited޺WWWEWWWqWlimitingWDWlimits޺WqWlineޙWޞWޟWާWިW޴W޵W޻W޾WWWWWWW WW0W?W@WXWhWWWWWWWWWWWW.W2W?WJWiWuWlineshouldread@Vline-of-sightEWWline4WW.W2WlinesޘWޡWWWWWWWlinkޥWWWWW*WlinkadaptationshallbeusedbytheaiforincreasingspectVlink-levelWWMWNWlink-levelend-to-endMWlistedޟWުWWllcWWloadWloadedW W!W0W3WloadingޥWWWGW*W.W2W3W4WloadsWlocal޺WqWlocationWWlogicalWWloss޽W)WcWWg2256iKlererjMerge with comments from othersmAccepted-Modified 2004/07/02MarkedEDougFKnisely^Technical, Binding_16`29a4.1.11.2bAA method that will provide message integrity across the air interface to protect user data traffic, as well as and signaling messages from unauthorized modification shall be providedwill be specified.@A  33b  33n  33o  33r  33  33  33  33c'Text should be a normative requirement.d143g2258iKlererjAgreed to in principle. kHarmonize with other commentsmAccepted-Modified 2004/07/02Marked EDougFKnisely^Technical, Binding_17`1a4.1.11.2bAEncryption across the air interface to protect user data traffic, as well as and signaling messages, from unauthorized disclosure shall be providedwill be incorporated.@4401 2004/07/02 bB/tocol layers such as EAP, TLS, SSL, IPSec, etc.@A  33[  33h  33z  33{  33  33  33  33  33  33  33  33  33  33  33  33   33!  33$  33%  33/  336  337  33  33 B3 33  33  33c&Clarify Network Security requirements.d141band/orޫW޴WWW߽WWSWiWWantenna޴W޺WHWIWiWmWpWqWWanyWWWapiWWappendޢWWappendtotheendofthesentencerequirementsofsection4.ޢVVappendix޵WWapplicableޚW޺WWWqWWWWWapplicationNWIWvWapplicationsWWWWWWW$WWWWWFWNW^W_WW}bcomplexityWWcompliant޺WWWWqWWWcomplyWW߻W_Wcompromised޹WWcomputerWWWconcernedWKWconditionsރWލWޥW޺WWWWWGWkWtWWWWWWW*W.W2W3W4WqWWWWWWWWnectedWconnectionsWWconsensusWconservationcWconsistentޢW޺WWWgW߻W߿WWWWconsistingWPWWWconsistsWW߽WWconstitutesW߽WcontextWWcontiguous:WcontributionުWCWDWHWIWPWWWWcontributions޳Wcontrol޷W޻WWWWWWW%W߽W߾WWW WcontrolandmonitoringVcontrolsconstraintsWWconversationalWcoreWcorrectionsWcorrectlyWcorrespondingWWWj(_‚(pvމޓ޺޻޽Ӄ -./0@JRpyߎߏߓߟߡߣߩߪ߫߳ߵqrstuvwxyz{|}߃‚)[fq|޼޾޿ƒÃ1234567ABSTߔߕߖߗߘߤ߬߭߮߯߰~ࠃ ۃ‚3bc‚4ުde`<߸߹ߺ ޜޞă 1AO}WW WprovisionableWWprovisioningWWWWprovisions޶WWWWpublic޺WqWWpurposeWW߽WWWncnotރWޅWކWވWދWލWޏWސWޒWޕWޢWޮW޴W޶W޸W޹WWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWW W"W$W%W)W-W/W1W2W3W4W5W8W9W:W;WFWNWRWTWVWYWZW\W]W^W`WaWcWdWeWkWmWnWqWtWvWwW|W߷W߻W߾WWWWWWWWWWWWWWWWWWWWWW WWWWWWWW!W#W$W%W'W(W+W,W.W/W0W1W2W6W7W9W:WFWGWIWLWMWPWQWVW\W`WcWgWhWiWjWtWwWxW{WWWWWWWWWWWV<8kseemWseemsuWselected.WselfWsense WWsentencevWހWW%WߙWWWGWYWoWWWseparateWseparatelyWseparatingWseptemberWserviceKWjW}WW߷WWWservicesNWWsessionEWsessionsWW%WsetWsetsWsettingeWshallXW WWWshouldKWXWYWfWhWpW|WWW%WߎW߽WWWWWWWWWW WW"W*W.W1W2W3W?WeWqWWWWshouldactuallyimpliesaredesiredbutnon-mandatoryfeaturVwWspecificallyAWWspecification߾WWspec