Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0)@0inding@cthenormativereferencesectionisblank@@00allowedtheconcatenationoftheseparat@@0coincide@entity@inserttheworddownlinkbeforemodeaandotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijkQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJ>@ Cj%7.hal e-iJ.hj -Ek. l`l -mFxrogermarkspQmarksprogermarksBRmarksBrogermarksTmarksrogermarks@Umarks@roger marksmarksroger marks( i marks!(!roger  marks"0#q#marks$"0$ marks( i marks!(!roger  marks"0#q#marks$"0$DTDT €Editor's NotesEditor's Questions and Concerns€AEditor's Action Items€A€A€A Starting Line #€A Section€A  Fig/Table# BA1BAj  !"#$%&'()*+,-./0234567j^_ `2a4bc d ijkmn.p+v"wx#y'{)€%€0€€€€1€€66leiOwang' *  wang * leiP wang wang ' leiQ wang VYwang VleiRwangwang YleiSwang wang leiTwang@nh&`wanghleiUwang1.55€A1.55: Added "Fig/Table Number" field Deleted XML file output option. 1.54: Added "Technical, Satisfied (was Binding)" to value list Comment Type/Group. 1.53: in Reply Comment layout, reduced display to three replies 1.52: *Changed instruction on saving files to specify .USR instead of .fp5 *Fixed bug that wouldn't allow exporting a ballot with no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create andB Submit Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new K 9@AOKA/A0@@A-A.@A,A-Cancel@A*A+@@A* ;X( `Before importing, Find the records eligible for proposals by this Clause Editor. Only these records will be affected by the import. ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoQ:ASort by RecommenderE'` iDT_DT`DTDTDTQÃY0?ÃY@@ÃYPAÃY`BÃYpCÃYDÃYEÃYFÃZGÃZ HÃZ0IÃZ@JÃZPKÃZ`LÃZpMÃZNÃZOÃZPÃaQÃa RÃa0SÃa@TÃaPUÃa`ZBUUX  w  $,.YesNo/,  , : AM PMf  HelveticaGenevaVerdanaTimesMonacoTimes New RomanArialCourierSymbol Courier New Bookshelf Symbol 7 Marlett@ A PICT,Macintosh 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 \M1,,./: AM PMYyTtNnFfNALL OFMPRP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , AXLS Sheet1X5CMY m]oApFfWyHCMY m]oApFfWyHCB-wang., .lei]} A1FPTH=RPTH NAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9NFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9OFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A10FPTHXRPTHNAMEMSPCMSPCA2NAMEANumberLastFirst.USRRPTHANumberLastFirst.USRA19uFPTH^RPTHNAMEMSPCMSPCA2NAMEANumber_Lastname_FirstnameRPTHANumber_Lastname_Firstname ot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisVDEF(LISTLISTVDEF(LISTLIST(:K?@MRS Y!^"CAStartup scriptEQADelete Empty RecordsE@ @b*QA Show VotesE@@H-Already voted; submitting additional commentsQASort by Page/LineE'` _DT`DTDTDTQASort by Comment OriginatorE'` DTDT_DT`DTQADelete All RecordsE@ @b*QADelete Abstain CommentsE@ @HAbstain for other reasonsQAShow Editor's ProblemsE @'`@n* _DT`DTDTDTQASort by Comment #E '` dDTQ8 €Bied in recommending rejection on grounds of incompleteness or lack of a specific change request. (3) When you are finished entering replies, look under Scripts and choose "Find Marked Records". This will find the records for which you checked the "Marked" box. (4) Put your name in the "Recommendation by" field of each reply {for a quick method, see Appendix below.} (5) Under Scripts, choose "Export Clause Editor's Proposals". Choose the file type "FileMaker Pro Runtime Files". Enter a Cfile name of the form "BallotNumber_LastName_Firstname.USR", where "Name" is your name. (6) Email the exported file as an attachment to: --------------- Appendix: Using "Replace" in Commentary You can replace everything in a particular field over a batch of records. For example, clause editors might not want to type their name in the the "Recommendation by" field each time. Here is a solution to the problem illustrating the use of "Replace": *Finish entering your data. *Find the bacAEditor's LayoutB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMYesNo/,  , : AM PM Dp=u Av 2 72w27+-f3%:EAFAGA' Submitted by:€QASDocument under Review:UFirst (Given) NameVLast (Family) NameWBallot Group Membership Status:€XAY#Letter Ballot Number or Ballot Code€ZA[ email address€\A] telephone€^A_Vote:`(1) Create Comments€aAHCreate and Submit Working Group Ballot or IEEE Balloting Center CommentsH@AR  33& * Rg2*t {EQFAImport CommentsENALL OTABS# ` ABCDEFGdH^I_J`KaLbMcNOPQRgSiTjUkVmWnXpYvZw[x\y]{^_`abcde f g hijklmnoQGA Email fileE)?@ @A owner-stds-802-16@majordomo.ieee.org The comment file name should include the Letter Ballot Number and : ABCdD^EiFmGjHk ghijklmnotuvwxyz{|}~րցւփքօֆևֈ։֊֋֌֍֎֏֐ְֱֲֳִֵֶַָֹֺֻּֽ֑֖֛֢֣֤֥֦֧֪֚֭֮֒֓֔֕֗֘֙֜֝֞֟֠֡֨֩֫֬֯־ֿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃg^_`abcd€€€€€bcd€€€€€es€ 'f€aA Create and Submit Reply Comments @A*  33*€APLEASE FOLLOW THESE INSTRUCTIONS EXACTLY OR EXPECT TO HAVE YOUR INPUT IGNORED. (1) Read the comments. You will probably find this easiest if you use the "Comment List" layout. You can choose it from the upper left corner of this window, or you can use this push button: (2) When you want to respond to a comment, check the "Marked" box at the top of that record. Then fill out the following fields: Recommendation: Proposed Resolution: Reason for Recommendation: You are fully justifing the buttons:€gng the buttons:€gng the buttons:€gg the buttons:€gicking the buttons:€gicking the buttons:€gowing steps by clicking the buttons:€ging the buttons:€gg the buttons:€ging the buttons:€ge buttons:€gbmit Ballot Filef9Proceed with the following steps by clicking the buttons:€gO+ A#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# cBl#[  bl[##KK##;;# Bmv#+  @iv+# >j# Dkv# 8w5 €\]Page€^A_Line€`A aSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A &'()+ €A €A €A€ARecommendation@@ByProposed ResolutionReasonSee reply details€A Fig/Table# BNA^  !"#$%*,-./0123^^_`u EDE^ "Technical, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, BindingG OKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !""Technical, Binding" comments are permitted only with the vote "Disapprove". You may submit comments of type "Technical, Non-binding". Please correct and try again.H) W()=0 W ABCDEFGHIJK^L_M`NaObPcQlEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf7# w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM     w  $,.YesNo/,  , : AM PMw w  $,.YesNo/,  , : AM PMf"$  w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PMf w $,.YesNo/,  , : AM PMf3IC dd5BDe5Bf#= q w $,.YesNo/,  , : AM PM     w $,.YesNo/,  , : AM PM          w  3  $,.YesNo/,  , : AM PM   {cTZbo|h[++ \_l)]l+ ^`l$)g_.?nAEditor's QuestionB GpA Editor's NoteB GvAResolution of GroupB GH vwADecision of GroupB GxAReason for Group DecisionB GyA Group's NotesB G{AEditor's ActionsB G€AGroup's Action ItemsB G€AEditor's Action ItemsB G€AVoterFirstNameB G€A VoterLastNameB G€A VoterEmailB G€A VoterPhoneB G€A VoterStatusG€A VoterStatus3m  ^ 3 $,.YesNo/,  , : AM PM_   `3 a d3 e3 f  3 g  3 t  3 u   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PM#39 XX+ASubmit Reply CommentsB  a   w   w $,.YesNo/,  , : AM PMf w w Aa#8 F mM5ft GM5ftM5ftGOC`E 7OC`EOC`E7 W   W   W    ÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷{xBKA Enter commentEQMAImport Global DataENALL # @ A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcdefghijklmnopqQNAExport CommentsE:NALL OFMPR$@` ABCDEFGdH^I_J`KaLbMcNQkUmVnWpXvYwZx[y\{]^_`abcdefgh`DTDTDT A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcde0Abpleasereplacethecurrentsection7.4.1withthesectionfr@yreplacecommandsourcebysourceidentifierinallmihprimiti@_suggestmergingthelinksdutransmitsuccessandlinksdut@8varies@csuggestion@the802.21standardmayspecifythemeansforsecurityinfor@thebasicschemadefinitionneedstoberevised@v@gmatchtheprimitivenamesmihcapabilitydiscoveryrequestw@usethefigurein21-06-0482-00-0000@w@e@|two@unified@ispartwiththemeshmodeisputtingtheunified@guagesyntax@tclanguagesyntax@u@|tofitclanguagesyntax@nguagesyntax@eparameterrcvphyarenot@|tofitclanguagesyntax@phyarenot@|tofitclanguagesyntax@arenot@|tofitclanguagesyntax@onthislineshouldread@typosubscriptyinformulanyky@ geunnecessa@o@;u@QAAExport Full RecordsEOFMPR$@` ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^QCAAbout CommentaryEDQEAExport Vote & CommentsE6NALL OFMPRV D@]W@gFD@ @D@  ] W@ g F E@D@]W@gFFD@F$@`V0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsical, Bindinghh' Cw# ,v # 0x #  2y # s 2 @BBA0 0^_`ab c dijkmvwxy€€€             XXXX$XXXX2 X  X  X X& X'X(X)XXXXXXXX!X jv   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   h stanwood# >S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM(s%jAResolution ProposedB GkAReason ProposedB GmARecommendationB Gnndation 1B Gn1O RR 3  $,.YesNo/,  , : AM PMU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW w $,.YesNo/,  , : AM PMX w $,.YesNo/,  , : AM PM)e@B@2@It@ֱ@ֳ@P;;P;;P;;@y„-@q @z @P;;P;;P;bleisnotreferencedinthetextnorhasitanymeani@dthetermburstprofileisdefinedinthestandardasdefinit@toclarifydocument@d@B@2A@@@cJ@c@M @ @3P;@3P; @3P; @3P;7WNWWWYWbWdWeWhWWWWWWWWWWWWWW)W/W5W8W=W>WBWDW`WhWmWWWWWW?WgapWWWW WW#W$W%WgenerateWgenerated4W6WWWWgeneratingWgenericWgetOWWWgetridofdashthisisaproblemallthroughoutsection6.2OV4/ RM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMBkS-X bWmkwj,AvCgE@!Sl€`zrAPFQKRPSUTZUBN@VhA~@M@LZ<>C @@@FIH@JQ3^&vmBD€QdnaD@Xbm{ACEe@EJoQTYB@X|CE@€ JOTYAC@XbmwBD@a@EJOU[B@|J& JQ 3 $,.YesNo/,  , : AM PMS   U   V   W   X 3 $,.YesNo/,  , : AM PMY   Z 3 $,.YesNo/,  , : AM PM[   \ 3 $,.YesNo/,  , : AM PM]   ]   No/,  , : AM PM]   1 RG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMw+#,v# 0x#  2 Ma bc dijkmvwxy!€€$€2'&()% @@@B s@A 3  $,.YesNo/,  , : AM PM77777777 7 7  7  7  7 7 7777777777771xy{€€€€€j77777777 7 7  7  7  7 7 7777777777771        Y7 ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   6" i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv    €Dtch of records in which you want to replace a field. *In browse mode, and put the cursor in the "Recommendation by" field. *Under "Records", choose "Replace". *Choose "Replace with calculated result". *In the box, write, in quotation marks, your name. Click "OK". *Click "Replace". @Af  ww    ww  ww  wwfSet up an email message for meGo to "Comment List" layout BnA€ (gE Peretz Feder^ Editorial_2`28a1.2bAdopt the following new textc clarify b3d4g2223jAThe Media Independent Information service provides the information model and an information repository to make for query and response, enabling a more effective handover decisions @AR 33g  n  33Rv006/01/17006/01/09A ֟EVivekFGupta^Technical, Non-binding_41`4a6.2.4bAChange section 6.2.4 as folows: "Link Commands Link Command include the commands from MIH Function to lower layers (e.g. MIH Function to MAC, or MIH Function to PHY). These commands mainly control the behavior of lower layer entities. Link Commands are local only. Link Commands are issued by MIH Function to lower layers in the local stack. Whenever applicable the IEEE 802.21 specification shall use existing media specific link commands for interaction with specific access networks. New liBnk commands if required, shall be defined as recommendations to media specific technology standards. It is to be noted that although Link Commands originate from the MIH Function, these commands are executed on behalf of MIH-User"cA.Updtae section 6.2.4 Link Commands, Link Commands are local onlyd50g2392wAccepted{k) done 2006/02/02 2006-01-04֠EVivekFGupta^Technical, Non-binding_88`44a 7.4.12.1.2PI3Import Full RecordsExport Full Records Enter commentExport Vote & Comments Email file Startup script Delete Empty RecordsDelete Abstain CommentsDelete All Records Show VotesShow All Records in OrderSort by Comment #Sort by Page/LineSort by Comment OriginatorSort by RecommenderShow Editor's Problems Assign Editors#Mark Found Records%Unmark Found Records'Find Marked Records)Import Ballot Comments+Export Comments-Import Comments/ Export Clause Editor's Proposals1 Import Clause Editor's Proposals3Export Group Resolutions5Import Group Resolutions7Export Editor's Input9Import Editor's Input:Import Global Data< Help WebLink>WirelessMAN WebLink@Export IEEE XMLCOpen Reply Comment FileEAbout Commentary<AKEG  7   :UVWQNF89=>>9=>gP:@K79@<E Q@ Q*E@uD QFGB{K@(MNxS@W@ZC[E\G]I^K_M`OaQbScUeW  A} !LISTAqVDEFEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEfterW=WcWWWallWalleviatebWallocationbWalphaWalsoWWWalternativeWalternativesWalthoughWbWalwaysbWanWareadWasWWcWWatW(WOWattributesWbandWbandsdWbandwidth(WbaseWbeWWW(WbWcWWbelowbWcWWerL> `Z   [w \ ]  ^ w  $,.YesNo/,  , : AM PMew h 3  $,.YesNo/,  , : AM PMi   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   ,  , : AM PMd   $ ANU#OV#V+X^5)SY{cTZbo|h[ +' \_l) ]D+b ^`l$)C_B+``al)a,maTbc -6cI dd De ]f)aTgvhYi< A_.^ -^; Pbj0=bi.  _l -d @/Tcj4A6XZB% K%[%K% %\%0E>]^% 7%e%D€B G€ AEmail ToB G€ A Email SubjectB G€ AEmail ccB G€A BallotNumberB G€A DocNumberB G€ACommentary VersionB G€A ExportDateB AbG€A Comment DateB G€ACommentary Version NotesB G€ACommentary Version DateB G€AMarkB G€A XML OutputB  B  " 0000000 87654321 "& & &""&""& ""&b&"" F€A Comment Type€ASuggested Remedy€ A Starting Page Number€ACommentXCreate CommentZDocument[Create another Comment\Create/Submit Ballot]In WG Ballot, "Binding" comnents are those which form the basis of a "Disapprove" vote. IEEE Balloting Center processes all Technical comments identically.€^AeShow All Comments€hAiSection€jAk Fig/Table#€lAmStarting Line # B?A6 6^_`abc€` a b cdX)*+,-.X()*+,-.X,-.XXolutionARecommendation byCRecommendation:EReason for RecommendationHEditor's QuestionsKEditor's Action ItemsN Group's Notes @B=Ayperetz@^bindingtechnicalbindingjtechnicalnon-binding@_‚@\`‚W@a@8.4.1.1@@and@ib1performhandoverassuggested@v21-06-0492-00-0000-g@05.4.1.1@$7.2.1.2@8@add@;adopt@and@asdescribedearliertherdfschemadefinitionformiiscons@ been@rcapability@Mchange@commands@]data@description0aborthandover@Wdot21@2enables@equipment@ examples@expected@Kfunction@Sgeneral@handover@higher@ieee@#inareplacethe3remainingoccurencesofarchitecturewith@Zintermediate@:ipaddrconfstate@"is@it@jee@line@logical@miis@fmore@9needexplicittextdefiningthescenariomobilegeneratedor@3network@new@old@other@old@other@2.11@2@E BDM VOTEREMAILpDs`jA.nA%€B?€A€CC@C@=====6_BdD`@4AFF*KL)QaA0@./////./////qq@@jAqcA%jBDkBZq@<jUq@q@qcMq@qcjqHBq@l_qkCq@qbAjBqjAfkAgq@vqcqboq@Pq@Giq@qPqjA q@qbq@abAqcr@Or=^6r@GprB@jA|rE@N^HrHPqrR@rSbjrT@jSril1rt@'r@Irl4r@bAjB[kA\ 2002-04-15Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15  w  $,.YesNo/,  , : AM PM  w AaBSn DyRoxp zqr srtyuB+zy*{QbSzaq@Hg@@PB s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMXY!€aACommentary Version@A* ww  ww*}Commentary Version # Version NotesCommentary Version Date B A€€€888r ysrtyuB+zw*{EV|GIU}n~pI~YjR[7iaGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #fFJ I 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK w  $,.YesNo/,  , : AM PMA%x  Yx% ^%  _l%@ l`l@% j%0  al0% cl%  bl@GY^6i7w"#$A=CEw€\€a@5BG4M1R/YOAC+'@€BD8, consequtive in time, of a preamble and data subchannels. --------------------------------------------- 8.3.6.3.5.2.3 should be handed to a clause-editor to be entirely rewritten. ItC needs substantial additional information on how to do this type of rotation in TDD, and it shouldn't use the word frame for allocations. How it will fit under the MAC etc.. (i.e. it needs definition on how this shifted superframe structure fits in with TX/RX boundaries)cH3  @BBA^_`abc€XXXXXXXXACreate and Submit BallotB    E 3 $,.YesNo/,  , : AM PMF 3 $,.YesNo/,  , : AM PMG 3 $,.YesNo/,  , : AM PM'   ^AAssign EditorsE 5 4 3 2 1 0 / . -  ,  *  )  (  ' & % $ "    !Q7AShow All Records in OrderE '` dDTQ8A Export Clause Editor's ProposalsE OFMPR$@` ABCdD^EiFmGjHkQ9A Import Clause Editor's ProposalsE NALL OTABSW@# `BBXXXXYYYYZZYYZZp` "Guillemette" GuillemetteQAAssign Editor 11E@[@!r@a11.@a11.@!r@a11.@802.16.1/D1-2000Q`"11"^52_ 8.2.1.2.5n'tuWdownstreamuWexistuW6M<?ACreate CommentB    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM   X , : AM PM      ~LA+Commentary: The IEEE 802.16 Comment ManagerA*by Roger Marks *@A> ww ) ww> AICreate and Submit Working Group Ballot or IEEE Balloting Center CommentsI@AR  33& + RN#Version: <<ACIABB>> (<<ACIABG>>)OView Comment ListA5For help, see 5@A> ww 4 ww>Xhttp://WirelessMAN.org B A   €€A>  ww    ww>AGo To Create Vote Page@A> ww  ww>UV sBl#. .#  al# cl#  bl# Bmv#  @iv# sj{#v Dkvv# 8w#f,Cjvf# 0x# V  2y V# 2 # F 6{ F# In # 6 qp 6# LF 8w#/,v/# 0/ Y w $,.YesNo/,  , : AM PMZ w $,.YesNo/,  , : AM PM[ w  $,.YesNo/,  , : AM PMabcd€€€€€€€€€€€€rQ RA 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMPR RF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMx+!  2y! 4z! 6QS RK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3 $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMRT RP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMT 3 $,.YesNo/,  , : AM PMSU RU  w $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY 3 $,.YesNo/,  , : AM PMTN OZ 3  $,.YesNo/,  , : AM PM[  3  $,.YesNo/,  , : AM PMA#x x#  #; d;# ##+ #+# ## # ^ #k  _lk#  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€ ++++++++ + +  +  +  + + +++++++++++++X5XX/X1XXXX X3 X X  X  X6X XXX$X"X X&XXXX,XXXX)X+-*,6{7TypeReason k b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PM-dG | w  $,.YesNo/,  , : AM PM}  w ~ w  $,.YesNo/,  , : AM PM  w  w  $,.YesNo/,  , : AM PM  w A^a):|+=9}R~T=b=NR?+M^ance'd303 2001/08/28G6AReply Comment LayoutB U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]     [A, HH HH*<*G!!!!!!!!1111111111 11 11 11 9999 99999999BBBBBBBBJJJJJJJJJJJJRRRRRRRRRRZZZZZZZZZZZZ ZZ!cccc"cc#cc$cc%kkkk&kkkk'kk(kk)kk*kk+ssss,ssss-ss.ss/ssB0{{{{1{{{{2{{3{{456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmZ\ Cnopqr!!s11tBBuRRvccwssxyz{|}~D[] Ek0>nk&8n]n]n!=700UnUnUfa&fH!1fQ!H,bH,Hn\X8FU7=nXnH7%fQH 7k=8HnX10kHbHHgfn=\HX7X8HHf\]?no`_`_`_`_`_`_`_`_`_`_`_`_`_`B]n` [    `    `    `n&0n4WUfZ _ZZZ._ Z)$')d)$')d\^ G)')$h#`` ) )B)y}_ Z ' ' Dyy3sy~[_  )  ) B|uv7~qu|t_Z ( ( Brz}rs9|pr}up|_ ` ) ) Bzprypq~<yppy~pps`_ ' ' @rpp{upp|?vppuvpzZ[ ) ) Ezpt}rppyAsppr}~pr_ _ ' 'Bqp|ypvB~qpyxpz[ ` ) ) BHxpvups@|ptqpr_ Z # #@qp~}rpq~Iypq|ypz_ _E BEB`E BEBmE 'BEBmxpvyp|SX&&Xvpqpr` [  A Z Zqpy8=SHHspzZ _  @  `  `xpv,5^kn~qpr_ [[  _Z`l[  __Yo[ 6__[oqpqrpsbfS=X|pvzpy_ _ ' ) Bxpq}wpq}=]_ IXU7Uyp{zqppq`_ ) ' Bqppq}~p{=TW\fvpr}qppxZ [ ' ) DwppsspxfgT0spw}qpq`  _  '  'A~ppszpu08]n%7~qpp~}qpxZ _ BBEBm BBEBm 'BBEBmvpsppsHQH|ps}qq` [ `  ` _~psvq}Dyz~sx_ _  Z  Z [Jvu|{9to_Z_o__[Z__[^o__[Z__[^o_[^Z_`Z^o~v }~o_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`m`                                                                             @lBB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB^` K@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@B_ fXX]XfkJ78H7k=aXH 007U!,7kX8HXU7TT8X7TX77XXXf77`QHU8bk1TnaXfgWU77L7%7XX\ n17&7nbT] Xb!78=HUUXWUTX7 X7TY07=\7Xk Q%QX777b]1n=5n7H8Q!8nn_a M7!Qn=!H% 7TX,XfUXn,7,a bHb7jn &HU\TX$WT878gnn8H W8L7AUXHn8nH,H88N 7X&78=;XT%X7=7&0&0n, n!7HX00T(TXfnn777 H8& X7T7778n XTX778Tbkb H=X!`b O=T TXM*HU7T7&Q= 7Tn7%UW& XTX.7,n7&H%H8,X7gn7 TXT7A78nXH&=TXf7&Q7 PXTX 8n7]&]n7TX8jUQ TXU=n7\gn3n7XHUk=7,+U XTWUH87nn3X8WU77f78 TXUn= 7ac QU7U78&QQ XUX bfb7==nX17!8717W177&7nUT TWTH8fX&k8UUn7771 XUX77j&W7 WX bR8nH7 TXT\7&XUkH8U U77TX XTXn%88=&gC!\7 WX 77nXTUnfXTagWUTgWUTi)())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())(be S))())RZ                                                    B'S66SmB3BmK63BmVEBBPE.R8|o" *e VK S) i )}=}t<  K o  e   '~tFxy}qx ZV V)Pe2 6V R `vs|zWX!Q{ps}qq  <JR 3` )  A~psuTq}84n]H5}qpp}}qpx  ) _e Z ' o xpsppr5dngspw}qpqm  l <. Vqps~yptk]gX=upqzpy  I: . i J  B )3Sxppq}spwU7fU7xp{zpr V _  Z` l  ;   6qppq}}p{W=ef]{puzpz o  oZ  `2  "  `xpX $%       !ACommentary VersionB ( a w hh h h h h  h hhhhhhhhh!hh$XX,XXXX)X+X5X3c Uq}wpq}nf]1&}qpr 6  <`  ' _m N  */B 6qpqqpsH7Q78spz  lZZ ) `6   ' @_ xpuUQFupqpr V  `_  Z F  ) B qpxLxpr}zpz B ') Io  `P  " B xpwzqp{Q{puqpr BB' B e39 *@ qp~}spq}S}qppqyxpz@;)Bm e 'B  VzpvvpsQspps}qpsE '' R) Zi m   B; rp}zqppuUuppvvp|S  _6IN3_ )`EBmO '_ zpt}sppxQxpqz~ppt `R V)*NO @BYm  B 6rpp|vpp{P{ps}vp|6  ;  oB  E@` 3_zpszqq}L}qv|t oV NEBBZ m <rz}ssCtz~oI)"Ie6)6_cBB@@B@__@BlBB@l<)-V|vui [ w  $,.YesNo/,  , : AM PMA#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# c^_#  _l#  `l#m  av CgTgvh ivTjxivPk#TlPm&3Tn{&h3Po pDw6YTqp&3`Pr nTsj{tTuivcPvXTwmvPxTykvq~l6V~%AAbout CommentaryB\   A wB w I N w  $,.YesNo/,  , : AM PMO W  $,.YesNo/,  , : AM PMX $,.YesNo/,  , : AM PMPMPMPMPMPMPM   $,.YesNo/,  , : AM PM  w ` D .orgl>.;tf ZU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMk, w  3 $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz   {   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     rksa_2Wj m   n 3 $,.YesNo/,  , : AM PMo   p  w $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   '   B@\[)!r S // €TA€UA€VA€WA€XA YType€ZA[Suggested Remedy€\A ]Starting Page #€^A _Starting Line #€`AaSection€bAcComment€dAe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yA=AB=AB[Ab  !"#$%&'()*+,-./012345b& v   $,.YesNo/,  , : AM PMww   3 A0@*E0:@F {G0Z=' QkS%26U%92VLWiyl XU%92VLWiyl XXXXXX T BcAJ  !"#$J €€€ € €€ €      AGlobal Field SetupB   €€€ € €€ €           " # J  3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMs; VOTEREMAILVOTERFIRSTNAME VOTERLASTNAME VOTERMEMBERID VOTERPHONE VOTERSTATUS XML OUTPUT^abcgijkmnpvwxy{_`d    d  ^_`abcgimjkvwxy{p n!"#$%&'()*+ , - ./AMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line Number E !LISTAa) awaiting resolution b) awaiting missing input c) instructions unclear d) confer with resolution group e) editor disagrees f) pass off to other editor g) didn't have time h) defer to next round i) to do j) in progress - k) done l) none neededVDEFA((A!1>VDEF(LISTLISTAEditorial Technical, Non-binding Technical, Binding Technical (was Editorial) Editorial (was Technical) Technical, Satisfied (was Binding)VDEFA((A!VDEF(LISTLISTAMarkedVDEFA((A Comment TypeBMembership TypeCVoteDRecommendationFEditor's ActionsGComment Type/GroupHMarked`AFMRLFMRLAbb7AFMRLFMRLAdBFind DuplicatesC ReplyComments`lP <zReason for Recommendation{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes8Note: Group may also edit and export Comment Type above.€ADocument under Review:€ABallot Number:€A  Comment Date€A€A  Fig/Table# @BA5BAj  !"#$%&'()*+,-./0123467j^_ ` a bcdi"j k&m$n)pvwxy,{€€+€1€/€3€5€€6@@XB s@p.D/A First NameB GA Last NameB GAMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line NumberB GaASectionB GbAChangeB GcAReasonB GdAComment NumberB GM9999gACounterB GL2237iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. ,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl#.  .#  al# bl# 8w#,v#  2y# 2#v 6{v# In#f qC>pf# L WE@@MarkedQYAExport IEEE XMLEOTABS D[@!d$@`@A14[p 0 h[[ [[ /0 h[p / AQ^AOpen Reply Comment FileE ! FMPRQ'`QdDTQAzHHddE(HH(d'`zA'dE7*`'`+ dDTQ] w  $,.YesNo/,  , : AM PM  UU? €Ad?2     _` a ^@"7 c>gt;Z<lt;Z b>gt;Z<lt;Zd W2&&Zgt;>Zlt;<Z:GC€A VoterMemberIDB G€A ReportNumberB G€A FigTabNumberB G ajayrajkumar@lucent.com 1IEEE 802.21 Comment Resolution for P802-21-D00-02 vivek.g.gupta@intel.comP802.21D00.04 08/2006ballot@wirelessman.orgm.comlot@wirelessman.orgmAComment 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 DataIsgvAhjAivAk@ljAmjAojAtbBubv@wbBDcAxbAcAvAy@bACz@bACE{@bAC|@v}@bApcր@ցbBփbօbAvֆbBDևbAֈ@bAA ։bBCD֋c֌@֍bACEGIKM!cA֎cAh֏@bA5C'E(G)֐@ bA*C֑@+v֒@֓bA.C1E֔b֕@J֖@4c6֘cA֚@>vk֝dA֟@9֠b ֡v֢@֣@֤c֧c֨@֪@֬c֭@֯@[ְbAVcn 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  33fg! QEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf3,jpointiWpptWpresentationWprimitiveshWprocedureoWprotocolWprovidesgWprovidingiWquerygWrealiWrecommendedhWrelativeiWremoteWremoveWWWremovethewordfragmentVVVVrespectivehWresponsegWoWrouternWrplaceWrplaceexistingfiguewithfigureasshowninpresentation2VsapshWsentenceWservicegWservingnWservinvgmWshownWWshowsoWsourcelWspecifichWlWspecificationhWspeedsiWstandardhWstartmWstateWstationiWstatusmWsuccessfulmWsupportedcommandlistlWsupportedeventlistlWsupportedtransportlilWtargetmWtechnologyhWthegWhWiWkWlWmWoWthedefinitionofnewlinklayersapsandassociatedprimitihVthemediaindependentinformationserviceprovidestheinforgVthislWmWW*jnewhWmWnewprimitiveshWnodeiWnoemWnotelWnowmWofhWlWmWoldmWnWoldservingfaaddressoldservingaccessrouteraddressnVonoWoperationmWoriWoverlayiWpacketsmWpduWWpeerkWpoamWpoamWmWmWmWmWmWoriWoverlayiWpacketsmWpeerkWpoamWmWmWmWmWmWmWmWoamWmWmWplacejWjWjWjWjWmoWphysicallylWplacejWjWjWjWjW of the groupd3iLucent_Peretz FedermRejected 2005/09/14^ENaviniF Dave Maez^ Editorial_1`22b/E Pro 3.0 - 4.1F!&HPro 5.0 A ?G USENGLSH.MPR?GUSER.UPRbjagWlWaboutiWaccesshWiWnWaddWaddnetworkinformationVaddresslWnWaddresseslWadoptjWadoptcontribution21-06-0490-0000-sect533jVadvertiseoWalsooWamendmentshWangWoWWanmihfentityresidinginthenetworkmayalsoadvertiseitoVandgWhWiWlWapplicablehWareiWkWndgWhWiWlWapplicablehWareiWkWkWkWfinedkWdefinitionhWdueiWduringhWeachhWeffectivegWeithermWenablinggWendpointjWkWnWendpointslWeventjWfallskWnWfastiWforgWhWmWoWfunctionhWpWfunctioninstancepVhandovergWhandovershWiWhelphWifhWinmWincludespWqWrWindependentgWinformationgWhWinfrastructureoWpWqWrWinfrastructurenodenetworknodethatcannotperformanykinoVjthismessageisusedbymihfunctiontocommunicatethestatmVthismessagemaycontainsupportedtransportlisupportedeventlVtimeiWtimelyiWtogWhWiWkWlWmWoWWunicastlWupperWusedkWmWuserWwaylWwhereWWWwhetherlWwillhWwithWWwithinWwordWWxxWWWk21-06-0483-00-0000W21-06-0484-00-0000W21-mailingWWW3W802.21WWaWWWWWagreedWagreementWWWallWWanWWWandWWWWWWWappliesWareWWWWWWWWbeenWWWWbeginningWbetterWWbetweenWcallbackWcommandWWWcommanddestinationWWconsideringWcorrectlyWdealingWWWWdecisionWdelayWd@ ր0ց@ւPg`hpփ֌}‚!~‚"ք‚#‚$i‚%|‚&j‚'ֻ‚({‚)z‚*y‚1ֳ‚2‚3֣‚4‚5t‚6֤‚7ֵ‚8ִ‚9֥‚:֦‚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‚vv‚w‚x֮‚y֧‚z‚֎‚ֽ‚֕‚֨‚֩‚֭‚֯‚ֱ‚‚֒‚ֿ‚֍‚֏‚֪‚֖‚֫‚u‚֔‚֠‚֡‚w‚֋‚‚‚ֺ‚x‚ְ‚‚‚־Ã!kÃ! ֗Ã!0lÃ!@mÃ!PnÃ!`oÃ!pֲÃ!֬Ã!֊ dDT  333  33  33  33@<jashWWWassociatedhWbaseiWbehWbeenWWbehaviorhWbroadcastlWbroadcastingoWbutlWbyiWmWoWWcallbackWcanmWcapabilitykWlWoWcapablelWchangeWcollecthWcommandWWWcommandxxrequestcommandsourcecommanddestinationcommandiVcommandxxresponsecommandsourcecommanddestinationcommandVcommanddestinationWWcommandinfosetWWcommandsourceWWcommunicatemWconditionsiWcontainlWcontributionjWcontrolhWdatalWdecisionsgWdefinitionhWdeleteWdeletestatemachineVdeliveredlWdemandoWdiscoverkWoWdiscoveryoWdocWdocumentWdoesn'tlWdot21WWWqWrWindependentgWinformationgWhWiWinfrastructureoWpWqWrWinfrastructurenodenetworknodethatcannotperformanykinoVjislWmWWisgeneratedbyanupperlayerentitysuchasmihuserthatVitlWitslWoWknowlWknowslWlayerhWWWlinkhWiWlocalWlocationinfoWmachineWmacro-cellsiWmakegWmaylWoWmediagWlWmessagekWlWmWoWmicro-cellsiWmihhWkWlWmWoWWWWmihfunctionmessageareusedtodiscovermihfuncationcapakVmihinformationrequestinfoqueryfilterinfoqueryparametersVmihflWoWmobileiWmodelgWmoregWmovementiWneighboringiWneighborsoWnetworkoWWiWoringiWiWiWiWiWelgWmoregWmovementiWneighboringiWiWiWiWjW-nodejWjWjWanchangepointofattachmentmVmobile-nodejWjWjWjWangepointofattachmentmVmVmVmV\EHassanFYaghoobi^Technical, Non-binding_1`27ssanNcsectionjWoWtWuWxWyWzW{WW֋W֍W֎W֏W֐W֒W֘W֙W֚W֟W֦W֨W֩W֬WְWֳWֶWַWֺWin close proximity of or coincide with the mobile terminal.  2005/09/14links at any time. The mobile node can either be in close proximity of or coincide with the mobile terminal.  2005/09/14MTG. To Detailed System Profiles including MAC, PHY, RF and Power Class elements Must be based on 802.16-200B4 as corrected by Corrigendum and amended by 802.16e Derived from requirements developed by relevant Working Groups for Mobiltiy Usage Scenarios Should be based on a harmonized set of assumptions and simulation test beds developed within MTG. @AR  33  33  33  33Rc*Need to change the content of the section.d8iLucent_Peretz FedermAccepted 2005/09/14\EHassanFYaghoobic< csectionsection8hasseveralinconsistenciesnotallcommandsandeְVsection8.5.1.2oVsectionsvWsecurityWWseem֔Wseems֎WsegmentsWWselectքWselected֏WsendwWsentWsentenceքWseparate֬WseptemberֽWserviceWօW֢W֮WְWּWWservices֐WseveralְWshall֎WsholdָWֹWshouldvW{W|W}W~WօWֆW։W֍W֎WֱWֵWshowWshowsWsignalֳWsignalingxW֔Wsince֒W֜WֽWsingleWsomexW֔W֘W֙WֳWּWWsource֧Wsourceidentifier֨W֪WspecificxW֡WWspecified֎WֿWWspecify֘WֱWWstandardWWstate֑WWstatehowthedirectionscopeoftheeventsintheremoteus֑Vstateful֍Wstateless֍Wstates{Wstatic{W֍Wstation֐Wstatus֓W֡WWW֐W֑W֒W֓WW=ccommunicationjWcompleteֿWcompletely֠Wconfiguration֍WּWconfigure֮WֱWּWconfirmWconnection֎WconnectivityցWydescribeabouuVcurrently{Wd04tWdataxWdefinedxW|W}WdependentxWdescribeuWdescriptiontWdetailedtWdifference{WdiscoverwWdiscoveringwWdoestWuWdrafttWxWdynamic{WeitherxWelementstWentitiesxWequipment~WestablishedtWevents{WexchangewWxWexchanges{WexchangingwWfiguretWfigure4indraftd04doesnotmatchwellitscaptionandthtVforxWforeignwWformatxWfromWfunctiontWxWfunctionaltWgeneraltWhandoveruWwWhigher|WieeeuWifwWintWxW{WWinsection7replaceresponseprimitivesbyconfirmprimitivVincludestWindependentwWinformationwWxW{WinfrastructurejdueiWduringhWeachhWeditoriallWeffectivegWenablinggWentitieskWentitylWoWWentity'slWeventWWeventxxindicationeventsourceeventdestinationeventinfoseVeventdestinationWeventinfosetWeventsourceWexchangeWexchangefigure27withfigure3-3fromdocument21-06-0485-VViWfigueWfigureoWWWfiguresWfillslWfinalWflowWWfollowingoWforgWhWforwardingmWfragmentWWfromWfuncationkWfunctionhWkWmWgeneratedWhandovergWmWhandovershWiWhandoversduetothemobilestationnodefastmovementspeediVhasWWheaderWhelphWhencelWhigherWhigherlayerprotocoltcp/udpVifhWlWmWinkWlWoWWWindependentgWindicationWxrequestrequestsourcerequestdestinationinforVDTposi}WotherֽWotherwiseֲWoutֽWphy}WpictureֲWpresentedtWprimitives֖Wprovided}WprovidingiWreadֲWredrawnֲWrejectedWremoved֖Wremovedtransportlayerfromallprimitivesinsection-7֖VrequestWresidingoWresponseֽWWrevision֒WWterm}WterminalցWtheiW}W~WցWthese}WthistWWWthishasbeenpresentedanddeferredmultipletimesalreadytVthroughout~WtimelyiWtimestWtoiW~WWWue~Wumts}Wuses}WwellWv1֐W֡WWW1clarifysubnetrelatedies֐V1locationinfocouldbeusedasanoptionalparameterV1performinghandoverassuggested֡V16tW2xW։WWW2.2։W21-06-0401-03-0000։W21-06-0477-01-0000֒21-06-0482-00-0000֜W21-06-0485-01-0000W21-06-0494-00-0000ֵW27֥W3xWW33aֵWֺW.peretzgWhWiWjWkWlWmWnWoWperetzfedergVhViVjVkVlVmVnVoVqiaobing֐ֿronnyvWwWxWronnykimvVwVxVsoohong֍W֎W֏Wsoohongxiayou֍V֎V֏Vsrinivas֑֖֒֓֔֕֗֘֙ulisesֲWֳWִWֵWֶWַWָWֹWֺֻulisesolveraֲVֳVִVֵVֶVַVָVֹVvivekyW|W}W~Wְ֛֢֣֤֥֦֧֪֚֭֮֜֝֞֟֠֡֨֩֫֬֯wolfgangƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃxiayou֍W֎W֏WyoshihiroօWֆWևWֈW։W֊W֋W֌WyoshihiroohbaօVֆVևVֈV։V֊V֋V֌VWoWpWqWrWaddanewdefinitiontosection3rVaddnewdefinitiontosection3gVhViVkVlVnVoVpVqVattachmentjWclarifyjWmW;MbadoptgWhWiWkWlWmWnWoWadoptthefollowingnewtextgVhVadoptthefollowingtextiVlVmVnVoVadoptthefollwingtextkVadvantagesֆWafter{WWagainst֏Wagent֐WagnosticWaheadzWall}WօW։W֐W֓W֚W֧W֪W֫WְWWWWallowsֆWalsoyWzW}W~WֈW։WalternativelyֈWalthough֟WamendmentsִWֵWֶWַWָWֹWֺWֻWamongֆWanyWzWքWֆWևWֈW։W֏W֨WWcommandyWcommandsyWcommentaryuWconnectedyWcontexttWcontributiontWuWvWcontrolyWcurrenttWdataxWdcn-21-06-0481-00-00vWdecisionsyWdefinedxWdeliverwWxWdeliveredwWdestinationyWdeviceyWdirecttWdirectlyyWdiscoverwWdoctWuWdownwWdrafttWexWeitherxWemphasistWWPBbc1֍W֏W֘WW1eventscanbegeneratedfromcommandsneedsomeintroducto֘V1miheventmihlinkparameterchangehasbeenspecifiedtabV10ִWWW11WW13֛WּW15֜W16ֻW19ֻWW7.4.10.1/2֍W֏W7.4.10.2uW7.4.15֋W8xW8.3.2kW8.4.1.1lW8.4.4.5mW8.4.4.7nW8.5.1.2oW802.16gvW802.21֔WatW{WWւW֍W֎W֏Waaa֐WaboutuWacceptedvWaccesswWadd{W֐WaddresswW֍W֏W֐W֔WadvertisementwWafter{Wafterparagraph4weshouldaddaparagraphthatstatesthe{VagentwWagreejWagreedւWalltW֒Walready֔WalsoցWambiguity֑Wambiguous֒WamountօWanւWքW֏W֐WandtWvWxW{W֐W֓W֔WappropriateքWarchitectureւWareuWxWW֏W֑W֒Wifyb3gVclarifychVclearxWfrancinitgroetingƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃguptaְ֛֢֣֤֥֦֧֪֚֭֮֜֝֞֟֠֡֨֩֫֬֯jeeuliu֍W֎W֏Wpark֍W֎W֏Wparkliu֍V֎V֏Vperesse/guptayz{|}~րցւփքsreemanthula֑֖֒֓֔֕֗֘֙xie֐ֿmemberu֍֎֏֐ֿ^bindingiWjWlW֑WֲWֳWִWֵWֶWַWָWֹWֺWֻWWWWWWWWWWWWWWWWWWWWWWWWhWiWjWkWlWmWnWoWpWqWrWarWaddgWhWiWkWlWnWoWpWqWrWaddanewdefinitiontosection3rVaddnewdefinitiontosection3gVhViVkVlVnVoVpVqVattachmentjWclarifyjWmW ^bindingeditorialghkmno~րցւփք֢֪֭֮֫non-bindinguWvWwWxWyWzW{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ֿWWtechnicaliWjWlWuWvWwWxWyWzW{W|W}WWօWևWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֡W֣W֤W֥W֦W֧W֨W֩W֬W֯WְWֱWֲWֳWִWֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWWWWWWWWWWWWWWWWWWWWWWtechnicalbindingiVyjWmWbnewgWhWtWwWzWցWքWօWֈW֍W֏W֐W֓W֟W֠WּWֿWWnewtextօVֈVnewtexttoreplacethecurrenttextingeneralahandoverdքVnewlinkidentifier֠WnotW֏WnodeyWzW֓Wnon-hierarchicalֆWnotyWzWևW֍W֏W֓W֔WWnoteօWnoted֟Wnotification֓Wnpoa֏WnumberֳWִWֵWֶWַWָWֹWֻWoֆWobjectֆWobtainօWobtainedֈWoccurenceւWփWoccurencesւWփWoftWwWxWyWzW{W|W~WցWւWփWքWֆWևWֈW։W֊W֋W֍W֏W֓W֚W֟W֠W֨W֩W֯WְWWWWjWuWvWxWservicewWyWshallxWslightlytWspecificxWspecifieduWstackyWstackstWstatezWswitchyWtablewWtechnology-specifictWtemplatetWterminalwWyWterminal'swW mjAThis message is used by MIH Function to communicate the status of handover operation. If the handover operation is successful the servinvg PoA can now start forwarding packets to the target PoA. old PoA can noe start forwarding packets to new PoA. @Af  33        33fwAccepted{k) done 2006/02/02 2006/01/09nE Peretz Feder^ Editorial_111`19a8.4.4.7bAdopt the following textcClarify 8.4.4.7d104g2230jA;Old Serving FA Address / Old Serving Access Router Address ;@A      33    $  33:  33wAccepted{k) done 2006/02/02 2006/01/09 oE Peretz Feder^ Editorial_113`25a8.5.1.2bAdopt the following textcSection 8.5.1.2d105g2231iPeretzjo@Binding_6a3 tbBspecific figures put more emphasis on the MIH interfaces and less in the representation of portions of the respective protocol stacks that have no direct interaction with MIH.cAFigure 4 in draft D04 does not match well its caption and the title of the section that includes it ("General MIH Reference Model"). Instead of presenting a general description of the functional positioning of the MIH Function, it contains a detailed overview of all possible relationships that can be established between the MIH Function and other functional elements, inside and outside the same network node that includes it. d24g2236pMIHF(Network) <> MIHF(Terminal) [Modify the text ; Page 111, Line: 3] The 'MIH_Network_Address_Information.request' is delivered from one MIHF in the network to another MIHF in the network in order to discover mobile terminal's network address related information before handover. @A  33%  33T  j  33v    33%        \  )  P  b                      ; B[         Fc KxvAThere are two ways of tranporting MIH messages remotely. One is using data frame, either over layer 2 transport or layer 3 transport, management frames, and the other is access type specific features. When applicable, specific features are native to media specific group, e.g. IEEE802.11, IEEE802.16, 3GPP, or 3GPP2. The MIH Function messages defined in the MIH protocol shall be used when two MIH function entities exchage messages remotely using data plane. @A  ++++wRejected{l) none needed 2006/02/02 2009/01/06ted information. Od90g2214 2006/01/19 2009/01/06xE Ronny Kim^Technical, Non-binding_99`21a8.1b            ; B[         Fc----------------------------------- [Modify the t8֬cDelete Appendix B (Media Independent Neighbor Graph). Neighbor Graphs have already been added as IEs and this section is mostly redundant at tis point. Any other sub-sections from here can be included if requred in Section 6 as a separate contribution.d107g2406wRejected{l) none needed 2006/02/02 2006-01-04֭EVivekFGupta^ Editorial_74`20a7.4.6b9Change MIH_Poll to MIH_Get_Status in entire section 7.4.6c0MIH_Poll is a misleading, and inappropriate named75g2407wAccepted{k) done 2006/02/02 2006-01-04ce more flexibility. This has been discussed in several Telecons. 2006/01/19 2006/01/0727ity. This has been discussed in several Telecons. 2006/01/19 2006/01/0727 | | Network-> Network | ---------------------------------------------------------------------------------------------------------------------------------------------------------- [Modify the t NxcAMIH protocol message format is used for remote message exchange between MIH function entities remotely. Because of the nature of the MIH, there are two transport mechanism one is using control plane and the other is using data plane either L2 or L3. When control plane is used, message format is media dependent and primitives will provide information to the media specific MAC for MIH related signaling. When Data plane is used, messgae format defined in Section 8 will be used. Some clariB;fication is required for clear understanding in the draft. )d95g2215vnformation. Od2g2214 2006/01/10 2009/01/06xE Ronny Kim^Technical, Non-binding_99`21a8.1btbjeeuWjeonֱWjust־WknowyWknowledgeօWlwWl2zW։Wl2sduzWl3։WWlanguageֆW֌WlayerxWyWzW{W|W}WցW֏W֐W֓W֜W֟W֧W֨WWlayersyWzW|W}W~W֓W֚W֟Wleast֓WlesstW{Wlet'sּWlevel{W|W}WքWW}WloweryWzW}Wlowerlayerslayerslocatedatosilevel2andbelowthisge}VmaczW}WmadeցWmakeցWmanagementxWzWmaywWyWzW|W}W~WmechanismzWmediaxWmediumyWzWmessagewWmessagesxWyWzWmics{Wmies{WmihtWuWwWxWyWzW|W}W~WmihfwWmiis{WmobilewWyWzW|WցWmobility{WmodeltWmodelstWmodifiestWmodifywWmodifythetextpage90line49wVmoretW~WmostքWmswWnature{WnearzWneedzWWbhandoveruWwWzW{WքWօW֍W֏W֡WֿWhandoverszW֐W֓Whandoverstatus֡WhaszWֆWhavetWօW֓W֚WְWheaderְWWhelpցW֐Whence|WheterogeneousWhierarchicalֆWionzWidentifierzWidentifierszWieeeօWieee802.11xWieee802.16xWillustratetWimminentzWimportantօWimprovezWintWuWwWxWyWzW{WցWւWփWքWօWֆWinareplacethe3remainingoccurencesofarchitecturewithւVփVincludeyWzWincludes}WincludingzWindicatezWindicationzWindiferentlyցWinformzWinformationwWzW{WցWօWֆWinformedwWinfrastructureցWinitiatezWinitiateswWinsertwWinteractiontWinteractionstWinterestzWinterfacestWinvokedyWipzW|WistWwWxWyWzW{WցWօWֆWcinitiateuW֍W֏WinsertֺWinsidetWinsteadtWևWֈWinter-access֐Winterface֎Wintroductory֘W֙Wip~W֍W֎W֏Wipv4֍Wipv6֍WiswWxW{WքWևWֈW֌W֎W֏W֐W֒W֓W֖W֗W֛W֠W֤W֧W֪W֫W֬W֭WֲWֺWֿWWWWWWisgeneratedbyanupperlayerentitysuchasmihfunctiontVVitstW֍W֎W֏WֿWWknown֏Wl2xWWl3xWlacֵWlanguageֆW֌WlargeօWlastֽWlatency֐Wlatest։Wlayer֎W֏W֐W֧WֵW־Wlayers|W}WlevelքWlimitationsWlinesֻWlink֎W֏W֓W֚W֛W֜W֝W֞W֟W֠W֡W֤W֥W֦W֧W֮WֱWֵWּW־WֿWWlinkcommandsarelocalonly֞VlinkconfigurethresholdcommandhasvaluesofthresholdwheֱVlinkeventsarelocalonly֚V ybAThe command service is a facility that enables the control of physical, medium access and logical link layers (also know as "lower layers"). 5.4.2.1 Command origination Commands can be invoked from upper layers (MIH Commands) as well as from the MIH Function (Link Commands). 5.4.2.2 Command destination The destination of a command may be the MIH Function or any lower layer. The recipient of a command can be located within the stack that originated the command, or within a remote stack. B 5.4.2.3 Command flow In case of local commands, messages typically propagate from the upper layers (policy engine) to the MIH Function and then from MIH Function to lower layers. In case of remote commands, messages may propagate from upper layers via MIH Function in one stack to the MIH Function in a peer stack (with the use of the MIH Protocol). Commands may then be further propagated to any lower layer. One of the stack may be present in a client or mobile terminal type of device whiQzE Mathieu/VivekF PERESSE/Gupta^Technical, Non-binding_21`18a5.4.1bntity can be a point of attachment or any node not directly connected to the other stack. 5.4.2.4 Command service use cases The commands generally carry the upper layer decisions to the lower layers on local device entity or at remote entity. For example the command service may be used by the policy engine of an entity in the network to request a terminal to switch between links (remote command to lower layers on termiD@nal stack). Comamnds defined include MIH_Switch, MIH_Poll, etc.  cReworking of section 5.4.2 d19g2356vgThe suggested organization is accepted. Make sure current content is not removed by the suggested text.wAccepted-Clarified 2006/01/29 2005-12-14zE Mathieu/VivekF PERESSE/Gupta^Technical, Non-binding_21`18a5.4.1bnds may then be further propagated to any lower layer. One of the stack may be present in a client or mobile terminal type of device whiS4bgeneraltWքWְWּWgenerallyyWgenerated֒W֓WgenerateswWgeneratingwWgeneric}Wgeo-coordinates։WgeographicalWgeospatial-location։Wget֭WgivenWgivesֆWgmmzWgoingwWzWgraphical։WgroupxWhanded֠WzcmobilitywWmodeljWtW֣WmodelsִWmoreֆW֛WmostքWmostly֬WmswW֍W֎Wms'swWmuch~WքWmultiple֐Wmust֒Wname֭W־WWּW־WnaturexW֛Wneed֓W֖W֘W֙W֠W֡W֧Wneedtoaddnewlinkidentifierasaparameterinmihhandover֠Vneeded֌Wneeds֊W֋W֕W֡Wnegotiation֕Wneighbor֬WnetworktWwWցWքW֒W֔WֲWnewjWwWփW֍W֏W֐W֠Wnewlinkidentifier֠Wnewly֏WnewprimitivesփWnewprimitivesnewprimitivesփVno֓W֖W֧W֮WnodetW~W֧WnormalizeֳWnottWuW{WօWևWֈW֎W֏W֒W֖W֛W֢W֧WְWֱWֳWּWnote{Wocal֜WoftWwWxWyWzWրWքWօWևWֈW։W֍W֏W֐W֑W֒W֓W֗W֡WֱWֲWֳWֵWֶWַWֺWWon֎W֑W zbE (L2 Handover Imminent), etc. Events may carry additional context data. For example a Link Up event may carry information including layer 2 & layer 3 identification, identifier of serving entities where these identifiers can be acquired. A link UP may also carry IP address renewal indication which can inform upper layers of the need to initiate a layer 3 handover . This can serve to improve the performance of layer 3 handovers.  icReworking of section 5.4.1d18g2357vgThe suggested organization is accepted. Make sure current content is not removed by the suggested text.wAccepted-Clarified{k) done 2006/02/02 2005-12-14 an event is established dynamically with a registration mechanism that enables an endpoint to register its interest in particular event types. 5.4.1.3 Event flow In case of local events, messages typically propagate from the lower layers (PHY, MAC, GMM...) to the MIH Function and from MIH Function to any upper layer. In case of remO{E Mathieu/VivekF PERESSE/Gupta^Technical, Non-binding_21`11a5.4bata. For example a Link Up event may carry information including layer 2 & layer 3 identification, identifier of serving entities where these identifiers can be acquired. A link UP may also carry IP address renewal indication which can inform upper layers of the need to initiate a layer 3 handover . This can serve to improve the performance of layer 3 handovers.  icReworking of section 5.4.1d18g2357vgThe suggested organization is accepted. Make sure current content is not removed by the suggested text.wAccepted-Clarified 2006/01/29 2005-12-14{E Mathieu/VivekF PERESSE/Gupta^Technical, Non-binding_21`11a5.4bat enables an endpoint to register its interest in particular event types. 5.4.1.3 Event flow In case of local events, messages typically propagate from the lower layers (PHY, MAC, GMM...) to the MIH Function and from MIH Function to any upper layer. In case of rem+z֑vEThe information in the column is redundent. Remove the entire column.wRejected{l) none needed 2006/02/02 2006/01/06 T2 and T3֒ESrinivasF Sreemanthula^Technical, Non-binding_82`1a7.4.10bNeed explicit text defining the scenario (mobile generated or network generated) and the corresponding effect. See remedy #2 in document 21-06-0477-00-0000-event-commands-updates.doccA(For remote MIH commands in Table-3 that are bi-directional, the corresponding "Effect of Receipt" section must reflect which scenario is considered e.g mobile generated or network generated. This is important since not all commands are supported by the terminal. The current text reads ambiguous.(@A  33d79g2224pDid not find revision 1.v21-06-0477-01-0000wAccepted-Modified{k) done 2006/02/02 2006/01/06s.d44g2236vEThe information in the column is redundent. Remove the entire column.wRejected 2006/01/18-- zbAEvents can indicate changes in state and transmission behaviour of the physical, medium access layers and logical link layers, or predict state changes of these layers. The Event Service can be used to indicate management actions or command status on part of network or some such management entity. 5.4.1.1 Event origination Events can originate from the MIH Function (MIH Events) or any lower layer (Link Events). 5.4.1.2 Event destination The destination of an event may be the MIH FunctioBn or any upper layer entity. The recipient of the event can be located within the stack that originated the event or within a remote stack . The destination of an event is established dynamically with a registration mechanism that enables an endpoint to register its interest in particular event types. 5.4.1.3 Event flow In case of local events, messages typically propagate from the lower layers (PHY, MAC, GMM...) to the MIH Function and from MIH Function to any upper layer. In case of rem2 benablesyWzW֍Wencompasses}WendpointzWengineyWքW֨Wentire֋W֭WְWentitiesxWzW֟WentityyWzW~WօWևW֓W֨WenumeratedֆWequalityֆWventszWeventscanindicatechangesinstateandtransmissionbehavizVexactlyֆWexampleyWzW}WֆWexamples|WexchagexWexperienceքWexpressionֆWexpressionsֆWextensibilityֆWextractօWfacilitate{WfacilityyWfiguretWfigurestWfirstւWփWfixedyWzWflexibleֆWflowyWzWfollowinggWhWiWlWmWnWoWxW{WֆWfollowsֆWfollwingkWfortWuWyWzW}WքWօWֆWframexWօWframeszWframeworkւWփWֆWfromwWyWzWօWfunctiontWwWxWyWzW|W}W~WօWfunctionszWfurtheryWzWfuturezWgxW~WֆW$b7.2.1.2vW7.2.1.3vW7.3֧W7.3.15֓W7.3.16֓W7.3.16.2֓W7.3.16.3֓W7.4֪W֫WֿWW7.4.1ֽW7.4.10ֿW7.4.10.1֍W7.4.10.2֍W7.4.11uW7.4.15֋W7.4.6֭W7.4.8.2.4WW։W֍W֓WְW8-3։W8.4xW8.5.3ֈW802֠W802.11tW}W~W֤W802.16tW}W~W802.2}W802.21}WօWֈW։W֍W֟W802.3tW}W~W9wWֆW֍W90wW91wW92wWatWyWzW{W~WւWփWքWօWֆWֈW։W֍W֏W֐W֓W֚W֨WְWּWֿWWaaa֐WabilityֆWableօWabort֡WaboutցWabove|WօWּWaccesstWyWzW}W~WևW֍W֏W֓W֟WaccessibilityֆWaccordingvWֲWֳWִWֵWֶWַWָWֹWֻWachievewWacquire֐WacquiredzWacquisitionwWacrossֆW֚WactionszW֓WW LbandtWvWxWyWzW{W|W}W~WցWօWֆWևWֈW։W֍W֐W֒W֓W֔W֚W֜W֣W֧WְWֺWּWWWannex֊WanotherwWanyyWzW~WֆWֈW֓WWapplicable֟Wapplication|W֨WappropriateքWօWְWarchitectureւWփWarexW|W}WֆW։W֓W֚W֟WְWareaWarq֓WastWuWyW{W|W}WցWւWփWֆWևWֈW։W֓W֟W֡W֨WְWֱWּWֿWWWWWևWֈWbeforewWօWbehaviourzWbelow}WbettertWbetweenyWzWֆWbothֆWbroadcastօWbuildsֆWbywWxWyWzW{W|W}WցWօWֆWcalledֆWcanyWzW|WցWօWֈWcapabilitiesֆWcapabilityֈWcarnalityֆWcarryyWzWcaseyWzWcasesyWzWceasezWceasingzWcellցW zbCote events, messages propagate from the MIH Function in one stack to the MIH Function in the peer stack. Events may then be further propagated to any upper layer. One of the stack may be present in a client or mobile terminal type of device while the other may be present in a fixed network entity. This network entity can be a point of attachment or any node not directly connected to the other stack. 5.4.1.4 Event service use cases and functions The event service will typically be used to Ddetect need for handovers. For example an indication that the link will cease to carry MAC SDUs at some point in the near future may be used by upper layers to prepare a new point of attachment ahead of the current point of attachment ceasing to carry frames. This has the potential to reduce the time taken to handover between attachment points. Events defined include Link Up, Link Down, Link Parameters Change, Link Going Down, and L2SDU Transmission Status, Link Event Rollback, Pre trigger {bAOriginal Text (in section 6.2.1): "The link status varies with time and terminal mobility. Information provided by MICS is dynamic information comprising of link parameters such as signal strength, link speed, etc, where as information provided by MIIS is less dynamic or static in nature and is comprised of parameters such as network operators, higher layer service information, etc. MICS and MIIS Information could be used in combination by the terminal/ network to facilitate the handover."B -> Add the following text after [paragraph 4]: The link status of a UE varies with time and terminal mobility. Information provided by MIES and MICS is dynamic information comprising of link parameters such as signal level, link speed, etc, whereas information provided by MIIS is less dynamic or static in nature and is comprised of parameters such as network operators, higher layer service information, etc. MIES, MICS and MIIS Information could be used in combination by the terminal/netw e{bCNork to facilitate the handover. -> Remove the Original Text in section 6.1.2*cA\[After paragraph 4], we should add a paragraph that states the difference between static and dynamic information in MIH exchanges. Note: The paragraph is currently located in section 6.2.1 [paragraph 2], but the dynamic information is only related to MICS (not MIES). MIES is used to carry Parameters Reports Events, which is dynamic information. \d17g2372vIThe IS and CS have not been introduced in the draft before this section. wRejected{l) none needed 2006/02/02 2005-12-14mobility. Information provided by MIES and MICS is dynamic information comprising of link parameters such as signal level, link speed, etc, whereas information provided by MIIS is less dynamic or static in nature and is comprised of parameters such as network operators, higher layer service information, etc. MIES, MICS and MIIS Information could be used in combination by the terminal/netwboldwW֏WontWwWyWzWֆW֓W֜W֟W֤WְWWonewWxWyWzW~WֆW֓W֚W֠WonlyւWփW֜W֟WְWontologiesֆWontologyֆW֌WopennessֆWoperator-identifier։Woperators{Wopoa֏WoptimumցWorxWyWzW{W}W~WցWօWֈW։W֍W֏W֒W֓W֚W֟W֠W֨W֩WWorderwWֆWֱWorg/tr/owl-ref֌Woriginal{WցWoriginaltextinsection6.2.1thelinkstatusvarieswitht{Voriginaltextthemobileterminaliswell-placedtodetectaցVoriginatezW֚W֟WoriginatedyWzWoriginationyWzWosi|W}WewWyWzWshallxWslightlytWsomezWspecificxWspecifieduWstackyWstackstWstatezWstatuszWsuchzWswitchyWtablewWtechnology-specifictWtemplatetWterminalwWyWterminal'swWxtbotherxWyWzWֆWֈWְWothersֆW։WoutֈWoutsideWoverxW֓W֠WoverallցWowlֆW֌Wpacket֓Wpackets֓WpagewW։Wparagraph{W։Wparameter֓W֖W֡WְWֱWWparameterszW{WְWֱWpartzWֈWparticularzW։WpartsևWpdu֓WpeeryWzW֓W֚W֩WperְWperformwW֡WperformancezWperiodicallyֈWphyzW}W֟WphysicalyWzWplacestWplease֣WּWֽWpleaseinserttextandfigurefromsection5.5indocument2֣VW֍W֏W֜Wpoa-location։WpointyWzW~WpointszWpolicyyWօW֨WpollyW֭Wpolling֯Wpollresponseset֯WportionstWpotentialzWprezWֈWpre-provisionedևWpredicateֆWpredictzWpreferredְWprefix֏Wpremitives֏WprepareuWzW֍Wpresence֍WzWterminal'swWxwbpresentyWzWpresentationWWprevious֏WprimitiveuWwWօWprimitives֋W֓W֧W֪W֫WְWpriorwW֍WprocedurewWpropagateyWzWpropagatedyWzW֚WpropertiesֆW։Wproperty։Wproposal֍Wproposal1֍VproposesuW֏WprotocoltWyW֨WprovideWprovided{W|W}WֆW֋WֳWִWֵWֶWַWָWֹWֻWprovidesWprovisionֈWpush-to-talk֍WputtWqosքWqueryֆWևWֈWquery/response֍WqueryingֆWrwW։W֝Wrange։W֍W֏W֠W֡W֨W֩W֯WrdfֆWևWrdf/xmlֆWreadyօWreceivingwWrecipientyWzWrecommendation֌Wrecommendations֟Wreconfiguration֏Wreconsider֔WreducezWreferּWrefered|W|W|W-specifictWtemplatetWterminalwWyWzW{Wterminal'swWterminal/network{W]WbdataxWzWօWֆWֈWdcnֳWִWֵWֶWַWָWֹWֻWdcn-21-06-0481-00-00vWdecisionքWdecisionsyWցWdefineֆWּWdefinedxWyWzWֆWֈW֐W֟WdefinesֆW։Wdefining֒WdefinitionֆWևWdelete֛W֞WּWWdeletefigure13remotelinkevents֛Vdeletefigure19remotelinkcommands֞VdeletestatemachineVdeliverwWxWdeliveredwW֓WֱWdependingWdeployedWderegisterּWdescribedևWֈWֺWdescribingֆWdescriptinְWdescriptionֆW֍W֏W֓W֠W֡W֨W֩W֯WְWְWְWifferent֏W֓W֚W֠WdirecttWdirection֝WdirectlyyWzWdiscoverwWdisjoint-nessֆWdispatched֚Wdistinguish֏WdistributedֆWdnsևWֈWdoctWuW։W֊W֋W֑W֒W֕W֗W֘W֙Wdocument֑W֒W֕W֗W֘W֙W֣W }bALower Layers: layers located at OSI Level 2 and below. This generic term encompasses all the access technologies supported by the 802.21 standard (802.3, 802.11, 802.16, 3GPP, 3GPP2). For example, for 802.11, Lower Layers are: the MAC Layer and the PHY layer. For 3GPP, Lower Layers are: MAC and UMTS layers. The term "Lower Layers" also includes Logical Link Control Layers such as 802.2 LLC or 3GPP RLC. The MIH Function may use the services provided by these layers. c*The term "Lower Layers" should be defined.d9g2377pALower Layers These are the layers located at OSI Level 2 and below across different media specific technology standards supported by the 802.21 specification. As an example, for 802.11 Lower Layers are the MAC Layer and the PHY layer and for 3GPP Lower Layers are the MAC and UMTS layers. The term "Lower Layers" also includes Logical Link Control Layers such as 802.2 LLC or 3GPP RLC. The MIH Function uses the services provided by these layers.XLbue{W~WօWumts}WunderlyingֆWunlikeֈWupzW֎Wupdate։W֤W֦WֲWֳWִWֵWֶWַWָWֹWֻWupdateaccordingtosubmitteddocument21-06-0494-00-0000-iִVֵVֶVַVָVֹVupdateaccordingtosubmitteddocument21-06-0495-00-0000-iֲVֳVupdatesection5.6.1from21-06-0361-02-00-000changes֦Vupdatethereferencemodelfor802.11basedonsection5.5.2֤VupdatedևWֈWְWupdatesְWupdtaedְWupperyWzW֏W֨WurisֆWurlևWֈWuseyWzW|W}W֓W֔W֟WusedtWxWyWzW{WօWևWֈWuser~WքW֨WWuserequipmentaterminalentitythatembedsoneormoresup~Vusers|W֚WusesֆWusingxWֆWֈWvalid֍W֏W֠W֡W֨W֩W֯Wvalidrange0-1֡Vvalidrangen/a֨V֩V֯VvaluesֱWֱWoutwWֈWwww֌WxmlֆW ցbBh as neighborhood cell lists, location of mobile devices, higher layer services available and thus help in optimum network selection. Decisions about connectivity can be made indiferently by the network or the mobile terminal.c?The network infrastructure can also make connectivity decision.d2g2384pOBoth the mobile terminal and the network can make decisions about connectivity.v5change the word "indiferently" to an appropriate wordwAccepted-Modified{k) done 2006/02/02 2005-12-14ւE Mathieu/VivekF PERESSE/Gupta^ Editorial_2`10a1.2bIn a), replace the 3 remaining occurences of "architecture" with "framework", as only the first occurence of "architecture" was replaced.czThe text in a) still refers to an architecture, whereas a decision to use the term "framework" has been previously agreed.d3g2385wAccepted{k) done 2006/02/02 2005-12-14փE Mathieu/VivekF PERESSE/Gupta^ Editorial_2`30a1.2/VivekF PERESSE/Gupta5breferencetW֌W֤W֧WregisterzWּWregister/deregisterּWregistrationzWrelatedwWrelationsֆWrelationshipֈWrelay֐WreliesWremainingւWփWremedies֓Wremedy֑W֒W֕W֗W֘W֙Wremedy1fromdocument21-06-0478-00-0000-cdoc֕Vremedy1fromdocument21-06-0479-00-0000-edoc֙Vremedy2fromdocument21-06-0478-00-0000-cdoc֗V~WցWservingzWshallxWsignal{Wsip|WslightlytWsomezWspecificxWspecifieduWspeed{WstackyWzW~WstackstWstandard}WstatezWstatic{WstatuszW{WstoreցWstrength{WsuchzW{W}WցWsupported}W~Wsupports~WswitchyWtablewWtakenzWtcp|Wtcp/ip~Wtechnologies}W~Wtechnology-specifictWtemplatetWterm}WterminalwWyWzW{W~WցWterminal'swWterminal/network{W ֡v: 1: Performing handover as suggestedwAccepted-Modified{k) done 2006/02/02 2006-01-04id Range: 0-1 Description: 0: Abort handover 1: Perform handover as suggested rk to which the connection needs to be handed overcNeed to add NewLinkIdentifier as a parameter in MIH_Handover_Commit.request... Only MacNewPoA is present, butto identify new link and PoA completely, also need the NewLinkIdentifierd88g2393wAccepted 2006/01/30 2006-01-04֡EVivekFGupta^Technical, Non-binding_89`40a 7.4.12.2.2bAdd following parameter: Name: HandoverStatus Type: BOOL Valid Range: 0-1 Description: 0: Abort handover 1: Perform handover as suggested andoverStatus Type: BOOL Valid Range: 0-1 Description: 0: Abort handover 1: Perform handover as suggested EcasuWW֐W֠W֤W֧W֨W֩W֬W֮WֳWֵWֻWּW־WֿWWat֎W֬WWattaching֍Wattachment֍WattemptֳWb֬Wb3gWbaoutWWbaselineֿWWsedtofollowthelatestlistof։VbetWvWxW|W}W~WWօWֆWևWֈW։W֊W֋W֍W֏W֐W֘W֙W֚W֡W֬WֱWֲWָWֹWbecausexWօWևWֈWbeeֵWbeenւW֬WְWֽWֿWbefore֏Wbelong֢WbetterևWֈWbetweentWxW{Wbi-directional֒Wbitmap֗Wbitmapencodingofevent/commandlistinthecapabilitydisc֗Vbroadcast-basedօWbroadcast-basedinformationserviceshouldnotbesupportedօVbut{WּWֽW־WֿWbutto֠WbywWW֏W֒W֣WֱWָWֹWchWvWcantWwWցWօW֍W֐W֘W֙W֚W֬Wcapability֕W֗WּWֽW?ctoo~WքWtowardֲWֵWtransmission֓Wtransmit֓WtransportxWWtransportlayer֖WtransportsWrstandingxWup֎WupdatedvWurlևWֈWuseւWևWֈW֎W֑WuseofdnsqueryforfindingthefqdnpartofthelocationoևVֈVusedwWxW{WֆW֐WusefulևWֈW֎Wuser~WWքWuserequipmentshouldbepreferedovermobilenodetoomuch~VusingxWwaywWwe{WwebֆW֌WwelltWwhat֑WwhenxW֍W֎W֐WwhereasւWwhetherwW֎Wwhich{W֍W֒WwillxWwithjWuWքWֆWwithoutօWd uvy֍֐֑0wz֎֒@x{֏֓P|֔`}֕p~րց‚!ւ‚"փ‚#քiandreahWandreapererzqiaobinghVpererzhWperetzijkloqiaobinghWj21-06-0490-0000-sectjW29oW3jW5jW\`‚Wk֐֣֦‚Y֔‚Zw‚bք֋֧‚cַ‚d֨‚e֩֯‚fօև‚g‚h֪‚iց‚q֖‚sֈ‚t‚vրցւփ1.62֌3|}~5.1.3ք5.1.65.1.8i5.3.2jֻ5.4{5.4.1z5.4.2y5.4.3Ã5.5t֣5.5.2֤5.5.4ֳ5.5.5ִֵ5.6֥5.6.1֦5.6.1.5ָ5.6.1.6ֹ5.8.2ֶ5.8.3ַ6.1.1֘֙6.1.2֛֚6.1.3֜6.1.4ƃ6.1.6֝6.1.7֑W֓6.1.7and6.1.8֑V6.1.8֑W6.2.2˃6.2.4֞֟6.2.6.2ּ֢6.3.2օ֐6.3.4.1ֆևֈ։77.2.1.2v7.3֧7.3.9.1֎7.4֪֨֩֫7.4.1ֽ֕7.4.10֖֒Wֿ7.4.107.4.117.4.137.4.14֖V7.4.10.1֍֏7.4.11u֖W7.4.12.1.2֠7.4.12.2.2֡7.4.13֖W7.4.14w֖֔W7.4.15֋7.4.15.3.4ֺ7.4.6֭7.4.6.2.2֯7.4.8.14ֱ7.4.8.2.48ְW8.1x8.3.2k־8.4.1֗~ conexWonly{W֚W֛W֜W֝W֞W֟W֠WֵWWonlymihtriggerslinkstatusupdateandhandovercontrolarVontologyֆW֌Woperation֎W֏WorwWxW֍W֎W֏W֒W֓W֚WWorderֶWַWֻWothertWxW֖W֬WoutwWoutsidetWWover~WoverviewtWowlֆW֌WowlwebontologylanguageshouldbeusedtogetherwithrdfsֆVp802.21/d00.04uWֱWpacket֓Wpackets֓Wpage֘WֻWֿWWparagraph{WparamWparameter֎W֖W֠W֧W֨W֩W֯WֱWֳWWparameters{W֑WְWֳWpartևWֈW֚WperֻWperform֎Wperformed֡WxWremotelyxWreplaceWreports{WrequestwWrequiredwWxWresponseuWwWWreworkingyWzWreworkingofsection5.4.1zVreworkingofsection5.4.2yVrouterwWsametWuWsapvWschemaֆW pljAThis message may contain SupportedTransportList, SupportedEventList and SupportedCommandList in the MIH message data. If a requesting MIHF entity doesnt know the MIHF capable entitys addresses, requesting MIHF entity fills its source addresses and may broadcast this message. If a requesting MIHF entity knows the address of entity but doesnt know whether the entity is MIHF capable, this message is delivered to the entity in a unicast way. Editorial note: Broadcast capability is media spB"ecific, hence it may broadcast. @A  33    33         33wAccepted{k) done 2006/02/02 2006/01/09mE Peretz Feder^ Editorial_110`30a8.4.4.5bAdopt the following textcClarify 8.4.4.5d103g2229j40a8.4.1.1bAdopt the following textcClarify 8.4.1.1103`40a8.4.1.1bAdopt the following textcClarify 8.4.1.13bnetworkwWyWzW{WցWքWօW։W֍W֏W֐W֒W֓W֔W֚W֜W֠WWWnetworkidentifier֠WnetworkstWցW֟W֠WWWWWWM]}bchangejWvWzW~WֆW֏W֓W֟W֭WWWchangemihpolltomihgetstatusinentiresection7.4.6֭VchangesectionjVchangesection6.2.4asfolows֟Vchangethesection7.2.1.2and7.2.1.3accordingtothecontvVchangedְWchangesuWzW֓W֣W֤W֦WְWֽWchannel-range։WcharacteristicsֆWcivic։Wcivic-location-infor։Wclass։WclassesֆW։WclientwWyWzWcoa֐WcollectionֆWcolumn֝WְWcomamndsyWcombination{WcommandyWzW֟WֱWּWcommanddestination֫WWconfiguration֍Wconfigured֏WconnectedyWzWconnection֠WconnectivityցWconsistingֆWconsistsևWcontacted֐WcontexttWzWcontributiontWuWvW֤WcontrolyW}W֟Wcorresponding֒W֓Wcould{W֐W֓Wcountry-address-elem։WcurrenttWzWքW֓Wd։WncinfrastructureցWTcconnotation~Wconsidered֒Wconsistent֖Wcontain־WcontainstWcontribution֬WֲWֳWֵWֺWֻWcontrolxWWconveyedֱWcorrectlyuWWcorresponding֒W֘WֵWּWֽW־WcouldֲWcoverages֐WcurrentuW֒WֱWּW־WWcurrentieeep802.21/d00.04doesnotcorrectlydescribeabouuVcurrentmihfunctionmessagesexactlyhavethesamenamesas־Vcurrently{W֧WֲWd04tWdataxWdecisionցWւWdefinedxW|W}W֔W֧WְWּWdefining֣WdefinitionֆW։W֊WֿWWdefinitions֓W֔W֖W֘Wdelete֢W֬Wdeleteappendixbmediaindependentneighborgraph֬Vdeletefirstthreeentriesfromtable-5thesecommandsdono֢VdependentxWdependingWdepictedWdeployedWderegisterּWdescribeuW֦WֺWeitherxWWformatxWfqdnևWֈWframeworkւWcture wbBthe mobile terminal initiates Network Address information acquisition procedure by generating this primitive. When the mobile terminal initiates handover which may be informed by Link_Going_Down remote event service, old PoA generates this message to achieve network address related information prior to handover. [Modify the text ; Page 91, Line: 13] MIHF(Terminal) <> MIHF(Network) <>MIHF(Network) [Modify the text ; Page 44, Line: 12; Table 4] --------------------------------------------C-------------------------------------------------------------------------------------------------------------- 9 | MIH Network Address Information | L, R | Client -> Network, | | | | Network-> Network | ---------------------------------------------------------------------------------------------------------------------------------------------------------- [Modify the tY`HcfromW֎W֘W֙W֢W֬W֮WֲWֵWֻWWfunctiontWxWֱWֵWּW־WWfunctionaltWfunctionality֔Wg֒WgeneraltWgenerated֒W֘W֙WWgeneric֣WgeographicalWgiveֆWgivenWgraph֬Wgraphs֬WgreatlyW֎W֏W֐Whow֑Whowever֎Wi֍Widentify֏W֠WieeeuWies֐WifwWimportant֒WintWxW{WWւWքW֍W֏W֐W֑W֒W֔W֖W֗W֘W֙W֛W֠W֡W֣W֤W֦W֨W֩Winsection7replaceresponseprimitivesbyconfirmprimitivVinclude֣Wincludeasub-sectionin5.5definingthegenericreference֣VincludestWincluding֋WindependentwW֣W֦W֬Windicate֎W֓Windication֎W֏Windicator֎Windividual֓Winflexible֗WinformationwWxW{WօW։W֎W֏W֐W֔Winfrastructure^bremotetWwWyWzW֚W֛W֜W֝W֞W֩WWremotelyxWremove{W֎W֓W֔W֖W֜W֝W֧W־WWWWWWWWremoveallreferencetoeventsourceandlinkeventsourcein֧VremoveallsegementsVVremoveiprenewalindicatorfromlinkupindication֎VremovemihfunctionwithmihuserVremoveprefixmihjustformihfunctionmessages־Vremoveremotedirectioncolumnfromtable-2removeremoter֝Vremovethetransportlayerparameterfromthelist֖VremovethewordfragmentVVremovethissentenceVVremovedְWrename֓WWrenamel3withhigherlayerVrenewalzW֎WreplacetWւWփWքW։W֊W֋W֓W֪W֫WְWֽWWreplacecommanddestinationbydestinationidentifieinallmi֫V֍W֏W֔W֨W֩Wrequesttoreconsidertheusecasesformihnetworkinformat֔Vwork{W bֆbD=ics of properties (e.g. symmetry), and enumerated classes. "@A> 33  33>cqOWL (Web Ontology Language) should be used together with RDF Schema to give more strict definition to the schema.d59g2214wAccepted{k) done 2006/02/02 2006/01/09ևEYoshihiro Ohba^Technical, Non-binding_49`55a6.3.4.1bAAs 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 DNS query may be used to access URL the location (FQDN) of the basic schema.@d with Web Ontology language (OWL) [OWL]. OWL is a Web Ontology language. OWL uses both URIs for naming and the description framework ablinewWxW։W֓Wlines։WlinkwWyWzW{W}W֎W֏W֓W֚W֛W֞W֟W֧WְWֱWּWֿWWlinkcommandincludethecommandsfrommihfunctiontolower֟Vlinkcommands֟Vlink-local֐Wlink-type։Wlink/mih֓WlinklayerֈWlinksyWlist֖WְWlistedօWlistsցWllc}WlocaltWyWzW֚W֜W֟W֩WְWWlocalandremoteeventslocaleventsarepropagatedacrossd֚Vlocal/remote֝WlocatedyWzW|W}WlocationցWևWֈW։WWWmethodsևWmics{Wmies{WmihtWuWwWxWyWzW|W}W~WօWևWmihfwWmiis{WևW։WmobilewWyWzW|WցWmobility{WmodeltWmodelstWmodifiestWmodifywWmodifythetextpage90line49wVmoretW~WֆWmostքWmswWnamingֆWnature{WnearzWneedzW ևbcUse of DNS query for finding the FQDN part of the location of the basic schema is not useful because FQDN does not tell the entire URL of the schema. Instead, use of DHCP might be better to tell the URL of the basic schema. d60g2215vAAs 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 expected to be 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 other methods such as DHCP DNS query may be enabled to be used to access URL the location (FQDN) of the basic schema.@A  33   33v {   33    33wAccepted-Modified{k) done 2006/02/02 2006/01/09ֈvstatemachine֯WstationiWsubnet֍W֐WsuchևWsuggestedyWzW֡WsupposedևWsureyWzWsystemּWtableֵWֺWtakeօWtaskօWtcp|Wtcp/udpWroperty belongs to and 'range' defines a type of a particular property. Figure 23 below shows an example graphical representation of the 802.21 MIIS basic schema in which 'PoA' ,'Subnet-Information', 'Address', 'Channel-Range', 'PoA-Location', 'Operator-Identifier', 'Geospatial-Location-ICnformation', 'Civic-Location-Information', 'Country-Address-Elements' , 'Country-Address-Element' are represented as classes, 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 particular property.@^U brequest/responseօWְWrequests֍W֯Wrequired֟Wreserved֍WresourceֆWrespectivetWresponseօW֍W֏W֩W֯WWretransmit֓WretrievedֈWreviseֆWrevisesection6.3.4.1asfollowsֆVricherֆWrlc}WrollbackzWrouter֏Wrow֓Wrows֐WrplaceWrplaceexistingfiguewithfigureasshowninpresentation2VsaְWsame֏Wsap֏WscalabilityֆWscenario֒WscenariosևWschemaֆWևWֈW։W֊Wschema-basedևWscopeWsdu֓WְWsduszWsectionjWuWvWxW{WֆWֈW։W֊W֋W֍W֓W֟W֣W֤W֦W֧W֪W֫W֭WְWֺWֽWֿWWsection-8ְWrvers֐WservicewWyWzW{WֈW֍Wservices|W}W~WցWservingzWsetֆWshallxW֟WshouldօWshow֜Wshowinteractiononlybetwenmihandmaclayeronlocalstac֜V ևbA 33a f  p 33    33e 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 DNS query may be used to access URL the location (FQDN) of the basic schema.@A 33a f  p 33    33cUse of DNS query for finding the FQDN part of the location of the basic schema is not useful because FQDN does not tell the entire URL of the schema. Instead, use of DHCP might be better to tell the URL of the basic schema. d60g2215vinding_49`55a6.3.4.1bses (e.g. disjoint-ness), carnality (e.g. "exactly one"), equality, richer typing of properties and characteristic ֈbA 33    33E I  ^ 33 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 pre- provision 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, oBcther methods such as DHCP a DNS query may be be enabled to be used for finding out the URL location (FQDN part) 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.Q@9ֈEYoshihiro Ohba^Technical, Non-binding_49`62a6.3.4.1b 33H7*bspecificxWօW֍W֓W֟WWspecificationօW֟WspecifieduWֈWֱWֿWWspecifies֠Wspeed{WstackyWzW~W֚W֜W֟WstackstWstandard}WWstandardsֆW֟Wstarting։WstatezWWstateful֍Wstateless֍Wstatic{W֍Wstation֏WstatuszW{W֓W֭W֯WstillְWstoreցWstored֓Wstrength{WstrictlyֆWstructureֆWֈWsub։Wsub-class։WsubjectֆWsubmittedֲWֳWִWֵWֶWַWָWֹWֻWsubnet֏Wsubnet-information։Wsubscribed֚Wsubsections֋Wsuccess֓Wsuccess/failureְWsuccessfully֓WsuchzW{W}WցWօWևWֈW֨WְWsuggest֓WֿWtechnologyֈWtechnology-specifictWtemplatetWterm}WterminalwWyWzW{W~WցW֐Wterminal'swWterminal/network{W=bitօW֏W֟WּWitszW~W֍W֏W#bhigher{W|W~WցW֐W֓WWhigherlayerslayerslocatedatosilevel3andabovethese|Vhigher-layerֈWhighlighttWhowWhttp֌WidentificationzWidentifierzW֏W֨W֩WidentifierszWidentifies֍WtWimminentzWimplementationևWimportantօWimprovezWintWuWwWxWyWzW{WցWւWփWքWօWֆWևWֈW։W֋Winareplacethe3remainingoccurencesofarchitecturewithւVփVincludeyWzWincludes}WֈWincludingzW֋WindicatezW։WindicationzWindiferentlyցWinformzWinformationwWzW{WցWօWֆWֈWinformedwWinfrastructureցWinitiatezW֍Winitiated֍WinitiateswWinsertwWinteractiontWinteractionstWinterestzWinterfacestWinternationalizationֆWinto֍WintroducedֈWinvokedyWipzW|W֍WWMbequipment~Wespecially֓WestablishedzWetcyWzW{WeventwWzW֏W֧WּWWWeventdestinationWeventszW֏W֚W֛WְWeventscanindicatechangesinstateandtransmissionbehavizVeventsource֧WexactlyֆWexampleyWzW}WֆW։WW։W։WtendedևWֈWextensibilityֆWextensionֈWextractօWfacilitate{WfacilityyWfiguretW։WfigurestWfindingֈWfirstւWփWfixedyWzWflexibleֆWflowyWzWfollowinggWhWiWlWmWnWoWxW{WֆWfollowsֆW։WfollwingkWfortWuWyWzW}WքWօWֆWևWֈWfqdnևWֈWframexWօWframeszWframeworkւWփWֆWfromwWyWzWօWֈWfunctiontWwWxWyWzW|W}W~WօWfunctionszWfurtheryWzWfuturezWgxW~WֆWֈWC ։bBties 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 particular property. Figure 23 below shows an example graphical representation of the 802.21 MIIS basic schema in which 'PoA' ,'Subnet-Information', 'Address', 'Channel-Range', 'PoA-Location', 'OperaCtor-Identifier', 'Geospatial-Location-Information', 'Civic-Location-Information', 'Country-Address-Elements' , 'Country-Address-Element' are represented as classes, 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 particu&cplanexWpoa֍W֏W֠W֡Wpoa'swWpoint֍W֬WWWWWpoint10and11saysallsegmentsVVpoint7andpoint8istalkingbaoutfragmentsVVpoll֭W֯Wpollresponseset֯WpositioningtWposswWpossibletWpossiblywWpppֵWpptWprefered~WpreferenceքWprefix־Wpremitives֍W֏WprepareuW֍Wprepared֍Wpresent֠WpresentingtWpreviouslyւWprimitiveuWֶWַWWprimitivesuWxWWփW֓W֔W֨W֩WְWֶWַWֺWּWֽW־WpriorwW֍WprocessWproposal֍W֎W֐WproposeֵWWproposed֏West/response֍WrequiredwWxWresponseuWwWWrevised։W֊W֋WreworkingyWzWreworkingofsection5.4.1zVreworkingofsection5.4.2yVrouterwWsametWuWsapvW֍WschemaֆWևWֈW։W֊W9֠bAdd: Name: NewLinkIdentifier Type: NetworkIdentifier. Can be one of different 802 or cellular networks Valid Range: N/A Description: This specifies the new network to which the connection needs to be handed overcNeed to add NewLinkIdentifier as a parameter in MIH_Handover_Commit.request... Only MacNewPoA is present, butto identify new link and PoA completely, also need the NewLinkIdentifierd88g2393wAccepted{k) done 2006/02/02 2006-01-04֡EVivekFGupta^Technical, Non-binding_89`40a 7.4.12.2.2bAdd following parameter: Name: HandoverStatus Type: BOOL Valid Range: 0-1 Description: 0: Abort handover 1: Perform handover as suggested cMIH Handover Commit.request, requests handover to be performed to a specific link and PoA. Handover Commit.response needs to return the status of this commit request. Need to add return HandoverStatus in MIH_Handover_Commit.responsed89g2394icular property.@rbasdescribedearliertherdfschemadefinitionformiisconsևVassignּWatxWyWzW|W}W~W։W֓W֚WattachօWattaching֍WattachmentyWzW~WaugmentedֆWauthenticatedօWavailableցWbased֤WְWbasicևWֈW։W֊WbewWxWyWzW{W|WցWօWֆWևWֈW֍W֐W֚W֟W֠W֨WֱWֳWִWֵWֶWַWָWֹWֻWֻWֻWwWօW֏Wbehalf֟Wbehavior֟WbehaviourzWbelonging֓Wbelongs։Wbelow}W։WbettertWbetweenyWzWֆWbetwen֜Wbit֍Wbool֡Wboolean֓WbothֆW֍WbroadcastօWbuffer֓Wbuffers֓WbuildsֆWbywWxWyWzW{W|W}WցWօWֆW֍W֏W֐W֟W֪W֫WֲWֳWִWֵWֶWַWָWֹWc֊WcalledֆWcanyWzW|WցWօWֈW֏W֐W֚W֠Wx֌EYoshihiro Ohba^Technical, Non-binding_5a2bwAdd the following reference: W3C Recommendation, "OWL Web Ontology Language Reference", http://www.w3.org/TR/owl-ref/.c3Reference to OWL (Web Ontology Language) is needed.d8g2221{k) done 2006/02/02 2006/01/09֍ESoohong, XiayouF Park, LiuGMember^Technical, Non-binding_82`8a7.4.10.1bg_5a2bwAdd the following reference: W3C Recommendation, "OWL Web Ontology Language Reference", http://www.w3.org/TR/owl-ref/.c3Reference to OWL (Web Ontology Language) is needed.d8g2221{k) done 2006/01/30 2006/01/09֍ESoohong, XiayouF Park, LiuGMember^Technical, Non-binding_82`8a7.4.10.1bcular property belongs to and 'range' defines a type of a particular property. Figure 23 below shows an example graphical representation of the 802.21 MIIS basic schema in which 'PoA' ,'Subnet-Information', 'Address', 'Channel-Range', 'PoA-Location', 'Operator-Identifier', 'Geospatial-Location-I{l) none needed 2006/02/02 2006/01/077E Wolfgang FGroeting^Technical, Binding_55`57a7.3.1.3b!Remove MIH Function with MIH UsercJ"...is generated by an upper layer entity such as MIH Function that is..."d69g2234jF"...is generated by an upper layer entity such as MIH User that is..."k!Upper layer entities are MIH Userv4 .... is generated by an MIH Function that is .... wAccepted-Modified{k) done 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_94`5a 7.4.15.1.2bAdd location infocI" ... MIH_Information.request (InfoQueryFilter,InfoQueryParameters) ..." d92g2235jKMIH_Information.request (InfoQueryFilter,InfoQueryParameters, LocationInfo)k\Make more efficient use of MIIS. See presentation "21-06-0484-00-0000_LocInfo_in_IS_req.ppt"v1) LocationInfo could be used as an Optional parameter. 2) It needs to be worked whether it would be a separate parameter or be placed within an existing parameter. Kbexamples|WexchagexWexchangeWexchangefigure27withfigure3-3fromdocument21-06-0485-Vexecuted֟Wexisting֟WWWexpanding֏WtensibilityֆWextensionֈWextractօWfacilitate{WfacilityyWfailure֓WfiguretW։W֛W֞WfigurestWfindingֈWfirstւWփWfixedyWzWflag֍WflexibleֆWflowyWzWflush֓WfollowinggWhWiWlWmWnWoWxW{WֆW֌W֐WfollowsֆW։W֓WfollwingkWfolows֟WfortWuWyWzW}WքWօWֆWևWֈW֍W֐W֔W֚WfqdnևWֈWframexWօWframeszWframeworkւWփWֆWfromwWyWzWօWֈW֎W֓W֕W֖W֗W֘W֙W֚W֝W֟WfunctiontWwWxWyWzW|W}W~WօW֚W֟WfunctionszWfurtheryWzWfuturezWgxW~WֆWֈW֍W֟Wf`blogicalyWzW}WloweryWzW}W֟Wlowerlayerslayerslocatedatosilevel2andbelowthisge}VmaczW}W֜W֟WmachineWmadeցWmainly֟WmaintainքWmakeցWmanagementxWzW֓Wmanual֍WmanyֆWmap֍Wmask֏WmaywWyWzW|W}W~WօWևWֈW֓W֨WmechanismzWmechanismsWmediaxWօW֍W֟WWmedia-specificֈWmediumyWzW֚Wmerging֓WmessagewW֍WmessagesxWyWzWְW־Wmethod֍WmethodsևWֈW֍Wmics{Wmies{W֏WmihtWuWwWxWyWzW|W}W~WօWևW֍W֏W֓W֔W֚W֜W֟W֨W֩W֪W֫W֭WְWֱWּW־WֿWWWmih-user֟WmihfwWְWWmobility{W֨WmodeltW֤WmodelstWmodifiestWmodifywW֓Wmodifythetextpage90line49wVmodule֓W"bistWwWxWyWzW{WցWօWֆWևWֈW֍W֏W֐W֓W֟W֨W֩W֯WWissued֟WctogetherֆWlGbthecommandserviceisafacilitythatenablesthecontroloyVthecontributionin21-06-0492-00-0000-gdocslightlymodifitVthetwofigure18and19donotshowthedifferencebetweenVthem֔WּWthentWyWzW֚WtherexW֓WthesezW|W}WօW֚W֟Wthey֚WthisuWwWyWzW}WֆW֍W֐W֓W֠W֨W֩W֯WWWWthiscommentaryproposestextchangesforthesection7.4.11uVthoseְWthresholdֱWּWthrough֚WthusցWtimezW{W~WtitledְWtotWvWwWxWyWzW{W|WցWքWօWֆWևWֈW։W֍W֏W֐W֓W֔W֚W֟W֠W֧W֭WְWֱWֲWֳWִWֵWֶWַWָWֹWֻWּWֿWWW֚WtriggerzWtriggeredwWtriggering֏WtriplesֆWtryքWtwoxWևWtypeyWzW։W֍W֏W֠W֡W֨W֩W֯Wwcto֊W֋W֌W֍W֎W֏W֐W֓W֔W֘W֠W֡W֢W֣W֮WֱWֲWֳWִWֵWֶWַWֻWWWWjLcthebasicschemadefinitionneedstoberevised֊Vtheentiresection7.4.15includingsubsectionsneedstobe֋VtheexistingannexaiscurrentlytbdcontributionentitledֲVtheexistingdraftdoesnotaddressmappingofqosparameterֳVthefigurebelowillustratesthedifferencesbetweenlocalaVthefiguredoesnotcorrectlyshowstheregistrationprocessVtheinformationmaybestoredwithinthemihfVthemappingof3gppand3gpp2primitivesisdescribeintablֺVthemih-3glink-saphasbeeagreedasthesapthatprovidesmֵVtherefore֏Wthese֐W֢WthiswW֎W֐W֑W֒W֔W֖W֘W֙W֡W֣W֧W֬Wthisproposalistoaddtwonewinformationelementsdhcpad֐Vthisproposalistoremovetheiprenewalindicatorparamete֎VthoseWֱWthree֢WthresholdֱWthresholds֮Wtis֬WtitletWtojWvWwWxW{WWւWքWֆWևWֈW։Wgcthebasicschemadefinitionneedstoberevised@thenetworkinfrastructurecanalsomakeconnectivitydecisi@jthereisnoneedfortransportlayerparameterinthesapthi@wto֊together@too@trigger@?url@Iwhere@{d‚bja@as@due@existing@infoqueryfilter@informationxxresponseresponsesourceresponsedestinationin@is@new@point@removethissentence@router@thismessageisusedbymihfunctiontocommunicatethestat@kbe@destination@evendestination@memory@process@storageofinformationisnotdonewithinthemihfunction@toenhancetheinterpretationofthemih-headerintointrod@papplicable@connectivity@Ldecisions@in@osi@revisited@Dspecific@there@word@drive@handover@handovers@itօmatch@ ֍bCe IP address configuration | | | method of new network to which handover | | | needs to be initiated. This is valid for | | | both IPv4 and IPv6. ---------D------------------------------------------------------------------------------------------------------------------------------------------------------ Add a new section into Section 7.4.10.2 (MIH_Handover_Initiate.response) -------------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | ! ֍bK---------------------------------------------------------------------------------------------- IMS Access (MSS, SMS, | Indication whether specific | N/A | 802.21 specific methods, e.g., a new Presence, Instant Message, | service is supported or not | | flag, query/response Push-to-Talk, ...) | | | -----------------------L-------------------------------------------------------------------------------------------------------------------------------------------- ..................................... | .............................. | ................ | ............................. ------------------------------------------------------------------------------------------------------------------------------------------------------------------- IP Address Co ֍bIPv6 stateful address configuration (DHCPv6) | | | 8: IPv6 manual configuration | | | 9: reserved --------------------------------------------------------------------------------------------------------------------------------------------------------------- [Proposal 2]J A new information in which enables a MS to prepare its IP address configuration method prior to attaching a new PoA (Table 6 of Section 6.3.2). ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Name of Information | Description | Media Type | Comments -------------------------------------------------------------------- ֍bG | | | both IPv4 and IPv6. | | | | | | 0 : IPv4 static configuration | | H | 1 : IPv4 dynamic configuration (DHCPv4) | | | 2 - 5 : reserved for IPv4 address configuration | | | 6 : IPv6 stateless address configuration | | | 7: I ֍bE Description -------------------------------------------------------------------------------------------------------------------------------------------------------------- ................. | .............. | ................. | ................ ------------------------------------------------------------------------------------------------------------------------------------------F-------------------- IPAddrConfState | BIT MAP | N/A | This identifies the IP address configuration | | | method of new network to which handover | | | needs to be initiated. This is valid for  ֍bA[Proposal 1] Add a new section into Section 7.4.10.1 (MIH_Handover_Initiate.request) --------------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | Description ---------------------------------------------------------------------------------------B------------------------------------------------------------------------ ................. | .............. | ................. | ................ --------------------------------------------------------------------------------------------------------------------------------------------------------------- IPAddrConfState | | N/A | This requests thh5Y֏ESoohong, XiayouF Park, LiuGMember^Technical, Non-binding_82`8a7.4.10.1bp.indication (Section 7.3.9.1) IP_Renewal_Indicator is to indicate whether a MS shall change IP when a layer 2 connection is established on the specified link interface. However, it seems not useful for the MS to use IP related information at layer 2 connection. To indicate IP change, the MS should perform its operation at layer 3 or higher layer not layer 2.d70g2321vHMake the "Flag" as well as Mobility Management Protocol field optional. wAccepted-Modified 2006/01/30 2006/01/09֏ESoohong, XiayouF Park, LiuGMember^Technical, Non-binding_82`8a7.4.10.1b | ................ --------------------------------------------------------------------------------------------------------------------------------------------------------------- IPAddrConfState | | N/A | This requests th!h  ֍cAIt proposes new mechanisms which enable a MS to prepare its IP address configuration method (i.e., static or dynamic of IPv4, stateless or stateful of IPv6) prior to attaching a new point of attachment. MS can recognize which IP messages should be prepared for its IP address when attaching a new PoA. [Proposal 1] A new MIH_SAP_Premitives in MIH_Handover_Initiate.request/response (Section 7.4.10.1/2) [Proposal 2] A new element in MIIS Elements (Table 6 of Section 6.3.2) d81g2315v 33  ) >c\Basic schema should be revised to follow the latest list of Information Elements definition.d62g2217pMarathon job in adding the IEsvMerge the bits specified for IETF with "other SDOs" in section 2.2 of 21-06-0401-03-0000. change "x octets" to "2 octets" in the first figure in 21-06-0401-03-0000wAccepted-Modified{k) done 2006/02/02 2006/01/09Fig 23n', 'OperaCtor-Identifier', 'Geospatial-Location-Information', 'Civic-Location-Information', 'Country-Address-Elements' , 'Country-Address-Element' are represented as classes, 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 particuxprevisitedWrlc}WscaledֲWsectionkWsection-7֖WseemskWservices}WsinceoWrds}WstateWstatemachineisnotapplicablefor802.21andthiscommentVsuch}Wsupported}Wtechnology}Wterm}WterminalցWtextֽWtheiWkW}W~WցWֽWthereֽWthese}WthistWWthishasbeenpresentedanddeferredmultipletimesalreadytVthroughout~WtimelyiWtimestWtitlekWtoiWkW~WWWtookֽWtransportֽWue~Wumts}Wuses}WwellkWWv1֐W֡WWW1clarifysubnetrelatedies֐V1locationinfocouldbeusedasanoptionalparameterV1performinghandoverassuggested֡V16tW2xW։WWW2.2։W21-06-0401-03-0000։W21-06-0477-01-0000֒21-06-0482-00-0000֜W21-06-0485-01-0000W21-06-0494-00-0000ֵW27֥W3xWW33aֵWֺWF Wcare֛W֜W֝W֞W֟WְWֱWּWWWWareaWQEcapplicable֛W֧WapprochֵWappropriateքWְWWappropriately֦WְWarchitecturalWarchitectureւWareuWxWW֏W֑W֒W֚W,2clinkeventsarelocalonlyinnaturefigure13isnotapplic֛Vlinksdutransmitsuccessandlinksdutransmitfailureprim֓Vlist։W֗Wlocal֚W֛W֝W֞W֟W֧WWlocated{WlocationևWֈWlonger֧Wlook־Wlower}WmvWmsapandcsapsectionsshouldbeupdatedtoreflecttheacvVmacxWmachineWmacnewpoa֠WmaintainքWmajoruWmakeցWmanagementwWmappingֳWֵWֶWַWֺWmatchtWmay֏W֔WWWmeansֳWWUbsideօWsignal{Wsingle֓WWsip|WslightlytWsms֍WsomezWsource֧Wsourceidentifier֪֨WsparqlֆWֆWֆW?{curlևWֈWuseւWևWֈW֎W֑W֣WֲWֳWֵWּWuseofdnsqueryforfindingthefqdnpartofthelocationoևVֈVusedwWxW{WֆW֐W֪W֫WusefulևWֈW֎Wuser~WWքWuserequipmentshouldbepreferedovermobilenodetoomuch~VusingxWusually־WvaluesֱWveryּWw֣Wwas֣WwaywWwe{W֧WֵW־WWwebֆW֌WwelltW֮Wwhat֑WwhenxW֍W֎W֐W־WherwW֎Wwhich{W֍W֒W֧WּW־WwillxWwithjWuWքWֆW֖W֥WֵWwithoutօWxxxֲWd uvy֍֐ֲ֑֚0wz֎ֳ֛֒@x{֏ִ֓֜P|ֵ֔֝`}ֶ֕֞p~ַ֖֟ָ֗֠րֹ֘֡ց֢֙‚!ւ֣‚"փ֤‚#ք֥‚$֦‚%֧‚&֨‚'֩‚(֪‚)֫‚*֬‚1֭‚2֮‚3֯‚4ְ6֕ESrinivasF Sreemanthula^Technical, Non-binding_72`30a7.4.1bKRemedy #1 from document 21-06-0478-00-0000-capability-discovery-updates.doccA֚vReword section 6.1.3, Local and Remote Events: Add text to clarify that a Link Event can go the MIHF and be sent to a remote entity as an MIH Event.wAccepted-Clarified{k) done 2006/02/02 2006-01-04֛EVivekFGupta^Technical, Non-binding_35`18a6.1.2b$Delete figure 13. Remote Link EventscKLink events are local only in nature. Figure 13 is not applicable any more.d37g2372wAccepted{k) done 2006/02/02 2005-12-1413֜EVivekFGupta^Technical, Non-binding_36`18a6.1.3b^Show interaction only betwen MIH and MAC layer on local stack only. Remove remote network PoA.c1Updtae figure 15, since link events are ocal onlyd38g2389v$Use the figure in 21-06-0482-00-0000w Withdrawn{l) none needed 2006/02/02 2006-01-0415֝EVivekFGupta^Technical, Non-binding_38`18a6.1.6bYRemove Remote direction column from Table-2. Remove Remote (R) from Local/Remote column c$.Table-2: Link events are local onlyXpbtranportingxWtransferօWtransmissionzW֓Wtransmit֓WְWtransmitted֓WtransportxW֨WְWWtransportlayer֖WtransportsWtraverse֚WtriggerzWtriggeredwWtriggering֏WtriplesֆWtryքWtwoxWևWWWtypeyWzW։W֍W֏W֠W֡W֨W֩W֯WYv3gppxW~W3gpp2xWֵW6.1.3֚W8.2.1W8.3.1WagW~W֏W֚WWWWWaboutiWaboveֵWacceptֵWWacceptonlythe3gpp2portionofthetable33aintheaboveֵVacceptsection8.2.1in21-06-0485-01-0000Vacceptsection8.3.1in21-06-0485-01-0000V | | In case of IPv4, subnet mask is included. | E | | in case of IPv6, network prefix is included. ----------------------------------------------------------------------------------------------------------------------------------------------------------- [2] It proposes a new link layer Events of MIES which can support a mobile station to distinguish whether or not its nPoA is a new subnet against oPoA MIH Events (Table 3) -----------------------------------------------------------------------`cinsection7replaceresponseprimitivesbyconfirmprimitivVinappropriate֭Winclude֣Wincludeasub-sectionin5.5definingthegenericreference֣Vincluded֬WincludestWincluding֋WִWinconsistenciesְWindependentwW֣W֦W֬Windicate֎W֓Windication֎W֏W־WWindicator֎Windividual֓Winflexible֗WinfoqueryfilterWinfoqueryparametersWinforequestsetWWinformֱWinformationwWxW{WօW։W֎W֏W֐W֔WֵWWWWWinformationxxWWinformationxxrequestrequestsourceinforequestsetwhereVinformationxxresponserequestsourceinforequestsetwhereVinfrastructureq 7ּbA1. Define a new service category "General" and assign it to "MIH Capability Discover" and "LInk Event Discover". 2. Assign "event" category to "MIH Event Register/Deregister" and "Link Event Register/Deregister". 3. Assign "command" category to "MIH Event Configure" and "Link Configure Threshold" 4. In Table 5-Link Commands, let's delete "Link Capability Discovery", "Link Event Register" and "Link Event Deregister" as we assign different service categories to them above. Please, refer to B0contribution 21-06-0487-00-0000-Service_CategorycGPP/3GPP2 Amendments.docd16g2223vBy the commentorw Withdrawn 2006/01/192ּE Eunah Kim^Technical, Non-binding_44`19a6.2.6.2bP2 Amendments.doc (DCN number to be provided by chairman)c8Remove SAP. This SAP shold be replaced by MIG-3GLINK-SAPg2221 2006/01/10 2005/11/06ֺ^Technical, Binding_98`34a 7.4.15.3.4Ncremoves֑Wrename֮Wrenewal֎WreplaceW֥WֵWreplacedָWֹWreportWreports{Wrepresented֤WrequestwW֔W֠W֡W־WWWWos ּcAThere are very close relationships among MIH Function Messages(Table 13), MIH_SAP Primitives(Table 8) and MIH_LINK_SAP Primitives(Table 7). Especially, MIH Capability Discover, MIH Event Register, MIH Event Deregister and MIH Link Event Configure messages have their corresponding MIH_SAP Primitives and MIH_LINK_SAP Primitives respectively. But there are some mismatches in their names and service categories among them. For example, they use Capability Discovery, Registration, Event ConfigurBMation as their service categories which are not defined in the current Draft.;d54vOModification change service category name from "General" to "System Management"wAccepted-Modified{k) done 2006/02/025ֽE Eunah Kim^Technical, Non-binding_72`30a7.4.1bsPlease replace the current section 7.4.1 with the section from contribution 21-06-0488-00-0000-Section7.4.1_changes Mfbbeen֓WְWbeforewWօW֏WֿWbehalf֟Wbehavior֟WbehaviourzWbeingWbelonging֓Wbelongs։Wbelow}W։WbettertWbetweenyWzWֆWWbetwen֜Wbit֍Wbool֡Wboolean֓WbothֆW֍WbroadcastօWbuffer֓Wbuffers֓WbuildsֆWbywWxWyWzW{W|W}WցWօWֆW֍W֏W֐W֟W֪W֫WֳWִWֵWֶWַWָWֹWֻWc֊WcallbackWcalledֆWcanyWzW|WցWօWֈW֏W֐W֚W֠WcapabilitiesֆWֆWֆWq>ֽcMIH Capability Discover messages have been changed since last September meeting, but their corresponding primitives haven't reflected that.d71pv In the response there is no need for transport options. Changed other text. Took out MIH Capability fromthe response.wAccepted{k) done 2006/02/02H Capability fromthe response.wAccepted{e) editor disagrees 2006/01/30ervice categories among them. For example, they use Capability Discovery, Registration, Event ConfigurBMation as their service categories which are not defined in the current Draft.;d54vOModification change service category name from "General" to "System Management"wAccepted-Modified 2006/01/305ֽE Eunah Kim^Technical, Non-binding_72`30a7.4.1bsPlease replace the current section 7.4.1 with the section from contribution 21-06-0488-00-0000-Section7.4.1_changes- ֿbASuggest to add a new section 7.4.x "MIH Link Handover Complete", as specified in 21-06-0465-00-0000-MIH_Link_Handover_Complete, before the current 7.4.10 "MIH Handover Initiate". @A*  33 33*cA"MIH_Link_Handover_Complete" has been specified as an MIH event (Table 3 on page 40 and Table 8 on page 54), but its detailed definition is still missing. This proposes the baseline text for the MIH_Link_Handover_Complete definition.@A  33d80g2220vThe comment needs to be looked at after the current categorization of Link Event, MIH Events, and MIH Commands is complete for possible duplication.wDeferred{l) none needed 2006/02/02 2006/01/09EQiaobingAXie@A  GMember^Technical, Non-binding_80`21a 7.4.8.2.4b*cGMember^Technical, Non-binding_82`1a7.4.10ba7.4.10b 2006/01/09avprimitiveWprimitives/messagesֲWprotocolxW֎WprovidetWWW the section from contribution 21-06-0488-00-0000-Section7.4.1_changescMIH Capability Discover messages have been changed since last September meeting, but their corresponding primitives haven't reflected that.d71 2006/01/18־^Technical, Non-binding_102`44atches in their names and service categories among them. For example, they use Capability Discovery, Registration, Event ConfigurBMation as their service categories which are not defined in the current Draft.;d54 2006/01/185ֽ^Technical, Non-binding_72`30a7.4.1bsPlease replace the current section 7.4.1 with the section from contribution 21-06-0488-00-0000-Section7.4.1_changescMIH Capability Discover messages have been changed since last September meeting, but their corresponding primitives haven't reflected that.d71 2006/01/18־^Technical, Non-binding_102`44i0b1performhandoverassuggested֡V1remedy1fromdocument21-06-0479-00-0000-edoc֘V10֓W11֓W11-13֓W111wW12wWW13wW֓W֛WְW18W19֞WW2xWzW}W։W֋W֍W֏W֒W֓W֗W֘WְWּW2assigneventcategorytomiheventregister/deregisterandּV2remedy2fromdocument21-06-0479-00-0000-edoc֘V21xW21-05-0468-00-0000-muW21-06-0361-02-00-000֣W֤W֦W21-06-0401-03-0000։W21-06-0425-01-0000-iֺW21-06-0460-00-0000-b։W֊W21-06-0461-00-0000-i֋W21-06-0465-00-0000-mֿW21-06-0466-00-0000-mW21-06-0473-00-0000-sְW21-06-0477-00-0000-e֑W֒W21-06-0478-00-0000-c֕W֗W21-06-0479-00-0000-e֘W֙W21-06-0482-00-0000WW21-06-0485-00-0000W21-06-0485-mih-protoְW21-06-0487-00-0000-sּW21-06-0488-00-0000-sֽW21-06-0491-00-0000-mֱWֽW21-06-0491-00-0000-mֱWֱWjcthereisnoneedfortransportlayerparameterinthesapthi֖VthereistoomuchsuggestioninthefollowingsentenceքVtherefore֏WtherforeֵWthese֐W֢WtheyּWthiswW֎W֐W֑W֒W֔W֖W֘W֙W֡W֣W֧W֬WֳWֶWַWָWֹWֿWWthisproposalistoaddtwonewinformationelementsdhcpad֐Vthisproposalistoremovetheiprenewalindicatorparamete֎VthoseWֱWthoughoutֳWthree֢WthresholdֱWthresholds֮WthusWtimeWtis֬WtitletWtojWvWwWxW{WWւWքWֆWևWֈW։Wbpleasereplacethecurrentsection7.4.1withthesectionfrֽVpoawW~WօW։W֍W֏W֜Wpoa-location։WpointyWzW~WpointszWpolicyyWօW֨WpollyW֭Wpolling֯Wpollresponseset֯WportionstWpotentialzWpptWWprezWֈWpre-provisionedևWpredicateֆWpredictzWpreferredְWprefix֏W־Wpremitives֏WprepareuWzW֍Wpresence֍WA_vbpleasereplacethecurrentsection7.4.1withthesectionfr@xpresent@reference@remote@,Dcmiheventscanbelocalorremote֚Vmihhandovercommitrequestrequestshandovertobeperforme֡VmihinformationrequestinfoqueryfilterinfoqueryparametersVmihlinkhandovercompletehasbeenspecifiedasanmihevenֿVmihlinksapisactuallyrepresentedasmlmesapin802.11֤VmihnetworkaddressinformationexchangeisusedtodiscoverwVmihnetworkaddressinformationrequestandresponseprimiti֔Vmihpollisamisleadingandinappropriatename֭VmihprotocolmessageformatisusedforremotemessageexchaxVmih-3glink-sapֵWmihfWmiis֍WWmiisprovidestheabilitytoaccessthisinformationaboutaVminorWmisleading֭WmismatchesּWmissingֿWWWmlme֤W֥W֦Wmobile~W֐W֒Wmobile-ip֔WIcwhereֱWWWWWWwhereasւWwhetherwW֎Wwhich{W֍W֒W֧WּW־WWwillxWWwithjWuWքWֆW֖W֥WֵWWwithinWwithoutօWxxWWWd ր0ց@ւPg`hpփ֌}‚!~‚"ք‚#‚$i‚%|‚&j‚'ֻ‚({‚)z‚*y‚1ֳ‚2‚3֣‚4‚5t‚6֤‚7ֵ‚8ִ‚9֥‚:֦‚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‚vv‚w‚x֮‚y֧‚z‚֎‚ֽ‚֕‚֨‚֩‚֭‚֯‚ֱ‚‚֒‚ֿ‚֍‚֏‚֪‚֖‚֫‚u‚֔‚֠‚֡‚w‚֋‚‚‚‚/kIn the beginning of the standardization process it has been agreed that memory functions are out of scope of 802.21. A state machine does need this, how far are we considering this in this standard, what is in scope and what is out of scope? pRState machine is not applicable for 802.21 and this comment needs to be revisited.wRejected{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_15`25a5.1.6bremove this sentencecL"The 802.21 standard may specify the means for security information to be "d12g2218k$Security is out of scope of 802.21.v 33W   33>c}Broadcast-based information service should not be supported because the amount of information can be large without filtering.d56g2211|e 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_23`4a5.4.3bAreplace with : " MIIS provides the ability to access this information about all heterogeneous networks in a geographical area from any single network, depending on how the 802.21 MIIS service is implemented. MIIS either relies on existing access media specific transports and security mechanisms or media agnostic transport and security mechanisms to provide access to the information. How this information is developed and deployed in a given network is outside the scope of the standard."c8 2005-12-14քE Mathieu/VivekF PERESSE/Gupta^ Editorial_14`51a5.1.3bNew Text to replace the current text: "In general, a handover decision engine will try to select the network with the most appropriate QoS support level for handover in an effort to maintain the level of user experience."րE Mathieu/VivekF PERESSE/Gupta^ Editorial_1`45a1.2csupportof -> support ofd1g2383wAccepted{k) done 2006/02/02 2005-12-14ցE Mathieu/VivekF PERESSE/Gupta^ Editorial_1`58a1.2bAOriginal Text: The mobile terminal is well-placed to detect available networks and make decisions about connectivity. The network infrastructure is well-suited to store overall network information, such as neighborhood cell lists, location of mobile devices, higher layer services available and thus help in optimum network selection. New text: The mobile terminal is well-placed to detect available networks. The network infrastructure is well-suited to store overall network information, sucd thus help in optimum network selection. New text: The mobile terminal is well-placed to detect available networks. The network infrastructure is well-suited to store overall network information, succIn section 7 replace .response primitives by .confirm primitives, as those are to be sent from a service provider to a service user .d63g2380w Withdrawn{l) none needed 2006/02/02 2005-12-14y also embed various higher layers (e.g. a TCP/IP stack). The User Equipment supports MIH Services and may change its point of attachment (PoA) at any time.9cSUser equipment should be prefered over Mobile Node (too much Mobile IP connotation)d10g2379voThe group agreed that a single term be used across the spec. UE has a 3GPP conotation. MN to be uniformly used.wRejected 2006/01/29 2005-12-14E Mathieu/VivekF PERESSE/Gupta^Technical, Non-binding_52a7single term be used across the spec. UE has a 3GPP conotation. MN to be uniformly used.wRejected 2006/01/29 2005-12-14E Mathieu/VivekF PERESSE/Gupta^Technical, Non-binding_52a7 services provided by these layers. c*The term "Lower Layers" should be defined.H}EMathieu /VivekF PERESSE/Gupta^Technical, Non-binding_7a3bbHigher Layers: layers located at OSI Level 3 and above. These layers may use the services provided by the MIH Function, and hence can be refered to as MIH users. Examples of higher layers are: IP, Mobile IP, SIP, TCP, UDP, application layer...c+The term "Higher Layers" should be defined.d14g2376vHigher Layers: These layers may use the services provided by the MIH Function, and hence can be refered to as MIH users. Examples of higher layers are: IP, Mobile IP, SIP, TCP, UDP, application layer...wAccepted-Modified 2006/01/29 2005-12-14}EMathieu /VivekF PERESSE/Gupta^Technical, Non-binding_7a3btion in MIH exchanges. Note: The paragraph is currently located in section 6.2.1 [paragraph 2], but the dynamic information is only related to MICS (not MIES). MIES is used to carry Parameters Reports Events, which is dynamic information. \g2372 2006/01/17 2005-12-14|w|EMathieu /VivekF PERESSE/Gupta^Technical, Non-binding_17a3bHigher Layers: layers located at OSI Level 3 and above. These layers may use the services provided by the MIH Function, and hence can be refered to as MIH users. Examples of higher layers are: IP, Mobile IP, SIP, TCP, UDP, application layer...c+The term "Higher Layers" should be defined.d14g2376S is used to carry Parameters Reports Events, which is dynamic information. \d17g2372vIThe IS and CS have not been introduced in the draft before this section. wRejected 2006/01/29 2005-12-14|EMathieu /VivekF PERESSE/Gupta^Technical, Non-binding_17a3bHigher Layers: layers located at OSI Level 3 and above. These layers may use the services provided by the MIH Function, and hence can be refered to as MIH users. Examples of higher layers are: IP, Mobile IP, SIP, TCP, UDP, application layer...c+The term "Higher Layers" should be defined.d14g2376 ybCle the other may be present in a fixed network entity. This network entity can be a point of attachment or any node not directly connected to the other stack. 5.4.2.4 Command service use cases The commands generally carry the upper layer decisions to the lower layers on local device entity or at remote entity. For example the command service may be used by the policy engine of an entity in the network to request a terminal to switch between links (remote command to lower layers on termiD@nal stack). Comamnds defined include MIH_Switch, MIH_Poll, etc.  cReworking of section 5.4.2 d19g2356vgThe suggested organization is accepted. Make sure current content is not removed by the suggested text.wAccepted-Clarified{k) done 2006/02/02 2005-12-14 MIH Function in a peer stack (with the use of the MIH Protocol). Commands may then be further propagated to any lower layer. One of the stack may be present in a client or mobile terminal type of device whi FxbA[Add the following text at line 21] There are two ways of tranporting MIH messages remotely. One is using data frame, either over layer 2 transport or layer 3 transport, and the other is using management frame. Management frame to deliver MIH messages shall be defined by media specific group, e.g. IEEE802.11, IEEE802.16, 3GPP, or 3GPP2. The MIH Function messages defined in section 8.4 shall be used when two MIH function entities exchage messages remotely using data frame. @A>  33$  333333%  ++++>celated information. Od90g2214vFThe context of this comment should be discussed in the adhoc on HL IEsw Withdrawn 2006/01/30 2009/01/06xE Ronny Kim^Technical, Non-binding_99`21a8.1b | Network-> Network | ---------------------------------------------------------------------------------------------------------------------------------------------------------- [Modify the t4֩EVivekFGupta^Technical, Non-binding_72`54a7.4bDestinationIdentifier: Type:MIH_LOCAL, MIH_REMOTE Valid range: N/A Description:The identifier destination of request or response. This is the identifier of local or peer MIH Function.cXRedefine DestinationIdentifier parameter in all MIH primitives in section 7.4 as followsd74g2403wAccepted{k) done 2006/02/02 2006-01-04֪EVivekFGupta^ Editorialy where the request is initiated. No other parts of the change are accepted.wAccepted-Modified 2006/01/30 2006-01-04֩EVivekFGupta^Technical, Non-binding_72`54a7.4bDestinationIdentifier: Type:MIH_LOCAL, MIH_REMOTE Valid range: N/A Description:The identifier destination of request or response. This is the identifier of local or peer MIH Function.cXRedefine DestinationIdentifier parameter in all MIH primitives in section 7.4 as followsd74g2403wAccepted{k) done 2006/01/30 2006-01-04֪EVivekFGupta^ Editorial&pcprovidedֵWֺWproviderWprovidesֲWֳWֵWWqosքWֳWqueryևWֈWqueued֓Wr֣WraeְWrdfֆWread־WreadabilityֻWreads֒Wreceipt֒Wrecognize֍WreconfigurationwWredefine֨W֩Wredefinedestinationidentifieparameterinallmihprimitive֩Vredefinesourceidentifierparameterinallmihprimitivesin֨Vreduce֐Wredundancy֔Wredundant֬Wref֣WreferencetW֌W֣WִWreferencetoowlwebontologylanguageisneeded֌Vreferred֣WrefersւWreflectvW֒WֶWַWWreflectedֽWregisterּWregistrationּWWrelatedwWxW{W֎WrelationshipstWּWrelayedwWrelevant֑WreliesWremotexW֑W֒W֚W֧WWremotelyxWremove֎WָWֹWֻWremovesapthissapsholdbereplacedbymig-3glink-sapָVֹVthulat sreemanthulauEusrinivas֗Ycevents{W֏W֑W֘W֙W֚W֛W֜W֝W֧WְWֱWeventscanbegeneratedfromcommandsneedsomeintroductory֙Veventsource֧WWexactly־WexampleֲWּWexchangewWxWexchanges{WexchangingwWexecuteֲWexistingֲWֳWֵWֶWַWWexperienceքWexplained֐WextendedֈWWfacilitate֏Wfailure֓WWfast֔WfiguretW֛W֜W֥WִWֵWWWWfigure4indraftd04doesnotmatchwellitscaptionandthtVfigureandtablearenotappropriateVfilteringօWfindingևWֈWfirst֢WflexibilityWflowWflowsWfollow։WfollowingքWfollows֨W֩W2))*(2*ronnykimx)+ ,>W3,a€`@)W:€gupta)€vivek֥ gupta€guptaW€vivek֦ gupta€bf€Bac7.3.9.1֎W7.4֨W֩W7.4.10.1/2֍W֏W7.4.10.2uW7.4.15֋W7.4.4֮W8xWְWּWֿWWWW8.3.2kW8.4.1.1lW8.4.4.5mW8.4.4.7nW8.5.1.2oW802.11֤W֥WֲW802.16gvW802.21֔W֣WֶWַWWW9֥WֵWatW{WWւW֍W֎W֏W֠W֡W֣W֬W֭WֲWֳWWWE Wolfgang FGroeting^Technical, Binding_41`65a6.2.3bVThe two figure 18 and 19 do not show the difference between local and remote commands.c^"... The figure below illustrates the differences between local and remote Link Commands. ..."d52g2229jGRename the command "remote command" within the stack to "local command"kCTo show the reader the difference between local and remote command.w Withdrawn{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_49`8a6.3.3bAdd request destinationcD"...InformationXX.request(RequestSource, InfoRequestSet) where, ..."d57g2230jOInformationXX.request(RequestSource, RequestDestination, InfoRequestSet) where,khIf no destination is mentioned, then all the MIHF who gets this information have to evaluate the requestvZTo be discussed/resolved along with other similar comments; Wolfgang to provide an update.wDeferred{l) none needed 2006/02/02 2006/01/07E Wolfgang jRemove the word fragment.kpSince we are not dealing with fragmentation it is better to remove this word in order not to mislead the reader.v4Wrong interpretation of "fragment" by the commentor.wRejected{l) none needed 2006/02/02 2006/01/073E Wolfgang FGroeting^Technical, Binding_40`56a6.2.2bAdd CommentDestination:c8Command xx.request(CommandSource, CommandInfoSet) where,d48g2227jECommand xx.request(CommandSource, CommandDestination, CommandInfoSet)kThere has been a long discussion on the .21-Mailing list ("An issue on primitives!") and an agreement has been found, that the CommandDestination should be transmitted in the Command request.vbased on a votewRejected{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_40`63a6.2.2bAdd CommentDestination:c9Command xx.response(CommandSource, CommandInfoSet) where,d49g2228nts.d47g2226jRemove the word fragment.f€Hcthe802.21standardmayspecifythemeansforsecurityinfor@k֨  gupta€"gupta#oe€#vivek֩ "gupta€$gupta%]h€%vivek֪ $gupta€&`'€'gupta(&`€(vivek֫ 'gupta€) *"p€*gupta+) €+vivek֬ *gupta€,1-€-gupta.,1€.vivek֭ -gupta€/%0e€0gupta1/%€1vivek֮ 0gupta€2e3€3gupta42e€4vivek֯ 3gupta€5 6!€6gupta75 €7vivekְ 6gupta€89€9:8€:ֱ9€;%<"P€<=;%€=ulisesolveraֲ<€>?+€?ulisesolveraֳ>€@A`€Aulisesolveraִ@€B#C9€CDB#€DulisesolveraֵC€EQFcHC€FGEQ€GulisesolveraֶF€HIEcAkmemoryWmentionedWWmihWWmih-headerWmihfWWWWmihfisnotdealingwithfragmentationVVmiisWWmiisfunctionisnotrestricetdtol2andl3sameappliesfoVmisleadWWmissingWmoreWWneedWnoWWnotWWWWWWWWofWWWWWonWWWorderWWoutWWpptWWpresentationWWprimitiveWprimitivesWWWproccessWremoteWremoveWWreqWrequestWWWresponseWrestricetdWsameWscopeWWsecurityWWsecurityisoutofscopeof802.21VseeWshouldWWWshowWWshowsWsinceWWsincewearenotdealingwithfragmentationitisbettertoVVstandardWstandardizationWstateWstorageW8kstorageofinformationisnotdonewithinthemihfunctionVtcpWtcpandudpprotocolsarenotlayer3protocolsVteleconsWthatWWWWtheWWWWWWWWWWWWWWWthefiguredoesnotcorrectlyshowstheregistrationprocessVthenWWthereWWWtherehasbeenalongdiscussiononthe21-mailinglistaniVVVthisWWWWWWtimeWtoWWWWWWWtoshowthereaderthedifferencebetweenlocalandremotecVtransmittedWWWtransportWtwoWtwoeventflowsaremissingwhichshowtheeventdiscoveryfVudpWupperWupperlayerentitiesaremihuserVuseWuserWweWWWwhatWwhichWwhoWWwithWWWWwithinWwordWWv,3,OE€QHcthe802.21standardmayspecifythemeansforsecurityinforVJ€LulisesolveraָK€MNJ$€NulisesolveraֹM€OEP€PQOE€QֺP€RS '€SֻR€T*UU€UVT*€VּU€Wֽp€XY U€Y־X€Zqiaobingֿhxie€[2\€\xie][2€]qiaobing\xieGcittWwW֍W֎Witproposesnewmechanismswhichenableamstoprepareits֍VitstW֍W֎W֏WֿWWknown֏Wl2xWWl3xWWWl3protocoltcp/udpwithVlacֵWlanguageֆW֌WlargeօWlastֽWlatency֐Wlatest։Wlayer֎W֏W֐W֧WֵW־WWlayers|W}WlevelքWlimitationsWlinesֻWlink֎W֏W֓W֚W֛W֜W֝W֞W֟W֠W֡W֤W֥W֦W֧W֮WֱWֵWּW־WֿWWWWlinkcommandsarelocalonly֞VlinkconfigurethresholdcommandhasvaluesofthresholdwheֱVlinkeventsarelocalonly֚Vesse/guptaCmathieu/vivekփ peresse/guptaDbE%E peresse/guptaFDbFmathieu/vivekքE peresse/guptaGWcfHYHIGfIyoshihiroohbaօHJSKfMZKLJSLyoshihiroohbaֆKMNJfN֣EVivekFGupta^Technical, Non-binding_22`46a5.5bmPlease insert text and figure from section 5.5 in document 21-06-0361-02-00-0000-Section5_Changes in draft. cInclude a sub-section in 5.5 defining the Generic Reference Model for different media w.r.t different SAPs in use by 802.21. This was also referred to in (21-05-0423-00-0000-Media_Independent_Handover_Ref_Model.doc) d22g2397vsChange MIH_SME_SAP to MIH_NMS_SAP in the figure. NOTE to Editor: Change the entire spec to reflect the name change.wAccepted-Modified{k) done 2006/02/02 2006-01-04֤EVivekFGupta^Technical, Non-binding_25`1a5.5.2bu.Update the reference model for 802.11 based on section 5.5.2 in contribution 21-06-0361-02-00-0000-Section5_Changes.֤EVivekFGupta^Technical, Non-binding_25`1a5.5.2bu.Update the reference model for 802.11 based on section 5.5.2 in contribution 21-06-0361-02-00-0000-Section5_Changes.inding_41`65a6.2.3chnical, Binding_40`56NkevendestinationWeventWevent-indicationWfarWfigureWflexibilityWflowWflowsWforWWfoundWWWfragmentationWWWWfunctionWWfunctionsWgetsWWhandoverWhasWWWWWhaveWWhowWifWWifnodestinationismentionedthenallthemihfwhogetsthVVinWWWWWWWWWinthebeginningofthestandardizationprocessithasbeenVinformationWWWinterpretationWintroduceWisWWWWWWWWWWWWissueWWWitWWWl2Wl3WlayerWWlistWWWlocalWlocinfoWlongWWWmachineWmakeWmakemoreefficientuseofmiisseepresentation21-06-0484-VmechanismW ,3,3 ABCDEFG^H_I`JaKbLcMdNgOiPjQkRmSnTpUvVwWxXyY{Z[\]^_`a b c defghijklmnoefghijklmnoZqiaobingֿhxie€[2\€\xie][2€]qiaobing\xie _DT`DTDTDTUjremovethissentenceVrenameWrenamethecommandremotecommandwithinthestacktolocalVrepositorygWrequestWWWrequestdestinationWrequestinglWrequestsourceWresidingoWrespectivehWresponsegWoWWWresponsedestinationWresponsesourceWfigureasshowninpresentation2VsapshWsentenceWservicegWservingnWservinvgmWshownWWshowsoWsourcelWspecifichWlWspecificationhWspeedsiWstackWstandardhWstartmWstateWstationiWstatusmWsuccessfulmWsupportedcommandlistlWsupportedeventlistlWsupportedtransportlilWtargetmWtechnologyhWthegWhWiWkWlWmWoWWWWthedefinitionofnewlinklayersapsandassociatedprimitihVthemediaindependentinformationserviceprovidestheinforgVthislWmWWvrdfևWrealiWredundent֑Wrefered|WreferencejWtWreferringWreflect֣WWregistrationWregistration/eventWrelatedies֐WrelativeiWremote֚WremotelyxWremovetW֑WremovedyWzWreplacedjWrepositorygWrequest֨WWresolution֐Wresolved֥WresponsegWresultWresultingWreword֚Wrewordsection6.1.3localandremoteevents֚VronnytWrow֮Wsap֣WWscenariosևWschemaևWschema-basedևWsdos։Wsection{W։W֚WWsecurityWsent֚WseparateWWservicegWּWservices|WsessionWshallxWshouldwW֔WsimilarWWsingle~Wsip|Wsme֣WsoWsourceWspec~W֓W֣WֲWֳWWWspecificxW֓Wspecified։WspeedsiWsrinitWtableֵWtakeօWtaskօWtcp|Wtcp/udpWicst־E Eunah Kim^Technical, Non-binding_102`44a8.3.2b4Remove prefix "MIH_" just for MIH Function Messages.cACurrent MIH Function Messages exactly have the same names as their corresponding MIH primitives, which doesn't look clear when we read the text. Primitives usually contain layer name as their prefix such as MIH_Link_Up Indication, DL_UNITDATA Request etc., but Messages don't.@Af 33  33 33  33 33fd99w Withdrawn{l) none needed 2006/02/0213ֿEQiaobingAXie@A  GMember^Technical, Non-binding_82`1a7.4.10bd99w Withdrawn{l) none needed 2006/01/3013ֿEQiaobingAXie@A  GMember^Technical, Non-binding_82`1a7.4.10b."d69g2234jF"...is generated by an upper layer entity such as MIH User that is..."\\^technicalnon-bindinguVvVwVxVyVzV{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ֿVV_ րց0ghւփP`֌}~‚%ք‚&i‚(|‚*jֻ‚2z{‚3yֳ֣‚4‚5t‚6֤‚9ֵ‚:ִ֥֦‚A‚Bָֹ‚Cֶַ‚F֛֚֘‚G֜‚Hƃ‚I֝‚J֑֓֙‚Qʃ˃‚R֞֟‚T֢‚Uּ‚Yօ֐‚Zֆևֈ΃‚a։‚c‚dv‚e֮‚f֧‚s֎‚ֽ֕֨֩‚֭‚֯‚ֱ‚‚֍֏ֿ֖֪֒‚֫@a1.2ghրցւփ1.62֌3|}~5.1.3ք5.1.65.1.8i5.3.2jֻ5.4{5.4.1z5.4.2y5.4.3Ã5.5t֣5.5.2֤5.5.4ֳ5.5.5ִֵ5.6֥5.6.1֦5.6.1.5ָ5.6.1.6ֹ5.8.2ֶ5.8.3ַ6.1.1֘֙6.1.2֛֚6.1.3֜6.1.4ƃ6.1.6֝6.1.7֑W֓6.1.7and6.1.8֑V6.1.8֑W6.2.2˃6.2.36.2.4֞֟6.2.6.2ּ֢6.3.2օ֐6.3.3΃6.3.4.1ֆևֈ։77.2.1.1Ѓ7.2.1.2v7.3֧7.3.1.37.3.9.1֎7.4֪֨֩֫7.4.1ֽ֕7.4.10֖֒Wֿ7.4.107.4.117.4.137.4.14֖V7.4.10.1֍֏7.4.11u֖W7.4.12.1.2֠7.4.12.2.2֡7.4.13֖W7.4.14w֖֔W7.4.15֋7.4.15.1.27.4.15.2.27.4.15.3.4ֺ7.4.6֭7.4.6.2.2֯7.4.8.1.4ֱ7.4.8.2.48ְW8.1x8.2.38.3.18.3.2k־8.4.1֗{bd‚‚ֺ‚x‚ְ‚‚‚־Ã!kÃ! ֗Ã!0lÃ!@mÃ!PnÃ!`oÃ!pֲÃ!֬Ã!֊ entity such as MIH Function that is..."g2234jF"...is generated by an upper layer entity such as MIH User that is..."k!Upper layer entities are MIH User 2006/01/17 2006/01/07E Wolfgang FGroeting^Technical, Binding_94`5a 7.4.15.1.2tion that is..."g2234jF"...is generated by an upper layer entity such as MIH User that is..."k!Upper layer entities are MIH User 2006/01/17 2006/01/07E Wolfgang FGroeting^Technical, Binding_94`5a 7.4.15.1.2tion that is..."g2234jF"...is generated by an upper layer entity such as MIH User that is..."k!Upper layer entities are MIH User 2006/01/17 2006/01/07E Wolfgang FGroeting^Technical, Binding_94`5a 7.4.15.1.2 is..."k!Upper layer entities are MIH User 2006/01/17 2006/01/07E Wolfgang FGroeting^Technical, Binding_94`5a 7.4.15.1.2UjrouternWrplaceWrplaceexistingfiguewithfigureasshowninpresentation2VsapshWsentenceWservicegWservingnWservinvgmWshownWshowsoWsourcelWspecifichWlWspecificationhWspeedsiWstackWstandardhWstartmWstateWstationiWstatusmWsuccessWsuccessfailurecallbackVsuccessfulmWsuchWsupportedcommandlistlWsupportedeventlistlWsupportedtransportlilWtableWtargetmWtcp/udpWtechnologyhWthatWthegWhWiWkWlWmWoWWWWWWthedefinitionofnewlinklayersapsandassociatedprimitihVthemediaindependentinformationserviceprovidestheinforgVthepduhasbeenVVthislWmWWWHjinformationxxresponseresponsesourceresponsedestinationinVkdestinationWWdifferenceWdiscoveryWdiscussedWdiscussionWWWdoesWWdoneWduringWefficientWenhanceWentitiesWevaluateWW<]csuggestionքWֳWsupportրWքWsupportedօW֒WsupportofրWsupportofsupportofրVsystem֐Wt֣Wtable֍W֏W֐WֺWּWֿWWWtable-2֝Wtable-2linkeventsarelocalonly֝Vtable-3֒Wtable-5֢Wtake֏WtalkingWWtbdֲWtcp/udpWtechnologyֵWtellևWֈWterm|W}WւW֪W֫Wterminal֒WtextvWւW֒W֘W֙WֵWֺWֻW־WֿWWtextsuWthattW{W֒W֘WֵWֽWWWthetWuWvWwWxW{W|W}WցWւWքWօWֆWևWֈW։W֊W֋W֎W֏W֐W֑W֒W֓W֔W֖W֗W֘W֠W֡W֣W֦WֲWֳWֵWֺWֻWּW־WֿWWWWWWWWWcsuggestion@ ֈbcUse of DNS query for finding the FQDN part of the location of the extended schema is not useful because FQDN does not tell the entire URL of the schema. Instead, use of DHCP might be better to tell the URL of the extended schema. d61g2216v!based on modifications discussed.wAccepted-Modified{k) done 2006/02/02 2006/01/09։EYoshihiro Ohba^Technical, Non-binding_50`8a6.3.4.1bAReplace with Figure 23 with the figure in Section 2 of 21-06-0460-00-0000-Basic_Schema.doc. and the contents of 21-06-0401-03-0000 Also, update the paragraph starting at line 8, page 50 (the paragraph explains Figure 23) as follows: Figure 8-3 below shows an example graphical representation of the 802.21 MIIS basic schema in which 'Network' 'L2', 'L3', 'Location', 'IPv4', 'IPv6' , 'Link-Type', 'PoA', 'Civic Address', 'Geo-Coordinates' are represented as class, while all others are properjinfoqueryfilterWinfoqueryparametersWinforequestsetWinforesulttsetWinformationgWhWiWWWinformationxxWWinformationxxrequestrequestsourcerequestdestinationinforVzkprocessWWprotocolsWreaderWWWreduceWreducedelaytimeduringthedecisionproccessforahandoveVregistrationWremoteWremoveWWreqWrequestWWWresponseWrestricetdWsameWscopeWWsecurityWWsecurityisoutofscopeof802.21VseeWWseveralWshouldWWWshowWWshowsWsinceWWsincewearenotdealingwithfragmentationitisbettertoVVstandardWstandardizationWstateWstatusWstorageWkbeWWWbeenWWWWWbeginningWbetterWWbetweenWcallbackWcommandWWWcommanddestinationWWconsideringWcorrectlyWdealingWWWWdecisionWdelayW) ֏bXie@A  GMember^Technical, Non-binding_82`1a7.4.10bASuggest to add a new section 7.4.x "MIH Link Handover Complete", as specified in 21-06-0465-00-0000-MIH_Link_Handover_Complete, before the current 7.4.10 "MIH Handover Initiate". @A*  33 33*c 33  33 33  33 33fd99 2006/01/1913ֿEQiaobingAXie@A  GMember^Technical, Non-binding_82`1a7.4.10bASuggest to add a new section 7.4.x "MIH Link Handover Complete", as specified in 21-06-0465-00-0000-MIH_Link_Handover_Complete, before the current 7.4.10 "MIH Handover Initiate". @A*  33 33*c`jexistingWfanWfacilitatediWfailureWfastiWfigueWfigureoWWWfillslWfinalWflowWfollowingoWforgWhWforwardingmWfragmentWWfromWfuncationkWfunctionhWkWmWgeneratedWhandovergWmWhandovershWiWhandoversduetothemobilestationnodefastmovementspeediVhasWWheaderWhelphWhencelWhigherWhigherlayerprotocoltcp/udpVifhWlWmWinkWlWoWWindependentgWindicationWWWonWWktoenhancetheinterpretationofthemih-headerintointrodVtoshowthereaderthedifferencebetweenlocalandremotecVtransmittedWWWtransportWtwoWtwoeventflowsaremissingwhichshowtheeventdiscoveryfVudpWupperWupperlayerentitiesaremihuserVuseWuserWweWWWwhatWwhichWwhoWWwithWWWWwithinWwordWWp1֒W15W2}W21-06-0425-01ֵW21-06-0494-00ֺW3gpp}W48W49W802.11}W802.2}W802.21}WWaboutiWցWacceptedWaccessiWacross}WaddoWadding։Wall֖WalreadytWalredayoWalso}WֵWֺWalsolookat21-06-0425-01ֵValsolookatcontribution21-06-0494-00ֺVan}WandiWtW}WցWWWtomnthroughoutthedocument~VchangingiWcommentWWconditionsiWdwResubmit{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_95`54a 7.4.15.2.2b Add CallbackcSuccess / Failured93g2236jSuccess / Failure / CallbackkReduce delay time during the decision proccess for a handover. See presentation "21-06-0483-00-0000_Callback_status_in_IS_primitive.ppt"v by a votewRejected{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_100`8a8.2.3brename L3 with higher layerc#"...L3 protocol (TCP/UDP) with ..."d97g2237j"...higher layer protocol (TCP/UDP)k0TCP and UDP protocols are not layer 3 protocols.w Withdrawn{l) none needed 2006/02/02 2006/01/071.2bAdd location infoUpper layer entities are MIH Userv4 .... is generated by an MIH Function that is .... wAccepted-Modified 2006/01/30 2006/01/07E Wolfgang FGroeting^Technical, Binding_94`5a 7.4.15.1.2bAdd location infovmatchWT`DTDTDTeting+)+wolfgang *groeting,-e-groeting.,.wolfgang -groeting/h0f0groeting1/h1wolfgang 0groeting2`33groeting42`4wolfgang 3groeting5e66groeting75e7wolfgang 6groeting89!9groeting:8:wolfgang 9groeting;<! <groeting=;=wolfgang <groeting _DT`DTDTDTֈEYoshihiro Ohba^Technical, Non-binding_49`62a6.3.4.1bANew text: Unlike the basic schema, the extended schema is expected to be updated periodically, e.g., when a new linklayer 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 pre- provision 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, oBcther methods such as DHCP a DNS query may be be enabled to be used for finding out the URL location (FQDN part) 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.Q@Rvtobediscussed/resolvedalongwithothersimilarcommentswVVtoberesolvedinconjunctionwithcomment27֥VtopicֳWtranportingxWtransportxWWtwoxWևWtypexWtypicallyևWudp|WuejW~WunderstoodWuniformly~WuntilִWuntiltheendoftheallcommentsִVupdate֮WWWupdatetherownumbertobegroupedwithcommands֮VupdatedևWupon}WurlևWuse|W֜WLpapplicableWappropriatekWareiW}WaskW}WWat}WֵWֺWbeֲWWbeentWbelow}WbothցWWboththemobileterminalandthenetworkcanmakedecisionsցVbyiW}WcanցWcapabilityֽWcellsiWchangekWchanged~WֽWchangeduetomnthroughoutthedocument~VchangingiWcommandWcommentWWconditionsiW>vitօWֳWWl3Wl3transportisgenerallyunderstoodtoincludel4tcp/udpeVl4WlayerxW|W}Wlayers|WlinkiW֚WֿWWlinkeventsasdefinedinspecareonlylocaldestinationisVlisttWlisted֓Wlocal֚WWlocationևWlocationinfoWlookedֿWlower}Wlowerlayerdefinitionneedstobeaddedthetextwouldhave}Vmacro-cellsiWmakegWyWzW֎Wmaketheflagaswellasmobilitymanagementprotocolfield֎VmanagementxW֎WּW khjwAccepted{k) done 2006/02/02 2006/01/09iE Peretz Feder^Technical, Binding_15`40a5.1.8bAdopt the following textc Clarify 5.1.8d13g2225iPeretzjAHandovers due to the mobile station node fast movement speeds relative to the base station or access point are facilitated by providing real time link conditions and timely information about overlay neighboring micro-cells and macro-cells. @A   33  #  6  337  j  33    33    33  33pHandovers due to the mobile node movement are facilitated by providing timely information about changing link conditions and different access networks in neighboring micro and macro cells.v^@>vhandovergW֡WֲWWhandovercontrolVhemobilestationnodemovementspeedsreliVhas~Whave{W}Whence|Whigher|Whigherlayerstheselayersmayusetheservicesprovidedby|Vin{W֣W֥WֳWֵWincludeWincorporatedֳWindependentgWindiferentlyցWinformationgWiWWintroduced{Wip|WisyWzW{WWitֳWl3Wl3transportisgenerallyunderstoodtoincludel4tcp/udpeVl4Wlayer|W}Wlayers|WlinkiWlower}Wlowerlayerdefinitionneedstobeaddedthetextwouldhave}Vmacro-cellsiWmakegWyWzWmay|WmediagWmicro-cellsiWmihjW|W֣WWmihcommandsVmihdeploymentmodelbechangedbacktotheoriginalnameuejVmiheventsVmisunderstoodWmnjW~WmobileiW|WmodelgWjWmoregWֳWmovementiWnamejW֣WW ivAHandovers due to the mobile station node movement speeds relative to the base station or access point are facilitated by providing real time link conditions and timely information about overlay neighboring micro-cells and macro-cells.@A   33  #  1  332  e  33    33    33wAccepted-Modified{k) done 2006/02/02 2006/01/09jE Peretz Feder^Technical, Binding_19`13a5.3.2bChange sectioncJChange section 5.3.2 to agree with new communication model (section 5.3.1)d15g2226iPeretzjA0Adopt contribution 21-06-0490-0000-section_5_3_30@A  33v}"MIH Deployment Model" be changed back to the original name. UE to be replaced with MN. Reference points be correctly placed.wAccepted-Modified{k) done 2006/02/02 2006/01/09 hjAz  33i  w    33    33z cA"...MIIS provides the ability to access this information about all heterogeneous networks in a geographical area from any single L2 network, depending on how the 802.21 MIIS service is implemented. MIIS either relies on existing access media specific transports and security mechanisms or L3 transport and L3 security mechanisms to provide access to the information. How this information is developed and deployed in a given L2 network is outside the scope of the standard. "d23g2220kdMIIS Function is not restricetd to L2 and L3. Same applies for the security and transport mechanism.vZL3 transport is generally understood to include L4 (TCP/UDP) etc. The original text is ok.wRejected{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_30a5.6bAdd "Network Information".cHOnly MIH Triggers, Link Status Update and Handover Control are depicted.d30g2221jAdd "Network Information".5.4.3b|vHigher Layers: These layers may use the services provided by the MIH Function, and hence can be refered to as MIH users. Examples of higher layers are: IP, Mobile IP, SIP, TCP, UDP, application layer...wAccepted-Modified{k) done 2006/02/02 2005-12-14vterm~WtextyWzW}WօW֚W֨WWthat~W֚WֺWWthegWiWjWtWwWxWyWzW{W|W}W~WցWօWևW։W֍W֎W֑W֓W֔W֚W֜W֣W֨W֮WֲWֳWִWֵWֺWVtheisandcshavenotbeenintroducedinthedraftbeforet{VthemediaindependentinformationserviceprovidestheinforgVthesuggestedorganizationisacceptedmakesurecurrentconyVzVthese|Wthis{WtimeiWtimelyiWtogWiWjW|W}W~WցW֣WֳWWtopicֳWtransportWudp|WuejW~WunderstoodWuniformly~Wupon}Wuse|Wused~Wusers|WwasWwithjWwordցWworkֳWworked}Wwould}Wwacceptedhրւփք֤accepted-clarifiedyz}accepted-modifiedgij|ց֣deferredtֳrejected{~withdrawnֻ|vcan|W֚WcapabilityWcategorizationֿWcategoryּWchangeցW։W֣W֨W֯WֲWּWWWchangemihsapenumerationtoVchangemihsmesaptomihnmssapinthefigurenotetoedit֣VchangethecallflowtobeconsistentwiththecurrentspecֲVchangethefigurestoseparateregistration/eventindicationVyWzWcontextWcontrolWcorrectlyjWcs{WcurrentyWzWdecisionsgWdefinition}WdeploymentjWdifferentgWdiscussedֳWdraft{WdueiWeditor֣WeffectivegWenablinggWendִWentire֣Wentity֚WenumerationWetcWevent֚Wevents֚WWexamples|WfacilitatediWfigure֣WfiguresWflowsWforgWfunction|WgenerallyWgo֚Wgroup~WֳWgroupdiscusseditthetopicneedsmoreworktobeincorporaֳVuvneeds}WֳWֿWWneighboringiWnetworkWnetworkinformationVnetworksgWnms֣Wno֨WnodeiWnotyWzW{WևWWWnote֣WֺWnotethattheexampletable33atobeplacedintheannexֺVnotionWnumber֮Woctets։WoftWwWxW|WօWևW։W֐W֔W֨WִWֵWֿWWWWokWonwWֈW֏W֔WWWonexWonly֨WֵWWonlychangetexttotheidentifierofentitywherethereque֨Voptional֎WWoriWxWWorganizationyWzWoriginaljWWotherxWևW։W֨WWWoverxWoverlayiWparameterWWparttWpartsևW֨Wperforming֡WplacedjWֺWWplanexWpointiWpointsjWpoll֯WportionֵWpossibleֿWpre-provisionedևWprepareֲWives/messagesֲWprotocolxW֎WprovideWWW]֧c.For local link layer events we do not need EventSource parameter. This parameter is currently defined as LINK_EVENT_SOURCE {Local Node, Remote Node} which is no longer applicable for link layer events d68g2401wAccepted{k) done 2006/02/02 2006-01-04֨EVivekFGupta^Technical, Non-binding_72`53a7.4bSourceIdentifier: Type:MIH_USER_TYPE valid range: N/A Description:The identifier of entity where the request is initiated. This may be a MIH User such as policy engine, an upper layer mobility protocol, transport, or application.cSRedefine SourceIdentifier parameter in all MIH primitives in section 7.4 as followsd73g2402vxOnly change text to: The identifier of entity where the request is initiated. No other parts of the change are accepted.wAccepted-Modified{k) done 2006/02/02 2006-01-04(ֶE Ulises Olvera^Technical, Binding_32`40a5.8.2bUpdate according to submitted document: 21-06-0494-00-0000-InterDigital3GPP/3GPP2 Amendments.doc (DCN number to be provided by chairman)c`Update this section in order to reflect mapping of existing 3GPP primitive to 802.21 primitives.d33g2218wDeferred{l) none needed 2006/02/02 2005/11/06ַE Ulises Olvera^Technical, Binding_32`52a5.8.3bUpdate according to submitted document: 21-06-0494-00-0000-InterDigital3GPP/3GPP2 Amendments.doc (DCN number to be provided by chairman)caUpdate this section in order to reflect mapping of existing 3GPP2 primitive to 802.21 primitives.d34g2219wDeferred{l) none needed 2006/02/02 2005/11/06ָE Ulises Olvera^Technical, Binding_31`8a5.6.1.5s.d34g2219wDeferred{l) none needed 2006/01/31 2005/11/06ָE Ulises Olvera^Technical, Binding_31`8a5.6.1.5Pbupdateaccordingtosubmitteddocument21-06-0xxx-02-0000-iֻVupdateaccordingtosubmitteddocument221-06-0493-01-0000dֳVupdatesection5.6.1from21-06-0361-02-00-000changes֦Vupdatethereferencemodelfor802.11basedonsection5.5.2֤VupdatedևWֈWְWupdatesְWupdtaedְWupperyWzW֏W֨WurisֆWurlևWֈWuseyWzW|W}W֓W֔W֟WusedtWxWyWzW{WօWևWֈWuser~WքW֨WWuserequipmentaterminalentitythatembedsoneormoresup~Vusers|W֚WusesֆWusingxWֆWֈWvalid֍W֏W֠W֡W֨W֩W֯Wvalidrange0-1֡Vvalidrangen/a֨V֩V֯VvaluesֱWֱWֱWֱWֱWֱWֱW8+bvaries@Pc2@B7.3.9.1@aaa@aambiguity@Qapplicable@Fare֛Eas@basic@capabilitydiscoverymechanismneedsnegotiationcapability@=communication@connotation@describethemediaandmediaindependentsapsappropriately@Telement@%entire@events@for@Yfrom@handover@`insection7replaceresponseprimitivesbyconfirmprimitiv@ninfrastructureցinitiate@it@linkeventsarelocalonlyinnaturefigure13isnotapplic@Gmechanism@,miheventscanbelocalorremote@zmobility@names@onֿ~one@plane@ proposes@&provided@removes@prequest/response@Nsection@still@<R vtheֻWֿWWWWWWWWthecommentneedstobelookedatafterthecurrentcategoriֿVthecontextofsecuritywasmisunderstoodbythecommentorVthecontextofthiscommentshouldbediscussedintheadhocwV֔Vnformationinthecolumnisredundentremovetheentire֑Vtheisandcshavenotbeenintroducedinthedraftbeforet{VthemediaindependentinformationserviceprovidestheinforgVthesuggestedorganizationisacceptedmakesurecurrentconyVzVthewordfragmentisreferringtohlfragmentandnotfragmeVtheworkwouldbediscussedinthesubnetinformationadhoc֍Vthese|WWthis{W֔Wthroughout֯WtimeiWtimelyiWtogWiWjW|W}W~WցWօWևW։W֓W֚W֣W֥W֨W֮W֯WֱWֳWּWֿWWWWWWWWtobediscussedfurtherֱVj|ց֣Ńdeferredt֘mlvacceptedyWzW֨WaccessgWiWxWևWacrossgW~Waction֯Wactionxiaoyuclarifystatemachineeffects֯Vadd֚Waddtexttoclarifythatalinkeventcangothemihfandbe֚Vadded}WadhocwW֍W֔WafterֿWagainօWagreed~WallִWalongWWalwaysWangWցWևW֚WWWWWandgWiWxW{W|WօWևW֚WֿWWannexֺWapplicablexWapplication|WappropriateցWareiWxW|W֨WWas|WևW֎W֚W֡WWWWasdescribedearliertherdfschemadefinitionformiisconsևVatֿWbackjWbaseiWbasedֈW֏WWbasedonavote֏VVbasedonmodificationsdiscussedֈVbasicևWbejWwWxW|W}W~WևWecontributionsforspecificfailurecodestobeli֓VbyiWyWzW|WֻWWWWbythecommentorֻVebִ 2006/02/02 2005/11/0610ֵE Ulises Olvera^Technical, Binding_28`12a5.5.5bUpdate according to submitted document: 21-06-0494-00-0000-InterDigital3GPP/3GPP2 Amendments.doc (DCN number to be provided by chairman)cAThe MIH-3GLINK-SAP has bee agreed as the SAP that provides mapping of 3GPP triggers toward the MIH Function. We propose to use the same approch toward 3GPP2 technology only that the link layer information should come from PPP and LAC. Therfore we propose to replace existing figure 9 and corresponding text with the figure and text provided in contribution 21-06-0494-00-0000-InterDigital3GPP/3GPP2 Amendments.cocd26g2217pAlso look at 21-06-0425-01vNAccept only the 3GPP2 portion of the table 33a in the above 21-06-0494-00-0000wDeferred{l) none needed 2006/02/02 2005/11/069rvhandoversiWhandoversduetothemobilestationnodemovementspeedsreliVhas~Whave{W}Whence|Whigher|Whigherlayerstheselayersmayusetheservicesprovidedby|VhlwW֔WWidWidentifier֨Wieee802.11xWieee802.16xWieswW֔WietftW։WifWimplementationևWimplicitWinwWxW{WևW։W֍W֑W֓W֔W֜W֣W֥WֳWֵWֺWWWWWincludeWincorporatedֳWindependentgWindicationWindication/de-registWindiferentlyցWinformationgWiW֍W֑WWinitiated֨WinterpretationWintroduced{Wip|WisxWyWzW{WևW֑W֨WֿWWWWWWisgeneratedbyanmihfunctionthatisVissues֐WWitrlayerdefinitionneedstobeaddedthetextwouldhave}Vmacro-cellsiWmakegWyWzWmanagementּWvmisunderstoodWmnjW~WmobileiW|Wmobility֎WmodelgWjWmodification֯WּWmodificationchangepolltogetthroughout֯VmodificationchangeservicecategorynamefromgeneraltosyּVmodificationsֈWmoregW֓WֳWmovementiWnamejW֣WּWnamesWnativexWneedtWneedtodiscuss16partwithronnysrinitoprovidelistoftVneededWgvchangethewordindiferentlytoanappropriatewordցVchangedjWclarify֐W֚W֯WWcleaningօWcodes֓Wcolumn֑WcommandWcommands֮WֿWWcommentwW֔W֥WֿWcommentorֻWWWcommentstWִWWWcompleteֿWconclusionWconditionsiWconjunction֥Wconotation~WconsistentֲWconsistsևWcontentyWzWcontextwW֔WWcontributions֓WcontrolWcorrectlyjWcouldWcs{WcurrentyWzWֲWֿWdataxWdecisionsgWdefinedxWWdefinition}WևWdeploymentjWdescribedևWdestinationWWdhcpևWdifferentgWdiscoveryWdiscusstWdiscussedwWֈW֍W֔WֱWֳWdiscussed/resolvedWWdnsևWdraft{WWfunction|WgenerallyWgo֚Wgroup~WֳWgroupdiscusseditthetopicneedsmoreworktobeincorporaֳVvusethefigurein21-06-0482-00-0000֜VusedxW~WևWWusers|WusingxWvalueWvote֏WWWwasWwaysxWwell֎WwhenxWwhereևW֨WwhetherWwill֐WwithjWtWևW։W֥W֮WֲWWWWwithinWwolfgangWWWwolfgangtodriveconclusionontheissuesVwordցWWwork֍WֳWworked}WWwould}W֍WWwrongWwronginterpretationoffragmentbythecommentorVx։Wxiaobing֐Wxiaobingwilldriveresolutionofissues֐Vxiaoyu֯WyoshihiroօWyoshihirototakethetaskofcleaningthetextandprovidinօVwacceptedhklւփքֆ֋ְֺֽ֖֛֢֤֦֧֪֭֓֗֝֞֟֠֩֫Ã̃accepted-clarifiedyz}֚֮accepted-modifiedgij|ցևֈ։֎ּ֣֒֡֨֯Ńƃdeferredt֍֐֘Bowacceptedmdeferred֥O{done֢kdone֓cneeded@ַ֙1vusethefigurein21-06-0482-00-0000@u^vprovided|WprovidesgWprovidingiWօWpurposesWquerygWևWևWrealiWredundent֑Wrefered|WreferencejWreferringWreflect֣WWregistrationWregistration/eventWrelatedies֐WrelativeiWremote֚Wremove֑WremovedyWzWreplacedjWrepositorygWrequestWresolution֐Wresolved֥WresponsegWresultWresultingWreword֚Wrewordsection6.1.3localandremoteevents֚Vsap֣WWschemaևWschema-basedևWsection{W֚WsecurityWsent֚WseparateWservicegWּWservices|WsessionWsimilarWWsingle~Wsip|Wsme֣WsoWsourceWspec~W֓W֣WֳWWWspecific֓WspeedsiWstationiWsubnet֐WsuggestedyWzWsupposedևWsureyWzWsystemּWtableֵWtakeօWtaskօWtcp|Wtcp/udpWvmatchtheprimitivenamesmihcapabilitydiscoveryrequestwVmay|WևWWmediagWxWmerge։Wmergethebitsspecifiedforietfwithothersdosinsection։VmessageֲWmessagesxWmethodsևWmicro-cellsiWmihjWxW|WևW֚W֣WֿWWWWWWmihcommandsVmihdeploymentmodelbechangedbacktotheoriginalnameuejVmiheventsVmihf֚WmiisևWgLvmatchtheprimitivenamesmihcapabilitydiscoveryrequestw@misunderstood@needs@primitive@uprovided@rdf@statemachine@term@theֻthegroupagreedthatasingletermbeusedacrossthespec@Rtobediscussed/resolvedalongwithothersimilarcommentsw@.J֓ESrinivasF Sreemanthula^Technical, Non-binding_39`7a6.1.7bbNeed explicit text defining the scenario (mobile generated or network generated) and the corresponding effect. See remedy #2 in document 21-06-0477-00-0000-event-commands-updates.doccA(For remote MIH commands in Table-3 that are bi-directional, the corresponding "Effect of Receipt" section must reflect which scenario is considered e.g mobile generated or network generated. This is important since not all commands are supported by the terminal. The current text reads ambiguous.(@A  33d79g2224v21-06-0477-01-0000wAccepted-Modified 2006/01/30 2006/01/06֓ESrinivasF Sreemanthula^Technical, Non-binding_39`7a6.1.7bjFCommand xx.response(CommandSource, CommandDestination, CommandInfoSet)kThere has been a long discussion on the .21-Mailing list ("An issue on primitives!") and an agreement has been found, that the CommandDestination should be transmitted in the Command Response.pFunny ...Comment 48 is rejected and 49 is accepted. Declining comment #49 as well for now to keep both Command.request and Command.response consistent.vWolfgang to drive conclusion on the issues: 1) Clarify purposes of event source, command source, event destination, command destination 2) Clarify value of these fields 3) Clarify if MIH session ID resulting from registration is needed as a parameter wAccepted{e) editor disagrees 2006/02/02 2006/01/07nical, Binding_40`63a6.2.2bAdd CommentDestination:c9Command xx.response(CommandSource, CommandInfoSet) where,d49g2228jFCommand xx.response(CommandSource, CommandDestination, CommandInfoSet)vdrive֐WWdueiWduplicationֿWexWearlierևWeaseևWeditor֣WeffectivegWeffects֯WeitherxWenabledևWenablinggWendִWentire֑W֣WentitiesxWentityևW֚W֨WenumerationWetcWevent֚WֿWWWevents֚WֿWWWexampleֺWexamples|WexchagexWexistingWWexpectedևWextendedևWfacilitatediWfailure֓WfeaturesxWfield֎WfieldsWfiguretW։W֜W֣WfiguresWfirst։Wflag֎WflowֲWflowsWforgWևW։W֓WֿWfqdnևWfragmentWWfragmentationWframexWframesxWfromtWּWWfunctionxW|WWfurtherֱWgxWgeneralּWgenerallyWgeneratedWget֯Wgo֚WgroupxW~WօWֳWgroupdiscusseditthetopicneedsmoreworktobeincorporaֳVgrouped֮W8 gvAThe Media Independent Information service provides the information model and an information repository to make for query and response, enabling a more effective handover decisions across different access networks.@AR 33g  n  33RwAccepted-Modified{k) done 2006/02/02 2006/01/09hE Peretz Feder^ Editorial_2`30a1.2bAdopt the following new textc Clarify cd5g2224iAndrea, Pererz, QiaobingjA^The definition of new link layer SAPs and associated primitives for each specific access technology. The newprimitives new primitives help the MIH Function collect link information and control link behavior during handovers. If applicable, the new SAPs will be recommended as amendments to the respective access technology standard specification. ^@tփbIn a), replace the 3 remaining occurences of "architecture" with "framework", as only the first occurence of "architecture" was replaced.cnewprimitives -> new primitivesd6g2386wAccepted{k) done 2006/02/02 2005-12-14քE Mathieu/VivekF PERESSE/Gupta^ Editorial_14`51a5.1.3bNew Text to replace the current text: "In general, a handover decision engine will try to select the network with the most appropriate QoS support level for handover in an effort to maintain the level of user experience."cThere is too much suggestion in the following sentence: "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."d11g2387wAccepted{k) done 2006/02/02 2005-12-14օEYoshihiro Ohba^Technical, Non-binding_48`55a6.3.2b }pvR"Lower Layer" definition needs to be added. The text would have to be worked upon.wAccepted-Clarified{k) done 2006/02/02 2005-12-14~EMathieu /VivekF PERESSE/Gupta^ Editorial_7a3bA9User Equipment: A terminal entity that embeds one or more supported access technologies (802.3, 802.11, 802.16, 3GPP, 3GPP2), and a MIH Function. The UE may also embed various higher layers (e.g. a TCP/IP stack). The User Equipment supports MIH Services and may change its point of attachment (PoA) at any time.9cSUser equipment should be prefered over Mobile Node (too much Mobile IP connotation)d10g2379p)Changed UE to MN throughout the document.voThe group agreed that a single term be used across the spec. UE has a 3GPP conotation. MN to be uniformly used.wRejected{k) done 2006/02/02 2005-12-14E Mathieu/VivekF PERESSE/Gupta^Technical, Non-binding_52a7LWpdecisionsցWdecliningWdeferredtWdidoW֒WdidnotaddresidinginnetworksincethatisalredayimplieoVdidnotfindrevision1֒VdifferentiW}WdifficultֲWdocument~WdueiWexample}WfacilitatediWfigureWfind֒WforkW}WֽWWWfrom֖WfromtheֽWfunctionkW}WfunnyWfunnycomment48isrejectedand49isaccepteddecliningcoVhandoversiWhandoversduetothemobilenodemovementarefacilitatedbyiVhastWheadingkWies։WimpliedoW}Wlogical}Wlower}Wlowerlayersthesearethelayerslocatedatosilevel2and}Vmac}WmachineWmacroiWmakeցWmaykWmedia}WmicroiWmih}WֽWmn~WmobileiWցWmovementiWmultipletWneedkWֽWneedsWneighboringiWnetworkցWnetworksiWnoֽWnodeiWnotWoptionsֽWor}W}Kv\Change MIH_SAP enumeration to: MIH Events MIH Commands Network Information Handover ControlwAccepted-Modified{k) done 2006/02/02 2006/01/0711E Wolfgang FGroeting^Technical, Binding_37a6.1.4bfRplace existing figue with figure as shown in presentation: "21-06-0482-00-0000_event_flow_change.ppt"c=The figure does not correctly shows the registration process.d39g2222jfRplace existing figue with figure as shown in presentation: "21-06-0482-00-0000_event_flow_change.ppt"k=The figure does not correctly shows the registration process.pUpdated figure 15vChange the figures to separate Registration/Event.indication/De-registration flows. Event.indication may not always result in MIH.indication so reflect the notion.wAccepted-Modified{k) done 2006/02/02 2006/01/0715/ָbUpdate according to submitted document: 21-06-0494-00-0000-InterDigital3GPP/3GPP2 Amendments.doc (DCN number to be provided by chairman)c8Remove SAP. This SAP shold be replaced by MIG-3GLINK-SAPd31g2220wDeferred{l) none needed 2006/02/02 2005/11/06ֹE Ulises Olvera^Technical, Binding_31`13a5.6.1.6bUpdate according to submitted document: 21-06-0494-00-0000-InterDigital3GPP/3GPP2 Amendments.doc (DCN number to be provided by chairman)c8Remove SAP. This SAP shold be replaced by MIG-3GLINK-SAPd32g2221wDeferred{l) none needed 2006/02/02 2005/11/06ֺEUlises ^Technical, Binding_98`34a 7.4.15.3.4bInsert the text and table described in section 5.1.5 and 5.1.5.1 from contribution 21-06-0425-01-0000-InterDigital3GPP/3GPP2 Amendments.doc {neededַWָWֹWֻW־WֿWWWWWWWWWWWWWWWWWnext֥WֲWnonetWwWxW{WWօW֍W֏W֐W֑W֔W֕W֘W֙W֜W֬WֱWֳWִWֵWֶWַWָWֹWֻW־WֿWWWWWWWWWWWWWWWWWround֥WֲWto֥WֲW> ֘cd35g2240wDeferred{l) none needed 2006/02/02 2006/01/06֙ESrinivasF Sreemanthula^Technical, Non-binding_39`2a6.1.1bBRemedy #1 from document 21-06-0479-00-0000-events-for-commands.doccTEvents can be generated from commands. Need some introductory text in this section. d45g2241wRejected-Duplicate{l) none needed 2006/02/02 2006/01/066 ,֘cA  33}jKEvent xx.indication(EventSource, EventDestination, EventInfoSet) where, ...kThere has been a long discussion on the .21-Mailing list ("An issue on primitives!") and an agreement has been found, that the EvenDestination should be transmitted in the Event-Indication.vGLink Events as defined in spec are only Local. Destination is implicit.wRejected{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_39a6.1.7bRemove the word fragment.c/Point 7 and Point 8 is talking baout fragments.d43g2225jRemove the word fragment.kpSince we are not dealing with fragmentation it is better to remove this word in order not to mislead the reader.vDThe word fragment is referring to HL fragment and not fragmentation.wRejected{l) none needed 2006/02/02 2006/01/072E Wolfgang FGroeting^Technical, Binding_40a6.1.8bRemove the word fragment.c/Point 7 and Point 8 is talking baout fragments.d47g2226cY{neededtWwWxW{WWօW֍W֏W֐W֑W֔W֕W֘WFGroeting^Technical, Binding_49`15a6.3.3bAdd response destinationcE"...InformationXX.response(RequestSource, InfoRequestSet) where, ..."d58g2231jTInformationXX. response (ResponseSource, ResponseDestination, InfoResulttSet) where,khIf no destination is mentioned, then all the MIHF who gets this information have to evaluate the requestvZTo be discussed/resolved along with other similar comments; Wolfgang to provide an update.wDeferred{l) none needed 2006/02/02 2006/01/07E Wolfgang FGroeting^Technical, Binding_53a7.2.1.1bremove all segementsc'Point 10 and 11 says: "all segments .."d64g2232jThe PDU has been k'MIHF is not dealing with fragmentation.w Withdrawn{l) none needed 2006/02/02 2006/01/077E Wolfgang FGroeting^Technical, Binding_54a7.2.1.1bremove all segementsc'Point 10 and 11 says: "all segments .."d66g2233jThe PDU has been k'MIHF is not dealing with fragmentation.w WithdrawnOc {done֢W֣W֤W֦W֧W֨W֩W֪W֫W֭W֮WְWֺWּWֽWWWWWWekWWeeditordisagreeskVVeditorkWWh֥WֲWhdefertonextround֥VֲVkgWhWiWjWlWmWnWoWuWvWyWzW|W}W~WրWցWւWփWքWֆWևWֈW։W֊W֋W֌W֎W֒W֓W֖W֗W֚W֛W֝W֞W֟W֠W֡W֢W֣W֤W֦W֧W֨W֩W֪W֫W֭W֮WְWֺWּWֽWWWWWWkdonegVhViVjVlVmVnVoVuVvVyVzV|V}V~VրVցVւVփVքVֆVևVֈV։V֊V֋V֌V֎V֒V֋cDThe entire Section 7.4.15 including subsections needs to be revised.d91g2220wAccepted{k) done 2006/02/02 2006/01/09VְcSection 8 has several inconsistencies. Not all commands and events rae defined. Service IDs are not appropriate and parameters for all primitives have not been updated appropriately.d96g2410wAccepted{k) done 2006/02/02 2006-01-04ֱ@ֲckE Peretz Feder^ Editorial_102`46a8.3.2bAdopt the follwing textc Clarify 8.3.2d100g2227iPeretzjAeMIH Function message are used to discover MIH Funcation capability in the peer MIH Function entities e@AR  33  33   33d  33RpMay need to change the section heading as well. The current MIH Function Messages title seems more appropriate. Leaving as is for now.wAccepted{e) editor disagrees 2006/02/02 2006/01/09lE Peretz Feder^Technical, Binding_103`40a8.4.1.1bAdopt the following textcClarify 8.4.1.1d102g2228iPeretzjt@bBubv@wbBDcAxbAcAvAy@bACz@bACE{@bAC|@v}@bApcր@ցbBփbօbAvֆbBDևbAֈEbA։bB DC֊@֋c֌@֍bACEGIKM!cA֎cAh֏@bA5C'E(G)֐@ bA*C֑@+v֓@bA.C1E֔b֕@J֗@6֘cA֚@>vk֝dA֟@9֠b ֡v֢@֣@֤c֧c֩@֪_4֫@֬c֮@֯@[ְbAVccVcVcpiniWoW։W֖WֽWintheresponsethereisnoneedfortransportoptionschangֽVincludes}WinformationiWiskWoWֽWWWit'sֲWjob։WkeepWlayer}Wlayers}WleavingkWlevel}WlinkiW}Wllc}Wlocated}Wlogical}WlookֵWֺWlower}Wlowerlayersthesearethelayerslocatedatosilevel2and}Vmac}WmachineWmacroiWmakeցWmarathon։Wmarathonjobinaddingtheies։VmaykWֲWmayneedtochangethesectionheadingaswellthecurrentmkVmedia}WmessageskWmicroiWmihkW}WֽWmn~WmobileiWցWmorekWmovementiWmultipletWneedkWֲWֽWneedsֲWWneighboringiWnetworkoWցWnetworksiWnoֽWnodeiWnotoW֒WWnowkWWoptionsֽWor}WDppspecific}Wspecification}Wstandards}WstateWstatemachineisnotapplicablefor802.21andthiscommentVsuch}Wsupported}WtֲWtechnology}Wterm}WterminalցWtextֽWthatoWtheiWkW}W~WցW։WֲWֽWthepictureneedstobescaledotherwiseit'sverydifficultֲVeferredmultipletimesalreadytVthroughout~WtimelyiWtimestWtitlekWtoiWkW~WֲWWWtookֽWtransportֽWue~Wumts}Wuses}WveryֲWwellkWWv1֐W֡WWW1clarifysubnetrelatedies֐V1locationinfocouldbeusedasanoptionalparameterV1performinghandoverassuggested֡V16tW2xW։WWW2.2։W21-06-0401-03-0000։W21-06-0477-01-0000֒21-06-0482-00-0000֜W21-06-0485-01-0000W21-06-0494-00-0000ֵW27֥W3xWW33aֵWֺW