Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0b)@0inding@cthenormativereferencesectionisblank@@00allowedtheconcatenationoftheseparat@@0coincide@entity@inserttheworddownlinkbeforemodeaandotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@HBAM3016AUG95@.annaarakWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWW#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNdougklmnopqrstuvwxyz{|}~؀؁؃؄؅؆؇؈؉؊؋،؍؎؏ؘؙؚؐؑؒؓؔؕؖؗ؛؜؝؞؟ؠءآأؤإeshwarةتثجحخدذرزسشصضطظعغػؼؽؾؿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃhariOPQRjimWWWWWWWWWWp BALLOTNUMBERCHANGEb COMMENT DATECOMMENT NUMBERd COMMENT TYPE^COMMENTARY VERSIONCOMMENTARY VERSION DATECOMMENTARY VERSION NOTESCOUNTERgDECISION OF GROUPw DOCNUMBEREDITOR'S ACTION ITEMSEDITOR'S ACTIONS{ EDITOR'S NOTEpEDITOR'S QUESTIONnEMAIL CC EMAIL SUBJECT EMAIL TO EXPORTDATE FIGTABNUMBER FIRST NAMEGROUP'S ACTION ITEMS GROUP'S NOTESy LAST NAMEMARKMEMBERSHIP TYPEREASONcREASON FOR GROUP DECISIONxREASON PROPOSEDkRECOMMENDATIONm REPORTNUMBER RESOLUTION BYiRESOLUTION OF GROUPvRESOLUTION PROPOSEDjSECTIONaSTARTING LINE NUMBER`STARTING PAGE NUMBER_VOTEVOTERBALLOTNUMBERVOTERDOCNUMBERGA Ballot NumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line Number BC,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bf20SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDecb[:I3 "Z22$&ts7 6/11/20041=w C;aTjx.;PkaTlPm_pwlaTsjt`Tuiv2PvATwDmviPx}bTykvq~zaTyPui_ ` PN %M %2I @EJOTYACXbmwBDa@EzJyOtUi[fBd|X||}q !A!VDEF(LIST3LISTA3Editorial Technical, Non-binding Technical, Binding3VDEFA((A!VDEF(LISTLISTAMember Observer OtherVDEFA((A!TVDEF(LISTLISTAApprove with no comments Approve with non-binding comments Disapprove with binding comments Abstain for lack of technical expertise Abstain for lack of time Abstain for reasons detailed in a comment field Comments only; no voteVDEFA((A!&VDEF(LISTgLISTAgAccepted Accepted-Modified Accepted-Clarified Accepted-Duplicate Rejected Rejected-Duplicate SupercededgVDEFA((A!Vt VDEF(LISTLISTLISTDT-W X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   v  V<E NALL # ` ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^_`abcdef g h ijklmnoqFMPR$@` ABCdD^EvFwGxHyIQ>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&`wanghleiUwang2@3.1@`4.1.2@a4.5@bK 9@AOKA/A0@@A-A.@A,A-Cancel@A*A+@@A* ;X( `Before importing, Find the records eligible for proposals by this Clause Editor. Only these records will be affected by the import. ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoQ:ASort by RecommenderE'` iDT_DT`DTDTDTQÃY0?ÃY@@ÃYPAÃY`BÃYpCÃYDÃYEÃYFÃZGÃZ HÃZ0IÃZ@JÃZPKÃZ`LÃZpMÃZNÃZOÃZPÃaQÃa RÃa0SÃa@TÃaPUÃa`ZBUUX  w  $,.YesNo/,  , : AM PMf  HelveticaGenevaVerdanaTimesMonacoTimes New RomanArialCourierSymbol Courier New@ A PICT,alisNAMEMSPCFPTHA9Macintosh HD:Desktop Folder:Ballot#2:802.16.2 Ballot Data9MSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataalisC-`@@XA Comment List@@*AAbout Commentary@@PACreate Comment@@fACreate and Submit Ballot@@AGlobal Field Setup@@ AEditor's Layout@@AComment List for Printing@@ AComment List for Projection@@ACommentary Version@@@AReply Comment Layout@@ ASubmit Reply Comments   A Comment ListB J  vor/ 11 against wRejected{l) none needed 2001/10/24»ETG3/4 MAC group^Technical, Bindinga6.2.XbFAdd new ARQ text found in document 80216abc_01/75 to the WG document. d339g2541wAccepted{k) done 2001/10/24 2001/09/11¼E TG3/4 MAC^Technical, Bindinga6.2.xb'Add a standalone NACK feedback message.d340g2542vneed accepted textwDeferred{l) none needed 2001/10/24 2001/09/13½E TG3/4 MAC^Technical, Bindinga6.2.xb Add RNR feedback message for ARQd341g2543vneed accepted text 2001/09/13D$aGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #{ Document #Report # B A € € € €€ €   G!MKe!MKG*fQjugD€QASDocument under Review€XAYLetter Balllot Number€^A_VoteaGlobal Field Setpb // etpb // etpb // etpb // tpb // b // b // d Setpb // Setpb // tpb // Setpb // b // ld Setpb // d(2) Save Data to Filee(3) Email Data Fileail Data File54 RB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMnD a w n w  $,.YesNo/,  , : AM PMo  w p w  $,.YesNo/,  , : AM PMq  w r w  $,.YesNo/,  , : AM PMs  w t w  $,.YesNo/,  , : AM PMu  w z w  $,.YesNo/,  , : AM PM{  w  D^"M1,,./: AM PMYyTtNnFfNALL OFMPRP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , AXLS Sheet1X5CMY m]oApFfWyHCB-wang., .lei]} A1FPTH=RPTH NAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9NFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9OFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A10FPTHXRPTHNAMEMSPCMSPCA2NAMEANumberLastFirst.USRRPTHANumberLastFirst.USRA19uFPTH^RPTHNAMEMSPCMSPCA2NAMEANumber_Lastname_FirstnameRPTHANumber_Lastname_Firstname ot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisVDEF(LISTLISTVDEF(LISTLIST(:K?@MRS Y!^"CAStartup scriptEQADelete Empty RecordsE@ @b*QA Show VotesE@@H-Already voted; submitting additional commentsQASort by Page/LineE'` _DT`DTDTDTQASort by Comment OriginatorE'` DTDT_DT`DTQADelete All RecordsE@ @b*QADelete Abstain CommentsE@ @HAbstain for other reasonsQAShow Editor's ProblemsE @'`@n* _DT`DTDTDTQASort by Comment #E '` dDTQ8 €Bied in recommending rejection on grounds of incompleteness or lack of a specific change request. (3) When you are finished entering replies, look under Scripts and choose "Find Marked Records". This will find the records for which you checked the "Marked" box. (4) Put your name in the "Recommendation by" field of each reply {for a quick method, see Appendix below.} (5) Under Scripts, choose "Export Clause Editor's Proposals". Choose the file type "FileMaker Pro Runtime Files". Enter a Cfile name of the form "BallotNumber_LastName_Firstname.USR", where "Name" is your name. (6) Email the exported file as an attachment to: --------------- Appendix: Using "Replace" in Commentary You can replace everything in a particular field over a batch of records. For example, clause editors might not want to type their name in the the "Recommendation by" field each time. Here is a solution to the problem illustrating the use of "Replace": *Finish entering your data. *Find the bacAEditor's LayoutB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMYesNo/,  , : AM PM Dp=u Av 2 72w27+-f3%:EAFAGA' Submitted by:€QASDocument under Review:UFirst (Given) NameVLast (Family) NameWBallot Group Membership Status:€XAY#Letter Ballot Number or Ballot Code€ZA[ email address€\A] telephone€^A_Vote:`(1) Create Comments€aAHCreate and Submit Working Group Ballot or IEEE Balloting Center CommentsH@AR  33& * Rg2*t {EQFAImport CommentsENALL OTABS# ` ABCDEFGdH^I_J`KaLbMcNOPQRgSiTjUkVmWnXpYvZw[x\y]{^_`abcde f g hijklmnoQGA Email fileE)?@ @A owner-stds-802-16@majordomo.ieee.org The comment file name should include the Letter Ballot Number and b ABCDEFGHIJK^L_M`NaObPcQ  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abdefghijklmnopqrstuvwxyz{|}~؀؁؃؄؅؆؇؈؉؊؋،؍؎؏ؘؙؚؐؑؒؓؔؕؖؗ؛؜؝؞؟ؠءآأؤإئابةتثجحخدذرزسشصضطظعغػؼؽؾؿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃'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\{]^_`abcde0\A^technicalbinding@.bas@capacity@classic@ is@Dreceiver@hthis@cand@:inthetableofoption4confusingcolumnheadingtrafficcl@now@thephraseshallbedesignedinamannerthatdoesisnota@+thisdocumentdoesnotspecifydetailedrequirementswhateve@with802.16allowsforatleasttwoseparate@there@these@5two@two@redefined@"there@*these@|two@e@|two@unified@ispartwiththemeshmodeisputtingtheunified@guagesyntax@tclanguagesyntax@u@|tofitclanguagesyntax@nguagesyntax@eparameterrcvphyarenot@|tofitclanguagesyntax@phyarenot@|tofitclanguagesyntax@arenot@|tofitclanguagesyntax@onthislineshouldread@typosubscriptyinformulanyky@ 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)r@B@2@Iؚ@@ @@9P;9P;9P;9P;-@q @z @P;;P;;P;bleisnotreferencedinthetextnorhasitanymeani@dthetermburstprofileisdefinedinthestandardasdefinit@toclarifydocument@d@B@2A@@@cJ@c@M @ @3P;@3P; @3P; @3P;7WNWWWYWbWdWeWhWWWWWWWWWWWWWW)W/W5W8W=W>WBWDW`WhWmWWWWWW?WgapWWWW WW#W$W%WgenerateWgenerated4W6WWWWgeneratingWgenericWgetOWWWgetridofdashthisisaproblemallthroughoutsection6.2OV4/ RM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMBkS-X bWmkwj,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€ ( EToddFChauvinGMember^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. cg2609 2004/06/11achieved. g08.952.1810g.952.1810gMember123g2535 2004/06/08Zd124g2536 2004/06/08[d125g2537 2004/06/08\d1267 2004/05/10\d126; @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=A.ayman@dan@%john@todd@naguib 6naguibsutivongtomcik@pittampalliصyuza@^bindingؿeditorial@/technicalR-ethustheaggregatedatarateper@aggregate@allow@as@bearer@)chanegtheentiresentenceasfollowsthephysicallayermea@changefigure2tofigure3-2@changetoduplexingschemesfdd/tdd@concerned@,definition@ downlink@frequency@#global@insertbitrateaftertrafficclasseswithdifferent@limited@monitor@optional@performance@rate@requirements@restore@should@stations@the@this@through@use@$c120km/hr@2@21@above@and@arq@because@column@conditions@definitions@efficiencies@enough@implementation@2@ BD VOTEREMAILpDs`jA.nA%€B?€A €CC@======6_BdD`@4AFF*KL)QaA0@./////./////qq@@jAqcA%jBDkBZq@<jUq@q@qcMq@qcjqHBq@l_qkCq@qbAjBqjAfkAgq@vqcqboq@Pq@Giq@qPqjA q@qbq@abAqcr@Or=^6r@GprB@jA|rE@N^HrHPqrR@rSbjrT@jSril1rt@'r@Irl4r@bAjB[kA\ 2002-04-15Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15  w  $,.YesNo/,  , : AM PM  w AaBSn DyRoxp zqr srtyuB+zy*{QbSzaq@Hg@@PB s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMXY!€aACommentary Version@A* ww  ww*}Commentary Version # Version NotesCommentary Version Date B A€€€888r ysrtyuB+zw*{EV|GIU}n~pI~YjR[7iaGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #fFJ I 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK w  $,.YesNo/,  , : AM PMA%x  Yx% ^%  _l%@ l`l@% j%0  al0% cl%  bl@GY^6i7w"#$A=CEw€\€a@5BG4M1R/YOAC+'@€BD8, consequtive in time, of a preamble and data subchannels. --------------------------------------------- 8.3.6.3.5.2.3 should be handed to a clause-editor to be entirely rewritten. ItC needs substantial additional information on how to do this type of rotation in TDD, and it shouldn't use the word frame for allocations. How it will fit under the MAC etc.. (i.e. it needs definition on how this shifted superframe structure fits in with TX/RX boundaries)cH3  @BBA^_`abc€XXXXXXXXACreate and Submit BallotB    E 3 $,.YesNo/,  , : AM PMF 3 $,.YesNo/,  , : AM PMG 3 $,.YesNo/,  , : AM PM'   ^AAssign EditorsE 5 4 3 2 1 0 / . -  ,  *  )  (  ' & % $ "    !Q7AShow All Records in OrderE '` dDTQ8A Export Clause Editor's ProposalsE OFMPR$@` ABCdD^EiFmGjHkQ9A Import Clause Editor's ProposalsE NALL OTABSW@# `BBXXXXYYYYZZYYZZp` "Guillemette" GuillemetteQAAssign Editor 11E@[@!r@a11.@a11.@!r@a11.@802.16.1/D1-2000Q`"11"^52_ 8.2.1.2.5n'tuWdownstreamuWexistuW6M<?ACreate CommentB    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM   X , : AM PM      ~LA+Commentary: The IEEE 802.16 Comment ManagerA*by Roger Marks *@A> ww ) ww> AICreate and Submit Working Group Ballot or IEEE Balloting Center CommentsI@AR  33& + RN#Version: <<ACIABB>> (<<ACIABG>>)OView Comment ListA5For help, see 5@A> ww 4 ww>Xhttp://WirelessMAN.org B A   €€A>  ww    ww>AGo To Create Vote Page@A> ww  ww>UV sBl# #I  alI# cl#O  blO# Bmv#?  @iv?# sj{#/ Dkv/# 8w#,Cjv# 0x#  2y# 2# 6{#w Inw# qp# g 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# #T  T# d# ## ## ## #d ^d#  _l#  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€           5/1 3      6 $" &,)+-*,6{7TypeReason k b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PM-dG | w  $,.YesNo/,  , : AM PM}  w ~ w  $,.YesNo/,  , : AM PM  w  w  $,.YesNo/,  , : AM PM  w A^a):|+=9}R~T=b=NR?+M^ance'd303 2001/08/28G6AReply Comment LayoutB U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]     [A, HH HH*<*G!!!!!!!!1111111111 11 11 11 9999 99999999BBBBBBBBJJJJJJJJJJJJRRRRRRRRRRZZZZZZZZZZZZ ZZ!cccc"cc#cc$cc%kkkk&kkkk'kk(kk)kk*kk+ssss,ssss-ss.ss/ssB0{{{{1{{{{2{{3{{456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmZ\ Cnopqr!!s11tBBuRRvccwssxyz{|}~D[] Ek0>nk&8n]n]n!=700UnUnUfa&fH!1fQ!H,bH,Hn\X8FU7=nXnH7%fQH 7k=8HnX10kHbHHgfn=\HX7X8HHf\]?no`_`_`_`_`_`_`_`_`_`_`_`_`_`B]n` [    `    `    `n&0n4WUfZ _ZZZ._ Z)$')d)$')d\^ G)')$h#`` ) )B)y}_ Z ' ' Dyy3sy~[_  )  ) B|uv7~qu|t_Z ( ( Brz}rs9|pr}up|_ ` ) ) Bzprypq~<yppy~pps`_ ' ' @rpp{upp|?vppuvpzZ[ ) ) Ezpt}rppyAsppr}~pr_ _ ' 'Bqp|ypvB~qpyxpz[ ` ) ) BHxpvups@|ptqpr_ Z # #@qp~}rpq~Iypq|ypz_ _E BEB`E BEBmE 'BEBmxpvyp|SX&&Xvpqpr` [  A Z Zqpy8=SHHspzZ _  @  `  `xpv,5^kn~qpr_ [[  _Z`l[  __Yo[ 6__[oqpqrpsbfS=X|pvzpy_ _ ' ) Bxpq}wpq}=]_ IXU7Uyp{zqppq`_ ) ' Bqppq}~p{=TW\fvpr}qppxZ [ ' ) DwppsspxfgT0spw}qpq`  _  '  'A~ppszpu08]n%7~qpp~}qpxZ _ BBEBm BBEBm 'BBEBmvpsppsHQH|ps}qq` [ `  ` _~psvq}Dyz~sx_ _  Z  Z [Jvu|{9to_Z_o__[Z__[^o__[Z__[^o_[^Z_`Z^o~v }~o_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`m`                                                                             @lBB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB^` K@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@B_ fXX]XfkJ78H7k=aXH 007U!,7kX8HXU7TT8X7TX77XXXf77`QHU8bk1TnaXfgWU77L7%7XX\ n17&7nbT] Xb!78=HUUXWUTX7 X7TY07=\7Xk Q%QX777b]1n=5n7H8Q!8nn_a M7!Qn=!H% 7TX,XfUXn,7,a bHb7jn &HU\TX$WT878gnn8H W8L7AUXHn8nH,H88N 7X&78=;XT%X7=7&0&0n, n!7HX00T(TXfnn777 H8& X7T7778n XTX778Tbkb H=X!`b O=T TXM*HU7T7&Q= 7Tn7%UW& XTX.7,n7&H%H8,X7gn7 TXT7A78nXH&=TXf7&Q7 PXTX 8n7]&]n7TX8jUQ TXU=n7\gn3n7XHUk=7,+U XTWUH87nn3X8WU77f78 TXUn= 7ac QU7U78&QQ XUX bfb7==nX17!8717W177&7nUT TWTH8fX&k8UUn7771 XUX77j&W7 WX bR8nH7 TXT\7&XUkH8U U77TX XTXn%88=&gC!\7 WX 77nXTUnfXTagWUTgWUTi)())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())(be S))())RZ                                                    B'S66SmB3BmK63BmVEBBPE.R8|o" *e VK S) i )}=}t<  K o  e   '~tFxy}qx ZV V)Pe2 6V R `vs|zWX!Q{ps}qq  <JR 3` )  A~psuTq}84n]H5}qpp}}qpx  ) _e Z ' o xpsppr5dngspw}qpqm  l <. Vqps~yptk]gX=upqzpy  I: . i J  B )3Sxppq}spwU7fU7xp{zpr V _  Z` l  ;   6qppq}}p{W=ef]{puzpz o  oZ  `2  "  `xpX $%       !ACommentary VersionB ( a w hh h h h h  h hhhhhhhhh!hh$XX,XXXX)X+X5X3c Uq}wpq}nf]1&}qpr 6  <`  ' _m N  */B 6qpqqpsH7Q78spz  lZZ ) `6   ' @_ xpuUQFupqpr V  `_  Z F  ) B qpxLxpr}zpz B ') Io  `P  " B xpwzqp{Q{puqpr BB' B e39 *@ qp~}spq}S}qppqyxpz@;)Bm e 'B  VzpvvpsQspps}qpsE '' R) Zi m   B; rp}zqppuUuppvvp|S  _6IN3_ )`EBmO '_ zpt}sppxQxpqz~ppt `R V)*NO @BYm  B 6rpp|vpp{P{ps}vp|6  ;  oB  E@` 3_zpszqq}L}qv|t oV NEBBZ m <rz}ssCtz~oI)"Ie6)6_cBB@@B@__@BlBB@l<)-V|vui [ w  $,.YesNo/,  , : AM PMA#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# c^_#  _l#  `l#m  av CgTgvh ivTjxivPk#TlPm&3Tn{&h3Po pDw6YTqp&3`Pr nTsj{tTuivcPvXTwmvPxTykvq~l6V~%AAbout CommentaryB\   A wB w I N w  $,.YesNo/,  , : AM PMO W  $,.YesNo/,  , : AM PMX $,.YesNo/,  , : AM PMPMPMPMPMPMPM   $,.YesNo/,  , : AM PM  w ` D .orgl>.;tf ZU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMk, w  3 $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz   {   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     rksa_2Wj m   n 3 $,.YesNo/,  , : AM PMo   p  w $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   '   B@\[)!r S // €TA€UA€VA€WA€XA YType€ZA[Suggested Remedy€\A ]Starting Page #€^A _Starting Line #€`AaSection€bAcComment€dAe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yA=AB=AB[Ab  !"#$%&'()*+,-./012345b& v   $,.YesNo/,  , : AM PMww   3 A0@*E0:@F {G0Z=' QkS%26U%92VLWiyl XU%92VLWiyl XXXXXX T BcAJ  !"#$J €€€ € €€ €      AGlobal Field SetupB   €€€ € €€ €           " # J  3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMs; VOTEREMAILVOTERFIRSTNAME VOTERLASTNAME VOTERMEMBERID VOTERPHONE VOTERSTATUS XML OUTPUT^abcgijkmnpvwxy{_`d    d  ^_`abcgimjkvwxy{p n!"#$%&'()*+ , - ./AMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line Number E !LISTAa) awaiting resolution b) awaiting missing input c) instructions unclear d) confer with resolution group e) editor disagrees f) pass off to other editor g) didn't have time h) defer to next round i) to do j) in progress - k) done l) none neededVDEFA((A!1>VDEF(LISTLISTAEditorial Technical, Non-binding Technical, Binding Technical (was Editorial) Editorial (was Technical) Technical, Satisfied (was Binding)VDEFA((A!VDEF(LISTLISTAMarkedVDEFA((A Comment TypeBMembership TypeCVoteDRecommendationFEditor's ActionsGComment Type/GroupHMarked`AFMRLFMRLAbb7AFMRLFMRLAdBFind DuplicatesC ReplyComments`lP <zReason for Recommendation{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes8Note: Group may also edit and export Comment Type above.€ADocument under Review:€ABallot Number:€A  Comment Date€A€A  Fig/Table# @BA5BAj  !"#$%&'()*+,-./0123467j^_ ` a bcdi"j k&m$n)pvwxy,{€€+€1€/€3€5€€6@@XB s@p.D/A First NameB GA Last NameB GAMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line NumberB GaASectionB GbAChangeB GcAReasonB GdAComment NumberB GM9999gACounterB GL2903iA 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 cAdg ccBggcAdgccBggb!bg&c)c+bAg/G4F8c;b=c?c @bB D cg BcDbFbBgJ^ KbA"g!Ob'd%PbSb&TabbDdcAEeFNgHicMkbA@mbAQqgVsbA[TtbA_UwbBYybZ{bAj^~cc؄c؇bAl؉bp،bt؍cAv؎bAug{ؒbAcؓbBؔbA@ؕbBؗbAA؛@;n 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  33fb1. 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.d23g2362 2004/06/11 2004/06/013-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" d24g2363 2004/06/11 2004/06/01!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"cconfusing,W8W؏WWWW Wconfusingunnecessarysentence؏Vconjunction WconsensusWWconsequentlyPWconsider4WconsideredWconsistent)WWconsolidate.WconsolidatedWconstrained WWSWW!WconstraintsfWconstructionWcontextWcontinuousWcontinuousisnottherightwordVyisnotclearػVconvergenceWW[W`Wconvey،WconveysWconvincingdWcooperativeغWcopied!Wcorresponding9Wcould WWSWfWcouplingWcovered~Wcovergae;WcreateWWXW^WcreatesؑWcriteriaبWcurrentWW+WCWXW]W^WWcurrentoptionshaveinternalinconsistenciesneedtoharmon+VcurrentlyWcurrentlyknownattackscurrentattackswereunknowntopastVdata WW/W5W7WUW]WjW،WئWضWؿWWWC 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 ;`@Ftomةփ0v؁1.1klmت1.2noثك1.3Opجحڃ2qrstخدذر2.2uwxyz{|20؎1.11.2>?4.1.2%&4.1.4'4.1.5()*4.1.5.1 +UVW]e4.1.6,-Pf4.1.7.Q^4.1.7.1/123456789Xg4.1.8:4.2@4.2.2A4.2.3BCRY_h4.2.4D4.2.6EF4.3GHI4.4K4.4.1LMN4.5.2[`i4.5.3Za4.5.4\bj50 aDT ABCDEFG^H_I`JaKbLcMdNgOiPjQkRmSnTpUvVwWxXyY{Z[\]^_`a b c defghijklmno9 @  @ @ @ @ @AAzHHddE(HH(d'`zA'dD!E Pro 3.0 - 4.1F!"HPro 5.0 A ?G USENGLSH.MPR?GUSER.UPR:g^_`abcd€€€€€8EbtransportتWtransportingmWtreatment؎WغWtrue،WWtuneاWtwo0WJWubiquitousW+WulطWWunauthorizedؙWؚW؛WWunder WWW!W+W@WCWOWRWSWWW!WunitؕWunnoticeableCWunprotected؝W@breplacethissentencewiththisdocumentprovides/definesthتVreplacewithbasisجVreplacewiththe802.20aishallsupportvariousvehicularmدVreplacewiththe802.20standardshallspecifyalltheparamVreplacewiththefollowingtextfromthejoingcontributionVreplacewiththesystemshallsupportatleast95VreplacewiththesystemshallsupportbothindoorandoutdooVreplacewiththesystemshallworkinurbansuburbanandrurVreplacewiththetextprovidedinthecontributiondocc802.VreportFWreportingFWjWrequestWrequestsaؒWrequireNWsWrequired@WAWؾWWrequiredn؟WrequirementWWCW\WbW؏WؓWؕWذWغWؾW W W W*Wrequirements(W.Wse 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 the new )bdownlink WW*W+WTWdW،W؟WؠWضWWWW"W-WdownloadإWdownloadingtWdraftWdriversKWdroppedبWdsأWdue@WؕWW؂W؍W؎WؒWؓWؔWe-mailtWeachwWؒWؓWؔWؕWeffective:WFWeffectivelyWW\WbWeffectivenessAWefficienciessWefficiency WW(W)W+WOWSWdW؇W؉Wefficient|Wefficiently{WeffortؕWeirp@Weither;WDWemission@Wemissions@WemployAWemployed?WenablesWؒWendW(WuWend-stations!Wend-to-end<WؒWend-userؔWenforceؒWenoughؕWentire'W:WFWentry)W+Wenvirnomental@WenvironmentiWenvironmentalAWenvironmentshWequipment@WerrorFWؓWؔWؕWeswWetc:W<W@WLWevaluation WW-WSWeven؏W8bthroughWW\WbWmWاW W*WthroughputFW؇Wthus)W-W؇Wtime؎WؓWtimesWtlsؗWto WWW"W$W&W(W*W,W-W8W:W>W?W@WAWCWEWFWIWJWKWLWOWPWSW]WfWmWnWoWpWsWtWwWxW{W|W؀W؁W؃W؆W؈W؋W؎WؒWؓWؔWؕWؗWؙWؚW؛W؜W؝W؟WآWأWإWئWاWةWدWرWصWطWغWWWWWWWWWWWWWWWWWWWWWWW W W W WWWW!W+W,W-Wtoavailablewithinlessthan25ms,VtooآWtopic9Wtraffic/W8W?W]WiWyWؑWؓWؔWؕWؙWؚW؝WئWؿWWWtransitions WwW؎WWtransmitted{Wtransmitter@WcarqWWXW^WW&Wartificially WWUWW#Was!W'W2W4W=W@WOWPWgWiWjW~W؋WصWWWWWWWWWWWWasanexamplemobilityisambiguousصVasdescribedintheparthe802.20standardisdesignedtosVaswrittentherequirementseemstobeanequipmentrequiremVaswrittentheseseemtobevagueequipmentrequirementsnotVsWWattribute/WauthenticationWauthorizationxWauthorized{WavailablefWWaverage WWUW،WضWWaverageuseddatagreaterisnotinexcessofexistingtechnضVaverageuserdatarateisnotdefinedanddependsonthenum،VavoidبWawk؇WawkwardmW؟WحWawkwardsentencemVawkwardwording؟VbWb/s/hz/cellOWb/s/hz/sectorOWdWbackbonezWWiWjWkWrWsWxWbearerPWg2252 2004/06/11EJohnFChen^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.d12g2253 2004/06/11EJohnFChen^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. 3d13g2254 2004/06/11EJohnFChen^Technical, Binding_12`22a4.1.5.1b#Remove option 1 and adopt option 2g2622 2004/06/11on. d1416Ba4.1.7.1/123456789Xgؔؕؽؾؿ&4.1.8:ؖƒۃ4.1.9Ã4.2@4.2.1؞ƃ4.2.2A؟ؠǃȃ߃W!W%W*W+W1addacaptionatthebottomofpage10underthefigures!V1addacaptioninline4table4-2blockassignmentsizes%V1addfigure3-1serviceattributesofmbwasystemsV1changetheheadingofsection4.1.5todataratesdownlink*V1deletethetable+V1.2+W10!W100-W11$W12+W15.W17W'W18W'W19W2 W W W WWWWWW!W"W%W*W+W4W2alternatetextforthissection+V2-1W2.0+W23$W25,W3WW!W%W*W+W-W3-1W3-2!W"W3.1W!W34562W360-W4%W4-1$W)W+W4-2%W4.1.1(W4.1.5*W4.1.5.1*W_cdefinitionsWWXW^WW&Wdefiniton]WdelayWWWأWdepending WWSWdepends،WdeploydWdeploymentdWdeploymentsWWXW^WdescribedؠWآWdescription]WؿWdesignIWKWgW؜WdesignedGWhWsWdesigningWWXW^WdesignsdWdesire{WdesiredآWظWdetailAWdetailedWW\WbWnWبWdevelopingdWdevicesdWdifferent WWSWdiffservWWXW^WdiscardBWdiscusses.WdiscussionjWdistinguish9WؓWdistorted6Wdistortedtable-likecolumnsinlines9through256Vdivided،WdodWdocumentWW4WXW^WnWqWتWdocuments0WبWdoesWW>WOW[W`WhWjWnW،WءWdoesn't؆Wdon't؆WءWdos؜Wdownlink W WWWOWSWTWdWdriven؍W\cspeedOWsplit W WWWSWTWWW!W"WsportsWspreadWsrd;Wstage؍WstandalonejWstandard!WlWتWWWWWWstandardizeWstandards W؍WWWWWstartingjWWWWW WWWstateHWstatedW Wstatement،WstatementssWstatesOWhW WstationWWstation'sWstationsWWstatisticsWW\WbW W*WstatusWstdWstraightforwardWWYW_WW'Wstreams{WWstrengthen؛WstrengthsOWWinfrastructureWinterestedWinterfaceWWinterpretedWip-dataWirrelevantWisWWWWWWitWlargeWlatencyWlayerWWWlimitWlowWmacWmac/phyWmaintainWmakeWWmandatingWmanyW|bshould(W<W?W@WAWCWIWKWfWhWiWrW؉W؍W؎WؕWأWإWبWسWWWWWWWWWWWnW؉W؍WWsideFWsidesWsightزWsignalFWأWWsignalingؙWؚW؝WWsignalling?WsignalsFWsignificantlyKWدWsimilar@WKWsimultaneous-W؎WsinceWsiteWsizetW؇Wsizes%WؖWsleep-modeAWsnr@WsoWW(W:W\WbWاWsoftWsoftwareإWsolution<WؗWWsolutionsؗWsomeW]WأWئWspace#Wspacing@Wspans'Wspecific1W@WJW؊Wspecification@WتWspecifications@Wspecified)W+W@WCWؙWWWspecify WWHWLWOWSWdW؆WWWWWWspecify2bits/sec/hz/sectorasthespectralefficiencyand VVSVnbcthisrequirementspecifiesstringentspectralefficienciesw VVSVV!Vthissectiondoesn'tbelonginthisdocumenteitherdeleteoVthissectionislackinginrfrequirementsitissuggestedt@Vthissectionseemstobeadiscussionovertheairservicep Vthissectionseemstohave3optionshoweveroption3doesnjVthissectionspecifiestwooptionsoption1makesreferenceeVthisseemstoplacearequirementonthenetworkandnottheVthissentenceisnotrelevanttohandoffbutrathertonatnVthissentencemaybeusefultoretainscalabilityisusefulVthisshouldbeanormativerequirementؤVthistermsimpleipisnotwelldefinedinthisdocumentandVthosenWبWthreeCWhWWthreeoptionsarespecifiedipreferoption3withthelasthVWWWW0WwellWWwere0Wwhat)W<WwhenWWWW‚&‚'‚(‚)zg2260 2004/06/11EToddFChauvin^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. d10g2261 2004/06/11EJohnFChenGMember^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. cg2619 2004/06/11Fg2260 2004/06/11EJohnFChen^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. d20g2261 2004/06/11EDanFGalGMember^ Editorial_7`3a2bCAdd "Figure 2-1. The Vision of Integrated MBWA" under the figure.cMissing "Figure 2-1" captiond21g2342 2004/06/11 2004/06/012-1EDanFGalGMember^Technical, Binding_8`17a3.1b(Change "must" in lines 17, 18 to "shall"c!Inadequate "must" in lines 17, 18d22g2344 2004/06/11 2004/06/01EDanFGalGMember^ Editorial_9`3a3.1g2631 2004/06/11oposalsWWWWWWpurposeWWqWqosWWWrarelyWWrateWWWWbthis WWWW+W9W;WCWKWOWSWXW^WfWgWmWtW؇W؉W،W؎W؏WأWتWغWWWWWWW W WWWWWWWWWW!W&Wthissectionshouldreadthe802.20aishouldenablemobileVthissentenceshallreadtheserequirementsshallbeconsistVthose{W؉WؓWWthreeWWturnWWtwoWWWWtwooptionsarespecifiedtheobjectivesspecifiedcanbesaVudpWWunderWWWWunnecessarilyWWWWuplinkWWWWWurbanWWuseWWWusedWWuserWWWWusersWversusWWWWveryWWvlanWWwasWwaysWWWweWWWWWWWWwellWWwgWwhatW!RRbmonitorWWFW\WbWاW W*WmonitoringAWFWMW|Wmore@WJWؽW WWmove$W*WأW-Wmovetable4-1captiontopage11line23$Vmovetonewsubsection4.1.6.2averageuserdataratesandc-VmpbsWmpls؃Wms,WAWCWPWؔWWWmsapؕWmsduؕWmtsWخWmultiWmulticombineswithotherwordsisusuallyattachedtothenVmulti-vendor@WmulticasttWwWxWyW{WWWmultiplayertWmultiple Wmultiplying)W+WmustWW WmutlipleWmutuallyشWnearؕWnecessaryjW؉WAWJWPW]WiWoperating@WAWoperationsCWoperatorWW\WbWoppositeFWoptimalAWoptimizedAWJWKWoption W W WWWWWW+W4WCWQWRWUWVWWWYW]W_WeWgWoption3+V!X4cmeansWW)WXW^WW&Wmeant<W،Wmeasured WmeasurementWmeasuresWmechanismWW[W`WiWWW)WmechanismsWmeetWWXW^WW&WmeetingdWmeetshWؠWءWmet؍WmetricsآWاWmhzfWWmib-likeآWmibs Wmicro-secondsWmicrosecondsWmimoWminimumrWsWWWmissingWW%W5W7WqWuW؈WWmissingcaptionunderthefigureVmissingcomma؈Vmissingfigure2-1captionVmissingperiodatendofsentenceuVmissingtablecaption%VmitigateWmobileOWgWqWsW{WWWWWWWWmobileipv4Wmobileipv6WmobilesWentencethedesignshallbeIVneedtoconsolidatewithorrefertosection4.4.1thatdisc.VneedtostatethatsomechannelbwsshouldbemandatoryandHVneededOWdW!g2364 2004/06/11 2004/06/01"EDanFGalGMember^ Editorial_10`1a3.1.1b"Change " Figure 2" to "Figure 3-2"c Incorrect reference to Figure 2.d26g2365 2004/06/11 2004/06/01#EDanFGalGMember^ Editorial_11`10a4.1.1b%Insert a space character after "(Hz)"c%Insert a space character after "(Hz)"d27g2366 2004/06/11 2004/06/01$EDanFGalGMember_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.d28g2367 2004/06/11 2004/06/01%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 captiond29g2368 2004/06/11 2004/06/01&EDanFGalGMember^ Editorial_12`6a4.1.2b)change to: "duplexing schemes (FDD/TDD)"g2638 2004/06/11_‚" #STd؇؈؉س!"‚# $%&'()*UVWe؊؋شص׃#$%‚$+,f،؍؎؏ئضطظعغ,-‚%-./1234X]gؐؑؒؓؔؕػؼؽؾؿ&‚&56789^ۃ‚':;<=>?ؘؙؖؗƒÃ܃݃ރ0-؆@P%5LMNk}` 0STdqr؊،ؑp&:O]l~Zms؇؍_ؖ6`ؒؓ‚!#‚#n؀‚$ P‚%uwxyz{|؃‚&.;Q\jot‚'@CX^g؄؈‚('a؋‚)!+R؅‚**/Kؔؗ‚1()fp؎‚21؉ؕ‚3 2UVWeg2257 2004/06/11EToddFChauvin^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d7g2258 2004/06/11EToddFChauvin^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 frameworkd8g2259 2004/06/11EToddFChauvin^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 2d9 UcBVthetable4-1captionshouldbeplacedabovethetable$Vtheterminterconnectivityatthephy/macisnotclear:VthetermnetworkisinappropriatehereEVthetextofsection4.1.5isnotspecificenough(VtheirOWdWthemOWthere1W;WPW]WdW؍WtherearehardlyanyapplicationsthatrequirebeareraccessPVtherefore WWUWeWiWthese2WOWdWsW{Wthey]WؠWthingآWthis WWWWWW=W@WSWZW[W]W`WaWeWjWnWqW|W،W؍WآWأWؤWإWتWZVaVcpage'WBWOWvWpaidWparWW0WXW^WdWkWبWWWW&WparagraphsWWparameter]WئWWWparsdWpart>W|Wpartial<WWparticularWW[W`W{WؠWpartitioning؄WpartsWpastWpeak WWUW]WئWWWpeakperuserdataratesisaveryimportantparameterfordئVpedanticsWper]WئWWperusualstylemultiantennashouldbecomemultianntenaVperceivedPWperformanceKW]WdWئWperhaps<WآWperioduWphase]WeW؍Wphased؍Wphases WWWW؍Wphrase-WphyWphy/mac:WWphysicalFWWplaceWplaced$W@WpleaseWpointjWpoliciesWpolicy-basedؒWportabledWportion9WpossibleWWXW^WdW؜WءWpotentially,WعWpotentiallyconfusingtext,V`>bthe W WWWWWWW W!W%W'W(W)W*W+W-W0W1W9W:W;W<W=W>W?W@WAWCWFWGWHWIWJWKWLWNWOWSWTW\W]WbWdWfWhWiWjWkWmWsWtWwWxWyWzW{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غWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWW W!W"W*W,WhallprovidemechanismsfortأVthe802.20standardshallalsoaddressestheneedsoflogica؅VWq:ballow WWNWSWW!WallowsiWtWalong@WؔWأWalso@W؅WؓWؕWأWaltered?Walternate+W@WalternativelyW؉WآWalternativelydefinespeedrequirementsformobilityclearlyValternativelyrewritetoclarifyintentآV>W?W@WAWCWFWHWIWJWKWMWNWRWSWTWUWVWWW]WdWeWhWjWmWqWsWtWwWyWzW|Wand/or1W:WiWmWantenna:W@WanyFWappend(Wappendtotheendofthesentencerequirementsofsection4.(Vappendix;Wapplicable W@WFWhWapplicationsNWsWtWapplicationstheaishallsupportapplicationsthatconformtVapply@WCWappropriateW+W9W?Warchetecture]WarchitectualKWarchitecture]WarchitecturesKWareWQW]WkWwWxW{W|W WWWwcconditions WWWWOWSWXW^WWW!W&WconformkWconfusesتWconfusingunnecessarysentence؏Vconjunction WconsequentlyPWconsider4Wconsistent)Wconsolidate.Wconstrained WWSWconstraintsfWcontradictory،WcontributionJWcontributions0Wcontrol=WAWؑWconvergenceWW[W`Wconvey،WconvincingdWcopied!Wcorresponding9Wcould WWSWfWcovered~Wcovergae;WcreateWWXW^WcreatesؑWcriteriaبWcurrentWW+WCWXW]W^Wcurrentoptionshaveinternalinconsistenciesneedtoharmon+Vdata WW/W5W7WUW]WjW،WئWdecidejWdecreasedfWdefine]WsWwWئWdefinebroadcastandmulticastserviceswVdefinedWW;WBWYW]W_WeWW،WؒWؠWءWآWاWb4.1.5.2*W4.1.6,W4.1.6.1,W4.1.6.2-W4.1.7أW4.2.1@WW4.2.1.1@W4.2.1.2@W4.2.1.3@W4.2.5ءW4.4.1.WؕW5+W-W1WCWrWطWW5/1.25-W500-W512kbps،WW6:WطWW73WؕW8ؕW802 W!WؕW802.1qiWبW802.2؅W802.20WW9W<W@WCWFWHWIWJWKWLW\WbWmWsWwWxWyWzW{W|WW؅W؊W؍WؒWؓWؔWؗW؝WأWإWاWةWدWWWWWWWWW W*W+W,W802.20'sحWfddؐVabilitywWxW{W|WؒWؓWؔWable؎Wabsence؎WabstractKWaccess=WFWPWmWaccommodateKWaccordanceؕWaccount@WKWaccounting|Waccuracy@Wachieve:WAWachieved WWSWactivePW؎Wactivities|WactivityؓWWWGcwhich WWOWSWfWؒWسWWWW!Wwhile|WW Wwhose WWUWW#WwhyWwide-areasWwidelyWwiderWwill W W WWWWWW?WSWTWUWXW^WdWWWWWWWW!W"W#W&Wwindow؍Wwireless{W؜WWwirelessbroadcast/multicastservicesneedtheabilitytotu{Vwith WWWW W!W)W+W-W.WSW\WbWhWqWzWؕW؝WبWتWثWدWWWWWWWWWWWW W!W*WwithbestcommercialpracticesambiguousV-‚I.‚J/‚Q0‚R1‚S2‚T3‚U4‚V5‚W6‚X7‚Y8‚Z9‚a:‚b;‚c<‚d=‚e>‚f?‚g@‚hA‚iB‚jC‚qD‚rE‚sF‚tG‚uH‚vI‚wJ‚xK‚yL‚zM‚NcneedsWW-W;W=WBWXW^WfWkW؍WWWWW&WneeedWnegativeWneither؝WnetworkWWEW[W`WؗWذWWWWWWW)WnetworkszWWnew@WKWno1W2W]WdWiW؊W؋WآWؾWWWW WnoideawhatthissectionistryingtosayآV W WWWWWWWW(W4W:W<W>W?WFWOWSWUWVWXW[W]W^W`WdWeWhWjWkWnWrWsW}WW؅W؆W؉W؊W؋W،W؍WؒWؖW؜WؠWءWnotarequirementimmediatelyobviousandaddsnovalue؊VnotasentenceؖVnotanexampleasadvertisednotrelevanttotherequirement؋Vnotclearwhatismeantbypartialsolutionperhapsrephrasi<VnotdefineduntestableVnottestable؉Vnottestablenotarequirement}VWx cfThe concept of bandwidth must be clarified given that we are not requiring specific channel bandwidthsd4g2255 2004/06/11 EToddFChauvin^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d5g2256 2004/06/11EToddFChauvin^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 documg2614 2004/06/11t these targets are realistic. Operators are making commitments to deploy systems in the 2s)bperformanceWW@WAWCWJWKWRW\WbWsWؔWؕW؟WاW W*WperioduWpermitؔW؝WpersonalKWperspectivejWphase؍WطWphbsأWphyJWKWmW؊WؓW؛Wphy-specificJWKWphy/mac؇WWphysical@WFWmWؕWتWWpick.Wpickoption3.VpicoWpicocellsWpleaseذWpleaseclarifywhatexactlyistherequirementذVpluralWpointWpoliciesؒWأWpolicy-basedؒWportionwWpossibleAWJWؕW؜WpossiblyآWpotentially؎WعWpotocolWpotocolinlayers1and2Vpower@WAWؠWW Wppp؃Wpractice؞Wpracticepractices؞VpracticesؗW؞WWide?WFWJWsW{W|WprovidersNWprovisioningNWprovisions<WNWpublic@WpurposeKWmWpurposes-Wput;Wqos+WMWNWqualityFW&cline 6 is "Duplexing schemes"d30g2369 2004/06/11 2004/06/01'EDanFGalGMember^Technical, Non-binding_12`17a4.1.4bJDelete the entire sentence that spans lines 17, 18: " As an example...".c[The sentence "As an example, ..." is redundant. Has the same meaning as line 21 in page 11.d31g2370 2004/06/11 2004/06/01(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 enoughd32g2371 2004/06/11 2004/06/01)EDanFGalGMember_12`20a4.1.5bAdd the following sentence: "Thus, the aggregate data rate per sector shall be calculated by multiplying the spectral efficiency entry from Table 4-1 by the specified channel bandwidth. "g2641 2004/06/11ealingwithaverageratesVshallWWWOcstringent WWSWW!WstyleWWsub]WئWsub-section>W@WsublayerWW[W`WW)Wsubmissions؍Wsubmitted0WsubmittersdWsubnetWsubsectionKWsuburbanWsuccinctWsuch4WOWWsuggest=WإWsuggested@WWsupportWWXW^WiWyW{W|W~WرWزWشWؾWWWWWWWWWW&Wsupportnon-lineofsightambiguousزVsupportingWsupportsWsureإWsustainedOWsynchronizationءWsynchronizationbetweenmtandbsisnotdefineditdoesnotءVsynchronizeءWsystemWW-W9WOWXW]W^WhWoW،W؜W؝WؠWئWتWWWWWWWWW&W.Wsystemmustworkunderthevariousenvironmentsofamacro/m.VsطVtable4.1specifiesadownlinkspectralefficiencyof2.0b/dVFwcrates WWWWUWXW]W^WئWWWWWW#W&W,W-WWreadilyextensibletowiderchannelsthisisanopen-endedrVreadsWreal؍WؠWrealisticdWrealities؍Wrealtime9Wreason؍WWreceive{WrecommendWWXW^WqWrecommended4WreduceWredunadantWredundancyGWredundancyinline30theaishallbedesignedGVredundant'WNWعWredundantsecondsemtencelines4-6NVrefer.WWreference"W1W2W3WeWreferenced0WبWrefined=Wreflect>WJWreflecttheproposalforcommonmacincontributionc802.20-JVrefrence2WregardبWregardingبWrelabeled!WrelativeOWrelevant0W؋WبWWrelevantchannelmodelsassociationofenvironmentswithchaVrenumbered!Wrephrasing<WreplacedؕWreportingjWrepresentative،WWc2WW!W"W1W9W[W`WeWiWjWqW؆WظWؿWWWWW)W2-1W2.0OWdW20WWXW^WWW&W20030W02.1WW802.16WW802.1qWW802.20WWWWa W W WWWWWWWWWW#Wabove$WaccomplishedWWaccumulatedWWachieved WWacrossWWadd/W0Waddanimportantattributeoftrafficclassesdatarate/VadditionWWWWadditional.WadoptWWadvocatingWWadvocatingaspecificmechanismforseparationoftrafficdoVVafter#WagnosticWWairWWWWall WWWW0WalloptionsareoverlydetailedwithrespecttospecificstaVVallow W WWWWWallowingWWan WW!W'W/Wg2257 2004/06/11EJohnFChen^Technical, Binding_17`29a4.2.3bAdopt Option 3c8Option 3 is simple, straightforward, and well defined. d17g2258 2004/06/11EJohnFChen^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 frameworkd18g2259 2004/06/11EJohnFChen^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 2d1904/06/11tcfThe concept of bandwidth must be clarified given that we are not requiring specific channel bandwidthsd14g2255 2004/06/11EJohnFChen^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d15g2256 2004/06/11EJohnFChen^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 documg2624 2004/06/11WWWsplitWWWWstatisticsWWstraightforwardWW d11This 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.d11cefficiencies WWSWdWWW!Wefficiency W WWW)W+WOWSWTWdW،WWWW!W"Wefficient|WWefficientlyyWeffortؿWegWWWWXW[W^W`WWW&W)WeitherfWiW؆WWelinateWelseBWelsewhereؠWآWWenableرWencrypted=Wencryption؝WenduWend-to-endؒWengineeringFWenhancing;WWWfromWW!WfurthermoreWWgiven WWgroupWWhandleWWharmonize+Whas'Whave+Wheading8Wheadings*Where0WhighWWhz#Will-defined WWimplementedWWimportant/Win W WWWWWWWWWW W'W2W4W5W6W7W8Winoption3line4missingdatarate5Vinoption4line27missingdatarate7VVWUscand W W WWWWWWWWWW W!W*W0W9W@WFWHWKWOWSWTWUWXWYWZW]W^W_WaWdWeWhWiWjWoWqWsWwWxWyW{W|W؅W؆W؊W،W؍WؒWؕWءWئWاWبWغWؿWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWW!W"W#W&W'W(W,W-WproachWW[W`W؍WappropriateWWXW^WarbitraryWWXW^Warchitecture]WؒWئWare W WWWWWWWWWPWSWVWXW[W\W]W^W`WbWdWfWgWhWiWnWsW{W؍WؠWآWبWغWWWWargumentsdW)cBNeed to clarify what "consistent with spectral efficiency" means.d33g2372 2004/06/11 2004/06/01*EDanFGalGMember^ Editorial_12`19a4.1.5bAE1. Change the heading of section 4.1.5 to "Data Rates - Downlink and Uplink" 2. Move the text in the current (and modified) section 4.1.5 into sub-section 4.1.5.1 with a heading "Aggregate Data Rates" 3. Change the current section number from 4.1.5.1 to 4.1.5.2 and change the heading to: "User Data Rates - Peak and Average"EcVNeed to change the headings of sections 4.1.5 and 4.1.5.1 and restructure the section.d34g2373 2004/06/11 2004/06/01+EDanFGalGMember_13`18a4.1.5.1bg2643 2004/06/11bas WW!W%W'W+W:W;W@WAWCWFWIWKWPWQWSWsW؇W؋W؍W؎WؒWؓWؔWؕWؖWؗWؙWؚW؟WأWWWWWWWWWWWWWWWW WW!Wasproposedincontributionc802.20-04/55Vassignment%W؇WassociateؓWassociatedAWؔWؕWassociationWWauthorizationsؒWauthorizedxW{WavailabilityIWavailable,WfWiW؎Waverage*W@WeW؇W،Wavoidance@Wb/s/hz/sectorOWdWbackboneiWband@Wband-classes@Wbands@Wbandwidth)W+W@W؊WbandwidthsHWIWbase:WAWEWmWؒWbasedsWtWwWؒWbasespWbasispWbatteryAWbe W)W+W-W<W?W@WAWCWFWHWIWJWOWhWsW{W؀W،W؍W؎W؏WؑWؓW8  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.a aggregation and reporting frequency. cg2608 2004/06/11Wac120km/hr WWSWW!W17W18WBW19.6W1xev-dvWW802.16WW802.1qWW802.20WWWWa W W WWWWWWWWWWaccomplishedWWaccumulatedWWachieved WWacrossWWadditionWWWWadoptWWadvocatingWWadvocatingaspecificmechanismforseparationoftrafficdoVVagnosticWWairWWWWall WWWWalloptionsareoverlydetailedwithrespecttospecificstaVVallow W WWWWWallowingWWan WWand W W WWWWWWWWWWanyWWapplicable WWapplicationsWWapproachWWappropriateWWarbitraryWWare W WWWWWWWWWWYbaggregate)W*W؇WaggregationjWai%W:W?WsWtW}WWؒW؟WؠWإWاWدWشWWWW WWai's=Wai802.20ؒWairWWFW\WbWmWؒWؙWؚWأWاWتWWW W*Wair-interfacesWallCWwW؇W؏WؓWؔWءWآWأWاWغWWalleviatingWallocationؠWأWW,Ybaddthefollowingsentencethustheaggregatedatarateper)Vaddthefollowingtextinline28AVaddthespecificreferenceinsection5and/orinafootnote1Vadditional.W@WaddresswWWaddressedyWaddresses؅WaddressingyWadjacent@Wadopt W W WWWWWWUWVWWWYW_WWWWWWWWWWWWW#W$W%W'Wc802.20-04.44Vadoptoption2Vadoptoption2withaminormodificationasfollowssystemsVadoptoption3VVYV_VVVadoptthec802.20-04-44textforthissectionVadopttheproposedtextinthejointcontributionc802.20-04VVadoptthetextinsection4.1.5.1ofc802.20-04-44withtheVadoptedJWadvanced:WWadvancementsIWafأWaffectCWafter W#W/W5W7WMW]WؔW؝WئWagainstؗW؜WW g2252 2004/06/11 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.d2g2253 2004/06/11 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. 3d3g2254 2004/06/11 EToddFChauvin^Technical, Binding_12`22a4.1.5.1b#Remove option 1 and adopt option 2g2612 2004/06/11  d1This 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.d1xcrequireWWPWXW^WsWW&WrequiredءWسWrequirement W WWW=W?WPWSWTW}W؊W؋WؙWؚW؛WآWؤWبWذWغWؾWWWWWWWWWWWWWW W WWWW!W"Wrequirements WWWW.W4W@WAWKWSWXW^WhWkWnWxW؆W،W؍WؒWؓWؗWؠWءWإWبWWWWWWWWWWWW W W WWWWW!W&Wored;WrestrictWWXW^WrestrictivePWrestructure*Wresult WWUWrevised؍WrewrittenWrfWW@WXW^WrightWrt9WrttWWXW^WruralWsame'WWsameascomment35VsatisfiediWsatisfyؼWsatisfyuserqosincompleteؼVsayآWWW 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.WWvlanWWwasWwaysWWWweWWWWWWWWwellWWwgWwhatW VcB?@ABCDEFGHIJKLMNgantiOPQRgoldburgSTUVWXYZ[\klerercdefghijkniselyklmnopqrstuvwxyz{|}~؀؁؃؄؅؆؇؈؉؊؋،؍؎؏ؘؙؚؐؑؒؓؔؕؖؗ؛؜؝؞؟ؠءآأؤإmurakami]^_`abparkابpittampalliةتثجحخدذرزسشbchangefigure2tofigure3-2"Vchangefrom802.20tosystemrequirementsforieeestandardةVchangelayertoiso/osilayersoVchangeline6shallreadforthe802.20packetmobilewireleVchangemitigateagainsttomitigatedenialofservicemitigaVchangemustinlines1718toshallVchangenetworktobasestationEVchangepppmplstopppormpls؃Vchangeqostoqos؈Vchangeshallclarifytospecify؆VchangetexttoreadinthisstatetheusershouldhavearadfVchangetheheadingof4.1.1.2toprivacyandmessageintegri>VchangethesentenceasfollowsIVchangethesentencestartingonthislinetostatehandofftVchangetoLVchangeto802.20systemsareintendedtoprovideubiquitous+Vol=WAWcostAWcould@Wcriteria WWcryptographic=Wcurrent!W*Wdata)W*W+W5W7W:W?WCWdefine@Wdefined@WCWWdl/ul+WF cinadequatemustinlines1718VinappropriateEWLWinappropriatetext802.20protocolsLVinclude؛WincludedWincompleteؼWinconsistencies+Wincorrect"W2WةWWWincorrectlinenumberreferenceinline22aftersection4.42Vincorrectreferencetofigure2"VincorrecttitleةVincreaseWWincreasedfWindefensibleWindividualsWWindoorhWinflammatorysWinformation{WWWWWWinformativesW؅WؑWWW Winformativeandnottestable؅VinfrastructureWWZWaWW(Winsert#WWWWinsertaspacecharacterafterhz#Vinsertbasedafter802.20document04-44thiscorrectstherVWWintegrity>W؝WintendedOWؒWintentdWW W Winter-frequencyآWinter-userؓWinterconnectivity:WWinterconnectivityatthephy/macambiguousV/ 2004/06/11 2004/06/010EDanFGalGMember^ 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 ?! d40g2379 2004/06/11 2004/06/011EDanFGalGMember^ Editorial_14`21a4.1.7.1b 33  33>c:add an important attribute of traffic classes - data rate.d39g2378;^technicalbinding V V V V VVVVVVVVVVVVVVVVV-V4V5V7V9V:V;V<V=V>V?V@VAVBVCVDVEVFVGVHVIVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVdVeVfVgVhVjVsVxVyVzV{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ؿVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V VذdCbinsertbitrateaftertrafficclasseswithdifferent/Vinsertdatarateafterwithdifferent5V7VinsertthefollowingsentenceatthispointitisfurtherasVtWinsteadؾWintegralWintegratedWintegrity>W?WؗWؙW؝Wintended WintentآW WinterؼWinter-frequencyWinteractiveؕWinterconnectivityWintereference@WinterfaceWW\WbWmWؒWؙWؚWأWاWتWWWinterfacesWW\WbWmWأWinterferenceWintermodulation@WinternallyFWinteroperableتWinteroperate@WinteroperationzWinterruptionFWintetrest@Winto*W@WKWأWWintolerantؕWintraؼWintra-frequencyWipmWtWwWؓWأWWWWWWWip-basedsWip-dataتWipsecؗWipv4yWzWؤWWipv6yWzWؤWWsAWlimitationstWac21'W222W256WPWW26W277W3WW5WOWYW_WdWgWhWjWqWW'W3.08W3.1.1!W30GW31-34W34562WؽW35W384W3gppWW3gpp2WW45W7W8W9WBWCWgWW4optionsarespecifiedallbutoption3imposetrade-offbugV4-1$W4-2طW4-6NW4.1OWdW4.1.1+W4.1.3W4.1.5(W*W4.1.5.1*WW4.1.7أW4.1.9W4.2.1@W4.4.1.W2WؽW4.4.2KW5بWWWW73W802 W!WبW802-2001W802.1WW[W`W802.16WW[W`W802.16.3W802.1qWW[W`WبW802.20WWWWLWXW[W^W`WdWsWzW؍WؠWبWدWWWWWWWW802.20mechanismsnotclearV؁W؂W؄W؆W؊W،W؍WؖWؙW4FGalGMember^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.d44g2402 2004/06/11 2004/06/025EDanFGalGMember^Technical, Binding_15`4a4.1.7.1b.insert "data rate," after "...with different"c+In Option 3, line 4, missing "data rate," d45g2403 2004/06/11 2004/06/026EDanFGalGMember^ Editorial_15`9a4.1.7.1bsubstitute with a proper table.c2distorted table-like columns in lines 9 through 25d46g2404 2004/06/11 2004/06/027EDanFGalGMember^Technical, Binding_15`27a4.1.7.1b.insert "data rate," after "...with different"c,In Option 4, line 27, missing "data rate," d47g2405 2004/06/11 2004/06/028EDanFGalGMember^ Editorial_15`30a4.1.7.1b5change "Traffic classes" to: "Service Characteristic"g2656 2004/06/11~.1cabove$WabsenceOWacceptableءWacceptancedWaccess=WPWWaccomplishedWW[W`WW)Waccounting|WaccumulatedWW\WbW W*WachievabledWachieveOWW Wachieved WWSWW!WacrossWW[W`WW)WactualdWadaptiveWadaptivebandwidthallocationnotclearVadd/W0WCWDWKWlWvWWaddaclarificationonimplementationDVaddanewsubsection4.4.2macdesignandperformancerequirKVaddanimportantattributeoftrafficclassesdatarate/VaddcommaafterstandardlVaddedWadding؋WadditionWWWWXWZW^WaWWWW&W(Wadditional.WOW؋WadvocatingWW[W`WadvocatingaspecificmechanismforseparationoftrafficdoVV[V`Vafter#W2WlW؍WWagainst؜WW`W8cFIn the table of Option 4, confusing column heading - "Traffic classes"d48g2406 2004/06/11 2004/06/029EDanFGalGMember^Technical, Binding_15`30a4.1.7.1bBHarmonize 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.d49g2407 2004/06/11 2004/06/02: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.d50g2408 2004/06/11 2004/06/03;EDanFGalGMember^Technical, Binding_16`15a4.1.10g2659 2004/06/11cinthetableofoption4confusingcolumnheadingtrafficcl8VinadequateW-WAWinadequatedetailofpowercontrolrequirementsneedmorespAVZa4.2.3BCRY_hɃʃ˃̃̓'.4.2.4D΃4.2.5ء4.2.6EFآσ4.3GHIЃу4.4K4.4.1LMNأ҃Ӄԃ4.5ؤ4.5.1Ճ4.5.1.14.5.2[`iب)4.5.3Zaإ (4.5.4\bjا *4.7 4.8 50b0.9-WW03/45r10W03/47r10W1 W W WWWWW!W%W*W+W@WJWOWUWVWWW]WdW؍WؔWئWبWضWطWWWWWW#W$W%Wttomofpage10underthefigures!V1addacaptioninline4table4-2blockassignmentsizes%V1addfigure3-1serviceattributesofmbwasystemsV1changeoption1line2-3tosystemarchetecturedatarate]V1changetheheadingof4.2.1torfrequirements@V4*ctheconceptofbandwidthmustbeclarifiedgiventhatweare VVVVV$Vtheconceptoftwophasesisill-defined VVWVV%VtheconstraintsonthetimeinwhichachannelneedstobeafVthedefinitionofsofthandoffgivenhereisincorrectsoftVthefigures12copiedfroman802standardneedtoberelab!VthelineisconfusingandneeedtoberewrittenitseensthaVthemaximumchanneldelayspreadcouldbemuchhigherthan5VtheparametersandmetricscannotbeproperlydefinedbeforeاVthephrasescaleslinearlywithsystembandwidthisinadequa-VidesetcnotclearVtheqosrequirementsinthedocumenttodayegdiffservflexiVVXV^VtherequirementaspreviouslywrittenallowsbroadcastviauVtherequirementsshallconformtotheparifnottheparneekVthescopeofthisrequirementneedstoberefinedasworded=V;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.d51g2409 2004/06/11 2004/06/03W?WAWOWSWTWUWVWWWXWZW[W]W^W`WaWdWfWiWjWqWsWuW{W~W،W؍W؝WأWئWبWزWضWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWWW!W"W#W$W%W&W(W)W.WWjW{W،W؍WثWWWWWWWWWWWWWWWWW W W WW!W:ccolumn8Wcolumns6Wcombination؝WcommalWqW؁W؈WWcommaismissingbeforeandinliststhroughthedocumentgeqVcommasWcommentؕWخWWWcommercialWcommitmentsdWcommonJWcompelling؍Wcompeting؍Wcompetitive؍WcompleteOWWcomplexityذWcompliantWcomplicates W WWWSWTWWW!W"WcomponentsOWconcept W WWWVWWWeWWW$W%W ~=cThe scope of this requirement needs to be refined. As worded, may suggest that the entire access control protocol must be encrypted.d53g2411 2004/06/11 2004/06/04>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.d54g2412 2004/06/11 2004/06/04?EDanFGalGMember^Technical, Binding_16`29a4.1.11.2bAChange 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. g2663 2004/06/11member  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQR]^_`abئ !+WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWdWeWfWgWhWjWsWxWyWzW{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 ?c`Language is not that of a requirement, especially the usage of "will" instead of "shall/should".d55g2413 2004/06/11 2004/06/04@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. Ming2664 2004/06/11}vbdefinition;W؇WWdefinitioninthisdocumentthetermsystemspectralefficie؇VdegradationCW؉Wdegrade؉W؋WصWdegradesWdelay,WCWRWfW؎WؓWؔWؕWغWWWdelaya؎WdelaysFW؎Wdelete!W'W+W0W2W3W4WGWNW]WeWgWiWrW~WW؀W؄W؉W؊W؋W،W؍W؏WؑWؕWءWآWثWطWظWعWWWWWWWW WWWWWWdelete34562Vdelete73VdeletealltextandpossiblythesectionheadingtooآVdeletealltextin4.2.5ءVdeleteasanexampledataratesgracefullydegradefrompede؋Vdeleteaverageuserdataratesinaloadedsystemshallbei،VdeletebasedontheclassificationoftrafficinaccordanceؕVdcontributionreferences03/45r1and030Vdeletethissectionorretainoption3gVl/ul+WdocumentmW@g2414 2004/06/11 2004/06/04AEDanFGalGMember^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/06/11 2004/06/07BEDanFGalGMember^Technical, Binding_18a4.2.3g2666 2004/06/11  @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. "  @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. "   @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(brequirements@WCWKWQWkWW؍WؓWؔW؟WةWWWWWrequirementswork؎WreservationأWresolveؒWresolvingؓWresourceؒWؓWأWresourcesأWWWrespect؎WrespectiveyطWresponse@WWZ?b1changetheheadingofsection4.1.5todataratesdownlink*V1deletethetable+V1line2-3ismodifiedtothesepeakdataratetargetsareiئV1.2+W1.25طWW1.5طW-W1.6W10!WؔWW10-8ؕW100-WPW؎W100msfW10e-1ؔW10e-8ؔWWWW!W"W%W*W+W4W@WJWRWSWUWVWWW]WeWiW؍WؔW2alternatetextforthissection+V2insertnewsubsection4.2.1.1general@V2-1W2-3]W2.0+W23$W25,W250CW25ms؎W28AW3WW!W%W*W+W-W@WQWYW_WgW3insertnewsubsection4.2.1.2radiotransmitter@V3-1W3-2!W"W3.1W!W3.1.1KW33HW34562W360-W4%W@WCW4insertnewsubsection4.2.1.3radioreceiver@V4-1$W)W+WdW4-2%W4.1.1(W4.1.1.2>W4.1.5*W4.1.5.1*W\gbrate)W+W/W5W7W]WؓWؔWؕW؟WؠWئWWWWrates*W:WCWFW]WeWsW؋W،WؔW؟WئWدWصWWWW,W-Wread(WfWhWWWWWWWWWWWW WWWWWreadilyKW؉WWreal-timeؕWreasonableWreceivewWxW{W؎WZW[W^W`WaWremoveoption1andadoptoption2 V V VVVVUVVVWVremovesectionVVVVZV[V`VaVremovethedistinctionbetweenuplinkanddownlink VVTVremovethissectionVVXV^VreplaceWWNW\WbWreplacerequirementwiththeairinterfaceshallsupporttheVV\VbVreportFWreportingFWjWrequireNWsWrequired@WAWrequirementWWCW\WbWrequirements(W.W#r"bglobal@Wglobally؁Wgloballychangeegxwhichisnotcommatoegx؂V؂Vgood-putFWgraphicaltWgreater-WCWhandAWhand-held@WhandoffFWharmonize9Wharmonizewiththeappropriate802.20contributionsonthis9Vhas]WhaveKWfWheading*W>W@Wheight@WhelpingAWhigh-speedsWWhigher:Whighre<WhomeqWhoweverOWhz#Wi{W؁WidentifiedwWidentify{Widentity?WidleAWieee!W<W@Wietf-specifiedzWifFWJW]WigmpzWignorewWimd@WimplementationmWimplementationsDWNWimprovedsWinWW W%W*W.W1W:W;W@WAWCWFWHWIWJWKW]WfWhWiWmWsW{WinabilityCWinclude@WAWFWincludes<WincludingtWindependent]Windication?Windividual?WwWafterhz#V*cthrough6WqWthroughoutWthroughouthtedocumentweusedifferntcaptializationsforVthus؋WtiaWtightfWtimePWfWWtimeframedWtimesWtitleةWWWtolerable9Wtoo WtrafficWWWW/W8W9WtransportWWturnWWtwo WWtypes9WudpWWunder WWWWW9WOWunnecessarily W WWWuplink W WWWOWupon;Wurban WWusage?WuseWW4WusedWWuseful4Wuseless4Wuser WWWWusingFWvague WFWMWvagueqosneedmorespecifityMVversion;Wversus W WWWvery WWvlanWWwant0Wwas;WwaysWWwe W W WWWWWW0WwellWWwere0Wwhat)W<WwhenWWWWwhereasOW1blimited@WFWtWWWlimitingؑWlimits@WlineW$W%W-W.W:W;WAWDWHWJW]WrWtW؀W؝WئWWWWWWlineshouldreadVline-of-sightWline4]WئWlinesW'W؀WثWlink+WFW؅WؠWWlinkadaptationshallbeusedbytheaiforincreasingspectؠVlink-levelؒWؓWأWlink-levelend-to-endؒWlisted%W0Wllc؅WloadإWloaded،WضWWloading+W]WئWWWloadsإWlocal@WlocationtWlogical؅WlossCWWlowAWؕWmWmacJWKWLWmW؊W؎WؓWؕW؛WأWmac'sNWmac/phyؔWWmacroWmacro/micro/pico+WmacrocellsWmadeؗWاWWmaintain؟WmaintenanceFWmakedWإWWWW W W W WWndVmanدWmanagementsWmanagmentiWzObstationsAWCWmWخWWWstatusWstdؕWstillؓWstoredFWstreamingtWstreams{W|WؓWstrengthFWstructureؒWsub]WئWsub-section*WKWsub-sections@Wsubheading,WsubnetsWsubsection@W-WsubsetwWأWsubstitute6Wsubstitutewithapropertable6VsuburbanhWWWsuccinctWsupportoption2forperformanceundermobilityanddelayspRVsupportoption3asfaraslatencyrequirementsareconcerneQVsupported-Wsystem+W?W]WhWsystemsWtable$W%W)W+W6WdWtakeKWtaking@Wtargets]WtaxedKWtddDWKWtechniques:Wtechnology-WIWJWterminology;Wtests@WtextW W*W+W.W<W@WAWJWKWeWfWhWthan,W-WJWfWthatWW'W(W<W@WCWIWJWKWNW\WbW Bc^Option 1: Page 18, line 4 - the "(TBR)" needs to be defined or else discard option-1 entirely.d58g2416 2004/06/11 2004/06/04CEDanFGalGMember^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." Kc9All current three options need improvement. Add Option 4.d59g2417 2004/06/11 2004/06/04DEDanFGalGMember^Technical, Binding_18a4.2.4g2668 2004/06/11DbOAdd on line 19: "Implementations may support either mode (FDD or TDD) or both."c%Add a clarification on implementationd60g2418 2004/06/11 2004/06/04EEDanFGalGMember^Technical, Binding_18`25a4.2.6b"Change "network" to "Base Station"c)The term "network" is inappropriate here.d61g2419 2004/06/11 2004/06/04FEDanFGalGMember^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 suppog2670 2004/06/113cimplementationDWWimplementedWWXW^W؍WWW&WimpliedWimpliesسWimportant/W]WئWWW WimposegWimprove<WimprovementCWin W WWWWWWWWWW W'W2W4W5W6W7W8W@WGWJWOWSWUWXWZW[W]W^W`WaWdWfWgWiWqW{W|W،W؍W؜WبWتWذWضWؽWWWWWWWWWWWWWWWWWWWW WWWWWWWWWWW!W#W&W(W)Winawirelesssystemprotectionagainstdosisnotalwayspo؜Vinoption3line4missingdatarate5Vinoption4line27missingdatarate7Vinsection4.4.13456notclearؽV Fg2420 2004/06/11 2004/06/04GEDanFGalGMember^Technical, Binding_18`30a4.3bDelete the sentence. c6Redundancy in line 30 - "The AI shall be designed ..."d63g2422 2004/06/11 2004/06/04HEDanFGalGMember^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. d64g2423 2004/06/11 2004/06/04IEDanFGalGMember^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?W@WEWIWLW]WfWnWoWpW؀W؁W؃W؆W؈WةWWWWWWWWWWWW WWW+W,W-Wchangeavailablewithadelayoflessthan25ms,VchangebasestobasispVchangecpetomobilestationinthissectionVchangedetailedtofunctionalnVx2boptionalHWoptionallyWoptionsؕWor;W?WCWDWNWgWiWwW{W؃W؉W،WؐWؓW؝W؟WWWWWWWWW W W W Worder؎WؔWغWoriginal!Wother WFWsW؎WأWاWWWWWotherwise?WoutFW؇WoutdoorCWزWWWoutdoor-indoorhWover-the-airأWإWoverallsWoverhead؇WpacketwWؓWؔWؕWpacketsmWwWإWpage!W$WparCWdWkWparagraphWparagraphsأWparamentersاWparameterؑWparameters+WؓWأWWWpart<W@WJWWpartialؗWparticipatingؓWparticularJWwW{Wpartitioning؄WpartnersiWpartsJWpathأWpeak*W+W]WsWئWWWpedestrian+WCWhW؋WصWWper)W؇W؎WؕWأWper-user؝WperformCW]]cbecause WWSWWW!WbecomeWWbeendWWWbeforeqWاWWWWbeginingثWbeginningتWدWbeingoWbelievedWbelongWbelow@WiW؍WWWWbestdW،WذWؿWWbestinclassoverallnetworkcomplexitytherequirementisذVbest-in-classsWbettersWWWW`WfWiWcannotgWcaptionWW$W%WcapturedWWZWaWcarriedWW[W`WcaseqWcdma]Wcell WWSWcells WWSWcertainly WWSWchance]Wchange*W2Wchannel W WWWHWOWSWVWfWchannels]Wcharacter#WcharacterizeOWclaimssWclarification;WDWclarified WWVWclarify)WoWqWclarify/changeIWclarifying WWSWclarity<WclasssWclasses/W8Wclear:W<WKcoptionsWW+WCW\WbWeWgWhWiWjW W*Wor WWWW.W0WBWSW[W]W`WfWiW{W؝WWWWWWWWWWW WWW!W)Worder WWUWdW|WWW#WorganizedWorphan1W3Worphanreference73Vorphanreferenceitu2thereisnoreference21Votasp Wother W0WsW؍W؛WءWWWWWWWWWWotheripnetworkstandardsnotcompleteVothersHWourWWXW^WWW&WoutdoorhWoutdoor-indoorWoverWWWWXW[W^W`W WWW&W)WoverallذWoverlyWW\WbW W*Wp&pبWpacketWWXW^WWW&Wbchangetoduplexingschemesfdd/tdd&VchangetoreadasfollowsbearerchannelavailablewithadeVchangetoreadasfollowsshouldscalewithsystembandwidthVchangetoreadieee802.20-basedsystemsshallsupportbroadVchangetoreadmobileipv4mobileipv6orsimpleipremovetheVchangetoreadservicesaretranslatedintoacommonsetofVchangetoreadshallprovidepowerconservationfeaturesto Vbetoisonlines12anddeletewillonline13؀Vchanged WطWchangesKWchannel)W+W-W@WHWIWPW]WfWhW؎WئWWWWWWWchannelization@WchannelsFW]WئWWcharacter#Wcharacteristic8Wcharacteristics@WJWchoosewWأWclarificationWclarificationisneededVclarify؆WآWذWclass@WؔWؕWؿWclasses/W8WؔWأWدWWWؕWcompromised?WcomputerKW"eJ^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.d66g2425 2004/06/11 2004/06/04KEDanFGalGMember^Technical, Binding_19`19a4.4bg2675 2004/06/11"'Kg2426 2004/06/11 2004/06/04LEDanFGalGMember^Technical, Binding_19`4a4.4.1bDchange to: "The 802.20 MAC design shall specify mechanisms ..." etc.c(inappropriate text "802.20 protocols..."d68g2430 2004/06/11 2004/06/04MEDanFGalGMember^Technical, Binding_19`4a4.4.1b+Add after "(QOS)": "control and monitoring"c&vague "...(QoS)" - need more specifityd69g2431 2004/06/11 2004/06/04NEDanFGalGMember^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)d70g2432 2004/06/11 2004/06/04OEHariFGantiGMember^Technical, Binding_Technical, Binding`6a1.3g2679 2004/06/11 ! KbAInitial 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"d67+bfrequency@WFWjWWfrom)W*W?WCWxW{W؋WؓWؗWؙWؚWإWةWصWWWWWWWftptWfulltW؇WfunctionalnWfunctionalitiesKWfunctionality؅WWfunctionsKWWfurtherWfutureIWKWgmWtWwWzW{W؎WؒWؓWؔWؖW؛WإW+Wgain@WgamesؕWgamingtWgathering|Wgeneral@WAWKWgetCWPWghzتWgiven+W?W؎WؓWإWغWbuse=WiWWWWWusemobileterminalandbasestationonlyandnootherabbreVusetheproposedversioninthejointcontributionc802.20-0Vused@W؅WؠWusefulWuser*W+W?WCWPW]WfWsW،W؎WؒWؓWؔWؖWؙWؚW؟WأWئWخWضWؼWWWWW,W-WusercapacitycellsizesandreliabilityasanexampleegmؖVWؓWvisionWvoiptW؎WvpntWweNWwebtWؓWwell!W@WAWCWFWKWsWwhen{W|W؅Wwhich WWHWNWOWSWmWxW|W؁W؂W؎WwhileAWؓWؕWwhoPWwholesaleiWwide-areasWwiderIWwill@WKW؀W؎Wwireless@WsWwithWW W(W*W,W/W5W6W7W9W;W@WIWNW\W]WbWdWeWfWjWkWmWzW؎WؓWؔWؕW'Od71gA1. 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.)5 2004/06/11PEHariFGantiGMember^Technical, Binding_Technical, Binding`13a4.1.6te specification of the channel conditions.)5<SbSpecify 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/06/11TEMarcFGoldburg^Technical, Binding_11`5!%ObKeep 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 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.)5#,baddWW W!W%W)W-W.W1WAWDWHWMWuWxWyWzW{W|Wؓ؝WWW,WaddadefinitionforsimpleipVentencebeforechannelbandwidthsinline33theHVaddasentenceonline3thescalingfactortobeassumedfo-Vaddafterline2؝VaddafterqosMVaddapplicableafterotherthechangedtextwouldbeinconj Vaddfigure2-1thevisionofintegratedmbwaunderthefigurVaddnewtextinline15seeadditionalrequirementsinsecti.Vaddonline19implementationsmaysupporteithermodefddoDVaddperiodatendofsentenceuVaddthe802.20systemshallprovidetheabilitytoefficient{Vaddthe802.20systemshallprovidetheabilitytosupportt|Vaddthe802.20systemshallsupportinteroperationwithextezVaddthe802.20systemshallsupporttheabilitytorestrictxVaddthe802.20systemshallsupportthedeliveryofmulticasyV8bbearerPWfW؎WWbecomeWWWJWإWbeginningثWbehaviorsأWbeingWWbelowتWbest+WJWؕWؗWأWWbest-in-classsWbetween WWTWmWؒWؓWbit/WؓWbits/sec/hz/sector WWSWblock%W؇Wblocking@WbootpإWbootstrapإWboth?WAWCWDWKWzWؗWؠWؤWؼWWWbottom!WbpsؔWbps/sector؇WbroadbandةWتWbroadcastFWwWyW{WbroadcastservicetheabilitytotransmitapacketofinformwVbroadcast/multicastzW|WbrowingؓWbrowsingtWbsCWbursty~Wbut@WFWtW؉W؝Wby)W+W?WwW؇W؎WؒWؓWؔWؗW؝WؠWأWدWc/iFWcalculated)W+W؇WcallCWFWcanWWPW\WbWsWwW؎WؕWإWاWcapabilitiesNWؒWؓW؛WcapableإWFWcto W W WWWWWWWWWW W!W"W)W*W+W-W.W0W2W4W9W;W=WBWHWIWOWPWSWTWUWXW[W\W]W^W`WbWdWeWfWjWkWqWsWxW{W|W~W؀W؋W،W؍WؓW؛W؝WءWآWأWئWبWرWؾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWW W!W"W#W&W)W*WtosupporttherequirementhasnoteethؾVifiedtheobjectivesspecifiedcanbesaiVtypes9WtypoجWtypobasesجVudpWWXW^Wun-meetablesWunachievable،Wunder WWWWW9WOWSWXW^WuniqueآWunncessaryثW&Kcit WW W4W@WSW]WdWhW،W؍WؑWءWئWتWWWWWWWWWWWWWWWW WWWW!WitisbettertospecifythesystempeakdataratesinsteadoVitisexpectedthatsystemaccesstimeswillbeaprobabalisVit'sئWitemqWitem3qWits@Witself Witu1Wjust،WjustifiedgWkmphOWdWknownWlacking@Wlanguage?WWWWWlanguageisnotthatofarequirementespeciallytheusageo?Vlarge WWUW]WئWWW#WlatencyWW9WXW^WWlaterWlayerWWWWWWFWXWZW[W^W`WaWoW|WؒWإWWWWlayersWleastWleavingؿWless]Wlet'sWlightdWlikesWWWlikelyPW|Wlimit WWUWgWeWbconcernedQWconditions WW+W@WOWSW]WئWWWW!WconferencingؓWconfigurationأWconflictsؓWconformtWؒWWconjunction WconnectedإWconnectionstWconsensusjWWconservation Wconsistent(W@WdWkWؗW؟WWconsisting|WWconsistsJWmWconsolidateWconsolidatetheusefulinformationVconstitutesmWconstraints؟WversationalؕWcorrectionsؔWcorrectlyؕWcorrespondingsWؕWcostAWcould@Wcoverage،Wcriteria WWSWcryptographic=Wcurrent!W*WؗWdata)W*W+W5W7W:W?WCW]WjWsW؋W،W؎WؔWؕWؗWؙWؚW؝W؟WdatagramwWdateIWdealingeWdefine@WPWW؉WؓWdefineanactiveuserasonewhocangetaccesstoabearerPVdefined@WCW]W؇WؔW/^technicalRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWdWeWfWgWhWiWjWkWnWoWrWsWwWxWyWzW{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ؾWؿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWW W!W"W#W$W%W&W'W(W)W*W,W,WA^technicalbinding@ ;technicalnon-binding@_@‚"@‚(@‚1@`p@J‚4@5a1.2@B4.1.7.1@4.2.3@b1addacaptionatthebottomofpage10underthefigures@Z1changetheheadingofsection4.1.5todataratesdownlink@11@2alternatetextforthissection@4.1.5.2@802.20-based@afddanfdd@#add@(addanewsentencebeforechannelbandwidthsinline33the@,addthefollowingsentencethustheaggregatedatarateper@adopt4.2.1fromc802.20-04.44@Yaggregate@allow@altogether@qand/or@applicationstheaishallsupportapplicationsthatconform@tbitrateaftertrafficclasseswithdifferent@is@ilimited@mandatory@Imonitor@need@Roptimize@xoptional@performance@preclude@squality-of-service@\rate@2@21@above@agreed@9-^editorial!"#%&*.012368lmpqtuv؀؁؃؇؈؎ؐؖؗ؞؟ةثح؃كڃۃ݃ރ߃non-binding W'W(W,W/WiWkWnWoWrWwW}W~W؄W؅W؆W؋W؏WؑWؘWWWWWWWWW Wtechnical W W W W WWWWWWWWWWWWWWWWW W'W(W,W-W/W4W5W7W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQW83 XcB?Yh؏ؙ '‚A89Gރ‚B3‚C‚DH‚E)‚FIу‚Hؿ‚I4a0v؁1.1klmتOpجح2qrstخدذر2.2uwxyz{|20؎3.1}~ز3.1.1 !"J؀؃؄؅؆4.1.1 #$STd؇؈؉س4.1.1.11.24.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.3ش4.1.4'؋ص4.1.5()*ضطظ4.1.5.1 +UVW]e،؍ئ׃4.1.6,-Pf؏ؐؑعغػ4.1.7.Q^ؒؓؼ4cthe W W W W WWWWWWWWWWWWW!W$W'W(W*W-W0W8W9W:W;W<W=W>W?WBWEWFWGWIWJWOWPWSW3? ]bAz#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." zcAOption 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. CurrentiGMember^Technical, Binding_14`6a4.1.5.1bg2693 2004/06/11n specific deployments.*<0 VWEMarcFGoldburg^Technical, Binding_12`22a4.1.5.1b"Remove option 1 and adopt option 2c)The concept of two phases is ill-defined d79g2687 2004/06/11XEMarcFGoldburg^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 documUcagreed;WaiGWشWWW W WairWWWW9WXW[W^W`W{WاWرWWWWWWW W W WWW&W)WairinterfacesupporttoenablenotclearرVall WWWW0W9W@WCWSW\W]WbWgW؍WءWئWWWW W!W*Wnsneedimprovementaddoption4CValloptionsareoverlydetailedwithrespecttospecificstaVV\VbV VallocationWallow W WWWWWSWTW[W`WWWWallowingWW[W`WWallowsWalreadyؠWWalsoqWsW؛WWWW Walthough]Walways؁W؜WambiguityبWambiguousزWشWصWطWWWWan WW!W'W/W;WSW|W؋WإWصWWWWWWWWWW!WanalysisWucand@anntenna@arq@ase@backend@kbe(^bearer@]because@between@]burdens@ocase@certainly@clarify@:column@conditions@confusing@contradicting@currentoptionshaveinternalinconsistenciesneedtoharmon@Pdecide@defines@definitions@delays@dense@description@detailed@duplexing@efficiencies@enough@figure@Bframes@grammarandclarifywhatlayersystemisbeingused@ahowerer@9implementaiton@3implementation@\^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. g2692 2004/06/11&8Ta4.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.d76g2684 2004/06/11UEMarcFGoldburg^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. 3d77g2685 2004/06/11VEMarcFGoldburg^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 bandwidthsd78g2686 2004/06/11.1.1?> ^cBThese requirements are consistent shall comply with the PAR...>@  33"  33/  33d‚h‚i‚j‚k‚lÃ!mÃ! nÃ!0oÃ!@pÃ!PqÃ!`rÃ!psÃ!tÃ!uÃ!vÃ"wÃ" xÃ"0yÃ"@zÃ"P{Ã"`|Ã"p}Ã"~Ã"Ã"؀Ã#؁Ã# ؃Ã#0؄Ã#@؅Ã#P؆Ã#`؇Ã#p؈Ã#؉Ã#؊Ã#؋Ã$،Ã$ ؍Ã$0؎Ã$@؏Ã$PؐÃ$`ؑÃ$pؒÃ$ؓÃ$ؔÃ$ؕÃ%ؖÃ% ؗÃ%0ؘÃ%@ؙÃ%PؚÃ%`؛Ã%p؜Ã%؝Ã%؞Ã%؟Ã&ؠÃ& ءÃ&0آÃ&@أÃ&PؤÃ&`إÃ&pئÃ&اÃ&بÃ&ةÃ'تÃ' ثÃ'0جÃ'@حÃ'PخÃ'`دÃ'pذÃ'رÃ'زÃ'سÃ(شÃ( صÃ(0ضÃ(@طÃ(PظÃ(`عÃ(pغÃ(ػÃ(ؼÃ(ؽÃ)ؾÃ) ؿÃ)0Ã)@Ã)PÃ)`Ã)pÃ)Ã)Ã)Ã*Ã* Ã*0Ã*@Ã*PÃ*`Ã*pÃ*Ã*Ã*Ã1Ã1 Ã10Ã1@Ã1PÃ1`Ã1pcfigureWW"W؆Wfigures!W9WfillWfinalqWfinalizedاWfirstWWXW^WW&WfixedWflexibleWWXW^WؕWW&Wflow!WWfocus؍WfollowWfollowthetextofc802.20-04-44inouropinionitiscleareVfollowed؁WfollowingWfor WWWWWWWW4W9WJWOWSWXWZW[W]W^W`WaWdWfWhWqWsW{W|W،W؍WؠWئWخWؿWWWWWWWWWWWWWWWW WWWWW!W&W(W)Wform-factordWformalWformatWforwardingؿWfragment WframeWnericخWget]Wgiven WWVWglobalvW؁WخWglobaladdpagenumbersvVglobalieshouldalwaysbefollowedbyacomma؁Vgoal؜WgraduallyWgrammaroWtW؃W4\$csituation]WئWsize WWSWW!Wsmall WWSWdWW!Wso!WWsoftWWsoftorhardhandoffsnotclearVsoftwareإWsole WWUWW#Wsolution<WsolvesؑWsome;WHWأWWWWsomethingآWsomewhatWspace#Wspan-WspecialWspecific WWWWWWWW(WAWVWXW[W\W^W`WbW{WWWWW W$W&W)W*WWWWWXW[W^W`WWW&W)WspecificationOWdWWspecified-W9WdWgWhWiWxWWWspecifies WWSWdWeWW!WspecifityMWspecify9WdWnWءWWWWspecs-manship WWUWW#Wspectral W WWW)W+WOWSWTWdW،WWWWW!W"WspecularOW>E bbReplace 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. d90g2222 2004/06/11 2004/06/08dEMarkFKlerer^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 .c 2d4g2220 2004/06/11 2004/06/08aEKazuhiroFMurakamiGMember^Technical, Binding_21`17a4.5.3bRemove sectione air interface without mandating 802.1 q at layer 2d4g2220 2004/06/11 2004/06/08aEKazuhiroFMurakamiGMember^Technical, Binding_21`17a4.5.3bRemove sectiong2697 2004/06/11DN dcATable 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. d91g2700 2004/06/114-1eEMarkScquite4WrؒWranWrangesWWrarely WWUWW#Wrate WWWW/W5W7WUWXW]W^W،WئWWWWWWW#W&WcwithinWWZWaWW(Wwithout WWWWSW[W`WWW!W)WwordpW؞WWWWWwordchoice؞Vworded=WwordingtW؎W؟WإWwordinggrammarclaritytVwordsWWworkqWzWحWWWW.WworkingWWworst،WwouldWW<WOWXW^WsW،WءWWWWW&WwritingqWwrittenWWWWwrongpWwrongwordpVxxxWyearsWWXW^WWW&Wyet WWSWW!Wd 0 @ P ` pI.‚J/‚Q0‚R1‚S2‚T3‚U4‚V5‚W6‚X7‚Y8‚Z9‚a:‚b;‚c<‚d=‚e>‚f?‚g@‚hA‚iB‚jC‚qD‚rE‚sF‚tG‚uH‚vI‚wJ‚xK‚yL‚zM‚NNMg 2004/06/11hEMarkFKlerer^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.  d95g2704 2004/06/11iEMarkFKlerer^Technical, Non-binding_19`34a4.5.2bADelete 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. ified as hard limit in a mobile environment.g2703Mark1LbmandatoryHWmanner@WWmappingأWmasks@Wmaximum+W@WؔWWWmayDWFWJWsWwW؊WؑWؓWأWسWصWWWmbpsضWطWW-Wmbs+WmbwaWWؗWتWmeansؒWWmeasureFWmeasuredWmeasurementFWWWmeasurementsFWWWmechanismiW؟WmechanismsAWLWأWWWWmediummWتWmeet@WؔWmentionedWmessage>W?WؙW؝Wmessage/data?Wmessages?WؙWؚWWnimum@WAWKWOWmitigateؗWmixؑWmmobilemWmobile:W@WAWCWmWqWsWwWxW{W|WؒWؓWؔWؗWmobilestationsshallperformwellquantitativerequirementsCVmobility+WCWRWW؋WmodeDWmodel!WsWmodelshWmodesCWKWmodificationؙWmodified*W<Wmodiulation@Wmodulation@WO/ctable-like6WtaggingWW[W`WW)WtargetedsWtargetsdWWtbrBWtcpWWXW^WW&WtddشWWtdma]WئWtechnicalqWtechnique WtechniquesjWؠWWtechnologies;WsW؍WضWtechnologyWW[W`W؍WءWWWW)WteethؾWtelematicstWtellsWtend2Wtense؀Wterm:WEWWWals{WغWterminologyؘtermsFWؠWWtermsarenotdefinednoraretheyrequirementsforasystemؠVtestablerW}W؅W؆W؉Wtext W(W,W4W;W>WLWؕWؙWؚW؛WأWثWWWWWWWWWtextbeginingonlinewithhowtheisunncessaryثVtextisinconjunctionwithother802standardsitistoobr VtextreplacedwithpreviouscommentproposingmoreextensiblؕVtextshouldbeanormativerequirementؙVؚVcoption1page18line4thetbrneedstobedefinedorelseBVoption1peakperuserdataratesisaveryimportantparame]Voption1peakratesresultinalargeuserdataratepeakto VVUVV#Voption2hasabetterorganizedformatwhichshowstherelevVoption2isnotdesiredظVoption2providesdescriptionforonlybesteffortdataleavؿVoption3issimplestraightforwardandwelldefinedVVYV_VV'Voption-1BWoptionalHWWK<jclimitation]Wline&W'W2W4W5W7WBWGWثWWWW WWline6isduplexingschemes&VlinearityWWlinearly-WlinesW6WNWWWlinkؒWlistsqWlittleOWWlookingWlooseWlossWWlowWWPWXW^WWW&WlowdelaylowdatalossratedoesnotprovidequantitativemVlowerdWqWlowersOWmacWWJWKWXW^W|WWWWWWW&Wmac-textأWmac/phyWWZWaWإWW(Wmacro/micro/pico.WmadeW+WmaintainWW[W`WW)Wmake W WWWSWTW]WئWWWWWW!W"Wmakes]WeWmakingdWmanagement Wmandate WketingsWmaterialWmatterhWmaximum9WWWmay0W4W=WؠWWWWWWWHicTwo 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.d96g2705 2004/06/11jEMarkFKlerer^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. d97g2706 2004/06/11kEDougFKnisely^Technical, Non-binding_5`4a1.1bA>These requirements are consistent shall comply with the PAR...>@EHeFKlerer^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.d92g2701 2004/06/11fEMarkFKlerer^Technical, Binding_13`20a4.1.6b{Change text to read: "In this state the user should have a radio bearer channel available with a delay of less than 100ms."cThe constraints on the time in which a channel needs to be available are to tight. For the 1.25 Mhz channel bandwidth either the number of users could be decreased or the time to have full use of the channel can be increased.d93g2702 2004/06/11gEMarkFKlerer^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.d94g2703bsuch+W;W@WCWJWKWsW؎WؒWؓWؕWؗWإWWsufficientjWؒWsuggestNWsuggestthatwedeleteitorreplacewiththefollowingNVsuitableIWsum]WئWsupportWW%W:WDWFWKWQWRW\WbWiWtWxWyWzW|WWؒWؔWؕW؟WؠWأWؤWإWدWرWزWشWWWWWWWWWWWWW W W*W,Wupported-WsWؔWأWsupportssW}WsustainedsWswitchإWsystem+W?W]WhWiWmWwWxWyWzW{W|W؇W،WؑWؒWؓWؔW؛WؠWؤWsystemsWsWؗWtable$W%W)W+W6WdWtaggingiWtakeKWtaking@W؇WtargetwWtargetedsWtargets]WؕWtaxedKWtddDWKWؐWtechnicaljWtechniques:Wtechnology-WIWJW؊W dj1WWspecifies 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. g2700 2004/06/114-1eEMarkV mbcAwkward sentenced100g2214 2004/06/11nEDougFKnisely^Technical, Non-binding_5`12a1.2b$Change "detailed" to "functional". cJThis document does not specify detailed requirements (whatever those are).d101g2215 2004/06/11oEDougFKnisely^Technical, Non-binding_5`15a1.2b"change "layer" to "ISO/OSI layers"c6Grammar and clarify what "layer" system is being used.d102g2216 2004/06/11pEDougFKnisely^ Editorial_5`20a1.3bChange "bases" to "basis"c wrong wordd103g2217 2004/06/11qEDougFKnisely^ Editorial_7`5a2b"work, home, and mobile"cAJcomma is missing before "and" in lists through the document; generally preferred usage is with the final comma, e.g., "item 1, item 2, and item 3" rather than "item 1, item 2 and item3". This is preferable in technical writing to clarify the binding of the last "and." Also recommend lower case for "work," "home," and "mobile."Jd104bneedFWKW{W؎WؽWneedmoreexplanationؽVneededFW{WWWneeds؅WWneedsthepluralVnegotiateؓWؔWnegotiatedؒWؓWأWnegotiationأWneigboringFWnetworkWWEW\WbWsWؗWأWإWاWWWWW W*WnetworksecurityinmbwasystemsshallprotecttheservicepؗVnetwork-basedإWWW!W%W(W*W+W,W-W:W<W>W?W@WAWCWFWIWJWKWNWOW\W]WbWdWfWiWmWsWuWwWxWyW{W|W؅W؇W،W؎WؒWؓWؔWؕWؗWofflineFWon-W9WAWDWjWrWtWwW؀W؏WؑWؒWؕWone%WAWJWPW]WiWmWonly؎WopentWoperating@WAWoperationsWؕWoperationsCWoperatorWW\WbWؒWؔWoppositeFWoptimalAWFcpriorityWWZWaWW(WprivaWprivacyWWprobabalisticWprobablyWproblemWproblemsؑWprocessdWproductsWprofilesWWXW^WW&Wpromote WproperFWWproperlyاWproposalJW]WdWءWproposals W W WWWWSWTWUWؠWWWW!W"W#Wproposed@WproposingؕWprotection؜Wprotocol=WWprotocolinlayer1and2VprotocolsLWprovedWprovide;WdWsWWprovidersW WprovidesFW]WئWؿWWprovisionWprovisioning WpublicWpublished؍Wpurpose WWUWW#WputsWqWW[W`WW)WqosWWWWMWXWZW^WaWؒWؓWؕWؼWWWWW&W(WquantitativeWquantityWW[_ sbcAEntire 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.d106g2220 2004/06/11tEDougFKnisely^ 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. @2004/06/11hEMark_Y tbc9Wording, grammar, clarity What the heck is "Telematics?"d107g2221 2004/06/11uEDougFKnisely^ Editorial_8`14a2.2bAdd period at end of sentence.c"Missing period at end of sentence.d108g2222 2004/06/11vEDougFKnisely^ Editorial_0`0a0cGlobal: Add page numbers!d109g2223 2004/06/11wEDougFKnisely^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 ltiplayer gaming. @ould" on line 5g2714 2004/06/11Q[qg2218 2004/06/11rEDougFKnisely^Technical, Non-binding_7`5a2bDelete "should" on line 5cWheadings*WhecktWhenceW Where0WEWآWWWWhi-defWhighWWZWaWWW(WhigherWWWhoWhomeqWhooks WhopeWhowإWثWW WWhowistherequirementforfastanddynamictransitionsbetw VWietfyWWif]WhWkW،W؍WبWWWW Wiff؍WilineWiline20readsservicetheuser'sprivacyandmitigateagainVill-defined WWWWimmediately؊Wدc:The sentence beginning with "The 802.20...)" is not clear.d165g2330 2004/06/11ذEEshwarF Pittampalli^Technical, Binding_7`12a2b/Please clarify what exactly is the requirement.cLBest in class "overall network complexity" -- the requirement is not clear.d166g2331 2004/06/11رEEshwarF Pittampalli^Technical, Binding_8`10a2b%Replace it with "enablers to support"c,"air interface support to enable" not clear d167g2332 2004/06/11زEEshwarF Pittampalli^Technical, Binding_8`19a3.1bNReplace it with "support non-line of sight outdoor and indoor coverage areas."c*"support non-line of sight...." ambiguousd168g2333 2004/06/11سEEshwarF Pittampalli^Technical, Binding_11`21a4.1.1bReplace "should" with "may"c6"should" implies a required feature which is not true.d169g2334 2004/06/11شEEshwarF Pittampalli^Technical, Binding_12`11a4.1.3ardg2773 2004/06/11^~c`Need to support non-bursty traffic as well. Bursty case is clearly covered by rest of sentence.d117g2231 2004/06/11EDougFKnisely^Technical, Binding_9`7a3.1byDelete "The 802.20 AI shall support high-speed mobility." Alternatively, define speed requirements for mobility clearly.cNot defined; untestable.d118g2232 2004/06/11؀EDougFKnisely^ 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.d119g2233 2004/06/11؁EDougFKnisely^ Editorial_0`0a0b; globally change "i.e." to "i.e., x"c7Global: "i.e." should always be followed by a comma. d120g2234 2004/06/11؃EDougFKnisely^ Editorial_9`14a3.1.1b#change "PPP, MPLS" to "PPP or MPLS"cGrammard121g2236 2004/06/11؄EDougFKnisely^Technical, Non-binding_9`16a3.1.1bDelete "partitioning"dbindoorCWزWWW,Windor,WinformationAWwWxW{W|WؓW؝WأWWWinformativeWW W W WinfrastructureWinitialKWinitialtextforthisnewsub-sectionKVinsert!W#W/W5W7W@WJW]WWinsertaspacecharacterafterhz#V))bdeliverwWdeliveredwWؕWdeliveryxWyWؓWؔWأWdells{WdemandؓWdenialؗW؜WWdensehWWdependingؑWdeployment%WIW؇WdescribedؕWdescriptionؿWdesignKWLWWWdesignedJWsWWns؊WdesirableWdesiredOWwWdetail@WdetailednWdetermine WWSWdeterminedؒWdevelopjWdeveloped@WdeviceKWsWخWdevices@WsWdifferent/W5W7W؏WؔWغWWdifferentiatedؓWأWdifferingؓWdiffferentWdiffservأWdisable{WdisclosureؚW؛WdiscriptionWdiscussjWdiscussthesectionwithatechnicalperspectiveanddevelopjVdisruptionCWdistinction WWTWdistinguishؓWdistinguishingiWdistortion@WdiversityWdivided؇WdlطWWdl/ul+Wdoable؉WdocumentmW؇WتWdon't؉Wdos؜WEbresultsFWWretaingWrewordWrewordasfollowstheairinterfacedesignshallscaletowiVrewording=WrewriteآWWrewritethewlineasfollowsVrf@W؟WrfcأWrm!WroleKWsWroutemWroutedأWroutingzWrsvpؒWأWrules@WruralhWWWsWsafelyإWsafety@WsameؓWWWsameascomment35Vsar@WsatisfiesأWsatisfy؎WؓWؼWsatisfyingؓWscaleWWscaling-WWscalingtheabovepeakdataratesinthereferencecasebyaVscenariosWW,Wschemes&W؊WscopeؒWscreentWsecondsؔWsectionWWWWWWW(W*W+W.W1W;W@WKWXWZW[W^W`WaWgWjWؕWآWأWبWWWWWWWW W WWWWWWW&W(W)Wsecurity<WؗW$Sbreceiver@WreceivingxW|Wrecipient?WrecommendedؔWreconfigurableNWreduction؟WWreference!W1W;WWWWWreferences0WWreferredWreflectWregulatory@WrelativesWrelaymWrelevanthWreliabilityؖWؠWremove W W W WWWWWWWWWWWTWUWVWWWXWZW[W^W`WaWWWWWW W WWWWW"W#W$W%W&W(W)Wremovemustorwilltomakethisaninformativesection Vremoveoption1andadoptoption2 V V VVVVUVVVWVVVV#V$V%VremovesectionVVVVZV[V`VaVV(V)V\WbWتWجWحWخWدWرWزWسWشWصWضWطWؼWWWWWWWWWWWVDabreceiver@gremovesentencestartingwithaqosbasedipnetwork@$replace802.20'sworkwiththestandard@replaceitwithsupportnon-lineofsightoutdoorandindoor@replacethissentencewiththisdocumentprovides/definesth@requirements@restore@results@fsector@Esee@shall@،|should@shouldread@specifyassociationofenvironmentswiththeappropriatecha@speeds@zstations@such@Osupportoption2forperformanceundermobilityanddelaysp@telematics@`the@the802.20macdesignshallspecifymechanismsetc@>the802.20systemshallprovidethemacandphycapabilities@the802.20-basedair-interfaceaishallbeisoptimizedfor@thesystemshallsupportthefunctionalityofmeasurementsi@802.20systemsshouldworkeffectivelywithbroadcast/multic@aؚability@~above@aggregation@agreed@9C1bis WW+W-WJWKWOWSW]WiWmWsWwWyW؀W؁W؅W؇W؉W؎WؕWؗWئWذWؾWWWWWWWW W WWWW!Wiso/osioWissuesؒWit+W;WJWKWNW؜WرWزWشWصWضWطWؼWWWWW W W WWitshallbepossibletoprovideprotectionagainstdenialof؜VitsAWjWituؔWjitterؓWؔWjoingWjointWWWkbps-WingAWkeptCWIWkeyCWkm/hدWWkm/hrCWland@WlastWlatencyQWsWؔWؕWlayer!W@WFWJWKWiWmWoW؇W؎WؒWؕWlayerprotocolsأWlayers<WoWؔWؗWتWWlayersthemWleast%WmWWlengthؕWless,WfW؎WؕWlessenWlevel@WCW؎WlevelsAWlicentsedتWlimitationstWZ^ {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.Ed114g2228 2004/06/11^cbackendWWZWaWW(Wbad؍Wbandwidth WW-WVWfWWWWW$Wbandwidths WWVWW$WbaseWWbased{WWWWbasedonthestandardsandproductstimeframethetechnologVbasesجWWbasis{WbcmcyWbcmcmustsupportietfipbroadcastandmulticasttrafficefyVbe W W WWWWWWWWWWWW!W$W-W0W4W9W;W=W@WBWGWHWIWOWPWSWUWVWXWZW[W\W]W^W`WaWbWfWgWhWiWjWkWrWsWxW|W؁W،W؍WؙWؚW؛W؜WؠWءWأWؤWإWاWبWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWW W!W#W$W&WWp ^؇bAODefinition: 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.d125g2240 2004/06/11؈EDougFKnisely^ Editorial_11`16a4.1.1bchange "QoS' to "QoS,"c Missing commad126g2241 2004/06/11؉EDougFKnisely^Technical, Binding_11`21a4.1.1؄EDoug؃EDoug^ Editorial_9`14a3.1.1b#change "PPP, MPLS" to "PPP or MPLS"cGrammarg2236 2004/06/11؄EDoug؛cdText should be a normative requirement. Also strengthen to include other MT identifying parameters.d145g2260 2004/06/11؜EDougFKnisely^Technical, Binding_17`8a4.1.11.4bAeIt shall be possible to provide protection against Denial of Service (DOS) attacks whenever possible.e@A>  33R  33d  33>ctIn a wireless system, protection against DoS is not always possible, but should be a design goal whenever practical.d146g2261 2004/06/11؝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." Schange "PPP, MPLS" to "PPP or MPLS"cthisdocumentdoesnotspecifydetailedrequirementswhatevenVthisisafeatureoftheuserterminalandbackendinfrastruVVZVaVV(Vthisisstatedelsewheresection4.1.3itisaduplicatedreVthisparagraphgoesintogreatdetailonwhatietfrfcstouVthisparameterisunderstoodtobeascalablequantityhowevVthisrequirementaswrittenplacesmayrequirementsonthemV]FcburdensgWbursty~Wbut]WgWjW؜WؠWءWآWئWWWWWbwsHWby WW<WSW~W؁W،W؍WؒWؠWآWWWWWW!Wc802-20-04-33r1 WWUWW#Wc802.20-04-44WWWWWWc802.20-04-44textinsection4.1.5.1representsaconsensusVc802.20-04-46JWc802.20-04/55Wcall]WWcanWWWWXW[W^W`WfWiW؍W؝WWWWWWW&W)WcannotgW؍WاWcapabilities{W؍WcapabilityWcapacity،WؑWػWcaptializationsWcaptionWW$W%WcapturedWWZWaWW(WcarriedWW[W`WW)Wcarrier؍Wyawkdefinition؇Vclarify/changeIWclarifying WWSWclarity<WtWclasssWclasses/W8Wclear:W<Wclearly~Wlt~؉bDelete "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.d127g2242 2004/06/11؊EDougFKnisely^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.d128g2243 2004/06/11؋EDougFKnisely^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.d129g2244 2004/06/11،EDougFKnisely^Technical, Binding_13`5a4.1.5.1mmarg2236 2004/06/11؄^Technical, Non-binding_9`16a3.1.1g2732 2004/06/11baltogetherCWamodified]Wan'W+W<WCWPWmWwW؋W؎WؐWؒWؔWؕWؖWإWتWWWWWW W WWWand W W W W WWWWWW!W*W+W0W;W>W?W@WAWCWFWHWIWJWKWMWNWRWSWTWUWVWWW]WdWeWhWjWmWqWsWtWwWyWzW|W؀W؅W؇W؊W،WؒWؓWؔ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"W#W$W%W,W-Wable W@WFWhWapplication؟WapplicationsNWsWtW؎WؓWؔWؕWغWwibgloballychangeiexwhichisnotcommatoiex؁Vgood-putFWgraceful؉W؟WWgraphicaltWgreater-WCWhandAWhand-held@WhandoffFWharmonize9Wharmonizewiththeappropriate802.20contributionsonthis9Vhas]WhaveKWfWheading*W>W@Wheight@WhelpingAWhigh-speedsWWhigher:W؉Whighre<WhomeqWhow؅WhoweverOWhz#W؇Wi{W؁WidentifiedwWidentify{Widentity?WidleAWieee!W<W@Wietf-specifiedzWifFWJW]WigmpzWignorewWimd@WimplementationmWimplementationsDWNWimprovedsWinWW W%W*W.W1W:W;W@WAWCWFWHWIWJWKW]WfWhWiWmWsW{W؇WinabilityCWinclude@WAWFWincludes<WincludingtWindependent]Windication?Windividual?WwWbprecludexWإWWpreferential؎WغWpreferredبWprescribedFWpresent{WpreservationWpreserveAWWprevent؛WpriorityإWprivacy>W?WؗWWWprobabilityؕWWproceduresأWإWprocessingFWproofKWproper6Wproposals؊WproposedW:W<W=W@WCWWWWWWproposedchangeoftheentiresentenceinline6theaishal:Vproposedmodifiedtextthesecurityprovisionsofieee802.2<Vproposedoption4CVproposedrewordingtheai'ssecureaccesscontrolshalluse=Vproposedtextforsection4.2.1.1general@Vprotect?WؗWؙWؚWؙW؛W؜WprovidedؔWprovidedwillؙWؚWproviderؗWprovidersNWprovisionؗWprovisioningNWprovisions<WNWpublic@WpurposeKWmWpurposes-Wput;Wqos+WMWNW؈W؎WؒWؓWؔWؕWqualityFWpvI،bDelete "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.d130g2245 2004/06/11؍EDougFKnisely^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.cnical, Binding_13`5a4.1.5.1v{ ؎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.d132tu ؍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.6d131g2246 2004/06/114-3؎EDougFKnisely^ Editorial_13`20a20b1.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.c5a4.1.5.1rbgracefully؉W؋WصWWgraphicaltWgreater-WCW،WWhaltWhandAWhand-held@WhandoffFWWWhandoffsWhardWhardware؛Wharmonize9Wharmonizewiththeappropriate802.20contributionsonthis9Vhas]WإWئWhaveKWfW؎WؠWإWheading*W>W@WآW,Wheadings؍WheavilyإWheight@WhelpingAWhereWhigh؋WإWWhigh-speedsWWhigher:W؉WؗWدWصWhighre<WholdingإWhomeqWhooksاWhopأWhow؅WثWhoweverOWhz#W؇Wi{W؁W؉W؍W؎WؓWidealWidentifiedwWidentifier؛Widentify{Widentity?W؛WidleAW Wieee!W<W@WؕWةWWWWietfأWietf-specifiedzWifFWJW]W؏WئWغWWgtWindependent]Windication?Windividual?WwW؊Wboptimize؊WoptimizedAWJWKWsW؟WتWoption W W WWWWWW+W4WCWQWRWUWVWWWYW]W_WeWgW؍WبWظWWWWWWWWWW#W$W%W'W.Woption1modificationVoption1preferredthe802.1qsectionshouldbedroppedبVoption3+V2W4cversion;Wversus W WWWSWTWWW!W"Wvery WWSW]WئWWWW!WviaWvideoWvlanWW[W`WW)WvoipغWvsؒWؓWwؒWwant0Wwas;WhW،WؒWWWwayWwaysWW[W`WiWW)Wwe W W WWWWWW0WSWUWVWXW^W؆WءWWWWWWWWW WWWWW!W#W$W&WthissectionitdoesnotseemrVwe'reWwellWWYW_W~WWWwere0WWwgdWwhat)W<WhWoWsWtW؄WؑWؒWآWئWWWWWwhatisapartitioningmodel؄VwhattheheckistelematicstVwhatevernWwhenWWWWXW[W^W`WWWWwhenever؜WwhereWwhereasOWwhetherWbspeeds؉W؋WصWWspreadRWspreadsCWspurious@WsserviceأWsslؗWstability@Wstandard@WCWFWHWIWJW؅WؒWؔW؝WأWةWحWWWWWstandards W@WtWأWاWWstandards-basedWstart|WstartingWWWstatefW؎WWstatedؕWstatesAW Wstation:WAWEWmWؒWؗWخWWWWWWu؎g2247 2004/06/11؏EDougFKnisely^Technical, Non-binding_13`29a4.1.6b[Delete "This requirement shall be met even if the sessions are all on different terminals."c Confusing, unnecessary sentence.d133g2248 2004/06/11ؐEDougFKnisely^ Editorial_14`1a4.1.6b+"a FDD" => "an FDD" "or TDD" => "or a TDD"cClarifyd134g2249 2004/06/11ؑEDougFKnisely^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?").d135g2250 2004/06/11ؒEDougFKnisely^Technical, Binding_14`9a4.1.7b#  33)  33*  33O  33m  33x  33N  33f  33j  33.cClarify wording.g2247 Obshall،W؏WؒWؓWؔWؕWؗWؙWؚW؛W؜W؝W؟WؠWأWإWاWدWشWضWغWWWWWWWWWWWWWWWWWWWWW WWWW W*W,W-WshallmustؤWshort؎W bdeletebursty~VdeletecurrentlyVdeletelines13-16textbeginningwithhowtheثVdeletenotedependingontrafficmixwithinacellthecontrؑVdeleteoption24VظVdeleteorusethefollowingtextiVdeletepartitioning؄Vdeletephase1columnsdeletephase2headingsiephase2r؍VdeletepotentiallyonlyعVdeletesectionVVVremoverequirementsandpreserveasininfVdeleteshouldonline5rVdeletethe802.20aishallsupporthigh-speedmobilityVdeletetheentiresentencethatspanslines1718asanexam'Vdeletetheindividual802.20technologyproposalsmayoptimi؊VdeletethelastthreewordsandendupwithVdeletethesentenceGVdeletethespectralefficiencyathigherspeedsthanthoses؉Vdeletethetwolistedcontributionreferences03/45r1and030Vdeletethisrequirementshallbemetevenifthesessionsar؏Vdeletethissectionorretainoption3gV>cability{Wable]WئWWaboutآWW{ ؒbAThe 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. @A  33  33  33  338  33B  33M  33Q  331  33P  33d  33r  33o  33  33larify wording.g2247bavoidance@Wb/s/hz/sectorOWdWbackboneiWband@Wband-classes@Wbands@WتWbandwidth)W+W@W؊WؠWWWWWbandwidthsHWIWWbase:WAWEWmWؒWؗWWWWWbasedsWtWwWؒWؕWأWWbasespWWbasesbecomesbasissincetableistheobjectVbasispW؝WجWWbatteryAW Wbe W)W+W-W<W?W@WAWCWFWHWIWJWOWhWsW{W؀W،W؍W؎W؏WؑWؓWؔWؕWؗWؙWؚW؜W؝WؠWأWإWcduplexing&WduplicatedWdvdWdynamic{W WeqW؁W؍WؑWeachWWWWearlier;Wearly؍WeasyWeditorialWWeffecftivenesdWeffectivelyzWoccaseqW~Wcdma]WئWcdma2000Wcell WWSWW!Wcells WWSW{WW!WcellularWW.WcellularwordconveysonlypartialinformationV؀VchangedأWchannel W WWWHWOWSWVWfWWchannels]WئWcharacter#WcharacterizeOWchoice؞WclaimssWclarification;WDWclarified WWVWclarify)WoWqW؆W؇W؎WؐؒWؔWؗW؝Wclarifyawkdefinition؇VclarifynetworksecurityrequirementsؗVclarifyrequirementswrtlinklayervsend-to-endqosandؒVclarifytrafficclassesؔVclarifywording؎Vclarify/changeIWclarifying WWSWclarity<WtWclasssWذWclasses/W8WؔWؕWؿWclear:W<WتWدWذWرWػWؽWWWWWWclearly~WcloseWXcneccessary]WئWnecessary;WjW؍WWWneedWWWW!W)W*W+W.W2W9WAWCWHWIWMWZW\WaWbWxW{W~WؓW؝WءWWWWWWW W(W*WneedclarificationtothetextVVneedfurtherclarificationontherequirementVneedtochangetheheadingsofsections4.1.5and4.1.5.1an*Vneedtoclarifythatsystemcanoperatewithanycombination؝Vneedtoclarifywhatconsistentwithspectralefficiencymea)Vneedtoclarify/changethesentencethedesignshallbeIVneedtoconsolidatewithorrefertosection4.4.1thatdisc.Vneedtodistinguishintra-uservsinter-userqosrequirementؓVneedtostatethatsomechannelbwsshouldbemandatoryandHVneedtosupportnon-burstytrafficaswellburstycaseiscl~VneededOWdW|WبW ؓbB. 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.d137g2252 2004/06/11ؔEDougFKnisely^Technical, Binding_14`19a4.1.7.1bstreams of information) 33  338  33B  33M  33Q  331  33P  33d  33r  33o  33  33ؒcClarify requirements w.r.t. link layer vs. end-to-end QoS and clarify what was intended by "Policy-based QoS architecture," which is not defined.d136g2251 2004/06/11ؓEDougFKnisely^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)  338  33B  33M  33Q  331  33P  33d  33r  33o  33  33|bshallWWW%W)W:W=W?W@WCWFWHWJWKWLWNW\WbWhWkWsWtWxWyWzW{W|W}WW؅W؆Wwd~bigmpzWignorewWimageإWimd@WimplementأWimplementationmWimplementationsDWNWimprove WimprovedsWinWW W%W*W.W1W:W;W@WAWCWFWHWIWJWKW]WfWhWiWmWsW{W؇W،W؎WؓWؔWؕWؗWؠWءWأWئWتWدWضWغWWWWWWWWWWWWWWWWWW WWW+W-WinabilityCWincertئWinclude@WAWFWأWؿWWincludeexpeditedforwardingtrafficclassdescriptionؿVincludes<WincludingtWأWWWincorporatedؚWincrease؟WWincreasingؠWindependent]WئWWindication?Windividual?WwW؊WؓWindividualsWindividulaؒW jؔb@A   33  33)  33*  332  33D  33  33   33\  33i  33  33cClarify traffic classes...d138g2253 2004/06/11ؕ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 sensitive all corrections provided by the MAC/PHY layers) (10E-8 to 10E-1), and - delay variation (jitter) (10 ms to 10 seconds). )bbbeاWبWضWغWWWWWWWWW WW-Wen 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. @A  33  33  33  338  33B  33M  33Q  331  33P  33d  33r  33o  33  33 ؔ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). qcdefinesWW[W`WW)WdefiningتWdefinition]WsW؇WWWW ؕ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).d139g2254 2004/06/11ؖEDougFKnisely^ 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.d140g2255 2004/06/11ؗEDougFKnisely^ Editorial_16`19a4.1.11bo 10 seconds).  ء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.3d151g2266 2004/06/11آEDougFKnisely^Technical, Binding_18`24a4.2.6bcDelete all text (and possibly the section heading, too). Alternatively, rewrite to clarify intent.cANo idea what this section is trying to say. MIB-like parameters are defined elsewhere. The only thing unique here is "intra-frequency, inter-frequency, ...". Perhaps something about operational service metrics is desired, but not described by this non-testable requirement.d152g2267 2004/06/11أEDougFKnisely^Technical, Binding_19`4a4.4.1b>bthe802.20systemshallprovidethemacandphycapabilitiesؓVthe802.20systemshallsupportnon-lineofsightoutdoorto,Vthe802.20systemsmustbespecifiedtoenableubiquitousmoVtheaishallsupportautomaticselectionofoptimizeduserd؟VtheaishallsupportpeaksystemdataratesinexcessoftheVtheaishallsupports}Vtheai802.20standardshallsupportthemeanstoenablelinkؒVthelineshouldreadVthemaclayershouldbeabletocontrol100simultaneousact؎VthesystemshallsupportanarbitrarysetvarietyoftrafficؔVthesystemshallmustsupportbothipv4andipv6ؤVthesystemwillshallprovideappropriatemacandphycapabi؛VthetextshouldreadthesystemshallworkindenseurbansuhVtheftؗWtheirAWFW؊Wthere{Wthese@W]WkWئWWtheserequirementsareconsistentshallcomplywiththeparkVtheyإWWthink؉W 8ؗbA  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  33ffic classes).g2254 2004/06/11ؖEDoug^ 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.g2255 2004/06/11ؗEDoug^ Editorial_16`19a4.1.11b :ؗ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.@ffic classes).g2254 2004/06/11ؖEDougFKnisely^ 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.g2255 2004/06/11ؗEDougFKnisely^ Editorial_16`19a4.1.11bpbassumesWassumed-WWWassuredأWatW!W%W:W@WCWFWiWmWuW؉WؓWؕWؗWإWWWWWWWattachedWattacksؗW؜WWattainable+WattainedOWattempting{WattributesWCWsWؔWaudiotWؓWaudio/videoؕWauthenticationؗWؘWWauthorizationؒWauthorizationsؒWauthorizedxW{Wautomatic؟WavailabilityIWavailable,WfWiW؎WWWWaverage*W@WeW؇W،WضWW-WavialableاW@W؊WؠWbandwidthsHWIWbase:WAWEWmWؒWؗWbasedsWtWwWؒWؕWأWbasespWbasispW؝WbatteryAWbe W)W+W-W<W?W@WAWCWFWHWIWJWOWhWsW{W؀W،W؍W؎W؏WؑWؓWؔWؕWؗWؙWؚW؜W؝WؠWأWإWb11$W12+W؀WطW128kbps،WW13؀W13-16ثW15.W;W17W'W18W'W19WDW2 W W W WWWWWW!W"W%W*W+W4W@WJWRWSWUWVWWW]WeWiW؍WؔWؕW؝WإWئWضWطWظWWWWWWWW!W#W$W%W@V2-1W2-3]WئW2.0+W2001ؕW23$W25,W250CWدW2597أW2598أW25ms؎W28AW3WW!W%W*W+W-W@WQWYW_WgWؕWأW3insertnewsubsection4.2.1.2radiotransmitter@V3-1W3-2!W"W3.0طW3.1W!W3.1.1KW3.5تW3289أW33HW34562WؕW360-W4%W@WCWؕW4insertnewsubsection4.2.1.3radioreceiver@V4-1$W)W+WdW4-2%W4.1.1(W4.1.1.2>W4.1.5*W4.1.5.1*W Iؗbc&Clarify Network Security requirements.d141g2256 2004/06/11ؘEDougFKnisely^Technical, Non-binding_16`27a4.1.11.1b+"Access control" => "Access authentication"c Terminologyd142g2257 2004/06/11ؙEDougFKnisely^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.d143g2258 2004/06/11ؚEDougFKnisely^Technical, Binding_17`1a4.1.11.2bS, SSL, IPSec, etc.@IPSec, etc.@2751 2004/06/11m ؚ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.d144g2259 2004/06/11؛EDougFKnisely^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  33znauthorized disclosure shall be providedwill be incorporated.@ bapplicationstheaishallsupportapplicationsthatconformtVapply@WCWapproachWappropriateW+W9W?WؕW؛W؟WWapprovedWapproximatelyWarbitraryؔWarchetecture]WarchitectualKWarchitecture]WؒWؕWأWWWWW+WarchitecturesKWareWQW]WkWwWxW{W|W؏WؔW؟WإWئWدWغWWWWWWWW+WareasزWWarrivedإWarrivingإW.lbas@assume@avoidance@beاbearer@)becomes@c802.20-04/44@ce@chanegtheentiresentenceasfollowsthephysicallayermea@changefigure2tofigure3-2@changetoduplexingschemesfdd/tdd@classic@concerned@,contention@defineanactiveuserasonewhocangetaccesstoabearer@definition@ deletebursty@}deliver@edownlink@duplexing@encryptionacrosstheairinterfacetoprotectuserdatatra@every@1experience@frequency@#global@globallychangeiexwhichisnotcommatoiex@rgracefully@wigmp@indoor@dinsertbitrateaftertrafficclasseswithdifferent@is@ilimited@mandatory@Imessaging@monitor@need@Rnetworks@oa&m@optimize@xoptional@performance@preclude@sprotected@quality-of-service@\rate@ bduplexing&W؊Wduplicated?Wduration؎Wduring؎Wdynamic WemWtWwWzW{W؁W؍W؎WؒWؓWؔWؖW؛WإW+We-mailtWeachwWؒWؓWؔWؕWeapؗWeasingWeditorialWefأWeffective:WFWeffectivelyWW\WbWاW W*WeffectivenessAWefficienciessWدWefficiency WW(W)W+WOWSWdW؇W؉WؠWWW!Wefficient|WWWefficiently{WeffortؕWأWeirp@Weither;WDW؝Welectronic؛Wemission@Wemissions@WemployAWأWemployed?WenablesWؒWاWWWenablersرWencryptionؚW؝WenvironmentiWenvironmentalAWenvironmentshWequipment@WerrorFWؓWؔWؕWeswWetc:W<W@WLWؗWevaluation WW-WSWeven؏W$buser's?WؓWؗWWusersNW]WsWؒWئWدWusersconstraints؎WusingyWؓWWWusuallyWutilizezWvaluesؔWاWWWWvariationؔWvarietyؔWvariousWW\WbWؒWؓWؔWدWW W*WvehicularCWhWدWverify@WversionWveryإWviamWwWvideotWؓWvisionWvoiptW؎WvpntWwغWذWwhen{W|W؅Wwhenever؜Wwhich WWHWNWOWSWmWxW|W؁W؎WأWwhileAWؓWؕWwhoPWwholesaleiWwide-areasWخWwiderIWwill@WKW؀W؎WؙW؛WؠWwireless@WsWةWتWخWwithWW W(W*W,W/W5W6W7W9W;W@WIWNW\W]WbWdWeWfWjWkWmWzW؎WؓWؔWؕWؗW؟WأWتWثWجWحWخWدWرW2cunderstoodWunderwayWunicastWuniqueآWunknownWunlikeWunmeasurable WunncessaryثW ;bBg;bBg;g;g;;إbBg;bBg;m؝chNeed to clarify that system can operate with any combination of integrity, encryption, neither, or both.d147g2262 2004/06/11؞EDougFKnisely^ Editorial_17`17a4.2.1b"practice" => "practices"c Word choice.d148g2263 2004/06/11؟EDougFKnisely^ 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 wordingd149g2264 2004/06/11ؠEDougFKnisely^Technical, Binding_17`24a4.2.2bEbsee.W;W@WselecteWselectoption2anddeletetextdealingwithaveragerateseVselection؟WWselectivity@Wsender?WsensitiveؕWsensitivity@WsentFWsentenceW'W(W)W-W:WFWGWHWIWuWتWWWWWWW WWWWseparateؓWserial؛WserversWserver-clientsWserviceW+W8W@WCWFWNWwW؎WؕWؗW؜WأWWWservicessWtWأWWWWsessionCW؎Wsessions-W؎W؏WغWsetؔWأWWWseveralؓW#b802.20-basedsWWWWW90،WW95WaWWW!W#W%W*W+W,W-W1W6W;W@WFWHWJWKWPW\WbWdWfWiWjWmWsWwW؇W،W؎WؐWؑWؓWؕWؗWؙW؝W؟WأWإWاWدWضWWWWWWWWWWWWW W*W+WovidemessageintegrityacrosstheairؙVabbreviationsWabilitywWxW{W|WؒWؓWؔWإWable؎WaboveWabsence؎WabstractKWacceptableWaccess=WFWPWmWؘWةWتWWWaccesscontrolaccessauthenticationؘVaccommodateKWaccordanceؕWaccount@WKWaccounting|Waccuracy@Wachieve:WAWachieved WWSWدWacrossؙWؚWactivePW؎WدWactivities|WactivityؓWadaptationؠWWadaptiveؠWWRbnetworksmWzWnew!W.W@WHWKWإW,W-WnextأWno{WWnoiseAWWnon-discriminatoryWnon-lineزW,Wnon-line-of-sightWnot@WFWKWtWxW{W؁WؑWؕW؝WإWWWWnotewW؎WؑWnounWnumber*W-WAWKW؛WدWWnumbersطWoaWJWKWNWOW\W]WbWdWfWiWmWsWuWwWxWyW{W|W؅W؇W،W؎WؒWؓWؔWؕWؗW؛W؜W؟WأWإWئWاWتWofflineFWofing؟WoldإWon-W9WAWDWjWrWtWwW؀W؏WؑWؒWؕW؝W؟WأWone%WAWJWPW]WiWmWإWئWonly؎WopentWoperating@WAWتWoperationsWؕWoperationsCWoperatorWW\WbWؒWؔWإWاWoperatorsأWoppositeFWoptimalAWT_‚(@ACYhؚ؛؜؝؞؟ؠăŃƃǃȃ߃'‚)BDEFGHIءآɃʃ˃̃̓΃σЃу.‚*KLMN[_iأؤ҃ӃԃՃփ)ئ@تP%5LMNk}؛أ` 0STdqr؊،ؑضػp&:O]l~Zms؇؍ط_ؖ؜إخد6`ؒؓ‚!#رÂ"شظ‚#n؀ذ‚$ Pثؼ‚%uwxyz{|؃‚&.;Q\jot‚'@CX^g؄؈‚('a؋؞ص‚)!+R؅˃‚**/Kؔؗز‚1()fp؎؟جح‚21؉ؕءؤس‚3 2UVWeعؽ ؠbA 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.d150g2265 2004/06/11ءEDougFKnisely^Technical, Binding_18`21a4.2.5bDelete all text in 4.2.5.cing 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 @cal.g2261 2004/06/11&ؚbA؛cm؝cؠbAءcAأbACؤbAإcئةFجbدcbشbطbػaFcE^cgcAkAFbcbbcAb^bAyA c cA bcAccccGE'E( a- b0 c5c=F?F@cAGcIaAcBHcAL bM!cAN"cQ%_T&cBS)cAX+b[.ceeIRbmessagingAWtWmet؏WغWmethodؙWmethods=W?WmetricsWW\WbWاWW W*Wmhz+W-WطWWmibاWmibsWW\WbW W*Wo-secondsCWmicrocellsWmimoؖWminimal؎WminimizeAWminimum@WAWKWOWWminorWmitigateؗWWmixؑWmixesWmmobilemWmobile:W@WAWCWmWqWsWwWxW{W|WؒWؓWؔWؗW؛WأWإWةWتWخWدWWWWWWWWWWWWWmobilestationsshallperformwellquantitativerequirementsCVmobileipv4Wmobileipv6Wmobility+WCWRWW؋WدWصWWWmodeDWmodel!WsWأWmodelshWWmoderateWmodesCWKWشWWmodificationؙWWWWWmodified*W<WئWmodiulation@Wmodulation@WؠW1KbencryptionacrosstheairinterfacetoprotectuserdatatraؚVendW(WuWأWWend-stations!Wend-to-end<WؒWؗWend-userؔWؗW؛WenforceؒWenforcementأWenoughؕWensureؗWإWentire'W:WFWentry)W+Wenvirnomental@WenvironmentiW؟WدWenvironmentalAWenvironmentshWWequipment@WerrorFWؓWؔWؕW؟WإWeswWestablishedWetc:W<W@WLWؗWevaluation WW-WSWW!Weven؏WغW~YcaؚW؛W؜WؠWءWؤWإWئWخWسWWWWWWWWWWWWWWWWWWW W WWWWWWWWW!W"W#W&W(W)W.WasimpleeditorialchangetoelinateunneededwordsinthefV/6Fctextshouldbeanormativerequirementalsostrengthentoin؛Vtextsuchasinline38itmaybeusefultoconsiderisnot4VthandWqWsWWWWWthat W WWWWWWW.W0W;W=W?W@WHWOWPWSWVWXW\W^WbWdWgWsW{W؍WؑW؝WؠWءWغWWWWWWWWWWWWW WWWWW W!W$W&W*WthatthefollowingtableispresentedasthebasesV hؤbAR  33   33  33  33R heading, too). Alternatively, rewrite to clarify intent.cto 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.3g2266 2004/06/11آEDougFKnisely^Technical, Binding_18`24a4.2.6bcDelete all text (and possibly the section heading, too). Alternatively, rewrite to clarify intent.ceed to specify all the possible non-requirements.3g2266 2004/06/11آEDougFKnisely^Technical, Binding_18`24a4.2.6bcDelete all text (and possibly the section heading, too). Alternatively, rewrite to clarify intent.cer allocation. The system will have adaptive modulation and coding in both the uplink and the downlink @s\Qbprotected؝Wprotection?W؜Wprotocol!W<WmWؕWؗWأW WprotocolstWzWؒWprovide?WFWJWsW{W|WؒWؓWؙW؛W؜W؟WأWاWWWWWWW W+WprovidereferencesforbestcommercialpracticesVprovidethereferencestootheripnetworkstandardsandipVprovidedؔWWWprovidedwillؙWؚWproviderؗWprovidersNWprovidesWprovides/definesتWprovidingWprovisionؗWWprovisionableاWprovisioningNWاWprovisions<WNWpublic@WpurposeKWmWpurposes-WpushإWput;Wqos+WMWNW؈W؎WؒWؓWؔWؕWأWؼWWWWqqualityأWqualitativeؾWqualityFWW$bupIWإWدWWupdatesإWupgradeإWuplink WW*WTW،W؟WؠWضWWWW"W-WuploadingtWupperKW؇WؒWurbanhWWurbanoutdoor-indoorW ؤbc'This should be a normative requirement.d154g2269 2004/06/11إEDougFKnisely^Technical, Binding_20`8a4.5.3bACPE 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* أ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,7bcontentionؒWcontext؇WcontiguousWcontribution0WWWWWWWcontributions9Wcontrol=WAWMWmW؅W؎WؑWؘWاWتWػWWcontrolandmonitoringMVcontrolsconstraints؎WconversationalؕWcoreWcorrectionsؔWcorrectlyؕWcorrespondingsWؕWcostAWcould@WW WlooselyشWcoverage،WؠWزWWWcpeإWخWWcpesoftwareupgradepushanoperatorshouldhavetheabilitإVcriteria WWSWcryptographic=Wcurrent!W*WؗWcurrentlyإWWdata)W*W+W5W7W:W?WCW]WjWsW؋W،W؎WؔWؕWؗWؙWؚW؝W؟WؠWأWئWدWصWضWWWWWWWdatagramwWdateIWdealingeWdecidingإWdecoupledشWdefine@WPWW؉WؓWأWػWWWWWWc802.20systemsshouldworkeffectivelywithbroadcast/multiczV802.20'sحW802.20'sworkisawkwardحV96WW W95Wa W W WWWWWWWWWW#W4W?WDWKWOWSWTWUWXWZW[W]W^W`WaWdWeWfWgWiWjWrWsW{W}W؁W؄W؆W؊W،W؍WؖWؙW أ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.d153g2268 2004/06/11ؤEDougFKnisely^Technical, Binding_19`21a4.5bA1The system shallmust support both IPv4 and IPv6. 1@-^technical.W.WcsaysWWXW^WW&WscalabilityWscalableWscales-Wscaling-WWscenarioshWschemesWW&WXW^WW&Wscope=WتWsecondNWءWsection!W(W*W+W.W2W@WeWjWآWؽWWWWWWWW W WWWWsections*WبWWsectors{WsecurityxWؗW@cnon-bursty~Wnon-discriminatoryWnon-lineزWnon-relatime9Wnon-requirementءWnon-requirementsءWnon-testableآWnorؠWnormativerWsWؙWؚW؛WؤWnot W W WWWWWWWW(W4W:W<W>W?WFWOWSWUWVWXW[W]W^W`WdWeWhWjWkWnWrWsW}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ؽWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW!W#W$W&W)W+W<VnotdefineduntestableVnotsurehowthisisamac/phyrequirementssoftwareupgradeإVnottestable؉Vnottestablenotarequirement}VnoteغW@Q mbAj  335  33@  33A @ 33M  33W @ 33n  33w @ 33  33  33 @ 33  33$ @ 33%  33&  33'  33y @ 33  33jCPE 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 sy 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 software load has arrived sg2765 2004/06/11إcyNot sure how this is a MAC/PHY requirements. Software upgrades should be an upper layer issue. Suggest simpler wording.d155g2270 2004/06/11ئEMasaakiFYuzaGMember^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. d156g2211 2004/06/11 2004/05/28ةF Pittampalli^ Editorial_0b{Change from "802.20 ...." to: "System Requirements for IEEE Standard 802.20 for Mobile Broadband Wireless Access Systems"cIncorrect titled159g2324 2004/06/11تEEshwarF Pittampalli^Technical, Binding_1`3a1.1bAReplace 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.d160g2325 2004/06/11ثEEshwarF Pittampalli^ Editorial_1`13a1.2b5Delete lines 13-16 (Text beginning with 'How the...")c6Text begining on line with "How the..." is unncessary.d161g2326 2004/06/11جEEshwarF Pittampalli^Technical, Binding_1`20a1.3ةئ4-3اEVincentFPark^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.d157g2767 2004/06/11بEVincentFPark^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. d158g2768 2004/06/11ةEEshwarcl؄cwhat is a "partitioning model?"d122g2237 2004/06/11؅EDougFKnisely^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.d123g2238 2004/06/11؆EDougFKnisely^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).d124g2239 2004/06/11؇EDougFKnisely^ Editorial_11`7a4.1.1b bchanceإWchanegFWbcapacitysWؑWؖWػWcaption!W$W%Wcaptions!WcaseWcaused؎Wcell،WؑWؖWؠWWWcellsFW{WWW+WcellularW+Wcertain؎WغWcertification@WO`tbsupportoption2forperformanceundermobilityanddelayspRVsupportoption3asfaraslatencyrequirementsareconcerneQVsupported-WsWؔWأWsupportssW}WsustainedsWدWswitchإWsystem+W?W]WhWiWmWwWxWyWzW{W|W؇W،WؑWؒWؓWؔW؛WؠWؤWئWةWضWWWWWWWWWWWWWW,W-WsystemsWsWؗWةWتWدWWWWWW+WtغWtable$W%W)W+W6WdWWWWtaggingiWtakeKWtaking@W؇WtargetwWدWtargetedsWtargets]WؕWئWWtaxedKWtbdWtbrWtddDWKWؐWشWtechnicaljWtechniques:WWtechnology-WIWJW؊WM@ hkbAR  33  33"  33/  33R[;.cWSystem must work under the various environments of a Macro/Micro/pico cellular system. d289g2261 2004/06/11lular system. g2261 2004/06/11bps downlink and 500 Kbps uplink. cTSeparate Peak and Average data rates. Too much span between peak and average rates g2260 2004/06/11.EJimFRagsdale_18`12a4.2.3bPick option 3 cWSystem must work under the various environments of a Macro/Micro/pico cellular system. g2261 2004/06/11 2004/06/11ents of a Macro/Micro/pico cellular system. g2261 2004/06/11 2004/06/11bجbreplace with "basis"c Typo "bases"d162g2327 2004/06/11حEEshwarF Pittampalli^ Editorial_1`20a1.3b+replace "802.20's work" with "the standard"c"802.20's work" is awkwardd163g2328 2004/06/11خEEshwarF 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.d164g2329 2004/06/11دEEshwarF 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."b6ش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.d170g2335 2004/06/11صEEshwarF Pittampalli^Technical, Binding_12`17a4.1.4bdreplace it with "Data rates may gracefully degrade from pedestrian speeds to higher speed mobility."c*"As an example,...mobility." is ambiguous.d171g2336 2004/06/11ض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.d172g2337 2004/06/11طEEshwarF Pittampalli^Technical, Binding_13`7a4.1.5mpalli^Technical, Binding_7`12a2b/Please clarify what exactly is the requirement.at exactly is the requirement.g2776 2004/06/11 1.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  €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 6102GAd‚!‚"‚#‚$‚%‚&‚'‚(‚)‚*‚1‚2‚3‚4‚5 ‚6!‚7"‚8#‚9$‚:%‚A&‚B'‚C(‚D)‚E*‚F+‚G,‚H-‚I.‚J/‚Q0‚R1‚S2‚T3‚U4‚V5‚W6‚X7‚Y8‚Z9‚a:‚b;‚c<‚d=‚e>‚f?‚g@‚hA‚iB‚jC‚qD‚rE‚sF‚tG‚uH‚vI‚wJ‚xK‚yL‚zM‚N‚O‚P‚Q‚R‚S‚T‚U‚V‚W‚X‚Y‚Z‚[‚\‚]‚^‚_‚`‚a‚b‚d‚e‚f‚g‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚W_uwxyz{|رز+ !}~؀؃؄؅‚!"J؆,bclassicؔWclassificationؕWclearlyWcloselyشWcodedإWcodingؠWcoexistence@WcollectionWW\WbWjWاW W*Wcolumns؍WطWcombinesWcomma؁WcommentWcommercialؗWWcommitments؎WؓWcommonJWأWWcommunicatesmWcommunication@WcommunicationsAWcompatibleأWcomplementedؗWcomplexitysWcompliant@WsWاWcomplykWؕWcompromised?WcomputerKWxboa&mاWobjectWoccupied@WoctetؕWofWWWW!W%W(W*W+W,W-W:W<W>W?W@WAWCWFWIWJWKWNWOW\W]WbWdWfWiWmWsWuWwWxWyW{W|W؅W؇W،W؎WؒWؓWؔWؕWؗW؛W؜W؟WأWإWئWاWتWدWزWضWؾWWWWWWWWWWWWWWWWWWW W*W,W-WofflineFWofing؟WoldإWon-W9WAWDWjWrWtWwW؀W؏WؑWؒWؕW؝W؟WأWغWWWWWone%WAWJWPW]WiWmWإWئWonly؎WعWWopentWoperating@WAWتWoperationsWؕWoperationsCWoperatorWW\WbWؒWؔWإWاW W*WoperatorsأWoppositeFWoptimalAWcthesentencebeginningwiththisdocumentisnotclearindeتVthesentencethephysicallayerprovidesisvagueandnotusFVtheseparationofdownlinkversusuplinkspectralefficiency VVTVV"Vthesub-sectionheadingdoesnotreflecttheintegritypart>VthesystemisexpectedtoworkindensenotclearandalsohVthesystemshallnotnegativecommentVthesystemshallsupport95notclearVthetextofsection4.1.5isnotspecificenough(Vthetwopartsofthesentencestartingatline10mayappearVtheirOWdWthemOWthere1W;WPW]WdW؍WtherearehardlyanyapplicationsthatrequirebeareraccessPVtherefore WWUWeWiWthese2WOWdWsW{Wthey]WؠWthingآWthis WWWWWW=W@WSWZW[W]W`WaWeWjWnWqW|W،W؍WآWأWؤWإWتWغW+Bcthisdocumentdoesnotspecifydetailedrequirementswhateve@nthisrequirementspecifiesstringentspectralefficienciesw@through@to@*today@understood@unnecessarily@2version@ywesupportoption1removingthissectionitdoesnotseemr@Wwhich@within@Gd@‚hAÃ1@Pj1changetoreadieee802.20-basedsystemsshallsupportbro@ data@shown@طbReplace 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.d173g2338 2004/06/114-2ظEEshwarF Pittampalli^Technical, Binding_13`11a4.1.5bDelete Option 2cOption 2 is not desired.d174g2339 2004/06/11عEEshwarF Pittampalli^Technical, Binding_13`22a4.1.6bDelete "potentially only"c"potentially only" -- redundantd175g2340 2004/06/11غ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.d176g2341 2004/06/11ػEEshwarF Pittampalli^Technical, Binding_14`51yuzaئW bwithزWسWشWصWضWطWغWؼWWWWWWWWWWWWWWWWWWW WWWWW W*Wbreplaceitwithsupportnon-lineofsightoutdoorandindoorزVreplaceitwiththeaishallsupportcloselycoupled/looselyشVreplaceitwithwirelessVreplacemobileterminalmtuserdevicemobiledevicewirelesخVreplacerequirementwiththeairinterfaceshallsupporttheVV\VbV V*VreplaceshouldwithmayسVreplacethewordshouldwithmayVreplacethewordwillonline26withshallVػa4.1.6bDefine "control capacity"c!"control capacity" is not clear. d177g2342 2004/06/11ؼEEshwarF Pittampalli^Technical, Binding_14`13a4.1.7b;Replace it with "satisfy both intra and inter user QoS..."c "satisfy user QoS..." incompleted178g2343 2004/06/11ؽEEshwarF Pittampalli^Technical, Binding_14`22a4.1.7.1bNeed more explanation.c,..in Section 4.4.1 "[3,4,5,6]..." not clear.d179g2344 2004/06/11ؾEEshwarF Pittampalli^Technical, Binding_14`25a4.1.7.1b>Quantitative requirement is required (instead of qualitative).c0"To support....." the requirement has no teeth.d180g2345 2004/06/11ؿEEshwarF Pittampalli^Technical, Binding_14`37a4.1.7.1b6Include Expedited Forwarding traffic class descriptionc{Option 2 provides description for only Best Effort data leaving Expedited Forwarding and Assured Forwarding traffic classesd181g2346 2004/06/11EEshwar/06/11hpittampalliصضطظعغػؼؽؾؿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃragsdale+,-.springer؃كڃۃ܃݃ރ߃sutivongWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWteetomcikWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWwilson youssefmir!"#$%&'()*$breplace802.20'sworkwiththestandardحVreplaceitwithaverageuserdatainaloadedsystemshallbضVreplaceitwithcontiguousVreplaceitwithdataratesmaygracefullydegradefrompedesصVreplaceitwithenablerstosupportرVreplaceitwithphase1numberschangedto3.0mbpsfor1.25طVreplaceitwithreasonableandnon-discriminatoryrandVreplaceitwithsatisfybothintraandinteruserqosؼVb2alternatetextforthissection+V2insertnewsubsection4.2.1.1general@V2-1W2-3]WئW2.0+W2.5W20W2001ؕW23$W25,WW250CWدWW2597أW2598أW25ms؎W26W28AW3WW!W%W*W+W-W@WQWYW_WgWؕWأWWW'W.W3insertnewsubsection4.2.1.2radiotransmitter@V3-1W3-2!W"W3.0طW3.1W!W3.1.1KW3.5تW3289أW33HW34562WؕW35W360-W3gpp2W4%W@WCWؕWW4insertnewsubsection4.2.1.3radioreceiver@V4-1$W)W+WdW4-2%W4-3W4.1.1(W4.1.1.2>W4.1.5*W4.1.5.1*WWF 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.d182g2347 2004/06/11EEshwarF Pittampalli^Technical, Binding_15`19a4.1.7.1bDefine "moderate"c8"..moderate delay, moderate data loss rate,.." ambiguousd183g2348 2004/06/11EEshwarF Pittampalli^Technical, Binding_16`6a4.1.8b2Define what is "Interconnectivity at the PHY/MAC?"c."Interconnectivity at the PHY/MAC.." ambiguousd184g2349 2004/06/11EEshwarF 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.d185g2350 2004/06/11EEshwarF Pittampalli^Technical, Binding_17`10a4.1.11.5bWOW[W`WhWjWnW،WءWWdoesn't؆Wdon't؆WءWdos؜Wdownlink W WWWOWSWTWdWdriven؍WPcdecidejWdecreasedfWdefine]WsWwWئWdefinebroadcastandmulticastserviceswVdefinedWW;WBWYW]W_WeWW،WؒWؠWءWآWاWWWWW'WEEshwarF Pittampalli^Technical, Binding_18`1a4.2.3bJReplace 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 informationd191g2356 2004/06/11EEshwarF 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 missingd192g2357 2004/06/11EEshwarF Pittampalli^Technical, Binding_18`18a4.2.3bKReplace with "The system shall support both indoor and outdoor scenarios."c+"The system shall NOT..." Negative comment.d193g2358 2004/06/11EEshwarF Pittampalli^Technical, Binding_18`3a4.2.3b7Replace with "The system shall support at least 95%..."c-"The system shall support 95%....." not cleard194g2359 2004/06/114EEshwarF PittampalliVKconafairandnon-discriminatoryisnotconsistentwithansiVone]WئWWoneofthefactorsthatwoulddetermineif802.20couldbeuVonlyWW0WXW]W^WhWآWئWعWؿWWW&Wonlytheparandthe5-criteriadocumentsshouldbereferenc0Vopen-endedWoperate؝Woperation WWSWsWW!WoperationalآWoperatorsdWopinionWopposite،WoptimalWoptimallyWoptimizedWWXW^WW&Woption WWWW5W7W8W9WBWCWUWYW]W_WeWgWhWiWjWظWؿWWWWWWW#W'W^Technical, Binding_18`15a4.2.3bSame as comment 35cSame as comment 35d195g2360 2004/06/11EEshwarF 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?d196g2361 2004/06/11EEshwarF Pittampalli^Technical, Binding_18`25a4.2.6b(Specify what metrics are being measured.c3"The physical layer provides ...., etc." Not cleard197g2362 2004/06/11EEshwarF Pittampalli^Technical, Binding_18`33a4.3bReplace it with "wireless"c1"cellular" word conveys only partial information.d198g2363 2004/06/11EEshwarF Pittampalli^Technical, Binding_18`35a4.3b"Specify maximum channel bandwidth.ls is missingg2802 2004/06/11":cthetable4-1captionshouldbeplacedabovethetable$Vtheterminterconnectivityatthephy/macisnotclear:VthetermnetworkisinappropriatehereEVthetextinc802.20-04-44issomewhatdifferentinthissectVthetextofsection4.1.5isnotspecificenough(Vthetwopartsofthesentencestartingatline10mayappearVtheuseofdenseurbansuburbanandruralisconfusingbecauVthewordmayhasnospecialmeaninginarequirementsdocumeVthewordmusthasnomeaninginarequirementsdocumentweaVPVtherefore WWUWeWiWthese2WOWdWsW{WWWWWthey]WؠWWWthingآWthingsWthis WWWWWW=W@WSWZW[W]W`WaWeWjWnWqW|W،W؍WآWأWؤWإWتWغWWWWWWWWWWWWWWWce"readily extensible to wider channels..." -- this is an open-ended requirement for channel bandwidth.d199g2364 2004/06/11EEshwarF Pittampalli^Technical, Binding_19`4a4.4.1b?Specify what mechanisms are being referred to in this sentence.c#"802.20...mechanisms...)" not cleard200g2365 2004/06/11EEshwarF Pittampalli^Technical, Binding_19`9a4.4.1bMProvide the references to other IP network standards and IP mobile standards.c1"...other IP network standards...." not completed201g2366 2004/06/11EEshwarF Pittampalli^Technical, Binding_19`16a4.4.1bReplace with " The 802.20 standard shall specify all the parameters needed to address diffferent classes of service and various QoS parameters."c)"The classes of service..." Is not clear.d202g2367 2004/06/11EEshwarF Pittampalli^Technical, Binding_19`23a4.5.1bReplace it with "contiguous"c""continuous" is not the right wordd203zbspecifyassociationofenvironmentswiththeappropriatechaVspecifymaximumchannelbandwidthVspecifywhatmechanismsarebeingreferredtointhissentenVspecifywhatmetricsarebeingmeasuredVspectral WW(W)W+WOWSWdWsW؇W؉WؠWدWWW!WspectrumIW؇WspeedCWW؋WصWWcnotarequirementimmediatelyobviousandaddsnovalue؊VnotasentenceؖVnotanexampleasadvertisednotrelevanttotherequirement؋Vnotclearwhatismeantbypartialsolutionperhapsrephrasi<VnotdefineduntestableVnotsurehowthisisamac/phyrequirementssoftwareupgradeإVnottestable؉Vnottestablenotarequirement}VnoteغWW+cnow@offered@Vonafairandnon-discriminatoryisnotconsistentwithansi@option1page18line4thetbrneedstobedefinedorelse@Koptions@page@parameters@partitioning@_potentiallyonlyredundant@priority@Squite@Frates@rather@referenced@require@requirementswithregardto802.1qaredetailedinthe802p@says@see@separation@shouldimpliesarequiredfeaturewhichisnottrue@4situation@Cspecifically@\speed@stringent@systems@Otable-like@Jterminal@/textshouldbeanormativerequirementalsostrengthentoin@the@6T4theconceptofbandwidthmustbeclarifiedgiventhatweare@e4-1captionshouldbeplacedabovethetable@thewordsasanexampleisnotveryappropriatehere@"thiscouldbeconsolidatedwithothermaterialnotethatlin@3g2368 2004/06/11EEshwarF Pittampalli^Technical, Binding_19`26b(Define "soft handoff" and "hard handoff"c$"soft or hard handoffs.." not clear d204g2369 2004/06/11Eshigeru 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 cEEshwarrovide the references to other IP network standards and IP mobile standards.c1"...other IP network standards...." not completed43g2366 2004/06/11EEshwarg2812:4ccertainly WWSWW!Wchance]Wchange*W2W؀WWWchangearetoshallbeandinsertapprovedbeforeparVchangefuturetensetopresenttense؀VchangedأWchanges+Wchannel W WWWHWOWSWVWfWWWWWWW!W$Wchannels]WئWWcharacter#WcharacterizeOWchoice؞WWciteWclaimssWclarification;WDWWWWWWWclarified WWVW WW$WmentsؗVclarifyrequirementswrtlinklayervsend-to-endqosandؒVclarifytrafficclassesؔVclarifywording؎Vclarify/changeIWclarifying WWSWclarity<WtWWWclasssWذWclasses/W8WؔWؕWؿWWWWclear:W<WتWدWذWرWػWؽWWWWWWWWWclearly~WcloseWclosestW LcA9It 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.9d205g2340jASection 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. kk -> Peak system data rates and average usB!er data rates -Downlink & Uplink c Uplink cg2815 2004/06/11%&PbRDefine 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. 2004/06/11QEHariFGantiGMember^Technical, Binding_Technical, Binding`15a4.1.7b>Support option 3 as far as latency requirements are concerned.d73 2004/06/11REHariFGantiGMember^Technical, Binding_Technical, Binding`18a4.2.3bCSupport Option 2 for "Performance under Mobility and Delay Spread."d74 2004/06/11SEMarcFGoldburg^Technical, Binding_11`5a4.1.1Jv_‚1Z\jإاب  (*‚2`ab‚3 ‚40`v؁ "$JؚؐɃ,0-؆؝ئʃ@تP%5LMNk}؛أ҃ۃ` 0STdqr؊،ؑضػ!"-Zms؇؍ط_ؖ؜إخد 6`ؒؓӃ‚!#رÂ"شظ‚#n؀ذ‚$ Pثؼ‚%uwxyz{|؃т&.;Q\jot̓ك ‚'@CX^g؄؈ԃ‚('a؋؞صƃ‚)!+R؅˃΃‚**/Kؔؗز‚1()fp؎؟جحڃ‚21؉ؕءؤس݃‚3 2UVWeعؽ׃߃PccontradictingWWcontradictory،WcontributionJWWWWWcontributions0Wcontrol=WAWؑWػWcontrolcapacityisnotclearػVcontstrtuionWconvergenceWW[W`WW)Wconvey،WconveysWconvincingdWcooperativeغWcopied!WcorrectsWcorresponding9WWcould WWSWfWWWWW WW!WcouplingWcovered~Wcovergae;WcpeWcpeseemsliketheincorrecttermhereitisusuallyusedinVcreateWWXW^WW&WcreatesؑWcriteriaبWcurrentWW+WCWXW]W^WWWW&Wsistenciesneedtoharmon+VcurrentlyWcurrentlyknownattackscurrentattackswereunknowntopastVcustomer'sWcyWdWdata WW/W5W7WUW]WjW،WئWضWؿWWWWWWWWWFSpringer^ Editorial_5`20a1.3b3bases becomes "basis" since "table" is the object. cNgrammical problem, "that the following table is presented as the bases ..... d208g2818 2004/06/11EWarrenFSpringer^ Editorial_15`4a4.1.8b?multi combines with other words is usually attached to the nounc?per usual style, "Multi Antenna" should become "multianntena" d209g2819 2004/06/11EWarrenFSpringer^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"d210g2820 2004/06/11EWarrenFSpringer^ Editorial_16`21a4.1.11 tems...  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/06/114-3EWarrenFSpringer^ 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 placed206g2816 2004/06/11EWarrenFSpringer^ Editorial_5`15a1.2b,potocol in layers 1 and 2 needs the plural cprotocol in layer 1 and 2d207g2817 2004/06/11EWarren6todd vincentابwarren؃كڃۃ܃݃ރ߃chauvin chengal !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNgantiOPQRgoldburgSTUVWXYZ[\kimuraklererdefghijkniselyklmnopqrstuvwxyz{|}~؀؁؃؄؅؆؇؈؉؊؋،؍؎؏ؘؙؚؐؑؒؓؔؕؖؗ؛؜؝؞؟ؠءآأؤإmurakami]^_`abnaguibWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W W WشjkandWareWaverageWbeWbetterWbyWconfusingWdataWdefinedWeachWforWhopeWifWimportantWinsteadWisWitWitisbettertospecifythesystempeakdataratesinsteadoVlargeWlittleWnecessaryWofWpeakWratesWreasonWshouldWspecifyWsystemWtheWthingsWtoWuserWwhyWmaccepted-modified jshownWspectrumWsupportWWsystemWWsystemsWtableWtargetsWthatWtheWtheseWthisWtoWtrafficWtrueWuplinkWuseWuserWusingWvaluesW jdataWdownlinkWefficientWexcessWforWgreaterWieeeWinWindependentWloadedWloadingWmakeWmechanismsWmodificationWmulticastWofWWoptionWorWpeakWrateWratesWreadWresourcesWsectionWsectionandoption1modificationVservicesWshallWWshouldW^binding W W W W WWWWWWWWWWWWWWWWW-W4W5W7W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWdWeWfWgWhWjWsWxWyWzW{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ؾWAPdÃ1Ã1Ã1Ã2Ã2 Ã20Ã2@Ã2PÃ2`Ã2pÃ2Ã2Ã2Ã3Ã3 Ã30Ã3@Ã3PÃ3`Ã3pÃ3Ã3Ã3Ã4Ã4 Ã40Ã4@Ã4PÃ4`Ã4pÃ4Ã4Ã4Ã5Ã5 Ã50Ã5@Ã5PÃ5`Ã5pÃ5Ã5Ã5Ã6Ã6 Ã60 Ã6@ Ã6P Ã6` Ã6p Ã6Ã6Ã6Ã7Ã7 Ã70Ã7@Ã7PÃ7`Ã7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@Ã8PÃ8` Ã8p!Ã8"Ã8#Ã8$Ã9%Ã9 &Ã90'Ã9@(Ã9P)Ã9`*Ã9p+Ã9,Ã9-Ã9.$bfshould read made for authentication of both base station and mobile terminal for privacy and for data 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 d211g2821 2004/06/11EWarrenFSpringer^ 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 d212g2822 2004/06/11EWarrenFSpringer^ Editorial_17`22a4.2.2bmline should read for graceful reduction in or increase of user data rates on the downlink and uplink, as a r usual style, "Multi Antenna" should become "multianntena" g2819 2004/06/11EWarrenFSpringer^Editoria_16`20a4.1.11cdescription]WؿWdesignIWKWgW؜W WdesignedGWhWsWWWdesigningWWXW^WW&WdesignsdWdesire{WdesiredآWظWdetailAWWbWnWبWdetermineWdevelopingdWdevicesdWdictateWdifferent WWSWWWdifferntWdiffservWWXW^WWdiffservmayworkwithinterfacingto3gppnetworksbuttheVdiscardBWdiscusses.WdiscussionjWdisruptWdistinguish9WؓWdistorted6Wdistortedtable-likecolumnsinlines9through256VdiversityWdivided،WdlWdodWWdocumentWW4WXW^WnWqWتWWWWdocuments0WبWdoesWW>WOW[W`WhWjWnW،WءWWdoesn't؆WWdon't؆WءWdos؜WdownlineWdownlink W WWWOWSWTWdWdriven؍WcanntennaWansiWantennaWanyWWPW[W`W،W؝WبWWWW WW)WanythingWanywhereWWappearWappearant]WئWappearsWapplicable WWSWW!WapplicationsWWPWXW^WWWW&WapproachWW[W`W؍WWW)WappropriateWWXW^WWWW&WapprovedWWWWarbitraryWWXW^WW&Warchitecture]WؒWئWare W WWWWWWWWWPWSWVWXW[W\W]W^W`WbWdWfWgWhWiWnWsW{W؍WؠWآWبWغWWWWWW W WWWWWW W!W$W&W)W*WargumentsdWaroundW.9WcaggregationjWaggressive؍WagnosticWW[W`WW)WcdenseWWdependWdepending WWSWWWW!Wdepends،WdeploydWdeployedWdeploymentdWdeploymentsWWXW^WW&WdescribedؠWآWWhWsWdesigningWWXW^WdesignsdWdesire{WdesiredآWظWdetailAWdetailedWW\WbWnWبWdevelopingdWdevicesdWdifferent WWSWdifferntWdiffservWWXW^WdiscardBWdiscusses.WdiscussionjWdisruptWdistinguish9WؓWdistorted6Wdistortedtable-likecolumnsinlines9through256VdiversityWdivided،WdodWdocumentWW4WXW^WnWqWتWWdocuments0WبWdoesWW>WOW[W`WhWjWnW،WءWWdoesn't؆Wdon't؆WءWdos؜WdownlineWdownlink W WWWOWSWTWdWdriven؍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.d217g2212 2004/06/11 2004/06/08EAnnaFTeeGMember^ 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. d218g2213 2004/06/11 2004/06/08EAnnaFTeeGMember^ Editorial_12`16a4.1.4FTeeGMember^ Editorial_8`14a2.2g2830 2004/06/11cthe 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/06/11EWarrenFSpringer^ 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 d214g2824 2004/06/11EWarrenFSpringer^ 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.d215g2825 2004/06/11ied.)bbecomesWbeforeHWJWإWbeginningثWbehaviorsأWbeingWWbelowتWbest+WJWؕWؗWأWWbest-in-classsWbetween WWTWmWؒWؓWW WW"Wbit/WؓWbits/sec/hzW!Wbits/sec/hz/sector WWSWblock%W؇Wblocking@WbootpإWbootstrapإWboth?WAWCWDWKWzWؗWؠWؤWؼWWWWWWbottom!WbpsؔWbps/sector؇WbroadbandةWتWWW+WbroadcastFWwWyW{WWWbroadcastservicetheabilitytotransmitapacketofinformwVbroadcast/multicastzW|WbrowingؓWbrowsingtWbsCWWbursty~Wbut@WFWtW؉W؝WWWby)W+W?WwW؇W؎WؒWؓWؔWؗW؝WؠWأWدWWWc/iFWc802.20-04-44WWc802.20-04.44WWcapableإW:EAnnaFTeeGMember^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.Id216g2211 2004/06/11 2004/06/08EAnnaFTeeGMember^ Editorial_8`14a2.2al_18`35a4.3ted to work in dense urban, suburban and rural outdoor-indoor g2824 2004/06/11EWarren^ Editorial_18`35a4.3crequirementswithregardto802.1qaredetailedinthe802pبVrequirenments@WrequiresWWXW^WW&Wrequiring WWVWW$Wrequrement]WrespectWW\WbW W*WrespectivelyOWdWWrest~Wrestored;WrestrictWWXW^WW&WrestrictivePWrestructure*Wresult WWUWW#WresultsWretainWrevised؍WrewordWrewrittenWrfWW@WXW^WW&WrfcsWrightWrlWWrt9WrttWWXW^WW&WruralWsaidWsame'WWsameascomment35VsatisfiediWsatisfyؼWsatisfyuserqosincompleteؼVsayآWWWkNcaseWassociationWassuredWassuredؿWat WWWWWW:W;WOWSWZW[W`WaWdWrWsWuW،W؍WWWWWWWWWW!W(W)Watsomeearlierversionofthesrdtherewasanagreedupon;VattacksWWattending Wattribute/WauthenticationWauthorizationxWauthorized{WavailablefWWWaverage WWUW،WضWWW#W,W-WaverageuseddatagreaterisnotinexcessofexistingtechnضVaverageuserdatarateisnotdefinedanddependsonthenum،VavoidبWawk؇WawkwardmW؟WحWawkwardsentencemVawkwardwording؟VbWb/s/hz/cellOWb/s/hz/sectorOWdWbackbonezWb"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."c