Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0G)@0mation@/c@00tytheieee802.21mustdefinehowt@@00agraphrepeatswhathasalre@@0@0ragraphrepeatswhathasalre@@0andotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@  33    33>vw@A> 33  33j 33>clearMarkedh as XML" , ^i Subir DasjmRejected{ 2006/04/3030SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDec+67y:#I3 "Z;;G&Gy- 11/16/2006=w C;aTjx.;PkaTlPm_pwlaTsjt`Tuiv2PvATwDmviPx}bTykvq~zaTyPui_ ` PN %M %2I @EJOTYACXbmwBDa@EzJyOtUi[fBd|X||}q !A!VDEF(LIST3LISTA3Editorial Technical, Non-binding Technical, Binding3VDEFA((A!VDEF(LISTLISTAMember Observer OtherVDEFA((A!TVDEF(LISTLISTAApprove with no comments Approve with non-binding comments Disapprove with binding comments Abstain for lack of technical expertise Abstain for lack of time Abstain for reasons detailed in a comment field Comments only; no voteVDEFA((A!-% VDEF(LISTzLISTAzAccepted Accepted-Modified Accepted-Clarified Accepted-Duplicate Rejected Rejected-Duplicate Superceded Deferred WithdrawnzVDEFA((A!Vt VDEF(LISTLISTDT-W X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   v  V<E NALL # ` ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^_`abcdef g h ijklmnoqFMPR$@` ABCdD^EvFwGxHyIQ>AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijkQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJ>@ Cj%7.hal e-iJ.hj -Ek. l`l -mFxrogermarkspQmarksprogermarksBRmarksBrogermarksTmarksrogermarks@Umarks@roger marksmarksroger marks( i marks!(!roger  marks"0#q#marks$"0$ marks( i marks!(!roger  marks"0#q#marks$"0$DTDT €Editor's NotesEditor's Questions and Concerns€AEditor's Action Items€A€A€A Starting Line #€A Section€A  Fig/Table# BA1BAj  !"#$%&'()*+,-./0234567j^_ `2a4bc d ijkmn.p+v"wx#y'{)€%€0€€€€1€€66leiOwang' *  wang * leiP wang wang ' leiQ wang VYwang VleiRwangwang YleiSwang wang leiTwang@nh&`wanghleiUwang5|cnarrow'WWnasyWWnashassametwoacronymsyVnasnetworkaccessserverVnasnon-accessstratumVnas-port-type<WnatureWneccessary(WnecessarywWxWWWfWWWWnecessitated]Wneed3WTWUWVWWWqWWWWWW W W!W-W9WvWWWWWWWWneedawayformiistotallthequerierthatoneormorereqUVneedmoredefinition/detailsontypeienetworkstandardstyVneedruletoreportunrecognizedieidsVVneedtosupportmechanismbywhichclientcanqueryanypoaVneeded~WWW)W0W>WOWhWWWWneedsWWWWWWW W=WLWVWWWWWneighborWneighborhoodWneithernWnet=WWWWWWW WWjWkWoWtWWnet-sap}WlistedVK 9@AOKA/A0@@A-A.@A,A-Cancel@A*A+@@A* ;X( `Before importing, Find the records eligible for proposals by this Clause Editor. Only these records will be affected by the import. ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoQ:ASort by RecommenderE'` iDT_DT`DTDTDTQÃY0?ÃY@@ÃYPAÃY`BÃYpCÃYDÃYEÃYFÃZGÃZ HÃZ0IÃZ@JÃZPKÃZ`LÃZpMÃZNÃZOÃZPÃaQÃa RÃa0SÃa@TÃaPUÃa`ZBUUX  w  $,.YesNo/,  , : AM PMf  HelveticaGenevaVerdanaTimesMonacoTimes New RomanArialCourierSymbol Courier New@ A PICT,alisNAMEMSPCFPTHA9Macintosh HD:Desktop Folder:Ballot#2:802.16.2 Ballot Data9MSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataalisC-`@@XA Comment List@@*AAbout Commentary@@PACreate Comment@@fACreate and Submit Ballot@@AGlobal Field Setup@@ AEditor's Layout@@AComment List for Printing@@ AComment List for Projection@@ACommentary Version@@@AReply Comment Layout@@ ASubmit Reply Comments   A Comment ListB   vor/ 11 against wRejected{l) none needed 2001/10/24»ETG3/4 MAC group^Technical, Bindinga6.2.XbFAdd new ARQ text found in document 80216abc_01/75 to the WG document. d339g2541wAccepted{k) done 2001/10/24 2001/09/11¼E TG3/4 MAC^Technical, Bindinga6.2.xb'Add a standalone NACK feedback message.d340g2542vneed accepted textwDeferred{l) none needed 2001/10/24 2001/09/13½E TG3/4 MAC^Technical, Bindinga6.2.xb Add RNR feedback message for ARQd341g2543vneed accepted text 2001/09/13D$aGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #{ Document #Report # B A € € € €€ €   G!MKe!MKG*fQjugD€QASDocument under Review€XAYLetter Balllot Number€^A_VoteaGlobal Field Setpb // etpb // etpb // etpb // tpb // b // b // d Setpb // Setpb // tpb // Setpb // b // ld Setpb // d(2) Save Data to Filee(3) Email Data Fileail Data File54 RB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMnD a w n w  $,.YesNo/,  , : AM PMo  w p w  $,.YesNo/,  , : AM PMq  w r w  $,.YesNo/,  , : AM PMs  w t w  $,.YesNo/,  , : AM PMu  w z w  $,.YesNo/,  , : AM PM{  w  D^"M1,,./: AM PMYyTtNnFfNALL OHTMLP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , AXLS Sheet1X5CMY m]oApFfWyHCB-wang., .lei]} A1FPTH=RPTH NAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9NFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9OFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A10FPTHXRPTHNAMEMSPCMSPCA2NAMEANumberLastFirst.USRRPTHANumberLastFirst.USRA19uFPTH^RPTHNAMEMSPCMSPCA2NAMEANumber_Lastname_FirstnameRPTHANumber_Lastname_Firstname ot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisVDEF(LISTLISTVDEF(LISTLIST(:K?@MRS Y!^"CAStartup scriptEQADelete Empty RecordsE@ @b*QA Show VotesE@@H-Already voted; submitting additional commentsQASort by Page/LineE'` _DT`DTDTDTQASort by Comment OriginatorE'` DTDT_DT`DTQADelete All RecordsE@ @b*QADelete Abstain CommentsE@ @HAbstain for other reasonsQAShow Editor's ProblemsE @'`@n* _DT`DTDTDTQASort by Comment #E '` dDTQ8 €Bied in recommending rejection on grounds of incompleteness or lack of a specific change request. (3) When you are finished entering replies, look under Scripts and choose "Find Marked Records". This will find the records for which you checked the "Marked" box. (4) Put your name in the "Recommendation by" field of each reply {for a quick method, see Appendix below.} (5) Under Scripts, choose "Export Clause Editor's Proposals". Choose the file type "FileMaker Pro Runtime Files". Enter a Cfile name of the form "BallotNumber_LastName_Firstname.USR", where "Name" is your name. (6) Email the exported file as an attachment to: --------------- Appendix: Using "Replace" in Commentary You can replace everything in a particular field over a batch of records. For example, clause editors might not want to type their name in the the "Recommendation by" field each time. Here is a solution to the problem illustrating the use of "Replace": *Finish entering your data. *Find the bacAEditor's LayoutB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMYesNo/,  , : AM PM9 Dp=u Av 2 72w27+-f3%:EAFAGA' Submitted by:€QASDocument under Review:UFirst (Given) NameVLast (Family) NameWBallot Group Membership Status:€XAY#Letter Ballot Number or Ballot Code€ZA[ email address€\A] telephone€^A_Vote:`(1) Create Comments€aAHCreate and Submit Working Group Ballot or IEEE Balloting Center CommentsH@AR  33& * Rg2*t {EQFAImport CommentsENALL OTABS# ` ABCDEFGdH^I_J`KaLbMcNOPQRgSiTjUkVmWnXpYvZw[x\y]{^_`abcde f g hijklmnoQGA Email fileE)?@ @A owner-stds-802-16@majordomo.ieee.org The comment file name should include the Letter Ballot Number and D AdB^C_D`EFaGbHc $'()+,0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⳃⴃⵃⶃⷃ⸃⹃⺃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ 'f€aA Create and Submit Reply Comments @A*  33*€APLEASE FOLLOW THESE INSTRUCTIONS EXACTLY OR EXPECT TO HAVE YOUR INPUT IGNORED. (1) Read the comments. You will probably find this easiest if you use the "Comment List" layout. You can choose it from the upper left corner of this window, or you can use this push button: (2) When you want to respond to a comment, check the "Marked" box at the top of that record. Then fill out the following fields: Recommendation: Proposed Resolution: Reason for Recommendation: You are fully justifing the buttons:€gng the buttons:€gng the buttons:€gg the buttons:€gicking the buttons:€gicking the buttons:€gowing steps by clicking the buttons:€ging the buttons:€gg the buttons:€ging the buttons:€ge buttons:€gbmit Ballot Filef9Proceed with the following steps by clicking the buttons:€gO+ A#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# cBl#[  bl[##KK##;;# Bmv#+  @iv+# >j# Dkv# 8w5 €\]Page€^A_Line€`A aSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A &'()+ €A €A €A€ARecommendation@@ByProposed ResolutionReasonSee reply details€A Fig/Table# BNA^  !"#$%*,-./0123^^_`u EDE^ "Technical, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, BindingG OKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !""Technical, Binding" comments are permitted only with the vote "Disapprove". You may submit comments of type "Technical, Non-binding". Please correct and try again.H) W()=0 W ABCDEFGHIJK^L_M`NaObPcQvlEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf7# w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM     w  $,.YesNo/,  , : AM PMw w  $,.YesNo/,  , : AM PMf"$  w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PMf w $,.YesNo/,  , : AM PMf3IC dd5BDe5Bf#= q w $,.YesNo/,  , : AM PM     w $,.YesNo/,  , : AM PM          w  3  $,.YesNo/,  , : AM PM   {cTZbo|h[++ \_l)]l+ ^`l$)g_.?nAEditor's QuestionB GpA Editor's NoteB GvAResolution of GroupB GH vwADecision of GroupB GxAReason for Group DecisionB GyA Group's NotesB G{AEditor's ActionsB G€AGroup's Action ItemsB G€AEditor's Action ItemsB G€AVoterFirstNameB G€A VoterLastNameB G€A VoterEmailB G€A VoterPhoneB G€A VoterStatusG€A VoterStatus3m  ^ 3 $,.YesNo/,  , : AM PM_   `3 a d3 e3 f  3 g  3 t  3 u   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PM#39 XX+ASubmit Reply CommentsB  a   w   w $,.YesNo/,  , : AM PMf w w Aa#8 F mM5ft GM5ftM5ftGOC`E 7OC`EOC`E7 W   W   W    ÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷{xBKA Enter commentEQMAImport Global DataENALL # @ A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcdefghijklmnopqQNAExport CommentsE:NALL OFMPR$@` ABCDEFGdH^I_J`KaLbMcNQkUmVnWpXvYwZx[y\{]^_`abcdefgh`DTDTDT A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcde0+A^technical@`@ b2biterrorrate@a1.4@changetomihgetstatus@(eitherdefineitinthisdocumentoraddareferencetowher@+makedefinitionoflinkparameterlistdefinitionconsistent@"name@lrevisefiguretodistinguishl2transmissionoverdataplane@toimprovethereadabilityofthetextitmaybettertoprov@cbecause@in@mihs@Yreject@Dthat@thereisnoencodingschemeforthesetofcommandids@jagreeaboutthetermbeingundefineduseofl2isself-refer@being@Fvannexisjustanexampleitdoesn'tmeanthecommandisn'tn@2curenttextseemscorrecteditorialnotshouldnotbeincap@notclearifweneedre-registrationprimitive@ € p@itisnotclearwhatisthedifferencebetweencommonandot@linkparametertypedefinitionsisinsufficientandneedsto@not@overload@repeat@text@;u@QAAExport Full RecordsEOFMPR$@` ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^QCAAbout CommentaryEDQEAExport Vote & CommentsE6NALL OFMPRV D@]W@gFD@ @D@  ] W@ g F E@D@]W@gFFD@F$@`V0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsical, Bindinghh' Cw# ,v # 0x #  2y # s 2 @BBA0 0^_`ab c dijkmvwxy€€€             XXXX$XXXX2 X  X  X X& X'X(X)XXXXXXXX!X j   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   h stanwood# >S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM(s%jAResolution ProposedB GkAReason ProposedB GmARecommendationB Gnndation 1B Gn1O RR 3  $,.YesNo/,  , : AM PMU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW w $,.YesNo/,  , : AM PMX w $,.YesNo/,  , : AM PM)@B@2@I@E@M@_@R@ @P;;;$P;$P;$P;$P;$P;$P;$P;$P;$P;$P;$P;$P;;;;;$P;$P;$P;$P;$P;$P;ng @$P;A@@@cJ@c@M @ @3P;@3P; @3P; @3P;7WNWWWYWbWdWeWhWWWWWWWWWWWWWW)W/W5W8W=W>WBWDW`WhWmWWWWWW?WgapWWWW WW#W$W%WgenerateWgenerated4W6WWWWgeneratingWgenericWgetOWWWgetridofdashthisisaproblemallthroughoutsection6.2OV4/ RM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMBkS-X bWmkwj,ACgEv@!Sl€`zrAPFQKRPSUTZUBN@VhA~@M@LZ<>C @@@FIH@JQ3^&vmBD€Qd9naD@Xbm{ACEe@EJoQTYB@X|CE@€ JOTYAC@XbmwBD@a@EJOU[B@|J& JQ 3 $,.YesNo/,  , : AM PMS   U   V   W   X 3 $,.YesNo/,  , : AM PMY   Z 3 $,.YesNo/,  , : AM PM[   \ 3 $,.YesNo/,  , : AM PM]   ]   No/,  , : AM PM]   1 RG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMw+#,v# 0x#  2 Ma bc dijkmvwxy!€€$€2'&()% @@@B s@A 3  $,.YesNo/,  , : AM PM77777777 7 7  7  7  7 7 7777777777771xy{€€€€€j77777777 7 7  7  7  7 7 7777777777771        Y7 ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   6" i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv    €Dtch of records in which you want to replace a field. *In browse mode, and put the cursor in the "Recommendation by" field. *Under "Records", choose "Replace". *Choose "Replace with calculated result". *In the box, write, in quotation marks, your name. Click "OK". *Click "Replace". @Af  ww    ww  ww  wwfSet up an email message for meGo to "Comment List" layout BnA€ ($EQiaobingFXieGMember^ Editorial_5`1a2bre-order referencesc References not ordered properly d2022g4671k  2006/11/16 2006/10/20'EQiaobingFXieGMember^Technical, Binding_61`48a6.3.6bEnhance the TLV information retrieval to allow the client specify what access networks/PoAs should be included in the response.c1 2006/10/20 2006/10/20im4 2006/04/24n rd(2) Save Data to Filee(3) Submit Ballot Filef9Proceed with the following steps by clicking the buttons:€gAFile name must follow format: BallotNumber_Lastname_Firstname.USR (Extension is .USR) File format choice must be: FileMakerPro or FileMakerPro Runtime@AR  33  V  33r  R€tAWORKING GROUP BALLOT: Send email to: using the subject line: Make sure to: Attach file created in (2) Send manually if this button does not work.@Az    33%  &  33M  h  33z€uA €vA wShow All Comments€A@IEEE SPONSOR BALLOT: Upload using IEEE Balloting Center web form@@A*    33* not work.@work.@   337  R  33fPI3Import Full RecordsExport Full Records Enter commentExport Vote & Comments Email file Startup script Delete Empty RecordsDelete Abstain CommentsDelete All Records Show VotesShow All Records in OrderSort by Comment #Sort by Page/LineSort by Comment OriginatorSort by RecommenderShow Editor's Problems Assign Editors#Mark Found Records%Unmark Found Records'Find Marked Records)Import Ballot Comments+Export Comments-Import Comments/ Export Clause Editor's Proposals1 Import Clause Editor's Proposals3Export Group Resolutions5Import Group Resolutions7Export Editor's Input9Import Editor's Input:Import Global Data< Help WebLink>WirelessMAN WebLink@Export IEEE XMLCOpen Reply Comment FileEAbout Commentary<AKEG  7   :UVWQNF89=>>9=>gP:@K79@<E Q@ Q*E@uD QFGB{K@(MNxS@W@ZC[E\G]I^K_M`OaQbScUeW  A} !LISTAqVDEFEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEfterW=WcWWWallWalleviatebWallocationbWalphaWalsoWWWalternativeWalternativesWalthoughWbWalwaysbWanWareadWasWWcWWatW(WOWattributesWbandWbandsdWbandwidth(WbaseWbeWWW(WbWcWWbelowbWcWWerL> `Z   [w \ ]  ^ w  $,.YesNo/,  , : AM PMew h 3  $,.YesNo/,  , : AM PMi   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   ,  , : AM PMd   $ ANU#OV#V+X^5)SY{cTZbo|h[ +' \_l) ]D+b ^`l$)C_B+``al)a,maTbc -6cI dd De ]f)aTgvhYi< A_.^ -^; Pbj0=bi.  _l -d @/Tcj4A6XZB% K%[%K% %\%0E>]^% 7%e%D€B G€ AEmail ToB G€ A Email SubjectB G€ AEmail ccB G€A BallotNumberB G€A DocNumberB G€ACommentary VersionB G€A ExportDateB AbG€A Comment DateB G€ACommentary Version NotesB G€ACommentary Version DateB G€AMarkB G€A XML OutputB  B  " 0000000 87654321 "& & &""&""& ""&b&"" F€A Comment Type€ASuggested Remedy€ A Starting Page Number€ACommentXCreate CommentZDocument[Create another Comment\Create/Submit Ballot]In WG Ballot, "Binding" comnents are those which form the basis of a "Disapprove" vote. IEEE Balloting Center processes all Technical comments identically.€^AeShow All Comments€hAiSection€jAk Fig/Table#€lAmStarting Line # B?A6 6^_`abc€` a b cdX)*+,-.X()*+,-.X,-.XXolutionARecommendation byCRecommendation:EReason for RecommendationHEditor's QuestionsKEditor's Action ItemsN Group's Notes @B=Aalbert@Cperetz@uxiaoyu@Plee@nadasxie@V member2observer@ W^bindingpeditorial@non-binding@]miheventunsubsc@config@eitherdefineitinthisdocumentoraddareferencetowher@eitherre-dothemappingagainstmihprotocolpdusorremove@event@events@fa@media@name@pdus@reorgthesesectionsasfollows@sections@specify@tlv@type@updatetable32toreflectthechangesmadeto6.3@c6@brokensentence@come@common@doesn't@entity@field@ie@independent@late@linkgetparametersprimitivemissingintable17@narrow@partner@related@system@thereshouldbesomeexplanatorytexttofigure20@type@whatistheservice-info@k€tbl2@2@E BD 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 sBlt# #  al#< cl<#n  bln# Bmv#  @iv#R sj{R# Dkv# 8w#c,Cjvc# 0x#S  2yS# 2#C 6{C# In#_ qp_# 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#6 6#M  M#} d}# ## ## ##X X# ^#J  _lJ#t  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€            5 / 1  3       6  $ "  & , ) +-*,6{7TypeReason k b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PM-dG | w  $,.YesNo/,  , : AM PM}  w ~ w  $,.YesNo/,  , : AM PM  w  w  $,.YesNo/,  , : AM PM  w A^a):|+=9}R~T=b=NR?+M^ance'd303 2001/08/28G6AReply Comment LayoutB U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]     [A, HH HH*<*G!!!!!!!!1111111111 11 11 11 9999 99999999BBBBBBBBJJJJJJJJJJJJRRRRRRRRRRZZZZZZZZZZZZ ZZ!cccc"cc#cc$cc%kkkk&kkkk'kk(kk)kk*kk+ssss,ssss-ss.ss/ssB0{{{{1{{{{2{{3{{456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmZ\ Cnopqr!!s11tBBuRRvccwssxyz{|}~D[] Ek0>nk&8n]n]n!=700UnUnUfa&fH!1fQ!H,bH,Hn\X8FU7=nXnH7%fQH 7k=8HnX10kHbHHgfn=\HX7X8HHf\]?no`_`_`_`_`_`_`_`_`_`_`_`_`_`B]n` [    `    `    `n&0n4WUfZ _ZZZ._ Z)$')d)$')d\^ G)')$h#`` ) )B)y}_ Z ' ' Dyy3sy~[_  )  ) B|uv7~qu|t_Z ( ( Brz}rs9|pr}up|_ ` ) ) Bzprypq~<yppy~pps`_ ' ' @rpp{upp|?vppuvpzZ[ ) ) Ezpt}rppyAsppr}~pr_ _ ' 'Bqp|ypvB~qpyxpz[ ` ) ) BHxpvups@|ptqpr_ Z # #@qp~}rpq~Iypq|ypz_ _E BEB`E BEBmE 'BEBmxpvyp|SX&&Xvpqpr` [  A Z Zqpy8=SHHspzZ _  @  `  `xpv,5^kn~qpr_ [[  _Z`l[  __Yo[ 6__[oqpqrpsbfS=X|pvzpy_ _ ' ) Bxpq}wpq}=]_ IXU7Uyp{zqppq`_ ) ' Bqppq}~p{=TW\fvpr}qppxZ [ ' ) DwppsspxfgT0spw}qpq`  _  '  'A~ppszpu08]n%7~qpp~}qpxZ _ BBEBm BBEBm 'BBEBmvpsppsHQH|ps}qq` [ `  ` _~psvq}Dyz~sx_ _  Z  Z [Jvu|{9to_Z_o__[Z__[^o__[Z__[^o_[^Z_`Z^o~v }~o_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`m`                                                                             @lBB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB^` K@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@B_ fXX]XfkJ78H7k=aXH 007U!,7kX8HXU7TT8X7TX77XXXf77`QHU8bk1TnaXfgWU77L7%7XX\ n17&7nbT] Xb!78=HUUXWUTX7 X7TY07=\7Xk Q%QX777b]1n=5n7H8Q!8nn_a M7!Qn=!H% 7TX,XfUXn,7,a bHb7jn &HU\TX$WT878gnn8H W8L7AUXHn8nH,H88N 7X&78=;XT%X7=7&0&0n, n!7HX00T(TXfnn777 H8& X7T7778n XTX778Tbkb H=X!`b O=T TXM*HU7T7&Q= 7Tn7%UW& XTX.7,n7&H%H8,X7gn7 TXT7A78nXH&=TXf7&Q7 PXTX 8n7]&]n7TX8jUQ TXU=n7\gn3n7XHUk=7,+U XTWUH87nn3X8WU77f78 TXUn= 7ac QU7U78&QQ XUX bfb7==nX17!8717W177&7nUT TWTH8fX&k8UUn7771 XUX77j&W7 WX bR8nH7 TXT\7&XUkH8U U77TX XTXn%88=&gC!\7 WX 77nXTUnfXTagWUTgWUTi)())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())(be S))())RZ                                                    B'S66SmB3BmK63BmVEBBPE.R8|o" *e VK S) i )}=}t<  K o  e   '~tFxy}qx ZV V)Pe2 6V R `vs|zWX!Q{ps}qq  <JR 3` )  A~psuTq}84n]H5}qpp}}qpx  ) _e Z ' o xpsppr5dngspw}qpqm  l <. Vqps~yptk]gX=upqzpy  I: . i J  B )3Sxppq}spwU7fU7xp{zpr V _  Z` l  ;   6qppq}}p{W=ef]{puzpz o  oZ  `2  "  `xpX $%       !ACommentary VersionB ( a w hh h h h h  h hhhhhhhhh!hh$XX,XXXX)X+X5X3c Uq}wpq}nf]1&}qpr 6  <`  ' _m N  */B 6qpqqpsH7Q78spz  lZZ ) `6   ' @_ xpuUQFupqpr V  `_  Z F  ) B qpxLxpr}zpz B ') Io  `P  " B xpwzqp{Q{puqpr BB' B e39 *@ qp~}spq}S}qppqyxpz@;)Bm e 'B  VzpvvpsQspps}qpsE '' R) Zi m   B; rp}zqppuUuppvvp|S  _6IN3_ )`EBmO '_ zpt}sppxQxpqz~ppt `R V)*NO @BYm  B 6rpp|vpp{P{ps}vp|6  ;  oB  E@` 3_zpszqq}L}qv|t oV NEBBZ m <rz}ssCtz~oI)"Ie6)6_cBB@@B@__@BlBB@l<)-V|vui [ w  $,.YesNo/,  , : AM PMA#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# c^_#  _l#  `l#m  av CgTgvh ivTjxivPk#TlPm&3Tn{&h3Po pDw6YTqp&3`Pr nTsj{tTuivcPvXTwmvPxTykvq~l6V~%AAbout CommentaryB\   A wB w I N w  $,.YesNo/,  , : AM PMO W  $,.YesNo/,  , : AM PMX $,.YesNo/,  , : AM PMPMPMPMPMPMPM   $,.YesNo/,  , : AM PM  w ` D .orgl>.;tf ZU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMk, w  3 $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz   {   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     rksa_2Wj m   n 3 $,.YesNo/,  , : AM PMo   p  w $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   '   B@\[)!r S // €TA€UA€VA€WA€XA YType€ZA[Suggested Remedy€\A ]Starting Page #€^A _Starting Line #€`AaSection€bAcComment€dAe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yA=AB=AB[Ab  !"#$%&'()*+,-./012345b& v   $,.YesNo/,  , : AM PMww   3 A0@*E0:@F {G0Z=' QkS%26U%92VLWiyl XU%92VLWiyl XXXXXX9 T BcAJ  !"#$J €€€ € €€ €      AGlobal Field SetupB   €€€ € €€ €           " # J  3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMs; VOTEREMAILVOTERFIRSTNAME VOTERLASTNAME VOTERMEMBERID VOTERPHONE VOTERSTATUS XML OUTPUT^abcgijkmnpvwxy{_`d    d  ^_`abcgimjkvwxy{p n!"#$%&'()*+ , - ./AMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line Number E !LISTAa) awaiting resolution b) awaiting missing input c) instructions unclear d) confer with resolution group e) editor disagrees f) pass off to other editor g) didn't have time h) defer to next round i) to do j) in progress - k) done l) none neededVDEFA((A!1>VDEF(LISTLISTAEditorial Technical, Non-binding Technical, Binding Technical (was Editorial) Editorial (was Technical) Technical, Satisfied (was Binding)VDEFA((A!VDEF(LISTLISTAMarkedVDEFA((A Comment TypeBMembership TypeCVoteDRecommendationFEditor's ActionsGComment Type/GroupHMarked`AFMRLFMRLAbb7AFMRLFMRLAdBFind DuplicatesC ReplyComments`lP <zReason for Recommendation{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes8Note: Group may also edit and export Comment Type above.€ADocument under Review:€ABallot Number:€A  Comment Date€A€A  Fig/Table# @BA5BAj  !"#$%&'()*+,-./0123467j^_ ` a bcdi"j k&m$n)pvwxy,{€€+€1€/€3€5€€6@@XB s@p.D/A First NameB GA Last NameB GAMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line NumberB GaASectionB GbAChangeB GcAReasonB GdAComment NumberB GM9999gACounterB GL5092iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. g! QEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl#.  .#  al# bl# 8w#,v#  2y# 2#v 6{v# In#f qC>pf# L WE@@MarkedQYAExport IEEE XMLEOTABS D[@!d$@`@A14[p 0 h[[ [[ /0 h[p / AQ^AOpen Reply Comment FileE ! FMPRQ'`QdDTQAzHHddE(HH(d'`zA'dE7*`'`+ dDTQ] w  $,.YesNo/,  , : AM PM  UU? €Ad?2     _` a ^@"7 c>gt;Z<lt;Z b>gt;Z<lt;Zd W2&&Zgt;>Zlt;<Z:GC€A VoterMemberIDB G€A ReportNumberB G€A FigTabNumberB G ballot@wirelessman.org IEEE 802.16 Letter BallotP802-21-D02-00.pdfdoc 21-05-xxxx-00-0000-Resource_Reserve.ppt 21-05-0352-00-0000-Event_Report.pptQphilips barber00.pdfrmAComment 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 DataIE`'cA(@+cJ1cA2@!3@5bA7@8v:@<@{=c>@@@BvPC@DcBkFbHL^OFQc%R@xvASvT@VFW@XcZ@[vA|]w^@_bA}`@a@jb@dwe@Xcf@gvA7h@&ic8j@nk@tlcAgjBvB&mvAnc5o@acHp@r@bs@jAetcuvAv@!x@#bA&z@;c8{@Q}c.~@dvA22@|bACbAbEc^cA@@1jconductWconfigurationNWconnectedWconnectionWconsecutivedWconsiderWconsistentlyWcontainsNWcontributionsWcorrectoWcostWcoverageWcreatesWcurrentWWcurrentlysWdataWWdecidelWWdefinelWWdefinedWWWdefinesaWdefinitionWWdefn'svWdeleteW!WdeliversWdependingNWdescribeWdescribed3WXWdescription[W^WWdetailXWdetailed3Wdetailedprocedureofmihfunctiondiscoveryoverlayer2is3VdetailslWWdeterminedWdhcpNWdhcpv4NWdhcpv6NWdifferent[WlWWdirectlyWdiscoverlWdiscoverylWWW3WWdiscrepanciesoWdoesWWdraftnWWdynamicNWeWNWWeachlWWeditorWeditorpleaserunspell-checkerV/E Pro 3.0 - 4.1F!"HPro 5.0 A ?G USENGLSH.MPR?GUSER.UPRitorial_10`12b'At this time it is more for informationc/This is just a test comment given as an example 2005/09/20e^Technical, Non-binding_30`2a6bRemovec Example 3 2005/09/20f^ Editorial_40`20a5bRemovecThis is an example 2005/09/20gEAjayFRajkumar^Technical, Binding_25`1a5bRemove the sectioncThis is another exampled2 2005/09/20 2005/09/20hEAjayFRajkumarohcsub-section5.6.1.1mihlinksapisundermediadependentsa5VsubmitteduWsubscribe:W;WWfWsubscriberWsubscription1W?WAWWWsubscription/registrAWsubscriptionsWsubsectionWWfWW'WWsubsectionsWsubstituedWsubstituted%WsuccesspWsuccessful/failureqWsuccessfullyWsuchW'WjWWWWWWWsuddenlyuWsuggestpW#W&WWWsuggestthatthestatuscodehaveadditionalvaluesforcatepVsuggested$W'WsuggestionsWsuitableWWsuitableamendmentsmayberequiredtolinklayermac/physpVsuitesWsummarizedWsupportWW>WxWWWWWsupportedUWWWgWWsupportedcommandlistgWsupportedeventlistgWsupportsW^WgWsupposedW-Wmments" script. It had not been updated in 1.1 to match the new ; @ @@@@%† sreemanthula)(†"kenichi@.-†Dtaniuchi0 @ @ @EGolmieFNadaGMember^ Editorial_90`55a7.3.20.2b"Fix inconsistency throughout draftc[Inconsistency between name in description and Name columns for Link Data rate or Data rate.d2257g2277 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_91`41a7.3.21.2bAdd a row for PERcXPER is listed under the description column, but not listed as an item under Name column.d2260g2279wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Binding_91`36a7.3.21.2b;make definition of LinkParameterList definition consistent.cYLinkParameterList definition is inconsistent with its other definition in section 7.3.7.2d2259g2322vin section 7.3.7.2 and the table below it change LinkParameterList to LinkParameterNameList. This needs to be changed in all places. There would be implications of this in section 8 as well.wAccepted-Modified 2006/11/166/11/14umn.d2260g2279 2006/11/142.2 2006/10/2010/20XcCLink Capability Discover primitive missing in Table 16 and Table 17d2233g4723k wAccepted 2006/11/16 2006/10/20Markedt16YEQiaobingFXieGMember^Technical, Binding_72`49a7.2.2.2b-Add Link Get Parameters primitive in Table 17c1Link Get Parameters primitive missing in Table 17d2235g4724k wAccepted 2006/11/16 2006/10/20Markedt17,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bfvbmovesub-section5.6.1.1mihlinksapundermediaindependen5Vmovetableinsection8.3.3.4tosection7.3.2.2andaddatVmovetableinsection8.3.3.5tosection7.3.19.2andaddaVmovethecontentof6.2.2.1into5.4.2BVmovethemult-hopoperationdiscussiontosection8andchanVmovetypehrdtlvmihfidandtypehdrtlvsessionidfromtzVmoved WmreplacenWmreplacethetextwiththefollowingnVmstlyWmtu`WmuchWmult-hopWmultipleWFWWWmustTWn-layervWn-uservWn-whateverWn/aWnaiuWomment 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 Peretz7fESubirFDasGMember^ Editorial_74`40a7.3b Section 7.3.1 should be "Link Event Discover "(as #1 in Table 16). Accordingly, Section 7.3.1.1 and 7.3.1.2 should be Link_Event_Discover.request and Link_Event_Discover.confirm, respectivelycThe Link Layer Primitives should have an additional subsection to group the request and confirm primitves reflecting the order described in Table 16. This can prevent conflicts appeared in the table and description. d2241g2465 2006/11/16 2006/10/23T15gESubirFDasGMember^Technical, Non-binding_189`1aA1.3bAeChange title to "Network-initiated Handover from 802.21 to 3GPP" or add subsections, similar to A1.4.e@A> 33 A 33>cSTitle not clear of which type of handover the procedure is describing in Figure 32.d2390g2467vABChange title to "Network-initiated Handover from 802.21 to 3GPP" B@ similar to A1.4.e@|?]wAccepted-Modified 2006/11/16 2006/10/209a6.3.7.1bfix the referencec[8] is wrong reference to RDFd2200g4728iYoshihiro Ohba Extended schema that is optional and may be vendor specific" Since extended schema should always be vender specificd2198g4727k  2006/11/15 2006/10/20]EQiaobingFXieGMember^Technical, Non-binding_64`59a6.3.7.1bfix the referencec[8] is wrong reference to RDFd2200g4728iYoshihiro Ohba 2006/11/15 2006/10/20\EQiaobingFXieGMember^Technical, Binding_64`54a6.3.7b>Change text to: " - Extended schema that is vendor specific."cInaccurate text: " - Extended schema that is optional and may be vendor specific" Since extended schema should always be vender specificd2198g4727k  2006/11/15 2006/10/20]EQiaobingFXieGMember^Technical, Non-binding_64`59a6.3.7.1bfix the referencec[8] is wrong reference to RDFd2200g4728iYoshihiro OhbaingCEVivekFGuptaGMember^Technical, Non-binding_48`17a6.3b cf(page 46, line 48 as well) Include a formal definiton of "geographical area" or "network neighborhood"d2139g2229v At any location there is coverage provided by different wireless networks. Network Neighborhood is the area of interest in which the Network Discovery and Selection entity, seeks to determine the available coverage from different wireless networks.wAccepted-Modified 2006/11/16 2006-10-23Table-6EVivekFGuptaGMember^Technical, Binding_61`48a6.3.6bgProvide amechanism such that PoA can indicate max length of query response it can handle to the MIIS. cnd Selection entity, seeks to determine the available coverage from different wireless networks.wAccepted-Modified 2006/11/16 2006-10-23Table-6ible.mRejected 2006/10/31 2006-10-23ld be hard to use.d22g4709k  2006/10/26 2006/10/20KEQiaobingFXieGMember+vbthedescriptionsfortable15areinsection7.4thereforeteVthedetailedprocedureofnetwork-initiatedhandoverneedtoVthedocument21-06-0789-00-0000-adescribeshowmihcanpiggdVthedocument21-06-788-00-0000-miregistrationdefinestheraVtheencodingusesabitmapwherethebitpositionrepresentsVVVVtheiesmayberetrievedusingeitherthetlvmechanismoraVthemaingoalbehindtheinformationserviceistoallowhVthemeasurementsreportmetricsthataretypicallyusedinhVthemihfunctionintheuediscoversthemihcapabilitysuppqVypefieldshallbeonefouroctetsLVthevalueisanonnullterminatedstringwhoselengthshallFVtheir_WthemWWW@WKWthemih-link-sapWthenNWcWeWtherejWthereafter$WthereforeeW^Wthese2WjWlWWWWW"W8WmWWWWtitlegW Wtitles WSblastHWWWlaterWWxWlayer5WW^WbWmWqWrWwWWWWWWlayers>W?WWWSW^WWWWlayoutWleastWWleaveUWleftWlengthFWW<WMWVWeWWWWlength/typeWWWWWWWlinkparameterlistWWlistGWPWUW_WlWnWWWWWWWlistedWlistsWlittleWlower>W?WWlsapWWmaccWmachinewWmacnewpoaWmade9WmagementlWmainhWmake@WAW^WaWWWmakedefinitionoflinkparameterlistdefinitionconsistentVmakedefinitionsoflinkparameterlistconsistentthroughoutVmakethedefintionconsistentaVmakesWmanagementjWWmandatory_Wmapping6WmarkedWmay_WiWlWsW{WWWmaybe>W?Wg& ljBcover MIH protocol message, MIH function discovery and capability discovery may be performed at the same time by exchanging MIH Capability Discovery messages with MIH peers. Following subsections define each of these methods more details. @A> 33   33>kIn case of using layer 2 transport for MIH function discovery, MIH function discover and capability discovery can be performed at the same time. mAccepted-ModifiedvAUse Ronny's suggested text: The MIH Function Discovery procedure can aquire a list of peers that support MIH Function. In certain instances, the MIH node may have a preconfigured MIH peer. In order to know the services that are supported by a MIH peer, the MIH node performs MIH Capability Discovery. The MIH node may perform MIH Capability Discovery with different MIH peer in order to decide which one to register with. When MN uses MIH function discovery using MIH Capability Discover MIH pr^technical'W(W)W+W,W0W1W2W4W5W6W7W8W9W:W;W<W=W>W?WBWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYW[W\W]W^W_W`WaWbWcWdWgWiWjWlWmWnWoWpWqWrWsWtWuWvWwWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW W!W#W$W%W&W'W)W*W+W,W-W.W/W0W1W2W3W4W6Wd9zbspecify'WWmWWWWspecifysearchradiusinqueriesVspecifytwocostvaluesoneforhomenetworkusersandonefVspecifyinggWspeedWspellWsplitWsplitthesetwolinkidentifierssothatthetable26typenVsplittedFWstackWWWstacks4WWstage~WstandardWrWwWWWWstandards=W>WWstands"WstartWWstartingtWWWWWWstatewWWWWstatedWstates)W0WhWstatingWstationaryWstatusqWWWW WWEWaWWstatus2indicatesanerrordueEVstorediWstratumWstrengthWZWWstringFWWstructureWsubnWsub-section5Wsubject~WsubmissionWW!W"WdWeWhWiWjWkWlWnWpWqWrWsWtWuWvWwWxWyW{W~W@Marked$'01345689:;@ACDEFGHIJKLMNOPQSTUVZ[\]^_`cdefghiklmnopqruwxyz}~⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⵃⶃ⻃⼃⽃⾃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃ܃݃߃ !"$%&'*+,-./012356789:;<=>?ABCDEFHIJKLMNOPQRS7EQiaobingFXieGMember^Technical, Non-binding_21`40a5.3.2bwExplain how MICS is related to the Information Database and How come the Information database is a command service PoS?cwExplain how MICS is related to the Information Database and How come the Information database is a command service PoS?d2059g4690k v$Delete this sentence and the next...wAccepted 2006/11/16 2006/10/20Marked8EQiaobingFXieGMember^Technical, Binding_62`63a6.3.6.1b;Add TYPE_IE_POA_IP_CONFIG_METHODS to Reporting Template TLVc?TYPE_IE_POA_IP_CONFIG_METHODS missing in Reporting Template TLVd2194g4691k k v$Delete this sentence and the next...wAccepted 2006/11/15 2006/10/20Marked8EQiaobingFXieGMember^Technical, Binding_62`63a6.3.6.1b;Add TYPE_IE_POA_IP_CONFIG_METHODS to Reporting Template TLVc?TYPE_IE_POA_IP_CONFIG_METHODS missing in Reporting Template TLVd2194g4691k edR" under 7.2.2r layers?d4V|bbe'W<WHWeWfWhWiWmWoWxW~WWWWWWWW W WWW W"W$W+W6WCWDWFWLW[W]W^W_W`WaWeWgWlWmWoWqWwW{WWWWWWWWWWWWWWWWWWWW W+WbetwenWbi-directionWbimapQWbitRWSWWWWWWWWWWWbit5&WbitmapWWWWWWbits WVWblockWbothZWboundarydWJWbriefWbroadcasWbroadcastWbroadcastingWWbroadcastingmihcapabitydiscoverresponsemessagemayinclVbroader_WbulletWbutWby4W5WlWyWWWWWWWW WbyteiWcalledjWSWcancWlWxWWW W$W]WcandidatesWW{8vBAdd TYPE_IE_POA_IP_CONFIGURATION_METHODS to Reporting Template TLVwAccepted-Modified 2006/11/16 2006/10/209EQiaobingFXieGMember^Technical, Binding_195`1aA3b2update Table 32 to reflect the changes made to 6.3c8Table 32 is out of date after recent changes made to 6.3d2403g4692k wAccepted 2006/11/16 2006/10/2032aobingFXieGMember^Technical, Binding_62`63a6.3.6.1b;Add TYPE_IE_POA_IP_CONFIG_METHODS to Reporting Template TLVc?TYPE_IE_POA_IP_CONFIG_METHODS missing in Reporting Template TLVd2194g4691e Information database is a command service PoS?d2059g4690k  2006/10/31 2006/10/208EQiaobingFXieGMember^Technical, Binding_62`63a6.3.6.1b;Add TYPE_IE_POA_IP_CONFIG_METHODS to Reporting Template TLVc?TYPE_IE_POA_IP_CONFIG_METHODS missing in Reporting Template TLVd2194g4691_METHODS to Reporting Template TLVc?TYPE_IE_POA_IP_CONFIG_METHODS missing in Reporting Template TLVd2194g4691~ cthereshouldbesomeexplanatorytexttofigure200VthereforemWvWWWWWW!W'WrWtheseyWzWWWW8W]W^WeWWediaindependentsa2VthoseKWLWtitle1WgWtitlenotclearofwhichtypeofhandovertheprocedureisdgVtlv'W8WDW[WmWtlvsiWto'W0W1W3W6W7W9W<W>W?W@WAWCWEWHWJWRWSWTWUWVWWW]W`WaWbWcWeWfWiWlWtobeconsistentwith7.1.1needasubsectionin7.2.1forlWVtobeconsistentwithfigure15remoteeventillustrationon>Vtobeconsistentwithfigure18remotecommandillustration?Vtomakeitreadbettermovelinkeventnametothe2ndcolum@Vtomakeitreadbettermovemiheventnametothe2ndcolumnAVtopreventfuturemismatchbetweentheprimitivesinthetabeVtransportediWtwoEWbtlv'W8WQWUWnWoWqWrWzWWW8W:W>WJWNW\WeWWWWWeWto'W0W1W4W5W7W8W9W:W;W<W=W>W?W@WAWFWGWHWMWRWSWTWVWZW\W_WdWgWhWlWoWrWsWxWzW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWW W!W"W&W'W*W+W-W.W1W6W7W9W:W<W>WCWDWEWFWJWMWNWRWSWTWVWYWZW[W\W]W^W`WaWgWkWlWmWoWqWrWtWwWxW{WJclate1WlatencyWlaterWlatterWlayerfWWWWWW]W^WbWkWlWrWWWWWWWWWlayer2kWlayers>W?WWWW WSWXWWWWWleavingWleftW WlengthEWHWW<WLWVWWlengthoftypeienetworktypeshouldbe4octetsbecausena<VlengthonitsownisanambiguousterminologyunitoflengthVVlengthyWngapauVlink2W@WXWYWZWfWsWWWWWWWWWWWWWWWWWWWW WW#W'W5Wlinkcapabilitydiscoverprimitivemissingintable16andtXVlinkcapabilitydiscoveryisnotlistedinthetablebutpreVlinkdetectedoutoforderintable17ZVlinkeventnameincludessdubutdescriptionusespdusodoeV@WAWHccommon(WWWgWWWcommunicatewWWcommunicationW4WSWWWcomparativelyWcompared"WcompetingWWcomplete6Wcomplicates`WcomposedWconcatenatedEWHWconceptualSWconcernedWconditionsWconfict*Wconfig8WWconfigurationW&WNWPWWconfigureWWWconfirmfWWW WDWEWfWWWconfirmationuWconflictingWWaWbWdWpWdefinition(WDWRWSWTW^WyWdefinitionformessagenotneccessaryit'sacommonterm(Vdefinitions)WsWdeliversWdependtWdependent2Wdescribed_WfWmWdescribinggWuWdescription@W[WeWfWjWuWwW{WWdescriptionsnWdesecribesvWdetailedRWSWdetailsJWKWLWMWNWOWPWQWdetectedZWdiagramwW{b:EQiaobingFXieGMember^Technical, Binding_161`3a8.3.5bachange the MIH Service ID of "MIH Event Subscribe" and "MIH Event Unsubscribe" to Command ServicecE"MIH Event Subscribe" and "MIH Event Unsubscribe" are command serviced2359g4693k wAccepted 2006/11/16 2006/10/2025;EQiaobingFXieGMember^Technical, Binding_193`15aA2bWchange Category of "MIH Event Subscribe" and "MIH Event Unsubscribe" to Command ServicecE"MIH Event Subscribe" and "MIH Event Unsubscribe" are command serviced2401g4694k wAccepted 2006/11/16 2006/10/2031A2bWchange Category of "MIH Event Subscribe" and "MIH Event Unsubscribe" to Command ServicecE"MIH Event Subscribe" and "MIH Event Unsubscribe" are command serviced2401g4694k wAccepted 2006/11/15 2006/10/2031ssing in Reporting Template TLVd194g4691k HODS to Reporting Template TLVc?TYPE_IE_POA_IP_CONFIG_METHODS missing in Reporting Template TLVd194g4691k L/bsections2WWMWxWsecurityuWsee2WiWWseetheupdatedflowchartsinthe21-06-0530-00-0000dociVseetheupdatedflowchartsinthe21-06-0656-01-0000-wwman2Vseeking4WWWseemWseems[WselectWselectedWWself-containedcWsendWsenseWsentW7WWWsentence[WjWtWxW{WWWWWWWWWWGWJWWWWsentencesWsentense~WseparateFWWWseparatelyWserve^WwWservedsWserverNWWserveraldWservice7W:W;WCWhW~WWWWWW WWW"WgWmWvWwWWserviceamihposmayactasanVtWsolicitation~WsolutionWWsome0WsomethingCWsortWsortoutfontsinfigureVspecific\WrWWWWspecificationWWoMmbreorgthesesectionsasfollows2VrepeatWrephraseSWTWVWYWZWrephrasetolengthofthevaluefieldoftheieinbitsVVrephrasetomonitoringofpacketlossonthelinkoncurrentZVrephrasetoprimitivesareaconceptualrepresentationoffuSVrephrasetothemihfunctiongeneratesthismessagewhenitTVrephrasetothemihsapreducingtheinter-mediadifferencesYVreplacemWrWWWWWWWWWWWWWWWWWWWWWWWW,WXWbWcWWwiththefollowingthemihcommandsareVreplaceommunicationwithcommunicationVreplaceonewithfourmVreplacethearrowofiswithauni-directionalarrowVreplacethetexualbasicschemadefinitioninannexbwithtVreplacethevaluesizeofdelaysto2octetsandupdatevaliVreplacewithVVVVVVVVVbevent4W:W;W>W@WAWRWfWsWWWWWWWWWWWW WWW$W?WWW\WWeventlist1VVeventnameidVeventlistRWSWeldGWHWJWKWLWQWfigure0W=WfloatingNWOWfollows2Wfor5W<WFWfrom4W>W?Wfunction4W5W>W?Wgenerated4Whih:Whow7WPWi@WAWQWid:WidentifierGWidentifyFWie8Win'W4WCWDWMWincluded'Windependent2Winformation'W7WCWintegerNWOWintoBWip8WQWis1W4W5W7WFWMWPWRWit@WAWIWMWits1WlastHWlayer5Wlayers>W?WlengthFWlikeCWline>W?Wlink2W4W5W@WlistGWPWlower>W?Wmade9Wmake@WAWmapping6Wmaybe>W?WW4Ab7.2.2.22WtWW7.2.2.2mihnetsap2V7.2.2.3tW7.2.3.13W7.3W7.3mihlinksapprimitivesV7.3.1fW7.3.1.1fW7.3.1.2fW7.3.19.2W7.3.2.2W7.3.4.2W7.4eWWWW7.4mihsapprimitivesV7.4.1.2.4$W7.4.1.2.4effectonreceipt$V7.4.10.2WW7.4.10.4W7.4.10.4mihhandoverinitiateconfirmV7.4.10.4.4W7.4.10.4.4effectonreceiptV7.4.11eWW7.4.11.3W7.4.11.3.4W7.4.12.4W7.4.12.4.4W7.4.4eW7.4.7.1.3'W7.4.7.1.3whengenerated'V7.5W7.6.5.2.2FW7.7!W71W8WWmWW8mihcandidateaccesscompleteV8.1W8.3.2 W8.3.3.4W8.3.3.5W8.3.4JW8.4.1MW8.4.1.12WWWWWWWWWWWWWWWWWWWWWWWWWW+W4W@WEWFW>EQiaobingFXieGMember^Technical, Binding_39`11a6.1.3bkAdd, on the remote entity side, an event arrow from lower layers to MIH Function (maybe using dashed line).cTo be consistent with Figure 15 remote event illustration, on the remote entity side should there be an event arrow from lower layers to MIH Function? d2108g4697k v*Accepted, by labelling line as link event.wAccepted 2006/11/16 2006/10/20Marked14?EQiaobingFXieGMember^Technical, Binding_43`40a6.2.2bpAdd, on the remote entity side, a command arrow from MIH Function to the lower layers (maybe using dashed line).cTo be consistent with Figure 18 remote command illustration, on the remote entity side should there be a command arrow from MIH Function to the lower layers? d2118g4698k vLabel line clearlywAccepted 2006/11/16 2006/10/20Marked17line clearlywAccepted 2006/11/08 2006/10/20Marked17 in Figure 12d2093g4696J! 1cAg1. the title of section 6 is "MIHF services", and no figure has shown "System Management" to be an MIHF service. Kinda late to chuck it in at this point. 2. How is System Management function here related to that of MIH_NMS_SAP (see 7.2.3.1), for example, both can "initialize" and "reset" MIHF? 3. "Event Subscription" is part of command service already. gd2207g4684iRonnyjMove section 6.4 before 6.1. kYSystem management can be part of command service but different name is given for clarity.mAccepted-Modifiedv_Move section 6.4 before 6.1. The resolution of this needs to be consistent with comment 2104.wAccepted-Modified 2006/11/16 2006/10/20nitions: N-entity N-event N-layer N-trigger N-user Peer N-entity Remote N-trigger d29g4676k  2006/10/26 2006/10/20+EQiaobingFXieGMember^Technical, Non-binding_10`1a4bdelete the unused acronymsc/Unused acronyms: HLSI LLI MDI MII MIHS OUI PMD d33g4678k  2006/10/26 crelated1W7W`W~WWWW$W&WrelationWrelationshipWWmWrelationshipsWrelevantWremaining"Wremote)W>W?WWWWWW7WvW~WWWWremotedirectionandcommentsfieldsofmihnetworkaddress7Vremoten-trigger)VremotelyXWremoveWremoved#W&Wrenamed:Wreparingrepeatedly<WreplacedqWbWcWWrepliesWreponseWreport'WVWWW#WWWreportedWWreporting8WeWrepositoryWrepresentation[WmWW8WSWWWrepresentationsWrepresentedWrepresentingaWrepresentsWoWWreqeustrequestfWWWWW-WCWFWdWfWuWWWWWWWstringsEWHWsubscribe:W;Wsubscription1WsubsectionWWfWsupportedUW&kbmedia2WWW5WbWoWqWrWtWWWWWWWmedia-dependentWjWWmedia-independentWWjWmedia-specificWmediumWmics7Wmih2W3W4W5W6W:W;W=W>W?WAW`WeWlWqWvWWWWWWmihfbWzWWmiisUW^WWmimimumWmissingWWmlme2Wmn~WmobilesWyWWWmodel`W|WmoreGWPWlWWmove3W<W@WAWBWCWHWzWWmovecurrent5.3tobeaftercurrent5.4forbetterreadabil<Vmovecurrentsection7.2.3.1mihnmssapunder7.2.23VmovestartingatthissentencetountiltheendofthissectVmovethecontentof6.2.2.1into5.4.2BVmovetypehrdtlvmihfidandtypehdrtlvsessionidfromtzVmreplacenWmreplacethetextwiththefollowingnVmuchWmultipleWmustTWP@EQiaobingFXieGMember^ Editorial_40`56a6.1.6b~To make it read better, move Link Event Name to the 2nd column, i.e., No | Link Event Name | Link Event Type | Description |c~To make it read better, move Link Event Name to the 2nd column, i.e., No | Link Event Name | Link Event Type | Description |d2113g4699k  2006/11/16 2006/10/20tbl 2AEQiaobingFXieGMember^ Editorial_41`30a6.1.7btTo make it read better, move MIH Event Name to the 2nd column, i.e., No | MIH Event Name | MIH Event Type | ......ctTo make it read better, move MIH Event Name to the 2nd column, i.e., No | MIH Event Name | MIH Event Type | ......d2115g4700k  2006/11/16 2006/10/20tbl 3BEQiaobingFXieGMember^Technical, Non-binding_43`54a6.2.2.1b&move the content of 6.2.2.1 into 5.4.2clNetwork selection discussion in 6.2.2.1 is out of place. This kind of discussion should happen in section 5.d2119g4701k  2006/11/02PkCEQiaobingFXieGMember^ Editorial_50`50a6.3.3b1. Move the text out of the current 6.3.3, and 2. put the text in a new section "Access Information Service Before Authentication" or something like that before the current 6.3.3.cIDiscussion text from line 50, pg 50, to line 13, page 51 is out of place.d2148g4702k  2006/11/16 2006/10/20DEQiaobingFXieGMember^ Editorial_53`9a6.3.5bas suggested in commentcAFor convenience, show the actual 32 ID in the definition table of each TLV defined in 6.3.5 (right now the IE IDs are only shown in Table 32). For example: ----------------------------------------------------------------- | Type | ... ------------------------------------------------------------------ | TYPE_IE_OPERATOR_IDENTIFIER | ... | (0x10000004) | ------------------------------------------------------------------006/10/31 2006/10/20\b6.39W6.3.3CWWW6.3.5iW8W6.3.5.1.29W6.3.5.4:W6.3.6.1:W6.3.7.1W8W6.4lW?W6.4.4,W60&W9W629W68lW69nW7WW7mihcandidatedecideV7-9W7.2.12WWWtWW7.2.1mediadependentsaps2V7.2.1.12W7.2.1.1mihlinksap2V7.2.1.22W7.2.1.2mlmesap2V7.2.22W3W7.2.2mediaindependentsaps2V7.2.2.12W7.2.2.1mihsap2Vcdoesn't2WW#W%WdomainWWdon't6W W WW$W&WdoneWWdown'WW'W\WcWdraftWWWWWWWWW WW$W]W^W_W`WaWeWqWsWWWWWWWWWWdrivenWdueWWWduplicateWWduplicateinformationVduplicatedWdurationWGWduringW-W/WWdynamicNWe@WAWWWWWNWSWdWfWgWxWWWWWWWWethestandardshallspecifymechanismstosupportmn-initiaxVeachDWWWWW)W0W>W[WgWhWWWWeffectTW^WeffectonreceiptmustalsodiscusswhatwillneedtohappenTVeffectiveWefficeientlydWefficiencyWWehfWsedeKVLVencodingsrWensureWentitiesW,Ivh-aaayWhanadoverxWhandovergWuW6W_WwWbEither define it or delete it.le 10 either with a diagram or additional text. 2. move Currency field to be the lastc1. unclear about how the 4 fields are encoded in Table 9. One can only assume that they are 4 concatenated octet strings. 2. having variable length field ahead of fixed length fields is awkward to encode and decode.d2165g4707k  2006/11/15 2006/10/20tbl 10IEQiaobingFXieGMember^Technical, Binding_55`33a 6.3.5.2.3bEither define it or delete it.ncy field to be the lastc1. unclear about how the 4 fields are encoded in Table 9. One can only assume that they are 4 concatenated octet strings. 2. having variable length field ahead of fixed length fields is awkward to encode and decode.d2165g4707k  2006/11/15 2006/10/20tbl 10IEQiaobingFXieGMember^Technical, Binding_55`33a 6.3.5.2.3bEither define it or delete it.2.2bwbtype8W@WAWcWdWmWnWoWrWzWWWWWWWWW9W:W>WEWLWMWUWgWWWWWWtypefieldshallbeonefouroctectmVtype-length-valueiWtypesWgWwWtypicallyWudp/tcpWueqWumtsWWWun-authenticated~WunavailableWunder3WWWW"W5Wuni-directionalWunicastWuniqueWuniquelyFWunitNWunlessWunpredictableWunrecognizedUWVWunsolicitedWunsubscribe5W:W;WWunsubscriptionWuntilWWuntillWunused)W+WupeWWWWWWW\W_WuWvWyWWupdate9WWWWWWW+W2W:WWWWW0W253EW2nd@WAWEW31W329WDW4HW5BW5.3<W5.4<W50CW51CWi"ctype8W@WAWDWcWgWmWnWoWWWWWWWWWW9W:W<W=W>WHWIWLWPW\WgWWWWWWWWWWtypefieldforthisandsomeofthefollowingsectionshaveVtypeieacessnetworkidentifierisjustaoctetstringcorr9Vtypeiepoaaddressshouldberenamedtotypeiepoamacadd:VtypeiepoaipconfigmethodsisdefinedastypeiepoaipcVWKWLWbWcWhWuseuppercaseforservicewhileusinginformationservicehVused[WdWuser4W5Wusing'WaWhWvalidJWvalueEWFWJWKWLWNWOWPWQWnWvalueisnotclearlydefinedFVvariableEWHWcWvariants[Wvender\Wvendor\WverylWwant'WwantsTWway'WUWwaysaWwhat,WIWJWTWwhatisoption1arethereanyotheroptions,V.jmiisWmnlWWWmobilesWWmodificationsvWmodifiedWmodifyNWmodifythetextindicatedasfollowingintoline34page183NVmorelWWWWXWWmove1Wmovesection6.4before6.11VnecesarilyWneedoWWneededW*WWWneedsWWWXWWnetworkaWsWWWWnetworksWnewWnms!WnoWWsWWWnodesWnon-802Wnon-editorialvWnormativeWnot*WXWWWWWWnumberWobtainedWof[WaWlWsWWWWW!W3WNWXWWWWon[WWNWonelWWonlyWWopaqueWopcodeWoperation!Wor[WaWWWWorderlWotherWWWWoutaWWoutsideWover3WWoverallWpageW3WNWparameterNWW$ccome7W&WcomesWcommand1W7W:W;W?WWWW'W6W?WgW~WWWWWcommandserviceisnotperformedonlywiththeflowfromuppVcommandlistSWcommandlistparameterlacksdetaileddefinitionthiscommentSVcommandsWWWW^WgW~WWWcommentRWSWTWfWWWcomments6W7Wcommentsfieldofmihhandovercompletecommandseemsinaccu6VcommitWWcommitmentWa6.2.2.1By6.2.46.2.56.2.5.1676.2.5.26.36.3.1hk6.3.2㊃6.3.30C⩃89:;qrゃ6.3.4r6.3.5Di⪃V6.3.5.16.3.5.1.1<6.3.5.1.2E6.3.5.2.1F6.3.5.2.2G6.3.5.2.3HI6.3.5.2.4J⫃=6.3.5.2.5K6.3.5.2.6L6.3.5.3.2M6.3.5.3.3N6.3.5.3.4O6.3.5.3.5P6.3.5.3.6Q6.3.5.3.7&6.3.5.4>6.3.6'㷃㹃㻃㼃6.3.6.18e6.3.6.2U6.3.6.2.1V6.3.7[\⬃6.3.7.1]^6.3.7.2_6.3.86.41⭃⯃Ⰳ?6.4.2lW36.4.2and6.4.3lV6.4.3lW6.4.4+7.1.17.1.2ⲃⳃ 7.2.1W7.2.1.1s7.2.2et7.2.2.1ⴃⵃⶃⷃ @7.2.2.22XYZ⸃7.2.2.37.2.337.3f⺃WAW329W4QWeW5.3<W5.4<W5.4.2BW6.2.2.1BW^bname@WAWWW W WW4WWnamesW WnasWasWWecessaryyWgWneedTWxWWWWneeded$W3Wneeds WTWWnegotiatedWneighborWnet2W=WWWW W W WWjWoWnetworkFWiWsWtWyWWWWWW+W4W7W9W>WCWDWRWZWlWmWnWqWrWwW|WWWWWWWWWWnetworkusingthemihprotocolVnetwork-initiatedgWWnetworksFWZW|WWnetworks/poas'WWnewCWWWWWWW"W'W6W9W\W^WWWWnewlinkidentifierWnihoWWnms3W!WpWno@WAW WWJWWnomiheventnamemiheventtypeAVnodelWsWyW~WWWW7WgWjWlWmWWWWWL^Technical, Binding_56`4a 6.3.5.2.6b+Define encoding details of the Value field caEncoding details of the Value field missing. Without those details the IE would be of little use.d2174g4711k vby comment 2167w Superceded 2006/11/16 2006/10/20MEQiaobingFXieGMember^Technical, Binding_57`14a 6.3.5.3.2bLEither define it in this document or add a reference to where it is defined.c4Encoding details of the CivicAddressElements missingd2176g4712k vqThis encoding has been defined in an IETF draft... Editor to follow up with Yoshi and get reference to the draft.wAccepted-Modified 2006/11/16 2006/10/20tbl 12NEQiaobingFXieGMember^Technical, Binding_58`14a 6.3.5.3.3bTAdd details on the endoding of the Data rate (integer, floating point, ascii? unit?)c+Encoding details of the Value field missingd2177g4713k v$Specify units: Kbps and Integer typewAccepted 2006/11/16 2006/10/20OEQiaobingerwc61WWW&WvWW6remoten-triggervV6.1.3W6.1.5W6.2.2.1BW6.39WW6.3.5DWmW8W6.3.7W6.3.7.1^W6.4jW6.4.4+W62W65^W65535W67810W69W7WWW7.1.12WWWWW7.1.1containsonegenericmediadependentsapmihlinksapV7.1.23W7.2.1WWW7.2.22W3W5W7.2.2.25W7.2.3.11W7.3WW7.3.18W7.3.19W7.3.7.2WW7.4WWWW7.4.1.2fW7.4.1.3fW7.4.1.4fW7.4.2.1fW7.4.2.2fW7.4.3.1fW7.4.3.2fW7.4.4.1fW7.4.4.2fW7.4.7.1.3'W^W7.5W7.6WWqWabout'WEWHWWaboveJWaccess'WWaccording{Waccurate_WachievebWackvWacronyms+WacrossWactualDWaddingWadditionalfWpWaddresscWdWjWWadjectiveWx9cindependent2W3WwWWWWWW5W[WbWoWWWindependentlyWindicate{WWWWindicatingWWWindicationWW-WCW\WuWindicationsWinfoqueryresponseWinfoquerytypenWinformWWWWWW WWW7W8WCWDWEWGWRW]W^WgWwW{WWWWinitialize1WinitiatedWinitiatingqWinoffWinsecureWinstance{WWWinsteadmWintfWintegratedWintendedWinter_Winter-media;Winteract)W0WhWinteractionWinteractionsWinterface6WW WnWinterfaces6WinteroperabilitybWinterrruptionWintervalcWinto`WWW WWintraW_WintroducedWWintroductionW"WintroductionparagraphcontainsmanygrammaticalerrorsandVbchangecategoryofmiheventsubscribeandmiheventunsubsc;Vchangefigureper21-06-0xxx-00-000doc}VchangeheadingtomediadependentsaphavebutonebulletitVchangeipaddressconfigurationmethodslist215PVchangelinkpatameterschangeindicationintolinkparameterVchangemihdiscoverytomihfunctiondiscoveryVchangepackertopacketVchangeparagraphcasfollowswVclarify,WEWHWQW[W^Wclarifyandrewritethesentence[Vclarifythatwhenpresenttheconditional/optionaldhcpaddrQVclarifytheaboveissuemakeclearwheretherdfschemadefi^VclarifytheencodingeitherwithadiagramortextEVclear^Wclearly`Wclearlydefinetheuseoftheqosmodelinthemihframework`Vclient'Wcolumn@WAWcome7Wcommand7W:W;W?WSWcommandlistSWcommentDWRWSWTWconceptpWconditional/optionalQWIWMW2TEQiaobingFXieGMember^Technical, Binding_74`62a7.3.1.4bEffect on receipt must also discuss what will need to happen if the receipient wants to reject the primitive. This comment applies to all primitive definition.cEffect on receipt must also discuss what will need to happen if the receipient wants to reject the primitive. This comment applies to all primitive definition.d2242g4719k vBPlease refer to 21-06-0824-01-0000-general-primitive-failure-case wAccepted-Modified 2006/11/16 2006/10/20UEQiaobingFXieGMember^Technical, Binding_64`1a6.3.6.2bsAdd an "Unrecognized IE List" TLV which will contains a list of IE IDs that the MIIS does not recognize or support.ciNeed a way for MIIS to tall the querier that one or more requested IE is not recognized or not supported.d2195g4720k v\If there are invalid IE requests in query, return error and not return any partial response.wRejected 2006/11/16 2006/10/20VEQiaobing 10=l5cpartnerGWpartydWpassingWpatternWpauseWpdsnyWpduWFWpdus6Wpeer)WiWlWWWW)W*W0W]WdWgWhWWpeern-entity)VpeersWperWWWperislistedunderthedescriptionbutnotlistedasaniteVperislistedunderthedescriptioncolumnbutnotlistedasVperceptibleWperformWWperformedlWWWperformslWperiodaWperiodicallyWWpermittedWWperviouslydWWplaceBWCWW,WplacesyWpmd+poa8WsW~WWWWW&W:W;W>W[Wpoashouldbepoainline62aswellVpoas'WWpoint1WWpoints WRWpolicyWportWpos7WWW[Wpossible_WWWZWpossiblyTWpotentialWpower'Wpre-authentication;WpreambleWpreferedpoalistWpwVv!€tbl2@Vtbl3AV AcI"MIH Event Subscription/Registration" should be "MIH Event Subscription".d2263g2445 2006/11/16 2006/10/23F24BE YoshihiroFOhbaGMember^ Editorial_130`18a 7.4.14.1.2bFix it.c2TargetPoSIdentifier should be TargetPoAIdentifier.d2299g2456 2006/11/16 2006/10/23CE YoshihiroFOhbaGMember^Technical, Binding_131`56a 7.4.14.2.2bChange the MIH_Network_Address_Information.indication parameters to be the same as MIH_Network_Address_Information.request parameters.cWhy MIH_Network_Address_Information.indication has a different set of parameters than that for MIH_Network_Address_Information.request?d2305g2454iRonnyjRefer to Comment #303m Supercededvby 2303w Superceded 2006/11/16 2006/10/23DE YoshihiroFOhbaGMember^Technical, Binding_134`47a 7.4.14.4.2bChange the MIH_Network_Address_Information.confirm parameters to be the same as MIH_Network_Address_Information.response parameters.g2321Rbeitherre-dothemappingagainstmihprotocolpdusorremove6VelementrWWWWelements_WiWrW~WWW8WqWrWWWelse WWembededlWqWemoteWncodingEWHWJWKWLWPWWWWWWWWWWWencodingsrWend4WdWjWWWWWendingWendodingNWOWengineWenhance'WWWW Wenhancesection6.3.3tohavegreaterdetailsontheindividVenhancesection8.1toimprovereadabilityVenhancesection8.3.2tosimplyhighlighttheexistenceand Venhancethetlvinformationretrievaltoallowtheclientsp'VVentireWWentitiesWentity>W?WWW7WentriesPWentryJWW9Wequivalent]WerrorpWWEWerrorsEWespeciallydWessidFWestablishW'Wetc2WWWDcwhatistheservice-infoIVwhateverWwhenWWWWW5WFWNW^WkWuWWWWWWWWWwhenacknowledgedconnection-orientedmodeisusedthedataFVwhenconnectedtoa3gpp/3gpp2networkamobilenodeshouldVwhenthecontribution21-06-0765-00-000issue19wasaccepteuVwhentheinformationoriginatesatalowerlayeroftheprotVwhentheinformationoriginatesataremotenetworkelementVwhenthemihfinthenewpoareceivesthismessagefromtheVwhenusingegetcisnotpermittedsinceyourarelistingeVVwhere]WfW|WWWWwhereasWW*G‚1H‚2I‚3J‚4K‚5L‚6M‚7N‚8O‚9P‚:Q‚A'‚B8‚CU‚DV‚E[‚F\‚G^‚H]‚I_‚J1‚QW‚R2‚SX‚TY‚UZ‚V3‚WT‚XR‚YS‚Z4‚a5‚b:‚c6‚d;‚e9kVcentity>W?WWWWWWWWentriesJWentry\WequationWerrorpWWWWWWerrorsWWWesWWes/csqWes/cscapabilitydiscoveryinstate1isallowedthisshouldqVespeciallyWWestablishWestablishmentZWetcpWWW W'WjWWWethernetaW]WethertypeWWevent1W:W;W>W@WAWsWWWWW?WAWWW\W]WfWgWWWWeventlistRWeventlistparameterlacksdetaileddefinitionthiscommentaRVeventsWWWWXW]W^WgWWeveryWeveryoneWeverywhere WexactWexactlyXWexample'W1WDW^WpWWWWWWWW WW2W^WiWWexamples[WWWWWW WlurepWfcsWfeltwWfewWWhbp`3Xs⇃k<D☃ⱃ⸃΃#,J\n‚!⼃⽃d‚">i‚#z[‚$5H⊃⣃)+0FZhr{‚%MNⷃ&c‚&;⤃W‚'R{㋃‚(bу>V‚)⑃̓ՃB‚*‚1℃ʃッ㄃ㆃ‚2VӃ‚36.1.4x6.1.56.1.6@6.1.7A6.2.2? qkA!Message size is about 21~30 bytes and this is not big as a data frame. This is for the MIH entity sitting in the network. Because this entitty is agnostic to PoA, PoA can not advertise MIH capability of the MIH entity and also layer 2 data frame is recommended to be use by the MIH entity.!mRejectedvIssue created for section 8wRejected 2006/11/16 2006/10/23EAjayFRajkumarGMember^Technical, Binding_154`49a8.3.1.2bIf MIH state machine needs to be defined in the specification then it should be defined more completely rather than piece meal else the above description should also be removed.ckThe description of timers and how the MIH protocol would function with the state machine is implemenation. d2337g2226v9See issue 4 for overall protocol state machine discussionwRejected 2006/11/16 2006/10/23 69) as a Media Dependent SAP. The latter is correct.d2229g2224 2006/10/31 2006/10/23EAjayFRajkumarqbeitherdefineitinthisdocumentoraddareferencetowherMVeitherdefineitordeleteitIVeitherdeletehandoverstatusfromthelistoraddarowforVeitherdeletemacnewpoafromlistoraddarowforitVeitherdeletepreferedpoalistfromlistoraddarowforitVeitherdeleterowfornewlinkidentifieroraddittothelisVeitherdeletethesefiguresormovethemtoannexa-1drawtV|3ZEQiaobingFXieGMember^ Editorial_73`43a7.2.2.2bCre-order Link Detected in Table 17 to the same order as in Table 16c&Link Detected out of order in Table 17d2236g4725k  2006/11/16 2006/10/20t17[EQiaobingFXieGMember^Technical, Non-binding_64`47a6.3.7b!Clarify and rewrite the sentence.cBroken sentence: "Examples include Resource Description Framework (RDF) which is based on XML which is used in 802 MIBs, Variants or a simple TLV representation of different information elements."d2197g4726iYoshihiro OhbajA simple TLV representation of different information elements How about: "Examples include Resource Description Framework (RDF) which is based on XML, or a simple TLV representation of different information elements"k mAccepted-Clarifiedvinding_69`45a7.2.1b;Add a subsection in 7.2.1 for LSAP and CS_SAP, respectivelycYTo be consistent with 7.1.1, need a subsection in 7.2.1 for LSAP and CS_SAP, respectivelyd2204722`<bconfig8WQWWconfigurationW7WNWPWrWWWconfigureW WWconfiguringjWconfirmfWW WWDWWWWconfirmedWconnectedlWWconnectiontWW[W^WWconnections[Wconsidered+Wconsist WconsistencyWconsistentaWWWWconsistentlyWWWconsistsjWconsitenthWconstrain^WconsumedWcontain_WcontainedFWNWinthedescrVVcorerWWcorrectWcorrecttheinconsistencyVcorresponded&WcorrespondingiW:WcorrespondsRWSWcreateWcreateanewannexandaddsection4of21-0460-04-0000-basiVcrossWcsWWcurrencyHWcurrent3W<WCW"W7WcurrentlysWdWdashed>W?WdataNWWWWWWEWFWdataonlywhenstatus0EVdatabase7WdecidelWWV} bare,WQW_WeWjWlWrWxWWWWWWW"W)W0W3WNWSW^WeWhWmWrWxWWWWWWWWareincludedinannexeVareaWarrow>W?WWWWas2W4WDWFWZWfWiWqWvWWWWWWWWWWWWWW W WWWWWWWW"W$W'W@WCWDW^W_WgWlWmWwWWWWWWWWWWWWWWWWWassuggestedincommentDVaswrittenmultipletimesinthecurrentdraftVasciiNWOWassociatedWWWgWWWWattached+WattachementsWattachmentqWWattacks~WauthenticationCWqWWauthorization$WavaialbleWavailabletW~WWWWb_WWW4Qbpdus6WpeerlWWWWgWlWmWqWrWWWpeerslWpending6WWper|W}WWWperformlWperformedWWperformslWperiodMWperiodsWpermissionlWpieceFWWpiecesWFWpiggy-backdWpiggybackWplace1WWplacementWplacesWplanejWkWmWnWpleasexWWWWWpleaserefertocontribution21-06-0731-01-0000-lfordetailVVpoa8WsW~WWWW+W:W>W[WlWqWWWWWWWWpoa2Wpoa3WpoakWpoanWpoasWpoint4WNWOWsW WgWpoint-to-pointWpoints WmWWWpolicymWpoll/get WportWWportsWpos7W~WW[WWWWWWWW W W WWW!W.W@WSWprinciples"WpriorsW2batjWWWWWWWdWgWWWWattached+WattachementsWattachmentqWWWWattacks~WauthenticationCWqWWauthorization$WavaialbleWavailabletW~WWWWb_WWWW €qnadarpR€rgolmieqnada€snadatps€tgolmiesnada€uvXx0€vnadawu€wgolmievnada€xnadayuX€ygolmiexnada€znada{pS€{golmieznada€| $}*P€}nada~|$€~golmie}nada€nada|*€golmienada€nada| €golmienada€nadaZ€golmienada€nadaV€golmienada€7u%€nada7€golmienada€cFunction discovery at L2 is optionally integrated with Capability discovery, however function discovery at L3 is not defined and therefore interactions with capability discovery are also left unspecified. d2318g2218iMichaelWjChange sentence to read: While the MIH Function discovery at Layer 3 may consider or be combined with capabilities discovery, these layer three discovery mechansims are are outside the scope of the 802.21 specification.mAccepted-ModifiedvCurrent text permits this.wRejected 2006/11/16 2006/10/19MarkedEEleanorFHepworthGMember^Technical, Binding_153`16a8.2.1bA9Delete the reference to TCP/UDP and port number. Replace "The same frame structure may also be used with a standard L3 protocol (UDP/TCP) with a well defined MIH port as well." with "The same frame structure may be used within any L3 transport solution, with additional encapsulation required by the transport."9ce needed 2006/11/08bfaQWNWfacilitatewWfacilityqWWfactWfailureMWWfairlyWfeatureWfeelsWfewWWfieldGWHWJWKWLWQWcWdWmWWWWWWWWWWW7W9WFWLWUWVWaWeWWfieldsiWfigure0W=WkW}WWWWWWWW,W4W:WkWmWWWWWWfigure1showstheplacementofthemihfwithinthemobilityVfigure20showsthelayoutofdifferentinformationelementsVfigure8showsthemihfunctionfor802.16basedsystemthemVfiguresQWWWfinalWWWfollows2WiWfontkWfor5W<WFWWW^WeWjWqWrWxWWWWWWWWWWWWforprimitivesyntaxpleaserefertoannexgxVformiWformatiWWformats_WfourmWhbevents5WWgWWevents/links/remoteWeverythingWexactlyRWSW WexampleFWlWW4WlWWexamplesWWWWexceedFWexceptW WUWqWexchangeWWjWWexchangedWexchangesWexchanginglWexecutedWexecutionwWexhaustivelyWexistWWexistence Wexists\WWexpected^WexpiredWexplain7Wexplainhowmicsisrelatedtotheinformationdatabaseand7VexplainedgWWexplanationWexplanatory0WexplicitlyRWSWexplicitlyshowexactlywhichbitisthecommandlistparametSVexplicitlyshowexactlywhichbitistheeventlistparameterRVextendWextended\W_WWWextendedschemathatisvendorspecific\VextentYWPWlower>W?Wmade9Wmake@WAWmapping6Wmaybe>W?WbdefineencodingdetailsofthevaluefieldKVLVdefinegenericlinkparametersencodingVdefinehowtoparsethisfieldespeciallyhowwouldtherecedVdefineresourcesinmediaspecificwaysgiveexamplesfor80VdefinedMW_WWWWWWWW WWWWwWWWWWWWdefines WaWbWoWdefinition(WTW^WyWWW!WvWWWdefinitions)WWW\WvWWdefintionaWdelayWWdelaysWdelete(W)W+W1WIWtWWWWWWWWWWWWWWWWWWWWWWWWW WWW#W%W&W?WnWpWWWWWdelete5.6.1.2through5.6.1.7oratamimimumputthemataVdelete5.6.1.3msapsubsectionnVnition(Vationavailablel2ctVHWIWMW\r+tcBecause MIH_LINK_SAP was decided to move to media dependent SAP section, this section also should be moved to media dependent SAP section. MIH_NET_SAP should be media dependent as well.d2230g5007vaMIH_LINK_SAP goes to Media Dependent category.... MIH_NET_SAP stays in Media Independent categorywAccepted-Modified 2006/11/16MarkeduERonny^Technical, Non-binding_131`48a7.4.14bODiscuss and accept clarifying text in 21-06-0793-00-0000_NAI_primitive_clean_upcWhen the contribution 21-06-0765-00-000_Issue 19 was accepted, there were request and response primitives. In order to align with request, indication and response, confirmation pairs, clearing text is submitted. d2303g5008v,This adds confirm and indication primitives.wAccepted 2006/11/16,?bwhentheinformationoriginatesatalowerlayeroftheprotVwhentheinformationoriginatesataremotenetworkelementV(q€golmienada€nada8€golmienada€nada+C€golmienada€nadaWZ€golmienada€nadaX€golmienada€nadaT€golmienada€nadaZ€golmienada€nadaR€golmienada€nadaX€golmienada€nada}€golmienada€nada}F€golmienada€nada}J€golmienada€nadaohba  €golmieⴃⵃnada€nada %€golmienada€nada€ cAPoAs/MNs may be able to handle MIIS query response of a limited size only. There needs to be a way for MN to specify max length of query response. There is a need to incorporate a means such that query from client does NOT result in too much data being delivered. A PoA may not be able to predict how large a query response may be. So the PoA needs a method to provide 802.21 IS with max length and then the MIIS can provide status response in place of query response if the response is too leBngthy. d2187g2230vbased on remedy 2 in contribution 21-06-0827-01-0000-TLV-indicating-network-types To be worked on and consolidated contribution to be submitted later. wRejected 2006/11/16 2006-10-23-23may be. So the PoA needs a method to provide 802.21 IS with max length and then the MIIS can provide status response in place of query response if the response is too leBngthy. d2187g2230wDeferred 2006/11/16 2006-10-23ing ^bindingWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW‚|srinivas{ sreemanthula‚} sreemanthula~u‚~srinivas} sreemanthula‚ sreemanthula1‚srinivasッ sreemanthula‚ sreemanthulaF‚srinivas sreemanthula‚1" ‚ sreemanthula1‚srinivas sreemanthula‚T"‚ sreemanthulaT‚srinivas sreemanthula‚vidal‚albert vidal‚vidal@‚albert vidal‚albert lvidal‚vidal1'‚albert vidal‚v#‚vidalv‚albert vidal‚vidaleE‚albert vidal‚vidaleR‚albert vidal‚ kbupdatetable32toreflectthechangesmadeto6.39Vupdated2WiWupdateswWuplinkWuplinkbroadcastingmessagefromaterminalmakeslittlesenVupon$WWupperWWWusageRWSWuse`WqWWWWlWqWWWWusestatustlvastheabortreasonformihhandoverinitiateqVusethesameencodingschemeassection7.3.4.2Vused5WFWcWdWkWWWW WEWaWmWoWqWvWWWuseingqWuser4W5WWWWusers'WWWWnWusing>W?WWWW8W_WqWrWvWWutilizedwWutillWvalidJWWUWvalueFWGWJWKWLWOWQWnW{WWWMWVWeWWvaluesJWoWWvariabelfWvariablePWWWWvelidityMWvendor\Wvendors_Wvery~WwantsTWwasEWWr%badddetailsontheendodingofthedatarateintegerfloatinNVadddetailsontheendodingofthevalueintegerfloatingpoOVaddfollowingdefinitioninsection3yVaddit}Vaddlinkcapabilitydiscoverprimitiveintable16andtableXVaddlinkgetparametersprimitiveintable17YVaddmechanismstoretrieveiformationbasedonabovequeryfVaddmihnetsaptofigure12=VVaddmissingprimitiveVaddmissingprimitiveandrelatedinformationVaddmissingsapVaddmoredetailsontheencodingofthelistofsubnetshowPVaddontheremoteentitysideacommandarrowfrommihfunct?Vaddontheremoteentitysideaneventarrowfromlowerlaye>VieidsVVaddsomeexplanatorytexttofigure200VaddstatustoheaderhereVaddthedefinitionofnmstosection3andthedescriptiono!Vaddthefollowingdescriptionintopage68line52insectiolVQWhcsystem1WjWpWWgWWsystemsWtable9WDWEWHWXWYWZWaWeWfWoWrWzWWWWWWWWWWWWWWW%W@WKWOWWWtable32isoutofdateafterrecentchangesmadeto6.39VtablehasmanycellsthatraeemptyVtableinpage170forabortreasondoesn'tmakesenseitsho%VfierWtechnologiesWtechnologyWWWWWtemplate8Wterm(WterminologyWtermsyWWtext0WCW\WWWWWWWWWWW WW%WtextcontainsmanygrammaticalerrorsandneedstobefixedVtexthasnothingtodowithhandoverpolicyVtextstatesdifferentprotocolstacksareshowninfigure4VtextstatesthatusecaseandhandoverareintheappendixyVtexts"WthanWWWWWWWW' bchangepercontribution21-06-0xxx-00-0000-rmodeltext53|Vchangerange0-127to1-127anddecidewhatactionshouldocVchangetextto\V_VchangethedescriptiontoEVchangethedirectionofthearrowforcommandservicefromoVchangethefontusedinfigure19kVchangethelengthto4<VchangethemihnetworkaddressinformationconfirmparameterDVchangethemihnetworkaddressinformationindicationparameCVchangethemihserviceidofmiheventsubscribeandmiheve:VentifierandmihactionidenVchangetheprimitivemihgetinformationresponseintomihg VchangethesecondoccurranceoftherowqueryresourcelisttoVchangethetextasfollowsVV Vchangethetextinsection6.3.5asfollowsiVchangethetypefieldinthetableasfollowsVVchangetitletonetwork-initiatedhandoverfrom802.21to3ggVchangetoFVGVchangetol3mmpVramework`V\IEEunahFKimGMember^Technical, Non-binding_199aAnnex A4bA1. Delete "Link_Switch" primitive as it is not defined in this draft specification. 2. Change "Link_parameters_change.indication" into "Link_Parameters_Report.indication". 3. Change the primitives from MIH to Decision Engine as follows "Link_Up.indication" => "MIH_Link_Up.indication" "Link_Down.indication" => "MIH_Link_Down.indication" 4. Change "MIH_Switch" into "MIH_Switch.request"cThe Link_parameters_change.indication primitive is not defined in this draft specification. Also, it is necessary to use the exact primitive names on this flow.d2409g2229vby comment 2407w Superceded 2006/11/16 2006-10-20386-10-23EVivekFGuptaGMember^Technical, Binding_197`1aAnnex A4MN to know DHCP server IP address before handover. mRejected 2006/10/31 2006-10-23EVivekFGuptaGMember^Technical, Binding_197`1aAnnex A4cie8WDWJWKWLWUWVWiWW&W9W:W;W<W=W>WWWWWWWieeeWWW9WWWWWiesiWrWzW8WietfWifTWcWdW~WWWWWWWWWW W&WGWNWcWdWgWWWWWWWWWWifmihfunctionofmobilenodehasnotreceivedeitherthemVifthesearemediaindependentsapsthenwhyisthe802.11tViidWillustrated4Willustration>W?WimpleWimplemeentGWimplemenationWimplementWW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W}`EChengFHongGMember^Technical, Binding_13`49a5.1.3b>Clearly define the use of the QoS model in the MIH framework. cfHow does the QoS model fit into the MIH framework? How is it related to the MIH function is not clear.d2037g4731vNeed more details from commenter on how the model does not fit in MIH framework? The section 5.1.3 tries to explain how QoS fits into MIH framework. Section 5.1.3 is NOT balanced w.r.t other sections.wRejectedThe section 5.1.3 tries to explain how QoS fits into MIH framework. Section 5.1.3 is NOT balanced w.r.t other sections. Please add a few lines to explain that better. 2006/11/16alanced w.r.t other sections.wRejectedThe section 5.1.3 tries to explain how QoS fits into MIH framework. Section 5.1.3 is NOT balanced w.r.t other sections. Please add a few lines to explain that better. 2006/11/15" and the rest are using "802.x". d2322g4732iMichaelWieGMember^ Editorial_73al_73al_73al_73al_73Jclinkgetparametersprimitivemissingintable17YVlinkidentifiermissingfromlistbutincludedasarowVlinkpacketerrorrateVlinkparameterlistisinconsistentwithpreviousdefinitionVlinkparameterschangeindicationisnotdefinedinthisdraVlink--sinceWlink/networkWlinkedWWlinkidentifier\WlinkparameterlistWlinkparameterlistdefinitionisinconsistentwithitsotherVlinksgWotdescribedinseVmapped6WmappingWmaterialWWmay'W\W{WWWmdi+meansWmeantWmeasuresWWmedia2W3WaWWWWWWmessage(WoW{WWWWWmessagesWWmethods8WiWmibs[Wmics7Wmih1W2W3W4W5W:W;W<W=W>W?WAW`WlWvWwW{WWWWWWWWWWWbWlWmWWAkmacceptedhjno7n~accepted-clarified[^accepted-modified1]als⁃ۃXo㢃㦃㬃㯃questionrejected☃⮃*dv〃㗃㘃㞃㡃㶃superceded ₃Cゃv1W10RW11yW2|WvW2n-entityvV2028)W2032W2071W2071/2072 W21xW21-06-0794-01-00-000|W21-06-0794-01-00-000text532|V22-1023RW2227W2233W2325W2328W248W3|W4WvWzW3n-eventvV325W328WW330w)WhW339 WdWW341dW345GW3gppW3gpp/3gpp2|WW3gpp2W4vWW4n-layervV5|WvW5n-uservV5.3W5.3.24W5.4.2.4BW55sW6vW6remoten-triggervV6.4.2W67W7vW7peern-entityvV7.4W8W8.2.1W8.3.3RW4cbrokensentence[VbscyWbssids/essidsWbulletedWbut^WWWWWWWWWWWWWWWWWWWWWWWW W W>WNWgW}W~WWWWWWWWWWWW&W]W^WbWcWdWgWnWWWWWbyteiWbytesWc_WWWwWc/iUWcallwWcalledWSWWcan1W6WEWHWeWfWqWWWWWWW&WGW]W^WdWgWkWWcan'tWcancelWcandidateWcandidatesWcannotWcapabilitiesgWcapabilityXWlWWWWWWWW&WRWfWqWWcapabilityies&WcapableWcaptionW~WcarriedNWcarry9W;WcarryingLWcasehWWWWWW^WdWeWkWWcfieldHWJWKWLWNWOWPWQWcWmWW6WLW\WdWeWWfieldsEWHWW7WUWfierstdWfig~WfigsWfigs3637and38donotbelonginannexa4Vfigure0W1W=W>W?WgWkW}WWWWWWWWWWW WWW,W4WkWWWWWWWWfigure1showstheplacementofthemihfwithinthemobilityVfigure12appearstobemissingthemihnetsapVfigure12shouldbeconsistentwithfigure4}Vfigure19isnotreadablekVfigure22needstobeupdatedVfigure4andfigure12arecompetingonlyoneisnecessaryVfigureismissingmihnetsapVfiguretexthasgoneabitwonkyVfigure-20WfiguresQWfinalWfinallyWfindWfirstlWW[W6addressisusedVi@WAWidDWbWidentifierDWidsDWVWXGecTo prevent future mismatch between the primitives in the table and the primitives in the description section, order the description to be the same as the table ( or otherwise).This can provide clarification and also sanity check.d2222g2464vEditor: Please note this.... 2006/11/16 2006/10/23T15eESubirFDasGMember^ Editorial_71a7.2.2b The descriptions for Table 15 are in section 7.4. Therefore, Table 15, #4 " MIH Link Up " description should be in section 7.4.4; Table 15, #11 "MIH Link Handover Imminent "description should appear in section 7.4.11, and so on.... #4 " MIH Link Up " description should be in section 7.4.4; Table 15, #11 "MIH Link Handover Imminent "description should appear in section 7.4.11, and so on....0/26cEChengFHongGMember^Technical, Binding_165`1a8.4.1.7bKDefine a self-contained MAC Address field that can indicate the type used. LL^non-binding]W^WgWjWnWrWsWtWuWyWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW#W$W%W&W'W,W2WQWiWkWlWnWrWtWuWvWwWxWyWWWWWWWWWWWWWWWWWA ^technical@7technicalbinding@ ptechnicalnon-binding@)_‚:@‚@b‚@{‚@HÃ&p@hchangecategoryofmiheventsubscribeandmiheventunsubsc@config@eitherdefineitinthisdocumentoraddareferencetowher@eitherre-dothemappingagainstmihprotocolpdusorremove@event@events@fa@media@name@pdus@reorgthesesectionsasfollows@sections@specify@tlv@type@updatetable32toreflectthechangesmadeto6.3@c6@brokensentence@come@common@doesn't@entity@field@ie@independent@late@linkgetparametersprimitivemissingintable17@narrow@partner@related@system@thereshouldbesomeexplanatorytexttofigure20@type@whatistheservice-info@k€tbl2@Vmember$'()+,0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⳃⴃⵃⶃⷃ⸃⹃⺃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !")*+,-./01^technicalbinding'V,V1V4V5V6V8V9V:V;V=V>V?VEVFVGVHVIVJVKVLVMVNVOVPVQVRVSVTVUVVVXVYV\V_V`VaVbVcVdViVlVmVoVqVvVwVzV{V|V}V~VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV VV V!V)V*V+V-V.V/V0V1V3V4V6V7V8V9V:V;V<V=V>V?V@VCVDVEVFVGVJVKVLVNVOVRVSVUV\V]V^V_V`VaVbVcVdVeVfVgVhVjVmVoVpVqVsVzV{V|V}V~VVVVVVVVVVVVB`@‚D@b‚J@#a4.0@5.5.4@5.6.2.3@6.2.2.1@7.3.1.4@7.4.10.1.2@7.4.11@8.3.5@8.5.13-6@9and@6b1addcurrentlinkidentiferandtargetpoaidentifier@?1clarifytheencodingoftable10eitherwithadiagramor@15-mih@detailsontheendodingofthedatarateintegerfloatin@addthefollowingdescriptionsattheendoffirstsentence@allow@annex@}are@be@capabilities@changecategoryofmiheventsubscribeandmiheventunsubsc@changepercontribution21-06-0xxx-00-0000-rmodeltext53@changetomihgetstatus@clearlydeterminethegroupingsforevents/links/remoteeven@`config@defineencodingdetailsofthevaluefield@deleteatleastpreambleandstartofframedelimiterfromf@deletemihsapfromendofline@mdeletetheunusedacronyms@*descriptions@effect@qbl2@Lcnot$W'W(W4W5W6W<WFWGWUW_W`WaWbWdWgWkWlWoWrWtWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WW"W'W,W-W8W>WFWMWOWPWSWUWXWZW]W^W`WaWcWdWeWfWgWjWlWnWpWvWyW|WWWWWWWWWWWWWWWWWWWWWWWWnotclearwhatremoteregistrationreferstodescriptionisVnotclearwhattypesofprimitivesexistforeachitemlisteVnotsurewhatismeantbythestatementandtheirpotentialVBWCWZWoutsideuWoveriWWcWpart1W^W@bfrom4W>W?WgWsWzWWWWWWWWWWWWWWWWWW"W'W6W7W?WMWUWWW^WkWqWrWWWWWfrontWfunction4W5W>W?WlWWWWWWW$WTWjWlWmWqWrWWWfunctionality^WwWfunctionsSWfurtherWWzWidentifierGWidentifiersrWidentifyFWidsUWVWie8WUWVWieeeuWiesrWifTWimminenteWin'W4WCWDWMWWWXWYWZW_W`WeWfWiWjWkWlWnWoWpWrWwWxWyW{W~WWincludeWincluded'W_WincludesWindependent2WindicatecW{WWindicatingyWindividual_WinfoquerytypenWinformation'W7WCW_WbWhWiWrWtWuW~WWWcbecause6WWW<W>WtWWWWbecausemihlinksapwasdecidedtomovetomediadependenttVbecomeWbecomesWbeenWWWWWWbefore~WWWWbeginningWbehavior^WbehaviourwWbeingyWWWWdWWWbelieveWbelong2WzWWWbenefitWbenefits&WberUWbetter@WAWxWWbetweeneWlWtWWWWWWWWW W W-W2WiWmWzWWWWWWWWbetwenWbi-castingWbi-directionalWbitWWWWdWbitmapWWWWbitsdWWblue^WbootingWboth1WiWWWWWZWdWeWoWWWboxWbrieflyjWbroadcastWWWWbroadcastingWWWbroken[W`cbecause@brokensentence@by@cases@civicaddresselements@$come@common@confliction@Hcontrol@correctly@_currentaccessroutera@defiend@defines@fdepending@>descriptions@detailed@Ndifference@discard@doesxdoesn't@either@entity@examplesincluderesourcedescriptionframeworkrdfwhichis@field@fit@foraparticularnetworkorsetofnetworks@forconvenienceshowtheactual32idinthedefinitiontabl@frames@pgiven@handoverstatusislistedbutnorowexistsforithappen@-have@khowdoestheqosmodelfitintothemihframeworkhowisit@iwouldsuggestthevalueberemovedunlesshavingthevalue@ie@implementation@mihcapabilitydiscoveryprocedureisalsousedbynetworkt@miheventsubscribeandmiheventunsubscribearecommandse@XcUc1encodingdetailsofthevaluefieldmissingJV1hardhandover/softhandover/seamlesshandovervV1howeverafterauthenticationandattachmenttoacertainpV1shouldbecalledmihfunctiondiscoveryV1thetitleofsection6ismihfservicesandnofigurehas1V1thereisnolinkcommandexecutionshownforlocalcommand~V1thereseemstobe2linkidentifierscurrenttype12andn\V71nW172nW18?W19kW1stEW21WHWJW_WzWWWW-W4W\W2extendedschemaisnotdescribedinannexb_V2whatarethevalidentriesfordifferentrevisionsJV200W22W23^W243\W244\W25WKW253EW26oWWWWW2nd@WAWEW31W_WW-W3anexhaustivelistofinformationresourcesandproperties_V31nWW329WDWgWrW32-1WWW<W47W49W5BWW3l4EEricFNJEDJOUGMember^Technical, Binding_20`1a5.3.2bChange the name of the Section 5.3.2 in: "A Deployment Example for the MIH Services" Change also the caption for the Figure 3 in: "An example of network model including MIH services"cmThe MIH Communication Model is already described in the previous Section 5.3.1 and illustrated in Figure 2. d2055g2256v Change the name of the Section 5.3.2 in: "A Deployment Example for the MIH Services" Change also the caption for the Figure 3 in: "Example of Network Model with MIH services"wAccepted 2006/11/16 2006/10/11Marked35.3.2 in: "A Deployment Example for the MIH Services" Change also the caption for the Figure 3 in: "Example of Network Model with MIH services"wAccepted 2006/11/15 2006/10/11Marked3d in the rest of the document. _67`48a6.4b/Delete MIH Event Subscription from Section 6.4.cPMIH Event Subscription are categorized as Command in the rest of the document. w  cavoidbW*WawkwardHWWb_WWWWbmihlinksapthisrepresentstheabstractmedia-dependentVb'sWb6Wb7WbackWbandwidthWbased[WWbasicWbasicschemaneedstobeupdatedVbe'W0W1W4W5W6W>W?WJWKWLWWW\W_WeWiWmWqWvW}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWW W"W#W$W%W&W'W*W,W-W/W1W:W;W<W=WAWBWEWFWHWIWLWRWVWZW[W\W]W^WaWbWcWgWjWkWlWoWqWrWsWtWvWyWzW|WWWWWWWWWWWWWWWWWWWWWWV0a7.3.1.4T7.3.11.2c7.3.14#7.3.17.1_7.3.19.2S7.3.2.2R7.3.20.2ƒÃăU7.3.21.2Ńƃ7.3.3.27.3.4.27.3.6.27.3.7.27.3.77.3.88.4.1.288.7.3.8.27.4.1,A7.4.1.1-7.4.1.2.4$7.4.1.3.2/7.4.1.3.3T7.4.15.3.27.4.2.1.27.4.2.2.27.4.3.1.27.4.3.1.347.4.3.2.27.4.4.1.157.4.4.1.27.4.4.2.27.4.5.1.27.4.8.1.4΃7.4.9.2.27.5ك7.6.2.3.47.6.2.4.37.6.48.1ۃ܃8.2a8.2.1ރ8.38.3.18.3.1.28.3.2v{ 8.3.3.1b8.3.48.3.4.28.3.5:8.4m8.4.1.11p8.4.1.128.4.1.208.4.1.328.4.1.35nW8.4.1.358.4.1.36nV8.4.1.36nW8.4.1.7c8.4.1.9d8.5o8.5.1.18.5.1.28.5.3.16qa1.3g Wa1.4.1a1.4.2a26; Wa39zWa4 WWW2.1BW3crequestedUWrequestedeventWWrequestsWrequiredmWWrequirementsWWreservesWreset1WresidesWWresource[Wresources_W`WWWrespectivelyWWresponse{WWWW WW-WDWEWdWfWuWWWWWWresponseeventWWresquestWrestaW?WrestrictedWrestrictiveWresultWWretransmissionW WretransmittedGWretriesWretrieval'WWWWeve'WWretrievesWreturnsWreverseWrevisionsJWrightDWWnWroamedWroamingGWWroleW WWrollback\WrouterNWrowWWWWWWrowsWWWrssiUWrttW WruleVWJWsYWsaWsameeWiWmWWWWW5W>WEWLWSWfWyWWWWWWcfit`WfiveWfixWWfixfontsizeaswellVfixthefontsinthefigureVfixedEWHWWWflowWWW^W~WWWWWflowswWWfollowing-WdWfWyWWWWfollowingacronymsareincorrectyVfollowingacronymsarenotusedyVfollowsWfontWfontsWfonts/labelsWfor'W(W1WDWJWUWWW^WhWiWpWqWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWW!W"W#W$W%W)W,W.W0W2W3W>WCWDWEWLWMWRW\W]WgWhWiWjWnW~WWWWWWWWWWWWWWWWWWWWWWbutnorowexistsforitW&5 mvAAll IE identifiers (TYPE values) as defined in Table 32 are 4 octets. These identifiers are used only in IE related payloads (MIH_Get_Information.request/response). Remove first two rows (these are MIH HDR related TLVs MIHF_ID and SESSION_ID ) from Table-32. Put them in a separate table or with other TYPE values as defined in Table-26. These TYPE values can be all 1 octet. Do *NOT* change 1 octel to 4 octet as suggested above. wAccepted-Modified 2006/11/16 2006/10/23nESubirFDasGMember^Technical, Non-binding_171`31a8.4.1.35 &8.4.1.36bAMreplace the text with the following: List of query parametrs depending on the value of InfoQueryType A list of responses depending on the value of the TLV IS Query Type (8.4.1.4), which accompanies in the same message."@A> 33)  i  > Elements). Therefore the type field in MIHF TLV shall be FOUR octects instead of ONE.d2360>#FkcontributionWcontrolvWWWcross-layervWdefineWdefinedW!Wdefining!WdhcpNWdifferent1WdiscoverlWdiscoverylWdraftWduplicate!WdynamicWeWentittyWentityWevent!WfaNWfall!WfigureWfigureinthecontributionhelpsunderstandthefunctionofVfor1WlWW!WNWWWframeWWfromWfunctionlWWWfunctions!WgWget!WWgiven1WhandoverWhave!Wheavy!Whelpful!WhelpsWhoweverWiesWinlWW!WWWincaseofusinglayer2transportformihfunctiondiscoverlVincludedWinformation!WWWinto!WipNWWis1WW!WNWWWWitWWkeep!WknowingWl2WWl3WlastWlayerlWWWlinkW!WWmadatedW1-3hMGMember^ Editorial_175`1a 8.5.1.[3-6]bAG[1] Remove Source Identifier and Destination Identifier from the tables in Sections 8.5.1.3 to 8.5.1.6 [2] Define Length and Type for Request Code, Velidity Period, Reg Result Code, Reg Failure Code and DeReg Failure TLVs in Section 8.4.1. [3] Remove Length and Value columns from the tables in Sections 8.5.1.3 to 8.5.1.6.Gc`The tables in sections 8.5.1.3 to 8.5.1.6 are not consistent with the tables for other messages.d2379g2453 2006/11/16 2006/10/23NE YoshihiroFOhbaGMember^Technical, Binding_183`34a8.5.3.23b9 33RcThe MIHF TLV Encoding scheme is the same as the encoding scheme described in page 52 (6.3.5 TLV Representation of Information Elements). Therefore the type field in MIHF TLV shall be FOUR octects instead of ONE.d360g2480 2006/10/31 2006/10/23nESubirFDasGMember^Technical, Non-binding_171`31a8.4.1.35 &8.4.1.36besESubirFDasGMember^Technical, Non-binding_9`7a3bA1Serving PoA: The network point of attachement of the mobile node that is currently being served prior to the link swicth event. Target PoA: The point of attachement of the mobile node that results from Candidate network point of attachement that a mobile node may swicth to due to link swicth event. 1@A  33  33A `   33    33cOServing PoA and target POA definitions are too much tied with Link Switch Eventd2030g2489imichael williamsjA `   33    33cOServing PoA and target POA definitions are too much tied with Link Switch Eventd2030g2489imichael williamsj  >%5baddthefollowingdescriptionsattheendoffirstsentencejVaddthefollowinginsection6.1.4afterthefirstsentencexVaddthefollowinginsection6.3.3VaddthefollowinginthedescriptionfieldVVVVaddthefollowinginthedescriptionfieldofsupportedevenVaddthefollowingrowsassuggested$Vaddthefollowingsentencetosection8.3.4JVthisprimitivetotable15onpage71VaddthreeperiodsieindicatingthemissingpiecesbetweenVaddtypeiepoaipconfigmethodstoreportingtemplatetlv8VaddedxWadditionjWadditionalHWWWaddressQWcWWWW:W;WCWDWaddttional$Wadopt;W=Wadopt21-06-0779-poaipaddressiedoc;Vadopttheformatproposedin21-06-0778-00-0000-nstandards=Vafter<WxWagainst6Wair~Walive+WallJWRWSWTWoW~WWWWWWWWWi=cafter9WlWcWWWWagnosticWagreeWaheadHWaims_WairWair/wireWalgorithmsWalignuWallRWSWTWoW~W*WRWgW{WWWWWWWalltypevaluesintheprotocolmessagetlvtablearenotupoVallow)W0WgWhWWWWallowedqWWallowingGWallowingemptyroamingpartnerlistdoesnotmakemuchsenseGVallowsgWqWalready1WW&W4W\WWalsoTWbWeWtWvWWWWWWW WWW W"W8W>WGW\W]WfWqWtW~WWWWWWWWalthoughW^Walthoughsection8.1describesthel3transportasbeingoutVWWWWWWWWWWWWWWWannex_WxWWannex2Wat1Wauthenticated~Wavailable~WrESubirFDasGMember^Technical, Non-binding_51`44a6.3.4bAReplace with the following text: Information element range "0x00000001 - 0x000000FF" are the core header specific IEs. Refer to Table 26 for TLV Encodings. Refer to Table 32 in Annex A3 - Type identifiers for Information Elements@A> 33{   >nding_51`44a6.3.4bAReplace with the following text: Information element range "0x00000001 - 0x000000FF" are the core header specific IEs. Refer to Table 26 for TLV Encodings. Refer to Table 32 in Annex A3 - Type identifiers for Information Elements@A> 33{   >range "0x00000001 - 0x000000FF" are the core header specific IEs. Refer to Table 26 for TLV Encodings. Refer to Table 32 in Annex A3 - Type identifiers for Information Elements@A> 33{   > vthoseoWthresholdsWthroughjWtWsWWWthroughoutnWthusuWeWtied$WtimelWtitlegWWWtlv8WRWl type values in the protocol message TLV table are not updated with the values assigned in Table 26.d374g2483 2006/10/31 2006/10/23pESubirFDasGMember^Technical, Binding_165`54a8.4.1.11bUDiscuss and accept the concept described in 21-06-0781-00-0000-MIH_Protocol_Error.ppt 2006/10/31 2006/10/23oESubirFDasGMember^Technical, Non-binding_173`49a8.5bcFix all TLV type values in section 8.5. According to Table 26, it should be 1, 3, 4 respectively. cgAll type values in the protocol message TLV table are not updated with the values assigned in Table 26.d374g2483 2006/10/31 2006/10/23pESubirFDasGMember^Technical, Binding_165`54a8.4.1.11bUDiscuss and accept the concept described in 21-06-0781-00-0000-MIH_Protocol_Error.pptNcdifferencelWdifferencesWdifferentJW[WW$W>WCWDWWWWWWdifferentiategWdifficultWWdifficult-to-followTWdirectionW7WdirectlyWWWRWfWgWdiscoveredlWdiscoverybWlWWWWWWWWW3W;WgWqWrWdiscoveryisimplicitelyperformedVdiscoverymechanismusinglayer2isinscopeof802.21therrVdiscussTWdiscussedWWdiscussesWdiscussion<WBWCWWWWdiscussionin5.3repeatedlyreferstomihserviceswhichar<VdiscussionofhandoversduetomobilenodemovementisproviVdiscussiontextfromline50pg50toline13page51isoutCVdistinguish-W\WdozWWWW^WdocumentyWWW?WdoesGW`WWWWWWWW#W&W'WFW^W`WaWdWeWgWE/)csection1W2WBW^WeWjWnWvW|WWWWWWWWWWWWWWWWWWWWW!W"W#W+W,W2W4W5W8WSWWWYWZW[W\W^WeWiWpWtWWWWsectionreadsprimitivesareaconceptualrepresentationofSVsectionseemstosayfirstconnectionwithposco-locatedwi[VsectionsWWWWW"WMWfWWsecurityuWWWcific\VsincetheieandtlvsaregoingtobetransportedovertheniVsome0Wsounds^Wspecific\WrWspecificationiWspecifyiWstates2WstatuspWqWstringsEWHWsubscribe:W;Wsubscription1WsubsectionWWfWsuccesspWsuccessful/failureqWsuddenlyuWsuggestpWsuggestthatthestatuscodehaveadditionalvaluesforcatepVsupportedUWswitchsWcthey6WEWHWWWW WUWWWWWWWWthink&Wthis1W2WBWRWSWTW^WbWdWeWfWuWvWzW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWW"W>WWW\W^W_W`WbWdWeWfWgWjWqWsWtWWWWWWWWWWWWWWWWWWWWWthisfigureiscompetingwithfigure26andisinconsistentVthisprimitiveisgeneratedbymihfunctiononnewpoatoinVlinklayershbVthissectionalsodesecribesmihprotocolwithoutackoperatvVthissectiondescribestypesofevents6.1.3talksaboutlocVthissectiondiscussesmediaspecificammendmentswithoutstVsportediWtwoEW#vESubirFDasGMember^Technical, Binding_154`58a8.3.2bA.Rename the Section as "MIH Protocol Operation".@A* 33 *cpThis section also desecribes MIH protocol without ACK operation. Therefore the Section heading should be genericd2338g2492wAccepted 2006/11/16 2006/10/23MarkedwESubirFDasGMember^Technical, Binding_156`6a new Section bbDiscuss and accept the proposal described in 21-06-0780-00-0000-MIH_Protocol_State_Machine.doc. cProtocol State Diagram is always helpful to understand the protocol behaviour and call flows. An implementation independent MIH Protcool State Diagram and its description is felt necessary.d2348g2493valso look at 2330 Work together with registration/deregistration and come back in next round with a more comprehensive contribution. wRejected 2006/11/16 2006/10/23port of information d2065g2491 2006/10/31 2006/10/23vN/ctypeiepoaipconfigmethodsmissinginreportingtemplate8VtypemihfidshouldbetypehdrtlvmihfidasdescribedinHVtypesessionidshouldbetypehdrtlvsessionidasdescribIVtypesaWWW\WgWWWWtypicallyWtypographicalWumts'WWWWunacknowledgedWunauthorizedpWunavailableWunclearEWHW^WbWWWTWWunclearabouthowthetwofieldsinthevalueisencodedinEVunclearwhichpartof6.3.7.1isnormativeandwhichpartis^Vunder2WWWWWW"W5WWundersection7indraftd02.00subsectionnamesareasfollVunderlinedSWunderstandwWxWunecesarily`WunexpectedWunintelligibleYWWunsubscribe:W;WWuntil<WWuntrueWunused)W+Wunusedacronyms+Vunuseddefinitions)VupEWWupdatedoWWWupontW!xESubirFDasGMember^ Editorial_39`29a6.1.4bAAdd the following in Section 6.1.4 after the first sentence. For primitive syntax please refer to Annex G. [Note: Same can be added to subsequent flows where primitives are shown]@call flows. An implementation independent MIH Protcool State Diagram and its description is felt necessary.d348g2493 2006/10/31 2006/10/23xESubirFDasGMember^ Editorial_39`29a6.1.4bAAdd the following in Section 6.1.4 after the first sentence. For primitive syntax please refer to Annex G. [Note: Same can be added to subsequent flows where primitives are shown]@ion is felt necessary.d348g2493 2006/10/31 2006/10/23xESubirFDasGMember^ Editorial_39`29a6.1.4bAAdd the following in Section 6.1.4 after the first sentence. For primitive syntax please refer to Annex G. [Note: Same can be added to subsequent flows where primitives are shown]@ _xctheabortreasontlvcanbereplacedbystatustlvassuccesqVtheadjectivegenericforsapisconflictingwiththedefiniVthecostofaccessingthenetworkmaydifferbetweenroamedVthecurrentdefinitionofthroughputseemstobedefinedwitVthecurrentdraftisnotclearastohow802.3technologyca]Vthecurrentdraftsupportsanumberofmihcommandsthatmig^VthecurrentmihnetsapdoesnothavemihtpdataresponsecVthedescriptionofremotemihcommandinthefigure17andfVthedescriptionoftheackoperationcontainsmanyspecific VthedescriptionoftimersandhowthemihprotocolwouldfunVthedescriptionsofthevalueinfoquerytypeinpage171linenVthedifferencebetweenmihfunctiondiscoveryandmihcapabilVthedraftaimsatenhancingintertechnologyhandoverswhile_VeVthelengthofthetypefieldoftlvforcarryingmihprotocoLVndmessagesinthisfiguredon'tma VPbinformationelementrange0x000000010x000000ffarethecorerVinitiateqWWWWWWinitiatedyWWWinitiatesyWinitiatingWinsecureWinsertsWinsertfollowingtextinline55sVmWinterface~WWjWmWinterfaces^WinterfacingnWintervalcWintoBWlWWWWWW W WWWW!W*W,WFWeWqWintraWintroduceWW!WintroducedW^WintroductionW^Wip8WQWW7W;WNWPWqWipv4NWis1W4W5W7WFWMWPWRWSW\W^W_WdWhWjWlWnWsWuWyW~WWWWWWWWWWWWWWWWWWWW WWWWWWWW'W+W-W.W8WEWFWJWNWQWUWWW^WcWfWlWqW; jxbcLReference to Annex G is necessary to understand the primitive names better. d2109g2494 2006/11/16 2006/10/23yESubirFDasGMember^Technical, Non-binding_43`56a6.2.2.1bALAdd following definition in Section 3: Mobile Initiated Handover: The mobile node initiates the handover process by indicating the network that the handover is necessary or desired. Network Initiated Handover: The network initiates the handover process by indicating the mobile node that the handover is necessary or desired. L@A* 33( *cNo definition on "Mobile-initiated" and "network-initiated handovers". However, these two terms are being used in several places in the document. d2120g2495v-Please also refer to LB-1 comment number 0047wAccepted 2006/11/16 2006/10/23l, Binding_195`12aAnnex A3b]Move TYPE_HRD_TLV_MIHF_ID and TYPE_HDR_TLV_SESSION_ID from Table 32 to Table 26 (page 163).bBroadcasting MIH_Capabity_Discover.response message may include too much information for a beacon. section 8.5.1.2 provide the lists to be broadcas. This includes too much broadcast data to be sent unsolicitedcMIH function entity in the network may broadcast its existence and capability by broadcasting the MIH protocol message, MIH_Capability_Discover.response, periodically over layer 2 data frame.d2333g2275iRonnyjRefer to comment #328m Supercededvsee 328w Superceded 2006/11/16MarkedEPeretzFFeder^Technical, Binding_131`54a 7.4.14.2.1bAThis primitive is generated by MIH Function on new PoA to indicate that MIH_Network_Address_Information Request message is received from a peer MIH Function on old PoA@A*  33  3333*cThis primitive is generated by MIH Function on new PoA to indicate that MIH_Network_Address_Information Request message is received from a peer MIH Function on old PoAQ<bprocedurelWWWwWWWprocedures+W2WWprocessyWWWWprogressWproper1WWproperties_Wproperty:WproposalwWWproposeWW^W`WWWproposedWW!W)W+W-W.W0W1W3W=WhWproposedtextsareneededforthissection3VproposesaWgWprotocol4W6WpWvWwWWWWW)W0WSWhWmWqWrWwWWWWWWprotocolswWprovidebWWWWWpWWWWWWprovideamechanismsuchthatpoacanindicatemaxlengthofVove,W6W{W~Wremoveoptiona1orclarifywhatareotheroptions,Vremovetheabovesentenseinun-authenticatedstagemnshoul~Vremovethesentencehoweverinthisinstancetheopcodemay{VrenamevWrenamethesectionasmihprotocoloperationvVreorg2W^_ ⅃Ↄ≃0⇃∃㦃@㨃㪃P⊃⋃⌃㬃`$Z(㮃)vs‚!+⍃y‚"‚$`⎃"‚%⏃␃‚&‚'⒃Ⓝ┃‚(<╃wx‚1|4z‚27[‚3‚4tu◃‚5☃{‚6♃j㣃‚7,⚃kl|‚8㠃‚9m⣃W‚RA⤃‚T?By‚U⦃‚V67‚Wh‚Xk‚Y89:‚Z;‚a0C~‚br‚ci⪃V‚dD<‚eEFG‚fHIJK⫃=‚gL‚hM‚iNOP‚jQ‚q&‚r'>e‚s8‚uUV[\]^‚w_⬃⮃‚x1l⭃⯃Ⰳ3?‚y+‚zWⱃⲃⳃ ‚eⴃⵃⶃⷃ @‚2XY⸃]‚Z‚3Tf⺃‚R‚‚‚‚‚mbdeletetheunusedacronyms+Vdeletetheunuseddefinitions)VdeletethesetwosentencessincetheinformationisalreadyVdeletethisVdeletethisannexVdeletethisentireparagraphVdelimiterWdeliversWdenial~Wdependent2WWbWoWtWWWdependingnWNWdeployment4WderegMWderegister/W@WTWderegistration+WdescribeW]WdescribewhatmihfunctiondiscoveryisVdescribed^WpWwWWW)W0W8WhWdescribesdWdescription@W_WeWlWWWWWWWWWWWWW!W+W,WEWFWQWUWWWWin21-06-0780-00-0wVdiscussedWdiscussionWdl~WdocwW|W}WdocumentMWhWdoesUWdownWdraftWWWduesWe@WAWQWWWWWWeachlWWWWMW("beitherdefineitinthisdocumentoraddareferencetowher@eitherre-dothemappingagainstmihprotocolpdusorremove@empty@entities@event@events@fa@find@follows@frame@from@ g@@goal@handove@homogeneous@ifcomment3isapprovedupdatedescriptiontofittheevent@zimmediate@ininclude@including@Pinformationelementrange0x000000010x000000ffarethecore@%instance@interfaces@isdefinedas@6itI1item@last@level@linkacommunicationfacilityormediumoverwhichnetworkn@lsap@ityormediumoverwhichnetworkn@lsap@s@mics@=mihcommandid@]mihlinksdutransmitstatus6@mihnetworkaddressinformation8@mlme@vmoble@movesub-section5.6.1.1mihlinksapundermediaindependen@@after@any@Oavoid@NcupperhWWusqWusableRWusageRWSWuseJWKWLWbWcWhWWWWWWW WWqWWWWWWWWuseuppercaseforservicewhileusinginformationservicehVused[WdWyWWWWWWWW W WW*WFWUW]W^WaWkWvWyWWWWWWWPWQWnW{WWvalueisnotclearlydefinedFVvaluesoWpWWWvariableEWHWcWvarialbeWvariants[WvariousWWvender\Wvendor\WverylWviaWvisitedWwant'WWwantingWwantsTWway'WUWWwaysaWweWWwellWWwhat,WIWJWTWWWWWWWWWWwhatismihfunctiondiscoverythisshouldhavebeenintroduVwhatisoption1arethereanyotheroptions,VkchappenBWTWWWWhardJWvWharderWhas1WEWiWWWWWWWWWCWDWTW\WdWgWyWWWWWWWHWIWheaderrWWLWheaderspecificrWheadingvWWhelp;WhelpfulwWhence]Where1WuWWWWWWWWWWW1WhigherXWhlsi+homeWhomogenousWhorizentalWhow1W7WEWHW`WbWcWdWWWWWW WNWXW]WaWhowdoestheqosmodelfitintothemihframeworkhowisit`VhowthemihfidisgeneratedandhowtoavoidconflictionanbVhowtoparsethemacaddressfieldifitisvariablehowwoucVhowwouldthereceiverknowifaipv4oripv6addressisusedVhoweveruWyW{WWWWW\W^WhttpsWi@WAW#W$W&W'WdWQd}c,Figure 12 should be consistent with Figure 4d2089g2272v1 21-06-0826-00-0000-New_Figure12 by comment 2086w Superceded 2006/11/162089g2271v021-06-0794-01-00-0000-Reference-Model_text_5_3_2wAccepted-Modified 2006/11/08}EPeretzFFeder^Technical, Binding_32`1a Figure 12b'Change figure per 21-06-0xxx-00-000.docc,Figure 12 should be consistent with Figure 4d2089ave a "response" opCode. On the other hand, a response message MUST have a "response" opCode according to 8.3.4.1.d2344g2435 2006/11/01 2006/10/23|EPeretzFFeder^Technical, Binding_20`1bJChange per contribution: 21-06-0xxx-00-0000-Reference_Model_text_5_3_2.doccChange section 5.3.2d2054g2271v021-06-0794-01-00-0000-Reference-Model_text_5_3_2wAccepted-Modified 2006/11/01}EPeretzFFeder^Technical, Binding_32`1a Figure 12b'Change figure per 21-06-0xxx-00-000.docc,Figure 12 should be consistent with Figure 4d20894csee1W$W\WWWWWseemW#W7WseemsWW WW6W[W\WWWWseenWselectWselectionBWWWsendWdWgWWWsenderfWsendingWsentence[WWWWWWXWcWsentenceinline1mentionsnetworkusingthemihisprotocoVsentencestatesthatastandardizedformatisusedyettwoaVsentencesWseparate-WsequentialWserverNWservice1W7W:W;WhWtWWWWWWWW WWW]W^WdWgW~WWWserviceanmihposmayactsasanVservice-infoIWservices1W<WjWWWW W^WWservingsWNWWservingfaaddressservingaccessrouteraddressdhcpserverNVservingpoaandtargetpoadefinitionsaretoomuchtiedwitsVsession*W-W/WIWsessionidWWWGcthissectiondoesn'tbelongunder7.2.2mediaindependentsa2VthissectionshouldonlycontainthespecificmihlinksapaVthistextisinappropriatehereandisalreadycontainedappVthoseKWLWthreeWthresholdWthresholdsWWthroughWkWsWWWWWthroughinsecureportwouldVthroughout WthroughputWthrought]WthusWW W\WgWnWrWwWxWzW{W~WWWWWWWtobeconsistentwith7.1.1needasubsectionin7.2.1forlWVtobeconsistentwithfigure15remoteeventillustrationon>Vtobeconsistentwithfigure18remotecommandillustration?Vtomakeitreadbettermovelinkeventnametothe2ndcolum@Vtomakeitreadbettermovemiheventnametothe2ndcolumnAVtopreventfuturemismatchbetweentheprimitivesinthetabeVtoosWtransportuWtransportediWtwoEWyWcprovideeWWW]WpWWWprovidedWW%W&W]WWprovidertWprovides{WproxiedWproxyWpskWpurposeWput3WpuzzlingWqos`W"WWWWqualityWWWWWreadablekWreaderWWreadsWreallyWWrealtionshiptWreasonqWreceipientTWreceiptTWreceivedWW WreceivercWdWreceivesWreceivingWrecent9WrecognizedUWreduceWreducedWredundantWWreferWreference]WrWxW WreferencetoannexgisnecessarytounderstandtheprimitivxVreferences$Wreferencesnotorderedproperly$VreferredWreferringnWrefers<WWWreflectingfWrefuseWregardinguWregisterWregistrant4Wregistrantwouldbeanmihusernotmihfunction4VregistrationWrejectTWrejectedpWi 4~vwAccepted-Modified 2006/11/16a Figure 12b'Change figure per 21-06-0xxx-00-000.docc,Figure 12 should be consistent with Figure 4d2089g2272 2006/10/31~EPeretzFFeder^Technical, Binding_50`1a Figure 12b'Change figure per 21-06-0xxx-00-000.docc,Figure 12 should be consistent with Figure 4d2089g2272 2006/10/31~EPeretzFFeder^Technical, Binding_50a "response" opCode. On the other hand, a response message MUST have a "response" opCode according to 8.3.4.1.d344g2435 2006/10/31 2006/10/23|EPeretzFFeder^Technical, Binding_20`1bJChange per contribution: 21-06-0xxx-00-0000-Reference_Model_text_5_3_2.doccChange section 5.3.2d2054g2271 2006/10/31}EPeretzFFeder^Technical, Binding_32`1a Figure 12b'Change figure per 21-06-0xxx-00-000.docc,Figure 12 should be consistent with Figure 4d2089g2272 2006/10/31~EPeretzFFeder^Technical, Binding_50 vprimitiveW'W.WprimitivesjWWW W!WSWuWWWprocedurelWW3WwWWproperties_WproposalWproposed=WprotocollWpWuW0WSWwWWWWWWprotocolsuWwWprovideuWWprovideduWWxWWprovidesWjW{WprovidingwWputmWqos`WWqueryUWnWoWeWWWquery-resourcesWquite0WWr`W9Wr1zWr1/r3/r4/r5zWr3/r4/r5zWradiusaWrateWWrdf[W]WWre-registration.WreadWreasoningWreceiptWreceivedWrecommendWWWW_WremoteWjWvWremoveWWW,WyWremoveanih-aaahmipyVremovelinkidentifierfromtheparameterdescriptiontableVremovesection8.2.1Vremovethefigure24andtheparagrahabovefigure24froms,VrephraseSWS+borderZWiWlWZWoriginallyWoriginatesWWother,WWWWWWEW[WmWqWWWWothererrorsstatus0indicatesEVothersgWout1WCWWWoutsideuWWrWoverWjWkWWWWp152WpackerWpacketWZWpackets6WmWWpaddingJWpagelWzWW W"W#W%W&W9WnWparagrah,WparagraphWWWWwWparameterRWSWNWfWWWparametersYWWWWWWCWDW\WWparametrsnWparsedWpartQWwWWWWparticularTWWWpartnerWpartspWpatametersWpayloadmWpduFWAcmobile-initiatedyWmobilityWWWWmoblelWmodeWWFWmodel`WWW4WmonitorZWmonitoredZWmonitoring]WmoreUWWWNWgWmWpWWWWWmoreclarifyingtextisrequiredtoshowproperrelationshipmVmotivatedWmove@WAWtWWmovedtWmovementWmovingWWmuchGWsWW WWmultinWmulti-hopWWmulti-linkWmultipleNW]WmustTW{WyWzWWWmutipleWnWn-entity)vWn-event)vWn-layer)vWn-thingyWn-trigger)WvWn-user)vWname@WAWWWWWWWWWWW WUWnamesxWW W WWnamingWWWnaminginconsistencywithtableandsection7.6xV9?aandlWannexzWWWW W W WWW2WRWiWWWWannex1.3Vannexa-4Vannexa12ViVannexa1.2Vannexa1.3 Vannexa2 VRVannexa3zVannexa4 VVVVannexbVannexeVannex-a1bWcwWeWxWfigure}Wfigure12}VnewwWnewsectionwVsectionwWxWb0WWWWWEW0speedV0-127W0x00000001rW0x000000ffrW1,WCWHWJWfWoWWWWWWWWW WWWWW+W,W7W9W:WEWFWMWNWOWRW\W`WgW~WWWWWWWWtandthesecondmihgetstatusprimitivesV1changethetitleandthetabletitlemappingmihprimitive V1changetypeiepoaaddressintable6andfigure20totyp:VWW WW9W.{l) none needed 2006/11/16`37bReplace "betwen" by "between"cfacilitating handover betwen d2002w Withdrawn network entity, the MIHF in the new PoA further delivers this message to the MIHF peer in the old PoA. When the mobile node receives this primitive,@Af  33        33fcWhen the MIHF in the new PoA receives this message from the network entity, the MIHF in the new PoA further delivers this message to the MIHF in the old PoA. When the mobile node receives this primitive,d307g2277iRonnyjRefer to comment #303m Superceded 2006/10/31EGolmieFNadaGMember^ Editorial_vi`37bReplace "betwen" by "between"cfacilitating handover betwen d2002w Withdrawnomment #303m Superceded 2006/10/31EGolmieFNadaGMember^ Editorial_vi`37bReplace "betwen" by "between"cfacilitating handover betwen d2002w Withdrawn&nicSince the IE and TLVs are going to be transported over the network, both peer has to have the same decoding methods for both TLVs and IEs. The specification should specify the byte order for the Information Elements.d2155g2471v^Byte ordering is defined by transports. Not clear if this needs to be included in 802.21 spec.wRejected 2006/11/16 2006/10/23fcSince the IE and TLVs are going to be transported over the network, both peer has to have the same decoding methods for both TLVs and IEs. The specification should specify the byte order for the Information Elements.lds may be stored in network byte order.@Af 33p  v } 33 fcSince the IE and TLVs are going to be transported over the network, both peer has to have the same decoding methods for both TLVs and IEs. The specification should specify the byte order for the Information Elements.bsubnetsPWsubscribe:W;WWsubscriber5WWWsubscriptionW?WWWsubscription/registr$WsubsectionWW%W'WWsubsectionsgWlWsubsequentxWwWsucceedWsucceededWWsuccessfulEWsuccessfullyEWsuch4WWmWwWWWWWWsucharesponseasdefinedinthespeccanbefairlylargeaVsufferWsuggestWsuggestedDWW$W'W,WsuggestednewlinklistWsuggestednewpoalistWsuggestions WWsuitableWsummaryWsupportUWlWgWqWWsupportedlWWEWWWsupportedcommandlistWsupportedeventlistWsupportingWWjWsupportsgWrWiWnWrW|WWWWWWtextual_WtexualWthat4WCWQWUW\WcWjWlWsWyWWWWWWWWWWWWjparametersWpartW!W*WparticularWpeerlWWpeerslWperoWperformlWperformedlWperformslWpgaWWphyWphysicalWpicoWpleasenWoWWWWpleaserefertocomment71forsuggestedremedyVVpoasWWposWpossibleWpossiblynWpreconfiguredlWprocedurelWW3WpropertiesWprotocollWsWWWWWWprotooclWprovideWWprovidedescriptionofthemappingfunctionaspartofmihfVquerynWoWWradiusaWralationNWratherWent336Vreferences]WreferredWregisterlWremedyWWremoteWrepresentation[WWrequiringWresource[W^Wright]WrouterNWsamelWschema^WWWsection1W^WWW3WsecuirtyWsenderdWsentdWsentencelWserverNW@EGolmieFNadaGMember^ Editorial_1`41a1.1b Remove "etc."caWhen using e.g., etc. is not permitted, since your are listing examples. Etc. is not an example.d2004g2241 2006/11/16EGolmieFNadaGMember^ Editorial_1`62a1.2bTo improve the readability of the text it may better to provide a brief summary of the requirements that are discussed in reference [19].ciThe reader is referred to the draft requirements document for an overview discussion of the requirements.d2006g2303 2006/11/16EGolmieFNadaGMember^ Editorial_2`7a1.2b3Delete lines 7-9 starting with " As an example...""cerence [19].ciThe reader is referred to the draft requirements document for an overview discussion of the requirements.d2006g2303 2006/10/31EGolmieFNadaGMember^ Editorial_2`7a1.2b3Delete lines 7-9 starting with " As an example...""ca1.2EPeretzFFeder^Technical, Non-binding_134`34g4765 2006/10/24(bprovideinformationaboutgeneratingthemihfidbVprovidemoretextandmechanismsordeletemihnmssaprelatpVprovidedqWWyW"WquerynWWWWEWeWquerytypestatus1isusedforEVqueryresourceflagWqueryresourcelistWquotationXWr1RWr2RWr4RWr5RWrangerWWWUWrateNWWrdf^WWre-do6Wre-order$WZWre-orderlinkdetectedintable17tothesameorderasintZVre-orderreferences$Vre-registraion$Wre-registration+W.Wread@WAW"Wreadability<WWWreasonqWreceipientTWreceiptTW$Wreceive4WreceivedWcWreceivesWreceivingdWWrecognizeUWrecommendWrecommendthatitisclarifiedthatfunctiondiscoveryatl3VreducingYWreferrWxWreferenceMW]WWWW WihprotocoloperationvVreorg2WcoveralljWoverheadWoverviewWownGWVWWpWp195HWIWp802.21/d02.00WpacketWWWWGWZWdWWWpacketsW WGWpadWpadding/alignmentJWpageCW^WmWnWW%WWpage46line48aswellVpairWWpairsuWparWparagraphW,WwWparagraphcinadequatetocommunicateanyusefulinformationwVparallelWparameterRWSWWWWW#WNWaWfWgWWWparametersYWWWWWCWDWWWparametertypeWWparsecWpart1W^WWSW^WWparticularWWWNLscaWhen using e.g., etc. is not permitted, since your are listing examples. Etc. is not an example.d2005g2242 2006/11/16EGolmieFNadaGMember^ Editorial_4`13a1.5bRemove "generic"cbThe adjective, generic, for SAP is conflicting with the definition of a Service Access Point (SAP)d2018g2243 2006/11/16EGolmieFNadaGMember^ Editorial_4`19a1.5bWRewrite this sentence so as to clarify what core elements are, or remove this sentence.c[The sentence states core elements are developed and does not indicate as to what they are. d2021g2244 2006/11/16Member^ Editorial_1`42a1.1b Remove "etc."g2304 2006/10/26EGolmieFNadaGMember^ Editorial_2`47a1.2b%replace with "enabling more effectivec7line 47 reads: "thus enabling making of more effective"g2305 2006/10/26EGolmieFNadaGMember^ Editorial_1`42a1.1b Remove "etc."hdrawn{l) none needed 2006/10/24cHbwhenthemihfinthenewpoareceivesthismessagefromtheVwhereMW^WxWWWWWWWWFWlWWwhereasmWwherever WwhetherEWrWwhichRWSWUWdWlWnWWWWWWW W WjWWWWWWWwhilegWWwhithinlWwholeWwhoseFWwhyWwillTWUW~WWWWeWgWWWWwillprovidetextlaterVVwithEWHWlWmWnWrWtWWWWWWWWWWWWWWWWW WWWWWWWWWWW"W,W@WXW[WcWjWmWnWwWWWWWWWWWWHWJW_WaWzWWWWW-W\W1and2donotbelongtothistablethesearetlvsnotieszV1annexcshouldbeannexb_V 6bgxWNWqWwWWWWWWgeneral+WvWWgenerated4WWW'WgeneratesTWgeneratingbWgenericWWgeograpicalWgernericbWgetYWWW W WWRWWWgiveWWgivenWWandoveWWhandovereWgWqWyWWWW'W6W\WmWwWWhandoversignalingprocedureaspartofhandoverexecutionawVhandover-prepareWhandoverswWhandoverstatusWhappenTWhasW$WmWhavelWWWW\WrWwWhavingQWhavingtexualdescriptiononthosefiguresismorepreferablQVhdrzWheaderrWWW*WfWheadertypeWheadingWWWhelpmWhereWheterogeneous{W|WhighermWqWwWWhighlight Whih:WhistoryWho2Whomegeneous{W|Whomegeneousandheterogeneous{VW5cmihs+mii+miisUW^WeW{WWWWWmiisprovidestheabilitytoaccessinformationaboutallhe{VminWminimumWminimum/maximumWminimzeWminusWmipWmismatcheWmissing8W=WJWKWLWMWNWOWXWYWWWWWWW+W.W3W@WJWKWNWOWYWWmissingmihlinkdetectedVmisspellingWmisspellingofpacketVmlmeWsWmnlW~WW-WWWWWWWWWWmnshouldhavecapabilitytochecklink/networkresourcesinVmn'sWmn-controlledxWmn-initiatedxWmnsWWmobileWWWWWWW.cshowDWWW]WkWmW1WDWWWshowsdWsiWside3W>W?WsignalZWsignaling]Wsimilar^Wsimple[Wsince\WiWrWWWWWWWWZW\WfWjWlWsince802.11udecidestoacceptmihmessageexchanveoverlalVsinceextendedschemashouldalwaysbevenderspecific\VsincetheieandtlvsaregoingtobetransportedovertheniVsingleWsitWsize`WsnrUWsoWWWWsome0WWWW-WsomeprimitivesareusedwronginthisfigureVsomewhereWsounds^WsourceW WfWsourceidentifierfWspecific\WrWWWWWWW WgWjWspecificacally_WspecificallyWspecificationiWWW W WW+W3WGW^WspecificationsWWWspecifiedWW-W/W=WNWVWaWcWWualbert㈃㉃㊃㋃㌃㍃benjamin cheng`abcddavid{eleanoreric45eunah golmie⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⳃⴃⵃⶃⷃ⸃⹃⺃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃guiming/guoWhongseokjamesjin#$%&'jingWWWjunghoonjunxiang㒃㓃㔃WkenichikentaroliuWWWmasahiro!"pengWWW"cwhethertWWWWwhethertheinformationissensitiveornotwilldependupontVwhich<W[W^WgWlWWWWWWWWWWW W"W;W\WdWkWlWWWWWWstartofframedelimiterneededinthemihVwhyisthisincludedVwillTWtWWWwith>W?WWWlWoWsW}W~WWWWWWWWWWWWWWW WWW"W$W&W)W0Wwiththecurrentdraftidon'tseeanydifferentactionfor$VwithoutJWKWLWvWWWWWwithouttheabovedetailstheiewouldbehardtouseJVwonkyWwords Wwould4W5WJWKWLWcWdWqWWWWW#W&Wwrong]WWWWWWWWwrongnameVVVxaWWxml[WWWxml/rdfWbreferences$WWreferencingWrefersWreflect9WWreformatWWregMWregisterlWW@WregisteredWregisteredeventWregistrant4WregistrationW$W+W,W-W.W1WTWaWreintegratedWrejectTWrelated7WW7WpWrWWWrelocate1WremaingWremaining"Wremedy"W+W,W-W.W1Wremote>W?WWWW7W@WjW~WWWWWWoraddsectiontodiscussotherhandoveVremovesection5.2Vremovesection7.5Vremovetheabovesentenseinun-authenticatedstagemnshoul~Vremovethehistoryandscopeparagraphstartingatline20aVremovethesentencehoweverinthisinstancetheopcodemay{VremovethissentenceVVrenamevWWrenameheadingtomihlinksapprimitivesVrenamethesectionasmihprotocoloperationvVreorg2W dÄ2>Ä2xÄ2!Ä2"Ä2#WÄ2$@Ä2%Ä2&AÄ2'Ä2(Ä2)?Ä2*BÄ21yÄ22~Ä23Ä24Ä25Ä26Ä27Ä286Ä297Ä2:hÄ2AÄ2BÄ2CÄ2DÄ2EÄ2FkÄ2GÄ2HÄ2I8Ä2JÄ2Q9Ä2R:Ä2S;Ä2TÄ2UÄ2V0Ä2W~Ä2XÄ2YCÄ2ZqÄ2aÄ2bÄ2crÄ2drÄ2eÄ2fiÄ2gVÄ2hÄ2i<Ä2jDÄ2qÄ2rEÄ2sFÄ2tGÄ2uÄ2vHÄ2wIÄ2x=Ä2yJÄ2zÄ2Ä2Ä2KÄ2Ä2LÄ2Ä2MÄ2NÄ2OÄ2PÄ2QÄ2Ä2Ä2Ä2&Ä2>Ä2Ä2Ä2Ä2Ä2Ä2Ä2'Ä2eÄ28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3Ä3_Ä3Ä3Ä3Ä3Ä31Ä3Ä3Ä3!Ä3"?Ä3#lÄ3$3Ä3%Ä3&+Ä3'Ä3(Ä3) Ä3*0^.ctiedsWtimeGWaWcWWWtimer WtimersWtimestampWtitle1WgWW"WtitlenotclearofwhichtypeofhandovertheprocedureisdgVtitlesWtlv'W8WDW[WmWoWqWrWWW>WHWIWLW\WtlvsiWrWzWto'W0W1W3W6W7W9W<W>W?W@WAWCWEWHWJWRWSWTWUWVWWW]W`WaWbWcWeWfWiWlWnWrWwWxWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWW W!W#W$W&W'W)W*W-W0W9W:W;W=WFWGWLWMWVWXWZW[W\W]W^W`WW|cconflictionbWconflictsfWconfuseWconfusesWconfusing3WWWWWW\WWcongestionWconjunction*WconnectWconnectedlWWWconnectionWZW[W^Wconnection-lessWconnection-orientedWFWconnectionsW[W^Wconnectivity]WconsecutivedWconsiderWconsideredWconsidering;Wconsideringinter-mediahandoveroptimizationlikepre-authe;Vconsist WconsistencyWWconsistent>W?WWWaW}WWW WMWWWWconsistentlyWconstrainedWcontainWWcontainedW-WFWcontainer>WcontainersWcontainsWWWW W\WeWfWWcontent\WcontextWcontinuity]WcontributionuWWWWWWW)W0WPWhWcorrectspellingofhomogenousVcorrectsyntaxVcorrectedW vdefineWdefineitasintegerOVdefinevaluesasfollows%VdefinedMWRW_WiWmWwWdefinitionRWWdefinitionsWWWdelete7WIW[WWrWvWxWyWWWrWvWxWyWWWoyment4WdescribeRWWdescribedRWSWW!WdescriptionWdetailRWdetails`WdidUWdifference_WdifferentW WwWxWWWdirectlylWdiscussionWdisregard,WdoSWWlWvWdocumentvWdoes`WW,Wdoesn'tWdont$Wdown_Wdraft+WyWWdrawkWewWeachRWWeachlinkhasauniqueidentifierVeditor+WeW,WvWyWeditorcheckforuseoftheseacronymsindraftbeforedelet+VeditorpleasenotethiseVeditorialcWWeffectivelyWefficiencywWeitherwWelsevWembededlWenablesuWendpointsW0/24 cthesameexampleisgiveninsection1.2withoutanyquantitVthescopedescriptionshouldbeidenticaltotheieee802.21Vthesection1.4discussedmediaindependencewhilesection1VthesectionimpliesthatsignalstrengthandpacketlosswilZVthesectioninunintelligibleaswrittenthereis/aremissinYVthesectionsformediaindependentinformationserviceseemsVthesentenceiflinkdownisnotreceivedwithinthespecificVthesentencestatesbothprimitivesandmessagesbutitisnVthesentencestatescoreelementsaredevelopedanddoesnotVthesentencethenatureofmihcommunicationmayimplyuseoVthesessionidcreatedduringmihregistrationproceduresho/VfullydefinedforthegenerictVthetypevaluesusedinsection8.5.2donotmatchtheonesVtheuseofn-thingydefinitionsintheterminologysectioniVthevalueipversion6prefixavailableinpoacapabilityie&VVVa?=kbridgingWbroadcastWbroadcastingWbut scnote2W~WWW^WgWnotedoesnotbelongtospecificationsVnotethisisforsystemmanagementservicecategoryandthegVnothingWnoticed#WnotifiesWnotionWnowDWWnumberW^WgWWnumbersWofWo7.4.2.1mihcapabilitydiscoverrequestfVo7.4.2.2mihcapabilitydiscoverconfirmfVo7.4.3.1miheventsubscriberequestfVo7.4.3.2miheventsubscribeconfirmfVo7.4.4.1miheventunsubscriberequestfVo7.4.4.2miheventunsubscribeconfirmfVo8.5.1.4mihregistrationresponsealso7.4.1.2fVo8.5.1.5mihderegistrationrequestalso7.4.1.3fVo8.5.1.6mihderegistrationresponsealso7.4.1.4fVW W W WWWW W!W"W&W)W0W6W7W8W9W;W<W=W>W?WCWDWEWLWNWPWSWUWVWXWZW[W\W^W_WdWfWationareoutsidethescopeV<^clA column heading of Remote direction is included in the table 3, yet no explanation exist for what it means.d2116g2260 2006/11/163EGolmieFNadaGMember^ Editorial_44`31a6.2.2bsreplace lines 44-45 with the following: The MIH commands are generated in the upper layers and destined to the MIH.ccorrect syntaxd2123g2314 2006/11/16EGolmieFNadaGMember^ Editorial_44`62a6.2.4bFix inconsistencycText states that use case and handover are in the Appendix, yet no Appendix exists. Handovers procedures are shown in Annex A1, but no user scenarios. d2124g2262 2006/11/16EGolmieFNadaGMember^ Editorial_46`60a6.2.5.2bFix inconsistencycjTable is missing link commands including link event discover , link event subscribe, lnk event unsubscribed2130g2315 2006/11/165EGolmieFNadaGMember^ Editorial_50`27a6.3.3entire paragraph.a6.1.5bDelete this entire paragraph.d35g2256ccdetailedRWSW!W5WWdetailsJWKWLWMWNWOWPWQWW WNWWdetectWdetectedZWWdetecting]WdetermineWGWWWdevelopedWWdeviationWdhcpNWWdhcpv4NWdiagramwWWdiagramsWdiconnected'WdifferW@cany'W,WWWW$W^WdWlWwWWWWanywhereWaplWWappearWappearedfWappearsWWappendixWWappliacbleWWappliacbleshouldbeapplicableVapplicableWW&WapplicationWappliesRWSWTWfWapplyWapproach"Wappropiate{Wappropriate"WWappropriatelyWare,W:W;W<WDWEWHWJWaWiWnWoWrWsWuWyWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW"W)W0W5W?W@WKWMWNWOWSWUW\W^WdWgWhWyWWWWWWWWWWWWWWWWWWW W$W'W?WEWHWIWLWW%bincludingW#W4WqWWinconsistencyWWWWWWWWWWWindWindentWindependenceWindependent2W5W[WqWrWWindicatecW{WWWWWindicatesWWWWWEWindicatingyWW6WindicationWWCWFW\W_WWindividual_WWWinfomationWinfoquerytypenWinformation'W7WCW_WbWhWiWrWtWuW~WWWWWWWWWWWWWW WWW7W8W9WCWDWEWRWjWqWrWwWWWWWWWWWWW8.{EDavidFFamolariGMember^Technical, Binding_155`16a8.3.2bAhRemove the sentence: "However, in this instance, the opCode may indicate an appropiate response value." h@A* 33  *cAIn MIH protocol description, it says that "However, in this instance, the opCode may indicate an appropiate response value." This implies that a response may have a "response" opCode. On the other hand, a response message MUST have a "response" opCode according to 8.3.4.1.d2344g2435wAccepted 2006/11/16 2006/10/23Marked|EPeretzFFeder^Technical, Binding_20`1bJChange per contribution: 21-06-0xxx-00-0000-Reference_Model_text_5_3_2.doccChange section 5.3.2d2054g2271v021-06-0794-01-00-0000-Reference-Model_text_5_3_2wAccepted-Modified 2006/11/16Marked}EPeretzFFeder^Technical, Binding_32`1a Figure 12b'Change figure per 21-06-0xxx-00-000.docMarkedg4791g\brewritethissentencesoastoclarifywhatcoreelementsarVrightWroamingWWrolewWrollbackW\WrouterNWrowWWWWWWWW#W&Wrows$WUWrssiWrttWruleVWrunWrunthespellcheckerontheentiredraftVs1WWWsaWsameZWnWxWWW WCWDW\W_WgWqWrWWWW5Wsatisfy^Wsay[WscanWscenariosWschema\W^W_WWWWWW:WschemeWscopeuWWWsduWsecondWW[Wsection1W3WCWeWfWiWlWoWvWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!W"W,W3W4W5W8W9W:W?WFWJWMWNWWW[W_W4*bopcode{WoperationvWW WoperatorGW9WWWoperatorsGWWoptionWoptiona,WoptionalQW>WeWWoptionallyWoptions,Wor,W6WCWEWGWHWIWMWUWdWgWyWWWWWWWWWWWWWWWW W6W7WEW\W^WpWqWrWwWWWWWWWWWWWWWWWWWWWWWHcyetWWWWWyourWWzeroWd +`< p7⁃,₃=>‚!@‚"A‚#?‚$B‚%0‚&C‚'D‚(E‚)F‚*G‚1H⅃Ↄ⇃‚2I‚3J‚4K⋃‚5L⍃‚6M‚7N⒃Ⓝ‚8O‚9P‚:Q‚A'‚B8‚CU‚DV⛃‚E[‚F\‚G^⟃⠃‚H]‚I_‚J1⥃‚QW‚R2⧃‚SX‚TY⪃‚UZ⬃⭃⮃⯃‚V3‚WT‚XR‚YS‚Z4‚a5‚b:‚c6‚d;‚e9‚fƒ‚g‚h‚iтj‚q‚r‚s‚t‚u‚v‚w‚x‚y‚z‚ۃ܃‚‚‚‚‚‚+bthe'W)W+W1W4W5W6W7W9W:W>W?W@WAWBWCWEWFWGWHWJWKWLWNWOWPWQWRWSWTWUWZW[W]W^W_W`WaWbWcWdWeWhWiWjWkWlWnWpWqWrWsWtWuWvWwWxWyW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWW W!W"W#W$W%W&W'W)W*W+W,W-W.W0W1W2W4W6W8W9W:W<W=WCWDWs xie$'()+,0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_yuan ^binding'W,W1W4W5W6W8W9W:W;W=W>W?WEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWXWYW\W_W`WaWbWcWdWiWlWmWoWqWvWwWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WW W!W)W*W+W-W.W/W0W1W3W4W6W7W8W9W:W;W<W=W>W?W@WCWDWEWFWGWJWKWLWNWOWRWSWUW\W]W^W_W`WaWbWcWdWeWfWgWhWjWmWoWpWqWsWzW{W|W}W~WWWWWWWWWWWWWWkcmiheventsubscribeandmiheventunsubscribearecommandse:V;Vmiheventsubscriptionarecategorizedascommandintheres?Vmiheventsubscription/registrshouldbemiheventsubscriptAVmihfunctionentityinthenetworkmaybroadcastitsexistenVVmihhandoverproceduresdescribedintheannex1arenotconVmihlinksapisrepresentedinvariousexpressionswhichareVmihnetsapismissinginfigure12=VmihnetsapisonlyfordataplanetransportthisisnotclejVmihnetsapseemstobeusedformihtransportservicebutmVmihnetsapseemstobeusedformihtransportservicesbut Vmihnetsapseemstobeusedinl2andl3transportservicesVmihnmssapisjustoneofthemediaindependentsapslisted3Vmihprimitivesdon'tneedtobemappedintoreferencepoints V3gppWmih-linkWmihf1WbWlWmWWWWWWWW)W*W0WWmihfsWDcmihs@Amobile-initiated@5narrow@network@|nformation@not@ note@Loam@sobvious@ofofthisinformationareoutsidethescope@roffered@conlypdusnotprimitivescanbemappedtoaninterfacebecau@others@overall@=partner@pg@lpreferedpoalistlistedbutnorowispresent@protocolstatediagramisalwayshelpfultounderstandthep@provide@1quantitative@range@Creferencesnotorderedproperly@[inkeventdiscover@that@dthe@), theabortreasontlvcanbereplacedbystatustlvassucces@$thelengthvalueofthelengthvarialbefirstoctetcannott@thenamesofprimitivesandmessagesneedtobeconsistentt@thesameexampleisgiveninsection1.2withoutanyquantit@Jthesessionidshallbeusedinallmihmessagestoavoidco@ thevaluesofsomeelementsarecodedwith4bytesgivingva@ bC resources are available, the MIH Function on the serving network may send MIH_Handover_Initiate.response to mobile node. If the queried resources are unavailable, the MIH Function on the serving network may again send MIH_Handover_Prepare.request to another candicate network to query the available link resource. This procedure may repeat untill resource query succeed or utill some criterias are satified, e.g. timer has expired or up to maximum retry times, then MIH Function on the serviDng network will send MIH_Handover_Initiate.response to mobile node. 7.4.12.4 MIH_Handover_Commit.confirm 7.4.12.4.4 Effect on receipt Upon receipt, the old Serving PoS may start forwarding any pending or remaing packets to the new Target PoS. The client recipient may initiate handover process and begin setting up of new layer 2 connection in case the handover is to be performed. In case of the handover is to be aborted, the client recipient may initiate once more handover initiating proce. dÄ4A0Ä4BhÄ4CÄ4DÄ4EÄ4FÄ4GÄ4HÄ4IvÄ4JÄ4QÄ4RÄ4S Ä4TdÄ4U{Ä4VÄ4WGÄ4XÄ4YwÄ4ZbÄ4aHÄ4bIÄ4cJÄ4dÄ4e*Ä4fÄ4gÄ4hÄ4iKÄ4j:Ä4qmÄ4rLÄ4sÄ4tcÄ4udÄ4vpÄ4wÄ4xÄ4y\Ä4zÄ4%Ä4Ä4nÄ4gÄ4oÄ4Ä4Ä4fÄ41Ä4MÄ4Ä4aÄ4Ä4qÄ4NÄ4OÄ4PÄ4Ä4Ä4 Ä4gÄ4Ä4Ä4QÄ4Ä4 Ä42Ä4Ä4RÄ4iÄ56Ä5;Ä5Ä59Ä5zÄ5Ä5 Ä5Ä5Ä5Ä5!Ä5"Ä5#Ä5$Ä5%ction of the Media Independent SAPs. However, the MIH_LINK_SAP is listed in the introduction (Section 7.1.1, p 69) as a Media Dependent SAP. The latter is correct.d229g2224 2006/10/31 2006/10/23EAjayFRajkumarb5|WWW WWWW5mihcandidateselectV5---linkW5.1.3"W5.1.8W5.2W"W5.2.1"W5.2.2"W5.3<WW5.3.24W5.4<W5.4.2BW5.6.1.15W5.6.1.2W5.6.1.3nW5.6.1.7W5.6.25W5.6.2.3oW5.7W5.8W51-59"W52lW55sW6W:WWW6mihqueryresourcesV6.1.4xW6.1.5WW6.2.2.1BW6.2.5.1W6.2.5.2W5DEEunahFKimGMember^Technical, Binding_34`3a5.6.2.3bhe text d) as follows d) MIH_NET_SAP : Media-independent interface which provides L3 transport services on the local node, supporting the exchange of MIH information and messages with remote MIH Function;@A> 33 3333 33>cMIH_NET_SAP seems to be used in L2 and L3 transport services but MIH_LINK_SAP is also used for L2 transport, which is duplicated and confusing.d2072g2230iRonnyj0Please refer to Comment #71 for suggested remedyk 33)  i  >cThe descriptions of the value "InfoQueryType" (in page 171 line 31 and page 172 line 8) are referring to "IS Query Type" in section 8.4.1.4.d2372g2482i Vivek GuptajChange "InfoQueryType " to "IS Query Type List" in 8.4.1.35 and 8.4.1.36 and possibly throughout the draft. Please look at 8.5.4.1 and 8.5.4.2 as well....mAccepted 2006/11/15 2006/10/23oESubirFDasGMember^Technical, Binding_173`49a8.5bcFix all TLV type values in section 8.5. According to Table 26, it should be 1, 3, 4 respectively. j 2006/10/23 2006/10/24g4803 2006/10/24#`‚DI╃H‚E₃⿃NX‚F⡃ⲃ6‚G_ƃ݃ 㗃㨃‚Hh⃃◃⺃‚I1J=㐃‚R⅃⯃‚S≃‚T,Z‚Ur‚V)W⎃̃‚WFa┃✃/‚XS[∃⬃‚Y'0‚ZY`o⍃⫃⮃"‚aC~⟃:‚b‚c⾃ǃ‚dm‚eB\p⁃ƒ‚fKă‚g@^qy⹃‚h▃‚iGtv˃Ѓك‚j]‚ql‚r(u 3‚sTↃ‚t8‚u␃σ-‚va1.1⅃1.2Ↄ⇃∃1.3W1.5⊃⋃12}W2$3()s4+5.1.25.1.3`⏃␃⑃"5.1.8⒃5.1.95.25.3<5.3.1╃5.3.2745.4.1.45.4.2.35.4.3tu☃5.5,♃⚃5.5.4⛃5.6=❃➃!5.6.15.6.1.15rcofferedWoftenWoldWW'WWWoldaccessrouteraddreWolderWGWoldfaaddressWommunicationWon>W?WTW[WyW{WWWWWWW WGWNWQWVWZW^WeWzWWWWWWonceWone3WEWHWUWmWWWWWWWWFWNW\W^WWWone-directionalWonesW Wonly'W6WDWEWHWpWWWWWWWWWWWW W8W>WZWdWgWjWpWrWWWWWWWrderingforcurrentaccessrouteraandcurrentfaaddressinlVorderingforoldaccessrouteraddreandoldfaaddressinlistaVorg/regauth/ethertypWorganizationWorganizedWother,W{WWWotherwiseeWoui+out3W9WBWCWZWWoutsideuWoveriWW)Zcthat1W2WEWHWUW\WlWpWuW{W~WWWWWWWWWWWWW W-WCWDWEWGWNWSWZW\W]W^WdWeWfWgWWWWWWWWWWWWWWWWWWgWiWjWlWmWnWoWpWqWrWtWuWvWwWxWyW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWW W!W"W$W%W&W'W)W*W+W+EGolmieFNadaGMember^ Editorial_71`1a7.2.2.1bKAdd a new column cross referencing where each entry in the tabe is defined.cXNo clear relationship with primitives in this table and the text in sections 7.3 and 7.4d2225g2270 2006/11/1615EGolmieFNadaGMember^ Editorial_71`1a7.2.2.1bkAdd a new column containing the appropriate type (i.e., req, ind, conf, or resp) for each listed primitive.c=Not clear what types of primitives exist for each item listedd2226g2271 2006/11/1615EGolmieFNadaGMember^Technical, Non-binding_71`14a7.2.2.1bNAdd descriptions of missing primitives in the appropriate place in section 7.4caMany Primitives listed in this table are not described in section 7.4. No 4, 5, 6,7,8,10, and 11d2228g2275EGolmieFNadaGMembersp) for each listed primitive.c=Not clear what types of primitives exist for each item listedd2226g2271 2006/11/0215EGolmieFNadaGMemberFK m^bAWe propose the introduction of a new set of primitives that serve as a "blueprint" for the specification of behavior that is expected from link layers when the primitive requesting the manipulation of link layer connection or interfaces is issued. It does not constrain any specific implementation as the primitives are abstract representations. Therefore any primitive that is already specified within specific link layer technologies that satisfy the functionality specified in this primitiveBf can be mapped to the Link_Switch primitive introduced in document 21-06-0737-01-0000-SwithCommand.docTcives exhibiting similar behavior may be found in existing link layer technologies. An example of these references can be found in section 7.4.7.1.3 "Effect on Receipt d2278g2301wDeferred 2006/11/16H_deregister are not included in this table, but are listing in 7.4 as key primitives as part of the MIH_SAPd48g2269 2006/10/2615EGolmieFNada~RbrewritethesentencestartingwithexamplesincludetostateVrewritethesentenceusingonlytvlwhichisstatedin5.7aVcsureWswitchsW'W^WswitchesWsynchronisationWsynchronisedWsynchronizationWWsyntaxWHctwoexamplesofschemaarediscussedwithoutspecificallystVEGolmieFNadaGMember^Technical, Binding_79`34a7.3.7.2bICopy encoding information from section 8.4.1.20 in the Description field.c`The Link Parameter Type uses a pair of {LinkType:ParameterType} but does not define the format. d2248g2224v8.4.1.20 seems to be incomplete as well. Also, seems odd to have examples in the table, maybe move them to text. Accept upon receipt of contribution giving the new table.wAccepted-Modified 2006/11/16MarkedEGolmieFNadaGMember^Technical, Binding_80`41a7.3.8.2bICopy encoding information from section 8.4.1.20 in the Description field.c`The Link Parameter Type uses a pair of {LinkType:ParameterType} but does not define the format. d2249g2228vSee comment 248ical, Binding_80`41a7.3.8.2bICopy encoding information from section 8.4.1.20 in the Description field.c`The Link Parameter Type uses a pair of {LinkType:ParameterType} but does not define the format. d2249g2228vSee comment 248s. HbmeetWmergeWmergesections1.4and1.5underasingleheadingmediaindeVmessage(WnWqWWWWW WWNWTW_W`WgWmWWWWmessagesWWW W W W\WdWjWmWsWWWWmethodNWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WmihcommandidVmihconfigure2VmiheventidVmihgetstatus0Vmihhandovercommit6Vmihhandovercomplete7Vmihhandoverinitiate4Vmihhandoverprepare5Vmihlinkdetected3Vmihlinkdown1Vmihlinkeventrollback5Vmihlinkgoingdown2Vmihlinkhandovercomplete8Vmihlinkhandoverimminent7Vmihlinkparametersreport4Vmihlinksapisactuallymedia-independentwhichisgoingtoVW"bname@ncms@net@ nodes@xnotificationfrommihfofthemntonewservingmihfornoti@occurrance@ofthisinformationisoutsidethescope@onlyqopcode@Sorder@4pdus@position@Qprocedure@(provideinformationaboutgeneratingthemihfid@WWstartWstatewWWlWqWWWstatedNWlWpWWstatementWWstates2WWWWWWWW)W0WhWWstatingWWstatuspWqWWEW]WWWstepWstillWWstrangeWstratumWstrengthZWstrictlyWstring9WWWstringsEWHWsub-section5WW'WsuggestionsWsummarizedWsupportWWsupportedUWWWsupportsWsupposedW-Wv€€marked()+,27<=>?BRWXYabjstv{| ⳃⴃⷃ⸃⹃⺃bcdjmnovyz{|}〃㠃㡃㢃㣃㤃㦃㨃㪃㫃㬃㭃㮃㯃㰃㺃€110HWIW1112=MW❃➃!}14>15ⴃⵃⶃⷃ 1617?18⹃~192@W╃200W21⪃W2223a24*,25:ރ26273AW⥃4z{31; 329 36 373846W〃W5,⨃k|7.2.2.2]9⛃f19kf24Af33QfigWfig20Vfig-35tWWt21Vt4Vt15ef@t16Xt17YZt25Kt31Rt4rt69:;t87table6Wtable46Vtable-6tbl@WAWHWIWMWtbl10HVIVtbl12MVbeffectTW$W_WWeffectonreceiptmustalsodiscusswhatwillneedtohappenTVeffectiveWefficiencywWeither4W6WEWHWIWMWWWWWWW7W\WqWwWWWWWWWeitheraddlinkidentifiertolistorremovetherowVeithercompletethistableappropriatelyordeleteitVbaddanewcolumncrossreferencingwhereeachentryinthetVaddarowforperVVaddasubsectionin7.2.1forlsapandcssaprespectivelyWVaddanintroductionforthesystemmanagementserviceinsecVaddanunrecognizedielisttlvwhichwillcontainsalistoUVaddbetweenwordswhichconsistofthenameofprimitivesan VadddescriptionsofmissingprimitivesintheappropriateplVV nadaⶃⷃ⸃⹃⺃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃njedjou45ohba6789:;<=>?@ABCDEFGHIJKLMNOPQRolveraUparkhirajkumar㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃sreemanthulavwxyz{|}~〃ぃゃッ㄃ㅃㆃtaniuchividal㈃㉃㊃㋃㌃㍃RYQbEUlises^Technical, Binding_32`62a5.6.1.1bHReplace by "this SAP defines the gerneric Media Dependent Link Layer..."c"This SAP defines the generic media independent link layer..." should be replaced by "This SAP defines the generic media dependent link layer...."d2096g2305wAccepted 2006/11/16Markedon is valid, should be used. d2381g2304 2006/11/15bEUlises^Technical, Binding_32`62a5.6.1.1bHReplace by "this SAP defines the gerneric Media Dependent Link Layer..."c"This SAP defines the generic media independent link layer..." should be replaced by "This SAP defines the generic media dependent link layer...."d2096g2305wAccepted 2006/11/15Marked32`62a5.6.1.1bHReplace by "this SAP defines the gerneric Media Dependent Link Layer..."c"This SAP defines the generic media independent link layer..." should be replaced by "This SAP defines the generic media dependent link layer...."d2096g2305wAcceptedCPperetz|}~ ⁃qiaobing$'()+,0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ronnyjklmnopqrstushuWshuguiming/guojunxiangVsoohonghisrinivasvwxyz{|}~〃ぃゃッ㄃ㅃㆃsubirefghijklmnopqrstuvwxyzsungjin)*ulisesSTUVWXYZ[\]^_`abcdefgvivek㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃhong`abcdishizujeejeonkim koh kuroda!"bmlme2WmWmn~WWW+W6WWWmobmWmobilesWyWWWlWmWWWmobilitymWwWmobility-managementW|W4WmodificationsWW!WgWmodifiedWmodifyW'WWmodifythesubsection7.4.7.1.3assuggested'VmonitoringZWmoreGWPWlWWQWpWWWWWWWmotivatedWmove3W<W@WAWBWCWHWzWWWWWWW5WoWtWWmove5.6.2.3mihnetsaptomediadependentsapsectionmoveoVmove7.2.2.2and7.2.2.3to7.2.1mediadependentsapstVmovecurrent5.3tobeaftercurrent5.4forbetterreadabil<Vmovecurrentsection7.2.3.1mihnmssapunder7.2.23Vmoveline38writtenbelowtoline30aftercssapoVmovesection7.2.2.2tobeasubsectionofsection7.2.1medVmovestartingatthissentencetountiltheendofthissectVc8]WnWWW8iswrongreferencetordf]V8.1WW8.3.3.2WWW8.3.4.1{W8.4.1.4nW8.5.1.3MW8.5.1.4fW8.5.1.5fW8.5.1.6MWfW8.5.2W8.5.2.1\W8.5.2.2\W8.5.2.6\W802[WaWW802.11'WWWW2W9WiWWWW802.11ulW802.15W802.162WnWqWWW802.1ag]W802.1xWW]W^W_WnWrWWWWW802.3]WiW802.3ah]W9EWHWa'W(W7W?WEWUWWW[WdWuW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W"W#W,W-W2W9W;W>WCWDWSWWW[W\W^W`WdWfWgWiWWWWWWWWWWWWWWWcinconsistencywithnamingwhichmakesithardertofindrelaVinconsistentWWWWWinconsistentnamebetweenheaderandnamelistedintable26VincorporateWincorrect7WyWWindeedWindentifyWindependenceW vthereW#W,W/WxWWWWthereisnosessionidaspartofregistration/Vthese+WjWlWmWoWW W,W_WvWyWWWWWd remove the rest.cVThe Name fields of RSSI, SNR, C/I, BER and Data Rate are not used. They are redundant.d2258g2292 2006/11/14able except first two, that is, leave LinkParameterList field and its corresponding Type, Valid Range and Description and remove the rest.cVThe Name fields of RSSI, SNR, C/I, BER and Data Rate are not used. They are redundant.d2258g2292 2006/10/31evious definition in section 7.3.7.2 for Link_Configure_Thresholdsd55g2321 2006/10/26EGolmieFNadaGMember^ Editorial_90`55itions of LinkParameterList consistent throughout the draftcmLink Parameter List is inconsistent with previous definition in section 7.3.7.2 for Link_Configure_Thresholdsd55g2321 2006/10/26EGolmieFNadaGMember^ Editorial_90`550/24bifcomment3isapprovedupdatedescriptiontofittheeventVVifmihstatemachineneedstobedefinedinthespecificatioVifdentifierWiformationWW\WimpleWimplementation W^WWimplicitlyWimproveWWWin'W4WCWDWMWWWXWYWZW_W`WeWfWiWjWkWlWnWoWpWrWwWxWyW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWW!W"W)W+W,W-W.W0W1W2W4W8W9W:W=WEWFWMWNWVWZW\W^WfWgWhWiWlWmWqWrWsWuWwWxWzWWWWWWWWWWWWWWWWWWWbH$_‚S‚ƒÃăUŃƃ‚,-A‚$./‚T‚‚‚4ʃ‚5Ã!Ã! Ã!`'Ã!Ã"Ã"0Ã"`Ã# Ã#`ӃÃ$ՃփBÃ$ ⁃CÃ$0Ã$P₃DÃ$Ã$كESÃ%PڃÃ%pÃ&FÃ&0aۃ܃Ã&@ރÃ&Pv ݃ )0Ã&`{GÃ&pbwHIÃ&߃*JÃ&Ã' :mKLÃ'`cdpÃ'pÃ'Ã(%Ã( nÃ(@oÃ(PÃ(`1MÃ(pÃ) qÃ)@NOPÃ)g Ã* Ã*0QÃ*@6; 2RÃ*`9zÃ* Ã*Ã*Ã1Ã4P` $+269=Ucg|}⌃❃➃ⴃⵃⶃ!124;@KMR0@:PELQj⒃׃8Tpw bB 9-31 MIH Command ID Command Name ID MIH Get Status 0 MIH Switch 1 MIH Configure 2 MIH Scan 3 MIH Handover Initiate 4 MIH Handover Prepare 5 MIH Handover Commit 6 MIH Handover Complete C 7 MIH Network Address Information 8 Reserved 9-31 In the Description field for SupportedEventList, add the following: The encoding uses a bitmap where the bit position represents the MIH Event ID. In the Description field for SupportedCommandList, add the following: The encoding uses a bitmap where the bit position represents the MIH Command ID. {dover Commit 6 MIH Handover Complete 4bannex_WrWxWWWWWWWWWWWWanotherjWW'W8WWWanyW6W^WqWrWWWappeareWWWappendix WapplicableWWWapplicationWWappliesRWSWTW\WWapplyFWappropiate{WappropriateWWWappropriatelyWapprovedWWaquirelWarQWcthereisnoencodingschemeforthesetofcommandidsVthereisnoencodingschemeforthesetofeventidsVthereisnoencodingschemeforthesetofmiheventsandcoVthereisnoencodingschemeforthesetofsupportedmiheveVthereisnoneedtolistcommandshereVthereisnoneedtolisteventshereVthereisnoneedtopresenttechnologyspecificrelationshipVthereisnonet-sapinthepicturebutthedescriptionshows}Vthereisnonmsdefinitioninthestandardandnosectionfo!Vthereisnotexualdescriptiononfigures33343637and38QVthereisnouseofthismodelinthedraftexceptforthetaVcThe MIH_SAP specifies the interface of MIHF with other higher layer entities such as transport, handover policy function and L3 Mobility protocol. d2082g2228i Ronny, Vivekk~Transport protocol, such as TCP may want to receive link layer information for better performance , e.g., congestion control. mRejectedwRejected 2006/11/16 2006/10/23Markednstead there is no "Transport" in the MIH Users box). d2081g2227v&IP Transport is an example of MIH UserwRejected 2006/11/08 2006/10/23EAjayFRajkumarGMember^Technical, Binding_28`47MIHF would add clarity to the text.cThe inclusion of "Transport" in the set of MIH users is not obvious and (if indeed motivated) should be articulated (beginning with Figure 4, where instead there is no "Transport" in the MIH Users box). d2081g2227v&IP Transport is an example of MIH UserwRejected 2006/11/01 2006/10/23EAjayFRajkumarGMember^Technical, Binding_28`47clinktypeWW\Wlist'WGW_WlWWWWWWWWWWWWWPWWWWWlisted3WWWWWWWWWWWWWWWWWlistingWWWlistsgWlittleKWLWWWlli+lnkWloads`WlocalW WGW~WWlocallyWlocated|WlocationeWWWWlong"WWlookWeWlooksWlossZWlotWlower>W?WWWWWWWWWlsapWWjWmWWnWmsapisnotdefinedformultiinterfacemanagementby802.1nVmaccW:W]WqWWmac/phyWmacaccessrouter#Wmacaccessrouterparameterdoesn'treallyseemtobeincluded#VmachineWWmacmobileOWmacnewpoaWmacnewpoalistedbutnorowispresentVWWWWWW>NcdescriptionsnWdesecribesvWdesignWdesignprinciplessectionhasnoplaceinaspecificationsdVdesignedWdestinationWW WGWdetail"WWWxcinconsistencybetweennameindescriptionandnamecolumnsfVVinconsistencyinnamingtargetposidentifierinlistortargeVFNadaGMember^Technical, Binding_98`20a 7.4.3.1.2bAdd the following in the Description field: The encoding uses a bitmap where the bit position represents the MIH event ID. A bit set to 1 indicates that subscriber is seeking to subscribe to the event.c8There is no encoding scheme for the RequestedEvent List d2271g2233wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Binding_98`58a 7.4.3.2.2bAdd the following in the Description field: The encoding uses a bitmap where the bit position represents the MIH event ID. A bit set to 1 indicates that subscription succeeded.c8There is no encoding scheme for the ResponseEvent List. d2273g2234wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Binding_99`45a 7.4.4.1.2bAdd the following in the Description field: The encoding uses a bitmap where the bit position represents the MIH event ID. A bit set to 1 indicates that subscriber is seeking to unsubscribe to the event.EGolmieFNadaGMember^Technical, Non-binding_130`18a 7.4.14.1.2bFix inconsistencycUInconsistency in naming TargetPoSIdentifier (in list) or TargetPoAIdentifier (in row)d2298g2286 2006/11/14EGolmieFNadaGMemberdaGMember^Technical, Non-binding_130`18a 7.4.14.1.2bFix inconsistencycUInconsistency in naming TargetPoSIdentifier (in list) or TargetPoAIdentifier (in row)d2298g2286 2006/11/14EGolmieFNadaGMemberMember^Technical, Non-binding_130`18a 7.4.14.1.2bFix inconsistencycUInconsistency in naming TargetPoSIdentifier (in list) or TargetPoAIdentifier (in row)d2298g2286 2006/11/14EGolmieFNadaGMemberal, Non-binding_130`18a 7.4.14.1.2bFix inconsistencycUInconsistency in naming TargetPoSIdentifier (in list) or TargetPoAIdentifier (in row)d2298g2286 2006/11/14EGolmieFNadaGMemberrgetPoAIdentifier (in row)d2298g2286 2006/11/14EGolmieFNadaGMember10/24_125`21a 7.4.12.4.2b>Either delete row for NewLinkIdentifier or add it to the listc.NewLinkIdentifier has a row, but is not listedd2295g2284vAdd this to the list..wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_125`23a 7.4.12.4.2b>Either delete HandoverStatus from the list or add a row for itc2HandoverStatus is listed, but no row exists for itd2296g2285vAdd a row for thiswAccepted 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_130`18a 7.4.14.1.2bFix inconsistencycUInconsistency in naming TargetPoSIdentifier (in list) or TargetPoAIdentifier (in row)d2298g2286v?Change PoA to PoS and also the Descripton for this in the tablewAccepted 2006/11/16ResourceList to QueryResourceFlag.d2289g2281 2006/11/14EGolmieFNadaGMember^Technical, Non-binding_115`17a 7.4.10.3.2b;Either delete PreferedPoAList from list or add a row for it6/10/31vbDelete the table-22. Change description of ScanRequestSets to :"List of link identifiers to scan"wAccepted-Modified 2006/11/16 2006-10-23ESrinivasF Sreemanthula^Technical, Binding_111`20a 7.4.9.2.2bAEThis is to scan a certain frequency band and determine one or more access network type(s), specific channel(s) and PoA information, if present. Reformat ScanResponseSet as variable data length to indicate one or more tuples as below. 1 Network access type (TYPE_IE_NETWORK_TYPE). 2. Channel # 3. PoA address (MAC address) Ec^ScanResponseSet needs to have a specific representation of data rather an unstructured string.d2287g2252vLLink Identifier + Channel # (LinkIdentifier : is Network Type + MAC Address)wAccepted-Modified 2006/11/16 2006-10-23ESrinivasF Sreemanthula^Technical, Binding_117`43a7.4.11.xbA list of one or more TSPEC.c8QuerResourceList and AvailableResource list not defined.d2292g2253vby 2291rHbaddanewcolumncontainingtheappropriatetypeiereqindV\Hb31W W329WrWzW%W38oW3gppgW3gpp/3gpp2|WW3gpp2W3triggers]W4QWeWoWWWWW WWWW1W9W:W<WgWW4---mihW4-255W4-255reservedV44-45W45-47W46-48W49Wvvbmihnetworkaddressinformation8VmihreportcontainsmeaningfulEVmihscan3Vmihswitch1Vmih-capableWmih-eventsWmih-id/Wmih-layerWmih-msgmWmihfbWzWWWWWWW WW"W'W+W6W7W@WTWjWmWnWoWqWrWWWWWWWWWWWmihf'sWmihprotocolpduFWmihuseridlistWmiisUW^WW9W:WeWqWWWmimimumWminimumWmismatchEWmissedWWmissingWWWWW8^ Editorial_130`21a 7.4.14.1.2bFix inconsistencyccOrdering for CurrentAccessRouterAddress and Current FAAddress in list are not the same in the rows.d2300g2287 2006/11/16EGolmieFNadaGMember^ Editorial_132`4a 7.4.14.2.2bFix inconsistencycZOrdering for OldAccessRouterAddress and OldFAAddress in list are not the same in the rows.d2306g2288 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_137`63a 7.4.15.3.2bFix inconsistencycRItems listed do not agree with rows. For example InfoQueryResponse and MIH_REPORTd2309g2289wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_139`58a7.5b%Delete section or move it to an annexd2312g2290v!Keep this here for consistency...wRejected 2006/11/16EGolmieFNadaGMember^Technical, Binding_144`51a 7.6.2.4.3bZReplace with: The receiving MIHF instance can request data transfers over the connection. c6/10/26*bdescriptionseWjWWdesign"WdesiredyWdesription@Wdestination/WMWTWWdestinationidentifiermih-id/VdestinationidentifieWWdestinedWdetailedWWWWWWdetailedincontribution21-06-0783-00-0000-cnihodocVVdetailedincontribution21-06-xxxx-00-0000-ecsproxydocVdetailsJWKWLWNWOWPWlWWWWdetectWdetectedZWWWW+W\WWdeteleteWdeteletelines45-47VdetermineW$WWWWdhcpQWNWdhcpv4NWdiagramEWHWdiagramsWdifferencesYWWdifferentGW_WlWWqWrWwWxWWclarifyingtextin21-06-0xxx-00-0000naiuVdiscussandaccepttheconceptdescribedin21-06-0781-00-00pVdiscussandaccepttheproposaldescribedin21-06-0780-00-0wVdiscussedWdiscussionWWdistinctNW baddWWWWWWWWWWW WW!W$W*W9W>W@WJWKWOWRWzW}W~WWWWWWWWWba1.4gWa2Wa3rWabortqWWabortedWaboutbWWWWWabove^W~W,WqWrWxWWWWabstract^WjWacceptpWwW+W-W.W1WuWWaccepttheproposedamendmentstothisprimitiveisinther-Vacceptthesuggestionsincontribution21-06-0739-02-0000-sVaccess'WCWFWWW9WNWmWwWWWWWaccompaniesnWaccompanyingWaccomplishedmWaccordingoWaccordinglyfW5WWaccountWeWachieved_Wack WacknowledgementdWacronyms+WacrossSWmWactWWactionW WWactionscWactive'W+WWactuallyWadd0W8W=W>W?WMWNWOWPWUWVWWWXWYWgWjWlWxWyWWWWWWWWWWWWWWWWWWWW8EGolmieFNadaGMember^Technical, Non-binding_152`23a8.1b(Describe what MIH Function Discovery is.cYWhat is MIH Function Discovery? This should have been introduced somewhere before here.d2320g2291iRonnyjAdd the following text into the beginning of line 23, page 152. The MIH Function Discovery procedure is to find more than one MIH peer for MN to communication with through MIH protocol. mAccepted-ModifiedvSee 6.4.2 page 67wRejected 2006/11/16Markedat is MIH Function Discovery? This should have been introduced somewhere before here.d2320g2291iRonnyjAdd the following text into the beginning of line 23, page 152. The MIH Function Discovery procedure is to find more than one MIH peer for MN to communication with through MIH protocol. mAccepted-ModifiedvSee 6.4.2 page 67wRejected 2006/11/14Markeda8.1bwill provide text latercNIntroduction paragraph contains many grammatical errors and needs to be fixed.d2321MWbreplacewithandhowwelltheymeettheapplicationqualityVreplacewithapplicableVreplacewitheitherVreplacewithenablingmoreeffectiveVreplacewithiflinkgoingdownisnotreceivedafterthespcVreplacewiththefollowingtextrVreportVWWWW9W:WEW\WWWWWrequest/confirmWrequest/responseWrequiredjWWrequirementsWWreservedWWreserved9-31VresourceWresources_WrespWrespectivelyWWfWoWresponse'WqW{WWWW WWresponsesnWresultssWretitleWretitlefigure25transportofmihframeinieee802l2dataVretransmissionWWretrieval'WWreviewWreviewsection8.5.2andupdatealltypevaluesasdefinediVrevisionJWrewrite[WWWWWrewritesentencetoreflectthefactthatonlyoneprotocolV/igctobeconsistentwith7.1.1needasubsectionin7.2.1forlWVtobeconsistentwithfigure15remoteeventillustrationon>Vtobeconsistentwithfigure18remotecommandillustration?Vtomakeitreadbettermovelinkeventnametothe2ndcolum@Vtomakeitreadbettermovemiheventnametothe2ndcolumnAVtopreventfuturemismatchbetweentheprimitivesinthetabeVtoosW W"W/WWWtpWWFWtransaction*Wtransaction-iddWtransferWWWtransmissionWWtransmittedkWtransportuWWWWWWWW WjWkWsWWWWWtransportediWtriggers]WtrueSWWtsgWtuneWtvlWtwoEWyWWWWWW W-W[WdWgWyWWboccurranceWoccursWWoctectmWoctetQWJWoctetsFWWWLWof1W4W5W:W;WBWCWGWHWJWKWLWNWOWPWQWUW_W`WdWjWlWnWsWuW~WWWWWWWWWWWWWWWWWWWWWWWW W WWWW W!W"W$W+W-W.W4W6W7W8W9W@WFWNWSWVWZW[W^W`WeWgWjWlWmWnWqWrWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW"W$WJWNWQWZWgWjWnWoncedWoneGWlWmWWWWWWW'W>WLW\WgWones WonlyWWEW\WgW~g2323 2006/11/16EGolmieFNadaGMember^ Editorial_154`36a8.3.1.2bwill provide text latercW?WAW`WlWvWwW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W| ?cnformationrWnformationelementrange0x000000010x000000ffaretheheaderVnihoWWnmWnms1W3W!WpWno1W3W@WAWaWqWyWWWWWWWWWWWWWWWWWWWWWWWWWW!W'WGWQW}W~WWWWWWnoclearrelationshipwithprimitivesinthistableandtheVnodefinitiononmobile-initiatedandnetwork-initiatedhandyVnomiheventnamemiheventtypeAVnodeWWWWOWSWdWgWlWyWWWWWnodesW WWWWnon-accessWnon-l3Wnon-poa[Wnon-standardWnoneWWnornWnormative^WWW-7=chandoverstatusislistedbutnorowexistsforitVcinmihprotocoldescriptionitsaysthathoweverinthisins{Vintable11oneofthemethodhasbeenstatedtobeieee802Vinthecaseofl3transporttheactualtransmissionofthepVinthecaseofnetwork-initiatedhandoverprocedureafterthVintlvlocationqueryitseemsthereshouldbeawaytospecVinaccurate\W6Winaccuratetext\VinadequatePWQW]WwWinappropriateWinclude[W WWWincludedWWWWWW#WNWincludesWWWincludingWWpWWinclusionWinconsistencyWWWWWW~0bcHThis figure is competing with Figure 26 and is inconsistent in labeling.d2356g2294 2006/11/1627EGolmieFNadaGMember^ Editorial_166`1a8.4.1.12boSplit these two Link Identifiers, so that the Table 26 Type Number will consistently match the section numbers.coSplit these two Link Identifiers, so that the Table 26 Type Number will consistently match the section numbers.d2367g2295 2006/11/16EGolmieFNadaGMember^Technical, Binding_168`16a8.4.1.20bDefine generic link parameters encoding: 0: Speed 1: Signal strength 2: Bit Error Rate 3: Frame Loss Rate Before Retransmission 4-255: reserved cUThe type of parameter is not fully defined. For the generic, there are only examples.d2369g2239v>Remove (for example) and mark other unused values as reserved.wAccepted 2006/11/16istent name between header and name listed in Table 26.d2371g2296 2006/11/15EGolmieFNadaGMemberEGolmieFNadaGMemberW9EAjayFRajkumarGMember^ Editorial_2`23a1.220a1.2b"Define a separate category for it.c@Is the reference to IEEE 802.15 under micro cells is incorrect. d2008g2233 2006/10/31 2006/10/23EAjayFRajkumarGMember^ Editorial_2`23a1.2Technical, Binding_2`20a1.2b"Define a separate category for it.c@Is the reference to IEEE 802.15 under micro cells is incorrect. d2008g2233 2006/10/31 2006/10/23EAjayFRajkumarGMember^ Editorial_2`23a1.2t use of acronym for Quality of Service: d39g2232 2006/10/31 2006/10/23EAjayFRajkumarGMember^Technical, Binding_2`20a1.2b"Define a separate category for it.c@Is the reference to IEEE 802.15 under micro cells is incorrect. d2008g2233 2006/10/31 2006/10/23EAjayFRajkumarGMember^ Editorial_2`23a1.2ent draft).c7Make consistent use of acronym for Quality of Service: d39g2232 2006/10/26 2006/10/23Memberpcforconvenienceshowtheactual32idinthedefinitiontablDVforinformationretrievalusingtlvclientshouldbeabletoVforinformationretrievalusingtlvthereshouldbeawayfo'VVfortypeiesecurityspecifyVformalWformatWWWWW1W=Wformatoftypeienetworkstandardsvalueneedstobespecif=Vfound^WfourmWframeWWWWdWfWgWkWsWWWWfulfillmentWfullyWfunction1W4W5W>W?W`WlWWWWWWWWWWWW3W_Wfunctiondiscoveryatl2isoptionallyintegratedwithcapabVfunctionsSW]WfurtherWfurthermore^WfutureeWgxWWWWWNWSWgeneal&WgeneralW,WSWgenerallyWgenerate]WgeneratedbWWgenericvWWWWWbWgetYWW WEWRWrit0EGolmieFNadaGMember^ Editorial_191`18aA1.4.1bChange to MIH_Link_Detectedc Wrong name.d2392g2297 2006/11/16EGolmieFNadaGMember^ Editorial_192`15aA1.4.2bChange to MIH_Link_Detectedc Wrong name.d2394g2298 2006/11/16EGolmieFNadaGMember^ Editorial_193`1aA2b-Add missing primitive and related informationcMissing MIH Link Detected.d2397g2300 2006/11/1631EGolmieFNadaGMember^ Editorial_193`38aA2bChange to MIH Get Statusc Wrong name.d2402g2299 2006/11/1631EGolmieFNadaGMember^Technical, Non-binding_200`1aBbDelete this annexcWhy is this included?d2410g2301iYoshihiro OhbajUThis is the formal Basic Schema definition and needs to be defined as normative text.mRejectedv-Add some clarification text for this section.wRejected 2006/11/16this annexcWhy is this included?d2410g2301iYoshihiro OhbaEGolmieFNadaGMemberbabsenteWabstract^WjWWacceptpWwW+W-W.W1WuWWaccepttheproposedamendmentstothisprimitiveisinther-Vacceptthesuggestionsincontribution21-06-0739-02-0000-sVaccess'WCWFWWW9WNWmWwWWWWWWWaccompaniesnWaccompanyingWaccomplishedmWaccordingoWaccordinglyfW5WWaccountWeWachieved_Wack WacknowledgementdWacronymWacronyms+WacrossSWmWactWWactionW WWactionscWactive'W+WWactuallyWadd0W8W=W>W?WMWNWOWPWUWVWWWXWYWgWjWlWxWyWWWWWWWWWWWWWWWWWWWWAcintroductoryWinvolvementWinvolvesWWipv4dWNWipv6dWis,W1W2W3W7W9W=WBWCWEWFWHWIWUW[W\W]W^W_W`WaWbWcWdWgWkWlWmWnWrWtWuWwWxW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWW!W"W%W+W,W-W.W3W4W5W8W9W<W>WFWGWJWNWOWPWQWSWTWVWWWXWZW\W]W^W_WaWcWdWfWJl(EQiaobingFXieGMember^Technical, Non-binding_7`61a3bdelete "Message" definitionc=Definition for "Message" not neccessary. It's a common term. d2027g4675k wAccepted 2006/11/16 2006/10/20Marked)EQiaobingFXieGMember^Technical, Non-binding_8`45a3bdelete the unused definitionsc]Unused definitions: N-entity N-event N-layer N-trigger N-user Peer N-entity Remote N-trigger d2029g4676k vby comment 2028w Superceded 2006/11/16 2006/10/20Marked+EQiaobingFXieGMember^Technical, Non-binding_10`1a4bdelete the unused acronymsQiaobingFXieGMember^Technical, Non-binding_8`45a3bdelete the unused definitionsc]Unused definitions: N-entity N-event N-layer N-trigger N-user Peer N-entity Remote N-trigger d2029g4676k vby comment 2028w Superceded 2006/11/15 2006/10/20Marked+EQiaobingFXieGMember^Technical, Non-binding_10`1a4bdelete the unused acronymsTEJamesFHanGMember^Technical, Binding_61`48a6.3.6bEnhance the TLV information retrieval to allow the client specify what access networks/PoAs should be included in the response.cA0For Information retrieval using TLV, there should be a way for the client to narrow down the list of the access networks and PoAs in the report. For example, a client may not want to retrieve any information about 802.11 networks. Or, a client may only want to retrieve information about UMTS networks. 0d2191g4671vby comment 2190w Superceded 2006/11/16 2006/10/20 information about UMTS networks. 0d2191g4671vby comment 2190w Superceded 2006/11/15 2006/10/20Ohbaitorial_193`38aA2bChange to MIH Get Statusc Wrong name.d402g2299 2006/10/3131EGolmieFNadaGMember^Technical, Non-binding_200`1aBbDelete this annexcWhy is this included?d410g2301iYoshihiro Ohbal, Non-binding_176`12 bframeWWWW*WqWsWWframesqWsWWframework`WWfrequencyWWfrequencyboundWblevelWwWlikeCWlimited~W`Wline>W?WlWWWWW#W&WnWoWsWlinesWWWWlink2W4W5W@WRWSWXWYWZWeWfWsWWWWWWWWWWWWWWWWW W W WWW%W'W5WZW\W^W_WbWcWgWwWWWWWWWWWWWWWWWlink-specificgWlinkidentifier\WlinkparameterlistWWUWlinksgWWWlinktype\WlistGWPWUW_WlWnWWWWWWWWWPWgWWWlistedWlistsWlittleWloadWlocalWWjWWWlocallyWlocatedlWqWrWlossWZWlowWlower>W?WWWWWWWWmaybe>W?WmechanismWmrbdeleteatleastpreambleandstartofframedelimiterfromfVdeleteentiresection5.3andannexa2containingtable31Vdeletefigure4andupdatefigure12andaddanotherblockmVdeletefromline22toendofsectionVdeletelastsentencewhichincludesthespecificcommandsVdeletelastsentencewhichincludesthespecificeventsVdeleteline19and20onpage69nVdeletelines49startingwiththemiisschemaisclassifiedVdeletelines7-9startingwithasanexampleVdeletemessagedefinition(Vdeletemiheventsubscriptionfromsection6.4?VEAjayFRajkumarGMember^Technical, Binding_27`8a5.5.1bA few examples of the kind of interactions that may exist between a transport entity (e.g., a TCP/IP implementation) and the MIHF would add clarity to the text.cThe inclusion of "Transport" in the set of MIH users is not obvious and (if indeed motivated) should be articulated (beginning with Figure 4, where instead there is no "Transport" in the MIH Users box). d2081g2227v&IP Transport is an example of MIH UserwRejected 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_28`47a5.5.2bIt may not be appropriate to include "transport" in the set of MIH users. Hence remove transport as an MIH user unless it can be motivated more./23MarkedEAjayFRajkumarGMember^Technical, Binding_28`47a5.5.2bIt may not be appropriate to include "transport" in the set of MIH users. Hence remove transport as an MIH user unless it can be motivated more.jayda BI€ p@p€markedv€tbl2@bl2@@ cAIt needs to be made clear that figure 25 is not a representation of the common frame format but a representation of how to embed the common frame format as an opaque entity into an IEEE 802 L2 frame. In particular the caption needs to be changed. In addition, it should be clarified which type field it is that is given the MIH function identifier. If this diagram is specific to IEEE 802 frames the we assume that the type field is the Ethertype field in which case this is managed by the IB4EEE (https://standards.ieee.org/regauth/ethertype). "d2323g2221iMichaelWjGRetitle figure 25 "transport of MIH frame in IEEE 802.3 L2 data frame".mAccepted-ModifiedvSee 2325w Superceded 2006/11/16 2006/10/19Marked250/1925.3 L2 data frame".mAccepted-Modified 2006/11/01 2006/10/1925ified 2006/11/01 2006/10/1925ers to IETF transport protocols which are generally considered as being at L4. Cd325Ztb2biterrorrateV2changethetextdasfollowsV2defineallthevalidrevisionentryvaluesJV2removemacmobilenodeOV2removeremote~V2.19W200WW:WnWW21-06-0460-04-0000-bWWW21-06-0530-00-0000iW21-06-0656-01-0000-w2W21-06-0731-01-0000-lWW21-06-0737-01-0000-s^W01-0000-s^W^WwW21-06-0781-00-0000-mpW21-06-0784-00-0000W21-06-0785-00-0000W21-06-0786-00-0000!W21-06-0787-00-0000"W21-06-0793W21-06-0xxx-00-000}W21-06-0xxx-00-0000-m)W+W,W-W.W0W1W21-06-0xxx-00-0000-r|W215PW22WW24,W243\W244\W25WW W25-mihf W W253FW26oWrWzWWWW2nd@WAW3oWyW|WWWWWW WWWWW!W.W4W9W:WFWMW3framelossratebeforeretransmissionVcexamplesincluderesourcedescriptionframeworkrdfwhichis[VexceptWexchageWexchangelWWWWexchangesWWexchangingWexchanvelWexecuteWexecutedWexecutionW~Wexercise Wexhaustive_Wexhibiting^WexistWW^WexistenceWWexisting^WexistsWWexpectedWexplain7WWexplainhowmicsisrelatedtotheinformationdatabaseand7VexplainationWexplanationWexplanatory0WWexpressionsWexsmapledWextended\W_WWextendedschemathatisoptionalandmaybevendorspecific\VextensionWfaNWfaaddressWfacilitateWWfacilitatingWfacilitatinghandoverbetwenVfacilityWfactFWWfailWfailurepWWfailuresWfcsWfeltwWfewWballow'WhWWgWqWallowed~WallowsmWalreadyW\W^WfWalsoTWWW4WFWlWmWWWWWWWalsoapplicableforhandoveinitiateprimitives7.4.10.2VVandoverprocedurefrom802.11to3gpp2Vamendments+W,W-W.W1Wan4W5W>WFWUWlW{WWWWWWWW'W4WEWFWJWdWgWwWand1W7W:W;WCWPWQWWWXW[W_WeWfWiWpWwWzW~WWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWW W!W$W'W+W,W5W6W:W@WFWJWMWNWOWRWUWZW\W]WaWeWgWjWmWnWpWqWrWtWuWvWwW{W|WWand/orqW ~cthevaluesofsomeelementsarecodedwith4bytesgivingvaVthewaystodefinemediatypesinthetablearenotconsisteaVtheworddefensiveisnotdefinedthemeaningofthesentencXVthewordingisuncleardifficult-to-followandpossiblyhasTVtheirWWWWWthenlWqWWW5WGWNWcWWWWthere'W,W0W3W>W?WqWuWWWWWWWWWWWWWWWWWWWWW!W8WGWQWYW\W^WdWnWuW}W~WWWWWWWWthereisadisconnectregardingthedescriptionheresuddenluVthereisnodescriptiononisbetweenmihfandlowerlayersVthereisnoencodingschemefortherequestedeventlistVVthereisnoencodingschemefortheresponseeventlistVVcthereisnoencodingschemeforthesetofcommandids@~thereshouldbesomeexplanatorytexttofigure20@they@ thisprocessmaybecarriedoutoncethecoreelementsofth@thissectiondoesn'tbelongunder7.2.2mediaindependentsa@0tied@Gtimeout@^tlvs@qtotoallowalltypesofnetworkinitiatedhandoversitisnece@/tobeconsistentwith7.1.1needasubsectionin7.2.1forl@twoexamplesofschemaarediscussedwithoutspecificallyst@itype@typeiepoaipconfigmethodsmissinginreportingtemplate@"unique@Nupper@,useful@way@whatistheservice-info@whether@Dwhile@"whymihnetworkaddressinformationconfirmhasadifferent@without@wording@Gxml/rdf8yet@TdÄ1@Ä2>FÄ3*Ä4A0[ija@aboutthetermbeingundefineduseofl2isself-refer@all@*[diguptanWoWWWnW~WWmichaelsWvWWWWmichaelwilliamssVvVVVVmichaelwaohba[W]W^WWWW*WdWWWohhaWronny1jl ⁃₃W!37CN〃ゃW㩃㺃ronnyvivekVVvivekhnWoWWWWXnWo~WWWvivekguptanVoVVVnV~VVwilliamssWvWWWWyoshihiro[W]W^WWWW*WdWWWWyoshihiroohba[V]V^VVVV*VdVVVyoshihiroohhaVWdescription[W^WdetailsWdeterminedWdifferent[WeWelements[WencapsulatedWencapsulationWevendWevery*Wexamples[WextendedWextensibilityWfactWforW*WdWformalW^ucstwo examples of schema are discussed without specifically stating which are supported by the 802.21 specifications.d2205g2265 2006/11/16EGolmieFNadaGMember^ Editorial_67`43a6.4b.Clearly group items as primitives or messages.cpThe sentence states both primitives and messages, but it is not clear which of the five bulleted items are whichd2209g2317 2006/11/16)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)Ã)s kcAgit should be clearly show which transport (SAP) shall be used in case of layer2 in the figure. In case of layer 2 transport, MIH frame can be transmitted either through data frame or control frame. When MIH frame is transmitted through data frame, MIH_NET_SAP should be used, when MIH frame is transmitted through control frame, MIH_LINK_SAP should be used. gd2076g4998vIn figure 5: Change "Lower layer Transport" to "Data" Show communication between two MGMT entities for L2 communication, separately. Draw another block for this communication.wAccepted 2006/11/165lERonny^Technical, Non-binding_26`61a5.5bwAccepted-Modified 2006/11/08kERonny^Technical, Non-binding_26`7a5.5bVRevise figure to distinguish l2 transmission over data plane from over control plane. c N  33X @ b  33    33'`bchangetomihgetstatusVchangetomihlinkdetectedVVchangetomihremoteregistrationmihfindifferententitiesVchangetypeiepoaipconfigmethodstotypeiepoaipconfiVchanged Wchanges9W+WFWchannelWWcharacteristicsWcharts2WiWcheckerWchoiceWclarificationWW"WclarifiedWWclarify,WEWHWQW[W^WWWclarifyandrewritethesentence[Vclarifythatwhenpresenttheconditional/optionaldhcpaddrQVclarifytheaboveissuemakeclearwheretherdfschemadefi^VclarifytheencodingeitherwithadiagramortextEVclarifyinguWclarityWclass:WclassesWclassifiedWcleanuWvWyWcleanupthedefinitionsvVcleanupthesectionyVclear^Wclearly`WWWclearlydefinetheuseoftheqosmodelinthemihframework`VD^ Editorial_1`1b+ Run the spell checker on the entire draft.c$ Many spelling errors in the draft. d2003g2242 2006/11/16 2006-10-23EVivekFGuptaGMember^ Editorial_47`24b Redraw the figure and fix fontsc Fix the fonts in the figured2136g2243 2006/11/16 2006-10-2319EVivekFGuptaGMember^Technical, Binding_154`58a8.3.2bj Include some explanation sa to why this feature is needed as part of MIH Protocol or remove this feature.c. Its not clear why ACK-Req/ACK-Rsp are needed?d2339g2244vWaiting for text from Subir and Miriam. Ad hoc confirms ACK is useful. Proposal was to leave ACK Functionality in draft. Need some explanation/text for improvement but that may be submited in next round. wAccepted-Modified 2006/11/16 2006-10-23-26d2366g2245dentifierc_ Add TLV description for CurrentLinkIdentifier and New Link Identifier as specified in Table-26d2366g224511/01 2006-10-23$ GcAo"Additionally, if retransmitted packets were to arrive outside the window then the destination may utilize time stamp information in the packet to determine that it is older than the timeout duration and discard the packet." There is no time stamp defined in the specification. Also, implementation can implemeent its own time window on its local stack to handle it.od2346g2467vsee 345w Superceded 2006/11/16 2006/10/23Markedy not be available at the MIH application layer so it may be impossible to tune timers to take it into account. cd2341g2223 2006/11/01 2006/10/19EEleanorFHepworthGMember^Technical, Binding_155`28bRemove this sentence.cIt is not possible to use the destination timestamp in packets to determine that it is older than the timeout duration and discard the packet unless MIH peers are synchronised. Can this synchronisation really be guaranteed? d2345g2224 2006/11/01 2006/10/19mber bcapabilitiesWWqWWcapabilityXWlWWRWqWcapabityWcaptionW4WWcarryWcarryingqWcaserWWWcaseslWcategory;WjW W@WWcauses/implies[WcautiousXWcertainlWgWqWwWWWWWchange:W;WFWGW\W_WgWiWkW|W}WWWWWWWWWWWWWWWWWWWW W W W WWWWWW4W7W:W<WCWDWEWFWNWPWwW|Wchange3gpp/3gpp2networkandcorenetworksto3gpp/3gpp2ne|VchangecaptiontomihfvariableheaderformatandremovetheVChEEleanorFHepworthGMember^ Editorial_153`4a8.3b|Change to "MIH Remote Registration: MIHF in different entities may register with each other to establish a new MIH session."cSNot clear what 'Remote Registration' refers to, description is a little confusing. d2324g2225 2006/11/16 2006/10/19EEleanorFHepworthGMember^Technical, Binding_155`40bRemove this sentence.cThe sentence "The nature of MIH communication may imply use of unacknowledged connection-less transport services to reduce transport overhead and ensure efficiency and reduced latency in the delivery of the MIH messages." is untrue. d2347g2226wAccepted 2006/11/16 2006/10/19MarkedEEleanorFHepworthGMember^Technical, Binding_47`13a6.3.2bzMove the mult-hop operation discussion to section 8, and change references to IS to MIH service (or other suitable term). con really be guaranteed? g2224 2006/10/26 2006/10/19EEleanorFHepworth|cb) MIH_LINK_SAP: This represents the abstract media-dependent interface of MIHF with the lower layers of the protocol stacks. Rationale: Make the definition pattern consistent with the other three definitions in the same list.d2070g2230vEMkae the definition pattern consistent after all Editorial changes...wAccepted 2006/11/16 2006/10/23Markedsport to conduct MIH signaling."@A> 33a d 33>mRejectedvAf"When connected to a 3GPP/3GPP2 network, a Mobile Node may use L3 transport to conduct MIH signaling."f@A> 337 : 33>wAccepted-Modified 2006/11/01 2006/10/23EAjayFRajkumarGMember^Technical, Binding_25`37a5.5bxb) MIH_LINK_SAP: Abstract media-dependent interface of MIHF with the lower layers of the media-specific protocol stacks. better performance , e.g., congestion control. ‚NfcdefiendWWdefineaWWWWWdefined<WDWFWaWbWdWpWWWWWWWWWW WWGWXW\W^WnWvWWWWWWWWdefiningWdefinitelyWdefinition(WDWRWSWTW^WyWWWWWWWWWW!WpWWWWWWWWdefinitionformessagenotneccessaryit'sacommonterm(VdefinitionofcategoriesisnotneededhereVdefinitions)WsWWWWvWWWWWdefinitionsofcommands567and8arerelevanttonetworkseVdefinitionsortermsnotusedinthemainspecificationneedvVdelayWWWdeletenWpWdeleted%WdelimiterWdeliveredWdeliversWdeliveryWdependtWdependenceWdependent2WWWW5WbWjWoWtWWWjcalways\WwW'WWambiguousVWXWamendWamendments-WWammendmentsWan1W4W5W6W>W^W_WfWwW{W~WWWWWWWWWWWWWWW WVW\W^WdWeWgWWWWWaninconsistencybetweenthenamemih-3gppsapinthefigureVanmihnodecanrequestitspeertoacknowledgethereciptodVanmihposmayactsVWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWW W!W*W,W-W2W4W7W@WGWKWOWQWRWTWUWZW\W]W^W`Wannex_WxWWWWWWannex2Wanother&WbfinddWfirstjWxWWWUW[WfitWWWfix]WoWWWWWWWWWWWWAWBWHWIWWfixalltlvtypevaluesinsection8.5accordingtotable26oVfixinconsistencyVVVVVVfixinconsistencythisoccursinmultipleplacesVfixinconsistencythroughoutdraftVVfixitVVAVBVHVIVfixthereference]Vfixed*WfloatingNWOWflowlWW2WiWWflowsxWfocusWfollowWfollowingjWlWnWrWxWyWWWWWWWW$W+W9WJW\WsWWWWeWjWqWrWxWWWWWWWWWWWWW W"W.W3W4WforprimitivesyntaxpleaserefertoannexgxVformiWformatiWWformats_Wforwarded6WfourmWhoEEleanorFHepworthGMember^ Editorial_47`25a6.3.2bSort out fonts in figure.c"Figure text has gone a bit wonky. d2137g2229 2006/11/16 2006/10/1919mote handover commands from a home network proxied via the visited network. This discussion would sit better in section 8 as it is mainly related to transport of MIH services. ^d2131g2228iRonnymAccepted 2006/10/31 2006/10/19EEleanorFHepworthGMember^ Editorial_47`25a6.3.2bSort out fonts in figure.c"Figure text has gone a bit wonky. d2137g2229 2006/10/31 2006/10/1919 2006/10/26 2006/10/19EEleanorFHepworthGMember^Technical, Binding_47`13a6.3.2bzMove the mult-hop operation discussion to section 8, and change references to IS to MIH service (or other suitable term). cration and discard the packet unless MIH peers are synchronised. Can this synchronisation really be guaranteed? g2224 2006/10/24 2006/10/1935cSub-section 5.6.1.1 "MIH_LINK_SAP" is under "Media Dependent SAPs" 5.6.1 section. Then, when the SAPs are detailed, the same sub-section 7.2.2.2 "MIH_LINK_SAP" is under "Media Independent SAPs" 7.2.2 section. d2087g2257 2006/11/16 2006/10/116E YoshihiroFOhbaGMember^Technical, Binding_45`35a6.2.5.1bANotification from MIHF of the MN to new serving MIHF or notification from new serving MIHF to previous serving MIHF indicating handover completion, and any pending packets may now be forwarded to the new MIHF.@A>  33   E  33>cAComments field of MIH Handover Complete command seems inaccurate.d2127g2435vANotification from MIHF of the MN to target MIHF or notification from target MIHF to serving MIHF indicating handover completion, and any pending packets may now be forwarded to the new MIHF@A> 33  @ 33>b9#& @xbA* 33? *ve N-whatever definitions from terminology section.cbit wonky. g2229 2006/10/26 2006/10/1919EEleanorFHepworthGMember^ Editorial_7`1a3b7Remove N-whatever definitions from terminology section.cit better in section 8 as it is mainly related to transport of MIH services. ^g2228 2006/10/26 2006/10/19EEleanorFHepworthGMember^ Editorial_47`25a6.3.2bSort out fonts in figure.c"Figure text has gone a bit wonky. g2229 2006/10/26 2006/10/1919EEleanorFHepworthGMember^ Editorial_7`1a3b7Remove N-whatever definitions from terminology section.c[ceitherWWkWWelementdWrWWelements[WiWmW~WWW8WWeliminateWelseWembedWemergencyWemptyGWWenabledWWenablingWencapsulatedWencodeHWencodedEWHWencodingJWKWLWMWNWOWPWQWmWWWWWWWWWWWWWencodingdetailsofthecivicaddresselementsmissingMVencodingdetailsofthevaluefieldinadequatePVQVencodingdetailsofthevaluefieldmissingNVOVencodingdetailsofthevaluefieldmissingwithoutthosedeKVLVencodingsrWendpointWendpointsWengine Wenhancing_Wenough^WensureWentireFWWWentitiesW)W*W0W]WhWWcconlypdusnotprimitivescanbemappedtoaninterfacebecau6VopaqueWopcode{WoperateWoperationvWWW W)W0WhWWWoperatorDW9Woptimization;Woption,WWWoptional\WeWoptionallyWoptions,WWor'WUW[WdWeWtWWWWWWWWWWWWWW W'W^WdWgWkWvWWWWWWWWWWWWorderZWeWfWiWuWWordered$WorderingWWorderingforcurrentaccessrouteraandcurrentfaaddressinlVorderingforoldaccessrouteraddreandoldfaaddressinlistaVorg/regauth/ethertypWorganizationWorganizedWoriginatedfWoriginatesWWoriginatingXWother,W{WWWW"W&W)W0WMW[W^WhWWWWWWWWW$ccasesWWcategoriesWcategorized?WcategorizingpWcategorygWcause^WWcauses/implies[WceasedWcellWcellsWWcellularzWcentralizedWcertaingWWWWchange|WWWchangesection5.3.2|VchangedW'Wchanges9WchargesWcheckeWWchoicesWchosenWNWchuck1WcipherWciphersuitesbitmapnoneweptkipaes-ccmpVW-WclarifylW$WclarifyingmWclassWWWclasspacketdelayjitterisdefiendasVclear`WgWlWtWWWWWWWWWW"W]WjWpW|WWWclearerWclearinguWclearlyFWbWWWkWclient'WWWcnyWcnmustbecorrespondentnodeyVco-located[WcodepWcodedWcoherencyWcoincidesWcolumn@WAWWWcolumnsWWcEKentaroFIshizuGMember^ Editorial_139`58a7.5bRemove section 7.5. cATMIH-3GLINK-SAP is a media-dependent SAP. If section 7.5 becomes one of the subsections under section 7, other media-dependent SAPs summarized in section 7.2.1 which are MLME_SAP, M_SAP and C_SAP should become sections in parallel with MIH_SAP, MIH_LINK_SAP and MIH_NET_SAP. However in section 7.5 MIH-3GLINK-SAP Primitives is redundant. Td2311g2217 2006/11/16 2006/10/23ber^ Editorial_139`58a7.5bRemove section 7.5. cATMIH-3GLINK-SAP is a media-dependent SAP. If section 7.5 becomes one of the subsections under section 7, other media-dependent SAPs summarized in section 7.2.1 which are MLME_SAP, M_SAP and C_SAP should become sections in parallel with MIH_SAP, MIH_LINK_SAP and MIH_NET_SAP. However in section 7.5 MIH-3GLINK-SAP Primitives is redundant. Td2311g2217 2006/10/31 2006/10/2311 2006/10/24 2006/10/231g4882{~=c#MIH_NET_SAP is missing in Figure 12d2093g4696k wAccepted 2006/11/16 2006/10/20Marked12igure 12ion of the context within which the acronym applies, as follows: NAS Non-Access Stratum (UMTS) NAS Network Access Server (RADIUS)c2NAS Non-access Stratum NAS Network Access Server d2035g2231vby comment 2032w Superceded 2006/11/08 2006/10/23ons in the same list.d2070g2230 2006/10/31 2006/10/23EAjayFRajkumarGMember^Technical, Non-binding_11`14a4bFor the same acronym for two distinct entities include indication of the context within which the acronym applies, as follows: NAS Non-Access Stratum (UMTS) NAS Network Access Server (RADIUS)c2NAS Non-access Stratum NAS Network Access Server d2035g2231vby comment 2032w Superceded 2006/10/31 2006/10/23onsistent with the other three definitions in the same list.d2070g2230 2006/10/31 2006/10/23ihiroN ohba‚"pcgivenWWWWWgives^WWgivingWgoingiWcWgoneWgood;W|WgrammaticalWWgroupfWnWgroupedWguaranteedWguidanceWguidingWh-aaayWhaddWhand{Whandle WGWWhandovergWqWtWWWWWWW2W6W;WiWvWWWWWWWWWWWWWhandover/seamlessvWhandover/softvWhandoversyWWWW_WxWWWWWWhandoverstatusWWhandoverstatusislistedbutnorowexistsforitlEKenichiFTaniuchiGMember^Technical, Binding_66`1a6.3.7.1b\Replace Figure 22 with the one described in Section 2 of 21-06-0460-04-0000-Basic_Schema.doccFigure 22 needs to be updated.d2201g2239v\Replace Figure 22 with the one described in Section 2 of 21-06-0460-04-0000-Basic_Schema.docwAccepted 2006/11/16 2006/10/21221-06-0460-04-0000-Basic_Schema.doccFigure 22 needs to be updated.d2201g2239v\Replace Figure 22 with the one described in Section 2 of 21-06-0460-04-0000-Basic_Schema.docwAccepted 2006/11/15 2006/10/2122EKenichiFTaniuchiGMember^Technical, Binding_234`65aAnnex Eandover Procedure from 802.11 to 3GPP2 as suggested in the accompanying contribution 21-06-0793. cDMIH Handover procedures described in the Annex 1 are not consistent.d391 2006/10/31 2006.10.2332EKenichiFTaniuchiGMember^Technical, Binding_234`65aAnnex Eindication is not defined in this draft specification.KEKentaroFIshizuGMember^ Editorial_74`37a7.3bjWe propose to change the section names as follows. 7.3 MIH_LINK_SAP Primitives 7.4 MIH_SAP Primitives cUnder section 7 in draft D02.00, subsection names are as follows which are not consistent. 7.3 Link Layer Primitives 7.4 MIH Primitives 7.6 MIH_NET_SAP Primitives d2239g2218 2006/11/16 2006/10/23EKentaroFIshizuGMember^ Editorial_146`52a7.6.4b+Replace "ommunication" with "communication"c$A typographical error "ommunication"d2316g2219 2006/11/16 2006/10/23as follows. 7.3 MIH_LINK_SAP Primitives 7.4 MIH_SAP Primitives cUnder section 7 in draft D02.00, subsection names are as follows which are not consistent. 7.3 Link Layer Primitives 7.4 MIH Primitives 7.6 MIH_NET_SAP Primitives d2239g2218 2006/10/31 2006/10/23Td311g2217 2006/10/26 2006/10/23EKentaroFIshizuGMember^ Editorial_74`37a7.3]bmihlinksdutransmitstatus6Vmihlinkup0Vmihnetsapprovidesl3transportservicesonthelocalnodeVmihnetsapshouldhavemihtpdataresponseconfirmVqc5.5W5.6.15W5.6.1.1W5W50CW51CW51-59"W52mW567W59^WxEKenichiFTaniuchiGMember^ Editorial_59`45a 6.3.5.3.6bFix it.c&POA should be PoA. In line 62 as well.d2183g2243 2006/11/16 2006/10/21EKenichiFTaniuchiGMember^Technical, Binding_200`6aAnnex BbReplace the texual Basic Schema definition in Annex B with the one described in Section 3 of 21-06-0460-04-0000-Basic_Schema.doc.c"Basic schema needs to be updated. d2411g2244wAccepted 2006/11/16 2006/10/21EEunahFKimGMember^Technical, Non-binding_3a1.2bYChange the direction of the arrow for command service from one direction to bi-direction.cCommand service is not performed only with the flow from upper layers to MIH function or MIH function to lower layers. It is rather achieved by the interaction between upper layers and MIH function, or MIH function and lower layers.d2011g2221i Vivek Guptajow for command service from one direction to bi-direction.10/21EEunahFKimGMembericable" .d169g2241bbmihlinksapabstractmedia-dependentinterfaceofmihfwiVbandWWbasedWWgWmWqWWWWWWbasic_WjWW:W7 cAWhen the information originates at a remote network element, the MIHF on the mobile node obtains it through MIH message exchanges with a peer MIHF entity that resides in the remote network element. Rationale: The current text only refers to the case where the MN retrieves information from other network nodes. Are other exchanges (e.g., a network node acquiring information from other network nodes or from a mobile node) not allowed by the standard? If they are allowed, the sentence should B)be made more general (see proposed text).d2015g2237wAccepted 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_3`62a1.3bAWhen the information originates at a lower layer of the protocol stack within a network element, the MIHF on the same network element obtains it locally through the service primitives of the SAPs that define the interface of the MIHF with the lower layers.cnicatypographicalerrorommunicationVa1WWa4Wability{Wable~WWWWabortqW%Wabout'WEWHWWWW{WWaboveJWabsenteWabstractWWacceptWlWaccepteduWaccess'WWW9WNW]W{WWWWWWWaccess-network-3zWaccessedWaccessingWaccomplishingWaccording{WWeWWaccordingtothetable15theonlyprimitiveforisismihgVaccordingtothissectionthemiistlvquerytlvcontainsaneVaccountWWWaccurate_Wacess9WachievebWachievedWackvW WWack-reqdWack-req/ack-rspWack-rspdWacknowledgedWretransmittedpacketsweretoarriveoutsideGVaddresscWdWjWW&W7W:W;WCWDWNWPWRWaddressesNW_WadhocWadjectiveWaffecting^W&XblsapWWmmWnWmaccWW:WWWmacaccessrouter#WmachinewWWWmacmobilenodeOWmacnewpoaWmade9WJWmagementlWmainhWmaintainaWmake@WAW^WaWWWWWWmakealltheflowdiagramsfollowasingletemplateandmakeVonsoflinkparameterlistconsistentthroughoutVmakethedefintionconsistentaVmakesW W'WmanagementjWW@WmWnWqWmandatory_Wmanipulation^WmappedW]W^Wmapping6W W WmarkedWmarksXWmatchWmaximizewWmaximumWmay_WiWlWsW{WWWWWWWW6WFWlWmWqWrWwWWWWWWWWmaybe>W?WmealWmeaningfulEWmeansrWmeanwhileWmeasuredWmeasurementsWmechanismWWmechanismspWrWwWVeb#Delete reference to 802.11 network.cQIf these are media independent SAPs, then why is the 802.11 technology specified?d2219g2268wAccepted 2006/11/16MarkedEGolmieFNadaGMember^Technical, Non-binding_71`1a7.2.2.1bInclude these primitives.cMIH_register and MIH_deregister are not included in this table, but are listing in 7.4 as key primitives as part of the MIH_SAPd2224g2269vby 2227w Superceded 2006/11/16Marked15NK_SAP is also used for L2 transport, which is duplicated and confusing.d2072g2230iRonnyj0Please refer to Comment #71 for suggested remedyk 33C F 33>cMIH_NET_SAP seems to be used for MIH transport services but MIH_LINK_SAP is also used for L2 transport. Thus, the role of MH_NET_SAP needs to be limited to L3 transport service.d2218g2232v2Use resolution as specified by comment 2071/2072 wAccepted-Modified 2006/11/16 2006-10-20Marked EEunahFKimGMember^Technical, Non-binding_71a7.2.2.1bpecified by comment 2071/2072 wAccepted-Modified 2006/11/15 2006-10-20Marked EEunahFKimGMember^Technical, Non-binding_71a7.2.2.1btion Service)@AR 33Q  33T _ 33R06-10-204EEunahFKimGMember^Technical, Binding_34`3EIEbremove,W6W{W~WWWWWWWWWWWWWWWW,WGWMWOWUWWW\W_WfW~WWWッWWWWremoveallrowsfromtableexceptfirsttwothatisleaveliUVremoveboth5and6Veotheroptions,Vremovesection5.1.8oraddsectiontodiscussotherhandoveVremovesection5.2Vremovesection7.5Vremovetheabovesentenseinun-authenticatedstagemnshoul~Vremovethefigure24andtheparagrahabovefigure24,Vremovethehistoryandscopeparagraphstartingatline20aVremovethesentenceGVremovethesentencehoweverinthisinstancetheopcodemay{VremovethissentenceVVremoved WrenamevWW:WrenameheadingtomihlinksapprimitivesVrenamethesectionasmihprotocoloperationvVrenamed"Wrenumber5Wreorg2W  bVChange the primitive "MIH_Get_Information.response" into "MIH_Get_Information.confirm"ctThe primitive from MIH to Decision Engine should not be MIH_Get_Information.response but MIH_Get_Information.confirmd2406g2225 2006/11/16 2006-10-2036EEunahFKimGMember^Technical, Non-binding_198aAnnex A4bA1. Change the first and the second, "MIH_Get_status" primitives on the flow into "MIH_Get_Status.request" primitives 2. Change all response type of primitives into confirm type of primitives; "MIH_Get_status.response" => "MIH_Get_Status.confirm" 3. Delete Link_Get_Status.request/response primitives as they are not defined in this draft specification. If "Link_Get_Parameters.request/confirm" primitives seem to be proper in this flow, use these primitives instead of "LiBnk_Get_Status" primitives.c-Some primitives are used wrong in this figured2408g2228vby comment 2407w Superceded 2006/11/16 2006-10-2037;N cALine 7 states that handovers should be executed during a pause in the conversation so as to minimze any perceptible interrruption in service. However, no quantitative measures are offered to back up this statement and show under what conditions improvements can be expected.d2007g2304 2006/11/16EGolmieFNadaGMember^ Editorial_2`47a1.2b%replace with "enabling more effectivec7line 47 reads: "thus enabling making of more effective"d2010g2305 2006/11/16a5.6.2.35.7`5.8⠃Y6j6.1.1⡃X6.1.26.1.3>6.1.4x6.1.5⣃W6.1.6@6.1.7A6.2.2?⦃9bbswicthsWswitchWW'W^WWWsynchronizationWsyntaxxWsystemjWlWW@WmWqWtabeWtable6W9WHWXWYWZWeWfWoWrWzWWWWWWWWW W W WWW9W:WNWUWWWWW7WZWWtargetpoaidentifierOWtcp/udpWtechnical+Wtechnologies^WwWtechnologyWqWtemplate8W9W:WtermWterminalWterminatedFWterminating4WterminologyWtermsWvWtext0WCWEWHW\W_WiWnWrW|WWWWWWW WWNWpWsWuWzWtexts"W+W3Wtextual_WtexualWQWtha`Wthat4WCWQWUW\WcWjWlWsWyWWWWWWWWWWWW W$WSWUW^WgWoWqW,cusefulWWgWwWWWuser4W5WWWWWusersWWWWWusesWWWWWWWWusing'WaWhWWWWW]WlWrWWWWWWutilizeGWvagueWvalidJWWaWvalidityaWvalueEWFWJWKWLWNWOWPWQWnW{WW W&W=WPW\WeWWWWvalueisnotclearlydefinedFVvaluesoWpWWWWWW&WvariableEWHWcWfWvarialbeWvariants[WvariesWvariousWWvender\Wvendor\Wversion&WverticalWverticalhandoversthisinvolvesmnsmovingbetweenaccesspVverylW"WviaWWWvisitedWvisited/homezWwant'WW'WWwantingWwantsTWwastWuWWwhatisoption1arethereanyotheroptions,V!XHcmihcapabilitydiscoveryprocedureisalsousedbynetworktV 0XcthisprocessmaybecarriedoutoncethecoreelementsofthVthissapdefinesthegenericmediaindependentlinklayershbVthissectionalsodesecribesmihprotocolwithoutackoperatvVthissectiondescribestypesofevents6.1.3talksaboutlocVthissectiondiscussesmediaspecificammendmentswithoutstVMRb[b@c!^kA"@#bA$bAn%v3&@Y'@bA)@y*j,@c-cA/^0v1@3@v4@5@3c6v8bA69bA:@ <^>c@@ AcDcFa0G@$cAH@ JbAL.M@-GNbA3cB,j6P@+2ScAT@:V@BY@zZcA\bAcA/]cAF^bAfcAKffocqbACrbAsbAvbwbBzc~ccbAdbAcAcB^cBbAbbACEcA`k=Kbmethods8WQWlWWNWPWmetricsWmhzWW6W:W;W=W>W?WAW`WeWlWqWvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW!W$W)W*W+W.W/W0W4W5W?W@WCWDWEWFWmihcommandidVmihconfigure2Vmihderegisterrequest/VmiheventidVmihgetstatus0Vmihhandovercommit6Vmihhandovercomplete7Vmihhandoverinitiate4Vmihhandoverprepare5Vmihlinkdetected3Vmihlinkdown1Vmihlinkeventrollback5Vmihlinkgoingdown2Vmihlinkhandovercomplete8Vmihlinkhandoverimminent7Vmihlinkparametersreport4Vmihlinksapisactuallymedia-independentwhichisgoingtoVJcthenamesofprimitivesandmessagesneedtobeconsistentt Vthenoandmihactionidentifierfieldsinthetabledon'tlVtheoveralldescriptionoftheservicesshouldaddresssystejVtheparagraphandfigureformihregistrationisagenerald,VtheparametersinmihcapabilitydiscoverrequestmessagearVtheparametersinmihcapabilitydiscoverresponsemessageaVtheprimitiveformihre-registationismissing.Vtheprimitivefrommihtodecisionengineshouldnotbemih VthereaderisreferredtothedraftrequirementsdocumentfoVtherepresentationoftheseinformationelementsdescribedi8VthesamecommentappliestothefollowingsectionsfV6EHongseokFJeonGObserver^Technical (was Editorial)_160a8.3.5baChange the "No" into "MIH Action Identifier" and "MIH Action Identifier" into "MIH Message Name".cgThe "No" and "MIH Action Identifier" fields in the table don't look like right titles for their values.d2357g2224i Vivek GuptajUp.indication" => "MIH_Link_Up.indication" "Link_Down.indication" => "MIH_Link_Down.indication" 4. Change "MIH_Switch" into "MIH_Switch.request"cThe Link_parameters_change.indication primitive is not defined in this draft specification. Also, it is necessary to use the exact primitive names on this flow.d2409g2229 2006/11/15 2006-10-2038EHongseokFJeonGObserver^Technical (was Editorial)_160a8.3.5baChange the "No" into "MIH Action Identifier" and "MIH Action Identifier" into "MIH Message Name".cgThe "No" and "MIH Action Identifier" fields in the table don't look like right titles for their values.d2357g2224i Vivek Guptaj*^ Editorial_173`49a8.5.1.1bChange the type field in the table as follows. Event List (1) Command List (2) Transport List (3) IS Query Type List (4)c\The parameters in MIH_Capability_Discover Request message are linked with wrong type values.d2375g2222 2006/11/16 2006-10-20EHongseokFJeonGObserver^ Editorial_174`7a8.5.1.2bChange the type field in the table as follows. Event List (1) Command List (2) Transport List (3) IS Query Type List (4)c]The parameters in MIH_Capability_Discover Response message are linked with wrong type values.d2376g2223 2006/11/16 2006-10-20r^ Editorial_161a8.3.5baChange the "No" into "MIH Action Identifier" and "MIH Action Identifier" into "MIH Message Name".cgThe "No" and "MIH Action Identifier" fields in the table don't look like right titles for their values.d357g2224 2006/10/26 2006-10-2025EHongseokFJeonGObserver^ Editorial49 EHongseokFJeonGObserver^ Editorial_161a8.3.5baChange the "No" into "MIH Action Identifier" and "MIH Action Identifier" into "MIH Message Name".cgThe "No" and "MIH Action Identifier" fields in the table don't look like right titles for their values.d2357g2224 2006/11/12 2006-10-2025EHongseokFJeonGObserver"MIH_Link_Down.indication" 4. Change "MIH_Switch" into "MIH_Switch.request"cThe Link_parameters_change.indication primitive is not defined in this draft specification. Also, it is necessary to use the exact primitive names on this flow.d409g2229 2006/10/31 2006-10-2038EHongseokFJeonGObserver^ Editorial_161a8.3.5baChange the "No" into "MIH Action Identifier" and "MIH Action Identifier" into "MIH Message Name".cgThe "No" and "MIH Action Identifier" fields in the table don't look like right titles for their values.d2357g2224 2006/10/31 2006-10-2025EHongseokFJeonGObserver?Hb1clarifytheencodingoftable10eitherwithadiagramorHV1defineadistincttlvforeachofservingfaaddressserviNV1defineencodingdetailsofthevaluefieldJV1deletel2transportinthemihnetsapV1deletelinkswitchprimitiveasitisnotdefinedinthisV1howeverafterauthenticationandattachmenttoacertainpV1movethetextoutofthecurrent6.3.3andCV1removesourceidentifieranddestinationidentifierfromtMV1shouldonlyhavetwodefinitionsoneforcurrenteither12\V1signalstrengthV1-127W1-2W1.3W1.4W1.5W10HWWW10mihresourcequerylrclienttonetworksentfrommihfiV11eWW12=WWW\WW13"W\WW14&W15eWWWHWJW|WWWWWW W WWWWW-W7W9W:WEWFWMWNWOWRW\WgWoW~W b2biterrorrate@21-06-0738-01-0000-8@Z21-06-xxxx-00-0000-s@31@5@\6.3@7.2.2.2@8.4.1.20@4802.2ah@ageneraldescriptionofmihregistrationproceduresisprop@addanewcolumncrossreferencingwhereeachentryinthet@radddetailsontheendodingofthedatarateintegerfloatin@addthefollowingdescriptionsattheendoffirstsentence@allow@annex@}are@be@capabilities@changecategoryofmiheventsubscribeandmiheventunsubsc@changepercontribution21-06-0xxx-00-0000-rmodeltext53@changetomihgetstatus@clearlydeterminethegroupingsforevents/links/remoteeven@`config@decision@defineencodingdetailsofthevaluefield@deleteatleastpreambleandstartofframedelimiterfromf@deletemihsapfromendofline@mdeletetheunusedacronyms@*descriptions@document@effect@qcmappingWmapsjWmatchWW WmaterialWWmaxWWmaximumWWmay'W\W{WWWWWWW-W>WFWGW^W|WWWWWWWWWWWWWmdi+meanWmeaningWXWmeansWWWmeantWWmeasureWmeasuredWmeasurementWmeasurementsWWWW5WbWjWoWtWWWmedia-dependentWWmentionsWmeshWmessage(WoW{WWWWWWWWW1WJW`WdWfWgWlWWWWmessagepadding/alignmentruleismissingJVmessage-iddWmessagesWWW W W*WKWLWMW]WdWgWqWsWWWmessagresdWmethodNWWmethods8WiWW&WNWPWWWmhW Wmibs[WmicroWmics7W[EBenjaminFKohGMember^ Editorial_20`48a5.3.2b'Replace with: The MN has a MIHF imple-cThe MN has an MIHF imple-d2057g4683 2006/11/16 2006/10/20EBenjaminFKohGMember^ Editorial_23`56a5.4.3bTReplace with either: through an insecure port would or: through insecure ports wouldcthrough insecure port wouldd2063g4684 2006/11/16 2006/10/20EBenjaminFKohGMember^ Editorial_23`65a5.4.3b6Replace with: of this information is outside the scopec)of this information are outside the scoped2066g4685 2006/11/16 2006/10/20EBenjaminFKohGMember^ Editorial_32`2a5.6cure port wouldd2063g4684 2006/10/31 2006/10/20EBenjaminFKohGMember^ Editorial_23`65a5.4.3b6Replace with: of this information is outside the scopec)of this information are outside the scoped2066g4685 2006/10/31 2006/10/20EBenjaminFKohGMember^ Editorial_32`2a5.6ng_17.3.13btheyWWmWthis1W4W5W6WFWMWRWSWTWdWhWuW{W~WWWWWWWWWWWWW WWWW'W-W3WFWTW^W_WaWbWgWjWnWoWrWwWWWWWWWWWWWWWWWthisistoscanacertainfrequencybandanddetermineoneoVVthisprimitiveisgeneratedbyanmihuseraregistrantsuch4VthisprimitiveisgeneratedbymihfunctiononnewpoatoinVthisprimitiveisusedbyanmihusermihfunctionthesubsc5Vthissectionisoutofplacerelocateitscontenttothepro1VthoseQWWthoughlWthoughtsWthreejWWthresholdWthroughinsecureportswouldVthroughouthWWWWpWthuseWgWmWtimeaWgWtimerWtimesWtitlegW W"Wtitles W cinWWWWWWWWW!W"W#W%W&W*W+W,W-W4W8W?W@WFWGWHWIWKWMWNWOWSWWWYW\W]W^WdWeWfWgWkWlWnWpWqWrWsWuWvW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWincurrentdraftlinkparameterthresholdconfigurationisvVincurrentdraftmncandiscoverandobtaininformationofaVincurrentdraftwehavemiheventregisterrequestandlinkVinmihhandoverprepareprimitivesqueryresourcelistandavaV~breporting8WrepresentationW8WSWWWrepresentationsW^WrepresentediWrepresentsWWWWWWrepresnetsjWreqWrequestfWWWWW$W/WCWFWMWqWrWWWWWrequest/confirmWrequest/responseWrequesting^WrequestsWWWrequirementsWWreservedWWreserved9-31VresourceWWWresources_WWWWrespWrespectivelyWWfWoWmWresponse'WqW{WWWW WWDWWWWresponsesnWrestUWrestricted{WresultW$WMWresultssWretitleWretitlefigure25transportofmihframeinieee802l2dataVretransmissionWWretrieval'WWretrievedEWretryWreviewWxWreviewsection8.5.2andupdatealltypevaluesasdefinediVrevisekW,bdecisionW'WdecodedPWdeeperlWdefensiveXWdefiendWdefineIWJWKWLWMW`WcWdWlWWMWNWWWWWdefineaself-containedmacaddressfieldthatcanindicatecVdefineaseparatecategoryforitVbEBenjaminFKohGMember^ Editorial_66`38a6.3.7.2b&Replace with: are included in Annex E.care included in Annex C.d2203g4702 2006/11/16 2006/10/20EBenjaminFKohGMember^ Editorial_152`11a8.1b+Enhance Section 8.1 to improve readability.cABThe intended meaning of "IEEE 802.21 supports Media Independent Handover Function in mobile node, and network" is unclear. Is it intended to mean that IEEE 802.21 supports the implementation of a MIHF in both mobile as well as network nodes? In general, the text in Section 8.1 contains many examples of awkward phrasing.ial_152`11a8.1b+Enhance Section 8.1 to improve readability.cABThe intended meaning of "IEEE 802.21 supports Media Independent Handover Function in mobile node, and network" is unclear. Is it intended to mean that IEEE 802.21 supports the implementation of a MIHF in both mobile as well as network nodes? In general, the text in Section 8.1 contains many examples of awkward phrasing.12L^non-binding(W)W+W0W2W7W<WBWWW[Wbtransportlist3VVtransportedWtransportingmWtreatiseWtreeWtriggeringwWtriggers]Wtry'WtspecWtspecsWtuplesWtvlWtwoWWUW[W\WWWWW cBd2319g4689 2006/11/16 2006/10/20EBenjaminFKohGMember^ Editorial_154`17a8.3.1b/Replace with: Discovery is implicitly performedc"Discovery is implicitely performedd2332g4690 2006/11/16 2006/10/20 EBenjaminFKohGMember^Technical, Binding_154`61a8.3.2bEnhance Section 8.3.2 to simply highlight the existence and purpose of the Ack bits. Specific implementation suggestions should be removed or else moved to the Appendix.cAfThe description of the Ack operation contains many specific details that should be left out. Examples include setting value of timer to RTT, source making only two retransmission attempts, etc. Also too much details on how the destination and source nodes should handle the received or sent packets that should ideally be left as an implementation exercise.fd2342g4691vsee 339w Superceded 2006/11/16 2006/10/20Marked!EMasahiroFKurodaGMemberng_32`1a5.6cimplementationwWWW WGWWimplementations`WWimplicitelyWimplies{WZWimplyWimportant~WimposesWimpossibleWimproveWWWWimprovementsWin'W1W3W8W<W=WBWDWEWHWWWXWYWZW[W_WaWbWcWdWeWfWgWjWlWmWnWoWqWyW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WYcininmihprotocoldescriptionitsaysthathoweverinthisins@inconsistencybetweennameindescriptionandnamecolumnsf@inconsistencywithnamingwhichmakesithardertofindrela@xindependent@information@introductory@ip@isgyisdefiendas@Tit@^itisnotclearwhatmihnmssapfunctionisonlydefinition@0itisnotclearwhyisistheonlyservicethatcansupport@itisunclearhowthismodelcanapplytopeertopeerconne@itsnotclearwhyack-req/ack-rspareneeded@late@less@Jlinkgetparametersprimitivemissingintable17@linktype@made@mapping@measures@might@!mihcapabilitydiscoveryprocedureisalsousedbynetworkt@miheventsubscribeandmiheventunsubscribearecommandse@Xmihre-registrationmessageformatshallbeaddedhere@mihfcapability@L!^Technical, Binding_32`1a5.6bAdd the definition of NMS to section 3 and the description of MIH_NMS_SAP primitives to 7.7. Introduce the modifications proposed in the submission 21-06-0786-00-0000_MIH_NMS_SAPclarification.doc into the 802.21 draft.cThere is no NMS definition in the standard and no section for the detailed description of MIH_NMS_SAP primitives. Therefore,we need a definition of NMS and a new section to describe MIH_NMS_SAP primitives.d2090g2216iRonnyjZInclude MIH_NMS_Initialize operation as part of link command and delete MIH_NMS_Get_State.kMS_SAP. Define primitives appropriately. Assigned to Vivek+Ulises Add: - MIHInitialize - MIHGetState - MIHResetwDeferred 2006/11/16 2006/10/2312deally be left as an implementation exercise.fd342g4691 2006/10/31 2006/10/20!EMasahiroFKurodaGMember^Technical, Binding_32`1a5.6!EMasahiroFKurodaGMember^Technical, Binding_32`1a5.6 2006/10/26:  !"#$%&')*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~〃ぃゃッ㄃ㅃㆃ㇃㈃㉃㊃㋃㌃㍃㎃㏃㐃㑃㒃㓃㔃㕃㖃㗃㘃㙃㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃg^_`abcd€€€€€TbservicesjWlWWWW W4WgWjWoWqWWWservingsW+W6W7WNWWservingpoathenetworkpointofattachementofthemobilensVsessionzWW'W*W+W/Wsessionid/VsessionidWWset5WWWWWWNW^WqWrWWWsetsWsettingWseveralWshallFWmWLWshifted"Wshould'WeWfWhWoW~WWWWWW W"W+W[W\WeWqWrWWWWWWWWWWWshouldbeexplainedastohowtowhichmediaspecificinterfVshouldn't~WshowRWSWshownxWW"WshowsmWWWside>W?WsignalWZWWWsignalingwWW/VsourceidentifierfWspecific\WrWWWWW W9W^WgWspecificationWW^Wspecified^WcW1}bitemWitemsWWits1W+WUWgWWWjustWkeep+WkeptWWkindNWWknowdWlWWknowledgerWlWWl2tWWWkWlWqWWWWl28Wl3WWWW WlWWWl3mmpWlabels/terminologyWlanguageWlargeW"EMasahiroFKurodaGMember^ Editorial_13`49a5.1.3bAThe title of section 5.1.3 should read "Quality of Service". The texts from 51-59 on page 13 should be as stands. The remaining texts should be shifted to new section 5.2.2 with the title of "QoS Design Principles". Current texts under section 5.2 should be renamed as section 5.2.1 MIHF Design Principles. Texts for these remedy are shown in submission 21-06-0787-00-0000_QoS_Clarification.doc. cA`The title of section 5.1.3 is not appropriate. The texts from line 51-59 are appropriate for the introduction of section 5.1.3. The remaining texts are too detail. Under section 5.1, section 5.1.3 is very long compared with the other sections which is unnatural. Also, a clear approach for QoS in this standard should be described in section 5.1.3. `d2038g2221 2006/11/16 2006/10/23#EJinFLee^Technical, Non-binding_86`9a7.3.14b06/10/23_  2006/10/23EAjayFRajkumarGMember^Technical, Binding_2`20a1.2b"Define a separate category for it.c@Is the reference to IEEE 802.15 under micro cells is incorrect. d2008g2233iMichael WilliamsjChange line 20 to read "The overall network may include pico cells such as IEEE 802.15, micro cells e.g. IEEE 802.11, and macro cells (e.g., 3GPP, 3GPP2, or IEEE 802.16 coverage) which will in general intersect.mAccepted-ModifiedwAccepted 2006/11/16 2006/10/23Marked3`49a5.1.3bAThe title of section 5.1.3 should read "Quality of Service". The texts from 51-59 on page 13 should be as stands. The remaining texts should be shifted to new section 5.2.2 with the title of "QoS Design Principles". Current texts under section 5.2 should be renamed as section 5.2.1 MIHF Design Principles. Texts for these remedy are shown in submission 21-06-0787-00-0000_QoS_Clarification.doc. c/10/24 bncmsmWneat WnecessaryyWgWWnecessityWneedTWxWWWWWneeded$W3WWneeds WTWWWnegotiatedWneighborWW=WWWW W W WWjWoWWnetworkFWiWsWtWyWWWWWW+W4W7W9W>WCWDWRWZWlWmWnWqWrWwW|WWWWWWWWWWWWWWWWnetworkusingthemihprotocolVnetwork-initiatedgWWnetworksFWZW|WWnetworks/poas'WWnewCWWWWWWW"W'W6W9W\W^WWWWnewlinkidentifierWnihoWWnms3W!WpWno@WAW WWJWWnomiheventnamemiheventtypeAVnodelWsWyW~WWWW7WgWjWlWmWWWWe_^cthelengthvalueofthelengthvarialbefirstoctetcannottVthelinklayerprimitivesshouldhaveanadditionalsubsectifVthelinkparametertypeusesapairoflinktypeparametertypVVthelinkparameterschangeindicationprimitiveisnotdefinVthemeasurementsmayreportsignalqualitysynchronizationtVthemihfunctiondiscoveryhasonlybeenlistedhereandisVthemihlinksapislistedhereasasubsectionofthemediaVthemihsapspecifiestheinterfaceofmihfwithotherhigheVthemihscanconfirmprimitiveinthecurrentdraftcannotVthemihstatesareneededforthecorrectoperationofmihp)V0VhVthemihftlvencodingschemeisthesameastheencodingschmVthemihfusesmihgetinformationprimitivetogetmihinforVthemnhasanmihfimpleVthenamefieldsofrssisnrc/iberanddataratearenotusUVthenamesofprimitivesandmessagesinthisfiguredon'tma V@cassignedoWassociatelWassociatedSWWWassumeEWHWWWassumedWassumingdWat1WWWWW*W_WWWWWattachmentWattempts WattributedWauthenticated~WWauthenticationWauthenticator;Wavailable~WWW&WWWWavailableresourceWavailableresourcelisWaverageWY& 2006/11/16 Non-binding_170`27a8.4.1.30bA6[Delete the subsection 8.4.1.30, page 170, link 32] : 6@A  33cuTable in page 170 for Abort Reason doesn't make sense. It should be deleted unless the substituted text is provided.d370g4928 2006/10/31&EJInFLee^Technical, Non-binding     33fcWith the current draft, I don't see any different action for MIH re-registration. To clarify related to MIH re-regisration, I propose the additional description as suggested be added.d265g4927 2006/10/31%EJinFLee^Technical, Non-binding_170`27a8.4.1.30bA6[Delete the subsection 8.4.1.30, page 170, link 32] : 6@A  33cuTable in page 170 for Abort Reason doesn't make sense. It should be deleted unless the substituted text is provided.d370g4928 2006/10/31&EJInFLee^Technical, Non-binding-btoimprovethereadabilityofthetextitmaybettertoprovVtomakeitreadbettermovelinkeventnametothe2ndcolum@Vtomakeitreadbettermovemiheventnametothe2ndcolumnAVtooWtpWFWtransfermWtransfersWtransmissionkWWtransmitWtransportuWWWWWW WWWjWmWoWsWWWWWWbtoimprovethereadabilityofthetextitmaybettertoprov@transportlist3@type@updatetable32toreflectthechangesmadeto6.3@uses@wassuccessfullyretrievedornot@,whentheinformationoriginatesatalowerlayeroftheprot@whenthemihfinthenewpoareceivesthismessagefromthe@?within@cc1encodingdetailsofthevaluefieldmissing@1unclearabouthowthe4fieldsareencodedintable9one@U2extendedschemaisnotdescribedinannexb@33@A5.1@5.5@6@8@w802.21@acolumnheadingofremotedirectionisincludedinthetabl@natypographicalerrorommunication@acknowledged@iafter@always@and@jani@any@Oareincludedinannexc@@assigned@avoid@be behorizentalintra@X'EJinFLee^Technical, Non-binding_105`28a 7.4.7.1.3bA[Modify the subsection 7.4.7.1.3 as suggested] : 7.4.7.1.3 When Generated This primitive is generated when MIHF users makes handover decision and try to disconnect the old link and establish the new link switch an active session from one link to another.@ of PoA. I would suggest the value be removed unless having the value in PoA Capability IE does come with additional benefits. If it does, another values related to IP address configuration would be applicable.d2184g4929 2006/11/15'EJinFLee^Technical, Non-binding_105`28a 7.4.7.1.3bA[Modify the subsection 7.4.7.1.3 as suggested] : 7.4.7.1.3 When Generated This primitive is generated when MIHF users makes handover decision and try to disconnect the old link and establish the new link switch an active session from one link to another.@26&EJInFLee^Technical, Non-binding_60`14IKyESrinivasF Sreemanthula^Technical, Non-binding_10`1a4.0bClean up the section.cFollowing acronyms are not used. ANI, BSC, H-AAA, HIP, HMIP, PDSN Following acronyms are incorrect. CN (must be correspondent node) NAS has same two acronyms.d2032g2238 network-initiated and network-controlled handovers. Does it?d2050g2237vIts up to upper layers to figure out how to utlize services provided by .21. Commenter needs to provide more details on problem and remedy.wDeferred 2006/11/08 2006-10-23yESrinivasF Sreemanthula^Technical, Non-binding_10`1a4.0bClean up the section.cFollowing acronyms are not used. ANI, BSC, H-AAA, HIP, HMIP, PDSN Following acronyms are incorrect. CN (must be correspondent node) NAS has same two acronyms.d2032g2238the above are covered adequately in the later sections. Need different sections to cover the above.h handovers either by providing 066 2006/10/25uqbdocumentMWhW)W0W1W]W^WaWdWgWhWdocument21-06-0738-01-0000-83triggersdocdescribehow802]VdoesUW$W^WWdoesn'tWdoneW$WdownWW\WcWWdraftWWWWWWW!WpWWWWWdrawWduesWEWdynamicNWe@WAWQWWWWWWWNWgWqWwWWWWWWeachlWWWWWWFWJWNW[WWWWeditWeditthetextbasedonresultofclarificationVeditorialWWWWALc5.1"W5.1.3"W5.3<W5.3.14W5.3.2|W5.4<W1CcquantitativeWWquerierUWeWqueriesWquerresourcelistWquerresourcelistandavailableresourcelistnotdefinedVquerynWeWWWWWWWqueryresourceflagWqueryresourcelistWWqueryresourcelistshouldbequeryresourceflagVquestionWquicktWr1RWr3zWWr3mustbepossibleonlinkbetweenvisited/homenetworkandzVradio`WradiusWraeWeceivingWrecent9WrecognizedUWreduceWreducedWredundantWWreferWreference]WrWxW WRWreferencetoannexgisnecessarytounderstandtheprimitivxVreferences$Wreferencesnotorderedproperly$VreferredWreferringnWrefers<WWWreflectingfWrefuseWregardinguWregisterW-W@WKWregistrant4Wregistrantwouldbeanmihusernotmihfunction4VregistrationW,W-W/WF[ dÄ3*Ä31WÄ32sÄ33eÄ34 Ä35Ä36Ä37Ä38@Ä39Ä3:Ä3AtÄ3B]Ä3C2Ä3DXÄ3EÄ3FYÄ3GZÄ3HÄ3I3Ä3JÄ3QÄ3RfÄ3STÄ3TRÄ3UÄ3VÄ3WÄ3XÄ3YÄ3ZÄ3acÄ3b#Ä3c_Ä3dSÄ3eÄ3fÄ3gÄ3hÄ3iUÄ3jÄ3qÄ3rÄ3s,Ä3tAÄ3u-Ä3v$Ä3w.Ä3x/Ä3yTÄ3zÄ3Ä3Ä34Ä3Ä35Ä3Ä3Ä3Ä3^Ä3Ä3Ä3'Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3BÄ4Ä4Ä4Ä4uÄ4Ä4CÄ4Ä4Ä4DÄ4Ä4!EÄ4"Ä4#Ä4$SÄ4%Ä4&Ä4'Ä4(FÄ4)Ä4*Ä41Ä42Ä43aÄ44Ä45Ä46Ä47Ä48Ä49Ä4:)Ä4Aka7.4.10.1.2Ѓ7.4.10.3.27.4.10.4.47.4.11.3.4W7.4.10.4.47.4.11.3.47.4.12.4.4V14u7.4.14.1.17.4.14.1.2ՃփB7.4.14.1.37.4.14.1.47.4.14.2.17.4.14.2.2׃C7.4.14.3.47.4.14.4.2D7.4.15.3.27.4.15.4.2E7.4.2.1.27.4.2.2.27.4.3.1.27.4.3.1.347.4.3.2.27.4.4.1.157.4.4.1.27.4.4.2.27.4.5.1.27.4.7.1^7.4.7.1.2ッ7.4.7.1.3'7.4.8.1.4΃7.4.9.1.27.4.9.2.2σ7.5كS7.6.2.3.47.6.2.4.37.6.47.6.5.1.2F8.1ۃ܃8.2a8.2.1ރ8.3)0h8.3.18.3.1.28.3.2v{ Gd8.3.3.1bH8.3.3.2I8.3.4߃J8.3.4.1*8.3.4.28.3.5:K8.4mL8.4.1.11p8.4.1.12\8.4.1.208.4.1.30%8.4.1.328.4.1.35nW8.4.1.358.4.1.36nV8.4.1.36nW8.4.1.7c8.4.1.9d8.5o8.5.1MWWctableismissinglinkcommandsincludinglinkeventdiscoverVtable-26WtablesMWtakeWWWtakingWtalksWtallUWtargetsWZWWWtargetpoaidentifierWBWOWtargetposidentifierWBWtargetposidentifiershouldbetargetpoaidentifierBVtechnologiesW^WWWtechnologyWWWWW]W_WWWtemplate8WeWterm(WWterminologiesWterminologyWVWWtermsyWWvWWtext0WCW\WWWWWWWWWWW WW%WjWmWpWqWuWWWWWWammaticalerrorsandneedstobefixedVtexthasnothingtodowithhandoverpolicyVtextstatesdifferentprotocolstacksareshowninfigure4VtextstatesthatusecaseandhandoverareintheappendixyVtexts"WtexualQWthanWCWDWGWNW7;EGolmieFNadaGMember^ Editorial_vi`20bQremove the history and scope paragraph starting at line 20 and ending at line 25.c@The scope description should be identical to the IEEE 802.21 PARd2001g2302{l) none needed 2006/11/162302{l) none needed 2006/10/31Pslee#$%&')*liu+,-./0123nada⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃ⰃⱃⲃⳃⴃCapability IE does come with additional benefits. If it does, another values related to IP address configuration would be applicable.Dciwouldsuggestthevalueberemovedunlesshavingthevalue&VidDWbW*W-W/WHWIWgWideally WidenticalWidentifiedWidentifierDWWWW9W\WWWWidentifiersW\WidentifiesfWidsDWVWWWWW ^editorial$3@ACDZefhkx⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⬃⭃⮃⯃Ⰳⱃⲃⵃⶃăǃփ׃܃݃߃ W"5ABHIMPTVWXYZ[㋃㌃㍃㎃㐃㓃㚃㥃㧃Ń4y*jOSession ID is carried in Variable Header part and not needed for every message.mRejectedwRejected 2006/11/16 2006-10-2324+EXiaoyuFLiuGMember^Technical, Binding_68`13a6.4.4bAA general description of MIH Registration procedures is proposed. The following technical issues should be considered: - The registration and deregistration between MIHF in MN and MIHF in a serving network. - The registration and deregistration between MIHF in a serving network and detected network. - Re-Registration when a MN changes its attached POA. - Registration update to keep the active session alive. Accept the proposed normative texts in the Remedy 1 of 21-06-0xxx-00-0000-MIH_RegBistration_Amendments.doc c1The specification in Section 6.4.4 is missing. d2215g2211vFResubmit in next round after more offline discussion and harmonizationwRejected 2006/11/16 2006-10-232006-10-2324y ^'bcMIH_Switch command does not want the old link to be diconnected as always. The old link could be maintained as suggested link action such as Link_Power_Down or Link_No_Action etc. Therefore I propose the subsection 7.4.7.1.3 be changed d2281g4930vAw7.4.7.1.3 When Generated This primitive is generated when the MIH User decides to switch from one link to another w@A* 33v *wAcceptedqDraft should use MIH Users all over the draft (and not MIHF Users). Please make this change throughout the draft. 2006/11/16A'cmihfcapabilityWmihfsWBcsetWWWWW>WCWDWNWdWgWWWWsetsdWsetting WdWseveralyWshallmWWW*W1WkWxWshortlWshould'W0W>W?WBW\W_WfWiWjWvW}W~WWWWWWWWWWWWWWWWW WW W"W%W&W,W-W/W:W<WAWBWEWHWIWRWZW[W^WaWbWcWeWjWkWlWoWqWsWtWWWWWWWWWWWWWshouldn'tWf3EXiaoyuFLiuGMember^Technical, Binding_67`61a6.4.2b+Proposed texts are needed for this section c8The specification for MIH Function Discovery is missing.d2213g2224iRonnyjAdd the following text into page 67 line 65 in Section 6.4 .2 Detailed procedure of MIH function discovery over layer 2 is described in 8.3.1.mAccepted-Modified1a6.4.2b+Proposed texts are needed for this section c8The specification for MIH Function Discovery is missing.d2213g2224iRonnyjAdd the following text into page 67 line 65 in Section 6.4 .2 Detailed procedure of MIH function discovery over layer 2 is described in 8.3.1.mAccepted-Modifieds are needed for this section c8The specification for MIH Function Discovery is missing.d2213g2224iRonnyjAdd the following text into page 67 line 65 in Section 6.4 .2 Detailed procedure of MIH function discovery over layer 2 is described in 8.3.1.mAccepted-Modifiedvbageneraldescriptionofmihregistrationproceduresisprop+ValistofoneormoretspecVa-1W(ba1.4@absent@addaddanewcolumncontainingtheappropriatetypeiereqind@addanewcolumncrossreferencingwhereeachentryinthet@radddetailsontheendodingofthedatarateintegerfloatin@addoneoptionalnetworkstandardsietotypecontainerpoa@%addthefollowingdescriptionsattheendoffirstsentence@addthefollowingtables@5addttional@allallow@alsoupdatetable15andsapdefinitionsinsection7.4x@anmihposmayact@annex@}are@at@bmihlinksapabstractmedia-dependentinterfaceofmihfwi@be@behorizontalintra@Vbeneficial@betwen@cannot@cannotberestrictedtoheterogeneous@capabilities@changecategoryofmiheventsubscribeandmiheventunsubsc@changepercontribution21-06-0xxx-00-0000-rmodeltext53@changethenameofthesection5.3.2inadeploymentexample@'3vAdd the following text into page 67 line 65 in Section 6.4 .2 "The detailed procedure of MIH function discovery over layer 2 is described in 8.3.1."wAccepted-Modified 2006/11/16 2006-10-23s between 802.11 and 802.16 networks.d396g2222 2006/10/31 2006-10-233EXiaoyuFLiuGMember^Technical, Binding_67`61a6.4.2b+Proposed texts are needed for this section c8The specification for MIH Function Discovery is missing.d2213g2224iRonnyetween 802.11 and 802.16 networks.d396g2222 2006/10/31 2006-10-233EXiaoyuFLiuGMember^Technical, Binding_67`61a6.4.2b+Proposed texts are needed for this section c8The specification for MIH Function Discovery is missing.d2213g2224iRonnyyuFLiuGMember^Technical, Binding_67`61a6.4.2b+Proposed texts are needed for this section c8The specification for MIH Function Discovery is missing.d2213g2224iRonnyF entities to interact with each other.g2217)$ ycthe,W-W.W/W0W2W3W4W5W8W9W>W?WEWFWGWLWMWOWPWSWTWUWXWYWZW[W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWpWqWrWsWuWvWxW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW9observer㏃㐃㑃㖃other+b Remove it.cWhat is the purpose of MIH_Network_address Information? None of the handover signaling flows in appendix A have used the command indicating that it is redundant definition in 802.21.d2110g2245iRonnykAcPurpose of MIH_Network_address Information is to get information related to network address configuration prior to handover. At last comment resolution, suggested modification of MIH_Network_Address Information was accepted and modified function is dynamic mechanism of PoA IP congifuration method IEs suggested and included in the Information service. cmRejectedv\Annex is just an example. It doesn't mean the command isn't needed or mean it isn't useful.wRejected 2006/11/16 2006-10-234ESrinivasF Sreemanthula^Technical, Binding_44btwork_Address Information was accepted and modified function is dynamic mechanism of PoA IP congifuration method IEs suggested and included in the Information service. cmRejected[1crejectTWrejectedpWrejectsWJUcthesessionidshallbeusedinallmihmessagestoavoidco*VthesourceidentifierparameterinthemessageidentifiesthefVthespecificationformihfunctiondiscoveryismissing3Vthespecificationinsection6.4.4ismissing+VthesystemmanagementserviceisunexpectedandhasnotbeenVthetablesinsections8.5.1.3to8.5.1.6arenotconsistentMVthetitleofsection5.1.3isnotappropriate"Vthetlv-basedqueriesinsection6.3aredrivenfromlocatioVthetypeofparameterisnotfullydefinedforthegenerictVthetypevalueofipaddressconfigurationmethodslistisnPVthetypevaluesusedinsection8.5.2donotmatchtheonesVtheuseofn-thingydefinitionsintheterminologysectioniVthevalueipversion6prefixavailableinpoacapabilityie&V6 9bA[1] Add the following new IE entry to Access Network specific information: | 2.1 | TYPE_IE_ACCESS_NETWORK_OPERATOR_IDENTIFIER | The operator of the access network | 6.3.5.1.2 | [2] Add TYPE_IE_ACCESS_NETWORK_OPERATOR_IDENTIFIER in the Type field of the table in Section 6.3.5.1.2. [3] Add Access Network Operator Identifier in TYPE_CONTAINER_NETWORK in page 60. [4] Add TYPE_IE_ACCESS_NETWORK_OPERATOR_IDENTIFIER in MIIS_REPORT_TEMPLATE in page 62. @A>  33L    33>cTYPE_IE_ACESS_NETWORK_IDENTIFIER is just a octet string corresponding to SSID of IEEE 802.11. We need additional IE to carry a unique operator identifier of the access network.d2140g2440vChange description of entry 1.2 in Table-6 to include Access Network identifier along with Core Network identifier. The Roaming partners are always w.r.t this particular identifier. wAccepted-Modified 2006/11/16 2006/10/23T6)C^technicalnon-binding(V)V+V0V2V7V<VBVWV[V]V^VgVjVnVrVsVtVuVyVVVVVVVVVVVVVVVVVVVVVVVVVV V VVVVV#V$V%V&V'V,V2VQViVkVlVnVrVtVuVvVwVxVyVVVVVVVVVVVVVVVVtechnicalwaseditorialVwasWWXcmihre-registrationmessageformatshallbeaddedhere1VmihregisterandmihderegisterarenotincludedinthistabVmihregisterandmihderegistermessagesaremissingintablKVmihregisterandmihderegisterprimitivesaremissinginta@Vmihswitchcommanddoesnotwanttheoldlinktobediconnec'Vmih-3glink-sapWmih-3glink-sapisamedia-dependentsapVmih-3gppWmih-linkWmihf1WbWlWmWWWWWWWW)W*W0WHW^WfWhWWWWWWWWWWWWWmihfcanbeusedtoexchangemessagesbymihusersbetweendVmihfcanfacilitatenetworkdetectandselectioninadditionV  member23456789:;<=>?@ABCDEFGHIJKLMNOPQRhi㈃㉃㊃㋃㌃㍃㎃㒃㓃㔃㕃㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃzbhomogeneousWWhorizontalWwWWhorizontalhandoverhandoverassociatedwithalinkswitchbVhow7WPWdWW]WaWdWWWhoweveruW{WlWqWWhoweverthetransportsecurityofthisinformationisoutsiduVhrdzWi@WAWQWWWWWWgWid:WbWzWWWWWWWWWW*W/WWWidentifiedWidentifierGWW WW/W9WMWWWWWidentifiersrWWidentifiesWidentifyFWidsUWVWie8WUWVWW9W:W;W>WJWVWWWieeeuWWrWiesrW8WWietfwWifTWWWWW$WNWcWeWxWWWWWWWWWifbothoptionaltlvsareabsentthenthevaluefieldoftheeVd2 |~vAf 33 A 33  33 33feral Network Information is specified for both 802.11 and UMTS networks, while in case of Operator_2 it is specified only for 802.11 network. For each network supported by an perator there is a list of supported PoAs. For each PoA the PoA Information Elements are specified. Figure 20 shows this information representation and tree hierarchy for different networks. "w be renamed to TYPE_IE_POA_ MAC_ADDRESSd2141g2465 2006/11/15 2006/10/23T6;E YoshihiroFOhbaGMember^Technical, Binding_49`1a6.3.3b'Adopt 21-06-0779-PoA_IP_Address_IE.doc cBTYPE_IE_POA_ ADDRESS should be renamed to TYPE_IE_POA_ MAC_ADDRESSd2141g2465 2006/11/15 2006/10/23T6;E YoshihiroFOhbaGMember^Technical, Binding_49`1a6.3.3b'Adopt 21-06-0779-PoA_IP_Address_IE.doc  j>cNetwork Standards IE is needed not only for TYPE_CONTAINER_NETWORK TLV but also TYPE_CONTAINER_POA TLV. This is because each PoA of the same network type may support a different set of network standards. d2185g2433wAccepted 2006/11/16 2006/10/23?E YoshihiroFOhbaGMember^Technical, Binding_67`48a6.4b/Delete MIH Event Subscription from Section 6.4.cPMIH Event Subscription are categorized as Command in the rest of the document. d2211g2443vFEvent Subsciption is not part of System management but Command ServicewAccepted-Modified 2006/11/16 2006/10/23o TYPE_CONTAINER_POA TLV. _NETWORK_STANDARDS value needs to be specified.d2167g2432 2006/11/15 2006/10/23>E YoshihiroFOhbaGMember^Technical, Binding_61`17a6.3.5.4bBAdd one optional Network Standards IE to TYPE_CONTAINER_POA TLV. 1.55€A1.55: Added "Fig/Table Number" field Deleted XML file output option. 1.54: Added "Technical, Satisfied (was Binding)" to value list Comment Type/Group. 1.53: in Reply Comment layout, reduced display to three replies 1.52: *Changed instruction on saving files to specify .USR instead of .fp5 *Fixed bug that wouldn't allow exporting a ballot with no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create andB Submit Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new C 2002-04-15 Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15!.cmeasuresWWmechanismrWWmechanismspWxWWmedia2W3WaWWWWWWWWW5WbWjWoWtWWWWWWWmedia-dependentWWmediumWmentionsWmeshWmessage(WoW{WWWWWWWWW1WJW`WdWfWgWlWWWWWWmessagepadding/alignmentruleismissingJVmessage-iddWmessagesWWW W W*WKWLWMW]WdWgWqWsWWWWWmessagresdWmethodNWWWmethods8WiWW&WNWPWWWmetricWmetricsWmfgWmhW Wmibs[WmicroWmics7W €Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool. up" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool. xbnotificationfrommihfofthemntonewservingmihfornoti6VnowWWW6WnullFWnumberWWWWgWnumbersWobjectWobservedWobtain7WrWWobtainsWWobtian~WocalWoccurW ^technical7W8W9W:W;W<W=W>W?W@WCWDWEWFWGWJWKWLWNWOWQWRWSWUW\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWzEAjayFRajkumarGMember^Technical, Binding_27`1a5.5bjWhen connected to a 3GPP/3GPP2 network, a Mobile Node can only use L3 transport to conduct MIH signaling. cAWhen connected to a 3GPP/3GPP2 network, a Mobile Node should only use L3 for exchanging MIH Signalling. Rationale: The "should" does not eliminate the possibility of using non-L3 transport, whereas the MIH standard simply does not offer this possibility with 3GPP/3GPP2.d2080g2229ectedwRejected 2006/11/08 2006/10/23EAjayFRajkumarGMember^Technical, Binding_27`1a5.5bjWhen connected to a 3GPP/3GPP2 network, a Mobile Node can only use L3 transport to conduct MIH signaling. cAWhen connected to a 3GPP/3GPP2 network, a Mobile Node should only use L3 for exchanging MIH Signalling. Rationale: The "should" does not eliminate the possibility of using non-L3 transport, whereas the MIH standard simply does not offer this possibility with 3GPP/3GPP2.d2080g2229 . JbAyAdd the following sentence to Section 8.3.4: Each TLV and IE is aligned on an octet boundary and no padding is made. y@A>  33.  33x  33>c*Message padding/alignment rule is missing.d2352g2466 2006/11/16 2006/10/23KE YoshihiroFOhbaGMember^Technical, Binding_161`1a8.3.5b Add them.cAMIH Register and MIH Deregister messages are missing in Table 25.d2358g2450wAccepted 2006/11/16 2006/10/23T25LE YoshihiroFOhbaGMember^Technical, Binding_161`53a8.4bA(The Type field shall be one four octets.(@Az  33    !  33&  '  33zcThe length of the Type field of TLV for carrying MIH protocol messages needs to be the same as the length of the Header Type field of Header TLV.d2361g2451vby comment 2360w Superceded 2006/11/16OhbaGT cxml/rdf8WydWEKentaroFIshizuGMember^ Editorial_3`1a1.2b>We propose to delete the arrow between MIHF and lower layers. cqThere is no description on IS between MIHF and lower layers in draft D02. But, there is an arrow between the two.d2013g2222 2006/11/16 2006/10/231EJunghoonFJeeGMember^ Editorial_101`6a 7.4.5.1.2bSChange "Link_Patameters_change.indication" into "Link_Parameters_Report.indication.cMLink_Parameters_change.indication is not defined in this draft specification.d2277g2218 2006/11/16 2006.10.23EJunghoonFJeeGMember^Technical, Binding_189`1a Annex 1.3bvAmend the Annex 1.3 Handover Procedure from 802.11 to 3GPP2 as suggested in the accompanying contribution 21-06-0793. cDMIH Handover procedures described in the Annex 1 are not consistent.d2391vby comment 2387w Superceded 2006/11/16 2006.10.2332EKenichiFTaniuchiGMember^Technical, Binding_234`65aAnnex E2006/10/23@bfollows2WiWWWWW W WWWWwWWWfontkWfontsWWfor5W<WFWWW^WeWjWqWrWxWWWWWWWWWWWWW W"W.W3W4W@WEWFWMWNW\W^WdWgWlWmWnWqWrWwWWWWWWWWWWWWWWWWWWforeachnetworksupportedbyanoperatorthereisalistofVforprimitivesyntaxpleaserefertoannexgxVforthesameacronymfortwodistinctentitiesincludeindicVformiWformatiWW=Wformats_WWforwarded6WforwardingWfourmWLWHE Yoshihiro FOhbaGMember^ Editorial_156`33a8.3.3.1bFix it.c@TYPE_MIHF_ID should be TYPE_HDR_TLV_MIHF_ID as described in p195d2350g2462 2006/11/16 2006/10/23IE YoshihiroFOhbaGMember^ Editorial_156`53a8.3.3.2bFix it.cFTYPE_SESSION_ID should be TYPE_HDR_TLV_SESSION_ID as described in p195d2351g2463 2006/11/16 2006/10/23JE YoshihiroFOhbaGMember^Technical, Binding_158`9a8.3.4bbaGMember^ Editorial_156`33a8.3.3.1bFix it.c@TYPE_MIHF_ID should be TYPE_HDR_TLV_MIHF_ID as described in p195d2350g2462 2006/11/01 2006/10/23IE YoshihiroFOhbaGMember^ Editorial_156`53a8.3.3.2bFix it.cFTYPE_SESSION_ID should be TYPE_HDR_TLV_SESSION_ID as described in p195d2351g2463 2006/11/01 2006/10/23JE YoshihiroFOhbaGMember^Technical, Binding_158`9a8.3.4brmation.request parameters.`cmight;WXW^Wmih1W2W3W4W5W:W;W<W=W>W?WAW`WlWvWwW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW!W$W'W)W*W,W-W.W/W0W1W3W4W5W6W7W?W@WAWCWDWEWFWKWLWRWSW\W]W^W`WdWfWgWhWjWkWlWoWpWsWtW|WWWWWWWWWWWWWWWWWWWWWWWWWWmihcapabilitydiscoverandmihgetinformationshouldbeusRVDcwhilehWuWWW_WWwhyWWWWCWDWWWWwhyisapreamblestartofframedelimiterneededinthemihVwhyisthisincludedVwhyistypeiepoadhcpaddressneededthatiswhydoesmnnVworkaddressinformationconfirmhasadifferentDVwhymihnetworkaddressinformationindicationhasadiffereCVwhymustamnsupportbothtlvandrdfquerytypeswhynotaVwihtoutdWwillTWtWWW;WZWdWWWWwindowGWwired]Wwireless]WWwith>W?WWWlWoWsW}W~WWWWWWWWWWWWWWW WWW"W$W&W)W0WMWSW[W^WhWuWWWWWWWWWWWWWWWwiththecurrentdraftidon'tseeanydifferentactionfor$VwithinSWcWdWWWWb`‚Jⳃȃ*g‚Q7?f⠃7O‚R⅃⯃Ń㎃‚S≃j‚T,Z⭃㇃㳃‚Ur‚V)W⎃̃Pv‚WFa┃✃/Y‚XS[∃⬃ⰃD㕃‚Y'0?u㰃㷃㹃㻃㼃‚ZY`o⍃⫃⮃"㙃‚aC~⟃:‚bڃ‚c⾃ǃ‚dmIL‚eB\p⁃ƒ‚fKăs‚g@^qy⹃CU‚h▃‚iGtv˃Ѓكe㓃㪃‚j]‚ql⨃mpq‚r( 3Sl‚sTↃ⧃b‚t8‚u␃σ-‚vuą"j ĆH'!a1.1⅃1.2Ↄ⇃∃㦃㧃1.3W㪃1.5⊃⋃⌃㬃12}W2$3()s㮃㯃3-6MW3.0v4+⍃.45.4.2.35.4.3tu☃5.5,♃⚃jkl5.5.3m0`GE YoshihiroFOhbaGMember^Technical, Binding_155`28a8.3.2bRemove the sentence.c splitted into multiple pieces of data, where each piece of data is contained in this Data field in a separate MIH_TP_Data.request." [3] Also, apply changes [1] and [2] for MIH_TP_Data.indication primitive in Section 7.6.5.2.2.9@A>  33C    33>cWhen acknowledged connection-oriented mode is used, the data contained in one MIH_TP_Data.request primitive does not have to be the entire MIH PDU. In fact, the data may be just one octet.d2317g2449 2006/11/14 2006/10/23GE YoshihiroFOhbaGMember^Technical, Binding_155`28a8.3.2bRemove the sentence.csplitted into multiple pieces of data, where each piece of data is contained in this Data field in a separate MIH_TP_Data.request." [3] Also, apply changes [1] and [2] for MIH_TP_Data.indication primitive in Section 7.6.5.2.2.9@2006/10/24baddoneoptionalnetworkstandardsietotypecontainerpoa>VaddprefixmihbeforeeachprimitivenameVaddr3addreferenceintextzVaddruletoreportunrecognizedieidsVVaddsomeexplanatorytexttofigure200VaddstatustoheaderhereVaddthedefinitionofnmstosection3andthedescriptiono!Vaddthefollowingdescriptionintopage68line52insectiolV8;hESubirFDasGMember^ Editorial_46`37a6.3.1bAzThe main goal behind the Information Service is to allow ....... [Note: This should be consitent throughout the document]z@AR 33% ff& 33B RcAUse upper case for "Service" while using "Information Service."d2129g2470iVivekmAccepted 2006/11/16 2006/10/23iESubirFDasGMember^Technical, Binding_52`11a6.3.5bAChange the text in Section 6.3.5 as follows: The Information Elements may be represented in Type-length-Value form format as follows and the corresponding fields may be stored in network byte order.@Af 33p  v } 33 fork byte order.@Af 33p  v } 33 f'  33zfbchangethenameofthesection5.3.2inadeploymentexample4Vchangethenamesofprimitivesandmessageswiththeonesde VchangethenointomihactionidentifierandmihactionidenVchangetheprimitivemihgetinformationresponseintomihg VchangethesecondoccurranceoftherowqueryresourcelisttoVchangethetextasfollowsVV Vchangethetextinsection6.3.5asfollowsiVchangethetypefieldinthetableasfollowsVVchangetitletonetwork-initiatedhandoverfrom802.21to3ggVchangetoFVGVchangetol3mmpV+bchangetomihgetstatus@clearlydeterminethegroupingsforevents/links/remoteeven@`config@container@W?W@WAWDWEWHWIWJWKWLWMWNWOWPWQWTWUW^W`WaWbWcWdWeWfWgWiWjWlWmWnWoWpWqWrWtWuWvWwWxWyW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWW W!W"W$W%W&W'W)W*W+WzEBenjaminFKohGMember^ Editorial_14`64a5.1.3bReplace with: is defined asc is defiend asd2042g4680 2006/11/16 2006/10/20EBenjaminFKohGMember^ Editorial_16`4a5.1.8b#Replace with: be horizontal (intra-cbe horizental (intra-d2045g4681 2006/11/16 2006/10/20EBenjaminFKohGMember^Technical, Non-binding_17`29a5.3.1b/Edit the text based on result of clarification.cIt is unclear how this model can apply to peer to peer connections such as the 802.11 "adhoc" mode or mesh networks. Should one peer assume the role of the network PoS?d2052g4682vhe scope of 802.21 covers access networks and handovers across them. Ad hoc networks and mesh are outsifde the scpe of 802.21. wRejected 2006/10/31 2006/10/20EBenjaminFKohGMember^ Editorial_16`4a5.1.8b#Replace with: be horizontal (intra-cbe horizental (intra-d2045g4681 2006/10/31 2006/10/20EBenjaminFKohU btheEWGWJWLWMWNWTWUWVWWWYWZW[W\W^W_W`WaWbWcWdWeWfWgWhWiWjWlWmWnWoWpWqWrWvWwWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWthecurrenttextreferstoapossibilitythatwillbeeitherVtextreferstoapossibilitythatwillbeeitherVVVbwassuccessfullyretrievedornotEVway8WqWWWwaysWweWW^W`WxWWWWWweproposethathesizeofthemihmessagebelimitedto1m`Vweproposetheintroductionofanewsetofprimitivesthat^VweproposetoaddadetaileddescriptionabouthowtogetthVweproposetochangethesectionnamesasfollowsVweproposetodeletethearrowbetweenmihfandlowerlayersVweproposetomodifyeitherthefigure17orthefigure18tVwereviewiftheabovearecoveredadequatelyinthelatersxVwesuggestthefollowingamendmentsVwellWWwhat'W,WTWWWWWWNWwhenQWWWW'W+WEWTW^WlWWWWWwhenconnectedtoa3gpp/3gpp2networkamobilenodecanonlVwhenconnectedtoa802networkamobilenodemaydirectlyulViginatesataremotenetworkelementVbtoamismatchinthesupportedEVtoaccepttheproposedprimitivesformihre-registrationis.Vtoaccepttheproposedremedy4inthedocument21-06-0xxx-01Vtoaddsessionidintothemihframefixedheader*VQDEVivekFGuptaGMember^Technical, Binding_56`1a 6.3.5.2.6b Please refer to contribution: 21-06-0731-01-0000-LB-issues-5-6 for details. This was mstly missed as part of editorial update in version D2.0cAs part of TYPE_IE_QOS, add the following parameters as well: Throughput Link Packet Error Rate Minimum/Maximum Packet Transfer Delay, Average Packet Transfer Delay Jitter d2173g2226vkAdd these IEs as per the definitions in draft in section 7 under primitives (Table 21, page 108 draft D2.0)wAccepted-Modified 2006/11/16 2006-10-23art of TYPE_IE_QOS, add the following parameters as well: Throughput Link Packet Error Rate Minimum/Maximum Packet Transfer Delay, Average Packet Transfer Delay Jitter d2173g2226vkAdd these IEs as per the definitions in draft in section 7 under primitives (Table 21, page 108 draft D2.0)wAccepted-Modified 2006/11/15 2006-10-23b^Technical, Binding_158`9a8.3.4bg4965 2006/10/24HctoallowalltypesofnetworkinitiatedhandoversitisneceVvkenichi taniuchitaniuchi kenichi taniuchitaniuchiWYkenichi taniuchitaniuchimpkenichi taniuchitaniuchimVkenichi taniuchitaniuchiXpkenichi taniuchikimreunahkimWkimSeunahkimkim@eunahkimykimeunahkimkim}Geunah kimeunah !kimkim%eunah kimkim&eunah kim*kimeunah kim*kimeunahkim*kimeunahkimjeon2hongseokjeon^citisnotclearwhatmihnmssapfunctionisonlydefinitionpVitisnotclearwherethemihfunctionmaybelocatedinthe|Vnotclearwherethemihfunctionmaybelocatedinthe|V|VitisstatedthatNVitisunclearhowthismodelcanapplytopeertopeerconneVitneedstobemadeclearthatfigure25isnotarepresentaVitshouldbeclearlyshowwhichtransportsapshallbeusedkVit's(WitemWWWitemsWWitemslisteddonotagreewithrowsforexampleinfoqueryresVitswWWWWWWGWVW\WdWgWitselfWjitterWWjust3W9WFWkeyWkindBWNWgWkinda1WknowcWdWWdWgWl2WWWW WoWl3WWWWW WoWl3mpWl3mpmissinganmVl4WlabelingWlackWlacksRWSWlastW6bitIWTW\W^WfWgWqW}W~WWWWWWWWWWWWWWitmaynotbeappropriatetoincludetransportinthesetofVitshouldbeqosnotqosV+P 2006/10/23QE YoshihiroFOhbaGMember^Technical, Non-binding_192aA1.4.1, A1.4.2, A4b>Having texual description on those Figures is more preferable.cAThere is no texual description on Figures 33, 34, 36, 37 and 38.d2393g2461vby comment 2387w Superceded 2006/11/16 2006/10/23F33RE YoshihiroFOhbaGMember^Technical, Binding_193`1aAnnex A2by[1] Add R2, R4 and R5 to MIH Capability Discover and MIH Get Information. [2] Add R1 to MIH Network Address Information.c- MIH Capability Discover and MIH Get Information should be usable for all reference points. - MIH Network Address Information should be usable for R1 as well.d2398g2460wAccepted 2006/11/16 2006/10/23T31SEUlises^Technical, Binding_139`61a7.5bnRephrase to: "Primitives are a conceptual representation of functions that are called across protocol layers."cultiple IP addresses are carried when more than one IP configuration me, NbA[1] Define a distinct TLV for each of Serving FA Address, Serving Access, Router Address and DHCP Server Address in the Table in Section 8.5.3.23. [2] Change the text to: "Serving FA Address, Serving Access Router Address, DHCP Server Address parameter are contained depending on what kind of IP address configuration methods is set. E.g., if IP Address configuration method is IPv4 dynamic configuration (DHCPv4), then DHCP Server Address is included in the message." cAIt is stated that: "Serving FA Address / Serving Access Router Address/ DHCP Server Address parameter is chosen depending on what kind of IP address configuration methods is set. E.g., if IP Address configuration method is IPv4 dynamic configuration (DHCPv4), then IP address included in "Serving FA Address / Serving Access Router Address/ DHCP Server Address" is DHCP Server address (IPv4)." But missing details on how multiple IP addresses are carried when more than one IP configuration me address.pb8.4.1.20WW8.4.1.30%W8.4.1.4nW8.5oW8.5.1.2W8.5.1.3MW8.5.1.6MW8.5.2W8.5.3.23NW802WlW802.11FWWWWWW802.11/802.16W802.16mWnWqWWWW802.1ag]W802.21gWuWWWW!W]WrWWW802.21-isW9#WW9-31Wa4W5W7W?WCWEWFWHWMWUWWW_WcWlWnWsWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW+W4W@WEWFWNWSWTWWW[W^W_WgWlWmWqWrWWWWWWWWWWWWWWWWWWWWWWWWWacouplethoughtsVafewexamplesofthekindofinteractionsthatmayexistbeV;baddthefollowingtablesVaddthemKVaddthemassystemmanagementcategoryprimitives@VaddthesetlvqueryexamplesinannexVaddthisprimitivetotable15onpage71VaddthreeperiodsieindicatingthemissingpiecesbetweenVaddtypeiepoaipconfigmethodstoreportingtemplatetlv8VaddedxWaddingWadditionjWadditionalHWWWwWadditionallyqWrWwWadditonalWaddressQWcWWWW:W;WCWDWNWPWRWWWWWional$WadequatelyxWadopt;W=Wadopt21-06-0779-poaipaddressiedoc;Vadopttheformatproposedin21-06-0778-00-0000-nstandards=Vafter<WxWcWmWoWqWWWagainWagainst6WagreementsWaidingwWair~WWalgorithmsWalignedJWalive+WallJWRWSWTWoW~WWWUWdWgWqWWWW1bisdefinedasVisquerytypelist4VVissue^Wissued^Wissues+Wit@WAWIWMWoWWWWWWWWWW WWW,W5WAWBWHW gcA[When the information originates at a lower layer of the protocol stack within the MN, the MIHF on the MN obtains the information locally through the primitives of the SAPs that define the interface of the MIHF with the lower layers. Rationale: The current text does not cover inter-layer exchanges within network nodes that are not Mobile Nodes. [d2016g2238vAQWhen the information originates at lower layer of the protocol stack within a MN or network entity, the MIHF on that entity obtains it locally through the service primitives of the SAPs that define the interface of the MIHF with the lower layers. MN: Communication Node that may change its Point of attachment from one link to anotherQwAccepted-Modified 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Non-binding_4`15a1.5b of the SAPs that define the interface of the MIHF with the lower layers.cZcSentence states that a standardized format is used, yet two are listed as possible candidates: XML and TVL. If this is a standard one should be chosen.d2067g2251iYoshihiro OhbajA+The text in Section 5.4.3 is about information representation format used by information service while Section 5.7 is about the encapsulation format used by the MIH protocol. In fact XML-represented IEs are encapsulated in TLVs by the MIH protoocl. So there is no inconsistency in the current text.+mRejected 2006/11/16EGolmieFNadaGMember^ Editorial_25`29a5.5bKRewrite sentence to reflect the fact that only one protocol stack is shown.czText states different protocol stacks are shown in Figure 4. This is wrong. Only one protocol stack is shown in Figure 4d2069g2252 2006/11/16EGolmieFNadaGMember^ Editorial_26`57a5.5bNMove starting at this sentence to until the end of this section into an annex.ууууууууу6<a8.5.13-6MV8.5.1.1g8.5.1.28.5.1.31f8.5.1.4a8.5.3.16q8.5.3.23NOPa-4Wa12WiWa1.2Wa1.3g Wa1.4.1QWa1.4.1a1.4.2a4QVa1.4.2QWa26; WRWa39zWa4 WWWQWWBTEUlises^ Editorial_95`4a 7.4.1.3.3bRephrase to: "The MIH Function generates this message when it needs to deregister a previous MIH registration to a particular destination MIHF."cJThe wording is unclear, difficult-to-follow and, possibly, has redundancy.d2268g2291 2006/11/16UEUlisesFOlvera^Technical, Binding_90`56a7.3.20.2bRemove all rows from table except first two, that is, leave LinkParameterList field and its corresponding Type, Valid Range and Description and remove the rest.cVThe Name fields of RSSI, SNR, C/I, BER and Data Rate are not used. They are redundant.d2258g2292v-That's exactly what we did....in Comment 2256w Superceded 2006/11/16JThe wording is unclear, difficult-to-follow and, possibly, has redundancy.d2268g2291 2006/10/3133  33>d313g2290 2006/10/26TEUlises^ Editorial_95`4a 7.4.1.3.3OhbaGMember^Technical, Binding_193g4973 2006/10/24.EVivekFGuptaGMember^Technical, Binding_50`1bA " Figure 20 shows the layout of different Information Elements and neighbor map of different networks in a geograpical area. Multiple operators can be providing support for a particular network. Thus support for 802.11 network is provided by both Operator_1 and Operator_2. A single operator may provide support for multiple networks. Thus Operator_1 provides support for 802.11 and UMTS networks while Operator_3 provides support for 802.16 and UMTS networks respectively. The General Networketworks in a geograpical area. Multiple operators can be providing support for a particular network. Thus support for 802.11 network is provided by both Operator_1 and Operator_2. A single operator may provide support for multiple networks. Thus Operator_1 provides support for 802.11 and UMTS networks while Operator_3 provides support for 802.16 and UMTS networks respectively. The General Network33RE YoshihiroFOhbaGMemberbcontainer9W:W>WcontainingWWqWcontainsGWUW_WEWcontent1WBWcontextWcontribution|WWWWWWWWcontro/managementsWcontrolkWmWcopyWWcopyencodinginformationfromsection8.4.1.20inthedescrVVcorerWW|WcorrectWcorrecttheinconsistencyVcorresponded&WcorrespondingiW:WUWWWcorrespondsRWSWcostWcoupleWcoverxWcoveredxWcreateWcreateanewannexandaddsection4of21-06-0460-04-0000-bVcriteriasWurrent3W<WCW"W7WZW\WcurrentlinkidentiferOWcurrentlysWdWjWdmihnetsapthisrepresnetstheabstractmedia-independentjVdashed>W?WdataNWWWWWWEWFWjWkWqWWWdataonlywhenstatus0EVdatabase7WdecidelWWWW]bmics7Wmih2W3W4W5W6W:W;W=W>W?WAW`WeWlWqWvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW!W$W)W*W+W.W/W0W4W5W?W@WCWDWEWFWRWTWYW\W`WaWdWfWgWhWjWlWmWoWpWqWrWsWWWWWWWWWWWWWWWWWWmihhandoverinitiate4Vmihhandoverprepare5Vmihlinkdetected3Vmihlinkdown1Vmihlinkeventrollback5Vmihlinkgoingdown2Vmihlinkhandovercomplete8Vmihlinkhandoverimminent7Vmihlinkparametersreport4Vmihlinksapisactuallymedia-independentwhichisgoingtoVfcdependingNWderegisterW@WKWderegistrationfWderivedWdescribe!Wdescribed_WfWmWWWWWW"W4W8WHWIWqWsWdescribesWWdescribinggWuWdescription@W[WeWfWjWuWwW{WWWWWWWWWWW W!W$W,WEWQW}WWWWWdescriptionofstatusofmihgetinformationconfirmshouldEV6Qb1addcurrentlinkidentiferandtargetpoaidentifierOV1addit~V1addr2r4andr5tomihcapabilitydiscoverandmihgetinRV1addthefollowingnewieentrytoaccessnetworkspecific9V1basedonthepreviouspointiediscoveringthenumberandgV1changemihprotocolpdutodataFV1changeremotedirectionfieldclientnetworknetworkclien7V1changethefirstandthesecondmihgetstatusprimitivesV1changethetitleandthetabletitlemappingmihprimitive V1changetypeiepoaaddressintable6andfigure20totyp:VOcareincludedinannexcVareaeWWarriveGWarrow>W?WWWarticulatedWasaWeWmWpWqWWWWWWWWWWWWWWWWWWW WWWWW W$W'W?WEWHWIWLWRWXWYW\W]W^WjWtWWWWWWWWWWWWWWWaspartoftypeieqosaddthefollowingparametersaswellV*c33QW34QW36QWW37QWW38QWW3glinkW3gppW3gpp/3gpp2|WW3gpp2W4HW}WWWWW<WgWvWWW4n-layervV46W47W48W49W5BWWvW5n-uservV:zVEUlises^ Editorial_52`17a6.3.5b?@ABCDEFGHIJKLMNOPQRzhuang㖃dasefghijklmnopqrstuvwxyzfamolari{feder|}~ ⁃guo㒃㓃㔃gupta㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃhanhepworthhong`abcdhongcheng㖃ishizujeejeonkim koh kuroda!"(bpositionWWWWWWpossibilityWpossibleYWWpptpWWWpre-authenticationqWpreambleWpreconfiguredlWpreferableQWpreferedpoalistWprefixWprepareWWpreparingpresentQWWWWprevious6WTWgWWprimitive4W5WTWXWYWxWWWWWWWW WW'W-WFW^WuWvWWWWprimitives4WjWlWxWWWWWWW W W WWW!W.W@WSW^WmWWWWWWWWprimitives/messagesWprinciples"WpriorsW{tmabThe document 21-06-788-00-0000-MIH_Registration defines the registration time and proposes how this field can be used by the MIH enabled nodes to maintain registration status.cThe draft does not specified how the Validity Period parameter, representing the time the registration is valid, should be used. d2381g2304w Withdrawn 2006/11/16 d2381g2304wDeferred 2006/11/16ion defines the registration time and proposes how this field can be used by the MIH enabled nodes to maintain registration status.cThe draft does not specified how the Validity Period parameter, representing the time the registration is valid, should be used. d2381g2304wDeferred 2006/11/16 references can be found in section 7.4.7.1.3 "Effect on Receipt g2301 2006/10/26_EUlises^Technical, Binding_88`26a7.3.17.1bYRemove this section as the same effect can be achieved using a Link_Up.Indication messageK{_EUlises^Technical, Binding_88`26a7.3.17.1bYRemove this section as the same effect can be achieved using a Link_Up.Indication messageer. However although there are enough MIH primitives that can do this, there does not exist any 802.21 link layer counter part or "blue print" as it is the case with other commands, events and information services. Furthermore the current specification makes references to link commands that should be used by the MIHF when it receives MIH commands affectinBg link layer connection. Note that these link layer commands are not defined in the specification, however primitives exhibiting similar behavior may be found in existing link layer technologies. An example of these references can be found in section 7.4.7.1.3 "Effect on Receipt d2278g2301 2006/11/14_EUlises^Technical, Binding_88`26a7.3.17.1bYRemove this section as the same effect can be achieved using a Link_Up.Indication messagey^~cisdefiendasVisthereferencetoieee802.15undermicrocellsisincorreVis/areYWissueWuWc1unclearabouthowthe4fieldsareencodedintable9oneHV1-127W1.2WW1.4W1.5WW100mW11WW12=W}WWW\WW13CW\WW15>WW@W16XWfW17XWYWZWW170%W171nW172nW18?WW19kWuW1stEW21WHWJW_WzWWWW-W4W\WgWkWlWqWrWvW~WWWWexb_V2n-entityvV2whatarethevalidentriesfordifferentrevisionsJV200W21-06-0765-00-000uW21-06-0783-00-0000-cWW21-06-xxxx-00-0000-eW22W23^WW243\W244\W25WKW253EW26oWWWWW2nd@WAWEW31W_WW-WgWqWrWvW3anexhaustivelistofinformationresourcesandproperties_V3n-eventvV31nWWW329WDWgWrW32-1WbbehorizontalintraVbeaconWWbeenmWbeforeCWWWmWbeginWbehavior^WbehindhWbeingsWWbelowWoWWW@WAWWbetweenWWW W+WmWbetwenWbi-directionWbimapQWbitRWSWWWWWWWWWWWbit5&WbitmapWWWWWWbits WVWblockWblueprint^WbothZWeWboundarydWJWbriefWbroadcasWbroadcastWqWbroadcastingWWbroadcastingmihcapabitydiscoverresponsemessagemayinclVbroader_WbsmWbulletWbutWlWWby4W5WlWyWWWWWWWW WaWbWmWoWqWrWwWWbyteiWcmWcalledjWSWcancWlWxWWW W$W]W^W_WaWdWoWwWcandidatesWWWY> dcAAn MIH node can request its peer to acknowledge the recipt of a message by setting the ACK-Req field in the MIH frame to 1. There are two ways in which the peer can send acknowledgement message: i. The peer send a standalon acknowledgement message only wihtout any service. In this case the acknowledging party set the ACK-Rsp bit of the MIH message to 1 and copies Message-ID and Transaction-ID from the received packet. ii. The acknowledging party can piggy-back the acknowledgement Bmessage within an MIH message that it is being sent to its peer. The second acknowledgement scheme i.e. piggy-backing does not work efficeiently and the following exsmaple shows the problem. Assuming an MIH Node x send two consecutive messages to MIH Node Y and sets the Ack-Req bits of both messagres to 1. If Node Y has a response message to send, it can piggi-bakc the ackowledgment by setting the Ack-Rsp bit to 1. However, Node X will not know which message (i.e., the fierst or second th89g RfcBty_Discover.request o 7.4.2.2 - MIH_Capability_Discover.confirm o 7.4.3.1 - MIH_Event_Subscribe.request o 7.4.3.2 - MIH_Event_Subscribe.confirm o 7.4.4.1 - MIH_Event_Unsubscribe.request o 7.4.4.2 - MIH_Event_Unsubscribe.confirm d2377g2309wAccepted 2006/11/16gEUlises^Technical, Binding_173`39a8.5.1.1bA1. Based on the previous point (i.e. discovering the number and type of links that a node supports), this document proposes modifications as explained in document 21-06-0792-00-0000-LinkTypeDiscovery 2. The document 21-06-0792-00-0000-LinkTypeDiscovery proposes modifications to allow an MIH node to list the Events it supports while at the same time specifying the type of links that support the Events (i.e. certain links support common Events while others support specific Events). 3. The to send, it can piggi-bakc the ackowledgment by setting the Ack-Rsp bit to 1. However, Node X will not know which message (i.e., the fierst or second thtWcEUlises^Technical, Binding_84`14a7.3.11.2b^Replace with "If Link_Going_Down is NOT received after the specified interval then actions..."cthe sentence "if Link_Down is NOT received within the specified time interval then actions..." should be replaced by "if Link_Going_Down is NOT received after the specified time interval then actions..."d2250g2306v@Curent text seems correct. EDitorial, NOT should not be in caps.wRejected 2006/11/16MarkeddEUlises^Technical, Binding_155`10a8.3.2bThe document 21-06-0789-00-0000-AckOperation describes how MIH can piggy-back an acknowledgement for serveral messages all at once.c...."d2096g2305 2006/10/31Ulises^Technical, Binding_32`62a5.6.1.1bHReplace by "this SAP defines the gerneric Media Dependent Link Layer..."c"This SAP defines the generic media independent link layer..." should be replaced by "This SAP defines the generic media dependent link layer...."d2096g2305 2006/10/31yb21-06-0738-01-0000-8]W21-06-0739-02-0000-sW21-06-0778-01-0000-n=W21-06-0779-poa;W21-06-0780-00-0000-mwW21-06-0781-00-0000-mpW21-06-0783-00-0000-cWW21-06-0784-00-0000W21-06-0785-00-0000W21-06-0786-00-0000!W21-06-0787-00-0000"W21-06-0789-00-0000-adW21-06-0792-00-0000-lgW21-06-0793W21-06-0793-00-0000uW21-06-0797-00-0000-m,W-W21-06-0808-00-0000-uW21-06-0xxx-00-000}W21-06-0xxx-00-0000-m)W+W.W0W1WhW21-06-0xxx-00-0000-r|W21-06-788-00-0000-miaW21-06-xxxx-00-0000-eWW24,W243\W244\W25WW W25-mihf W W253FW26oWrWzWWWW2nd@WAW3oWyW|WWWWWW WWWWW!W.W4W9W:WFWMWgWmWnWrWWW3framelossratebeforeretransmissionV30oWC hcreferencesnotorderedproperly$VreferredWreferringnWrefers<WWWWWreflectWreflectingfWrefuseWregardinguWregisterW-W@WKWWregisteredWregistrant4Wregistrantwouldbeanmihusernotmihfunction4VregistrationW,W-W/WaWfWRLbsap2W3W=WWWWWWWWWWWWW W W WW!W5WYWbWjWmWnWoWpWWWWsapclarification!Wsaps2W5WmWtWWWsatifiedWsatisfy^Wsay[WWscanWWWWscancommandWscannedWscanresponsesetWscenariosWschema\W^W_WWWWWW:WschemeWWscopeuWWWlWrWsdosWsduWsearchWsecondWW[Wsection1W3WCWeWfWiWlWoWvWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!W"W,W3W4W5W8W9W:W?WFWJWMWNWWW[W_WnWoWyWWWWWWW=XbmihcommandidVmihconfigure2Vmihderegisterrequest/VmiheventidVmihgetstatus0Vmihhandovercommit6Vmihhandovercommitprimitives/messagesareusedtocommunicVmihhandovercomplete7Vmihhandoverinitiate4Vmihhandoverprepare5Vmihlinkdetected3Vmihlinkdown1Vmihlinkeventrollback5Vmihlinkgoingdown2Vmihlinkhandovercomplete8Vmihlinkhandoverimminent7Vmihlinkparametersreport4Vmihlinksapisactuallymedia-independentwhichisgoingtoVGqhctimeoutWGWtimer WtimersWWtimestampWtitle1WgWW"WtitlenotclearofwhichtypeofhandovertheprocedureisdgVtitlesWtkipWtlv'W8WDW[WmWoWqWrWWW>WHWIWLW\WeWfWWWWWWWtlv-basedW<W>W?W@WAWCWEWHWJWRWSWTWUWVWWW]W`WaWbWcWeWfWiWlWnWrWwWxWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWW W!W#W$W&W'W)W*W-W0W9W:W;W=WFWGWLWMWVWXWZW[W\W]W^W`WdWeW$pcthedraftdoesnotspecifiedhowthevalidityperiodparametaVthedraftstatesthereceivingmihfinstanceshallissueeitVtheencodingusesabitmapbutthedefinitionofeachbitisVVVthefigurecaptioncontainstextindicatingoption1butnoVthefollowingamendmentsshouldbemadetotheprimitive-Vthehandoverflowdiagramsinannexa1useinconsistentreprVtheinclusionoftransportinthesetofmihusersisnotobVtheintendedmeaningofieee802.21supportsmediaindependeVthelengthofthetypefieldoftlvforcarryingmihprotocoLVge gcANote: this is for System Management Service category and the MIH frame of this message has the MIH Service ID set to 1. 1.Does not allow to an MIH node to discover the number and types of links that is supported by its MIH peer. It is useful to know the number and type of links that an MIH node supports e.g. it allows another node to send MIH messages that can be specific for certain link types only and others that can be common to all links. 2.The SupportedEventList parameter in the mesBsage lists all the Events that an MIH node supports. However, it does not differentiate what kind of Events are specific or common to certain link types. 3.The SupportedCommandList parameter in the message lists all the Commands that an MIH node supports. However, it does not differentiate what kind of Commands are specific or common to certain link types. 4. This function allows the discovery of service types (i.e. Event, Command, and Information) that a node supports but only for a cevsubnetPWsubsciption?Wsubscription$WsubsectionslWsubsequentwWsubstantialWsuccess%WsuchuWWwWWWWsufficientuWsuggestedlWmW_WficientuWsuggestedlWmW_W_Wechanisms including primitives. Otherwise delete the section. d2098g5003wDeferred 2006/11/14dependent. d2099g5002iVivekkMIH_NET_SAP uses (or maps to) MIH_LINK_SAP for all L2 interactions with respective media. For L3 this SAP may define other primitives...mAccepted-Modified 2006/11/01pERonny^Technical, Binding_33`60a5.6.2b[Provide more text and mechanisms or delete MIH_NMS_SAP related parts throughout the draft. cIt is not clear what MIH_NMS_SAP function is. Only definition is stated in the specification. Provide more text and mechanisms including primitives. Otherwise delete the section. d2098g5003wDeferred 2006/11/01e used by MIHF. {_‚c‚#‚_?vbwithinW^WqWrWWWWwithout~WXWwlanFWWWwman2Wwords WworklWWwoulddWWWWWwouldprovideadditonalinformationseparatelyVwrittenoWWxWxmlWW8WzeroGWWc0WWW0x00000001rW0x000000ffrW0x10000004DW1,W1WEWHWJW_WaWzWWWWW-W\WdWgWlWqWvW~WWWWW1and2donotbelongtothistablethesearetlvsnotieszV1annexcshouldbeannexb_VDbspecifiesEWmWspecifieswhethertheinformationEV`m  gcCrtain link type. Thus, if node supports two or more link types, an MIH peer would have to send two or more messages to discover the capabilities for each link. Ts. d2373g2310v To be socialized and resubmittedwRejected 2006/11/16orted by its MIH peer. It is useful to know the number and type of links that an MIH node supports e.g. it allows another node to send MIH messages that can be specific for certain link types only and others that can be common to all links. 2.The SupportedEventList parameter in the mes proposes modifications to allow an MIH node to list the Commands it supports while at the same time specifying the type of links that support the Commands (i.e. certain links support common Commands while others support specific Commands) 4.The document 21-06-0792-00-0000-LinkTypeDiscovery proposes modifications to allow an MIH node discover all the services that its peer support for all link types. Thus only one message will be necessary to >]cdefinesbWdefiningWdefinitelyWdefinition(WDWRWSWTW^WyWWWWWWWWWW!WpWWWWWWWWWdefinitionformessagenotneccessaryit'sacommonterm(VdefinitionofcategoriesisnotneededhereVdefinition/detailsWdefinitions)WsWWWWvWWWWWWdefinitionsofcommands567and8arerelevanttonetworkseVdefinitionsortermsnotusedinthemainspecificationneedvVdefinitonWdelayWWWWWdelaysWdeletenWpWdeleted%WdelimiterWdeliveredWWdeliversWdeliveryWdependtWdependenceWdependent2WWWW5WbWjWoWtWWWit can piggi-bakc the ackowledgment by setting the Ack-Rsp bit to 1. However, Node X will not know which message (i.e., the fierst or second thX` *gbBdocument 21-06-0792-00-0000-LinkTypeDiscovery. proposes modifications to allow an MIH node to list the Commands it supports while at the same time specifying the type of links that support the Commands (i.e. certain links support common Commands while others support specific Commands) 4.The document 21-06-0792-00-0000-LinkTypeDiscovery proposes modifications to allow an MIH node discover all the services that its peer support for all link types. Thus only one message will be necessary to C#discover all link-specific service core link types, an MIH peer would have to send two or more messages to discover the capabilities for each link. Ts. d2373g2310wDeferred 2006/11/16s support common Commands while others support specific Commands) 4.The document 21-06-0792-00-0000-LinkTypeDiscovery proposes modifications to allow an MIH node discover all the services that its peer support for all link types. Thus only one message will be necessary to H_Ã&pbwHIÃ&߃*JÃ&Ã'Ã' :mKLÃ'0Ã'`cdpÃ'p\Ã'Ã(%Ã( nÃ(@ogÃ(PÃ(`1MafÃ(pÃ) qÃ)@NOPÃ)`Ã)Ã)g Ã* Ã*0QÃ*@6; 2RiÃ*`9zÃ*pÃ* Ã*Ã*Ã1Ã4PƉ"1#pNj('` $+269=Ucg|}⌃❃➃ⴃⵃⶃ!124;@KMR]`fioty㏃㜃㢃㲃㴃㵃㿃ƒÃс0@:PELQj⒃׃8T`wxpwcacknowledgedW&WFWacknowledgementdWacknowledgingdWackowledgmentdWacquiringWacronymWacronyms+WyWacrossWSWWWactionW#W$W'WactionscWactsWWactualDWWactuallyWaddW2W;WiWWWWWaddasectionfortheexamplehandoverscenariosbetween8022ViVaddexplanatorytextforfigure-20VaddtlvdescriptionforcurrentlinkidentifieandnewlinkidVadded$W1WWaddingWadditionWWWadditionalfWpW$W&W9WadditionallyGWWadditionallyifretransmittedpacketsweretoarriveoutsideGVaddresscWdWjWW&W7W:W;WCWDWNWPWRWWWWaddressesNW_WWadhocWadjectiveWaes-ccmpWaffecting^Wccand'W1W3W7W:W;WEWHWWWXW\W^W_WaWbWeWfWiWlWnWsWtWwWyWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWW W!W*W,W-W2W4W7W@WGWKWOWQWRWTWUWZW\W]W^W`WdWeWgWiWoWpWqWuWxWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWanibsch-aaahiphmippdsnyVannex_WxWWWWWWWannex2Wanother&WgWWWW->chavefWiWpW{WWWFWgWWWWWWWWWWWWhavingHW&WhdrHWIWheWheaderrWWLWfWheaderspecificrWheadingvWWhelp;WWhelpfulwWWhence]WWhere1WuWWWWWWWWWWW1WvW|WWheterogeneous{WWheterogenousWhigherXWWWWhipyWhisWhlsi+hmipyWhomeWWhomogenousWhorizentalWhorizontalWhorizontalhandoversthisinvolvesmnsmovingbetweenaccessVhow1W7WEWHW`WbWcWdWWWWWW WNWXW]WaWeWWWWWWWWisusedVhoweveeWhoweveruWyW{WWWWW\W^WdWgWWhttpsWi@WAW#W$W&W'WdWfWgWcpgCWphrasingWphysical]Wpicture}WWpiggi-bakcdWpiggy-backdWpiggy-backingdWplaceBWCWW,WWWplacedWplacementWplacesyWplanejWpleaseWWWpmd+poa8WsW~WWWWW&W:W;W>W[WWWWWWWWWWWpoashouldbepoainline62aswellVpoas'WWWWpoas/mnsWpoas/mnsmaybeabletohandlemiisqueryresponseofalimiVpoint1WWWpoint-to-multipointWpoints WRWWWpoliciesWpolicyWWpopulationWportWportionWpos7WWW[WWWpossibilityWpossible_WWWZWzWpossiblyTWpotentialWWpower'Wpre-authentication;WpreambleWpredictWpreferedpoalistWehESoohongFParkGMember^Technical, Binding_154`13a8.3bjThe proposed MIH protocol states are described in the document: 21-06-0xxx-00-0000-MIH_Protocol_States.docportedCommandList parameter in the message lists all the Commands that an MIH node supports. However, it does not differentiate what kind of Commands are specific or common to certain link types. 4. This function allows the discovery of service types (i.e. Event, Command, and Information) that a node supports but only for a ceCrtain link type. Thus, if node supports two or more link types, an MIH peer would have to send two or more messages to discover the capabilities for each link. Ts. d2373g2310 2006/11/15hESoohongFParkGMember^Technical, Binding_154`13a8.3bjThe proposed MIH protocol states are described in the document: 21-06-0xxx-00-0000-MIH_Protocol_States.dociscover all the services that its peer support for all link types. Thus only one message will be necessary to cacolumnheadingofremotedirectionisincludedinthetablVaguidanceonhowtocreateanextendedschemawouldbeusefVasessionidisaeventsubscriptionisredundantsincethisWVathedefinitionforjitterisnon-standardinthedefinitioV comment applies to the following sections: o 8.5.1.4 - MIH_Registration Response (also 7.4.1.2) o 8.5.1.5 - MIH_DeRegistration Request (also 7.4.1.3) o 8.5.1.6 - MIH_DeRegistration Response (also 7.4.1.4) o 7.4.2.1 - MIH_CapabiliBty_Discover.request o 7.4.2.2 - MIH_Capability_Discover.confirm o 7.4.3.1 - MIH_Event_Subscribe.request o 7.4.3.2 - MIH_Event_Subscribe.confirm o 7.4.4.1 - MIH_Event_Unsubscribe.request o 7.4.4.2 - MIH_Event_Unsubscribe.confirm IbremovethesourceidentifierparametersinceitisalreadyinfVremovethetextoption1fromthefigurecaptionVremovethissectionasthesameeffectcanbeachievedusing_VremovethissentenceVVremoved WWWrenamevWW:WWWrenameheadingtomihlinksapprimitivesVrenamesection8.4.1.12tocurrentlinkidentifieandaddanotVrenamethecommandstoVrenamethesectionasmihprotocoloperationvVrenamed"Wrenumber5Wreorg2WcframesWsWWframework[W`Wfrom>W?WCWlWWWWWWWWWW W"W-W^WdWfWjWnWWWWWWWWWWfrowardedfulfillmentWfullyWfunction1W4W5W>W?W`WlWWWWWWWWWWWW3W_WgWpW|WWWWWWfunctiondiscoveryatl2isoptionallyintegratedwithcapabVfunctionalitynWWfunctionsSW]WWfurtherWWWfurthermore^WfutureeWgxWWWWWNWSWgWWWWWWWgeneal&WgeneralW,WSWWgeneralizeWgenerallyWgenerate]WgeneratedbWWWgenericvWWWWWbW|WWgeographicalWgetYWW WEWRWWW^ctlvsiWrWzWeWto'W0W1W3W6W7W9W<W>W?W@WAWCWEWHWJWRWSWTWUWVWWW]W`WaWbWcWeWfWiWlWnWrWwWxWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWW W!W#W$W&W'W)W*W-W0W9W:W;W=WFWGWLWMWVWXWZW[W\W]W^W`WdWeWfWgWhWjWlWmWnWqWtWuWwWxW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWcBcofthisinformationareoutsidethescopeVofferWLGcoam]Woampdus]Wobtain~WWobtainsWWoccurWoccursWoctectsmWoctetEWHWW9WFWoctetsW<Wof'W1W3W9WBWCWDWHWJWKWLWMWNWOWPWQWZW[W^W_WbWcWgWjWlWmWnWpWrWuWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWW W!W"W&W)W0W6W7W8W9W;W<W=W>W?WCWDWEWLWNWPWSWUWVWXWZW[W\W^W_WdWfWgWhWkWrWsWWWWWWWWWWWWWWWWWWWWWWWWsjERonny^Technical, Binding_25`42a5.5bAd) MIH_NET_SAP: This represnets the abstract Media-independent media-dependent interface of MIHF which provides transport services over data plane on the local node, supporting the exchange of MIH information and messages with remote MIH Function.@A   33  ,  33-  ? @ N  33X @ b  33    33cMIH_NET_SAP is only for data plane transport. This is not clear from the text. Since it maps to media specific data link SAPs, such as CS_SAP, LSAP, etc, MIH_NET_SAP should be media dependent. d2071b  33    33cMIH_NET_SAP is only for data plane transport. This is not clear from the text. Since it maps to media specific data link SAPs, such as CS_SAP, LSAP, etc, MIH_NET_SAP should be media dependent. d2071} -bdochWiWWWWWypeDiscovery. proposes modifications to allow an MIH node to list the Commands it supports while at the same time specifying the type of links that support the Commands (i.e. certain links support common Commands while others support specific Commands) 4.The document 21-06-0792-00-0000-LinkTypeDiscovery proposes modifications to allow an MIH node discover all the services that its peer support for all link types. Thus only one message will be necessary to C#discover all link-specific service cp €marked⿃ۃރ  #)4@G_bchjmnostvyz{|}㝃㠃㡃㢃㣃㤃㦃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃€110HWIW1112=MW❃➃!}14>15ⴃⵃⶃⷃ 1617?18⹃~192@W╃200W21⪃W2223a24*,25:ރ26273AW⥃4z{31; 329 36 373846W〃W5,⨃k|7.2.2.2]9⛃f19kf24Af33QfigWfig20Vfig-35tWWt21Vt4Vt15ef@t16Xt17YZt25Kt31Rt4rt69:;t87table6Wtable46Vtable-6tbl@WAWHWIWMWtbl10HVIVtbl12MVMVMVMVonly for a ce`6mERonny^Technical, Binding_28`60a5.5.3bNode may directly use L2 for exchanging MIH Signalling, as the peer MIH Function may be embeded in a PoA. Though a Mobile Node is not connected to a specific 802 network, a Mobile Node may directly use L2 for exchanging MIH signalling whithin the scope of the specific 802 network permission. However, the Mobile Node may also use L3 for exchanging MIH signalling, for example in cases where the peer MIH Function in not located in the PoA, but deeper Bin the network. @A>  33  M  33>cSince 802.11u decides to accept MIH message exchanve over layer 2 in state 1, which is Moble Node is not connected to any AP, MIH message exchange using layer 2 should be stated. d2079g4999wDeferred 2006/11/14mERonny^Technical, Binding_28`60a5.5.3b 33    33 bnodesWaWWnonFWnon-accessWnon-poa[Wnormative_W+WnotFWUWWWW$WEW^WcWeWlWrWwWWWWWWWnotehWxWWWWnotethisshouldbeconsitentthroughoutthedocumenthVnoteupfrontthattherttinformationmaynotbeavailableVnotedqWnotification6WTcisgWjWkWlWmWnWpWqWrWsWuW|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWBYEUlises^ Editorial_34`46a5.8b`Rephrase to : "... (the MIH SAP), reducing the inter-media differences to the extent possible."cGThe section in unintelligible as written. There is/are missing word(s).d2103g2296 2006/11/16ZEUlises^ Editorial_5`13a5.1.3bRephrase to: ".monitoring of packet loss on the link on current network and of signal strength on the link on both current and target networks in order to."cn in unintelligible as written. There is/are missing word(s).d2103g2296 2006/10/31ZEUlises^ Editorial_5`13a5.1.3bRephrase to: ".monitoring of packet loss on the link on current network and of signal strength on the link on both current and target networks in order to."co: ".monitoring of packet loss on the link on current network and of signal strength on the link on both current and target networks in order to."c... event subscription." from 6.1.5.SRu_cThe draft aims at enhancing INTER technology handovers while the function addresses INTRA handovers specificacally. This is outside the scope of 802.21d2252g2302vAThe MACs have enough state to know the difference between link up/down/going down and link handover imminent/complete. They are not the same. We cannot accept the suggested remedy. See link handover imminent for justifcation of value of these link events for intra technology handover wRejected 2006/11/16Marked`EUlises^Technical, Binding_34`1a5.7b>We propose tha the size of the MIH Message be limited to 1 MTUcCurrently the draft does not specify a limit to the MIH message size. This unecesarily loads scarce radio resources and complicates implementationsd2100g2303w Withdrawn 2006/11/16aEUlises^Technical, Binding_175`22a8.5.1.47.1bYRemove this section as the same effect can be achieved using a Link_Up.Indication messagecnetworkBWiWpWWWWWWWWW-W7W9W<W=W>WCWDWRWZWzW|WWWWWWWWWWWWWWWWWWnetworkselectiondiscussionin6.2.2.1isoutofplacethisBVnetworkstandardsieisneedednotonlyfortypecontainern>Vnetwork-controlledxWnetwork-initiatedyWxWWnetwork/poaWnetworks'WWW-W2WZW]WiW{WWWWWnewWW!W;W\WWWWnewlinkidentifierWnewlinkidentifierhasarowbutisnotlistedVubdistinguishkWdl~WdocwW|W}WWWWW!W"W)W+W,W-W.W0W1W2W;W=W]W^Wgbrevisefiguretodistinguishl2transmissionoverdataplanekVrevisionJWrewrite[WWWWWrewritesentencetoreflectthefactthatonlyoneprotocolVl{brevisefiguretodistinguishl2transmissionoverdataplane@~rewritethesentencestartingwithexamplesincludetostate@grewritethissentencesoastoclarifywhatcoreelementsar@Rsap@\section7.3.1shouldbelinkeventdiscoveras1intable16@Lsections@services@signalling@specifies@dspecify@subnets@9swicth@tables@the@UE+thedescriptionsfortable15areinsection7.4thereforet@themnhasamihfimple@they@thresholds@tlv@tlvs@totoamismatchinthesupported@-(qERonny^Technical, Binding_50`60a6.3.3bAThe MIH function in the UE discovers the MIH capability support from the PoA either through the media specific broadcast information containing the system capabilities. It should be noted that the pre-authentication query facility is provided only for MIH information query and cannot be used for carrying other MIH protocol services except ES and/or CS capability discovery query using MIH_Capability_Discover embeded into L2 management frame. However, after authentication and attachment to containing the system capabilities. It should be noted that the pre-authentication query facility is provided only for MIH information query and cannot be used for carrying other MIH protocol services except ES and/or CS capability discovery query using MIH_Capability_Discover embeded into L2 management frame. However, after authentication and attachment to ines the transport services that can be used by MIHF. >006/10/24 |bAf  33        33f determine one or more access network type(s), specific channel(s) and PoA information, if present. Reformat ScanCommand to indicate as below. 1. Lower Frequencybound for the band in MHz 2. Upper Frequencybound for the band in MHz 3. Network access type (TYPE_IE_NETWORK_TYPE).CcW?WWW7WWWWWentriesPWentryJWW9WmWequivalent]WerrorpWWEWWerrorsEWesqWespeciallydWessidFWestablishW'Wetc2WWWmWWr8rcDiscovery mechanism using layer 2 is in scope of 802.21. Therefore discovery mechanism using layer 3 only be outside the scope of 802.21. d2152g5005viDelete the sentence: "The mechanisms related to discovery or configuration of peer MIH entities ......"wAccepted-Modified 2006/11/16e network may request for the above set of Information Elements from a peer MIHF located in same or different network using the MIH protocol. The mechanisms related to discovery using layer 3 protocol or configuration of peer MIH entities are oB)utside the scope of IEEE 802.21 standard.@A>  33    33>otocol. The mechanisms related to discovery using layer 3 protocol or configuration of peer MIH entities are oB)utside the scope of IEEE 802.21 standard.@A>  33    33>X  33~ts from a peer MIHF located in same or  qbBa certain PoA, all the MIH protocol services including MIIS may by use of data frames specific to that media technology or in a media independent way by useing higher layer IP based protocol in a media independent way. Some technology, .e.g. 802.16 may allow MIH protocol services using L2 management frame after authentication and attachment to a certain PoA. Additionally, any MIHF within the network may request for the above set of information elements from a peer MIHF located in same or C-different network using the MIH IS protocol.  @A~  33M  T  33O    33*  .  331  335  338  33i  33  33    33  33    33  X  33~MIHF. )bT_‚:‚A‚B‚C=}❃➃⟃!5b}‚Dnp‚E⠃Y`o‚Gj⡃X‚H‚J>x‚Q@⣃W‚RA⤃‚T?By‚U⦃⧃~‚V67㈃‚Wh‚Xk㊃㋃‚Y89:‚Z;‚a0C~⩃qゃ㽃‚brr‚ci⪃V‚dD<‚eEFG‚fHIJK⫃=㜃‚gL㛃‚hM‚iNOP‚jQ‚q&‚r'>e㷃㹃㻃㼃‚s8‚uUV[\]^‚w_⬃⮃‚x1l⭃⯃Ⰳ3?‚y+‚zWⱃⲃⳃ s‚eⴃⵃⶃⷃ @‚2XY⸃]t‚Z‚3Tf⺃‚R‚‚‚‚‚_a5.5.4⛃5.6=❃➃!5.6.1⟃n5.6.1.15b5.6.2opBUcshown1WDWWW~WshowsdW}W~WWsiWside3W>W?WsignalZWWsignaling]WWWsignallingWsimilar^Wsimple[WsimplyWsince\WiWrWWWWWWWWZW\WfWjWlWnWoWsWWsince802.11udecidestoacceptmihmessageexchanveoverlalVsinceextendedschemashouldalwaysbevenderspecific\Vsincemihnetsaprepresentsbothmediadependentl2datalioVsincemlmesapisinchargeofmihframetransportthroughcsVgureVsomewhereWsounds^WsourceW WfWsourceidentifierfWspecific\WrWWWWWWW WgWjWspecificacally_WspecificallyWspecificationiWWW W WW+W3WGW^WnWspecificationsWWWspecifiedWW-W/W=WNWVWaWcWvESrinivasF Sreemanthula^Technical, Non-binding_8`45a3.0bqClean up the definitions. "Service primitive" definition used n-user and n-layer. Redefine using general terms.cDefinitions or terms not used in the main specification need not be defined here. 1.hard handover/soft handover/seamless handover 2.N-Entity 3. N-Event 4. N-Layer 5. N-User 6. Remote N-Trigger d2028g2235imichael williamsjpEnough modifications in defn's section that text is required (non-editorial?) so reject the comment completely .kons or terms not used in the main specification need not be defined here. 1.hard handover/soft handover/seamless handover 2.N-Entity 3. N-Event 4. N-Layer 5. N-User 6. Remote N-Trigger d2028g2235imichael williamsjpEnough modifications in defn's section that text is required (non-editorial?) so reject the comment completely .kell.d230g5007 2006/10/31uERonny^Technical, Non-binding_131`48a7.4.14 peer MIHF located in same or o2csincetheieandtlvsaregoingtobetransportedovertheniVsingleWsitWsize`WWWsnrUWsoWWWWWWWsome0WWWW-WWWWWWsomeprimitivesareusedwronginthisfigureVsomethingWsomewhereWsounds^WsourceW WfWWsourceidentifierfWspecWspecific\WrWWWWWWW WgWjW~WWWWWWWWWspecificacally_WspecificallyWspecificationiWWW W WW+W3WGW^WnWpWvWspecificationsWWWWspecifiedWW-W/W=WNWVWaWcWWWWspecifiesW<JbprovidesWWjWWprovidingwWWproxyWW,Wqos`W"WqualityW"WquerynWWWWEWeWqWWWquerytypestatus1isusedforEVqueryresourceflagWqueryresourcelistWquotationXWrWr1RWr2RWr3zWr4RWr5RWrangerWWWUWrateNWWrdf^WWre-do6Wre-order$WZWre-orderlinkdetectedintable17tothesameorderasintZVre-orderreferences$Vre-registraion$Wre-registration+W.Wread@WAW"Wreadability<WWWreasonqWreceipientTWreceiptTW$Wreceive4WreceivedWcWreceivesWreceivingdWWrecognizeUWrecommendWrecommendthatitisclarifiedthatfunctiondiscoveryatl3VredefinevWreducingYWredundantWreferrWxWreferenceMW]WWWW WzW0citisnotclearwhyisistheonlyservicethatcansupportVitisnotpossibletousethedestinationtimestampinpackeVitisstatedthatNVitisunclearastowhatismeantbythebroadcastdomaininVitneedstobemadeclearthatfigure25isnotarepresentaVitshouldbeclearlyshowwhichtransportsapshallbeusedkVit's(WWWitemWWWitemsWWitemslisteddonotagreewithrowsforexampleinfoqueryresVitswWWWWWWGWVW\WdWgWWWWWitselfWjitterWWjust3W9WFWkeyWkindBWNWgWkinda1WknowcWdWWdWgWWl2WWWW WoWWl3WWWWW WoWWWWl3mpWl3mpmissinganmVl4WlabelingWlackWlacksRWSWlastW +lbAWhen connected to a 802 network, a Mobile Node may directly use L2 for exchanging MIH Signalling, as the peer MIH Function may be embeded in a PoA. Though a Mobile Node is not connected to a specific 802 network, a Mobile Node may directly use L2 for exchanging MIH signalling whithin the scope of the specific 802 network permission. However, the Mobile Node may also use L3 for exchanging MIH signalling, for example in cases where the peer MIH Function in not located in the PoA, but deeper Bin the network. @A>  33  M  33>cSince 802.11u decides to accept MIH message exchanve over layer 2 in state 1, which is Moble Node is not connected to any AP, MIH message exchange using layer 2 should be stated. d2079g4999v 2006-10-233|ESrinivasF Sreemanthula^Technical, Binding_26beChange "3GPP/3GPP2 network and core networks" to "3GPP/3GPP2 Networks" homegeneous and heterogeneousK {v@A> 33:  33G 33>wAccepted-Modified 2006/11/16 2006-10-23Marked3|ESrinivasF Sreemanthula^Technical, Binding_26bHChange "3GPP/3GPP2 network and core networks" to "3GPP/3GPP2 Networks" ciIt is not clear where the MIH function may be located in the 3GPP/3GPP2 network. Good to be generic here.d2075g2241v6Change to "3GPP/3GPP2 network or other core networks" wAccepted-Modified 2006/11/16 2006-10-23Marked5}ESrinivasF Sreemanthula^Technical, Binding_32bAdd it.c@there is no NET-SAP in the picture but the description shows it.d2088g2242wAccepted 2006/11/16 2006-10-23Marked12~ESrinivasF Sreemanthula^Technical, Binding_44b1. Add it 2. Remove "Remote"c1. There is no "Link Command Execution" shown for local commands. 2. Fig also shows local commands but the caption is specific to remote command service flow.d2121[bEnhance Section 6.3.3 to have greater details on the individual Information Service Elements and move specific representations such as to the Annex (as being done with XML).cADThe Sections for Media Independent Information Service seems to lack coherency. For example, Section 6.3.7 on Information Service Schema seems to be applicable to both TLV and XML/RDF representations. It is also passing strange that the XML details are in the Annex while the TLV information is listed in Section 6 itself.Dd2154g4701v4by current draft as it already does things that way.w Superceded 2006/11/16 2006/10/20from 802.21 to 3GPP" or add subsections, similar to A1.4.e@A> 33 A 33>cSTitle not clear of which type of handover the procedure is describing in Figure 32.d390g2467 2006/10/31 2006/10/23hESubirFDasGMember06/10/31 2006/10/23hESubirFDasGMemberS (bonlyqWrWWWW!bofthisinformationisoutsidethescopeVofferWoldWW'WWoldlinkactionWomit WommunicationWon>W?WNWOWPWTWeWnWWWWWWWWWW"W$WJWNWQWZWgWjWnWWWWWWWWWoncedWWoneGWlWmWWWWWWW'W>WLW\WgWWWWWWWones WonlyWWEW\WgWbthemnhasamihfimpleVthenewdefinitionofmihscanconfirmprimitiveisasfolloVtheproposedmihprotocolstatesaredescribedinthedocume)V0VhVthequeryissuccessfulEVtherequiredmessagesshouldpiggybackmihuseridormihfpVthetextsfrom51-59onpage13shouldbeasstands"Vthetitleofsection5.1.3shouldreadqualityofservice"Vthetlvrepresentationoftheseinformationelementsisdesc8VthetypefieldshallbeonefouroctetsLVthevalueisanonnullterminatedstringwhoselengthshallFVthewholesectionshouldbeclarifiedandifthegroupfeelsVtheir_WthemWWW@WKWWWthemih-link-sapWthenNWcWeWWWWWWtherejWWWthereafter$WthereforeeW^Wthese2WjWlWWWWW"W8WmWWWWW#ESrinivasF Sreemanthula^Technical, Binding_23bRename the commands to 5. MIH_Candidate_Select 6. MIH_Query_Resources 7. MIH_Candidate_Decide 8. MIH_Candidate_Access_Complete Also update table 15 and SAP definitions in section 7.4.x.cADefinitions of commands 5,6,7 and 8 are relevant to network selection but the use of term "handover'" coincides with the terminology used by handover signaling protocols e.g. MIP. This confuses the scope of functionality between 802.21 and mobility management protocols. d2061g2244vinitions in section 7.4.x.cADefinitions of commands 5,6,7 and 8 are relevant to network selection but the use of term "handover'" coincides with the terminology used by handover signaling protocols e.g. MIP. This confuses the scope of functionality between 802.21 and mobility management protocols. d2061g2244vESrinivasF Sreemanthula^Technical, Binding_4006-10-234ESrinivasF Sreemanthula^Technical, Binding_403EQiaobingFXieGMember^ Editorial_74`7a7.2.3b6move current section 7.2.3.1 "MIH_NMS_SAP" under 7.2.2cMIH_NMS_SAP is just one of the media independent SAPs listed in 7.1.2. There is no need (and is confusing) to put it out side of 7.2.2d2238g4686k  2006/11/16 2006/10/204EQiaobingFXieGMember^Technical, Binding_98`28a 7.4.3.1.3bAThis primitive is generated by an MIH User a registrant such as MIH Function that is seeking to receive event primitives from a point in the protocol stacks terminating either end of the link.@AR 33  +  33M 33Rc2Registrant would be an MIH User, not MIH function.d2272g4687k wAccepted 2006/11/16 2006/10/205EQiaobingFXieGMember^Technical, Binding_99`13a 7.4.4.1.1bArThis primitive is used by an MIH User MIH Function (the subscriber) to unsubscribe for a set of link layer events.r@%binstance{WWWinstanceslWinsteadWWintegerNWOWWintelligentwWintendedWinter-mediaYWinteractionmWinteractionsWinterface~WWjWmWWWfacingnWintervalcWintiateWintoBWlWWWWWW W WWWW!W*W,WFWeWqWWintraWintroduceWW!WintroducedW^WintroductionW^Wip8WQWW7W;WNWPWqWwWWWipv4NWis1W4W5W7WFWMWPWRWSW\W^W_WdWhWjWlWnWsWuWyW~WWWWWWWWWWWWWWWWWWWW WWWWWWWW'W+W-W.W8WEWFWJWNWQWUWWW^WcWfWlWqWwWWWWWWcway'WUWWWWWWwaysaWdWweWW W!W9W\W]WWWwellWWWRWtWWWWWwepWwereGWuWwhat,WIWJWTWWWWWWWWWWNWgWpWWWWWWWWWwhatdoestheoldlinkhavetodowhenb6bi-castingrequestVwhatdoestheoldlinkhavetodowhenb7handovercancelreVwhatismihfunctiondiscoverythisshouldhavebeenintroduVwhatisoption1arethereanyotheroptions,VwhatisthepurposeofmihnetworkaddressinformationnoneVH_7ccontrolWkWcontrol/managementsWcontrolledWconvenienceDWWconversationWcopiesdWcorerWWWcorollationWcorrectrWWWW)W0WPWhWWcorrectspellingofhomogenousVcorrectsyntaxVcorrectedWobMove "5.6.2.3 MIH_NET_SAP" to media dependent SAP section. Move the section after section5.6.1.1. Move line 38 (written below) to line 30 after CS_SAP. 2) MIH_NET_SAP: This SAP defines the transport services that can be used by MIHF. cSince MIH_NET_SAP represents both media dependent L2 data link SAPs and media independent L3 data link SAP, it should be media dependent. d2099g5002iVivekkMIH_NET_SAP uses (or maps to) MIH_LINK_SAP for all L2 interactions with respective media. For L3 this SAP may define other primitives...mAccepted-ModifiedwAccepted 2006/11/16MarkedpERonny^Technical, Binding_33`60a5.6.2b[Provide more text and mechanisms or delete MIH_NMS_SAP related parts throughout the draft. cIt is not clear what MIH_NMS_SAP function is. Only definition is stated in the specification. Provide more text and mechanisms including primitives. Otherwise delete the section. d2098g5003vby comment 2090.w Superceded 2006/11/16 \"EVivekFGuptaGMember^Technical, Binding_50`50a6.3.3b Add the following in section 6.3.3: " The IEs may be retrieved using either the TLV mechanism or a RDF based query mechanism. The standard does not recomend or mandate choice of a particular mechanism."c Why **must** a MN support both TLV and RDF query types? Why not allow the MIHF mfg to support just the type they believe is needed. This would have the benefit of MN implementations being more lightweight. d2147g2234vAdd the following in section 6.3.3: " The IEs may be retrieved using TLV or RDF based query mechanism. The standard does not recommend or mandate choice of a particular mechanism."wAccepted 2006/11/16 2006-10-23EVivekFGuptaGMember^Technical, Non-binding_14a5.1.3b c3: " The IEs may be retrieved using TLV or RDF based query mechanism. The standard does not recommend or mandate choice of a particular mechanism."wAccepted 2006/11/15 2006-10-23PbincludeWWWWWWWincludesomeexplanationsatowhythisfeatureisneededasVincludetheseprimitivesVincluded'W_WWWNWfWincludesWWWWWWWNWfWincludesWWWWWW}`bdirectionW7WWdirectlylWdisconnect'WdiscoverXWfWWWRWgWqWWdiscoveredWdiscoveringgWdiscoversqWdiscoverylWWWWWWqWrWdiscoveryisimplicitlyperformedVdiscussTWpWwWWuWdiscussandacceptclarifyingtextin21-06-0793-00-0000naiuVdiscussandaccepttheconceptdescribedin21-06-0781-00-00pVdiscussandaccepttheproposaldescribedin21-06-0780-00-0wVdiscussedWdiscussionWWdismissedWdistinctNWWW RcdoesxWWWWWWWWWWWW#Ja4.0y5.1.25.1.3`⏃␃⑃"Z㥃5.1.8⒃5.1.95.2wWxW5.2cwV5.2exV5.3<5.3.1╃[5.3.274z5.4.1.45.4.2.35.4.3tu☃{5.5,♃⚃jkl㚃㢃㣃5.5.15.5.25.5.3mz 9ZcAThe section implies that signal strength and packet loss will be monitored on both current and target networks. Packet loss should refer to current network only, since it is not possible to monitor packet loss until establishment of data connection on target network link.d2023g2297 2006/11/16[EUlises^ Editorial_21`12a5.3.1bSection seems to say: first connection with PoS co-located with PoA causes/implies a second connection to non-PoA PoS. The two connections should be independent of each other. cSection seems to say: first connection with PoS co-located with PoA causes/implies a second connection to non-PoA PoS. The two connections should be independent of each other. d2058g2298 2006/11/16\EUlises^Technical, Binding_166`9a8.4.1.12b‚g‚h‚iтj‚q‚r‚s‚t‚u‚v‚w‚x‚y‚z‚ۃ܃‚‚‚‚‚‚'d2304g2276iRonnyjAChange new PoA to new PoS@AR 33 33 33 RkPoA should be PoSmAccepted-ModifiedvAThis primitive is generated by MIH Function on new PoA PoS to indicate that MIH_Network_Address_Information Request message is received from a peer MIH Function on old PoA Also change 7.4.14.2.4 as well.@A 333  337 338 < 33  33 33 wAccepted 2006/11/16EPeretzFFeder^Technical, Non-binding_134`34a 7.4.14.3.4bAWhen the MIHF in the new PoA receives this message from the network entity, the MIHF in the new PoA further delivers this message to the MIHF peer in the old PoA. When the mobile node receives this primitive,@ction on old PoAd2304g2276iRonnyjAChange new PoA to new PoS1bcannotberestrictedtoheterogeneous{V-btoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWw Superceded 2006/11/16 2006-10-23EAlbertFVidalGMember^Technical, Binding_45`9a6.2.5.1b@Detailed in contribution 21-06-0783-00-0000-centralized_NIHO.doccATo allow all types of network initiated handovers it is necessary to allow Network -> Network and Client -> Network for the commands MIH_Get_Status and MIH_Configure, not only Network -> Client. Please, see contribution 21-06-0783-00-0000-centralized_NIHO.doc d2126g2222vFor Table-3 and Table-4 (MIh Events and MIH Commands), Remove the "Remote Direction" column. Merge the contents of this column with that of Description column and add appropriate text.wAccepted-Modified 2006/11/16 2006/10/23T 4g2253 2006/11/14 2006-10-2331 2006-10-23ESrinivasF Sreemanthula^Technical, Binding_111`20a 7.4.9.2.2bg looks.d284g2251 2006/10/31 2006-10-23ESrinivasF Sreemanthula^Technical, Binding_111`20a 7.4.9.2.2bbcannotqW{Wb15-mih W W16XWZWfW16-mih W W161 W163zW17XWYWZWW17-mih W170%W18W18-mih W W19kWWnW2CWHWJW|WWWWWW W WWWWW-W7W9W:WEWFWMWNWOWRW\WgWoW~WWWWWWW6 T6vwAccepted-Modified 2006/11/16 2006/10/23Table 47E YoshihiroFOhbaGMember^Technical, Binding_45`40a6.2.5.1bA[1] Change Remote Direction field: Client -> Network, Network -> Client Network [2] Change Comments field: Sent from MIHF entity of Moble Node to either current MIHF entity or target MIHF entity or sent from serving MIHF to target MIHF to obtain IP configuration related information.@A  33A  H  P  Q  33    33cWRemote Direction and Comments fields of MIH Network Address Information seem incorrect.d2128g2436iRonnymAcceptedwAccepted 2006/11/16 2006/10/23T88E YoshihiroFOhbaGMember^Technical, Binding_48`4a6.3.3bb^Technical, Binding_111`20a 7.4.9.2.2b05`20a 7.4.7.1.2a^Technical, Binding_105`20a 7.4.7.1.2g5022 2006/10/24binWWWWWWWWWWWWinanycasethemihfunctionshouldhavetheknowledgeofwhrVenada€!€nada!€golmienada€c€nadac€golmienada€E€nadaE€golmienada€R€nadaR€golmienada€pefg.€nadap€golmienada€nadae€golmieƒnada€nadaf€golmienada€GRc€nadaR€golmienada€nadaG€golmienadanadacgolmienadaJnadaJgolmienada:nada:golmiebalsoupdatetable15andsapdefinitionsinsection7.4xVamechanismWamendWamendtheannex1.3handoverprocedurefrom802.11to3gpp2Vamendments+W,W-W.W1WWWamountWan4W5W>WFWUWlW{WWWWWWWW'W4WEWFWJWdWgWwWWWWWWWWCWPWQWWWXW[W_WeWfWiWpWwWzW~WWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWW W!W$W'W+W,W5W6W:W@WFWJWMWNWOWRWUWZW\W]WaWeWgWjWmWnWpWqWrWtWuWvWwW{W|WWWWWWWWWWWWWWWWWand/orqWUcbtablesWMWtakeWeWtargetsW7WZWWWWtargetpoaidentifierOWtcp/ipWtcp/udpWtechnical+Wtechnologies^WwWWtechnologyWqWWtemplate8W9W:WWtermWterminalWterminatedFWterminating4WterminologyWtermsWvWtext0WCWEWHW\W_WiWnWrW|WWWWWWW WWNWpWsWuWzWWWWWtexts"W+W3Wtextual_WtexualWQWtha`WthanWthat4WCWQWUW\WcWjWlWsWyWWWWWWWWWWWW W$WSWUW^WgWoWqWWWWWWWWWWWWWWcdiscardWGWdisconnectuWWdiscoverXWWWWWWWRWfWgWWWWWdiscoveredlWdiscoverybWlWWWWWWWWW3W;WgWqWrWdiscoveryisimplicitelyperformedVdiscoverymechanismusinglayer2isinscopeof802.21therrVdiscussTWdiscussedWWdiscussesWdiscussion<WBWCWWWWdiscussionin5.3repeatedlyreferstomihserviceswhichar<VdiscussionofhandoversduetomobilenodemovementisproviVdiscussiontextfromline50pg50toline13page51isoutCVdistanceWdistinguish-W\WWdozWWWW^WWWWWdocWWWdocumentyWWW?WdoesGW`WWWWWWWW#W&W'WFW^W`WaWdWeWgW=cothersgWotherwiseeWW#WpWoui+out3W9WBWCWZWW WWoutsideuWWGW_WrWoveriWWlWWWWWycip8WW&W;WNWPWWWipv4dWNWipv6dWis,W1W2W3W7W9W=WBWCWEWFWHWIWUW[W\W]W^W_W`WaWbWcWdWgWkWlWmWnWrWtWuWwWxW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWW!W"W%W+W,W-W.W3W4W5W8W9W<W>WFWGWJWNWOWPWQWSWTWVWWWXWZW\W]W^W_WaWcWdWfWmEAlbertFVidalGMember^Technical, Binding_108`3a 7.4.8.1.4b@Detailed in contribution 21-06-0783-00-0000-centralized_NIHO.doccAThe current definition of 'Throughput' seems to be defined without taking into account the already in use bandwidth by other users. We suggest to add another parameter called 'CoS Available Throughput' which refers to the maximum data throughput that a user can use, given the data throughput already used by other users and the data throughput the PoA reserves for other potential users, according to its own policies. We also consider this available throughput needs to be specified for everyr parameter called 'CoS Available Throughput' which refers to the maximum data throughput that a user can use, given the data throughput already used by other users and the data throughput the PoA reserves for other potential users, according to its own policies. We also consider this available throughput needs to be specified for everySrinivasg5025 2006/10/248bcThere is no need to present technology specific relationships in the introductory material, especially before the MIH is clearly defined.d2078g2253 2006/11/16EGolmieFNadaGMember^ Editorial_29`44a5.5.4bCorrect the inconsistency.chAn inconsistency between the name, MIH-3GPP_SAP, in the figure and its name, MIH_3GLINK_SAP, in the textd2084g2254 2006/11/169EGolmieFNadaGMember^ Editorial_30`46a5.5.4bRemove line 46-48.c&Note does not belong to specificationsd2085g2311 2006/11/169EGolmieFNadaGMember^ Editorial_32`1a5.6bAdd missing SAP.cFigure is missing MIH_NET_SAPd2091g2255 2006/11/1612EGolmieFNadaGMember^ Editorial_32`1a5.6boDelete figure 4 and update figure 12 and add another block marked other to the right and below theMIH-LINK-SAP.c>Figure 4 and Figure 12 are competing. Only one is necessary .d2092g2256 2006/11/1612VbbeneficialWberWbetter<W@WAWWbetweenWWW W+WmWWWWWnWbi-directionWbimapQWbitRWSWWWWWWWWWWWWbit5&WbitmapWWWWWWbits WVWblockWblueprint^WbothZWeWWboundarydWJWbriefWbroadcasWbroadcastWqWWbroadcastingWWbroadcastingmihcapabitydiscoverresponsemessagemayinclVbroader_WbsmWbulletWbutWlWWWby4W5WlWyWWWWWWWW WaWbWmWoWqWrWwWWWWbyteiWbytesWcmWcalledjWSWcancWlWxWWW W$W]W^W_WaWdWoWwWWWWWWWcandicateWcandidatesWWWcandidatedWkchowdoestheqosmodelfitintothemihframeworkhowisit`VhowthemihfidisgeneratedandhowtoavoidconflictionanbVhowtoparsethemacaddressfieldifitisvariablehowwoucVhowwouldthereceiverknowifaipv4oripv6addressisusedVhoweveeWhoweveruWyW{WWWWW\W^WdWgWWWhttpsWi@WAW#W$W&W'WdWfWgWWm$EAlbertFVidalGMember^ Editorial_47`16a6.3.2ban MIH PoS may actcAan MIH PoS may acts@A* 33  33*d2134g2225 2006/11/16 2006/10/23EAlbertFVidalGMember^ Editorial_129`65a 7.4.14.1.1b forwardedc frowardedd2297g2226 2006/11/16 2006/10/23EAlbertFVidalGMember^ Editorial_131`34a 7.4.14.1.3b preparingcreparingd2301g2227 2006/11/16 2006/10/23EAlbertFVidalGMember^ Editorial_131`41 acts@A* 33  33*d2134g2225 2006/11/15 2006/10/23EAlbertFVidalGMember^ Editorial_129`65a 7.4.14.1.1b forwardedc frowardedd2297g2226 2006/11/15 2006/10/23EAlbertFVidalGMember^ Editorial_131`34a 7.4.14.1.3b preparingcreparingd2301g2227 2006/11/15 2006/10/23EAlbertFVidalGMember^ Editorial_131`41qTÄ1H@Ä1x@Ä2:@Ä2Q@+Ä3@Ä3@* @ @Dxg€ €€7@€NA€bperetz€eYC€koh4€golmie@€@2€#€BA€golmie@€nada/uB1ishizu.2golmie@*):6-]eleanor@,+r1@0$6@3W7jin@5<yoshihiro@8‚V;‚"ohba:9‚Fronny@?‚N>=‚\qF‚u@‚guptaI‚D‚ H‚@G‚guptaKJ! @@EEYan PENG / Jing LiuGObserver^ Editorial_43`38a6.2.2bCommit Request to MN and target PoS is not restricted strictly. In figure 31, after the serving PoS receives MIH_Handover_Commit Response message, it send MIH_Handover_Commit Resquest message to inform the target PoS. Then the problem comes. If the target PoS rejects the request of handover via MIH_Handover_Commit Response (with HandoverStatus option set to 0), due to some reasons such as the resources are unavailable now. In curC rent draft, the serving PoS has to way to inform the MN this information, because there is no message exchage between serving PoS and MN, after the MN sent the MIH_Handover_Commit Response. Then the handover would fail, and the service of subscriber would interrupt.d388g2219 2006/10/31 2006/10/2331EYan PENG / Jing LiuGObserver^ Editorial_43`38a6.2.2b sending the MIH_Handover_Commit Response message to the Serving PoSpIa 7.4.14.1.4brequestcreqeustd2302g2228 2006/11/16 2006/10/23EYan PENG / Jing LiuGObserver^Technical, Non-binding_187`1a Annex A1.2bThe detailed procedure of network-initiated handover need to be modified. Or 802.21 should offer a mechanism and corresponding primitives to handle handover failure.cAIn the case of network-initiated handover procedure, after the Serving PoS decides the handover target, it requests handover commitment to the specified PoA by sending the MIH_Handover_Commit Request message to the MN. And the Serving PoS also notifies the target PoS of the fact that MN is about to move to the network through the MIH_Handover_Commit Request messages. The MN replies the result of the handover commitment by sending the MIH_Handover_Commit Response message to the Serving PoSrial_131`34a 7.4.14.1.3b preparingcreparingd301g2227 2006/10/31 2006/10/23EAlbertFVidalGMember^ Editorial_131`41a 7.4.14.1.4 citisunclearhowthismodelcanapplytopeertopeerconneVitisunlcearmihprotocolackoperationisdefiningastateVitneedstobemadeclearthatfigure25isnotarepresentaVitshouldbeclearlyshowwhichtransportsapshallbeusedkVit's(WWWWitemWWWitemsWWitemslisteddonotagreewithrowsforexampleinfoqueryresVitswWWWWWWGWVW\WdWgWWWWWWWitselfWjitterWWWWjust3W9WFWWWkeyWWkindBWNWgWkinda1WknowcWdWWdWgWWWWknowsWl2WWWW WoWWWWWl3WWWWW WoWWWWl3mpWl3mpmissinganmVl4WlabelingWlackWlacksRWSWlargeWlastWvatlWnWwWWWWatanylocationthereiscoverageprovidedbydifferentwireVattachmentWWauthenticated~WlWauthenticationtWWavailabletWuW~WWavoidedWb_WbackwWbalanced`WbasedWWWWWWWbasedonremedy2incontribution21-06-0827-01-0000-tVbasedonremedy3incontribution21-06-0827-01-0000-tVbasedonremedy4incontribution21-06-0827-01-0000-tVbasic_WbasicallyWWbe1WRWiWlWmWoWpWtWuW~WWWWW6W]WcWdWeWgWlWwWWWWWWWWW2244thesameremedyshouldapplyVVVby2291Vby2303VCVDVbycomment2028)Vbycomment2032Vbycomment2071Vbycomment2090pVbycomment21430Vbycomment2187Vbycomment2328Vc/iWcanwW7 bAComment: The current text refers to a possibility that will be either dismissed or confirmed as a necessity when the 802.21 standard reaches completion. The sentence should not appear as is in the final specification of the standard. Meanwhile, it can be kept in the draft as an editorial note and then either removed entirely or modified and reintegrated in the text when the necessary amendments to other standards are exhaustively identified.cASuitable amendments may be required to link layer (MAC/PHY) specifications of different media specific technologies such as IEEE 802.11, IEEE 802.16, 3GPP, 3GPP2, etc. to satisfy the requirements of generic link layer intelligence identified by IEEE 802.21.d2019g2239iMichael Williamsj/10/23EAjayFRajkumarGMember^Technical, Non-binding_4`15a1.5bof the SAPs that define the interface of the MIHF with the lower layers.c$ bAWe propose to modify either the figure 17 or the figure 18 to make the consistency between the two figures. We may add the link command between the remote MIHF and its low layers in figure 17, or delete the link command between the remote MIHF and its low layers in figure 18. cAThe description of Remote MIH Command in the figure 17 and figure 18 is not consistent. In the figure 17, after the MIH Function in Remote Entity receives the remote MIH Command, it does not deal with it further. But in the figure 18, after the Remote MIHF receives the remote MIH Command from local MIHF, it will send the corresponding link command to remote lower layers further. It's not puzzling that whether the Remote MIH Comment flow includes the Link_Command in remote entity.d2117g2220 2006/11/16 2006/10/2317EYan PENG / Jing LiuGObserver^Technical, Non-binding_66`45a6.3.8 2006/10/24 2006/10/23g5034 2006/10/24^technicalbindingVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVbpurpose WputCWW,WputsWqos`W"WWWqualityW"WWqueriedWqueriesWqueriyWquerynWWWWEWeWqWWWWWWWWWWquerytypestatus1isusedforEVqueryresourceflagWWWqueryresourcelistWWWquiteW^WWre-do6Wre-order$WZWre-orderlinkdetectedintable17tothesameorderasintZVre-orderreferences$Vre-registraion$Wre-registration+W.Wread@WAW"Wreadability<WWWreasonqWreceipientTWreceiptTW$WWreceive4WreceivedWcWreceivesWreceivingdWWWrecipientWrecognizeUWrecommendWrecommendthatitisclarifiedthatfunctiondiscoveryatl3VredefinevWreducingYWredundantWreferrWxWreferenceMW]WWWW WzWij1NW11NW12WNW149W152W153W16]W17]W173oW183NW193NW23WNW20W23aWWW25W252oW3WNW303WCW328W336W34NW3gppWWW3gpp/3gpp2W3gpp2WW4oW5.4.3W5.7W55oW59^W6.11W6.3.7.1W6.41W3W61NW653W673W71WW8aW8.2W8.2.1W8.3.13W8.4.1.35nW8.4.1.36nW8.5.1oW8.5.2oW8.5.3oW8.5.4.1nW8.5.4.2nW802W802.1W802.11WWW802.15W802.16WW802.21WWWW802.3aWWne65insection6.423Vaddthefollowingtextintothebeginningofline23page15VaddthesuggesedsentenceasfollowinglVaddedWaddressNWWaddress/accessNWaddress/dhcpNWaddsWagentNWagreeaWWCEEleanorFHepworthGMember^ Editorial_153`64b.change MIH Discovery to MIH Function Discoveryc+1) should be called MIH Function Discovery d2327g2222 2006/11/16 2006/10/19EEleanorFHepworthGMember^Technical, Binding_154`61bNote up front that the RTT information may not be available, and that immediate retransmission by an application may suffer from unpredictable delay introduced by the transport layer.cAcIn the case of L3 transport, the actual transmission of the packet on the air/wire may be constrained by the operation of the L3 protocol, for example, because the protocol imposes congestion or flow control. Note also that RTT information may not be available at the MIH application layer so it may be impossible to tune timers to take it into account. cd2341g2223v Need text.. wRejected 2006/11/16 2006/10/19MarkedEEleanorFHepworthGMember^Technical, Binding_155`28bRemove this sentence.s sentence.cthemihcommunicationmodelisalreadydescribedintheprev4VthemihfunctiondiscoveryhasonlybeenlistedhereandisVthemihlinksapislistedhereasasubsectionofthemediaVthemihsapspecifiestheinterfaceofmihfwithotherhigheVthemihscanconfirmprimitiveinthecurrentdraftcannotVthemihstatesareneededforthecorrectoperationofmihp)V0VhVthemihftlvencodingschemeisthesameastheencodingschmVthemihfusesmihgetinformationprimitivetogetmihinforVthemnhasanmihfimpleVthenamefieldsofrssisnrc/iberanddataratearenotusUVthenamesofprimitivesandmessagesinthisfiguredon'tma Varo vishizuxishizuy3 ykentaro xishizuzkentaro 1ishizu{kentaro ishizu|c}%p}ishizu~|c~kentaro }ishizup! jeepjunghoonjeeZIEGolmieFNadaGMember^ Editorial_16`4a5.1.8brRemove section 5.1.8 or add section to discuss other handover scenarios including when nodes are stationary nodes.cuDiscussion of handovers due to Mobile Node movement is provided however this represents only one case for handovers. d2046g2247 2006/11/16EGolmieFNadaGMember^ Editorial_16`22a5.1.9b%Delete from line 22 to end of sectionc+Text has nothing to do with Handover Policyd2047g2309 2006/11/16EGolmieFNadaGMember^ Editorial_16`46a5.2bremove section 5.2nts only one case for handovers. d2046g2247 2006/11/02EGolmieFNadaGMember^ Editorial_16`22a5.1.9b%Delete from line 22 to end of sectionc+Text has nothing to do with Handover Policyd2047g2309 2006/11/02EGolmieFNadaGMember^ Editorial_16`46a5.2bremove section 5.2itorial_16`46a5.2bremove section 5.2itter: is defiend as d43g2219w Withdrawn/csenseGW%WWsensitivetWsent WdWWsentence[WWWWWWXWcWWWsentenceinline1mentionsnetworkusingthemihisprotocoVsentencestatesthatastandardizedformatisusedyettwoaVsentencesWseparate-WsequenceWsequentialWserverNWWWWserver'sWservice1W7W:W;WhWtWWWWWWWW WWW]W^WdWgW~WWWWWWserviceanmihposmayactsasanVservice-infoIWservices1W<WjWWWW W^WWWWservingsWNWWWservingfaaddressservingaccessrouteraddressdhcpserverNVservingpoaandtargetpoadefinitionsaretoomuchtiedwitsVsession*W-W/WIWsessionidWWZxie€xiexX€qiaobing[xie€ xie xe€ qiaobing\}banmihposmayactVand1W7W:W;WCWPWQWWWXW[W_WeWfWiWpWwWzW~WWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWW W!W$W'W+W,W5W6W:W@WFWJWMWNWOWRWUWZW\W]WaWeWgWjWmWnWpWqWrWtWuWvWwW{W|WWWWWWWWWWWWWWWWWWWWWWWand/orqW cB(ration should reflect this. 4) MIH Configure Thresholds command is different from MIH configure command and they perform different functions, MIH Configure Thresholds is the corresponding MIH command for Link Configure Thresholds, MIH Configure Thresholds should not be replaced by MIH configure.d2414g4639vChanges are quite substantial. Not clera if we need to add the thresholds in media independent manner. This needs more evaluation.wRejected 2006/11/16 2006/10/20recipient of the primitive is a client upper layer and in case the handover is to be aborted, the entity which originally initiated the handover request may decide to intiate once more handover to another candidate neighbor PoA.This procedure may repeat untill handover initiating succeed or utill some criterias are satified, e.g. timer has expired or up to maximum retry times. 7.4.11.3 MIH_Handover_Prepare.response 7.4.11.3.4 Effect on receipt After receiving the response,if the queriedsvtbmoble7WWmodel`W|W4WmodificationsWW!WgWmodifiedWWmodifyW'WWmodifythesubsection7.4.7.1.3assuggested'VmonitoringZWmoreGWPWlWWQWpWWWWWWWWWmotivatedWmove3W<W@WAWBWCWHWzWWWWWWW5WoWtWWWmove5.6.2.3mihnetsaptomediadependentsapsectionmoveoVmove7.2.2.2and7.2.2.3to7.2.1mediadependentsapstVmovecurrent5.3tobeaftercurrent5.4forbetterreadabil<Vmovecurrentsection7.2.3.1mihnmssapunder7.2.23Vmoveline38writtenbelowtoline30aftercssapoVmovesection7.2.2.2tobeasubsectionofsection7.2.1medVmovestartingatthissentencetountiltheendofthissectVX Y1YnadaZX ZgolmieYnada[jameshan\hepworth]] ,EXiaoyuFLiuGMember^Technical, Non-binding_92`9a7.4.1bRemove the Figure 24 and the paragrah above Figure 24. Replace the description with the suggested Remedy 1 in 21-06-0797-00-0000-MIH_Registration_Amendments.doc and put it into Section 6.4.4. ing network. - The registration and deregistration between MIHF in a serving network and detected network. - Re-Registration when a MN changes its attached POA. - Registration update to keep the active session alive. Accept the proposed normative texts in the Remedy 1 of 21-06-0xxx-00-0000-MIH_RegBistration_Amendments.doc c1The specification in Section 6.4.4 is missing. d2215g2211 2006/11/15 2006-10-23,EXiaoyuFLiuGMember^Technical, Non-binding_92`9a7.4.1bRemove the Figure 24 and the paragrah above Figure 24. Replace the description with the suggested Remedy 1 in 21-06-0797-00-0000-MIH_Registration_Amendments.doc and put it into Section 6.4.4. cbyqWWWWWWWWWWWW&W]W^WbWcWdWgWnWWWWWWWWWWWWWWbyteiWbytesWc_WWWwWWc/iUWcalculatedWcallwWWWcalledWSWWcan1W6WEWHWeWfWqWWWWWWW&WGW]W^WdWgWkWWWWWWWWWWWcan'tWcancelWcandidateWWcandidatesWcannotWWWcapabilitiesgWWcapabilityXWlWWWWWWWW&WRWfWqWWWWcapabilityies&WcapableWcaptionW~WWcarriedNWWWcarry9W;WcarryingLWcasehWWWWWW^WdWeWkWWWWWWfederbNQ€bperetzFEJunxiangFGuoGMember^ Editorial_112`58a 7.4.10.1.2b0Replace QueryResourceList by QueryResourceFlag. c.QueryResourceList should be QueryResourceFlag.d2288g4638 2006/11/16 2006/10/17EJunxiangFGuoGMember^Technical, Non-binding_79 /170 /180/168`1 /1 /59 /1a/7.3.7,7.3.8,8.4.1.28,8.5.3.13,8.5.3.14,8.4.1.20bvAccept the suggestions in contribution 21-06-0739-02-0000-Suggestion about link parameter threshold configuration.doc.cAIn current draft, link parameter threshold configuration is vague due to the following reasons: 1) The TLV for Link Parameter Threshold is not definitely defined; 2) Link Quality Parameter Type definition is not normative and cannot reflect the common QoS measurement parameter for all technologies, hence make it difficult for 21 to configure threshold value for each technology. 3) The threshold value of a certain link QoS parameter varies with different QoS Class, current threshold configuthe response,if the queried bD---------------------------------------------------------------------------------------------------------------------------------------------- | 9 | MIH Network | L, R | Client -> Network | Sent from MIHF entity of Moble Node to either current MIHF entity or | | Address Information | | Network -> Client | target MIHF entity to obtain IP configuration related information. -----------------------------------------E---------------------------------------------------------------------------------------------------------------------------------------------------- | 10 | MIH_RegisteredEvent | L, R | MIH user query for the registered MIH-Events. | | _Discover.request | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------UABc2extendedschemaisnotdescribedinannexb_V2n-entityvV2whatarethevalidentriesfordifferentrevisionsJV200W21W21-06-0765-00-000uW21-06-0783-00-0000-cWW21-06-xxxx-00-0000-eW22W23^WW243\W244\W25WKW253EW26oWWWWW2nd@WAWEW31W_WW-WgWqWrWvWW3anexhaustivelistofinformationresourcesandproperties_V3n-eventvV31nWWW329WDWgWrW32-1Wcinformation'W7W[W_WhWiWmWtWuW~WWWWWWW WWW7W8WCWDWEWGWRW]W^WgWwW{WWWWWWWWWWWinitialize1WinitiatedWinitiatingqWinoffWinsecureWinsideWinstance{WWWinsteadmWWWintfWintegratedWintelligenceWintendedWinter_Winter-layerWinter-media;Winteract)W0WhWinteractionWinteractionsWinterface6WW WnWWWWinterfaces6WinteroperabilitybWinterpretationWinterrruptionWinterruptWintervalcWintitateWinto`WWW WWintraW_WintroducedWWintroductionW"WWintroductionparagraphcontainsmanygrammaticalerrorsandV‚K%L‚LMK%‚M@bgoalhWgoingWW\WcWWgreaterWgroupWWWgroupingsWhandleWWveWWhandovereWgWqWyWWWW'W6W\WmWwWWWWWWWWhandoversignalingprocedureaspartofhandoverexecutionawVhandover-prepareWhandovermodeWhandoverswWhandoverstatusWhappenTWhasW$WmWWWhavelWWWW\WrWwWhavingQWhavingtexualdescriptiononthosefiguresismorepreferablQVhdrzWWheaderrWWW*WfWWheadertypeWheadingWWWhelpmWhenceWhereWWherewegiveaproposalforaddingseveralcommandprimitiveVheterogeneous{W|WWhighermWqWwWWhighlight Whih:WhistoryWho2WhomeWhomegeneous{W|Whomegeneousandheterogeneous{VOIEZhuangF Hongcheng^Technical, Non-binding_159`36a8.3.4.2b7.4.12bAMIH_Handover_Commit primitives/messages are used to communicate remote MIHF which candidated network and PoA will be selected to handover. Extend these primitives/messages to improve handover delay. Please see: "21-06-0808-00-0000-Use MIHF to improve handover delay.ppt"cMIHF can facilitate Network Detect and Selection. In addition, it should help to further improve handover delay, especially for heterogenous handover.d2293g2211k wDeferred 2006/11/16 2006-10-17EZhuangF Hongcheng^Technical, Non-binding_159`36a8.3.4.2b-0808-00-0000-Use MIHF to improve handover delay.ppt"cMIHF can facilitate Network Detect and Selection. In addition, it should help to further improve handover delay, especially for heterogenous handover.d2293g2211k wDeferred 2006/11/15 2006-10-17EZhuangF Hongcheng^Technical, Non-binding_159`36a8.3.4.2bOEJunxiangFGuoGMember^Technical, Non-binding_162`47a8.4.1boCurrent Link Identifier(12) and New Link Identifier(13) should be combined into one type: Link Identifier(12).ckCurrent Link Identifier(12) and New Link Identifier(13) are duplicate types, they have the same definition.d2362g4640v.Each parameter needs a separate TYPE value....wRejected 2006/11/16 2006/10/2026EZhuangF HongchengGObserver^Technical, Non-binding_121`16a7.4.12bAMIH_Handover_Commit primitives/messages are used to communicate remote MIHF which candidated network and PoA will be selected to handover. Extend these primitives/messages to improve handover delay. Please see: "21-06-0808-00-0000-Use MIHF to improve handover delay.ppt"cMIHF can facilitate Network Detect and Selection. In addition, it should help to further improve handover delay, especially for heterogenous handover.d2293g2211k current threshold configu-binding_79 /170 /180/168da$Z bAWe suggest the following amendments: 7.4.10.4 MIH_Handover_Initiate.confirm 7.4.10.4.4 Effect on receipt On receiving the primitive the entity which originally initiated the handover request may decide to carry out the handover or abort it based on the primitive. If the recipient of the primitive is a client upper layer and in case the handover is to be executed, it may also provide information about selected link identifier on the selected network with a MIH Handover Commit message. If thBe recipient of the primitive is a client upper layer and in case the handover is to be aborted, the entity which originally initiated the handover request may decide to intiate once more handover to another candidate neighbor PoA.This procedure may repeat untill handover initiating succeed or utill some criterias are satified, e.g. timer has expired or up to maximum retry times. 7.4.11.3 MIH_Handover_Prepare.response 7.4.11.3.4 Effect on receipt After receiving the response,if the queriedF cAIn current draft, MN can discover and obtain information of a list of neighbor PoAs, so when handover decision is made MN have mutiple choices of target PoA to handover to, but the current draft does not allow this case happen: e.g., when MIH_handover_Intitate.reponse, MIH_handover_Prepare.response, or MIH_handover_Commit.response are received and they include parameters indicating handover failure, then the handover process will be ceased finally,this does not allow the MN or servingB PoA to perform handover to another suitable candidate neighbor PoA. So it will reduce handover efficiency and cause comparatively higher handover failure ratio.d2413g4635vhandover to another candidate neighbor PoA.This procedure may repeat untill handover initiating succeed or utill some criterias are satified, e.g. timer has expired or up to maximum retry times. 7.4.11.3 MIH_Handover_Prepare.response 7.4.11.3.4 Effect on receipt After receiving the response,if the queried<IbcrossWcsWWmWoWqWWcurrencyHWcurrent3W<WCW"W7WZW\WWWWWWWcurrentlinkidentifier12andnewlinkidentifier13shouldVcurrentlinkidentiferOWcurrentlinkidentifieWWcurrentlysWdWjWdmihnetsapthisrepresnetstheabstractmedia-independentjVd2.0WWdashed>W?WdataNWWWWWWEWFWjWkWqWWWdataonlywhenstatus0EVdatabase7WdecidelWWWW4##`!nada" 2"golmie!nada#nada$ 4$golmie#nada%)&2($&nada'ohba %)'golmie&nada(nada)%2)golmie(nada*P+$0+nada,*P,golmie+nada-t.$.nada/-t/golmie.nada05i1r)$1Fa7.4.11W7.4.11xV7.4.127.4.12.1.27.4.12.4.2Ӄ7.4.12.4.4W7.4.14u7.4.14.1.17.4.14.1.2ՃփB7.4.14.1.37.4.14.1.47.4.14.2.17.4.14.2.2׃C7.4.14.3.47.4.14.4.2D7.4.15.3.27.4.15.4.2E7.4.2.1.27.4.2.2.27.4.3.1.27.4.3.1.347.4.3.2.27.4.4.1.157.4.4.1.27.4.4.2.27.4.5.1.27.4.7.1^7.4.7.1.2ッ7.4.7.1.3'7.4.8.1.4΃7.4.9.1.27.4.9.27.4.9.2.2σ7.5كS7.6.2.3.47.6.2.4.37.6.47.6.5.1.2F8.1ۃ܃8.2a8.2.1ރ8.3)0h8.3.18.3.1.18.3.1.2݃㟃8.3.2v{ Gd㱃8.3.3.1bH8.3.3.2I8.3.4߃J8.3.4.1*8.3.4.211p8.4.1.12\8.4.1.208.4.1.30%8.4.1.328.4.1.35nW8.4.1.358.4.1.36nV8.4.1.36nW8.4.1.7c8.4.1.9d8.5o8.5.1MWEbquotationXWrWWr1RWr2RWr3zWr4RWr5RWradiusWWrangerWWWUWWrateNWWratesWratherWrdf^WWWre-do6Wre-order$WZWre-orderlinkdetectedintable17tothesameorderasintZVre-orderreferences$Vre-registraion$Wre-registration+W.WreachesWread@WAW"Wreadability<WWWreasonqWreceipientTWreceiptTW$WWreceive4WreceivedWcWreceivesWreceivingdWWWrecipientWrecognizeUWrecomendWrecommendWrecommendthatitisclarifiedthatfunctiondiscoveryatl3VredefinevWredrawWredrawthefigureandfixfontsVreducingYWredundantWreferrWxWWWWreferenceMW]WWWW WzWo ishizu|c}%p}ishizu~|c~kentaro(GEShu Guiming/Guo JunXiang GOther^Technical, Non-binding_45`4a6.2.5 bAHere we give a proposal for adding several command primitives for queriy about the registered events. Please refer to 21-06-XXXX-00-0000-Support for query of the registered event at MIH Layer and Link Layer.ppt. 6.2.5.1 MIH Commands The following set of MIH Commands are defined. Table 4---MIH Commands ---------------------------------------------------------------------------------------------- Table 4---MIH Commands ---------------------------------------------------------------------------------------------- communication systems. During handover procedure, there are some Event indications generated by MIH_Handover primitives/messages to some specific MIH users. How to indentify or indicate different MIH users?d355g2223g2223( bAThe required messages should piggyback MIH User ID or MIHF puts MIH User ID in the MIH frame header. For example: MIH_Handover_Initiate.request ( SourceIdentifier, DestinationIdentifier, CurrentLinkIdentifier, SuggestedNewLinkList, SuggestedNewPoAList, HandoverMode, OldLinkAction, QueryResourceList, QueryResourceFlag, MIHUserIDList ) Or use MIHF Variable Load: Type Length Value TYPE_HDR_TLV_MIH_user_ID Variable MIHF user ID that identifies which MIB'H users need to process this message @Az 33@  M 33   33 zcAMIHF can be used to exchange messages by MIH users between different communication systems. During handover procedure, there are some Event indications generated by MIH_Handover primitives/messages to some specific MIH users. How to indentify or indicate different MIH users?d2355g2223ng_159EAjayFRajkumarGMember^ Editorial_26a5.5b4Remove the text "(Option 1)" from the figure captionc\The figure caption contains text indicating "(Option 1)" but no other options are presented.d2074g2221 2006/11/16 2006/10/235EAjayFRajkumarGMember^Technical, Binding_56`59a 6.3.5.3.2bRemove both #5 and #6cIn Table 11, one of the Method has been stated to be IEEE 802.11 WLAN Access Point (#6). All other methods are access agnostic whereas this one is access specific. Also, the IE is to define PoA location which is what Cell and AP are.d2175g2222wRejected 2006/11/16 2006/10/2311d285g2328 2006/10/31 2006/10/20EAjayFRajkumarGMember^ Editorial_26a5.5b4Remove the text "(Option 1)" from the figure captionc\The figure caption contains text indicating "(Option 1)" but no other options are presented.d2074g2221 2006/10/31 2006/10/235EAjayFRajkumarGMember ccThis process may be carried out once the core elements of the IEEE 802.21 standard are developed. d2020g2240vDelete this sentencewAccepted-Modified 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_7`31a3b|Horizontal Handover - Handover associated with a link switch between homogeneous points of attachment (e.g., WLAN to WLAN). cHorizontal handovers This involves MNs moving between access points of the same type (in terms of coverage, data rate and mobility), such as, UMTS to UMTS, or WLAN to WLAN. Rationale: Improve consistency across definitions.d2025g2241vHorizontal handovers This involves MNs moving between PoAs of the same link type (in terms of coverage, data rate and mobility), such as, UMTS to UMTS, or WLAN to WLAN.wAccepted-Modified 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_7`38a3cmie.nada05i1r)$1:bthresholds WWthroughWWqWsWWWthroughaninsecureportwouldVthroughinsecureportswouldVthroughouthWWWWpWthuseWgWmWWtimeaWgWWtimerWtimesWWtitlegW W"Wtitles WG'GnadaHF'HgolmieGnadaI8fJ(JnadaKIfKgolmieJnadaL#M(pMnadaNL#NgolmieMnadaO)P* PnadaQO)QgolmiePnadaR&&S*0SnadaTR&TgolmieSnadaUgolmie'nadaVnadaW&IWgolmieVnadaX Yp1YnadaZX ZgolmieYnada[jameshan\hepworth]k]scobviousWWoccurWoccursWoctectsmWoctetEWHWW9WFWoctetsW<Wof'W1W3W9WBWCWDWHWJWKWLWMWNWOWPWQWZW[W^W_WbWcWgWjWlWmWnWpWrWuWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWW W!W"W&W)W0W6W7W8W9W;W<W=W>W?WCWDWEWLWNWPWSWUWVWXWZW[W\W^W_WdWfWgWhWkWrWsWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWbtlvsGWQWMWeWto'W0W1W4W5W7W8W9W:W;W<W=W>W?W@WAWFWGWHWMWRWSWTWVWZW\W_WdWgWhWlWoWrWsWxWzW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWW W!W"W&W'W*W+W-W.W1W6W7W9W:W<W>WCWDWEWFWJWMWNWRWSWTWVWYWZW[W\W]W^W`WaWgWkWlWmWoWqWrWtWwWxW{W|Wada:golmie_ccurrentaccessrouteraWcurrentlinkidentiferOWcurrentlinkidentiferandtargetpoaidentifieraremissinginOVcurrentlinkidentifieWcurrentlypW W`WWcurrentlythedraftdoesnotspecifyalimittothemihmess`Vd02Wd02.00WdataWWWWWWFWUWZWjWkWoWWWWWWWdatabase7Wdate9Wde-registrant5Wde-registrantwouldbeanmihusernotmihfunction5Vde-registration/WdealWdecided WtWdecideslWlWWdecision WWdecisionsWdecodeHWdecodingiWdecribesWdeepWdefensiveXW2"golmie!nada#nada$ 4$golmie#nada%)&2($&nada'golmie&nada(nada)%2)golmie(nada*P+$0+nada,*P,golmie+nada-t.$.nada/-t/ bJ_RegisteredEvent_Discover.request | MIH-Layer query for the registered Link-Events . --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 4 | Link_RegisteredEvent_Discover.confirm | Link -Layer response for queriy about the registered Link-Events. --------------------------------------------------------------------------------Kq------------------------------------------------------------------------------------------------------------- - @Aj 33Y ff 33M  33  33  33  E 33K  33{  33  33 Z bE#ss to another candidate network. This procedure may repeat untill handover process succeed or utill some criterias are satified, e.g. timer has expired or up to maximum retry times. The network recipient may determine that the handover procedure is in progress to the intended network. @A 33%  33K 33L  33h 33 m  33 33  33V 33Y   3 4  33P Q 33 G 33I n 33  33crocess and begin setting up of new layer 2 connection in case the handover is to be performed. In case of the handover is to be aborted, the client recipient may initiate once more handover initiating proce9a8.3.5:K8.4mL8.4.18.4.1.11p8.4.1.12\8.4.1.208.4.1.30%8.4.1.328.4.1.35nW8.4.1.358.4.1.36nV8.4.1.36nW8.4.1.7c8.4.1.9d8.5o8.5.1MWgolmienada€wBsU€nadaB€golmienada€nadas€golmienada€nada(q€golmienada€nada8€golmienada€nada+C€golmienada€nadaWZ€golmienada€nadaX€golmienada€nadaT€golmienada€nadaZ€golmienada€nadaR€golmienada€nadaX€golmienada€nada}€golmienada€nada}F€golmienada€nada}J€golmienada€nadaځ €golmieⴃⵃada bj--------------------------------------------------------------------------------------- | NO. | MIH Command | (L) ocal, | Remote Direction | Comments | | |(R) emote | | -----------------------------------------------------------------------------------------------------------------------------------------------------------C---------------------------------- | 1 | MIH Get Status | L, R | Network -> Client | Get the status of links -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ~ ~ ~ ~ ~ -----------------------------------------------l bAThe new definition of MIH_Scan confirm primitive is as follows: MIH_Scan.confirm (SourceIdentifier, DestinationIdentifier, Scan Response Sets, Scan Not Detect Links) Name Type Valid Range Description --------------------------------------------------------------------------------------------------------------------------------------------------------B------------------------------------- Source Identifier Identifier Any valid individual or group identifier The identifier of entity where the request is initiated. This field may be optionally ,~busesWWWWWWnWWusing>W?WWWW8W_WqWrWvWWWutilizedwWutillWvalidJWWUWWvalueFWGWJWKWLWOWQWnW{WWWMWVWeWWWvaluesJWoWWWvariabelfWvariablePWWWWvariousWvelidityMWvendor\W_Wvendors_WversionWWverticalWverticalhandoverhandoverassociatedwithalinkswitchbetVvery~WvisitedWvisitingWwantsTWWwasEWWW:€golmienada€nadah€golmienada€U:€nadaU€golmienada€WA€nadaW€golmienada€golmie❃;nada€nada:a€golmienada€QE€nadaQ€golmienada€nada bF------------------ | 11 | MIH_RegisteredEvent | L, R | MIH Layer response to the MIH user for the query about the registered MIH-Events. | | _Discover.confirm | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 6.2.5.2 Link Commands The following set of Link Commands are defined. G Table 5---Link Commands --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | NO. | 9EEleanorFHepworthGMember^Technical, Binding_152a8.1bRecommend that it is clarified that function discovery at L3 can take capabilities into account as this can be beneficial to L3 solution. L28, P152: add at end of paragraph "the function discovery mechanism may take capabilities into account."networks and PoAs in the report. For example, a client may not want to retrieve any information about 802.11 networks. Or, a client may only want to retrieve information about UMTS networks. 0d2191g4671 2006/11/15 2006/10/20EEleanorFHepworthGMember^Technical, Binding_152a8.1bRecommend that it is clarified that function discovery at L3 can take capabilities into account as this can be beneficial to L3 solution. L28, P152: add at end of paragraph "the function discovery mechanism may take capabilities into account."al to L3 solution. L28, P152: add at end of paragraph "the function discovery mechanism may take capabilities into account." bO<------------------------------------------------------------@@A 33|  33 3333 333 3333  33 N  3333 c 3333  33  33?  33    33B  W  33cThe MIH_Scan confirm primitive in the current draft can not support multi-link scan request. It is also necessary to amend this primitive to provide more information in order to facilitate making handover decisions. d2285g2328wAccepted-Modified 2006/11/16 2006/10/20 is initiated. This field may be optionally l bcA In current draft, we have "MIH_Event_Register.request" and "Link_Event_Register.request " for MIH Users and MIHF to register events they concerned at MIH Layer and Link Layer, and by the primitives of "MIH_Event_Register.confirm" and "Link_Event_Register.confirm" , MIH Users and MIHF can know what events have been registered successfully. For the convenience of the implement of the MIH, the query methods for the registered events should be provided also. Through the query methodBs, MIH User can query its registered events from MIH Function and MIH Function can query its registered events from Lower link layers. xd2125g2325iYoshihiro Ohbaj{This is not needed because the entity that has subscribed for particular events is supposed to keep the subscription state.mRejectedvAgree with Yoshi's reasoningwRejected 2006/11/16 2006/09/22€ATable@A  33---------------------------------------- bC left empty if the command is local --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Destination Identifier Identifier MIH_LOCAL, MIH_REMOTE The destination identifier of request or D response. This is the identifier of local or peer MIH Function -------------------------------------------------------------------daGcwithoutJWKWLWvWWWWWWwithouttheabovedetailstheiewouldbehardtouseJVwlanWWWwonkyWwordXWYWU€nadaB€golmienada€nadas€golmienada€nada(q€golmienada€nada8€golmienada€nada+C€golmienada€nadaWZ€golmienada€nadaX€golmienada€nadaT€golmienada€nadaZ€golmienada€nadaR€golmienada€nadaX€golmienada€nada}€golmienada€nada}F€golmienada€nada}J€golmienada€nadaohba  €golmieⴃⵃnada€nada %€golmienada€nada€da bH Link Command | Comments --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 1 | Link Configure Thresholds | Configure the thresholds for various link layer events such as Link Going Down . ----------------------------------------------I---------------------------------------------------------------------------------------------------------------------------------------------- | 2 | Link Get Parameters | Get parameters measured by the active link, such as SNR, BER, RSSI --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 3 | Link >bentitiesWmWrWWentity>W?WWW7WWWWWentriesPWentryJWW9WmWequivalent]WerrorpWWEWWerrorsEWesqWespeciallydWessidFWestablishW'Wetc2WWWmWWWZb21-06-xxxx-00-0000-sW215PW22WW24,W243\W244\W25WW W25-mihf W W253FW26oWrWzWWWW2nd@WAW3oWyW|WWWWWW WWWWW!W.W4W9W:WFWMWgWmWnWrWWWWW3framelossratebeforeretransmissionV30oWssionV30oWoWDQDxieECgEqiaobing@DxieFAGRGxieHFAHqiaobingAGxieIxieJ@eJqiaobingBIxieKxieLaLqiaobingCKxieMNdNxieOMOqiaobingDNxiePPQWSiUeQxieRPPRqiaobingEQxieSxieTPWTqiaobingFSxieUxieVPiVqiaobingGUxieW$XDZI\f^fXxieYW$YqiaobingHXxieZxie[WD[qiaobingIZxie\R@lbACEGIKMO@@cA@wckA@c@iz@c@@_@bWcA`kO@cAcA7bAjAcbjAccT@@.@QcAC@cA@^bAD@qc@cA\C@ m@@;bBvE@^@v@^@@ more handover to another candidate neighbor PoA.This procedure may repeat untill handover initiating succeed or utill some criterias are satified, e.g. timer has expired or up to maximum retry times. 7.4.11.3 MIH_Handover_Prepare.response 7.4.11.3.4 Effect on receipt After receiving the response,if the queriedEAjayFRajkumarGMember^Technical, Binding_55`1a 6.3.5.2.3bSpecify two cost values, one for home network users and one for visiting network users or a distinct cost value for each of all possible visited networks (based on negotiated roaming agreements or SLAs).chich is what Cell and AP are.d2175g2222 2006/11/15 2006/10/2311EAjayFRajkumarGMember^Technical, Binding_55`1a 6.3.5.2.3bSpecify two cost values, one for home network users and one for visiting network users or a distinct cost value for each of all possible visited networks (based on negotiated roaming agreements or SLAs).cdecisions. d2g2328 2006/10/26 2006/10/20EAjayFRajkumarGMember^ Editorial_26a5.5b4Remove the text "(Option 1)" from the figure captionc\The figure caption contains text indicating "(Option 1)" but no other options are presented.d74g2221 2006/10/26 2006/10/235EAjayFRajkumarGMember^Technical, Binding_5625 bM------------------------- Scan Not Detect Links LINK ID N/A The link type, identifier and address of the link that exists in the previous N scan but can not be detected in the current scan. --------------------------------------------------------------------------------------------------------------------------------- bKdent (optional) link information defined in related SDOs. ---------------------------------------------------------------------------------------L------------------------------------------------------------------------------------------------------ The parameter Scan Not Detect Links is defined as: Name Type Valid Range Description -------------------------------------------------------------------------------------------------------------------------------------------------------------------- bI The link type, identifier and address of the scanned link. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Signal Strength J Integer N/A Signal strength of the scanned link. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Media Dependent Information N/A N/A The extended media depen bG scan but can not be detected in the current scan. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The information of detecteHd links includes: Name Type Valid Range Description --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Link Identifier LINK ID N/A  bE-------------------------------------------------------------------------------------------------------------------------- Scan Response Sets Response for requests N/A List of discovered links and related information. ----------------------F----------------------------------------------------------------------------------------------------------------------------------------------------------------------- Scan Not Detect Links STRING N/A List of links that exist in the previous ~brequiredjWWWrequirementsWWreservedWWreserved9-31VresidesWresourceWWWresourcesWWWWWrespWrespectivelyWWfWoWmWWresponse'WqW{WWWW WWDWWWWWWresponsesnWrestUWrestricted{WWresultW$WMWresultssWretitleWretitlefigure25transportofmihframeinieee802l2dataVretransmissionWWretrieval'WWretrieveWretrievedEWWretryWreviewWxWreviewsection8.5.2andupdatealltypevaluesasdefinediVrevisekWkW9,jthe]WaWlWnWoWsWthetextinsection5.4.3isaboutinformationrepresentatioVthetwocategoriesareneededforextensibilityieextendedVthereWWthis^WWWWthisisnotneededbecausetheentitythathassubscribedfoVthisistheformalbasicschemadefinitionandneedstobedVthisistoomedia-specificanddoesnotworkforothermediaVthoseWtlv[WtlvsWto]W^WWWWWWtooWtransaction-iddWtransaction-idcandeterminewhichmessageisbeingacknowledVtransmissionWtwoWdWupdatedWusableWuseWusedWuserWuseridentificationinformationcanbeobtainedbyothermeaVusing^Wvariable*WwgWwhich[WdWwhileWWwithoutWworkWxml[Wxml-representedWyes]Wyes16and17aretherightreferencestordf]Vkbe1Wbutkvin3W4W9W=WUWcWkWlWsWtWvWwWxWyWzWWWWWWWWWWWWWWWWinfigure3changezVinfigure5kVinsection7.3.20.2removerssisnrc/iberdataraterowenVinsection7.3.7.2andthetablebelowitchangelinkparametVinclude[W9W]WWWincludeappropriatedefinitionsforotherlinksaswellVincluded_WiWincompleteW)jformatWframeWWframework[W^WfromWdWfunctionlWWWW3WgNWWWhavelWheader*Whow[WiWid*WidentificationWiesWifdWWimplementationsWinlWW*W3WWWWintable16thereisnomihlinksapprimitiveusablefortrVinclude[W!Wincludemihnmsinitializeoperationaspartoflinkcommand!VinconsistencyWindicatedNWinformation[WWWinitialize!WinstanceslWintoW3WNWipNWis[WWWWW*W3WNWdWWWWkeepWkindNWknowlWlayer3Wline^WW3WNWlink!WWlistlWmappingWmaylWmeansWmediaWmedia-specificWmessagelW*WdWmessageslWdWWmessgeWmethodslWNWmihlWWWW!W3WWWLf{l) none needed 2006/11/16EGolmieFNadaGMember^ Editorial_15`18a5.1.3bWReplace with "and how well they meet the application quality of service requirements. "cmNot sure what is meant by the statement: " and their potential fulfillment as well as their relation to ...""d2044g2308{l) none needed 2006/11/16p € p؃كڃۃ܃݃ރ߃  !"#$%&')*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~〃ぃゃッ㄃ㅃㆃ㇃㈃㉃㊃㋃㌃㍃㎃㏃㐃㑃㒃㓃㔃㕃㖃㗃㘃㙃㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃ`LmcJMore clarifying text is required to show proper relationship between SAPs.d2083g5000wAccepted 2006/11/16MarkednERonny^Technical, Non-binding_33`9a5.6.1bADelete "5.6.1.3 M_SAP" sub section. Delete line 19 and 20 on page 69. 3) M_SAP : The MIHF uses this SAP for interfacing with the Management plane of the 802.16 network. @A>  33H    33>cM_SAP is not defined for multi interface management by 802.16 working group. Since there is neither functionality nor primitive is defined in 802.21 specification, it is right to delete M_SAP from 802.21 specification. d2097g5001i Vivek Guptak802.21 is not using M_SAP...mAcceptedwAccepted 2006/11/16MarkedoERonny^Technical, Binding_34`1a5.6.2}^EQiaobingFXieGMember^Technical, Non-binding_64`56a6.3.7.1b\Clarify the above issue. Make clear where "the RDF schema definition for MIIS" is described.cUnclear which part of 6.3.7.1 is normative and which part is example. Line 59 says "This section gives an example..." but line 23, page 65, says "... the RDF schema definition for MIIS" which sounds normative. d2199g4729iYoshihiro OhbajZChange line 59 to: "This section gives a schema using Resource Description Framework...."k mAccepted-ClarifiedvbChange as follows: "This section describes a schema using Resource Description Framework format "wAccepted-Modified 2006/11/16 2006/10/20_EQiaobingFXieGMember^Technical, Binding_66`36a6.3.7.2bd-Modified 2006/11/15 2006/10/20das€.P/G€/das0.P€0subirj/das€152X€2das315€3subirk2das€4das5q€5subirl4das€6das72deEKenichiFTaniuchiGMember^ Editorial_55`48a 6.3.5.2.4bFix it.c%"appliacble" should be "applicable" .d2169g2241iVivekj!Editor: Please run spell-checker.mAccepted 2006/11/16 2006/10/21EKenichiFTaniuchiGMember^Technical, Binding_59`6a 6.3.5.3.6bMChange TYPE_IE_POA_IP_CONFIG_METHODS to TYPE_IE_POA_IP_CONFIGURATION_METHODS.cTYPE_IE_POA_IP_CONFIG_METHODS is defined as TYPE_IE_POA_IP_CONFIGURATION_METHODS in Table 6 in page 49. This should be corrected.d2181g2242v(Please change this all across the draft.wAccepted 2006/11/16 2006/10/21FIGURATION_METHODS.cTYPE_IE_POA_IP_CONFIG_METHODS is defined as TYPE_IE_POA_IP_CONFIGURATION_METHODS in Table 6 in page 49. This should be corrected.d2181g2242v(Please change this all across the draft.wAccepted 2006/11/15 2006/10/21TFdÄ1Ä1Ä1Ä1Ä1Ä1Ä1Ä1Ä1Ä1!Ä1"Ä1#Ä1$Ä1%Ä1&Ä1'Ä1(Ä1)Ä1*Ä11Ä12Ä13$Ä14ZÄ15Ä16Ä17Ä18(Ä19vÄ1:)Ä1AsÄ1BÄ1CyÄ1D+Ä1EÄ1FÄ1GÄ1H`Ä1I"Ä1JÄ1QÄ1RÄ1SÄ1TÄ1UÄ1VÄ1WÄ1XÄ1YÄ1ZwÄ1axÄ1b<Ä1cÄ1dÄ1e|Ä1f4Ä1gzÄ1hÄ1i[Ä1j7Ä1qÄ1rÄ1sÄ1tÄ1utÄ1vuÄ1wÄ1xÄ1y{Ä1zÄ1Ä1jÄ1Ä1Ä1Ä1|Ä1kÄ1,Ä1Ä1lÄ1Ä1Ä1Ä1mÄ1Ä1Ä1Ä15Ä1}Ä1}Ä1!Ä1Ä1Ä1=Ä1Ä1Ä1bÄ1nÄ1pÄ1oÄ2`Ä2Ä2Ä2YÄ2jÄ2XÄ2Ä2Ä2Ä2Ä2Ä2Ä2Ä2Ä2Ä2Ä2bbetwenWbi-directionWbimapQWbitRWSWWWWWWWWWWWWbit5&WbitmapWWWWWWbits WVWblockWblueprint^WbothZWeWWWboundarydWJWbriefWbroadcasWbroadcastWqWWWbroadcastingWWbroadcastingmihcapabitydiscoverresponsemessagemayinclVbsmWbulletWbutWlWWWWby4W5W_WlWyWWWWWWWW WaWbWmWoWqWrWwWWWWWWbyteiWbytesWcmWwWcalledjWSWcancWlWxWWW W$W]W^W_WaWdWoWwWWWWWWWWWWcandicateWcandidatesWWWcandidatedWWW;feder€`peretz~Kfeder€afederbNQ€bperetz1_cprotocolstatediagramisalwayshelpfultounderstandthepwVprotocolsWWdhong€ ! %€!das"kim €"subire!das€#das$Q€$subirf#das€% &)€&das'jee% €'subirg&das€(H)qW€)das*(H€*subirh)das€+",(0Cc€,das-+"€-subiri,das€.P/E4FG€/das0.P€0subirj/das€1$l&'526nX€2das315€3subirk2das€4das5q€5subirl4das€6das7ohba2dTEVivekFGuptaGMember^Technical, Binding_117`43a7.4.11bDefine resources in media specific ways. Give examples for 802.11/802.16 etc. 802.11: Specify TSPECS 802.16: Specify QoS classes cdIn MIH_Handover_Prepare primitives QueryResourceList and AvailableResourceList are not yet defined. d2291g2211v8Include appropriate definitions for other links as well.wRejected 2006/11/16 2006-10-23EVivekFGuptaGMember^Technical, Binding_185`1aAnnex-A1bsMake all the flow diagrams follow a single template and make them consistent (labels/terminology..representation). cv The handover flow diagrams in Annex A1 use inconsistent representation and terminologies (fonts/labels) and messages.d2387g2225vThe template document: 21-06-0822-02-0000 has been finalized. The other flows need to be updated based on these flows. Contribution no: 0821, 0656-02 (ppt), 0813-01, 0793-00 need to be updated based on the updated template.wAccepted-Modifiednada€.blinkacommunicationfacilityormediumoverwhichnetworknVlink-eventsWlink-specificgWlinkidentifier\WlinkparameterlistWWUWlinksgWWWlinktype\WlistGWPWUW_WlWnWWWWWWWWWPWgWWWWlistedWlistsWlittleWloadWlocalWWjWWWlocallyWlocatedlWqWrWlocationWlossWZWlowWlower>W?WWWWWW7& 9gvwAccepted 2006/11/16 2006/10/23A 33>rces in media specific ways. Give examples for 802.11/802.16 etc. 802.11: Specify TSPECS 802.16: Specify QoS classes cdIn MIH_Handover_Prepare primitives QueryResourceList and AvailableResourceList are not yet defined. d291g2211ber^Technical, Binding_117`43a7.4.11bDefine resources in media specific ways. Give examples for 802.11/802.16 etc. 802.11: Specify TSPECS 802.16: Specify QoS classes cdIn MIH_Handover_Prepare primitives QueryResourceList and AvailableResourceList are not yet defined. d291g2211plaination should be added to each section.g2245 2006/10/26 2006/10/23EVivekFGuptaGMember^Technical, Binding_117`43a7.4.11bDefine resources in media specific ways. Give examples for 802.11/802.16 etc. 802.11: Specify TSPECS 802.16: Specify QoS classes cdIn MIH_Handover_Prepare primitives QueryResourceList and AvailableResourceList are not yet defined. d291g2211/ \bA1. Should only have two definitions one for current (either 12 or 244) and one for new (either 13 or 243) 2. Remove LinkType since it already exists in LinkIdentifier TLV. The same comment applies to the following messages: - MIH_Link_Up Indication - MIH_Link_Going_Down Indication - MIH_Link_Detected Indication - MIH_Link_Parameters_Report Indication - MIH_Link_Event_Rollback Indication - MIH_Link_Handover_Imminent Indication - MIH_Link_Handover_CompleteB Indication ct of each other. cSection seems to say: first connection with PoS co-located with PoA causes/implies a second connection to non-PoA PoS. The two connections should be independent of each other. d58g2298 2006/10/31\EUlises^Technical, Binding_166`9a8.4.1.12b€golmienada€ EdaQ€golmienada€nada.F€golmienada€9H€nada9€golmie2: ScASection reads: "Primitives are a conceptual representation of functions that are called across protocol layers within the same communication node." The underlined part is not true in general, e.g. primitives associated with MIH_SAP.@A>  33o  33  33>d2313g2290voRephrase to: "Primitives are a conceptual representation of functions that are invoked across protocol layers."wAccepted-Modified 2006/11/1690 2006/11/14of functions that are called across protocol layers."cASection reads: "Primitives are a conceptual representation of functions that are called across protocol layers within the same communication node." The underlined part is not true in general, e.g. primitives associated with MIH_SAP.@A>  33o  33  33>d2313g2290 2006/10/310/31.+ 2006/11/16 2006-10-23(i.e. discovering the number and type of links that a node supports), this document proposes modifications as explained in document 21-06-0792-00-0000-LinkTypeDiscovery 2. The document 21-06-0792-00-0000-LinkTypeDiscovery proposes modifications to allow an MIH node to list the Events it supports while at the same time specifying the type of links that support the Events (i.e. certain links support common Events while others support specific Events). 3. The Bdocument 21-06-0792-00-0000-LinkTypeDiscovery. proposes modifications to allow an MIH node to list the Commands it supports while at the same time specifying the type of links that support the Commands (i.e. certain links support common Commands while others support specific Commands) 4.The document 21-06-0792-00-0000-LinkTypeDiscovery proposes modifications to allow an MIH node discover all the services that its peer support for all link types. Thus only one message will be necessary to cforaparticularnetworkorsetofnetworksVforaparticularpoaorsetofpoasVforalll2servicesmihnetsapusesthemihlinksapVnada€nada3€golmienada€nadaW€golmienada€nada7D€golmienada€h3€nadah€golmienada€nadaIH€golmienada€$r5€nada€golmienada€:HS6€nada:€golmienada€nadah€golmienada€U:€nadaU€golmienada€WA€nadaW€golmienada€golmie❃;nada€nada:a€golmienada€ EQ€golmienada€nada.F€golmienada€9H€nada9€golmiecitsnotclearwhyack-req/ack-rspareneededVitselfWjitterWWWWjust3W9WFWWWkeyWWkindBWNWgWkinda1WknowcWdWWdWgWWWWknowsWl2WWWW WoWWWWWl3WWWWW WoWWWWl3mpWl3mpmissinganmVl4WlabelingWlackWlacksRWSWlargeWlastWz`bimmediateWimminenteWW\WimpleWimplementation W^WWimplicitlyWimproveWWWin'W4WCWDWMWWWXWYWZW_W`WeWfWiWjWkWlWnWoWpWrWwWxWyW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWW!W"W)W+W,W-W.W0W1W2W4W8W9W:W=WEWFWMWNWVWZW\W^WfWgWhWiWlWmWqWrWsWuWwWxWzWWWWWWWWWWWWWWWWWWW€nadaohba  €golmieⴃⵃnada€nada %€golmienada€nada€da rbcnformation element range "0x00000001 - 0x000000FF" are the headerspecific TLVs. Reference to Table 32 is not correct since it is not the TLV encodings of core header specific IEs. d2153g2486wAccepted 2006/11/16 2006/10/23T4- Type identifiers for Information Elements@A> 33{   >ing_51`44a6.3.4bAReplace with the following text: Information element range "0x00000001 - 0x000000FF" are the core header specific IEs. Refer to Table 26 for TLV Encodings. Refer to Table 32 in Annex A3 - Type identifiers for Information Elements@A> 33{   >nge "0x00000001 - 0x000000FF" are the core header specific IEs. Refer to Table 26 for TLV Encodings. Refer to Table 32 in Annex A3 - Type identifiers for Information Elements@A> 33{   >dActextcontainsmanygrammaticalerrorsandneedstobefixedVtexthasnothingtodowithhandoverpolicyVtextstatesdifferentprotocolstacksareshowninfigure4VtextstatesthatusecaseandhandoverareintheappendixyVtexts"WtexualQWthanWCWDWGWNW€nadac€golmienada€E€nadaE€golmienada€R€nadaR€golmienada€pef€nadap€golmienada€nadae€golmieƒnada€nadaf€golmienada€GRc€nadaR€golmienada€nadaG€golmienadanadacgolmienadaJnadaJgolmienada:nada:golmienadaEEVivekFGuptaGMember^Technical, Binding_61`48a6.3.6bD Add mechanisms to retrieve iformation based on above query formats.cFor Information retrieval using TLV, client should be able to retrieve information: - for a particular network or set of networks - for a particular PoA or set of PoAs d190g2241 2006/10/31 2006-10-23EVivekFGuptaGMember specified. Figure 20 shows this information representation and tree hierarchy for different networks. "c;Add explanatory text for Figure-20. Fix font size as well. d143g2240 2006/10/31 2006-10-23Fig 20EVivekFGuptaGMember^Technical, Binding_61`48a6.3.6bD Add mechanisms to retrieve iformation based on above query formats.cFor Information retrieval using TLV, client should be able to retrieve information: - for a particular network or set of networks - for a particular PoA or set of PoAs d190g2241 2006/10/31 2006-10-23EVivekFGuptaGMember1;EVivekFGuptaGMember^Technical, Binding_196`1a Annex A-4b Either complete this table appropriately or delete it. If there is a need to define media specific primitives, then those need to be appropriately defined.ck Table has many cells that rae empty. Are there any new media specific primitives that need to be defined?d2405g2239wRejected 2006/11/16 2006-10-23Fig-35ose need to be appropriately defined.ck Table has many cells that rae empty. Are there any new media specific primitives that need to be defined?d2405g2239wRejected 2006/11/15 2006-10-23Fig-35ienada€U:€nadaU€golmienada€WA€nadaW€golmienada€golmie❃;nada€nada:a€golmienada€ EQ€golmienada€nada.F€golmienada€9H€nada9€golmie"cwhymihnetworkaddressinformationconfirmhasadifferentDVwhymihnetworkaddressinformationindicationhasadiffereCVwhymustamnsupportbothtlvandrdfquerytypeswhynotaVwihtoutdWwillTWtWWW;WZWdWWWWwindowGWwired]Wwireless]WWwith>W?WWWlWoWsW}W~WWWWWWWWWWWWWWW WWW"W$W&W)W0WMWSW[W^WhWuWWWWWWWWWWWWWWWwiththecurrentdraftidon'tseeanydifferentactionfor$VwithinSWcWdWWWW*0SnadaTR&TgolmieSnadaUgolmie'nadaVnadaW&IWgolmieVnadaX Y1YnadaZX ZgolmieYnada[jameshan\hepworth]]jOcaniyWanibsch-aaahiphmippdsnyVannex_WxWWWWWWWWannex2Wanother&WgWWWW@E YoshihiroFOhbaGMember^Technical, Binding_71`1a7.2.2.1bAdd them as System Management category primitives, with Desription of "Register with a remote MIHF" for MIH Register and "Deregister with a remote MIHF" for MIH DeRegister.cCMIH Register and MIH DeRegister primitives are missing in Table 15.d2227g2442wAccepted 2006/11/16 2006/10/23MarkedT15AE YoshihiroFOhbaGMember^ Editorial_92`32a7.4.1bFix it.remote MIHF" for MIH DeRegister.cCMIH Register and MIH DeRegister primitives are missing in Table 15.d2227g2442wAccepted 2006/11/15 2006/10/23MarkedT15AE YoshihiroFOhbaGMember^ Editorial_92`32a7.4.1bFix it.ster with a remote MIHF" for MIH DeRegister.cCMIH Register and MIH DeRegister primitives are missing in Table 15.d2227g2442wAccepted 2006/11/15 2006/10/23MarkedT15AE YoshihiroFOhbaGMember^ Editorial_92`32a7.4.1bFix it.t.3 2006/10/31 2006-10-23EVivekFGuptaGMember^Technical, Binding_54`1a6.3.5.1b c Need more definition/details on TYPE_IE_NETWORK_STANDARDS, TYPE_IE_NETWORK_SECURITY, TYPE_IE_NETWORK_QOS and TYPE_IE_POA_CAPABILITIES d2160g2236v no remedywRejected 2006/11/16 2006-10-23EVivekFGuptaGMember^Technical, Binding_59`41a 6.3.5.3.6b Delete thisc Why is TYPE_IE_POA_DHCP_ADDRESS needed? That is, why does MN need to know IP address of DHCP server? Shouldn't it be using DHCP protocol to discover the server's address? d2182g2237iRonnykTYPE_IE_POA_DHCP_ADDRESS is for IP address pre-configuration prior to handover. Without this IE, there is no way for MN to know DHCP server IP address before handover. ldn't it be using DHCP protocol to discover the server's address? d2182g2237iRonnykTYPE_IE_POA_DHCP_ADDRESS is for IP address pre-configuration prior to handover. Without this IE, there is no way for MN to know DHCP server IP address before handover. dicbeWWW&@;nada<:6J&>nada?=A?golmie>nada@GA&A hongchengnadaB@GBgolmieAnadaC D<'pDnadaEC EgolmieDnadaF'G'GnadaHF'HgolmieGnadaI8fJ(JnadaKIfKgolmieJnadaL#M(pMnadaNL#NgolmieMnadaO)P* PnadaQO)QgolmiePnadaR&&S*0SnadaTR&TgolmieSnadaUgolmie'nadaVnadaW&IWgolmieVnadaX Yp1YnadaZX ZgolmieYnada[jameshan\hepworth]]?vbycomment2190'VVbycomment2195VVbycomment2328Vbycomment2360LVbycomment2370qVbycomment2374V\Vbycomment2387V2VQVbycomment23956Vbycomment2407VVbycurrentdraftasitalreadydoesthingsthatwayVbyvote6vs6VbyteiWbyteorderingisdefinedbytransportsnotclearifthisneeiVc/iWcanlWmW]WwWcan'tWierarchy for different networks. "c;Add explanatory text for Figure-20. Fix font size as well. d2143g2240 2006/11/15 2006-10-23Fig 20EVivekFGuptaGMember^Technical, Binding_61`48a6.3.6bD Add mechanisms to retrieve iformation based on above query formats.cFor Information retrieval using TLV, client should be able to retrieve information: - for a particular network or set of networks - for a particular PoA or set of PoAs d2190g2241 2006/11/15 2006-10-23x;bnet2W=WWWW W W WWjWoWWnetworkFWiWsWtWyWWWWWW+W4W7W9W>WCWDWRWZWlWmWnWqWrWwW|WWWWWWWWWWWWWWWWWnetworkusingthemihprotocolVnetwork-initiatedgWWnetworksFWZW|WWWnetworks/poas'WWnewCWWWWWWW"W'W6W9W\W^WWWWWnewlinkidentifierWnihoWWnms3W!WpWno@WAW WWJWWnomiheventnamemiheventtypeAVnodelWsWyW~WWWW7WgWjWlWmWWWWnadaJgolmienada:nada:golmieq/&ctoWWWWW4Ptaniuchivkenichi taniuchitaniuchi kenichi taniuchitaniuchiWYkenichi taniuchitaniuchimpkenichi taniuchitaniuchimVkenichi taniuchitaniuchiXpkenichi taniuchikimreunahkimWkimSeunahkimkim@eunahkimykimeunahkimkim}Geunah kimeunah !kimkim%eunah kimkim&eunah kim*kimeunah kim*kimeunahkim*kimeunahkimjeon2hongseokjeon;E bB Information Elements are specified for each network supported by an operator. Thus in case of Operator_1, General Network Information is specified for both 802.11 and UMTS networks, while in case of Operator_2 it is specified only for 802.11 network. For each network supported by an operator there is a list of supported PoAs. For each PoA the PoA Information Elements are specified. Figure 20 shows this information representation and tree hierarchy for different networks. "c;Add explanatory text for Figure-20. Fix font size as well. d2143g2240wAccepted 2006/11/16 2006-10-23Fig 20EVivekFGuptaGMember^Technical, Binding_61`48a6.3.6bD Add mechanisms to retrieve iformation based on above query formats.cFor Information retrieval using TLV, client should be able to retrieve information: - for a particular network or set of networks - for a particular PoA or set of PoAs d2190g2241v/21-06-0827-01-0000-TLV-indicating-network-typesEcretrieve'WWWretrievesWreturnsWreverseWrevisionsJWrightDWWnWroamedWroamingGWWroleW WWrollback\WrouterNWrowWWWWWWrowsWWWrssiUWrttW WruleVWJWsYWsameeWiWmWWWWW5W>WEWLWSWfWyWWWWWWWW cbehorizentalintraV(Pjeonhongseokjeonbenjaminkohbenjaminkohkoh7:benjaminkohkoh\YbenjaminkohkohIgbenjaminkohkohIvbenjaminkohkoh:0benjaminkohkoh1&benjaminkohkohC benjaminkohkoh+benjaminkohkohIbenjaminkohkoh"benjaminkohkohN(benjaminkohbenjamin dkohmasahiro! ;kurodamasahiro" kurodaleejin#lee9Alee9jin$leeleeI8jin%lee%qlee%leemthc|The MIH states are needed for the correct operation of MIH protocol to allow peer MIHF entities to interact with each other.d2331g2217vsee 330w Superceded 2006/11/16 2006-10-23MarkediESoohongFParkGMember^Technical, Non-binding_193`1aAnnex A1b:See the updated flow charts in the 21-06-0530-00-0000.doc cSAdd a section for the example handover scenarios between 802.3 and 802.11 networks.d2399g2222w Withdrawn 2006/11/16 2006-10-23r a ceCrtain link type. Thus, if node supports two or more link types, an MIH peer would have to send two or more messages to discover the capabilities for each link. Ts. d373g2310 2006/10/31hESoohongFParkGMember^Technical, Binding_154`13a8.3bjThe proposed MIH protocol states are described in the document: 21-06-0xxx-00-0000-MIH_Protocol_States.doc4b802.2ah]W86#W9#WW9-31Wa4W5W7W?WCWEWFWHWMWUWWW_WcWlWnWsWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW+W4W@WEWFWNWSWTWWW[W^W_WgWlWmWqWrWWWWWWWWWWWWWWWWWWWWWWWWWWWWacouplethoughtsVafewexamplesofthekindofinteractionsthatmayexistbeVeric5 njedjouFQVohbaFyoshihiro6ohbaohbaQyoshihiro7ohbaP9aYohbaPyoshihiro8ohbaohba9yoshihiro9ohbaohbaa\ cCcfficult metric to use. Another question on PER is whether the reported value includes L2 retries. ?d2040g2235v`ITU: Y1540/1541. The current definitions in draft are based on ITU-T references (1540 and 1541).wRejected 2006/11/16 2006-10-23 to call it the "standard deviation of jitter" and specify equation for same so everyone has a common interpretation. b) for packet transfer delays, it would be helpful to specify the :"population". Maximum packet delay can Bonly be calculated given a certain population. That it, how long must a node measure before it can report the transfer delays? Also, how often do these transfer delays need to be updated? c) How is PER measured in a point-to-multipoint system (like 802.11 or 802.16); if packet is received in error, the packet cannot be attributed to a particular link--since the receiver typically does not know which bits are in error (i.e., error could be in MAC source address). So this could be a di5baddttional$WadequatelyxWadopt;W=Wadopt21-06-0779-poaipaddressiedoc;Vadopttheformatproposedin21-06-0778-01-0000-nstandards=Vafter<WxWcWmWoWqWWWagainWagainst6WagreementsWaidingwWair~WWalgorithmsWalignedJWalive+WallJWRWSWTWoW~WWWUWdWgWqWWWWqwcIn TLV location query, it seems there should be a way to specify a search radius. If the client knows their present location, it may want to determine the available networks within some distance (e.g. 100m). d2189g2233v[ Operators dont want to expose network topology and this may be a security risk as well....wRejected 2006/11/16 2006-10-23 a TLV method to make this specific query cA1The TLV-based queries in section 6.3 are driven from location. This makes a lot of sense, but it can be too restrictive as well. Is it assumed that a MN can always determine its location? What if it's not connected to a network/PoA when it needs to make a query (e.g., the MN is just booting up). 1d2188g2232 2006/11/15 2006-10-23EVivekFGuptaGMember^Technical, Binding_61`48a6.3.6b" Specify search radius in queries.iroMohba‚E Q")@‚ ohba!E‚!yoshihiroN ohba‚"r2cofWWWWWWWhba%V‚%yoshihiroP$ohba‚&ohba'R‚'yoshihiroQ&ohba‚(yoshihiroR'ohba‚)*0r‚*ulisesS)‚+P,‚,-+P‚-ulisesT,‚.olvera/g‚/ulisesU .olvera‚01+(‚1ulisesV0‚23C&‚3ulisesW2‚45.E‚5ulisesX4‚67W‚7ulisesY6‚89$‚9ulisesZ8‚:;)#‚;ulises[:‚<=C‚=ulises\<‚>ronnytulises]‚?4@!P‚@A?4‚Aulises^@‚B7C‚CDB7‚Dulises_C‚EF ‚FE‚GH3‚HulisesaG‚IJ:s‚JulisesbI‚K%L‚LMK%‚MulisescL‚N.bhandoveWWhandovereWgWqWyWWWW'W6W\WmWwWWWWWWWWhandover-prepareWhandovermodeWhandoverswWhandoverstatusWhappenTWhasW$WmWWWhavelWWWW\WrWwWhavingQWhavingtexualdescriptiononthosefiguresismorepreferablQVhdrzWWheaderrWWW*WfWWheadertypeWheadingWWWhelpmWhenceWhereWWherewegiveaproposalforaddingseveralcommandprimitiveVheterogeneous{WWhierarchyWhighermWqWwWWhighlight WhistoryWho2WhomeWhomegeneous{Whomegeneousandheterogeneous{V{V{V{V{Vusandheterogeneous{V{Veous{V{V{V{V{V7yEGolmieFNadaGMember^ Editorial_vi`37bReplace "betwen" by "between"cfacilitating handover betwen d2002age from the network entity, the MIHF in the new PoA further delivers this message to the MIHF peer in the old PoA. When the mobile node receives this primitive,@Af  33        33fcWhen the MIHF in the new PoA receives this message from the network entity, the MIHF in the new PoA further delivers this message to the MIHF in the old PoA. When the mobile node receives this primitive,d2307g2277iRonnyjRefer to comment #303m Superceded 2006/11/14EGolmieFNadaGMember^ Editorial_vi`37bReplace "betwen" by "between"cfacilitating handover betwen d2002jRefer to comment #303m Superceded 2006/11/14EGolmieFNadaGMember^ Editorial_vi`37bReplace "betwen" by "between"cfacilitating handover betwen d2002ÃAÃA ballWRliuohbarajkumar xiaoyu1liuxiaoyu2'liuliurxiaoyu3liueric4 ]njedjounjedjou sreemanthulav:eric5 njedjouPFQVohbaFyoshihiro6ohbaohbaQyoshihiro7ohbaP9aYohbaPyoshihiro8ohbaohba9yoshihiro9ohbaohbaawnc802.21~WWWW]W^W_WnWrWWWWWW802.3]WiW802.3ah]W9EWHWa'W(W7W?WEWUWWW[WdWuW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W"W#W,W-W2W9W;W>WCWDWSWWW[W\W^W`WdWfWgWiWWWWWWWWWWWWWWWWWWWWWWW‚kronnyuj‚lsrinivasv sreemanthula‚m sreemanthulan7`‚nsrinivaswxm sreemanthula‚osrinivasy sreemanthula‚p sreemanthulaq\6‚qsrinivaszp sreemanthula‚r sreemanthulas$‚ssrinivas{r sreemanthula‚trajkumar sreemanthulau‚usrinivas|laD^Technical, Binding_25`43a5.5bg Add: " For all transport services over L2 MIH_NET_SAP uses the primitives specified by MIH_LINK_SAP. "c8 For all L2 services, MIH_NET_SAP uses the MIH_LINK_SAP.d2073g2231iRonnyj0Please refer to Comment #71 for suggested remedykA It is better to separate L2 transport over data plane from L2 transport over control plane. In case of using L2 control plane, MIH_LINK_SAP should be used. In case of using L2 data plane (i.e., ethernet frame), MIH_NET_SAP should be used. (no its actually LSAP ...) mAccepted-ModifiedwAccepted 2006/11/16 2006-10-23MarkedEVivekFGuptaGMember^Technical, Binding_61`48a6.3.6b06/10/31 2006-10-23EVivekFGuptaGMember method to provide 802.21 IS with max length and then the MIIS can provide status response in place of query response if the response is too leBngthy. d187g2230 2006/10/31 2006-10-23EVivekFGuptaGMemberptaEEleanorFHepworthGMember^Technical, Binding_153a8.2.1bERetitle figure 25 "transport of MIH frame in IEEE 802 L2 data frame".crate drawings would be needed. Also, it is not required to indicate PHY-only portions of the frame. Also, there are no drawings for the cellular link types. Also, the term General Packet Frame is not exactly defined in the spec, it is General Frame only.mAccepted-ModifiedvRemove section 8.2.1wAccepted-Modified 2006/11/08 2006/10/19EEleanorFHepworthGMember^Technical, Binding_153a8.2.1bERetitle figure 25 "transport of MIH frame in IEEE 802 L2 data frame".copaque to the transport.)kccepted-Modified 2006/11/01 2006/10/19d2325ext here appears to provide implementation suggestions about how this would be designed. In addition, the text is confusing because it decribes transport at L3 but refers to IETF transport protocols which are generally considered as being at L4. Cd2325EVivekFGuptaGMember^Technical, Binding_61`48a6.3.6bgProvide amechanism such that PoA can indicate max length of query response it can handle to the MIIS. cAPoAs/MNs may be able to handle MIIS query response of a limited size only. There needs to be a way for MN to specify max length of query response. There is a need to incorporate a means such that query from client does NOT result in too much data being delivered. A PoA may not be able to predict how large a query response may be. So the PoA needs a method to provide 802.21 IS with max length and then the MIIS can provide status response in place of query response if the response is too leBngthy. d2187g2230 2006/11/15 2006-10-23EVivekFGuptaGMember method to provide 802.21 IS with max length and then the MIIS can provide status response in place of query response if the response is too leBngthy. d2187g2230 2006/11/15 2006-10-23EVivekFGuptaGMemberDDcthat@dthe@), theabortreasontlvcanbereplacedbystatustlvassucces@$thedraftdoesnotspecifiedhowthevalidityperiodparamet@_thelengthvalueofthelengthvarialbefirstoctetcannott@themihcommunicationmodelisalreadydescribedintheprev@thenamesofprimitivesandmessagesneedtobeconsistentt@thesameexampleisgiveninsection1.2withoutanyquantit@Jthesessionidshallbeusedinallmihmessagestoavoidco@ thevaluesofsomeelementsarecodedwith4bytesgivingva@€golmienada€nada}F€golmienada€nada}J€golmienada€nadaohba  €golmieⴃⵃnada€nada %€golmienada€nada€  EEunahFKimGMember^Technical, Non-binding_193aAnnex A2bA1. Change the title and the table title, "Mapping MIH Primitives to Reference Points" into "Mapping MIH Messages to Reference Points". 2. Change column titles as follows "No" => "Action Identifier" "MIH Message Identifier" => "MIH Message Name" "Category" => "Service Identifier" 3. Change "MIH Poll/Get Status" into "MIH Get Status" 4. Delete "MIH Link Event Configure Thresholds" 5. Table 31 is exactly the same as table 25 (page 161) except foBqr the column "Reference Point". Omit columns, "No", "Operation Code" and "Category", which makes the table neat. _cpMIH Primitives don't need to be mapped into Reference Points as they are used in local interface between layers.d2395g2226wAccepted 2006/11/16 2006-10-2031 EEunahFKimGMember^ Editorial_197aAnnex A4d182iRonnyro Ohbag2244 2006/10/26 2006-10-232EQiaobingFXieGMember^Technical, Non-binding_72`1a7.2.2.2bReorg these sections as follows: 7.2.1 Media Dependent SAPS 7.2.1.1 MIH_LINK_SAP 7.2.1.2 MLME_SAP etc. 7.2.2 Media Independent SAPs 7.2.2.1 MIH_SAP 7.2.2.2 MIH_NET_SAPcThis section doesn't belong under 7.2.2 "Media Independent SAPs". Note that section 7.1.1 correctly states that MIH_LINK_SAP is media dependent. d2232g4685k wAcceptedbefore 6.1. kYSystem management can be part of command service but different name is given for clarity.mAccepted-Modified 2006/11/15 2006/10/202EQiaobingFXieGMember^Technical, Non-binding_72`1a7.2.2.2bReorg these sections as follows: 7.2.1 Media Dependent SAPS 7.2.1.1 MIH_LINK_SAP 7.2.1.2 MLME_SAP etc. 7.2.2 Media Independent SAPs 7.2.2.1 MIH_SAP 7.2.2.2 MIH_NET_SAPcThis section doesn't belong under 7.2.2 "Media Independent SAPs". Note that section 7.1.1 correctly states that MIH_LINK_SAP is media dependent. d2232g4685k wAccepted02+l<bmakedefinitionoflinkparameterlistdefinitionconsistent@&media@meet@kmethods@mics@=mihcommandid@]mihlinksdutransmitstatus6@mihnetworkaddressinformation8@mlme@vmoble@movesub-section5.6.1.1mihlinksapundermediaindependen@guo"j ‚junxiangguo‚X'0‚guoX‚junxiangguo‚ hongcheng'‚zhuang  hongcheng‚zhuang A hongcheng‚P‚shuguiming/guojunxiang‚yuanZ‚liuyuan‚ajay trajkumar‚rajkumar`j‚ajay rajkumar‚rajkumarW ‚ajay rajkumar‚rajkumar‚ajay rajkumar‚rajkumarN‚ajay rajkumar‚rajkumarNZ‚ajay rajkumar‚8‚rajkumar‚ajay rajkumarkdataWvWWWWdef'nvWdefineWWoWdefinedWW!Wdefining!WdefnvWdefn'svWdefnintionvWdefnsvWdescribedWdescribingWdesignvWdhcpNWWdifferent1WdiscoverlWdiscoverylWdiscussionWvWdiscussionbecause21offersmac-likeservicetoanylayer/uvVdiscussionresponsefrmmihfinnetworkwouldbeunicastVdocumentsvWdomainsWdraftWdrawingsWduplicate!WdynamicWeWWencapsulationWentittyWentityWerrorsWethernetWevent!WexactlyWfaNWfacilitatesvWWiesWinlWW!WWWWincaseofusinglayer2transportformihfunctiondiscoverlVincludedWinformation!WWWinteractionsWoWinto!WipNWWWis1WW!WNWnWWWWWitWvWWiccivicaddresselementsMWclarificationeWclarifiedW-WclarifylW$WclarifyingmWclassWWWclasspacketdelayjitterisdefiendasVclear`WgWlWtWWWWWWWWWW"W]WjWpW|WWWWclearerWclearinguWclearlyFWbWWWkWclient'WWWWWWWcnyWcnmustbecorrespondentnodeyVco-located[WcodepWcodedWcoherencyWcoincidesWcolumn@WAWWWcolumnsWWreemanthula‚trajkumar sreemanthulau‚usrinivas|xzQc/Encoding details of the Value field inadequate.d2180g4716k wAccepted 2006/11/16 2006/10/20 subnets (how the list of variable size entries is encoded and decoded?)gd2178g4714k  2006/11/15 2006/10/20PEQiaobingFXieGMember^Technical, Binding_58`31a 6.3.5.3.5bwAdd more details on the encoding of the list of subnets (how the list of variable size entries is encoded and decoded?)eld missingd2178g4714k  2006/11/15 2006/10/20PEQiaobingFXieGMember^Technical, Binding_58`31a 6.3.5.3.5bwAdd more details on the encoding of the list of subnets (how the list of variable size entries is encoded and decoded?)he Value field missingd2178g4714k  2006/11/15 2006/10/20PEQiaobingFXieGMember^Technical, Binding_58`31a 6.3.5.3.5bwAdd more details on the encoding of the list of subnets (how the list of variable size entries is encoded and decoded?)es is encoded and decoded?)+bmakedefinitionoflinkparameterlistdefinitionconsistentVmakedefinitionsoflinkparameterlistconsistentthroughoutVmakethedefintionconsistentaVmakesW W'WmanagementjWW@WmWnWqWmandateWmandatory_Wmanipulation^WmapWmappedW]W^Wmapping6W W WmarkedWmarksXWmatchWmaxWmaximizewWmaximumWmay_WiWlWsW{WWWWWWWW6WFWlWmWqWrWwWWWWWWWWWWmaybe>W?WWmealWmeaningfulEWmeansrWmeanwhileWmeasuredWmeasurementsWmechanismWWWWmechanismspWrWwWW[vobtainsWobvious0WoctelmWoctetEWmWoctetsmWoddW'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''iYoshihiro OhbajmUser identification information can be obtained by other means and does not need to be carried in MIH messge.k mRejectedwRejected 2006/11/16 2006-10-17 CurrentLinkIdentifier, SuggestedNewLinkList, SuggestedNewPoAList, HandoverMode, OldLinkAction, QueryResourceList, QueryResourceFlag, MIHUserIDList ) Or use MIHF Variable Load: Type Length Value TYPE_HDR_TLV_MIH_user_ID Variable MIHF user ID that identifies which MIB'H users need to process this message @Az 33@  M 33   33 zcAMIHF can be used to exchange messages by MIH users between different communication systems. During handover procedure, there are some Event indications generated by MIH_Handover primitives/messages to some specific MIH users. How to indentify or indicate different MIH users?d2355g2223.jgeneralWWWgenericWget!Wgives^WgivingaWgramaticWgrammarsWhasWWWhavelWheader*WheadingsWhelpsWhelpwithenglishgrammarusagesVhenceWhigherWhomeWhome/visitedWhow[WiWianaWidW*WidentificationWidentifiedWidentifierWieeeWWWiesWifNWdWWimplementationsWimplicitWinlWnWoWWWWWW*W3WNWXWvWWWWWWinclude[W!WWincludemihnmsinitializeoperationaspartoflinkcommand!VincludedNWinconsistencyWindicateWindicatedNWinfoquerytypenWinformation[WWWWinherentlyWinitialize!WinstanceslWintelligenceWinteractionWintersectWintoW3WNWipNWipconfigrationmethodNWipv4NW@sjalloWWWalsoWWamendmentsWanWand]WaWlWnWoWWWW!W*WNWWWWWanotherWanyWaquirelWare]WlWWWWdWWWWaroundWasaWlWnWoWWWWW!WNWWWWassignedWassociatedWatlWnWWWbaoutWbased[WbasicWWbelWoWWWWWWWXWWWWWbecauseWbeenWbefore1WbeginningWbehaviourXW62KPE YoshihiroFOhbaGMember^ Editorial_183`45a8.5.3.23bA3Change: IP Address Configuration Methods List (215)3@AR  33/  0  2  33RcGThe Type value of IP Address Configuration Methods List is not correct.d2386g2458 2006/11/16aGMember^ Editorial_183`45a8.5.3.23bA3Change: IP Address Configuration Methods List (215)3@AR  33/  0  2  33RcGThe Type value of IP Address Configuration Methods List is not correct.d2386g2458 2006/11/152006/11/15 2006/10/23PE YoshihiroFOhbaGMember^ Editorial_183`45a8.5.3.23bA3Change: IP Address Configuration Methods List (215)3@AR  33/  0  2  33RcGThe Type value of IP Address Configuration Methods List is not correct.d2386g2458 2006/11/15s.36 NcBthod are specified.d2384g2457iRonnyjAModify the text indicated as following into line 34 page 183 and line 61 page 193: Serving FA Address / Serving Access Router Address/ DHCP Server Address parameter is chosen depending on what kind of IP address configuration methods is set. E.g., if IP Address configuration method is IPv4 dynamic configuration (DHCPv4), then IP address included in "Serving FA Address / Serving Access Router Address/ DHCP Server Address" is DHCP Server address (IPv4). Ralation of Bit setting in IPConfigraBtionMethods and IP address included in the FA Address/Access Router Address/DHCP Server Address TLV is as following: Bit 1 is set : IP Address TLV contains DHCPv4 server IP address. Bit 2 is set: IP Address TLV contains Foreign Agent IP address. Bit 3 is set: IP Address TLV contains DHCPv4 server IP address. Bit 11 is set: IP Address TLV contains IPv6 Router IP address. Bit 12 is set: IP Address TLV contains DHCPv6 server IP address.;rjwhenlWWWwhich[WaWlWsWdWWWwhileWWWwillW>nada?=A?golmie>nada@GA&A hongchengnadaB@GBgolmieAnadaC D<'pDguptanadaEC EgolmieDnadaF'G'GnadaHF'HgolmieGnadaI8fJ(JnadaKIfKgolmieJnadaL#M(pMnadaNL#NgolmieMnadaO)P* PnadaQO)QgolmiePnadaR&&S*0SnadaTR&TgolmieSnadaUgolmie'nadaVnadaW&IWgolmieVnadaX Yp1YnadaZX ZgolmieYnada[jameshan\hepworth]])jipv6NWis[WnWoWsWWWWWWWW*W3WNWXWdWvWWWWWitaWWitselfXWjustWkeepWkindNWknowlWl2WWWWl3WlayersWW3WWWWlayeredWlayersWleaveWleftWleft-mostWline^WoWWW3WNWWlinkaWsW!WWWlistlWnWoWlistedoWlocalWlooknWlowerWmac/phyWmacroWmadeWmandateWmappingWmaylWWWWWmeansWmechanismsWmechansimsWmediaWWWWmedia-specificWmessagelW*WdWmessageslWoWdWmessgeWmethodNWWmethodslWNWmichaelwWmichaelwacceptedmodifiedVmicroWmihlWWWWWWWWW!W3WWWWBJESrinivasF Sreemanthula^Technical, Binding_105`20a 7.4.7.1.2PoA, all the MIH protocol services including MIIS are transported by use of data frames specific to that media technology or in a media independent way by using higher layer IP based protocol." 2. Redundant. remove.cA1. "However, after authentication and attachment to a certain PoA, all the MIH protocol services including MIIS by use of data frames specific to that media technology or in a media independent way by using higher layer IP based protocol." something missing. 2. After authentication and attachment to a certain PoA, the MIH protocol may be used for information retrieval by use of data frames specific to that media technology. d2150g2248iRonnyjRefer to comment #149k]Using data frame after authentication and attachment to a certain PoA should not be madated. m Superceded 2006/11/15 2006-10-23ESrinivasF Sreemanthula^Technical, Binding_105`20a 7.4.7.1.2$Fa 7.6.5.1.2bA9[1] Change "MIHProtocolPDU" to "Data" [2] Change Description to: "An MIH PDU may be splitted into multiple pieces of data, where each piece of data is contained in this Data field in a separate MIH_TP_Data.request." [3] Also, apply changes [1] and [2] for MIH_TP_Data.indication primitive in Section 7.6.5.2.2.9@A>  33C    33>cWhen acknowledged connection-oriented mode is used, the data contained in one MIH_TP_Data.request primitive does not have to be the entire MIH PDU. In fact, the data may be just one octet.d2317g2449wRejected 2006/11/16 2006/10/23aGMember^Technical, Binding_150`13a 7.6.5.1.2bfirm should be the same as that for MIH_Get_Information.response.d2310g2448 2006/11/14 2006/10/23FE YoshihiroFOhbaGMember^Technical, Binding_150`13a 7.6.5.1.2beunahkimjeon2hongseokjeon@ijcommunicationWWcompatibilityaWcompletelyvWcomplexityWcompliantWctWconfigurationNWconnectedWconnectionWconsecutivedWconsiderWconsistentlyWcontainsNWcontributionsWcostWcoverageWcreatesWcurrentWcurrentlysWdataWWdecidelWWdefinelWWdefinedWWdefinesaWdefinitionWWdefn'svWdeleteW!WdeliversWdependingNWdescribeWdescribed3WXWdescription[W^WWdetailXWdetailed3Wdetailedprocedureofmihfunctiondiscoveryoverlayer2is3VdetailslWWdeterminedWdhcpNWdhcpv4NWdhcpv6NWdifferent[WlWWdirectlyWdiscoverlWdiscoverylWWW3WWdoesWWdraftWdynamicNWeWNWWeachlWWeditorWeditorpleaserunspell-checkerVW=\kjustvWkeep!WknowWknowingWl2WWoWWl3WWoWlastWlayerlWvWWWlayer/uservWleavevWlinesWlinkWWW!WoWWWlookingvWlsapWmnWmacWvWmac-likevWmacsWmadatedWmadeWvWmacsWmadatedWmadeWWW5EEricFNJEDJOUGMember^ Editorial_32a5.6.1.1bsMove sub-section 5.6.1.1 "MIH_LINK_SAP" under "Media Independent SAPs" 5.6.2 section (and renumber it accordingly)tion for the Figure 3 in: "An example of network model including MIH services"cmThe MIH Communication Model is already described in the previous Section 5.3.1 and illustrated in Figure 2. d2055g2256 2006/10/31 2006/10/1135EEricFNJEDJOUGMember^ Editorial_32a5.6.1.1bsMove sub-section 5.6.1.1 "MIH_LINK_SAP" under "Media Independent SAPs" 5.6.2 section (and renumber it accordingly)/10/31 2006/10/1135EEricFNJEDJOUGMember^ Editorial_32a5.6.1.1bsMove sub-section 5.6.1.1 "MIH_LINK_SAP" under "Media Independent SAPs" 5.6.2 section (and renumber it accordingly)leejin#lee9Alee9jin$leeleeI8jin%lee%qlee%lee7|kprotocolvWWpurposeWpurposeofmihnetworkaddressinformationistogetinformaVre-wordvW] bAChange the text as follows. MIH_NET_SAP provides L3 transport services on the local node, supporting the exchange of MIH information and messages with remote MIH Function.@A> 332 5 33>cMIH_NET_SAP seems to be used for MIH transport service but MIH_LINK_SAP is also used for L2 transport. Thus, the role of MH_NET_SAP needs to be limited to L3 transport service.d2101g2231iVivekkMIH_NET_SAP uses (or maps to) MIH_LINK_SAP for all L2 interactions with respective media. For L3 this SAP may define other primitives...mAcceptedvMIH_NET_SAP provides transport services on the local node, supporting the exchange of MIH information and messages with remote MIH Function. For L2 this SAP uses the primitives provided by MIH_LINK_SAP.wAccepted-Modified 2006/11/16 2006-10-20MarkedEEunahFKimGMember^Technical, Non-binding_68`7a6.4.3be and Information Service)@ F8bAThe TLV representation of these Information Elements is described in Section 6.3.5. Another way of representation of IEs using XML is described in Section 6.3.7.1.@AR  33    33T  RcThe representation of these Information Elements described in Section 6.3.5 is not only the representation of the IEs. There is also XML/RDF representation of IEs.d2138g2437wAccepted 2006/11/16 2006/10/239E YoshihiroFOhbaGMember^Technical, Binding_48`28a6.3.3bpted 2006/11/15 2006/10/23T88E YoshihiroFOhbaGMember^Technical, Binding_48`4a6.3.3bAThe TLV representation of these Information Elements is described in Section 6.3.5. Another way of representation of IEs using XML is described in Section 6.3.7.1.@AR  33    33T  R4kreceive!WWrecommendedWregister!WrelatedWrequiredWresolutionWrespectiveWoWresponseWrouterNWsamelWsapWWW!WnWoWWseevWseem!WseparateW!WWserverNWWservice1W!WvWWservingNWshouldWWW!WWWsittingWsizeWsolicitWsomethingvWstandardWvWstandardsvWstate!Wsubscription!WsuchvWWsuggestvWsuggested!WWsupport!Wsystem1Wsystemmanagementcanbepartofcommandservicebutdiffere1VtcpWtermvWtermsvWthelWW!WvWWWthefunctionsdefinedbythecommenterseemtofallintocat!VthereWthisWW!WoWWWtimelWtlvNWtoWW!WoWvWWWWWWWtoo!WtransportlWWWW cAHThe draft states: "The receiving MIHF instance shall issue either an MIH_TP_Connect.response primitive to accept the connection, or an MIH_TP_Disconnect.request primitive to refuse the connection." Since the MIHF receiving the MIH_TP_Connect.confirm is the last step to establish a connection, there is no more message to send.Hd2315g2238wAccepted 2006/11/16nny jEProvide description of the mapping function as part of MIH function. kFigure in the contribution helps understand the function of MIH_LINK_SAP. However, the mapping function should be defined in the 802.21 draft because media specific standard would not define it. mAccepted-Modified 2006/10/31 2006/10/23EKentaroFIshizuGMember^Technical, Binding_144`1a 7.6.2.3.4bMIH_NET_SAP should have MIH_TP_Data.{response,confirm}. Introduce the modifications proposed in the submission 21-06-0785-00-0000_MIH_NET_SAP_additional_primitives.doc into the 802.21 draft. ca‚"j jtheWWWWWWWWW3WNWXWdWvWWWWWWWthebehaviourneedstobedescribedinmoredetaileitherofXVthetextinsection5.4.3isaboutinformationrepresentatioVthetlvvaluesforallmessagesinsections8.5.18.5.2andoVthetwocategoriesareneededforextensibilityieextendedVthenWNWWthenthemnalsoneedstospecifytypeofuserhome/visitedVnandneedstobedVthisistoomedia-specificanddoesnotworkforothermediaVthismaynotbenecesarilytrueinallcaseseitherway802.VthoseWthroughWtimelWtlv[WNWtlvsWto]W^WlWWWWWWWWWCWXWWWWWWWWWtooWtransaction-iddWtransaction-idcandeterminewhichmessageisbeingacknowledVtransportW*WwayWwgWwhatNWjserviceWWserviceslWWservingsWNWservingfaaddressservingaccessrouteraddressdhcpserverNVsession*Wsessionidiscarriedinvariableheaderpartandnotneeded*VsetNWsettingNWshouldWWWWsidWsidesWsignalingWsimple[WsoWvWWsolicitedWsomethingWspecificWWWspecificationWWWspecifyWspell-checkerWstate!WWstrictlyWsubscribedWsubscriptionWsubsectionslWsuchWWWsufficientXWsuggesedlWsuggestWsuggestedWWsuitableWsupportlWsupportedlWWsupposedWtableaWWtable8pgdefinesnetworktypeswhichwecalllinktypeselaVtargetsWtechnologiesWtermWterminologyWtextWWWW3WNWvWWthanWWthatlWWvWWWW-aNjwithaWlWsWWWWWWWwithinWwordingWworkWxml[Wxml-representedWyes]Wyes16and17aretherightreferencestordf]Vk1vW2lWvWW21vWW3vW30W4vW5vW5.1vW6vW802.21WnW802.21isnotusingmsapnV9NWaW!WvWWWaboutWacceptedWaccessNWaddressWNWWWadvertiseWafterWagnosticWakinvWallW!WNWoWalsoWvWWandlWW!WNWWWWanyvWareWNWasWvWWWatlWWattachmentWauthenticationWawarevWbe1WlWWWW!WNWWWWbecauseWNWvWWbecauseservingfaaddressservingaccessrouteraddressandNVbeforeWbetterWWbigWbotyWbroadcastingWbutbM cAThis section describes Types of events; 6.1.3 talks about local and remote events; and 6.1.5 talks about event subscriptions, yet there si no clear corollation across sections. Leaving the reader wanting to know what is being described and how they are really grouped or organized.d2107g2258 2006/11/16EGolmieFNadaGMember^ Editorial_40`13a6.1.5bDelete this entire paragraph.cYThis text is inappropriate here and is already contained appropriately in section 8.3.3.2d2111g2259 2006/11/16EGolmieFNadaGMember^ Editorial_41`15a6.1.6b2Fix inconsistency (This occurs in multiple places)cLink event name includes SDU, but description uses PDU, so does the event contain the status of service data units or protocol data units.d2114g2261 2006/11/162EGolmieFNadaGMember^ Editorial_41`31a6.1.7bDelete the column.2_kmanagement1WmanyWmappingWNWmapsWoWmayW!WoWmediaWoWmemory!WmessageWmessagesizeisabout2130bytesandthisisnotbigasadVmethodWmihlWWWW!WoWWWWmihnetsapisforbotyl2andl3transportoverdataplaneVmihnetsapusesormapstomihlinksapforalll2interactoVmnWmobileWmobilecannotsolicitusingunicastaddresswithoutknowingVmodificationWmodifiedWname1WneededNWnetWoWWnetworkWWnms!WnoWnodesWnotWW!WnWWWof1WlWW!WWWWoperation!WoroWorder!WoverWWpart1WpeerWperformanceWperformedlWplaneWWpoaWWWWWpoashouldbeposVposWpre-configurationWprimitives!WpriorWWW?lkcan1WlWW!WNWWWcannotWcapabilitylWWcaselWWWcasesNWWcategory!WcellularWcertainWclarificationWclarity1WNWclearNWcommand1W!WcommentWcommenter!WcompliantWconfigurationWcongestionWcongifurationWylWdraftWduplicate!WdynamicWevent!WfaNWfall!WfigureWfigureinthecontributionhelpsunderstandthefunctionofVfor1WlWW!WNWfunctionlWWWfunctions!Wget!WWgiven1WhandoverWhave!Wheavy!Whelpful!WhelpsWhoweverWinlWW!Wincaseofusinglayer2transportformihfunctiondiscoverlVinformation!WWinto!WipNWWis1WW!WNWWitWkeep!WknowingWl2Wl3WlastWlayerlWlinkW!WK> 8kbut1W!WvWby!WWbytesW3‚HulisesaG‚IJ:s‚JulisesbI‚K%L‚LMK%‚MulisescL‚N*1jbeingdWWWbetweenWbitNWbridgingWbroadcastWbutoWbylWWWXWWWWcallaWcallsaWcanlWWWdWWWcapabilitiesWcapabilitylWWcarried*WWcasesWcategoriesWcellsWcertainlWchange^WaWnWWWWWWWchangeinfoquerytypetoisquerytypelistin8.4.1.35and8nVchangeline20toreadtheoverallnetworkmayincludepicoVchangeline59to^VchangenewpoatonewposVchangesentencetoreadVchangetexttoreadsuitableamendmentsarerequiredtoexisVchoicesXWchosenNWcolumnoWWcolumnsWcombinedWcommand!WcommandsWcommandsessentiallyflowfromhigherlayerstolowerlayersVcommentaWWWWCWvWWWWcommonWcommunicateW*WdWWWWformalWUktransportprotocolsuchastcpmaywanttoreceivelinklayeVtypeNWWtypeiepoadhcpaddressisforipaddresspre-configurationVtypesWunderstandWunicastWuseWWusedWNWvWWusefulvWuser!WvWusesWoWusinglWWnWWWusingdataframeafterauthenticationandattachmenttoaceVvariousvWvsvWwantWwasWwayWwhereWwhichvWwirelessWwithWWoWWwithinvWwithoutWWwouldWWWnada€nada}F€golmienada€nada}J€golmienada€nadaohba  €golmieⴃⵃnada€nada %€golmienada€nada€/ ]bcA1. "However, after authentication and attachment to a certain PoA, all the MIH protocol services including MIIS by use of data frames specific to that media technology or in a media independent way by using higher layer IP based protocol." something missing. 2. After authentication and attachment to a certain PoA, the MIH protocol may be used for information retrieval by use of data frames specific to that media technology. d2150g2248iRonnyjRefer to comment #149k]Using data frame after authentication and attachment to a certain PoA should not be madated. m SupercededvRemove this sentence: "After authentication and attachment to a certain PoA, the MIH protocol may be used for information retrieval by use of data frames specific to that media technology." wAccepted-Modified 2006/11/16 2006-10-233cIt is not possible to use the destination timestamp in packets to determine that it is older than the timeout duration and discard the packet unless MIH peers are synchronised. Can this synchronisation really be guaranteed? d2345g2224wAccepted 2006/11/16 2006/10/19Markedaranteed? d345g2224 2006/10/31 2006/10/19 for example, because the protocol imposes congestion or flow control. Note also that RTT information may not be available at the MIH application layer so it may be impossible to tune timers to take it into account. cd341g2223 2006/10/31 2006/10/19EEleanorFHepworthGMember^Technical, Binding_155`28bRemove this sentence.cIt is not possible to use the destination timestamp in packets to determine that it is older than the timeout duration and discard the packet unless MIH peers are synchronised. Can this synchronisation really be guaranteed? d345g2224 2006/10/31 2006/10/193 ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnomnoaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoP‚shuguiming/guojunxiang‚yuanZ‚liuyuan‚ajay trajkumar‚rajkumar`j‚ajay rajkumar‚rajkumarW ‚ajay rajkumar‚rajkumar‚ajay rajkumar‚rajkumarN‚ajay rajkumar‚rajkumarNZ‚ajay rajkumar‚8‚rajkumar‚ajay rajkumarM@icA]@b'dbA@{7@@;cA@Nc>@L{@cZc8cEbcA<cMb^c@ucVb@evd^@jw@@bB|cFcb_@^cA8@@g@~c@0@@@ccAkA@cA@cCC2bjbeing@@communication@1conduct@editorial@elements@format@general@)ipv6@.miis@node@parameters@:rdf@replace@service@:specifications@the@9there@jtrue@when@-with@;without@akbridging@Kbut1?can@>contribution@data@#fall@just@2management@=mayofvprimitivesprotocol@4receive@7somewhat@transportprotocolsuchastcpmaywanttoreceivelinklaye@Amaccepted-modified!v21-06-0794-01-00-000@:2325@2360@=8.3.3.5@8.4.1.20@a@ability@!addthefollowinginsection6.3.3@vaddress@alsowUandmarkotherunusedvaluesasreserved@1@Gare_at@bebycomment2190@ candidate@changetextto@#check@configuration@1vannexisjustanexampleitdoesn'tmeanthecommandisn'tnVanotherRW'WkWWWany+WUWW6WyWWanythingW$Wanywhere!WvWapplicableeWappliesWapplyWWWappropriateWWappropriately!WxWaquirelWareEWRWUW[W]W_WjWlWmWWWW!W#W9WSWa/ocgAll type values in the protocol message TLV table are not updated with the values assigned in Table 26.d2374g2483i Vivek GuptajA%The TLV values for all messages in sections 8.5.1, 8.5.2 and 8.5.3 in Type column under () need to be updtaed and be as per those in Table-26. For example IS Query Type List is listed as (252) on page 173,, line 55, but in Table-26 the actual value is 4. Please correct all these discrepancies%mAcceptedvA%The TLV values for all messages in sections 8.5.1, 8.5.2 and 8.5.3 in Type column under () need to be updtaed and be as per those in Table-26. For example IS Query Type List is listed as (252) on page 173,, line 55, but in Table-26 the actual value is 4. Please correct all these discrepancies%wAccepted 2006/11/16 2006/10/23,xESrinivasF Sreemanthula^Technical, Non-binding_17`5a5.2 (e)bpWe review if the above are covered adequately in the later sections. Need different sections to cover the above.c(e) The standard shall specify mechanisms to support MN-initiated, MN-controlled, network-initiated and network-controlled handovers. Does it?d2050g2237vAIts up to upper layers to figure out how to utlize services provided by .21. There are flows in Annex which address this. The Hanadover Commands address this in section 6 as well. Delete "mobile initiated, network initiated, etc." from this section. Reword the sentence appropriately as: "Different access networks support horizontal handover mechanisms as per their respective standards."wAccepted-Modified 2006/11/16 2006-10-230-23|+c/Unused acronyms: HLSI LLI MDI MII MIHS OUI PMD d2033g4678k vP(Editor: Check for use of these acronyms in draft before deleting any of these.)wAccepted 2006/11/16 2006/10/20Marked,EQiaobingFXieGMember^Technical, Binding_26`43a5.5b4Remove "Optiona 1" or clarify what are other optionsc0What is "Option 1"? Are there any other options?d2077g4679k wAccepted 2006/11/16 2006/10/20Marked50EQiaobingFXieGMember^Technical, Non-binding_50`48a6.3.3b'Add some explanatory text to Figure 20.c4There should be some explanatory text to Figure 20. d2145g4683k vby comment 2143w Superceded 2006/11/16 2006/10/20201EQiaobingFXieGMember^Technical, Binding_67`38a6.4bbThis section is out of place. Relocate its content to the proper place(s) and delete this section.cyvRemove : ANI, H-AAA, HMIP CN: Core Network (Just keep as Core Network) NAS: Non-Access Stratum (delete this acronym) and spell this out in Figure -11 (Editor: Check for use of these acronyms in draft before deleting any of these.)wAccepted-Modified 2006/11/16 2006-10-23MarkedzESrinivasF Sreemanthula^Technical, Binding_20`25a5.3.2bAdd R3. Add reference in text.cXR3 must be possible on link between Visited/Home network and Access-Network-3 (cellular)d2056g2239vVIn Figure 3 change: Change R3/R4/R5 to R1/R3/R4/R5 Change R1 to R1/R3/R4/R5 as well. wAccepted-Modified 2006/11/16 2006-10-23Marked3{ESrinivasF Sreemanthula^Technical, Binding_24`13a5.4.3bHcannot be restricted to heterogeneous.... homegeneous and heterogeneouscPMIIS provides the ability to access information about all heterogeneous networksd2068g2240vAPMIIS provides the ability to access information about all heterogeneous networksP>EGolmieFNadaGMember^ Editorial_4`1a1.5bMerge sections 1.4 and 1.5 under a single heading " Media Independence" and focus the discussion on the media independence characteristics of 802.21.cThe section 1.4 discussed Media Independence while section 1.5 discussed Media dependence. Both sections provide a redundant description. d2017g2306 2006/11/16EGolmieFNadaGMember^ Editorial_10`49a4bChange to L3MMPcL3MP missing an "M"d2034g2245 2006/11/16EGolmieFNadaGMember^ Editorial_13`45a5.1.2bdetelete lines 45-47.cJThe same example is given in section 1.2 without any quantitative measuresd2036g2307 2006/11/16EGolmieFNadaGMember^ Editorial_14`26a5.1.3bChange Packer to PacketcMisspelling of Packetd2041g2246 2006/11/16EGolmieFNadaGMember^ Editorial_14`64a5.1.3bReplace "defiend" by "defined"c)Class Packet Delay Jitter: is defiend as d2043g2219w WithdrawnEz@cAh@@o@ScA9@bc@@@b@@@jA@bA@]bA5bA @ bA @ b@@jA@^@*vA@@ @ @ @ @ @ @ggg>GEGolmieFNadaGMember^ Editorial_1`42a1.1b Remove "etc.""enabling more effectivec7line 47 reads: "thus enabling making of more effective"d10g2305 2006/10/31EGolmieFNadaGMember^ Editorial_1`42a1.1b Remove "etc."owever, no quantitative measures are offered to back up this statement and show under what conditions improvements can be expected.d7g2304 2006/10/31EGolmieFNadaGMember^ Editorial_2`47a1.2b%replace with "enabling more effectivec7line 47 reads: "thus enabling making of more effective"d10g2305 2006/10/31EGolmieFNadaGMember^ Editorial_1`42a1.1b Remove "etc."7g2304 2006/10/31EGolmieFNadaGMember^ Editorial_2`47a1.2b%replace with "enabling more effectivec7line 47 reads: "thus enabling making of more effective"d10g2305 2006/10/31EGolmieFNadaGMember^ Editorial_1`42a1.1b Remove "etc."TkMichaelW: Text of lines 36-55 has many syntactic errors. This text also needs clarification if there are cases where broadcast domains are not compliant with 802.1 bridging. The text can be made to specify the behavior for IEEE media only.m Supercededvby comment 2328w Superceded 2006/11/16 2006/10/23Markedseems media specificd2335g2236iRonnyjARefer to Comment #336 MichaelW: (Accepted Modified) Re-write the section to fix gramatic errors (editorial change). Change the section title to "Solicited MIH Capability discovery in 802 media". Add the sentence: Layer two broadcast mechanisms are inherently media specific. This specification creates a common broadcast discovery method only for the media compliant with 802.1 bridging. Add another section afterward "Solicited MIH Capability discovery in non-802 media" with text: BroadcBVast mechanisms for discovery within non-802 media are defined in other specifications.Dm Superceded 2006/11/01zBv7OK to mntion specific command names. Compare to 5.4.2.4wAccepted 2006/11/16 2006/10/20Markedm MIH Function to the lower layers (maybe using dashed line).cTo be consistent with Figure 18 remote command illustration, on the remote entity side should there be a command arrow from MIH Function to the lower layers? d2118g4698k  2006/11/02 2006/10/2017ngFXieGMember^Technical, Binding_43`40a6.2.2bpAdd, on the remote entity side, a command arrow from MIH Function to the lower layers (maybe using dashed line).cTo be consistent with Figure 18 remote command illustration, on the remote entity side should there be a command arrow from MIH Function to the lower layers? d2118g4698k  2006/11/02 2006/10/20174698k  2006/10/31 2006/10/2017is also used for L2 transport, which is duplicated and confusing.d72g2230iRonnyj0Please refer to Comment #71 for suggested remedyEEunahFKimGMember.CpEVivekFGuptaGMember^Technical, Binding_55`52a 6.3.5.2.5bPlease refer to contribution: 21-06-0731-01-0000-LB-issues-5-6 for details. This was missed as part of editorial update in version D2.0cFor TYPE_IE_SECURITY specify Cipher_Suites ::= BITMAP {None, WEP,TKIP, AES-CCMP} Authenticated_Key_Management_Suites ::= BITMAP {None, WEP, Psk, 802.1X } d2171g2227iYoshihiro OhhajThis is too media-specific and does not work for other media. Those parameters specific to 802.11 should be defined in 802.11 WG. 802.21 WG should define only general secuirty properties if such definition is possible.mRejectedvJUse individual network specific standard revision to specify the security.wAccepted-Modified 2006/11/16 2006-10-23EVivekFGuptaGMember^Technical, Non-binding_61`48a6.3.6b'Add these TLV query examples in Annex. cividual network specific standard revision to specify the security.wAccepted-Modified 2006/11/15 2006-10-23&_@Sc{abRb@tc@YdcAWC>e@fvfcBXgbBgcA`Ceh@mcj@tgskcAlbAvAm@wbA`cobq@bBcrcs@rtcv@kAwEvAx@Iy@vK{v@~g@vA@b bAbAB@/bvw@cBm@acBpv@@bAb$bACZEcAvAF@cB@vO@bAi(@bBDFHJo9EKentaroFIshizuGMember^ Editorial_3`1a1.2b7Replace the arrow of IS with a uni-directional arrow. cA!According to the Table 15, the only primitive for IS is MIH_Get_Information. But, the arrow of IS in the Figure 1 is bi-directional. If there is MIH_Set_Information, then the current figure is correct. Otherwise, the arrow should be one-directional from "MIH Function" to "Lower Layers". !d2012g2211 2006/11/16 2006/10/231EKentaroFIshizuGMember^Technical, Binding_31`22a5.6bMIH_LINK_SAP is actually media-independent which is going to be mapped to each specific media-dependent link technology. Introduce the modifications proposed in the submission 21-06-0784-00-0000_MIH_LINK_SAP_clarification into the 802.21 draft. cer Layers". !d2012g2211 2006/10/31 2006/10/231cType field for this and some of the following sections have not been defined. Also, some explaination should be added to each section.d2380g2245wRejected 2006/11/16 2006/10/23led treatise should be given a separate section.chIt is unlcear MIH Protocol Ack Operation is defining a state machine or implementation specific details.d2340g2244 2006/11/01 2006/10/23EAjayFRajkumarGMember^Technical, Binding_175`1a8.5.1.3b/Would provide additonal information separately. feels that MIH state machine needs to be defined in the spec then more detailed treatise should be given a separate section.chIt is unlcear MIH Protocol Ack Operation is defining a state machine or implementation specific details.d2340g2244 2006/10/31 2006/10/23EAjayFRajkumarGMember^Technical, Binding_175`1a8.5.1.3b/Would provide additonal information separately.otion.jd26g2242 2006/10/31 2006/10/23EAjay1 GvalsowWyWWWW4W=WEWlWalsochangemihreporttoinfoqueryresponseEValsolookat2330wValways9WamendmentsWanMWuW~WWWWWWand7WEWMWNWRWSWUW[W]W_WlWmWnWoWtWuWwWWWWWWWWWW&W+W,W0W6WNW]W_WdWeWgWjWuWvWwWyWWWWWWWWWWWWWWWWWW protocol behaviour and call flows. An implementation independent MIH Protcool State Diagram and its description is felt necessary.d2348g2493v330 wDeferred 2006/11/01 2006/10/23nly saying that "however, the security of this information are outside the scope..." while describing the transport of information d65g2491 2006/10/31 2006/10/23vESubirFDasGMemberucTThe system management service is unexpected and has not been introduced until here. d2208g2319 2006/11/16EGolmieFNadaGMember^ Editorial_67`47a6.4b*Add this primitive to Table 15 on page 71.cXThe MIH Function discovery has only been listed here and is not described anywhere else.d2210g2320 2006/11/16EGolmieFNadaGMember^ Editorial_69`9a7.1.1bChange heading to Media Dependent SAP; Have but one bullet item MIH_LINK_SAP; remove the other bullet items, or at least indent them to be under the single MIH_LINK_SAP.c7.1.1 contains one generic media dependent SAP (MIH_LINK_SAP) which is composed of various technology specific SAPs. The current organization does not clearly show this relationship.d2216g2266 2006/11/16EGolmieFNadaGMember^ Editorial_69`35a7.1.2bDelete MIH_SAP from end of lined2217g2267 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_69`39a7.1.2bThe measurements report metrics that are typically used in handover algorithms, such as signal quality, synchronization time differences, transmission error rates, etc.cThe measurements may report signal quality, synchronization time differences, transmission error rates, etc. and are some of the metrics used in handover algorithms. Rationale: Improve flow of sentence.d2009g2234 2006/11/16 2006/10/23EAjayFRajkumarGMember^Technical, Binding_3`36a1.2bFigure 1 shows the placement of the MIHF within the mobility-management protocol stack of an MIH-capable network element that includes one or more access link endpoints.ceESubirFDasGMember^ Editorial_71a7.2.2b The descriptions for Table 15 are in section 7.4. Therefore, Table 15, #4 " MIH Link Up " description should be in section 7.4.4; Table 15, #11 "MIH Link Handover Imminent "description should appear in section 7.4.11, and so on....not defined. d2364g4735 2006/11/15eESubirFDasGMember^ Editorial_71a7.2.2b The descriptions for Table 15 are in section 7.4. Therefore, Table 15, #4 " MIH Link Up " description should be in section 7.4.4; Table 15, #11 "MIH Link Handover Imminent "description should appear in section 7.4.11, and so on....7.2.2b The descriptions for Table 15 are in section 7.4. Therefore, Table 15, #4 " MIH Link Up " description should be in section 7.4.4; Table 15, #11 "MIH Link Handover Imminent "description should appear in section 7.4.11, and so on....65`1a8.4.1.7bKDefine a self-contained MAC Address field that can indicate the type used. 3&EJInFLee^Technical, Non-binding_60`14a 6.3.5.3.7bA=[Delete the row corresponded to Bit5, page 60, line 14] : =@A  33cAThe value 'IP Version 6 Prefix Available ' in PoA Capability IE can be acknowledged by PoA IP configuration Methods IE already. I don't think it should be provided with other geneal capabilityies of PoA. I would suggest the value be removed unless having the value in PoA Capability IE does come with additional benefits. If it does, another values related to IP address configuration would be applicable.d2184g4929v1This information is duplicated and hence deleted.wAccepted other geneal capabilityies of PoA. I would suggest the value be removed unless having the value in PoA Capability IE does come with additional benefits. If it does, another values related to IP address configuration would be applicable.d2184g4929v1This information is duplicated and hence deleted.wAccepted8cDesign principles section has no place in a specifications document since the design & guiding principles should be obvious and clear in from the definitions provided.d2048g2310 2006/11/16EGolmieFNadaGMember^ Editorial_17`33a5.3.1b:Delete entire section 5.3 and Annex A2 containing Table 31cMThere is no use of this model in the draft, except for the Table 31 in Annex2d2053g2248 2006/11/162EGolmieFNadaGMember^ Editorial_22`57a5.4.1.4b7Delete last sentence which includes the specific Eventsc%There is no need to list events here.d2060g2249 2006/11/16EGolmieFNadaGMember^ Editorial_23`37a5.4.2.3b9Delete last sentence which includes the specific commandsc'There is no need to list commands here.d2062g2250 2006/11/16EGolmieFNadaGMember^ Editorial_24`9a5.4.3b_Rewrite the sentence using only TVL, which is stated in 5.7 as the one used in the MIH protocol\bAdd MIH_NET_SAP to Figure 12c/Figure 12 appears to be missing the MIH_NET_SAPd2094g4686 2006/11/16 2006/10/2012EBenjaminFKohGMember^ Editorial_47`15a6.3.2b.Replace with: Service, a MIH PoS may act as anc"Service, an MIH PoS may acts as and2133g4687 2006/11/16 2006/10/20EBenjaminFKohGMember^Technical, Non-binding_51`1a6.3.3bReplace with: network using the MIH protocol or: Clarify what is MIH IS protocol, is it the query language to access the IS schema? etc.clSentence in line 1 mentions "network using the MIH IS protocol". Later sentences only refer to MIH protocol.d2151g4688iVivekj*Replace with just MIH Protocol (delete IS)mAcceptedv delete ISwAccepted 2006/11/16 2006/10/20EBenjaminFKohGMember^Technical, Binding_52`8a6.3.5 greater details on the individual Information Service Elements and move specific representations such as to the Annex (as being done with XML).c cA a) The definition for jitter is non-standard. In the definitions seen for jitter, it is the max transfer delay minus min transfer delay. This definition of jitter can be derived from the transfer delays and the standard deviation is a useful number. Would suggest to call it the "standard deviation of jitter" and specify equation for same so everyone has a common interpretation. b) for packet transfer delays, it would be helpful to specify the :"population". Maximum packet delay can Bonly be calculated given a certain population. That it, how long must a node measure before it can report the transfer delays? Also, how often do these transfer delays need to be updated? c) How is PER measured in a point-to-multipoint system (like 802.11 or 802.16); if packet is received in error, the packet cannot be attributed to a particular link--since the receiver typically does not know which bits are in error (i.e., error could be in MAC source address). So this could be a dii cAIf MIH Function of mobile node has not received either the media specific broadcast messages, including the information related to MIH Function and capability discovery, or media independent MIH capability broadcast message from the MIH function it may discover MIH function and capability of its peer entities by broadcasting MIH protocol message, MIH_Capability_Discover.request, to either its broadcast domain. In this case, layer 2 data frame with MIH ethertype shall be used for broadcastiBng.@A>  337  }  33>d2336g2274iRonnykMobile can not solicit using unicast address without knowing a MIH peer address. This case mobile nodes should use broadcasting mechanism to solicit a MIH peer. Discussion: response frm MIHF in network would be unicastmRejectedvsee comment 328w Superceded 2006/11/16MarkedMbkAdd three periods (i.e., ...) indicating the missing pieces between PoA3 and PoAk and between PoA2 and PoAnd2144g2263 2006/11/1620EGolmieFNadaGMember^Technical, Binding_52`32a6.3.5bOChange range 0-127 to 1-127 AND decide what action should occur if zero occurs.cthe length value of the Length varialbe first octet cannot take the value of 0. Its range is 1-127. An error should be reported if zero occurs here.d2157g2264wRejected 2006/11/1621EGolmieFNadaGMember^Technical, Binding_55`49a 6.3.5.2.4breplace with applicablecspelling of appliacbled2170g2316wAccepted 2006/11/16EGolmieFNadaGMember^ Editorial_66`47a6.3.7brewrite the sentence starting with " Examples include.." to state "Examples include the Resource Description Framework (RDF) which is based on XML,and a Type Length Value (TLV) representation.EAjayFRajkumarGMember^ Editorial_13`51a5.1.3bKit should be QoS, not QOS (as written multiple times in the current draft).c7Make consistent use of acronym for Quality of Service: d2039g2232 2006/11/16UMTS) NAS Network Access Server (RADIUS)c2NAS Non-access Stratum NAS Network Access Server d2035g2231 2006/10/31 2006/10/23EAjayFRajkumarGMember^ Editorial_13`51a5.1.3bKit should be QoS, not QOS (as written multiple times in the current draft).c7Make consistent use of acronym for Quality of Service: d2039g2232 2006/10/31s, as follows: NAS Non-Access Stratum (UMTS) NAS Network Access Server (RADIUS)c2NAS Non-access Stratum NAS Network Access Server d2035g2231 2006/10/31 2006/10/23EAjayFRajkumarGMember^ Editorial_13`51a5.1.3bKit should be QoS, not QOS (as written multiple times in the current draft).c7Make consistent use of acronym for Quality of Service: d2039g2232 2006/10/31w mbAFigure 8 shows the MIH function for 802.16 based system. The M_SAP and C_SAP service access points are common between the MIHF and NCMS. These SAPs specify the interaction between MIHF and the control and management plane entities respectively and they also help in transporting MIH messages across to peer MIHF entities. The C_SAP specifies the interface between MIHF and the management plane (MLME) and allows MIHF payload to be encapsulated in management message (such as MOB_MIH-MSG). Thus B{primitives specified by C_SAP may be used to transfer packets before and after a Mobile Node has entered network with a BS, whereas the CS SAP may be used to transfer packets after network entry has been accomplished with a BS. The MIH_SAP specifies the interface of MIHF with other higher layer entities such as transport, handover policy engine, layer 3 mobility protocol, etc.i@A>  33B    33>;KjwithoutWwordingWworkWxml[Wxml-representedWyes]Wyes16and17aretherightreferencestordf]Vk1vW2lWvWW21vWW3vW30W36-55W4vW5vW5.1vW6vW802.1W802.21WnW802.21isnotusingmsapnV9NWaW!WvWWWaboutWacceptedWaccessNWactuallyWaddressWNWWWadvertiseWafterWagnosticWakinvWallW!WNWoWalsoWvWWWandlWW!WNWWWWanyvWareWNWWasWvWWWatlWWattachmentWauthenticationWawarevWbe1WlWWWWW!WNWWWWWbecauseWNWvWWbecauseservingfaaddressservingaccessrouteraddressandNVbeforeWbehaviorWbetterWWbigWbothW<EGolmieFNadaGMember^ Editorial_32`50a5.6.1b\Delete 5.6.1.2 through 5.6.1.7 or at a mimimum put them at a lower level under MIH_LINK_SAP.cThis section should only contain the specific MIH LINK SAP and not confuse by adding dependent SAP from a few select technologies at the same level as the MIH-LINK_SAP, since the other technology specific SAPs are mapping to the MIH_LINK_SAP.d2095g2257 2006/11/16EGolmieFNadaGMember^ Editorial_34`40a5.8bDelete section 5.8clThis section discusses Media specific ammendments without stating what they are and therefore is not useful.d2102g2312 2006/11/16EGolmieFNadaGMember^ Editorial_36`35a6.1.1breplace by homogeneousccorrect spelling of homogenousd2106g2313 2006/11/16EGolmieFNadaGMember^ Editorial_37`28a6.1.2bhClearly determine the groupings for events/links/remote/local/and event types and use them consistently ce mapping to the MIH_LINK_SAP.bMIH_NET_SAP should have MIH_TP_Data.{response,confirm}. Introduce the modifications proposed in the submission 21-06-0785-00-0000_MIH_NET_SAP_additional_primitives.doc into the 802.21 draft. cAThe current MIH_NET_SAP does not have MIH_TP_Data.{response,confirm}, and is not capable of accomplishing the acknowledged connection-oriented data transfer. This means that MIHF can not execute retransmission, state synchronization and sequential execution when some failures happen between two MIHFs. Therefore MIH_TP_Data need to support the acknowledged connection-oriented data transfer.d2314g2215wAccepted 2006/11/16 2006/10/23 into the 802.21 draft. c.;~EPeretzFFeder^Technical, Binding_50`50bARemove the above sentense. In un-authenticated stage MN shouldn't be allowed to obtian ALL the IS elements. This will subject the PoA node, air interface and PoS to Denial of Service Attacks. Very limited information should be available in the DL without solicitation.@A>  33W  Z  33>cIt is important to note that before an MN is authenticated with the PoA, the MN should be able to obtain all the 802.21 related information elements available, if needed.d2146g2273vAIt is important to note, that in case of certain access networks, before an MN is authenticated with the PoA, the MN should be able to obtain all 802.21 related information elements available, if needed.@be able to obtain all 802.21 related information elements available, if needed.@ LsjAHelp with English grammar, usage. For Serving PoA ... The network side node currently exchanging link layer protocol with the mobile node. For Target PoA... The network side node with which the mobile node is evaluating the exchange of link layer protocol.mAccepted-ModifiedvServing PoA: PoA of the current link being used by the MN. Candidate PoA: A PoA being evaluated for switching the link. Target PoA: Once a Candidate PoA is selected it becomes the Target PoA. wAccepted-Modified 2006/11/16 2006/10/23MarkedtESubirFDasGMember^Technical, Non-binding_23`58a5.4.3bAcDelete the sentence starting with : "Information available .... L2 connection with the network" c@AR 33& '  a 33R>*eEUlises^Technical, Binding_61`58a6.3.6.1bIf both optional TLVs are absent then the value field of the MIIS_TLV_QUERY should be empty and thus the length field will not take into account the length of the value field.cA$According to this section the MIIS_TLV_QUERY TLV contains an optional Querier Location TLV and an optional Reporting Template TLV. Howeve, in the case that both these optional TLVs area absent, the current draft does not specify how the value field on the MIIS_TLV_QUERY TLV should look like.$d2193g2308is section the MIIS_TLV_QUERY TLV contains an optional Querier Location TLV and an optional Reporting Template TLV. Howeve, in the case that both these optional TLVs area absent, the current draft does not specify how the value field on the MIIS_TLV_QUERY TLV should look like.$d2193g2308t qlcARThe difference between MIH Function Discovery and MIH Capability Discovery is not very clear. Clarify that the capability discovery procedure is performed after the function discovery. In short, the MN first decides to which MIHF peer to associate with from the list of MIHF peer discovered and then performs the capability discovery. Rd2212g2476iRonnyjAAdd the suggesed sentence as following: The MIH Function Discovery procedure can aquire a list of peers that support MIH Function. In certain instances, the MIH node may have a preconfigured MIH peer. In order to know the services that are supported by a MIH peer, the MIH node performs MIH Capability Discovery. The MIH node may perform MIH Capability Discovery with different MIH peer in order to decide which one to register with. When MN uses MIH function discovery using MIH Capability Dis 33E *c +cA^It is not clear why IS is the only service that can support multi-hop operation - why can't ES and CS also operate in a multi-hop mode; there are use cases for this, e.g. remote handover commands from a home network proxied via the visited network. This discussion would sit better in section 8 as it is mainly related to transport of MIH services. ^d2131g2228i Ronny, VivekmAcceptedvTMove it to section 5. Replace all references to IS in this section with MIH Service.wAccepted-Modified 2006/11/16 2006/10/19suitable term). ctency in the delivery of the MIH messages." is untrue. d347g2226 2006/10/31 2006/10/19EEleanorFHepworthGMember^Technical, Binding_47`13a6.3.2bzMove the mult-hop operation discussion to section 8, and change references to IS to MIH service (or other suitable term). c2]EPeretz FFeder^Technical, Binding_154`40bUplink broadcasting message from a terminal makes little sense. Mobile should solicit using Unicast address or the point-to-point link when avaialble.c Very limited information should be available in the DL without solicitation.@A>  33W  Z  33>cIt is important to note that before an NM is authenticated with the PoA, the MN should be able to obtain all the 802.21 related information elements available, if needed.d2146g2273 2006/11/15EPeretz FFeder^Technical, Binding_154`40bUplink broadcasting message from a terminal makes little sense. Mobile should solicit using Unicast address or the point-to-point link when avaialble.c2a6.2.4bFix inconsistencyIH.ccorrect syntaxd123g2314 2006/10/31EGolmieFNadaGMember^ Editorial_44`62a6.2.4bFix inconsistency9WjthereWWtheselWoWWXWthis^WaWWWWWWWWWthisisnotneededbecausetheentitythathassubscribedfoVthisistheformalbasicschemadefinitionandneedstobedVthisistoomedia-specificanddoesnotworkforothermediaVthismaynotbenecesarilytrueinallcaseseitherway802.VthoseoWWthreeWthroughWthroughoutnWtimelWtitleWtlv[WoWNWtlvsWto]W^WaWlWnWoWWWWWWWWWWWWCWXWWWWWWWWWWWWtooaWWtransaction-iddWtransaction-idcandeterminewhichmessageisbeingacknowledVtransportWWWtransportsW DcB--------------------------- d2159g4703k  2006/11/16 2006/10/20EEQiaobingFXieGMember^Technical, Binding_54`4a 6.3.5.1.2b3Clarify the encoding either with a diagram or text.cunclear about how the two fields in the Value is encoded in Table 9. One can only assume that they are two concatenated octet strings - the 1st one has a fixed length 1 and the 2nd one has variable length up to 253. d2161g4704k vxthey are two concatenated octet strings - the 1st one has a fixed length 1 and the 2nd one has variable length up to 253wAccepted 2006/11/16 2006/10/20FEQiaobingFXieGMember^Technical, Binding_54`46a 6.3.5.2.1bAchange to: The value is a non NULL terminated string whose length shall not exceed 253 octets. This is used to uniquely identify the access network. As an example for 802.11 (WLAN) networks this is the ESSID. @A> 33   a 33>KELiuFYuanGObserver^Technical, Non-binding_110`49a7.4.9.2bd "Link_Event_Register.request " for MIH Users and MIHF to register events they concerned at MIH Layer and Link Layer, and by the primitives of "MIH_Event_Register.confirm" and "Link_Event_Register.confirm" , MIH Users and MIHF can know what events have been registered successfully. For the convenience of the implement of the MIH, the query methods for the registered events should be provided also. Through the query methodBs, MIH User can query its registered events from MIH Function and MIH Function can query its registered events from Lower link layers. xd2125g2325iYoshihiro Ohbaj{This is not needed because the entity that has subscribed for particular events is supposed to keep the subscription state.mRejected 2006/11/15 2006/09/22€ATable@A  33ELiuFYuanGObserver^Technical, Non-binding_110`49a7.4.9.2b------- cB class of service as PoA policies may be class of service dependent. Please, see contribution 21-06-0783-00-0000-centralized_NIHO.doc ud2282g2223wRejected 2006/11/16 2006/10/23T 21EAlbertFVidalGMember^Technical, Binding_47`13a6.3.2b;Detailed in contribution 21-06-xxxx-00-0000-ES_CS_Proxy.doccACurrent draft P802.21/D02.00 addresses the multi-hop operation for the Information Service. This comment proposes to generalize the multi-hop operation to the Event Service and Command Service. Please, see contribution 21-06-xxxx-00-0000-ES_CS_Proxy.doc d2132g2224vby 2131w Superceded 2006/11/16 2006/10/23to the maximum data throughput that a user can use, given the data throughput already used by other users and the data throughput the PoA reserves for other potential users, according to its own policies. We also consider this available throughput needs to be specified for every8tjESubirFDasGMember^Technical, Non-binding_36`4a6bAAdd the following descriptions at the end of first sentence: In addition, there is another category called System Management consists of primitives that are required for configuring these three basic three services.@A* 33@ *cdThe overall description of the services should address "System Mangement" (in section 6.4) briefly.d2104g2473iRonnymAcceptedvAjThese services are managed through System Management primitives that are required for configuring tthem..j@A*  33  *wAccepted-Modified 2006/11/16 2006/10/23MarkedModified 2006/11/15 2006/10/23Markede transported over the network, both peer has to have the same decoding methods for both TLVs and IEs. The specification should specify the byte order for the Information Elements.d155g2471 2006/10/31SEEleanorFHepworthGMember^ Editorial_7`1a3b7Remove N-whatever definitions from terminology section.cAHThe use of N-thingy definitions in the terminology section is a little confusing (e.g. the definition of Remote N-trigger). If the "N" is supposed to be read as being substitued by ES, CS or IS, this needs to be made much clearer in the section, and there doesn't seem to be a single instance of their use in the specification.Hd2024g2230 2006/11/16 2006/10/19 to be made much clearer in the section, and there doesn't seem to be a single instance of their use in the specification.Hd2024g2230 2006/10/31 2006/10/19@  cB. The detailed message sequence of sending MIH_Handover_Commit Request to MN and target PoS is not restricted strictly. In figure 31, after the serving PoS receives MIH_Handover_Commit Response message, it send MIH_Handover_Commit Resquest message to inform the target PoS. Then the problem comes. If the target PoS rejects the request of handover via MIH_Handover_Commit Response (with HandoverStatus option set to 0), due to some reasons such as the resources are unavailable now. In curC rent draft, the serving PoS has to way to inform the MN this information, because there is no message exchage between serving PoS and MN, after the MN sent the MIH_Handover_Commit Response. Then the handover would fail, and the service of subscriber would interrupt.d2388g2219vNPlease refer to 21-06-0810-00-0000_Network-initiated Handover Procedure UpdatewDeferred 2006/11/16 2006/10/2331DhEVivekFGuptaGMember^Technical, Binding_61`48a6.3.6b" Specify search radius in queries.on given an observed MAC address (e.g., say from a 802.11 beacon or some such broadcast mechanism for other technologies) b) Maybe the MN doesn't know its current location, but just wants to know if a certain operator or roaming partner is supported on this network. Add a TLV method to make this specific query cA1The TLV-based queries in section 6.3 are driven from location. This makes a lot of sense, but it can be too restrictive as well. Is it assumed that a MN can always determine its location? What if it's not connected to a network/PoA when it needs to make a query (e.g., the MN is just booting up). 1d2188g2232wDeferred 2006/11/16 2006-10-23EVivekFGuptaGMember^Technical, Binding_61`48a6.3.6b" Specify search radius in queries.sERonny^Technical, Binding_69`55a7.2.1.1bAbInsert following text in line 55 - MIH frame transport through contro/management frames (messages)b@A*  33!  *cSince MLME_SAP is in charge of MIH frame transport through control/management frames (messages), this should be described in the draft. d2221g5006vA[Insert following text in line 55 - MIH frame transport through control or management frames[@A* 33!  *wAccepted-Modified 2006/11/16MarkedtERonny^Technical, Non-binding_72`1a7.2.2b6Move 7.2.2.2 and 7.2.2.3 to 7.2.1 Media Dependent SAPs *wAccepted-Modified 2006/11/15MarkedtERonny^Technical, Non-binding_72`1a7.2.2b6Move 7.2.2.2 and 7.2.2.3 to 7.2.1 Media Dependent SAPs/02uERonny^Technical, Non-binding_131`48a7.4.14_131`48a7.4.14tjg4997vAd) MIH_NET_SAP: Abstract Media-independent media-dependent interface of MIHF which provides transport services over data plane on the local node, supporting the exchange of MIH information and messages with remote MIH Function.@A  33    33  , @ ; 33E @ O 33p   33wAccepted-Modified 2006/11/16MarkedkERonny^Technical, Non-binding_26`7a5.5bVRevise figure to distinguish l2 transmission over data plane from over control plane. c> 33  33>cThere is a disconnect regarding the description here. Suddenly saying that "however, the security of this information are outside the scope..." while describing the transport of information d2065g2491vtESubirFDasGMemberngkESubirFDasGMember^ Editorial_47`24a6.3.1b"Change the font used in Figure 19.cFigure 19 is not readable.d2135g2475 2006/11/16 2006/10/23F19lESubirFDasGMember^Technical, binding_67`60a6.4.2 and 6.4.3bA Add the following description into page 68 line 52 in Section 6.4 Following is an example of the system magement primitives work flow: The MIH Function Discovery procedure can aquire a list of peers that support MIH Function. In certain instances, the MIH node may have a preconfigured MIH peer. In order to know the services that are supported by a MIH peer, the MIH node performs MIH Capability Discovery. The MIH node may perform MIH Capability Discovery with different MIH peer in orderBh to decide which one to register with. Following subsections define each of these methods more details. V@A* 33E *cVEGolmieFNadaGMember^ Editorial_66`49a6.3.7b^delete lines 49- starting with "The MIIS schema is classified..." Also delete section 6.3.7.1.c,Definition of categories is not needed here.d2206g2318iYoshihiro OhbajA:The two categories are needed for extensibility, i.e., extended schema can be updated without requiring any specification change while basic schema needs to be supported all MIIS implementations that use RDF query. Also, Section 6.3.7.1 is needed to describe more details on the basic schema and extended schema.:mRejected 2006/11/16EGolmieFNadaGMember^ Editorial_67`41a6.4bCAdd an introduction for the system management service in section 5.ion 6.3.7.1 is needed to describe more details on the basic schema and extended schema.:mRejected 2006/10/31EGolmieFNadaGMember^ Editorial_67`41a6.4bCAdd an introduction for the system management service in section 5. is not needed here.d206g2318!^vaddthefollowinginsection6.3.3Vaddthefollowingtextintopage67line65insection6.423Vaddtheseiesasperthedefinitionsindraftinsection7uVaddthistexteVaddthistothelistVaddtypeiepoaipconfigurationmethodstoreportingtempla8VaddedWadditionalwWadditionallywW06-10-23EVivekFGuptaGMember^Technical, Binding_50`50a6.3.38a6.3.6b" Specify search radius in queries.cIn TLV location query, it seems there should be a way to specify a search radius. If the client knows their present location, it may want to determine the available networks within some distance (e.g. 100m). d189g2233 2006/10/31 2006-10-23EVivekFGuptaGMember^Technical, Binding_50`50a6.3.3EAjayFRajkumarGMember^Technical, Binding_72a7.2.2.2bPMove Section 7.2.2.2 to be a subsection of Section 7.2.1 - Media Dependent SAPs.n his home network while User B has a different cost on that same network because he is roaming. The reverse may be true on User B's home network. Additionally, Users A and B may both have still a different cost if they are both roaming. The current definition of cost and a centralized repository for the value for all accessed networks does not accountB for this.d2164g2223iVivekjThen the MN also needs to specify type of user (Home/Visited) or the network needs to figure this out.... Adds complexity. Should cost for home users be added or is this something more implicit (not needed)..?mQuestion 2006/11/15 2006/10/23EAjayFRajkumarGMember^Technical, Binding_72a7.2.2.2bPMove Section 7.2.2.2 to be a subsection of Section 7.2.1 - Media Dependent SAPs.%YREQiaobingFXieGMember^Technical, Binding_75`16a7.3.2.2bExplicitly show exactly which bit is the Eventlist parameter corresponds to which link event. This comment applies to all eventlist parameter usage.ceEventlist parameter lacks detailed definition. This comment applies to all eventlist parameter usage.d2243g4717k vValue field inadequate.d2180g4716k  2006/11/15 2006/10/20REQiaobingFXieGMember^Technical, Binding_75`16a7.3.2.2bExplicitly show exactly which bit is the Eventlist parameter corresponds to which link event. This comment applies to all eventlist parameter usage.ceEventlist parameter lacks detailed definition. This comment applies to all eventlist parameter usage.d2243g4717k varameter lacks detailed definition. This comment applies to all eventlist parameter usage.d2243g4717k vSEQiaobingFXieGMember^Technical, Binding_89`47a7.3.19.2cal, Binding_89`47a7.3.19.24715k  2006/10/31)ESungjinFLeeGMember^Technical, Binding_154`13a8.3bjThe proposed MIH protocol states are described in the document: 21-06-0xxx-00-0000-MIH_Protocol_States.docc|The MIH states are needed for the correct operation of MIH protocol to allow peer MIHF entities to interact with each other.d2329g2217vsee 330w Superceded 2006/11/16 2006-10-23Marked*ESungjinFLeeGMember^Technical, Binding_158`39a8.3.4.1b2To add Session ID into the MIH frame fixed header.cThe Session ID shall be used in all MIH messages to avoid confict at peer MIHF entities. Session ID and Transaction ID shall be used in conjunction. d2354g2218iYoshihiro Ohbaember^Technical, Binding_158`39a8.3.4.1b2To add Session ID into the MIH frame fixed header.cThe Session ID shall be used in all MIH messages to avoid confict at peer MIHF entities. Session ID and Transaction ID shall be used in conjunction. d2354g2218iYoshihiro Ohbai Vivek GuptajAThis may not be necesarily true in all cases. Either way 802.21 should not strictly mandate transport used by 3GPP and other networks leave it to 3GPP and other networks to decide that. Contributions are being made so that 3GPP networks can provide information baout other networks at L2 as well. "When connected to a 3GPP/3GPP2 network, a Mobile Node may use L3 transport to conduct MIH signaling."@A> 33a d 33>mAccepted-ModifiedvAf"When connected to a 3GPP/3GPP2 network, a Mobile Node may use L3 transport to conduct MIH signaling."f@A> 337 : 33>wAccepted-Modified 2006/11/16 2006/10/23Marked676k  2006/10/31 2006/10/20+EQiaobingFXieGMember^Technical, Non-binding_10`1a4bdelete the unused acronymsc/Unused acronyms: HLSI LLI MDI MII MIHS OUI PMD d2033g4678k Change text to: " - Extended schema that is vendor specific."cInaccurate text: " - Extended schema that is optional and may be vendor specific" Since extended schema should always be vender specificd2198g4727k wAccepted 2006/11/16 2006/10/20]EQiaobingFXieGMember^Technical, Non-binding_64`59a6.3.7.1bfix the referencec[8] is wrong reference to RDFd2200g4728iYoshihiro Ohbaj3Yes, [16] and [17] are the right references to RDF.k mAccepted-Modifiedv3Yes, [16] and [17] are the right references to RDF. _bATChange text to: "The basic schema and their textual description in different formats are included in Annex B. Basic schema is normative and contains a list of mandatory information elements and their properties. Extended schema is defined by individual vendors and may contain vendor specific list of information elements and properties. "Tc1. Annex C should be Annex B 2. extended schema is NOT described in Annex B. 3. "an exhaustive list of information resources and properties" is not accurate (not possible)d2202g4730k vATChange text to: "The basic schema and their textual description in different formats are included in Annex B. Basic schema is normative and contains a list of mandatory information elements and their properties. Extended schema is defined by individual vendors and may contain vendor specific list of information elements and properties. "TwAccepted-Modified 2006/11/16 2006/10/20erties. "Lg4729iYoshihiro OhbaEGolmieFNadaGMember^ Editorial_158`30a8.3.4bVDelete these two sentences since the information is already present in first paragraphcDuplicate informationd2353g2293 2006/11/16EGolmieFNadaGMember^ Editorial_159`36a8.3.4.2bChange caption to MIHF Variable Header Format and remove the HeaderType (4 octets) from figure. Or modify figure 26 to include the combined information to remove inconsistency. PAD, FCS, and Extension included here?d2326g2292 2006/11/0125EGolmieFNadaGMember^ Editorial_158`30a8.3.4bVDelete these two sentences since the information is already present in first paragraphcDuplicate informationd2353g2293 2006/11/01EGolmieFNadaGMember^ Editorial_159`36a8.3.4.2bChange caption to MIHF Variable Header Format and remove the HeaderType (4 octets) from figure. Or modify figure 26 to include the combined information to remove inconsistency.X)dw Withdrawn 2006/11/16Binding_165`1a8.4.1.71b1Provide information about generating the MIHF ID.cHow the MIHF ID is generated and how to avoid confliction and achieve interoperability is not clearly defined. How to make use of this in the discovery process is also unclear.d2349g4733 2006/11/01cEChengFHongGMember^Technical, Binding_165`1a8.4.1.7F ID is generated and how to avoid confliction and achieve interoperability is not clearly defined. How to make use of this in the discovery process is also unclear.d2349g4733 2006/11/01cEChengFHongGMember^Technical, Binding_165`1a8.4.1.7IHF ID is generated and how to avoid confliction and achieve interoperability is not clearly defined. How to make use of this in the discovery process is also unclear.d2349g4733 2006/10/31cEChengFHongGMember^Technical, Binding_165`1a8.4.1.7 -cAThe following amendments should be made to the primitive: 1. Re-registration in MIH_Register.request is not specified in the specs. It may be clarified in a separate primitive. 2. Session ID is not contained in the MIH_Register.response. It is supposed to be created during registration procedures. 3. Need some indication to distinguish the registration between MN and network from that between two networks. d2264g2214wRejectedqin section 8.3.3.2 change Remote registration to remote event subscription... to fix the definition of session-Id 2006/11/16 2006-10-23.EXiaoyuFLiuGMember^Technical, Binding_94`30bTo accept the proposed primitives for MIH Re-Registration is in the Remedy 3 of 21-06-0xxx-00-0000-MIH_Registration_Amendments.doc. c0The primitive for MIH Re-Registation is missing.d2266g2215v.Not clear if we need re-registration primitivewRejected 2006/11/16 2006-10-23/EXiaoyuFLiuGMember networks. )vlistofeventsisdescribedinsection8.3.3.4movethattabVlistedoWlocalWjWlocallyWWlocatedlWlocationWlooknWwWlowerkWWlsapWmac#WWmac/phyWmacaccessrouter#WmachineWmacs_WmadetWmakeuWmanagedjWmanagementjW?WsWmanagmentuWmandateWWmandatory_WmannerWmanyWmapped]WmappingWmarkWmaximizewW7.3.2.237a7.3b)Rename heading to MIH_LINK_SAP PrimitivescHInconsistency with naming which makes it harder to find related materiald2240g2274 2006/11/02EGolmieFNadaGMember^Technical, Binding_75`27a7.3.2.2aGMember^Technical, Non-binding_74`37a7.3b)Rename heading to MIH_LINK_SAP PrimitivescHInconsistency with naming which makes it harder to find related materiald2240g2274 2006/11/02EGolmieFNadaGMember^Technical, Binding_75`27a7.3.2.20vSubir and Xiaoyu will return with revised presentations. See issue # 21-06-0796-03-0000-MIH_Protocol_States.doc This diagram just shows registration state which is quite obvious. Need to combine this with the ACK part.wRejected 2006/11/16 2006-10-23  33>crThe session ID created during MIH registration procedure should be specified during de-registration procedure too.d2267g2216 2006/11/14 2006-10-230EXiaoyuFLiuGMember^Technical, Binding_154`13a8.3 33    33>crThe session ID created during MIH registration procedure should be specified during de-registration procedure too.d2267g2216 2006/11/14 2006-10-230EXiaoyuFLiuGMember^Technical, Binding_154`13a8.30EXiaoyuFLiuGMember^Technical, Binding_154`13a8.32272 2006/10/3116EGolmieFNadaGMember^Technical, Non-binding_73`56a7.2.2.3WEQiaobingFXieGMember^Technical, Non-binding_69`45a7.2.1b;Add a subsection in 7.2.1 for LSAP and CS_SAP, respectivelycYTo be consistent with 7.1.1, need a subsection in 7.2.1 for LSAP and CS_SAP, respectivelyd2220g4722k wAccepted 2006/11/16 2006/10/20MarkedXEQiaobingFXieGMember^Technical, Binding_72`7a7.2.2.2b@Add Link Capability Discover primitive in Table 16 and Table 17 2220g4722k wAccepted 2006/11/15 2006/10/20MarkedXEQiaobingFXieGMember^Technical, Binding_72`7a7.2.2.2b@Add Link Capability Discover primitive in Table 16 and Table 17 ion in 7.2.1 for LSAP and CS_SAP, respectivelycYTo be consistent with 7.1.1, need a subsection in 7.2.1 for LSAP and CS_SAP, respectivelyd2220g4722k wAccepted 2006/11/15 2006/10/20MarkedXEQiaobingFXieGMember^Technical, Binding_72`7a7.2.2.2b@Add Link Capability Discover primitive in Table 16 and Table 17 pectivelyd2220SvList of Commands is described in section 8.3.3.5. Move that table to section 7 and update this part accordingly. Do the same for events as well.wAccepted 2006/11/16 2006/10/20es to all primitive definition.cEffect on receipt must also discuss what will need to happen if the receipient wants to reject the primitive. This comment applies to all primitive definition.d2242g4719k  2006/11/02 2006/10/20appen if the receipient wants to reject the primitive. This comment applies to all primitive definition.cEffect on receipt must also discuss what will need to happen if the receipient wants to reject the primitive. This comment applies to all primitive definition.d2242g4719k  2006/10/31 2006/10/20|EGolmieFNadaGMember^ Editorial_91`52a7.3.21.2b"Fix inconsistency throughout draftc[Inconsistency between name in description and Name columns for Link Data rate or Data rate.d2261g2278 2006/11/16EGolmieFNadaGMember^Technical, Binding_96`39a 7.4.2.1.2bAAdd the following tables: MIH Event ID Event Name ID MIH Link UP 0 MIH Link Down 1 MIH Link Going Down 2 MIH Link Detected 3 MIH Link Parameters Report 4 MIH Link Event Rollback 5 MIH Link SDU Transmit Status 6 MIH Link Handover Imminent 7 MIH Link Handover Complete 8 Reserved  5bc5De-Registrant would be an MIH User, not MIH function.d2274g4688k wAccepted 2006/11/16 2006/10/206EQiaobingFXieGMember^Technical, Binding_193`1aA2bHEither re-do the mapping against MIH protocol PDUs or remove this table.cvOnly PDUs, not primitives, can be mapped to an interface, because primitives don't cross interfaces, they cross SAPs. d2400g4689k vby comment 2395w Superceded 2006/11/16 2006/10/20vents and command IDs. d2270g2232 2006/11/14EGolmieFNadaGMember^Technical, Binding_98`20a 7.4.3.1.2bAdd the following in the Description field: The encoding uses a bitmap where the bit position represents the MIH event ID. A bit set to 1 indicates that subscriber is seeking to subscribe to the event.c8There is no encoding scheme for the RequestedEvent List d2271g2233 2006/11/14EGolmieFNadaGMember^Technical, Binding_98`58a 7.4.3.2.2 bB----------------------------------------------------------------------------------------------- | NO. | MIH Command | (L) ocal, | Remote Direction | Comments | | |(R) emote | | -----------------------------------------------------------------------------------------------------------------------------------------------------------C---------------------------------- | 1 | MIH Get Status | L, R | Network -> Client | Get the status of links -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ~ ~ ~ ~ ~ -----------------------------------------------5wESrinivasF Sreemanthula^Technical, Non-binding_17`5a5.2 (c)bAChange paragraph [c] as follows: " Handover signaling procedure (as part of handover execution and subsequent updates) may is not part of this standard since higher layer (e.g. IP) mobility protocols defined in IETF can be utilized for certain handover types. Additionally, different access network technologies have defined handover signaling mechanisms to facilitate horizontal handover. The role of this specification is to serve as an handover aiding service to maximize the efficiency ofB~ such handovers either by providing intelligent link level triggering information or with additional protocol functionality. "l@Af 33x  33{ 33  33j 33fc@Paragraph (c) inadequate to communicate any useful information. d2049g2236vommenter to provide clarification and justification...wDeferred 2006/11/14 2006-10-23:jrdf[W]WWre-writeWre-writethesectiontofixgramaticerrorseditorialchangeVreadWWWreasonaWreferWWWCWWWWrefertocomment149Vrefertocomment303VCVrefertocomment328Vrefertocomment336Vreferences]WreferredWregisterlWrejectaWvWremedyWWremoteWremoveWremovesection8.2.1entirelyVrenameWreorderWreorderthecolumnsintable-25VisVrepresentation[WWrequiredvWWrequirementsWrequiringWresource[W^WretitleWretitlefigure25transportofmihframeinieee802.3l2daVright]WrouterNWrunWsamelWsatisfyWschema^WWWscopeWsection1W^WWWW3WvWWsecuirtyWself-referentialWsenderdWsentdWsentencelWWWserverNWjelements[WelsewhereaWencapsulatedWencapsulatingWencapsulationWenglishsWenoughvWenoughmodificationsindefn'ssectionthattextisrequiredvVentirelyWentitiesWentityWerrorsWessentiallyWetcWethernetaWethertypeWevaluatingsWevendWeventsWevery*WexampleoWexamples[WexchangesWWexchanginglWsWexistingWexplanationXWextendedWextensibilityWfaNWfactWfigureWWWfindWfixWflowWfollowedWWfollowinglWW3WNWfollowsWforoWsWWWW*WdWWWWWWWforeignNWformalWj-jtrueWtwoWdWWtypenWoWWtypesaWundefinedWunderoWuniqueWunitsWupdatedWupdtaedoWuponWusagesWuseWWWusedWWWuserWWuseridentificationinformationcanbeobtainedbyothermeaVusersWuseslWusing^WlWvalueoWvaluesoWvariable*WwayWweaWwellnWWwgWwhatNWzEAjayFRajkumarGMember^Technical, Binding_25`37a5.5bxb) MIH_LINK_SAP: Abstract media-dependent interface of MIHF with the lower layers of the media-specific protocol stacks.works to decide that. Contributions are being made so that 3GPP networks can provide information baout other networks at L2 as well. "When connected to a 3GPP/3GPP2 network, a Mobile Node may use L3 transport to conduct MIH signaling."@A> 33a d 33>mAccepted-ModifiedvAf"When connected to a 3GPP/3GPP2 network, a Mobile Node may use L3 transport to conduct MIH signaling."f@A> 337 : 33>wAccepted-Modified 2006/11/08 2006/10/23EAjayFRajkumarGMember^Technical, Binding_25`37a5.5bxb) MIH_LINK_SAP: Abstract media-dependent interface of MIHF with the lower layers of the media-specific protocol stacks.= HkmayWmechanismWWmediaWWoWWmemory!WmessageWmessagesizeisabout2130bytesandthisisnotbigasadVmethodWmichaelwmihlWWWWW!WoWvWWWWmihnetsapisforbothl2andl3transportoverdataplaneVmihnetsapusesormapstomihlinksapforalll2interactVoVmihfWWmnWmobileWmobilecannotsolicitusingunicastaddresswithoutknowingVmodificationWmodifiedWmorevWn-entityvWn-layervWname1WneededWNWneedsWnetWWoWWnetworkWvWWWnms!WnoWWWnodesWnotWWW!WnWvWWWWof1WlWWW!WWperformanceWperformedlWplaneWWpoaWWWWWpoashouldbeposVposWpre-configurationWprimitives5 <bAChange the text as follows. The MIH_Capability Discovery procedure is used by a MN MIHF entity to discover the peer MIHF's capabilities in terms of MIH Services (Event Service, Command Service and Information Service)@AR 33Q  33T _ 33RcgMIH_Capability_Discovery procedure is also used by network to discover a MN's MIHFCapability Discovery.d2214g2234vA The MIH_Capability Discovery procedure is used by one MN MIHF entity to discover the peer MIHF entity's capabilities in terms of MIH Services (Event Service, Command Service and Information Service)@AR 338  33; F 33RwAccepted-Modified 2006/11/16 2006-10-2045kprimitivesW!WoWpriorWWO`36a8.3.1.2b[Should be explained as to how to which media specific interfaces this scheme would work on.cIt is unclear as to what is meant by the broadcast domain in the wireless uplink context and how MIHF would "broadcast the MIH protocol message, MIH_Capability_Discover.request, to either its broadcast domain". The description seems media specificd2335g2236iRonnyjARefer to Comment #336 MichaelW: (Accepted Modified) Re-write the section to fix gramatic errors (editorial change). Change the section title to "Solicited MIH Capability discovery in 802 media". Add the sentence: Layer two broadcast mechanisms are inherently media specific. This specification creates a common broadcast discovery method only for the media compliant with 802.1 bridging. Add another section afterward "Solicited MIH Capability discovery in non-802 media" with text: BroadcBVast mechanisms for discovery within non-802 media are defined in other specifications.Dding_154`36'(vof+W1WSW[W_WlWpWsWtWuW~WWWWWWWWWWW#W,W/W3W4W6W9W=W?WSW_WeWjWrWwWyWWWWWWWWWWWWWWWWWoffline+WWointsWokBWoktomntionspecificcommandnamescompareto5.4.2.4BVoldW#Won`WoWWWW!WjWWWWWWWWoncesWonceacandidatepoaisselecteditbecomesthetargetpoasVoneEWPWlWWWW'WWWonlyPWmWWWopcodeWoperatorsWoperatorsdontwanttoexposenetworktopologyandthismayVoptionaleWoptionsuWor[WmWuW#W6WrWsWwW|WWWWWWorderlWWpage[WW!W]WWparagrah,WparameterW jAChange text to read "Suitable amendments are required to existing link layer (MAC/PHY) specifications of different media specific technologies such as IEEE 802.11, IEEE 802.16, 3GPP, 3GPP2, etc. to satisfy the requirements of generic link layer intelligence identified by IEEE 802.21."mAccepted-ModifiedvAChange text to read "Suitable amendments are required to existing link layer (MAC/PHY) specifications of different media specific technologies such as IEEE 802.11, IEEE 802.16, 3GPP, 3GPP2 to satisfy the requirements of generic link layer intelligence identified by IEEE 802.21."wAccepted-Modified 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Non-binding_4`18a1.5bComment: The sentence should not appear as is in the text of the standard. It can instead be kept in the draft as an editorial note until the process in object is completed. vmay_WlWuWW6W=WlWwWWWWWWWWWWmayneedtoaddothernetworktypestothisaswellVWmessageWmessagesRWWjWWmgmtkWmichaeluWmihRW`WWWWWWW!W$W'W4WEWjWlWsWtWWWmihframetransportthroughcontrolormanagementframessVmihissymmetricinnatureandbyitselfdoesnotmandateanVmihlinksapgoestomediadependentcategorytVmihnetsapprovidestransportservicesonthelocalnodesuVmihnetsapstaysinmediaindependentcategorytVmih-handover-commitWmih-handover-commitmih-mn-hocommitVmih-handover-commitmih-nethocandidate-commitVmih-handover-completWmih-handover-completmih-mn-hocompleteVmih-handover-completmih-n2n-ho-completeVmih-handover-initiatWmih-handover-initiatmih-mn-hocandidate-queryV!-vaEW[W^W_WlWmWsWtWwWWWWWWWW$W4WSWlWwWWWWWWWWWapoabeingevaluatedforswitchingthelinksVasimpletlvrepresentationofdifferentinformationelement[VceptW_Waccepted>Wacceptedbylabellinglineaslinkevent>Vaccess~W9WwWxW{WaccesseduWaccordinglyPWSWWvWackWacronymyWacronyms+WyWacrossWSWactionRWadWadd8WRWWWWWWW WW=WeWWWWaddarowforitVaddarowforthisVaddasub-sectioninsection7.4wheremihindicationsbasicVaddanentryforpreferredpoalistVaddbetweenwordsintablesforthesedifferentprimitives VaddhandoverhointhenameVaddmnnetn2nformninitiatednetinitiatedandnetworktoVannexxWWwrejectedU`abiw⪃كۃ$*+-./0:FN^_cdg〃ぃ㉃㏃㑃㒃㔃㕃㖃㗃㘃㛃㜃㞃㟃㠃㡃㲃㳃㹃㻃㼃㾃㿃ƒsuperceded')06JKLVqz} ₃ⴃ⸃⼃⽃⾃ރ )2CDGLQU\hp㇃㊃㤃㩃㱃withdrawncd1`ai{lWWWWWWWWlnoneneededVVVVVVVVneededWWWWWWWWnoneWWWWWWWW€bLink A communication facility or medium over which network nodes may communicate for exchange of L2 messages. Each link is associated with a minimum of two endpoints. Each link endpoint has a unique link layer identifier.cAjLink A communication facility or medium over which L2 network nodes may communicate for exchange of L2 messages. Each link is associated with a minimum of two endpoints. Each link endpoint has a unique link layer identifier. Rationale: Remove the "L2" from "L2 network nodes", since there is no need (and no given definition) for the "L2 network node" notion.jd2026g2242iMichael williamsj006/10/23EAjayFRajkumarGMember^Technical, Binding_7`38a3rms of coverage, data rate and mobility), such as, UMTS to UMTS, or WLAN to WLAN.wAccepted-Modified 2006/11/08 2006/10/23EAjayFRajkumarGMember^Technical, Binding_7`38a3TcVertical handovers This involves MNs moving between access points of different type, such as, UMTS to WLAN. Rationale: Improve consistency across definitions.d2031g2243vnVertical handovers This involves MNs moving between PoAs of different link types, such as from UMTS to WLAN.wAccepted-Modified 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_154`60a8.3.2bThe whole section should be clarified and if the group feels that MIH state machine needs to be defined in the spec then more detailed treatise should be given a separate section.chIt is unlcear MIH Protocol Ack Operation is defining a state machine or implementation specific details.d2340g2244vsee 339w Superceded 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_175`1a8.5.1.3b/Would provide additonal information separately. cjAAgree about the term being undefined. Use of L2 is self-referential. Suggest wording: Link A communication protocol layered directly upon PHY services over which nodes may communicate for exchange of protocol data units. Each link is associated with a physical media connection between nodes that delivers the protocol to the node. Each link node has a unique link layer address. mAccepted-ModifiedvLink A communication layer through which nodes may communicate for exchange of L2 protocol data units. Each link is associated with two endpoints. Each link has a unique identifier.wAccepted-Modified 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_9`48a3b{Vertical Handover Handover associated with a link switch between heterogeneous points of attachment (e.g., UMTS to WLAN).*Sjagreeaboutthetermbeingundefineduseofl2isself-referVaidWvexistingWexpectsuWexplain`WWexplanation/textWexposeWextended_WfacilitatewWfacilitatingwWfaihure%WfailureWfieldeWntofthemihfwithinthemobilityVfigure-1Wfit`Wfits`WfixWfixedEWflowWflowsxWfollowMWfollowingWsWWfollows=Wfor+WRWSWjWsWuWWWWWWWWWWW W4W=W]W_WkWlWwWyWWWWWWWWfortransportoverdataplaneal2lsapprimitiveswhichareVformat=Wforwarded6WframesWframessWWframework`WfromRW`WWWWW'W,W6WxWWWWfunctionWWjWlWfunctionalitywWfunctionsSWfurtherWgwWgeneratedW'WgenericWgetMWgivingWgoestWgood$Wgroup=WwWV 8ESrinivasF Sreemanthula^Technical, Binding_40_17`5a5.2 (e)bpWe review if the above are covered adequately in the later sections. Need different sections to cover the above.c(e) The standard shall specify mechanisms to support MN-initiated, MN-controlled, network-initiated and network-controlled handovers. Does it?d2050g2237vIts up to upper layers to figure out how to utlize services provided by .21. Commenter needs to provide more details on problem and remedy.wDeferred 2006/11/14 2006-10-23 2006-10-23d is used in spec which is overlapped in terms of defn. 6. Not a protocol defnintion term. Something more akin to control plane vs. data plane is used. mRejectedvIf these are NOT being used anywhere else in document...delete these. Editor to check and do accordingly. 2.N-Entity 3. N-Event 4. N-Layer 5. N-User 6. Remote N-Trigger 7.Peer N-entitywAccepted-Modified 2006/11/08 2006-10-23wESrinivas#2kfall!WfigureWfigureinthecontributionhelpsunderstandthefunctionofVfor1WlWWWW!WNWoWvWWWWWformalizationvWframeWWWWfrmWfromWfunctionlWWWfunctions!WgWgeneralWget!WWgiven1WhandoverWWhard/softvWhasWhave!WheavilyvWheavy!Whelpful!WhelpsWhoweverWiWieWieeevWWiesWietfvWifWinlWWWW!WvWWWWincaseofusinglayer2transportformihfunctiondiscoverlVincludedWindicateWinformation!WWWinteractionsWoWinto!WintroductionvWipNWWWis1WWW!WNWnWvWWWWWitWWvWWitisbettertoseparatel2transportoverdataplanefromlVitsWkofvWWWWWoffersvWonlyWvWWoperation!WorWoWvWorder!WotherWoWvWoverWWoverlappedvWpacketWparlancevWpart1WpeerWperformanceWperformedlWphy-onlyWplaneWvWWpoaWWWWWpoashouldbeposVportionsWposWpre-configurationWprimitives7ANksomewhat!WspecWvWspecificWspecifyWstandardWvWstandardsvWstate!Wsubscription!WsuchvWWsuggestvWsuggested!WWsupport!WsyntacticWsystem1Wsystemmanagementcanbepartofcommandservicebutdiffere1VtcpWtermWvWtermsvWtextWtextoflines36-55hasmanysyntacticerrorsthistextalsoVthelWWW!WvWWWWthefunctionsdefinedbythecommenterseemtofallintocat!VtheportionsoftheframedescribingthemacencapsulationoVthereWWWthisWW!WoWWWWtimelWtlvNWtoWWW!WoWvWWWWWWWWtoo!WtransportlWWWW%DvrequiredjWuWWrequirementsWrequiresWreservedRWWWresolution1W Wresource[W^WresourcesWrespectivexWresponseUWresubmit+Wresubmitinnextroundaftermoreofflinediscussionandhar+VresubmittedgWretrievalWretrievedWreturnUW0Wrevised0WrevisionWrewordxWright]WriskWroaming9WroleWwWronny'slWroundpWwW+WWWrouter's#WrowRWWWWrowsmWrssiWsalientWsameSWlWWWWW_WWsapWWW!WjWtWsapsWsatisfyWsay$WscanWscanrequestsetsWscenariosuWschema[W^W_WWsectiionWsection1W)W0WGW_WdWhWWWsee2325Vsee325Vsee328Vsee330)VhVsee339 VVsee339and341dVsee345GVetcWhether the information is sensitive or not will depend upon the information service provider. Also it is not clear the realtionship between "less sensitive information" and "quick handover".d2064g2490vInformation available through the non-secure port would allow a network selection decision to be made before incurring the overhead of authentication and the establishment of a secure L2 connection with the network. wAccepted-Modified 2006/11/16 2006/10/23MarkeduESubirFDasGMember^Technical, Non-binding_23`65a5.4.3bAZHowever, the transport security of this information is outside the scope of IEEE 802.21.Z@A> 33  33>cThere is a disconnect regarding the description here. Suddenly saying that "however, the security of this information are outside the scope..." while describing the transport of information d2065g2491vabvsuitableWsupportlWWxWsupportedlWWsupportedcommandlistWingsWsymmetricWsystemjWt`WtableSWWWWWWtable-17]Wtable-19W!Wtable-19onpage74hasmihnmssapprimitiveswhicharenot!Vtable-25RWtables WtargetsWtargetpoasVtechnologieswWWtechnology_WtermsWtextbW|WWWWW]WcWsWWWthanWthatRWSWjWW$WWthat'sUWthat'sexactlywhatwedidincomment2256UVthe7WRWSW`WsWtWuWWWWWWWWWWWW,W4W_WjWlWwWxW{WWWWWWWWWthefigurebasicallyshowshowcommandsarebeinginitiatedVthemacshaveenoughstatetoknowthedifferencebetweenli_VtheirxWthemWWthenWthereWy #vcandidatesWWcandidatepoasVcandidate-commitWcandidate-queryWcannot_WcapabilitiesW=WcapabilitylWWWcapscWcaption4WcaptureWcarrieduWWcaseuW~WWcasesuWlWWWcategorytWcertainlWuW~WlWwWWWcertifications=WchangePW[W^W_WgWmWnWWWWWWW%W,W4W9WEWkWzW|WWWWWWchangeabortreasontoerrorcode%Vchangeasfollows^Vchangedescriptionofentry1.2intable-6toincludeaccess9Vchangeinfoquerytypetoisquerytypelistin8.4.1.35and8nVchangelowerlayertransporttodatakVchangepoatoposandalsothedescriptonforthisinthetaVchanger1tor1/r3/r4/r5aswellzVchanger3/r4/r5tor1/r3/r4/r5zVtworkorothercorenetworks|VchangedWchangesWchannelWW )vitselfWituWituy1540/1541Vitu-tWjustW0WyWWWWjustifcation_WkbpsNWkeepW!WyWkeepmihnmssapdefineprimitivesappropriately!VkeepthishereforconsistencyVkeyWknowlWuWWlWWlabel?Wlabellineclearly?Vlabelling>Wlater}WlayeruWWkWwWWWWlayersWSWxWWleave,WlengthEWeWlessuWlevelRWwWlimiteduWline>W?W[WsWlink>WsWWWWW'W_WtWwWWWWWWWWlinkacommunicationlayerthroughwhichnodesmayVlinkidentifierchannellinkidentifierisnetworktypemacaVlinkidentifierWWlinkparameterlistWlinkparameternamelisWlinksWlistRWSW_WlWWWWlistofcommandsisdescribedinsection8.3.3.5movethattSV* vAMIH is symmetric in nature and by itself does NOT mandate anything special on any one node. As such from MIH perspective the peer node need NOT assume any other role.. MIH is independent of network topologies as well. The current Communication model reflects the infrastructure based network. Sectiion 5.3 add: "The following sections describe the key and salient .oints with regard to MIHF communication between MN and infrastructure based networks " wRejected 2006/11/16 2006/10/20MarkedIvexchangeWjWWexchanginglWlWexecutionwW#vcheck+WvWyWchoiceWclarificationWWcleariW#W.Wclearly?WRWclearlyshowthebitlevelpositionforeacheventherealsoRVcleraWcnyWcncorenetworkjustkeepascorenetworkyVcolumnoWWWcolumnsWcombine0WcomewWcommandBWW?WWcommandsRWSWWxWWWcomment'W)W0W1W6WJWKWLWVWqWyWzW}WWWWWWWW WWW,W2WLWQWUW\WpWWWWWcommenter`WcommentspWcommitWcommunicateWcommunicateforexchangeofl2protocoldataunitseachlinkVcommunicationWkWWWcompareBWcompleteWWcompletion6WcomprehensivewWconcatenatedEWconceptpWconceptualSWconductWWcorrespondsRWcoverageWcreatedWcurentcWle4WGswaccepted-modifiedz{|ゃㅃㆃ㈃㙃㢃㨃㫃㬃㭃㮃㯃㰃㴃㵃㶃㸃deferred uvADeferred to Michael. " IEEE 802.21 protocol may be transported within L2 protocols. IEEE 802.21 protocol may be carried via an L3 transport. In the case where L2 protocol transport is not available, L3 must be used to obtain MIIS. If the information within the MIIS is administratively limited to contain less content when accessed via an L2 transport , the information required by the mobility managment entity may not be available or sufficient to make intelligent handover decision. InB such cases, higher layer information service is also required. The security of the MIIS data must be provided by the transport. " In certain scenarios information over L2 may not be available to make intelligent handover decision. In such cases, higher layer information service is required. Thus IEEE 802.21 enables both L2 and L3 transport options for this information and expects the transport to provide security for this information.wAccepted-Modified 2006/11/16 2006/10/23vincurringtWindependentWtWWindicateWWindicating6WindicationuWindicationsWindividual_WWinfoqueryresponseEWinfoquerytypenWinformation[W_WmWtWuW~WWWW&WjWwW{WWWinformationavailablethroughthenon-secureportwouldallotVinformativeWinfrastructureWinitiateWinitiatedWxWWinitiatesWinsertWsWinsertfollowingtextinline55sVinserttheabovetableVinstanceslWinsteadWintegerNWOWintelligenceWintelligentuWwWintentWinterestWinterfacejWWinto`W3Wintra_WinvalidUWWWWW#W$W&W'W,W/WwWWWWWWisn'tWissue0WWWissuecreatedforsection8VitIWOWRWsW~WWWWWW,WWW "vto1W8WBWEWMWRWSWTW]W_W`WaWgWiWlWmWnWoWpWtWuWyW~WWWWWWWWWWWWWWWWW#W$W%W'W,W0W6W9WEWSW]W_WdWgWkWlWrWtWvWwWxWzW{W|WWWWWWWWWWWWWWWWWWWWWWWWWWtobesocializedandresubmittedgVtobesubmittedaftermoreharmonizationdVtoconductmihsignalingVtogetherwWtopologiesWtopologyWtransportuWWWjWkWsWWWtransporteduWtransportsiWment2071/2072 VusedsWuWWvWWuseful#WWWuser'WWusesWusingaWWusingethernettoconrofmtoradiusaVutilizedwWutlizexW] bA;1. Delete "L2 Transport" in the MIH_NET_SAP" 2. Change the text d) as follows d) MIH_NET_SAP : Media-independent interface which provides L3 transport services on the local node, supporting the exchange of MIH information and messages with remote MIH Function;@A> 33 3333 33>cMIH_NET_SAP seems to be used in L2 and L3 transport services but MIH_LINK_SAP is also used for L2 transport, which is duplicated and confusing.d2072g2230iRonnyj0Please refer to Comment #71 for suggested remedykV?V@VCVDVEVFVGVJVKVLVNVOVRVSVUV\V]V^V_V`VaVbVcVdVeVfVgVhVjVmVoVpVqVsVzV{V|V}V~VVVVVVVVVVVV*vmobilityWmobility-managementWmodel`WW4Wmodifications=Wmore`WlWwW+WdWWWWmove1WSWWWWW,Wmoveittosection5replaceallreferencestoisinthisseVmovesection6.4before6.11VureWneed`WbWWWW.Wneedmoredetailsfromcommenteronhowthemodeldoesnotf`VneedtextbVVneededWneedsWnetWWjWtWWnetworktWWW4WlWwWxWyW|WWWWWWnetworktomnVnetwork-networknetworksWlWxW{W|WnewWW#W6Wnext7Wnms!WnoRW#W/WnodeWWjWlWWWnodesWnon-accessyWnon-securetWnormative]Wnot`WuWWW!W#W$W,W.W_WcWlWvWwWfulorrelevantto#VnoteeW#Wnumbering,W kAThe portions of the frame describing the MAC encapsulation of the MIHF frame cannot be used as described with wireless MACs. Separate drawings would be needed. Also, it is not required to indicate PHY-only portions of the frame. Also, there are no drawings for the cellular link types. Also, the term General Packet Frame is not exactly defined in the spec, it is General Frame only.mAccepted-ModifiedvRemove section 8.2.1wAccepted-Modified 2006/11/16 2006/10/19Markede the MIH protocol. This ethertype can be used when encapsulating MIH protocol in L2 transports. The MIH protocol general frame is opaque to the transport.)klso be used with a standard L3 protocol (UDP/TCP) with a well defined MIH port as well." with "The same frame structure may be used within any L3 transport solution, with additional encapsulation required by the transport."9cEGolmieFNadaGMember^ Editorial_152`23a8.1bwill provide text latercNIntroduction paragraph contains many grammatical errors and needs to be fixed.d2321bEChengFHongGMember^Technical, Binding_156`17a8.3.3.1b1Provide information about generating the MIHF ID.cHow the MIHF ID is generated and how to avoid confliction and achieve interoperability is not clearly defined. How to make use of this in the discovery process is also unclear.d2349g4733v Need text.wRejected 2006/11/16MarkedcEChengFHongGMember^Technical, Binding_165`1a8.4.1.7bKDefine a self-contained MAC Address field that can indicate the type used. cwHow to parse the MAC address field? If it is variable, how would the receiver know the type of the MAC address in use? d2363g4734w Withdrawn 2006/11/16dEChengFHongGMember^Technical, Binding_165`23a8.4.1.9bDefine how to parse this field, especially, how would the receiving end know which type is used, or find the boundary of the field.c^How would the receiver know if a IPv4 or IPv6 address is used in this element is not defined. d2364g4735ja[W^WlWWWWasimpletlvrepresentationofdifferentinformationelement[Vabout[WWWaboveWacceptedWaccessNWacknowledgeddWactionWactualoWaddlWWW3WWaddtextto8.2aroundpg153line12aftertable23Vaddthefollowingtextintopage67line65insection6.423Vaddthefollowingtextintothebeginningofline23page15VaddthesuggesedsentenceasfollowinglVaddedWaddressNWWaddress/accessNWaddress/dhcpNWaddsWafterWafterwardWagentNWagreeaWWFSjagreeaboutthetermbeingundefineduseofl2isself-refer@all@* vkADiscussion: Because .21 offers MAC-like service to any layer/user (not just MAC or network layer) it facilitates cross-layer design. As such the formalization of N-layer terms is useful for other documents looking for standards for such terms. 1. hard/soft used in 5.1 introduction only. Suggest leave in def'n as is or re-word within 5.1. 2. N-entity used in various defn's only. Not aware of standard term within IETF or IEEE parlance. Suggest leave in def'n as is or re-word defns. 3.B See 2. 4. See 2. 5. See 2 but more heavily used. Also, MIH user is used in spec which is overlapped in terms of defn. 6. Not a protocol defnintion term. Something more akin to control plane vs. data plane is used. mRejectedvIf these are NOT being used anywhere else in document...delete these. Editor to check and do accordingly. 2.N-Entity 3. N-Event 4. N-Layer 5. N-User 6. Remote N-Trigger 7.Peer N-entitywAccepted-Modified 2006/11/16 2006-10-23MarkedwOEAjayFRajkumarGMember^Technical, Binding_3`58a1.3bWhen the information originates at a remote network element, the MIHF on the local network element obtains it through MIH message exchanges with a peer MIHF instance that resides in the remote network element.cw Superceded 2006/11/08 2006/10/23EAjayFRajkumarGMember^Technical, Binding_3`58a1.3bWhen the information originates at a remote network element, the MIHF on the local network element obtains it through MIH message exchanges with a peer MIHF instance that resides in the remote network element.ctwo broadcast mechanisms are inherently media specific. This specification creates a common broadcast discovery method only for the media compliant with 802.1 bridging. Add another section afterward "Solicited MIH Capability discovery in non-802 media" with text: BroadcBVast mechanisms for discovery within non-802 media are defined in other specifications.D/jeditorialWeitheraWXWW:vjspecificationsWWspecifyWspell-checkerWstate!WWstrictlyWsubscribedWsubscriptionWsubsectionslWsuchWWWsufficientXWsuggesedlWsuggestWsuggestedWWsuitableWsupportlWsupportedlWWsupposedWtableaWWtable8pgdefinesnetworktypeswhichwecalllinktypeselaVtable-25Wtable-26oWtargetsWtechnologiesWtermWterminologyWtextWWWW3WNWvWWWthanWWthatlWWvWWWW cACAlthough section 8.1 describes the L3 transport as being out of scope, the text here appears to provide implementation suggestions about how this would be designed. In addition, the text is confusing because it decribes transport at L3 but refers to IETF transport protocols which are generally considered as being at L4. Cd2325g2220iMichaelWjA)Remove section 8.2.1 entirely. Add text to 8.2 around pg 153 line 12 (after Table 23): There is an IANA ethertype number assigned to indicate the MIH protocol. This ethertype can be used when encapsulating MIH protocol in L2 transports. The MIH protocol general frame is opaque to the transport.)k Replace "The same frame structure may also be used with a standard L3 protocol (UDP/TCP) with a well defined MIH port as well." with "The same frame structure may be used within any L3 transport solution, with additional encapsulation required by the transport."9cBvvalueoW_WeWWvaluesmWoWW%WvariableEWvendor_Wvendors_WverticalWverticalhandoversthisinvolvesmnsmovingbetweenpoasofVveryWviauWvoteWvsWw`W9WwaitingWwaitingfortextfromsubirandmiriamadhocconfirmsackiVwantWwasWwayWwaysWW=WUW_WwellSWnWWWWWW!W]WxWzWWWwhatRWUWWwhenlWuW'WlWWWwhenconnectedtoa3gpp/3gpp2networkamobilenodemayuseVwhenconnectedtoa802networkamobilenodemaydirectlyulVwhentheinformationoriginatesatlowerlayeroftheprotocVwhereRWuWWlWwhichlWW!W0WjWxWWWwhy#Wwifi=Wwill0WeWwirelessWwith1WMWlWmWtWwW~WWWWW0W4W9WjWlWyEVivekFGuptaGMember^Technical, Binding_166`1a8.4.1.12bb Rename section 8.4.1.12 to CurrentLinkIdentifier and add another section for New Link Ifdentifierc_ Add TLV description for CurrentLinkIdentifier and New Link Identifier as specified in Table-26d2366g2245ould be broadcast periodically over the air.;d2328g2225iRonnykA!Message size is about 21~30 bytes and this is not big as a data frame. This is for the MIH entity sitting in the network. Because this entitty is agnostic to PoA, PoA can not advertise MIH capability of the MIH entity and also layer 2 data frame is recommended to be use by the MIH entity.!mRejectedvIssue created for section 8wDeferred 2006/11/16 2006/10/23EAjayFRajkumarGMember^Technical, Binding_154`49a8.3.1.2bIf MIH state machine needs to be defined in the specification then it should be defined more completely rather than piece meal else the above description should also be removed.n1EXiaoyuFLiuGMember^Technical, Binding_175`1a8.5.1.3bbTo accept the proposed Remedy 4 in the document 21-06-0xxx-00-0000-MIH_Registration_Amendments.docc7MIH Re-registration message format shall be added here.d2378g2219w Withdrawn 2006/11/16 2006-10-232EXiaoyuFLiuGMember^Technical, Non-binding_193`1aAnnex A1bYSee the updated flow charts in the 21-06-0656-01-0000-WLAN_WMAN_HO_Procedures_update.doc cTAdd a section for the example handover scenarios between 802.11 and 802.16 networks.d2396g2222vby comment 2387w Superceded 2006/11/16 2006-10-23rawn 2006/11/16 2006-10-232EXiaoyuFLiuGMember^Technical, Non-binding_193`1aAnnex A1bYSee the updated flow charts in the 21-06-0656-01-0000-WLAN_WMAN_HO_Procedures_update.doc cTAdd a section for the example handover scenarios between 802.11 and 802.16 networks.d2396g2222vby comment 2387w Superceded 2006/11/16 2006-10-23]'5EPeretzFFeder^Technical, Binding_154`30ceived either the media specific broadcast messages, including the information related to MIH Function and capability discovery, or media independent MIH capability broadcast message from the MIH function it may discover MIH function and capability of its peer entities by broadcasting MIH protocol message, MIH_Capability_Discover.request, to either its broadcast domain. In this case, layer 2 data frame with MIH ethertype shall be used for broadcastiBng.@A>  337  }  33>d2336g2274iRonnykMobile can not solicit using unicast address without knowing a MIH peer address. This case mobile nodes should use broadcasting mechanism to solicit a MIH peer. Discussion: response frm MIHF in network would be unicastmRejectedvsee comment 328w Superceded 2006/11/08EPeretzFFeder^Technical, Binding_154`30vaRename section 8.4.1.12 to CurrentLinkIdentifier and add another section for New Link IfdentifierwAccepted 2006/11/16 2006-10-23 Link Ifdentifierc_ Add TLV description for CurrentLinkIdentifier and New Link Identifier as specified in Table-26d2366g2245 2006/11/15 2006-10-23 !kAThe functions defined by the commenter seem to fall into category of command service. Defining a separate SAP for link command is not helpful. MIH_NMS_Get_State operation is somewhat duplicate of event subscription. NMS can be a MIH User and may register to receive primitives. In order to support the suggested operation of MIH_NMS_Get_State, MIH should have memory to keep all information for primitives but this is too heavy operation for MIH. mAccepted-ModifiedvTable-19 on page 74 has MIH_NMS_SAP primitives which are NOT described anywhere as well. Keep MIH_NMS_SAP. Define primitives appropriately. Add: - MIHInitialize - MIHGetState - MIHReset wAccepted-Modified 2006/11/16 2006/10/2312%vsee6.4.2page67Vseecomment248Vseecomment328Vseeissue4foroverallprotocolstatemachinediscussionVseeksWseemsWcWselectedsWselectiontWWsentence7W[WrWxWWWseparatemWWWseparatelykWsequencesWservewWserverWserviceuWWWWW?WwWWservicesjWlWWW4WjWxWservingsW6WignalingwWWsignallinglWsince,WwWsingleWsnrWsoW$Wsodontsayanythingaboutthatinthissection$VsomeWspecialWspecificBWWspecificationwWspecificationsWspecified WspellyWstackWWWstandardwWstandardsxWstate_WWstatedRWstaystWstill#WstratumyWsub-sectionWsubir0WWsubirandxiaoyuwillreturnwithrevisedpresentationssee0Vsubmit]WevAdd a sub-section in section 7.4 where MIH indications basically refer to corresponding link layer indications........ If the description is not there for a link layer event then it may need to be added. wAccepted 2006/11/16Marked15EGolmieFNadaGMember^Technical, Non-binding_72`9a7.2.2.2bAdd missing primitivec[Link Capability Discovery is not listed in the table, but present in text 7.3.18 and 7.3.19d2234g2272vby 2233w Superceded 2006/11/16Marked16EGolmieFNadaGMember^Technical, Non-binding_73`56a7.2.2.3b)Add prefix MIH before each Primitive namec1Naming inconsistency with table and section 7.6.xd2237g2273v>This applies to Table-19 as well. Please fix table-19 as well.wAccepted 2006/11/16Marked18EGolmieFNadaGMember^Technical, Non-binding_74`37a7.3b)Rename heading to MIH_LINK_SAP PrimitivescHInconsistency with naming which makes it harder to find related material @bcWhen the MIHF in the new PoA receives this message from the network entity, the MIHF in the new PoA further delivers this message to the MIHF in the old PoA. When the mobile node receives this primitive,d2307g2277iRonnyjRefer to comment #303m Supercededvby 2303w Superceded 2006/11/16H_LINK_SAP goes to Media Dependent category.... MIH_NET_SAP stays in Media Independent categorywAccepted-Modified 2006/11/08uERonny^Technical, Non-binding_131`48a7.4.14.4.14  bAAdd "_" between words which consist of the name of primitives and messages in Table 15-MIH_SAP Primitives, Table 16-MIH_LINK_SAP Primitives, Table 17-MIH_LINK_SAP Primitives Mapping, Table 18-MIH_NET_SAP Primitives and Table 25-MIHF Messages and wherever it needs to be changed.cThe names of primitives and messages need to be consistent throughout the specification. For example, if we decided to use "_" between words which consist of the name of primitives and messages, use it everywhere in the textd2223g2233v@Add "_" between words in Tables for these different primitives. wAccepted 2006/11/16 2006-10-20Marked15RajTable 8 pg defines network types, which we call "link types" elsewhere. It calls out Ethernet too, giving the reason of compatibility with RADIUS. Either change Table 8 and 23 to agree as 802.3, or reject this comment.mAccepted-Modifiedv#Using Ethernet to conrofm to RADIUSwRejected 2006/11/16Marked23ix MIH before each Primitive namec1Naming inconsistency with table and section 7.6.xd2237g2273v>This applies to Table-19 as well. Please fix table-19 as well.wAccepted 2006/11/0818cal, Non-binding_73`56a7.2.2.3b)Add prefix MIH before each Primitive namec1Naming inconsistency with table and section 7.6.xd2237g2273v>This applies to Table-19 as well. Please fix table-19 as well.wAccepted 2006/11/0818Technical, Non-binding_74`37a7.3b)Rename heading to MIH_LINK_SAP PrimitivescHInconsistency with naming which makes it harder to find related materiald2240g2274wAccepted 2006/11/02wcThe MIH_LINK_SAP is listed here as a subsection of the Media Independent SAPs. However, the MIH_LINK_SAP is listed in the introduction (Section 7.1.1, p 69) as a Media Dependent SAP. The latter is correct.d2229g2224wAccepted 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_154a8.3.1.1bSuch a Response as defined in the spec can be fairly large and quite a bit of 802.16 air resources can be consumed. The amount of infomation broadcast should be restricted to a few (1-2) bytes stating the Access Network capabilities only.cA;"MIH function entity in the network may broadcast its existence and capability by broadcasting the MIH protocol message, MIH_Capability_Discover.response, periodically over layer 2 data frame." - currently the draft spec states that an MIH_Capability_Discover.response could be broadcast periodically over the air.;d2328g2225iRonnyk!52 2006/11/16 2006/10/20MarkedW cAFigure 1 shows the placement of the MIHF within the mobility management protocol stack for handovers associated with heterogeneous link switches. Rationale: The current text is confusing, because it makes MIHF appear as if it was present in the mobility management protocol stack only when handovers associated with heterogeneous link switches take place. Instead, the MIHF is placed in the protocol stack independently of whether heterogeneous link switches will actually occur. The final porBtion of the proposed text is to distinguish the picture from the case of an MIH Network Entity that resides deep inside the network (e.g., an MIIS server) and does not support any of the access media covered by MIH (listed in Figure 1).d2014g2235vqFigure 1 shows the placement of the MIHF within the mobility-management protocol stack of a MN or Network entity.wAccepted-Modified 2006/11/16 2006/10/23MarkedEAjayFRajkumarGMember^Technical, Binding_154d2240g2274wAccepted 2006/11/16MarkedEGolmieFNadaGMember^Technical, Binding_75`27a7.3.2.2bMove table in section 8.3.3.4 to section 7.3.2.2 and add a table number. Update Description to fit the Event ID defined in the table (i.e bit 0 is now Link UP).cWThe encoding uses a bitmap but the definition of each bit is not defined in the draft. d2244g2220vq List of events is described in section 8.3.3.4. Move that table to section 7 and update this part accordingly. .wAccepted-Modified{l) none needed 2006/11/16EGolmieFNadaGMember^Technical, Binding_76`10a7.3.3.2bqIf comment 3 is approved, update Description to fit the Event ID defined in the table (i.e bit 0 is now Link UP).cWThe encoding uses a bitmap but the definition of each bit is not defined in the draft. d2245g2221v&by 2244. The same remedy should apply.w Superceded{l) none needed 2006/11/16EGolmieFNadaGMemberaGMemberx RvAThis has been described in detail in the TLV part in section 8.3.3 where IDs are defined for each event. Clearly show the bit level position for each event here. Also add that to Also in Table-25 add another row : Reserved for MIH messages from 22-1023 (10 bits). Also the No in Table-25 are Action IDs. This should be clearly stated. In TLV definition for events and commands list...describe each bit position clearly as to what event/command it corresponds to.. wAccepted-Modified 2006/11/16 2006/10/20MarkedSEQiaobingFXieGMember^Technical, Binding_89`47a7.3.19.2bExplicitly show exactly which bit is the Commandlist parameter corresponds to which link command. This comment applies to all eventlist parameter usage.ciCommandlist parameter lacks detailed definition. This comment applies to all Commandlist parameter usage.d2253g4718k vidsRWie8WUWmWWieeeuWWiesWWietfMWwWifUWiWuW~WW.WeWvWWifbothoptionaltlvsareabsentthenthevaluefieldoftheeVifthereareinvalidierequestsinqueryreturnerrorandnUVifthesearenotbeingusedanywhereelseindocumentdeletevVifdentifierWimminent_Wimminent/complete_WimplicationsWimportant~WimprovementWin+WMWRWSWUW[W_W`WiWlWmWnWoWpWuWwW~WWWWWWWWWW WWW#W$W+W,WWWWWinfigure3changezVinfigure5kVinsection7.3.20.2removerssisnrc/iberdataraterowenVinsection7.3.7.2andthetablebelowitchangelinkparametVinclude[W9WWincludeappropriatedefinitionsforotherlinksaswellVincluded_WiWincompleteWAEEunahFKimGMember^Technical, Binding_25`42a5.5b upper layers to MIH function or MIH function to lower layers. It is rather achieved by the interaction between upper layers and MIH function, or MIH function and lower layers.d2011g2221i Vivek GuptajACommands essentially flow from higher layers to lower layers and this terminology has been consistently followed in the draft. The interaction referred above is more with "remote" entities rather than with local entities. Hence the figure should be left as is.mRejectedvThe figure basically shows how commands are being initiated. Upper layers initiate commands locally within a stack, and Figure-1 just shows flow for a single stack only.wRejected 2006/11/13 2006-10-20Marked1EEunahFKimGMember^Technical, Binding_25`42a5.5b 2006/11/16^Technical, Binding_90`6a7.3.19.2bJMove table in section 8.3.3.5 to section 7.3.19.2 and add a table number. c8There is no encoding scheme for the set of command IDs. rType} but does not define the format. d2249g2228 2006/11/02EGolmieFNadaGMember^Technical, Binding_90`6a7.3.19.2bJMove table in section 8.3.3.5 to section 7.3.19.2 and add a table number. c8There is no encoding scheme for the set of command IDs. Gv8.4.1.20W8.4.1.20seemstobeincompleteaswellalsoseemsoddtohaV8.4.1.35nW8.4.1.36nW8.5.1oW8.5.2oW8.5.3oW8.5.4.1nW8.5.4.2nW802lW802.1/802.3]W802.11=WW802.16W802.1ag]W802.21gWiWuW~W]WW802.2ah]WjwAccepted-Modified 2006/11/16MarkedEGolmieFNadaGMember^Technical, Binding_90`6a7.3.19.2bJMove table in section 8.3.3.5 to section 7.3.19.2 and add a table number. c8There is no encoding scheme for the set of command IDs. d2254g2229vby comment 2187w Superceded 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_90`54a7.3.20.2bAdd a row for PERcJPER is listed under the description, but not listed as an item under Name.d2255g2276wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_90`54a7.3.20.2bEmake definitions of LinkParameterList consistent throughout the draftcmLink Parameter List is inconsistent with previous definition in section 7.3.7.2 for Link_Configure_Thresholdsd2256g2321vIn section 7.3.20.2 Remove RSSI, SNR, C/I, BER, Data Rate row entries from the table. Do the same in section 7.3.21.2 (Move them to a separate table in this case).wAccepted-ModifiedvcurenttextseemscorrecteditorialnotshouldnotbeincapcVcurrentsWWWWWWWcurrenttextpermitsthisVcurrentlinkidentifieWdjWdmihnetsapabstractmedia-independentmedia-dependentintjVd2.0W2 vcurenttextseemscorrecteditorialnotshouldnotbeincap@data@defineIdeletedirection@WRWWW$W?Weventsubsciptionisnotpartofsystemmanagementbutcomma?Vevent/commandRWeventsRWSWW_WWevents/commandsWexactlyUWWexampleoWW4WlWWWWexamples[WWWG evare_WeWvWxWWWWWWareaWaroundWas>WOWRWSW[W^WmWnWoWWWWWW WWWW!W%W,W/W=W]WlWwWxWyWzWWWWWWWWassignedNWassociatedWassumeWvekulises!VassociatedWassumeWWWyvtheseservicesaremanagedthroughsystemmanagementprimitijVtheyEW_Wtheyaretwoconcatenatedoctetstringsthe1stonehasafiEVthingsWWthis1W7WMWPWRWSW^WeWiWuWWWWWWWWWWWWWWWW#W$W%W&W'W,W0W9WeWkWlWuWwWxWyWWWWWWWWWWthisaddsconfirmandindicationprimitivesuVthisappliestotable-19aswellpleasefixtable-19aswellVthiscontainsonlyonesubnetchangethedescritpionaccordiPVthisencodinghasbeendefinedinanietfdraftMVthishasbeendescribedindetailinthetlvpartinsectionRVthisinformationisduplicatedandhencedeleted&Vthisisagoodobservation$VthisprimitiveisgeneratedbymihfunctiononnewpoapostVWeWtied$WtimelWtitleWtlv8WRWTUVWXYZ[\]^`adefgiklpqruwx~〃ぃゃッ㄃ㅃㆃ㇃㈃㉃㊃㋃㌃㍃㎃㏃㐃㑃㒃㓃㔃㕃㖃㗃㘃㙃㚃㛃㜃㞃㟃㥃㧃㲃㳃㴃㵃㶃㷃㸃㹃㻃㼃㽃㾃㿃ƒÃăŃƃǃÄ1Ä1Ä1Ä1Ä1Ä1Ä1Ä1Ä1!Ä1"Ä1#Ä1$Ä1(Ä1)Ä12Ä13$Ä14ZÄ15Ä1EÄ1GÄ2V0Ä2W~Ä2YCÄ2drÄ2fiÄ2jDÄ2rEÄ2sFÄ2tGÄ2vHÄ2wIÄ2yJÄ2KÄ2LÄ2MÄ2NÄ2OÄ2PÄ2QÄ2'Ä28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3_Ä31Ä3#lÄ33eÄ3GZÄ3I3Ä3RfÄ3STÄ3dSÄ34Ä35Ä4Ä4Ä4YwÄ4j:Ä4qmÄ4tcÄ4udÄ4vpÄ4nÄ4oÄ4qÄ4gÄ56Ä5;Ä59Ä5zW ^bindingpWqWvWwWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WW W!W)W*W+W-W.W/W0W1W3W4W6W7W8W9W:W;W<W=W>W?W@WCWDWEWFWGWJWKWLWNWOWRWSWUW\W]W^W_W`WaWbWcWdWeWfWgWhWjWmWoWpWqWsWzW{W|W}W~WWWWWWWWWWWWW+gÄ2:hÄ2AÄ2BÄ2CÄ2DÄ2EÄ2FkÄ2GÄ2HÄ2I8Ä2J:Ä2S;Ä2UÄ2V0Ä2W~Ä2YCÄ2ZqÄ2aÄ2bÄ2crÄ2drÄ2eÄ2fiÄ2gVÄ2hÄ2i<Ä2jDÄ2rEÄ2sFÄ2tGÄ2uÄ2vHÄ2wIÄ2x=Ä2yJÄ2zÄ2Ä2Ä2KÄ2Ä2LÄ2Ä2MÄ2NÄ2OÄ2PÄ2QÄ2Ä2Ä2&Ä2>Ä2Ä2Ä2'Ä2eÄ28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3Ä3_Ä3Ä3Ä3Ä3Ä31Ä3Ä3Ä3!Ä3"?Ä3#lÄ3$3Ä3%Ä3&+Ä3'Ä3(Ä33eÄ36Ä37Ä3B]Ä3GZÄ3I3Ä3JÄ3RfÄ3STÄ3UÄ3VÄ3WÄ3XÄ3dSÄ3eÄ3fÄ3gÄ3hÄ3iUÄ3jÄ3qÄ3rÄ3s,Ä3tAÄ3u-Ä3v$Ä3w.Ä3x/Ä3yTÄ3zÄ3Ä3HpESubirFDasGMember^Technical, Binding_165`54a8.4.1.11bUDiscuss and accept the concept described in 21-06-0781-00-0000-MIH_Protocol_Error.pptcSuggest that the status code have additional values for categorizing the Failure of status. Currently defined as only Success, Failure, Rejected. For example System Error, Network Failure, Unauthorized, etc.d2365g2484vThe concept is good. Details to be worked out in next round of comments. Do *NOT* accept contribution 21-06-0781-00-0000-MIH_Protocol_Error.ppt.wAccepted-Modified 2006/11/16 2006/10/23qESubirFDasGMember^Technical, Binding_181`56a8.5.3.16bOUse Status TLV as the Abort Reason for MIH_Handover_Initiate Response message. cThe Abort Reason TLV can be replaced by Status TLV as successful/failure in initiating handover. Then there would be no need for Abort Reason TLV.d2383g2485vby comment 2370w Superceded 2006/11/16 2006/10/23:maccepted-modified!3NXo㢃㦃㬃㯃questionrejected☃⮃*dv〃㗃㘃㞃㡃㶃superceded ₃Cゃv0%W0success%V0047yW0656-02W0793-00W0797,W0813-01W0821W1EWmWW1.29W10RW108W11yW1540W1541W16]W17]W173oW1stEW2|WW3WvWW2n-entityvV2028)W2032W2071W2071/2072 W2086}W2090pW21xWW21-06-0460-04-0000-bW21-06-0738-03-0000-8]W21-06-0778-02-0000-n=W21-06-0781-00-0000-mpW21-06-0784-01-0000WV21-06-0810-00-0000W21-06-0812-00-0000-l21-06-0824-01-0000-gTW21041W2131W21430W2167JWKWLW2187W2190'WW2195VW22W22-1023RW2227W2233W2244WWW2256UW2291W2303WCWDW:9jnodelWsWWWnodesWnon-802Wnon-editorialvWnormativeWnot*WXWWWWWWnumberWobtainedWof[WaWlWsWWWWW!W3WNWXWWWWon[WoWWNWonelWWonlyWWopaqueWopcodeWoperation!Wor[WaWWWWorderlWotherWWWWoutaWWoutsideWover3WWoverallWpageoWW3WNWparameterNW: jreplaceWreplacewithjustmihprotocoldeleteisVrepresentation[WWrequiredvWWrequirementsWrequiringWresource[W^WretitleWretitlefigure25transportofmihframeinieee802.3l2daVright]WrouterNWrunWsamelWsatisfyWschema^WWWscopeWsection1W^WWWW3WvWWsectionsoWsecuirtyWself-referentialWsenderdWsentdWsentencelWWWserverNW :jAfReorder the columns in Table-25: "MIH Action Identifier" needs to be the left-most column, followed by "MIH Service ID", followed by "MIH Opcode", followed by "No" Then rename current column headings as follows: "MIH Action Identifier" to "MIH Action" "No" to "Action Identifier (AID)" "MIH Opcode" to "Opcode" "MIH Service ID" to "Service Identifier (SID)"fmAccepted-ModifiedvAfReorder the columns in Table-25: "MIH Action Identifier" needs to be the left-most column, followed by "MIH Service ID", followed by "MIH Opcode", followed by "No" Then rename current column headings as follows: "MIH Action Identifier" to "MIH Action" "No" to "Action Identifier (AID)" "MIH Opcode" to "Opcode" "MIH Service ID" to "Service Identifier (SID)"fwAccepted 2006/11/16 2006-10-2025 jACommands essentially flow from higher layers to lower layers and this terminology has been consistently followed in the draft. The interaction referred above is more with "remote" entities rather than with local entities. Hence the figure should be left as is.mRejectedvA?The figure basically shows how commands are being initiated. Upper layers initiate commands locally within a stack, and Figure-1 just shows flow for a single stack only. Change the title of figure and add some text to explain this. " The intent of Figure-1 is to show the entity that initiates a particular service. "?wAccepted-Modified 2006/11/16 2006-10-201 ust shows flow for a single stack only. Change the title of figure and add some text to explain this.wDeferred 2006/11/16 2006-10-201€ p$'()+,0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⳃⴃⵃⶃⷃ⸃⹃⺃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփփ׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃׃*b]Create a new Annex and add Section 4 of 21-06-0460-04-0000-Basic_Schema.doc to the new annex.cOA guidance on how to create an Extended Schema would be useful to add in annex.d2412g2234wAccepted 2006/11/16 2006/10/21+*Ä34Ä3Ä35Ä3Ä3Ä3Ä3^Ä3Ä3Ä3'Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3Ä3BÄ4Ä4Ä4Ä4uÄ4Ä4CÄ4Ä4Ä4DÄ4Ä4!EÄ4"Ä4#Ä4$SÄ4%Ä4&Ä4'Ä4(FÄ4*Ä42Ä45Ä48Ä4A0Ä4CÄ4EÄ4TdÄ4YwÄ4aHÄ4bIÄ4cJÄ4dÄ4e*Ä4gÄ4hÄ4iKÄ4j:Ä4qmÄ4rLÄ4sÄ4tcÄ4udÄ4vpÄ4xÄ4y\Ä4zÄ4%Ä4Ä4nÄ4gÄ4oÄ4Ä4Ä4fÄ41Ä4MÄ4aÄ4Ä4qÄ4NÄ4OÄ4PÄ4Ä4 Ä4gÄ4Ä4Ä4QÄ4Ä4 Ä42Ä4Ä4RÄ4iÄ56Ä5;Ä5Ä59Ä5zÄ5 Ä5Ä5Ä5!Ä5"Ä5#Ä5$Ä5%*D dDTÄ4aHÄ4bIÄ4cJÄ4dÄ4e*Ä4fÄ4gÄ4hÄ4iKÄ4j:Ä4qmÄ4rLÄ4sÄ4tcÄ4udÄ4vpÄ4wÄ4xÄ4y\Ä4zÄ4%Ä4Ä4nÄ4gÄ4oÄ4Ä4Ä4fÄ41Ä4MÄ4Ä4aÄ4Ä4qÄ4NÄ4OÄ4PÄ4Ä4Ä4 Ä4gÄ4Ä4Ä4QÄ4Ä4 Ä42Ä4Ä4RÄ4iÄ56Ä5;Ä5Ä59Ä5zÄ5Ä5 Ä5Ä5Ä5Ä5!Ä5"Ä5#Ä5$Ä5% dDTLÄ2Ä2MÄ2NÄ2OÄ2PÄ2QÄ2Ä2Ä2Ä2&Ä2>Ä2Ä2Ä2Ä2Ä2Ä2Ä2'Ä2eÄ28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3Ä3_Ä3Ä3'Ä2eÄ28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3Ä3_Ä3uÄ1xÄ1zÄ1Ä1kÄ1Ä1lÄ1Ä1Ä1Ä15Ä1}Ä1!Ä1Ä1Ä1Ä1Ä1pÄ2`Ä2Ä2YÄ2XÄ2Ä2Ä2xÄ2!Ä2"Ä2#WÄ2$@Ä2%Ä2&AÄ2'Ä2(Ä21yÄ22~Ä23Ä24Ä25Ä26Ä27Ä286Ä297DÄ2rEÄ2sFÄ2tGÄ2vHÄ2wIÄ2yJÄ2zÄ2Ä2KÄ2LÄ2MÄ2NÄ2OÄ2PÄ2QÄ2Ä2Ä2&Ä2Ä2'Ä28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3Ä3_Ä3Ä3Ä3Ä31Ä3Ä3Ä3!Ä3#lÄ3$3Ä3%Ä3&+Ä3'Ä3(Ä33eÄ36Ä37Ä3GZÄ3I3Ä3JÄ3RfÄ3STÄ3UÄ3VÄ3WÄ3XÄ3dSÄ3eÄ3fÄ3gÄ3hÄ3jÄ3qÄ3rÄ3s,Ä3u-Ä3v$Ä3w.Ä3x/Ä3zÄ3Ä3Ä1H`Ä1I"Ä1JÄ1QÄ1RÄ1SÄ1TÄ1UÄ1VÄ1WÄ1XÄ1YÄ1ZwÄ1axÄ1dÄ1hÄ1i[Ä1qÄ1rÄ1sÄ1tÄ1vuÄ1wÄ1Ä1Ä2Ä2Ä2Ä2xÄ2"Ä2$@Ä2%Ä2&AÄ2'Ä21yÄ24Ä25Ä2:hÄ2AÄ2BÄ2FkÄ2HÄ2UÄ2V0Ä2W~Ä2YCÄ2drÄ2fiÄ2hÄ2jDÄ2rEÄ2sFÄ2tGÄ2vHÄ2wIÄ2yJÄ2zÄ2Ä2KÄ2LÄ2MÄ2NÄ2OÄ2PÄ2QÄ2Ä2Ä2Ä2'Ä28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3Ä3_Ä3Ä3Ä31Ä3Ä3Ä3!Ä3#lÄ3%Ä3'Ä3(Ä33eÄ36Ä37Ä3GZÄ3I3Ä3JÄ3RfÄ3STÄ3UÄ3VÄ3WÄ3XÄ3dSÄ3eÄ3fÄ3gÄ3hÄ3jÄ3qÄ3rÄ3zÄ3Ä3aEChengFHongGMember^Technical, Binding_152`46a8.2bMake the defintion consistent.cThe ways to define media types in the table are not consistent. No. 1 is defined as "Ethernet" and the rest are using "802.x". d2322g4732iMichaelW vA21-06-0812-00-0000-LB1a-comment-61 Add Handover (HO) in the name. Add MN, Net, N2N for MN initiated, Net initiated and Network to Network messages (Please use _ instead of - consistently) Network to MN MIH-Handover-Initiate -> MIH-Net-HO_Candidate_Query MIH-Handover-Commit -> MIH-Net_HO_Candidate-Commit MN to Network MIH-Handover-Initiate -> MIH-MN-HO_Candidate-Query MIH-Handover-Commit -> MIH-MN-HO_Commit MIH-Handover-Complete -> MIH-MN-HO_Complete Network-Network MIH-Handover-PreBPpare -> MIH-N2N-HO_Query-Resources MIH-Handover-Complete -> MIH-N2N-HO-Complete >wAccepted-Modified 2006/11/16 2006-10-234!uw <lvAWhen connected to a 802 network, a Mobile Node may directly use L2 for exchanging MIH Signalling, as the peer MIH Function may be embeded in a PoA. The MN may be able to do this for certain 802 networks even before being authenticated with the network.. However, the Mobile Node may also use L3 for exchanging MIH signalling, for example in cases where the peer MIH Function in not located in the PoA, but deeper in the network.@A> 33   33>wAccepted-Modified 2006/11/16vhandoverxWWWWhandoversignalingprocedureaspartofhandoverexecutionawVhandoverswWWWharmonization+WdWhasEWMWRW!WWWhavelWW#W_WwWhdrmWheadingsWhence&WhereRWWheterogeneous{WhigheruWwWhmipyWhoWhocWhorizontalwWxWWhorizontalhandoversthisinvolvesmnsmovingbetweenpoasoVhow`WW]WxWhowever$WlWhowevereventsubscriptionisnottiedtomihregistartion$VidmWWidentifiedNWWidentifierW9WWWidentifiersmWWI kwvA" Handover signaling procedure (as part of handover execution and subsequent updates) may is not part of this standard since higher layer (e.g. IP) mobility protocols defined in IETF can be utilized for certain handover types. Additionally, different access network technologies have defined handover signaling mechanisms to facilitate horizontal handover. The role of this specification is to serve as a handover facilitating service to maximize the efficiency of such handovers either by proBeviding intelligent link level triggering information and or with additional protocol functionality. "S@A  33V  33Y 33  33 33  33 33'  33. 33wAccepted-Modified 2006/11/16 2006-10-23vU vaddressW#WxWWWaddsuWadministrativelyuWadopt=Wadopttheformatproposedin21-06-0778-02-0000-nstandards=Vafter#W+W,WdWWWafterauthenticationandattachmenttoacertainpoathemihVagreeWagreewithyoshi'sreasoningVaidWallmWoW~WWWW{WWWallieidentifierstypevaluesasdefinedintable32are4mValliance=WallowtWalong9WalreadyWWWalsoRWuW4W=WEWlWalsochangemihreporttoinfoqueryresponseEValways9WamendmentsWanMWuW~WWWWand7WEWMWNWRWSWUW[W]W_WlWmWnWoWtWuWWWWWWWWWW&W+W,W0W6WNW]W_WdWeWjWuWvWwWyWWWWWWWWWWWWWBG rvwithwWWWWWwithinuWWWWwlanWWwme=Wwon'tWworkwWWworkedpWWWWwouldtWWwpa=Wwpa2=Wxiaoyu0Wxml[Wy1540/1541Wyear=Wyes]Wyes16and17aretherightreferencestordf]VyoshiMWyoshi'sWwaccepted(+,24579:;<=>?BEFGHINOQSWXY\gnorvy{⁃⫃ⳃⷃ⹃⺃ƒŃȃɃʃ˃̃̓΃Ѓу҃ӃԃՃ؃ڃ #&'478;<>@KORbfkmnoqu}~ッ㄃㝃㣃㦃㪃㺃㽃Ãaccepted-modified18MPRT[]^_jlmpstu|~⻃⿃Ãƃσ !%,369=?ES]ejlrstvwxy'vmih-handover-initiatmih-net-hocandidatequeryVmih-handover-prepareWmih-handover-preparemih-n2n-hoquery-resourcesVmih-mn-hoWmih-n2n-hoWmih-n2n-ho-completeWmih-netWmih-net-hoWmihfmWWW6WjWWWmihgetstate!mihinitialize!mihreset!miisuWeW{Wmiisprovidestheabilitytoaccessinformationaboutallhe{VmiriamWmkaeWmkaethedefinitionpatternconsistentafteralleditorialcVmnlWsW~WWW6WlWWWWmntonetworkVmnsWWmntionBWmobilelWxWWmobilityuWwW3vpleasereferto21-06-0824-01-0000-gTVpleaseuseinsteadofconsistentlyVplesaeWplesaereferto21-06-0784-01-0000mihlinksapclarificatioVpoa8WsW~WWWlWWWpoaofthecurrentlinkbeingusedbythemnsVpoasWWpointWporttWposWWpositionRWpossibilitiesWpossibleWpossiblynWpptpWWpreconfiguredlWpreferredpoalistWpresentations0Wj^Technical, Binding_77`10a7.3.4.2bqIf comment 3 is approved, update Description to fit the Event ID defined in the table (i.e bit 0 is now Link UP).cWThe encoding uses a bitmap but the definition of each bit is not defined in the draft. d2246g2222v&by 2244. The same remedy should apply.w Superceded{l) none needed 2006/11/16EGolmieFNadaGMember^Technical, Binding_78`52a7.3.6.2b/Use the same encoding scheme as section 7.3.4.2c6There is no encoding scheme for the set of event IDs. d2247g2223v&by 2244. The same remedy should apply.w Superceded{l) none needed 2006/11/16=#v8.3.3.5SW8.4.1.12W:=(v2325W2328W2330wWLW2370qW2374W\W2387W2WQW23956W24,W2407WW2408W2409W248W252oW253EW2ndEW3|W4WvWzW3n-eventvV32mW325W328WW330)WhW339 WdWW341dW345GW3gppgWW3gpp/3gpp2|WW3gpp2W3triggers]W4mWoWvWW4n-layervV5|WWkWvW5n-uservV5.1.3`W5.3W5.3.24W5.4.2.4BW5.6W55oWsW6vWxWW6remoten-triggervV6.11W6.3.3W6.41W3W6.4.2W6.4.4,W61[W64[W653W67W3W7SWW,WvWW7peern-entityvV7.3.20.2W7.3.21.2W7.3.7.2W7.4W7.4.14.2.4W7.4.7.1.3'W7.4.7.1.3whengenerated'V74!W8WW8.2.1W8.3.13W8.3.3RW8.3.3.4W,cThe paragraph and figure for MIH Registration is a general description. It should not be place in a section for MIH primitives. d2262g2212vA Remove the Figure 24 and the paragrah above Figure 24 from section 7, since it does NOT belong in there. Move these to section 6.4.4. Editor please disregard contribution 0797 as part of this comment. Leave section numbering in section 7 as is even after the change.  wAccepted-Modified 2006/11/16 2006-10-2324-EXiaoyuFLiuGMember^Technical, Binding_92`64a7.4.1.1bzAccept the proposed amendments to this primitive is in the Remedy 2 of 21-06-0797-00-0000-MIH_Registration_Amendments.doc.cn |$bAf  33* 33     33f'+vobservation$WobtainuW~W4vnotclearifweneedre-registrationprimitive.Vnotclearwhyrouter'smacaddressisusefulorrelevantto#VnoteeW~WW#Wnotification6Wnotificationfrommihfofthemntotargetmihfornotificat6Vnow6WnumberyWnumbering,W?/^Technical, Binding_94`46a 7.4.1.3.2bAMIH_DeRegister.Request ( Source Identifier (MIH-ID), Destination Identifier (MIH-ID), Session ID ) @A>  33    33>crThe session ID created during MIH registration procedure should be specified during de-registration procedure too.d2267g2216v.There is no sessionId as part of registration.wRejected 2006/11/16 2006-10-230EXiaoyuFLiuGMember^Technical, Binding_154`13a8.3bjThe proposed MIH protocol states are described in the document: 21-06-0xxx-00-0000-MIH_Protocol_States.docc|The MIH states are needed for the correct operation of MIH protocol to allow peer MIHF entities to interact with each other.d2330g2217|cQThere is no encoding scheme for the set of supported MIH events or commands IDs. d2269g2230vPlease note, these are different than link events/commands. Insert the above table. Change name of supportedEventList and supportedCommandList to supportedLinkEventList/supportedMIhEventList and supportedLinkCommandList/supportedMIHCommandListwAccepted 2006/11/16EGolmieFNadaGMember^Technical, Binding_97`29a 7.4.2.2.2bAAdd the following in the Description field of supported event list: The encoding uses a bitmap where the bit position represents the MIH event ID. A bit set to 1 indicates that event is supported. Add the following in the Description field of supported command list: The encoding uses a bitmap where the bit position represents the MIH command ID. A bit set to 1 indicates that command is supported. cGThere is no encoding scheme for the set of MIH events and command IDs. d2270g2232wAccepted 2006/11/16EGolmie:vsupportedeventlistWsupportedlinkcommandWsupportingWjWswitchingsWsymmetricWsystemjWt`WtableSWWWWWWtable-17]Wtable-19W!Wtable-19onpage74hasmihnmssapprimitiveswhicharenot!Vtable-25RWtables WtargetsWtargetpoasVtechnologieswWWtechnology_WtermsWtextbW|WWWWW]WcWsWWWthanWthatRWSWjWW$WWthat'sUWthat'sexactlywhatwedidincomment2256UVthe7WRWSW`WsWtWuWWWWWWWWWWWW,W4W_WjWlWwWxW{WWWWWWWWWthefigurebasicallyshowshowcommandsarebeinginitiatedVthemacshaveenoughstatetoknowthedifferencebetweenli_VtheirxWthemWWthenWthereW8vsupportedlinkeventliWsupportingWjWswitch'WswitchingsWsymmetricWsystemjW?Wt`W9WtableSWmWWWWWWWWWtable-19W!Wtable-19onpage74hasmihnmssapprimitiveswhicharenot!Vtable-22W-22WWWtargetpoasVtechnologieswWWtechnology_WtermsWtextbW|WWWWW]WcWsWWWthanWthatRWSWjWW$WWthat'sUWthat'sexactlywhatwedidincomment2256UVthe7WRWSW`WsWtWuWWWWWWWWWWWW'W,W4W_WjWlWwWxW{WWWWWWWWWWthefigurebasicallyshowshowcommandsarebeinginitiatedVthemacshaveenoughstatetoknowthedifferencebetweenli_VtheirxWthemWWthenWthereW h5bAR 33  &  333 33Rc9There is no encoding scheme for the RequestedEvent List. d2275g2235wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Binding_100`18a 7.4.4.2.2bAdd the following in the Description field: The encoding uses a bitmap where the bit position represents the MIH event ID. A bit set to 1 indicates that the unsubscription succeeded.c8There is no encoding scheme for the ResponseEvent List. d2276g2236wAccepted 2006/11/16EGolmieFNadaGMember^Technical, Binding_108`9a 7.4.8.1.4bDReplace the Value size of delays to 2 octets and update Valid range.cThe values of some elements are coded with 4 bytes giving Valid Ranges between 0 and 2^32-1. In the description, valid ranges for delay and jitter are specified to be between 0 and 65535. Therefore the encoding can be done with 2 octets.d2283g2237wAccepted 2006/11/1621EGolmieFNadaGMember^Technical, Non-binding_110`64a 7.4.9.2.2/bBRemove. Also applicable for handove initiate primitives. 7.4.10.2cKWhat does the old link have to do when B6 (bi-casting request) is enabled? d2279g2249wAccepted 2006/11/16 2006-10-23ESrinivasF Sreemanthula^Technical, Binding_105`20a 7.4.7.1.2bBRemove. Also applicable for handove initiate primitives. 7.4.10.2cPWhat does the old link have to do when B7 (handover cancel request) is enabled? d2280g2250wAccepted 2006/11/16 2006-10-23ESrinivasF Sreemanthula^Technical, Binding_110`35a 7.4.9.1.2bACThis is to scan a certain frequency band and determine one or more access network type(s), specific channel(s) and PoA information, if present. Reformat ScanCommand to indicate as below. 1. Lower Frequencybound for the band in MHz 2. Upper Frequencybound for the band in MHz 3. Network access type (TYPE_IE_NETWORK_TYPE).Cc  33c  @  33>cqDescription of Status of MIH_Get_Information.confirm should be the same as that for MIH_Get_Information.response.d2310g2448v+Also change MIH_REPORT to InfoQueryResponsewAccepted-Modified 2006/11/16 2006/10/23FE YoshihiroFOhbaGMember^Technical, Binding_150`13---- ,vrephrasetoprimitivesareaconceptualrepresentationoffuSVreplaceWWreplacefigure22withtheonedescribedinsection2of21-Vreport#WEWreporting8Wrepresentation[WSWrepresented[WrequestWrequest/responsemWrequestsUW--------------------------------------------------------------------------------------------- Link Identifier LINK ID N/A I The link type, identifier and address of the scanned link. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Signal Strength \~g2243i Vivek GuptamAcceptedwAccepted 2006/11/16 2006-10-2318  bA 10. MIH Resource Query | L,R | Client to Network | Sent from MIHF in MN to target MIHF to query available resources Definition is same as MIH_Handover-Prepare but extended to client->network query. Update section 7.4.11 accordingly. Also, need a corresponding link command in table 5. cMN should have capability to check link/network resources in the candidate networks (over R3) directly. This is useful for MN controlled handovers and in other cases where network involvement is not available. d2122g2246wRejected 2006/11/16 2006-10-234ESrinivasF Sreemanthula^Technical, Binding_50`64a6.3.3bA#1. "However, after authentication and attachment to a certain PoA, all the MIH protocol services including MIIS are transported by use of data frames specific to that media technology or in a media independent way by using higher layer IP based protocol." 2. Redundant. remove the sentence.#@avservingpoasVsessionmWsessionid/WshouldRW~WWWWcWeWshowRWWkWshowsW0WWsidWsignalingwWWsignallinglWsimple[Wsince,WwWsingleWsnrWsoW$Wsodontsayanythingaboutthatinthissection$VsocializedgWsomeWWWsparql[WspeciWspecialWspecificBW_WWWWWspecificationwWspecificationsWspecified WspecifyNWWspecifyunitskbpsandintegertypeNVspellyWstackWWWstandardwWWWstandards=WxWstate0W_WWstatedRWstates0WstaystWstill#WstratumyWstringsEWsub-sectionWsubir0WWsubirandxiaoyuwillreturnwithrevisedpresentationssee0VsubmitedWsubmitteddWWWWWAvmovingWWmustuWn-entityvWn-eventvWn-layervWn-triggervWn-uservWn2nWnameW4WWWnamesBWnasyWnatureWneed`WbWoWWWW.W0W=WWWWWWWWneedmoredetailsfromcommenteronhowthemodeldoesnotf`VneedtextbVVneeded~WWneeds1WiWWWWWtWWjWtWWnetworktWWW4W9WlWwWxWyW|WWWWWWWWWnetworktomnVnetwork-initiatedgWWnetwork-networknetworks~WWlWxW{W|WWnewWW#W6WWnext7WpWwW+WWnms!WnoRWW#W/WWWnoremedyVnodelWWWjWlWWWnodesWnon-accessyWnon-securetWnon-zero%Wnon-zerogeneralfaihure%VWvnotclearifweneedre-registrationprimitive@observation@obtains@'of@ordering@(part@pleasereferto21-06-0824-01-0000-g@primitive@3refer@ rephrasetoprimitivesareaconceptualrepresentationoffu@required@sectionR%see6.4.2page67@servingpoa@subnet@asuitable@supportedeventlist@supportedlinkeventli@table-25@the"thereUytheseservicesaremanagedthroughsystemmanagementprimiti@those@tlv[ to@tries@value@we@Bwithwwords@Gwaccepted-modifiedzrejected@€ifiedzrejected@€:E YoshihiroFOhbaGMember^Technical, Binding_48`50a6.3.3bA[1] Change TYPE_IE_POA_ ADDRESS in Table 6 and Figure 20 to TYPE_IE_POA_ MAC_ADDRESS. [2] Change PoA Address IE in TYPE_CONTAINER_POA in Section 6.3.5.4 to PoA MAC Address IE. [3] Change TYPE_IE_POA_ ADDRESS in MIIS_TLV_REPORT_TEMPLATE in Section 6.3.6.1 to TYPE_IE_POA_ MAC_ADDRESS. [4] Update the Basic Schema to rename the class and property corresponding to TYPE_IE_POA_ ADDRESS. cBTYPE_IE_POA_ ADDRESS should be renamed to TYPE_IE_POA_ MAC_ADDRESSd2141g2465wRejected 2006/11/16 2006/10/23T6;E YoshihiroFOhbaGMember^Technical, Binding_49`1a6.3.3b'Adopt 21-06-0779-PoA_IP_Address_IE.doc cConsidering inter-media handover optimization like pre-authentication, it might be good to add a new IE to carry IP Address of PoA, which will help authenticator discovery. d2142g2464wAccepted 2006/11/16 2006/10/23T6 33   33>B TbA> 33p  33>?GvbeWWWWbecomessWbeenMWRWWW1WtW~WlWyWbeingsWWlWvWbelong,WbelowWberWbetween WW_WkWWWbitRWbitsRWblockkWboth[WuWeWbreaksWbutoW?WlWWby'W)W0W6W>WJWKWLWVW_WiWlWqWsWuWzW}WWWWWWWWWWWWWWW WWWWWW2WCWDWLWQW\WpWwWxWWWWWWWWWby2131Vby2227Vby2233Vby2244thesameremedyshouldapplyVVVby2291Vby2303VCVDVbycommentzVbycomment2028)Vbycomment2032Vbycomment2071Vbycomment2086}Vbycomment2090pVbycomment21430Vbycomment2167JVKVLVbycomment2187VYvconfiguration8WrWconfiguringjWconfirmuWconfirmsWconfusingWconnectedlWWconnectiontWconrofmaWconsistencyWconsistent1WWconsistently%WWconsolidatedWWWcontain_WuWcontainerWcontainsPW_WcontentuWcontentsWcontributionpWwWW,WWWWWWWcontrolsWcore9WyW|WcorrectoWcWcorrectedWcorrespondingWcorrespondsRWcouldWcoverageWWcreatedWcurentcWcWcWcW< "vdraftW%WyWWWWdrawkWduplicated&WewWeachRWlW=WWWeachlinkhasauniqueidentifierVeachparameterneedsaseparatetypevalueVeditor+WMWeW,WvWyWeditorcheckforuseoftheseacronymsindraftbeforedelet+VeditorpleasenotethiseVeditorialcWWeffectivelyWefficiencywWeitherwWelements[W_W~WelsevWembededlWemptyeWenablesuWencodingMWendpointsWRvtries`WtriggeringwWtriggers]WtthemjWtwoEWmWkWWtype8WNWmWnWoWWWWWtypeswWWWumtsWWunderoWWuniqueWunitsNWWunusedWupEWMWxWup/down/going_WupdateSWWWupdatedWWupdateswWupdtaedoWuponWupperWxWuse+WlW WlWyWWWWWWuseindividualnetworkspecificstandardrevisiontospecifyVuseresolutionasspecifiedbycomment2071/2072 Vuseronny'ssuggestedtextlVusedmWsWuWWWvWWuseful#WWWuser'WWuseslWWusing^WaWlWWusingethernettoconrofmtoradiusaVutilizedwWutlizexW <^Technical, Binding_53`8a 6.3.5.1.1bChange the Length to 4.c[Length of TYPE_IE_NETWORK_TYPE should be 4 octets because NAS-Port-Type length is 4 octets.d2158g2452wAccepted 2006/11/16 2006/10/23=E YoshihiroFOhbaGMember^Technical, Binding_55`38a 6.3.5.2.4bEAdopt the format proposed in 21-06-0778-01-0000-Network_Standards.docc@Format of TYPE_IE_NETWORK_STANDARDS value needs to be specified.d2167g2432vAAdopt the format proposed in 21-06-0778-02-0000-Network_Standards.doc: For 802.11 we may need other modifications as follows: Add the year of release Define capabilities for each task group for WiFi Also add release certifications for WiFi Alliance (WPA, WPA2, WME, etc.) wAccepted-Modified 2006/11/16 2006/10/23>E YoshihiroFOhbaGMember^Technical, Binding_61`17a6.3.5.4bBAdd one optional Network Standards IE to TYPE_CONTAINER_POA TLV. w 5cAThe cost of accessing the network may differ between roamed access networks for different users. For example, User A may have one cost on his home network while User B has a different cost on that same network because he is roaming. The reverse may be true on User B's home network. Additionally, Users A and B may both have still a different cost if they are both roaming. The current definition of cost and a centralized repository for the value for all accessed networks does not accountB for this.d2164g2223iVivekjThen the MN also needs to specify type of user (Home/Visited) or the network needs to figure this out.... Adds complexity. Should cost for home users be added or is this something more implicit (not needed)..?mQuestionwRejected 2006/11/16 2006/10/23k FbcValue is not clearly defined.d2162g4705k wAccepted 2006/11/16 2006/10/20GEQiaobingFXieGMember^Technical, Binding_54`58a 6.3.5.2.2bAochange to: List of different operators. The value field contains one zero or more Operator Identifier TLVs. o@Af 33C  F 33G  33K 33fc=Allowing empty roaming partner list does not make much sense.d2163g4706k wAccepted 2006/11/16 2006/10/20HEQiaobingFXieGMember^Technical, Binding_55`13a 6.3.5.2.3bs1. Clarify the encoding of table 10 either with a diagram or additional text. 2. move Currency field to be the lastc1. unclear about how the 4 fields are encoded in Table 9. One can only assume that they are 4 concatenated octet strings. 2. having variable length field ahead of fixed length fields is awkward to encode and decode.d2165g4707k wAccepted 2006/11/16H 2006/10/20tbl 10IEQiaobingFXieGMember^Technical, Binding_55`33a 6.3.5.2.3bEither define it or delete it.cWhat is the "service-info"?d2166g4708k v delete itwAccepted 2006/11/16 2006/10/20tbl 10JEQiaobingFXieGMember^Technical, Binding_55`38a 6.3.5.2.4b[1. Define encoding details of the Value field 2. define all the valid revision entry valuesc1. Encoding details of the Value field missing 2. What are the valid entries for different revisions? Without the above details the IE would be hard to use.d2168g4709k vby comment 2167w Superceded 2006/11/16 2006/10/20KEQiaobingFXieGMember^Technical, Binding_55`55a 6.3.5.2.5b+Define encoding details of the Value field caEncoding details of the Value field missing. Without those details the IE would be of little use.d2172g4710k vby comment 2167w Superceded 2006/11/16 2006/10/20LEQiaobingFXieGMember%OFXieGMember^Technical, Binding_58`22a 6.3.5.3.4bJAdd details on the endoding of the Value (integer, floating point, ascii?)c+Encoding details of the Value field missingd2178g4714k vDefine it as integerwAccepted 2006/11/16 2006/10/20PEQiaobingFXieGMember^Technical, Binding_58`31a 6.3.5.3.5bwAdd more details on the encoding of the list of subnets (how the list of variable size entries is encoded and decoded?)c0Encoding details of the Value field inadequated2179g4715k vBThis contains only one subnet. Change the descritpion accordingly.wAccepted-Modified 2006/11/16 2006/10/20QEQiaobingFXieGMember^Technical, Binding_59`4a 6.3.5.3.6bClarify that, when present, the conditional/optional DHCP_ADDRESS and FA_AR_ADDRESS TLVs are part of the Value field of TLV IP_CONFIG_METHODS. I.e., IP_CONFIG_METHODS Value = [4 octet bimap] [(optional) DHCP_ADDRESS] [(optional) FA_AR_ADDRESS] RmRejectedvABy vote 6 vs 6 Change the name to TYPE_IE_POA_DHCP_SERVER_ADDRESSwRejected 2006/11/16 2006-10-23EVivekFGuptaGMember^Technical, Binding_197`1aAnnex A4bo Either delete these figures or move them to Annex A-1. Draw them consistently with other figures in Annex A-1.c/ Figs 36, 37 and 38 do not belong in Annex A4. d2407g2238vChange the title of these figures. These figures are related to QoS contribution. Please refer to comment 2408 and 2409 These figures need to be corrected.wAccepted-Modified 2006/11/16 2006-10-238 'cA0For Information retrieval using TLV, there should be a way for the client to narrow down the list of the access networks and PoAs in the report. For example, a client may not want to retrieve any information about 802.11 networks. Or, a client may only want to retrieve information about UMTS networks. 0d2192g4674k vby comment 2190w Superceded 2006/11/16 2006/10/20fX^evAdd this text: " If both optional TLVs are absent then the value field of the MIIS_TLV_QUERY should be empty and thus the length field will not tbe applicable "wAccepted-Modified 2006/11/16fEUlises^Technical, Binding_175`1a8.5.1.3b]Remove the SourceIdentifier parameter since it is already included in the MIH Variabel HeadercAThe sourceIdentifier parameter in the message identifies the source where this message originated from. It is not necessary since the MIH frame contains a TLV (i.e., int eh MIHF Variable Header) that identifies the MIHF INof the sender of the MIH Message The same comment applies to the following sections: o 8.5.1.4 - MIH_Registration Response (also 7.4.1.2) o 8.5.1.5 - MIH_DeRegistration Request (also 7.4.1.3) o 8.5.1.6 - MIH_DeRegistration Response (also 7.4.1.4) o 7.4.2.1 - MIH_Capabili,KvfigureWWW,W4WkWxWyWzWWfigure1showstheplacementofthemihfwithinthemobilityVfigure-1Wfigure12}WfiguresWfinalizedWfirstmWfit`Wfits`WfixWfixedEWflowWWflowsxWWfollowMWfollowedWWSWjWsWuWWWWWWWWWWW W4W=W]W_WkWlWwWyWWWWWWWWfortransportoverdataplaneal2lsapprimitiveswhichareVformat^W=Wformats_Wforwarded6WframesWframessWWframework[W^W`WfromRW`WWWWW'W,W6WxWWWWfunctionlWWW3WjWlWfunctionalitywWfunctionsSWfurtherWgwWgeneralWgeneratedW'WgenericWgetMWgivingWgoestWgood$Wgroup=W"y vthereUWW !vinvokedSWinvolvesWWip8WwWWiptransportisanexampleofmihuserVisSW_W`WiWnWoWpWsWuW~WWWWWWWWWW#W$W&W'W,W/W0W3W?WwWWWWWWWWWWisn'tWissue0WNWWWissuecreatedforsection8VissueidentifiedandassignedNVitIWOWRWsW~WWWWWWW,WWWVFXieGMember^Technical, Binding_64`21a 6.3.6.2.1b&Add rule to report unrecognized IE IDsc'Need rule to report unrecognized IE IDsd2196g4721k vby comment 2195w Superceded 2006/11/16 2006/10/20 3vtlv[WoWeWWtlvsmWeWvvability{Wable~WlWabortedWabortreason%Wabout$W{WabovemWW,WabsenteWabstractjWacceptpWW_Waccepted>Wacceptedbylabellinglineaslinkevent>Vaccess~W9WwWxW{WaccesseduWaccordinglyPWSWWvWack0WWacronymyWacronyms+WyWacrossW%WSWactionRWWactualoWadWadd8WRWWWWWWWWW WW!3W=WeWWWWWWWWWaddarowforitVaddarowforthisVaddasub-sectioninsection7.4wheremihindicationsbasicVaddanentryforpreferredpoalistVaddbetweenwordsintablesforthesedifferentprimitives VaddhandoverhointhenameVaddmnnetn2nformninitiatednetinitiatedandnetworktoVaddsomeclarificationtextforthissectionV vtheWWWWWWW%W'W,W0W3W4W6W9W=W_WeWjWlWrWwWxW{WWWWWWWWWWWWWWWWWWWWWWWtheconceptisgooddetailstobeworkedoutinnextroundopVthedescriptionisveryspecifictocertaincasesandbreaksVthefigurebasicallyshowshowcommandsarebeinginitiatedVthemacshaveenoughstatetoknowthedifferencebetweenli_VthemechanismsrelatedtodiscoveryorconfigurationofpeerrVthemihcapabilitydiscoveryprocedureisusedbyonemnmihVtheotherflowsneedtobeupdatedbasedontheseflowsVthetemplatedocument21-06-0822-02-0000hasbeenfinalizedVthetlvvaluesforallmessagesinsections8.5.18.5.2andoVtheir_WxWthemmWWWthenWWeWtherevchangetextto_VchangetexttoreadsuitableamendmentsarerequiredtoexisVchangethenameofthesection5.3.2inadeploymentexample4VchangethenametotypeiepoadhcpserveraddressVchangethetitleofthesefiguresthesefiguresarerelatedVchangetitletonetwork-initiatedhandoverfrom802.21to3ggVchangeto3gpp/3gpp2networkorothercorenetworks|VchangedWchangesWWchangesarequitesubstantialVchannelWbWe propose to add a detailed description about how to get these information elements over L2 or L3 transport, and provide the concrete messages (or primitive) exchanged in this procedures. cAThe MIHF uses MIH_Get_Information primitive to get MIH Information service. The corresponding message may be carried over appropriate transport (L2 or L3) and is delivered to the remote MIHF. Remote MIHF returns the necessary information to the NM via the appropriate response frame. In figure 23, the draft gives the MIIS information flow. But in the case of L2 transport, it's still no clear that what message exchange would happen between MIHF and lower link layer.d2204g2221vUThe description is very specific to certain cases and breaks the current general flowwRejected 2006/11/16 2006/10/2323EJunxiangFGuoGMember^Technical, Non-binding_ 117/ 120/ 126` 37/ 16/ 10a!7.4.10.4.4,7.4.11.3.4, 7.4.12.4.4b vsectionRWSW^W`WWWWWWWWW$W,W3W4WxWWWWWsections`WoWWWsecuretWsecurityuWWWseeWWWWWW W)W0WGW_WdWhWWWsee2325Vsee325Vsee328Vsee330)VhVsee339 VVsee339and341dVsee345GV VlvBrotocol message, MIH function discovery and capability discovery may be performed at the same time by exchanging MIH Capability Discovery messages with MIH peers. Following subsections define each of these methods more details.@A> 33   33>wAccepted-Modified 2006/11/16 2006/10/23mESubirFDasGMember^Technical, Binding_161`53a8.4bAAReplace "one " with four": Type field shall be one four octect .A@AR 330  4 9 33RcThe MIHF TLV Encoding scheme is the same as the encoding scheme described in page 52 (6.3.5 TLV Representation of Information Elements). Therefore the type field in MIHF TLV shall be FOUR octects instead of ONE.d2360g2480v  vmihWWWWWWWWW!W$W'W3W4WEWjWlWrWsWtWWWWWWmihframetransportthroughcontrolormanagementframessVmihissymmetricinnatureandbyitselfdoesnotmandateanVmihlinksapgoestomediadependentcategorytVmihnetsapprovidestransportservicesonthelocalnodesuVmihnetsapstaysinmediaindependentcategorytVmih-handover-commitWmih-handover-commitmih-mn-hocommitVmih-handover-commitmih-nethocandidate-commitVmih-handover-completWmih-handover-completmih-mn-hocompleteVmih-handover-completmih-n2n-ho-completeVmih-handover-initiatWmih-handover-initiatmih-mn-hocandidate-queryV)vorderingiWoriginatesWother`WmWWWW#W=W|WWWWoutpWWxWyWoveruWW3WjWoverallWoverheadtWpackets6Wpage[WoWW!W3WWparagrah,WparameterWW xvknow_Wl2tWuWWWkWlWWl3uWWlWWlabel?Wlabellineclearly?Vlabelling>WlaterWWWlayeruWW3WkWwWWWWlayersWSWxWWlb-1yWleave,WWleft-mostWlengthEWeWlessuWlevelRWwWlimiteduWline>W?W[WoW3WsWlink>WsWWWWWW'W_WtWwWWWWWWWWWWlinkacommunicationlayerthroughwhichnodesmayVlinkidentifierchannellinkidentifierisnetworktypemacaVlinkidentifierWWlinkparameterlistWlinkparameternamelisWlinksWlistRWSW_WlWnWoWWWWlistofcommandsisdescribedinsection8.3.3.5movethattSVÄ3Ä3Ä3Ä3Ä3Ä3BÄ4Ä4Ä4Ä4uÄ4Ä4CÄ4Ä4Ä4DÄ4Ä4!EÄ4"Ä4#Ä4$SÄ4%Ä4&Ä4'Ä4(FÄ4*Ä42Ä45Ä48Ä49Ä4A0Ä4CÄ4EÄ4HÄ4JÄ4TdÄ4YwÄ4aHÄ4bIÄ4cJÄ4dÄ4e*Ä4fÄ4gÄ4hÄ4iKÄ4j:Ä4qmÄ4rLÄ4sÄ4tcÄ4udÄ4vpÄ4wÄ4xÄ4y\Ä4zÄ4%Ä4Ä4nÄ4gÄ4oÄ4Ä4Ä4fÄ41Ä4MÄ4Ä4aÄ4Ä4qÄ4NÄ4OÄ4PÄ4Ä4Ä4 Ä4gÄ4Ä4Ä4QÄ4Ä4 Ä42Ä4Ä4RÄ4iÄ56Ä5;Ä5Ä59Ä5zÄ5Ä5 Ä5Ä5Ä5Ä5!Ä5"Ä5#Ä5$Ä5%Ä2Q9Ä2R:Ä2S;Ä2TÄ2UÄ2V0Ä2W~Ä2XÄ2YCÄ2ZqÄ2aÄ2bÄ2crÄ2drÄ2eÄ2fiÄ2gVÄ2hÄ2i<Ä2jDÄ2qÄ2rEÄ2sFÄ2tGÄ2uÄ2vHÄ2wIÄ2x=Ä2yJÄ2zÄ2Ä2Ä2KÄ2Ä2LÄ2Ä2MÄ2NÄ2OÄ2PÄ2QÄ2Ä2Ä2Ä2&Ä2>Ä2Ä2Ä2Ä2Ä2Ä2Ä2'Ä2eÄ28Ä2UÄ2VÄ2[Ä2\Ä2^Ä3]Ä3Ä3_Ä3Ä3Ä3Ä3Ä31Ä3Ä3Ä3!Ä3"?Ä3#lÄ3$3Ä3%Ä3&+Ä3'Ä3(Ä33eÄ36Ä37Ä3B]Ä3GZÄ3I3Ä3JÄ3RfÄ3STÄ3UÄ3VÄ3WÄ3XÄ3dSÄ3eÄ3fÄ3gÄ3hÄ3iUÄ3jÄ3qÄ3rÄ3s,Ä3tAÄ3u-Ä3v$Ä3w.Ä3x/Ä3yTÄ3zÄ3Ä3vfollowing[WlWW3WsWWfollows[W^WW%W=Wfor+WRWSWjWoWsWuWWWWWWWWWWWW W4W=W]W_WkWlWwWyWWWWWWWWWWfortable-3andtable-4miheventsandmihcommandsremovetVfortransportoverdataplaneal2lsapprimitiveswhichareVformat^W=Wformats_Wforwarded6WframesWframessWWframework[W^W`WfromRW`WgWmWWWWWW'W,W6WxWWWWWfunctionlWWWW3WjWlWfunctionalitywWWfunctionsSWgwWgeneral%WWgeneratedW'WgenericWgetMWmWgiveWgivingWgoestWgoodpW$Wgroup=W.ME YoshihiroFOhbaGMember^Technical, Binding_161`53a8.4bA(The Type field shall be one four octets.(@Az  33    !  33&  '  33zcThe length of the Type field of TLV for carrying MIH protocol messages needs to be the same as the length of the Header Type field of Header TLV.d2361g2451 2006/11/15 2006/10/23ME YoshihiroFOhba-L 2006/10/23F \cA1. There seems to be 2 Link Identifiers - current (Type 12) and new (Type 13) link identifiers. However, in section 8.5.2.1 MIH_Link_Up indication, there is a LinkIdentifier of Type 243 (defined as new linkidentifier). Also, in section 8.5.2.6 MIH_Link_Event_Rollback Indication, there is a LinkIdentifier of Type 244 (defined as current link identifier). Thus there are many LinkIdentifier Types and it is confusing to distinguish which is which. 2. Link Identifier has a Link Type TLV as oneB content of its value field. However, in section 8.5.2.2 MIH_Link_Down Indication, we see that there is an entry for LinkType and LinkIdentifier. This redundant since LinkIdentifier already contains a LinkType TLV.d2368g2299vby comment 2374w Superceded 2006/11/16]EUlises^Technical, Binding_72`1bDocument 21-06-0738-01-0000-802_3Triggers.doc describe how 802.2ah and 802.1ag triggers can be mapped to equivalent 802.21 triggerscEGolmieFNadaGMember^ Editorial_170`55a8.4.1.32bAdd Status to header here.c=Inconsistent name between header and name listed in Table 26.d2371g2296 2006/11/16EGolmieFNadaGMember^Technical, Non-binding_176`12a 7.4.8.1.4bGReview section 8.5.2 and update all Type values as defined in Table 26.cPThe type values used in section 8.5.2 do not match the ones defined in Table 26.d2382g2240vby comment 2374w Superceded 2006/11/16UG^vandmarkotherunusedvaluesasreservedVaniyWannex_WxWWWFvannexisjustanexampleitdoesn'tmeanthecommandisn'tn@Gare_at@bebefore@?bycomment2190@ candidate@changetextto@#check@configuration@nY%vChange AbortReason to "ErrorCode"... Define values as follows: 0: Success non-zero: General Faihure Do this change consistently across the draftwAccepted-Modified 2006/11/16Avnormative_WnotUW`WiWmWpWuWWW!W#W$W,W.W?W_WcWeWlWvWwWWWWa&ncThe descriptions of the value "InfoQueryType" (in page 171 line 31 and page 172 line 8) are referring to "IS Query Type" in section 8.4.1.4.d2372g2482i Vivek GuptajChange "InfoQueryType " to "IS Query Type List" in 8.4.1.35 and 8.4.1.36 and possibly throughout the draft. Please look at 8.5.4.1 and 8.5.4.2 as well....mAcceptedvChange "InfoQueryType " to "IS Query Type List" in 8.4.1.35 and 8.4.1.36 and possibly throughout the draft. Please look at 8.5.4.1 and 8.5.4.2 as well....wAccepted 2006/11/16 2006/10/23,+ Nj@AR 33  33 33 RkBecause Serving FA Address, Serving Access, Router Address and DHCP Server Address are IP address, IP Address TLV (type 9) can be used for all cases. Clear mapping is needed for clarity. mAccepted-ModifiedvIssue identified and assignedwRejected 2006/11/16 2006/10/23OE YoshihiroFOhbaGMember^Technical, Binding_183`40a8.5.3.23bO[1] Add CurrentLinkIdentifer and TargetPoAIdentifier. [2] Remove MacMobileNodeceCurrentLinkIdentifer and TargetPoAIdentifier are missing in the table. MacMobile Node is not needed.d2385g2459wAccepted 2006/11/16 2006/10/23 @gvA* 33 *;Qzc@#1 and #2 do not belong to this table. These are TLVs not IEs. d2404g2497v by comment w Superceded 2006/11/16 2006/10/23S cAeMIH_LINK_SAP is represented in various expressions which are confusing. For example, it is described as "technology dependent interface" (1.2), "generic link layer" (1.5), "abstract link layer" (5.5) and "generic media independent" (5.6.1.1). These terms should not be used without their definitions. Therefore we need a clear definition for MIH_LINK_SAP.ed2086g2214iRonny jEProvide description of the mapping function as part of MIH function. kFigure in the contribution helps understand the function of MIH_LINK_SAP. However, the mapping function should be defined in the 802.21 draft because media specific standard would not define it. mAccepted-ModifiedvPlesae refer to 21-06-0784-01-0000_MIH_LINK_SAP_clarification Take out the Mapping function from the figure. It is confusing. Add the other text from sections 5.6.wAccepted-Modified 2006/11/16 2006/10/23v21-06-0794-01-00-000|W21-06-0794-01-00-000text532|V21-06-0796-03-0000-m0W21-06-0810-00-0000W21-06-0812-00-0000-l21-06-0822-02-0000W21-06-0824-01-0000-gTW21-06-0826-00-0000-n}W21-06-0826-00-0000-nfigure12}V21-06-0827-01-0000-tWWW21041W2131W21430W2167JWKWLW2187W2190'WW2195VW22W22-1023RW2227W2233W2244WWW2256UW2291W2303WCWDW&8zESubir FDasGMember^Technical, Binding_195`12aAnnex A3b]Move TYPE_HRD_TLV_MIHF_ID and TYPE_HDR_TLV_SESSION_ID from Table 32 to Table 26 (page 163).^vdirectionWdirectlylWWdiscoverlWWdiscoverylWW3WrWWdiscrepanciesoWdiscussion+WWWdiscussionaroundneedtoincludeabortedhandoverinthemiVdisregard,WdoSWmWpWW%WlWvWdothischangeconsistentlyacrossthedraft%VdocW0W=W]Wdocument]WvWWdocument21-06-0738-03-0000-83triggersdocdescribehow802]Vdocuments]Wdoes`WWW,WWdoesn'tWdoingWdont$WWdown_Wdraft+WMWnWWv2360LW2370qW2374W\W2387W2WQW23956W24,W2407WW2408W2409W248W252oW253EW2ndEW3|W4WvWzWW3n-eventvV32mW325W328WW330)WhW339 WdWW341dW345GW3gppgWW3gpp/3gpp2|WW3gpp2W3triggers]W4mWoWvWWW4n-layervV5|WWkWvW5n-uservV5.1.3`W5.3W5.3.24W5.4.2.4BW5.6W55oWsW6vWxWW6remoten-triggervV6.11W6.3.3W6.41W3W6.4.2W6.4.4,W61[W64[W653W67W3W7SWW,WvWW7peern-entityvV7.3.20.2W7.3.21.2W7.3.7.2W7.4W7.4.14.2.4W7.4.7.1.3'W7.4.7.1.3whengenerated'V74!W8WW8.2.1W8.3.13W8.3.3RW8.3.3.4WWf WdcC8at had perviously sent to Node y) is being acknowledge. d2343g2307iYoshihiro OhbajTransaction-ID can determine which message is being acknowledged for, even if two consecutive messages are sent from the sender.mRejectedv:see 339 and 341. To be submitted after more harmonizationwRejected 2006/11/16 vbefore+W1WtW~WlWyWWbeingsWWlWvWbelong,WbelowWberWbetween WW_WkWWWbitRWbitsRWblockkWboth[WuWeWbreaksWbutoW?WlWWby'W)W0W6W>WJWKWLWVW_WiWlWqWsWuWzW}WWWWWWWWWWWWWWW WWWWWW2WCWDWLWQW\WpWwWxWWWWWWWWWby2131Vby2227Vby2233Vby2244thesameremedyshouldapplyVVVby2291Vby2303VCVDVbycommentzVbycomment2028)Vbycomment2032Vbycomment2071Vbycomment2086}Vbycomment2090pVbycomment21430Vbycomment2167JVKVLVbycomment2187Vp&vPlease refer to 21-06-0810-00-0000_Network-initiated Handover Procedure Update Needs more offline work on failure cases and an updated contribution could be submitted in next round. There are just informative ways of doing things.wRejected 2006/11/16 2006/10/23314 hvneedsWWneighborhoodWnetWWjWtWWnetworktWWW4W9WlWwWxWyW|WWWWWWWWWWnetworktomnVnetwork-initiatedgWWnetwork-networknetworks~WWlWxW{W|WWnewWW#W6WWnext7WpWwW+WWWnms!WnoRWW#W/WWWnoremedyVnodelWWWjWlWWWnodesWnon-accessyWnon-securetWnon-zero%Wnon-zerogeneralfaihure%Vvwe.W=WUW_WWwellSWnWWWWWW!W]WxWzWWWWwhatRWUWWwhenlWuW'WlWWWwhenconnectedtoa3gpp/3gpp2networkamobilenodemayuseVwhenconnectedtoa802networkamobilenodemaydirectlyulVwhentheinformationoriginatesatlowerlayeroftheprotocVwhereRWuWWlWwhichlWW!W0WjWxWWWwhy#Wwifi=Wwill0WeWwirelessWwith1WMWlWmWtWwW~WWWWW0W4W9WjWlWQ cANeed to support mechanism by which client can query any PoA( BSSIDs/ESSIDs) that can support emergency call services. The client should be able to query list of services supported at a PoA. Explain how this can be done using IE containers and TLV mechanisms.d2186g2228v{21-06-0827-01-0000-TLV-indicating-network-types This capability is already supported. Just need to add an example in Annex.w Superceded 2006/11/16 2006-10-23q bAA couple thoughts: a) Add a way so that a MN can query an 802.21-IS for its current location given an observed MAC address (e.g., say from a 802.11 beacon or some such broadcast mechanism for other technologies) b) Maybe the MN doesn't know its current location, but just wants to know if a certain operator or roaming partner is supported on this network. Add a TLV method to make this specific query cA1The TLV-based queries in section 6.3 are driven from location. This makes a lot of sense, but it can be too restrictive as well. Is it assumed that a MN can always determine its location? What if it's not connected to a network/PoA when it needs to make a query (e.g., the MN is just booting up). 1d2188g2232vbased on remedy 3 in contribution 21-06-0827-01-0000-TLV-indicating-network-types To be worked on and consolidated contribution to be submitted later.wRejected 2006/11/16 2006-10-23vbased on remedy 4 in contribution 21-06-0827-01-0000-TLV-indicating-network-types May need to add other network types to this as well. To be worked on and consolidated contribution to be submitted later.wRejected 2006/11/16 2006-10-23 vADiscussion around need to include aborted handover in the MIH handover commands. Discussion that many ways to use these commands. Many sequences possible. There won't be one diagram to capture all possibilities. Comment that MBB requires resources to be already reserved and link established before handover is complete, that can't be avoided. MIH commands may not indicate that directly. wRejected 2006/11/16 2006/10/17vwords WworkwWWworkedpWWWWwouldtWWwpa=Wwpa2=Wxiaoyu0Wxml[Wy1540/1541Wyear=Wyes]Wyes16and17aretherightreferencestordf]VyoshiMWyoshi'sWwaccepted(+,24579:;<=>?BEFGHINOQSWXY\gnorvy{⁃⫃ⳃⷃ⹃⺃ƒŃȃɃʃ˃̃̓΃Ѓу҃ӃԃՃ؃ڃ #&'478;<>@KORbfkmnoqu}~ッ㄃㝃㣃㦃㪃㺃㽃Ãaccepted-modified18MPRT[]^_jlmpstu|~⻃⿃Ãƃσ !%,369=?ES]ejlrstvwxy