Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0)@0inding@cthenormativereferencesectionisblank@@00allowedtheconcatenationoftheseparat@@0coincide@entity@inserttheworddownlinkbeforemodeaandotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@?>?>?>?WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWֹVֺVֻVּVֽV־VֿVVp 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 BC9DE Pro 3.0 - 4.1F!"HPro 5.0 A ?G USENGLSH.MPR?GUSER.UPR20SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDec[:I3 "Z22-& 5/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(LISTqLISTAqAccepted Accepted-Modified Accepted-Clarified Accepted-Duplicate Rejected Rejected-Duplicate Superceded WithdrawnqVDEFA((A!Vt VDEF(LISTLISTDT-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€€66leiOwang' *  wang * leiP wang wang ' leiQ wang VYwang VleiRwangwang YleiSwang wang leiTwang@nh&`wanghleiUwang1.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 K 9@AOKA/A0@@A-A.@A,A-Cancel@A*A+@@A* ;X( `Before importing, Find the records eligible for proposals by this Clause Editor. Only these records will be affected by the import. ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoQ:ASort by RecommenderE'` iDT_DT`DTDTDTQÃY0?ÃY@@ÃYPAÃY`BÃYpCÃYDÃYEÃYFÃZGÃZ HÃZ0IÃZ@JÃZPKÃZ`LÃZpMÃZNÃZOÃZPÃaQÃa RÃa0SÃa@TÃaPUÃa`ZBUUX  w  $,.YesNo/,  , : AM PMf  HelveticaGenevaVerdanaTimesMonacoTimes New RomanArialCourierSymbol Courier New@ A PICT,alisNAMEMSPCFPTHA9Macintosh HD:Desktop Folder:Ballot#2:802.16.2 Ballot Data9MSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataalisC-`@@XA Comment List@@*AAbout Commentary@@PACreate Comment@@fACreate and Submit Ballot@@AGlobal Field Setup@@ AEditor's Layout@@AComment List for Printing@@ AComment List for Projection@@ACommentary Version@@@AReply Comment Layout@@ ASubmit Reply Comments   A Comment ListB J  vor/ 11 against wRejected{l) none needed 2001/10/24»ETG3/4 MAC group^Technical, Bindinga6.2.XbFAdd new ARQ text found in document 80216abc_01/75 to the WG document. d339g2541wAccepted{k) done 2001/10/24 2001/09/11¼E TG3/4 MAC^Technical, Bindinga6.2.xb'Add a standalone NACK feedback message.d340g2542vneed accepted textwDeferred{l) none needed 2001/10/24 2001/09/13½E TG3/4 MAC^Technical, Bindinga6.2.xb Add RNR feedback message for ARQd341g2543vneed accepted text 2001/09/13D$aGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #{ Document #Report # B A € € € €€ €   G!MKe!MKG*fQjugD€QASDocument under Review€XAYLetter Balllot Number€^A_VoteaGlobal Field Setpb // etpb // etpb // etpb // tpb // b // b // d Setpb // Setpb // tpb // Setpb // b // ld Setpb // d(2) Save Data to Filee(3) Email Data Fileail Data File54 RB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMnD a w n w  $,.YesNo/,  , : AM PMo  w p w  $,.YesNo/,  , : AM PMq  w r w  $,.YesNo/,  , : AM PMs  w t w  $,.YesNo/,  , : AM PMu  w z w  $,.YesNo/,  , : AM PM{  w  D^"M1,,./: AM PMYyTtNnFfNALL OFMPRP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , AXLS Sheet1X5CMY m]oApFfWyHCB-wang., .lei]} A1FPTH=RPTH NAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9NFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9OFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A10FPTHXRPTHNAMEMSPCMSPCA2NAMEANumberLastFirst.USRRPTHANumberLastFirst.USRA19uFPTH^RPTHNAMEMSPCMSPCA2NAMEANumber_Lastname_FirstnameRPTHANumber_Lastname_Firstname ot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisVDEF(LISTLISTVDEF(LISTLIST(:K?@MRS Y!^"CAStartup scriptEQADelete Empty RecordsE@ @b*QA Show VotesE@@H-Already voted; submitting additional commentsQASort by Page/LineE'` _DT`DTDTDTQASort by Comment OriginatorE'` DTDT_DT`DTQADelete All RecordsE@ @b*QADelete Abstain CommentsE@ @HAbstain for other reasonsQAShow Editor's ProblemsE @'`@n* _DT`DTDTDTQASort by Comment #E '` dDTQ8 €Bied in recommending rejection on grounds of incompleteness or lack of a specific change request. (3) When you are finished entering replies, look under Scripts and choose "Find Marked Records". This will find the records for which you checked the "Marked" box. (4) Put your name in the "Recommendation by" field of each reply {for a quick method, see Appendix below.} (5) Under Scripts, choose "Export Clause Editor's Proposals". Choose the file type "FileMaker Pro Runtime Files". Enter a Cfile name of the form "BallotNumber_LastName_Firstname.USR", where "Name" is your name. (6) Email the exported file as an attachment to: --------------- Appendix: Using "Replace" in Commentary You can replace everything in a particular field over a batch of records. For example, clause editors might not want to type their name in the the "Recommendation by" field each time. Here is a solution to the problem illustrating the use of "Replace": *Finish entering your data. *Find the bacAEditor's LayoutB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMYesNo/,  , : AM PM Dp=u Av 2 72w27+-f3%:EAFAGA' Submitted by:€QASDocument under Review:UFirst (Given) NameVLast (Family) NameWBallot Group Membership Status:€XAY#Letter Ballot Number or Ballot Code€ZA[ email address€\A] telephone€^A_Vote:`(1) Create Comments€aAHCreate and Submit Working Group Ballot or IEEE Balloting Center CommentsH@AR  33& * Rg2*t {EQFAImport CommentsENALL OTABS# ` ABCDEFGdH^I_J`KaLbMcNOPQRgSiTjUkVmWnXpYvZw[x\y]{^_`abcde f g hijklmnoQGA Email fileE)?@ @A owner-stds-802-16@majordomo.ieee.org The comment file name should include the Letter Ballot Number and  ABCDEFGHIJK^L_M`NaObPcQ TUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxփքօֆևֈ։֊֋֌֍֎֏֐֑֖֒֓֔֕  "#$%&'()*+,-./0123456789:@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_^_`abcd€€€€€'f€aA Create and Submit Reply Comments @A*  33*€APLEASE FOLLOW THESE INSTRUCTIONS EXACTLY OR EXPECT TO HAVE YOUR INPUT IGNORED. (1) Read the comments. You will probably find this easiest if you use the "Comment List" layout. You can choose it from the upper left corner of this window, or you can use this push button: (2) When you want to respond to a comment, check the "Marked" box at the top of that record. Then fill out the following fields: Recommendation: Proposed Resolution: Reason for Recommendation: You are fully justifing the buttons:€gng the buttons:€gng the buttons:€gg the buttons:€gicking the buttons:€gicking the buttons:€gowing steps by clicking the buttons:€ging the buttons:€gg the buttons:€ging the buttons:€ge buttons:€gbmit Ballot Filef9Proceed with the following steps by clicking the buttons:€gO+ A#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# cBl#[  bl[##KK##;;# Bmv#+  @iv+# >j# Dkv# 8w5 €\]Page€^A_Line€`A aSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A &'()+ €A €A €A€ARecommendation@@ByProposed ResolutionReasonSee reply details€A Fig/Table# BNA^  !"#$%*,-./0123^^_`u EDE^ "Technical, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, BindingG OKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !""Technical, Binding" comments are permitted only with the vote "Disapprove". You may submit comments of type "Technical, Non-binding". Please correct and try again.H) W()=0 W ABCDEFGHIJK^L_M`NaObPcQlEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf7# w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM     w  $,.YesNo/,  , : AM PMw w  $,.YesNo/,  , : AM PMf"$  w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PMf w $,.YesNo/,  , : AM PMf3IC dd5BDe5Bf#= q w $,.YesNo/,  , : AM PM     w $,.YesNo/,  , : AM PM          w  3  $,.YesNo/,  , : AM PM   {cTZbo|h[++ \_l)]l+ ^`l$)g_.?nAEditor's QuestionB GpA Editor's NoteB GvAResolution of GroupB GH vwADecision of GroupB GxAReason for Group DecisionB GyA Group's NotesB G{AEditor's ActionsB G€AGroup's Action ItemsB G€AEditor's Action ItemsB G€AVoterFirstNameB G€A VoterLastNameB G€A VoterEmailB G€A VoterPhoneB G€A VoterStatusG€A VoterStatus3m  ^ 3 $,.YesNo/,  , : AM PM_   `3 a d3 e3 f  3 g  3 t  3 u   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PM#39 XX+ASubmit Reply CommentsB  a   w   w $,.YesNo/,  , : AM PMf w w Aa#8 F mM5ft GM5ftM5ftGOC`E 7OC`EOC`E7 W   W   W    ÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷{xBKA Enter commentEQMAImport Global DataENALL # @ A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcdefghijklmnopqQNAExport CommentsE:NALL OFMPR$@` ABCDEFGdH^I_J`KaLbMcNQkUmVnWpXvYwZx[y\{]^_`abcdefgh`DTDTDT A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcde0;Absupport@Bcissues@vthrough@Usthecorenetworkdrivestheqosallowedre@U}non-interoperable@Ypath@required@Psense@which@c802.16@Qattempts@comment@for@`from@{i@make@ofdm/ofdma@selected@the@thecompliancewith802.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 jv   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   h stanwood# >S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM(s%jAResolution ProposedB GkAReason ProposedB GmARecommendationB Gnndation 1B Gn1O RR 3  $,.YesNo/,  , : AM PMU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW w $,.YesNo/,  , : AM PMX w $,.YesNo/,  , : AM PM)v@B@2@I@I@L@!@9P;;P;;@y„-@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 PMBqS-X bWmkwj,AvCgE@!Sl€`zrAPFQKRPSUTZUBN@VhA~@M@LZ<>C @@@FIH@JQ3^&vmBD€QdnaD@Xbm{ACE@e@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€ (TELarry FAlder^Technical, Binding_8`12a2.2bReplace "shall" with "should".cate data rate. The reason why to specify the spectral efficiency is enough. g2212 2004/05/07Q^Technical, Binding_19a4.2.3b Adopt Option3c#MBWA shall work indoor and outdoor.g2213 2004/05/07R^Technical, Binding_21a4.5.3bDelete sectionding_21a4.5.3bDelete sectiong"PQRa; @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=ABEalder@Igoldburg@Rsutivong@lyoussefmir@^^binding@technical@technicalbinding@_@E`p@Faa4.1.1@Pb@3֕C802.20@achieved@adoptthejointcontributiontextforthissectionandmodif@[assigned@between@changetoreadfrequencydivisionduplexingfddhalfduplex@Gclarify@jconsolidate@deletetherequirementormakemorequantitativethanitis@zdownlink@general@ip@mloss@cmodify2ndsentenceinthesectionastheresolutionofqos@needed@option@performance@ remove@removeoption1@+replacerequirementwithamodificationofoption3asfollo@Aselect@Nsimultaneously@statistics@t@support@targets@the@thecurrenttexthasthreeoptions@,through@under@7up@urban@:well@within@U2@ BD VOTEREMAILpDs`jA.nA%€B?€AP€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 sBln# #  al# cl#  bl # Bmv#  @iv# sj{# Dkv#x 8wx#,Cjv#h 0xh#  2y#X 2X# 6{#H InH# qp# 8 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# #!  !#H dH#y #y# ## ## #% ^%#F  _lF#n  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€           ;51:/:14112 ;3 2 3  3  ;63 428$7"7 8&6559,6679)9+-*,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 GL2340iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. ,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl1#  #!  al!# bl# 8w#,v#  2y#y 2y# 6{#i Ini# qC>p# Y 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? a€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 GH Disapprove with binding commentsQ802.20 SRD V12 MarkKlererklerer@flarion.com 908-997-2069m 908-997-206999llot@wirelessman.orgllot@wirelessman.orge.orgggmAComment List for PrintingB   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    AS T3C|U#3}C<V#3ACWDGW#X^H_UYGpW \_lHUn]GW ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$Tgvh C iTkTlGTPmn{Tn{ng{Po pw~Tqpn{_PrP{T|DnP}T~5ETy(5P#3"$1"2$L63C#0z@@ B s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM |e 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#8  8#  # ## ## ## # d#q ^q#  _l#1  `  @BBA* *^_` a b dnpvw y{€€€€€€           /6(5$5"///6& 1 / 0 0  6)0 1 325 23344In # 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, S // €TA€UA€VA€WA€XA YType€\A ] Starting Page€^A _ Starting Line€`AaSection€bAcSuggested Remedy€dA €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 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 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 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 DataITcACUcBV@ WcAXcACYcAZcAC[cB]cAC^cB`cAacACbcAccACdcBfcACgcBicAjcACkcAlcBmcAnbojAp@cACqcBscAtcAC ucAvcACwcB փcAC քcB(ֆcAևcACֈcA։b֊@cB"֋cA'֌b)֍cB/֎cA2֏c1֐cB5֑cB6D8֒cB9֓cB;֔cA=֕b>@cbAjA@@@jA@bvAgx@cA0@V}H^bBDFn 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  33f8 TcAThe current text reads, "The AI shall support broadcast and multicast services." Most cellular systems today support the ability to broadcast transmissions across the entire user base in a cell or sector. The spirit of this requirement should be to support the efficient transmission of broadcast services wherein a single RF transmission from the basestation is received and shared across multiple receivers in the user base. However such capability must be traded off against the complexityB of efficiently implementing this capability in a network setting. For example, this requirement complicates the use of antenna array systems that boost spectral efficiency through the use multiple of antennas that directively transmit towards specific users in the user base. Since it is not clear how to address such issues without further analysis, and since from a services perspective broadcast services are secondary to the ability to provide users with dedicated streams, this requiremenAAzHHddE(HH(d'`zA'dUyjvwyentioned in many places in the document. We recommend consolidation of these so that it is easier to interpret and comply with QoS provisions in the AI. and drive the QoS, consistent with customer subscription and provisioning parameters.am cipher mode) or a block cipher (such as AES in block mode). Neither the use of AES nor RC4 shall be mandated." i@Az  33    33    336  zlThere has been a request from one member for additional time to put in additional comments for this section.3 ABCDEFG^H_I`JaKbLcMdNgOiPjQkRmSnTpUvVwWxXyY{Z[\]^_`a b c defghijklmnomno dDT ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoklmnoKEMarkFKlererd150g2319 2004/05/11LEMarkFKlerer^Technical, Binding_12`1a4.1.1biMake t Table 4-1 consistent with the PAR and specify a downlink spectral efficiency of 1 b/s/Hz/sector .cnlink spectral efficiency of 1 b/s/Hz/sector .cemented shall use IETF protocols. Some of the possible interfaces are illustrated below.[d148g2317 2004/05/07JFmigaldid149g2318 2004/05/07KEMarkFKlererd150g2319 2004/05/07LEMarkFKlerer^Technical, Binding_12`1a4.1.1biMake t Table 4-1 consistent with the PAR and specify a downlink spectral efficiency of 1 b/s/Hz/sector .c TcCt should be softened. d1 2004/05/11UELarry FAlder^Technical, Binding_11`10a4.1.1bSpecify 2 bits/sec/Hz as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved.cAThis requirement specifies stringent spectral efficiencies without explicitly clarifying the conditions under which it should be achieved. For example, because cell size is not constrained by the requirements, the spectral efficiencies could be achieved with very small cells. Or, for example, operation at 120km/hr is very different depending on the environment - certainly we are not interested in operation at 120km/hr in an urban setting, yet the requirement could be interpreted that it i the user base. Since it is not clear how to address such issues without further analysis, and since from a services perspective broadcast services are secondary to the ability to provide users with dedicated streams, this requiremen?7caiTWXW]WaWfWjWpWtWփWևW֍W֑WWWWWIWairYWbWuWֈW֒WWWWWWWW WWWWW[W]WallUW^WgWqWքW֎WWWPWUW_Walloptionsareoverlydetailedwithrespecttospecificsta_VallowUWVWXW^W_WaWgWhWjWqWrWtWքWօWևW֎W֏W֑WUWVW]WallowedWallowing]WallowsWalmostWalreadyWalsoWalternativeWamendIWamendthedefinitionofinterfaceschaptertoincluderefereIVanUW[W^WdWgWmWqWwWքW֋W֎W֔WWWWWWWWWWUWWgWlWqWvWքW֊W֎W֓WapplicationsYWbWkWuWֈW֒WappropriateYWbWuWֈW֒WarbitraryYWbWuWֈW֒WWtcefficiencyTWUWVWWW]W^W_W`WfWgWhWiWpWqWrWsWփWքWօWֆW֍W֎W֏W֐WWWAWEWFWGWLWTWUWVWefficientTW]WfWpWփW֍WWTWefficientlyTW]WfWpWփW֍WTWegYWbWkWuWֈW֒W[W]WeitherWOWRWelsewhere Wend-to-endWenoughAWensure[WdWmWwW֋W֔WensuringYWbWuWֈW֒W[WentireTW]WfWpWփW֍WTWentitiesIWenvironmentUW^WgWqWքW֎WEWPWUWenvironmentsZWcWlWvW֊W֓WequipmentWWW WWWWerrorYW[WbWdWmWuWwWֈW֋W֒W֔W[WetcYWbWkWuWֈW֒WWW[WevidenceLWexactSWlsupportbroadcastandmuTVthisTWUWWLcthroughTW]WfWpWփW֍WTWtiaWtightOWtimeOWtimeframeLWtimesFWtoTWUWVWXWYWZW[W\W]W^W_WaWbWcWdWeWfWgWhWjWkWlWmWnWpWqWrWtWuWvWwWxWփWքWօWևWֈW֊W֋W֌W֍W֎W֏W֑W֒W֓W֔W֕WWWWWWWWWWW W W WWWWWWWWWWAWDWEWGWHWIWLWNWOWSWTWUWVWXW[W]W_WtospecifylittlehopelargepeakdatarateisnomeaningDVWtransmitTW]WfWpWփW֍WtransportYWbWuWֈW֒WtrueXWaWjWtWևW֑WturnYWbWuWֈW֒WtwoXWaWjWtWևW֑WtypeWudpYWbWuWֈW֒WulWW`WiWsWֆW֐WWccexampleTWUWWW]W^W`WfWgWiWpWqWsWփWքWֆW֍W֎W֐WWTWUWexcessXWaWjWtWևW֑WexisitingIWexisting[WdWmWwW֋W֔WWexpectedZWcWlWvW֊W֓WexplicitlyUW^WgWqWքW֎WUWextensiveSWfastWfavorWfddWfeature[WdWmWwW֋W֔WWCW^WfigureWfiguresWfirstYWbWkWuWֈW֒W[WfixedkWflexibleYWbWkWuWֈW֒W[WTWUWWWXWYWZW[W]W^W`WaWbWcWdWfWgWiWjWlWmWpWqWsWtWuWvWwWփWքWֆWևWֈW֊W֋W֍W֎W֐W֑W֒W֓W֔WWWWWWWDWEWLWOWQWTWUWform-factorLWformalWforward-lookingWfragmentWWwcprovideTW]WfWpWփW֍WWLWTWproviders WprovidesWprovisioningWWprovisionsWpurposeXWaWtWևW֑WGWXWpurposeofieee802.20iscreatethehighefficiencysystemtGVpush[WdWmWwW֋W֔Wputs Wq]WqosYW[WbWdWkWmWuWwWֈW֋W֒W֔WWWWW[W^WqosismentionedinmanyplacesinthedocumentwerecommendVquotedWWranWrangesWrarelyXWaWjWtWևW֑WXWrateWWXWYW`WaWbWiWjWsWtWuWֆWևWֈW֐W֑W֒WAWDWFWGWXW[WratesWWXWYW`WaWbWiWjWsWtWuWֆWևWֈW֐W֑W֒WWXW[WratherWWcWlWschemesYWbWkWsecondaryTW]WfWpWsectionXW\WaWeWjWnWW RWcACurrent Text: OPTION 1: [ The aggregate data rate for downlink and uplink shall be consistent with the spectral efficiency. Example Aggregate Data Rates are shown in table 4-2) Parameter Aggregate Data Rates 1.25 MHz. @ 3km/hr 1.25 MHz . @ 120km/hr 5 MHz.@ 3km/hr 5 MHz. @ 120 km/hr DL UL DL UL DL UL DL UL Aggregate Date Rates (Mbps/sector) 2.50 1.88 1.25 0.94 10 5 5 2.5 Table 4 2 Aggregate Data Rates ] OPTION 2: [The aggregate data rate for downlink and uplink shall be consistenBt with the spectral efficiency.] Comment: The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Option 2 is clear and specific and does not assume specific channel bandwidths.d4 2004/05/11XELarry FAlder^Technical, Binding_14`1a4.1.5.1bRemove Option 1cdata rate for downlink and uplink shall be consisten XcACurrent Text: Editors Note: There are two versions of text for this section to consider at the next WG meeting OPTION 1: [ The AI shall support peak per-user 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. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design and operational choices. Average user data rates in a loadedB system shall be in excess of 512Kbps downlink and 128Kbps uplink. This shall be true for 90% of the cell coverage or greater. Table 4 3 ] OPTION 2: [The AI shall support peak per-user data rates in excess of 1 Mbps on the downlink and in excess of 300 kbps on the uplink. These peak data rate targets are independent of channel conditions, traffic loading, and system architecture. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design ևcACurrent Text: Editors Note: There are two versions of text for this section to consider at the next WG meeting OPTION 1: [ The AI shall support peak per-user 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. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design and operational choices. Average user data rates in a loadedB system shall be in excess of 512Kbps downlink and 128Kbps uplink. This shall be true for 90% of the cell coverage or greater. Table 4 3 ] OPTION 2: [The AI shall support peak per-user data rates in excess of 1 Mbps on the downlink and in excess of 300 kbps on the uplink. These peak data rate targets are independent of channel conditions, traffic loading, and system architecture. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design[bachievedUW^WgWqWքW֎WUWaddoW։W֖WWWWWWWaddadefinitionforsimpleipVaddaphysaptofigure3.1Vaddtexttoreflect3gpp2approachtoqosVaddthefollowingfiguresquotedinthisdocumentassumetheVaddthejointcontributionsuggestionforsection4.1.1.2heVadjustedWadoptWWZW`WcWiWlWsWvWֆW֊W֐W֓WWWW WBWDWWW\Wadoptoption2WV`ViVsVֆV֐VDVWVadoptoption2withaminormodificationasfollowssystems Vadoptoption3ZVcVlVvV֊V֓V\Vadoptoption3BVadoptthejointcontributiontextforthissectionVVWWWWanyWapproachWareWasUW\W^WeWgWnWqWxWքW֌W֎W֕WWassumeWbeWW128kbpsXW2WWXWZW[WXW ZcAThe current text has three options: Option 1: [The system is expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds. The system should support 95% (TBR) of the channel models with various delay spread values in each of the above environments.] OPTION 2: [The system isB expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds.] OPTION 3: [The system shall work in dense urban, suburban, rural outdoor-indoor, pedestrian and vehicular environments and the relevant channel models shall be applicable. The system shall NOT be designed for ind YcAThe QoS requirements, 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 document requires a MAC laB'yer RTT of <10ms, ensuring the air interface can support low latency traffic under appropriate RF conditions. We recommend that the group not adopt specific packet error rate and latency requirements that would be arbitrary and only restrict possible service definitions in specific deployments.d6 2004/05/11ZELarry FAlder^Technical, Binding_19`6a4.2.3bAdopt Option 3.co large peak data rates whose sole purpose is specs-manship and will rarely be seen $XcC and operational choices. 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.] Comment: Option 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 Din practice. The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Additionally, the concept of two phases is ill-defined. zd5 2004/05/11YELarry FAlder^Technical, Binding_15`14a4.1.7bRemove this section. cK&acdateWW`WiWsWֆW֐WdecideSWdeciding[WdWmWwW֋W֔WdecreasedOWdedicatedTW]WfWpWփW֍WTWdefineGWdefinedZWcWlWvW֊W֓WWEWNW\Wdefines]WdefinitionWWIWdefinitionsYWbWuWֈW֒W[WdelayZWcWlWvW֊W֓WdeleteW Wdeleted WQWdeletingWdeletionWdeliverWdemand WdenseZWcWlWvW֊W֓WdependingUW^WgWqWքW֎WWUWdeployLWdeploymentLWdeploymentsYWbWuWֈW֒W[WdesignXWaWjWtWևW֑WWPWdesignedZWcWlWvW֊W֓WQWdesigningYWbWuWֈW֒W[WdesignsLWdetailWWeditorsnotetherearetwoversionsoftextforthissectionXVaVjVtVևVefficienciesUW^WgWqWքWctargetsXWaWjWtWևW֑WLWtbrZWcWlWvW֊W֓WtcpYWbWuWֈW֒W[WtechniqueWtechniquesWSWtechnologicalWtechnology]WtellsWtermWWterminal[WdWmWwW֋W֔W^WtextTWWWXWZW[W]W`WaWcWdWfWiWjWlWmWpWsWtWvWwWփWֆWևW֊W֋W֍W֐W֑W֓W֔WWWWWWWWIWthanXWaWjWkWtWևW֑WWWLWthatTWUWWWXWYW[W\W]W^W`WaWbWdWeWfWgWiWjWkWmWnWpWqWsWtWuWwWxWփWքWֆWևWֈW֋W֌W֍W֎W֐W֑W֒W֔W֕WWWWWW WWWGWIWLWPWTWUWYW[W_WciencieswUV^VgVthreeZWcW# c2.5WW`WiWsWֆW֐W2.50WW`WiWsWֆW֐W20YWbWkWuWֈW֒W[W0XWaWjWtW3km/hrWW`WiWsW4WWXW`WaWiWjWsWtW4-2WW`WiWsW4-3XWaWjWtW5WWZW`WcWiWlWsW512kbpsXWaWjWtW802.20YWbW90XWaWjWtW95ZWcWlWaTWUWVWXWYWZW[W]W^W_WaWbWcWdWfWgWhWjWkWlWmWpWqWrWtWabilityTW[W]WdWfWmWpWaboveZWcWlWaccumulated\WeWnWachievedUW^WgWqWacrossTW]WfWpWadaptkWadditionYW[WbWdWmWadditionallyXWaWjWtWaddressTW]WfWpWadoptYWbWagainstTW]WfWpWaggregateWWXW`WaWiWjWsWtWrPcmeetingXWaWjWtWևW֑WLWmeetsQWmembersWmentionedWmhzWW`WiWsWֆW֐WWOWmibWmicro-secondsZWcWlWvW֊W֓Wmicroseconds WmimoWminimum WmobileWWWWPWmobileipv4Wmobileipv6WcWlWvW֊W֓WmoreWWWmostTW]WfWpWփW֍WmovementWmsWWmulticastTW]WfWpWփW֍WWmultipleTW]WfWpWփW֍WmustTWWWXW]W`WaWfWiWjWpWsWtWփWֆWևW֍W֐W֑WWnatWWneed[W\WdWeWmWnWwWxW֋W֌W֔W֕WneedsYWbWkWuWֈW֒WWWWnetworkTW[W]WdWfWmWpWwWփW֋W֍W֔WWWWWWnetworksWnew[WdWmWwW֋W֔WcarchitectureXWaWjWtWևW֑WareTWUWWWXWYW[W\W]W^W`WaWbWdWeWfWgWiWjWmWnWpWqWsWtWuWwWxWփWքWֆWևWֈW֋W֌W֍W֎W֐W֑W֒W֔W֕WWWWW WWWIWLWOWPWQWRWTWUWYW[W]W_W]WfWpWփW֍Warrived[WdWmWwW֋W֔Warriving[WdWmWwW֋W֔WartificiallyXWaWjWtWևW֑WasWWWWWWWWWaswrittentherequirementisontheupperlayersmakeinforVaswrittentherequirementseemstobeanequipmentrequiremVassignmentEWassumeWW`WiWsWֆW֐WWatUWXWZW[W^WaWcWdWgWjWlWmWqWtWvWwWքWևW֊W֋W֎W֑W֓W֔WWcservicesTW]WfWpWփW֍WWTWsetSWsetsWsettingTWUW]W^WfWgWpWqWփWքW֍W֎WTWUWseveralYWbWkWuWֈW֒WHW[WshallTWWWXWZW]W`WaWcWfWiWjWlWpWsWtWvWփWֆWևW֊W֍W֐W֑W֓WBWIWQWsizeUW^WgWsmallUW^WgWsoftenedTW]WfWsoftware[WdWsoleXWaWspecificTWWWXWYW\W]W`WaWbWeWfWspecificallyYWbWspecifiesUW^WgWspecs-manshipXWaWspectralTWUWVWWW]W^W_W`WfWgWhWspiritTW]WfWsplitUWVW^W_WgWhWspreadZWcWstatistics\WeWstraightforwardZWcWstreamsTW]WfWstringentUW^WgWsuburbanZWcWsuchTW[W]WdWfW ^cBs applicable under all channel conditions. The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.d11 2004/05/11_EToddFChauvin^Technical, Binding_12`10a4.1.1b3Remove 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. d12 2004/05/11`EToddFChauvin^Technical, Binding_13`13a4.1.5bAdopt Option 2cser terminal and backend infrastructure and is irrelevant at the MAC/PHY layer. In addition, the need for high priority should be captured within QOS framework ( 2004/05/07\ELarry FAlder^Technical, Binding_21`25a4.5.44.5.4 [cB:d has arrived safely at the CPE before deciding to switch from the old software load to the new software load. Comment: This 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 framework (d8 2004/05/11\ELarry FAlder^Technical, Binding_21`25a4.5.4bReplace requirement with a modification of option 3, as follows: "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."cvOptions 1 and 2 in this section are overly detailed with respect to specific statistics that need to be accumulated. d9 2004/05/11]EToddFChauvin^Technical, Binding_8`12a2.2bReplace "shall" with "should".cnts and the relevant channel models shall be applicable. The system shall NOT be designed for ind ZcCoor only and outdoor only scenarios.] Comment: Of the three options, only option 3 is simple, straightforward, and well defined.^d7 2004/05/11[ELarry FAlder^Technical, Binding_21`17a4.5.3bRemove sectioncACurrent Text: CPE 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 loa-4ccellTWUWXW]W^WaWfWgWjWpWqWtWփWքWևW֍W֎W֑WTWUWcellsUW^WgWqWքW֎WUWcellularTW]WfWpWփW֍WTWcertainlyUW^WgWqWքW֎WUWchance[WdWmWwW֋W֔WchannelUWWWXWZW^W`WaWcWgWiWjWlWqWsWtWvWքWֆWևW֊W֎W֐W֑W֓WEWOWUWWWYWchapterIWchoicesXWaWjWtWևW֑WciteWclarificationWWclarifiedWWXW`WaWiWjWsWtWֆWևW֐W֑WWYWclarify WclarifyingUW^WgWqWքW֎WWUWclarityWWclaritythatthetopspeedsarevehicularspeedsVVcleanWWclearTWWW]W`WfWiWpWsWփWֆW֍W֐W WHWTWWWtWֆWևWWNcmac/phy[WdWmWwW֋W֔W^WmadeWmaintainW]WmakeUWVW[W^W_WdWgWhWmWqWrWwWքWօW֋W֎W֏W֔WWWWWUWVWmakesGWNWmakingWLWmanagementWmandateWmandating]WmandatoryCWRWmanyWW]Wmaterial WmatterQWmayWW WWIWmayhasnoparticularmeaninganditappearsthatdefinitionVmbpsXWaWjWtWևW֑Wmbps/sectorWW`WiWsWֆW֐WmbwaWBWmbwashallworkindoorandoutdoorBVmeaningWWDWmeaningfulNWmeansYWbWuWֈW֒WFW[WmeasuredWmechanismWRW]WmeetYWbWkWuWֈW֒W[W ]cAThe current text reads, "The AI shall support broadcast and multicast services." Most cellular systems today support the ability to broadcast transmissions across the entire user base in a cell or sector. The spirit of this requirement should be to support the efficient transmission of broadcast services wherein a single RF transmission from the basestation is received and shared across multiple receivers in the user base. However such capability must be traded off against the complexityB of efficiently implementing this capability in a network setting. For example, this requirement complicates the use of antenna array systems that boost spectral efficiency through the use multiple of antennas that directively transmit towards specific users in the user base. Since it is not clear how to address such issues without further analysis, and since from a services perspective broadcast services are secondary to the ability to provide users with dedicated streams, this requiremenGbbetweenVW_WhWrWօW֏WWIWVWbits/sec/hzUW^WgWqWքW֎WEWUWblockoW։W֖Wblocks/pduHWbothWHWbroadcastWbyWWHWcan\WeWnWxW֌W֕WHW_WcapabilitiesHWcapableHWcapacityHWcellsWchanceHWchangeWWWWWWWWWWWWWWWWOWchangecpetomobilestationinsectionVchangemusttoshouldalsoaddthesentencethereisnorequVchangesentencestartingonthislinetostatehandofftechnVchangetexttoreadinthisstatetheusershouldhavearadOVchangetoread802.20systemshallprovideVchangetoread802.20systemsareintendedtoprovideVchangetoreadaishallefficientlyVchangetoreadaishallprovideVchangetoreadanynetworkinterfacesmayuseVVVdivisionWthat\WWbtheUWVW\W^W_WeWgWhWnWoWqWrWxWքWօW։W֌W֎W֏W֕W֖WWWWWWWWWWWWWWWWWWW WWWWWWWHWIWLWMWOWQWRWSWUWVW_WthetextshouldreadthesystemshallworkindenseurbansuQVthereWtheseHWthey WHWthisUWYW^WbWgWkWqWuWքWֈW֎W֒WWWWWWWWWWWWW WFWMWOWPWUW[WxW֌W֕WtimeWtimingHWtoUW^WgWqWքW֎WWWWWWWWWWWWWW WWWWWWWWHWOWTWUWtopologyHWtotalHWtrafficHWRWtransitionsHWtranslatedWulHWuncorrectableHWWi_bReplace 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. d170g2222 2004/05/11 2004/04/29mulated. g2222 2004/05/07 2004/04/29r 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. g2222 2004/05/07 2004/04/29 ]cCt should be softened. d10 2004/05/11^EToddFChauvin^Technical, Binding_11`10a4.1.1bSpecify 2 bits/sec/Hz as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved.cAThis requirement specifies stringent spectral efficiencies without explicitly clarifying the conditions under which it should be achieved. For example, because cell size is not constrained by the requirements, the spectral efficiencies could be achieved with very small cells. Or, for example, operation at 120km/hr is very different depending on the environment - certainly we are not interested in operation at 120km/hr in an urban setting, yet the requirement could be interpreted that it iYckbpsXWaWjWtWևW֑Wkm/hrWW`WiWsWֆW֐WkmphLWlanguageWWWWlargeXWaWjWtWևW֑WDWGWXWlargepeakdatarateislittlehopeforuserDVlastQWlatencyYWbWuWֈW֒W[WlayerYW[WbWdWmWuWwWֈW֋W֒W֔WW[W]W^WlayersWleastZWcWlWvW֊W֓WlessXWaWjWtWևW֑Wlet's WlightLWlikeWlimitXWaWjWtWևW֑WPWXWlimitedGWlineWlinearity WlittleDWload[WdWmWwW֋W֔WloadedXWaWjWtWևW֑WDWloadingXWaWjWtWևW֑Wloads[WdWmWwW֋W֔WlotEWlowYWbWuWֈW֒W[WlowerLWmacYWbWuWֈW֒WW[W<!cphasesXWaWjWtWևW֑WZWphyWplaceWplacesWWpointSWpoorWWpoorlanguagecleanupVVportableLWportionHWpossibleYWbWuWֈW֒WIWLW[WpowerWppp]WpracticeXWaWjWtWևW֑WXWprecludeWpreferQWSWpreviousWWpreviouslyWpriority[WdWmWwW֋W֔W^WprivateWprocessLWprofilesYWbWkWuWֈW֒W[WpromoteWproperWproperuseofrequirementslanguageVproposalHWLWproposalsUWVWXW^W_WaWgWhWjWqWrWtWքWօWևW֎W֏W֑WUWVWXWprotocolsIWproveLW S`cACurrent Text: OPTION 1: [ The aggregate data rate for downlink and uplink shall be consistent with the spectral efficiency. Example Aggregate Data Rates are shown in table 4-2) Parameter Aggregate Data Rates 1.25 MHz. @ 3km/hr 1.25 MHz . @ 120km/hr 5 MHz.@ 3km/hr 5 MHz. @ 120 km/hr DL UL DL UL DL UL DL UL Aggregate Date Rates (Mbps/sector) 2.50 1.88 1.25 0.94 10 5 5 2.5 Table 4 2 Aggregate Data Rates ] OPTION 2: [The aggregate data rate for downlink and uplink shall be consistenBt with the spectral efficiency.] Comment: The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Option 2 is clear and specific and does not assume specific channel bandwidths.d13 2004/05/11aEToddFChauvin^Technical, Binding_14`1a4.1.5.1bRemove Option 1cata rate for downlink and uplink shall be consistenzbdownlinkVW_WhWrWօW֏WLWVWduplexWduplexingWeWeffectively\WeWnWxW֌W֕WHW_WefficiencyUW^WgWqWքW֎WWEWLWMWUWefficientWefficientlyWeitheroW։W֖WenableWendoW։W֖Wend-to-endWensureHWensuringHWentitiesIWenvironmentRWenvironmentsQWerrorHWerrorsHWevaluationUW^WgWqWքW֎WUWeventHWexistingHWexpressedMWfailedHWfddWfeaturesWWfigureWfiguresWfinalMWfirstWfollowingoWWHWRWfollows\WeWnWxW֌W֕W W WforWWWWWWWHWRWforwardHWforwardingHWfragmentWWfreeHWfrequenciesWfrequencyWSWfromWWWWWHWgW֕WWintoWW acACurrent Text: Editors Note: There are two versions of text for this section to consider at the next WG meeting OPTION 1: [ The AI shall support peak per-user 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. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design and operational choices. Average user data rates in a loadedB system shall be in excess of 512Kbps downlink and 128Kbps uplink. This shall be true for 90% of the cell coverage or greater. Table 4 3 ] OPTION 2: [The AI shall support peak per-user data rates in excess of 1 Mbps on the downlink and in excess of 300 kbps on the uplink. These peak data rate targets are independent of channel conditions, traffic loading, and system architecture. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for designcfocusGWforTWUWWWXWYWZW[W]W^W`WaWbWcWdWfWgWiWjWlWmWpWqWsWtWuWvWwWփWքWֆWևWֈW֊W֋W֍W֎W֐W֑W֒W֓W֔WWWWWWWDWEWLWOWQWTWUW[W]W^Wform-factorLWformalWforward-lookingWfragmentWframes]Wcwithin[WdWmWwW֋W֔WW^WwithoutTWUW]W^WfWgWpWqWփWքW֍W֎WTWUW]WwordWworkZWcWlWvW֊W֓WWBWworkingW WwouldYWbWuWֈW֒W[WwrittenWWWWWyearsYWbWkWuWֈW֒W[WyetUW^WgWqWքW֎WUWd T0U@VPW`XpYZ[\‚!]‚"^‚#_‚$`‚%a‚&b‚'c‚(d‚)e‚*f‚1g‚2h‚3i‚4j‚5k‚6l‚7m‚8n‚9o‚:p‚Ap‚Ap‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚A‚B‚C‚D ‚E ‚F ‚G ‚H ‚I‚J‚Q‚R‚S‚T‚U‚V‚W‚X‚Y‚Z‚a‚b‚c‚d‚e‚f‚g ccAThe current text has three options: Option 1: [The system is expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds. The system should support 95% (TBR) of the channel models with various delay spread values in each of the above environments.] OPTION 2: [The system isB expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds.] OPTION 3: [The system shall work in dense urban, suburban, rural outdoor-indoor, pedestrian and vehicular environments and the relevant channel models shall be applicable. The system shall NOT be designed for ind bcAThe QoS requirements, 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 document requires a MAC laB'yer RTT of <10ms, ensuring the air interface can support low latency traffic under appropriate RF conditions. We recommend that the group not adopt specific packet error rate and latency requirements that would be arbitrary and only restrict possible service definitions in specific deployments.d15 2004/05/11cEToddFChauvin^Technical, Binding_19`6a4.2.3bAdopt Option 3.c large peak data rates whose sole purpose is specs-manship and will rarely be seen %acC and operational choices. 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.] Comment: Option 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 Din practice. The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Additionally, the concept of two phases is ill-defined. zd14 2004/05/11bEToddFChauvin^Technical, Binding_15`14a4.1.7bRemove this section. c.ycoption1WVXVZV`VaVcViVjVlVsVtVvVֆVևV֊V֐V֑V֓Voption1peakratesresultinalargeuserdataratepeaktoXVoption2isclearandspecificanddoesnotassumespecificWVoption3issimplestraightforwardandwelldefined\VoptionalWoptionsZW\WcWeWlWnWvWxW֊W֌W֓W֕WHWMWNWPWQWRWSW_Woptions1and2inthissectionareoverlydetailedwithres\VeVnVxV֌V֕VorTWUWXW]W^WaWfWgWjWpWqWtWփWքWևW֍W֎W֑WW W WWWWOWRWTWUW]WlWvW֊W֓WoverYWbWuWֈW֒WWoverly\WeWnWxW֌W֕WpacketYWbWuWֈW֒Wpackets[WdWmWwW֋W֔WpaidWparYWbWuWֈW֒Wpara WparagraphWZcwellZWcWlWvW֊W֓WW\Wwell-definedWwgXWaWjWtWևW֑WLWwhatWW WWQWwhenYWbWkWuWֈW֒W[W]WwhereinTW]WfWpWփW֍WTWwhetherWwhichUW^WgWqWքW֎WWOWUWwhileWWwhoseXWaWtWևW֑WXWwhyWAWwhy8e-8inoption1needsclarifyingtextVwidthFWwillUWVWXWYW^W_WaWbWgWhWjWqWrWtWuWքWօWևWֈW֎W֏W֑W֒W WLWUWVWXW[WwithTWUWWWZW\W]W^W`WcWeWfWgWiWlWnWpWqWsWvWxWփWքWֆW֊W֌W֍W֎W֐W֓W֕WWWWWWW WWQWTWUW_W9cframework[WdWmWwW֋W֔W^WwWfromTWYW[W]WbWdWfWkWmWpWuWwWfurtherTW]WfWpWfurthermoreYWbWuWfuturekWgivenWWXW[W`WaWdWiWjWmWsWtWwWgreaterXWaWjWtWgroupYWbWuWhandleYWbWuWhasZW[WcWdWlWmWvWwWhave[WdWmWwWheavily[WdWmWwWhigh[WdWmWwWholding[WdWmWwWhowTW]WfWpWhoweverTW]WfWpWill-definedXWaWjWtWimage[WdWmWwWimplementedYWbWkWuWimplementingTW]WfWpWimposingkWinTWUWWWXWYWZW[W\W]W^W`WaWbWcWdWeWfWgWiWjWkWlWmWnWpWqWsWtWuWvWwWindependentXWaWjWtW gcBs 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.d20 2004/05/11hEJohnFChen^Technical, Binding_12`10a4.1.1b3Remove 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. d21 2004/05/11iEJohnFChen^Technical, Binding_13`13a4.1.5bAdopt Option 2c 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 framework ( 2004/05/07eEToddFChauvin^Technical, Binding_21`25a4.5.44.5.4 dcB:d has arrived safely at the CPE before deciding to switch from the old software load to the new software load. Comment: This 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 framework (d17 2004/05/11eEToddFChauvin^Technical, Binding_21`25a4.5.4bReplace requirement with a modification of option 3, as follows: "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."cvOptions 1 and 2 in this section are overly detailed with respect to specific statistics that need to be accumulated. d18 2004/05/11fEJohnFChen^Technical, Binding_8`12a2.2bReplace "shall" with "should".cents and the relevant channel models shall be applicable. The system shall NOT be designed for ind ccCoor only and outdoor only scenarios.] Comment: Of the three options, only option 3 is simple, straightforward, and well defined.^d16 2004/05/11dEToddFChauvin^Technical, Binding_21`17a4.5.3bRemove sectioncACurrent Text: CPE 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 loacsupportTWXWYWZW]WaWbWcWfWjWlWpWtWuWvWփWևWֈW֊W֍W֑W֒W֓WWWWWHWIWRWTW[WsupposedW Wswitch[WdWmWwW֋W֔WsystemXWYWZWaWbWcWjWlWtWuWvWևWֈW֊W֑W֒W֓WCWGWQW[WsystemsTW]WfWpWփW֍WWLWTWtableWWXW`WaWiWjWsWtWֆWևW֐W֑WWEWLWtable4.1specifiesadownlinkspectralefficiencyof2.0b/LVtagging]W fcAThe current text reads, "The AI shall support broadcast and multicast services." Most cellular systems today support the ability to broadcast transmissions across the entire user base in a cell or sector. The spirit of this requirement should be to support the efficient transmission of broadcast services wherein a single RF transmission from the basestation is received and shared across multiple receivers in the user base. However such capability must be traded off against the complexityB of efficiently implementing this capability in a network setting. For example, this requirement complicates the use of antenna array systems that boost spectral efficiency through the use multiple of antennas that directively transmit towards specific users in the user base. Since it is not clear how to address such issues without further analysis, and since from a services perspective broadcast services are secondary to the ability to provide users with dedicated streams, this requiremenC-b802.20\WeWnWxW֌W֕WWWWHW_W802.20-basedW8e-8Wa\WeWnWoWxW։W֌W֕W֖WWWW WWWWWHWLWMWOWRWSW_WabilityHWaccessHWaccountW boptionWWXWZW\W`WaWcWeWiWjWlWnWsWtWvWxWֆWևW֊W֌W֐W֑W֓W֕WW WAWDWHWMWPWWWXWYWZW\Woption1GWoption2FWoption3BWoptionallyWoroW։W֖WW WWWWWWIWPWRWoutdoor-indoorQWpacketWpacketsHWpagingHWparLWparagraphWWparametersWpartnersRWpedestrianQWperHWeshallwithshouldTV]VfVpVrequirement\WeWnWsectionYW[WbWdWkWmWseeoWseeconributionc802.20-04/xxoVshallTW\W]WeWfWnWpWshouldTW]WfWpWso\WeWnWspecifyUW^WgWqWspecify2bits/sec/hzasthespectralefficiencyandallowtUV^VgVqVspectralUW^WgWqWsupport\WeWnWthat\WeWnW u]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 2d168g2220 2004/05/11 2004/04/29^EKazuhiroFMurakami^Technical, Binding_21`17a4.5.3bRemove sectioncThis is a feature of the user terminal and backend infrastructure and is irrelevant at the MAC/PHY layer. In addition, the need for high priority should be captured within QOS frameworkd169g2221 2004/05/11 2004/04/29_EKazuhiroFMurakami^Technical, Binding_21`25a4.5.4 fcCt should be softened. d19 2004/05/11gEJohnFChen^Technical, Binding_11`10a4.1.1bSpecify 2 bits/sec/Hz as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved.cAThis requirement specifies stringent spectral efficiencies without explicitly clarifying the conditions under which it should be achieved. For example, because cell size is not constrained by the requirements, the spectral efficiencies could be achieved with very small cells. Or, for example, operation at 120km/hr is very different depending on the environment - certainly we are not interested in operation at 120km/hr in an urban setting, yet the requirement could be interpreted that it i2^technicalbindingTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVփVքVօVֆVևVֈV։V֊V֋V֌V֍V֎V֏V֐V֑V֒V֓V֔V֕V֖VAVBVCVDVEVFVGVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_Vtechnicalnon-bindingHVIVWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWֽWi֨Vwhile֘WwiderֻWwith֨WַWword֟W֠WworkַW7:Bcup[WdWmWwW֋W֔WWWupgrade[WdWmWwW֋W֔WupgradesHWuplinkUWVWWWXW^W_W`WaWgWhWiWjWqWrWsWtWքWօWֆWևW֎W֏W֐W֑WEWLWUWVWupperWupstreamIWWփW֍WusedYWbWkWuWֈWuserTWXW[W]WaWdWfWjWmWpWtWwWփWևW֋W֍W֑WusersTW]WfWpWփW֍WvaluesXWZWaWcWjWlWtWvWևW֊W֑WvariousZWcWlWvW֊WvehicularZWcWlWvW֊WversionsXWaWjWtWևW֑WversusUWVW^W_WgWhWqWrWքWօW֎W֏WveryUW[W^WdWgWmWqWwWքW֋W֎WweUWWWXWYW^W`WaWbWgWiWjWqWsWtWuWքWֆWևWֈW֎W֐W PicACurrent Text: OPTION 1: [ The aggregate data rate for downlink and uplink shall be consistent with the spectral efficiency. Example Aggregate Data Rates are shown in table 4-2) Parameter Aggregate Data Rates 1.25 MHz. @ 3km/hr 1.25 MHz . @ 120km/hr 5 MHz.@ 3km/hr 5 MHz. @ 120 km/hr DL UL DL UL DL UL DL UL Aggregate Date Rates (Mbps/sector) 2.50 1.88 1.25 0.94 10 5 5 2.5 Table 4 2 Aggregate Data Rates ] OPTION 2: [The aggregate data rate for downlink and uplink shall be consistenBt with the spectral efficiency.] Comment: The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Option 2 is clear and specific and does not assume specific channel bandwidths.d22 2004/05/11jEJohnFChen^Technical, Binding_14`1a4.1.5.1bRemove Option 1cata rate for downlink and uplink shall be consisten jcACurrent Text: Editors Note: There are two versions of text for this section to consider at the next WG meeting OPTION 1: [ The AI shall support peak per-user 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. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design and operational choices. Average user data rates in a loadedB system shall be in excess of 512Kbps downlink and 128Kbps uplink. This shall be true for 90% of the cell coverage or greater. Table 4 3 ] OPTION 2: [The AI shall support peak per-user data rates in excess of 1 Mbps on the downlink and in excess of 300 kbps on the uplink. These peak data rate targets are independent of channel conditions, traffic loading, and system architecture. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design!IcAK@ates 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. 4_6csharedTW]WfWpWփW֍WTWshouldTWUWXWZW[W]W^WaWcWdWfWgWjWlWmWpWqWtWvWwWփWքWևW֊W֋W֍W֎W֑W֓W֔WWWWWWWWWWEWGWRWTWUWXW^WshownWWXW`WaWiWjWsWtWֆWևW֐W֑WsideWsignificantlyLWsimpleZWcWlWvW֊W֓WW\WsimplifiedWsimultaneousWsimultaneouslyWքW֎WsmallUW^WgWqWքW֎WsokWsoftenedTW]WfWpWփW֍Wsoftware[WdWmWwW֋W֔WsoleXWaWtWևW֑WsolutionkWspecificTWWWXWYW\W]W`WaWbWeWfWiWjWnWpWsWtWuWxWփWֆWևWֈW֌W֍W֐W֑W֒W֕WspecificallyYWbWuWֈW֒WֆW4dcconditionsUWXWYW^WaWbWgWjWqWtWuWքWևWֈW֎W֑W֒WWWUW[WconfusesWconfusingWWconsiderXWaWjWtWևW֑WconsistentWW`WiWsWֆW֐WWconstrainedUW^WgWqWքW֎WcontributionoW։W֖WcouldUW^WgWqWքW֎WcoverageXWaWjWtWևW֑Wcpe[WdWmWwW֋W֔WcreateYWbWkWuWֈW֒WcurrentTWWWXWYWZW[W]W`WaWbWcWdWfWiWjWlWmWpWsWtWuWvWwWփWֆWևWֈW֊W֋W֍W֐W֑W֒W֓W֔WcurrenttextWVXV[V`VaVdViVjVmVsVtVwVֆVևV֋V֐V֑V֔Vcurrently[WdWmWwW֋W֔WdataWWXW`WaWiWjWsWtWֆWևW֐W֑W lcB expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds.] OPTION 3: [The system shall work in dense urban, suburban, rural outdoor-indoor, pedestrian and vehicular environments and the relevant channel models shall be applicable. The system shall NOT be designed for indCoor only and outdoor only scenarios.] Comment: Of the three options, only option 3 is simple, straightforward, and well defined.^d25 2004/05/11mEJohnFChen^Technical, Binding_21`17a4.5.3bRemove sectionc kcAThe QoS requirements, 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. These flexible schemes can be used to adapt QoS profiles to the performance of the internet backbone in the future, so it is a better solution than imposing fixed QoS performance requirements.d24 2004/05/11lEJohnFChen^Technical, Binding_19`6a4.2.3bAdopt Option 3.cAThe current text has three options: Option 1: [The system is expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds. The system should support 95% (TBR) of the channel models with various delay spread values in each of the above environments.] OPTION 2: [The system is jcC and operational choices. 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.] Comment: Option 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 that will rarely be seen in practice. The concept of bandwDidth must be clarified given that we are not requiring specific channel bandwidths. Additionally, the concept of two phases is ill-defined. Wd23 2004/05/11kEJohnFChen^Technical, Binding_15`14a4.1.7bRemove this section. c*{csectorTW]WfWpWփW֍WTWseeXWaWjWoWtWևW։W֑W֖WWXWseecontribution04/56r1֖Vseecontributionc802.20-04/56r1oV։VseemWSWseemsWW W WWWWSWseenXWaWjWtWևW֑WXWsensiblyUWVW^W_WgWhWqWrWքWօW֎W֏WUWVWsentenceW WWWWWQWseparationUWVW^W_WgWhWqWrWքWօW֎W֏WUWVW]WserviceYWbWuWֈW֒WW WW[WW WW[W[W[WuscindoorZWcWlWvW֊W֓WBWQWinfluenceWinformativeWWWWinfrastructure[WdWmWwW֋W֔W^WintentWLWinterestedUW^WgWqWքW֎WUWinterfaceYWbWuWֈW֒WWWWWWWW WWWWW[W]WerpretedUW^WgWqWքW֎WintoWipWWWWip-dataYWbWuWֈW֒Wipv4WWipv6WWirrelevant[WdWmWwW֋W֔WWisTWUWWWXWYWZW[W]W^W`WaWbWcWdWfWgWiWjWkWlWmWpWqWsWtWuWvWwWփWքWֆWևWֈW֊W֋W֍W֎W֐W֑W֒W֓W֔WWWWWWWWWWWWWW W W WWWWWWWWis-95WissueW,1ctheTWUWVWWWXWYWZW[W]W^W_W`WaWbWcWdWfWgWhWiWjWkWlWmWpWqWrWsWtWuWvWwWփWքWօWֆWևWֈW֊W֋W֍W֎W֏W֐W֑W֒W֓W֔WWWWWWWWWWWWWWWWWWWWW WWWWWWWWWWWWWWWW WAWCWGWHWIWLWOWQWRWSWTWUWVWXWYWZW[W]W^WtheconceptofbandwidthmustbeclarifiedgiventhatweareYVtheconceptoftwophasesisill-definedZVtheconstraintsonthetimeinwhichachannelneedstobeaOVWmWnWpWqWtWwWxWփWքWևWthisrequirementspecifiesstringentspectralefficiencieswUV^VgVqVքVthreeZWcWlWvW֊Wp3Qcbackend[WdWmWwW֋W֔W^WbandFWbandwidthWWXW`WaWiWjWsWtWֆWևW֐W֑WGWOWYWbandwidthsWWXW`WaWiWjWsWtWֆWևW֐W֑WWWYWbaseTW]WfWpWփW֍WWIWTWbasedWaWbWcWdWeWfWgWiWjWkWlWmWnWpWqWsWtWuWvWwWxWփWքWֆWևWֈW֊W֋W֌WbecauseUW^WgWqWքWbefore[WdWmWwW֋WbetterkWbetweenUWVW^W_WgWhWqWrWքWօWboostTW]WfWpWփWbroadcastTW]WfWpWփW֍WbyUW^WgWqWքWc802-20-04-33r1XWaWjWtWևWc802.20-04/xxoW։WcanYW[WbWdWkWmWuWwWֈW֋WcapabilityTW]WfWpWփWcapable[WdWmWwW֋WnbReplace requirement with a modification of option 3, as follows: "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."cvOptions 1 and 2 in this section are overly detailed with respect to specific statistics that need to be accumulated. d27 2004/05/11oEJohnFChen^Technical, Binding_17`28a4.1.13.5bPropose to add following text at the end of section 4.1.13.5: "The AI may use either a stream cipher (such as RC4 or AES in stream cipher mode) or a block cipher (such as AES in block mode). The use of AES shall not be mandatory."c"See contribution C802.20-04/56r1. d28j#1: "The AI may use either a stream cipher (such as RC4 or AES in stream cipher mode) or a block cipher (such as AES in block mode). The use of AES shall be optional."@A>  33    33> "should".c]d‚Aq‚Br‚Cs‚Dt‚Eu‚Fv‚Gw‚Hx‚Iփ‚Jք‚Qօ‚Rֆ‚Sև‚Tֈ‚U։‚V֊‚W֋‚X֌‚Y֍‚Z֎‚a֏‚b֐‚c֑‚d֒‚e֓‚f֔‚g֕‚h֖Âq@ÂrPÂs`ÂtpÂuÂvÂwÂx Ây"Âz#Â$Â%Â&Â'Â(Â)Â*Â0Â2Â3Â4Â5Â6Â7Â8Â9Â:Â@ÂBÂCÂD ÂE ÂF ÂG ÂH ÂIÂJÂPÂRÂSă!@ă!%Pă!5`ă!Epă!Uă!eă!uÃ!ă! ă!0ă"@ă"&Pă"6`ă"Fp Ã"P"Ã"`#Ã"p$Ã"%Ã"&Ã"'Ã#(Ã# )Ã#0*Ã#@+Ã#P,Ã#`-Ã#p.Ã#/Ã#0Ã#1Ã$2Ã$ 3Ã$04Ã$@5Ã$P6Ã$`7Ã$p8Ã$9Ã$:Ã$@Ã%AÃ% BÃ%0CÃi Ãj0 mcACurrent Text: CPE 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 loaB:d has arrived safely at the CPE before deciding to switch from the old software load to the new software load. Comment: This 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 framework (d26 2004/05/11nEJohnFChen^Technical, Binding_21`25a4.5.4rhcnextXWaWjWtWևW֑WnoWWWAWDWLWRWnotTWUWWWXWYWZW]W^W`WaWbWcWfWgWiWjWlWpWqWsWtWuWvWփWքWֆWևWֈW֊W֍W֎W֐W֑W֒W֓WWWWW W WWWWWWWWW WCWGWLWNWQWSWTWUWWWXWYW[W]Wnotclearwhatthisissupposedtoconveyifthereareairi VWjWkWlWmWpWqWrWsWtWuWvWwWփWքWօWֆWևWֈW֊W֋W֍W֎W֏W֐W֑W֒W֓W֔WWWWWWWWWWWoffTW]WfWpWփW֍Wold[WdWmWwW֋W֔WonUWXW^WaWgWjWqWtWքWևW֎W֑WWWWone[WdWmWwW֋W֔WֆWևW֊W pcAThe current text reads, "The AI shall support broadcast and multicast services." Most cellular systems today support the ability to broadcast transmissions across the entire user base in a cell or sector. The spirit of this requirement should be to support the efficient transmission of broadcast services wherein a single RF transmission from the basestation is received and shared across multiple receivers in the user base. However such capability must be traded off against the complexityB of efficiently implementing this capability in a network setting. For example, this requirement complicates the use of antenna array systems that boost spectral efficiency through the use multiple of antennas that directively transmit towards specific users in the user base. Since it is not clear how to address such issues without further analysis, and since from a services perspective broadcast services are secondary to the ability to provide users with dedicated streams, this requiremen [cB`ַַַַַַַַַַַַַև֑‚&Ybkuֈ֒‚(o։‚*Zclv֊֓‚2[\demnwx֋֌֔֕` Xajtև֑pZclv֊֓‚!UV^_ghqrքօ֎֏‚#T]fpփ֍‚$W`isֆ֐‚%Ybkuֈ֒‚([dmw֋֔‚6\enx֌֕‚9o։a2.2T]fpփ֍4.1.1UV^_ghqrքօ֎֏4.1.13o։֖4.1.5W`isֆ֐4.1.5.1Xajtև֑4.1.7Ybkuֈ֒4.2.3Zclv֊֓4.5.3[dmw֋֔4.5.4\enx֌֕b1XWaWjWtWևW֑W2UWWW^W`WgWiWqWsWքWֆW֎W֐W3ZW\WcWeWlWnWvWxW֊W֌W֓W^-^bindingTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWփWքWօWֆWևWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖WAWBWCWDWEWFWGWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_Weditorialnon-bindingHWIWhandofftechnVVVVVVVVVVVVchangetoread802.20systemshallprovide֚V֚Vchangetoread802.20systemsareintendedtoprovide֙V֙VV֙Vvide֙V֙V֙V֙V֙V֗Wieee֘Winclude֗Windustry֗Wintended֙Winterface֗Witu-t֗Wjitter֗Wlatency֗Wloss֗Wmake֘Wmbwa֗Wmechanisms֘Wminimum֘W֘W"B֊EJoanneFWilson^Technical, Binding_19`6a4.2.3bAdopt Option 3.cAThe current text has three options: Option 1: [The system is expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds. The system should support 95% (TBR) of the channel models with various delay spread values in each of the above environments.] OPTION 2: [The system isThe system ispectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.g2212 2004/05/07օEJoanneFWilson^Technical, Binding_12`10a4.1.1b3Remove the distinction between uplink and downlink.( [ֆcACurrent Text: OPTION 1: [ The aggregate data rate for downlink and uplink shall be consistent with the spectral efficiency. Example Aggregate Data Rates are shown in table 4-2) Parameter Aggregate Data Rates 1.25 MHz. @ 3km/hr 1.25 MHz . @ 120km/hr 5 MHz.@ 3km/hr 5 MHz. @ 120 km/hr DL UL DL UL DL UL DL UL Aggregate Date Rates (Mbps/sector) 2.50 1.88 1.25 0.94 10 5 5 2.5 Table 4 2 Aggregate Data Rates ] OPTION 2: [The aggregate data rate for downlink and uplink shall be consistenBt with the spectral efficiency.] Comment: The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Option 2 is clear and specific and does not assume specific channel bandwidths.d41g2214 2004/05/11ևEJoanneFWilson^Technical, Binding_14`1a4.1.5.1bRemove Option 1c4.1.1b3Remove the distinction between uplink and downlink.he split between uplink and downlink.ink and downlink. 2004/05/07@a4.1.1"#$%&'()*+,-./0123456789:@HIJK2.12.2T]fpփ֍T3.13.1.13.24.1.1UV^_ghqrքօ֎֏AELUV4.1.1.24.1.104.1.114.1.124.1.13.5o։֖4.1.34.1.44.1.5W`isֆ֐FMW4.1.5.1Xajtև֑DGNXYZ4.1.6O4.1.7Ybkuֈ֒P[4.1.84.1.94.2.14.2.24.2.3Zclv֊֓ BQ\4.2.4 4.2.6 4.3 4.4.14.54.5.14.5.1.14.5.2R]4.5.3[dmw֋֔C^4.5.4\enx֌֕S_4.74.85 afwl Hl H Ã"P"Ã"`#Ã"p$ EJG?W]IV<f#3ACWDGW#X^H_UYGpW \_lHUn]GW ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$TgvhJcaboveZWcWlWvW֊W֓WacceptanceLWaccomplished]Waccumulated\WeWnWxW֌W֕W_WachievableLWachieveWWachievedUW^WgWqWքW֎WUWacrossTW]WfWpWփW֍WTW]WactingWactualLWadaptkWaddHWaddedWWadditionYW[WbWdWmWuWwWֈW֋W֒W֔WW[W^WadditionalWadditionallyXWaWjWtWևW֑WaddressTW]WfWpWփW֍WTWadoptYWbWuWֈW֒W[Wadvocating]Wadvocatingaspecificmechanismforseparationoftrafficdo]VagainstTW]WfWpWփW֍WTWaggregateWWXW`WaWiWjWsWtWֆWևW֐W֑WAWFWGWaggregatedataratemeansspectralefficiencytimesbandwidFVaggregationSWagnostic]WnchoweverTW]WfWpWփW֍WSWTWiLWQWRWSWieee802.20GWietfWIWifW WWQWill-definedXWaWjWtWևW֑WZWillustratedIWimage[WdWmWwW֋W֔WimplementationWimplementedYWbWkWuWֈW֒WIW[WimplementingTW]WfWpWփW֍WTWimportantWDWimportantthingisaveragedatarateforuserinloadedDVimposePWuWvWwWxWփWքWֆWևWֈW֊W֋W֌W֍W֎W֐W֑W֒W֓W֔W֕WWWWWWWW WWWWWWW WDWincludingWinclusionWinclusionofanipnetworkonthemssideisconfusingisthVinconsistentWWincorrectWWincorrectdefinitionofsofthandoffsofthoisahowiththVindependentXWaWjWtWևW֑WindividualsW -ևcC and operational choices. 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.] Comment: Option 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 Din practice. The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Additionally, the concept of two phases is ill-defined. zd42g2215 2004/05/11ֈEJoanneFWilson^Technical, Binding_15`14a4.1.7bRemove this section. crarely 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 "bsupport\WeWnWxW֌W֕WWWWWWHWIWRW_WsupportedWswitchHWswitchingWsystemWW WHWQWRWsystemsWWWtLWtableWLWtaggingRWtakingWtbdWtechnicalSWtechniquesWterminalsWtextoWWWWWWWWWHWIWOWQWRWthan WWHWOWthat\WeWnWxW֌W֕WWWHWIWMWRW_W ֈcAThe QoS requirements, 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 document requires a MAC laB'yer RTT of <10ms, ensuring the air interface can support low latency traffic under appropriate RF conditions. We recommend that the group not adopt specific packet error rate and latency requirements that would be arbitrary and only restrict possible service definitions in specific deployments.d43g2216 2004/05/11։EJoanneFWilson^Technical, Binding_17`28a4.1.13.5bSee conribution C802.20-04/xx.cSee contribution C802.20-04/xx.d44g2222 2004/05/11\icthewordmusthasnomeaninginthisdocumentaddedsentenceVtheirLWthenEWthereXWaWjWtWևW֑W WWWWWLWthereforeXWaWjWtWևW֑WNWRWXWtheseXWaWjWkWtWևW֑WWWWLWthey[WdWmWwW֋W֔W WEWthingDWthisTWUWXW[W\W]W^WaWdWeWfWgWjWmWnWpWqWtWwWxWփWքWևW֋W֌W֍W֎W֑W֔W֕WWWWWWWWWWWW W W W WWWWWWWWWWWW WAWCWMWNWSWTWUW]W^WthiscontributionisnotreferencedanywhereintherequiremV Vthiscouldbedeletedorconsolidatedwithothermaterialno VVELarry FAlder^Technical, Binding_12`10a4.1.1b3Remove 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. d3 2004/05/11WELarry FAlder^Technical, Binding_13`13a4.1.5bAdopt Option 2cdownlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink. d3 2004/05/11WELarry FAlder^Technical, Binding_13`13a4.1.5bAdopt Option 2cwith respect to specific statistics that need to be accumulated. g2220 2004/05/07t possible service definitions in specific deployments.g2216 2004/05/07։E Joanne Wilson^Technical, Binding_17^Technical, Binding_17g2222 2004/05/07LcAMEPERbAScATcBUcAVcY`[cB]cA_b_bhannel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds. The system should support 95% (TBR) of the channel models with various delay spread values in each of the above environments.] OPTION 2: [The system isB expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds.] OPTION 3: [The system shall work in dense urban, suburban, rural outdoor-indoor, pedestrian and vehicular environments and the relevant channel models shall be applicable. The system shall NOT be designed for ind' ֊cB expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds.] OPTION 3: [The system shall work in dense urban, suburban, rural outdoor-indoor, pedestrian and vehicular environments and the relevant channel models shall be applicable. The system shall NOT be designed for indCoor only and outdoor only scenarios.] Comment: Of the three options, only option 3 is simple, straightforward, and well defined.^d45g2218 2004/05/11֋EJoanneFWilson^Technical, Binding_21`17a4.5.3bRemove sectioncn the current requirements document requires a MAC la$lc2ևW֊W֋W֌W֐W֑W֓W֔W֕W WNWRWSWWW]W2.0LW#bc10msYWbWuWֈW֒W[W120WW`WiWsWֆW֐WLW120km/hrUWWW^W`WgWiWqWsWքWֆW֎W֐WUW128kbpsXWaWjWtWևW֑W2WWXWZW[W\W`WaWcWdWeWiWjWlWmWnWsWtWvWwWxWֆW_cspecifiesUW^WgWqWքW֎WLWMWNWUWspecifyWAWDWLWspecifyingWspecs-manshipXWaWtWևW֑WXWspectralTWUWVWWW]W^W_W`WfWgWhWiWpWqWrWsWփWքWօWֆW֍W֎W֏W֐WWWWAWEWFWLWTWUWVWspectralefficiencyisdefinedtodistinctbetweenuplinkanEVspeedEWspeedsWWtcdetailed\WeWnWxW֌W֕W_WdevelopedWdevelopingLWdevicesLWdictateWdifferentUW^WgWqWքW֎WWUWdiffservYWbWkWuWֈW֒WW[Wdiffservmayworkwithinterfacingto3gppnetworksbutthe3VdirectionHWdirectivelyTW]WfWpWփW֍WTWdiscussWdiscussionWSWdistinctEWWWdoesWW`WiWsWֆW֐WWdoesn'tWdownlinkUWVWWWXW^W_W`WaWgWhWiWjWqWrWsWtWքWօWֆWևW֎W֏W֐W֑WdraftingWdriveWdrivesWduplexWduplicated WeachZWcWlWvW֊W֓WeasierWeasyWeditorsXWaWjWtWևW֑WeditorsnotetherearetwoversionsoftextforthissectionXVaVjVtVևV֑VefficienciesUW^WgWqWքW֎WW") ֋cACurrent Text: CPE 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 loaB:d has arrived safely at the CPE before deciding to switch from the old software load to the new software load. Comment: This 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 framework (d46g2219 2004/05/11֌EJoanneFWilson^Technical, Binding_21`25a4.5.4channel models shall be applicable. The system shall NOT be designed for ind  քcBs applicable under all channel conditions. The separation of downlink versus uplink spectral efficiency unnecessarily complicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink.d39g2212 2004/05/11օEJoanneFWilson^Technical, Binding_12`10a4.1.1b3Remove 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. d40g2213 2004/05/11ֆEJoanneFWilson^Technical, Binding_13`13a4.1.5bAdopt Option 2cich this is achieved.cnd is irrelevant at the MAC/PHY layer. In addition, the need for high priority should be captured within QOS framework (g2219 2004/05/07֌E Joanne Wilson/05/07֌E Joanne Wilsong2225 2004/05/07'/֌bReplace requirement with a modification of option 3, as follows: "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."cvOptions 1 and 2 in this section are overly detailed with respect to specific statistics that need to be accumulated. d47g2220 2004/05/11֍EMichaelF Youssefmir^Technical, Binding_8`12a2.2bReplace "shall" with "should".cAThe current text reads, "The AI shall support broadcast and multicast services." Most cellular systems today support the ability to broadcast transmissions across the entire user base in a cell or sector. The spirit of this requirement should be to support the efficient transmission of broadcast services wherein a single RF transmission from the basestation is received and shared across multiple receivers in the user base. However such capability must be traded off against the complexityXcsafely[WdWmWwW֋W֔WsaidWsameWsatisfiedRWsaysYWbWuWֈW֒WW[Wscalability WscalingsWscarceWscenariosZWcWlWvW֊W֓WQWschemesYWbWkWuWֈW֒W[WscopeWsecondaryTW]WfWpWփW֍WTWsectionXW\WaWeWjWnWtWxWևW֌W֑W֕WWWW W WWWHWMWNWSWsectionsWAbremoveoption1XVaVjVtVևV֑VAVXVYVZVremovesection[VdVmVwV֋V֔VV]V^VremovesentencestartingwithaqosbasedipnetworkVremovethedistinctionbetweenuplinkanddownlinkVV_VhVrVօV֏VVVremovethefragmentbedesignedinamannerthatdoesVremovetheipnetworkfromthemobilestationsideVremovethescalingfor1.25mhzfromthetableVremovethetextortoaswitchinglayeregpppmplsVremovethewordgenerallyfromthislineVVremovethissectionYVbVkVuVֈV֒V[VreplaceTW\W]WeWfWnWpWxWփW֌W֍W֕WTW_WTW]WfWpWփW֍Wso\WeWnWxW֌WspecifyUW^WgWqWքW֎Wspecify2bits/sec/hzasthespectralefficiencyandallowtUV^VgVqVքV֎VspectralUW^WgWqWքW֎W\cthecurrenttexthasthreeoptionsZVcVlVvV֊V֓VthecurrenttextreadstheaishallsupportbroadcastandmuTV]VfVpVփV֍VtheexistingtextofthissectionisvagueandthelanguageVthejointcontributionrepresentsaconsensusofmanypeopleVtheqosrequirementsegdiffservflexiblearqschemesetccaYVbVkVuVֈV֒Vtheqosrequirementsinthedocumenttodayegdiffservflexi[VthereasonwhytospecifythespectralefficiencyisenoughAVtherequirementaspreviouslywrittenallowsbroadcastviauVtherequirementismoreofanequipmentrequirementthananVtherequirementsarevagueandunmeasurablewerecommenddelVWքWևW֋W֌W֍W֎W֑W֔W֕WWthisrequirementspecifiesstringentspectralefficiencieswUV^VgVqVքV֎VthreeZWcWlWvW֊W֓WOWccaptured[WdWmWwW֋W֔W^Wcarried]Wcdma2000WconlyYWZWbWcWlWuWvWֈW֊W֒W֓WQW[WopenIWoperationUW^WgWqWքW֎WUWoperationalXWaWjWtWևW֑Woperator[WdWmWwW֋W֔WoperatorsLWoptimizedYWbWuWֈW֒W[WoptionWWXWZW`WaWcWiWjWlWsWtWvWֆWևW֊W֐W֑W֓WWNWPWQWRWSWWWXW\W)2 ֍cB of efficiently implementing this capability in a network setting. For example, this requirement complicates the use of antenna array systems that boost spectral efficiency through the use multiple of antennas that directively transmit towards specific users in the user base. Since it is not clear how to address such issues without further analysis, and since from a services perspective broadcast services are secondary to the ability to provide users with dedicated streams, this requiremenCt should be softened. d48 2004/05/11֎EMichaelF Youssefmir^Technical, Binding_11`10a4.1.1bSpecify 2 bits/sec/Hz as the spectral efficiency and allow the evaluation criteria to determine the conditions under which this is achieved.cV cALInclusion of an IP network on the MS side is confusing. Is this the same as the IP network connecting to the base station? Is it a private network? The Mobile Station is already connected to the IP network via the air interface. If this is supposed to convey a MS acting as a NAT, the concept is irrelevant to the air interface.Ld70.13g2481vDelete section 3.2w Superceded 2004/05/11s. Make informative.d69.12g2480 2004/05/11FNaguib, Sutivong, Tomcik_11`4a3.2b5Remove the "IP Network" from the Mobile Station Side.cequirement is on the upper layers. Make informative.d69.12g2480 2004/05/11FNaguib, Sutivong, Tomcik_11`4a3.2b5Remove the "IP Network" from the Mobile Station Side.ck" from the Mobile Station Side.cddress such issues without further analysis, and since from a services perspective broadcast services are secondary to the ability to provide users with dedicated streams, this requiremen25>֏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. d50 2004/05/11֐EMichaelF Youssefmir^Technical, Binding_13`13a4.1.5bAdopt Option 2cACurrent Text: OPTION 1: [ The aggregate data rate for downlink and uplink shall be consistent with the spectral efficiency. Example Aggregate Data Rates are shown in table 4-2) Parameter Aggregate Data Rates 1.25 MHz. @ 3km/hr 1.25 MHz . @ 120km/hr 5 MHz.@ 3km/hr 5 MHz. @ 120 km/hr DL UL DL UL DL UL DL UL Aggregate Date Rates (Mbps/sector) 2.50 1.88 1.25 0.94 10 5 5 2.5 Table 4 2 Aggregate Data Rates ] OPTION 2: [The aggregate data rate for downlink and uplink shall be consistenplicates the requirement - a single spectral efficiency will allow proposals to sensibly make the split between uplink and downlink. 2004/05/07֏EMichaelchael/1 ֎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.d49 2004/05/11֏EMichaelF Youssefmir^Technical, Binding_12`10a4.1.1b3Remove the distinction between uplink and downlink.OcbasestationTW]WfWpWփW֍WTWbeTWUWWWXWYWZW[W\W]W^W`WaWbWcWdWeWfWgWiWjWkWlWmWnWpWqWsWtWuWvWwWxWփWքWֆWևWֈW֊W֋W֌W֍W֎W֐W֑W֒W֓W֔W֕WWWWW W W W WWWWWEWIWOWPWQWRWSWTWUWXWYW[W]W^W_WbecauseUW^WgWqWքW֎WUWbeenWLWbefore[WdWmWwW֋W֔WWWbelieveW WWLWbelongWbelowIWRWbestLWqWքW֎WWWc802-20-04-33r1XWaWjWtWևW֑Wc802.20-04/xxoW։WcallWcanYW[WbWdWkWmWuWwWֈW֋W֒W֔WcapabilityTW]WfWpWփW֍Wcapable[WdWmWwW֋W֔WZccoded[WdWmWwW֋W֔WcombineHWcommentWWXWZW[W`WaWcWdWiWjWlWmWsWtWvWwWֆWևW֊W֋W֐W֑W֓W֔WWcommitmentsLWcompetingWcomplexityTW]WfWpWփW֍WTWcompliant WcomplicatesTWUWVW]W^W_WfWgWhWpWqWrWփWքWօW֍W֎W֏WTWUWVWcomplyWconceptWWXW`WaWiWjWsWtWֆWևW֐W֑WWNWYWZWconceptsW16 Y֐cBt with the spectral efficiency.] Comment: The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Option 2 is clear and specific and does not assume specific channel bandwidths.d51 2004/05/11֑EMichaelF Youssefmir^Technical, Binding_14`1a4.1.5.1bRemove Option 1cACurrent Text: Editors Note: There are two versions of text for this section to consider at the next WG meeting OPTION 1: [ The AI shall support peak per-user 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. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for design and operational choices. Average user data rates in a loaded aggregate data rate for downlink and uplink shall be consisten58 ֑cB system shall be in excess of 512Kbps downlink and 128Kbps uplink. This shall be true for 90% of the cell coverage or greater. Table 4 3 ] OPTION 2: [The AI shall support peak per-user data rates in excess of 1 Mbps on the downlink and in excess of 300 kbps on the uplink. These peak data rate targets are independent of channel conditions, traffic loading, and system architecture. The peak per user data rate targets are less than the peak aggregate per cell data rate to allow for designC and operational choices. 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.] Comment: Option 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 LTcunderUWYW^WbWgWqWuWքWֈW֎W֒WWUW[WunderwayWunicastWunmeasurableWWWWunnecessarilyUWVW^W_WgWhWqWrWքWօW֎W֏WUWVWunnecessaryWunnecessarytospecifyconfusesthemodelconceptsV69 +֑cDin practice. The concept of bandwidth must be clarified given that we are not requiring specific channel bandwidths. Additionally, the concept of two phases is ill-defined. zd52 2004/05/11֒EMichaelF Youssefmir^Technical, Binding_15`14a4.1.7bRemove this section. cAThe QoS requirements, 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 document requires a MAC lal 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 8; ֒cB'yer RTT of <10ms, ensuring the air interface can support low latency traffic under appropriate RF conditions. We recommend that the group not adopt specific packet error rate and latency requirements that would be arbitrary and only restrict possible service definitions in specific deployments.d53 2004/05/11֓EMichaelF Youssefmir^Technical, Binding_19`6a4.2.3bAdopt Option 3.cAThe current text has three options: Option 1: [The system is expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds. The system should support 95% (TBR) of the channel models with various delay spread values in each of the above environments.] OPTION 2: [The system is~curbanUWZW^WcWgWlWqWvWքW֊W֎W֓WUWuseTW]WfWpWփW֍WWWWAWIWOWTW]W֒Wuseful WuserTWXW[W]WaWdWfWjWmWpWtWwWփWևW֋W֍W֑W֔WWusersTW]WfWpWփW֍WvagueWWvaluesXWZWaWcWjWlWtWvWևW֊W֑W֓WvariousZWcWlWvW֊W֓WvaryWvehicularZWcWlWvW֊W֓WWWversionsXWaWjWtWևW֑WversusUWVW^W_WgWhWqWrWքWօW֎W֏WveryUW[W^WdWgWmWqWwWքW֋W֎W֔WviaWWwasWwayWweUWWWXWYW^W`WaWbWgWiWjWqWsWtWuWքWֆWևWֈW֎W֐W֑W֒WWWWWW WWW9= ֓cB expected to work in dense urban, suburban and rural outdoor-indoor environments and the relevant channel models shall be applicable. The system shall NOT be designed for indoor only and outdoor only scenarios. The system should support a delay spread of at least 5 micro-seconds.] OPTION 3: [The system shall work in dense urban, suburban, rural outdoor-indoor, pedestrian and vehicular environments and the relevant channel models shall be applicable. The system shall NOT be designed for indCoor only and outdoor only scenarios.] Comment: Of the three options, only option 3 is simple, straightforward, and well defined.^d54 2004/05/11֔EMichaelF Youssefmir^Technical, Binding_21`17a4.5.3bRemove sectioncThe system should support 95% (TBR) of the channel models with various delay spread values in each of the above environments.] OPTION 2: [The system isxcparameterWW`WiWsWֆW֐WparametersWWSWparityWparsLWpartWparticularWW]WpeakXWaWjWtWևW֑WDWGWXWpedestrianZWcWlWvW֊W֓WpeopleWperXWaWjWtWևW֑Wper-userXWaWjWtWևW֑WperformancekWLWperformsWperspectiveTW]WfWpWփW֍WWTWphaseNW;> ֔cACurrent Text: CPE 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 loaB:d has arrived safely at the CPE before deciding to switch from the old software load to the new software load. Comment: This 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 framework (d55 2004/05/11֕EMichaelF Youssefmir^Technical, Binding_21`25a4.5.4=֕bReplace requirement with a modification of option 3, as follows: "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."cvOptions 1 and 2 in this section are overly detailed with respect to specific statistics that need to be accumulated. d56 2004/05/11֖EMichaelF Youssefmir^Technical, Binding_18a4.1.13.5bPropose to add at the end of section 4.1.13.5: "The AI may use either a stream cipher (such as RC4 or AES in stream cipher mode) or a block cipher (such as AES in block mode). The use of AES shall not be mandatory."cSee contribution 04/56r1d57 2004/05/11stry standard codecs. Specific VOIP Codecs to be supported by the underlying QoS features include those specified by 3GPP, 3GPP2, and ITU-T."_ include those specified by 3GPP, 3GPP2, and ITU-T."_;canalysisTW]WfWpWփW֍WTWandTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWlWmWnWpWqWrWsWtWuWvWwWxWփWքWօWֆWևWֈW֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕WWWWWWW WWWWWWWW WBWEWHWIWLWNWQWRWSWTWUWVWWWXW[W\W^WfWpWփW֍WTWantennasTW]WfWpWփW֍WTWany WWIWanywhereW WappearsWapplicableUWZW^WcWgWlWqWvWքW֊W֎W֓WUWapplicationsYWbWkWuWֈW֒WapproachWWappropriateYWbWuWֈW֒WWWapprovedWWW WarbitraryYWbWuWֈW֒WFNaguib, Sutivong, Tomcik_9`4a3.1b'Change to read: ...AI shall provide...cPoor language - clean up.d62.5g2473j withdrawnw Withdrawnx#Not a significant change to clarityy Withdrawn 2004/05/11 33>wAcceptedy 21yes/0 no 2004/05/11FNaguib, Sutivong, Tomcik_9`4a3.1b'Change to read: ...AI shall provide...cPoor language - clean up.d62.5g2473j withdrawnw Withdrawnx#Not a significant change to clarityy Withdrawn 2004/05/11`5a3.1b*Change to read: ...AI shall efficiently...cPoor language - clean up.d63.6g2474jAv#1: The AI shall efficiently convey bi-directional packetized, bursty IP traffic with packet lengths and packet train temporal behavior consistent with that of wired IP networks. #2: The AI shall support the efficient delivery of bi-directional packetized, bursty IP traffic with packet lengths and packet train temporal behavior consistent with that of wired IP networks.v@+Nbreplacerequirementwithamodificationofoption3asfollo\VeVnVxV֌V֕Vreplacerequirementwiththeairinterfaceshallsupportthe_VreplaceshalltoshouldTVreplaceshallwithshouldTV]VfVpVփV֍VreportingSWrequiredWWrequirement\WeWnWxW֌W֕WWWWW_WresolutionWresourcesWrestateWrestatethisasaminimumperformancerequirementVretainPWretriesHWreuseHWreverseHWreword Wrewordasfollowstheairinterfacedesignshallscaletowi VruralQWsHWs0028HWsafelyHWsapWscale WscalingWsectionYW[WbWdWkWmWoWuWwWֈW։W֋W֒W֔W֖WWWWWWWWWW W WWWWWCWFWHWPWSW[W]W^WsectionsWWstationWsuggestionWAvYbsupport@the@those@under@fusing@c04/56r1@10ms@$2և#2.5@3@ 512kbps@Jabove@ai@analysis@?and3gpp2@architecture@area@atLaverage@pbackend@basestation@3better@Ocaptured@-cell@coded@4conditions@connected@dcould@DdataKdate@detailed@&dl@tefficiency@example@focus@framework@free@have@nhowever@imposing@indoor@interfaces@uparameter@ 33   33> 2004/05/11jcodecsWcommunicationsWconsistentWWWconveyWcoverageWWcurrentWdeleteWWWdeliveryWeWefficientWWefficientlyWeitheroWcingWentitiesWfeaturesWfiguresWforWgWgenerallyWhaveWieeeWWietfWillustratedWimplementedWinWWincludingWindoorWindustryWintendedWinterfaceWinterfacesWipWjitterWjustWlatencyWlayeredWWlengthsWlossWmacro/micro/picoWmakeWmayoWWmbwaWWmechanismsWmobileWWmulticastWneededWnetworkWnetworksWWnon-lineWnotWofWWWWWWWopenWorWotherWoutdoorWpacketWWpacketizedWperformanceWpossibleWprecludeWWFNaguib, Sutivong, Tomcik_8`17a3.1b9Change to read: "802.20 systems are intended to provide"cUThis sentence, almost a requirement is unmeasurable as written. Make it informative.d60.3g2471j802.20 systems are intended to provide ubiquitous mobile broadband wireless access in a cellular architecture (e.g. macro/micro/Pico cells). v802.20 systems are intended to provide ubiquitous mobile broadband wireless access in a cellular architecture (e.g. macro/micro/Pico cells). wAcceptedy 19yes/3no 2004/05/11FNaguib, Sutivong, Tomcik_8`18a3.1b1Change to read: ...802.20 system shall provide...c#Proper Use of Requirements Languaged61.4g2472jA#1: The 802.20 system shall support non-line of sight, outdoor to indoor scenarios, and indoor coverage. #2: The 802.20 system shall support non-line of sight including outdoor to indoor scenarios and indoor coverage. @vtheWWWWWthe802.20systemshallsupportnon-lineofsightoutdoortoVtheaishallsupporttheefficientdeliveryofbi-directionaVthembwashallprovideairinterfacesupporttoenablevoipVtheresolutionofqosintheaishallbeconsistentwiththeVthisWthislayeredapproachshouldbeconsistentwithotherieee8VthursdayoWtilloWtoWWWtrafficWtrainWubiquitousWuseWusingWutilizationWvoipWwhileWwillWwiredWwirelessWwithWWWwithinWwacceptedaccepted-modifiedsupercededwithdrawnveWefficientWenableWend-to-endWfeaturesWfiguresWgWieeeWinWWWindoorWindustryWintendedWinterfaceWintoWipWjitterWlatencyWlayeredWWlengthsWlossWmacro/micro/picoWmbwaWWmobileWWneededWnetworksWWnon-lineWofWWWWWotherWoutdoorWpacketWWpacketizedWperformanceWprovideWWqosWWremainWrequiredWresolutionoWWresolutiondeferredtillthursdayoVscenariosWscopeWsectionWWservicesWshallWWWWshouldWshownWsightWspecifiedWstandardWstandardsWsupportWWWsystemWsystemsWWtakingWtemporalWthatW@ ;jk)comment is to replace "must" with "shall"vAdThe 802.20 system shall support non-line of sight, outdoor to indoor scenarios, and indoor coverage.d@A> 33  33>wAcceptedxlanguage cleaned upy 21yes/0 no 2004/05/112FNaguib, Sutivong, Tomcik_9`10a3.1.1b(Delete the First Sentence of the Sectionc%Redundant with the Previous statementd64.7g2475jto delete: "Adopting current communications systems specification principles, 802.20 MBWA systems will be specified using a layered architecture. " #2: Just have: "802.20 MBWA systems will be specified using a layered architecture. "vF"802.20 MBWA systems will be specified using a layered architecture. "wAccepted-Modifiedy No objections 2004/05/11FNaguib, Sutivong, Tomcik_9`13a3.1.15jto delete: "Adopting current communications systems specification principles, 802.20 MBWA systems will be specified using a layered architecture. " #2: Just have: "802.20 MBWA systems will be specified using a layered architecture. "vF"802.20 MBWA systems will be specified using a layered architecture. "wAccepted-Modifiedy No objections 2004/05/11FNaguib, Sutivong, Tomcik_9`13a3.1.1 jkreplace "must" with "shall".vAThe AI shall support the efficient delivery of bi-directional packetized, bursty IP traffic with packet lengths and packet train temporal behavior consistent with that of wired IP networks.@Af 33  33  / 33fwAccepted-Modifiedxlanguage cleaned upy 18 yes/0 no 2004/05/11vairWandWWWWapplicableWapproachWarchitectureWWareWasWbeWWWbehaviorWbi-directionalWbroadbandWburstyWcellsWcellularWcodecsWconsistentWWWcoverageWdeferredoWdeleteWWdeletesection3.2VdeliveryWjprinciplesWprotocolsWprovideWWqosWWrc4oWreadWremainWremoveWrequiredWresolutionWresourcesWscenariosWscopeWsectionWWWservicesWWshalloWWWWWWWWWshouldWWshownWsightWsomeWspecificationWspecifiedWspectrumWstandardWstandardsWstationWstreamoWsuchoWsupportWWWWWWsystemWWWsystemsWWWtakingWtechnologiesWtemporalWtextWthatWWWtheoWWWWWWWWv802.20mbwasystemswillbespecifiedusingalayeredarchitV802.20systemsareintendedtoprovideubiquitousmobilebroVaWWaccessWaccountWaiWWaiutilizationVgb>Remove the text: ...or to a switching layer(e.g. PPP, MPLS)...c5Unnecessary to specify. Confuses the model concepts.d65.8g2476w Withdrawny Withdrawn 2004/05/11FNaguib, Sutivong, Tomcik_9`15a3.1.1b+Remove the word "generally" from this line.c6"generally consistent" is an unmeasurable requirement.d66.9g2477jAj#1: This layered approach shall be generally (remove) consistent with other IEEE 802 standards and shall remain generally within the scope of other IEEE 802 standards as shown in figures 1 & 2. #2: This layered approach should be consistent with other IEEE 802 standards and should remain within the scope of other IEEE 802 standards as shown in figures 1 & 2. j@A 33# 6 33   33  33ksimplifies the textv]j1changetoreadieee802.20-basedsystemsshallsupportbroV1deletetextthesystemshallsupporttheuseofcoverageeV1movesection4.1.12tomakeit4.1.7andsection4.1.7isV1thislayeredapproachshallbegenerallyremoveconsistentV2WWWWWW2thislayeredapproachshouldbeconsistentwithotherieeeV3W3.2W802W802.20WWW802.20systemsareintendedtoprovideubiquitousmobilebroV802.20-basedWaWWaccessWadoptingWaiWWairWandWWWWWWanyWapplicableWapproachWappropriateWarchitectureWWareWWasWWbaseWbeWWWbehaviorWbelowWbetweenWbi-directionalWbroadbandWbroadcastWburstyWcellsWcellularWchangeW jA 33   33  33  33@FNaguib, Sutivong, Tomcik_9`5a3.1b*Change to read: ...AI shall efficiently...cPoor language - clean up.d63.6g2474jAv#1: The AI shall efficiently convey bi-directional packetized, bursty IP traffic with packet lengths and packet train temporal behavior consistent with that of wired IP networks. #2: The AI shall support the efficient delivery of bi-directional packetized, bursty IP traffic with packet lengths and packet train temporal behavior consistent with that of wired IP networks.v@ |jAf 33 # 33  33f0FNaguib, Sutivong, Tomcik_11`4a3.2b2Change to read: Any network interfaces may use...cEAs written the requirement is on the upper layers. Make informative.d69.12g2480jA#1: Any interfaces that may be implemented shall use IETF protocols as appropriate. Some of the possible interfaces are illustrated below. #2: Open interfaces: The AI shall not preclude support for open interfaces between the base station and any upstream network entities, or the use of IETF protocols as appropriate for these interfaces. Some of the possible interfaces are illustrated below. #3: Delete section 3.2v#3: Delete section 3.2wAccepted-ModifiedxVDiscussion of details in later sections, this section is redundant and/or out of scopey No objections 2004/05/11FNaguib, Sutivong, Tomcik_11`4a3.2b5Remove the "IP Network" from the Mobile Station Side.cons 2004/05/11jthisWtoWWWWWWtodeleteadoptingcurrentcommunicationssystemsspecificatVtrafficWtrainWubiquitousWupstreamWuseoWWWWWusingWWutilizationWvoipWwhileWwillWwiredWwirelessWwithWWWwithdrawnwithinWkaWandWasWcommentWWcommentistoreplacemustwithshallVeditorialWinsteadWintroducesWisWWlastWmustWWofWredundantWreplaceWWreplacemustwithshallVsecondWsentenceWshallWWsimplifiesWsimplifiesthetextVtechnicalWtextWtheWWthelastsentenceisredundantwiththesecondsentenceandVthisWtoWwithWWWmacceptedW3deletesection3.2V3.2WW802W802.20WWWgx^We can't change the diagram. The standard will address the details of the 802.20 architecture. 2004/05/111j1the802.20systemshallsupportnon-lineofsightoutdoorV1theaimayuseeitherastreamciphersuchasrc4oraesioVaishallefficientlyconveybi-directionalpacketizedV1thislayeredapproachshallbegenerallyremoveconsistentV2WWWWWW2thislayeredapproachshouldbeconsistentwithotherieeeV3W3.2W802W802.20WWW802.20systemsareintendedtoprovideubiquitousmobilebroV802.20-basedWaoWWWaccessWadoptingWaesoWaioWWWairWandWWWWWWanyWapplicableWapproachWappropriateWarchitectureWWareWWasoWWWbaseWbeWWWbehaviorWbelowWbetweenWbi-directionalWblockoWbroadbandWbroadcastWburstyWcellsWcellularWchangeWcipheroWPCHb1XWaWjWtWևW֑WWAWLWXWYWZW1.25W1000HW100msOW12W2UWWW^W`WgWiWqWsWքWֆW֎W֐W WDWEWHWMWRWUWWW2ndW3ZW\WcWeWlWnWvWxW֊W֌W֓W$c04/56r1֖W1WWXWZW\W`WaWcWeWiWjWlWnWsWtWvWxWֆWևW֊W֌W֐W֑W֓W֕WWLWNWRWXW1.0LW1.25WW`WiWsWֆW֐WWOW1.5LW1.88WW`WiWsWֆW֐W10WW`WiWsWֆW֐W10:1XWaWjWtWևW֑WXW'։bPropose to add at the end of section 4.1.13.5: "The AI may use either a stream cipher (such as RC4 or AES in stream cipher mode) or a block cipher (such as AES in block mode). The use of AES shall not be mandatory."c!See contribution C802.20-04/56r1.d44g2222 2004/05/11>FNaguib, Sutivong, Tomcik^ Editorial_8`10a2.1bA_Change to read: "The MBWA shall provide air interface support to enable VoIP Services. QoS Features shall provide the required performance of latency, jitter, and packet loss needed to support the use of industry standard codecs. Specific VOIP Codecs to be supported by the underlying QoS features include those specified by 3GPP, 3GPP2, and ITU-T."_^pEMarcFGoldburg^Technical, Binding_8`12a2.2bReplace "shall" with "should".cd".c #ojA#1: "The AI may use either a stream cipher (such as RC4 or AES in stream cipher mode) or a block cipher (such as AES in block mode). The use of AES or RC4 shall be optional." #2: "The AI may use either a stream cipher (such as RC4 or AES in stream cipher mode) or a block cipher (such as AES in block mode). Neither the use of AES nor RC4 shall be mandated." #3: "No particular encryption algorithm is mandated."@A  33    33    336  i  v!resolution deferred till thursdayThere has been a request from one member for additional time to put in additional comments for this section. Bring this comment back on Thursday. 2004/05/116jenableWencryptionoWend-to-endWentitiesWfeaturesWfiguresWforWgWgenerallyWhaveWieeeWWietfWillustratedWimplementedWinoWWWWincludingWindoorWindustryWintendedWinterfaceWinterfacesWipWisoWWitWjitterWjustWlatencyWlayeredWWlengthsWlossWmacro/micro/picoWmadeWmakeWWmandatedoWmayoWWmbwaWWmechanismsWmobileWWmodeoWmoveWmulticastWneededWneitheroWnetworkWnetworksWWnooWnon-lineWnoroWnotWofoWWWWWWWWWopenWoptionaloWoroWWotherWoutdoorWpacketWWpacketizedWparticularoWperformanceWpossibleWprecludeWj1theaishallefficientlyconveybi-directionalpacketizedV1theresolutionofqosintheaishallbeconsistentwithtV2oWWWWWWW2thislayeredapproachshouldbeconsistentwithotherieeeV3oWW3.2W4.1.10W4.1.12W4.1.7W4.1.7.1W802W802.20WWW802.20systemsareintendedtoprovideubiquitousmobilebroV802.20-basedWaoWWWaccessWaccountWadoptingWaesoWaioWWWWairWalgorithmoWandWWWWWWWanyWapplicableWapproachWappropriateWarchitectureWWareWWasoWWWbaseWbeoWWWWWbehaviorWbelowWbetweenWbi-directionalWblockoWbroadbandWbroadcastWburstyWcellsWcellularWchangeWcipheroWmaccepted-modifiedv1W2W3W3deletesection3.2V3.2WW802W802.20WWWbx\Historical reasons - request from KT in Singapore meeting, proposed to include this section. 2004/05/11FNaguib, Sutivong, Tomcik_17`16a4.1.11bDelete the section.cThis requirement is an equipment requirement, not an air interface requirement. It may be appropriate to re-introduce in the specification drafting stage, as appropriate.d85.28g2496mAcceptedwAcceptedxThe group elected to delete this section, however if needed members can bring comments to reintroduce the section with new wording.y|This section (4.1.11) was included by Sprint, since there was no discussion/resolution on this, the brackets have been used. 13 yes/2 no 2004/05/11FNaguib, Sutivong, Tomcik_17`20a4.1.12bAModify 2nd sentence in the section as: "The resolution of QoS in the AI shall be consistent with the end-to-end QoS in the core network, while taking into account AI utilization."@customer subscription and provisioning parameters.SFNaguib, Sutivong, Tomcik_17`20a4.1.12bConsolidate all QoS SectionscQos is mentioned in many places in the document. We recommend consolidation of these so that it is easier to interpret and comply with QoS provisions in the AI.d87.30g2498jL#1: move section 4.1.12 to make it 4.1.7; and section 4.1.7 is made 4.1.7.1y]Write up the sequence of sections in section 4.1, that can come together as QoS requirements. 2004/05/11s QoS requirements. 2004/05/11 bcThis section says the core network drives the QoS allowed. Reword so that the air interface conditions, the scarce resource in the end-to-end model can influence and drive the QoS, consistent with customer subscription and provisioning parameters.d86.29g2497jA}#1: "The resolution of QoS in the AI shall be consistent with the end-to-end QoS, while taking into account AI utilization."}@A>  33R  |  33>vAz "The resolution of QoS in the AI shall be consistent with the end-to-end QoS, while taking into account AI utilization."z@A>  33O  y  33>wAccepted-Modifiedy 14 yes/3 no 2004/05/11 TbA>  33    33>cbmodify2ndsentenceinthesectionastheresolutionofqosVmonitor\WeWnWxW֌W֕WHW_WmonitoringHWmoreWmplsWmsecsHWmulticastWmustWWHWnecessarySWjenhancingWentitiesWfeaturesWfiguresWforWgWgenerallyWhaveWieeeWWietfWillustratedWimplementedWinoWWWWincludingWindoorWindustryWintendedWinterfaceWinterfacesWintoWipWisoWWitWjitterWjustWlatencyWlayeredWWlengthsWlossWmacro/micro/picoWmadeWmakeWWmandatedoWmayoWWmbwaWWmechanismsWmobileWWmodeoWmoveWmulticastWneededWneitheroWnetworkWnetworksWWnooWnon-lineWnoroWnotWofoWWWWWWWWWopenWoptionaloWoroWWotherWoutdoorWpacketWWpacketizedWparticularoWperformanceWpossibleWprecludeWj1thislayeredapproachshallbegenerallyremoveconsistentV2oWWWWWWW2thislayeredapproachshouldbeconsistentwithotherieeeV3oWW3.2W4.1.10W4.1.12W4.1.7W4.1.7.1W802W802.20WWW802.20systemsareintendedtoprovideubiquitousmobilebroV802.20-basedWaoWWWaccessWaccountWadoptingWaesoWaioWWWWairWalgorithmoWandWWWWWWWanyWapplicableWapproachWappropriateWarchitectureWWareWWasoWWWbaseWbeoWWWWWbehaviorWbelowWbetweenWbi-directionalWblockoWbroadbandWbroadcastWburstyWcellsWcellularWchangeWcipheroW UcBs 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.d2yThe comments on this section (4.1.1) remains unresolved, as there was 80% support in March Plenary , and in this meeting there is no quorum either. 2004/05/11