Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0 Hx)binformation@/ctoinsureinteroperabilitytheieee802.21mustdefinehowt@@00agraphrepeatswhathasalre@@0@0ragraphrepeatswhathasalre@@0andotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@@ABCILMNO~ဃ၃ႃჃᄃᅃᆃᇃሃቃኃዃጃ᷃ṃểƃ ///////////////////////////////////////////////////////////alistairanorȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ eric݂݃eunahyzp BALLOTNUMBERCHANGEb COMMENT DATECOMMENT NUMBERd COMMENT TYPE^COMMENTARY VERSIONCOMMENTARY VERSION DATECOMMENTARY VERSION NOTESCOUNTERgDECISION OF GROUPw DOCNUMBEREDITOR'S ACTION ITEMSEDITOR'S ACTIONS{ EDITOR'S NOTEpEDITOR'S QUESTIONnEMAIL CC EMAIL SUBJECT EMAIL TO EXPORTDATE FIGTABNUMBER FIRST NAMEGROUP'S ACTION ITEMS GROUP'S NOTESy LAST NAMEMARKMEMBERSHIP TYPEREASONcREASON FOR GROUP DECISIONxREASON PROPOSEDkRECOMMENDATIONm REPORTNUMBER RESOLUTION BYiRESOLUTION OF GROUPvRESOLUTION PROPOSEDjSECTIONaSTARTING LINE NUMBER`STARTING PAGE NUMBER_VOTEVOTERBALLOTNUMBERVOTERDOCNUMBERGA Ballot NumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line Number BC#AAzHHddE(HH(d'`zA'dvMThis kind of partitioning does not help at this stage. Needs more discussion.wRejectedions in the related area.iscover.request MIH_Capability_Discover.request ( SourceIdentifier, DestinationIdentifier, RequestNetworkType, rator is specified here?). For security specify cipher suites and authentication methods. QoS: Investigate using media independent parameters such as delay, jitter etc. defined in (Ulises et al) QoS contribution. Cost: Investigate QoS based cost?? wDeferredrredjmRejected{ 2006/04/3020SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDec'7y:!I3 "Z22&f 9/21/20061=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&`wanghleiUwang8Aj>Use "Contents" instead of "Table of Contents" as section titlemAccepted-Modified{k) done 2006/09/21 2006/04/24MarkedEQiaobingFXieGMember^ Editorial_6`37aToCbAAdd Annexes to the end of ToC@A  cAnnexes missing from ToCd45g2235{k) done 2006/08/29 2006/04/24EQiaobingFXieGMember^ Editorial_5`10a2c>Reference number is missing for all the references in the listd40g2237{k) done 2006/08/29 2006/04/24EQiaobingFXieGMember^ Editorial_8`21a3b?They must either be merged into one, or one of them be removed.c)There are two "Mobile Node" definitions. d60g2238{k) done 2006/08/29 2006/04/24EQiaobingFXieGMember^ Editorial_8`21a3b?They must either be merged into one, or one of them be removed.c)There are two "Mobile Node" definitions. d61g2239{k) done 2006/08/29 2006/04/24 EQiaobingFXieGMemberK 9@AOKA/A0@@A-A.@A,A-Cancel@A*A+@@A* ;X( `Before importing, Find the records eligible for proposals by this Clause Editor. Only these records will be affected by the import. ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoQ:ASort by RecommenderE'` iDT_DT`DTDTDTQÃY0?ÃY@@ÃYPAÃY`BÃYpCÃYDÃYEÃYFÃZGÃZ HÃZ0IÃZ@JÃZPKÃZ`LÃZpMÃZNÃZOÃZPÃaQÃa RÃa0SÃa@TÃaPUÃa`ZBUUX  w  $,.YesNo/,  , : AM PMf  HelveticaGenevaVerdanaTimesMonacoTimes New RomanArialCourierSymbol Courier New@ A PICT,alisNAMEMSPCFPTHA9Macintosh HD:Desktop Folder:Ballot#2:802.16.2 Ballot Data9MSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataalisC-`@@XA Comment List@@*AAbout Commentary@@PACreate Comment@@fACreate and Submit Ballot@@AGlobal Field Setup@@ AEditor's Layout@@AComment List for Printing@@ AComment List for Projection@@ACommentary Version@@@AReply Comment Layout@@ ASubmit Reply Comments   A Comment ListB   vor/ 11 against wRejected{l) none needed 2001/10/24»ETG3/4 MAC group^Technical, Bindinga6.2.XbFAdd new ARQ text found in document 80216abc_01/75 to the WG document. d339g2541wAccepted{k) done 2001/10/24 2001/09/11¼E TG3/4 MAC^Technical, Bindinga6.2.xb'Add a standalone NACK feedback message.d340g2542vneed accepted textwDeferred{l) none needed 2001/10/24 2001/09/13½E TG3/4 MAC^Technical, Bindinga6.2.xb Add RNR feedback message for ARQd341g2543vneed accepted text 2001/09/13D$aGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #{ Document #Report # B A € € € €€ €   G!MKe!MKG*fQjugD€QASDocument under Review€XAYLetter Balllot Number€^A_VoteaGlobal Field Setpb // etpb // etpb // etpb // tpb // b // b // d Setpb // Setpb // tpb // Setpb // b // ld Setpb // d(2) Save Data to Filee(3) Email Data Fileail Data File54 RB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMnD a w n w  $,.YesNo/,  , : AM PMo  w p w  $,.YesNo/,  , : AM PMq  w r w  $,.YesNo/,  , : AM PMs  w t w  $,.YesNo/,  , : AM PMu  w z w  $,.YesNo/,  , : AM PM{  w  D^"M1,,./: AM PMYyTtNnFfNALL OFMPRP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , AXLS Sheet1X5CMY m]oApFfWyHCB-wang., .lei]} A1FPTH=RPTH NAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9NFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9OFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A10FPTHXRPTHNAMEMSPCMSPCA2NAMEANumberLastFirst.USRRPTHANumberLastFirst.USRA19uFPTH^RPTHNAMEMSPCMSPCA2NAMEANumber_Lastname_FirstnameRPTHANumber_Lastname_Firstname ot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisVDEF(LISTLISTVDEF(LISTLIST(:K?@MRS Y!^"CAStartup scriptEQADelete Empty RecordsE@ @b*QA Show VotesE@@H-Already voted; submitting additional commentsQASort by Page/LineE'` _DT`DTDTDTQASort by Comment OriginatorE'` DTDT_DT`DTQADelete All RecordsE@ @b*QADelete Abstain CommentsE@ @HAbstain for other reasonsQAShow Editor's ProblemsE @'`@n* _DT`DTDTDTQASort by Comment #E '` dDTQ8 €Bied in recommending rejection on grounds of incompleteness or lack of a specific change request. (3) When you are finished entering replies, look under Scripts and choose "Find Marked Records". This will find the records for which you checked the "Marked" box. (4) Put your name in the "Recommendation by" field of each reply {for a quick method, see Appendix below.} (5) Under Scripts, choose "Export Clause Editor's Proposals". Choose the file type "FileMaker Pro Runtime Files". Enter a Cfile name of the form "BallotNumber_LastName_Firstname.USR", where "Name" is your name. (6) Email the exported file as an attachment to: --------------- Appendix: Using "Replace" in Commentary You can replace everything in a particular field over a batch of records. For example, clause editors might not want to type their name in the the "Recommendation by" field each time. Here is a solution to the problem illustrating the use of "Replace": *Finish entering your data. *Find the bacAEditor's LayoutB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMYesNo/,  , : AM PM9 Dp=u Av 2 72w27+-f3%:EAFAGA' Submitted by:€QASDocument under Review:UFirst (Given) NameVLast (Family) NameWBallot Group Membership Status:€XAY#Letter Ballot Number or Ballot Code€ZA[ email address€\A] telephone€^A_Vote:`(1) Create Comments€aAHCreate and Submit Working Group Ballot or IEEE Balloting Center CommentsH@AR  33& * Rg2*t {EQFAImport CommentsENALL OTABS# ` ABCDEFGdH^I_J`KaLbMcNOPQRgSiTjUkVmWnXpYvZw[x\y]{^_`abcde f g hijklmnoQGA Email fileE)?@ @A owner-stds-802-16@majordomo.ieee.org The comment file name should include the Letter Ballot Number and  ABCDEFGHIJKdLM^N_O`PQaRbScTgUiVmWjXkYvZw[x\y]^{_p`nabcdefghijk l m no  "#$()*+?@ACDGIJKLOPQRSTUVWZ^`cdefghilpqrstvwxۀۃۄۅۉۋیۍێۏېۓ۔ەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫ۮۯ۰۱۲۳۴۶۹ۺۻۼ۽ۿƒÃăƃǃȃʃ˃̃̓Ѓуԃ؃كۃ܃ރ'f€aA Create and Submit Reply Comments @A*  33*€APLEASE FOLLOW THESE INSTRUCTIONS EXACTLY OR EXPECT TO HAVE YOUR INPUT IGNORED. (1) Read the comments. You will probably find this easiest if you use the "Comment List" layout. You can choose it from the upper left corner of this window, or you can use this push button: (2) When you want to respond to a comment, check the "Marked" box at the top of that record. Then fill out the following fields: Recommendation: Proposed Resolution: Reason for Recommendation: You are fully justifing the buttons:€gng the buttons:€gng the buttons:€gg the buttons:€gicking the buttons:€gicking the buttons:€gowing steps by clicking the buttons:€ging the buttons:€gg the buttons:€ging the buttons:€ge buttons:€gbmit Ballot Filef9Proceed with the following steps by clicking the buttons:€gO+ A#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# cBl#[  bl[##KK##;;# Bmv#+  @iv+# >j# Dkv# 8w5 €\]Page€^A_Line€`A aSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A &'()+ €A €A €A€ARecommendation@@ByProposed ResolutionReasonSee reply details€A Fig/Table# BNA^  !"#$%*,-./0123^^_`u EDE^ "Technical, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, BindingG OKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !""Technical, Binding" comments are permitted only with the vote "Disapprove". You may submit comments of type "Technical, Non-binding". Please correct and try again.H) W()=0 W ABCDEFGHIJK^L_M`NaObPcQlEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf7# w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM     w  $,.YesNo/,  , : AM PMw w  $,.YesNo/,  , : AM PMf"$  w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PMf w $,.YesNo/,  , : AM PMf3IC dd5BDe5Bf#= q w $,.YesNo/,  , : AM PM     w $,.YesNo/,  , : AM PM          w  3  $,.YesNo/,  , : AM PM   {cTZbo|h[++ \_l)]l+ ^`l$)g_.?nAEditor's QuestionB GpA Editor's NoteB GvAResolution of GroupB GH vwADecision of GroupB GxAReason for Group DecisionB GyA Group's NotesB G{AEditor's ActionsB G€AGroup's Action ItemsB G€AEditor's Action ItemsB G€AVoterFirstNameB G€A VoterLastNameB G€A VoterEmailB G€A VoterPhoneB G€A VoterStatusG€A VoterStatus3m  ^ 3 $,.YesNo/,  , : AM PM_   `3 a d3 e3 f  3 g  3 t  3 u   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PM#39 XX+ASubmit Reply CommentsB  a   w   w $,.YesNo/,  , : AM PMf w w Aa#8 F mM5ft GM5ftM5ftGOC`E 7OC`EOC`E7 W   W   W    ÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷{xBKA Enter commentEQMAImport Global DataENALL # @ A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcdefghijklmnopqQNAExport CommentsE:NALL OFMPR$@` ABCDEFGdH^I_J`KaLbMcNQkUmVnWpXvYwZx[y\{]^_`abcdefgh`DTDTDT A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcde/A^technical@b27@;addrefertotable26inannex4inthecommentsfield@dand@as@collects@configured@'depending@figure@.from@e@.from@.from@.from@iddlecolumniscicrcular@extra@.from@cicrcular@extra@.from@deora@provide@referenced@rephreasethetwosentencesasfollowsinanycasethemihf@tspecificationshouldbeaddedevenifthisisjustanxreft@thisprimitiveisgeneratedbymihfunctionwhenitneedsto@Utoanewvalueallocateanewoneorsplittheentry@/wired@candothertlvencodingsitisconceivablethatthese@destination@differences@6easily@Uimprovement@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 jv   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   h stanwood# >S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM(s%jAResolution ProposedB GkAReason ProposedB GmARecommendationB Gnndation 1B Gn1O RR 3  $,.YesNo/,  , : AM PMU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW w $,.YesNo/,  , : AM PMX w $,.YesNo/,  , : AM PM/@B@2@I۔@'{<@ ܬ@݅@ $@5A@lb@}@@@c 19@A@D@\@@@ @ @$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,AvCgE@!Sl€`zrAPFQKRPSUTZUBN@VhA~@M@LZ<>C @@@FIH@JQ3^&vmBD€Qd9naD@Xbm{ACEe@EJoQTYB@X|CE@€ JOTYAC@XbmwBD@a@EJOU[B@|J& JQ 3 $,.YesNo/,  , : AM PMS   U   V   W   X 3 $,.YesNo/,  , : AM PMY   Z 3 $,.YesNo/,  , : AM PM[   \ 3 $,.YesNo/,  , : AM PM]   ]   No/,  , : AM PM]   1 RG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMw+#,v# 0x#  2 Ma bc dijkmvwxy!€€$€2'&()% @@@B s@A 3  $,.YesNo/,  , : AM PM77777777 7 7  7  7  7 7 7777777777771xy{€€€€€j77777777 7 7  7  7  7 7 7777777777771        Y7 ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   6" i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv    €Dtch of records in which you want to replace a field. *In browse mode, and put the cursor in the "Recommendation by" field. *Under "Records", choose "Replace". *Choose "Replace with calculated result". *In the box, write, in quotation marks, your name. Click "OK". *Click "Replace". @Af  ww    ww  ww  wwfSet up an email message for meGo to "Comment List" layout BnA€ (EQiaobingFXieGMember^ Editorial_0`1aToCbAS1. Add "Table of Contents" as section title 2. renumber pages of ToC, LoF, and LoT.S@A  c1. Table of contents section title missing 2. Page numbers (0-6) of ToC should not repeat the main text 3. Page numbers of "List of Figures" and "List of Tables" should not repeat main textd1g2220i Eunah Kim4 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=Abenjamin@wfamolari@xgreg@9hongcheng@gmathieu@nada@nadagolmiemember@peretz@1sanjeevUsrinivas@zulisesolvera@yoshihiro@'daley@gupta@hepworth@kim@liu@skomra@Ktaniuchiއtxie@memberܖ92observer@hother@ j^bindingܑܕܖxܚܬy%I>Seditorial@irw݅݉݋Y#non-binding@ tedenterpriseenvironment@=acceptthechangestosection7.4.7.2.2asdescribedin21-0@uacross@-addanewsection7.3.1calledlinkeventid@adddiscussionabouttherelationshipormappingbetweenmih@Taddrefertotable26inannex4inthecommentsfield@aaggregates@8also@Fan@*2@E BD VOTEREMAILpDs`jA.nA%€B?€A€A=CjC@C@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\j 2002-04-15Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15  w  $,.YesNo/,  , : AM PM  w AaBSn DyRoxp zqr srtyuB+zy*{QbSzaq@Hg@@PB s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMXY!€aACommentary Version@A* ww  ww*}Commentary Version # Version NotesCommentary Version Date B A€€€888r ysrtyuB+zw*{EV|GIU}n~pI~YjR[7iaGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #fFJ I 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK w  $,.YesNo/,  , : AM PMA%x  Yx% ^%  _l%@ l`l@% j%0  al0% cl%  bl@GY^6i7w"#$A=CEw€\€a@5BG4M1R/YOAC+'@€BD8, consequtive in time, of a preamble and data subchannels. --------------------------------------------- 8.3.6.3.5.2.3 should be handed to a clause-editor to be entirely rewritten. ItC needs substantial additional information on how to do this type of rotation in TDD, and it shouldn't use the word frame for allocations. How it will fit under the MAC etc.. (i.e. it needs definition on how this shifted superframe structure fits in with TX/RX boundaries)cH3  @BBA^_`abc€XXXXXXXXACreate and Submit BallotB    E 3 $,.YesNo/,  , : AM PMF 3 $,.YesNo/,  , : AM PMG 3 $,.YesNo/,  , : AM PM'   ^AAssign EditorsE 5 4 3 2 1 0 / . -  ,  *  )  (  ' & % $ "    !Q7AShow All Records in OrderE '` dDTQ8A Export Clause Editor's ProposalsE OFMPR$@` ABCdD^EiFmGjHkQ9A Import Clause Editor's ProposalsE NALL OTABSW@# `BBXXXXYYYYZZYYZZp` "Guillemette" GuillemetteQAAssign Editor 11E@[@!r@a11.@a11.@!r@a11.@802.16.1/D1-2000Q`"11"^52_ 8.2.1.2.5n'tuWdownstreamuWexistuW6M<?ACreate CommentB    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM   X , : AM PM      ~LA+Commentary: The IEEE 802.16 Comment ManagerA*by Roger Marks *@A> ww ) ww> AICreate and Submit Working Group Ballot or IEEE Balloting Center CommentsI@AR  33& + RN#Version: <<ACIABB>> (<<ACIABG>>)OView Comment ListA5For help, see 5@A> ww 4 ww>Xhttp://WirelessMAN.org B A   €€A>  ww    ww>AGo To Create Vote Page@A> ww  ww>UV sBl# #=  al=# cl#  bl# Bmv#  @iv#" sj{"#1 Dkv1# 8w#,Cjv#v 0xv#  2y#f 2f# 6{#V InV# qp#r 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}# ## ## ## # ^#  _l#  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€           25(1/11+((( 13 ( )  *  26* *).$.". /&-+,0,,--/)0+-*,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 GL4671iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. ,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl#.  .#  al# bl# 8w#,v#  2y# 2#v 6{v# In#f qC>pf# L WE@@MarkedQYAExport IEEE XMLEOTABS D[@!d$@`@A14[p 0 h[[ [[ /0 h[p / AQ^AOpen Reply Comment FileE ! FMPRQ'`QdDTQAzHHddE(HH(d'`zA'dE7*`'`+ dDTQ] w  $,.YesNo/,  , : AM PM  UU?= €Ad?2     _` a ^@"7 c>gt;Z<lt;Z b>gt;Z<lt;Zd W2&&Zgt;>Zlt;<Z:GC€A VoterMemberIDB G€A ReportNumberB G€A FigTabNumberB G ajayrajkumar@lucent.com 1IEEE 802.21 Comment Resolution for P802-21-D00-02 vivek.g.gupta@intel.com P802-21-D1.01.55€.panasonic.com+81-3-6710-2033MemberrmAComment List for PrintingB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM X 3  $,.YesNo/,  , : AM PMY   \ 3  $,.YesNo/,  , : AM PM]   ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   $,.YesNo/,  , : AM PMa   a   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   l 3  $,.YesNo/,  , : AM PMl 3  $,.YesNo/,  , : AM PM Hm   n 3 $,.YesNo/,  , : AM PMo   p  3 $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   H{   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     esNo/,  , : AM PM       esNo/,  , : AM PM         3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM    C iTkTlGTPmn{Tn{ng{Po pw~Tqpn{_PrP{T|DnP}T~5ETy(5P#3"$1"2$L63C#0 AS T3C|U#3}C<V#3ACWDGW#X^H_UYGpW \_lHUn]GW ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$Tgvhz@@ B s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM xe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes€ADocument under Review:€ABallot Number:€A Comment Date€A€A  Fig/Table# BA(B$AP  !"#$%&')*P^_` a b dnpvwy {€€€$€"€&€(€€))f1234f01234f1234f1234f/@@ B s@A 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM$,.YesNo/,  , : AM PMo RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM MaSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uA vRecommendation by€wA xRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A Fig/Table# BAN  !"#$%&N^_`a bc dijkmvwxy!€€$€%%f1234f1234f1234f1234f1234f-./01234fo ZQ 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM T 3 $,.YesNo/,  , : AM PMU  3 $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PM OY 3 $,.YesNo/,  , : AM PMZ 3  $,.YesNo/,  , : AM PMA#x  x#  #h #h# ##X #X# # d# ^ #k  _lk#  `  @BBA* *^_` a b dnpvw y{€€€€€€           XX(X$X"XXXX& X X X X  X)X X XXX XXXXXIn # u L u#  @BBA( ( DmvkPx QdTykv zX{cTyKXPTwbk_+j)€UA€VA€XAYType€ZA [Suggested Remedy€\A]Page€^A_Line€`A ~PmRbapwcTsjtbTuiv4PvCTw A#x x#  #; d;# ##+ #+# ## #9  _l9#  `l# B#t  alt# ^# cl#  bl# Bmv#  @iv# >j#v Dkvv# 8w#f, EJG?W]IV<fS // €TA€UA€VA€WA€XA YType€\A ] Starting Page€^A _ Starting Line€`AaSection€bAcSuggested Remedy€dA  ^`BlHU_GW`alHWUaWTbblIVhc4ID dd5BDe5Bf$Tgvh| AS T3C|U#3}C<V#3ACWDFoVX^HBUlY=TZbe[EmU \_BlHUh]WTbcHU3c3IC dd5BDe5Bf 0""/1"L1 B+``al)a,aTbc -6cI dd De ]fccTgvUbhT[biCHcTjxPkcTl~PmRbapwcTsjtbTuiv4PvCTw X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   ANU#OV#V+X^5)SYcTZbh[ +( \_l) ]I+g ^`l*)I_|  3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM       3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM C3C#0aTjR_R_TivR]_PR_XTmvRz_P#D$wTkvTvTxP_<TR_P*OT   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    QEy*PGTT{GiTPW^TpGT]PanPodTnn{P|/TFJEU `lHUEUalHdUEKUiHUF _<TR_P*OT  3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM       3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM3C S // €TA€UA€VA€WA€XAYType€ZA[Suggested Remedy€\A ]Starting Page #€bAcComment€dAe Comment #fComment submitted by:€ADocument under Review:€ABallot Number:€A  Comment Date€AProposed Resolution€ARecommendation by€ARecommendation:Resolution of GroupDecision of Group:€A€AReason for Recommendation8Note: Group may also edit and export Comment Type above.€A€A&Reason for Group's Decision/Resolution€AGroup's Action Items€A Group's Notes€AEditor's Actions€A Line #€`A aSection€bA cChange€dA ^w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM      esNo/,  , : AM PM       esNo/,  , : AM PM     @@B s@A 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PM$,.YesNo/,  , : AM PM RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM RJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3 $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PM RO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM RT 3 $,.YesNo/,  , : AM PMU  w $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PM Y 3 $,.YesNo/,  , : AM PMZ 3  $,.YesNo/,  , : AM PM[  3  $,.YesNo/,  , : AM PM #=# ##- #-#_ ^_#  _l#  `l#m  a Hm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv   $,.YesNo/,  , : AM PMv   v   $,.YesNo/,  , : AM PMv   v   X1XXXX XXX X X  X2 X6 X4XX XXXXXXX"X#X'X%X)X+X.X0AComment List for ProjectionB   U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMSUAMark Found RecordsE[@!@A0"1jP l+  jP l_ jP m0*@ @@A lAABB l*"Marked"MarkedQVAUnmark Found RecordsE[@!@A$1jP l+  jP l_ jP m0*@ @@A lAABB l*""keQWAFind Marked RecordsAzHHHV E(HH(d'`zA'd b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMx(S@A :http://WirelessMAN.orgdocs/Commentary.htmlQ X 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]   ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   e W y}zy kUa55nn!b,!n]bfHX7X8T=\=ngfGH\H\&&Tn=78f8QQ!f,8Qnbn=7X7U]nH&7]HQg0Hn,!]k&!XnbnXX88 7=n\n ]n7&fn7%g, @! %K 0Ձ9uNOOkA9O FPTH9RPTHalisNAMEMSPCMSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataI'jA ^.B"EjA#bA$^(@6C)bA*vA?bAA@cAAbACHEkD@Dd@GbB!AW{IbAJbBczL@bAObAUPbAQbAvPRvASbATbAvA#UbA^V^AdEZ@5m^cIFcecGgGaNcandothertlvencodingsitisconceivablethattheseVand/or:Wh fÃh0ېÃh@ÃhPÃh`ÃhpÃhÃhÃhÃi[Ãi Ãi0IÃi@ÃiPÃi`ÃipÃiÃiLÃiMÃjÃj JÃj0IÃj@5ÃjPÃj`KÃjpÃjÃjkÃjÃq݇Ãq Ãq0یÃq@ÃqPÃq`ÃqpÃqLÃqfÃqÃrcÃr ݈Ãr0mÃr@ÃrPgÃr`ۃÃrphÃrdÃrÃriÃsÃs jÃs0oÃs@hÃsPkÃs`MÃspNÃsۄÃslÃsgÃtÃt /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/20hEAjayFRajkumar(cgeteW-WWW=WWWWiW{WWWWWgetsܫWgetstatusresponsesetWgetstatusresponsesetismissingVggsnWgiveۅWWWgivenܭWWjWWWW WWzWWWglobalIWglobally۩WWWgloballyreplacespecificationwithstandardwhenreferring۩VglonassWgmiiWgni@Wgninotintheacronymlist@Vgni/lli/hlsiWgo6WWWWWW6W6W6W6WNode" definitions. d6g2239 2006/05/01 2006/04/24 EYogeshFBhattGMember^ Editorial_15`46a5.2bd7g2784 2006/04/29 2006/04/24bjin"W?WWܾW,W|WWWWW+WYWtWzWWWWincorrectvWindependentWindicateWWindicatetransmissionstatusofapduVindicatedܾWindicationWWinfouWWYW{W{W{W{W{W{Wrfaces,WinterfereWintra-technology?Wintra-technologyhandoverhorizontal-handover?VipݍWis?WaWuWW+WܶWW W݄W,W1W3W>WKWgWit@WaWܶW W,W>Wit's>Wits W,Wjust,Wknow WhWknown?Wl-shaped,Wl2uW,Wl3,Wl4,WlastWlayer,W>Wlayers W,W>Wleft>Wlength|Wlike>WlinkWWW W>WKWlistWlmakeWlmake2differentdiagramsoneforlocalcommandsoneforreVlocWܽWlocalWWgWlocatedܶWlook݄Wlower,W>WWMDa5.6.12Yj5.6.1.15.6.1.245.6.1.355.6.1.4H5.6.2ܰ5.6.2.1ƒZ[5.6.2.25.6.385.6.3.15.7(5.7.1Ã҃5.8)*n5.8.16.1.3W;<6.1.36.2.2V6.1.4ăӃr6.1.5ݒ6.1.5.2-.߃ޫެ6.1.6Nܳ6.1.76.1.8ŃJ6.2.16.2.2W=?6.2.3K6.2.4y>s6.2.56.2.5.1/:ܴޔޭ޸6.3;}6.3.1?@AǃȃɃ˃ܵܶՃփ׃LMNQݓ@A޽޾޿6.3.2KZ[\ۑےۓʃ̃̓΃σЃу҃ !"#ܷܻܺ؃كڃۃ܃݃ރ߃OPRSTUVW|݉ݔݕݖtP5jparagraphWparametersށWpart,WWWparticularuWpassedWpduWpeersWper,WperformanceWjWpersistentWpicture=WpleaseݍWjW=WpleasebemorespecificaboutthegivencomplexityandcompujVpleaselookatdoc21-06-0612-00-0000-rnetworkppt=VpoaܾWWdWvWpoasvWpointsWpositionWpossibleuWpptW+W=WpreferzWprimitive{WWpropertiesvWpropertyvWproposal|Wproposed|WWprotocol|W}WWprotocols WprovidezWprovidedjWW=WprovidesWWWWWWy/response|WquestionWratezWrather,Wreadable=WreasonWredundantށWreferenceWreferencepointsareusedinthedocumentegline24-49pagVreflectedWregister/deregisterWregistr/deregisterWrejectWrejecttheproposedremedyVVBWg! QEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5BfhGcpageWKWیWWWWYWhWܬWaW݆W݇WWWWWWWWW0WmWWWWWWpage5secondsentenceitshouldallinsteadofalonelis݆Vpage86line64changeittoupperlayersitjustsaysupper݇Vpairs>WCWCWCWCWCWCWCWCWCWCWCWCWpartners_WaWpartocularZW]WpartsەWWpassSWpassingSWpduWperformuWۂWېWperhapsېWWperiod۳Wperiodic۳WphraseWWphrasing۱Wpicture۽WplaceqWsW۟WplacedYWWplaying:W;W<W=W>WpluralWpluralformVpoa_WaWۇWۈWۊWWpoas_WaWpointۊWpoints۬WpoorlyZWposWpossibilitywWpossibleۈWpossiblyKWWpotential\WpppWpre-defined_WbWpre-establishment\WpreparationۅWvby comment 352, 360w Superceded 2006/09/21 2006-04-306EXiaoyuFLiuGMember^Technical, Non-binding_56`29a6.3.6.2bOLink Type is not necessary to put here if the proposed general mechanism works.cA general mechanism for TLV type IS Query/Response is discussed in the document: 21-06-0606-00-0000_loc_info_over_tlv.doc. Link Type in the additional parameter could be put into MIH_Get_Information REQUEST frame as one of the InfoFilter. d907g2214w Superceded 2006/09/21 2006-04-30EXiaoyuFLiuGMember^Technical, Non-binding_88`47a7.4.6.1byReplace the first sentence with: "This primitive is generated by upper layers to control the behaviors of link layers". cayers". cayers". cᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃᬃ ^ ܚbc:Header TLVs are defined but no values are assigned to themd890g2270wAccepted{k) done 2006/09/21 2006.04.25Marked ܛEVivekFGuptaGMember^Technical, Non-binding_4`30a1.6bRemove section 1.6cDefinition of interoperability and compliance mechanisms is outside the scope of the 802.21 standard. This functionality/capability is handled elsewhere outside of IEEE.d31g3221vwRemove this section. Need more offline discussions on how we plan to handle compliance and interoperability for 802.21wAccepted{k) done 2006/08/29ܟEVivekFGuptaGMember^ Editorial_9`38a3bAService Primitive - Conceptual abstraction describing the information transfer that occurs between N-user and N-layer in the provision of a service. The abstraction resides in the exclusive specification of the service provided and not in the means by which the service is provided@A> 33O  33S 33>Y^editorial݈݉݉݉wwwwwwwws on the new link --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | SuggestedNewLinkIdentifier | Boolean | 0: | 0: Current POA can select another new network Identifier for | | G | | handover. | Unchangeable | | | 1: Current POA can not select another new network Identifier | | | | for handover. | | jrepositoryWrepresent|WrepresentationW,WvWrequiredށWWres+Wresponse{WWrfc?Wsame0WWsamecommentascomment170VsapWsapsWsayingWschemaZWvWjWWsdos"Wse,WsectionWgWuW|WWYW}WWsecurityܾWsee@WWseecomment315andchangefigureaccordingtoit@Vselected?WselectionWserveWservicejWsessionWWWset|WseveralܾWshould?WܾW|WWWWVWWWWshouldbediscussedcarefullyVVshouldthemihusersknowaboutthesessionidVVVVVVhVhVhVhVidhVhVhVhVhVidhVhVhVhVhVhVhVhVhVhVhVhVhVhVer^Technical, Binding_38`3a6.1.6nstead of operators. c.3, Binding_140`140a Annex A-1y used for references.5/01eHcdestinationWWWVWWdestinationidentifiedetail[W WWdetailedWWWWdetails+WݽWWWdetectWdetectedSWSWݛW?WWWWdetection?WWdetects?WdeterminationWdetermineWaWWWWWdetermined WޖWdeterministic WdevelopedܭWwWxWyWzW{W~WWWWWWdevelopmentܭWdeviceWWdevicesWWdhcp݋Wdhcpv6WdiagramۿWWW݃WW WWdiagramconfusingexplanationofmeaningofdottedlinesisVdiagramdoesnotclearlyrepresentthetextbelowthefigureVdiagramneedlesslycompressedۿVdiameterWdifferenceېWWWWWWWWWWWWWWWWWWWW2g2229 2006/04/28&9%pofWW)W;WܰW{W݃WWkWvWofficialݓWon۽WܵWܾWW{W݃WݒWݓW@WoneۅWۓWWܾWaWonlyWRW{Wonlyaddednew6.4andsubsections{Voos/securityܾWopen{W2WorۓWܾW݃WoriginalAWotherܰW{WoutWp9-l6ܡWpage݃WkWpage/line/sectionWparaWparameterJWݜWparametersW܁WݜWpartW)WܰWWkWper.WݓWWpic>WpickۓWping۴WpleaseݜWpopulateۓWportۓWposܥWpppWppt݃WݓWpresentWpreviousۖWލWprimitiveWRWprimitives۽Wprobably;WܰWprobablynoneneededܰVproblematicgWprocedures-WWކWproposeaWprovideWWprovidedݒWquestions{WradiusJWۓWratherJWre-defined-WWކWreadWreadabilityDWrecommendedܾWbb7RW|W(WݗW1W6W[WlWW7.1.2CW7.2.2.1lW7.2.2.2lW7.2.3.1kW7.3SWlWlWlWlWlWlWlWlWlW.1.1functionېV7.3.1.2ېW7.3.1.2semanticsofserviceprimitiveېV7.3.1.3ېW7.3.1.3whengeneratedېV7.3.1.4ېW7.3.1.4effectonreceiptېV7.3.2ېW7.3.2.1ېW7.3.2.2ېW7.3.2.3ېW7.3.2.4ېW7.4W7.4.1.1ۊW7.4.1.2ۊW7.4.101W7.4.10.1.2ۂW7.4.10.1.2semanticsofserviceprimitiveۂV7.4.112W7.4.123W7.4.134W7.4.14<W7.4.15.1.2ܘW7.4.15.3NW7.4.15.3.1ܙW7.4.15.3.2oW7.4.15.3.3oW7.4.15.3.4oW7.4.7.2.2ۄW7.4.8gW8WJW|WGWRWܑWܔW8.2.1rW8.2.1l2dataframespacketformatrV8.3tW8.3protocoldescriptiontV8.3.1qW8.3.2.3ݳW8.3.3.2W8.4.2.13hW8.4.2.22܂W8.5W8.5.1.1\W8.5.1.2\WV.WjlinkܾWWWWWWWlinksWlistܾWvWWlistedܾWlocWYWlocalWWWlocatedWlocationsWlongWlook=Wlower,WmacܾWWmakeWWWWWWÃ$`Ã$pÃ$8ܰEVivekFGuptaGMember^Technical, Non-binding_31a5.6.2b3Come up with a more accurate classification scheme.cA@"Media Independent SAPs" MIH_SAP and MIH_LINK_SAP include functions/primitives that may carry technology specific parameters (MAC Addresses, Security/QoS info, etc.). As such these primitives may not always be completely link/media agnostic. Hence "media independent SAP" may be inaccurate classification of these SAPs.@d227g3242pprobably none needed [ Vivek] This is now getting addressed by other comments as well. No changes are needed as part of this comment. vNMIH_LINK_SAP is Media specific: MIH_SAP is still a technology independent SAP.wAccepted-Modified{l) none needed 2006/09/21eded 2006/09/15ddt and remove it. Typically, "typically" is not used in standards d255g3228{k) done 2006/08/28 ܵEVivekFGuptaGMember^ Editorial_42a6.3.1ivekFGuptaGMember^ Editorial_42a6.3.1 {doneWWWW!W"W#W$W&W'W(W)W*W+W,W.W/W0W1W3W7W8W9W<W=W>WwW݅W݆W݋W݌WݐWWWWWWWWpWqWeWeeditordisagreesVeditorWiWW#WWW,WitodoVV#VVV,VinܥWinputWW&WinstructionsۢWW WW-W6WjܥWjinprogressܥVkWWW WەWۖWۗWۘWۙWۚWۛWۜW۝W۞W۟W۠WۡWۣWۤWۥWۦWۧWۨW۩W۪W۫WۭWۮWۯW۰W۱W۲W۹WWWWW WWWW,W.W/W0W1W2W3W4W5W6WܛWܟWܠWܡWܣWܤWܧWܨWܫWܭWWWWW!W"W#W$W'W(W)W*W+W,W.W/W0W1W3W4W5W7W8WDcthose0WthoughmWܕWWWWWWWthoughithasbeenagreedinthelastmeetingthetlvssentܕVthree-WtWuWWWthresholdGWIWZWޖW5WlWmW4WoWWWWWthresholdsۉWWZW`WaWoWWWWthresouldWthrough7WWOW?W8WWWthroughoutWWthus۔WWWWtidWWWWWthus۔WWܐWWtidWWWWWWthus۔WWܐWWtidWWWWWWthus۔WWܐWWtidWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmWnWoWzW{W|W}W~WہWtreesjWkWmWnWoWzW{W|W}W~WہWN"bintra-roaming۫WWWintra-roamingshouldbedefinedthewhole2ndsentenceinth۫Vintra-technologyAWەWintroduceWWWintroduceterminologytodescriberoaminghomenetworkandVintroducetextsayingthatschemaquerysupportispurelyanVintroducetheconceptofvisitedandhomenetworkswhenVintroducethemodificationsproposedinsubmission0598intoVintroduced8W WWWintroduction`WW/WWWinvokedWWinvolvedWWWWWWWWcWdWiWjWkWlWmWnWpWsWuWvWwWxWۂWۇWېW۝W۶W۹WWWWWWWWWWWWWW#W)W*W2W=WGWHWKWLWNWRWTWUWVWWWXWZW\W]W^W`WdWkWsWtWzW{W|W܅W܆W܋WܕWܟWܡWܢWܤWWWdÃhpÃhÃhÃhÃi[Ãi Ãi0IÃi@ÃiPÃi`ÃipÃiÃiLÃiMÃjÃj JÃj0IÃj@5ÃjPÃj`KÃjpÃjÃjkÃjÃq݇Ãq Ãq0یÃq@ÃqPÃq`ÃqpÃqLÃqfÃqÃrcÃr ݈Ãr0mÃr@ÃrPgÃr`ۃÃrphÃrdÃrÃriÃsÃs jÃs0oÃs@hÃsPkÃs`MÃspNÃsۄÃslÃsgÃtÃt Ãt0mÃt@ÃtPOÃt`]ÃtpPÃtۋÃtÃt܎ÃuݭÃu QÃu0Ãu@^ÃuP|Ãu`_ÃupRÃu6Ãu`Ãu ÃvgÃv "Ãv0SÃv@#ÃvP 7cARepetitive sentences: Remote MIH events originate at remote MIH Function. They traverse through the medium to local MIH Function and are then dispatched to MIH Users that have subscribed for these events within the local stack. Remote MIH Events traverse from the remote MIH Function to the local MIH Function and then from the local MIH Function to the local upper layer entities as shown in Figure 14.d264g2241{k) done 2006/09/218ENada, Golmie, Member^ Editorial_40`30bA?Replace "Link Command originate" with "Link Commands originate"?@Af 33  33 33,  334 33fcA(Syntax error in "Link Command originate"(@A> 33  33 33>d291g2242i Eunah KimmAccepted{k) done 2006/09/21:ENada, Golmie, Member^Technical, Binding_42`24_42`24_42`240 <܄cAThe decription is the same as the request. The status information contained in the MIH_Configure Response only indicates if the configuration was successful or not. In some cases, it may be of valuable information to know which configuration element failed.d839g2321{k) done 2006/09/21Marked܅ENada, Golmie, Member^ Editorial_135`33bChange the description to This message is used for communication between MIH Function on client with MIH Function on network. The function is used to respond to an intent of handover initiation. c8The description of the mesage is the same as the requestd843g2322{k) done 2006/08/29 ܆ENada, Golmie, Member^ Editorial_136`4bAUReplace "This is used to respond the result" with "This is used to return the result"U@Af 33  33  33C  33I 33fcA4Syntax error in "This is used to respond the result"4hi76{c) instructions unclear 2006/09/21he system"d125{c) instructions unclear 2006/08/31Marked7EFarrokhFKhatibiGMember^ Editorial_18`37a5.3.2b*Change "be communicating" to "communicate"cTense consistencyd134{k) done 2006/08/29 8EFarrokhFKhatibiGMember^ Editorial_18`65a5.3.2bremove dash in "link-state"cInappropriate use of dashd139{k) done 2006/08/29 9EFarrokhFKhatibiGMember^ Editorial_18`26a5.3.2bf" from the visited network about that visited network or about home network via visited network PoS."cUnwieldy sentenced132{k) done 2006/08/29 W@WjWuW|WWWWWWWWWWWWWWWWW"W"W"W"W"W"W"WWWWWWWWWV73 {kdone4V5V6V7V8V:V;V<VAVBVCVDVEVGVHVPVQVSVTVUVVVWVYVYVܟVܠVܡVܣVܤVܧVܨVܫVܬVܭVܱVVVVVVVVVVVVVVVV!V"V#V$V'V(V)V*V+V,V.V/V0V1V3V4V5V7V8V9V<V?V@VAVGVHVKVMVNVOVPVQV^VbVwV݅V݆V݉V݋V݌VݍVݎVݐVݑVݔVݕVݖVݗVݘVݚVݛVVVVVVVVVVVVVVVVVVVVVVV V VVVVVVVVV-V.V/V2V4V5V8V:VAVIV_VlVnVpVqVtVuVvV1Vl#W?W^W`WۺW'WIWWW=W>WTWW2& 2pand.W:W;WRW{WݜWWWanswer{Wanymore)Wappendex۽WareWas)WRWܾWݛW1WatۖWWbeۓW:WWYWbetterDWWWbit1Wbits)WbothWbothareusedaddedtheadditionaldefVbreakWbullet݃WbutܥWW&Wby?W^W`W:WIWcan:WcaseYWcasesܥWchangeWchanged2WAWchangedto2octetsconsistentwiththeoriginal6.3.4.1.2AVchangedtoanmihthroughoutthedocument2Vchanges۽W:WYWܥW{WCWchangesmadein5.5.5text۽VchangingWcommendRWcomment?WۖWW.W;WSWYWcomment9iseditorial;VcommetCWconflictWconsistentAWYWcontainerZWcontributionZWcontribution21-06-0711-00-0000-itlvretrievalnoexclusionZVcontribution21-06-0712-00-0000-itlvcontainerdoneZVcopyۓWcreateۓWzWWY+tc6Length of TYPE_IE_LIST_OF_NETWORKS should be variable.d340g2412wAccepted{k) done 2006/09/216uEKenichiFTaniuchi^ Editorial_52a 6.3.4.3.1bA,Length od of CivicAddressElements in octets.,@Af 33   33   33fctypo " length od ..."d428g2414{k) done 2006/09/2110 vEKenichiFTaniuchi^Technical, Binding_61a6.3.8.1bDReplace Figure 21 with section 2 of 21-06-0460-02-0000-Basic_Schemac-subClassOf is not defined in the Figure. -the direction of arrows of domain from Civic-Location-Information , Civic-Address-Element are wrong. -longtitude, longitude-resolution should be longitude, longitude-resolutiond468g2415i Vivek Guptajek Guptajek GuptajjVcmihcapabilitydiscoverprocedureneedstobedistinguishedVmihcapabilitydiscoverresponsemessageIVmihcapabilitydiscoveryisspecifiedasmaybedonethroughOV$ @ @btheencodingformatisdefinedastablebelowGVtheencodingformatisdefinedintable8GVthefirststepistore-organizetheiesintoatreeormulttVinthetablebelowVVencodingformatisdefinedasshowninthetablebelowVV%cbeyond:WmWbillingbWbinding-WiWbit)W1WލW}WWWW?WlWbitmapWWbitsWWWWblerGWIWJWlWmWblockGWIWJW,WlWmW~WbodiesWboilsWbold:WW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"WddynamicdatacomponentscanreadilybeVbound:WboundaryWboxWboxes-WWbracketsWWfWbraodcastfWbreakۮWbreakdownsentenceforbetterreadabilityaftercommaۮVbreakoutWbriefmWbroadcastۈWWܺWWOWPWQWbroadcast/multicastܻWclayer"WLWOWPWQWRWSWTWUWVWWWcWdWeWۉWېW۪W/W7WQWZW`WfWiWkWܤWܫW+W0WaWݍWݐWW WW"W$WޖW5W\W]W^W_W`WaWbWcWdWeWfWgWhWiWnWWWWWWWWW W$W%W?WzWWWWWWWWWWWWWWWWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWVmnctoward3WWtowardsWtowarsWtrackWtrafficWW WWWWtrailingWtramissionWtranmissions Wtransaction۔WuW WWWW WWWWtransactionidisnowpartofmihffixedheaderassuchitcVtransactionisnotdefinedanywherethustransactioniddoes۔Vtransactions WWWWtransferۨW WܟW|WtransmissionWtransmitTWUWWWtransmittedWtransparent*WWWtransportwWWWW܋WW W2WfWgWhWiWWWW W W WW WrW~WWWtransportsWtraverse7WtreewWxWyWzW{W~WWWWWWtreeswWxWyWzW{W~WWWWWWWWWWW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2WہWtbannexۀWDWEWܚW}WW>WXWWWWWWWW<WWannexesWanother?WpWW"W'WaWWWWpWWWanotherwordlikehandovershouldbeusedVanyPWRWUWWWܫWWPWWW W W8WWWWWW)W<WWanybetterinfactit'sbettertoconvertthedatasoVanythingpWapWܵWap/bsWapisuW~WappearanceMWappears(W,WappendەWappendaparagraphthefollowingitemsarenotwithinthescەVەVWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYW7WCWTWUWVWWWXWYW\WcWsWtWxWܪWܴWܺWܾWWWW W(W*W0W1WJWareaWaren'tWarrayۉWarrivesWarticle2W B3 ABCDEFGHIJKdLM^N_O`PQaRbScTgUiVmWjXkYvZw[x\y]^{_p`nabcdefghijk l m nom noÃ=Ã>Ã?à Ã0Ã@ÃPÃ` dDTN{ehWWdWeeditordisagreeshVVdVeditorhWWdWh-WܾWWWކWhdefertonextround-VܾVVVކViۃWbWitodoۃVbVinRWCWV@V@V@V@V@V@V@V@V@V@V@V@V@V@V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V=V _bcA:Syntax error in "Number of parameters in LinkParamterList":@A>  33)  339  33>d551g2284{k) done 2006/09/21Marked`ENada, Golmie, Member^Technical, Non-binding_78`37bRemove line 37-43 and add reference to the definition of the link parameter types defined in the Link_Parameter_Thresholds.request primitive (after a definition is agreed upon) see comment 40 (518/525). cThe link layer parameters defined here must not be examples. They LinkParameterType must be defined and match the definition located in Link_Parameter_Thresholds.request.d552g2285vSPlease refer to comment 518/525 and add the table/reference from their accordingly.wAccepted{k) done 2006/08/29 aENada, Golmie, Member^ Editorial_82`35bA-Replace "Specific t IE" with "Specific to IE"-@Af  33  33  33'  33)  33 vneedWjWWWWWWWWW"W&W)WVW|WWWWneedbothnumberofoperatorsandlistofoperatorsVneedclarificationforrequestparametersupdatescanresponseVneedmoreclarificationandappropriatesuggestedremedy)VneedtoprovideclarifyingtextalongwithcommentVneedtostilldefineerrorcodesforerrorcasesVneeded WWWneedsW\WWWWW WWWneighbor?W?WWWQ7cserviceKWW5W:WܟWܬWWKWeWzW}W#W(W)W-W>W?WjWWWWW:W?WIWWWservicecontinuityisdefinedbutitisnotclearwhattransVserviceprimitiveconceptualabstractiondescribingtheinfoܟVVܟVܟVܟVngtheinfoܟVservices+W۾W+WW݂WݏWWW>WnWީWWWIWservingۇWW:W!W"W#W*WsessionsWWWWݒWݵWWWUWhWsessioniddoesnotmakesenseUVsessionidentifierismissingVsessionidentifierneedstobedescribedݒVsessionisnotdefinedanywherethussessioniddoesnotmakVsessionsWsetWFWGWHWIWۄW=WTWUWVWWWXWeWiWkW|WܻWWWEWFWGWHWޚWWWWWWWWWW W3W4W5W6W:WxbissuedkWWWWWitDWLWSWVWWWhW۔W۶W۹WWWW#W2WܤWܾW݅W݆W݇W݉WݑWݚWݭWWW,WNWVWWW[WWWWWWWWWWW(W,W<WlWpWrW{WWWWWW#Witappearsthatreferenceistothedefinitionofoperator-n(V,VitmaybeinterestingforanupperlayertoregisteronapeVitseemsthatreportavailabilityshouldoccurafterresponsVitshouldnotbethecaseinsteaditshouldbethatthenumblVitwouldbemoreeconomicalforthenetworktobroadcasttheVit'sWWWWityshouldoccurafterresponsVitshouldnotbethecaseinsteaditshouldbethatthenumbVit'sWitem۪WW܍W#W%W0WitemsەWitmeWitswWWWܡWܤW(W,W0WW W!W+W>W8 =cshouldW#W,W-W0W[WWWW WW'WHWeW݅W݆W݋WݍWݓWݔWݕWݖWݘWݜWݵWݺWݽWWWWWWW:W>WBWCWNWYWnWqWtWvW|WވWފWދWތWލWޖW1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W0W0W0W0W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲WRbsourceW&WWWsourceidentifierۋWW|WsouthboundWsparqlqW}W~WހWށWނWރWxWzWWWރWރWރWރWރWރWރWރWރW WsWvWwWstartOWVWstate,WstatementW Wstation'siWstatusUWstep_WstopWWstoredUWstrengthFWGWHWIWJWstringkWnWstringsbWstructure#WZW]W_WbWsWsubnet?Wsubsection'WsuccessUWsuccessfulxWsuchW W#W'WAWDW_WsWsufficient#WAWsuggestedZW]WsuitabilityTWsuitablePWuWsupAWsupport W?WAWbWpWsupported.WAWLWuWsupportspWuWsupposedkWnWswitching?WVWsynchronouspWtableW/W0W5W:W;W=WEWJWNWZW[W\WhWtakeOWPWQWTWUWVWucconfusionW>WWWcongestion WWcongestion-safe WconiferlWconnectmWconnected:WWWconnectionrWWWconnectionsWconnectivityW:WܡWWW?WconnectivityprotocolisbeingmigratedawayfrompppVconsiderWlWWWconsidercase2ieifthenumberofoctetsoccupiedbythelVconsiderthelinethatsaysafterregistrationthemihusersVconsiderthesentencealocalmihgetstatuscommandcausesVconsideration?WconsiderationsWconsidered W Wconsidering'W'W'W'WWW7WHWڤWىWيWَWُWْW٠W٣W٤W٨WٮWٰWٱWٲWٴWٷWٺWٻWټWٿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWC^technicalWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW14Consider removing "Generic"c="Generic" may convey conflicting notion wrt "media-dependent"d182 2006/05/1423`38a5.5bConsider removing "Generic"c="Generic" may convey conflicting notion wrt "media-dependent"d182 2006/05/14ۻESanjeevFAthalyeGMember^ Editorial_22`53-54a5.4.3bPChange end of sentence to " to effect seamless handover across these networks."cUse of "roaming" is confusing.d179 2006/05/14ۼESanjeevFAthalyeGMember^ Editorial_23`38a5.5bConsider removing "Generic"c="Generic" may convey conflicting notion wrt "media-dependent"d182 2006/05/14 Y?bcAThere is no need to define new terms "horizontal handover" and "vertical handover" here. Terms "intra-technology handover" and "inter-technology handover" are well-known and sufficient already. @A  33d315g2275iWolfgang GrtingjA intra-technology handover = horizontal-handover inter-technology handover = vertical-handover this terminology is also well known and is defined in RFC 3753 - Mobility Related Terminology one terminology should be selected and used through out the draft@A* 33  33*p superceded by an earlier comment{l) none needed 2006/09/21 2006/04/24@EQiaobingFXieGMember^Technical (was Editorial)_42`33a6.3.1bARemove Figure 19.@A  33ccnd "vertical handover" here. Terms "intra-technology handover" and "inter-technology handover" are well-known and sufficient already. s{jcontentsWWcontextܾWWcontributionjW}WcorrectZWWcorrectlyvWcostjWvWvWvWvWvWcostBWcs+W>Wdcn+WdecideWdecidesgWdefineݍW>Wdefined?WݻW1W3WdefinitelyWdeletewWWWWdeletefigure24wVVVdeletethefigureVdependentWdeploymentWdescribeTWdescribed+WdiagramW>WdiagramsWWdidn't1W3WdifferentWW,W>WdirectlyKWdisagreeaWܶWWݳdisagreeifthissectionisremovedthenitisnotpossibleaVdisagreeitisnotadvisabletorestrictisrepresentationnVdisagreethereisnoneedtoexplainwhereitislocatedܶVdisagreed|WWdisagreedfortransactionidVdiscovery+WdiscusseduWݴW+Wdo+WWWdoyoumeanherefigure23VdocWܽW݄WݻWKWdocument+WS^editorial W#$W(W)*W+W?@WAWCWKW`pWqrsWtvWxیۍۏۖۗۘۙۚۛWۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩ۭۮۯ۰۱۲۹ۺۻۼW۽WۿÃăƃǃȃ˃̃̓Ѓ؃WރW './02345678?@GIKMNQRT^cdefggbshows?WwW}WWWsideۧW5WsignalGWIWJWۉWYWlWmW>WsignalingPW݃WWsignificantWsimilarۮW۰WW,WWsimple W1WsimplyWsince2WܡWW1WWWWsincemihispronouncedlikeemihitisnecessarytoputt2VsincethegenerationoflinkgoingdownisimplementationdeVsingle*WWWWsinrWsionAWAWAWAWAWAWAWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWُWْW٨WٯWٰWٴWٷWWWWWWWWWWWWWWWWWWWW;W>W@WAWlinkconfigurethresholdsaddsinrinadditiontosignalstrَVVmUbchangetextto?VAVIVLVcVdVeVsVxVmVnV|VVVVchangethecategorytocommandserviceVchangethecurrenttexttoVchangethecurrenttextwiththefollowingthemihsapfirstVchangethedefinitionto/Vchangethedescriptionto܅Vchangethefirstsentencesofitembasfollowsmihfunction0Vchangethefixedheadersizefrom6to8bytesinthefigureܑVchangethelefthandstacknamefromlocalstacktopeer1staVVchangethelengthfieldto4ݵVchangetheoccurstothatoccurs.VchangetherepresentationfieldfromݕVchangethesizefrom6to8bytesinthefigure27ܔVchangethesizeofaidto10WVchangethesizeofopcodeto2WVchangethetextforthisitemaccordinglytoreflectthatthVVV V V VVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVouttheavailabilityofacceVܙW28`T`‚:hێ'4ܑăݭI5^aᮃᵃ55558_eܓܛʃӃ݉ݎݷ̓KLe‚BNXܣ(-kʃ܃‚C/k׃4ݬޭ‚D@{܅AIdx"|ގ޾-‚Eۋەۙ۵i܍փ%1‚FɃaܫܭM‚G%.4Pу߃12;]^ށޣެ޲΃!C‚H`҃7`ޙ׃9‚ILgےۓۣۨۼ57=Gܟڃ.ݐݔ~‚JHMUۂ Z܎ƃ΃ݓ݃/ƃ˃Ӄ5‚QB۹ܱy݀./‚R|ۅ۫݃Bȃ#‚SQXm(/Cܦ r3‚TKNjۯp TޚɃ̃؃ :‚U0ۉ,уOޮUpinsteadofremovingwordchangingittoseamlessseemsbetteVinstructed۽Winstruction۽WݓWintentionWinter-technology:Winter-technologyhandoverandintra-technologyhandoverscan:VintoܾW݃Wintra-technology:Wintroductory݃W;beventIWLWOWPWQWRWSWTWUWVWWWpWۉWېWWRWSWTWUWVWWW^W܃WbWݍWݛW#W(WIWދWmWWWWWWWWWWWWWWWWeventiddescriptionRVRVRVRVRVRVW/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/WÄ9CمÄDEٝÄRVPÄSrىÄWXٌÄbgفÄdenÄfhsÄijZÄqrٖa1.1H1.2IJKLMNOP1.3Q1.5Rv vbA  33  33  339  33@ 33l  33v 33  33 33hat help to analyze and coordinate the payload are embedded."@A 33\  33^ 33  33 33  33 33cqSyntax error in "additional identifiers are present that help to analyze and coordinate the payload is embedded."d746g2305 2006/08/13 uENada, Golmie, Member^ Editorial_116`1b Remove line 1cRThe Transaction ID is already defined in the Fixed Header part of the MIH message.d751g2306 2006/08/13 d d 6g2305 2006/07/20uENada, Golmie, Member^ Editorial_116`1b Remove line 1cRThe Transaction ID is already defined in the Fixed Header part of the MIH message.d751g2306 2006/07/20=(btoanewvalueallocateanewoneorsplittheentryVtoimproveconsistencyhandoverdecisionmodule.VtomihfnetworkmihmobilenodeVtooneofthefollowingtypeswVyVÃf@mÃfPޖÃf`TÃfpFÃfUÃfÃfGÃgVÃg HÃg@WÃgPÃg`cÃgpdÃgeÃgÃgۍÃhaÃh fÃh0ېÃh@ÃhPÃh`ÃhpÃhÃhÃhÃi[Ãi Ãi0IÃi@ÃiPÃi`ÃipÃiÃiLÃiMÃjÃj JÃj0IÃj@5ÃjPÃj`KÃjpÃjÃjkÃjÃq݇Ãq Ãq0یÃq@ÃqPÃq`ÃqpÃqLÃqfÃqÃrcÃr ݈Ãr0mÃr@ÃrPgÃr`ۃÃrphÃrdÃrÃriÃsÃs jÃs0oÃs@hÃBÃCÃC ÃC0AÃC@MÃCPÃC`ÃCpNÃCÃCÃCÃDݓÃD KÃD0ÃD@ÃDPOÃD`06/08/14   jA1. Link transmission events are ***local only*** (see line 47, page 38, in Table 3), so the first part of the question should be answered already. 2. The usefulness of local transmission events is fully explained in the current text (see line 26, page 35). 3. It is never the intention nor a design objective of link transmission events to replace any upper layer end-to-end transmission status information. 4. Upper layer end-to-end transmission status indication can not serve the same purBdpose as the link transmission events, as explained clearly in the current text (line 22, page 35). RmRejectedvh Refer to contribution 21-06-0708-00-0000_Link_Trans_Event_explanation for explanation. Keep this event.wRejected{a) awaiting resolution 2006/09/21EAjayFRajkumarGMember^Technical, Binding_35`36a6.1.3bOClarify the context of a system here or delete "or a system" from the sentence.c-The meaning of ".... or a system" is unclear.d263ear.d263hb855W8802-11pW9RWTWUWVWWWܒW,WݘW.WWWWa W"W#W*W?WAWDWGWLWOWTWUWVWWWZWiWlWpWsWvWxWېWەWۖWۚWۜW۝WۢW۪W۰W۳W۶WW#W,W5WHWRWSWTWUWVWWWYW^W`WiWjWkWmWyWzW{W|W~W܃W܄WܕWܚWܟWܡWܤWܫWܬWܰWܵWܾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWclose٪WcoٿWcode٘WWWWcodesٝWcoincide٪Wcollecting;Wcollectively@WcolumnكWٴWٵWٶWWcombinationWWcompletedCWcrepeatW+WrepeatingxWrepeatspWvWrepetitive7Wrepetitivesentences7VrephrasingۘWWreplace۩WܥWWݭWW=WvWwWxWyWWWreplacealloccurencesofmihinthedraftbymihfthedraftܥVreplaceapplicationwithapplicationݭVreplacebytesbyoctetsVreplacefig4bythesubmittedcontributionVreplacefigure5withabetterdescriptionofthemihfuncti=Vreplacewithupdatedtextforsection5.5listingallthe4vVreplacewithupdatedtextforsection5.5.1listingallthewVxVreplacewithupdatedtextforsection5.5.3listingalltheyVyVyV V V V V V V V V V V V ViWmWܕWܗWrequestsetsWmWrequireWrequired"WW)Wrequirements۟WrequiresWrequiringWOWreserve"Wreserved}WresideWܩWresidesܟWܩWresiding:Wt9cspecifies{WnWWWspecifiyWspecifyWaWWWWoWtWWspeculativeAWspellingTjmpspiritWWWWsposWsquareWfWssid[Wsta/ue-WiWstack۪W/W7WW%W=WsWWstacksWWWWstaion'sއWstandardەW۟W۩W'WܖWܛWܣWܭWWWWW>WNWWWWW W!W3WpWtWWstandardizekWstandardizedkWkWkWkWkWkW dÃ) AÃ)0ۼÃ)@Ã)P#Ã)`uÃ)pÃ)݃Ã)=Ã)Ã*wÃ* xÃ*0yÃ*@2Ã*PÃ*`۽Ã*pÃ*$Ã*Ã*&Ã1YÃ1 %Ã10 Ã1@Ã1PۿÃ1`EÃ1pÃ1Ã1 Ã1*y8banalyzetWݸWanalyzing'Wanchor>Wchor݊W݊Wous(WanalyzetWݸWanalyzing'Wanchor݊W݊W'W'W'W'W'WW.W/W0W5W6W7W8W9W>WAWDWEWNWOWPWTWUWVWWWZW\W]W_W`WbWeWfWkWlWnWpWqWsWuWvWwWxWyWzW{W}WWۉWېWۘWۣW۬W۳W۶W۸W۾WWWWWWWWWWWWW#W)W+W,W4W5W7W:W;W<WAWBWRWVWXW\W`WgWhWnWsWtWzW{WܕWܟWܡWܤWܨWܪWܬWܴWܸWܺWܾWܿWWWWWWWWWWWWWWW WWWWW&W'W)W2W:WCWUWWWYWfWoWyWzW݂W݃W݊WݎWݕWݖWݗWݴWVXjaccessWܾWWaccording@Wacross"WWactually"WaddressݍWaddressesWadpotYWagree"Wagreed|WWW WWagreedformihfsessionidsVagreedfragmentationishandledbytransportprotocols VagreedtodescribethereasonfornotbeinggloballyuniqueVV:cfig/tableifapplicableVVfig/tableifapplicabletable20/table21VfigurewW۪W۴WW7WܑWܒWܓWܔWܵWWWWWKWWW WBWvW2WYWZWWWWWWWWW!W7W=WjWpWqWrW}W~WWWWWWWWWWWWWfigure11hasbeenintroducedwithoutanytextandpurposeVfigure15isincompletelocaleventsarenotshownproperlyVfigure15wouldbenefitfrommoreexplanatorymaterialhighlVfigure18isincompletelocalcommandsarenotwhownVfigure23onpage111istitledcommonmihfframeformataltVfigure23representsanmihframeusing802.3/ethernetotherqVfigure24dealswithhowthemihwilltransportmihmessagerVfigure24doesnotrelatetothesection8.3weputittoshVVVVVVtothesection8.3weputittoshScby+WLWOWPWQWRWSWTWUWVWWWcWdWۄWۅWۋWېWW/W:WCWDWEWHWRWYWZWzW{WܟWܡWܥWܬWܾWWWW0WWWWW WWWW W#W%W>WOWޏWޖW\W]W^W_W`WaWbWcWdWeWkWnWtWvW|WWWWWWWWWWWWWW WWWlWtWzW|W}WWWWWWWWWWWWWWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrW{awaiting$W@WAWCWKWpWsWvWۼWWWNW[WܵWWWWIWRWaW@WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#WWWWܵWWLW}W,W>W@W2WdoneWWW W"W(W)W*W+WەWۖWۗWۘWۙWۚWۛWۜW۝W۞W۟W۠WۡWۣWۤWۥWۦWۧWۨW۩W۪W۫WۭWۮWۯW۰W۱W۲W۳W۶W۹WۻWۿWWWWWWWWW WWWWWWWWWW,W.W/W0W1W2W3W4W5W6W7W8W:WܛWܟWܠWܡWܣWܤWܧWܨWܫWܬWܭWܱWWWWW0_‚(ۮۯ۰˃456‚)۱۲۳789Xঃਃ<‚*۴!‚1"ܫ‚2۶6̓<ݍݎ"‚3#$۹ۺۻܬܭ=>?@ݐۃ-.੃?v‚4ۼ΃A#u‚5݃ృ=‚6w‚7xy‚8۽2$‚9ۿE Y%&‚:σG ////////////////////////////Ճ‚TKȃɃʃ˃ܶ׃؃‚UZ[ےۓ̃̓΃ <=>?@Aܷڃۃ‚VۑσЃ!"B݃‚W߃‚XX\у҃#$CDEܸܹܻܺ‚YYF‚Z]^%&Gܗܼ‚a'H‚bӃ(‚c‚dԃ‚e_`)Iܾܽ‚fa*‚gbՃփJKLܿ‚i׃MrbdeletethefollowingtextvVxVzVdeletethesentenceVVdeletethisdefinitionVdeletethistypeoraddanewdefinitionVdeletedWW-W:WWdelineationWdeliverNWqW"W$WtWdeliveredW"W$WWdeliversoWtWdeliverywWkWWdemandW}WdemonHWdependantWdependencemedia)WdependencyWdependentDWpWWWW2W2W2WWW2W2WendentDWpWWWW2W2WDWpWWWW2W2WWWWWWWWWWWWWWWscribingW5WܟWdescribingroamingaspectsonin5.3.2beforethetermsareVdescription?WpWtWۂWېW=WNWRWSWTWUWVWWWXWYW\WcWkWmW܄W܅WܲWܶWܷWWdescriptiveWdescriptonܹWdescriptorW+crejectedۄWrelatetWuWWrelatedۓW:W"W#W$W%W>W1WtWuWWW<WWrelationshipDWW,WWWWrelationshipbetweentable6andsection6.3.4.1isunclearVrelationship/mapping[WW'W'W'WVVVVVVVVVWOWܖWܫWWWremoveۙW۱W۷WWWWWܱWWremoveapparentlimitationsVremoveimplicationthataccessisremotesinceinformationm۷VremoveimpliedlimitationbetterexplainuseVremovelimitationsVremoveredundancyۙVremovereferencestoasn1VremovedAWsW۝WWWrenameۭWWrenamethemessagefromtheremotemihftolocalmihfaseveVrenamethenon-posmihentitytomihnon-posforconsistencyۭVreorderWreorderthetable4andtable5tobeconsistentwithorderiV | + 'btheWWWW#W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"WÃYnÃY 2ÃY0CÃY@DÃYPÃY`ÃYpCÃYÃYNÃYPÃZݛÃZ lÃZ0ÃZ@ÃZPÃZ`\ÃZpfÃZÃZÃZSÃakÃa Ãa0RÃa@LÃaPQÃa`TÃapIÃaUÃaÃaVÃbWÃb Ãb0Ãb@aÃbPÃb`ÃbpÃb_ÃbYÃbÃclÃc ZÃc0Ãc@nÃcPbÃc`GÃcpÃcݜÃc[ÃcÃdTÃfUÃgVÃg@WÃg`cÃgpdÃgeÃgÃgۍÃhaÃh fÃh0ېÃh@ÃhPÃhÃhÃi[Ãi Ãi@ÃiPÃipÃiLÃiMÃjÃj0IÃj@5ÃjPÃjkÃjÃq݇Ãq Ãq0یÃq@ÃqPÃq`ÃqfÃrcÃr ݈Ãr@ÃrPgÃr`ۃÃrphÃrdÃriÃsÃs jÃs@h ۄcAIn current draft D01, MIH_Configure.request primitive has a ConfigurationRequestsSets parameter, this means that it can configure a set of parameters at one time. But the ResultCode of the corresponding MIH_Configure.response primitive is a enumerate type: Success, Failure, Rejected. Obviously, the ResultCode return only one value, so it cannot reflect the configuration result of each link parameter which is contained in ConfigurationRequestsSets and is to be configured by the MIH_ConfigurBe.request command.d627g2216wAccepted{k) done 2006/09/21 2006/04/24ۅEYuanFLiuGObserver^Technical, Binding_75`41a7.3.11b]See the proposal 21-06-0631-00-0000-Proposal_for_Amendment_of_Link_Going_Down.ppt for detailsc detailscribed in 21-06-0628-00-0000-Amendment about OldLinkAction parameter.doc.c ) ---------------------------------------------------------------------------------------------------------W*9bofsparqlqueryresultwhenthistlvisހVނVltwhenthistlvisހVނVނVnetworkaddressinformationfromtable14'Vremovemihnetworkaddressinformationfromtable19)Vremovesection7.4.14(Vremovetheentiresection8.5.3.11and8.5.3.12"Vremovetheentiresection8.5.3.13and8.5.3.14#Vremovetheentiresection8.5.3.15and8.5.3.16$Vremovetheentiresection8.5.3.17and8.5.3.18%Vremoveunnecessary/misplacestatementasfollows VremovedW W WrenumberWrepresentedWrequiredWWreserveWresourcesWrespectiveWretrieveWsWWsapWWsapsWscenariosWschemaWscope WWsectionWW WWWWW W"W#W$W%W(WsecurityWselection WserWserviceWWservicesWshallW WWWsingleWsome WWbiiYWuWillustratedWillustrates Willustration WXWimihfWimmediatelyeWېWWimmidiately2WimminentVWRWWimpending|WimplementWimplementationAWWWimplementationsAWimplicitlyPWW%WimplementationsAWimplicitlyPWPWPWPWPWWWWWWWWWWWWWWuWvWxWWۃWۄWۇWېWۓWۜW۞WۧW۫W۰W۶WWWWWWWWWWWWWWWWW#W%W&W,W2W3W5W7W:W=W>W?WAWBWDWEWGWHWNWPWSWTWUWVWWWXWYW\W]W_W`WcWnWqWyWzW{W~W܁W܂WܑWܔWܕWܗWܘWܙWܚWܟWܤWܥWܧWܩWܪWܬWܴWܶWܷWܹWܼWܽWWWWWWv bbjcc @bB|cA  2#@bb#@kbk#b#bcAk#bbbI supercededJHtechnicalbinding‰JI superceded‰KtechnicalbindingL*P‰L supercededMKtechnicalbinding‰ML superceded‰NtechnicalbindingO%@‰OrejectedPNtechnicalbinding‰P Orejected‰QtechnicalbindingR‰RrejectedSQtechnicalbinding‰S Rrejected‰TtechnicalbindingU‰UrejectedVTtechnicalbinding‰V Urejected‰WtechnicalbindingX‰X supercededYWtechnicalbinding‰YX superceded‰Ztechnicalbinding[‰[ superceded\Ztechnicalbinding‰\[ superceded‰]technicalbinding^0‰^ superceded_0 ܀bAHReplace "status of hnadover request." with "status of handover request."H@Af 33  33 336  33> 33fcA-Syntax error in "status of hnadover request."-@A> 33  33# 33>d801g2317{k) done 2006/09/21܁ENada, Golmie, Member^ Editorial_127`1a8.4.2.21bDepending on wether the response queries has only one or multiple parameters, adjust the section name or the parameter name in Table 21cDThe name of the section does not match the name defined in table 21.d807g2318p&use "Link Status Parameters Response" {k) done 2006/09/21܂ENada, Golmie, Member^Technical, Binding_122`15b|Change name to Link Configure Parameter Value as defined in section 8.5.3.5. Section 8.4.2.22 would also need to be changed.e changed.e changed.Editorial_126`15bMember^ Editorial_126`15bHcproxyiW,WއWpsdn/fa-WiWpsdxa-WiWpsychological<WpureWpurposeWWWWput>WWWqos:WܾW0WWWWWtWWqualityJW<WquantityWqueries|WNWtWuWWWWquery"WiWlWQW|W~WWWWWWW|WWWquery/responseWqueryingWqueryresourcelist܎WquestionWW WkWkWWWWWquestionableۀWquickly'WquiteWWquotesWWWquoting:Wr1۴WWr1andr3inetrafceseemtobeinterfacesbetweenmnandnet۴Vr2Wr3۴WWr4ܪWWr5ܪWradioۂW۽WWWW+WradiusۓW=Wradius-nas-port-type^Wradius-nas-port-typeisunsuitableforourusesinceitdoes^VraexWފWran۽WrandomlyWrangeWWhWWoWWrank ZjmakesށWmanagement"W,Wmany,Wmatter,Wmay"WWWzWWWWmaybegWWmaybeweneedtoclarifythesectioninsteadofremovinggVVmeanWmeantWmechanismWmechanismsWmediaWmemoryWmgmtWmih,WWW{WWWWWmihfWWWWWmiminumzWminimumzWmis-classifiedWmobility"W?W,WWmodifyWmootjWmoreށWjW=WmostWWmultiple,WWmultiplexWmustܾWWWWWWWWWWWWTWWmultiplexWmustܾWTWTWTWTWTWTWWTWTWwdiagramandtextprovidedin21-06-0612-01-0000-rnetworVnms+WnoܶWnotaW+WW W,W1W3W>WTWnowWnumber݄Wof۬WW+WWW W,W>WonWW W>WKWone+4cremotemihfreturnsthenecessaryinformationviaappropriatVremoveۙW۱WWWWܱWWPWWWWWWW*WWWzWremoveapparentlimitationsVremoveimplicationthataccessisremotesinceinformationmVremoveimpliedlimitationbetterexplainuseVremovelimitationsVremovelimitationsremoveimplicationofcapabilityuniquetPVremoveredundancyۙVremovereferencestoasn1VremovesfromnotifiesinthefollowingsentencethemihmigVCFcgoal#WWWgoesWWWWWWWEWFWGWHWgoingۅWW\WaW#WdWgong܈WgoodۓW'WWgov/nost/wwwclassic>WgprsWgrammarۺW)WgranularityWgre-WWgreatjWkWmWnWoWzW{W|W}W~WہWWgreaterXWWgroupWHWYWIWgroupsWWgsfc>WgsmPWgsm/gprsFWGWHWIWJWWWWWWWWWWW3W4W5W6W7WdWeWfWgWhWߢWߣWߤWߥWߦWWWWWWguaranteeWguidance}WguidelineWgveܬWhWh-aaa:W݌Wh-aaaisnotdefinedintheabbreviationlist݌Vha-W:WWhadnover1Whand-WWhandleWnWWWhandledWWܛWWWhandlesWhandlingW WhandoffWܜWJWT?bchangeotherieeegroupstosomeieeestandards?Vchangep90line46fromthisprimitiveisissuedbyupperstkV" 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 4f) ZcAIt is important to clarify which entities will generate the primitives for the MIH_LINK_SAP. In this case it says "is generated by an upper layer entity". Does it mean that other sources (i.e protocols) may call the threshold configuration for the same link? If this is the case, it could cause unwanted behavior where a protocol configured a threshold but will not receive notification because another entity changed the thresholds.d521g2279wAccepted{k) done 2006/09/21[ENada, Golmie, Member^Technical (was Editorial)_73`55bMRemove "(SSID+BSSID) serves as unique network identifier for 802.11 networks"cThe SSID+BSSID is only valid for 802.11 networks. The document should either define the link identifiers for all technologies or none.d528g2280{a) awaiting resolution 2006/09/21]ENada, Golmie, Member^Technical (was Editorial)_76`13b76`13b76`13b must define how to transmit the set of Event IDs. d510g22760WlQcthereisnoneedtodefinenewtermshorizontalhandoverand?V@Vthereisnoreferencetotheidentifiersdefinedby802.21DVEVthereisnospecificationfortherepresentationofthelistVthereisnotextfollowingtheheadingforsection5.6.12Vthereisnotextunderfigure5onpage24andfigure11onVthereisvaguenessinhowgeographicareaisdefinedconside'Vtherewillbenodirectcommunicationbetweenthephyandma VthereafterWthereafterthesepacketsmaybeencapsulatedinal2mihproVthereby WWaybeencapsulatedinal2mihproVVafterthesepacketsmaybeencapsulatedinal2mihproVVafterthesepacketsmaybeencapsulatedinal2mihproVVafterthesepacketsmaybeencapsulatedinal2mihproVV V V V V V V V V V V VWWWWWWW%W&W'W)W-W/W:W;W=W@Wcnew?W@WێW#WgWݍW W"W$W%WdW?WtWvWWWWW WW<W|WWWWWWWWWWWWWWWWW W>W?WDWEWMW\WcWjWܐWܓWܖWܘWܙWܚWWWnoieforperformanceofaccessnetworkshasbeendefinedVVnomentionaboutwhetherhigherlayerammendmentsarerequirVnoproperexampleisgivenfortlvreques/responseܙVnospaceforexpansionofmihtlvencodingsVnodeWWۉWۏWۦW W.W3W4WܝWܡWnodesW:Wnon-posۭWWnone[WnorۇWnormalWnormativeܪWnormativelyܪWnotW!W#W%W&W(W)W*W:W;W<W=W>WBWDWEWKWLWMWOWPWQWRWSWTWUWVWWWXW[W^W_WaWcWdWeWfWiWjWVgcmihf"WwW۪WWCWoW|WܑWܔWܥWWWWW0WݸWWW"W$W*WYW2WWWWWWWWWW WWW W}WWWWWWWWWWmihfheaderformatishaving8bytesinfixedheaderpartseܑVmihf-idsWmihf-idscouldbeconflictedbetweencommunicatingnodesVmihfid/sidWWVmiih2Wmiis#W_W`WbWiWjWkWlWmWnWoWzW۳WWWWIWܻW_W`WuW݂WWmiisisnotdefininganinformationrepositoryVmiisprovidestheabilitytoaccessthisinformationaboutaVmime|W~WminimizeWminimumWminutesWmip-WWJWWmipv4Wmis-correlationWmisleadingWW=W@WfWWmisleadinguseofsquarebracketswhicharecustomarilyusedVfVmismatchW\EBenjaminFKohGMember^Technical, Binding_83`19a 7.4.1.1.2b0Replace with " valid local or remote identifier"cThe "Valid Range" for Destination Identifier is given to be (MIH_LOCAL, MIH_REMOTE). This creates confusion as these two are not the valid values for the field. The same problem occurs throughout section 7.4 d578g2217v%"Replace with "Valid MIHF identifier"wAccepted-Modified{k) done 2006/09/21 2006/04/26݃EEric FNJEDJOUGMember^Technical, Binding_24a5.5bAKHide L2 sublayers (they are shown in details in each specific L2's MIH reference model) Show only one arrow that will represent ES/CS/IS together (all MIH signaling) Show only two kind of arrows: Local Interaction and Transport : only 2 colors instead of 3 different colors... -> Replace by 21-06-0612-03-0000-Reference_Network.pptKtK4/26݃EEric FNJEDJOUGMember^Technical, Binding_24a5.5bBenjaminFKohGMember^Technical, Binding_42`7a6.3 B1} breplacethedefinitionofhorizontalandverticalhandovers:Vreplacethedescriptionwiththismessagereturnsthestatus܄VreplacethefirstsentencewithVreplacetheformatofthelengthfieldshallbeperthedefiivVreplacethelistofeventsthatmaycarriedinamessageyVreplacethelistofeventsthatmaycarriedinamessageeaczV{Vreplacethemihgetinforesponseline20withmihgetinfo=Vreplacethenumberofparametersthatmayincludedinalist~VreplacetheremainingoctesieexcludingthefirstoctetofwVreplacetheueisknowntothenetworkbutnottransportcha܋Vreplacethewiththat VreplacethisbytheܣVreplacethisisusedtorespondtheresultwiththisisused܆V܋Vreplacethewiththat VreplacethisbytheܣVܣVa^VreportTW_WWreportedQWreportsAW_WrepositoryWrepresentationAW=W] Xܚb@A> 335  33>e Valid Range from N/A to - 0: success - 1: failure - 2: rejectedF@string which encodes an Information Element TLVs that carry Requests responses as defined in Section "Information Request and Response".@A  33j  m 33  33   33  33c- Though it has been agreed in the last meeting, the TLVs sent within response is still restricted to on element. This is inconsistent with the request. - These TLVs carries responses and not requests.d670g2265wAccepted 2006/08/11 2006.03.05  ܖEWolfgangFGroetingGMember^Technical, Binding_107`53a 7.4.15.2.2bAFChange Valid Range from N/A to - 0: success - 1: failure - 2: rejectedF@ 28d756g2264 2006/05/14 2006.03.05F27rialLccthedefinitionoftheparameterforsupportedisqueryismissVthedefinitionsgivenforthemihhandoverxxxprimitivesinVefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofisquerytypelistisnotcorrectVthedescriptionofthemesageisthesameastherequest܅VthedescriptionoftypeielistofoperatorsismisleadingiVthedescriptionsofitems3and4areidenticaltheprimitivNVthediagramimpliesthatanynon-l2transportwillrundirec Vthedifferencesbetweencoreheaderspecificiesandcore80$Vthediscoveryofmihfunctionentitiesatl3isoutsidetheVthedocumentprovidesnoalgorithmsforrttestimationtherVthedocumentspecifiesthatanupperlayermayconfiguretheVtheeffectofreceiptisnotcoherentbecauseitmentionsthoVtheexampleinbracketsinconfusingegbsorrncorggsniVT candzWzWzWzWzWzW  8    33       33  #    om different media types and assemble a consolidated view to facilitate its inter- media handover decision.A@A 33:  33F 33  33 33  33! 33cA Typically, in a heterogeneous network composed of multiple media types, it is the handover decision module or higher layer mobility management will collect information from different media types and assemble a consolidated view to facilitate its inter- media handover decision.d99g3227 2006/05/14ܥEVivekFGuptaGMember^ Editorial_15`21a5.2b#Replace MIH by MIHF in entire draftablish network-layer connectivitytablish network-layer connectivity"$bremovethefirstsentenceIVremovethefollowinglinesܬVremovethefollowingsentencefromthedefinitionthemobile3VremovethemobilenodemaymoveacrossdifferentaccessnetwQVremovetheparagraphassociatedwithitem1animplementatioVremovethereferencestoasn1Vremovethesecondhandovercomplete܉VremovethesecondsapۤVremovethesentenceVremovethesentencethisincludesthelistofnetworkoperatVremovethesystemmanagementanddefinethecapabilitydiscoVentenceVVthesecondsapۤVremovethesentenceVVthesecondsapۤVremovethesentenceVV܉VremovethesecondsapۤVremovethesentenceVVۤVdsapۤVۤV܉VVimplementatio%Vremovethereferencestoasn1VV%V%V%V%V%V%V%V%V%V%V%V%V%V%V%V%V%V%V%V%V%V%VVrepeatedWrephreaseW^bprovided"WAWpWWܟWWWWބW4WWprovidedsWprovider's۳WprovidesAWpW0WW4W5W8WtW|WWWWWprovidingWprovision5WܟWprovisionedWprovisioning۳Wproximity3WproxylW,Wpure>WpurelyWpurposexW Wput2WWWWputcontentsofsection6.3.8toannexcVVVVVVVVVVVVVVVVVVVVhsFVGVre-definethelinkqualityparametertypeencodingtableasJVre-organize_WbWre-verificationWWreasonWreceiptېWreceive-WLWuWېWreceivedHWIWVWreceptionWWrecipienteWfWlWېWredefinebWredrawing۽WreevaluateRWreference$W۬W۴WreferencedۑWrefersۖWWreformatWregardingTWregime۶W‚c9n#bmRemove MIH_Command.confirm as with or w/o it the MIH_Command.response is the real confirmation to the requestctThe MIH_Command.confirm is adding no value. Same can be done with a timer. The key is the remote MIH_Command.responed296g2248pshould be technicalv2The .confirm acts as a response in the local case.wRejected{a) awaiting resolution 2006/09/21 2006/04/28dhernet". d687g2302vIremove figure entirely and enhance this section for other L2's we supportyAssigned as issue number 30 2006/08/14#EPeretzFFeder_40`48a Figure 18bmRemove MIH_Command.confirm as with or w/o it the MIH_Command.response is the real confirmation to the requestctThe MIH_Command.confirm is adding no value. Same can be done with a timer. The key is the remote MIH_Command.responed296g2248 2006/08/14 2006/04/28poned296g2248 2006/08/14 2006/04/28a`TÃapIÃaUÃaVÃbWÃb Ãb0Ãb@aÃbpÃb_ÃbYz} bAFor the first comment: "The MIH might also notify the local MIH User." For the second comment: "This is illustrated by the dotted arrow." For the third comment: "(which previously registered for the ...)" For the fourth comment: Have to be consistent, either use "MIH User" or "MIH user" For the fifth comment: "... could have been previously obtained or it could be readily..."cARemove "s" from "notifies" in the following sentence: "The MIH might also notifies the local MIH User." Also on line 6, replace "with" by "by" in the sentence "This is illustrated with the dotted arrow." Also on line 8: replace "register" with "registered" in the following sentence: "(which previously register for the ....)" Also, their is inconsistency with the use of "MIH User" and "MIH user". See lines 5, 6 and others on that page. On line 12 of the same page: replace "of" witument bremoveܛWܬWܱWWWW$W(W)W*W8W@WGWNWQW^WfWwWWW:WNW_dnWކWކWކWކWކWކWކWކW7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙW} cAa) Add an "s" to "toward" on line 20 b) Add an "s" to "relay" on line 24 c) Correct the word "towars" on line 25 d) Reword line 40: "Mobil IP registration might be now trigger." e) Reword line 43: "....using an MIH complete request. side" f) Add a "d" to "use" on line 44: "A Link Tear Down is use to release resources." g) Add a "d" to "issue" on line 45: "....A Link Tear Down response is issue ..." h) Add a "d" to "issue" on line 46 i) Add a "d" to "issue" on line 47 j) Add a "d" to "B[issue" on line 49 k) Add an "s" to "toward" on line 49 l) Add an "s" to "toward" on line 50Id879g2240{k) done 2006/09/21 E Ulises Olvera^ Editorial_22`46a5.4.3b?"Other IEEE groups define similar means and support clients..."c|Remove "s" from the word "supports" in the line that quotes "Other IEEE groups define similar means and supports clients..."d173g2243{k) done 2006/09/212006/08/29 E Ulises Olvera^ Editorial_32`31a5.8.2a33r ݔbAChange Representation field to: " For example, RADIUS NAS-Port-Type attribute value which is a unique identifier defined in http://www.iana.org/ assignments/radius-types, e.g., i.e., "@A 33$  331 33  33 33  33c7The use of NAS-Port-Type should not be just an example.d350g2392wAccepted{k) done 2006/09/21 2006/04/28Marked6ݕE YoshihiroFOhbaGMember^Technical, Binding_45`19a6.3.2bAChange the Representation field from: " RADIUS Operator-Name attribute defied in draft-ietf-geoprivradius-lo- 05.txt. " to: " A combination of operator namespace and operator name. "@A> 33  33>c.Reference to Internet-Draft should be removed.d369g2393wAccepted{k) done 2006/08/29 2006/04/28Table 6 ݖE YoshihiroFOhbaRbremovemihusersareinthebeginning*VremovemoreNVremovenewpoaidentifierfVremovenumberofaddressheaderidentifiersXVthebeginning*VremovemoreNVNVhusersareinthebeginning*VremovemoreNVNVNVremovenewpoaidentifierV*VremovemoreNVremovenewpoaidentifierVVVVVVVVVVVVVesection8.5.3.17and8.5.3.189Vremoveunnecessary/misplacestatementasfollows VremovedWWWrenumberWrepresented#Wrequired"W#Wreserve"Wresources"Wrespective*Wretrieve.WsW'Wsap'W*Wsaps'Wscenarios#Wschema#Wscope W#WsectionWW!W'W1W2W3W4W6W7W8W9W<Wsecurity#Wselection Wser#Wservice#W*Wservices"WshallW W-W.Wsingle*Wsome W,WB$vthe.themihfunctionaggregatesdisparateinterfaceswithrespec@othese{thisۋܛethiswillbehandledseparatelyforalsuchiesandappropri@toatransportzupdatetable-8indraftd01.09@ .use۳various@wherever@with@!waccepted#accepted-modifiedrejected-duplicate@ ${aawaiting@b@donelA4-Ne@input@instructionshk@`Z9akdoneO74Z3ܕݺf lglnoneneeded@Gneeded€ 5@ P =,ZT &(€<€10@"5@#"5@# member˃̃̓Ѓуԃ؃كۃ܃ރ2܍ܑܒܓܔܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܕܔܔܔܔܔܔܔܔܔ܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍ܒܓܔܕܖܗܘܙܚܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܮܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&~ENada, Golmie, Member^ Editorial_123`61bAReplace "the number of parameters that may included in a list." with "the number of parameters that may be included in a list."@Af 33'  333 33d  33t 33fcAGSyntax error in "the number of parameters that may included in a list."G@A> 33/  33< 33>d795g2315{k) done 2006/09/21ENada, Golmie, Member^ Editorial_124`43bA2Replace "which sttaus may" with "which status may"2@Af 33  33 33'  33- 33fcA"Syntax error in "which sttaus may""@A> 33  33 33>d797g2316{k) done 2006/09/21܀ENada, Golmie, Member^ Editorial_126`15b126`15b126`15b~&qbentities W"WpWsW7WfWrW0W3W݈W/W|WWentitiesmake݈VWWWWWWWWWWWۚWۭW,WZWfWܡWW݊WW"W%W/W8W9W=WentriesܹWentryWkWݛWenumerated\WenvelopeWenvironment,WWܤWIWenvisonedJWequipmentWerrorFWGWHWIWJWۉW\WesbWpWes/cs/is݃WespeciallyUW1Wess?Wessential?WܽW'WessentiallyWessentiallyanisclientcanaskforcertainclassesofVestablishܡWestablishedOWRW܋WޕWestablishingOWSW_WbWestimationW WetcAWHWIW_WۖWW=WYWܵWܷWWWW|WethernetsWWW=WqW^WethertypeWܯWetypWeuqivalentކWevaluateTWevaluatedTWevenW^WܼWWWo^technicalܖWܖWܕWܕWܕWܔWܔWܔWnWnWnWnWnWnWnWnWion" from Table 14.7@A  33cA)The inclusion of "MIH Network Address Information" primitive in 802.21 is not sufficiently justified. Both the requester and provider of "Network Address information" will be an upper layer entity, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33d307g2270 2006/05/14 2006/04/244;EQiaobingFXieGMember^Technical, Binding_66`53a7.2.2.1bA8Remove "MIH Network Address Information" from Table 14.ust transport something for the upper layer, which is improper.)@A  33d307g2270 2006/05/02 2006/04/244;EQiaobingFXieGMember^Technical, Binding_66`53a7.2.2.1bA8Remove "MIH Network Address Information" from Table 14.yvbtext#W$W?WAWGWIWLWOWPWQWRWSWTWUWVWWWcWdWeWfWiWlWpWqWsWvWxWWhWWWWWW{W}WWW,W2W4W5WIWނW[WlWmWnWoWtWwWxWyWzW|WWWWWWWWWWW W1W>WtWWWWWWWWWWWWW߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾WWW nݓvACommenters agree, applicable to ES and CS but only under certain scenarios. Comment this scenario also covers network to network MIH communication as well. Discussion that MIHF ID can't be known across an intermediary given the current definition of multi hop. and MIH sessions. Discussion about discovery of ES or CS PoS beyond first MIH PoS, consensus is the L3 proto will define this, but probably won't use this multi-hop model. For L2, we only support discovery through first L2 broadcB-ast domain. Discussion that in an implementation, an intermediate PoS will terminate the session from the MN and create a new session with another PoS, then act as intermediary when recieving transactions for that service/session from MN. We are not doing anything within the protocol to enable this.wAccepted{k) done 2006/09/21 2006/04/28doFOhbaGMemberr network. "d161g2412 2006/05/17 2006/04/28ݐE YoshihiroFOhbaGMembers.6AkcsapCWDWSWیWۤWZWܰWWW0WAWW4W5W8W2W>W?WYWZW[WkWWWWWW%WWWWWWWWsap'sWWsapsDWܰWWW8W[WWWjWvWwWxWyWWWWWsatelliteWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsayWWsaying/WWsaysWrW۾W%W&W.WZWWWyW݇WWWWޚWW W:WxW߶WWscanۆWWNWmWscanschedulingNWscares݃WscenarioWݓWWscenarios\WۈWWMbusedVWWWcWiWpWsWxWېW#WNWVWZWwW܅W܆WWWW%W4W5W8W>W}WހWނWބWޅWއWxWzWWWWWWWW|WWWWusedmimetypeapplication/xmlshallbeހVނVusefulWVނVނVނVނVނVނVނVWzWWWusers-WpW۵W7W܊W*W0WW7Wuses۝WTWUWVWWWXWcWusing_WuWxWۗWۜWWWHWTWUWVWWWXWcWWWutilised}Wutilize"WWWutmostgW&Wv-aaa:Wvalid\WۂWېWTWUWVWWWXWYW\WcWkWmWܖWW|WWvalidrangeۂWvalueJWXW_WfWjWmWzW{W}WۉWWWW*W=WFWHWwW|W܂WWXW[W~W݁WݔWݗWݘWݙWWW }bthefollowingfigureillustratesthecombinationofallthe VthefollowingsetofmihcommandsaredefinedV"VVthefollowingsetofmihcommandsaredefinedޔVޔVwingsetofmihcommandsaredefinedޔVޔVollowingsetofmihcommandsaredefinedޔVޔVGVGV network may be sufficient. In such cases information elements like intra-technology neighbor reports and other link layer information required during handovers is directly available from the accessB network. In such cases the availability of higher layer services offered by the network typically does not change appreciably across different network point of attachments. On the other hand during vertical handovers the mobile node may move across different access networks. In such cases there is a need to select appropriate PoA in the new network based on both optimum link layer connectivity as well as availability of appropriate higher layer services to permit service and session cont\ctheWW"W#W(W)W*W+WDWGWIWJWLWOWPWQWRWSWTWUWVWWWZW^W`WcWdWeWfWgWhWiWlWpWqWrWsWvWwWxWۀWۃWۄWۅWۋWیWېWەWۖW۟WۤWۦWۨW۪WۭW۽WWWWW W WWWWWWW#W$W,W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-WdthenomustbeupdatٵVٶVimplementationW1W٧WimprovedsentenceflowzV+].^technicalbindingܑVܒVܓVܔVܔV_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g2349 2006/05/14 2006/04/28ݤE YoshihiroFOhbaGMember^Technical, Binding_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g23498ݤE YoshihiroFOhbaGMember^Technical, Binding_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g23498ݤE YoshihiroFOhbaGMember^Technical, Binding_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g2349Identifer TLV.d561g2349W]w]cis܎WܑWܒWܓWܔWܕWܖWܛWܟWܡWܤWܫWܭWܱWܵWWWWWWWWWWWWWWWW W WWWW!W+WEWaWeWzW{W}WW݃W݆W݉W݌WݎWݐWݓWݗWݛWݸWݾWݿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰW@W GbBset | | |Examples: | | | | |{Generic:Link Speed}, | | | | |{Generic:Link Bit Error Rate}, | | | | |{Generic:Link Frame Loss Rate | | | | | before retransmission}, | | | | Cs |{Generic:Link Signal Strength}, | | | | |{GPRS:BLER}, | | | | |{GPRS:RxLevNCell} | | | |-------------------|--------------------------------|-----|-------------------------------| O@O_P`QaRbScTgUnVpWvXwYxZy[{\]^_B/cimprovement WAWZWsWWWWWWWWWWWWWWWWWWWWWWWaWbWhWqWuWvWwWۀWۂWۃWۄWۅWۆWۇWۈWۊWۋWیWېWۑWەWۤW۬W۳W۴W۾WWWWWWWWWWWWWWW WWWW-W.W1W2W3W5W6W7W8W:W<W=WGWHWIWKWLWPWRWYWZW\W^W_W`WaWfWiWlWoWpWrWtWuWvWwWxWyWzW{W}W~WW܀W܁W܃W܄W܆W܇W܈W܊W܋W܌WܑWܒWܓWܔWܕWܖWܗWܝWܟWܢWܤWܥWܧWܩWܬWܭWܯWܱWܴWܶWܷWܹWܺWܼWܾWWWWWWWWWWWWWWWWWWWcseegW۪WۯWܑW#WW|WWseeitemabove#VseepreviouscommentۯVseem۴W WWWWWseemsۦWWݛWWWW'WWWseennWseervice۶WsegamentationWsegaments'sWsegment۹WWNWWselectۋWselected|WWselectionۋWܡW-W WWselectorWselectsܡWsemanticallyCWWsemanticsۗWۛW WWWsemanticscorrectionۗVۛVsendeW"W$WWWsenderWWWsendingeWWsense(W)W۔WWWWWzWWWWWWWWWWWWWWsWۚWۥWۮWWW WW3W5WQWiWW6W9W@WMWWW^WxW݆WݐWWWWWWWWWWފWދWތWsentencesayingaspecificinformationrequest/responseprimVlabcrossTWWcrossedRWcrossesޖW5WcspWWWcurrencyHWcurrency/unitHWcurrentGWTWZWWW>WWWlWpWsWWWWWWcurrenttextinrepresentationshouldbemovedtothedescriVcurrenttextshouldmovetothedescriptioncolumnandaspeVVVVVVVVVVVVVVVVVVVVVkWmWnWrWsWzWWWWW#WYWqW|WܷWdataschemaisadoptedVdatabase۳W۶WWWWdayHWdbYWdealingۈWdecision W#W?WvWwWWfWܤWܴWdefiitevWdefineAWNWےW۔W۟WWWW+WAWBWYWhWsWܦWܬWdefineandmakedefinitionsinsection6.3.4.1.4and6.3.2cAVdefineandmakedefinitionsinsection6.3.4.2.1and6.3.2cBVleteoneofthemۦV_bbasisܾWWWbeWW W#WAWDWGWRWTWVWWWZWiWsW۫W۳W۶WWWWWWW#W3WCWRWTWUWVWWWYWZWhWvWwWyWzW{W~W܂WܕWܨWܬWܾWWWWWW7W=WIWOWzW}WݺWWWWWWWWWWW WW#W%W,W-W.W2W>WAWBWOW~WހWނWފWދWތWWW[WlWpWsWtWWWWWWWWWWWWWWWWWWWWWWWWWW W"W'W(W,W3W4W7W:W<W>WkWlWmWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW pand2WanotherۏW۽Wanswer{WanyWanymore)Wappendex۽WareW-WܰWWކWasېWۓW)WRWܰWܾW{WݛW1WatۖWWattributeۓWbased{WbeۓW:WWVWYW2W#WbeforeۓWbeing-WWކWbest&WbetterDWWWbit1Wbits)WbothWbothareusedaddedtheadditionaldefVbreakWݜWbullet݃Wbullets݃WbutgWۅWۓWWܥWWbutdidnotmakethechangestomihlinkgoingdownsomeoneۅVbutdidn'tchangenameofexistingmihconfiguretomihconfgVbutthisisinconflictwiththeacceptedcomment195pppisVVVeditorial;VcommetCWconflictWconsistentAWYWcontainerZWcontributionZWcontribution21-06-0711-00-0000-itlvretrievalnoexclusionZVcontribution21-06-0712-00-0000-itlvcontainerdoneZVcopyۓWcreateۓWzWYbconfigured@|consideration@contribution@cooperative@Ccopy@lcross@$currentlinkaction@database@defied@define@Ydefineitas0forversion1thisdraftothervaluesforfut@)defined@5defines@definitions@deletemiho@deletethefollowingtext@thefollowingtext@thefollowingtext@@@ttpwwwianaorg@ianaorg@wwianaorg@deletel2fromabovesentence@deletetheaninformationrepositorypart@deletethefirstsentenceofitema@depending@rdesignated@Zdetailed@fdetails@discover@discussion@done@eusingamihhandovercompleterequest@eitherexplaintheunlabeledtableorremoveit@encodes@enterprise@entities@entitiesmake@&eveniftheschemawereretrieveditwouldn'tassista@eventiddescription@examples@expansion@-@Wbtoorco-locatedwiththepoaVtoprovideclientofthenumberofnetworksinsteadofoperaVtothefollowingtextIVVtothefollowingtextIVIVIVersupportedisquerytypeismissingVthepoacapabilitybitmapisnotsophisticatedenoughtocap6Vthepresenceofthefahah-aaaandv-aaainthereferencemڄVtheprevioussub-sectionstalkaboutthemodificationsthatVtherelationshipormappingbetweenmihlinksapandmediad0Vtherepresentationofnumberpoaisnotspecified'VtheruleshereseemtoimplythatreceiverprocessingcouldTVtherulesonhandlingduplicatetransactionsarenotclearsVVtherulesstatethatinanycasethedestinationshallnotpUVthescanrequestsetsisnotdefinedthelistofscanrequestVthescanrequestsetsshouldidentifylinkietechnologytoْVthescopesectiondoesnotadequatelyaddresswhichpartsofHVVbvaluescWdW)WhWxWW8WVWފW6WnWvWWvaraibleWvaripWvariableۉWHWW'WtW~WހWނWWWWW8WvariablesWvarious?WpW"WWW[W9WvendorTWUWVWWWWWWvendorspecificiesVvendor/networkWverifyWversionVW~W1WWW;Wvertical?WAW:WWWvia#WܬW9WݎWWWvice#WvidedtW_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWweproposetoaddanienewmacaddresstotellthemihfoftaۇVweproposetospecifythewayfordealingwithmihcapabilitۈVwell WAWiWpWsW۶WWܷWܸWwereWwether܁WVFbanLWOWPWQWRWSWTWUWVWWWZWcWdWiWlWېWWW,W2WZWfW܅WܕW+WIW}WހWނWއWދWXWnWrWsWwWxWyWzW|WWWWWWWWWWWWWWWWW/WuWWWWWanexamplewouldbeaquerytoretrievealistofalleventsVanalogous(W(W(W(W(W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W~^technicalbinding"VDVGVIVJVLVOVPVQVRVSVTVUVVVWVZV^VcVdVeVfVgVhViVlVwVۀVۅVۓV۔V۳V۴V۶VVVVVVVVVVVVVV,V:V;VCVHVRVSVTVUVVVWVYVkV܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V܂V^technicalbindingVVVVV VV'V0V1VEVHVOVPVaVbV{V}VV݃VݍVݎVݒVݓVݔVݕVݖVݗVݘVݛVݜVݺVݾVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVa`GcanotheriWZWW"W'WnWtWuWWW~WWWanr:WanyOWPWQWRWSWTWUWVWWW۪W)WIWܫWW W WޖW>WkWoWWWW WWWWW<W?WoWWWWanythingWWWnythingWWngWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW)W7W:W=WNWRWcWjWtW܏WܖWܗWܚWܪWܭWܯWܲWܴWܹWܿWWarelinksynchronouseventsapplicableforl2handoversonlyܲVareaW=WIWareasWarticle۰Wo ;vtheWWWW"W*W-W/W4W5WNWOWVWdW\WqWwWxWWWWWWWWWWWWWWWWW WWWWW W"W#W%W4W=W>W?WUWVWjWoWtW|WWWWWWWWWWWWWWWWWWW#Wtheconfirmactsasaresponseinthelocalcase#VthedefinitionofschemaisnormativeanditisalreadyinaVtheentirelengthcolumnintable-6isbeingdroppedasperVthegroupfeelstheoriginaltextisbetterthanthesuggestVthelanguageistoostronginsomecasesmayneedtochange{Vthelineshavebeendeletedintextbycomment162VVUbtoc@towards@traversed@Itype@`typemimetlvvariableamimetypetlvanoctetstringfora@uk/currency/by@.under@updatefigure@upon@url@useofabitmapmodeltoencodethelistofeventsthatare@used@user@users@values@)video@what@Vwhere@/whichwifi@wireless@Swishes@Reless@S/whichwhy@wireless@SSforme@/whichwhy@wireless@Swhire@tisementmobnbr-adv@/whichwhire@8.5@802.21@s802.3@FaܼWabettertitlefor5.5wouldbemihreferencemodelforacce@abbreviation@achive@add@addacommaaftermobilitybecausewithoutacommathesente@addtheinthefollowinglineinthissectionareprovidedi@adopt@walgorithm@all@also@among@and@%W܂cThe name Link Configure Parameters Response is not appropriate for the parameter name. This parameter is just used to store a configuration value. d784g2319wAccepted{k) done 2006/09/21܃ENada, Golmie, Member^ Editorial_132`22bA@Replace "the a Link_Event_Rollback" with "a Link_Event_Rollback"@@A> 33   33 33>cA+Syntax error in "the a Link_Event_Rollback"+@A> 33  33 33>d835g2320{k) done 2006/09/21܄ENada, Golmie, Member^ Editorial_134`15bA>Replace the description with "This message returns the status of a configuration request" Name Type ConfigureRequestSet Link Configure Parameters Type (14) ConfigureStatus Status (245)>c>c>c_breferencesWܱWWW&W'WWW(W,WrWreferencingWreferred)WrefersۖWWWreflectWWreformatWregardingTW+Wregime۶W۶W۶W۶W۶W۶W۶W۶W۶W۶W۶Wcify .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 and BSubmit 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 coJncinWW6W@WEWHWLWzW{W}W݅W݋W݌WݐWݛWݽWWWWWWWWWWWWWWWWWWWWW WWWW W"W$W&W'W*W,W-W.W/W8W>W@WCWIWNWYWlWnWqWvWwW|WށWރWބWޅWކWއWވWފWދWތWގWޖW2W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WWWWWWWWWWWWWWWWWWWWWWWWWW})clistWWZWېWRWSWYWgWhWmWyWzW{W|W~WW݌W@WtWWsWWWWWWWWWWWlistedkWWWlistingW'WvWwWxWyWlistsWW W<Wlittle1WtWvWWW.W?WlocWlocalW7WܖWܫWWzWWWW>WWWWWWW2W7WWWWWlocal/mihWlocalizedWlocally"WWWWWWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWVmaintains۳Wmake(W)W۔W۰WWWmakeindefinitearticleformconsistent۰VmakesfWmaking*WۅWۆWܳWܴWmanagedWmanagement"WW+WܤWܴWmandatoryWWmanditorilyWmannerܢWmanualۂWGRc20܇WWtWuW20/tableW21ۦWPW܁WW21-05-xxxx-00-0000-qW21-06-0522-04-sessioݵW21-06-0524-01-0000-88W21-06-0601-00-0000nW21-06-0602-00-0000W21-06-0606-00-0000W21-06-0614-00W21-06-0xxx-00-0000-wW22ܬWހW23ݿWނWqWWW24wWEWݿWWWWrWW2461W25W256W26W28ܑWܒWܓWܔW29WW}WW2ndtWW3W۽WW)WNW}WݍW>W|WWWWWWWWW3.4W3.43.5and4.1donotstatewhatrepresentationshouldbeuV3.5W30WW33aW34W35W36W37W3753:W38W3gW3ggp2W3glink>W3glink-sapWWWWWWWWWWW&W'WHW W3gpp2documentnumbershouldbeusedۡV3gpp2hrpdshouldbesupported'V)bdefinedZWpWsW۫WGWHWYW`W܂WܕWTWݔWݘWWW.W4W5WކW6WsWtWWWWWWW(W,WmWWWWWdefinedinhttpwwwianaorgݔVdefinednotdefiedTVTVTVݔVdefinednotdefiedTVTVTVTVdefinedinhttpwwwianaorgݔVdefinednotdefiedTVTVTVTVTVTVdefinedinhttpwwwianaorgݔVdefinednotdefiedTVTVTVTVTVݔVdefinednotdefiedTVTVdefinedinhttpwwwianaorgݔVdefinednotdefiedTVTVVdefinednotdefiedTVTVwwwianaorgݔVdefinednotdefiedTVTVesAWpW۟W=WWW8WdefiningAWdefinitevWWݹWdefinitionW W#WJWZW]W۴W۶WWW W WWW/W3W4W:W`WcWܜWܝWܪWܬWWUWYWWޚWޞWޡWC(EQiaobingFXieGMember^Technical (was Editorial)_31`28a5.7bABChange to: 5.7 Media IndependenceMIH Protocol 5.7.1 MIH ProtocolB@Af 33  "  33. 330  fcQThe section title "Media Independence" is confusing and does not make much sense.d234g2250wAccepted{k) done 2006/09/21 2006/04/24 2006/04/24(EQiaobingFXieGMember^Technical (was Editorial)_31`28a5.7bABChange to: 5.7 Media IndependenceMIH Protocol 5.7.1 MIH ProtocolB@Af 33  "  33. 330  fcQThe section title "Media Independence" is confusing and does not make much sense.d234g2250wAccepted{k) done 2006/09/15 2006/04/242006/04/24)EQiaobingFXieGMember^ Editorial_31`60a5.8bA:Change to: 5.7 Media DependenceMedia Specific Amendments :@PcpresenceWW!WWpresenttWݸW'WW"WWpresentationwWxWyWzW{W~WWWWWW8WpresentedWpresentedastlvwithoutrequiringchangestoschemaeVpresentingpWpresumablyWpretty۽Wprettyconfusingpicturewithmihreferencemodelfor3gpp1۽VpreventWW۽V۽V۽V۽V۽V۽V۽VW W W W W W W W W W W W W W W W W W W W W WproposeۅWprotocoliW۪WWWprotocols۾WprovidedEW۾WWprovider:W;W<W=W>WprovidingۆWproxyiWqosWqualityJWqueries_WaWquery"WiWlW{W|W}W~Wquerying۸WquestionableۀWr1۴Wr1andr3inetrafceseemtobeinterfacesbetweenmnandnet۴Vr3۴WradioۂW۽WradiusۓWran۽WrangeWWoucwhat@ewhere@7whether@whichۄK whire@why@Bwill@Mwired@within@you@d‚1@‚Q@\‚@Ã) @Ã2@ÃA@ÃC /ÃT0ÃXp@Ãe@RÃhp@ÃvP$Ãp@ Ã`ݹvÃpސidasۓ,jinlee@qiaobingxie@ ronnykim@subir@wolfgang@jaccess@agreedtosetthelengthfieldto1@and@"asindicatedseveralitemsofthelistmustbeinterpretedi@between@Mclearly@contents@could@sdoes@facilitate@Ehowever@in@information@bis,link@makes@need@ one?Pparagraph@purpose@5related@Brelationships@renewal@repository@e@nce@~tlvs@=xml/rdf@xml/rdf-based@yes@Fike@necessary@on@td819g2410vAX "Although the subsequent subsections specifies TLVs to be carried in the MIHF Payload part of each MIH message, any MIH message generated by a primitive that has Source Identifier and Destination Identifier in its parameter carries MIHF ID TLVs for Source Identifier and Destination Identifier in the MIHF Variable Header part of the message."X@Af 33  33 33   33' 33fwAccepted-Modified{k) done 2006/09/21 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_134`31a8.5.2.8b0Replace Network Identifier with Link Identifier.c-Network Identifier should be Link Identifier.d840g2372wAccepted{k) done 2006/09/21 2006/04/28E Ulises OlveraGMember^ Editorial_84`44a7.4.4b*".....are described in the section below."on below."on below."le Header part is not mentioned anywhere in this section and its subsections. mvinsection7onlyhavedescriptionofevents/primitivesWVinsection8havespecificvaluesWVinsection8.6.1changemaytoshallasspecifiedinthecomOVinthejuneadhocmeetingasagreeduponbycommenterVincludeݜWWWW>W?WWincludetextfrom21-06-0755-01-0000-lVincluded)WincludeingSWindependentܰWWWW#WWindicateۋWWWindicatetransmissionstatusofapduVindicatedWindication۔WކWindicationsTWaWinfoWinformationZWlW۳WWܬWW"WWWWW"W?WinformativenWinitiateQWWinitiatedRW۫W>Winitiator۔WinsertەWWinsertbelowtextonpage37line30draftd01.00VinsertwithfollowingchangesەVinstanceW۴W1W#WintermediaryݓWintermediateݓWinteroperabilityܛWinterpretlWinto*WZWWWW(cthesentencehoweverthetarnsportandsecurityofthisinfoVthespecificationdoesnotdefinethestatemachineVthespecificationdoesnotuseasn1VthespecificationhasnotusedthetermnetworkselectorVthessidbssidisonlyvalidfor802.11networksthedocumen[Vthestandardshouldnotplacerequirementsonitself۟Vthestatementthesamenetworkentityisveryconfusing VthestatementthisprimitiveisgeneratedwhenmihcapabilitVthesub-sectionsdonotexplainordefineallthemediaspecjVthesupportforqosisimmatureinthep802.21standarddrafVthesyntaxandsemanticsofthetransactionidareextremelyVJVJVJVrepresentationcellisadescriptionnotasVthetextofthissectionmakesalotofhypothesishowinfor݂Vthetextsaysnonewprimitivesorprotocolsneedtobedefi۾Vthetextthisparameterspecifiesthelistofcommandsthat{Vacronymmihisinconsisten2V;v18۳WW186W187=W19@W195W$WW2ەWށWރW\WWWWW2handoverpolicyەV2onesparqlqueryparametersށV2onesparqlqueryresponseparametersރV2.2W2.3W2.4W20W200%W2000W2006\WW203W208W21-05-0671-00-0000-8WlW21-05-0696-01-0000RW21-06-0522-06-sessioݒW21-06-0598-04-0000-qW21-06-0611-00-0000-m}WW21-06-0633-01-0000-aW21-06-0637-02-0000-mW21-06-0637-02-0000-mcapabilitydiscoverypptV21-06-0641CW21-06-0641-01-0000-c>WW21-06-0642CW21-06-0642-02-0000-iBWW2W{W€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 icmicroWmiddleWmies WmightWWWWWWmigratedWmih$W+WCWDWLWOWPWQWRWSWTWUWVWWWcWdWfWgWiWlWۂWۂWۂWۂWWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWWہWWWہWہWuWzW{W|W}W}W|W}W}Wrected 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. _Yogesh`BhattaMemberb10c 4/24/2006d Editorial {1ۅvRemove: Packet_Timeout, No_Broadcast. Explain NO Resources better (Which resources?) LinkParameters Degrading (based on QoS parameters or link quality parameters)? wAccepted-Modified{k) done 2006/09/21 2006/04/12ۉE HongchengFZhuangGObserver^Technical, Non-binding_157`44a8.5.2bAadd LinkType IE to MIH_Configure_thresholds and MIH_Event_register, MIH_Event_Deregister primitives according to 21-06-0632-00-0000-LinkType_for_MIH_Configure_Threshold and Event.ppt. Name Type(1 octet) Length(1 octet) Value LinkType 31 Variable Identifier of link for which link was configured LinkParameter 33 2 Pramaeters for which link hich link nges to MIH_Link_Going_Down . Some one has to add such a section first. Degrading (based on QoS parameters or link quality parameters)? wAccepted-Modified 2006/08/07----D!Dd483g2280pY- done 21-06-0705-00-0000-Link-SAP-Mapping (in two separate table for better readability)v7as per contribution 21-06-0705-00-0000-Link-SAP-MappingwAccepted{k) done 2006/09/21 2006/04/24GEQiaobingFXieGMember^Technical, Binding_73`12a7.3.8.2bARe-define the "Link ParameterType" as a pair of {LinkTech : TechSpecificParameterType}. When LinkTech is "Generic" the parameter is then a generic link parameter. Examples - {GPRS : BLER}, {GPRS : RxLevNCell}. Change the current text to: |-------------------|--------------------------------|-----|-------------------------------| |Link ParameterType |A pair of {LinkType:ParamType}. |N/A |Parameters for which thresholds| | | | |may be |may be available higher layer services such as access to internet connectivity, availability of VPN services, etc. The set of different higher layer services provided by the MIIS may constantly evolve. At  w{donelWqWrWtWwWxWۀWۄWۅWۉWۋWۍWێWېWۓW۔WەWۖWۗWۘWۙWۚWۛWۜW۝W۞W۟W۠WۡWۣWۤWۥWۦWۧWۨW۩W۪W۫WۭWۮWۯW۰W۱W۲W۳W۴W۶W۹WۻW۽WۿWWWWWWWWWWWW, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33d34g2271 2006/05/01 2006/04/2414Ã?à @Ã0AÃ@BÃPCÃ`D dDT ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_BlbcooperativeۘWcooperativeuseofinformationavailableatthemobiletermiۘVcoordinatetWݸWWcopeWWcopied(W,WWWcificationoftypeienetworkqosisnotmediaindependenنVspecifiedWِWW$W'W1W4WڏWWspecifiesWWspecifiyWspecifyBWFWګWWWspeculative-Wspellingٜٔٗٛ١ڞڴڷںsquareٚWڰWssidWstack]WٮWWڎWWstaion's WstandardDWHWRW\WWct. *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. _Yogesh`BhattaMemberb12c 4/24/2006d EditorialctimeۄWWW:WWWWWWWWWtime-of-dayWtimeinterval]WtimelyWtimeoutWtimer&WޖWW{W#Wtimerandreleasethesavedcopyofthepacketthesourcema&VtitleW$W(W)WrWtW'WWWtitleneedstobeimprovedtVtitleofsection8.2.1isincorrectsincethetextsaysl3irVtitledWtitles/W0WtlvWAWBWܬWݜWݵW6WWWWWWWWW-WAWBWCWDWEWFWGWHWJWKWVWYW[W]W^W_W`WaWbWcWWWtlvforlinkidentifiershouldbedefinedYVYVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVݻVtothemobiledevicemntheonlyvisiblemihentityismihpVtocWWtooۢW۳W۵W۶Wtop۽WcdomainvWdonېWdon'tWWdoneOWWkW{WW#WdottedWWdownۅWۮW-W܈WaWbWW#WdWWWWWiWmWmWWdWdWdWdWdW{W}W~W݂W݃WdriveriWdropWdue:Wduplicate4W܉W܍W W Wduplicatedefinitionofmobilenode4Vduplicateentryhandovercomplete܉Vduplicatenumber10܍VduplicatedیWWduplicationwWduplicationofthemobilenodedefinitionwVdurationWduring|WdynamicWWݏWdynamicallyWe#W_WaWiWۈW۪WWWWWWZWwWWWWWWWWWWWWW0WBWCW\WWerewordline43usinganmihcompleterequestsideVe-core۽We-utra۽WeachuWۄWW@WCWzW{WܸW:W~WearlierpWvWxWearlyܫWjyouݍWvWWvWvWvWvW3Wandreqyoshihiro'sWWyouWݍW1W3W3W3W3Ws cannot have Destination identifier as local or remote since there is no information available to MIH users about mih peers.d575g2249 2006/05/14 2006/04/26h no MIh capability in the network since it could be provided deep in the network.d547g2248 2006/05/14 2006/04/26gESrinivasF Sreemanthula^Technical, Binding_83`1a 7.4.1.1.2b*remove destination identifier parameter. call mih primitives cannot have Destination identifier as local or remote since there is no information available to MIH users about mih peers.d575g2249 2006/05/14 2006/04/26hstination identifier parameter. call mih primitives cannot have Destination identifier as local or remote since there is no information available to MIH users about mih peers.d575g2249 2006/05/14 2006/04/26hc9binformativeWnWWWWWWinformed#WinformsHWinfrastructureۘWinfroquerytypeބWinitiateQWۋWݍW\WaWWWWinitiateactionthreshۉWۉWWۉWۉWۉWۉWۉWۉWۉWۉWLWW)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)W)WionthreshۉWinitiated,WRWܴWުWWWWJWpW߈W߮WWWWinitiates#Winitiation܅WinlcudesWinputܽWinsecure<WinsertWWWWWgW(WMWOWݿWinsertatendofsentencealthougnetworkconfigurationchanOVinsertatendofsentenceonlywhenprobabilityofaccessingVinsertbeforeorbyassociatinginformationcontainedinitsVinsertcommaafterfirstappearanceofnetworkMVWbperformanceWݍWWsWperformancematrixofothernetworkelementsaretypicallyrsVperformed?WWperformingAWperiodVWޒWperiodicWpermissiblenWpermitAWpersistentWpersonallyWpersonallyithinkit'soktohaveanxmlschemabutitVperspectiveWpertinent|WphasedWphrase6Wphy WpWWphysicalpWpicture۽Wcture۽W۽WWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpW*W?W۬WWܨWܪWܯWWpolicyOWPWvWەW#WܡWW݊WݎWportsWportedAWposW,WW2W9W\WpositionTWUWVWWWXWcWpossibilitiesWpossibility۳WpossiblewW۸WWYW=WoWpossiblyܡWW)W݂WpotentialOWPWsW% ^bindingWWWWEditorial_36`30a6.1.4bChange sentence to "the selection of the transport mechanism is dependent on the access technology that connects the MN to the network and the location of the MIH PoS".clText does not reflect the dependency of the transport mechanism on the location of the MIHF in the network. d235g2233 2006/05/14 2006/04/28EEleanorFHepworthGMember^ Editorial_36`30a6.1.4 dependent on the access technology that connects the MN to the network and the location of the MIH PoS".clText does not reflect the dependency of the transport mechanism on the location of the MIHF in the network. d235g2233 2006/05/14 2006/04/28EEleanorFHepworthGMember^ Editorial_36`30a6.1.4xt does not reflect the dependency of the transport mechanism on the location of the MIHF in the network. d235g2233 2006/05/14 2006/04/28EEleanorFHepworthGMember^ Editorial_36`30a6.1.4ptWLcitem#WWWWWitem9oftable4soundsmorelikeaeventthanacommandVitemsNWitsܡWܤW0W6W{WݐWWW WXWtWuWW W!W<W|W}WWWitself"WwW۟W?WWitu-tvWivWjWjapanesewWxWyWzW{W~WWWWWWjoblWlWlWlWlWitu-tvWivޗWjWjoblWlWlWlWlWlWjoblWlWlWlWlWlWlWlWlWlWlWlWlWWnWoWzW{W|W}W~WہWjoblWlWWnWoWzW{W|W}W~WہWjoblWlWWnWoWzW{W|W}W~WہWjoblWlWWnWoWzW{W|W}W~WہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWTcutmost&Wutra۽Wv-aaa!Wvague6W-WW4W9Wvaguedefinitionofthresholdparametervaluerange4Vvaguesentencedependingonitspositioninthesystem6VvaguenessW'W)vaguenessinenoughinformationandconfusingtrailingphrasVvalid[WhWW݃WWWvalidrangefordestinationidentifierismihlocal/mihremoVvaluable܄WvaluewWۄWWwW܂WݾWWVWށWގWtWuWWWWWWWW W!W+W.W4W9W;WWWlWzW{W#Wvalue4descriptionisincorrectݾVvaluecolumnintablesection8.4.2.23needstobemodifiedށVedށVށVW=WMW|WWݳWWvariousW'WWaW݂WvarySWverbW/WversionېWWW݁Wvertical?W@W:W;Wvery_WwW WܸWܾWWWviaܬWviable۳WviewIWܤWݐW2jb|Change "Containing a set of configuration parameters." with "Containing a set of configuration parameters. See table below."cCThere is no information to where the configuration parameters are. d621g2295{k) done 2006/09/21kENada, Golmie, Member^Technical, Binding_91`32bAChange p90 line 46 from "This primitive is issued by uppers to control the behavior of a set of lower layer links." to "This primitive is issued by upper layers to control the behavior of a lower layer link." Add a new entry to the list of parameters line 10 Name Type Valid range Description Link Identifier Identifier N/A Identifier of the link to configureB   2006/08/21 jENada, Golmie, Member^ Editorial_91`10lower layer, for example, to set some feature of the driver of a specific link."r of a specific link."BcwilleWlWېWZWܤWWWWݐWݑWW WfWgWhWiWkWWWWWW W WW$WrWWWwillresultsݑVwindowWWwindowing W W WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW|W}W~WہWۇWۈWۉWۑWےW۩W۽WWWW WW#W.W3WYWcWhWrWsWܒWܔWܕWܝWܩWܺWW WWWW%W(W*WDW݄WݏWݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWݭWWWWWWWWWWWWWWWWW W W W WWWWW!W"W#W$W%W'W*W,W/WKWWWXWYWlWoWޕWޗWWW>csyntaxerrorinnumberofparametersinlinkparamterlist_Vsyntaxerrorinreceptionofthespecifiedsduwasacknowled܌VMacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhba9a7.3.13.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc c^MacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhbaTechnical, Binding_77`49a7.3.13.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc c^MacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhba 21-06-0xxx-Link_Identifier.doc c^MacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhba cthis WWHW{WW݃W݋WݍWWWWWWWWWWWW WWWWW"W#W$W%W*W4W5WOWYW\WaWnWއWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWL jone?WށWoneormoremakesitredundantandisnotrequiredށVonlyWWoperatorvWoperatorsvWoptionWor"W,WށWWWWother"WzWotherszWout?WoveruWWYWzWpageWtWWWW W WÃ@ÃPrÃ`OÃpPÃ+ÃQÃۏÃà ކÃ0-Ã@ÃPޗÃ`ÃpސÃÃޑÃÃޒà ܈Ã0܉Ã@܊ÃP܋Ã`sÃp܌ÃÃޓÃRÃܚà ܍Ã0ۀÃ@tÃPÃ`uÃpÃvÃoÃہÃމà wÃ0ۉÃ@8ÃP9Ã`:Ãp;Ã<Ã=Ã>Ã?à @Ã0AÃ@BÃPCÃ`D dDT ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_Ts&ݸbn"Within the MIHF header, additional identifiers that help to analyze and coordinate the payload are embedded."cy"Within the MIHF header, additional identifiers are present that help to analyze and coordinate the payload is embedded."d748g2429{k) done 2006/09/21 2006/04/28MarkedݹE YoshihiroFOhbaGMember^ Editorial_118`5a8.4b"the Length", "definite"c"theLength", "defiite" d765g2430{k) done 2006/08/29 2006/04/28 ݺE YoshihiroFOhbaGMember^Technical, Binding_118`57a8.4.1b'Network Identifeir should be Link Type.c'Network Identifeir should be Link Type.d773g2373wAccepted{k) done 2006/08/29 2006/04/28 ݽE YoshihiroFOhbaGMember^Technical, Non-binding_127`9a8.4.2.21c_Link Status Parameter should be described here in more details as specifed in Section 7.4.5.2.4d809g2371v&Refer to Section 7.4.5.2.4 for detailswAccepted{k) done 2006/08/29 2006/04/28 ݾE YoshihiroFOhbabremoveoreventhroughtheinformaitonservice?VremoveorrenameoneofthetwodefinitionswVremoveparenthesesremoveoriginating$VremovepreferredpoaidentifieVremoverdfdatardfschemaurlandrdfschemafromthevalue~VremovereferencepointsfromfigureandrestofdocumentVremovereferencestotransactionidfrommihfvariablehedaeVremovereferencestotypicallyfromthedraftܱVremoveseconddefinitionofmobilenodeatlines29and304Vremovesection1.6ܛVremovesection5.3.2andpossiblymoveittoannexrenaming<Vremovesection5.8orincludeasinformativenVremovesection6.3.6uVremovesection6.3.8jVremovesection7.2.3.1andtable16kVremovesection7.4.14gVremovesection7.4.15.3andreplaceitwiththeappropriatlyNVremovesection8.3.2.3UVremovesections7.4.15.3.27.4.15.3.37.4.15.3.4{Vremovesections8.5.3.19and8.5.3.20iVesection8.3.2.3.3.2.3*kcurrentdWWdatawWxWyWzW{W~WWWWWWWWWdeal)WdealingWdecided|WdecisionWdecisionsWdecodersWdefineWuWdefined|WWWdefiningwWxWyWzW{W~WWWWWWvWdefinition۴WWWdefinitionsWdeleteAWdeliverWdependentOWWWdeploymentWdescribingpWUWdestinationVWdetailedWWWWݴWݴWݴWݴWݴWݴWݴWݴWݴWnݴWݴWdiscoveryuWdiscussion<WjWdoۓWWW=WdocjWkWmWnWoWzW{W|W}W~WہWdocumentW-WdoesAWbWWWWdoesn'tWW+Wdomain\Wdon'tuWWݻWdon'tmentionintergernumbersbutusethetypeiexxxnamesݻVdowndWdraftWܬWdynamicWWdynamicallyW4baddh-aaainsection4݌VaddlinktypeietomihconfigurethresholdsandmiheventreۉVaddlsapandcssapalsomihnmssapshouldbesimplylistedVaddmihlinksapinthefiguredeleteothersapswhichmaynVV݌Vaainsection4݌V݌VVaddgetstatusresponsesetVaddh-aaainsection4݌VaddlinktypeietomihconfigurethresholdsandmiheventreۉVaddlsapandcssapalsomihnmssapshouldbesimplylistedDVaddmihlinksapinthefiguredeleteothersapswhichmaynWVaddmihlinksaptosection7.1.2CVVaddmoredescriptivetextmoveexamplequeriestotheannexVaddmoredetailtotable11VaddmoredetailtothecostiedefinitionVaddmoreinformationonscopingofthestandardVaddnewsectionsprobablyaftercurrentsection8thatdetaVޚVaddnewsubsectionsandtextinbothsection5andsection'VޥVaddqueryresourcelistattheendoftheparameterlist܎V/bthresholds@Otitle@tlvs@-to@a>=toanewvalueallocateanewoneorsplittheentry@toorco-locatedwiththepoa@(3=transporti@Iunder@upon@used@values@)what@Vwired@Swords@c1thisisalinklayerindicationwhichshouldonlyberecei@^2.5@45.6.2.1@7@8.5@aܼWabettertitlefor5.5wouldbemihreferencemodelforacce@achive@algorithm@among@and@annexes@-as@}aspects@avoided@@be[because@been@gbefore@beyond@but|by@capabilities@(clearlydefinewhichreferencepointsarenormativeandwhic@comma@compressed@confusion@consistency@contents@coverage@define@Ndefinitions@Ldefinitionsofhorizontalhandoverandverticalhandoverare@NceventsW7WQWRWyWzWܫWWaWWWWWWWWWWWWWWWWWWWWeventsmayoriginatefromthemihfunctionmiheventsoranyܫVeventsshouldbeallowedfromupperlayersorusersofthemVevery'WWWeverything!Wevolved۽WevolvingېWېWېWېWېWېWېWېWېWexaminetheusageofthewordtypicallyinthedraftandremܱVexample_WaWeWۈWېWےW۪W۵W۾WWWWWW'W-W:W@WiWܙWܼWWWWWW WWW W:W[W~WݔWWNWexamplequeriesneedmoredescriptivetextandshouldbeinVexamplesW`WW\WWexamplesprovidedlackcontextrequestingsuchinformationwVexceptW2WexceptionWexceptionalېWexcerpt>WexchangeWܖWWWFcaWWW+W0WAW݃WݍWݐWWWWWWWWWWWWW%W'W/W>WIWNWOW\W]W_WއWޒWޖW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WޗWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWgbclarifytextVclarifythatisservicescouldbeperformedbeforeauthenticVclarifythecontextofasystemhereordeleteorasystemfVclarifytherelationshipbetweenthesesectionsVclarifytowhatumtsradioprotocolsthemihlayerhasacce$Vclarifywhethertheeventnosintable2andtable3aremeaVclarifywhichiesareavailablebeforeattachingtoalinkaVclassWWWclassesWWWWWtoalinkaܺVfywhichiesareavailablebeforeattachingtoalinkaܺVܺVfywhichiesareavailablebeforeattachingtoalinkaܺVܺVreavailablebeforeattachingtoalinkaܺVܺVngtoalinkaܺVܺVommentsDWEWcommit/W0W5WcommonlyWcommunicatepWcommunicatesWcommunicatingWcommunicationuWxWۖW܅Wcomplete/W0W5WWWRWcW܉WcompletedWWRWcompletelyYWܓWhow All Records" button in Create and qscsupportedrWRW'W|WWWWWWtWzWWsupportedcommandlistېWsupportedeventlistېWsupportedisqueryWsupportedisquerytypeWWsupportedisquerytypeshouldbeinsertedforconsistencywithVsupporting!WWsupports|W3WWWsupposedWW WkWsureޏWWtWvWwWxWyWzW}W~WW܀W܃W܆W܇W܈W܊W܋W܌WܗWsyntaxerrorandconfusingsentenceincontrolthebehavioriVsyntaxerrorin3127reserved}VsyntaxerrorinadditionalidentifiersarepresentthathelptVsyntaxerrorinafterupperlayerentitiesmakeshandoverdefVsyntaxerrorinalsoknowaslowerlayers6VsyntaxerrorindeliversthismessagetothemihfoVsyntaxerrorindifferententitiesmayrregisterwithrVsyntaxerrorinlinkcommandoriginate8Vsyntaxerrorinlinkgongdown܈Vsyntaxerrorinmanyuser܊VfbdestinationWWdestinationidentifieۋWW|WdestnationidentifierWdetailzWWW7W7WzWzWu  x  )c    )c    )c    )c    )c    )c&)c'  )cscript so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create and g2710 2006/04/28@cbeWW#W'W,W-W.W0W1W3W:W;WCWHWYW`WkWmWvWwW|W܄WܬWܰWܾWWWWWWWWW WWW'W+W0W1WEWHW}WW݅W݋WݍWݒWݓWݔWݕWݖWݘWݛWݜWݵWݺWݽWWWWWWWWWWWWW WWWW#W%W/W/W/W/W/W/W/W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1WX cthe.W/W2W3W5W7W:W;WAWBWCWDWEWGWHWIWNWPWQWRWSWTWUWVWWWYWZW[W]W`WgWhWiWjWkWlWmWoWtWuWvWwWyWzW{W|W~W܁W܂W܃W܄W܅W܆W܋W܌W܎WܒWܓWܕWܖWܛWܟWܠWܡWܤWܥWܧWܫWܬWܭWܱWܾWWWWWWWWWWWWWWWW WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWQchImproper sentence "This primitive returns the result of the query to discover link layer events request"d504g2269{k) done 2006/09/21RENada, Golmie, Member^Technical, Binding_68`16bAAdd a new section 7.3.1 called Link Event ID Add the following table Event ID Description Link Detected 0 A new L2 connectivity has been detected for use Link Up 1 L2 connectivity is established Link Down 2 L2 connectivity is lost Linkost Link4/brestSWW1WrestrictedHWrestructure1Wrestructureascommunicateswiththemihfthatmayresidelo1VrestructuredZWsWresultېWlW܆WݑWW~WހWނWresultsqW~WނWresumeWWretain6WretainedWretention܇WtowardsVl2WWWWWuW}WWWl2'sWl3}WڎWWlabelWlacڎWlanWlanguageWWWlargeLWlat/lonڝWlaterW&WlayWlayerW-W4W5W8W9W;WAWBWCWHWVWنW٨WٮWWWWWWWWWWڍWڎWWWWlayerare{WlayersWW-W;W<W=W>W?W@WAWhW٭WWWW6WWWlayers/mihfhWlearnediWv?Change the text and make R1 as R1/R2/R3 on page 18 (line 57/58)wAccepted-Modified{k) done 2006/09/213EDasFSubir ^Technical, Non-binding_22`5a5.4.3bDelete the sentence cThe sentence "However the tarnsport and security of this information are outside the scope of IEEE 802.21" is not correct. IEEE 802.21 is aksing IETF to define the transport . d160g2433vnSecurity is out of scope. 802.21 enables both L2 and L3 transport options. Modify the sentence appropriately.wAccepted-Modified{k) doneRConsider adding a reference to Apendix (L2 and L3 Requirements) from this section 2006/09/212006/08/29 EDasFSubir^Technical, Binding_28`55a5.5.3b;Until additional text is provided, it should be deleted. c"For the case where MIH funcion is placed in the 3GPP2 network, it sPoS may be remote" . Why is it mentioned only in case of 3GPP2? d203vdelete the text.wAccepted{k) done 2006/08/29 EDasFSubir8 hފbAR 331  4 8 33Rimitives that are defined in the specification or remove these primitives. cKLink_Up.request and Link_Up.response are not defined in the specification. d871g2433predrawv!Replace .request with .indicationwAccepted{i) to do 2006/08/21Marked30 the description is not correct . d861g2432wAccepted{k) done 2006/08/21 ކEKenichiFTaniuchi^Technical, Non-binding_140a Annex A-1bmEither replace with euqivalent primitives that are defined in the specification or remove these primitives. cKLink_Up.request and Link_Up.response are not defined in the specification. d871g2433predrawv!Replace .request with .indicationwAccepted{i) to do 2006/08/21Marked30 5.4.2b8.5.4.2b_clText does not reflect the dependency of the transport mechanism on the location of the MIHF in the network. d235g2233wAccepted{k) done 2006/09/21 2006/04/28MarkedEEleanorFHepworthGMember^Technical (was Editorial)_36`30a6.1.4bAdd explanatory text.cFigure 15 would benefit from more explanatory material highlighting the difference between local and remote events, and how they may be combined at the MIHF. d268g2234{a) awaiting resolution 2006/08/29 2006/04/2815 EEleanorFHepworthGMember^ Editorial_39`11a6.2.1bChnage to different.cTypo: difference d285g2235i Eunah KimmAccepted{k) done 2006/08/29 2006/04/28 EEleanorFHepworthGMember^Technical (was Editorial)_42`34a6.3.1b Update diagram/text accordingly.cDiagram confusing; explanation of meaning of dotted lines is needed (or they need to be removed), explanation of relevence of GNI/LLI/HLSI breakout for APz or remove. d319 T6cA> 33  33 33> occurs between N-user and N-layer in the provision of a service" with "Conceptual abstraction describing the information transfer that occurs between N-user and N-layer in the provision of a service"@Af  33E  33H  33  33  33fcGSyntax error in the first sentence of the Service Primitive definition.d76g2239{k) done8/016ENada, Golmie, Member^ Editorial_21`11bAMReplace "(also know as "lower layers")" with "(also known as "lower layers")"M@Af 33  33 334  33: 33fcA/Syntax error in "(also know as "lower layers")"/@A> 33  33 33>d150g2240 2006/08/017ENada, Golmie, Member^ Editorial_35`38b lcthedefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofisquerytypelistisnotcorrectVthedescriptionofthemesageisthesameastherequest܅VthedescriptionoftypeielistofoperatorsismisleadingiVthedescriptionsofitems3and4areidenticaltheprimitivNVthediagramimpliesthatanynon-l2transportwillrundirec Vthedifferencesbetweencoreheaderspecificiesandcore80$Vthediscoveryofmihfunctionentitiesatl3isoutsidetheVthedocumentprovidesnoalgorithmsforrttestimationtherVthedocumentspecifiesthatanupperlayermayconfiguretheVtheeffectofreceiptisnotcoherentbecauseitmentionsthoVtheexampleinbracketsinconfusingegbsorrncorggsniVÃpܔÃ(ÃaÃhÃà vÃ0Ã@ÃPiÃ`ݹÃplÃZ0ÃZ`\ÃZpf ېbcAIt is obviously that SupportedEventList parameter in MIH_Capability_Discover.response primitive can be obtained from the Link_Event_Discover.response primitive. But from where MIH layer can obtain SupportedCommandList and report them to upper layer? Perhaps we can report it depend on table 4 in IEEE P802.21/D01.00, but most media specified technology is evolving, I think the MIH command list in table 4 and the Link command in table 5 is also probably changed, so we should discover the capaBbility of link layer command of different media specified technology. Most of MIH commands may be mapped to Link commands, so before the MIH commands initiate a Link command, MIH Function should learn about if the low layer can perform this Link command, in other words, MIH Function should discover the capability of link layer commands. For example, If MIH Function issue a Link command but the low layer dont have the capability to execute it, so there will be an exceptional result. FoObthisprimitiveisusedbymihfunctiontoqueryanddiscoverېVthistypeނWthosePWWthresholdTWۉWޖW5WnWW4WWLWresholdMWTWۉW\WoWޖW3W5W5WWthresholdMWTWۉW\WoWޖW3W5W5WWthresholdMWTWۉW\WoWޖW3W5W5WWthresholdMWTWۉW\WoWޖW3W5W5WHWresholdMWTWۉW\WoWޖW3W5W5WWthresholdMWTWۉW\WoWޖW3W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W\W`W{WޔWWWWW3W4WdWeWߢWߣWWWthroughpWW7WWWthroughoutWtidWtifyAW޿WW.W_WߝWWtimeAW\W]WܳW:W޿WW.W_WߝWWtimeinterval\WtimelyWtimerW&WޖWkusingWWWvalue۴WWWvWvaluesYWvariationWversaWversionWvery۳W-WvWWverygoodpointsthemiiscanbelocallyplacedontheclien۳VveyWviaWviceWwaywWxWyWzW{W~WWWWWWWWwaysrW|WWwe#WAWۓWCW|WOW\WgWpWrWuWvW|WWWWWWWWVWWWWWwehaven'tmentionedwheremiisistobelocatedthusitcanVweneedaparagraphsimilartothisthiswillgiveanideaaAVwellݓWWWvWWWwereWWWWWWW|WܸWWwhatisapageinthiscontextVwhenW+WwhereܶWwhich"W۴WWW݀WwhileWWWwhileuseofschemaisanoptionrequiredonlyforxml/rdfqVwholeW-Wwhy\WjWkWmWnWVX_bclassificationܰWclauseۮW۳WclearۢWܾWWclearlyܾWWWWWWclearlyspecifyextensibilityaspectsofiesfrom802.21perVclearlyspecifywhatrepresentationshouldbeusedforthenVclientAW۳W܅WܫWrWtWWWWWWWWWWclientsWclose3Wclouds!WcoHWco-locatedWcodeWzW{WWދWތWWcode1ۉWcode2ۉWcode3ۉWcodesۉWbWWWcoincide3WcollectܤWcollectingOWcollectivelyTWTWTWTWTWTWTWTWTWTWTWTWcollectingOWOWbWcoincide3WcollectܤWcollectingOWOWOW'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'WissiblenVcomeܰWW-observerۅۉۋیۍێۏېېېېې  >d7inding_75`36a7.3.10.3bAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Down" event. The MIH User(s) Higher layers may take different actions on this notification. The handover policy may eliminate this link from list of active links for routing connections and may consider handing over any potential active connections to other more suitable links. @Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d55g2293 2006/05/01 2006/04/24=EYogeshFBhattGMember^Technical, Binding_76`42a7.3.11.3bd56g2833 2006/04/29 2006/04/24jstring|WsuchWsuggestܾWsupercededWsupportWsupportedzWsupportingjWsure"WtableWYWtWWWtechnologies,WtechnologyWterminology?WtextW=WWWWthat,WjWWWWthe?WZWW|WܾW,WdWvWgWjWWWWW WW=WYWzW{WWWWWWWthemiheventregister/deregisterconfirmareokVthemihisl-shapedtoshowthatitcancommunicatewithdif,VthemihsapshouldbetechnologyindependenthowevertheconVtheminimumdataratemayprovidevalueincertaincasesforzVzVzVzVzVzVzVVVVcthenamespacemustbeassignedby802.21tosatisfyinteropeCVtheneedformihfunctiontosupportinformationserviceschjVtheneedformihnmssapisnotsufficientlyjustifiedthepkVtheneedforsection5.3.2isnotclearXVustifiedthepEVEVtheneedforsection5.3.2isnotclear!VedthepEVtheneedforsection5.3.2isnotclear!V!VVVVVVVort Comments" script. It had not been updated in 1.1 to match the new coCmment 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. _Hong-Yon`LachaMemberb34c 4/24/2006dTechnical, Binding cAThe command MIH_Configure_Thresholds should allow to define thresholds not only in the terminal, but also in other entities of the network. So this primitive should also be defined Network -> Network. Please, see the proposal 21-05-xxxx-00-0000-QoS_considerations_in_NIHO.docd303g2218v6MIH Configure Thresholds has been deleted from Table-4wRejected{a) awaiting resolution 2006/09/21 2006/04/30T. 4EQiaobingFXieGMember^Technical, Binding_41`32a6.2.5.1bAwRemove "MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" from Table 4w@A  33cA"MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" are improper for 802.21 scope. The functionality represented by these primitives is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@@gure 18Y-vselectingSWselectorWsemanticsWsend"Wsent۔Wsentence۪W۳WWW݃W/W W WWsentencesWseparateۓWWqWWseparatelyWsepartae\Wsept\Wsequence\WserverZWlW"Wservice*W۳W*W۳WWWWWݓWservices۳W W{WsessionݓWsessionsݓWsetۆWێW:WshallZW=Wshalls{Wshould0WZWWܗWW WzWSWshouldbeacceptedaspercontribution641fromeunahinjunzVshow0WshowingZWSWshown۴Wside݃WsimilarWsince۵Wsincemihfdoesnotreallymakeanypolicytypedecisionsit۵Vsingle*WsoWWsomeܗW;W{WݜWSWsparqlBWܗWspecificےWەWWWWWܗWܰWW0WSWspecifically݀WspecificationHWspecifiedWWW{WspecifyܾWWWWSWbctoinsureinteroperabilitytheieee802.21mustdefinehowtTVUVVVWVVtoorco-locatedwiththepoaVtothemobiledevicemntheonlyvisiblemihentityismihpVtocWWtogether݅WtooۢW۳W۶W݃WW W:W<Wtop۽W>Wtopic|WtopologiesWtotalWlW>W>W>W>W>W>WWWWWWWWWWWWWW!W%W,W-W.W/W2W:W<W=W>WDWEWHWJWLWMWOWPWQWRWUWVWWWXWZW[W\WaWcWiWuWzW|WڄWڋWڝWڡWڦWWWWWWWW Ec@Marked 0ە@Pۖ`pۗۘ‚!‚"‚#‚$ۙ‚%‚&ۚ‚',‚(‚)ۛ‚*!‚1ۜ‚2s‚3‚4‚5"‚6۝‚7۞‚8#‚9$‚:݅‚A۟‚Bܛ‚C‚D‚EW‚F‚G۠‚H݆‚I&‚Jp‚Q‚R‚Sۡ‚T'‚Uq‚V‚W‚X>‚Yۢ‚Z‚a1‚b‚c(‚dۣ‚e)‚f ‚gۤ‚h*‚i.‚jw‚q‚r‚s‚tۥ‚u3‚v4‚w‚x/‚y,‚z‚+‚‚ۦ‚ۧ‚‚-‚5‚ۨ‚ܟ‚.‚ ‚2‚0‚݋‚݌‚‚‚‚ܠ‚‚‚۩‚‚t‚ܡ‚‚/‚ܣ‚‚ܤÃ!۪Ã! ܥÃ!00Ã!@1Ã!P۫4Ã# ۯÃ#05Ã#@Ã#P۰Ã#`6Ã#pÃ#XÃ#۱Ã$Ã$ Ã$09Ã$@Ã$P7Ã$`Ã$p8Kjshow@string@ithenotionofinformationrepositoryiscorrect@then@~tlvs@=variable@you@FFcorrect@them@~tlvs@=usefulness@you@Fs@Fhihiro's@Fyoshihiro's@Fchorizontal?W@W:W;W,WWWhorizontalhandover:Vhot-spots'WhotspotsWhoweWTWUWVWWWmWܭWWWW}WYWWWWWWWWWWWWWWWWWWWWW W WWWWWWW'W<WlWrWWWWWWhowarethelinktypeparameterslistsupdatedasnewtechno VhowisextensibilitymanagedfortheinformationelementsnaVhowthisinformationisdevelopedanddeployedinagivenl2ܭVhoweverۅWW)WYWܬW WaWW*WOWYWWWtWuWWW WWWWWWWWWWWWWWWWWWWWWWWWWWidentifiersDWEW[WtWܓWidentifyWWidsNWCWRWTWUWVWWWXWW.ܒEWolfgangFGroetingGMember^Technical, Binding_115`5a8.3.3.1bA- Change size field for "Reserved" from 4 to 10 - Change size field for "OpCode" from 3 to 2 - Change size field for "Act.ID" from 9 to 10@Az 33- / 33\ ] 33 zc@Size of the fields is not consistent with that in the figure 28.d740g2262wAccepted{k) done 2006/09/21 2006.03.05T18ܓEWolfgangFGroetingGMember^Technical, Binding_115`30a8.3.3.1bRemove this row completelycLThe field "Number of Additional Header Identifiers" is no more in figure 28 d744g2263wAcceptedwAccepted262wAccepted{k) done 2006/08/27 2006.03.05T18 ܓEWolfgangFGroetingGMember^Technical, Binding_115`30a8.3.3.1bRemove this row completelycLThe field "Number of Additional Header Identifiers" is no more in figure 28 d744g2263wAcceptedtorialcisW"W#W(W)W*W+W?W@WAWCWDWGWIWJWKWLWOWPWQWRWSWTWUWVWWW^WfWgWhWiWlWrWsWwWxWۀWۄWۅWیWېW۔WەWۢWۥW۪W۳W۶WۻW۽WWWWWW W WWWWWWW'W)W-W.W/W1W2W3W:W;WAWBWDWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEW\ RcA Most areas where Mobile IPv6 are referred to, should be IPv6. These cases are referring to IPv6 access network topologies. Mobile IPv6 is not associated with IPv6 access networks (unlike MIPv4) The address generation is instead handled by RFC 2461 IPv6 Neighbour Discovery, which is a primitive service of IPv6. - Starting Page#: p72, p105, p122, p137 - Starting Line#: p72 (14-15), p105 (64), p122 (49-50), p137 (35) - Section#: 7.3.9.1, 7.4.14B.2.2, 8.4.2.2, 8.5.3.19 d519g2219vCommenter needs to clarify this more. Changes in section 7.3.9.1 do not lok accurate If any discrepancies are found a separate comment can be submitted. May need to remove SIP from this list. Add room for ading other choices as well.wRejected{a) awaiting resolution 2006/09/21d 2006/08/29 EDas,FSubir^Technical, Binding_87`59a 7.4.5.2.2bAdd GetStatusResponseSet.c GetStatusResponseSet is missing.d605'abreplacethedefinitionofhorizontalandverticalhandovers@replacetimeintervalinwhichthelinkisexpectedtogodo@}repository@represented@request/response@`resides@4rest@^retransmission@est/response@`resides@4rest@^retransmission@resides@4rest@^retransmission@des@4rest@^retransmission@rkinformat@`resides@4rest@^retransmission@des@4rest@^retransmission@`resides@4rest@^retention@@^andremovesuchremotem@`reside@4eproposal21-06-0631-00-0000-pforamendmentoflink@"sentence@serviceprimitiveconceptualabstractiondescribingtheinfo@;services@set@\shouldbeincludedintable3sincetheyfallundermiheven@shouldrewordthisandsaythatduringregistrationtheuser@shows@sion@sory@spec@Remberemove@bmakesfWcWdWmaking*WvWwWWmanagedܾWmanagementUW۝WWWܤWIW4W5W8W2WWWWWWmandatoryWWWW2WmandatoryWW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2WmaximumWWWmay W"W#W,W-WAWFWGWMWOWPWQWRWSWTWUWVWWWXW_WdWfWiWsWuWWۂWۉWېW۫W۳W۶WWWWWWW#W,W3WCW\WeWrWyWzW{W~WWܪWܫWܶWW;WIWQW_WtW݊WݍWݎWWWW W W"W#W$W%W&W+W/WmaybeVmaynotliketVmaycauseۉWmbit/sYWmeanWmeaningoWmeaningoflinkparameterthresholdshouldbeexplainedpossoVAW tbAReplace "additional identifiers are present that help to analyze and coordinate the payload is embedded." with "additional identifiers are present that help to analyze and coordinate the payload are embedded."@A 33\  33^ 33  33 33  33 33cqSyntax error in "additional identifiers are present that help to analyze and coordinate the payload is embedded."d746g2305{k) done 2006/09/21uENada, Golmie, Member^ Editorial_116`1b Remove line 1cRThe Transaction ID is already defined in the Fixed Header part of the MIH message.d751g2306{k) done 2006/09/21vENada, Golmie, Member^ Editorial_118`5bAReplace "The format of theLength field shall be per the defiite form of ITU-T X.690." with "The format of the Length field shall be per the definite form of ITU-T X.690."@@@HcthelasttwowordsofthelastlineneedtobeinterchangedVasttwowordsofthelastlineneedtobeinterchangedVVasttwowordsofthelastlineneedtobeinterchangedVVasttwowordsofthelastlineneedtobeinterchangedVVXVthelengthfieldisimproperfortherequestthereisnoaddMVthelengthoftheisquerytypelistissettovariablebut|VthelinkdetectedismissingfromthelistofprimitivesSVthelinklayerparametersdefinedheremustnotbeexamples`VthelistofparametertypeneedstobecompletelydefinedbyYVthemappingisnotfullybespecifiedintable24p145EVthemayrespectingusewiththesidisnotmeaningfulhowisVthemihconfigurerequestisusedtocontrolthebehaviorofkVthemiheventregisterandmiheventderegisterrefertotheeVthemihlinksapshouldbeshownonthisfigureitwillclarV܂V ^bindingܖWܖWܕWܕWܕWbinding_112`21a8.3bA[Delete the following rows, page 112, line16] : Figure 24 shows possible MIH message delivery and its relation with other protocol layers. [Remove figure 24, page 112] @A>  332  33  33>us' valuse can be taken from the values defined in section 8.4.2.17 , or vice versa.d647g2220 2006/05/14 2006/04/307EJinFLeeGMember^Technical, Non-binding_112`21a8.3bA[Delete the following rows, page 112, line16] : Figure 24 shows possible MIH message delivery and its relation with other protocol layers. [Remove figure 24, page 112] @A>  332  33  33>_ 33} >con | Bitmap | 0-31 | 0: LINK_DISCONNECT | eGMember^ Editorial_71`1g3503 2006/05/01Wu==balinkupeventmayalsocarrynewipaddressrenewalacquisݍValistofoeratoridentifiertlvs@VamihgetstatuscommandisissuedbythelocalmihfunctionVanumberofcommandshavebeenaddedprovidedtoallowtheuVatowardsVavisitedenterpriseenvironmentVa-2WardsVavisitedenterpriseenvironmentVVVavisitedenterpriseenvironmentVVspecificVhighW+WhigherW-W;W<W=W>W@WAW٨W6WhihWhnadoverWhoړWho-typeAWhomeڃWڄWڝWhorizontal+W-WٱWhorizontallyrWhotspot#WhoursٿWngeneralhandoversmaybeinitiatedeitherbythemobilenVinclude4W5Wincludeing?Wincludes+W-WincludingWinconsistencyWWindependencemihWindependent+W-WindexingiWindicationAWBWCWindications@WindividuallyfWinforma-WJc"Link Quality Parameter Type" encoding is insufficient and needs to be expanded. For instance, what if the link parameter that needs to be encoded in the BLER (block error rate) or RxLevNCell parameter of a GSM/GPRS link?d796g2286v1Use Radius NAS-Port Type for specifying Link TypewAccepted-Modified{k) done 2006/09/21 2006/04/24KEQiaobingFXieGMember^Technical (was Editorial)_43`43a6.3.2cText between line 43, page 43 and line 12, page 44 is not about Information service elements. This text should be moved (and possibly merged) into Section 6.3.1.d331g2287v%Move the text as is to section 6.3.1.wAccepted{a) awaiting resolution 2006/09/21 2006/04/24d | +--------+----------+---------------------------------| @Af 33M 33   33 fefore retransmission}, | | | | W Gbc"Link ParameterType" definitions is insufficient and needs to be expanded. For instance, what if an upper MM algorithm wants to set a threshold on the BLER (block error rate) or RxLevNCell parameter of a GSM/GPRS link?d525g2283wAccepted{k) done 2006/09/21 2006/04/24IEQiaobingFXieGMember^Technical, Binding_85`15a 7.4.4.1.1bA.change text to: Examples of link layer parameters that could trigger this event include: - {Generic : Link Speed} - {Generic : Link Bit Error Rate} - {Generic : Link Frame Loss Rate before Retransmission} - {Generic : Link Received Signal Strength} - {GPRS : BLER} - {GPRS : RxLevNCell} - etc..@.@ 33  33  33K  33W 33  33 33 M 33 | | | before retransmission}, | | | |  #bB------------ MacMobileNode | MAC Address | N/A | MAC Address of Mobile Node MACNewPoA | MAC Address | N/A | MAC Address of New AP/BS MacOldAccessRouter | MAC Address | N/A | MAC Address of old Access Router (if any) MacNewAccessRouter | MAC Address | N/A | MAC Address of new Access Router (if any) IP_Renewal_Indicator | Boolean C | N/A | 0 : Change Required | (Optional) | | 1 : Change Not Required @AR  33I  33    33Rcssion of the problem. d298g2333{a) awaiting resolution 2006/08/21EPeretzFFeder^Technical, Non-binding_41`1b>Remove until Appenidx inlcudes such handover command scenariose$caswWۉWیW۶WWWW'W6W7W:WGW܄W܅WܧWܬWܰWܾWWWWWWWW0WHWOWaWeWzWW݅WݽWWWWWWWW>WBWOW_WnWqWޖW1W5WrWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWW WWW.W7W8W<W?WkWWWWWWWWWWWWWWWWWWasshowninthepresentation21-06-0524-01-0000-816paramet8VaskWasnWWasoWaspecisܾWaspectWWWnWoWqWsWtWzW{W|W}W~WہWۂWۄWۅWۊWۋWۍWېWۓWەW۝WۡW۪W۴W۵W۷W۾WWWWWWW cforۚW۪WۭWۮW۽WWWWW-W7W:WZW[WiW܂WܖWܫWܵWWWW WaWfW{WW݋WWWWWWW WW'W-W2W>WVWYWaWpW~WޖWXW\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWqWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWW W!W7W8W9W;W<WIWVWWWYWiWkWoWtWvWwWxWyWzW|WWWWWWWWWWf5bencodingJWGWHWTWUWVWWWhWݘWWWWW+Wencodingformatisdefinedindraft-ietfgeoprivݘVencodingformatisdefinedintable9ݘVencompasses,WendWAW۠WۧW۶WۻWQW܎WOWPWWWendthesentenceasmnastheotherendpointalsoremovedasۧVend-points۴WendpointۧW+WengagedWWengineWݎWenginesWenhancementsەWenoughTWUWVWWW"W$WWWWenterWenterpriseWseWW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WWWWWWWWWWWWW:W;W=W>WAWIWgWuWڎWڔWڹWWWWWWWWWWlinkcommandindicationrequestVlinkcommandsoriginateVistWWٲWٸWٹW:cfieldPWvWwWܓWWݵWWW6WWWWW+W9WlWWfieldsܒWWfigWWtion6.3.8toannexc٧VqosقWنWWqualifyingکWquality6W>W@WٳWqueriesWqueryWW-WWWWWWWWWWWWW Wquery-20041012Wquery-20041012httpwwww3org/tr/rdf-sparql-quVqueryresourcelistWquerytype WquickWWr0087pWradioIW!WeWgWڍWradiusٴWWraeWڴWWise, "Show All Records" button in Create and g2341 2006/04/28bevents WLWېW7WTWUWVWWWyWzW{WܫWW|WWWWWWWWWWWWWWeventsmayoriginatefromthemihfunctionmiheventsoranyܫVeventuality Wevery'WevolveAWexactlyބWޅWexamineېWexample?WAWJWVWZWHWTWUWVWWWYWiWW}WݔWWtW5WsWtWWWWWWW.W<WWWWWWWWWW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WzHLEQiaobingFXieGMember^Technical, Binding_68`38a7.3.1.3b3.2cText between line 43, page 43 and line 12, page 44 is not about Information service elements. This text should be moved (and possibly merged) into Section 6.3.1.d331g2287{a) awaiting resolution 2006/09/15 2006/04/24LEQiaobingFXieGMember^Technical, Binding_68`38a7.3.1.3buld be wrong.v1Use Radius NAS-Port Type for specifying Link TypewAccepted-Modified{e) editor disagrees 2006/08/29 2006/04/24MarkedKEQiaobingFXieGMember^Technical (was Editorial)_43`43a6.3.2cText between line 43, page 43 and line 12, page 44 is not about Information service elements. This text should be moved (and possibly merged) into Section 6.3.1.d331g2287{a) awaiting resolution 2006/08/29 2006/04/24LEQiaobingFXieGMember^Technical, Binding_68`38a7.3.1.3b7.3.1.3b | | etransmission}, | | | | kquery/response|WquitewWxWyWzW{W~WWWWWWradiusۓWrae WrangingWrate"Wrdf/sparql/owlWre-submission:WreadwWxWyWzW{W~WWWWWWreadilyWreallocationYWreasonWWWreasonsWreceivedWrecommendWrecommendedwWxWyWzW{W~WWWWWW:WreconfigureWreference"W۴WWrejectWrejectedWWWremedyWremoteWremoveWremovingWrenewalWrepeatedWrepetitionsWreportuWreportsuWrepositoryWrepresentYWrepresentationWrequestWrequesttypeprimitivecannotbeissuedfromlowerlayertoVrequest/responseWrequestsWrequireWrequiredWWW WWWrequiringWresourceWWWcie^WێWWW'WaWܾWtWqWWWWWWWWWWWWWWWWWWieeeېW۩WWHWRWTWUWVWWWYWܛWܧWWWWW݅WWWWWWWWWieee802.11WWieee802.16ۋWWieee802.21݅Wies$WtWuWWWWWWWWies2.22.32.4shouldbeundergeneraliecategoryVies/reportsfromWietfWWifGWIWJWiWېWW;WCWZW܄WݵWW*WޖW6WW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W*WޖW6W6W6W6W6W6W6W6WWWWWWW*WޖW6W6W6W6W6W6W6W6W6W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WVW+kalong۴WalreadyWYWalsooWalsoalsoadyalsoalsoWalsoalsoalsoalsoWalsoalsoWalsoalsoalsowWalong۴WalreadyWݻWalsoalsoWalsoalsoalsoWalsoWWalsoWWWsoWWWXvbclarificationWWWWclarify۴WWWWWWWWWWWWWW W$WWWWWWclarifyanyinteractionbetweenmihfandhardwareormodifyVclarifydefinitionofmobilenodeVclarifydefinitionofreferencepointend-points۴VclarifydefinitionsVclarifydescriptionoflinksynchronouseventsVclarifyhow/inwhatwaysecurityinformationismadeavailabVclarifymihprotocolwrtVclarifymihswitchoperationVclarifyrepresenttaionofalliesintable-6operatornamesVVVVVommandcodezW{WcommandsuWېW8WcommentۓWۯW`WcWcommentsDWEWcommit/W0W5WcommonlyWcommunicatepWcommunicatesWcommunicatingWcommunicationuWxWۖW܅Wcomplete/W0W5WWWRWcW܉WcompletedWWRWcompletelyYWܓWbentireAWZWiWܥWW]W^W_W`WbWcWdWeWsWentirelyWentitesWtitesWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW5W9WڟWڣWWWWWWWWWWtable22sparqlquerytlvvalueparametersformatVtable23sparqlquerytlvvalueresponseparametersformatVtablexxextendedschemaurlparameterformatVtablesGWtailښWtake;W<W=W@WAWBWtakenٿWWtargetgWtayloredfW/}dÃAÃA;ÃBܵÃB @ÃB0}ÃB@LÃBPAÃB`?ÃBp:ÃBÃB@ÃBÃCÃC ÃC Ãb@aÃbPÃb`ÃbpÃb_ÃbYÃbÃclÃc ZÃc0Ãc@nÃcPbÃc`GÃcpÃcݜÃc[ÃcÃdÃd OÃd0Ãd@AÃdPPÃd`ۅÃdpÃdBÃddÃd]ÃeQÃe CÃe0^Ãe@RÃePÃe`ÃepDÃeÃeSÃeÃfEÃf _Ãf0`Ãf@mÃfPޖÃf`TÃfpFÃfUÃfÃfGÃgVÃg HÃg0aÃh fÃh0ېÃh@ÃhPÃhÃhÃi[Ãi Ãi@ÃiPÃipÃiLÃiMÃjÃj0IÃj@5ÃjPÃjpÃjkÃjÃq݇Ãq Ãq0یÃq@ÃqPÃq`ÃqpÃqfÃqÃrcÃr ݈Ãr@ÃrPgÃr`ۃÃrphÃrdÃrÃriÃsÃs jÃs@hÃsPkÃsۄÃslÃsgÃtÃt ecvsW/Ww/oWwaittWvWwaiting8WwanttWvWWwantsGWIWޖWlWmWwas܄W܌W*WwWxWyWzW{W~WWWWWWwayۋW/WIW>WWWW WWWways1WweۅWېWݵW2WXWWWW>WWWWwehavedecidedthatcsapandmsapbetweenncmsandmihfa2Vwe'd?Wwell'WHWWWWWWwell-known?W@WwepWwg>W>W>W>W>W>W>W>W>W>W>W>W>WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWeedstospecifyit'sownlocܽVwhereeWېWWWAWBWZWjWwhereas%W&WwhereverܥWQbpre-provisioned۶WpredefinedޖW5WpredictedRWpredictive^WWpredictiveeventspredictiveeventsexpressthelikelihoodoVpreferedpoaidentifieۋWpreferredlinkidentifۋWpreferredpoaidentifieWprefix~W-WpreparationWprepareQW\WaW8W|WWpreparesWpresenceWpresent۶WtW'WW"WpresentedsWpreserves)WpreviousۯWpreviouslyۉWWprimitiveLWcWdWeWiWlWېW#WNWVWZW`WkWܟWaWzWWWWW"W$W%W>WBWއWnWWWWWW7W|WWWWWW@W@W@W@W@W@W@W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WW8W>WlWmWކW<^technicalWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW MIP.d530g2266 2006/05/14 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`45r should not have to interpret this information to pass it to the MIHF.wd529g2265 2006/05/14 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`9a7.3.9bRemove SIP from list.cIt is difficult to envisage a scenario where SIP is supported in the PoA. SIP proxies may be placed in the network somewhere, but one support by the PoA is not required in quite the same way as it is for MIP.d530g2266 2006/05/14 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`45thGMember^Technical, Binding_74`45Wd& RېcCr different technologies or different version of the same technology, the Link command capability may be different, which can result in the MIH Function has different MIH commands capability. The MIH users should know the difference by discovering capability of link layer command.@A*  33  *d572g2248p)- added as new sections 7.3.20 and 7.3.21wAccepted{k) done 2006/09/21 2006/04/11ۓETakashiFAramakiGMember^Technical, Binding_44`38a6.3.2bH?... Discuss the issue in .21, send LS to IETF for comment if necessary.cYUsing RADIUS related definition may be a good idea but it also implies RADIUS dependency.d348g2215i Subir Dask_It is not clear what additional things we need to do with the RADIUS. Need more clarification. mRejectedpRejectedpt to create a new table and copy current RADIUS draft values in? Which values should be included?ility @exceptional result. Fobsip_WލWW>WWsizeHWܑWܒWܔWݗWހWނWWWWWslightlyWsm$WsoTWUWVWWWWWWWsocketuW~WsoftWsoften۳Wsoftentheclausebysayingmayusemiisinformationallowt۳VsoleWsome WiW?WIWWW'WWWWWWsomebody's'WsomethingWsometimesWsomewhereWsoonVWsory W W WW.W.W.W.W.W.W.W.W.W.W.W.W.W.W.W.Wth no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create and g2344 2006/04/28P^technicalܚWܛWܬWܭWܰWܾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWW W%W'W+W0W1W2W3W:W;WAWBWCWDWEWFWHWJWLWOWPWSWUWVWWWXWYWZW[W\W]W_W`WaWbWhWkWoWuWxWyWzW{W|W}W~WW݀W݁W݂W݃W݄W݊WݍWݎWݏWݒWݓWݔWݕWݖWݗWݘWݙWݛWݜWݝWݞWݟWݠWݡWݢWݣWݤWݥWݦWݧWݨWݩWOcthey۴W7W`WWWW6WkW|WWWW_WcWWWWthingeWthingsIWWthinkېW6WWthis#W*W+WAWKWLWOWPWQWRWSWTWUWVWWWZWfWgWۄWېWەWۥW۴WWWW'W)W-W/W:W;WQWYWZWoW{W܂W܆WܕWܖWܛWܣWܫWܭWܾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhisinformation@reject@removelimitationsremoveimplicationofcapabilityuniquet@repeat@resource@ isubirW\WoWpWrWsWtWvWWWWWWWWW Wsubirdas#VۓVCVV\VoVpVrVsVtVvVVVVVVVVV Vvivek"WZW۳W۴W۶WWWWݓW)W-WvWށWWWWWWWWMWOWQWTWvWzW~WWWWWWWWWWWWWvivekgupta"VZV۳V۴V۶VVVVݓV)V-VvVށVVVVVVVVMVOVQVTVvVzV~VVVVVVVVVVVVVVVVVUWyoshihiroBWjWkWmWnWoWzW{W|W}W~WہWWWWW݀WoWyoshihiroohbaBVjVkVmVnVoVzV{V|V}V~VہVVVVV݀VoVJ=bfrom?WAWPWVWiWW#W3W7WHWkWܑWܒWܔWܖWܤWܫWܭWܱWW9WzWݎWݕWݘWWWW"W(W,W>WIW\W5W\WaWfWhWqW~WWWWWWWWWWWWWWW W(W,W2W7W>W@WlW|WWWWWWWWWWfromoneaccessnetworktoanotherwillresultinVfromthevisitednetworkaboutthatvisitednetworkorabout9V9V9V9V9V9V9V5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WިWWWWWWW1WEWHWbW߃W߆WWdcthatJWwWۄWۋWېW۪W۳W7W:W;WZWtWyWzW{W|W~WܒWܔWܬWܰWWW W0W3WaW݃WݛWݸWWWWWWWWW%W,W/W>WnW1W2W5W|WWWWWWWWWWWWWWWWW W WWWWWWW!W"W$W'W1W5W7W<WjWkWlWWWWWWWWWWWWWWWWWthat'slWlWlWlWlW5W5W5W5W5W5WۂWۃWۄWۅWۆWۇWۈWۊWۋWیWېWۑWەWۖW۟WۤWۦWۨW۪W۬WۭW۵W۸W۽W۾WWWWWWWWWWWWWWWWWWWW W W W WWWWWWWW#WVncincurrentdraftd01mihconfigurerequestprimitivehasacۄVincurrentdraftd01severalhandoverprimitivesareinconsiۃVinfigure12showmihlinksapandit'srelationshipwithotVinfigure3interfacetocellularbsisincorrectaspertheVingeneralitisnotclearfromthecurrentdrafthowthisiVinlinkdetectedisitenvisonedthatmiphandoffbetweentwVJVJVnkdetectedisitenvisonedthatmiphandoffbetweentwJVJViWkWnWpWqW|W~WفWقWكWمWٕW٥W٦W٧W٨W٩W٪W٫W٬WٱWٳWٴWٷWٽWٿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#W(W0W6W8WJWZW^W_WcWeWgWlWrWuWyWzW|W`\brepresented#WzW{WܬWWݗWWދWތWWWlWrepresentingHWTWUWVWWWWWrepresentsTWUWVWWWWWrepresenttaionWrepresetsWrequestVWiWlWۋWېWQWVW`W܀W܄WܕWW%W>WCW~WޅWއW6WtWWWWWWWW7WIW{W|WWWWWWW#WrequesttoreconsidertheusecasesandremovesuchremotemVrequesttoreconsidertheusecasesformihnetworkinformatVequestnetworktypeۊWrequestsUWWWܕWܽWrequireW>WrequirelargemessagesupportfromtheunderlyingtransportVrequired"W#WAWەWW\WܬWWW WWWWrequiresxWrequiresclarificatioxVrescindedRWreserve"WWreservedyWۉW$WRWTWUWVWWWXW|W}WܒWܹWWA{bWaWbawaitingmissinginputVaVcیWۢWWWWW WWWWW-W6WcinstructionsunclearیVۢVVVVV VVVVV-V6Vdefer-WܾWWWކWdisagreeshWWdWdoۃWbWdoneWWWWW W"W(W)W*W+WDWGWIWJWLWOWPWQWRWSWTWUWVWWWZWcWdWeWfWgWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWۗWۘWۙWۚWۛWۜW۝W۞W۟W۠WۡWۣWۤWۥWۦWۧWۨW۩W۪W۫WۭWۮWۯW۰W۱W۲W۳W۶W۹WۻWۿWWWWWWWWWj#ctheneedfortypeienumberofoperatorsisnotsufficiently^VqVthenewlinkidentifierismissingfromthelistofparametegVtheoverheadinexchangeofinformationshouldbeaslessasVtheparameterqueryresourcelistismissing܎VtheparametersupportedisquerytypeismissingVtheparameterstimeboundandconfidenceshouldnotbebold:VthepoacapabilitybitmapisnotsophisticatedenoughtocapVthepoadefinitionisassociatedwithaninterfaceinsteadoVthepresenceofthefahah-aaaandv-aaainthereferencem!Vtheprevioussub-sectionstalkaboutthemodificationsthatkVtheprotocoldoesnotseemtoincludeanycapabilitytoreacVeprimitiveisthemihfunctionwhichwillVtherecipientshouldbemihfunctionsincethisisalinkprfVthereferencemodelincludesamedia-dependentpartthemihAVthereferencepointsarenotusedanywhereinthedocumentt۬V 1bcEach mobile node should be aware that the peer entity has the MIH Function to initiate media independent handover. As one of the ways, Information Element related to MIH Function discovery can be provided.d439g2214padded as Bit 4wAccepted{k) done 2006/09/21 2006/04/302EJinFLeeGMember^Technical, Non-binding_27a5.5.3bAV[Delete C_SAP and M_SAP between MH Function and Management Entity , Figure 8, page 27]V@A  33cWe have decided that C_SAP and M_SAP between NCMS and MIHF are the common point to transport MIH message. Therefore C_SAP and M_SAP between MIHF and Management Entity in Figure 8 should be deleted. d193g2215pneed to redraw fig [Vivek] This is a VISIO figure which is embedded in Framemaker. Should be easy to open it sa is and delete the two lines to C_SAP and M_SAP along with the SAPs.wAccepted{k) done 2006/09/21 2006/04/30888g_85`29a7.4.4.1bi3eclocated:W`WlocationWWWW=Wlocation/interestWlocationsWlogicalXWWWlogicallyWlongitudevWlongitude-resolutionvWlongtitudevWwWlooking+Wlooks݃W>WW7Wlooksoutofplace>VloopWloosexWloseWloss۝WWkWlotAW<WlowېWWlower6WiWkWmWܫW,WWlsapYWWlsapsWlte۽WmNW2WWmacWܰWW+W WWWWW?WWmacaddressisnotsuitableforallmediaalsohowaretechnVVmacaddressquestionagainistheuseofmacaddressessuitaVmac/phy$WmachineWWWWWWWWWWWWWWWWWWWWWWormconsistent۰VmakesfW:W݂W݈Wmaking*WۅWۆWܳWܴWݏWmanageWmanagedWWWc55-WiW55-56lW56-WiW56-61W580W6ZW)WWWWWWWWWWWWWW6.1.3W6.1.7W6.2.3W6.2.4zW7W6.3;WW6.3.1KW`W6.3.3pW6.3.4pWW6.3.4.1sWWW6.3.4.1.19W6.3.4.1.4AW6.3.4.2.1BW6.3.4.2.39W6.3.5`WtW6.3.6.1/W6.3.8WW:W64W݇W66W67W690vWvWvWvWvWvWvWvWvWvW90vWvWvWvWvWvWvWvWvWvWvWvWvWvWvWvWvWvWWalternativeSWan*W+W.W:W;W<W=W>WFWGWHWIWLWMWSWandWW"W#W%W&W'W(W)W*W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WAWBWDWEWFWGWHWIWJWKWOMb4c$Duplicate definition of Mobile Node.d65g2238{k) done 2006/09/21 5ENada, Golmie, Member^ Editorial_9`38bAReplace "Conceptual abstraction describing the information transfer the occurs between N-user and N-layer in the provision of a service" with "Conceptual abstraction describing the information transfer that occurs between N-user and N-layer in the provision of a service"@Af  33E  33H  33  33  33fcGSyntax error in the first sentence of the Service Primitive definition.d76g2239{k) done 2006/09/21 6ENada, Golmie, Member^ Editorial_21`11bAMReplace "(also know as "lower layers")" with "(also known as "lower layers")"M@Af 33  33 334  33: 33fcA/Syntax error in "(also know as "lower layers")"/@/@/@WSg_cbecauseZWWއWtWuWWoWpWbecomeW WbeefedWnced I-Ds to become RFCs.cCannot interoperate with using the standard document which refers to IETF I-Ds. (also happens in P46-L9, P51-L26, P152-L15, P158-L16. P158-L39)g2211ayout 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 coCmment 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. _Hong-Yon`LachaMemberb23c 4/24/2006dTechnical, Binding6camongZW3WsWamountsWan*W+WGWIWLWSWiWۅWېWW-W2W:WZWWWWW+WݔWW>WIWfWgWhWiWlWmWnWWWWWWWWWWWWWWWWWWWWW W!WiWpWqWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWtvsome{WݜWWW"WWsourceWsparqlށWރWjWWspecificەWWWܰWW0WށWރWWWWWWWW4WWspecifically:WspecificationHWWWWspecifiedlW{WOWWW WspecifiesWspecifyܾWWWWWWWWWspecifyܾWWWWWWWWWWWWSWSWSWSWSWSWSWSWXu(bmakethefollowingchangeto*Vtocontribution21-06-06makethefollowingchangeto*V*Vution21-06-06܏Vmakethefollowingchangeto*V*VckWroomڝWroundTWrouterٱWuWWroutersٱWrowWrrcڍWrregisterWNWrttMWQWRWTWrulesTWUWVW_WrunOWrxlevncell2W3W4W5W6WsWWWWWWWsafeMWsameWىWيW٦W٨WٱWWWWWW<W>WڔWڥWWWWWmment 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. _Yogesh`BhattaMemberb33c 4/24/2006dTechnical, Binding:݃{k) done 2006/09/21 2006/04/3055cific L2's MIH reference model) Show only one arrow that will represent ES/CS/IS together (all MIH signaling) Show only two kind of arrows: Local Interaction and Transport : only 2 colors instead of 3 different colors... -> Replace by 21-06-0612-03-0000-Reference_Network.pptKcAlthough valid, this diagram looks too busy. This is exactly the type of diagram that scares the reader and does not help them have a straightforwad reading of the overall MIH reference model. This plays against the acceptance of the draft.d187g2255pre.]v[Delete the last sentence of second bullet and add MIH User from network side in the figure.wAccepted-Modified{c) instructions unclear 2006/08/22 2006/04/30Marked5nhance this section for other L2's we supportyAssigned as issue number 30{a) awaiting resolution 2006/08/21ۺÃ(p@Ã($Ã(ۻÃ) AÃ)0ۼÃ)@Ã)pvnosuggestedtextcommentassignedforfurtherworkZVnosuggestedtextissueidentifiedVnosuggestedtextissueidentifiedandassignedVVnosuggestionprovidedforaremedyVnotexthasbeenprovidedVnodeW"W?Wnode's"WnoneWnoneoftheidentifiersaregloballyuniqueVnormativeWWnormativedoesnotmeanmandatoryinfactschemasupportisVnot۔W۴WWW)W-WW{WݓWݜW\WWWWWWWWWWW W WWWWW W'W4WVWoWWWWWWWWWWWWWWWWVWoWWWWWWWWWWWlednetworksegmentssuchaVnotsureifthisisreallyrequiredۈVnoteWܗWWnothingށWnotificationQWRWSWTW\WnotionfW=FjvariableWversionܾWvertical,Wvertical-handover?Wvery"WwantWwe"WgWW=WWwell?WwhatWwhenzWwhereWwhich"WjWwhichupperlayershandlethis"VwholeWwinthinWwithW,WjW|WWW=W}Wwithin,WWwithoutjWwordWxmljWxml/rdfWxml/rdf-basedjWyoshihiro'sWWBWBWBWBWBW:_‚gۄlӃN‚mO‚ۋ܎]P‚ݭ‚Q‚^|‚_RÃ!6Ã! `Ã!0 Ã!@"gSÃ!P#$%Ã!`ৃTÃ!pioއwxӃÃ!lܕܖ|}ވyzÃ!pN~{ԃÃ"pqe Ã" rstfԃ|pqÃ"0vwێr gݲ& rÃ"@x ݵUVᎃÃ"P۔ܑăՃ'V}Ѓ;VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV]ۀہی۔۬ۃ-0Ju܁ܜܠܼܾ0#ۏ۞؃ܗܬ@"&'SsPDy܆`۠rv}ܒpۢƒӃ)p۩Tܡ%ܚJW K‚!2ۄ܃ Oj^bradioۖWWWW$WradiusݔWݕWݘWtWWradiusoperator-nameattributeݕVradius-lo-04ݘWradius-lo-04txtݘVraexWjWފWrangeېWWTWUWVWWWYWkWmWܖW6WWWWW4W8WWWratzWrateGWIWJWۉWYWWlWmWWWzWrather%W'Wratherthenlistingprovideindividualdescriptorforeachn'Vrdf|WqWwW}W~WwWxWyWzW~Wrdfdatawhenthisinfoquerytypeisspecifiedinfoqueryparam}Vrdf/sparql/owlWrdf/sparql/owlaren'tnecessaryVV~W~W~W~W~W~W~W~W~W~W~W~W~W~WparametertypeasapairoflinktechtechsFVGVre-definethelinkqualityparametertypeencodingtableasJVre-organize_WbWre-verificationWWre-visitWreadqWWreader݂WreadersWreadilyWbditto)Wdiuc8WdividezW7Wdo WWWdocۃW}WݒWݓWݜWWWWWWAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWYW[W\W]W^W_W`WaWbWcWvWwWxWyWWWWdocumentۋW۶WW1WWWWWWdoesAW,WWdoesn'tWdoneWkWWWWsn'tWWesn'tWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWۻWWWendthesentenceasmnastheotherendpointalsoremovedasۧVend-points۴WendpointۧWengagedWWenhancementsەWenoughWenterpriseWentire1W2W3W4W6W7W8W9WAWZW]WiWbuponWW`W W"W$Wuponreceiptthereceivingmihfunctionintheoldlinkmay Vuponreceptionofthisprimitivethemihfontargetnewpoa$Vupper"W*WLWQWSWWWcWdWpWۉWېWەW7WNWZWfWkWݍWݎWWWWW"W$W,WnWWWWWWWkWWWWupper-layerWupperskWupportingWW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WމWurlsWuseUWfWuWۘWۜW۞W۰W۳W۸W۽WWWRWSWTWUWVWWWXWcWsWܯWܿWW W W"W3WZW݂WݎWWW WVWiWjWWsWuseaasinothersimilarcasesintable۰Vuseatvariousinsteadofother"VMWb4sip_VލVV4zerooroneextendedschemaurlparametersށV4-mihW4.3rW40`W40-417W41,WWW42-45W43-447W45,W46kWWW4889W5ەWWHWRWSW1W6W[W}WmWvWwWxWyWW5fixedethernetV5-7ލW5-7reservedލV5.1W5.2W5.3pWW5.3.2XWW<W5.5=WvWwW5.5.2xW5.5.3yW5.6.1WW5.6.1mediadependentsapsV5.6.1.4W5.6.1.4lsapV5.6.1.5W5.6.1.6WWW1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W|W6.1W6.3;W6.3.1`WܶWW6.3.2AWBW6.3.3YW6.3.4YWܗWܷW6.3.4xxinformationquerytypeܗV6.3.4.1]W6.3.4.1.2^W6.3.4.1.4AW6.3.4.2.1BW6.3.5`W6.3.6aW6.3.7bW6.3.8BWW݀W63~W65W690vWcmihreportshouldbeinfoqueryresponsesinceinsection8.5.|VވVmihsapalreadyhassapinthenameۤVmihswitchrequestVmihswitchrequestshouldincludenewlinkidentifierieێVmih-3g%Wmih-3glinksapshouldinterfacewithl3functionofthecdm%Vmih-3glink-sapWmih-capabilityWmih-function,Wmih-isWmihconfigureWyQWmih-function,Wmih-isܘWmihconfigureEWEWih-isܘWmihconfigureEWEWmih-isܘWmihconfigureEWEWEWEWEWEWEWEWEWe "below sections."g2235 2006/05/01^ Editorial_141`6a Annex A-1bg3239 2006/04/29ayout 1.1: Many changes, including addition of use as a balloting tool. _Yogesh`BhattaMemberb34c 4/24/2006dTechnical, Binding 'voutەWWW"WWWoverTWWown WpacketۅWWpackets*WWpage۳WWHWܬWW WWWWpage18sentenceonline22changesasfollows۳VpagingWU lLbAChange text to: This primitive is generated by MIH Function when it needs to discover what link events are supported by a link layer. an upper layer entity of type MIH User that is seeking to receive link layer event notifications.@Af 33  33  0  )c  TTfciThis is a link layer primitive which should only be generated by the MIH function, not by an upper layer.d503g2289wAccepted{k) done 2006/09/21 2006/04/24OEQiaobingFXieGMember^Technical, Binding_74`25a7.3.9.3b7.3.9.3b06/08/13 2006/04/24LEQiaobingFXieGMember^Technical, Binding_68`38a7.3.1.3bAChange text to: This primitive is generated by MIH Function when it needs to discover what link events are supported by a link layer. an upper layer entity of type MIH User that is seeking to receive link layer event notifications.@ | | }caspects۽WWassembleܤWݐWassignedCWxWܚWލWWWassignmentoWassociateWiatedBWW WWassociationWassumeWassumethereferencetodiameterisactuallyapointertohoVassumedWWassumesiWassuming۳WW_WuWassumingthatmnreliesonaccesstomiisistoostrongmore۳VassumptionWassumptions:WatjWkWmWnWoWzW{W|W}W~WہWۄW۔W۪WW7W܌WܝWWWW WW+W;WWWW7WKWQWZWattached+WattachesݏWattachingOWattachmentܝWattempts&WaugmentܶWautenticated#Wautenticatedwiththepoaandshouldbenewpoa#VauthenticatingܺWauthenticationWWbWavailabilityWWavailable=WYWܡWܢWܶWWWSW|WݏWWWW!W%WgWavoidWW6coffers:WtWvWoldhW W"W#WdWqWoldlinkactionۃWoldlinkactionsoldlinkidentifierKWbWoldmacmobilenodeWKWbWoldmacmobilenodeandoldlinkidentifiershouldbereplacedwiKVbVed "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 and g2352 2006/04/28[s[cMMisleading use of square brackets, which are customarily used for references.d793{k) done 2006/09/21 ESanjeevFAthalyeGMember^ Editorial_124`43a8.4.2.11b"status"cSpellingd798{k) done 2006/09/21 ESanjeevFAthalyeGMember^ Editorial_126`15a8.4.2.17b "handover"cSpellingd802{k) done 2006/09/21 ESanjeevFAthalyeGMember^ Editorial_137`5a8.5.3.18bRemove "basically"cSuperfluous wordd852{k) done 2006/09/21 ESanjeevFAthalyeGMember^ Editorial_145`12aAnnex A2b"acknowledged"cSpellingd887{k) done 2006/09/21 EGregFDaleyGMember^Technical (was Editorial)_72`14a7.3.9.1b Use the term "IPv6 with DHCPv6" instead of "Mobile IPv6 with DHCPv6", and "IPv6" instead of "Mobile IPv6". c6". cPv6". cPv6". cPv6". cPv6". cà ޅÃ0Ã@ÃPrÃ`OÃۏÃà ކÃ0-Ã`Ãpސ" abfhe text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link SDU Transmit Status" event. The MIH User(s) Higher layers may take different actions on this notification. A higher layer intermediate buffer management entity in MIH could use the success indication to flush higher layer packets stored in any intermediate buffers and a failure indication to retransmit higher layer packets stored in any intBVermediate buffers, especially if there are changes in access network during handovers.D@Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d557g2298v0as per comment 555. (Resolve it the same way...)wAccepted-Modified 2006/08/07 2006/04/24 VEQiaobingFXieGMember^Technical, Binding_80ngG  L{neededWYW6WW<WWnext-WܾWWWކWnone#W?W^W`WۏWۺWW'WIWgWhWlWܰWWW=W>WTWcWtW݈WWWYW6WW<WWprogressRWCWresolution$W@WAWCWKWpWsWvWۼWWNW[WܵWWWWIWRW@WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#Wround-WܾWWWކWtoۃW-WܾWWWbWކWunclearیWۢWWWWW WWWWW-W6W€€W€W€W€W€W€RRC (MAC/PHY)d197 2006/05/14DEFarrokhFKhatibiGMember^Technical, Binding_28`23a5.5.5ibiGMember/05/14XfcperhapsېWWperiod۳WޒWWperiodic۳W<WWperiodicallyޖWperspectiveW!WWpertains*Wpertinent<WphraseWkWW*W6Wphrasing۱W"W,WnWqWphy+W Wphy/channelsWpicture۽W>W$WpiecesWpiggybackedWpiggybacking WW WW W"W#WܩWܺWܾWWWWWWpoas_WaWpointۊW-WܝWpointerWpoints۬W:WܨWܪWܯWWpolicyܡWWpolicyenginetypeentityshouldbechangedtopolicyengineVpoorlyZWportWportsWposWܩWܯWpositioningWpossibilitywWpossibleۈWW:W@W|WWWWWWpossiblyKWWܡWpotential\WWpotentiallyܩWpowerWpowerfulWpppWpre-defined_WbWܿWpre-establishment\Wpredictive^WpreparationۅW candW"W#W(W)W*W?W@WAWDWGWIWJWKWZW`WeWfWlWqWsWwWxWۄWۅWۋWېWەW۳W۴W۶W۽WWWWW#W$W)W-W7W:W;W<WNWRWVWYW`WiWmWtWzW{WܕWܛWܟWܡWܤWܨWܫWܬWܭWܰWܱWܾWWWWWWWWWWWW W W W W W W W W W W W W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%Wbchanged܂WWWWchangesUWۃWۄW;WWWOW{WWWchangesinradioconditionsofservingandtargetlinkVchangingWchannelW܋WWchaper/WchapterWWWchemaހWނWchnageWchnagetodifferentVcicrcularWcivicݖWcivicaddresselementsuWclafiryWclafirytextasaboveVclarificatioWeVVWclafirytextasaboveVVWWW#W$W%W'W,W3W8WPWUWVWWWXWall 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. _Yogesh`BhattaMemberb38c 4/24/2006d EditorialcstandardsܱWWW>WtWvWWstart W*WWWstartingWWWWWWWstartingline1Vstartinglinep1018p5951Vstartinglinep225Vstartingpage118Vstartingpagep10p59Vstartingpagep22VstateW<WWWWWstate-1WstatedaW-WW/WaW-W-WWaW-W-W-W-W-W-W-W-W-W-W-W-W-W-W-WWܕWstore܂WstreamlinestrengthWstrong۳WstructureܬWܼWstructuredjWkWmWnWoWzW{W|W}W~WہWstructuresWsttausWsub-optimal۶Wsubdivision/WsubmittedܮWsubnet\Wsubnetinformationaloneisinsufficienttosupportscenario\VsuboptimalWsubscribed7WsubsetWsubsystems/WsucceedseWsuccessۄWsuccessful܄WsuccessfullyWsuccinctnessW 'bA   33        33         33 |bremovethewordrequestattheendofthesentenceQVremovetheseareinthebeginningofsentencealternatively(Vremovethiscommandsinceitiscoveredbyitme9oftable3VremovethisrowcompletelyܓVremovetransparentVremovetypehdrtlvmihfidVVremovetypeienumberofoperatorsfromtable6qVremoveunnecessary/misplacestatementasfollows VremoveuntilappenidxinlcudessuchhandovercommandscenariVremovedWW۫W>WBWWWWWWޗWVremovedWWW۫W6W>WBWޗWޗWWWW۫W6W>WBWޗWޗWW>WBWޗWޗW6W>WBWޗWޗWW۫W6W>WBWޗWޗWW۫W6W>WBWޗWޗWޗWWWWWWWWWWWWWWWWWWWWWWWWWWWWۭWWW:WKWwWdband@y&$,oand/or@annex@appended@application/xml@architecture@^are{area@arrow@larrow@larchitecture@^are{area@arrow@larrow@lllow@array@ltionbelow@array@l{aredescribedinthesectionbelow@beexchangedinordertoachieveisservice@9beare@becomes@mbeginning@bitXbler@bottom@byބbyr1r2orr3overanyaccessnetworkandtwomihnetworke@cahnge@cards@certain@ chages@%change{}change5.6.3.1mihnmssap@5changeasfollows@ changecontainingasetofconfigurationparameterswithcon@Tchangenetworkmaybeabletoindicatetothemobilenodeto@?changep90line46fromthisprimitiveisissuedbyupperst@mchangetextto@changethesizefrom6to8bytesinthefigure27@6cdestination@ Wapplication/rdfWapplication/sparql-qWapplication/sparql-rWapplication/xmlWWapplications-Wappreciably-Wappropriate-W@WقWڟWڣWWappropriatelyـWګWapprovedWWaps+WڔWarchitectureWare WW-W8W:W;WAWHWٮWٺWWWWWWWWWWWWW8WIWVWrWtWzW{WڔWڴWWWWWW WWescribedinthesectionbelowVarenotraeڴVarea#WWarrivesٍWarrowWWarrowsWarticle٩WasW WW-W2W3W6W:W;W=WBWCWIWZW^WcWiWwWقWلWمWٓWٟW٤W٥W٭WٮWٲWٺWپWWWWW WWWW>WHWIWeWiWpWsWzWڇWښWکWڶWWWW WW vremoteWWWWremotemihfreturnsthenecessaryinformationtothemnviaVremotelyWremove@WgWhWۅWHWܛWdWWremove7.4.8gVremovefigure19@Vremovereferencetothewebpagehttpwwwjhalldemoncouk/HVremovetablehVremovethementionof802.3ethernetinthelabeloftheproVremovethissectionܛVremovedWreplaceW1WWWކWWWWreplaceadministrativecategorybystatechangecategoryforVreplaceallupperlayersbymihfuserswhereverapplicableVreplacelocal/remotestackbylocalentity/remoteentityVreplacemaybewithisVreplaceperformanceofaccessnetworkswithconfigurationanVWۆW۔W_WWކWrequest/responseWrequestparametersۆWrequiredۈW۔WەWW_WSWrescindedRWreservation"WreserveVWreservedWresolutionfW>W&bdeletemihoܠVdeleteoneofthemۦVdeleteoraddanewdefinitionVdeletetheaninformationrepositorypartVdeletethedefinitionVdeletethefirstsentenceofitema۪Vdeletethefollowingrowspage112line16VdeletethefollowingsentencewVwV۪VW4WڟWڣWWdefinitionofnetworkoperatorinmiddlecolumniscicrcularكVdefinitionsٱWٸWٹWWBWWdelayقWdeleteYW]WMWOWڋWdeletemediaagnosticڋVdeleteoneofthemYVdeletethefirstsentenceofitema]VdeletedWdeliverWڻWdeliversWdeliveryWdemonٿWdependantWdependencemediaWdependent0WW(Wdepending-WWWWdependingonthetypeofmobilitysupportfordifferenttypeV]+ RbB Going Down 3 L2 connectivity loss is imminent Link Event Rollback 4 Predicted event has not occurred and hence event indication must be rolled back Link Parameters Change 5 Link parameters have crossed specified thresholds Link SDU Transmit Status 6 Indicate transmission status of all PDU segments Link Handover Imminent 7 C L2 handover is imminent Link Handover Complete 8 L2 handover has been completed Reserved 9~31 Future usecTo Discover what type of events are supported by the Link Layers and to register to receive these events, the primitives use Event IDs. The IEEE 802.21 must define the list of Event IDs in order to support interoperability between different Link Layers. d502g2270A5 bcein this standard, in order to access 3GPP services provides through existing 3GPP SAPs. This does notd246g2245{k) done 2006/09/21 2006/04/28 EPeretzFFeder^ Editorial_34`44bAjPredictive events: Predictive events express the likelihood of change in the link properties in the futurej@Af  33I  R  33`  c  33fc]Predictive events: Predictive events express the likelihood of change in properties in futured257g2246{k) done 2006/09/21 2006/04/28 EPeretzFFeder^Technical, Binding_52`54a 6.3.4.3.2bAPoA maximum Data Rate@A>  33    33>c8PoA Data Rate The relevant information is max data rated430g2253wAccepted{k) done 2006/09/21 2006/04/28EPeretzFFeder^Technical, Non-binding_61`48b61`48b61`48b61`48b06/05/17 ~܆c@A> 33!  33( 33>d847g2323{k) done 2006/09/21Marked܇ENada, Golmie, Member^ Editorial_137`11bANReplace "Resource Retention,Status (20)" with "Resource Retention Status (20)"N@Af 33  33" 338  33H 33fcA0Syntax error in "Resource Retention,Status (20)"0@A> 33  33* 33>d853g2324{k) done 2006/08/29 ܈ENada, Golmie, Member^ Editorial_142`21bA0Replace "Link Going Down" with "Link Going Down"0@Af 33  33 33%  33* 33fcA Syntax error in "Link Gong Down" @A> 33  33 33>d881g2325{k) done 2006/08/29 ܉ENada, Golmie, Member1xnadagolmiemember2V3V4V5V6V7V8V:V;V<VAVBVCVDVEVGVHVIVNVPVQVRVSVTVUVVVWVYVZV[V]V^V_V`VaVfVgVhViVjVkVlVmVoVpVrVtVuVvVwVxVyVzV{V|V}V~VV܀V܁V܂V܃V܄V܅V܆V܇V܈V܉V܊V܋V܌V܍V܎VVVVVVVVVVVVVVVVVVVVVVVolveraWWWWWWWWWWWWWWWWWWWWWWWWWjWkWlWmWWWWparknpeklWnWWWpekyewlVnVVVpengWWWWWɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃5 8bA{This primitive is issued by upper layers to discover the status of the currently connected and potentially available links.{@A>  33  (  33>cThis primitive is issued by uppers to discover the status of the currently connected and potentially available links. Clarify "uppers"d599g2257{k) done 2006/09/21 2006/04/28 EPeretzFFeder^ Editorial_90`46bAFThis primitive is issued by upper layers to control ......layer links.F@A>  33  (  33>cPThis primitive is issued by uppers to control ....layer links. Clarify "uppers"d620g2258{k) done 2006/09/21 2006/04/28 EPeretzFFeder^Technical, Non-binding_102`27b102`27b102`27b006/04/2814 EPeretzFFeder^ Editorial_86`64b 2006/04/28 d d ^Technical, Binding_62`11a Figure 22V!=ccoverage:WWW'WcoveredgWWcreatedWcreatesWcriteriazWcriterion-WcriticalDWcritically[WW WYWZW]W_WbWeWuWWۃWۄWۅWۆWۇWۈWۋW۸W۽WWWYWnWW{Wcurrenttextneedsimprovement,Vcurrently'WSW_W:WcurrrentPWcustomarilyWfWcustomaryۣWWWGWlWcustomaryuseVVlVcustomerWd01ۃWۄWdalay|Wdash۱W8WrWdashes۝WdataWWWWW:WWWdatabase۳Wdatabases:WdatagramWdcd|WdealjWkWmWnWoWzW{W|W}W~WہWۈWdecideۋWWWdecidedWW WdecisionfWܤWܳWܴWdecisionsۅWۆWWWdecodeVWXWdecodersWdecription܄WdedicatedWdeepWdefault:WdefiitevWWU 6PbAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Down" event. The MIH User(s) Higher layers may take different actions on this notification. The handover policy may eliminate this link from list of active links for routing connections and may consider handing over any potential active connections to other more suitable links. @Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d534g2293wAccepted{k) done 2006/09/21 2006/04/24QEQiaobingFXieGMember^Technical, Binding_76`42a7.3.11.3b7.3.11.3bh >observeropqrList, SupportedCommandList, SupportedISQueryTypeList ) 7.4.1.2 MIH_Capability_Discover.response MIH_Capability_Discover.response ( C SourceIdentifier, DestinationIdentifier, ResponseNetworkType, MacPoA, SupportedEventList, /29Gy{lgWhWlWܰWWW=W>WTWcWtW݈WWWYW6WW<WWAfter an upper layer entity makes handover decision"w@Af  33   33$  33C  33_  33fcESyntax error in "After upper layer entities makes handover decision" d608g2291 2006/08/07 gENada, Golmie, Member^ Editorial_88`64_88`64d586g2290 2006/07/19fENada, Golmie, Member^ Editorial_88`47bAwReplace "After upper layer entities makes handover decision" with "After an upper layer entity makes handover decision"w@Af  33   33$  33C  33_  33fcESyntax error in "After upper layer entities makes handover decision" d608g2291 2006/07/19gENada, Golmie, Member^ Editorial_88`64upports the events.}d583g2288b_ kare۴W)W\WrWWWWWWVW~WWaren'tWas"W#W۴WݓWW-WOW\WgWwWxWyWzW{W~WWWWWWWWWWWOWvWWWWWasaresultofadhocdiscussionwehadgroupconsensusthatgVVaskWaspectWassistWassociateWat\WVWavaiableWavailableWbackbone}WbasedWbasicOWbe"W۳W۴WWݓW)WOWrWuW|WWWWWWWWWWWWWW:WvW}WWWbecauseWbecomeYWbeenvWWWbeforepWWWWbehaviourWbetter)WWWWbW+WOWcarefulܹWcarrydWcaseCWW+WdWcasesoWcertainWchangesWclarificationۓWܹWclarifyWclarifyingWclassesWbaksince#W\WWWWWVWsincetlvandxml/rdfarefunctinallydifferentinthattlvVsincewearenotaiminginthepresentstateonroutingforwVVsmallWsodWWWWsockets~Wsolution#WsomeWvWWsometechnologylike802.16hastriggerforiprenewalifthVVec"W-Wspecific"WuWWܺW݀W+WOWPWspecificationYWWspecificationsWstaWstandardWstartYWstateݴWstaticWstep"WstructuredjWkWmWnWoWzW{W|W}W~WہWstructuresWsuccess"Wsuch#W\WWsufficientjWkWmWnWoWzW{W|W}W~WہWsuggest"W/WsuggestedWsuggestionWsuggestions/recommen"WsuggestsZWsupercededXWwWWbWW7Wsupercededby577bVsupercededby695Vsupercededby697wVV7V!vforwardlWforwarding*WVWfoundWfragmentation Wfragmentationneedstobehandledbytransportlayeraddaf VframeWframework3WWtion of the IEs. Then redefine the mechanism in section 6.3.7 to allow the requester to specify which root and which branch(es) to retrieve, also add support for filter strings and wild cards. The retrieved values are returned with full contextual information. pcs the realtionship between the IEs. mRejected 2006/05/14 2006/04/24bEQiaobingFXieGMember^Technical, Binding_56`62a6.3.7bApFirst to re-organize the IEs into a tree (or multiple trees) structure, establishing the contextual information of the IEs. Then redefine the mechanism in section 6.3.7 to allow the requester to specify which root and which branch(es) to retrieve, also add support for filter strings and wild cards. The retrieved values are returned with full contextual information. pc.wbfrom@front@function@,functional@!functions@0generic@geographical@going@greater@handing@handoverhandovermode@ghandovershas@Xheader@hence@"hnadover@however@:identifier@ieee802.11@if@ii@important@inz3inthedescriptionfieldreplace@inthissectionareprovidedintheappendix@include@includeadescriptonforfollowingentriesintable-7@Bincluded@independencemih@indicate@#infoquerytype@~pe@~#infoquerytype@~~inclusion@indicate@#infoquerytype@~ndicate@#infoquerytype@~~#infoquerytype@~~querytype@~~~~iton@#infoquerytype@~inclusion@indicaiton@#infoquerytype@~pe@~pe@~pramaeters@W;W>WCWHWLWTWshow٠WW' {[XYFC@ZFt[ccAs@\@qciVv_^kAO#bAB$bA4)p-cA1.@p41v34c6cAb7cA:bcB D,;c;cpTbAUbAVbA[cWcYcAfZcA]bA)_bab"hcjbLkcmbA obAtbAvvbAwc@ycA{bA|cD~E܀bA܂c0܄cA܆c@܉^܋cAܑ^qܓ{ܕcsܚb@ ܟbܡbA|ܤbAܥcܫbudf {kdone V"V#V$V%V&V'V(V)V*V,V-V.V/V2V4V5V8V:V>VAVBVIVLVMVNVOVVV[V\V]V_VaVdVkVlVnVpVqVtVuVvVwV|V}V~VVހVށVނVރVބVޅVއVވVފVދVތVލVގVޏVސVޑVޒVޓVޖV1V2V5V=V>V?Vl#W?W^W`WۏWۺWW'WIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWrs to control ....layer links. Clarify "uppers"d620g2258 2006/08/07 2006/04/28 EPeretzFFeder^Technical, Non-binding_102`27b102`27b102`27byer links. Clarify "uppers"d620g2258 2006/05/18 2006/04/28 EPeretzFFeder^Technical, Non-binding_102`27b006/05/14zcshowZWwWWBWYWsWWWWWWWWWWWshowingWpWshown7WWWYWZWWW8WjWWWWWWWWWWWWWWWWWWsideCWW0WsignalWdWsignaling/W0W1W2W3W4W5W6W7W8W9WjWޭWޮWޯWްWޱW޲W޳W޴W޵W޶W޷WWWWWWWWWWWWWWWW W!W"W#W$W%W&WMWNWOWPWQWRWSWTWUWVWWWߋWߌWߍWߎWߏWߐWߑWߒWߓWߔWߕWsignificantWW WWsimilar(W*W\W]WWEWFWGWHWsimilartopage58lines1-21lackofcontextunnecessarypa]Vsimilartowhatisstatedin6.3.6.1exampleslackcontextr\VsimilarlyWWZ&aannexa-1-VVVކVސVޑVޒVViVVannexa-2ޓVannexa2VsVannexbۀVannexb1tVV5Vannexb2V6VannexcwVVVVannex-3annex-a1bۀWb1tWW5Wb2W6WcwWWWWfigure{W#Wfigure18#Vfigure22{Vtocb0JWۉWHWRWTWUWVWWWYW|WܖWWVWގ1W6WWWWW;WWW0successܖV0unknownV0-100W0-255YW0-316W0-65535W0-or-1W0006&W001122334455~W0123456789ab~W04ݖW04txtiegeospatiallocationinformationݖV05ݕW05txtݕV0598W06(W,W0626-00-000WWVVݖVVVrkaddressinformationV1createanewiewiththefollowinginformationatline38=V1dividetheflowintotwoinafigurelocalandremotecommyV\bservices"WAWpW0WW1W|WWkWWservingW"W#WW|WWsesAWsessionxWܚWWWWWWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhW[Wsetthelengthfieldto1|VsettingW8WsetupۉW/WshallW W-W.WeWW۟WvWwWܕWW W WOWQWshallsubmitthecorrectcallflowQVshoudlWshoudlexplainwhatammendmentsneedbedoneinordertoallVshouldVWWWZW]W۫W۷W۸WWWWWWWWW#W%W&W(W*WܨWܷWWWWWWDWUWYWkWoW݀W݂WݺWWWWWWWWWWWW,W-W.W0W6W9W=W>WAWBWDWJWPWTWshouldbeaddedtotable5anddefinedVPQaۤbRemove the second SAPc#MIH_SAP already has SAP in the named56{k) done 2006/09/21MarkedۥESanjeevFAthalyeGMember^ Editorial_8`23a3bRemove sentencecThis sentence is circular.d63{k) done 2006/08/29 ۦESanjeevFAthalyeGMember^ Editorial_8`21, 28a3bDelete one of them.cMThere are two Mobile Node definitions. The definition on line 21 seems wrong.d72{k) done 2006/08/29 ۧESanjeevFAthalyeGMember^ Editorial_8`58-59a3brEnd the sentence as "... MN as the other endpoint". Also remove dash "Network side" in the beginning of sentence.cImproved clarity.d73{k) done 2006/08/29 ۨESanjeevFAthalyeGMember^ Editorial_9`38a3b Remove "the"c."the information transfer occurs" reads betterd77{k) done 2006/08/29 ۩ESanjeevFAthalyeGMember^ Editorial_13`7a5.1cNGlobally replace "specification" with "standard" when referring to IEEE 802.21d91{k) done 2006/08/29(cchangeۏW:W;W1W݇WWWWWWW"W#W$W/WIWYWޖW5W>WWWWWchangearealreadytomayalreadybe1Vchangemiheventregister/deregistertomiheventcommandsVchangepoaVchangetable33ainlinethatquotesdescribedintable33aVchangethefollowingtextaninterestinaparticularorgroIVchangeuserequipmentVVVVcle-WWcircularۥWciteWclaimingWclarificationWclarifiediW1WmWWݏWclarifyZWcWWclarityۧW$W>Wclarityconciseness$VclassesWWWclassificationWܰWclauses(W*Wclear!W-WۆWۈW۾WW WW$W.WsWܳWܷWܸWܹWܾWܿWWWWWWWWWW W W W WWWW!WclearerWclearlysWܪWܴWW Wbnetwork-side+Wnetworks"WAWZWۻWW[WܡWW,W0WPWQWWWWYWsWtWWWWWWWWWWWWW>WWWWWnetworks-specificpWnetworkstechnologies$WnetworktypesZWnewAWەWۚW#WHWRWSWTWUWVWWWkWmWWWkWݍWݛW W"W$W%WWW[WWWWWWWWW WW|WWWWWWWnewtextVnewlinkidentifiergWnewmacaddressWnewpoaidentifierfWnextfWfWfWfWWWWpoaidentifierWWfiergWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWi5jshowZW,WvWshown+Wshows,Wsip/mipWslide+WsoWsome=WWspcifiedܾWspecific"WܾWށWjWWspecifiesWspecifyWWsrcWstack,Wstacks"WstandardWstatusWWstillWstreamline=W=W=W=W=W=WsupercededWsupport WsupportedWsupportingBWsure"WtableWWݻWWWtechnologies,Wtechnology Wterminology?WtextWWW݄WTWthatBWWW,WTWthe<W?WBWZW۬WWWWW|WܾWWW W݄WݻWWW,WTWdWgWhWjWrWvWthemiheventregister/deregisterconfirmareokrVthemihisl-shapedtoshowthatitcancommunicatewithdif,Vthemihsapshouldbetechnologyindependenthoweverthecon VtheminimumdataratemayprovidevalueincertaincasesforV WkBpt in standardized manner (as is) across all networks....but some variation of this is probably required in different networks. Any specific primitives/mechanism dealing with handover execution (address/route updating) etc. should be completely outside the scope of this draft.m Question?vby comment 495w Superceded{a) awaiting resolution 2006/09/21 2006/04/24tbl 4EPeretzFFeder^Technical, Binding_41`36a6.2.5.1bAThis command is sent by current the serving MIHF entity to the target MIHF entity to allow for resource query, context transfer (if applicable) and handover preparation.@A   33  33   33!  -  33<  ?  33p    33PeretzFFeder^Technical, Non-binding_39`21b39`21b39`21b39`21b applicable for L2 handovers only?d259g3230d259g3230Fc 2006/09/21 2006/04/24dEQiaobingFXieGMember^Technical, Binding_81`58a7.3.18.3bAchange text to: This primitive is generated by the MIH Function when an upper layer entity that may needs to get values of certain Information Elements@A 33  0  )cF  \  TTe  i  )cj  cNLink primitive can only be generated by MIH Function, not from the link layer.d566g2313wAccepted{k) done 2006/09/21 2006/04/24eEQiaobingFXieGMember^Technical, Binding_81`65a7.3.18.4bAchange text to: The recipient first shall get the information and then responds immediately with Link_Get_Information.response primitive.@A 33    )cH  Q  TT\  TT]  recinterpretlWWWinterpretedܾWWinterprettedWintertechnologyWintervalޖWWintoKW`WW?WWWW WWWWWintra-roamingWintra-roaminghandovermechanismsisundefinedVintra-technology?W@WintroduceܫWWuWintroducetextexplainingmihnet-sapuVintroducedWWWintroducingWintroduction`W WWintuitiveWinvokedWWWinvokingWinvolvedWtWinvolves:WipwW۪W:W WݍWWrWWWWW WWWip-configurationWipaddressnWipv4Wipv6WWWipv6routeradvertisementcannotfitintotheipaddresstypVirrelevanceWirrelevancenumberofoperatorsisofnorelevanceVVVVVVVVVVVVVVVVVWۇWۈWۉWۋWېWۓW۪WA;^technical@Mh:ܑܕoܖܚݵW<CnS>technicalbinding@+ܑܕ]ܖܚܬ,Ytechnicalnon-binding@wtechnicalwaseditorial@;0_‚(@‚A@‚B@‚H@p‚S@d‚j@‚t@‚@‚@Ã"`@Ã%@`0@?‚"@‚'@‚7@`‚:@‚A@‚E@‚V@>‚a@t‚e@‚s@Ä23@ÄJR@a5.1.5@M5.6.1@5.8.2@D6.2.1@ 6.3.3@7.3.11.1@g7.4.12.1.1@8.3.2@8.5.2.5@annexa-1@b0x00000001@Z1addtableofcontentsassectiontitle@1oneormoretlvspecificparameters@11.0@17@r2rejected@20@21-06-0xxx-00-0000-i@add3gpp2after3gpp@Fan@*WfWkWicmedia-dependentۼWAWmedia-independentmedia-specificWWmedium7WmeetingܕWWmentionW3WHW?WWW"Wmentionthattheframeworksupportsuseofeitherl2orl3m3Vmentionthattheinformationservermaybepresenteitherlo"VmentionedWWW,WLWMW|WވWYWmWWmentions WoWmergedKW`WmerleyWmesage܅WmessageiWۉWۋWWuWyWzW{WW W"W#W$W2WbWcWdWeWWWWWWWWWWWIWrW}W}W$W+W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W"WOWiW޳WW"WSWߑWWmessagetooWmethodۈW(W\WW,_‚ۃa‚܃YZlnᢃᣃ‚G[ݜ‚O_A‚PۅbʃB‚Q]d‚R^?ଃCD‚ST_`ޖmE‚UF‚VGH‚Wcde‚fۍېa‚҃[˃ᙃᧃ‚уLM̃̓΃IJሃ‚I5K‚݇k‚ی‚ރfgc݈Lm‚ۃhd‚i‚hjkMooPD`۠pۢƒӃ)p۩T%JW K‚!2ۄ܃ OM4^technicalhWiWlWpWsWvWwWۀWۃWۄWۅWۉWۋWێWېWۓW۔WەWۛW۪W۫W۳W۴W۶WۼW۽WWWWWWWWWWWWWWWWWW#W$W)W,W-W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W?W@WAWBWCWFWHWJWKWLWMWOWRWSWTWUWVWWWXWYWZW\W`WbWcWdWeWhWkWmWnWqWsW|W܂WbreplaceafterupperlayerentitiesmakeshandoverdecisionwfVreplacealloccurencesofjust802.21byieee802.21consistܧVreplacealsoknowaslowerlayerswithalsoknownaslowerl6VreplacebothwitheitherۛVreplacebythisprimitiveisusedbyupperlayersVreplacebytesbyoctetsinentiredraftVreplaceconceptualabstractiondescribingtheinformationtr5Vreplacecurrentlinkactionvaluesbythevaluesdefinedin8.6VreplacedeliversthismessagetothemihfwithdeliversthisoVreplacedifferententitiesmayrregisterwithwithdifferentrVreplacefacilitieswithamorecleartermۢVreplacefig4Vreplacefigure21withsection2of21-06-0460-02-0000-bschvVreplacefigure23commonmihfframeformatwithfigure23miqVreplacefurtherdeliverwithforwardqVreplaceinterfaceswithaccesstechnologies!V!VqVreplaceinterfaceswithaccesstechnologies!V!Vwbprovide@provided@ qos@^radio@rdf/xml@reason@&refer@references@1real@&refer@removemihhandoverinitiatemihhandoverpreparemihhandov@removemihnetworkaddressinformationfromtable4@Rremovetable22fromline41page127toline8page128@ rephreasethetwosentencesasfollowsinanycasethemihf@replaceshalldefinewithdefines@represented@resume@retrieved@#sap@~seetheproposal21-06-0631-00-0000-pforamendmentoflink@"sion@sory@spec@Rstation's@\suggestednewlinkiden@tcp@Gtechspecificparamete@ytext@the@Etheaccesstoinformationshouldbefast@thecreationthereinofanewentitytoanewentitycreatedۚthefirststepistore-organizetheiesintoatreeormult@ themselves@theymusteitherbemergedintooneoroneofthemberemove@{ kthisOW\WpWrWsWuWvWwWxWyWzW{W~WWWWWWWWWWWWWWvW}WWWWWWWWthishasbeenbroughtupmanytimesinpastaswellthevaluvVthisisarepetitionplseecomment345sVthisisnotthecorrectflowspecificationshouldhaveielipVthisisnottruesinceseveralplacesinthissectionwetal#VthismakesthefigureveyconfusingmaybeusetwosepartaefVVVVcbaddanotesayingthathandoverisalsoreferredtoashando)Vaddanoteunlessotherwisenotedmediareferstomethod/modVaddaparametertomihcapabilitydiscoveryresponse[VaddaperiodtothesentenceޒVaddasentenceafterline65Vaddasentenceatendofparagraphadditionallyoralternati۶VaddadditionaleventcodesbVaddannexestotheendoftocVaddanotherparameterlinktypeaVVVaddcallflowsasdescribedindcn21-06-0622-00-0000VaddclarificationintextthatallreferencepointsarewithVaddclarificationtotextVaddcorrectreferenceVadddefinitionofhandoff/handoverVadddiscussionabouttherelationshipormappingbetweenmihDVaddexplanatorytextVaddflowdiagrams/usecasesandexplanatorytexttoclearlyVaddfollowinginformationelementintable6informationele8VaddfurtherclarificationtothetextVVrlyܴVܴV;bparametertypeGWlWparamtypeGWlWparentheses$Wparenthetical/Wparsing'WpartAWQWpW۳WWIWWW'W4W5WpWtW|WWWWWparticularAW,WܾWIW'WpartnersWpartsW'WpassesOWPWQWRWSWTWUWVWWWfWpathxWpatternWW/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/WVW WWtWpereWvWܾWclengthoftypeielistofnetworksshouldbevariabletVlengthsWlessWVWlets*WletterWlevelܬWWleverage<WliaisonWliesWlevelۈWܬWleverage݂WliaisonWliesWWlevelۈWܬWleverage݂WliaisonWliesWWWlineKWۦWWWWWWWWW-WkWWWlinesܬWWlink&W'WCWDWFWGWHWIWJWLWMWOWPWQWRWSWTWUWVWWWcWdWeWfWۄWۅWۉWێWېWWWWWWWWW-W8W9W=W@WJWQWRWSWYWZW[W\W`WeWgWhWiWlW܂W܃W܈WܐWܝWܡWܫWܰWܲWܳWWWWWWWWWWW WlinkconfigurethresholdsaddsinrinadditiontosignalstrVlinkhandoverimminentmayV)bofferedAW6WofflineWoftencWnWokWold W"W#WWoldlinkactionۃWoldlinkidentifiergWWon WAWOWPWQWTWUWVWcWfWiWpWېWۮWWhW܁W܅WܡWܬWܾWW W)W,W0WIWfWWW W"W$W%W.W>WYWއWWWnWtWWWWWWWWWWWWWWWlWuW|W}WWWWWWon-demandrW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WW<W=W]W(vbtocWWtocolpWxWtogether݃WtopZW>WsWtotalݗWWtoward۠W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W?WtypeAWJWLWtypes?WAWtypicallyAWunderRWunnecessary/misplace WupOWuponWWupper"W*WLWMWQWSWWWuseUWusedVWWWuser,W-W.WAWLWOWPWQWRWSWTWUWVWWWusers-Wutilize"WvalueJWXWvaluesMWvariousW'W?Wvertical?WAWvia#Wvice#WvpnAWwayAWwell WAWwhatWLWwhenFWGWLWOWVWwhether-WNWwhich-WFWGWOWPWQWRWSWTWUWVWWWwireless!Wwish-Wwith*W-WWWwithin?Wwlan?Wwould.Wxml#Wc0-6W1W!WSW1tableofcontentssectiontitlemissingVconlyLWOWPWQWRWSWTWUWVWWWcWdWiWۄWW'W1W[W|W܄WܫWܬWWݎW>WBW|WވWޖWnWtWuWWWWWWWWWWWWWWWWWWWW$W1W5WUWkWWWWWWWWonlyshow4primitivesBVontainedܬWopaqueWopcodeWWopenWWoperateWoperatesWWWW W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W"WqWsWWۊWWoutsideWoverW-WoverkilljWkWmWnWoWzW{W|W}W~WہW ~ENada, Golmie, Member^Technical, Non-binding_41bBMake changes to the draft according to contribution 21-06-0614-00.cThe definitions given for the MIH_Handover_XXX primitives (including initiate, prepare, commit, complete) are confusing. Refer to contribution 21-06-0614-00 for an in-depth discussion of the problem. d298g2333{a) awaiting resolution 2006/09/21e added but rather introduced and providedd286g2247{a) awaiting resolution 2006/09/15 2006/04/28ENada, Golmie, Member^Technical, Non-binding_41bBMake changes to the draft according to contribution 21-06-0614-00.cThe definitions given for the MIH_Handover_XXX primitives (including initiate, prepare, commit, complete) are confusing. Refer to contribution 21-06-0614-00 for an in-depth discussion of the problem. d298g2333{a) awaiting resolution 2006/09/152006/08/29EPeretzFFeder^Technical, Non-binding_41`1b>Remove until Appenidx inlcudes such handover command scenariosDB mbA  33  Z  33[  ^  )ci  s  )cu  x  )c    )c    )c    )c    )c    )c&)c'  )c^Ãe@RÃeSÃf _Ãf0`Ãf`TÃfUÃgVÃg@WÃg`cÃgpdÃgeÃgۍÃhaÃh fÃh0ېÃj0IÃq0یÃq@Ãq`ÃqfÃr@ÃrPgÃr`ۃÃrphÃriÃs jÃs@hÃsPkÃsۄÃslÃsgÃt0mÃtۋÃt܎ÃvoÃwiÃw`lÃwܖÃxܕÃxpÃxpÃy0qÃy`ÃyrÃzsÃzPtÃzrÃzÃ@vÃPwÃێÃxÃ۔Ã`ܑÃpÃܒÃPܓÃptÃà uÃpܔà vO cAConsider the sentence "A local MIH Get Status command causes the specified link to issue a Link Get Status command to get the information on the status of hte links." The link cannot issue a Link Get Status command and this command does not exist anywhere else in the document.d604g2268wAccepted{k) done 2006/09/21EParkFSoohongGMember^Technical, Binding_62`7a 6.3.4.3.6cJPlease refer to the #21-06-0602-00-0000_PoA_Capability_Prefix_Availabilityd476g2244wAccepted{k) done 2006/09/21 2006/04/207EMathieuFPERESSEGObserver^ Editorial_78`7a7.3.14cLink_Parameters_Change should be renamed Link_Parameters_Report (to match its MIH counterpart MIH_Link_Parameters_Report) or MIH_Link_Parameters_ Report should be renamed MIH_Link_Parameters_Change ... d549g2247{k) done 2006/09/21 2006/04/30EMathieuFPERESSEGObserver^ Editorial_86`64a 7.4.5.1.1 7.4.5.1.1 7.4.5.1.1 7.4.5.1.1'blinesqW4WSWܬWWW0Wlink WAWCWDWGWIWJWLWOWPWQWRWSWTWUWVWWWcWeWۅWۉWېWەWۣW8WRWSWTWUWVWWW]W`WiWkWlWmW܂W܃W܄W܈WܡWܫWWWWW+WݍWݛWݺWWWWWWWWW W#W2W4W5WaWlW5W6W[WlWmWnWtWWWWWWWWWWWWWWWWWW W%W4W7WZWzW|WWWWWWWWWWWWWWWWWWWWWWWWWW"W"W"W"W"W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WW0  bAChange text to: ... MIH Users that need to receive event notifications shall register themselves with the MIH Function. After registration, the MIH Users may specify a list of events for which they wish to receive notifications from the MIH Function. For an HIH event that can originate both locally and remotely, an MIH user may specify whether it is registering for the local event only, remote event only, or both. @A>  33    )c>cAIt should be made clear that when a MIH user registers for a specific MIH event, it should be able to register for the local or remote MIH event only. There is no need to force every MIH user to receiver both. @A  33d277g2255va) awaiting resolution 2006/09/18MarkedEQiaobingFXieGMember^Technical, Binding_37`29a6.1.5.2b266g2255{a) awaiting resolution 2006/08/21 2006/04/2814cfully*WEWfuncionWfunctionLWOWPWQWRWSWTWUWVWWWcWdWfWlWۉWۋWېW۪W7WܫW{WWWWW W W"W%W'W,W4W5W1W5WjWnW|WWWWW%W=W|W}W~WWWWWWWWfunction/operationWfunctionalities:W:W:W:W:WW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W"W#W$W%W&WMWNWOWPWQWRWSWTWUWVWWWwaccepted#%'(),-./28@ACNY[\_ktv|}~ހނބޅކއލޖ1256>?ૃу nᦃᵃṃÃ˃΃accepted-clarified>Baccepted-modified"*IJQRSTUVWZfglۅۓ۔ە۪ۛ۫۳ԃ)-1HRܬܾܰۃ݃ރ 0{}݃ݒݜ vacceptedZWzW>WW4WtWWacceptedaspercontribution641>Vaccess*W۫W۳WWWܬWܾW0WW"WWWW"W?WjWWaccordingly`WaccurateWachieve"Wack۔Wacknowledgement۔WWacrossەWݓWjWactݓWWactionۃWactionsQWTWacts#WactualWactuallyW?WVWWadzWW!WaddZWۋWێWWWWRW`WܬW3W݃WaWdWWWWW W WWW&W>WjWWWWWWaddacommentinlinkuptothateffectVaddanewlineafterline583VaddastatementVaddanotherflowdiagramforthistheorderingofchoicesmaۋVaddcontribution21-06-0728-01-0000-squeryexampleinannexVadddescriptionofparametersinthisprimitivechangegetstVx^boccur^WWWoccurencesܧWoccurredRWoccurs5WܟW.WoctectlWocteswWoctetJWۉWwWWݗWހWނWWLW"W"W"W"W"W"WcWwWWݗWofWWWWW W!W#W,W-W.W?WAWFWGWHWIWJWLWMWPWQWSWTWVWWWZW[W\W]W_W`WbWcWdWfWiWjWkWlWmWnWpWsWuWvWwWxWۂWۅWۆWۇWۉWېWەWۖWۗWۘWۚW۞W۠WۦWۧW۪W۬W۳W۴W۶W۸WۻW۽W۾WWWWWWWWWWWWWWWWWWWW/W2W3W4W5W:W<W=W@WFWHWJWKWLWQWRWSWTWUWVWWWXW\W_W`WcWdWhWiWjWkWlWmWqWsWvWwW'albertޖ᥃ᦃaramakiۓasou۔athalyeەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫ۮۯ۰۱۲۳۴۶۹ۺۻۼ۽ۿƒÃăƃǃȃʃ˃̃̓Ѓуԃ؃كۃ܃ރࠃࡃࢃchengࣃःृă  !"#$%&'()*+gomie23groetingܑܒܓܔܕܖܗܘܙܚLycdeifnitionWdelaykWdelays WdeleteیWdeleted2WdeletingWdeliver"W$W>W>W>W>W>WWdeleted2WdeletingWWdeliver"W$W>W>WaWdeliversoWdemandۊWdenverWdepecting!WdependېWdependence)WdependencyۓWWdependentDWܯW WݴWWdependingW+W6WWdepictedܔWdeployedܭWdeploymentWWܭW݂WdeprecatedWderegistereWWderegistrationWWdescribe'WeWWWdescribed+W_WjWkWmWnWoWzW{W|W}W~WہWۊWیW{WݒWݓWݛWݽWWWWdescribingܟWdescribled݀WdescriptionjWkWmWnWoWzW{W|W}W~WہWۆWWW0W=W@WPW܅WܷWܹWW݄WݗWݾWWWWdescriptionsNWdescriptiveWWdesign#W . vtext4W5WnW\WfWWWWWWWWWWWWWWWWWWWWW=W>W?WtWWWWWWWWWWWthanWWthatRWTW۔WەW۳WWWWݓWWnWjWWWWWWW W WWWtWWWWWWWWWthatisusefulinformationVthe"W)W*WCWKWQWRWSWTWUWZWlWۉWۋWێW۔W۪W۳WWWWWHW`WܬWܾWWWWW0W3W{W݃WݓWݓWݓWݓWݓWݓWݓWݓWrelengthcolumnintable-6isbeingdroppedasper%Vthegroupfeelstheoriginaltextisbetterthanthesuggest7VtheieshouldrepresenttheqoscapabilitiesoftheaccessnVthelanguageistoostronginsomecasesmayneedtochange{V SbcA31. This is a link layer indication which should only be received by the MIH function, not by any upper layer. 2. To pass this notification to an MIH user, need to add "MIH Link Detected" event to MIH_SAP, which is not currently defined. An alternative is to disallow passing this link event to an MIH user.3d548g2296vA@MIH Function receives this event from link layer. MIH Function then passes this notification to the MIH User(s) which have registered for this notification. The MIH User(s), Upper layers includeing MIH Function itself, may discover additional properties of the link before selecting it for establishing connectivity.@@A  )c  TT    TT  )c    )c  wAccepted-Modified{k) done 2006/09/21 2006/04/24TEQiaobingFXieGMember^Technical, Binding_78`53a7.3.14.3b7.3.14.3b19_brelated WOWRWTWiW"W#W$W%WkWpWWrelationwWWWrelationshipDWWrelationship/mapping[WrelationshipsZWsWrelationshipsbetweeninformationelementsmustbeaddedtoZVsVrelaysWreleaseW W&Wrelevant(W,WpWWreliableeWreliablyWrely WWremainingwWݗW WW1WremediesYWWremedyZWsWremote WiWpWW7WKWzWWݎW WW#W|W1W2W7WuWWWWremotemihfreturnsthenecessaryinformationtothenmviaVremotely1WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWQW[W`WqWuWzbnmWnms8WWWnoSWYW܋WW W6WWWWW8W>WWnomihcommandlocalremoteremotedirectiondescriptionVnoprimitivesservicecategorydescriptionSVSVSVdescriptionSVSVcriptionSVSVdiagramhorizontallyrVstringٿWW WWWWstructureWWWsttausWsubjectڡWsublayersWsubmissionWsubnet+WsubscribedٮWsubsectionWWsubsectionof6.3.8shouldbedeletedVsubsequent WsuccessAWW WWsuccessfulWWsuchW WWW-W0WiWلWٓWWWڛWbmostgWW&WWW>WmoveAW`WWWQW>WXWpWWWW<WWmoveandmergethefirstparagraphof6.3.5into6.3.1intro`Vmovesection5.3toannexasaninformationalguidelineforVmovesection5.6.2.1intothemedia-dependentsapsection5.Vmovesection6.3.4tobebeforethecurrentsection6.3.3pVmovetable13csapprimitivestoannex>VmovetabletoinformativeannexVmovedWmovementWmsbݗWmsc>WmuchVWmulti-technologyXWmulticast/broascastWmultihopݓWmultiple܁WܤWWtWvW܁WܤWWWtihopݓWmultiple_WbW܁WܤWWWWWWWWWWWWWWWWWWW 33M 33   33 fb21-06-0xxx-00-0000-izW21-06-0xxx-linkAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWYW[W]W^W_W`WaWbWcW21-06-500-02-0000-neۋW21-06-606-00-0000WWW22ܬWހWWWW23sWނWWWqWW23-43qW24wWݿWW=WW245܄W25ܑWW26DWEWHW/WW/W/W/W/W/W/W/W/W/WDWEWHW/W/WEWHW/W/W/W/WDWEWHW/W/WDWEWHW/W/WDWEWHW/W/WW33ۉWcW34ۉW35ۉW35-40W36ۉW37-43`W3753:W38ۮW=W38-49=W39=W3gpp۽W۾WYW3gpp/3gpp2W3gpp2&W'W4/W:WjWmW{W}WۉWەWW%W&W)W=WDWEWHWRWTWUWVWWWXWcW|WܒWܚWܮWcoverload@page@paragraph@hpart@particular@Xperhaps@place@please@portion@Ppresence@7previous@primitives@protocols@provide@proxy@questionable@Hrate@reason@receives@referencetointernet-draftshouldberemoved@mregistration@rejected@relationships@+remotemihfreturnsthenecessaryinformationviaappropriat@removesfromthewordsupportsinthelinethatquotesothe@sremoveimplicationofcapabilityuniquet@@ionsremoveimplicationofcapabilityuniquet@Yswitch@syntaxerrorinnetworksecurityandqualityofsecuritycap@Dsyntaxerrorinthisisusedtorespondtheresult@4systemmanagementhasbeenintroducedasaserviceherehowe@.take@?textneedsimprovement@that@that's@the$\gnmentofistoanyinformationelementshouldnotb@# 4TbAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Parameter Report" event. The MIH User(s) Higher layers may take different actions on this notification. If parameters related to link quality cross a certain threshold then that link may need to be evaluated for handing over current connections. The MIH Function may collectively evaluate different parameters and give appropriate indicationsB; to higher layers regarding suitability of different links.)@Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d555g2297vted" event to MIH_SAP, which is not currently defined. An alternative is to disallow passing this link event to an MIH user.ternative is to disallow passing this link event to an MIH user.pcneededWW݉WpWWWWWW@WPWQWRWSWTWXW_WcWdWeWfWkWneedlesslyۿWWW8W9W;W<W=W>W?W@WAWBWCW}WوW٢W٤W٥W٩WWWWW W$W&W-WUWVWoWuWڦWWWW WWTf 2006/04/29kE1.55F 2002-04-15A1.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 and g2367 2006/04/28|bconsiderationRWܾWconsideredWWW<Wconsistency۝WۭW.WjWconsistentWAWBWhWWWWconsistentlyۜWWܧWWconsistentlyusethewordroamingVconsistsW'WuWconsolidatedܤWconstantlyAWconstitute,WcontactrWcontain}WބWxWzWWcontainedW:WހWނWcontainerYWcontainingHWjWmWcontains}WނWxWzWcontentݾWݿWcontentsWlWWWWWcontextW/W|WWWcontextualtWvWcontinueWcontinuityAWAWAWual_WbWcontinue1WcontinuityAWAW;Wcontextual_WbWcontinue1WcontinuityAWAWue1WcontinuityAWAW;Wcontextual_WbWcontinue1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1WUz 9sanjeevshikichishinkichiVshuWWWWWWWWWWWWWWWWsactioniddoesGVtransactionsMWPWVWZWtransfer[WtransmitWWWiesWtriggerxWtwo W WYWٴWٷWWtype6WEWنWٱWٴWٵWٶWٷWٺWWWWtypesٴWٷWWWtypographicalSWtypographicalerrorSVumtspWٱWٷWunavailableWunclear^WsWٍWٕWuncleardefinition^Vunclearfunction/operationinboxmiisreportavailabilityٍVunderstand0WِWٺWunderstandingWuniformWunlikelyقWunrealisticWunspportedWupsWُWup-to-dateqWupdatedٲWٵWٶWupperWWWWWWW W!W"W#W$W%W&W'W(W)W*W2W3W4W5W8W9W;W<W=W>W?W@WAWBWCWhWٮW ېbCrameters are as follows: Link_Event_Discover.confirm Link_Capability_Discover.confirm( SupportedEventList SupportedCommandList ) Name Type Valid Range Description SupportedEventList Set of Event IDs Set of valid link events List of link layerD events supported by the link layer SupportedCommandList Set of Command IDs Set of valid link command List of link layer commands supported by the link layer 7.3.2.3 When generated This primitive is generated in response to a Link_Event_Discover.request Link_Capability_Discover.request primitive. 7.3.2.4 Effect on receipt The recipient may examine the returned event and command list and learn about link layer capability @ Wd637g2252 2+#EPeretzFFeder_40`48a Figure 18on-binding_111`12bEither remove the mention of "802.3 Ethernet" in the label of the protocol stack in Figure 23 or revise the caption of Figure 23 to read:"L2 Data Frame Packet Format in 802.3 Ethernet".cFigure 23 on page 111 is titled: "Common MIHF Frame Format" although the label on the leftmost protocol stack is labeled "MIHF Frame Format for 802.3 Ethernet". d687g2302vIremove figure entirely and enhance this section for other L2's we supportyAssigned as issue number 30{a) awaiting resolution 2006/09/19Marked#EPeretzFFeder_40`48a Figure 18n page 111 is titled: "Common MIHF Frame Format" although the label on the leftmost protocol stack is labeled "MIHF Frame Format for 802.3 Ethernet". d687g2302vIremove figure entirely and enhance this section for other L2's we supportyAssigned as issue number 30{a) awaiting resolution 2006/09/19Marked#EPeretzFFeder_40`48a Figure 18ݚ F?bAChange text to: ... Media Independent Information Service includes support for various Information Elements (IEs). Information Elements provide information that is essential for a handover module to make intelligent handover decision. Figure shows a high level description of scenarios that distinguish between two different types of mobility. - Horizontal handovers: A horizontal handover is performed by switching between different points of attachment of the same access network. For exB9ample, switching between different APs within the 802.11 network (e.g. Inter ESS or inter subnet). - Vertical handovers: A vertical handover is a handover from one access network to another access network. For example switching between different PoAs across heterogeneous technologies (e.g. from WLAN to GPRS). '@ologies (e.g. from WLAN to GPRS). '@heterogeneous technologies (e.g. from WLAN to GPRS). '@g2229 2006/05/14 2006/04/28{ IbA 33  Z  33[  ^  )ci  s  )cu  x  )c    )c    )c    )c    )c    )c&)c'  )crks.cCRemove limitations, remove implication of capability unique to GSM. 2006/05/01ڛEFarrokhFKhatibiGMember^ Editorial_43`5-6a6.3.1bQRemove "the mobile node may move across different access networks. In such cases"cRestating the obvious 2006/05/01ڜEFarrokhFKhatibiGMember^ Editorial_44`48a6.3.2bChange to "cdma2000-HRPD"cUnfamiliar acronym 2006/05/01ڝEFarrokhFKhatibiGMember^Technical, Non-binding_44`38-49a6.3.2g3185 2006/04/29cords" button in Create and g2368 2006/04/28cnewlinkidentifierKWRWSWTWbWfWnewmacmobilenodeKWbWnewpoamacfWnewpoamacisnotneededifitispartofnewlinkidentifierfVnext*WnihoWnmWWWWWWWWWW W>W?WDWEWMW\WcWjWܐWܓWܖWܘWܙWܚWWWWWWW WW W2W:WCWeW}W݂WݥWnoformatforthesynchinformationisdefinednorareanyrVnoguidanceindraftonhowthemediaindependentinformatio}VnoieforperformanceofaccessnetworkshasbeendefinedVVnomentionaboutwhetherhigherlayerammendmentsarerequirVnoproperexampleisgivenfortlvreques/responseܙVnospaceforexpansionofmihtlvencodingsVnodeWWۉWۏWۦW W.W3W4WܝWܡW+WwW{W|WݏWnode's{WnodesW:WW+WWfWiWjWbblerGWIWlWmWblock,W~bodiesWbold:WbooleanWWbothAWۛW۶W[WtWWbottom>Wbound:W:WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWܵWbufferUWbufferingVWbuffersUWbutۜWW܋W݊Wby"W,W?WAWLWMWRW_WcWdWiWpWxWېW۳W۶WWWWWWW#W*WFWGTWVWXWYWZW\WcWkWzW{WܟWܡWܣWܥWܧWܾWWWWWWW0WPWUWYW_W`W݂W݃WݗWݙWWWWWWWWWW WWWWWW W!W#W%W+W9W=W^WW`bfirstJW`WeW۪WIWwWW0WMWݗWW8WtWvWWlWWWWfirsttore-organizetheiesintoatreeormultipletreessvVbVbVbVbVsbVfix%W&W۠W݅W݆W݇W݉WݭWޣWޤWfixit݅V݆V݇V݉VݭVfixtheinconsistency%V&VޣVޤVfixtypotowardtheendoflineall۠VfixedsWܑW'W^WflagۂWflexibilityAW_WiW޿WflexibleAW޿WflowܴWWKWyWzWWBWQWflows)WWKWflushUWfocusXWYWfollowedWݙWfollowing*W_WjWkWmWnWuWvWwWxWەWW3W=WHWRWSWTWUWVWWWXW\WcWdWmWܚWܬWܹW|W݊WWW W2W7WIWފWޔWިWfollows WJWXWۂWېWWCWYW\WܤW)W0WlWޞWWVguptaܛܟܠܡܣܤܥܧܨܫܬܭܱܾܰܵăǃՃփ׃؃كڃۃ܃݃ރ߃ᴃᵃᾃȃhan߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳߳ hiranohuoܮikedaTUVjiangۍېkhatibi !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxLhcdThe valid range of Old Link actions is not consistent with the list on page 125 (section 8.4.2.13). d616g2293psuperceded by 615vas defined in section 8.4.2.13wAccepted{l) none needed 2006/09/21iENada, Golmie, Member^ Editorial_90`34bAReplace "control the behavior of lower layer, for example, to set some feature of the driver of a specific link." with "control the behavior of lower layers."@Af  33(  33.  33  33  33fcASyntax error and confusing sentence in "control the behavior of lower layer, for example, to set some feature of the driver of a specific link."@A>  33F  33K  33>d619g2294{k) done 2006/09/21jENada, Golmie, Member^ Editorial_91`10_91`10_91`10.4.2.13 on page 125. Add text as per section 8.4.2.13 on page 125, Binding_84`15bDnada2W3W4W5W6W7W8W:W;W<WAWBWCWDWEWGWHWIWNWPWQWRWSWTWUWVWWWYWZW[W]W^W_W`WaWfWgWhWiWjWkWlWmWoWpWrWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎WWWWWWWWWWWWWWWWWWWWWWWfghijklmnopqrstuvwxyz{|}~ۀہsanjeevەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱۲۳۴۵۶۷۸۹ۺۻۼ۽۾ۿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃$ gۉcGd902g2214vDChange the primitive definition and the protocol definition as well.wAccepted{k) done 2006/09/21 2006-04-07ۋE HongchengFZhuangGObserver^Technical, Non-binding_94`34a 7.4.10.1.2bAUpdate according to submitted document: 21-06-500-02-0000-Network_select.ppt replace with: MIH_Handover_Initiate.request ( SourceIdentifier, DestinationIdentifier, CurrentLinkIdentifier, TransportLayer SuggestedNewLinkList, SuggestedNewPoAList, HandoverMode, CurrentLinkAction, QueryResourceList ) MIH_Handover_Initiate.response ( SourceIdentifier, DestinationIdentifier, CurrentLinkIdentifier, TransportLayer, HandoverAck PreferredLinkIdentifierList, PreferedPoAIdentifierList, AbortReason ) @Af 33  3333 33  3333 33fcfcsage from upper layer, such as MIH_Configure_thresholds, it needs to know which access network interface it should conduct. "cAThis primitive is delivered from MIH Function on old PoA to another MIH Function on new PoA in order to discover mobile nodes network address related information before handover. Upon reception of this message, the MIHF on new PoA may either interact with upper layer to achieve enough information or further deliver this message to the MIHF in the network, e.g Access Router with MIHF which may have enough information on this message. This may also trigger the network entity, e.g, Access RoButer or Foreign Agent to send out Mobility related messages directly to the mobile node. Change text, change "new" to "target" and old" to "serving". Consistent with other SDOs d651g2261v 33x  {  33    336 =  @  33A 33wAccepted-Modified 2006/08/11#EPeretzFFeder e"bAThis primitive is delivered from MIH Function on old serving PoA to another MIH Function on target new PoA in order to discover mobile nodes network address related information before handover. Upon reception of this message, the MIHF on target new PoA may either interact with upper layer to achieve enough information or further deliver this message to the MIHF in the network, e.g Access Router with MIHF which may have enough information on this message. This may also trigger the network Bnentity, e.g, Access Router or Foreign Agent to send out Mobility related messages directly to the mobile node.\@A   331  4  =  33\  c  f  33      33  33cl, Binding_103`33b2lKPbAmend tail end of sentence as "GSM, CDMA, or any other cellular network, whether by means of request/response signaling, or information that is specifically or implicitly broadcast over those cellualar networks.cCRemove limitations, remove implication of capability unique to GSM.d337wAccepted{k) done 2006/09/21MarkedQEFarrokhFKhatibiGMember^ Editorial_43`5-6a6.3.1bQRemove "the mobile node may move across different access networks. In such cases"cRestating the obviousd338{k) done 2006/08/29 REFarrokhFKhatibiGMember^Technical (was Editorial)_44`48a6.3.2bChange to "cdma2000-HRPD"cUnfamiliar acronymd351{a) awaiting resolution 2006/08/29 TEFarrokhFKhatibiGMember^ Editorial_45`20a6.3.2b"defined", not "defied"cSpellingd371{l) none needed 2006/08/29 ^EFarrokhFKhatibiGMember^ Editorial_60`12a6.3.8.1bRemove sentence "OWL is ".cSuperfluous sentenced467{k) done/14! vlistۓWW-WWqWWWWWWWlistofnetworksismoreappropriateVlistedWlists۳WWlocal۳W4W5WWjWWWWW#Wlocal/remoteWWNWWlossWlotWlowWlowerW4W5WWlower-layer*WlsapjWm4WmacWWW?WmacnewaccessrouterdWmacnewpoaWmacoldaccessrouterdWmailWmaintained۳WmakeW WW,WWWmakemihfunctionhorizontalinfigure1,VmakesimilarchangesthroughoutthedocumentVmaking*W?Wmanagement4W5W#WWmandateWmandatoryݜWWmanyZWWWmappingWmatch۔WmayQWRWSWTWۋWۛW۳WWW1W{WݜW"W*WOWWWWWWW W#W'W?WWWmeanWWWmechanismW"WmechanismsC)chandover"W?W@WfWۃWۅWۋWW-W1W:WfW܉WܠWܤWWݍWݐW"W#W*W.WAWnW1W6W\W]W^W_W`WaWbWcWdWeWwWxWyWzW{W~WWWWWWWWWWWWWW8W<W?WiWtW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW{|_EQiaobingFXieGMember^Technical, Binding_99`24a7.4.12bARemove entire section 7.4.12.@A  33cA"MIH Handover Commit" is improper for 802.21 scope. The functionality represented by this primitive is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d645g2263vby comment 495w Superceded 2006/09/21 2006/04/24Marked`EQiaobingFXieGMember^Technical, Binding_101`36a7.4.13bARemove entire section 7.4.13.@A  33cA"MIH Handover Complete" is improper for 802.21 scope. The functionality represented by this primitive is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d648g2264vby comment 495w Superceded 2006/08/29 2006/04/24aEQiaobingFXieGMember^Technical, Bindingg/ dÃT0ÃT@ÃTP-ÃT`ÃTpܾÃTÃT)ÃT1ÃU ÃU IÃU0`ÃU@tÃUPuÃU`ÃUpÃUÃUÃUÃV@ÃV vÃV0ÃV@.ÃVPÃV`ÃVp/ÃVÃVÃV:ÃWjÃW ÃW0 ÃW@ÃWPݚÃW`0ÃWpÃW^ÃWvÃWÃXÃX 1ÃX0zÃX@BÃXPÃX`ÃXpÃXOÃXÃXÃYÃY `ÃY0CÃY@DÃYPÃY`DÃYpCÃYÃYNÃYPÃZݛÃZ lÃZ0ÃZ@EÃZPFÃZ`0ÃZp;ÃZGÃZHÃZSÃaEÃa mÃa0RÃa@LÃaPQÃa`TÃapIÃaUÃayÃaVÃbWÃb Ãb0XÃb@aÃbPzÃb`{ÃbpÃb_ÃbYÃbÃcFÃc ZÃc03Ãc@MÃcPbÃc`GÃcpÃcݜÃc[ÃcÃdÃd OÃd0Ãd@ݝÃdPPÃd`ۅÃdp\ÃdݞÃddÃd]ÃeQÃe ݟÃe0^Ãe@d ېbA 33  33" 33#  L 333  33O 33P  s 33  33 33  33 33   2 33  33 33  33 33   33  33   33Beive link layer event notifications and learn about which link layer command the low layer can support. 7.3.1.4 Effect on receipt The recipient responds immediately with Link_Event_Discover.confirm Link_Capability_Discover.confirm primitive. 7.3.2 Link_Event_Discover.confirm Link_Capability_Discover.confirm 7.3.2.1 Function This primitive returns the result of the query to discover link layer events capability request 7.3.2.2 Semantics of service primitive The primitive paH lbfeGMember^Technical, Binding_107`15a 7.4.15.1.4bALChange the text to: The recipient will forward the query in an MIH message to the designated MIIS server (or a proxy function of MIIS). The MIIS server tries to interpret the query request and retrieve the specified information. Once the information is retrieved the recipient responds with MIH_Get_Information.response primitive.L@Af 33  $  )c  fcAThe recipient of the primitive is the MIH Function, which will not try to interpret the query and do the retrieve. That's the job of the MIIS server.@A  33d665g2321vf the MIIS server.@A  33d665g2321vRc Rc#M#^non-bindingۃWۄWۉWۋWێWېWەW۪W۫WWW#W$W)W-W1WAWBWZW`WhWmW|WܛWܰW+W3WAWLWkWzWݵWݽWW W WWW WkWކWއW1W2W5W6W>WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW#W'W)W*W-W7W8W>W?WiWoWpWqWrWsWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW+W-W0W2W3W6W9W;W<W=W>W?W@WAWBWCWFWPW`WfWkWقWُWِW٤W٨WٮWٷWWWWwvaddifavailabletothewordoptionalintablefornewpoadVaddlinktypetoallmihlinkindicationsaVjotherۃۄ-binding_157`44a8.5.2bAadd LinkType IE to MIH_Configure_thresholds and MIH_Event_register, MIH_Event_Deregister primitives according to 21-06-0632-00-0000-LinkType_for_MIH_Configure_Threshold and Event.ppt. Name Type(1 octet) Length(1 octet) Value LinkType 31 Variable Identifier of link for which link was configured LinkParameter 33 2 Pramaeters for which link g3421 2006/05/01nsert "or could be maintained in an internal database by the MN".cRemove limitations 2006/05/01~ESanjeevFAthalyeGMember^ Editorial_43`4-5a6.3.1bCChange "point of attachments" to "points of attachment" or "PoA's".c Plural form 2006/05/01ESanjeevFAthalyeGMember^ Editorial_44`11a6.3.2b+Change to "may influence handover decision"c Improved grammar (verb vs. noun) 2006/05/01ـg2900~btheieeestandardshoulddefinesthepacketformatVthelengthiVthelengthdefiniteݹVthemihfunctionheaderconsistsofatwopartsonewithfix'VthemihfunctionheaderconsistsoftwopartsVthemihfunctioninthenetworkmayadvertiseitsmihcapabi}VthenorthboundprimitivegeneratedlocallyinresponseVtheoverheadinexchangeofinformationshouldbeminimizedVtheparametersoftheprimitiveareasfollowsVtheprimitiveparametersareasfollowsېVthethirdprimitiveintheflowmihgetinfoconfirmBVthevaluefieldofradiuslocation-informationݘVtheirWWthelengthvWthemWWfWxWۦW݋WCWsW|WWkWWuWxWۦWܿW݋WWCWjWjWW]WfWuWxWۦWܿW݋WWCWjWjWW]WfWuWxWۦWܿW݋WWCWjWjW߸W߸W߸W߸W߸W߸W߸W߸W߸W߸W߸W"bsectionsWWLWMWiW{WWWsecurity#WەW<WܾW1WWseeۅWۯW`WjW#WWkWWWWWWW0WWseeitemabove#Vseepage58lines1-210VseepreviouscommentۯVseerelatedcontribution21-06-0644-02-0000-mkVseetheproposal21-06-0630-00-0000-pforamendmentofmihsVseetheproposal21-06-0631-00-0000-pforamendmentoflinkۅVseethesuggestedannexa-2intheproposal21-06-0656-00-00VstingWinterfaceWqWW!WzWڎWinterfacesWWWkW{WintermediateAWinternal}WلWinternally٢Winternet-Winterpretation_WintervalWWinto W W WWuWٴWGWڡWintra-roaming^Wintra-roamingshouldbedefinedthewhole2ndsentenceinth^Vintra-technology-WHWintroducedIWintroductionوWinvokedVWfhWlearnediWsEjdoesZWvWWdoesthisinterferewithsessionidifweestablishasessioVdoesn'tWdraft?WdstWeܾWWeachvWelementWtWend-to-endWentityWenumerator|WestablishWetcܾWWeven"WZWeventhecurrentschemadiagramisnotcorrectanddoesnotZVeventWeventsWexampleWWzWexplainWexplainedWWW W W W WKWflows>WforuWWWWgWformat|Wfrom>WKWfromthedoconewouldbethatlinkeventregistrationisinKVfunctionuW,WKWgeneric,WgetWgood WhandKWhandover?Whave W>WKWhelps,Whigher W,Whope,Whorizontal,Whorizontal-handover?Whowever Wi W,WidWhWidea WidentifierW Widentify WidsWWW WifaWuWWgWimho+W4ݖbmn۞WۧW۶WW#W,WWWW WW"WsWWWmnsWmobNWmobileAWVWpWۘWۜW۞WW3W4WܡWIWQWWWW W"W#W$WOWޏWtW|WW>WWWWWWWWWWmobilenodeoruserequipmentVmobile-assisted>Wmobile-assistednetwork-controlledhandover>Vmobile-controlled>W>W>WܤWܴWWIWW"W3W4W5W7WޕWުW޽W޿Wmobility-managementGWmobilitymgmtprotocolޕWmodel$WۮW,WTWUWVWWWXWcWnW݂W݃WޢWmodelaftersimilarclauseonpage17line38ۮVmodificationsSWmodifiedޗWmodifyWmodule?WܤW.WAW޽WmomentWmonthHWmoreAWPW_WqWۢW۽WWWܰWWWWWWWWNWIWXWYWށWރWEmcoperation"W*WWWWoperationsfWoperatorWWWWW<WWWWWWWWWWWWoptionalWXWWW WWoptonsܯWor-W.WDWFWGWHWIWJW_WaWiWjWkWmWnWoWwWzW{W|W}W~WہWۂWۈWۊWېW۵W۾WWWWWWWW-W.W3W9W:WCW[WcWsW܄WܝWܡWܤWܫWܬWܺWWWWWWWWWWWWW W WWWW+W2W3W;WJWWW}W~WorderۅWۆWWHWRWYWWtW{WorderingWWordinary:WoriginalWoriginate7W8WܫWotېWotheruWۂWۊWېWWWWWWW'W1WCWZWWWWWWWWbWothersWP QbAdChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Going Down" event. The MIH User(s) Higher layers may take different actions on this notification. Upper layers may prepare to initiate handovers based on the confidence level reported as part of the event.d@A 33  33  )c"  )c*  )c  TT  cjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d540g2294vAWMIH Function receives this event from link layer. MIH Function then passes this notification to the MIH User(s) which have registered for this notification. MIH User(s) Higher layers may take different actions on this notification. Upper layers may prepare to initiate handovers based on the confidence level reported as part of the event.xbisއWދWތWޏWޏWޏW---------------------------------------------------------| | TYPE_MIME_TLV | Variable | A MIME Type TLV An octet string for a MIME type to specify an XML a format | | | | of SPARQL Query Result. When this TLV is | | | | not containedC, MIME type "application/xml application/sparql-query" is | | | | used. MIME type "application/xml" shall be | | | | supported for this type of query. | |-------txie "#$()*+?@ACDGIJKLOPQRSTUVWZ^`cdefghilpqrstvwxۀWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ƒʃ̓zhuangۉۋیێێێێێێ !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ۀہۑےۓ۔ەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱cotherwiseܫWWouiWourWout"WqWsWܡW W"W%W*W>WWWWWWWWWoutsideWܛWܭWWYWWWoutstanding WoverW-WWWW W WWWiW}WWover-the-airWover/underWoverall݃WWoverheadWoverkillwWxWyWzW{W~WWWWWWWWnWoWzW{W|W}W~WہWہWہWہWہWہWہWہW`٩ G_َ0Qً@?٨P0`SٔٗٞpUuن٢\6C‚! ُ‚"٭ٹ‚#"3ٚ١‚$ {‚%*2‚&5yٜ‚'ٍɃ‚(dْ‚)$W]٘‚*DR`‚1+jٳ‚2 k‚3>‚4X٪‚5/Bٱ‚6(;‚7لهٿ‚8a‚9Z1|b1addtableofcontentsassectiontitleV1addthefollowinglinesSV1changethetypeofthenetworkaddressinformationV1createanewiewiththefollowinginformationatline38V1dividetheflowintotwoinafigurelocalandremotecomm7V1dividetheflowintotwoinafigurelocalandremoteinfozV1eitherremoveorprovidedetailsexpeciallyonall4primiV1failureܖV1ieeestd802.111999editioniso/iec8802-111999informatpV1mihgetstatuslrnetworkclientgetthestatusoflinksV1movetheconceptofhorizontalandverticalhandoverstosVV4r1vhDelete "heterogeneous interfaces" from defn of Seamless handover and replace with "Points of Attachment"wAccepted-Modified{k) done 2006/09/212ENada, Golmie, MemberFGomieGMember^ Editorial_10`0a4b`Since MIH is pronounced like "em I H", it is necessary to put the article "an" in front of "MIH"cGThe usage of "a" / "an" in front of the acronym "MIH" is inconsistent.d81g2214p,changed to "an MIH" throughout the document {k) done 2006/09/213ENada, Golmie, MemberFGomie^ Editorial_8`23bRemove the following sentence from the definition: "The mobile node may either be in close proximity of or coincide with the mobile node."cIn the definition of Mobile Node, the sentence "The mobile node may either be in close proximity of or coincide with the mobile node." is not coherent.d64g2237{k) done 2006/09/212006/08/292006/08/294ENada, Golmie, Member^ Editorial_8`29b;Remove second definition of Mobile Node at lines 29 and 30.vXwRejected 2006/09/21 2006/04/24YEQiaobingFXieGMember^Technical (was Editorial)_30`36a5.6.1bAfix the inconsistency.@A  33cAmInconsistency between Figure 12 and 5.6.1: LSAP and CS_SAP are shown in figure 12 but not mentioned in 5.6.1.m@A  33d221g2247vby comment 212w Superceded 2006/09/21 2006/04/2412ZEQiaobingFXieGMember^Technical (was Editorial)_31`3a5.6.2.1bAfix the inconsistency.@A  33cAUInconsistency between Figure 12 and 5.6.2.1: MIH_LINK_SAP is not shown in figure 12. U@A  33d228g2248vby comment 215w Superceded 2006/09/21 2006/04/24[EQiaobingFXieGMember^Technical, Binding_31`3a5.6.2.1b5.6.2.1b5.6.2.1b5.6.2.1bECT | |  EDasFSubir ^Technical, Non-binding_7`23a3b Delete "heterogeneous" . cKSeamless handover can happen between homogeneous interferfaces as well. d51g2421v>Word "heterogeneous" was deleted by another editorial comment.w Superceded{a) awaiting resolution 2006/09/21EDasFSubir ^Technical, Non-binding_8`52a3bDelete this definition c+Network Detection definition is redundant d69g2424vOKeep the definition as it relates to Network discovery and Link Detected event.wRejected{a) awaiting resolution 2006/09/21EDasFSubir^Technical, Non-binding_8`59a3bDelete the sentence cX" The POA definition is associated with an interface instead of a node" is not clear. d71g242571g242571g2425DasFSubir^Technical, Non-binding_8`59a3bDelete the sentence cX" The POA definition is associated with an interface instead of a node" is not clear. d71g242526{a) awaiting resolution 2006/08/29eva3n bcACurrent text needs improvement.@A  33d252g2254wAccepted{a) awaiting resolution 2006/09/21 2006/04/24dbe relevant to handover may originate from MAC, PHY or MIH Function either at the mobile node or at the network point of attachment. This could be due to user or mobile node mobility, state change in the environment or because of some management function on part of the network. @bAIn general handovers may be initiated either by the mobile node or by the network. Events that may initiate be relevant to handover may originate from MAC, PHY or MIH Function either at the mobile node or at the network point of attachment. This could be due to user or mobile node mobility, state change in the environment or because of some management function on part of the network. @@ESrinivasF Sreemanthula^Technical, Binding_83`1a 7.4.1.1.2d575 2006/04/26pdocument2Wdoes۽W݃Wdon'tWdoneDWZW۽WWW>BCWYWdone21-06-0705-00-0000-lintwoseparatetableforbetterrDVdone2ndpartVdonecommet482relatedchangesin21-06-0676CVdonefirstpartbutneedmoreinputonthewiredexamplesVdownۅWdraftۓW݃WdrawingszWBWCWduplicateیWeܥWݜWearlier?W݃Weasy2Weditor{Weditor'sEWeditorial;WeffectivelyݜWeither۽W;Wembedded2WendWݜWentireۓWentity۪WentriesۓWeric/mathieu݃WeventRWexactݜWexamplesWexclusionZWexistinggWexmaple-WWކWexplainedhWfacilitates۪Wfig۴WܵW}W@W2W2W2WܾWif۽WܾWinDWۓW۽WW:WܡWܾW{W݃WCWin21-06-0691-02-0000-3۽VincludedۓW)WinputWinsert۽Winserting۽Winstead:WW2cinformativeWWWWinformed#WޖWinforquerytype}WinfrastructureWinfromationWinitiateۃWۋWېWݍW1W\W]WaWbWWWWinitiate/prepare/comWinitiated-W>WiWWinitiates#WinitiationWWWWW8Winitiates#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#WW W*WܥWZW݆WinsteadofprefixthepoasubnetinformationtlvshouldcontZVinsufficientFWGWHWIWJW\WyWinsureTWUWVWWWXWintelligence:WintentWWintentoffigure24unclearVintentofmiddlesentenceisunclearandpossiblymisleadingVintentioniWintentionallyWinterܤWinter-bsWinter-essWinter-media*W: ) DvcommentݓWNWOWWWYWZW[W]W^W_W`WaWbWcWdWgWhWiWrWtWuWvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W$W%W+W,W.W/W0W2W5W6W7W:W;W=W@WBWCWDWEWFWJWKWMWOWPWQWRWSWTWWWYWZW[W]W^W_W`WaWbWcWdWeWfWgWhWjWkWlWmWtW{W}WWWWWWWWWWWWWWWWWWWWWWWWfbeitherreplacewitheuqivalentprimitivesthataredefinediކVeithersaytheframestructureVeithertheseshouldbedeletedorwrittenasobjectiveandm-VeitherwedeletethisdependencyforinteroperabilityorweVelementWWܕWoWW8Welements?WAWZWcWdW#WCWHWWބWޅWoWsW|WW8WsWeliminatePWeliminatesWelseWWeliminates Welse W WeliminatePWeliminates Welse W WWބWޅWeliminatePWeliminates Welse W W W W W W WWބWޅWeliminatePWeliminates W WWބWޅWeliminatePWPWWWWWWWWWWWW)WUWYWem2WembeddedWtWݸWWemoteޔWemptyۂWencapsulate WޞWWencapsulatedWޏWencodeTWUWVWWWXWcWencodedݘWހWevthiswillbehandledseparatelyforalsuchiesandappropriVthoseەWthreadWthresholdTWgW4WthresholdsgWaWWthroughݓWthroughoutWtidWtidissignificantonlywhenthereisaresponseVtime-intervalWtimeoutۅWtimerWtitle)WtlsWtlvZWށWރWWWtlvsZWWWto*WIWKWQWRWSWTWZWfWgWlWێW۔WەW۳W۴WWWWWWHWRW`WܛWܾW WWW1WbW{W}WݓWݜWݽWWWWWW"W*W/W4W5W>WBWCWNWOW7W>WBWCWNWOWSWTWTWTWTWTWTWTWTWTWTWTWTWTWTWTWTWOWSWTWTWTWTWTWTWnWއWtodayܗWtoo{Wtoward3Wtransaction۔WWtransactionsݓWtransparent*WtransportW^editorial݆݈݅݇wwwwwwwwa8.3.4bbARemove entire section 7.4.13.@A  33cA"MIH Handover Complete" is improper for 802.21 scope. The functionality represented by this primitive is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d648g2264 2006/05/14 2006/04/245EQiaobingFXieGMember^Technical, Binding_117`46a8.3.4b33cA"MIH Handover Complete" is improper for 802.21 scope. The functionality represented by this primitive is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d648g2264 2006/05/14 2006/04/245EQiaobingFXieGMember^Technical, Binding_117`46a8.3.4bed" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new ayer mbAAdd a new table called ScanRequestInfo containing the following information Name Type Valid Range Description Link Identifier Identifier identifier Identify the link associated with the scan command ScanCommand STRING N/A The scan command for the link Change the Description of link 17 to "List of ScanRequestInfo"@Af  33  33&  33  33  33fcThe Scan RequestSets is not defined. The List of scan requests must be clarified. Even though the scan command is defined per SDO and is beyond the scope of 802.21, the MIH must be able to know how to dispatch the scan commands to the lower layers. d632g2298wAccepted{k) done 2006/09/21oENada, Golmie, Member^ Editorial_106`12b106`12b #vfirstݓWnWWWfixedWWflexibilityZWflowۋW>WBWCW\WWWW2W{WWWfolksWfollowingەWWWWfollowsۛW۳WWWWWWfolowslWforCWIWJWQWRWSWTWZWfWۋWۓWWRWܛWWWaW{WݓWݽWW4W5WCWVWdW\WjWWWWWWWWWWWWWWWWWW"WUWjWvWWWWWWWWWWWWWWWforamiheventthatcanoriginatebothlocallyandremotelyVforeachaccessnetworkthereisanoperatorandsametypeoVforwhatscenariosl3doyoureallyneedthisVforceW!Wforeign"WޏWformZWformat\WWformatsWntifier " to: " A list of Oerator Identifier TLVs. " @( bseekingLWېWWseemsWsegment*WsegmentsRWselectAWۋW~W|WWselected|WselectingSWselection WܡWWWWselector.WAWselectsܡWsemanticsېWWWWWsendۓW"W$W/WWsendxmlbeforetransmissionVsendingVW#WsendmsguWsenetenceWsensoryۖWWsentW%WWWWWWyۖWWsent۵WW\WW%W%WWsensoryۖWWsent۵WW\WW%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%W%WsentencesW0WseparateWWser#WserveNWxWserver\WiWlWW;W`WzW݊Wserves[Wservice#W*W?WAW_WiWpWۂWېW۳WW+W5W<WHWSW\WܘWܟWܬWW0WKWeWyWzW}W#WWW^ TvAMIH Function receives this event from link layer. MIH Function then passes this notification to the MIH User(s) which have registered for this notification. The MIH User(s) Higher layers may take different actions on this notification. If parameters related to link quality cross a certain threshold then that link may need to be evaluated for handing over current connections. The MIH Function may collectively evaluate different parameters and give appropriate indications to higher layersB* regarding suitability of different links @AR  )c  TT    )cRwAccepted-Modified{k) done 2006/09/21 2006/04/24UEQiaobingFXieGMember^Technical, Binding_79`39a7.3.15.3b7.3.15.3b555g2297v )c  wAccepted-Modified 2006/08/07 2006/04/24 TEQiaobingFXieGMember^Technical, Binding_78`53a7.3.14.3b7.3.14.3bcal, Binding Ww{a$W@WAWCWKWpWsWvWۼWWNW[WܵWܾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWܞWܮWWWW:WWWSWaawaitingresolution$VۼVVV V V VܝVܞVܮVV:VVVSVyI ^bindingWWWWW WW'W0W1WEWHWOWPWaWbW{W}WW݃WݍWݎWݒWݓWݔWݕWݖWݗWݘWݛWݜWݺWݾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW{pnetworkܾW݃WnetworksۓWnewېWۓW۽WWRWzW{W>WBWCWnoZWیWܰWnoduplicatetable18foundیVnode.WnoneܰWnotۅWۓW۽WW)WRWܥW{WݒWݓWVWnote݃WnotesEW݃WnothingYWnowۓWܰW݃WݒWnumeriousۓWoctetsAWofgWۓWۓWۓWۓWWRW{Wonlyaddednew6.4andsubsections{Voos/securityܾWopen{WorܾW݃WoriginalAWp9-l6ܡWpagekWpage/line/sectionWparaWparameterݜWparametersWݜWpartW)WWkWper.Wpic>Wplaceholders&Wplaceholdersaddedbutneedsomeonetoprovidedetails&VpleaseݜWposܥWpppWppt݃WpresentWpreviousۖWprimitiveWRWprimitives۽WprobablyܰWprobablynoneneededܰVprovideW&WWquestions{WradiusۓWreadWreadabilityDWbbline۠WۮW7WHW`WkWuWW(W)W,W/W,W1W5W=WWWWWWWUWtWWWWline26setthevalueinformationtocostofaccessingthenHVline16WWۅWۉWېWەWۣWWWWW8W9W=WlinkcapabilitydiscoverrequestېVlinkeventdiscoverrequestېVlinkparamaeterۉWlinkparameterۉWlinksPWTWlinktechFWGWlinktypeFWGWۉW"Wlist-W.WAWPWZW]W_WuWۂWېW=W@Wlocal W-WۂW۳W۶WW7Wlocally-W۶WlofWlossFWGWHWIWJWۉWlotWlowېWlowerAWpW۵W6Wlower-layer*WlsۓWmac,Wmac/phy WmachineWmacpoaۊWmadeWmaintainedWWmaintaining۶Wmaitained۳Wmake#W*W?WZWW;WAWBW2/cgeneral+W`WwWۢWWWWWWWWWWWWgenerallyۉWW<Wgenerallydon'tunderstandwhatthepurposeofthisprimitivVgenerateZWWWgeneratedLWcWdWۅWZWޖW5WnWWWWgenerates#WgeneratingaWWWgenerationWgenericۼWWWgenericmayconveyconflictingnotionwrtmedia-dependentۼVgeographicW'W/WgeographicalIWWWgeran۽Wgeran/umts/lte۽W۽W۽W۽W۽W۽W۽W۽W۽W۽W۽W۽W۽W۽W۽W۽WetechnologytoْVthescopesectiondoesnotadequatelyaddresswhichpartsofHVn" 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 coY5abdefineitas0forversion1thisdraftothervaluesforfutVVdefineitproperly۔VVVdefinemigrationstrategyasnewlinktypesareintroduced VdefinemorefalurecodesifdeemednecessaryVdefinepagingrelatedeventsVdefinethelistofactionsthatcanbetakenandprovideenchVdefinethescopingrulesforthetidVdefinethesyntaxofthetransactionidincludingallocationVdefinethetermsessionproperlyVdefinethevalueforversionlike0forversion1;VdefinetypehdrtlvsrcmihfidandtypehdrtlvdstmihfidVVܝWܪWܬWWdefinitionofnetworkoperatorinmiddlecolumniscicrcularVdefinitions:WAWBWWWdefinitonܞWdelayWdelet)WdeletekWnWvWwWۦW۪WWWW W W WWWWWWW"WܠWܭWdeleteheterogeneousVteoraddanewdefinitionV< HibAChange the text to: This primitive is used by an MIH user station's MIH (or an application on behalf of MIH) to request information either from the network or from an remote MIH Information Server. The information query may be related to a specific interface, attributes to the network interface as well as entire network capability. The service primitive has the flexibility to query either a specific data within a network interface or extended schema of a given network. @AB 33  0  )c1  2  )c;  TTn    TT    )c    TT      )c  Bcven network. @crelationshipsZWsWrelativeNWWrelayWreleaseW W&WrelevanceۀWWrelevant۳W;WLWWWrelevenceWreliabilityeWrelies۳W<Wremainder WremainingwW WWlWremoteWW7WܖWܫWWKWzW{WW WW#W>W|WWWWW7W{WWWWWWWW#W!W!W!WnsthenecessaryinformationviaappropriatVremoveۙW۱WWWWܱWWPWWWWWWW*WWWzWremoveapparentlimitationsVremoveimplicationthataccessisremotesinceinformationmVremoveimpliedlimitationbetterexplainuseVremovelimitationsVremovelimitationsremoveimplicationofcapabilityuniquetPVremoveredundancyۙVremovereferencestoasn1VremovesfromnotifiesinthefollowingsentencethemihmigVu0csuchۃWۉW:WܬWܰWaWeWW*WWWrWWWWWWWWWW/W8W<W?WkWqWtWWWWsuddenlyWsufferingWW.Wsufficient?W@W|WWsufficiently^WpWvWfWgWhWiWjWkWqWwWxWyWzW{W|W~WWWWWWW WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsingۘVsuggestedۂWWqWsuggestedrephrasingofgapsinradiocoverageVsuggestednewlinkidenݬWWsuggestednewpoaidentݬWW?bacross"W?WAWۻWQWWWWacrossheterogeneousnetworkinterfacesupperlayersmayuti"VactܒWVVVVVVVVVVVVVVVVVVVVVVVVVVޖW޿WWactivitiesۉWactualwWWacuallyWad݊WadaptationWWWWaddWWW'WCWDW\WbWۇWۉW۶WWWWWWWWWDWEWRWSWTWUWVWWWXWYW\W`WbWcWdWkWmW܎WܐWܗWܘWܙWܚWܜWܴWܺWܻWWWWWWWWWWWWWWWWWW'W)WHWbW|W݊W݋W݌WݛWݥWWWWWW2WDWKWLWMWWW[WaWbWcWhWޒWޘWޙWޚWޥWWWWWW4?gcsystemsWWWtaWtableWZWhWیWېWW)WGW܁WWWEWݛWݿWWWWW\WlWހWށWނWރW>WkWWWWWWWWWWWWWmWWWWWWWWtable22needstoberevisedހVtable23needstoberevisedނVtable24ismissingrightaftertable23ݿVtable6doesnotdefineanylengthhoweverthisis4octets)Vtablemissingthisisacapabilitynegotiation\Vtable-6Wtable-7WtablesWWWWW-6ܷWtable-7ܹWtablesWWWWWWWWWWWWWWWWWWWMWlatterWZWaintained? g2641 2006/04/29~EEleanorFHepworthGMember^Technical, Non-binding_59`43g2642 2006/04/28A vasܾWWWWEWzWݓW"W4W5W>WOWVWYWnW\WzW{WWWWWWWWWWWWWWWWWWW WWW W%W-W2W:W=W>W?WjWkWnWvW{W|W}WWWWWWWWW#W#W#Wnt555VVWVaspercomment555resolveitthesamewayUVaspercommenterrequest{Vaspercommenter'srequestzVaspercontribution21-06-0691-02-0000-3۽VEVYVaspercontribution21-06-0705-00-0000-lDVasperrequestfromcommenterVaspectsWassignedZW-WWWWWWWWW4WoWvWassignedtoteamvVassignmentWatWNWWW"WVWattachment1WWattentionWauthenticationWWavailable{WdWWavialableWbWWback!W!bfunctionspWxW|W<Wfurther WWqWݗW"W$WWWfutureOWRWWVWWg?WWWۖWWWݎWݔWWW"W$W%WހWWWW'W1W>WgalinkteardownresponseisissuedVgainpWgathers>WgeneraltWWWWgeneratedLWdWېWZWWޖW5WnWWWWWgenerates#WgenerationW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WgenericFWGWHWIWJWۼWYWW2WWWWWWWWWWW3W4W5W6W7WdWeWfWgWhWߢWߣWߤWߥWߦWWWWWWWW W!W"W[videntifierWWWݒWݜWWLWMWWWidentifiersWWidsRWWWUWWieWWWWWWWnWie'sWieee4W5WjWiesZWWjWWWWWWWietfݜWWWifTW۔WW W*WdWWWWWWW"WWWifthehandoveroperationissuccessfulthemihfinserving*VimplementationݓWjWWimplementedWimplicitlyWimpliedWimplyWimportantWimposeWinZWlW۔WەW۪W۳W۴WWWWWRWWWhWܬWܾWWzW{WzW{W{W{W{W{W{W{W{W{W{W{W{W{WzW{W{W{W{W{W{W{W{W{W{W{W{W{W(cgiW۪W0WWW"W$W%W~WސW>WtWuWWWWWWWWWWWWW#W/WWWgalileoWgapsWW@Wsuitable<W$W?Wsup-WsupplementpWڪWsupplementtitlebyappenidngfromaremoteserverڪVsupplementwith3gpp2standardsreferencesasaminimumsuggpVsupport W+W-WHWmLWWWueryWsupportedW-W8WWWWWsupportedisquerytypeWsupportsمWWW}Wsure{WswitchCWswitching+WBWsynch_WsyntaxٿWWWXWYWZWsystemIWeWtWtableWWW!W&W'W)W1W6W:WcWyW٥WٻWټWپWٿWWWWWWWW5W9WڟWڣWtablesGWtailښWtake;W<W=W@WAWBWtakenٿWWtargetgWtayloredfW {kdoneZV]V^V_V`VaVfViVjVkVmVoVpVrVtVuVvVwVxVyVzV{V|V}V~VV܀V܁V܂V܃V܄V܅V܆V܇V܈V܉V܊V܋V܌V܍V܎VܑVܒVܓVܔVܖVܚVܛVܟVܠVܡVܣVܤVܥVܧVܨVܫVܬVܭVܱVVVVVVVVVVVVVVVVVV V VVVVVVVV!V"V#V$V&V'V(V)V*V+V,V.V/V0V1V3V4V5V7V8V9V<V?V@VAVEVGVHVKVLVMVNVOVPVQV^VbVeVfVgViVjVkVlVmVnVpVqVrVsVwVzV}VV݃V݅V݆V݇V݉V݋V݌VݍVݎVݐVݑVݒVݓVݔVݕVݖVݗVݘVݚVݛVݜVݭVݲVݵVݸVݹVIWD.gcsyntaxerrorinwhenapredictiveevenexpectedtooccur^VsyntaxerrorinwhichsttausmayVsyntaxerrorinwhirepVsyntaxerrorsintheremainingoctesieexcludingthefirstwVsystemەW۽WW6WWYWWW8WWWWWsystemmanagementhasbeenintroducedasaserviceherehoweVVdasaserviceherehowe+V+Vnthasbeenintroducedasaserviceherehowe+V+Vwise, "Show All Records" button in Create and BSubmit 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 coEZEQiaobingFXieGMember^Technical, Binding_44`30a6.3.2bARelationships between Information Elements must be added to the definition and the entire IE list must be restructured into a tree structure. For instance, LIST_OF_OPERATORS should be the top of the tree; and under each operator in the LIST_OF_OPERATORS, there will then be a LIST_OF_NETWORKS and OPERATOR_IDENTIFIER. In other words, LIST_OF_NETWORKS and OPERATOR_IDENTIFIER must be defined as attributes of LIST_OF_OPERATORS. The above is just an example. The suggested remedy is to identifBPy and re-classify all the current IEs in Table 6 to make the table into a tree.>cThe current Information Elements in Table 6 are poorly defined and need improvement. In partocular, the current definitions are expressed in a flat, unstructured list. This fails to show the relationships among the Information elements. d345g2303i Vivek GuptajOEven the current schema diagram is not correct and does NOT show this clearly.U~cdifferences@difficult@discovering@8document@domain@Edraft@each@edge@nganmihcompleterequestside@24isincorrectinparticularitimpliesmihfusingi@forۋ~force@front@g@2general@(get@goal@handover@he@horizontal@pie@implementation@improvement@"in2in802.21alinkgoingdownmihlinkgoingdowntriggerisu@infigure3interfacetocellularbsisincorrectasperthe@in-scope@}incorrect@inetrafce@@informationserviceclassificationisnotconsistentwithth@inter-operability@interpret@is@rF isnasacryonymcorrect@cissoft-handoverlimitedtohandoverbetweenhomogeneousacc@3issue@itisobviouslythatsupportedeventlistparameterinmihcap@Jjob@Llayer@lengthis2octetswhereasietable6saysitis4octetsth@TavsameCWUWۓWWWW Wsameascomment90Vsap*WܰWW4W5WjWWWsapsCWsaying WscanWscanresponsesetsWscenarioݓWscenariosݓWWscheduledWschemaܬWށWރWjWWWWscopeەWWWsdo4Wseamless1Wsecond۪W݃WWsectionCWKW۔WWRWWWhWܛWݽWWNWOWnWގWWWWW W4WUWjWkW}WWWWWWWWsection5.3.1referstogeneralarchitectureandnoteveryth Vsection5.8.3isdeletedaspercomment247VkVsectionsCWsecurityەWWWWW?WsecurityisoutofscopeVsecuriyܾWseeێW WWWWW WpWqWe31|Vseeissue34VseemsqWWWseemsusefultokeepthenumberofoperatorsseparatefromtqVsegmentsW~FGbagreed`WWaidWWalgorithmWalgorithms WWalignWalignterminologyoradddefinitionsVallZWۜW۠W#WRWYWܧWW݃WWW WsWWWWWWW W!WlWuWWWWallocatableWallocateWallocationWWallow۳WTWUWVWWWvWWWWkWWWalloweventstobesentfromupperlayersorfrommihfusersVallowsAWpWVWtWWalreadyRWW|WW(W,W,W,WWYWWW*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*Wout 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 coxggregঃৃਃ੃ઃૃguimingWguoۃWۄWWWWguojunxiangۃVۄVguojunxiangshuguimingVhongࣃःृă n3cfig/tableWWWWWWremoveline1Vremoveline37-43andaddreferencetothedefinitionoftheVremovemiddlesentenceremoveinthiscaseatendsVc? This boils down to an architectural question - can multiple technologies reside under the same MIH_LINK_SAP (so the example if GPRS and UMTS under a single MIH_3GLINK-SAP) and if so - since all the decisions about moving betwen these technologies are decided under the SAP (and hence out of MIHF and upper Blayer control) why should the changes be visible to higher layers as anything more than changes in bit rates, QoS, other link characteristics etc.?bparametersېWRWYW_WjWkW~W܁W܄Wm8WހWށWނWރW5WlWmWnWrWWWWWWWW4WWWW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wrting 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 and g2379 2006/04/28G*}gGMember^Technical, Binding_92`38a7.4.8b Remove 7.4.8.cfThis is redundant. The "MIH Configure" primitive (see 7.4.7) has already covered this functionality. d629g2316pabut didn't Change name of existing MIH configure to MIH_Configure_Threshold. It is problematic. vRemove 7.4.8. Change name of existing MIH configure to MIH_Configure_Threshold. Only keep MIH Configure Thresholds which always calls Link Configure Thresholds.wAccepted-Modified{k) done 2006/09/21 2006/04/24hEQiaobingFXieGMember^Technical, Binding_91`29a 7.4.7.1.4b0Either explain the unlabeled table or remove it.c-What is the unlabeled table in 7.4.7.1.4 for?d623g2317pTable explained by comment 621v Remove tablewAccepted{e) editor disagrees 2006/09/21 2006/04/24iEQiaobingFXieGMember^Technical, Binding_106`23a 7.4.15.1.1b4.15.1.1b4.15.1.1b  33&  33  33  33f~jtlvsWto"W@WW|WܾW,WvWgWuWWWWWWWWWWW=WqWzW}WWWWWWWWtoo=Wtop,WtransactionWtransmissionWWtransport Wtried=WtwoܾWWtypeܾWWWtWtypeieqosinformationelementisdefinedinlb1line46ptVtypesWunderstanding,WuniqueWupdate|W}Wupper"WWWurlWuseW"W|WWusecontentsinsteadoftableofcontentsassectiontitleVusetlvsforvariablepoaidentifierrepresentationVused?WjWWWWusefulnessWuserWusersWWWusesWvaluezWzWzWzWzWzWzWzWzWzWzWwithBWuWWWW W݄W+W,W>Wwithin,WTWwithoutBWwlan Wwman Wwould W>WKWxmlBWWS $^bindingWWWW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W.S[ctakeۅW?WWtaken6WtakesWtalk#WkWtalks`W?WݏWݏWݏWݏWݏWݏWhniquejWkWmWnWoWzW{W|W}W~WہWtechniquesWtechnlogiesWtechnologicalWtechnologies$WېWWWYW[WWWWWWW WBWtechnologyېWWWW:WܰWWW0WJWtechnology-dependent Wtechnology-independe W0Wtell_WaWۈWtense7Wtenseconsistency7Vterm W,W.W:W;WW-WterminalۂWۋWۏWterminalsۋWterms?W@W۲W۽W:WWterrestrialWtest%WtextW W,WAWKWeWiWrWsWuWWەW۾WWW{WWWWWWW݂W݄Wtextbetweenline43page43andline12page44isnotabouKVtextdoesnotreflectthedependencyofthetransportmechanVcinfoܰWW=W>WtWuWWW{WWWinfofilterWinfomration%Winfoqueryresponse|WވWinformݍWinformantion+Wtion+W+WW<W=W>WBWKWXWZW\W]W_WaWeWiWjWkWmWnWoWzW{W|W}W~WہWۆWۇWۊWۨW۳W۶W۷W۸WWWWWWWWWWW=WCWHWIWNWOWjW܄WܖWܘWܟWܡWܢWܤWܩWܬWܭWܶWܺWܻWWWWWWWWWWWWWWWWWWWW2W;WZW\WzW|W}W~W݀W݂WݏWݐWݥWWWWWWWWWWWWW"W#W$W%W'W-WBWZWdWgWjW޸W޹W޺W޻W޼WWWWWWWWW'W(W)W*WV^V^Technical, Binding_80`24a7.3.16.3bAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Handover Imminent" event. The MIH User(s) Application may take necessary actions to minimize the effect of the pending native link layer handover or switching on user data transfer. For example, to cover the handover period (when packets cannot be transferred), the network may proactively start sending the additional data as soon as it has Breceived indication about the event and should expect a request from the mobile specifying how much data it needs to cover the handover period. This event may also be used as an indication to start buffering packets.@Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.McwhyۅWW'WW W,WdWkW|WWWWWWWWWWWWwhydoeslinkgoingdownprovideinformationaboutnewpoaodVwhyisho-typeusefulhigherlayersmightcareaboutchangesVwhyisitadditionalparametersinsteadofvalueVwhyismihflinkedtohardwareinterfaceVwhyisthemih-functionblockl-shapedthetextfromline41,Vwildly'W'WSWSWSWSWSWSWd possibly elsewhere.c"Completeness; conciseness; Grammar 2006/05/01tEFarrokhFKhatibiGMember^ Editorial_8`18a3b(Remove "MIH Users are" in the beginning.c0Consistency with similar nearby section clauses. 2006/05/01uEFarrokhFKhatibiGMember^Technical, Non-binding_8`57a3b_Change "Network-side endpoint of a link that " to "Network-side endpoint of an L2 link that "cg3145 2006/04/29st" layout (otherwise, "Show All Records" button in Create and g2381 2006/04/289hT1v(Change "are already" to "may already be"wAccepted{k) done 2006/09/21Marked3EFarrokhFKhatibiGMember^Technical, Non-binding_16`58a5.3bvMention that the framework supports use of either L2 or L3 mechanisms toward communication among MIH network entities.cvMention that the framework supports use of either L2 or L3 mechanisms toward communication among MIH network entities.d116vAdd a new line after line 58, "The framework supports use of either L2 or L3 mechanisms toward communication among MIH network entities."wAccepted{k) done 2006/08/29 4EFarrokhFKhatibiGMember^ Editorial_17`32a5.3.1b#Break the sentence after the comma.c Readiablityd120{k) done 2006/08/29 5EFarrokhFKhatibiGMember^ Editorial_17`48a5.3.1b#Break the sentence after the comma.c Readabilityd122{k) done 2006/08/29 6EFarrokhFKhatibiGMember^ Editorial_17`6-7a5.3.1b'None offered, unclear intent of phrase.05/024csyntaxerrorinresultoftryingtoconiferthelinklVsyntaxerrorinspecifictieaVsyntaxerrorinstatusofhnadoverrequest܀Vsyntaxerrorinthealinkeventrollback܃VsyntaxerrorintheencodingformatisdefinedastablebeloGVsyntaxerrorinthefirstsentenceoftheserviceprimitive5VsyntaxerrorintheformatofthelengthfieldshallbepertvVsyntaxerrorinthelistofeventsthatmaycarriedinamesyVzVsyntaxerrorinthenumberofparametersthatmayincludedi~Vsyntaxerrorintheueisknowntothenetworkbut܋Vsyntaxerrorinthisisusedtorespondtheresult܆VsyntaxerrorinvaluesraeassignedxVVsyntaxerrorinvaluesraeassignedxVxVdtheresult܆V܆V܋V~Vsyntaxerrorintheueisknowntothenetworkbut܋V܋VyntaxerrorsintheremainingoctesieexcludingthefirstwVsystemۇWەW۽WW+WHT]cusediWۅWۡWWWkWwW܂W܆WܱWW WWaWfWW%W.W>WAW_W~WއWWWWWWWWWW W W W WVWpW|WWWWWWWWused/whyWusefaulWuseful>WtWWWWWWusefulnesstWuWuselesstWuWuser+WSW܊WWWޖW?WWWWWWWusersېW۪W7W0W>WaWWWWWWWWWWusesWWWWWWWW7W>WaWbWcWgW9WusesWWWW7W>WaWbWcWgW9WusesWW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WVusingradiusrelateddefinitionmaybeagoodideabutitalۓVzIbnot W#WAWەWۜWW#W,WRWVW܋WܟWܬW1WTWjWtWWWހWނW[WWWWWWW>WlWpWWWWWWWWWnotcontainedmimetypeapplication/xmlapplication/sparql-qހVnotcontainedmimetypeapplication/xmlapplication/sparql-rނVnotsuremihinterfaceswithlowerlayerarearespecifiedin1V1V1V9W9W9W9W9W9W9W9W9W9Wparql-qހVnotcontainedmimetypeapplication/xmlapplication/sparql-rނVnotsuremihinterfaceswithlowerlayerarearespecifiedin1VnoteuW#WHWW)WnotedۖWWnothingށWnotificationOWPWQWRWSWTWUWVWWW\WޕWޖWWWWWWWWWWmWnWoWpWqWrWsWtWuW߫W߬W߭W߮W߯W߰W߱W߲W߳WWWWWybtechnologies?WsW۱W!WWW WuWtechnologyWWWW0WW2WpWWtechnology-independeW W We W W W W W W W W W W W W W W W WmWnWpWqWsWthatW W,W-W.W?WAWHWIWLWMWRWTWWW\W_WdWfWjWmWtheWW W!W"W#W$W%W&W'W*W,W-W.W6W7W8W9W?WAWDWFWGWJWNWOWPWQWRWSWTWUWVWWWXWYWZW\W]W_W`WbWcWdWeWfWhWiWjWkWlWmWnWpWsWthefirststepistore-organizetheiesintoatreeormult_VthemWW]WfWthemselves-WthenFWGWTWZW]W_WbWeWthereAWUWZW]Wthese WpWtheyWW-WAWEcusage+WۖW2WܱWW:WWusageofinformationserviceschemadescribledin6.3.8ist:Vuse`WwWۣW۶WۻW۽WWWWWW,W;WRWYWܥWWWWW3W8WGWeWfWlWݔWWW WއWtWvWwWxWyWzW{W~WWWWWWWWWWW W WWqWWWWWWuseofmacaddressisnottechnologyneutralenoughtoincorVuseofnetworkbasedserverasasolesourceofinformation۶VuseofroamingisconfusingۻVSWۂWۊWW܊WusersېW۪W۵W7WܐWusesWusing"W_WaWbWjWkWmWnWoWwWzW{W|W}W~WہWۑWےWۓWWeWܬWWusingmihftoqueryandreserveresourcesrequiredforahan"VusingradiusrelateddefinitionmaybeagoodideabutitalۓVOWF^cGThe need for TYPE_IE_NUMBER_OF_OPERATORS is not sufficiently justified.d415g2307psuperceded by 345wAccepted{l) none needed 2006/09/21 2006/04/24Marked`EQiaobingFXieGMember^ Editorial_54`50a6.3.5bEMove and merge the first paragraph of 6.3.5 into 6.3.1 Introduction.c~The first paragraph of 6.3.5 talks about general use of MIIS and therefore should be moved and merged into 6.3.1 Introduction.d442g2309psuperceded by 345{l) none needed 2006/08/29 2006/04/24 cEQiaobingFXieGMember^Technical, Binding_81`21a7.3.18.1bAchange text to: This primitive is used by the link layerMIH Function (often on behalf of an upper layer user) to retrieve values of specified Information Elements.@Af 33  /  TT9  )cn  fcNLink primitive can only be generated by MIH Function, not from the link layer.d565g2312wAccepted{k) dones. bforcingWforeign"W%WformvWWformally.WformatrWsWvWGWHWvWWݘWݿWWW:WqWހWނWWWWW9WpWqWWformatspWvWformattedۉWނWforwardlWqW Wforwarding W6WfoundpWfour>WfourthWfragmentationWframeGWIWJWpWsWvWۉWYWWW'WlWmWWpWqWWframesrWWframework3W3W3WW'WframesrWWframework3W3W3W3WW'WframesrWWframework3W3WamesrWWframework3W3WWWW'WframesrWWframework3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WVshow٠WWshowingW cwhichۄWۉWۋWېWەW۳WWW'W:WPWZWkWW܄WܟWܡWWW W+WaWfWݍWW"W#W$W'WOWaWfWgWhWiWkWnWtWuW|WWWWWWWWWWWWWWW W W WWWWWWW!W?WtWWWWWWWWWWWWWWWW$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W38-cdefinitionsWWGWIWZWۦW.W1W:W;WWWlWmWsWWWWWWWdefinitionsofhorizontalhandoverandverticalhandoverare:VdefintionWWW W W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W'WeWdescribed+W_WjWkWmWnWoWzW{W|W}W~WہWۊWیWdescriptionjWkWmWnWoWzW{W|W}W~WہWۆWWW0W=W@WPW܅WdescriptionsNWdesign#Wdetail'WdetailedۆWdetails+WWdetectedSWWSWdetection WdevelopedjWkWmWnWoWzW{W|W}W~WہWdeviceWdevicesWdiagramۿWdiagramneedlesslycompressedۿVdifferenceېWjbetweenWWbit|WboundWbut|W,WbyvWjWW W{WWc462Wcan,WWWWcannotWWcapabilityܾWcarefullyVWcarriesWcaseszWcertainWzWchange@WWWW+WYWWchangefigure20asshownin21-06-0607-00-0000-sforcommen+VchangetexttoVchangethetableasdefinedin21-06-606-01-0000locinfoovYVchangetothedescriptionoftypenetworkqoselementtoindVchangetypeieqostotypeienetworkqosVcharactersticsWcheckWclarifygWWWclassifiedWWWWW-cdefine?W@WW)WRWTWUWVWWW[WܖWWWWWWW>WjWWWWdefineeventforpagereceivedthereceiptofapagefromteVdefinedSWZWیW۔WWW-WDWEWGWHWPWYW]W`WmWuW܁WܖWܚWWW݌WWW.W>WAWVWvWކWޖW6WWWtWvWWWWWWWWWWWWWWWWWWWWWW'W9W;WYWiWWWWWWWWWWWW"W"W"W"W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WW.W3W4W5WCW`WcWdWeWܛWܜWܬWWWoWwW7WKWޕWޗWdefinitionofinteroperabilityandcompliancemechanismsisܛVi 1bA[Insert 'MIH Capability' , page 54, line 14]: --------------------------------------------------------------------------------------------------------------------------------- Type | Description | Length | Value | --------------------------------------------------------------------------------------------------------------------------------- TYPE_IE_POA_CAPABILITIES | PoA CapabiliBties | 4 octets | PoA Capability bitmap | | | | Bit 0 : Security Y/N | | | | Bit 1 : QoS Y/N | | |  oQvW@A>  )c  TT  >wAccepted-Modified{k) done 2006/09/21 2006/04/24REQiaobingFXieGMember^Technical, Binding_77`22a7.3.12.3bAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Event Rollback" event. The MIH User(s) Higher layers may reevaluate the link under consideration by retrieving other link quality related parameters. Any handover procedures that may have already been initiated may need to be rescinded.@Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d543g2295v3g2295vcsentencesvW7WIWseparate݅WWNWseparateieee802.11intotwowordsVsequentiallWsequentiallyWserverlW۶WWWW"WWserverstWvWsentencesمWzW WseparateڡWserWserve:WserverڅWڪWservesWserviceWW+W-WfW٬WٳWٿWWWWzWڕWگWWWservice-infoٿWservicesW-W.WzWWservinggWses-WsessionWWYWset-W2W3W9WٿWWWWWWWWWWWWyWW%W&W'W(WshowW0WshownٮWshows+WsideZWsignal2W3W4W5W6WWsimilaraWcWiWvWsimpleLWsince٥W٩WWsincemihispronouncedlikeemihitisnecessarytoputt٩VsincethegenerationoflinkgoingdownisimplementationdeVsingleWقWsinrَW`1a 7.4.1.1.2b*remove destination identifier parameter. call mih primitives cannot have Destination identifier as local or remote since there is no information available to MIH users about mih peers.d575g2249iMathieu Peressej_Then MIH users cannot decides if the primitive is intended for local or remote communication ?mRejectedvONot clear from which primitives the Destination identifier needs to be removed.wRejected{a) awaiting resolution 2006/09/21 2006/04/26dresolution 2006/09/18 2006/04/24Marked4EPeretzFFeder^Technical, Binding_41`65b8Include contribution 0626-00-000_Link_Get_Parameters.doccAaPer last (March 06 - Denver) accepted comment resolution, add a new commnad : Link Get Parametersa@A>  33  %  33>d308g2250{a) awaiting resolution 2006/09/18 2006/04/28MarkedESrinivasF SreemanthulaRSbwirelesssWWpWXWWWwirlessWwishWWWW^W^W^W^WbWeWlWpWsWuWwWWۈWۋWېWۛW۝W۟WۡWۢW۽W۾WWWWWWWWWWW WW#W,W3W5W6W7W8W9W:W<W=W>W?WCWHWJWKWLWMWNWOWTWUWVWWWXWZW\W]W^W_WaWcWdWfWhWiWjWlWmWoWpWrWtWvWwWxWyWzW{W}W~WW܀W܃W܄W܅W܆W܇W܈W܊W܋W܌WܰWܷWܿW!W%W&W-W1W=WBWDWWW\W_WqWsWW݄W݊WݎWݼWWWWWWWWWWWW W W W WWW!W"W$W%W'W.W/W1W3W7W8W9W=WAWBWNWPWl7vroaming۳WWWroomWrouter"WޏWWrouteradvertisementisencapsulatedޏVroutingVWrtt WruleWsQWRWSWTWWWscanۆWscanresponsesetsۆWscenarioݓWscenariosۈWݓWscheduledWschemaBWW WܬWscopeەWWWseamless1Wsecond۪W݃WsectionWRWWWqWܗWܛW2WݳWWWW6WSWnWsection5.3.1referstogeneralarchitectureandnoteveryth2Vsection5.8.3isdeletedaspercomment247VVsecurityەWWWWWsecurityisoutofscopeVsecuriyܾWseeuWێWWܗWܘWܙWWW W WWWWsee413ܙVsee687Vsee687issue30Vsee704VVseealso709rttshouldbeprovidedbytransportifneededm Vseecomment413ܘVseediscussionof06-0611issue31uVseeissue34 Vseeissue35VW ObAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link UP" event. The MIH user(s) Higher layers may take different actions on this notification. The handover policy function may start collecting routing metrics for this link and may consider this link as a potential candidate for establishing future connections. When higher layer connections are being established over this link, the Transport laBKyer may adjust transport (TCP) related parameters based on link properties.9@Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d531g2292wAccepted{k) done 2006/09/21 2006/04/24PEQiaobingFXieGMember^Technical, Binding_75`36a7.3.10.3b7.3.10.3bf 2006/09/21 EDasFSubir ^ Editorial_10`30bDelete c!FMIP , GMII , ICMP are not used d87g2429{k) done 2006/09/21 EDasFSubir^ Editorial_11`19a4b3NAS is commonly called as " Network Access Server" cIs NAS acryonym correct? d89g2430p'both are used. Added the additional def{k) done 2006/09/21 EDasFSubir^Technical, Binding_16`63a5.3.1bDelete caIt is important to ........ interface or transport mechansim" contradicts the definition of POAd117g2431vChange the sentence as follows: " It is important to note that each of the communication relationships in the communication model does not imply a particular transport mechanism."wAccepted-Modified{k) done 2006/09/212006/08/292006/08/292006/08/29 EDasFSubir^Technical, Binding_18a5.3.2bReplace R1/R2/R3 with only R1caIn figure 3, interface to cellular BS is incorrect (as per the text in page 18 , line 56-61) d126g2432!{ GbA 33 33N c  33   33& z  33   33  334  33Q 33  33 33  33  33K  33W 33  33 33 M 33Bset | | |Examples: | | | | |{Generic:Link Speed}, | | | | |{Generic:Link Bit Error Rate}, | | | | |{Generic:Link Frame Loss Rate | | | | | before retransmission}, | | | | 6.bhasOWPWQWRWSWTWUWVWWWiWRWSWVW܁WW5WW$WhaveRW,W7WRWWW"W$W|WWWWWhdrܚWVWhead~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~WschemaxmlViۈWWi-dsۑWianaWidXWWidenAWidentifierZW]WۂWۇWۉWWidentifiersXWxWidentifyZW]WxWWidentityWidsNWXWېWieZW[W\W_WۇWۉWieee#WWieee802.11.WJWieee802.16JWieee802.21pWies?WAWZW]W_WbWfW W!W$WietfۓWWietfinformationelementsfor802.21VAWcofQWRWSWTWUWVWWWYW]W_WgWhWiWkWlWmWuWvWwWyWzW{W|W~W܀W܁W܄W܅W܌WܒWܓWܔWܖWܛWܟWܡWܤWܥWܬWܭWܰWܱWܾWWWWWWWWWWWWWWWWWW0W3W8WIWPWfWwW{W݃W݆WݍWݐWݔWݵWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWp{k`WaWfWiWjWkWmWoWpWrWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎WܑWܒWܓWܔWܕWܖWܚWܛWܟWܠWܡWܣWܤWܥWܧWܨWܫWܬWܭWܱWWWWWWWWWWWWWWWWWW W WWWWWWWW!W"W#W$W&W'W(W)W*W+W,W.W/W0W1W3W4W5W7W8W VbAUse of a bitmap model to encode the status of the event registration process to the MIH . There are currently 9 events, so using 32 bits will allow enough bits to add new or vendor based events. In the Valid Range, replace "Set of valid link events" with "4 octets representing the list of events" In the Description, add the following: The encoding uses a bitmap where the bit position represents the event ID. A bit set to 1 indicates that the registration for that event has been successfBul, otherwise either the registration was unsuccessful or not requested. For example, if bit #0 is set to 1, The MIH requested to receive Link Detected indications and the registration was successful. Bits corresponding to reserved event IDs must be set to 0. Mapping the bitmap used in the request and the one returned by this primitive allows quick detection of registration failure. w Event IDs in order to support interoperability between different Link Layers. d502g2270er % SvsupportەW۫WݓWWWsupportedWsupports3WsureWswitching{WWsystemWWsytsem{WtWWtableIWhWdW\WWWWW Wtable-4Wtable-6W)WWtable-7 Wtable-8Wtable/reference`WtakeQWTWWWtalked Wtarget"W*Wtask!Wtcp'sWtechnologiesWWWWtechnologyەWܰWW0WW&WtermWterminateݓWtermsZWWWtestingWtextKWZWlWWWWW۵W۷WWWWWW WܗWܬWWWWWW0W2W3W;WBWDW{W݃W݄WݓWݳWW-W/W4W5W7WSWthegroupfeelstheoriginaltextisbetterthanthesuggest7VtheieshouldrepresenttheqoscapabilitiesoftheaccessnVthelanguageistoostronginsomecasesmayneedtochange{Ve 6. !vbasedQWۅW0WjW}WWWWWWWW~WWbasedonrequestfromcommenter}VVVV~VbeRWTWZWەWWەWەWەWەWەWەWc1.2WW10܍WtWuW11W WWW111W118W12KWWYWZWtWuWWjWWW124YW125hWhWhWhWhW_WaWWWW6WWW124YW125hWhW_WaWWWW6WWW124YWYW#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#WlWޗW14-15W15WWݛWWlWޗW1500W16EWWW|WWWW2W17یWW18یWWWWyWWBW19ܵW1stvW1xev-doFW2W!WSWiWsWuW۴W۽WW&W=WAWBWCWݗWWW>WEWGWHWޕWޘWޟWWWWWW8W?W2pagenumbers0-6oftocshouldnotrepeatthemaintextVޘVVV8V2.2!W2.3_WaW!W2.4!W1PbregisterۉWrWWݲWWWWWWregisterationWregisteredOWPWQWRWSWTWUWVWWWWregisteringWWregistrantWregistrataionWregistrationVWW|WWWWregularޖW5WrejectWrejectedܖWWWWWWWWWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWWWWWWWWWWWWW+W3W4W7W=W@WIWPWQW[W`WqWuW-Fcanywhere۔WWWWW Wap-WܵWWiWap/bts+Wapi'sWapparentWkWapparently WWWappearsW WappendixWWNWWWappliancesWapplicableWܥWWWWWWWWapplication۪W+WݭW WWapplication/protocol"WappliedWappliesWWapplyYW{WWapproachWappropriateۅW܂WWWW<WWapprovedWWapsWapzWar:WdWarbitrary WWWWWWWW:W=WNWRWcWjWtW܏WܖWܗWܚWܪWܭWܯWܲWܴWܹWܿWWWWWWWWWWWWWWWarelinksynchronouseventsapplicableforl2handoversonlyܲVaremorefailurecodesneededtoindicatewhyaparticularsVareaW=WIWareasWWarticle۰W-^cannexۀW>WWWWWannexesWannexesmissingfromtocVcVV>WannexesWannexesmissingfromtocVVlinklayerindicationwhichshouldonlybereceive@thissectionshoulddescribeallmediaspecificsapsshowni@thisstatementmakingtheinter-mediadifferencesfullytran@tlvs@ toږtodiscoverwhattypeofeventsaresupportedbythelinkla@6tothemobiledevicemntheonlyvisiblemihentityismihp@transaction@transmitted@_two@\typo@understand@usage@xuseofmacaddressisnottechnologyneutralenoughtoincor@v-aaa@,valid@variable@wherewhether@which<swhy@rwill@ dp@‚d@n'blefthand-side>WlegendܵWlengthJWۉW)WHWvWwW|WWiWݗWݵWݹW'WuWހWނWޅW1WWWW8WlWlengthodofcivicaddresselementsinoctetsuVless=Wlevel#W?WQWܬWWlikeAW2WUWWWtWWW;WWlikelihoodWlimitWlimitthescopeofmihcapabilitytol2mihcapabilityVlimitationWWfVfVlimitationWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWIWJWۉWlotWlowېWlowerAWpW۵Wlower-layer*WlsۓWmac,Wmac/phy WmachineWmacpoaۊWmadeWmaintainedWWmaintaining۶Wmaitained۳Wmake#W*W?WZWWRvproposedWWWprotoݓWprotocolۉWW0WݓWWWWUWVW}WWWprovideW?WnWWWprovideupdateddefinitionswithappropriatereferencesfromVprovided WWWWWWWWWWW-Wprovider's۳Wprovides4W5W?WjWWprovisioned۳Wprovisioning۳WproxylWpsdn/fa-Wpsdn/fashouldreadpdsn/fa-VqosۅWܾWWWWW4WtWWqualityRWTWۅW4Wqualityparametertype4WqueriesZWWquerlyWquery"WlWށWރWWWWWquery/responseWqueuedWquiteWWrWWcmostېWWWWWWmostareaswheremobileipv6arereferredtoshouldbeipv6VmostlytWuWWmove)WWmovesections8.5.2.1and8.5.2.3fromeventservicecategor)Vsections8.5.2.1and8.5.2.3fromeventservicecategor)V)VWmuch(W)WW݂Wmulti-hopݓWmultipleۋW۪W"WIWcW|WܞWܤWWWWW!WݐWmultipledefinitionsofmnܞVmustEWiW>W?WCWHWKWLWRWTWUWVWWWXW`WmWsWWmvno"Wn/WWn-layer/WܟWn-layerasubdivisionofthelayeredprotocolarchitecturec/Vn-userܟWnameۤW۽W܁W܂WWWnamesWnamespaceCWnasWnas-port-type=WݔWnativeWnaturaljWkWmWnWoWzW{W|W}W~WہWnatureAWܖWxWnavigationWneWnearby(W*WܾWWWW vthisܛWWW0WݓW"W4W5WnWfW|WWWWWWWWWWWWW WW!W&W4W=W?WjWmWvWWWWWWWWWWWthisfieldactuallyreferstotypeintlvasopposedtoabiVthishasalreadybeenaddressedbyothercontributions|VthisisdesiredbutwecannotmandatethiscertaintechnologVthisisquitecorrectVthiskindofpartitioningdoesnothelpatthisstageneedsVVV W=WHW`WܐWܗWܛWܢWܽWܾWܿWWWWWWWWWW WW W1W2W:W;WDWFW{W}WW݀WݏWݓWݜWWWWW/W1W4W5W6W7W>WBWCWSWdWfWnWtodayܗWtoo{Wtoward3WtransactionsݓWtransparent*WtransportWer TLV.d561g2349 YcAThe List of parameter type needs to be completely defined by the IEEE 802.21 group in order to support interoperability. MIH Functions and Upper layers need to understand what the parameter types in order to configure and use them properly. However, the current list of parameters provided does not apply to all link type technologies available. In addition, this list is not consistent with the types defined by the MIH protocol in section 8.4.2.8 on page 124. d518g2278p/made consistent changes to accepted comment 525wAccepted{k) done 2006/09/21ZENada, Golmie, Member^Technical, Non-binding_72`39bAIf the primitive is to be used only by the MIH Function, replace "This primitive is generated by an upper layer entity" with "This primitive is generated by an MIH Function"@Af  33d  33v  33  33  33fcfccbeen+WpWvWxWW)WܕW݅WWLWMWWWWWWWWWWWWWWWWWWWWWWWWWWWWWGWHWIWJWblockFWGWHWIWJWboth-W:W;W<W=W>W_Wbut%WDWEW_WaWiWby+W/W0W1W2W3W4W5W6W7W8W9WEWLWMWOWPWQWRWSWTWUWVWWW_WbWcWdWuWc_WaWcanAW_WbWcWdWeWjWkWmWnWoWcapabilitiesuWcapabilityuWcapable_WaWcharacteristicsiWclarifiediWclassesWclear!W-WcommentsuWcommit/W0W3W5W8Wcomplete/W0W4W5W9WcomplexityBWcomplianceWcomputationalBWconfiguregWconfusing(W)Wconnection\Wcontent!W!qvbelow"WWWbenefitsWWbernardݜWbesidesWbetterۅWWbetween۔W۴W4W5W\WW"WjWWWWbeyondݓWbitmapWbits)WbodiesۓWbothWW/WWWbothdatarepresentationformatsneedtobeprovidedasoptiVbringWbroadcastۅWWstۅWWWW>W?W@WWWWWWWW W0WCWDW{W݂WݪW0WFWWWXWmWyWby215WVby394XVby482yVby492FVby516Vby518FVby527ݪVbycomment162۸Vbycomment195۾VCVbycomment200tobeverifiedwhenre-drawingthefigureasDVbycomment203Vbycomment208Vbycomment212%VVbycomment215&Vbycomment215andissue40'Vbycomment348Vbycomment369ۑVbycomment384Vbycomment480\Vbycomment500mVbycomment704Vqec?No IE for " performance of access networks" has been defined. d22g2413i Qiaobing Xiej^replace "performance of access networks" with "configuration and condition of access networks"mAccepted-Modifiedv^replace "performance of access networks" with "configuration and condition of access networks"wAccepted-Modified{k) done 2006/09/21MarkedEDasFSubir^ Editorial_7`6a3c#Handover needs a better definition d49g2416{c) instructions unclear 2006/08/29 EDasFSubir^ Editorial_8`9a3cEThe statement " The same network entity...... " is very confusing..d55g2423{c) instructions unclear 2006/08/29 EDasFSubir^ Editorial_9`39a3bReplace " the" with "that" ... cVIn the sentence " Conceptual ...... transfer the occurs between", "the" is a typo d80g2427{k) done 2006/08/29 EDasFSubir^ Editorial_10`18a4bDelete c%The specification does not use ASN.1 d86g2428{k) done w^binding"WDWGWIWJWLWOWPWQWRWSWTWUWVWWWZW^WcWdWeWfWgWhWiWlWwWۀWۅWۓW۔W۳W۴W۶WWWWWWWWWWWWWW,W:W;WCWHWRWSWTWUWVWWWYWkW܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂WܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐWܐW[/4wAccepted-Modified{k) done 2006/09/21 2006/04/285EAjayFRajkumarGMember^Technical, Binding_30`54a5.6.1.3bAEchange the text to "The C_SAP, defined in the IEEE 802.16 standard, provides the interface between the MIH Function and the 802.16 control plane. This SAP is used for local MIH exchanges between the MIH Function and the lower layers of the mobility management plane (as part of the 802.16 instantiation of the MIH_LINK_SAP)."EcModify the current text "This SAP defines the interface between the MIH Function and the control plane of 802.16 network." to better explain the SAPd224g2236vAEchange the text to "The C_SAP, defined in the IEEE 802.16 standard, provides the interface between the MIH Function and the 802.16 control plane. This SAP is used for local MIH exchanges between the MIH Function and the lower layers of the mobility management plane (as part of the 802.16 instantiation of the MIH_LINK_SAP)."E@E@f1TnvreturnsWrfcWW>Wrfc3268listsallciphersuitesfortlsnistalsohasalistVValistVVcnotcustomaryuseGVnotsurewhatismeantbyagentadvertisementisޏVnottransportchannelisestablished܋Vnote WW>WWWWWWnotethatalternativeunderlyingtransportswouldallowtheVnoted*WiveunderlyingtransportswouldallowtheVnoted*W*WiveunderlyingtransportswouldallowtheVnoted*W*WnderlyingtransportswouldallowtheVnoted*W*WiveunderlyingtransportswouldallowtheVnoted*W*Wv@tlvwhenthisinfoquerytypeisspecifiedtheinfoqueryparame@toچ$toprovideclientofthenumberofnetworksinsteadofopera@ntoc@Ltypemimetlvvariableamimetypetlvanoctetstringfora@underlying@up@useatvariousinsteadofother@Iallot 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 and  bAz  c  TTl  )c{    TT  TTzaccepted comment resolution, add a new commnad : Link Get Parametersa@A>  33  %  33>d308g2250{a) awaiting resolution 2006/08/21 2006/04/28ESrinivasF Sreemanthula^Technical, Binding_83`1  33d307g2270i Ronny KimmRejected{a) awaiting resolution 2006/08/21 2006/04/244EPeretzFFeder^Technical, Binding_41`65b8Include contribution 0626-00-000_Link_Get_Parameters.doccAaPer last (March 06 - Denver) accepted comment resolution, add a new commnad : Link Get Parametersa@A>  33  %  33>d308g2250{a) awaiting resolution 2006/08/21 2006/04/28ESrinivasF Sreemanthula^Technical, Binding_83`104/24^technicalܕWܕWܕWܕWܕWܔWܔWܔWnWe received by the MIH function, not by any upper layer. 2. To pass this notification to an MIH user, need to add "MIH Link Detected" event to MIH_SAP, which is not currently defined. An alternative is to disallow passing this link event to an MIH user.3ijkmnpvw{ 2006/05/146/04/24der" 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 ?/ۍE bingqiangFjiangGObserver^ Editorial_82`26a7.3.19.2cA)request source should be response source,)@A>    33  >d569g2242{k) done 2006/09/21 2006-04-07ێE hongchengFzhuangGObserver^Technical, Non-binding_112`29a 7.4.7.1.2cA8MIH_Switch.request should include New Link Identifier IE8@A d707g2243vRgo ahead and add it to the param set of the primitive definition see pg 88 line 64wAccepted{k) done 2006/09/21 2006/04/11ۏEbingyunFquGObserver^ Editorial_139`2a8.6.1.2cA%Mobile Terminal change to Mobile Node%@A>    33  >d869g2245p8redraw - section 8.6 already removed by another comment{l) none needed 2006/09/21 2006/04/1129999n-binding_82`51a7.3.20b nbneedAWRWTWpWxWۉWW)W܂WܾWݍWWWWnWWkWWWWneedtoaddsometexttobeconsistentwithothercasesVneedtoverifythecorrectnessofthisstatementandifnotVneeded;WWW<WWWWWWneedsLWVWdWWܾWIWWWneedstobeconfiguredofflineorout-of-bandandit'sVnegotiate|WneighborAWNWtWneighborhoodtWneighboringܡWtWtWW}Wneighboring-poa~WneitherWneoustWnetuWWWWWW~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W;WIWMWOWPWSWZW_WuW|W݃W݊WݺWWWWWWW WW!W"W#W$W%W+WbdependingAW܁WW%WlWdependingonthetypeofmobilitysupportfordifferenttypeVdependingonwethertheresponsequerieshasonlyoneormul܁Vsonlyoneormul܁VdeploymentW}WderegisterۉWWWFWHWrWzWderegistrationWXWderivedHWdesciptorSWdescribe'WWWWWޥWWWEW߃Wdescribed'WsWۃWۄWnWݓWWWWKWLWMWTWޥWWWEW߃Wdescribedintable33aVdescribesvWdescribingW5WܟWdescribingroamingaspectsonin5.3.2beforethetermsareVdescription?WpWtWۂWېW=WNWRWSWTWUWVWWWXWYW\WcWkWmW܄W܅WܲWܶWܷWWWWW|WހWނWޔW޽WW,W]WߛWdescriptionsWdescriptiveWdescriptonܹWdescriptorWSWdesctiptionހWނWgjcouldݍWcouldyoupleasedefineipaddressaquisitionandipaddressݍVcovers"WcreateܾWcurrent"WZWWdatazWdecideWdecidesWdefine"WݍWdefined?WYWtWdefinitelyWdeletewWW WrWWdeletefigure24wVVrVVdeletethefigure VdependentWWdepictvWdeploymentWdescribeWdescriptionWdesignWdetailedjWdiagramZWWdifferent"W,WdisagreeuWWUdisagreeifthissectionisremovedthenitisnotpossibleuVdisagreethereisnoneedtoexplainwhereitislocatedVdisagreed|WWdisagreedfortransactionidVdiscussed|WVW}WdividedܾWdoWWdoyoumeanherefigure23VdocjWW=WYWdocumentWWWWW۬W۬W۬W۬WW۬WWW+WݻWKWdocument+W+W+Wo bC----------------------------------------------------------------------------------------------------------------------| ...... | .............. | .............. | ................. | ............................. -------------------------------------------------------------------------------------------------------------------------------------------------------------D-------------------------------- | 4 | MIH Configure Thresholds | L, R | Network -> Client | Configure thresholds for link events | | | | Client -> Network | | | | =5baccess#W$W*W?WAWUWpW۱W۳WWWWܬWܾWWW!W0WQWWWWWW WW"W$W%WpW1WWWWWWWW$W'W1WWWWWaccesstechnologies۱Vies۱V۱V3WpW1W4W;Waccesstechnologies۱V۱V3WpW1W4W;Waccesstechnologies۱V۱V1W3WpW1W4W;Waccesstechnologies۱V۱VW4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4WordanceފWaccordingۉWۊWۋWYW܏WyWzWaccordinglyWWaccoridingly_WaccountedOWaccurateܰWXWachievexWW"W#W$Wack-rspyWacknowledge܌Wacknowledged܌WacquisitionݍWacronym@WdVcthelengthdoesnotmatchthetlvrepresentationofsection@themihconfigurerequestisusedtocontrolthebehaviorof@ themihfunctionheaderconsistsofatwopartsonewithfix'xthemihlinksapshouldbeshownonthisfigureitwillclar@thenamespacemustbeassignedby802.21tosatisfyinterope@jtheneedfortypeienumberofoperatorsisnotsufficiently@therecipientoftheprimitiveisthemihfunctionwhichwil@#therepresentationofnumberpoaisnotspecified@thesentencehoweverthetarnsportandsecurityofthisinfo@;thetermgenericsapisconfusingsinceinline47itthens@theunitoftimeintervalisnotdefined@elementscurre@thetwomechanismsforretrievinginformationelementscurre@ctiontitlemediaindependenceisconfusinganddoesn@;IW^WuWڄWڌWWWdifferenttechnologieshavedifferentnmsinterfaceseg802ڌVdifferentiate|WYc^technicalnon-bindingۃVۄVۉVۋVێVېVەV۪V۫VVV#V$V)V-V1VAVBVZV`VhVmV|VܛVܰV+V3VAVLVkVzVݵVݽVV V VVV VkVކVއV1V2V5V6V>VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V VVVVV#V'V)V*V-V7V8V>V?ViVoVpVqVrVsVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVtechnicalwaseditorial V$V(V*V+V+V+VAVYVۛVۼV۽VVVVVVVOVܭVVVVVVVVVw9famolari.1farrokh!"#$&'()*+,-./013456789<=>?@AEGHIKLMNOPQRT^abcdefgijklmnpqrstw !"#$%&'()*+,-./0123456fran=golmie2W3W4W5W6W7W8W:W;W<WAWBWCWDWEWGWHWIWNWPWQWRWSWTWUWVWWWYWZW[W]W^W_W`WaWfWgWhWiWjWkWlWmWoWpWrWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎WWWWWWWWWWWWWWWWWWWWWWW /vvrefertocontribution21-06-0690-00-0000-iVrefertocontribution21-06-0708-00-0000linktranseventexVrefertocontribution21-06-0726-01-0000-i3Vrefertocontribution21-06-0737-01-0000-sVrefertocontribution21-06-0740-00-0000-saboutmihconfiguoVrefertodoc21-06-0675Vrefertosection7.4.5.2.4fordetailsݽVreferenceHWW>Wreferenced WreferencesWWW>WWrefersWWW WWregardingTWWWregisterationWregisteredQWRWSWTWregisteringWWregistration}WWregster{WrejectWrejectedXWWWWW<Wrejectedbyvote8-8XV<VrelatedRWTW۳W"WWWjWtWWrelatedtocomment142128226Vrelatedtocomment219jVrelatesWsaprelatesWWW environment). cmments" script. It had not been updated in 1.1 to match the new ijkmFbnodeAWpWۜW۞W3W4WܡWIWQWWW W"W#W$WOWtW|W>WuWWWWWWWWWnode's"WnodespWWnonHWYWWWnon-posۭW Wnon-secure<Wnone6Wnoneofferedunclearintentofphrase6VnorWnormalWWWnormallyOWPWQWRWSWTWUWVWWWnormativeWWnorthboundWnosWW WJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWtedWexplainHWIW|WexplainusageofthewordmediaIVexposedنWfacilitiesUWfacilitiesistoogeneralUVfailsWfeatureW? ۉbBthresholds need to beset. Bit 0: Link speed Bit 1: Link bit error rate Bit 2: Link frame loss rate before retransmission C Bit 3: Link signal strength Bit 4~15: Reserved InitiateActionThreshold 34 Variable LinkParamaeter specific threshold value that maycause upper layers to start setup type activities RollbackActionThreshold 35 Variable LinkParamaeter specific threshold value that may cause upper layers to1J2p9۽W;Wotmakesenseclarifywhichpartof0644-02go9۽W;W;Wave more space between characters in "STA/UE" and "PSDN/FA" boxes. - "PSDN/FA" should read "PDSN/FA". - PSDXA, should be GRE be in the flow? - Acronym for GRE needs to be defined in Section 4. - Is this an example of "Network Initiated Hand Over" ? - Line 55. the circle point left to "MIP binding to HA" should be shifted to the left. - Line 56. Does the AP get Link Tear Down or Handover complete indications before it is disassociated? d873g2399 2006/05/14 2006/04/28 Figure 30E Ulises Olverald be shifted to the left. - Line 56. Does the AP get Link Tear Down or Handover complete indications before it is disassociated? d873g2399 2006/05/14 2006/04/28 Figure 30E Ulises Olveran or Handover complete indications before it is disassociated? d873g2399 2006/05/14 2006/04/28 Figure 30E Ulises Olvera.ccinappropriateW8WW'Winappropriateuseofdash8VincludeێW:WܰWWW8WnWWWWWWW WWWW?WWWincludedefinitionofhandoffandhandoveranddistinguishbVincludesomesamplereferencelocationsofmihposanddiscuVincludethemihnmssapinthemediaindependentsapssectio8VVincluded~WWWWWWincludes:WAWW WWincludingW WWinclusionWfWgWhWiWWWWinclusionofmihfidinvariableheaderpartisnotmentioneVincompleteW3WWinconsistenciesWWWWWWWWWWWWWWWWWWWWWWentioneVincompleteWWhWinconsistenciesWinconsistency%W&WWޣWޤWWWWWCWDW߁W߂W߿WW*W=jthenvWuWzWWWthenmihuserscannotdecidesiftheprimitiveisintendedfVthereWthereforeܾWtheyWWtheyareinfactcommandsfrommihusertomihforfrommihfVthis"W?WZWWvWjWuW|WWWWWzWthiscommentshouldbediscussedinconjunctionwithproposa|Vthrough?WWWtitleWtlvށWjWuWWYWYWYWYWYWYWݻWݻWݻWݻWunderstanding,Wuniquely Wup+W>WuseuWW WusetlvsforvariablepoaidentifierrepresentationVused+WW W>Wuseful۬Wuser>WKWusers>WgWhWusesWusinguWvariableWvertical,WweuWW W݄W>Wwell+Wwere>Wwhat WwhenKWwhich W>Wwhole Wwill>WwithW W݄W,W>Wwithin,Wwlan Wwman Wwould W>WKWnÃ!`@ EÃ$@ ?Ã2p@ >Ã60@ HÃDp@ÃRP@ DÃZ@ @Ãg@@ FÃt0@ÃzP@ AÃ@@ GÃp@ Cà @ B HÃ@@p@ Ã`@ Ã@  Gkdone@€kcinstructionsunclear@€€aawaitingresolution@€€0Ih editorialkdoneCtechnicalbinding editorial‚ editorial‚,‚M@‚p@‚‚technicalwaseditorial‚‚kdone@ƒ editorialƒ&ƒJkdone@ƒhkdone@ƒƒƒlnoneneeded@ƒkdone@„„"kdone@„G editorial„gkdone@„„@„ editorial„„accepted…@…2@…Paccepted-modified…m editorial…?cmany܊WܡWWtWuWWlWWmappedېWWmappingDWEW>Wmarch*WWmask-WmatchAWBW`W܁WW6WWWmaterialWmaxWmaximum WWWzWmaximumlengthofthesessionidandothersyntaxaspectsarVVVVVVVVVVVVWܰWܳWܶWܺWܻWܼWWWWWWWWWWWWWmaybeexhaustedifdifferentclassesofdataareVmbbWmeanIWZWWWWmeaningeWWmeaningful_WaWmeaninglessWmeansۄW۸WܟWܢWWmeasurementWmechanism_WaWbWܘWWW W Wmechanisms_WܛWܦWWWmechansimWmedia'W(W)WDWېWۖWWWIWܠWܢWܤWܰWܺWWWWWWWthodۈW(W\W{W|W}W$Ac^The length does not match the TLV representation of section 6.3.4.1.4 where length is 2 octetsd354g2251pWۈWەWWWWWWWWWaddressedWaddressesܰWWWWaddswWadequatenWadequatelyەWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWWadvanceۅWadvertisementWadvicedܖWaffectܳWafterۅWۇWۮWfWWagain+WWagnosticܭWܰWagreedܕWaidWWaimingܗWair۽WairportWaksingWcincorrectrWwWWgWݗWݾWWWWWincorrectuseoflinkcommandindicationwhenacommandisaVincorrectwordgVincorrectly!WWincorrectnesssincreased WincrementalWW.Windefinite۰Windependence(WindependentܠWܰW}WW8WnW1WWWWindicateۅWwWWWWWWlWindicates܄W,W3WlWWindicatingWindicationOWPWQWRWSWTWUWVWWWWݍW>WޖW5W?WWWWWWWWWWindicationsۅW-WiWindicatorWindicatorsWindispensableWinefficiencies W WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWatorsWinefficienciesWc bcarriedyWzW{WWWށWދWތWcarriesW'W}WxWzWcarryܕW WݍWWcarryingWcaseAWW#WݎWݗW WޏWWWWW W*W1W8WlWcase2ifthenumberofoctetsoccupiedbythevaluefieldiݗVcases#WAW۰WWQWW'WWWWWWWcasting6WcategorySWWcatualwWcatuallengthofthevaluefieldwVcause WۉWWcdmaPWcdma2000 WtWW%W'WWcdma2000-hrpdRWcellualarPWcellularWPW>WuWWW^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^WWWWWWWWWW+W,W.W0W7W<W>W?WIWchangeasfollowsܤVchangebecommunicatingtocommunicate7Vg^a7.4.12.1.167.4.12.1.2R7.4.13`7.4.13.17.4.13.27.4.14kg7.4.14.1.2S7.4.14.1.3#7.4.14.2.2ৃT7.4.15.1.1iއ7.4.15.1.2wxz7.4.15.1.4l7.4.15.2.2ܕܖ|}ވy7.4.15.3N7.4.15.3.17.4.15.3.2~{7.4.2L7.4.3M7.4.47.4.4.157.4.4.1.1IJ7.4.4.2.1K7.4.5.1.1݇7.4.5.1.47.4.5.2.27.4.5.2.4L7.4.6҃7.4.6.17.4.6.1.1ރc݈m7.4.6.1.27.4.10.1.27ۃ7.4.6.1.3d7.4.6.27.4.7.1.2ێ7.4.7.1.4hMo7.4.7.2.2ۄ7.4.8g7.4.97.4.9.17.4.9.1.2N7.4.9.2.2O8.1pqe 8.2.1rsԃpq8.3tvw fݲ|W r8.33.1V8.3.1 gggggggggggggggggggggggggggggggggWW-W SbA 33  33  )c  TT    TT  )c    )c  H Function itself, may discover additional properties of the link before selecting it for establishing connectivity.H@A 33  33  )c  TT    TT  )c    )c  cA31. This is a link layer indication which should only be received by the MIH function, not by any upper layer. 2. To pass this notification to an MIH user, need to add "MIH Link Detected" event to MIH_SAP, which is not currently defined. An alternative is to disallow passing this link event to an MIH user.3d548g2296vestablishing connectivity.H@H@idbsuggestednewpoalistۋWsuggestion$suggestionsWsuitabilityTWsuitablePW|WWW>WsupAWsupplement&W2Wsupplementtitlebyappenidngfromaremoteserver2Vsupplementwith3gpp2standardsreferencesasaminimumsugg&Vsupport W?WAWpWېWەWۺWWvWWWW WWsupportdisqueryWsupportedAWLWېWTW|WݖW[WހWނW|WWWWWzWWWWsupportedforthistypeofqueryހVނVsupportedindraft-ietf-geopriv-rݖVݖVݖVv-rݖVV-ietf-geopriv-rݖVݖV-ietf-geopriv-rݖVVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVނVameters|WWctoWWWWWWWWWW WWW+W0W1WKWLWOWPWaW{W}WW݇WݍWݐWݒWݕWݖWݘWݛWݸWWWWWWWWWWWWWWWWWWWWWWWWWW W"W#W$W%W)W*W,W/W4W5W>WOWYWaWdWހWށWނWރWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWރWoWoW b$"3GPP systems already broadcast...."c:Add "s" to "systems" in "3GPP system already broadcast..."d243g2244{k) done 2006/09/21 E Ulises Olvera^ Editorial _32`39a5.8.2b9"...described in Table 33a..." Also need to add Table 33acvChange "table 33a" in line that quotes "...described in table 33a, a direct...." Note: that Table 33a does not exist.d245g2245p\This is technical, and someone needs to provide Table 33a! - clarified with changes from 195{k) done 2006/09/21ddial_35`8a6.1.2b:"... from one access network to another will result in..."ceRemove the "s" from "results" in the line "... from one access network to another will results in..."d261g2246{k) done 2006/08/28 E Ulises Olvera^ Editorial_37`36a6.1.5.2b "IEEE 802.11"c$Separate "IEEE802.11" into two wordsd278g2247{k) done 2006/08/28 E Ulises Olvera^ Editorial_40`29a6.2.3b"Link Commands originate..."e -vthisۋW۔WەWWWRWqWܐWܐWܐWܐWܐWWWWWW0W:WFW݄WݓW4W5W7WSWnWthisisdesiredbutwecannotmandatethiscertaintechnologܽVthiswillbehandledseparatelyforalsuchiesandappropriVthoseەWthreadSWthresholdTWthresholdsaWthroughݓWthroughoutWtime-interval\WtimeoutۅWtitle)WtlsWtlvܗWtlvsZWܗWto*W0WBWQWRWSWTWZW[WێWەW۬W۳W۴W۵WWWW W=WHW`WܐWܗWܛWܢWܽWܾWܿWWWWWWWWWW WW W1W2W:W;WDWFW{W}W݀WݏWݓWݜWWWWW/W1W4W5W6W7W>WBWCWSWdWfWnWtodayܗWtoo{Wtoward3WtransactionsݓWtransparent*WtransportW HbBhe currency value taken from http:www.jhall.demon.co.uk/currency/by_country.html The size of the string is derived using the Length of the Information C elements. Unit 1 The unit of the cost 0: second 1: minute TQXlEPek YewFTanGMember^ Editorial_66`1a7.2.2bChange Section 7.2.2.1 & Table 14 to reference contents of MIH Link SAP primitives. Change Section 7.2.2.2 & Table 15 to reference contents of MIH_SAP Primitives.cThe content in section 7.2.2.1 & section 7.2.2.2 and it respective Table 14 &15 is not in sequential order with the content in Section 7.3 and 7.4d491g2211p$move Link Detected to align with 7.3{k) done 2006/09/21 2006/04/2814,15nEPek YewFTanGMember^Technical (was Editorial)_31`60a5.8b.Remove section 5.8 or include as informative. ormative. P Primitives.cThe content in section 7.2.2.1 & section 7.2.2.2 and it respective Table 14 &15 is not in sequential order with the content in Section 7.3 and 7.4d491g2211p$move Link Detected to align with 7.3{k) done 2006/08/28 2006/04/2814,15 nEPek YewFTanGMember^Technical (was Editorial)_31`60a5.8b.Remove section 5.8 or include as informative.  .܋cd884g2328{k) done 2006/09/21Marked܌ENada, Golmie, Member^ Editorial_145`12bA|Replace "Reception of the specified SDU was acknowledge at L2" with "Reception of the specified SDU was acknowledged at L2" |@Af 33,  337 33h  33t 33fcAFSyntax error in "Reception of the specified SDU was acknowledge at L2"F@A> 334  33? 33>d886g2329{k) done 2006/08/29 ܍ENada, Golmie, MemberGMember^ Editorial_147`34bDUpdate the number of the item starting at the "TYPE_IE_POA_LOCATION"cDuplicate number 10d891g2330{k) done 2006/08/29Marked ܎ENada, Golmie, Member^ Editorial_94`39b8Add "QueryResourceList" at the end of the parameter listc*The parameter QueryResourceList is missingd639g2331{k) done 2006/08/29 ܑEWolfgangFGroetingGMembervofWWܬWܾWWWWWWWWbreplacelinkcommandoriginatewithlinkcommandsoriginate8Vreplacelinkgoingdownwithlinkgoingdown܈VreplacelistofnetworkslinktypeswithlistofnetworktypVreplacemacmobilenodewithlinkidentifiergVhVindicationwithlinkcommandrequest9V9Vplacelinkcommandindicationwithlinkcommandrequest9V9VlistofnetworktypJVreplacemanyuserwithmanyusers܊VreplacemihbymihfinentiredraftܥVreplacemihgetinfoindicationwithmihgetinforequestOVreplacenetworksecurityandqualityofsecuritycapabilitie<Vreplacenumberofparametersinlinkparamterlistwithnumber_VreplaceperformanceofaccessnetworkswithaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1Vreplacereceptionofthespecifiedsduwasacknowledgeatl2܌Vreplaceresourceretentionstatus20withresourceretention܇VUcThis command is sent by current MIHF entity to target MIHF entity to allow for resource query and handover preparation. Change the term cutrrentd305g2249wAccepted{a) awaiting resolution 2006/09/21 2006/04/28EHongFChengGMember^Technical, Binding_41`43a6.2.5.1bIRemove this Command since it is covered by itme 9 of Table 3 as an Event.c:Item 9 of Table 4 sounds more like a Event than a Command.d306g2216v MIH Link Handover Complete event is very different than MIH Handover Complete command. We may need different names for handover commands.wRejected{a) awaiting resolution 2006/09/21 2006/04/274EQiaobingFXieGMember^Technical, Binding_41`49a6.2.5.1bA7Remove "MIH Network Address Information" from Table 4.7@A  33ccctbl 4EPeretzFFeder^Technical, Binding_41`36a6.2.5.1b................ ---------------------------------H hAbE\ to query the information in a more flexible and efficient manner. As part of defining this schema the MIIS may also identify a set of basic information elements that may define the core functionality of different implementations of MIIS. Other information elements as they are added may become part of the more extended set of MIIS capabilities.  @A.  33  :  )c;  <  TT@    TT  TT-  TT.  )c3  Y  TT  p  TT   TT.cAjText needs improvement. A lot of discussion is speculative in nature and can be removed from this section.j@A  33d322g2277iSubir ined.cyThe relationship or mapping between MIH_Link_SAP and media dependent SAPs is critical to understand but is not discussed.WKclinkparametertypedefinitionsisinsufficientandneedsto@linkprimitivecanonlybegeneratedbymihfunctionnotfro@}list@3located@macmobilenode@emacro@rmanagement@many@may@mean@media-dependent@messages@imicro@>mihۃ=jmihcapabilitydiscoverprocedureneedstobedistinguished@miheventderegisterhasnotbeenexplicitlymentioned@Vmiheventregisterhasnotbeenexplicitlymentioned@;mihlinkparametersreportindicationcanbegeneratedwhen@issing@>missingreferencesfrom3gpp2@&mode@morecallflowsshouldbeaddedtoshowhowmihprotocolis@dmoved@necessarily@needed@needlessly@needs@pnegotiated@@network4networkdetectiondefinitionisredundant@new@newlinkidentifier@nms@node's@Pnon-3gpp2@Nnon-adaptiveness@andmediad@"cresultsݑWWWretention܇Wretransmission W WWretransmissionsWretransmitWretransmitted&WretrievaltWuWvWretrievelWIWtWvWWWretrievedtWuW<WretrievingtWuWWreturnۄWWtWuWWWWreturningWreturnsQWWreverse WrevisedހWނWrewardWrewardthissentenceVrewordWWrewordthedescriptionentryoftable18thisfieldisintenVrework>Wework>W>Wbout/WrouteWrouterW:W+Wrouters:WrrcCWrregisterrWWݲrttWWW Wrules W W WWrunWrxlevncellFWGWHWIWJWskWsafeWsaidxWsalientܨWsamݛWsame+WېWWWWW W.W/W:WIWZW܄W܅WܠWܩWܼWWWWJW[W~WWcenarios\WۈWlbgoing WQWۅWRW܈W#WWgprs?WGWIWlWmWgranularityWWW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!WhandleWhandledWhandoff)WJWhandoff/handoverܜWhandover W"W#W,W/W0W5W?WOWPWRWVWWWfWpWuWvWWۂWۇWۉWۋWەWۻWWWW#WRWfW܀W܅W܉WܤWܳWܴW)W|W݊WݍWWWW!W"W#W.WAWXWYWޞWޠWޡWުWޭWޮW޳W޽WhandovermoduleshouldbereplacedwithnetworkselectorAVhandover/switchingWWhandoverackۋWhandovermodeۂۋWgWhandovers,W?WAWQWUWuW:WYNcswitchۃWێWW+WWWWWWswitchingWsynchWsynchronisationWsynchronousWsyntax5W6W8W<WGW^W_WaWfWiWlWoWpWrWtWvWwWxWyWzW}W~WW܀W܃W܆W܇W܈W܊W܋W܌W-WWWWsyntaxerrorandconfusingsentenceincontrolthebehavioriVsyntaxerrorin3127reserved}VsyntaxerrorinadditionalidentifiersarepresentthathelptVsyntaxerrorinafterupperlayerentitiesmakeshandoverdefVsyntaxerrorinalsoknowaslowerlayers6VsyntaxerrorindeliversthismessagetothemihfoVsyntaxerrorindifferententitiesmayrregisterwithrVsyntaxerrorinlinkcommandoriginate8Vsyntaxerrorinlinkgongdown܈Vsyntaxerrorinmanyuser܊Vsyntaxerrorinnetworksecurityandqualityofsecuritycap<VsyntaxerrorinnumberofparametersinlinkparamterlistH AbAChange text to: Depending on the type of mobility support, for different types of information elements may be necessary for performing handovers. For example in case of horizontal handovers across different PoAs of the same access network information available from lower link layers of access network may be sufficient. In such cases information elements like intra-technology neighbor reports and other link layer information required during handovers is directly available from the accessB network. In such cases the availability of higher layer services offered by the network typically does not change appreciably across different network point of attachments. On the other hand during vertical handovers the mobile node may move across different access networks. In such cases there is a need to select appropriate PoA in the new network based on both optimum link layer connectivity as well as availability of appropriate higher layer services to permit service and session cont CmemberܖܚܛܟܠܡܣܤܥܧܨܫܬܭܱܾܰܵăǃɃʃ˃̓΃σЃ҃Ӄԃփ׃؃كۃ݃ރ߃ !"#$&'()*+,-./0134567888888888888888888888888888888888888888888888888888888888888888888888888888888888888888ode and occupies one byte." with "the list of events that may be carried in a message.Each command is represented by a command code and occupies one byte."@2553 2006/04/28HfcrateGWIWJW:WWlWmWWzWratesWratherWW WW%WWrdf0WwW}WwWxWyWzW{W~WWWWWWrdfresourcedescriptionframeworkshouldbeaddedtosectio0VrdfresourcedescriptionframeworktechniquewasdevelopedawVxVyVzV{V~VVVVVVrdf/xmlWWre-usedWre-writtenWreactWread-WWiWreadabilityۮW5reader݃Wreadiablity4readilyWWreading݃WreadsۨWreally WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWܧWWreferto802.21asieee802.21consistentlyinthedraftܧVreferenceW!W$W۬W۽WWWWWDWEWܪWܯWWWWR cA)The inclusion of "MIH Network Address Information" primitive in 802.21 is not sufficiently justified. Both the requester and provider of "Network Address information" will be an upper layer entity, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33d307g2270i Ronny KimmRejectedvby comment 597w Superceded{a) awaiting resolution 2006/09/21 2006/04/244EPeretzFFeder^Technical, Binding_41`65b8Include contribution 0626-00-000_Link_Get_Parameters.doccAaPer last (March 06 - Denver) accepted comment resolution, add a new commnad : Link Get Parametersa@A>  33  %  33>d308g2250v6 Updtae the parameters based on changes to the draft.wAccepted{a) awaiting resolution 2006/09/21 2006/04/28ESrinivasF Sreemanthula^Technical, Binding_83nding_83nding_83 cbutWޖW>WYWkWtWuWWWWWWWWWW WW7W?WmWWWWWWWW"W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WtawhenthisinfoquerytypeisspecifiedinfoqueryparamVrdf/xmlWre-define2W3W6Wre-definethelinkparametertypeasapairoflinktechtechs2V3Vre-definethelinkqualityparametertypeencodingtableas6Vre-verificationCWre-visit6WreadWreaderWreadersW5WBWreceivesWreceivingWWreceptionCWWrecipientWrecommendediWredrawOWredrawthefiguretoindicateallpossibilitiesordeletethOVredrawingpWreevaluate>WreferٻWټWreferenceW_WgWWW$W2WڟWڣWWWreferencedDWڟWڣWreferencesWWfWpWqWڟWڣWWocissueېWWW>W WissuedWW>WWissues#WܭW>WWWWWWWWWWNW_WaWbWeWiWpWvWwWۄWۅWۆWۇWۈWۉWۋWېWۓW۪WWWWWWWWWWWW%W&W'W*W-W.W:W=W@WFWZWcWsW|W܄WܕWܖWܤWܩWܱWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWWW!W%W+W0W2W:WJWaWyW݂W݅W݆W݇WݍWݏWݐWݬWݮWݯWݰWݱWWWWWWWWWWWWWW W*WEWFWGWHWKWOW^WdWfWlWnWoWޖWޗWޟWޫWWWWWWWWWgXbhandoversW|WWWWhandoversduethemobilenodemovementmaybehorizentalintVhardWhardwareWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!WcommonWcommunicateځWcommunicatesٌWکWcommunicatingٌWځWcommunicationIWWeW}WWcompleteWW!WCWWWWWcompletedCWWcompletelyW WcompletionW112`5bA\Replace "different entities may rregister with" with "different entities may register with" \@Af 33   33) 33M  33U 33fcA7Syntax error in "different entities may rregister with"7@A> 33(  331 33>d65g2545 2006/04/29g2546 2006/04/28kcsectionW#W(W)W+WAWKWrWەWWWW-W0W;WAWBWYWhW܁W(W*WHWzWW݋WݽWWWWWWW2W8WCWYWlWnW|WށWރWބWޅWވW5W6W>WXWpWsWWWWWWWWWWW W W7W<WUWiWkWvWwWxWyWWWWWWWWWWWWWWWWWWWWsection46.3.8Vsection5.4.3Vsection5.8.3isjustaboutgeneralusageofmihservicesby+Vsection6.2.4saysthatfigure18showstheflowforlocala7Vsection6.3.4isbettertobeplacedbeforethecurrentsectpVsection7.1.1doesnotmentionthelsapsforwiredmediaVsection8.48.4.1-8.4.2VVVVWWsecurityW<WܢWܼWܾWWݏWWsecurity/qosܰWWbpowerW6WpoweritdownVpppWpptۄWۅWۉWۋWzW݃WWWWWW7WWpramaetersۉWprarametersWpre-definedtWtWifiersarepresentthathelptoanalVwitheitherNVreplaceconceptualabstractiondescribingtheinformationtr٬VreplacedeliversthismessagetothemihfwithdeliversthisVreplacedifferententitiesmayrregisterwithwithdifferentVreplacefacilitieswithamorecleartermUVreplacelinkcommandindicationwithlinkcommandrequestٰVreplacelinkcommandoriginatewithlinkcommandsoriginateٯVreplacelistofnetworkslinktypeswithlistofnetworktypVreplacemihgetinfoindicationwithmihgetinforequestVreplacenetworksecurityandqualityofsecuritycapabilitieٳVreplacenumberofparametersinlinkparamterlistwithnumberVreplacepppwithnetworkconnectivityprotocoltVeassignedidenٺV_‚tCDC‚uNP>‚wݛl\fᄃ‚xSkᆃᇃ‚yLQR‚zTUI‚VWyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy‚1ۂۋ‚2‚3Ã! 4Ã!@<Ã!`Ã!pijkÃ!lmnÃ!oÃ"pqÃ" rstuÃ"0vwێÃ"@xÃ"Py۔Ã"`+Ã"5=Ã"Ã"zÃ#0Ã#@Ã#PJÃ#pÃ#{|Ã#}~Ã#ۈÃ$`67ۇÃ$p89Ã$>Ã$Ã$ۏÃ%-Ã%`Ã%ۀÃ%Ã&ہÃ&ۉ`2 ]ۀہی۔۬ۃ-0J0#ۏ۞@"&'SPD`۠pۢƒӃ)p۩T%JW K‚!2ۄ܃ ObS ^Technical, Binding_113`9a8.3.1bvProvide RTT estimation algorithms or rely on the underlying transport to carry out RTT estimation and retransmission. cAeThe rules here seem to imply that receiver processing could be dependent on RTT estimation. However, since the receiver is not the transaction initiator it is not clear which round trips should be used for round trip estimation. Note that RTT estimation from link type is not possible with IP transport since the buffering delays are not deterministic. ed714g2296vssee also 709. RTT should be provided by transport. if needed. Make text change to make it clear RTT is an example. wAccepted-Modified{k) done 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_114`8a8.3.2.3b(Define the scoping rules for the TID. he TID. Member^Technical, Binding_113`9a8.3.1leanorFHepworthGMember^Technical, Non-binding_59`43r^Technical, Non-binding_59`43_53UV{k) done 2006/09/21MarkedESanjeevFAthalyeGMember^ Editorial_43`13a6.3.1bRemove "access to"cSuperfluous segmentd325{k) done 2006/08/29 ESanjeevFAthalyeGMember^Technical, Binding_43`54a6.3.2bBInsert "or could be maintained in an internal database by the MN".cRemove limitationsd336i Vivek GuptamAcceptedp/Added at the end of para.. seems to read betterwAccepted{k) done 2006/08/29ESanjeevFAthalyeGMember^ Editorial_43`4-5a6.3.1bCChange "point of attachments" to "points of attachment" or "PoA's".c Plural formd332{k) done 2006/08/29 ESanjeevFAthalyeGMember^ Editorial_44`11a6.3.2b+Change to "may influence handover decision"c Improved grammar (verb vs. noun)d342{k) done 2006/08/29 ESanjeevFAthalyeGMember^ Editorial_44`11-12a6.3.2bY"Other information may be vendor/network specific, and could be specified appropriately."c Streamline.d363197n}ZclinkparametertypedefinitionsisinsufficientandneedstoGVIVlVmV!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!VJVVlinkstatusparametershouldbedescribedhereinmoredetaiݽVlinktransmissioneventsitisnotclearwhyweneedthisfoVlinktypenetworkidentifierparameterisrequiredformihuaVbVcVlinkupmacaddressnotdefinedin3gpp2usesectorid128biVlinkuprequestandlinkupresponsearenotdefinedintheކVlink-layer6Wlink/mediaܰWlinkedWlinkidentiferݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWWWWWWWlinkidentifierݜWݦWݼWWWlinkparametertype`Wlinkparamterlist_WlinkskWJWWWlinktype W"Wlinktypeoperatorisnotneededunderapoamultipleoperato"V von۳WW-WܛWܬWWW0W"WwWxWyW}W~WWWWWWWWWWWW W!W"W1W8WVW\W~WWWWWonrequestfromcommenterVonrequestofcommenteryV~V8V\Vonrequestofcommenterfurtherclarificationrequired1VontherequestofcommenterwVxVoncelWWone{WށWރWWWWWWoneoctetcanactuallyhold255valuesVongoing WonlyZWgWWWݓWjWWWWWWoperation*W\Woperational{WoperatorWWWoperatorsWqWWWWopposedܾWWWWWݜW"WށWރWWW>WWWorderW"WorderingۋWorganizeZWorganizedZWoriginalZWWotherRWۓW۳WWWWWW W"W>WWWother/futureVWVvvarious۳WWvendorWver Wverified%WversionVWWWWverticalWveryWviaܬWWvoteXWW<WvsWwWWwantWwasWwayUWWW#WweܛWݓWjWWWWWW"WVWWWweacceptthisinprinciplebutthereisnosuggestedtexthVwearefollowingtheitu-tdefinitionofdifferentqosparamVweneedtoinvestigatefurtherifaninformationservercan"VwebHWwellfWۉWWRWݓW"W\WWWW W>WWWwgWwgsWwhat{W\WWW W:WnW|WWwhatarethebenefitsoftheseparametersshouldtheyreallyVwhathappenstomihhandoverprepare\Vwhen۳W{WݓWWW%WwherefWWWWmWxcnetworkidentifeirshouldbelinktypeݺVnetworkidentifierisaconfusingterm]VnetworkidentifiershouldbelinkidentifierVnetworkselectionistheprocessbywhichamobilenodeoraܡVnetworktypesrelationshiptopreviousnetwortypedefinitioVnetwork-basedWnetwork-layerܡWnetwork-related:Wnetworks"WۋWWW[WܡWWWWYWtWWWWWWWWWWWW!W'W<W?WtWWWnetworktypesZWnetworktypesshouldbelinkidentifierZVneutralWnever.WAWAWAWAWAWAWAWAWerݼVneutralWnever.WAWAWAWAWAWAWAWAW24c 4/24/2006dTechnical, Binding>ޅFTaniuchi^Technical, Binding_138`21a8.5.4.2bAThis message is used by MIH Function to retrieve value of different Information Elements. This is used as a response to MIH_Get_Information.request. The length of IS QueryType is exactly one query type. @A>  Y 33Z >c5In Section 8.5.4.2 the description is not correct . d861g2432wAccepted{k) done 2006/09/21 ކEKenichiFTaniuchi^Technical, Non-binding_140a Annex A-1bmEither replace with euqivalent primitives that are defined in the specification or remove these primitives. cKLink_Up.request and Link_Up.response are not defined in the specification. d871g2433pBredraw - handover command exmaple procedures are being re-defined.v!Replace .request with .indicationwAccepted{h) defer to next round 2006/09/2130އEKenichiFTaniuchi^Technical, Non-binding_106`23a 7.4.15.1.1b4.15.1.1b4.15.1.1bKenichi:bAdd the missing parameter. Add description for oldLinkIdentifier and New Link Identifier. Clarify at what instant the new link becomes operational? cAXMIH_Switch.request ( SourceIdentifier, DestinationIdentifier, HandoverMode, NewLinkIdentifier, OldLinkIdentifier, OldLinkActions ) parameter missing. When handover mode is MBB, would the MIHF handle the route table entries to ensure that the right link will be used at the right time? X@A> 33|  33 33>d603g3253vAdd the missing parameter.wAccepted-Modified{k) done 2006/09/21EVivekFGuptaGMember^ Editorial_114`29a8.3.3b)Replace bytes by "octets" in entire draftcReplace bytes by "octets"d736g3241predraw{k) done 2006/09/21F-25EVivekFGuptaGMember^ Editorial_140aAnnex-A1b"Draw figure 30 in Landscape formatpe formatape formats'c8.5.2.1)W8.5.2.3)W8.5.3.19W8.5.4.1ބW8.5.4.2|WޅWވW8.6.1.1W8.6.1.2W802W802.11[WWWWWW#WW802.11pWW802.16W4W5W>WW#WWW802.16eW802.1xWWW1xWWWWܸW802.3WqW87یW9W;Wa!W"W$W-WAWFWGWHWIWJWLWMWOWPWQWRWSWTWUWVWWWZW\W]W_WaWbWfWiWjWkWmWnWoWuWzW{W|W}W~WہWۂWۄWۅWۆWۈWۉWۋWېWۓWەW۞W۪W۵W۶W۽WWWWWWWWWWW W WW"W+W/W2W9W:W=WIWOWZW\W^WeWiWkWyWzW{W|W~W܂W܃WܐWܗWܘWܟWܡWܢWܤWܩWܬWܭWܷWܺWܻW"ghENada, Golmie, Member^Technical, Non-binding_89`26bDefine the list of Actions that can be taken and provide encoding for the values consistent with section 8.4.2.13 on page 125. Add text as per section 8.4.2.13 on page 125n page 125҃Ӄԃփ׃؃كۃ݃ރ߃ !"#$&'()*+,-./013456789<=>?@AEGHIKLMNOPQRT^abcdefgijklmnpqrstwz{}݆݈݃݅݇݉݋݌ݍݎݐݑݒݓݔݕݖݗݘݚݛݜݭݲݵݸݹݺݽݾݿʃу҃ӃԃՃ,-./2458:>@ABCILMOVYlnwޓޖ1256=>?WXYZ[\]^_`abcdefghij bbit1WlWmWoW}WWWWWbitmapTWUWVWWW1W6WWWWbitsTWUWVWWWݗWW}WWWWlWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhere a standard transport layer could provide advantages over the techniques considered here include: piggybacking of acknowledgement semantics on arbitrary reverse traffic; windowing allowing multiple outstanding g3105 2006/04/29conGWIWۃWېW۟WۦW۳W۽W:WYWhWܕWܡWܫWܬWWW WWW+W6W@WaW}WWWWWWW W"W$W%W>WBWYW>WWWlWmW|WWWWWWWWWW WWWWW8W<WVWlWmW|W}W~WWWWWWWWWWWWonpage41itisstatedthatlinkconfigurethresholdscommaaVontheleftsideofthemihfunctionblockthefigure~Vonthetopportionoftheflowmodelpicturethemihcommand>VonceWWWaWbWiWۄWۋW'W:W=W@WKWLWeWzW{WܗWܝWܩWWWWWWWW+W݆WݏWݜWݝWݞWݠWݣWݤWݦWݧWWWWWWW'W/W>WoneofmanyVoneofthestackmaybeVonesەWmBbbecauseIWWWbecomeAWWbecomesWWWWWWWWWWWWWWWWbeforeFWGWHWIWJWSWYWۉWۜWWWWW#W\WܺWW"W2WWWWWWWbeginningۧWWܚW(W*WbehalfMWcWiWއWWbehavioriWkWW8WbehaviourWWbeingOWWbelongWbelongs\WbelowGWHW\WjWWWWbesetۉWbest݂Wbetter۾WWWWWW-W[WWbetterunderstandandclarifytheamountofworkneededtoi۾Vbetween W"W'W?WDWZW]WpWqWuWxWۣW5WgW܅WܟWWW WW,W1W2W3W4W5W7W8WpWޞWޠWޥW޽WWWWWWbinaryܕWbindWbinding~WbitFWGWHWIWJWND8csyntaxerrorinresourceretentionstatus20܇Vacknowledsyntaxerrorinresourceretentionstatus20܇V܇V܌V܌VMacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhba9a7.3.13.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc c^MacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhbaTechnical, Binding_77`49a7.3.13.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc c^MacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhba 21-06-0xxx-Link_Identifier.doc c^MacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345 2006/05/14 2006/04/28ݡE YoshihiroFOhba cthewordingislooseandlargelyrepeatingwhathasbeensaixVtheirۃWVWWYWtWuWWWWWWthelengthvWݹWthelengthdefiiteݹVthemېWYWܚW݃WWkWWWWWWWWWW݃WWWWWۈWېWWYWܚWWW݃WWWWWۈWېWWYWܚWWW݃WWWWWۈWېWWYWܚWWW݃WWWWWYWܚWWW݃WWWWWWWWWWWWWthereWW-W?W@W_WaWuWۇWېWۦWWWWW WDWEWMW\WcWjWܐWܖWܘWܩWWWWWWWW WW:WSWeW݂WݥWWWW W2WfWgWޕWޗWޜWޝWޫW޽W޾Wthereare256possibleencodingsforgeneralVjcreplacedݜWWAWBWCWDWEWFWGWHWJWKW[W]W^W`WaWbWgWhWreplicating WrepositoryWrepresentFWܗWWWrepresentationہW=WAWBWܷWWWWWWWWWrepresented/W0W1W2W3W4W5W6W7W8W9W@WzW{WܬWWWWWrepresents=Wreques/responseܙWrequestۂWۃWۄWۆWۇWۈWۍWێW9WMWOWQW`WkW܀W܄W܅WܕWܗWWrequestsourceshouldberesponsesourceۍVrequest/responseܺWWrequestedaWrequester:W;W<W=W>W_WaWrequestingW\WrequestsiWmWܕWܗWrequestsetsWmWrequireWWrequired"WW)WWWWrequirementWWrequirements۟WrequiresWrequiringWOW WrerenceUWYW:WP GbcA@Syntax error in "The encoding format is defined as table below."@@A> 330  33> 33>d417g2257{k) done 2006/09/21HENada, Golmie, Member^Technical, Binding_50`26bALine 26, set the Value information to "Cost of accessing the network. The encoding format is defined in the table below" Line 29, replace the example with a new table containing the following information Syntax Length (octets) Note Currency Variable A non NULL terminated string representing tesenting t99g2255{k) done 2006/08/21 GENada, Golmie, Member^ Editorial_49`38bAiReplace "The encoding format is defined as table below." by "The encoding format is defined in Table 8."i@E3 lbtheWWW WWWW#W,W/W2W3W5W7W:WCWDWEWGWHWIWNWPWQWRWSWTWUWVWWWYWZW]W`WhWiWkWlWmWoWtWvWwWyWzW{W|W~W܁W܃W܄W܅W܆W܉W܋W܌W܍W܎WܑWܔWܕWܚWܟWܡWܣWܤWܧWܫWܬWܱWWWWWWWWWW WWWW(W)W*W.W0W3W4W5W9WIWKWQWaWiWkWwWzW{W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W{W{Wc7CWtWuWWlWWWW7.1.1W7.1.2CW7.2.1.4>W7.2.2ݛW7.2.2.1lW7.2.2.2lW7.3lW7.3.11.1W7.3.13ݛWW7.3.16W7.3.16.1W7.3.17.1WW7.3.17.3W7.3.18.1W7.3.18.3W7.3.7.3W7.3.9.1W7.4WlW7.4.12W7.4.13WW7.4.14.2.2W7.4.4.1.25W7.4.5.2.4ݽWW7.4.7gW7.4.7.1.4hWW8ܑWW2WW8.1qWW8.2.1rW8.3W8.3.1qW8.4W8.4.1-8.4.2W8.4.2.13hW6W8.4.2.176W8.4.2.2W8.4.2.23ށW8.4.2.24ރW8.4.2.8YW8.5tWuW8.5.1.2WWWjWkWmWnWoWuWzW{W|W}W~WہWۂWۄWۅWۆWۈWۉWۋWېWۓWەW۞W۪W۵W۶W۽WWWWWWWWWWW W WW"W+W/W2W9W:W=WIWOWqsܓ{k) done 2006/09/21 2006.03.05T18ܔEWolfgangFGroetingGMember^Technical, Binding_116`18a8.3.3.3bA6Change the size from 6 to 8 bytes in the figure 27 6@A> 33  33>cKSize of MIHF Fixed Header is not consistent with that depicted in figure 28d756g2264wAccepted{k) done 2006/09/21 2006.03.05F27ܕEWolfgangFGroetingGMember^Technical, Binding_107`58a 7.4.15.2.2bATLV: When this InfoQueryType is specified, the InfoQueryParameters shall be a binary string which encodes an Information Element TLVs that carry Requests responses as defined in Section "Information Request and Response".@A  33j  m 33  33   33  33 33l, Binding_116`188/03r]cisGWNWNWNWNWW  33] r 33Rtation, show that first octet is length of length which is followed by the value length.c=Diagram does not clearly represent the text below the figure.d405g2254 2006/05/14 2006/04/2820EEleanorFHepworthGMember^ Editorial_48`30a6.3.4b~For the multiple octet length representation, show that first octet is length of length which is followed by the value length.c=Diagram does not clearly represent the text below the figure.d405g2254 2006/05/14 2006/04/2820d.d400g2253 2006/05/14 2006/04/287EEleanorFHepworthGMember^ Editorial_48`30a6.3.4b~For the multiple octet length representation, show that first octet is length of length which is followed by the value length.c=Diagram does not clearly represent the text below the figure.d405g2254 2006/05/14 2006/04/2820inding:,bidentifierZWۉWW[WkWmWWWݒWݔWݜWWW]WsWWWW@WAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWYWZW[W\W]W^W_W`WaWbWcWWWidentifierfor802.11networks[VidentifiersxWCWtWݸWoWWXWidentifyZWxWmWsWWWidentifyingWWidentityWidsېWCWTWUWVWWWWoWWWWieZWۉWaW܍WtW1WqWrWtWWWWWWWWW8Wieee#WܧW?WWWWW4W5WpWWWWuWWWWieee802.11VVVVVVWWWWWWWWWWWWWWWWۓWWܹWWietfinformationelementsfor802.21V|binthissectionareprovidedintheappendixVinthisstandardinordertoaccess3gppservicesprovidedsVvicesprovidedsVVss3gppservicesprovidedsVVandardinordertoaccess3gppservicesprovidedsVVisstandardinordertoaccess3gppservicesprovidedsVVisstandardinordertoaccess3gppservicesprovidedsVVVVVVVVVntable-7ܹVincludealegendforfigure19bsapbstnetcܵVincludeamentionoftheseevenifistostatethattheyareVincludeatimebasedstatediagramshowingdifferentlinklaܳVincludeclientlocationasanessentialinputparameterinaܽVincludedescriptionofcasewhereinformationrepositorymayܶVincludeexamplesofiereportsandclarifyhowtousethemfܿVincludeguidelinesonratelimitationandtimeradaptationfVincluderecommendationsfortransportoptionseitherinthisܩVtedintable-6thisܼVW^#bretransmissionGWIWۉW WlWmWWretransmissionsWretransmitUWretransmitted&WretrievaltWretrievecWlWބWޅWtWvWWWޅWޅWWޅWޅWWޅWޅWWޅWޅWޅWޅWޅWޅWޅWޅWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'W1W2W3W4W6W7W8W9W<WBWCWEWYW]WaWbWsections>Wsecurity#WseekingLWselectAWselectingSWselection WsendingVWser#WserveNWserver\Wservice#W*W?WAW_Wservices"WAWsesAWsetAWFWGWMW_WshallW W-W.WshouldVWWWZW]Wshows?WsignalFWGWHWIWJWsingle*WIbtowardsAWWtraffic)WtransactionWWWWUWtransferVWWW#W5WܟW|WWtransferredVWtransmissionRWWWtransmitUWRWtransparent*WWtransport#WOWWWxW܋WW W݃W|WWWW WWWWWuW~WWWWtransportiWtransportlayerۋWtraverse7W7W7W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W0x00000002ܚVtypelistdWtypes?WAW_WjWmWW=WJW`WdWܤWtypicallyAWܤWtypicallyinaheterogeneousnetworkenvironmentcomposedofܤVtypo۠Wudp/ipWudp/tcpsWue܋Wuk/currency/byHWumts_W=WunchangeableۂWunclear۫W?Wb 06cd150g2240{k) done 2006/09/21 7ENada, Golmie, Member^ Editorial_35`38bAChange sentence "They traverse through the medium to local MIH Function and are then dispatched to MIH Users that have subscribed for these events within the local stack." with "They traverse the medium to the local MIH Function and are then dispatched to MIH Users that have subscribed to these events within the local stack as shown in Figure 14." at line 40-41. Remove sentence "Remote MIH Events traverse from the remote MIH Function to the local MIH Function and then from the local MIH FBPunction to the local upper layer entities as shown in Figure 14." at line 43-44.>@Af  33  33!  33E  33\  33fcfc06/05/145ENada, Golmie, Member^ Editorial_9`38b to: " N-layer - the N-th layer of the layered protocol stack. "rm "MIH proxy" should be avoided.d114g2391V@ۿESanjeevFAthalyeGMember^ Editorial_28`8-30a5.5.5bStretch diagram horizontallycDiagram needlessly compressedd204{k) done 2006/09/21 ESanjeevFAthalyeGMember^Technical, Binding_28a5.5.5b3Replace "PPP" with "Network Connectivity Protocol".c5Connectivity protocol is being migrated away from PPPd198pABut this is in conflict with the accepted comment 195. PPP is not only present in the figure, it is also referred strongly in the new text accepted from comment 195. Replacing PPP in the figure alone will break the text and reference [28]. The group may need to consider this further.wAccepted{k) done 2006/09/21 Figure 10ESanjeevFAthalyeGMember^Technical, Binding_30`6a5.6.2.1a5.6.2.1a5.6.2.1r this.wAccepted{e) editor disagrees 2006/08/28 Figure 10 ESanjeevFAthalyeGMember^Technical, Binding_30`6a5.6.2.1PP terminologycl, Non-binding_22`20a5.4.3121)KbwordsZW>WsWworkWW>WworkingWworksWwouldUWWW܂W2WWWW WWWWwouldconsiderremovinglinktypeasunnecessaryVwouldn'tWwriteWwritten-WwwwHWݔWqW~WWWxvW&WWWx1~Wx2~Wx3~Wx4~Wxml#WܬWݚWqW~WހWނWWxmlthismaymeanthatquerysyntaxisextraneousandVxmlns~WxrefWxxހWނWWy/n1WyearHWyouWzeroށWރWWWWރWރWރWރWރWރWރWރWރWރWރWރWރWforV1W!WSWiWsWuW۪W۽WWWWW(W=WWWW>W1tableofcontentssectiontitlemissingV1textneedstoimprovesV1thecurrenttextimpliesthatthediscoveryofmihfunctiouV1theinformationelementtypeielistofnetworksrepresent=VIbinthedescriptionfieldreplaceNVinthesectionsbelowVriptionfieldreplaceNVinthesectionsbelowVVdescriptionfieldreplaceNVinthesectionsbelowVVVaddanewsectionassuggestedin21-06-606-00-0000locinfoVaddanewtablecalledscanrequestinfocontainingthefollowVaddanotesayingthathandoverisalsoreferredtoashandosVaddanoteunlessotherwisenotedmediareferstomethod/modeVaddaperiodtothesentenceVaddasentenceatendofparagraphadditionallyoralternatiiVaddadditionaleventcodesڬVaddannexestotheendoftocVaddclarificationintextthatallreferencepointsarewithVaddclarificationtotextV_Alistair`ButtaraMemberb35c 4/24/2006dTechnical, BindingbdottedWdouble-headed~Wdown WPWQWۅWWRW]W܈WW#W6WWWdraftPWܥWܧWܱWWVW(W,W<WWWdraft-ietf-geopriv-rݖWdraft-ietf-geoprivraݕWdraft-ietfgeoprivݘWdrawWdrawfigure30inlandscapeformatVdrive8WWdriveriWdstVWdueIWWWduplicateWduplicatesWduringAWUWWdynamicWe?WWWۖWwWWWݎWݔWݖWWWW"W$W%WހWWWWWW'W1W>WzWWeusingamihhandovercompleterequestVVVVV9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WeitherdiscussthismoredetailsordeletethiseventVW [bA Add new subsection(s) and text in both section 5 and section 7 to fully describe the relationship/mapping between MIH_LINK_SAP and the various media specific SAPs. If such a relationship/mapping is not meant to be described in the 802.21 spec, it must be explained. @A  33cAThis is critically important to describe in full detail the relationship/mapping between MIH_LINK_SAP and the various media specific SAPs in 5.6.1. This relationship/mapping is currently missing in the spec.@A  33d229g2249vby comment 215 and Issue #40w Superceded 2006/09/21 2006/04/24\EQiaobingFXieGMember^Technical, Binding_66`44a7.2.2.1bAxRemove "MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" from Table 14x@A  33cc ga6.3.3$o݃ރ+6.3.4ݗp9l6.3.4.1s6.3.4.1.16.3.4.1.2^6.3.4.1.46.3.4.2.3'6.3.4.2.56.3.4.3.1ݘuໃ,6.3.4.3.26.3.4.3.46.3.4.3.5-6.3.4.3.6ܾ16.3.4.6)6.3.5`t6.3.6u6.3.6.16.3.6.2.6.3.6.36.3.6.3.2@6.3.7v6.3.7.2/6.3.7.306.3.8jृઃ:6.3.8.1؃^ݚv6.3.9كzB=ୃ127C7.1D7.1.17.1.2C7.2.1>7.2.2l7.2.2.1یݛ\fᄃᅃ7.2.2.2ᆃ7.2.3.1k7.3.1.3L7.3.10bA7.3.10.17.3.10.3P7.3.11ۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅۅݜ7.3.9.3O7.4ܐ7.4.1ۊ7.4.1.1.27.4.1017.4.10.1.2ۂۋVmJcnotificationSWZWޖWnotificationsWnotifiesWޑWnotifiesnotifyޑVnotifyۅWޑWnotionۼWܬW/WnounW/WeWnounvsverb/VnowWWnssdc>Wnth/WnumberW^WۡW_W~W܍WܓWWWpWqWtWuWWWWWW@WXWlWWnumberofaddressheaderidentifiersisnotneededXVnumberofoperatorsisnotneeded@VnumberedWnumbersWWWobjective*W*WWWWWWWWWWWWWWWWިWWWHW߆WWobtainېWIW݂WobtainedېWܬWWWobtianedܬWobviousQWobviouslyۄWېWoccupiedWoccupieszW{Woccur^WoccurencesܥWoccursۨW WܟWWWocteswWoctet(WFWwWWoctetsW%W&W)W=WAWBWFWWWoduW=W#;]ctherepresentationofnumberpoaisnotspecifiedVtheruleshereseemtoimplythatreceiverprocessingcould VtherulesonhandlingduplicatetransactionsarenotclearsVtherulesstatethatinanycasethedestinationshallnotpVthescanrequestsetsisnotdefinedthelistofscanrequestmVthescanrequestsetsshouldidentifylinkietechnologytoVthescopesectiondoesnotadequatelyaddresswhichpartsofەVthesectiontitlemediadependenceisconfusinganddoesnot)Vthesectiontitlemediaindependenceisconfusinganddoesn(Vectiontitlemediaindependenceisconfusinganddoesn(V(Vindependenceisconfusinganddoesn(V(Vntitlemediadependenceisconfusinganddoesnot)V)VW*W+W1W2W3W4W6W7W8W9WAWKWLWMWOWPWQWRWSWTWUWVWWWZW]W_WaWbWfWgWuWWۄWۈWۊWېWەW:evnotallissueshaveremediesassignedonissuelist@number@ofWon۳optimize@ out@paragraph@'please@poaݜproposed@cr1@Rre-drawing@ /refertocontribution21-06-0690-00-0000-i@yrelationships@remote@replacerequestwithindication@resolutionreturns@lroaming@Tsame@7see413@selecting@lserviceܬsome@specifythesevaluessecuriyandqosinthecontextofacces@standard@%still@ %support@\text  44text a4s@standard@:support@\textܢa4thiswillbehandledseparatelyforalsuchiesandappropri@transportuse۳various@swherever@cwith@waccepted#accepted-modified"rejected-duplicate@{lnoneneeded@G€ @G$xY(cnecessarysWۅWەWWWޖWWWWneed#W+W?W@WSWZW^WpWvW1WYWܾWWWWݍWWW?WXWjWkWqWsW|WWWWWWWWWW W!W>WkWWWWWneedtocorrectmihgetsttausVneedtoexplicitlystatethatbothtypesoflocationinformaVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV8.5.3.19*ٟڻ8.6.1ڼaWa4Va-1٠WWWa2١WڽWannex٠W١W٢W٣WڽWھWڿWWWWgkthewholenotionof802.21asspecifiedintheparistoopt-VtheirWWW Wintheparistoopt-V-Vholenotionof802.21asspecifiedintheparistoopt-V-V0W\WܺWthere\WےWWWWWݴWݻWthereisacommenttoremoveforexamplecomment350ےVthereisanoverlapofthevaluesalreadyallocatedformihfݻVthereforeWthese0W۴W۵WW)Wtheseareadministrativetypepriitivesthatdealwithevent)Vtheseareconsideredasmediaindepedentcommandseachmobil0Vthesearenoteventsbutcommandsaswehavedefinedthemup۵Vthey۴WW WthingsۓWthinkuWWܸWthis"W#W/W0WAWYW\W]WaWbWjWkWmWnWoWzW{W|W}W~WہW۳WWWWWWCW|WܸWܺWWWWݓWW+W-Wesinceseveralplacesinthissectionwetal#VccommaۮWWWWWcommandۄWېW8WmWzW{WKWaWzWWW(W)W>WތWWWWWWWWWWWWWWW#WcommandcodezWތWcommandsېWmW{WWWWW7WmWWWWWWcommandsmaybeinvokedfromupperlayersmihcommandsasweVcommence{WWcommentۯWW;W*WBWWWWWWcomments|WWWWWWWWWcatesWcommunicationەW3W Wcomplete/W0W4W5W9WۇW-W܉W܏W WWWcompletedۂWcompletelyYWܰWcompleteness)Wcompletenessconcisenessgrammar)VcomplexityBWcomplianceWܛWW%WcomplicatesWcomponentsWcomposed:WܤWݐWcomposedofmultiplemediatypesitisthehandoverdecisionݐVcomprehendedW vaddlowhighrangemhzrefertodefinitionintable-6VaddsectionexplainingcssapandlsapjVaddtextinsection6.1.1line37pg33draftd01.00VaddthebelowtextVaddthefollowinginsection8.3.3.3VaddthemissingparameterVaddthisinsection8addidsforcommandsaswellRVaddedWWWadditionalSWWWaddressWݜW"W?WoWaddressed|WaddressesݜWWW?WaddsWadequateWadingWadministrativeW v552IWmW555UWVWWWfW57/58W577WWIW578W583W588W597gWhWiWWW6WWW6.1.1W6.1.5.2WW607MW609mWW626BWCWDWEWFWGWHWJW632W64ێW641zW>W673NW675ZW68W687pWqW7WWWW7-255W7.4.10.2.2ގW7.4.15.1.2W7.4.5.2.4ݽW7.4.8gW704WW W709 W719WWWWWWWWW737;W741WW744XW752/756W+WlW757W8RWWW8-8XW<W8.4.2.13hW8.6.1OW802.11ەWWWjWW802.164W5WWjWWW802.2jW802.21ۓWەWWܛW802.21enablesbothl2andl3transportoptionsV802.3jW803W824WW872iW88ێW892WW5W6W90WWtWW93W>j cmihۃWۄWۅWۉWۋWیWێWېWۤWۭW۽WWW,W2W7WHWYWZWkWmWuW܄WܠWܥWܫWܰWWWWW0W3WAW{WW݃WݛWWWWWWWWWWW WW W"W%W'W(W,W/W4W5W8W>WLWMWOWYWaWkW|WއWވWޖW1W2W5W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W޲W޲W޲W޲W޲W޲W޲W޲W޲W޲WOVYF^technicalbindingVVVVVVVV"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"V"Vblocal W۳W۶WW7WzWW݃WݎWWW4W5W8WW7W>WuWWWWWWWlocality,Wlocally۶WW"W1WWWlocation|W܍WWݖWݘW>WWlocationinformationisencodedinthisfieldtheݘVlocation-informationݘWlofWlogical<WWWlongtitude-resolutiowWloopWlossGWIWJWۉWRWYWlWmWlostRWlotWWWWWW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"WDWlte Wm4Wmac,WNW WpWުWWWmac/phy WޞWW WmachineWmacmobilenodeWW oironnykimNVOVfVgVhViV|VVVV}VVVVVV Vcconceptual WܟWconcerns>Wconciseness$W)WconcreteWconditionsWWconductۉWconfidence:WconfigurableޖWconfigurationۄWZWjW܂W܄WaW5WWnWoWWconfigurationrequestۄWWestۄWۄWestۄWۄWۄWۄWۄWۄWۄWۄWequestۄWۄWۄW5W5WgurationrequestۄWconfiguregWۄWۉWWYW\WkW܂W܄WaWWWFWGWHW{WޔW3WconfiguredۄWZWޖWconfined1WconfirmWWWW>WrWyWzW{WconfirmprimitiveformihcommandisnotdefinedVconflictedTWconflictingۼWconflictsWconfusedWconfusing(W)WۻW۽WW W:WiW܏WܫWWWWWWkWvWyWzWWW]WަWާWWWWWFWGW߄W߅WWWWWconfusingphrasekVvV 3 cAThe protocol does not seem to include any capability to react to or avoid congestion events except as provided by the underlying transport. In particular, there is no mechanism to prevent the initiation of large numbers of parallel transactions, and the retransmission timeout is not adaptive (there is no backoff). This may be acceptable for operation of the MIHF protocol between nodes which directly connected over a single link which has native overload control; however, it would not be anB acceptable approach for operation over IP networks in which congestion in intermediate nodes is not visible. The lack of rate limitation and the non-adaptiveness of the retransmit timer means that the protocol has no way to avoid causing congestion events. d708g2292veed text for such a comprehensive issue, see 32wRejected 2006/09/19 2006/04/28Markedhe paragraph repeats what has already been sufficiently discussed earlier. No need for it here.yAkucschema#WܬWjW|WWWWWW W:WWschemaismandatoryshouldbeoptionalVschemaeWschemeWschemesWscope"WەWWmWܛWܭWWWIWWYW>W\W]W^W_W`WaWbWcWdWeWWWWW WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmogeneousinterferfacVsecondWW݆WW Q{doneWWWWWWW W WWWWdefied"cSpellingd371 2006/08/04 dokhFKhatibiGMember^Technical, Non-binding_47`26-27a6.3.2It appears that reference is to the definition of Operator-Name attribute defined in referenced draft, which is already progressed to revision 06. Relevant information should be copied from the draft and inserted in table or elsewhere, accmpanied by appropriate references.c"Improper rerence to Internet Draftd375w Superceded 2006/08/03 WEFarrokhFKhatibiGMember^Technical, Non-binding_47`26-27a6.3.2b:Insufficient information of intent, to suggest any change.c Vaguenessd382v8Need more clarification and appropriate suggested remedywRejected 2006/08/03 WEFarrokhFKhatibiGMember^Technical, Non-binding_47`26-27a6.3.227a6.3.227a6.3.2ied by appropriate references.c"Improper rerence to Internet Draftd375ember  obATReplace "delivers this messageto the MIHF" with "delivers this message to the MIHF" T@Af 33  33  33?  33I 33fc2Syntax error in "delivers this messageto the MIHF"d658g2300{k) done 2006/09/21pENada, Golmie, Member^ Editorial_108`43bReplace "WHIRE" with "WHERE"cSyntax error in "WHIRE"d678g2301{k) done 2006/09/21MarkedMarkedrENada, Golmie, Member^ Editorial_112`5bA\Replace "different entities may rregister with" with "different entities may register with" \@Af 33   33) 33M  33U 33fcA7Syntax error in "different entities may rregister with"7@A> 33(  331 33>d698g2303{k) done 2006/08/29 tENada, Golmie, Member^ Editorial_115`59bc,UcexhaustiveWWexist۳WWWWexistingWWWexistsWtWexpandedGWIWJWlWmWJWJWJWJWJWJWJWJWJWJWJWJWJWIWJWJWWJWJW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W4W5WexplainthattheremoteflowofeventsandcommandsforfiguV ij1|WtWW1linktransmissioneventsarelocalonlyseeline47page3V108XWW127XWW128XWW14/15W142XWW170WW187=W2WW20+W21-05-0407-04-0000-xjW21-06-0607-00-0000-s+W21-06-0611-00-0000-m|W}W21-06-0612-00-0000-r=W21-06-0612-01-0000-rW21-06-606-01-0000WYW22W23W24wWWrWW24-49W26W3W+WYWW315@W35W3753?W38W4W45tW46tW47W6tW6.3.4.3.3ܾW6.3.8W687qW7.2.1W8.6Wa"WܾW,WvWWzW{WWWWWWaboutjWWWacceptancejWjWjWjWjWjWjWjWjWjWjWjWjWjWjWWWtBWWhWacceptableWWWWhWhWhWcinfoovertlܽVagreedformihfsessionidsV,VWk ,cA  33ndover Prepare", "MIH Handover Commit", and "MIH Handover Complete" are improper for 802.21 scope. The functionality represented by these primitives is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d304g2259i Vivek GuptajHow is Network Selection handled handovers? Is network selection (across heterogeneous links) also part of upper layer Mobility Mgmt protocol like SIP/MIP etc.? If NOT, then some mechanism (albeit better explained) may be needed.k15 2006/04/30T. 4EQiaobingFXieGMember^Technical, Binding_41`32a6.2.5.1bAwRemove "MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" from Table 4w@A  33cc------------------------------------------------------------------------------------------------------------------------ "vAAccept modified text below and also change PoA to PoS below as well " This primitive is delivered from MIH Function on old serving PoA to another MIH Function on target new PoA in order to discover mobile nodes network address related information before handover. Upon reception of this message, the MIHF on target new PoA may either interact with upper layer to achieve enough information or further deliver this message to the MIHF in the network, e.g Access Router with MIHF which may haveB enough information on this message. This may also trigger the network entity, e.g, Access Router or Foreign Agent to send out Mobility related messages directly to the mobile node. "@A  33x  {  33    336 =  @  33A 33wAccepted-Modified{k) done 2006/09/21 #EPeretz9cafewconcernsregardingtable13>Vafurtherexpansionoftheieslistedintable6isneededfVageneralcommentwithmiheventandlinkeventsisthatitVageneralmechanismfortlvtypeisquery/responseisdiscusValinkupeventmayalsocarryipaddressrenewalindicationݍVanumberofcommandshavebeenaddedtoallowtheupperlayeVasectiononsystemmanagementismissingVa-1Wabbreviation݌Wabbreviations݋Wabbreviationsfordhcpandpppshouldbeaddedinthissecti݋VabilityWableWacceptance݃Waccepted;Waccess$W\WۉW۳W۷W۸W۽WWWWWWW1W:W;W=W@WܬWܾWW:WCW_WuW݂WݏWWWaccessing۾WaccomplishWaccordingۂWۅWW:Waccordingtorfc3753thedefinitionsarequoting:VaccountWaccurateXWaccuratelyWachieve|WWannexۀW~cconsistencyۜ۞WۣWۭW۲W(W*W7WޖWWconsistencycustomaryuseۣVconsistencyofterms۲Vconsistencywithsimilarnearbysectionclauses(V*Vconsistencywithinaparagraph/sentence۞Vconsistent۰W۽WWYWhWܒWܔWW"W#W$W'W/W6WWWWWWWconsistentlyܥWܧWconsistingIWconsistsW'WconsolidatedܤWݐWconstWconstantWconstituted/WconstrainedWconsumerWcontainkW-WcontainedۄW܄WcontainsWcontent۝WlWXWWWWt Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool. _Alistair`ButtaraMemberb43c 4/24/2006dTechnical, Binding*H icA}1. What is a "station's MIH"? Is it a mobile station or base station? Must be clarified. 2. An MIH protocol message, not an MIH primitive, should be used when one MIH requests information from another MIH. If the intention is to imply some architectural characteristics (e.g., proxy based MIIS query), it is not only unnecessary but also improper to overload the the text here. }d660g2318wAccepted{k) done 2006/09/21 2006/04/24MarkedlEQiaobingFXieGMember^Technical, Binding_107`15a 7.4.15.1.4bALChange the text to: The recipient will forward the query in an MIH message to the designated MIIS server (or a proxy function of MIIS). The MIIS server tries to interpret the query request and retrieve the specified information. Once the information is retrieved the recipient responds with MIH_Get_Information.response primitive.L@Af 33  $  )c  29C h)bAR 33   339 33RA  cAnnexes missing from ToCd45g2235{k) done 2006/08/21 2006/04/24C@A  cAnnexes missing from ToCd45g2235{k) done 2006/08/21 2006/04/24QÃۏÃà ކÃ0-Ã@ÃPޗÃ`ÃpސÃÃޑÃÃޒà ܈Ã0܉Ã@܊ÃP܋Ã`sÃp܌ÃÃޓÃRÃܚà ܍Ã0ۀÃ@tÃPÃ`uÃpÃvÃoÃہÃމà wÃ0ۉÃ@8ÃP9Ã`:Ãp;Ã<Ã=Ã>Ã?à @Ã0AÃ@BÃPCÃ`D dDT ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_Bctherefore+W`W:W2W6WWWWWWWWWWWWtheseWW1W7WRWܕWܰWWWW>W\WaWtWuWWWWWWWWWWWWWWWWthesearecommandsandnoteventVthesecasesarereferringtoipv6accessnetworktopologiesVtheserecommendationsshouldbehandledbyspecificieee802VVVVVVVVVVVVVVVVVVVVVVVVWTWUWVWWWZW]W_WaWbWfWgWuWWۄWۈWۊWېWەWۥW۴WWWWWWWWWWW%W&W'W)W-W/W:W;W=W@WQWYWZWoW{W܂W܆WܕWܖWܛWܢWܣWܫWܭWܷWܼWܾWWWWWWWWWWVkthatAWCW)W-WgWwWxWyWzW{W|W~WWWWWWWWWWW WWthe"WAWۓW۳WCWW-WdW\WpWtWuWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWWUWVWYWvW}W~WWWWthecommentshouldberejectedforthefollowingreasonsVthedocnumbershouldbe627VthelinklayerqoscharatersticsareavailabletothestaviVthereasonisnotclear0x2161432bitsVthereasonisnotclearwhyisbroadcast/multicastnecessaryVthesectionisdescribingtheidsusedformihfprotocolUVUVUVnical, Binding_4`42a1.6b]Either we delete this dependency for interoperability or we define "state machine" for MIH. c7The specification does not define the "state machine" d33g2415JYKcofW"W#W+WAWGWIWJW^W`WlWqWrWsWۀWۃWۄWۅWۉWیWېWەWۖW۝W۪W۲W۶WۻW۽WWWWWWWWW,W-W.W/W2W3W4W5W:W;W<WAWBWCWHWIWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWNWvcommentersݓWcommentersagreeapplicabletoesandcsbutonlyundercertݓVcommentsZW\WWWWWWWcommitWcommmentLWcommunicationW3WݓWWcomplete\WWcompletingWcomplexWcomplianceܛWcomprehensiveWcomputedWcomputingWconceptsWconcernWconditionWWconditionallyWconfidenceQWWconfidencelevelisvagueandit'snotclearifvariouslinkV64g2320iYoshihiro OhbakAJust defining a structured data as a tree or trees is not sufficient. A query language that can understand the structured data is needed for efficient information retrieval. Without use of a query language, the way to retrive information on the structured data is quite limited. That is why XML/RDF query is supported to address this issue. It is recommended to read 21-05-0347-00-0000-XML_IS_Introduction.doc for more information.mRejectedobing vmn۳W۴W{WݓWW\WW"WWmns"Wmobile۫W"WޏW"W?Wmobile/network>Wmobility"W4W5WWmodelWݓWWmodified"WmodifyWLWMWmodifythesentenceappropriatelyVmodifywithinterfaceidentifierLVMVmoreZWWܛWjWWW)W?WmoveKWNW\WWmovethesectiontoappendixalsolookatcomment673NVmovethetextasistosection6.3.1KVmultiݓWmulti-hopݓWmultipleWWWmustWnWWnamegWnamesWWnaming\WWnas-portJWnas-port-typeWnecessaryWneedRWTWZW۴WWܛW{W{W{WrrequestparametersupdatescanresponseۆVneedmoreclarificationandappropriatesuggestedremedyVVneedtextforsuchacomprehensiveissuesee32VneedtoprovideclarifyingtextalongwithcommentܢVneededܗW WneedsWbtableWJWZWhW۰WW)WDWEWGWHWRWSWjWmW܁WWݘWݛWݿWWW\WlWހWނW>W\WaWfWhWkWqWrWWWWWWWW(W,W8WmWWWWWWWWWWWWtable22sparqlquerytlvvalueparametersformatހVtable23sparqlquerytlvvalueresponseparametersformatނVtable4-mihcommandsVtable6needtomentionthatlengthis4octetsdeletbit3)VtablexxextendedschemaurlparameterformatހVtable-6WWtable-7WWWWWWWW&W&W&W&W&W&W&W&WhemaurlparameterformatހVtable-6ܷWܼWtable-7ܹWtablesWtailPWtakeOWPWQWTWUWVWWWWWWWtakenHWhWtargetۇWW݊WW!W"W$W%Wtaylored۳WeDctoWWWWWWWWWW"W"W"W"W"W"W"W"W"W"W"W"W4btheaccesstoinformationshouldbefastV 8vdefinitionݓWݜWWWWWWWdefinitionofmnfixedbyanothercontributionindraftversVdefinitionsW>WWdefn1WdefnitionWdegradingۅWdelayWWdelete۪WW)W1W݃W-W4WWWWWWdeletebits3and4lengthisnotincludedaspartoftable-)Vdeleteheterogeneousinterfacesfromdefnofseamlesshandov1Vdeletethefirstsentenceonpage37line27insection6.1.Vdeletethelastsentenceofsecondbulletandaddmihuserf݃Vdeletethelines-VdeletethesecondandthirdsentencesinthedefinitionofnVdeletethesentencementionmihfisalogicalentityaspart۪V6 llbcAThe recipient of the primitive is the MIH Function, which will not try to interpret the query and do the retrieve. That's the job of the MIIS server.@A  33d665g2321vAQChange text as folows: " The recipient will forward the query in an MIH message to the designated MIIS server (or a proxy function of MIIS). The MIIS server tries to interpret the query request and retrieve the specified information. Once the information is retrieved the recipient responds with MIH_Get_Information.response primitive. "Q@A  '  )cn  )c  )c    N  wAccepted-Modified{k) done 2006/09/21 2006/04/24pEQiaobingFXieGMember^Technical (was Editorial)_110`7a8.1ba8.1bL@Af 33  $  )c  =btoW WWWW)W+W.W0W7W<W>W?WIWKWRWcWdWeWgWkWzW}WݍWݎWݑWݔWݕݗWݘݚWݵWݸWWWWWWWWWWWWW WWWWW W"W#W$W%W(W,W.W2W4W5W8W>WIWOWYW[W\WlW}W~WހWނWބWޅWއWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒWޒW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WWWWWWWWWWWWWWWWW?`‚"̃6B܇ԃ]uT]{ႃ‚#G^ro܌^=brpᅃጃ‚$vȃ]X‚%YL(1ilൃᭃ‚&Ilsƃ܀܂܄Ճ'ޓ̃!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!۪Lܔƒ*؃8N޶%V‚*ۑۭ۟!dݕݶ!-A‚1?۷#*<ܙTqڃރޒ޽,]‚2c}۸.V܈ܥ=wݳcޅޜޝڃۃ <=‚3RS܃ܝ>t‚4iqxۥ3ܺDJއ‚53CV:lwՃNݘݾ˃ޱԃ 0Qa‚6WYW[WaWlWtWuWvW}WWހWނWޅWއWދWތWޏWޖW5WWWXWlWmWnWqWrWsWtWvWwWxWyWzW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWW W%W'W(W)W,W-W1W4W7W8W:W<W>W@WWWXWkWlWsWuWzW|WWWWWWbinformation@informative@Ginitiated@9insertmihcapabilitypage54line14@nintelligent@intent@internal@intra-roaming@ip@Nipv6@isނއޖxissued@item@itself@l2@l3@Glayers@lefthand-side@bline@'lines@linklinkeventdiscoverrequest@link-layer@qessarytoputhereiftheproposedgener@qener@qnk@confirmresponse@qlinktypetypeofthelink@link@typemediatypeofthelink@nktypemediatypeofthelink@rged@ method@%mgmt@kmihfZmihcommandconfirmprimitiveshouldberemovedfromitscur@*mihhandoverinitiaterequest@Xmn@mobilenodeoruserequipment@moreandmergetextbetweenlines23-43into8.3.1@must@need@qneither@networkidentifeirshouldbelinktype@progressed@ v5ەWW5.3.1 W5.6.1CWW5.6.1.6jW5.6.1.6lsapjV5.6.1.7jW5.8nW5.8.3WkW500W508W514515W516W518lW518/525`W527BWCWDWEWFWGWHWJWNW527/626KWLWOWPWQWRWSWTWYWZW[W]W^W_W`WaWbWcWdWeWfWgWhW55 WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW7WWܗW7-255W7.4.15.1.2ܗW7.4.8gW704WWW709 W752/756FWXWW8RWWW8-8!W݂W8.4.2.13hW802.11ەWWWSW802.16 W4W5WSW802.21ۓWەWWܛW802.21enablesbothl2andl3transportoptionsV88ێW_Ã"`tܒܓݸփ׃གྷ3WXÃ"puܔÃ"(ahÃ"vwxijݹݺފૃYÃ"yz{|ދތ~Ã#0܂k]ލᓃÃ#@}~lmÃ#PJZÃ#`nÃ#p܀ގ4Ã#܁pݽހށÃ#ݾݿނރÃ#؃\Ã$)a[\Ã$ ]^_ᕃᖃÃ$0܃`abcÃ$P܄Ã$`܅bcdeÃ$p܆*defÃ$܇qޏighÃ$rOބޅ}ኃÃ$ۏÃ%-ǃކࠃiÃ% كڃސޑޒÃ%0܈܉Ã%P܊܋Ã%`܌sޓÃ%pޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓݥЃ ghltk bE | Network -> Network | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ...... | .............. | .............. | ................. | ............................. ---------------------------------F------------------------------------------------------------------------------------------------------------------------------------------------------------  E@A>  33    33>c ................. | ............................. -------------------------------------------------------------------------------------------------------------------------------------------------------------wcalgorithmGWIW\W]W^W_W`WaWbWcWdWeWlWmWWWalgorithms W WWalignedWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWambiguitysuccinctnessallowthecasethatmihisnotsupporVamendۆWamendedܸWamendmentۅWamendsۊWamendsmihcapabilitydiscoverymessagebyaddingnetworkidۊVammendmentsWRbcommaW4W5WMWcommandpWېWW8WmWzW{WKWWW(W>WWތWWWWW7WWWWWWWWWWW#WcommandcodeVcommandcodezW{WތWcommandsېW8WݎWWWWދWތW|WWWWcommandsmaybeinvokedfromupperlayersmihcommandsasweVcommentۓWۯW`WWސWޑWޓWWWcommentsDWEWcommit\WaWWWWWWWW/W0W5W5W W W W W W W W W W W W W W W W W W W W W WesW_WcommunicatingW7WcommunicationuWxWۖW܅WW3W݂W WcommunicationsiWcomplete/W0W5WWWRWcW܉WWޭWޮW޳WWWcompletedWWRWWcompletelyYWܓWcompletionW  !"#$&'()*+,-./013456789<=>?@AEGHIKLMNOPQRT^abcdefgijklmnpqrstwz{}݆݈݃݅݇݉݋݌ݍݎݐݑݒݓݔݕݖݗݘݚݛݜݭݲݵݸݹݺݽݾݿʃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃kdx_‚jݚjृઃ 0:‚q؃^‚rكv1‚szB=ୃȃ2n{xxxxxxPۅ‚Q‚R‚HST‚U‚V‚Wcde‚fۊۍې‚I‚ی‚‚ۃ‚h‚gۄۆ‚‚1ۂۋ‚2‚3Ã! 4Ã!@<Ã!`Ã!pijkÃ!lmnÃ!oÃ"pqÃ" rstuÃ"0vwێÃ"@xÃ"Py۔Ã"`+Ã"5=Ã"Ã"zÃ#0Ã#@Ã#PJÃ#pÃ#{|Ã#}~Ã#ۈÃ$`67ۇÃ$p89Ã$>Ã$Ã$ۏÃ%-Ã%`Ã%ۀÃ%Ã&ہÃ&ۉ`2 ]ۀہی۔۬ۃ-0J0#ۏ۞@"&'SPD`۠pۢƒӃ)p۩%JW K‚!2ۄ܃ X"bheader$WܑWݸWWW'WWW3WXWheadertypesmustbefullyspecified3Vheading2WhedaerWWhelptW@WݍWݸWYWWWhelpfulWhelpsAWAWWWWWWWRWܬWhereWWfW;Wheteroge_Wheterogeneous"W?W_WۙWWܤWܴWWޠW޽WWWW,W@W]W~WߛW߼WWWWhetrogenousWhexbinary~Whide݃Whidel2sublayerstheyareshownindetailsineachspecific݃Vhigh#W?WܬWޡW޽WWWW,WAW]WWߛW߽WWWWhigher#WAWOWPWQWRWTWUWWWܤWWޡW޿WWWWWWWWWW.WAW_WmWnWoWpWrWsWWߝW߫W߬W߭W߮W߰W߱W߽WWWWWWWWWWcyouWd 0ە@Pۖ`pۗۘ‚!‚"‚#‚$ۙ‚%‚&ۚ‚',‚(‚)ۛ‚*!*!*!!!!*!!-‚Q޿.‚R/‚S0‚Tƒ1‚UÃ2‚Vă3‚WŃ4‚Xƃ5‚Yǃ6‚Zȃ7‚a‚b‚c‚d‚e‚f‚g‚h‚i‚j‚q‚r‚scdifferences*W$WdifferentۉWۋWېW:WHWRWrWܤWW+WݍWݐWWWW*WtWvWWWWWWWWWWW WW!W#W?WVWsWWWWdifferenttechnologieshavedifferentnmsinterfaceseg802#VdifferenttlvsshouldbeusedforsourceidentifieranddestVVdifferentiateW W W WVdiscoveringېWdiscoveryuWWۊWWdiscussܯWdiscussedDWpWvW+WdiscussionAWWW܏WWdiscussionofhow802.3networkscangetdirectinternetaccVdiscussionoflogicalnetworkreferencemodelusesroamingcVdispatchmWdispatched7WdistinctWdistinguishۊW:WܜW:WdistinguishedWdistributedWdo_WbWeWfWlWۈW۬WWCWܐWWWWWWWNon-binding_56`18g2967 2006/04/29 2006/04/28cenough+WW"W$WWWWWWWensureWensuringWentailWentersWentier'Wentire۽W'WentirelyWentities۴W7WZWfWrW3W{W݈WWWW|WWWkWWWentitiesmakes݈VentityۭW۴W WZWܡWWW{WW"W%WޖW1W2WfWgWhWiWWWWWWWWWWWWWWW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2Wentry܉WWWEWFWGWHWRWentry2linkeventderegisterhasbeendefinedasaneventeHVentry2linkeventregisterhasbeendefinedasaneventeveGVentry2miheventregisterhasbeendefinedasaneventevenEVfb20܇W)W=W2000W21ۓWPW܁WvW21-06-0460-02-0000-bvW21-06-0522-04-sessioݒW\W21-06-0598-00W21-06-0608-linkݜW21-06-0609-isݓW21-06-0611-00-0000-m{WW21-06-0612-03-0000-r݃W21-06-0614-00W21-06-0620-00-0000-nvW21-06-0622-00-0000LWMWW21-06-0624-00-00W21-06-0624-00-0000-nwW21-06-0625-00-0000W21-06-0625-00-0000-nxW21-06-0627-00-0000WW21-06-0627-00-0000-nyW21-06-0628-00-0000-aۃW21-06-0629-00-0000-aۄW21-06-0630-00-0000-pW21-06-0631-00-0000-pۅW21-06-0632-00-0000-lۉW21-06-0634-00-0000-mW21-06-0636-00-0000-rW21-06-0637-00-0000-mW21-06-0644-02-0000-mkW21-06-0645-00-0000}W21-06-0656-00-0000-wW21-06-06xx-01-0000-a=W21-06-0xxx-00-0000-c7W7WWdeliversWdemonٿWdependantWdependencemediaWdependent0Wdepending-Wdeployment٤WقWlctheunitoftimeintervalisnotdefined]Vtheusageofaaninfrontoftheacronymmihisinconsisten2VtheusecasesandhandoverscenariosforthecommandsdefineVtheuseofforexampleisinappropriateintherepresentatioVtheuseofnas-port-typeshouldnotbejustanexampleݔVtheuseofthetermmihproxyshouldbeavoided,Vtheuseofunreliabletransportmayinfactleadtosignific VthevalidrangefordestinationidentifierisgiventobemiVthevalidrangeofoldlinkactionsisnotconsistentwiththVthevalueforversionisnotdefined;VhVthevalueforversionisnotdefined݁V݁VtentwiththVthevalueforversionisnotdefined݁V݁VhVthevalueforversionisnotdefined݁V݁V݁VtentwiththVthevalueforversionisnotdefined݁V݁V ) Name Type Valid RanWcnotۅ<݌>>notclearwhatgranularitymihswitchoccursonwheninvoked@3notclearwhythescopeofdefinitioncolumnisneededasal@notcustomaryuse@mnotification@obtain@Jof@QY>offered@6offers@on@one@only@operation@operators@Eor@order@otherwise@@propriateintherepresentationcolumn@column@ution@Qspecifies@standardize@statement@such@,supported@Ysyntaxerrorinnetworksecurityandqualityofsecuritycap@Dsyntaxerrorinthisisusedtorespondtheresult@4systemmanagementhasbeenintroducedasaserviceherehowe@.take@?textneedsimprovement@that@that's@the$\the1sttwosentencesintheparagraphrepeatswhathasalre@theassignmentofistoanyinformationelementshouldnotb@<bifDWTWUWۓWWHWTWUWVWWWZWܾWWݗWW,WWW[WWWWWWWWWWWWWWWWWWWWWWif0-or-1transactionsemanticsarerequireduseanunderlyiVifcertainclassesoftlvsarenotsupportedViffinergranularityofinformationisusefulathigherlayeViftheprimitiveistobeusedonlybythemihfunctionreplZViftypeielistofnetworktypeisapprovedreplacetypeieVVVVVVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVWWWWWW#W%W&W,W2W3W5W7W:W=W>W?WAWBWDWEWGWHWNWPWSWTWUWVWWWXWYWinanetworkmodel,VtypeofjVmVinformaAW-bexamplesGWIWWlWmWWWexapndedIWexceedsWexcept$WexchangevWxWWpW|WuWexchanged WWexchanges4W5WWWexchangingpWexcludingwWWexclusiveܟWexecuteۉWexecuteactionthreshoۉWexecuting>WexhaustiveWexist WexistingWexists,Wexpand@Wexpandgniintheacronymlist@VexpansionexpeciallyWexpectVWVWVW@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@V@VnationWexplanatoryܴWWWexplicitWexplicitlyW W,Wexplicitlyreserve128generaland127otherforfutureVexposed0WexpressWexpressions\WextendedAWiWkWnW{W}WݾWݿWextensibilityAWܸWWWextensible WWextensionsWextent_WWWucstatement*W WWWstatesWWWstaticOWWW?WstationiWstation'siWstatusVW܀W܄W܇WܖWݽWWW*WWWWWWWstepWstepsWstillܕW|WWWstore܂Wstraightforwad݃WstreamlinestrengthWstrong۳WstructureܬWWYWWpWWstructuredwWxWyWzW{W~WWWWWWWstructuresWsttausWWsub-optimal۶Wsub-sectionsjWkWsubclassofvWsubclassofisnotdefinedinthefigurevVsubdivision/WsubjectWWWWWaloneisinsufficienttosupportscenario\VsuboptimalWsubscribed7WsubsectionsW1WsubsetWsubstantiallyPWsubsystems/WsubtleWsucceedseWsuccessۄWsuccessful܄W*WsuccessfullyWsuccinctnessWWannex٠W١W٢W٣W7ucprevious+WۯWWWkWpreviouslyWprimitiveLWcWdWfWgWiWlWۄWۅWېWW5WNWQWkWܟWaWWWW"W$W%W>WއW]W^W_W`WfWgWhWiWnWWWWWWWWWWoW|WWWWWW"W"W"WWWW!W"W$W%W>WJWއWޔWޗWޗWWޗWޗW&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&WWWWWWdboptional'WWWWWWoptional1changenotrequiredVoptionallyWV4V4V4V4V4V4V W!#W,W-W.W?WDWVW\W_WbWhWiWkWlWnWuWxW{W}WWۂWۈWۙW۵W۶WWWWWWWWWWWWWWWWWWWW#W%W&W*W3WTWUWVWWWXWcWeWnWqW܁WܡWܤWܩWܫWܽWܾWWWWWWWW W W3W9W;WIWPWUWYW[W_WwW~WW݊WWWWWWWW WWW W"W$W%W-W8W;WIWTWmWnW}WށWރWކWއWޖWޗWޚWޜWޝWޞWޟޡWުWޫWެW޽WWWWWWWWWWWWW W W W WubaW&W)W+W-WzWݍWݎWݔWݕWݛWWWWWW W%W'W,W2WCWIW[W}WWހWނWޅWއWދWތWޒWޖW5WXW[WlWoWrWsWtWvWxWzW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'W*W2W6W7W>W@WjWuWzW|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWW߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽WO^Technical, Binding_31`47a5.7.1bAAdd the following paragrpah instead: "Thereafter these packets may be encapsulated in a L2 MIH Protocol using MIH ethertype when the payload needs to be sent over normal data frames as in case of ethernet. In other cases the TLV based messages and payload may be directly encapsulated in media specific management frames. Alternatively, MIH protocol may be encapsulated using a higher layer transportI " @Af 33Y  [ 33D  33fcAG"Thereafter these packets may be encapsulated in a L2 MIH Protocol using MIH ethertype when the payload needs to be sent over normal data frames as in case of ethernet. In other cases the TLV based messages and payload may be directly encapsulated in media specific management frames." No mention about L3 and above transport Gd237g2437i Vivek Guptak some texts or delete the figure. coverloadiWWowlwWownۋW۳WYWW!WWp10Wp105Wp111 Wp122Wp137Wp145EWp152-l15Wp158-l16Wp158-l39Wp18Wp22Wp46-l9Wp51-l26Wp59WWp72Wp77Wp79Wp802.21Wp802.21/d01.00ېWp90kWpacket۽WW&W'WWWkWpacketsW W*WWpadding/alignmentW9WیWparticularuWwWpartner_WaWpartners_WaWpartocularZW]WpartsەWpassSWpassingSWperformuWۂWېWperhapsېWperiod۳Wperiodic۳Wphrasing۱Wpicture۽WplaceqWsW۟WplacedYWplaying:W;W<W=W>Wpoa_WaWۇWۈWۊWpoas_WaWpointۊWpoints۬WpoorlyZWpossibilitywWpossibleۈWpossiblyKWpotential\Wpre-defined_WbWpre-establishment\WpreparationۅWcheader$WuWܑWܓWܔWܚWWݸWWW'WWW3WUWXWheadertlvsaredefinedbutnovaluesareassignedtothemܚVheading2WWhedaerWhelptW@W݃WݍWݸWYWW<W?WWWhelpfulWhelpsIWW?WhenceܰW\W]W^W_W`WaWbWcWdWeWWWWWWQWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWoposalforaddingaparameterinthemihhaۂVheterogeneous"W1WIWܤWݐWWޠWWWW} cinorderformobilenode'smihfunctionentitytocommencem{Vinsection8.5.4.1thedescriptionisnotcorrectބVinsection8.5.4.2thedescriptionisnotcorrectޅVinsomeplacesieee802.21hassomehowbeenclubbedtogether݅VinthecurrentdefinitionofmessagemihhandoverpreparereVinthecurrentdraftthedescriptionabouttheprimitivemihVinthecurrentdraftthemihcapabilitydiscoverrequestmesVinthedefinitionofmobilenodethesentencethemobilenod3Vinthemihsam7.2.2table14andtable15seemstobemissiݛVinthesentenceconceptualtransfertheoccursbetweenthei Vinthisstandardinordertoaccess3gppservicesprovidestVin-depthWin-scopeWinaccurateܰWdestVin-depth܏Win-scopeWinaccurateܰWܰWdestVin-depth܏W܏Wrdertoaccess3gppservicesprovidestVin-depth܏W܏W7KcwhetherWWOWWWW WWWWW W*WWWwhethertoincludethemihfid/sidisnotapparentlydefinedVwhichLWOWPWQWRWSWTWUWVWWWlWlWWW_WaWlWuWWWWWWWWmacُW٨W(W:W=W?WjWuWmacaddressisnotsuitableforallmediaalsohowaretechn:V=Vmacaddressquestionagainistheuseofmacaddressessuita?Vmac/phyڍWmadeWmainWmainlypWmaintainedIWmaintainsfWmakeWWGWcWهWdWiWjWWmakeindefinitearticleformconsistentcVmakesWڄWWmakingWmanageXWmanaged-WZWmanagementW;WWWmanages-WmandatoryWiWWmany:WWWWWmaterialWmaximumLWWWYWmaximumlengthofthesessionidandothersyntaxaspectsarYV cd304g2259i Vivek GuptajHow is Network Selection handled handovers? Is network selection (across heterogeneous links) also part of upper layer Mobility Mgmt protocol like SIP/MIP etc.? If NOT, then some mechanism (albeit better explained) may be needed.kAWould suggest to identify some common mechanism to aid in communicating network selection decisions across different networks. Such a mechanism should be able to communicate network selection (link identifier + PoA) choices from client to network and vice versa. The entity (client or network) communicating the decision...may not always carry out the handover. Any specific details (primitives, parameters etc.) pertaining to this may need to be included in draft. This may be difficult to ado"MIH Handover Commit", and "MIH Handover Complete" from Table 4w@A  33c----------------------------------------------------------------------------------------------------------------------Du(ctlvsܕWܚWWWVW"W#W'W*W+W-W.W/W0W1W2W3W4W5W6W7W8W9W?W@WBWDWEWFWGWHWIWJWSWXWYWZW\W]W_WaWbWiWjWkWlWmWnWoWqWsWtWuWwWzW{W|W}W~WہWۂWۃWۄWۅWۆWۇWۈWۉWۊWۋWۏWېWۑWےWەW۩W۪WۭW۳W۴W۶W۸W۾WWWWWWWWWWWWWWWWWWWWWWWWW'W-W0W1W7W9W:W;W=W@WCWDWEWHWIWNWOWPWQWRWTWUWVWWWXWYWZW^WcWeWiWjWkWlWmWnWsWtWwW{W|W܂W܄W܆W܋W܏WܐWܕWܖWܗWܘWܚWܝWܡWܢWܤWܥWܧWܴWܶW.bunderRWZW۳WܾWsWWunderlying WW WWWunderstandWunderstandingWunique[WݔWފWWWuniqueeventidentiferWuniquelyWuniquenessWunitHWunited'WunitsYWunknown}WxWzWWunlabeledhWunlessۖWWunlessotherwisenotedmediareferstomethod/modeofaccessۖVunnecessaryWunnecessary/misplace WunregisterWWunrestrictedHWunsuccessfulVWWuntilWWtWWuntiladditionaltextisprovideditshouldbedeletedVupOWRWܰW/WݍWWWWupdateۋWSW܍WWWWWaW{WWWWupdateaccordingtosubmitteddocument21-06-0637-00-0000-mVupdateaccordingtosubmitteddocument21-06-500-02-0000-neۋVupdatediagram/textaccordinglyVupdatefig29anoverallflowcontroldiagramisrequiredshVViepoalo܍VWR  #$'),-./012345678:;WAW]Wnbintelligent#W?WW?W?W?W?WWWWWWWWWWWWWWWWinter?WܤWW޽WWinter-media*WިWWWinteractpW"W$WinteractionW݃WinterestIWinterestingeWinterface*WiW۾WWeWWW0WDWWW1W2W3W4W5W7W8WޖWިWWWinterfaces"W*W.W,W!W1W2WޠWިWެWWWWWWWintermediateUWWinternalWWinternallyWinternetAW޿WWinteroperabilityWinterpretlWinterpretationWinterval\W]WޖWintitate|WintoWW!W*WZW_W`WbWqWWW=WWWWyWzWSWޜWޝWޟWިWWWWW W WWWintonetworkaddressinformationjustanaddressVintraW'bregister@_related@remove@ܛ?removeaccessto@2removefigure19@removemihusersareinthebeginning@removeoreventhroughtheinformaitonservice@Rremovesecondinstanceofdefinitonofmn@itonservice@Rservice@Rce@Rice@Re@Rderidentifiers@Ridentifiers@Rtions8.5.3.19and8.5.3.20@ons8.5.3.19and8.5.3.20@sections8.5.3.19and8.5.3.20@Dremovesuggestedmacnewpoaid@"removetheabovetextuntilqoscontributionisacceptedby@ removethesentencethisincludesthelistofnetworkoperat@removing@|renamethenon-posmihentitytomihnon-posforconsistency@ rephrase@replace@replaceadditionalidentifiersarepresentthathelptoanal@replacelinkbynetworksincethisisnetworkselection@replacelinkcommandoriginatewithlinkcommandsoriginate@replacelinkgoingdownwithlinkgoingdown@]cforeign"W%W%W%W%W%W%W%W%W%W%WlisedWformatGWHWqWvWܑWWWWW~WWWWformats%WformattedWWformerWformulation۸Wforward Wforwarding:W WfounduWWWfragmentWfragmentationWWfragmentingWframeqWWWWWWframesWframeworkjWkWmWnWoWzW{W|W}W~WہW0WnW3WframeworksWfree-stylejWkWmWnWoWzW{W|W}W~WہWfrenchjWkWmWnWoWzW{W|W}W~WہWfroWfromWAW_WbWcWdWiWۉWۋWېW۵WWWWWWW7W9WOWSWgWܘWܝWܤWܩWܫWܶWܺWWWWWW W&W0W:W[WxWݐWWWWWWW"WcWHMە{k) done 2006/09/21MarkedۖESanjeevFAthalyeGMember^ Editorial_1`48a1.2bUnless otherwise noted,"media" refers to method/mode of accessing a telecommunication system (e.g. cable, radio, satellite, etc.), as opposed to sensory aspects of communication (e.g. audio, video, ...)c!Explain usage of the word "media"d4psame at previous comment{k) done 2006/08/29ۗESanjeevFAthalyeGMember^ Editorial_1`52a1.2b7Suggest using "Additionally" instead of "Alternatively"cSemantics correctiond7{k) done 2006/08/29ۘESanjeevFAthalyeGMember^ Editorial_1`62a1.2bh "... cooperative use of information available at the mobile terminal and at network infrastructure ..."cSuggest rephrasingd9{k) done 2006/08/29ۙESanjeevFAthalyeGMember^ Editorial_2`34a1.2b,Remove either "different" or "heterogeneous"cRemove redundancyd13{k) done 2006/08/29ۚESanjeevFAthalyeGMember^ Editorial_2 cthisisalinklayerindicationwhichshouldonlybereceiveOVPVQVRVTVUVVVWVthisisalinklayerprimitivewhichshouldonlybegenerateLVnVthisiscriticallyimportanttodescribeinfulldetailthe[VthisisnotanexhaustivelistwhataboutgalileoandglonasVthisisredundantthemihconfigureprimitivesee7.4.7hasgVthisistrueonlyforlocaleventsandnotforremoteeventsܫVthismechanismretrievingnetworkinfousingspecificiesisuVVVVthisisnotanexhaustivelistwhataboutgalileoandglonasVthisisredundantthemihconfigureprimitivesee7.4.7hasgVthisistrueonlyforlocaleventsandnotforremoteeventsܫVthismechanismretrievingnetworkinfousingspecificiesisaVthisneedtobere-writtenasaproperreferenceVthisprimitiveisdeliveredfrommihfunctiononoldpoato"VthisprimitiveisissuedbyupperstocontrollayerlinksV9, :cBNetwork (AN) An IP network which includes one or more Access Network Routers. Access Network Router (ANR) An IP router in the Access Network. An Access Network Router may include Access Network specific functionalities, for example, related to mobility and/or QoS. This is to distinguish between ordinary routers and routers that have Access Network-related special functionality. Access Router (AR) An Access Network Router residing on the eCdge of an Access Network and connected to one or more Access Points. The Access Points may be of different technology. An Access Router offers IP connectivity to Mobile Nodes, acting as a default router to the Mobile Nodes it is currently serving. The Access Router may include intelligence beyond a simple forwarding service offered by ordinary IP routers. " To summarize, an Access Network is composed of one of more Access Routers connected to one or %{bmergedWWmessagelWvWwWWoWyWzW{W܄W܅WW W"W#W$WWބWޅWދWތW|WWWWW W/W}WWmessaged-idۉWmessages WpWxWWݎW"W|WWWuWWWmessagetooWmethodWmethodlengthshouldbe2octetsV(VoWoWoWoWoWoWoWoWoWoWoWVWWWdWfWiWlWpWsWuWvWwWxWWۂWۄWۆWۈWۉWۊWۋWېWۭW۾WWWWWWW#W,W2W7WOWUWVWWWXWZW\WcWmihhandoverinitiaterequestۂVmihreferencemodelforaccessnetworkstechnologies$Vmih-enabled!WmihfpWuWxWWۇW۵WWmiisAW_WlWuW۳WWmilliseconds\W]WminimizeVWminimized۸WminimumWW\WminuteHWWbW HbD 2: hours 3: day 4: month 5: year Value 4 E The cost value in Currency/Unit Service-Info 1 Informs if service information is available 0: Restricted 1: Unrestricted XMal  [Hb cThe format of the Cost Information Element must be defined by the IEEE 802.21 group in order to satisfy interoperability between different MIH implementations. d419g2259vpRemove reference to the web page http:www.jhall.demon.co.uk/currency/by_country.html from the specification...wAccepted-Modified{k) done 2006/09/21IENada, Golmie, Member^ Editorial_54`50bRemove the first sentence.cA The first two sentences mean the same things: "MIIS helps to obtain a global view of the network neighborhood information consisting of multiple media types. MIIS provides a uniform way to retrieve heterogeneous neighbor network information in any geographical area." d441g2260psuperceded by 345{l) none needed 2006/09/21NENada, Golmie, Member^Technical (was Editorial)_64`31b4`31b64`31b 1: minute D]!vxEvent and Command IDs have been defined in section 8.3.3.4 in draft version D01.09. Check spelling of Command in 8.3.3.4w Superceded{a) awaiting resolution 2006/09/21 2006/04/242EDasFSubir^Technical, Binding_37`63a6.1.6b)Delete this type or add a new definition cFWhat is an "Administrative" link event type? It has not been defined. d281g2442vReplace "Administrative" category by "State Change" category for different events.\\ Do this for all occurences in the draft. wAccepted{a) awaiting resolution 2006/09/212EHongFChengGMember^Technical, Binding_38`3a6.1.6bChange the text for this item accordingly to reflect that the indication of transmission is about the higher layer PDU instead of link layer SDU.cyer SDU.cyer SDU.cmeant to serve as the Event IDs. If not, clearly define Link Event IDs and MIH Event IDs. 36a6.1.5.2b6.1.5.2bg_37`29a6.1.5.2bnical, Binding_37`29a6.1.5.2bboutside W#WsWvWwW۶WoverOWPWTWWPWW|WWWW}Wover-the-airWoverallWoverheadWWowl^WwWowlonpropertyrdfresourcelongtitude-resolutiowVp0028-100&Wp0028-200&Wp69/l65Wp70/l13Wp71/l3Wp72/l21Wp72/l62Wp90kWpacketrWsWW&W'WWpWWpacketsUWVWW WpageۮWWhWܬW(W,W/WfW.W1W2W5W6WWWW0W=WWWWWpage14line26setupinsteadofsetup/VpagesWpagingW7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7Wetup/VpagesWޘWWW8WvWߴWWpagingWpairFWGWWWWW3W4WdWeWߢWߣWWWWWMW)`‚sAۘǃHvxzৃ3‚t}‚u*۽gܨf݇ݵ%}BJKc‚ve8KMݚ?ඃ˃$Y\᥃ᰃ΃‚x)6Ã"4Ã#Ã# /Ã$0Ã%ÃۿÄ"#Ä'XÄ*2(((V3urlresponseoneextendedschemaurlparameterV3.2)W30٫W31W32WWWWWW33W33aW35-40قW37-43W3753ٱW38aWٴW38-49ٴW39ٴW3gpppWqWWڒWڽWW3gppsystemsalreadybroadcastV3gpp/3gpp2ُW3gpp2pWqW{WڒWڽW4W&WHWyWٴWٻWټWٿWWWWWWWWW WWWWWW4sipV4zerooroneextendedschemaurlparametersVcomments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new co`KwGMember^Technical, Binding_44`50a6.3.2bCurrent text should move to the Description column, and a specification for how this information is represented should be added.csThe text in the representation cell is a description, not a specification as to how the information is represented.d352g2242vRepresent as IntegerwAccepted-Modified{k) done 2006/09/21 2006/04/286EEleanorFHepworthGMember^Technical, Binding_45`10a6.3.2b]Current text in representation should be moved to the description, and a specification added.c2The representation of NUMBER_POA is not specified.d366g2244v]This will be handled separately for al such IEs and appropriate resolution would be proposed.wAccepted-Modified{l) none needed 2006/09/21 2006/04/286EEleanorFHepworthGMember^Technical, Binding_45`53a6.3.253a6.3.253a6.3.2n is represented should be added. layer services provided by the MIIS may constantly evolve. At xy ^bindingܚWܚWܚWܚWܕWists of a two parts; one with fixed length and another with variable length. The fixed length part of the header carries the essential information which is present in every packet and is important for parsing and analyzing the packet quickly. The variable length part of the header carries information which is optional in some cases. Make the entire paragraph consistent with the title and the MIH payload format (= frames)ijkmnpvw{ 2006/05/146/04/2851: 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 [V8_bassociatedmWWWWassociatingWassociationWassume Wassuming|Wassumingtwomihfunctionshavealreadydiscoveredeachnote|VasynchronouspWatAWsWۘW۶W4W7WQW܌W܍W܎WܚWW"W(WOWgWkW&W>WޖW5WWWWWWWWWW"W5WsWWWWWWattach#WattachingWattachment?WWWWattachmentsAWWattainableWattempts&WattributeݔWݕWݘWWW(W,WattributeisencodedinthisfieldtheݘVattributevaluewhichisauniqueidentifierݔVVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVݘVWQWpWWTWUWVWWWXWcWܳWܽW0WbasicAWbasicallyWeW6) /pbC02.21 supports Media Independent Handover Function in mobile node, and network. The MIHF Protocol allows peer MIH Function entities to interact with each other. @Az 33  TTH  TTI  )c   33zcAaThe first paragraph repeats what has already been sufficiently discussed earlier. No need for it.a@A  33d679g2325wAccepted{a) awaiting resolution 2006/09/21 2006/04/24dendent lower layer resources. To support remote ES, CS, and IS, MIH Functions on different nodes need to communicate with one another. The Media Independent Handover protocol defines frame formats for exchanging messages between peer MIH Function entities. These messages are based on the primitives which are part of Media Independent Event service, Media Independent Command service and Media Independent Information service. IEEE8x ^bindingܕWܕWܕWܕWܕWists of a two parts; one with fixed length and another with variable length. The fixed length part of the header carries the essential information which is present in every packet and is important for parsing and analyzing the packet quickly. The variable length part of the header carries information which is optional in some cases. Make the entire paragraph consistent with the title and the MIH payload format (= frames)ijkmnpvw{ 2006/05/146/04/2851: 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 }WBbincluded~WtWWincludeingSWincludes?WAWWincludingWW|WWinclusionWWinconsistencyYWZWincreasedWincrementalWW.W.WWWWWWWWWWWWWWWWWWWWWW[Windependencemih(WަWWindependent?WAWpWuWvWWWWW}W޽W޿WWWindexing۶WindicateWRWwWWݗWWOWindicatesFWTWUWVWWWXWYWcW|WݗWindicationUWVWWWW9WOWRWUW\WyWݍW>WsWxWޕWWWWindicationsTWUWVWWWXWWindividualۂWܽWSWindividually۳WinfluenceWinfoWOWܗWܘWܙWzWWBWxWinfomrationW%WinfoqueryparameterskWnWܕW}Winfoqueryresponse|WވW3bShould define the values for these IDs in the Annex A-4 for example with the other available values or directly where mentionedcTThere are no ID values defined for MIH Function ID, Session ID, and Transaction IDd719g2265iWolfgang Grtingj:agreed for MIHF & Session IDs disagreed for Transaction IDkMno need to define an ID for Transaction ID as it is in the fixed header part.pO- made text changes per 06-0690 - took out any mentioning of global uniqueness.verefer to contribution 21-06-0690-00-0000-ID-definition... None of the identifiers are globally uniquewAccepted-Modified{k) done 2006/09/21E Ulises OlveraGMember^Technical, Binding_87`36a 7.4.5.1.4bmA MIH Get Status command is issued by the local MIH Function to get information on the status of the links. clinks. cand Transaction IDd719g2265iWolfgang Grtingj:agreed for MIHF & Session IDs disagreed for Transaction ID% ctriesYWWWtriggerۅWW"W$WWtriggeredWtrip Wtrips WtrueWܫW|WWWtrylWWtWtryinglWYWWtwoWWqWvWۦW.W1WIWWWWWWW&W'W>W=WtW|WWWWWWWW WWWWWWWtwodefinitionsofthesametermmobilenode.VtwomihcommandshassimilarfunctionsmihswitchandmihhaVVVVVVYW|WܗWܼWܾWWWWWWWWWWW W W~W݃WݠWݺWWWWtypeiepoacapabilitiesthesecurityandqoscapabilitiesoܾVtypes=W@WIWJWYWܤWWWWWWWhWݐWWtypicallyܤWܱWݐWWtypicallyinaheterogeneousnetworkݐVtypicallyinaheterogeneousnetworkcomposedofmultiplemeܤV6$^Technical (was Editorial)_22`57a5.5bAHChange the text to: MIH Reference Model for Access NetworksTechnologiesH@AR  33  4  <  33RcANA better title for 5.5 would be: "MIH Reference Model for Access Technologies"N@A  33d177g2244wAccepted{a) awaiting resolution 2006/09/21 2006/04/24dcthecontentinsection7.2.2.1section7.2.2.2anditrespeclVthecurremtspecsaysvariousclassesofinter-operabilityaWVthecurrent802.21draftdoesnotincludeanadequateframewVthecurrentinformationelementsinsection6.3.4.1needimpsVthecurrentinformationelementsintable6arepoorlydefinZVthecurrentmihreferencemodelfor3gpptriestoshowhowmVurrentinformationelementsintable6arepoorlydefinZVZVthecurrenttextimpliesthatthediscoveryofmihfunctionVthedecriptionisthesameastherequest܄VthedefinitionofeventidsaremissingitiscriticallyimpNVthedefinitionoftheparameterforsupportedisqueryismissdVthedefinitionsgivenforthemihhandoverxxxprimitivesin܏VthedefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofthemesageisthesameastherequest܅V coNvwhereverއW>WWwhetherWwhichQWRWSWTWgWۅWۛWW"W\WWWW?WnWWWWWwhyZWWWwhyshouldinformationbeorganizedintreestructureonlyZVwilllWەWWݓWwiredۛWwirelessۛWWwishWxcanother@-anywhere@`architectural@are=area@as@}aspects@associated@aware@@be[:t2Tbeconsistentwiththemdeiadependentandmediaindependent@Sbecause@been@gbefore@below@beyond@both@bs@butby@fo@butܖby@88roadcasting@but|by@3byr1r2orr3overanyaccessnetworkandtwomihnetworke@networke@renormativeandwhic@comma@comments@compressed@confusion@consistency@contents@context@coverage@critical@=d01@define@Ndefines@-definitions@Ldefinitionsofhorizontalhandoverandverticalhandoverare@delivered@dependency@Edescriptionofrdfdataunderinforquerytypeisnotcorrcet@}descriptions@e<pwhether WwhichۓWܾW2WwillWwiredWwithۓW۴WWAW{W݃WݜWWlWvW2Wword WW>WwordingݜWwouldܾWݜWyoshiݒWyoshiprovidedthemissingfilein2006/07foldernowݒVyouۓW{Wv0VWގWW0aborthandoverގV0x20000000W0x2fffffffW0x30000000W0x31000000W0x31ffffffW0x32000000W0x32ffffffW0x3fffffffW1ەWݒW,WVWށWރWގW\WWWW1accepthandoverގV1intra-technologyhandoverhnadoversacrossesssincaseofەV1tlvspecificparametersށV1tlvspecificresponseparametersރV1-4W10W102W104W108W11W11eW12W128WWW137W!W14 WW142WWW162WW178uWwWxWyWWyWa5.5ba5.5blid local or remote identifier"-------------01kprimitives"W\WWWvWWprimitives/mechanismWprobablyWprobeWprocessWprogramming~WproperWproperlyWproposalWWproposedWprotocolWUWVWprotocol/mechansim\WprotocolsW WprovideWWqosWWqueriesuWWquery|WuWvWwWxWyWzW{W~WWWWWWWWWWWWWWWoWoW_ScanScheduling is relative to scan information.d488g2265 2006/05/14OENada, Golmie, Member^ Editorial_62`10bA=Replace "MIH_Get_Info.indication" with "MIH_Get_Info.request"=@Af  33  33   335  33<  33f  33U  33`  33  33  33f \ vtext WW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"WBWRWTWۂWەW۳WWW WܗWWWWWWݓW7WSWfWnWthatisusefulinformationVthe"W)W*W0WQWRWSWTWUWZW[WۉWۋWێW۪W۳W۵W۷WWWWWWWW W%WHW`WܗWܬWܽWܾWWWWWWW0W2W3W;WBWDW{W݃W݄WݓWݳWWW-W/W4W5W7WSWdWthedefinitionofschemaisnormativeanditisalreadyinaVtheentirelengthcolumnintable-6isbeingdroppedasper%Vthegroupfeelstheoriginaltextisbetterthanthesuggest7VtheieshouldrepresenttheqoscapabilitiesoftheaccessnVthelanguageistoostronginsomecasesmayneedtochange{V]hvbeۛW۳W۴WWWܬWW WWW1WzW{WݓWW\WfWWWWWWWWWW W WW W"W#W%W'W4W=WmWWWWWWWWWWWbeenRW|WWWWW2WtW{WWWbeforeSW"W W?Wbehave\WbehaviorWbeingZWWWW Wbeinghandledaspartofcomments384396incommentassignmV abcSyntax error in "Specific t IE"d570g2286{k) done 2006/09/21fENada, Golmie, Member^ Editorial_88`47bAwReplace "After upper layer entities makes handover decision" with "After an upper layer entity makes handover decision"w@Af  33   33$  33C  33_  33fcESyntax error in "After upper layer entities makes handover decision" d608g2291{k) done 2006/09/21gENada, Golmie, Member^ Editorial_88`64bIInsert "NewLinkIdentifier" between "HandoverMode" and "OldLinkIdentifier"c>The new link identifier is missing from the list of parametersd614g2292{l) none needed 2006/09/212006/08/292006/08/29 hENada, Golmie, Member^Technical, Non-binding_89`26bDefine the list of Actions that can be taken and provide encoding for the values consistent with section 8.4.2.13 on page 125. Add text as per section 8.4.2.13 on page 125#bretrievedlWWtWvWWWretrievesfWretrievingRW8WWreturn܆WWreturnedېWVWvWWreturnsېW܄WWreview;Wreviewsection6.3andmakechangesasneeded;VreviseWrevision(W,WrevisitWWWWrevisitparametersusedbylinkdownforidentifyingaccessVrevisitparametersusedbylinkupVrevisitparametersusedbylinkupforidentifyingaccessroVrevisitwhetherthisissuitableVrewordWWVVWܷWrollbackRWۉWRW܃WrollbackactionthreshۉWrolledRWrootbWroutersWWroutingOWPWWrowܓWrrcCWrregisteruWWrWrttW WrtxJWrulesWWWWWrxlevncellFWGWHWIWsW'WOWPWQWRWSWTWUWVWWWfW&WCWs0001&Ws0004-dۡWs0024&Ws0024-a'W*Wy band&W'W'WA  33overmobility+W+WmultipleWmultiplexWWWneedWWWWWWWWWWWmultipleWmultiplexWneedWWnet3W3W3WnetworkWnewWWWWWWWWWWWand simply described as a tree or trees. The use of RDF for MIIS is not sufficiently justified.@A  33d664g2320iYoshihiro OhbakAJust defining a structured data as a tree or trees is not sufficient. A query language that can understand the structured data is needed for efficient information retrieval. Without use of a query language, the way to retrive information on the structured data is quite limited. That is why XML/RDF query is supported to address this issue. It is recommended to read 21-05-0347-00-0000-XML_IS_Introduction.doc for more information.mRejectedobing k|bmethod/modeۖWWmethodsܬWmetricsOWmetropolitanpWmgmtWmh2WmibWmics|W|WtܴWܴWpWpWpWWmiesuWmightWWmigrationWmih W"W$W'W(W*W,W-W.W/W0W5W:W;W=WCWDWLWMWNWOWPWQWRWSWTWUWVWWWdWfWiWlWpWsWuWvWwWxWWۂWۄWۆWۈWۉWۊWۋWېWۭW۾WWWWWWW#W,W2W7WOWUWVWWWXWZW\WcW܅WܐWܥWܫWܯWWWWWW*W0W1W3W;WCWyWzW|W݂W݃WݎWݛWݥWWWWWWWWWWWW WWWW W!W"W%W'W+W,W/W0W1W2W3W4W5W6W7W8W>WBWDWEWFWWW[WWbreason,WWWreasonsIWreassemblyWreceiptېW WWreceiveLWېWUWVW|WWWWreceivedIWVW5WmWreceivesNWreceivingWW WWreceptionWW܌W"W$WrecipienteWfWlWېWWrecommendationqWrecommendationsWWrecommendedWreconfigureWreconsiderWWreconstructedWrectangle,WredefineCWvWredefinethemwhereeverthereisadiscrepencyasrequestcoCVredraw Wredrawthefiguretoindicateallpossibilitiesordeleteth Vredrawing۽WreevaluateRWRWRWRWRWRWRWRW*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*WBWreferencecouldbemadetostaticschemaeintheisqueryVt\bremovesentence@Dremovethe@"removethefirstsentence@ removethewordrequestattheendofthesentence@removing@|renamethenon-posmihentitytomihnon-posforconsistency@ rephrase@replace@replaceafterupperlayerentitiesmakeshandoverdecisionw@replacelinkbynetworksincethisisnetworkselection@replacelinkcommandoriginatewithlinkcommandsoriginate@replacemaintenancewithabetterterm@replacenetworksecurityandqualityofsecuritycapabilitie@replaceshalldefinewithdefines@21-06-0627-00-0000-n@litie@apabilitie@worksecurityandqualityofsecuritycapabilitie@ilitie@ion" 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 ccapabilities<WܾW|WcapabilityېWܬWPWWOWYW\W|WWWWWWWWWW1W5WIW}WWWWWWWcapableOWtWuW"WcaptionKWcaptureWcareWcarriedyWzW{WUWWcarriesܕW'WcarryܰWaWݍWWcaseWWZW WݗWW WWWWWW WW2WlWcase2descriptionisincorrectݗVcasesWW܄W'WWWWWcategorizationWcategorizedWcategory)WWcatualwWcatuallengthofthevaluefieldwVcauseZW>WWWcausesbWW8WcausingWccsds>Wcdma2000%WcellWcellsWcellularWcertainWWWWWcertainty3WchanelWWsWܳWܷWܸWܹWܾWܿWWWclearerWclearlysWܪWܴWW'qEQiaobingFXieGMember^ Editorial_110`23a8.1b4More and merge text between lines 23-43 into 8.3.1. cANThe last two paragraphs in 8.1 are out of place and should be moved to 8.3.1. N@A  33d682g2326{k) done 2006/09/21 2006/04/24rEQiaobingFXieGMember^ Editorial_111`12a8.2.1bA5Change title to: 8.2.1 L2 Data Frames Packet Format5@@A  33d679g2325{a) awaiting resolution 2006/09/15 2006/04/24qEQiaobingFXieGMember^ Editorial_110`23a8.1b4More and merge text between lines 23-43 into 8.3.1. cANThe last two paragraphs in 8.1 are out of place and should be moved to 8.3.1. N@A  33d682g2326{k) done 2006/09/15 2006/04/24rEQiaobingFXieGMember^ Editorial_111`12a8.2.1bA5Change title to: 8.2.1 L2 Data Frames Packet Format5@5@5@EEE8ielbadding&WWadditionWadditionalSWVWWWtWbWݸWWWadditionalbehaviourforthegetinformationprimitivesneedVadditionallyۗW۶WaddressxWWkWݍW"W#W$W%W~WfWhWrWWXWWWaddressingkWaddressingthenewpoashouldchangetoaddresswhenatthekVadequatelyܬWadjustOW܁WadoptݒWݓWݜWAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWYW[W\W]W^W_W`WaWbWcWadoptsuggestedchagesdescribedid21-06-0609-ismultihopsݓVadoptsuggestedchange1in21-06-0522-04-sessioidentifierݒVݒVVadoptsuggestedchangein21-06-0xxx-linkidentifierdocAVBVCVDVEVFVGVHVJVKVLVMVNVOVPVQVRVSVTVYV[VadoptedWadoptionWadvancedWW#FFeder^Technical, Binding_104`41a 7.4.14.1.3bAWhen the mobile node initiates handover which may be informed by Link_Going_Down remote event service, serving old PoA generates this message to achieve network address related information prior to the handover.@AR  33g  o  r  33RcAWhen the mobile node initiates handover which may be informed by Link_Going_Down remote event service, old PoA generates this message to achieve network address related information prior to the handover. Change text, change "old" to "serving". Consistent with other SDOs d653g2262wAccepted{k) done 2006/09/21 2006/04/28 $EPeretzFFeder^ Editorial_104`48b104`48b    336 =  @  33A 33wAccepted-Modified{k) done 2006/08/21 #EPeretz idasۓWCWW\WoWpWrWsWtWvWWWWWWWWW WeunahW8WWW>WBWWWWWWeunahkimV8VVV>VBVVVVVVgroting?W@W|WWuWWWW W+WUWVWYWWgupta"WZW۳W۴W۶WWWWݓW)W-WvWށWWWWWWWWMWOWQWTWvWzW~WWWWWWWWWWWWWhongܾWWWWhongchengܾVVVVjinwWdWWWoWrWrWrWVV,V1V3V>VKVgVhVperesse!W۬WWWWWW+WWWWW W0W݂W݄WݍWWW,W1W3W>WKWgWhWronny<WuWNWWWW+WOWPWQWWa"btlvsܕWWW@W W!W"W#W$W'W(W)W*W,W-W.W?WAWCWFWGWHWIWJWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW\W]W_WbWcWdWeWfWiWjWkWlWmWnWpWrWsWtWuWvWxWyW|W~WWۂWۄWۇWۈWۉWۊWۋWېWۑWۓWەWۖWۚWۭW۲W۳W۵W۷WۻW۾WWWWWWWWWWWWWWWWWWWWWWWWWWW#W)W,W/W2W7WDWEWHWNWTWUWVWWWXWYWZW\W]W^W`WaWbWcWeWiWkWlWmWoWqWsWtWwW|W܂W܅W܆W܋W܏WܐWܑWܒWܔWܖWܡWܢWܤWܪWܱWܴWܺWܻWܾWܿWWW-kThe whole notion of 802.21 as specified in the PAR is to OPTIMIZE handovers. That in itself is also not very objective and mesaurable.m Question?vDelete the lineswAccepted{k) done 2006/09/21 2006/04/28.EAjayFRajkumarGMember^Technical, Binding_22`40a5.4.3bzTo improve consistency, "handover decision module" should be replaced with "network selector", formally defined on Page 9.cTThe "handover decision module" is never defined nor used elsewhere in the document. d172g2233wAccepted{k) done 2006/09/21 2006/04/28/EAjayFRajkumarGMember^Technical, Binding_29`39a5.6baReplace "MIH Function entities may also send....." with "MIH Function entity may also send......"clTo be consistent with notion that one instance of MIH be in a network element or mobile change the followingd210g2234v=Change "entities" to "entity" in both places in the sentence.wAccepted{k) done{k) done{k) donek Guptaef2wAccepted-Modified{k) done 2006/09/21Marked!EFarrokhFKhatibiGMember^ Editorial_3`53a1.3b/Replace "interfaces" with "access technologies"c;It is not clear what "supporting multiple interfaces" meansd19{k) done 2006/08/29"EFarrokhFKhatibiGMember^ Editorial_3`61a1.3b$Use "at various" instead of "other".cImproved phrasingd24{k) done 2006/08/29#EFarrokhFKhatibiGMember^ Editorial_4`2a1.3bsee item abovecsee item aboved27{k) done 2006/08/29$EFarrokhFKhatibiGMember^ Editorial_4`3a2b*Remove parentheses; Remove "originating".cClarity, conciseness.d28{k) done 2006/08/29&EFarrokhFKhatibiGMember^ Editorial_5`6a2bSupplement with 3GPP2 standards references. As a minimum, suggest adding C.S0001~0006, C.S0024, S.R0087, X.P0028-100 and X.P0028-200.cMissing references from 3GPP2d38pTried best to add details{k) done 2006/08/29' vmechanismsەW۫W3WWmediaەWܰWWWWW#W4WWmedia-dependent*WWmedia-specificWmeetingWmention۪WWWmentionthatvalues7-255arereservedVmergethiswithcomment212VVV WWmessages۔WW"WWWjWmethodsWWnWmhzWmibjWmichaelWmih*WQWRWSWTWgWlWWܰWW3W{W}W݃WݓWW"W,W4W5WaWއW\WWWWWWW W#WjWoWWWWWWWWWWWmihconfigurethresholdshasbeendeletedfromtable-4VmihfunctionreceivesthiseventfromlinklayermihfunctioQVRVSVTVmihlinkhandovercompleteeventisverydifferentthanmihVmihlinksapismediaspecificܰVmihlinksapisnowaddedtofigure12andexplainedinsectVUperetz  "#$%&'()*stuvwxyz{|}˃΃#qiaobing "#$()*+?@ACDGIJKLOPQRSTUVWZ^`cdefghilpqrstvwxۀWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ƒʃ̓reijoronny{8sanjeevەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫ۮۯ۰۱۲۳۴۶۹ۺۻۼ۽ۿƒÃăƃǃȃʃ˃̃̓Ѓуԃ؃كۃ܃ރbremoveaccesstoVremoveack-rspbitandchangereservedfieldto5bits}VremoveannexbۀVremoveannexcVremoveassuchVremoveatnetworkside5VremovebasicallyVremoveboldformatfortimeboundandconfidence:Vremoveconceptsofposandnon-pos VremovedashbetweenlinkandlayerۣVremovedashinlink-state8Vremovedashinmobility-managementGVremovedestinationidentifierparameterVremoveeitherdifferentorheterogeneousۙVremoveentiresection7.4.10]Vremoveentiresection7.4.11^Vremoveentiresection7.4.12_Vremoveentiresection7.4.13`VremoveexampleorbetterconveyincrementalvalueVV.Vremovefahah-aaav-aaa!V!V3Vremoveentiresection7.4.134V4Vtiresection7.4.123Vremoveentiresection7.4.134V4VtypepossiblyaddlinktypeinsteadVremoveinthe21draftPVremoveisembeddedVremoveitis۹VbinzW{W}W݃W݌WݎWݒWݔWݕWݖWݘWݛWݜWWWWWWWWWWWW W WWWW W"W$W&W'W,W4W5W8W>W@WBWIWLWMWuWWހWނWކWއWފWދWތWޏWސWޑWޓW6W[WsWvW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W"W(W*W,W/W1W7W8W9W>WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWYW[W\W]W^W_W`WaWbWcWkWuW}WWWWWWWWWWWWWWWWWWWWWWsWsWsWsW`^#bresidesWܟWresidingWresolution,Wresource܇WwW6W|WWresources"WpWW WWWrespective*WWrespond܅W܆WrespondseWlWېWWresponseeWlWۄWۋWېWNW܁WܕWzWWW%W>WBW[W}W~WނWރWޅW=WtWWWWWWWW/W7W8W{W}WWWWWWW#WresponsenetworktypeWresponsesܕWresponsibilityWWܕWܕWeۊWresponsesܕWܕWܕWܕWܕWܕWܕWܕWܕWܕWܕWܕWܕWܕWܕW 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 and BjpurposeWqosܾWWWtWqueryjWuWWquery/response|WquestionWratezWrather,Wreadable=WreasonWredundantށWreferenceWreferencepointsareusedinthedocumentegline24-49pagVreflectedWregister/deregisterWregistr/deregisterWrejectWrejecttheproposedremedyVVV  .vintra-technologyەWintroducedWW"WinvestigatedmWinvoked{WipWipv4ޏWipv6ޏWislW۔W۪WWW)WܰWW WW{WݓWݜW"W*W4W5WnWށWޏWjWWWWWWWWWWWWWWWWWWWW WW W"W:WUWVWjWkWmWWWWWWWWWWisencapsulatedandincaseofmobileipv6ޏVissue-WW[WuW|WWWWWWWWWWWWWWWW-W3W4WmWoWqW~WWWWWWissue1Vissue34Vissue40Vissueidentified3VissueidentifiedandassignedVissueidentifiedandassignednosuggestedremedyVissueidentifiednosuggestedtextVissueidentifiedsuggestedremedycannotbeappliedtoaspeVkincrease"Windepedent\WindependentݓWuWindicationWindividualWWWinform|WinformationdWtWuWwWxWyWzW{W~WWWWWWWWWWWWinformationserverwouldbeoneofmihuserssoindicationpVinformative"W۴WWinsteadWWinsteadoftryingtomapmihprimitivesto3gpp/3gpp2802.21VintendedvWinterface}Winterfaces~WintergerYWintoWintroduceWWWintroductionwWxWyWzW{W~WWWWWWinvestigationWipgWrWWWis#W#W#W#W#W#W#W#W#W#W#W#W#WWܶWܸWܺWܻWܼWWWW݀WݳWݴWݻWW-WOWjWoWisthisabootsrappingissueifnotthenwhyithastobemeܺVisthisfortlvonlyisthatisthecaseweshouldsaytlviCVv ހbGh-------------------------------------------------------------------------------------------------------  @A$ 33!  * 5 33     33  *  5 S UU|    UU    UU,  2 UU    UUz   UU. B N UU 33l  33s    33  N 33   ! 33cTable 22 needs to be revised. d806g2427wAccepted{k) done 2006/09/2122 ށEKenichiFTaniuchi^Technical, Binding{$ ~bBA/> aabbccddeeff 0123456789ab ", Success)/@Aj 33R  ] i 33    33  33    33"  $ ' 33    33jc^ - ' - ' can not be used for Variables e.g. ?poa-address - Also SPARQL query is not correct.d677g2425wAccepted{k) done 2006/09/21 EKenichiFTaniuchi^Technical, Binding_119`48a8.4.1.4b8.4.1.4bvbLreplace section 5.5 with contribution 21-06-0620-00-0000-New_Section_5_5.doccEReplace with updated text for section 5.5 listing all the 4 MIH SAPs d178g2235i Vivek GuptakA&This has been brought up many times in past as well. The value of defining MIH_NMS_SAP in 802.21 is not very clear as pointed by some others and it's not clear what is intended to be accomplished by defining MIH_NET_SAP. It's very clera 802.21 shall not be defining any primitives for this SAP.&mRejectedvzPlease refer to contribution 21-06-0736-02-00-0000 for updates and explanations. Accept remedies as per this contribution.wAccepted-Modified 2006/09/21 2006/04/28wEPeretzFFeder^Technical, Binding_25`1bQReplace section 5.5 .1 with contribution 21-06-0624-00-0000-New_Section_5_5_1.doccGReplace with updated text for section 5.5.1 listing all the 4 MIH SAPs d190g2236vby comment 178w Superceded 2006/09/21 2006/04/28xEPeretzxEPeretzxEPeretz0^technicalwaseditorialVVIVRVnVޖV?VYVZVpVVVVVVVVVVVVVVVVVVVwas W$W(W*W+W@WAWCWKWpWsWvWۛWۼW۽WWWNW[W]WܭWWWWWWWWIWRWnWޖW?WYWZWpWWWWWWWWWWWWWWWWWWW> cnotۅW۔WەW۟W۪W۽WWWWWWWWW$W)W.W3WAWBWCWYWZW]W`WhWkWmW{W܁W܂W܄W܋WܒWܔWܕWܖWܟWܫWܰWܱWܾWWWWWWWWWWW W WWWWW!W0WEWGWOWaWeW{WW݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݃W݁W݁W݁W݁W݁WWWWWWWWVyuba-4Waabbccddeeff~WabilityWable#WOWtWWWabortreasonۋWaboutAWDWVWpWۃWېWW9WWWtWW8W>WWWaboveZWsWܬWܭW#WWWWWsWWpWtWWabstraction5WܟWacceptۃWۄW{WWWWWaccept21-06-0627-00-0000iesdocVVaccepttextchangesinthecontribution21-06-0611-00-0000-m{Vacceptthechangesasdescribedin21-06-0628-00-0000-aabouۃVacceptthechangestosection7.4.7.2.2asdescribedin21-0ۄVacceptthecontribution21-06-0624-00-00figuer15pptVacceptthecontribution21-06-0625-00-0000figuer18pptVacceptedtWtWtWtWtWtWWWWۃVۃVۃVetherthescopeoftheprotocolfunctionsLVitisnotinscopeof802.21toprovidehorizontalhandoverVitisthefirsttimethattheframestructureisreferredtoVg&cmissingWWWCWWWWSWgW܎WܨWܵWW&WiWrW݆WݛWݿWWWW[W\WޒW[WWWWNWOW\WWWWWmissingaperiodޒVmissingathatinthefollowingsentenceandcoordinatetheVmissingcommaVVmissingdashrVmissingreferencesfrom3gpp2&V&VrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVlenodewithmihfunctiongenerallyhasseveraldifferenۉVmobileterminalchangetomobilenodeۏVmobility"W:WܤWܴWWmodeۂWWmodel!W$W۽WW"W:WAWFWmodify;WmoduleܤWmore_WwWۆW۳WWWWW-W:WܓWܗWܸWܼWܿWWWWWWWWWWWKLxbAChange text to: The purpose of the MIHF protocol is to exchange information between two peer MIH Functions by using a transport protocol. In order to achieve a successful communication between two MIHF peers using this protocol there is a need to address and identify the communication path or session between them. Following identifiers are used to serve this purpose. in MIHF protocol messages:@Az 33  TT>  ]  TTs  )ct  )czcAFThe wording is loose and largely repeating what has been said earlier.F@A  33d718g2333{k) done 2006/09/21 2006/04/24 ۀEQiaobingFXieGMember^Technical, Binding_148`1aAnnex BbRemove Annex B.cA8The relevance of Annex B in 802.21 spec is questionable.8@A  33d892g2342wAccepted{k) done 2006/08/29 2006/04/24 2[Ccaware0W1WWawayWbۀWWtWuWbaddanstorelayonline24VbackeWWbackbone}WbackoffWbaseiWwWxWyWzW{W~WWWWWWbasediW۶WWWWWWWbasicOWYWWWbasically<WbasisWbbmWbe$WAWGWIWJWKWLWOWPWQWRWSWTWUWVWWW`WcWdWfWiWqWsWtWۄWۅWۋWۍWېWۓWەW۝WۡW۪W۴WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWed2W3W4W5W6WexpectedWexplainHWIW|WJWexplainusageofthewordmediaIVexplanation WexplanatoryW EPeretzFFeder^Technical, Binding_19`4bRemove the above senetencecMobility management entities are merley shown as a possible scenario of interaction with mobility and security frameworks. Mobility management entities are not shown in this sectiond144g2229wAccepted{k) done 2006/09/21 2006/04/28EPeretzFFeder^ Editorial_20`52a5.4.1.3bOne of the stacksc*One of the stack may be.... one of many, d148g2230{k) done 2006/09/21 2006/04/28 EPeretzFFeder^ Editorial_21`17bAyCommands may be invoked from upper layers (MIH Commands) as well as from the MIH Function (Link Commands - see Figure 16)y@A*  33i  *cACommands may be invoked from upper layers (MIH Commands) as well as from the MIH Function (Link Commands) Text is red is confusing w/o a reference to Figure 16@@@cate with each other via R4j@pvO4 #bAReplace POA with new POA: It is important to note that before a MN is authenticated with the new PoA and ready to transfer data, the MN should be able to obtain all the information elements available. These information elements may be used by the handover policy function to determine the appropriate PoA to attach. Before authenticating with the new PoA, the MIH Function in the MN may extract the Information Elements either from media specific broadcast information or by sending a specificBU information request/response primitive, in which case the MIH protocol is not used. C@Af 33^ b 33\ _ 33fc?"... autenticated with the POA and ..... ", should be new POA d387g2450wAccepted{k) done 2006/09/21$EDasFSubir^Technical, Non-binding_47`52a6.3.3.ba6.3.3.bhe MIH protocol is not used. C@WkitAWۓW۴WW\WrWuWwWxWyWzW{W|W~WWWWWWWWWWWWWWWitdoesn'tmakesensetomanditorilysupportxmlandtlvVitisnotclearwhatadditionalthingsweneedtodowiththۓVitshouldbeclearwhichreferencepointsareoptionalinfor۴Vit'sWWvWitemWitsW}WV۴V۴V۴V۴V۴V۴VWoWzW{W|W}W~WہWWjustdefiningastructureddataasatreeortreesisnotsujVkVmVnVoVzV{V|V}V~VہVkeepaWWknowWknowledge0WlanguagebWjWkWmWnWoWzW{W|W}W~WہWlayerWxWlayers0WWleft"WOWlessWlevelݴWlike"W0WaWWWWlimitedjWkWmWnWoWzW{W|W}W~WہWہWہWapability+VW  cA}MIH function should reject the registration if the MIH user tries to register for an unspported events or unavailable events.}@A  33d279g2256vAAdd the below text: "If the MIH event that an MIH User is registering for is not supported or not available, the MIH Function shall be able to reject the registeration and notify the MIH User."@A* 33  )c*wAccepted{a) awaiting resolution 2006/09/21 2006/04/24EQiaobingFXieGMember^Technical, Binding_37`43a6.1.6bClarify whether the Event Nos in Table 2 and Table 3 are meant to serve as the Event IDs. If not, clearly define Link Event IDs and MIH Event IDs. cThe definition of Event IDs are missing. It is critically important since Event IDs are used in many section 7 primitive definitions. d280g2291280g2291ng_37`36a6.1.5.2b may have mis-classified them.mRejected{a) awaiting resolution[XbtheW W"W#W$W*W?WAWDWGWJWOWPWQWRWSWTWUWVWWWZW`WcWdWeWfWhWiWlWpWsWvWwWxWۃWۄWۅWېWۓWەWۘWۚW۠WۤWۧWۨW۪W۫WۭW۳W۶WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW (otherwise, "Show All Records" button in Create and g2461 2006/04/288*"balsoAWVWWWsWۜWۧW6W܂WܾW)WOWݍWWW W"W/WއWtWvW|WWWWW/WWWalsoneedtoaddtable33aValternativelyۗW۶WW(WalthougOWalthoughWalwaysWݗWamendWWPWamendreferencesVamendsentenceVamendtailendofsentenceasgsmcdmaoranyothercellularPVamendmentۅWWamendments)WWammendmentsWWkWamong3WamountW۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾W۾Wterms+W,WeWpWٱW>WterrestrialFWtestoWtextW WW-W7WHWqWWW%W.W0W3WWWWtextbetweenline43page43andline12page44isnotabou7VtextdoesnotreflectthedependencyofthetransportmechanV py0Group needs the submission number in the comment{a) awaiting resolution 2006/09/21F-44PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP~cunnecessaryiW/W0Wunrealistic*Wunreliable W WunspportedWunstructuredZWsWunsuitableWunwantedZWunwieldy9Wunwieldysentence9VupWݍWWކWWWWWWup-to-dateWupdateWupdated)W;WkWWW WvWwWxWyWWWupdatesۋW WupdatesmihhandoverinitiatemessagetoextendmihfunctionۋVupgradeWupon W"W$W*Wuponreceiptthereceivingmihfunctionintheoldlinkmay Vuponreceptionofthisprimitivethemihfonnewpoamayeit$V$V$V$Vt$V$VV$V$VV V V V V VOWPWQWRWSWTWUWVWWWۅWۉWېW۵WW7WYWZW\WcWeWfWܢWWW݇WݍWݎWWWWW"W$Wuppers݇WWWWurl{W}W`btraversedWtreeZWsWtWvWtreestWvWtrieslWtriggerIWIW"W$WmWtriggeredWtriggers WtrueWtryinglWtwo?WxWYWܬWWfWwWzW݃WݖWWW&W'W,W|WWW7WWtwooptionsfortheresolution1makethemihfunctionblock,VtwotypesoflocationinformationareݖVtxtݕWݖWݘWWݘWݘWWݖWݘWݘWݖWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWݘWW_WjWmWW=WJW`WdWܤWܷWܾWWhWݖWtypicallyAWܤWܱWݎWtypicallyinaheterogeneousnetworkenvironmentcomposedofܤVtypo۠Wucd|Wudp/ipWudp/tcpsWue܋Wuiuc|Wuk/currency/byHWumts_W=WCWunchangeableۂWunclear۫W6W2cinWWWWWWWmay change and even the link type may change in a way which is not visible to the initiator (e.g. if the initiator is deep in the network). ijkmnpvw{ 2006/05/146/04/28specify .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 abThe description should be phased in more media independent terms, and the representation column should be made more explicit, e.g. the link-layer address of PoA; this representation is technology dependent.cmUse of MAC address is not technology neutral enough to incorporate all technologies addressed by IEEE 802.21.d374g2245iMathieu Peressej4Use TLVs for variable PoA identifier representation?v8call it as PoA identifier and do not specify MAC AddresswAccepted-Modified{k) done 2006/09/21 2006/04/286 EEleanorFHepworthGMember^Technical, Binding_46`8a6.3.2b3Add sentence to 3.2 representation to reflect this.c\Need to explicitly state that both types of location information are re-used by IEEE 802.21.d378g2246wAccepted{k) done 2006/08/29 2006/04/286 EEleanorFHepworthGMember^Technical, Binding_47`7a6.3.2bremove.c9"Others" is not appropriate in the representation columnd385g2248wAcceptedJcjust+W܂WܥW݇WݔWfWgWhWiWWWWWWWjustification|W}W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmissingandܨVkindsۉWknowۅWۉWېW6WcWmW܄WOWknowledgejWkWmWnWoWzW{W|W}W~WہWknown܋Wl݆WWl-shaped,Wl2W܌WܩWܭWܲWWW3Wl3rWWܩWܴWW+W3WDWWW0WlabelqWlabeledqWlacDWlackWWWW[W\W]WfWlanguagejWkWmWnWoWzW{W|W}W~WہWܬWlargeWWWlargelyxWlastqWsWܕWWWWWWޗWlatenciesWlatter.WWW ^technical W"W$W(W*W+W@WAWCWDWGWIWJWKWLWOWPWQWRWSWTWUWVWWWZW^WcWdWeWfWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWVreplacefacilitieswithamorecleartermUVreplacefigure21withsection2of21-06-0460-02-0000-bschVcefigure23commonmihfframeformatwithfigure23miVreplacefurtherdeliverwithforwardڻVreplaceinterfaceswithaccesstechnologieskVreplacelinkcommandindicationwithlinkcommandrequestٰVreplacelinkcommandoriginatewithlinkcommandsoriginateٯVreplacelinkgoingdownwithlinkgoingdownVreplacelistofnetworkslinktypeswithlistofnetworktypVreplacemaintenancewithabettertermwV~bipWWݍWW1WrW WWiprenewalindicatorbooleann/a0changerequiredVipv4ޏWrWޏWޏWޏWޏWޏWDWFWGWJWLWMWXWZW]W_WcWdWiWjWkWlWmWnWpWsWuWvWwWxWۂWۇWېW۝W۶W۹WWWWWWWWWWWWWW#W)W*W2W=WGWHWKWLWNWRWTWUWVWWWXWZW\W]W^W`WdWkWsWtWzW{W|W܅W܆W܋WܕWܟWܡWܢWܤWWWWWWWWWWWWWWW W)WPWUWWWXWYW^WnW}W݂W݊WݔWݗWݘWݛWWWWWWWWWWWWW WWWWWW!W"W$W%W'W1W2W3W4W5W7W8WCWTW[W9predrawۏ۴W-ܑܵWW݃W@Wކ2W=redrawing۴Wredrewzref۽WRWrefer݃WreferenceWreferredWrefers;W݃Wreg}WrelatedCWremove۽WݜWremovedۏW.W WލWremovedmiesmentioning Vremovedthe2ndmobilenodedefandremovedthe2ndsentence.VremovingWrepeatRWrephrase۪Wrephrasethesentenceto۪Vreplaced۴W۽W:WvWreplacedfigures9and10۽Vreplacedthefigurewithsection2of21-06-0460-02-0000-bsvVreplacingWݜWreservedVWލWresolutionܵW@Wresponse܁WretrievalZWright۽Wronny{WsWsa{W2WsameۖWܡWݜW\WEEleanorFHepworthGMember^ Editorial_5321 to try and specify an exhaustive list of all possible location determination schemes. 4d425g2278 2006/05/14 2006/04/28EEleanorFHepworthGMember^ Editorial_53 |GbAf 33)  337 33]  33g 33f393g2424 2006/08/04 2006/04/28 dihiroFOhbaGMember^Technical, Non-binding_7`1a3bAAdd the following text: " * Mobile-assisted, network-controlled handover A network entity instructs the network and the mobile node for handover with the assistance of the mobile node in executing handover procedures and where the mobile gathers information, such signal strength measurements, and reports to the network node. Most of the cellular networks work that way (e.g., MSC controlled) * Network-assisted, mobile-controlled handover A mobile node instructs m "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 14rialxI>csolution#WWsolutions۶WWsomeiWiW܄WW݅WW'W,W?WWWWWW WWsomeindicationdatasuchaslinkdetectedVsomehow݅WsomethingfWgWhWiWWsometimes!WsomewhereWsophisticatedW W WceidentifiersourcesZWspaceWW-WWWiWspacesWWspans۪Wsparql{W|W}W~WspecW'WuWwWWۀWܸWspecial:Wspecially Wspecific'W-W_WaWWW W$W:WCWaWiWܘWܰWܺWܾWWWWW~Wspecificformatforthevalueportionineachtypeofinform~Vspecifically WspecificationW۩W۾WWW WWܟWWWWspecificationoftypeienetworkqosisnotmediaindependenVspecifictaion+WspecifiedWېWW܌WܾWWWWWEWbspecDW[Wspecific)WJWiWۉWWW#W$WaWiWܾWWW0W݃WW,W2WށWރW[WtWWWWWWWWuWWspecificallyPWspecificationYWܟWWWWWW8WކWWWWWWWspecificationshouldbeaddedevenifthisisjustanxreftVVWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWtaticVspecifyparametertoidentifylinktypetoscanVspecifyingVWWspeedFWGWHWIWJWۉWspelled۝WsplitWWsquareWssid[Wstack/W7WqWܫWstagesܳWstandard WsWvWwWەWWWWWstartOWVWۉWstartedۉWstarting܍Wstate,WWܳWW WstatementW WWstaticWWstationWVcbeconsistentwiththemdeiadependentandmediaindependentVbeaconW#@Ã#P۰Ã#`6Ã#pÃ#<Ã#XÃ#۱Ã$Ã$ Ã$09Ã$@Ã$P7Ã$`Ã$pÃ$Ã$۲Ã$8Ã%۳Ã% ۴Ã%0!Ã%@Ã%PÃ%`"Ã%pÃ%ܫÃ%Ã%ݍÃ&6Ã& Ã&0ݎÃ&@"Ã&P۶Ã&`Ã&p<Ã&ܬÃ&#Ã&Ã'Ã' ?Ã'0-Ã'@Ã'PÃ'`Ã'p=Ã'>Ã'Ã'ܭÃ(ݐÃ( ۹Ã(0.Ã(@Ã(P?Ã(`ۺÃ(p@Ã($Ã(vÃ(ۻÃ) AÃ)0ۼÃ)@Ã)P#Ã)`uÃ)pÃ)݃Ã)=Ã)Ã*wÃ* xÃ*0yÃ2Ã32Ã3 YÃ3@4Ã3P5Ã3`HÃ3ܰÃ3ZÃ3[Ã408Ã4P(Ã4`Ã4pÃ4Ã4Ã4nÃ5)Ã5 *Ã50Ã5@Ã5PÃ5`Ã5pÃ5+Ã6{Ã6@IÃ6`ܱÃ6Ã6:Ã7 Ã70ݑÃ7P7Ã75NbchangeifapplicablethenewsapsshallberecommendedasamVchangeinmostcasestoinsomecasesVchangeincludetorequire>Vchangeinsecuretonon-secure<VchangeiscommunicatingtocommunicatesisresidingtoresidVchangeittowillresultݑVchangeittoxmlݚVchangelinkeventderegistertoacommandVchangelinkeventregistertoacommandVchangemakestomakecVdVchangemiheventderegistertoacommandVchangemiheventregistertoacommandVchangemihlinksapinline46tosaywhichisatechnologyVchangemihfnetworkmihnetworkVchangenametolinkconfigureparametervalueasdefinedin܂VchangenetworkmaybeabletoindicatetothemobilenodetoOVchangenetwork-sideendpointofalinkthattonetwork-side+Vndpointofalinkthattonetwork-side+V+Venetwork-sideendpointofalinkthattonetwork-side+V+Vstandards?VWWWWXW6celements@lements@ntries@oentry23miheventregisterandmiheventderegisterincorre@Bequivalent@ event@events@Veverything@Nexchanges@,execute@expansion@explainusageofthewordmedia@field@fig/table@:fig/tableifapplicable@figure24isincorrectinparticularitimpliesmihfusingi@figures@forۋ~%forbettersentenceflow@]forno1.2intherepresentationfieldifnetworksofthesa@force@form@forwarding@front@function/operation@1functionality/capabi@g@2general@(get@goal@goes@ handover@2handovermoduleisneverdefinedorusedelsewhere@handoverneedsabetterdefinition@have$havemorespacebetweencharactersinsta/ueandpsdn/fabox@he@here@high@horizontal@phrpd@ie@ifL/bwhatLWWWWWWW$W<WkWwhenGWLWOWVWdWېWWNW^WܕWkWWWW#W$W}WހWނWޖW5WlWxWzWWWWW+WtWWWWwhen802.16macreceivesneighboradvertisementmobnbr-advNVwhenprovisionedthemnVwhenthemobilenodeinitiateshandoverwhichmaybeinforme#V#VW5W5W5W5W5W5W5W5W5W5W5W5WcWpWܶWW݊WW W%W}W~WwhereeverCWwhether-WNWWWPWޫWWwhich-WFWGWOWPWQWRWSWTWUWVWWWbWkWnWpWuWWۇWۉWېWWWW#W=W\W]WWܕWܟWܡWܪWܺWWWW W WUWWWYW\WݍWݔWWW"W#W$W'WWW}WޫWWWWWWW<2^technicalݵWݺWݽWݾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW*bmihreferencemodelforaccessnetworkstechnologies$Vmihreportinfoqueryresponse|VވVmih-3g%Wmih-3glinksapshouldinterfacewithl3functionofthecdm%Vmih-enabledXWmihbasic~WhecdmDVmih-enabled!Wmihbasic~W~WfunctionofthecdmDVmih-enabled!W!WecdmDVmih-enabled!W!W!WWWWWWWWWWWWWWxWWۇW۵WWoWܚWܥWܯWWWW WW_WyWzWݴWݸWWWWW!W"W$WXWއWޕWmihf/802.21YWmihoܠWmiisAW_WlWuW۳WW}WW޿WW.W_WmiisprovidestheabilitytoaccessthisinformationaboutaVmilliseconds\W]WmimeހWނWminimal=WminimizeVWWtWminimized۸WWminimumWW\W&WWminuteHWmipJWmissingܺWWmlme3W#6^editorial݋݌ݐݑݚݭݲݸݹݿwwne 1cRThe Transaction ID is already defined in the Fixed Header part of the MIH message.d751g2306 2006/05/14ers are present that help to analyze and coordinate the payload are embedded."@A 33\  33^ 33  33 33  33 33cqSyntax error in "additional identifiers are present that help to analyze and coordinate the payload is embedded."d746g2305 2006/05/14uENada, Golmie, Member^ Editorial_116`1b Remove line 1cRThe Transaction ID is already defined in the Fixed Header part of the MIH message.d751g2306 2006/05/14d is embedded."d746g2305 2006/05/14uENada, Golmie, Member^ Editorial_116`1b Remove line 1cRThe Transaction ID is already defined in the Fixed Header part of the MIH message.d751g2306 2006/05/14])vby comment 281w Superceded{a) awaiting resolution 2006/09/213EAjayFRajkumarGMember^Technical, Binding_39a6.2.2bWstretchۿWstretchdiagramhorizontallyۿVۿVW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W#WZW]W_WbWsWܬWWWޡWWWAWWsttausWsubjectWWsublayer1Wsublayers݃WsubmissionSWsubmitQWsubmittedۊWۋWsubnet?W޽WW,W]WߛWsubscribed7Wsubsection'W݀WޥWWWEW߃Wsubsectionof6.3.8shouldbedeleted݀VsubsectionsWsubsequentݗWWއWZ cAFor Item 7 of Table 2: According to the defintion of this event, information is regarding whether a PDU from Higher Layer is successfully transmitted. Segamentation would be carried out and handled by the Link Layer, e.g. the MAC. The specific segaments's tramission status would not be usefaul to the Higher Layer. Therefore, for this event, what should be included is whether a higher layer PDU is successfully transmitted instead of the "PDU segment" or the Link SDU. Same comment for ItemB 7 or Table 3 in section 6.1.7 d282g2219i Qiaobing Xiej8change text to: "Indicate transmission status of a PDU"mAccepted-ModifiedvbChange to: "Indicate transmission status of a PDU" Do this for all such occurrences in the draft.wAccepted-Modified{a) awaiting resolution 2006/09/21 2006/04/272EDasFSubir^Technical, Binding_38`42a6.1.7bDelete or add a new definition c3Administartive MIH event type has not been defined d283g2443283g2443 bqosܾW1WWWW>WtWqualifying1WqualityJWRWTW<Wqueries܁WWquery"WAWiWlWېW|W[WqW}WWހWށWނWރWބWޅWwWxWyWzW|WWWWWWWWWWW|WWWWquery-20041012qWquery-20041012httpwwww3org/tr/rdf-sparql-quqVqueryingWqueryresourcelistۋW܎W|WquerytypeޅWquickVWWquickly'WquiteWrWWWr0087&Wr1WWr1/r2/r3Wr2Wr3Wr4WraWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWredrawing۽WreevaluateRWreference$W۬W۴WWWreferencecouldbemadetostaticschemaeintheisqueryVm ނbC | not contained, MIME type "application/xml application/sparql-results+xml" is | | | | used. MIME type "application/xml" shall be | | | | supported for this type of query. | D |--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | SPARQL_QUERY_ | Variable | A value that is formatted with the MIME type specified | | RESULTS_TLV | | in the MIME_Type_TLV. When the MIME type is /013bfigure?W@WsWwW7WܑWܔWܵWWWWKWzWW WvW2WWWWWWWW W7WqWrW}WWWWWWWfillWfillinwithreasoncodesVfiltervWfinds>WfinerWVVVVVVVUWfollowing*W_WjWkWmWnWuWvWwWxWەWfollows WJWXWۂWېWWforW W"W$W-W.W?WAWDWFWGWJWMWOWPWQWRWSWTWUWVWWWZW]W_WbWkWnWpWsWuWvWWۂWۄWۅWۆWۇWۈWۉWۓW۝WۭW۳W۸WWWWforconsistencywithuseselsewheremobilitymanagementiss۝VformatrWsWvWWformatspWvWformattedۉWforwardlWfoundpWframeFWGWHWIWJWpWsWvWۉWframesrWYbaddrefertotable26inannex4inthecommentsfieldDVEVaddreferenceVaddrepresentationVaddsection6.1from21-06-0611-00-0000-mprotocoldocVaddsentenceto3.2representationtoreflectthisVaddsinrinformationelementVaddsupportedisquerytypeasspecifiedinmihcapabilitydiscIVaddsupportedisquerytypetotheparameterlistVaddtexttosupportmulticast/broascastofinformationonclVaddtheammendmentsassuggestedin21-06-606-00-0000locinVaddtheexampleassuggestedin21-06-606-00-0000locinfooVdthefollowingparagrpahinsteadVaddthefollowingtableRVaddthefollowingtext݊Vaddthefollowingtextinsection8.5VaddthemissingparameteradddescriptionforoldlinkidentifVaddthem݋Vaddtotable6\VaddtothesentenceorfromaninternallymaintainedmiisdaVaddedAWZW]WWWW}WWWW`WfWܺWWyksayCWsaying۴WWscanningdWscenariosWschemaWWWWWschemaismandatoryshouldbeoptionalVschemaeWschemasWschemeWscope۴W|WW~WWsdo|Wsection#W)WWWW:WUWYWWsectionsWseeWsWWWWQWseecomment362Vseecomment636QVseemsWWselectionWWsemanticvWWWsendWsenseݓWWWsepartaeWWserverWservicedW\WWWservicesݓWWWseveral#WrWshallvWshould۴WCWݓWOWpWrWWWWWWWWWWWshouldn'tWshowWshownWsimilarAWvWWsimilartocomment444doesthisnotmeanweneedsemanticqvVvVvVvVvVl_basW W#WAWGWJWOWQWVWWWZWiWsWۃWۄWۉWېWۖWۧW۫W۰W۶WWWWWW6W7W;WCWGWYW[WhW܂WܕWܤWܬWܾWWW&W)W0W=WPWlWWWWW-W4W5WCWLWMWVWnWޅWސWޑWޓWlWoWsWtW|WWWWWWWWWWWWWWWW W1W<WIWpW{WWWWWWWWWW#WWW&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&Wu ܫbc"Events may originate from the MIH Function (MIH Events) or any lower layer (Link Events)." This is true only for local events and not for remote events. Introduce local and remote events early on, otherwise this gets confusing.d147g3251{k) done 2006/09/21 ܬEVivekFGuptaGMember^Technical, Binding_22`2a5.4.3bAMRemove the following lines: "The capability of such network information service can be obtained via schema access. The structure and definition of schema can be represented in a high level language such as XML" Lines 27 and 28 on page 22 define adequately methods of information access and hence the above two lines re not required.McMcY  33 33>c"Events may originate from the MIH Function (MIH Events) or any lower layer (Link Events)." This is true only for local events and not for remote events. Introduce local and remote events early on, otherwise this gets confusing.d147g32517jcwhatGWIWJWeWhWiWpWvWxWەW۳W۽WRWYWWWWW!W*WޏWlWmWWWWWWWWWWWWWWW W WWW/W<W>WWWWWWwhatisa3gpp2radiodoyoumeanusinga3gpp2interfaceVwhatisanadministrativelinkeventtypeithasnotbeendeVwhatisthedeifnitionofsecureandinsecureportisthistVwhatistheunlabeledtablein7.4.7.1.4forhVwheniWۉW۩WW^WWW#W$WޖW5WWWWWWWWWW+W<WWWwhenprovisionedthemnVwhenretrievingiestheclientneedstospecifyit'sownlocVwhenthemobilenodeinitiateshandoverwhichmaybeinforme#V#V#V#V#V#V5W5W5W5W5W5W5W5W5WWWEWFWGWHWwhereverܥWZbdetailedpWW1ENada, Golmie, Member^ Editorial_92`24bA\Replace "Result of trying to conifer the link" with "Result of trying to configure the link"\@Af  33  33$  33I  33R  33fc7Syntax error in "Result of trying to conifer the link" d59g2297 2006/05/01ENada, Golmie, Member^Technical, Non-binding_93`17bAAdd a new table called ScanRequestInfo containing the following information Name Type Valid Range Description Link Identifier Identifier identifier Identify the link associated with the scan command ScanCommand STRING N/A The scan command for the link Change the Description of link 17 to "List of ScanRequestInfo"Af  33  33&  33  33  339'hongchengۉۋیێjeff᪃jin1256ᧃᨃᩃjunjunxiangۃWۄWWWWkeigo۔kenichipqtuvw|}~ހށނރބޅކއވފދތލގޏސޑޒޓឃៃ᠃ᡃᢃᣃޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓles7777777777777777777777777777777777777777777777777Wecparagraph`WpWvW'W?Wparagraph/sentence۞WparagraphsqWparallelWparamaterWparameterGWIWJWۃWۄWۉWېWYW`WkW{W܂W܎WWݽW[WaWޖWlWmWWWWWWWW W4W8WWWWparametermissingV[VparametersۄWۅWYW_W`WgWjW~W܂WܰW0WW:WޖW5WWW W8W?WNWOWWWparametertypeGWIWlWmWparenthetical0Wparethetical/Wparsing'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'WerformanceWW%wctypo WWWWWuWwWފWtypodefiiteVtypodifferenceVtypoinowlrdfresourcelongtitudewVprimitiveisusedbyuppersVtypographical۠W.Wtypographicalerror۠V.Vucd|WudpWudp/ipwWue܋Wumts۽W:W@WWCWun-usedWunableۇWunacknowledgedWunavailable.WWunchanged0Wunclear۫WWWWWWWWWWW-W݀W;WKWuncleardefinition۫Vunclearfunction/operationinboxmiisreportavailabilityVunclearterm-VunclearwhetherdurationisperiodoverwhichtheconstinfoVuncontrolledWundefinedܦWWunderuW W!W"WWWWWWunderlyingcWeWWWWWunderstandDWWCWYWWunderstandingjWkWmWnWoWzW{W|W}W~WہWJWWWWunfamiliarRWb:Add section 6.1 from 21-06-0611-00-0000-MIH protocol.doc cA section on System Management is missing. Discovery , Registration and Event Registration mechanisms are described through primitives and Protocol messages, but there is no general introduction about them in section 6.d251vby comment 250 w Superceded{l) none needed 2006/09/21 2006/04/30EFarrokhFKhatibiGMember^Technical, Non-binding_33`33a6.1.1bRequires clarificationcIf the sentence "From the recipients perspective these events are mostly advisory in nature and not mandatory. " is correct and these events are not mandatory from client's perspective, does that mean they can all be igoned?d254g3208vIAdd a statement: The recipient is NOT obligated to act on these events.wAccepted-Modified{a) awaiting resolution 2006/09/21EVivekFGuptaGMember^Technical, Non-binding_34`54a6.1.2b.Clarify description of link synchronous eventsous eventsous events$ ހbA Table 22 -- SPARQL Query TLV Value parameters Format -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | Type | Size Length | Description Value | -----------------------------------------------------------------------------B--------------------------------------------------------------------------------------| | TYPE_MIME_TLV | Variable | A MIME Type TLV An octet string for a MIME type to specify an XML a format | | | | of SPARQL Query Result. When this TLV is | | | | not containedchiC$bcopy&W\Wcopytablefromsection8.5.1.2to8.5.1.1\VcoreAW$WW!Wcore802.21hedaerspecificiesVcore802.21specificiesVcorrectWWzW7WWcorrectrregisterVcorrectnessWcorrespondingTWUWVWWWwWyWWWW>WcostHWWcouldIWUWWWWIWWmWWWW'WWcountryHWcoverVWcoveredWcreateWcreatedۚWcreationۚWcriterion-W-WW-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-Wedia)WdependentDWpWdependingAWderegisterۉWdescribe'Wdescribed'WsWۃWۄWdescribesvWdescription?WpWtWۂWېW?bchangeradiotointerfaceVchangerepresentationfieldtoݔVchangesection7.2.2.1table14toreferencecontentsofmihlVchangesection7.2.2.2table15toreferencecontentsofmihlVchangesentencetheytraversethroughthemediumtolocalmi7VchangesentencetotheselectionofthetransportmechanismVchangesizefieldforactidfrom9to10ܒVchangesizefieldforopcodefrom3to2ܒVchangesizefieldforreservedfrom4to10ܒVto2ܒVchangesizefieldforreservedfrom4to10ܒVܒVto2ܒVchangesizefieldforreservedfrom4to10ܒVܒVbbBDFcg bA bcAgcAgEbA g b@bEb@!cA"g!#b$g#%bA&%&c*(cA,++bA/g..c9binsertmihcapabilitypage54line141VinsertnewlinkidentifierbetweenhandovermodeandoldlinkidegVinsertorcouldbemaintainedinaninternaldatabasebytheVinserttable24extendedschemacontenttlvformatݿVinsertthesuppotedisquerytypelpage83line1Vinserted(W,WinstanceZW8WsWWWWinstances*WuWinstantWinstantiationW4W5WWWinsteadۗWWW"W/W݃WWWW-WlWWinsteadofprefixconsidertheuseofnetworkmask-Vinstructs>Winsufficient)Winsufficientinformationofintenttosuggestanychange)VintegerwWyWWWWentinformationofintenttosuggestanychangeVVVVtosuggestanychangeVVVVVVVVVVVVVVVVVVkWlWmWnWpWsWuWvWwWxWۂWۇWېW۝W۶W۹WWWWWWWWWt bA6.2.5.1 MIH Commands The following set of MIH Commands are defined. Table 4-MIH Commands --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | No | MIH Command | (L)ocal, (R)emote | Remote DirecBtion | Description --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 1 | MIH Get Status | L, R | Network -> Client | Get the status of links -----------------------------------------------------------------------}@cneeds WAWGWIWJWsWtWۉWWW-W;WYWkWܥWWݒWWWOWހWށWނWރWkWlWmWWWWW?WiWWWWnegotiated|Wnegotiation\W\W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8WW۽WWWWWWW W W WW-W:W;W<W=W>W?W@WIW܋WܝWܡWܤWܩWܬWܭWܴWܶWܻWܼWܾWWWWWWW+W2W3W:W;WSW_WuW݂W݊WݏWݐWݨWݩWݺWWWWWW WW!W"W#W$W%W+W/W\iEDasFSubir ^ Editorial_1`50a1.2bAdd correct reference cCReference [1] is not correct. Also reference numbers are missing. d5g2411{k) done 2006/09/21EDasFSubir^Technical, Binding_2`33a1.2b/Delete the "an information repository" part. c1MIIS is not defining "an information repository" d12g2412i Vivek Guptaj The notion of "Information repository " is correct ..... May want to change the word "provides" to "specifies" in this paragraph.mRejectedwAccepted{k) done 2006/09/21EDasFSubir^Technical, Binding_3`60a1.3bCReplace "performance of access networks" with " access networks" networks" networks" is correct ..... May want to change the word "provides" to "specifies" in this paragraph.mRejectedwAccepted{k) done 2006/08/28EDasFSubir^Technical, Binding_3`60a1.3bCReplace "performance of access networks" with " access networks" Rejected 2006/08/0320   @WbA*  33\  *bility and implementation compliance shall be specified based on the set of mandatory and optional features in the specification." However, no such definitions have been defined in the document. @A>  33   33>pۇÃ܆Ã8ÃÃ9à *Ã0Ã@܇ÃP>Ã`qÃpÃÃޏÃÃބà ޅÃ0Ã@ÃPrÃ`OÃpPÃ+ÃQÃۏÃà ކÃ0-Ã@ÃPޗÃ`ÃpސÃÃޑÃÃޒà ܈Ã0܉Ã@܊ÃP܋Ã`sÃp܌ÃÃޓÃRÃܚà ܍Ã0ۀÃ@tÃPÃ`uÃpÃvÃoÃہÃމà wÃ0ۉÃ@8ÃP9Ã`:Ãp;Ã<Ã=Ã>Ã?à @Ã0AÃ@BÃPCÃ`D dDT Abyc802.21*WۀWۅW۩WW$WCWDWEWHWRWTWUWVWWWYWmWܛWܣWܧWWWWW݅W݉WYW>W\W]W^W_W`WaWbWcWdWeWfWgWhWiWkWWWWWWWWW W!W<WkWtWWWWWW W WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWZ[FAthalyeGMember^ Editorial_110`42a8.1bRemove "As such".cSuperfluous phrased685{k) done 2006/09/21 ESanjeevFAthalyeGMember^ Editorial_112`5a8.3bCorrect "rregister".cSpellingd699{k) done 2006/09/21 ESanjeevFAthalyeGMember^ Editorial_115`60-61a8.3.3.2bRemove "is embedded".cSuperfluous words.d750psuperceded by 746{l) none needed 2006/09/21MarkedMarkedMarkedESanjeevFAthalyeGMember^ Editorial_118`5a8.4b "definite"cSpellingd762{k) done 2006/08/29 ESanjeevFAthalyeGMember^ Editorial_119`18a8.4.1.2b"command code"cMissing space between words.d779{k) done 2006/08/29 ESanjeevFAthalyeGMember^ Editorial_122`40a8.4.2.2bCapitalize "Management"c Customary used789{k) done 2006/08/29 ESanjeevFAthalyeGMember^ Editorial_123`12a8.4.2.3bARemove square brackets here and 3 additional places on this page.Dd ܫb>MarkedܬEVivekFGuptaGMember^Technical, Binding_22`2a5.4.3bAMRemove the following lines: "The capability of such network information service can be obtained via schema access. The structure and definition of schema can be represented in a high level language such as XML" Lines 27 and 28 on page 22 define adequately methods of information access and hence the above two lines re not required.McA^The information can be obtianed either by TLV or schema. However the following lines on page 22, gve the notion that information can be ontained using schema only. "The capability of such network information service can be obtained via schema access. The structure and definition of schema can be represented in a high level language such as XML" , ^d157g3225i Qiaobing XiemAcceptedvAdd " The capability of such network information service can be obtained via schema access. " later on in the page (lines 27/28)wAccepted-Modified{k) done  vPlease refer to comment 259 Change Upper layers to MIHF Users. Call one Local Entity and other Remote Entity... General Note to Editor: Replace all Upper Layers by MIHF Users wherever applicable Replace Local/Remote Stack by Local Entity/Remote EntitywAccepted-Modified{a) awaiting resolution 2006/09/21 2006/04/2814EDasFSubri ^Technical, Binding_36`30a6.1.4b8Accept the contribution 21-06-0624-00-00_figuer15.ppt. c?Figure 15 is incomplete. Local events are not shown properly. d269g2441i Vivek Guptak_This makes the figure vey confusing. Maybe use two separtae figures for remote and local cases.mRejectedvby comment 482w Superceded{a) awaiting resolution 2006/09/2115E Ulises Olvera^Technical, Binding_37a7.2.2.1b^Should be included in Table 3 since they fall under MIH Events Should be included in Table 2c Table 2c Table 2c06/09/18 2006/04/28MarkedE Ulises Olvera^Technical, Binding o%cisWWWWWWWWWWWWWIH Function that sent out a MIH_Network_Address_Infomration.request. The primitive is used to communicate the response of MIH_Network_Address_Information.request. The response may be sent either by the new PoA or the network entity, e.g, Access Router or Foreign Agent, depending on where the related information is available.ijkmnpvw{ 2006/05/146/04/28 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 bobtained#WܬWWWWobtainingAW}WxWzWobtains)WocalWoccupiedݗWoccupieszW{WWދWތWތWތWތWތWތWތWތWތWތWތWތWތWތWތWWWWW W!W#W,W-W.W?WAWFWGWHWIWJWLWMWPWQWSWTWVWWWZW[W\W]W_W`WbWcWdWfWiWjWkWlWmWnWpWsWuWvWwWxWۂWۅWۆWۇWۉWېWەWۖWۗWۘWۚW۞W۠WۦWۧW۪W۬W۳W۴W۶W۸WۻW۽W۾WWWWWWWWWWWWWWWWWWWW/W2W3W4W5W:W<W=W@WFWHWJWKWLWQWRWSWTWUWVWWWXW\W_W`WcWdWhWiWjWkWlWmWqWsWvWwWGbtechspecificparameteGWlWtelecommunicationۖWWtelecommunicationspWtellWtermۢWW-WWterminalۘWۜWterminatedHWterminology۽WWWtermsWWWWWWWWWWWWWWWWWWWvWxWWthatW W,W-W.W?WAWHWIWLWMWRWTWWW\W_WdWfWjWmWۉWېWەWtheWW W!W"W#W$W%W&W'W*W,W-W.W6W7W8W9W?WAWDWFWGWJWNWOWPWQWRWSWTWUWVWWWXWYWZW\W]W_W`WbWcWdWeWfWhWiWjWkWlWmWnWpWsWuWvWwWxWzW{W}WWۂWۃWۄWۅWۆWۇWۈWېWۑWۓWەWۘWۚWthecreationthereinofanewentitytoanewentitycreatedHsrinivas[\]_adkᓃᔃᕃᖃᗃᘃᙃᚃᛃstewartYᐃᑃtakashiۓulisesWWWWWWWWWWWWWWWWWWWWWWWWWjWkWlWmWWWWWWWWVVVVVVVVvivekܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃwolfgangܑܒܓܔܕܖܗܘܙܚyanۇWۈWyanpengjunxiangguoۇVۈVyoshihiro݆݈݅݇݉݊݋݌ݍݎݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟݠݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σyuanۅۆ 9 }bc=Description of RDF_DATA under InforqueryType is not corrcet. d672g2424wAccepted{k) done 2006/09/21 ~EKenichiFTaniuchi^Technical, Binding_108`38a 7.4.15.3.2bAMIH_Information.request (RDF_DATA, "PREFIX mihbasic: SELECT ?poa-address poa_address WHERE {?x1 mihbasic:neighboring-poa ?x2 . ?x2 mihbasic:link-type 19 . ?x2 mihbasic:poa-address ?poa-address x3 . ?x3 mihbasic:address ?poa_address . ?x1 mihbasic:poa-address ?x3 x4 . ?x3 x4 mihbasic:address "001122334455" }") MIH_Information.response(RDF_DATA, "  33  33 33>cANetwork Selection is the process by which a mobile node or a network entity collects policy information on its neighboring networks and selects a link (possibly out of many available) to establish network-layer connectivity@A> 33  33 33>d94g3248palso made the same fix in P9-L6{k) done 2006/09/21 ܣEVivekFGuptaGMember^ Editorial_14`31a5.1.7bReplace "This.." by "The"c"This 802.21 Standard..."d97g3222{k) done 2006/09/21 ܤEVivekFGuptaGMember^ Editorial_15a5.2b15a5.2b15a5.2bDbreplacetimeintervalinwhichthelinkisexpectedtogodo]VreplacevaluesraeassignedwithvaluesareassignedxVreplacevariablewith0VreplacewhichsttausmaywithwhichstatusmayVreplacewhirewithwherepVreplacewithcs0004-dۡVreplacewithvalidlocalorremoteidentifierVreplaced.WAWBWWWWWreplca^Wreplcawhenapredictiveevenexpectedtooccurwithwhena^Vreponse8WreportTW|WވWtWWreportedQWsWreportsAWtWWW>W>W>WedQWWreportsAW_WܽWܿW݊W݊WWܽWܿW݊W݊W_WܽWܿW݊W݊WreportedQWWreportsAW_WܽWܿW݊W݊WreportedQWWreportsAW_WܽWܿW݊W݊W݊W݊WWWWWWWWWWWWWWWWWWWWWW|WݔWݕW޿WWVbsap*WCWDWpWۤWWWW2W4W5W8WlW2W>W[W%WuWWWWWWWWsapsDWpWWWW2W[WWsatelliteۖWWsaved&WsayWWWsWWsaytheabovementionedframestructureVsaying۳W)WWWscanNWmWWWscancommandmWscanrequestinfomWscenarioݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWW!W'W1W2W3W4W6W7W8W9W<WBWCWEWYW]WaWbWpWۄWWWWW;WAWBWRWSWYWcWhW܁W܂WܕWܗWܘWܙWܛWܩWܪWܶWܷWWWWW{W݂W݄W݌WEXiaoyuFLiuGMember^Technical, Non-binding_101`60a7.4.13.1b)Add "MIHF(Mobile Node) <> MIH " cMIH Handover Complete should be available between MIHF (client) <> MIHF (Network). The description of 7.4.13 should be consistent with Table 4.d913g2220vby comment 495w Superceded 2006/09/21 2006-04-30EXiaoyuFLiuGMember^Technical, Non-binding_102`57a7.4.13.2b)Add "MIHF(Mobile Node) <> MIH " cMIH Handover Complete should be available between MIHF (client) <> MIHF (Network). The description of 7.4.13 should be consistent with Table 4.d914g2221vby comment 495w Superceded 2006/09/21 2006-04-30EXiaoyuFLiuGMember^Technical, Non-binding_142`1aAnnex Ab\See the suggested Annex A-2 in the proposal: 21-06-0656-00-0000-WLAN_WMAN_HO_Procedures.doc cTAdd a section for the example handover scenarios between 802.11 and 802.16 networks.d915g2222915g2222915g2222{ C\vARefer to contribution 21-06-0677-00-0000-Hnadover_Flow What happens to MIH_Handover_Prepare? These commands are still vague. The sequence of operation with these commands needs to be clearly described. Update figure 30 as well(Ulises) Refer to commands in table and show which are useful and which are not. How a command should behave? Final Resolution: Sept 2006 Keep these commands in draft and clarify their operation as per contribution 21-06-0677-07-0000-MIH_Handover_Procedures EditorialB comments to to updtae figure (line format etc.) and change the color of text. Classify the figure/diagrams (Fig 1 and 2) as Examples and move them to Annex Use separtae naming for MIH_Handover_Complete primitive between MN and Pos and between two PoSs. wAccepted-Modified 2006/09/21 2006/04/24144ibed. Update figure 30 as well(Ulises) Refer to commands in table and show which are useful and which are not. How a command should behave? PwDeferredUpmatchWmayۓWW݃Wmentioning WWmichael۴Wmies WmihgWۅW۪W2WܥW}W݃Wmih-3glink-sap۽WmihfܥW݃WmismatchedWmismatchingWmismatchingsection/page/linedon'tknowwheretochangeVmissing WݒWmobile.Wmodel۴WmoreWmoveܾWlWmovelinkdetectedtoalignwith7.3lVmoved;WmultihopݓWnada;WnamegWname/description/etcݜWnasۓWneed۴WWܵWWWWzW}W݃W>W@WBWCW2WneedhelptocreatenewdrawingszVneedhelptoredrawfigܵVneedhelptoredrawthefig۴VneedhelptoredrawvisioVneednewdrawingsBVCVneedsomeonetoprovidethecorrectversionsVneedtochangeaaatomihreginthefig}Vneedtoredrawfig@V2Vneedwordpicnewfigure>VneededܰWWVreplacingWright۽WsameۖWܡWeparametersރV14 .E Famolari FDavid^ Editorial_8`21a3cTwo definitions of the same term "Mobile Node". Also, the latter definition of mobile node is not clear since it says "The mobile node may either be in close proximity of or coincide with the mobile node.d58g2403- Line 55. the circle point left to "MIP binding to HA" should be shifted to the left. - Line 56. Does the AP get Link Tear Down or Handover complete indications before it is disassociated? d872g2399predrawvcNot all issues have remedies. Assigned on Issue List. Change: - "PSDN/FA" should read "PDSN/FA". wAccepted-Modified{i) to do 2006/08/27Marked Figure 30 .E Famolari FDavid^ Editorial_8`21a3cTwo definitions of the same term "Mobile Node". Also, the latter definition of mobile node is not clear since it says "The mobile node may either be in close proximity of or coincide with the mobile node.d58g2403bkresponse|WWWWWresultgWWWretrievalwWxWyWzW{W~WWWWWWWretrievedWretrivewWxWyWzW{W~WWWWWWretriveduWreviseWrfcWrfc4889WrightWroutingVWsameWWOWsameascomment626OVsapvWWWWWsapsWWDW3WDWDWDWDWWDWDW3WDWDWDWWDWDWWDWDW3WDWDW3WDWDWDWDWDWWDWDWWDWDW3W6WDWDWDW3W6WDWDWDWWDWDWWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWDWWseveral#W\WܬWshouldYW\WCWܻWW-WshowsZWsimilarAWbWsimilartocomment444doesthisnotmeanweneedsemanticqbV}vKby comment 495. Update as per resolution of Handover commands and resubmit.w Superceded 2006/09/21 2006-04-30MarkedEVivekFGuptaGMember^Technical, Binding_8`22a3b!Clarify definition of Mobile NodecAMobile Node - Network node that may change its point of attachment from one link to another at any time. The mobile node may either be in close proximity of or coincide with the mobile node.@AR  33i  33  33  33Rd62g3244{a) awaiting resolution 2006/08/29EVivekFGuptaGMember^Technical, Binding_8`29a3b)Remove second instance of definiton of MNcMultiple definitions of MNd66g3245{a) awaiting resolution 2006/08/29EDavidFHuoGMember^Technical, Binding_23a5.5b Replace Fig 4c+Replace Fig 4 by the submitted contributiond180g3262y0Group needs the submission number in the comment{a) awaiting resolution 2006/08/29vnotallissueshaveremediesassignedonissuelist-VnotclearfromwhichprimitivesthedestinationidentifiernVnotclearwhatsentenceisbeingtalkedabouthere VnotconsideredrelevanttoschedulednetworksegmentssuchaVnotsureifthisisreallyrequiredVnoteWWWWnotedWnothingށWnotificationQWRWSWTWWnotificationsWnotifyWnotionWnovemberWnowWThe use of the term "MIH proxy" should be avoided.d114g2391 2006/05/14-EDavid FFamolari^Technical, Non-binding_140`1a Annex A-1cdescribed in section 6, in a 6.4 subsection. 2006/05/1418,EDavid FFamolari^Technical, Binding_16`44a5.3.1bMember^Technical, Binding_114`63a8.3.3.1b;Remove "ACK-Rsp bit" and change "Reserved" field to 5 bits.cA4The justification for "ACK-Rsp" bit is insufficient.4@A  33d739 hcATwo MIH Commands has similar functions: MIH Switch and MIH Handover Commit. We need clear definition for these two commands to minimize the potential confusion. MIH Switch: this command may be use to control the behavior of link layer and start L2 connection establishment, i.e., L2 preparation MIH Handover Commit: It may be use to start the excution of handover. The difference between these two commands may be illustrated in the example flow charts in the proposal: 21-06-0xxx-00-0000-WBLAN_WMAN_HO_Procedures.doc  d911g2218vby comment 609w Superceded 2006/09/21 2006-04-30EXiaoyuFLiuGMember^Technical, Non-binding_100`65a7.4.12bQChange "MIHF(Network) <> MIH " to "MIHF(Network) <> MIH " cMIH Handover Commit should be available between MIHF (client) <> MIHF (Network). The description of 7.4.12 should be consistent with Table 4.d912g2219vby comment 495w Superceded 2006/08/29 2006-04-30W~bthenGWTWZWeW7WݎWݗWlWsWtWvWWW'W>WWthereAWUWZWxWTWUWVWWWYWW WCWsWWWWWtherearetwopossibleremediesforthisYVtherearetwopotentialremediesVtherewillbenodirectcommunicationbetweenthe3gpp2phy VthereafterW|Wtherefore,WthereinۚWthese WpWۻWW#W7WܾW(WWW-WކWWWWWWWthesecapabilitiesneedtobespecifiedclearlyfordifferenܾVtheserecommendationsshouldbehandledbyspecificieee802VVVVVWWWWWWWWWWWWWWWWWWWWWW802VtheyWW-WAWW7WW݂W݃WWWޜWޝWޫW޿WWWWW W WW.W<W=WKW_W6cofWWWWWWWWWWWWWWWWWWWWWWWWWW"W"W"W"W"W"W"W"W"W"W"W"W"WTbreplaceۋWۛW۟WۡWۢWWW WW#W5W6W8W:W<WCWGHWNWTWUWVWWWZW]W_WaWfWilWoWpWrWtWvWwWxWyWzW{W}W~WW܀W܃W܄W܆W܇W܈W܊W܋W܌WܡWܣWܥWܧWW!W-WqWsWW݃WWW/W>WNW]WvWކWއW6W=WWWWWWWWWWWWWW#W=WZWgWhWqWvWwWxWyWWWWreplace1.2with1.3inthenocolumnVreplace1.3with1.4inthenocolumnVreplace3127reservedwith3127reserved}Vreplace3gppwith3gpp2sVreplaceadditionalidentifiersarepresentthathelptoanaltVtVaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1VG5EJinFLeeGMember^Technical, Non-binding_85`29a7.4.4.1b2bOLink Type is not necessary to put here if the proposed general mechanism works.ormation 4) Higher Layer Services cLine 14 says 'IE are classified into three groups', however, it seems that there are 5 groups in Table 6. The classification in page 44, the groups in Table 6 and the groups of TLV formats in Section 6.3.4 should be consistent. d906g2212vby comment 352, 360w Superceded 2006/08/21 2006-04-306EXiaoyuFLiuGMember^Technical, Non-binding_56`29a6.3.6.2bOLink Type is not necessary to put here if the proposed general mechanism works.hnical, Non-binding_56`29a6.3.6.2bOLink Type is not necessary to put here if the proposed general mechanism works.s.s.d907 2006-04-30*{cIn order for mobile node's MIH Function entity to commence MIH Protocol procedures, MIH Function entity of mobile node shall discover its peer remote MIH Function entities. This procedure is not cleary described in the current draft. .d250g2211pA- only added new 6.4 and subsections - did NOT make section 8 changes - did NOT try to answer the open questions in group decision [Vivek] Contribution 0611 was updated by Ronny with some of these changes sa well. You could update changes for Section 8 and we can capture open questions as issues. [Editor] - did not make the changes in 8.3. The mark-up is not based on D01.00 text. - made other changes to section 8. - made 8.3 changesv23 2006-04-30Marked22{ERonnyFKimGMember^Technical, Binding_33`1a6.1bYAccept text changes in the contribution "21-06-0611-00-0000-MIH protocol section update".m Eunah in June Ad Hoc.wAccepted{i) to do 2006/08/21 2006-04-30Marked22]MPENada, Golmie, Member^ Editorial_64`55bRemove "in the .21 draft"cfThe Description field refers to primitives defined "in the .21 draft", which is the currrent document.d489g2268{k) done 2006/09/21QENada, Golmie, Member^ Editorial_68`53b5Remove the word "request" at the end of the sentence.  33U  33`  33  33  33fcpThe descriptions of items 3 and 4 are identical. The primitive M_ScanScheduling is relative to scan information.d488g2265i Ronny KimmAccepted{a) awaiting resolution 2006/09/15PENada, Golmie, Member^ Editorial_64`55bRemove "in the .21 draft"cfThe Description field refers to primitives defined "in the .21 draft", which is the currrent document.d489g2268{k) done 2006/09/15QENada, Golmie, Member^ Editorial_68`53b5Remove the word "request" at the end of the sentence. sentence. sentence. 4 ]^technicalbindingܖVܖVܕVܕVܕV_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g2349 2006/05/14 2006/04/28ݤE YoshihiroFOhbaGMember^Technical, Binding_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g23498ݤE YoshihiroFOhbaGMember^Technical, Binding_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g23498ݤE YoshihiroFOhbaGMember^Technical, Binding_80`59a7.3.17.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d561g2349Identifer TLV.d561g2349LcclientsWclose.W3WWclphrasing?Wclubbed݅Wcn۽Wco-locatedWWcoaWcodeۅW{WތWWWcodesWWcoherent3WoWcoincide.W3WWcollectܤWݐWcollectsܡWcolummގWcolumnWWWWWށWރWcolumnintablesection8.4.2.24needstobemodifiedރVcombinationWcombineWcombinedWWcomeWWW9W9W9W9W9W9W9W9We9W9WnationWcombineWcombinedsWWcome9W9Wf`Ä23ЃnÄ29ۦÄ2R.Ä37۳Ä45ۚÄ4eÄ78*,Ä9CÄDEÄIZ'ÄIZSÄJREÄRV۝ÄSrÄWXÄbgÄdeۻÄfhÄgjVÄijۧÄqrĆEGUGa1.1ە1.2ۖۗۘۙۚۛۜ۝Ƀ 1.3۞!"#1.5۟1.6ܛ%2۠ۡʃ$&'3ۣۢۤۥۦۧۨ ./1ܜܝܞܟ()*+,-.3.1+W40ܚWܠ5.1۩5.1.3n5.1.5ܡ5.1.6ܢ/5.1.7ܣ5.2 ۪ܤܥܦܧܱ015.3ۭܨ35.3.1۫۬ۮۯ۰,ܩܪ˃24565.3.2!۱۲۳۴̃789:5.4"=5.4.1.1۵ܫ5.4.3#۶۷۸۹ۺۻܬܭ̓;<>?@5.5$ۼܮ΃AB5.5.35.5.4۽۾C5.5.5ۿσDEF5.6ЃGB"EQiaobingFXieGMember^Technical, Binding_20`3a5.4bA...... across heterogeneous network interfaces. Upper layers may utilize services provided by the MIH Function across different entities to query and reserve resources required for a handover operation between heterogeneous networks. @A>  0  TT  33>cAUsing MIHF "to query and reserve resources required for a handover operation between heterogeneous networks" is out of scope for MIHF. Handover resource management belongs to the upper layer mobility management application/protocol itself.@A  33d145g2242i Vivek Guptajs may utilize services provided by the MIH Function across different entities to query and reserve resources required for a handover operation between heterogeneous networks. @A>  0  TT  33>c]^_B`jrelationships,WremedyWremoteWWremoveduWremovinggWWWWgWremove WremovedaWremoving<WjWrenewalݍWreplaceWWreplacethelastmihgetinforesponsebyaconfirmprimitivVrepresent|WrepresentationWW,WrequestW>Wrequests>Wrequire WresXWresponseWW>WrestrictWrfc?Wroles>Wsame0W>Wsamecommentascomment170Vsap W1W3W>WsapsWschemaBWse,Wsection<WaWuW+WݻW+W>WjWsee@W+Wseecomment315andchangefigureaccordingtoit@Vseems>Wselected?WsendKWsense+WseparationKWserviceBW>WsessionWWhWset۬W+W|W Wshall+Wshould?WuW۬WW WݴWTWhWshouldbediscussedcarefullyݴVshouldthemihusersknowaboutthesessionidhVAbitselfSW|W>Witu-tvWityAWjWjissuedVjhallHWjustWWZWܧWsWWWkWktowardsVkeepWkeptWkeyܨWWWkind݃Wknow6WknowledgeWknown6W܋WWlWWltowardsVl-shaped,W,W,W,W,W,W,W,W,W,W,W,W,W,W,W,WWlanguage#WkWnWܬWlargeWlastܶWlat/lonSWlaternWܪWWlay݂Wlayer#WAWHWIWLWMWOWUWVWWWcWdWpWېWەWۣWWWWW/W7WSWTWZW\WcWeWfWiWkWܤWܫWܳWCWDWݍWlayerare1Wlayered/WlayermihcWlayers"W*WAWOWPWQWRWSWTWUWpWwWۉW۵WW6WNWiWkWܢWWyWݍWݎWlayers/mihf۵WlearnېWlearned۶WgCcbeforeeWېW-W W"WpWtWvWWW?WiWbeforeauthenticatingwiththepoathemihfunctioninthemVbehaviorZWiWkWWbehaviourWbeingWWbelongtWuWbelongs"W\W]W^W_W`WaWbWcWdWeWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW2WJWSWiW݉WW WW4W5W7W>WTWޠWޣWޤWޥWWWWWWWWWW,cedge:WWeffectWoWeffective?Weffects8WefficiencyWefficient WWeither.W3W[WܬW3W"W$W%WޖWWWW"WWelaboratedWelementHW܄WܕWW/W1WoWWWW9W9WW1W1W1W1W1W1W1W1W1W1W1W1WntsKWZW]W_WW@WCWܘWܺWWWWWiWߧWW#Welse2W:WWelsewhereܛW~W.WAWelsewhereinthedocument.VembeddedtWݸWWenable݂WenablesۋWencapsulatedWޏWencapsulatedrouteradvertisementisencapsulatedޏVencodeےWencodedJWWW7WhWߦWW"WencodingJWGWWXWWWW7WhWߦWW"WencodingsWWend-to-endWengineWݎWenglishjWkWmWnWoWzW{W|W}W~WہW*breplaceshalldefinewithdefines۟VreplacespecifictiewithspecifictoieaVreplacestatusofhnadoverrequestwithstatusofhandoverr܀Vreplacethe802.21informationelementsmaybeassignedidenCVreplacethealinkeventrollbackwithalinkeventrollback܃Vcethealinkeventrollbackwithalinkeventrollback܃V܃Vcethealinkeventrollbackwithalinkeventrollback܃V܃Vcethealinkeventrollbackwithalinkeventrollback܃V܃VrregisterٔWWrttQWTWrtx6WrulesZW[W^W_WcWWrxlevncell2W3W4W5WsWW;W<W=W>W?W@WAWBWCWpWڍWWWs0001pWs0004-dTWs0024pWs0024-aqWs0063-aqWsame+W-WڔWWWWsamechangeisneededatthetableofcontentsandp72/l62VsapWW/W0WWWuWWWڎWsapsW0WiWsatelliteIWeWk {vAThe language is too strong in some cases. May need to change some "shalls" to "may". Link layer may NOT regster by itself with MIH Functon in 6.4.1. MIH capabilities may be discovered by MN and or the Network (not just MN alone in 6.4.3) What happens when any of the specified services are not available or fail for one reason or another? Clarify operational characteristics. These services are invoked during sytsem startup, during link switching etc.wAccepted-Modified{k) done 2006/09/21 2030/04/06en questions as issues. [Editor] - did not make the changes in 8.3. The mark-up is not based on D01.00 text. - made other changes to section 8.v%vspecifythesevaluessecuriyandqosinthecontextofaccesܾVspecifyingJWspellingWsprecifyގWsprecifyabortreasonfromsection7.4.10.2.2ގVstackWWstacksWstageWh as Security and QoS are on a per PoA basis or are common for a specific access network managed by a particular operator. cATYPE_IE_POA_CAPABILITIES: The Security and QoS capabilities of the PoA need to be interpreted in context of Security and QoS capabilities of specific access network as specified by TYPE_IE_NETWORK_SECURITY and TYPE_IE_NETWORK_QOS: This aspecis not very cleard436g3237i Hong Chengja particular operator. cATYPE_IE_POA_CAPABILITIES: The Security and QoS capabilities of the PoA need to be interpreted in context of Security and QoS capabilities of specific access network as specified by TYPE_IE_NETWORK_SECURITY and TYPE_IE_NETWORK_QOS: This aspecis not very cleard436g3237i Hong Chengj33d252OhopsameatpreviouscommentۖVsametablecopiedto8.5.1.1\Vsap2Wsaps2WscenarioݓWݓW:WRW{WݜWkWvWsection/page/lineWsectionsېWseeSWEWsee195editor'snotesEVseecomment490SVseem۽WseemsWWsensekWsentence۪W.W݃WseparateDWserverݒWݓWshouldۓWWYWshouldbetechnicalVside݃WsipލWsomeۅWWܥWsomeone&WWsource/destLWMWspec݃WspecificܾWݛWsplitܾWstatus܁WstronglyWsubmitݜWsubsections{WsuchۅWsuperceded?W^W`WWIWhWWYW6supercededby345^V`VIVsupercededby615hVsupercededby746VVsupercededbyanearliercomment?Vsure۽WܥWtableDWhWیWۓW۽WRWW\Wtableexplainedbycomment621hVtable-6)WtbdݛWtechݛWtechnicalWW~Gbinformation#W?WAWZWcWdWeWfWiWlWpWxWۘW۳W۶WWWWWW#W5WCWHWNWmWܕWܟWܡWܤWܬWWW,WPWzW}WݖWݘWWWWWWWW"W#W$W%W'WpW~WބWޅWއWfWhWoWsWtWvW|WWWWWWWWWWWWWWWWWWWWW"W(W)W+W,W8W>WsWuWWWWWWWWinformationusingtlvswithawelldefinedbehaviourpatternVinformationalXWWWinformationlist|W|WVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVabled!Wmobile,Wmobility,Wmodel$Wmove!Wmulti-technology!W%HbbebeexchangedinordertoachieveisserviceVbeareoWXWXWW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9Wƒkenichi taniuchiƒkenichi Xtaniuchiƒkenichi Ztaniuchiƒtaniuchi&ƒkenichi taniuchiƒpark soohongƒsoohongƒpark soohong DTDT_DT`DTZx{k9W<W?W@WAWEWGWHWKWLWMWNWOWPWQW^WeWfWgWiWjWkWlWmWnWpWqWrWsWwWzW{W}WW݃W݅W݆W݇W݉W݋W݌WݍWݎWݐWݑWݒWݓWݔWݕWݖWݗWݘWݚWݛWݜWݭWݲWݵWݸWݹWݺWݽWݾWݿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWW W"W#W$W%W&W'W(W)W*W,W-W.W/W2W4W5W8W:W>WAWBWIWLWMWNWOWVW[W\W]W_W_W_WގWޖW1W5WkdoneVVV V"V(V)V*V+VDVGVIVLVcinter-technology?W@WWinteract"W$WWinteractionWinteractionsWinterafces۴WinterchangeWinterchangebelowsectionsVinterchangedWinterestIWWWWWWinterfaceۉW۽WWW:WkWW4W5WޖW5WWWWW%WWWWWinterfacesۉW۴W!W0WWWWW#WinterfacingWinterferfacesWintermediaݐWintermediateWinternationally>WinternetW!W(W,Winternet-draftݕWݖWݘWinteroperabilityCWHWRWTWUWVWWWYWܛWW WinteroperableWinteroperateWWWےWےWperateۑWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWےWitself"WwWjapanesejWkWmWnWoWzW{W|W}W~WہWWfCbdetailsۅW݃WWWWWW9WWW WWWWWWWSWWRWSWTWUWVWWWXWݛWWqW߯WdetectionVWXW Wdetermine#W݂Wdetermined WޖWdeterminesW\WdeterminingWdeveloped_WdeviceۜWWܫWܶWdevicetoreconfigureandpresentdatatoupperlayersVdevices_Wdhcp\Wdhcpv6WdiagramۿWܳWW>Wdiagram/textWdiagrams/useܴWdicoveryuWdifferences*WިWWWHW߆Wdifferent W"W?WAWMWOWPWQWTWUW_WpWuWۙWrWܤWܳWܴWܾWܿWW0WQW݃WWWWPWޅWޞWޠW޽W޿WWWWWWWWWWW WW,W.W>W@W]W_WkWmWnWoWrWsW|W~WߛWߝWߩW߫W߬W߭W߰W߱WWklines#W۴WlinkdWWWWWWWlistpWlistedWlocalWlocally۳WlocatedWlower\WWlowrWlsapWmac WmacnewpoadWmadeWmaintainWmaintainingWmakeWWWmakethefiguremoreconfusingmaybeusetwosepartaefigureVmakesWmakingWmanagedWmanagement\WmandateOWmandatory۴WWWmanditorilyWmannerWmanyrWvWmapWWWmappingWmatchWmayAWW\WWWWWW}W~WWWmayneedtoconsiderthistextinlightofothercommentsmeVmaybeWWWmaybeweshouldmodifyfigure12andshowmihlinksapandcVVVVVVVthodsWmihuW۾WWOWWW+W6WOWmihfunctioninthenetworkmayadvertiseitsmihcapability+V5 (GEFarrokhFKhatibiGMember^ Editorial_29` 34, 36, 44a5.6b$Remove dash in "mobility-management"cNot customary use.d211{k) done 2006/09/21HEFarrokhFKhatibiGMember^Technical, Binding_30`62a5.6.1.4badd /3GPP2 after 3GPP.c03GPP2 should be mention in this section as well.d225wAccepted{k) done 2006/09/21IEFarrokhFKhatibiGMember^Technical (was Editorial)_33`33a6.1.1b"This could be due to user or mobile node mobility, state change in the environment or because of some management function on part of the network." needs to be exapnded to include other reasons that may trigger HO.cLimited scope of HOd253v=No remedy suggested. Also superceded by previous comment #252wRejected{a) awaiting resolution 2006/09/21dMember^ Editorial_40`65a6.2.3b8Rename the figure caption to Remote Command Service Flowc8Rename the figure caption to Remote Command Service Flowd297{k) done 2006/09/18hatibi2cresource"W0W܇WwWwWxWyWzW{W~WWWWWWW|WWresources"WW WWWrespectingWrespectivelWWrespectively7WWrespond܆Wrespone{W#WresponseeWۃWۄWۍWېW܂W܄WܕWWW%W>WCWކW=W?WWWWWWWWWWIW}WWWWWWWWresponsesܕWWWresponsible WrestatingQWrestatingtheobviousQVrestricted۪WܕWrestrictive۶WrestructureݐWrestructurethefollowingsentenceݐVresubmitWresubmitofcomment138fromthedenvermeetingVresultۄWېWQWlW܆W0W>WresultcodeۄWۄWۄW>W>W>W>W>W>W>WHWsaying/WsaysWrW۾W%W&W.WZWscanۆWWNWscanschedulingNWscenarios\WۈW|bmustWWDWZWRWTWUWVWWWOWނWބWWW[WsWtWWW3WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWprotocolstack/Vn-th/Wn-user5WܟWn/aFWGWjWmWۂWkWmWܖWWWWW3W4WdWeWn0WnameۂWۉWېW=W\WkWmW܁W܂W܄WzW|WݕWW<W?W~WޕWnametype܄VnametypevalidrangedescriptionۂVnamesܷWnamespaceݕWnasWnasiscommonlycalledasnetworkaccessserverVnas-port-type=WݔWtWnativeVWWWWWtWuWnature WޞWW W>W|Wnbr-advNWnearbyWnecessaryAWVWۓWW2WW݂WW޿WWW.W_WtW1rb1.0~W1.1tWW1.1typeielistlistofneighboringforexampleradiusnas-tV1.2WWW1.3WWW1.4W1.6ܛW10kWܒWWW1006W1016W11pWW112W12=W125hW127}WݗWWW128WW+W13>WW147W܄W/WݛWlW1W\WfWWW14bitidV15ۉWݛWlWWW16WkWlW16WWWWWWWWWWWWWWWW16EWWWWWWWWWWWWWWWWWWWWWWWWWWWkWmWnWuW{W}WۉWەWWW&W(W=WHWRWSWYW\W|WܒWܖWܯWܴWWyWzW݃WݗWݶWW W,W>WPW^WpWvW}WށWރWޕWޘWޟWWWWWW[%cbe:W>WCWNWOWOWOWPWPWQWQWconsistency.@A  33cH@AR  33  4  <  33RcANA better title for 5.5 would be: "MIH Reference Model for Access Technologies"N@A  33d177g2244 2006/05/14 2006/04/24%EQiaobingFXieGMember^ Editorial_30`36a5.6.1bAfix the inconsistency.@A  33c  4  <  33RcANA better title for 5.5 would be: "MIH Reference Model for Access Technologies"N@A  33d177g2244 2006/05/14 2006/04/24%EQiaobingFXieGMember^ Editorial_30`36a5.6.1bAfix the inconsistency.@A  33c  TT>c_ctexts>WthanWWWWW WW%W+WlWWWWWWܴWWWW WDWXWWWWܗWܩWܴWWWW WDWXWWW WDWXWWWWWWWWWWWWWWWnformationprimitivei:V;V<V=V>Vtheneedforsection5.3.2isnotclear!Vthesectiontitlemediadependenceisconfusinganddoesnot)Vthesectiontitlemediaindependenceisconfusinganddoesn(VthereWW-W?W@WtherearetwomobilenodedefinitionsVVthereisnoneedtodefinenewtermshorizontalhandoverand?V@Vtherefore+Wthese/W0W5Wthis#W'W*W+W1W2W3W4W6W7W8W9WAWthisiscriticallyimportanttodescribeinfulldetailthe'Vthissectionisaboutdesignthegoalofmiisnotneedtota#V)Fe kandݓW-WuWWWWWWWWWWWvW~WWWWWWWannexWany"WݓWWvWWWanything۴Wanywhere|Wapis~Wapisapplicationprogramminginterfacesandsuchareoutside~Vappear۴WappliancesWapplicabilityWapplicableWapplication~WappropriatedWWWWWW-WOWbemorespecificforinformationservicetoworkandunderstVbecauseWbecomeݻWbeforeYWzWWbetweenZWjWkWbitsWbootsrappingܺWboth=Wbroadcast+WOWbroadcast/multicastܻWbut0WW=W|WWݻW+WbyXWwWWWbWܻWWcallQWcan\WuWܶWOWdWcapabilitybW+WOWcarefulܹWcarrydWcaseCWW+WdWcasesoWclaimBWclarificationۓWܹWclarifyWclarifyingW bprovide W?WhWW WtWWWWWWWWWWWWWWWWW'W+W/WWWprovideaconcreteextensiblesyntaxforthemihfidVVprovideaconcretesyntaxforthesessionidVprovideaccurateinformationregardingencodingwhenvaluef+VprovideanalgorithmforduplicatepacketdetectionoruseaVprovidebetterdefinitionforchannelidVprovidecontextwithanintroductiontotherequest/responseV/VprovideextensibilityrulesforallocationofnewtypenumbeVprovideformatandrulesforinclusionandinterpretationofVprovidemorespecificsonwhatenoughinformationmeansistVprovideoperatoridentityattributetoeachinstanceofwlanVproviderttestimationalgorithmsorrelyontheunderlying VVV V V V V V V V V V V V V Vremovefigure19@VWvdeletethetextVdeletethewordmobility4VdeletedWWWkWWWdeliberately Wdeliver"Wdelivered"WdemonHWdescribed\WWdescribingWUWdescriptionWWWfWdescriptionofusecaseswherethismaybeapplicablefVdesignatedlWdesiredWdestinationWVWWdetailmWdetailsݽWW-WdetectedWWdetermineWdevices"WdiagramۋWdiagrmsWdifferences*WWdifferentQWTWۋW۫W0WWW?WWWdifferentaccessnetworkssupporthorizontalhandovermechan۫Vdirectly"WdiscoverSW"Wdiscovered{Wdiscovering"WdiscoveryݓWW"W?WWdiscrepanciesWdiscussionݓWWWdiscussionthatsomeie'sinthesubmissionarenotinthetVdiscussionsܛWݜWdisparate*WdistinctWdistinctionWdividedWW | R|*bconceptual5WܟWconcreteWWWconditionsWWconductedۉWconfidenceQW:WWconfidencelevelWconfigurableޖW5WconfigurationjW܄WOW8WWWconfigureۄWۉWkWlW܂W܄WWWWW"WWޔWW{WޔWޔWޔWޔWLWW{WޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔWޔW4܄Vconfigurestatus܄Wconfigurestatusstatus245܄VconfirmېWWW\WyWzWWW>WBWCWJWrWyWzWconfirmationWWconfusingWcongestion-safeWconiferlWconistent۽WconnectW W0WconnectedWconnection,WconnectionsOWPWTWconnectivAWconnectivityAWSWWRWSWܡWconnectsWconsiderOWPWۼW۽WWWWWZWconsideraddinguniqueeventidentiferforlinkdetectedVWW8EMcdocumentۡWPW[WW.W>WWWWWWW WWWWW WtWWdoes(W)WeWfWwW۔WەWWW$W)W-WAWBWYWZWkW{W܁WWWWWWaW݃WWWWdWWWWWWWWWWWW WWWWW W$W<WiWkWWWWWWWWdoeseverydevicehavetosupporteveryquerytypehowisthVdoesn'ttWuWW WoWVVVVVVVVVVVVVVcWWdynamicallyWe#W_WaWiWۈW۪WWWWWWZWwWWWWWWWWWe-core۽We-utra۽WeachuWۄWW@WCWzW{WܸWearlierpWvWxWearlyܫWeWhWjWkWmWnWoWpWuWWabtheymusteitherbemergedintooneoroneofthemberemoveVVthinkWWWVVVVVVVVVVWAWHWIWLWMWOWPWQWRWSWTWUWVWWWcWdWiWkWnWxWۂWېWەW۶WWWWWWWWWWW WWWWWW%W&W@WNWVWXWYWZW\WkWoW܄W܅W܆WܓWܕWܡWܣWܩWܴWܼWWWWWWWWWWW0WIWݍWݘWWWWWWWWWW W WWWWWWW!W"W#W$W%W1W2W3W4W5W7W8WVW}WWހWނWބWޅWއWމWދWތWޕWޖWޗWޞWޡWުW޿WWWWWWWWWWWWWWWWWWWW \cA"MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" are improper for 802.21 scope. The functionality represented by these primitives is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d495g2260i Subir DaskAThese are considered as Media indepedent commands. Each mobility management protocol/mechansim may have equivalent primitives, but we need primitives like this at the MIHF since it has a knowledge of lower layers. If not then what is command service? mRejectedvPRefer to contribution 21-06-0677-00-0000-Hnadover_Flow What happens to MIH_Handover_Prepare? These commands are still vague. The sequence of operation with these commands needs to be clearly described. Update figure 30 as well(Ulises) Refer to commands in table and show which are useful and which are not. How a command should behave? PwDeferredvccontentsWWWWWWWWWWܯWܾWW[W\W]W!W>Wcontextual_WaWcontinuesWcontinuityWcontradictoryWcontradictsWcontradoictedWcontribution܏WܮWcontroliWkWWWWWWW5Wcontrolled@WW݊Wconventions>WconveyۼWconveyed WconveyinghWconveyingpossibilitynotcertaintyregardingheadertypesihVconveys<Wconweys@WcoordinatetWݸWWcopy&Wcore۽W$W:Wcorrcet}WcorrectWWWxWWW&W~WWބWޅWއWcorrectedCWcorrectionۗWۛWcorrectlyW,Wcorrectness WcorrespondingۃWۄWۇW+WdWcostBW_WaWHWW~WPWWcouldۊWWWZWWW W+W݂WݏWWKWQWTWfWhWcounterpartWcountriesSWWWJvofWW0W3W{W݃WݓWݜWWWW"W4W5WޏW\WfWqWwWxWyW~WWWWWWWWWWWWWWWWWWWWWWWWW W!W%W1W4W8W=W?WVW\WjWWWWWWWWWWWWWWofflineܛWok Wold"WonQWTWZWۅWۅWۅWWoperator@WWWoperators[WW@WܗWWopposedܾWoptionaldWoptionsWWorۅWۛW۳WWܗWW3W{W݊WݓWݜWSWfWorderingۋWorganizeZWorganizedZWoriginalZW7WotherRWۓW۳WWqWWWWW2W;W݊WSWoutەWWWWoverTWpacketۅWpage۳WWHWܬW2Wpage18sentenceonline22changesasfollows۳V-`bfWfalinkteardownisusedtoreleaseresourcesVfa!WfacilitatevWܤWfacilitatesWfacilitiesۢW)WuWfactWfailureUWVWܖWWWfallWfalureWfastWfeatureiWfieldDWEWNWvWwW|WܒWݔWݕWݗWݘWݵWWނW}W~WWWWW+W@WlWfields9WfifthWfigWWfiguer15Wfiguer18WWWW18WWfifthWfigܮWWfiguer15Wfiguer18WWWWWWWWWMcaddSWWbWWWWWWWW WWWW W!W=W|WWWaddacommaafterhoweverandpartinthelinehoweverformVaddacommaaftermobilitybecausewithoutacommathesenteVaddasectionfortheexamplehandoverscenariosbetween802VVovidediVaddedۊWW0WܸWWFW݋WaddingۂWۅWۊWadditionuWWWWWYWܶWW[WadditionalەW W*WMWtWܓW݄WݸWadditionalieisneededundergeneraliealsothereisnone Vadditionally:W\Waddress:W;W<W=W>WۈWەWWWWWWWWW W%WݍWݷWaddressedWaddressesܰWWWW WݏWaddswWadequatenWadequatelyەWadjectiveeWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWW,creasonۅWWreasonsۅWWreassembled Wreassembly Wreceipt WoWWreceiveRWZW>WWreceivedOWPWQWRWSWTWUWVWWWۅW>W5WWWreceiver WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWtgW WrefeernceܯWrefereW܏WܧWWWWWreferto802.21asieee802.21consistentlyinthedraftܧVreferenceW!W$W۬W۽WWWWWDWEWܪWܯWWWWW:WAWFW\W݂W݃WݕWݖWݘWWXWYWpWqWޛWޟWޢWWWW WWWP RvAv MIH Function receives this event from link layer. MIH Function then passes this notification to the MIH User(s) which have registered for this notification. The MIH User(s) Higher layers may reevaluate the link under consideration by retrieving other link quality related parameters. Any handover procedures that may have already been initiated may need to be rescinded.v@A>  )c  TT  >wAccepted-Modified{k) done 2006/09/21 2006/04/24SEQiaobingFXieGMember^Technical, Binding_78`3a7.3.13.3bAHChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Detected" event. The MIH User(s), Upper layers includeing MIH Function itself, may discover additional properties of the link before selecting it for establishing connectivity.H@H@ded.@ cA1. The description and categorization of Horizontal and Vertical Handovers are general and not directly related to a certain MIH Service. It might not be so appropriate to place general mobility concepts in the section 6.3 which is for MIIS only. 2. The Figure 19 should focus on the illustration of MIIS. It seems that the the current title and description focus on the concept of Horizontal and Vertical Handover d905g2211v:by contribution from Eunah and comments 473, 474, 475, 477w Superceded 2006/09/21 2006-04-3019EXiaoyuFLiuGMember^Technical (was Editorial)_44`14a6.3.2bpAdd two groups to keep consistent with Table 6: 2) Access Network Specific Information 4) Higher Layer Services cLine 14 says 'IE are classified into three groups', however, it seems that there are 5 groups in Table 6. The classification in page 44, the groups in Table 6 and the groups of TLV formats in Section 6.3.4 should be consistent. d906g2212906g2212!callWۋW۔W۝WYW[WܥWWWW݆WWWCWWWWWWWWWWWWWWWWWWjWvWwWxWyWWWWWallmihprimitivescannothavedestinationidentifieraslocVallmihprimitivescouldoptionallyhavesessionidentifierVallmihfisrequiredtoequipwithxml/rdfregardlessofitsVallrequestresponsepairsinsection7shouldbesemanticalCVallocateWallocatedWallowWW2WWWWallowlocalmiiscase2VallowedWWallowing WallowsW WaloneWrWalready?W@WgWpWvWۤWWuW1WW|WWWWWWWWWWWWWWWWWWWWWWWWWWsmihcapabilitydiscoverymessagebyaddingnetworkidۊVammendmentsW7kimproveAWin"W#W۳W۴WݓWW)W-WdW|WWWWWWWWWWWVWYWvW}WWWWWWWincaseanmobilenodehastheinformationofthemacnewpoadVinsection6.3.4.2.5itisnamedtypeienetworkqosinsteadVincludeWincludedWincludingWinclusionWinconsistencyWincorrectWWWtoWintroductionjWkWmWnWoWzW{W|W}W~WہWinvestigationܹWip<W\WWjWis#W0W<WYWZW\W]W_WaWjWkWmWnWoWuWzW{W|W}W~WہWےWۓWWWWCW|WܬWܶWܸWܺWܻWWWWWݳWݴWݻWW-WOWjWoWisthisabootsrappingissueifnotthenwhyithastobemeܺVisthisfortlvonlyisthatisthecaseweshouldsaytlviCVV Gcd151g2231wAccepted{k) done 2006/09/21 2006/04/28MarkedEPeretzFFeder^ Editorial_22`21a5.4.3bA;The overhead in exchange of information should be minimized;@A*  332  *c[The overhead in exchange of information should be as less as possible Reward this sentenced165g2232i Subir DaskPl. see Comment # 162m Superceded{l) none needed 2006/08/29 2006/04/28 EPeretzFFeder^ Editorial_22`31bAlMIIS provides the ability to access this information about all heterogeneous networks in a geographical areal@A>  33#  33)  33>cAMIIS provides the ability to access this information about all heterogeneous networks in a geographical area This is supeflous, remove it@A>  33$  (  33>d168g2233{k) done 2006/08/29 2006/04/28 zxcsimple:WWsimplify۱Wsimplifyphrasingremovedash۱VsimplywWxWyWzW{W~WWWWWWsincefWrW۪W)W.WܖWW WWeWOW|WވWtWuWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWsinceweareaimingtorepresentmorethanonesyntaxforieVsingleWW W WWsinrWsip۪W_WWWWsipisnotusedasamobilitymanagementprotocol_VVsizeܒWܔWWWW WW'WWWlWsizeofmihffixedheaderisnotconsistentwiththatdepictܔVsizeofthefieldsisnotconsistentwiththatinthefigureܒVsizevalueforopcodeandaidisincorrectWVsleepmWslightlyWslightlyconfusediflinkupgoesfromlinklayertomihhowVsm/gmm/rrc$WsmallW W W WWcprovidedWW WW?WkWprovideareferencetotheplaceinthedocumentwheretherVprovided'WYWܟWWWW1WkWWWWWWWWzWWWWproviderfWgWhWiWWprovidesIWWW>WW?WkWWprovidingWWWprovisionܟWprovisionedW<WproxiesWproximity.W3WWWWWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝW`carchitecturaliWWarchitecture/W W<WareWW?W@WZWqWۃWیWەWۦWWWWWW$W)W7W:WNWRWjWtWܖWܚWܭWWWWW WW0W1WfWzWWݸWWWWWWWWWW(W-W>WYWvWކWފW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^WLbchangevalidrangefromn/atoܖVchangevisitingtovisited۲Vvisitingtovisited۲V۲Vevisitingtovisited۲V۲V V+ceventSWېWWRWTWUWVWWW܃WaWݍWݛWW#W(W)WIWLWMWaW?WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW4W4W4W4W4W4W4W4W4WcToctheexamplequeriesshouldbeinaseparateappendixandnotNVtheexytensibilityaspectofdifferentiesisnotveryclearVthefactthatthetidisinthefixedheadermeansthatinfVthefieldnumberofadditionalheaderidentifiersisnomoreܓVthefirstparagraphof6.3.5talksaboutgeneraluseofmiis`VthefirstparagraphrepeatswhathasalreadybeensufficientpVthefirsttwosentencesmeanthesamethingsIVthefollowingparagraphtalksaboutthestaticanddynamici?Vthefollowingsubsectionsshouldbeaddedtosection5.6.1mVtheformatofthecostinformationelementmustbedefinedbHVthehandoverdecisionmoduleisneverdefinednorused.VtheieeestandardshoulddefinethepacketformatVtheinclusionofmihnetworkaddressinformationprimitiveifVgVhViVV VdefinethepacketformatVV.VtheieeestandardshoulddefinethepacketformatVVedbHVHVVccThe 'may' respecting use with the SID is not meaningful. How is the receiver of a message to determine whether the TID is to be interpreted in the scope of the SID or not? Is it implicitly defined depending on the presence of the SID in the message? d731g2303vA Replace "may be" with "is". In order to handle the case of duplicate transaction identifiers at the responding node, this identifier may be is used in conjunction with the Session Identifier.@Af 33  33 33  33 33fwAccepted-Modified{k) done 2006/09/21 2006/04/28 EEleanorFHepworthGMember^ Editorial_116`1a8.3.3.2b c,The TID is actually in the fixed header d753g2305 2006/08/29 2006/04/28 EEleanorFHepworthGMember^ Editorial_118`5a8.4bcahnge to definite cTypo defiite d763g2308{k) done 2006/08/29 2006/04/28 EFarrokh@ ۽cAPretty confusing picture with MIH Reference Model for 3GPP: 1) Not consistent use of the terms GERAN/UMTS/LTE (GERAN is a radio access network, UMTS is the entire system (CN+RAN), LTE is the current name for the evolved system (mainly air interface and radio access network aspects)); 2) E-UTRA is the evolved (UTRA) air interface (not consistent with what is on top of UMTS and GERAN); 3) E-CORE is the evolved packet core (not consistent with what is on top of UMTS and GERAN)d195pAIn 21-06-0691-02-0000-3GPP-3GPP2Amendments, - added new ref "IS-2000.4-D" - replaced figures 9 and 10 - changes made in 5.5.5 text ?? the changes against 5.8.3 "3GPP Amendments" is unclear and not done. ?? the instruction on "new MIH-3GLINK-SAP Primitives" is unclear and not done. 1. Inserting new text after 7.4.15.3.3 does not seem right. 2. Not sure if this is a new section either. 3. does it want to insert another table 24 after 7.4.15.3.3, and remove the current table 24 from AP<wcnon-posۭWW Wnon-trivialWnon-usWnone[Wnor.WWWnormalWnormative-WNW>WWWWnormativelyWnorthboundWWWWnotW#W(W)W*WDWKWLWOWPWQWRWSWTWUWVWWW^WcWdWeWfWiWlWsWwWۂWۂWۂWۂWWWۂWۂWۂWWWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWWۂWۂWWۂWۂWtl`‚eʃ5‚fEP[|Pa Vೃ;[k‚g۲ܧQݗޏ+6t‚h$۰W܋+ݺ~"-‚idt۶ܕ3mqÃ@l}‚jۜăt׃ӃH‚q)ݸnt௃sv‚r~̓"W?WWWWplacedW WpWWW!Wplacement Wplaces݅W<Wplane4W5WplayingfWgWhWiWWplays݃W݃Ws݃W݃WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWssconfiguVpleaserefertothe21-06-0602-00-0000poacapabilityprefixVpluralWcWdWpluralformVcVdVpoa_WaWۇWۈWۊWW WW W"W#WܩWܺWܾWWWWWW+WZWWWWWWW"W#W$W%W*WQWdWfWpoadatarateVpoa-address~Wpoas_WaWpointۊW-WܝW݂WWIWpointerWpoints۬W:WܨWܪWܯWWpolicyܡWWݎWpolicyengineisnottheonlyupperlayersݎV <+EJeffFKeatingGMember^Technical, Non-binding_18`23a5.3.2bAJIt would be more economical for the network to "broadcast" the information about networks, i.e. roaming lists, priorities, etc. to all users on a periodic basis or as significant changes occur. New users, as they enter the network, can still request this information, but it would not be requested by the MNs on a periodic basis.ut to the mobile terminal for start of MIH interactions. d903g2225v,Identified as Issue 60. no suggested remedy.wRejected 2006/09/19 2006/04/04MarkedEJeffFKeatingGMember^Technical, Non-binding_18`23a5.3.2bAJIt would be more economical for the network to "broadcast" the information about networks, i.e. roaming lists, priorities, etc. to all users on a periodic basis or as significant changes occur. New users, as they enter the network, can still request this information, but it would not be requested by the MNs on a periodic basis.r3ݖGMember^Technical, Binding_46`7a6.3.2bA" Two types of location information are supported in draft-ietf-geopriv-radius-lo- 04.txt, i.e., geospatial location information and civic location information. "@A> 33$  33Z 33>c.Reference to Internet-Draft should be removed.d377g2394wAccepted{k) done 2006/09/21 2006/04/28Table 6ݗE YoshihiroFOhbaGMember^Technical, Binding_48`56a6.3.4bA" Case 2: If the number of octets occupied by the value field is greater than 127, then the length field is always greater than 1 octet. The MSB of the first octet of the length field is set to the value '1' and the remaining 7 bits of the first octet indicate the number of octets that are appended further. The number represented by the 2nd octet and subsequent octets of the length field indicates the total size of the value field. "@@ ݖE YoshihiroFOhbaa8.3.2xU8.3.2.1V8.3.2.2ݵ8.3.2.3۔8.3.3ܑăՃ'8.3.3.1ܒܓփV}WX8.3.3.2ݸ׃38.3.3.3ܔ8.3.4(ah8.4ijݹފૃ8.4.1ݺY8.4.1.1ދ8.4.1.2ތ8.4.1.4~8.4.1.8]8.4.2.1k8.4.2.11Z8.4.2.13n8.4.2.1648.4.2.178.4.2.18ގ8.4.2.2ލ8.4.2.21܁pݽ8.4.2.23ހށ8.4.2.24ݾݿނރ8.4.2.3l8.4.2.7m8.4.2.8J8.58.5.1.1\8.5.1.28.5.2ۉ8.5.2.1)8.5.2.10a8.5.2.11b8.5.2.12cۉۉۉۉۉۉ.5.3.1588.5.3.1798.5.3.188.5.3.19>q8.5.3.208.68.6.1r8.6.1.2ۏaܚWa4ܚVa-1W-WWWWa2WsWannexۀWہWWWWW-WsWtWuWvWWWW TbA>  332  33  33> MIH message delivery and its relation with other protocol layers. [Remove figure 24, page 112] @A>  332  33  33>cFigure 24 does not relate to the section 8.3. We put It to show how MIH Protocol can interact with other protocol but I don't think it's indispensable to be there. Therefore, I suggest the figure 24 be removed.4݅E YoshihiroL2 sublayers (they are shown in details in each specific L2's MIH reference model) Show only one arrow that will represent ES/CS/IS together (all MIH signaling) Show only two kind of arrows: Local Interaction and Transport : only 2 colors instead of 3 different colors... -> Replace by 21-06-0612-03-0000-Reference_Network.pptKcAlthough valid, this diagram looks too busy. This is exactly the type of diagram that scares the reader and does not help them have a straightforwad reading of the overall MIH reference model. This plays against the acceptance of the draft.d187g2255pwhere is the "last sentence of second bullet "? Does it refer to the D01.00 draft spec or 21-06-0612-03-0000-Reference_Network.ppt? where to add MIH User from network side in the figure? v[Delete the last sentence of second bullet and add MIH User from network side in the figure.wAccepted-Modified{c) instructions unclear 2006/08/22 2006/04/30Marked5݅E Yoshihiro8vnumberWqWWnumberofoperatorsisarequiredpieceofinformationVobligatedWobtain۳WobtainedܬWoccurencesWoccurrencesWoctetWofIWQWSWTWZWgWlWۋWێWۓW۔WەW۪W۳WWWWW)W1WJWWJWJWJWJWJWJWJWJWJWJWJWJWXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXݠ!ptext۴W۽WWW{W݃WWthat۪W)W;W݃WtheۅWۓW۪W۴W۽WWWW.W2W;WAWRWWYWthisisinconflictwiththeacceptedcomment195pppisnotVthisistechnicalandsomeoneneedstoprovidetable33aVthisshouldbeasupercededcasenothingisdonehereYVthroughout2WtlvZWto۪W۽WWW2WAWܾWW&W{WݛWWlWtry{WtwoDWܾWunclear۽WusedWuserܥWvaluesۓWvertical:WvsܥWwant۽WܾWweܾWwhen)Wwhether WwhichۓWܾWwillWwiredWwithWAWlWvWword WW>Wx۽Wv0VWގW0aborthandoverގV1ەWݒW,WVWށWރWގW1accepthandoverގV1intra-technologyhandoverhnadoversacrossesssincaseofەV1tlvspecificparametersށV1tlvspecificresponseparametersރVN ctheKWLWQWaWwWzW{W}WW݃W݌WݍWݎWݐWݔWݛWݵWݸWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWW W"W#W$W%W&W'W*W,W-W.W/W2W4W5W8W:W>W@WBWIWNWOWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWvcthelastlineunderthevaluecolumnneedstobefixedthee@thelasttwowordsofthelastlineneedtobeinterchanged@wthelasttwowordsofthelastlineneedtobeinterchanged@wthelasttwowordsofthelastlineneedtobeinterchanged@wthelasttwowordsofthelastlineneedtobeinterchanged@wthelasttwowordsofthelastlineneedtobeinterchanged@wthekeyprimitivesdefinedaspartofmihsaparedescribed@cmayۋWېWۓWەW۳W۶WۼWWW'W.W3W:WCWZWrWyWzW{W|W~WW܄WܫWܰWWWW1WݍWWWW W W"W#W$W%W&W*W>WOWދWތW>W?WWWWWWWWWWWWWWWWWWWWW WWWW"W?WpWtW}WWWWWWWWWWmaybeexhaustedifdifferentclassesofdataareVmayshouldbemaybeinthesentenceދVmayshouldbemaybeinthesentenceandcommandcodeshouldbތVmaybeWދWތWmbbWmdeiaWmeachismWWWWW Wmechanisms_WܛWܦWWW3WWmechansimWmedia'W(W)WDWېWۖWWWIWܠWܢWܤWܰWܺWWWWWWWW}WݐWWWrcmanagement"WWܤWݐWW4WYW_W2WWW<WWWWWWWmanagesWmandatoryWWWWWmanditorilyWmannerWmanualWWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWf 'EFarrokhFKhatibiGMember^Technical, Binding_5`53a2b5Add 3GPP2 HRPD C.S0024-A and C.S0063-A in references.c3GPP2 HRPD should be supported.d43wAccepted{k) done 2006/09/21(EFarrokhFKhatibiGMember^ Editorial_7`31a3b~Remove "These are" in the beginning of sentence. Alternatively, insert "Protocol" in its place. Analogous at page 7 line 52.c0Consistency with similar nearby section clauses.d52{k) done 2006/09/21)EFarrokhFKhatibiGMember^ Editorial_7`6-7a3bAdd a note saying that Handover is also referred to as Handoff. Rephrase the sentence as follows: " ... obtains facilities and preserves traffic flows ... ". Also, remove dash in link-switch in that paragraph. Ditto on line 20 and possibly elsewhere.c"Completeness; conciseness; Grammard54{k) done 2006/09/21*EFarrokhFKhatibiGMember^ Editorial_8`18a3b(Remove "MIH Users are" in the beginning.beginning.beginning.beginning.(EFarrokh-aEEleanorFHepworthGMember^Technical (was Editorial)_30`1a5.6b#Update figure to show MIH_LINK_SAP.cThe MIH_LINK_SAP should be shown on this figure (it will clarify the relationship between the "generic" SAP and the media-specific instantiations of it) d215g2231vJIssue 40 Resolved by contribution 21-06-0692-00-0000-MIH-SAPs-GenericModelwAccepted{k) done 2006/09/21 2006/04/2812EEleanorFHepworthGMember^Technical (was Editorial)_31`37a5.7.1bChange sentence to "the selection of the transport mechanism is dependent on the access technology that connects the MN to the network and the location of the MIH PoS".ModelwAccepted{k) done 2006/08/29 2006/04/2812EEleanorFHepworthGMember^Technical (was Editorial)_31`37a5.7.1bChange sentence to "the selection of the transport mechanism is dependent on the access technology that connects the MN to the network and the location of the MIH PoS". MIH PoS". vbcA_Syntax error in "The format of theLength field shall be per the defiite form of ITU-T X.690."_@Af 33  33( 33A  33H 33fd761g2307{k) done 2006/09/21MarkedwENada, Golmie, Member^ Editorial_118`24bA$Replace "The remaining octes (i.e. excluding the first octet) of the Length field shall be used to indicate the catual length of the Value field." with "The remaining octets (i.e. excluding the first octet) of the Length field shall be used to indicate the actual length of the Value field."$@A  33  33 33p  33v 33  33 33  33 33cASyntax errors in "The remaining octes (i.e. excluding the first octet) of the Length field shall be used to indicate the catual length of the Value field." G ecThe current text does not describe what the link layer will do before sending back the response. For example, where and how will the link layer get the information before it can send the response.d567g2314wAccepted{k) done 2006/09/21 2006/04/24MarkedfEQiaobingFXieGMember^Technical, Binding_82`50a7.3.19.4bAChange the text to: The recipient retrieves the value of requested IEs and passes them on to the MIH user(s) that originally requested the information. The MIH user(s) may proceeds to use them in handover operations.@A 33  33  L  )c    TT  cuthe recipient should be MIH Function since this is a link primitive and MIH Function does not do handover operations.d571g2315v3Please refer to comment 555 for resolution as well.wAccepted-Modified{k) done 2006/08/29 2006/04/24 gEQiaobingFXie6bcalledWWRWmWcanېWhWܬW}WWW WYWrWtWWWW>WpWWWWWWWcancel6WcandidateOW|Wcandidates}WcannotVWWWcapabilitiesAW<WܾW1WWWWWcapability#WAWiWېWܬW[W1W|WWWWWWIW}WWWWcapable"WcapitalizeWWcapitalizeethernetconsistentlyVcapitalizemanagementVcaptionKWWcardsvWvWvWvWKWcardsbWbWsbWbWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKW3mcnotclearwhythescopeofdefinitioncolumnisneededasalVnotclearwhythistableishereforthecsapbutequivalenVwhythistableishereforthecsapbutequivalenVVlearwhythistableishereforthecsapbutequivalenVVq ݍcA"A Link Up event may also carry IP address renewal indication which may inform upper layers of the need to initiate a layer 3 handover. This may help to improve the performance of layer 3 handovers." Should it be new IP address acquisition, IP address renewal has a different meaning. d149g2414iMathieu PeressejJCould you please define "IP address aquisition" and "IP address renewal" ?wAccepted{k) done 2006/09/21 2006/04/28MarkedݎE YoshihiroFOhbaGMember^Technical, Binding_21`30a5.4.2.3bAU "In case of local commands, messages typically propagate from the upper layers (e.g., policy engine... ) to the MIH Function and then from MIH Function to lower layers. In case of remote commands, messages may propagate from upper layers via MIH Function in one stack to the MIH Function in a peer stack (with the use of the MIH Protocol)."U@Af 33Q W 33d  g 33܉^ Editorial_142`46b%Remove the second "Handover Complete"c#Duplicate entry "Handover Complete"d882g2326{k) done 2006/09/21܊ENada, Golmie, Member^ Editorial_144`26bA%Replace "many user" with "many users"%@Af 33  33 33  33$ 33fcASyntax error in "many user"@A> 33  33 33>d883g2327{k) done 2006/09/21܋ENada, Golmie, Member^ Editorial_144`57bAReplace "The UE is known to the network but not transport channel is established" with "The UE is known to the network but no transport channel is established"@Af 33,  33/ 33|  33~ 33fcAYSyntax error in "The UE is known to the network but not transport channel is established"Y@Y@Y@r*clikezWW<WWWlikecommandserviceflowinsection6.2.4theinformationszVlikelihoodWlikelyWlimitationOWWWWW1W5W5WmitsWlineKWۦWWWWWWWWW-WkWWWlinesܬWW]Wlink&W'WCWDWFWGWHWIWJWLWMWOWPWQWRWSWTWUWVWWWcWdWeWfWۄWۅWۉWێWېWWWWWWWWW-W8W9W=W@WJWQWRWSWYWZW[W\W`WeWgWhWiWlW܂W܃W܈WܐWܝWܡWܫWܰWܲWܳWWWWWWWWWWW W W0WAWDWJWaWbWlinkconfigurethresholdsaddsinrinadditiontosignalstrVlinkdownaddothercausesauthenticationfailurebillingfabVlinkhandoverimminentmayVJcitisobviouslythatsupportedeventlistparameterinmihcapېVitisthefirsttimethattheframestructureisreferredtoVitshouldbemadeclearthatwhenamihuserregistersforaVitwouldbehelpfultohaveadiscussionofpadding/alignmenVit'sWWWWWWit'snotclearwhatthedifferencebetweendifferentlinklaVit'snotclearwhatthepurposeofpre-definedreportsishoVVVVOcjust@Ljustified@key@layer@layers@lengthoftypeielistofnetworksshouldbevariable@like@limitations@*lines@linkalinkdetectedindicationthedetectionmaybeeventhrought@linkparameterschangeindicationcanonlybegeneratedwhen@nnlinkparameterschangeindicationcanonlybegeneratedwhen@nt@linkidentifierismissingintheparameters@nguret@linkidentifierismissingintheparameters@nA |cAf  33*  9  33Z  i  33fation model should be considered as the only reference model. It gives the necessary logical lay out of functions needed by any reader of the Draft standard to determine what is the best use they want of 802.21. HcAThe text of this section makes a lot of hypothesis how information for handover management is retrieved "When provisioned the MN relies on periodic access to its operator MIIS to obtain pertinent information such as new roaming lists, priorities and any other related information that would enable to utilize services in various access networks." More generally, there is too much suggestion what the architecture for using 802.21 reference model could be like. There is no point in hinting a +EXiaoyuFLiuGMember^Technical (was Editorial)_42`20a6.3.1bAs1. Move the concept of Horizontal and Vertical Handovers to somewhere in Section 5.1, Introduction. For example, Page 13, line 7, mentiones ' hard' and 'soft' handover. Horizontal and Vertical Handover may also be put there. 2. Change the title of Figure 19 to 'Media Independent Information Service' and slightly change the figure to hightlighten the concept of MIIS.scoduction. For example, Page 13, line 7, mentiones ' hard' and 'soft' handover. Horizontal and Vertical Handover may also be put there. 2. Change the title of Figure 19 to 'Media Independent Information Service' and slightly change the figure to hightlighten the concept of MIIS.scscted remedy.wRejected 2006/08/21 2006/04/04EJeffFKeatingGMemberd903g2225v,Identified as Issue 60. no suggested remedy.wRejected 2006/08/21 2006/04/04EJeffFKeatingGMemberererd904bupdatefigureVupdatefiguretoshowmihlinksapVupdatesectionVupdatethenumberoftheitemstartingatthetypeiepoalo܍VupdatetheprimitiveprototypeappropriatelyaVlo܍VupdatetheprimitiveprototypeappropriatelyaVaVveprototypeappropriatelyaVaVlo܍VupdatetheprimitiveprototypeappropriatelyaVaVlo܍VupdatetheprimitiveprototypeappropriatelyaVaVoband/orWentcouldbeand/orWWthedocumentcouldbeVand/orWWVandthedocumentcouldbeVand/orWWouldbeVand/orWWqblinkeventdiscoverrequestېVlinkeventregisterconfirmresponseVlinktypeisnotnecessarytoputhereiftheproposedgenerVsponserVrVlinkeventdiscoverrequestېVlinkeventregisterconfirmresponserVlink-layerWWlink-state8Wlink-switch)WlinkidentifierWWlinkparamaeterۉWlinkparameterۉWlinkparameterlist_Wlinkparamterlist_WlinksPWTWkWWWW1WlinktechFWGWlinktypeFWGWۉW"WaWbWcWlinktypemediatypeofthelinkaVlinktypetypeofthelinkbVcVlist-W.WAWPWZW]W_WuWۂWېW=W@WJWKWLWSWTWUWVWWWXWbWcWdWhWkWmWyWzW{W~W܎WܷWWWݙWWW@W[W^Wlistatableoflinktypessupportedby802.21^VlistedܼWDWlistingSWlittlevWlocܗWܘWܙWc vpoaݜW"W*WdWfWWWWW?WWpoa'sWpoasݜWpointWpoints*W۴W1WpolicyەWWposݓW"W*W\WfWWW WpositiveݜWpositivediscussionswithietfbernardnotclearhowtohandݜVposs\Wpossible*Wppt>WBWWW2W{WWpragraphWpragraphhasbeendeletedVprepareQW\Wpresent"WVWprettyWpreviousIW=WprimitivelWۉWێWWW"W\WWWprimitivesW0WCWWWWWWWprincipleWpriorities۳WprioritizeWpriorityۋWprobablyݓWproceduresRW\WWpropertiesSWZWprovider's۳Wprovides4W5Wprovisioned۳Wprovisioning۳WqosۅWWWܾWWWSWqualityRWۅWqueriesZWܗWquerlyܗWquery"WܗWWquery/response WrWܳUYbAMove section 5.6.2.1 into the media-dependent SAP section (5.6.1)cInconsistent with section 5.5d216wAccepted{k) done 2006/09/21ESanjeevFAthalyeGMember^ Editorial_31`48a5.7.1b"Capitalize "Ethernet" consistentlyc Customary used238{k) done 2006/09/21 ESanjeevFAthalyeGMember^ Editorial_36`59a6.1.4bMRename the message from the remote MIHF to local MIHF as Event DeregistrationcMRename the message from the remote MIHF to local MIHF as Event Deregistrationd270{k) done 2006/09/21ESanjeevFAthalyeGMember^ Editorial_41`15a6.2.5bQReorder the table 4 and table 5 to be consistent with ordering in other sections.cQReorder the table 4 and table 5 to be consistent with ordering in other sections.d302phow?{c) instructions unclear 2006/09/2192006/08/292006/08/29 ESanjeevFAthalyeGMember^ Editorial_42`62a6.3.1bInsert comma after "mobility"cImproved sentence flowd321( bmedia-dependent*WW#WuWmedia-independent#WWmedia-specificWmedium7WpWmention)W3WW"WpWWWmentionthattheflowsarelogicalsincereaderscanthinktVmentionthattheframeworksupportsuseofeitherl2orl3m3Vmentionthattheinformationservermaybepresenteitherlo"VmentionedWWmentionesWmerge`WqWqWqWqWqWRVEbspecificationsYWpWspecificsWspecifiedcWlWWRW܌WܕWܾW1W}WނWޖW5WwWxWyWzW3WIWWspecifiesWWދWތWWspecifyހWނWvWWWWWWWWW9WWWspecifyenvelopeofcapabilitiesasappropriateforastaticVspecifyparametertoidentifylinktypetoscanVspecifytheformatorgivegreaterdetailsinthevariousva9VspecifyingVWWspeedGWIWJWۉWlWmWspelled۝W۝W۝WFWGWHWIWJWۉWspelled۝W۝WW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W/W7WqWܫWDWݎWW2W9W<W=W?WstacksW WWabsplit@Vstandard@station's@\string@success@|suggestedisuggestednewpoalist@supportedcommandlist@t@table@tables@technologies@Gtechspecificparamete@ytext@vthan@that[the@Eݍ3=+theaccesstoinformationshouldbefast@thebroadcastmechanismwithlayer2transportwouldbediff@theencodingformatisdefinedastablebelow@thefollowingfigureillustratesthecombinationofallthe@theieeestandardshoulddefinesthepacketformat@ them~then@they@9tiesneedtobespecifiedclearlyfordifferen@they9y9@they9theinforma@thisparameterspecifiesthelistofcommandsisquerytype@thisprimitiveisdeliveredfrommihfunctiononoldserving@4cshifted-WiWshim۪WshouldWKWLWOWPWQWRWSWTWUWVWWW`WfWiWqWsWۉWۋWۍWێWېW۟WۡWWWWWWWWWWWWWWWWWWWWWWW۟WۡWۡWbreplacemaintenancewithabetterterm-Vreplacemanyuserwithmanyusers܊Vreplacemedia-independentwithmedia-dependent#VreplacemihbymihfinentiredraftܥVreplacemihfunctionentitiesmayalsosendwithmihfunctio/VreplacemihgetinfoindicationwithmihgetinforequestVreplacenetworkidentifierwithlinkidentifierVreplacenetworkidentifierwithmediatype]Veplacenetworkidentifierwithmediatype]V]VifierVreplacenetworkidentifierwithmediatype]V]Vlacenetworkidentifierwithmediatype]V]VfierVVkparamterlistwithnumber_VreplaceperformanceofaccessnetworkswithaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1Vreplacereceptionofthespecifiedsduwasacknowledgeatl2܌Vreplaceresourceretentionstatus20withresourceretention܇VbuseofabitmapmodeltoencodethelistofeventsthatareTVVuseofabitmapmodeltoencodethelistofeventsthattheUVWVuseofabitmapmodeltoencodethestatusoftheeventdereVuseofabitmapmodeltoencodethestatusoftheeventregiVVuseofnetworkresourcesforaccessinginformationshouldbeVusethetermipv6withdhcpv6insteadVipv6withdhcpv6insteadVVshouldbe۸Vusethetermipv6withdhcpv6insteadVV bC----------------------- ..................................................|...................|...............................................|........................................................................... ------------------------------------------------------------------------------------------------------------------------------------------------- SupportedISQueryTypeList | List | Set of supported | List of supported IS Query types on client D | | IS query types | [@Az  ;      I  0  zcT'SupportedISQueryTypeList ' should be inserted for consistency with section 8.5.1.2d577g2211vit's already there in draft wRejected 2006/09/21 2006/04/30EJinFLeeGMemberxhN_108`18a7.4.15.3bNRemove section 7.4.15.3 and replace it with the appropriatly numbered appendixcgThe example queries should be in a separate Appendix and not in the main normative part of the standardd674g2218v7Move the section to Appendix. Also look at comment 673.wAccepted{k) done 2006/09/21 2006/04/28OEAjayFRajkumarGMember^Technical, Binding_138`44a8.6.1.1bChange ".. network may be able to indicate to the mobile node....." to "... network shall be able to indicate to the mobile node..."cAMIH Capability Discovery is specified as "may" be done through media specific broadcast messages, however, this needs to be specified as a "shall" since this would be the basic mode by which a terminal may be able to know whether the network it is attaching to is MIH capable or not.d865g2229i Ronny Kim Ronny Kim MEAjayFRajkumarGMember^Technical, Binding_84`35a7.4.3n$boriginator}WxWzWother WAWPWRWZWpWsWwWۧW۰WWWWW"W?WIWPWfWWWWW>WVWYWrWsW|WWWWWsWWWWotherieeegroupsdefinesimilarmeansandsupportclientsVotherinformationmaybevendor/networkspecificandcouldbVothersuWotherwiseۖWWVWWWoutܡW W"W%W|WWWW*W<W>WWout-of-bandWf-bandWWf-bandWWWWWWWWWWWWWWWWWWWWWWWWWW3vbimportant#W'WimproperDWimpropoerWWimproveݍW.Win W#WAWOWPWQWRWSWTWUWVWWWZWfWlWpWsWvWxWۃWۄWېWۓWۜW۞WۧW۫W۰W۶WWWWWW#W,W2W3W5W7W:WAWBWDWEWGWHWNWPWSWTWUWVWWWYW]W_W`WyWzW{W~W܁W܂WܑWܔWܕWܚWܟWܤWܥWܧWܬWWWWWWWWW'W(W)W*W,W1W8WGWIWQWWQWWWWWWWWWWWWWWWWW\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\WYW\W\W_W_W_W_W_W_W_W_W_W_W_WWWWW > "cand݃W݉W݋WݐWݛWݜWݸWWWWWWWWWWWWWWW WWWWW W"W&W'W(W)W,W-W4W5W:W>WNWYWdWlWnWqWކWތW2W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W2W2WޕWޕWޕWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWchavemorespacebetweencharactersinsta/ueandpsdn/fabox-ViVhavingܑWWnWWhavingasinglemih-3glink-sapseemsinappropriateasthemiVhavingtwonormativedefinitionstlvrdf/xmlofthedatarepVhetWvW member9<=>?@AEGHIKLMNOPQRT^abcdefgijklmnpqrstwz{}݆݈݃݅݇݉݋݌ݍݎݐݑݒݓݔݕݖݗݘݚݛݜݭݲݵݸݹݺݽݾݿʃу҃ӃԃՃ,-./2458:>@ABCILMOVYlnwޓޖ111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111000000000000ޗޗޗޗޣޣޣޣޣޣޣޣޣޣޣޣ~vbsame?WAWsWWWWWsamechangeisneededatthetableofcontentsandp72/l62V62{V{V62{V{V{V{V{V{V{V{V{V{V{V{V{V{V{V{Vpchrpd'W&Whrpd1xev-doshouldbeaddedtothereferencemodel&VhteWhttp>Whypothesis<Wi#WېWZWwWW5W6WWWW W$WlWWWWWWi-dsWicmpWid۔WuWWWWWWWWWWWWLWMWWideaۓWidenticalNWWWidentifeirݵWݺWidentifer_WcWidentifiedWidentifierێWgWWݒWݵWW]WaWWWWWNWOWVWYW\WWWWWidentifiersDWEW[WtWܓWݸWUWXWidentifyWWidsCWRWTWUWVWWWWWWWWW W&W&W&W&W&W&W&Wu ctoWWWs in a congestion safe way; adaptive RTT measurement which allows retransmission in a congestion-safe way; concatenation of several small messages into single tranmissions; guarantee of transaction ordering (if this is required); efficient transport of large messages which require fragmentation (by partial rather than full retransmission); and so on. ]ijkmnpvw{ 2006/05/146/04/28ise, "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 Fo[cwithinەW۞W7W:WܕWݸWYWtWuWWWsWWwithinthemihfheaderadditionalidentifiersarepresentthݸVwithout۝WWWWWWW/WWwlan:WwmanWwon'tqWwordۖWWWܱWWWgWtWWWWwordorderVtVwordingxW=WwordsېWWW1WiWWWWworkYW>WW<WWworkingWwould$WWWWOW6WtWvWWWWWWW<WWWWWWwouldbegoodtocitethespecifictechnologiesasexamplesVwpaWwpa2WwraparoundWwrongۦWvWwrtۼWxvWxml#WܬWݚWWWWxml/rdfWxxxWxxxxxxxtWvWyesWWW܏W܏W܏W܏W #vetc۫W{W\WWWWW?WWethernetWeunahzWWevaluateTWevaluatedTWeventQWRWSWTWWWWWWWWeventandcommandidshavebeendefinedinsection8.3.3.4iVvntsWexaminationWexamineއWexample WWWexamplesZW\WWexchange۔Wexchanged۔Wexchanges4W5WjWexclusionZWexistinggWWW>WexplainۅWexplainedWWexplainingjWexplainsWexplanationWexplicitly&Wexposed0WextendedށWރWextent*WfactWfail{WfeatureWfeelWfeelsWfewnWWfieldWfig۴W\WWfigure۴W݃W,W\WW%W2W{WWWWWfigure22hasbeenupdatedaspercomment473andcontributiV2V{Vfigure/diagrams\WfilterWfinal\WformZWformatܗW۵W3Wc ^Technical, Non-binding_29`1bThe following figure illustrates the combination of all the protocol stacks in a mobile node. In this illustration we assume the MN can connect to one of the following access technologies: 802.16, 802.11, cdma2000, GERAN, UMTS or LTE.c;Add the following text before the introduction of Figure 11d208g2240wAccepted{k) done 2006/09/21 2006/04/28MarkedEPeretzFFeder^ Editorial_30`36a5.6.1b5.6.1 Media Dependent SAPsc[5.6.1 Media Specific SAP Be consistent with the mdeia dependent and media independent textd217g2241{k) done 2006/08/29 2006/04/28Marked EPeretzFFeder^ Editorial_31`46bA6The IEEE standard should defines the packet format....6@Af  33  33  33    33fceThe IEEE standard should define the packet format.... Should is a requirement. Not appropriate hered236g2243{k) done4  ܬcAܭܰ@ܱ@8ܾcApA$@bc:@;cv @-@ca_@`GbKa{ @)g b ^ccFd@ew/f'E*c g.G0v91vCh6{7@i=?jE{5G@K@ kLG%M@2Pbl^0c@6e@mk@nrbpzbA*{cvA}@kv@݃c{{{bc^wbcAbObAp{AcA Ec ^+bAAbA5bA bA"bAcAvA#F+Pbchangethetextto#V$VOVPVQVRVSVTVUVVVWVfViVlVpVoVwVyVchangethetexttothecsapdefinedintheieee802.16stan5Vchangethetexttothemsapdefinedintheieee802.16stan4VchangethevalidrangefordestnationidentifierinallprimiVethevalidrangefordestnationidentifierinallprimiVVidentifierinallprimiVVonidentifierinallprimiVVdrangefordestnationidentifierinallprimiVVV5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5VhangetomayinfluencehandoverdecisionVchangetomobilityextensionsof802.16andchangereferenceVchangetopolicyengineentityVchangetoprovideinformationabouttheavailabilityofacceV$b27ܔWܬW2W28ܬW294WHWWW}WW2nd۫WݗWWlW3JWۉWەWW)WHWRWSWYW|W}WܒWzW݃WݍWpWށWރW1W6WwWyW|WWWWWWWWpWyWWWWWWW3cellularumtsV3nothingiscarriedށV3rdfschemaurlwVyV3urlresponseoneextendedschemaurlparameterރV3useofmihfethertypeV3.2W3.78W304WW5W5W5W5W5W5W5W5W5W5W5W5W5W1W32XWTWUWVWWWXWcW33ۉWcWݳW33aW34ۉW3493W35ۉW35-40W36ۉW37-43`W3753:W38ۮW=W38-49=W39=W3gW3glink1W3gpp۽W۾WYWHWsWWWXW3gppsystemsalreadybroadcastV3gpp/3gpp2W3gpp2&W'W1WHWsW WYW >cAOn the top portion of the Flow Model picture, the MIH_Command.confirm primitive looks out of place. The model that should be followed is defined in the following document: "Standard Terminology, Conventions, and Methodology (TCM) for Defining Data Services", CCSDS 910.2-G-1 (http://nssdc.gsfc.nasa.gov/nost/wwwclassic/documents/text/CCSDS-910.2-G-1.txt). Note: The Standard Terminology, Conventions, and Methodology (TCM) for Defining Data Services is a summary of, and cross-reference to,B internationally adopted standards for defining data services. Here is an excerpt: "The OSI service model provides limited terminology for describing the roles of the two (or more) users of an OSI service. These roles are requestor and acceptor. In the context of a particular instance of OSI-service-procedure, a requestor is "an OSI-service-user that issues a submit primitive and as a result may receive one or more deliver primitives." In the context of a particular instance of OSI-serviing8$ ܾcATYPE_IE_POA_CAPABILITIES: The Security and QoS capabilities of the PoA need to be interpreted in context of Security and QoS capabilities of specific access network as specified by TYPE_IE_NETWORK_SECURITY and TYPE_IE_NETWORK_QOS: This aspecis not very cleard436g3237i Hong ChengjAAs indicated, several items of the list must be interpreted in the context of a specific link, e.g.spcified in TYPE_IE_POA_MAC_TYPE IE (6.3.4.3.3). Therefore, the item listed here should be divided into two groups, the link specific information, e.g. Security, QoS, and the network specific information, e.g. Internet Access, IP version, etc. Therefore, suggest to create two IEs: TYPE_IE_POA_LINK_CAPABILITY; TYPE_IE_POA_NETWORK_CAPABILITY.mAccepted-Modifiedpfy these values (Securiy and QoS) in the context of access network as opposed to in the context of just the PoA.wAccepted-Modified{a) awaiting resolution 2006/08/29Markedndard.cHepworthGMember(pcbytezW{WWbytesܑWWcW2WtWuWWWWWccorrectthewordtowarsonline25VcallZWWWcalled WW~WcanAWcWdWeWwWۄWۅWۋWېW۝W۪W:WܬW}W*W>WYW~WއWޖW1W5W6WtWvWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWW'W1W5W8W{WWWWWWWW#Wcannotbeusedforvariablesegpoa-address~Vcan'tWcandidate|WcannotۄWWWWWWWWmWWWcannotinteroperatewithusingthestandarddocumentwhichrVcannotinteroperatewithusingtypeielistofnetworksiesVVVےVےVےVےVےVTwcthelastlineunderthevaluecolumnneedstobefixedtheeVthelasttwoparagraphsin8.1areoutofplaceandshouldbqVcalso*WiWrWwWېWۓW۳WWW)W.W6W:W|WWWݍWWW W"WYW~WއWޖWWWWWWWWWWWWWWWWWW WW!W?WpWWWWWWWWalsosparqlqueryisnotcorrect~Valsothelatterdefinitionofmobilenodeisnotclearsince.V.Vsince.ValternativeSWۈWWWalternatives۳WalthoughqW~W݃Walthoughvalidthisdiagramlookstoobusythisisexactlyt݃ValtituderesolutionWalways۾WWܰWWWއWambiguityWWWambiguityofwhetheraphrasepertainstothewholesentenceWVambiguitysuccinctnessallowthecasethatmihisnotsupporVamendۆWamendedܸWamendmentۅWamendmentsWamendsۊWamendsmihcapabilitydiscoverymessagebyaddingnetworkidۊVammendmentsWcitisimportanttointerfaceortransportmechansimcontradiVitisimpossibletotestcompliancewithabstractionssuchaVitisnotclearwhatisthedifferencebetweencommonandotVitisnotclearwhatsupportingmultipleinterfacesmeans!Vitisnotclearwhetherthescopeoftheprotocolfunctions Vitisnotinscopeof802.21toprovidehorizontalhandoverVLXcthecurrentmihreferencemodelfor3gpp2triestoshowhowYVthecurrenttextcanbebetterexplainedthissapdefinesthVthecurrenttextdoesnotdescribewhatthelinklayerwilleVthecurrenttextdoesnotstatehowremotecommunicationisVthecurrenttextimpliesthatthediscoveryofmihfunctionVurrenttextimpliesthatthediscoveryofmihfunctionVVYVYVYVYVYVYVYVecommunicationis3VthecurrenttextimpliesthatthediscoveryofmihfunctionVthedecriptionisthesameastherequest܄VthedefinitionofeventidsaremissingitiscriticallyimpNVthedefinitionoftheparameterforsupportedisqueryismissdVthedefinitionsgivenforthemihhandoverxxxprimitivesin܏VthedefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofthemesageisthesameastherequest܅V^Technical, Non-binding_72`39a7.3.7.3bA[Modify the section 7.3.7.3 as following ]: 7.3.7.3 When generated This primitive is generated by an upper layer entity MIH Function that may need to set threshold value for different link prarameters. @Az  33-  33c  33y    33  33zcALink_Configure_Thresholds command is Link command that goes from MIH Function to Link layer through MIH_Link_SAP. It is issued by MIH configure command to set thresould values for link parameters. Therefore, section 7.3.7.3 should be changed as suggested.d522g2216w Superceded 2006/09/21 2006/04/30EJinFLeeGMember^Technical, Non-binding_112`21a8.3bA[Delete the following rows, page 112, line16] : Figure 24 shows possible MIH message delivery and its relation with other protocol layers. [Remove figure 24, page 112] @@4uܧEVivekFGuptaGMember^ Editorial_15`56a5.2bUReplace all occurences of just "802.21" by "IEEE 802.21" consistently in the draft.c=Refer to "802.21" as "IEEE 802.21" consistently in the draft.d107g3223{k) done 2006/09/21 ܨEVivekFGuptaGMember^ Editorial_15`64a5.3b%should be "key and salient points..."c$"key salient points..." missing andd109g3215{k) done 2006/09/21 ܫEVivekFGuptaGMember^ Editorial_20`35a5.4.1.1bAEvents may originate from the MIH Function (MIH Events) or any lower layer (Link Events) within the protocol stack of a client device.@A> 33Y  33 33 33 33 ܫEVivekFGuptaGMember^ Editorial_20`35a5.4.1.1bAEvents may originate from the MIH Function (MIH Events) or any lower layer (Link Events) within the protocol stack of a client device.@A> 33Y  33 33 < YbcFigure 24 does not relate to the section 8.3. We put It to show how MIH Protocol can interact with other protocol but I don't think it's indispensable to be there. Therefore, I suggest the figure 24 be removed.d705g2222i Ronny KimjDelete figure 24ksuperceded by 697m Supercededw Superceded 2006/09/21 2006/04/3024EJeffFKeatingGMember^Technical, Non-binding_138`44a8.6.1.1bAdd a figure (flow diagram) for section 8.6.1.1, that is the complement to figure 29, that shows the MIH capability discovery procedure initiated by the network POA.ck POA.cor link parameters. Therefore, section 7.3.7.3 should be changed as suggested.d522g2216w Superceded 2006/08/21 2006/04/30EJinFLeeGMember^Technical, Non-binding_112`21a8.3b6/08/21 2006/04/30EJinFLeeGMember^Technical, Non-binding_112`21a8.3bbbd705 2006/04/3024 brephrase)W,Wrephrasecollectsinformationonnetworksinitslocalitysi,VrephreaseWrephreasethetwosentencesasfollowsinanycasethemihfVhfVVLۄE Guo JunxiangF Shu GuimingGOther^Technical, Non-binding_92`10a 7.4.7.2.2bvAccept the changes to section 7.4.7.2.2 as described in: 21-06-0629-00-0000-Amendment for MIH_Configure.response.ppt .cAIn current draft D01, several handover primitives are inconsistent to their corresponding messages on the definition of OldLinkAction parameter. Such primitives are: MIH_Switch.request, MIH_Handover_Initiate.request , MIH_Handover_Commit.request, MIH_Handover_Commit.responsed615g2211wAccepted{k) done 2006/09/19 2006/04/24ۄE Guo JunxiangF Shu GuimingGOther^Technical, Non-binding_92`10a 7.4.7.2.2bvAccept the changes to section 7.4.7.2.2 as described in: 21-06-0629-00-0000-Amendment for MIH_Configure.response.ppt .cse.ppt .c.vokA.[vokA.okA.okA.okA. Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new ed repor^editorialwwwwwwwwwwwwwornms+W+W6/04/28 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 14breplacenetworksecurityandqualityofsecuritycapabilitie<VreplacenetworktypeswithlinkidentifierZVreplacenormativewithinformativeVreplacenumberofparametersinlinkparamterlistwithnumber_Vreplacepage24withcontribution21-06-06xx-01-0000-atose=VreplaceperformanceofaccessnetworkswithaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1Vreplacereceptionofthespecifiedsduwasacknowledgeatl2܌Vreplaceresourceretentionstatus20withresourceretention܇VreplaceresultoftryingtoconiferthelinkwithresultoflVreplacesection5.51withcontribution21-06-0624-00-0000-nwVreplacesection5.5withcontribution21-06-0620-00-0000-nsvVreplacesection5.5.2withcontribution21-06-0625-00-0000-nxVreplacesection5.5.3withcontribution21-06-0627-00-0000-nyV8GcdifficultWWdirectW WWdirectionvWdirectlywWW"W$WW WW WWdisallowSWdisambiguateWdisassociated-WiWdisconnectmWdiscoverېWQWRW{WW"WWWWIW}WWWdiscoveredWWWQWQWQWQWWۊWWݏWWW+WdiscoveryregistrationandeventregistrationmechanismsareVdiscussܯWݳWdiscussedDWpWvW+WdiscussionAWWW܏WWdiscussionofhow802.3networkscangetdirectinternetaccVdiscussionoflogicalnetworkreferencemodelusesroamingcVdispatchmWdispatched7WdistinctWdistinguishۊW:WܜW:WdistinguishedWdistributedWdo_WbWeWfWlWۈW۬WWCWܐWWWWWWW݊WWdoweneedtodefinewhatnetworkinitiatednetworkcontroll݊V0 vmessagelW۔WW"W WWmessages۔WW"WWWjWmethodsWWnWmhzWmibjWmichaelWmih*WQWRWSWTWgWlWWܰWW3W{W}W݃WݓWW"W,W4W5WCWaWއW\WWWWWWW W#WjWoWWWWWWWWWWWmihconfigurethresholdshasbeendeletedfromtable-4VmihfunctionreceivesthiseventfromlinklayermihfunctioQVRVSVTVmihlinkhandovercompleteeventisverydifferentthanmihVmihlinksapismediaspecificܰVmihlinksapisnowaddedtofigure12andexplainedinsectVᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃᧃKliuۅ=>?ᬃᭃᮃᯃᰃ᱃ᲃnjedjou݃?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghiperesseopqrquۏrajkumar,-./2458:>@ABCILMNO~ဃ၃ႃჃᄃᅃᆃᇃሃቃኃዃጃ᷃ṃểƃsalminenshuۄWshuguimingۄVVVVVV]^_`abcdefghijksubir  !"#$%&'()*+subritaisuke݀݁tanlmnotaniuchipqrstu@_‚AƒЃH245Yj~ဃܰ҃‚C+܃݃‚D,ܱIx{‚Eܲ‚F7ݑ‚GăӃ‚H-.NŃܳJݒ߃‚I‚Jԃ‚Q89Ky‚R/:ƃܴ‚S?@Aǃ:;ܵՃփLM}‚TKȃɃʃ˃ܶ׃؃كNOPQݓ‚UZ[ےۓ̃̓΃ <=>?@Aܷڃۃ܃RSݔ‚VۑσЃ!"B݃ރTUݕ‚W߃V|ݖ‚XX\у҃#$CDEܸܹܻܺW݉‚YYFX~ݗ‚Z]^%&Gܗܼ‚a'H‚bӃ(Yݘ‚c‚dԃZ‚e_`)Iܾܽ‚fa*‚gbՃփJKLܿ[ݙ‚i׃M\2bremovefigure19@VremoveforloopandsplitintotwotablesVremovehelp@Vremoveho-typepossiblyaddlinktypeinsteadVremoveinthe21draftPVremoveisembeddedVremoveitis۹Vremoveline1uVremoveline33transactionidUVremoveline37-43andaddreferencetothedefinitionofthe`VremovemiddlesentenceremoveinthiscaseatendVremovemihcommandconfirmaswithorw/oitthemihcommand#Vremovemihcommandconfirmfromfigure18Vremovemihgetinfoconfirmaswithorw/oitthemihgetin{Vremovemihgetinfoconfirmfromfigure22Vremovemihhandoverinitiatemihhandoverpreparemihhandov\VaVVremovemihnetworkaddressinformationfromtable14fVremovemihnetworkaddressinformationfromtable19hVremovemihnetworkaddressinformationfromtable4V V VGc4ېWWW)W-W0WNWݵWݾWBWWWWiWmWvWwWxWyWWWWWWWW4.1W40WW41aW,WmW43KWW44KWWW45WW,WWW46kWW47WW48W49W49-50W5ېWW݆WWWW=WmWWW5.3.2XWW5.4.3W5.5$WWvW5.5.1wWxW5.5.3yW5.6.1W2WYW[WWW5.6.1mediaspecificsapV5.6.2.1ZW5.8nW5.8.3+W50W51W52WWWWVVVVVVVVVVVVVVVVVVVVVVVVVVVV| 2 cA Link_Handover_Complete command can be used for upper layer to check whether IP-configuration need to be updated as described in 7.3.17.1 and 7.3.17.3 of the current draft. Therefore, I suggest 'IP_Renewal_Indicator' be inserted in Link_Handover_Complete event.  d562g2217v#Link may not have this knowledge...wRejected{a) awaiting resolution 2006/09/21 2006/04/30ENada, Golmie, Member^Technical, Non-binding_111`12bEither remove the mention of "802.3 Ethernet" in the label of the protocol stack in Figure 23 or revise the caption of Figure 23 to read:"L2 Data Frame Packet Format in 802.3 Ethernet".cFigure 23 on page 111 is titled: "Common MIHF Frame Format" although the label on the leftmost protocol stack is labeled "MIHF Frame Format for 802.3 Ethernet". d687g2302vVremove the mention of "802.3 Ethernet" in the label of the protocol stack in Figure 23wAcceptedyAssigned as issue number 30{a) awaiting resolutionresolutionBOcerrorGWIWJW۠W5W6W8W<WGW^W_WaWfWiWlWoWpWrWtWvWxWyWzW}W~WW܀W܃W܆W܇W܈W܊W܋W܌W.WlWmWerrorswWesWespecially;WWessential'Wessentially WestablishܡWestablished܋W WestablishmentWestimation WWWetcܰWܵWWWWWW?WethernetWWethertypeWWevaluatedWeven^WmW?W WWWWWWWHW?W?WWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHW|+brenamethenon-posmihentitytomihnon-posforconsistencyۭVrenaming<WrenewalݍWWrenumberWreorderWSWreorderthetable4andtable5tobeconsistentwithorderiVrepalce=Wrepalcebeaslessaspossiblewithbeminimal=VrepeatedWbeaslessaspossiblewithbeminimal=VrepeatedWWaslessaspossiblewithbeminimal=V=VxcthemihconfigurerequestisusedtocontrolthebehaviorofkVthemiheventregisterandmiheventderegisterrefertotheVthemihfunctionheaderconsistsofatwopartsonewithfixthemihfunctionheaderconsistsofatwopartsonewithfixthfix%9bcertain#WTWdWWWchagesݓW,W,W,W,W,W,W,W,W,W,W.W?WAWFWGWHWIWLWMWOWPWQWRWSWTWUWVWWWXW_WcWdWeWfWiWjWlWmWpWrWsWtWuWxWyWW۲WۻWWWWWWWW,/W7W=WRWYWjWkWmW|W܂W܅WܑWܒWܔWܖWܤWWWWWWWWWWW+W,W.W0W7W<W>W?WIWRWVW_WcWdWeWgWkWzWݑWݒWݔWݕWݘWݙWݚWݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWݨWݩWݪWݫWݬWݮWݯWݰWݱWݵWݶWݻWݾWWWWWWWWWWWW(W3W4W5W7W8W<W?WEWFWGWHWOWRWlWyWzWtcremovesfromthewordsupportsinthelinethatquotesotheVremovetheletterafromthesentencethatsaysthemihfuncVremovethesfromresultsinthelinefromoneaccessnetworVremovedAWsW۝WWݕWݖWݘWWWWrenameۭWWKWrenamethefigurecaptiontoremotecommandserviceflowKVrenamethemessagefromtheremotemihftolocalmihfaseveVrenamethenon-posmihentitytomihnon-posforconsistencyۭVrenamedWrenewalݍWWWreorderWreorderthetable4andtable5tobeconsistentwithorderiVerthetable4andtable5tobeconsistentwithorderiVVonsistentwithorderiVVwithorderiVVerthetable4andtable5tobeconsistentwithorderiVVVVVVVVVcrepeat@replaced@reponse@jrequest@Zrequests@+reserved@resource@results@rfc@round@samesap@satisfy@Aschema@sdo@ksection@sections@see@#sent@sentences@Qservice@services@setsets@4shifted@should2shouldn't@ouldn't@houldn't@tivenotnounformsincethereisnosuchth@sincethereisnosuchth@ivenotnounformsincethereisnosuchth@haveanotherblockcalledl3transport@suggestednewpoaidentisnotneededifitispartofsuggeste@qsupported@Yswitch@syntaxerrorinnetworksecurityandqualityofsecuritycap@Dsyntaxerrorinthisisusedtorespondtheresult@4systemmanagementhasbeenintroducedasaserviceherehowe@.take@?target@Stechnology@that's@the$\0Qctoinsureinteroperabilitytheieee802.21mustdefinehowt@Fupper@what@8jshow@oKk&v5@ !changeline46onpage23ofd01.00asfollows@ changetheprimitivedefinitionandtheprotocoldefinition@:notallissueshaveremediesassignedonissuelist@the@assignedonissuelist@nthe@kretrieval@&isincorrect@8jby@Kkretrieval@&HcunifiedݜWAWBWDWGWHWJWKW[W]W^WbWuniformIWuniquePWWWuniqueeventidentiferWuniquenessWunit]WWWunknownWWunlabeledhWunless WunlikeWunlikelyW/v 5vwAccepted-Modified{k) done 2006/09/21 2006/04/288EAjayFRajkumarGMember^Technical, Binding_31`18a5.6.3bAChange "5.6.3.1 MIH_NMS_SAP This SAP defines the interface between MIH Function layer and the Network Management Entity or the Network Management System. This SAP defines the interface of MIH Function with the system and is used for configuration and operation of MIH Function in any given system." to 5.6.2.2 MIH_NMS_SAP The MIH_NMS_SAP, first introduced in this specification, provides the interface between the MIH Function and the Network Management System (NMS). The SAP defines primitBives for setting and retrieving the values of the configuration parameters that drive the functional behavior of the local MIH Function instance.c>Include the MIH_NMS_SAP in the Media Independent SAPs section.d232g2242wAccepted{k) done 2006/09/21 2006/04/282006/04/28 :EAjayFRajkumarGMember^ Editorial_34`49a6.1.2bappendedݗWlWappendixWWNWWWappenidng2WappenidxWapplicableWWapplicationVWiWއWapplication/rdfނWapplication/sparql-qހWapplication/sparql-rނWނWނWfނWނWނWނWނWނWނWplication/xmlހWނWapplicationsAW7WapplyܪWappreciablyAWappropriateAWTWkWnWۉWW#WUWYWW}WappropriatelyWWaWappropriatlyNWapprovedKWLWaps?WJWarchitecture݂W Ware W#WAWLWNWOWUWbWpWxWۂWېWەWWWW7WCWTWUWVWWWXWYW\WcWsWtWxWܪWܴWܺWܾWWWW W(W*W0W1WJWjW|W݃WݖWݗWݸWWWWWWWWW2WaredescribedinthesectionbelowVarenotraejVareaWWWpWbdefinitions:WAWBWWwWWdefinitonWdelayWdelet)WdeletevWwWۦW۪WWWܠWܭWAW2WxWzWWWWW W WWWWWWWWWWWdeletecsapandmsapbetweenmhfunctionandmanagementen2VdeleteheterogeneousVdeletel2fromabovesentenceܭVdeletelinktypeoperatorVdeletemediaagnosticAVAVAVAVAVAVV"Vdbpronounced2WpropagateݎWproperly۔WWWWpropertiesOWSWܾWWproposalۅWWWWWproposeWWproposedWWprotocol(WpWsWtWwWxWWW#W/WܫW(W0W{WݎW W2W}WxWzW|WWWW$W%WsWWWWWprotocolsW WWprototypeaWaWaWaWaWaWaWaWaWaWaWaWaWaWaWaWaWaWaWaW+creserved}WWލWWreservedbitshouldbeassignedލVresideWWW1W5WWresidesܟWWresiding:Wresolution*WWWW*W*W*W*W*W*W*W*W"cimpropersentencethisprimitivereturnstheresultoftheqQVimproperuseofthemihgetinfoindicationwhenacommandiVimprovesWݍW WimprovedtWۧWWW"W,W>W?WMWnWqW8WimprovedclarityۧV>Vimprovedclphrasing?VimprovedgrammarverbvsnounVimprovedphrasing"V,VnVqVimprovedsentenceflowVMVqVimprovedsentenceflowVMVMVy!cimprovement@"in@J2=nincurrentdraftd01mihconfigurerequestprimitivehasac@inorderformobilenode'smihfunctionentitytocommencem@inappropriate@}inconsistency@cinconsistent@incorrect@inetrafce@info@@information@?informative@initiator@instantiations@inter-technology@interpret@is@rGP]܎ wo>Nismulti-hopscenarioshouldbedescribed@issoft-handoverlimitedtohandoverbetweenhomogeneousacc@Wissue@it@>itisimportanttointerfaceortransportmechansimcontradi@itisobviouslythatsupportedeventlistparameterinmihcap@item@Jm@JJJfultohaveadiscussionofpadding/alignmen@Jowheresipissupporte@lv@ |cfMIH_REPORT should be InfoQueryResponse since in Section 8.5.4.2, only InfoQueryResponse is mentioned. d666g2423wAccepted{k) done 2006/09/21 }EKenichiFTaniuchi^Technical, Binding_107`64a 7.4.15.2.2bA--RDF_DATA: When this InfoQueryType is specified, InfoQueryParameters Response is a string which contains a SPARQL (Protocol and RDF Query language) query response [2] where the SPARQL query is supposed to contain an appropriate query for obtaining expected RDF/XML data. --RDF_SCHEMA_URL: When this InfoQueryType is specified, InfoQueryParameters Response is a null string an URL of extended schema . This InfoQueryType is used for obtaining the URL of the extended schema. --RDF_SCHEMA: WhenB this InfoQueryType is specified, InfoQueryParameters Response carries either the URL of the extended schema the query originator wants to obtain or a null string when the URL of the extended schema is unknown an extended schema. @@`22aAnnex B1 >ނbC(  33e parameters Format ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | Type | Size Length | Description Value | ---------------------------------------------------------------B------------------------------------------------------------------------------------------------------| | TYPE_MIME_TLV | Variable | A MIME Type TLV An octet string for a MIME type to specify an XML a format | | | | of SPARQL Query Result. When this TLV is | | | chimnkEFarrokhFKhatibiGMember^Technical, Non-binding_122`31a8.4.2.1bL" addressing the new PoA" should change to " address when at the new PoA".cConfusing phrased785wAccepted{k) done 2006/09/21MarkedlEFarrokhFKhatibiGMember^ Editorial_123`9a8.4.2.3b "as follows:"c Customary used792{k) done 2006/08/29 mEFarrokhFKhatibiGMember^ Editorial_123`58a8.4.2.7b "Parameters"cSpellingd794{k) done 2006/08/29 nEFarrokhFKhatibiGMember^ Editorial_125`21-22a8.4.2.13b'"Combination of actions is permissible"cImproved phrasingd800{k) done 2006/08/29 pEFarrokhFKhatibiGMember^ Editorial_127`9a8.4.2.21b"status"cSpellingd808{k) done 2006/08/29 qEFarrokhFKhatibiGMember^ Editorial_137`20a8.5.3.19b(Replace "further deliver" with "forward"cImproved phrasingd855{k) done 2006/08/29 rEFarrokhFKhatibiGMember^ Editorial_138`42a8.6.1ngM `ÄJREÄRV۝ÄSrÄWXÄWZ1ÄbgÄdeۻÄfhÄgj)ÄijۧÄqrĆEGUGa1.1ە1.2ۖۗۘۙۚۛۜ۝Ƀ,1.3۞!"#1.4݅1.5۟1.6ܛWஃ18#W2۠ۡʃ$&'݆pq22{W3ۣۢۤۥۦۧۨ ./1ܟ()*+,-.wՃ>ᴃᵃ3.1W402ܚWܠ݋݌5.1۩5.1.3σ݌݌݌݌݌݌݌ܪ˃24565.3.2!۱۲۳۴̃789:݂5.4"=5.4.1.1۵ܫ5.4.3#۶۷۸۹ۺۻܬܭ̓;<>?@5.5$ۼܮ΃AB݃5.5.35.5.4۽۾C5.5.5ۿσDEF5.6ЃGhXcpartیWuWܑWAWWW'WNW\W]W^W_W`WaWbWcWdWeWWWW*WPWQWRWSWTWUW_WcWdWeWfWWpartial W WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWpdsn/fa-WWpduWpeer{W!W%W3W<W>W?WpeersW>WgWpending WpeopleWperWeWmWvWWWperlastmarch06denveracceptedcommentresolutionaddanVperformuWۂWېW|WperformanceWW|WݍWperformed3W,(^technicalbindingܬVܾVVVVVVVVVVVVVVVVVVVVVorted in the PoA. SIP proxies may be placed in the network somewhere, but one support by the PoA is not required in quite the same way as it is for MIP.d530g2266 2006/05/14 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`45r should not have to interpret this information to pass it to the MIHF.wd529g2265 2006/05/14 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`9a7.3.9bRemove SIP from list.cIt is difficult to envisage a scenario where SIP is supported in the PoA. SIP proxies may be placed in the network somewhere, but one support by the PoA is not required in quite the same way as it is for MIP.d530g2266 2006/05/14 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`45thGMember^Technical, Binding_74`45'vpleasefWRW`WWbWWCWjWWWvWWWpleasealsorefertocontributionsCVpleaseprovideupdatedfigureVpleaserefertobVpleaserefertocomment108Vpleaserefertocomment259Vpleaserefertocomment518/525andaddthetable/reference`Vpleaserefertocomment555forresolutionaswellfVpleaserefertocontribution21-05-0696-01-0000docRVpleaserefertocontribution21-06-0678formoreupdatesjVpleaserefertocontribution21-06-0736-02-00-000forupdatevVpleaserefertodocument21-06-0648VplesaeWplesaerefertocontribution21-06-0733-00-0000-cresolutionVplusWpoaܾWWppropriatereferencesfromSVprovidedW@WܗW Wprovider's۳Wprovides4W5Wprovisioned۳Wprovisioning۳WqosۅWWWSWqualityۅWqueriesZWܗWquerlyܗWquery"WܗWquery/response WrWgV*c0Consistency with similar nearby section clauses.d57{k) done 2006/09/21Marked+EFarrokhFKhatibiGMember^Technical, Non-binding_8`57a3b_Change "Network-side endpoint of a link that " to "Network-side endpoint of an L2 link that "cAAn MN could be attached to different nodes on the network, depending on which layer one is looking at. At the PHY, the PoA could be an AP/BTS. At the MAC, it could be a radio switch or a BSC. At L3, it could be a router. At the application layer, it is the corresponding node. d70wAccepted{k) done 2006/08/29 ,EFarrokhFKhatibiGMember^ Editorial_8`51a3bbRephrase "... collects information on networks in its locality." Similar change on page 9 line 6.cImproved phrasingd68{k) done 2006/08/29 -EFarrokhFKhatibiGMember^ Editorial_9`31a3b(Replace "maintenance" with a better termc unclear termd75{c) instructions unclear 2006/08/29 .EFarrokhFKhatibi900&H۔EKeigoFAsouGMember^Technical, Binding_114`1a8.3.2.3bDefine it properly.cW"Transaction" is not defined anywhere. Thus Transaction ID does not make sense at all.d728g2211vA Define MIHF Transaction in the definition section: " MIHF Transaction is a combination of MIHF Request or Indication message and the corresponding MIHF Response message (if applicable) that are exchanged between two MIHF peers. This is required to match each request message that is sent by the initiator and its response message. ACK: The acknowledgement messages exchanged as part of the above message exchange do not affect the transaction." wAccepted-Modified{k) done 2006/09/21ەESanjeevFAthalyeGMember^Technical, Non-binding_1`34a1.1b34a1.1b above message exchange do not affect the transaction." wAccepted-Modified{k) done 2006/08/23 ەESanjeevFAthalyeGMember^Technical, Non-binding_1`34a1.1bher standrad bodies.D bremovetheۨVremovetheabovesenetenceVremovetheabovetextuntilqoscontributionisacceptedbytVremovetheentiresection8.5.3.11and8.5.3.12bVremovetheentiresection8.5.3.13and8.5.3.14cVremovetheentiresection8.5.3.15and8.5.3.16dVremovetheentiresection8.5.3.17and8.5.3.18eVremovethefigureandreferencestoitrVY ^editorialу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃$&:IlnWpquwވފދތސޑޒޓޖW=?WYWZWpWWWWWWWWWWWWWWW6WWWWW#########################################################################################? ۋcAWupdates MIH_Handover_Initiate message to extend MIH function. It enables multiple network selection. In IEEE802.16, Terminal can decide to select own suitable network which may be different from one that the current network suggests . So should supply a way by which terminals and networks all can select a suitable network for the handover. Wd637g2252vhAdd another flow diagram for this. The ordering of choices may indicate priority for different networks.wAccepted{k) done 2006/09/21 2006-04-07یE HongchengFZhuangGObserver^ Editorial_87`1a7.2.2.1bA @A 3333cAsThe key primitives defined as part of MIH_SAP are described in Table 18 17. delete page 87, Table 18 is duplicated.s@Af 33E  G H  K 33fd602g2220pno duplicate table 18 found{c) instructions unclear 2006/08/29 2006-04-07 %vstandardەW4W5WWWjWstandardsەWstandradۓWstart*WWstartup{WstateVWWstatementWWstates'Wstatic?WstatusWWstrategy Wstrong{WstructureZWWWWsublayerjWsubmissionWsubmitZWsubmittedWsubscriptionWsubsectionsWsubsequentWsubtypeWWsuccessful*Wsuch۳WܬWWWWWWW?WsuggestnWsuggested)WZWۓWWIWݒWWWWWWWWWWWWWWWWWWWWWW)W3W4W?WoWWWWWWWWWWWsuggestionWsuitabilityTWsuitesWWWsupercededIWWWWWWWsupercededby195Vsupercededby577Vsupercededbycomment186Vsupercededbycomment346V>cmissingspacebetweenwordsViVmissingvaluerangeandcodesVmisuse:WmixedzW7WmkaeWmmGWIW\W]W^W_W`WaWbWcWdWeWlWmWWWFWGWHWIWIW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W`WޕWޖWޠWmobilitymanagemententitiesaremerleyshownasapossibleVmobilitymanagementprޕW9vparagraph۪WparamێWparameterWWރWW4WparametersIWRWTWۅWWaWށWރWWWWW4W?WWWWpart"WQW۔W۪W۳W)WW4W5WWWWWWW%W:W=WparticularWW?WpartnersWWpartsWW WpassesQWRWSWTWpaxsonWpayloadWpdsn/fa-WpduWpeer"Wpeers۔WWperDWUWVWWW۽WEWzW>WYW\WzW{WWWWWW2WkWvW{W}WWWperformanceWpertinent۳WpgێWWphyWWWpicturesWpieceWpiggybackWplaces/WWplanܛWWplane4W5We4W5W5Wlaces/WWplanܛWWplane4W5W5W5Wrovisioned۳Wprovisioning۳WqosWqueriesܗWquerlyܗWquery"WܗWWqbmeansܟWPWWWWmeant[WWmeasureable-Wmeasurements>WmechanismWtWvW|WWWmechanismsەW3WtWWmechannismtWmedia(W)W?WAWDWpWvWۖWW#WܤWWWWAW}WW2W]WaW[W|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWJbwithin?WiWەW7WܫWWݸWsWWwithinthemihfheaderadditionalidentifiersthathelptoaݸVwithout۝Wwlan?WW'WwllkWwmanWwordۜWQWWWWSWwllWwmanDWwordۜWWQWܺWܺWSWwllWwmanDWwordۜWWQWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWclimitationsWWPWlimitedwW1WIW>WtWuWlimitedscopeofhoIVlimiting!WlimitsWlineKWۦWWWW-WkWW݇WWWWWWWWWWWW*W,W?WWWWWW WiWlWtWWWline14saysieareclassifiedintothreegroupshoweveritVVOWPWQWRWSWTWUWVWWWcWdWeWfWۄWۅWۉWێWېWWWWWWWWW-W8W9W=W@WJWQWRWSWYWZW[W\W`WeWgWhWiWlW܂W܃W܈WܐWܝWܡWܫWܰWܲWܳWWWWWWWWWWW W W0WAWDWJWaWbW~WݍWݏWݛWݠWݨWݩWݪWݫWݺWݻWݽWWWWWWWWWWWWWWV 1bJcIf the MN requests detailed information on a "periodic" basis, this could cause excessive traffic buildup as more and more users come into range and make similar requests. d904g2226v1no suggested text. Issue identified and assigned.wRejected 2006/09/21 2006/04/17dstill request this information, but it would not be requested by the MNs on a periodic basis.J mobile terminal for start of MIH interactions. d903g2225v,Identified as Issue 60. no suggested remedy.wRejected 2006/09/15 2006/04/04EJeffFKeatingGMember^Technical, Non-binding_18`23a5.3.2bAJIt would be more economical for the network to "broadcast" the information about networks, i.e. roaming lists, priorities, etc. to all users on a periodic basis or as significant changes occur. New users, as they enter the network, can still request this information, but it would not be requested by the MNs on a periodic basis.J.J1cifweadopt21-06-0522-04-sessioidentifierthelengthfieldݵVignoreWignoresWigonedWiiWiiiWillustratedWWillustrationWimmatureWimminentWimpending|WimplementWWimplementationWWkWWWWrWmW WmWmWSWimminentWimpending!Wimplement WmWmWtWimpending!Wimplement WmWmWWmWmWqkeither|WelementWelementsWelse|W~WenableWenabled۳WencapsulatedWencodingWenginesWenoughWentityWentriesWequivalent\Wessential"WessentiallyWetc"WWevenOWWevent)WeventsݓW)WWexamined/investigateWexampleWWWWWexchangeWexchangedWexecutionWexistingWWexperienceWWWW/W/W/W/W/W/W/W/W/W/W/W/WWflowYWQWfollowedܻWfollowingWݻWfor"WjWkWmWnWoWzW{W|W}W~WہWےWWWWWCWܸWܻWWWWWݳWݻWWoWformat|WformatsforwardingݴWfragmentingWfrom/WWWxWfunctinalityWfunctinallyWfunctionuW+WOWfunctionalityWfurtherܹWgW'I rbcAMTitle of section 8.2.1 is incorrect since the text says L3 is also supported.M@A  33d689g2327{k) done 2006/09/21 2006/04/24MarkedsEQiaobingFXieGMember^Technical (was Editorial)_111`15a8.2.1bAChange text to: The data frame packet format is described in Figure 23. The frame may be used for wired 802 technologies such as ethernet and also other wireless 802 technologies such as 802.11 and 802.16. The above same frame structure may also be used with a standard L3 protocol (UDP/TCP) with a well defined MIH port as well. The discovery of MIH Function entities at L3 is outside the scope of the standard.@Az 33    TT  )c  K  TTzcAj1. text needs to improve. 2. The last sentence is out of place, not necessary here, and should be removed.j@A  33d690 dÃC ÃC0AÃC@MÃCPÃC`ÃCpNÃCÃCÃCÃDݓÃD KÃD0ÃD@ÃDPOÃD`ÃDpÃDPÃDQÃDÃEtÃE ÃE0ÃE@ÃEP<ÃE`ZÃEpÃEÃEۓÃEÃFݔÃF RÃF0ÃF@ÃFPAÃF`ÃFpÃFqÃFÃFÃGÃG ÃG0ÃG@ÃGP'ÃG`ÃGpÃGBÃGÃGݕÃHÃH TÃH0ÃH@ÃHPÃH`(ÃHpÃHݖÃHÃHzÃIÃI 8ÃI0)ÃI@ÃIPÃI`ÃIprÃI#ÃIÃIÃJÃJ ÃJ0ÃJ@݉ÃJPCÃJ`oÃJpÃJDÃJ$ÃJEÃQÃQ *ÃQ0ÃQ@9ÃQPpÃQ`ÃQpÃQ+ÃQݗÃQÃRlÃR ÃR0sÃR@ÃRPÃR`^ÃRpÃRGÃRÃRHÃS'ÃS ÃS0ÃS@ÃSPݘÃS`ÃSpÃS,ÃSuÃSÃTÃT ÃT0;^_ ەۖۗۘ0ۙۚɃ@ۛۜ۝!",௃sP۞۟ܛ#$݅Wஃ`۠ۡʃ&'݆pqpۣۢ1()Ճ>ۤۥۦۧ ./34*+,wᴃᵃۨ 5ܟ-.‚!02݋݌‚"ܠ‚$۩σt‚%ܡܣ/‚& ۪۫ܤܥܧܨ01ࣃ‚'ۭ,3؃ b1oneormoretlvspecificparametersށV1oneormoretlvspecificresponseparametersރV1removesection5.3.2XV1tlvwVyV1transportoptionsV1wirelessieee802.11a/b/gV1-210WރV1removesection5.3.2!V!VcificresponseparametersރV1removesection5.3.2!V!V.3.2!V!VcificresponseparametersރV1removesection5.3.2!V!VcificresponseparametersރV1removesection5.3.2!V!V|pa WۅWۓW۽WRW݃WYWލW2Wa-2۽Waaa}WaboutܥWaboveܾWacceptedWYWaccessܾWaddۅWW&W݃Waddtowheremismatchedpage/line/sectionVadded WېW۽WWWRW{WLWMWލW1Wadded4-7reservedsipisremovedbyapreviouscommentލVaddedasbit41Vaddedasnewsection8.3.2.4linkeventandcommendidRVaddedasnewsections7.3.20and7.3.21ېVaddedattheendofparaseemstoreadbetterVaddednewrefis-2000.4-d۽VadditionalWaddressedܰWafter۽Wagainst۽WalignlWallۓWaloneWalong2WalreadyۏW݃Walso WWܡWLWMWalsoaddedamissingwordwhether Valsoaddedsource/destidsLVMValsomadethesamefixinp9-l6ܡVamۓWamendments۽Wan?W2WܾWandېWۓW۪W۴W۽WW)Wocation in the stack. Add additional text.+ btheݍWݎWݕWݗWݘWݵWݸWݹWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWW W"W#W$W%W&W'W,W2W4W5W8W>W@WBWIWLWMWNWOWYWaW}WWނWބWޅWކWފWދWތWސWޑWޒWޓWޖW5W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWp݅FOhbaGMember^ Editorial_4`10a1.4bFix it.cbIn some places IEEE 802.21 has somehow been clubbed together as IEEE802.21, it should be separate.d29g2421{k) done 2006/09/21 2006/04/28Marked݆E YoshihiroFOhbaGMember^ Editorial_5`5a2bFix it.cGPage 5, second sentence it should All instead of Al (one l is missing).d37g2420{k) done 2006/08/29 2006/04/28݇E YoshihiroFOhbaGMember^ Editorial_86`64a 7.4.5.1.1bFix it.cBPage 86, Line 64 change it to "upper layers", it just says uppers.d600g2422{k) done 2006/08/29 2006/04/28 ݈E YoshihiroFOhbaGMember^ Editorial_88`48a 7.4.6.1.1b"entities make"c"entities makes"d611g2423{l) none needed 2006/08/29 2006/04/28 ݉E YoshihiroFOhbaGMember^ Editorial_47`30a6.3.2bFix it.c0Space is needed between 802.21 and specificationd393g2424{k) done 2006/08/29 2006/04/28 ݋E YoshihiroFOhbaGMember^ Editorial_10" $bAcA%bA&@'bA)i*vA,jA-k./4bA[wk5vA/8v:b>cACE-OkYcA3[6ackFncQp{YtcvjA|c}bA {~bB9bA$ހbAkCEvG8ށ_ނbAmC_EGIACރvAޅFއbAފbA`ލ^ޏcޒdޖcA1bAOCiA5@bA6bAC=c?b WbArXw[bA\cA_Ea_5bcA97dg8fcA:gj;jjA=kg?lbBAACcoffered:W {kdoneOVPVQVRVSVTVUVVVWVZVcVdVeVfVgViVlVqVrVtVwVxVۀVۄVۅVۉVۋVۍVێVېVۓV۔VەVۖVۗVۘVۙVۚVۛVۜV۝V۞V۟V۠VۡVۣVۤVۥVۦVۧVۨV۩V۪V۫VۭVۮVۯV۰V۱V۲V۳V۴V۶V۹VۻV۽VۿVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV VVVVVVVVVV#V$V)V,V.V/V0V1V2V3V3V33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d534g2293wAccepted 2006/08/03 2006/04/24 QEQiaobingFXieQR۩ ۪ESanjeevFAthalyeGMember^Technical, Non-binding_15`18a5.2b%Delete the first sentence of item (a)cThe MIHF is not a shim layer, but is a function. It spans multiple layers of a protocol stack. See Figure 1, for example. Since users of the MIHF can be at any layer (e.g., IP, SIP, application), it follows that the MIHF is not restricted to layer 2.5d100ppRephrase the sentence to: "MIH Function is logical entity that helps and facilitates handover decision making." v^Delete the sentence. Mention MIHF is a logical entity as part of second sentence in paragraph.wAccepted-Modified{k) done 2006/09/21 ۫ESanjeevFAthalyeGMember^Technical, Non-binding_15`41a5.3.1bj"intra-roaming" should be defined. The whole 2nd sentence in that paragraph may be removed as unclear (?)cUnclear definitiond104vmDifferent access networks support horizontal handover mechanisms (mobile initiated, network initiated, etc.).wAccepted-Modified{k) doneDC0v"The service primitives exposed by this unified interface are based on the technology specific protocol entities of the different access networks." wAccepted-ModifiedyAChange the third sentence in this paragraph to as suggested above. Also the notion that MIH_SAP is *NOT* technology transparent needs to be reflected in the draft. Some parameters in MIH_SAP (such as MAC Addresses) could be abstracted and these values exposed as different parameters. But there may be other values which may be difficult to abstract and maybe exposed as is or in a link specific manner. MIH_SAP is not technology transparent but it is also technology independent since it can hBandle different technologies.  {k) done 2006/09/211EFarrokhFKhatibiGMember^Technical, Binding_15`34a5.2b`Not sure MIH interfaces with lower layerare are specified in 3GPP2 document especially for HRPD.c(Change "are already" to "may already be"d103 be"d103--------------------------bhowever#WvWWWWWhoweverformostpartdynamiclinklayerVhrpd'W1WhtmlHWhttpHWݔWqW~WWWhttpwwwianaorgrfc4889schemaxmlVi2WYWwWݔWݖWWWWWWuWWiissuedVi-dsWianaݔWWWidRWTWUWVWWWܒWܚWݓWWoWWWWWWWWWWWWWUWVWidenAWidentifeirݺWWWWWW< v21-06-0648WW21-06-0674ZW21-06-0675WWW21-06-0675-02-0000-lW21-06-0675-03-0000-lW21-06-0675-03-0000-lwithanadditionalstatementfrommichaV21-06-0676CW21-06-0677-00-0000-h\W21-06-0677-07-0000-m\W21-06-0678jW21-06-0680-00-0000W21-06-0681-01-0000-cW21-06-0686-01-0000W21-06-0687-01-0000-qW21-06-0688-00-0000-eۃW21-06-0688-00-0000-eaboutlinkactiondocsubmittedۃV21-06-0689-00-0000W0-mW21-06-0698-01-0000nW21-06-0703-00-0000-c W21-06-0705-00-0000-lDW21-06-0708-00-0000W21-06-0711-00-0000-iZW21-06-0712-00-0000-iZW21-06-0716-00-0000-rW21-06-0716-00-0000-rmodeltextavailableaddsclarificationV21-06-0721-00-0000-iW21-06-0722-00-0000-iW21-06-0723-00-0000-iW21-06-0724-00-0000-i W21-06-0725-00-0000-iW21-06-0726-01-0000-i3W21-06-0728-01-0000-sW21-06-0729-00-0000-l>WWQ2 &knotۓW۴W|WݓW-W\WpWtWvWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWVWvW}WWWWWWnotclearifweneedtointroducethisnotionofnetsapthiVVnotclearwhatisthecontextualinformationmeantVnotificationsWnotion-WWWWnumberWWnumbersYWobjective-WobtainedWof۴W|WݓW-WdW\WgWrWuWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWW:WVWYWvW~WWWWWWofflineWokWWWWWoptionsWor/WaWjWkWmWnWoWuWzW{W|W}W~WہWWWWW|WWdWorderWorgWorganization W@ccross-reference>WcrossesޖW5WcsYWWWcurremtWWcurrentZWeWۃWۄWۅWۋW۽WYW{W4W5WYWޖWXWpWsWtWvW|WWWWWWWWWWWWWWWWWWcurrenttextneedsimprovementVcurrentlinkaction6Wcurrentlinkactionvaluesinmihhandovercommitrequest/resp6VcurrentlySW:WWޖW5W[WtWWcurrrentPWPWPWPWPW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WdWdrewordline40mobilipregistrationmightbenowtriggerV< cnot݌WݎWݔWWWWWWWWWWW(W*W,W:W@WLWMWNWOWVW_WlWnWvW}W~WWބWޅWކWއWޏW6W6W6W6W6W6W6W6W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W`0#ۏ۞؃ܬ#҃N@"S$sݍދZ[ృЃPDy܆)ސQ`۠rv}ܒi݆ݲݹd੃pۢƒ) &փكޑࡃp۩TܡɃ}ݖ5CGܚ߃bݑރ6ใ ?`JW lpݽބŃz‚!ۄ܃j݃݅_p^ȃ<ᄃᚃpp  ۽pBUppendex A-2?? - instructed to use "21-06-0691-03-0000-3GPP-3GPP2Amendments" instead.CvWWapplicationsWappliedWappliesWapplyWappropriateTWWWWWW'W)WWappropriatelyWWapprovedWarchitecture WareZW۔WەWWW0W1W{WݓWW\WWWWWW WWWVWnWWWareaWWas)WDWKWQWUWVWWWfWlWۉWۓW۔WۛW۪W۳W۴W۽WWWWWW)WRWhWent555resolveitthesamewayUVassignedZWWWassignedtoteamVassignmentWatW;WfWattachment W1WattentionWauthenticationWWavailableW{WdWUbincludeadescriptonforfollowingentriesintable-7Vincludealegendforfigure19bsapbstnetcܵVincludeamentionoftheseevenifistostatethattheyareVincludeatimebasedstatediagramshowingdifferentlinklaVincludeclientlocationasanessentialinputparameterinaVincludecontribution0626-00-000linkgetparametersdocVincludedescriptionofcasewhereinformationrepositorymayVincludeexamplesofiereportsandclarifyhowtousethemfVincludeguidelinesonratelimitationandtimeradaptationfVincluderecommendationsfortransportoptionseitherinthisVincluderulesontheinclusionoftheseidentifiersVincludespecificexamplesofallieslistedintable-6thisVincludetheqosmodelandprimitivesdescribedincontributiVVVS^technicalWWWW W WWWWW W"W#W%W'W(W)W*W,W-W.W/W2W4W5W8W>W@WAWBWCWLWMWNWOWVWYW[W\W]W_WaWdWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWmWkWeWeWeWeWeWeWeWeWeWeWeWeWeWeWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWcWcWcWcWcWcWcWcWcWcWcWcWcWcWcW"bremovesentenceۥVremovesentenceowlis^VremovesipfromlistVremovesquarebracketshereand3additionalplacesonthisVremovesquarebracketshereandtwootherplacesonnextpagfVremovessidbssidservesasuniquenetwork[VremovesuggestedmacnewpoaiddVremovetable22fromline41page127toline8page128Vremovetable23fromline29toline63Vremovetechnology-independeVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVcoperators^WWqWWWWWW@WopposedWoptimize?WoptionWWoptional'WWWoWWWWWoptionallyWoptonsWWWoptonsܯWor-W.WDWFWGWHWIWJW_WaWiWjWkWmWnWoWwWzW{W|W}W~WہWۂWۈWۊWېW۵W۾WWWWWWWW-W.W3W9W:WCW[WcWsW܄WܝWܡWܤWܫWܬWܺWWWWWWWWWWWWW W WWWW+W2W3W;WJWWW}W~W݂WݐWWWWWWWWWW W"W$W%W/W7W;W>WAWIWOWfWgWޖWޫWެWWWWWWWWWWWWWWWWW1W3W4W5W6W7WKWLWbWWbWc86݇W87یW9;WW910.2-g-1>Wa"W$WAWGWIWJWLWOWPWQWRWSWTWUWVWWWZWfWiWۄWۅWۉWۋWېWۓWەW۞W۪W۶W۽WWW WW/W2W:WIWZW^WiWkWyWzW{W|W~W܂W܃WܟWܡWܤWܬWܭWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW[{lnoneneeded#V?V^V`VۏVۺVV'VIVgVhVlVܰVVV=V>VTVcVtV݈VVVYV6VV<VVmissingWaWneeded#W?W^W`WۏWۺWW'WIWgWhWlWܰWWW=W>WTWcWtW݈WWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWFWۺW۾WWWWWWWnWܜWܢWܦWܩWܪWW W%W2W;W=W>WBWCWFW݂W݊WݏWWWWXWZWprogressܥWresolution$WۼWWW W W WܝWܞWܮWWW:WWWW W W WSWtoWW۴WW,W2WunclearۢW۽WW WW-W6W݃W݄W€! ەbA,Append a paragraph, "The following items are not within the scope of this standard: 1. Intra-technology handover 2. Handover policy 3. New security mechanisms 4. Link layer enhancements that are required to support this standard 5. Upper layer enhancements that are required to support this standard",cThe scope section does not adequately address which parts of a communication system are within the scope of this standard, and which ones are not. Additional text may be necessary to explain what IS in scoped2vAInsert with following changes: " 1. Intra-technology handover (Hnadovers across ESSs in case of 802.11 are IN scope of 802.21) 2. Handover policy 3. Security mechanisms 4. Media specific link layer enhancements that are required to support this standard will be carried out by those respective technology standards and are out of scope of 802.21 5. Upper layer (L3 and above) enhancements that are required to support this standard" "wAccepted-ModifiedGQ"csort,WW WsoundsWsourceۍW۶W&WWVWsourceidentifiersourcesZWsouthboundWWWWspaceW-WiW݉WWWWWiWspaceisneededbetween802.21andspecification݉VspacesWWW݉V݉V݉V݉Vfication݉V݉V݉V݉V݉V݉V݉Von݉V݉Vededbetween802.21andspecification݉V݉VWWWWWWWWWWWWWWWWWWWWWWWWWW$W:WCWaWiWܘWܰWܺWܾWWWWW~Wspecificformatforthevalueportionineachtypeofinform~Vspecifically WspecificationW۩W۾WWW WWܟWWWW݉WspecificationoftypeienetworkqosisnotmediaindependenVspecifictaion+WspecifiedWېWW܌WܾWWWWWEW#|p2۴W۽WAWVWvW215reservedVV2006/07ݒW21-06-0460-02-0000-bvW21-06-0609-00-0000-iݓW21-06-0609-isݓW21-06-0609-ismultihopscenariodocnotfoundontheofficiaݓV21-06-0612-03-0000݃W21-06-0612-03-0000-r݃W21-06-0676CW21-06-0691-02-0000-3۽W21-06-0691-03-0000-3۽W21-06-0705-00-0000-lDW21-06-0711-00-0000-iZW21-06-0712-00-0000-iZW21-06-0716-01-0000-r۴W24۽W28W2ndW.W3۴W۽W)W:W319ܵW@W33aW345^W`WIW3gpp۽W4)W1W4-7ލW482CW490SW5۴W5.3.2۴W5.5.5۽W5.8.3۽W525YW6.3;W6.3.4.1.2AW6.4{W615hW621hW63.W637ݜW7ۓW7.3lW7.3.20ېW7.3.21ېW7.3.9.1ݜW7.4.10.1.2ݜW7.4.15.3.3۽W746WW8{W8.3{W8.3.2.4RW8.5.1.1\W8.6ۏWevices with more functionality. 802.21 should allow b0Wo&jk697@action@along@also-andݓare@between@_clear@completely@*current@Sdetails@either@-explained@qgeneric@iOimprove@increase@7isۓit@Citself@Wlines@mean@mihf@'needs@QnotۓWitu/3gppWjhallHWjitterWWjoinWjunezWWjustܾW{WWWkWWkeep"WgWnW\WqWWWWWWkeepitasinformativenVkeepthedefinitionasitrelatestonetworkdiscoveryandlVkeeptwostackspicturesVknowWknowledgeWknownݓWݓWݓW:a5.1.5ܡ5.1.6/5.1.7ܣ5.1.85.2 ۪ܤܥܧܱ015.3ۭܨ35.3.1۫ۮۯ۰,˃456؃ك 5.3.2۱۲۳۴789Xঃਃ!<ᒃ5.4"=5.4.1.1ܫ5.4.1.35.4.1.4ݍ5.4.2.3ݎ5.4.3#۶۹ۺۻܬܭ̓<>?@ݐۃ-.੃"?5.5$ۼ΃A݃ృ#5.5.2x5.5.325.5.4۽$5.5.5ۿσEY%&5.6ЃG/~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW x{done-W.W/W2W4W5W8W:W>WAWBWIWLWMWNWOWVW[W\W]W_WaWdWkWlWnWpWqWtWuWvWwW|W}W~WWހWށWނWރWބWޅWއWވWފWދWތWލWގWޏWސWޑWޒWޓWޖW1W2W5W=W>W?W?WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWdWWYWeeditordisagreesJVhVVVVdVVYVeditorJWhWWWWdWWYWiWWۏW۴WW-WܑWܵWWWWWLWzW}W,W>W@WBWCWކW2W=WitodoVVۏV۴VV-VܑVܵVVVVVLVzV}V,V>V@VBVCVކV2V=VB kA"Alternatively, MIH protocol messages may be encapsulated using a lowr layer (L2) or a higher layer(L3 and above ) transport". @A mAccepted-ClarifiedvAChange as follows: "Alternatively, MIH protocol messages may be encapsulated using a lower layer (L2) or a higher layer(L3 and above ) transport". @A wAccepted-Modified{k) done 2006/09/21EDasFSubir^Technical, Non-binding_32`31a5.8.2b`Need to verify the correctness of this statement and if not always true, it should be deleted. cl"3GPP system already broadcast information regarding other Radio Access Technologies". Is this always true? d244g2438vrChange as follows: "3GPP system has ability to broadcast information regarding other Radio Access Technologies". wAccepted-Modified{k) done 2006/09/21#EDasFSubir^Technical, Non-binding_47`20a6.3.2ba6.3.2ba6.3.2bmat....47!cportion>W9WportsWpos WWWW Wposition6WpositioningWpossibilitywW3Wpossible:W|WW WWWWWWWWW WW!WkWWpossiblyKWܡWWpotentialrWWWpotentiallyWWpowerWmWpowerfulWpppW݋Wpre-definedtWvWWpre-establishmentrWpredefinedޖWpredictive^WWpredictiveeventspredictiveeventsexpressthelikelihoodoVpreferredlinkidentifQWeWpreferredpoaidentifiQWeWpreferredpoaidentifiisnotneededifitispartofpreferreQVeVprefixW-WpreparationۅWWWprepare\W^WaWcWW|WWWWWWW@W@WWWW'<.kneeds۳WݓWWWneitherWnetvWWWnetworkWWWW}WWnetworksWWWWnformationWnmsvWno۴WWWWWVWWWnoneedtodefineanidfortransactionidasitisinthefVnoproposedcorrectcallflowthistimeVnospecifictextproposalVnodedWWnodesݓWWnon-3gppWnorWnormative۴WWWnormativedoesnotmeanmandatoryinfactschemasupportisVnot#WAWAWAWbWbWہWہWہWہWہWہWہWہWہWہWہWہWW|WWWW|WܸWݴWݻW-WdWjWonZWjWkWmWnWoWzW{W|WWݴWoneZW\WonlyZW\WWCWW+WoperationsaWoptionܬWoptionalWOWoptionsWoraWjWkWmWnWoWuWzW{W|W}W|WWdWc /vr1۴WWr1/r2/r3Wr3۴WradioWradiusJW WWradiusnas-port-typeisgonnabeavialablefor802.16Vradius-iana WrangeWWrateW-WWreallyWWWreason{WގWWreceiveWreceivesQWRWSWTWreception"WrecievingݓWrecipientlWWrecommendations!WreevaluateRWref۴WreferIWfWW`WݽWWW>WBWCW\WjWWWWWWWW>WWWWreferto21-06-0641-01-0000-cserviceflowppt>Vreferto21-06-0642-02-0000-iserviceflowpptBVrefertocomment102Vrefertocomment552fortableoflinklayerparametersIVrefertocomment588asithasspecificresolutionnoclearVrefertocontrib21-06-067621-06-064121-06-0642CVrefertocontribution21-06-0677-00-0000-hflow\Vrefertocontribution21-06-0686-01-0000mihhandoverprocedV?ctarget"W$W*WrWWWtarnsportWtcm>Wtcp/ipwWtear-WWiWteardownWtechnicalnWtechniquewWxWyWzW{W~WWWWWWtechniques WtechnlogiesWtechnolgy*WtechnologicalWtechnologies$WېWWYW[WWWWWWWW WW#WWWWWWWWWWWtechnology-independe W0Wtell_WaWۈWtense7Wtenseconsistency7Vterm W,W.W:W;WW-WWterminalۂWۋWۏWterminalsۋWterms?W@W۲W۽W:WWWterrestrialWtest%WtextW W,WAWKWeWiWrWsWuWWەW۾WWW{WWWWWWW݂W݄WWWWWW W W W W WWW"W#W$W&W+W,W-W2WctheinformationcanbeobtianedeitherbytlvorschemahoweܬVtheinformationrepositorycanbepresentlocallyatthemobVtheinformationtransferoccursreadsbetterۨVtheinterfacesegmihsapexposedbymihfarenottechnolog0Vthejustificationforack-rspbitisinsufficient}VthekeyprimitivesdefinedaspartofmihsaparedescribedیVmihsaparedescribedیVیVesdefinedaspartofmihsaparedescribedیVیVcationforack-rspbitisinsufficientyVyV0V0VVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨVۨV1 sanjeevࠃࡃࢃding_115`13a8.3..3.12456 2006/05/14*EDasFSubir ^Technical, Non-binding_55`20a6.3.6b[Should be replaced by "Value" or provide supporting text why it is "Additional Parameters" c3Why is it additional parameters instead of Value? d445g2457 2006/05/14+EDasFSubir ^Technical, Binding_115`13a8.3..3.1alue" or provide supporting text why it is "Additional Parameters" c3Why is it additional parameters instead of Value? d445g2457 2006/05/14+EDasFSubir ^Technical, Binding_115`13a8.3..3.1rs" c3Why is it additional parameters instead of Value? d445g2457 2006/05/14+EDasFSubir ^Technical, Binding_115`13a8.3..3.1~)bscenarios#W?WWschema#WAWiW|WܬWݾWݿWvW}WހWށWނWރWwWxWyWzW|W~WWWWW WWschemaeWschemaecanbeusedtomapouttypesofdataandtheirVschemeܰWscn-rspNWWWWWWWWWWWWscopingWWsdo WsdosܸWܹWsduUWWRW܌WseamlessۻWsecondJWۤW4WHW܉WܞWWsectionWW!W'W1W2W3W4W6W7W8W9W<WBWCWEWYW]WaWbWpWۄWWWWW;WAWBWRWSWYWcWhW܁W܂WܕWܗWܘWܙWܛWܩWܪWܶWܷWWWWW{W݂W݄W݌WݳWWWWWWWW W W W6WNWXWYW\WlWnWvWsection5.6.2.1mihlinksapshouldberemovedentirely6Vcissoft-handoverlimitedtohandoverbetweenhomogeneousacc1VisgenertedWisn'tWisn'tthisalreadydoneduringtheprocessofregistrationVVV\ ctheWWWWWW  4  =  33\  c  f  33      33  33ruction 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 4)bdefineAW۔W۟WWAWBWYWhWܬWWWWVWWWWWWWW WWW;WVWWWWWdefineanextensibilityprocedureVdefineandmakedefinitionsinsection6.3.4.1.4and6.3.2cAVdefineandmakedefinitionsinsection6.3.4.2.1and6.3.2cBVdefineaporbasestationidentifierfor3gpp/3gpp2VdefineiflinkeventsareenvisonedtobeusedformiphandoVdefineintra-roamingVVob0x00000001ܚW0x00000002ܚW0x00000100$W0x1fffffff$W1WJWۉWەWWHWRWSWTWUWVWWWYWuW|WܖWzWݒWݗW,WVWpWށWރW1W6WXWwWyW|WWWWWWWWW7W;WwWWWWWWWW"W"WtableofcontentsassectiontitleV1addthefollowinglinesSV1changethetypeofthenetworkaddressinformationV1createanewiewiththefollowinginformationatline38V1dividetheflowintotwoinafigurelocalandremotecomm7V1dividetheflowintotwoinafigurelocalandremoteinfozV1eitherremoveorprovidedetailsexpeciallyonall4primiV1failureܖV1ieeestd802.111999editioniso/iec8802-111999informatpV1mihgetstatuslrnetworkclientgetthestatusoflinksV1movetheconceptofhorizontalandverticalhandoverstosV1vhaveCWQWRWSWTW-WWWݜW"WWWWWhavingWWWheaderWWhelp?Whelps?WhenceWhereWW Wheterogeneous1WWhighWhigherQWRWTWWW?WhnadleWhnadoversەWhoczWW!WholdWhomogenousWhopݓWhorizontal۫WW,WhowܛWݜW\WWWWhowever WhtmlHWhttpHWhubsݜWiWWianaWW Wicmpv6WidݓWWWWWWWidentifiedWW-W|WWWWidentifiedasanissueneedtounderstandwhatisthecontex|Videntifiedasissue42-V-V-Vissue60nosuggestedremedyVVVVWimportantWin0WZWەW۪W۳W۴W۵W۷WWWW W%WRWWWܗWܬWܾWWWWWWWWW2WzW{WWIEJinFLeeGMember^Technical, Non-binding_83`11a 7.4.1.1.2bfined in the last version of the draft: i. In step 7, there is a MIH_Switch.Request, but a MIH_Switch.Response is missing ii. In step 8, Link_Up is used as REQUEST/RESPONSE, but in section 7 of the draft this primitive is defined as an INDICATION primitive iii. In step 14, the use of MIH_Handover_Complete is not consistent with the definition in the draft. The use in the Annex is local, but in the draft it is defined as MIHF(NeBwtwork) <> MIHF(Network). iv. In step 15, a Link_Teardown.Request is used. This primitive is not defined in the draft. ed874g2221vIssue identified and assignedwRejected 2006/09/15 2006/04/30F 30EJinFLeeGMember^Technical, Non-binding_83`11a 7.4.1.1.2b.4.1.1.2b cisPWSWYWZW[W]WgWhWjWkWmWtWuWzW{W|W܂W܄W܅W܆W܋W܋W܋W܋W܋W܋W܋W܋W܋We length field is set to the value '1' and the remaining 7 bits of the first octet indicate the number of octets that are appended further. The number represented by the 2nd octet and subsequent octets of the length field indicates the total size of the value field. "@AR 33W  33] r 33Rc Case 2 description is incorrect.boctets)WHWTWUWVWWWwWWݗWuW1WWWWWWWW@WlWoduWoerator@WofWWWW W#W?WAWGWIWJWLWPWQWSWTWVWWWZW`WcWdWfWiWlWpWsWvWwWxWۅWۉWېWەWۖWۗWۘWۚW۞W۠WۦWۧW۪W۳W۴W۶WۻW۽WWWWWWW/W2W3W4W5W:W<WHWQWRWSWTWUWVWWW_W`WhWiWjWkWlWmWvWwWyWzW{W|W~W܀W܄W܅W܌W܍W܎WW܎W܎W܎WW܎W܎W܎WܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘWܘW%battributesZWiWsWaudioۖWWauthenticated#Wauthenticating#WauthenticationWavailabilityAWWWavailable#WAWۘWW#WHWܡWWWW%WWWWW8W>WuW|WWavialableWbۀWYW0WWWbrelaysVbackRWtWbackbone}Wbandwidth>WbaseWbased WAWOWQWpWWTWUWVWWW0WWWWWbasicAWuWbasicallyWWWasicAWWbasicallyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWIbtypeAWJWLWۉWېWYWkWmW|W܄W܍WܚWzWݺWWW]WaWtWWހWނWބWޅWފW1W6WqWrWtWwWyWWWWWWWWWWWWW7W8WVWWWWWWWWtypedescriptionlengthvalue1VtypedesctiptionlengthvalueހVtypehdrtlvmihfid0x00000001ܚVtypehdrtlvsessionid0x00000002ܚVܚV0001ܚVtypehdrtlvsessionid0x00000002ܚVtypemimetlvvariableamimetypetlvanoctetstringforaހVނVtypesizelengthdescriptionvalueހVނVtypelistdWtypes?WAW_WjWmWW=WJW`WdWܤWܷWܾWWhWݖWWIW[W^W޽W޿WWW,W.W]W_WߛWߝWWWWW0WtypicalWtypicallyAWܤWܱWݎWWW޿WW.W_WߝWWW-SbtoW W"W#W$W(W)W*W?WAWCWGWIWJWLWOWPWQWRWSWTWUWVWWWZWcWdWeWfWiWlWpWrWsWtWvWxWۄWۉWۋWېWۓWەWۖWۚWۭW۲W۳WۻWWWWWWWWWW#W)W,W/W2W7WDWEWHWNWTWUWVWWWYWZW]W^W`WaWiWkWlWmWoWtWwW|W܂W܅W܆W܋WܑWܒWܔWܖWܡWܤWܱWܾWܾWܾWܾWܾWܾWܾWܾWܾWܾWܾWܾWܾWܾWܾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWjinformationWܾWdWjWWtWWinsteadWgWWWintendedWintentionWinter-technology?Winter-technologyhandoververtical-handover?Vinteract,Winterfaces,WinterfereWinternetܾWinterpretedܾWWintoܾWintra-technology?Wintra-technologyhandoverhorizontal-handover?VipܾWݍWis"W?WZWWWWWWWWWWWWWWWW>WTWit's>Wits W,Wjust,WkeepdWkeepthenewpoainformationdVknow WhWknown?Wl-shaped,Wl2,Wl3,Wl4,WlastWlayer,W>Wlayers W,W>Wleft>Wlength|Wlike>WlinkWWW W>WKWlistWlmakeWlmake2differentdiagramsoneforlocalcommandsoneforreVlocWܽWݻWlocalWWgWlocatedܶWlook݄Wlower,W>Wbaddanewsection7.3.1calledlinkeventidRVaddanewsectionassuggestedin21-06-606-00-0000locinfoVaddanewtablecalledscanrequestinfocontainingthefollowmV;,baddrefertotable26inannex4inthecommentsfield@aaddthefollowingintheannexa4atthebeginning@added@ladding@*adoptsuggestedchange4in21-06-0522-04-sessioidentifier@advertisement@~agreed@8also@Fan@*analyze@n@*analyze@greed@8also@Fan@*analyze@ze@tifierdoc@~agreed@8also@Fan@*analyze@ogous@logous@*analogous@o@Fan@*analogous@also@Fan@*analogous@*analogous@*analogous@rcmacmobilenodeݜWAWBWCWDWEWFWGWHWJWSWTW[W]W^W_W`WaWcWgWhWmacmobilenodeandlinkidentifiershouldbereplacedwithoneJVmacmobilenodeandmacnewpoaarenotneedediftheyarepart_VcVmacmobilenodeandmacnewpoashouldbereplacedwithoneunifBVGVHV[V]V^VmacmobilenodeandmacoldpoashouldbereplacedwithoneunifAVmacmobilenodeisnotneededifitispartofnewlinkidentifiSVTVmacmobilenodelinktypeandmacnewpoashouldbereplacedwitDVmacmobilenodelinkidentifierandmacnewpoashouldbereplaceݜVmacmobilenodeshouldbereplacedwithlinkidentifertlvCVEVFV`VaVmacmobilenodeshouldbereplacedwithlinkidentifiergVhVmacnewpoaݜWBWDWGWHWRW[W]W^W_WcWmacnewpoaisnotneededifitispartofnewlinkidentifierRVmacoldpoaAW U{kdoneݺVݽVݾVݿVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V VVVVVVVVVVV 2006/08/13 2006/04/28 "c"theLength", "defiite" d765g2430 2006/08/13 2006/04/28 ݺE YoshihiroFOhbaGMember^Technical, Binding_118`57a8.4.1b'Network Identifeir should be Link Type.c'Network Identifeir should be Link Type.d773g2373wAccepted 2006/08/13 2006/04/28 d d d ^Technical, Binding_118`65a8.4.1b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc*TLV for Link Identifier should be defined.d774g2374iWolfgang GrtingjkChange the Table as defined in 21-06-606-01-0000_loc_info_over_tlv.doc section 3 and adpot new identifiers.pes with Link Identifier.a7.3.11.1dB7.3.11.3Q7.3.12.1C7.3.12.3R7.3.137.3.13.1D7.3.13.2?7.3.13.3S7.3.147.3.14.1mE7.3.14.2ޖ7.3.14.3T7.3.15.1F7.3.15.3U7.3.16.1G7.3.16.3V7.3.177.3.17.1H7.3.17.3W7.3.18.1c7.3.18.3d7.3.18.4e7.3.19.2ۍ7.3.19.4f7.3.20ې7.3.3.1I7.3.47.3.57.3.7a7.3.7.2l7.3.7.3n7.3.8ۃ7.3.8.2G_7.3.9܃7.3.9.1ݜ7.3.9.3O7.4у7.4.17.4.1.1.2ᙃᧃ7.4.1.2[7.4.1.2.2I7.4.1.2.37.4.10]7.4.10.1.2ۋP7.4.10.1.3ݭ7.4.10.2.2Q7.4.11^7.4.12_ݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮ!SpschemavWseamlessWsecond݃WsectionۅWۏW۽W:W;WRW{WݜWvWsection8.6alreadyremovedbyanothercommentۏVsection/page/lineWsectionsېWseeSWܾWEWsee195editor'snotesEVseecomment490SVseem۽WseemsW;WWsend݃Wsentence۪W.W݃WseparateDWۓWserverݒWݓWshall۴Wshape݃WshouldۓW;WWYW2W#WshouldbetechnicalV#Vside݃Wsimplify;WsipލWsoۓW;Wsolved;WsomeۅWWܥWaW{WsomeoneneedstoproposedetailsforthechangeaVsomeoneWWsource/destLWMWspec݃WspecificܾWݛWsplitܾWsriniܾWstatus܁WstronglyWsubmitݜWsubmitted;Wsubsections{WWtableDWhWیWۓW۽WRWW\Wtableexplainedbycomment621hVtable-6)WtbdݛWtechݛWtechnicalWW|{bsuggestedsuggestedmacnewpoaiddWsuggestednewlinkidensuggestednewlinklistۋWsuggestednewpoaidenttۂnۂnۂnۂnۂnۂWWWWWZcreponse>WWreportېWW|WވWޖW5WtWvWWreporting*WreportstWvWW?WrepositoryWWrepresentWWWWrepresentationAWBWWWWWWWWWWWWWrepresentedzW{WܬWW\W]W^W_W`WaWbWcWdWeWWWWWlWWrepresentsWqWreques/responseWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW:W;W<W=W>W_WaW޸W޹W޺W޻W޼WrequestingW\W}EBenjaminFKohGMember^Technical, Binding_42`7a6.3bGive example operations of how the Media Independent Information Service can be utilised. Suggested text to be added is given in 21-06-0645-00-0000_MIIS_Deployment_Example.doc Add this to annexc`No guidance in draft on how the Media Independent Information Service can or is to be utilised. d312g2211p+- need to change AAA to MIH reg in the fig.ng sytsem startup, during link switching etc.wAccepted-Modified{c) instructions unclear 2006/09/01 2030/04/06Marked}EBenjaminFKohGMember^Technical, Binding_42`7a6.3bGive example operations of how the Media Independent Information Service can be utilised. Suggested text to be added is given in 21-06-0645-00-0000_MIIS_Deployment_Example.doc Add this to annexc`No guidance in draft on how the Media Independent Information Service can or is to be utilised. d312g2211p+- need to change AAA to MIH reg in the fig.ctherearetwomihgetinforesponseinthisflowchart=VtherearetwomobilenodedefinitionsVVtherearetwomobilenodedefinitionsthedefinitiononlineۦVthereisnodefinitiononhowthelistofeventsiscreatedVthereisnodescriptionofthisfigureandwhysuddenlyweiVthereisnoinformationtowheretheconfigurationparameterjVthereisnomechanismtoaskforaspecificlocation/interesVisnomechanismtoaskforaspecificlocation/interesܘVܘV_ ނbA Table 23 -- SPARQL Query TLV Value response parameters Format ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | Type | Size Length | Description Value | ---------------------------------------------------------------B------------------------------------------------------------------------------------------------------| | TYPE_MIME_TLV | Variable | A MIME Type TLV An octet string for a MIME type to specify an XML a format | | | | of SPARQL Query Result. When this TLV is | | | clinkparameterschangeindicationcanonlybegeneratedwhenޖVlinkparameterschangeshouldberenamedlinkparametersrepVeshouldberenamedlinkparametersrepVVVw'cisWWWWWWWW WWWWW"W$W%W'W*W,W.W2W>WAWOWVWYW\W]W_WaWdWlWnWpWqWvW|W}W~WWބWޅWއWވWގWޏWޖW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWO bAHandovers due the mobile node movement may be Horizental (intra technology) or Vertical (Inter technology) as defined in section 6.3.1. This specification facilitates handovers across hetrogenous access technologies by providing timely infomration about changing link conditions and/or information about different available access networks in a given area when traversed by the MN. In addition, Handovers command may be delivered to a MN forcing it to change access technology.cAHandovers due to the mobile node movement are facilitated by providing timely information about changing link conditions and different access networks in neighboring micro and macro cells. The section needs to beefed up and remove the undefined terms: micro and macro cells.d98g2224vDefine horizontal and vertical handovers in definition section (take definition from section 6.3.1) Adopt the above text. Clean up section 6.3.1 and just reference the above terms.wAccepted-Modified0Y csuggestsۋWWWsuitableۋWWWWWsuitedoWsummarize:Wsummary>WsupeflousWsuperfluous۹WWWWWNW^WsuperfluousphraseVsuperfluoussegment۹VVNVsuperfluoussentence^VsuperfluouswordVsuperfluouswordsVsupervisionޓWsuppervisonޓWsuppervisonsupervisionޓVsupplyۋWsupportRWYWWjWrWWWWWWWWWWWWWSWWSWSWSWSWSWSWSWSWSWSWSWSWSWWWWWWWWecmacroWmadeWtWWmainWNWmainly۽Wmaintained WmaintainingWmaintainingtwoformatscomplicatesmessagestructuresandVmaintains۳Wmajor8Wmake(W)W۔W۰WWWW W&W'W5W>WWWWWWmakeindefinitearticleformconsistent۰VmakesfW݈W!W<WzWmaking*WۅWW?WtWWWmanageWmanagedWWWWWWܴWݏWWmanageWmanagedWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW qcAThe MIH_Link_Up Indication includes the field MobilityManagementProtocolSupport , defined as bitmap. In the draft there are only 2 bits reserved for that purpose, and the following protocols are supported: 0 : Mobile IPv4 with FA (FA-CoA) 1 : Mobile IPv4 without FA (Co-located CoA) 2 : Mobile IPv6 3 : Mobile IPv6 with DHCPv6 4 : SIP This definition excludes other possible mobility management protocols, like Network-based Localized Mobility Management (NetLMM), but also open to others. 5B : NetLMM @A*  33  *d826g2219vBThis field actually refers to Type in TLV as opposed to a bitmap.wRejected 2006/09/21 2006/04/30EVidalFAlbertGMember^Technical (was Editorial)_140`17a Annex A-1bQThis figure should be either modified or removed, because it can cause confusion.cusion.c>`‚a`fۡIUۃc؃Z‚bېA,ލqःฃʃS_mኃ‚c+ۗ$D˃كݜࢃσ8‚dTۛރQܖރ!'fhy,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,cto"W#W*W+W?W@WDWGWIWJWSWZWiWlWqWsWtWwWۃWۄWۅWۉWۋWۏWېWەW۩W۪WۭW۳W۴W۶WWWWWWWWWWW'W-W0W1W7W:W;WCWDWEWHWIWNWPWQWRWTWUWVWWWYWZW^WiWjWkWlWmWtWwW{W|W܂W܄W܆W܋WܕWܖWܚWܡWܤWܥWܧWܾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW  dÃ`ݹÃpÃwÃxÃÃà jÃ0ފÃ@ݺÃPYÃ`ދÃpyÃzÃތÃÃ{à Ã0|Ã@~ÃP܂Ã`kÃp]ÃÃÃÃލà }Ã0lÃ@ÃPmÃ`~ÃpJÃÃÃZÃnà ܀Ã0Ã@ގÃP4Ã`ÃpހÃ܁ÃpÃݽÃà ށÃ0Ã@ނÃPރÃ`ÃpݾÃÃݿÃÃà \Ã0Ã@)ÃPaÃ`[ÃpÃ\ÃÃ]Ãà ^Ã0Ã@_ÃP`Ã`܃ÃpaÃbÃcÃ܄Ãà bÃ0dÃ@܅ÃPeÃ`cÃpÃ܆ÃdÃfÃeà *Ã0Ã@܇ÃPiÃ`qÃpgÃhÃޏÃÃބà ޅÃ0Ã@ÃPrÃ`OÃpÃ}ÃÃۏÃà ކÃ0-Ã@iÃPÃ`ÃpcadoptݵWkWadoptmihregistrationkVadopted>WadvanceۅWadvantages WWadvertise}Wadvertisement$WޏWWadvicedܖWadvisoryWaffectWafterۅWۮWfWLWݿWWW>WWW*WWagain+WWagainst݃WWagent"W%WޏWagnosticܭWܰWagreedܕWaidWWWWaimingWair۽W}WairportWaksingWal݆W݆W݆W݆W݆W݆W݆W݆WQcsoۄWۅWۋWېWWWWWW W W8WWWWsocketsrWsoft-handover1WsoftenOWsoftenstaticastonottoimplylimitationOVsole۶W۶W۶W۶Wsole۶W۶WsoftenstaticastonottoimplylimitationOVsole۶W۶Wole۶W۶W$0bandW W"W#WAWDWOWPWTWUWVWWWZW`WeWfWlWpWqWsWvWwWxWۉWېWۘWۣW۳W۶WWWWWWW#W)W,W4W5W7W:W;W<WAWBWRWVW`WgWhWtWzW{WܕWܟWܡWܤWܨWܬWܾWWWWWWWW WWWW&W'W)WfWzW݃WݎWݕWݖWݗWݸWWWWWW WWW W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W WuSE Ulises Olvera^ Editorial_115`6a8.3.3.1bl"This field is intentionally kept reserved. When not used, all the bits of this field are to be set to '0'."cReword the description entry of Table 18 "This field is intentionally kept reserved. In un-used case, it all the bits of this field are to be set to '0'."d741g2231{k) done 2006/09/2118 E Ulises Olvera^ Editorial_115`59a8.3.3.2b1"...and coordinate the payload that is embedded."cWMissing a "that" in the following sentence "...and coordinate the payload is embedded."d747g2232psuperceded by 746{l) none needed 2006/09/21E Ulises Olvera^ Editorial_129`18a8.5b"...in the sections below."cInterchange "below sections."d820g2235{k) done 2006/09/21 E Ulises Olvera^ Editorial_141`6a Annex A-1bnnex A-1bnnex A-1bnnex A-1bal_115`6a8.3.3.1ated? d873g2399 2006/05/14 2006/04/28 Figure 30E Ulises Olvera.wkthisshouldbetrueforeventsandcommandsaswellatransaݓVthistypeisusedtoinformwhattypeofcodingisusedwith|VthoughOWthroughdWWWWthroughout۳WthusWWtimeWtimesvWWWtlvCW|WpWuWWWWWtlvsWto"WAWۓW۳W۴W|WݓWW)W-WuWvWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWYWvWWWWWWtransactionݓWWtransmissionWtransportWtrasport Wtrasportprotocolsliketcpor802.11machavetheirownmet VtreewWxWyWzW{W~WWWWWWtreeswWxWyWzW{W~WWWWWWtriggerWWہWWmWnWoWzW{W|W}WWݻWoWused|WWݳWuseful<WjWijbsuccessUWܖW~WWsuccessfulxWVWWsuccessfullyWsuch W#WAWDWsW۶WWWYWܬWܾWQWWW[WtWW>WuWWWsufficient#WAWsuggestۗWۜW&W W)Wsuggesttodeletethissentence VsuggestusingadditionallyinsteadofalternativelyۗVsuggestedZW}WݒWݓWݜWsWWWWAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWYW[W\W]W^W_W`WaWbWcWWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢW cBeh "or" in the following sentence ".... could have been previously obtained of it could be readily..."Sd877g2239{k) done 2006/09/21 E Ulises Olvera^ Editorial_141`20a Annex A-1bAa) "towards" b) "relays" c) "towards" d) "Mobile IP registration might be triggered now." e) "....using a MIH Handover Complete.Request" f) "A Link Tear Down is used to release resources." g) "A Link Tear Down response is issued ..." h) "issued" i) "issued" j) "issued" k) "towards" l) "towards" ccregister" with "registered" in the following sentence: "(which previously register for the ....)" Also, their is inconsistency with the use of "MIH User" and "MIH user". See lines 5, 6 and others on that page. On line 12 of the same page: replace "of" witthe bits of this field are to be set to '0'."E Ulises Olvera8badvertisementNW$WޏWadvi WafterۮWW`WfW4W5WHWMW2WWWWWWWagent"W%WޏWaggregates*WagnosticAWAW%WޏWaggregates*WagnosticAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWAWicAWAWticAWAWAWAWAWticAWAWAWWagent"W%WޏWaggregates*WagnosticAWAWWagent"W%WޏWaggregates*WagnosticAWAWWagent"W%WޏWaggregates*W*WޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏWޏW\ bA[Insert the 'SuppotedISQueryTypeList' , page 83, line 1]: MIH_Capability_Discover.response ( SourceIdentifier, DestinationIdentifier, SupportedEventList, SupportedCommandList, B SupportedISQueryTypeList ) -------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | Description --------------------------------------------------------------------------------------------------------------------------- )bcOThe section title "Media Dependence" is confusing and does not make much sense.d240g2251vChange the title as suggested.wAccepted{k) done 2006/09/21 2006/04/24*EQiaobingFXieGMember^Technical (was Editorial)_31`64a5.8bA4Make the following change to The MIH Function aggregates disparate interfaces with respective media-dependent lower-layer instances (media-dependent service access points) into a single interface with the upper layers (the MIH SAP), making the inter-media differences fully transparent to the upper layers. 4@Af 33    TT2  3 33fcAThis statement "...making the inter-media differences fully transparent to the upper layers" is unrealistic (hard to achive) and also not necessarily an 802.21 objective.@A  33d241g2252v1g2252v>cd, and should as suggested below. lnclinkdetectedindicationthedetectionmaybeeventhrought?VlinkdownaddothercausesauthenticationfailurebillingfabVlinkeventderegisterconfirmshouldbelinkeventderegisteVlinkeventregisterconfirmshouldbelinkeventregisterreVlinkhandovercompletecommandcanbeusedforupperlayertVlinkhandoverimminentmayVlinkidentifierismissingintheparametersNVOVmayVsedforupperlayert4VlinkhandoverimminentmayVVsedforupperlayert4VlinkhandoverimminentmayVVsedforupperlayert4VlinkhandoverimminentmayVVsedforupperlayert4VlinkhandoverimminentmayVV $vdo۔WWWjWWWWWWWdothisforalloccurencesinthedraftVdothisforallsuchoccurrencesinthedraftVdoingݓWWWdomainݓWdon'tWdon'tneedadditionallinktypeundermihparametersforcapVdont&W>WWdontneedtoaddeachandeverytechnologyexplicitlycdma20&VdownWdraft\W WWWWWWWWWWdriveWdrop"Wdropthereservationpartbutkeepthequerypart"VdroppedWdueWduplicateWduring{Wdynamic?We"WWWWWWeach۔WWWW&WeditorWއWWWeditortoexaminereplacingmihwithmihfwhereverapplicablއVeditorial\WWWeffectWWeffective?WefficiencyWeither3W"WelsewhereWWembeddedZWenable۳WݓWenablesWenabling"Wfcnms8WkW#WWWno+W?W@WpWvWۅWWWDWEWjWܓWܖWܚWeW}WWWW WW2WYWWWtWuW|WWWWWWWWWWWWWWWWWWWWWWWWWWW W!W$W<WIWzW{WWWWWWWW#WnodetaildescriptionandusageofthemihnmssapprimitiveVnoformatforthesynchinformationisdefinednorareanyrVnoguidanceindraftonhowthemediaindependentinformatio}V}V}VVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVsponseܙVnospaceforexpansionofmihtlvencodingsVnodeWWۉWۏWۦW W.W3W4WܝWܡW+WwW{W|WݏWW"W#W$WZWW:WW+WTWnon-3gppXWcGAdd "s" to Commands in the line that quotes "Link Command originate..."d290g2249i Eunah KimmAccepted{k) done 2006/09/21MarkedE Ulises Olvera^ Editorial_41`2a6.2.4b2"...in this section are provided in the Appendix."cNAdd "the" in the following line "...in this section are provided in Appendix."d301g2250{k) done 2006/08/29 E Ulises Olvera^ Editorial_42`62a6.3.1b["Depending on the type of mobility, support for different types of information elements..."cAdd a comma after mobility because without a comma the sentence might be misleading "Depending on the type of mobility support for different types of information elements..."d320g2251{k) done 2006/08/29 E Ulises Olvera^ Editorial_44`1a6.3.2b/"However, for most part, dynamic link layer..."c`Add a comma after "However" and "part" in the line "However for most part dynamic link layer..."d341g2252{k) done 2006/08/29 E Ulises Olverav ldÃpސÃÃޑÃÃޒà ܈Ã0܉Ã@܊ÃP܋Ã`sÃp܌ÃÃޓÃÃܚà ܍Ã0ۀÃ@tÃPÃ`5ÃpÃ6ÃÃÃà wÃ0ۉÃ@ÃPÃ`ÃpÃÃ=Ã>Ã?à Ã0Ã@ÃPÃ`DDoes the AP get Link Tear Down or Handover complete indications before it is disassociated? Itcspans۪WsparqlqW~WWWWWspecwWۀWWW[W|WWWspecial:Wspecially WspecifedݽWWݽWݽWݽWWspecial:W:WWWWWWWWWWWWWecially WspecifedݽWspecific'W-W_WaWWW W$W:WCWaWiWܘWܰWܺWܾWWWWW~WWWWWW1W6W>WOWWWޥWޫWWWWWEWKW߃W߉WWspecificformatforthevalueportionineachtypeofinform~Vspecifically WspecificationW۩W۾WWW WWܟWWWW݉WWnWކWޚWW W:WxW߶WspecificationoftypeienetworkqosisnotmediaindependenVspecifictaion+WspecifiedWېWW܌WܾWWWWWEWWWOWޖWޚWW W:WxW߶Ww )cthelengthdoesnotmatchthetlvrepresentationofsectionAVBVthelengthencodingwhenvaluefieldisgreaterthan128is+VthelengthfieldisimproperfortherequestthereisnoaddVthelengthoftheisquerytypelistissettovariablebut|VthelinetVthelinkdetectedismissingfromthelistofprimitivesSVthelinklayerparametersdefinedheremustnotbeexamples`VthelistofparametertypeneedstobecompletelydefinedbyYVthelistofsap'sisnotcompletesincelsapandcssapareVthemappingisnotfullybespecifiedintable24p145EVthemayrespectingusewiththesidisnotmeaningfulhowisVthemeaningoforasystemisunclearVthemihcommandconfirmisaddingnovaluesamecanbedone#VthemihconfigurerequestisusedtocontrolthebehaviorofkVthemiheventregisterandmiheventderegisterrefertotheVthemihfunctionheaderconsistsofatwopartsonewithfix+^technicalWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W1:vin݃WݒWݓWWW"W*W,W/W4W5WOWdWnWޏW\WfWWWWWWWWWWWWWWWWWWWWW W WWW W4W>W?WVWjWmWnWWWWWWWWWWWWWWWWW#Wincaseofmobileipv4agentforeignagentadvertisementޏVinfirstfewlinesundersection5.8uselanguagetoclearlynVyݓWintermediateݓWintoZWܗWinvestigateWW;Winvoked{Wip۵WisBWۈW۪WWWW W@WܗWܰWWWWW W2W;W{W݀WݓWݜWݳW4W5W6W7WSWnWissue'WuW۽WܯWWWW W WWW0Wissue1ܯVissue34 Vissue38۽Vissue40VissuesZWSWitێW۵WWܗWWݠcrfcW:WrightWݿWWrncWroamingۻWtWuWW<WrolefWgWhWiWWroles>Wrollback܃WrolledWroom'W'WWWWWWWWWWWWWWWWWWWWWWWWWWteWrouterW:W+W"W$W%WޏWrouters:WrowWrrcCWrregisterrWWݲrttWWW Wrules W W WWrunWrxlevncellFWGWHWIWJWWWWWWWWWWW3W4W5W6W7WdWeWfWgWhWskWWWWWWWsafeWsaidxWsalientܨWsamݛWsame+WېWWWWW W.W/W:WIWZW܄W܅WܠWܩWܼWWWWJW[W~WWWWWWBWKWjWީWWWIW{fkktrnsactionݓWtrue#WݓWtryWtryingWtwoݓWWWWWtype|W)WuWWWWYWWtypesWWumtsWunclear:WunderrWunderstandOWwWxWyWzW{W~WWWWWWWunicastWupWvWWWupdatingWupgradeWupperWWurlWurlsWuseuWwWxWyWzW{W~WWWWWWWWWWYW~WWused|WWWUWusefulgWWWuserWusersWWWWOWOWOWOWOWOWOWOWOWOWOWOWhZ{kWWWWW W"W(W)W*W+WDWGWIWJWLWOWPWQWRWSWTWUWVWWWZWcWdWeWfWgWiWlWqWrWtWwWxWۀWۄWۅWۉWۋWۍWێWېWۓW۔WەWۖWۗWۘWۙWۚWۛWۜW۝W۞W۟W۠WۡWۣWۤWۥWۦWۧWۨW۩W۪W۫WۭWۮWۯW۰W۱W۲W۳W۴W۶W۹WۻW۽WۿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWW#W$W)W,W.W/W0W1W2W3W4W5W6W7W8W:W;W<WAWBWCWDWEWGWHWPWQWSWTWUWVWWWYWZW]W^W_W_W_W_W_W_W7W8WcofWWWWWW W WWWW"W$W%W&W'W*W,W-W/W4W5W>WIWNWYWqWtWvW}WWޖW1W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[WstݾGMember^Technical, Binding_128`24a8.4.2.24b%Change "4: Extended Schema Content"c!Value 4 description is incorrect.d816g2383wAccepted{k) done 2006/09/21 2006/04/28MarkedݿE YoshihiroFOhbaGMember^ Editorial_128`45a8.4.2.24b8Insert: "Table 24 -- Extended Schema Content TLV Format"c)Table 24 is missing right after Table 23.d818g2384{k) done 2006/08/29 2006/04/28 E YoshihiroFOhbaGMember^Technical, Binding_129`16a8.5bAAdd the following text in Section 8.5: "Although the subsequent subsections specifies TLVs to be carried in the MIHF Payload part of each MIH message, any MIH message generated by a primitive that has Source Identifier and Destination Identifier in its parameter carries MIHF ID TLVs for Source Identifier and Destination Identifier in the MIHF Variable Header part of the message."ckInclusion of MIHF ID in Variable Header part is not mentioned anywhere in this section and its subsections.doc ~ bA-Upon receipt, the receiving MIH Function in the old link may start forwarding any pending or remaining packets to the new link and also release any resources in use by the old link. Upon receipt, the receiving MIH Function on the new link shall forward the message to the MIH Function in the old link.-@Af  33o  ~  33  33  33fcA9Upon receipt, the receiving MIH Function in the old link may start forwarding any pending or remaining packets and also release any resources in use by the old link. Upon receipt, the receiving MIH Function on the new link shall forward the message to the MIH Function in the old link. forwarding to the new link9d649g2259wAccepted{k) done 2006/09/21 2006/04/28 "EPeretzFFeder^Technical, Binding_103`33b103`33b8a7.3.14.2blSupport | Mobility management Protocol List (4) |beachZWpWYWzW{W|W݃WWWW2WWދWތWWWoWsWtW|WWWW'W4W@WearlierWeconomicalWeditionpWeffectVWېWۻWWeffective|WefficientAWeitherWWhWiWۙWۛW#W3WVW3WWW"W$W%W-W}WކWއWޖW5WWWxWzWWWWWWWWW"WWWWWWeitherdeletethisfigureorprovidetheupportingtextVeitherdiscussthismoredetailsordeletethiseventVeitherexplaintheunlabeledtableorremoveithVeitherintable6itshouldbe2octetsorthistableshouldVeitherintable6itshouldbevariableorthistableshouldVeitherprovidesometextsordeletethefigureVeitherremovethementionof802.3ethernetinthelabelofVVVVGnbl2#WrWWRWSW܌WܭW+W3W݃WpWWWWWl2's݃WWWWWW݃Wl3sWܴW3WDWW0WlabelqWlabeled0WlacDWlanpWlandscapeWlanguage#WkWnWܬWqW}WޡWWWAWW߽WlargeWlastܶWBWlat/lonSWlaternWܪWWlay݂Wlayer#WAWHWIWLWMWOWUWVWWWcWdWpWېWەWۣWWWWW/W7WSWTWZW\WcWeWfWiWkWܤWܫWܳWCWDWݍWWW WWW"W$W2W8WPWpWޕWޡW޿WWWWWWWWWWWWWW.W5W6WAW_WfWgWjWkWmWsWtWuWWߝWߤWߥWߨWߩW߫W߱W߲W߳W߽WWWWWWWWWW@Nlcd01ۃWۄWdalay8Wdash۱W8WrWdashes۝WdataW:WW>W}WWWWWWWzWdataratezVdatabase۳Wdatabases!Wdatagram Wdcd8WdealwWxWyWzW{W~WWWWWWWdeals*WrWdealtWdecideۋWWWdecided2WWWWdecisionfWܤWݐW.W?WtWWWdecisionsۅWWWWdecodeVWWdecodersWdecription܄WdedicatedWdeepWWdefault:WdefiitevWWݹWݹWݹWEkcdraftۃWۄWPWܥWܧWܱW{W}W݃WޖWWWWW(W,W9W<WWWWWdraw?WdriveriWdropWdue:WWduplicate4W܉W܍WWWduplicatedefinitionofmobilenode4Vduplicateentryhandovercomplete܉Vduplicatenumber10܍VduplicatedیWWduplicationwWduplicationofthemobilenodedefinitionwVdurationWduring8WWdynamicWWW?WdynamicallyWe#WiW۪WZWwW0WWW"W$W%W~WސW>WtWuWWWWWWWWWWWWW WWWW#W$W/WlWWWWWegegސVerewordline43usinganmihcompleterequestsideVe-core۽We-utra۽W۽W۽W@WCWzW{WܸW:W~WWWWWpWearlierpWvWxWeWearlyܫWbtaWWWWWܳWcchangedېWZWWWWWWWchanges>WWWWchangingWchannelW܋WW?WchannelidshouldbebetterdefinedaddasspecifiedbytheVchapter/WcharacteristicsiWWWcharacters-WiWchargeWchart=WchartsWcheckWcircle-WiWcircularۥWciteWcivic-address-elemenvWcivic-location-inforvWclaimingWclarificationWclarifiediW1WmWW?WWclarifyZWWWWW}WclarifyuppersVVclarityۧW$W>Wclarityconciseness$VclassesWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWW!WWWWޟWޫWWWWW?WKW}W߉Wp$݋`1a4b Add them.c?Abbreviations for DHCP and PPP should be added in this section.d83g2415{k) done 2006/09/21 2006/04/28 ݌E YoshihiroFOhbaGMember^ Editorial_10`1a4b- Add H-AAA in Section 4.c1- H-AAA is not defined in the abbreviation list. d84g2418{k) done 2006/09/21 2006/04/28 ݍE YoshihiroFOhbaGMember^Technical, Binding_21`3a5.4.1.4bA"A Link Up event may also carry new IP address renewal acquisition indication which may inform upper layers of the need to initiate a layer 3 handover. This may help to improve the performance of layer 3 handovers." @A 33  $ 33/  336 337 B 33ccce need to define what network initiated, network controlled, mobile initiated, mobile controlled are? d47g2419 2006/07/18 2006/04/28݋E YoshihiroFOhbaGMemberBbincludeIWpWܵW>WIWnWmWWWWWWWWWWWWjWWWWWWdeadescriptonforfollowingentriesintable-7Vincludealegendforfigure19bsapbstnetcܵVincludeamentionoftheseevenifistostatethattheyareVincludeatimebasedstatediagramshowingdifferentlinklaVVincludeclientlocationasanessentialinputparameterinaVincludecontribution0626-00-000linkgetparametersdocVincludedescriptionofcasewhereinformationrepositorymayVincludeexamplesofiereportsandclarifyhowtousethemfVincludeguidelinesonratelimitationandtimeradaptationfVincluderecommendationsfortransportoptionseitherinthisVincluderulesontheinclusionoftheseidentifiersVincludespecificexamplesofallieslistedintable-6thisVincludetheqosmodelandprimitivesdescribedincontributiVdlcmodeWOWWmodel$W۽WAW݃W>WYWއWXWWW!W&W<WWmodificationskWmodifiedށWރW5Wmodify;W4W5Wmodifythecurrenttextthissapdefinestheinterfacebetwe4V5VmoduleܤWݐW.WAWmorewW۳W-W:WܓWWݽW WW>WYW6WtWWWWWWWWWWWWWWWWW<W?WiWoWWWWWWWWWmorecallflowsshouldbeaddedtoshowhowmihprotocolisVV9W9Wa   "#$%&'()*,-./2458:>@ABCILMNOVY[\]_adklnpqtuvw|}~ހށނރބޅކއވފދތލގޏސޑޒޓޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޖޗޗޗޗޗޗޗޗޗޗޗޗޗޗޗޗ݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃s bB------------------------------------------------------------------------------------------- | ...................... | ............................ | ----------------------------------------------------------------------------------------------------------------------------- | MobilityMgmtProtocolSupport | Mobility management Protocol List (4) |C~ -----------------------------------------------------------------------------------------------------------------------------Z@A>  33    33>c "persistent URL" and a standard cannot be in a position to specify persistent URL locations....mRejectedvHIssue identified. suggested remedy cannot be applied to a specification.wRejected 2006/08/21EVidalFAlbertGMemberdalFAlbertGMembererererd826LcaddaspaceformaybetomakeittwowordsthisisintableVaddstocommandsinthelinethatquoteslinkcommandorigiVaddstosystemsin3gppsystemalreadybroadcastVaddthefollowingtextbeforetheintroductionoffigure11 VaddtheinthefollowinglineinthissectionareprovidediVheinthefollowinglineinthissectionareprovidediVVheinthefollowinglineinthissectionareprovidediVVW[WadditionalەW W*WMWtWܓW݄WݸWadditionalieisneededundergeneraliealsothereisnone Vadditionally:W\Waddress:W;W<W=W>WۈWەWWWWWWWWW W%WݍWݷWaddressedWaddressesܰWWWW WݏWaddswWadequatenWadequatelyەWadjectiveeWadjustmentsWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWW hbAR  33  #  .  33R  33  Rc6MIH_Get_Info.indication should be MIH_Get_Info.request^technicalbindingVVVV"V#V%V'V(V)V*V,V-V.V/V2V4V5V8V>V@VAVBVCVLVMVNVOVVVYV[V\V]V_VaVdVtVvV|V}V~VVހVށVނVރVބVޅVލVގVޏVWVXV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV;Octhetermgenericsapisconfusingsinceinline47itthensVthetextintherepresentationcellisadescriptionnotasVthetextofthissectionmakesalotofhypothesishowinfor<VthetextsaysnonewprimitivesorprotocolsneedtobedefiVthetextthisparameterspecifiesthelistofcommandsthat{Vthethreecriterionstatedinthenormativetextforselecti-VthetidisactuallyinthefixedheaderVthetransactionidisalreadydefinedinthefixedheaderpauVthetwomechanismsforretrievinginformationelementscurretVthetwostacksinthefigureareidenticalVVthetypemustmatchtheonedefinedintable6VVtheunderstandingofthetitlelistofnetworkslinktypesiVtheuniquenessofthemihfidisnotclearforexampleitisVVVvFkcthewordingislooseandlargelyrepeatingwhathasbeensai@then@therearetwomihgetinforesponseinthisflowchart@lthereisnoneedtodefinenewtermshorizontalhandoverand@therefore@they@this O=thisisalinklayerindicationwhichshouldonlybereceive@ thisneedtobere-writtenasaproperreference@ thissectionisaboutdesignthegoalofmiisnotneedtota@those@time@Dtlvs@to@uޖ>etobeconsistentwithnotionthatoneinstanceofmihbein@to@uޔ3evs@to@uޔ3eime@Dtlvs@to@uޔ2eto@uހ2e2eDtlvs@to@uܸހ1e%typo@iunfamiliaracronym@unlabeled@Heutralenoughtoincor@E waccepted-modified"*45LMOV]adnށރގޏ\f݃ރ߃ 3>?jvፃ᷃ểῃărejectedӃIXjkpqwxyz{|}~ࣃृଃසໃƒăŃʃ΃҃Ճփ؃كۃ܃  "#&')148:W|W|W|W|W|W|WI ^bindingWWWW"W#W%W'W(W)W*W,W-W.W/W2W4W5W8W>W@WAWBWCWLWMWNWOWVWYW[W\W]W_WaWdWtWvW|W}W~WWހWށWނWރWބWޅWލWގWޏWWWXW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#brewriteYWWrewritethesectionandfocusmoreonhow3gppnetworkscanVrewritethesectionandfocusmoreonhow3gpp2networkscanYVrfc:WWuWrfc4889WrfcsWrighthandWWroamingWWWrollbackRWۉWRW܃WrollbackactionthreshۉWrolledRWrootvWrouter"W$W%WޏWWrouteradvertisementisencapsulatedޏVroutersWWroutingOWPWWrowܓWrowsWrrc$WrregisterWrW|Wrtt WWrtxJWrulesWފWWWWWrxlevncellGWIWlWmWmWmWWIWIWIWIW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W&Ws0004-dۡWs0024&Ws0024-a'WbshowWW݃WWshowinformationrepositoryatthemnaswellVshowingWWWshown7WzW݃WW>W7W7WܳWWshown7WyWzW݃WW>W>W bcFLink_Event_Deregister.confirm should be Link_Event_Deregister.responsed514g2421vby comment 482w Superceded 2006/09/2136EKenichiFTaniuchi^Technical, Binding_72a7.3.8bAm7.3.8 Link_Configure_Thresholds.confirm response Same change is needed at the table of contents, and P72/L62m@AR  33   '  2  33RcNLink_Configure_Thresholds.confirm should be Link_Configure_Thresholds.responsed515g2422w Superceded 2006/09/2148EKenichiFTaniuchiGMember^Technical, Binding_150`16aAnnex CbA6One persistent URL of this schema shild be assigned. 6@A*  334  *c.An URL of Basic Schema is still not assigned.d900g2436i Vivek GuptajIt's not clera what is meant by "persistent URL" and a standard cannot be in a position to specify persistent URL locations....mRejectedRejectedmRejected414HݔE YoshihiroFOhbaGMember^Technical, Binding_44`38a6.3.2brtain scenarios. Comment this scenario also covers network to network MIH communication as well. Discussion that MIHF ID can't be known across an intermediary given the current definition of multi hop. and MIH sessions. Discussion about discovery of ES or CS PoS beyond first MIH PoS, consensus is the L3 proto will define this, but probably won't use this multi-hop model. For L2, we only support discovery through first L2 broadcB-ast domain. Discussion that in an implementation, an intermediate PoS will terminate the session from the MN and create a new session with another PoS, then act as intermediary when recieving transactions for that service/session from MN. We are not doing anything within the protocol to enable this.wAccepted{b) awaiting missing input 2006/08/23 2006/04/28MarkedݔE YoshihiroFOhbaGMember^Technical, Binding_44`38a6.3.2b bA   33    $  338  ?  I  33^  e  o  33    / ېbA 7.3.1 Link_Event_Discover.request Link_Capability_Discover.request 7.3.1.1 Function This primitive is used by MIH Function to query and discover the list of supported link layer events and link layer commands. 7.3.1.2 Semantics of service primitive The primitive parameters are as follows: Link_Event_Discover.request Link_Capability_Discover.request( ) 7.3.1.3 When generated This primitive is generated by an upper layer entity of type MIH User that is seeking to recBeive link layer event notifications and learn about which link layer command the low layer can support. 7.3.1.4 Effect on receipt The recipient responds immediately with Link_Event_Discover.confirm Link_Capability_Discover.confirm primitive. 7.3.2 Link_Event_Discover.confirm Link_Capability_Discover.confirm 7.3.2.1 Function This primitive returns the result of the query to discover link layer events capability request 7.3.2.2 Semantics of service primitive The primitive paKacvalueforversionisnotdefinedVVvalue-addWvaluesxW|WܖWܚWWW6WtWuWW9WWvaluse6Wvariable|WW'WtWWWWWWUWvariables~WvariousaWWW[WW<Wvary'WverbW/Wversa6WversionېWWVW W;WWvertical?W@W:W;WWverywW WܾWWtWW WviaܬWWWWviable۳Wvice6WviewIWܤWݐWvisibleWWWWvisitedW!WvlansWW6WviewIWܤWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWݐWz'XulisesolveraVVVVVVVVVVVVVVVVVVVVVVVVVjVkVlVmVVVVvidalޖ᥃ᦃvivekܛܟܠܡܣܤܥܧܨܫܬܭܱܾܰܵăǃՃփ׃؃كڃۃ܃݃ރ߃ᴃᵃᾃȃwolfgangܑܒܓܔܕܖܚ҃Ӄxiaoyu=>?ᬃᭃᮃᯃᰃ᱃ᲃyanWWyanpengjunxiangguoVVyewlWnWWWWWWWWWWWݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σyuanۅۆVbshouldbereplacedwithnetworkselectorformallydefinedon.Vshoulddefinethevaluesfortheseidsintheannexa-4forVshouldincludeadefinitionorexplanationforconsistencyajVshouldmakeclearifnetworksrefertoaccesstechnologiesVshouldrewordthisandsaythatduringregistrationtheuserVVrewordthisandsaythatduringregistrationtheuserVVdrewordthisandsaythatduringregistrationtheuserVVuringregistrationtheuserVV|corderۅWWHWRWYWtW{WW"WlWWWVWkWorderingW WVWordinary:WoriginalWoriginate7W8WܫWWoriginatessWoriginationIWosi>Wosi-service>Wosi-service-procedur>Wosi-service-user>WotېWotherېWWWWW'W1WCWZWWbWWW"W#W$WYW>W|WWWWWWWWWWW<WqWsWWWWWWothersWWWothersisnotappropriateintherepresentationcolumnVVp{k) done 2006/09/21 2006/04/28EPeretzFFeder^ Editorial_16`42b(Mobile Node or User Equipment)cChange (User Equipment)d113g2225{k) done 2006/09/21 2006/04/28MarkedMarkedzFFeder^ Editorial_18`22bWhen provisioned, the MNc*When provisioned the MN.... missing commad131g2226{k) done 2006/08/29 2006/04/28 EPeretzFFeder^ Editorial_18`31b"to, or co-located with the PoA....c,to or co-located with the PoA missing commad133g2227{k) done 2006/08/29 2006/04/28 EPeretz FFeder^ Editorial_18`38bAjby R1, R2 or R3 over any access network and two MIH network entites can communicate with each other via R4j@A>  33<  G  33>cby R1, R2 or R3 over any access network and two MIH network entity communicate with each other via R4 two entities as opposed to two entityd135g2228{k) done 2006/08/29 2006/04/281 TycA> 33)  335 33> 33. 33fr "a" from the sentence that says "The MIH Function Header consists of a two parts..."g2230 2006/05/01e frame structure...."g2229 2006/05/01E Ulises Olvera^ Editorial_114`15a8.3.3b2"The MIH Function Header consists of two parts..."cfRemove the letter "a" from the sentence that says "The MIH Function Header consists of a two parts..."g2230 2006/05/01tence that says "The MIH Function Header consists of a two parts..."g2230 2006/05/01he letter "a" from the sentence that says "The MIH Function Header consists of a two parts..."g2230 2006/05/01wAccepted{k) done 2006/09/215E Ulises Olvera^Technical, Binding_44`51a6.3.2bShould make clear if networks refer to access technologies. The number of operator list i.e. No 1.2 can be obtained from the network operator list i.e. N0 1.3 so there is no need to have No 1.2cAUFor No. 1.2 in the representation field: "if networks of the same link type have different operators then they are classified as different networks...." It is not clear if networks refer to access technologies. Is it necessary to have the number of operators for each available link type (No 1.2 of the Name of Information Element column)?Ud355g2261v^Clarify networks to mean access networks. Need both number of operators and list of operators.wAccepted-Modified{k) done 2006/09/216E Ulises OlveraGMember^Technical, Binding_113`29a8.3.229a8.3.229a8.3.2ation may be provided"crovided"crovided"crovided"c5/14E Ulises Olvera9vconfigurationW4WnWWconfiguregWaWoWWconfirm#Wconfirm/request/respWconfusionWcongestionWconjunctionWconnectionsTWWconnectivitySW?WconsensusݓWconsider>WconsiderationRWconsideredWconsistencyۓWconsistentCWcontaWcontainerZWcontextܾW|WcontribZWCWWcontrib21-06-0674ZVcontrib21-06-0675VcontributionDWZW۽WRWWEWzWW>WYW\WfWjWWWWWWWWWWWWWW WWW2W3W4W>WlWoWvW{W}WWWWWWWWWcontribution21-06-0633-01-0000-aformihhandoverinitiateVcontribution21-06-0725-00-0000-iVcontributionsCW|WWWal, Non-binding_111`18a8.2.1bRemove the sentence.EMathieuFPERESSEGObserver[VczTo insure interoperability, the IEEE 802.21 must define how to decode the Set of Event IDs and their registration status. d509g2275wAccepted{k) done 2006/09/21WENada, Golmie, Member^Technical, Binding_70`57bAUse of a bitmap model to encode the list of events that the MIH would like to unregister. There are currently 9 events, so using 32 bits will allow enough bits to add new or vendor based events. In the Valid Range, replace "Set of valid link events" with "4 octets representing the list of events" In the Description, add the following: The encoding uses a bitmap where the bit position represents the event ID. A bit set to 1 indicates that the MIH wishes to deregister for that event. For Bexample, if bit #0 is set to 1, The MIH requests to stop receiving Link Detected indications. Bits corresponding to reserved event IDs must be set to 0.  q ݎbfhbaGMember^Technical, Binding_21`30a5.4.2.3bAU "In case of local commands, messages typically propagate from the upper layers (e.g., policy engine... ) to the MIH Function and then from MIH Function to lower layers. In case of remote commands, messages may propagate from upper layers via MIH Function in one stack to the MIH Function in a peer stack (with the use of the MIH Protocol)."U@Af 33Q W 33d  g 33 33 ‚& ‚T ‚q‚v"@€P"P€ @`"p€`p‚9"jun hirano"@jun‚f"@farrokh khatibi 0@P farrokh‚Q‚b‚c ‚&‚I0‚S ‚d!‚r"@0#@$‚E%P $cAUpon reception of this primitive, the MIHF on new PoA may either interact with upper layer to achieve enough information or further deliver this message to the MIHF in the network, e.g Access Router with MIHF which may have enough information on this message. When this primitive is delivered to the upper layer of the MIHF in the network, e.g, Access Router with MIHF, this may trigger to send network address related information, e.g, Router Advertisement either directly to the mobile node oBNr to MIHF. Change text, change "new" to "target". Consistent with other SDOs <d654g2263{k) done 2006/09/21 2006/04/28 %EPeretzFFeder^Technical, Binding_104`64b104`64bEPeretzFFeder^ Editorial_22`31bAlMIIS provides the ability to access this information about all heterogeneous networks in a geographical areal@A>  33#  33)  33>ceach other via R4j@aAbaddthefollowingintheannexa4atthebeginningܚVaddthefollowingparagrpahinsteadVaddthefollowingtableRVaddthefollowingtext>Vaddthefollowingtextimmidiatelyaftertheheadingandbef2Vaddthefollowingtextinsection8.5VaddthemissingparameteradddescriptionforoldlinkidentifVaddthesectionsasdescribedindcn21-06-0622-00-0000LVMVaddthem݋Vaddtotable6rVaddtothesentenceorfromaninternallymaintainedmiisdaVaddtwogroupstokeepconsistentwithtable6VallymaintainedmiisdaVdmiisdaVVaintainedmiisdaVVothesentenceorfromaninternallymaintainedmiisdaVVorfromaninternallymaintainedmiisdaVVothesentenceorfromaninternallymaintainedmiisdaVVallymaintainedmiisdaVVenceorfromaninternallymaintainedmiisdaVVaddedAWZW]WWWW}WWW޿WM4cableCWmWOWW$WWWWWmWabilityWable-WCWmWܶWCWOWmWmWWOWmWmWWOWmWmWWWWWWWWaWۆWۇWۊWېWWWWWWWWWݏWWWWWdWgWޡWީWWWWaboveWWW#W[WWWabstractionܟWabstractions%WacceptableWacceptance݃Waccepted;WWacceptor>Waccess$W\WۉW۳W۷W۸W۽WWWWWWW1W:W;W=W@WܬWܾWW:WCW_WuW݂WݏWWWWWWWW"W$W%W*WޢWWaccessing۾WaccomplishWaccordingۂWۅWW:Waccordingtorfc3753thedefinitionsarequoting:VaccortingoWaccountWaccurateXWaccuratelyWachieve|W"W#W$WDcprotocolsZWW W$WWWprototypeaWaWksureݓWsyntaxWsystemsWWtableWWWWtakedWWtalbeYWtalk#Wtcp WtechnologyOWWtermsWtextAWWWWWtexts WthanWWWWWtextsWthanWWWhanWWWWWWWWWWWWWWWWWWWWWWPWtextsWthanWWW<WAWjWkWmWnWoWuWzW{W|W}W~WہWWWWCWWWjWthe0WAWYWZW_WaWjWkWmWnWoWzW{W|W}W~WہWۓWWWWW=WCWܶWܻWWWWWݳWݴWݻWW+W-WdWthecommentshouldberejectedforthefollowingreasonsVthelinklayerqoscharatersticsareavailabletothestaviVthereasonisnotclear0x2161432bitsVo bAMIH_Get_Info.indication request@AR  33     33  Rc6MIH_Get_Info.indication should be MIH_Get_Info.requestd474g2418i Eunah KimkIRequest type primitive cannot be issued from lower layer to higher layer.mRejectedvby comment 473w Superceded 2006/09/2122EKenichiFTaniuchi^Technical, Binding_70a7.3.4bAp7.3.4 Link_Event_Register.confirm response Same change is needed at the table of contents, P69/L65, and P70/L13p@AR  33  !  ,  33RcBLink_Event_Register.confirm should be Link_Event_Register.responsed508g2420vby 482.w Superceded 2006/09/211EKenichiFTaniuchi^Technical, Binding_72a7.3.5bAq7.3.6 Link_Event_Deregister.confirm response Same change is needed at the table of contents, P71/L3, and P72/L21q@q@q@226acu"Link Type" (Network Identifier) parameter is required for MIH users to determine which link is generating this eventd824g2240v)Add Link Type to all MIH_Link indicationswAccepted-Modified{k) done 2006/09/21 2006/04/26MarkeddESrinivasF Sreemanthula^Technical, Binding_76`5a7.3.11.1b9Remove: MACNewPoA MACOldAccessRouter MACNewAccessRouter cWhy does LInk going down provide information about new PoA, old AR and new AR? Does it mean the signal corresponding to new PoA is better?d538g2246iJin LeejKeep the new PoA information kIn case an mobile node has the information of the MACNewPoA through periodic scanning or information service, link going down can carry the MACNewPoA information so current PoA can take an appropriate action in advance.mAccepted-Modifiedvj Remove MACOldAccessRouter MACNewAccessRouter Add if available to the word optional in table for new PoA.wAccepted-Modified{k) done 2006/08/29 2006/04/26 kESrinivas$GEVivekFGuptaGMember^Technical, Binding_87`23a 7.4.7.1.2 in the context of a specific link, e.g.spcified in TYPE_IE_POA_MAC_TYPE IE (6.3.4.3.3). Therefore, the item listed here should be divided into two groups, the link specific information, e.g. Security, QoS, and the network specific information, e.g. Internet Access, IP version, etc. Therefore, suggest to create two IEs: TYPE_IE_POA_LINK_CAPABILITY; TYPE_IE_POA_NETWORK_CAPABILITY.mAccepted-ModifiedpDo we want to split this into two IEs, as recommended above? or do we want to move the OoS/Security in an Access Network specific IE? If the latter, which one?vvSpecify these values (Securiy and QoS) in the context of access network as opposed to in the context of just the PoA.wAccepted-Modified{c) instructions unclear 2006/08/23MarkedEVivekFGuptaGMember^Technical, Binding_87`23a 7.4.7.1.2c006/04/28k entites can communicate with each other via R4j@&7pby?W^W`WhWۏWW:WIWhWܰW{WݓWݜWWލWc2Wcan:W{W݃Wcapture{WcaseYWcasesܥWchangegWWWaW}Wchanged2WAW݃Wchangedto2octetsconsistentwiththeoriginal6.3.4.1.2AVchangedtoanmihthroughoutthedocument2VchangesۅW۽W:WYWܥWܰW{WݜWWWCWchangesmadein5.5.5text۽VchangingWclarifiedWclarifiedwithchangesfrom195VV95VVVcomment?WhWۏWۖWW.W;WSWYW݃WލWcomment9iseditorial;VcommenterݓWcommetCWconfiguregWconflictWconsistentAWYWcontainerZWcontributionZW{W݃Wcontribution21-06-0711-00-0000-itlvretrievalnoexclusionZVcontribution21-06-0712-00-0000-itlvcontainerdoneZVcopied\WcopyۓWcouldܾW{WcreateۓWzWcreatedۓW(\d‚‚ܤÃ!۪Ã! ܥÃ!00Ã!@1Ã!P۫Ã!`Ã!p Ã!ܧÃ!Ã!ܨÃ"Ã" Ã"0ۭÃ"@Ã"P,Ã"`Ã"p3Ã"Ã"Ã"ۮÃ#4Ã# ۯÃ#05Ã#@Ã#P۰Ã#`6Ã#pÃ#<Ã#XÃ#۱Ã$Ã$ Ã$09Ã$@Ã$P7Ã$`Ã$pÃ$Ã$۲Ã$8Ã%۳Ã% ۴Ã%0!Ã%@Ã%PÃ%`"Ã%pÃ%ܫÃ%Ã%ݍÃ&6Ã& Ã&0ݎÃ&@"Ã&P۶Ã&`Ã&p<Ã&ܬÃ&#Ã&Ã'Ã' ?Ã'0-Ã'@Ã'PÃ'`Ã'p=Ã'>Ã'Ã'ܭÃ(ݐÃ( ۹Ã(0.Ã(@Ã(P?Ã(`ۺÃ(p@Ã($Ã(vÃ(ۻÃ)AÃ)0ۼÃ)@Ã)P#Ã)`uÃ)pÃ)݃Ã)=Ã)Ã*wÃ* xÃ*0yÃ*@2Ã*PÃ*`۽Ã*pÃ*$Ã*Ã*&Ã1YÃ1 %Ã10 Ã1@Ã1PۿÃ1`EÃ1pÃ1Ã1 Ã1 clinkaWdWކWޖW5W6W?WZW[WlWmWnWWWWWWWWWWWWWWWW WWWW%W9W?WDWLWMWNWOWYW_WcWiWmWzW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWlinkcommandindicationshouldbelinkcommandrequestVlinkconditionsanddifferentaccessnetworksinneighboringVlinkconfigurethresholdsaddsinrinadditiontosignalstrVlinkconfigurethresholdscommandislinkcommandthatgoesVlinkconfigurethresholdsconfirmshouldbelinkconfiguretVlinkconnectlinkdisconnectlinksleepandlinkpowerdownmVlinkdetectonlyindicateswhatisinthebraodcastorstateVVVVVVVVferentaccessnetworksinneighboringV)VbvideoۖWWviewܤWvisited۲W9WWW!Wvisitednetworkinsection3thenthetextshouldVvisited/home!Wvisiting۲WvpnAWwWWw/o{W#Ww3qW~Ww3cqWw3crecommendationsparqlquerylanguageforrdfhttpwwww3qVwaitWwaituntilthereferencedi-dstobecomerfcsVwant<Wwants}WxWzWwasۉWVW܌WWwayAWWW>Wwe WWWWweproposetoaddanienewmacaddresstotellthemihfoftaVweproposetospecifythewayfordealingwithmihcapabilitVwell WAWiWpWsW۶WWWWWWwereWwether܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁WbbytezW{WWދWތWbytesܑWܔWWcۡWYW&W'WW5W2W>WWWWctowardsVcableۖWWcahngeWcahngetodefiniteVcallWW2W>WctowardsVcableۖWWWo bcAMIH_Event_Register.confirm should be MIH_Event_Register.response. Link_Event_Register.confirm should be Link_Event_Register.response. MIH_Event_Deregister.confirm should be MIH_Event_Deregister.response. Link_Event_Deregister.confirm should be Link_Event_Deregister.response.d267g2410i Vivek GuptajThe MIH_Event_Register/deregister.confirm are ok. The Response from remote entity can be reflected as indication to local MIHF Users. Link Event_Registr/Deregister.confirm are ok.mRejectedvBy comment 482w Superceded 2006/09/2115EKenichiFTaniuchi^Technical, Binding_40a6.2.4bALink_Command.indication request@AR  33     33  Rc6Link_Command.indication should be Link_Command.requestd289g2411i Eunah KimmAcceptedvby comment 287w Superceded 2006/09/212006/08/2918EKenichiFTaniuchi^Technical, Binding_62a6.3.9bbonlyWZW܁W݃W>WWW<WtWuWWWonpropertywWontouWonwardslWopcodeܒWWWoperation"W8WW WoperationalWoperationsfW}WoperatorZWWܾWݕWWWsWWWW@WoperatornameݕVoperator-nameݕW(W,WoperatorsZWqWsWtWWW>W@WopposedۖWWWoptimalum|WoptimumAWoptiontWtWtWmalumuWoptimumAWoption_W_WAWAWWWWWWWWWWWWWWWWWWWWWWWWWWWWW&pneedsWaWWneitherpage86/line48norsection8.4.1.1makesenseclarikVrikVkVikVkVBWCWnoZWnode.WnoneܰWnorkWnotۅW۽WW)WRWܥW{WݒWݓWnotesEWnothingYWoctetsAWofW)WW݃WkWvWofficialݓWon۽WWݒWݓWoneۅWܾWonlyWRW{Wonlyaddednew6.4andsubsections{Voos/securityܾWopen{WorܾW݃WoriginalAWp9-l6ܡWpagekWpage/line/sectionWparaWparameterݜWparametersݜWpart)WWkWper.Wpic>Wplaceholders&Wplaceholdersaddedbutneedsomeonetoprovidedetails&VpleaseݜWposܥWpppWppt݃WpresentWpreviousۖWprimitiveRWprimitives۽WprobablyܰWprobablynoneneededܰVprovide&WWquestions{WradiusۓWreadWreadabilityDWWsameۖWܡW06/05/14pchighWܬWhigherܤWݐWWWWWW?WWWhighlightingWhighlywWxWyWzW{W~WWWWWWWhindersWhindersdeploymentonlytomorepowerfulnodesVhinting<Whnadover܀WhoIWzWWho-typeWhomeW!Whomogeneous1WWhop-by-hopW W Wo vthese{W\W WWWWtheseeventsmayalsobeusedforhomogenoushandoversVtheyZWWWWWthings"WthirdWthisCWQWRWSWTW4W5W7WSWnWthisisdesiredbutwecannotmandatethiscertaintechnologܽVthiswillbehandledseparatelyforalsuchiesandappropriVthoseەWthreadSWthresholdsaWthroughݓWthroughoutWtime-interval\WtimeoutۅWtitle)WtlsWtlvܗWtlvsZWܗWto*W0WBWZW[WێWەW۬W۳W۴W۵WWWW W=WHWܗWܛWܢWܽWܾWܿWWWWWWWWW WW W1W2W:W;WDWFW{W}W݀WݏWݓWݜWWWWW/W1W4W5W6W7W>WBWCWSWdWnWtodayܗWtoo{Wtoward3WtransactionsݓWtransparent*WtransportW~7 cforWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWctextneedsimprovement VtextneedsimprovementalotofdiscussionisspeculativeinAVtextsaysafterauthenticationandassociationtoacertainVsaysafterauthenticationandassociationtoacertainVVvdÃ2/Ã2 GÃ20jÃ2@~Ã2PÃ2`Ã2pÃ2Ã2Ã2Ã32Ã3 YÃ30Ã3@4Ã3P5Ã3`HÃ3pÃ3ܰÃ3ZÃ3[Ã4Ã4 Ã408Ã4@Ã4P(Ã4`Ã4pÃ4Ã4Ã4nÃ5)Ã5 *Ã50Ã5@Ã5PÃ5`Ã5pÃ5+Ã5kÃ5Ã6{Ã6 Ã60Ã6@IÃ6PÃ6`ܱÃ6pÃ6Ã6:Ã6Ã7Ã7 Ã70ݑÃ7@Ã7P7Ã7`Ã7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@ݒÃ8PÃ8`Ã8pÃ8Ã8Ã8Ã9Ã9 Ã90Ã9@Ã9PÃ9`Ã9pÃ9>Ã9Ã9Ã:Ã: 8Ã:07Ã:@Ã:PÃ:`Ã:p#Ã:KÃ:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃA ÃB@ÃBÃCÃC Hbplace۞W(Wplaced Wplacement WplacesWfWplane4W5WWpleaseWpleasenumberthereferencesandupdatecrossreferencingVpoaAW#W܍WܾWWkWWW"W#W$W%W~W1WrWWW8WzWWWpoamaximumdatarateVpoa'sWpoa-address~Wpoas?WAWpointAW۴WWIW'WWWpoints*W?WWܨWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWXWcWpossibilitiesWpossibility۳WpossiblewW۸WWYW=WoW7WpossiblyܡWW)W݂WpotentialOWPWsWWWpotentiallyWFbnetwork-layerܡWtwork-layerܡWܡWnetwork-layerܡWܡWassisted݊Wnetwork-controlled݊W݊W5bnode@znot@Fnote@InotificationPnotifications@obtained@xoccur@octets@^ofܟ(*ofsparqlqueryresultwhenthistlvis@offered@once@only@optional@options@or?order@originate@noriginator@outside@pair@paragraph@parametersې;parametertype@payload@performance@Hplace@policy@power@pre-provisioned@primitives@Qprior@dpronounced@imitives@Qprior@dprogressed@mitives@Qprior@dprogressed@dprogressed@primitives@Qprior@dprogressed@sed@d ܬcA^The information can be obtianed either by TLV or schema. However the following lines on page 22, gve the notion that information can be ontained using schema only. "The capability of such network information service can be obtained via schema access. The structure and definition of schema can be represented in a high level language such as XML" , ^d157g3225i Qiaobing XiemAcceptedvAdd " The capability of such network information service can be obtained via schema access. " later on in the page (lines 27/28)wAccepted-Modified{k) done 2006/09/21ܭEVivekFGuptaGMember^Technical (was Editorial)_22`35a5.4.3bDelete L2 from above sentence.cA"How this information is developed and deployed in a given L2 network is outside the scope of the standard." The IS development and deployment issues are agnostic of network layers.@A> 33:  33= 33>d169g3226wAccepted{k) doneV\\bstandard WsWvWwWەWWWW4W5WWW W<WWWstandardsW&W?WstartOWVWۉW WstartedۉWstarting܍W*WlWstateIWWWWWWstated,Wstatement WWWWstates'WstaticWWstationWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWUcadded0W݋WWWWW&WWWWaddingۅWWW{W#WadditionWYW|WWWWWW.WadditionalەWtWܓWݸWWWW=WWadditionalieisneededundergeneraliealsothereisnoneVadditionally!W/WaddressەWWWWݍW"W#W$W%WfWgWhWiWWWWWWWWWXWWWaddressedWaddressesܰWWWWW?WaddswWaddtion6WadequateWW WݏWaddswWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWatenWadequatelyەWadjectiveeWadjustmentsWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWWcmeanIWZWWdWWWW$WWWmeaningWݍWWWmeaningfulWtWuWmeaninglessW/WmeansۄWܟWW!WWWWWWtWmeantޏWmeasurement WmechanismWtWuWvWWWWWWWmechanismsܛW3WtWWW WWmechansimWmedia(W)WDWېWۖWWIWܠWܤWܰWW}WݐWW8WOWnW1W>W[WWWWWWWWWWjWWWWWmediaindependentsapsܰVܰV1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W*vnetwork۫W۴WܬWܾW3W{W݃WݓW"WWWWWWWWWW#W?WWWWWnetwork/link-levelWnetworksۋWۓW۫W۳WW0WWWWW?WjWnew۳W3WݓW"WdWWWWWnewtextVnewtextprovidedaspartofdocument21-06-0648VnistWnmsWnoZWۅWWIWWWWWWWWWWWWWWWWWWW-W=WVWWWWWWWWnoavailablesuggestedtextcommentassignedforfurtherworVnoclarifyingtextprovidedrefertocomment339formoredeVnocurrenttextprovidedVnodetailsprovided-V-V-V-V-V-V-V-V-V-V-V-V-V-V-VVVVVVcomment350addressesthisVnosuggestedremedyVVVVVVh"vbroadcastݓWbucketWbullet݃Wbut"WۓWݓWWWWWWWWWbyRWۓW۔WەW۳WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W%W0WCWDWXWYW[WyW{W~W݂WݙWݪWW0WFWWWXWmWrWsWxWyWzWby215WVby378380~Vby394XVby460Vby473Vby482yVby492FVby516Vby518FVby527ݪVbycomment142128226Vbycomment162۸Vbycomment195۾VCVbycomment200tobeverifiedwhenre-drawingthefigureasDVbycomment203Vbycomment208Vbycomment212%VVbycomment215&Vbycomment215andissue40'Vbycomment287VV9VyVsVbycomment31V%V( ptheܡWܾWWWWaW{W}W݃WݒWݓWݜWVWvW2Wthechangesagainst5.8.33gppamendmentsisunclearandnot۽Vthere݃Wthese{Wthis۴W۽WWW;WܰWܾW݃WWYW2Wthisistechnicalandsomeoneneedstoprovidetable33aVthisshouldbeasupercededcasenothingisdonehereYVthoughRWthreeݜWthresholdgWthroughout2Wtitled݃WtlvZWtogWۅWۓW۪W۴W۽WWWWWW2W;WAWRWYWܵWܾWWWW&WaWzW{W}W݃WݛWW@WVW\WlW2WtooۓWۓWۓWۓWWݛWW@WVW\WkWlW2WtooۓWۓWۓWWlW2WtooۓWۓWۓWۓWoutanymentioningofglobaluniquenessVtried&Wtriedbesttoadddetails&Vtry{WtwoDWܾW2WtypeJWۓWunclear۽WuniquenessWbieee802.11JWWWieee802.16JWWieee802.21pWies?WAWZWfW$WsWtWvWWWWWWWWWWietfۓWWWuWietfinformationelementsfor802.21VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV=EPek YewFTanGMember^Technical, Binding_150aAnnex Cb&replace "normative" with "informative"ctAll MIHF is required to equip with XML/RDF regardless of its use accorting to Annex C since it is a normative annex.d898g2220iYoshihiro OhbakoNormative does not mean mandatory. In fact, schema support is optional feature required for XML/RDF query only.mRejectedvNormative does not mean mandatory. In fact, schema support is optional feature required for XML/RDF query only. Add a couple of lines to that effect in Annex C.wRejected 2006/09/21 2006/04/28EKenichiFTaniuchi^Technical, Binding_36a6.1.4bAMIH_Event_Register.confirm response Link_Event_Register.confirm response MIH_Event_Deregister.confirm response Link_Event_Deregister.confirm response@@SAP primitives. Implementor would not be able to implement interoperable solutions based on the brief descriptions on 4 primitives.d501g221616 2006/04/2816 ycd776g2310{k) done 2006/09/21zENada, Golmie, Member^ Editorial_119`17bAReplace "the list of events that may carried in a message.Each command is represented by a commandcode and occupies one byte." with "the list of events that may be carried in a message.Each command is represented by a command code and occupies one byte."@A  33!  33- 33[  33f 33  33 33  33 33cASyntax error in "the list of events that may carried in a message.Each command is represented by a commandcode and occupies one byte."@Af 33)  335 33c  33n 33fd777g2311{k) done 2006/09/21{ENada, Golmie, Member^ Editorial_119`48b119`48b119`48bage."C@14EPeretzetz 3vchangetheprimitivedefinitionandtheprotocoldefinitionۉVchangethesentenceasfollowsVchangethetextandmaker1asr1/r2/r3onpage18line57/5Vchangethetexttothecsapdefinedintheieee802.16stan5Vchangethetitleassuggested)VchangetoVchangeupperlayerstomihfusersVchangesەW۳WWWWWchangesinsection7.3.9.1donotlokaccurateVchannelW?Wcharacteristics{WcheckWchoiceWchoicesۋWWchooseWcipherWWWclarificationWWW)W1Wclarified/modifiedWclarifyW{WW\WjWWWclarifynetworkstomeanaccessnetworksVclarifyingWWclaritynWclassificationCWclassify\W {bAReplace "the list of events that may carried in a message.Each command is represented by a commandcode and occupies one byte." with "the list of events that may be carried in a message.Each command is represented by a command code and occupies one byte."@A  33!  33- 33[  33f 33  33 33  33 33cThe text "This parameter specifies the list of commands that may carried in a message. Each command is represented by a command code and occupies one byte." does not apply properly to the message.d780g2312{k) done 2006/09/21 |ENada, Golmie, Member^Technical, Non-binding_119`55bSet the Length field to 1 Change the Value to : For each bit location a value of 1 indicates that the Query type is supported. Bit #0: TLV Bit #1: RDF_DATA Bit #2: RDF_SCHEMA_URL Bit #3: RDF_SCHEMA Bit #4~7: Reserved ,0dichengܾWWWWdas#WbWbWbWbWbWbWbWbWbWہWہWہWہWہWہWہWWWW=WCWܬWܸWܹWܻWWWWW݀WW-Wmathieu!WuWwW۬WWWWWW+WWWWWW W0W݂W݄WݍWWW,W1W3W>WKWgWhWmathieuperesse!VuVwV۬VVVVVV+VVVVVV V0V݂V݄VݍVVV,V1V3V>VKVgVhVperesse!WuWwW۬WWWWWW+WWWWWW W0W݂W݄WݍWWW,W1W3W>WKWgWhWsubir#W0WAXWYWZW\W]W_WaWbWjWkWmWnWoWzW{W|W}WےWۓW۷WWWW=WCWܬWܸWܹWܻܺWWW '|vbyby215Vby250Vby3783809Vby394oVby460 Vby473Vby482Vby492Vby495eVby496Vby516Vby518lVby527NVby527626GVHVby552mVby577IVby578Vby744XVby872iVbycomment137V!Vbycomment142128226Vbycomment162Vbycomment178uVwVxVyVVbycomment195V$Vbycomment200tobeverifiedwhenre-drawingthefigureas%Vbycomment203Vbycomment208Vbycomment212YVVVbycomment215ZVbycomment215andissue40[Vbycomment250VVVbycomment250aspercontribution21-06-0611-00-0000-mprot}VVbycomment256Vbycomment266Vbycomment281Vbycomment287VVV7VVbycomment31WVVycomment339andissue3uVbycomment348Vbycomment352360Vbycomment361V.V@V vjA3The schema representation is basically INCORRECT. You need to show list of Networks, followed by Properties of each network.....then list of operators for each network...and then for a combination of network+operator, list of PoAs followed by property of each PoA. The schema does NOT depict this correctly.3mRejectedpH- Replaced the Figure with section 2 of 21-06-0460-02-0000-Basic_SchemawAccepted{k) done 2006/09/2121wEKenichiFTaniuchiGMember^ Editorial_155`28aAnnex CbA77@A> 33#  $ 33>c3typo in "W?WjWnWoWvW|WWWWWWWWWWWWWWWWWWWtodayWtokenWtoo{Wtoward3WtraceWtrafficWtransWtransaction۔WWWtransactionsݓWtransmissionWWtransparent*WtransportWmmand ServicecLMIH event register and DeRegister Are Command Service and not Event Serviced757g2267i Qiaobing XiemAccepted 2006/07/20 2006/04/2819)EPeretzFFeder^Technical, Binding_130`4a8.5.2.1cZMove Sections 8.5.2.1 and 8.5.2.3. from Event Service category to Command Service categoryd823g2268i Vivek GuptajAs well as 8.5.2.2 and 8.5.2.4. 'bcAThe MIH Function Header consists of a two parts; one with fixed length and another with variable length. The fixed length part of the header carries the essential information which is present in every packet and is important for parsing and analyzing the packet quickly. The variable length part of the header carries information which is optional in some cases. Make the entire paragraph consistent with the title and the MIH payload format (= frames)d734g2266wAccepted{k) done 2006/09/21 2006/04/28 (EPeretzFFeder^Technical, Binding_117`14a8.3.4b,Change From Event Service to Command ServicecLMIH event register and DeRegister Are Command Service and not Event Serviced757g2267i Qiaobing XiemAcceptedwAccepted{k) done 2006/08/29 2006/04/2819 )EPeretzFFeder^Technical, Binding_130`4a8.5.2.1cZMove Sections 8.5.2.1 and 8.5.2.3. from Event Service category to Command Service categoryd823g2268dercprimitivesۃWیWPWRWSWZWܰWWW>WBW\WkWWWWWWWWWWWWWWprimivie?Wprior#Wpriorities<WprobablyېWproblemWkWWproblematic۳Wprocedure{WWW}WWprocedures{WWprocessܡWWWWWprocessing WWpropagatedWWproperWWWproperlyYW{WWWpropertiesWproposalWWWproposeۅW5WprotocoliW۪WWW/WYWZWW{W_WWWW WWWW%WpWsWWWWWWWWWWWW7W7W7W7W7W7W7W7W7W7W7W ?bA   33    TTZ  \  TT_  TTs  TTQ  T  TTe  TT&  TT therefore no need to repeat the same informantion here again.@A  33d247dependent service access points) into a single interface with the upper layers (the MIH SAP) "making the inter-media differences transparent to the extent possible.."@A  wAccepted-Modified{k) done 2006/08/21 2006/04/24+EQiaobingFXieGMember^Technical (was Editorial)_32`52a5.8.3b Remove 5.8.3.cASection 5.8.3 is just about general usage of MIH services by an MIH user. This has been described in enough details in the previous sections. This is therefore no need to repeat the same informantion here again.@A  33d2479ucgThe last two words of the last line need to be interchanged: ".....are described in the below section."d590g2224{k) done 2006/09/21MarkedE Ulises OlveraGMember^ Editorial_83a7.4.6b"MIH Get Status"c Need to correct "MIH Get Sttaus"d574g2225{k) done 2006/08/29 E Ulises OlveraGMember^ Editorial_92`45a7.4.9b"PoA"c Change "POA"d630g2226{k) done 2006/08/29 E Ulises OlveraGMember^ Editorial_111`16a8.2.1bUEither say: "The frame structure..." or say "The above mentioned frame structure...."csIt is the first time that the frame structure is referred to and so should not say "The above frame structure...."d691g2229{k) done 2006/08/29 E Ulises OlveraGMember^ Editorial_114`15a8.3.3b2"The MIH Function Header consists of two parts..."cfRemove the letter "a" from the sentence that says "The MIH Function Header consists of a two parts..."d733g2230{k) done 2006/08/29 ebthisprimitiveisgeneratedbymihfunctionwhenitneedstoLVthisprimitiveisissuedbyupperlayerstocontrollayerliVthisprimitiveisissuedbyupperlayerstodiscoverthestaVthisprimitiveisusedbyamihfunctionontheservingnetw|Vthisprimitiveisusedbyapeermihfunctiontocommunicate%Vthisprimitiveisusedbyastation'smihfunctionoranappއVbdiscoverAWLWSWېWW"W|WWWWIW}WWdiscovered|WdiscoveringWdiscovers|WdiscoverysW[W|WWWWW}WWdiscrepencyCWdiscussۓWWdiscusstheissuein21sendlstoietfforcommentifnecesۓVdiscussionDWdisparate*Wdispatched7Wdistinguish?W?WۓVۓVۓVۓVEcdelivered"W$WW8WdeliveringtWuWdeliversoWdemandW}WWdenverWWdepectingXWdependېWdependence)WnWnWWWWWWWWWWWWWWWdependentonearliercommentonsection7.3.11.1eVdependingW+W6WW%WdepictedܔWdeployedܭWdeploymentWWܭW݂WdeprecatedWderegistereWW(WFWHWMWRWrWzWderegistrationWWdescribe'WeWWWޥWWdescribed+W_WjWkWmWnWoWzW{W|W}W~WہWۊWیW{WݒWݓWݛWݽWWWW6WީWdescribingܟW>Wdescribled݀WdescriptionjWkWmWnWoWzW{W|W}W~WہWۆWWW0W=W@WPW܅WܷWܹWW݄WݗWݾWWWWmW}WWބWޅWWcform۰WWvWcWdWeWWformalisedWformatGWHWvWܑWWW'WWW WW9WqWWformatsWWformattedWWformerWformulationWforward W*W:W W*WfounduWWWfragmentWfragmentationWWfragmentingWframeqWWWWWWframesW'WframeworkjWkWmWnWoWzW{W|W}W~WہW0WnW3WframeworksWfree-stylejWkWmWnWoWzW{W|W}W~WہWfrenchjWkWmWnWoWzW{W|W}W~WہWfroWfromWAW_WbWcWdWiWۉWۋWېW۵WWWWWWW7W9WOWSWgWܘWܝWܤWܩWܫWܶWܺWWWWWW W&W0W:W[WxWݐWWWWWWW"W)Wcinitiator WWinlcude$WinputWinsecureW<Winsecureconveyspsychologicalstate<VinsertLWinsertrelevanttothemnafterintheareaLVinsertedWWinstanceGWIWJW/W>WlWmW/W>W>W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"WsubnetinformationtlvshouldcontZVinsufficientFWGWHWIWJW\WyWWWWWWWWWWW3W4W5W6W7WdWeWfWgWinsureTWUWVWWWXWintelligence:WintentWWintentoffigure24unclearVintentofmiddlesentenceisunclearandpossiblymisleadingVintentioniWintentionallyWinterܤWinter-bsWinter-essWinter-media*WިWWWHW.[/=Change "entities" to "entity" in both places in the sentence. 2006/09/21 2006/04/282EAjayFRajkumarGMember^Technical, Binding_30`36a5.6.1bAaAdd the following text immidiately after the heading and before technology specific SAPs are explained: "MIH_LINK_SAP is the generic media dependent link layer SAP that interfaces between the MIH Function to the lower layers of the protocol stack. For each specific technology interface, this generic SAP would be mapped to a technology dependent SAP."ac8There is no text following the heading for Section 5.6.1d220g2250wAccepted{k) done 2006/09/21 2006/04/284EAjayFRajkumarGMember^Technical, Binding_30`48a5.6.1.2b5.6.1.2b5.6.1.2bnt with notion that one instance of MIH be in a network element or mobile change the followingd210g2234v=Change "entities" to "entity" in both places in the sentence.wAccepted{k) done{k) done{k) done2`40nical, Binding_22`40 dÃvP$Ãv`%ÃvpTÃvÃvoÃvއÃwiÃw Ãw0wÃw@ÃwPxÃw`lÃwp|ÃwyÃwވÃwܖÃxܕÃx zÃx0}Ãx@ÃxPNÃx`Ãxp{Ãx~ÃxpÃxpÃy Ãy Ãy0qÃy@eÃyP Ãy`ÃypÃyÃypÃyrÃzsÃz Ãz0Ãz@qÃzPtÃz`|ÃzpfÃz ÃzrÃzÃà ݲÃ0 Ã@vÃPwÃ`ÃprÃێÃÃÃ&à gÃ0Ã@ÃP Ã`ÃpÃUÃxÃÃà Ã0VÃ@ÃPÃ`ÃpݵÃÃ۔ÃsÃà Ã0Ã@ÃP'Ã`ܑÃpÃVÃ݁ÃyÃܒà Ã0+Ã@ݶÃPܓÃ`ݷÃptÃÃݸÃhÃà uÃ0Ã@ÃPÃ`ÃpܔÃ(Ã5Ã=Ãà vÃ0Ã@ÃPiÃ`kj}vChange AAA to MIH RegistrationwAccepted-Modified{k) done 2006/09/21 2006/04/26d node shall discover its peer remote MIH Function entities. This procedure is not cleary described in the current draft. .d250g2211p- only added new 6.4 and subsections - did NOT make section 8 changes - did NOT try to answer the open questions in group decisionvAThe language is too strong in some cases. May need to change some "shalls" to "may". Link layer may NOT regster by itself with MIH Functon in 6.4.1. MIH capabilities may be discovered by MN and or the Network (not just MN alone in 6.4.3) What happens when any of the specified services are not available or fail for one reason or another? Clarify operational characteristics. These services are invoked during sytsem startup, during link switching etc.wAccepted-Modified{c) instructions unclear 2006/08/22 2030/04/06Marked}EBenjaminFKohGMember^Technical, Binding_42`7SbwifiWwildvWwillZWlWTWUWVWWWܤWzW݃WݑWW WsWWW7WwimaxWwiredsWsWsWsWsWsWsW/gbwithއJwithin@)words@c1.2@^127@20@43gpp@G4@55@7@8.5.2.1@802.21@sb86@FaW>afewconcernsregardingtable13@able@about@Macknowledge@add@addaspaceformaybetomakeittwowordsthisisintable@added@adequately@adopt@walgorithm@all@also@alternative@among@an6analyze@and@z ݃>>andothertlvencodingsitisconceivablethatthese@annex@and@2 B|9>and/or@aa2|9>and/or@a>and/or@a9>and/or@a|9>lwouldn@and@2z4>>>>n@and@2x4>2B2>Hrcupper"W*WGWIWLWOWPWQWRWSWTWUWVWWWۅWۉWېW7WYWZWfW݇WݍWݎWW"W$W,W\W]W^W_W`WaWbWcWdWeWfWgWhWiWlWmWnWWWWWWWWkWtWWWWWWW W W WWWW"W,W7W4W4W4WdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWF8cupper@uppers@usage@Hused@Eusing@Tutmost@Kvalueforversionisnotdefined@vs@dified@stobemodified@.2.23needstobemodified@ chave2W6WWWtWvW|WWWWWWWWWW WWWW#WiW~WWWWW!Wpfigure۴WW݃W>WvW2Wfigures۽WfileݒWfirstۅWWfixܡWfolderݒWforDWۓW۴WܵWaW{W@WfoundیWݒWݓWframemaker2WfromۓW۴W۽WWܾW݃WWfunction۪W݃WfurtherWgܥWݜWgettingܰWgiven݃WglobalWgoingۅWgroupW{Whandover۪W-W:WWކWhandovercommandexmapleproceduresarebeingre-defined-VVކVhandovers:W;Whappened)WhasۅWhelp۴WܵWWzWhelps۪WhereYWhim۴Whorizonbtal:Whorizontal݃WhowWWWWidRWidenticalݜWidsLWMWieܾWiesܾWif۽WܾWinDWۓW۽WWW:WܡWܾW{W}W݃WݒWݜWCW2Win21-06-0691-02-0000-3۽VincludedۓW)WindicatedJWinputWinsert۽Winserting۽Winstead۽W:WW۾40x,IbnTo the following text: "... an interest in one or more event types from a particular event origination point"cChange the following text "..... an interest in a particular or group of event types from a particular event origination point"d506g2224{k) done 2006/09/21 2006/04/28MarkedLEAjayFRajkumarGMember^Technical, Binding_84`30a7.4.2b7Add the sections as described in DCN 21-06-0622-00-0000c5MIH Event Register has not been explicitly mentioned.d588g2226palso added source/dest ids v Modify with interface identifierwAccepted-Modified{k) done 2006/08/29 2006/04/28 MEAjayFRajkumarGMember^Technical, Binding_84`35a7.4.3b7Add the sections as described in DCN 21-06-0622-00-0000c7MIH Event DeRegister has not been explicitly mentioned.d589g2227palso added source/dest ids v Modify with interface identifierwAccepted-Modified{k) done 2006/08/29 2006/04/28 NEAjayFRajkumar^Technical, Binding"bsentencewWۥWۧW۪W۫W۶WۻWW3W7WIWQWܭWWWW(W)W4W5WOWPW^WWޒWWWWWWW W*WpWsWWWWsentences0WއWWseparate*WWser#WservexWWserveriWlWWzWrW"W2W>Wserves[Wservice#W*W?WAWiWpWېW۳W5W<WHWSWܟWܬW0WKWeWzW}W#W(WބW?WtWWWWWWW7WWWserviceprimitiveconceptualabstractiondescribingtheinfoܟVservice-infoHWservice-specificWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWTacbetWvW|W~WހWށWނWރWވWފWދWތWލWޖW1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W0W0W0W0W0W0W0WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWO-wbtitleWrWtWXW2WWtitles/WtlvW|WܕWܚWݿWހWށWނWރWފWwWyWWWWW@WVWtlvencodingbutneithertheschemanoritsurlsneedstoVtlvtypevaluesshallbeuniquetlvtypevaluesraeareassiފVtlvwhenthisinfoquerytypeisspecifiedtheinfoqueryparameܕVܕVܕVhenthisinfoquerytypeisspecifiedtheinfoqueryparameܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVܕVT$baddgetstatusresponsesetVntintable6informationeleaddgetstatusresponsesetVVetextaddgetstatusresponsesetVV etc. 2- Line 39, change "1.1" into "1.2". Also change "TYPE_IE_LIST_OF_NETWORKS" with "TYPE_IE_LIST_OF_NETWORK_TYPES" in the column Name of Information Element. Replace "4" with "Variable" in the Length column. 3- Lines 42-45, remove "List of Neighboring Access Networks." in column Description 4- Replace line 38-49 EAof column Representation with List of TYPE_IE_LIST_OF_NETWORKS c and this one suggests to explain the relationship between IEs. I am confused. mRejectednpvw{ 2006/05/14604/24666666al 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 d af wc@Af 33   33% 33y  33 33fd767g2308{k) done 2006/09/21xENada, Golmie, Member^ Editorial_118`28bA8Replace "values rae assigned" with "values are assigned"8@Af 33  33 33+  33. 33fcA%Syntax error in "values rae assigned"%@A> 33  33 33>d768g2309{k) done 2006/09/21yENada, Golmie, Member^ Editorial_119`4bAwReplace "the list of events that may carried in a message." with "the list of events that may be carried in a message."w@Af 33!  33- 33Z  33i 33fcACSyntax error in "the list of events that may carried in a message."C@C@C@d." xjcthemihlinksapshouldbeshownonthisfigureitwillclarVthemihlinkupindicationincludesthefieldmobilitymanageVthemihonthenetworkmaybroadcast/multicastinformationcVthemihprimitivesdonotincludealinkidentifierthustheVthemihsapisnottechnology-independeforexamplethemihVthemihfisnotashimlayerbutisafunctionitspansmult۪Vthemnmayusel2transportforexchangingmihinformationwVthenamelinkconfigureparametersresponseisnotappropria܂Vthenameofthesectiondoesnotmatchthenamedefinedint܁VthenamesofthetwostacksshouldbechangedtoreflecttheVV V V}careaIWLWWnWWW'WareasW W'WarfejWargumentsIWarrivesWarrowWarrowsvWarticle۰WݥWarrives WarrowWarrowsvWarticle۰W۰WݥWarrives WarrowWarrowsvWarticle۰W۰WarrowWarrowsvWarticle۰W۰Wma8.5.2.5a[8.5.2.5-12\8.5.2.6]8.5.2.7^ᖃ8.5.2.8ʃ_8.5.2.9`8.5.3.11bd8.5.3.12e8.5.3.13c8.5.3.15df8.5.3.17e8.5.3.188.5.3.19qig8.5.3.20ޏh8.5.4.1ބ8.5.4.2ޅ8.68.6.1r8.6.1.1O8.6.1.2ۏኃaܚWWa4ܚVa-1-WWWކWސWޑWޒWWiWWa-2ޓWa2WsWannexۀWW-WsWtWWWwWކWސWޑWޒWޓWWWWW5W6WiWWWWWannexaVxaDVDVxaDVDVxaDVDVaDVDVWWWWWWWWWWWWWWWWWWWWWWWWWWWWd=cmovedKW`WqWmovementWmoving:WWmsblWmuch(W)W<WWmulti-hopݓWmultipleۋW۪WIW|WܤW!WݐWWWWWW WWmultipledefinitionsofmnVmustiWCWHWRWTWUWVWWW`WmWkWWWWWWWWmvnoWn/WWn-layer/WܟWn-layerasubdivisionofthelayeredprotocolarchitecturec/Vn-userܟWnameۤW۽W܁W܂WWWnamesW>WWWnamespaceCWnasWnas-port-typeݔWWnasa>WnativeWnaturalwWxWyWzW{W~WWWWWWnatureAWܖWWnavigationWncms2WneWnearby(W*Wnecessarily*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*WlvresolutionW\WWWWWWWWW>WWWWWresolveUWWresolvedWresolvedbycontribution21-06-0692-00-0000-mVresourcesۅWrespective*WەWrespondingWrespondslWresponselW۔WWރWW#WresubmitWretransmissionWretransmissionsWretrievalZWretrievelWretrievedlWretrievingRWWreturnWction receives an MIH Event Registration. On the other hand, an MIH User could directly send an explicit Link Event Registration Command. Since there is a clear separation between MIH Events and Link Events, the first option is a better." Is an MIH User supposed to have access to Link Primitives ?@A> 33  33 33> 2006/05/14 2006/04/28LEAjayFRajkumarGMember^Technical, Binding_84`30a7.4.2ing_67`15a7.2.2.2can only be received afr^editorialWWWWW׃؃كW W!"#$&()*,-./456789<=>?@GIWKMNQRWT^cdefgfgfgfgfgfgfg)>chandovers;WݍWWYWWWWWhandoversduetothemobilenodemovementarefacilitatedbyVhandoverstatus6WhappenWhappensWWhard*WW?WhardwareWhas+WgWpWvWxWۄWۅWۉWېWۤWW)W|WܕW݅WݍW>WLWMWYW1W5W>WWWWWWWWWW!W.WWWWWWWWWWhaveېW'W-W7W:WCWܠW0W݃WWW"W$W$W$W$WjWgWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWWW"W"W"W"W"W"W"W"W"W"W"W"WW ^technicalWWWWWWW WWW'W+W0W1W3WAWEWHWIWLWOWPWRWaWbWkWzW{W}WW݃WݍWݎWݒWݓWݔWݕWݖWݗWݘWݛWݜWݜWݜWݜWݜWݜWݜWݜWݜWݜWݜWݜWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩWݩW*clinesܬWWW0WlinkCWDWGWIWJWLWOWPWQWRWSWTWUWVWWWcWdWeWfWۄWۅWۉWێWېWWW-W8WQWRWSWYWZW[W`WgWhWiWlW܂W܃W܈WܡWܫWܰWWW W0WAWaWbWݍWݛWݺWݽWWWWWWWWWWW W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W#WWccommitۃW6W\W_WaWdWWWWWcommnadWWWWWW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WWcommunicatesWcommunicatingTWcommunicationەW3W W*W3W>WcommunicationshWcomplete/W0W4W5W9WۇW-W܉W܏W WWWDWޗWޭWޮW޲W޳W޷WWWWWWWW!W"W&WMWNWRWSWWWߋWcompletedۂWcompletelyYWܰWcompleteness)Wcompletenessconcisenessgrammar)Vcompletion*WcomplexityBWWW/W`WcomplianceWܛWW%WޚWW W:WxWcomplicatesWcomponentsWcomposed:WܤWݐWcomposedofmultiplemediatypesitisthehandoverdecisionݐVcomprehendedWbcforwarding:W W*Wfound|WmWWfragment WfragmentationW Wfragmenting WframeWW WpWqWWWframesW'Wframework0W3WwWxWyWzW{W~WWWWWWWframeworksWfree-stylewWxWyWzW{W~WWWWWWfrenchwWxWyWzW{W~WWWWWWfroWfromWAWcWdWiWۉWۋWېWWW7WSWgWܤWܫWW W&W0WݐWWWWWW"W)W,WIWvW5W6WtWvWWWWWWWWWWWWWW!W.WWWWWWWWWWfront2WfuctionۉWfull[W W W W W WW8WqF4bnetwork W"W#W?WAWUWVWiWpWۘWۧWWWW,W<WHW[W܅W܋WܡWܤWܬWܾWWW3W9WIWMWOWPW݃WݺWWWWW W"W#W$W%W.W8WAWOW]WXWfWhWrWtW|WWWWWWWWWWWWW!W"W'W-W1W5W8W>WsWuW|W}WWWWWWWWWWWWWWW"W"W"WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWcbsWܵWWbsc+Wbssid[WbstnܵWbuffering WbuildupWbulletWbullet1needssomeclarificationVburdenWbusinessYWWbusy݃WbutDWiWۄWېWۓW۪W:WZW|W܋WܖWܚWWܚWWܚWܚWܚWܚWܚWܚWW۪WWW:WZW\W|W܋W܋W|W܋W܋W|W|WW\W|W|W x*vAThe MIH Function aggregates disparate interfaces with respective media-dependent lower-layer instances (media-dependent service access points) into a single interface with the upper layers (the MIH SAP) "making the inter-media differences transparent to the extent possible.."@A  wAccepted-Modified{k) done 2006/09/21 2006/04/24+EQiaobingFXieGMember^Technical (was Editorial)_32`52a5.8.3b Remove 5.8.3.cASection 5.8.3 is just about general usage of MIH services by an MIH user. This has been described in enough details in the previous sections. This is therefore no need to repeat the same informantion here again.@A  33d247g2253wAccepted{k) done 2006/09/21 2006/04/24?EQiaobingFXieGMember^ Editorial_42`20a6.3.1ba6.3.1ba6.3.1bifferences fully transparent to the upper layers. 4@hnical, Binding_30`36a5.6.1 h:bkReplace the definition of horizontal and vertical handovers with the definitions contained in the RFC 3753.cADefinitions of Horizontal handover and Vertical handover are confusing due to the misuse of the term "Access Network". According to RFC 3753, the definitions are quoting: "Horizontal handover 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. Vertical handover This involves MNs moving between access points of different type, such as, UMTS to WLAN. Access 33  33 33,  334 33fcA(Syntax error in "Link Command originate"(@A> 33  33 33>d291g2242i Eunah KimmAccepted{k) done 2006/08/21 :ENada, Golmie, Member^Technical, Binding_42`24 2006/04/2813:-wAEAjayFRajkumarGMember^Technical, Binding_42`19a6.3.1b="handover module" should be replaced with "network selector".c6"handover module" is never defined or used elsewhere. d314g2239wAccepted{k) done 2006/09/21 2006/04/28BEAjayFRajkumarGMember^Technical, Binding_62a6.3.9bThe third primitive in the flow (MIH_Get_Info.confirm) should be removed. The last primitive (MIH_Get_Info.response) should be replaced with MIH_Get_Info.confirm.cRSame as Comment on Figure 18. The information flow should only show 4 primitives. d473g2240i Eunah KimmAcceptedpneed new drawings - donev8Refer to 21-06-0642-02-0000-Information_service_flow.pptwAccepted-Clarified{k) done 2006/09/21 2006/04/282006/04/2822CEAjayFRajkumarGMember^Technical, Binding_63a7bJRedefine them whereever there is a discrepency as .request/.confirm pairs.cLAll .request/.response pairs in Section 7 should be semantically corrected. d482g224428c1|vbycommentfromsection7adoptsimilarresolutionascommenVbycomments287289292293294295andcontribution21-06-0Vbycomments482508514515267whichtakecareofconfirm/reVbycomments493494Vbycommment527/626LVbycontributionfromeunahandcomments473474475477Vbyresolutionofcomment346Vbyvote1-4V/]vasdefinedinsection8.4.2.13hVaspartofcomments142128226Vaspercomment555VVWVaspercomment555resolveitthesamewayUVaspercommenterrequest{Vaspercommenter'srequestzVaspercontribution21-06-0691-02-0000-3۽VEVYVaspercontribution21-06-0705-00-0000-lDVaspercontribution21-06-0748-00-0000issue46-linkgetinfVasperrequestfromcommenterVaspectsWassignedZW-WWWWWWassignmentWassumesWatWNWW"WVWWattaches?Wattachment1WWattentionWauthenticationWWavailable{WdWWW?WWavialableWavilablenWWbWWbackW!W!W!WbackW!W!W!W!W!W!W!W!W!Wa){k) done 2006/09/21 2006/04/286EEleanorFHepworthGMember^ Editorial_48`30a6.3.4b~For the multiple octet length representation, show that first octet is length of length which is followed by the value length.c=Diagram does not clearly represent the text below the figure.d405g2254pneed help to redraw (Visio){k) done 2006/09/21 2006/04/282000pworthGMember^ Editorial_50`31a 6.3.4.2.3b Add referencec0This need to be re-written as a proper referenced421g2256{l) none needed 2006/08/23 2006/04/28 EEleanorFHepworthGMember^Technical (was Editorial)_51`42cA4This is not an exhaustive list. What about Galileo and GLONASS non-US satellite positioning systems. There are also other terrestrial navigation systems not mentioned. Which one does 802.16 use? It is difficult for 802.21 to try and specify an exhaustive list of all possible location determination schemes. 4d4255݅@F4p݋`ݍcAqݎbݒpݓvAݔ@bArݖGݗbA3ݛb1ݜpA<ݭ@ݸbQsݾGtd9cu@zbAcB}cAb@c^wbcAbObAp{AcA Ec ^+bAAbA5bA bA"bAcAvA#F+FddFdFdFdDFddBDFddb5.6.2.1WW5.6.2.28W5.6.3.18W5.7(W)W5.7mediadependencemediaspecificamendments)V5.7mediaindependencemihprotocol(V5.7.1(W5.7.1mihprotocol(V5.8nW5.8.3+W518/525`W52(W541W580W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W]W6ZW[W\W%W&W)WRWܑWܔW,W|W6.1W6.2.5.1ޔW6.2.5.1mihcommandsޔV6.3;W6.3.1`WܶWW6.3.2AWBW6.3.3YW6.3.4YWܗWܷW6.3.4xxinformationquerytypeܗV6.3.4.1]W6.3.4.1.2^W6.3.4.1.4AW6.3.4.2.1BW6.3.5`W6.3.6aW6.3.7bW6.3.8BWW݀WWW/W`WߞWWW63~W65W690vWCbcontribution{WkWWW=WtWvWwWxWyWWWWcontrolpW۳WiWkWW5WpWtWWWWWcontrolled>Wcontrols>WconvergenceWconvertWconveyWW.W.W.Wcbaddanewentryintable14ݛVaddanewentryintable15ݛVaddanewlinewiththefollowinginformationVaddanewparametersessionidentifierVformationdVdVaddanewparametersessionidentifierhVanewparametersessionidentifierhVhVaddanewparametersessionidentifierhVhVndVdV- >cCce-procedure, an acceptor is "an OSI-service-user that receives a deliver primitive and as a result may issue one or more submit primitives." Names are defined for the submit and deliver primitives used by the requestor and acceptor: request, indication, response, and confirm. - A request is a submit primitive issued by a requestor. - An indication is a deliver primitive received by an acceptor. The indication is related (in a way that is specific to the OSI-service) to the request isDsued by the requestor. - A response is a submit primitive issued by an acceptor as a result of the indication received. - A confirm is a deliver primitive received by the requestor. The confirm is related (in a way that is specific to the OSI-service) to the response issued by the acceptor." The excerpt shows that, in a communication between remote peers: 1. A .response primitive can only be issued in response to an .indication primitive. 2. A .confirm primitive can only be received af/28 *vwAccepted-Modified{k) done 2006/09/21 2006/04/28 ,EAjayFRajkumarGMember^Technical, Binding_3a1.2bTwo options for the resolution: (1) Make the MIH Function block a rectangle between the upper layers and the lower layers. (2) If a specific reason for the block to be L-shaped exists, it should be explicitly stated in the text from Line 41 to Line 45.cA#Why is the MIH-Function block L-shaped? The text from Line 41 to Line 45 correctly indicates the relationship of the MIH FUnction with upper and lower layers. The L-shaped block implies some sort of horizontal relationship with the upper layers that is not explicitly mentioned in the text. #d16g2232iMathieu Peressej Peressej the handover operation is successful the MIHF in serving PoA (PoS) may start forwarding packets to MIHF in target PoA. PoS~@v[abthanݗW%W+WWWthat W?WAWIWLWRWTWWWdWfWۉWېWەW۫W W#W)W,W5W7WTWUWVWWWhWtWyWzW{W|W~WܕWܟWܤWWWW)W+W.W3W9WIWPW݃WݗWݸWWW%W2W8WWނWކWދWތWWWmWnWrWtWwWyWWWWWWWWWWWWW"W(W,W1W8W>WkWlWuWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW ctexttextbetweenline43page43andline12page44isnotabouKVtextdoesnotreflectthedependencyofthetransportmechanVW#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W@ hcnetworknetworkdetectiondefinitionisredundantVnetworkidshouldbelinkidLVMV V V V V V V V V V V8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8WjrenewalݍWreplaceW{WWreplaceperformanceofaccessnetworkswithconfigurationanVreplacethelastmihgetinforesponsebyaconfirmprimitiv{V{VVVsent|WrepresentationW,WrequestW>Wrequests>Wrequire WrequiredWresXWresponseWW>Wrfc?Wroles>Wsame0W>Wsamecommentascomment170Vsap W1W3W>WsapsWsayingWschemaBWWsdoWsdosWse,Wsection<WaWuWW+WݻW+W>WjWsee@W+Wseecomment315andchangefigureaccordingtoit@Vseems>Wselected?WsendKWsense+WseparationKWserviceBW>WsessionWWhWset+W|W Wshall+Wshould?WuWWW WݴWTWhWshouldbediscussedcarefullyݴVshouldthemihusersknowaboutthesessionidhVhVl lvserviceܬW0W>WBWWW2W?W{WWservice-specificjWservice/sessionݓWservices۳W{WW?Wserving"W*WsessionWݓWWsessionsݓWWsetێWWW!WsetsWsettingWshallZWOWWWshalls{WshouldZW-W WzW\WWW W4WWWshouldbeacceptedaspercontribution641fromeunahinjunzVshow\WshowingZWWshown۴Wside݃WsignalingWsignificantWsimilarWWsinceWWVWsincemihfdoesnotreallymakeanypolicytypedecisionsitVsincewearenotaiminginthepresentstateonroutingforwVVsingle*WWsipWWsipcanbeusedformobilitymanagementandsolet'skeepthVsoWWWWWSWspecifically݀WspecificationHWspecifiedlWWWW{WspecifyܾWWWWSW p_‚B()*Ãܰ҃8nZ[ڃ၃ႃ‚C+܃݃ೃk‚DܱI{‚E:᷃‚F7ݑރḃ‚GăӃឃẃểrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrLM}@A‚TKȃɃʃ˃ܶ׃؃كNOPQݓ‚UZ[ےۓ̃̓΃ <=>?@Aܷڃۃ܃RSݔ‚VۑσЃ!"B݃ރTUݕ‚W߃V|ݖ‚XX\у҃#$CDEܸܹܻܺW݉‚YYFX~ݗ‚Z]^%&Gܗܼ‚a'H‚bӃ(Yݘ‚c‚dԃZ‚e_`)Iܾܽ‚fa*‚gbՃփJKLܿ[ݙ‚i׃M\[bchangethevaluefieldfromݘV@Vchangethevalueto|VchangetitletorVtVchangeto(V)Vchangetoamediaspecificinformationrequest/responseprimVchangetocdma2000-hrpdRVchangetoinclude802.11whichalsomayhavethiscaseinVchangetomayinfluencehandoverdecisionVchangetomobilityextensionsof802.16andchangereferenceVchangetopolicyengineentityVchangetoprovideinformationabouttheavailabilityofacceVchangetoregisterVchangetoreliableserviceeVchangeutmosttoatmostgVabouttheavailabilityofacceVVVVVVVVVVVVVVVV'Abcollects@comma@common@Rconceptual@eptual@ts@comma@common@Rconcept@Rconcept@common@Rconcept@mmon@Rconcept@omma@common@Rconcept@common@Rconcept@eaccurateclassificationscheme@common@Rconcept@common@Rconcept@ubmannerAWvWmany܊WܡWmapWmapped2WmappingDWVWWmapsAWuWmask-WmatchWmaterialWmatrixsWWWWWWWWWWWWWWWWWWWWWWWW"W#W,W-WAWFWGWMWOWPWQWRWSWTWUWVWWWXW_WdWfWiWsWuWWۂWۉWېW۫W۳W۶WWWWWWW#W,W3WCW\WeWrWyWzW{W~WWܪWܫWܶWW;WIWQW_WtW݊WݍWݎWWWW W W"W#W$W%W&W+W/WOWTWWWWދWތWޞWޠWޡWުWޫW޿WWWWWWWWWWWWWWWWWWWWW WWWWW.W3W4W>W@WAWJWKWSctechnologyېW:WܰWW0WWWWWWtechnology-dependentWtechnology-independe0WWtelltWuWWtense7Wtenseconsistency7Vterm,W.W:W;WW-W]WWWterminalۋWۏWOWWWWWterminalsۋWWterminology>Wterms?W@W۲W۽W:WWWterrestrialWtestWtextW WAWKWeWiWrWsWەWW{WWWWWW W WW"W#W$W&W,W-W2W4W5WIW|WWWWWWW<W=WtWuWvWwWxWyW}WWWWWWW2W2W2W2W2W2W2Wctexttextneedsimprovement@texts@that@the@.\XKdNlK> ?the1sttwosentencesintheparagraphrepeatswhathasalre@thecontentinsection7.2.2.1section7.2.2.2anditrespec@thecurrentmihreferencemodelfor3gpp2triestoshowhow@thedecriptionisthesameastherequest@Lthedefinitionoftheparameterforsupportedisqueryismiss@ thedefintionoftheinformationserviceschemaisanimplem@ctheexamplequeriesshouldbeinaseparateappendixandnot@theinformationcanbeobtianedeitherbytlvorschemahowe@T41)pg- Deleted bits 3 and 4. - "Length is not included as part of Table-6 anymore": when did that happened?vGDelete bits 3 and 4. Length is not included as part of Table-6 anymore.wAccepted-Modified{k) done 2006/09/21,EDavid FFamolari^Technical, Binding_16`44a5.3.1bAvChange: " In a network model that encompasses a MIH proxy, the MIH Network Entity that interfaces with the MIH proxy does not have a direct connection to the MN and therefore does not constitute a MIH PoS for that particular MN. " to: " An MIH Network Entity may not have a direct connection to the MN and therefore does not constitute a MIH PoS for that particular MN. "v@A> 33 t 33>c2The use of the term "MIH proxy" should be avoided.d114g2391i Qiaobing XiemAcceptedwAccepted{k) done 2006/09/21-EDavid FFamolari^Technical, Non-binding_140`1a Annex A-1cex A-1cnnex A-1crameters" 1i 1bA   UU-  33/ 33H  33I  f h 33  33cފ@ފ@ފ@cފ@މcފ@ފ@ފ@nd functionality of MIH Function."[)big2278v'Mention that values 7-255 are Reserved.wAccepted-Modified{k) done 2006/09/21 2006/04/28EEleanorFHepworthGMember^ Editorial_53`41b+remove for loop, and split into two tables.cKThis table is confusing; the use of for loop does not aid understanding. d432g2280p)how? please provide marked up text change{c) instructions unclear 2006/09/21 2006/04/2812EEleanorFHepworthGMember^ Editorial_110`16a8.1b Clarify text.c>Not clear whether this is an MIH protocol or MIHF protocol d681g2287{k) done 2006/09/21 2006/04/282006/04/28Member^ Editorial_112`5a8.3bchange to register.cTypo: rregister d700g2290{k) done 2006/08/29 2006/04/28 EEleanorFHepworthGMember^ Editorial_112`6a8.3cWtypeJW^WۄW:WCWRWYW|WܾWW W݃WݺWWWWaWtWWqWtWvWWWWWWWWWWWWWWWWWWWWWWW WWW9WDWWWWWWtypeiepoacapabilitiesthesecurityandqoscapabilitiesoܾVtypesIWYWܤWWݐWWIWWWWWWWWW3WtypicallyܤWܱWݐWsWtypicallyinaheterogeneousnetworkݐVtypicallyinaheterogeneousnetworkcomposedofmultiplemeܤVܤVܤVVܤVܤVܤVܤVܤVܤVܤVܤVܤVgeneousnetworkcomposedofmultiplemeܤVܤV)cqall mih primitives could optionally have session identifier which may be applicable for MIh remote communicationsd576g2250iMathieu Peressej0Should the MIH users know about the session ID ?wRejected 2006/09/21 2006/04/26ESrinivasF Sreemanthula^Technical, Non-binding_97`10a7.4.11bgrequest to reconsider the use cases and remove such remote MIH communications out of the specification.cAMIH Handover prepare request and response messages in remote scope may require intertechnology inter-PoA connection. 802.21 assumes presence of such an interface but does not facilitate any interface@A  33d642g2226vRefer to contribution 21-06-0686-01-0000_MIH_Handover_Procedures....for flow diagrms Also refer to comment 495 no suggested text and clear remedy as well.wRejected 2006/09/21 2005/11/06ESrinivasF Sreemanthula^Technical, Non-binding_86`48a7.4.14a7.4.148a7.4.14 2006/04/26QkmihfݓW\WWWUWVWYWmihf-idVWmiisAW۳WWmisunderstandWmobiledWWmobility\WmodeOWmodelWmodifiedWmodifyWmodifyingWmoreۓWݓWwWxWyWzW{W~WWWWWWWWW W:WmoveWmuchWmultipleWWWmvnoWnamedWnamesYWnecessarilyWnecessaryWWneedAWۓWW\WvWWWWWWWWVWWWWWneededwWxWyWzW{W~WWWWWWWWW*bofWWWWWWWWWWWWWWWWWWWWWWWWWWW"W"W"W"W"W"W"W"W"W&vby comment from section 7. Adopt similar resolution as comment .... Keep MACNewPoA Remove: MACOldAccessRouter MACNewAccessRouter w Superceded 2006/09/21 2006/04/26ESrinivasF Sreemanthula^Technical, Binding_77`51a7.3.13.1b;Limit the scope of MIH capability to "L2 MIH capability". cALink detect only indicates what is in the braodcast (or state-1 query), so it provides MIH capability of the PoA only. Lack of MIH capability on PoA does not mean that there is no MIh capability in the network since it could be provided deep in the network.d547g2248vThere is only one notion of MIH capability. It may be avilable at link layer or from L3 but we dont need to make a distinction between that.wRejected 2006/09/21 2006/04/26ESrinivasF Sreemanthula^Technical, Binding_83`1a 7.4.1.1.2b&add a new parameter session identifieridentifieridentifiera8.5.2.7.7.7.7d832 2006/04/26BX:bmihlinkdetectedeventanewlinkisdetectedݛVtobeamihlinkdetectedeventanewlinkisdetectedݛVݛVtanewlinkisdetectedݛVݛVdetectedݛVݛVbasicurltobea~V~Vtaprefixmihbasicurltobea~V~VZ0crequestsiWmWܕWWWrequestsetsmWWrequireW WWrequired"W)WaWWWW WWWWWrequirementWWWrequirements۟WrequiresWrequiringWWWrerence(W,Wreserve"W"W"W"WWYWYWYWYWNcexcludingwWexclusiveܟWexcutionWexecuteېWexecution\W]W^W_W`WaWbWcWdWeWWexhaustedWWbexpected]W^W}WxWzWWexplainhWW*WkWexplainorreformatthechannelrangeinformationelementVexplainedDW2WWW[W4WexplainingWexplainsW/WexplanationjWexplanatoryWWWexplicitWexplicitly,WWWexplicitlyreserve128generaland127otherforfutureVexposed0WexpressWexpressions/WextendedAWiWݾWݿW}WހWށWނWރWxWzWWWextensibilityAWWWWextensibleWWextensionsWextenttWextra Wextratextisrequiredheretoclarifythepurposeandopera Vextract#WextraneousWWW#WW_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_WXbfigure@`first@fix@flow@for@forcing@Jleoctetlengthrepresentationshowthatfirst@Jcalmi@Jrstcommentthemihmightalsonotifythelocalmi@J)4binformation@list@node@provide@register@removesentence@'replacethedefinitionofhorizontalandverticalhandovers@tretrieved@asplit@theymusteitherbemergedintooneoroneofthemberemove@thresholds@Utoc@/with@lds@Utoc@/wish@gtypes@/wish@beremove@schemathisdoesn'tmeanyouhaveto@Utoanewvalueallocateanewoneorsplittheentry@/wired@candothertlvencodingsitisconceivablethatthese@destination@differences@6easily@Uifcomment9isacceptedtomodifythedefinitionsofhorizo@yimprovement@itisnotclearwhatisthedifferencebetweencommonandot@linkparametertypedefinitionsisinsufficientandneedsto@miheventderegisterhasnotbeenexplicitlymentioned@Wnot@overload@repeat@show@text@l6^ 2006/09/21aEFarrokhFKhatibiGMember^Technical, Binding_71`55a7.3.7b-Update the primitive prototype appropriately.cAOn page 41, it is stated that link configure thresholds command is used to configure the thresholds for various link layer events such as link going down. However, the primitive does not carry prototype to specify the event for which the thresholds configuration is requested.d513p2- some one needs to propose details for the changevHLink Configure Thresholds updates thresholds for Link Parameters Change.wAccepted{b) awaiting missing input 2006/09/21bEFarrokhFKhatibiGMember^Technical, Binding_75`8a7.3.10bAdd additional event codescCLink Down add other causes: Authentication failure, Billing failured524v1 Please refer to: 21-06-0754-00-0000-LB-Issue-25 wAccepted{i) to do 2006/09/21d0{l) none needed 2006/08/27 dEFarrokhFKhatibiGMember^ Editorial_8989 vc5WWcallWWWcallitaspoaidentifieranddonotspecifymacaddressVcallonelocalentityandotherremoteentityVV"W=WWWcan'tݓWcannotWWWcannottracethecontributionVcapabilities{WWWcapabilityܬWWWcapableWcareWcarefulWcarriedەWWށWcarriesWcaseەWWޏWWcases{WcategoryWcdma2000&Wcents/minuteWcertainTWݓWWWWchange)WgWlWۉWۛW۴WWWWWW-W W1WaW{W}WݒW"W/W4W5WOW\WWWchangeaaatomihregistration}Vchangearealreadytomayalreadybe1VchangeasfollowsVVchangeasfollowswhichmaybewirelessorwiredۛVchangeentitiestoentityinbothplacesinthesentence/Vchangefigure3۴VlV}kMIH function in the network may advertise its MIH capability not only over the backbone network but also over the air interface. This case would be when the network doesn't support media specific MIH capability broadcast. mRejectedvSby comment 250 as per contribution 21-06-0611-00-0000-MIH protocol section updatew Superceded 2006/09/21 2006/04/28~EAjayFRajkumarGMember^Technical, Binding_30a5.6bpA double-headed arrow labeled "Socket APIs" should connect the "MIH Function" block to the "L3 Transport" block.cjOn the left side of the "MIH Function" block, the figure should have another block called "L3 transport". d213g2246i Vivek GuptakAPIs (Application Programming interfaces) and such are outside the scope of the specification. One implementation may use sockets, other may use something else. mRejectedvbased on request from commenterwRejected 2006/09/21 2006/04/2812EAjayFRajkumarGMemberarGMemberAjayFRajkumary YcAThe current MIH Reference Model for 3GPP2 tries to show how MIHF fits within 3GPP2 network. However 3GPP2 networks do their own system design. 802.21 has no business in designing 3GPP2 networks. Instead this section should focus more on how 3GPP2 networks can work with other non-3GPP2 networks with help of MIH capability. Mobility management and handovers within 3GPP2 networks are outside the scope of 802.21. Trying to change basic structure of 3GPP2 networks is also outside the scope of 8B02.21d200g3212p9This should be a "superceded" case. Nothing is done here.v;as per contribution 21-06-0691-02-0000-3GPP-3GPP2AmendmentswAccepted{l) none needed 2006/09/21100SrinivasF Sreemanthula^Technical, Binding_83`47a7.4.1.2bAdd a parameter to MIH_Capability_Discovery.Response SupportedISQueryTypeList | List | Set of supported IS query types | List of supported IS query typescParameter missing.d580g2235wAccepted{k) doneOcsetsWWsettingWsetupWseveralۃWۉW۝WW WWseveraldashescanallberemovedwithoutlossofcontent۝VshallvWwWW{W W WOWWWW8WtWshalldoesnotmakesenseinthiscontextthewordshouldonVshareWWsharingW}T|bchangeendofsentencetotoeffectseamlesshandoveracrossۻVchangefromeventservicetocommandservice(VossۻVۻVVy[ 2006/09/21 2006/04/26\ESrinivasF Sreemanthula^Technical, Binding_129`28a8.5.1.1b*copy table from section 8.5.1.2 to 8.5.1.1c0Table missing (this is a capability negotiation)d821g2238psame table copied to 8.5.1.1 wAccepted{k) done 2006/09/21 2006/04/26]ESrinivasF Sreemanthula^Technical, Binding_122`36a8.4.1.8b.Replace "Network Identifier" with "Media Type"c)"Network Identifier" is a confusing term.d786g2239vUse "Link Type"wAccepted-Modified{k) done 2006/09/21 2006/04/26_ESrinivasF Sreemanthula^Technical, Binding_74`10a7.3.8.2bremove: 4:SIPc1SIP is not used as a mobility management protocold517g2242wAccepted{k) done 2006/09/21 2006/04/26aESrinivasF Sreemanthula^Technical, Binding_130`46a8.5.2.5bHAdd another parameter "LinkType" LinkType | Media type of the link the link the link the link the link missing.d580g2235wAccepted{k) doneecwhereeWېWWWAWBWZWjW W%WWWW WWWwhereasWWoWWWWWwhereverܥWeas%W&WWEWFWGWHWwhereverܥWܥWeas%W&WWEWFWGWHWwhereverܥWܥWWHWwhereverܥWܥWcdiscoveringېWdiscoveryWWOW1W|WWW?W}WWWWdiscoveryregistrationandeventregistrationmechanismsareVdiscussWUWdiscussedDWpWvWWWdiscussionAWWWWWdiscussionofhow802.3networkscangetdirectinternetaccVdiscussionoflogicalnetworkreferencemodelusesroamingcVdispatchmWdispatched7WdistinctWdistinguish:WWW!WdistinguishedWdistributedWdoeWfWlWCWWYW6W?WtWvWWWWWWW WWW>WjWWdoweneedtodefinewhatnetworkinitiatednetworkcontroll>VdocWWW"W@W@W@WޔWޔWޔWޔWޔWޔWޔWޔWޔWޔW 8vcontrol۳W5WWjWconventionWconvergencejWcoreWcorrectWWcorresponding۔WWcostWWWW?WWcountryHWcoupleWcoversݓW&WcreateۓWݓWcreateseparate802.21listofnetworksۓVcrossTWcsݓWjWcurrentTWݓWWWWd01.00WWWd01.09WWWd1.0 WdataWdatabase۳WdealsWdecideWdecision?WdecisionsWdeeperWdeeringWdeferredWdeferred/rejectedWdefine۔WݓWWVWdefinehorizontalandverticalhandoversindefinitionsectiVdefinemihftransactioninthedefinitionsection۔Vdefineversionas1andreservethevalue0forother/futureVVdefinedZWhW4W5WWWWWWjWWdefinesWWWdefiningW>Wdefinite/clearWdefinitelyWdefinitionۉWێW۔WWV vcomment`WWIWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWeWeWeWWWWWWWWWW W%WCWDWXWYW[W\W]W`WyW݀W݄WݓWݙWݞWݟWݠWݡWݢWWWW7WEWSWmWrWsWxWzWcomment104ܦVcomment492EVcommentisintwopartspart1istoaddtypeienetworkcap Vcommentisunclearastospecificallywhatpartisunclear݀VcommenterۊW_WݏWcommentertoprovidesuggestedtextݏVcommentersݓWcommentersagreeapplicabletoesandcsbutonlyundercertݓVcommentsZWWWcommunicationW3WݓWcompleting WcomplianceܛWcomprehensiveWWconcern WconditionWconditionallyܗWconfidenceQW\WVjcmiheventregisterhasnotbeenexplicitlymentionedLVmihfunctionshouldrejecttheregistrationifthemihuserVmihgetinfoconfirmprimitiveisnotdefinedVmihgetinfoindicationshouldbemihgetinforequestVmihhandovercommitisimproperfor802.21scopethefunctio_VdVmihhandovercommitshouldbeavailablebetweenmihfclientVmihhandovercompleteisimproperfor802.21scopethefunct`VeVmihhandovercompleteshouldbeavailablebetweenmihfclienVVmihhandoverinitiateisimproperfor802.21scopethefunct]VbVmihhandoverinitiatemihhandoverpreparemihhandovercomm\VaVVmihhandoverinitiate/prepare/comVmihhandoverprepareisimproperfor802.21scopethefuncti^VcVmihhandoverpreparerequestandresponsemessagesinremoteVVVV("€€1˃,WYu&W11σಃ12ЃY~13>14ݛW\fᄃ1415l15SӃᆃᇃ1618یփ>Wഃགྷྃ7WWXW19@ܵփ(@a20ૃYW21v22zBހ=Wȃl23ނq24ޓ r2529ۏ3!W30-WކiW5݃6ZABۃ݃ރ߃ݔWݕWݖWVtqrඃ࿃ƒ܃ᎃ7$݃n829۽Wໃf-24f-25f-3۴f-30f25ܑf27ܔfigure۽WW-WWW!W&WiWfigure10V&Vfigure18Vfigure22Vfigure3!Vfigure30-ViVfigure9۽Vt-1t-7t18ܒܓtableݔWݕWݖWݛWWWXWYWtable14ݛVtable18WVXVtable20YVtable6ݔVݕVݖVIvASIP can be used for mobility management and so let's keep this...wRejected 2006/09/21 2006/04/26ESrinivasF Sreemanthula^Technical, Binding_131`2a8.5.2.6bCAdd another parameter "LinkType" LinkType | type of the link cu"Link Type" (Network Identifier) parameter is required for MIH users to determine which link is generating this eventd828g2243vby comment 824w Superceded 2006/09/21 2006/04/26MarkedMarkedESrinivasF Sreemanthula^Technical, Binding_131`21a8.5.2.7bEAdd another parameter "LinkType" LinkType | type of the link cu"Link Type" (Network Identifier) parameter is required for MIH users to determine which link is generating this eventd830g2244vby comment 824w Superceded 2006/08/29 2006/04/26ESrinivasF Sreemanthula^Technical, Binding_131`30a8.5.2.7b9Remove: MACNewPoA MACOldAccessRouter MACNewAccessRouter c1dependent on earlier comment on section 7.3.11.1 d832g2247t`‚V˃؃ݿӃઃe‚W ܉?ۃaaeMRh‚XۺfO[kྃ‚YۖÃ{5Rc݈$4kޖਃ Aᛃ#‚Z@*:ވDOV mHbchangepointofattachmentstopointsofattachmentorpoa'sVepointofattachmentstopointsofattachmentorpoa'sVVfromthisprimitiveisissuedbyupperstkVkVep90line46fromthisprimitiveisissuedbyupperstkVkVpcneighborIW?WneighborhoodIWneighboringܡWWWneighbors}WneighbourWnet-sapuWnetlmmWnetman>Wnetowrk۴WnetscapewWxWyWzW{W~WWWWWWnetworWnetworkۉWۋW۴W۶W۽WW WW-W:W;W<WIW܋WܡWܤWܬWܭWܾWW+W3WݐWݺWWWW W"W#W$W%W/W4W5WOWYW]WaWXWfWgWhWiWrWtWuWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWW W!W"W'W1W5W<W>W?WLWMWiWsW|W}WWWWWWWWWWWWWWWWWW"W"W"W"W+ hbAR  33:  ;  <  33R."d243g2244 2006/08/03MarkedE Ulises Olvera^ Editorial _32`39a5.8.2b9"...described in Table 33a..." Also need to add Table 33acvChange "table 33a" in line that quotes "...described in table 33a, a direct...." Note: that Table 33a does not exist.d245g2245 2006/08/03E Ulises Olvera^ Editorial_35`8a6.1.2b:"... from one access network to another will result in..."ceRemove the "s" from "results" in the line "... from one access network to another will results in..."d261g2246 2006/08/03E Ulises Olvera^ Editorial_37`36a6.1.5.2b "IEEE 802.11"c$Separate "IEEE802.11" into two wordsd278g2247 2006/08/03E Ulises Olvera^ Editorial_40`29a6.2.3b"Link Commands originate..."cGAdd "s" to Commands in the line that quotes "Link Command originate..."d290g2249i Eunah KimmAccepted 2006/08/03lvera 'cequipmentWequivalentWpmentWWentWWWWequivalentWlentWWvisonedJWequipoWequipmentWequivalentWWvisonedJWequipoWequipmentWequivalentWWYZ>FAthalyeGMember^ Editorial_61`46-47a6.3.9bGChange "is communicating" to "communicates"; "is residing" to "resides"cTensed470{k) done 2006/09/21 ESanjeevFAthalyeGMember^Technical (was Editorial)_71`1a7.3.8bAdd SINR information elementcCLink configure thresholds add SINR in addition to signal strength d511p-add to where? mismatched page/line/section # wAccepted{c) instructions unclear 2006/09/21ESanjeevFAthalyeGMember^Technical, Binding_72`10a7.3.9b3Define AP or base station identifier for 3gpp/3gpp2coLink Up MAC address not defined in 3gpp2. Use SectorID (128 bits ?) This comment applies to other events also.d516p9mismatching section/page/line. don't know where to changewAccepted{c) instructions unclear 2006/09/21529ESanjeevFAthalyeGMember^ Editorial_88`53a 7.4.6.1.1b" power it down "c Word orderd613{k) done 2006/08/29 ESanjeev390I|cThe length of the IS Query Type List is set to variable but only has a few values. Also it may be possible that the MIHF supports multiple type of queries. d782g2313iWolfgang Grtingj-Agreed, to set the length field to 1 - disagreed to use bit string to represent the query/response format, but as proposed an enumeratork- This type is used to inform what type of coding is used within a query and within a response - Within a query/response we have either TLV format or XML format or other format, but not a combination of them.wAccepted{k) done 2006/09/21 }ENada, Golmie, Member^ Editorial_123`5bA1Replace "3: 127: Reserved" with "3~127: Reserved"1@Af 33   33 33!  33& 33fcA"Syntax error in "3: 127: Reserved""@A> 33  33 33>d791g2314{k) done 2006/08/29 ~  jfacilitate,WfactWfield|Wfigure@WwWWWW W+WrWWfigure3isdefinitelyanexampleofdeploymentVfirstWWfollowedvWfor"WWWvWWWW+WzWWWformat|Wfragmentation WfromWWfullyWfunction,WgܾWWgenereallyWgeneric,Wget{WgivenjWgivingjWgloballyWgroupsܾWhandle"WWhandled WWhandover?WhandoversWhaveWhelps,WhereܾWWheterogeneous"WWWhigher,WzWhnadovers"Whope,Whorizontal,Whorizontal-handover?WhowWWhowisnetworkselectionhandledhandoversVVVVVVVVVVVVidentifierWidentifiersݻWidsWWWWieܼWܾW WWiesܾWif"WaWW WgWimplementations"Wctoinsureinteroperabilitytheieee802.21mustdefinehowt@mtoward@tries@txt@%typo@itypolengthod@wunderlying@unified@unnecessary@Hwunderlying@unified@unlikely@Hikely@Hunlikely@HHunderlying@unicast@unlabeled@Heled@H@wunderlying@unfamiliaracronym@unlabeled@H4tc3gpp۽WWWWW>WWW<WW3gppsystemalreadybroadcastinformationregardingotherraV3gpp/3gpp2W3gpp2ۡWWWW&W'WHW WYWWWW3gpp2documentnumbershouldbeusedۡV3gpp2hrpdshouldbesupported'V3gpp2shouldbementioninthissectionaswellHV AbCinuity for active user applications. Media Independent Information Service (MIIS) MIIS provides the capability for obtaining the necessary information for handovers. This includes information about lower layers such as neighbor maps and other link layer parameters as well as information about available higher layer services such as access to internet connectivity, availability of VPN services, etc. The set of different higher layer services provided by the MIIS may constantly evolve. At Dthe same time the list of access networks that are supported by MIIS may also evolve. As such there is a need for flexibility and extensibility in the way the MIIS provides support for different information elements. Towards this end the MIIS defines a schema. The schema helps a client of MIIS to discover the capabilities of MIIS and also discover the entire set of different access networks and IEs supported by a particular implementation. Schema representation also allows the mobile node=^ESrinivasF Sreemanthula^Technical, Binding_122`36a8.4.1.8bList a table of link types supported by 802.21 0 - Unknown 1 - Wireless IEEE 802.11a/b/g 2 - Wirless IEEE 802.16 3 - Cellular - UMTS 4 - Cellular - CDMA2000 5 - Fixed - Ethernet cPRadius-NAS-Port-Type is unsuitable for our use since it does not include 802.16 d787g2241v5Radius NAS-Port-Type is gonna be avialable for 802.16wRejected 2006/09/21 2006/04/26ESrinivasF Sreemanthula^Technical, Binding_122`37a8.4.2.2bremove: 4:SIPc1SIP is not used as a mobility management protocold788g2245rnet cPRadius-NAS-Port-Type is unsuitable for our use since it does not include 802.16 d787g2241v5Radius NAS-Port-Type is gonna be avialable for 802.16wRejected 2006/09/15 2006/04/26ESrinivasF Sreemanthula^Technical, Binding_122`37a8.4.2.2bremove: 4:SIPc1SIP is not used as a mobility management protocold788g2245788g2245788g2245side the scope of 802.2121R) bwithއWފW=WtWvW|WWWWWWWWWWWWWWWWWWWWWWWWW#W%W*W/W1W=W>WZWgWhWpWqWuWvWwWxWyW{W|WWWWWWWWWWWWWW#WwiththelistofeventsthatmaybecarriedinamessageyVwiththenumberofparametersthatmaybeincludedinalist~V~V~V~VN ncthelWnWqWvWWބWޅWކWފWދWތWގWޖW1W2W5W6W6W6W7W7W7W7WSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSW ycthedecriptionisthesameastherequest܄VthedefinitionofeventidsaremissingitiscriticallyimpV VefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofisquerytypelistisnotcorrectVthedescriptionofthemesageisthesameastherequest܅VthedescriptionoftypeielistofoperatorsismisleadingiVthedescriptionsofitems3and4areidenticaltheprimitivNVthediagramimpliesthatanynon-l2transportwillrundirec Vthedifferencesbetweencoreheaderspecificiesandcore80$Vthediscoveryofmihfunctionentitiesatl3isoutsidetheVthedocumentprovidesnoalgorithmsforrttestimationtherVthedocumentspecifiesthatanupperlayermayconfiguretheVtheeffectofreceiptisnotcoherentbecauseitmentionsthoVtheexampleinbracketsinconfusingegbsorrncorggsniVb4ۉWەWW)WDWEWHWRWTWUWVWWW|WܒWܚW݌WݵWݾW_WtWށWރWލW1W6WwWyWWWWWWWW@W\WWWWWWWWWW4cellularcdma2000V4extendedschemacontentݾV4higherlayerservicesV4rdfschemawVyVyVyVyVyVK cthedWjWjWjWp'b4replace by "this primitive is used by upper layers" c)typo: "this primitive is used by uppers" d601g2249{k) done 2006/09/21 2006/04/30EMathieuFPERESSEGObserver^Technical, Non-binding_111`18a8.2.1bRemove the sentence.c"The discovery of MIH Function entities at L3 is outside the scope..." This sentence is not relevant here and the subject is dealt with in section 8.1.d692g2254wAccepted{k) done 2006/09/21 2006/04/30EPeretz FFeder^Technical, Binding_14`40a5.1.8ba5.1.8ba5.1.8bSSEGObserver^ Editorial_86`64a 7.4.5.1.17a7.3.14cLink_Parameters_Change should be renamed Link_Parameters_Report (to match its MIH counterpart MIH_Link_Parameters_Report) or MIH_Link_Parameters_ Report should be renamed MIH_Link_Parameters_Change ... d549g2247{k) done 2006/08/07 2006/04/30 EMathieuFPERESSEGObserver^ Editorial_86`64a 7.4.5.1.1kESrinivasF Sreemanthula/26cfcnode's{W"Wnodes:W+WWWWnon-3gppWnon-3gpp2YWnon-adaptivenessWnon-l2 Wnon-mihWzncThis technical specification specifies the Media Independent handover services and it should not include sections that defines Media Dependence. Having the media dependence in Section 5.8 is seen as another area this specification is defining.d239g2219v{Keep it as informative. In first few lines under section 5.8 use language to clearly suggest that this is informative text.wAccepted-Modified{k) done 2006/09/21 2006/04/28MarkedpEKenichiFTaniuchi^ Editorial_5`10a2bA@[1] IEEE Std 802.11, 1999 Edition [ISO/IEC 8802-11: 1999], Information Technology- Telecommunications and information exchange between system-Local and metropolitan area networks-Specific Requirements- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. [2] ... [3]... ..........@@AR  33& 3 33Rc.Reference Number is needed for each reference.d39g2341hulaSJbwishesUWWWwith*WWWeWlWpWsWwWۋWېWۛW۝W۟WۡWۢW۽WWWWWW WW#W,W3W5W6W7W8W:W<WCWHWNWTWUWVWWWZW]W^W_WaWfWhWiWjWlWmWoWpWrWtWvWwWxWyWzW{W}W~WW܀W܃W܄W܅W܆W܇W܈W܊W܋W܌WܰW!W&W-W1W=WqWsWWݎWWWWWW W"W$W%W'W.W/W8WAWBWNWYW]WvWނWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWކWC^technicalnWtWvW|W}W~WWހWށWނWރWބWޅWކWއWލWގWޏWޖW1W2W5W6W6W6W;W;W;W;W;W;W;W;W;W;W;W;W;W;W;W;W;W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`WEKccusing"WwWۓWWܬWWWtWuWvWwWxWyWzW{W~WWWWWWWWWW<WqWusingmihftoqueryandreserveresourcesrequiredforahan"VusingradiusrelateddefinitionmaybeagoodideabutitalۓVusuallyۅWutilised}Wutilize<WVۓVۓVۓVۓVۓVۓVۓVۓVpisgW۪W۴W۽WW)W;WܰW{W݃WWYWލW2Wis-2000.4-d۽Wissues{WitgWۓW۽WW;WW݃W2WknowWlast݃WlatterܾWleaveݛWleavemappingtospecificlinktechastbdݛVlength)Wlines2WlinkۅWRW܁WݛWlWlinkidentifierݜWlistݜWlogical۪Wm2WmacmobilenodeݜWmacnewpoaݜWmade۽W:WYWܡWܥW{WWmadeconsistentchangestoacceptedcomment525YVmadesomechangesbutnotsureaboutsomecasesegmihposܥVmadetextchangesper06-0690VmakeۅW{Wmaking۪WmappingEWݛWmappingtableupdatedEVmark-up{WmarkedWWWWW1ەW WܗWܯWݒW,WVWށWރWގW1accepthandoverގV1intra-technologyhandoverhnadoversacrossesssincaseofەV1tlvspecificparametersށV1tlvspecificresponseparametersރV;cmiheventderegisterhasnotbeenexplicitlymentionedMVmiheventregisterandderegister(VmiheventregisterandmiheventderegisterwhicharementioVmiheventregisterconfirmshouldbemiheventregisterrespVVtderegisterwhicharementioVVcmihreportshouldbeinfoqueryresponsesinceinsection8.5.@mihf@miho@gmissing@>missingspacebetweenwords@&mn@mode@most@dmoved@necessary@needed@needs@pneighbor@@networknetworkidentifeirshouldbelinktype@new@newlinkidentifier@nms@noieforperformanceofaccessnetworkshasbeendefined@fnode's@Pnon-pos@accessnetworkshasbeendefined@fnode's@Pnon-pos@efined@fnode's@Pnon-mih@non-l2@themediaindependentinformatio@fnode's@Pnon-l2@ode's@Pnon-l2@nednorareanyr@fnode's@Pnon-l2@ess@ednorareanyr@fnode's@Pnon-adaptiveness@daptiveness@aptiveness@veness@bmacnewaccessrouterdWmacnewaccessroutermacaddressn/amacaddressofnewaccessVmacnewpoadWmacnewpoamacaddressn/amacaddressofnewap/bsVmacoldaccessrouterdWmacoldaccessroutermacaddressn/amacaddressofoldaccessVmacpoaWmadeܾWWWWmaintainedWWmaintaining۶Wmaintenance-Wmaitained۳Wmake#W*W?WZW;WAWBWWcWdW݈WW&W,WWWmakeannexcinformationalorreplaceifanonqueryingVmakechangestothedraftaccordingtocontribution21-06-06Vzp{k) done 2006/09/21qEKenichiFTaniuchi^ Editorial_5`58a2bAW3C Recommendation, "SPARQL Query Language for RDF", http://www.w3.org/TR/2004/WD-rdfsparql- query-20041012/. http://www.w3.org/TR/rdf-sparql-query/. W3C Recommendation, "SPARQL Query Results XML Format", http://www.w3.org/TR/rdf-sparql-XMLres/@AR 336  n 33p RcGURL of SPARQL in the reference is old, and should as suggested below. d44g2409{k) done 2006/09/21tEKenichiFTaniuchi^Technical, Binding_44a6.3.2bA----------------------------------------------------------------------------------------------------------------------------------------- | 1.1 | TYPE_IE_LIST_ | List of Neighboring | For example, RADIUS NAS-Port-Type | 4 Variable |@AR 33    33RRR16kB >bmihlW|W~WބWޅWއWވW1W5W5W7W7W7W7W7W7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWk 4bAHchange the text to "The M_SAP, defined in the IEEE 802.16 standard, provides the interface between the MIH Function and the 802.16 management plane. This SAP is used for local MIH exchanges between the MIH Function and the lower layers of the mobility management plane (as part of the 802.16 instantiation of the MIH_LINK_SAP)."HcModify the current text "This SAP defines the interface between the MIH Function and the management plane of 802.16 network." to better explain the SAPd223g2235vAdDelete the word "mobility" change the text to "The M_SAP, defined in the IEEE 802.16 standard, provides the interface between the MIH Function and the 802.16 management plane. This SAP is used for local MIH exchanges between the MIH Function and the lower layers of the mobility management plane (as part of the 802.16 instantiation of the MIH_LINK_SAP)."d@Af 33  33 33  33 33fbsetAWGWېWHWTWUWVWWWiWjWkW|W/WݗWW[WlWnWtWWWWWWWWsetthelengthfieldto1|Vsetting8WWsetupۉW/Wshall WeW۟WvWwWܕWW W WOWހWނWފWWWWWWWshallsubmitthecorrectcallflowVshildWshoudlkWshoudlexplainwhatammendmentsneedbedoneinordertoallkVkVkVkVWWWWWWWWWWWWWWWWWWWWWWWWWWWW%W&W(W*WܨWܷWWWWWWDWUWYWkWoW݀W݂WݺWWWWWWWWWWWW,W-W.W0W6W9W=W>WAWBWDWJWPWTWޗWWWshouldbeaddedtotable5anddefinedV7cforthecasewheremihfuncionisplacedinthe3gpp2networVforthepoachannelrangeiethevalueoflowandhighdoesVforceWWuncionisplacedinthe3gpp2networVV#A UbAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link SDU Transmit Status" event. The MIH User(s) Higher layers may take different actions on this notification. A higher layer intermediate buffer management entity in MIH could use the success indication to flush higher layer packets stored in any intermediate buffers and a failure indication to retransmit higher layer packets stored in any intBVermediate buffers, especially if there are changes in access network during handovers.D@Af 33  33  )c  TT  fcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d557g2298v0as per comment 555. (Resolve it the same way...)wAccepted-Modified{k) done 2006/09/21 2006/04/24VEQiaobingFXieGMemberieGMember, BindingfkbetweenݓWWWWbitsWbootsrappingWbothWWWbroadcastOW}Wbroadcast/multicastWbroughtvWWWbut|W\WWWWWWYW}WWbywWoWWWWWMWTWrWvWWWbycomment607MVbycomment652TVbycomments493494VcallWWcan"W۳WOWdWrWwWxWyWzW{W|W~WWWWWWWWWcannotWcapabilitiesWcapabilityOWvW}WcarefulWcarrydWWcaseCWdWW}WWcasesWcertainWchangesWchangingWcharactersticsWcharatersticsWchoicesWclarificationۓWWWclarifyWclarifying WclassWclassesWWWWW4brequest/response#WPWWW/WrequestedfWVWނWWWWrequestedeventlistۉWrequestertWvWrequestnetworktypeWrequestsUWWWܕWWrequire>W Wrequirelargemessagesupportfromtheunderlyingtransport Vrequired"W#WAWەWܬWWWW WWkWWWrequirementspWrequiresWrequiresclarificationVrescindedRWreserve"WWreservedۉW$WRWTWUWVWWW|W}WܒWWލW1W6W}WWWreservedforietfVreservedforothersdosVreside1W_W_WܹVreservedforothersdosܹVreside_W_W_W_WܹVreservedforothersdosܹVreside_W_WW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6Wtrbretrieved@#rewrite@s@same@sap@~scenarios@Vscope@scoping@sectionsections@ seeking@"sentence@services@set@\should@shouldbereplacedwithnetworkselectorformallydefinedon@show@shows@sip@source@spec@Rspecifications@source@spec@Rspecifications@source@spec@Rspecifications@ons@specifications@on@source@spec@Rsource@spec@Ruser@shows@sion@source@spec@Rws@sion@source@spec@RR{b7.3.1ېWRWW7.3.1linkeventdiscoverrequestېV7.3.1.1ېW7.3.1.1functionېV7.3.1.2ېW7.3.1.2semanticsofserviceprimitiveېV7.3.1.3ېW7.3.1.3whengeneratedېV7.3.1.4ېW7.3.1.4effectonreceiptېV7.3.14.2ޖW7.3.14.2whengeneratedޖV7.3.17.1W7.3.2ېW7.3.2.1ېW7.3.2.2ېW7.3.2.3ېW7.3.2.4ېW7.3.4W7.3.4linkeventregisterconfirmresponseV7.3.6W7.3.6linkeventderegisterconfirmresponseV7.3.7.3W7.3.7.3whengeneratedV7.3.8W7.3.8linkconfigurethresholdsconfirmresponseV7.4W7.4.1.1W7.4.1.2W7.4.10]W7.4.10.1.2W7.4.10.1.2semanticsofserviceprimitiveV7.4.11^W7.4.12_W7.4.13`W7.4.14gW7.4.15.1.2W7.4.15.3NW7.4.15.3.1W7.4.15.3.2{W7.4.15.3.3{W7.4.15.3.4{WW8.4.2.13hW8.4.2.22܂W8.5W8.5.1.1\W8.5.1.2\W EPeretzFFeder^Technical, Non-binding_28`55bAThere will be no direct communication between the 3GPP2 PHY and MAC layers with and the MIH layer. For the case where MIH function is placed in the 3GPP2 network, its PoS may be remote. The architecture placement of any MIH function shall be determined by the 3GPP2 SDO in this case.@A   332  8  33K  33O  33P  S  33  33  33cAOThere will be no direct communication between the PHY and MAC layers with the MIH layer. For the case where MIH function is placed in the 3GPP2 network, its PoS may be remote. The architecture placement of any MIH function shall be determined by the 3GPP2 SDO in this case. Improve the text, make it more flexible for the 3GPP2 SDO Od202g2239wAccepted{k) done 2006/09/21 2006/04/28 EPeretzFFederetzFFederQ bprior#WWprioritiesWpropWxWtWproactivelyVWprobabilityWprobablyWWprocedureW}WWproceduresRWvW>WWproceedsfWprocessVWܡWWprocessing Wprogressed(W,WWWWWWWWWWWWWWWWWWWWEhcdescriptionsNWWdescriptiveWWdesign#WYWWdesigningYWWYWYWYWYWYWYWYWPcnoieforperformanceofaccessnetworkshasbeendefinedVVnomentionaboutwhetherhigherlayerammendmentsarerequirVnoproperexampleisgivenfortlvreques/responseVnospaceforexpansionofmihtlvencodingsVnodeWWۉWۏWۦW.W3W4WܡW+WwW{WW"W#W$W1W8W?WWWWWW{W|WݏWW"W#W$WZW1W1WHWW{W|WݏWW"W#W$WZW1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W>ucmihoܠWmihomediaindependenthandoverܠVmiih Wmiis#W`WiWlW۳WWIWWtWvWwWxWyWzW{W~WWWW1W2W5W<WWmiisisnotdefininganinformationrepositoryVmiisprovidestheabilitytoaccessthisinformationaboutaVmimeWWminimizeWWminimumzWminutesWmip-WWiWWmipv4Wmis-correlationWmisleadingWfWWWWWmisleadinguseofsquarebracketswhicharecustomarilyusedVfVmismatchWmisplacedގWlacedގWގWomarilyusedVfVmismatchWmisplacedގWގWcedގWގWcustomarilyusedVfVmismatchWmisplacedގWގWގWގWގWގWގWT{instructionsWW-W6WjRWCWjinprogressRVCVgressܥVkWWW W"W(W)W*W+WDWGWLWZWەWۖWۗWۘWۙWۚWۛWۜW۝W۞W۟W۠WۡWۣWۤWۥWۦWۧWۨW۩W۪W۫WۭWۮWۯW۰W۱W۲W۳W۶W۹WۻWۿWWWWWWWWWWWWWWWWWW WWWWWWWWWW#W$W)W,W.W/W0W1W2W3W4W5W6W7W8W:W<WAWBWCWDWEWGWHWPWQWRWSWTWUWVWWWZWܛWܟWܠWܡWܣWܤWܧWܨWܫWܬWܭWܱWWWWWWWWWWWWWWWW!W"W#W$W'W(W)W*W+W,W.W/W0W1W3W4W5W7W8WO 1bC | Bit 2 : Internet Access Y/N | | | | Bit 3 : IP Version 4 Y/N | | | | Bit 4 : IP Version 6 Y/N | | | | Bit 5 : Emergency SeDrvices Y/N | | | | Bit 6 : MIH Capability Y/N | | | | Bit 7 - 31 : Reserved | V@ | | | Bit 5 : Emergency SebiliC 2002-04-15ormat. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool. s to specify .USR instead of .fp5 *Fixed bug that wouldn't allow exporting a ballot with no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create andB Submit Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Peretz%ZbmiddleWWmies|WmightWWmigration Wmih W"W$W(W*WCWDWLWOWPWQWRWSWTWUWVWWWdWfWiWlWpWsWvWwWxWۄWۉWۋWېWۭWW#W,W2W7WUWVWWWZW܅WܥWܫWWWW*W0W1W3WzW݃WݎWݛWWWWWWWWW W W"W%W'W,W/W2W4W5W8W>WBW[WW[W[W[W[WjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWiWjWjWjWjWjWjWjWjWjWiWiWiWc:barrow݃WW~Warrows݃Warticle2Wle2W2W2W2We2W2W1creferencetointernet-draftshouldberemovedݕVݖVݘVreferencetotrafficclassesisvaguealsothisinformationVreferencesWWWWW&WfWWreferencesarenotnumberedVreferencesto3gppstandardsshouldincludeanindicationofVreferencesto802.16eshouldberemovedasnosuchstandardVreferredWWWreferring۩WWrefersPWWreflectۄW;WWWWWregardingW>W$W3WWregardingtheumtssidedoesthepicturemeanthatthemihl$VregardlessWregistationWregisterRWW(WLWWWWWWWWWWWWregister/deregisterWregisteredWregisteringWregistersWWWWWWWWWsters-WeWޫWWWKWregistration.WuWVWXWWWWWkWެWWWLWregularޖWeboriginate8WܫWWWWoriginatessWoriginating$WoriginationIWIWIWIWW$WWWWWWWWWWWW.vthemihfunctionaggregatesdisparateinterfaceswithrespec*VtherecipientisnotobligatedtoactontheseeventsVthesectionisdescribingtheidsusedformihfprotocolUVtheserviceprimitivesexposedbythisunifiedinterfaceare0VthetermnetworkselectorisusedinfewplacesindraftpagVthetextaspartofthiscommentcanbeharmonizedwithprev=Vthewaymihinterfaceswiththenetworkmanagementfunction#Vtheir`W\Wthem\WthenQWRWSWTWݓWWthereWWWWWVWWWWtherearenopagingrelatedconceptsinthecurrentdraftVthereisonlyonenotionofmihcapabilityitmaybeavilablVtheseܾWܾWܗWܢWWWWW W W1W2W:W;WDWFW{W}W݀WݏWݓWݜWWWW/W1W4W5W6W7WSWtodayܗWtoo{Wtoward3WtransactionsݓWtransportWd_‚Hݒ߃ὃᾃῃƒÃ‚Iă‚Jԃƃ‚Q8K>ఃഃྃ7ៃǃ#‚RƃȃɃʃ˃̃̓΃""""""""""""""""""ܵՃփLM}@A޽޾޿,-.]^_ߛߜߝ‚TKȃɃʃ˃ܶ׃؃كNOPQݓɃiߧ‚UZ[ےۓ̃̓΃ <=>?@Aܷڃۃ܃RSݔt‚VۑσЃ!"B݃ރTUݕ‚W߃V|ݖ‚XX\у҃#$CDEܸܹܻܺW݉‚YYFX~ݗ‚Z]^%&Gܗܼ‚a'H‚bӃ(Yݘ‚cu‚dԃZ‚e_`)Iܾܽ‚fa*‚gbՃփJKLܿ[ݙ‚i׃M\blink-layerWuWlink-state8Wlink-switch)Wlink-type~WlinkidentifiergWhWlinkparamaeterۉWlinkparameterۉWlinkparameterlist_Wlinkparamterlist_WlinksPWTWkWWWWWWlinktechGWlWlinktypeGWۉWaWlWWWWlinktypemediatypeofthelinkaVlinktypetypeofthelinkVVVnkaVaVaVaVthelinkaVaVaVaVaVaVaVaVlinkaVaVVlinktypemediatypeofthelinkaVaVaVaVaVaWbWcWcWWWWWWWWWWWWWWWWWWWWWWWWWWWWKWLWSWTWUWVWWWXWbWcWdWhWkWmWyWzW{W~W܎WܷWWWݙWWW@W[W^WtWWދWތWޕWޫWެW޿WWWWWW6^editorialijlmnpqrstv46a8.3.4bbARemove entire section 7.4.13.@A  33cA"MIH Handover Complete" is improper for 802.21 scope. The functionality represented by this primitive is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d648g2264 2006/05/14 2006/04/245EQiaobingFXieGMember^Technical, Binding_117`46a8.3.4b33cA"MIH Handover Complete" is improper for 802.21 scope. The functionality represented by this primitive is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d648g2264 2006/05/14 2006/04/245EQiaobingFXieGMember^Technical, Binding_117`46a8.3.4bed" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new VcIn Figure 12 show MIH_LINK_SAP and it's relationship with other media specific SAPs to mkae the figure more clear. For 3GPP/3GPP2 technologies consider deleting MIH_3GLINK-SAPd214g3209vby 215w Superceded 2006/09/21MarkedEStewartFSkomraGMember^Technical, Binding_27a5.5.4bsRewrite the section and focus more on how 3GPP networks can handover to other non 3GPP networks with help of MIHF. cAThe current MIH Reference Model for 3GPP tries to show how MIHF fits within 3GPP networks. However 3GPP networks do their own system design. 802.21 has no business in designing 3GPP networks. Instead this section should focus more on how 3GPP networks can work with other non-3GPP networks with help of MIH capability. Mobility management and handovers within 3GPP networks are outside the scope of 802.21. Trying to change basic structure of 3GPP networks is also outside the scope of 802.21d194g3211vSuperceded by 195w Superceded 2006/08/299KZtaniuchiއވފދތލގޏސޑޒޓឃៃ᠃ᡃᢃᣃޓޓޓޓޓޓޓޓޓޓޓ,lcsubjective-Wsubmit>WsubmittedWsubnetrW-WsubnetinformationaloneisinsufficienttosupportscenariorVsuboptimalWsubscribed7WsubsectionsWWsubsetWsubstantiallyWsubsystems/WsubtleWsucceedsWsuccessۄWsuccessful܄W*WsuccessfullyWsuccinctnessWWWWctnessWWsuccessfullyWsuccinctnessWW8 ހbE | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | TYPE_MIME_TLV | MIME Type | Variable | An octet string for a MIME type, e.g., "application/xml" | ---------------------------------------------------------------------------------------F---------------------------------------------------------------------------------- | TYPE_EXTENDED_S | URL of extended | Variable | URL of an Extended Schema encoded in octet string | | CHEMA_URL | | | | ------------------------------------------------------------------36ictypolengthoduVtyporaeinthesentenceshouldbeareފVtyporregisterVtypothisprimitiveisusedbyuppersVtypographical۠W.Wtypographicalerror۠V.Vucd8Wudp Wudp/ipwWue܋Wumts۽W:WWW$Wun-usedWunableWunacknowledgedWunavailableWWunchanged0Wunclear۫W-WWWWWWWWWWW:WWWuncleardefinition۫Vunclearfunction/operationinboxmiisreportavailabilityVunclearterm-VunclearwhetherdurationisperiodoverwhichtheconstinfoVuncontrolledWundefinedWWunderWWW}W|WWWWWWWWWWW}W}WWW}W}WWW}W}W}W}W}W}W}W}W}WerstandingjWkWmWnWoWzW{W|W}W~WہWJWWWWunfamiliarRW)bisޖW5WWW[WlWnWoWsWtWwWxWyWzW|WWWWWWWWWWWWWWWWWWWWWWWW WWW(W*W+W,W<W>WpWtWuW{W|WWWWWWWWWWWWWWWWWWWW#Wisencapsulatedandincaseofmobileipv6ޏVisquerytypesVisinitiatedWiso/iecpWissueۓWۓWۓWۓWۓWۓWۓW0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V% ^bindingܬWܾWWWWWWWWWWWWWWWWWWWWW Query language) query response [2] where the SPARQL query is supposed to contain an appropriate query for obtaining expected RDF/XML data. --RDF_SCHEMA_URL: When this InfoQueryType is specified, InfoQueryParameters Response is a null string an URL of extended schema . This InfoQueryType is used for obtaining the URL of the extended schema. --RDF_SCHEMA: WhenB this InfoQueryType is specified, InfoQueryParameters Response carries either the URL of the extended schema the query originator wants to obtain or a null string when the URL of the extended schema is unknown an extended schema. @be is mentioned. g2423 2006/05/02}EKenichiFTaniuchi^Technical, Binding_107`64a 7.4.15.2.2bg4177 2006/05/01 .vtransportWW W WWWW"WjWtreeZWtriesZWlWtriestoorganizeiesintotreestructureZVtrigger"Wtwo۔W۴W\WW"WWtypeJW]WaWWWWWWWWWW W4W>WWWtypeielistofnetworktypeisnotapprovedVtypesWWtypically?Wuk/currency/byHWulises\WWWunclear:WuncleraWunderRW۳WݓWnWWWunderlyingWunderstand|Wunified0WuniqueWWuniquenessWunited'Wunitedstatesmaynotbeanappropriaterepresentation'VuntilWupWWupdate\WWW}WWWWupdtae\WWupdtaetheparametersbasedonchangestothedraftVupdtaestWupon"WWWWupper*WQWSWەW"WWWurlށWރWusWWuseJWۓWbheb7.4.4.1.25W7.4.4.1.2whengenerated5V7.4.7.2.2ۄW7.4.8gW8JWGWRWܑWܔW2W6WWWW8.2.1rW8.2.1l2dataframespacketformatrV8.3tW8.3protocoldescriptiontV8.3.1qW8.3.2.3UW8.3.3.2W8.4.2.13hW6W8.4.2.22܂W8.5W8.5.1.1\W8.5.1.2\W8.5.2.5W8.5.2.5mihlinkupindicationV8.5.3.11bW8.5.3.12bW8.5.3.13cW8.5.3.14cW8.5.3.15dW8.5.3.16dW8.5.3.17eW8.5.3.18eW8.5.3.19iW8.5.3.20iW8.5.3.5܂W8.6.1.1W80W0>W>W.3.20>W>W.20>W>W.3.20>W>W0>W>W0>W>W0>W>W0>W>W3.189W8.5.3.19>W8.5.3.20>W>W.3.20>W>W0>W>W20>W>W20>W>WޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVޕVbconfiguredۉWYWޖW5WWconfigurerequestset܄Wconfigurerequestsetlinkconfigureparameterstype14܄Vconfigurestatus܄Wconfigurestatusstatus245܄VconfirmېWzW>WBWCW=WWWW7W{WWWWWW#Wconfirmation{W#WconfusingWconfusionWcongestion-safeWconiferlWconistent۽Wconnect WuW~WconnectedWconnection,WWconnectionsOWPWTWconnectivAWconnectivityAWSWWRWSWܡWconnectsWconsiderOWPWۼW۽WWWWW-WconsideraddinguniqueeventidentiferforlinkdetectedVconsiderredrawingpicturewithmoreconistentuseof3gppt۽VconsiderremovinggenericۼVconsiderremovingorbetterexplainingintentoffiguretheVconsiderspecifyingtheqosinformationinlinklayerindepeVVVVV%5 bchangechange5.6.3.1mihnmssap8VchangeasfollowsܤVchangebecommunicatingtocommunicate7VchangecontainingasetofconfigurationparameterswithconjVjVjV5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W#binfoquerytypeܕW}WwWxWyWzWinfoquerytypeanintegervaluecorrespondingn/athetypeofwVyVinformݍWinformaAWinformaiton?WWWWW .ނbcTable 23 needs to be revised.d813g2429wAccepted{k) done 2006/09/2123 ރEKenichiFTaniuchi^Technical, Binding_128`20a8.4.2.24bA1: One or more TLV specific response parameters 2: One SPARQL Query response parameters 3: URL response One Extended Schema URL parameter 4: zero or one Extended Schema URL response One Extended Schema parameters@AB 33  33% / 333 6 33M X 33\  h 33i l 33   33 Bc9Column in Table (Section 8.4.2.24) needs to be modified.d814g2430v4g2430vtiption | Length | Value | --------------------------muށ_127`36a8.4.2.23bA1: One or more TLV specific parameters 2: One SPARQL Query parameters 3: Nothing is carried 4: Zero or one Extended Schema URL parameters@Az 33  33* - 33  zc?Value column in Table (Section 8.4.2.23) needs to be modified.d811g2428i Vivek Guptaj`"One or more" makes it redundant and is not required. Just leave it as "TLV specific parameters"mAccepted-ModifiedvA~1: TLV specific parameters 2: One SPARQL Query parameters 3: Nothing is carried 4: Zero or one Extended Schema URL parameters ~@AR 33 ! 33|  RwAccepted-Modified{k) done 2006/09/21ނEKenichiFTaniuchi^Technical, Binding_128a8.4.2.24b8.4.2.24bsed. d806g2427wAccepted{k) done 2006/08/2122 ށEKenichiFTaniuchi^Technical, BindingqkgenericݓWWWgiveAWgoingdWgood۳W۶Wgoodpoint۶VgroupgWWWhadgWWhandWhandover"WWhandovers-WWhangingWhasdW\WWWvWWWhaveAW|W\WpWuW|WWWWW Whavewedecidedthatmihfunctiondiscoveryisoutsidescope|Vhaven'tWhavingWheaderWYWhelpsWhenceWWhereWheterogeneousWhigh-levelWhigherWWhighlyWhindersWhocgWWhowOWrWWWhowwecanmandatemediaspecifictechnologyeventhoughiuOVhowever"WWWhttpWhvaeWiWiWWWuWWWWWW0WaWWܺWWWifthisinformationistoberetrivedusereportsliketypeaVifwedon'tneedtohavesectionsaboutexistingsapsandprVimplementationuWWimplementsbuserAWLWOWPWQWRWSWTWUWVWWWcWfWiWېW܊WIWzWWWޖW5WW7WWWWWWW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wvalid\WۂWېWTWUWVWWWXWYW\WcWkWmWܖWW|WWvalidrangeۂWvalueJWXW_WfWjWmWzW{W}WۉWWWW*W=WFWHWwW|W܂WWXW[W~W݁WݔWݗWݘWݙWWWހWނWޅWWW7WwcunderlyingWWW WWWunderstandDWCWYWWWunderstandingWWwWxWyWzW{W~WWWWWWWWunfamiliarRWunfamiliaracronymRVunicastW $vencapsulatedWޏWendWenhancementsەWenough"WentireWentities۴W0W3W/Wentity۪W۴W"W/WWWentity/remoteWequivalentWerrorWWesݓWesssەWestablishingSWetWWWWWW WexamplesZWܗWexchanges4W5WexistingWWexplainۅWexplainedܗW6WexplainingWexplicitlyFWexposed0Wfail{Wfeels7Wfig۴WܗWfigure0W۴WqWDW݃W6WZWfilterܗWfirstݓWfixedܗWflexibilityZWflow0WۋW۵WfolksSWfollows۳WWforBWZWۆWۈWۋWۓWW W@WRWqWܗWWWWWW;WaW{WݓWݳW4W5Wforeachaccessnetworkthereisanoperatorandsametypeo@Vforwhatscenariosl3doyoureallyneedthisۈVforce:WformZWformatܗWframework۵W3W ނbI-------------------------------------- | TYPE_EXTENDED_S | Schema Data | Variable | When MIME_Type_TLV is not contained ...... This field | | CHEMA_ | | | contains Extended Schema stored in the requested URL. | ------------------------------------------------Jz------------------------------------------------------------------------------------------------------------------------- @ type "application/rdf+xml" is used. | | | | | MIME type "application/xml" MUST be supported for thistype of query.| -----------------------------------------------------------------------------------------------------------------------------------xva*WTWlW۔W۪W۳WWWWܰWW3WݓWݜWW\WjWWWWWWWW W WWWW!W"W?WVWWWWWWWWWWW#Waaa}WabilityWableWWWabortގWaboutۃWݓWW WW4W?WoWWabove۔WەWWWaccept"WގWWWvWWacceptcontribution21-06-0775-00-0000-itextandfigureVacceptmodifiedtextbelowandalsochangepoatoposbelow"VacceptableWW4WZWۋWێWWW WRW`WܗWܬWW3WFW݃WWSWdWaddacommentinlinkuptothateffectVaddanewlineafterline583VaddanotherflowdiagramforthistheorderingofchoicesmaۋVadddescriptionofparametersinthisprimitivechangegetstVtothewordoptionalintablefornewpoadV&brdf/xml}WxWzWreܬWre-classifyZWsWre-defineGWJWlWre-definethelinkparametertypeasapairoflinktechtechsGVlVre-definethelinkqualityparametertypeencodingtableasJVre-organizetWvWre-verificationWWre-visitWreadWWreader<WreadersWreadilyWready#Wreal{W#WWdy#W#WWready#W#WWreader݂WreadersWreadilyWready#W#WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW8bliteral~Wlittle6WlocWWWWܗWܙWܙWܙWܙWWܙWܙWeral~WlittlevWlocܗWܘWܙWܙWbthisparameterspecifiesthelistofcommandsthatmaybecaދVތVthisprimitiveisdeliveredfrommihfunctiononoldserving"VthisprimitiveisgeneratedbyanupperlayerentityoftypeېVaCbtoWWWWWWWWWWWWWWWWWWWWWed the MN relies on periodic access to its operator MIIS to obtain pertinent information such as new roaming lists, priorities and any other related information that would enable to utilize services in various access networks." More generally, there is too much suggestion what the architecture for using 802.21 reference model could be like. There is no point in hinting a Breference network architecture in the 802.21 Draft. A reference is basically a recommendatin and it its not appropriate to recoommend any architecture or deployment model.This basically does not help leverage 802.21 work to places like 3GPP. .ijkmnpvw{l) none needed 2006/05/146/04/30 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 14rialxvreplacerequestwithindicationކVreplaceupperlayerbymihfuserVreplacewithvalidmihfidentifierVreplacingއWreportedQWreports?WrepresentWWrepresentasintegerVrepresentationWWW'WrequestlW۔WކWwWxWyWzW{W}W~WWWWWWWW1W8W\W~Wrequest/confirmWrequest/responseWrequestparametersWrequired۔WەWWWW1WWWrequirementWrescindedRWreservation"WreserveVWreservedWresolutionfWnfWfW Y 33Z >c5In Section 8.5.4.2 the description is not correct . d861g2432 2006/07/20ކEKenichiFTaniuchi^Technical, Non-binding_140a Annex A-1bmEither replace with euqivalent primitives that are defined in the specification or remove these primitives. | --------------------------_ ނbE | | | |"application/xml application/sparql-results+xml" this field contains XML text for | | | |SPARQL Query Results | ----------------------------------------------------------------------------------------------------------------------------F------------------------------------------ Table xx -- Extended Schema parameters Format -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | Type | Desctiption | Length | Value | -------------------------- 8އbAThis primitive is used by a station's MIH Function (or an application on behalf of MIHF) to request information either.... Also replace MIH with MIHF in subsequent sentences. @A> 33  % 33>cwThis primitive is used a Staion's MIH is not always correct. Because in IS model, a proxy can also use this primitive. d659g2434v>Editor to examine replacing MIH with MIHF wherever applicable wAccepted{k) done 2006/09/21 ވEKenichiFTaniuchi^ Editorial_107`49a 7.4.15.2.2bAMIH_REPORT InfoQueryResponse @A*   *cfMIH_REPORT should be InfoQueryResponse since in Section 8.5.4.2, only InfoQueryResponse is mentioned. d668g2435{k) done 2006/09/212006/08/29ފEKenichiFTaniuchi^ Editorial_118`28a8.4bAiTLV type values shall be unique. TLV Type values rae are assigned in accordance with the following rules:i@kv ހbC, MIME type "application/xml application/sparql-query" is | | | | used. MIME type "application/xml" shall be | | | | supported for this type of query. | |-------D------------------------------------------------------------------------------------------------------------------------------------------------------------ Table xx -- Extended Schema URL parameter Format ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | Type | Desctiption | Length | Value  ނbA3 33!  * > 33   ) 33+ 5  @ ^ UU    UU    UU? 33G UU   - UU   UUF B f UU 33    = 33   33     33 C  L 33     33 # 33   33   33     33 sectoޖW1W2W5W5W7W7W7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsd721g4136iWolfgang Grtingjagreed to describe the reason for not being globally unique. Text may be: The MIHF ID is aimed to be "unique" within the communication area between the 2 peers. It is not a MUST that the ID should be "globally" unique.vby comment 719 This is quite correct: " The MIHF ID is aimed to be "unique" within the communication area between the 2 peers. It is not a MUST that the ID should be "globally" unique."w Superceded 2006/09/216E ShinkichiFIkedaGMember^Technical, Binding_113`55a8.3.2.2b#Define the term "session" properly.c!"Session ID" does not make sense.d724g4137i Qiaobing XiemAcceptedv'by comment 719 which defines session IDw Superceded 2006/09/216EStewartFSkomraGMember^Technical, Binding_30a5.6bMAdd MIH_LINK_SAP in the figure . Delete other SAPs which may not be required. required. required.echnical, Binding_113`43a8.3.2.1.1d7216` ފbc(Typo rae in the sentence should be are.d772g2437{k) done 2006/09/21 ދEKenichiFTaniuchi^ Editorial_119`3a8.4.1.1bAThis parameter specifies the list of commands that may be carried in a message. Each event is represented by an event code and occupies one byte.@A> 337 9 33>c$may should be maybe in the sentence.d775g2439{k) done 2006/09/21MarkedMarkedތEKenichiFTaniuchi^ Editorial_119`17a8.4.1.2bAThis parameter specifies the list of commands that may be carried in a message. Each command is represented by a commandcode command code and occupies one byte.@Az 337 9 33q  |  33zcLmay should be maybe in the sentence, and commandcode should be command code.d778g2440{k) done 2006/08/29 ލEKenichiFTaniuchi "L?vissuesZW-WWWitSWUWێWWWWZWW-WSWitSWUWێWWܗWWWWWW a position to specify persistent URL locations....mRejected 2006/07/20Response is mentioned. d668g2435 2006/05/14މEKenichiFTaniuchiGMember^Technical, Binding_150`16aAnnex CbA6One persistent URL of this schema shild be assigned. 6@A* 334 *EKenichiFTaniuchi^ Editorial_107`49a 7.4.15.2.2bAMIH_REPORT InfoQueryResponse @A*   *cfMIH_REPORT should be InfoQueryResponse since in Section 8.5.4.2, only InfoQueryResponse is mentioned. d668g2435 2006/05/14މEKenichiFTaniuchiGMember^Technical, Binding_150`16aAnnex CbA6One persistent URL of this schema shild be assigned. 6@A* 334 *ޏcgNot sure what is meant by Agent Advertisement is encapsulated, Router Advertisement is encapsulated. d858g2443vAIn case of Mobile IPv4, Agent Foreign Agent Advertisement is encapsulated and in case of Mobile IPv6, Router Advertisement is encapsulated.@AR 33   - 33RwAccepted-Modified{k) done 2006/09/21ސEKenichiFTaniuchi^ Editorial_141`4a Annex A-1bas in the comment.cAE.g., e.g., @A>    33>d876g2444{k) done 2006/09/212006/08/29ޑEKenichiFTaniuchi^ Editorial_141`6a Annex A-1bas in the comment.cAnotifies notify @A>    33>d878g2445{k) done 2006/08/29 ޒEKenichiFTaniuchi^ Editorial_141`20a Annex A-1badd a period to the sentence. cmissing a period. i> 6ރvA1: TLV specific response parameters 2: One SPARQL Query response parameters 3: URL response One Extended Schema URL parameter 4: zero or one Extended Schema URL response One Extended Schema parameters@A 33 # 33' * 33A L 33P  \ 33] ` 33   33 wAccepted-Modified{k) done 2006/09/21 ބEKenichiFTaniuchi^Technical, Binding_138`9a8.5.4.1bAThis message is used by MIH Function to retrieve the Information Elements provided by the information service. The InfroQueryType must contain exactly one query type. @A* 333 *c5In Section 8.5.4.1, the description is not correct . d860g2431wAccepted{k) done 2006/08/29 ޅEKenichi ނbG------------------------------------------------------------------------------------------------------------------------------------------------ | TYPE_MIME_TLV | MIME Type | Variable | A MIME Type TLV to specify an XML a | | | | | format of the Schema_Data. When this H | | | | | TLV is not contained, MIME type "application/rdf+xml" is used. | | | | | MIME type "application/xml" MUST be supported for thistype of query.| -----------------------------------------------------------------------------------------------------------------------------------ޒd880g2446{k) done 2006/09/21 ޓEKenichiFTaniuchiGMember^ Editorial_145`15a Annex A-2bas in the comment.cASuppervison Supervision@A*   *d888g2447{k) done 2006/09/2124ޖEVidalFAlbertGMember^Technical (was Editorial)_78`48a7.3.14.2bA7.3.14.2 When generated This notification is generated either at a predefined regular interval determined by a user configurable timer or when a specified parameter of the currently active interface crosses a configured threshold.@A* 33 *c*c*c5g2439 2006/08/13 ތEKenichiFTaniuchi^ Editorial_119`17a8.4.1.2b8.4.1.2b8.4.1.2b14ތEKenichiFTaniuchi^ Editorial_119`17a8.4.1.2baAnnex CbA6One persistent URL of this schema shild be assigned. 6@A* 334 *2jkother|WݓWrWuWWWW~WWothersvWotherwiseuWWWoutWWWout-of-bandWoutside|WW~WWover}WoverlapYWown Wpage#WWWpar-WparagraphAWparameterWparameters"WWWpartWW:WpastvWpatternWperiodicdWpersonallyWpertaining"WWplWsWWplseecomment162VVplaceWplaced۳Wplaces#Wplease:Wpleasebemorespecificwhichpartofsection6.3.8isuncle:VpoadWuWWWpoint۶WWpointedvWpoints۳W۴WpolicyWpossibility۳WpowerfulWpre-configurationgWWpresentWVWpresentedWpreventWpriitives)WprimitiveWWWWWWWWWkWmWnWoWzW{W|W}W~WہWWWW|WܻWWoW^bapplication/xmlހWނWapplicationsAWWapplyWappreciablyAWappropriateAWTWۉW#WW}WxWzWW(W,WappropriatelyWaWWappropriatlyNWapprovedWWaps?WWJW?WJWJWJWaps?WJWJWJWJWJWJWJWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWOWUWbWpWxWۂWېWەWWWW7WCWTWUWVWWWXWYW\WcWsWtWxWܪWܴWܺWܾWWWW W(W*W0W1WJWjW|W݃WݖWݗWݸWWWWWWWWW2WކWފWޔWޞWޡW޿WWWWWWWW WW.W>WAW_WjWlWmWsW|WWߝWߨWߪW߫W߱Wrb2rejectedܖV2renumberpagesoftoclofandlotV2shouldbereplacedbyinformationaboutaccessnetworksV2wirlessieee802.16Vwirlessieee802.16^V02.16^V^V^VVMbscope W#WsWvWwWەW۶WW|WWWWfWfWWfWfWWsWuWvWwWەW۶WܪWWfWfWWfWfWWWWWWWWWWWWWWWWRW܌WWseamlessۻWsecondJWۤW4WHW܉WܞWWWWsectionWW!W'W1W2W3W4W6W7W8W9W<WBWCWEWYW]WaWbWpWۄWWWWW;WAWBWRWSWYWcWhW܁W܂WܕWܗWܘWܙWܛWܩWܪWܶWܷWWWWW{W݂W݄W݌WݳWWWWWWWW W W W6WNWXWYW\WlWnWvWޘWޚWޟWޥWޯWްWޱW޲W޴W޵W޶W޷W޺WWWWWWWWWWWWWWWWWWWWW^bc0WގWW0ismisplacedinthevaluecolummގV0-6W06*WW0x2W0x2a16bitouia14bitsid34bitsalsothecommentsforV1WSWiWsW۪W۽WWWWW>W>WXW|WWWWlWtWWW1tableofcontentssectiontitlemissingV1textneedstoimprovesV1thecurrenttextimpliesthatthediscoveryofmihfunctio|V1thedescriptionandcategorizationofhorizontalandvertiV1theinformationelementtypeielistofnetworksrepresentV1thisisalinklayerindicationwhichshouldonlybereceiSV1whatisastation'smihisitamobilestationorbasestaiV1-210W1.0WW ݎbc+Policy engine is not the only upper layers.d152g2413wAccepted{k) done 2006/09/21 2006/04/28ݐE YoshihiroFOhbaGMember^ Editorial_22`38a5.4.3cAIiwxᙃ᳃σ!D #bAChange the text to: In certain scenarios L2 information may not be available or sufficient to make intelligent handover decision. In such cases, higher layer information service is required. The capability of such network information service may be obtained via schema access. The structure and definition of a schema may be represented in a high level language such as XML. However the transport and security of this information are outside the scope of IEEE 802.21.@A>  33    TT>cAmThis section is about design the goal of MIIS, not need to talk about solution issues (i.e., schema and XML).m@A  33d158g2243i Subir DaskThis is not true since several places in this section we talk about solution such as lines 52, 53 (page 21), lines 12, 13, 27 and 28 (page 22)mRejected{l) none needed 2006/09/21 2006/04/24$EQiaobingFXieGMembereGMemberT^technical:W;WAWBWCWHWNWRWSWTWUWVWWWYWZW[W]W`WhWkWmW|W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W܂W-‚I. ‚7/%‚80‚E1& 2‚i3'‚C4‚Y5‚x6(‚79‚H7‚v8):*‚h;‚r<2‚2=‚3>‚W?‚Z@3‚DA‚RB4‚vC8F‚4DÄJRE9ĆEGUG:‚sHA‚DIxD‚:JH‚vKQ‚%L‚vMS‚5N‚XO‚fP‚gQT‚YRÄIZSU ‚1Tw;^technicalwaseditorial@VAVCVKVpVsVvVۛVۼV۽VVVNV[V]VܭVVVVVVVVVVVVVVVVVVVVVA -{doneWWWWWWWWWWWWWWWWWWWW WWWWWWWWWW#W$W)W,W.W/W0W1W2W3W4W5W6W7W8W:W;W<WAWBWCWDWEWGWHWPWQWSWTWUWVWWWYWZW]W^W_W`WaWfWiWjWkWmWoWpWrWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎WܑWܒWܓWܔWܕWܖWܚWܛWܟWܠWܡWܣWܤWܥWܧWܨWܫWܬWܭWܱWWWWWWWWWWWWc7The use of NAS-Port-Type should not be just an example.d350g2392wAccepted 2006/06/20 2006/04/28Table 6 ݕE YoshihiroFOhbaGMemberbaGMemberbaGMember |w>IEAjayFRajkumarGMember^ Editorial_69`29a7.3.3.1JRedefine them whereever there is a discrepency as .request/.confirm pairs.cLAll .request/.response pairs in Section 7 should be semantically corrected. d482g2244pC- done Commet 482 related changes in 21-06-0676 - need new drawingsv4Refer to Contrib: 21-06-0676, 21-06-0641, 21-06-0642wAccepted{i) to do 2006/08/23 2006/04/28MarkedIEAjayFRajkumarGMember^ Editorial_69`29a7.3.3.1r^Technical, Binding_63a7bJRedefine them whereever there is a discrepency as .request/.confirm pairs.cLAll .request/.response pairs in Section 7 should be semantically corrected. d482g2244pC- done Commet 482 related changes in 21-06-0676 - need new drawingsv4Refer to Contrib: 21-06-0676, 21-06-0641, 21-06-0642wAccepted{i) to do 2006/08/23 2006/04/28MarkedIEAjayFRajkumarGMember^ Editorial_69`29a7.3.3.1 ............................. ---------------------------------hZ{inputWaWinstructionsیWۢWWWWW WWWWWWWܾWܾWܾWܾWܾW{W݃WjܥWjinprogressܥVkWWW W"W(W)W*W+WZWەWۖWۗWۘWۙWۚWۛWۜW۝W۞W۟W۠WۡWۣWۤWۥWۦWۧWۨW۩W۪W۫WۭWۮWۯW۰W۱W۲W۳W۶W۹WۻWۿWWWWWWWWWWWWWWWW WWWWWWWWWW#W$W,W.W/W0W1W2W3W4W5W6W7W8W:W<WAWBWCWDWEWGWHWܛWܟWܠWܡWܣWܤWܧWܨWܫWܬWܭWܱWWWWWWWWWWWWWWWW!W"W#W$W'W(W)W*W+W,W.W/W0W1W3W4W5W7W8Wibthebroadcastmechanismwithlayer2transportwouldbediffVthecreationthereinofanewentitytoanewentitycreatedۚVthedescriptionshouldbephasedinmoremediaindependenttVtheencodingformatisdefinedasshowninthetablebelowV 5bA[Modify the section 7.4.4.1.2, page 85, line 30] : 7.4.4.1.2 When generated This notification is generated either at a predefined regular interval determinded by a user configurable timer or when a specified parameter of the currently active interface crosses a configured threshold. For example, when the MIH Function has received Link_Parameters_change.indicaiton from link layers@A>  336 33  @ >cA7MIH_Link_Parameters_Report.Indication can be generated when a specified of the currently active interface crosses a configuration threshold that is to say when the MIH Function has received Link_Parameters_Change.indication from link layer. To make clear, I propose section 7.4.4.1.2 be modified as suggested : 7d593g2218wAccepted{k) done 2006/09/21 2006/04/306EJinFLeeGMember^Technical, Non-binding_100`8a 7.4.12.1.1b4.12.1.1b 33  @ >cli Ibc"Link ParameterType" definitions is insufficient and needs to be expanded. For instance, what if an upper MM algorithm wants to set a threshold on the BLER (block error rate) or RxLevNCell parameter of a GSM/GPRS link?d592g2285v7Refer to comment 552 for table of link layer parameterswAccepted-Modified{k) done 2006/09/21 2006/04/24JEQiaobingFXieGMember^Technical, Binding_124`9a8.4.2.8bARe-define the "Link Quality Parameter Type" encoding table as the follows: +--------+----------+---------------------------------| | Type | Length | Value | +--------+----------+---------------------------------| | 8 | 2 | First Octet: Type of Link: | | | | 0: Generic | | | | 1: IEEE802.11 | | | | 2: IEEE802.16 | | | | ssion}, | | | | EAjayFRajkumarGMember^Technical, Binding_146`12aAnnex-3b(Change the Category to "Command Service"c_Entry 2,3: MIH Event Register and MIH Event DeRegister incorrectly categorized as Event Serviced889g2228i Vivek GuptakBy comments 493, 494m SupercededvBy comments 493, 494w Superceded 2006/09/21 2006/04/2825EReijoFSalminenGMember^Technical, Binding_13a5.1.3bNIntroduce the modifications proposed in submission 0598 into the 802.21 draft.cBThe support for QoS is immature in the P802.21 standard draft 1.0.d90g2219i Vivek GuptakYMay need to consider this text in light of other comments mentioned in the draft as well.m Question ?vandard draft 1.0.d90g2219i Vivek GuptakYMay need to consider this text in light of other comments mentioned in the draft as well.m Question ?vtion ?vestion ?v06/04/28EAjayFRajkumarGMember^Technical, Binding_139a8.6.1.2.2.2d868 2006/04/2829nborderxWW"WWWkWorderingWorgݔWWWorg/2001/xmlschema~Worg/2005/sparql-resu~Worg/tr/2004/wd-rdfspqWorg/tr/rdf-sparql-quqWorg/tr/rdf-sparql-xmqWoriginallyfW~cfinalized>Wfirst`WpW5WIWwWWtWWlWWfitW WfitsYWWfixeduWܑWܔWWW'WWWflatZWsWflexibilitytWvWflexible WflowۚWW-WKWMWzW>WBW=WWW7WiWWWWWflowsWWflyWWfmipWfmipgmiiicmparenotusedVfocusYWWWWfollowlWfollowed>WfollowingܬWݐWWWWW W/W2W>WIW$W?WWWfollows۪WforW"W$WGWIWJW^WeWhWpWvWۅWۋWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWېWۋWۈWۋWۋWWۈWWۈW#csections+WWW)W*WnWWWsectoridWsecureWWsecurityW<WܾWWWWW?Wsecurity/qosܰWWsecurity/qosܰWܰWWܢWܼWܾWWݏWWsecurity/qosܰWܰW<WܢWܼWܾWWݏWWsecurity/qosܰWܰW<WܢWܼWܾWWݏWWsecurity/qosܰWܰWܢWܼWܾWWݏWWsecurity/qosܰWܰWܰWrity/qosܰWܰWcurity/qosܰWܰWܰWܰWܰWܰWܰWܰWܰWܰWܰWܰWܰWܰWܰWܰWFJjk0x2W1W1isgeneralaccessnetworknformationandsoV12#WW13#W14W15W16W162WW2W2.6W21#W21-05-0347-00-0000-xwWxWyWzW{W~WWWWWW22#W27#W28#W29W32W345sW350WW362W394oW3gpp/3gpp2W444vW45W4889W493W494W52#W53#W577W6W6.3.4.2.5W6.3.8W:W607MW626OW627W636QW652TW695WW802.11eW802.16W802.1dW802.21uW۾WWWa/W0W<WAW]WbWjWkWmWnWoWzW{W|W}W~WہWےWWWW|WܶWܺWWݓWݴWݻW-WOWjWabdܹWable/Wabout#WAWWWWaboveWaccessWWaccessibleWachieveWWacross/WWbThe broadcast mechanism with layer 2 transport would be different than the layer 3 transport and should be specified in separate sections.cA/This section of "On demand MIH Capability Discovery" needs to be elaborated and clarified substantially. The advantages of General broadcast meachism from the mobile terminals should be evaluated against the cost such broadcast would entail on the over-the-air resources as well as in the wired network./d866g2245i Ronny KimkNo specific text proposal.mRejectedvSby comment 250 as per contribution 21-06-0611-00-0000-MIH protocol section updatew Superceded 2006/09/21 2006/04/28EAjayFRajkumarGMember^Technical, Binding_139a8.6.1.2b#Shall submit the correct call flow.cAn MIH Capability Discover Request from the terminal would not be interpretted at a non-MIH PoA. Hence the first PoA could not broadcast the MIH-Capability_Discover.Request further. d868g2257i Ronny KimRonny KimOkimz{78koh}9lee1256ᧃᨃᩃ67777777777777777777777777777777777777777777777777777777777777775IZmAcceptedpContribution 21-06-0712-00-0000-IE_TLV_container -- done Contribution 21-06-0711-00-0000-IE_TLV_retrieval_no_exclusion -- done vAno suggested text. Comment assigned for further work. Contrib: 21-06-0674 Tries to organize IEs into tree structure. Why should information be organized in tree structure only? Yoshi has many issues and shall submit comments embedded within the original doc on the server. Add examples showing flexibility in queries. IEs are being defined in terms of TLVs and they need to be defined in more generic form. Harmonize with contribution #675: Contribution 21-06-0712-00-0000-IE_TLV_container B Accepted Contribution 21-06-0711-00-0000-IE_TLV_retrieval_no_exclusion Accepted qwAccepted-Modified{k) done 2006/09/21 2006/04/246^EQiaobingFXieGMember^Technical, Binding_49`12a 6.3.4.1.2bRemove 6.3.4.1.2.6.3.4.1.2.how this clearly.mAcceptedmctobeconsistentwithnotionthatoneinstanceofmihbein/VtodiscoverwhattypeofeventsaresupportedbythelinklaRV3 ۳vA~Page 18, sentence on line 22 changes as follows: " When provisioned the MN may use MIIS to obtain pertinent information such as new roaming lists, priorities and any other related information that would enable to utilize services in various access networks. The MIIS can be part of provisioning under service provider's control or may be a local database maintained by the client. "~wAccepted-Modified{k) done 2006/09/21۴ESanjeevFAthalyeGMember^Technical, Binding_19a5.3.2b0Clarify definition of reference point end-pointscR1 and R3 inetrafce seem to be interfaces between MN and network entity in figure 2. In this figure they seem to be interafces between netowrk entities.d141i Vivek GuptakIt should be clear which Reference Points are optional (informative)and which mandatory (normative) and in scope of specification. Not saying anything along these lines adds no value to definition of Reference points and they appear as only confusing.onfusing.wcadequatelyەWadjectiveeWadjustmentskWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWWWWWWWf Fkhatibi„HfederkhatibiIpr„Ifarrokhg Hkhatibi„JkhatibiKls„Kfarrokhh Jkhatibi„Lfarrokhi pkhatibi„Mfarrokhj khatibi„NkhatibiOtB„Ofarrokhk Nkhatibi„PkhatibiQw„Qfarrokhl Pkhatibi„RkhatibiSwi„Sfarrokhm Rkhatibi„T23U#`„UkhatibiVT23„Vfarrokhn Ukhatibi„WkhatibiX|"„Xfarrokho Wkhatibi„YkhatibiZ„Zfarrokhp Ykhatibi„[khatibi\^1„\farrokhq [khatibi„]khatibi^S„^farrokhr ]khatibi„_khatibi`@„`farrokhs _khatibi„akhatibib3„bfarrokht akhatibi„ckhatibid„dfarrokhctcinconsistentۃWW)W2WܕWWWinconsistentwithsection5.5VincorporateWܕWinconsistentwithsection5.5VincorporateWWwithsection5.5VincorporateWWWWWWWWWWWWWWWWie<"==xie><">qiaobing1=xie?!@@xieA?!Aqiaobing2@xieB5CCxieDB5Dqiaobing3CxieEGF! FxieGEGGqiaobing4FxieHWId\"IxieJHWJqiaobing5IxieK#LaN$`LxieMK#Mqiaobing6LxieNxieOKaOqiaobing7NxieP)QWS$pQxieRP)Rqiaobing8QxieSxieTPWTqiaobing9SxieUxieV6ZVqiaobing:UxieWxieX9dXqiaobing;WxieY6Z!@Zxie[Y6[qiaobing<Zxie\h memberᆃᇃሃቃኃዃጃፃᎃᏃᐃᑃᒃᜃᝃᤃ᥃ᦃᧃᨃᩃ᪃᫃ᬃᭃᮃᯃᰃ᱃ᲃ᳃ᴃᵃᶃ᷃ṃểᾃƒăƃǃȃɃʃ̃̓""""""""""""""""""v6:b5Remove Bold format for "time bound" and "confidence" c@The parameters "time bound" and "confidence" should not be Bold.d258g2230{k) done 2006/09/21 2006/04/28 >EAjayFRajkumarGMember^Technical, Binding_40a6.2.4bA*MIH_Command.confirm primitive should be removed from its current location and used to replace the lefthand-side MIH_Command.response at the bottom of the diagram. In other words, only four primitives should be shown: 2 on the top (request and indication) and 2 on the bottom (response and confirm).*c*cfor setting and retrieving the values of the configuration parameters that drive the functional behavior of the local MIH Function instance.c>Include the MIH_NMS_SAP in the Media Independent SAPs section.d232g2242wAccepted{k) done 2006/08/21 2006/04/28 :EAjayFRajkumarGMember^ Editorial_34`49a6.1.26/04/28 :EAjayFRajkumarGMember^ Editorial_34`49a6.1.230`36a5.6.1{ ۉbD rollback previously started setup type activities ExecuteActionThreshold 36 Variable LinkParamaeter specific threshold value that may cause upper layers to execute appropriate handover specific action Name Type Length Value LinkType 31 Variable Identifier of link for which Event Register was conducted RequestedEventList 4 Variable Array of event codes formatted as messaged-id:Event CodeE"1, Event Code2, Event Code3, .... @Af 33   33  S 33fcAGMobile Node with MIH function generally has several different kinds of access network interfaces. Different kinds of access network has different link parameter thresholds. When MIH fuction receives a message from upper layer, such as MIH_Configure_thresholds, it needs to know which access network interface it should conduct.7pcurrentۓW۽WVWcurrentlyݜWd01.00{W݃Wd2.0ܾWdecideۓWdecision۪W{WdefW.W:Wdefchangesmadeinsection3instead:VdeferܾWdefinition;Wdelete2Wdeleted)Wdeletedbits3and4)VdescriptionWRWdetails&WaWdetectedlWdiagram݃WdidۅWۓW)WRW{Wdidnotmakesection8changes{VdidnotrepeattheprimitivedescriptionthoughonlyaddedaRVdidnottrytoanswertheopenquestionsingroupdecision{Vdidn'tgWۓWdifferentݜWdoۓWܾWdowewanttocreateanewtableandcopycurrentradiusdraۓVdowewanttosplitthisintotwoiesasrecommendedaboveoܾVdoc۴WݒWݓW 331  339 33>d344g2246 2006/05/17=ENada, Golmie, Member^Technical, Binding_44`38b 2006/05/14osed of one of more Access Routers connected to one or 0cfiguresWfilteringWfime8WtheprimitivesdefiguresWfiltering W WwiththeprimitivesdeޗVfiguresWWijR=>EFarrokhFKhatibiGMember^ Editorial_22`22a5.4.3bChange "include" to "require"cImproved clarityd167{l) none needed 2006/09/21?EFarrokhFKhatibiGMember^ Editorial_22`46a5.4.3b3Change "Other IEEE groups" to "Some IEEE standards"cImproved clphrasingd174{k) done 2006/09/212006/08/29Marked@EFarrokhFKhatibiGMember^ Editorial_22`49a5.4.3b Remove "help"c6"facilitate" further on in the sentence conweys "help"d176{k) done 2006/08/29 AEFarrokhFKhatibiGMember^Technical, Non-binding_23`33a5.5bDelete "media agnostic"cFThe reference model includes a media-dependent part (the MIH_LINK_SAP)d181wAccepted{k) done 2006/08/29 EEFarrokhFKhatibiGMember^Technical, Binding_28`39-41a5.5.5c9The mapping is not fully be specified in Table 24 (P145).d205p/see 195 Editor's notes - mapping table updated.v;as per contribution 21-06-0691-02-0000-3GPP-3GPP2AmendmentswAccepted(qbmbit/sYWmeanWmeaning4Wmeaningoflinkparameterthresholdshouldbeexplainedposs4VossoVoVngoflinkparameterthresholdshouldbeexplainedpossoVoVoVsoVoVsoVoVcxie€exiefb4€fqiaobingqexie€g!#h&j')H3JilrnuF" €hperesseGxieig#€iqiaobingrhxie€jxiekg&€kqiaobingsjxie€lxiemgi€mqiaobingtlxie€nxieogr€oqiaobingunxie€p`hp$q's2L:bdrH'Xj"0€qxierp$€rqiaobingvqxie€sxietp'€tqiaobingwsxie€u &24v::TZfquv"@€vxiewu4€wqiaobingxvxie€xxie€2:#€xie2€qiaobing}xie€:&EPeretzFFeder^ Editorial_112`61bAptimer and release the saved copy of the packet. The source may at most utmost make two retransmitted attempts inp@AR  33?  G  M  33Rcwtimer and release the saved copy of the packet. The source may utmost make two retransmitted attempts in Correct textd710g2265{k) done 2006/09/21 2006/04/28 'EPeretzFFeder^Technical, Binding_114`15a8.3.3bAvThe MIH Function Header consists of a two parts; one with fixed length and another with variable length. The fixed length part of the header carries the essential information which is present in every frame packet and is important for parsing and analyzing the frame packet quickly. The variable length part of the header carries information which is optional in some cases.v@v@cc Add context transfer d644g2260 2006/05/14 2006/04/28cconfiguregWۄWۉWWYWkW܂W܄WaWWoWWWWWWWWconfiguredۄWZWޖWconfined1Wconfirm>WWW{WWWWW#WconfirmprimitiveformihcommandisnotdefinedVconflictedWconflictingۼWconflictsWconfusedWconfusing(W)WۻW۽W W:WiWܫWWWWkWzWW]WWWW6W7WpWWconfusingphrasekV6V6VkVvVvVvVvVvVvVvVvVvVvVvVvVvVvVvVvVvV„ohbavc„yoshihiroݜohba„ohba Y„yoshihiroݝohba„ohbau„yoshihiroݞohba„ohba„yoshihiroݟohba„ohbaZ„yoshihiroݠohba„ohbay6„yoshihiroݡohba„ohba(„yoshihiroݢohba„;Pbparagraph`WەW۫W۶W)WWWW1WparagrpahWparameterGWJWTWWWۃWYW`W܁W܂W܎WWW[WaWWހWރWދWތWޖW5WlWWWWW4W8WWWWWparametersAWGWIWOWRWTWTW\W\W\W{WWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWMWubirdas subirsubirAdas subir*"subir*das subirsubirtdas subirsubirdas subirdas subir@5subir@das subirsubirfdas subir:subirdas subirsubir"Xycforۚ~7forthecasewheremihfuncionisplacedinthe3gpp2networ@]foreign@form@forwarding@fully@functionality@functions@g@2general@(get@goal@going@Chandover@)handovers@have2havemorespacebetweencharactersinsta/ueandpsdn/fabox@header@here@high@horizontal@phrpd@ie@if>ifweadopt21-06-0522-04-sessioidentifierthelengthfield@,opt21-06-0522-04-sessioidentifierthelengthfield@,field@,periodicbasis@if9if6if6f6":bhnadover܀WhoIWWho-typeWhoc>Whome9WW!W'WhorizentalWhorizontal?WAW:WWhorizontallyۿWhotspotWhoursHWhowVWW}WYWWWW/WWWhow/inWWYWhow/inܢWܢWWܴWܿWW\W}WXWYWhow/inܢWܢWnܢWܢWhow/inܢWܢWW.W.W.W.W.W.W.W.W.W.W.W.W.W.W.W.W.W.W Dccepted-Clarified@cinetrafce۴Winetrafce۴W۴Wnetrafce۴W۴Wrafce۴W۴Wafce۴W۴W_fbestimation WWetcAWIWۖWYWܵWWmWtWWWWWW8WWethernetsWWWWWWethertypeWWetypWeuqivalentކWevaluateTWevaluatedTWeven^W?WWWWWeveniftheschemawereretrieveditwouldn'tassistaVWWWWWWWWWWWWWWWWWWWWI€qiaobingLxie€[xie sJ€ qiaobingMxie€ feder6G…peretz feder…feder6v…peretz feder…feder6 …peretz feder…federR…peretz feder…federge…peretz feder…federSY…peretz feder…federV"…peretz feder…feder9!…peretz feder…peretz feder…JKDv{a) awaiting resolution 2006/09/21 2006/04/24desolution 2006/09/15 2006/04/24MarkedwEQiaobingFXieGMember^Technical, Binding_112`16a8.3bADelete the following sentence: ... decision making is outside the scope of the standard. Figure 24 shows possible MIH message delivery and its relation with other protocol layers. And delete Figure 24. @Af 33  33$  Z  TT  33fcAFigure 24 is incorrect. In particular, it implies MIHF using IP directly and does not show the possibility that MIHF can also use UDP/IP or TCP/IP as transport. More general, the value the figure itself adds to the spec is very limited. @A  33d704g2332iJin LeejDelete figure 24ksuperceded by 697m SupercededwAccepted{k) done 2006/08/29 2006/04/24xEQiaobingFXieGMember^ Editorial_113`23a8.3.2vZby comments 482, 508, 514,515, 267 which take care of confirm/request/response primitives.w Superceded 2006/09/21 2006/04/28EAjayFRajkumarGMember^Technical, Binding_84`30a7.4.2b5Add Call Flows as described in DCN 21-06-0622-00-0000cACA general comment with MIH Event and Link Events is that it is unclear what the call flow for Registering Link Events would be. MIH Events by definition are generated by MIH User and Link Events are generated by MIH Function. At the same time MIH Event could be generated by an MIH Function towards a Remote MIH Function. Cd587g2225i Vivek GuptakOA very similar call flow for amore generic case is shown in Figure 15 as well.mAccepted-Clarifiedveby comments 287, 289, 292, 293, 294, 295 and contribution 21-06-0641-01-0000-Command_service_flow.pptw Superceded 2006/09/21 2006/04/28EAjayFRajkumarGMember^Technical, Binding_138`51a8.6.1.2a8.6.1.2a8.6.1.2Px_bnotificationsLWېWWWWnotifyWWnowWnullHW}WxWzWnumber_W~W܍WWݗWWqWtWWWW@WXWlWWnumberofoperators4octetsfollowed@VnumberedNWnumbersSWWobjective-Wobtain#W}WrWxWzWWWWW}W}W}W}W}W}W}W}W}W}W}W}W}W}W}W}WguojunxiangۃnadagolmiememberhliuKb€yuanۆliu€Kh€yanpengjunxiangguoۇ€c#€c€yanpengjunxiangguoۈ€U&€zhuangU€hongchengۉ zhuang€quHi€bingyunۊqu€zhuang<E€hongchengۋ zhuang€ j€zhuang €hongchengی zhuang€jiangH7€bingqiangۍ jiang€:N {done4W5W7W8W9W<W?W@WAWEWGWHWKWLWMWNWOWPWQW^WeWfWgWiWjWkWlWmWnWpWqWrWsWwWzW{W}WW݃W݅W݆W݇W݉W݋W݌WݍWݎWݐWݑWݒWݓWݔWݕWݖWݗWݘWݚWݛWݜWݭWݲWݵWݸWݹWݺWݽWݾWݿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWW W"W#W$W%W&W'W(W)W*W,W,WWYWiWW۴WWܵWWWLWzW}W,W>W@WBWCW2WitodoVV۴VVܵVVVLVzV}V,V>V@VBVCV2V8WGblayers"W*WAWOWPWQWRWSWTWUWpWwWۉW6WNWiWkWݍWݎWWW WWW,W2W4W5W5WWWWW7WkWsWWWWWW7W7W5W7W7W5WWWWW9U;qiaobing0:xie<"=Cxie?!@@xieA?!Aqiaobing2@xieB5CCxieDB5Dqiaobing3CxieEGF! FxieGEGGqiaobing4FxieHWId\"IxieJHWJqiaobing5IxieK#LDaNh$`LxieMK#Mqiaobing6LxieNxieOKaOqiaobing7NxiePP)QWS$pQxieRP)Rqiaobing8QxieSxieTPWTqiaobing9SxieUxieV6ZVqiaobing:UxieWxieX9dXqiaobing;WxieY6Z!@Zxie[Y6[qiaobing<Zxie bmodule?WܤW.WAWmomentWmonthHWmoreAWPWqWۢW۽WܰWWNWIWYWށWރWtWWWWWWWWWWWmoreandmergetextbetweenlines23-43into8.3.1qVmoreappropriateWWW9W9W9W9Wba… yoshihiro ohba…  mU… ulisesolvera … j…ulisesolvera …KV…ulisesolvera…g'…ulisesolvera…federx&…ulisesolvera…lp…ulisesolvera…)…ulisesolvera…p1% …p…ulisesolvera…1…ulisesolvera…ulisesolvera…ulisesolvera… !+J…!ulisesolvera …"ulisesolvera…#:vcleanWclear WݜWWWWW WWWclearlynW\WWcleraWclient۳WWclusterWcoHWcodesWcoldWcollectivelyTWcolor\WcolumnWWWWcombination۔Wcome!Wcommand\WWWWcommandsRW\WWWWcommentIWUWVWWWZWfWWWۑWۑWfWۑWۑWۑWۑWۑWۑWۑWۑWۑWےWWdelete۪W݃W-Wdeletethelastsentenceofsecondbulletandaddmihuserf݃Vdeletethelines-Vdeletethesentencementionmihfisalogicalentityaspart۪Vdeleted۷Wdevices;Wdifferent۫W0Wdifferentaccessnetworkssupporthorizontalhandovermechan۫Vdiscovering;Wdiscovery;Wdocument2Wdoes۵WWdraft2Wdrop"Wdropthereservationpartbutkeepthequerypart"VeachWeither3Wenable۳WenablesWWj $^bindingܑWܒWܓWܔW, Non-binding_112`21a8.3bA[Delete the following rows, page 112, line16] : Figure 24 shows possible MIH message delivery and its relation with other protocol layers. [Remove figure 24, page 112] @A>  332  33  33>us' valuse can be taken from the values defined in section 8.4.2.17 , or vice versa.d647g2220 2006/05/14 2006/04/307EJinFLeeGMember^Technical, Non-binding_112`21a8.3bA[Delete the following rows, page 112, line16] : Figure 24 shows possible MIH message delivery and its relation with other protocol layers. [Remove figure 24, page 112] @A>  332  33  33>_ 33} >con | Bitmap | 0-31 | 0: LINK_DISCONNECT | Fmathieu Eperesse…GmathieuhperesseTbaddmihlinksaptosection7.1.2CVaddmihfmobilenodemihnetworkVVaddmoredescriptivetextmoveexamplequeriestotheannexVaddmoredetailtotable11VaddmoredetailtothecostiedefinitionVaddmoreinformationonscopingofthestandardVaddnewsectionsprobablyaftercurrentsection8thatdetaWVaddnewsubsectionsandtextinbothsection5andsection[VenodemihnetworkBVCVCVion7.1.2CVaddmihfmobilenodemihnetworkBVCVCVhnetworkBVCVCVtextmoveexamplequeriestotheannexVaddmoredetailtotable11VaddmoredetailtothecostiedefinitionVaddmoreinformationonscopingofthestandardVaddnewsectionsprobablyaftercurrentsection8thatdetaVޚVV V:VxVaddnewsubsectionsandtextinbothsection5andsection'VޥVVVEV߃Vaddqueryresourcelistattheendoftheparameterlist܎Vbfix۠W݅W݆W݇W݉WݭWYWZWfixit݅V݆V݇V݉VݭVfixtheinconsistencyYVZVfixtypotowardtheendoflineall۠VfixedܑW'WWWflagWflexibilityAWiWtWflexibleAWWflagۂWflexibilityAW_WiWflexibleAWAWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWfollowedWݙWfollowing*W_WjWkWmWnWuWvWwWxWەWW3W=WHWRWSWTWUWVWWWXW\WcWdWmWܚWܬWܹW|W݊WWW W2W7WIWފWޔWިWWWHWfollows WJWXWۂWېWWCWYW\WܤW)W0WlWޞWWWW W7W>W/ <bwhichwhirepWwhole۫WwhyW*WW/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/Wzqiaobingyyxie€{@=P()rYfh|"€|xie}{h€}qiaobingz|xie€~* VDG,R#€xie~D€qiaobing{xie€xie~R€qiaobing|xie€.1025. ,jAThe MIH is L-shaped to show that it can communicate with different layers, it shows clearly that it is not a layer per se, but rather a function that interfaces with lower and higher layers, to facilitate generic mobility management. It is horizontal at its base because, it can interact with many L2 technologies It is vertical in its top part because it can interact with L3, L4 or applications. Just a matter of representation, I hope it helps in the understanding of the multiple relationsBhips within a stack.. v(make MIH Function horizontal in Figure 1wAccepted{k) done 2006/09/21 2006/04/281-EAjayFRajkumarGMember^Technical, Binding_22`19a5.4.3bQEither these should be deleted or written as objective and measureable criterion.cxThe three criterion stated in the normative text for selection of Information Service syntax are subjective and vague. d162g2259i Vivek Guptaivek Guptaplicitly mentioned in the text. #d16er celementsKWZWCWWsWtWWWWWWsWelseW W!WelsewhereܛW.WAW9Welsewhereinthedocument.VembeddedtWݸWWenable<WenablesۋWencapsulatedWޏWencapsulatedrouteradvertisementisencapsulatedޏVencodeWencodedJWencodingJWGWWW+WencodingsWWend-to-endWengineWݎWenglishwWxWyWzW{W~WWWWWWWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہWہW(…`peretz _feder…aperetz  feder…bfedercB…cperetz bfeder…dfedereU…eperetz dfeder…ffedergq…gperetz ffeder…h i6…ifederjh …jperetz  ifeder…k ldn7…lfedermk …mperetz  lfeder…nkd`.btypemimetlvvariableamimetypetlvanoctetstringforaހVނVtypesizelengthdescriptionvalueހVނVtypelistWtypes?WAW`WܤWܾWݖWWIW[WtWwWyWWWWWW W3WWWtypicalWtypicallyAWܤWܱWݎWsWuWtypicallyinaheterogeneousnetworkenvironmentcomposedofܤVtypo۠Wucd8Wudp/ipWudp/tcpsWue܋Wuiuc8WܤVcomposedofܤVܤVܤVܤVWWWWWWWWWWfeder…feder6 …peretz feder…federQ…peretz feder…federfe…peretz feder…federSY…peretz feder…federV"…peretz feder…federrajkumar9!…peretz feder…peretz feder…federxW…peretz feder…8!0…bgeographicalWWgeolocationWgeospatialݖWgeran WgetdWeWlWzWWWBWޅW=WtWWWW>W{WWWWWgets>WgetstatusresponsesetWgiveTW}WtW9Wgiveexampleoperationsofhowthemediaindependentinforma}VgiveniW}WW8WW4WzWgives<Wgmm$Wgni@Wgo]WWWgoesWWWjeev *athalye,sanjeev fathalye-athalye.$.sanjeev -athalye/athalye0F0sanjeev /athalye1athalye2e2sanjeev 1athalye3athalye43athalye5athalye6+"6sanjeev 5athalye7athalye8+"#8sanjeev 7athalye9athalye:+bg:sanjeev 9athalye;athalye<W23>sanjeev =athalye?7b6ZW)WRWܑWܔW,W1W6WqWrWWW8WW6.1W6.2.5.1W6.2.5.1mihcommandsV6.3;W6.3.1`WWW6.3.2AWBW6.3.3pW6.3.4pWWW6.3.4xxinformationquerytypeV6.3.4.1sW6.3.4.1.2^W6.3.4.1.4AW6.3.4.2.1BW6.3.5`W6.3.6uW6.3.7vW6.3.8jWW:W63W65WW690vWvWvWvWvWvWvWvWvWfeder…federPZ…peretz* feder…federi…peretz+ feder…rajkumar…ajay, rajkumar…rajkumar*…ajay- rajkumar…ajay.  rajkumar…rajkumarJ…ajay/ rajkumar…ajay0 0rajkumar…ajay12  rajkumar…rajkumarS…ajay3 rajkumar…rajkumarY…ajay4 rajkumar…rajkumare…ajay5rajkumarS-kdetails"WWdeviceWdevicesWWdhcprWdifferentWWWWWdifficultWdirectionWdiscovery|WdiscussiongWWdoۓWWWWdocwWxWyWzW{W~WWWWWWWdocumentWdoesAWvWWWWWWdoesn'tWW}WdomainrWdon't|WWYWdon'tmentionintergernumbersbutusethetypeiexxxnamesYVdowndWdraft۳WWWWdscpWdynamicWWdynamicallyWeWeach\WpWuWWedcaWedgeWefficientwWxWyWzW{W~WWWWWWWWWWUecenough@entries@equipment@Berror@ event@events@Vexactly@Nexcluding@,exhaustive@expansion@Uexplainusageofthewordmedia@field@fig/table@:fig/tableifapplicable@figure24isincorrectinparticularitimpliesmihfusingi@figures@finalized@ized@theprimitivesde@fime@finalized@usingi@filtering@finalized@pdatedwiththeprimitivesde@fime@force@form@forwarding@front@function/operation@1functionality/capabi@g@2general@(get@goal@goes@ handover@2handovermoduleisneverdefinedorusedelsewhere@handoverneedsabetterdefinition@have$havemorespacebetweencharactersinsta/ueandpsdn/fabox@he@here@high@horizontal@phrpd@ie@ifL#bpairGWlWpairsCWsCWCWCWCWingWpairFWGWGWWWWWWWWWWWWWWWWWWWWWW rajkumar…rajkumarZ…ajay: rajkumar…rajkumarG…ajay; rajkumar…ajay< 3rajkumar…rajkumar>…ajay= rajkumar…rajkumartaniuchi…ajay>? rajkumar…ajay@ "rajkumar…rajkumara*…ajayA rajkumar…ajayB irajkumar…rajkumark…ajayC rajkumar…ajayD lrajkumar…ajayE rajkumar…rajkumar9#…ajayF rajkumar…rajkumarp&…ajayG rajkumar…rajkumarp(…ajayH rajkumar…rajkumarN:…ajayI rajkumar…rajkumarm4…ajayJ rajkumar…ar 6bA[Replace 'CurrentLinkAction' values by the values defined in 8.4.2.13, page 100, page 101] : ----------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | Description ------------------------------------------------------------------------------------------------------------ CurrentLinkAction | Bitmap | 0-31 | 0: LINK_DISCONNECT | B | | 1: LINK_LOW_POWER | | | 2 : LINK_POWER_DOWN | | | 3 : LINK_NO_ACTION | | |4 : LINK_RESOURCE_RETAIN | | |5 : DATA_FORWARDING_REQUEST | aconeiWۄWۋW'W:WzW{WW+W݆WݜWWW'W/W>W1WtWuWvWWWWWWWWWWWWWW?WAWBWDWGWHWJWKW[W]W^WbWWWoneofmanyVoneofthestackmaybeVonesەWەWەWoneofmanyVoneofthestackmaybeVonesەWەWmanyVoneofthestackmaybeVonesەWەWoneofmanyVoneofthestackmaybeVonesەWەWezathalye{T{sanjeev zathalye|&}DE#p}athalye~|&~sanjeev }athalyeathalye|DEsanjeev athalyeathalye^`sanjeev athalyeathalye^*2sanjeev athalye%%athalye%sanjeev athalye#%`athalye#sanjeevw Superceded 2006/09/21 2006/04/2815EAjayFRajkumarGMember^Technical, Binding_67`17a7.2.2.2b+Change Link Event DeRegister to a "Command"cAIEntry 2, "Link Event DeRegister" has been defined as an Event even though it is more of a command to show an interest in a set of events. This is similar in spirit to the Link Configure Threshold, which has been defined as a Command. Also, note that Events are defined to go northbound, whereas MIH Event Register goes southboundId498g2223w Superceded 2006/09/21 2006/04/2815EAjayFRajkumarGMember^Technical, Binding_84`23a 7.4.1.2.3bzThe northbound primitive, generated locally in response to a southbound .request primitive should be a .confirm primitive.cThe statement "This primitive is generated when MIH_Capability_Discover.request primitive is received by MIH Function." is semantically incorrect when applied to a .reponse primitive. d585g2243585g2243585g2243Mb31ۉWRW1W6W32TWUWVWWWoWWW33ۉWWUW33aW34ۉW3493uW35ۉW35-40W36ۉW37-43`W3753:W38ۮWW38-49W39W3guW3glinkW3gpp۽WYWHWsWWWWW3gppsystemsalreadybroadcastV3gpp/3gpp2W3gpp2&W'W1WHWsW WYWYWYWYWYWYWsdaleyঃৃਃ੃ઃૃdavid.1famolari,-/0feder  "#$%&'()*stuvwxyz{|}˃΃#gomie23groetingܑܒܓܔܕܖܚ҃ӃguimingۄWWWWWWWWܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܙܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚathalye@_#&N%`athalye#sanjeev2 +>EXiaoyuFLiuGMember^Technical, Non-binding_64a7.2.1b)Move Table 13 - C_SAP Primitives to AnnexcAA few concerns regarding Table 13: 1. This table is media specific mapping between 802.21 to 802.16. This is useful info but not in scope of 802.21 WG. This table may be put in Annex 2. The work in the 802.16 NETMAN is not finalized. If there is any change of the table in 802.16 WG, 802.21 has to rework on this table to make corresponding changes. If not, it may cause confusion between 802.16 and 802.21. 3. The media specific amendmens to other SDO, e.g., 3GPP in MIH_3GLINK_SAP in section B(7.2.1.4, are not in the normative texts.d909g2216wAccepted{k) done 2006/09/21 2006-04-3013?EXiaoyuFLiuGMember^Technical (was Editorial)_77`65a7.3.13.2a7.3.13.216wAccepted{k) done 2006/08/27 2006-04-3013?EXiaoyuFLiuGMember^Technical (was Editorial)_77`65a7.3.13.227a5.5.3b | Bit 5 : Emergency SebiliJ @bforforconsistencywithuseselsewheremobilitymanagementiss۝Vforexampleitwouldbelikesayingdoyousupportrfc4889Vforexampleradiusnas-port-typeݔVforthefirstcommentthemihmightalsonotifythelocalmiVforthemultipleoctetlengthrepresentationshowthatfirstVVVVV9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9Wn†tan†pekyewotan†kenichip  taniuchi†taniuchi i†kenichiq taniuchi†kenichir 4taniuchi†kenichis taniuchi†kenichit taniuchi†taniuchig†kenichiu taniuchi3۶ESanjeevFAthalyeGMember^Technical, Binding_21`58a5.4.3bA?Add a sentence at end of paragraph: "Additionally or alternatively, information may be present locally in the MN, and may be learned by the MN or pre-provisioned, or both. The definition of and indexing of such local database, as well as regime of maintaining it or accessing it, is outside the scope of this document"?cUse of network based server as a sole source of Information Seervice is too restrictive, and may lead to sub-optimal solutions.d154i Vivek Guptak Good point!mAcceptedwAccepted{k) done 2006/09/21۹ESanjeevFAthalyeGMember^ Editorial_22`40a5.4.3bRemove "it is"csuperfluous segmentd171{k) done 2006/09/21 d d 154i Vivek Guptak Good point!mAcceptedwAccepted{k) done 2006/08/27۹ESanjeevFAthalyeGMember^ Editorial_22`40a5.4.3bRemove "it is"csuperfluous segmentd171{k) done 2006/08/27 EAjayFRajkumarGMember^Technical, Binding_63`9a7.1.1b[Add LSAP and CS_SAP. Also, MIH_NMS_SAP should be simply listed as a media-independent SAP. cEThe list of SAP's is not complete, since LSAP and CS_SAP are missing.d485g2241i Vivek Guptak\802.21 is not modifying LSAP and CS_SAP in any way. Hence they were not listed in section 7.mAccepted-Clarifiedvby comment 483w Superceded 2006/09/21 2006/04/28 2006/04/28MarkedEAjayFRajkumarGMember^Technical, Binding_66`10a7.2.2.1b(Change MIH Event Register to a "Command"cADEntry 2, "MIH Event Register" has been defined as an Event even though it is more of a command to show an interest in a set of events. This is similar in spirit to the MIHConfigure Threshold, which has been defined as a Command. Also, note that Events are defined to go northbound, whereas MIH Event Register goes southboundDd493g2220v comment 492w Superceded 2006/08/29 2006/04/2814EAjayvfromQWRWSWTWW1WHW`WzW݃WݓWW"WގWqW}WWWWWWWWWWWWWW>W~WWWWWWWWfunction*WQWRWSWTWlW"W,W4W5W#WjWWWWfunctionalWfuncton{WfurtherZW"WWW"W1WfutureWg"WWWWWWgeneralW WWgeneralnotetoeditorVgeneratedWgenericZWgetlWWWgetstatusrequestsetWgetstatusresponsesetWgiveTWgivenݓWgivesWgloballyWWgoێWgoaheadandaddittotheparamsetoftheprimitivedefiniێVgonnamWWgroup!WWgroupadhoctaskforcetoworkonthisandcomebackwitha!VguptaWhandingTWhandleܛWWݜWhandledWW Wows۳Vd0WupWverticalW *vA 33<  33? 33@  33E 33u  33x 33{  33cfigure24isincorrectinparticularitimpliesmihfusingiwVfigure30inannexa-1isnotupdatedwiththeprimitivesdeVfigure30inannexa-1isnotupdatedwiththeprimitivesdeޗVe24doesnotrelatetothesection8.3weputittosh7V7Vsnotrelatetothesection8.3weputittosh7V7Ve24doesnotrelatetothesection8.3weputittosh7V7V24doesnotrelatetothesection8.3weputittoshtoshfigure24doesnotrelatetothesection8.3weputittoshtosh)28ERSWgru&xieWqiaobing xie!w$(13U7BWHIYYf0gv37q'u)B#xie$"@$qiaobing&'#xie%xie&"9&qiaobing(%xie'xie("q(qiaobing)'xie)xie*"u*qiaobing*)xie+c,C,xie-+c-vwith*WCWZWlWەWW1WW{WWݓWݜW"WLWMWކWއW\WjWWWW#W=W?WnWWwithinZWݓWWwon'tݓWword4WdWWwordheterogeneouswasdeletedbyanothereditorialcommentVwordingWworkZWW W!WworkedWWWwould۳WWWWWwriteWwrongWwwwHWxml/rdfWyoshiZWyouWWzeroށWރWwaccepted $()+@ACDGKLOP^cdehipsvwۀۃۄۉۋێې۴۶ۼ۽ƒʃуۃ܃#$,:;ABCNSTUVWYZ]`hkm|܂ܑܒܓܔܕܖܚܛܭ΃Ѓ҃߃'+13AEHLOPRabkzݍݎݓݔݕݖݗݘݛݵݺݽݾʃ  'akmeanAWtWvWWWmechanismWWmechanismsWmediaOW\WWWW}WmentionYWmentionedWWmesaurable-WmessageWmessagesWmethods WmihWOW|WWWWvW}WWmihfunctioninthenetworkmayadvertiseitsmihcapability}V}Vihcapability+V+V+V+V+V+V+V+Vss links (as the 802.3 instantiation and part of the 802.11 instantiation of the L2 pBortion of the MIH_NET_SAP). 5.6.1.5 CS_SAP The CS_SAP, defined in the IEEE 802.16 standard, provides the interface between the MIH Function and the service-specific Convergence Sublayer in IEEE 802.16 networks. This SAP is used for the L2 transport of MIH messages across 802.16 access links (as the 802.16 instantiation of the L2 portion of the MIH_NET_SAP). 5.6.1.6 MIH_3GLINK_SAP .....continue with the current text........ | List of supported IS Query types on client bmobility?WAW۝WWܤWIWW"W4W5WWWWWWWmobility-managementGWmobilitymgmtprotocolWmodel$WۮW,WTWUWVWWW݃WWWW<Wmodelaftersimilarclauseonpage17line38ۮVmodificationsWmodifiedWmodify5WWWmodifythesection7.3.7.3asfollowingVmodifythesection7.4.4.1.2page85line305V5Vine305V5Vthesection7.4.4.1.2page85line305V5V85line305V5V.4.4.1.2page85line305V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5VWWmomentWmonthHWmoreAWPW_WqWۢW۽WWWܰWWWWWWWWNWIWXWYWށWރW޿WWW.W_WnWߝW߬WWWW(Wbjis,WvWށWjWuWWWWWW WW=WtWzWWWWWWisnetworkselectionacrossheterogeneouslinksalsopartofVissue"Wit@W,WށWuWWWWWWit'sWit'snotclerawhatismeantbypersistenturlandastandarVitemܾWitemsܾWits,WitselfWjust,WށWjustleaveitastlvspecificparametersށVkeepdWkeepthenewpoainformationdVknowWknown?Wl-shaped,Wl2,Wl3,Wl4,Wlast{Wlayer"W,WWWWlayers"W,WlbtWleaveށWlength|WlikeWlineWtWWWWWW W W W W WWWW WlinksWWlistܾWvWWlistedܾWlocWYWlocalWWW WlocatedWlocationsWlongWlook=Wlower,WmacܾWWmakeW+ |$bAUpon reception of this primitive, the MIHF on target new PoA may either interact with upper layer to achieve enough information or further deliver this message to the MIHF in the network, e.g Access Router with MIHF which may have enough information on this message. When this primitive is delivered to the upper layer of the MIHF in the network, e.g, Access Router with MIHF, this may trigger to send network address related information, e.g, Router Advertisement either directly to the mobileB node or to MIHF.@AR  33.  5  8  33Rcstent with other SDOs d653g2262wAccepted{k) done 2006/08/21 2006/04/28 $EPeretzFFeder^ Editorial_104`48b7.4.14.1.3bf  33      33  33cc Add context transfer d644g2260 2006/05/14 2006/04/28FRajkumarGMember^Technical, Binding_66`12a7.2.2.1b*Change MIH Event DeRegister to a "Command"cAGEntry 3, "MIH Event DeRegister" has been defined as an Event even though it is more of a command to show an interest in a set of events. This is similar in spirit to the MIH Configure Threshold, which has been defined as a Command. Also, note that Events are defined to go northbound, whereas MIH Event Register goes southboundGd494g2221vby 492w Superceded 2006/09/21 2006/04/2814EAjayFRajkumarGMember^Technical, Binding_67`15a7.2.2.2b)Change Link Event Register to a "Command"cAGEntry 2, "Link Event Register" has been defined as an Event even though it is more of a command to show an interest in a set of events. This is similar in spirit to the Link Configure Threshold, which has been defined as a Command. Also, note that Events are defined to go northbound, whereas MIH Event Register goes southboundGd497g2222497g2222gbcollectsܡW,Wcolors݃WcolumnWYWWWWWWWWcombinationnWݕWW WWcombinationofactionsispermissiblenVcomeܰWcomeupwithamoreaccurateclassificationschemeܰVschemeܰVܰVc€yanpengjunxiangguoۈ€U&€zhuangU€hongchengۉ zhuang€quHi€bingyunۊqu€zhuang<E€hongchengۋ zhuang€ 4G<j€zhuang €hongchengی zhuang€jiangH7€bingqiangۍ jiang€?ƒvivekܿ guptaƒguptak3ƒvivek guptaƒgupta4ƒvivek guptaƒ gupta!_)ƒ!vivek  guptaƒ"gupta#gƒ#vivek "guptaƒ$vivek guptaƒ%vivek guptaƒ&vivek guptaƒ'gupta(ƒ( 331  339 33>d344g2246{k) done 2006/09/21AENada, Golmie, Member^Technical, Non-binding_44`51bGDefine and make definitions in section 6.3.4.1.4 and 6.3.2 consistent. nsistent. rk security and quality of security capabilities"G@A> 331  339 33>d344g2246{k) done 2006/08/23 AENada, Golmie, Member^Technical, Non-binding_44`51bGDefine and make definitions in section 6.3.4.1.4 and 6.3.2 consistent. ۏÃÃ0- isubir#WAۓWCWܹWܹWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWl@baddedAWZWWW}WsWWmWWZWWWW}WWWWWelated to a certain MIH Service. It might not be so appropriate to place general mobility concepts in the section 6.3 which is for MIIS only. 2. The Figure 19 should focus on the illustration of MIIS. It seems that the the current title and description focus on the concept of Horizontal and Vertical Handover  Horizontal and Vertical Handovers are general and not directly related to a certain MIH Service. It might not be so appropriate to place general mobility concepts in the section 6.3 which is for MIIS only. 2. The Figure 19 should focus on the illustration of MIIS. It seems that the the current title and description focus on the concept of Horizontal and Vertical Handover @ÃۏÃÃ0-Ã`à ܈Ã0܉Ã@܊ÃP܋Ãp܌ÃÃܚà ܍Ã0ۀÃPÃpÃہÃ0ۉ dDTr WbcAThe curremt spec says: "Various classes of inter-operability and implementation compliance shall be specified based on the set of mandatory and optional features in the specification." However, no such definitions have been defined in the document. @A>  33   33>d34g2236v by comment 31w Superceded 2006/09/21 2006/04/24XEQiaobingFXieGMember^Technical, Binding_18`13a5.3.2bA1. Remove section 5.3.2 --or-- 2. Change the section title to "Illustration of a MIH-enabled Multi-technology Wireless Network" and move the section into an informational annex. @A  33cThe need for Section 5.3.2 is not clear: 1. Its current content is NOT depecting a logical network reference model. 2. It is not clear we need a logical network reference model.d128g2241iMathieu Peressej$Related comments #128 #142 #108 #127vRejected by Vote 8-8y Vote 8-8bgreaterݗWtW+W9WgroupWtWgroups?WWWWgsmWPWgsm/gprsJWguaranteeWguidelineWguidelinesWh2WWhissuedVh-aaa݌W!Wha!WhandAWhandAWAWWWWWWWWWWWWWWWrWhandleWhandledWhandoff)WJWhandoff/handoverܜWhandover W"W#W,W/W0W5W?WOWPWRWVWWWfWpWuWvWWۂWۇWۉWۋWەWۻWWWW#WRWfW܀W܅W܉WܤWܳWܴW)W|W݊WݍWWWW!W"W#W.WAWXWYWޞWޠWޡWުWޭWޮW޳W޽WWWWWWWWWWWWWW WWWWWW"W,W>W@WAWJWMWNWSW]WmWnWpWtWuW|W~WW(VbdetectionVWWWdeterminded5Wdetermine#W<Wdetermined WޖWdeterminesW/WdeterminingWdevelopedtWdeviceۜWܫWWWdevicetoreconfigureandpresentdatatoupperlayersVdevicestWdhcprWdhcpv6WdiagramۿW>WWWWdiagram/textWdiagrams/useWdicovery|Wdifferences*Wdifferent W"W?WAWOWPWQWTWUWpWۙWrWܤWܾWW0WQW݃WWWޅWnWtW|WWsWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWRS۫ 2006/09/21MarkedۭESanjeevFAthalyeGMember^ Editorial_16`19a5.3b=Rename the Non-PoS MIH entity to MIH Non-PoS for consistency.c=Rename the Non-PoS MIH entity to MIH Non-PoS for consistency.d112{k) done 2006/08/29 ۮESanjeevFAthalyeGMember^ Editorial_17`27a5.3.1b-Model after similar clause on page 17 line 38c8Break down sentence for better readability, after comma.d119{k) done 2006/08/29 ۯESanjeevFAthalyeGMember^ Editorial_17`43a5.3.1bSee previous commentcSee previous commentd121{k) done 2006/08/29 ۰ESanjeevFAthalyeGMember^ Editorial_17`57a5.3.1b*Use "a" as in other similar cases in tablec'Make indefinite article form consistentd124{k) done 2006/08/29 ۱ESanjeevFAthalyeGMember^ Editorial_18`17a5.3.2b"access technologies"cSimplify phrasing, remove dashd129{k) done 2006/08/29 ۲ESanjeevFAthalyeGMember^ Editorial_18`56a5.3.2Lcjustified^WfWgWhWiWjWkWqWwWxWyWzW{W|W~WWWWWWWkWkeptWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWjWkWmWnWoWzW{W|W}W~WہWknown܋Wl݆WWl-shaped,Wl2W܌WܩWܭWܲWWW3Wl3rWWܩWܴWW+W3WDWWW0WlabelqWlabeledqWlacDWlackWWWW[W\W]WfWlanguagejWkWmWnWoWzW{W|W}W~WہWܬWlargeWWWlargelyxWlastqWsWܕWWWWWWޗWlatenciesWlatter.WWWbbracketsWfWbranchvWbreak4W5W*Wbreakoutthesegmentstartingwithinwhichcaseintoasep*Vbreakthesentenceafterthecomma4V5Vbroadcast#WPWWWWWWbroadcasting}WbsܵWbssid[WbstnܵWbufferUWbufferingVWbuffersUWbutۜW܋WW>WWby"W?WAWLWRWcWdWiWpWxWېW۳W۶WWW#WGTWVWYWZWkWzW{WܟWܡWܣWܥWܧWܾWWW0WPW݃WݗWWWWWWW WWWW W#W%WWބWޅWއWދWތWWWދWތWތWތWތWތWތWތWތWތWތWތWތWތWތWތWWތWތWތWތWތWތWތWތWތWތWތWތWތWތWތWWWWWWWWWWWWWWWWyoshihiroohba„|4 ܤbAAChange as follows: "Typically, in a heterogeneous network environment composed of multiple media types, it is the handover decision module or higher layer mobility management module that will collect information from different media types and assemble a consolidated view to facilitate its inter- media handover decision.A@A 33:  33F 33  33 33  33! 33cA Typically, in a heterogeneous network composed of multiple media types, it is the handover decision module or higher layer mobility management will collect information from different media types and assemble a consolidated view to facilitate its inter- media handover decision.d99g3227{k) done 2006/09/21 ܥEVivekFGuptaGMember^ Editorial_15`21a5.2b#Replace MIH by MIHF in entire drafttire draft bAnChange the current text with the following: "The MIH_SAP, first introduced in this specification, provides the interface between the MIH Function and the MIH Users. Possible MIH Users include mobile applications, upper-layer mobility protocols, and network selection engines. The introduction of the MIH_SAP is key to the functional delineation of the MIH Function."ncA[The current text can be better explained. "This SAP defines the interface between MIH Function and MIH Users such as an upper layer mobility protocol, or a handover function which might reside at higher layer or a higher layer transport entity as well. The definition of this SAP is required to define the scope and functionality of MIH Function."[d231g2237vThe group feels the original text is better than the suggested remedy. The group also feels that this is comment is of Editorial type and the resolution could be left to the Editor.wRejected 2006/09/21 2006/04/28d83OkHow we can mandate media specific technology? Even though I understand media dependent MIH capability broadcast is a basic mode, this function should be left as optional. mRejectedvHIn section 8.6.1 change "may " to "shall" as specified in the comment. wAccepted-Modified{k) done 2006/09/21 2006/04/28VE ShinkichiFIkedaGMember^Technical, Binding_114`55a8.3.3.1bIDefine it as: '0' for version 1(this draft), other values for future use.c#Value for "Version" is not defined.d737g4138p:0: Not to be used 1: The current version 2 - 15: reserved.vBDefine Version as 1. and Reserve the value 0 for other/future use.wAccepted-Modified{k) done 2006/09/216YEStewartFSkomraGMember^Technical, Binding_28a5.5.5b|Rewrite the section and focus more on how 3GPP2 networks can handover to other non 3GPP2 networks with help of MIHF/802.21. c2.21. c802.21. cclayers*WۅW۪W6WRWYWmWܭW0W݇WݍWݎWW W,WWWWWWWWWkWsWtWWlbtWlead۶WW WWlearnېWlearns۳WleavingWleft-WiW~WleftmostWlegendܵWlegendforfigure19bsapbstnetcismissingܵVlenghtWlength)WAWBWwW|WݵW'WtWuWWWWWWWWW+W9WlWlengthis2octetswhereasietable6saysitis4octetsthVlengthisvariablewhereasietable6saysitis4octetsthVhepworthƒhepworthx&ƒeleanor hepworthƒhepworthQSƒeleanor hepworthƒeleanor hepworthƒhepworthFRƒeleanor hepworthƒhepworthFbƒeleanor hepworthƒhepworth7Yƒeleanor hepworthƒhepworthhTƒeleanorc8basasfollowslVlVlV9Wmkthem|W)WWYWthen\WrWWthererWWWWWWVWYWthereisacommenttoremoveforexamplecomment350VthereisanoverlapofthevaluesalreadyallocatedformihfYVthereforeWthese۴W)W\WWWtheseareadministrativetypepriitivesthatdealwithevent)Vtheseareconsideredasmediaindepedentcommandseachmobil\VthesearenoteventsbutcommandsaswehavedefinedthemupVthey۴WWWWthingsۓWWthink|WWWthis"W#WAW۳WCW|WݓW3WWܸWܺWWWWݓWW+W1W3W3W3W3WܺWWWWݓWW+W1W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W'.bdepending@rdeployment@destination@Zdetailed@fdetails@detected@detection@different(direct@discover@ditto@dotted@each@eitherreplacewitheuqivalentprimitivesthataredefinedi@elsewhere@fencoding@entire@entities@entity@&established@_estimation@event@events@examples@expected@-f@@xpected@-extraneous@ially@-extract@expecially@-extract@examples@expecially@-extract@tract@requiredheretoclarifythepurposeandopera@--scription@examples@expansion@-iption@examples@expansion@-- khatibiƒkhatibi7ƒfarrokh9 khatibiƒfarrokh: khatibiƒkhatibihƒfarrokh; khatibiƒfarrokh< 2khatibiƒ  khatibilcthen7WCWWWWWWlWthereWW?W@WېWۦWDWEWjWܖWWeWWW W2W=W>WtWuW|WWWWWWWWWWWWWWWWWWWWW!W'W<WIWWWWWWWWWWthereare256possibleencodingsforgeneralVtherearenoargumentsforcapabilityofinformationserviceIVtherearenoidvaluesdefinedformihfunctionidsessioniVtherearenovaluesdefinedforstatussincetheexchangeofܖVܖVܖVadagolmiemember]`‚bc'‚cnadagolmiemember^b‚deyA‚enadagolmiemember_d‚fgyH‚gnadagolmiemember`f‚hiHF‚inadagolmiememberah‚j   *r3‚kljv‚lnadagolmiememberbk‚mi~jthenotionofinformationrepositoryiscorrectVtheschemarepresentationisbasicallyincorrectvVtheirWthemWWb pblayerslayers/mihfWlearnېWlearned۶WleastWWWleftWlefthandWW W WW7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7Wxie€xie~R€qiaobing|xie€21425:V#€xie2€qiaobing}xie€shihiroݿohba„ohba'„yoshihiroohba„Pfv$„ohbaf„yoshihiroohba„ohbav„yoshihiroohba„":b$ „ohba"„yoshihiroohba„ohba:„yoshihiroohba„ohbab„yoshihiroohba„ohba„yoshihiroohba„ohba:„yoshihiroohba„31 ݗbc Case 2 description is incorrect.d408g2395wAccepted{k) done 2006/09/21 2006/04/28ݘE YoshihiroFOhbaGMember^Technical, Binding_51`24a 6.3.4.3.1bAChange the Value field from: " The Value field of RADIUS Location-Information attribute is encoded in this field. The encoding format is defined in draft-ietfgeopriv- radius-lo-04.txt. " to: " Location Information is encoded in this field. The encoding format is defined in Table 9. "@A> 33  33>c.Reference to Internet-Draft should be removed.d424g2396wAccepted{k) done 2006/09/21 2006/04/28ݚE YoshihiroFOhbaGMember^ Editorial_59`65a6.3.8.1bChange it to "XML."c"XML.."d464g2417{k) done 2006/09/21 2006/04/28 ݛE YoshihiroFOhbaGMember^Technical, Binding_66`1a7.2.2.1a7.2.2.1a7.2.2.1a7.2.2.1field. "@d329 2006/05/14ESanjeevr?b3Remove ' or even through the Informaiton Service'. cALink_Detected.indication, ... "the detection may be ... even through the Information Service'. Link_Detected.indication is a primivie in MIH_LINK_SAP. We'd better draw a hard line between Event Service and Information Service. Even if Information Service detects some new link, MIH User itself may take the Information Response into consideration. Do not need to mention 'Information Service' at this place. d910g2217wAccepted{k) done 2006/09/21 2006-04-30 WEQiaobingFXieGMember^Technical, Binding_4`43a1.6bA]Add new section(s), probably after current section 8, that details the various classes of 802.21 compliance, including at least details on what capabilities shall be mandatory and optional for each class. --or -- If such compliance class definition is impropoer for 802.21, it must be explained and the above statement be either changed or removed. ]@]@a6.3.9K cthe>W?WWWXW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWWWWWWW W!W"W$W%W&W'W*W+W-W.W7W8W9W;W<W=WVDa6.2.16.2.2Wƃ6.2.3K6.2.4>76.2.56.2.5.1ȃɃʃ˃̃6.3;}6.3.1?@Aǃȃ˃ܵփ׃LMNQݓ@Aۃ6.3.2KZۓʃ̃̓Ѓу#؃كۃ݃ރ߃OPRT݉ݔݕݖtqrःൃඃසฃ܃߃'()*8nn#################################### Ycthisneedtobere-writtenasaproperreferenceVthisprimitiveisdeliveredfrommihfunctiononoldpoato"VthisprimitiveisissuedbyupperstocontrollayerlinksVthisprimitiveisissuedbyupperstodiscoverthestatusofVthisprimitiveisusedastaion'smihisnotalwayscorrectއVthisprimitiveisusedbyamihfunctionontheservingnetw|Vthisprimitiveisusedbyapeermihfunctiontocommunicate%Vthisretrievalmechanismusingpre-definedreportsofferslivVthissectiondoesnotactuallyexplainwhatthisschemaisr VK bcwhichwhichstandardisthiswhyonlyoneieexampleisprovidedi'VwhileWWDAAkWe need a paragraph similar to this. This will give an idea about MIIS. We may need to improve the text. That does not mean we have delete it completely. mRejectedwAccepted{a) awaiting resolution 2006/09/21 2006/04/24CEQiaobingFXieGMember^Technical (was Editorial)_63`24a7.1.2b"Add MIH_Link_SAP to section 7.1.2.c!MIH_Link_SAP is missing in 7.1.2.d486g2279v^Mkae this section consistent with section 5.6.1 and have the same classification for all SAPs.wAccepted{a) awaiting resolution 2006/09/21 2006/04/24ddprovides the capability for obtaining the necessary information for handovers. This includes information about lower layers such as neighbor maps and other link layer parameters as well as information about available higher layer services such as access to internet connectivity, availability of VPN services, etc. The set of different higher layer services provided by the MIIS may constantly evolve. At Pc[The current text does not state how remote communication is performed across peer entities.d222g2247i Vivek GuptakvNot clear if we need to introduce this notion of NET_SAP. This has been brought up before multiple times and rejected.mAccepted-Clarifiedvby comment 178w Superceded 2006/09/21 2006/04/28dgement plane (as the 802.11 instantiation of the MIH_LINK_SAP) and for the L2 transport of MIH messages across the access link prior to the association of the Mobile Node with the Access Point (as part of the 802.11 instantiaB,tion of the L2 portion of the MIH_NET_SAP)."tion and the lower layers of the mobility management plane (as the 802.11 instantiation of the MIH_LINK_SAP) and for the L2 transport of MIH messages across the access link prior to the association of the Mobile Node with the Access Point (as part of the 802.11 instantiaB,tion of the L2 portion of the MIH_NET_SAP)."""JScinW+WAWCWJWZWhWqWvWwWۀWۃWۄWۅWۋWیWېWەWۤW۳W۴WWWW WWWW-W.W1W2W3W5W6W7W8W:W<WGWHWIWPWRWYWZW^W_W`WaWfWiWlWoWpWrWtWuWvWwWxWyWzW{W}W~WW܀W܁W܃W܄W܆W܇W܈W܊W܋W܌WܑWܒWܓWܔWܕWܖWܟWܤWܥWܧWܬWܭWܱWܾWWWWWWW W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W0CbgenericGWIWJWۼWYW2WlWmWuWW2W2WW2W2W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W,bfunction W"W*WLWOWPWQWRWSWTWUWVWWWcWdWlWpWsWېW#W7WZW܅WܫW0WIWݎWWWW W W"W%W'W,W/W2W4W5W8WބWޅWއW2W5WnW|WWWW%WuW|W}W~WWWWWWWWWWWWWohba„ohbaQ„yoshihiroݖohba„yoshihiroݗ*ohba„ohbaC5„yoshihiroݘohba„ohba?i„yoshihiroݙohba„ohbahv„yoshihiroݚohba„ohbatan9 „yoshihiroݛohba„ohbavc„yoshihiroݜohba„ohba Y„yoshihiroݝohba„ohbau„yoshihiroݞohba„ohba„yoshihiroݟohba„ohbaZ„yoshihiroݠohba„ohbay6„2iwolfgang?W@W|WWuWWWW W+WUWVWYWWwolfganggroting?V@V|VVuVVVV V+VUVVVYVVxieW,WܬWOW(WWWWWW W W<WtWWWWWWyoshihirojWwWxWyWzW{W~WWWWWWWWWW:WWyoshihiroohbajVwVxVyVzV{V~VVVVVVVVVV:VVVVVV #kalso-WWWWWWW}WalternativeWalternativelyWalternativelymihprotocolmessagesmaybeencapsulatedusinValwaysWamoreWan"WAWWdWWWWWYWand"W#W۳W۴WW|W|WWWWWWWWWWWsultofadhocdiscussionwehadgroupconsensusthat<VaspectܸWat0WݴWbase-WbasicZWbeZW\WaWjWkWuWWWܶWܺWܻWW݀W-WbemorespecificforinformationservicetoworkandunderstVbecomeݻWbeforeYWzWWbetweenZWjWkWbitsWbootsrappingܺWboth=Wbroadcast/multicastܻWbut0WW=W|WWݻWbyXWwWWWbWܻWcan\WuWܶWcapabilitybWcarefulܹWcaseCWWcasesoWclaimBWclarificationۓWܹWclarifyWclarifyingW&cmn۳W۴W+WLWWWWWWWW W"W<WsWWWWmns:WmobilWmobileWWiWۉWۏWۦWW.W3W4W:WܡWwW{WW"W#W$W/W1WWW8W>W?WWWWWWmobilenodenetworknodethatmaychangeitspointofattachVmobilenodewithmihfunctiongenerallyhasseveraldifferenۉVmobileterminalchangetomobilenodeۏVmobile-ipWmobility"W:WܤWݐWWW"WYW_WޖWWWWWWWWmobilitymanagemententitiesaremerleyshownasapossibleVmobilitymanagementprWWWWWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWL kcThe MIH_Configure.request is used to control the behavior of a set of lower layer links (p90 line 46). The primitive does not contain a parameter defining which interface(s) needs to be updated. d624g2296wAccepted{k) done 2006/09/21lENada, Golmie, Member^ Editorial_92`24bA\Replace "Result of trying to conifer the link" with "Result of trying to configure the link"\@Af  33  33$  33I  33R  33fc7Syntax error in "Result of trying to conifer the link" d628g2297{l) none needed 2006/09/21mENada, Golmie, Member^Technical, Non-binding_93`17b93`17b93`17b N/A Identifier of the link to configureB kactiondWactionsWactualWactuallyVWadgWWaddrWadditionalۓWaddressrWwWxWyWzW{W~WWWWWWaddress/routeWadds۴Wadministrative)WadoptWadvancedWadvertise}WadvisableuWagreeW Wagreethatmoreclarifyingtextsraerequired VagreedWaidWaimingVWair}WalgorithmsuWVWallWWallocatedYWallowWWWWW5_bdefinesAWpW۟WW8WWWdefiningAWdefinitevWWݹWdefinition W#WJWZW۴W۶WW/W3W4W:W`WܬWWWsWWWWWW(W,WjWWWWWWdefinitionofnetworkoperatorinmiddlecolumniscicrcularVVVV"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"Wkhatibi„ khatibi.D„farrokhIx  khatibi„farrokhJ 2khatibi„khatibiv„farrokhK khatibi„khatibia%„farrokhL khatibi„khatibiav„farrokhM khatibi„khatibi5„farrokhN khatibi„khatibiX„farrokhO khatibi„khatibif„ibik697wWrWW7WWYWW7.2.1W8.6W802.11W W802.11eW802.16W802.1dW802.21-W|WWWWvWW802.21isnotmodifyinglsapandcssapinanywayhencetheVaAWW|WݓWOW\WgWsWvWwWxWyWzW{W~WWWWWWWWWWWVWYWWWWWaverysimilarcallflowforamoregenericcaseisshowninVabdWableWabout#WAWWWWaboveWaccessWWaccessibleWaccomplishedvWachieveWWacrossWWacsWWWWWWW<QݭE YoshihiroFOhbaGMember^ Editorial_95`29a 7.4.10.1.3bFix it.c)Replace "Application" with "application".d640g2427{k) done 2006/09/21 2006/04/28 ݲE YoshihiroFOhbaGMember^ Editorial_112`5a8.3b "register"c "rregister"d701g2428{k) done 2006/09/21 2006/04/28 ݵE YoshihiroFOhbaGMember^Technical, Non-binding_113`64a8.3.2.2bChange the Length field to 4.cfIf we adopt 21-06-0522-04-Session_Identifier, the Length field of Session Identifeir TLV should be 4. d726g2409wAccepted{k) done 2006/09/21 2006/04/28ݸE YoshihiroFOhbaGMember^ Editorial_115`60a8.3.3.2a8.3.3.2a8.3.3.2a8.3.3.2e the Length field to 4.cfIf we adopt 21-06-0522-04-Session_Identifier, the Length field of Session Identifeir TLV should be 4. d726g2409wAccepted{k) done 2006/08/28 2006/04/28 ݸE YoshihiroFOhbaGMember^ Editorial_115`60a8.3.3.2ist. Please submit the exact wording changes.X >ctheWW+W0W3W6W@WAWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWe initiator is deep in the network). ijkmnpvw{ 2006/05/146/04/28specify .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 `% 7,valone{WalongWalreadyRW1W|WWWWWWalredayWalso WIWݓW"WCWNWWWWW4W>W?WWWWWalternativelyWalthoughWWalthoughthesubsequentsubsectionsspecifiestlvstobecarValwaysgWamendmentsWWamong3WanlW WݓWWWWW"W'W|WWWWandCWTWZWlWۉWێW۔WەW۳W۴WWWWW)W1W`WܛWܾWWWWW{W݃WݓWWWW"W4W5WVWޏW[W\WuWWWWWWWWWWWWWWWWWWWWW WW"W&W)W2W?WjWlWtW{WWWWWWWWWWWWWWWWWWWannex\WWWWf kwhatۓW|W\WtWWWvWWwhatisapageinthiscontextVwhenW}WwhereWwhich"W۴WWW:WwhileWWWwhileuseofschemaisanoptionrequiredonlyforxml/rdfqVwhole-WWwhyrWwWxWyWzW{W~WWWWWWWWWWwhyitisonlydhcpaddressthereareseveralotherwaysonerVwiderWsvHIssue identified. suggested remedy cannot be applied to a specification.wRejected 2006/09/21!LccontextܾWW>WtWuWWWWW.W/W0W|WcontextualtWuWcontinuesWcontinuityWcontradictoryWcontradictsWcontradoictedWcontributionWWcontroliWkWW5WWW WWWWcontrolledWW>Wconventions>WconveyۼWconveyedWconveying3Wconveyingpossibilitynotcertaintyregardingheadertypesi3Vconveys<Wconweys@WcoordinatetWݸWWcopy&Wcore۽W$W!Wcorrcet}WcorrectWWWWW&W~WWބWޅWއWWcorrectedCWcorrectionۗWۛWcorrectly,WWcorrectnessWcorrespondingۃWۄW+WdW>WWcostHWjWtWuWW9WWWWWWWۊWWWZWWW W+W݂WݏWWKWQWTWfWhWcounterpartWcountriesSW#kwillAWWYWwithۓW)WuWvWWWWWWWwithin|WWwithoutwWxWyWzW{W~WWWWWWWworkWWworkingWwould"W)WWW}WWwouldsuggesttoidentifysomecommonmechanismtoaidincoVwouldsuggesttoidentifysomethinglikethisasanessentia"Vwouldn'tWwwwWxml|WWWxml-basedWxml/rdfwWxWyWzW{W~WWWWWWWWWWWxxxYWyesWWyesitneedsfurtherclarificationabdalsotable7needscaVyouWWWWWWWWWWWWWWWWWWWWWWWWWWWWRcded schema is unknown. @AR 33  RcWccouldZW W+WWWWWW W<W?WWWWWWWWcounterpartWcountries'WbhenceRWܬWhereWfW WWWheterogetWheterogeneous"W?WۙWܤWWtWWWhetrogenousWhexbinary~Whide݃Whidel2sublayerstheyareshownindetailsineachspecific݃Vhigh#W?WܬWhigher#WAWOWPWQWRWTWUWWܤWWWWhigher-layeruWhighlyWhighlyconfusingtoseetheconceptsrepeatedintlvandVhightlightenWhihWWWWWW-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W~ bindicateRWwWݗWOWW WlWindicatesTWUWVWWWYW|WݗWWWWindicationUWVWWWRWUWݍW>WWWW7WWWWWindicationsTWUWVWWWWindicatorWindividualWW'Windividually۳WinfluenceWinfozWBW=WWWWWW{WWinfomrationW%WinfoqueryparametersܕW}WxWzWinfoqueryresponse|WވWވWވWވW|WވWވWވWވWވWވWވWވWވWވWވWވWވWވWވWވWވWވWވWވWވW;B @ 1aK@%† sreemanthula)(†"kenichi@.-†Dtaniuchi0 @ @ @ }bchange#W$W(W)W*W?WAWGWIWLWOWPWQWRWSWTWUWVWWWcWdWeWfWiWlWpWrWsWtWxW۲WۻWWWW,/W7WRWYWjWkWmW|W܂W܅WܑWܒWܔWܖWܤWWWWWWWW+W,W.W0W7W<W>W?WIWRWcWdWeWgWkWzWݑWݒWݔWݕWݘWݚWݜWݵWݾWW(W4W5W8WOWlW5WXWlWmWnWoWtWwWyW|W}WWWWWWWWW)W1W@WAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWWWYW[W\W]W^W_W`WaWbWcWsWWWWWWWWWWWWWWWWWWWWWWWW_'bentityLWUWdWېWۚWۭW,WZWfWܡWW"W%W/W8W2WnW|WWW>WWWWWentriesWentrykWݛWWenumeratedWenvelopeWenvironmentܤWIWWWenvisonedWequipmentWerrorGWIWJWۉWlWmWWespWvWes/cs/is݃WespeciallyUW1Wess?Wessential?W'WWessentiallyWessentiallyanisclientcanaskforcertainclassesofVestablishܡWܡWܡWܡWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWestablishingOWSW_WbWWWmWqW߫W߯WMyoshihiro݆݈݅݇݉݋݌ݍݎݐݑݒݓݔݕݖݗݘݚݛݜݭݲݵݸݹݺݽݾݿʃ>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghiyuanۅ‚562I‚6nadagolmiememberG5‚787‚8nadagolmiememberH7‚9nadagolmiememberI:‚:;? ‚;nadagolmiememberJ:‚<=?‚=nadagolmiememberK<‚>??)‚?nadagolmiememberL>‚@AM9‚AnadagolmiememberM@‚Bu‚CDBB‚DnadagolmiememberNC‚EFV!‚FnadagolmiememberOE‚GHBf‚HnadagolmiememberPG‚IJd‚JnadagolmiememberQI‚KL'‚LnadagolmiememberRKbdifferent3W3W3W3W3W3W3W3WchandoverhandovermoduleisneverdefinedorusedelsewhereAVhandoverneedsabetterdefinitionVhandovermodeeeeeee(.bofofmobileipv6withdhcpv6andVVVVVV5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W‚lmkv‚mnadagolmiememberbl‚npn&‚p3 bthe=W?WWWXWYWZW[WbWcWdWeWlWoWpWrWsWtWvWwWxWyWzW|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWW"W$W%W(W*W,W-W/W1W7W8W9W;W<W>W@WWWkWlWpWrWsWtWuWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!=bfunctionfunctionwhichisoptionaltoimplementVVV5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wderi…peretz+ feder…rajkumar…ajay, rajkumar…rajkumar*…ajay- rajkumar…ajay.  rajkumar…rajkumarJ…ajay/ rajkumar…ajay0 0rajkumar…ajay12  rajkumar…rajkumarS…ajay3 rajkumar…rajkumarY…ajay4NLocdefines4W5WnWWWdefiningWkW>WnWdefinitionۃWۅWۓWۦW۫WWW.W3W4W5WCW`WܛWܬWWwWWWWWWWWW W4WWWWWWWWWdefinitionofinteroperabilityandcompliancemechanismsisܛVܛVܛVܛVܛV b† srinivasf sreemanthula† sreemanthula j † srinivasgh sreemanthula† srinivasi@ sreemanthula† sreemanthula~Y†srinivasjk sreemanthula†pekyewltan†tanpa†pekyewmtan†pekyewn'tan†tan†pekyewotan†kenichip  taniuchi†taniuchi i†kenichiq taniuchi†kenichir 3taniuchi†kenichis taniuchi†kenichit  taniuchi†taniuchif†kenichiu taniuchigbuk/currency/byHWumts WtWW$WWunchangeableWunclear۫W6W6W6W6W6WW6W6WW6W6W6W6W6W6WWCW W^WunchangeableۂWunclear۫W6W6Wiememberiy‚{|N!‚|nadagolmiememberj{‚}~NC‚~nadagolmiememberk}‚K5‚nadagolmiememberl‚nadagolmiemembermd‚c‚nadagolmiemembern‚Q#‚nadagolmiemembero‚_T‚nadagolmiememberp‚nadagolmiememberqh‚nadagolmiememberrh‚x@‚nadagolmiemembers‚lj‚nadagolmiemembertulisesolvera‚ @`'xie("q(qiaobing)'xie)xie*"u*qiaobing*)xie+c,C,xie-+c-VbwhereTWUWVWWWpWW W%W}W~WxWzWWWWW W>WwhereeverCWwhetherPWWWWWwhichGWOWPWQWRWSWTWUWVWWWpWۉWېW#W]WWܕWܟWܡWWWݍWݔWW"W#W$W'W}WlWvWxWzW|WWWWWWWWWWWWW(W*W,W/WWWWWWWWW"W$W'WWW}W}W}WW$W'WWW}W}WHWWݔWWW"W#W$W'WWW}W}W}W}W}W}W}W}W}W}W}W}WWWWWWWWWWbing*)xie+6wBJ Ryc,fC,xie-+c-ohba„ohba„yoshihiroݟohba„ohbaZ„yoshihiroݠohba„ohbay6„,q>csuggestۘW6WWWsuggestrephrasingۘVsuggestedWqW5WWWsuggestedrephrasingofgapsinradiocoverageVsuggestednewlinkidenPWdWsuggestednewpoaidentPWdWsuggestednewpoaidentisnotneededifitispartofsuggestePVdVsuggestion<W<ݛb- Add a new entry in Table 14 "MIH Link Detected Event A new link is detected" - Add a new entry in Table 15 "Link Detected Event A new link is detected"cuIn the MIH_SAM 7.2.2 table 14 and table 15 seems to be missing the Link Detected Event that is described in 7.3.13 d490g2398p*leave mapping to specific link tech as TBDwAccepted{k) done 2006/09/21 2006/04/28Table 14ݜE YoshihiroFOhbaGMember^Technical, Binding_73`52a7.3.9.1b9Adopt suggested change in 21-06-0608-Link_Identifier.doc ccMacMobileNode, LinkIdentifier and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d527g2341p7g2341peplacing currently different parameters in the same parameter list (e.g., MacMobileNode, LinkIdentifier and MacNewPoA in Section 7.3.9.1), we would end up with three identical parameters with same name/description/etc, effectively break the parameter list. Please submit the exact wording changes.<3kon۳WwWxWyWzW{W~WWWWWWWWWWWVWonerWWW~Wonly"W۴WCWrWWWWW}WWoperationsuWoperatorWWoperatorsWoptimize-WoptionWoptional۴WOWWWWWoptionallyWoptionsWorW|WݓWdWuWwWxWyWzW{W|W~WWWWWWWWWW WWorderWorgWorganizationWW cnotclearwhatgranularitymihswitchoccursonwheninvokedVnotclearwhetherthisisanmihprotocolormihfprotocolVnotclearwhylinktypeisincludedinthelinkdetectedpriVnotclearwhymiesiscalledoutspeciallyinthiscase V.pMremoved the 2nd Mobile Node def. and removed the 2nd sentence per comment #63{k) done 2006/09/21/EDavid FFamolari^ Editorial_8`42a3bWChange the definition to: " N-layer - the N-th layer of the layered protocol stack. "cN-layer - A subdivision of the layered protocol architecture, constituted by subsystems of the same rank (N).---is this a roundabout way of saying the Nth layer of the stack. d67g2404{k) done 2006/09/21 0EDavid FFamolari^ Editorial_10`1a4cCRDF (Resource Description Framework) should be added to Section 4.d82g2405{k) done 2006/09/21 1E Famolari FDavid^Technical, Non-binding_7`17a3cIs soft-handover limited to handover between homogeneous access only? In other words is seamless handover is confined to hadnover between heterogeneous access only. These two definitions need to be clarified little bit. d50g240650g240650g240650g2406ickcmbA bA[Remote MIHF returns the necessary information to the NM via the appropriate response frame.[@Af  33.  8  33<  @  33fcvRemote MIHF returns the necessary information via appropriate response frame. Return info to the NM, be more specificd469g2254vA[Remote MIHF returns the necessary information to the MN via the appropriate response frame.[@Af 33. 8 33< @ 33fwAccepted{k) done 2006/09/21 2006/04/28 EPeretzFFeder^Technical, Binding_66`10c\Change MIH Event Register/DeRegister to MIH Event Commands These are commands and not Eventd492g2256wAccepted{k) done 2006/09/21 2006/04/2814EPeretzFFeder^ Editorial_86`64b86`64b86`64bder^Technical, Non-binding_61`48bdeleted. deleted. cananmihcapabilitydiscoverrequestfromtheterminalwouldnVanmncouldbeattachedtodifferentnodesonthenetworkde+VanurlofbasicschemaisstillnotassignedV] cforforbettersentenceflowۚVforitem1.2oftable6thenumberofoperatorsdoesnotnecVforitem7oftable2accordingtothedefintionofthiseveVforno1.2intherepresentationfieldifnetworksofthesaVVVVVVVVHbasinthecommentސVޑVޓVasthesectionisdealingwithl2dataframepacketformatipVaskWasnWaspectsۖWWWWassembleܤWassignedCWxW~WފWoWWassignments/radius-tݔWWassignments/radius-tegieݔVassistWassistance>Wtance݊W݊WGnUbinitiatedRWWWWinitiates#Winitiation܅WinlcudesWinputWinsecure<WinsertWWWWgW(WMWOWݿW1WWWWinsertatendofsentencealthougnetworkconfigurationchanOVinsertatendofsentenceonlywhenprobabilityofaccessingVinsertbeforeorbyassociatinginformationcontainedinitsVinsertcommaafterfirstappearanceofnetworkMVinsertcommaaftermobilityVinsertiprenewalindicatorinsection7.3.17.1page80lineVinsertisbeforecalledVV vchangetheprimitivedefinitionandtheprotocoldefinition@clean@comment`:ݓ )  comment104@commenters@configuration@control@9could@ 8definitionݓdeletethetext@do@doc@ $encapsulated@etc@events@ #first@!forward@from@handover@have@[identifier@1in݃insection7onlyhavedescriptionofevents/primitives@:instances@ intra-technology@6investigate@ is "issues@itLl2@linesܬ!list@locally@ mechanismsە0message@mihnmssapisalredayinmediaindependentcategory@ mn@neednetwork@noremedysuggestedalsosupercededbypreviouscomment252@nosuggestedremedyissueassigned@nosuggestedtextnosuggestedtextcommentassignedforfurtherwork@( d{b27@31@4@M4sip@5.6.2.1@6@7@7.3.1@b7.4.4.1.2@{802@h85@aualinkupeventmayalsocarrynewipaddressrenewalacquis@ya-4@=access@uaccessing@across@-action@?actual@addaddanewentryintable14@addanewsection7.3.1calledlinkeventid@caddanotesayingthathandoverisalsoreferredtoashando@addgetstatusresponseset@addh-aaainsection4@Taddmihlinksaptosection7.1.2@addqueryresourcelistattheendoftheparameterlist@theendoftheparameterlist@ftheparameterlist@0-0000locinfo@W^technicalWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWHbto>WXW[WlWmWnWoWpWrWsWtWvWwWxWyWzW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WW!W$W(W)W,W/W7W8W<W=W>W@WWkWmWpWrWsWuW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#W W W W W W W W W Whandoverdecisionmodule.VtomihfnetworkmihmobilenodeVtooneofthefollowingtypeswVyV cand>W?WWWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWtWvWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWW W!W#W7W8W9W<W?WAWBWDWGWHWJWKWVWWW[W]W^W_WbWcWiWkWlWmWtWzW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWthattheseVand/or:W-bactionۉW6WactionsOWPWQWTWUWVWhWnWactiveAWPWޖW5WactivitiesۉWۉWLW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WWۉW۶WWWWWWWWWDWEWRWSWTWUWVWWWXWYW\W`WbWcWdWkWmW܎WܐWܗWܘWܙWܚWܜWܴWܺWܻWWWWWWWWWWWWWWWWWW'W)WHWbW|W݊W݋W݌WݛWݥWWWWWW2WDWKWLWMWWW[WaWbWcWhWޒWޘWޙWޚWޥWWWWWWWWWWW WW0W1W8W9W:WEWaWbW=ccustomarilyWfWcustomaryۣWWWGWlWcustomaryuseVVlVcustomerWcutrrentWdWdrewordline40mobilipregistrationmightbenowtriggerVVVV2csatisfyCWHWsaved&WsayW5WWsaying/WWsaysrW.WZWW݇WWWWWWWW7WlWWWscanNWmWWWscanschedulingNWscares݃WscenarioݓWWWscenariosrWWWWWDWDWWWWWWZ* bmih=W[W\WaWfWhWnW|WWWWWWWWWWWWWWWWWWWW"W$W7W8W<WIWuW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#WmihcapabilitydiscoverresponseVmihcommandconfirmprimitiveshouldberemovedfromitscur>VmiheventderegisterconfirmresponseVmiheventregisterconfirmresponseVmihgetinfoindicationrequestVmihgetstatusVmihhandoverinitiaterequestVmihinformationrequestrdfdataprefixmihbasicurltobea~V~V~V~V~V~V~V~V~VcgoingۅWaW#WdWWWgong܈WgoodۓW'WWgov/nost/wwwclassic>WgprsWgrammarۺW)WgranularityWgre-WiWgreatwWxWyWzW{W~WWWWWW Wgreater+WlWgroupHWYWIWWgroupsWWWgsfc>WgsmPWgsm/gprsGWIWJWlWmWguarantee Wguidance}WguidelineWgveܬWhWh-aaa݌W!Wh-aaaisnotdefinedintheabbreviationlist݌Vha-W!WiWhadnover1Whand-WiWhandleWWWWhandledWܛWWWWhandles Whandling WWhandoffWWWWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJW a5.8.2܃݃5.8.3+ೃk66.1{6.1.1I᷃6.1.2ݑރ:ḃ6.1.3W6.1.36.2.2V6.1.4ăӃឃ6.1.5ݒ6.1.5.2߃ῃ6.1.6ᾃƒÃ6.1.76.1.8&&&&&&&&&&&&&.76.1.8ŃJ6.2.16.2.2W=?6.2.3K6.2.4y>s6.2.56.2.5.1/:ܴޔޭ޸'MXߋߖɃԃ6.3;}6.3.1?@AǃȃɃ˃ܵܶՃփ׃LMNQݓ@A޽޾޿,-.]^_ߛߜߝكڃۃ6.3.2KZ[\ۑےۓʃ̃̓΃σЃу҃ !"#ܷܻܺ؃كڃۃ܃݃ރ߃OPRSTUVW|݉ݔݕݖtɃiߧ#e{cdependencyۓWWdependentDW WWWVWWdependentonearliercommentonsection7.3.11.1VdependingW+W6WW%WdepictedܔWdeployedܭWdeploymentܭWWW<WdeprecatedWderegister(WMWWWWWWWWderegistrationWWdescribeeWW[WWdescribed+WیW{WݒWݓWݛWݽWWWtWwWxWyWzW{W~WWWWWWWWWWdescribingܟW>Wdescribled:Wdescription0WPW܅WWݗWݾWWW}WWބWޅWwWxWyWzW{W~WWWWWWWWWWWWW=WoWWWWWWdescriptionofrdfdataunderinforquerytypeisnotcorrcet}V}VޅWޅWޅWޅWޅW bnetworknetworkidentifeirshouldbelinktypeݺVnetworkselectionistheprocessbywhichamobilenodeoraܡVnetwork-assisted>Wnetwork-controlled>WWbl3sW3W%WpW~WWlabelWlabeled~Wlac%WlanpWlandscapeWlanguage#WܬWqW}WxWzWlarge WlastBWWlat/lon'WlaterWWWlay<Wlayer#WAWIWLWOWUWVWWWcWdWpWېWەWۣWW/W7WSWTWZWfWiWkWܤWܫWݍWW WW"W$W2W8WpWmWnWWWWWW$W%WpWzWWWWWWWlayerare1Wlayered/WlayermihcWcWcWcW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WcquestionableۀWquickly'WquiteW WquotesWWWquoting:Wr1۴WWr1andr3inetrafceseemtobeinterfacesbetweenmnandnet۴Vr2Wr3۴WWr4WWr5Wradio۽WWWW+WWradiusۓWWradius-nas-port-typeWradius-nas-port-typeisunsuitableforourusesinceitdoesVraexWފWran۽WrandomlyWrangeWhWWWW4WWrank/W/W/W/W/W/W/W9Wrank/W/Wank/W/WFPbnote#WHWW)W|WnotedۖWWnothingށWnotificationOWPWQWRWSWTWUWVWWWޖW5WWWWRWSWTWUWVWWW\WޕWޖW5W5WWRWSWTWUWVWWW\WޕWޖW5W5WWRWSWTWUWVWWW\WޕWޖW5W5WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW[cobtainېWIW<WobtainedېWܬWWtWobtianedܬWobviousQWobviouslyۄWېWoccupiedlWoccupieszW{Woccur^WoccurencesܥWoccursۨW WܟWWWocteswWoctetwWWWlWoctets)WAWBWWWWWWWlWoduWoduWuWuWuWuWuWuWuWuWtskomraYᐃᑃsoohongnsreemanthula[\]_adkᓃᔃᕃᖃᗃᘃᙃᚃᛃsubir #$')ୃஃ௃ఃృಃೃഃൃඃසฃใ຃ໃ༃གྷḃÃŃsubritaisuke:;tanlnᜃtaniuchipqtuvw|}~ހށނރބޅކކކކކކކuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuucclearlyWWWWrWWclearlydefinewhichreferencepointsarenormativeandwhicVcleary{WclientWWWWWWclient'sWWNcabout#W+WKW`WېWWWWWdWtWuWWWWWWWWWW?WkWWWaboveW#WWWW.WpWabstractionܟWabstractionsWacceptableWacceptance݃Waccepted;WWacceptor>Waccess$WۉW۳W۽WWWW1W:W;WܬWܾWWWWWWW"W$W%W*WrWWWWWWWWW!W$W1W5W<W?WtWaccessingWaccomplishWaccordingۅW:WWWaccordingtorfc3753thedefinitionsarequoting:VaccortingWaccountWaccurate+WaccuratelyWachieve"W#W$W8Wachive*WackWWack-bitWack-rsp}W}W}W}W$W$W$W$W$W$W$W$W$W$W$W$W$WV,cexactly݃WWexamineܱWexaminetheusageofthewordtypicallyinthedraftandremܱVexampleeWېW۪W'W-W:WiWݔWNWtWuWWWWWWWWWWWWWWWW WWWWW!W.W9WiWWWWexamplequeriesneedmoredescriptivetextandshouldbeinVexamples`WWWW/WexamplesprovidedlackcontextrequestingsuchinformationwVexceptW WexceptionWexceptionalېWexcerpt>WexcessiveWexchangeܖWWWexchanges>WexchangingWexcludesWWeKbthresholdsGWۉWRW`WlWWWWthroughpW7WW?WWWthroughoutWtidWtifyAWtimeAW]W:WWWtimeintervalWtimelyWtimer&WޖW5WWtimerandreleasethesavedcopyofthepacketthesourcema&VtionAWAWAW5W5W5W5W5W5W5W5W5W5W5W5WIbnotification5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wd|bprimitivespWۉWSWW0W8W>WlWކW>WWWWW7WWWWWbcommonܾWWqWuWcommonlyWcommunicatepW7WW%W|WcommunicatesW1WcommunicatingW7WcommunicationxWۖW܅WW3W W|W<WcommunicationsWcomplementWcompleteWWRW܉WW\WaWWWcompletedWWRWcompletelyYWܓWcompletionjWcomplianceWWcomposedܤWconceptWWconceptsW W WWWWWWWWWWWWWWWWWW> ^binding/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/Wcbe2W5W6W>W?WWWfWgWhWiWkWlWmWnWoWpWtWvWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWW"W$W&W8W<W?WAWBWCWDWEWFWGWHWJWKWLWMWVWYWZW[W]W^W`WaWbWgWhWiWkWmWpWtW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#WWWWWcexpansionܠWWWexpected^W*WexplainەWۖWW4W5WW WjWkWWWexplainthattheremoteflowofeventsandcommandsforfiguVVVVbsplitWWsquareWfWsrcVWssid[Wstack/W7WܫWݎW2W%WsWWWWWWstacksW WstagesWWWWWWCnkitself-WjustwWxWyWzW{W~WWWWWWWWjustdefiningastructureddataasatreeortreesisnotsuwVxVyVzV{V~VVVVVVkeepuWWknowWknowledge\Wl2Wl3WlanguagevWwWxWyWzW{W~WWWWWWlayerWWWlayers\WWWleft"WOWWlessWlevae)WlevelVWlightWlike"W\WuWWW WlimitedwWxWyWzW{W~WWWWWWہWہWہWہWہWہWہWہWہWcparticularwW>WIW|WWWWWW?Wpartly WpartnertWuWpartnerstWuWpartocularZWsWpartsەWWW'WWpartsoffigure30areveryhardtoreadVpassSWWpassed0WWpassingSWpayloadWtWݸWW'WpdsnWpdsn/fa-WiWpduWpeer{W%W>W1W|WWWWpeers>WWWpending WpeopleWperWmWvWWWWperlastmarch06denveracceptedcommentresolutionaddanVperformېW|WW8WperformanceWݍWW8WperformedWWWWWWWW3W3W3W3W3W3Ww^technicalbinding/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/V/Vj+crequestۃWۄWۍWێWQW`WkW܀W܄W܅WܕWWW%W>WCWކWWWWWWWWWWWWWWWWWrequestsourceshouldberesponsesourceۍVrequest/response6WWWWrequestedaWrequesterfWgWhWiWtWuWWrequestingW/Wrequestor>W>W>W>W>W>W>W>W>W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\W\WE bthatthatsWWW8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8Wd‚Q‚R‚Sۡ‚T'‚Uq‚V‚W‚X>‚Yۢ‚Z‚a1‚b‚c(‚dۣ‚e)‚f ‚gۤ‚h*‚i.‚jw‚q‚r‚s‚tۥ‚u3‚v4‚w‚x/‚y,‚z‚+‚‚ۦ‚ۧ‚‚-‚5‚ۨ‚ܟ‚.‚ ‚2‚0‚݋‚݌‚‚‚‚ܠ‚‚‚۩‚‚t‚ܡ‚‚/‚ܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣ^technicalbindingܕVܕVܕVܕVܕVted 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 Ran{barchitecture W<Ware W#WAWLWOWUWpWxWېWەW7WCWTWUWVWWWYWtWxWܾWW(W*W0W1WjW݃WݖWݗWݸWWWWW2WކWފWvWWWWWWWWWWWW WW8WsWuWWWWWWW"W"W"W"W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W߱W&ObestablishedOWRW܋WWestablishingOWSWtWvW_WbWbWRW܋WޕWestablishingOWSW_WbWbW_WbWbW+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W`‚7ۃۍуԃHh܊/9eଃփۃg‚8ۮ0 ‚9(xj\wފǃ 1256=>?WXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ࠃࡃࢃࣃःृঃৃਃ੃ઃૃଃୃஃ௃ఃృಃೃഃൃඃසฃใ຃ໃ༃གྷྃ࿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJsF \c802.21802.3WpWW802.3/ethernetqW802.3adWW802sqWWWWWWWW}cinconsistencyWYWZWinconsistencybetweenfigure12and5.6.1YVinconsistencybetweenfigure12and5.6.2.1mihlinksapisZVpis&V&V&V&Vnksapis&V&Vsistencybetweenfigure12and5.6.2.1mihlinksapis&V&Vp_‚S?@Aǃ:;ܵփLM}@A‚TKȃʃ˃׃؃كNOPQݓۃ‚UZۓ̃̓W?W[W\W]W^W_W`WaWbWcWdWeWjWkWlWmWoWpWrWsWtWuWvWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWWWWW W!W$W&W'W(W*W,W.W/W0W8W<W>W?WVWiWkWlWnWtW|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWbelsewhere۝W)W(W,Wem2WembeddedWtWݸWWemergency1WemoteWemptyWencapsulate WencapsulatedWޏWencodeTWUWVWWWWWencodedݘWހWencodesܕWܕWܕWcodesܕWܕWWހWހWހWހWހWހWހWހWހWހWހWހWPbhandovermodeۋWgWhandovers?WAWQWUW:WݍWWݍWݍWݍWWܴWܴWWuW:WܴWܴWhandovers,W?WAWQWUWuW:WܴWܴW:W:W:W:W{fb802sWWuW802.11?WsWYW[WW WpWtWWWWWW802.11a/b/gW802.16sWNWYW W4W5WtWW8WWW802.2W802.21#WDW$WCWܧWWW[WoWWWWWW<WWW802.3qWWW83W^WSW^W^WSW^W^WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW>cmessagesۃWW"WOWaW W WWWWWWmessagetooWmethodWWWmethodlength1octetisnotsufficientalready7methodsarVmethodology>WmethodsW  cmih=W>W?WZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWnWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W"W$W8W=WIWmWoWqWrWuWvWwWxWyW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#W"W"W"W"W"W"W"W"W"W"WitydiscoverprocedureneedstobedistinguishedVmihcapabilitydiscoverresponsemessageIVmihcapabilitydiscoveryisspecifiedasmaybedonethroughOVcsdomW W>Wsdos"W#W$Wsdu܌WWseamless1WWseamlesshandovercanhappenbetweenhomogeneousinterferfacVsecond݆W*WlWlW* baddedWWWWWWbbeenRWRWSWVWWWWbeforeGWIWJWSWۉWۜWWW#W"W2WlWmWpWWWWWWLWW2W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+WelowGWHW\WjWWWWbesetۉWbest݂Wbetter۾WWWWWW-W[WWbetterunderstandandclarifytheamountofworkneededtoi۾Vbetween W"W'W?WDWZW]WpWqWuWxWۣW5WgW܅WܟWWW WW,W1W2W3W4W5W7W8WpWޞWޠWޥW޽WWWWWWW WWW,W1WbinaryܕWbindWbinding~WbitFWGWHWIWJW2cin=W>W?WWWYWZW[WfWgWhWiWkWsWtWuWvW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWW W!W"W'W.W/W0W1W5W8W9W:W<W=W?WIWNWOWUWVWiWjWkWmWtW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWin802.21alinkgoingdownmihlinkgoingdowntriggerisuۅVinadditiontosufferingfromthesamelackofcontextasabVV.V.V.V.V.V.V.V.V.V.V bandandciviclocationinformationݖVandcoordinatethepayloadthatisembeddedVandlinkhandoverimminentVandresponsebydocumenturlorversionnumberonlyVandroutingconfigurationinformationraVandthedocumentcouldbeV7W7Wn*krb "on-demand"c Missing dashd864{k) done 2006/09/21sEFarrokhFKhatibiGMember^ Editorial_145`3aAnnex A2bReplace "3GPP" with "3GPP2"c Incorrectnessd885{k) done 2006/09/21tEFarrokhFKhatibiGMember^ Editorial_148`22aAnnex B1b"may not like"c Word orderd893{l) none needed 2006/09/21wEFarrokhFKhatibiGMember^ Editorial_8`21a3b,Remove or rename one of the two definitions.c+Duplication of the "Mobile Node" definitiond59g3207{k) done 2006/09/21zEEunahFKimGMember^Technical, Non-binding_62a6.3.9ba6.3.9ba6.3.9ba6.3.9ba6.3.9brd"cImproved phrasingd855{k) done 2006/08/21 rEFarrokhFKhatibiGMember^ Editorial_138`42a8.6.1qEFarrokhFKhatibiGMember^ Editorial_137`20a8.5.3.19b(Replace "further deliver" with "forward"cImproved phrasingd855{k) done 2006/08/21 rEFarrokhFKhatibiGMember^ Editorial_138`42a8.6.1e-kexplainedݓWextensibilityWextraneousWfactWWfeatureWWfigureWWWWWfiguresWWfirstpWfixedWflowpWWWfocusWfollowedWfollowingWYWfor"WCWݓWWwWxWyWzW{W~WWWWWWWWWWWWWWWWWW WUWYWvWWWWformvnoorothersuchmodelwemayhvaemultipleentriesfoVformat|WformatsforwardingVWfragmenting WfromWWWWfunctinalityWfunctinallyWfunctionOW|W}WfunctionalityWfurtherWWgWgeneralWWWgenerateWWWWWLb17ۮWmW18WW19@WܵW~WaWhWWW1999pW1x-evW2WJWۉWەWHWRWSWYW|WܒWܖWzW݃WݗW,W>WpWvW}WށWރW1W6WXWwWxWyWzW|WWWWWWWWWWW7WWWxWWWWWWWWW2accessnetworkspecificinformationV2onesparqlqueryparametersށV2onesparqlqueryresponseparametersރV2rdfdatawVyV2referencepointsVVVVW6W6W6W6W6W6W6W6W6W6W6W]ܕc- Though it has been agreed in the last meeting, the TLVs sent within response is still restricted to on element. This is inconsistent with the request. - These TLVs carries responses and not requests.d670g2265wAccepted{k) done 2006/09/21 2006.03.05Marked ܖEWolfgangFGroetingGMember^Technical, Binding_107`53a 7.4.15.2.2bAFChange Valid Range from N/A to - 0: success - 1: failure - 2: rejectedF@AR 33   33 RcThere are no values defined for status. Since the exchange of this information is not local but remote in nature, it is adviced to define this in standard. d669g2266wAccepted{k) done 2006/08/29 2006.03.05  ܚEWolfgangFGroetingGMember^Technical, Binding_147`8aA.4bAAdd the following in the annex A.4 at the beginning TYPE_HDR_TLV_MIHF_ID 0x00000001 TYPE_HDR_TLV_SESSION_ID 0x00000002 McspecificW$W:WCWaWiWܰWܾWWWWW>WOW>W[WtWuWWWWWWW9WjWrWWWWWWspecificformatforthevalueportionineachtypeofinform9VspecificallyWspecification۩WWܟWW݉WWnWކWWWWWWWWWspecificationoftypeienetworkqosisnotmediaindependenVspecifictaionWspecifiedېW܌WܾWWEWWOWޖW5WWWWWWWWWW5WޖW5W5WW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WybaacombinationofoperatornamespaceandݕVadefineatransactionidthatisuniqueVadouble-headedarrowlabeledsocketapisshouldconnectthe~V0V0V9W9W9W9W9W9W9W9W btexttextsW/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/Wxbenjamin}9bingqiangۍېbingyunۏdas #$')ୃஃ௃ఃృಃೃഃൃඃසฃใ຃ໃ༃གྷḃἃÃŃdavid,-/0eleanorɃʃ˃̓΃σЃ҃Ӄԃփ׃؃كۃ݃ރ߃  eric݃W!W7W}WWsidWsideW$W~WsignalWdWsignaling\W]W^W_W`WaWbWcWdWeWWWsignificant WWWWsimilar(W*WW/W0WWWWWWWsimilartopage58lines1-21lackofcontextunnecessarypa0Vsimilartowhatisstatedin6.3.6.1exampleslackcontextr/VsimilarlykWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW^ FbarearedescribedinthesectionbelowVarenotraejV-W-W-W-W bremovingۼWWWrenameۭWWKWwWW!WrenamethefigurecaptiontoremotecommandserviceflowKVrenamethemessagefromtheremotemihftolocalmihfaseveV3uclinkprimitivecanonlybegeneratedbymihfunctionnotfrocVdVlinkqualityparametertypeencodingisinsufficientandneeJVlinkstatusparametershouldbedescribedhereinmoredetaiݽVlinktransmissioneventsitisnotclearwhyweneedthisfoVlinktypenetworkidentifierparameterisrequiredformihuaVVVlinkupmacaddressnotdefinedin3gpp2usesectorid128biVlinkuprequestandlinkupresponsearenotdefinedintheކVlink-layerWlink/mediaܰWlinkedWlinkidentiferݜWAWBWCWDWEWFWGWHWJWKW[W]W^W`WaWbWlinkidentifierݜWJWZWgWhWlinkparametertype`Wlinkparamterlist_WlinkskWWWWlinktypeWWlinktypeoperatorisnotneededunderapoamultipleoperatoVV"V"V"V"V"V"V  "bthemthemselvessWWWLMcclassificationܰWWWclassifiedWWclauses(W*Wclear$W.WܾWWW W WW!WW5WXWWWWWWWWWWWWWWW W WWWWWWWWWWWclearerWWWWW5W5W5W5W5WJbdetectedSWRWSWTWUWVWWWݛWWW+W+W+W+W+WtionVWXW Wdetermine#W݂Wdetermined WޖWdeterminesW\WdeterminingWdeveloped_WdeviceۜWWܫWܶWdevicetoreconfigureandpresentdatatoupperlayersVdevices_Wdhcp\Wdhcpv6WdiagramۿWܳWW>Wdiagram/textWdiagrams/useܴWdicoveryuWdifferences*WިWWWHW߆WWWdifferent W"W?WAWMWOWPWQWTWUW_WpWuWۙWrWܤWܳWܴWܾWܿWW0WQW݃WWWWPWޅWޞWޠW޽W޿WWWWWWWWWWW WW,W.W>W@W]W_WkWmWnWoWrWsW|W~WߛWߝWߩW߫W߬W߭W߰W߱WߺW߼WWWWWWWWWWWW cshould2WnWoWWWWWWWWWWWWWWWWWWWWWWWWWW W%W&W-WAWBWCWDWEWFWGWHWJWKWLWMWUWVWYWZW[W]W^W`WaWbWgWhWiW~WWWWWWWWWWWWWWWWWWWWWWWshouldhaveanotherblockcalledl3transport~VshouldisarequirementnotappropriatehereVshoulduseadjectivenotnounformsincethereisnosuchtheVshouldn'tWWWWWWW BIcwhirepWwhoWwholeW*WwhoseWwhownWWWWpWwhoWwholeWWWwhoseۊWwhownWWdbinternalWWinternallyWinternetAW1WinteroperabilityWinterpretlWinterpretationWinterval]WޖW5WWintitate8WintoWW*WZW`WqWWWzWXWtWvWWW*W7WWintonetworkaddressinformationjustanaddressVintraWWWWWWWWWWWWWWWWWWWWWWWWWHbpayloadWtWݸWWW|WpduRWWpeerpWxWݎW%W|W|WWWpeer-to-peer>Wpeer1WWpeer2WWpeersxWpendingVW WperhWvWܾWWpercentageWWWWWWWW; 8crNot clear why the "Scope of definition" column is needed, as all reference points are in the scope of IEEE 802.21 d123g2226{k) done 2006/09/21 2006/04/281EEleanorFHepworthGMember^ Editorial_21`61a5.4.3b%Align terminology or add definitions.cwhat is the deifnition of "secure" and "insecure" port - is this the same as controlled and uncontrolled ports in IEEE 802.1X? d155g2228{c) instructions unclear 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_23`39a5.5boChange "(MIH_LINK_SAP)" in line 46 to say "(which is a technology specific instantiation of the MIH_LINK_SAP)" c|The term generic SAP is confusing since in line 47 it then says this "assumed media-specific names and sets of primitives". d183g2229{a) awaiting resolution 2006/09/18 2006/04/28Marked of IEEE 802.21 d123g2226{i) to do 2006/08/27 2006/04/28Marked1 Editorial_114`29+cshow@shows@zsimple@so@xsolution@Qsort@Ispans@specific@tspecifies@standards@statement@subjective@usuch@,suggest@0suggests@qsupported@Yswitch@syntaxerrorinnumberofparametersinlinkparamterlist_Nsyntaxerrorinresourceretentionstatus20@syntaxerrorinresultoftryingtoconiferthelink@Dsyntaxerrorinwhenapredictiveevenexpectedtooccur@4systems@.take@?target@Stechnology@s@.take@?target@Stechnology@echnology@Stechnology@ocis>W?WXWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWtWuWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWW W!W'W+W/W7W8W9W:W;W<W?W@W7C1kisۓWCW|WݓWW-WOW\WgWpWrWsWtWuWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWW:WUWVWYWvWWWWWWWisthisabootsrappingissueifnotthenwhyithastobemeVisthisfortlvonlyisthatisthecaseweshouldsaytlviCVissuewWxWyWzW{W~WWWWWWWissuedWW Lbsectionsection5.6.2.1mihlinksapshouldberemovedentirelyVirely6V6V6V6VW8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W#bindependencemih(Windependent?WAWpWvWW}W|WWWWWindexing۶Windicaiton5W5W5W5W5W5Wdicaiton5W5W5Witon5W5W5Witon5W5WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWing۶WindicateWRWwWWݗWWOWindicatesFWTWUWVWWWXWYWcW|WݗWindicationUWVWWWW9WOWRWUW\WyWݍW>WsWxWޕWWWWsWtWuW߱W߲W߳WWWWindicationsTWUWVWWWXWWrW߰WWindividualۂWܽWSWindividually۳WinfluenceWinfoWOWܗWܘWܙWzWWBWxWinfomrationW%WinfoqueryparameterskWnWܕW}Winfoqueryresponse|WވWbthirdWBWthis W#WAWIWLWOWPWQWRWSWTWUWVWWWcWdWiWxWېWەW۶WWWNWVWYWZWkWoW܄W܅W܆WܓWܕWܡWܣWWWWW0WIW}WݍWݘWWWWWWW W WWWWW"W#W$W%W2W4W5W8WVW}WWހWނWބWޅWއWދWތWޖW5WmWnWxWzWWWWWWWWWWWWWWWWWWWWWW W WsWtW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnW\|bstringHWmWܕW}WހWނWxWzWstringsvWstructure#WZWsWܬWWsWtWvWpWsttausWsubject*WsublayerWsublayers݃WsubmissionWsubmitWsubmittedۋWWsubnet?Wsubscribed7Wsubsection[W:Wsubsectionof6.3.8shouldbedeleted:VsubsectionsWsubsequentݗWWއWsubsequentݗWWއWއWWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWއWW<ca>W?WXWlWmWnWrWsWtWuWvWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWW W!W'W*W/W<W=W?WkWpWqWzW{W|WWWWWWWWWWWWWWWWWWWWWWWWWWW#Waaddanstotowardonline20Vabettertitlefor5.5wouldbemihreferencemodelforacce$V$V$V$V$V$V$VkbscopingWWsdo WsdosWWsduUWRW܌WWseamlessۻWsecondJWۤW4WHW܉WWWsectionWCWpWۄWW;WAWBWRWSWYWhW܁W܂WܕWܛW{W݌WWWWWNWYW\WlWnWvW5WWWXW[W]W^W_W`WbWcWdWeWgWjWkWpWsWuWvWWWWWWWWWWWWWWWW<W=WUWpWvWwWxWyWWWWWWWWWWvWvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW\bshouldVWWWZW۫WWW#WܨWWWWkWݺWWWWWW,W-W.W>WAWBWsWWWWWWWWWWWWWWWW%W(W,W4W:W<WjWlWmWsW~WWWWWWWWWWWshouldbeaddedtotable5anddefinedmVshouldbeincludedintable3sincetheyfallundermihevenVshouldbekeyandsalientpointsܨVshouldbereplacedbyasinglestackwiththeentitystackVVshouldbereplacedbyvalueorprovidesupportingtextwhyiVVVVVVVVbn-layer/W5WܟWn-layerthen-thlayerofthelayeredprotocolstack/Vn-th/Wn-user5WܟWn/aGWkWmWܖWlWwWyWWWn0WnameۉWېWkWmW܁W܂W܄WzWݕW~W6WWWW8WuWWWWWWnametype܄VnametypevalidrangedescriptionVVnametypevalidrangedescriptionVnamesWnamespaceݕWnasWnasiscommonlycalledasnetworkaccessserverVnas-port-typeݔWtWWnativeVWWWnature Wnbr-advNWnearbyWnecessaryAWVWۓW2WWWW<WWWWWWWWWWWWWWWWWWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWbitem۪W܍W#W0WWWitemsەWitmeWitswWWܡWܤW(W,W0WW W>WW|W}WWWWW(W,W0WW W!W+W>W7W7WWܤW(W,W0WW W!W+W>W7W7W7W7WWܤW(W,W0WW W!W+W>W7W7WWܤW(W,W0WW W!W+W>W7W7WWܤW(W,W0WW W!W+W>W7W7WcbelowGWWWWWqW$WbeneficialWbenefitWWbetter$WۚWۨWۮWWW=WW4W5WdW?WpWWW=WWbetterwording=Vbetween"WDWKW۴WW W$W-W1W:WHWRWܟWWWiW݉W W4W5W>W2W>W?WYWZW[WWWW WWWW W'WiWWWWWWWWWWWWbetwenWW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2Wbor?WWWXrWtWvWxWzW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWW"W(W,W.W1W9W>WjW{WWWWWWWWWWWWW#WWWWWWWaBbaddqueryresourcelistattheendoftheparameterlist܎Vistattheendoftheparameterlist܎V܎Vaddqueryresourcelistattheendoftheparameterlist܎V܎Vaddqueryresourcelistattheendoftheparameterlist܎V܎Vourcelistattheendoftheparameterlist܎V܎Voftheparameterlist܎V܎Vaddqueryresourcelistattheendoftheparameterlist܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V?bactualwWWacuallyWad>WadaptationWWWaddWWCWDWۉW۶WWWWWDWEWRWSWTWUWVWWWYW`WhWkWmW܎WܚWWWWWWWW'W)WHWbW}W݋W݌WݛWWWW2WLWMW[WaWޒWWW[WrWvWWWWWWWWWWWWWWWWWWWWWWWWWW8W>WIWtWWWWWWWWWWWWWWWWWWWWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbhandingPWTWhandle WhandledWhandoff)WWhandoff/handoverWhandover W"W#W?WOWPWRWVWWWfWpWvWۉWۋWەWۻWW#WRWfW܀W܅W܉WܤW)WݍWW"W#W.WAWYW6W\WaW|WWWWWW8W>W|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWqbnecessary.W.W.W.W.W.WrZbdeployment}WWderegisterۉWWWWWWWderegistrationWWderivedHWdesciptor'Wdescribe[WW*WpWdescribedsWۃWۄWݓWWWLWMW[WWuWWWdescribedintable33aVdescribesvWdescribing5WܟWWdescribingroamingaspectsonin5.3.2beforethetermsareVdescription?WpWtWېWNWRWSWTWUWVWWWYWkWmW܄W܅WWWWWހWނW1W6WWWWWWWW8WWWWWdescriptionsWdescriptiveWdescriptonWdescriptorW'WdesctiptionހWނWdesignatedlWlWWSWdesctiptionހWނWdesignatedlWlWriptorWSWdesctiptionހWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނW member256=>?WXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ࠃࡃࢃࣃःृঃৃਃ੃ઃૃଃ҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghimn~ဃ၃ႃჃᄃ>,`‚Eۋەۙi܍փ1‚FaܫܭM‚GP߃2]ށY`ᓃṃ‚H`҃7‚ILgۓۣۨۼ57Gܟ.ݐݔ~࿃‚JU Z܎΃ݓ݃/mn‚Q۹ܱ.jഃ7:‚Rۅ۫#ृః#b‚SQ/Croyஃໃ׃ဃ‚TKۯpWw ᎃƒ‚Uۉ,уO\u8888888888888888888888888888888888888888888888888888888888888888888888888888888888888u-ibaccessingۖW۶WHWWWWaccmpanied(W,WaccordanceފWaccordingۉWۋWYWzWW7WWaccordinglyWWaccoridingly1WaccountedOWaccurateܰW+WachievexW"W#W$WWack-rsp}Wacknowledge܌Wacknowledged܌WacquisitionݍWacronym@W@Wacronym@W@WB:centriesWWentriesintable-7arenotclearandneedfurtherdescriptioVentry܉WWWWWWWWentry2linkeventderegisterhasbeendefinedasaneventeVentry2linkeventregisterhasbeendefinedasaneventeveVentry2miheventregisterhasbeendefinedasaneventevenVentry23miheventregisterandmiheventderegisterincorreVentry3miheventderegisterhasbeendefinedasaneventevVenumerateۄWenvironmentWenvisageWenvisonedWequipW*cit>WXWjWkWtWuWvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWWWWW W!W7W<W?WPWQWRWSWTWdWeWfWiWlWoWtWWWWWWWWWWWWWWWWWWWWitdoesn'tmakesensetomanditorilysupportxmlandtlvVitisdifficulttoenvisageascenariowheresipissupporteVitisentirelyunclearhowprotocolextensibilityishandledVitisimportanttoclarifywhichentitieswillgeneratetheZVZVZVZVZVmcreceivesۉW0W>WtWuWWreceivingۅW WWreception܌W"W$WrecipientfWlWrecipient'sWrecommendatin<WrecommendationsWrecoommend<WredWredundancyۙWWredundantgWWrefeernceWreferܧWWWWWnWWreferto802.21asieee802.21consistentlyinthedraftܧVreferenceW$W۽WWDWEWWWAW݃WݕWݖWݘWWYWpWqWXWWWWWWWWW!W&W/W<WWreference1isnotcorrectalsoreferencenumbersaremissinVreferencenumberismissingforallthereferencesintheliVreferencenumberisneededforeachreferencepVpV pblistlistatableoflinktypessupportedby802.21VlistedWWlisting'WlistsW0W0W2 bremove?WXW\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWqWuW{W}W~WWWWWWWWWWWWWWWWWWWWW W!W.W/W1W5W6W<WUWVWXWdWeWfWpWrWtW{WᔃWWWWWWWWWWW#Wremove2bitsfromthe14bitidaddexplanatorymaterialtoVremove2sparqlqueryparametersand4zerooroneextendedVremove2sparqlqueryresponse3urlresponseand4zeroorVremove5.8.3+Vremove6.3.4.1.2^Vremove7.4.8gVremovealittle6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V<bfront2WfullvWfully*WDW[W3Waboutfront2WfullbWfully'W*WDWhWhWt2WfullbWfully'W*WDWhWhWWWWWWWWWWWWWWWWWWWWWWP cpleaseWnWWpleaserefertothe21-06-0601-00-0000poaipaddressconfigunVpleaserefertothe21-06-0602-00-0000poacapabilityprefixVpluralWcWdWpluralformVcVdVpoaWW#WܾWW+WWWWW"W#W$W%W*WdWtWuWWWWWWWWWWWW-WnWzWWWWWpoadatarateVpoa-address~WpoastWuWpoint-WIW2WW<WiWWpointerWpoints:WܨWWWWWpolicyܡWWݎWpolicyengineisnottheonlyupperlayersݎVpolicyenginetypeentityshouldbechangedtopolicyengineVpoorlyZWportWWW7cround Wroundabout/WrouteWrouter:W+W"W$W%WޏWWrouters:WrowWrrc$WrregisterrWWݲrtt W WWWrules WWWWrun WrxlevncellGWIWJWlWmWskWWWWWWWsafe WsaidxWsalientܨWsamݛWsame+WېW W.W/W:WIWZW܄W܅WܠWWWWWBW6WWWWWWWW.W9W{WWWWW#WW6WW6W6WjW6W6WWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIW2cfunctionsYW|W WWfunctions/primitivesܰWfurther@W"W$WWWWfurthermoreWWfutureWWcWfutureWW;cmihlinkparametersreportindicationcanbegeneratedwhen5Vmihlinksapismissingin7.1.2CVmihmediaindependenthandoverܠVmihnetworkaddressinformationrequestandresponseprimitiVhmediaindependenthandoverܠVܠVmihnetworkaddressinformationrequestandresponseprimitijVjVetworkaddressinformationrequestandresponseprimitijVjVjVjVetworkaddressinformationrequestandresponseprimitijVjV5V5V5V5V5V5V5V5V5V5V5V T܋cA> 334  337 33> "PSDN/FA" should read "PDSN/FA". - PSDXA, should be GRE be in the flow? - Acronym for GRE needs to be defined in Section 4. - Is this an example of "Network Initiated Hand Over" ? - Line 55. the circle point left to "MIP binding to HA" should be shifted to the left. - Line 56. Does the AP get Link Tear Down or Handover complete indications before it is disassociated? d872g2399vcNot all issues have remedies. Assigned on Issue List. Change: - "PSDN/FA" should read "PDSN/FA". wAccepted-Modified 2006/08/13 Figure 30 0  c 6.3.4.3.6bA These capabilities need to be specified clearly for different network types under consideration. Also it needs to be made clear if properties such as Security and QoS are on a per PoA basis or are common for a specific access network managed by a particular operator. c>cimproperimproperrerencetointernetdraft(V,VWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW clayerlayered/W/W/W/W/WW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wgmathieuopqrmatsumoto:;member2W3W4W5W6W7W8W:W;W<WAWBWCWDWEWGWHWIWNWPWQWRWSWTWUWVWWWYWZW[W]W^W_W`WaWfWgWhWiWjWkWlWmWoWpWrWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎WWWWWWWWWWWWWWWWWWWWWWWchere+W?W@WiWsWvW`W WݽWWW*W>WfWgWhWiWWWWW WmWWherewegiveaproposalforaddingaparameterinthemihhaVheterogeneous"W1WIWܤWݐWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWccommon2WWWcommunicateW%W|WWcommunicated WcommunicatesWcommunicatingWcommunicationەW3W W*W>WWcommunicationsWcomplete-W܉WW\W`WaWeWWWiWWWWWWWWcompletedWcompletelyYWܰWcompleteness)Wcompletenessconcisenessgrammar)Vcompletion*WcomplexityjWcomplianceܛWWWWWcomplicatesWcomponentsWcomposed:WܤWݐWcomposedofmultiplemediatypesitisthehandoverdecisionݐVcomprehendedWcompressedۿWcomputationaljWconcatenation W WconceivableWconceptWconceptsW WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWg{bhandoverhandovermoduleshouldbereplacedwithnetworkselectorAVhandover/switchingWWhandoverackۋWۋWۋW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W Xcsamesameascommentonfigure18theinformationflowshouldBVsampleWksomething"W~WspaceYWspec"WWspecific"WOW|WWWW:W}WWWspecificallyݓWspecification۴WpWWW~WspecificationsWspecified-WWstaWstandardWstandardizedWstartpWstateVWstaticWstep"WstructuredwWxWyWzW{W~WWWWWWstructuresWsuccess"Wsuch#WrWWWW~WWsufficientwWxWyWzW{W~WWWWWWsuggest"WWsuggestedWWsuggestionWsuggestions/recommen"WsupercededwWoWWWrWWsupercededby577Vsupercededby695Vsupercededby697wVrVVsupercededbycomment394oVsupportWWW}WWsupportedwWxWyWzW{W~WWWWWWWWsupportsWWWWW>3 cnot>W?WXWYWZWfWgWhWiWjWkWnWoWqWtWuWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWWWWWW W+W3W9W;W<W@WPWQWRWSWTWXW_WcWdWeWfWjWkWoWtW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWW"W"W"W"W"W"W"W"W"Wledoutspeciallyinthiscase Vburl|W}W~WހWށWނWރWwWxWyWzW~WWWWWurlsWuseUWfWۘWۜW۞W۰W۳W۽WWRWSWTWUWVWWW"W3WݎWW WVW|WWWWWWWWWWW-W<WkWWWuseaasinothersimilarcasesintable۰Vuseatvariousinsteadofother"VuseinbeforemobilenodealsosuggestusingawordconsisteۜVusemninplaceofmobilenode۞Vnode۞V۞Ve۞V۞Venode۞V۞Vmcinformation?WfWgWhWiWjWoWrWsWtWuWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W"W-W/W8W9W:W<W?WIWsWtWWWWWWWWWWinformationintable11isnotdetailedenoughtosupportimVinformationserviceclassificationisnotconsistentwiththVVVVVMcwiredWWWwishWwithۉW۩W۽WWWW#W.W3WYWhWrWܒWܔWܕW WWW(W*WݜWݭWWWWWW WW"W#W$W%W'W*W,W/WYWlW6WjWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWW%W=W?WAWBWCWDWEWFWGWHWJWKW[W]W^W`WaWbWgWhWpWrWvWwWxWyW{W|WWWWWWWWWWWWWWWW#WWWCWCWCWCWLWWCWCW8W8W8W8W,ceachۄWCWzW{WWWWpW1W|WWWW!W9WtWeachmobilenodeshouldbeawarethatthepeerentityhasth1VearlierpWvWxWWearlyܫWeasilywWxWyWzW{W~WWWWWWWܫWlyܫWܫWX8bmihfpWxWWoWܚWܥWzWݸWWW"W$WއW|WWWWWWWWWW1W7WVWqW|WWWWWWWmihf/802.21YWmihoܠWmiisAWlW۳W}WWtW|WWWmiisprovidestheabilitytoaccessthisinformationaboutaVmilliseconds]WWmimeހWނWminimal=WminimizeVWminimizedWWminimum&WWWWzWminuteHWmipWmissingWWmlmeWW3W3W3W3W3W3W3W3W3W3WQbtheyWWAW7W݃WWW<WWWWWWWWW7WW݂W݃WWWWWW-WAWW7WW݂W݃WWWW_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_Wbintent܅W6WWW)WintentionallyWinter?WܤWWinter-media*WinteractpW"W$Winteraction݃WWinterestIWinterestingWinterface*WiWW0W2W4W5W8WޖW5WWWWW%WuWWWWWinterfaces"W*W,W!W1W2WWintermediateUWUW-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-WabilityWinterpretlWinterpretationWinterval\W]WޖWintitate|WintoWW!W*WZW_W`WbWqWWW=WWWWyWzWSWޜWޝWޟWިWWWWW W WWW<W=W?WHWzW{W}W߆WWYMbdefiedTWݕWdefiedindraft-ietf-geoprivraݕVdefiitevWbpolicyOWPWvWەW#WܡWWݎW>WportsWportedAWportionWWpos,WW9W WW W/WpositionTWUWVWWWWWpossibilities Wpossibility۳WpossiblewWYW=WWW4WWWpossiblyܡW)WW<WpotentialOWPWWpotentiallyWWWWWWWWWWWWWWWWWWWWWWWWWWWWhepworthɃʃ˃̓΃σЃ҃Ӄԃփ׃؃كۃ݃ރ߃  hiranohuoikedaVᎃjiangۍېkeating᪃khatibi!"#$&'()*+,-./013456789<=>?@AEGHIKLMNOPQRT^abcdefgijklmnpqrstw !"#$%&'()*+,-./0123456, & € 5Z[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ࠃࡃࢃࣃःृঃৃਃ੃ઃૃଃୃஃ௃ఃృಃೃഃൃඃසฃใ຃ໃ༃གྷྃ࿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRS Kbtheytheymatchanagreedschemathisdoesn'tmeanyouhavetoVV9WEqcorDWGWIWJWiWwWېWW-W.W3W:WCW[W܄WܡWܤWܫWܬWWWW+W3W}WݐWWWWW W"W$W%W/W>WAWIWOWޖW6WlWmWtWuWwWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW W"W*W9W<WiWjWmWsWWWWWWWWWWWW!W!W!W!W!W!W!WWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbW}brepositoryWWWrepresent݃WrepresentationAWWWWWݔWݕWWWW8WWWWWWWW  baddadd3gpp2after3gppHVadd3gpp2hrpdcs0024-aandcs0063-ainreferences'Vaddafigureflowdiagramforsection8.6.1.1thatisthecoVaddalinkidparametertoallmihprimitivesVaddamoredetailedinformativesectionVckeyیWܨWW{W#WkeysalientpointsmissingandܨVkindsۉWknowۅWۉWېW6WmW܄WOWWknowledgewWxWyWzW{W~WWWWWWknown܋Wl݆WWl-shaped,Wl2W܌WܭW3WWW WWWl3rWW+W3WWW W%WpW~WWlabelWlabeledWlac%WlackWWWW.W/W0WWlanguageܬWwWxWyWzW{W~WWWWWWlarge W WWlargelyxWlastqWsWܕWWWWWWWlatencies Wlatter.WWWWWWW,cimplementationsCWHWimplementedtWvWimplementorWimplicationPWWimplicitWimplicitlyWWimpliedWWW1W5WimpliedlimitationofcapabilityassumedsuboptimalsolutionVimpliedlimitationofcapabilityinassumingthatmiiscanoV1V5VimplieswWۓW*W,W|WWW W}WimplyiW WOW*WtW}WimplyingWimportantWZW'W[WWWWWimpossibleWimproperiWQW\W]W^W_W`WaWbWcWdWeWfWgWhWiWWWW(W,WWWW W WYWYWYWYWYW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!WYcofWWcess Points that can be of different technology. Therefore, It is possible to have a Vertical handover within an Access Network. It is also possible for an interface to change Access Points of the same type but located in different Access Network@A   33  33  33n  33  33  33  33D  33_  33  33  33(  ^  33ijkmnpvw{ 2006/05/14s "horizontal handover" and "vertical handover" here. Terms "intra-technology handover" and "inter-technology handover" are well-known and sufficient already. @A  33ijkmnpvw{ 2006/05/146/04/24ded "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new erviO cthis=W>W?W[W]W^W_W`WbWcWdWeWnWsWtWuWvW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWW W8W<W?WUWiWkWoWpWrWsWtW|W}WWWWWWWWWWWWWWWWWWWWWWWWthis802.21standardܣVthiscommandissentbycurrentmihfentitytotargetmihfeVthisinformationtypicallyoriginatesatdifferentlayersofsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVsVbdatabase۳W۶WWWWdatatype~WdayHWdbYWdcd8WdcnLWMWWdealingWpWdecision W#W?WvWwWWfWܤW.WWdeemedWW.W.WܴW.W.WWWWWWWWWWWWWWWWWWWWWW3fbininanetworkmodel,VincaseoflocalcommandsmessagestypicallypropagatefromݎVincaseofmobileipv4agentrouteradvertisementޏVingeneralhandoversmaybeinitiatedeitherbythemobilenVinscopeofdefinitionsectionspecifywhichreferencepointVinsomecasesintra-roamingpage15line41section5.2Vq#blistAWPWZWېWSWTWUWVWWWhWkWmWyWzW{W~W܎WW@W[WtWWދWތWsWtW|WWWWWWWWWWWWWW@WWWWWWWWWW0W0W0W0WtWWދWތWޕW0W0WWWWWWWWablist@literal@local@low@macnewaccessrouter@Xmakethefollowingchangeto@makes@umanner@maximum@maymbit/s@means@(media-dependent@merged@ method/mode@%middle@kmihlZ=Bmihlinkdetectedeventanewlinkisdetected@*mihreferencemodelforaccessnetworkstechnologies@Xmihf@mn@mobility@module@most@must@n-layer@necessaryneed@qnetwork@Fnetwork-layer@network-side@nm@ork-assisted@network-side@nm@next@@network-side@next@xt@ssisted@next@ssisted@Lcbybyr1r2orr3overanyaccessnetworkandtwomihnetworkeVVV8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W&1breferDWEWWreference$W۴WW`WWW݃WlWWWWWW(W,W<WreferencecouldbemadetostaticschemaeintheisqueryVreferencedW(W,WVVcfunctionalitygW:W\W]W^W_W`WaWbWcWdWeWWWWWfunctionality/capabiܛWܛWpabiܛWܛWnality/capabiܛWܛWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWHcuppers݇WWWWurlqWWWWurlofsparqlinthereferenceisoldandshouldassuggesteqVScbothܠWWfWgWhWiWtWWWW WWWbothhavethesameexpansionܠVbothstaticanddynamicdatacomponentscanreadilybeVbound:WboundaryWboxWboxes-WiWbracketsWfWWbraodcastWbreakۮWbreakdownsentenceforbetterreadabilityaftercommaۮVbreakoutWbriefWbroadcastWWOWWWWWbroadcast/multicastWbroadcasting}Wbroadcasts}WbroadenWbroadenthestatementtouseofnetworkresourcescurrentfoVVVWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻWܻW bthisthiscommandissentbycurrenttheservingmihfentitytotVthiscouldbeduetouserormobilenodemobilitystatechanIVthisfieldisintentionallykeptreservedwhennotusedallVthisfigureshouldbeeithermodifiedorremovedbecauseitVVޗV9W9W9W9W9W9W9W9W9W9W9W9W9W9WXgblowېW6WlowerAWpW6WiWkWܫW1WݎW,W2W4W5WW7WWWlower-layer*WlsۓWlsapWWlte Wm4W2WmacNW WpWWWmac/phy WmachineWmacmobilenodegWhWWmacmobilenodemacaddressn/amacaddressofmobilenodeV4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4VmbbeginningۧWܚW(W*WWbehalfcWiWއWnWbehavioriWkW8WWbehaviorsWbehaviourWWbeingOWbelongWbelongsrWbelowGWHWjWWWWWbesetۉWbest<Wbetter-WWWWWWWW.WbetterunderstandandclarifytheamountofworkneededtoiVbetween W"W?WDWZWpWqWxWۣW5WgW܅WܟW W,W2W4W5W8WpW2W[WsW|WWWWWWWbi6WbinaryܕWbinduWbinding~WbitGWIWJWۉW)WTWUWVWWW|W|W|W|W|W|W|W|WWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJW/boncelWWoneWW?WpWۦWVWzW{W܁WwW݃WݎWWW W'WIWWށWރWބWޅWދWތWwWyWWWWWWWoneofthestacksVonepersistenturlofthisschemashildbeassignedVWWWWWWWWWWbas@casinthecomment@8associated@attributes@_basis@%bebecause@been@mbeginning@bit1bler@brackets@byޖbyte@called@carried@certain@ change@%}changeendofsentencetotoeffectseamlesshandoveracross@5changeifapplicablethenewsapsshallberecommendedasam@Tchangeotherieeegroupstosomeieeestandards@changepointofattachmentstopointsofattachmentorpoa's@?changeradiotointerface@mchangetextto@changethetextto@changethevaluefieldfrom@changevalidrangefromn/ato@changed@clarification@clarifytext@Xclassification@gon@gadeavailab@Xecurityinformationismadeavailab@X{lLbareaWWWpWaren'tWarrayۉWarrivesWWpWaren'tWW(obdirect,W WdirectionzW7WWdirectlyAWWW"W$Wdisconnect6W6W6W6W6W6W6W6W ~care=W>WYW\WaWsWtWuWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW W!W/W>WIW_WcWkWmWWWWWWWWWWWWWWWWWWWWWWWWWarecommandserviceandnoteventservice(Varelinksynchronouseventsapplicableforl2handoversonlyVaremorefailurecodesneededtoindicatewhyaparticularsVVVVVVVVV blinklinkcapabilitydiscoverrequestېVlinkcommandindicationrequestVlinkcommandsoriginateVlinkdetectedeventanewlinkisdetectedݛVlinkeventderegisterconfirmresponseV6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WGbtablesWtailPWtakeOWPWQWTWUWVWtakenHWhWtargetW"W$W%WW>W|WWtaylored۳WtcpOWtcp/ipWtearWWWWWWWred۳WtcpOWtcp/ipWtearWWW%Wtaylored۳WtcpOWtcp/ipWtearWW/ipWtearWW%Wtaylored۳WtcpOWtcp/ipWW$W%Wtaylored۳WtcpOWtcp/ipWW۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W۳W6*canalyzetWݸWanalyzing'WssignedanalyzetWݸWanalyzing'W'WtillnotassignedމVanalyzetWݸWanalyzing'W'WtillnotassignedމVanalyzetWݸWanalyzing'W'W%cservices+WW>WnWWWW<W?WkWserving:W"W#W*WWW|WsessionݒWݵWWWWWW\WWWsessioniddoesnotmakesenseVsessionidentifierismissing\VsessionidentifierneedstobedescribedݒVsessionisnotdefinedanywherethussessioniddoesnotmakVsessionsWsetGWIWۄWTWUWVWWWiWkW|WWWWlWmWWWWWlWWWWWW3W3WWܻWWWEWFWGWHWHWWiWkW|WܻWWWEWFWGWHWHWHWHWHWHW:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:Wboptions,WWWorWW W#W?WDWVWhWiWlWxWۙW۶WWWWWW#W3WTWUWVWWW܁WܡWܤWܫWܾWWW W3W9WIWPWwWWWWWWWW W W"W$W%W-W8WIWnW}WށWރWކWއWޖW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WWWWWWWWWWWWWWWWWWWWWWWWW(cpupdate{W݃WupdatedEW{Wupdates۴WupdtaeܾWupdtaedܾWuseۓW۽W܁Wuselinkstatusparametersresponse܁VusedWݓWVWuserܥW݃Wusers݃WvaluesۓWversionܾWW݃WVWvertical:Wvertical/horizontal;WvisioW2WvivekۓW۴W;WܰWܾW{W݃W2Wvivekthenotesrefertocontribution21-06-0612-03-0000the݃Vvivekthisisavisiofigurewhichisembeddedinframemaker2VvsܥWwaitܵWܾW@Wwaitforresolutionon319ܵV@VwantۓW۽WܾWwas{Wway;WweۓWܾW{W݃WݜWwellۓWܰW{Wwhen)WݜWwhenreplacingcurrentlydifferentparametersinthesamepaݜVwhereWW݃Wwhereisthelastsentenceofsecondbulletdoesitreferto݃V݃V݃V݃V݃V݃VV݃VV݃V>  ]  TTs  )ct  )czUsbtheymusteitherbemergedintooneoroneofthemberemove@third@thisthismessageisusedbymihfunctiontoretrievetheinforma@thisparameterspecifiesthelistofcommandsthatmaybeca@thisprimitiveisgeneratedbymihfunctionwhenitneedsto@thisprimitiveisusedbymihfunctiontoqueryanddiscover@ethisprimitiveisusedbymihfunctiontoqueryanddiscover@e/<bcanother@byte@destination@differences@6elements@Uenough@for@implementations@yimprovement@just@linkparametertypedefinitionsisinsufficientandneedsto@mihreportshouldbeinfoqueryresponsesinceinsection8.5.@Wnot@overload@repeat@show@text@thelastlineunderthevaluecolumnneedstobefixedthee@thelengthdoesnotmatchthetlvrepresentationofsection@vthewordingislooseandlargelyrepeatingwhathasbeensai@readydefinedinthefixedheaderpa@.tionidisalreadydefinedinthefixedheaderpa@.at@show@text@'cinstantiationsWWWinsteadWܥW݆WYWW-WWWWinsteadofprefixthepoasubnetinformationtlvshouldcont-VinsufficientGWIWJWlWmWrW}WinsureTWUWVWWWWintelligence:WintentWWintentoffigure24unclearVintentofmiddlesentenceisunclearandpossiblymisleadingVintentioniWintentionallyWinterܤWinter-bsWinter-essWinter-media*Winter-operabilityWWinter-poaWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW``‚'wR^ԃp9n‚(۱1mzތ຃Fᇃ‚)۪ۤܔ*؃8Ndƃ‚*ۭ۟ݕ-Aස̓W|‚1?#tq‚4iqxۥ3އ߃%ሃ᫃‚5CV:lwNݘݾ_d‚6Og2ELLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL'''''''''''''''''''''''''''' cupper4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4WbsOWPWQWRWSWTWUWVWWWfW&WހWނWWW[W$Ws0001&Ws0004-dۡWs0024&Ws0024-a'Ws0063-a'WsalientܨW'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'W'WQciteWiWpWvWwWۄWۅWۉWۋWېWۓW۪WWW'W-W.W:WZW|W܄WܕWܖWܤWܱWWWW WWWW!W+W0WaW݅W݆W݇WݍWݐWWWWWWW W*WOWdWlWnWޖW6W6W6W6W6W6W6W6W6W6W6W6W6W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WWWWWWWWcor6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W4 cset3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W^4Fc127}WlW128W+W13>W138W147WݛWlWWWWWW14-15W15WݛWlWWWW1500W16WkWW W8W17یWW18یWWWWBWW7W19ܵWW1stvW1xev-do&W2WSWiWsW۴W۽WAWBWCWݗW>W>WXW|WWWlWWWWWWWW2pagenumbers0-6oftocshouldnotrepeatthemaintextV2.2W2.3tWuWW2.4W2.5۪W۪W۪W۪W۪W۪W۪W۪W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!WS^technical>W?WWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWbflowKWzWBWW7WWWWWflows)WWWflushUWfocusYWWfollowedW@Wfollowing*WvWwWxWەWW3WHWRWSWTWUWVWWWmWܚWܬWWW W2WIWފWtWwWxWyWzW|WWWWWWW8W>WWWWWfollows WJWېWCWYWܤW)W0WlWoWWWWWWWW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W#QBcsentWܕW%WޖWWsentencesWۚWۥWۮWW WW3W5WQWiW6W9W@WMW^W݆WݐWWWWWWWWWފWދWތWWW*WpWWsentencesayingaspecificinformationrequest/responseprimVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVbmaximumWWzWmay W"W#WAWGWOWPWQWRWSWTWUWVWWWdWfWiWsWۉWېW۫W۳W۶WWWW#W,W3WCWrWyWzW{W~WWܫWWIWQWtWݍWݎWWWW W W"W#W$W%W&W/WOWWދWތWlWnWoWtW|WWWWWWWWWW"W1W>W}WWWWWWWWWތW3W3WW3W3WތWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKW bmaymaybeVmaynotliketVmayshouldbechangedtoshouldorthereasonwhytheuniqueVmaycauseۉWۉWۉWLWW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W1calternativeSWWWalternatives۳Walthough݃W9WWalthoughvalidthisdiagramlookstoobusythisisexactlyt݃ValtituderesolutionWalwaysWܰWއWWWlWambiguityW*Wambiguityofwhetheraphrasepertainstothewholesentence*VambiguitysuccinctnessallowthecasethatmihisnotsupporVamendWamendedWamendmens>WamendmentۅWamendmentskWamendsWamendsmihcapabilitydiscoverymessagebyaddingnetworkidVammendmentsWscoverymessagebyaddingnetworkidۊVammendmentsWWtworkidۊVammendmentsWWWWEjhowever"WWi,WidWWWWidentifierWidentifiersYWidsWWWWieܾWWWtWiesܾWif"WuWWWzWWWimplementations"W"W"W"W"W"W"W"W"W"W"W"W@cinformationKWZWeWiWۨW۳W۶WWWWCWHWIWNWjW܄WܖWܟWܡWܤWܬWܭWWWzW}WݐWWWWWWWWWW"W#W$W%W'W-WBWdW1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*Wcof>WWW\W]W^W_W`WaWbWcWdWeWfWgWhWiWlWmWoWqWrWtWuWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWW W!W%W'W*W-W.W0W1W4W5W9W:W<W=W@WIWPWQWRWSWTWXW_WcWdWeWfWiWlWoWsWtWzW|W~WWWWWWWWWWWWWWWWWWcbyte@capabilities@(change@changed@classification@clearly@Lclients@comma@commit@common@conceptual@configure@confusion@consistency@contents@context@could@!coverage@cross-reference@=customarily@@d01@define@Ndefines@-definitions@Ldeifnition@delivered@dependency@Edescriptions@eaunderinforquerytypeisnotcorrcet@descriptions@eions@eotcorrcet@}descriptions@eisnotcorrcet@}descriptions@e\d‚1ۜ‚2s‚3‚4‚5"‚6۝‚7۞‚8#‚9$‚:݅‚A۟‚Bܛ‚C‚D‚EW‚F‚G۠‚H݆‚I&‚Jpߣ‚Xƃ5fߤ‚Yǃ6gߥ‚Zȃ7hߦ‚aɃiߧ‚bʃjߨ‚c˃kߩ‚d̃lߪ‚e̓m߫‚f΃n߬‚gσo߭‚hЃp߮‚iуq߯‚j҃r߰‚qӃs߱‚rԃt߲‚sՃu߳ +memberƒÃăƃǃȃʃʃʃ`‚AZ8_ܓܛʃӃ݉ݎL{΃Xfቃᗃ‚BNܣ(-kʃ܃Ƀ‚Ck׃4P‚D@܅AId"|ގi܍փ%1‚FɃaܫܭM‚G%.4Pу߃12;]^ށޣެ޲΃!CLRn߁ߊߐ‚H`҃7`ޙ׃9w‚ILgےۓۣۨۼ57=Gܟڃ.ݐݔ~ʃj‚JHMUۂ Z܎ƃ΃ݓ݃/ƃ˃Ӄ5fks‚QB۹ܱy݀./`‚R|ۅ۫݃Bȃ#‚SQXm(/Cܦ r3σo‚TKNjۯp TޚɃ̃؃ :ilx‚U0ۉ,уOޮNߌ)buserspW7W܊W*W0WWWWWWuses۝WTWUWVWWWWWusingxWۗWۜWWHWTWUWVWWWWWtW|WWWWutilised}Wutilize"WWWutmostgW&Wv-aaa!WvalidېWTWUWVWWWYWkWmWܖWW6WrWWWWWW8WWWvalidrangeWvalueJWfWۉWHWwW|W܂WWݔWݗWݘWހWނWޅW1WoWtWwWyW~WWWWWWWWW+W.W9W;W@WlWzWWWW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W,cif>W?WlWmWtWvWWWWWWWWWWWWWWWWWWW WWWWWW8WPWQWRWSWTW_WcWdWeWfWlWWWWWWifcomment9isacceptedtomodifythedefinitionsofhorizo;Vifthehandoveroperationissuccessfulthemihfinserving*VifthemnrequestsdetailedinformationonaperiodicbasisVifthesentencefromtherecipient'sperspectivetheseeventVifthetransactionidistobeuniqueitisimportanttocleVifthetypeienetworktypeisapprovedthenomustbeupdatVVVVmkcregistrationVWWkW|WWWWWWregularޖWrejectWWWWWWgularޖWޖWkWregularޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖW[vhandoverRWەW۫W1W"W*WގW\WW?WWWWhandoversQWW>WWhappens{W\WharmonizeZW4Wharmonized=WhasZWWW|WWWWWWW2WtW{WWlyWimportantWin۪W۳W۴W۵W۷WWRWWWܗWܬWWWWWW2W݃WWinsection7onlyhavedescriptionofevents/primitivesWVinsection8havespecificvaluesWVindependentWBWinformation۳WWܬW;Winitiated۫WintegerWinterface0Winterfaces۴WBWinvestigate;Wip۵Wis۪WWWW@WܗWWW W2W;W݀WݳWissueuWWW W WWWissue34 VitێW۵WWWW W;Wit's۵WWit'suncleraiftherequest/responseprimitiveneedstobemVjustWkeep"W[Wknow۵WV~member "#$()*+?@ACDGIJKLOPQRSTUVWZ^`cdefghilpqrstvwxۀۓ۔ەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫ۮۯ۰۱۲۳۴۶۹ۺۻۼ۽ۿۿۿۿۿۿۿۿۿۿtensibilityܸWextensibleoWextraneousWWaneousWWWWW/05/14h 3GPP2 standards references. As a minimum, suggest adding C.S0001~0006, C.S0024, S.R0087, X.P0028-100 and X.P0028-200.cMissing references from 3GPP2d38g2275 2006/05/140024, S.R0087, X.P0028-100 and X.P0028-200.cMissing references from 3GPP2d38g2275 2006/05/14rial${aWWWIWRW@WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#Waawaitingresolution$V@VAVCVKVpVsVvVۼVVNV[VܵVVVVIVRV@VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV#Vre effective handover decision making before the mobile node actually attaches to any particular network. "d161g2412v$Commenter to provide suggested text.e node actually attaches to any particular network. "d161g2412v$Commenter to provide suggested text.sted text.berbreplacelinkbynetworksincethisisnetworkselectionܡVreplacelinkcommandindicationwithlinkcommandrequestV25}EPeretzFFeder_138`58bAThe MIH Function in the network may advertise its MIH capability over the backbone network to the neighboring candidates by broadcasting MIH_Capability_Discover.response message. Figure 29 shows the on demand MIH capability discovery procedure.@A>  33A  y  33>cABThe MIH Function in the network may advertise its MIH capability to the neighbors by broadcasting MIH_Capability_Discover.response message. Figure 29 shows the on demand MIH capability discovery procedure. This text implies MIHF broadcasts MIH capability over the backbone. Clarify to imply is is not over the air messageBd867g2270i Ronny KimjWNeed to be discussed with contribution "21-06-0611-00-0000-MIH protocol section update"IH protocol section update"on update"dover and to query the available link resource of the candidate network Add context transfer NOۚ`23-24a1.2bY"... the creation therein of a new entity... " to " ... a new entity created therein ..."cFor better sentence flowd15{k) done 2006/09/21MarkedۛESanjeevFAthalyeGMember^Technical (was Editorial)_3`53a1.2bReplace "both" with "either"cSemantics correctiond18v9Change as follows...."....which may be wireless or wired"wAccepted-Modified{k) done 2006/08/29ۜESanjeevFAthalyeGMember^ Editorial_3`59a1.2b}Use "in" before "mobile node" Also suggest using a word consistently, "terminal", "mobile node", "mobile device", but not allc Consistencyd20{k) done 2006/08/29۝ESanjeevFAthalyeGMember^ Editorial_3`41-45a1.2bTFor consistency with uses elsewhere "mobility management" is spelled without a dash.c  33_ 33} >cA'CurrentLinkAction' values in MIH_Handover_Commit.request/response do not match the TLV field values in section 8.4.2.13. I think it would be more consistent if they have the same values. Therefore, I suggest 'currentLinkAction' values go with the 'Link Action' values in section 8.4.2.13. In addtion, 'HandoverStatus' valuse can be taken from the values defined in section 8.4.2.17 , or vice versa.d647g2220p supercededwAccepted{l) none needed 2006/09/21 2006/04/30=EXiaoyuFLiuGMember^ Editorial_62`12a6.3.9bQReplace the MIH_Get_Info.response (line 20) with MIH_Get_Info.confirm (line 12). line 12).  _bfeemanthula^Technical, Binding_76`5a7.3.11.1b9Remove: MACNewPoA MACOldAccessRouter MACNewAccessRouter cWhy does LInk going down provide information about new PoA, old AR and new AR? Does it mean the signal corresponding to new PoA is better?d538g2246iJin LeejKeep the new PoA information kIn case an mobile node has the information of the MACNewPoA through periodic scanning or information service, link going down can carry the MACNewPoA information so current PoA can take an appropriate action in advance.mAccepted-Modifiedvj Remove MACOldAccessRouter MACNewAccessRouter Add if available to the word optional in table for new PoA.ation of the MACNewPoA through periodic scanning or information service, link going down can carry the MACNewPoA information so current PoA can take an appropriate action in advance.mAccepted-Modifiedvj Remove MACOldAccessRouter MACNewAccessRouter Add if available to the word optional in table for new PoA.26c@y|v@Identified as an issue. Need to understand what is the context. wRejected 2006/09/21 2006/04/28date network. This is used to prepare the new link resource for impending handover, and to query the available link resource of the candidate network and to transfer pertinent context from serving MIHF to target MIHF. MIH_Handover_Prepare.request ( SourceIdentifier, DestinationIdentifier, CurrentLinkIdentifier, QueryResourceList, Context informationList, )@A  33  33  33   O  33    33cA This primitive is used by a MIH function on the serving network to communicate with its peer MIH function on the candidate network. This is used to prepare the new link resource for impending handover and to query the available link resource of the candidate network Add context transfer d644g2260v wDeferred 2006/09/19qvadoptݒWWfWWWWWWnWWadoptremedyfrom21-06-0752-01-0000-lVadoptremedyinin21-06-0698-01-0000ipconfigurationmethonVadoptsuggestedchange1in21-06-0522-06-sessioidentifierݒVadopttextfrom21-06-0721-00-0000-iVadopttextfrom21-06-0722-00-0000-iVadopttextincontribution21-06-0765-00-0000-idocfVadoptthecontribution21-06-0749-00-0000-i47-link-idVadopttheresolutionin21-06-0723-00-0000-iVadopted WadvertisementޏWaffect۔Wafter3WWagent"WޏWaggregates*WagreeݓWagreedWaheadێWaimedWaimingVWalWWWalgorithmWalgorithmsVWalistWallCW-WaWWWWWWWWWWallmanWallowWWallowsW{W݃WݓWWWWWWW"W4W5W6W7WKWSWVW`WiWannexWW,^technicalbindingVVVVVV w"jAZ"...belongs to upper layer mobility management.." Which upper layers handle this? For heterogeneous hnadovers across networks, this is a very complex issue and even if we define this, other SDOs may or may not agree to use this. However not sure if any specific "upper layer" in current stacks on different implementations actually covers this.ZkA;Would suggest to identify something like this as an essential step in handover which can increase handover success rate. However any specific details (primitives, parameters etc.) pertaining to this can be identified as informative only and left as informative suggestions/recommendations in the spec for reference.;mQuestionv3Drop the reservation part, but keep the query part.wAccepted-Modified{k) done 2006/09/21 2006/04/24#EQiaobingFXieGMember^ Editorial_22`2a5.4.3ba5.4.3b identified as informative only and left as informative suggestions/recommendations in the spec for reference. . vuse۳W3WݓWVW]WnW\WfWWW W>WWuseexistingdefinitionsfromitu-torotherreferenceswher>Vuselinktype]Vuseourowntablein802.21draftanddontrefertotheradi Vuseradiusnas-porttypeforspecifyinglinktypeJVusedW4W5WjWW WWUWjWWWWWuseful\WqWWWWusefuleWusefulnessWuserQWRWSWTW݃WWWWusersWWusingWWWWutilize۳WvWvague\WWvalidWvalueVWvaluesۓWWWܾWWWW WnWWvariableWmationservercan;VwebHWwell0WۉW WRW2W݊WݓWSWwgWwhat0WۆWۈWW{W݀WSWwhatarethebenefitsoftheseparametersshouldtheyreallySVwhathappenstomihhandoverprepare0Vwhen۳WDW{WݓWwhereܗW@d{EPeretzFFeder^Technical, Binding_62`11a Figure 22bpRemove MIH_Get_Info.confirm as with or w/o it, the MIH_Get_Info.response is the real confirmation to the requestcvThe MIH_Get_Info.confirm is adding no value. Same can be done with a timer. The key is the remote MIH_Get_Info.responed478g2255iMathieu Peressej?Replace the last MIH_Get_Info.response by a .confirm primitive.vnFigure 22 has been updated as per comment 473 and contribution 21-06-0642-02-0000-Information_service_flow.pptw Superceded 2006/09/21 2006/04/28|EPeretzFFeder^Technical, Binding_97`19b7`19btwork over others.mRejectedwRejected 2006/08/21 2006/04/28{ajThe minimum data rate may provide value in certain cases. For example if the miminum supported rate is a higher value when compared to other networks, then clients may prefer this network over others.mRejectedwRejected 2006/08/21 2006/04/28{ 2006/04/28{{{{fCWc^To insure interoperability, the IEEE 802.21 must define how to transmit the set of Event IDs. d510g2276v[In section 7 only have description of events/primitives. In section 8 have specific values.wAccepted{k) done 2006/09/21YENada, Golmie, Member^Technical, Binding_72`14bAThere are two possible remedies for this: I - completely define all parameters according to each specifications, such as 802.11, 802.16, 3GPP, etc. For example: 0: data rate in Mbit/s 1: Signal strength in dB 2: Frame loss rate (no units) 3:... II- define a generic container for the type as follows: a- In the "Type" column add: "Parameter type" b- In the Valid Range section add: "0-255" c- Change the Description to: Indicates the parameter type to be configured as defined by each speciB fication . cc corresponding to reserved event IDs must be set to 0.  the brief descriptions on 4 primitives.d501g2216 2006/05/14 2006/04/2816yvrelationshipsWrelevantWremedies-WvWremedyWIWWWWWWWWWW)WnWWWWWWWWWWWWWhWۅHWqWܛWdremove7.4.8gVremovefigureentirelyandenhancethissectionforotherl2qVremovereferencetothewebpagehttpwwwjhalldemoncouk/HVremovetablehVremovethissectionܛVreplaceW1WWWreplacemaybewithisVreplaceperformanceofaccessnetworkswithconfigurationanVreplacewithvalidmihfidentifierVreplacingއWreportedQWrepresentWWrepresentasintegerVrepresentationWWWSWrepresented0WrequestjWkWlWmWnWoWۂWۆW۔W_Wrequest/responseWrequestparametersۆWrequiredۈW۔WەWW_WSWrescindedRWreservation"WreservedWresolutionfW>Wes\ cAFigure 30 in Annex A-1, is not updated with the primitives defined in the last version of the draft: i. In step 7, there is a MIH_Switch.Request, but a MIH_Switch.Response is missing ii. In step 8, Link_Up is used as REQUEST/RESPONSE, but in section 7 of the draft this primitive is defined as an INDICATION primitive iii. In step 14, the use of MIH_Handover_Complete is not consistent with the definition in the draft. The use in the Annex is local, but in the draft it is defined as MIHF(NeBwtwork) <> MIHF(Network). iv. In step 15, a Link_Teardown.Request is used. This primitive is not defined in the draft. ed874g2221v@Accept contribution 21-06-0775-00-0000-Issue61 (Text and figure)wAccepted 2006/09/21 2006/04/30F 30cdÃXpÃXÃX{ÃXÃYnÃY 2ÃY0CÃY@DÃYPÃY`ÃYpCÃYÃYNÃYPÃZݛÃZ lÃZ0ÃZ@ÃZPÃZ`\ÃZpfÃZÃZÃZSÃakÃa Ãa0RÃa@LÃaPQÃa`TÃapIÃaUÃaÃaVÃbWÃb Ãb0Ãb@aÃbPÃb`ÃbpÃb_ÃbYÃbÃclÃc ZÃc0Ãc@nÃcPbÃc`GÃcpÃcݜÃc[ÃcÃdÃd OÃd0Ãd@AÃdPPÃd`ۅÃdpÃdBÃddÃd]ÃeQÃe CÃe0^Ãe@Ãe@Ãe@; :v21-06-0690-00-0000-iW21-06-0691-02-0000-3۽WEWYW21-06-0692-00-0000-mW21-06-0695-02-0000-nCW21-06-0695-02-0000-nsectionsformihprimitivesCV21-06-0697-01-0000-pCW21-06-0697-01-0000-pflowCV21-06-0698-01-0000nW21-06-0703-00-0000-c W21-06-0705-00-0000-lDW21-06-0708-00-0000W21-06-0711-00-0000-iZW21-06-0712-00-0000-iZW21-06-0716-00-0000-rW21-06-0716-00-0000-rmodeltextavailableaddsclarificationV21-06-0721-00-0000-iW21-06-0722-00-0000-iW21-06-0723-00-0000-iW21-06-0724-00-0000-i W21-06-0725-00-0000-iW21-06-0726-01-0000-i3W21-06-0728-01-0000-sW21-06-0729-00-0000-l>W21-06-0731-01-00-000WvgdÃpݵÃÃ۔ÃÃà Ã0Ã@ÃP'Ã`ܑÃpÃVÃ;Ã}Ãܒà Ã0Ã@WÃPܓÃ`XÃptÃÃݸÃ3Ãà uÃ0Ã@ÃPÃ`ÃpܔÃ(ÃaÃhÃà vÃ0Ã@ÃPiÃ`Ã`Ã`Ã`Ã`Ã`Ã`Ã`Ã`Ã`{ }bA 33;  E N 33  33   33Q  33[ 33\ d 33h  33u 33w  33   33  # - 335    33B this InfoQueryType is specified, InfoQueryParameters Response carries either the URL of the extended schema the query originator wants to obtain or a null string when the URL of the extended schema is unknown an extended schema. @xtended schema is unknown an extended schema. @d schema the query originator wants to obtain or a null string when the URL of the extended schema is unknown an extended schema. @420 2006/05/141zEKenichiPjneedvWgWWWWWW}WWneedtobediscussedwithcontribution21-06-0611-00-0000-m}Vneedtodecidehowtohandle7.2.1mediadependentsapsfirsVneedtomodifywhole8.6VneededWnetworkܾWvWWWW=WzWWnetworks"WWvWzWneverWnewdWWYWnewdiagramandtextprovidedin21-06-0612-01-0000-rnetworVnoWnorWnot"WZW,WvWށWuWWWWWWWnotejWnotionWnumber=WobjectiveWofWWWܾW,WvWgWjWWWWWWWWWWokWon"WjWWWoneWoneWoneWoneWoneWoneWoneWoneWoneWoneWoneiqiaobingxieV,VܬVOV(VVVVVV V V<VtVVVVVVronnyNWOWfWgWhWiW|WWWW}WWWWWWWWWW W/14 5 cAThe rules on handling duplicate transactions are not clear. Specifically, it is not clear whether an entity invoking a transaction has any mechanism within the protocol for ensuring that the transaction is invoked exactly once or not at all. The rules for filtering duplicate transactions seem to operate only within a simple time window and to be optional to implement at the receiver, and are presumably allowed for efficiency rather than protocol correctness. d715g2298vM21-06-0675-03-0000-LB-issues-srini with an additional statement from Michael.wAccepted-Modified 2006/09/21 2006/04/28d - v3ەW۴W)WށWރWuWW3nothingiscarriedށV3securitymechanismsەV3urlresponseoneextendedschemaurlparameterރV30\WqWWWW|WW32W3268W33W339tWuWvWWWWWWW/W0W34WW345W346WW348W350W352WW360W361W.W@W369W37WWW3789W3809W384WW394oW396W3gppW4ەW)WށWރW4zerooroneextendedschemaurlparametersށV4.2W40W[W413WW415W419W42-W424,W44846W460W W462W473WWW2W{WWW474W475W477W480rW482WWWWW483WW492WW493W494W495]W^W_W`WaWbWcWdWeWWWWWW,  ijinleewVdVVVoVrVkimW8WNWWW>WBWOWfWgWhWiW|WWWWWWW}WWWWWWWWleewWdWWWoWrWmathieuW0WݍW,WXWWWWWW=WqW{WWWmathieuperesseV0VݍV,VXVVVVVV=VqV{VVVohbajWwWxWyWzW{W~WWWWWWWWWW:WWperesseW0WݍW,WXWWWWWW=WqW{WWWqiaobingW,WܬWOW(WWWWWW W W<WtWWWWWWWWWWWWWWUWUWUWUWUWUWUWUWVVV+V,VܬVronny<WuWNWWWW+WOWPWQWjW7WT=۲bChange "visiting" to "visited"cConsistency of termsd138{k) done 2006/09/21 ۳ESanjeevFAthalyeGMember^Technical, Binding_18`22-26a5.3.2bSoften the clause by saying "may use MIIS information. Allow the access to MIIS to be a part of provisioning under service provider's control. Allow for possibility of local database individually taylored and maitained by client.cAssuming that MN "relies" on access to MIIS is too strong. More viable alternatives may exist in which MN learns relevant information and maintains own database. Also, assuming that MIIS access is "periodic" is problematic: what period?d140i Vivek GuptakVery good points. The MIIS can be locally placed on the client and this possibility needs to be comprehended and enabled throughout in the draft.mAcceptedvAcceptedv`27a5.3.1b-Model after similar clause on page 17 line 38c8Break down sentence for better readability, after comma.d119 2006/05/16ۯESanjeeveevl7^{kaWdWkWlWnWpWqWtWuWvWwW|W}W~WWހWށWނWރWބWޅWއWވWފWދWތWލWގWޏWސWޑWޒWޓWޖW1W2W5W=W>W?WkdoneVVVVV V"V(V)V*V+VDVGVIVJVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVLVember^Technical, Binding_128`24a8.4.2.24b%Change "4: Extended Schema Content"c!Value 4 description is incorrect.nk Status Parameter should be described here in more details as specifed in Section 7.4.5.2.4d809g2371v&Refer to Section 7.4.5.2.4 for detailswAccepted 2006/08/03 2006/04/28ݾE YoshihiroFOhbaGMember^Technical, Binding_128`24a8.4.2.24b%Change "4: Extended Schema Content"c!Value 4 description is incorrect. TTbAUse of a bitmap model to encode the list of events that are supported by the Link Layer. There are currently 9 events, so using 32 bits will allow enough bits to add new or vendor based events. In the Valid Range, replace "Set of valid link events" with "4 octets representing the list of events" In the Description, add the following: The encoding uses a bitmap where the bit position represents the event ID. A bit set to 1 indicates that the Link Layer supports the event. For example, ifBz bit #0 is set to 1, The Link Layer supports Link Detected. Bits corresponding to reserved event IDs must be set to 0. hc^To insure interoperability, the IEEE 802.21 must define how to transmit the set of Event IDs. d505g2272wAccepted{k) done 2006/09/21UENada, Golmie, Member^Technical, Binding_69`50b69`50b Event IDs. The IEEE 802.21 must define the list of Event IDs in order to support interoperability between different Link Layers. d502g2270AEcVd560g2299vas per comment 555.wAccepted-Modified{k) done 2006/09/21 2006/04/24MarkedWEQiaobingFXieGMember^Technical, Binding_81`9a7.3.17.3bAChange the text to: MIH Function normally passes this link notification to the MIH User(s) which has registered for this notification in an "MIH Link Handover Complete" event. Upon reception of this event, an upper layer (e.g., transport) may stop any handover adaptation that it has engaged to cope with the just completed native link layer handover/switching and resume normal data transfer. This event may also be used as an indication that a re-verification of the IP parameter should be cB onsidered.@AR 33  33  )c  RcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d563g2300vas per comment 555wAccepted-Modified{k) done 2006/08/29 2006/04/24   cAIt is not clear whether the scope of the protocol functions includes mechanisms for handling large messages (i.e. which are too large to fit in a single L2 or L3 datagram). For example, it is not clear whether the MIHF is responsible for fragmenting to a single datagram or whether the underlying transport is supposed to do this, how the frame format handles concatenation, what algorithms should be used for retransmission and reassembly (including the handling of partly reassembled messagesB3), how the maximum fragment size is established. !d680g2288iWolfgang Grtingj7agreed: Fragmentation is handled by transport protocolskQtrasport protocols like TCP or 802.11 MAC have their own methods for fragmenting.v Fragmentation needs to be handled by transport layer. Add a few lines in draft to that effect. 21-06-0703-00-0000-Control Message Fragmentation (802.16 case) is ongoing work. wAccepted 2006/09/21 2006/04/28dg9.GMember^ Editorial_9`38a3b%Change "the occurs" to "that occurs".cTypographical errord79{k) done 2006/09/21 /EFarrokhFKhatibiGMember^ Editorial_14`26a5.1.6b/Page 14 line 26: "set up", instead of "setup".cNoun vs. verb.d96{k) done 2006/09/21 0EFarrokhFKhatibiGMember^Technical, Binding_15`27a5.2bChange the first sentences of item (b) as follows: "MIH Function provides services to its users. The service primitives exposed by this interface are based on the technology specific protocol entities of the different access networks."cAThe interfaces (e.g. MIH_SAP) exposed by MIHF are not technology-independent. E.g., the QoS parameters passed by the MIHF to its users are unchanged from those that it receives from the link layers. As a result, MIHF users have to be aware of the link layer technology parameters. d102iMathieu PeressejSame comment as comment #17.mment #17.mment #17. different access networks."cMjclearlyZW,WWWcleraWclientszWcombinationvWcommandsWcomment@W0WjW|WWWWW+W=WqWcommentsXWWcommunicate,WcommunicationWWWcomparedzWcomplex"WcomplexityjWcomputationaljWconditionWconfigurationWconfirm{WWconjunction|W|W|W|WnditionWconfigurationWWWWWgWcomplex"WconditionWconfigurationWWigurationWWWWWonWWionWWationWWionWWWWWWgurationWWationWWWWލ^Technical, Binding_122`51a8.4.2.2bA4:SIP 5-7: Reserved@A* 33 *c Reserved bit should be assigned.d790g2441p>- added "4-7: Reserved.", SIP is removed by a previous commentwAccepted{k) done 2006/09/21 ގEKenichiFTaniuchi^Technical, Binding_126`33a8.4.2.18bA0:@A  c$0: is misplaced in the Value columm.d803g2442vUSprecify Abort Reason from section 7.4.10.2.2 0: Abort Handover 1: Accept handover wAccepted-Modified{k) done 2006/09/21 ޏEKenichiFTaniuchi^Technical, Binding_137`56a8.5.3.20bAIn case of Mobile IPv4, Agent Router Advertisement is encapsulated and in case of Mobile IPv6, Router Advertisement is encapsulated.@AR 33   % 33RRRA4:SIP 5-7: Reserved@@^| ܟbcAService Primitive - Conceptual abstraction describing the information transfer the occurs between N-user and N-layer in the provision of a service. The abstraction resides in the exclusive specification of the service provided and not in the means by which the service is provided@A> 33O  33R 33>d78g3246{k) done 2006/09/21 ܠEVivekFGuptaGMember^ Editorial_11`1a4b Delete MIHOcAdMIH Media Independent Handover MIHO Media Independent Handover both have the same expansion. d@A> 33"  33E 33>d88g3247{k) done 2006/09/21 ܡEVivekFGuptaGMember^ Editorial_14`7a5.1.5ba5.1.5ba5.1.5bܕ@ܔܕ@ܕ@bisނWބWޅW 33!  * 5 33     33  *  5 S UU|    UU    UU,  2 UU    UUz   UU. B N UU 33l  33s    33  N 33   ! 33paragraph. Ditto on line 20 and possibly elsewhere.c"Completeness; conciseness; Grammard54g2292 2006/05/14 2006/04/24 *EFarrokhFKhatibiGMember^ Editorial_8`18a3er^ Editorial_8`18a3m 3GPP2d38g2275 2006/05/14rial:4vEPeretzFFeder^Technical, Binding_22`60ia-dependent interface with the transport facilities available on the local node, supporting the exchange of MIH information and messages with remote MIH Function instances. In an IEEE 802 network, the MIH_NET_SAP typically maps onto (i) the link-layer transport SAP that is specific of that network and (ii) the interface to higher-layer transport facilities that is common to all link-layer technologies. In a 3G cellular network, the MIH_NET_SAP only Bmaps onto the common interface to higher-layer transport facilities. Such interface to higher-layer transport facilities consists of the basic socket APIs (bind(), connect(), sendmsg() and others) that are described in IETF RFC 3493.c%Introduce text explaining MIH_NET-SAPd185g2234wDeferredAssigned to Ajay's team 2006/09/20 2006/04/28MarkedvEPeretzFFeder^Technical, Binding_22`603`565656d93 2006/04/287lvsee413Vsee687pVsee687issue30qVsee704V Vseealso709rttshouldbeprovidedbytransportifneededm Vseecomment413VseemsqWWWseemsusefultokeepthenumberofoperatorsseparatefromtqVsegmentsWegmentsWWparatefromtqVsegmentsWW^ Editorial_44`54a6.3.2bc"may be" "For each (Link Type and Operator) combination the following information may be provided"cAAdd a space for "maybe" to make it two words. This is in Table 6 under the Description column Also add "the" on the last line of the last row in the Table (that continues on page 45 on line 52) "For each (Link Type and Operator) combination following information may be provided"d358g2253{k) done 2006/09/21Marked E Ulises Olvera^ Editorial_49`39a 6.3.4.1.4b="The encoding format is defined as shown in the table below."cgThe last line under the Value column needs to be fixed "The encoding format is defined as table below."d418g2254{k) done 2006/08/29 E Ulises Olvera^Technical, Binding_24a5.5b7Need to add some text to be consistent with other casescUThere is no text under Figure 5 on page 24 and Figure 11 on page 29 to describe them.d186g2256v#Please refer to document 21-06-0648era[ UbAUse of a bitmap model to encode the list of events that the MIH would like to receive indications. There are currently 9 events, so using 32 bits will allow enough bits to add new or vendor based events. In the Valid Range, replace "Set of valid link events" with "4 octets representing the list of events" In the Description, add the following: The encoding uses a bitmap where the bit position represents the event ID. A bit set to 1 indicates that the MIH wishes to receive indication forB that event. For example, if bit #0 is set to 1, The MIH requests to receive Link Detected indications. Bits corresponding to reserved event IDs must be set to 0. c^To insure interoperability, the IEEE 802.21 must define how to transmit the set of Event IDs. d507g2274wAccepted{k) done 2006/09/21VENada, Golmie, Member^Technical, Binding_70`21b70`21bst of Event IDs in order to support interoperability between different Link Layers. d502g2270=j €Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool. s to specify .USR instead of .fp5 *Fixed bug that wouldn't allow exporting a ballot with no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create andB Submit Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new ? ۅcAIn 802.21, a Link_Going_Down (MIH_Link_Going_Down) trigger is usually used to indicate a link going down in advance and notify the upper layers for making a preparation to handover. It is necessary for the upper layers to know the reasons for why the link is going to be down. However, the current definition of the Link_Going_Down (MIH_Link_Going_Down) primitive has no parameters for why it has generated, so the upper layers can not take appropriate actions according to the received indicatB ions. We propose to give an amendment to the primitive Link_Going_Down (MIH_Link_Going_Down) by adding a reason code in order to facilitate making appropriate handover decisions after receiving the Link_Going_Down (MIH_Link_Going_Down) indications by upper layers. d535g2218pb- but did not make the changes to MIH_Link_Going_Down . Some one has to add such a section first. --------------------------------------------------------------------------------------------------------Q vlinesܬW-WnWW WWlinkIWJWQWRWSWTWgWۃWۅWەWܰWWaW{WݜW4W5W]WaWWWWWWWWWWW W4W?WjWWWWWWWlinkconfigurethresholdsupdatesthresholdsforlinkparameaVlinkmaynothavethisknowledgeVlinkparametersۅWlinksTWWjWlinktypeWlinktypedoesnotapplytophychannelbutactuallinklayerVropriatelyVmoreVWmultiple@Wneed۴WܢW;WVWWneedbothnumberofoperatorsandlistofoperatorsVneedmoreclarificationandappropriatesuggestedremedyVVneedtoprovideclarifyingtextalongwithcommentܢVneeds۵WWnetwork۫W۴WW@WܬW3WBW݃WnetworksۓW۫W۳W0WWnew۳W3WnoZWےWܷWܸWWW݄Wine22changesasfollows۳Vor,W vbyWW W0WIW{WWWWXWYWZW[W]W_W`WaWbWcWdWeWgWhWiWlWmWoWrWtWuWvW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW!W$W%W+W,W.W/W0W5W6W7W9W;W<W@WBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWRWSWTWWWXWYWZW[W]W^W_W`WaWbWcWdWeWfWgWhWiWlWmW}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWW JykmacceptedZ۳۴۶ʃ,8NܬԃO(>Bགྷྃ  33    33>cxThis information typically originates at different layers of the protocol stack within the MN or other network elements.d21g2222wRejected 2006/09/21 2006/04/28tEPeretzFFeder^Technical, Binding_13`56bzRemove the above text until QoS contribution is accepted by the group. Only when QoS text is included, add this line back c back cne back c687, issue 30w Superceded 2006/08/21 2006/04/3023rEMathieuFPERESSEGObserver^Technical, Non-binding_112`21a8.3.3.3d706 2006/04/3024K !k#p2@J9@|a@2and.2&by@command@7current@document@figure@howpleaseprovidemarkeduptextchange@insteadofremovingwordchangingittoseamlessseemsbette@is@Umatch@needs@network@&of9redraw@Osameatpreviouscomment@schema@hsuch@!text@theܡtook@(update@whether@v18@<21-06-0648@;21-06-0690-00-0000-i@ 21-06-0732-00-0000-c@ :21-06-0741-00-0000-saboutpiggybackacknowledgement@ 621-06-0753-00-0000-l@ -3@31@ fertodefinitionintable-6@adopt@alone@another@Aasܾ/asdefinedinsection8.4.2.13@ based@]beۛ!below@hbroadcastݓby" bycomment369@bycomment577@cbycommentfromsection7adoptsimilarresolutionascommen@ c@1calls@ ). hrbAR 33    TT  RA  33d689g2327 2006/08/11 2006/04/24MarkedsEQiaobingFXieGMember^Technical (was Editorial)_111`15a8.2.1bAChange text to: The data frame packet format is described in Figure 23. The frame may be used for wired 802 technologies such as ethernet and also other wireless 802 technologies such as 802.11 and 802.16. The above same frame structure may also be used with a standard L3 protocol (UDP/TCP) with a well defined MIH port as well. The discovery of MIH Function entities at L3 is outside the scope of the standard.@Az 33    TT  )c  K  TTzcAj1. text needs to improve. 2. The last sentence is out of place, not necessary here, and should be removed.j@A  33d690g2328 &< €€marked###############################################################ǃɃʃ˃̓΃σЃ҃Ӄԃփ׃؃كۃ݃ރ߃ !"#$&'()*+,-./013456789<=>?@AEGHIKLMNOPQRT^abcdefgijklmnpqrs Q]bAReplace "Time Interval in which the link is expected to go down." with "Time Interval (in milliseconds) in which the link is expected to go down."@A>  33V  33h  33>c)The unit of TimeInterval is not defined. d539g2282wAccepted{k) done 2006/09/21Marked^ENada, Golmie, Member^ Editorial_77`16bAeReplca "when a predictive even expected to occur" with "when a predictive event is expected to occur"e@Af  33  33  33J  33R  33fc:Syntax error in "when a predictive even expected to occur"d542g2283{k) done 2006/08/29 _ENada, Golmie, Member^ Editorial_78`30bAcReplace "Number of parameters in LinkParamterList" with "Number of parameters in LinkParameterList"c@Af  33!  331  33Q  33b  33SZkcompletelyAWݓWWcomplexuWcomplicatedYWcomplicatesWcomponentWcomponentsWcomprehended۳WconceptsWconfigurerWconfiguredWconfirmWconfusing۴WWWWconsensusgWWconsiderWconsidered\WconsideringWconsideringprimitivetypeswiththeirdirectionconfirmpriVconsistentWconstrainedWconstructWconsumerWcontainWcontextݓWWcontextualtWconvertWcorrectpWWWWcouldWWcoversWcsWWWA 2006/09/21 2006/04/28EPeretzFFeder^Technical, Non-binding_32`25a5.8.1bAThese recommendations should be handled by specific IEEE 802 working groups, e.g. IEEE802.11 and IEEE802.16. For the better understanding of this specification, some examples are provided as informative recommendations in the Appendix.@A*  33m  33*cA2These recommendations should be handled by specific IEEE 802 working groups, e.g. IEEE802.11 and IEEE802.16. For the better understanding of this specification, some examples are provided as informative recommendations in the Appendix. The last sentence should be removed. No such examples in the Appendix2d242g2244wAccepted{k) done 2006/09/21 2006/04/28EPeretzFFeder^ Editorial_32`41a5.8.2bAfin this standard, in order to access 3GPP services provideds through existing 3GPP SAPs. This does notf@f@f@|||  h:cDmore Access Points that can be of different technology. Therefore, It is possible to have a Vertical handover within an Access Network. It is also possible for an interface to change Access Points of the same type but located in different Access Network@A   33  33  33n  33  33  33  33D  33_  33  33  33(  ^  33d316g2244pInter-technology handover and intra-technology handovers can be replaced by vertical and horizonbtal handovers * def changes made in section 3 instead.wAccepted{k) done 2006/09/21;ENada, Golmie, Member^Technical, Binding_42a6.3b.Review section 6.3 and make changes as needed.as needed. EEleanorFHepworthGMember^ Editorial_29`1a5.5.5bUpdate figure.cHaving a single MIH-3GLINK-SAP seems inappropriate as the MIH is interfacing to different underlying technlogies (may be better to show different technological instantiations of the MIH-3GLINK-SAP). d209g2230pshould be technical{h) defer to next round 2006/09/21 2006/04/2811EEleanorFHepworthGMember^ Editorial_29`1a5.5.5bUpdate figure.cHaving a single MIH-3GLINK-SAP seems inappropriate as the MIH is interfacing to different underlying technlogies (may be better to show different technological instantiations of the MIH-3GLINK-SAP). d209g2230pshould be technical{h) defer to next round 2006/09/15 2006/04/2811ate figure.cHaving a single MIH-3GLINK-SAP seems inappropriate as the MIH is interfacing to different underlying technlogies (may be better to show different technological instantiations of the MIH-3GLINK-SAP). d209g2230rieAB ^Technical (was Editorial)_15`46a5.2bARemove unnecessary/misplaced statement as follows: d) MIH Function may do further processing on MAC/PHY triggers and other related local events. Definition of this processing is outside the scope of the standard. The standard shall provide support for Remote Events remote events as well. Some of these events may encapsulate messages related to network selection (such as Link Going Down) that may be exchanged between different MIH entities. Events are advisory in nature. The decision to BScause a handover or not based on these events is outside the scope of the standard.A@A   333  8    33       33  #    cText needs improvement. d106g2240p#also added a missing word "whether"wAccepted{k) done 2006/09/21 2006/04/24"_18k |5vAf 33  33 33  33 33fEEE 802.16 standard, provides the interface between the MIH Function and the 802.16 control plane. This SAP is used for local MIH exchanges between the MIH Function and the lower layers of the mobility management plane (as part of the 802.16 instantiation of the MIH_LINK_SAP)."EcModify the current text "This SAP defines the interface between the MIH Function and the control plane of 802.16 network." to better explain the SAPd224g2236vAEchange the text to "The C_SAP, defined in the IEEE 802.16 standard, provides the interface between the MIH Function and the 802.16 control plane. This SAP is used for local MIH exchanges between the MIH Function and the lower layers of the mobility management plane (as part of the 802.16 instantiation of the MIH_LINK_SAP)."E@of the MIH_LINK_SAP)."E@OP ۞c(Consistency within a paragraph/sentence.d26{k) done 2006/09/21۟ESanjeevFAthalyeGMember^ Editorial_4`19a1.5b%Replace "shall define" with "defines"c5The standard should not place requirements on itself.d30{k) done 2006/09/21MarkedMarked۠ESanjeevFAthalyeGMember^ Editorial_5`5a2b&Fix typo toward the end of line "All".cTypographical errord36{k) done 2006/08/29ۡESanjeevFAthalyeGMember^ Editorial_5`50a2bReplace with C.S0004-D. c%3GPP2 document number should be used.d42{k) done 2006/08/29ۢESanjeevFAthalyeGMember^ Editorial_7`6a3b+Replace "facilities" with a more clear termc"facilities" is too generald48{c) instructions unclear 2006/08/29ۣESanjeevFAthalyeGMember^ Editorial_7`38a3b#Remove dash between link and layer.cConsistency, customary use.d53{k) done 2006/08/29ۤESanjeevFAthalyeGMember^ Editorial_8`18a3rialWpc"The above frame structure may also be used with a standard L3 protocol...." This sentence is confusing, because the Figure presenting the frame structure is showing an 802.3 frame.d688g2244vsee 687w Superceded 2006/09/21 2006/04/30MarkedqEMathieuFPERESSEGObserver^Technical, Non-binding_111`22a8.2.1bZReplace "Figure 23 - Common MIHF Frame Format" with "Figure 23 - MIHF 802.3 Frame Format"caFigure 23 represents an MIH Frame using 802.3/Ethernet. Other 802s won't use such a frame format.d693g2245iMathieu Peressejrelated to comment # 687vsee 687, issue 30w Superceded 2006/08/29 2006/04/3023rEMathieuFPERESSEGObserver^Technical, Non-binding_112`21a8.3b'Remove the figure and references to it.crFigure 24 deals with how the MIH will transport MIH message. This is clearly implementation specific (sockets....)d706g2243iJin LeejDelete figure 24ksuperceded by 697m Supercededw Superceded 2006/08/294/30%MEFarrokhFKhatibiGMember^ Editorial_42`65a6.3.1b0Insert comma after first appearance of "network"cImproved sentence flowd323{k) done 2006/09/21NEFarrokhFKhatibiGMember^ Editorial_43`24a6.3.1b Remove "more"cSuperfluous segmentd326{k) done 2006/09/21OEFarrokhFKhatibiGMember^Technical, Binding_43`47a6.3.2b^Insert at end of sentence", althoug network configuration changes must also be accounted for."c.Soften "static" as to not to imply limitation.d334i Qiaobing XiemAcceptedwAccepted{k) done 2006/09/21PEFarrokhFKhatibiGMember^Technical, Binding_43`55a6.3.255a6.3.255a6.3.255a6.3.2Qiaobing XiemAcceptedwAccepted{k) done 2006/08/23PEFarrokhFKhatibiGMember^Technical, Binding_43`55a6.3.2ervice Flowc8Rename the figure caption to Remote Command Service Flowd297{k) done 2006/08/21 LEFarrokhFKhatibiGMemberbiGMember hݗbAR 33W  33] r 33Rfield.c;There is no reference to the identifiers defined by 802.21.d399g2255 2006/08/04 EENada, Golmie, Member^ Editorial_47`55b9Add "Refer to table 26 in Annex 4" in the Comments field.c;There is no reference to the identifiers defined by 802.21.d399g2255 2006/08/04 d d Member^Technical, Non-binding_48`58bA Replace "The number represented by the 2nd octet of the length field indicates the total size of the value field." by "The number represented by the remaining octets of the length field (i.e. excluding the first one) indicates the total size of the value field." @Af  33(  33P  33  33  33fcfThe 2nd octet itself does not represent the total size of the value field. It is the remaining octets.d409g2256 2006/07/18B $bAnSuggestion: 0x00000100 - 0x1FFFFFFF Reserved for 802.21 Core 802.21 specific IEs except header specific IEs n@A* 33S *cThe differences between Core Header Specific IEs and Core 802.21 specific IEs are not clear. Does core 802.21 specific IEs inlcude Header Specific IEs? d398g2451wAccepted{k) done 2006/09/217'EDasFSubir ^ Editorial_50`29a 6.3.4.2.3coWhich standard is this? Why only one IE example is provided? It may be good to have other IE example as well. d420g2454{l) none needed 2006/09/21 )EDasFSubir^Technical, Non-binding_54`6a6.3.4.6bMTable 6 need to mention that length is 4 Octets. Delet bit 3 and 4 values. cTable 6 does not define any length, however, this is 4 Octets. This is inconsistent. Also bit 3 and 4 are not required since Table 6 has been updated. d438g2456438g2456438g245603 2006/04/287arked7arked7arked7|9a_117`46a8.3.4bAxRemove "MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" from Table 19x@A  33cA"MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" are improper for 802.21 scope. The functionality represented by these messages is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d758g2265vby comment 495w Superceded 2006/09/21 2006/04/2419bEQiaobingFXieGMember^Technical, Binding_135`12a8.5.3.11bA0Remove the entire section 8.5.3.11 and 8.5.3.12.0@A  33cA"MIH Handover Initiate" is improper for 802.21 scope. The functionality represented by this message is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@@0m7cEFarrokhFKhatibiGMember^ Editorial_88`48a 7.4.6.1.1bChange "makes" to "make".c Plural formd610{l) none needed 2006/09/21dEFarrokhFKhatibiGMember^ Editorial_89`33a 7.4.6.1.3bChange "makes" to "make".c Plural formd617{e) editor disagrees 2006/09/21.c Plural formd610{l) none needed 2006/09/17dEFarrokhFKhatibiGMember^ Editorial_89`33a 7.4.6.1.3bChange "makes" to "make".c Plural formd617{e) editor disagrees 2006/09/17-Clarifiedp21-06-0609-IS_Multihop_Scenario.doc not found on the official server - used 21-06-0609-00-0000-IS-Multihop-Scenario-alt.ppt, per instruction by the commentervd in context of IS services or in a more generic sense.mAccepted-Clarifiedp21-06-0609-IS_Multihop_Scenario.doc not found on the official server - used 21-06-0609-00-0000-IS-Multihop-Scenario-alt.ppt, per instruction by the commentervffffffffffffffY9} Pbcd841g2266vby comment 495w Superceded 2006/09/21 2006/04/24MarkedcEQiaobingFXieGMember^Technical, Binding_135`50a8.5.3.13bA0Remove the entire section 8.5.3.13 and 8.5.3.14.0@A  33cA"MIH Handover Prepare" is improper for 802.21 scope. The functionality represented by this message is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d845g2267vby comment 495w Superceded 2006/08/29 2006/04/24dEQiaobingFXieGMember^Technical, Binding_136`18a8.5.3.15bA0Remove the entire section 8.5.3.15 and 8.5.3.16.0@A  33cA"MIH Handover Commit" is improper for 802.21 scope. The functionality represented by this message is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d848}dg2268vby comment 495w Superceded 2006/09/21 2006/04/24eEQiaobingFXieGMember^Technical, Binding_136`46a8.5.3.17bA0Remove the entire section 8.5.3.17 and 8.5.3.18.0@A  33cA"MIH Handover Complete" is improper for 802.21 scope. The functionality represented by this message is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33d850g2269vby 495w Superceded 2006/09/21 2006/04/24fEQiaobingFXieGMember^Technical, Binding_66`53a7.2.2.1bA8Remove "MIH Network Address Information" from Table 14.8@A  33cccge is part of the handover execution signaling and hence belongs to the upper layer MM algorithm.@A  33ngs to the upper layer MM algorithm.@A  3357 ,bcA  333< gEQiaobingFXieGMember^Technical, Binding_103`25a7.4.14bARemove section 7.4.14.@A  33cA)The inclusion of "MIH Network Address Information" primitive in 802.21 is not sufficiently justified. Both the requester and provider of "Network Address information" will be an upper layer entity, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33d650g2272i Ronny Kimmove section 7.4.14.@A  33cA)The inclusion of "MIH Network Address Information" primitive in 802.21 is not sufficiently justified. Both the requester and provider of "Network Address information" will be an upper layer entity, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33d650g2272i Ronny Kim Ronny Kim>= PibcA)The inclusion of "MIH Network Address Information" primitive in 802.21 is not sufficiently justified. Both the requester and provider of "Network Address information" will be an upper layer entity, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33d854g2274i Ronny KimmRejectedvby comment 597w Superceded 2006/09/21 2006/04/24jEQiaobingFXieGMember^Technical, Binding_59`40a6.3.8bARemove section 6.3.8.@A  33cAThe need for MIH function to support information service schema is not sufficiently justified, given the complexity and computational cost associated with it. @A  33d460g2278iYoshihiro Ohbajiro Ohbajs Information" from Table 19.8@_117`53a8.3.4.bA8Remove "MIH Network Address Information" from Table 19.8@/04/24:~gj:Maybe we need to clarify the section instead of removing. k_As a result of ad hoc discussion, we had group consensus that IP pre-configuration is useful. mRejectedvby comment 597w Superceded 2006/09/21 2006/04/24MarkedhEQiaobingFXieGMember^Technical, Binding_117`53a8.3.4.bA8Remove "MIH Network Address Information" from Table 19.8@A  33cA)The inclusion of "MIH Network Address Information" primitive in 802.21 is not sufficiently justified. Both the requester and provider of "Network Address information" will be an upper layer entity, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33d759g2273i Ronny KimmRejectedvby comment 597w Superceded 2006/08/29 2006/04/24iEQiaobingFXieGMember^Technical, Binding_137`14a8.5.3.19bA&Remove Sections 8.5.3.19 and 8.5.3.20.&@; yjjAPlease be more specific about the given complexity and computational cost associated with supporting information service schema. Without giving detailed analysis, the comment is moot. Note that performance analysis on TLV and XML is provided by contribution 21-05-0407-04-0000-XML-TLV-Integration.doc and this analysis is used as the basis of acceptance of the XML/RDF-based query which is based on schema. mRejectedvPlease refer to contribution 21-06-0678 for more updates. Clarify that SPARQL is used only with schema based implementation. Do we need a MIB for IEs? wRejected 2006/09/21 2006/04/24kEQiaobingFXieGMember^Technical, Binding_67`47a7.2.3.1b$Remove section 7.2.3.1 and Table 16.cThe need for MIH_NMS_SAP is not sufficiently justified. The primitives listed in Table 16 will be provided by any implementation, but it needs to be justified why they need to be standardized and why it must be 802.21 which needs to standardize them.d500~; ,ibA  33cA)The inclusion of "MIH Network Address Information" primitive in 802.21 is not sufficiently justified. Both the requester and provider of "Network Address information" will be an upper layer entity, the role 802.21 is playing here is just transport something for the upper layer, which is improper.)@A  33A:lEQiaobingFXieGMember^Technical, Binding_72`14a7.3.7.2bARe-define the "Link ParameterType" as a pair of {LinkTech : TechSpecificParameterType}. When LinkTech is "Generic" the parameter is then a generic link parameter. Examples - {GPRS : BLER}, {GPRS : RxLevNCell}. Change the current text to: |-------------------|--------------------------------|-----|-------------------------------| |Link ParameterType |A pair of {LinkType:ParamType}. |N/A |Parameters for which thresholds| | | | |may be | | |may be |may be 2006/08/21 2006/04/24kEQiaobingFXieGMember^Technical, Binding_67`47a7.2.3.1b$Remove section 7.2.3.1 and Table 16.6.d500 2006/04/24 >lbDmbABoaEqbFrkGscHtbBIALMcCKucBJvbANwbAOcAPRxbAQcAUvTycASvXzcAVv[{kAY|bA\CacA`_~kA^cAbkAecAdkAgcAfkAicAhkAkbAmjilbAnCtEsGrcAqcAocAucAvbAwCzcAycpwx@{cA~ccckB`bmcA@bAbAwbACkACEGcAkA@cAbb@vAcvEbACE?C lbBset | | |Examples: | | | | |{Generic:Link Speed}, | | | | |{Generic:Link Bit Error Rate}, | | | | |{Generic:Link Frame Loss Rate | | | | | before retransmission}, | | | | Cs |{Generic:Link Signal Strength}, | | | | |{GPRS:BLER}, | | | | |{GPRS:RxLevNCell} | | | |-------------------|--------------------------------|-----|-------------------------------| O@ 2006/04/24 %mbc"Link ParameterType" definitions is insufficient and needs to be expanded. For instance, what if an upper MM algorithm wants to set a threshold on the BLER (block error rate) or RxLevNCell parameter of a GSM/GPRS link?d553g2284vby 552w Superceded 2006/09/21 2006/04/24MarkednEQiaobingFXieGMember^Technical, Binding_72`39a7.3.7.3bAChange text to: This primitive is generated by MIH Function (often on behalf of an upper layer entity) that may need to set threshold values for different link parameters.@A  33  33  0  )cQ  f  )cg  h  TTu  v  ciThis is a link layer primitive which should only be generated by the MIH function, not by an upper layer.d523g2290w Superceded 2006/08/29 2006/04/24oEQiaobingFXieGMember^Technical, Binding_47`42AD lbA  33 33N c  33   33& z  33   33  334  33Q 33  33 33  33  33K  33W 33  33 33 M  33Cs |{Generic:Link Signal Strength}, | | | | |{GPRS:BLER}, | | | | |{GPRS:RxLevNCell} | | | |-------------------|--------------------------------|-----|-------------------------------| O@C lbc"Link ParameterType" definitions is insufficient and needs to be expanded. For instance, what if an upper MM algorithm wants to set a threshold on the BLER (block error rate) or RxLevNCell parameter of a GSM/GPRS link?d520g2282vby 518w Superceded 2006/09/21 2006/04/24mEQiaobingFXieGMember^Technical, Binding_78`39a7.3.14.1bA.change text to: Examples of link layer parameters that could trigger this event include: - {Generic : Link Speed} - {Generic : Link Bit Error Rate} - {Generic : Link Frame Loss Rate before Retransmission} - {Generic : Link Received Signal Strength} - {GPRS : BLER} - {GPRS : RxLevNCell} - etc..@.@eter of a GSM/GPRS link?Foa6.3.3bAChange the text to: The 802.21 Information Elements may beare assigned identifiers (IDs) as follows. Each Information Element ID is a 32 bit value.@Az  33  33  5  TT;  )c>  zcGThe assignment of IS to any Information Element should not be optional.d395g2301i Subir DaskSuperceded by Comment # 394m Supercededvby 394w Superceded 2006/09/21 2006/04/24pEQiaobingFXieGMember^Technical (was Editorial)_48`16a6.3.4b:Move section 6.3.4 to be before the current section 6.3.3.cFSection 6.3.4 is better to be placed before the current section 6.3.3.d404g2302i Subir DasknThis is not the correct flow. Specification should have IE list first before we start describing each IE TLV. mRejectedwRejected 2006/09/21 2006/04/24qEQiaobingFXieGMember^Technical, Binding_44`51a6.3.251a6.3.251a6.3.2EGqb0Remove TYPE_IE_NUMBER_OF_OPERATORS from Table 6.cGThe need for TYPE_IE_NUMBER_OF_OPERATORS is not sufficiently justified.d357g2304vQseems useful to keep the number of operators separate from the list of operators.wRejected 2006/09/21 2006/04/246rEQiaobingFXieGMember^Technical, Binding_47`12a6.3.2bA  33   33V  33>c>c_SCHEMA_URL", and "RDF_SCHEMA" from the value field.cccd783 2006/04/24^}_114`63a8.3.3.1b;Remove "ACK-Rsp bit" and change "Reserved" field to 5 bits.cA4The justification for "ACK-Rsp" bit is insufficient.4@A  33d739g2334vbased on request from commenterwRejected 2006/09/21 2006/04/24~EQiaobingFXieGMember^Technical, Binding_119`57a8.4.1.4bKRemove "RDF_DATA", "RDF_SCHEMA_URL", and "RDF_SCHEMA" from the value field.cARDF (resource description framework) technique was developed at Netscape to deal with knowledge base presentation and free-style natural language understanding (English, French, Japanese, ...). Using RDF for MIH network handover information description is a great overkill since the network handover information is highly structured and can be easily and simply described as a tree or trees. The use of RDF for MIIS is not sufficiently justified.@A  33d783g2336iYoshihiro Ohbakiro Ohbakort. As part of message ea |cA1. The current text implies that the discovery of MIH function entities is supported by this spec, which is not true. 2. There is no sufficient justification for MIH remote registration. In particular, under [1] MIH capability discovery, the two MIH functions have already found each other and negotiated and selected capabilities with each other, why they still need to perform a registration in addition? 3. Schema supported is not sufficiently justified (see other comments on this topicB). @A  33d695g2330i Ronny KimjnThis comment should be discussed in conjunction with proposal "21-06-0611-00-0000-MIH protocol section update"kHave we decided that MIH Function Discovery is outside scope of 802.21? I don't think it can be defined in anywhere else SDO or implementation specific ways.mRejectedv7This has already been addressed by other contributions.wRejected 2006/09/21 2006/04/24d part of message e\` |bCaxchange the peer MIH Function entities may use the MIES, MICS and MIIS for effective handovers. =@A  33  )c  TT    )c    TT    )c  .  )cP  TT    )c  TT    )c     )c  5  TT  )c  TT>  TT@ B TTD  )cH    TT  )c  <nc^e YcARDF (resource description framework) technique was developed at Netscape to deal with knowledge base presentation and free-style natural language understanding (English, French, Japanese, ...). Using RDF for MIH network handover information description is a great overkill since the network handover information is highly structured and can be easily and simply described as a tree or trees. Therefore, the inclusion of "SPARQL Query parameters" and "Schema URL parameters" is not sufficientlB y justified.@A  33d810g2337iYoshihiro OhbakTechnical, Binding_127`33a8.4.2.23bAmRemove "2. SPARQL Query parameters" and "4. zero or one Extended Schema URL parameters" from the value field.m@A>  33   33V  33>ccd810 2006/04/24  vbycomment577Vbycomment597gVhViVVVbycomment607MVbycomment609Vbycomment609wherethisissueisgonnabeinvestigatedinmVbycomment632Vbycomment704Vbycomment715Vbycomment719VVVVVVbycomment719thatdefinesmihfidVbycomment719whichdefinessessionidVbycomment719whichexplainstheuniquenessaspectsofmihfVbycomment737;Vbycomment741WVbycomment752/756+Vbycomment752/756andbycontribution21-05-0671-00-0000-8lVbycomment752/756bycontribution21-05-0671-00-0000-821-fVbycomment757Vbycomment803Vbycomment824VVbycomment874Vbycomment892VV5V6V5267whichtakecareofconfirm/reVbycomments493494Vbycommment527/626LVbyresolutionofcomment346Vbyvote1-4Veg PcARDF (resource description framework) technique was developed at Netscape to deal with knowledge base presentation and free-style natural language understanding (English, French, Japanese, ...). Using RDF for MIH network handover information description is a great overkill since the network handover information is highly structured and can be easily and simply described as a tree or trees. Therefore, the definition of XML related MIME type TLVs for SPARQL query is not sufficiently justifiBed.@A  33d812g2338iYoshihiro OhbakFXieGMember^Technical, Binding_127`41a8.4.2.23b  33   33f  33>ccd815 2006/04/24df PkAJust defining a structured data as a tree or trees is not sufficient. A query language that can understand the structured data is needed for efficient information retrieval. Without use of a query language, the way to retrive information on the structured data is quite limited. That is why XML/RDF query is supported to address this issue. It is recommended to read 21-05-0347-00-0000-XML_IS_Introduction.doc for more information.mRejectedvbased on request from commenterwRejected 2006/09/21 2006/04/2422EQiaobingFXieGMember^Technical, Binding_128`21a8.4.2.24bA}Remove "2. SPARQL Query response", "3. URL response", and "4. zero or one Extended Schema URL response" from the value field.}@A>  33   33f  33>c>cik PcARDF (resource description framework) technique was developed at Netscape to deal with knowledge base presentation and free-style natural language understanding (English, French, Japanese, ...). Using RDF for MIH network handover information description is a great overkill since the network handover information is highly structured and can be easily and simply described as a tree or trees. Therefore, the definition of XML related MIME type TLVs for SPARQL query is not sufficiently justifiBed.@A  33d817g2340iYoshihiro OhbakngFXieGMember^Technical, Binding_128`29a8.4.2.24b)Remove Table 23 (from line 29 to line 63)ccd817 2006/04/2423fh kAJust defining a structured data as a tree or trees is not sufficient. A query language that can understand the structured data is needed for efficient information retrieval. Without use of a query language, the way to retrive information on the structured data is quite limited. That is why XML/RDF query is supported to address this issue. It is recommended to read 21-05-0347-00-0000-XML_IS_Introduction.doc for more information.mRejectedvbased on request from commenterwRejected 2006/09/21 2006/04/24EQiaobingFXieGMember^Technical, Binding_128`29a8.4.2.24b)Remove Table 23 (from line 29 to line 63)cline 63)cm gbcAThe current text implies that the discovery of MIH function entities is supported by this spec, which is not true. While MIH capability discovery is in-scope, MIH discovery is out of scope. @A  33d863g2341iJin Leeksuperceded by 695m Supercededvby 250w Superceded 2006/09/21 2006/04/24MarkedEQiaobingFXieGMember^Technical, Binding_150`1aAnnex CbRemove Annex C.cARDF (resource description framework) technique was developed at Netscape to deal with knowledge base presentation and free-style natural language understanding (English, French, Japanese, ...). Using RDF for MIH network handover information description is a great overkill since the network handover information is highly structured and can be easily and simply described as a tree or trees. Therefore, the support of RDF/XML schema representation is not sufficiently justified.@A  33d899g2343hm kAJust defining a structured data as a tree or trees is not sufficient. A query language that can understand the structured data is needed for efficient information retrieval. Without use of a query language, the way to retrive information on the structured data is quite limited. That is why XML/RDF query is supported to address this issue. It is recommended to read 21-05-0347-00-0000-XML_IS_Introduction.doc for more information.mRejectedvbased on request from commenterwRejected 2006/09/21 2006/04/2423EQiaobingFXieGMember^Technical, Binding_138`39a8.6bA/Change text to: The network entities and the mobile nodes with MIHF shall discover which entity supports MIHF in order to utilize MIHF for media independent handover. MIH capability discovery may be done through media specific broadcast messages or through on demand MIH capability discovery messages. /@/@iYoshihiro OhbakAJust defining a structured data as a tree or trees is not sufficient. A query language that can understand the structured data is needed for efficient information retrieval. Without use of a query language, the way to retrive information on the structured data is quite limited. That is why XML/RDF query is supported to address this issue. It is recommended to read 21-05-0347-00-0000-XML_IS_Introduction.doc for more information.mRejectedvon request from commenterwRejected 2006/09/21 2006/04/24EGuo JunXiang / Shu GuimingGOther^Technical, Non-binding_94`39a 7.4.10.1.2b10.1.2bF for MIH network handover information description is a great overkill since the network handover information is highly structured and can be easily and simply described as a tree or trees. Therefore, the support of RDF/XML schema representation is not sufficiently justified.A  33d899 2006/04/24kj hbAR  33  TT  .Rt bC------------------------------------------------------------------------------------- | Name | Type | ValidRange | Description --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | Source Identifier D| Identifier | Any valid individual | The identifier of entity where the request isinitiated. This field | | | or group identifier | may be optionally left empty if the command is local. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------qu cA[In the current draft, the description about the primitive MIH_Scan is not clear and enough. It is necessary to give the parameter Scan Request Sets a more detailed description, and it is also useful to amend the parameter Scan Response Sets and add a new parameter for providing more information in order to facilitate making handover decisions. [d631g2219vNeed clarification for RequestParameters. Update ScanResponseSets and clarify what they mean. Use same network identifier for link type. Scan not detected set may be useful? Rejected on request of commenter.wRejected 2006/09/21 2006/04/12EYan PENG / Junxiang GuoGObserver^Technical, Non-binding_135`57a8.5.3.13bWe propose to add an IE (NewMACAddress) to tell the MIHF of target PoA the identifier of the MN in target system, which is to handover from serving PoA to target PoA. See the proposal 21-06-0636-00-0000-Resource-Prepare-Amendment.ppt for detailsc detailscy_cCannot interoperate with using the standard document which refers to IETF I-Ds. (also happens in P46-L9, P51-L26, P152-L15, P158-L16. P158-L39)d368g2211vby comment 369w Superceded 2006/09/216ETakashiFAramakiGMember^Technical, Binding_44`38a6.3.2bDefine it properly.ckCannot interoperate with using TYPE_IE_LIST_OF_NETWORKS IE since how to encode is just given as an example.d347g2214i Subir Dask:There is a comment to remove "for example" (Comment # 350)mRejectedv:No specific remedy suggested. Comment #350 addresses this.wRejected 2006/09/212006/08/296ESanjeevFAthalyeGMember^Technical, Binding_16`1a5.3.1b8Remove reference points from figure and rest of documentcpThe reference points are not used anywhere in the document. They do not add any value while they add confusion. d110i Qiaobing XiejEReference points are used in the document, e.g., line 24-49, page 17.mRejectedvPlease refer to Comment 108roEYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.c changed in the case of manual switching mode. According to the proposal, in the case of the manual switching the terminal can either switch to the radio network selected by the user or fail to perform the handover for some reason. If the handover can not be completed the fail reason will return to the user by MIH_ Handover_Initiate.response oBr other primitive. d638g2325vContribution 21-06-0633- Until we have a request to reject a request there is no point in hanving something that overrides a request...wDeferred 2006/09/15 2006/04/17€ATable@A  33EYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.cdetails.c-----------------------------------------sq GcAHere we give a proposal for adding a parameter in the MIH_ Handover_ Initiate.request primitive indicating the suggested network type should not be changed in the case of manual switching mode. According to the proposal, in the case of the manual switching the terminal can either switch to the radio network selected by the user or fail to perform the handover for some reason. If the handover can not be completed the fail reason will return to the user by MIH_ Handover_Initiate.response oBr other primitive. d638g2325vContribution 21-06-0633-01-0000-Amendment for MIH_Handover_Initiate.request Handover_Commit allows MN or Network PoS to force having a particular choice of candiddate link and PoSwRejected 2006/09/21 2006/04/17€ATable@A  33 ) --------------------------------------------------------------------------------------------------------tr bG | | handover. | Unchangeable | | | 1: Current POA can not select another new network Identifier | | | | for handover. | | H | 1: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- @Az  33  ;  33     33   zc----------------------------------------------------------------------------------------ns bE------- | ...... | ....... | ....... | ....... --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | QueryResourceList | Boolean | N/A | F Flag to query the available list of resources on the new link --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | SuggestedNewLinkIdentifier | Boolean | 0: | 0: Current POA can select another new network Identifier for | | ov cAIn the current definition of message MIH_Handover_Prepare.request, there is no information about the MN that would handover to target network. So that after the MN enters the target system, the target PoA is unable to associate the MN with the corresponding MIH_Handover_Prepare.request message, nor can it send MIH_Handover_Complete.request to the corresponding previous serving PoA.d846v6in the June Ad hoc meeting as agreed upon by commenterwRejected 2006/09/21 2006/04/24EYan PENG / Junxiang GuoGObserver^Technical, Non-binding_129`52a8.5.1.2bWe propose to specify the way for dealing with MIH_Capability_Discover.request, i.e. broadcast or not. See the proposal 21-06-0634-00-0000-MIH-Capability-Discovery-Amendment.ppt for details.cdetails.coA is unable to associate the MN with the corresponding MIH_Handover_Prepare.request message, nor can it send MIH_Handover_Complete.request to the corresponding previous serving PoA.uz >cAIn the current draft, the MIH_Capability_Discover.request message is used in different scenarios. But this message is not clear enough. For example, when a PoA receives a message MIH_Capability_Discover.request, how does the PoA deal with it, i.e. to broadcast the message or only to response directly? Both the alternative are possible. Different actions are suitable for different cases. A method is needed to tell the receiver of message MIH_Capability_Discover.request, what the sender waB[nt it to do. And a transport level broadcast or unicast address can't differentiate them.Id822g2219vVNot sure if this is really required. For what scenarios (L3) do you really need this? wRejected 2006/09/21 2006/04/12EBingyunFQuGObserver^Technical, Non-binding_82`58a7.4.1b7.4.1b address can't differentiate them.Ithe sender waB[nt it to do. And a transport level broadcast or unicast address can't differentiate them.IIz  bC SourceIdentifier, DestinationIdentifier, ResponseNetworkType, MacPoA, SupportedEventList, De SupportedCommandList )/@Az 33  33    33zcst ) 7.4.1.2 MIH_Capability_Discover.response MIH_Capability_Discover.response ( !w Superceded 2006/09/21MarkedESanjeevFAthalyeGMember^Technical, Non-binding_20`34a5.4.1.1bSAllow events to be sent from upper layers or from MIHF users to lower layers/MIHF. c{Events should be allowed from upper layers or users of the MIHF, too. For example, IP may indicate a loss of connectivity. d146i Vivek GuptakA/These are not events but commands as we have defined them. Upper layers may use MIHF services and take specific actions. Link selection policy engines are outside the scope of spec and hence such it's not clera what specific value may be obtained through such notifications to MIHF in the specification./mRejectedvASince MIHF does not really make any policy type decisions, , it's not clear if it needs to know about loss of IP level connections. Also in the current MIHF framework defnition, evnts flow from lower layers (L2) to higher layers and commands flow from higher layers to lower layers.wRejected 2006/08/29 pxETakashiFAramakiGMember^Technical, Binding_45`19a6.3.2b.Wait until the referenced I-Ds to become RFCs.etwork and PoA the MIH capability is about. In figure 29, On Demand MIH Capability Discovery Procedure is described. MIH user should point out the type of network whose MIH capability need to be discovered. Without an identifier, receiver could not distinguish MIH capability information included in response message relative to which Entity send this message. So, PoA identifier (orBh other identifier ) should be added into response message to indicate which entity return this message. Vd573g2247vDon't need additional link Type under MIH parameters for Capability Discovery. Commenter does feel this may be useful. Refer to contribution: 21-06-0637-01-0000-wDeferred 2006/09/15 2006-04-07ETakashiFAramakiGMember^Technical, Binding_45`19a6.3.2b.Wait until the referenced I-Ds to become RFCs.come RFCs. vw bAUpdate according to submitted document: 21-06-0637-00-0000-MIH Capability Discovery.ppt 7.4.1.1 MIH_Capability_Discover.request MIH_Capability_Discover.request ( SourceIdentifier, DestinationIdentifier, RequestNetworkType, B SupportedEventList, SupportedCommandList, SupportedISQueryTypeList ) 7.4.1.2 MIH_Capability_Discover.response MIH_Capability_Discover.response ( ~ESanjeevFAthalyeGMember^Technical, Non-binding_22`20a5.4.3b*"The access to information should be fast"cHRemove implication that access is remote, since information may be locald163i Subir DaskPl. see Comment # 162m Supercededv2The lines have been deleted in text by Comment 162w Superceded 2006/09/21ESanjeevFAthalyeGMember^Technical, Binding_22`21a5.4.3b"Use of network resources for accessing information should be minimized (e.g. over-the-air messages should be curtailed, and when needed should contain least possible overhead)"cBroaden the statement to "use of network resources". Current formulation implies that the only way to access information is by means of querying server by the MN.d164vby comment 162w Superceded 2006/09/21ESanjeevFAthalyeGMember^Technical, Binding_27`65a5.5.4b^Better understand and clarify the amount of work needed to interface MIH with 3gpp protocols. ctocols. ctocols. con.n.  $icA- Have more space between characters in "STA/UE" and "PSDN/FA" boxes. - "PSDN/FA" should read "PDSN/FA". - PSDXA, should be GRE be in the flow? - Acronym for GRE needs to be defined in Section 4. - Is this an example of "Network Initiated Hand Over" ? - Line 55. the circle point left to "MIP binding to HA" should be shifted to the left. - Line 56. Does the AP get Link Tear Down or Handover complete indications before it is disassociated? d873g2399vby 872w Superceded 2006/09/21 2006/04/28 Figure 30jE Ulises Olvera^Technical, Binding_30a5.6.1bIShould include a definition or explanation for consistency and completioncfThe sub-sections do not explain or define all the media specific SAPs that arfe shown in the figure 12d212g2257vkE Ulises Olvera^Technical, Binding_32`55a5.8.3 No text available. wRejected 2006/09/18MarkedkE Ulises Olvera^Technical, Binding_32`55a5.8.381818181 2006/04/28ecNPreferredPoAIdentifier is not needed if it is part of PreferredLinkIdentifier.d844g2378vby comment 527/626w Superceded 2006/09/21 2006/04/28MarkedfE YoshihiroFOhbaGMember^Technical, Binding_136`30a8.5.3.15bRemove NewPoAIdentifier.c;NewPoAMAC is not needed if it is part of NewLinkIdentifier.d849g2379vby comment 527/626w Superceded 2006/08/29 2006/04/28gE YoshihiroFOhbaGMember^Technical, Binding_137`26a8.5.3.19b*Replace MacMobileNode with LinkIdentifier.c5MacMobileNode should be replaced with LinkIdentifier.d856g2380vby comment 527/626w Superceded 2006/08/29 2006/04/28hE YoshihiroFOhbaGMember^Technical, Binding_137`46a8.5.3.20b*Replace MacMobileNode with LinkIdentifier.c5MacMobileNode should be replaced with LinkIdentifier.d857g2381vby comment 527/626w Superceded 2006/08/29 2006/04/28iE YoshihiroFOhbaGMember^Technical, Non-binding_140`1a Annex A-1c{ cAeThe text says: " [...] no new primitives or protocols need to be defined in 3GPP specification for accessing these services. The MIH function services may be easily mapped to existing 3GPP primitives". Not clear how MIH can be easily mapped to existing primitives, since primitives in 3gpp are only provided as an example and they are not always up-to-date.ed196i Vivek GuptakAjInstead of trying to map MIH primitives to 3GPP/3GPP2 , 802.21 should try to focus on how to enable handovers between 3GPP/3GPP2 and non-3GPP systems through individual MIHF services, their individual value and applicability in 3GPP/3GPP2 networks. The idea of trying to introduce MIHF in 3GPP/3GPP2 in generic sense may not work well with 3GPP/3GPP2 community.jmAcceptedvby Comment 195w Superceded 2006/09/21ESanjeevFAthalyeGMember^Technical, Binding_28`55-57a5.5.5b5Remove middle sentence. Remove "in this case" at end.e" at end.ESanjeevFAthalyeGMember^Technical, Binding_51`6a 6.3.4.2.5bIConsider specifying the QoS information in link layer independent format. should have the knowledge of whether or not network supports IEEE 802.21 specification, and may obtain this knowledge by means of media independent or media specific discovery mechanisms."cNAmbiguity, succinctness. Allow the case that MIH is not supported in network.d402wDeferred 2006/09/15ESanjeevFAthalyeGMember^Technical, Binding_51`6a 6.3.4.2.5bIConsider specifying the QoS information in link layer independent format.ecific discovery mechanisms."cNAmbiguity, succinctness. Allow the case that MIH is not supported in network.d402wDeferred 2006/09/15ESanjeevFAthalyeGMember^Technical, Binding_51`6a 6.3.4.2.5bIConsider specifying the QoS information in link layer independent format.nt format.nt format.Technical, Binding_45`46a6.3.2.2.2.2.2d372~c^Intent of middle sentence is unclear and possibly misleading. These decisions are up to 3GPP2.d206vby comment 203w Superceded 2006/09/21ESanjeevFAthalyeGMember^Technical, Non-binding_43`35a6.3.1b[Insert at end of sentence "only when probability of accessing those networks is increased".c-Remove implied limitation, better explain used329wRejected 2006/09/212006/08/29MarkedESanjeevFAthalyeGMember^Technical, Non-binding_44`51-56a6.3.2bEProvide operator identity attribute to each instance of WLAN instead.c4Irrelevance. Number of operators is of no relevance.d365v6Number of operators is a required piece of informationw Superceded 2006/08/29ESanjeevFAthalyeGMember^Technical, Binding_45`46a6.3.2bSpecify envelope of capabilities as appropriate for a static descriptor associated with QoS, e.g. maximum allocatable data rate for a single user, minimum attainable delay, etc. See also page 46 lines 35-40.cwSpecification of TYPE_IE_NETWORK_QOS is not media independent. Thus the MIH user will be exposed to link layer details.d423i Hong ChengjAChange to the description of "TYPE_NETWORK_QOS" element to indicate that it carries information about QoS characterstics of the access network. Such information is used for heterogeneous access, and is genereally not avaialble through link layer mechanisms. kAThe link layer QoS charaterstics are available to the STA via individual link layer specific mechanism, e.g. 802.11 provide QoS characterstics (e.g. EDCA parameters) in the Probe Response, and Associate Response. Therefore, this Information Service element should be used to provide network QoS information that is useful for the heterogeneous access, and not avaiable through link layer mechanisms. One example of such QoS information is the QoS Mapping table, e.g. from DSCP to 802.1D, or frt supported in network.d402wDeferred 2006/08/21ESanjeevevev}bc- OldMacMobileNode and OldLinkIdentifier should be replaced with one unified LinkIdentifer TLV. - NewMacMobileNode and NewLinkIdentifier should be replaced with one unified LinkIdentifer TLV. d837g2367vby comment 527/626w Superceded 2006/09/21 2006/04/28cE YoshihiroFOhbaGMember^Technical, Binding_132`64a8.5.2.12b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccRMacMobileNode and MacNewPoA are not needed if they are part of Link Identifer TLV.d838g2368vby comment 527/626w Superceded 2006/09/21 2006/04/28dE YoshihiroFOhbaGMember^Technical, Binding_135`24a8.5.3.11b#Remove SuggestedMACNewPoAIdentifiercTSuggestedNewPoAIdentifier is not needed if it is part of SuggestedNewLinkIdentifier.d842g2377vby comment 527/626w Superceded 2006/09/21 2006/04/28eE YoshihiroFOhbaGMember^Technical, Binding_135`45a8.5.3.12bRemove PreferredPoAIdentifierIdentifierIdentifierIdentifier28mAccepted-Modifiedvsee 704w Superceded 2006/09/21ESanjeevFAthalyeGMember^Technical, Binding_126`33-34a8.4.2.18bFill in with reason codescMissing value range and codesd805vby comment 803w Superceded 2006/09/21MarkedMarkedESanjeevFAthalyeGMember^Technical, Binding_137`19-21a8.5.3.19bProvide more specifics on what "enough information means. Is the intent to say "in this message" as opposed to "on this message".ceVagueness in "enough information" and confusing trailing phrase "enough information on this message".d859v0no suggested text. Issue identified and assignedwRejected 2006/08/29ESanjeevFAthalyeGMember^Technical, Binding_140`140a Annex A-1cMore call flows should be added to show how MIH Protocol is used. In addition the call flow here seems not right. It should be replaced by call flow that is shown in 3GPP2 liaison.d875v3Issue identified and assigned. No suggested remedy.wRejected=`42-61a6.3.6.3b3Remove example, or better convey incremental value.cjIn addition to suffering from the same lack of context as above, the example has little incremental value.d454vby comment 339w Superceded 2006/09/21ESanjeevFAthalyeGMember^Technical, Binding_58`23-54a6.3.7.2b3Remove example, or better convey incremental value.cjIn addition to suffering from the same lack of context as above, the example has little incremental value.d457vby comment 339w Superceded 2006/09/21ESanjeevFAthalyeGMember^Technical, Binding_62`16a6.3.9bFIt seems that Report Availability should occur after response arrives.cEbkQInformation Server would be one of MIH Users, so indication primitive is correct.mRejectedvby comment 473w Superceded 2006/09/2122ENada, Golmie, Member^Technical, Binding_71`31bAUse of a bitmap model to encode the status of the event deregistration process to the MIH . There are currently 9 events, so using 32 bits will allow enough bits to add new or vendor based events. In the Valid Range, replace "Set of valid link events" with "4 octets representing the list of events" In the Description, add the following: The encoding uses a bitmap where the bit position represents the event ID. A bit set to 1 indicates that the deregistration for that event has been succ been succ0"E_LIST_OF_NETWORK_TYPE".c0The Type must match the one defined in Table 6. d449g2263v448wRejected-Duplicate{l) none needed 2006/08/21ENada, Golmie, Member^Technical, Non-binding_58`28bREplace "Variable" with "0" bBessful, otherwise either the deregistration was unsuccessful or not requested. For example, if bit #0 is set to 1, The MIH requested to stop receiving Link Detected indications and the deregistration was successful. Bits corresponding to reserved event IDs must be set to 0. Mapping the bitmap used in the request and the one returned by this primitive allows quick detection of deregistration failure. czTo insure interoperability, the IEEE 802.21 must define how to decode the Set of Event IDs and their registration status. d512g2277w Superceded 2006/09/21ENada, Golmie, Member ^Technical, Binding_75`51b75`51b71`31b would be one of MIH Users, so indication primitive is correct.mRejectedvby comment 473w Superceded 2006/08/2122ENada, Golmie, Member^Technical, Binding_71`31bbbd512 bASince the generation of Link_Going_Down is implementation dependant, the upper layer may be able to configure the following thresholds for the Link_Going_Down generation: - TimeInterval: minimum time required by upper layer. A Link Going down event is generated when the time interval goes below this threshold. - ConfidenceLevel: minimum confidence level required by upper layer. A Link Going Down event is generated when the confidence level exceeds this threshold (and TimeInterval is . AddB a primitive Link_Going_Down_configure.request Function This primitive is used by MIH Function to configure the Link_Going_Down indication Semantics of service primitive The primitive parameters are as follows: Link_Going_Down_configure.request ( TimeInterval, ConfidenceLevel )"M{jasindicatedseveralitemsofthelistmustbeinterpretediܾVassociatedjWat,W=WavaialbleWbase,WbasedjWbasicallyvWbasisjWbe?WܾWjW|WWWW=WVW}WWWWWWbecause,WbeingWbelongs"Wbelongstoupperlayermobilitymanagement"VbetterWWWWWbut|W,WbyvWjWW W{WWc462Wcan,WWWWcannotWcapabilityܾWcarefullyVWcarriesWcaseszWcertainWzWchange@WWWW+WYWWchangefigure20asshownin21-06-0607-00-0000-sforcommen+VchangetexttoVchangethetableasdefinedin21-06-606-01-0000locinfoovYVchangetothedescriptionoftypenetworkqoselementtoindVchangetypeieqostotypeienetworkqosVcharactersticsWcheckWclarifygWWWclassifiedW,\E YoshihiroFOhbaGMember^Technical, Binding_130`65a 8.5.2.5-12bBAdopt suggested change [4] in 21-06-0522-04-Session_Identifier.doccSession Identifier is missing.d827g2390von request of commenterwRejected 2006/09/21 2006/04/28]E YoshihiroFOhbaGMember^Technical, Binding_131`11a8.5.2.6b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d829g2362vby comment 527/626w Superceded 2006/09/21 2006/04/282006/04/28^E YoshihiroFOhbaGMember^Technical, Binding_131`29a8.5.2.7b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d831g2363vby comment 527/626w Superceded 2006/08/29 2006/04/28_E YoshihiroFOhbaGMember^Technical, Binding_131`51a8.5.2.8b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cA}There is no definition on how the list of events is created. It is also necessary to clarify what are the supported events. It can be the events supported by the MIH or the events supported by the underlying interfaces. Furthermore, if there are multiple interfaces with different event support, it may be beneficial to the upper layers to know which interface supports the events.}d583g2288v!Superceded by appropriate commentw Superceded 2006/09/21dthat the Link Layer supports the event. Event IDs are definedBK in Table XX in section 7.3.1." (see comment 33 for complete definition) 9ccription, add the following: "The encoding uses a bitmap where the bit position represents the event ID. A bit set to 1 indicates that the Link Layer supports the event. Event IDs are definedhe encoding uses a bitmap where the bit position represents the event ID. A bit set to 1 indicates that the Link Layer supports the event. Event IDs are definedededYjkChange the Table as defined in 21-06-606-01-0000_loc_info_over_tlv.doc section 3 and adpot new identifiers.k- There is an overlap of the values already allocated for MIHF coder header space (talbe 7) - Don't mention interger numbers, but use the TYPE_IE_xxx names to represent them in the following section. A reallocation of the numbers will become complicatedvby comment 527/626w Superceded 2006/09/21 2006/04/28Table 20ZE YoshihiroFOhbaGMember^Technical, Binding_124`50a8.4.2.11b*Replace NetworkTypes with Link Identifier.c%NetworkTypes should be LinkIdentifierd799g2370vby comment 527/626w Superceded 2006/09/21 2006/04/282006/04/28[E YoshihiroFOhbaGMember^Technical, Binding_130`55a8.5.2.5b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d825g2361vby comment 527/626w Superceded 2006/08/29 2006/04/28\ bG 2: Rejected When generated This primitive is generated in response to a Link_Going_Down_configure.request. Effect on receipt The recipient prepares to receive Link_Going_Down notifications  o@Af  33  33  33  33  33fcThe document specifies that an upper layer may "configure the time interval in which a Link_Going_Down event may be delivered" but there is no configuration method defined in the standard. d536g2281vkConfidence level is vague and it's not clear if various links can support time-interval based notification.wRejected 2006/09/21ENada, Golmie, Member^Technical, Binding_83`65b5Add "SupportedISQueryTypeList" to the parameter list.c4The parameter "SupportedISQueryTypeList" is missing.d581g2287iJin Leeksuperceded by 577m Supercededvsuperceded by 577w Superceded 2006/09/212006/08/29 bEe Link_Going_Down_configure.confirm Function This primitive is sent in response to a Link_Going_Down_configure.request. It specifies the status of the request. Semantics of service primitive The primitive parameters are as follows: Link_Going_Down_configure.confirm ( Status ) Name Type Valid RanFge Description Status Enumerated Success, Error, The status of the request Rejected 0: Success 1: Failure  bC Name Type Valid Range Description TimeInterval Integer 0-65535 Minimum requested time Interval (in milliseconds) in which the link is expected to go down before notification ConfidenceLevel Percentage D 0-100 The minimum confidence level required for link to go down notification When generated This primitive is generated by a registrant such as MIH Function that is seeking to configure the Link_Going_Down notification. Effect on receipt The recipient responds immediately with Link_Going_Down_configure.confirm Add a primitivbIt may be interesting for an upper layer to register on a per interface basis or to return the status code for each interface. cAThe MIH Event Register and MIH Event Deregister refer to the Link Event primitives for their definition. When an upper layer entity registers for a set of events, the underlying interfaces may not all support these events. Using the link layer primitives to retrieve the results, only one status code per event can be set. Therefore, if one interface fails to register the event and another one succeeds, what is the meaning of the status code? d586g2290vLRefer to comment 588 as it has specific resolution. No clear text proposed.wRejected 2006/09/21ENada, Golmie, Member^Technical, Binding_13`52a5.1.3boInclude the QOS model and primitives described in contribution # 21-06-0598-00 (or later version if available.)c]The current 802.21 draft does not include an adequate framework and primitives to handle QOS.d92ENada, Golmie, Member^Technical, Binding_84`19bAAdd a new line with the following information: SupportdISQuery- List Set of supported IS List of supported IS query types on client TypeList query types c?The definition of the parameter for SupportedISQuery is missingd584g2289vby comment 577w Superceded 2006/09/21^Technical, Binding_84`19bAAdd a new line with the following information: SupportdISQuery- List Set of supported IS List of supported IS query types on client TypeList query types c?The definition of the parameter for SupportedISQuery is missingd584g2289vby comment 577w Superceded 2006/09/152006/08/29ENada, Golmie, Member^Technical, Non-binding_84`30 AvC (no need to add it). The type column refers to IE's but should be defining TLVs. Part 3: Query examples are definitely needed. Want to accept from In Section: 7.4.15.1.2 Semantics of service primitive on down once clarified/modified text provided. wRejected 2006/09/21 2006.04.25  is used in the request response.d413g2267v49`2a6.3.4.1bwAdd a new section as suggested in 21-06-606-00-0000_loc_info_over_tlv.doc, chapter 3: 6.3.4.x.x Information Query TypecSince we are aiming to represent more than one syntax for IE requests and responses, we need a TLV to indicate which type of syntax is used in the request response.d413g2267vg2267ve of the message. Given that, the Session ID must be part of the fixed header information. d729g2299vSame as comment 90w Superceded 2006/09/21ENada, Golmie, Member^Technical, Non-binding_114`3bAThere are two potential remedies: a) define a transaction ID that is unique. b) Use the combination of Session ID and Transaction ID to uniquely identify the source of the message. Given that, the Session ID must be part of the fixed header information. cIf the transaction ID is to be unique it is important to clearly define the scope of the ID. It is not clear whether the transaction ID must be globally unique or combined with the Session ID.d729g2304vby comment 719w Superceded 2006/09/21ENada, Golmie, Member^Technical, Binding_82a7.4b.add a link ID parameter to all MIH primitives.cyThe MIH primitives do not include a link identifier. Thus there is no way for MIH users to specifiy the link of interest.d568g2334vg2334v8g2334v cA&Not clear what granularity MIH_SWITCH occurs on. When invoked, does it move all active sessions from one interface to another, is it only called when an interface is about to lose connectivity, how does it have enough information about sessions to decide when an interface should power down. &d609g2275vRefer to contribution 21-06-0737-01-0000-SwithCommand This command refers to link switching and not switching of sessions. Clarification already in draftwRejected 2006/09/21 2006/04/28d divided into multiple parts. Only the last part is accepted (conditionally) Part 1 regarding Table 7 changes is rejected. Reason: The table refers to IE's, not TLV (see Table 20 vs Table 26). Also not clear why we need "Core header specific 'IEs' Part 2 There is confusion in Table 7 between IE and TLV. The fixed header is not in TLV format (see fig 28) . Note the fixed header length is wrong. This part is rejected. Reason: Already have QUERY type defined|c3No proper example is given for TLV reques/response.d675g2269vSee 413w Superceded 2006/09/21 2006.04.25MarkedEVivekFGuptaGMember^Technical, Non-binding_7`1a3b"Add definition of handoff/handovercJInclude definition of handoff and handover and distinguish between the twod46g3263vNo text has been provided...wRejected 2006/08/29EVivekFGuptaGMember^Technical, Non-binding_14`26a5.1.6bOClarify how/in what way security information is made available to upper layers.c"The 802.21 standard specifies the means for security information to be made available to the upper layers to setup secure connections." Is this done in a media independent manner? If not then what is the value-add of 802.21?d95g3249v3Need to provide clarifying text along with comment.wRejected 2006/08/29EVivekFGuptaGMember^ Editorial_15`42a5.2bDefine "Intra-roaming"c0"Intra-roaming" handover mechanisms is undefinedd105,g3220v comment 104.w Superceded 2006/09/21EVivekFGuptaGMember^Technical, Non-binding_16`50a5.3.1boInclude recommendations for transport options either in this section or in Appendix as informative suggestions.cA"The MN may use L2 transport for exchanging MIH information with a MIH PoS that resides in the same Network Entity as its Network PoA. The MN may use L3 transport for exchanging MIH information with a MIH PoS that may not reside in the same Network Entity as its Network PoA. " From MN implementation perspective, it is important that there will be one transport it should support, rather than leaving it open and potentially supporting both.d115g3250wRejected 2006/09/21EVivekFGuptaGMember^Technical, Binding_17a5.3.117a5.3.17a5.3.1-binding_7`1a3b"Add definition of handoff/handovercJInclude definition of handoff and handover and distinguish between the twod46distinguish between the twod46464646EWolfgangFGroetingGMember^Technical, Binding_106`59a 7.4.15.1.2bAdd the ammendments as suggested in 21-06-606-00-0000_loc_info_over_tlv.doc, chapter 3: "In Section: 7.4.15.1.2 Semantics of service primitive" cThere is no mechanism to ask for a specific location/interest based information elements from a MIH-IS server over TLV queries.d663g2268vSee comment 413w Superceded 2006/09/21 2006.04.25 EWolfgangFGroetingGMember^Technical, Binding_108`20a 7.4.15.3.1bAdd the example as suggested in 21-06-606-00-0000_loc_info_over_tlv.doc, chapter 3: "In Section: 7.4.15.3.1 Example Query for TLV" er over TLV queries.d663g2268vSee comment 413w Superceded 2006/09/15 2006.04.25 EWolfgangFGroetingGMember^Technical, Binding_108`20a 7.4.15.3.1bAdd the example as suggested in 21-06-606-00-0000_loc_info_over_tlv.doc, chapter 3: "In Section: 7.4.15.3.1 Example Query for TLV" for TLV" for TLV" j Ic=Are link Synchronous Events applicable for L2 handovers only?d259g3230vNo suggested Remedy. Issue #68.wRejected{a) awaiting resolution 2006/09/21ESanjeevFAthalyeGMember^Technical, Non-binding_37`29a6.1.8bDefine paging related eventscDefine event for page received. The receipt of a page from technology A may trigger handoff to technology A (e.g. if no traffic exchange is in process for the current technology).d275i Vivek GuptakWhat is a page in this context?m Question?vONo suggested remedy. There are no paging related concepts in the current draft.wRejected{a) awaiting resolution 2006/09/21EFarrokhFKhatibiGMember^Technical, Non-binding_37`29a6.1.8b`Define if link events are envisoned to be used for MIP handoff within APs of the same technologytechnologytechnology6.1.2b.Clarify description of link synchronous eventsc=Are link Synchronous Events applicable for L2 handovers only?d259g323026a6.3.1bInclude description of case where Information Repository may be locally avialable on a client device in last paragraph of section 6.3.1cThe client may also have local information for different available networks. In addition the client may also be able to augment information available from the network. d327g3240iWolfgang Grtingj:disagree, there is no need to explain where it is located.kb- We haven't mentioned where MIIS is to be located. Thus it can also be a component in the client.wRejected 2006/09/21EVivekFGuptaGMember^Technical, Binding_44a6.3.2bA Clarify representtaion of all IEs in Table-6. Operator Names, List of Networks, Roaming partners, etc. all should be represented clearly in well known data types. Also clearly specify relation of all IEs in Table-6 with their corresponding description in section 6.3.4. cmThe Representation of different IEs listed in Table-6 is not clear. In most cases this is just a description.d339gUb;- Remove line 33 "Transaction ID" - Remove Section 8.3.2.3.cMThis section should discuss identifiers carried in Variable Header part only.d717g2388iWolfgang Grtingjdisagreek9The section is describing the IDs used for MIHF protocol.v9The section is describing the IDs used for MIHF protocol.wRejected 2006/09/21 2006/04/28VE YoshihiroFOhbaGMember^Technical, Binding_113`49a8.3.2.1bZRemove TYPE_HDR_TLV_MIHF_ID Define TYPE_HDR_TLV_SRC_MIHF_ID and TYPE_HDR_TLV_DST_MIHF_ID.c}Different TLVs should be used for Source Identifier and Destination Identifier in order to be less dependent on TLV ordering.d722g2408iWolfgang Grtingjshould be discussed carefullykSince we are not aiming in the present state on routing\forwarding algorithms at MIHF protocol level, actually there is no need of a destination MIHF-ID.n MIHF-ID.ion 8.3.2.3.cMThis section should discuss identifiers carried in Variable Header part only.d717g2388888888 2006/04/28EVivekFGuptaGMember^Technical, Binding_47`26a6.3.2bWAdd text to support multicast/broascast of information on client query for certain IEs.cThe MIH on the network may broadcast/multicast Information certain IEs/Reportsfrom the MIIS. The information broadcast/multicast should commence only when a client queries for a certain set of IEs.d391g3260i Subir Das Subir kvIs this a bootsrapping issue? If not, then why it has to be media specific information request/response primitive. mRejectedwRejected 2006/09/19MarkedEVivekFGuptaGMember^Technical, Binding_47`26a6.3.2bWAdd text to support multicast/broascast of information on client query for certain IEs.cThe MIH on the network may broadcast/multicast Information certain IEs/Reportsfrom the MIIS. The information broadcast/multicast should commence only when a client queries for a certain set of IEs.d391g3260i Subir Das ir Das Subir Das Subir Das.3.4. d3396kzThe reason is not clear. Why is broadcast/multicast necessary for query? Query should be followed by unicast response. mRejectedwRejected 2006/09/21dd the missing word "media"cA " Before authenticating with the PoA, the MIH Function in the MN may extract the Information Elements either from media specific broadcast information or by sending a media specific information request/response primitive, in which case the MIH protocol is not used. " @A>  33  33  33>d388g3252iSubir kvIs this a bootsrapping issue? If not, then why it has to be media specific information request/response primitive. mRejectedwRejected 2006/09/15EVivekFGuptaGMember^Technical, Binding_47`26a6.3.2ormation request/response primitive. mRejectedwRejected 2006/09/15EVivekFGuptaGMember^Technical, Binding_47`26a6.3.226a6.3.226a6.3.2T-7EVivekFGuptaGMember^Technical, Binding_49`1a6.3.4bTInclude specific examples of all IEs listed in Table-6. This could even go in Annex.cA further expansion of the IEs listed in table 6 is needed. For example, a structure of all the contents of TYPE_IE_LIST_OF_NETWORKS may help - 6.3.4.1 lists this out.but an example would help more. Same for TYPE_IE_NETWORK_SECURITY, TYPE_IE_QOS etc.d411g3234i Hong Chengj-Change "TYPE_IE_QoS" to "TYPE_IE_NETWORK_QOS"15EVivekFGuptaGMember^Technical, Binding_49`1a6.3.4bTInclude specific examples of all IEs listed in Table-6. This could even go in Annex.cA further expansion of the IEs listed in table 6 is needed. For example, a structure of all the contents of TYPE_IE_LIST_OF_NETWORKS may help - 6.3.4.1 lists this out.but an example would help more. Same for TYPE_IE_NETWORK_SECURITY, TYPE_IE_QOS etc.d411g3234i Hong Chengj-Change "TYPE_IE_QoS" to "TYPE_IE_NETWORK_QOS"TWORK_QOS"2006/08/21mkuIn section 6.3.4.2.5, it is named "TYPE_IE_NETWORK_QOS" instead of "TYPE_IE_QOS" as in item 2.6 of table 6 (page 45).mAccepted-Modifiedw Superceded 2006/09/21EVivekFGuptaGMember^Technical, Binding_54a6.3.5buInclude client location as an essential input parameter in all client requests for individual IEs or IE based reportscXWhen retrieving IEs the client needs to specify it's own location as an input parameter.d435g3239i Qiaobing XiemAcceptedvyThis is desired but we cannot mandate this. Certain technologies may be able to determine the client location implicitly.wRejected 2006/09/21EVivekFGuptaGMember^Technical, Binding_56a6.3.7bInclude examples of IE Reports and clarify how to use them for different cases with examples. Include specific examples for client query and corresponding response. response. response.elp more. Same for TYPE_IE_NETWORK_SECURITY, TYPE_IE_QOS etc.d411g3234i Hong ChengngmAccepted-ModifiedcIt's not clear what the purpose of pre-defined reports is, how many such reports are defined, can more be defined and how these can be used.d446g3238vCNo clarifying text provided. Refer to comment 339 for more details.wRejected 2006/09/21EVivekFGuptaGMember^Technical, Binding_83`22a7.4bPChange the Valid Range for DestnationIdentifier in all primitives in section 7.4cA;Valid Range for Destination Identifier is MIH_LOCAL/MIH_REMOTE Destination Identifier always needs to be MIHF Identifier of local MIHF or remote MIHF. It is not a constant value. Also since multiple remote MIHF entities may be available the Destination Identifier helps to correctly identify the remote MIHF entity;d579g3259iMathieu Peressej Peressejeports and clarify how to use them for different cases with examples. Include specific examples for client query and corresponding response.e.e.d446 ZjA!Does this interfere with Session ID ? If we establish a session, do we still need to specify MIHF ID Src and Dst, as they should already be in memory. .. or Session ID is used to multiplex multiple MIH communication between two MIHF IDs ? We should list all the IDs and clarify their uses.!vby 578w Superceded 2006/09/21MarkedEVivekFGuptaGMember^Technical, Non-binding_108`18a7.4.15.3b@Add more descriptive text. Move Example Queries to the Annex. .cEExample queries need more descriptive text and should be in Appendix.d673g3257v1no suggested text. Issue identified and assigned.wRejected 2006/08/29EVivekFGuptaGMember^Technical, Binding_112b.Clarify any interaction between MIHF and hardware, or modify Figure 25 appropriately or Rename hardware interface to something moreappropriatec)Why is MIHF linked to hardware interface?d686g3243iWolfgang GrtingjDo you mean here Figure 23?vby comment 704w Superceded" 2006/09/21F-24EVivekFGuptaGMember^Technical, Binding_116`1a8.3.3.2bRemove references to Transaction ID from MIHF Variable Hedaer section (8.3.3.2) Specify MIHF Variable Header is optional in a MIHF frame.cTransaction ID is now part of MIHF fixed Header. As such it cannot be part of MIHF Variable header. Aso MIHF Variable Hedaer is Optional.d752g3258vby comment 719w Superceded 2006/09/21EVivekFGuptaGMember^Technical, Binding_138`39a8.6bAUpdate Fig 29. An overall flow control diagram is required showing all of these key steps involved in discovering MIH Presence, determining iMIHF capabilities, carrying out any required MIHF registrataion and then service specific registration to utilize MIHF capability.cccware interface to something moreappropriatec)Why is MIHF linked to hardware interface?d686g3243iWolfgang GrtingjDo you mean here Figure 23?vby comment 7040404F-24 cA?MIH Capability Discover procedure needs to be distinguished fro overall MIH Functionality discover (presence) in the network. Also if there are any MIHF registation steps involved, they also need to be comprehended in overall scheme of things. An overall flow control diagram is required showing all of these key steps.?d862g3255i Ronny KimjNeed to modify whole 8.6kCommenter's right. However not only figure 29 but also whole 8.6 section should be modified. Since this comment doesn't contain enough text proposal and suggestion for figure 29, it seems to be right to reject this comment and revise the section 8.6.mRejectedvby comment 250w Superceded 2006/09/2129EEleanorFHepworthGMember^Technical (was Editorial)_5a2bXchange to "mobility extensions of 802.16" and change references to 802.11 to IEEE 802.11cqReferences to 802.16e should be removed as no such standard exists and references to 802.11 should be formalised d35g2218EEleanorFHepworthGMember^Technical, Binding_44`38a6.3.2bClearly specify what representation should be used for the network type information. The specification should either be an exhaustive list in this document, or a suitable reference to a list defined by another standard.cThe use of "for example" is inappropriate in the representation entry for TYPE_IE_LIST_OF_NETWORKS. The representation should be properly specified. d349g2241i Subir DasTechnical, Binding_44`38a6.3.2bClearly specify what representation should be used for the network type information. The specification should either be an exhaustive list in this document, or a suitable reference to a list defined by another standard.cThe use of "for example" is inappropriate in the representation entry for TYPE_IE_LIST_OF_NETWORKS. The representation should be properly specified. d349g2241i Subir Das Subir Das-wRejected 2006/09/21 2006/04/28MarkedEEleanorFHepworthGMember^Technical (was Editorial)_18`55a5.3.2bAdd clarification to text.cA1The example in brackets in confusing: "(e.g. BS or RNC or GGSN in 3GPP and PDSN in 3GGP2)". Does it mean GGSN in 3GPP, PDSN in 3GPP2, and BS or RNC in either? Or does it mean BS or RNC and GGSN in 3GPP, and only the PDSN in 3GPP2? If the latter, is it not possible for the BS to act as a PoA in 3GPP2? 1d137g2227v Related to comment 142, 128, 226wDeferred 2006/08/29 2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_30`36a5.6.1bUpdate section.cThis section should describe all media specific SAPs shown in Figure 12, not just a subset of them. It may also be clearer to combine the M_SAP and C_SAP under a general 802.16 type of heading. d218g2232vby comment 212w Superceded 2006/08/29 2006/04/28EEleanorFHepworthGMember^Technical, Binding_42 *kI agree with the notion, however, not clear about the suggested remedy. Is there an alternative standard? Also there is a comment (#350) on removing "for example" mRejectedvby comment 348w Superceded 2006/09/21 2006/04/286EEleanorFHepworthGMember^Technical, Binding_44`58a6.3.2b\Specification should be added, even if this is just an xref to later IE format descriptions.cJThere is no specification for the representation of the LIST_OF_OPERATORS.d360g2243vg2243v.21 to provide horizontal handover capability for all media specific access networks (i.e. inter-BS handover in 3G networks in not a focus of this work). The exception to this is inter-ESS handover for IEEE 802.11, this should ne stated more explcitly. d317g2236v By vote 1-4wRejected 2006/08/21 2006/04/28EEleanorFHepworthGMemberg2236v By vote 1-4wRejected 2006/08/21 2006/04/28EEleanorFHepworthGMembererererd349TScbe"W"W"W"WEEleanorFHepworthGMember^Technical, Binding_47`25a6.3.2bCChange to "a media specific information request/response primitive"ing existing Networks IDs defined elsewhere (IANA). Investigate having a Network Subtype IE which can include all the network standard amendments. For example for 802.11, this would include (.a, .b, .e, .g, .i, .k, .n and so on). Doing it this way may allow us to delete certain other IEs such as IE_POA_MAC_TYPE, IE_POA_PHY_TYPE, etc. Roaming partners (which opeBrator is specified here?). For security specify cipher suites and authentication methods. QoS: Investigate using media independent parameters such as delay, jitter etc. defined in (Ulises et al) QoS contribution. Cost: Investigate QoS based cost?? wDeferred 2006/09/20 2006/04/28Marked6EEleanorFHepworthGMember^Technical, Binding_47`25a6.3.2bCChange to "a media specific information request/response primitive"hould be used.d380g2247v0g2247vVvSince we are not aiming in the present state on routing\forwarding algorithms at MIHF protocol level, actually there is no need of a destination MIHF-ID.wRejected 2006/09/21 2006/04/28WE YoshihiroFOhbaGMember^Technical, Binding_115`19a8.3.3.1bD- Change the size of opcode to 2. - Change the size of AID to 10. c+Size value for Opcode and AID is incorrect.d743g2385vby comment 741w Superceded 2006/09/21 2006/04/28Table 18XE YoshihiroFOhbaGMember^Technical, Binding_115`30a8.3.3.1b-Remove Number of Address Header Identifiers .c3Number of Address Header Identifiers is not needed.d745g2386vby 744w Superceded 2006/09/21 2006/04/28Table 18YE YoshihiroFOhbaGMember^Technical, Binding_118`65a8.4.1b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc*TLV for Link Identifier should be defined.d774g2374iWolfgang Grtingng Grtingng Grtingng Grting 2006/04/28cOSentence saying "a specific information request/response primitive" is unclear.d389g2249vIt's unclera if the request/response primitive needs to be media independent. You cold still do this using MIH protocol and by using link specific primitive Please refer to contribution in 21-06-0675-02-0000-LB-issues-sriniwAccepted-Modified 2006/09/21 2006/04/28dallow us to delete certain other IEs such as IE_POA_MAC_TYPE, IE_POA_PHY_TYPE, etc. Roaming partners (which opeBrator is specified here?). For security specify cipher suites and authentication methods. QoS: Investigate using media independent parameters such as delay, jitter etc. defined in (Ulises et al) QoS contribution. Cost: Investigate QoS based cost?? wDeferred 2006/09/15 2006/04/286EEleanorFHepworthGMember^Technical, Binding_47`25a6.3.2bCChange to "a media specific information request/response primitive"primitive"Deferreded 2006/04/28Marked6pEEleanorFHepworthGMember^Technical, Binding_47`46a6.3.3b"Define an extensibility procedure.cAHow is extensibility managed for the Information Elements Name Space? What specification needs to be provided to allocate a new Information Element? Who manages the Identifier space? Behaviour in the case of receiving an unknown identifier must also be defined.d396g2250vby comment 384w Superceded 2006/09/21 2006/04/287EEleanorFHepworthGMember^Technical, Binding_47`27a6.3.2bQClarify that IS services could be performed before authentication and attachment.e of receiving an unknown identifier must also be defined.d396g2250vby comment 384w Superceded 2006/09/15 2006/04/287EEleanorFHepworthGMember^Technical, Binding_47`27a6.3.2bQClarify that IS services could be performed before authentication and attachment.ttachment.ttachment.cText says "After authentication and association to a certain PoA, ...". This appears to only apply to ES and CS. It may be possible to use IS before authentication.d392g2252vLWE accept this in principle. But there is no suggested text, hence rejected.wRejected 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_47`57a6.3.3bRRemove 2 bits from the 14 bit ID? Add explanatory material to the comment column.ce0x2 + a 16 bit OUI + a 14 bits ID = 34 bits. Also, the comments for the 14 bits ID need to be added.d400g2253i Subir Dask3The reason is not clear. 0x2 +16+14 = 32 bits.....mRejectedvEBeing handled as part of comments 384, 396 in Comment Assignment Listw Superceded 2006/09/21 2006/04/287EEleanorFHepworthGMember^Technical (was Editorial)_48`30a6.3.4b0Clarify the relationship between these sections.cections.cections.cmber87EEleanorFHepworthGMembererererd392^technicalbindingVVVVVVVVVVVVVV V V VVVVVVVVVVVVVV V!V"V$V%V&V(V+V,V.V/V0V1V2V3V4V5V9V:V;V<V=V@VAVBVCVDVEVFVGVHVIVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhVjVkVlVmVnVtVuVvVwVxVyVzV{V|V~VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV> ^bindingWWWWWWWWWWWW W W WWWWWWWWWWWWWW W!W"W$W%W&W(W+W,W.W/W0W1W2W3W4W5W9W:W;W<W=W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWjWkWlWmWnWtWuWvWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW ~cA"Relationship between table 6 and section 6.3.4.1 is unclear and confusing. e.g. for TYPE_IE_NUMBER_OF_OPERATORS it looks as though there are contradictory lengths specified. Also, the representation and encoding information seems to be distributed across multiple sections of the document."d406g2255vby comment 361w Superceded 2006/09/21 2006/04/28MarkedEEleanorFHepworthGMember^Technical, Non-binding_43a6.3b(Add a more detailed informative section.cA'In general, it is not clear from the current draft how this information could be used/why some IEs are useful etc. The draft would benefit from more descriptive text to aid understanding of why certain pieces of information are useful (e.g. in some sort of more detailed informative section). 'd324g2257vrNo available suggested text. Comment assigned for further work and other future contributions in the related area.wRejected 2006/08/29 2006/04/28EEleanorcisNWOWPWQWRWSWTWWWXW\WdWeWfWiWkWlWoWpWrWtW{W|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#W!W!W!W!W!W!W!W!W!W!W!W!WWWWWWWWWWWWWWWWWW$cthe1sttwosentencesintheparagraphrepeatswhathasalrevVthe2ndoctetitselfdoesnotrepresentthetotalsizeofthVthe802.21standardspecifiesthemeansforsecurityinformaVtheaboveframestructuremayalsobeusedwithastandardlpVtheassignmentofistoanyinformationelementshouldnotboVtheclientmayalsohavelocalinformationfordifferentavaVthecommandmihconfigurethresholdsshouldallowtodefineVtheconceptsofposandnon-posarenotusedanywhereelsei V VFHepworthGMember^Technical, Binding_50`31a 6.3.4.2.3b*Add more detail to the Cost IE definition.cA~Unclear whether duration is period over which the const information is valid or whether it is the duration of service provided per unit cost. The cost IE only allows for time based services not network traffic quantity based services. Some services charge different amounts for the first n minutes - how is this represented? No actual format of the cost information is specified.~d422g2258vby comment 419w Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_52`19bAdd more detail to table 11.c{Information in table 11 is not detailed enough to support implementation. e.g. what unit is altituderesolution provided in?d429g2259v*Adopt text from 21-06-0721-00-0000-Issue41wAccepted 2006/09/21 2006/04/2811EEleanorFHepworthGMember^Technical, Non-binding_54`6a 6.3.4.3.6 6.3.4.3.66RDbremovesecondinstanceofdefinitonofmnVremovesection1.6ܛVremovesection5.3.2andpossiblymoveittoannexrenaming<Vremovesection5.8orincludeasinformativenVremovesection6.3.6uVremovesection6.3.8jVremovesection7.2.3.1andtable16kVremovesection7.4.14gVremovesection7.4.15.3andreplaceitwiththeappropriatlyNVremovesection8.3.2.3UVremovesections7.4.15.3.27.4.15.3.37.4.15.3.4{Vremovesections8.5.3.19and8.5.3.20iViVÃypÃyrÃzsÃz Ãz0Ãz@qÃzPtÃz`|ÃzpfÃz ÃzrÃzÃà ݲÃ0 Ã@vÃPwÃ`ÃprÃێÃÃÃ&à gÃ0Ã@ÃP Ã`ÃpÃUÃxÃÃà Ã0VÃ@ÃPÃ`ÃpݵÃÃ۔ÃÃà Ã0Ã@ÃP'Ã`ܑÃpÃVÃ;Ã}- 'cvbycomment369Vbycomment380Vbycomment384Vbycomment401*Vbycomment415Vbycomment419Vbycomment424,Vbycomment433-Vbycomment460Vbycomment462Vbycomment473VVbycomment480rVbycomment482VVVbycomment483VVbycomment495]V_V`VaVbVcVdVVVVVVVbycomment495updateasperresolutionofhandovercommandsVbycomment500Vbycomment527626BVCVDVEVFVJVbycomment527/626KVOVPVRVSVTVYVZV[V]V^V_V`VaVbVcVdVeVfVgVhVbycomment737;Vbycomment741WVbycomment752/756+Vbycomment752/756bycontribution21-05-0671-00-0000-821-fVbycomment803Vbycomment892VV5V6Vbycommment527/626LVbyresolutionofcomment346Vbyvote1-4V kABSince TLV and XML/RDF are functinally different in that TLV does not support semantic query in general while XML/RDF does, the two ways of data representation are needed. There should be no inconsistency in high-level data definitions while the detailed data representation definitions can be different between the two.BmRejectedvgBoth data representation formats need to be provided as options due to differences in query mechanisms.wRejected 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_63`9a7.1.1bcInclude a mention of these, even if is to state that they are not considered further at the moment.c9Section 7.1.1 does not mention the LSAPs for wired media.d484g2262vby comment 483w Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_64`12a7.1.1b Move table to informative annex?ive annex?ive annex?EEleanorFHepworthGMembererererd458 EEleanorFHepworthGMember^Technical, Non-binding_59a6.3.8cHaving two normative definitions (TLV, RDF/XML) of the data representation may lead to potential conflicts and inconsistencies - is it possible to decide on one?d458g2261iYoshihiro Ohbakmean WEP, WPA, WPA2...?d437g2260vNo suggestion provided for a remedy. RFC 3268 lists all cipher suites for TLS. NIST also has alist that is pretty comprehensive. wRejected 2006/09/15 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_59a6.3.8cHaving two normative definitions (TLV, RDF/XML) of the data representation may lead to potential conflicts and inconsistencies - is it possible to decide on one?d458g2261iYoshihiro Ohbakiro Ohbakvby 516w Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`1a7.3.9b#Revisit parameters used by Link_Up.cAwSlightly confused, if link up goes from Link Layer to MIH, how is the link layer supposed to discover information about IP renewal indicators and mobility management support. If this is opaque data that is discovered using L2 mechanisms, it should be passed as opaque data across the SAP - the link layer should not have to interpret this information to pass it to the MIHF.wd529g2265i Ronny KimkSome technology like 802.16 has trigger for IP renewal. If this information is received we need to deliver it to MIH. Because not all media dependent technology supports IP renewal trigger, this is why IP renewal parameter is optional. mRejectedv(Add a comment in Link Up to that effect.wRejected 2006/09/21 2006/04/28dEEleanorFHepworthGMember^Technical, Binding_74`9a7.3.9cNot clear why this table is here for the C_SAP, but equivalent information is not included for the other SAPs. Is this information just informative? d487g2263i Ronny Kimj?Need to decide how to handle 7.2.1 media dependent SAPs first. kIf we don't need to have sections about existing SAPs and primitives in media dependent specifications, I recommend to move 7.2.1 to annex. Otherwise we need keep this section with other media dependent sections. mRejectedwRejected 2006/09/21 2006/04/2813EEleanorFHepworthGMember^Technical, Binding_73`35a7.3.9bFRevisit parameters used by Link_Up for identifying access routers etc.cMAC Address is not suitable for all media. Also; how are technologies such as 802.3ad (where one or more interfaces can share a MAC address), IEEE 802.11p which can generate MAC addresses on the fly, and VLANs represented to the higher layers?d526g2264iMathieu Peressej2Related to most of Yoshihiro's comment on Link IDs^technicalWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWWWWW W!W"W#W$W%W&W'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W7W8W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWbRemove SIP from list.cIt is difficult to envisage a scenario where SIP is supported in the PoA. SIP proxies may be placed in the network somewhere, but one support by the PoA is not required in quite the same way as it is for MIP.d530g2266w Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_74`45a7.3.10.1bHRevisit parameters used by Link_Down for identifying access routers etc.cMAC Address is not suitable for all media. Also; how are technologies such as 802.3ad (where one or more interfaces can share a MAC address), IEEE 802.11p which can generate MAC addresses on the fly, and VLANs represented to the higher layers?d532g2269iMathieu Peressej2Related to most of Yoshihiro's comment on Link IDsw Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_77`32a7.3.13.1b1Would consider removing Link Type as unnecessary.ccessary.ccessary.cݒp^0522-06 not found on the doc server - Yoshi provided the missing file (in 2006/07 folder now)vBAdopt suggested change [1] in 21-06-0522-06-Session_Identifier.docwAccepted-Modified{k) done 2006/09/21 2006/04/28ݓE YoshihiroFOhbaGMember^Technical, Binding_43`39a6.3.1bGAdopt suggested chages described id 21-06-0609-IS_Multihop_Scenario.docc*IS multi-hop scenario should be described.d330g2382i Vivek GuptakAThis should be true for events and commands as well. A transaction between two MIHF nodes is completely independent of any other trnsaction between any other MIHF nodes. Not sure if this needs to be specifically needs to be explained in context of IS services or in a more generic sense.mAccepted-Clarifiedp21-06-0609-IS_Multihop_Scenario.doc not found on the official server - used 21-06-0609-00-0000-IS-Multihop-Scenario-alt.ppt, per instruction by the commentervommentervTTTTTTTTTTTTTTT vcomment104Vcomment492Vcomment495^Vcomment527/626QVcomment90hasbeenacceptedandthatupdtaestheqosrelatetVcommentisunclearastospecificallywhatpartisunclear:VcommenterWwWxWyW{W}W~WWWWWWWWW1W8W?W\W~WcommenterneedstoclarifythismoreVcommentertoprovidesuggestedtext?Vcommenter'szWcommentertoprovidesuggestedtext?Vcommenter'szWzW cANot clear why Link Type is included in the Link Detected primitive. What does this represent; link type in terms of technology, or link type in terms of which PHY/channels are used etc? This boils down to an architectural question - can multiple technologies reside under the same MIH_LINK_SAP (so the example if GPRS and UMTS under a single MIH_3GLINK-SAP) and if so - since all the decisions about moving betwen these technologies are decided under the SAP (and hence out of MIHF and upper Blayer control) why should the changes be visible to higher layers as anything more than changes in bit rates, QoS, other link characteristics etc.?d545g2270vKlinkType does NOT apply to PHY channel but actual link layer technologies. wRejected 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_80`1b!Revisit whether this is suitable.suitable.KcWhy is HO-Type useful? Higher layers might care about changes to link characteristics, or that the link type has changed, but not about the HO-Type - what is the higher layer supposed to do with this information?d596g2273vThat is useful information...wRejected 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_88`9bClarify definitions.cNETWORK_TYPES: relationship to previous networ type definitions in table 6 is unclear. In general it is also useful to specify this in one place and refer to it in the tables (e.g. this applies to duplicated information in 7.4.5.2.4 and 7.4.7.1.4)d606g2274vno suggested text.wRejected 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_88`47a7.4.6bClarify MIH_SWITCH operation.ceration.cation.cMATION_SOURCE field is useful.Bd564g2272v)No remedy suggested. Identified as issue.wRejectededed 2006/04/28Marked qEEleanorFHepworthGMember^Technical, Binding_86`5b/Remove HO-Type; possibly add link type instead?xt.cABGenerally don't understand what the purpose of this primitive is and what it's scope is. 7.3.18.1 states this is used by the link layer to retrieve values, this seems to be contradoicted by 7.3.18.3 that states the primitive isgenerted by an upper layer entity. It's not clear why the INFORMATION_SOURCE field is useful.Bd564g2272v)No remedy suggested. Identified as issue.wRejected 2006/09/15 2006/04/28EEleanorFHepworthGMember^Technical, Binding_86`5b/Remove HO-Type; possibly add link type instead?g2272v)No remedy suggested. Identified as issue.wRejected 2006/09/15 2006/04/28EEleanorFHepworthGMember^Technical, Binding_86`5b/Remove HO-Type; possibly add link type instead?e instead?e instead?EEleanorFHepworthGMember^Technical, Non-binding_53`51bClafiry text as above.cAssume the reference to Diameter is actually a pointer to how the IP address information should be formatted as a TLV? If so, this should be clarified. d433g2281v*Adopt text from 21-06-0722-00-0000-Issue42wAccepted 2006/09/21 2006/04/2812 EEleanorFHepworthGMember^Technical, Binding_54`48b;Define migration strategy as new link types are introduced.cHow are the 'link type' parameters lists updated, as new technologies become available? Will the 'link type' parameter have some sort of version control, so that interoperability between different updates is maintained? d440g2284v0g2284vnk types are introduced.cHow are the 'link type' parameters lists updated, as new technologies become available? Will the 'link type' parameter have some sort of version control, so that interoperability between different updates is maintained? d440g2284v  ~vAGAdopt the contribution 21-06-0749-00-0000-Issue 47-Link-ID Some MIH primitives may refer to multiple link layer technologies. So there needs to be careful examination of all primitives where this needs to be added. Identified as an issue and listed in list, to be worked upon. Rejected since there is no definite/clear remedy.GwAccepted 2006/09/21dechnical, Binding_54`48b;Define migration strategy as new link types are introduced.cHow are the 'link type' parameters lists updated, as new technologies become available? Will the 'link type' parameter have some sort of version control, so that interoperability between different updates is maintained? d440g2284 are introduced.cHow are the 'link type' parameters lists updated, as new technologies become available? Will the 'link type' parameter have some sort of version control, so that interoperability between different updates is maintained? d440g228440g2284 EEleanorFHepworthGMember^Technical, Non-binding_59`43bOExtra text is required here to clarify the purpose and operation of the schema.cThis section does not actually explain what this schema is really used for. A definition of a schema is given, but its use is not very clear. d462g2285i Subir Dask/Agree that more clarifying texts rae required. m Supercededvby 460w Superceded 2006/09/21 2006/04/28 EEleanorFHepworthGMember^Technical, Binding_110`8a8.1bRequire large message support from the underlying transport. This would be simple in the IP case where standard transport protocols exist to handle this eventuality. c`8a8.1bRequire large message support from the underlying transport. This would be simple in the IP case where standard transport protocols exist to handle this eventuality. cuality. cuality. cat interoperability between different updates is maintained? d440g22848484 2006/04/28:g^_`abcd€€€€€q EEleanorFHepworthGMember^Technical, Non-binding_110`27a8.1b!Suggest to delete this sentence. cssages (i.e. which are too large to fit in a single L2 or L3 datagram). For example, it is not clear whether the MIHF is responsible for fragmenting to a single datagram or whether the underlying transport is supposed to do this, how the frame format handles concatenation, what algorithms should be used for retransmission and reassembly (including the handling of partly reassembled messagesB3), how the maximum fragment size is established. !d680g2288iWolfgang Grtingj7agreed: Fragmentation is handled by transport protocolskQtrasport protocols like TCP or 802.11 MAC have their own methods for fragmenting.wDeferred 2006/09/15 2006/04/28 EEleanorFHepworthGMember^Technical, Non-binding_110`27a8.1b!Suggest to delete this sentence. cntence. c  cAThe use of unreliable transport may in fact lead to significant inefficiencies and increased latencies unless extremely sophisticated algorithms and protocols are used at the application layer (thereby essentially replicating the transport layer in the application layer). Areas where a standard transport layer could provide advantages over the techniques considered here include: piggybacking of acknowledgement semantics on arbitrary reverse traffic; windowing allowing multiple outstanding Botransactions in a congestion safe way; adaptive RTT measurement which allows retransmission in a congestion-safe way; concatenation of several small messages into single tranmissions; guarantee of transaction ordering (if this is required); efficient transport of large messages which require fragmentation (by partial rather than full retransmission); and so on. ]d684g2289v3Not clear what sentence is being talked about here.wRejected 2006/09/21 2006/04/28 ?EVidalFAlbertGMember^Technical, Non-binding_130`65a8.5.2.5bA8.5.2.5 MIH_Link_Up Indication This notification is delivered from MIHF in the PoA to MIHF in the network when a layer 2 connection is successfully established with mobile node. ---------------------------------------------------------------------------------------------------------------------------- | Name | Type | ---------------------------------- Type | --------------------------------------------ZcZcZcZXcZXcZXcZXcZXcZXcZcZcZXcZXcZcZcZXcZXcZZ8Q 2006/09/21 2006/04/28RE YoshihiroFOhbaGMember^Technical, Binding_99`46a 7.4.12.1.2b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc;MacNewPoA is not needed if it is part of NewLinkIdentifier.d646g2358vby comment 527/626w Superceded 2006/09/21 2006/04/28MarkedMarkedSE YoshihiroFOhbaGMember^Technical, Binding_103`51a 7.4.14.1.2b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc?MacMobileNode is not needed if it is part of NewLinkIdentifier.d652g2359vby comment 527/626w Superceded 2006/08/29 2006/04/28TE YoshihiroFOhbaGMember^Technical, Binding_105`11a 7.4.14.2.2b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc?MacMobileNode is not needed if it is part of NewLinkIdentifier.d656g2360i Vivek GuptakBy Comment 652m Supercededvby comment 527/626w Superceded 2006/08/29 2006/04/28UE YoshihiroFOhbaGMember^Technical, Binding_113`21a8.3.2a[ KLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ဃ၃ႃჃᄃᅃᆃᇃሃቃኃዃጃፃᎃᏃᐃᑃᒃᓃᔃᕃᖃᗃᘃᙃᚃᛃᜃᝃឃៃ᠃ᡃᢃᣃᤃ᥃ᦃᧃᨃᩃ᪃᫃ᬃᭃᮃᯃᰃ᱃ᲃ᳃ᴃᵃᶃ᷃ḃṃẃểἃὃᾃῃƒÃăŃƃǃȃɃʃ˃̃̓΃σ#"""""""""""""""""""""""""""" 4IEEleanorFHepworthGMember^Technical, Binding_112`53a8.3.1 to or avoid congestion events except as provided by the underlying transport. In particular, there is no mechanism to prevent the initiation of large numbers of parallel transactions, and the retransmission timeout is not adaptive (there is no backoff). This may be acceptable for operation of the MIHF protocol between nodes which directly connected over a single link which has native overload control; however, it would not be anB acceptable approach for operation over IP networks in which congestion in intermediate nodes is not visible. The lack of rate limitation and the non-adaptiveness of the retransmit timer means that the protocol has no way to avoid causing congestion events. d708g2292v0need text for such a comprehensive issue, see 32wRejected 2006/09/15 2006/04/28EEleanorFHepworthGMember^Technical, Binding_112`53a8.3.153a8.3.1708 2006/04/28O EEleanorFHepworthGMember^Technical, Binding_112a8.3bHRedraw the figure to indicate all possibilities (or delete the figure). cAcThe diagram implies that any non-L2 transport will run directly over IP. However, even in the unreliable transport case, transport over UDP is also quite possible (p111 line 16 mentions both). This appears to be a question of transport selection for the non-L2 case, which is apparently not considered in great detail in the remainder of the document. cd697g2291i Qiaobing Xiejdelete the figuremAccepted-Modifiedvsee 704w Superceded 2006/09/21 2006/04/2824EEleanorFHepworthGMember^Technical, Binding_112`51a8.3.1b~Include guidelines on rate limitation and timer adaptation for retransmissions, or use a transport which is congestion-safe. cafe. cbvProvide RTT estimation algorithms or rely on the underlying transport to carry out RTT estimation and retransmission. cAThe document provides no algorithms for RTT estimation. The RTT estimation algorithm may need to take into account several subtle issues: whether to use all responses for RTT estimation or just 'pure Ack' responses (given that the application processing time for other responses may be non-trivial); how to disambiguate responses to retransmissions from responses to the original message (mis-correlation may lead to significant over/under estimation of the true RTT); how to track the RTT overB time, given that network conditions may change and even the link type may change in a way which is not visible to the initiator (e.g. if the initiator is deep in the network). d709g2293vNot considered relevant to scheduled network segments such as many wireless media, plus out of scope. Leav it to transport or MME.wRejected 2006/09/21 2006/04/28 5~EEleanorFHepworthGMember^Technical, Non-binding_113`1a8.3.1cANote that alternative underlying transports would allow the ack-bit semantics to be piggybacked on other return traffic which would be more efficient. In addition, if a receiver takes the option to handle most acknowledgements by returning the ack by setting the ack bit in a response packet, there may be no dedicated acknowledgements generated which allow the sender to carry out RTT estimation. d713g2294v21-06-0741-00-0000-Suggestions about Piggyback Acknowledgement.... ..the proposed remedy is quite complex and cost benefits are not adequate for this suggestion. This is a requirement for the underlying transport and NOT for MIH Protocol. Noted duly. wRejected 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_113`15a8.3.115a8.3.1e an algorithm for duplicate packet detection or use a transport which reliably eliminates duplicates.  zvwith!W#W4W=W?WnWWwithinZWݓWWwon'tݓWword4WdWWwordheterogeneouswasdeletedbyanothereditorialcommentVwordingWworkZWW W!WworkedWWWwould۳WWWWWwriteWwrongWwwwHWxml/rdfWyoshiZWyouWWzeroށWރWwaccepted $()+@ACDGKLOP^cdehipsvwۀۃۄۉۋێې۴۶ۼ۽ƒʃуۃ܃#$,:;ABCNSTUVWYZ]`hkm|܂ܑܒܓܔܕܖܚܛܭ΃Ѓ҃߃'+13AEHLOPRabkzݍݎݓݔݕݖݗݘݛݵݺݽݾʃ   8.3.1.1.1d716 2006/04/28EEleanorFHepworthGMember^Technical, Binding_113`43a8.3.2.1b7Provide a concrete extensible syntax for the MIHF ID. csaction has any mechanism within the protocol for ensuring that the transaction is invoked exactly once or not at all. The rules for filtering duplicate transactions seem to operate only within a simple time window and to be optional to implement at the receiver, and are presumably allowed for efficiency rather than protocol correctness. d715g2298vIssue 34wDeferred 2006/09/15 2006/04/28EEleanorFHepworthGMember^Technical, Binding_113`43a8.3.2.1b7Provide a concrete extensible syntax for the MIHF ID. cHF ID. ccitly that the protocol cannot guarantee that a transaction is invoked at most once. ccd715 2006/04/28 =cAProvide a reference to the place in the document where the registration process is actually defined. Otherwise it is unclear how to manage the Session ID space (e.g. how to manage deregistration). Registration messages are apparently only defined for particular event types. d725g2300v#by comment 719 that defines MIHF IDw Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_113`65a8.3.2.2b1Provide a concrete syntax for the session ID. . cNMaximum length of the session id (and other syntax aspects) are not defined. d727g2301vby comment 719w Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Binding_114`4a8.3.2.3bEDefine the syntax of the transaction id including allocation rules. crules. crules. che MIHF ID. c3`60a8.3.2.2b7Provide a concrete extensible syntax for the MIHF ID. cccd725 2006/04/28 cAThe uniqueness of the MIHF ID is not clear. For example, it is not clear why uniqueness is important and whether it is important to the sender or receiver of a message; in particular, it is not clear how the scope within which the MIHF is unique is decided and how it is conveyed in the message (implicitly or explicitly). Also, the maximum length of the MIHF ID is not defined but this will clearly have a significant effect on message size.d720g2299vDby comment 719...which explains the uniqueness aspects of MIHF ID...w Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_113`60a8.3.2.2b7Provide a concrete extensible syntax for the MIHF ID. cHF ID. c 9,EEleanorFHepworthGMember^Technical, Non-binding_118`6a8.4b cIt would be helpful to have a discussion of padding/alignment issues (e.g. are messages and information fields only byte aligned and not word aligned). d766g2309v#no suggested remedy. Issue assignedwRejected there an implicit assumption of time-of-day synchronisation between devices? d755g2307vno suggested textwRejected 2006/09/19 2006/04/28MarkedEEleanorFHepworthGMember^Technical, Non-binding_118`6a8.4b cIt would be helpful to have a discussion of padding/alignment issues (e.g. are messages and information fields only byte aligned and not word aligned). d766g2309v#no suggested remedy. Issue assignedwRejected4b cIt would be helpful to have a discussion of padding/alignment issues (e.g. are messages and information fields only byte aligned and not word aligned). d766g2309v#no suggested remedy. Issue assignedwRejected6/04/2828 9 cAThe syntax and semantics of the transaction ID are extremely unclear. It is not clear if transaction IDs are allocated sequentially or randomly; if the former how wraparound is managed, if the latter how out of order transactions are identified (if this is a requirement). d730g2302vby comment 719w Superceded 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_114`9a8.3.2.3b cThe fact that the TID is in the fixed header means that in fact it is present in *all* messages. Does this mean it is significant in all messages (even, for example, unacknowledged messages which do not form part of a structured transaction?) d732g2304vno suggested remedy TID is significant only when there is a response. Add the following in section 8.3.3.3. In messages where Transaction ID is not required it is set to 0.wAccepted 2006/09/21 2006/04/28EEleanorFHepworthGMember^Technical, Bindingl, Bindingk)No proposed correct call flow this time. mRejectedv$no suggested text. Issue identified.wRejected 2006/09/21 2006/04/28299d where the boundary between the two number spaces lies. d769g2310v#no suggested remedy. Issue assignedwRejected 2006/09/15 2006/04/28 2006/04/28MarkedEEleanorFHepworthGMember^Technical, Binding_118`28a8.4b?Provide extensibility rules for allocation of new type numbers.cIt is entirely unclear how protocol extensibility is handled for these various number spaces. For example, if a new information element is defined, how is the receiver to determine what to do with unknown types (drop, ignore, reject message, etc.) d770g2311v"no suggested text. Issue assigned.wRejected 2006/08/29 2006/04/28EJunFHiranoGMember^Technical, Binding_113`55a8.3.2.2bDefine it properly.cO"Session" is not defined anywhere. Thus Session ID does not make sense at all.d723g22112vby comment 719w Superceded 2006/09/21MarkedEFarrokhFKhatibiGMember^Technical, Binding_3`42a1.2bRemove "technology-independent"cAThe MIH SAP is not technology-independent. For example, the MIH_Link_Handover_Complete.indication primitive has the OldMacMobileNode paramater, which is of type MAC Address. However, the MAC address of an MN is highly technology-dependent. No mechanism has been defined in this document to make MAC addresses technology-independent, thereby requiring MIH SAP users to be aware of the details of the link technologies. d17i Hong ChengjAThe MIH SAP should be technology independent. However, the contents of certain IE passed through the SAP may need to be interpreted winthin certain context. This doesn't make the SAP itself technology independent, as long as the SAP is not bound to certain specific technology. For example, if the SAP can support all types of MAC addresses, it should not be classified as technology dependent.vnosuggestedtextV3VXvnosuggestedremedyissueassignedVVnosuggestedtextVVVVVV jmRejectedvRefer to comment 102. wRejected9Adopt any clarifying text from comment 102 (Group Notes). 2006/09/21EFarrokhFKhatibiGMember^Technical, Binding_4`34a1.6bCRemove the paragraph associated with item (1): "An implementation"cAIt is impossible to test compliance with abstractions, such as primitives and SAP's. It IS possible to test compliance with concrete API's. However, this document does not address API's. It is impossible to test compliance of formats when the formats have not been defined. d32v by comment 31w Superceded 2006/09/21 EFarrokhFKhatibiGMember^Technical, Binding_16`1a5.3.1b$Remove concepts of PoS and non-PoS. con-PoS. con-PoS. cchnologies. d17i Hong Chengjd17i Hong ChengjjjmRejectedKc- OldMacMobileNode and OldLinkIdentifier should be replaced with one unified LinkIdentifer TLV. - NewMacMobileNode and NewLinkIdentifier should be replaced with one unified LinkIdentifer TLV. d595g2351vby comment 527/626w Superceded 2006/09/21 2006/04/28MarkedLE YoshihiroFOhbaGMember^Technical, Binding_88`25a 7.4.5.2.4b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccNETWORK _ID should be LINK_IDd607g2353vby commment 527/626w Superceded 2006/08/29 2006/04/28ME YoshihiroFOhbaGMember^Technical, Binding_91`46a 7.4.7.1.4b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccNETWORK _ID should be LINK_IDd625g2354i Vivek GuptakBy Comment 607m Supercededvby comment 607w Superceded 2006/08/29 2006/04/28NE YoshihiroFOhbaGMember^Technical, Binding_92`2a 7.4.9.1.2b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc-Link Identifier is missing in the parameters.d626  cA.The concepts of PoS and non-PoS are not used anywhere else in the document, and add no value. Whether MIIH information is communicated directly between an MN MIHF and a network MIHF or not is a transport issue. 802.21 does not need to differentiate the two, and it doesn't, except for in this section. .d111i Qiaobing XiemRejectedvSection 5.3.1 refers to General Architecture and not everything in General Architecture may be referenced in other parts of the document. MIH PoS is referenced on page 55, line 14 as well (Draft ver D1.0). wRejected 2006/09/21!EFarrokhFKhatibiGMember^Technical, Binding_19a5.3.2bRemove FA, HA, H-AAA, V-AAA. Remove all Visited Core Network clouds, and rename "Home Core Network" to "Visited/Home Core Network"ctwork"c jMIH SAP should be technology independent. However, the contents of certain IE passed through the SAP may need to be interpreted winthin certain context. This doesn't make the SAP itself technology independent, as long as the SAP is not bound to certain specific technology. For example, if the SAP can support all types of MAC addresses, it should not be classified as technology dependent.WTcismulti-hopscenarioshouldbedescribedݓVisnasacryonymcorrectV