Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0H)@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 n@+G&H!.2.2@F4.1.2@&4.2.2@4.2.4@7 @* @g@* @ @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   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`NaObPcQvlEz\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 j   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߷@&@?@Ddi @ @@9P;;;;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,ACgEv@!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/135^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 sBl8#[ [#  al#6 cl6#  bl#& Bmv&#  @iv# sj{# Dkv# 8w#~,Cjv~# 0x#n  2yn# 2#^ 6{^# In# N qp N# 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 #8  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€    !!!!! " "  "  "  " # ####$$$$$%%%%45*3/31-*** 33 * +  ,  46, ,+0$0"0 1&/-.2,.//1)2+-*,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! QEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC 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'[@_jejEf@mujxi|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  33f*3 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 #G2456789:;<=>@ABCDEFGHIJKMNOPQRTUVWXYZ\]^_`abcefghijklmnpqrstuvxz{|}~ހށނރބޅކއވމފދތލގޏސޑޒޓޔޕޖޘޚޡޢޣޥަާީޮޯޱ޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃  !"#$%&'()*&'()********************************************9' @ s / @ @AAzHHddE(HH(d'`zA'dDE Pro 3.0 - 4.1F!"HPro 5.0 A ?G USENGLSH.MPR?GUSER.UPR:g^_`abcd€€€€€ €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. up" 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. sted_remedy>+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/136^Technical, Binding_20`7a4.5.3d8g4190iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/137^Technical, Binding_19`34a4.5.2d9g4191iNaguib, Sutivong, Tomicikj%Same as comment 273 - Reject comment mRejected-Duplicate 2004/07/138^Technical, Binding_20`15a4.5.4d10g4192iNaguib, Sutivong, Tomcikj#Same as comment 97 - Reject CommentmRejected-Duplicate 2004/07/139^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/13:^Technical, Binding_20`7a4.5.3d18g4194iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate>_: 2004/07/13;^Technical, Binding_19`34a4.5.2d19g4195iNaguib, Sutivong, Tomcikj$Same as comment 273 - Reject commentmRejected-Duplicate 2004/07/13<^Technical, Binding_20`15a4.5.4d20g4196iNaguib, Sutivong, Tomcikj#Same as comment 97 - Reject CommentmRejected-Duplicate 2004/07/13=^Technical, Non-binding_12`17a4.1.4d31g4197iNaguib, Sutivong, Tomcikj0Disagree, this is not implied in line 21/page 11mRejected 2004/07/13>^Technical, Binding_12`20a4.1.5d33g4198 2004/07/13`5a5d40g4199i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13@^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/13A^Technical, Binding_?`6a1.3d71g4201iNaguib, Sutivong, Tomcikk`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/13F^Technical, Binding_21`9a4.5.2d88g4206iNaguib, Sutivong, Tomickj$Same as comment 273 - Reject commentmRejected-Duplicate 2004/07/13G^Technical, Binding_21`17a4.5.3d89g4207iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/13H^Technical, Binding_21`25a4.5.4d90g4208iNaguib, Sutivong, Tomcikj dup of 157mRejected-Duplicate 2004/07/13I^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/134-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/13K^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/13L^ 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/13M^Technical, Non-binding_8`14a2.2d110g4213mAccepted 2004/07/13N^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/13O^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/13P^Technical, Binding_11`21a4.1.1d127g4216ted-Clarified 2004/07/02&74.2.2޻/0Rߣߪ߫uwxy{4.2.3fpvމޓ޼޽̃Ӄك123Spyߎߏߝߟߠߡ߬߭߮߳ߵ|}~߃ހށނރބޅކއވމފދތލގޏސޑޒޓޔޕޖޘޣޥާޮޯޱ޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃  !"#$%&'()*+,-./0123456789:Ã3Gߋ4Ã3 HmÃ30IpÃ3@JÃ3P[Ã3`KÃ3pLÃ3MH`Ã6@aÃ6PbÃ6`cÃ6dÃ6eÃ6f5Ã7g߿Ã7 h`jtext4W5WIW]W|W~WWޘWޡWޥWަWެWWW߷W߽WWWWWWWWWWW W W2WJWLWthanIWޮW WߪWthatIWOWQWާW޵W޷W޺WWLWߙWWWWFWNWvWWWWWQWSWTWUWZW]WeWgWiWqWrWuWxWyWzW{W|W~WWހWރWވWޘWޡWޣWޤWޥWަWީW޵W޷W޹W޺WWWWWWW WHWUW߀W߄W߈W߉WߎWߓWߔWߖWߘWߙWߝWߞWߟWߠWߡWߣWߧWߩW߯W߳WߴWߵW߹W߽WWWWWWWW WW2W3Wthe802.20aishallsupportmobilityupto250km/hxVtheaverageuserdataratedependsonnumberofusersandch߉VthefinaldispositionofthiswillneedtobedeterminedbyޤVdiannagWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWހWށWނWannateegVhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVހVށVނVjoanne߷W߸W߹WߺW߻W߼W߽W߾W߿WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWWWW W!W"W$W%W&WVPi&Naguib, Sutivong, Tomcik, YallapragadajEvaluation criteria could be used to define graceful degradation. Add a reference to Evaluation Criteria Document for further definition.mAccepted-Clarified 2004/07/13Q^Technical, Non-binding_12`17a4.1.4d129g4217iNaguib, Sutivong, TomcikjAfIf we delete that sentence, we need to make it clear somehow that the 802.20 system is not required to maintain the same data rate at different speeds. The fact that data rates degrade gracefully from ped speeds to high speeds need to be stressed out. Otherwise, it might be wrongly implied that system need to maintain same data rate across different speedsfmRejected 2004/07/13R^Technical, Non-binding_13`29a4.1.6d133g4218iNaguib, Sutivong, Tomcikj"use option 2 in joint contributionmAccepted-Modified 2004/07/13S^ Editorial_16`8a4.1.8d140g4219iNaguib, Sutivong, Tomcikj$Suggest removing the MIMO "example".qjbroadcast/multicastNWbrowingNWbrowsingWbsWbudgetgWbutLW[WW޺WWWMWWbw Wby4W5W9WIWZW]WdWeWޤWUWߘWߣWWNWwWc/iWc802.20-04-18r1~Wc802.20-04-55iWrWuWcalculatedWcallWWcangW޺WWߞWߴWWcapabilitiesNWcapturedNWcdmaZWcellgWߣW3WwWcellsizeisconstrainedasstatedinsection3.1iemacrogVcellsgWWWWWcellularWcenterWcertainFWcggW8jaddareferenceto3gpp2'sbcmcsstage1documenthereasfoNVaddclarificationtothesetermsYVadddefinitiontoappendixadefinitionoftermsandconceptVaddnewtextinline15seemac-relatedrequirementsinsectJVaddingߓWadditionalWߓWaddressWWaddressesWadoptfWpWvWyW{WWadoptoption2fVadoptoption3pVadoptoption3asisvVadoptproposalifpossibleibelievethatthefigure1ispaVadoptthesuggestedremedywithtypofixedindividual{VW8W:W;W<WCWDWEWFWGWLWNWZW[W^W_WaWbWcWeWgWvWassignmentZWat4W5WQW]WavailableIWavoidyWb/s/hzeWbandwidthsqWbaseZWbasedZWbcmcsNWbeIWPWQWeWgWbeen4W5WIW]WgWbefore@WZWbetterIWbetweenOWZWborderOWSkTMIMO is a multiantenna technology that can be used, however it is not the only one.mAccepted-Modified 2004/07/13T^Technical, Binding_20`8a4.5.3d155g4220iNaguib, Sutivong, Tomickje This is a terminal feature and has nothing to do with MAC/phy specs. Recommend to remove the sectionmAccepted-Modified 2004/07/13U^Technical, Binding_20a4.5.4d157g4221iNaguib, Sutivong, Tomcikj-change "all the hooks" to "specific features"kMore specific language.mAccepted-Modified 2004/07/13V^Technical, Binding_20a4.5.2d158g4222iNaguib, Sutivong, Tomcikj(Similar to comment 273 - Reject commentmRejected-Duplicate 2004/07/13W^Technical, Binding_7`8a2d164g4223iNaguib, Sutivong, Tomcikj< We need to standardize on a term. Should decide which one.mAccepted-Modified 2004/07/13X^Technical, Binding_8`10a2d167g4224iNaguib, Sutivong, Tomcikodified 2004/07/02jfurtherPWWOW߉Wfurthermore߄WfutherߞWߴWfutureߙWgyWzW߽WWWFWNWgamingWgeneralߙWWgetީW߄WWghzWgiven޵WFWNWgiventhatwehaveaneweditordanshouldlocatethedefint޵VgivesOWgoodޣWgood-putWgoodputyWgorup]WgracefulPWvWgracefullyQWzWgraphicalWgreater3WWgroup4W5WIWdW~WߘWguaranteeWguardޣWhandWhandoffZWWWWhandoffsZWWhappensޡWhardZWWWhas4W5WIWTWgWߘWߣWWhaveIW]WޣW޵WWߞWߴWwWheWhelpingWhereNWOWީWhighQWhigher߀WWWhooksUWhowޣWhoweverOW޲Whtml/specs/sNWhttpNW~WhzWigWyWީWެW޲W޳W޶W޹W޺W޽WWWUWWNWRjusedOWPWgWzWޣWީWߣWwWuser W߀W߉WWW3WNWvWzWWuser'sNWusers߄W߉WusingLW WNWv1.0NWvagueߧWvaluegWރWަWvaluesIWeW3WvariousqWߞWߴWNWvehicularWvergWverygWWvideoWNWvisibilityWvoipWWFWvotedWvoted4W5WIW]WߘWvpnWwasOW~WwayOW޺Wwcdma߀WweOWQWWWރWޣW޵W޶W޹WߓWߖWWweneedtodiscusswhatisparetialaboutthissolutioniam޶VeWyW{WWހWރWކWަWworkވWworking4W5WIW]WdWwould@WދWާWwouldliketoseethepreviousdefinitionandreviewbefore@VwrittenOWwronglyQWwwwNW~Wk1AWhWkW1-1AW1.3AWhW2fWhWlWvedIW]WarchitecturejWareYWiW߈jgThe proposed terms "closed coupled/ loosely coupled/ mutually coupled" are not defined. Please clarify.mAccepted-Clarified 2004/07/13߉^Technical, Binding_13`5a4.1.5d172g4529iNaguib, Sutivong, TomcikjThe average user data rate depends on number of users and channel conditions. As such, this requirement is incomplete and needs further clarification.mRejected 2004/07/13ߊ^Technical, Binding_14`5a4.1.6d177g4530iNaguib, Sutivong, TomcikjAgreed.mAccepted 2004/07/13ߋ^Technical, Binding_12`22a4.1.5.1d220g4531iNaguib, Sutivong, Tomcikj]Agreed. 802.20-based systems should be at least on par with other existing systems out there.mAccepted 2004/07/134-2ߌ^Technical, Binding_12`22a4.1.5.1d268g4532iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/13ߍ^Technical, Binding_12`22a4.1.5.1d278g4533iNaguib, Sutivong, TomcikmRejected-DuplicatejterminalTWNWWWterminalsWߩW WFWNWWterminatingZWterminolgyWtermsYW߈WWWtestableWBjspecsTWspectraleWgWߣWWwWspectrumLWWWspeedWspeedsQWspreadߎWߟWߠWߡW߳WߵWspreadsWsrdgWstageNWstandIWstandardqWWWWW߶WWWWWWWWWstandardizeWWstandardsހWWstartingWstatedgW߀W߄WstatesWWstationZWWWstationsW߽W WWWWstations/baseWstayރWstaysޡWstill޽WNWstoredWstreamީWstreamingWstreamsީWNWstrengthWstressOWstressedQWsub-layeringWsubjectީWsubmitted9WsubnetsWsubscriberߩWsubsectionsޤWsuchLW[WW߀W߉WFWNWWsufficientlyߘWsthathavebeendebatedandapproveIVtahtރWtddߔWtechnologyIWWtelematicswWWtemporaryZWtermLWWWޣWterminal^editorial?LS[dowyޗޙޛޜޝޞޟޠޤިުޫެޭް޲ރ߃ <=?@ABDEFHIJKPQZ_ghij|߶߸߹ߺ߼߽߿ăŃƃȃʃ˃̃̓΃уփ׃ރ  CJSTUXZjlmprvzృÃ̓ԃnon-binding=WJWMWOWQWRWޚWޡWޢWަWީWWWWWWWWWWWWWWVW\W]W^WaW߻WWWWWWWWWWW WWWW>WBWDWRWtWWWWWWWWWWWW W WWWWWWWWWށkSee reply to comment #6mRejected-Duplicate 2004/07/13ނ^Technical, Binding_14`16a4.1.7.1d281g4266iAnna TeejSee reply to comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/13nnel. 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ހWGJcWSystem must work under the various environments of a Macro/Micro/pico cellular system. d289g2261i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13Markedeads in a mobile environment can be much larger.mRejected 2004/07/13 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/13004/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ަWacrossQWWactiveZWaddNWPWYWE/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>V@VAVBVCVDVEVFVGVHVIVKVNVPVTVUVVVWVXVYVZV\V]V^V_V`VaVbVcVeVfVgVhViVjVkVlVmVnVpVqVrVsVtVuVvVxVzV{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޿VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V V V VVVVVVVVVVVVVVVVV1miAnna TeejPlease see Comment #220k$See reasons proposed for comment #3.mRejected-Duplicate 2004/07/13n^Technical, Binding_14`16a4.1.7.1d16g4246iAnna TeejSee reply to comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/13o^ Editorial_7`3a2d21g4247iAnna TeemAccepted 2004/07/132-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/13q^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/13߁^Technical, Binding_12`22a4.1.5.1d13g4521iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/13߂^Technical, Binding_14`2a4.1.6d37g4522iNaguib, Sutivong, Tomcikj"Why is 0.9 chosen? Please clarify.mRejected 2004/07/13߃^Technical, Binding_16`29a4.1.11.2d55g4523iNaguib, Sutivong, TomcikjAgreed.mAccepted 2004/07/13߄^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/13ߘ^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/13ߙ^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/13v^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/13w^ 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/13x4ߙksThe last sentence of the "suggested remedy" may not entirely describe the intent of the remainder of the paragraph.mAccepted-Modified 2004/07/13ߚ^Technical, Binding_19`4a4.4.1d68g4546i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߛ^Technical, Binding_19`4a4.4.1d69g4547i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߜ^Technical, Binding_19`4a4.4.1d70g4548i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߝ^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/13ߞ^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/13y^ 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/13z^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/13{^Technical, Binding_14`9a4.1.7d136g4259iAnna Teej8Adopt the suggested remedy with typo fixed: "individual"mAccepted 2004/07/13|^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/13}^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/13~^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/13#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/13ހ^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/13ށ^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/13ߴ^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/13ߵ^Technical, Binding_17`29a4.2.3d282g4573i&Naguib, Sutivong, Tomcik, Yallapragadaj>The requirement for minimum delay spread needs to be specifiedmRejected 2004/07/13߶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/13Markedބ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/13Markedޅ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/13Markedކ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/13Markedއ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/13Markedވ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/13MarkedމEToddFChauvin^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d7g2258iKlererjSee modification in my commentmAccepted-Modified 2004/07/13Markedފ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/13Markedދ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/13Markedތ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/13Markedލ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/13Markedގ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/13Markedޏ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/13Markedސ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/13Markedޑ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/13Markedޒ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/13MarkedޓEJohnFChen^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d17g2258iKlerermAccepted-Duplicate 2004/07/13Markedޔ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/13Markedޕ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/13Markedޖ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/13MarkedޗEDanFGalGMember^ Editorial_7`3a2bCAdd "Figure 2-1. The Vision of Integrated MBWA" under the figure.cMissing "Figure 2-1" captiond21g2342iKlerermAccepted 2004/07/13 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/13 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/13 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/13 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(8ޚ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/13 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/13 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/13 2004/06/01MarkedޞEDanFGalGMember^ Editorial_12`1a4.1.1>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޻WuWcompatibleWWcomplementedWWW83ޟ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/13 2004/06/01MarkedޠEDanFGalGMember^ Editorial_12`6a4.1.2b)change to: "duplexing schemes (FDD/TDD)"cline 6 is "Duplexing schemes"d30g2369iKlerermAccepted 2004/07/13 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.d31g237017a4.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_WjWpWW19ޡ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/13 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/13 2004/06/01MarkedޣEDanFGalGMember^Technical, Binding_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.d33g2372iKlerercthereforeޅ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/13 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/13 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/13 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/13 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>W@WAWBWCWDWEWFWGWHWIWKWNWPWTWUWVWWWXWYWZW\W]W^W_W`WaWbWcWeWfWgWhWiWjWkWlWmWnWpWqWrWsWtWuWvWxWzW{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޿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/13 2004/06/02MarkedޭEDanFGalGMember^ Editorial_14`31a4.1.7.1b delete "[7]"cOrphan reference [7]d43g2401iKlerermAccepted 2004/07/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 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/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_19`4a4.4.1b+Add after "(QOS)": "control and monitoring"c&vague "...(QoS)" - need more specifityd69g2431iKlerermAccepted 2004/07/13 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/13 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/13MarkedEHariFGantiGMember^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/13MarkedEHariFGantiGMember^Technical, Binding_Technical, Binding`15a4.1.7b>Support option 3 as far as latency requirements are concerned.d73iKlerermAccepted 2004/07/13MarkedEHariFGantiGMember^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/13MarkedEMarcFGoldburg^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/13MarkedEMarcFGoldburg^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/13MarkedEMarcFGoldburg^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/13MarkedEMarcFGoldburgg4344 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/13MarkedEMarcFGoldburg^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/13MarkedEMarcFGoldburg^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/13MarkedEMarcFGoldburg^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d81g2689iKlerermAccepted-Duplicate 2004/07/13MarkedEMarcFGoldburg^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/13MarkedEMarcFGoldburg^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/13 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/13 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/13 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 W6^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ߩWߪWj$See reply comment to initial commentmAccepted-Duplicate 2004/07/13 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/13 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/13 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/13MarkedEDougFKnisely^ Editorial_5`6a1.1cadd comma after "standard"d99g2213iKlerermAccepted 2004/07/13MarkedEDougFKnisely^ Editorial_5`7a1.1bg4359 2004/07/02\^technical4W5W6W7W8W9W:W;W<W=W>W@WAWBWCWDWEWFWGWHWIWJWKWMWNWOWPWQWRWTWUWVWWWXWYWZW\W]W^W_W`WaWbWcWeWfWgWhWiWjWkWlWmWnWpWqWrWsWtWuWvWxWzW{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޽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/13MarkedEDougFKnisely^Technical, Non-binding_5`12a1.2b$Change "detailed" to "functional". cJThis document does not specify detailed requirements (whatever those are).d101g2215iKlerermAccepted 2004/07/13MarkedEDougFKnisely^Technical, Non-binding_5`15a1.2b"change "layer" to "ISO/OSI layers"c6Grammar and clarify what "layer" system is being used.d102g2216iKlerermAccepted 2004/07/13MarkedEDougFKnisely^ Editorial_5`20a1.3bChange "bases" to "basis"c wrong wordd103g2217iKlerermAccepted 2004/07/13MarkedEDougFKnisely^ 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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^ 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/13MarkedEDougFKnisely^ Editorial_8`14a2.2bAdd period at end of sentence.c"Missing period at end of sentence.d108g2222iKlerermAccepted 2004/07/13MarkedEDougFKnisely^ Editorial_0`0a0cGlobal: Add page numbers!d109g2223iKlererjMine prints with page numbersmAccepted-Clarified 2004/07/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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}cA@ߍ^ߓ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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^Technical, Binding_8`14a2.2bg4373 2004/07/02g2228iKlererj$OK except "dells" should be "cells"mAccepted-Modified 2004/07/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^ 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/13MarkedEDougFKnisely^ Editorial_0`0a0b; globally change "i.e." to "i.e., x"c7Global: "i.e." should always be followed by a comma. d120g2234iKlerermAccepted 2004/07/13MarkedEDougcnon-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/13MarkedEDougFKnisely^Technical, Non-binding_9`16a3.1.1bDelete "partitioning"cwhat is a "partitioning model?"d122g2237iKlerermAccepted 2004/07/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^ 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/13MarkedEDougFKnisely^ Editorial_11`16a4.1.1bchange "QoS' to "QoS,"c Missing commad126g2241iKlerermAccepted 2004/07/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKniselyg4390 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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^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/13MarkedEDougFKnisely^ 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/13MarkedEDougFKnisely^ 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/13MarkedEDougFKnisely^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/13Marked 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߾WWspecifiedߎWspecifypW߶WspecifyingWspectralAWWspreadfWߎWspreadsfWsrdpWstandardAWhWހWWWstandard'srWstandardshWiWjWuW}W߶WWstatementW  bctIn a wireless system, protection against DoS is not always possible, but should be a design goal whenever practical.d146g2261iKlerermAccepted 2004/07/13Marked EDougFKnisely^Technical, Binding_17`2a4.1.11.2bASAdd after line 2: "The 802.20 standard shall permit the data traffic and signaling information on a per-user basis to be protected by: - message integrity and encryption, - protected by message integrity but not encryption, - protected by encryption but not message integrity, or - unprotected by either message integrity or encryption." SchNeed to clarify that system can operate with any combination of integrity, encryption, neither, or both.d147g2262iKlererjThis should only apply to data traffic. The treatment of signalling information is a network operator issue more than a user issue.mAccepted-Modified 2004/07/13Marked EDougFKnisely^ Editorial_17`17a4.2.1b"practice" => "practices"g4405 2004/07/02 T bA>  33R  33d  33>JG$cinawirelesssystemprotectionagainstdosisnotalwayspo VVinoption3line4missingdatarateޯVWVinoption4line27missingdatarateޱVYVinsection4.4.13456notclear`Vinthetableofoption4confusingcolumnheadingtrafficcl޲VZVcwithinފWޔWWWrWzWWWWWWWWW!WwithoutރWދWލWޕWWWWkWqWtWWWWWWWWWWWWWWWWWWWwordW W6W:WWWWrWWWWWW WWWwordchoice VrVworded޷W WwordingWWWWWvWWwordinggrammarclarityVVwordsBWFWWWR c Word choice.d148g2263iKlerermAccepted 2004/07/13MarkedEDougFKnisely^Technical, Binding_17`24a4.2.2bA Link adaptation shall be used by the AI for increasing spectral efficiency, data rate, and cell coverage reliability. The AI shall support adaptive bandwidth allocation, and adaptive power allocation. The system will have adaptive modulation and coding in both the uplink and the downlink @A>  33v  33  33>cTerms are not defined, nor are they requirements for a system that meets the 802.20 requirements. They may be techniques used by particular proposals, but the real requirements are already described elsewhere.d150g2265iKlerermAccepted 2004/07/13MarkedEDougFKnisely^Technical, Binding_19`4a4.4.1bg4407 2004/07/02ctermsarenotdefinednoraretheyrequirementsforasystemVwVtestableWWWWWWWWWWWtextޚWޢWަWޮW޵W޸WWWW W WWWHWIWPWUWfWhWiWjWWWWWWWWWW WWWWW5W>WVW_WmWnWpWtWWWWWWWWtextbeginingonlinewithhowtheisunncessaryVVtextisinconjunctionwithother802standardsitistoobrޚVVtextreplacedwithpreviouscommentproposingmoreextensiblV_VtextshouldbeanormativerequirementV VVVtextshouldbeanormativerequirementalsostrengthentoin VVtextsuchasinline38itmaybeusefultoconsiderisnotޮVVVthanWWGWJW]WWWWW4WWWWW g2268iKlererkTNeed to sort out higher layer issues (e.g., the use of RSVP)from lower layer issues.mRejected 2004/07/13MarkedEDougFKnisely^Technical, Binding_19`21a4.5bA1The system shallmust support both IPv4 and IPv6. 1@AR  33   33  33  33Rc'This should be a normative requirement.d154g2269iKlerermAccepted 2004/07/13MarkedEDougFKnisely^Technical, Binding_20`8a4.5.3bg4409 2004/07/02 bAThe 802.20 MAC layerprotocols shall provide mechanisms for the over-the-air delivery of user data that satisfies negotiated link-level qQuality of sService (QOS). The 802.20 protocol standards shall define the interfaces and procedures that facilitate the configuration, negotiation, and enforcement of QoS policies, which operators may choose to implement. Move the next 3 paragraphs to section 4.1.7: "The 802.20 air interface shall support the IETF Differentiated Services (DS) ArchitectureB to be compatible with other IP network standards including IP mobile standards. To this end, 802.20 shall support the standard DiffServ QoS model. Some of the forwarding behaviors that should be supported by 802.20 include: Expedited Forwarding (EF), Assured Forwarding (AF), and Best Effort (BE) DS per Hop Behaviors (PHBs) as defined by the RFC 2597 and RFC 2598. 802.20 shall also support configuration of the PHBs by a DS API that shall be based on a subset of the information model define bC2d in RFC 3289. Service and QoS Mapping The classes of service and QoS parameters of all services may be translated into a common set of parameters defined by 802.20. A QoS based IP network may employ the Resource Reservation Protocol (RSVP) to signal the allocation of resources along a routed IP path." @AB  33  33   33  33  33;  33  33  33  33  33  33  33   33  33g    33BcjMost of this text is not MAC-text. Some should be moved to 4.1.7. Some should be changed. Some deleted.d153O=bmovetable4-1captiontopage11line23ޞVVmovetonewsubsection4.1.6.2averageuserdataratesandc~V=VmpbsGW4WWmplsWWmsަW޻W޽WWWHWMW>W@WHW^WmWuWWWWWmsapW_WmsduW_W3Rbincorporated WWincrease@WvWzWincreasingWwWWW.W2W3Windication޹WWindividual޹WWWWWWWNWindividualsWindividulaMWindoor޽WW2WEW}WWW<Windor}W<Winformation޻WWWWWW WWWWWWWNWuWinformativeRWUW`WaWbWinitialWinitialtextforthisnewsub-sectionVinsertޛWޝWީWޯWޱW޺WWWiWWWWW.WRWWWYWqWinsertaspacecharacterafterhzޝVVinsertbitrateaftertrafficclasseswithdifferentީVRVinsertdatarateafterwithdifferentޯVޱVWVYVinsertthefollowingsentenceatthispointitisfurtherasiVVinsertthefollowingtextinline1beforefigure2VVinstantWWinstead'WaWintegralIWpW/GbdisableWWdisclosure W WWWdiscription3WdiscussWdiscussthesectionwithatechnicalperspectiveanddevelopVdisruption޽WWWdistinctionބWގWWlWuWWWWWWWWWW WdistinguishWNWdistinguishingWdistortion޺WqWWdiversityIWpWdividedWWdl!WGW"W4WWdl/ulޥW*WdoableWWWdocWdocumentWWjW߽W߾WWWdoesZWWdon'tWWWdonebWWdos WWdownlinkބWގWޤWޥWWWW W@WlWuW~WWWWWWW W!W*W0W3W=WvWwWzWWWWW WWWefficiencyރWލWޢWޣWޥWWWWWWLWkWtWefficientWDWLWefficientlyWeffortWWv!!bpart޶W޺WWIWWWpWqWWpartialWWparticipatingWNWparticularWWWWWWpartitioningWWpartnersWpartsWWpathWWpeakޤWޥWWWWGW}WW W*W.W2W3W4W<WWpedestrianޥW޽WWWFWWWW*WWWWWperޣWWWWWWWW_WWper-user WWperform޽WWWbshallmustWWDcthoseWWWWthree޽WAWWWWWthreeoptionsarespecifiedipreferoption3withthelastVthroughްWWWXWWthroughout<W߸Wthroughouthtedocumentweusedifferntcaptializationsfor<V߸VWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW'W,W.W1W7W<Wtosupporttherequirementhasnoteeth'VtodayވWޒWWWtolerable޳WtooޚWWtotalWtrafficވWދWޒWޕWީW޲W޳WWWWWWWWW(WtransportވWޒWWWtrueWturnވWޒWWWWtwoއWޑWW,Wtypes޳WtypoWtypobasesVudpވWޒWWWun-meetableWunachievableWg2270iKlererkNAgree that this is not a MAC/PHY issue and should, therefore, not be included.mRejected 2004/07/13MarkedEMasaakiFYuzaGMember^Technical, Binding_13`2a4.1.5.1bA#1:Line 2-3 is modified to "These peak data rate targets are independent of channel conditions, traffic and loading." #2:Incert following line to after Line4 "If system has some sub channels for users, user data rate is defined sum of user data rates in one sub channel" cA"Peak Per User Data Rates" is a very important parameter for define the system performance for TDMA and CDMA architecture. It is not define system performance for FDMA system, it's define only performance for one user. It is able to all sub channels provides to one user, for make appearant large peak user data rate. But, What is it meaning for FDMA system? It is not neccessary define a performance of very few situation. d156g2211iKlererkSee reply on initial comment 2004/07/02 bACPE software upgrade "push" - an operator should have the ability to "push" a software upgrade to CPE that are currently connected to the network. The packets that make up the software image should be given a very high priority and should be coded heavily such that they have a very high chance of arriving error free at the CPE. The CPE should be capable of holding 2 software loads (the existing one and a new one) such that an operator can ensure that the "new" software load has arrived sB#afely at the CPE before deciding to switch from the "old" software load to the "new" software load. The 802.20 AI shall not preclude over-the-air download of firmware and software updates for the mobile terminal. The 802.20 AI shall support network-based bootstrap procedures, e.g., bootp.@A*  33S  33*cyNot sure how this is a MAC/PHY requirements. Software upgrades should be an upper layer issue. Suggest simpler wording.d155 bshallmust{RqbpreferentialW$WWFWpreferredWWprescribedWWWpresentWWpreservation[WWpreserve޻WRWuW{WWprevent WWpriorityWWprivacy޸W޹WW>WW W W WWprobabilityWMWHW_WproceduresWWWWprocessingWWWproofWWWproperްWXWWproposalsWWproposedޙW޴W޶W޷W޺W޽WCWDWGWHWIWWWW4WeWiWmWpWqWWWWWWproposedtextforsection4.2.1.1general޺Vprotect޹WWW Wprotected Wprotection޹W WprotocolޛW޶WWWWWbW߽WWprotocolsWWWWprovide޹WWWWWWWW W WWW9WIWPWQWcW|WWWWWWWWV"cnotsurehowthisisamac/phyrequirementssoftwareupgradeVVnottestableVVVnottestablenotarequirementVVnote$WFWWnowވWޒWWWLWPWQW\WgWhWWWnrt޳W[WnumberެWWWLWfWWW0W5WAWTWtWWWnumbersެWWW߹WWTWWoa&maWWoa&mrequirementsareequipmentrequirementsnotairinterfaaVVobjectivesWobviousWWWWWWWWWWWWWWWWWWWWWW WWWWW W,W4W>WAWCWEWGWKWLWOWUWYW_W`WaWcWfWgWkWlWmWnWoWqWrWtWuWvWwWxWzWW߿WWWWWWWWWWWWWWWWWWWGWAcon@Uonlytheparandthe5-criteriadocumentsshouldbereferenc@Aoption1page18line4thetbrneedstobedefinedorelse@options@%orphan@otheripnetworkstandardsnotcomplete@uoutdoor-indoor@overall@partitioning@peakperuserdataratesisaveryimportantparameterford@perceived@ppp@practice@probably@provides@pr@reader@*sentenceshouldnotbenormativenottestableataminimum@;shall/should@usimple@software@Bspecifity@Hsports@statistics@.system@table-like@3termsarenotdefinednoraretheyrequirementsforasystem@that@thatthefollowingtableispresentedasthebases@thejthe802.20standardshallsupportthissentenceisnotclear@utheconceptofbandwidthmustbeclarifiedgiventhatweare@ thescopeofthisrequirementneedstoberefinedasworded@9kissuesWitSWhWpWrWހWWWWW%WWWWWWWWWWWWWW"W*W.W3W=WpWvWWWWitdoesn'tmatterobviouslyapartitioningmodeldividesorVitisambiguouswhatistherequiredframeerrorrategivenvVitisbettertospecifythesystempeakdataratesinsteado3VitisimportanttorealizethatthetheoreticalcapacityindVitnotclearhowadesignscalestowiderchannelbandwidthsVitshouldbepossibletohaveasingleqosclassthatapplieVit'sW!WWit'snotclearwhythecurrentrequirementisinadeaquateanVitshWWWW"W4WWitsprobablyimpossibletoprotectagainstunforeseeablefutVitself>Wjargon[Wjustification=WeWWkeepXWWkeepingAWkept|WlanguageUWlarge*W3W=WtWlimitingWWmRejected-Duplicate 2004/07/13 2004/05/28Marked4-3EVincentFPark^Technical, Binding_20a4.5.4bANThe AI shall provide all the hooks to enable the provisioning and collection of metrics, so that the network operator can effectively control, monitor, and tune the performance of the 802.20 air interface. Provisionable paramenters, performance metrics, and other OA&M values shall be made avialable through a standards compliant MIB.Nc\The parameters and metrics cannot be properly defined before the air interface is finalized.d157g2767iKlerermAccepted 2004/07/13MarkedEVincentFPark^Technical, Binding_20a4.5.2b:Option 1: Preferred. The 802.1Q section should be dropped.cg4412 2004/07/022B  memberCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijkt|߿ƃǃ̃̓փރ߃  *.245>?@HIJKLRSTUVWXYZ[efimnpqtu{~ࠃࡃࢃࣃः੃ઃૃୃ௃ఃృಃೃഃฃໃÃăʃ̓΃у҃ӃԃՃփ׃كcpeakperuserdataratesisaveryimportantparameterfordV2VpedanticWWperWW.W2WlWperusualstylemultiantennashouldbecomemultianntenalVW2Wperhaps޶WWperiodWWperspectiveXWphaseWW.W/W1WphasedW1WphasesއWޑWWWoWxW&W)W-W1W8W;WphraseާWZW?WphyCWVWXWZWeWphy/mac޴W+WiWkWphysicalW5Wplace<WVW߸WplacedޞW޺WWplacesXWpleaseCWeWpolicies-WWpolicy-basedMWportableWportion޳W[WpossibleވWޒWWW WWWLWPWQW\WgWhWpotentiallyަW#W>WEWpotentiallyconfusingtextަV>Vpotentiallyonlyredundant#VEVpower޻WcWpppދWޕWWWqWpractical WWchauvinރބޅކއވމފދތ$%&P|ൃྃǃ׃chenލގޏސޑޒޓޔޕޖ'()Q}ඃ࿃ȃكڃۃ܃݃ރ߃galޗޘޙޚޛޜޝޞޟޠޡޢޣޤޥަާިީުޫެޭޮޯްޱ޲޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃ̓  *>?JRSTUVWXYZ[iqu~ࡃࢃࣃःԃ ߹ߺ߻߼߽ƒÃȃ΃σЃу׃؃كڃۃ܃݃ 01BCDMN, bshallWWW W$W0W1W2W3W>WBWDWFWGWHWIWLWPWQWSWTWcWgWhWsW{W}W~W߻W߿WWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWWW!W0W3W4W<W=WBWFWMWNW^W_WiWmWpWqWvWwWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWnbcapabilitiesWW WWMWNWWWcapableWWcapacityWWW%WWDWGWjW WcaptionޛWޞWޟWWWWcaptionsޛWWcaseGW4WWcausedWWcellWWWW0W3WDWjWwWW WcellsWWEWXW|WWWWWWWcellularEW|WWWcertainW$WWFW)=g2768iKlerermAccepted 2004/07/13MarkedEEshwarF Pittampalli^ Editorial_0`0a0b{Change from "802.20 ...." to: "System Requirements for IEEE Standard 802.20 for Mobile Broadband Wireless Access Systems"cIncorrect titled159g2324iKlerermAccepted 2004/07/13Markedlli^ Editorial_1`13a1.2b5Delete lines 13-16 (Text beginning with 'How the...")c6Text begining on line with "How the..." is unncessary.d161g2326iKlererk%I can live with or without that text.mAccepted 2004/07/02MarkedEEshwarF Pittampalli^Technical, Binding_1`20a1.3breplace with "basis"c Typo "bases"d162g2327iKlerermAccepted 2004/07/02MarkedEEshwarF Pittampalli^Technical, Binding_7`8a2bAReplace "Mobile Terminal (MT)," "user device," "mobile device," "wireless MT," "mobile wide-area stations," and "CPE" with "Mobile Station"@A> 33|  33 33>> &cA Requirements with regard to 802.1Q are detailed in the 802 P&P "5 criteria", the 802.20 "5 criteria", and the 802.20 PAR. If needed the relevant sections of those documents should simply be referenced, to avoid introduction of any ambiguity regarding the requirement. d158E~c5-criteriaުWWW6ޠWWGWWW4WWW6-32GW4WW7ޭWiWWUW802ޚWޛWWWWW802-2001CWeW802.1ދWޕWWWqWWWWWWWWW802.16ދWޕWWWqWWWWWWWWW802.16.3CWeW802.1qދWޕWWWWqWWWWWWWWWW802.20ވWދWޒWޕWWWWWWWWWWWW4W8WCWEWLWPWQW]WaWhWjWqWWWWWWWWWWW1WLWPWQW\WeWgWhWwWWWWWWWWWWWWWWWWWWW WWSWVWWWYWZW[W`WfWhWkWlWmWqWrWtWuWvWzWWs  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~߀߁߂߃߄߅߆߇߈߉ߊߋߌߍߎߏߐߑߒߓߔߕߖߗߘߙߚߛߜߝߞߟߠߡߢߣߤߥߦߧߨߩߪ߲߫߬߭߮߯߰߱߳ߴߵ߶߷߸߹ߺ߻߼߽߾߿ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ )" bc3Multiple names for "MT" A generic global comment.d164g2329iKlererj%Use common terminolgy across documentk?i do not care what term we ue as long as we use it consistentlymAccepted-Modified 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_7`8a2bAReplace with "The 802.20 AI shall support various vehicular mobility classes up to 250 km/h in a MAN environment and target spectral efficiencies, sustained data rates and number of active users that are significantly higher than achieved by the existing mobile systems."c:The sentence beginning with "The 802.20...)" is not clear.d165g2330iKlerermAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_7`12a2b/Please clarify what exactly is the requirement.cLBest in class "overall network complexity" -- the requirement is not clear.d166g2331iKlererk&There is no explanation of the problemmRejected 2004/07/13MarkedEEshwarg4419'btheރ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޽WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWW$W+W,W0W1W2W3W9W=W>W?W@WAWBWDWEWFWGWHWIWLWNWOWPWQWTWUWWWXWZW[W`WbWfWgWhWiWjWkWlWsWtWuW{W}W߻W߽W߾W߿WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW"$ 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_8`19a3.1bNReplace it with "support non-line of sight outdoor and indoor coverage areas."c*"support non-line of sight...." ambiguousd168g2333iKlerermAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_11`21a4.1.1bReplace "should" with "may"c6"should" implies a required feature which is not true.d169g2334iKlererk$I believe it is a "required" featuremRejected 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_12`11a4.1.3boReplace it with "The AI shall support closely coupled/loosely coupled / mutually decoupled FDD and TDD modes."c0"The AI shall support..... (TDD)." is ambiguous.d170g2335iKlererk,I prefer the comment of Dan Gal to fix this.mRejected 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_12`17a4.1.4g4423 2004/07/02!F Pittampalli^Technical, Binding_8`10a2b%Replace it with "enablers to support"c,"air interface support to enable" not clear d167g2332iKlerermAccepted maccepted-clarifiedNPYx~ވި޺ ߈accepted-duplicateގޏސޑޒޓޔޖ΃σЃу҃Ӄԃكڃۃ܃mnopruvwxyz'()+,-6789:;Q\ghඃසฃ຃༃གྷ࿃ăŃƃȃɃʃ΃σЃك 'FHKMUqߖߙߝ߶߽Ńу؃ rejected5=@AIQX]fghijruv|}ހރލޣޥާީެ޳޷޽ƒÃăŃ׃ !"$%()*12367:;GOf~߀߂߄߉ߎߔߘߞߟߠߡ߳ߴߵ߷߹߾߿ẵЃӃԃփكڃۃ܃݃ރ߃ !"!(bdreplace it with "Data rates may gracefully degrade from pedestrian speeds to higher speed mobility."c*"As an example,...mobility." is ambiguous.d171g2336iKlererkPrefer other proposed solutionsm Superceded 2004/07/13Marked EEshwarF Pittampalli^Technical, Binding_13`5a4.1.5bpReplace it with "Average user data in a loaded system shall be in excess of 2 Mbps downlink and 1 Mbps uplink."cW"Average used data..................greater" is not in excess of existing technologies.d172g2337iKlererkWe need to maintain some sense of reality in numbers we throw about; certainly these numbers make no sense for a mobile system with a 1.25 MHz channel. mRejected 2004/07/13Marked!EEshwarF Pittampalli^Technical, Binding_13`7a4.1.5bReplace it with Phase 1 numbers changed to >3.0 Mbps (for 1.25 MHz DL), >1.5 Mbps(for 1.25 MHz UL),, >12 Mbps(for 5 MHz DL),, >6 Mbps (for 5 MHz UL) respectivey and delete Phase 2 columnsg4425 2004/07/02| bfromW?WFWPWfW߶WWWWWWWWWWWWW W5WNWtWWWWWW;B^technicalbinding V!V"V#V$V%V&V'V(V)V*V+V,V-V.V/V0V1V2V3V4V5V6V7V8V9V:V;VCVGVLVMVNVOVRVSVTVUVWVXVYV[V`VbVcVdVeVfVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{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߫V߬V߭V߮V߯V߰V߱V߲V߳VߴVߵV߷V߾VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V VVVVVVVVVV_7Cbexchange޻WuWWexcludingWWexistingWWWWexpectedWAWWWexpeditedWW(W_WbWWexperience޽WWWexplain/WxWexplainwhatisadaptivebandwidthallocation/VxVexplanation`WextensibleBWWޙWޛWޜWWWfiguresޛWfileWfirmwareWflexibleWWfloor޻WflowWWflowsWfollow޺WfollowingޣW޻WWWWfollowsޟWWWWfollwingWfootnoteޫWforޛWޥWާW޹W޺W޻WWWWWWWWWWWWWWWWWWWWWWWWW!W)Wforthepurposeofthisdocumentan802.20systemconstituteVforwardingWW(WfreeWfrequency޺WWfromޣWޤW޹W޽WWWWWWW WWW$.!cTable 4-2 ambiguous.d173g2338iKlererjSee my commentskI prefer option 2mRejected 2004/07/13Marked4-2"EEshwarF Pittampalli^Technical, Binding_13`11a4.1.5bDelete Option 2cOption 2 is not desired.d174g2339iKlererkI prefer option 2 to option 1mRejected 2004/07/13Marked#EEshwarF Pittampalli^Technical, Binding_13`22a4.1.6bDelete "potentially only"c"potentially only" -- redundantd175g2340iKlerermAccepted 2004/07/13Marked$EEshwarF Pittampalli^Technical, Binding_13`26a4.1.6bRepalce with "Certain applications shall be given preferential treatment w.r.t. delay in order to work and this requirement shall be met even if the sessions are all on different terminals."cVSentences "Note that...VOIP." and "This requirement....terminals" are not cooperative.d176g2341iKlererkI do not understand the commentmRejected 2004/07/13Marked%EEshwarF Pittampallig4429 2004/07/02:+ ^binding!W"W#W$W%W&W'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;WCWGWLWMWNWOWRWSWTWUWWWXWYW[W`WbWcWdWeWfWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{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߯W߰W߱W߲W߳WߴWߵW߷W߾WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWWWbreplaceitwithphase1numberschangedto3.0mbpsfor1.25!V"Vreplaceitwithreasonableandnon-discriminatoryrand-VVreplaceitwithsatisfybothintraandinteruserqos&VOVreplaceitwithsupportnon-lineofsightoutdoorandindoorVVreplaceitwiththeaishallsupportcloselycoupled/looselyVVreplaceitwithwireless6VV VreplacemobileterminalmtuserdevicemobiledevicewirelesVVs~breplaceitwithphase1numberschangedto3.0mbpsfor1.25@*replacerequirementwiththeairinterfaceshallsupportthe@replacewithbasis@5replacewiththesystemshallsupportbothindoorandoutdoo@9requirementswork@mrewordasfollowstheairinterfacedesignshallscaletowi@mscaling@`seconds@sector@sentence|separate@set@,shallshallmust@ short@significantly@zsoft@specify2bits/sec/hzasthespectralefficiencyandallowt@1spectral@standard@^stations@^suitable@system@t@techniques@Ltelematics@terminals@terminate@thatthe@ 'PbsetWW^WWWWseveralWNWshallތWޖWޘWޟWޣW޴W޷W޹W޺W޽WWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWkunderstand$WundulyWunforeseeableWunlicensedWunlikely*WunnecessarilyWunnecessary߿unspecified5Wunsupportable!Wup4WuplinkWuplinkanddownlinkcharacteristicandrequirementsarediffVupperWuseWWWpWWusedSWusefulWWWWuserhWvWW*W3W=WEWuserswWWEWusesWusing1W4WvaguenessNWvaluesfWvariationsjW}WvariousYWWWWvariouslevelsofcouplingarenotdefinedinthisdocumentYVvehiclewWvehicularwWversavWversionsWviaWvicevWvoiceKWXWvoip߽WwalksvWwantpWwasWW WGWeWWway&WweAWXWWW W6WWWWWWW?WeWWwecannotestablishrequirementsontheimplementationsofVwedomeancellular6V(1%^Technical, Binding_14`5a4.1.6bDefine "control capacity"c!"control capacity" is not clear. d177g2342iKlererkThe first sentence speaks about being able to "control"more than 100 s imultaneous active sessions"; it should be obvious that control capacity refers back to that.mRejected 2004/07/13Marked&EEshwarF Pittampalli^Technical, Binding_14`13a4.1.7b;Replace it with "satisfy both intra and inter user QoS..."c "satisfy user QoS..." incompleted178g2343iKlererkI can go either waymAccepted 2004/07/13Marked'EEshwarF Pittampalli^Technical, Binding_14`25a4.1.7.1b>Quantitative requirement is required (instead of qualitative).c0"To support....." the requirement has no teeth.d180g2345iKlererkI prefer option 3mAccepted-Modified 2004/07/13Marked(EEshwarF Pittampalli^Technical, Binding_14`37a4.1.7.1b6Include Expedited Forwarding traffic class descriptiong4432 2004/07/02 /iklerer%&'()*+,-.012345678:;<=>?ABDEFGHIJKMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~kotechaWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWWWWW W!WVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVgVbPkactualfWactuallyWWW>Wadaptation|WadaptivewWadditionWadditionalwWadditionally4WqWtWWaddressWaddressedWqWaddressingWtburstyandnon-burstytrafficneedstobesupportVagreethatthisisnotamac/phyissueandshouldthereforeVagreewithcommentVagreewithcommenterVagreewithrationalVagreewiththecommentsVagreedKWNWagreedthatthisparagraphshouldbeinformativesuggestremKVairWWWWWWairbagwWallpWWWallowjW}WallowedWalreadywWހWWWalreadycoveredintheparanywayValso߽WWanrWvWwWހWWWWWWWandIWLW]WiWjWpWrWuWvWwW}WWW߷W߽W߾WWWWWWWWWWWWWWWWWW.4(c{Option 2 provides description for only Best Effort data leaving Expedited Forwarding and Assured Forwarding traffic classesd181g2346iKlererkI prefer option 3mRejected 2004/07/13Marked)EEshwarF Pittampalli^Technical, Binding_15`11a4.1.7.1b1Define requirements for delay and data rate loss.ch"low delay, low data loss rate,..." does not provide quantitative measures for delay and data loss rate.d182g2347iKlererkConsistent with RFCmRejected 2004/07/13Marked*EEshwarF Pittampalli^Technical, Binding_15`19a4.1.7.1bDefine "moderate"c8"..moderate delay, moderate data loss rate,.." ambiguousd183g2348iKlererkSee previous reply commentmRejected 2004/07/13Marked+EEshwarF Pittampalli^Technical, Binding_16`6a4.1.8b2Define what is "Interconnectivity at the PHY/MAC?"c."Interconnectivity at the PHY/MAC.." ambiguousd184g2349iKlererm Superceded 2004/07/13Marked,EEshwarg4436 2004/07/02yuza2memberރލޗޘޙޚޛޜޝޞޟޠޡޢޣޤޥަާިީުޫެޭޮޯްޱ޲޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃɃʃ˃̃׃؃كڃۃXblow޻WW_WuWWmWmacWWWWWWWW WW߽WWWWWNW_WWWWWWWmacro/micro/pico|WWmacrocellsPWWmadeWWW WmaintenanceWmakeWDWLWUW`WaWbWiWWWWWmaketable4-1consistentwiththeparandspecifyadownlinVmakethesectioninformativetoshowintentorremoveit`VmanWWmanagementWWmandatoryWmanner޺WZWmappingWmasks޺WmaximumޥW޺WW7WFWW*W^Wmay޾WWWWWWWWWWW,WIWWWWWWWDWNWmbps W!WGW~W!W"W4W=WmbsޥW*WmbwaޗWޙWW߾WWWWmeans>W WMWmeasureWmeasured5WmeasurementWmeasurementsW16,F Pittampalli^Technical, Binding_16`10a4.1.9b$Replace the word "should" with "may"caThe two parts of the sentence - starting at line 10 - may appear to be contradicting each other.d185g2350iKlererm Superceded 2004/07/13Marked-EEshwarF Pittampalli^Technical, Binding_17`10a4.1.11.5bWZWgW߻W߿WW WW=C7 2004/07/13Marked8EEshwarF Pittampalli^Technical, Binding_19`4a4.4.1b?Specify what mechanisms are being referred to in this sentence.c#"802.20...mechanisms...)" not cleard200g2365iKlererm Superceded 2004/07/13Marked9EEshwarF Pittampalli^Technical, Binding_19`9a4.4.1bMProvide the references to other IP network standards and IP mobile standards.c1"...other IP network standards...." not completed201g2366m Superceded 2004/07/13Marked:EEshwarF Pittampalli^Technical, Binding_19`23a4.5.1bReplace it with "contiguous"c""continuous" is not the right wordd203g2368iKlererk>"contiguous" is definitley not the right word in this context.mRejected 2004/07/13Marked;EEshwarF Pittampalli^Technical, Binding_19`26a4.5.1b(Define "soft handoff" and "hard handoff"c$"soft or hard handoffs.." not clear d204g2369iKlererkNo proposal providedmRejected 2004/07/13Marked<07/028<07EEshwarF Pittampalli^Technical, Binding_18`35a4.3b"Specify maximum channel bandwidth.ce"readily extensible to wider channels..." -- this is an open-ended requirement for channel bandwidth.d199g2364iKlererk?The max channel bandwidth would be equal to the max block size.mRejecteddÃ1PZ;߷Ã1`3Ã1p<߸Ã1Ã1=Ã1lÃ2> Ã2 Ã20?Ã2@@zÃ2PAÃ2`BÃ2pCeÃ2DÃ2EÃ2FÃ3Gߋ4Ã3 HmÃ30IpÃ3@JÃ3P[Ã3`KÃ3pLÃ3MHÃ3NIÃ3OfÃ4nÃ4 PÃ40QÃ4@tÃ4PR{Ã4`SÃ4pÃ4Ã4Ã4TÃ5ހU੃Ã5 Ã50VૃÃ5@WୃÃ5PXÃ5`YఃÃ5pZÃ5[Ã5\ೃÃ5]ഃÃ6^Ã6 _ÃÃ60\`Ã6@aÃ6PbÃ6`cÃ6pӃÃ70iÃ7@jÃ7PÃ7`Ã7p]kÃ7lÃ7mߌ6Ã7n7Ã8o8Ã8 ށgÃ80p߳Ã8@qÃ8P^rÃ8`_sÃ8p`tÃ8uÃ8vߍ9Ã8w:Ã9x;Ã9 ނߴhÃ90yߵcbmediumW߽W߾Wmeet޺WW^WqWWmentionedTWWmessage޸W޹WW W WWWWmessage/data޹WWmessages޹WW W?WWWWWmessaging޻WWWuWWmetW$WBWFW WmethodWWmethods޷W޹WWmetricsތWޖWWWW5WsW{WWWWWWWWWWWmhzޥWާW!WGW"W*W4W?WWWWminimize޻Wminimum޺W޻WWWLWWWminorSWmitigateW>WW WmixWmixesNWmmobileW߽Wmobile޴W޺W޻W޽WWWWWWWWWWW WWWWWW9W<WEWIWPW_WhWjW|W߶W߸W߽W߾WWWWWWWWWWWWWWWW WWWkcontrol%W߾WWcontrolledWcorrectWcorrectionߺWWWWpWcostspWcouldKWWWWWWWWdatahWWWdebatedIW]WdefinedYWpWdefiningWWdefinitionsWdefinitionsshouldbeconsistentwithindustryuseandapproVdefinitley:WdelayfWߎWdenisWdepending߷WdeployWdeployedwWWdescribeߙWdesignWdetailWWdetailedWWWWdevelopedWdevicesWdictionaryWdisagreeWdisagreethatthecurrentphase2requirementsarerealisticVdiscussionWdisruption߷WdoW$W6WdocumentNWYW߷W߸W߾WWWWWWWWWdoesrWW߶WdougWdownWdraftrWdroppedvWduplexingWduplicateqWehWwWWW߽WWeachWeasilyWeditiorilaWebhardware WWharmonize޳W[Wharmonizewiththeappropriate802.20contributionsonthis޳V[VhasWWW.W2WWhaveWWWWWAWwWWWWWheadingޤW޸W޺W}W W W<WqWWWheadingsW1WheavilyWWheight޺WqWWhelping޻WuWWhereTWWhighWWFWWWWWhigh-speedWWWWhigher޴WWWWWWWWWiWWhighre޶WWholdingWWhomeWWhooksWWhopWWhowWWWWhoweverWWhzޝWWWWWiWWWWWWߺWWWW1WNWWidealGW4WWidentifiedWWidentifier WWidentifyWWidentity޹W WWWicsoftwareWWsoleޅWޏWWmWvW$W'W+W6W9WWWsolution޶WWsolvesWDW Wsome޵WWW1W?WWWWWWWWWWWsomethingWsomewhathWWspaceޝWWWspan~W=WspecialWspecificކWވWދWތWސWޒWޕWޖWޢW޻WWWWWWWWWTWnWqWsWwW{WWW%W(W,W7W:WLWPWQW\WgWhWuWWWWWWWWWWWWWWWWWWWWWWWspecificallyވWދWޒWޕWWWWWqWLWPWQW\WgWhWWWWWWWWWWWW[W]WeWfWWWspecifiesރWލWWkWtWWWWWWW/WWW<FEWarrenFSpringer^Editoria_16`20a4.1.11bChange mitigate against to mitigate denial of service , mitigate means an easing or alleviating ... Or could be " service, the user's privacy and and lessen or halt denial of service attacks. Provision shall be g4454 2004/07/02 ecthusWWWtia\WWWtightAWWtimeWGW4W@WAWWWWtimeframeWtimesMWHWޥWާWިWުWެWޮW޳W޵W޷W޼WWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW'W,W.W1W7W<W?W@WAWBWCWGWHWIWLWtosupporttherequirementhasnoteeth'VtodayވWޒWWWtolerable޳WtoleranceCWtooޚWWtotalWtrafficވWދWޒWޕWީW޲W޳WWWWWWWWW(WCWtransportވWޒWWWtrueWturnވWޒWWWWtwoއWޑWW,WGWtypes޳WCWtypoWtypobasesVubiquitousEWudpވWޒWWWun-meetableWunachievableWcgreater W!WgroupވWޒWWWdWeWLWPWQW\WgWhWWWWWWWhandleވWޒWWWLWPWQW\WgWhWWWhandoffYW]WWWWWhandoffs;W߷WWhard;W߷W]WWhardlyW@WWharmonizeޥW*WhasޡW'W1WKWOWWWWaWfWtWWWWWWhaveޥWW4WCWRWfWWW*W5WAWeW{WWWWheading޲W޸W WZWheadingsޤW WheckWWhenceXW`WWWhereުW޿WFWYW_WWWWWWWWWWWhi-defGW4WWhighފWޔWWWGWrWzW4WWWWWWWWWW!WWimplementaiton`Wimplementation޾WimplementedވWޒWWWW]WCI>cIline 20 reads "service, the user's privacy and mitigate against denial of service attacks. Provision shall be "\ Mitigate against is a indefensible use of the language ... it should be "mitigate denial"d210g2820iKlererm Superceded 2004/07/13Marked?EWarrenFSpringer^ Editorial_16`30a 4.1.1.11.2bnthe line should read traffic, as well as signaling messages from unauthorized modification, will be specified.c_sentece construction needs some modification ... a comma needs to be added to increase clarity d212g2822iKlerermAccepted 2004/07/13Marked@EWarrenFSpringer^ Editorial_17`22a4.2.2bmline should read for graceful reduction in or increase of user data rates on the downlink and uplink, as a cthe line is confusing and neeed to be rewritten ... it seens that we're looking to say that the Ai should be able to gradually reduce the data rate or gradually increase the data rate on the downline and uplinkd213g2823 2004/07/02ZbandރWބWޅWކWއWލWގWޏWސWޑWޛWޤWޥWުW޵W޸W޹W޺W޻W޽WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWW W!W$W&W)W-W1W2W9W;W<W>W@WAWBWDWEWGWHWLWPWRWXWiWkWlWmWnWoWtWuWvWwWxW}W~W߷W߸W߽W߾WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWW W!W"W$W%W&W'W(W)W*W+W,W-W.W/Wfbchangemitigateagainsttomitigatedenialofservicemitiga>V Vchangemustinlines1718toshallޘVVchangenetworktobasestation޿VVVchangepppmplstopppormplsVVchangeqostoqosVVchangeshallclarifytospecifyVVchangetexttoreadinthisstatetheusershouldhavearadAVVchangetheheadingof4.1.1.2toprivacyandmessageintegri޸V VchangethesentenceasfollowsVVVchangethesentencestartingonthislinetostatehandofftXVVchangetoVVVchangeto802.20systemsareintendedtoprovideubiquitous|VVsupportbroadLVchangetoreadmobileipv4mobileipv6orsimpleipremovethe[VchangetoreadshallprovidepowerconservationfeaturestocVchangetoreadthesystemshouldsupportipv4ipv6orbothWVchangetotheaishallprovideprovideprivacyandmessagei޹VFM@m Superceded 2004/07/13MarkedAEWarrenFSpringer^ Editorial_18`1a4.2.3bnrewrite the wline as follows The system is expected to work in rural, suburban and dense urbanoutdoor-indoor cthe use of dense urban, suburban and rural is confusing because dense is used to as an adjective for all three in this contstrtuion The system is expected to work in dense urban, suburban and rural outdoor-indoor d214g2824iKlerermAccepted 2004/07/13MarkedBEWarrenFSpringer^ Editorial_18`35a4.3bDelete the last three words and end up with The design shall be readily extensible to wider channels as they become available.csA simple editorial change to elinate unneeded words. In the future is already implied when we say become available.d215g2825iKlerermAccepted 2004/07/13MarkedCEAnnaFTeeGMember^Technical, Binding_14`16a4.1.7.1b*As proposed in Contribution C802.20-04/55.cg4459 2004/07/02KcinBWCWGWOWRWUWWWZW\W_WcWdWeWfWhWkWmWqWrWtWvWzW߸W߾WWWWWWWWWWWWWWWWWW WWW!W$W'W+W.W0W1W4W5W6W9WAWLWPWQWTWVWWWXWYWZW\W]W`WeWfWgWhWnWqW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!WJcimpliedBWWimpliesWWimportantީWWWCW`W.W2W3WRWeWWWimpose]Wimprove޶WWimprovement޽WWWinރWޅWވWފWދWލWޏWޒWޔWޕWޘWޚWޡWެWޮWޯWްWޱW޲W޺WWWWWWWWWWWWWWWWWW WWW W1W4W<WAWMRCg2211 2004/07/13 2004/06/08MarkedDEAnnaFTeeGMember^ Editorial_8`14a2.2bUse the proposed version in the Joint contribution: C802.20-04/44, quoted as follows: "IEEE 802.20-based systems shall support broadcast and multicast services using mechanisms that make efficient use of system resources."c.Need further clarification on the requirement.d217g2212iKlerermAccepted 2004/07/13 2004/06/08MarkedEEAnnaFTeeGMember^ Editorial_8`17a3.1bA%"The 802.20 systems must be specified to enable ubiquitous mobile broadband wireless access in a cellular architecture, including but not limited to macro, micro, pico cells. The 802.20 system must support coverage in line-of-sight , non-line-of-sight, outdoor to indoor and indoor scenarios."%cwOne of the factors that would determine if 802.20 could be ubiquitous depend on how widely the technology is deployed. d218g2213iKlerermAccepted 2004/07/13 2004/06/08MarkedFIL fCcAAs described in the PAR, the 802.20 standard is designed to support various types of applications. In order to support these applications that could have very different requirements in error rate and latency tolerance optimally, it is important to specify the corresponding minimum requirements for different classes of traffic as targets for the specification of optimal PHY and MAC standards. Similar requirements have been specified for other similar standards such as IEEE 802.16.3, IEEE B[Std. 802-2001 and 3GPP. Please refer to Contribution C802.20-04/55 for further information.Id216s3ccallWOW.WfWcanވWދWޒWޕWWWWWW WUWqWW1WAWLWPWQW\WgWhWtWWWWWWWWWWWWWWWWWcannotWW1W]WWcapabilitiesWWW1WcapabilityGW4WWcapacityWW%W0WDWGW Wcaptializations<W߸WcaptionޗWޙWޞWޟWWWWWWWcapturedފWޔWWWrWzWWWWWWWWW!WcarriedދWޕWWWqWWWWWWWWWcarrierW1WcaseWWWWcdmaWW.W2Wcdma2000YWWWtialinformation6VVcertainlyރWލWWkWtWWWWWWchanceW.WchangeޤWެWWBWgW߿WW WTWWbmobilestationsshallperformwellquantitativerequirements޽VVVmobileipv4[WWmobileipv6[WWmobilityޥW޽WWWWWWFWXWWWWWW*WWWWWWmode޾WWWmodelޛWWWWWWmodelsWWmoderate*WdWmodes޽WWWFWWWWWWWmodificationW?WSWfWWW3W5WWmodifiedޤW޶WWW W2Wmodiulation޺WqWWmodulation޺WWqWwWWmonitorތWޖWWWWWsW{WWWWWWWWWWWWmonitoring޻WWWWWuWWWWWmore޺WWiWWW`WqWWWWmoveޞWޤWW~WW W=WWbcpeWW_WWWWWcpesoftwareupgradepushanoperatorshouldhavetheabilitVVcriteriaރWލWWkWtWWWWWWWWWWWޱW޴W޹W޽WWWWWWWWWW W WWWWWW W)W@WFWGWdatagramWdateWdecidingWdecoupledWdefine޺WWWWWW%W)W*W+W;WOWdefineanactiveuserasonewhocangetaccesstoabearerVdefinecontrolcapacity%VdefinedrafttextforsectionxxxdefinethetbrvaluesofoOVdefinemoderate*Vdefinerequirementsfordelayanddatarateloss)Vdefinesofthandoffandhardhandoff;Vdefinewhatisinterconnectivityatthephy/mac+Vdefined޺W޽WWWWWWdefinition޵WW\WdefinitioninthisdocumentthetermsystemspectralefficieVRVFg2214iKlererkMerge with other proposalsmAccepted-Modified 2004/07/13 2004/06/08MarkedGEAnnaFTeeGMember^Technical, Binding_12`22a4.1.5.1bAXScaling the above peak data rates in the reference case by approximately 1.6 times results in the following proposed values: "Under an ideal channel and loading conditions, the AI shall support peak user data rates in excess of the following: 1.25 MHz channel bandwidth - DL: 5 Mbps; UL: 2.5 Mbps 5 MHz bandwidth - DL: 20 Mbps; UL: 10 Mpbs" Xcg4463 2004/07/02LQ2FEAnnaFTeeGMember^ Editorial_12`16a4.1.4b"The AI shall support different modes of ....speeds(250 km/h). It is acceptable that the maximum user data rate degrades gracefully from pedestrian speeds to high speed mobility."cWW WWNWusersWWWWWWW.W2WMWWusersconstraintsWWusingWWDWLWWWWNWusuallylWutilizeWWWvaluesWWGWOW3W4W^WfWWWvariationW^WvarietyW^WvariousތWޖWWWWWWsW{WWMWNW^WWWWWWWWWWcthewordsasanexampleisnotveryappropriatehereFVVtheirWWWthemWWthereޫW޵WWWW4WWW[W`WaWWWW.W1W@WSWWWWWWWWWWV\Gg2215iKlererk The multipliers are artificial. mRejected 2004/07/13 2004/06/08Marked4-2HEAnnaFTeeGMember^ Editorial_16`6a4.1.8bAdopt the proposed text in the joint contribution: C802.20-04/44, quoted as follows: "The 802.20 standard shall include MAC/PHY features to support mutliple antenna capabililites at both the BS and the MS. "cNeed clarification to the text.d221g2216iKlererj,This should be a should especially at the MSmAccepted-Modified 2004/07/13 2004/06/08MarkedIEAnnaFTeeGMember^ Editorial_16`9a4.1.9bAAdopt the proposed text in the joint contribution: C802.20-04/44, quoted as follows: "The base station should provide antenna diversity, which may be an integral part of an advanced antenna solution. The standard shall not preclude the use of antenna diversity at the mobile stations."cNeed clarification to the text.d222g2217iKlerermAccepted 2004/07/13 2004/06/08MarkedJEAnnaQU 1GcABased on the standards and products time frame, the technology would probably be available at least two years later. It would be necessary for this technology to support maximum user data rates that are higher than the capability of the current technology, which is supporting similar applications of a relatively older generation. As a reference, 1xEV-DV Release D supports peak data rates of 3.08 Mbps and 1.5 Mbps for the DL and RL respectively in an 1.25 MHz bandwidth. Scaling these to 5B$ MHz channel bandwidth results in: 12.32 Mbps and 6 Mbps respectively. For further information on bandwidth requirements for video streams: 6-32 Mbps for high definition MPEG-2 movies, up to 19.6 Mbps for hi-def MPEG-2 sports; DVD with standard definition: maximum requirement of 9 Mbps. d220XbcapabililitesHWmWiWbburstyWWbut޺WWWW WEWWWWWqWWWWWWbyޣWޥW޹WWWWWWW WWWWGWLWWWWWWWWWW*W4WMWNW^WwWWWc/iWWWc802.20-04-44fW5WnWc802.20-04.44tWc802.20-04/44DWHWIWWWmWpWc802.20-04/55CWeWcalculatedޣWޥWWWW*Wcall޽WWWWWWcanތWޖWWWWWWWWWWsW{WWWW@W_WWWWWWWWWWWWcapabililitesvhcneedfurtherclarificationontherequirementDVVneedtochangetheheadingsofsections4.1.5and4.1.5.1anޤV Vneedtoclarifythatsystemcanoperatewithanycombination VVneedtoclarifywhatconsistentwithspectralefficiencymeaޣVVneedtoclarify/changethesentencethedesignshallbeVVV7Djthisshouldonlyapplytodatatrafficthetreatmentofsign VthissuggestionmaybeacceptableoncewehaveagoodundersޣVthistexthasbeenreviewedandvotedbytheworkinggroups5VthoseNWthoughީWthroughputyWWWthusWtime4W5W]W߄WNWtitle߶Wto4W5W@WIWLWNWOWPWQWTWUWVWWWYWZW[W]WeWgWiWnWqWrWsWtWuWxWyWހWށWނWޘWޡWޤWޥWާWިWީWޮWޯWޱW޵W޶W޷W޹W޺WWWWWWWWWWWWWW WKWLW߄WߎWߓWߙWߞWߟWߡWߩWߪW߳WߴWߵW߶W߽WWWWWWW WWWW0WFWKWLWNWOWRWTWUW[W\W]WbWcWdWkWvWyWzW|W}WWWWWWW\`Jg2218iKlerermAccepted 2004/07/13 2004/06/08MarkedKEAnnaFTeeGMember^ Editorial_20`18a4.5.4bAdopt option 2.cSOption 2 has a better organized format which shows the relevancy of each parameter.d225g2220iKlererj%Needs to be mergd with other commentsk%Needs to be mergd with other commentsmAccepted-Modified 2004/07/13 2004/06/08MarkedLEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_8`13a2.2bAChange to read: "IEEE 802.20-based systems shall support broadcast and multicast services using mechanisms that make efficient use of system resources. The minimum spectral efficiency provided by an 802.20 system while providing broadcast shall be (TBD).cThe requirement as previously written allows broadcast via unicast. 802.20 Air Interface systems should support a more efficient broadcast mechanism. The addition of a spectral efficiency number seems to be an easy way to preclude broadcast by unicast.U[JFTeeGMember^ Editorial_17`29a4.2.3bAdopt option 3.ctThe maximum channel delay spread could be much higher than 5 micro-seconds, depending on the cellular environment. d223zScwhileWYW`WWWWWwhoseޅWޏWWmWvW$W'W+W6W9WWWwhy3Wwide-areaWWwidelyEWWwider7WW WwillރWބWޅWވWލWގWޏWޒW޹WWWWWWMW]WkWlWmWtWuWvWWWWWWWWWWWWW$W'W+W6W9WHWLWPWQW\WgWhWWWWWWWWWWWWWWWWW WdtheabilitytotuVVwithރWތWލWޖWޚWޛWޣWޥWާWިWWWWWWW WWWW-WGWOWPWUWYWkWsWtW{W߾WWWWWWWWWWWWWWWWW*W4W?WJW_WfWsWWWWWWWWWW ?knetworkrWހW߽WWWWWnetworksWnewlyWnoW W;W߷WWWWWW!W#W4W5W=W`WaWjWkWqWWWWnoexplanationgivenastothebenefitofprovidingthesevaVnoneedtoberedundantVWWW$W:WߙW߶W߷W߾WWWWWWWWWnotatallclearwhattextfromc802.20-04/44isbeingpropoVnotnecessaryandoutofscopeofthisdocumentVnumberWWnumbers WobjectivesWobservableWobviousW%WofAWKWNWYWhWjWpWwW}WހWWWWWWWW WߎWߙWߥW߶W߾WWWWWWWWWWWonrW|WW WW2W3W߷WWWWWon-lineWoneSWWW߽WWonlyAWSWW߶WWopenW`bLg2470jA_#1: Change to read: "IEEE 802.20-based systems shall support broadcast and multicast services using mechanisms that make efficient use of spectrum and system resources. " #2: Change to read: "IEEE 802.20-based systems shall support broadcast and multicast services, and should use mechanisms that make efficient use of spectrum and system resources. "_@A> 33   33>yAAd hoc - lead by Mark Klerer. Following are the notes: ISSUES Requirement shall vs should in first sentence Definition of Appropriate Metric Spectral Efficiency as metric with assumption that wrap-around occurs with all broadcast channels on same frequency allocation (i.e. best case) How does or should this work for multicast How is spectral efficiency impacted by different types of broadcast traffic Broadcast alternate assumptions 1 Same information available from every cell (and 2004/07/02[_ Ld226bhL 2004/07/13 2004/06/07MarkedMEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_13`23a4.1.6b|Change to read as follows: "...bearer channel available with a delay of less than 25 ms with a probability of at least 0.9.cIIt is expected that system access times will be a probabalistic quantity.d227g2489iKlererjAProbability is OK but number should be as proposed in my comment.mAccepted-Modified 2004/07/13 2004/06/07MarkedNEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_14`2a4.1.6bnChange to read as follows: "...should scale with system bandwidth if the same application mixes are assumed."clThis parameter is understood to be a scalable quantity, however linearity may not be the appropriate choice.d228g2341iKlererkI can live with the vagueness.mAccepted 2004/07/13 2004/06/07MarkedOEAyman, Arak, JimFNaguib, Sutivong, TomcikGMemberg4471 2004/07/02_a LyB synchronized ?) 2 Information may not always be in the same band 3 No requirement for prior communication with the mobile for access to broadcast information ? E jefficientLWWeitherވWLWWWWeitherthisoptionortheonespecifiedinmycommentswillވVeliminatingޮWemployWemployedWenableWencryptionWend-to-endWend-userWenforcementWensuregWWentireSWentirelyWenvironmentvWenvironmentalWequalާWerroryWWNWvWzWespeciallyHWevaluatingߞWߴWevaluationPWgWzWevaluationcriteriacouldbeusedtodefinegracefuldegradaPVevenFWexampleSWޡWjWnWexceptWexcess3WexchangeWexcludingWexistingߋWexpedited~WexperienceWexplanationޥWާWexpressedެWextentߙWexternal߽WfacilitateWW6j1changetoreadieee802.20-basedsystemsshallsupportbroLV1supercedesthiscommentV1.2ޥW10W100߄W11=WޡW120gW1220W128kbps3W13gW2W136LW137OW15JW150yW152LW153OW154W1556W:WCWGW^WaWRWSWTWUW[W\W]WbWcWdWDctitleW߶Wtoރ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޼WWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW'W,W.W1W7W<W?W@WAWBWCWGWHWIWLWNWOWRWSWTWUWVWWWYWZW]W^W`WaWbWcWfWgWhWjWkWlWmWqWsWtWuWvW{W߸W߻W߿WWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWW W$W'W*W+W.W/W0W1W2W3W4W5W6W9W?W@WAWIWJWLWNWPWRWjprobablyWproceduresWprocessingWproducedWpromiscuousWpromoteWproofߙWproponentWproposal޺WWߓWWproposalsgWߞWߴWproposeKWRWTWUW[W]WbWcWdWkWWWproposetoacceptthewordinginrecord180replytocommentkVproposetodeletesection4.1.7.1asopposedtoadoptinganyKVproposetodeletethesectionperreplyinrecord155tocomRVTVUV[V]VbVcVdVproposediWkWlWrWuW~WWMW߀W߈WߙWߣWprotectWWprotocolWWprotocolsWprovideqWWW߀WߓWWNWvWWWprovided߄WߩWWpurposeߙW߽WqcZWqosީWߞWߴWNWWWqualityWWquestionWquiteީWr0030-aNWradio߶Wrandom߄WrangegWrateQWީW߉WߣW3WNWvWwWzWbWcWpark຃pittampalli !"#$%&'()*+,-./0123456789:;߶߷߾ăɃʃ҃ӃԃՃ!"#EFGO`abcdkosxyঃৃਃஃ ragsdale|}~<=springer<=>?@AB߸Ń˃ lzsutivongLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjW߿WWWWWWWWW5WHWIWfWnWtW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWajO^Technical, Binding_15`1a4.1.7.1bDefine draft text for Section XXX. Define the "TBR" values of Option 4. Then add Text to Reflect 3GPP2 Approach to Qos to Section XXX.cADiffServ may work with interfacing to 3GPP networks, but the 3GPP2 approach is different. The 3GPP2 network sets the QoS for the Mobile based on call type and type of service the user has paid for. The network tells the RAN what it needs to deliver. Option 4 seems to be the closest to this, with ranges specified for different traffic classes. However, we need to fill in Section XXX.d229g2491iKlererjNeeds further idscussionmRejected 2004/07/13 2004/06/07MarkedPEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_8`18a3.1b replace with the following text from the joing contribution "The 802.20-based system shall provide mobile broadband wireless access in an architecture consisting of macrocells, microcells, and picocells" g4472 2004/07/02jHbofflineWWWofingvWoldWWonާW޳W޻W޾WWWWWWWW WW$W0W@WXWWWWWWW?WBWDWFWMW[W_WuWvWyWzWWWWWWW W WoneޟW޻WWWWWWW߽WWW.W2W@WuWWWWWonlyW#W<W߸WWEWopenWWoperating޺W޻W߾WqWuWWWoperationWWW_WhoPcXRemove the sentence starting with "The 802.20" and replace with text from C802.20-04-44.d231g2219iKlererm Superceded 2004/07/13 2004/06/07MarkedQEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_8`17a3.1bHThe sentence should read " The 802.20-based systems shall provide ...." cXInsert based after 802.20 document 04-44. This corrects the requirements language used.d232g2218iKlerermAccepted 2004/07/13 2004/06/07MarkedREAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_17`19a4.2.2bMDelete Section or remove requirements and preserve as in informative section.cThis section doesn't belong in this document. Either delete or make it informative. We have approved spectral efficiencies, data rates, etc. The requirements document should not dictate what tools to use to achieve these.d234g2500iKlererm Superceded 2004/07/13 2004/06/07MarkedSg4475 2004/07/02`‚*ޤީŃ*Rߙߢߧ R^d{ࡃ‚1>ޢޣ=>ȃɃʃ˃ Av‚2PޫWߤ S_ଃୃ‚3hms~ޅކއޏސޑެσЃу#@Gfmnovwx߀߁߅ߋߌߍ$%&'()+,-/3456789:;ET`zۃ܃݃@:xcinsertbasedafter802.20document04-44thiscorrectstherQVVinsertieee802.20beforemobilethisaddsclaritytothetejVVinstead޹WW3Wintegrity޸W W WWintendedWWMWintentUWaWcWWWWWWinter-frequencyWinter-userWNWinterconnectivity޴W+WiWkWinterconnectivityatthephy/macambiguous+VkVinterestedރWލWWkWtWWWWWWWWWWWinterfaceވWދWޒWޕW޳WWWWWWWWLWVW]W^W`WaWcWqWWWWLWPWQW[W\WgWhWtWWWWWWWWWWWWWWWWWWWWWinterfacingOWfW9mbrequirementsworkWWreservationWWresolveMWresolvingWNWresourceWWMWNWWresourcesWDWLWWWWrespectWWrespectivey!W"Wresponse޺WqWWWrestore޵WWrestorethedefinitionandputiteitherinthissectionin޵VVrestrictWWresultsWGW4WWWWretain]WrewordTWWnshallscaletowiTVrewording޷WrewriteAWWWrewritethewlineasfollowsAVVrf޺WqWvWrfcWrmޛWWroleWWWrouteW߽WroutedWroutingWWrsvpWMWrules޺WqWrural1WAWWWWssWsafelyWsafety޺WqWsameWNWIWNWWsameascomment35Vsar޺WqWsatisfiesWsatisfyWW&WWNWOWsatisfyingWNWscaleNWTWIW$ctotalW0Wtr45\WWWtrade-off]WtrafficވWދWޒWޕWީW޲W޳WWWWWWWWW(WCWOWqWWWLWPWQWRWZW[W\W^W_WbWeWfWgWhWWWWWWWWWWWWtransitionsbWWtranslation]WWWtransmitYWWWtransmittingYWWWtransportވWޒWWWLWPWQW\WgWhWWWWWLWPWQW\WgWhWtwoއWޑWW,WGWYWoWxW&W)W-W/W4W8W;WoWWWWtwooptionsarespecifiedtheobjectivesspecifiedcanbesaVtypeOWfWtypes޳WCW[WeWtypoWWtypobasesVVubiquitousEWWudpވWޒWWWLWPWQW\WgWhWun-meetableWWunachievableW0WjpSEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_18`8a4.2.3bMAdopt Option 2 with a minor modification as follows: ...system shall work...cn5 Microseconds seems to be a reasonable minimum requirement. Option 2 seems to be reasonable for the section.d235g2501iKlererk*Prefer option 3 but can live with option 2mAccepted 2004/07/13 2004/06/07MarkedTEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_18`35a4.3bReword as follows: The air interface design shall scale to wider channel bandwidths than those mentioned here, as they become available.cThis sentence may be useful to retain. Scalability is useful, but let's not demand linearity or any other specific functional relationship.d239g2505iKlerermAccepted 2004/07/13 2004/06/07MarkedUEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_19`8a4.4.1g4477 2004/07/02otUb)Delete the Paragraph or make informative.cAThis paragraph goes into great detail on what IETF RFCs to use in equipment. This can vary depending on the customer's requirements, services offered, etc. We recommend deletion of the paragraph, or removal of requirements language to show intent with informative text.d240g2506iKlererjSI cn live with this if it becomes a should or informative as request by the commentmAccepted-Modified 2004/07/13 2004/06/07MarkedVEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_19`17a4.4.1b9Remove sentence starting with "A Qos based IP network..."cVThis seems to place a requirement on the network and not the air interface PHY or MAC.d242g2508iKlerermAccepted 2004/07/13 2004/06/07MarkedWEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_19`21a4.5b?Change to read: The system should support IPv4, IPv6, or both.g4479 2004/07/02aymanarakjimLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjV߿VVVVVVVVV5VHVIVfVnVtV{VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV eshwar !"#$%&'()*+,-./0123456789:;hariɃʃ˃jimLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWjohnލގޏސޑޒޓޔޕޖkazuhiro׃؃كڃۃ,bremovethedistinctionbetweenuplinkanddownlinkބVގVVlVuVVVVVVVVVV VremovethefragmentbedesignedinamannerthatdoesZVVremovethissectionވVޒVVVLVPVQV\VhVVVwithcertainapplicationsshallbegivenpreferentia$VFVreplaceތWޖWWWWWWWWWWWW W!W&W,W-W0W1W2W3W6W:WPWsW{W߾WWWWWWWWWWWWW!W"WOWoWyWWWWWWWWWWWWWWreplace802.20'sworkwiththestandardVreplaceitwithaverageuserdatainaloadedsystemshallb V!Vreplaceitwithcontiguous:VVreplaceitwithdataratesmaygracefullydegradefrompedesVVreplaceitwithenablerstosupportVVw+Mbremovethedistinctionbetweenuplinkanddownlink@rrepalce@pxWcThe word "must" has no meaning in a requirements document. We also would like some clarification regarding the support for IPv4 and IPv6 to specify that there is no requirement for simultaneous support.d243g2509iKlererm Superceded 2004/07/13 2004/06/07MarkedXEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_19`24a4.5.1bChange the sentence starting on this line to state: Handoff techniques are required to support mobility between cells, systems, frequencies, and optionally between IP subnets.cThis requirement as written places "may" requirements on the mobile station's movement! Recommended sentence places requirements on the AI. IP subnet mobility is at the network layer, hence is considered optional from an AI PHY and MAC perspective.d244g2510iKlerermAccepted 2004/07/13 2004/06/07MarkedYEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_19`26a4.5.1g4481 2004/07/02 cthe802.20standardshallsupportthissentenceisnotclear4VVtheaishallsupporttddisambiguousVVtheclassesofserviceisnotclearVthecommasaroundprivacyinthislinebelowdisrupttheme VvsboptionsW_Wor޵W޹W޽W޾WWWWWWWWW W<W>W@WRWUWWW[W`WaWbW߸WWWWWW WWW0W3WCWNW]WvWzW{WWWWWWWWWWWWWWWWWWWotherޚWWWWWW9W<W߸WWWWlWWWotherwise޹WWoutWWWWoutdoor޽WW2WEW}WWW<WWWoutdoor-indoorWover-the-airWWoverallW}WW<WoverheadWWpacketWWWWhWWWNW^W_WpacketsWWW߽WWpageޛWޞWWWpar޽WWgW߻W߿WWWparagraphUWbWparagraphsWparamentersWparameterWDWparametersޥWWW*WNW`sboptions@vortddoratdd@vpart@ performance@!physical@{preferential@proposedchangeoftheentiresentenceinline6theaishal@Rprovidethereferencestootheripnetworkstandardsandip@provided@purposes@rates@readily@regulatory@]removemustorwilltomakethisaninformativesection@removesentencestartingwithaqosbasedipnetwork@tzYbDelete sentence.cA The "definition" of soft handoff given here is incorrect. Soft HO is a HO with the MS transmitting simultaneously to two BS on the RL, while two BS transmit simultaneously to the MS. Generic make before break handoff is NOT soft handoff. See IS-95 or cdma2000 for a formal definition.  d245g2511iKlerermAccepted 2004/07/13 2004/06/07MarkedZEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_19`29a4.5.1.1b8Remove the fragment: "be designed in a manner that does"c}The phrase "shall be designed in a manner that does..." is not a requirement on the PHY and MAC. Reword to clarify as below.d246g2513iKlerermAccepted 2004/07/13 2004/06/07Marked[EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_19`30a4.5.1.1btChange to read: "MobileIPv4, MobileIPv6, or Simple IP." Remove the fragment starting with "for the preservation..."g4483 2004/07/02'bdeletesentenceYVVVx}[cvSince there is a requirement for both IPv4 and IPv6, the Mobile IP support should cite both MobileIPv4 and MobileIPv6.d247g2514iKlerermAccepted 2004/07/13 2004/06/07Marked\EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_19`30a4.5.1.1b Add a definition for "Simple IP"caThis term Simple IP is not well defined in this document and was developed in TIA TR45 and 3GPP2.d248g2515iKlerermAccepted 2004/07/13 2004/06/07Marked]EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_19`32a4.5.1.1bDelete this sentence.cThis sentence is not relevant to handoff, but rather to NAT (Network Address Translation) techniques. These are implemented at higher layers than the 802.20 air interface will address.d249g2512iKlerermAccepted 2004/07/13 2004/06/07Marked^EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_19`34g4486 2004/07/02bafddanfddVCV%fbforthepurposeofthisdocumentan802.20systemconstituteV߽VforwardingWW(W_WbWWfragmentZW[WWWframevWfreeWWfrequenciesXWWfrequency޺WWqWWWWWWfromޣWޤW޹W޽WWWWWWW WWWz^a4.5.2bRemove Section.ciWe support Option 1, removing this section. It does not seem relevant to the air interface requirements.d250g2516iKlerermAccepted 2004/07/13 2004/06/07Marked_EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_20`7a4.5.3b/Change "CPE" to Mobile Station in this section.c]CPE seems like the incorrect term here. It is usually used in the context of fixed services.d251g2517iKlerermAccepted 2004/07/13 2004/06/07Marked`EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_20`8a4.5.3b;Make the section "informative" to show intent or remove it.cThis section seems to be a discussion Over the Air Service Provisioning (OTASP). This function, while important to equipment design and implementaiton is not a part of the air interface itself. Hence there should be no requirements on the AI.d252g2518iKlerermAccepted 2004/07/13 2004/06/07Markedag4489bthoseWWWTWWWNWWWthreeBWWthroughތWޖWWWWWsW{W߽WWWWWWWWWWthroughputWWWWWthusޣWާWWWW?WWަWާW޲W޴W޸W޹W޺W޻W޽W޿WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWW!W$W8W9W>WAWBWEWFWHWLWMWNWOWTWWWXW[W_W`WaWbWcWiWkWtW|W}W~W߶WߺW߽WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W Wa 2004/07/13 2004/06/07MarkedbEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_22`23a4.7bClarify this requirement or make the sentence an informative lead-in to the paragraph. It could be done as follows: "The AI is intended to support multiple protocol states with dynamic transitions between states."cHow is the requirement for "fast and dynamic" transitions between states measured? This sentence should be clarified, since it is confusing to the reader.d254g2520iKlerermAccepted 2004/07/13 2004/06/07MarkedcEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_22`26a4.7bgChange to read: ...shall provide power conservation features to improve battery life in idle terminals.cIs the intent of the sentence to promote power management "hooks" in the air interface? The requirement should not mandate any particular technique to achieve this.d255g2521iKlerermAccepted 2004/07/13}aEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_20`15a4.5.4b>Remove "must" or "will" - to make this an informative section.cOA&M requirements are equipment requirements, not Air Interface Requirements. This section should be informative to show the intent of the service providers attending 802.20. If there are requirements on the AI or on the MIBs these could be stated.d253g2519iKlerermAcceptedMc 2004/06/07MarkeddEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_23`5a5bDelete this reference.ckThis contribution is not referenced anywhere in the requirements, and is not approved by the working group.d257g2523iKlerermAccepted 2004/07/13 2004/06/07MarkedeEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_23`9a5bDelete this reference.ckThis contribution is not referenced anywhere in the requirements, and is not approved by the working group.d258g2524iKlerermAccepted 2004/07/13 2004/06/07MarkedfEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_12`22a4.1.5.1bxAdopt the text in Section 4.1.5.1 of C802.20-04-44, with the modification of deleting the word "channel" from the table.g4494 2004/07/02qdanޗޘޙޚޛޜޝޞޟޠޡޢޣޤޥަާިީުޫެޭޮޯްޱ޲޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃ̓  *>?JRSTUVWXYZ[iqu~ࡃࢃࣃःԃdoug݃ރ߃ ߹ߺ߻߼߽ƒÃȃ΃σЃу׃؃كڃۃ܃݃ 01BCDMN^_jrvwृଃƒ !"#EFGOWybdelete3456ެVTVdelete7ޭVUVdeletealltextandpossiblythesectionheadingtooVdeletealltextin4.2.5VdeleteasanexampledataratesgracefullydegradefrompedeVVVdeleteaverageuserdataratesinaloadedsystemshallbeiV0VdeletebasedontheclassificationoftrafficinaccordanceV_VdeleteburstyVVdeletecurrently.VVdeletelines13-16textbeginningwithhowtheVVdeletenotedependingontrafficmixwithinacellthecontrVDV Vdeleteoption2ޮV"V#VVVdeleteorusethefollowingtextVdeletepartitioningVVdeletephase1columnsdeletephase2headingsiephase2rV1Vdeletepotentiallyonly#VEVdeletesectionqVrVVVVVdeletesectionorremoverequirementsandpreserveasininfRV{VTfc (C802.20-04-44) text in Section 4.1.5.1 represents a consensus of a number of Individuals. It was included previously in V12, but seems to have been removed in V13.d259g2487iKlererj kI prefer option 2mRejected 2004/07/13 2004/06/07MarkedgEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`4a1.1bWThis sentence shall read "These requirements shall be consistent with the approved PAR"cChange "are" to "shall be" and insert "approved" before PAR. Reason: proper user of requirement language and editorial change to make the section more succinct.d260g2211iKlererm Superceded 2004/07/13 2004/06/07MarkedhEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`6a1.1bSChange Line 6 shall read: " ... for the 802.20 packet mobile wireless standard ..."g4496 2004/07/02cchangearetoshallbeandinsertapprovedbeforepargV߿VchangefuturetensetopresenttenseVVchangedWWchanges|WWchannelރWކWލWސWWWWW7WGWJWkWnWtWwWWWWWWW%W(W,W4W7W:WAWWWWWWWWWWWW WWWWchannelsWW7W.W2WW WcharacterޝWWWcharacterizeWWchoice WNWIWrWcite[WWclaimsWWclarification޵W޾WDWHWIWWWhWWWWmWpWWWWWWclarifiedކWސWWbWnWwW%W(W,W7W:WWWWclarifyޣWWWWWWWW WZWWWWWWWWWCMW^WWhcThe text in C802.20-04-44 is somewhat different in this section. Modify to add clarification that 802.20 is a packet mobile wireless standard. d261g2212iKlerermAccepted 2004/07/13 2004/06/07MarkediEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`7a1.1bInsert the following sentence at this point: "It is further assumed that Layer-3 and above are standards-based IP architecture" This is an editorial change to make the section more succinctc"Remove text starting at line 7. Id262g2213iKlererm Superceded 2004/07/13 2004/06/07MarkedjEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`12a1.2bnThe sentence should read " This document established the detailed requirements for the IEEE 802.20 Mobile ..."cDInsert "IEEE 802.20" before Mobile. This adds clarity to the text.d263g2215iKlerermAccepted 2004/07/13 2004/06/07MarkedkEJoanneFWilsonGMemberg4499 2004/07/02g`naguibsutivongtomcikhViVjV߿VVVVVVVVV5VHVIVfVnVtV{VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV{]b802.20-basedWDWLWPWQWWWWWW87 W90W0W3W953WWaތWޖWޙWޛWޝWޟWޤWޥWަWާWޫWްW޵W޺WWWWWWWWWWWWWWWWWWWW WWWWW W@WEWMWSWVWZW\WsW{W|W߽WWWWWWWWWWWWWWWWWWW W!W*W0W3W>W?W@WAWCWDWHWNWSWXW_WqWvWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWTcthetextinc802.20-04-44issomewhatdifferentinthissecthVVthetextofsection4.1.5isnotspecificenoughޢVVthetwopartsofthesentencestartingatline10mayappear,VoVtheuseofdenseurbansuburbanandruralisconfusingbecauAVVthewordmayhasnospecialmeaninginarequirementsdocumeVthewordmusthasnomeaninginarequirementsdocumentweaWVVV5Hcthetextinc802.20-04-44issomewhatdifferentinthissect@thewordsasanexampleisnotveryappropriatehere@Ttherearehardlyanyapplicationsthatrequirebeareraccess@therefore@4they@thisthiscontributionisnotreferencedanywhereintherequirem@thisisafeatureoftheuserterminalandbackendinfrastru@thissectionspecifiestwooptionsoption1makesreference@those@ thus@Dtitle@etoQtosupporttherequirementhasnoteeth@total@ntrue@under@"naguibsutivongtomcikLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgV cthejWkWlWmWnWoWqWrWtWuWvWwWxWzWW߻W߾W߿WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWW W$W%W&W'W(W)W+W,W-W.W0W1W2W3W4W6W7W8W9W:W;W?W@WAWIWLWPWQWZW[W\WaWeWfWgWhWiWkWmWnWoWpWtWwWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWk^Technical, Binding_11`5a4.1.1bSpecify 2 bits/sec/Hz 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.d266g2233iKlerer 2004/07/02kkI prefer my own proposalmAccepted 2004/07/13MarkedlEJoanneFWilson^Technical, Binding_11`5a4.1.1b6Remove the distinction between uplink and downlink. cThe 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.d267g2234iKlerermAccepted 2004/07/13MarkedmEJoanneFWilson^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. 3d268g2235iKlerermAccepted-Duplicate 2004/07/13MarkednEJoanneFWilson^Technical, Bindingg4502 2004/07/02Pn bcryptographic޷WcurrentޛWޤWWWW WcurrentlyW.WWWdataޣWޤWޥWޯWޱW޴W޹W޽WWWWWWWWWW W WWWWWW W)W@WFWGW}W~WWWWW WWWWWWWWW W!W*W.W0W2W3W4W<W=WWWYW^W_WcWiWvWwWzWWWWWWWetaccesstoabearerVdefinecontrolcapacity%VdefinedrafttextforsectionxxxdefinethetbrvaluesofoOVdefinemoderate*Vdefinerequirementsfordelayanddatarateloss)Vdefinesofthandoffandhardhandoff;V߷Vdefinewhatisinterconnectivityatthephy/mac+Vdefined޺W޽WWWWWWWdefinition޵WW\WWWdefinitioninthisdocumentthetermsystemspectralefficieVV`bdegradation@delete3456@deletesentence@ydeleteshouldonline5@deletethesentence@denial@designed@|desirable@/disable@ download@effective@zeirp@end@,example@_exchange@'extent@7fading@for@forthepurposeofthisdocumentan802.20systemconstitute@|from%ftp@g@hardware@Aidle@eigmp@Yinz6inability@incorporated@ independent@3informative@{integrated@@interactive@ipv4@[isYiso/osi@:keeping@level@licentsed@,linkadaptationshallbeusedbytheaiforincreasingspect@Xlow@3mac's@mandatory@measurements@_ativerequirements@Omovetable4-1captiontopage11line23@mt@nearnecessary@network@)new@next@note@qofjoffline@ioperations@\vcitisexpectedthatsystemaccesstimeswillbeaprobabalisMVHVit'sW2WitemWWitem3WWits޺WqWWitself`WWituޫWSWjustW0Wjustified]WkmphWWWknown.WWlacking޺WqWWlanguage޹W>WQWUWgW߿WW WWWWWmWvWlastWWlatencyވWޒW޳WWWCWlaterGWlayerވWފWދWޒWޔWޕWWWWWWWWWWW5WXWqWrWzWWWWlayers]WleastGWleaving(WlessWlet'sTWlightWlikeWWW_WWlikelyWWWlimitޅWޏWWmWvWlimitationWlineޠWޡWެWޮWޯWޱW޼WWW,W@WiWWWline6isduplexingschemesޠVlinearityNWTWlinearlyާWlinesޘWްWW0WWIcconstruction?WWcontext_WWWcontinuous:WWWcontinuousisnottherightword:VVVcontradicting,W0WoWyWcontradictoryW0WcontributionWCWdWeWWeWtWWWWWcontributionsުWWWcontrol޷W޻WW%W WDWGWuWW Wcontrolcapacityisnotclear%VGVcontstrtuionAWWcthatthefollowingtableispresentedasthebases=VVtheރ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޿WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'W+W,W1W2W3W4W5W:W=W>W@WAWBWCWDWEWFWGWHWIWJWKWLWNWOWPWQWRWSWUWVWWWXWYWZW[W]W^W_W`WaWbWcWdWeWgWhWccasimpleeditorialchangetoelinateunneededwordsinthefBVVabilityWWH.xcsportsGW4WWspreadJWWsrd޵WWstageW1WstandaloneWstandardޛWW4WCWGWhW߼W߾WWW4WeWWWWstandardize<W߸WstandardsޚWW-W9WCWGWWW1W4WeWWWWstarting,W0WPWiWWWWoWtWyWWWWstateWWWstatedaWWWWstatementW0WstatementsWWstatesWbWWWWstation<W߸W Wstation'sXWWstations<W߸WWd`pAޠ޴Ƀ׃ރ+Hhߒ߼ǃ.ikm6:CK^axyފޔԃ߃!_irz߽Ѓ"1ྃ࿃ÃŃƃ!STW\ހك SU`ߠ҃Ӄjn੃ƒă,-Ճo‚"")#c‚#jƒƃԃ‚$ޚʃ&Lẵ߃@O‚%.D׃؃كڃۃ܃݃ރ‚&ތޖި޵˃փas{ÃŃуփJKǃȃɃ˃΃σЃ‚'ވޒ޺޽҃؃CFLPQ\]eghqਃઃރ‚(ޘޡۃ EQV|rstૃ‚)ޛޥ̃24KP*n_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 bandwidthsd269g2236iKlerermAccepted-Duplicate 2004/07/13MarkedoEJoanneFWilson^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d270g2237iKlerermAccepted-Duplicate 2004/07/13MarkedpEJoanneFWilson^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d272g2239iKlerermAccepted-Duplicate 2004/07/13MarkedqEJoanneFWilson^Technical, Binding_19`34a4.5.2bDelete Section.cg4505 2004/07/02qg2240iKlererk-This is a duplicate see initial reply commentmAccepted-Modified 2004/07/13MarkedrEJoanneFWilson^Technical, Binding_20`7a4.5.3bDelete section.cThis 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 frameworkd274g2241iKlerermAccepted-Duplicate 2004/07/13MarkedsEJoanneFWilson^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."caAll options are overly detailed with respect to specific statistics that need to be accumulated. d275g2242iKlererm Superceded 2004/07/13MarkedtEMichaelF YoussefmirGMember^Technical, Binding_11`5a4.1.1g4508 2004/07/02 qcAAdvocating 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 2d273EchigherGWJW]W4WWWWWhoYWWWhomeWWhookscWWhope3WhowWWEWbWWWWWWhowistherequirementforfastanddynamictransitionsbetwbVVhowererW.WhoweverNWOWIWfWWhte<W߸WhzޝWWWiWWiWߺWWW1WWWWideaW1WWidentifying WWieeeCWjWWeWietfWUWWWWifWWWWW4WEWaW߻WW.W0W1W3WWWWWiffW1Wiline>W Wiline20readsservicetheuser'sprivacyandmitigateagain>V Vill-definedއWޑWWoWxW&W)W-W8W;WWWimmediatelyWWimplementaiton`WWimplementation޾WtWWWW]W1WLWPWQW\WgWhWWWtbSpecify 2 bits/sec/Hz 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.d276g2252iKlerermRejected-Duplicate 2004/07/13Markedug4509 2004/07/02uEMichaelF Youssefmir^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.d277g2253iKlerermAccepted-Duplicate 2004/07/13MarkedvEMichaelF Youssefmir^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. 3d278g2254iKlerermAccepted-Duplicate 2004/07/13MarkedwEMichaelF Youssefmir^Technical, Binding_12`22a4.1.5.1g4511 2004/07/02 z|bdownloadWWdownloadingWWdraftOWfWdriversWWWdroppedWWdsWWdue޺WW_WqWWduplexingޠWWWWWduplicated޹WWdurationWWduringWWdynamicbWWeWWWWWWWWWWW WW|WߺW߽WWWWWWWW1WMWNW^WjWWWe-mailWWeachWWWWWMWNW^W_WeapWWeasing>W WeditorialiWWefWWޖWWWWsW{Weffectiveness޻WuWefficienciesWWWWefficiencyރWލWޢWޣWޥWWWWWWLWkWtWWWWWWWWWWWWW*WwWefficientWDWLWWWWefficientlyWWeffortWW_Wwb#Remove option 1 and adopt option 2cfThe concept of bandwidth must be clarified given that we are not requiring specific channel bandwidthsd279g2255iKlerermAccepted-Duplicate 2004/07/13MarkedxEMichaelF Youssefmir^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d280g2256iKlerermAccepted-Duplicate 2004/07/13MarkedyEMichaelF Youssefmir^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d282g2258iKlerermAccepted-Duplicate 2004/07/13MarkedzEMichaelF Youssefmir^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 frameworkd283g2259iKlerermAccepted-Duplicate 2004/07/13Marked{g4515 2004/07/024ߢa4.1.7.1d138g4554i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߣ^Technical, Binding_17`24a4.2.2d150g4555i&Naguib, Sutivong, Tomcik, YallapragadajAMUse of the word "will" is not appropriate. Suggest the following remedy; Comment 190 has the same proposed resolution Link adaptation may be used by the AI for increasing spectral efficiency, data rate, and cell coverage reliability. The 802.20 AI may use adaptive modulation and coding schemes in both the uplink and the downlink.M 2004/07/13ߤ^Technical, Binding_18`21a4.2.5d151g4556i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߥ^Technical, Binding_19`4a4.4.1d153g4557i&Naguib, Sutivong, Tomcik, Yallapragadak2These changes improve clarity of the requirements.mAccepted 2004/07/13ߦ^Technical, Binding_15`11a4.1.7.1d182g4558i&Naguib, Sutivong, Tomcik, YallapragadamAccepted130g4526cistheintentofthesentencetopromotepowermanagementhocVVis-95YWWWissueWWWtWW`cbadW1WbandwidthކWސWާWW/W7WGWnWwW%W(W,W4W7W:W?WAWxWWWWW WWbandwidthsކWސWWnWwW%W(W,W7W:WWWbase WWWbcmcWWbcmcmustsupportietfipbroadcastandmulticasttrafficefVVbeރ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`WaWbWgWkWmWnWqWrWsWtWvWwWzW{WߺW߻W߿WWWWWWWWWWWWWWWA{EMichaelF Youssefmir^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. d285g2261iKlererm Superceded 2004/07/13Marked|EJimFRagsdaleGMember^ Editorial_8`17a3.1b change to: "802.20 systems are intended to provide ubiquitous mobile broadband wireless access in a cellular architecture (e.g.macro/micro/pico cells). cAdopted changes were not made, d286g2252iKlerermAccepted 2004/07/13Marked}EJimFRagsdale^Technical, Binding_13`1a4.1.5.1b The 802.20 system shall support non-line of sight, outdoor to indoor scenarios and indor coverage. Change overall heading to 4.1.6 User Data rates. Add new subheading 4.1.6.1 Peak User Data rates callcurrentthreeoptionsneedimprovementaddoption4޽VVValloptionsareoverlydetailedwithrespecttospecificstaތVޖVVVsV{VVVVVVVVVallocation/WxWallowރWބWދWލWގWޕWWWWWkWlWqWtWuWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWW W1W<WWW߸WWWWWWalthoughW.WalwaysW WߺWWambiguityWWambiguousWWW!W*W+WWWW"WdWkWsWanރWލWޛWޡWީW޵WWWWWW7WAWFWGWLWXWkWtWWWWWWWWWWWWWW4WRWtWWWWWanalysis.WWHLbchangetoduplexingschemesfdd/tddޠVVVchangetoreadasfollowsbearerchannelavailablewithadeMVHVchangetoreadasfollowsshouldscalewithsystembandwidthNVIVchangetoreadieee802.20-basedsystemsshallsupportbroadLVVchangetoreadmobileipv4mobileipv6orsimpleipremovethe[VVchangetoreadservicesaretranslatedintoacommonsetofVchangetoreadshallprovidepowerconservationfeaturestocVVchangetoreadthe802.20airinterfaceshallprovidefeaturVchangetoreadthesystemshouldsupportipv4ipv6orbothWVVVchangetotheaishallprovideprovideprivacyandmessagei޹VVAW߀^Technical, Binding_12`22a4.1.5.1d3g4520iNaguib, Sutivong, Tomcikjarious environments of a Macro/Micro/pico cellular system. d289g2261iKlerermAccepted 2004/07/13Marked߀^Technical, Binding_12`22a4.1.5.1d3g4520iNaguib, Sutivong, Tomcikje rates d288g2260iKlerermRejected 2004/07/13MarkedEJimFRagsdale_18`12a4.2.3bPick option 3 cWSystem must work under the various environments of a Macro/Micro/pico cellular system. d289g2261iKlerermAccepted 2004/07/13Marked߀^Technical, Binding_12`22a4.1.5.1d3g4520iNaguib, Sutivong, Tomcikj/07/13Marked߀^Technical, Binding_12`22a4.1.5.1d3g4520iNaguib, Sutivong, Tomcikjn 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. }0&bthe802.20systemsmustbespecifiedtoenableubiquitousmoEVVthe802.20-basedair-interfaceaishallbeisoptimizedforVVtheaishallprovideallthehookstoenabletheprovisioninVVtheaishallsupportautomaticselectionofoptimizeduserdvVlsupportdifferentmodesofspeeds250km/hitiFVVtheaishallsupportpeaksystemdataratesinexcessofthe3VtheaishallsupportsVVtheai802.20standardshallsupportthemeanstoenablelinkMVthelineshouldread?VVthemaclayershouldbeabletocontrol100simultaneousactVVthesentenceshouldreadthe802.20-basedsystemsshallprovQVVthesentenceshouldreadthisdocumentestablishedthedetaijVVthesystemshallsupportanarbitrarysetvarietyoftrafficV^Vthesystemshallmustsupportbothipv4andipv6Vthesystemwillshallprovideappropriatemacandphycapabi VVtheftWWS4j2RWeWfWjWlW}WWLW߀WߝW߳WWSWWWWWW W201W202W206|W}WWWWWWWWWWWWW21/page=W212WW220hWmW223WWW224|W237WWWW243W247W2475~W250JWxWW2597~W2598~W2737W;WDWFWVWbW278WW279WWW3pWsWvW~WެW޽W1W2WWW3-2W3.1gW3.1.1ߙW3.5W39ޯWޱW3gpp2NW3gpp2'sNW4~WއW޲W޳WWW4-1IW4-33W4.1.2ߘW4.1.3ߔW߯W4.1.5.13WW4.1.7ިW4.1.7.1KW4.2.4ߔW߯WWWߙWߣWߩW߶W߽WWWWWNW802.20-basedLWߋW903W920W95|W}WWWWWWWWWWWߍ 2004/07/13268g4532iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02ߍe at least on par with other existing systems out there.mAccepted 2004/07/02ߌ^Technical, Bindingd268g4532iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02ߍ^Technical, Bindingd268g4532iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02ߍ Sutivong, Tomcikj]Agreed. 802.20-based systems should be at least on par with other existing systems out there.mAccepted 2004/07/02ߌ^Technical, Bindingd268g4532iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02ߍsed systems should be at least on par with other existing systems out there.mAccepted 2004/07/02ߌ^Technical, Bindingd268g4532iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02ߍ^Technical, Bindingd268g4532iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/02ߍ 2004/07/02ߍd278g4533 2004/07/02ߦ 2004/07/13ߧ^Technical, Binding_15`19a4.1.7.1d183g4559i&Naguib, Sutivong, Tomcik, Yallapragadaj$Agreed, the word "moderate" is vaguemAccepted 2004/07/13ߨ^Technical, Binding_16`10a4.1.9d185g4560i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߩ^Technical, Binding_17`17a4.2.1d188g4561i&Naguib, Sutivong, Tomcik, YallapragadajRelevant references or information need to be provided to specify the blocking and selectivity requirements for 802.20 subscriber terminalsmAccepted 2004/07/13ߪ^Technical, Binding_17`25a4.2.2d189g4562i&Naguib, Sutivong, Tomcik, YallapragadajSThis section should be worded to be informative rather than specifying requirements 2004/07/13߫^Technical, Binding_17`25a4.2.2d190g4563i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13߬^Technical, Binding_18`1a4.2.3d191g4564 itomicik7WtomickFWTWbWwilson߸W߹WߺW߻W߼W߽W߾W߿WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWWWW W!W"W$W%W&W'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W=W>W?W@WAWBWCWDWEWFWGWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^WW<javoidyWbޮWb/s/hzeWbandsޣWbandwidthޣWwWbandwidthsqWbaseZWW WWbasedZWWbasisWbatteryWbcmcsNWbeIWPWQWeWgWހWދWޣWޤWޥWާW޷W޹WWWWWWWHWKWMW߀W߄WߋWߎWߞWߟWߡWߣWߩWߪW߳WߴWߵWWW3WFWNWwWWWWWWW WWWWbecomesUWbeen4W5WIW]WgWߘWWbefore@WZWWbeginWbelieveީW޹WWWbelowWbestޥW߄WbetterIWbetweenOWZW߽WNWWbitީWNWbits/sec/hz/sectorރWblockWblockingߩWborderOWbothߙWߣWW2WwWWWWbothbasestationandmobilestationshouldemploytransmitVbottomWbps/sectorWbreakWbroadband߶WWbroadcastWLWIXj978W<WEW_WcWWWa9WNWOWPWTWWWZWgWqWޣWާWީW޵W޷W޺WWWWWWW WHWUW߄WߙWWWWW W3WNWvWWWWW WabilityNWableW߄WߞWߴWabout޶WabstractߙWacceptLWކWkWaccepttheparagraphwiththefollowingchangereplaceincluLVacceptwithmodificationassuggestedinmycommentކVacceptableދWޣWWacceptedެW߀Waccess޷WW߄W߶WW WaccommodateߙWaccomodateqWaccordanceަWaccountߙWachieveWacrossQWWWWWactiveZW߄WactivityNWadaptationߣWwWadaptiveߣWwWaddNWPWYWWJWW2ߎ^Technical, Binding_17`29a4.2.3d7g4534i&Naguib, Sutivong, Tomcik, Yallapragadaj>The requirement for minimum delay spread needs to be specifiedk_Option 2 is preferable. Some sort of minimum requirement for delay spread should be specified.mRejected 2004/07/13ߏ^Technical, Binding_17`29a4.2.3d17g4535i&Naguib, Sutivong, Tomcik, YallapragadajDuplicate with Comment 7mRejected-Duplicate 2004/07/13ߐ^Technical, Binding_15`4a4.1.7.1d45g4536i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߑ^Technical, Binding_15`27a4.1.7.1d47g4537i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߒ^Technical, Binding_16`6a4.1.8d50g4538i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13ߓ^Technical, Binding_17`16a4.2d56g4539, YallapragadamAccepted 2004/07/02ߓ^Technical, Binding_17`16a4.2d56g4539daqjgThe standard should provide a scalable solution to accomodate deployment in various channel bandwidths.mAccepted-Modified 2004/07/13r^Technical, Binding_?`15a4.1.7d73g4250iAnna Teej:Please refer to C802.20-04-55 for the proposed resolution.kAOption 3 refers to an expired IETF draft for latency and error rate requirements. The IETF draft does not have clear requirements on latency and error rates, and it is mainly focus on requirements for the IP network. 802.20 standard's focus is mainly the wireless access network. mRejected 2004/07/13s^Technical, Binding_12`22a4.1.5.1d77g4251iAnna TeejSee reply to comment #3kSee reply to comment #3mRejected-Duplicate 2004/07/13t^Technical, Binding_14`16a4.1.7.1d80g4252iAnna TeejSee reply to comment #6kSee reply to comment #6mRejected-Duplicate 2004/07/13u^Technical, Binding_14`16a4.1.7.1d94g4253iAnna TeeRjwhy߂Wwhyis0.9chosenpleaseclarify߂VwillވWޡWޤWިWߓWߙWߣWWwWWwilldependonresolutionofothercommentspertainiongto4ިVwilldependonwhathappenstothetextonpage11iftheseޡVwirelessZW߄W߶WWwithLWTWZWeWyW{WWހWރWކWަW޺WWWWKWUW߀WߋWߏWߘW߽WW WFWNWlWvWWWWWWWn߄W߽WNWwithoutWwordߣWߧWwordedߪWwordingkWworkވWߝWworking4W5WIW]WdWߘWwould@WދWާWߙWwouldliketoseethepreviousdefinitionandreviewbefore@VwrittenOWwrongWwronglyQWwwwNW~Wk1AWhWkW"WWW W.W1WW1-1AW1.25 W1.3AWhW100%W101WWW111%W&W135GW138_W139AW140nWW ߄jAThe requirement on number of simultaneous active users is not clearly stated. For instance, are all 100 users supposed to be able to get a bearer channel within the specified time limit under all channel conditions and loading? Due to the random nature of the wireless channel, at best this requirement should be probabilistic in nature. Furthermore, rationales on number of users as well as access latency should be provided.mRejected 2004/07/13߅^Technical, Binding_12`22a4.1.5.1d77g4525iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/13߆^Technical, Binding_13`5a4.1.5.1d130g4526iNaguib, Sutivong, TomcikjAgreed.mAccepted 2004/07/13߇^Technical, Binding_14`9a4.1.7d136g4527iNaguib, Sutivong, TomcikjAgreed.mAccepted 2004/07/13߈^Technical, Binding_12`11a4.1.3d170g4528iNaguib, Sutivong, Tomcikaguib, Sutivong, Tomcik, Yallapragada 2004/07/02it4teegWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWހ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ߗ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ߵWIjsuggest4W5WOWSW]WߖWߣWsuggestremovingthemimoexampleSVsuggestedJW{WކW޷W߽WWsuggestionޣWsuggestsWsupercedesWsupply޵W޺WsupportNWxWހWެW޳WWLWߙWWWWW3WFWvWwWWWWsupported WWsupposed߄Wsure޶WsystemQWZWޘWޥWLWߝW߽WWW2W3WNWwWWWsystemsLW߀WߋW߶WWWtableIW3Wtable4-1containsvaluesthathavebeendebatedandapproveIVtahtރWtakeߙWtakingWtargets3WtaxedߙWtddߔWߙW߯WWtechnologyIWWtelematicswWWWtemplatesNWtemporaryZWtermLWWWޣWWterminalF7-joptio޲WoptionRWfWjWpWvW}W~WވWެWޮW޲W޳W޼W޽WWW1W߀WߝW߳W3WWoption2insec4.1.5.1specifieddatarateveryclosetospVoptionalދWoptions2WKWorZWzWވWޣWޥWUWߩW߽W3WLWNWvWzWWWWWWorg/internet-drafts~WoriginalWotherzWހWިWWKWߋWothersWotherwiseQWޥWoutQWWߋWߖWWWout-of-bandWarticularOWWpartitioningOWpartitioningisusedheretostressthattheborderbetweenOVpdfNWpeak߀WpedQWperWperformancegWߙWߞWߴWperiodicitiesߖWpertainiongިWphb~WphyOWߙWphy-specificߙWphysicalWpickedޮWpico-cellsgWpleasehWiWmWrWuW߂W߈Wpleaserefertoc802.20-04-55fortheproposedresolutionrVuVE_j"Same as comment 97- Reject CommentmRejected-Duplicate 2004/07/13`^Technical, Binding_11`5a4.1.1d276g4232iNaguib, Sutivong, TomcikmRejected-Duplicate 2004/07/13a^Technical, Binding_20`7a4.5.3d283g4233iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/13b^Technical, Binding_19`34a4.5.2d284g4234iNaguib, Sutivong, Tomickj$Same as comment 273 - Reject commentmRejected-Duplicate 2004/07/13c^Technical, Binding_20`15a4.5.4d285g4235iNaguib, Sutivong, Tomcikj"Same as comment 97- Reject CommentmRejected-Duplicate 2004/07/13d^ Editorial_8`17a3.1d286g4236iNaguib, Sutivong, Tomcikj5These were previously approved by working group vote.mAccepted 2004/07/13e^Technical, Binding_13`5a4.1.5.1d288g4237iNaguib, Sutivong, Tomcik4551 2004/07/020߷@5߸@ߺm߽bAg߾bAgcFbcAgAbcAgbBgbAg@mbbAgkbbAgbbAgEbkA ` kAc`mkAbA$g#cA&g%cA)g(F+i,cA0g/jA54m<;cACgBcAGgFjKkAONbAWAXgV c] iabAfgebAmgl^tbAwgvb~bEgG @!kA$b$b$b$b$b'Xk]We should keep more specific text. We think " shall support Voice over IP." is preferable.mRejected 2004/07/13Y^Technical, Binding_12`11a4.1.3d170g4225iNaguib, Sutivong, Tomcikj!Add Clarification to these terms.kmvarious levels of "coupling" are not defined in this document. They should be defined, or a reference given.mAccepted-Clarified 2004/07/13Z^Technical, Binding_19`26a4.5.1d204g4226jASame as a QC comment on the topic. A possible definition is based on CDMA as follows: "Soft Handoff: A handoff occurring while the mobile station in transmitting and receiving on a Traffic Channel. 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 mothe uplink and the downlink.Mw6jtherequirementforminimumdelayspreadneedstobespecifiߎVߟVߡV߳VߵVtherequirementonnumberofsimultaneousactiveusersisno߄Vtherequirementsonthedlandulpeakuserdataratesasst߀Vthesectionandtexthavebeenreviewedandvotedbythewor]Vthesentenceshouldthenbetheieee802.20standardformstVthestandardshouldprovideascalablesolutiontoaccomodatqVthesuggestedparaphrasecouldbeinterpretedtoimplythat޷VthesystemshallworkindenseߝVthetextchangeisokifthevalueischangedinaccordanceަVthetextforoption1wasproposedinjanuary'smeetingint~VtheirWWthemWthenޡWWther޷WthereWWߋWWthereisnothingwrongwiththepresenttextV߬i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13߭^Technical, Binding_18`18a4.2.3d193g4565i&Naguib, Sutivong, Tomcik, YallapragadajAgreedmAccepted 2004/07/13߮^Technical, Binding_18`3a4.2.3d194g4566i&Naguib, Sutivong, Tomcik, Yallapragada 2004/07/13߯^Technical, Binding_18`18a4.2.4d196g4567i&Naguib, Sutivong, Tomcik, YallapragadajoSection 4.1.3 already specifies the AI requirements on FDD and TDD frequency arrangements. Remove Section 4.2.4 2004/07/13߰^Technical, Binding_18`33a4.3d198g4568i&Naguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13߱^Technical, Binding_19`4a4.4.1d200g4569i&Naguib, Sutivong, Tomcik, Yallapragada 2004/07/13߲^Technical, Binding_19`16a4.4.1d202g4570iLNaguib, Sutivong, Tomcik, YallapragadaNaguib, Sutivong, Tomcik, YallapragadamAccepted 2004/07/13߳bjindicateީWindividual{WޤWWNWindividualoptimizationofeachproposalisallowedsub-layeVindoorWWindustryWinformation WߩWNWWinformativeUWߪWWWinitialWWWWWWWinportantީWinputsߓWinstance߄WinstantWinsteadWintegrityWintercept޹WinterfaceހW߶WWWWWinterfacesWinternallyWinterpretation޶Winterpreted޷WinterruptionsWintoߙWintuitiveWipހW߽WWNWWWsedKWipv4Wipv6Wis9W=WIWOWQWTWZWgWvWޘWޡWޣWޥWަWީWެW޲W޳W޶W޷W޺WWWWWWWWW WMW߂W߄W߉WߙWߣWߧW߹W߽W߾W߿WWWWWWW WWWWWWWis/wasޘWissue WWTjindicate@ip-based@it@*link@maintainasis@ maintainasispagenumbersalreadyappearinthedocument@maybe@qmetric@msap@name@not@nothing@ones@Foptio@outdoor@7paging@pleaserefertocontributionc802.20-04-55fortheproposed@probably@fproviding@rates@rejectthecomment@reliability@reply@review@sameasaqccommentonthetopicapossibledefinitionisb@see@ >dÃ)/ߪxÃ*0߫yÃ* 1߬Ã*0Ã*@2߭Ã*P3߮Ã*`Ã*p4߯Ã*5Ã*6߰ Ã*7 Ã18߱ঃ Ã1 9ৃÃ10߲Ã1@:ஃvjreliabilityߣWwWremedyJWyW{W޳WߙWߣW߽WOWremovalߞWߴWremovalofsectioncanonlyfutherconfusionindefiningqosߞVߴVremoveKWTWߔWߙW߯WWremoveip-basedfromthefirstsentenceKVremovethelastsentenceoftheproposedremedyߙVremovesWremovingSWrenamedWrepalceFWrepalcewithsupportforcertainapplicationsegvoiprequiFVreplaceLWW߽WW WlWWWreplacetextforthesectionwiththebasestationshouldprVreplacethefirsttwosentencesinsection4.3withthefollVreplacethetextinquestionwiththembwa802.20airinterfVreplacethetextwithaccesscontrolshallincludeauthentic Vreplacewithmulti-antennalVreplacewiththe802.20standardshalldefineacommonsetoVWlWrWuWިWߣWresourcesLWresultsWretainwWWretaintelematicswVV'[^ Editorial_18`24a4.2.6d224g4227j2Change "including but not limited to" to "such as"kReadability. Less jargon.mAccepted-Modified 2004/07/13\^Technical, Binding_20`8a4.5.3d252g4228 2004/07/13]^Technical, Binding_11`5a4.1.1d266g4229iNaguib, Sutivong, Tomcikjv The section and text have been reviewed and voted by the working gorup. Suggest not to change the text at this time.k.Text has been debated, and approved by the WG.mRejected 2004/07/13^^Technical, Binding_20`7a4.5.3d274g4230iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/13_^Technical, Binding_20`15a4.5.4d275g4231iNaguib, Sutivong, Tomcik20`7a4.5.3d274g4230iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/02_^Technical, Binding_20`15a4.5.4d275g4231iNaguib, Sutivong, TomcikjspecifyingߪW6?^technical߫W߬W߭W߮W߯W߰W߱W߲W߳WߴWߵW߷W߻W߾WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWWWWWWW!W"W#W$W%W&W'W(W)W*W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W>W?W@WAWBWDWEWFWGWHWIWKWLWMWNWOWPWQWRWVWWWYW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWkWnWoWqWsWtWuWwWxWyW{W|W}W~WWWWWWWWWWWWWWWWMjspecifyyWzWWߞWߩWߴWWW Wspecifyalistofchannelbwtobesupported VspecifyanalternativefairnesscriteriaegtheoneusedinzVspecifyingjsee9W@WJWhWkWlWmWnWsWtW|WށWނWރWމWލWޯWޱWWWWWWWWWWWW!W0WJWOWSWyW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWseecomment224forthealternativetext|V߶b{Change from "802.20 ...." to: "System Requirements for IEEE Standard 802.20 for Mobile Broadband Wireless Access Systems"cIncorrect titled159g2324jChange title to, "Requirements for IEEE 802.20 Radio Interface (MAC/PHY) Standard for Mobile Broadband Wireless Access Systems"k802.20 does not specify a full system, only the MAC/PHY aspects of the systems. This title better reflects the scope of the 802.20 standardsmAccepted-Modified 2004/07/13Marked4573i&Naguib, Sutivong, Tomcik, Yallapragadaj>The requirement for minimum delay spread needs to be specifiedmRejected 2004/07/02߶EEshwarF Pittampalli^ Editorial_0al, Bindingd282g4573i&Naguib, Sutivong, Tomcik, Yallapragadaj>The requirement for minimum delay spread needs to be specifiedmRejected 2004/07/02߶EEshwarF Pittampalli^ Editorial_0minimum delay spread needs to be specifiedmRejected 2004/07/02߶EEshwarF Pittampalli^ Editorial_0g4574 2004/07/025 ߷EEshwarF Pittampalli^Technical, Binding_19`26a4.5.1b(Define "soft handoff" and "hard handoff"c$"soft or hard handoffs.." not clear d204g2369i Joanne Wlsonjmaintain current textkA)The current text states that, "handoffs can be classified as either soft or hard handoffs, depending on whether there is a momentary service disruption or not." This text is informative and sufficient because there are no further requirements in this document related to how such are carried out.)mRejectednding_19`26a4.5.1b(Define "soft handoff" and "hard handoff"c$"soft or hard handoffs.." not clear d204g2369i Joanne Wlsonjmaintain current textkA)The current text states that, "handoffs can be classified as either soft or hard handoffs, depending on whether there is a momentary service disruption or not." This text is informative and sufficient because there are no further requirements in this document related to how such are carried out.)mRejected4dbwithތWޖWޚWޢWޤWަWީWޯWްWޱW޳W޵W޺WWWWWWWWWWWWWWWWWWWWWWWW W!W$W&W,W-W0W1W2W3W6W:WBWMWNWPWSWVW[WbWfWgWsW{W߻W߽W߾W߿WWWWWWWWWWWWWWWWWWWWWW W!W"W.W/W5W>WAWFWHWIWNWOWRWWWXWYW[W^W_WlWoWqWvWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWgwkoperatepWoperatingWoperationqWoperatorWoperatorsWopposedWoptionfWrW!W"W'W(WSWfWߎW#W$W.W/W1WZWWoption2ismorereasonableandrealistic$Voption2ispreferablesomesortofminimumrequirementforߎVoption2ispreferabletotherecommenderswhile5microseconfVoption3referstoanexpiredietfdraftforlatencyanderrrVoptionalWoptionallyWoptionsWWWorKWYWwW|WWW߷WWWWWW=WZWeWWWWrsWoutsideWoverKWXWoverarchingWoverlyWoverviewWownWkWpackets߽WWpageAWparhW߻WWWWWparagraphAWKWހWߙWparitallyWpartWWpartiallyWparticipantsNWparticularWparticularly1WpartitioningWpartitionsWpathW5߸EWarrenFSpringer^ Editorial_0`0a0bUUse mobile terminal. and base station only and no other abbreviations fd or tems... cAThroughout hte document, we use differnt captializations for B ase Stations, mobile terminal, Mobile Terminal, etc. We need to standardize for clarity and style. Also, in 4.1.9 Anntenna diversity, we use mobile station, no where defined or used any other placed206g2816i Joanne Wilsonk7Better to maintain consistency throughout the document.mAccepted 2004/07/13Marked߹EDougFKnisely^ Editorial_0`0a0cGlobal: Add page numbers!d109g2223i Joanne Wilsonj=maintain as is. Page numbers already appear in the document.mRejected 2004/07/13MarkedߺEDougFKnisely^ Editorial_0`0a0b; globally change "i.e." to "i.e., x"c7Global: "i.e." should always be followed by a comma. d120g2234i Joanne WilsonkEditorial correction4i Joanne WilsonkEditorial correction 2004/07/02/iklererރބޅކއވމފދތލގޏސޑޒޓޔޕޖޗޘޙޚޛޜޝޞޟޠޡޢޣޤޥަާިީުޫެޭޮޯްޱ޲޳޴޵޶޷޸޹޺޻޼޽޾޿ƒÃăŃƃǃȃɃʃ˃̃̓Ѓу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$h;khoweverAWSW=WihWWWWW!W"W$W&W'W(WNWfWkW߽WWWWWWEWWWWibelieveitisarequiredfeatureVibelievethe802.20systemshouldalsosupportroutingpack߽Vicangoeitherway&VicanlivewithorwithoutthattextVicanlivewiththevaguenessNVidonotcarewhattermweueaslongasweuseitconsistenVidonotunderstandthecomment$Vidon'tbelievethisiswhatisintendedbythesentencewhiV2tooption1"Vipreferoption3'V(VipreferthecommentofdangaltofixthisVieeejW}WietfrWifWWWW.W3W?WWifitmakesdoughappywhynotVifoption1isselectedthenitshouldbemodifiedperthis.Vill1Will-definedWimmediatelyWimpactWeWimplementationW^WpWWimplementationsWW qjmaintainasispagenumbersalreadyappearinthedocument߹Vmaintaincurrenttext߷VVVVVVVVVmaintaincurrenttextoneeditorialimprovementistoplural VmaintaincurrenttextwhichisinformativeVmaintenanceWmakeQWLWWmakingދWmakingitoptionalwouldbeacceptableދVmannerWmayޣW޹WWWWߣWWNWWWWWߺmAccepted 2004/07/13Marked߻EDougFKnisely^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.d98g2212i Joanne WilsonkAImprovement in the text since the PAR requirements are mandatory.mAccepted 2004/07/13Marked߼EDougFKnisely^ Editorial_5`6a1.1cadd comma after "standard"d99g2213i Joanne Wilsonk Editorial mAccepted 2004/07/13Marked߽EDougFKnisely^ Editorial_5`7a1.1bg4581 2004/07/02caߺWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWW$W'W+W.W/W0W1W2W4W5W6W9WAWHWIWLWPWQWVW\W]WgWhWjWtWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!W!}keditorialߺW߼WWWWWWWW WW>WCWXlmWpWrWzWWWWWeditorialandthechangedoesn'timpactthemeaningofthesVciencyAWWWWeither&W߷WWWWeitherisokayVemergencywWend-to-endހWWenhancingWensurevWWentirelyߙWenvironmentfWenvironmentspWequal7WerroriWrWuWessential|WestablishesWestablishingWetcwWethernetKWevaluationWWexanationAWexistingAWhWWWexpiredrWexplanationWWWexplanatoryWexplicitKWexpressesWextensiveWexternalWfeatureWWWWWfindWfirstAWހW%WfixWfixedWflexibilityjW}WWWWflowWfocusrWU߽g2214i Joanne WilsonjACUse the text of the first sentence of the suggested remedy. Replace the second sentence of the remedy with the following sentence, "The purpose of the 802.20 system is to route and/or relay packets (e.g., IP packets) between the external networks and the mobile stations or between mobile stations within an 802.20 system.C@A>  33 @ 33B  33>kAI believe the 802.20 system should also support routing packets between mobile stations within the 802.20 network to support applications that may require routing packets from one mobile to another mobile, e.g. applications such as gaming and VoIP between two 802.20 mobile stations.mAccepted-Modified 2004/07/13Marked߾EEshwarF Pittampalli^Technical, Binding_1`3a1.1bg4582 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 sentenced100n߾g2325i Joanne Wilsonjmaintain as iskThe suggested remedy is incorrect. This document provides the requirements of the 802.20 MAC/PHY and not the specification of the physical and medium access control layers....mRejected 2004/07/13Marked߿EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`4a1.1bWThis sentence shall read "These requirements shall be consistent with the approved PAR"cChange "are" to "shall be" and insert "approved" before PAR. Reason: proper user of requirement language and editorial change to make the section more succinct.d260g2211i Joanne Wilsonjmaintain as isk unnecessarymRejected 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`6a1.1bSChange Line 6 shall read: " ... for the 802.20 packet mobile wireless standard ..."g4584 2004/07/02 ߾bAReplace this sentence with "This document provides/defines the specification of physical and medium access control layers of an air interface for interoperable mobile broadband wireless access (MBWA) systems, operating in licentsed bands below 3.5 GHz, optimized for IP-data transport."c~The sentence beginning with "This document...." is not clear in defining the scope. It confuses the Standard with the System.d160dcrequirementsރWވWލWޒWިWޮW޺W޻WWWWWWWWWWWWWWWWCWGWQWRWUWWWXW^W`WaWdWeWkWtW߻WWWWWWWWWWW0W1W4WJWLWMWNWPWQWVW\WeWgWhWqWuWwW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWrespectތWޖWWWsW{WrespectivelyWGWWW4WrestWWrestored޵WWrestrictވWޒWWWLWPWQW\WrestrictiveW@WrestructureޤW WresultޅWޏWWmWvW$W'W+W6W9WresultsGW4WretainTWrevisedW1WrewordZWrewritten@WcThe text in C802.20-04-44 is somewhat different in this section. Modify to add clarification that 802.20 is a packet mobile wireless standard. d261g2212i Joanne Wilsonjmaintain as isk unnecessarymRejected 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`7a1.1bInsert the following sentence at this point: "It is further assumed that Layer-3 and above are standards-based IP architecture" This is an editorial change to make the section more succinctc"Remove text starting at line 7. Id262g2213i Joanne Wilsonjmaintain as isk/not necessary and out of scope of this documentmRejected 2004/07/13 2004/06/07MarkedEDougFKnisely^Technical, Non-binding_5`12a1.2b$Change "detailed" to "functional". cJThis document does not specify detailed requirements (whatever those are).d101g2215i Joanne Wilsonk more accuratemAccepted 2004/07/13MarkedEDougg4587 2004/07/02c802.20mechanismsnotclear8VV V802.20systemsshouldworkeffectivelywithbroadcast/multicVVV802.20'sW802.20'sworkisawkwardV9ްWGW4WXWWWWW953WWaރWބWޅWވWފWދWލWގWޏWޒWޔWޕWޝWޮW޹W޾WWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW-W>W?WBWGWKWLWMWNWSWVWWWYWZW[W`WfWhWkWlWmWqWrWtWuWvWzWWdIcdoesn'tWRWW{Wdon'tWWWdos WWdownline@WzWdownlinkރWބWލWގWWWWkWlWtWuWWWWWWWWWWWWWWWWWWWWWW WdrivenW1Wcdoesn't@duplexing@either@ensuringPentire@entireparagraphshouldbeinformativenotnormativethesea@FKnisely^Technical, Non-binding_5`15a1.2b"change "layer" to "ISO/OSI layers"c6Grammar and clarify what "layer" system is being used.d102g2216i Joanne Wilsonk%accurate and probably useful additionmAccepted 2004/07/13MarkedEEshwarF Pittampalli^ Editorial_1`13a1.2b5Delete lines 13-16 (Text beginning with 'How the...")c6Text begining on line with "How the..." is unncessary.d161g2326i Joanne WilsonjMaintain current textkLThe current text is useful for further clarifying the scope of this documentmRejected 2004/07/13MarkedEWarrenFSpringer^ Editorial_5`15a1.2b,potocol in layers 1 and 2 needs the plural cprotocol in layer 1 and 2d207g2817i Joanne Wilsonj!use, "protocol in layers 1 and 2"k editiorilamAccepted-Modified 2004/07/13MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`12a1.2g4590 2004/07/02kthecurrenttextisusefulforfurtherclarifyingthescopeVthecurrenttextstatesthathandoffscanbeclassifiedase߷VtheevaluationcriteriashoulddefinehowtomeasureaggregaVthefirstsentencehasalreadyimpliedtherestoftheparagހVthefirstsentenceisredundantwiththesecondthemodificaVthefirstsentencespeaksaboutbeingabletocontrolmoret%VthelastsentenceisarequirementtoensurethatanactivevVthelastsentenceofthesuggestedremedymaynotentirelydߙVthemaxchannelbandwidthwouldbeequaltothemaxblocksi7VthemultipliersareartificialGVthenewlyproposedtextisthoroughlyambiguousVqcanntenna<W߸Wansi-WWantennalWanyދWޕWWWWW WW4W<WTWcWqW߸WW0W@WWWWWWWWWWWWWWanythingWanywheredWeWWWWWappear,WoWappearantWW.W2WappearsWapplicableރWލWWkWtWWWWWWWWWWWapplicationsވWޒWWWWCWGW4W@WLWPWQW\WeWgWhWWWWWapproachދWޕWWWWOWqW1WfWWWWWWWWWappropriateވWޒWWWFWNWWIWLWPWQW\WgWhWWWapprovedRWdWeWgW߿W{WWWWWarbitraryވWޒWWWLWPWQW\WgWhWWWbnThe sentence should read " This document established the detailed requirements for the IEEE 802.20 Mobile ..."cDInsert "IEEE 802.20" before Mobile. This adds clarity to the text.d263g2215i Joanne Wilsonkimproves claritymAccepted 2004/07/13 2004/06/07MarkedEHariFGantiGMember^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.cg4591 2004/07/02joanneklmnopqrs678g༃Ńσjohnލގޏސޑޒޓޔޕޖ'()Q}ඃ࿃ȃكڃۃ܃݃ރ߃kazuhiro׃؃كڃۃ܃.Lฃ]breadilyWWBWWWWWWreal-timeW_Wreasonable-WWreceiveWWWWWWWWreceiver޺WqWWreceivingWWWWrecipient޹WWrecommendedW^WreconfigurableWWreduction@WvWzWreferenceޛWޫW޵WGWdWeWWW4WSWsWWWWWWreferencesުW9WWWWWreferred8WW WreflectOWfW 2004/07/13MarkedEDougFKnisely^ Editorial_5`20a1.3bChange "bases" to "basis"c wrong wordd103g2217i Joanne Wilsonk EditorialmAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_1`20a1.3breplace with "basis"c Typo "bases"d162g2327i Joanne Wilsonkeditorial correctionmAccepted 2004/07/13MarkedEEshwarF Pittampalli^ Editorial_1`20a1.3b+replace "802.20's work" with "the standard"c"802.20's work" is awkwardd163g2328iJoannekeditorial improvementmAccepted 2004/07/13MarkedEWarrenFSpringer^ Editorial_5`20a1.3b3bases becomes "basis" since "table" is the object. cNgrammical problem, "that the following table is presented as the bases ..... d208g2818i Joanne Wilsonkeditorial correctionmAccepted 2004/07/13MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_5`13a1.3g4596 2004/07/02 UcA1. 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 inBGtended 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.)5d71g gA1. 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 inBGtended 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.)5i Joanne WilsonkConsistent with the PARmAcceptedcmacވWޒWWWWWWCWVWXWZWWWLWPWQW\WeWgWhWWWWWWWWWWmac-textWWmac/phyފWޔWWWWrWzWWWWWWWWWW!Wmacro/micro/picoWWmade|WW WmaintainދWޕWWWqWWWWWWWWWmakeރWބWލWގWWWWWRWYWgWkWlWtWuW߿WWWWWWWWWWW.W2W{WWWWWWWWWWWW WWOWTWXW WmbpsGWmeaningޡWWWWWWW WW.Wmeaningful/WmeansވWޒWޣWWWWmeant޶WWW0WmeasuredbWmeasures)WmechanismދWޕWWWLWqWWmechanisms8WbReplace with the text provided in the Contribution Doc C802.20-04/44. There is consensus of a number of individuals on this text.c2Remove the text starting with "How the system ..."d264g2216i Joanne Wilsonjmaintain current textkRNot at all clear what text from C802.20-04/44 is being proposed as replaced text.mRejected 2004/07/13 2004/06/07MarkedEDanFGalGMember^ Editorial_7`3a2bCAdd "Figure 2-1. The Vision of Integrated MBWA" under the figure.cMissing "Figure 2-1" captiond21g2342i Joanne Wilsonk EditorialmAccepted 2004/07/13 2004/06/01Marked2-1EDougFKnisely^ Editorial_7`5a2b"work, home, and mobile"cg4598 2004/07/02vg2218i Joanne Wilsonk if it makes Doug happy, why not?mAccepted 2004/07/13MarkedEDougFKnisely^Technical, Non-binding_7`5a2bDelete "should" on line 5cWconnectionsWEEshwarF Pittampalli^Technical, Binding_7`8a2bAReplace "Mobile Terminal (MT)," "user device," "mobile device," "wireless MT," "mobile wide-area stations," and "CPE" with "Mobile Station"@A> 33|  33 33>c3Multiple names for "MT" A generic global comment.d164g2329i Joanne WilsonkImproves consistencymAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_7`8a2bAReplace with "The 802.20 AI shall support various vehicular mobility classes up to 250 km/h in a MAN environment and target spectral efficiencies, sustained data rates and number of active users that are significantly higher than achieved by the existing mobile systems."c:The sentence beginning with "The 802.20...)" is not clear.d165g2330i Joanne Wilsonj+maintain current text which is informative.kKThe proposed text is from the PAR and already appears in the prior section. 2004/07/02lmRejected 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_7`12a2b/Please clarify what exactly is the requirement.cLBest in class "overall network complexity" -- the requirement is not clear.d166g2331i Joanne WilsonkUNo remedy proposed. It is not clear what needs to be clarified in the current text.mRejected 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_8`10a2b%Replace it with "enablers to support"c,"air interface support to enable" not clear d167g2332i Joanne WilsonjtReplace the text in question with, "The MBWA 802.20 air interface shall support the provision of VoIP applications."kEClearer than either the existing text or that proposed in the commentmAccepted-Clarified 2004/07/13MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_7`15a2g4606 2004/07/02jreplynWsWtWށWނWލWޯWޱWWWWWWWWWWW0WLWOWRWSWTWUW[W\W]WbWcWdWkWyW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWreportingWreportsWrequestUWrequireWrequiredQWWWrequirementgWW߄W߉WߎWߟWߠWߡW߳WߵWNWWrequirementsNWޘW߀WߓWߔWߙWߞWߩWߪW߯WߴW߶WFWJWNWvWWrequiresާWWߓWFWrequiresfurtherdiscussionVrequirmentWrequirmentsWresolutioniWkWlWrWuWިWߣWresolvingNWresourceNWresourcesLWWrespectFWWrespectivelyWresultsWretainwWWretaintelematicswVVkclearerWclearerthaneithertheexistingtextorthatproposedinthVcombinationWcommenWcommentiWkWlWmWnWsWtWuW|WށWނWރWWW$W*W2W3WqWWWWWWW W WWWW#W%W&W.W5WAWGWMW_WnWqWxWyWWWWWWWWWWWWWWWWWWWWWWWWcomment35isnotrelatedtosection4.2.3VcommenterWcommentsW WKWWPWcommercial WsWcommonWWWcommonly>WcommunicatesWbThis section should read "The 802.20 AI should enable mobile terminals to inter-work with an IP core network. Applications shall conform to ... ..." cTFollow the text of C802.20-04-44. In our opinion it is clearer than what is there. d265g2217i Joanne Wilsonjmaintain current textkA*802.20 cannot place requirements on applications that are above layers 1 and 2. Appropriately, we can have a requirement on the air interface that it supports those applications that are compliant to open standards. Thus, the current text is clear and more appropriately worded than that proposed*mRejected 2004/07/13 2004/06/07MarkedEDougFKnisely^ Editorial_8`14a2.2bAdd period at end of sentence.c"Missing period at end of sentence.d108g2222kpurely an editorial correctionmAccepted 2004/07/13MarkedEDougFKnisely^Technical, Non-binding_8`14a2.2bg4608 2004/07/02@[binteractiveW_Winterconnectivity+WkWintereference޺WqWWinterfaceތWޖWWWWW WWWTWsW{W߽W߾WWWMWWWWWWWWWWWWWinterfacesތWޖWWWWWsW{W߽WWWWWWWWWWinterferenceWintermodulation޺WqWWinternallyWWWinteroperable߾Winteroperate޺WqWWinteroperationWWWinterruptionWWWintetrest޺WqWWintoޤW޺WWW WqWWWWWWintolerantW_Wintra&WOWintra-frequencyWipWWWWW9WVWXW[W\WiW߽WWWWWNWWWWWWWWWWip-basedWWip-data߾WipsecWWWWWWmrejected-duplicate46789:;WWthoughaneditorialchangethisiscommonlyreferredtoasa>VuWvW|W}WހWށWނWWWWW WWW W"W%W7WKW߷W߸W߽WWWWWWWWWWWWWWWWWWWtobeconsistentwiththearchitectureofieee802standardsjV}VtodayAWtooWtrafficKWWtransportingWtrivialWtsWtwo߽WtyingWtypepWtypesKWueWultimateWunderpWunderminesW3bAdd "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.d113g2227i Joanne WilsonkThis proposed requirement is more detailed than necessary. We should let proponents propose how they would support this requirement and which protocols they support.mRejected 2004/07/13MarkedEDougFKnisely^Technical, Binding_8`14a2.2bg4612 2004/07/02{,kprotocolsWprovideWWWWprovided;W*WproviderWproviderspWprovides߾WWWWWprovidingWprovision Wprovisions Wpruposes|WpurelyWpurelyaneditorialcorrectionVpurposeWWpurposesWqosހWWWEWWqualityWquestionkWWWquotedWradioWrangewWratehWiWrWuWWW*WWWYWvWratesrW"W3W=WrationalWreadability[Wzg2228i Joanne Wilsonjmaintain current textk4This is more detailed than needed for this section.mRejected 2004/07/13MarkedEDougFKnisely^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.d115g2229i Joanne Wilsonk:This is more detailed than what is needed in this section.mRejected 2004/07/13MarkedEAnnaFTeeGMember^ Editorial_8`14a2.2g4614 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.Ed114RTbprovidethereferencestootheripnetworkstandardsandip9VVV\cisWWWWWWWWWWWWW WWWWWWWWWW!W#W$W&W'W)W+W-W.W/W0W1W2W3W4W6W8W9W;W?W@WDWGWHWIWLWMWPWQWSWVW\WeWfWgWhWiWnWqWzW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWWWWW!WbUse the proposed version in the Joint contribution: C802.20-04/44, quoted as follows: "IEEE 802.20-based systems shall support broadcast and multicast services using mechanisms that make efficient use of system resources."c.Need further clarification on the requirement.d217g2212i Joanne WilsonkAAThis appears to be a requirement on operators of 802.20-based systems to deploy a particular technology. Such a requirement is beyond the scope of this document. We can only place requirements on the aspects (layers 1 and 2) of the 802.20 air interface that we are specifying and not on the systems based that standard.AmRejected 2004/07/13 2004/06/08MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_8`13a2.2bg4615 2004/07/02g2470i Joanne Wilsonjmaintain current textkNo need to limit the how proponents propose to support this feature. Also, there are too many arbitrary assumptions required to get to a spectral efficiency goal specifically for the broadcast service.mRejectedyAAd hoc - lead by Mark Klerer. Following are the notes: ISSUES Requirement shall vs should in first sentence Definition of Appropriate Metric Spectral Efficiency as metric with assumption that wrap-around occurs with all broadcast channels on same frequency allocation (i.e. best case) How does or should this work for multicast How is spectral efficiency impacted by different types of broadcast traffic Broadcast alternate assumptions 1 Same information available from every cell (andB synchronized ?) 2 Information may not always be in the same band 3 No requirement for prior communication with the mobile for access to broadcast information ?  2004/07/13 2004/06/07Markedg4616 2004/07/02 bAChange to read: "IEEE 802.20-based systems shall support broadcast and multicast services using mechanisms that make efficient use of system resources. The minimum spectral efficiency provided by an 802.20 system while providing broadcast shall be (TBD).cThe requirement as previously written allows broadcast via unicast. 802.20 Air Interface systems should support a more efficient broadcast mechanism. The addition of a spectral efficiency number seems to be an easy way to preclude broadcast by unicast.d226EDougFKnisely^ Editorial_13`20a20bAThe 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 qbcClarify wording.d132g2247i Joanne Wilsonkeditorial improvementmAccepted 2004/07/13MarkedEDanFGalGMember^Technical, Binding_8`17a3.1b(Change "must" in lines 17, 18 to "shall"c!Inadequate "must" in lines 17, 18d22g2344i Joanne WilsonjA,Change to, "The 802.20 systems must be shall support the designed to of networks that provide ubiquitous mobile broadband wireless access in a cellular architecture (e.g. macro/micro/Pico cells). The 802.20 system must shall support non-line of sight outdoor to indoor scenarios and indoor coverage. ,@A   33  33&  33'  338  33?  33D  33E  33U  33  33  33  33  33k 2004/07/02 b.   2004/07/13 2004/06/01MarkedEDanFGalGMember^ 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.d23g2362i Joanne Wilsonkeditorial improvementmAccepted 2004/07/13 2004/06/01Marked3-1EDougFKnisely^Technical, Non-binding_9`4a3.1bA"The AI shall supports..."@Af  33  33   33 @ 33  33fc Not testable; not a requirement.d116g2230i Joanne Wilsonjmaintain as iskthough this is not a testable performance requirement, it is an observable requirement on the design of the 802.20 air interfacemRejected 2004/07/13MarkedEDougFKnisely^Technical, Non-binding_9g4620 2004/07/02 (kAIn the Overview of this document it states that, "For the purpose of this document, an "802.20 system" constitutes an 802.20 MAC and PHY implementation in which at least one Mobile 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 layers. " So, this requirement is actually that the 802.20 system can be deployed as a network that provides mobile broadband wBireless access.mAccepted-ModifiedHb18ޘWޡWWW19ޙW޾WWWWWonbaddadefinitionforsimpleip\VVVaddanewsentencebeforechannelbandwidthsinline33theVVVaddasentenceonline3thescalingfactortobeassumedfoާV?Vaddafterline2 VVaddafterqosVVaddapplicableafterotherthechangedtextwouldbeinconjޚVVaddfigure2-1thevisionofintegratedmbwaunderthefigurޗVVVaddnewtextinline15seeadditionalrequirementsinsectiިVJVaddonline19implementationsmaysupporteithermodefddo޾VVVaddperiodatendofsentenceVVV2jmaintainasis߾V߿VVVV`6a3.1bDelete "bursty ".c`Need to support non-bursty traffic as well. Bursty case is clearly covered by rest of sentence.d117g2231i Joanne Wilsonk>agree that bursty and non-bursty traffic needs to be supportedmAccepted 2004/07/13MarkedEDougFKnisely^Technical, Binding_9`7a3.1byDelete "The 802.20 AI shall support high-speed mobility." Alternatively, define speed requirements for mobility clearly.cNot defined; untestable.d118g2232i Joanne Wilsonk"Already covered in the PAR anyway.mAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_8`19a3.1bNReplace it with "support non-line of sight outdoor and indoor coverage areas."c*"support non-line of sight...." ambiguousd168g2333i Joanne Wilsonk 2004/07/02Jkanother߽WantennapWanyWW!W1WanywayWappear=WappearsWWWWappendixWapplicableWapplicationshWwWW߽WWWvWappliesWapproachWappropriateWWWWWWappropriatecompletionofthesentenceVappropriatelyWWWapprovedIW]WarbitraryWarchitecturejW}WWjWWarchitectures2WareYWiWuWwW|WWWGW߷W߻WWWWWWW"W*W3WfWoWqWsWwWWWWWWarea!WartificialGW 2004/07/13MarkedEAnnaFTeeGMember^ Editorial_8`17a3.1bA%"The 802.20 systems must be specified to enable ubiquitous mobile broadband wireless access in a cellular architecture, including but not limited to macro, micro, pico cells. The 802.20 system must support coverage in line-of-sight , non-line-of-sight, outdoor to indoor and indoor scenarios."%cwOne of the factors that would determine if 802.20 could be ubiquitous depend on how widely the technology is deployed. d218g2213i Joanne Wilsonk&See reply to comment #22 in record #44m Superceded 2004/07/13 2004/06/08MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_8`18a3.1b replace with the following text from the joing contribution "The 802.20-based system shall provide mobile broadband wireless access in an architecture consisting of macrocells, microcells, and picocells" g4624 2004/07/02  kAdThe proposed text could be interpreted as the support of pico cells that could be deployed indoors to provide indoor coverage. The requirement is to be able to provide seamless coverage outdoors, moving from outdoors to indoors and indoors from the same macro-cell that is deployed outdoors. I believe the current text uses accepted industry terminology.dmRejected?hariɃʃ˃̃ǃ@KjimLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjW|}~߿WWWWWWWWW5W<=HWIWfWnWtW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW@UkcouplingYWcoverageWW!WWcoveredWWcreatingqWcriteriaWW?WcurrentW߷WWWWWWW WWW!W5W>WWWcurrently!WWdefinitionWdefinitionsWdefinitionsshouldbeconsistentwithindustryuseandapproVdefinitley:WdegradeWdelayfWߎWdeletingWdemonstratedWdenisWdepending߷WdeployWdeployedwWWWdescribeߙWdescribedWdesignWWdesiredWdetailWWdetailedWWWWdevelopedWWdevelopingWdevelopmentWdevicesWWdictionaryWdifferentWdisagreeWdisagreethatthecurrentphase2requirementsarerealisticVdiscussionWdisruption߷WdividesWdoW$W6WdocumentNWYW߷W߸W߾WWWWWWWWWWWWcXRemove the sentence starting with "The 802.20" and replace with text from C802.20-04-44.d231g2219i Joanne Wilsonk&See reply to comment #22 in record #44m Superceded 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_8`17a3.1bHThe sentence should read " The 802.20-based systems shall provide ...." cXInsert based after 802.20 document 04-44. This corrects the requirements language used.d232g2218i Joanne Wilsonk&See reply to comment #22 in record #44m Superceded 2004/07/13 2004/06/07MarkedEJimFRagsdaleGMember^ Editorial_8`17a3.1b change to: "802.20 systems are intended to provide ubiquitous mobile broadband wireless access in a cellular architecture (e.g.macro/micro/pico cells). cAdopted changes were not made, d286g2252iJoanne 'Wilsonk&See reply to comment #22 in record #44m Superceded 2004/07/13MarkedEDanFGalGMember^Technical, Non-binding_92`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" d24g2363i Joanne WilsonkagreemAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^ 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.1d25g2364i Joanne Wilsonjadopt proposal, if possible. I believe that the "Figure 1..." is part of the imported image and it may not be possible to delete it. 2004/07/02:cipW9WXW[W\WWWWWWWWip-dataވWޒWWWLWPWQW\WgWhWWWWW[WWWipv6WW[WWWirrelevantފWޔWWWrWzWWWWWWWisރWޅWއWވWމWފWލWޏWޑWޒWޓWޔWޚWޠWޡWޢWާWޫWޮW޴W޶W޹W޺W޿WWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWWW W"W%W-W1W4W7W:W=W>W@WAWBWCWEWFWGWMWNWOWTWWWXWYWZW[W\W]W_W`WbWcWdWeWhWkWmWoWpWrWtWvWxWyWzW߾WWWWWWWWWWWWWW[ijoannewlson߷VPmAccepted-Modified 2004/07/13 2004/06/01MarkedEDanFGalGMember^ Editorial_10`1a3.1.1b"Change " Figure 2" to "Figure 3-2"c Incorrect reference to Figure 2.d26g2365i Joanne WilsonkagreemAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^Technical, Binding_10`1a3.1.1bAInsert the following text in line 1, before "Figure 2...." "If more than one PHY technology is adopted for the 802.20 standard, the MAC layer shall be designed such that it consists of two parts: a common part and a PHY-specific part. To provide the best possible performance, the PHY-specific part of the MAC may be optimized for the specific characteristics of a particular PHY. "cBReflect the proposal for common MAC in contribution C802.20-04-46.d66g2425iJoanne Wilson, Mike Youssefmirk 2004/07/02 b1addacaptioninline4table4-2blockassignmentsizesޟVV1addfigure3-1serviceattributesofmbwasystemsޙVVV1changeoption1line2-3tosystemarchetecturedatarateV.V1changetheheadingof4.2.1torfrequirements޺VqVV1changetheheadingofsection4.1.5todataratesdownlinkޤV V1deletethetableޥV*V1line2-3ismodifiedtothesepeakdataratetargetsareiV2V1.2ޥW*W1.25!WGW"W4WW1.5!W~W"W=W1.6GW4WW10ޛWWGWW4W^WW10-8W_W100ާWWWW?W@WW100msAWW10e-1W^W10e-8W^W11ޞWW12ޥWW!WW"W*W128kbpsW0W3W13WW13-16WW15ިW޵WWJW17ޘWޡWWWqqbnextWWnoW<W߸WWnoise޻WuWWWnon-discriminatory-WWnon-lineW}WW<Wnon-line-of-sightEWWnot޺WWWWWWWWW WWEWIWߺWWWWWWDW_WpWqWWWWWWWW WWobject=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߾WWWWWWWWWWWWWWWWWWWWWWWWW W W WijoannewilsonVVVVVVVVVVVVVVVVVV V V V V VVVVVVVVVVVVVVVV V"V$V%V&V'V(V)V*V+V,V-V.V/V1V2V3V4V5V6V7V8V9V:V;V=V>V?V@VAVBVCVDVEVFVGVIVJVKVLVMVWVXVYVZV\V]VhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV|V}V~VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV$ 2004/07/13 2004/06/04MarkedEDougFKnisely^ 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.d119g2233i Joanne WilsonkSince the requirements document proceeds the development of the standard, it is appropriate for it to be written in future tensemRejected 2004/07/13MarkedEDougFKnisely^ Editorial_9`14a3.1.1b#change "PPP, MPLS" to "PPP or MPLS"cGrammard121g2236i Joanne Wilsonkeither is okaymAccepted 2004/07/13MarkedEDougFKnisely^Technical, Non-binding_9`16a3.1.1bDelete "partitioning"cwhat is a "partitioning model?"d122g2237i Joanne WilsonkIt doesn't matter. Obviously, a "partitioning model" divides (or partitions) the functionality to various layers. But, either wording is okay.mAccepted 2004/07/13MarkedEDougFKnisely^Technical, Non-binding_9`18a3.1.1bg4634 2004/07/02 kAThe working group has not adopted a policy of developing a common MAC that supports multiple PHYs. No one has demonstrated that this provides any performance benefits and it undermines the ability to ensure interoperability between different 802.20 network implementations. Such an approach may be acceptable for fixed wireless access systems, but it undermines the ability of mobile terminal devices to roam between different 802.20 compliant mobile systems.mRejectedH2\badvanced޴WIWiWpWadvancementsWWWafWWaffect޽WWWafterޚWޝWީWޯWޱWWWW WWWWW.W2WRWWWYW^WWWWagainstW W>WW WWaggregateޣWޤWWWW WaggregationWaiޟW޴W޹WWWWWWWWWWFWGWbWWWWWWWWWWW3W4WMWiWvWwWWWWWai's޷Wai802.20MWbadvanced@air@2alternativelyrewritetoclarifyintent@Zand@G0and/or@applicationstheaishallsupportapplicationsthatconform@approved@areas@/asq'asproposedincontributionc802.20-04/55@ZDijoannewilson߸V߹VߺV߻V߼V߽V߾V߿VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV^@knoneedtolimitthehowproponentsproposetosupportthisVnoproposalprovided;Vnoremedyproposedforanon-specifiedproblem`VaVnoremedyproposeditisnotclearwhatneedstobeclarifieVnotextremedyproposedonlyaquestionforconsiderationkVnowirelesscouldincludeunlicensedorfixedsystemscellulVnon-burstyWnon-mandatoryWnon-specified`WaWnormativewWWWtVnumberWWnumbers WobjectivesWobservableWWobviousW%WobviouslyWWofAWKWNWYWhWjWpWwW}WހWWWWWWWW WߎWߙWߥW߶W߾WWWWWWWWWWWWWWokayWWonrW|WW WW2W3W߷WWWWWWon-lineWoneSWWW߽WWWonlyAWSWW߶WWopenWTekdoesrWW߶WfWWWdoesn'tWW5W=WdoingeWdon'tWeWWdone WdosWdougWdownWdownlinkWdraftrWdroppedvWWdsWduplexingWduplicateqWehWwWWW߽WWWWeachW3WeasilyWeditiorila2murakami׃؃كڃۃ܃.LฃnaguibLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjW߿WWWWWWWWW5WHWIWfWnWtW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW$&Bg2238i Joanne Wilsonjmaintain current textkThough this is not a testable performance requirement, it is a requirement on the structure of the design and it is observable.mRejected 2004/07/13MarkedEDougFKnisely^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).d124g2239i Joanne Wilsonjchange to "will specify"kPshould be written in future tense to be consistent with the rest of the documentmAccepted-Modified 2004/07/13MarkedEToddFChauvinGMember^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. cg4636 2004/07/02# 2bAThe 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.d123&)g2252iJoanne Wilson, Mike Youssefmirkagree with commentmAccepted 2004/07/13MarkedEToddFChauvin^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.d2g2253iJoanne Wilson, MIke YoussefmirmAccepted 2004/07/13MarkedEJohnFChenGMember^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. cg4638 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.d1 } cbtheWWWWWWWWWWWWWWWW W WWWWWWWWWWWWW W*W.W0W1W3W4W5W<W?WAWBWDWFWIWMWNWSW[W^W_WfWiWkWlWmWnWoWpWqWuWvWwWyWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWW W)+g2252iJoanne Wilson, MIke YoussefmirmAccepted-Duplicate 2004/07/13MarkedEJohnFChen^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.d12g2253iJoanne Wilson, Mike YoussefmirmAccepted-Duplicate 2004/07/13MarkedEDanFGalGMember^ Editorial_11`10a4.1.1b%Insert a space character after "(Hz)"c%Insert a space character after "(Hz)"d27g2366i Joanne Wilsonkeditorial and trivialmAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^ Editorial_12`1a4.1.1b+Move Table 4-1 caption to page 11, line 23.c9The "Table 4-1" caption should be placed above the table.d28g2367i Joanne Wilsonk editorialmAccepted 2004/07/13 2004/06/01MarkedEMarc2%( 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.d11;csentece?WWsentececonstructionneedssomemodificationacommaneedst?VVsentenceޡW޶WWWWWWWWWWW,W4WPWTWXW]WbWcW߽W߾WWWWWWW WWBWDWjWoWWWWWWWWWWWWWW W WW(,FGoldburg^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.d75g2683 2004/07/02+0iJoanne Wilson, Mike YoussefmirmAccepted-Duplicate 2004/07/13MarkedEMarcFGoldburg^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.d76g2684iJoanne Wilson, Mike Youssefmirkagree with commentermAccepted-Duplicate 2004/07/13MarkedEMarkFKlerer^Technical, Binding_11`5a4.1.1bgMake Table 4-1 consistent with the PAR and specify a downlink spectral efficiency of 1 b/s/Hz/sector .cg4644 2004/07/02 €marked  !"#$%&'()*+,-./0123456789:;=>?@ABCDEFGIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz|}~ࠃࡃࢃࣃःृঃৃਃ੃ઃૃଃୃஃ௃ఃృಃೃഃൃඃසฃใ຃ໃ༃གྷྃ࿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃EU8cofferedUWWWolderGW4WW05>g2700i Joanne Wilsonkagree with the commentsmAccepted 2004/07/13Marked4-1EDougFKnisely^ 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.d125g2240iJoanne Wilson, Mike Youssefmirj 2004/07/02,/ cATable 4.1 specifies a downlink spectral efficiency of 2.0 b/s/Hz/sector at 3 kmph and 1.5 b/s/Hz/sector at 120 kmph and uplink spectral efficiencies of 1.0 and 0.75 b/s/Hz/sector respectively. It is the intent to specify spectral efficiencies that are achievable in actual deployment in the timeframe of the PARs effecftivenes. For full mobility and small form-factor portable devices I do not believe that these targets are realistic. Operators are making commitments to deploy systems in the Btimeframe of the 802.20 PAR that have performance that is significantly lower than the 1 b/s/Hz/sector specified in the PAR. In light of the deployment evidence, there have been no convincing arguments that prove that systems meeting the PAR targets are not needed. Furthermore the process of developing the specification will assure that submitters provide their best possible designs in order to gain WG acceptance of their proposal. d91bspecify2bits/sec/hzasthespectralefficiencyandallowtkVtVVVVVspecify2bits/sec/hz/sectorasthespectralefficiencyandރVލVVVVVVVVspecifyassociationofenvironmentswiththeappropriatechaVspecifymaximumchannelbandwidth7VV Vspecifywhatmechanismsarebeingreferredtointhissenten8VV Vspecifywhatmetricsarebeingmeasured5VVcform-factorWformalYWWWformatKWWforwarding(WbWfragmentWWframeGW4WWframesދWޕWWWqWWWWWWWWWframeworkފWޔWWWrWzWWWWWWWWW!WfromވWޒWޛWWWPWXWWWLWPWQW\WgWhWtWWWWWfullWAWWfullyWWfunction`WWfunctionalTWWfurtherCWDWGWW4WeWWWfurtherclarificationonthetextVfurthermoreވWޒWWWWLWPWQW\WgWhWWWfutureWBWWWfwiwWWgWWWDW WgainWgenerallyWWgenerationGW4WWgenericWYWWWWctable-likeްWXWWtaggingދWޕWWWqWWWWWWWWWtargetedWWtargetsCWWeWtbr޼W~WWtcpވWޒWWWLWPWQW\WgWhWWWtddW4WWWtdmaWW.W2WtechnicalWWtechniquecWWtechniquesW]WwWWWWologies޵WWW WWW!W1WtechnologyދWޕWWWWEWGWqWW1W4WWWWWWWWWWWteeth'WaWtelematicsWWtellsOWfWtendެWTWtenseWWterm޴W޿W\W_WiWWWWWWterminalފWޔWWWW<WrWzW߸WW WWWWWWWWWterminalsW$WWFWterminology termsWW4WwWWWW5< 2004/07/13MarkedEDougFKnisely^ Editorial_11`16a4.1.1bchange "QoS' to "QoS,"c Missing commad126g2241i Joanne Wilsonk EditorialmAccepted 2004/07/13MarkedEDougFKnisely^Technical, Binding_11`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.d127g2242i Joanne WilsonkABy deleting this text it could be interpreted that the spectral efficiency will remain constant at higher speeds. Obviously, this is not the case and should not be implied. I don't think its necessary to define "degrade gracefully." We can see how the various proposals will perform through the evaluation process and should therefore be able to predict how the ultimate 802.20 standard will perform. In any case, the spectral efficiency is likely to degrade in some manner at higher speedBs./4 jAKUse the following, "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 throughput per sector (bps/sector), divided by the spectrum block assignment size (in Hz)( taking out excluding all PHY/MAC layer overhead)."K@A   33  33  33  33  33  33$  33-  33:  33@  33k|The evaluation criteria should define how to measure aggregate throughput per sector. Thus, the current text is sufficient.mAccepted-Modifiedrdij0.9߂W012004NW19WNWeWkW~WރWލWާWެW޼WLW߀WWW3WWWWWjoutdoorWWover-the-airWoverheadWpacketߞWߴWNWpackets߽WpageޡWW߹WWpagenumberisatbottomrightcornermovepagenumbertoboVersWNWWparaphrase޷WWparetial޶WpartެWߝWWSWparticipatingNWparticularOWWpartitioningOWpartitioningisusedheretostressthattheborderbetweenOVpdfNWpeak߀W3WpedQWpedestrianWperWRWTWUW[W]WbWcWdWWWperpreviouscommentsproposetodeletesection4.2.6VperfomancevWperformWperformancegWߙWߞWߴWzWWWperiodicitiesߖWpertainiongިWphb~WphyOWߙWNWphy-specificߙWphy/macWWphysicalWpickedޮWpico-cellsgWpleasehWiWmWrWuW߂W߈Wpleaserefertoc802.20-04-55fortheproposedresolutionrVuVkshouldbewritteninfuturetensetobeconsistentwiththeVshouldnotdefineperformancerequirementsforonlyasubset2VshouldnotprovideanexhaustivelistofthemeasurementstoVsignificantlyhWsimilarWsinceKW߻WW"W1W_WqWsWsince802.20isnotestablishingrequirementsonthechannel"VsincetherequirementsdocumentproceedsthedevelopmentofVsingleW*WsituationwWsize7WWsoAWW>WeWWsoft߷WsolutionWfWWsolutionsWsomeLWwW|W WߎWWIWsomethingWsortWߎWsourceWspaceW3WspecifyingWspectralAWWWW*Wspectrum*WspeedsWspirit WspreadfWߎWspreadsfWsrdpWstandardAWhWހWWWWW!W4Wstandard'srWstandardshWiWjWuW}W߶WWstatementW W!W=kissueWfcmissingcaptionunderthefigureޙVVVmissingcommaVVmissingfigure2-1captionޗVVVmissingperiodatendofsentenceVVVmissingtablecaptionޟVVmitigate>W WmobileWWWW<WOWXW[WhWjW߸WWWWWWW W]WfWWWmobileipv4[WWmobileipv6[WWmobilesWmobilityWXWWWWmodelWWmodelsWmoderate*WdWmoderatedelaymoderatedatalossrateambiguous*VdVmodification?WWmodifiedW߻WWmodifyhWWmore޻WWWWLWgW߿WWDW_WuWWW WmostWWWWmostofthistextisnotmac-textsomeshouldbemovedto4.VVmovedWWmovementXWWmoviesGW4WWmpeg-2GW4WW<Cs 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_11`21a4.1.1bReplace "should" with "may"c6"should" implies a required feature which is not true.d169g2334i Joanne WilsonkShould actually implies are desired but non-mandatory feature. In this case, "may" is better because this described allowed though certainly not desired performance.mAccepted 2004/07/13MarkedEJoanneFWilsonGMember^Technical, Binding_11`5a4.1.1bSpecify 2 bits/sec/Hz as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved.cg4649 2004/07/024;mRejected 9jkisWWWWW W W WWWWW!W"W#W$W*W.W1W3W4W5W=W>W?WEWNWVWWWYW^WoWpWqWtWvWWWWWWWWWWWWWWWWWWWWWWWW <kintheoverviewofthisdocumentitstatesthatforthepurpVinadeaquateWinappropriateWtWincludewW*WWincludedAWWqWincludingpWincompleteeWqWinconsistentWincorporatedWincorrect߾Wincreasing=WindicatedWindividualpWindoorWindoorsWindustryNWWWinformationAWinformativeKW߷WWWwWWWWinitialWqWinstead3W^WqWwWWintegrity WintendedW WoWWinterimWinternallyWinteroperabilityWinterpretEWinterpretedWWintovWހWWintroductionWipXWrWހWWip-basedKWހWisAWSWXWfWpWrWvWwWހWWWWWWW:WqWߎW߷W߾WWWWWWWWWWWWWWWWWWWWWkc802.20-04-55iWuWc802.20-04/44Wc802.20-04/55eWcalculation*WcallvWcanAWSWfWhWWWW&WNWSW߷WWWWW!W4WEWWWWWcannotestablishrequirementsontheimplementationonlyonVcannotWcapabilityhWcapacityWW%WcareWcarriedKW߷WcaseWWcasesWcell!WcellsWcellularhW6WWcertainly WWWchangeLWW>WWWWchangedwWWchangedthetextfrombeinginformativetonormativeandremVchangesߥW WchannelpWW W7WW"W*W1WWWWcharacteristicWeWclarifiedWWclarifiedtextVclarifyingWclarityߥWWW WWWWclassWclassesWclassified߷WclearpWrWWWWW"WWWWW _knotSWYWrWvWWWWWW$W:WߙW߶W߷W߾WWWWWWWWWWWWWWW"W#W*W2W?WNW^WfWjWoWpWqWsWtWwWWWWWWWWWWWWWWWobjectivesWobservableWWobviousW%WobviouslyWWofAWKWNWYWhWjWpWwW}WހWWWWWWWW WߎWߙWߥW߶W߾WWWWWWWWWWWWWWWW W W WWWWWWW!WoffsWokayWWWokaywordingVonrW|WW WW2W3W߷WWWWWWWW!W"W*Won-lineWoneSWWW߽WWWonlyAWSWW߶WWopenWkthoughthisisnotatestableperformancerequirementitisVVthroughWWthroughout߸WthroughputWWthrow WthusWWWtime4WsWWtimes*Wtitle߶WtoAWKWfWiWjWkWnWpWrWsWtWuWvW|W}WހWށWނWWWWW WWW W"W%W7WKW߷W߸W߽WWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W%W&W*W0W3W4W5W=W>W?WAWEWGWSWVWZWjWnWoWpWvWwWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsWCGg2233iMike YoussefmirmAccepted-Duplicate 2004/07/13MarkedEJoanneFWilson^Technical, Binding_11`5a4.1.1b6Remove the distinction between uplink and downlink. cThe 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.d267g2234iMike YoussefmirmAccepted-Duplicate 2004/07/13EMichaelF YoussefmirGMember^Technical, Binding_11`5a4.1.1bSpecify 2 bits/sec/Hz as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved. cg4651 2004/07/02;B 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.d266xcusage޹WWWWuseދWޕWޮWWW<W>WAWRWUWqW߸W WAWVW{WWWWWWWWWWWWWusedވWޒWWWWW W<WAWQW_W߸WWW!WLWPWQW\WgWhWwWWWWWWgWmWrWvWzW߿W$W'W+W.W0W2W3W4W6W9WOWuser's>W WusersW0WAWusingWusually_Wv12fW5Wv13fW5WvagueޚWWWWvagueqosneedmorespecifityVvalueWWWWvariousCWWvaryUWversion޵WWversusރWބWލWގWWWkWlWtWuWWWWWWWWWWWveryރWލWWWWCWFWkWtWWWWWWW.W2WviaLWWvideoGW4W.cofWWWWW W W W WWWW W!W$W%W&W'W(W)W+W,W-W.W0W1W2W3W4W5W6W7W8W9W:W;WAWLWPWQWRWZW[W\WeWfWgWhWoWtWuWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!WGKTg2252i Joanne WilsonkGthe spectral efficiency requirement is ill-defined and overly stringentmAccepted-Duplicate 2004/07/13MarkedEMichaelF Youssefmir^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.d277g2253i Joanne WilsonkagreemAccepted-Duplicate 2004/07/13EWarrenFSpringer^ Editorial_16`30a 4.1.1.11.2bnthe line should read traffic, as well as signaling messages from unauthorized modification, will be specified.c_sentece construction needs some modification ... a comma needs to be added to increase clarity d212g2822i Joanne Wilson 2004/07/02BF 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.d276cspecifityWWspecify޳WWCWWWWW3W[WeWWWWspecs-manshipޅWޏWWmWvW$W'W+W6W9WWWspectralރWބWލWގWޣWޥWWWWWLWRWkWlWtWuWWWWWWWWWWWWWWW*W0W{WWWWWWWWWW WspecularWWspeedWWsplitރWބWލWގWWWkWlWtWuWWWWWWWWWWWWWWWWWWWW WJccomponentsWWconceptކWއWސWޑWWWnWoWwWxW%W&W(W)W,W-W/W7W8W:W;WWWWWconditionsރWވWލWޒWWWWWkWtWWWWWWWLWPWQW\WgWhWWWWWWWWconformW߻Wconfuses߾WconfusingަW޲WW@WAWbW3W>WBWZWzWWW WconfusingunnecessarysentenceVBV VconjunctionޚWWconsensusfW5WtWconsequentlyW@WWconsiderޮWVWconsideredXWWconsistentޣW-WWWconsolidateިWJWconsolidatedWconstrainedރWލWWkWtWWWWWWWWWWWconstraintsAWWc kandWWW W W WWWWWW!W$W*W3W=W?WEWIWNW^WeWjWpWvWwWWWWWWWWWWWWWWWFOjRevise sentence to read, "The 802.20 standard shall specify a means to ensure message integrity across the air interface to protect both user data traffic and signaling messages from unauthorized modification."kimproves claritymAccepted-Modified 2004/07/13MarkedEDanFGalGMember^Technical, Binding_16`15a4.1.10bRestore 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.d51g2409i Joanne Wilsonk 2004/07/02`cbeWW W WWWWW$W%W'W(W+W,W.W0W1W3W4W6W7W9W:W?W@WAWHWIWLWPWQWVW[W\W]WfWgWhWnWoWqWtWwWzW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W%jsignalling WsignificantlyIW߀WߙWsimilarVWsimilartocomment273rejectcommentVVsimpleipWsimultaneous߄WsinceIW2WsizegWWWsleep-modeWsmallgWso޹WsoftZWWWWWsofthandoffisnotdefinedinthissectionifcommentsuggeVsoftwareWsolutionqW޶WsomehowQWsourceWspecificUWߓWspecificationWߠWspecifiedވW޳W߄WߎWߟWߡW߳WߵWWWspecifiesߔW߯WOW 2004/07/13 2004/06/03MarkedEDanFGalGMember^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.d52g2410i Joanne WilsonkAThis text is informative because it refers to the end-to-end security architecture that is beyond the scope of the 802.20 project and of this document. As such, it is inappropriate to say that this "should be part of ...". Thus, the current text is preferrable.mRejected 2004/07/13 2004/06/03MarkedEDougFKnisely^ Editorial_16`19a4.1.11bg4656 2004/07/02KN kAThis text was developed to address a proposal made at the September 2003 Interim 802.20 meeting. I reviewed the previous versions of the 802.20 requirements document and could not find a further definition of "coverage enhancing technologies." I believe the text is self explanatory and intended to provide the proponents with the flexibility in how they support this requirement .mRejected0kadoptedWafterwWagainst WWaggregateWWWagreeWWWWWW W1W=WDMWNWPWwWWWWWWWൃໃWthefirstrequirementismetthesecondoneisirreVagreethatadaptivebandwidthallocationandadaptivepowerwVagreethatbasestationistheappropriateentityVagreethatburstyandnon-burstytrafficneedstobesupportVagreethatthereistoolargeaspanbetweenpeakandaverag=Vagreethatthisisnotamac/phyissueandshouldthereforeVagreethatthisisnotrelatedtohandoffsVagreewithcommentVagreewithcommenterVagreewithcommentsPVagreewithcomnentVagreewithrationalVagreewithtextexceptthatnegotiationoftemplatesisahiNVagreewiththecommentMVagreewiththecommentsVagreewiththespiritofthecommentbutbelievetheabovei VkrevisionW WrevisionsWrfqWrfrequirementsshouldnotbeincludedinthisdocumentbecaqVrfc)Wright:WriskWWroamW}bproposedchangeoftheentiresentenceinline6theaishal޴ViVproposedmodifiedtextthesecurityprovisionsofieee802.2޶VVproposedoption4޽VVVproposedrewordingtheai'ssecureaccesscontrolshalluse޷Vproposedtextforsection4.2.1.1general޺VqVVprotect޹WWW WWWWWprotected WWprotection޹W WWWprotocolޛW޶WWWWWbW߽WWWW_WWWprotocolsWWWWMWWprovide޹WWWWWWWW W WWW9WIWPWQWcW|WWWWWWWWWWWWMWNWpWsWvWWWWWWWWWprovidereferencesforbestcommercialpracticessVtcreplacePWWreplacedW_WreportingWrepresentativeW0WrepresentsfW5W!>kdocumentWW?WeWqWtWWWkdanWdatahWWW WW"W*W3W=WWWYWdebatedIW]WdecisionpWdefineWW2WdefinedYWpW1W3WWnitionsshouldbeconsistentwithindustryuseandapproVdefinitley:WdegradeWdelayfWߎWdeleted1WdeletingWdemonstratedWdemonstrates*WdenisWdependency1Wdependent*Wdepending߷WdeployWdeployedwWWWdescribeߙWdescribedWdesignWW*WdesiredW#WdetailWWdetailedWWWWdevelop!WdevelopedWWdevelopingWdevelopmentWdevicesWWdictionaryWdifferentWdisagreeWdisagreethatthecurrentphase2requirementsarerealisticVdiscussionWdisruption߷WdividesWdoW$W6WdocumentNWYW߷W߸W߾WWWWWWWWWWWWX]g2256i Joanne Wilsonkeditorial improvementmAccepted 2004/07/13Marked EWarrenFSpringer^Editoria_16`20a4.1.11bChange mitigate against to mitigate denial of service , mitigate means an easing or alleviating ... Or could be " service, the user's privacy and and lessen or halt denial of service attacks. Provision shall be cIline 20 reads "service, the user's privacy and mitigate against denial of service attacks. Provision shall be "\ Mitigate against is a indefensible use of the language ... it should be "mitigate denial"d210g2820i Joanne Wilsonk|"mitigate against" is acceptable terminolgy. See comment #141 and reply #83 for an editorial improvement for this section.mRejected 2004/07/13Marked EWarrenFSpringer^ Editorial_16`21a4.1.11bfshould read made for authentication of both base station and mobile terminal for privacy and for data g4658 2004/07/02NX :bANetwork 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 proB/tocol layers such as EAP, TLS, SSL, IPSec, etc.@WV hbA  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.d141[:bisWW*W.W2W?W_WaWkWlWxWWWWWWWWWWWWWWW'N;basproposedincontributionc802.20-04/55CVeVYbipv4WWWWWWWWWWWipv6WWWWWWWWWWWisރWލWޥWާWWWWWWWWWWWWWWWWWWWW'W+W/W4W=WAWFWbWiWkWtWߺW߽WWWWWWWWWWWWWWWWWWWW<clanguageisnotthatofarequirementespeciallytheusageo޹VVlargeޅWޏWWWWmWvW$W'W+W.W2W3W6W9WWWlastWWWlatencyވWޒW޳WWWCWLWPWQW[W\WeWgWhWWWWޒWޔWޕWWWWWWWWWWW5WXWqWrWzWWWWLWMWPWQW\Wlayers]WleastGW4Wleaving(WbWlessW.Wlet'sTWlightWlikeWWW_WWlikelyWWW@WlimitޅWޏWWmWvW$W'W+W6W9W]WlimitationW.WlineޠWޡWެWޮWޯWޱW޼WWW,W@WiWWW WWWTWVWWWYWline6isduplexingschemesޠVVlinearityNWTWIWlinearlyާW?WlinesޘWްWW0WWXWlinkMWVa cthe commas around priva\cy in this line (below) disrupt the meaning and flow of the sentence made for authentication of both base station and mobile terminal, for privacy, and for data d211g2821i Joanne Wilsonjimaintain current text. One editorial improvement is to pluralize "base stations" and "mobile terminals".kAhThe proposed revision changes the meaning from what was intended. The intended meaning is that 1). Provision shall be made for authentication of both base station and mobile terminal. 2) Provisions shall be made for privacy. and 3) Provision shall be made for data integrity. All of which shall be done "consistent with the best current commercial practice"hmRejected 2004/07/13Marked EDanFGalGMember^Technical, Binding_16`27a4.1.11.1bUse reply to comment #87cThe scope of this requirement needs to be refined. As worded, may suggest that the entire access control protocol must be encrypted.d53g2411 2004/07/02^bstations޻W޽WWWIW߽WWpWuWWWWWstatusWstdW_WstillWNWstoredWWWstreamingWWstreamsWWWWWNWstrengthWWWstructureMWsubWW.W2Wsub-sectionޤWW WWWsub-sections޺WqWWsubheading}W<WsubnetsXWWsubsection޺W~W=WqWWsubsetWWWWsubstituteްWXWWsubstitutewithapropertableްVXVVsuburban1WAWWWWsuccinctiWWsuchޥW޵W޺W޽WWWWWWWWWWWWWW*WMWNW_WqWWWWWWWWsufficientMWWsuggestWWsuggestthatwedeleteitorreplacewiththefollowingVVscbreakYWWWbroadޚWWbroadcastWWLWWWWbroadcast/multicastWWWWWWWbroadcast/multicastservicemustbebillablewhilethisismVVbsYWWWWburdens]WburstyWWbutW WWWOWTW]WfWW.W2W5W]WfWwWWWWWWWLcbasedWGWOWQWWW4WfWWbasedonthestandardsandproductstimeframethetechnologGV4VVbasesW=WWWbasisWWbcmcWWbcmcmustsupportietfipbroadcastandmulticasttrafficefVVbeރ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`WaWbWgWkWmWnWqWrWsWtWvWwWzW{WߺW߻W߿WWWWWWWWWWWWWWW]f i Joanne Wilsonkimproves claritymAccepted-Modified 2004/07/13 2004/06/04Marked EDougFKnisely^Technical, Non-binding_16`27a4.1.11.1b+"Access control" => "Access authentication"c Terminologyd142g2257i Joanne WilsonjbReplace the text with, "Access control shall include authentication using a cryptographic method."klAgree with the spirit of the comment, but believe the above is a more complete statement of the requirement.mAccepted-Modified 2004/07/13Marked 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.d54g2412i Joanne WilsonkNThere should be consistency between the header and the contents of the sectionmAccepted 2004/07/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_16`29a4.1.11.2bg4662 2004/07/02K0kabilityWablefW%WWW4W?Wabout W%W#WaboveW WacceptableW WuWWacceptedWaccepting#W_WaccessrWހW߾WWW*WaccountWaccurateWWaccurateandprobablyusefuladditionVaccuratelyWachievableWachieveAWachievedAWacrossWactivevW%WEWJkagreedKWNWagreedthatthisparagraphshouldbeinformativesuggestremKVaiWairWWWWWW*W2W^WWairbagwWallpWWW W*W/WWallocationwWallowjW}WWallowedWallowspWalone*WalreadywWހWWW4WWWalreadycoveredintheparanywayValso߽WWWW!W*WtWwWWWalternativeWambigous"WambiguitiesWambiguityIWWambiguousWvWambitious!WanrWvWwWހWWWWWWW W>WEWeWpWWWWWWWanalysiseWandIWLW]WiWjWpWrWuWvWwW}WWW߷W߽W߾WWWWWWWWWWWWWWWWWW jcdoes W0WcWWWWWWWWWWWWWWfmg2413i Joanne Wilsonj'Use reply in record #80 to comment #212kThe second part of the proposed remedy establishes requirements on higher layers that are outside of the scope of the 802.20 standard.mRejected 2004/07/13 2004/06/04MarkedEDougFKnisely^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.d143g2258i Joanne Wilsonj'Use reply in record #80 to comment #212mAccepted-Modified 2004/07/13MarkedEDougFKnisely^Technical, Binding_17`1a4.1.11.2bg4664 2004/07/02ae 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".d55d btoWWWWWWWWWWW W"W.W2W<W=W>W?W@WAWFWHWIWMWNWZW^W_WfWiWlWmWqWuWvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWW~-btoavailablewithinlessthan25ms@dtwo@Kunder@ourbanoutdoor-indoor@?userkusercapacitycellsizesandreliabilityasanexampleegm@Svehicular@wide-area@wireless@4with@within@c1notarequirementsnottestable@asimpleeditorialchangetoelinateunneededwordsinthef@able@addaclarificationonimplementation@jagnostic@allcurrentthreeoptionsneedimprovementaddoption4@and@anntenna@architecture@arq@ asanexamplemobilityisambiguous@average@awk@bad@based@`beLbearer@break@_bws@scall@Nchangearetoshallbeandinsertapprovedbeforepar@clarifyawkdefinition@columns@Jcomponents@Iconstruction@convergence@copied@decreased@define@defined@design@designed@ydesigns@does dXbbottomޛWWbpsW^Wbps/sectorWWbroadbandWEWPW|W߶W߾WWWWbroadcastWWWWDWLWWWWWWWWbroadcastservicetheabilitytotransmitapacketofinformVVbroadcast/multicastWWWWWbrowingWNWbrowsingWWbs޽WHWmWWWqibofWWWWWW W!W*W.W0W2W3W4W5W<W=W>W?WAWHWMWNW^W_WaWfWiWpWqWuWvWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW?S buserWWW W!W*W.W0W2W3W4W<W=W@WAWMWNWOW^WjWvWzWWWWWWWmtg2259i Joanne WilsonjRevise sentence to read, "The 802.20 standard shall support encryption across the air interface to protect user data traffic, as well as signaling messages, from unauthorized disclosure ." kimproved claritymAccepted-Modified 2004/07/13MarkedEDougFKnisely^Technical, Binding_17`2a4.1.11.2bASAdd after line 2: "The 802.20 standard shall permit the data traffic and signaling information on a per-user basis to be protected by: - message integrity and encryption, - protected by message integrity but not encryption, - protected by encryption but not message integrity, or - unprotected by either message integrity or encryption." SchNeed to clarify that system can operate with any combination of integrity, encryption, neither, or both.d147g2262iJoanne Wilson, Mike YoussefmirkJNo explanation given as to the benefit of providing these various options.mRejected 2004/07/13MarkedEDougFKniselyg4666 2004/07/02el bAEncryption across the air interface to protect user data traffic, as well as and signaling messages, from unauthorized disclosure shall be providedwill be incorporated.@A   33@  33L  33M  33P  33c  33d  33  33  33  33c'Text should be a normative requirement.d144bdatagramWWdateWWWdealing/WdecidingWWdecoupledWWdefine޺WWWWWW%W)W*W+W;WOW߷WWW@WGWNWcWdWfWkWqWWWWWWdefineanactiveuserasonewhocangetaccesstoabearerV@VVdefinecontrolcapacity%VGVdefinedrafttextforsectionxxxdefinethetbrvaluesofoOVfVdefinemoderate*VdVdefinerequirementsfordelayanddatarateloss)VcVdefinesofthandoffandhardhandoff;V߷VVdefinewhatisinterconnectivityatthephy/mac+VkVdefined޺W޽WWWWWWW.W2W^WqWWWWWdefinition޵WW\WWWWWdefinitioninthisdocumentthetermsystemspectralefficieVVK?bunderރWލWޗWޛWޥW޺W޽WWWWGWkWtWWWWWWWWW*W4WqWWWWWWWWWWWWunitW_Wunnoticeable޽WWWunprotected WWupWWWBWWWWWWupdatesWWupgradeWWuplinkބWގWޤWWWW W@WlWuW~WWWWWW W!W0W3W=WvWwWzWWWWW WuploadingWWupperWWWMWWWurban1WWWbre<V߸Vusereplytocomment87 Vusetheproposedversioninthejointcontributionc802.20-0DVVused޺WWWWqWwWuserޤWޥW޹W޽WWWWWWWWWW WWWW W&W@WFWGW}W~WWWWWUjdealtߘWdebatedIWdecideWWdecodeWdecodingWdefinePWNWWWWdefinedOW߈WWWWdefinesWdefiningߞWߴWdefinition@WPWZWWWdefinitionsWdefinitions/requiremWdefintion޵WdegradationPWWdegradeQWdelayߎWߟWߠWߡW߳WߵWFWNWWdelay/jitter/bwWdelaysWdeleteQWWWW2WKWLWRWSWTWUW[W]WbWcWdWjWnWxWWWWWWWWWWWdeletefollowingsentenceVdeletereferencetoitu2aspartofdeletingentiresectionSVdependޡWިWdepends߉WdeploymentqWWdescriptiveޘWdesignWߙWdesignedgWޘWWdetailed޳WߓWdeterminedޤWdiff-servީWdifferentQWWߞWߴWFWdifferentiated~WހWNWdifferingNWj_bnoteWWWWWDW WnounlWnumberޤWާW޻WW WWWWW W?WuWWWWnumbers!W"WoaWoa&mWWobject=WWoccupied޺WqWWoctetW_Wofތ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߾WWWWWWWWWWWWWWWWWWWWWWWWW W W W 6iwlson߷Wyallapragada5W9W?W@WBWIWPWߎ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ߵWyallapragadaagadaߝWyallapragadanaguib߲WyallaprnaguibߝWyoussefmirWWWWWWWWWWWW!W0WNWOWPWQWRWSWTWUWVW[W^W_W`WaWbWcWdWeWfWgWWWWWWWyoussefmrW  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ࠃࡃࢃࣃःृঃৃਃ੃ઃૃଃୃஃ௃ఃృಃೃഃൃඃසฃใ຃ໃ༃གྷྃ࿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ lw^Technical, Binding_17`4a4.1.11.3bAThe system will shall provide appropriate MAC and PHY capabilities to prevent the unauthorized disclosure of the mobile terminal identifier, mobile terminal hardware identifier (e.g., electronic serial number), and end-user identity.@Az  33   33  33F  33q  33  33zcdText should be a normative requirement. Also strengthen to include other MT identifying parameters.d145g2260iJoanne Wilson, Mike YoussefmirkIt's not clear why the current requirement is inadeaquate and why lower level requirements are not implied by the existing text. Also unclear as to what are the trade offs associated with this requirement. More explanation is needed.mRejected 2004/07/13MarkedEDougFKnisely^Technical, Binding_17`8a4.1.11.4bg4667 2004/07/02cotheripnetworkstandardsnotcomplete9VVVothersWWWourވWޒWWWWLWPWQW\WgWhWWWoutdoorWWW`WqWLWPWQW\WoverallWWoverlyތWޖWWWsW{Wp&pWpacketވWޒWWWhWWLWPWQW\WpageޡW޼WWW߹WWWpaidOWfWparވWޒWުWWWWWCWgW߻W߿WWLWPWQW\WeWparagraphWUWWparameterWWKWNW.W2WIWparametersW WWWWparsWpart޸WW`WW Wpartial޶W6WWparticularދWޕWWWWWcWqWWpartitioningWWparts,Wpast.WWpeakޅWޏWWWWGWmWvW}W~W$W'W+W.W2W3W4W6W9W<W=Ww~=g2261i Joanne WilsonkLIts probably impossible to protect against unforeseeable future DoS attacks.mAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_17`10a4.1.11.5b  33R  33d  33>ctIn a wireless system, protection against DoS is not always possible, but should be a design goal whenever practical.d146bbeWW!W*W0W1W3W=W?WBWDWFWNW^W_WpWqWuWwWWWWWWWWWWWWWWWWWWW W WcdesignedWWCWZWWeWWWWWdesigningވWޒWWWLWPWQW\WgWhWWWetailedތWޖWWWWWsW{WWdetermineEWWdeveloped\WdevelopingWdevicesWdictateRWdifferentރWލWWCWOWhWkWtWWWWWWWdiffernt<W߸WdiffservވWޒWWWOWLWdiffservmayworkwithinterfacingto3gppnetworksbuttheOVdiscard޼WdiscussesިWJWdiscussion`Wdisrupt Wdistinguish޳WWdistortedްWdistortedtable-likecolumnsinlines9through25ްVdiversity<W߸WdividedW0WdlGW4WdoWdocumentވWޒWޮWWWWW<WQWRWWW\W߸W߾WWWWLWdocumentsުWWdoesދWޕW޸WWWWWW)WZW^WqWWW]cwhere<W߸WwhereasWWwhether4WWwhichރWލWWWWGWKWkWtWWWWWWWW4WAWMWWWWWWWWWkproblemW5W`WaWqWproceedsWprocessWprojectWprojection4WpromotejWproponent'sWproponentsWWWproposalfW;WkWWproposalsWFWW1W?WWproposeWWfWWWproposedmW|WWWWWWWWWW WWW!W2W5W>W`WaWkWqWtWWproposersfWprotectWprotocolWQPa4.1.2ޟޠ4.1.3Y߈4.1.4=QޡF4.1.5>ޢޣޤ !"߉ !"#4.1.5.1ehmszޅކއޏސޑޥσЃу׃Gfmnovwx}~߀߁߅߆ߋߌߍ$%&'()*+,-./0123456789:;<=ۃ܃݃4.1.6Rަާʃ#$%MN߂߄ߊ>?@ABCDEFGHI ޻/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ުdekeditorialandtrivialVeditorialcorrectionߺVVVeditorialimprovementVVVVCVmVrVzVVVeditorialimprovementthatdoesnotchangethemeaningofthVeffficiencyAWefficiencyAWWWW*WWeither&W߷WWWWeitherisokayVeliminatesWWeliminatesredundancyandimprovesclarityVemergencywWemissionWend-to-endހWWenhancingWensurevWWentailspWentireVWentirelyߙWentityWenvironmentfWenvironmentspWequal7WequipmenttWerroriWrWuWvWessential|WestablishWWestablishedWestablishesWWestablishingW"WWetcwWethernetKWevaluate?WevaluationWWW?Wexample*WexanationAWWfixedWflexibilityjW}WWWWflowWfocusrWfollowsEWvb1. 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 captiond29g2368i Joanne Wilsonk&improves consistency of text and tablemAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^ Editorial_12`6a4.1.2b)change to: "duplexing schemes (FDD/TDD)"cline 6 is "Duplexing schemes"d30g2369i Joanne Wilsonk okay wordingmAccepted 2004/07/13 2004/06/01MarkedEDougFKnisely^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.d128g2243i Joanne WilsonkText is informative and useful.mRejected 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_12`11a4.1.3g4673 2004/07/026 'binability޽WWWincertW2Winclude޺W޻WWW(WHWbWmWqWuWWWWWWincludeexpeditedforwardingtrafficclassdescription(VbVincludes޶WWincludingWWEWWWWWix`bbandwidthsWWTWWWWWWbase޴W޻W޿WWW<WIW߸W߽WW WMWiWpWuWWWWWbasedWWWWWVWWWWMW_WWWWbasesW=WWWWbasesbecomesbasissincetableistheobject=VVbasisW WW=WWWWWWbattery޻WcWuWWWbeޚWޣWޥWާW޶W޹W޺W޻W޽WWWWWWWWWWWWWWWWWWW W W WWWWWW W$W>W?WBWEWIWLWZWbWgW~W߿WWWWWWWWWWWWW WWWWWEwcofރ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޻WWWWWWWWWWWWWWWWWWWWW WWWWW W,W4W>WAWCWEWGWKWLWOWUWYW_W`WaWcWfWgWkWlWmWnWoWqWrWtWuWvWwWxWzWW߿WWWWWWWWWWWWWWWWWWWNkthanhW%WWWWWWWW>WEWWthatKWSWfWhWpWvWwWWWWWWWW%W߷W߽WWWWWWWWWWWWW WWW!W"W*W1W2W4W=W?WEWNWWWYWeWfWvWwWWWWWWWWWWthat'sWWuWvWwW|W}WހWWWWWWWWW$W%W7W:WGWNWߙWߥW߶W߷W߸W߻W߽W߾WWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW W!W"W#W*W1W2W3W4W5W=W>W?WEWIWMWNWZW^WeWiWoWpWqWtWvWwW~boReplace it with "The AI shall support closely coupled/loosely coupled / mutually decoupled FDD and TDD modes."c0"The AI shall support..... (TDD)." is ambiguous.d170g2335i Joanne Wilsonk0The newly proposed text is thoroughly ambiguous.mRejected 2004/07/13MarkedEDanFGalGMember^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.d31g2370i Joanne Wilsonkno need to be redundantmAccepted 2004/07/13 2004/06/01MarkedEDougFKnisely^Technical, Non-binding_12`17a4.1.4bdDelete "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.d129g2244i Joanne Wilsonk,same as reply in record #101 to comment # 31mAccepted-Duplicate 2004/07/13Marked^editoria> B=(^technicalbindingVVV"V#V$V%V&V'V(V)V+V,V-V.V/V0V1V2V3V4V5V6V7V8V9V:V;V?V@VAVEVFVGVHVIVKVLVMVNVOVPVQVVVWVYV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVkVnVoVqVsVuVwVxVyV{V|V}V~VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV|,bseparateWNWserial WWserverWWserver-clientWWserviceޙWޥW޲W޺W޽WWWWWWW WW>WWWWW WW*WZW_WqWWWWWWWWWWservicesWWWDWLWWWWWWWsession޽WWWWWsessionsާWWW$WW?WBWFW WkreferiWuWreferenceKWYWreferenced"WreferencessWWreferred>WrefersrW%WWreflectshW߶WrelatedwW߷WWWWrelativeWremainWremainderߙWWWremedyߙW߾WWW5W>W`WaWfWkWWremedydoesnotproposesolutiononlythatvaluesareneededfVremedyingqWremoveWremovesIWremovingKWreplacedWreplacementWreplykWnWsWtWށWނW WW*WqWWWWW WWWW%W&W0WAWGWSWnWxWyWWWWWWWWWWWWWWWWWWWWWWNWhWiWpWrWuWWߥW߷W߻W߾WWWWWWWWW!W"W2W=W?WeWresponsibilityNWrestހWWretainZWreviewedWnctosupporttherequirementhasnoteeth'VaVtodayވWޒWWWLWPWQW\WgWhWWWtolerable޳W[WtoleranceCWeWtooޚWW~WW=W@WWtoolsRW{Wg2336jdelete sentence, k(see reply in record #101 to comment #31mRejected-Duplicate 2004/07/13MarkedEAnnaFTeeGMember^ Editorial_12`16a4.1.4b"The AI shall support different modes of ....speeds(250 km/h). It is acceptable that the maximum user data rate degrades gracefully from pedestrian speeds to high speed mobility."cWAWBWEWFWHWLWMWNWOWTWWWXW[W_W`WaWbWcWiWkWtW|W}W~W߶WߺW߽WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W! 2004/07/13Marked"EEshwarF Pittampalli^Technical, Binding_13`7a4.1.5bReplace it with Phase 1 numbers changed to >3.0 Mbps (for 1.25 MHz DL), >1.5 Mbps(for 1.25 MHz UL),, >12 Mbps(for 5 MHz DL),, >6 Mbps (for 5 MHz UL) respectivey and delete Phase 2 columnscTable 4-2 ambiguous.d173g2338i Joanne WilsonkSince 802.20 is not establishing requirements on the channel bandwidth, it should not express requirements for the data rates based on channel bandwidths. Hence, these requirements are ambigous in that its not clear what bandwidth is being referenced.mRejected 2004/07/13Marked4-2#EEshwarF Pittampalli^Technical, Binding_13`11a4.1.5bDelete Option 2cOption 2 is not desired.d174g2339kthere is no reason given in the comment about why option 2 is not desired. Hence, there is no basis for accepting this comment.mRejected 2004/07/13Marked$EToddFChauvin^Technical, Binding_12`22a4.1.5.1g4684 2004/07/02 !kA{The current requirement is sufficiently ambitious for a loaded system at 90% of the cell coverage area. The statement that existing technologies meet this requirement is unsupportable and there is no assurance that the proposed requirements can be met by any currently available technology. It's also impossible to develop a standard based on currently unavailable technology.{mRejected<@ B^binding"W#W$W%W&W'W(W)W*W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W?W@WAWEWFWGWHWIWKWLWMWNWOWPWQWVWWWYW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWkWnWoWqWsWuWwWxWyW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWn#cnotarequirementimmediatelyobviousandaddsnovalueVVnotasentenceVjVnotanexampleasadvertisednotrelevanttotherequirementVVVnotclearwhatismeantbypartialsolutionperhapsrephrasi޶VVnotdefineduntestableVV mrejected#*145=>?EGKORVWYZ[^_`abcdefkopqstࠃࡃࣃःृঃৃ੃ૃஃ؃$b"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. 3d3g2254i Joanne Wilsonk)option 2 is more reasonable and realisticmAccepted 2004/07/13Marked%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 bandwidthsd4g2255i Joanne Wilsonk&see reply in record #111 to comment #3mAccepted 2004/07/13Marked&EToddFChauvin^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d5g2256i Joanne Wilsonk&see reply in record #111 to comment #3 2004/07/02&mAccepted 2004/07/13Marked'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. 3d13g2254i Joanne WilsonmAccepted-Duplicate 2004/07/13Marked(EJohnFChen^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 bandwidthsd14g2255i Joanne WilsonmAccepted-Duplicate 2004/07/13Marked)EJohnFChen^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d15g2256i Joanne WilsonmAccepted-Duplicate 2004/07/13D&m)*kA+@-m.cAg0cAg1k2cAg3cAg4bAcBg5k8F;m=kAC>@AbDbFbHbJjLcAgMbANbBgjBPcBgQcgT`WE[b\cAg^bA@g_bBgbc e^ kA gcAghgkFmkpbA"g!qbB$D%c&g#t_(ubA+g*vjA.-wjA21zc5|^7bA9g8c=bBkCcFcGcJdMdRgQbBWgVc\F^jakAcdk141 W143GW150xWyW154W169_W181nW194xWyW1993-2004W1995-02-07W1bpsW2fWhWlWW!W"WSWfWߎWWW W#W$W.W1WW2003W201W202W206WWWWWWWWWWWWA%coption1page18line4thetbrneedstobedefinedorelse޼V~VVoption1peakperuserdataratesisaveryimportantparameV.Voption1peakratesresultinalargeuserdataratepeaktoޅVޏVVmVvV$V'V+V6V9VVVoption2hasabetterorganizedformatwhichshowstherelevKVVoption2isnotdesired"V#Voption2providesdescriptionforonlybesteffortdataleav(VbVoption3issimplestraightforwardandwelldefinedމVޓVVVpVyV|V}VVVVVVVoption-1޼W~WWoptionalWXWWWW ijoanne'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W=W>W?W@WAWBWCWDWEWFWGWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#maccepted-modifiedJKLORSTUW[eqwyކއމދޕޘޡޤަޮ޶޹Ճփ؃ 'FHKMUqߖߙߝ߶߽Ńу؃ 023FJLNSTU]jlnvwxyz|}ࢃਃઃଃୃ௃ఃృƒ̓уԃ rejected5=@AIQX]fghijruv|}ހރލޣޥާީެ޳޷޽ƒÃăŃ׃ !"$%()*12367:;GOf~߀߂߄߉ߎߔߘߞߟߠߡ߳ߴߵ߷߹߾߿ẵЃӃԃփكڃۃ܃݃ރ߃ !")Marked*EDanFGalGMember^Technical, Binding_13`18a4.1.5.1bAoption 3: 1. delete the table. 2. Alternate text for this section: "The user peak data rate is the maximum attainable data rate, under best channel conditions, mobility, system loading and service parameters such as QoS. For a given link (DL/UL) and a given channel bandwidth, it is calculated by multiplying the appropriate spectral efficiency entry of Table 4-1 by the specified channel bandwidth and factored by 1.2. As an example, the peak user data rate for a pedestrian user of a 5 MHBWW WmixWDW WmixesNWIWmmobileW߽Wmobile޴W޺W޻W޽WWWWWWWWWWW WWWWWW9W<WEWIWPW_WhWjW|W߶W߸W߽W߾WWWWWWWWWWWWWWWW WWMWNW^WiWpWqWuWWWWWWWWWWWWW@knotatallclearwhattextfromc802.20-04/44isbeingpropoVnotnecessaryandoutofscopeofthisdocumentVnotneededandnoreasontopromoteaparticulartypeofmuljVnowWWnumbers WobjectivesWobservableWWobviousW%WobviouslyWW=WofAWKWNWYWhWjWpWwW}WހWWWWWWWW WߎWߙWߥW߶W߾WWWWWWWWWWWWWWWW W W WWWWWWW!W*W/W1W2W3W4W?WEWNW^WeWjWoffsWokayWWWokaywordingVonrW|WW WW2W3W߷WWWWWWWW!W"W*W4WEW^Won-lineWoneSWWW߽WWWonlyAWSWW߶WW2W4WEWfWoob*WopenWqcdefineWWWWWW.W2WdefinebroadcastandmulticastservicesVVEcreaderbWWreadily7WW Wreadilyextensibletowiderchannelsthisisanopen-endedr7VV Vreads>W WrealWW1WwWrealisticWrealitiesW1Wrealtime޳W[WreasonWgW߿W1W3WreasonableSWWreceiveWWcrecommend@recommended@referenced@regulators@replace@Srequire@requirements@requirementswithregardto802.1qaredetailedinthe802p@rf@rtt@rural@scope@sentece@*sentenceshouldnotbenormativenottestableataminimum@;service@)shall/should@usimple@software@Bspecification@specifity@Hsports@statistics@.streams@>supportnon-lineofsightambiguous@system@table-like@3technologies@termsarenotdefinednoraretheyrequirementsforasystem@that@thatthefollowingtableispresentedasthebases@thejthe802.20standardshallsupportthissentenceisnotclear@utheconceptofbandwidthmustbeclarifiedgiventhatweare@ thedefinitionofsofthandoffgivenhereisincorrectsoft@thescopeofthisrequirementneedstoberefinedasworded@-mAccepted-Duplicate 2004/07/13Marked.EKazuhiroFMurakamiGMember^Technical, Binding_14`6a4.1.5.1bAz#1:Change option 1 Line 2-3 to "System Archetecture"data rate and Amodified to "These peak data rate targets are independent of channel conditions, traffic and loading." (Delete "and system architecture" "2:Insert after Option 1 Line4 with the follwing words "If system has some sub channels for users, user data rate is defined sum of user data rates in one sub channel." zcg4694 2004/07/02.g2215i Joanne WilsonkdIf option 1 is selected then it should be modified per this comment. My preference is for option 2.mAccepted 2004/07/13 2004/06/08Marked/EMarkFKlerer^Technical, Binding_12`22a4.1.5.1b;Select option 2 and delete text dealing with average rates.cThis section specifies two options. Option 1 makes reference to a Phase 1 and Phase 2. This concept is not defined, and is therefore, not meaningful.d92g2701i Joanne Wilsonkmost preferred option of all.mAccepted 2004/07/13Marked0EDougFKnisely^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."cg4696 2004/07/02 .cAOption 1 "Peak Per User Data Rates" is a very important parameter for definiton of the system performance for TDMA and CDMA architecture even if there is no or less chance for one user get this defined peak user data rate. Howerer, for FDMA system, this definition is not system performance, but this is only performance for one user. they are able to provides all sub channels to one user, for make appearant large peak user data rate. But, for FDMA system, it is no meaning. CurrentB description makes a limitation of system architecture in system requrement phase, (it must be executed in call for proposal and evaluation phase) although it is not neccessary to define a performance of very few situation d85EbconferencingWNWconfigurationWWconflictsWNWconformWWWMWconjunctionޚWWconnectedWWconnectionsWWconsensusWWconservationcWWconsistentޢW޺WWWgW߻W߿WWWWqWvWWstingWPWWWconsistsWW߽WWconsolidateWconsolidatetheusefulinformationVconstitutesW߽WconstraintsvWcontentionMWcontextWWcontiguous:WWcontributionުWCWDWHWIWPWWWWeWmWpWWWcontributions޳W[Wcontrol޷W޻WWWWWWW%W߽W߾WWW WDWGWuWWWWcontrolandmonitoringVVcontrolsconstraintsWWconversationalW_WcoreWcorrectionsW^WcorrectlyW_WcorrespondingWWW_W cthissectionspecifiestwooptionsoption1makesreference/VthisseemstoplacearequirementonthenetworkandnottheVVVVthissentenceisnotrelevanttohandoffbutrathertonatn]VVVthissentencemaybeusefultoretainscalabilityisusefulTVVthisshouldbeanormativerequirementVVthistermsimpleipisnotwelldefinedinthisdocumentand\VVV0g2245iJoanne Wilson, Mike Youssefmirj'see reply in record #122 to comment #92kconsequential to previous replymAccepted-Modified 2004/07/13Marked1EDougFKnisely^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.6d131g2246i Joanne Wilson 2004/07/02 0cAAverage 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.d130G band0W2W3W4W6W7W8W9W:W;W<W=WFWMWNWOW^W_WcWjWmWqWuWvWwWzW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW Wp1kPreference is for option 2. Agree that the concept of phases should be deleted, but the "bandwidth" dependency is ill defined in option 1, particularly since proposals may be submitted using any channel bandwidth.mRejected 2004/07/13Marked4-32EMasaakiFYuzaGMember^Technical, Binding_13`2a4.1.5.1bA#1:Line 2-3 is modified to "These peak data rate targets are independent of channel conditions, traffic and loading." #2:Incert following line to after Line4 "If system has some sub channels for users, user data rate is defined sum of user data rates in one sub channel" cg4698 2004/07/02U;kdefiningWWdefinitionWdefinitionsWdefinitionsshouldbeconsistentwithindustryuseandapproVdefinitley:WdegradeWdelayfWߎW>WEWdeleteGWVWZWWWWWdeleted1WdeletingWWdeliver4WdemonstratedWdemonstrates*WdenisWdependency1WqWdependent*WWdepending߷WEWdeployWWdeployedwWWWdeploymentWdescribeߙW5WdescribedWdesignWW*WwWWWWWWWdesiredW#WdetailWWWdevelopedWW4WdevelopingWdevelopmentWdevicesWWdictionaryWdifferentW=WvWdifferently?WdisagreeW?WWWYWdisagreethatdatarateismissinginthissentenceYVdisagreethatdatarateismissinginthistextWVdisagreethatthecurrentphase2requirementsarerealisticV2g2211i Joanne WilsonjlShould delete "and system architecture" in both lines 3 and 13, since the same text appears in both options.kShould not define performance requirements for only a subset of the system architectures that may be proposed for the 802.20 air interface.mAccepted-Modified 2004/07/13 2004/05/28Marked4-33Eshigeru Fkimura^Technical, Binding_12`22a4.1.5.1bAOption 1 modification The AI shall support peak system data rates in excess of the values shown in table 4-3. These peak data rate targets are independent of channel conditions, traffic loading, and system architecture. 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. change the section discription User Data Rates - Downlink & Uplink -> Peak system data rates and average usB!er data rates -Downlink & Uplink cg4699 2004/07/02 2cA"Peak Per User Data Rates" is a very important parameter for define the system performance for TDMA and CDMA architecture. It is not define system performance for FDMA system, it's define only performance for one user. It is able to all sub channels provides to one user, for make appearant large peak user data rate. But, What is it meaning for FDMA system? It is not neccessary define a performance of very few situation. d156cmakesW.W/WmakingWmanagementcWWmandatecWWmandatingދWޕWWWqWWWWWWWWWmandatoryWWWWmannerWZWWWmanyދWޕWWWqWWWWWWWWWmarketW1WmarketingWWmaterialWmatterWmaximum޳WGWJW4W[WWWުWޮW޷WW,WNWOWTWXW WIWVWfWoWwWWWWWWmbpsGW4WmeaningޡWWWWWWW WW.W2WWWmeaningful/WmeansވWޒWޣWWWWLWPWQW\WgWhWWWmeant޶WWW0WmeasuredbWWmeasurementWmeasures)WcWmechanismދWޕWWWLWqWWWWWWWWWWWmechanisms8WW W* 'jlinkgWWߣWwWlinkadaptationshallbeusedbytheaiforincreasingspectwVlink-levelNWlistW Wlisted~Wlive޺WUWloaded3Wloading߄W3Wlocate޵WlocationWlogicalWloosely߈WlossWlowWlowergWlowestWmacOWߙWNWmac-relatedJWmac/phyTW߶WmacrogWmacro/micro/picoWmaintainQW߷W߹W߾W߿WWWWWWWWWWWWW WvWzWWjsameasaqccommentonthetopicapossibledefinitionisbZVsameascomment155rejectcomment6V:VCVGV^VaVsameascomment273rejectcomment7V;VDVFVbVsameascomment97rejectcomment8V<VEV_VcVsameasreplyinrecord155tocomment6\VsatisfyNWsatisfyingNWscalableqWscenariosWschemesߣWWscopeWscreenWsecWsecondޘW߽WWsection4WTW]WgWWރWWWߓWߔWߘWߙWߞWߪW߯WߴW3WJWKWLWRWSWTWUW[W]WbWcWdWWWWWWWWWWsection4.1.2hasalreadydealtwiththisaspectsufficientlߘVsection4.1.3alreadyspecifiestheairequirementsonfddaߔV߯Vsectionandoption1modification3VsectorW3g2340i Joanne WilsonjASection and Option 1 modification 4.1.5.1 Peak system data rates and average user data rates -Downlink & Uplink The AI shall support peak system data rates in excess of the values shown in table 4-3. These peak data rate targets are independent of channel conditions, traffic loading, and system architecture. 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. kA:It is better to specify the system peak data rates instead of peak user data rates. The reason why the large peak data rates is little hope and confusing for user. Important things are system data rates and average user data rates. The peak user data rates should be defined by each system for user if necessary. :mAccepted-Modified 2004/07/13Marked4-34EAnnaFTeeGMember^Technical, Binding_12`22a4.1.5.1bg4700 2004/07/02 T3cA9It is better to specify the system peak data rates instead of peak user data rates. The reason why the large peak data rates is little hope and confusing for user. Important things are system data rates and average user data rates. The peak user data rates should be defined by each system for user if necessary.9d205fYcneedފWތWޔWޖWޛWޣWޤWޥWިWެW޳W޻W޽WWWWWWWWWWWW W<WDWHWIWOWrWsWzW{W߸WWWWWWWW W*WJWNWTW[WfWmWpWuWWWWWWWWWWWWWWWWWWWWWWWWWW!WneedclarificationtothetextHVIVmVpV"jratesQWW߀W3WvWzWWratherޮWߪWrationales߄WreadLWWWzWWreadilyߙWreceivingZWWreciveWrecommendTWrecommendsރWrecordWW0WLWOWRWSWTWUW[W\W]WbWcWdWkWyW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWrecordsWreducezWreducedgWreductionvWredundancyWreferiWrWuWreferenceNWPWWWreferenced~WWreferencesߩWreferencetoSWreject6W7W8W:W;W<WAWCWDWEWFWGWVW^W_WaWbWcWT\jtransferredZWtransitionsWtransmissionsyWtransmitWtransmittingZWtreatment WFWtrue3WtwoWtxt~WtypesߞWߴWtypo{WubiquitousWul߀WunauthorizedWWunder߄WWunderstandingޣWunnoticeableWunwieldyީWupxWWupdatedWW3WvWwWzWuploadingWupperyWߙWuseRWWީWWW1WLWߣW߽WWWWWWLWWusecommonterminolgyacrossdocumentVusedefinitionsfromareferencedindustrysourceaddadopteVuseofthewordwillisnotappropriatesuggestthefollowinߣVuseoption2injointcontributionRVuseoption31Vuseprotocolinlayers1and2Vusereplyinrecord80tocomment212VVusethefollowinginthisdocumentthetermsystemspectralVusethefollowingtextVusethetextofthefirstsentenceofthesuggestedremedyr߽VklargerfWWWlastvWߙWlatencyiWrWuWeWlayerހWWNWlayers߾WWWWWWleastWleavepWlegal-eseLWlends>Wless[W>WletW*WlevelWWW4W=WEWlevelsYWlicensed*WWWlikelyWvWWlimitWWlimitingWWk4g2215i Joanne WilsonkA`The standard can only be based on the technology available at the time the standard is developed. Its impossible to develop a standard that can be assured to work well using a projection of what future technology will be able to deliver. Additionally, the is no technical basis for scaling up this requirement beyond its already unachieveable level.`mRejected 2004/07/13 2004/06/08Marked4-25EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_12`22a4.1.5.1bxAdopt the text in Section 4.1.5.1 of C802.20-04-44, with the modification of deleting the word "channel" from the table.c (C802.20-04-44) text in Section 4.1.5.1 represents a consensus of a number of Individuals. It was included previously in V12, but seems to have been removed in V13.d259g2487i Joanne Wilsonj  2004/07/02 a4bAXScaling the above peak data rates in the reference case by approximately 1.6 times results in the following proposed values: "Under an ideal channel and loading conditions, the AI shall support peak user data rates in excess of the following: 1.25 MHz channel bandwidth - DL: 5 Mbps; UL: 2.5 Mbps 5 MHz bandwidth - DL: 20 Mbps; UL: 10 Mpbs" XcABased on the standards and products time frame, the technology would probably be available at least two years later. It would be necessary for this technology to support maximum user data rates that are higher than the capability of the current technology, which is supporting similar applications of a relatively older generation. As a reference, 1xEV-DV Release D supports peak data rates of 3.08 Mbps and 1.5 Mbps for the DL and RL respectively in an 1.25 MHz bandwidth. Scaling these to 5 ?4cB$ MHz channel bandwidth results in: 12.32 Mbps and 6 Mbps respectively. For further information on bandwidth requirements for video streams: 6-32 Mbps for high definition MPEG-2 movies, up to 19.6 Mbps for hi-def MPEG-2 sports; DVD with standard definition: maximum requirement of 9 Mbps. d2202tomcikLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjW߿WWWWWWWWW5WHWIWfWnWtW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWwilsonklmnopqrs678g༃Ńσyoussefmirtuvwxyz{9:;hགྷƃЃ !kthesuggestedremedyisincorrectthisdocumentprovidesthe߾VthetextisbothinformativeandusefulVthetextisclearthestandardshallhavebothatddandanVthetextissetstheoverallparametersofthembwasolutionVthetwopartsofthesentencearenotcontradictorythestatoVtheworkinggrouphasnotadoptedapolicyofdevelopingacVtheirqWWthemWthenW.WtheoreticalWthereWWW߷WW W!W#W5W=WEWWWthereappearstobeamis-readingofthetextbecauseitisVthereisnoexplanationoftheproblemVthereisnoreasongiveninthecommentaboutwhyoption2i#Vthereshouldbeconsistencybetweentheheaderandtheconte VthereshouldnotbearequirementforacommonmacdesigntoVtherebyWthereforeWWthese WߥWW"W=WthesechangesimproveclarityoftherequirementsߥV5kThe comment doesn't describe a problem with the current text. There is no technical basis presented for the proposed remedy to the unspecified problem.mRejected 2004/07/13 2004/06/07Marked6EJoanneFWilson^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. 3d268g2235i Joanne WilsonmAccepted-Duplicate 2004/07/13Marked7EJoanneFWilson^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 bandwidthsd269g2236i Joanne WilsonmAccepted-Duplicate 2004/07/13Marked8EJoanneg4704:kthecommentdoesn'tdescribeaproblemwiththecurrenttext5Vthecurrentrequirementissufficientlyambitiousforaload!VthecurrenttextexplainswhatneedstobesupportedontheVthecurrenttextissufficientforathepurposesofthereqV8 2004/07/13Marked9EMichaelF Youssefmir^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. 3d278g2254i Joanne WilsonmAccepted-Duplicate 2004/07/13Marked:EMichaelF Youssefmir^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 bandwidthsd279g2255i Joanne WilsonmAccepted-Duplicate 2004/07/13Marked;EMichaelF Youssefmir^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d280g2256i Joanne Wilson 2004/07/028FWilson^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d270g2237i Joanne WilsonmAccepted-DuplicateC;mAccepted-Duplicate 2004/07/13MarkedEDanFGalGMember^Technical, Non-binding_13`24a4.1.6bcChange "...available with a delay of less than 25 ms." to: "...available within less than 25 ms."cPotentially confusing text .d36g2375i Joanne WilsonkThough an editorial change, this is commonly referred to as a delay requirement, so the current text is actually lends itself to less confusion than the proposed remedy.mRejected 2004/07/13 2004/06/01Marked?EDanFGalGMember^Technical, Binding_14`2a4.1.6bAdd a sentence (on line 3): "The scaling factor to be assumed for the technology evaluation purposes is 0.9. Thus, for a 5 MHz channel, the number of supported simultaneous sessions would be greater than 100*(5/1.25)*0.9 = 360". ckThe phrase "scales linearly with system bandwidth" is inadequate. The scaling factor needs to be specified.d37g2376i Joanne Wilsoni Joanne Wilson 2004/07/028kspan=Wspeaks%WspecificUWXWwW*WqWsWWspecificreferencesarenotneededparticularlysincebestcsVspecificallyAWWspecification߾WWtWspecifiedߎWW*WspecifiyWspecifypW߶W3WWspecifyingWspectralAWWWW*WWspectrum*WWspeedsWspirit WspreadfWߎWspreadsfWsrdpWstandardAWhWހWWWWW!W4W^WpWWWWWWWWstandard'srWstandardshWiWjWuW}W߶WWWstatementW W!WEWoWkorderހWWoriginalރWWotherKWhWiWpWuWWWW WWFWKWEWWourVWourpreferenceistodeletethisentiresectionVVoutW߷WWWoutdoorvWoutdoorsWoutsideWWoverKWXWsWoverallWoverarchingWoverlyWoverviewWownWkWpacketeWpackets߽WWpageAWparhW߻WWWWWparagraphAWKWހWߙWwWparametersWparentheticalEWparitallyWpartWW?WNW^WWpartiallyWparticipantsNWparticularWjWparticularly1WeWsWpartitioningWpartitionsWpartsoWpathWkorder@peak@preferoption1whichistodeletethesectiontheproposed@preferenceisforoption2agreethattheconceptofphases@problem@{protocols@readabilitylessjargon@refer@requested@revision@Qrouting@see@seemycommentonthissection@seereplyinrecord237tocomment68@tseereplyoninitialcomment@ "an FDD" "or TDD" => "or a TDD"cClarifyd134g2249i Joanne Wilsonkeditorial improvementmAccepted 2004/07/13MarkedDEDougFKnisely^Technical, Non-binding_14`5a4.1.6g4716 2004/07/02cdecreasedAWW cthedefinitionofsofthandoffgivenhereisincorrectsoftYVVVthefigures12copiedfroman802standardneedtoberelabޛVVthelineisconfusingandneeedtoberewrittenitseenstha@VzVthemaximumchanneldelayspreadcouldbemuchhigherthan5JVVtheparametersandmetricscannotbeproperlydefinedbeforeVVthephrasescaleslinearlywithsystembandwidthisinadequaާV?VthephraseshallbedesignedinamannerthatdoesisnotaZVVthephysicallayerprovidesetcnotclear5VVtheqosrequirementsinthedocumenttodayegdiffservflexiވVޒVVVLVPVQV\VgVhVVVtherequirementaspreviouslywrittenallowsbroadcastviauLVVtherequirementsarevagueandunmeasurablewerecommenddelVVtherequirementsshallconformtotheparifnottheparneeV߻V&DbtDelete "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?").d135g2250i Joanne Wilsonkagree.mAccepted 2004/07/13MarkedEEEshwarF Pittampalli^Technical, Binding_13`22a4.1.6bDelete "potentially only"c"potentially only" -- redundantd175g2340i Joanne Wilsonk"potentially only minimal delay" is explained by the parenthetical statement that follows. I interpret this to mean that a user in an active session can have more than a "minimal delay" depending on there QoS level and that of other users.mRejected 2004/07/13MarkedFEEshwarF Pittampalli^Technical, Binding_13`26a4.1.6g4718 2004/07/02A-ktobeconsistentwiththearchitectureofieee802standardsjV}VtodayAWtooW=WtradeWtradeoffpWtradeoffseWtrafficKWWvWtransportingWtrivialWtsWtutorialtWtwo߽WoWtyingWtypepWjWtypesKWvWueWultimateWunachieveable*W4WunambigousWunavailable!WunclearWunderpWunderminesWFbRepalce with "Certain applications shall be given preferential treatment w.r.t. delay in order to work and this requirement shall be met even if the sessions are all on different terminals."cVSentences "Note that...VOIP." and "This requirement....terminals" are not cooperative.d176g2341i Joanne WilsonjRepalce with "Support for certain applications (e.g. VoIP) requires that they be given preferential treatment with respect to delay and such requirements shall be met even if the sessions are all on different terminals."mAccepted-Modified 2004/07/13MarkedGEEshwarF Pittampalli^Technical, Binding_14`5a4.1.6bDefine "control capacity"c!"control capacity" is not clear. d177g2342i Joanne WilsonkLSee reply in record #143 to comment #135 which was to delete this sentence.mRejected 2004/07/13MarkedHEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_13`23a4.1.6g4720 2004/07/02ccopiedޛWWcorrectsQWWcorresponding޳WCW[WeWcouldރWލWWCWEWJWaWkWtWWWWWWWAWeWWWWWWWWWWcoupling4WWcoveredWWcovergae޵WWcpe_WWWcpeseemsliketheincorrecttermhereitisusuallyusedin_VVVcreateވWޒWWWLWPWQW\WgWhWWWW*W.W4WLWPWQW\WgWcurrentoptionshaveinternalinconsistenciesneedtoharmonޥ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=WRWWWYWbWcWdWFjthe4W5W@WAWIWKWLWOWQWSWTWUWZW]WeWgWiWqWrWuWxWyWzW{W|W~WWހWރWވWޘWޡWޣWޤWޥWަWީW޵W޷W޹W޺WWWWWWW WHWUW߀W߄W߈W߉WߎWߓWߔWߖWߘWߙWߝWߞWߟWߠWߡWߣWߧWߩW߯W߳WߴWߵW߹W߽WWWWWWWW WW2W3WFWKWLWNWRWTWUW[W]WbWcWdWkWnWvWwWzWWWWWWWWWWWWWWWWthe802.20aishallprovidehandoffmethodsarerequiredinVthe802.20aishallsupportmobilityupto250km/hxVdvVtheaverageuserdataratedependsonnumberofusersandch߉VthefinaldispositionofthiswillneedtobedeterminedbyޤVHb|Change to read as follows: "...bearer channel available with a delay of less than 25 ms with a probability of at least 0.9.cIIt is expected that system access times will be a probabalistic quantity.d227g2489 2004/07/13 2004/06/07IEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_14`2a4.1.6bnChange to read as follows: "...should scale with system bandwidth if the same application mixes are assumed."clThis parameter is understood to be a scalable quantity, however linearity may not be the appropriate choice.d228g2341i Joanne Wilsonk2improvement in the text and removes some ambiguitymAccepted 2004/07/13 2004/06/07MarkedJEDanFGalGMember^ 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.d38g2377i Joanne Wilson 2004/07/02pbcprobablyGW4WWproblem=WWproblemsWDW WprocessWproductsGW4WWprofilesވWޒWWWLWPWQW\WgWhWWWpromotecWWproperWgW߿WWWproperlyWWproposalWWWW.WWproposalsރWބWޅWލWގWޏWWWWWkWlWmWtWuWvWWWWWWWWWWW$W'W+W6W9WwWWWWWWWWWWWW Wproposed޺WqWWproposingW_Wprotection WWprotocol޷WW Wprotocolinlayer1and2VprotocolsWWWproveWprovide޵WW)WWWWcWprovidersaWWWJjHAdd new text in line 15: "See MAC-related requirements in section 4.4.1"mAccepted-Modified 2004/07/13 2004/06/01MarkedKEHariFGantiGMember^Technical, Binding_Technical, Binding`15a4.1.7b>Support option 3 as far as latency requirements are concerned.d73i Joanne WilsonjKpropose to delete section 4.1.7.1 as opposed to adopting any of the optionsmRejected 2004/07/13MarkedLEKazuhiroFMurakamiGMember^Technical, Binding_15`16a4.1.7bRemove this section. cg4724 2004/07/02Lg2218i Joanne Wilsonj]Agree to either delete the section or to use the text in record #152 in reply to comment #136mAccepted-Modified 2004/07/13 2004/06/08MarkedMEDougFKnisely^Technical, Binding_14`9a4.1.7bAThe AI802.20 standard shall support the means to enable link-levelend-to-end QoS between the base station and the mobile terminal. The link-level QoS structure shall provide sufficient capabilities to conform to an end-to-end QoS architecture, e.g., as negotiated by upper layer protocols such as RSVP. within the scope of the AI and The 802.20 standard shall support the ability to enforce QoS authorizations for each user and to support various policies determined by the system operator toB resolve air interface resource contention issues between users based on the individula users' QoS authorization and QoS requestsa Policy-based QoS architecture. @4725 2004/07/02 HLcAThe 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?WAWHW_WWthatތWޖWޡWޢW޶W޺W޽WWWWWWWWWWWWWWWWWWWWWWWDWFWLWZWiWsW{WWWWWWWWWWWWWWWWWWWNW^W_WqWvWWWWWWWWWWWWW"Ng2252iJoanne Wilson, Mike YoussefmirjA"The 802.20 system shall provide the MAC and PHY shall provide the 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  2004/07/02 pNbB. 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.d137N 2004/07/13MarkedOEEshwarF Pittampalli^Technical, Binding_14`13a4.1.7b;Replace it with "satisfy both intra and inter user QoS..."c "satisfy user QoS..." incompleted178g2343iJoanne Wilson, Mike Youssefmirj=See reply in record #153 to comment #137 for preferred remedymRejected 2004/07/13MarkedPEToddFChauvin^Technical, Binding_14`16a4.1.7.1bRemove 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 documg4728 2004/07/02 NjBinformation). The 802.20 system shall provide the MAC and PHY shall provide the 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., CAQoS parameters such as delay, bit rate, error rate, and jitter)."@A   33   33%  331 @ 33B  33  33!  33- @ 33?  33  33  33kwAgree with text, except that negotiation of templates is a higher layer responsibility and not part of the MAC and PHY.mAccepted-Modified|bdenialW W>WW WWdenseAWWWdependingWDW WdeploymentޟWWWWWWWdescribedW_Wdescription(WbWdesignWWBWTWWWWWWW}kexceptNWexhaustiveWexistingAWhWWW!WexpiredrWexplainedEWexplainsWexplanationWWWexplanatoryWexplicitKWexpress"WexpressesWextensiveWexternalWfactor?WfactorsWfddWWWfeatureWWWWWfindWfirstAWހW%WWWfixWfixedWWflexibilityjW}WWWWflowWfocusrWfollowsEWPg2257iJoanne Wilson, Mike Youssefmirkagree with commentsmAccepted 2004/07/13MarkedQEJohnFChen^Technical, Binding_14`16a4.1.7.1bRemove 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Ã6@Ã9@@ijoanne'joannewilson@joannewilsonmikeyoussefmir@][joannewlson@klerer@%/lalit@mike@naguib@;naguibsutivongtomcikyallapragada@sutivong@t@tomicik@wilson_ wlson@r6j1changetoreadieee802.20-basedsystemsshallsupportbro@d157@2@4.2.5@S 33  33>c:add an important attribute of traffic classes - data rate.d39g2378iJoanne Wilson, Mike YoussefmirjDPropose to delete the section, per reply in record 155 to comment #6mRejected 2004/07/13 2004/06/01MarkedSEDanFGalGMember^ Editorial_14`21a4.1.7.1bW WWattendingaWWattributeީWRWWauthentication WauthorizationWWauthorizedWWavailableBWGW4WAWW"gantiɃʃ˃̃ǃ@Kgoldburg̓΃σЃу҃ӃԃՃփ+,-\සɃkimura3klerer/A]ใ˃knisely݃ރ߃ ߹ߺ߻߼߽ƒÃȃ΃σЃу׃؃كڃۃ܃݃ 01BCDMN^_jrvwृଃƒ A}murakami@"naguibsutivongtomcik@hpark@gsutivongtee@tomcik@yuza@2memberB^bindingޣ:!)߀+<"+@editoria@editorial@technical@~6߫+?Otechnicalbinding@ޣ; &߀B!=?(technicalnon-binding@_@‚#@%‚'@k‚(@‚*@j‚1@`p@@‚*@k‚4@a4.1.11@Q4.1.2@|4.1.7@4.2.3ߝ34.5.1@0-based@afddanfdd@{amethodthatwillprovidemessageintegrityacrosstheair@account@oaddadefinitionforsimpleip@ addthe802.20systemshallprovidetheabilitytoefficient@addthefollowingtextinline28@baddthespecificreferenceinsection5and/orinafootnote@Cadopt4.2.1fromc802.20-04.44@HQd`a0<߶߸߹ߺ1.1݃ރ߃ghi߻߼߽߾߿1.2jƒÃăŃ1.3AɃ=ǃȃɃʃ˃̃2KLWXowޗ̓΃σЃу҃ӃԃՃփ2.2MNDL׃؃كڃۃ܃݃ރ߃203.1dxޘޙEPQ|3.1.1Oޚޛޜă4.1.1459BIP]`gklyރބލގޝޞ̓΃kltu׃؃كڃ 4.1.1.11.2?4.1.10@޵pcrMWranOWfWrangesOWfWWrarelyޅWޏWWmWvW$W'W+W6W9WWWrateޅWވWޏWޒWީWޯWޱWWWWWWW)W*W@WCWmWvW$W'W+W.W0W2W6W9WLWPWQWRWWWYW\WcWdWeWgWhWzWWWWWWratesޅWވWޏWޒWWWWWWGWRWmWvW}W~W$W'W+W.W2W3W4W6W9W<W=WLWPWQW\WgWhW{WWWWWWratherW]WWWWratioޅWޏWWmWvW$W'W+W6W9WWW{kpreferenceisforoption2agreethattheconceptofphases1VpreferrableWpreferred/WpresentedW5W=W?Wprevious*WW0WSWpriorWprivacy WprobablyWWW 2004/07/13 2004/06/02MarkedXEDanFGalGMember^ Editorial_15`9a4.1.7.1bsubstitute with a proper table.c2distorted table-like columns in lines 9 through 25d46g2404i Joanne Wilsonk editorialmAccepted 2004/07/13 2004/06/02MarkedYEDanFGalGMember^Technical, Binding_15`27a4.1.7.1b.insert "data rate," after "...with different"c,In Option 4, line 27, missing "data rate," d47g2405i Joanne Wilsonk5Disagree that "data rate" is missing in this sentencemRejected 2004/07/13 2004/06/02MarkedZEDanFGalGMember^ Editorial_15`30a4.1.7.1b5change "Traffic classes" to: "Service Characteristic"cFIn the table of Option 4, confusing column heading - "Traffic classes"d48g2406i Joanne Wilsonk/Prefer to delete the section or retain option 3mRejected 2004/07/13 2004/06/02Marked[EDanFGalGMember^Technical, Binding_15`30a4.1.7.1g4739 2004/07/02WEDanFGalGMember^Technical, Binding_15`4a4.1.7.1b.insert "data rate," after "...with different"c+In Option 3, line 4, missing "data rate," d45g2403i Joanne Wilsonk1disagree that "data rate" is missing in this textmRejectedJ[bBHarmonize with the appropriate 802.20 contributions on this topic.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.d49g2407iJoanne Wilson, Mike YoussefmirjDPropose to delete the section, per reply in record 155 to comment #6mRejected 2004/07/13 2004/06/02Marked\EMarcFGoldburg^Technical, Binding_14`16a4.1.7.1bRemove this section. cg4740 2004/07/02c1notarequirementsnottestableVV1spectralefficiencypage6table1.1andpage12table4.1VV1.0WWW1.1WW1.25GW4WAWWW1.5WGWWW4WW10,WoW10:1ޅWޏWWmWvW$W'W+W6W9WWW10msވWޒWWWLWPWQW\WgWhWWWhc11@120km/hr@2-1@38@E5-criteria@802.20mechanismsnotclear@aߺasimpleeditorialchangetoelinateunneededwordsinthef@able@addaclarificationonimplementation@jadditional@agnostic@allcurrentthreeoptionsneedimprovementaddoption4@allowing@and@qanntenna@architecture@arq@ asanexamplemobilityisambiguous@atsomeearlierversionofthesrdtherewasanagreedupon@er@break@_bws@scall@Ncell@changearetoshallbeandinsertapprovedbeforepar@clarifyawkdefinition@columns@Jcomponents@Iconstruction@convergence@copied@creates@decreased@define@defined@defines@design@designed@ydesigns@diffservmayworkwithinterfacingto3gppnetworksbutthe@does d:\g2688i Joanne Wilsonj)Same as reply in record 155 to comment #6mAccepted-Duplicate 2004/07/13Marked]EMarkFKlerer^Technical, Binding_14`16a4.1.7.1b'Delete this section or retain option 3.c4 Options are specified. All but option 3 impose trade-off burdens in design that cannot be justified as hard limit in a mobile environment.d94g2703i Joanne WilsonjDPropose to delete the section, per reply in record 155 to comment #6mAccepted-Modified 2004/07/13Marked^EDougFKnisely^Technical, Binding_14`19a4.1.7.1bg4742 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 documBW WusersW0WAWWusingWWWusuallWusually_WWWv12fW5Wv13fW5WvagueޚWWWWWWWWWWvagueqosneedmorespecifityVVvalueWWWWWvariousCWWeWWvaryUWWWrsusރWބWލWގWWWkWlWtWuWWWWWWWWWWWWWWWWWveryރWލWWWWCWFWkWtWWWWWWW.W2WeWWWWviaLWWvideoGW4WW ^cwhen\WgWhWWWWWWWWWWWW}cwesupportoption1removingthissectionitdoesnotseemr^VVwe're@WzWwellމWޓWWWW\WpWyWW|W}WWWWWWWWWwereުW.W|WWWWWwgWwhatޣW޶WWWWWWWOWRWUWWWWWWWW2WDWMWfW{WWWW WWwhatisapartitioningmodelVVwhattheheckistelematicsVVwhateverWWwhenވWދWޒWޕWWWWWBWqWLWPWQW5^g2253iJoanne Wilson, Mike YoussefmirkThis is not a requirement on the air interface, but is instead a requirement on the scheduler which is part of the implementation and is not within the scope of the standard. mRejected 2004/07/13Marked_EDougFKnisely^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 sensitiveg4743 2004/07/02 ^bAThe 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 Bflow, 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).  ^b@A   33  33)  33*  332  33D  33  33   33\  33i  33  33cClarify traffic classes...d138xeshwar !"#$%&'()*+,-./0123456789:;߶߷߾ăɃʃ҃ӃԃՃ!"#EFGO`abcdkosxyঃৃਃஃ  q_g2254iJoanne Wilson, Mike Youssefmirk[consequential, since accepting this comment required accepting comment #138 in record #169.mRejected 2004/07/13Marked`EEshwarF Pittampalli^Technical, Binding_14`22a4.1.7.1bNeed more explanation.c,..in Section 4.4.1 "[3,4,5,6]..." not clear.d179g2344iJoanne Wilson, Mike Youssefmirk.No remedy proposed for a non-specified problemmRejected 2004/07/13MarkedaEEshwarF Pittampalli^Technical, Binding_14`25a4.1.7.1b>Quantitative requirement is required (instead of qualitative).c0"To support....." the requirement has no teeth.d180g2345iJoanne Wilson, Mike Youssefmirk.No remedy proposed for a non-specified problemmRejected 2004/07/13MarkedbEEshwarF Pittampalli^Technical, Binding_14`37a4.1.7.1b6Include Expedited Forwarding traffic class descriptiong4746 2004/07/02 Q_bB 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).d139bratesޤW޴W޽WWWWWWWWWW@WGW}W~WWWWW W.W/W0W2W3W4W<W=W^WiWvWzWWWWWWWreadޢW?W@WLWMWNWQWWW[WcWgWhWjW߿WWWWWWW WWAWHWIWzWWWWWWWWW3bmac'sWWmac/phyWHW^WmWmacroEWWmacro/micro/pico|WWmacrocellsPWWmadeWWW WWmaintainvWmaintenanceWWWmakeWDWLWUW`WaWbWiWWWWWWWWWWWWWmaketable4-1consistentwiththeparandspecifyadownlinVmakethesectioninformativetoshowintentorremoveit`VVmanWWmanagementWWmanagmentWmasks޺WqWmaximumޥW޺WW7WFWW*W^WqWWmay޾WWWWWWWWWWW,WIWWWWWWWDWNWoWpWWWWmbps W!WGW~W!W"W4W=WmbsޥW*WmbwaޗWޙWW߾WWWWmeans>W WMWmeasureWWmeasured5WWmeasurementWWWWr iwilson_W`WaWbWcWdWeWfWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWdÃ)'aÃ) (bÃ)0)ߦcÃ)@*ߧdÃ)P+kÃ)`,ߨoÃ)p-Ã).Ã)ߩs bc{Option 2 provides description for only Best Effort data leaving Expedited Forwarding and Assured Forwarding traffic classesd181g2346iJoanne Wilson, Mike YoussefmirjDPropose to delete the section, per reply in record 155 to comment #6mRejected 2004/07/13MarkedcEEshwarF Pittampalli^Technical, Binding_15`11a4.1.7.1b1Define requirements for delay and data rate loss.ch"low delay, low data loss rate,..." does not provide quantitative measures for delay and data loss rate.d182g2347iJoanne Wilson, Mike YoussefmirjDPropose to delete the section, per reply in record 155 to comment #6mRejected 2004/07/13MarkeddEEshwarF Pittampalli^Technical, Binding_15`19a4.1.7.1bDefine "moderate"c8"..moderate delay, moderate data loss rate,.." ambiguousd183g2348iJoanne Wilson, Mike YoussefmirjDPropose to delete the section, per reply in record 155 to comment #6mRejected 2004/07/13MarkedeEAnnaFTeeGMemberg4749 2004/07/02 e^Technical, Binding_14`16a4.1.7.1b*As proposed in Contribution C802.20-04/55.cAAs described in the PAR, the 802.20 standard is designed to support various types of applications. In order to support these applications that could have very different requirements in error rate and latency tolerance optimally, it is important to specify the corresponding minimum requirements for different classes of traffic as targets for the specification of optimal PHY and MAC standards. Similar requirements have been specified for other similar standards such as IEEE 802.16.3, IEEE B[Std. 802-2001 and 3GPP. Please refer to Contribution C802.20-04/55 for further information.Id216g2211iJoanne Wilson, Mike Youssefmirk 2004/07/02e 2004/07/13 2004/06/08MarkedfEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_15`1a4.1.7.1bDefine draft text for Section XXX. Define the "TBR" values of Option 4. Then add Text to Reflect 3GPP2 Approach to Qos to Section XXX.cADiffServ may work with interfacing to 3GPP networks, but the 3GPP2 approach is different. The 3GPP2 network sets the QoS for the Mobile based on call type and type of service the user has paid for. The network tells the RAN what it needs to deliver. Option 4 seems to be the closest to this, with ranges specified for different traffic classes. However, we need to fill in Section XXX.d229g2491iJoanne Wilson, Mike Youssefmirk=Remedy does not propose solution only that values are needed.mRejected 2004/07/13 2004/06/07MarkedgEJoanneFWilson^Technical, Binding_14`16a4.1.7.1bDelete this section.cg4751 2004/07/02  .ekAContribution C802.20-04/55 was incomplete with many TBRs. Plus, we still don't believe that this requirements document should be setting packet loss and latency requirements, particularly without a justification for doing so or an analysis of the impact and tradeoffs.mRejected,crequirementswithregardto802.1qaredetailedinthe802pVVrequirenments޺WqWWrequiresވWޒWWWLWPWQW\WgWhWWWrequiringކWސWWnWwW%W(W,W7W:WWWrequrementW.WrespectތWޖWWWsW{WWWWWWWWWrespectivelyWGWWW4WWrestWWrestored޵WWrestrictވWޒWWWLWPWQW\WgWhWWWrestrictiveW@WWrestructureޤW WresultޅWޏWWmWvW$W'W+W6W9WWWresultsGW4WWretainTWWrevisedW1WrewordZWWrewritten@WzWdcdiffservmayworkwithinterfacingto3gppnetworksbuttheOVfVdiscard޼W~WWdiscussesިWJWdiscussion`WWWdisrupt Wdistinguish޳WWNW[WdistortedްWXWWdistortedtable-likecolumnsinlines9through25ްVXVVdiversity<W߸WdividedW0WdlGW4WWdoWWdocumentވWޒWޮWWWWW<WQWRWWW\W߸W߾WWWWLWPWQWVW\WgWhW{WWWWWWWWdocumentsުWWWWWdoesދWޕW޸WWWWWW)WZW^WqWWWgg2238iMIke YoussefmirmAccepted-Duplicate 2004/07/13MarkedhEMichaelF Youssefmir^Technical, Binding_14`16a4.1.7.1bRemove 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?HI߃ߒߨ ijcperceivedW@WWperformanceWWWW.W2WWWperhaps޶WWWperiodWWWperspectiveXWWphaseWW.W/W1WphasedW1WphasesއWޑWWWoWxW&W)W-W1W8W;WWWphraseާWZW?WWphyCWVWXWZWeWWWWWWphy/mac޴W+WiWkWphysicalW5WWWWplace<WVW߸WWWplacedޞW޺WWqWWplacesXWWpleaseCWeWpointtWWpolicies-WWpolicy-basedMWportableWportion޳W[WpossibleވWޒWWW WWWLWPWQW\WgWhWWWWpotentiallyަW#W>WEWpotentiallyconfusingtextަV>Vpotentiallyonlyredundant#VEVpower޻WcWuWWWWWWWpractical WW"mkeditorial improvementmAccepted 2004/07/13 2004/06/08MarkednEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_16`8a4.1.8b-Adopt the C802.20-04-44 Text for this SectioncaRemove reference to the "MIMO" Example. The text in C802.20-04-44 is all that needs to be said.d230g2492i Joanne Wilsonj*delete the sentence "As an example, MIMO."k'see reply in record 181 to comment #140mAccepted-Modified 2004/07/13 2004/06/07MarkedoEEshwarF Pittampalli^Technical, Binding_16`10a4.1.9b$Replace the word "should" with "may"caThe two parts of the sentence - starting at line 10 - may appear to be contradicting each other.d185g2350i Joanne WilsonkThe two parts of the sentence are not contradictory. The statement is intended to be a recommendation, but not a mandatory requirement.mRejected 2004/07/13MarkedpEAnnaFTeeGMember^ Editorial_16`9a4.1.9bg4760 2004/07/02Q_krequestedWrequireWW߽WpWrequiredWWW*W_WvWWrequirementAWhWvWWߎWWWWWWWWWW WWW!W*W4W>W^WoWWWWWWWWWrequirementsNWhWiWpWrWuWWߥW߷W߻W߾WWWWWWWWW!W"W2W=W?WeWqWtWwWWWWWWWresponsibilityNWrestހWWresultWretainZWreviewedW>==kintentߙWinterfaceWWWWWW*W2W^WWinterfacesWinterimWinternallyWinteroperabilityWinterpretEWinterpretedWWintovWހWWWintroductionWipXWrWހWWWip-basedKWހWirrelevantWisAWSWXWfWpWrWvWwWހWWWWWWW:WqWߎW߷W߾WWWWWWWWWWWWWWWWWWWWW"$pg2217i Joanne WilsonkAKThis is not an editorial correction as it allows the standard to require the use of antenna diversity at the mobile station. Many members of the 802.20 WG want to leave this as an implementation decision for system and mobile terminal providers because it entails a tradeoff between performance and both system and terminal costs.KmRejected 2004/07/13 2004/06/08MarkedqEDanFGalGMember^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. Ming4761 2004/07/02! \pbAAdopt the proposed text in the joint contribution: C802.20-04/44, quoted as follows: "The base station should provide antenna diversity, which may be an integral part of an advanced antenna solution. The standard shall not preclude the use of antenna diversity at the mobile stations."cNeed clarification to the text.d222&(qg2414i Joanne WilsonkARF requirements should not be included in this document because of their dependency on the specific bands of operation, which are not addressed in this document. Additionally, since no text is proposed this comment is incomplete, creating instead of remedying a problem in the document.mRejected 2004/07/13 2004/06/04MarkedrEDougFKnisely^ Editorial_17`17a4.2.1b"practice" => "practices"c Word choice.d148g2263i Joanne Wilsonkeditorial improvementmAccepted 2004/07/13MarkedsEEshwarF Pittampalli^Technical, Binding_17`17a4.2.1b4Provide reference(s) for "best commercial practices"c."..with best commercial practices.." ambiguousd188g2353i Joanne Wilsonkispecific references are not needed, particularly since "best commercial practices" may improve over time.mRejected 2004/07/13MarkedtEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-bindingg4764 2004/07/02!% qbBimum 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. "$& qbD 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. " %#qcThis 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/ZbasqWuWvWzW{WWWWWWWWWWWWWWWWWWWWWWWWWW#+t_17`17a4.2.1bAdopt 4.2.1 from C802.20-04.44cAAs written, the requirement seems to be an equipment requirement and an implementation issue. Not an air interface requirement. Contribution C802.20-04-44 has consensus text from a number of individuals. It can serve as a good starting point for this section.d233g2499i Joanne WilsonkThe proposed text is inappropriate for a requirements document, which is not a equipment specification. Additionally, much of the material is of a tutorial (text book) nature which is also inappropriate for a requirements document.mRejected 2004/07/13 2004/06/07MarkeduEDanFGalGMember^Technical, Binding_17`28a4.2.2bg4765 2004/07/02;uicserviceވWޒWWWW>WOW`WaWW WLWPWQW\WfWgWhWWWWWWWWservicesWWUW_WWWWWWWsetWsetsOWfWsettingރWލWWWkWtWWWWWW@WWWWWWWseveralވWޒWWWLWPWQW\WgWhWWWshallWWWWW2W3W4W>WZWgW߻W߿WW WWWWWWWWWWW+.ug2415i Joanne Wilsonktext seems acceptable.mAccepted 2004/07/13 2004/06/07MarkedvEDougFKnisely^ Editorial_17`20a4.2.2bAXThe AI shall support automatic selection of optimized user data rates that are consistent with the RF environment constraints and application requirements. The AI shall provide for graceful reduction or increase ofing user data rates, on the downlink and uplink, as a mechanism to maintain a requiredn appropriate frame error rate performance.X@A   33  33  33  33#  33-  33:  33K  33W  33cAwkward wordingd149g2264i Joanne Wilsonj 2004/07/02(* ubAAdd 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.d57Xblicentsed߾WlifecWWlimitationsWWlimited޺WWWEWWWqWWWWWlimitingWDW Wlimits޺WqWWlineޙWޞWޟWާWިW޴W޵W޻W޾WWWWWWW WW0W?W@WXWhWWWWWWWWWWWW.W2W?WJWiWuWyWzWWWWWWWWlineshouldread@VzVline-of-sightEWWline4WW.W2WlinesޘWޡWWWWWWWlinkޥWWWWW*WwWWWWWWMWNWlink-levelend-to-endMWlistedޟWުWWllcWWloadWloadedW W!W0W3WloadingޥWWWGW*W.W2W3W4WloadsWlocal޺WqWlocationWWlogicalWWloss޽W)WcWW.2v 2004/07/13MarkedwEDougFKnisely^Technical, Binding_17`24a4.2.2bA Link adaptation shall be used by the AI for increasing spectral efficiency, data rate, and cell coverage reliability. The AI shall support adaptive bandwidth allocation, and adaptive power allocation. The system will have adaptive modulation and coding in both the uplink and the downlink @A>  33v  33  33>cTerms are not defined, nor are they requirements for a system that meets the 802.20 requirements. They may be techniques used by particular proposals, but the real requirements are already described elsewhere.d150g2265i Joanne Wilsonj 2004/07/02*- ivjAJThe AI shall support automatic selection of optimized user data rates that are consistent with the RF environment constraints and application requirements. The AI shall provide for graceful reduction or increase ofing user data rates, on the downlink and uplink, as a mechanism to maintain appropriate frame error rate perfomance.J@AR  33  33  33  33RkIt is ambiguous what is the "required" frame error rate given that this is likely to be different for different traffic types and applications.mAccepted-Modified'+bareasW1WWWarrivedWWarrivingWWasރWލWޛWޟWޡWޥW޴W޵W޺W޻W޽WWWWWWWWWWWWWWWWWW WW?W@WAWBWCWDWHWIWMWNWRWSWTWbWkWtWWWWWWWWWWWWWWWWWWW*W1W@WHWIWKWMWNW^W_WeWiWjWmWpWmebtheaishallsupportdifferentmodesofspeeds250km/hitiFVVtheaishallsupportpeaksystemdataratesinexcessofthe3VtheaishallsupportsVVtheai802.20standardshallsupportthemeanstoenablelinkMVthelineshouldread?VVthemaclayershouldbeabletocontrol100simultaneousactVVthesentenceshouldreadthe802.20-basedsystemsshallprovQVVthesentenceshouldreadthisdocumentestablishedthedetaijVVthesystemshallsupportanarbitrarysetvarietyoftrafficV^VthesystemshallsupportthefunctionalityofmeasurementsiVthesystemshallmustsupportbothipv4andipv6VVthesystemwillshallprovideappropriatemacandphycapabi VVthetextshouldreadthesystemshallworkindenseurbansuVtheftWW25Fw 2004/07/13MarkedxEEshwarF Pittampalli^Technical, Binding_17`25a4.2.2b1Explain what is "adaptive bandwidth allocation" ?c-"..adaptive bandwidth allocation.." not cleard189g2354i Joanne Wilsonjdelete sentencek(see reply in record #194 to comment #150mAccepted-Modified 2004/07/13MarkedyEEshwarF Pittampalli^Technical, Binding_17`25a4.2.2b/Replace the word "will" on line 26 with "shall"cCSentences starting on lines 25 and 26 are contradicting each other.d190g2355i Joanne Wilsonj(see reply in record #194 to comment #150k(see reply in record #194 to comment #150mAccepted-Modified 2004/07/13MarkedzEWarrenFSpringer^ Editorial_17`22a4.2.2bmline should read for graceful reduction in or increase of user data rates on the downlink and uplink, as a g4770 2004/07/02-1 wjA.Link adaptation shall be used by the AI for increasing spectral efficiency, data rate, and cell coverage reliability. The AI shall support adaptive bandwidth allocation, and adaptive power allocation. The system will have shall include adaptive modulation and coding in both the uplink and the downlink.@A  33v  33  33  33  33 @ 33  33kagree that adaptive bandwidth allocation and adaptive power allocation are design techniques, not performance requirements. Also changed the subsequent paragraph to be normative instead of informative.mAccepted-Modified {bindependentWW.W2W3Windication޹WWindividual޹WWWWWWWNWindividualsWindividulaMWindoor޽WW2WEW}WWW<WWWWindor}W<Winformation޻WWWWWW WWWWWWWNWuWWWWWUW`WaWbW{WinfrastructureWinitialWWinitialtextforthisnewsub-sectionVVinsertޛWޝWީWޯWޱW޺WWWiWWWWW.WRWWWYWqWinsertaspacecharacterafterhzޝVVinsertbitrateaftertrafficclasseswithdifferentީVRVinsertdatarateafterwithdifferentޯVޱVWVYVinsertthefollowingsentenceatthispointitisfurtherasiVVinsertthefollowingtextinline1beforefigure2VVinstantWWinstead'WaWintegralIWpWbwireless޺WWWW6WEWPWhW|W߶W߾WWWWWWWqWWW W17zcthe line is confusing and neeed to be rewritten ... it seens that we're looking to say that the Ai should be able to gradually reduce the data rate or gradually increase the data rate on the downline and uplinkd213g2823i Joanne Wilsonjchange the sentence to read, "The AI shall gracefully reduce or increase the user data rates, on the downlink and uplink, to maintain an appropriate frame error rate performance."keditorial improvementmAccepted-Modified 2004/07/13Marked{EAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_17`19a4.2.2bMDelete Section or remove requirements and preserve as in informative section.cThis section doesn't belong in this document. Either delete or make it informative. We have approved spectral efficiencies, data rates, etc. The requirements document should not dictate what tools to use to achieve these.d234g2500 2004/07/13 2004/06/07|EToddFChauving4772 2004/07/02YbinzW{WWWWWWWWWWWWWWWWWWWWWWWWWW WWW59|^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d7g2258i Joanne Wilsonj'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13Marked}EJohnFChen^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d17g2258i Joanne Wilsonj'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13Marked~EDanFGalGMember^Technical, Binding_18a4.2.3c^Option 1: Page 18, line 4 - the "(TBR)" needs to be defined or else discard option-1 entirely.d58g2416i Joanne WilsonmAccepted 2004/07/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_17`16a4.2.3bg4775 2004/07/029=g2417i Joanne Wilsonkperformance of the mobile stations is also dependent on the quality of the implementation of the standard and on network design and deployment factors. Much of the text is informative and would need further detail to be unambigous.mRejected 2004/07/13 2004/06/04MarkedEHariFGantiGMember^Technical, Binding_Technical, Binding`18a4.2.3bCSupport Option 2 for "Performance under Mobility and Delay Spread."d74i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mRejected 2004/07/13MarkedEMarcFGoldburg^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d81g2689i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13MarkedEKazuhiroFMurakamiGMember^Technical, Binding_19`8a4.2.3bAdopt Option 3 g4778 2004/07/0278 bAProposed 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." Kc9All current three options need improvement. Add Option 4.d59N ktheWWWWWWWWWWWWWWWWWWWWWWWWWWWWtheapplicableblockassignmentsestablishesanupperlimitVkdetailedWWWWWdetermined?Wdevelop!W4WdevelopedWW4WdevelopingWdevelopmentWdevicesWWdictionaryWdifferentW=WvWWdifferentiatedWdifferently?WdiminishWdisagreeW?WWWYWdisagreethatdatarateismissinginthissentenceYVdisagreethatdatarateismissinginthistextWVdisagreethatthecurrentphase2requirementsarerealisticVtkseereplyoninitialcommentVseereplytocomment22inrecord44VVVVseereplytocomment3sVseereplytocomment6nVtVށVނVseereplytoothercommentsonthissection Vseereplytorecord201tocomment58V8Bc:"Option 3 is simple, straightforward, and well defined. " d87g2219i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13 2004/06/08MarkedEMarkFKlerer^Technical, Binding_17`29a4.2.3bThe text should read: "The system shall work in dense urban, suburban, rural outdoor-indoor, pedestrian and vehicular environments and the relevant channel models shall be applicable. "cA Three options are specified. I prefer option 3 with the last sentence deleted. The last sentence states " The system shall NOT be designed for indoor only and outdoor only scenarios." If the system meets the requirements it does not matter what it was designed for.  d95g2704i Joanne WilsonkFAgree. If the first requirement is met, the second one is irrelevantmAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_18`1a4.2.3g4780 2004/07/02.cstreamsWGWW4WWstrengthen WWstrengthsWWstringentރWލWWkWtWWWWWWWWWWWstyle<W߸WlWsubWW.W2Wsub-section޸W޺W WqWWsublayerދWޕWWWqWWWWWWWWWsubmissionsW1WsubmittedުWWWsubmittersWsubnetXWWsubsectionWWWsuburbanAWWsuccinctgW߿WsuchޮWWCWWVWeWsuggest޷WW WWsuggested޺WqWWWsupportވWޒWWWWWWWWWW'W3W4WCWGWLWWW[W^WWWWWWWWW4WLWPWQW\WaWeWgWhWWWWWWWWWWWeenmtandbsisnotdefineditdoesnotVsynchronizeWok burbanoutdoor-indoorAWWuse޷W<WDWIWLW߸WWW WpWWusemobileterminalandbasestationonlyandnootherabbre<V߸Vusereplytocomment87 Vusetheproposedversioninthejointcontributionc802.20-0DVVused޺WWWWqWwWWusefulWuserޤWޥW޹W޽WWWWWWWWWW WWWW W&W@WFWGW}W~WWWWWGlcindoorWinflammatoryWWinformationW1W6WCWGWW4WeWWWW WWinformativeWWWRWUWaWWWDW{WWW WWinformativeandnottestableVVinfrastructureފWޔWWWrWzWWWWWWWWW!WinsertޝWQWgWjW߿WWWWWinsertaspacecharacterafterhzޝVVV=cinsertbasedafter802.20document04-44thiscorrectsther@linternal@:ip@ipr@isistheintentofthesentencetopromotepowermanagementho@it@itisexpectedthatsystemaccesstimeswillbeaprobabalis@languageisnotthatofarequirementespeciallytheusageo@\later@layers@lists@mac@makes@may@meet@missingcaptionunderthefigure@:mpls@fneed@needfurtherclarificationontherequirement@Yneedtoconsolidatewithorrefertosection4.4.1thatdisc@vnetworks@non-relatime@not@nnotarequirementimmediatelyobviousandaddsnovalue@notsurehowthisisamac/phyrequirementssoftwareupgrade@of@Eoffered@.=CbJReplace with "The system shall work in urban, suburban and rural areas..."cc"The system is expected to work in dense...." Not clear .. And also has some redunadant informationd191g2356i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_18`2a4.2.3bHSpecify association of environments with the appropriate channel models.cZ"...relevant channel models..." association of environments with channel models is missingd192g2357i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_18`18a4.2.3bKReplace with "The system shall support both indoor and outdoor scenarios."c+"The system shall NOT..." Negative comment.d193g2358i Joanne Wilsonj'See reply in record #206 to comment #95 2004/07/02BFk'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_18`3a4.2.3b7Replace with "The system shall support at least 95%..."c-"The system shall support 95%....." not cleard194g2359i Joanne Wilsonj&See reply to record 201 to comment #58k&See reply to record 201 to comment #58mRejected 2004/07/13Marked4EEshwarF Pittampalli^Technical, Binding_18`15a4.2.3bSame as comment 35cSame as comment 35d195g2360i Joanne Wilsonk*Comment 35 is not related to section 4.2.3mRejected 2004/07/13MarkedEWarrenFSpringer^ Editorial_18`1a4.2.3bnrewrite the wline as follows The system is expected to work in rural, suburban and dense urbanoutdoor-indoor g4785 2004/07/02ZTjtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWc38ޮWVW3gppCWOWeWfW3gpp2OW\WfWWW4ޯWޱW޲W޳W޼W޽WOWWWYWZW[W]WfW~WWWW4optionsarespecifiedallbutoption3imposetrade-offbu]V4-1ޞWW4-2!W"W4-6WW4.1WWW4.1.1ޥW*W4.1.3WW4.1.5ޢWޤWW W4.1.5.1ޤWfW W5W4.1.7WW4.1.9<W߸W4.2.1޺WqWW4.4.1ިWެWJWTW`W4.4.2WWW5WGWJWSW4WWWWW5microsecondsseemstobeareasonableminimumrequirementSVVCGcthe use of dense urban, suburban and rural is confusing because dense is used to as an adjective for all three in this contstrtuion The system is expected to work in dense urban, suburban and rural outdoor-indoor d214g2824i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13MarkedEAnnaFTeeGMember^ Editorial_17`29a4.2.3bAdopt option 3.ctThe maximum channel delay spread could be much higher than 5 micro-seconds, depending on the cellular environment. d223g2218i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13 2004/06/08MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_18`8a4.2.3bMAdopt Option 2 with a minor modification as follows: ...system shall work...g4787 2004/07/02Fcn5 Microseconds seems to be a reasonable minimum requirement. Option 2 seems to be reasonable for the section.d235g2501i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mRejected 2004/07/13 2004/06/07MarkedEJoanneFWilson^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d272g2239i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13MarkedEMichaelF Youssefmir^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d282g2258i Joanne Wilsonj'See reply in record #206 to comment #95k'See reply in record #206 to comment #95mAccepted-Modified 2004/07/13MarkedEJimFRagsdale^Technical, Binding_18`12a4.2.3bPick option 3 Cbadopt4.2.1fromc802.20-04.44tVadoptoption2KVVadoptoption2withaminormodificationasfollowssystemsSVVadoptoption3މVޓVVVJVpVyV|V}VVVVVVVVadoptthec802.20-04-44textforthissectionnVadopttheproposedtextinthejointcontributionc802.20-04HVIVmVpVadoptthetextinsection4.1.5.1ofc802.20-04-44withthefV5VadoptedWWSj95WWMEDanFGalGMember^Technical, Binding_18a4.2.4bOAdd on line 19: "Implementations may support either mode (FDD or TDD) or both."c%Add a clarification on implementationd60g2418i Joanne WilsonkWe can not establish requirements on the implementations of the standard. This is outside of the scope of this document and of 802.20 WG.mRejected 2004/07/13 2004/06/04MarkedEEshwarF Pittampalli^Technical, Binding_18`18a4.2.4bClarification is needed.c"The 802.20 standard shall support..." This sentence is not clear in terms of whether the standard should have any coupling between FDD and TDD. Are they mutually exclusive? If there is any coupling, is it close coupling or loose coupling?needed.c"The 802.20 standard shall support..." This sentence is not clear in terms of whether the standard should have any coupling between FDD and TDD. Are they mutually exclusive? If there is any coupling, is it close coupling or loose coupling?g4792 2004/07/02bokaKWNWSWYWfWvWwWWWWWW WqW߶W߷WWWWWWWWWWWW WW!W*W2W4W5W=W>W?WEWNW^W`WaWeWjWkWoWpWqWtWWWWWWWWWWWWjbtechniques޴WXWiWWtechnologyާWWWWWW?WWWJRd196g2361i Joanne WilsonkThe text is clear. The standard shall have both a TDD and an FDD mode. That's the only requirement established in this section.mRejected 2004/07/13MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_18`17a4.2.4bDelete Section.cJThis is stated elsewhere (Section 4.1.3). It is a duplicated requirement.d236g2502i Joanne WilsonkyThey are consistent. The requirement appropriately appears as both a functional requirement and as a PHY/RF requirement.mRejected 2004/07/13 2004/06/07MarkedEDougFKnisely^Technical, Binding_18`21a4.2.5bDelete all text in 4.2.5.cA3"Synchronization" between MT and BS is not defined. It does not seem to be required; a technology proposal that meets all other requirements but does not synchronize between MT and BS would be acceptable. Second sentence is a "non-requirement." We don't need to specify all the possible non-requirements.3:~ktheAWIWKWLWSW]WfWhWiWjWpWrWuWvWwW|W}WހWWWWWWWWW$W%W7W:WGWNWߙWߥW߶W߷W߸W߻W߽W߾WWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW W!W"W#W*W1W2W3W4W5W=W>W?WEWIWMWNWZW^WeWiWoWpWqWtWvWwW?^technicalWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWWWW W!Wkthings3WthinkXWWthisKWLWNWYWpWwW|WWW WWW2W3W:WqW߶W߷W߾WWWWWWWWWWWWWWWWWWW WWW!W#W*W.W4W>WEWGWVWWWYW^W_WeWpWqWvWWWWWWWWWWWWWoperatorsof802.20-baseVthisisaduplicateseeinitialreplycommentqVthisisanimportantmeta-requirementwhichhasbeenthesubVthisismoredetailedthanneededforthissectionVthisismoredetailedthanwhatisneededinthissectionVthisisnotarequirementontheairinterfacebutisinstea^VthisisnotaneditorialcorrectionasitallowsthestandarpVthisproposedrequirementismoredetailedthannecessaryweVthisprovidesmoredetailthanwhatisneededinthisdocumeVRWg2266iJoanne Wilson, Mike Youssefmirjdelete section 4.2.5kagreemAccepted 2004/07/13MarkedEDanFGalGMember^Technical, Binding_18`25a4.2.6b"Change "network" to "Base Station"c)The term "network" is inappropriate here.d61g2419i Joanne Wilsonk1agree that base station is the appropriate entitymAccepted 2004/07/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18`25a4.2.6bAChaneg 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 suppog4796 2004/07/02MQ d151Ij4.2.5W4.2.6WWW4.3W4.4.1ިWJW5~WWWW50kW512kbps3W58W6nWtW~WށWނWRWTWUW[W\W]WbWcWdW62WWW68WWWW7ߏWW72W8ߝWW80WW802.20NWQWxWހWWWߙWߣWߩW߶W߽WWWWWNWWWWWWWWWW802.20definesphy/maconlyqosisanend-to-endissuetoguV802.20-basedLWߋW9W903W920W95|W}WWWWWWWWWWWzj95I97@addareferenceto3gpp2'sbcmcsstage1documenthereasfo@adoptthisremedywiththefollowingmodificationsispecify@already@alternative@architecture@WGWIWLWPWaWbWiW߽W߾WWWWWWWW WWW*W4W@WCWMW^W_WjWpWWWWWWWWW]#_ijoannewilsonmikeyoussefmirVVVVjoannewilsonmikeyoussefmrVV^c3"The physical layer provides ...., etc." Not cleard197g2362i Joanne Wilsonj(see reply in record #223 to comment #62k(see reply in record #223 to comment #62mRejected 2004/07/13MarkedEAnnaFTeeGMember^ Editorial_18`24a4.2.6bAThe system shall support the functionality of measurements in the physical layer of both the network and the mobile terminal sides. The physical layer provides a set of measurement capabilities including but not limited to: signal frequency, signal quality, interference and noise level, to support other functionality such as intra-frequency, inter-frequency handoffs, cell site selection, link adaptation, power control, and OA & M functions. c"Further clarification on the text.d224g2219iJoanne Wilson, Mike Youssefmirj(see reply in record #223 to comment #62k(see reply in record #223 to comment #62mRejected 2004/07/13 2004/06/08MarkedEAyman, Arak, Jimg4800 2004/07/02[ijoannewilsonmikeyoussefmirVVVVVVVVVV!V0VNVOVPVQVRVSVTVUVVV[V^V_V`VaVbVcVdVeVfVVV\aFNaguib, Sutivong, TomcikGMember^Technical, Binding_18`24a4.2.6bAChange to read: "The 802.20 air interface shall provide features for the Base Station to request Status and Measurement Information from mobile stations, and a "Status Response" for mobile stations to transmit measurements and status to the infrastructure."cAs written these seem to be vague equipment requirements, not requirements on the air interface PHY or MAC. The text suggested below adds an air interface requirement so that Base Stations can extract measurement or status information from mobiles.d237g2503iJoanne Wilson, Mike Youssefmirj6per previous comments, propose to delete section 4.2.6mRejected 2004/07/13 2004/06/07MarkedEDanFGalGMember^Technical, Binding_18`30a4.3bDelete the sentence. c6Redundancy in line 30 - "The AI shall be designed ..."d63g2422i Joanne Wilson 2004/07/02cGbmeasurementsWWWWWmechanismvWWwKbmechanisms@cmedium@?mib@mobilestationsshallperformwellquantitativerequirements@Omovetable4-1captiontopage11line23@mt@nearnecessary@network@)new@next@note@qofjoffline@ioperations@option1modification@^cjReplace the first two sentences in section 4.3 with the following sentence, "The 802.20 AI standard shall support system implementation in TDD or FDD licensed spectrum below 3.5 GHz and allocated to the Mobile Service. "k*eliminates redundancy and improves claritymAccepted-Modified 2004/07/13 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. d64g2423iJoanne Wilson, Mike Youssefmrk 2004/07/02ci 2004/07/13 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."cVchangebasestobasisVVVchangecpetomobilestationinthissection_VVVchangedetailedtofunctionalVVchangefigure2tofigure3-2ޜVVVchangefrom802.20tosystemrequirementsforieeestandardV߶Vchangelayertoiso/osilayersVVchangeline6shallreadforthe802.20packetmobilewirelehVVkoffsWokayWWWokaywordingVonrW|WW WW2W3W߷WWWWWWWW!W"W*W4WEW^WqWWWWWWWon-lineWoneSWWW߽WWWWWonlyAWSWW߶WW2W4WEWfWkWWWWoob*WopenW kiprefermyownproposalkVipreferoption2!VfVipreferoption2tooption1"Vipreferoption3'V(VipreferthecommentofdangaltofixthisVieeejW}WietfrWWifWWWW.W3W?WWifitmakesdoughappywhynotVifoption1isselectedthenitshouldbemodifiedperthis.Vill1Will-definedWimmediatelyWimpactWeWimplementationW^WpWWWimplementationsWWbkkNo, wireless could include unlicensed or fixed systems. Cellular implies licensed systems and are most likely to be mobile. Could agree to change "cellular" to "mobile", but not to merely "wireless".mRejected 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_18`35a4.3b"Specify maximum channel bandwidth.ce"readily extensible to wider channels..." -- this is an open-ended requirement for channel bandwidth.d199g2364i Joanne WilsonkThe applicable block assignments establishes an upper limit on the channel bandwidths. Beyond that the WG has no justification for limiting proponent's design options.mRejected 2004/07/13MarkedEWarrenFSpringer^ Editorial_18`35a4.3bDelete the last three words and end up with The design shall be readily extensible to wider channels as they become available.csA simple editorial change to elinate unneeded words. In the future is already implied when we say become available.g4806 2004/07/02X_‚*7;DJZbjހދޕŃƃǃȃՃك89:;UVWXYZ[\]^qߙߚߛߜߠߥ߲߱߷ࡃࢃࣃःृঃৃਃ੃ઃૃଃୃஃ௃ఃృಃೃഃൃඃසใໃ༃གྷ ƒÃăŃƃǃȃɃ˃̃̓΃σЃ‚2ڃۃ܃ฃ‚3bcу҃‚4ުdeԃՃփ`<߸߹ߺ ޜޞă 1AO}csupportnon-lineofsightambiguousVVsupportingGW4WWsupportsGW4WWsureWWsustainedWWsynchronizationWsynchronizationbetweenmtandbsisnotdefineditdoesnotVsynchronizeWPkthisappearstobearequirementonoperatorsof802.20-baseVthisisaduplicateseeinitialreplycommentqVthisisagoodalternativethoughmypreferenceistodeleteVthisisagoodchangefromadesignrequirementtothemoreVthisisanimportantmeta-requirementwhichhasbeenthesubVthisismoredetailedthanneededforthissectionVthisismoredetailedthanwhatisneededinthissectionVthisisnotarequirementontheairinterfacebutisinstea^VthisisnotaneditorialcorrectionasitallowsthestandarpVthisproposedrequirementismoredetailedthannecessaryweVthisprovidesmoredetailthanwhatisneededinthisdocumeVthisrequirementneedstobeseparatelydefinedforbsasweVBAkthisappearstobearequirementonoperatorsof802.20-base@thissectionimpliessomenearreal-timemeasurementonthe@thoughthisisnotatestableperformancerequirementitis@Atobeconsistentwiththearchitectureofieee802standards@understand@-weneedtogettoarealisticsetofqosclassesthatcanre@were@with@m@accepted  accepted-clarified@#accepted-modified@rejected#rejected-duplicate@superceded@€marked-bChange the sentence starting on this line to state: Handoff techniques are required to support mobility between cells, systems, frequencies, and optionally between IP subnets.cThis requirement as written places "may" requirements on the mobile station's movement! Recommended sentence places requirements on the AI. IP subnet mobility is at the network layer, hence is considered optional from an AI PHY and MAC perspective.d244g2510i Joanne WilsonjAThe 802.20 AI shall provide handoff methods are required in MBWA systems to facilitate providing continuous service for a population of moving Mobile Stations. The handoff methods shall enable mobile stations may to move connectivity between across cells, between across systems, between across frequencies, and at the higher layer between across IP Subnets. At the lowest layers, handoffs can be classified as either soft or hard handoffs, depending on whether there is a momentary service dBisruption or not.@ 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_19`26a4.5.1bDelete sentence.cA The "definition" of soft handoff given here is incorrect. Soft HO is a HO with the MS transmitting simultaneously to two BS on the RL, while two BS transmit simultaneously to the MS. Generic make before break handoff is NOT soft handoff. See IS-95 or cdma2000 for a formal definition.  d245g2511i Joanne WilsonjNchange "soft" to "make before break" and change "hard" to "break before make"mAccepted-Modified 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_19`29a4.5.1.1b8Remove the fragment: "be designed in a manner that does"c}The phrase "shall be designed in a manner that does..." is not a requirement on the PHY and MAC. Reword to clarify as below.d246g2513i Joanne Wilsonj 2004/07/02 tjA @ 33  33,  33I  33 @ 33  33  33  33 @ 33  33  33  33 @ 33  33  33  33  @ 33  33  33! @ 33'  33M  33T  33U @ 33[ B  33kLChanged the text from being informative to normative and remove ambiguities.mAccepted-ModifiedqMjmetricgWmicrogWmicro-secondsWmightQWmimoSWjWnWmineWmineprintswithpagenumbersVminimizeWminimumߎWߙWߟWߠWߡW߳WߵWWmobileZWWހW߶W߽WW WNWWWWWWmobilestations/basestationsshallperformwellquantitativVmobileipWmobilityxWޥWWmodelOWmoderateߧWmodesߙWWmodificationކWމWW3WmodificationsyWmodifyޥWߝWWWmodifythefirstpartofline8foroption2asfollowsߝVmodifythesentencetoreadthe802.20mbwaairinterfacestVmodifyingߖWmodulationߣWwWmomentaryWmonitoringWWmore W߀WߓWmoveߓWWWmovingWmsHWWWfAjprovidingWprovisionWpurelyޥWpurposeߙW߽WqcZWqosީWߞWߴWNWWWWqualityWWquantitativeWquestionWquiteީWr0030-aNWradio߶Wrandom߄WrangegWrateQWީW߉WߣW3WNWvWwWzWW\jclearQWWWclearly߄WcloseWclosed߈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}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW Wt2VVcomment3VVcomment4VVcomment5Vcomment7Vcomment72Vcomment8Vcomment9V4cwithbestcommercialpracticesambiguoussVNccellރWލWWkWtWWWWWWWWWWWcellsރWލWWWkWtWWWWWWWWWWWWcellular6WJWWWWW Wcellularwordconveysonlypartialinformation6VV VcertainlyރWލWWkWtWWWWWWWWWWWchanceW.WchangeޤWެWWBWgW߿WW WTWW 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_19`30a4.5.1.1btChange to read: "MobileIPv4, MobileIPv6, or Simple IP." Remove the fragment starting with "for the preservation..."cvSince there is a requirement for both IPv4 and IPv6, the Mobile IP support should cite both MobileIPv4 and MobileIPv6.d247g2514i Joanne Wilsonj^not necessary to remove fragment starting with "for the preservation..." as it is informative.kimproved claritymAccepted 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_19`30a4.5.1.1b Add a definition for "Simple IP"caThis term Simple IP is not well defined in this document and was developed in TIA TR45 and 3GPP2.d248g2515i Joanne Wilsonj?Add definition to Appendix A - Definition of Terms and ConceptsmAccepted 2004/07/13 2004/06/07MarkedEAyman, Arak, Jimg4828 2004/07/02 jAModify the sentence to read, "... the 802.20 MBWA air interface standard shall be designed in a manner that does not preclude allow the use of either MobileIP or of SimpleIP @A   33& @ 33,  33-  331  33@ @ 33H  33O  33}  33~ @ 33  33keditorial improvementmAccepted-ModifiedFjnothingTWWnotification޹WnowWnumberMW߄W߉WߙWWWnumbers4WW߹WoccurZWoccurringZWofHWOWZWyWWރWޣWޤWޥWާWިWީWެW޺WWWWW WLW߄W߉WߙWߝWߞWߣWߴW߽WWWWWW3WKWNWSWvWWWWWWWWWWW WofflineWofingvWokޘWޡWަWާW޲WWMWokexceptdellsshouldbecellsVokifoption4isselectedhoweveripreferoption3޲VoldZWon@WWWZWރWޡWިW޺WWWWW߀W߄W߉WߋWߔW߯WWFWvWzWWWWonceޣWoneWWzWވWާWޮW WWWoneoptionneedstobepickedratherthanonlyeliminatingޮVcdefinesދWޕWWWqWWWWWWWWWdefining߾WdefinitionWWWGWYWWW.W4WWWWWdefinitionsވWޒWWWLWPWQW\WgWhWWWdefinitonW.Wdelay)W*WJWcWdWWdelaysWWdeleteRW{WdeletedWWWdeletionUWWWWWdeliverOWfWdemandTWWdenial>W Wdense1WAWWWdependEWWdependingރWލWWJWUWkWtWWWWWWWWWWWWWWdependsW0WdeployWdeployedEWWdeploymentWdeploymentsވWޒWWWLWPWQW\WgWhWWWdescribedWCWeWwWWdescriptionW(W.WbWFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_19`32a4.5.1.1bDelete this sentence.cThis sentence is not relevant to handoff, but rather to NAT (Network Address Translation) techniques. These are implemented at higher layers than the 802.20 air interface will address.d249g2512i Joanne Wilsonk*agree that this is not related to handoffsmAccepted 2004/07/13 2004/06/07MarkedEToddFChauvin^Technical, Binding_19`34a4.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 2d9g2260i Joanne Wilsonkagree.mAccepted 2004/07/13MarkedEJohnFChen^Technical, Binding_19`34a4.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 2d19g2260i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEMarcFGoldburg^Technical, Binding_19`34a4.5.2bRemove Section cg4831 2004/07/02|sbsectorޣWWWWWWsectorsWWsecure޷Wsecurity޶WWWWseeިW޵W޺WWJWqWWselect/Wselectoption2anddeletetextdealingwithaveragerates/VselectionvWWselectivity޺WqWWsender޹WWsensitiveW_Wsensitivity޺WqWWsentWWWsentenceޙWޡWޢWޣWާW޴WWWWWW8WQWVWXWYW]WbWgWiWjW߾W߿WWWWWWWWW?WiWWWWWg2691i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEKazuhiroFMurakamiGMember^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 2d88g2220i Joanne WilsonmAccepted-Duplicate 2004/07/13 2004/06/08MarkedEMarkFKlerer^Technical, Non-binding_19`34a4.5.2bg4833 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 2d83rLbremovesentencestartingwithaqosbasedipnetworkVVVVcpartitioningWWparts,WoWpast.WWpeakޅWޏWWWWGWmWvW}W~W$W'W+W.W2W3W4W6W9W<W=WWWWg2705i Joanne Wilsonkpprefer option 1, which is to delete the section. The proposed replacement text for option 2 is also acceptable.mAccepted 2004/07/13MarkedEVincentFPark^Technical, Binding_20a4.5.2b:Option 1: Preferred. The 802.1Q section should be dropped.cA Requirements with regard to 802.1Q are detailed in the 802 P&P "5 criteria", the 802.20 "5 criteria", and the 802.20 PAR. If needed the relevant sections of those documents should simply be referenced, to avoid introduction of any ambiguity regarding the requirement. d158g2768i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_19`34a4.5.2bRemove Section.ciWe support Option 1, removing this section. It does not seem relevant to the air interface requirements.d250g2516i Joanne WilsonkagreemAccepted 2004/07/13 2004/06/07MarkedEJoanneFWilsong4836 2004/07/02 bADelete or use the following text: The system should support a mechanism that allows the managment of backbone traffic and/or the distinguishing of traffic for wholesale partners in a wholesale environment. One that mechanism that is available at layer 2 is 802.1Q tagging. cTwo options are specified. The objectives specified can be satisfied in a number of ways and no single mechanism should be mandatory. I, therefore, support either option 1 or option 2 modified as below.d96_wbmandatoryWWWmanner޺WZWqWWWmappingWWmasks޺WqWWmaximumޥW޺WW7WFWW*W^WqWWW Wmay޾WWWWWWWWWWW,WIWWWWWWWDWNWoWpWWWWWW Wmbps W!WGW~W!W"W4W=WWmbsޥW*WmbwaޗWޙWW߾WWWWWWmeans>W WMWmeasureWWWmeasured5WWmeasurementWWWWW4bwide-areaWWWWwiderWBWTWWWWWwill޺WWWWW WW0W?WaWWWWWWqWwWyWWWWWKkpreferoption1whichistodeletethesectiontheproposedVpreferoption3butcanlivewithoption2SVpreferotherproposedsolutionsVpreferthesolutioninmycommentsVprefertodeletethesectionorretainoption3ZVpreferableXWfWߎWpreference.W1WVWWW^Technical, Binding_19`34a4.5.2bDelete 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 2d273g2240i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEMichaelF Youssefmir^Technical, Binding_19`34a4.5.2bRemove Section cg4837 2004/07/025g2260i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEToddFChauvin^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 frameworkd8g2259i Joanne Wilsonkagree. mAccepted 2004/07/13MarkedEJohnFChen^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 frameworkd18g2259i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEMarcFGoldburg^Technical, Binding_20`7a4.5.3bRemove sectiong4840 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 2d284callowingދWޕWWWqWWWWWWWWWallowsLWWalreadyWBWwWWalsoWW W1W<WWW߸WWWWWWWWWalthoughW.WalwaysW WߺWWambiguityWWambiguousWWW!W*W+WWWW"WdWkWsWanރWލWޛWޡWީW޵WWWWWW7WAWFWGWLWXWkWtWWWWWWWWWWWWWW4WRWtWWWWWWWWWWW WWWWanalysis.WWjcadditionalިWWWJWaddress]WWWaddsWjWWWWadjectiveAWWadoptވWޒWWWW1WLWPWQW\WgWhWWWadopted|WWadoptedchangeswerenotmade|VVadvertisedWWWadvocatingދWޕWWWqWWWWWWWWWadvocatingaspecificmechanismforseparationoftrafficdoދVޕVVVqVVVVVVVVVafterޝWެWWWQW߼WWW1WTWWagainst W>W WWaggregationWaggressiveW1WPcLkagreeifthefirstrequirementismetthesecondoneisirreVagreethatadaptivebandwidthallocationandadaptivepowerwVagreethatbasestationistheappropriateentityVagreethatburstyandnon-burstytrafficneedstobesupportVagreethatthereistoolargeaspanbetweenpeakandaverag=Vagreethatthisisnotamac/phyissueandshouldthereforeVagreethatthisisnotrelatedtohandoffsVagreethecurrenttextismoredetailedthannecessaryVagreewithcommentVagreewithcommenterVagreewithcommentsPVagreewithcomnentVagreewithrationalVagreewithtextexceptthatnegotiationoftemplatesisahiNVagreewiththecommentMVagreewiththecommentsVagreewiththespiritofthecommentbutbelievetheabovei VSkagreed@candJanother@as@bandwidths@ebeen@c802.20-04-55@?choice@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@]ijoannewilsonVVVVVVVVVVVVVVVVVVVVVVVcThis 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 frameworkd82g2690i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEKazuhiroFMurakamiGMember^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 frameworkd89g2221i Joanne WilsonmAccepted-Duplicate 2004/07/13 2004/06/08MarkedEDougFKnisely^Technical, Binding_20`8a4.5.3bg4842 2004/07/02]bremovemustorwilltomakethisaninformativesectionaVVremoveoption1andadoptoption2ޅVކVއVޏVސVޑVVVVmVnVoVvVwVxV$V%V&V'V(V)V+V,V-V6V7V8V9V:V;VVVVVVVremovesectionފVދVޔVޕVVVVV^VzVVVVVVVVVVVVVVVV!Vg2270iJoanne Wilson, Mike YoussefmirjADelete the section entirely, or only maintain the sentence, "The 802.20 AI shall not preclude over-the-air download of firmware and software updates for the mobile terminal. "@A*  33<  33*kJThis is a good alternative, though my preference is to delete the section.mAccepted-Modified 2004/07/13MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^ Editorial_20`7a4.5.3b/Change "CPE" to Mobile Station in this section.c]CPE seems like the incorrect term here. It is usually used in the context of fixed services.d251g2517i Joanne Wilsonk,My preference is still to delete the sectionmAccepted 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_20`8a4.5.3b;Make the section "informative" to show intent or remove it.g4844 2004/07/02 bACPE software upgrade "push" - an operator should have the ability to "push" a software upgrade to CPE that are currently connected to the network. The packets that make up the software image should be given a very high priority and should be coded heavily such that they have a very high chance of arriving error free at the CPE. The CPE should be capable of holding 2 software loads (the existing one and a new one) such that an operator can ensure that the "new" software load has arrived sB#afely at the CPE before deciding to switch from the "old" software load to the "new" software load. The 802.20 AI shall not preclude over-the-air download of firmware and software updates for the mobile terminal. The 802.20 AI shall support network-based bootstrap procedures, e.g., bootp.@A*  33S  33*cyNot sure how this is a MAC/PHY requirements. Software upgrades should be an upper layer issue. Suggest simpler wording.d155!cThis section seems to be a discussion Over the Air Service Provisioning (OTASP). This function, while important to equipment design and implementaiton is not a part of the air interface itself. Hence there should be no requirements on the AI.d252g2518i Joanne Wilsonj$preference is to delete the section.mAccepted-Duplicate 2004/07/13 2004/06/07MarkedEJoanneFWilson^Technical, Binding_20`7a4.5.3bDelete section.cThis 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 frameworkd274g2241i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEMichaelF Youssefmir^Technical, Binding_20`7a4.5.3bRemove sectiong4846 2004/07/02-cThis 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 frameworkd283g2259i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEToddFChauvin^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. d10g2261i Joanne Wilsonk9agree. The current text is more detailed than necessary.mAccepted 2004/07/13MarkedEJohnFChen^Technical, Binding_20`15a4.5.4g4848 2004/07/02bReplace 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. d20g2261i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEMarcFGoldburg^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. d84g2692i Joanne WilsonmAccepted-Duplicate 2004/07/13MarkedEKazuhiroFMurakamiGMember^Technical, Binding_21`25a4.5.4g4850 2004/07/02bReplace 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. d90g2222i Joanne WilsonmAccepted-Duplicate 2004/07/13 2004/06/08MarkedEMarkFKlerer^Technical, Binding_20`15a4.5.4bDiscuss the section with a technical perspective and develop consensus on the necessary and sufficient data, its collection frequency, data aggregation and reporting frequency. cAThis section seems to have 3 options. However Option 3 does not seem to be a standalone section. I prefer Option 2 as a starting point. But extensive discussion is necessary to decide on the exact set of parameters and on data aggregation and reporting intervals and techniques. d97g2706i Joanne WilsonmAccepted 2004/07/13Markedg4852 ^cwithWWWWWWWWWWWWWW 2004/07/13MarkedEAnnaFTeeGMember^ Editorial_20`18a4.5.4bAdopt option 2.cSOption 2 has a better organized format which shows the relevancy of each parameter.d225g2220i Joanne WilsonjISee reply in records #278 and #279 to comments #97 and #157, respectivelymAccepted-Modified 2004/07/13 2004/06/08MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Non-binding_20`15a4.5.4b>Remove "must" or "will" - to make this an informative section.cOA&M requirements are equipment requirements, not Air Interface Requirements. This section should be informative to show the intent of the service providers attending 802.20. If there are requirements on the AI or on the MIBs these could be stated.d253g2519i Joanne Wilsonj'see reply in record #278 to comment #97mAccepted-Duplicate 2004/07/13 2004/06/07MarkedEJoanneFWilson^Technical, Binding_20`15a4.5.4g4855 2004/07/02EVincentFPark^Technical, Binding_20a4.5.4bANThe AI shall provide all the hooks to enable the provisioning and collection of metrics, so that the network operator can effectively control, monitor, and tune the performance of the 802.20 air interface. Provisionable paramenters, performance metrics, and other OA&M values shall be made avialable through a standards compliant MIB.Nc\The parameters and metrics cannot be properly defined before the air interface is finalized.d157g2767i Joanne WilsonmAccepted FbthatWWWWWWWWWWHjseereplyinrecords278and279tocomments97and157respVseereplyoninitialcommentVseereplytocomment3sVbReplace 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."caAll options are overly detailed with respect to specific statistics that need to be accumulated. d275g2242i Joanne Wilsonj(See reply in record #279 to comment #157mAccepted-Duplicate 2004/07/13MarkedEMichaelF Youssefmir^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. d285g2261i Joanne Wilsonj(See reply in record #279 to comment #157mAccepted-Duplicate 2004/07/13MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMemberg4857 2004/07/020UbcolumnsW!W"W1WcombineslWcommaWߺWcomment WWcommercialWWsWcommitmentsWWWNWcommonWWWWWcommunicatesW߽Wcommunication޺WqWWcommunications޻WuWWcompatibleWWcomplementedWW8jseereplyinrecord279tocomment157VV^Technical, Binding_22`23a4.7bClarify this requirement or make the sentence an informative lead-in to the paragraph. It could be done as follows: "The AI is intended to support multiple protocol states with dynamic transitions between states."cHow is the requirement for "fast and dynamic" transitions between states measured? This sentence should be clarified, since it is confusing to the reader.d254g2520i Joanne WilsonjAThe AI shall support multiple protocol states with fast and dynamic transitions among them. It will shall provide efficient signaling schemes for allocating and de-allocating resources, which may include logical in-band and/or out-of-band signaling, with respect to resources allocated for end-user data. The AI shall support paging polling schemes for idle terminals to promote power conservation for MTs.@Af  33_  33c  33e @ 33j  33f 2004/07/02keditorial improvementmAccepted-Modified 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_22`26a4.7bgChange to read: ...shall provide power conservation features to improve battery life in idle terminals.cIs the intent of the sentence to promote power management "hooks" in the air interface? The requirement should not mandate any particular technique to achieve this.d255g2521i Joanne Wilsonk_this is a good change from a design requirement to the more appropriate functional requirement.mAccepted 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_22`29a4.8b?Delete the requirement or make it more quantitative than it is.cThe requirements are vague and unmeasurable. We recommend deletion. There is also a fragment that should be removed, starting on line 9.d256g2522i Joanne Wilsonjprefer to delete the section. 2004/07/02 0ijoanneWWWWWWM6jshallmustWshouldOWWWqWW޵WWWW WHWLWMWUW߀W߄WߋWߙWߪW2WWWWshoulddeleteandsystemarchitectureinbothlines3and132Vshown3WsideWsightWsignalWsignalingWWWbterminateWWterminology޵WWtermsW^Wtests޺WqWWtextޙWޚWޤWޥWިW޶W޺W޻WWWWHWIWOWPWfW~WWWWWWWW W*W/W5W=WAWJWfWmWnWpWqWuWWWWWWWWWWWthanަWާWWWWWWMWTWWWWW>W?WAWHW_WWWWWWthatތWޖWޡWޢW޶W޺W޽WWWWWWWWWWWWWWWWWWWWWWWDWFWLWZWiWsW{WWWWWWWWWWWWWWWWWWWNW^W_WqWvWWWWWWWWWWWWW>dÃ6dՃÃ6eփÃ6f5Ã7g߿Ã7 hÃ70iÃ7@jÃ7PÃ7`Ã7p]kÃ7lÃ7mߌ6Ã7n7Ã8o8Ã8 ށgÃ80p߳Ã8@qÃ8P^rÃ8`_sÃ8p`tÃ8u Ã8vߍ9Ã8w:Ã9x;Ã9 ނߴhÃ90yߵmAccepted 2004/07/13 2004/06/07MarkedEDanFGalGMember^ 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 ?! d40g2379i Joanne WilsonjThe reference list has not been kept up to date. It should either be updated on only reference the PAR and 5 Criteria documentsmAccepted-Modified 2004/07/13 2004/06/01MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_23`5a5bDelete this reference.ckThis contribution is not referenced anywhere in the requirements, and is not approved by the working group.d257g2523i Joanne WilsonmAccepted 2004/07/13 2004/06/07MarkedEAyman, Arak, JimFNaguib, Sutivong, TomcikGMember^Technical, Binding_23`9a5bDelete this reference.g4862 2004/07/02bdeletethesentenceVVVdeletethespectralefficiencyathigherspeedsthanthosesVVVdeletethetwolistedcontributionreferences03/45r1and03ުVVVdeletethisreferencedVeVVVVVdeletethisrequirementshallbemetevenifthesessionsarVBV VdeletethissectiongVdeletethissectionorretainoption3]Vdeletethissentence]VVVdeletingfW5WdeliverWWdeliveredWWW_WdeliveryWWWWWWWNW^WWdellsWWdemandWNWu )ctheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!WjupdatesWupdatingWuplinkeWߣW3WvWwWzWuploadingWupperyWߙWuseRWWީWWW1WLWߣW߽WWWWWWLWWusecommonterminolgyacrossdocumentVusedefinitionsfromareferencedindustrysourceaddadopteVuseofthewordwillisnotappropriatesuggestthefollowinߣVuseoption2injointcontributionRVuseoption31Vuseprotocolinlayers1and2Vusereplyinrecord80tocomment212VVusethefollowinginthisdocumentthetermsystemspectralVusethefollowingtextVusethetextofthefirstsentenceofthesuggestedremedyr߽VckThis contribution is not referenced anywhere in the requirements, and is not approved by the working group.d258g2524i Joanne Wilsonk0Terminology already incorporated into Appendix AmAccepted 2004/07/13 2004/06/07MarkedEToddFChauvinGMember^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 ig4863 2004/07/02YteeCDEFGHIJKރ4emp̓ d1s 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.d1 cBs 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.]cwindowW1WwirelessW WhWWWWwirelessbroadcast/multicastservicesneedtheabilitytotuVVwithރWތWލWޖWޚWޛWޣWޥWާWިWWWWWWW WWWW-WGWOWPWUWYWkWsWtW{W߾WWWWWWWWWWWWWWWWW*W4W?WJW_WfWsWWWWWWWWWW?kchoiceWclarifiedWWclarifiedtextVclarifyingWclarityߥWWW WWWWclassWclassesWclassified߷WclearpWrWWWWW"WWWWWg2252i Lalit Kotechaj#1 supercedes this commentmAccepted-Duplicate 2004/07/13MarkedEJohnFChen^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.d12g2253i Lalit kotechaj Comment #2mRejected-Duplicate 2004/07/13MarkedEJohnFChen^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. 3d13g2254i Lalit Kotechaj Comment #3m Superceded 2004/07/13 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.d11GMarkedEJohnFChen^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 bandwidthsd14g2255i Lalit Kotechaj Comment #4m Superceded 2004/07/13MarkedEJohnFChen^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d15g2256i Lalit Kotecham Superceded 2004/07/13MarkedEJohnFChen^Technical, Binding_14`16a4.1.7.1bRemove this section. cg4870 2004/07/02g2257i Lalit Kotecham Superceded 2004/07/13MarkedEJohnFChen^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d17g2258i Lalit Kotecham Superceded 2004/07/13MarkedEJohnFChen^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 frameworkd18g2259i Lalit Kotecham Superceded 2004/07/13MarkedEJohnFChen^Technical, Binding_19`34a4.5.2bRemove Section cg4873 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@WAWBWCWEWFWGWMWNWOWTWWWXWYWZW[W\W]W_W`WbWcWdWeWhWkWmWoWpWrWtWvWxWyWzW߾WWWWWWWWWWWWWWn>ctrueWWtryingWturnވWޒWWWWWLWPWQW\WgWhWWWtwoއWޑWW,WGWYWoWxW&W)W-W/W4W8W;WoWWWWWWWtwooptionsarespecifiedtheobjectivesspecifiedcanbesaVtypeOWfWtypes޳WCW[WeWtypoWWtypobasesVVubiquitousEWWudpވWޒWWWLWPWQW\WgWhWWWun-meetableWWunachievableW0Wg2260i Lalit Kotecham Superceded 2004/07/13MarkedEJohnFChen^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. d20g2261i Lalit Kotecham Superceded 2004/07/13MarkedEDanFGalGMember^ Editorial_7`3a2bCAdd "Figure 2-1. The Vision of Integrated MBWA" under the figure.cMissing "Figure 2-1" captiond21g2342i Lalit KotechamAccepted 2004/07/13 2004/06/01Marked2-1EDanFGalGMember^ 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."  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 2d19z1bsoft;W߷WWsoftwareWWsolution޶WWIWWWpWsolutionsWWsomeޙWWWWW.W2WWWspaceޝWWWspacing޺WqWWspansޡWWspecificޫW޺WWWWWSWqWWspecification޺W߾WqWWspecifications޺WqWWspecifiedޣWޥW޺W޽WW?WEWWWWW*WqWWWWspecifyރWލWWWWWW5W7W8WkWtWWWWWWWWWWWWWWWWWWWWW W WWWg2362i Lalit KotechamAccepted 2004/07/13 2004/06/01Marked3-1EDanFGalGMember^ Editorial_10`1a3.1.1b"Change " Figure 2" to "Figure 3-2"c Incorrect reference to Figure 2.d26g2365i Lalit KotechajsAlso "Figure 2" needs to be renamed as "Figure 3-2" along with reference change suggested as aprt of this comment mAccepted-Modified 2004/07/13 2004/06/01MarkedEDanFGalGMember^ Editorial_11`10a4.1.1b%Insert a space character after "(Hz)"c%Insert a space character after "(Hz)"d27g2366i Lalit KotechamAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^ Editorial_12`6a4.1.2b)change to: "duplexing schemes (FDD/TDD)"cline 6 is "Duplexing schemes"d30g2369i Lalit KotechamAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^Technical, Non-binding_14`19a4.1.7.1bA=insert "bit rate," after ".. traffic classes with different" =@4880 2004/07/02/c!Missing caption under the figure.d23Lbt$WFWtableޞWޟWޣWޥWްW=WfWWWWWW*W3W5WXWWtaggingWtakeWWWtaking޺WWWqWWtargetWWWWtargetedWWtargetsWWW.W2W3W_WtaxedWWWtbdLWWtbrOWfWtdd޾WWWWWCWWWWWtechnicalWjwithin߄W߽WNWwithoutWwordߣWߧWwordedߪWwordingkWworkވWߝWworking4W5WIW]WdWߘWwould@WދWާWߙWwouldliketoseethepreviousdefinitionandreviewbefore@VwrittenOWwrongWwronglyQWwwwNW~Wk1AWhWkW"WWW W.W1WW1-1AW1.25 W1.3AWhW100%W101WWW111%W&W135GW138_W139AW140nW<jalternativezW|WaltogetherWalways޹Wam޶WambiguousޥWamongWanzW~WީW߽WjWnWzWWWand4W5W@WIWOWTWZW]WeWgWިWީW޵WWLW߀W߄W߉WߓWߔWߘWߙWߞWߣWߩW߯WߴW߽WWWWWWWW W2W3WFWNWvWwWzWWWWWWWWWWWWWWand/or߽WWanotherBWZWanotherduplicateBVantennaWanyzWWWߓWKWappear߹WappearsޥW2WappendixWWapplicableWapplicationvWapplicationsWWFWNWapplicationstheaishallsupportapplicationsthatconformVapply WWappropriatezWߣWvWzWapprovalߘWapprovedIWdWaprtWarbitraryޥWarchitectualߙW bc:add an important attribute of traffic classes - data rate.d39g2378i Lalit KotechamAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^ 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 ?! d40g2379i Lalit KotechamAccepted 2004/07/13 2004/06/01MarkedEDanFGalGMember^ Editorial_15`9a4.1.7.1bsubstitute with a proper table.c2distorted table-like columns in lines 9 through 25d46g2404i Lalit KotechamAccepted 2004/07/13 2004/06/02MarkedEDanFGalGMember^Technical, Binding_17`16a4.2bg4883 2004/07/02 TbA> 33  33>;#imikeWWWWWWWWWWWW!W0WNWOWPWQWRWSWTWUWVW[W^W_W`WaWbWcWdWeWfWgWWWWWWWWmikeyoussefmirVVgVsg2414i Lalit KotechamAccepted 2004/07/13 2004/06/04MarkedEDanFGalGMember^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.d57g2415i Lalit Kotechaj 2004/07/02 bA1. 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. MinBimum 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 ma bCximum 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. "D 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 envirnomen bEtal 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. " 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.d56bconsistingWPWWWconsistsWW߽WWconsolidateWconsolidatetheusefulinformationVconstitutesW߽WconstraintsvWcontentionMWcontextWWcontiguous:WWWcontributionުWCWDWHWIWPWWWWeWmWpWWWcontributions޳W[Wcontrol޷W޻WWWWWWW%W߽W߾WWW WDWGWuWWWWW WcontrolandmonitoringVVcontrolsconstraintsWWconversationalW_WcoreWcorrectionsW^WcorrectlyW_WcorrespondingWWW_W 2004/07/13 2004/06/07MarkedEDanFGalGMember^Technical, Binding_18a4.2.3c^Option 1: Page 18, line 4 - the "(TBR)" needs to be defined or else discard option-1 entirely.d58g2416i Lalit KotechamAccepted 2004/07/13 2004/06/04MarkedEDanFGalGMember^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." Kg4886 2004/07/02 }jA" 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' operating states should include sleBRep-mode and in general should minimize their idle communications to the minimum. "@@A>  33  ?  33>kAStrikeout part of the text needs to be covered in addressing power save requirement in a separate section in requirements document. This helps separating "power control" and "power save" requirementsAf  33  33  33    33f k@Af  33  33  33    33fmAccepted-ModifiedncpppދWޕWWWqWWWWWWWWWpractical WWc9All current three options need improvement. Add Option 4.d59g2417i Lalit KotechajA"Mobile stations/Base 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 and ouBWtdoor (BS) to indoor (MS) operations at delay spreads of 5 micro-seconds or greater." E@A>  33  33  33>mAccepted-Modified 2004/07/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18a4.2.4bOAdd on line 19: "Implementations may support either mode (FDD or TDD) or both."g4887 2004/07/02c%Add a clarification on implementationd60g2418i Lalit KotechakThis requirement needs to be separately defined for BS as well as MS. e.g. BS will support FDD or TDD as mandatory mode and optionally may support operating at FDD and TDD mode at the same time. Similar requirements for MS is required.mRejected 2004/07/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18`25a4.2.6b"Change "network" to "Base Station"c)The term "network" is inappropriate here.d61g2419i Lalit KotechamAccepted 2004/07/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18`25a4.2.6bg4889 2004/07/02KwcimplementedވWޒWWWW]W1WLWPWQW\WgWhWWWWWg2420i Lalit KotechamAccepted 2004/07/13 2004/06/04MarkedEDanFGalGMember^Technical, Binding_18`30a4.3bDelete the sentence. c6Redundancy in line 30 - "The AI shall be designed ..."d63g2422i Lalit KotechamAccepted 2004/07/13 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. d64g2423i Lalit KotechamAccepted 2004/07/13 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."g4892 2004/07/02 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.d62(^technicalbindingVVVVVVVVVVVVVVVVVV V V VVVVVVVVVVVVVV V!VcW WWattendingaWWattributeީWRWWauthentication WauthorizationWWauthorizedWWavailableBWGW4WAWWWWcaverage@awk@bad@based@`beLbearer@break@_bws@scall@Ncell@changearetoshallbeandinsertapprovedbeforepar@clarifyawkdefinition@columns@Jcomponents@Iconstruction@convergence@copied@creates@decreased@define@defined@defines@design@designed@ydesigns@diffservmayworkwithinterfacingto3gppnetworksbutthe@does d- €marked  !/ilalitWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWWWWW W!WlalitkotechaVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V V V V VVVVVVVVVVVVVVVVVVV V!Vvg2686i Lalit Kotechaj Comment #4m Superceded 2004/07/13MarkedEMarcFGoldburg^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d79g2687i Lalit Kotechaj Comment #5m Superceded 2004/07/13MarkedEMarcFGoldburg^Technical, Binding_14`16a4.1.7.1bRemove 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 documg4901 2004/07/02EMarcFGoldburg^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 bandwidthsd78vboption1modification3Voption1preferredthe802.1qsectionshouldbedroppedVVoption3ޥV*VoptionalWWWoptionallyXWWg2688i Lalit Kotecham Superceded 2004/07/13MarkedEMarcFGoldburg^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d81g2689i Lalit Kotechaj Comment #7m Superceded 2004/07/13MarkedEMarcFGoldburg^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 frameworkd82g2690i Lalit Kotechaj Comment #8m Superceded 2004/07/13MarkedEMarcFGoldburg^Technical, Binding_19`34a4.5.2bRemove Section cg4904 2004/07/02 VcBQYhmsޅކއޏސޑޞޟޠޡޢޣޤσЃуFGfmnovwx߀߁߅߈ߋߌߍ $%&'()+,-/3456789:;ۃ܃݃‚$Rezޥަ !"#$M}~߆߉!"#*012<=>ABEFH ‚%intu{~ށނވޒާިީޫެޭޮ҃׃%&'(CN߂߇ߊߞߢߴ.?CDGIJMNOPQRSTUV\]^_`abeghރ ‚&ޯްޱ޲޳؃)*OߐߑߦߧLWXYZ[cdflF4.1.24.1.3Y߈4.1.4=Qޡ4.1.5>ޢޣ !"߉!"#4.1.5.1ehmszޅކއޏސޑޥσЃу׃Gfmnovwx}~߀߁߅߆ߋߌߍ$%&'()*+,-./0123456789:;<=ۃ܃݃4.1.6Rަާʃ#$%MN߂߄ߊ>?@ABDEFGHI 4.1.7r{˃؃&߇KLMNO4.1.7.1intu~ށނވޒީޮޯޱ޳҃'()*COߐߑߞߢߦߧߴPQRVWY[\]^_`abcdefghރ4.1.8޴+ߒikn4.1.9,ߨo4.2޺ߓq4.2.1ߩst޽̃Ӄك123Spyߎߏߝߟߠߡ߬߭߮߳ߵ ZjBbile 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/13ǃȃɃʃ˃̃̓΃σЃ4.7bcу4.8Ӄ5ުdeԃՃփ dDT=L^technicalbinding?V@VAVEVFVGVHVIVKVLVMVNVOVPVQVVVWVYV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVkVnVoVqVsVuVwVxVyV{V|V}V~VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVEEshwarF Pittampalli^ Editorial_1`13a1.2b5Delete lines 13-16 (Text beginning with 'How the...")c6Text begining on line with "How the..." is unncessary.d161g2326iKlererk%I can live with or without that text.mAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_1`20a1.3breplace with "basis"c Typo "bases"d162g2327iKlerermAccepted 2004/07/13MarkedEEshwarF Pittampalli^Technical, Binding_7`8a2bAReplace "Mobile Terminal (MT)," "user device," "mobile device," "wireless MT," "mobile wide-area stations," and "CPE" with "Mobile Station"@A> 33|  33 33>7 ading=JMOQRޚޡޢަީ݃V\]^a߻ƒÃσ؃ >BDRtઃૃೃഃใໃ΃  a 4.1.1.11.2?4.1.10@޵4.1.11޶> 4.1.11.1޷ 4.1.11.2޸޹ ߃ 4.1.11.3 4.1.11.4 4.1.11.5-.4.1.2ޟޠ4.1.3Y߈4.1.4=QޡF4.1.5>ޢޣޤ !"߉ !"#޾4.2.6[|޿4.3qƒ4.44.4.1ހƃǃȃ4.54.5.1Z4.5.27;DFJVbj}ދޕՃڃ4.5.36:CGT\^aފޔԃۃ4.5.48AjReject the comment...kAXTable 1-1 is included for information only. See exanation in first paragraph of section 1.3. (specifically lines 22-23 of page 5). We suggest keeping the requirement for spectral efficiency high, however so as to achieve the best possible standard. Spectral effficiency of 1 b/s/hz/sector can be achieved with "existing" technologies today. XmRejected 2004/07/13B^Technical, Binding_11`5a4.1.1d75g4202i&Naguib, Sutivong, Tomcik, YallapragadajAnother duplicate...mRejected-Duplicate 2004/07/13C^Technical, Binding_20`7a4.5.3d82g4203iNaguib, Sutivong, Tomcikj$Same as comment 155 - Reject CommentmRejected-Duplicate 2004/07/13D^Technical, Binding_19`34a4.5.2d83g4204iNaguib, Sutivong, Tomcik j$Same as comment 273 - Reject commentmRejected-Duplicate 2004/07/13E^Technical, Binding_20`15a4.5.4d84g4205iNaguib, Sutivong, Tomcikg@jA/i^1miqjujx^|k^ށkރ@bjޅm ވcA g ދcAgލcAgސ^ޒcA#g"ޕcA'g&ޘj(ޚ-ޞb8ޟ@1ޡi3ޣj9ޤ@6ޥbA9ަ@8ާc=ީjA?>ެjDްGI޳cM޵bO޶jP޹bAWgV޺bBYDZc[gX޻ia޽cgbAlgk^rjtFyxEcBgBmcg^cAgcAgbAcBgcgj^bAgcAgbBgmbBbBbBbBmbBbBmbBHF!1.1݃߻߾1.2ƒ1.3AɃǃ2KWXσЃ҃Ӄԃ.1.1Oޚă4.1.1459BIP]`gklރބލގ̓΃4.1.10@޵4.1.11޶4.1.11.1޷4.1.11.2޸޹ 4.1.11.3 4.1.11.4 4.1.24.1.3Y4.1.4=Qޡ4.1.5>ޢޣ4.1.5.1ehmszޅކއޏސޑޥσЃу׃4.1.6Rަާʃ4.1.7r{˃؃4.1.7.1intu~ށނވޒީޮޯޱ޳҃4.1.8޴4.1.94.2޺4.2.2޻4.2.3fpvމޓ޼޽̃Ӄ4.2.4޾4.2.6|޿4.3qƒ4.44.4.1ހƃǃȃ4.54.5.1Z4.5.27;DFJVbj}ދޕՃڃ4.5.36:CGT\^aފޔԃۃ4.5.48The requirement for minimum delay spread needs to be specifiedmRejected 2004/07/13ߠ^Technical, Binding_19`8a4.2.3d87g4552i&Naguib, Sutivong, Tomcik, YallapragadajThe requirement for minimum delay spread needs to be specifiedmRejected 2004/07/13ߢ^Technical, Binding_14`19'߷ 2004/07/13Marked^technical~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*w4.2.4޾4ߔ߯4.2.5ߤ4.2.6|޿5ߕߖ4.3qƒÃ67Tߗߘ߰ࠃ 4.4Ńߙࡃ4.4.1ހƃǃȃ89UVߚߛߜߥ߲߱ࢃࣃःृঃৃਃ੃ઃૃ 4.5Wଃୃ4.5.1Z:;XY߷ஃ௃ః4.5.1.1[\]ಃೃഃ4.5.27;DFJVbj}ދޕՃڃ^qൃඃසฃใ຃ໃ༃གྷ4.5.36:CGT\^aފޔԃۃ`rzྃ࿃ƒăŃƃ!4.5.48W?W@WAWBWDWEWFWGWHWIWKWLWMWNWOWPWQWRWVWWWYW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWkWnWoWqWsWtWuWwWxWyW{W|W}W~WWWWWWWWWWWWWWWWW ^binding+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W?W@WAWEWFWGWHWIWKWLWMWNWOWPWQWVWWWYW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWkWnWoWqWsWuWwWxWyW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW}c%Separate Peak and Average data rates d287g2259iKlerermAccepted 2004/07/13Marked~EJimFRagsdale^Technical, Binding_13`5a4.1.5.1bMove to new subsection 4.1.6.2 Average User Data rates and change text to: System average user data rates shall be in excess of 1.5 Mbps downlink and 500 Kbps uplink. cTSeparate Peak and Average data rates. Too much span between peak and average rates d288g2260iKlerermRejected 2004/07/13MarkedEJimFRagsdale^Technical, Binding_18`12a4.2.3bPick option 3 cWSystem must work under the various environments of a Macro/Micro/pico cellular system. d289g2261iKlerermAccepted 2004/07/13Marked&h^technicalbinding߀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ߨVߩVߪV߫V߬V߭V߮V߯V߰V߱V߲V߳VߴVߵV߷V߾VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V VVVVVVVVVV ]=kAAgree that there is too large a span between peak and average rates. However, there is no justification given for increasing the system average user data rates to the level presented. Obviously, it doesn't matter whether these requirements appear in the same or different sections.mRejected 2004/07/13Markedis too large a span between peak and average rates. However, there is no justification given for increasing the system average user data rates to the level presented. Obviously, it doesn't matter whether these requirements appear in the same or different sections.mRejected 2004/07/13d?kAbDbFbHbJjLcAgMbANbBgjBPcBgQcgT`WE[b\cAg^bA@g_bBgbc e^ kA gcAghgkFmkpbA"g!qbB$D%c&g#t_(ubA+g*vjA.-wjA21zc5|^7bA9g8c=bBkCcFcGc@JdMdRgQbBWgVc\F^jakAccejvChange 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/13f^Technical, Binding_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/13.&"2.2MNL؃كڃۃ܃݃߃3.1xޘ3.1.1Oޚă4.1.1459BIP]`gklރބލގ̓΃kltu׃؃كڃ 4.1.10@޵4.1.11޶4.1.11.1޷ 4.1.11.2޸޹ ߃ 4.1.11.3 4.1.11.4 4.1.11.5-.tu~ށނވޒީޮޯޱ޳҃'()*4.1.8޴+4.1.9,4.2޺4.2.2޻4.2.3fpvމޓ޼޽̃Ӄ4.2.4޾4.2.6|޿4.3qƒ4.44.4.1ހƃǃȃ4.54.5.1Z4.5.27;DFJVbj}ދޕՃڃ4.5.36:CGT\^aފޔԃۃ4.5.48?@ABDEFGHIKLMNOPQRVWY[\]^_`abcdefghiknoqstuwxy{|}~ࠃࡃࢃࣃःृঃৃਃ੃ઃૃଃୃஃ௃ఃಃೃഃൃඃසฃใ຃ໃ༃གྷྃ࿃ƒăŃƃǃȃɃʃ˃̃΃σЃу҃ӃՃփ׃؃كڃۃ܃݃ރ߃