Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0)@0inding@cthenormativereferencesectionisblank@@00allowedtheconcatenationoftheseparat@@0coincide@entity@inserttheworddownlinkbeforemodeaandotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@ 33  33 33>20SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDec8:7y:I3 "Z22#& 9/17/20051=w C;aTjx.;PkaTlPm_pwlaTsjt`Tuiv2PvATwDmviPx}bTykvq~zaTyPui_ ` PN %M %2I @EJOTYACXbmwBDa@EzJyOtUi[fBd|X||}q !A!VDEF(LIST3LISTA3Editorial Technical, Non-binding Technical, Binding3VDEFA((A!VDEF(LISTLISTAMember Observer OtherVDEFA((A!TVDEF(LISTLISTAApprove with no comments Approve with non-binding comments Disapprove with binding comments Abstain for lack of technical expertise Abstain for lack of time Abstain for reasons detailed in a comment field Comments only; no voteVDEFA((A!&VDEF(LISTgLISTAgAccepted Accepted-Modified Accepted-Clarified Accepted-Duplicate Rejected Rejected-Duplicate SupercededgVDEFA((A!Vt VDEF(LISTLISTLISTDT-W X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   v  V<E NALL # ` ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^_`abcdef g h ijklmnoqFMPR$@` ABCdD^EvFwGxHyIQ>AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijkQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJ>@ Cj%7.hal e-iJ.hj -Ek. l`l -mFxrogermarkspQmarksprogermarksBRmarksBrogermarksTmarksrogermarks@Umarks@roger marksmarksroger marks( i marks!(!roger  marks"0#q#marks$"0$ marks( i marks!(!roger  marks"0#q#marks$"0$DTDT €Editor's NotesEditor's Questions and Concerns€AEditor's Action Items€A€A€A Starting Line #€A Section€A  Fig/Table# BA1BAj  !"#$%&'()*+,-./0234567j^_ `2a4bc d ijkmn.p+v"wx#y'{)€%€0€€€€1€€66leiOwang' *  wang * leiP wang wang ' leiQ wang VYwang VleiRwangwang YleiSwang wang leiTwang@nh&`wanghleiUwangC1.55€A1.55: Added "Fig/Table Number" field Deleted XML file output option. 1.54: Added "Technical, Satisfied (was Binding)" to value list Comment Type/Group. 1.53: in Reply Comment layout, reduced display to three replies 1.52: *Changed instruction on saving files to specify .USR instead of .fp5 *Fixed bug that wouldn't allow exporting a ballot with no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create andRecords" button in Create ands" button in Create andte andplit "Cn" Split "Cosals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Cd 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. S2002-01-04 (or later)802.16-01/53r1VersionK 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  ABCDEFGHIJK^L_M`NaObPcQ S]^_`acdefgijklmnopqrstuvwxyz{|}~րցւքօֆֈ։֊֋֌֍֎֏֐ְֱֲֳִֵֶַָֹֺֻּֽ֑֖֛֢֣֤֥֦֧֪֚֭֮֒֓֔֕֗֘֙֜֝֞֟֠֨֩֫֬֯־ֿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃^_`abcd€€€€€'f€aA Create and Submit Reply Comments @A*  33*€APLEASE FOLLOW THESE INSTRUCTIONS EXACTLY OR EXPECT TO HAVE YOUR INPUT IGNORED. (1) Read the comments. You will probably find this easiest if you use the "Comment List" layout. You can choose it from the upper left corner of this window, or you can use this push button: (2) When you want to respond to a comment, check the "Marked" box at the top of that record. Then fill out the following fields: Recommendation: Proposed Resolution: Reason for Recommendation: You are fully justifing the buttons:€gng the buttons:€gng the buttons:€gg the buttons:€gicking the buttons:€gicking the buttons:€gowing steps by clicking the buttons:€ging the buttons:€gg the buttons:€ging the buttons:€ge buttons:€gbmit Ballot Filef9Proceed with the following steps by clicking the buttons:€gO+ A#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# cBl#[  bl[##KK##;;# Bmv#+  @iv+# >j# Dkv# 8w5 €\]Page€^A_Line€`A aSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A &'()+ €A €A €A€ARecommendation@@ByProposed ResolutionReasonSee reply details€A Fig/Table# BNA^  !"#$%*,-./0123^^_`u EDE^ "Technical, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, BindingG OKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !""Technical, Binding" comments are permitted only with the vote "Disapprove". You may submit comments of type "Technical, Non-binding". Please correct and try again.H) W()=0 W ABCDEFGHIJK^L_M`NaObPcQvl SEz\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\{]^_`abcde0A^c@5.3.2@802.21onlydefinesenablersformobilitymanagementprotoco@network@replace@jdonottalkaboutanarchitecurebutratherintroduceinterf@have@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 jg   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)P@B@2@IdjP;;;P;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 PMBeS-X bWmkwj,AgCvE!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€ (SE Eric NJEDJOU^Technical, Binding_1`58a1.2ccThe infrastructure is also in the position to have overall visibility of radio resource conditions.d1g2215j]E Eric NJEDJOU^Technical, Binding_2`10a1.2cqWe should be careful on using the word architecture. 802.21 defines a set of functionalities not an architecture d2g2219 2005/09/15 2005-09-14005/09/15 2005-09-14n 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=>jgP:@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=Aeric@njedjou@subir@Ng@*research@srinivassreemanthulanokiacom@wolfgang@^editorial@noonly@technical@technicalbinding@withfinesenablersformobilitymanagementprotoco@lamodificationissuggestedtosection6byaddingnewprimi@Zabove@againreplacewithhlehigherlayerentity@alink@an@daugmented@be@called@cellular@Xconnectivity@definition@deliver@*@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  a,v AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bfl6V~%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 8zReason 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 GL2314iA 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! CgTgvh ivTjxivPk#TlPm&3Tn{&h3Po pDw6YTqp&3`Pr nTsj{tTuivcPvXTwmvPxTykvq~ 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 GMathieuPERESSE!mperesse.ext@rd.francetelecom.com ajayrajkumar@lucent.com 1IEEE 802.21 Comment Resolution for P802-21-D00-02 vivek.g.gupta@intel.com€D00-02mAComment 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 DataIjSjA^j _@`ccc d@e@g@idmjn qjAr@t@vj w@yc|@ց@օ^ֈ@֋֏@֑@֖֕@֘@֜@֟@֢֥@֫a֮cACdֱgAֵcACdֹ_ ֺcB"D#d!ּcA%C&@'d$־cA)d(_.cA0C1E2G3d/cA7C8d6a;cA>C?d=cAACBd@cADCEdCcBFDGdcBKDLAMdJgQgRcATdScBVDWdUgA\[g]cB`d_cAbdacBiDk @fjtargetcWkWWterminalzW֛WWterminationWWterminologydWdWminal. In cellular systems, the network generally helps with this process so that the terminal can save operational power.d6g2223 2005/09/15 2005-09-14cE Eric NJEDJOU5 2005-09-141aE Eric NJEDJOU^Technical, Binding_3`54a1.3cThis could be performance destructive for the terminal. In cellular systems, the network generally helps with this process so that the terminal can save operational power.d6g2223 2005/09/15 2005-09-14cE Eric NJEDJOUhe terminal. In cellular systems, the network generally helps with this process so that the terminal can save operational power.d6g2223 2005/09/15 2005-09-14cE Eric NJEDJOUinal. In cellular systems, the network generally helps with this process so that the terminal can save operational power.d6g2223 2005/09/15 2005-09-14cE Eric NJEDJOU֮d 732-699-2483gDNo need to have such a descriptive introduction in Section 6.3.1,  2005/09/17Member֯ESubirFDasGsubir@research.telcordia.com_Technical, Non-bindingcsInclude the text and figure from Section 3 of document number 21-05-0348-01-0000_Higher_layer_IS.doc to Annex ZZ. d 732-699-2483gHInclude the Information Service Use Case Scenarios as informative text  2005/09/17MemberְESubirFDasGsubir@research.telcordia.comd 732-699-2483 2005/09/17MemberֱEWolfgangFGroetingGwolfgang.groeting@siemens.com_Technical. Non-binding`120a30b8.3.1c- Interchange Transaction ID and MIH Function ID Length positions - Interchange MIH Function Identifiers with MIH Message ID d +492871912142gObserverTcnetworkaWnW֎W֗W֝W֮WֵWּWWWWWWWWWWWWWnetwork-operatorWnetworksֵWWWWWWWnew֋W֭WWWWWWWWWWWWWWWWWWWWaftok֋VnorW֞W֣W֤WWnodecW֮WWnoiseWnon-freeWnonnegativeintegerWnot]W^W`WcWdWeWfWqWrWvWyW{WւWքWօW֊W֎W֑W֖W֬WֵWWWWWWWWWnotaccurate^VnotaccurateagainwhatisthemobilitymanagementprotocoleVnotsosure֊Vnottrueicanusethe802.11interfacetotalktoanmihlovVnoteWWnsert֮Wnumber֮W֯WobjectpropertyWobtain֮WWWobtainedWWobtainingWobtainsWoccurֵWoccurenceswWxW"cofSW]W`WfWnWrWsWwWxWyWւWքWօW֝W֩W֬W֮W֯WֵWֺWֻWּWWWWWWWWWWWWWWWWWWWWWWWWWWWWWok֋Won]W`WmW֑WֵWWWWWWWWon-goingWoneօW֍WֵWWWWWWWoneofWonly_W`WyW֌W֑W֕W֤WֵWWonlyexistsfor11֕VonpropertyWontologiesWontologyWWopennessWoperationWoperationalaWoperator֗WWWWoperatorienetworkidentifierandoperatorinformationelem֗Voperator-idWoperator-nameWoperatorsWoptionalWWorlW֮WֵWּWWWWWWWWWWWWWorderWWorg/1999/02/22-rdf-sWW^approveWWWWWWWWWWWWWapprovewithnocommentsVVVVVVVVVVVVVbindingSW]W^W_W`WaWcWdWeWfWgWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWրWցWւWքWօWֆWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֢W֣W֤W֥W֦W֧W֨W֩W֪W֫W֬W֭WWWWWWWWWWWWWcommentsWWWWWWWWWWWWWWWWWWcommentsonlynovoteVVVVVWWWWWWWWWWWWWWWWY@ dDT ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^_`abcdef g h ijklmnomnolmnono֑‚b֒‚c֓‚d֔‚e֕‚f֖‚g֗‚h֘‚i֙‚j֚‚q֛‚r֜‚s֞‚t֢֣֤֥֦֧֪֭֝֟֠֨֩֫֬ dDT ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^_`abcdef g h ijklmno<cdefinitionfWkWWWWWWWWWWWWWdefinitionsnW֭WWWdeleteֻWּWֽWWWWdeleteanexdֽVdeleteentriesforeventidentifiers7-11fromthetabledelּVdeletelines22-43descriptionoflinksynchronouseventsanֻVdeletesection7.2.13or7.2.14oraddmorehandoverrelatedVdeletesection7.2.157.2.167.2.17oraddmoretexttoclarVVnւWքW֠W֢WֺWֻWּW־Wdestination֢WdestructiveaWdetailsfWdetection{WdeterminelWpWdifference֟WּWdifferencesWdifferentmWnW֎W֮WֵWWdifferentiate֒WdirectWdirectlyWdiscover֮Wdnamic־WdopW֤Wdoc֬W֭W֮W֯WdocumentnW֬W֮W֯WdoesrWyW֚W֟WdomainֵWdon't֤WdownWdraft֋W֌WּWWdynamic־WeֵWe֮Wfecfigure`WօW։W֐W֑W֮W֯WWWWWfigure2correctionVfilterWfindingWflagWWflavourmWflow֐W֑Wfollowing֮WWWWWWWfor_WaWfWqWyWքW֌W֐W֕W֣W֬W֮WֵWּW־WWWWWWWWWWWWWWWWWWWWforneighborreportiesremovemeasurementreportfromthed־VformatWWWWframeWframesւWքWWframework֮WWWfreeWfromyWzW֎W֮W֯WּW־WֿWWWWWWWWWWWfunction`W֮WֱWֵWWWWWWWfunctionalities]Wfunctionality`WֵWWfunctionalpropertyWfunctionsֵWfunctonWfurtherWWgֵWWWWWmWrWtWuW֑WWcthisreferenceisnotadaptedtoieee802ietfvocabularyisdVthisreferencemodelandtheoneoffigure3arenotalinedօVthisterminologyis11specificjVthresholdWthroughcWֵWthusWtightֵWtimeּWWtimedifferenceּWWtimeoutֺWWtitle֑WtoSW`WcWdWfWqWsWtWuWvWyWzWցWւWքW֌W֍W֐W֗W֚W֟W֠W֢W֬W֭W֮W֯WֵWּWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW`WlWwithaWtWwithinrWword]WwrongkWyoulWd S0]@^P_``paedc‚!f‚"g‚#i‚$j‚%k‚&l‚'m‚(n‚)o‚*p‚1q‚2r‚3s‚4tm€ dE Eric NJEDJOU^Technical, Binding_5`41a2.1cpThis reference is not adapted to IEEE 802. IETF vocabulary is not precise enough when link layers are consideredd8g2226j%define a more appropriate terminology 2005/09/17 2005-09-14 Binding_5`41a2.1cpThis reference is not adapted to IEEE 802. IETF vocabulary is not precise enough when link layers are consideredd8g2226j%define a more appropriate terminology 2005/09/15 2005-09-14 seE Eric NJEDJOU^Technical, Binding_3`55a1.3cANot accurate Again what is the mobility management protocol stackd7g2227jA&Original Text: This information typically originates at lower layers of the mobility management protocol stack, within the MN or other network elements. Proposed Text: This information typically originates at differents layers of the protocol stack, within the MN or other network elements. & 2005/09/17 2005-09-14 fE Eric NJEDJOU^Technical, Binding_6`31a3cAThis level of definition is sufficient for IETF but certainly not for IEEE. 802.21. We need to go into the details of what is a MAC link, an LLC link, a PHy link, an RLC link..This is sufficient for IP because what matters for IP is the layer 2 connectivity it views as a single stack.d10g2228 2005/09/17 2005-09-14 g2230 2005/09/14 2005-09-14 iE Eric NJEDJOU^Technical, Binding_6`40a3cSame as previous comment%^technicalSW]W^W_W`WaWcWdWeWfWgWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWրWցWւWքWօWֆWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֢W֣W֤W֥W֦W֧W֨W֩W֪W֫W֬W֭WWWWWWWWWWWWWWgViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVրVցVւVքVօVֆVֈV։V֊V֋V֌V֍V֎V֏V֐V֑V֒V֓V֔V֕V֖V֗V֘V֙V֚V֛V֜V֝V֞V֟V֠V֢V֣V֤V֥V֦V֧V֨V֩V֪V֫V֬V֭VwithWWWWWWW{id12g2231 2005/09/17 2005-09-14 jE Eric NJEDJOU^Technical, Binding_6`53a3c This terminology is .11 specificd13g2232 2005/09/17 2005-09-14 kE Eric NJEDJOU^Technical, Binding_7`31a3cThis is a wrong definition d14g2233jSuggested definition: the process by which a network node collects information on its detected neighboring networks, map them to policies to determine a target link to establish network-layer connectivity 2005/09/17 2005-09-14lE Eric NJEDJOU^Technical, Binding_12`8a5.1chHow can you determine before hand that the handover will be" break before make" or "make before break"? d15g2234 2005/09/17 2005-09-14 mE Eric NJEDJOU^Technical, Binding_12`51a5.1.3cOThis has policy flavour. Selection could be based on different criteria types. d16g2235g2235nE Eric NJEDJOU^Technical, Binding_13`7a5.1.5Eric NJEDJOU^Technical, Binding_13`7a5.1.5^^_ Sֱִֵֶַָֹֺֻּ֮֯־ֿƒÃŃƃǃȃɃʃ˃̃΃σ҃Ճփ׃؃كڃۃ܃݃ރ߃s‚'tu‚(vwxyz{|‚)}‚*~‚1ր‚2ցւ‚4ք‚6օֆ‚7ֈ։‚8֊֋֌֍‚9֏‚A֭‚B֎‚D֐֑‚E֒‚F֓֔‚I֕‚J֖֬‚S֗‚W֘‚Z֙‚f֛֚֜‚֞‚֝‚֢֣֤֟֠‚֥‚֦֧‚֨‚֩‚֪‚֫`@֏p~֊֖nlc‚!]vw֨‚#^xy֚‚$‚%֟‚&ִ‚'ֵ֩‚(_‚)oz‚*ֶ‚1ַ‚2ָ֥‚4ֿ‚5}‚6ֹֺ֘‚7֋֎‚8{|‚Bfkֻ‚E֦֕‚Fgּ‚Gք‚Hpqր‚J֮‚Qiց‚RdtՃ‚S־‚Uֆ‚V֧‚Wuւ‚Z֙cthisisonlytruefor11thedraftneedstobemoregeneric֌Vthisissomekindofinformationrequestshouldbepartoft֩VthislevelofdefinitionissufficientforietfbutcertainlfVlevelofdefinitionissufficientforieeenutcertainlfVfVforieeenutcertainlfVfVthislookswrongasethertypeisonlyvalidfor802.3/ethern֏V֏VHYncpossible֞WWpoweraWpppWWpre-provisionedWprecisedWprecised֐WprefixWprepareWpreventzWpreviousgWiWprimarilyWprimitive֝W֠W֢WWWWprimitives֭WWWWWWWWprivateWproblem֬WprocedureWprocessaWֺWWWpropagateyWpropertiesWWWWWpropertyWWproposalWproposedWWprotocol_WeWօW֐W֜WWWprovide֮WֵWWWprovidedWWprovides֮Wpurpose֝WWpurposesWqos־WWWqueriesWqueryWWWqueryparametersWqueryresourcelistWqueryresourselistrWradioSWradiusWrangeWWWrateWWWeferencemodelVreorganisation֬WreorganizeWreorganizesapsinsection7basedonrevisedsapdefinitionVcbe]W`WaWlWmWoWsWtWuWցW֌W֎W֐W֗W֚W֜W֩W֬W֮W־WWWWWWWWWWWWWbecausefWqW֖WbeenrW֑WbeforelW֞W֤WWWWbehaviourWbelongWbelongsWWbelow֑WֵWWWWWWWWWbesidesցWbesidesmihmacsapthelsapcanalsobeusedtotransportpցVbetterWbetweenqW֟WֵWּWWWWWWbeyondWbidirectionalWbindingWbitWbitmap֜WֺWWbooleanWboth֮WֵWWWWboxrWbreaklW֞W֤WbroadcastWbszWbssidsWbuildsWbutfW֬WWbypW֬W֭W֮WִW־WWWWWWWcWWWWWcachingּWWiWcomplete֔WconditionsSWconfigure֝WWjdonottalkaboutanarchitecurebutratherintroduceinterfrVdonottalkaboutl3mpuseupperlayersyVdoneqWecWzWWeffectivenWeffortmWeitheraWWelement֗Welements^W_WeWenablenWenables]Wencapsulated֍WendpointvWWWWWWWendpointsvWWentity_W~WWestablishkWetcnWqWethernet֍Wethertype֍WeventvWWeventsvWzWexchangevWWexecutionqWexistingqWexperiencemWfallsWWWfollowingnWformWnWօW֌WWWframes֌W֍W֕Wfunction_WaWWWfunctioninstanceVfunctionalities]W]W]WrE Eric NJEDJOU^Technical, Binding_14`55a5.3d for inter-system d20g2239 2005/09/15 2005-09-14rE Eric NJEDJOU^Technical, Binding_14`55a5.3[cthererW֞W֤W֬WWWthereare3waystosolvethisVthereisaneedtoaddaninformationelementsetforusere֬VthereisnomihboxassuchthathasbeendefinedthereforerVthereforerWtheseּWWWtheyWthing֟WWthisaWdWfWjWkWmWtWuWւWքWօW։W֌W֎W֐W֑W֓W֔W֖W֚W֛W֜W֞W֤W֩WֵWּWWWWWWWthisclassificationisnotconsistentbecause6.2.5.1alread֖VthiscouldbeperformancedestructivefortheterminalinceaVthishaspolicyflavourselectioncouldbebasedondifferenmVthishastobereplacedwithupperlayerstVuVthisisawrongdefinitionkVthisisnotabsolutelytrueaslinklayereventsconsumersc֎VycWhy would I want to propagate event to the remote L3MP? What even can I propagate to the Home Agent? The Home Agent does not perform Mmobility management. It is only responsible for hiding change of IP location from the correspondent view point.d28g2247j)Do not talk about L3MP. Use upper layers. 2005/09/17 2005-09-14zE Eric NJEDJOU^Technical, Binding_17`18a5.4.1cNAgain what prevent from using my 802.11 interface to talk to an MIH in the BS?d29g2248jOriginal Text: Note, remote events between two stacks of different media types (e.g., between an 802.11 mobile terminal and a UMST BS) are not supported since a link between such two stacks are impossible Proposed Text: remove this sentence.  2005/09/17 2005-09-14 {E Eric NJEDJOU^Technical, Binding_17`27a5.4.1cNeed not detectiond30g2249jReplace "detection" with "need" 2005/09/17 2005-09-14ers" d31g2250jReplace with "upper layers"  2005/09/15ingechaveSW`W֗W֟W֤WWWhaving֝W֤WheadWhelpsaWhence־WhereօWheterogeneous֮WhexbinaryWWhidingyWhigher~W֮W֯WWWWhigher-layerWhle~Wholds֐WhomeyWhomogeneous֮WhowlW։W֜WhowcanyoudeterminebeforehandthatthehandoverwillbelVhoweverֵWhttpWWiqWvWyWWWWiinsection1.2purposeisnotonlytoenablebetterusereVimodifycmdconfiguretoindicatethetypeofparameterandVianaWid֝WֱWWidentifier֗W֠W֢W֣WWWidentifiersֱWּWidentify֛WWWie֗WieeedWfWWWies֬W֮W־WietfdWfWifpWqW֤WWWWWWifiwouldliketotransitionbetweentwolinksiwontuseqViiWWiidefineanewcommandViiiWWVpWuctobetakenoutofthespecificationsVtoinsertVVtoreplaceVVtransactionֱWtransferWtransitionqWtransmissionֻWtransportցWֵWWWtransportlayertravelsoWtruevW֌W֎WֵWtwonWqW֟WWWWWtwodifferentdefinitionsofnetworkselectioninthesamednVtype֜W֤W֮WֵWֺWּWWWWWWWWWWWWtypesmW֮WtypicallyֵWWWWtypingWuamWue֮WunauthenticatedWunclearֆunderWWupdatedWupon֮WuppertWuWwWxW|WWWWurisWurlWWWuseqWvWւW֮WWWusedցWւWքW։W֐W֜WWWWuser֬WusersWusesWWusing]WzWֵWWWusngWvalidWvalueWWWWvalueoflinkWcthelinkeventrequesthasnotbeendefinedanywhere֑VthesubnetassociationisnotastepthatamobilenodenececVthe11thWtheiroWWthemWthenWcVtheiroWoWtionisnotastepthatamobilenodenececVcVcVjtrytosticktotheglobalreferencemodelfortheueprotocօVtwovWzWtypecWvWtypesvWzWtypicallyeWueօWumstzWuniqueWupdatesqWuppernWtWuWwWxWyW|WuseqWvWyWցWusednWցWusefulqWusermWnWusing֍WvariousnWvisibilitySWwellvWwell-suitedSWwhenqW֍WWwhichkWWwithcWmWtWuWwWxW{W|W~WցWWWWWWwithin^W_WeWWWWWwork֣Wworkondefiningidentifiers֣Vm€m€m€atedd36g2255 2005/09/15 2005-09-14#ւE Eric NJEDJOU^Technical, Binding_21`46a5.5.2sport packets when associatedd36g2255 2005/09/15 2005-09-14#ւE Eric NJEDJOU^Technical, Binding_21`46a5.5.2.5.25.5.2crlcfW֒WrncvWroamingWWroaming-parnersWrouterּWWrowWrrcWWsamegWiWnW֟W֥W֦W֧WֵWWsameaspreviouscommentgViVsapցWւWքW։WֿWWWWWsapsWWsatisfied־WsaveaWscalabilityWscanWscanningWscenarioֵWWscenarios֮WֵWWWschemaWWWeWWsdoWsection֘W֭W֮W֯WִWֵWֶWַWָWֺWWWWWWWWWsectionsּWsecureoWsecurityWsee֜W֝W֬W֭WselectWWselectingWselectionmWnWsemanticsWsendingWWsenserWWsentWsentence֋WserveֵWservice֩W֮WֵW־WWWWservicesWsessionWset]W֬WWWsetsWWsetupֺWWshallWWW44cwhywouldiwanttopropagateeventtotheremotel3mpwhatyVwichւWwill`WlW֬WWwirelineWwithaWtWuWwWxW|W~W֛WֱWֵWֶWַWָWֹWֺWWWWWWWWWWWWWWy֮Wzz֯Wd S0]@^P_``paedc‚!f‚"g‚#i‚$j‚%k‚&l‚'m‚(n‚)o‚*p‚1q‚2r‚3s‚4t‚5u‚6v‚7w‚8x‚9y‚:z‚A{‚B|‚C}‚D~‚E‚Fր‚Gց‚Hւ‚Iք‚Jօ‚Qֆ‚Rֈ‚S։‚T֊‚U֋‚V֌‚W֍‚X֏‚Y֎‚Z֐‚a֑‚b֒‚c֓‚d֔‚e֕‚f֖‚g֗‚h֘‚i֙‚j֚‚q֛‚r֜‚s֞‚t֝‚u֟‚v֠‚w֢‚x֣‚y֤‚z֥‚֦‚֧‚֨‚֩‚֪‚֫‚֬‚֭ƊaH#(eִֵֶַָֹֺֻּֽ־ֿdXcalink֓W֔WallּWWWWWWallowWWalongWalreadyqW֖W֘W֟Walreadydescribedinsection5.3.3֘ValsoSWցWWWWWWalternativelyWaltitudeWaltresWalways`WoW֞WambiguityWamendmentsWamongWWWWWWWWWWWWanexֽWannex֮W֯Wanywhere֑WapplicableֵWappliedWarchitecture]WrWaredWօW֖W֮W־WWWWarea֮Was`WfWgWiWoWrW֎W֠W֢W֤W֥W֦W֧WWWWWWWascendingWassignWassociatedցWassociationcWoWatWWWattachWattached֬W֭WattachmentWaugmentedWauthenticatedWauthenticatesWauthenticationֺWWavailableֵWWbasedmWWWWbasicWW5citisalwaystobeclearlyrecalledthatmobilitymanagement`Vitshouldbeprecisedwhichcontextthisfigureholdstois֐Vits֛WWk֮WkbpsWkeyWkind֩WknowledgeWl2֐WֵWl3ֵWl3mp`WwWxWyWWlabelWlacWWlanguageWWlaresWlatitudeWlayerfW~W֎W֚W֮W֯WWWWWWWWWWWWWlayersdWtWuWwWxW|W֎WWWWWlciWlengthֱWWlevelfWlikeqW֓W֔WlikelyWWlineWWWWWWWWline10WlinesֻWWWWvWzWցWքWօWmmobilityyWmobilecWmobility_W`WeWmodel֐W֑Wmore֌Wmp֏WmultiplewWxWmyzWnecessarilycWneedfW{Wneednotdetection{Vneeds֌WneighboringkWnentpWցE Eric NJEDJOU^Technical, Binding_21`40a5.5.2cSbesides MIH_MAC_SAP, the LSAP can also be used to transport packets when associatedd36g2255jOriginal Text: Thus MIH_MAC_SAP is use to transfer packets after a station associates with an AP Proposed Text: Thus MIH_MAC_SAP or the MIH_LSAP is used to transfer packets after a station associates with an AP 2005/09/17 2005-09-14$ւE Eric NJEDJOU^Technical, Binding_21`46a5.5.2cWhat is not clear in this description is the clarification of wich specific SAP is used to deliver data frames and which other is used37g2256 2005/09/17 2005-09-14'քE Eric NJEDJOU^Technical, Binding_23`36a5.5.4cWhat is not clear in this description is the clarification of which specific SAP is used to deliver data frames and which other is used for MIH management.d38g2258 2005/09/17 2005-09-14(օE Eric NJEDJOUօE Eric NJEDJOUric NJEDJOU'օE Eric NJEDJOUa5.4.3cagainreplacewithhlehigherlayerentity~Vagainwhatpreventfromusingmy802.11interfacetotalktozVagentyWּWWairoWalinedօW֑E Eric NJEDJOU^Technical, Binding_33a6.1.3cCommand on the title below Figure 14:: This is only an example link event flow model. Other can exist The Link Event request has not been defined anywhere d50g2271 2005/09/17 2005-09-1414+֒E Eric NJEDJOU^Technical, Binding_34`55a6.1.6c-Should differentiate PHY, MAC, LLC RLCeventsd51g2272 2005/09/17 2005-09-14+֓E Eric NJEDJOU^Technical, Binding_35a6.1.6cJLink Handoff Imminent: Is this alink event? Looks like rather an MIH eventd52g2273 2005/09/17 2005-09-141+֔E Eric NJEDJOU^Technical, Binding_35a6.1.6cJLink Handoff Complete: Is this alink event? Looks like rather an MIH eventd53g2274 2005/09/17 2005-09-141+֕E Eric NJEDJOU^Technical, Binding_38`34a6.2.4conly exists for .11 d54g2275jhOriginal Text: Remote commands may be transported over higher layer protocols or L2 management frames.  2005/09/17.2.5.3^r`‚bm‚c֪‚dj։‚ea֌‚fer֒‚iS‚j‚qƃ‚s֍ǃ‚u‚‚‚‚‚‚‚‚‚‚‚‚̃Ã"pÃ#ֱÃ#0Ã#@Ã$0Ã%Pֽa1ֿƒÃ˃ۃ1.2S]^_`1.3ae1011ֵ14ǃ141ֹ152.1d20уՃ22ֻּ24252627n5.1.6o5.2pq5.3r5.3.1s5.4tu5.4.1vwxyz{|5.4.3}~5.55.5.1ր5.5.2ցւ5.5.4ք5.6օֆֈ5.6.2։5.6.4֊5.6.6֋5.7.1֌֍֏535455ִ56ָ58Ƀ596֭6.1.2֎6.1.3֐֑6.1.6֒֓֔6.2.4֕6.2.5.3֖6.3֬6.3.2֗6.3.3֘6062ֶ7.2֙7.2.7.1֛֚֜7.4.10.1.2֢֣֤֠7.4.11.1֥7.4.11.1.4֦7.4.11.2.1֧7.4.12.1.1֨WֈE Eric NJEDJOU^Technical, Binding_26a5.6d41g2262 2005/09/17 2005-09-1410(։E Eric NJEDJOU^Technical, Binding_26`53a5.6.2c&Can't figure out how is this SAP used.d42g2263 2005/09/17 2005-09-14&֊E Eric NJEDJOU^Technical, Binding_27`6a5.6.4c Not so sure.d43g2264 2005/09/17 2005-09-14'֋E Eric NJEDJOU^Technical, Binding_27`26a5.6.6c$New sentence since the May draft. OKd44g2265 2005/09/17ric NJEDJOU^Technical, Binding_27`26a5.6.6c$New sentence since the May draft. OKd44g2265 2005/09/15 2005-09-14&֊E Eric NJEDJOU^Technical, Binding_27`6a5.6.4c Not so sure.d43g2264 2005/09/15 2005-09-14'֋E Eric NJEDJOU^Technical, Binding_27`26a5.6.6c$New sentence since the May draft. OKd44g2265 2005/09/152265 2005/09/1409/14^Technical, Binding_27`26a5.6.6c$New sentence since the May draft. OKd44g2265 2005/09/14օ^Technical, Binding_25a5.6cwThis reference model and the one of figure 3 are not alined. Why locate the mobility management protocol above IP here?d39g2259jFTry to stick to the global reference model, for the UE protocol stack. 2005/09/17 2005-09-149'ֆE Eric NJEDJOU^Technical, Binding_25`44a5.6cUnclear d40g2260 2005/09/17 2005-09-14'-14&2258 2005/09/15 2005-09-14&3$p֋ 2005-09-14&֌E Eric NJEDJOU^Technical, Binding_27`54a5.7.1c>This is only true for .11. The draft needs to be more generic d45g2266jOriginal Text: The packet payload for these services may be carried over L2 management frames, L2 data frames or other higher layer protocols.  2005/09/17 2005-09-14)֍E Eric NJEDJOU^Technical, Binding_27`62a5.7.1cSpecific to one technology! d46g2267jOriginal Text: Thereafter these packets can be encapsulated in a L2 MIH Protocol using MIH ethertype when the payload needs to be sent over normal data frames as in case of ethernet  2005/09/17 2005-09-14-֎E Eric NJEDJOU^Technical, Binding_31`26a6.1.2cdThis is not absolutely true as link layer events consumers can be different from the network layers.d48g2268 2005/09/17 2005-09-14,+this fihure holds to. Is for an 802.11 flow model? Why is MAC the L2 protocol used? ?????????d49g2270 2005/09/149QclinkdWfW֎W֑W֓W֔WֺWֻWWWWWWWWWWWWWWWlinkhandoffcompleteisthisalinkeventlookslikerather֔Vlinkhandoffimminentisthisalinkeventlookslikerather֓Vlink-specificWlinksqWֵWWWlistWWlisted־WWlistsWliteralWllcfW֒WWlocalWWlocateօWlocatedvWlocationyWWWWWlongoWlongitudeWlooks֓W֔WloresWlowerWWlsapցWmWWWmacfWցW֐W֒W֛W֣WWWWmacmobileWmacmobileterminal֛WmacsWmainWmakelWrW֞W֤W֮WWWWWmakethefollowingtextchangeVVWmight֬WWmih`WpWrWvWzWցWքW֓W֔W֝W֟W֥W֦W֧W֩W֮WֱWֵWֿWWWWynjedjouSW]W^W_W`WaWcWdWeWfWgWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWրWցWւWքWօWֆWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֢W֣W֤W֥W֦W֧W֨W֩W֪W֫W֬W֭WpererzWWWWWWWWWWWWWpererzfederVqiaobingWWWWWWWWWWWWqiaobingpererzandreaajayVVVVVVVVVVVVronnyƒÃăŃƃǃȃɃʃ˃̃srinivas΃σЃу҃ӃohbaՃփ׃؃كڃۃ܃݃ރ߃sreemanthula^cconnectivityfWWWconsidereddWconsistencyWconsistent֖WWconsistsWconsumers`W֎WcontainWWWWcontainsWWcontentoWcontentsWcontext֐WcontributionֶWַWָWֹWֺWWWWWcontrolWWWcontrolledWspondentyWcorrespondingּWWWWWcostWWWcouldaWmWcouplingֵWcriteriamWcurrentִWWcurrentlinkidentifiecurrentlyWdֽWWd00-02WWWdataւWքW־WWWWWWWdata-rateWdatatypeWWdatatypepropertyWdatumWdcnִWֶWַWָWֹWֺWWWWWdecision֮WdedicatedqWdeeply֚WdefinepWWWWdefinedrW֑W֠W֢WWWWWWWWdefines]W_WWWWdefiningWcwhatdoeslayer2meanweneedtobedeeplyaccurateinthis֚VwhatisnotclearinthisdescriptionistheclarificationoւVքVwhendWցW֞WֵWּWWWWWWwhereֵWWWWWWWwhetherWwhichւWքW֐W֟W֮WֵWWWWWWWwhileWWwhyyWօW֐W֘E Eric NJEDJOU^Technical, Binding_46`25a6.3.3c"Already described in section 5.3.3d57g2278 2005/09/17 2005-09-14/֙E Eric NJEDJOU^Technical, Binding_49`49a7.2d58g2279 2005/09/17 2005-09-141֚E Eric NJEDJOU^Technical, Binding_55`12a7.2.7.1cKWhat does layer 2 mean? We need to be deeply accurate in this specificationd59g2280 2005/09/17 2005-09-142֛E Eric NJEDJOU^Technical, Binding_55a7.2.7.1ceIn the table: MAcMobileTerminal: This implies that we identify every terminal with its MAC addressd60g2281j@Need to agree on identifiers... (MIH IDs, Mobile Terminal IDs).  2005/09/17 2005-09-146t purpose. 2005/09/15 2005-09-145at purpose. 2005/09/15 2005-09-144ed to agree on identifiers... (MIH IDs, Mobile Terminal IDs). A work item should be launched on that purpose. 2005/09/15 2005-09-144gEctheSW]W`WaWcWeWfWlWnWoWpWsWvWyWzWցWւWքWօW֋W֌W֎W֐W֑W֛W֜W֝W֞W֟W֠W֢W֣W֤W֩W֬W֭W֮W֯WִWֵWֺWּW־WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWtheinfrastructureisalsointhepositiontohaveoverallvSV֜E Eric NJEDJOU^Technical, Binding_55a7.2.7.1ckIn the table: Mobility Management Protocol Support Type bitmap : Can't see how this parameter can be usedd61g2282 2005/09/17 2005-09-144֝E Eric NJEDJOU^Technical, Binding_73a 7.4.8.1.4c^In the table: can't see the purpose of having NETWORK_ID in the MIH_Configure primitive d63g2283 2005/09/17 2005-09-149֞E Eric NJEDJOU^Technical, Binding_70a 7.4.7.1.2crIn the table: Handover Mode: We always want make before break when possible. There is no point specifying thisd62g2284 2005/09/17 2005-09-148 2005-09-148284jRemove Handover Mode 2005/09/15 2005-09-147֟E Eric NJEDJOU^Technical, Binding_74`14a7.4.9cl We already have MIH_Poll which does the same thing. We need to specify the difference between the two... d64g2285 2005/09/15 2005-09-147֠E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.265g2286ccinthetablemacmobileterminalthisimpliesthatweidentify֛Vinthetablemobilitymanagementprotocolsupporttypebitma֜Vinthetablesuggestedpoaidentifiernomacaddressforcel֣Vinclude֮W֯WWWWWincludethetextandfigurefromsection3ofdocumentnumbe֯VincludedWincludes֮WWWincludingWindependent֮WWWindicateWWWWindicatedWWWindicatesֺWWindicationWinfoWWinfoqueryfilterWinfoqueryparametersWinformation_WoWpW֗W֩W֬W֮WֵWּW־WWWWWWWWWWWWWWWWinformationrequestseWinformationresultsetWinformationxxWinfrastructureSWWinitiate֥W֦W֧WWWinsertWWWWWWWWWspage59linVit`WfWpWyW֐W0jremovehandovermode֤VremovedmWreplacewWxW{W|W~Wreplacedetectionwithneed{Vreplacehigherlayermobilityprotocolhlmpwithhigherlaye~Vreplacel3mpwithupperlayerswVxVreplacewithupperlayers|VreplacedtWuWrequirednWWrequirednWnWnWnWZcabove`WօWWabsolutely֎WaccessֵWWWWWWaccessesֵWaccessibilityWaccessingWaccurate^WeW֚WacrossֵWWWWWactiveֵWWadapteddWadd֬WWWWWWWWWWWWWWWWWWaddanewdefinitiontosection3VVVVVhandoveVaddanothertableformiheventsorlistmiheventsinthetVaddedWWWWadding֭WadditionalWadditionsWaddress֛W֣WּWWWaddsWadoptWWWWadoptremedy5inthecontributiondcn21-05-0359-00-0000Vadopttheremedy1and2inthecontributiondcn21-05-0359-Vadopttheremedy3inthecontributiondcn21-05-0359-00-000Vadopttheremedy4inthecontributiondcn21-05-0359-00-000VadvertisementּWWafteroWagaineWzW~W֤Wr_a7.4.13֩7.4.7.1.2֞7.4.8.1.4֝7.4.9֟8.2.1֪8.3.1֫b1W1.22WW21-05-0370-00-0000W3W4W5.1.95.35.3.2ִ5.3.3ֵ5.5.1ֶ5.5.2ַ5.5.3ָ5.5.4ֿ5.5.55.6ֹֺ6.1.2ֻ6.1.5Ѓ6.1.66.2.26.2.5.16.2.5.3.2V7.2W7.2.117.2.11.17.2.12.17.2.13ƃ7.2.15W7.2.157.2.167.2.17V7.2.16W7.2.17W7.2.7.17.4.17.4.11.2.27.4.127.4.14.1.27.4.14.3.17.4.8.17.4.9.2.47.47.13.2.28.38.3.1ֱ8.3.28.4annexֽWWWWWannexc1Vannexc2Vannexc3Vannexc4VannexdֽVcWWWWdֽWtable-1ּtable-5־c0ֺWWWWW0successV001122334455W0123456789abW1ֺWWWWWWWWWW:Pcspecifying֞WspeedWsta֮WWWsta'sWstackeWfWstandardWWstandardsWstartingWWWWWstateWstationWstepcWstoreWstrengthWstrictlyWstringWWstructureWsubWsubclassofWsubnetcWsubpropertyofWsubsection֮WWWistWsure֊WsynchronousֻWsystemWWsystemsaWtqWtable֛W֜W֝W֞W֠W֢W֣W֤WּWWWtablesWtakensWtalkvWzWtalkingrWtechnology֍Wterm֠W֢WterminalaW֛W֬WֵWWterminologyjWtextoW֥W֦W֧W֮W֯WֵWWWWWWtextisthatsameasin7.4.10.2mihhandoverinitiaterespo֥V֧Vtextisthatsameasin7.4.10.2.4mihhandoverinitiateres֦Vthat`WaWcWlWpWrW֖W֛W֥W֦W֧W֬W֮WW֥E Eric NJEDJOU^Technical, Binding_79`21a7.4.11.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d69g2291 do break before make only if we don't have other choice. d68g2290 2005/09/15 2005-09-14=֥E Eric NJEDJOU^Technical, Binding_79`21a7.4.11.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d69g22912290 2005/09/15 2005-09-14=֥E Eric NJEDJOU^Technical, Binding_79`21a7.4.11.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d69g2291 do break before make only if we don't have other choice. d68g2290 2005/09/15 2005-09-14=֥E Eric NJEDJOU^Technical, Binding_79`21a7.4.11.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d69g2291g2290 2005/09/15 2005-09-14=֥E Eric NJEDJOU^Technical, Binding_79`21a7.4.11.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d69g2291֥ 2005/09/17 2005-09-14>֦E Eric NJEDJOU^Technical, Binding_80`34a 7.4.11.1.4cCText is that same as in 7.4.10.2.4 (MIH_Handover_Initiate.response)d70g2292 2005/09/17 2005-09-14?֧E Eric NJEDJOU^Technical, Binding_80`45a 7.4.11.2.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d71g2293 2005/09/17 2005-09-14@֨E Eric NJEDJOU^Technical, Binding_82`10a 7.4.12.1.1d72g2294 2005/09/17 2005-09-14C֩E Eric NJEDJOU^Technical, Binding_83`16a7.4.13cXThis is some kind of Information Request. Should be part of the MIH Information Service.d73g2295jMIH_Network_Address_Information should be deleted and the information carried in this primitive should be put into a MIH_Information primitive. 2005/09/17 2005-09-14C֪E Eric NJEDJOU^Technical, Binding_92`52a8.2.1d74g2296 2005/09/17 2005-09-14D֫E Eric NJEDJOU^Technical, Binding_95֫a8.3.1c.d75g2297 2005/09/17 2005-09-1413G֬E Eric NJEDJOU^Technical, Binding_39a6.3cAThere is a need to add an Information Element set for User Equipements. The problem is that some IEs will not be carried by IS but rather by ES/CS. Some reorganisation of the document might be needed for that matter. Please see the attached doc "Terminal_IEs.doc"d76g2298 2005/09/17 2005-09-14I֭E Eric NJEDJOU^Technical, Binding_30a6cA modification is suggested to section 6, by adding new primitives and by modifying certain definitions. Please see the attached doc, called New_ECI.docd77g2299 2005/09/17 2005-09-14J֮ESubirFDasGsubir@research.telcordia.com_Technical, Non-binding`39a49b6.3.1cd 732-699-2483MemberIOcweneedtospecifythedifferencebetweenthetwo֟VwerequesttomergethetwotablesandprovideaconsistentVweshouldbecarefulonusingthewordarchitecture802.21d]VwebWwellWwell-placedWwell-suitedWwereqWwetherpWwhateWfWpWyWzWւWքW֚WwhatdoweexactlydefinebyhandoversignalingisittheexpVtheexpVpVqVqV"cimminentpW֓WimplementationWWWimplies֛WimportantWWinSWaWnWoWvWzWւWքW֘W֚W֛W֜W֝W֞W֠W֢W֣W֤W֥W֦W֧W֮WִWֵWֶWַWָWֹWֺWּW־WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWinthetablecan'tseethepurposeofhavingnetworkidint֝Vinthetablecommanddestinationdefinedasdestinationiden֢Vinthetablecommandsourcedefinedassourceidentifierin֠Vinthetablehandovermodeagainthereisnopointhavingth֤Vinthetablehandovermodewealwayswantmakebeforebreak֞V k_E Eric NJEDJOU^Technical, Binding_2`17a1.2cZ802.21 only defines enablers for Mobility Management (protocol for information exchange.)d4g2221jAfOriginal Text: A set of handover-enabling functions within the mobility-management protocol stacks of the network elements and the creation therein of a new entity called the MIH Function. Proposed Text: A set of handover-enabling functions within the protocol stacks of the network elements and the creation therein of a new entity called the MIH Function.f 2005/09/17 2005-09-14`E Eric NJEDJOU^Technical, Binding_3a1.2ling functions within the protocol stacks of the network elements and the creation therein of a new entity called the MIH Function.f 2005/09/15 2005-09-14`E Eric NJEDJOU^Technical, Binding_3a1.28 SjAOriginal Text: The network infrastructure is well-suited to store overall network information, such as neighborhood cell lists and the location of mobile devices. Proposed Text: The network infrastructure is well-suited to store overall network information, such as neighborhood cell lists, the location of mobile devices. The network infrastructure is also in the position to have overall visibility of radio resource conditions. 2005/09/17 2005-09-14]E Eric NJEDJOU^Technical, Binding_2`10a1.2cqWe should be careful on using the word architecture. 802.21 defines a set of functionalities not an architecture d2g2219jmOriginal Text: An architecture that enables (...) Proposed Text: A set of functionalities that enables (...) 2005/09/17 2005-09-14^E Eric NJEDJOU^Technical, Binding_2`12a1.2c Not accurated3g2220tion over which network elements will support the handover.d3g2220jtextSW]W^W_WaWcWeWmWqWvWzWցW֌W֍W֕Wthat]W^WWWWWWWWWWWtheSW^W_WaWcWeWkWmWnWqWrWsWvWցWօW֌W֍W֩WWWWthemkWthennWthereafter֍Wtherein_Wthese֌W֍WtheyvWthiseWqWtWuWzW֖W֩WthishastobereplacedwithupperlayerstVuVthusցWtimenWWtoSWkWmWnWsWtWuWvWցWօW֍W֗W֛WWWtobetakenoutofthespecificationsVtransferցWtransmitsaWtransportvWtransported֕WtriggerqWtryօWօWvWyWցWusedցWusefulqWusermWvisibilitySWwellvWwell-suitedSWwhenqWwhichkWwithcWmWoWtWuWwWxW|W~WցWwithin^W_WeWm€jnetworkSW^W_WaWeWkWmWnWqW֗W֩WWWWWnetworknodecollectionofphysicallycollocatedlinkendpoiVVWnetwork-sideWnetworksaWkWqWnew_W֗WnodeaWkWvWWWWnodesvWnormal֍WnotnWqWrWyWzWnotezWofSW]W^W_WaWcWeWmWnWqWsWvWzW֍W֖WWWWon^WaWkWnW֛W֣WoneWonesrWonlynWoperationnWWoperator֗Woperatorienetworkidentifierandoperatorinformationelem֗VoraWeWցW֌W֕WWoriginalSW]W^W_WaWcWeWqWvWzWցW֌W֍W֕Woriginaltextasetofhandover-enablingfunctionswithinth_Voriginaltextanarchitecturethatenables]VoriginaltexthandoversignalingaspartofhandoverexecutiqVqVWpartpWpoaoW+jneighborhoodSWneighboringkWWSW^W^W^W^Wgement^W^W^W^Wanagement^W^WjhaveSWvW֗WheterogeneousqWhigher~W֌W֕Whle~Whlmp~WhomogeneousqWhoweverqWicWid֗Widentification^Widentifier֗W֠W֢WWidentifiers֛W֣Wids֛Wie֗WifnWvWimpossiblezWinSWaWmWqWrW֍W֩WWincludesWWWindependentvWinformationSWaWeWkWnW֗W֩WinfrastructureSWWWWWinfrastructurenodenetworknodethatcannotperformanykinVinitiatedqWinitiationqWinstanceWWinter-systemqWinterfacesrWinto֩Wintra-roamingqWintra-systemqWintroducerWisSWmWnWvWցWWWitskWWWWWmechanismsqWmediaqWvWzWmih_W`WaWmneWmobileSWaWqWzWmobility`WeW~Wmobility-management^W_WmostmWmotorolarWmtoW/E Pro 3.0 - 4.1F!"HPro 5.0 A ?G USENGLSH.MPR?GUSER.UPRjfunctions_WgzWWgivennWglobalօWhandover^WmWnWqW֤Whandover-enabling_WhandoversqWhastWuWuWuWuWuWtWuWuWB jhave@keep@media@ mihpointofattachmentmih-activepointofattachmentona@neighborhood@network@networkselectionisthecontinuousprocessofselectingthe@nodes@originaltextiewiththetypeoftheservingandtargetpo@originaltextthisinformationtypicallyoriginatesatlower@performance@position@removehandovermode@resource@target@text@trytosticktotheglobalreferencemodelfortheueprotoc@jalsoSWWan]WmWrWvWzWցWWWandSW_WaWcWqWzW֗W֩WanynWWWapցWapplicableWapplication/layer`WappropriatedWmWnWarchitecture]W^WarchitecurerWarevWzWaroundaWasSWnWqWvW֍WWassociatedWassociatesցWassociationscWateWnWWWWWWattachmentcWWWWWWautomatedWavailablenWbasednWbemWnWqWsWtWuW֌W֍W֕W֗W֠W֢W֩WWbetweenzWbszWbutrWbykWcalled_WcannWqWvW֍WWcannotWcarried֌W֩Wcase֍WcellSWchangeWcloseWcoincideWcollectionWcollectskWcollocatedWcommands֕WcommunicationWcomplete֖W֖W֖WWdifferentqWvWzWdorWyW `cIt is always to be clearly recalled that Mobility Management function sits above MIH. On such a figure, it is essential to have it so as to clearly show that not only the L3MP will be consumers of the MIH functionalityd5g2222j9Add a "Mobility Management Application/Layer" above MIH.  2005/09/17 2005-09-141aE Eric NJEDJOU^Technical, Binding_3`54a1.3cThis could be performance destructive for the terminal. In cellular systems, the network generally helps with this process so that the terminal can save operational power.d6g2223jOriginal Text: The MIH Function on the mobile node continuously receives (...) Proposed Text: " The MIH Function, either on the mobile node or in the network, receives and transmits information about the performance of access networks around the MN  2005/09/17 2005-09-14 cE Eric NJEDJOU^Technical, Binding_3`9a3on is not a step that a mobile node necessarily has to go through.d9g2225gE Eric NJEDJOU^Technical, Binding_6`35a3cSame as previous commentd11g2229 2005/09/17 2005-09-14 iE Eric NJEDJOU^Technical, Binding_6`40a3cSame as previous comment PHy link, an RLC link..d10g2228 2005/09/15 2005-09-14 gE Eric NJEDJOU^Technical, Binding_6`35a3cSame as previous commentd11g2229 2005/09/15 2005-09-14 iE Eric NJEDJOU^Technical, Binding_6`40a3cSame as previous comment[jpositionSWpotentialWprefered֠W֢WpreferencemWpreferencesnWpreferrednWprimitive֩WprimitivesWpriorWprocesskWnWproposedSW]W^W_WaWeWmWqWrWvWzWցWproposedtextasetoffunctionalitiesthatenables]Vprotocol^W_WeW~WօW֍Wprotocols֌W֕Wprovider֗WproximityWput֩WqosmWnWradioSWnWratherrWreceivesaWreferenceօWregardlessvWrelies^WremotevWzW֕Wremove^WzW֤W֤WW֤W֤W֤W֤W֤W֤W֤WW֞W֤W֤W֤Wremovedetection{V{Ve^WzW{W֝W֞W֤Wremovedetection{V{Von{V{V{VV{VW{W֝W֞W֤Wremovedetection{V{V{V{Vlmpwithhigherlaye~Vreplacel3mpwithupperlayerswVxVreplacewithupperlayers|VreplacedtWuWoW aqjAOriginal Text: Handover signaling (as part of handover execution and subsequent updates) may not be part of the standard. Different networks support different intra-roaming handover mechanisms (mobile initiated, network initiated, etc.). Handover initiation trigger may be useful in heterogeneous handovers when not done as per the homogeneous scheme. Proposed: Intra-System Handover signalling can make use of existing standards and may not be part of this standard. However, inter-system HB7andover signalling shall be specified in this standard.% 2005/09/17 2005-09-14ical, Binding_14`37a5.2cIf i would like to transition between two links I won"t use already existing messages because intra-romaing messages were not dedicated for inter-system d20g2239j mjOringinal Text: The preference is to select the network with the most appropriate QoS support level for handover in an effort to maintain the level of user experience. Proposed Text: To be removed. 2005/09/17 2005-09-14 nE Eric NJEDJOU^Technical, Binding_13`7a5.1.5cCTwo different definitions of network selection in the same documentd17g2236jAKeep only the following definition Network selection is the continuous process of selecting the most appropriate network for any user operation at any given time. The selection can be based on various criteria such as radio parameters, required QoS, cost, user preferences, policies, etc. If the selected network is not the currently used network, then a handover to the preferred network may be required. The 802.21 standard may specify the means for such information to be made available to tB7he upper layers to enable effective network selection. % 2005/09/17 2005-09-14Technical, Binding_14jperformanceaWphysicallyWplaceWpointcWWWWWWpointofattachmentnetwork-sideendpointofalinkwithatVpolicieskWnWnWhjoriginaltextiewiththetypeoftheservingandtargetpocVoriginaltextnoteremoteeventsbetweentwostacksofdiffezVoriginaltextremotecommandsmaybetransportedoverhigher֕Voriginaltextthearchitecturereliesontheidentification^VoriginaltextthemediaindependenteventservicesupportslvVoriginaltextthemihfunctiononthemobilenodecontinuousaVoriginaltextthenetworkinfrastructureiswell-suitedtosSVoriginaltextthepacketpayloadfortheseservicesmaybec֌Voriginaltextthereafterthesepacketscanbeencapsulatedi֍Vnaltextthepacketpayloadfortheseservicesmaybec֌V֌VoriginaltextthusmihmacsapisusetotransferpacketsafցVoriginateseWoringinalmWoringinaltextthepreferenceistoselectthenetworkwithmVothereWkW֌WoutsWover֌W֍WoverallSWpacket֌WpacketsցW֍WpartqWpayload֌W֍WrE Eric NJEDJOU^Technical, Binding_14`55a5.3ctThere is no MIH box as such that has been defined; Therefore talking of architecture within .21 does not make sense.d21g2240jiDo not talk about an architecure, but rather introduce interfaces (like the ones Motorola proposed in SF) 2005/09/17 2005-09-14sE Eric NJEDJOU^Technical, Binding_14a5.3.1c$To be taken out of the specificationd22g2241j%To be taken out of the specification. 2005/09/17 2005-09-142r signalling shall be specified in this standard.) 2005/09/15 2005-09-14rE Eric NJEDJOU^Technical, Binding_14`55a5.3ctThere is no MIH box as such that has been defined; Therefore talking of architecture within .21 does not make sense.d21g2240jiDo not talk about an architecure, but rather introduce interfaces (like the ones Motorola proposed in SF) 2005/09/15 2005-09-14sE Eric NJEDJOU^Technical, Binding_14a5.3.1 .vj 2005/09/17 2005-09-14by handover signaling? Is it the exhange if MIH information that determine wether a handoff is imminent?d19g2238jdProvide a definition for definition for Handover Signalling:Is it just ES and CS, or ES, CS AND IS ? 2005/09/15 2005-09-14Yjdonottalkaboutanarchitecurebutratherintroduceinterf@functions@ tE Eric NJEDJOU^Technical, Binding_16`41a5.4c)This has to be replaced with upper layersd23g2242j)This has to be replaced with upper layers 2005/09/17 2005-09-14uE Eric NJEDJOU^Technical, Binding_16`46a5.4c)This has to be replaced with upper layersd24g2243j)This has to be replaced with upper layers 2005/09/17 2005-09-14vE Eric NJEDJOU^Technical, Binding_17`10a5.4.1cMNot true. I can use the 802.11 interface to talk to an MIH located in the RNCd25g2244jAOriginal Text: The Media Independent Event service supports local events as well as remote events if the remote node(s) is of the same media type. Proposed Text: The Media Independent Event service supports local events as well as remote events regardless of the remote nodes' media type. If the two endpoint are of the same media type, they can use an L2 transport to exchange events; if the two endpoints are of different media types, they have to use L3 transport.jresourceSWrespectivecWresultWreworking֖WsvWsamevWsapցWschemeqWscopeWWWWselectmWselectednWselectingnWselectionnWsent֍Wsentence^WzWservicevWservices֌WservingcWWset]W_WsfrWshallqWshould֠W֢W֩WsignalingqWsignallingqWsincezWsource֠Wsourceidentifiershouldbeprefered֠VspecificationsWspecifiedqWspecifynWstack^WeWօWstacks_WzWstandardnWqWstandardsqWstationցWstickօWstoreSWsubnetcWsubsequentqWsuchSWnWzWsuggestedkWsuggesteddefinitiontheprocessbywhichanetworknodecolkVsupport^WmWqWsupportedzWsupportsvWswitchWtakensWtakesWtalkrWyWyWwE Eric NJEDJOU^Technical, Binding_17`10a5.4.1c;Replace with "upper layers" (multiple occurences of "L3MP")d26g2245j#Replace "L3MP" with "upper layers"  2005/09/17 2005-09-14xE Eric NJEDJOU^Technical, Binding_17`12a5.4.1c;Replace with "upper layers" (multiple occurences of "L3MP")d27g2246j#Replace "L3MP" with "upper layers"  2005/09/17 2005-09-14yE Eric NJEDJOU^Technical, Binding_17`12a5.4.13 transport. 2005/09/15 2005-09-14wE Eric NJEDJOU^Technical, Binding_17`10a5.4.1c;Replace with "upper layers" (multiple occurences of "L3MP")d26g2245j#Replace "L3MP" with "upper layers"  2005/09/15 2005-09-14xE Eric NJEDJOU^Technical, Binding_17`12a5.4.1c;Replace with "upper layers" (multiple occurences of "L3MP")d27g2246j#Replace "L3MP" with "upper layers"  2005/09/15 2005-09-14yE Eric NJEDJOU^Technical, Binding_17`12a5.4.1ja]W^W_W`WdWkWnWzWցW֍W֩WWWWWWWaboutaWrWyWabove`WaccessaWadd`Waddamobilitymanagementapplication/layerabovemih`Vaddress֩WafterցWagree֛W֛WWրWրW?| 2005-09-14}E Eric NJEDJOU^Technical, Binding_18`24a5.4.3d32g2251 2005/09/17 2005-09-14~E Eric NJEDJOU^Technical, Binding_19`6a5.4.3c+Again replace with HLE =Higher Layer Entityd33g2252jLReplace Higher Layer Mobility Protocol (HLMP) with Higher Layer Entity (HLE) 2005/09/17 2005-09-14E Eric NJEDJOU^Technical, Binding_19a5.5d34g2253 2005/09/17 2005-09-143 րE Eric NJEDJOU^Technical, Binding_20`37a5.5.1d35g2254 2005/09/17 2005-09-14"the author is talking about 802.3 or EThernetd35g2254j0ERIC: I guess it's alright. It's 802.3 anyway... 2005/09/155g2254j0ERIC: I guess it's alright. It's 802.3 anyway... 2005/09/15րE Eric NJEDJOU^Technical, Binding_20`37a5.5.1c[It is very confuding in this paragraph wether the author is talking about 802.3 or EThernetd35g2254j0ERIC: I guess it's alright. It's 802.3 anyway... 2005/09/15 jkeepnWkeeponlythefollowingdefinitionnVkindWl2vW֌W֍W֕Wl3vWl3mpwWxWyWlayer~W֌W֕WlayerseWnWtWuWwWxWyW|WleastWWWWWlevelmWlikerWlinkkWzWWWWWWWWWlinkendpointlinkterminationassociatedwithalink-layerVlink-layerWlink-switchWlinksWWlistsSWlocalvWlocationSWlowereWlsapցWmacցWmadenWmaintainmWmakeqWmanagement`WeW֌W֕WmapkWmaynWqW֌W֕WWmeansnWmechanismsqWqWthein֩VmnaWeWmobileSWaWqWzW֛Wmobility`WeW~Wmobility-management^W_Wmode֞W֤WmodelօWmoredWmostmWnWmotorolarWmtoWneed֛Wneedtoagreeonidentifiersmihidsmobileterminalidsaw֛Vneeds֍W֕ 2005-09-14.cal, Binding_27`62a5.7.1cSpecific to one technology! d46g2267jAOriginal Text: Thereafter these packets can be encapsulated in a L2 MIH Protocol using MIH ethertype when the payload needs to be sent over normal data frames as in case of ethernet Proposed Text: Thereafter these packets can be encapsulated in a L2 MIH Protocol when the payload needs to be sent over normal data frames (as in case of ethernet where an MIH ethertype should be used) 2005/09/15 2005-09-14,,for an 802.11 flow model? Why is MAC the L2 protocol used? d49g2270 2005/09/15 2005-09-1414+9/15 2005-09-1414+X֏E Eric NJEDJOU^Technical, Binding_28`3a5.7.1d47g2269 2005/09/17 2005-09-14+֐E Eric NJEDJOU^Technical, Binding_33a6.1.3cxIt should be precised which context this figure holds to. Is for an 802.11 flow model? Why is MAC the L2 protocol used? d49g2270j???? 2005/09/17 2005-09-1414, NJEDJOU^Technical, Binding_33a6.1.3cxIt should be precised which context this figure holds to. Is for an 802.11 flow model? Why is MAC the L2 protocol used? d49g2270j???? 2005/09/15 2005-09-1414,,joriginaltextthisinformationtypicallyoriginatesatlowereVoriginaltextthusmihmacsapisusetotransferpacketsafցVoriginateseWoringinalmWoringinaltextthepreferenceistoselectthenetworkwithmVothereW֌WoutsWover֌W֍W֕WoverallSWpacket֌WpacketsցW֍WparametersnWpartqW֖Wpayload֌W֍WperqWperformWWyload֌WperqWqWqWqWqWjcompletereworkingofthispart֖VconditionsSWconfiguredWconnectivitykWcontinuousnWcontinuouslyaWcostnWcreation_WcriterianWcurrentlynWdata֌W֍WdefinedWdefineamoreappropriateterminologydVdefinedWdefining֣WdefinitionkWnWdeleted֩Wdestination֢Wdestinationidentifiershouldbeprefered֢VdetectedkWdetection{WdeterminekWdevicesSWdifferentqWvWzWdifferentseWdorWyWyWrWyWyWyWyWyW*֖E Eric NJEDJOU^Technical, Binding_39`6a6.2.5.3ceThis classification is not consistent because 6.2.5.1 already describe some commands that are remote.d55g2276j"Complete reworking of this part... 2005/09/17 2005-09-14/֗E Eric NJEDJOU^Technical, Binding_42a6.3.2cSOperator IE: Network Identifier and Operator information element have to be mergedd56g2277jmOperator IE: Network Identifier and Operator information element have to be merged. New name: Provider ID  2005/09/17 2005-09-144/IE: Network Identifier and Operator information element have to be mergedd56g2277jSOperator IE: Network Identifier and Operator information element have to be merged 2005/09/15 2005-09-144.֟E Eric NJEDJOU^Technical, Binding_74`14a7.4.9cl We already have MIH_Poll which does the same thing. We need to specify the difference between the two... d64g2285 2005/09/17 2005-09-147֠E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIn the table: Command Source : Defined as "Source Identifier" in other primitive description. Need to choose a single term. d65g2286j%Source Identifier should be prefered. 2005/09/17 2005-09-14;֢E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIn the table: Command Destination : Defined as "Destination Identifier" in other primitive description. Need to choose a single term. d66g2288j)Destination Identifier should be prefered 2005/09/17chnical, Binding_74a 7.4.10.1.2cIn the table: Command Destination : Defined as "Destination Identifier" in other primitive description. Need to choose a single term. d66g2288j)Destination Identifier should be prefered 2005/09/15֢ 2005-09-14=֣E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIIn the table: Suggested PoA identifier : No MAC address for cellular. d67g2289j Work on defining identifiers... 2005/09/17 2005-09-14>֤E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIn the table: Handover Mode : Again there is no point having this as a type. We do break before make only if we don't have other choice. d68g2290jRemove Handover Mode 2005/09/17 2005-09-14>^jOriginal Text: The architecture relies on the identification of a mobility-management protocol stack within the network elements that support the handover. Proposed text: remove the sentence.  2005/09/17 2005-09-14ccVThe subnet association is not a step that a mobile node necessarily has to go through.d9g2225j|Original Text: (i.e., with the type of the serving and target point of attachment and the respective subnet associations).  2005/09/17 2005-09-14 noE Eric NJEDJOU^Technical, Binding_13`18a5.1.6cEven after secure association, the events, commands and information messages can always be eavesdropped as long as their content travels the air interface in clair textd18g2237 2005/09/17 2005-09-14pE Eric NJEDJOU^Technical, Binding_14`37a5.2cWhat do we exactly define by handover signaling? Is it the exhange if MIH information that determine wether a handoff is imminent?d19g2238 2005/09/17 2005-09-14qE Eric NJEDJOU^Technical, Binding_14`37a5.2cIf i would like to transition between two links I won"t use already existing messages because intra-romaing messages were not dedicated for inter-system d20g2239jjmediavWzWmerged֗Wmih_W`WaWցW֍W֛W֩WWWWWWWmihinfrastructurenodeinfrastructurenodethatincludesanVmihlinkendpointmih-activeendpointofalinkthatfallswVmihmobilenodemobilenodewithatleastonemih-activeendVmihnetworkaddressinformationshouldbedeletedandthein֩VmihnodeofattachmentmihinfrastructurenodethatincludesVVVWWWWmih-activeentityacommunicationentityegalinkendpointVmnaWeWmobileSWaWqWzW֛WWWWmobilenodenetworknodethatcanchangepointofattachmentVmobile-nodeWmobility`WeW~Wmobility-management^W_Wmode֤WmodelօWmoredWmostmWnWmotorolarWname֗Wneed{W֛Wneedtoagreeonidentifiersmihidsmobileterminalids֛Vneeds֍W֍W vj|E Eric NJEDJOU^Technical, Binding_17`27a5.4.1cReplace with "upper layers" d31g2250jReplace with "upper layers"  2005/09/17|E Eric NJEDJOU^Technical, Binding_17`27a5.4.1cReplace with "upper layers" d31g2250jReplace with "upper layers"  2005/09/15 ֮cAMove the introductory text and figure of section 6.3.1 to Annex XX. Include the following text in Section 6.3.1 instead. Media Independent Information Service (MIIS) provides a framework by which a MIH Function (Media Independent Handover Function) both in the mobile node (a.k.a UE or STA) and in the network can discover and obtain information of homogeneous or heterogeneous network within a geographical area to facilitate the handovers. MIIS includes support for various InformatBion Elements (IEs) (Section 6. 3.2 ). Information Elements provide information that is essential for a handover module to make intelligent handover decision. Depending upon the type of mobility support and use case scenarios, different types of information elements may be necessary for perfroming handovers. Such case scenarios are described in Annex YY and following subsection describes the reference model of MIIS. 6.3.1.1 MIIS Reference Model [nsert the text from Section 2 of d K֮cC8ocument number 21-05-0348-01-0000_Higher_layer_IS.doc] +cmovetheintroductorytextandfigureofsection6.3.1toan֮VmsdusWmsecsּWWmultiplewWxWֵWWmustWWWWmyzWnameֺWּWWWWWWWWnametypedescriptionVnamelyWnamingWnas-port-typeWWncmsWnecessarilycWnecessary֮WWneedfW{W֚W֟W֠W֢W֬WWWWWneedexplicittextdefiningthescenariomobilegeneratedorVneednotdetection{Vneeded֬WWneeds֌Wneighbor־WneighborhoodWneighboringWWWWneighboring-networkWneighboring-poaWWcnetwork@newsentencesincethemaydraftok@of@ohba@org/2000/01/rdf-sche@out@nparameter@Hpossible@rather@Yrelated@tion5.5.3withsection5.5.3incontributionwit@reprovision@mresponsible@rlc@schema-based@should@:specifying@subsequent@Psynchronous@gthe@thelinkeventrequesthasnotbeendefinedanywhere@there@thisisonlytruefor11thedraftneedstobemoregeneric@thisreferenceisnotadaptedtoieee802ietfvocabularyis@tobetakenoutofthespecification@unidirectional@valueoflinkparameter@Oweneedtospecifythedifferencebetweenthetwo@whatdoeslayer2meanweneedtobedeeplyaccurateinthis@whywouldiwanttopropagateeventtotheremotel3mpwhat@within@4d0@Ɗ75@ifig@ja@also@completereworkingofthispart@GKd82-31-450-1879gAMWhen MIH_Scan command is issued to request scanning for multiple links, each link may scan to find the neighboring PoAs. If the MIH capability delivery through broadcast message is adopted by SDOs, MIH capability can be discovered during scanning. It is natural to include MIH capability information in the scanning response. M 2005/09/17EJinFLeeGjins978@lge.com_Technical, Non-binding`58a54b7.2.11cA[Insert valueOfLinkParameter as one of parameters, Page 59, Line10 ]: Parameters ------------------------------------------------------------------------------------------------------------------------------------------ Name | Type | Description ------------------------------------------------------------------------------------------------------------d82-31-450-1879ֱObserverֲEWolfgangFGroetingGwolfgang.groeting@siemens.comd +492871912142 2005/09/17ObserverֳEWolfgangFGroetingGwolfgang.groeting@siemens.comd +492871912142 2005/09/17ObserverִEVivekFGuptaGvivek.g.gupta@intel.com_Technical, Non-binding`15a55b5.3.2cASReplace current section 5.3.2 by the section 5.3.2 in DCN # 21-05-0361-00-0000 " S@A>  7  O  >d 503 712 1754gThis is to add information about a general Communication Model and the specific interfaces/reference points within scope of IEEE 802.21 for the various services. 2005/09/17MemberֵEVivekFGuptaGvivek.g.gupta@intel.com_Technical, Non-binding`16a11b5.3.3cd 503 712 1754Member ֱgAProposal to change the present MIH General Packet Format (same applies for the MIIS packet format) - Use fixed header instead of variable header to avoid scheduling problems - Locate variable MIH Func. Destination/Source Identifier before MIH Message data - Change MIH Function Identifier Length from 4 octets to 1 octet - Unusual that MIH Function ID Length value > 255 -Examples: MAC address = 6, IPv4 = 4, IPv6 = 16 - Change Transaction ID from 1 octet to 4 octets - TransactionBls IDs do have a value greater than 255 - Examples: IP - packet ID = 2 bytes; TCP - sequence no. = 4 bytes Zi27 2005/09/17Xccalled֭WcanaWlWoWvWyWցW֎W֑W֜W֮WֵWWWWWWWcan't։W֜W֝Wcan'tfigureouthowisthissapused։Vcannot־WcapabilitiesWcapabilityWWWWcardinalityWcareful]WcarnalityWcarried֬WWcarrierWcarriesWcarry־WWWcase֮WֵWWcasesWWcategoriesWcellWWclairoWclarificationւWքWclarifyWclassification֖WclassifiedWclearւWքWclearly`Wcolumn־WWcommand֑W֠W֢WWWcommandonthetitlebelowfigure14thisisonlyanexample֑VcommanddestinationcommandsoW֖WcommandsourcecommentgWiWcomments־WcommunicateֵWWcommunicatesֵWcommunicationֵWWcomplete֔WconditionsSWconfigurationWconfigure֝WconnectWconnectionsW ֵd 503 712 1754g(Current section 5.3.3 is too ambiguous. i10 2005/09/17MemberֶEVivekFGuptaGvivek.g.gupta@intel.com_ Technical`19a62b5.5.1cVReplace section 5.5.1 with section 5.5.1 in contribution with DCN # 21-05-0361-00-0000d 503 712 1754gLUpdate the reference model for ethernet and make the description more clear. 2005/09/17MemberַEVivekFGuptaGvivek.g.gupta@intel.com_ Technical`20a45b5.5.2cAVReplace section 5.5.2 with section 5.5.2 in contribution with DCN # 21-05-0361-00-0000V@A  33d 503 712 1754g@Update the reference model for 802.11 and associated description 2005/09/17MemberָEVivekFGuptaGvivek.g.gupta@intel.com_ Technical`21a56b5.5.3cVReplace section 5.5.3 with section 5.5.3 in contribution with DCN # 21-05-0361-00-0000d 503 712 1754g3Update Reference diagram and description for 802.16 2005/09/17MemberֹEVivekFGuptaGvivek.g.gupta@intel.comd 503 712 1754 ֵcAReplace section 5.3.3 with text below. The relationships between different peer MIH Function entities depends on the specifics of interworking scenario between different access networks. " The MIH Function in the terminal communicates with one and only one MIH Function in the PoA for a single access network. This is true for both L2 and L3 mode of transport " The MIH Function in the PoA of a gven access network may communicate with other MIH Functions in the same or different networks.B However this communication is not visible to the MIH Function within the terminal. " In case of multiple active links supported through multiple access networks, the MIH Function in the terminal may communicate with one MIH Function for each access network (or a single MIH Function across multiple access networks when applicable, e.g. L3 transport in tight coupling scenarios where one MIH Function may serve multiple accesses in a domain). " The MIH Function in the terminal may communicat ֵcCEe with other MIH Functions in the network which may provide Information Service function or MIH Controller type functionality. This communication may typically occur over L3. The MIH Function on the terminal can communicate with multiple such MIH Functions in different networks using different available access networks. " !@A*  33&  33*<wolfgangֱWֲWֳWwolfganggroetingsiemenscomֱVֲVֳVyohbaWWWWWWWWWWWWWWWWWyohbataritoshibacomVVVVVVVVVVVVVVVVVfceachֵWWWWWWearlierWeaseWeavesdroppedoWeci֭WeditorWeffectWeitherWWWeitherdeletethefigure10ormodifyforconsistencyVelement֗W֬WWWWelements֮W־WWWenableWenablers_WencapsulatesּWWencapsulatingּWWendingWWWWenhancementsWenoughdWenterpriseWenterprise-numberWWentirelyWWWentitiesֵWWWWWWentity~WWWWWWWWWentriesּWWWenumeratedWequalityWW֒WֻWּWWeventsourceWevery֛WexactlypWWexample֑WWWexamplesWexchange_WWexhangepWexist֑WexistingqWWexists֕WextendedWWWextensibilityWextractWfacilitate֮WfailֺWWfigֹWOdƊ75ְ֮֯Ɗ7dՃփ׃؃كڃۃ܃݃ރ߃ƊƊ9TgNjBVƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃnjZ92Sֱֲֳi10ֵֺW1422W23W26ֽ27ֱ4W5W6W7ֿWW8W9ֹWandreaWWWWWWWWWWWWandreapererzqiaobingVVVVVVVVVVVVigureֿWWWWfigure22Vfigure23Vfigure7ֿVfigure8VpererzWWWWWWWWWWqiaobingWWWWWWWWWWt1t2Wt2t3Vt3WtableWWWWtable4Vtable5Vtable6Vtable7Vj802.11zW802.21nWWWW*research֮W֯WְWronnykimWWWWWWWWWWWWronnykimlgecomVVVVVVVVVVVVsgWWWWWsiemensֱWֲWֳWsreemanthulaWWWWWWWWWWWWWsrinivasWWWWWWWWWWWWWVVVVVVVsubir֮W֯WְWsubirresearchtelcordiacom֮V֯VְVtariWWWWWWWWWWWWWWWWWtelcordia֮W֯WְWtoshibaWWWWWWWWWWWWWWWWWvivekִWֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWvivekgguptaintelcomִVֵVֶVַVָVֹVֺVֻVּVֽV־VֿVVV-mcreplacesection5.5.3withsection5.5.3incontributionwitָVreplacesection5.6withsection5.6incontributionwithdcֺVreplacetable23withtheonedescribedinsection2.4of21Vreplacetable4withtheonedescribedinsection2.1of21-Vreplacetable5withtheonedescribedinsection2.2of21-Vreplacetextbetweenlines20and44ofpage41withthefolVreplacetextstartingatline10ofpage116andendingatlVreplacetextstartingatline27ofpage89andendingatliVreplacethetextwithVreplacethetwoparagraphsstartingatline1ofpage47witVreplacewithupperlayers|Vreplacewithupperlayersmultipleoccurencesofl3mpwVxVreplacedtWuWreport־WWreports־WrepositoryWrepresentWrepresentationWrepresentedWrepresentsWapindicatestheresultoflinksetupprocessVretrievedWrevisedWricherWrightW "LֹMemberֺEVivekFGuptaGvivek.g.gupta@intel.com_ Technical`25a34b5.6cAReplace section 5.6 with section 5.6 in contribution with DCN # 21-05-0361-00-0000 ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description ---------------------------------------------------------------------------------------------d 503 712 1754Memberֹ_ Technical`25a141b5.6cFReplace Fig 9 with Fig 9 in contribution with DCN # 21-05-0361-00-0000d 503 712 1754gGUpdate Fig 9 based on changes in Reference models for 802.11 and 802.16iFig 9 2005/09/17#%fֺd 503 712 1754g?Update the section based on changes to SAPs and reference modeliFig 10 2005/09/17MemberֻEVivekFGuptaGvivek.g.gupta@intel.com_Technical, Non-binding`31a22b6.1.2cAWDelete lines 22-43. Description of Link Synchronous Events and Link Transmission EventsW@A  d 503 712 1754gThe definition of these type of events is not clear and these events are not well defined in the draft. This just adds to confusion. 2005/09/17MemberּEVivekFGuptaGvivek.g.gupta@intel.com_Technical, Non-binding`35a22bTable-1cd 503 712 1754Member# ֺcB------------------------------------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- Result | BITMAP | Indicates the result of Link setup process. C | | 0: Success | | 1: Authentication Fail | | 2: Link setup timeout | | 3~7: Reserved ---------------------------------------------"! ֺcDs------------------------------------------------------------------------------------------------------------------ =@Az  33R  S  +      z')ּd 503 712 1754gIt's not clear why these events are needed. They are not very useful in the generic handover case. In some cases the functionality specified by some of these events is already covered by other primitives. 2005/09/17MemberֽEVivekFGuptaGvivek.g.gupta@intel.com_ Editorial`144a42bAnnex DcA Delete Anex D @A  d 503 712 1754gAnnex D contents are captured by other independent documents and it is difficult to keep the draft and those documents in synch. Besides those documents would be submitted independently to other standard groups. We dont need this info in 802.21 draft.i26 2005/09/17Member־EVivekFGuptaGvivek.g.gupta@intel.com_ Technical`42a41bTable-5cd 503 712 1754Member!& ּcADelete entries for Event Identifiers 7-11 from the table. Delete all subsequent reference to these events from all other corresponding sections of the draft ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description ------------------B---------------------------------------------------------------------------------------------------------------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- TimeDifference | Time in msecs %' ּcC | When a PoA encapsulates Agent Advertisement | | or Router Advertisement in Network Address | | Information parameter, this parameter is time | | difference between the time of caching the D | | information and the time of encapsulating the | | information ---------------------------------------------------------------------------------------------------------------------------------------------------------------TAR  33  33  v  R&$ mּc@AR  33  33  v  R).־d 503 712 1754gCDynamically changing IEs cannot be supported by Information Service 2005/09/17MemberֿEVivekFGuptaGvivek.g.gupta@intel.com_ Technical`23a1b5.5.4c-Remove MIH_MGMT_SAP from 3GPP Reference Modeld 503 712 1754gMIH_MGMT_SAP is not definediFigure 7 2005/09/17MemberEVivekFGuptaGvivek.g.gupta@intel.com_ Technical`24a1b5.5.5c.Remove MIH_MGMT_SAP from 3GPP2 Reference Modeld 503 712 1754gMIH_MGMT_SAP is not definediFigure 8 2005/09/17MemberEVivekFGuptaGvivek.g.gupta@intel.com_ Technical`49a31b7cReorganize SAPs in section 7 based on revised SAP definitions in section 5.6. Media Specific SAPs MIH_LINK_SAP C_SAP M_SAP MIH_RRC_SAP MIH_PPP_SAP MIH_LAC_SAP Network management SAPs MIH_SME_SAP Media Independent SAPs MIH_SAP d 503 712 1754gHMIH_MGMT_SAP is not defined and the overall SAP organization has changed 2005/09/17MemberERonnyFKimGronnykim@lge.comd82-31-450-1879Member$( \־cA For Neighbor Report IEs: remove measurement report from the description column. Measurement reports carry dynamic data and hence cannot be satisfied by Information Service For QoS: The elements listed in Comments column are dnamic values and cannot be supported be Information Service.@A  33NgִWֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWgroetingֱWֲWֳWguptaִWֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWintelִWֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWjins978WWWWWWWjins978lgecomVVVVVVVkohtmWWWWWlgeWWWWWWWWWWWWWWWWWWWmotWWnokiaWWWWWWWWWWWWWpanasonicWWWWWqxie1WWqxie1emailmotcomVVHcmiis֮WWWWmincardinalityWmininclusiveWmmobilityyWmobilecW֮WWWWWmobility_W`WeWօW֜W֮Wmode֞W֤WֵWmodelօW֐W֑W֮WֿWWWWWWWmodification֭WmodifyWWWWWWmodifythefollowingtextVmodifythetextpage74line13Vmodifythe11throwintable14asindicatedbelowVmodifying֭Wmodule֮Wmore֌WWWWmostWWmostlyWmove֮WWxc5.3.2ִW5.3.3֘WֵW5.5.1ֶW5.5.2ַW5.5.3ָW5.6ֺWW5.6.1WW5.6.1mihmgmtsapVV5.6.2W5.6.3W5.6.4W5.6.5W5.6.6W5.6.76W5.6.87W5.6.9W5.6.98W58W59WW6֭W֮WWWW6.1.5WW6.1.5primitivesforeventsVentsV6.2.5.1֖W6.3.1֮W6.3.1.1֮W7ֺWWWW7-11ּW7.1W7.2W7.2.11.3W7.2.13WW7.2.14WW7.2.15WW7.2.16WW7.2.17WW7.2.7W7.4.10.2֥W֧W7.4.10.2.4֦W7.4.11.2.2W7.4.13.2.2W7.4.14.1.2W7.4.14.3W7.4.14.3.1W7.4.14.3.2W7.4.14.3.3W7.4.9W7.4.9mihscanV74W8W8-3W8.4W8.5.3W802dW802.11vWzW֐WWWWW802.16WWW802.21]W_WfWWWWWcreplacewWxW|W~WִWֵWֶWַWָWֹWֺWWWWWWWWWWWWreplace6.1.5primitivesforlinklayereventsby6.1.5primVreplacecurrentsection5.3.2bythesection5.3.2indcn21ִVreplacefig9withfig9incontributionwithdcn21-05-0361ֹVreplacesection5.3.3withtextbelowֵVreplacesection5.5.1withsection5.5.1incontributionwitֶVreplacesection5.5.2withsection5.5.2incontributionwitַV(0z_Technical, Non-binding`20a1b5.5.3cAKAdopt the remedy 1 and 2 in the contribution " DCN # 21-05-0359-00-0000 " K@A>  33/  33G  33>d82-31-450-1879gAIn order to reflect the discussion on the MIH reference model for 802.16 during Ad Hoc teleconference, it is necessary to change the figure as suggested in the contribution " DCN # 21-05-0359-00-0000 ". @A>  33  33  33>i6 2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`26a1b5.6cd82-31-450-1879Member37d82-31-450-1879gAXIn 5.6, SAPs such as MIH_PHY_SAP, MIH_LLC_SAP are descibed but elsewhere they are not illustrated or defined. Some of SAPs only apply to some media specific type, e.g., MIH_SME_SAP only applies to 802.11, MIH_MAC_SAP applies to 802.3 and 11 only. For consistency, it is required to specify which SAP belong to which media specific interface. Xi10 2005/09/17MemberERonnyFKimGronnykim@lge.com_ Editorial`13a44b5.1.9c1change all "handoff" to "handover" in the draft. d82-31-450-1879gi"Handover" and "Handoff" are used together in the draft. For consistency, use one term for same meaing.  2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`49a36b7.1, 7.2cd82-31-450-1879Member.1 cAEither delete the figure 10 or modify for consistency; Make the following text change; 5.6.1 MIH_MGMT_SAP This SAP is defined in 802.11, 3GPP, 3GPP2. This defines the interface between the MIH Function layer and the management plane of different networks. This SAP can be used for sending MIH messages between MIH Function and local link layer entities as well as between peer MIH Function entities. Messages based on management frames can be sent in the unauthenticated state as well. BThe MIH_MGMT_SAP defines primitives for MIES, MICS and MIIS. 5.6.2 MIH_SME_SAP This SAP is defined in 802.11. This SAP defines the interface between MIH Function layer and the Station Management Entity or the Network Management System. This SAP defines the MIH interface with the system and is used for MIH configuration and operation. 5.6.3 MIH_SAP This SAP defines the interface between MIH and a L3MP, or a Handover Function MIH users which might reside at higher layer or a higher layer T02 cCransport as well. The interface between MIH and higher layers is a local interface which may depend on the choice of L3MP as well. The methods and other messages defined by this SAP result in local communication between peer layer entities. Definition of this SAP is required to define the scope and functionality of MIH Function. 5.6.4 MIH_MAC_SAP This SAP is defined in 802.3, and 802.11. This SAP defines the interface between MIH Functon and media specific MAC. The interfaces defined by Dthis SAP are primarily used to transfer data (MSDUs) between peer entities. No new interfaces and primitives need to be defined for this SAP. The interfaces defined by this SAP can be used to deliver MIH protocol based payloads to peer MIH entities usng the data plane. 5.6.5 MIH_PHY_SAP This SAP defines the direct interface between MIH Function and the media specific PHY. The MIH Function shall communicate with different media specific PHYs using the media specific MACs. There are no ne13 cEw primitives to be defined as part of this SAP. 5.6.6 MIH_LLC_SAP This defines the LLC interface to MIH. The MIH can directly use the existing LLC primitives to initiate connections and communicate with peer LLC entities and thus establish data path for sending MSDUs across different links. There are no new primitives to be defined as part of this SAP. 5.6.76 MIH_RRC_SAP This SAP is defined in 3GPP. This defines the interface between the MIH Function and RRC. 5.6.87 MIH_PPP_SAP This SAPF is defined in 3GPP2. This defines the interface between the MIH Function and PPP. 5.6.98 MIH_LAC_SAP This SAP is defined in 3GPP2. This defines the interface between the MIH Function and LAC. 5.6.9 M_SAP (Management SAP) This SAP is defined for management purposes in 802.16 and can be extended to define the interface between MIH Function and Management Entity. 5.6.9 C_SAP (Control SAP) This SAP is defined for control purposes in 802.16 and can be extended to define the interface betw2/ cG)een MIH Function and Management Entity.  @A.  33X  33m    33  33    33>  ]  33    33    33     33}    33    33:  d  33    33   B 33 !  "  #  33 0  M  33       33     33       33   +  33 h    33   0  33 1    33mcwithinrW֮WֵWwithoutWwonqWword]WwouldqWyWwrongkWwwwWWx1Wx2Wx3WxmlWWxmlnsWWxsWxsdWWxsiWxx֮WxxxWyoshihiroWWWyoulWyy֮Wzz֯Wd S`paedc‚!f‚"g‚#i‚$j‚%k‚&l‚'m‚(n‚)o‚*p‚1q‚2r‚3s‚4t‚5u‚6v‚7w‚8x‚9y‚:z‚A{‚B|‚C}‚D~‚E‚Fր‚Gց‚Hւ‚Iք‚Jօ‚Qֆ‚Rֈ‚S։‚T֊‚U֋‚V֌‚W֍‚X֏‚Y֎‚Z֐‚a֑‚b֒‚c֓‚d֔‚e֕‚f֖‚g֗‚h֘‚i֙‚j֚‚q֛‚r֜‚s֞‚t֝‚u֟‚v֠‚w֢‚x֣‚y֤‚z֥‚֦‚֧‚֨‚֩‚֪‚֫‚֬‚֭ƊaH#(eִֵֶַָֹֺֻּֽ־ֿccinstead֮WintegerWintelligent֮Winter-systemqWinterchangeֱWinterchangetransactionidandmihfunctionidlengthpositiֱVinterfaceoWvWzWWWinterfacesWinterfacingWinterferenceWinternationalizationWinterruptedWinterworkingֵWintofWWWWintra-romaingqWintroducedWintroductionWintroductory֮WinversefunctionalproWipfWyWօWirrespectiveWisSW`WcWdWeWfWjWkWpWrWyWւWքW։W֌W֎W֐W֑W֓W֔W֖W֞W֤W֥W֦W֧W֩W֬W֭W֮W֯WֵWּWWWWWWWWWWWWWWWWWWWWissuedWWWit`WfWpWyW֐WWWWWWW8;d82-31-450-1879gIf the MIH reference model for 802.16 is accepted, section 7' s structure for 802.16 shall be changed accordingly. Since MIH_SME_SAP is only applied to 802.11 and MIH_MGMT_SAP is not applied to 802.16, restriction shall be added in the text.  2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`60a32b7.2.13cCDelete section 7.2.13 or 7.2.14 or add more handover related text. d82-31-450-1879gAIn section 7.2.13 and 7.2.14 SDU related event services are described. These triggers are for interaction between MAC and intermediate buffers (?). What is the purpose of these events? Are they related to the handover? This trigger is not very general enough to use for handover case. If there is no full context transfer including ARQ state from old PoA to new PoA, these trigger can not be used for handover case. 2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`62d82-31-450-1879Member/8 cAMake the following text change; 5.6.1 MIH_MGMT_SAP This SAP is defined in 802.11, 3GPP, 3GPP2. This defines the interface between the MIH Function layer 7.1 Introduction Following are the key SAPs MIH Function uses for interfacing other entities. 1) MIH_MGMT_SAP: The MIH Function uses this SAP for interfacing with lower layers of media specific access networks. Primitives defined as part of this SAP are recommended as enhancements to media specific SAPs. This SAP is not applied to 802B.16. In case of 802.16, M_SAP shall perform the same function as MIH_MGMT_SAP. 2) MIH_SME_SAP: The MIH Function uses this SAP for interfacing with the System Management Entity in 802.11. or Network Management entity. In case of 802.16, M_SAP shall provide interface between MIH Function and Network Control and Management System (NCMS). 3) MIH_SAP: This is the main SAP which upper layers use for interfacing with MIH Function and accessing the various MIH services. This is a new SAP. 7.276 cC MIH_MGMT_SAP, M_SAP Primitives The key primitives defined as part of MIH_MGMT_SAP, M_SAP are described in the table below. Table 8.MIH_MGMT_SAP, M_SAP Primitives@A  33   335  a  33b  33    33  =  33    33    33  B  33    33.  5  33    33cmanagement_W`WeWyWքWօW֜WWWWWWmanyWmarkWmatter֬WmattersfWmaxcardinalityWmaximumWmaxinclusiveWmay֋W֮WֵWWWWWWWWWWmdiWWWmean֚WmeaningWmeasurement־Wmedia֮WWWWWWWmedia-dependentWWmedia-dependent-infoWmedia-independentWWmedia-independent-inWmedia-specificWmergeWWmerged֗WmessageֱWWmessagesoWqWWWmethodsWWmgmtֿWWWWmibWmib-iiWmicsWWmiesWWmight֬WWmih`WpWrWvWzWցWքW֓W֔W֝W֟W֥W֦W֧W֩W֮WֱWֵWֿWWWWWWWWWWWWWWWWWWWWWmiiWWWcshould]W֐W֒W֩WWWshoulddifferentiatephymacllcrlcevents֒Vshow`WWshownWWWshowsWsignalWsignalingpWsince֋WsinglefW֠W֢WֵWsits`WsmeWWWsmiWso`WaW֊WWsolveWsome֖W֩W֬WWWsomehowWsource֠WWWWWsparqlWspecificjWւWքW֍WWWWWWWWWspecifictoonetechnology֍VspecificationsW֚WspecificsֵWspecifiedWWspecifiesWWspecify֟WW6>a14b7.2.15, 7.2.16, 7.2.17cDelete Section 7.2.15, 7.2.16, 7.2.17 or add more text to clarify the differences from Link_Going_Down, Link_Down, and Link_Up. d82-31-450-1879gAIn section 7.2.15, 7.2.16, 7.2.17, Link_Handover_Imminent.indication, Link_Handover_Proceeding.Indication, Link_Handover_Complete.Indication are described repectively. What is the difference between Link_Handover_Imminent.Indication and Link_Going_Down ? What is the difference between Link_Handover_Proceeding.Indication and Link_Down? What is the difference between Link_Handover_Complete.Indication and Link_Up? I think there is overlap in event services.  2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`55a49b7.2.7.1cd82-31-450-1879MembercdeliverւWքWWdenyWdependWdepending֮WWdependsֵWdescribe֖WWdescribed֘W֮WWWWWWdescribes֮WWWdescribingWdescriptionւWքW֠W֢WֺWֻWּW־WWWWWWdescriptionsWdestination֢WWdestructiveaWdetailedWdetailsfWdetectWdetection{WdeterminelWpWWdevicesWdhcpWdifference֟WּWWdifferencesWdifferentmWnW֎W֮WֵWWWWWWdifferentiate֒WdiffservWdirectWWdistinctWdistributedWdnamic־WdopW֤Wdoc֬W֭W֮W֯WWWWdoctypeWdocumentnW֬W֮W֯WdoesrWyW֚W֟WdomainֵWWWdon't֤WdownWdraft֋W֌WּWWduringWdynamic־WeֵWWWWWW?Ad82-31-450-1879gIn the draft, all successful cases are considered. During a link setup procedure, link setup may fail due to various reason, and failure shall be reported to upper layer. 2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`81a58b7.4.12cADAdopt the remedy 3 in the contribution " DCN # 21-05-0359-00-0000 " D@A>  33)  33A  33>d82-31-450-1879gMIH Handover Commit is defined in Table 10. MIH_Handover_Commit.request/response primitives section shall be aded in the text.  2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`86a22b 7.47.13.2.2cd82-31-450-1879Member;? cAInsert the parameter "result" in parameters of 7.2.7: ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description -------------------------------------------------------------------------------------------------------------------------B--------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- Result | BITMAP | Indicates the result of Link setup process. >= cC | | 0: Success | | 1: Authentication Fail | | 2: Link setup timeout | | 3~7: Reserved -------------------------------------------------------------------------DW-------------------------------------------------------------------------------------- !@A  335  336  7    x    BDd82-31-450-1879gSince MIH_Network_Address_Information.response can carry router advertisement or agent advertisment buffered at PoA, time difference for MS to check the freshness of the message shall be added.  2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`94a1b8.3cACAdopt the remedy 4 in the contribution " DCN # 21-05-0359-00-0000 "C@A>  33)  33A  33>d82-31-450-1879gmBecause figure 26 only reflects the IPv4 case, it is necessary to update the figure to reflect IPv6 as well. i26 2005/09/17MemberERonnyFKimGronnykim@lge.com_Technical, Non-binding`96a41b8.4cd82-31-450-1879Member=B cAInsert the parameter "TimeDifference" in Semantics Table of 7.4.13.2.2 as indicated below: ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description -----------------------------------------------------------------------------------B----------------------------------------------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- TimeDifference | Time in msecs | When a PoA encapsulates Agent Advertisement A@ cC | | or Router Advertisement in Network Address | | Information parameter, this parameter is time | | difference between the time of caching the | DI | information and the time of encapsulating the | | information ---------------------------------------------------------------------------------------------------------------------------------------------------------------@AR  33[  33]  5  REF*d82-31-450-1879giIn order to make standard TLV (Type Length Value) format, type field shall be added in all tables in 8.4. 2005/09/17MemberERonnyFKimGronnykim@lge.comd82-31-450-1879 2005/09/17MemberEJinFLeeGjins978@lge.com_Technical, Non-binding`75a60b 7.4.9.2.4cAModify the following text: [Modify the text, page 74, line 13]: 7.4.9 MIH Scan A MIH Scan command is issued by upper layer entities to discover the neighboring POA of the access networks. MIH Scan may contain the scan command for multiple links. The scan command for each link is defined in the related SDO and beyond the scope of the current version of the standard. If the currently active link is required to scan, it is most likely that the on-going session is interrupted. If the MIH cad82-31-450-1879@E cAInsert "type column" in all tables in the 8.4 section following the example below; editor shall insert type column in all tables in the 8.4 section and assign subsequent values in ascending order: ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Length | Value ------B---------------------------------------------------------------------------------------------------------------------------------------------------- SupportedEventList | 1 | 4 | ---------------------------------------------------------------------------------------------------------------------------------------------------------- SupportedCommandList | 2 | 4 | ---------------------DC cC------------------------------------------------------------------------------------------------------------------------------------`@A  33    33  33      33        33      CG cBpability may be discovered during scanning procedure, MIH_Scan.response may include MIH capability parameter. [Insert the MIH Capability parameter, page 74, line 59]: MIH_Scan.response ( Source Identifier, Destination Identifier, Scan Response Sets, MIH Capability ) -------------------C---------------------------------------------------------------------------- Name | Type | Valid Range | Description ----------------------------------------------------------------------------------------------- .. | .. | .. | .. ----------------------------------------------------------------------------------------------- MIH CapabilitF 0cDy | Flag | | 0: MIH Capability Not Supported | | | 1: MIH Capability Supported ----------------------------------------------------------------------------------------------- @A  33 33  @  B   ^        (  )             T  r w B n,cparameter֜WּWWWWWWWWWWWWparametersWWWparsetypeWpart֩WWWWparticularWpartnersWWpartsWpassedWWpathWpayloadsWpeerֵWWperformyWWperformanceaWperfroming֮WperiodicallyWphyfW֒WWWphysWphysicalWplaneWplease֬W֭WWpleaseseethecompaniondocument21-05-0365-00-0000-cmodelVplusWpoa֣WֵWּWWWWWWWWpoa-idWWpoa-id'sWpoa-typeWWpoasWWpointyW֞W֤WWWWWWpointsWpolicymWpoll֟WpositionSWpositionsֱWc1authenticationfailV1.0WW1.2W10WW11jW֌W֕WW112W116W13W14֑WW19W2fW֚W֮WֺWWWWWWWWWWW2linksetuptimeoutV2.1W2.2W2.4W20WW21rW21-05-0346-0000WWW21-05-0348-01-0000֮W֯W21-05-0359-00-0000WWWW21-05-0361-00-0000ִWֶWַWָWֹWֺWW22-43ֻW23WW27W3օW֯WֺWWWWWWWWWWWWWWWWWWWW37reservedV3.2֮W30W34W36W3825W39W3fffffffW3ffffffffW3gppֿWWW3gpp2WWW4WWWWWWW41W42W44WW45W46WW47W5WWWWMQ~d82-31-450-1879gABy the current draft, when MIH Function receives Link_Detected.indication event from the active links, MIH Function may try to find out additional propoerties of the links before selecting new link for establishing connectivity. If the Link_Detected.indication is triggered as a result of PoA discovery procedure including scanning, 'valueOfLinkParameter' can be included. Therefore, we propose to add the parameter "valueOfLinkParameter" in Link_Detected.indication so that MIH Function sBelects the target connection link instantly without discovering additional link properties such as link speed, link bit error rate. r 2005/09/17EJinFLeeGjins978@lge.com_ Editorial`34a38b6.1.5cARReplace "6.1.5 Primitives for Link Layer Events" by "6.1.5 Primitives for Events"R@A  33d82-31-450-1879L cB------------------------------ EventSource | Link_EVENT_SOURCE | The origination point from where the event is generated ------------------------------------------------------------------------------------------------------------------------------------------ MacMobile | MAC Address | MAC address of Mobile Terminal Terminal --------------------------------------------------------------------C---------------------------------------------------------------------- ValueOfLink | | Specify the value of link parameter Parameter ------------------------------------------------------------------------------------------------------------------------------------------ MIH Capability | Flag | 0: MIH Capability Not Supported KM cD 1: MIH Capability Supported ------------------------------------------------------------------------------------------------------------------------------------------ Examples of link layer parameters : Link Speed Link Bit Error Rate Link Received Signal Strength Indication Link Carrier to Interference plus Noise Ratio Modify the subsection 7.2.11.3 as shown below, Page 59, Line 36 ] : Upper layers include MIH Function may discover additional properties of the Elink before selecting it for establishing connectivity. If the 'ValueOfLinkParameter' is included, upper layers may select the link to connect based on the value of 'ValueOfLinkParameter. v@LJ ocAV  33G 33 33  33" #  / o      33  '  33k 33l 33  V*NbenjaminWWWWWbenjaminkohtmsgpanasoniccomVVVVVcom֮W֯WְWֱWֲWֳWִWֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWemailWWcvalueoflinkparameterWvalues־WWvariableWvarious֮WWWverifyWversionWWWviaWWWviewyWviewsfWvisibilitySWvisibleֵWvocabularydWWw3WWwantyW֞WwaysWwe]WfWpW֚W֛W֞W֟W֤WWwealreadyhavemihpollwhichdoesthesamething֟VgrcsubsequentּWWsuccessֺWWsuch`WrW֮WֵWWWWsufficientfWsuggested֣W֭WsupplementWWWsupport֜W֮WWsupportedֵW־WWWWsupportedcommandlistWsupportedeventlistWsupportsWsupposedWWsure֊WswitchWsymmetryWtable֛W֜W֝W֞W֠W֢W֣W֤WּWWWWWWWWtablesWWWtakensWtalkvWzWtalkingrWtechnologiesWtechnology֍Wterm֠W֢WterminalaW֛W֬WֵWWterminologyjWtextoW֥W֦W֧W֮W֯WֵWWWWWWWWWWtextisthatsameasin7.4.10.2mihhandoverinitiaterespo֥V֧Vtextisthatsameasin7.4.10.2.4mihhandoverinitiateres֦Vthat`WaWcWlWpWrW֖W֛W֥W֦W֧W֬W֮WWWWJRgsection 6.1.5 is to show the general primitive format for event service, not only for link layer events. Therefore, title should be changed. 2005/09/17EJinFLeeGjins978@lge.com_ Editorial`96a20b8.3.2cAModify the11th row in table 14 as indicated below ---------------------------------------------------------------------------------------------------------------------------------------------------- 11 | MIH Command Discover MIH Event Discover | Request/Response | Event Service | ----------------------------------------------------------------------------------------------------------------------------------------------------@A  332 33    33  33    33d82-31-450-1879QTgThe MIH message for 'MIH Command Discover' in table 14 does not exist in the current draft. In addition, MIH Event Discover message was omitted from this table. Therefore, we suggest that MIH command Discover should be replaced with MIH Event Discoveri14 2005/09/17EJinFLeeGjins978@lge.com_Technical, Non-binding`64a44b7.4.1cA@Adopt Remedy 5 in the contribution "DCN # 21-05-0359-00-0000" @@A  33d82-31-450-1879gDetails of the MIH Capability Discover was left out. As the proposed contribution, MIH_Capabilty_Discover.request/response primitive should be defined. 2005/09/17EJinFLeeGjins978@lge.com_ Editorial`80a53b 7.4.11.2.2cd82-31-450-1879TVLd82-31-450-1879gone of parameters for MIH_Handover_Prepare.response is missing. For consistency with the table of section 7.4.11.2.2, 'ResourceStatus' should be added. 2005/09/17EJinFLeeGjins978@lge.comd82-31-450-1879 2005/09/17E YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`41a20b6.3.2cAReplace text between lines 20 and 44 of page 41 with the following: " The information elements provided by the Information Service can be classified into two categories: 1) Media-Independent Information (MII): These information elements describe the media-independent properties of the network. MII includes of Point of Attachment, Neighboring Networks, Neighboring PoAs, Location of PoA, Network Operator, Roaming Partners, Cost, Higher Layer Security Support, and Higher Layer QoS Supportd 732-699-5305MemberRS cAInsert the parameter "ResourceStatus" in subsection, 7.4.11.2.2 as indicated below: MIH_Handover_Prepare.response ( CommandSource , CommandDestination , CurrentLinkIdentifier , TranspoBrtLayer, ResouceStatus , QueryResourseList ) @A  33U 33s  33 33) 3  D 33W\d 732-699-5305gA- General Network Information (GNI) and Higher Layer Information (HLI) should be merged into "Media-Independent Information (MDI)". Link Layer Information (LLI) should be renamed to "Media-dependent Information (MII)". - Tables 4, 5 and 6 should be reduced into two tables of MDI and MII, and revised with more detailed description. - Definition of basic set and extended set needs to be clearly described in this section. 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`41a49b6.3.2cnReplace Table 4 with the one described in Section 2.1 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.d 732-699-5305gMemberSW cB . 2) Media-Dependent Information (MDI): These information 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. TCables 4 and 5 describe a set of information elements in both categories that include the basic and extended set. When new information elements are added to MII or MDI, they need to be most likely defined in the extended set. Information elements may be obtained via a PoA before the STA authenticates to the PoA irrespective of whether they belong to the basic or extended set. While all of the above information elements are necessary and will be available via 802.21 information service frVU cDamework, it is important to note that MDI will be mostly directly available via media specific technologies. In cases where media specific amendments are not available or possible, information elements in MDI can be carried over via higher layer transport. "ccellularaW֣Wcertain֭WcertainlyfWchangeyWWWWWchangeallhandofftohandoverinthedraftVchangedWWcharacteristicsWWchoice֤WWchoose֠W֢WWclairoWclarificationւWքWclarifyWWWclarifymobilenodeinsection3requiredtofurtherclarifyVclarifypointofattachmentinsection3requiredtofurtherVclassWWclassesWWclassification֖WclassifiedWclearւWքWclearly`WWcmdWcodeWcollectionWcolumn־WWWWcommand֑W֠W֢WWWWWWcommandonthetitlebelowfigure14thisisonlyanexample֑VcommanddestinationcommandinformationseWcommandresultsetWcommandsoW֖WWWcommandsourceWcommandxxWcommentgWiWWWWHcrather֓W֔W֬WratioWrdfWWWWrdf/xmlWrdfsWreadyWrecalled`WreceiveWWWreceivedWrecommendedWreconsiderWreferencedWօW֮WּWֿWWWWregisterWWregisteringWregistrationWWWrelationsWrelationshipWrelationshipsֵWremedyWWWWremoteyW֖WWWremove־WֿWWWWWWWWWWWWWWremoveannexc2entirelyVremoveannexc3entirelyVremoveannexc4entirelyVremovefigure22Vremovemihmgmtsapfrom3gppreferencemodelֿVremovemihmgmtsapfrom3gpp2referencemodelVremovetable6Vremovetable7Vremovetextstartingatline20ofpage87andendingatlinVreorganisation֬WreorganizeWreorganizesapsinsection7basedonrevisedsapdefinitionVlcamodificationissuggestedtosection6byaddingnewprimi֭VaabbccddeeffWabilityWableWaboutWW\]MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`42a39b6.3.2cnReplace Table 5 with the one described in Section 2.2 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.d 732-699-5305gA- Media Types column is not meaningful. The Media Types column should be replaced with another column that indicates whether a given information element belongs to basic set or extended set. - "Neighbor information" can contain MII and MDI, and can be obtained by querying the basic set and extended set of each PoA in the "neighboring PoAs" information element in MII. Thus, this is redundant and should be removed from MDI. - "AccessRouterInfo" is not MDI and should be removed. - More BLdetailed description and comments are needed for each information elements. :iTable 5 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`43a6b6.3.2cRemove Table 6.d 732-699-5305MemberU[ gA- Media Types column is not meaningful. The Media Types column should be replaced with another column that indicates whether a given information element belongs to basic set or extended set. - "List of networks available" should be renamed to a less confusing name. - "Network standards supported" is ambiguous and should be removed. - "Network identifier" is similar to "Operator" and should be removed. - "Operator" needs to have not only a name but also a unique identifier. - "IP VersBion" is not useful information and should be removed from MII. - "SLAList" information is ambiguous and should be removed. - "neighbor information" contain only static and limited information such as a list of neighboring PoAs. Also it should be replaced to more specific name like "neighboring PoAs". - "AccessRouterInfo" is too detailed to be defined in the basic set. - More detailed description and comments are needed for each information elements. iTable 4 2005/09/17[`gS- Since GNI and HLI are merged into MII, this table for HLI is not needed anymore.iTable 6 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`43a42b6.3.2cAReplace the text with: " MIHF entity (e.g., a STA or network entity) can extract the information elements in the basic set and the extended set either from media specific broadcast information or by sending a specific request/response primitive. On the other hand, before sending a request/response, the MIHF entity should have the knowledge that the network supports the 802.21 MIH standard (e.g., via a management frame that carries capability information). For example, MIHF entity in STA md 732-699-5305Member_0]^_@`ace`dpfgijk‚#lm‚$no‚%pqrs‚&‚'tu‚(vwxyz{|‚)}‚*~‚1ր‚2ցւ‚4ք‚6օֆ‚7ֈ։‚8֊֋֌֍‚9֏‚A֭‚B֎‚D֐֑‚E֒‚F֓֔‚I֕‚J֖֬‚S֗‚W֘‚Z֙‚f֛֚֜‚֞‚֝‚֢֣֤֟֠‚֥‚֦֧‚֨‚֩‚֪‚֫` @֏p~֊֖nlc‚!]vw֨‚#^xy֚‚$‚%֟‚&ִ‚'ֵ֩‚(_‚)oz‚*ֶ‚1ַ‚2ָ֥‚4ֿ‚5}‚6ֹֺ֘‚7֋֎‚8{|‚Bfkֻ‚C‚E֦֕Ѓ‚Fgּ‚Gք‚Hpqր‚I‚J֮‚Qiց‚RdtՃ‚S־‚T؃‚Uֆ‚V֧‚Wuւ܃݃‚X‚Z֙`bd 732-699-5305gAJ- The text can be described without referring Table 7 (which is refereed incorrectly to as Table 8.3) and Figure 22. - The text should be revised that information elements in both the basic set and extended set can be obtained either from media-specific broadcast information or by sending a specific request/response primitive.J 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`44b6.3.2cRemove Figure 22.d 732-699-5305gFigure 22 is not useful.i Figure 22 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`45a1b6.3.2cb- Remove Table 7 - Remove text starting from line 39 of page 45 and ending at line 23 of page 46.d 732-699-5305gGTable 7 is just informative and should not be included in this section.iTable 7 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`46a58b6.3.3.1cd 732-699-5305Member]_ xcBcay request the MIHF entity of PoA for such information. It is important to note that before a STA is authenticated to the PoA and ready to exchange data, it should be able to obtain all the information elements listed in Tables 4, 5 and 6. These information elements may then be used by the STA's handover function to determine the right PoA to attach. "Qbid 732-699-5305gkSince the basic schema uses OWL in addition to RDF Schema, a brief description about OWL needs to be added. 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`46a59b6.3.3.1cAReplace the two paragraphs starting at line 1 of page 47 with: " As described earlier, the RDF schema definition for MIIS consists of two parts; the basic and the extended schema. The basic schema is not supposed to be updated. An MIH entity is typically pre-provisioned with the basic schema for ease of implementation of schema-based query. In scenarios where the basic schema is not pre-provisioned methods such as DHCP may be used to access the URL of the basic schema. Unlike the basic sd 732-699-5305Member_a YcAInsert the following text at line 58 of page 46: " In order to strictly define each information element in an RDF schema, the schema is augmented with Web Ontology language (OWL) [OWL]. OWL is a Web Ontology language. OWL uses both URIs for naming and the description framework provided by RDF to add the following capabilities to ontologies: - Ability to be distributed across many systems - Scalability - Compatibility with other Web standards for accessibility and internationalizationBR - Openness and extensibility OWL builds on RDF and RDF Schema and adds more vocabulary for describing properties and classes: among others, relations between classes (e.g. disjoint-ness), carnality (e.g. "exactly one"), equality, richer typing of properties and characteristics of properties (e.g. symmetry), and enumerated classes. "@5cinsertthefollowingtextatline58ofpage46Vinserttheparameterresourcestatusinsubsection7.4.11.2.2Vinserttheparameterresultinparametersof7.2.7Vinserttheparametertimedifferenceinsemanticstableof7.Vinserttypecolumninalltablesinthe8.4sectionfollowinVinsertvalueoflinkparameterasoneofparameterspage59linVinstanceWtcan]WfWvWzW֐W֑W֓W֔W֬WWWWWWWWWWօW֗W֭W֮W֯WֱWֵWֻWּW־WWWWWWWWWWWWWWWWWWWWWWWWWand/changesWanexֽWannex֮W֯WWWWanotherWanyWWWanywhere֑WapplicableֵWappliedWappropriateWarchitecture]WrWaredWօW֖W֮W־WWWWWWWWWarea֮Was`WfWgWiWoWrW֎W֠W֢W֤W֥W֦W֧WWWWWWWWWWWascendingWassignWassignedWWassociatedցWassociationcWoWatWWWWWWWattachWattached֬W֭WattachmentWWWWattachmentsWattributeWWcgenerallyaWgeneratedWWWgeneric֌WWWgeo-coordinateWWgeographicWgeographical֮WgivenWgocWfWgoingWgraphicalWgvenֵWhandlWWhandlingWhandoffpW֓W֔WWWhandoverlWpW֞W֤W֥W֦W֧W֮WWWWWWWWWhandovers֮WhascWmWrWtWuW֑WWW)cequipements֬WequivalentclassWerrorWes/cs֬Wessential`W֮WestablishWestablishingWevenoWyWevenaftersecureassociationtheeventscommandsandinformoVeventyW֑W֓W֔WּWWWWWWWeventsoW֎W֒WֻWּWWWWeventsourceWevery֛WexactlypWWexample֑WWWWWexamplesWexchange_WWexchangedWexhangepWexist֑WexistingqWWexists֕WexpectedWWexperienceWexplainedWexplicitWextendWextendedWWWWWextensibilityWextensibleWWextensionWextractWfacilitate֮WfailֺWWfigֹWPlcsynchronousֻWsystemWWsystemsaWWtqWtable֛W֜W֝W֞W֠W֢W֣W֤WּWWWWWWWWWWWWWtable-1WtablesWWWWWWWtakensWtalkvWzWtalkingrWtcp/ipWtechnologiesWtechnology֍WWterm֠W֢WterminalaW֛W֬WֵWWWterminologyjWtextoW֥W֦W֧W֮W֯WֵWWWWWWWWWWWWWWWWtextisthatsameasin7.4.10.2mihhandoverinitiaterespo֥V֧Vtextisthatsameasin7.4.10.2.4mihhandoverinitiateres֦Vthat`WaWcWlWpWrW֖W֛W֥W֦W֧W֬W֮WWWWWWWWWWkpd 732-699-5305gA- Some description is needed as to how extended schema can be created. - Use of DNS query for finding the FQDN part of the location of the extended schema is not useful because it does not tell the entire URL of the extended schema. Instead, use of DHCP might be better to tell the URL of the extended schema. - Since Figure 23 needs to be revised, the corresponding explanatory text in section 6.3.3.1 should be revised as well. 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`47b6.3.3.1coReplace Table 23 with the one described in Section 2.4 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.d 732-699-5305gIFigure 23 should be updated to be consistent with the revised basic set.i Figure 23 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`89a27b 7.4.14.3.1cd 732-699-5305Memberak cBchema, the extended schema is expected to be updated periodically, e.g., when a new link layer technology is introduced. The extended schema can be retrieved from the specified URL via the IEEE 802.21 information service using the schema query capability described in Section 8.5.3 without any reprovision of such extended schema. The URL of the extended schema can also be obtained via the schema URL query capability described in section 8.5.3. Alternatively DHCP may be used for finding out Cthe URL of extended schema. The extended schema is defined as an extension of the basic schema and includes data structure and relationship of media-specific or higher-layer information. In that sense extended schema is the complement of basic schema. An extended schema may be automatically generated from various of media-specific or higher-layer MIB definitions such as 802.11 MIB, 802.16 MIB and TCP/IP MIB-II. Figure 8-3 below shows an example graphical representation of the 802.21 MIIS;dhcApCqdocBtDuFvHwJxLyNzP{R|T}V~XZ\^`bddsggAg^dg_gAcAdgBbbAjAd^j@gEcACdcBdF @@ih cD basic schema in which 'Network' 'MII', 'MDI', 'PoA', 'NAS-Port-Type', 'Location', 'Operator', 'Cost' , 'Geo-Coordinate' and 'Enterprise-Number' are represented as class, while all others are properties of classes. The lines indicate either the range or domain of a property or a sub class of a class. In particular 'r' represents the range of a property and 'd' represents domain of a property. 'Domain' defines the class that a particular property belongs to and 'range' defines a type of a Eparticular property. "Zwc802.21onlydefinesenablersformobilitymanagementprotoco_V802.3W87W88W89W9ֹW9.1W9.2W90Wa]W`WcWfWkWpW֠W֢W֤W֬W֭W֮WֵWּWWWWWWWWWWWWWWWWWWWWWWWcreprovisionWrequest֑W֩WWWWWWWWWWWWWrequestthatanewparametertocarryabasicinformationelVrequestthatanewparametertoindicatethetypeofparametVrequesttoreconsidertheusecasesformihnetworkinformatVrequesttoremovesection7.2.13and7.2.14andrespectiveeVrequesttoremovesection7.2.157.2.16and7.2.17andrespeVrequest/responseWWrequestsWrequestsourceWrequiredWWWWWreservedֺWWresideWresolutionWresoucestatusresourceSWWresourcestatusWrespectiveWWWresponse֥W֦W֧WWWWWWresponsesourceWWyWrestrictionWresultֺWWWWWresultbitmapindicatestheresultoflinksetupprocessVresultsWretrievedWrevisedWrfcWricherWrightWHcoutsW։WWoverֵWWoverallSWWoverlappingWowlWWpacketsցWpageWWWWWWWWWpanaWparagraphsWqtd 732-699-5305g`The schema-based query example should be updated to be consistent with the revised basic schema. 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`116a10b Annex C.1cAReplace text starting at line 10 of page 116 and ending at line 44 of page 112 with: " ]> SELECT ?poa-id WHERE { ?x1 mihbase:neighboring-poa ?x2 . ?x2 mihbase:poa-type 19 . ?x2 mihbase:poa-id ?poa-id . ?x1 mihbase:poa ?x3 . ?po cCx3 mihbase:poa-type 19 . ?x3 mihbase:poa-id "001122334455" . } MIH_REPORT: aabbccddeeff 001122334455 0123456789ab "o/a3cfgijk30ֱ313234ֺ3638Ѓ394041־̃42ֽ44ă45ַ46474849֮ȃ5.1l5.1.3m5.1.5n5.1.6o5.2pq5.3r5.3.1s5.4tu5.4.1vwxyz{|5.4.3}~5.55.5.1ր5.5.2ցւ5.5.4ք5.6օֆֈ5.6.2։5.6.4֊5.6.6֋5.7.1֌֍֏535455ִ56ָ5758Ƀ596֭6.1.2֎6.1.3֐֑6.1.6֒֓֔6.2.4֕6.2.5.3֖6.3֬6.3.2֗6.3.3֘6062ֶ7.2֙7.2.7.1֛֚֜7.4.10.1.2֢֣֤֠7.4.11.1֥7.4.11.1.4֦7.4.11.2.1֧7.4.12.1.1֨d 732-699-5305g.The basic schema definition should be updated. 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`122a48b Annex C.2cRemove Annex C.2 entirely.d 732-699-5305gfThe Basic Schema Representation in ASN.1 is not useful unless a schema-based query is defined for it. 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`123a47b Annex C.3cRemove Annex C.3 entirely.d 732-699-5305gThe extended schema representation in RDF/XML can be automatically generated from various lower-layer and higher-layer MIB definitions, and does not need to be described in this document. 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`132a24b Annex C.4cRemove Annex C.4 entirely.d 732-699-5305gThe ASN.1 representation of extended schema is not needed as it is not tied with a schema-based query language and should be removed.Memberou cB="&owl;" xmlns:xsd="&xsd;"> Basic Schema for IEEE 802.21 Information Service This property contains a RADIUS NAS-PorCt-Type attribute value defined in http://www.iana.org/assignments/radius-types. This property contains an SMI Network Management Private Enterprise Code defined in http://www.iana.org/assignments/enterprise-numbers. 1 1 Network class has two properties, namely mii for media-independent information and mdi for media-dependent information. A distinct instancEe of this class must be assigned for each point of attachment. 0 Media-Dependent-Information class has properties that are specific to link layer or lower. The properties include data-rate. Any property can be added to this class in an extended schemGa. Data Rate The data-rate property contains a maximum data rate of the link layer of the PoA in unit of Kbps. 1 0 0 0 1 0 1 0 1 0 1 0 2 PoA Neighboring Networks Neighboring PoAs Location of PoA Network Operator z| cP Roaming Partners Cost Basic Higher Layer Characteristics UAM PANA Basic Higher Layer Characteristics Diffserv 0 1 This class has properties that indicate a location of PoA. The properties include geo-coordinate. Any |~ cTproperty can be added to this class in an extended schema. 1 1 1 } cV 1 1 1 1 1 This class has properties that represent geographic coordinate. The format is based on the Location Configuration Information (LCI) defined in RFC 3825. 0 34 This property contains the latitude resolution. 0 3FFFFFFFF This property contains the integer part of latitude of the location. 0 34 This property contains the longitude resolution. 0 3FFFFFFFF This property contains the longitude of the location. 0 2 This property contains the altitude type. 0 30 This property contains the altitude resolution. 0 3FFFFFFF _ This property contains the altitude of the location. 1 2 This property contain c`s the datum type. 1 1 This class has properties that represent a PoA. The properties are poa-type and poa-id. This property contains a RADIUS NAS-Port-Type attribute value defined in http://www.iana.org/assignments/radius-types. This property contains a link-specific identifier of PoA. 0 1 1 This class has pros cdperties that represent an operator. The properties are operator-id and operator-name. This property contains the name of the operator. "Enacorg/2000/01/rdf-scheWorg/2001/sw/dataacceWorg/2001/xmlschemaWWorg/2001/xmlschema-iWorg/2002/07/owlWorg/assignments/enteWorg/assignments/radiWoriginatedWWoriginationWotherւWքW֑W֠W֢W֤WֵWּWWWWWWWothersWW:cschema-basedWschemalocationWscopeWWsdoWsection֘W֭W֮W֯WִWֵWֶWַWָWֺWWWWWWWWWWWWWWWWWWWWWWWWWsectionsּWWsecureoWsecurityWWsee֜W֝W֬W֭WWselectWWselectingWselectionmWnWsemanticsWsendingWWsenserWWsentWsentence֋WserveֵWservice֩W֮WֵW־WWWWWWWservicesWWsessionWset]W֬WWWsetsWWsetupֺWWshallWWWcaugmentedWauthenticatedWauthenticatesWauthenticationֺWWautomaticallyWavailableֵWWWbWbaseWbasedmWWWWWbasicWWWWWs 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.com_Technical, Non-binding`87a20b 7.4.14.1.2c- Remove text starting at line 20 of page 87 and ending at line 6 of page 88. - Move the contents of Sections 7.4.14.3, 7.4.14.3.1, 7.4.14.3.2, 7.4.14.3.3 to Section 7.4.14.1.2.d 732-699-5305gAll QueryFilterTypes and its usage defined in this section are not well-defined. Since we have another set of QueryFilterTypes for schema-based query in 7.4.14.3, why do we need all these QueryFilterTypes for schema-less query? 2005/09/17MemberE YoshihiroFOhbaGyohba@tari.toshiba.comd 732-699-5305 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no comments_Technical, Non-binding`60a31b7.2.13cWRequest to remove section 7.2.13 and 7.2.14 and respective entries in the event tables.d 972-894-4356MemberP802-21-D00-02.pdff@A gLink_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, will be redundant functionality in 802.21. 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no comments_ Editorial`34a55b6.1.6cAAdd another table for MIH events or list 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.d 972-894-4356gMemberMemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no comments_Technical, Non-binding`59a11b7.2.11.1cbRequest that a new parameter to carry a basic information element is added to the parameter table.d 972-894-4356gADuring the exercise of L2 requirements, it was realised that some link types are able to provide some basic information elements either in the broadcast or by specific query mechanism. This information is beyong a simple MIH-capability flag. When this information is obtained in the MAC layer at the link detect phase, the primitive Link_Event_Detect and MIH_Event_Detect must have means to support the information elements. 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no comments_Technical, Non-binding`59a41b7.2.12.1cfRequest that a new parameter to indicate the type of parameter that has changed is added to the table.d 972-894-4356Member gARequest 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. If it is assumed that Table-1 is also applicable to MIH events then it would be clear if it is explicitly state. 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 column in the tables to mark whiBmch of Link_Event_XXX and MIH_Event_XXX are local, remote or both. Also applies to discovery and registration.[iT1 2005/09/17N,subirְ֮֯vivekִֵֶַָֹֺֻּֽ־ֿwolfgangֱֲֳyoshihiroՃփ׃؃كڃۃ܃݃ރ߃dasְ֮֯groetingֱֲֳguptaִֵֶַָֹֺֻּֽ־ֿkimƒÃăŃƃǃȃɃʃ˃̃kohlee΃σЃу҃ӃohbaՃփ׃؃كڃۃ܃݃ރ߃sreemanthulaxiegThe parameters table must include the type e.g. bandwidth, QoS etc of the parameter that has changed in addition to just providing old and new values of the parameter. 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no comments_Technical, Non-binding`62a14b7.2.15c_Request to remove section 7.2.15, 7.2.16 and 7.2.17 and respective entries in the event tables.d 972-894-4356gALink_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). When a L2 handoff mechanism is present, the MAC protocol will already support equivalent signaling to indicate the status. In any case, the status of the handover are can be obtained directly from the other link events currently defined e.g. link_up, link_going_down and link_down. 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.comd 972-894-4356gA`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. ` 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no comments_Technical, Non-binding`38a46b6.2.5.1cA@We 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.@d 972-894-4356Memberx^Approve with no comments_Technical, Non-binding`71a57b7.4.8.1cAThere are 3 ways 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.gTables 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, we hare remote commands. iT2 T3 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no comments_Technical, Non-binding`76a1b7.4.10cnNeed explicit text defining the scenario (mobile generated or network generated) and the corresponding effect.d 972-894-4356gA'For remote MIH commands in Table-3 that are bi-directional, the correspongin "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  33 2005/09/17MemberESrinivasF SreemanthulaGSrinivas.Sreemanthula@nokia.com^Approve with no commentsd 972-894-4356Memberb6.3.1֮6.3.2Ճփ׃؃كڃ6.3.36.3.3.1܃݃77.1W7.17.2V7.2W7.2.117.2.11.17.2.12.17.2.13ƃ7.2.15W7.2.157.2.167.2.17V7.2.16W7.2.17W7.2.7.17.4.17.4.107.4.11.2.27.4.127.4.137.4.14.1.27.4.14.3.17.4.8.17.4.9.2.47.47.13.2.28.3˃8.3.1ֱ8.3.28.4802.16WaWactiveWWWWadoptthefollowingnewtextVadoptthefollowingtextVadoptthefollwingtextVVanWandWannexֽWWWWWannexc1Vannexc2Vannexc3Vannexc4VannexdֽVassociatedWatWattachedWattachmentWavailableWbeWbetweenWbyWcWWWWcanWcapabilitiesWcapableWcaseWcommunicationWcoversWcurrentWO<cunidirectionalWunitWunlikeWunsignedintWunsignedshortWupWupdatedWupon֮WWuppertWuWwWxW|WWWWWWWurisWurlWWWusageWuseqWvWւW֮WWWWusedցWւWքW։W֐W֜WWWWWWusefulWuser֬WWusersWusesWWusing]WzWֵWWWWusngWvalidWvalidateWvalueWWWWvalueoflinkW<cdirectionsWdirectlyWWWdiscover֮WWWWdiscoveredWdisjoint-nessWdistinctWdistributedWdnamic־WdopW֤WWWdoc֬W֭W֮W֯WWWWWdoctypeWdocumentnW֬W֮W֯WWdoesrWyW֚W֟WdomainֵWWWdon't֤WdownWdraft֋W֌WּWWduringWWdynamic־WeֵWWWWWW .^withWWWWWWA^_0@^`‚b@a3@r7.4.13@b6.3.1@actually@d@function@instance@replaces@with@ymanagementprotoco@lamodificationissuggestedtosection6byaddingnewprimi@Zabove@againreplacewithhlehigherlayerentity@alink@an@daugmented@be@called@cellular@Xcomment9.1needtoverifyifhandovercommitisnotoverlap@connectivity@controller@definition@deliver@ 33  33 33> [bAThe new Point of Attachment definition replaces current definition - Network Point of Attachment. It defines the point of attachment independently of the MIH capabilities of the link endpoint. The "with at least one mobile-node termination" is required by the sentence in the link definition that says: "each link is associated with a minimum of two endpoints". Since a link may have more than two endpoints, there can be more than one Mobile Node attached to the link that includes the poinBt of attachment. @A> 33  33 33>cApClarify Point of attachment in section 3. Required to further clarify the proposed communication reference modelp@A> 33  33 33>d1g2304iAndrea, Pererz, Qiaobingj jARPoint of Attachment -- Network-side endpoint of a link with at least one mobile-node termination. Serving Point of Attachment The point of attachment of the mobile node prior to a potential link-switch event. Target Point of Attachment The point of attachment of the mobile node that may result when a link-switch event takes place.R@A*  33 33* 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the follwing textc!Add a new definition to section 3d1g2305iAndrea, Pererz, QiaobingjAMIH Point of Attachment -- MIH-active point of attachment on a link that falls within 802.21 scope. Also defined as a network-side MIH link endpoint. @A*  33 33* 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the follwing textc!Add a new definition to section 3LbdֽWdefinesWdefinitionWWWdistinctionWdoesWeachWemphasizesWendpointWWendpointsWentityWexampleWexchangeWexchangesWfigureWfollowingWWWWWWWWWfollwingWWforWd1g2306iAndrea, Pererz, QiaobingjACNetwork Node -- Collection of physically collocated link endpoints.C@A*  33  33* 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bThe following new definition covers the case where the Mobile Node is capable of maintaining multiple links simultaneously active.cAhClarify Mobile Node in section 3. Required to further clarify the proposed communication reference modelh@A> 33  33 33>d1g2307iAndrea, Pererz, QiaobingjAMobile Node -- Network node that can change point of attachment for at least one of its links at any time. The mobile node can either be in close proximity of or coincide with the mobile terminal. @A*  33  33* 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, AjayIbwithWWWc0ֺWWWWW0successV001122334455W0123456789abW1ֺWWWWWWWWWWcaddanoptionalparameterqueryresourcelistintomihhandoveVaddanothertableformiheventsorlistmiheventsinthetVaddnewdefinitiontosection3VVVVVaddedWWWWadding֭WadditionalWadditionsWaddress֛W֣WּWWWaddsWadoptWWWWadoptremedy5inthecontributiondcn21-05-0359-00-0000Vadopttheremedy1and2inthecontributiondcn21-05-0359-Vadopttheremedy3inthecontributiondcn21-05-0359-00-000Vadopttheremedy4inthecontributiondcn21-05-0359-00-000VadvertisementּWWafteroWagaineWzW~W֤W֤W4d0]@^P_``paedc‚!f‚"g‚#i‚$j‚%k‚&l‚'m‚(n‚)o‚*p‚1q‚2r‚3s‚4t‚5u‚6v‚7w‚8x‚9y‚:z‚A{‚B|‚C}‚D~‚E‚Fր‚Gց‚Hւ‚Iք‚Jօ‚Qֆ‚Rֈ‚S։‚T֊‚U֋‚V֌‚W֍‚X֏‚Y֎‚Z֐‚a֑‚b֒‚c֓‚d֔‚e֕‚f֖‚g֗‚h֘‚i֙‚j֚‚q֛‚r֜‚s֞‚t֝‚u֟‚v֠‚w֢‚x֣‚y֤‚z֥‚֦‚֧‚֨‚֩‚֪‚֫‚֬‚֭ƊaH#(eִֵֶַָֹֺֻּֽ־ֿƊvvaerbactuallyWadoptWWWWWWWWWadoptthefollowingnewtextVadoptthefollowingtextVVVVVVadoptthefollwingtextVVanWandWannexֽWWWWWannexc1Vannexc2Vannexc3Vannexc4VannexdֽVassociatedWatWattachedWattachmentWavailableWbeWbetweenWbyWcWWWWcanWcapabilitiesWcapableWcaseWcommunicationWcontributionWcoversWcurrentW^Technical, Binding_6a3bAdopt the following textcAdd new definition to section 3d1g2308iAndrea, Pererz, QiaobingjAoMIH Mobile Node -- Mobile node with at least one MIH-active endpoint on a link that falls within 802.21 scope. o@A*  33 33* 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textcAdd new definition to section 3d1g2309iAndrea, Pererz, QiaobingjAqInfrastructure Node -- Network node that cannot perform any kind of automated link switch for any of its links. q@A*  33 33* 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textcAdd new definition to section 3d1g2310iAndrea, Pererz, QiaobingjAXMIH Infrastructure Node -- Infrastructure node that includes an MIH function instance. Xcnewsentencesincethemaydraftok֋VnorW֞W֣W֤WWWnodecW֮WWnoiseWnon-freeWnonnegativeintegerWnot]W^W`WcWdWeWfWqWrWvWyW{WւWքWօW֊W֎W֑W֖W֬WֵWWWWWWWWWnotaccurate^VnotaccurateagainwhatisthemobilitymanagementprotocoleVnotsosure֊Vnottrueicanusethe802.11interfacetotalktoanmihlovVnoteWWnsert֮Wnumber֮W֯WobjectpropertyWobtain֮WWWobtainedWWobtainingWobtainsWoccurֵWoccurenceswWxW j 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textcAdd new definition to section 3d1g2311iAndrea, Pererz, QiaobingjA[Node of Attachment -- Infrastructure node that includes at least one point of attachment. [@A*  33 33* 2005/09/17 2005/09/14EQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textcAdd new definition to section 3d1g2312iAndrea, Pererz, QiaobingjAgMIH Node of Attachment -- MIH infrastructure node that includes at least one MIH point of attachment. g@A*  33 33* 2005/09/17 2005/09/14E Pererz Feder^ Editorial_15a5.3.1b6Replace figure 2 with contribution 21-05-0370-00-0000csFigure 2 Correction Wireline connection (access network 4) is shown as connected directly into an operators networkd1ifigֹWֺWfig10ֺVfig9ֹVfigureֿWWWWfigure22Vfigure23Vfigure7ֿVfigure8VpererzWWWWWWWWWWWWqiaobingWWWWWWWWWWWWt1t2Wt2t3Vt3WtableWWWWtable4Vtable5Vtable6Vtable7Vj802.11zW802.21nWWWWWW Dj@A*  33 33*jnodesvWnormal֍WnotnWqWrWyWzWnotezWofSW]W^W_WaWcWeWmWnWqWsWvWzW֍W֖WWWWWWWWWon^WaWkWnW֛W֣WWWoneWWWWWonemihpointofattachmentVonesrWonlynWoperationnWWoperator֗Woperatorienetworkidentifierandoperatorinformationelem֗VoraWeWցW֌W֕WWWoriginalSW]W^W_WaWcWeWqWvWzWցW֌W֍W֕Woriginaltextasetofhandover-enablingfunctionswithinth_Voriginaltextanarchitecturethatenables]VoriginaltexthandoversignalingaspartofhandoverexecutiqVqVqVqV >jmihpointofattachmentmih-activepointofattachmentonaVmih-activeWWWWmih-activeentityacommunicationentityegalinkendpointVmnaWeWmobileSWaWqWzW֛WWWWmobilenodenetworknodethatcanchangepointofattachmentVmobile-nodeWmobility`WeW~Wmobility-management^W_Wmode֤WmodelօWmoredWmostmWnWmotorolarWname֗Wneed{W֛Wneedtoagreeonidentifiersmihidsmobileterminalids֛Vneeds֍Wg2313 2005/09/17 2005/09/14#EQiaobingFXieGqxie1@email.mot.com_Technical, Non-binding`32a55b5.3cAhPlease see the companion document 21-05-0365-00-0000-communication_model_text.doc for detailed proposal.h@A d 847-372-8481gAAt the last 802.21 face-to-face meeting, a proposal was made to add a top-level communication model to section 5 that would serve the purposes of showing the communication relationships among different MIHF entities. To further explore the idea, a 802.21 communications model Ad-hoc Meeting was held on July 19, 2005 at the meeting. There was general consensus from that ad hoc meeting that a communication model diagram and some text to explain the relationships would be very useful to enhancBe the architecture discussion in the spec. The present contribution is to propose such a communication model diagram and new text. q@A  2005/09/17dcandoWւWքWօW֗W֭W֮W֯WֱWֵWֻWּW־WWWWWWWWWWWWWWWWWWWWWWWWWWWWand/changesWanexֽWannex֮W֯WWWWanotherWanyWWWanywhere֑WapplicableֵWappliedWappropriateWarchitecture]WrWaredWօW֖W֮W־WWWWWWWWWWWarea֮Was`WfWgWiWoWrW֎W֠W֢W֤W֥W֦W֧WWWWWWWWWWWWWascendingWassignWassignedWWassociatedցWassociationcWoWatWWWWWWWattachWattached֬W֭WattachmentWWWWattachmentsWattributeW2breplacesWrequiredWsaysWsentenceWsimultaneouslyWsinceWtable-1ּtable-5־terminationWtextWWWWWWWWWthanWthatWWtheWWWWWWWWWWWWthefollowingnewdefinitioncoversthecasewherethemobilVthefollowingnewdefinitionemphasizesthedistinctionbetwVthenewpointofattachmentdefinitionreplacescurrentdefiVthereWtoWtwoWwhereWI, c21-05-0365-00-0000-cW22W22-43ֻW23WW27W3օW֯WֺWWWWWWWWWWWWWWWWWWWW37reservedV3.2֮W30W34W36W3825W39W3fffffffW3ffffffffW3gppֿWWW3gpp2WWW4WWWWWWW41W42W44WW45W46WW47W5WWWW?c5.3.2@,6.1.5primitivesforlinklayerevents@agementprotoco@lamodificationissuggestedtosection6byaddingnewprimi@Zabove@addanoptionalparameterqueryresourcelistintomihhandove@againreplacewithhlehigherlayerentity@alink@an@dand@augmented@be@called@cellular@Xcomment9.1needtoverifyifhandovercommitisnotoverlap@connectivity@controller@definition@deliver@d +65-6550-5481gURemote registration would be equally useful for the MICS and MIIS as well as the MIES 2005/09/17MemberEBenjamin ?cBle parameter that may contain implementation specific information and may be different across different queries. InformationRequestSet completely describes the query that is issued. Information primitives typically do receive a response defined as: InformationXX. response (ResponseSource, InformationResultSet) where, - ResponseSource: is used to identify the source entity where the response originated; - InformationResultSet: is an extensible parameter that may contain the result of tC:he request and may be different across different queries.  ^onlyWWW^onlyWWmcresponsibleyWrestrictionWresultֺWWWWWWresultbitmapindicatestheresultoflinksetupprocessVresultsWretrievedWrevisedWrfcWricherWrightW^noWWv^editorialnoWWWWWWWWWWWWWWWWY-crelatedWWWrelationsWrelationshipWrelationshipsֵWremedyWWWWremoteyW֖WWWremove־WֿWWWWWWWWWWWWWWremoveannexc2entirelyVremoveannexc3entirelyVremoveannexc4entirelyVremovefigure22Vremovemihmgmtsapfrom3gppreferencemodelֿVremovemihmgmtsapfrom3gpp2referencemodelVremovetable6Vremovetable7Vremovetextstartingatline20ofpage87andendingatlinVreorganisation֬WreorganizeWreorganizesapsinsection7basedonrevisedsapdefinitionVQcreplace@-replacesection5.5.3withsection5.5.3incontributionwit@reprovision@mresponsible@rlc@schema-based@should@:specifying@subsequent@Psynchronous@gthe@thelinkeventrequesthasnotbeendefinedanywhere@there@thisisonlytruefor11thedraftneedstobemoregeneric@thisreferenceisnotadaptedtoieee802ietfvocabularyis@tobetakenoutofthespecification@unidirectional@valueoflinkparameter@Oweneedtospecifythedifferencebetweenthetwo@whatdoeslayer2meanweneedtobedeeplyaccurateinthis@whywouldiwanttopropagateeventtotheremotel3mpwhat@within@4d0@Ɗ75@ifig@ja@also@completereworkingofthispart@cohbaWWWok֋Won]W`WmW֑WֵWWWWWWWWon-goingWoneօW֍WֵWWWWWWWoneofWonly_W`WyW֌W֑W֕W֤WֵWWonlyexistsfor11֕VonpropertyWontologiesWontologyWWopennessWoperationWoperationalaWoperator֗WWWWoperatorienetworkidentifierandoperatorinformationelem֗Voperator-idWoperator-nameWoperatorsWoptionalWWorlW֮WֵWּWWWWWWWWWWWWWorderWWorg/1999/02/22-rdf-sWnFKohGbenjamin.kohtm@sg.panasonic.com^Comments only; no voted +65-6550-5481 2005/09/17Member