Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0)@0inding@cthenormativereferencesectionisblank@@00allowedtheconcatenationoftheseparat@@0coincide@entity@inserttheworddownlinkbeforemodeaandotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijkQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJ>@ Cj%7.hal e-iJ.hj -Ek. l`l -mFxrogermarkspQmarksprogermarksBRmarksBrogermarksTmarksrogermarks@Umarks@roger marksmarksroger marks( i marks!(!roger  marks"0#q#marks$"0$ marks( i marks!(!roger  marks"0#q#marks$"0$DTDT €Editor's NotesEditor's Questions and Concerns€AEditor's Action Items€A€A€A Starting Line #€A Section€A  Fig/Table# BA1BAj  !"#$%&'()*+,-./0234567j^_ `2a4bc d ijkmn.p+v"wx#y'{)€%€0€€€€1€€66leiOwang' *  wang * leiP wang wang ' leiQ wang VYwang VleiRwangwang YleiSwang wang leiTwang@nh&`wanghleiUwang€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   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 PM9 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  ABCDEFGHdIJ^K_L`MNaObPcQiRmSjTkUvVwWxXyYZ{[p\n] ~֗֞!"#$%&'()*+,-./012345689:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^`abcdefghijklmnopqrstuvwxyz{|}~׀ׁׂ׃ׄg^_`€€€€€'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\{]^_`abcde0UAbfollowing@cbring@not@to@jbereplacedwithupperlayers@sourceidentifiershouldbeprefered@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)b@B@2@I.@u@P;;;;P;;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 PMBkS-X bWmkwj,AvCgE@!Sl€`zrAPFQKRPSUTZUBN@VhA~@M@LZ<>C @@@FIH@JQ3^&vmBD€Qd9naD@Xbm{ACEe@EJoQTYB@X|CE@€ JOTYAC@XbmwBD@a@EJOU[B@|J& JQ 3 $,.YesNo/,  , : AM PMS   U   V   W   X 3 $,.YesNo/,  , : AM PMY   Z 3 $,.YesNo/,  , : AM PM[   \ 3 $,.YesNo/,  , : AM PM]   ]   No/,  , : AM PM]   1 RG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMw+#,v# 0x#  2 Ma bc dijkmvwxy!€€$€2'&()% @@@B s@A 3  $,.YesNo/,  , : AM PM77777777 7 7  7  7  7 7 7777777777771xy{€€€€€j77777777 7 7  7  7  7 7 7777777777771        Y7 ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   6" i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv    €Dtch of records in which you want to replace a field. *In browse mode, and put the cursor in the "Recommendation by" field. *Under "Records", choose "Replace". *Choose "Replace with calculated result". *In the box, write, in quotation marks, your name. Click "OK". *Click "Replace". @Af  ww    ww  ww  wwfSet up an email message for meGo to "Comment List" layout BnA€ (~EEric FNJEDJOU^Technical, Non-binding_26a5.3.1bu Take out the figure of the specification This figure is to be replaced by the General Communication Reference Model c>Figure 2. This figure does not bring much clarity to the text.d14vRe-Submit with proper fieldswRejected{l) none needed2 2005/12/07 2005-09-142 ֗EEric FNJEDJOU^Technical, Non-binding_41`25a6.1.240n 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  33fPI3Import 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=>gP:@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=ACeric@@^non-binding@technical@technicalnon-binding@_`‚6@a5.3.1@b16@3gpp-defined@5.4.2.2@Q7.2.15.1@7.4.6.2@above@Kaccess@acquired@Xaddthefigurelocatedinsection2.3inthefile21-05-0xxx@Zalthough@and/or@|annexes@Fasynchronous@@be@can@`commands@configure@,could@/dcn@device@5effect@entities@Rexpanding@figure@pletely@letely@etely@0completely@n@links@(measurement@9message@multiple@Jon@ only@uparameter@queryresourselist@nreference@replacecurrentsection5.3.2bythesection5.3.2indcn21@greports@/sdo@_subsectionsuch@termination@ this@ttransport@!values@Sweb@2 BD VOTEREMAILpDs`jA.nA%€B?€A€ACC@==========6_BdD`@4AFF*KL)QaA0@./////./////qq@@jAqcA%jBDkBZq@<jUq@q@qcMq@qcjqHBq@l_qkCq@qbAjBqjAfkAgq@vqcqboq@Pq@Giq@qPqjA q@qbq@abAqcr@Or=^6r@GprB@jA|rE@N^HrHPqrR@rSbjrT@jSril1rt@'r@Irl4r@bAjB[kA\ 2002-04-15Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15  w  $,.YesNo/,  , : AM PM  w AaBSn DyRoxp zqr srtyuB+zy*{QbSzaq@Hg@@PB s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMXY!€aACommentary Version@A* ww  ww*}Commentary Version # Version NotesCommentary Version Date B A€€€888r ysrtyuB+zw*{EV|GIU}n~pI~YjR[7iaGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #fFJ I 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK w  $,.YesNo/,  , : AM PMA%x  Yx% ^%  _l%@ l`l@% j%0  al0% cl%  bl@GY^6i7w"#$A=CEw€\€a@5BG4M1R/YOAC+'@€BD8, consequtive in time, of a preamble and data subchannels. --------------------------------------------- 8.3.6.3.5.2.3 should be handed to a clause-editor to be entirely rewritten. ItC needs substantial additional information on how to do this type of rotation in TDD, and it shouldn't use the word frame for allocations. How it will fit under the MAC etc.. (i.e. it needs definition on how this shifted superframe structure fits in with TX/RX boundaries)cH3  @BBA^_`abc€XXXXXXXXACreate and Submit BallotB    E 3 $,.YesNo/,  , : AM PMF 3 $,.YesNo/,  , : AM PMG 3 $,.YesNo/,  , : AM PM'   ^AAssign EditorsE 5 4 3 2 1 0 / . -  ,  *  )  (  ' & % $ "    !Q7AShow All Records in OrderE '` dDTQ8A Export Clause Editor's ProposalsE OFMPR$@` ABCdD^EiFmGjHkQ9A Import Clause Editor's ProposalsE NALL OTABSW@# `BBXXXXYYYYZZYYZZp` "Guillemette" GuillemetteQAAssign Editor 11E@[@!r@a11.@a11.@!r@a11.@802.16.1/D1-2000Q`"11"^52_ 8.2.1.2.5n'tuWdownstreamuWexistuW6M<?ACreate CommentB    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM   X , : AM PM      ~LA+Commentary: The IEEE 802.16 Comment ManagerA*by Roger Marks *@A> ww ) ww> AICreate and Submit Working Group Ballot or IEEE Balloting Center CommentsI@AR  33& + RN#Version: <<ACIABB>> (<<ACIABG>>)OView Comment ListA5For help, see 5@A> ww 4 ww>Xhttp://WirelessMAN.org B A   €€A>  ww    ww>AGo To Create Vote Page@A> ww  ww>UV sBl#. .#  al# cl#  bl# Bmv#  @iv# sj{#v Dkvv# 8w#f,Cjvf# 0x# V  2y V# 2 # F 6{ F# In # 6 qp 6# 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#x x#  #; d;# ##+ #+# ## # ^ #k  _lk#  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€ ++++++++ + +  +  +  + + +++++++++++++X5XX/X1XXXX X3 X X  X  X6X XXX$X"X X&XXXX,XXXX)X+-*,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 XXXXXX9 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 GL2222iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. ,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl#.  .#  al# bl# 8w#,v#  2y# 2#v 6{v# In#f qC>pf# L WE@@MarkedQYAExport IEEE XMLEOTABS D[@!d$@`@A14[p 0 h[[ [[ /0 h[p / AQ^AOpen Reply Comment FileE ! FMPRQ'`QdDTQAzHHddE(HH(d'`zA'dE7*`'`+ dDTQ] w  $,.YesNo/,  , : AM PM  UU? €Ad?2     _` a ^@"7 c>gt;Z<lt;Z b>gt;Z<lt;Zd W2&&Zgt;>Zlt;<Z:GC€A VoterMemberIDB G€A ReportNumberB G€A FigTabNumberB G ajayrajkumar@lucent.com 1IEEE 802.21 Comment Resolution for P802-21-D00-02 vivek.g.gupta@intel.com P802.21D00.031.55€1.55€mAComment 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    C iTkTlGTPmn{Tn{ng{Po pw~Tqpn{_PrP{T|DnP}T~5ETy(5P#3"$1"2$L63C#0 AS T3C|U#3}C<V#3ACWDGW#X^H_UYGpW \_lHUn]GW ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$Tgvhz@@ B s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM xe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes€ADocument under Review:€ABallot Number:€A Comment Date€A€A  Fig/Table# BA(B$AP  !"#$%&')*P^_` a b dnpvwy {€€€$€"€&€(€€))f1234f01234f1234f1234f/@@ B s@A 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM$,.YesNo/,  , : AM PMo RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM MaSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uA vRecommendation by€wA xRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A Fig/Table# BAN  !"#$%&N^_`a bc dijkmvwxy!€€$€%%f1234f1234f1234f1234f1234f-./01234fo ZQ 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM T 3 $,.YesNo/,  , : AM PMU  3 $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PM OY 3 $,.YesNo/,  , : AM PMZ 3  $,.YesNo/,  , : AM PMA#x  x#  #h #h# ##X #X# # d# ^ #k  _lk#  `  @BBA* *^_` a b dnpvw y{€€€€€€           XX(X$X"XXXX& X X X X  X)X X XXX XXXXXIn # u L u#  @BBA( ( DmvkPx QdTykv zX{cTyKXPTwbk_+j)€UA€VA€XAYType€ZA [Suggested Remedy€\A]Page€^A_Line€`A ~PmRbapwcTsjtbTuiv4PvCTw A#x x#  #; d;# ##+ #+# ## #9  _l9#  `l# B#t  alt# ^# cl#  bl# Bmv#  @iv# >j#v Dkvv# 8w#f, EJG?W]IV<fS // €TA€UA€VA€WA€XA YType€\A ] Starting Page€^A _ Starting Line€`AaSection€bAcSuggested Remedy€dA  ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$Tgvh| AS T3C|U#3}C<V#3ACWDFoVX^HBUlY=TZbe[EmU \_BlHUh]WTbcHU3c3IC dd5BDe5Bf 0""/1"L1 B+``al)a,aTbc -6cI dd De ]fccTgvUbhT[biCHcTjxPkcTl~PmRbapwcTsjtbTuiv4PvCTw X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   ANU#OV#V+X^5)SYcTZbh[ +( \_l) ]I+g ^`l*)I_|  3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM       3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM 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 DataI֗b!_"@b#@#$c%@'b)v*@"+@-@2v 5b!8@"a9bB$:cA%;bA'cA(EbABC;GbCIbAHEJbBJDOKbAPLbATCVNbAWObYQ@[cA]S@\TckWcZ_[@abAeCdEcGbIg\bAhCfE]bAnCj^bAoCpEi`@q^sabAvCwEuArxdbAtebACcA}gbA~hbAibBAkbAAlbBAnbAco@cBpcAqb@FJeeׅ׀ׁׂ׃ׄwxyzDEFGHIJKLMNOP֫֬ke %  e ericnjedjoun   BFQd(    ericnjedjouo  Bericnjedjour Fericnjedjous Qericnjedjout dericnjedjouub4ericnjedjouwbericnjedjoux(5ericnjedjouy(ericnjedjouz{ H!6!" H"ericnjedjou|!#$7$%#%ericnjedjou~$& 'D'(& (ericnjedjou֎')Y*F*+)Y+cfor֗W֞W!W"W#W$W%W&W(W)W.W/W0W8W9W:W;W?W@WCWGWJWQWRWSWTWUW]W`WoWpWtWuWvWwWxWyW{W|W}WW׀WׁWforremotemihcommandsintable-3thatarebi-directionaltvVforceJWformoWformat|WformatsuWfourthEWfourthparagraphhastotakeintoaccountnewlydefineduppeEVfragmentsrWrWrWWWWfunctionalitiesjWfunctionalitymWWWfurtherֹWּWWgWWgeneralWWWWWWgeneralnetworkinformationgniandhigherlayerinformationVgenerallynWgeneratedWgeneric֕WWgivenWWgniWWgooWrWgoingWgreaterWgroupsWhandwWhandoff{W֜W֝WWhandoverwW{W֧W֬W֭W֮W֯WWWWWWWk^_ y‚%@`‚*!"S‚1#‚2$(‚3%T‚4&U‚5)AK‚68‚7~VWX‚8;L‚WM‚X3NO‚Y֞2‚Z45Ph‚ez‚f+,]‚g-‚ip‚jq‚qbr‚rQcdi‚sfjks‚tlmn‚u׀‚vׁ‚:‚t‚v‚[‚w‚^x‚R‚{‚|Ã!ׂÃ! ׃Ã!ׄÄ66‚s‚u‚֧‚֦‚֪֨֩֫֬‚‚֭‚֮֯‚‚ְ‚ֱ‚‚‚‚ֲ‚‚‚ֳ‚Ã"pÃ#Ã#0Ã#@Ã$0Ã%P` ԃՃ׃؃@֘p։֓֟ywo‚!jցւְ‚"‚#kփք֣‚%֨VQccomment֗W֞W;Wcommentmanagementframesonlyexistfor11֞Vcomments!W*WcommitׂWcommunication!W`WcompletelWmWnWconfigure0WtWconfirmWׁWconnected=Wconnectivity=W?WAWconsideryWconsideredvWconsistency}WconsistentoWV~Vweshouldnottalkaboutaspecificarchitecturethe~V~V~Vntweshouldnottalkaboutaspecificarchitecturethe~V~V~Vuldnottalkaboutaspecificarchitecturethe~V~V~Voutaspecificarchitecturethe~V~V~V~V~V~V~V~V~V~V~V~Vaboutaspecificarchitecturethe~V~V~V~V~V~V~V~V~Vntweshouldnottalkaboutaspecificarchitecturethe~V~V~V~V~V~Vntweshouldnottalkaboutaspecificarchitecturethe~V~V~VV~V~V~V~V~V~V~V~V~V~V~V~V~VWWWC €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. s 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 -9bwith֞W!W"W#W$W%W&W*W8W9W;W<W>W?W@WAWBWCWDWEWHWIWKWLWMWaWbWcWjWmWnW{W|W׀within?WEWJWwithoutEWaWword,Wwould;WxEWxxxoWyEWEWWsiWWWWWWWWWWWsiWWWWWWWWWWWWWWWWWWWWWWWWWWWWW22WW23WW255W26W3֏WֶWַWָWֹWֺWֻWּWֽW־WֿWWW4WWW5W5.3.3֡WW5.6W6ֵWWW6.1.5W6.2.5.1֟W6.3.1W6.3.3.1W7WWW7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.4.10.2֭W֯W7.4.10.2.4֮W7.4.11.2.2W8.3W8.4W&cdoes~WJWyW|W~Wdown-WsWׂWdraft`WaWeW}WduplicatedׂWduring׃Wdynamic:W<We:WAWoWpWqWrWsWvWeachWׁWeditor'saWeWeditorialzWeffectvWeg:Weither:W:WWWWWWWWWWWWWWWWWformationeoWօWWWWWWWWWWWWWWWWWWWWWWWWenablerslWenhanceWenoughpWWentireWentitiesWentity։WequallyWequipementsִWerrorWes/csִWessentialmWestablishingWethernetWevenzWքWevenaftersecureassociationtheeventscommandsandinformzVeventքW֚W֜W֝WWWWWWWeventszW֗W֛WWWWWWWevery֤Wexactly{Wbspecification~WLWspecifies0Wspecify2W8WspecifyingkWspeed0W<WssessionlWstack?WJWNWstacks?WstagePWstandard8WstartkWstate?WCWaWeWstated5Wstateful[W\Wstateless[W\Wstatic<Wstation]Wstatus<W?WAWLWaWstillaWstopnWstoreyWstrength0W<WiWWowWWWWWWWWWWWWWWwWWWowWWWWWWWWWehowWWWWWWWWWWWWWWWWWWWWWWWWWWWwWWWWWWWsomehowWWWWhowWWWstartingWWWWstateWstationWstrengthWstrictlyWstringWstructureWsubWsubsectionI?breplaced~Wreport:WeWreportingAWreports9W;WrepositoryyWrepresentation.W9WrequestJWRW^WhWkWpWqWrWsWuWwWxWzWWׁWׂWׄWrequestthatanewparametertoindicatethetypeofparametqVrequestthattwonewparametersareaddedtotheparametertpVrequesttoreconsidertheusecasesformihnetworkinformatxVrequesttoremovesection7.2.13and7.2.14andrespectiveerVrequesttoremovesection7.2.157.2.16and7.2.17andrespesVuter^WrunningiWsameCW]Wsap5W^WscanRWschema.Wsdus?WsecondCWsection(W*W.W1W3W4W5W:W<WFWGWHWLWMWNWOWPW[W`WfWsection74W5Wsections,WsecurityCWseeoWsegmentsdWselectIWselectivelyIWaWsendingkWsendskWsentLWRWbstrike֗Wstrikethesentenceout֗VstronglyeWstructure9Wsub-sections.WsubmittedSWTWUWVWWWXWYWZWsubnet]W^Wsubscribe/WsubsequentJWsuccessaWsuccessfuldWsuccessfullyaWsuch'W9W<W?WCWLWaWiWyWsupport+W8W]Wsupported1W\WׁWsupportedcommandlist׃Wrtedeventlist׃Wsupportedtransportli׃WsupportingCWswitchJW׀WswitchoveriWsynchronous;WeWgWsynchronousl2iWlWsynchronously=Wtable*W1W2W6W>WoWpWqWtWtable-1/WoWrWtable-10ׁWtable-8Wtables*WeWoWsWuWtake~WDW^WkWtakeoutthefigureofthespecification~Vtaken?WtargetaWnWtbd]WtechnologyLWterminal<W?WCWJW[W\WyWterminal/network<Wterminals;WterminateEWFW  btextthanaWeWthat0W?W@WAWCWEWIWJWLWNWOWaWdWeWiWlWnWpWqWthe~W֗W֞W!W"W#W$W%W&W'W(W/W0W1W5W8W9W:W;W<W=W?W@WCWDWEWFWGWHWIWJWKWLWMWNWOWPWRW[W\W`WaWeWfWiWkWlWnWoWpWqWrWsWtWuWvWwWxWyW|W}WׂW׃WׅWWWWWWWWWWWWWWWWWWthefollowingnewdefinitioncoversthecasewherethemobilּVthefollowingnewdefinitionemphasizesthedistinctionbetwֶVthenewpointofattachmentdefinitionreplacescurrentdefiֹVthe11thWtheirWthemWthenWthereֹWWWthereare3waystosolvethisVtheseWWWtheyWthingW<bfigure~W!W"W#W$W%W&W*W3W@WBWEWGWHWMWNWOW~Wfile>W@WBWGWHWMWOWfilteringAWfirstCWaWfixed5W?Wflag\Wflow?W@WJWflowslWflushaWflushedaWflushingaWWցWfinepWpWpWinepWpWepWpWpWpWfinepWpWnepWpWpWpWfinepWpWinepWpWnepWpWWfinepWpWpWpWpWpWnepWpWpWpWpWWfinepWpWpWpWinepWpWflagWWflagWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWca֗W!W"W#W$W%W&W'W.W0W8W9W:W;W<W=W?WGWJWLWNWOWPW[W\W]W^W`WbWcWdWjWmWoWrWsWtWyWafigurerepresentingupperlayercommandsisneededtoilluOVanewmihsappremitivesinmihhandoveraddressinformation^VanewsectionlistingupperlayercommandsisneededPVasectiononmihupperlayercommandsisneededNVable?WDWaboutDWRWpWyW_WaWdWfWjWrWցWօW֙W֚W֜W֝WandzW֍W֎W֏W֠WanotherRWbWgWanywhere֚WarchitecturejW}WarepW֏W֟WasOW_WdWmWrWsWtWzW}W֗W֩W֪W֬W֭W֮W֯Wassociated֌WassociationoWzWbasedxWbbbbbchbejWmWnWwWxWzW~WWրW֌W֕W֗W֙W֠W֣W֥WֱWM/bprotocols֞WCWDWprovideIWJWuWprovided<WIWLWSWTWUWVWWWXWYWZWtWprovides9WAWIWprovidingaWpurposeyWpush9W;Wpush-to-talk\WqualityAWquery;WwWquery/response9W;W\WqueryresourcelistwWqueuesaWquicklyaWr1/Wr2/WradioLWaWrange[W^WwWrate0Wrc-Wre-fragmentationaWre-tagaWre-verificationnWreadynWrealaWreceiptkWnWreceive1W;WCWDWIWiWlW{WreceivedaWdWreceiveraWreceiving1WlWreceptionnWrecipient?WJWrecipient'sDWreconfiguration]WreconsiderxWrecv-Wreduce?WreducingiWEWregistration?WIWregular;W=WaWeWrelated;WeWrelationshipEWrelay?WJWrelevanceeWrelevantKWeWreliabilityDWrelyaWI ^DT ABCDEFGdHkIJK^L_M`NaObPcQRSTUVgWX Y Zm[n\p]v^w_x`yabjcd e{fghijklmnoiof data packets between the mobile node and the network." Comment: How can you determine before hand that the handover will be" break before make" or "make before break"? d15vNo specific text proposedwRejected 2005/10/28 2005-09-14xE Eric NJEDJOU^Technical, Binding_23`51a5.1.3bRemove the original text.c09-14xE Eric NJEDJOU^Technical, Binding_23`51a5.1.3bRemove the original text.cformation on its detected neighboring networks and selects a link (possibly out of many available) to establish network-layer connectivity." Comment:This is a wrong definition.  d145-09-14rE Eric NJEDJOUbnetwork֞W<W?WCWJWLW[W\W^WaWeWkWvWxWyW׀WׁWׄWnetwork-controlled8Wnetwork-initiated8WnetworkanaWnetworksLWyWnew)W:W?W[W\W]W^W`WaWiWpWqWtWuWwWnnodeaWno-WIWPW]W{WWׁWׂWnomihmessageidentifiermihopcodecategoryׂVnoprimitivesopcodeservicecategorydescriptionVׁVnode?WCWaWbWcWjWkWmWnormalnWnormallyaWnot*W?WCWDWEWNW\W]WaWeWiWlWxWyWnoted'WNWnotesaWeWnoticeableaWnotification0WdWnotifications1WCWIWnotifyinglWnWnpoa]W^WnumberLWSWTWUWVWWWXWYWZWnumbers3WobtainsyWoccuraWoccurredeWoccurrenceaWeWoccursaWiWohbaWWW cbebeaconpWbecauseQW׀WbederivedpWbeen`Wbefore.WCWbehavior|Wbelong׀WbetweeenQWbetween!W<W?WQWsWyWbi-directionalvWbidirectionnality?WbindingJWbothoWuW׃W׃W cnotnotationoWnote<WaWeWnotifications0WnotifyrWnumbers3WobjectivesyWobtainedsWobtainsyWof!W*W+W-W2W9W:W;W=W?WKWLWQWRW\W`WaWeWfWgWhWiWlWnWoWpWqWrWsWvWwWyW|WW׀WׁW׃WoldqWon)W*W4W5W9W:W?WNWpWwWone}WWׁWones!W!Wab0[W1=W>WAW[WoWWׁW1linkeventdiscoverrequestconfirmeventV1.2yW10gW10linksynchronouslinkhandoverproceedinggV101gW101linksynchronouslinkhandovercompletegV101reservedreservedgV11HW13EWhW13linkhandoverproceedingindicationeventhV134hWׂW134linkhandovercompleteindicationeventhV134mihhandoverpreparerequestresponsecommandserviceׂV14WׁW14linkhandovercompleteindicationeventV145hW145linkinformationrequestrequestinformationhV146ׂW146mihhandovercompleterequestresponsecommandserviceׂV15WׁWׂW15linkinformationrequestrequestconfirminformationV15mihhandovercommitrequestresponsecommandserviceׂV15mihinformationrequestrequestinformationserviceׂV156hW156linkinformationresponseresponseinformationhVindicatetotheuppereVJWcas֗W!W(W+W-W4W5W:W;W?WCWLWoWrWyWaspreviouslyexplainedcommandsshouldnotberestrictedfrLVassociated(WassumedoWasynchronous;WAWasynchronously9W:WatyWattachmentyWattentionyWavailable'W+WyWbyWbandwidthqWbased)W.W4W5W:WwWbasis:WedWWWWWWWWWWWWedWWWWWWWWWWWWWWWWWedWWWWWWWWWWWWWWWWWWWWWWWbejWmWnWwWxWzW~WWրW֌W֕W֗W֙W֠W֣W֥WֱWִWWWWWWWWWWWWWWWWWWWWWWWWWWWWWcmuch~Wh~W~Wmobility֥W֥W֥W֥W֥Wty֥W֥W֥W֥W֥WW֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥WWmobilitylWmWpWqW֏W֥W֥W֏W֥W֥W֥Wmobile-ipWmobilitylWmWpWqW֏W֥W֥W֥W֏W֥W֥W֥W֥W֥W֥W֥W֥WqW֏W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥WW֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥W֥Wmobile-ipWmobilitylWmWpWqW֏W֥W֥W֥W֥W֥W֥Wmobile-ipWmobilitylWmWpWqW֏W֥W֥W֥WmWpWqW֏W֥W֥W֥W֥W֥W֥W֥W֥W֏W֥W֥W֥Wcnetwork֗W:WvWxWyWׄWnetwork-controlled:Wnetworks!W"WSWyWnew)W*W0W:W=WPW[W\W]W^W`WpWqWnewlyEW]Wnext!Wno-W2W?WoWnorestrictiononthedirectionoftheeventmessagesshould?Vnot~W֗W!W+W,W;W<W=W?WAWCWJWKWLWQWRW]WtWvWwWyW|W~WWׁWׅW֣W֣W֣W֣W֣W֣W֣W֟W֟WW֟W֟WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW8crelevance֗Wremote֞WoWuWvW|WremovalfWgWhWremovegWhWreorganization?Wreorganizationofsection5.4.1isneeded?VreplaceHWMWreplacethefiguretoincludepreviouslyintroducedupperlaHVMVMVscenarios:Wschema.Wsection!W"W#W$W%W&W*W2W4W5W6W<W?Wsections!Wsending9Wseptember*Wservice!W2W:W;Wservices;Wshould9W<W=Wsignal:Wso:Wsollicited9Wspecific:Wspecified+Wstart8Wstate:W=Wstates<Wstatic<Wstatic/quasi-static9Wstrength:Wsubject!Wsuggested;Wsupport9Wsynchronous;Wsynchronously:Wtable'W*W>Wtable1needstoincorporatelinkparameterevents>Vtable7entry11stillreferstoaminglistavailableitem'Vtechnology-specific!Wtelecon(Wtelecons*Wterminals;W dijaֱWandֱWndֱWֱWֱWֱWֱWֱWap֌WW֌W֌W֌W֌W֌W֌W֌Wp֌W֌W֌W֌WyּW־Wap֌W֌Wap֌W֌Wp֌W֌Wp֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌W֌WapplicableַWַWַWַWַWַWַWַWַWַWeַWַWַWַWַWַWַWַWַWַWַWַWappropriateyWַWeַWַWַWַWWanyyWּW־Wap֌WapplicableַWַWַWַWַWַWַWַWַWַWַWַWַWַWWeoWeffortxWeithernWelementskWlWqWenablesjWentitylWestablishvWexperiencexWfollowingyWforxWyWfunctionlWnWfunctionalitiesjWfunctionslWhandoverkWxWhandover-enablinglWhaveiWioWidentificationkWiniWnWxWzcnotonly@originaltextremotecommandsmaybetransportedoverhigher@over@protocols@relevance@report@8reports@9representatio@revision@separate@simply@StakeEDtechnology@:text@the~themihcommandsdefinitiondoesnotmentionthepossiblity@this@*the|this@his@his@this@@Msubsequent@>text@*the|this@there@bsequent@>terminal@text@*the|there@there@subsequent@>terminal@terminology@*theut@>terminal@terminology@*theklonusingthewordarchitecture802.21d@whatdoweexactlydefinebyhandoversignalingisittheex@which@ad‚b֛japplication/layer@connectivity@different@event@information@is@a5.3.1~5.4;<5.4.1?5.4.2J5.4.395.5!BS5.5.1"5.5.2#5.5.3$(5.5.4%T5.5.5&U5.6)5.6.1.4V5.6.1.5W5.6.1.6X5.8.2Y5.8.3Z6.1.1CDE6.1.2֗=FGHae6.1.4I6.1.6/>go}6.2.1L6.2.3M~6.2.4֞NO6.2.5.1u6.2.6.2016.2.6.4P6.3.2'*\6.3.4.6.3.52375W6W7.147.2h7.2.1.1Q7.2.11.1p7.2.12:7.2.12.1q7.2.13rW7.2.13and7.2.14rV7.2.13.1b7.2.14rW7.2.14.1c7.2.14.2d7.2.15s7.2.15.1ij7.2.15.2k7.2.16f7.2.17.1lm7.2.17.2n7.2.6.2z7.2.7.1+]7.2.8.1-7.4׀ׁ7.4.10v7.4.10.1[7.4.11w7.4.14^x7.4.8.1t7.4.9.1.2R8.3{8.3.1|8.3.2ׂ8.4.1.2׃8.4.4.8ׄandrWh8Wsection5W6Wsection75V6V6V֏W5.3.3֡W6.2.5.1֟W^technicaltechnicalbindingSVTVUVVVWVXVYVZV[V]V^VpVqVrVsVtVuVvVvVcdelivered֗Wdepending9Wdescribe`WyWdescribedWׁWdescription*W/W8WRWaWeWyWdescriptions!WdestinationRW|Wdetails!WdetectpWyWdevicesyWdifference<W<Won֪W֪W֪Wion֪W֪W֪Won֪W֪W֪W֪W֪W֪W֪Wnation֪W֪W֪WdestructivenWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWdescriptiveWWWWWWWWWWWWWcister-systemisWistra-romaingisWisng|WisWisg|WisWismaing|WisWisg|WisWising|WisWisiW|WisiWiWiWiWiWiWiWiWiWiWiWiWiWoWoWoWoWiWoWoWoWoWoWoWoWoWoWoWpWpWpWpWoWpWpWpWpWpWpWpWiWmWoWpWpWpWpWpWpWoWpWpWWoWpWpWpWpWpWpWpWpWpWoWpWpWpWpWpWpWpWpWpWWoWpWpWWoWpWpWpWpWiWmWoWpWpWpWpWpWpWpWpWpWpWpWpWpW֬W֭W֮W֯WֱWִWֵWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWissuedW_` )246Vrv0|@׃P,>I`opUWz+-:?qׁT]=‚!j‚"*9X‚%Cks‚*l‚1(‚2R‚35BQS\ee```````````````````````````````````` @kփք֣‚%֨&bsentence֗Wserve?Wservice2W9W;W<W?WAWEWJWKWLW\W|WWׁWׂWservices;WLW{Wserving?Wset*W1W9WLWset/extended*Wsetting0Wseveral5Wshall/W8WRWshould'WLWkWnWuWshowuWshownEWwWsignal0W<WiWsignificantlyaWeWsimplified!W"W#W$W%W&Wsince'WsipNWsms\WsoaWsolvetWsome?WCWtWuWsomehowuWsoonkWsourceCWEWIWaWbWcWjWmW|Wsource/destinationaWspecific0W=WEW\WiWqWqWqW}cto@transported@types@upperlayerseventsneedtobeintroduced@Gdjjjjjjdjjjjjwhen@which@ayou@)d‚b֛j@ers@yers@mihnetworkaddressinformationshouldbedeletedandthein@hein@put@@merged@for@information@is@lsap@element@for@information@is@lsap@for@information@is@lsap@for@information@is@lsap@l@local@vent@information@is@local@hold values for different parameters. It is not clear if the MIH_Configure and Link_configure command primitives are to be used for this purpose. But the`6a2220 2005/09/22EP802-21-D00-01.pdf^icexist֞W~WexistingaWdWeWiWjWkWlWmWnWexpected|WexperienceyWexplainedLWexplicityWexplicitlyoWfacilitate?WJWfactLWfastxWfetchyWfew!Wfield|Wfig)Wfigure~W3W@WBWGWHWMWOWSW~WWׁWfigure2~Vfigure3thefigureneedstobeupdatedtoincludeupperlayBVfigure7.1doesnotexist~Vfigures!W"W#W$W%W&Wfinal!Wfinalization!WfirstCWuW|WfirstandsecondparagraphsCVfirstprobleminthecurrentmihgeneralpacketformatisre|VfixbWcWjWmWfixacopy-and-pastetypobVcVfixed!WflowWׁWfollowing1WQWRWpWfollowinglinklayercommandsaremissinglinkcapabilitydisc1V1V1V1V1VbewVi|WցWքWid֦Widentifier֠W֩W֪W֫Widentify֤WօW֍W֎Wcelement֗W\Welements\Welse!Wemploying;WenablingyWenhanceaWeWiWlWnWyWenough`Wentire5WentitiesDWKW׀Wentity:W?WLWRW|W׀Wentry'WerrordWjWmWetc4W5WqWevent֗W:W;W=W?WJWoWpWsW|WW׀WׁWevents֗W/W=W>W?W@WAWBWCWDWEWFWGWHWIWQW]WaWeWoWsW}WWׁWeverything!Wexample?WJWLWWׁWexcept׀Wexceptfortheprimitivesoftheeventservicecategoryall׀Vexception!Wexchanges<W<W<W{W{Wtly{W{W{W{W{W{Wxactly{W{W{WW{W{WRcframes֞Wfrom֗W!W*W;W?WAWCWJWKWLWgWhWpWsWwWyW|W׀Wfrom/to@WfullyWׁWfunction9W?WIWLWQWiWjWkWlWmW|W׀Wfunctional|WfunctionalityrWxWfurther?WJWg:WAWoWpWqWrWsWvWgeneral|W׀Wgenerally|WgeneratedvWwW׀WgenericCWDWyWgive9WgoJWgoesCWgoingAWCWKWLWsWgroup!Wguiidelines4W5WhandoffsWyWhandover8W:WCWJW^WfWgWhWiWjWkWlWmWnWsWwWxWׂWhandovertypesdescriptionneedsmoreacuracyuserfc3753d8Vhandovers?WCWyWharmonize*WhasEW`WWׁWׁWׁWׁWׁWׁWWWWWWWWWWWWWWWWtable-1WtablesWWWyoshihiro@`bbe~W֞W'W/W0W8W9W;W<W?W@WCWEWFWIWJWLWNWRWSWTWUWVWWWXWYWZW[WaWeWiWkWlWnWtWuWyWbecauseCWaWbecomeaWbecomesaWbeen1WLWPWaWiWkWlWnWbefore0W^W`WaWiWbeginskWbehalfNWbehaviorKWNWbehaviour?WJWuWbelowEWwWWׁWber0WbetteraWeWlWyWbetween?WEWJWNWeWbidirectionaluWbit[Wbitmap+WblackoutkWboth?WEWiWlWoWbroadcast-WbroadlyEWbroughtlWbufferaWnWbufferingkWnWbullet=WbutEWaWiWlWyWby~W/W1W<W?WCWDWEWIWJWLWNWSWTWUWVWWWXWYWZW\W]WaWeWiWlWnW~WׁWׄWbytes|WׅWKXbaccess֞W?WJWLW\W^WaWyWaccordingSWTWUWVWWWXWYWZWachievingaWackaWIWadd4rcrecvnobroadcastmsg-Vaddthefigurelocatedinsection2.3inthefile21-05-0xxxGVaddthefollowinglinklayercommandsinsection6.2.6.2the1Vaddthefollowingtextattheendofbullet1=Vaddthefollowingtextattheendofsection6.1.2FVaddtosection7.2aftersection7.2.12thecontentsofthe:VaddupperlayereventsregistrationdescriptionIVadded5WEWadditional?WEWIWaddress?WadvisoryDWafter:W<WGWahead?Wall*W,W/WIWallows0Walong!W"W#W$W%W&Walredy1Walso/W?WDWJWLWan;W?WCWJWand*W,W.W/W1W2W3W5W8W9W<W?W@WAWCWDWEWFWGWHWIWJWKWLWand/orLWbof~W!W"W#W$W%W&W'W.W0W5W8W9W:W<W=W?WCWFWIWJWLWNWOWRW[W\W]W^WaWbWcWdWeWiWjWkWlWmWnWpWqWrWtWwWyW|WׁWofevents1WoftenaWold^WaWon0W9W;W=W?WCWJWNWaWiWkWnWtWuWwWone'W.W?WJWaWׂWonly'W/W[WeWiWlWyW|WׂWopcodeWׁWׂWoperators<Wopoa]W^WopposedDWiWlWoptimalLWoptiontWoptional+W,WpWwWoptionstWtWtWWWWWWWWWWWWWWWWWWWWWWWWWWWWWAbfollowing@found@6gprs@7here@Aimminent@Ninclude@informative@yip@Lis@layer@linkthresholdsconfigureisalocallinkcommandthatcanc@low-loss@zmay@messages@lnametypevalidrangedescription@need@network@of@or@packet@{possible@Mprotocols@reestablishment@remote@replace@replacehwiththefollowingtext@Ireplaced@requestevent@response/type@&sentence@specification@strike@supportedeventlist@text@ thethis@ thiscommentproposesanewinformationinwhichenablesam@tomodifytable-10asindicatedbelow@transfer@?updatesection7fromcontribution21-05-0402-00-0000sectio@^varies@0which@-with@where@xxx@re@xxx@xx@ojmp1@WoW21-05-0439-00-0000oW21-05-0439-00-0000usedforupdatessincerevision1isnotoV3gppTW4uW5.3.1`W6.1.2<W6.2.1<W6.3.52W802.16(WawWaccess֞WaccompanyingTWadded-W0W1W`Wintable1Vaddedmessageinlinkdownindication-Vaddednewtableforlinkcommands0Vall)Wand<WVWeWuWareVWavailableoWbe֞W)W<Wbeen)WbetterTWbothuWchanged֞W2W6Wchangedlinkconfiguretolinkconfigurethreshold6Vchangednameofprimitiveinsectio6.3.52Vchangedtoremotecommandsmaybetransportedovernetworkl֞VclarificationseWcommands֞W0W1WuWcomment<Wcommunication/Wconfigure6WcontentaWdiagram(WTWdiagrams)Wdifferent/Wdoes<Wdown-WdrawSWeditedaWeWeditedandaddedtextmayneedmoreclarificationshereeVcbe֗W֞W!W+W9W:W;W=W?WBWCWDWFWIWJWLWQWRW]WoWpWsWtWwW{WW׀WׁW׃WW֥W֣W֥W֥W֥W֥W֥W֥WֱWWֱWֱWֱWֱW֥WֱWֱWֱWWֱWֱWWWֆW֌W֕W֗W֙W֠W֣W֥WֱWֱWֱWW֥WֱWֱWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWch Wswitch WtableWWtablesWWWWWWWWWWWWWWWWWWWWWWtable-1WtablesWWWWWWWWWbc141@a@absolutely@addanewlinklayercommandlinkconfigurethresholdstoco@malso@arrows@as@be@cuments@,anymore@at@bew^technicalnon-binding~V֗V֞V!V"V#V$V%V&V(V*V+V-V.V0V1V5V8V9V:V;V=V>V?V@VAVBVCVDVEVFVGVHVIVJVKVLVMVNVOVPVQV\V`VeVfViVkVlVnVwVxV{V|VV׀VׁVׂVׂVׂVׂVׂVׂVׂVׂVׂVׅVրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWրWVwasiWiWVVVVW W W W WthereWWWWWWWWWWWWxxxWctransported֞Wtrigger:Wtriggers]Wtrue֗WtwooWpWsWW׀WׁWtype,W:W;W=WpWqWtWW׀WׁWsWW׀WtypobWcWue9Wue's9W:Wul?WCWunder`WyWunidirectionnal@WunitdatarWunsollicited9Wup+WJWsWupdate(W)W*W4W5W9WJWSWupdateentiresection7asperguiidelinesissuedlasttime5Vupdatefig9basedonnewupdatedreferencemodelfor802.16)Vupdatesection6.3.2ondescriptionofieswithnewtablefr*Vupdatesection7.1asperguiidelinesissuedlasttimebased4Vupdatethereferencemodelandassociatedtextfor802.16as(Vupdated)WBWupdtae6Wupdtaediscrepanciesinsection76Vupper?W@WAWBWCWEWFWGWHWIWJWKWLWMWNWOWPWQWupperlayereventsneedtoberegisteredbythemihfunctionIVcbring~Wbroadcast-WpWbuLWbut,W<W?WCWoWrWsWtWWׁWbyIWLWQW]WrWvWyW׀Wcalled=Wcan֗W9W:WLWsWyW|WWׁWcannotsWcapability|W׃WcapablewWcarry:W<WpWcase.W9WJWcategories׀Wcategory׀WcausexWcellyWchange0W=WtWchanges=Wchoices:WclarifynWclarity~WaWeWiWkWlWclassifiedoWclearoWtWwWclearer!WclientwWcolumn,WoWcommand0W;WJWRWoWtW׀W׀W׀WWWzW{WcapabilityWcapabiltyWcapableWWWWWWWWWWbleWWWWWleWWWWWWWWWWWWWWcellularnW֫WcertainֵWcertainlyrWchangeքWWWW#$cbContribution 21-05-0423-00-0000 with a proposed revision for the text and figures in Section 5.5.3d4w Withdrawn{l) none needed 2005/12/07 2005/11/066 2005/12/01 2005-09-14 Comment: This is not absolutely true as link layer events consumers can be different from the network layers.d18vNo specific text proposedwRejected 2005/11/17 2005-09-14sedwRejected 2005/11/05 2005-09-14֙EEric FNJEDJOU^Technical, Non-binding_43a6.1.3ent delivered to a link layer element must be conveyed to the corresponding network layer element in order for the event to have relevance." Comment: This is not absolutely true as link layer events consumers can be different from the network layers.d18vNo specific text proposedwRejected 2005/11/05 2005-09-14֙EEric FNJEDJOU^Technical, Non-binding_43a6.1.3 2005-09-14֙EEric FNJEDJOU^Technical, Non-binding_43a6.1.3vchave֗WAWpWxW׀WheterogeneousyWhigher֞WsWhigher-layerQWhowyWhoweveroWwWi:WyWidentifierRW|Widentifiers|Widentify]WieeeyWies*WifoWtW׀WiiyWiiiyWiit,WillustrateOWimminentiWjWkWimportantpWvWyWimprovekWkWkW֠W֠W֠W֠W֠W֠W֠W֠W֠W֠W֠Wfy֤Wie֠W֠W֠W֠WW֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤W֤WdentifierrW֠W֩W֪W֫WWidentify֤W֤W֤WdentifierrW֠W֩W֪W֫WWidentify֤W֤W֤W֤WdentifierrW֠W֩W֪W֫WWidentify֤W֤W֤W֤W֤WidsWWWsWWWsWWWWWWWW<bremote֞W/W?WCWEWFWJWNW[WbWcWjWmWoW{WremotelyDWremove*W,W6W<WQWfWrWsWuWxWremovealltablesfromsection6.3.2andreplacewithtable*VremoveoranyotherupperlayerQVremovereferencetotable7.17.2removereferencetolinkc6Vremovetheentiresection7.2.16fVremovewordoptionalfromtypecolumnandmoveitintoname,VrenamezWrenamelinkeventregisterrequesttolinkeventderegisterzVrenewal+W?Wvwaccepted֞(*1356<=@QRSTV`abcdfghijkmnpqwz{}~ׂ׃ׄaccepted-modified),-0248>elouydeferred!W.W?WJWUWWWXWYWvW׀WׁWdeferredfornextmeeting!V.V?VJVUVWVXVYVvV׀VׁVfor!W.W?WJWUWWWXWYWvW׀WׁWmeeting!W.W?WJWUWWWXWYWvW׀WׁWnext!W.W?WJWUWWWXWYWvW׀WׁWrejected~9:]x|superceded֗'/twithdrawn"#$%&+;ABCDEFGHIKLMNOPZ[\^rs{defer)Wdisagrees<Wdo,Wdone֞W(W*W-W0W1W2W3W4W(W*W-W0W1W2W3W4W5W8W@WaWeWoWuWm^non-binding~W֗W֞W!W"W#W$W%W&W(W*W+W-W.W0W1W5W8W9W:W;W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQW\W`WeWfWiWkWlWnWwWxW{W|WW׀WׁWׂWׂWׂWׂWׂWׂWׂWׂWׂWׅWWWWWWWWWWWWWWWWWWWWWWWWWWofWorWparameterWWparametersWremoteWremoveWWrequestWWWWrequestthatanewparametertocarryabasicinformationelVrequestthatanewparametertoindicatethetypeofparametVrequesttoremovesection7.2.13and7.2.14andrespectiveeVrespectiveWWWsectionWWtableWWWtable-1WtablesWWW^technical~W֗W֞W!W"W#W$W%W&W(W*W+W-W.W0W1W5W8W9W:W;W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWSWTWUWVWWWXWYWZW[W\W]W^W`WeWfWiWkWlWnWpWqWrWsWtWuWvWwWxW{W|WW׀WׁWׂWׂWׂWׂWׂWׂWׂWׂWׂWׂWׅWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW~bc1=W>WAWgWpW1.2yW10-mihׁW11֞W11still'W135*W14ׂW14-linkWWpWuW2005*W21-05-0423-00-0000!W"W#W$W%W&W3BWuWyW37538W3gppTWYW3gpp/3gpp2yW3gpp2UWZW4<W5.4.1?W5.5!WSW5.5referencemodelsforaccessnetworksSV5.5.1"W5.5.2#W5.5.3$W5.5.4%WTW5.5.4mihreferencemodelfor3gppTV5.5.5&WUW5.5.5mihreferencemodelfor3gpp2UV5.6!W5.6.1.4VW5.6.1.4mih-rrc-sapVV5.6.1.5WW5.6.1.5mih-ppp-sapWV5.6.1.6XW5.6.1.6mih-lac-sapXV5.8.2YW5.8.23gppamendmentsYV5.8.3ZW5.8.33gpp2amendmentsZV6\W6.2.1<W6.2.5OW6.3.2*W\W7'W5W6W7.14W~W7.2.12tW7.4.10wW7.4.10.1[W8hW8-mihW802.11rW802.16(W)W802.21oWrWsWxWyW9)Wcl2֞WsW|Wl3|Wl3mp?Wlast4W5W׃Wlayer֗W֞W0W1W?WBWCWEWGWHWIWKWLWMWNWOWPWQW]WsW}W}W}WW@WAWCWFWJWKWLWoWpWrWless!Wlike;WsW|WlikelyCWlink֗W+W-W0W1W;W=W>WJWQW]WaWeWfWgWhWiWjWkWlWmWnWoWpWrWsWtW}WlinkeventhandoffxxxprimitivesaredefinedtoindicatethsVlinksdutransmitxxxprimitivesareusedtonotifythetranrVlinkcapabilitydiscov1Wlinkevent1Wlinkeventderegister1Wlist'W9WQWtWlistingPWlistsyWlocalRWoWuWlocated<Wlocation9WyWlooksWlowerLWlower-layerQWmarWmacpWrWmade?Wmake.W:WyWmakeacasefortlvrepresentatiobeforethatforschemabas.Vcthis~W֗W2W:W@WCWLWQWVWWWXWYWZW`WaWdWeWfWgWhWpWrWtWvWxWyW|W׀Wthisfiguredoesnotbringmuchclaritytothetext~Vthisfigureshowsunidirectionnalarrowsforeventsandcomm@VthisistoproposetheremovaloflinkhandoverproceedingifVgVhVthisproposalistocorrectacopy-and-pasteerrorintheexdVthisproposalistoenhancetheclarityoftheexistinglinkaVeVthisproposalistoinsertanewsectiontodescribethemih`VthissectionisoutdatedVVWVXVYVZVthoseCWpWthreshold:WtWthresholds0Wthrough;Wthus|Wtime4W5Wtlv.W.W.WVonisnotconsistentbecause6.2.5.1alread֟V֟V֟V֟Vficationisnotconsistentbecause6.2.5.1alread֟V֟Vblayer֞W0W1W<W?WDWEWFWIWJWKWLWNWOWQW]WaWdWeWiWkWlWnW}Wlayers;W=W?W@WAWCWEWFWJWLWNWPWaWeWiWlength|Wless<Wlevel0W<Wlevels0WlimitingaWlinesyWlink/W0W1W2W5W6W:W<W=W?WAWEWIWJWKWLW]WaWbWcWdWeWgWhWiWjWkWlWmWnWoWpWqWrWwWzW}WWׁWׂWlinkeventsourceisdefinedasfollowsbVcVjVmVlinkhandovercompleteisgeneratedwheneveranativelinkllVlinkhandoverimminentisgeneratedwhenanativelinklayeriViVCWEWFWJWNWRWaWbWcWlocallyDWlocated?WGWHWJWOWlocationJWlogical?WJWlongaWlosingiWloss0WiWlosslessaWlostaW]cto~W֗W!W'W0W9W:W;W<W=W>W?WAWBWCWDWEWFWHWIWJWKWLWMWOWQWRWSW]W`WaWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWwWxWyW|WW׀WׁW׃WׄWׅW\ccommands֞W1W@WBWJWKWLWMWNWOWPWuWvW֞W֞WW{W֞W֞W֞W֞WzW{W֞W֞W֟W֟W֟WW֟W֟W֟WW֟W֟WW֟W֟WW֟W֟W14thisisonlyanexamplecommandszW{W֟W֟W֟WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWnexample֚VcommandszW{W֟WWWWWWWWnexample֚VcommandszW{W֟WWWWWWUcin֗W!W"W#W$W%W&W(W*W,W-W2W6W9W:W<W=WAWJWKWLWQW^WaWdWeWgWhWjWkWmWoWpWqWrWsWtWuWvWwWxWyW|W}WWׁWׂW׃Win1statechangeseventsrefertochangesintheconnectivi=Vin1weshouldnotrestricttheeventsfromgoingfromtheuAVin2weshouldnotrestrictthecommandsfromgoingfromtheKVKVWJWindications;WinfluenceCWinformation2W9W:W;W<WAWinformativeCWinitiateCWinstantiations!WintegrateCWinteraction;Winterface=Winto,WEWintricate!Wintroduce:W?WGWintroduceafigureforpreviouslyintroducedupperlayereveGVintroduceanewprimitivethatwillcarrymediaindependent:VintroducedFWGWHWintroducingCWinvoked:Wip?WAWingaliV!_19a5.5bReplace current figure 3 with a more simplified version of the figure as described in contribution 21-05-0423-00-0000 along with explaining text.cAContribution 21-05-0423-00-0000 with a proposed revision for the text and figures in Section 5.5 (MIH Reference Models for Access Networks). The rationale for the next few comments is to provide clearer and less intricate pictures and descriptions than the current ones. The sections are not meant to be final, as the technology-specific instantiations of the MIH_NET_SAP (SAP between MIH and Transport Plane) are subject to the finalization of the MIH Communication model. With the exceptioBn of the reference to MIH_NET_SAP, everything else is well aligned with the current content of Section 5.6 (Service Access Points). A few details in the technology-specific models may need to be fixed, for which any contribution from the whole group is welcome.d1vcontinuing workwDeferred for next meeting{l) none neededed`,bcommands֞W1W?W@WGWHWJWLWMWNWOWPW[WuWcomment[W\WcommentaryEWcomments\Wcommit׀WׂWcommunication~W/WcompletegWhWlWnWWׁWׂWcompletedlWnWcompleteduponnWcompletionnWcomprised<Wcomprising<WconditioniWconfigurationJW[W\WlWions5Wdelete+Wdeletemobilitymgmtprotocolsupporttypebitmap+Vdependent*Wderegister1Wdescribed!W"W#W$W%W&Wdescribes:Wdiagram)Wdiscussed'Wdo*Wdoc:Wdocument:Wdynamic<We9W;Weach0Weditorial5Weither9W;Welement.Welements*W9Wemploying;Wentity/Wetc/Wevent/W0W1W9W;Wevents/Wexchanged;Wexecute0Wexecuted0Wexecution0Wexplaining!W"W#W$W%W&Wexpose/Wfalls0WWconly֞W<WoWsWuWyW|WWׁWopcodeW׀WׁWoperations;WoperatorJWoperatorsyWoptimize?WJWoptional,Wor֞W2W:WQWRWoWsWvW|Worder֗Woriginal֗W֞W;Woriginaltextalinklayereventdeliveredtoalinklayere֗Voriginaltextmobileterminalsemployingthemihserviceswo;V;V;VrizV{V{V{V{VormationmessagescarrizV{V{V{VandinformationmessagescarrizV{V{V{V{V{VzV{V{V{VrmationmessagescarrizV{V{V{V{V{V{V{V{V{V{V{V{VxteventscommandsandinformationmessagescarrizV{V{V{V{V{V{V{V{V{V{V{V{VxteventscommandsandinformationmessagescarrizV{V{V{VandinformationmessagescarrizV{V{V{VessagescarrizV{V{VzV{V{VtVcprotocols֞Wprovide!W9WwWyWprovidedpWprovidingqWpurposetWyWpurposesuWpush;WqosqWquery;WQWwWqueryingwWrate:Wrather?WCWrationale!Wrc-WreadSWreadsvWreasonablewWreceiptvWreceive;WDWreceivedJW׀Wreceiving|Wrecv-WredundancyxWredundantrW|Wrefer=WWׁWreference!W"W(W)WSWTWUWreferencesyWrefers'WreflectvWregardyWregister1WWׁWregisteredIWregistrationoW{W|Wregistrationshouldbeallowedforallmihservices{Vregular:Wrelated<W=W|W|W|WׅWׅWWWWrefereedWreferencepW}W֏WֹWּWWWWWWWWreferencesWreferringWreflectWWWreflectsWregardWregardingtWregistrationWW)%EAndreaFFrancini^Technical, Non-binding_22a5.5.4bReplace current figure 7 with a more simplified version of the figure as described in contribution 21-05-0423-00-0000 along with explaining text.cbContribution 21-05-0423-00-0000 with a proposed revision for the text and figures in Section 5.5.4d5w Withdrawn{l) none needed 2005/12/07 2005/11/06&EAndreaFFrancini^Technical, Non-binding_23a5.5.5bReplace current figure 8 with a more simplified version of the figure as described in contribution 21-05-0423-00-0000 along with explaining text.cbContribution 21-05-0423-00-0000 with a proposed revision for the text and figures in Section 5.5.5d6w Withdrawn{l) none needed 2005/12/07 2005/11/06'EPeretzFFeder^ Editorial_44`33a6.3.2on for the text and figures in Section 5.5.5d6w Withdrawn{l) none needed 2005/12/01 2005/11/06'EPeretzFFeder^ Editorial_44`33a6.3.2ing text.Technical, Binding_82;) @ @a@a@icnjedjou@ @ @a@ea@a@a@a@a@ @a@a@cAcAFbBcBF @a@#v"bReplace current figure 4 with a more simplified version of the figure as described in contribution 21-05-0423-00-0000 along with explaining text.cContribution 21-05-0423-00-0000 with a proposed revision for the text and figures in Section 5.5.1 (MIH Reference Models for Access Networks).d2w Withdrawn{l) none needed 2005/12/07 2005/11/064ayers.d18w Superceded 2005/12/01 2005-09-14֞EEric FNJEDJOU^Technical, Non-binding_48`34a6.2.4bReplace the original text with the following: "Remote commands may be transported over network layer protocols or access layer protocols."link layer events consumers can be different from the network layers.d18w Superceded 2005/12/01 2005-09-14֞EEric FNJEDJOU^Technical, Non-binding_48`34a6.2.4bReplace the original text with the following: "Remote commands may be transported over network layer protocols or access layer protocols.", Non-binding_41`25Bcjpaddedeoeditedthecontent@need@sections@_updated802.16referencediagram@Yv2@adopoting@changenametocontrolbroadcastinsteadofbroadcast@fields@ not@ proper@specify@srini@within@{done5kdone@needed!:ctext~W֗W֞W!W"W#W$W%W&W(W;W?WQW`WdWvWyWthan!Wthat.W:W<WCWDWLWoWqWvWwWyW׀WtheWiWnWnWnWnWnWnWnWnWnWnWnWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWjWjWjWW֥W֦W֧W֩W֪W֫W֬WtheiWjWjWjWjWjWjWjWW֧W֩W֪W֫W֬W֯W WtheiWjWjWjWjWjWjWjW֤W֥W֦W֧W֨W֩W֪W֫W֬WֱWִWֵWֹWּWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWGcdifferent֗WoWtWuWW׀WׁWdifficultSW׀Wdirection?Wdirectly=WsWdisconnected=WdiscoverQW׃WdiscoveryoW|Wdiscrepancies6Wdiscussed:WdiscussesyWdiscussion`Wdiscussions(W*Wdistinguish׀WdotWdocumentyWyWWWWWsesWWWW֛WdirectlyWdiscoveryրWWdiscussesWWsesWWWWcussesWWWWussesWWWWssesWWWWdiscussesWWWWeavesdroppedzWeciֵWelement֠WִWelsewhereWenablerslWenoughpWWentity։WequallyWequipementsִWes/csִWessentialmWethernetWevenzWքWevenaftersecureassociationtheeventscommandsandinformzVeventքW֚W֜W֝WWWeventszW֗W֛WWWWWevery֤Wexactly{W:abcd€€€€€€L@bis~W'W0W<W=W?WCWEWIWJWNW[W\W]W^WaWbWcWdWeWiWjWkWlWmWnWqWyW{WׄWissuedNWissuesDWit,W/WIWNW]W`WdWiWkWnWuWitproposesanewlinklayereventsofmieswhichcansuppor]Vitem'Wits9W?WJW[W\W]WaWiWkWlWyWitselfNWjusteWlWnWkey5Wl2?WLWeWlWnWl2sdu?Wl3?Wl3mpJWlatencyaWeWWWWWWWWWWWlayersqWWWWWlciWleastֹWlengthWWlikelyWWlineWWWWWWWWline10WlinesWWWWlinkvWֶWֹWWWWWWWWWWWWWWWWWlink-specificW`‚6֗{‚8D‚9cf‚:g‚A01pt‚Ca‚D'E׀‚E֞d‚F~‚GYb‚I/‚QMy‚T[‚Um‚V.LZ‚Wu‚Xin‚Y3^xׄ‚Z8‚aH‚dFJ‚eGw‚f}‚gNO‚hh‚jA‚rP‚s;WBWDW|WneedstobemoregenericabouttheentitiesthatareabletoDVneighborhoodyWneighboring9Wnet!W!WWWWWWWW֕WWWWWneighborWWneighboringWWWnetworknWyW֗W֠W֦WWWWWnetworksWnew֔WֵWֶWַWָWֺWֻWֽW־WֿWWWWWnewsentencesincethemaydraftok֔Vno}W֧W֫W֬WWWWnoneedtohavesuchadescriptiveintroductioninsection6VnodeoWּWnotjWkWmWoWpWqWrW|W}WցWքWֆW֍W֎W֏W֓W֗W֚W֟WִWWWWWWWWWWWWWWWWWWWWg! QEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bffeder"#$'francini!%&gupta()*+,-./0123456jee|kim}~׀ׁׂ׃ׄkoh{liu[W\W]W^Wnjedjou~֗֞park[W\W]W^Wparkliu[V\V]V^Vperesse89:;<=>?@ABCDEFGHIJKLMNOPsreemanthulaopqrstuvwxyzxie`abcdefghijklmn^bindingSWTWUWVWWWXWYWZW[W]W^WpWqWrWsWtWuWvWeditorial'),/2346Yku׃/?Zlvׄ0@mw‚!1Anx‚"2By‚#3Cz‚$4D‚%~5E‚&6F‚'G‚(H‚)֗I‚*J‚1K‚2L‚3M‚4N‚5֞O‚6P Eric NJEDJOU^Technical, Binding_7`31a3cThis is a wrong definition d14tE Eric NJEDJOU^Technical, Binding_6`40a3cSame as previous commentd12vNo specific text proposedwRejected 2005/10/17 2005-09-14uE Eric NJEDJOU^Technical, Binding_6`53a3c This terminology is .11 specificd13vNo specific text proposedwRejected 2005/10/17 2005-09-14vE Eric NJEDJOU^Technical, Binding_7`31a3cThis is a wrong definition d14ic NJEDJOUcover֞WoverallyWpacket|Wpackets|Wparagraph<WDWEWparagraphsCWparameter,W0W:W>WqWtWparameters+W<W=WpWqWtWpart+Wpast`WpeerRW|Wper(W4W5Wperform|WpictureTWUWpictures!Wplane!WpleaseSWpleaseupdatesectionSVpoa]Wpoas9Wpoints!WyWpollRWpollingRWpossibleyWpossiblityJWpremitives^WpreparewWpresentationuWpreviously;WGWHWLWMWprimitive:WQWpWtWW׀WׁWprimitives2WhWoWrWsWtWwWxWW׀WׁWproblem|WprocedureLWsWproceedingfWgWhWprocessJWprocessing|Wproposal`WaWdWeWgWhWproposefWgWhWproposed!W"W#W$W%W&W]Wprotocol|WׅWׅWׅWׅWׅWׅWׅWzlUbmay֞W0W9W?WAWCWDWEWFWIWJWLWaWkWnW׃WmeaninguWmeansJWmecanism;Wmechanism9W;W?WIWmechanisms8Wmedia*WAWKWLW\WeWiWlWqW{Wmedium?WJWmergeuWmessage\WoW|WׂW׃WׅWW0W2W;W?W@WBWCWEWFWIWJWKWLWNWRWmih-userNWmiis9W<Wming'WmipNWmn-controlled8Wmn-initiated8Wmobile;W?WCW[W\Wmobility+W<W?WCWKWmodel~W/W9WBWLWmodified@Wmore!W"W#W$W%W&WDWmostlyDWmove,Wmsg-Wmss\Wmulti-modeLWmultiple0WCWmust@Wn/a[W\Wname'W,W[W\Wnametypevalidrangedescription[Vnature<WDWnear?Wneed?WCWDWneeded.WCWneeds[Wneighbor'Wrcmanagement֞WJWmarkoWmay֞W!W+W:W;WAWKW]WxWmeaning}W!WmechanismsWmechanisms;Wmedia:W?WJWmeeting*Wmeetings`WmehanismssWmention2WJWmentionnedCWLWmessage9W?Wmessages?WmgmtQWhWmics<Wmies<Wmih!W"W/W9W;W<W?W@WAWCWIWJWKWLWNWQWRWTWUW]W^W`WhWoWpWtWuWvWwWxWmihhandoverpreparerequestandresponseprimitivesarecapwVmih-lac-sapXWmih-ppp-sapWWmih-rrc-sapVWmih/higherpWmiis9W\Wmiisshouldalsoprovideawayformihfunctiontoasynchron9Vming'Wmissing1Wml:Wmme:Wmmis9Wmobile;WvWmobile-ipxWmobilityJWmodel!W(W)W;WTWUW`Wmodels!W"WSWmore8WCWDWpWmove,Wmsg-W MvnotlW{Wobjected]W^Wof,W-W.W[W\WeW{W׀WׁWon)W8W:WeWonavote:Vonly0W>Wonlychnagethetextrelevanttocomment31>VopcodeWoptional,Wor,Wparameter,Wpartiicpants[W\WprimitiveׁWprimitivesׁWveׁWprimitivesׁWׁWׁWedyWscope|WselectingyWselectionyWshouldyWspecificpWrWsWtWuWwWzW{W֍W֎WsubmitoWsubmitagainwithcorrectpagenumberoVtextpWrWsWtWuWwWyWzW{WօW֌W֍W֎WtextnotavailableinthenewversionօVtheyWօWthisyWtimeyWto}Wupdated֌WuseryWversionօWwithoWyW~WցWworkցWworkwitheditorցVwacceptedւփaccepted-modifiedvy}ցrejectedoprstuwxz{|~քօֈ֊֌֍֎€bthis~W0W3W9W:W?WLWPW[W\WaWdWeWiWkWlWnWtW׃WׄWtproposesanewinformationinwhichenablesam\Vthiscommentproposesanewparameterwhichenablesamobile[VthisnotificationisgeneratedwhenlinkarqmodulehasdetedVthreeEWLWthreshold0W=WtWthresholds0W5Wthrough;WthroughputaWthusCWeWtime<W?WCWaWkWtime-sensitiveaWtimeraWtimingeWtitle.Wtlv.Wto~W.W/W0W1W3W6W8W:W<W=W?W@WAWCWDWEWFWIWJWKWLWNWRWSWTWUWVWWWXWYWZW[W\W]W^WaWbWcWdWeWiWjWkWlWmWnWoWpWqWrWsWtWuWwWxWyWzW{W|W}WWׁWׂWtoinsertthemihlinkdownandmihhandovercommitmessagesׂV vfields~WforlW׀Wgroup)Win,Winstead,W-Winsteadofusingoptionalinthenameaddanothecolumnwher,Vinter-technologylWintra-technologylWis,W0WoWlastoWlinkeWlist׀WׁWlistiing׀Wmake2Wmakethenameconsistentwiththedescription2Vmandatory,WmaylWmedia4Wmeeting?WJWmembers]W^Wmemberswhoobjectedwouldworkwiththecommentortoresolv]V^VmergeWmergeopcodeanddescriptioncolumnsVmodels)WmodificationsoWmodificationstothetableasdiscussed21-05-0439-01-0000oVmodifiedeWmodifyuWyWmodifycolumn7and8asdiscusseduVmodifythetexttoreflectthediscussionyVmoreUW[W\WlWmorediscussionrequestedUVmotivation/explainatlWmoved4Wname,W-W2WneedlWׁWnetworklWnextvW֨W֫W֭W֮WnospecifictextchangepVbtext֞W!W"W#W$W%W&W*W.W8W9W;W<W=WDWEWFWIWLWRW`WvWyW׃W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬W֬WWWWtheiWֶWַWָWֹWֺWֻWּWֽW־WֿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWthefollowingnewdefinitioncoversthecasewherethemobilּVthefollowingnewdefinitionemphasizesthedistinctionbetwֶVthenewpointofattachmentdefinitionreplacescurrentdefiֹVthe11thWtheirWthemWthenWthereֹWWWthereare3waystosolvethisVtheseWWWtheyWthingW cthe~W֗W!W"W#W$W%W&W(W,W9W:W;W<W=W?WAWBWCWDWHWIWJWKWLWMWQWRW\W]W`WaWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyW|W}WW׀WׁWׂW׃WׄWthefollowingdescriptionfordestinationidentifieristalkRVtheinformationprovidedinlinkdetectindicationmustcontpVtheintroductory/overviesectionmustdescribeallthepossiyVthelinklayereventsandlinkeventsareusedtogetherint}V}VameterqVthewordoptionalappearsintypecolumntypeisnotoptiona,VthemyWthen?WoWthere2W?WuWthereisnodecriptionormentionofanyinformationservice2Vtherefore=WrWtheserWyWtheyCWthirdDWthirdparagraphDVcconsumers֗WcontainpWcontent!Wcontribution!W"W#W$W%W&Wcontribution21-05-0423-00-0000withaproposedrevisionfor!V"V#V$V%V&VcontrolJWKWLWyWcontrolledyWconveyyWconveyed֗WconveysyWcopy-and-pastebWcWdWjWmWcorrectdWcorrectionzWcorresponding֗WvWcould?WJWpWcrossed:Wcuase-Wcurrent!W9W:WSWTWUWtWvWyW|WcurrentfigureisdifficulttoreadanditisoutdatedSVcurrentpictureisoutdatedTVUVcurrently<WsW|Wdata:W׃WdecisionsCWdecode|Wdecription2Wdefined=WEWQWoWsWxW|WWׁWdefines|Wdefinition8WJWiWjWkWlWmWnWtW|WdefinitionsoWxWdefnitionnWnWnWnWnWnWnWWWW6bfollowingfollowsbWcWjWmWfor)W,W.W/W0W9W;W=W?WCWEWIWJWLW[WaWeWiWkWlWnWoWtWxW{WformatuW|WׅWic'Wget2W5Wgiven=Wgmm?Wgprs?Wh8Whandover;W<Whandovers8Whave1Where0Whigher<Wi9W;W=Wie'W.Wies*W9Wif.W0Win!W"W#W$W%W&W'W*W,W.W/W0W1W3W5W8W;W<W>W?Winclude*W.Wincludetextfromcontribution21-5-401-00-0000-ietlvrepre.Vindependent/media*Windicate/W?Windication+Windications;W=Winformation.W2W5W9W;W<W?Winformative'Winitial0Winitiate0Winsert(W*W2Winsertatableandspecifyinformationserviceprimitivesli2Vinterest?Winterested/Winto,Wip+WW jstobereplacedwithupperlayers@s@operatorinformationelem@prefered@remove@emove@emove@remote@scanbeencapsulatedi@part@remote@reference@reference@ervicesmaybec@packet@reference@I breplacereplace1withAVreplace2withKVreplace6.1.4withthefollowingtextIVreplacecurrentfigure3withamoresimplifiedversionoft!Vreplacecurrentfigure4withamoresimplifiedversionoft"Vreplacecurrentfigure5withamoresimplifiedversionoft#Vreplacecurrentfigure6withamoresimplifiedversionoft$Vreplacecurrentfigure7withamoresimplifiedversionoft%Vreplacecurrentfigure8withamoresimplifiedversionoft&Vreplacefigure11withthefigurelocatedinsection2.1inHVreplacefigure16withthefigureinsection2.2inthefileMVreplacefigure7.1byfigure16and17~VparagraphbythefollowingtextEVreplacetheoriginaltextwith;Vreplacetheoriginaltextwiththefollowingremotecommands֞VreplacethethirdparagraphbythefollowingtextDVreplacewithfigureinfile21-05-0xxx-00-0000-gmihrefmodBV !bthethecommandserviceisafacilitythatenablesthecontroloJVthefiguremustbemodifiedtoreflectthefactthatevents@VtheidentifieroflocalorpeermihentitytowhichthescanRVtheitemshouldbenotedasinformativesincemingisonlyd'Vtheir5WlWoWthem/WaWiWlWxWthenJWaWtheretWthereare3optionstosolvethistVtherebyiWthese8W=W?WCWDWFWNWaWeWthey/W1WDWaWeWlWthirdDWtheyցWWthingWWWWWWtheseրWWWWtheyցWWthingWWWWWtheseրWWWWtheyցWWthingWWWeric~֗֞eunah}~׀ׁׂ׃ׄjoughoon|mathieu89:;<=>?@ABCDEFGHIJKLMNOPohbaQWRWolveraSWTWUWVWWWXWYWZWperetz"#$'qiaobing`abcdefghijklmnsoohong[W\W]W^Wsoohongxiayou[V\V]V^VsrinivasopqrstuvwxyzulisesSWTWUWVWWWXWYWZWulisesolveraSVTVUVVVWVXVYVZVvivek()*+,-./0123456xiayou[W\W]W^WyoshihiroQWRWyoshihiroohbaQVRVQVRVRVVֱVֱVjin9DeE Pro 3.0 - 4.1F!"HPro 5.0 A ?G USENGLSH.MPR?GUSER.UPR elements describe the information related to link and physical layers. MDI includes of Data Rate, MAC Type, PHY Type, Link Layer Security, and Link Layer QoS . Each information element in MII and MDI belongs to one of the following two sets, e.g, , the basic set and the extended set. Information elements in the basic set must be supported by all MIH entities. Support for information elements in the extended set is optional. T.c0bAv2c5bA 8@!9bA;^%cA'd$?bB+D2F3v.@@1bA{4CbBcACBGb;IbACHJbBEDJKbAOLbAPCTNbAVObWQcA[Sb]Uc\Xbk[bAaCbEcGdIe\bAgCfEh]bACn^b@iCjEp`cAqa@sbArCuEwAvce@tbACcAgbA}hbA~{ibBAkbAAlbBAm@nbAcxo@cApbAq^rcs{s{ #vproper~WprovoidedeWqualify׀Wquite[W\Wquiteabitofdiscussionpartiicpantswanttounderstandmo[V\Vre-submit~W]W^Wre-submitwithproperfields~Vref)Wreference8Wreferenceonrfcwouldbeworked8VreflectyWregistration{Wregistrationofcommandserviceswouldnotberestricted{Vrelevant>WrequestedUWresolve]W^Wresolved?WJWrestricted{Wrfc8Wsap4WsecondoWservices{Wshould4WsidelWidelWlWlWW֝W֞W֟WsubmitoWsubmitagainwithcorrectpagenumberoVtable֠WtextpWrWsWtWuWwWyWzW{WօW֌W֍W֎W֒W֓W֕W֖W֗W֙W֚W֛W֜W֝W֞W֟WtextnotavailableinthenewversionօVtheyWօW֏WthisyWtimeyWto}W֠Wupdated֌WuseryWversionօWwithoWyW~WցW€Wvspecify0Wspecifyclearlythatsuchacommandisonlyapplicabletoth0Vth0V0V0VeWtableoWterminal0WlWtext֗W֞W>WeWyWthat0W׀Wthe)W,W.W0W>W]W^WeWlWoWyW׀WׁWthesecondlastcolumnisemptytable1and2oVtheir]W^Wthis.W?WJWtimevWto-W0W>W?WJW[W\W]W^WeWlWoWyW׀WׁWtobediscussedafterallcommentsareresolvedduringthis?VJVtobetrackedbythetodolistacontributionlistiingthel׀Vtodo׀WׁWtracked׀WׁWtrackedbythetodolistthedetailsoftheprimitivealsonׁVtracking.WuliseseWunderstand[W\WuntilvWupdate)Wupdatebasedon1116and3gpprefmodelsacceptedbythegr)Vusing,Wvote:Wwant[W\Wwhere,Wwho]W^Wwith~W]W^WׁW]W^W{Wbreplace֞W!W"W#W$W%W&W*W8W9W;W>W@WAWBWCWDWEWHWIWKWLWMW{~W׀ׄW֙W֞W֣W֣W֣W֣W֣WW֣W֣W֣W֣WW֣W֣WWֆWWjWlWnWqWvW|WWրWօWֆWֆWֆW|WWրWօWֆWֆWֆW|WWրWօWֆWֆWֆW|WWրWօWֆWֆWֆWWօWֆWֆWօWֆWֆWրWօWֆWֆWֆWրWօWֆWֆWֆWրWօWֆWֆWֆWWֆWֆWֆWֆWֆWWօWֆWֆWֆWֆWֆWֆWֆWWjWlWnWqWvW|WWրWօWֆWֆWօWֆWֆWnWqWvW|WWրWօWֆWֆWօWֆWֆWֆWnWqWvW|WWրWօWֆWֆWֆWֆWֆWֆWWօWֆWֆWֆWֆWWWreplace6.1.5primitivesforlinklayereventsby6.1.5primVction;"EPeretzFFeder^Technical, Non-binding_19a5.5.1 revision for the text and figures in Section 5.5 (MIH Reference Models for Access Networks). The rationale for the next few comments is to provide clearer and less intricate pictures and descriptions than the current ones. The sections are not meant to be final, as the technology-specific instantiations of the MIH_NET_SAP (SAP between MIH and Transport Plane) are subject to the finalization of the MIH Communication model. With the exceptioBn of the reference to MIH_NET_SAP, everything else is well aligned with the current content of Section 5.6 (Service Access Points). A few details in the technology-specific models may need to be fixed, for which any contribution from the whole group is welcome.d1vcontinuing workwDeferred for next meeting 2005/12/01 2005/11/063"EPeretzFFeder^Technical, Non-binding_19a5.5.1'bThe item should be noted as Informative since MING is only discussed in one of the Informative annexes. The name of the IE should be made generic such as "Neighbor_List_Available"c=Table 7, entry 11still refers to a MING_List_Available item. d7w Superceded{l) none needed 2005/12/07 2005/11/067(EVivekFGupta^Technical, Non-binding_21`20a5.5.3bTPlease insert the section 5.5.3 from contribution 21-05-361-01-0000-Section5_ChangescWUpdate the Reference model and associated text for 802.16 as per discussions in telecond1p!Updated 802.16 reference diagram.wAccepted{k) done 2005/12/07 2005/11/03Fig 6)EVivekFGupta^ Editorial_24`1a5.6bMUse new reference diagram for 802.16 from 21-05-0361-01-0000-Section5_Changesc7.1.3 should be moved to be under 7.1.1 as media dependent SAPwAccepted-Modified{k) done 2005/12/07 2005/11/035EVivekFGupta^Technical, Non-binding_49`22a Section 7bn service primitives in this section.d110vMSpecify clearly that such a command is only applicable to the terminal devicewAccepted-Modified{k) done 2005/12/07 2005/11/031EVivekFGupta^Technical, Non-binding_38`30a6.2.6.2bAfAdd the following link layer commands in section 6.2.6.2. They have alredy been defined in section 7.2 (Table 8) LinkCapabilityDiscover : Set ofevents and commands supported by a link LinkEvent Register: Register to receive local link layer event notifications LinkEventDeregister: Deregister from receiving local link layer event notificationsfciFollowing link layer commands are missing LinkCapabilityDiscover, LinkEvent Register, LinkEventDeregisterd10pAdded link commands in tablewAccepted{k) done 2005/12/07 2005/11/032EVivekFGupta^ Editorial_48`1a6.3.5bhInsert a table and specify Information Service primitives: Link_Get_Information and MIH_Get_Information.! 5bAUpdate section 7 from contribution 21-05-0402-00-0000_Section7_Changes. Key Changes: SAP definitions and their list of primitives are stated upfront in the section. Added Link_Configure_Thresholds primitive Added LINK_Get_Information primitives Fixed several editorial anomalies cNUpdate entire section 7 as per guiidelines issued last time based on SAPs etc.d14wAccepted{k) done 2005/12/07 2005/11/036EVivekFGupta^ Editorial_70, 74`1a Section 7bNRemove reference to Table 7.1, 7.2. Remove reference to Link Configure commandc!Updtae discrepancies in Section 7d15p7Changed Link Configure to Link Configure Threshold.... wAccepted{k) done 2005/12/07 2005/11/03imitives are stated upfront in the section. Added Link_Configure_Thresholds primitive Added LINK_Get_Information primitives Fixed several editorial anomalies Link_Configure_Thresholds primitive Added LINK_Get_Information primitives Fixed several editorial anomalies  58EMathieuFPERESSE^Technical, Non-binding_25`49a5.2.hbReplace h) with the following text: h) The standard shall specify mechanisms to support network-initiated, network-controlled, MN-initiated, and MN-controlled handovers. Definition of these types of handovers can be found in [RFC3753].cSHandover types description needs more acuracy. Use RFC 3753 definition for a start.d1v Reference on RFC would be workedwAccepted-Modified{k) done 2005/12/07 2005-10-079EMathieuFPERESSE^Technical, Non-binding_29`11a5.4.3bmore acuracy. Use RFC 3753 definition for a start.d1v Reference on RFC would be workedwAccepted-Modified{k) done 2005/12/05 2005-10-07uracy. Use RFC 3753 definition for a start.d1v Reference on RFC would be workedwAccepted-Modified{k) done 2005/12/05 2005-10-07ial_47`48a6.3.5bBUpdtae reference to figure numbers 8.6.1 and 8.6.2 in this sectionc!Incorrect figure numbers are usedd12h*EVivekFGupta^Technical, Non-binding_41`11a6.3.2bA=Remove all tables from section 6.3.2 and replace with table in contribution 21-05-400-00-0000-Information Elements. Insert other text from abovecontribution in section 6.3.2 as well. Do not classify IEs as Media independent/Media dependent. Do not include a classification as basic set/Extended set. Remove Figure 22.=cUpdate section 6.3.2 on description of IEs with new table from discussions in telecons. (Also harmonize with comments 135 -141 from September 2005 meeting).d3wAccepted{k) done 2005/12/07 2005/11/031/03L#EPeretzFFeder^Technical, Non-binding_20a5.5.2bReplace current figure 5 with a more simplified version of the figure as described in contribution 21-05-0423-00-0000 along with explaining text.cbContribution 21-05-0423-00-0000 with a proposed revision for the text and figures in Section 5.5.2d3w Withdrawn{l) none needed 2005/12/07 2005/11/065$EPeretzFFeder^Technical, Non-binding_21a5.5.3bReplace current figure 6 with a more simplified version of the figure as described in contribution 21-05-0423-00-0000 along with explaining text.-00-0000 with a proposed revision for the text and figures in Section 5.5.2d3w Withdrawn{l) none needed 2005/12/01 2005/11/065$EPeretzFFeder^Technical, Non-binding_21a5.5.3bReplace current figure 6 with a more simplified version of the figure as described in contribution 21-05-0423-00-0000 along with explaining text.*+>d7v-Only chnage the text relevant to comment # 31wAccepted-Modified{k) done 2005/12/07 2005-10-071?EMathieuFPERESSE^Technical, Non-binding_28`7a5.4.1bA5.4.1.1 Event origination Events can indicate changes in state and transmission behaviour of the physical, medium access layers and logical link layers, or predict state changes of these layers. Events can also indicate changes in state of network layers (GPRS Mobility Management (GMM) layer state, Packet Data Protocol connectivity state). The Event Service can be used to indicate management actions or commands on part of network or some such management entity Events can also originate frReport.doc". This contains a new section which describes the Link_Parameters_Report primitive.cing text: "MIIS primarily provides a set of Information Elements (IEs), the information structure and its representation. The transfer of such information may be either based on a query/responseon a query/response'~;^Technical, Non-binding_27`62a5.4bAReplace the original text with: "Mobile terminals employing the MIH services would receive indications from various layers in either a synchronous manner (i.e. on a regular basis) or an asynchronous manner (i.e. trigger based), using the Event Service. For handover control, messages will be exchanged through the Command Services using a synchronous query/response type mechanism. For handover related information transfer, messages will be exchanged through the Information Service using eitBNher a query response/type mechanism or a push mecanism (unsollicited reports). Add the following text after [paragraph 4]: The link status of a UE varies with time and terminal mobility. Information provided by MIES and MICS is dynamic information comprising of link parameters such as signal level, link speed, etc, whereas information provided by MIIS is less dynamic or static in nature and is comprised of parameters such as network operators, higher layer service information, etc. MIES, MICS and MIIS Information could be used in combination by the terminal/netw(*  Remove the Original Text in section 6.1.2*cAU[After paragraph 4], we should add a paragraph that states the difference between static and dynamic information in MIH exchanges. Note: The paragraph is currently located in section 6.2.1 [paragraph 2], but the dynamic information is only related to MICS (not MIES). MIES is used to carry Parameters Reports, which is dynamic information. Ud5pMIES does not get information. MICS may retrieve information. The original comment in section 6.2.1 seems fine and no new comment seems to be neeed in 6.1.2.wAccepted{e) editor disagrees 2005/12/07 2005-10-07=EMathieuFPERESSE^Technical, Non-binding_41`9a6.1.2bereas information provided by MIIS is less dynamic or static in nature and is comprised of parameters such as network operators, higher layer service information, etc. MIES, MICS and MIIS Information could be used in combination by the terminal/netw)$ =bA}Add the following text at the end of bullet 1): 2) Link Parameters events: These events correspond to indications of lower layers parameters. These events are triggered either synchronously (i.e. on a regular basis) or asynchronously (i.e. when a value of a given parameter crosses a specific threshold). For example, the primitive Link_Parameter_Change is a Link Parameter event.}cARIn 1): State changes events refer to changes in the connectivity state (connected, disconnected), not in link parameters (not directly related to the state of the interface). Therefore a new event type, called "Link Parameters Events", should be defined. Link Parameters Event include Link_Parameters_Change and Link_Parameters_Report)Rd6wAccepted{k) done 2005/12/07 2005-10-07>EMathieuFPERESSE^Technical, Non-binding_45`4a6.1.6bFReplace Table 1 with Table in file "21-05-0xxx-00-0000-Event_List.doc"c3Table 1 needs to incorporate Link Parameter events.$2 ?bBom the MIH Function, in which case the MIH Function acts as the event relay. 5.4.1.2 Event destination The destination of an event may be the MIH Function or any upper layer entity. The recipient of the event can be located within the stack that originated the event, within a remote stack or both. The destination of an event is established dynamically with a registration mechanism that enables an endpoint to register its interest in particular event types. 5.4.1.3 Event flow In case of lCocal events information typically propagates upwards from the lower layers (PHY, MAC, GMM...) to the MIH Function and from MIH Function to upper layers. Information might also propagates downwards (e.g. L3 connectivity state) to the MIH and upwards from MIH to upper layers. In case of remote events information may propagate from lower layers or upper layers via MIH Function in one stack to upper layers in another stack via its MIH. One of the above endpoint stacks may be present in a clien/|bconfigure0W5W6WLWtWW׀WׁWconfigured]WconfirmzWW׀WׁWconnected?WconnectionaWconnectivity?WiWlWyWconsideration0WCWconsiderednWconsistentuWconsuming/Wcontain׃Wcontains:WiWcontentaWcontents:Wcontext?Wcontrasts9Wcontribution!W"W#W$W%W&W(W*W.W4W5Wcontrol;WJWKWLWNWcontrolledyWcontrolseWconvenience/WconveyedeWcopenWcorrespond=WcorrespondingAWdWeWoWtWvW9W;Weach0Weditorial5Weither9W;Welement.Welements*W9Wemploying;Wend=Wentity/Wetc/W<Wevent/W0W1W9W;Wevents/W=Wexchanged;Wexecute0Wexecuted0Wexecution0Wexplaining!W"W#W$W%W&Wexpose/Wfacilitate<Wfalls0W0bwhich/W0W:W?WAWJWKWRW[W\W]WiWlWoWuWwhile?Wwill;W?WaWtWwirelessaW31?vDTo be discussed after all comments are resolved, during this meetingwDeferred for next meeting{l) none needed 2005/12/07 2005-10-07yers, or predict state changes of these layers. Events can also indicate changes in state of network layers (GPRS Mobility Management (GMM) layer state, Packet Data Protocol connectivity state). The Event Service can be used to indicate management actions or commands on part of network or some such management entity Events can also originate frBom the MIH Function, in which case the MIH Function acts as the event relay. 5.4.1.2 Event destination The destination of an event may be the MIH Function or any upper layer entity. The recipient of the event can be located within the stack that originated the event, within a remote stack or both. The destination of an event is established dynamically with a registration mechanism that enables an endpoint to register its interest in particular event types. 5.4.1.3 Event flow In case of l,bcould<WCWcouplingeWcoverkWcrossed0Wcrosses=Wcurrent!W"W#W$W%W&W?W`WyWdata?WJWLWaWiWkWlWnW׃WUWVWWWXWYWZWdealDWdecidediWdecisioneWiWkWdecisionsCWJWdefault/WdefensiveDWdefined/W1W?WEWLWPWbWcWiWjWlWmWdefinition8Wdefinitions5WdelayaWeWdelete+Wdeletemobilitymgmtprotocolsupporttypebitmap+VdeliveredeWdemandsaWdependent*WdependingLWkWdependingonwhetheritisthemobilenodeorthenetworkitkVderegister1Wdescribed!W"W#W$W%W&Wdescribes:WOWdescriptionIW[W\W]W^WdesiredaWdestination?WJWdestinationsCWdetect?Wdetecting]WeWdetectionaWdetermineIWLWdetermineddWdeterministiceW^-:bvaries<Wvarious;WCWEWvendor/technology0Wversion!W"W#W$W%W&Wvia?WJWview@WvoipaWwaitingaWwantFWweuW|Wweproposetodeletethemihserviceidentifiermihfunction|VwerequesttomergethetwotablesandprovideaconsistentuVwell*W0WJWLW[WaWwell-placedyWwell-suitedyWwhen0W=WDWaWdWiWkWnWtWwheneverlWnWwhere<W?Wwhereas<Wwhether\W]WaWkWlWlWlW.=@EMathieu FPERESSE^Technical, Non-binding_14a1.2triction on the direction of the event messages should be made. -> There is a need for Events to be able to originate from the Upper Layers. Such upper layers events could be used to further facilitate and optimize Media Independent Handovers. For example, IP connectivity state could be reported from the IP layer and then reported to another entity via the MIH Function. -> Introduce bidirectionnality for Events between MIH and UL. Also, thBe text should not specify MIH users as L3MP but rather "MIH users". Also, Event messages are independent from the technology the event message is transmitted on.d8vDTo be discussed after all comments are resolved, during this meetingwDeferred for next meeting 2005/12/05 2005-10-07@EMathieu FPERESSE^Technical, Non-binding_14a1.2ration mechanism that enables an endpoint to register its interest in particular event types. 5.4.1.3 Event flow In case of l+3 ?bDt or mobile terminal type of device while the other may be present in a fixed network entity. This entity can be a point of attachment or any node not directly connected to the other stack. 5.4.1.4 Event service use cases and functions The event service will typically be used to detect need for handovers. For example an indication that the link will cease to carry MAC SDUs at some point in the near future may be used by upper layers to prepare a new point of attachment ahead of the currenEt point of attachment ceasing to carry frames. This has the potential to reduce the time taken to handover between attachment points. Events defined include Link Up, Link Down, Link Parameters Change, Link Going Down, and L2SDU Transmission Status, Link Event Rollback, Pre trigger (L2 Handover Imminent), Packet Data Protocol connectivity state, etc. Events may carry additional context data. For example a Link Up event may carry information including layer 2 & layer 3 identification, ident2. ?bFifier of serving entities where these identifiers can be acquired. A link UP may also carry IP address renewal indication which can inform upper layers of the need to initiate a layer 3 handover This can serve to improve the performance of layer 3 handovers.  cAReorganization of section 5.4.1 is needed: No restriction on the direction of the event messages should be made. -> There is a need for Events to be able to originate from the Upper Layers. Such upper layers events could be used to further facilitate and optimize Media Independent Handovers. For example, IP connectivity state could be reported from the IP layer and then reported to another entity via the MIH Function. -> Introduce bidirectionnality for Events between MIH and UL. Also, thBe text should not specify MIH users as L3MP but rather "MIH users". Also, Event messages are independent from the technology the event message is transmitted on.d8a new point of attachment ahead of the currenA{l) none needed 2005/12/07 2005-10-07BEMathieuFPERESSE^Technical, Non-binding_30`22a5.5bKReplace with figure in file "21-05-0xxx-00-0000-General_MIH_ref_model.doc" cTFigure 3: The figure needs to be updated to include Upper Layer Events and Commands.d11w Withdrawn{l) none needed 2005/12/07 2005-10-073CEMathieuFPERESSE^Technical, Non-binding_40`14a6.1.1bAReplace the first and second paragraphs with: "In general, handovers can be initiated either by the mobile terminal or by the network. Events that can influence handover decisions may originate from lower layers, MIH Function or upper layers, either at the mobile node or at an entity in the network. Event generation could be due to UE mobility, state change in the environment or because of some management function on part of the network. Thus the source of these events can be either local. IP connectivity state) d10w Withdrawn 2005/12/05 2005-10-078bdevice?WJWLWdevicesyWdhcpv6[W\Wdiagram)WdiagramsGWHWMWOWdiffereWdifferencesNWdifferentLW]WaWeWuW{WdirectionsuWdirectly?WdiscoverW׀WׁW׃Wdiscussed'WdispatchingCWdistinguish]WdividedEWIWdo*WeWdoc:W>W@WBWGWHWMWOWSWTWUWVWWWXWYWZW`Wdocument:WSWTWUWVWWWXWYWZWdoesiWlWdoneIWdown?WiWׂWdownwards?WJWdraft}WdueCWiWduringaWdynamic<WAWdynamically?We9W;W=W?WJWNW\WaWeWiWlWnWeach0WIW{Weditor'saWeWeditorial5WenableLWaWenabledeWenableriWenables?WJWKW[W\Wend=WFWNWOWend-to-endaWendpoint?WengineJWentirefW7bfound8WfourthEWframe0Wframes?WaWfrom(W)W*W,W.W/W1W4W5W;W?W@WCWDWEWFWJWLWNWaWdWeWiWkWlWyWfunction?W@WCWEWFWIWJWKWLWNWeWiW|WׁWfunctions?WCWJWLWfurtherEWfuture?WeWg?WJWNW\WaWeWiWlWnWgeneral~W@WCWׁWgenerallyJWgenerateddWiWkWlWnWvWgeneratingEWgenerationCWgeneric'Wget2W5WLWgiven=Wgmm?WJWgoing?WiWׂWׂWindicate/W?Windication+W?Windications;W=Winformation.W2W5W9W;W<W?Winformative'Winitial0Winitiate0Winsert(W*W2Winsertatableandspecifyinformationserviceprimitivesli2Vinterest?Winterested/Winto,Wip+W6Abgprs?WguaranteeiWh8WhandoffyWhandover;W<W?WCWLW[W^WaWeWgWhWiWkWlWnWwW{WW׀WׁWׂWhandover/switchingeWiWkWlWnWhandover/switchoverlWhandovers8W?WCWKWLWaWiWlWhardnWhas?WaWdWeWiWkWlWnWqWhave1WCWEWLWPWaWeWuWhelpCWhelpsaW.W?Wincludetextfromcontribution21-5-401-00-0000-ietlvrepre.Vincluding?WindependentAWindependent/media*Windicate/W?Windication+W?Windications;W=WinfluenceCWinform?Winformation.W2W5W9W;W<W?Winformative'Winitial0Winitiate0W?WinitiatedCWinsert(W*W2Winsertatableandspecifyinformationserviceprimitivesli2Vinterest?Winterested/WCWinto,Wip+W?W9"creport=Wreported?Wts:W<Wrepresentatio.Wrepresentation.Wrequest/response9Wresponse;Wrestricted;Wrestriction?Wrevision!W"W#W$W%W&Wrfc8Wsap!Wsaps4W5Wscenarios:Wschema.Wsection!W"W#W$W%W&W*W2W4W5W6W<W?Wsections!Wsending9Wseptember*Wservice!W2W:W;Wservices;Wshould9W<W=W?Wsignal:Wso:Wsollicited9Wspecific:Wspecified+Wstart8Wstate:W=W?Wstates<Wstatic<Wstatic/quasi-static9Wstrength:Wsubject!Wsuch?Wsuggested;Wsupport9Wsynchronous;Wsynchronously:Wtable'W*W>Wtable1needstoincorporatelinkparameterevents>Vtable7entry11stillreferstoaminglistavailableitem'Vtechnology-specific!Wtelecon(Wtelecons*Wterminals;W8=creports:W<WreposirotyyWrepositoryyWpresentation.WrepresentingOWrequestRWoWwWxWrequestforaconsistentformofeventandcommanddefinitiooVrequest/response9W^WwWrequestedoWrequiredwWresourcewWresourceswWrespectiverWresponse;WaWeWwWxWrestyWrestrictAWCWKWrestricted;WLWrestriction?WrestrictiveyWrevision!W"W#W$W%W&Wrfc8WsamexWsap!WQW^WhWsaps4W5WscanRWscenariovWscenarios:WyWschema.WscopesWyWsdurWsecondCWuWsection!W"W#W$W%W&W*W2W4W5W6W<W?WCWLWNWOWPWSWVWWWXWYWZW[W\W`WfWgWhWvWwWyWsections!WyWseerWseemxWseenpWselected]Wsending9WsentLWRWWDctechnology?Wtechnology-specific!Wtelecon(Wtelecons*Wterm}WterminalvWyWterminal-centricyWterminals;WBCGbzAdd the figure located in section 2.3 in the file "21-05-0xxx-00-0000-Events_and_Commands_diagrams.doc" after paragraph 6)c@Introduce a figure for previously introduced upper layer events d16w Withdrawn{l) none needed 2005/12/07 2005-10-07HEMathieuFPERESSE^Technical, Non-binding_40`50a6.1.2bzReplace figure 11 with the figure located in section 2.1 in the file "21-05-0xxx-00-0000-Events_and_Commands_diagrams.doc"cGReplace the figure to include previously introduced upper layer events.d17w Withdrawn{l) none needed 2005/12/07 2005-10-0711IEMathieuFPERESSE^Technical, Non-binding_44`4a6.1.4bMIH Function as MIH Events. These events can be local or remote. Gc)Upper layers events need to be introducedd15w Withdrawn 2005/12/05 2005-10-07GEMathieuFPERESSE^Technical, Non-binding_41`54a6.1.2 connectivity state) d10 2005/11/17 2005-10-07BEMathieuFPERESSE= ECcAFirst and second paragraphs. -> those need to be more generic and to integrate "Upper Layer Events". As mentionned before, we should not restrict Events from going from Upper Layers to MIH: this is the appropriate section for introducing the "Upper Layer Events" (events that goes from the UL to the MIH). -> Events are informative, so they are not likely to "initiate handovers" but rather "influence handover decisions"d12w Withdrawn{l) none needed 2005/12/07 2005-10-07DEMathieuFPERESSE^Technical, Non-binding_40`27a6.1.1b destinations."6cthe network. Event generation could be due to UE mobility, state change in the environment or because of some management function on part of the network. Thus the source of these events can be either local<> DbAReplace the third paragraph by the following text: "From the recipient's perspective these events are mostly "advisory" in nature and not "mandatory". Entities registered to receive events may also need to deal with reliability and robustness issues associated with these events. Higher layer protocols and other entities may prefer to take a more "defensive" approach when events originate remotely as opposed to when they originate locally."c^Third paragraph: needs to be more generic about the entities that are able to receive events.d13w Withdrawn{l) none needed 2005/12/07 2005-10-07EEMathieuFPERESSE^Technical, Non-binding_40`33a6.1.1b=B EbAReplace the fourth paragraph by the following text: "The Event Service may be broadly divided into three categories: Link Events, MIH Events, and Upper layer events. Both Link and MIH Events typically traverse from a lower to higher layer. Link Events are defined as events that originate from event source entities below the MIH Function and typically terminate at the MIH Function. Entities generating Link Events include but are not restricted to: various IEEE802-defined, 3GPP-defined and B3GPP2-defined interfaces. Upper layer events are defined as events that originate from event source entities above the MIH Function (Upper Layer entities) and typically terminate at MIH Function. Within the MIH Function, Link Events and Upper Layer may be further propagated, with or without additional processing, to local or remote upper layer entities that have registered for the specific event. Events that are propagated by the MIH to the upper layers are defined as MIH Events. The rela^Ebtransfer9W;WnWtransferredFWtransissionaWtransmission?WaWdWkWrWtransmitaWtransmittedaWtransportCWaWiWlWnWtransported֞WtraverseEWtrigger;W?WJWtriggered=Wtriggering]WttheaWkWtwo.WLWpWuWtype+W,W9W;W?W[W\W]W^WeWiWlWpWqWtWwWtypes8W?WeWiWlWpWqWtypically?WEWJWue<WCWulNWunder0W`WyWunidirectionaluWunsollicited9W;Wup/W?WlWWׁWׂWupdate4W5WJWSWTWUWVWWWXWYWZWupdateaccordingtosubmitteddocument21-05-0000-00-0000-iSVTVUVVVWVXVYVZVusenewreferencediagramfor802.16from21-05-0361-01-0000)Vused<W?WJWusefulFWuserKWusersLWusing;WutilizeLWvalue=WF"basynchronous9W;Wasynchronously=Wat=W?WCWEWFWJWOWPWeWattheendofsection6.2.5addafigurethatdescribesuppeOVatthisstagenoupperlayerscommandshavebeendefinedPVattaching[W\Wattachment?W[W\WiWoWuWvWyWattemptaWautonomousiWlWautonomouslyeWavailable'WwWyWavailableresourceliswWbyWback0WbalanceLWbased.W9W;WaWtWbasic*Wbasis;W=W7NXbhere0Whigher<WDWEWLWaWdWhighlyeWhowaWeWkWi9W;W=WeWtWyWiinsection1.2purposeisnotonlytoenablebetterusereyVimodifycmdconfiguretoindicatethetypeofparameterandtVidׂWidentification?Widentifier?WRW]W|WׂWidentifiers?Widentifies[WidentifyaWie'W.Wieee802-definedEWies*W9Wif.W0WIW]WaWuWxWiitWyWiidefineanewcommandtViiitWyWiimprovelWillustratesNWNWFWindication+W?Windications;W=WinfluenceCWinform?Winformation.W2W5W9W;W<W?WFWinformative'Winitial0Winitiate0W?WinitiatedCWinsert(W*W2Winsertatableandspecifyinformationserviceprimitivesli2Vinterest?Winterested/WCWIWinterfacesEWinto,WEWIW?W>; EbCtionship between Link Events and MIH events is shown in Figure X, the relationship between Upper Layer Events and MIH Events is shown in FIgure Y " -> Figure Y is added in Commentary #13. cMFourth paragraph has to take into account newly defined Upper Layer events. d14w Withdrawn{l) none needed 2005/12/07 2005-10-07FEMathieuFPERESSE^Technical, Non-binding_41`53a6.1.2bAGAdd the following text at the end of section 6.1.2: 6) Upper layer Events: Upper layers may want to indicate useful information to the MIH. These events originates from the upper layers and terminate at the MIH Function. These events may be transferred from the MIH Function as MIH Events. These events can be local or remote. Gc)Upper layers events need to be introducedd15w Withdrawn{l) none needed 2005/12/07 2005-10-07GEMathieuFPERESSE^Technical, Non-binding_41`54a6.1.2o the upper layers are defined as MIH Events. The rela;H IbAAdd upper layer events registration description. Replace 6.1.4 with the following text: Event registration provides a mechanism for interested entities to selectively receive events. Registration may be divided into Link Events Registration, MIH Events Registration and Upper Layer Events Registration. Link Events Registration is performed by the MIH Function with the event source entities in order to determine the events that each event source (link) is able to provide. MIH Event RegisB}tration is performed by upper layer entities with the MIH Function to select the events to receive. It is possible for upper layer entities to register for all existing events or notifications that are provided by the event source entity even if no additional processing of the event is done by the MIH Function. Upper Layer Events Registration is performed by the MIH Function. kc=Upper layer events need to be registered by the MIH Function.d18w Withdrawn{l) none neededS: ctakeEWtalkingRWHJ JbBk layer). The recipient of a command can be located within the stack that originated the command, within a remote stack. 5.4.2.3 Command flow In case of local commands, information typically propagates downwards from the upper layers (policy engine) to the MIH Function and then from MIH Function to lower layers. Information might also propagate downwards to the MIH Function and then from MIH to network layers (e.g. order to trigger an action of the L3MP). In case of remote commands, infoCrmation may propagate from upper layers via MIH Function in one stack to lower or upper layers in another stack via its MIH Function. 5.4.2.4 Command service use cases The commands generally carry the upper layer decisions to the lower layers on local device entity or at remote entity. For example the command service may be used by the policy engine of an entity in the network to request a terminal to switch between links (remote command to lower layers on terminal stack) and perform sub|@/bannexes'Wanomalies5Wanother.W?WCWJWaWoWany0W?WJWQWaWdWeWiWnWuWapplicationaWiWkWapplicationsaWapproachDWare/W0W5W=WDWEWIWLWNWaWeWoWpWtWuWarqaWdWas!W"W#W$W%W&W'W*W/W0W<W?WCWDWEWFWJWLW[WaWbWcWiWjWkWlWmWnWwWyWWׁWׄWassignׂWassociatedDWcupperlayerseventsneedtobeintroducedFVuse8W9W;W}W׀Wused3W<W?WJWQWrWtWyW}WuseryWusers?WusingyWutilizestW|WvaluesqWtWveryyWvia?WwantKWwantsJWwas׃Wway9Wwe<WAWCWKWrW׀Wwelcome!Wwell!Wwell-placedyWwell-suitedyWwhatwWwhenJWwWwhereJWyWwhich!W<WQWRWoWsWvW|WW׀WwhileyWwhole!WJWwill:W;Wwith!W"W#W$W%W&W*W;WKWuW|WWׁWwithinyWword,WworkyWworkscopeyWwould;WoW׀WxxxoWrWsWsWsWsWCEaI 2005/12/07 2005-10-07JEMathieu FPERESSE^Technical, Non-binding_28`53a5.4.2bAThe command service is a facility that enables the control of physical, medium access and logical link layers. Commands can also provide means to control the behaviour of network layers (GMM, Packet Data Protocol, L3MP) 5.4.2.1 Command origination Commands originate from upper layers as well as from the MIH Function (in which case the MIH Function acts as a relay). 5.4.2.2 Command destination The destination of a command may be the MIH Function or any other layer (lower layer and networIt is possible for upper layer entities to register for all existing events or notifications that are provided by the event source entity even if no additional processing of the event is done by the MIH Function. Upper Layer Events Registration is performed by the MIH Function. kc=Upper layer events need to be registered by the MIH Function.d18w Withdrawn 2005/12/05 2005-10-07Gbreplacehwiththefollowingtext8Vreplacemiisprimarilyprovidesasetofinformationelement9Vreplacetable1withtableinfile21-05-0xxx-00-0000-elist>Vreplacetextinsection6.2.1withthefollowingtextLVreplacethefirstandsecondparagraphswithCVreplacethefourthparagraphbythefollowingtextEVreplacetheoriginaltextwith;Vreplacetheoriginaltextwiththefollowingremotecommands֞VreplacethethirdparagraphbythefollowingtextDVreplacewithfigureinfile21-05-0xxx-00-0000-gmihrefmodBVEO #JbDmsequent functions as IP configuration and location update (remote command to upper layer on terminal stack). 7cAThe MIH Commands definition does not mention the possiblity for a command to go from the MIH to the upper layers. Commands could control upper layers to further facilitate and optimize media independent handover control. For example a command could be used to force a Binding Update when needed, and not simply when the Link_Up event is received (in the case where an operator wants to control the whole mobility management process).d19vDTo be discussed after all comments are resolved, during this meetingwDeferred for next meeting{l) none needed 2005/12/07 2005-10-07KEMathieu FPERESSE^Technical, Non-binding_24`62a5.1.9bample the command service may be used by the policy engine of an entity in the network to request a terminal to switch between links (remote command to lower layers on terminal stack) and perform subbabove?WEWabovecontribution*Waccept`Waccepttheproposedtextin21-05-0418-02-0000-cmodeltext`Vyubip+W?WJW]W^WaWlWnWipv4^Wipv6[W\W^Wipv6addrconfstate[W{abpossibleIWpotential?Wpre?Wpre-triggerkWpredict?WeWpredictiveeWpreferDWprefix^Wpremitives^Wprepare?W[W\WaW׀WׂWpresence\Wpresent?Wprevious0W]W|Wprimarily9Wprimitive5W:W=WwWprimitives,W2W5WWׁWprior[W\WproactivelykWproceedinggWhWprocessaWprocessingEWIWpropagate?WJWpropagatedEWpropagates?WJWpropose|Wproposed`Wproposes[W\W]Wprotocol+W?WCWJWJWJWAbimminent?WiWimminentbeforekWimpactaWimportantCWimprove?WaWims\Win!W"W#W$W%W&W'W*W,W.W/W0W1W3W5W8W;W<W>W?W@WAWBWCWDWEWGWHWIWJWLWMWNWOW[W\W^W`WaWeWiWlWnWoWrWsWwWyW{W|W}W׃WׅWWEWNWincludetextfromcontribution21-5-401-00-0000-ietlvrepre.Vincluded^Wincluding?WaW{WindependentAWKWLWeW{Windependent/media*Windicate/W?WFWaWeWlWqWtWindicatedkWindicatesiWlWindicatingeWindication+W?W\W^WaWhWkWlWnWindications;W=WinfluenceCWinfoyWinform?Winformation.W2W5W9W;W<W?WFWJWLW\W^WaWhWiWtWuWxWyWWJP VKbAReplace 2) with: 2) A Media Independent Command Service (MICS) which : - enables MIH user to manage and control link behavior relevant to handovers and mobility. - enables the MIH Function to manage and control upper layer behavior relevant to handovers and mobility. .cIn 2), we should not restrict the commands from going from the MIH to the Upper Layers. Control Entities may want to control the Upper layer with the aid of the MIH.d20w Withdrawn{l) none needed 2005/12/07 2005-10-07LEMathieuFPERESSE^Technical, Non-binding_45`45a6.2.1b after all comments are resolved, during this meetingwDeferred for next meeting 2005/12/05 2005-10-07KEMathieu FPERESSE^Technical, Non-binding_24`62a5.1.9bte entity. For example the command service may be used by the policy engine of an entity in the network to request a terminal to switch between links (remote command to lower layers on terminal stack) and perform subOT LbAReplace text in section 6.2.1 with the following text: Media Independent Command Service refers to the commands sent from the higher layers to the lower layers, as well as to the commands sent from the MIH Function to the higher layers, in the reference model. Upper layers and other MIH users may utilize command services to determine the status of links and/or control the multi-mode device for optimal performance. Command services may also enable MIH users to facilitate optimal handover poBlicies. For example, the network may initiate and control handovers to balance the load of two different access networks. A number of commands have been added to allow the upper layers to configure, control, and get information from the lower layers. A set of command services that are provided by the L2 data link (MAC, functions such as MAC, Radio Resource Management etc. depending upon the L2 access link technology) and PHY should be defined in this specification. The commands are clasb5.4.2.2JW5.4.2.3JW5.4.2.4JW5.5.3(W6$WFWGWׂW6mihlinkdownindicationeventserviceׂV6.1.2<WFW6.1.4IW6.2.1<WLW6.2.4NW6.2.5NWOW6.2.6.21W6.2.6.4PW6.2.6.4upperlayerscommandsPV6.3.2*W6.3.4.W67ׂW67mihlinkgoingdownindicationeventserviceׂV7%W5W7.14W6W~W7.21W6W:WNW7.2.11.1pW7.2.12:W7.2.13rW7.2.14rW7.2.15sW7.2.17.2nW7.2.17.2whengeneratednV7.2.17.3nW7.4.10.1[W7.4.10.2[W8&W1W8.6.13W8.6.23W802.16)W802.16eeWiWlW802.21\Wa!W"W#W$W%W&W*W0W1W2W9W:W;W<W=W?WAWCWDWEWIWJWKWLWNWOW[W\W]W`WaWdWeWiWkWlWnWoWqWaapplicationlWableIWaboutNWdWiWkWbentities?WCWDWEWIWNW{Wentity/W?WCWIWJWRWdWnWentriesrWsWenumeratedpWqWenvironmentCWespeciallyaWestablished?Wetc/W<W?WLWevenIWevent/W0W1W9W;W=W?WAWCWEWIW]WbWcWeWhWiWjWkWlWmWnWoWsWtWzWWׁWׂWeventtypelinksynchronousl2handoveriVevents/W=W?W@WAWCWDWEWFWIW]WaWeWiWlWoWrW}WׁWexample=W?WJWLWaWeWkWexchanged;Wexecute0Wexecuted0WNWeWexecution0WiWkWexisteWexistingIWexistsiWlWning!W"W#W$W%W&Wexpose/Wfacilitate<WLWaWfacilitatingeWfacilityJWfact@WfactoraWfaileddWfailureaWfalls0WfastaWfeedbackaWDcsimplyJWsince`WvWso:WCWsollicited9WsomeuWxWsource|Wspec`WaWeWspecific:W|Wspecified+WWׁWspecify?WsWtWstablized`WstandardyWstart8Wstate:W=W?WAWstatedoWstates<WyWstatic<Wstatic/quasi-static9WstatusrWsWstoreyWstrange׀Wstrength:Wsubject!Wsubnet]Wsuch?WyWsuggested;Wsupport9WtWsupportedQWrWvWsupportedtransportli׃WsupportingyWsynchronous;WeWsynchronously:Wtable'W*W>W\WgWhWqWuWWׁWׂWtable1needstoincorporatelinkparameterevents>Vtable7entry11stillreferstoaminglistavailableitem'Vtable-1oWtable-10ׁWtable-3vWtable-8WtablesoWuWtables2and3aremihcommandsforlocalandremotepurposeuVtaketaketakePV LbCUsified into three categories: MIH Commands, Link Commands and Upper Layer Commands. 1@Af 33  33 33  33. 33fcAAs previously explained, commands should not be restricted from going from the MIH Function to the Upper Layer (example: control of the BU procedure by a control entity). The fact that commands can be sent from lower layers to the the upper layers is not mentionned in this section.d21w Withdrawn{l) none needed 2005/12/07 2005-10-07MEMathieuFPERESSE^Technical, Non-binding_46`40a6.2.3bsReplace figure 16 with the figure in section 2.2. in the file "21-05-0xxx-00-0000-Events_and_Commands_diagrams.doc"cIReplace the figure to include previously introduced upper layer commands.d22w Withdrawn{l) none needed 2005/12/07 2005-10-07NEMathieuFPERESSE^Technical, Non-binding_47`56a6.2.4bnds are clasfcinlinkdownaddrcrecvnobroadcastmsgasanothercuaseo-Vintable10-mihsapprimitivestheopcodeisdefinedforeacׁVintable14themihlinkdownandmihhandovercommitmessagׂVintable8-mihmgmtsapprimitivestheopcodeisdefinedforVinthefollowingtextoranyotherupperlayershouldnotbeQVinclude/W=WBWHWMWqW|Wincludedescriptionformihevents/Vinclusion|Wincorporate>Wincorrect3WyWincorrectfigurenumbersareused3Vindependent:W?WJWindicatesWindicationfWgWhWiWjWkWlWmWnWpWindication/confirm׀Windications;WinfluenceCWinfoyWinformation2W9W:W;W<WAW]W^WpWwWxWyW|WW׀WׁWׂWׄWinformativeCWCWCWCWpendent:VintroducedFWGWHWMWintroducingCWintroductionyWintroductoryyWTW NbAAdd a section about MIH Upper Layer Commands (Commands from MIH to upper layers). Add the following section after the end of section 6.2.4: 6.2.5 MIH Upper Layer Commands MIH Upper Layer (UL) Commands include the commands from MIH Function to upper layers (e.g. MIH Function to MIP, SIP). These commands mainly control the behavior of upper layer entities. Local MIH UL Commands are issued by MIH Function to upper layers in the local stack. Remote MIH UL Commands are issued by MIH FunctionB to upper layers in the peer stack. Figure 7.2 illustrates the differences between local and remote MIH UL Commands. It is to be noted that although MIH UL Commands originate from the MIH Function, these commands are executed on behalf of an MIH-User, not from the MIH Function itself. c0A section on MIH Upper Layer Commands is needed.d23w Withdrawn{l) none needed 2005/12/07 2005-10-07OEMathieuFPERESSE^Technical, Non-binding_47`56a6.2.4V[ObAt the end of section 6.2.5: Add a figure that describes Upper Layer Commands. Add the figure located in section 2.4 in the file "21-05-0xxx-00-0000-Events_and_Commands_diagrams.doc"cPA figure representing Upper Layer commands is needed to illustrate section 6.2.5d24w Withdrawn{l) none needed 2005/12/07 2005-10-07PEMathieuFPERESSE^Technical, Non-binding_49`61a6.2.6.4bzAdd the following 6.2.6.4 section: 6.2.6.4 Upper Layers Commands At this stage no Upper Layers Commands have been defined.c4A new section listing Upper Layer Commands is neededd25w Withdrawn{l) none needed 2005/12/07 2005-10-07QEYoshihiro Ohba^Technical, Non-binding_61`22a7.2.1.1b"Remove "or any other upper layer".com the MIH Function itself. c0A section on MIH Upper Layer Commands is needed.d23w Withdrawn 2005/12/05 2005-10-07OEMathieuFPERESSE^Technical, Non-binding_47`56a6.2.4Z bacquired?Waction0WJWactions?WkWactivitieseWacts?WJWadaptlWadaptationiWnWadd-W1W:W<W=WFWGWIWNWOWPW[WoWtWuWwWadd4rcrecvnobroadcastmsg-Vaddanewsectionintosection7.4.10.1[VaddasectionaboutmihupperlayercommandscommandsfrommNVaddanoptionalparameterqueryresourcelistintomihhandovewVaddanothertableformiheventsorlistallmiheventsintoVscriptionIVadded5WEWLWadditional?WEWIWaddress?WadvisoryDWafter:W<WGWahead?Wall*W,W/WIWallowLWallows0Walong!W"W#W$W%W&Walredy1Walso/W?WDWJWLWan;W?WCWJWand*W,W.W/W1W2W3W5W8W9W<W?W@WAWCWDWEWFWGWHWIWJWKWLWMWand/orLW_Hpupdated802.16referencediagram(Vupdatedfigure1@VupdatesoWupdtaed)WuWupdtaedtable4withbothlocalandremotemihcommandsuVusedoWvalid,Wversion,WvisioSWwant,Wwe,Wwell,W`WwhenVWwithuWword֞Wv1oW11)W16)Wchnical, Non-binding_61`22a7.2.1.1b"Remove "or any other upper layer".collowing 6.2.6.4 section: 6.2.6.4 Upper Layers Commands At this stage no Upper Layers Commands have been defined.c4A new section listing Upper Layer Commands is neededd25w Withdrawn 2005/12/05 2005-10-07QEYoshihiro Ohba^Technical, Non-binding_61`22a7.2.1.1b"Remove "or any other upper layer".cd on behalf of an MIH-User, not from the MIH Function itself. c0A section on MIH Upper Layer Commands is needed.d23 2005/11/17 2005-10-07OEMathieuFPERESSE^Technical, Non-binding_47`56a6.2.4Xbaddthefigurelocatedinsection2.3inthefile21-05-0xxxGVaddthefollowing6.2.6.4sectionPVaddthefollowinglinklayercommandsinsection6.2.6.2the1Vaddthefollowingtextattheendofbullet1=Vaddthefollowingtextattheendofsection6.1.2FVaddtosection7.2aftersection7.2.12thecontentsofthe:VaddupperlayereventsregistrationdescriptionIVadded5WEWLWpWqWadditional?WEWIWkWtWadditionsoWaddress?W[W\W]W^WpW׀WׁWׄWaddressesaWadvisoryDWaffectseWafter:W<WGWNWagainst]Wahead?Wall*W,W/WIWdWoWallowLWyWallows0Walong!W"W#W$W%W&WyWalredy1Walso/W?WDWJWLWeWiWkWlWnWuWyW@WAWCWDWEWFWGWHWIWJWKWLWMWNWOW`WaWbWcWW] QcAaIn the following text, "or any other upper layer" should not be in the text because the primitive is defined for MIH_MGMT_SAP which is defined between lower-layer and MIH Function, not betweeen lower-layer and higher-layer. "This primitive is used by MIH Function or any other upper layer to query and discover the list of supported link layer events."ad1wAccepted{k) done 2005/12/07 2005/11/03REYoshihiro Ohba^ Editorial_87`21a 7.4.9.1.2bjChange the text to: "The identifier of local or peer MIH entity to which the scan request shall be sent."cThe following description for Destination Identifier is talking about MIH Poll command, not MIH Scan. "The identifier of local or peer MIH entity to which the polling request shall be sent."d2wAccepted{k) done 2005/12/07 2005/11/03SE Ulises Olvera^Technical, Binding_19`22a5.5]kUcBCurrent picture is outdated. 5.5.5 (MIH Reference Model for 3GPP2)d3vMore discussion requested.wDeferred for next meeting{l) none needed 2005/12/07 2005/11/068VE Ulises Olvera^Technical, Binding_26`1a5.6.1.4bUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)c/This section is outdated. 5.6.1.4 (MIH-RRC-SAP)d4p>Hard to update text when some SAPs are updated and some not...wAccepted{k) done 2005/12/07 2005/11/06WE Ulises Olvera^Technical, Binding_26`6a5.6.1.5bUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)c/This section is outdated. 5.6.1.5 (MIH-PPP-SAP)d5wDeferred for next meeting{l) none needed 2005/12/07 2005/11/06XE Ulises Olvera^Technical, Binding_26`11a5.6.1.6N number to be provided by chairman)[\SbUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)cyCurrent figure is difficult to read and it is outdated. Please update section: 5.5 (Reference Models for Access Networks)d1pPlease draw pictures in VISIOwAccepted{k) done 2005/12/07 2005/11/063TE Ulises Olvera^Technical, Binding_22`8a5.5.4bUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)cACurrent picture is outdated. 5.5.4 (MIH Reference Model for 3GPP)d2pKUpdated 3GPP Reference diagram. Need better text accompanying this figure.wAccepted{k) done 2005/12/07 2005/11/067UE Ulises Olvera^Technical, Binding_23`6a5.5.5bUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)?02bupdatesection7fromcontribution21-05-0402-00-0000sectio5Vupdatesection7.1fromcontribution21-05-0402-00-0000sect4Vupdated/WlWupdatingaWeWupdtae3Wupdtaereferencetofigurenumbers8.6.1and8.6.2inthiss3Vupfront5WuponLWlWnWupper?W@WAWCWEWFWIWJWKWLWNWOWPWQW]WaWeWiWlWnWupwards?Wuse)W.W/W?WJWaWlWxWusealllinkeventsfromtable-1andalsoexposethemasmih/Vusenewreferencediagramfor802.16from21-05-0361-01-0000)Vused<W?WJWaWiWkWnWusefulFWiWuserKWkWyWusersLWusing;WyWutilizeLWvalid[W^WwWvalue=WtWYxpsections`Wseems<Wseparate4WserveroWshall)W,Wshallbedoneinnextversionofdraftwemightwanttotake,VsinceoWsomeVWspecifyingwWtable0W1WuWtablesWtake,WtextTWVWeWthe4W<WaWyWWtheseWthis)WTWthispictureshallbeupdtaedonceallreferencediagramsha)Vthreshold6Wto֞W,W/W6W<WVWyWtook`Wtransported֞WtrminalyWupdateVWupdated(W)W@WTWVWupdated3gppreferencediagramneedbettertextaccompanyingTVbUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)c/This section is outdated. 5.6.1.5 (MIH-PPP-SAP)d5 2005/11/16 2005/11/06XE Ulises Olvera^Technical, Binding_26`11ated. 5.6.1.5 (MIH-PPP-SAP)d5 2005/11/16 2005/11/06XE Ulises Olvera^Technical, Binding_26`11bcan/W0W8W?W@WCWFWJW]WaWiWkWlWnW{Wcancellation0Wcapability׀WׁW׃Wcarry?WJWtWcase?WJW^Wcases?WJWiWlWxWcategoriesEWLWcategoryWׁWׂWcausesaWcease?Wceasing?WcellyWcellulareWiWlWcertainiWchairmanSWTWUWVWWWXWYWZWchange.W0W=W?WCWRW]WaWeWiWtW}W׃Wchangelinklayereventstolinkeventsinthedraft}VchangethetexttoRVchangedqWyWchanges(W)W4W5W?WAWlWcharacteristicsAWchecklWclassification*WAWclassified0WLWclassify*WclearlyuWclient?WcmdtWco-locatedCWcolumn,WoWuWcombination<Wcommand0W6W;WJWKWLWtW{WׁWׂWkb [bAThis comment proposes a new parameter which enables a mobile terminal to prepare its IPv6 address configuration method in either stateless or stateful manner prior to attaching a new point of attachment. Add a new section into section 7.4.10.1 ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | B Description ---------------------------------------------------------------------------------------------------------------------------------------------------------- ................. | .............. | ................. | ................ ------------------------------------------------------------------------------------------------------------------------------ac [bC------------------------- IPv6AddrConfState | | N/A | This requests the IPv6 address configuration | | | method of new network to which handover | | | needs to be initiated. This is valid only for D | | | remote commands as well as IPv6. --------------------------------------------------------------------------------------------------------------------------------------------------------------- Add a new section into section 7.4.10.2 -----------------------------------------------------------------------------------------------------------------------------------------------bd [bE----------- Name | Type | Valid Range | Description ---------------------------------------------------------------------------------------------------------------------------------------------------------- ................. | .............. | ................. | ................ ---------------------F---------------------------------------------------------------------------------------------------------------------------------- IPv6AddrConfState | BIT MAP | N/A | This identifies the IPv6 address configuration | | | method of new network to which handover | ce [bG | | needs to be initiated. This is valid only for | | | remote commands as well as IPv6. | | | | | | 0 : IPv6 statHeless address configuration | | | 1: IPv6 stateful address configuration (DHCPv6) | | | 2: IPv6 manual configuration | | | 3: N/A or reserved ----------------dg i[bI-----------------------------------------------------------------------------------------------------------------------------------------------@A  33  33        33)    c*Add a new section into section 7.4.10.1 d1vPQuite a bit of discussion. Partiicpants want to understand more before adopotingw Withdrawn{l) none needed 2005/12/07 2005/10/26\ESoohong, XiayouF Park, Liu^Technical, Non-binding_43`22a6.3.2b---------------------------------------------------------------------------------------------------------------- ................. | .............. | ................. | ................ ------------------------------------------------------------------------------------------------------------------------------gh \bC | ---------------------------------------------------------------------------------------------------------------------------------------------------------- ..................................... | .............................. | ................ | ............................. -----------------------------------------------------------------------------------------------------------------------------------------------D------------ IPv6 Address Configuration | IPv6 Address configuration | N/A | 802.21 specific methods, e.g., a new flag, Method | method supported by the | | query/response. | new network: Stateless IPv6 | | | Address Configuration, Stateful | ef \bAThis comment proposes a new information in which enables a mobile terminal to prepare its IPv6 address configuration method either stateless or stateful manner prior to attaching a new point of attachment. --------------------------------------------------------------------------------------------------------------------------------------------------------- Name of Information | Description | Media Type | Comments ----------------B------------------------------------------------------------------------------------------------------------------------------------------ IMS Access (MSS, SMS, | Indication whether specific | N/A | 802.21 specific methods, e.g., a new Presence, Instant Message, | service is supported or not | | flag, query/response Push-to-Talk, ...) | | f l\bE | | IPv6 Address Configuration | | | (DHCPv6), or IPv6 Manual Configuration | | --------------------------------------------------------------------------------------------------------------------------------------------------------------  =@A  x  y      33    33cGAdd a new element into the MIIS Elements (Table 6 of section 6.3.2) d2vPQuite a bit of discussion. Partiicpants want to understand more before adopotingw Withdrawn{l) none needed 2005/12/07 2005/10/266]ESoohong, XiayouF Park, Liu^Technical, Binding_55`8a7.2.7.1bag, query/response Push-to-Talk, ...) | | nj^bAExpanding MIH_SAP_Premitives to take an indication of IP subnet before handover MIH_Handover_Address_Information.request ------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | Description ----------------------------------------------------------------------------------B--------------------------------------------------------------------- oPoA Subnet | IPv4 subnet mask | N/A | Subnet information of old PoA (Access Router). Information | IPv6 network prefix | | In case of IPv4, subnet mask is included. | | | in case of IPv6, network prefix is incip ^bCluded. -------------------------------------------------------------------------------------------------------------------------------------------------------- MIH_Handover_Address_Information.response ------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | DescriptionD ------------------------------------------------------------------------------------------------------------------------------------------------------- nPoA Subnet | IPv4 subnet mask | N/A | Subnet information of new PoA (Access Router). Information | IPv6 network prefix | | In case of IPv4, subnet mask is included. | \aXbUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)c/This section is outdated. 5.6.1.6 (MIH-LAC-SAP)d6wDeferred for next meeting{l) none needed 2005/12/07 2005/11/06YE Ulises Olvera^Technical, Binding_27`36a5.8.2bUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)c2This section is outdated. 5.8.2 (3GPP Amendments)d7wDeferred for next meeting{l) none needed 2005/12/07 2005/11/06ZE Ulises Olvera^Technical, Binding_27`45a5.8.3bUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)c2This section is outdated. 5.8.3 (3GPP2 Amendments)d8w Withdrawn{l) none needed 2005/12/07 2005/11/06[ESoohong, XiayouF Park, Liu^Technical, Binding_78`43a7.4.10.1b----------bmessages;W{WׂWmethod[W\Wmethods\Wmgmt+Wmics<WKWmies<WAW]W{Wmight?WJWiWmih/W0W2W;W?W@WBWCWEWFWIWJWKWLWNWRW]W^WiWlWoWwWxW{W|W׀WׁWׂW׃WׄWmih-userNWmihfyW{Wmiis9W<Wming'WminimizekWmipNWmmobileaWmn-controlled8Wmn-initiated8Wmobile;W?WCW[W\W]WaWiWkWvWyWmobility+W<W?WCWKWeWmodel~W/W9WBWLW`Wmodification|Wmodified@WmodifytWyWWׁWmoduledWmore!W"W#W$W%W&WDWmostlyDWmove,Wmsg-Wmss\WmtuaWmuchkWmulti-modeLWmultiple0WCWmust@WeWyWn/a[W\W^Wname'W,W[W\W]W^WpWqWwWwWwWcaddanewlinklayercommandlinkconfigurethresholdstoco0Vaddanewsectionintosection7.4.10.1[Vadded׃Wadding`Waddition9WqWaddress]W^WpWxW|WׄWaffectedqWafter<Wafterparagraph4weshouldaddaparagraphthatstatesthe<VaidKWsWaimsyWaligned!Wall+WvWyW{W|W׀Wallspecifiedparametersaspartoflinkupmaynotbealway+Vallow:WyWallowed{WalreadyrWxWxWxW$W%W&W(W;W<W=W?W@WBWCWJWQWSW`WnWoWpWqWandfiguresinsection5.5.1mihreferencemodelsforaccess"Vandfiguresinsection5.5.2#Vandfiguresinsection5.5.4%Vandfiguresinsection5.5.5&Vanother-W?Wany!W2WQWap/bspWappears,WapplicableoWappliesoWappropriate:WCWare!W1W3W?WCWDWoWpWrWi ]bC | | If same subnet, no triggering upper layer | | | if different subnet, triggering upper layer | | | to initiate IP reconfiguration. -----------------------------------------------------------------------------------------------------------D------------------- @A>  33  ^  33>cThe new subnet address for newly selected PoA may not be known by link layer triggers. A new MIH Events is proposed to identify the new subnet information. vZmembers who objected would work with the commentor to resolve their concerns and re-submitwRejected{l) none needed 2005/12/07 2005/10/26^ESoohong, XiayouF Park, Liu^Technical, Binding_86`48a7.4.14 paddedeWaddedinsection5.3.1tookoutotheradjacentredundantsec`Vaddedlinkcommandsintable1Vaddedmessageinlinkdownindication-Vaddednewtableforlinkcommands0Vadjacent`Wall)WbWand<WVWeWuWareVWas,W`WavailableoWbe֞W)W,W<Wbeen)WbetterTWbothuWcare,Wchanged֞W2W6Wchangedlinkconfiguretolinkconfigurethreshold6Vchangednameofprimitiveinsectio6.3.52Vchangedtoremotecommandsmaybetransportedovernetworkl֞VclarificationseWcolumn,WWcommands֞W0W1WuWcomment<Wcommunication/Wconfigure6WcontentaWdiagram(WTWdiagrams)Wdifferent/Wdoes<Wdone,Wdown-Wdraft,WdrawSWeditedaWeWeditedandaddedtextmayneedmoreclarificationshereeV | in case of IPv6, network prefix is incjq Y^bE| | in case of IPv6, network prefix is included. -------------------------------------------------------------------------------------------------------------------------------------------------------- @Af  336    33e    33fcMA new MIH_SAP_Premitives in MIH_Handover_Address_Information.request/responsevZmembers who objected would work with the commentor to resolve their concerns and re-submitw Withdrawn{l) none needed 2005/12/07 2005/10/28`EQiaobingFXie^Technical, Non-binding_14`62a5.3bAccept the proposed text in 21-05-0418-02-0000-communication_model_text.doc and make it into a new section under current section 5.3 and before the current section 5.3.1.c | In case of IPv4, subnet mask is included. | ps `cA This proposal is to insert a new section to describe the MIH communication model. The adding of the communication model section has been under discussion since the past several meetings and the joint draft text has been stablized enough for insertion into the spec. d1pKAdded in section 5.3.1. Took out other adjacent redundant sections as well.wAccepted{k) done 2005/12/07 2005/11/05luded. | E| | in case of IPv6, network prefix is included. -------------------------------------------------------------------------------------------------------------------------------------------------------- @Af  336    33e    33fcMA new MIH_SAP_Premitives in MIH_Handover_Address_Information.request/response 2005/11/16 2005/10/28`EQiaobingFXiesu abA4) Link Transmission events: These events indicate the transmission status (e.g., success or failure) of higher layer PDUs by the link layer. This information can be used by upper layer to improve buffer management for achieving low-loss or lossless handovers. For example, tThe occurrence of a handover of a mMobile nNode, from one access network (AN) to another will results in the reestablishment of a link layer connection to the target access networkAN. When this occurs the upper layer maBy still have data that have been transmitted over the old link but are not received by the receiver (e.g., The reestablishment of a new link layer connection with target AN causes the link layers of source AN as well as the mobile node to flush out the content of outstanding transmit and retransmit MAC ARQ queues in the old access network as well as the mobile node that is flushed out during the handover). This data will become lost because of the handover. If low-loss or lossless handoverqr5aEQiaobingFXie^ Editorial_30`32a6.1.2bept the proposed text in 21-05-0418-02-0000-communication_model_text.doc and make it into a new section under current section 5.3 and before the current section 5.3.1.cA This proposal is to insert a new section to describe the MIH communication model. The adding of the communication model section has been under discussion since the past several meetings and the joint draft text has been stablized enough for insertion into the spec. d1wAccepted 2005/12/05 2005/11/05aEQiaobingFXie^ Editorial_30`32a6.1.2bBeEQiaobingFXie^Technical, Non-binding_30`22a6.1.2bdetermined that it has received notification from peer entity about successful failed transmission of all any link layer segments corresponding to a higher layer PDU.@A  8  )cO  TT  )c    TT  )c  cHThis proposal is to correct a copy-and-paste error in the existing text.d4wAccepted 2005/12/05 2005/10/30eEQiaobingFXie^Technical, Non-binding_30`22a6.1.2b  33>cfix a copy-and-paste typo.d3 2005/11/16 2005/10/30dEQiaobingFXie^Technical, Non-binding_61`34a7.2.14.2bl, Non-binding_61`34a7.2.14.2bd4 2005/10/30rw abC is desired, the upper layer will attempt to retransmit any lost data over the new link. But before the retransmission can occur, the upper layer needs to first identify the lost data and then re-tag them in its buffer, including updating (if necessary) the source/destination IP addresses and re-fragmentation if the MTU of the new link demands so. The upper layer normally has to rely on the use of retransmission timer and end-to-end feedback (such as the ACK in the application or transportD layer) to identify lost packets. The latency of this lost data detection based on timer and end-to-end feedback often becomes a limiting factor to the handover performance as well as the overall data throughput, especially for time-sensitive applications over long round-trip delay wireless links. The flushing of outstanding radio frames introduces noticeable impact on the performance of end-to-end application especially for real time applications such as VoIP. Link Transmission events can abcThis proposal is to enhance the clarity of the existing Link Transmission events description in the draft spec, in response to the Editor's note.d1pEdited the contentwAccepted{k) done 2005/12/07 2005/10/30bEQiaobingFXie^ Editorial_60`36a7.2.13.1bALINK_EVENT_SOURCE is defined as follows. {Local Node, Remote Node}. Local and remote is referred with respect to origination of requestevent.@A>  33>cfix a copy-and-paste typo.d2pFixed all event indicationswAccepted{k) done 2005/12/07 2005/10/30cEQiaobingFXie^ Editorial_61`28a7.2.14.1bALINK_EVENT_SOURCE is defined as follows. {Local Node, Remote Node}. Local and remote is referred with respect to origination of requestevent.@A>  33>cfix a copy-and-paste typo.d3wAccepted{k) done 2005/12/07u SabE significantly facilitate this process in the upper layer by providing a fast local indication on whether a particular PDU has been successfully transmitted over the link or not. enable lossless inter-technology handovers.This helps the upper layer to quickly identify lost packets and prepare for selectively retransmission of the lost data if needed, without waiting for a retransmission timer expiration or end-to-end feedback. [Editor's Notes: Link Transission Events need to be better explFHained. How are they different than regular MAC/PHY State Change events?] @ and end-to-end feedback often becomes a limiting factor to the handover performance as well as the overall data throughput, especially for time-sensitive applications over long round-trip delay wireless links. The flushing of outstanding radio frames introduces noticeable impact on the performance of end-to-end application especially for real time applications such as VoIP. Link Transmission events canncbTo enhance the defnition and clarify of the existing Link_Handover_Complete.Indication definition.d10wAccepted{k) done 2005/12/07 2005/11/06o origination of requestevent.@A>  33>cfix a copy-and-paste typo.d3wAccepted 2005/12/05 2005/10/30dEQiaobingFXie^ Editorial_61`34a7.2.14.2bALINK_EVENT_SOURCE is defined as follows. {Local Node, Remote Node}. Local and remote is referred with respect to origination of requestevent.@A>  33>cfix a copy-and-paste typo.d3wAccepted 2005/12/05 2005/10/30dEQiaobingFXie^ Editorial_61`34a7.2.14.2b  33>cfix a copy-and-paste typo.d3wAccepted 2005/12/03 2005/10/30dEQiaobingFXie^ Editorial_61`34a7.2.14.2bcanLbinformative'WinfrastructureyWinitial0Winitiate0W?WLW]WiWwW׀WinitiatedCW[WinitiatingiWinsert(W*W2WׂWinsertatableandspecifyinformationserviceprimitivesli2Vinstant\Winter-technologyaWiWlWinterest?Winterested/WCWIWinterfacesEWintermediatenWinto,WEWIWLW[W`WwWintra-technologyiWlWintroducesaWinvolvedeWblow-lossaWlower=W?WCWEWJWLWmac?WLWaWpWmac/phyaWeWmacnewpoapWmade'WeWiWkWmainlyNWmake+W`WoWyW׃Wmakeiprenewalindicationoptional+Vmakethefollowingtextchange׃Vmake-before-breakiWmakingeWmanageKWmanagement?WCWLWaWeWnWmandatoryDWmanner;W[W\Wmanual[W\WmanyeWiWlWmap/W[WmarkoWmask^WMbpacket?WJWiW|WpacketsaWkWnWparagraph<WDWEWGWparagraphsCWparameter0W=W[WnWpWqWtWwWparameters0W:W<W=W?WoWpWpart0W?WCWparticular?WCWaWpassiWlWpasteWpayload|WpduaWdWpdusaWpeerNWRWdWpendingkWperformJWperformance?WLWaWperformedIWperiodkWperspectiveDWphy?WLWphysical?WJWplease(Wpleaseinsertthesection5.5.3fromcontribution21-05-361-(Vpoa^WpWpoint?W[W\WiWpoints/W?WyWpoliciesLWpolicyJWpoll׀WׁWpossibilityeWeWeWFband/orLW~ gbA10 Link Synchronous Link Handover Proceeding 101 Link Synchronous Link Handover Complete 101+ Reserved Reserved@A   J  33K  L  M  N        cThis is to propose the removal of Link_Handover_Proceeding.Indication from Table 1, in accordance to the proposal to remove Link_Handover_Proceeding.Indication section.d3wAccepted{k) done 2005/12/07 2005/11/061hEQiaobingFXie^ Editorial_49`57a7.2bd2wAccepted 2005/12/03 2005/11/06gEQiaobingFXie^ Editorial_34`29a6.1.6bd is made and executed autonomously, i.e., independent of the upper layer mobility management function. And indicating the occurrence of these link layer handover/switching events to} hbA13 Link Handover Proceeding Indication Event 134 Link Handover Complete Indication Event 145 Link Information Request Request Information 156 Link Information Response Response Information ... ..... .... .... 167+ Reserved Reserved @A  E  G  H  I                    cThis is to propose the removal of Link_Handover_Proceeding.Indication from Table 8MIH_MGMT_SAP Primitives, in accordance to the proposal to remove Link_Handover_Proceeding.Indication section. d4wAccepted~oh{k) done 2005/12/07 2005/11/068iEQiaobingFXie^Technical, Non-binding_61`47a7.2.15.1bA7.2.15.1 Function Link Handover Imminent is generated when a native link layer handover/switching decision has been made and its execution is imminent (as opposed to Link Going Down which only indicates that a link is losing connectivity due to a change in certain link condition such as signal strength, but does not guarantee that an autonomous link switchover has been decided by the link layer)before the handover occurs. It contains information about the new point of attachment of the mo                cThis is to propose the removal of Link_Handover_Proceeding.Indication from Table 8MIH_MGMT_SAP Primitives, in accordance to the proposal to remove Link_Handover_Proceeding.Indication section. d4wAccepted ebC upper layers is highly relevant for facilitating upper layer mobility management decision making.The timing of link layer handover events controls the latency involved in detecting handover at the network layer and thus affects the delay in updating the route tables. A link layer event delivered to a link layer element must be conveyed to the corresponding network layer element in order for the event to have relevance. This coupling between Link Events and Network Events is enabled by L2 Dhandover event type. [Editor's Notes: Link Synchronous Events need to be better explained. How are they different than regular MAC/PHY State Change events]e@A         ff  ff  ff  ff  ff=  ffK  ff>  TTcfunction. And indicating the occurrence of these link layer handover/switching events toZ|balthoughNWambiguityuWan;W?WCWJWNW^WaWeWiWkWnWwWand*W,W.W/W1W2W3W5W8W9W<W?W@WAWCWDWEWFWGWHWIWJWKWLWMWNWOW`WaWbWcWeWiWjWkWlWmWnWoWrWsWtWuWvWxWyW|W~WׁWׂWand/changesoWoWce the clarity of the existing Link Synchronous events description in the draft spec, in response to the Editor's note. @A* 3333*t ebA3) Link Synchronous events: These events indicate to the upper layer link layer activities (not necessarily related to any MAC/PHY state change) that are strongly relevant to upper layer mobility management decision making. Link Synchronous events differ from Link State Change events in that they do not necessarily report a link state change that has occurred in the past. Link Synchronous events also significantly differ from Predictive events in that they are deterministic and do not predBict any future link state change that is only a possibility. An example of Link Synchronous events is the native link layer handover/switching related events that exist in many media types (e.g., cellular, 802.16e). Native link layer handover/switching decision is deterministic (i.e., not just a possibility) and is made and executed autonomously, i.e., independent of the upper layer mobility management function. And indicating the occurrence of these link layer handover/switching events toQb3gpp-definedEW3gpp2-definedEW4"W-W<WaWWׁW4linkeventconfigurerequestconfirmeventV4linktransmissioneventstheseeventsindicatethetransmiaV5#WWׁWׂW5linkupindicationeventV5mihlinkupindicationeventserviceׂV5.3`W5.3.1`W5.4.1.1?W5.4.1.1eventorigination?V5.4.1.2?W5.4.1.3?W5.4.1.4?W5.4.2.1JW ibBbile. It also contains information about any application specific data that might be useful for the application running on the mobile. Link Handover Imminent can be used by upper layers (e.g., transport ) to initiate handover specific adaptation and as an enabler for initiating effective make-before-break handover thereby reducing packet loss due to link layer handovers. This is a link layer event that exists for intra-technology handovers defined in many media types (e.g., cellular, 802.1C6e). MIH can receive the Link Handover Imminent events from the link layer and pass them to upper layer as MIH events for both inter-technology and intra-technology handover cases. Event Type: Link SynchronousL2 Handover. @        d4 2005/11/068 nibAV  7  ff    u  ffd  )c  ff  )c  ff  )c  ff   )c    )c  TT    )cVnk layer handovers. This is a link layer event that exists for intra-technology handovers defined in many media types (e.g., cellular, 802.1C6e). MIH can receive the Link Handover Imminent events from the link layer and pass them to upper layer as MIH events for both inter-technology and intra-technology handover cases. Event Type: Link SynchronousL2 Handover. @information about the new point of attachment of the mod5 2005/11/06b16MW~WW16linkinformationresponseresponseinformationV167hWׂW167reservedreservedhV17~W2=W?WKW[WkWuW{WWׁW2amediaindependentcommandservicemicswhichKV2linkeventregisterrequestconfirmeventV2.1HW2.2MW2.3GW2.4OW21-05-0000-00-0000-iSWTWUWVWWWXWYWZW21-05-0361-01-0000-s)W21-05-0402-00-00004W5W21-05-0418-02-0000-c`W21-05-0423-00-0000!W"W#W$W%W&W21-05-0xxx-00-0000-e>WGWHWMWOW21-05-0xxx-00-0000-gBW21-05-0xxx-00-0000-l:W21-05-0xxx-00-0000-m@W21-05-361-01-0000-se(W21-05-400-00-0000-in*W21-5-401-00-0000-ie.W22*W23ׁW24ׁW25ׁW3!W?W[WeWtWvWyWWׁW3linkeventderegisterrequestconfirmeventV3linksynchronouseventstheseeventsindicatetotheuppereV nkbAV  f  ff    4  ff    ff    ff       (  ffF  \    ff  V layer handover/switching on its user data transmission and receipt. For example, to cover the handover blackout period,. Tthe network can pB!roactively start sending the additional data as soon as it is indicated about the event sends the pre-trigger and should expect a request from the mobile specifying how much data it needs to cover the blackout time. This event may be used also as an indication to start buffering packets. @ ibc]To enhance the clarity of the existing Link_Handover_Imminent.Indication function definition.d5wAccepted{k) done 2005/12/07 2005/11/06jEQiaobingFXie^ Editorial_62`10a7.2.15.1bALINK_EVENT_SOURCE is defined as follows. {Local Node, Remote Node}. Local and remote is referred with respect to origination of requestevent. @AR    TT  )c  RcdTo fix a copy-and-paste error in the existing Link_Handover_Imminent.Indication function definition.d6wAccepted{k) done 2005/12/07 2005/11/06kEQiaobingFXie^Technical, Non-binding_62`14a7.2.15.2bynchronousL2 Handover. @ .kbA7.2.15.2 When generated Depending on whether it is the Mobile node or the Network, it is generated when a native link layer handover/switching decision has been made and its execution is imminentbefore the layer 2 handover begins. 7.2.15.3 Effect on receipt Application may take necessary actions to minimize the effect of the pending native link layer handover/switching on its user data transmission and receipt. For example, to cover the handover blackout period,. Tthe network can pB!roactively start sending the additional data as soon as it is indicated about the event sends the pre-trigger and should expect a request from the mobile specifying how much data it needs to cover the blackout time. This event may be used also as an indication to start buffering packets. @breestablishmentaWrefBWreference~W)W/W3W6WLWreferredbWcWjWmWrefersLWreflect@Wregister1W?WCWIWtWzW{WWׁWregisteredDWEWregisteringtWregistration?WIW{Wregular;W=WaWeWnWrelated;WeWrelationshipEWrelay?WJWrelevanceeWrelevantKWeWreliabilityDWrelyaWzblinkthresholdsconfigureisalocallinkcommandthatcanc0Vlinkcapabilitydiscov1Wlinkevent1Wlinkeventderegister1WlinksJWLWaWlist'W5W>WoWwWׁWlistsyWloadLWlocal/W0W1W?WCWEWFWJWNWRWaWbWcWjWmWoWlocallyDWlocated?WGWHWJWOWlocationJWyWlogical?WJWlongaWlosingiWloss0WiWlosslessaWlostaW $lbA  ff4  5  ff6  )cd  TTe  l  TTp  {  )c|  TT}    )c  TT    ff      )c  ff  )c  ff  )c    )c B TT   their data flows by can better adapt their data flows bd8 2005/11/06 kbcYTo improve clarity in the existing Link_Handover_Imminent.Indication function definition.d7wAccepted{k) done 2005/12/07 2005/11/06lEQiaobingFXie^Technical, Non-binding_63`19a7.2.17.1bALink Handover Complete is generated whenever a native link layer handover/switching has just been completed (as opposed to Link Up which only indicates that a link has been brought up for L2 connectivity, but does not indicate that a native link handover/switchover has just been completed by the link layer). Notifying the upper layer of this event can iImprove OSI transport, sSession and aApplication layer responsiveness to autonomous link changes. They can better adapt their data flows b event may be used also as an indication to start buffering packets. @ lbBy resuming flows upon receiving this indication. The upper layer can also use this event to check whether its IP configuration needs to be updated. This is a link layer event that exists for intra-technology handovers defined in many media types (e.g., cellular, 802.16e). MIH can receive the Link Handover Complete events from the link layer and pass them to upper layer as MIH events for both inter-technology and intra-technology handover cases. Event Type: Link SynchronousL2 Handover.@nges. They can better adapt their data flows b event can iImprove OSI transport, sSession and aApplication layer responsiveness to autonomous link changes. They can better adapt their data flows b5R`beffectkWnWvWeffectiveiWeither9W;W=WCW[W\Welement.WeWelements*W9Wemploying;WenableLWaWyWenabledeWenableriWenables?WJWKW[W\Wend=WFWNWOWend-to-endaWendpoint?WengagednWengineJWentirefWbneed?WCWDWaWeWvWneedexplicittextdefiningthescenariomobilegeneratedorvVneeded.WCWaWxWneeds[WaWkWlWneighbor'WneighborhoodyWx}oESrinivasF Sreemanthula^ Editorial_34`5a6.1.6bA1Add another table for MIH events or list all MIH events in the Table-1. Add a column for both tables to mark which are local, remote or both. make corresponding additions and/changes in the event message descriptions for MIH_Event_XXX and Link_Event_XXX and their respective parameters. See attachment #11cng additions and/changes in the event message descriptions for MIH_Event_XXX and Link_Event_XXX and their respective parameters. See attachment #11chould be considered.Notifying a transport layer, by the target Buffer Management entity in response to the hard handover complete indication that data transfer may resume. This may be an indication to stop buffering any intermediate packets. @A  ,  ffs      ff!    )c! 9bAReplace : "MIIS primarily provides a set of information elements (IEs), the information structure and its representation and a query/response type of mechanism for information transfer. This contrasts with the asynchronous push model of information transfer for the event service.", with the following text: "MIIS primarily provides a set of Information Elements (IEs), the information structure and its representation. The transfer of such information may be either based on a query/responseBI type of mechanism, or on a push mechanism (i.e. unsollicited reports) " 7cAjMIIS should also provide a way for MIH Function to asynchronously update Static/Quasi-Static information. MIIS should support unsollicited sending of information, in addition to sollicited (request/response) sending of information. Use case for unsollicited MMIS message, can be: - give the UE a list of neighboring PoAs, depending on the current UE's location.jd2wRejected{l) none needed mEQiaobingFXie^ Editorial_63`44a7.2.17.1bALINK_EVENT_SOURCE is defined as follows. {Local Node, Remote Node}. Local and remote is referred with respect to origination of requestevent. @AR    TT  )c  RcdTo fix a copy-and-paste error in the existing Link_Handover_Complete.Indication function definition.d9wAccepted{k) done 2005/12/07 2005/11/06nEQiaobingFXie^Technical, Non-binding_63`47a7.2.17.2b    TT  )c  RcdTo fix a copy-and-paste error in the existing Link_Handover_Complete.Indication function definition.d9wAccepted{k) done 2005/12/05 2005/11/06nEQiaobingFXie^Technical, Non-binding_63`47a7.2.17.2b Klbc]To enhance the clarity of the existing Link_Handover_Complete.Indication function definition.d8vApplicable to the terminal side and not at the network side. Applicable for intra-technology. May need more motivation/explaination for inter-technologywAccepted-Modified{k) done 2005/12/07 2005/11/06    )c  ff  )c  ff  )c    )c B TT   vtyc 2005/10/30dEQiaobingFXie^ Editorial_61`34a7.2.14.2bAThis notification is generated when link ARQ module has determined that it has received notification from peer entity about successful failed transmission of all any link layer segments corresponding to a higher layer PDU.@A  8  )cO  TT  )c    TT  )c  cHThis proposal is to correct a copy-and-paste error in the existing text.d4wAccepted{k) done 2005/12/07 2005/10/30ises Olvera^Technical, Binding_27`45a5.8.3bUpdate according to submitted document: 21-05-0000-00-0000-InterDigital3GPPAmendments.doc (DCN number to be provided by chairman)c2This section is outdated. 5.8.3 (3GPP2 Amendments)d8w WithdrawnAmendments.doc (DCN number to be provided by chairman)c2This section is outdated. 5.8.3 (3GPP2 Amendments)d8w WithdrawnRbexpanding^Wexpandingmihsappremitivestotakeanindicationofipsub^VexpectkWexperienceyWexpirationaWexplainedaWeWuWexplaining!W"W#W$W%W&WexplicitvWexpose/WextendtWfacilitate<WLWaWfacilitatingeWfacilityJWfact@WfactoraWfaileddWfailureaWfalls0WfastaWfeedbackaWfield|Wfields|W|WׅW ocARequest for a consistent form of event and command definitions. 802.21 Events are classified as MIH events and Link events and are defined as primitives across different layers. However, only link events are defined, but no MIH events are defined. If it is assumed that Table-1 is also applicable to MIH events then it would be clear if it is explicitly stated. Also a consistent notation for the two types of events is requested e.g. Link_ Event_XXX and MIH_Event_XXX. Also request to add a cBolumn in the tables to mark which of Link_Event_XXX and MIH_Event_XXX are local, remote or both. Also applies to discovery and registration.zd1pP21-05-0439-00-0000 used for updates since revision 1 is not available on server.vlModifications to the table as discussed. 21-05-0439-01-0000 The second last column is empty (Table 1 and 2)wAccepted-Modified{k) done 2005/12/07 2005/11/06T1pESrinivasF Sreemanthula^Technical, Binding_58`30a7.2.11.1bhn ]bAIt proposes a new link layer Events of MIES which can support a mobile station to distinguish whether or not its nPoA is a new subnet against oPoA MIH Events ------------------------------------------------------------------------------------------------------------------------------ Event identifier | Event Type | Event Name | Description --------------------------------------------------------------------------------------B---------------------------------------- TBD | IP Reconfiguration | IP Subnet Change | Detecting a new link which is | | | configured by different IP subnet | | | against previous IP address. | x nbA7.2.17.2 When generated This is generated whenever a native link layer handover/switching has just been completedupon completion of L2 handover when link is ready for regular traffic. 7.2.17.3 Effect on receipt Upon reception of this event, an upper layer (e.g., transport) can stop any handover adaptation that it has engaged to cope with the just completed native link layer handover/switching and resume normal data transfer. This event may also be used as an indication that a re-verBification of the IP parameter should be considered.Notifying a transport layer, by the target Buffer Management entity in response to the hard handover complete indication that data transfer may resume. This may be an indication to stop buffering any intermediate packets. @A  ,  ffs      ff!    )c/5bdcnSWTWUWVWWWXWYWZWdealDWdecidediWdecisioneWiWkWdecisionsCWJWyWdefault/WdefensiveDWdefinetWdefined/W1W?WEWLWPWbWcWiWjWlWmWdefiningvWdefinition8Wdefinitions5WdelayaWeWdelete+W|Wdeletemobilitymgmtprotocolsupporttypebitmap+VdeliveredeWdemandsaWdenote|Wdependent*WdependingLWkWdependingonwhetheritisthemobilenodeorthenetworkitkVderegister1WzWWׁWdescribed!W"W#W$W%W&Wdescribes:WOWdescriptionIW[W\W]W^WpWqWwWWׁWdescriptionsoWdesiredaWdestination?WJW|WdestinationsCWdetect?WyWdetecting]WeWdetectionaWdetermineIWLWdetermineddWdeterministiceWeWeWeWq^Technical, Binding_59`7a7.2.12.1bARequest that a new parameter to indicate the type of parameter that has changed is added to the table. Name Type Description -------------------------------------------------------------------------------------------------------------- Link Parameter Type Enumerated link parameter types Media specific parameter typescThe parameters table must include the type of the parameter that is affected e.g. bandwidth, QoS etc in addition to just providing old and new values of the parameter.d3wAccepted{k) done 2005/12/07 2005/11/06rESrinivasF Sreemanthula^Technical, Binding_60`1a7.2.13 and 7.2.14bnRequest to remove section 7.2.13 and 7.2.14 and respective entries of Link Transmission events in the Table-1.r Type Enumerated link parameter types Media specific parameter types pbARequest that two new parameters are added to the parameter table of 7.2.11.1 Name Type Description -------------------------------------------------------------------------------------------------------------- Link Type Enumerated link types Type of link MACNewPoA MAC Address(optional) MAC Address of New PoAcAThe information provided in link detect indication must contain more information about the link for MIH/higher layers to analyse the link.. The following two parameters are seen to be important. 1. Link Type 2. MAC address of AP/BS This information could bederived from broadcast signaling on the new link e.g. beacon. The primitive Link_Event_Detect (and MIH_Event_Detect, ) must have means to carry those parameters.d2wAccepted{k) done 2005/12/07 2005/11/06qESrinivasF Sreemanthulas{l) none needed 2005/12/07 2005/11/06tESrinivasF Sreemanthula^Technical, Binding_73`30a7.4.8.1bAeThere are 3 options to solve this. i) Modify Cmd.Configure to indicate the type of parameter and the corresponding threshold value and add to the table. ii) define a new command iii) Extend some other event.register to carry this information when registering for the parameter_change. Additional information will be provided based on the selected option.ecA`According to definition in 7.2.12 Link Parameters Change utilizes a separate command to specify threshold values for different parameters. It is not clear if the MIH_Configure and Link_configure command primitives are to be used for this purpose. But the current parameter list in the primitive do not support the parameter type and threshold values. `d6w Superceded{l) none needed 2005/12/07 2005/11/06 types Media specific parameter types&brequesteventbWcWjWmWrequests[Wrequired{Wreserved[WgWhWresourceLWresourceswWrespectbWcWjWmWrespectiveoWrWsWresponeׂWresponse^WhWnWwWW׀WׁWׂW׃WׄWnse/type;WresponsivenesslWrestrictedEWresults0WaWresumenWresuminglWretransmission0WaWretransmitaWrfc37538WrobustnessDWrollback0W?Wround-tripaWrouteeWrouter^WrunningiWsameCW]Wsap5W^WscanRW׀WscenariovWschema.Wsdus?WsecondCWsection(W*W.W1W3W4W5W:W<WFWGWHWLWMWNWOWPW[W`WfWrWsWyWsection74W5Wsections,WsecurityCWseeoWuWvWsegmentsdWselectIWselectedtWselectivelyIWaWsendingkWsendskWsentLWRWׄWAv{l) none needed 2005/12/07 2005/11/06wESrinivasF Sreemanthula^Technical, Non-binding_80`54a7.4.11bAAdd an optional parameter "QueryResourceList" into MIH Handover Initiate request as below. Name Type Valid Range Description QueryResourceList To query the available list of resources on the new link Add an optional parameter "AvailableResourceList" in the response primitive as shown below. Name Type VBalid Range Description AvailableResourceList To query the available list of resources on the new link cr to carry this information when registering for the parameter_change. Additional information will be provided based on the selected option.ecQb7.2.15.1iW7.2.15.1functioniV7.2.15.2kW7.2.15.2whengeneratedkV7.2.15.3kW7.2.15.3effectonreceiptkV7.2.16fWsW7.2.17sW7.2.17.2nW7.2.17.2whengeneratednV7.2.17.3nW7.4.1.2׀W7.4.1.2mihcapabilitydiscoverconfirm׀V7.4.1.2mihcapabilitydiscoverresponse׀V7.4.10.1[W7.4.10.2[W׀W7.4.10.2mihhandoverinitiateconfirm׀V7.4.10.2mihhandoverinitiateresponse׀V7.4.11.2׀W7.4.11.2mihhandoverprepareconfirm׀V7.4.11.2mihhandoverprepareresponse׀V7.4.12.2׀W7.4.12.2mihhandovercommitconfirm׀V7.4.12.2mihhandovercommitresponse׀V7.4.14.2׀W7.4.14.2mihnetworkaddressinformationconfirm׀V7.4.14.2mihnetworkaddressinformationresponse׀V7.4.15.2׀W7.4.15.2mihinformationconfirm׀V7.4.15.2mihinformationresponse׀VoWqWtWuWaapplicationlWableIWaboutNWdWiWkWyWcarrows@Wm"calso*W9W?WoWyWW׀WׁWalways+WambiguousvWamendmentsYWZWan:WJWanalysepWand!W"W#W$W%W&W(W;W<W=W?W@WBWCWJWQWSW`WnWoWpWqWsWtWuWwWxWyW|W}WW׀WׁWׂW׃Wandfiguresinsection5.5.1mihreferencemodelsforaccess"Vandfiguresinsection5.5.2#Vandfiguresinsection5.5.4%Vandfiguresinsection5.5.5&Vanother-W?Wany!W2WQW|Wap/bspWappears,WapplicableoWappliesoWappropriate:WCWare!W1W3W?WCWDWoWpWrWsWtWuWvWwWyW|W}WW׀WׁWׂWׂWׅWׅWuESrinivasF Sreemanthula^Technical, Binding_38`46a6.2.5.1bASWe request to merge the two tables and provide a consistent format and remove any ambiguity. Also request to add a new information column to clearly show which commands are unidirectional and bidirectional. Also, if some commands have somehow a different meaning /behaviour on the two directions, it should be explained. See attachment #2SuESrinivasF Sreemanthula^Technical, Binding_38`46a6.2.5.1bASWe request to merge the two tables and provide a consistent format and remove any ambiguity. Also request to add a new information column to clearly show which commands are unidirectional and bidirectional. Also, if some commands have somehow a different meaning /behaviour on the two directions, it should be explained. See attachment #2Sistering for the parameter_change. Additional information will be provided based on the selected option.ec wcAeMIH Handover prepare request and response primitives are capable of querying for required resources for the handover. However, it is not clear based on what information the resource query is generated. It is be reasonable to provide that query information in the Handover initiate request/response primitives (section 7.4.10) when generated from the client.e@A  33d9p;QueryResourceList is a flag specifying query or no query...wAccepted{k) done 2005/12/07 2005/11/06xESrinivasF Sreemanthula^Technical, Non-binding_86`48a7.4.14b^Request to reconsider the use cases for MIH network information and remove them if not needed.cAMIH Network Address Information request and response primitives seem to have the same functionality already defined for fast mobile-ip handover signaling. This may cause some redundancy in 802.21 definitions.@A  33d10wRejected{l) none needed54S5cseparatetW|Wseptember*Wservice!W2W:W;W|WW׀WׁWservices;W{W|WsetyWseveral`WshallRWshould9W<W=W?WAWCWKWLWQWyW{Wshows@WsideyWsignal:WsignalingpWsWxWxWxWxWx 2005/12/07 2005/11/06yESrinivasF Sreemanthula^ Editorial_1`40a1.2bAi) In section 1.2, purpose is not only to enable better user experience but also to enable network controlled handoff ii) Modify the text along the lines of "The mobile terminal is well-placed to detect available networks and make decisions about connectivity. The network infrastructure is well-suited to store overall network information, such as neighborhood cell lists and the location of mobile devices, and to make decisions about mobile terminal connectivity." iii) Section 1.2, b) 3) unBder IS The mobile terminal obtains information from the repository using its current network points of attachment. Must be changed to allow also MIHF in network to access info c 33d8 2005/11/15 2005/11/06wESrinivasF Sreemanthula^Technical, Non-binding_80`54a7.4.11b*u@cv{wcAxycAC{bA|cACbACEGcA׀@bAcAׁbACEGIAׂbACEcׄbA ycAThe introductory/overview/purpose section must describe all the possible objectives of the work scope within 802.21. In this regard, while the rest of the document discusses about how network controlled handovers are possible, it is important that the introductory sections make explicit references to them. These scenarios are very important for the 3GPP/3GPP2 operators to provide attention to the 802.21 workscope. i) The introduction states that "The purpose of the IEEE 802.21 standard is Bto enhance user experience of mobile devices by supporting handovers between heterogeneous networks." This is a restrictive description. The text does not convey the more generic set of scenarios 802.21 aims at enabling. ii)The text states that "The mobile terminal is well-placed to detect available networks" and "The network infrastructure is well-suited to store overall network information, such as neighborhood cell lists and the location of mobile devices." This conveys the incorrect me.2 ׀cAExcept for the primitives of the event service category, all primitives that belong to general, command and information service categories have two different types of opcode; request and response. This response type of primitive is issued by the MIH entity and received by the upper layers, which seems to be strange because request/response types of primitives are typically generated by upper layers and indication/confirm types of primitives are issued by lower layers. Also, if we use theB response type of opcode for the primitives issued by MIH entities, it would be difficult to distinguish MIH Function Messages from MIH_SAP Primitives.d4vsTo be tracked by the todo list. A contribution listiing the list of commands that qualify for confirm be developed.wDeferred for next meeting{l) none needed 2005/12/07 2005-11-05ׁEEunahFKim^Technical, Non-binding_65`7a7.4breemanthula^ Editorial_1`40a1.2blbnametypevalidrangedescription[VnativeeWiWkWlWnWnature<WDWnear?WnecessarilyeWnecessaryaWkW cmeanspWmeant!WmechanismsWmechanisms;Wmedia:W?WJWmeeting*W׃Wmeetings`WmehanismssWmention2WJWmentionnedCWLWmessage9W?WyW|W׃WׄWmessages?W|W׀WׂW׃WmgmtQWhWWmics<Wmies<Wmih!W"W/W9W;W<W?W@WAWCWIWJWKWLWNWQWRWTWUW]W^W`WhWoWpWtWuWvWwWxW{W|W׀WׁWׂW׃WׄWmihhandoverpreparerequestandresponseprimitivesarecapwVmihnetworkaddressinformationrequestandresponseprimitixVmih-lac-sapXWmih-ppp-sapWWmih-rrc-sapVWmih/higherpWmiis9W\Wmiisshouldalsoprovideawayformihfunctiontoasynchron9Vming'WminorzWminoreditorialcorrectionzVzVzVzVWmodels!W"WSWmore8WCWDWpWyWmove,Wmsg-W {bAoReplace: [2] MIH remote registration: Remote MIHF in different entities can register with each other to receive Media Independent Handover Messages including remote MIES. No registration is required for command services. With: [2] MIH remote registration: Remote MIHF in different entities can register with each other to receive Media Independent Handover Messages.oc4Registration should be allowed for all MIH Services.v8Registration of command services would not be restrictedwAccepted{k) done 2005/12/07|EJoughoonFJee^Technical, Non-binding_98`2a8.3.1bAWe propose to delete the MIH Service identifier, MIH Function identifier length, Source MIH Function identifier and Destination MIH Function identifier fields in the previous MIH packet format with modification of message length field to denote only the payload length in bytes.c ycCssage that the network is used only as reposiroty for information, therefore only for IS, and that the 802.21 standard does not consider scenarios where the network can control the handoff. iii) Section 1.2, b) 3) under IS The mobile terminal obtains information from the repository using its current network points of attachment. is terminal-centric and restrictive. Should also allow network side to fetch this info.@A  33d11pLRemoved reference to only mobile trminal retrieving the information from IS.v)modify the text to reflect the discussionwAccepted-Modified{k) done 2005/12/07 2005/11/06zESrinivasF Sreemanthula^ Editorial_54`6a7.2.6.2bCRename Link_Event_Register.request to Link_Event_Deregister.confirmcMinor editorial correction d12wAccepted{k) done 2005/12/07 2005/11/06{EBenjaminFKoh^Technical, Non-binding_97`25a8.3be devices." This conveys the incorrect me |cAFirst problem in the current MIH general packet format is redundant definition of identifiers, MIH service identifier and MIH message identifier. Currently, MIH message identifier field defines separate identifiers for all MIH function messages, which are related with MIH capability discovery, MIH remote event registration and MIH services. Only with this MIH message identifier, the receiving peer MIH function entity can decode the MIH packets and then perform the expected behavior from thBe sending MIH peer. Therefore, the MIH service identifier does not act any active role in the MIH packet processing. Second problem in the current MIH general packet format is the inclusion of L2 or L3 address like MIH function destination and source identifier. Generally, L2 and L3 address are defined in the L2 or L3 protocol itself and this address information is revealed to the functional entity which utilizes the specific transport protocol. Thus, MIH packet format needs not to include?cintroductory/overvieyWinvoked:Wip?WAWcthemihcommandsdefinitiondoesnotmentionthepossiblityJVthemihnetworkaddressinformationresponseistheresponseׄVthenewsubnetaddressfornewlyselectedpoamaynotbekno]VtheparameterstablemustincludethetypeoftheparameterqVthesupportedtransportliwasresolvedtobeaddedinthemih׃Vthewordoptionalappearsintypecolumntypeisnotoptiona,VthemyWthen?WoW|Wthere2W?WuWWׁWthereisnodecriptionormentionofanyinformationservice2Vtherefore=WrWyW|WtheserWyWtheyCWׁWthirdDWthirdparagraphDVDVDVUcinfrastructureyWinitiateCWwWinsert`Winsertion`Winstantiations!WintegrateCWintegratedWׁWinteraction;Winterface=Winto,WEW[W\W`Wintricate!Wintroduce:W?WGWintroduceafigureforpreviouslyintroducedupperlayereveGVintroduceanewprimitivethatwillcarrymediaindependent:VintroducedFWGWHWMWintroducingCWintroductionyWintroductoryyW9crepresentatio.Wrepresentation.WrepresentingOWrequestRWoWwWxWW׀WׁW׃WׄWrequestforaconsistentformofeventandcommanddefinitiooVrequest/response9W^WwW׀WrequestedoWrequiredwWresolved׃WresourcewWresourceswWrespectiverWresponse;WaWeWwWxW׀W׃WׄWrestyWrestrictAWCWKWrestricted;WLWrestriction?WrestrictiveyWrevealed|WׅWsap!WQW^WhWsaps4W5WscanRWscenariovWscenarios:WyWschema.WscopesWyWsdurWsecondCWuW|Wsection!W"W#W$W%W&W*W2W4W5W6W<W?WCWLWNWOWPWSWVWWWXWYWZW[W\W`WfWgWhWvWwWyWsections!WyWseerWseemxWseenpWselected]Wsending9W|WsentLWRWcmissing1WׂWml:Wmme:Wmmis9Wmobile;WvWyWmobile-ipxWmobilityJWmodel!W(W)W;WTWUW`WWׁWmodels!W"WSWmore8WCWDWpWyWmove,Wmsg-W |cCA MIH function destination and source identifier field in itself. wRejected{l) none needed 2005/12/0727}EEunahFKim^ Editorial_33`55a6.1.6b:Change "Link Layer Events" to "Link Events" in the draft. cThe "Link Layer Events" and "Link Events" are used together in the draft. For consistency, use one term for the same meaning. d1wAccepted{k) done 2005/12/07 2005-11-05~EEunahFKim^ Editorial_35`35a6.2.3b+Replace "Figure 7.1" by "Figure 16 and 17".cFigure 7.1 does not exist.d2wAccepted{k) done 2005/12/07 2005-11-05EEunahFKim^Technical, Non-binding_49`30a7.2bs the inclusion of L2 or L3 address like MIH function destination and source identifier. Generally, L2 and L3 address are defined in the L2 or L3 protocol itself and this address information is revealed to the functional entity which utilizes the specific transport protocol. Thus, MIH packet format needs not to includercLink_SDU_Transmit_xxx primitives are used to notify the transmission status of fragments, but these primitives are already supported by respective MAC layers (e.g MA.UNITDATA.xxx in 802.11). Therefore, we see this as a redundant functionality in 802.21.d4w Withdrawn{l) none needed 2005/12/07 2005/11/06sESrinivasF Sreemanthula^Technical, Binding_62`14a7.2.15b_Request to remove section 7.2.15, 7.2.16 and 7.2.17 and respective entries in the event tables.cALink_Event_Handoff_XXX primitives are defined to indicate the status of the handover but look like L2 handover signaling mechanism (which is outside the scope of 802.21). 802.21 can only aid in native or higher layer handover mehanisms but cannot specify a L2 handover signaling procedure between two link types. But, the status of the handover can be obtained directly from the other link events currently defined in 802.21 e.g. link_up, link_going_down and link_down.d5w Withdrawn cAIn Table 8-MIH_MGMT_SAP Primitives, the opcode is defined for each primitive, but it's not fully specified. For example, the "Link Event Register" primitive has two types of opcode : request and confirm. (refer to Figure 14-Link Events Flow Model) But in Table-8, only request type of opcode is described in "Link Event Register" primitive. Also, there are two information service primitives defined for information service, which can be integrated to one primitive with two different types oB f opcode.d3p,Removed the opcode column from these tables.v$Merge Opcode and description columnswAccepted-Modified{k) done 2005/12/07 2005-11-058-------------------------------------------------------------------------------------------------------------------------------------------------------- 2 Link Event Register Request, Confirm Event ----------------------------------------------------------------- bATo modify Table-8 as indicated below. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- No Primitives Opcode Service Category Description ---------------------------------------------------------------------------------------------------------------------------------------B------------------------------------------------ 1 Link Event Discover Request, Confirm Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 2 Link Event Register Request, Confirm Event -----------------------------------------------------------------Nybinclude*W.W?WEWNWincludetextfromcontribution21-5-401-00-0000-ietlvrepre.Vincluded^Wincluding?WaW{WindependentAWKWLWeW{Windependent/media*Windicate/W?WFWaWeWlWqWtWindicatedkWWׁWindicatesiWlWindicatingeWindication+W?W\W^WaWhWkWlWnWWׁWׂWindications;W=WinfluenceCWinfoyWinform?Winformation.W2W5W9W;W<W?WFWJWLW\W^WaWhWiWtWuWxWyWW׀WׁWׂWׄWacrevision!W"W#W$W%W&Wrfc8Wrole|WsamexW}Wsap!WQW^WhWW׀WׁWsaps4W5WscanRWscenariovWscenarios:WyWschema.WscopesWyWsdurWsecondCWuW|Wsection!W"W#W$W%W&W*W2W4W5W6W<W?WCWLWNWOWPWSWVWWWXWYWZW[W\W`WfWgWhWvWwWyWsections!WyWseerWseemxWseems׀WseenpWselected]Wsending9W|WsentLWRWRWRWRW Iclayers֗W;W?W@WAWCWFWJWKWLWoWpWrW׀Wless!Wlike;WsW|WlikelyCWlink֗W+W-W0W1W;W=W>WJWQW]WaWeWfWgWhWiWjWkWlWmWnWoWpWrWsWtW}WWׂWlinkeventhandoffxxxprimitivesaredefinedtoindicatethsVlinksdutransmitxxxprimitivesareusedtonotifythetranrVlinkcapabilitydiscov1Wlinkevent1Wlinkeventderegister1Wlist'W9WQWtWlistingPWlistsyWlocalRWoWuWlocated<Wlocation9WyWlooksWlowerLW׀Wlower-layerQWmarWmacpWrWmade?Wmake.W:WyWmakeacasefortlvrepresentatiobeforethatforschemabas.V.V ׀bAReplace 7.4.1.2 MIH_Capability_Discover.response 7.4.6.2 MIH_Poll.response 7.4.7.2 MIH_Switch.response 7.4.8.2 MIH_Configure.response 7.4.9.2 MIH_Scan.response 7.4.10.2 MIH_Handover_Initiate.response 7.4.11.2 MIH_Handover_Prepare.response 7.4.12.2 MIH_Handover_Commit.response 7.4.14.2 MIH_Network_Address_Information.response 7.4.15.2 MIH_Information.response with 7.4.1.2 MIH_Capability_Discover.confirm 7.4.6.2 MIH_Poll.confirm 7.4.7.2 MIH_Switch.confirm 7.4.8.2 MIH_Configure.confirm 7.4B.9.2 MIH_Scan.confirm 7.4.10.2 MIH_Handover_Initiate.confirm 7.4.11.2 MIH_Handover_Prepare.confirm 7.4.12.2 MIH_Handover_Commit.confirm 7.4.14.2 MIH_Network_Address_Information.confirm 7.4.15.2 MIH_Information.confirm confirm 7.4.15.2 MIH_Information.confirm c4.15.2 MIH_Information.confirm cd4 2005-11-05=׀EEunahFKim^Technical, Non-binding_64`33a7.4b defined for each primitive, but it's not fully specified. For example, the "Link Event Register" primitive has two types of opcode : request and confirm. (refer to Figure 14-Link Events Flow Model) But in Table-8, only request type of opcode is described in "Link Event Register" primitive. Also, there are two information service primitives defined for information service, which can be integrated to one primitive with two different types oB f opcode.d3v$Merge Opcode and description columnswAccepted-Modified 2005/12/05 2005-11-058׀EEunahFKim^Technical, Non-binding_64`33a7.4b Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 4 Link Event Configure Request, Confirm Event --- bC---------------------------------------------------------------------------------------------------------------------- 3 Link Event DeRegister Request, Confirm Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 4 Link Event Configure Request, Confirm Event ---D------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 5 Link Up Indication Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ... ... bE... ...... ...... --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 14 Link Handover Complete Indication Event --------------------------------------------------------------------------------------------------F------------------------------------------------------------------------------------- 15 Link Information Request Request, Confirm Information --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 16 Link Information Response Response Information --------------------------------- bG------------------------------------------------------------------------------------------------------------------------------------------------------ *@A  33V  _  33p  y  33    33    33    33    33 &  '  33   33   33 -  4  33   33 A  P  33 r  33c----------------------------------- 5 Link Up Indication Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ... ...c141*W15-mihׁW2~W<WKWpWuW2005*W21-05-0423-00-0000!W"W#W$W%W&W3BWuWyW37538W3gppTWYW3gpp/3gpp2yW3gpp2UWZW4<W5.4.1?W5.5!WSW5.5referencemodelsforaccessnetworksSV5.5.1"W5.5.2#W5.5.3$W5.5.4%WTW5.5.4mihreferencemodelfor3gppTV5.5.5&WUW5.5.5mihreferencemodelfor3gpp2UV5.6!W5.6.1.4VW5.6.1.4mih-rrc-sapVV5.6.1.5WW5.6.1.5mih-ppp-sapWV5.6.1.6XW5.6.1.6mih-lac-sapXV5.8.2YW5.8.23gppamendmentsYV5.8.3ZW5.8.33gpp2amendmentsZV6\W6.2.1<W6.2.5OW6.3.2*W\W7'W5W6W7.14W~W7.2.12tW7.4.10wW7.4.10.1[W8hW8-mihW802.11rW802.16(W)W802.21oWrWsWxWyW9)W ׁbA!  33n    33    33     33    33    33    33    33'  (  33     33     33     334  > B 33H  I  334  33;  33Z  a  33F  33  33 Discover list of Events and Command supported by MIH Function ---------------------------------------------------------------------- ׁbATo modify Table-10 as indicated below. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- No Primitives Opcode Service Category Description -------------------------------------------------------------------------------------------------------------------------B-------------------------------------------------------------- 1 MIH Capability Discover Request, Confirm General Discover list of Events and Command supported by MIH Function ----------------------------------------------------------------------K5b7.4.6.2׀W7.4.6.2mihpollconfirm׀V7.4.6.2mihpollresponse׀V7.4.7.2׀W7.4.7.2mihswitchconfirm׀V7.4.7.2mihswitchresponse׀V7.4.8.2׀W7.4.8.2mihconfigureconfirm׀V7.4.8.2mihconfigureresponse׀V7.4.9.2׀W7.4.9.2mihscanconfirm׀V7.4.9.2mihscanresponse׀V8&W1W8.4.1.2׃W8.4.1.2mihcapabilitydiscoverresponse׃V8.6.13W8.6.23W802.16)W802.16eeWiWlW802.21\Wa!W"W#W$W%W&W*W0W1W2W9W:W;W<W=W?WAWCWDWEWIWJWKWLWNWOW[W\W]W`WaWdWeWiWkWlWnWoWqWtWuWׄWaapplicationlWableIWaboutNWdWiWkWyWGwctypes8WoWsWW׀WׁWtypically׀WtypobWcWue9Wue's9W:Wul?WCWunder`WyWunidirectionnal@WunitdatarWunsollicited9Wup+WJWsWupdate(W)W*W4W5W9WJWSWupdateentiresection7asperguiidelinesissuedlasttime5Vupdatefig9basedonnewupdatedreferencemodelfor802.16)Vupdatesection6.3.2ondescriptionofieswithnewtablefr*Vupdatesection7.1asperguiidelinesissuedlasttimebased4Vupdatethereferencemodelandassociatedtextfor802.16as(Vupdated)WBWupdtae6Wupdtaediscrepanciesinsection76Vupper?W@WAWBWCWEWFWGWHWIWJWKWLWMWNWOWPWQW׀WupperlayereventsneedtoberegisteredbythemihfunctionIV @ׄbA*  33z  33* This is sent as a response to MIH_Network_Address_information.response by This is sent as a response to MIH_Network_Address_information.request@message data.@A>  33d  z  33>cThe "SupportedTransportList" was resolved to be added in the MIH message data of both MIH_Capability_Discover.request and MIH Capability_Discover.response messages during the last meeting.d7wAccepted 2005/12/05 2005-11-05ׄEEunahFKim^ Editorial_108`48a8.4.4.8bAReplace This is sent as a response to MIH_Network_Address_information.response by This is sent as a response to MIH_Network_Address_information.request@4.8bAReplace This is sent as a response to MIH_Network_Address_information.response by This is sent as a response to MIH_Network_Address_information.request@------------- ׁbC----------------------------------------------------------------------------------------------------------------- 2 MIH Event Register Request, Confirm Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 3 MIH Event DeRegister Request, Confirm D Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 4 MIH Event Configure Request, Confirm Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------- ׂbATo insert the "MIH Link Down" and "MIH Handover Commit" messages and assign only one MIH message ID to the "MIH Information" message. ----------------------------------------------------------------------------------------------------------- No MIH Message Identifier MIH Opcode Category ----------------------------------------------------------------------------------------------------------- .. ...... .B.. ... ----------------------------------------------------------------------------------------------------------- 5 MIH Link Up Indication Event Service ----------------------------------------------------------------------------------------------------------- 6 MIH Link Down Indication Event Service ----------------------------- ׁbE------------------ 5 MIH Link Up Indication Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ... ...... ...... ...... -----------F---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 14 MIH Link Handover Complete Indication Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 15 MIH Poll  ׁbG Request, Confirm Command --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ... ...... ...... ...... -------------------------------------------------------------H-------------------------------------------------------------------------------------------------------------------------- 23 MIH Network Address Information Request, Confirm Command --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 24 MIH Information Request Request, Confirm  ׁbI Information --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 25 MIH Information Response Response Command ------------------------------------------------------------------------------------------------------------------------------------------------------------------------J--------------- n@-------------------------------------------------------------------------------------------------------------------------------------------- 14 MIH Link Handover Complete Indication Event --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 15 MIH Poll   ׁbcAIn Table 10-MIH_SAP Primitives, the opcode is defined for each primitive, but it's not fully specified. For example, the "MIH Event Register" primitive has two types of opcode : request and confirm. (refer to Figure 15-MIH Events Flow Model) But in Table-10, only request type of opcode is described in "MIH Event Register" primitive. Also, there are two information service primitives defined for information service, but they can be integrated to one primitive with two different types of oBpcode.d5vdtracked by the todo list. The details of the primitive also need to be submitted with the primitiveswDeferred for next meeting{l) none needed 2005/12/07 2005-11-0510ׂEEunahFKim^Technical, Non-binding_100a8.3.2b Request, Confirm Event ---------------------------------------------------------------------------------------------------------------------------------------------------------------------?lbtomodifytable-10asindicatedbelowׁVtomodifytable-8asindicatedbelowVtrafficnW ׄbcpThe MIH_Network_Address_information.response is the response message to MIH_Network_Address_information.request.d8wAccepted{k) done 2005/12/07 2005-11-05rk_Address_information.request@A*  33z  33*d  z  33>cThe "SupportedTransportList" was resolved to be added in the MIH message data of both MIH_Capability_Discover.request and MIH Capability_Discover.response messages during the last meeting.d7 2005/11/16 2005-11-05ׄEEunahFKim^ Editorial_108`48a8.4.4.8bAReplace This is sent as a response to MIH_Network_Address_information.response by This is sent as a response to MIH_Network_Address_information.request@A*  33z  33*  33z  33*d8 2005-11-05ׂcvIn Table 14, the "MIH Link Down" and "MIH Handover Commit" messages are missing and "MIH Information" is duplicated.d6wAccepted{k) done 2005/12/07 2005-11-0514׃EEunahFKim^ Editorial_101`3a8.4.1.2bAMake the following text change; 8.4.1.2 MIH_Capability_Discover.response This message may contain SupportedTransportList, SupportedEventList, SupportedCommandList, in the MIH message data.@A>  33d  z  33>cThe "SupportedTransportList" was resolved to be added in the MIH message data of both MIH_Capability_Discover.request and MIH Capability_Discover.response messages during the last meeting.d7wAccepted{k) done 2005/12/07 2005-11-05ׄEEunahFKim^ Editorial_108`48a8.4.4.8bAReplace This is sent as a response to MIH_Network_Address_information.response by This is sent as a response to MIH_Network_Address_information.request@ ׂbE------------------------------------------------------------- 15 MIH Information Request Request Information Service ----------------------------------------------------------------------------------------------------------- 167 MIH Information Respone Request, Response Information Service ----------------------------------------------------------------------------------------------------------- u@A  33]    33+  33,  -  33  33    33    33A  33B  C  33  33P  33  33    33  33  33    33 Service ---------------------------------------------- ׂbC------------------------------------------------------------------------------ 67 MIH Link Going Down Indication Event Service ----------------------------------------------------------------------------------------------------------- .. ...... ... ... -------------------------------------------------------------------------------------------------------D---- 134 MIH Handover Prepare Request, Response Command Service ----------------------------------------------------------------------------------------------------------- 15 MIH Handover Commit Request, Response Command Service ----------------------------------------------------------------------------------------------------------- 146 MIH Handover Complete Request, Response Command Service ---------------------------------------------- bthiscommentproposesanewinformationinwhichenablesam\Vthiscommentproposesanewparameterwhichenablesamobile[VthisnotificationisgeneratedwhenlinkarqmodulehasdetedVthreeEWLWthreshold0W=WtWthresholds0W5Wthrough;WthroughputaWthusCWeWtime<W?WCWaWkWtime-sensitiveaWtimeraWtimingeWtitle.Wtlv.Wto~W.W/W0W1W3W6W8W:W<W=W?W@WAWCWDWEWFWIWJWKWLWNWRWSWTWUWVWWWXWYWZW[W\W]W^WaWbWcWdWeWiWjWkWlWmWnWoWpWqWrWsWtWuWwWxWyWzW{W|W}WWׁWׂWׄWtoinsertthemihlinkdownandmihhandovercommitmessagesׂVׂV ^bsupportedeventlist׃Wsupportedtransportli׃WsupportingCWswitchJW׀WswitchoveriWsynchronous;WeWgWsynchronousl2iWlWsynchronously=Wtable*W1W2W6W>WoWpWqWtWtable-1/WoWrWtable-10ׁWtable-8Wtables*WeWoWsWuWtake~WDW^WkWtakeoutthefigureofthespecification~Vtaken?WtargetaWnWtbd]WtechnologyLWterminal<W?WCWJW[W\WyWterminal/network<Wterminals;WterminateEWFW4< aCbB or remote. A transport protocol is needed for supporting remote events. Security is another important consideration in such transport protocols. Various entities, such as upper layers and MIH Functions, either co-located with the source entity of the event (Local Event) or not (Remote Event), may be interested in these events at the same time. Thus these events may need to have multiple destinations. Interested entities can register to receive event notifications from a particular evenCZt source. The MIH Function can help in dispatching these events to multiple destinations."6cat the mobile node or at an entity in the network. Event generation could be due to UE mobility, state change in the environment or because of some management function on part of the network. Thus the source of these events can be either local either localYv2oW21-05-0439-00-0000/W21-05-0439-01-0000oW31>W3gpp)W7uW7.1.14W7.1.34W7.1.3shouldbemovedtobeunder7.1.1asmediadependents4V8uWa0W:W[W\W׀Waccepted)Wadd,WtotheterminalsideandnotatthenetworksidelVare?WJWasoWuWatlWbased)WeWbasedonthediscussionenhancethedefinitionoflinksyncheVbe8W?WJWeW{W׀WׁWbefore[W\Wbit[W\WbyeW׀WׁWchnage>WcolumnoWuWcolumnsWcommand{Wcommands׀Wcomment>Wcommentor]W^Wcomments?WJWconcerns]W^Wconfirm׀Wcontribution׀WdeferredvWdeferreduntilnexttimevVdefinitioneWdescriptionWdetailsׁWdeveloped׀Wdiscussed?WJWoWuWdiscussionUW[W\WeWyWduring?WJWemptyoWenhanceeWeventseWvadopoting[W\Wafter?WJWall?WJWalsoׁWand)W]W^WeWlWoWuWWanothe,Wapplicable0WlWapplicabletotheterminalsideandnotatthenetworksidelVare?WJWas,W4WoWuWatlWbased)WeWbasedonthediscussionenhancethedefinitionoflinksyncheVbe.W4W8W?WJWeW{W׀WׁWbefore[W\Wbit[W\Wbroadcast-Wby)WeW׀WׁWchange-W,WoWuWcolumnsWcommand{Wcommands׀Wcomment>Wcommentor]W^Wcomments?WJWconcerns]W^Wconfirm׀Wcontribution׀Wcontrol-WdeferredvWdeferreduntilnexttimevVdefinitioneWdescriptionWdetailsׁWdeveloped׀Wdiscussed?WJWoWuWdiscussionUW[W\WeWyWduring?WJWemptyoWenhanceeWeventseW"\+EVivekFGupta^Technical, Non-binding_55`7a7.2.7.1bUMake IP_Renewal_Indication optional Delete Mobility mgmt protocol support type bitmapcGAll specified parameters as part of Link Up may not be always availabled4w Withdrawn{l) none needed 2005/12/07 2005/11/03,EVivekFGupta^ Editorial_55`4bgremove word "Optional" from Type column and move it into Name column for all primitives in all sectionsczThe word "Optional" appears in Type column. type is not optional..but the parameter is optional..move iit into Name columnd5pcShall be done in next version of draft. We might want to take care of column "Valid Range" as well.vuInstead of using optional in the "name", add anothe column where the parameter is stated as "mandatory" or "optional"wAccepted-Modified{i) to do 2005/12/07 2005/11/03a^ Editorial_55`4bgremove word "Optional" from Type column and move it into Name column for all primitives in all sections vchangenametocontrolbroadcastinsteadofbroadcast-Vchnage>Wclearly0Wcolumn,WoWuWcolumnsWcommand0W{Wcommands׀Wcomment>Wcommentor]W^Wcomments?WJWconcerns]W^Wconfirm׀Wconsistent2Wcontinuing!Wcontinuingwork!Vcontribution׀Wcontrol-Wdcn.W/Wdcn21-05-0439-00-0000/VdeferredvWdeferreduntilnexttimevVdefinitioneWdependent4Wdescription2WWdetailsׁWdeveloped׀Wdevice0Wdiscussed?WJWoWuWdiscussionUW[W\WeWyWduring?WJWemptyoWenhanceeWeventseWevolving.Wevolvingworktrackingofthisworkwouldbewithinthedcn.V 0bALink_Thresholds_Configure is a local link command that can configure thresholds for Link_Parameters_Change event notification. The command may be executed as part of MIH_Configure command as well. The command allows setting of multiple thresholds for any link layer parameter. The thresholds levels are classified as: Initiate Threshold: Specifies initial action when this threshold level is crossed Rollback Threshold: Specifies a cancellation or rollback on previous action if the threshoB+ld falls back to this level. Execute Threshold: Threshold level which results in execution of a specific action. The threshold levels for each parameter are vendor/technology specific. Parameters under consideration here are: Link speed, BER, Frame Loss Rate before retransmission, Signal StrengthcwAdd a new link layer command Link_Configure_Thresholds to configure thresholds for Link_Parameter_Change notifications.d9p!Added new table for Link Commandscvwithin.Wwork!W.W]W^Wworked8Wwould.W8W]W^W{WvsrinieWstated,WsubmittedׁWsuch0WsynchronouseWtableoWterminal0WlWtext>WeWyWthat0W׀Wthe)W,W.W0W2W>W]W^WeWlWoWyW׀WׁWthesecondlastcolumnisemptytable1and2oVtheir]W^Wthis.W?WJWtimevWto-W0W4W>W?WJW[W\W]W^WeWlWoWyW׀WׁWtobediscussedafterallcommentsareresolvedduringthis?VJVtobetrackedbythetodolistacontributionlistiingthel׀Vtodo׀WׁWtracked׀WׁWtrackedbythetodolistthedetailsoftheprimitivealsonׁVtracking.WuliseseWunder4Wunderstand[W\WuntilvWupdate)Wupdatebasedon1116and3gpprefmodelsacceptedbythegr)Vusing,Wvote:Wwant[W\Wwhere,Wwho]W^Wwith~W2W]W^WׁWׁWׁW8֗bstrike the sentence out.cAOriginal Text: "A link layer event delivered to a link layer element must be conveyed to the corresponding network layer element in order for the event to have relevance." Comment: This is not absolutely true as link layer events consumers can be different from the network layers.d18w Superceded{l) none needed 2005/12/07 2005-09-14 ֞EEric FNJEDJOU^Technical, Non-binding_48`34a6.2.4bReplace the original text with the following: "Remote commands may be transported over network layer protocols or access layer protocols."cOriginal Text: "Remote commands may be transported over higher layer protocols or L2 management frames." Comment: Management frames only exist for .11.d24j pChanged to "Remote commands may be transported over network layer protocols or link layer protocols." (Changed word access to link)wAccepted{k) done 2005/12/07 2005-09-14 !EAndreaFFrancini^Technical, Non-binding0! 2005/12/07 2005/11/063 {needed!W"W#W$W%W&W'W+W.W/W9W:W;W?WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWUWWWXWYWZW[W\W]W^WrWsWtWvWxW|W׀WׁWnext)Wnone~W֗W!W"W#W$W%W&W'W+W.W/W9W:W;W?WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWUWWWXWYWZW[W\W]W^WrWsWtWvWxW|W׀WׁWround)Wto)W,W€{kdone֞V(V*V-V0V1V2V3V4V5V6V8V=V>V@VQVRVSVTVVV`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVpVqVuVwVyVzV{V}V~VVׂV׃VׄVl~W֗W!W"W#W$W%W&W'W+W.W/W9W:W;W?WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWUWWWXWYWZW[W\W]W^WrWsWtWvWxW|W׀WׁWlnoneneeded~V֗V!V"V#V$V%V&V'V+V.V/V9V:V;V?VAVBVCVDVEVFVGVHVIVJVKVLVMVNVOVPVUVWVXVYVZV[V\V]V^VrVsVtVvVxV|V׀VׁVneeded~W֗WucTables 2 and 3 are MIH commands for local and remote purposes with different presentation formats. In the first table some commands are both local and remote. In the second table, there are only remote commands. d7p7Updtaed Table 4 with both local and remote MIH commandsv"modify column 7 and 8 as discussedwAccepted-Modified{k) done 2005/12/07 2005/11/06T2 T3vESrinivasF Sreemanthula^Technical, Binding_76`1a7.4.10bNeed explicit text defining the scenario (mobile generated or network generated) and the corresponding effect. See attachment #3cA(For remote MIH commands in Table-3 that are bi-directional, the corresponding "Effect of Receipt" section must reflect which scenario is considered e.g mobile generated or network generated. This is important since not all commands are supported by the terminal. The current text reads ambiguous.(@A  33d8vdeferred until next timewDeferred for next meetingwv *abA'        )c  TT  5  )c6  TT7  =  )c>  TT?  B  TTC  \  TTa  l  )cq  w  TTx    )c  TT    )cY B# TT    )c"  (  )c    )c  TT    )c  )c  )ck  TT  )c g  TT} ecAThis proposal is to enhance the clarity of the existing Link Synchronous events description in the draft spec, in response to the Editor's note. @A* 3333*d1p9Edited and added text. May need more clarifications here.vABased on the discussion, enhance the definition of "Link Synchronous events". Modified text to be provoided by Srini and Ulises@A* 334  ff*wAccepted-Modified{k) done 2005/12/07 2005/11/06fEQiaobingFXie^Technical, Non-binding_62`28a7.2.16bA!Remove the entire section 7.2.16.!@A cNThis is to propose the removal of Link_Handover_Proceeding.Indication section.d2wAccepted{k) done 2005/12/07 2005/11/06gEQiaobingFXie^ Editorial_34`29a6.1.6b14@bThe figure must be modified to reflect the fact that events can flow from upper layers to the MIH, and commands can flow from the MIH Function to the Upper Layers. Replace the figure with the figure in file "21-05-0xxx-00-0000-MIH_general_view.doc"ccThis figure shows unidirectionnal arrows for events and commands, from/to MIH to/from upper layers.d9pUpdated Figure 1wAccepted{k) done 2005/12/07 2005-10-071AEMathieu FPERESSE^Technical, Non-binding_24`59a5.1.9bAReplace 1) with: 1) A Media Independent Event Service (MIES) which provides event classification, event filtering and event reporting corresponding to: - dynamic changes in link characteristics, link status, and link quality. - events that may originate in upper layers.cIn 1): we should not restrict the events from going from the Upper Layers to the MIH. Upper layers may have to transmit asynchronous information to the MIH (e.g. IP connectivity state) d10w Withdrawn")vBupdate based on .11, .16 and 3GPP ref models accepted by the groupwAccepted-Modified{h) defer to next round 2005/12/07 2005/11/03Fig 9.cMMake a case for TLV representatio before that for schema based representationd7v=Evolving work. Tracking of this work would be within the DCN.wDeferred for next meeting{l) none needed 2005/12/07 2005/11/03/EVivekFGupta^ Editorial_34`38a6.1.6bAUse all link events from Table-1 and also expose them as MIh Events. Indicate which events are remote and which local...For convenience all link events can be local by default. Only MIH events can be remote. It shall be up to the event consuming entity to subscribe to events they are interested in. Also map all events to communication reference points (R1, R2 etc.) as defined in updated communication model.c"Include description for MIH eventsd8p=Need to map events/commands to different Communication PointsvDCN 21-05-0439-00-0000w Superceded{l) none needed 2005/12/07 2005/11/03Table 10EVivekFGupta^Technical, Non-binding_38`30a6.2.6.2b_pneed/WTWeWneedtomapevents/commandstodifferentcommunicationpoint/Vneeed<Wnetwork֞W4Wnew0W<Wnext,Wno<WwWnot<WVWoWnow4Wof,W2WonoWonce)WonlyyWopcodeWor֞WwWoriginal<Wother`Wout`Wover֞Wpicture)WpicturesSWpleaseSWpleasedrawpicturesinvisioSVpoints/Wprimitive2Wprotocols֞WquerywWqueryresourcelistwWqueryresourcelistisaflagspecifyingqueryornoquerywVrange,Wredundant`Wreference(W)WTWyWremote֞WuWremovedyWWremovedreferencetoonlymobiletrminalretrievingtheinfoyVremovedtheopcodecolumnfromthesetablesVretrieve<WretrievingyWrevisionoWsaps4WVWsectio2Wsection<W`Wupdated(W)W@WTWVWupdated3gppreferencediagramneedbettertextaccompanyingTV {done5W6W8W=W>W@WQWRWSWTWVW`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWuWwWyWzW{W}W~WWׂW׃WׄWe<Weeditordisagrees<Veditor<Wh)Whdefertonextround)Vi,Witodo,Vk֞W(W*W-W0W1W2W3W4W5W6W8W=W>W@WQWRWSWTWVW`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWuWwWyWzW{W}W~WWׂW׃WׄW%9 2005/12/07 2005-10-07:EMathieuFPERESSE^Technical, Non-binding_70`7a7.2.12bAdd to section 7.2, after section 7.2.12, the contents of the document "21-05-0xxx-00-0000-Link_Parameters_Report.doc". This contains a new section which describes the Link_Parameters_Report primitive.cAIntroduce a new Primitive that will carry media independent parameter reports. This will allow Network-Controlled Handover scenarios, as dynamic information can be transmitted to an entity in the network (e.g. an MME), so that this entity can make choices based on the UE's current state (Signal Strength, Data Rate...) This primitive may be invoked either synchronously (on a regular basis) or asynchronously (specific trigger, eg. threshold crossed) As discussed in the ML, the Event ServiBSce is appropriate for this type of information transfer (i.e. dynamic information).Ad3v on a votewRejected{l) none needed 2005/12/07 2005-10-07;EMathieuFPERESSE