Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0f)binformation@/cthetwostacksinthefigureareidentical@@0@00agraphrepeatswhathasalre@@0@0ragraphrepeatswhathasalre@@0andotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@?@ABCDEFGHIJKLMNOPQRajoy//////////////////////////////////////////////////////////////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'dݒvwe the suggested Annex A-2 in the proposal: 21-06-0xxx-00-0000-WLAN_WMAN_HO_Procedures.doc vwouter Advertisement is encapsulated.@AR 33   % 33Rvwnterested folks to resolve issues. What are the benefits of these parameters? Should they really be in MIH or can some other layer decide what to do about these? Add a use case showing how these parameters can be clearly used. Is this End to End QoSBt or just Access Network/Link-level QoS? If Comment 90 is deferred/rejected then comment 93 may need to be accepted bh as delay, jitter etc. defined in (Ulises et al) QoS contribution. Cost: Investigate QoS based cost?? h as XML" , ^i Subir DasjmRejected{ 2006/04/3020SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDec D g7y:!I3 "Z22}o&  7/20/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&`wanghleiUwangEFarrokhFKhatibiGMember^ Editorial_22`22a5.4.3bChange "include" to "require"cImproved clarityd167 2006/07/20?EFarrokhFKhatibiGMember^ Editorial_22`46a5.4.3b3Change "Other IEEE groups" to "Some IEEE standards"cImproved clphrasingd174 2006/07/20@EFarrokhFKhatibiGMemberibiGMember^ Editorial_22`22a5.4.3bChange "include" to "require"cImproved clarityd167 2006/05/17?EFarrokhFKhatibiGMember^ Editorial_22`46a5.4.3b3Change "Other IEEE groups" to "Some IEEE standards"cImproved clphrasingd174 2006/05/17@EFarrokhFKhatibiGMemberFarrokhFKhatibiGMember/05/14K 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 r ABCDEFGHdIJ^K_L`MNaObPcQiRmSjTkUvVwWxXyYZ{[p\n]  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ۀہۂۃۄۅۆۇۈۉۊۋیۍێۏېۑےۓ۔ەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱۲۳۴۵۶۷۸۹ۺۻۼ۽۾ۿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃'f€aA Create and Submit Reply Comments @A*  33*€APLEASE FOLLOW THESE INSTRUCTIONS EXACTLY OR EXPECT TO HAVE YOUR INPUT IGNORED. (1) Read the comments. You will probably find this easiest if you use the "Comment List" layout. You can choose it from the upper left corner of this window, or you can use this push button: (2) When you want to respond to a comment, check the "Marked" box at the top of that record. Then fill out the following fields: Recommendation: Proposed Resolution: Reason for Recommendation: You are fully justifing the buttons:€gng the buttons:€gng the buttons:€gg the buttons:€gicking the buttons:€gicking the buttons:€gowing steps by clicking the buttons:€ging the buttons:€gg the buttons:€ging the buttons:€ge buttons:€gbmit Ballot Filef9Proceed with the following steps by clicking the buttons:€gO+ A#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# cBl#[  bl[##KK##;;# Bmv#+  @iv+# >j# Dkv# 8w5 €\]Page€^A_Line€`A aSection€bA cComment€dAe Comment #f Comment by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€pA€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yAzReason for Recommendation€A Group's Notes-Note: Group may also edit Comment Type above.€A€A &'()+ €A €A €A€ARecommendation@@ByProposed ResolutionReasonSee reply details€A Fig/Table# BNA^  !"#$%*,-./0123^^_`u EDE^ "Technical, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, BindingG OKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !""Technical, Binding" comments are permitted only with the vote "Disapprove". You may submit comments of type "Technical, Non-binding". Please correct and try again.H) W()=0 W ABCDEFGHIJK^L_M`NaObPcQvlEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf7# w  3  $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz    3  $,.YesNo/,  , : AM PM     w  $,.YesNo/,  , : AM PMw w  $,.YesNo/,  , : AM PMf"$  w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PM w $,.YesNo/,  , : AM PMf w $,.YesNo/,  , : AM PMf3IC dd5BDe5Bf#= q w $,.YesNo/,  , : AM PM     w $,.YesNo/,  , : AM PM          w  3  $,.YesNo/,  , : AM PM   {cTZbo|h[++ \_l)]l+ ^`l$)g_.?nAEditor's QuestionB GpA Editor's NoteB GvAResolution of GroupB GH vwADecision of GroupB GxAReason for Group DecisionB GyA Group's NotesB G{AEditor's ActionsB G€AGroup's Action ItemsB G€AEditor's Action ItemsB G€AVoterFirstNameB G€A VoterLastNameB G€A VoterEmailB G€A VoterPhoneB G€A VoterStatusG€A VoterStatus3m  ^ 3 $,.YesNo/,  , : AM PM_   `3 a d3 e3 f  3 g  3 t  3 u   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PMu   $,.YesNo/,  , : AM PM#39 XX+ASubmit Reply CommentsB  a   w   w $,.YesNo/,  , : AM PMf w w Aa#8 F mM5ft GM5ftM5ftGOC`E 7OC`EOC`E7 W   W   W    ÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷{xBKA Enter commentEQMAImport Global DataENALL # @ A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcdefghijklmnopqQNAExport CommentsE:NALL OFMPR$@` ABCDEFGdH^I_J`KaLbMcNQkUmVnWpXvYwZx[y\{]^_`abcdefgh`DTDTDT A B C DEFGHIJ^K_L`MaNbOcPdQgRiSjTkUmVnWpXvYwZx[y\{]^_`abcde/A^technical@b27@;addmoredetailtothecostiedefinition@dand@as@class@configured@'depending@figure@.from@@.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 j   3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM    3 $,.YesNo/,  , : AM PM    w  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   h stanwood# >S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PM(s%jAResolution ProposedB GkAReason ProposedB GmARecommendationB Gnndation 1B Gn1O RR 3  $,.YesNo/,  , : AM PMU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW w $,.YesNo/,  , : AM PMX w $,.YesNo/,  , : AM PM<@B@2@I?@p@ۃ@ۈ@ۖ@@4/@܄@ܞ@ @3|@@@6@-@ d@ތ@ޔ@ =@ @ @$P;$P; @$P;;;$P;d@B@2A@@@cJ@c@M @ @3P;@3P; @3P; @3P;7WNWWWYWbWdWeWhWWWWWWWWWWWWWW)W/W5W8W=W>WBWDW`WhWmWWWWWW?WgapWWWW WW#W$W%WgenerateWgenerated4W6WWWWgeneratingWgenericWgetOWWWgetridofdashthisisaproblemallthroughoutsection6.2OV4/ RM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMBkS-X bWmkwj,ACgEv@!Sl€`zrAPFQKRPSUTZUBN@VhA~@M@LZ<>C @@@FIH@JQ3^&vmBD€Qd9naD@Xbm{ACEe@EJoQTYB@X|CE@€ JOTYAC@XbmwBD@a@EJOU[B@|J& JQ 3 $,.YesNo/,  , : AM PMS   U   V   W   X 3 $,.YesNo/,  , : AM PMY   Z 3 $,.YesNo/,  , : AM PM[   \ 3 $,.YesNo/,  , : AM PM]   ]   No/,  , : AM PM]   1 RG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMw+#,v# 0x#  2 Ma bc dijkmvwxy!€€$€2'&()% @@@B s@A 3  $,.YesNo/,  , : AM PM77777777 7 7  7  7  7 7 7777777777771xy{€€€€€j77777777 7 7  7  7  7 7 7777777777771        Y7 ^ 3  $,.YesNo/,  , : AM PM_   ` 3  $,.YesNo/,  , : AM PMa   b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   6" i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   p  w  $,.YesNo/,  , : AM PMs 3  $,.YesNo/,  , : AM PMt   u 3  $,.YesNo/,  , : AM PMv   _ €Dtch of records in which you want to replace a field. *In browse mode, and put the cursor in the "Recommendation by" field. *Under "Records", choose "Replace". *Choose "Replace with calculated result". *In the box, write, in quotation marks, your name. Click "OK". *Click "Replace". @Af  ww    ww  ww  wwfSet up an email message for meGo to "Comment List" layout BnA€ (EQiaobingFXieGMember^ Editorial_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  33faPI3Import 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=A|benjamin@wfamolari@xgreg@9hongcheng@gmathieu@nada@nadagolmiemember@peng@1sanjeevUsrinivas@zulisesolvera@yoshihiro@'cheng@gupta@hepworth@kim@liu@skomra@Ktaniuchiއtxie@memberܖ92observer@hother@ j^bindingܑܕܖxܗܝy%ISeditorial@irw݅݉݋Y#non-binding@ thatisunique@yavisitedenterpriseenvironment@=acceptthechangestosection7.4.7.2.2asdescribedin21-0@uacross@-addanewsection7.3.1calledlinkeventid@adddiscussionabouttherelationshipormappingbetweenmih@Taddrefertotable26inannex4inthecommentsfield@aaggregates@8also@Fan@*2@E BD VOTEREMAILpDs`jA.nA%€B?€A€AC=jC@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$#J J#  al# cl#~  bl~# Bmv#n  @ivn# sj{#^ Dkv^# 8w#N,CjvN# 0x#>  2y># 2# . 6{ .# In #  qp # LF 8w#/,v/# 0/ Y w $,.YesNo/,  , : AM PMZ w $,.YesNo/,  , : AM PM[ w  $,.YesNo/,  , : AM PMabcd€€€€€€€€€€€€rQ RA 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMPR RF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMx+!  2y! 4z! 6QS RK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3 $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMRT RP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMT 3 $,.YesNo/,  , : AM PMSU RU  w $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY 3 $,.YesNo/,  , : AM PMTN OZ 3  $,.YesNo/,  , : AM PM[  3  $,.YesNo/,  , : AM PMA#x x#  # d#7 #7# ## ##  # ^#  _l#$  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€ ../////0 0 0  0  0  1 1 1112222233333%5$/%1 %3      &6 "$""! "&!$,  !#)#+-*,6{7TypeReason k b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PM-dG | w  $,.YesNo/,  , : AM PM}  w ~ w  $,.YesNo/,  , : AM PM  w  w  $,.YesNo/,  , : AM PM  w A^a):|+=9}R~T=b=NR?+M^ance'd303 2001/08/28G6AReply Comment LayoutB U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]     [A, HH HH*<*G!!!!!!!!1111111111 11 11 11 9999 99999999BBBBBBBBJJJJJJJJJJJJRRRRRRRRRRZZZZZZZZZZZZ ZZ!cccc"cc#cc$cc%kkkk&kkkk'kk(kk)kk*kk+ssss,ssss-ss.ss/ssB0{{{{1{{{{2{{3{{456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmZ\ Cnopqr!!s11tBBuRRvccwssxyz{|}~D[] Ek0>nk&8n]n]n!=700UnUnUfa&fH!1fQ!H,bH,Hn\X8FU7=nXnH7%fQH 7k=8HnX10kHbHHgfn=\HX7X8HHf\]?no`_`_`_`_`_`_`_`_`_`_`_`_`_`B]n` [    `    `    `n&0n4WUfZ _ZZZ._ Z)$')d)$')d\^ G)')$h#`` ) )B)y}_ Z ' ' Dyy3sy~[_  )  ) B|uv7~qu|t_Z ( ( Brz}rs9|pr}up|_ ` ) ) Bzprypq~<yppy~pps`_ ' ' @rpp{upp|?vppuvpzZ[ ) ) Ezpt}rppyAsppr}~pr_ _ ' 'Bqp|ypvB~qpyxpz[ ` ) ) BHxpvups@|ptqpr_ Z # #@qp~}rpq~Iypq|ypz_ _E BEB`E BEBmE 'BEBmxpvyp|SX&&Xvpqpr` [  A Z Zqpy8=SHHspzZ _  @  `  `xpv,5^kn~qpr_ [[  _Z`l[  __Yo[ 6__[oqpqrpsbfS=X|pvzpy_ _ ' ) Bxpq}wpq}=]_ IXU7Uyp{zqppq`_ ) ' Bqppq}~p{=TW\fvpr}qppxZ [ ' ) DwppsspxfgT0spw}qpq`  _  '  'A~ppszpu08]n%7~qpp~}qpxZ _ BBEBm BBEBm 'BBEBmvpsppsHQH|ps}qq` [ `  ` _~psvq}Dyz~sx_ _  Z  Z [Jvu|{9to_Z_o__[Z__[^o__[Z__[^o_[^Z_`Z^o~v }~o_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`m`                                                                             @lBB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB^` K@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@B_ fXX]XfkJ78H7k=aXH 007U!,7kX8HXU7TT8X7TX77XXXf77`QHU8bk1TnaXfgWU77L7%7XX\ n17&7nbT] Xb!78=HUUXWUTX7 X7TY07=\7Xk Q%QX777b]1n=5n7H8Q!8nn_a M7!Qn=!H% 7TX,XfUXn,7,a bHb7jn &HU\TX$WT878gnn8H W8L7AUXHn8nH,H88N 7X&78=;XT%X7=7&0&0n, n!7HX00T(TXfnn777 H8& X7T7778n XTX778Tbkb H=X!`b O=T TXM*HU7T7&Q= 7Tn7%UW& XTX.7,n7&H%H8,X7gn7 TXT7A78nXH&=TXf7&Q7 PXTX 8n7]&]n7TX8jUQ TXU=n7\gn3n7XHUk=7,+U XTWUH87nn3X8WU77f78 TXUn= 7ac QU7U78&QQ XUX bfb7==nX17!8717W177&7nUT TWTH8fX&k8UUn7771 XUX77j&W7 WX bR8nH7 TXT\7&XUkH8U U77TX XTXn%88=&gC!\7 WX 77nXTUnfXTagWUTgWUTi)())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())(be S))())RZ                                                    B'S66SmB3BmK63BmVEBBPE.R8|o" *e VK S) i )}=}t<  K o  e   '~tFxy}qx ZV V)Pe2 6V R `vs|zWX!Q{ps}qq  <JR 3` )  A~psuTq}84n]H5}qpp}}qpx  ) _e Z ' o xpsppr5dngspw}qpqm  l <. Vqps~yptk]gX=upqzpy  I: . i J  B )3Sxppq}spwU7fU7xp{zpr V _  Z` l  ;   6qppq}}p{W=ef]{puzpz o  oZ  `2  "  `xpX $%       !ACommentary VersionB ( a w hh h h h h  h hhhhhhhhh!hh$XX,XXXX)X+X5X3c Uq}wpq}nf]1&}qpr 6  <`  ' _m N  */B 6qpqqpsH7Q78spz  lZZ ) `6   ' @_ xpuUQFupqpr V  `_  Z F  ) B qpxLxpr}zpz B ') Io  `P  " B xpwzqp{Q{puqpr BB' B e39 *@ qp~}spq}S}qppqyxpz@;)Bm e 'B  VzpvvpsQspps}qpsE '' R) Zi m   B; rp}zqppuUuppvvp|S  _6IN3_ )`EBmO '_ zpt}sppxQxpqz~ppt `R V)*NO @BYm  B 6rpp|vpp{P{ps}vp|6  ;  oB  E@` 3_zpszqq}L}qv|t oV NEBBZ m <rz}ssCtz~oI)"Ie6)6_cBB@@B@__@BlBB@l<)-V|vui [ w  $,.YesNo/,  , : AM PMA#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# c^_#  _l#  `l#m  av CgTgvh ivTjxivPk#TlPm&3Tn{&h3Po pDw6YTqp&3`Pr nTsj{tTuivcPvXTwmvPxTykvq~l6V~%AAbout CommentaryB\   A wB w I N w  $,.YesNo/,  , : AM PMO W  $,.YesNo/,  , : AM PMX $,.YesNo/,  , : AM PMPMPMPMPMPMPM   $,.YesNo/,  , : AM PM  w ` D .orgl>.;tf ZU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMk, w  3 $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz   {   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     rksa_2Wj m   n 3 $,.YesNo/,  , : AM PMo   p  w $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   '   B@\[)!r S // €TA€UA€VA€WA€XA YType€ZA[Suggested Remedy€\A ]Starting Page #€^A _Starting Line #€`AaSection€bAcComment€dAe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yA=AB=AB[Ab  !"#$%&'()*+,-./012345b& v   $,.YesNo/,  , : AM PMww   3 A0@*E0:@F {G0Z=' QkS%26U%92VLWiyl XU%92VLWiyl XXXXXX9 T BcAJ  !"#$J €€€ € €€ €      AGlobal Field SetupB   €€€ € €€ €           " # J  3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMs; VOTEREMAILVOTERFIRSTNAME VOTERLASTNAME VOTERMEMBERID VOTERPHONE VOTERSTATUS XML OUTPUT^abcgijkmnpvwxy{_`d    d  ^_`abcgimjkvwxy{p n!"#$%&'()*+ , - ./AMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line Number E !LISTAa) awaiting resolution b) awaiting missing input c) instructions unclear d) confer with resolution group e) editor disagrees f) pass off to other editor g) didn't have time h) defer to next round i) to do j) in progress - k) done l) none neededVDEFA((A!1>VDEF(LISTLISTAEditorial Technical, Non-binding Technical, Binding Technical (was Editorial) Editorial (was Technical) Technical, Satisfied (was Binding)VDEFA((A!VDEF(LISTLISTAMarkedVDEFA((A Comment TypeBMembership TypeCVoteDRecommendationFEditor's ActionsGComment Type/GroupHMarked`AFMRLFMRLAbb7AFMRLFMRLAdBFind DuplicatesC ReplyComments`lP <zReason for Recommendation{Editor's Questions and Concerns€|A}Editor's Action Items€~A€A Group's Notes8Note: Group may also edit and export Comment Type above.€ADocument under Review:€ABallot Number:€A  Comment Date€A€A  Fig/Table# @BA5BAj  !"#$%&'()*+,-./0123467j^_ ` a bcdi"j k&m$n)pvwxy,{€€+€1€/€3€5€€6@@XB s@p.D/A First NameB GA Last NameB GAMembership TypeB GAVoteB GAVoterDocNumberB GAVoterBallotNumberB G^A Comment TypeB G_AStarting Page NumberB G`AStarting Line NumberB GaASectionB GbAChangeB GcAReasonB GdAComment NumberB GM9999gACounterB GL4633iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. g! QEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl#.  .#  al# bl# 8w#,v#  2y# 2#v 6{v# In#f qC>pf# L WE@@MarkedQYAExport IEEE XMLEOTABS D[@!d$@`@A14[p 0 h[[ [[ /0 h[p / AQ^AOpen Reply Comment FileE ! FMPRQ'`QdDTQAzHHddE(HH(d'`zA'dE7*`'`+ dDTQ] w  $,.YesNo/,  , : AM PM  UU? €Ad?2     _` a ^@"7 c>gt;Z<lt;Z b>gt;Z<lt;Zd W2&&Zgt;>Zlt;<Z:GC€A VoterMemberIDB G€A ReportNumberB G€A FigTabNumberB G 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 DataIj_@BcA;@6 bA.!@bA"cAk#@cA8%cA7'bA)b*vA,@c-@jbA.bA=/cAkA0bAYvA2b@4cAW6G17@9F:@.m,m>@A]HbAcIbAzJ@bBcULcN@bObAQ_RbA#SbA^TaUbA>VbA5AX@IbAMZ@RbA\[c]bA5^c`_bBAcC`@ acBsbcAdbAecgch@ibAAjbA/kbAcAlb 0yAChange 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.   2006/07/20 1EFarrokhFKhatibiGMember^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"d103v(Change "are already" to "may already be"wAccepted 2006/07/20 2EFarrokhFKhatibiGMember^Technical, Binding_16`1a5.3.1b$Remove concepts of PoS and non-PoS. con-PoS. con-PoS. c/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(cgeteWWW-WOWWWWWWWxW<W=WgetsܫWgetstatusresponsesetWgetstatusresponsesetismissingVggsnWgiveۂWۅWۆWgivenBWےW=W܏WܙWܭWWWWWWglobalIWglobally۩WWsWgloballyreplacespecificationwithstandardwhenreferring۩VglonassWgmiiWgni@Wgninotintheacronymlist@Vgni/lli/hlsiWgoEWFWGWHW6W6W6W6W6W6WNode" definitions. d6g2239 2006/05/01 2006/04/24 EYogeshFBhattGMember^ Editorial_15`46a5.2bd7g2784 2006/04/29 2006/04/24ijin"W?WuW۬WWWWWܾWWXWݻWWWW,WމWincorrectvWindependent WindicateWWindicatetransmissionstatusofapduVindicatedܾWindicationWrWinfoaWWWinteract,Winterface Winterfaces,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.1%у125.6.1.135.6.1.245.6.1.355.6.1.4H5.6.2ܰ5.6.2.1&'ƒ65.6.2.275.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|݉ݔݕݖtPBujpage۬WWWparagraphWparametersށWpart/WW,WparticularaWpassed WpduWpeersTWper,WperformanceBWWpersistentމWpicture݄WpleaseBW݄WݍWpleasebemorespecificaboutthegivencomplexityandcompuBVpleaselookatdoc21-06-0612-00-0000-rnetworkppt݄VpoaܾWWdWvWpoasvWpoints۬WpositionމWpossibleaWpptWXW݄WpreferWprimitiveWgWpropertiesvWpropertyvWproposaluWproposedW|Wprotocol/WuW+WprotocolsWprovideWprovidedBWW݄WprovidesWpurposeWqosWܼWܾWWqueryBWaWWquery/response|WquestionWrateWrather,Wreadable݄WreasonTWredundantށWreference۬W۬W۬Wlatedcomments128142108127!VV݂Vrelatedtocomment687Vancommunicatewithdif,VBW,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5BfhGcpageWKWیWWWWWWWWWWYWhWqWܬW]WaW݆W݇WWWWWWW;Wpage5secondsentenceitshouldallinsteadofalonelis݆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ۅWxHcthemihgetinfoconfirmisaddingnovaluesamecanbedoneVihgetinfoconfirmisaddingnovaluesamecanbedoneVVihgetinfoconfirmisaddingnovaluesamecanbedoneVV | | 3 : LINK_NO_ACTION | | |4 : LINK_RESOURCE_RETAIN | | |5 : DATA_FORWARDING_REQUEST | C | |6 : BI_CASTING_REQUEST | | |7 : HANDOVER_CANCEL | | |8 -31 : RESERVED @A>  33_ 33} >ct 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 04/24s ܖbcThere 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 2006/07/20 2006.03.05  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.d670g2265 2006/05/14 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@d in figure 28d756g2264 2006/05/14 2006.03.05F27stY^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. | | jreplacethelastmihgetinforesponsebyaconfirmprimitivVrepositoryWrepresent|WrepresentationW,WvWrequiredWށWresXWresponseWrWrfc?WsameW0Wsamecommentascomment170Vsap WsapsWsayingWschemaBWZWWvWsdos"Wse,WsectionW<WaWuWWݻW+WjWsecurityܾWsee@WWseecomment315andchangefigureaccordingtoit@Vselected?Wselection/WserveWserviceBWsessionWWhWset|WseveralܾWshould?WuWWWܾWW WݴWTWhWshouldbediscussedcarefullyݴVshouldthemihusersknowaboutthesessionidhVhVhVhVidhVhVhVhVhVhVhVhVhVhVhVhVhVhVer^Technical, Binding_38`3a6.1.6nstead of operators. c.3, Binding_140`140a Annex A-1y used for references.5/01eHcdestinationW WWݴWgWdestinationidentifiedetail'WWmWdetailedۆWWW9Wdetails+WW WݽWdetectfWdetectedSWWSWWJWݛW?Wdetection W?Wdetects?WdeterminationWdetermine WWWaWbWcWdetermined WޖWdeterministic WdevelopedjWkWmWnWoWzW{W|W}W~WہWܭWdevelopmentܭWdeviceWWdevicesWWdhcp݋Wdhcpv6ޕWdiagramۿWWWWW݃W8WdiagramconfusingexplanationofmeaningofdottedlinesisVdiagramdoesnotclearlyrepresentthetextbelowthefigureVdiagramneedlesslycompressedۿVdiameterWdifferenceېWܳWWWW@WWWWWWWWWWWWWWW2g2229 2006/04/28 ic@A>  33F  33K  33>d619g2294 2006/07/20jENada, Golmie, Member^ Editorial_91`10b|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 2006/07/20kENada, 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  a specific link."bb7'WRW|W(WݗWW1W6W:W7.1.2CW7.2.2.1lW7.2.2.2lW7.2.3.1EW7.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.WdESanjeevFAthalyeGMember^ Editorial_60`2a6.3.8.1bInsert "is" before "called".cGrammard466 2006/07/20ESanjeevFAthalyeGMember^ Editorial_61`46-47a6.3.9, the example has little incremental value.d457 2006/07/18ESanjeevFAthalyeGMember^ Editorial_60`2a6.3.8.1bInsert "is" before "called".cGrammard466 2006/07/18ESanjeevFAthalyeGMember^ Editorial_61`46-47a6.3.9, the example has little incremental value.d457 2006/07/18ESanjeevFAthalyeGMember^ Editorial_60`2a6.3.8.1bInsert "is" before "called".cGrammard466 2006/07/18ESanjeevFAthalyeGMember^ Editorial_61`46-47a6.3.9as above, the example has little incremental value.d457 2006/05/14ESanjeevFAthalyeGMember^ Editorial_60`2a6.3.8.1bInsert "is" before "called".cGrammard466 2006/05/14ESanjeevFAthalyeGMember^ Editorial_61`46-47a6.3.9njeevܨEVivekFGuptaGMember^ Editorial_15`64a5.3b%should be "key and salient points..."c$"key salient points..." missing andd109g3215 2006/07/20ܩEVivekFGuptaGMember^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/07/20 ܪEVivekFGuptaGMember^Technical, Binding_17a5.3.117a5.3.1s "IEEE 802.21" consistently in the draft.d107g3223 2006/05/14Iagcall 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 ?mRejected 2006/07/20 2006/04/26hESrinivasF Sreemanthula^Technical, Binding_83`1a 7.4.1.1.2b&add a new parameter session identifiercqall 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/07/20 2006/04/26iESrinivasF Sreemanthula^Technical, Non-binding_97`10a7.4.11bgrequest to reconsider the use cases and remove such remote MIH communications out of the specification.cl or remote since there is no information available to MIH users about mih peers.d575g2249iMathieu Peresse 2006/04/26cDcthose0WthoughWmWܕWWEWFWGWHWthoughithasbeenagreedinthelastmeetingthetlvssentܕVthree_WaW+W-W;WthresholdFWGWHWIWZWoWWEWFWGWHWޖW5WthresholdsۉWWZW`WaWW{WޔW3Wthresould3Wthrough7W|WWWOW3W?Wthroughout+WWthus۔WWܐWWtidWWWWWthus۔WWܐWWtidWWWWWWthus۔WWܐWWtidWWWWWWthus۔WWܐWWtidWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmWnWoWzW{W|W}W~WہWtreesjWkWmWnWoWzW{W|W}W~WہWN"bintra-roaming۫WWܦWintra-roamingshouldbedefinedthewhole2ndsentenceinth۫Vintra-technologyAWەWintroduceWWSWintroduceterminologytodescriberoaminghomenetworkandVintroducetextsayingthatschemaquerysupportispurelyanVintroducetheconceptofvisitedandhomenetworkswhenVintroducethemodificationsproposedinsubmission0598intoSVintroducedWW7W8Wintroduction`WW\W7W:Winvoked WWinvolvedWWWWWWWWcWdWiWjWkWlWmWnWpWsWuWvWwWxWۂWۇWېW۝W۶W۹WWWWWWWWWWWWWW#W)W*W2W=WGWHWKWLWNWRWTWUWVWWWXWZW\W]W^W`WdWkWsWtWzW{W|W܅W܆W܋WܕWܟWܡWܢWܤWWW<9|ERonnyFKimGMember^Technical, Non-binding_46`52a6.3.2bAAdd following Information Element in table 6- Information Elements --------------------------------------------------------------------------------------------------------------------------------------------------------------------- No | Name of Information Element | Description | Representation | Length ---------------------------------------------------------------------------------------------------------------------------------------------- No | Name of Information Element | Description | Representation | Length --------------------------------------------------------------------------------------------------------------d?d254g3208 2006/05/14yEEunahFKimGMembered?d254g3208 2006/05/14yEEunahFKimGMember48`22aAnnex B1[.nvas per commenter's requestwRejected 2006/07/20 2006/04/24 oEQiaobingFXieGMember^Technical, Binding_108`30a 7.4.15.3.2b2Remove Sections 7.4.15.3.2, 7.4.15.3.3, 7.4.15.3.4cARDF (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  33d676g2324iYoshihiro OhbakuggestedWsupporting-WtableZWtalk#WtermܬWtextAWܬWthatAWWtheAWZWWܬW-WthereܬWtheseWthis#WAWܬW-Wthisisnottruesinceseveralplacesinthissectionwetal#V20܂cThe name Link Configure Parameters Response is not appropriate for the parameter name. This parameter is just used to store a configuration value. d784g2319wAccepted 2006/07/20he name of the section does not match the name defined in table 21.d807g2318 2006/05/14܂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. 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.d807g2318 2006/05/14܂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.7g2316 2006/05/14܀ENada, Golmie, Member^ Editorial_126`15bda, Golmie, Member^ Editorial_126`15bW:4EFarrokhFKhatibiGMember^ Editorial_17`32a5.3.1b#Break the sentence after the comma.c Readiablityd120 2006/07/205EFarrokhFKhatibiGMember^ Editorial_17`48a5.3.1b#Break the sentence after the comma.c Readabilityd122 2006/07/206EFarrokhFKhatibiGMember.d116 2006/05/164EFarrokhFKhatibiGMember^ Editorial_17`32a5.3.1b#Break the sentence after the comma.c Readiablityd120 2006/05/165EFarrokhFKhatibiGMember^ Editorial_17`48a5.3.1b#Break the sentence after the comma.c Readabilityd122 2006/05/166EFarrokhFKhatibiGMemberentities.d116 2006/05/144EFarrokhFKhatibiGMember^ Editorial_17`32a5.3.1b#Break the sentence after the comma.c Readiablityd120 2006/05/145EFarrokhFKhatibiGMember^ Editorial_17`48a5.3.1b#Break the sentence after the comma.c Readabilityd122 2006/05/146EFarrokhFKhatibiGMemberalbforW W"W$W-W.W?WAWDWFWGWJWMWOWPWQWRWSWTWUWVWWWZW]W_WbWkWnWpWsWuWvWWۂWۄWۅWۆWۇWۈWۉWۓW۝WۭW۳W۸WWWWWWWWWWW$W,W7W@WRWSWTWUWVWWWXWYW[W\WcWeWhWiWmW|W܅WܒWܙWܩWܴWܵWܹWܻWܽWܾWܿWWWWWWWWWWWWW W WWWWWW1WJWOWSWoW|W݁W݊WݔWݙWWWWWWWWWW WWWW!W'W,W1W2W3W4W5W8W:WVWjWqWtW}WހWނWޔW3W5WWWWWWWWWWWWWWWWWWWVݠc^MacMobileNode, Link Type and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d546g2345vby comment 527, 626w Superceded 2006/07/20 2006/04/28ݡE YoshihiroFOhbaGMember^Technical, Binding_78`25a7.3.14.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc c8MacMobileNode should be replaced with LinkIdentifer TLV.d550g2346vby comment 527, 626w Superceded 2006/07/20 2006/04/28ݢE YoshihiroFOhbaGMember^Technical, Binding_79`17a7.3.15.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc c8MacMobileNode should be replaced with LinkIdentifer TLV.d556g2347vby comment 527, 626w Superceded 2006/07/20 2006/04/28ݣE YoshihiroFOhbaGMember^Technical, Binding_80`7a7.3.16.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d559g2348v by 527, 626w Superceded 2006/07/20&d?^ Editorial_42`20a6.3.1bAChange 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). '@33d848g2268 2006/05/14 2006/04/249EQiaobingFXieGMember9EQiaobingFXieGMember8.5.3.11b4/24hbIConsider specifying the QoS information in link layer independent format.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 fr6.1njeev3|@bBWLWMWOWPWQWRWSWTWUWVWWWcWdWeWۉWېW۪WWWWW/W7WQWZW\W`WeWfWiWkWܤWܫWܳWWWWWW+W0WCWDWaWݍWݏWݐWW WWWW"W$W7WޖW3W4W5WߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWߌWVmctotalFWWtoward3WWtowardsKWtowarsWtrackWtrafficWWWWW9WtrailingWtramissionWtranmissionsWtransaction۔WsWuWWW W WWWWtransactionidisnowpartofmihffixedheaderassuchitcVtransactionisnotdefinedanywherethustransactioniddoes۔VtransactionsWW WWtransferۨW WܟW!WtransmissionWtransmitTWUWWWtransmittedWtransparent*WWWtransport:W;W<W=W>WwWۈWWWW܋WܩWܯWWWWWW W2WW0W7W2WtransportsWtraverse7Wverse7W7WW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2WہWtbannex!WۀWہWWWWDWEWܚWܼWWW}W݂WW>WDWannexesWanother?WpWۂWWWWW"W'WaWbWcWanotherwordlikehandovershouldbeusedVanyPWRWUWWWۂWWWܫWWWWPWVW݂WWW W W8W4Wanybetterinfactit'sbettertoconvertthedatasoVanythingWapWܵWap/bs4WapisW0WappearanceMWappearsUWYWappendەWappendaparagraphthefollowingitemsarenotwithinthescەVەVWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYWYW7WCWTWUWVWWWXWYW\WcWsWtWxWܪWܴWܺWܾWWWW W(W*W0W1WJWareaWaren'tWarrayۉWarrivesWarticle2W :cCdge 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 Dmore 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@ing. 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 xcwDeferred 2006/07/20dENada, 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/07/20eENada, Golmie, Member^Technical, Non-binding_84`30bIt may be interesting for an upper layer to register on a per interface basis or to return the status code for each interface. cts. 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.}d583g2288bWW\cThe 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/07/20]ENada, Golmie, Member^Technical (was Editorial)_76`13bAReplace "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 2006/07/20 equest ( TimeInterval, ConfidenceLevel )~ lvneedݴWWSWfWneedbothnumberofoperatorsandlistofoperatorsVneedclarificationforrequestparametersupdatescanresponseۆVneedmoreclarificationandappropriatesuggestedremedyVVneedtextforsuchacomprehensiveissuesee32VneedtoprovideclarifyingtextalongwithcommentܢVneededܗW WneedsQLcservers_WbWserviceBWKWWWW+W5W:WܟWܬWWWKWeWzW}W݀WݏWݥW#W(W)W-W>WRW:W?WservicecontinuityisdefinedbutitisnotclearwhattransVserviceprimitiveconceptualabstractiondescribingtheinfoܟVngtheinfoܟVservices+W۾W+WW݂WݏWWW>WnWީWWWIWservingۇWW:W!W"W#W*WsessionsWWWWݒWݵWWWUWhWsessioniddoesnotmakesenseUVsessionidentifierismissingVsessionidentifierneedstobedescribedݒVsessionisnotdefinedanywherethussessioniddoesnotmakVsessionsWsetWFWGWHWIWۄW=WTWUWVWWWXWeWiWkW|WܻWWWEWFWGWHWޚWWWWWWWWWW W3W4W5W6W:WxlbissuedkWWWWWitW'W-WDWLWSWVWWWhWےW۔W۶W۹WWWWWWW#W%W&W*W2W\WeWܤWܾW WWUWYW݂W݅W݆W݇W݉WݑWݚWݭWWWWWWWWW,WNWVWޗW9W9W9WW9W9WޗW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WpeeVitseemsthatreportavailabilityshouldoccurafterresponsVitshouldnotbethecaseinsteaditshouldbethatthenumbVit'sWitem۪WW܍W#W%W0WitemsەWitmeWitswWWWܡWܤW(W,W0WW W!W+W>W8 cshouldWW!W#W,W-W0W=W@W[WܩWܻWWWWWWWWWWWWWWW WW'WDWFWHWZWeW݅W݆W݋WݍWݓWݔWݕWݖWݘWݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWݨWݩWݳWݴWݵWݺWݻWݼWݽWWWWWWWWWWWWWWWW0W1W:W<W>W?WBWCWNWPWXWYWnWqWrWsWtWvWxWyWzW{W|WވWފWދWތWލWޔWޖW0W1W1W1W0W0W0W0W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲W߲WRbsourceۂWsWW&WsourceidentifierۂۊWۋW!W0southboundJWsparqlkWnW{W}WqW}W~WހWށWނWރWރ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\WhWtakeOWPWQWTWUWVWucconfusion۬WW>W@WcongestionWWcongestion-safeWconiferlWconnectWconnected:WWWconnection\WiW@WconnectionsܢWconnectivity۵WW:WܡWWݏWconnectivityprotocolisbeingmigratedawayfrompppVconsiderWWWWWconsidercase2ieifthenumberofoctetsoccupiedbytheVconsiderthelinethatsaysafterregistrationthemihusersVconsiderthesentencealocalmihgetstatuscommandcausesVconsideration?WconsiderationsޔWconsideredWWconsideringSWWٹWWWW7WHWڤ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&a ?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* 2006/07/20 2006/04/24@EQiaobingFXieGMember^Technical (was Editorial)_42`33a6.3.1bARemove Figure 19.@A  33cAThere 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. ljconfirmWrWconjunctionuWcontentsW WcontextܾW WcontributionBW+WcorrectZWWcorrectlyvWcostBWcs+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)*W+W,W?@WAWCWKWYW`pWqrsWtvWxیۍۏۖۗۘۙۚۛWۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩ۭۮۯ۰۱۲۹ۺۻۼW۽WۿÃăƃǃȃ˃̃̓Ѓ؃WރWWWWWW './023456789W?@GIKMNQRT^cdefggbshows?WwW+W7W8WsideۧWuWsignalFWGWHWIWJWۉWYW݊WsignalingܴWPW݃Wsignificant9WsimilarۮW۰WW,WWsimpleW_WsimplyDWsinceW2W\WܡW_WWWsincemihispronouncedlikeemihitisnecessarytoputt2Vsincethegenerationoflinkgoingdownisimplementationde\Vsingle*WW9W=WsinrWsionAWAWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWُWْW٨WٯWٰWٴWٷWWWWWWWWWWWWWWWWWWWW;W>W@WAWlinkconfigurethresholdsaddsinrinadditiontosignalstrَVVmUbchangetextto-V.V?VAVHVIVLVMVcVdVeVsVuVxVVchangethecategorytocommandserviceRVchangethecurrenttextto3Vchangethecurrenttextwiththefollowingthemihsapfirst7Vchangethedefinitionto/Vchangethedescriptionto܅Vchangethefirstsentencesofitembasfollowsmihfunction0Vchangethefixedheadersizefrom6to8bytesinthefigureܑVchangethelefthandstacknamefromlocalstacktopeer1sta<V?Vchangethelengthfieldto4ݵVchangetheoccurstothatoccurs.VchangetherepresentationfieldfromݕVchangethesizefrom6to8bytesinthefigure27ܔVchangethesizeofaidto10ݶVchangethesizeofopcodeto2ݶVchangethetextforthisitemaccordinglytoreflectthatthVVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVݕVouttheavailabilityofacceVܙW28`T`‚:-h~ێŃ'4ܑܞăJݭăǃI5<5555558_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ޮ \SEReijoFSalminenGMember^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 ?vdraft.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 ?veferred 2006/06/30 2006/04/27 d Technical, Binding_139a8.6.1.2 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./d866g2245 2006/05/14 2006/04/28QEAjayFRajkumarGMember^Technical, Binding_139a8.6.1.2-00001;bevent-W.WHWIWLWNWOWPWQWRWSWTWUWVWWWpWۉWېWWWWRWSWTWUWVWWWXW\W^WcW܃WbWݍWݛW#W(WEWFWGWHWIWrWyWzWދWeventiddescriptionRVRVrWyWzWދWދW/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/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.5RtENada, Golmie, Member^ Editorial_115`59bAReplace "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 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/20d is embedded."d746g2305 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 {bAm7.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/07/2048 |EKenichiFTaniuchi^Technical, Binding_107`33a 7.4.15.2.2bAMIH_REPORT InfoQueryResponse @A*   *cfMIH_REPORT should be InfoQueryResponse since in Section 8.5.4.2, only InfoQueryResponse is mentioned. d666g2423wAccepted 2006/07/20}EKenichiFTaniuchi^Technical, Binding_107`64a 7.4.15.2.2b9/L65, and P70/L13p@AR 33  ! , 33RcBLink_Event_Register.confirm should be Link_Event_Register.responsed508g2420 2006/05/141zEKenichi'ۦ 2006/07/20ۧ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 2006/07/20ۨESanjeevFAthalyeGMember^ Editorial_9`38a3b Remove "the"c."the information transfer occurs" reads betterd77 2006/07/20۩ESanjeevFAthalyeGMember^ Editorial_13`7a5.1cNGlobally replace "specification" with "standard" when referring to IEEE 802.21d91 2006/07/20۪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.5d100۫ESanjeevFAthalyeGMembernjeevFAthalyeGMemberWapplicableiWh!b802.3qWW1W830W855W8802-11pW9WRWTWUWVWWWXWcWܒW,WݘW.Wa W!W"W#W'W*W-W.W?WAWDWFWGWLWOWTWUWVWWWXWZW\W]W_WbWiWkWlWnWpWsWuWvWxWېWەWۖWۚWۜW۝WۢW۪W۰W۳W۶WWWWWWWWWWW#W,W5W=WHWRWSWTWUWVWWWXWYW\W^W`WcWdWeWiWjWkWmWsWyWzW{W|W~W܃W܄WܐWܕWܗWܚWܟWܡWܤWܪWܫWܬWܰWܳWܵWܶWܹWܺWܾWWWWWWWWWWclose٪WcoٿWcode٘WWWWcodesٝWcoincide٪Wcollecting;Wcollectively@WcolumnكWٴWٵWٶWWcombinationWWcompletedCWcrepeatW+WrepeatingxWrepeatspWvWrepetitive7Wrepetitivesentences7VrephrasingۘWWreplace۩WܥWܮWW݄WݭWWW W W WWreplacealloccurencesofmihinthedraftbymihfthedraftܥVreplaceapplicationwithapplicationݭVreplacebytesbyoctetsVreplacefig4bythesubmittedcontributionܮVreplacefigure5withabetterdescriptionofthemihfuncti݄Vreplacewithupdatedtextforsection5.5listingallthe4Vreplacewithupdatedtextforsection5.5.1listingallthe V Vreplacewithupdatedtextforsection5.5.3listingallthe V V V V V V V V V V V V V V ViWmWܕWܗWrequestsetsWmWrequireWrequired"WW)Wrequirements۟WrequiresWrequiringWOWreserve"Wreserved}WresideWܩWresidesܟWܩWresiding:Wt9cspecifies\W{WܢWnWspecifiyܐWspecifyܯWܽWWWaWWWWspeculativeAWspellingTjmpspiritEWFWGWHWsposWsquareWfWssid[Wsta/ue-WWstack۪W/W7WqWDW݄WWWstacks9W<W=W?Wstaion'sއWstandardۑWەW۟W۩W'W\WܖWܛWܢWܣWܭWWWWW:WhWWWWW>WNWSWstandardizeEWstandardizedEWWnGMember^ Editorial_125`21-22a8.4.2.13b'"Combination of actions is permissible"cImproved phrasingd800 2006/07/20oEFarrokhFKhatibiGMember^Technical, Binding_126`1-10a8.4.2.16bpMeaning of link parameter threshold should be explained, possible parameters given, and range provided for each.c6Vague definition of "threshold", parameter value ranged804v!no suggested text. Issue assignedwRejected 2006/07/20atus"cSpellingd808 2006/07/20qEFarrokhFKhatibiGMember^ Editorial_137`20a8.5.3.19b(Replace "further deliver" with "forward"cImproved phrasingd855 2006/07/20rEFarrokhFKhatibiGMember^ Editorial_138`42a8.6.1b "on-demand"c Missing dashd864 2006/07/20sEFarrokhFKhatibiGMember^ Editorial_145`3aAnnex A2bReplace "3GPP" with "3GPP2"c Incorrectnessd885 2006/07/20tEFarrokhFKhatibiGMember^ Editorial_148`22aAnnex B1_148`22aAnnex B1*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ݴWVJcIn link detected, is it envisoned that MIP handoff between two APs of the same technology may be triggered by this event. Or is this event only for links of another technology ?d276 2006/07/20KEFarrokhFKhatibiGMember^ Editorial_40`65a6.2.3b8Rename the figure caption to Remote Command Service Flowc8Rename the figure caption to Remote Command Service Flowd297 2006/07/20LEFarrokhFKhatibiGMember^Technical, Non-binding_42`14a6.3.1c/Insert "relevant to the MN" after "in the area"d313wAccepted 2006/07/20 MEFarrokhFKhatibiGMember^ Editorial_42`65a6.3.1b0Insert comma after first appearance of "network"cImproved sentence flowd323 2006/07/20NEFarrokhFKhatibiGMember^ Editorial_43`24a6.3.1b Remove "more"cSuperfluous segmentd326 2006/07/20OEFarrokhFKhatibiGMember^Technical, Binding_43`47a6.3.247a6.3.2doff within APs of the same technologyMember/05/14:kcfig/tableifapplicableVVfig/tableifapplicabletable20/table21Vfigure%W&WwWۊW۪W۴WWWWWWWWW7WqWܑWܒWܓWܔWܵWWWWWW:WKWyW݄WWWWWWWW W+W0W6W9W=WBWWWZWvWޗW2W7W8W:Wfigure11hasbeenintroducedwithoutanytextandpurposeVfigure15isincompletelocaleventsarenotshownproperlyVfigure15wouldbenefitfrommoreexplanatorymaterialhighlVfigure18isincompletelocalcommandsarenotwhownVfigure23onpage111istitledcommonmihfframeformataltqVfigure23representsanmihframeusing802.3/ethernetotherVfigure24dealswithhowthemihwilltransportmihmessageVVfigure24dealswithhowthemihwilltransportmihmessageVfigure24doesnotrelatetothesection8.3weputittoshMcby+W/W0W1W2W3W4W5W6W7W8W9WEWLWMWOWPWQWRWSWTWUWVWWW_WbWcWdWuWWۂWۄWۅWۊWۋWېW۸WWWWW/W:W@WCWDWEWHWRWYWZWcWzW{WܟWܡWܥWܪWܬWܮWܯWܺWܾWWWWWWWWW0WJWWWWWWW WWWWWW W!W#W%W+W>WJWKWOWޏWޖW3WrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWcfime|Wfime|W|WWpdatedwiththeprimitivesdefiguresWfiltering W WwiththeprimitivesdeޗVfiguresWWwWWWWQWfitWWfitsXWYWfixeduWܑWܔWWWWW'WflatZW]Wflexibility_WbWflexible WflowۚWWW-WWKWMWyWzWWW>WBWKWflowsWWflyWWfmipWfmipgmiiicmparenotusedVfocusWXWYWfollowWfollowed>WfollowingܬWCWݏWݐWWWWW W/W1W2W>WIWޕWfollows۪WforW!W"W$W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WBWEWFWGWHWIWJW[W^W_WaWbWeWhWjWkWmWnWoWpWuWvWyWzW{W|W}W~WہWۂWۅWۆWۈW0_‚(ۮۯ۰ܪ˃456‚)!۱۲۳̃789݂9‚*۴:Z‚1"۵ܫ‚2۶6̓;<ݍݎ‚3#$۷۸۹ۺۻܬܭ=>?@ݏݐۃ-.‚4ۼܮ΃AB‚5݄݃‚6 ‚7 ‚8۽۾CX2‚9ۿDEF Y‚:σG /////////////////////////////Ճ‚TKȃɃʃ˃ܶ׃؃‚UZ[ےۓ̃̓΃ <=>?@Aܷڃۃ‚VۑσЃ!"B݃‚W߃‚XX\у҃#$CDEܸܹܻܺ‚YYF‚Z]^%&Gܗܼ‚a'H‚bӃ(‚c‚dԃ‚e_`)Iܾܽ‚fa*‚gbՃփJKLܿ‚i׃MrbdeletethefollowingtextkVnVvVdeletethesentence VVdeletethisdefinition VdeletethistypeoraddanewdefinitionVdeletedWWܴW݀W-Wdelineation7Wdeliver_WNWqW"W$WdeliveredW"W$WޕWdelivers_WoWdeliverywWW7WdemandW+WdemonHWdependant\Wdependencemedia)WdependencyWdependentDWpWWWW2WpWWWW2W2WendentDWpWWWW2W2WDWpWWWW2W2WWWWWWWWWWWWWWWscribingW5WܟWdescribingroamingaspectsonin5.3.2beforethetermsareVdescription?WpWtWۂWېW=WNWRWSWTWUWVWWWXWYW\WcWkWmW܄W܅WܲWܶWܷWWdescriptiveWdescriptonܹWdescriptorW+1creject.WWrejectedۄWrelate_WaW7Wrelated_WaW|W~WۓW:W݂W"W#W$W%W>W1W:WrelationshipDWWWW,WWWrelationshipbetweentable6andsection6.3.4.1isunclearVrelationship/mapping'WVVVVVVVVVWOWܖWܫWWWremoveۙW۱W۷WWWWWܱWWremoveapparentlimitationsVremoveimplicationthataccessisremotesinceinformationm۷VremoveimpliedlimitationbetterexplainuseVremovelimitationsVremoveredundancyۙVremovereferencestoasn1VremovedAWsW۝WWWrenameۭWWrenamethemessagefromtheremotemihftolocalmihfaseveVrenamethenon-posmihentitytomihnon-posforconsistencyۭVreorderWreorderthetable4andtable5tobeconsistentwithorderiV |  (cAConsider case 2 i.e. 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 1 and the remaining 7 bit indicate how many octets follow. On line 55-56 it says that the value represented by the second octet of the length field indicates the total size of the value field.d410g2262vLBy comment 752/756 and by contribution 21-05-0671-00-0000-802 21-FrameFormatw Superceded 2006/07/2022 appended octets (starting from the 2nd onwards depending on the value of the 7 bits of the first octect) indicate the length of the value field.c3 so there is no need to have No 1.2c3.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.2cl flow when acually it is the logical flow.@ ۄ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 .c_Initiate.request , MIH_Handover_Commit.request, MIH_Handover_Commit.responsed615g2211wAccepted 2006/07/19 2006/04/24Markedۄ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 .c€ATable@A  33ۃE Guo JunxiangGOther^Technical, Non-binding_89`26a*7.4.6.1.2,7.4.10.1.2,7.4.12.1.2,7.4.12.2.2bbAccept the changes as described 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 WWfbiftypeielistofnetworktypeisapprovedreplacetypeieKVLViiYWWillustratedWillustrates Willustration!W WimihfWimmediatelyeWېW\Wimmidiately2WimminentVWWRWimpending!WimplementWimplementationAW\W%WimplementationsAWimplicitlyPWWWWWWWWWWWWWWuWvWxWWۃ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ܽWWWWWW d@wzf@IgcicAj@kl@Qnc%oUp@YbASqdrj 33/  33< 33>d795g2315 2006/07/20ENada, 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 2006/07/20܀ENada, Golmie, Member^ Editorial_126`15bHcproxyiW,WއWpsdn/fa-WWpsdxa-WWpsychological<WpureWpurposeWܿWWޕWput7W<W>WqosW:WnWܼWܾWW0WWSWqualityJW<WquantityWqueries_WaW|WܘWܻWWNWquery"WiWlW{W|W}W~WQW|WWW!WfW~WWquery/response<Wquerying۸Wqueryresourcelist܎WWWesourcelist܎WquestionWWWWquestionableۀWquickly'WquiteWWquotesWWWquoting:Wr1۴WWr1andr3inetrafceseemtobeinterfacesbetweenmnandnet۴Vr2Wr3۴WWr4ܪWWr5ܪWradioۂW۽WWWW+WradiusۓW=Wradius-nas-port-type^Wradius-nas-port-typeisunsuitableforourusesinceitdoes^VraexWފWran۽WrandomlyWrangeWWhWWoWWrankpfjmake WmakesށWmanagement"W,Wmany,Wmatter,Wmay"W/WW WWWTWmaybe<WjWmaybeweneedtoclarifythesectioninsteadofremoving<VjVmeanWmeantމWmechanism/WmechanismsWmediaWmemoryWmgmt/WmihW WWW,WgWhWrWmihfWWWTWrWmiminumWminimumWmis-classifiedWmobility"W/W?W,WmodifyWmootBWmoreBW݄WށWmostWWmultipleW,WmultiplexWmustܾWTWTWWTWTWTWTWTWTWTWWmultiplexWmustܾWTWTWTWTWTWTWWTWTWwdiagramandtextprovidedin21-06-0612-01-0000-rnetworVnms+WnoܶWnotaW+WW W,W1W3W>WTWnowWnumber݄Wof۬WW+WWW W,W>WonWW W>WKWone }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/07/20 2006/04/24 ~EQiaobingFXieGMember^Technical, Binding_128`29a8.4.2.24b)Remove Table 23 (from line 29 to line 63)cRejected 2006/05/14 2006/04/2422 }EQiaobingFXieGMember^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>Ccgoal#WWWWWWWWWWWEWFWGWHWgoingۅ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 4 XbBessful, 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/07/20 YENada, Golmie, Member^Technical, Binding_72`14b72`14bat event has been succ be set to 0. c^To insure interoperability, the IEEE 802.21 must define how to transmit the set of Event IDs. d510g2276 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. d510g22760Wl<cthereisnoneedtodefinenewtermshorizontalhandoverand?V@Vthereisnoreferencetotheidentifiersdefinedby802.21DVEVthereisnospecificationfortherepresentationofthelistVthereisnotextfollowingtheheadingforsection5.6.12Vthereisnotextunderfigure5onpage24andfigure11onVthereisvaguenessinhowgeographicareaisdefinedconsideSVtherewillbenodirectcommunicationbetweenthephyandma VthereafterWthereafterthesepacketsmaybeencapsulatedinal2mihproVafterthesepacketsmaybeencapsulatedinal2mihproVVafterthesepacketsmaybeencapsulatedinal2mihproVVafterthesepacketsmaybeencapsulatedinal2mihproVVafterthesepacketsmaybeencapsulatedinal2mihproVV V V V V V V V V V V VWWWWWWW%W&W'W)W-W/W:W;W=W@Wcnew?W@W_WbWۆWێW۾W#WgWWWWW݂WݍWW W!W"W$W%WdW?WWWWWWWWWWWWWWWW 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۪W۵WW9WCWOWoWqW|WܑWܔWܥWWWWWWWWWWWWW W0W2WݸWWWW"W$W*W+WXWYWoWޗW2W8WAWBWCWmihfheaderformatishaving8bytesinfixedheaderpartseܑVmihf-idsTWmihf-idscouldbeconflictedbetweencommunicatingnodesTVmihfid/sidWerܠVmiih2Wmiis#W_W`WbWiWjWkWlWmWnWoWzW۳WWWWIWܻW_W`WuW݂WWmiisisnotdefininganinformationrepositoryVmiisprovidestheabilitytoaccessthisinformationaboutaVmime|W~WminimizeWminimumWminutesWmip-WWJWWmipv4Wmis-correlationWmisleadingWW=W@WfWWmisleadinguseofsquarebracketswhicharecustomarilyusedVfVmismatchW{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. .d250g2211vAThe 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 2006/07/20 2030/04/06Marked9bare not mandatory from client's perspective, does that mean they can all be igoned?d254g3208 2006/05/14yEEunahFKimGMembered?d254g3208 2006/05/14yEEunahFKimGMemberx B1} breplacethedefinitionofhorizontalandverticalhandovers:Vreplacethedescriptionwiththismessagereturnsthestatus܄Vreplacethefirstsentencewith@VreplacetheformatofthelengthfieldshallbeperthedefiivVreplacethelistofeventsthatmaycarriedinamessageyVreplacethelistofeventsthatmaycarriedinamessageeaczV{Vreplacethemihgetinforesponseline20withmihgetinfo=Vreplacethenumberofparametersthatmayincludedinalist~VreplacetheremainingoctesieexcludingthefirstoctetofwVreplacetheueisknowntothenetworkbutnottransportcha܋Vreplacethewiththat VreplacethisbytheܣVreplacethisisusedtorespondtheresultwiththisisused܆V܋Vreplacethewiththat VreplacethisbytheܣVܣVa^VreportTW_WWreportedQWreportsAW_WrepositoryWrepresentationAW=Wkܕ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  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/07/20 2006.03.05  @A> 33  33>cKSize of MIHF Fixed Header is not consistent with that depicted in figure 28d756g2264 2006/05/14 2006.03.05F27rialGEFarrokhFKhatibiGMember^ Editorial_29` 34, 36, 44a5.6b$Remove dash in "mobility-management"cNot customary use.d211 2006/07/20HEFarrokhFKhatibiGMember^Technical, Binding_30`62a5.6.1.4badd /3GPP2 after 3GPP.c03GPP2 should be mention in this section as well.d225wAccepted 2006/07/20MarkedIEFarrokhFKhatibiGMember^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 HOd253 2006/07/20n part of the network." needs to be exapnded to include other reasons that may trigger HO.cLimited scope of HOd253 2006/06/21rrokhFKhatibiGMember^Technical, Non-binding_37`29a6.1.8b`Define if link events are envisoned to be used for MIP handoff within APs of the same technology/05/14 &cand:WBWxWyWzWzW  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"bremovetheentiresection8.5.3.11and8.5.3.126Vremovetheentiresection8.5.3.13and8.5.3.147Vremovetheentiresection8.5.3.15and8.5.3.168Vremovetheentiresection8.5.3.17and8.5.3.189VremovethefigureandreferencestoitVremovethefirstsentenceIVremovethefollowinglinesܬVremovethefollowingsentencefromthedefinitionthemobile3VremovethemobilenodemaymoveacrossdifferentaccessnetwQVremovetheparagraphassociatedwithitem1animplementatio%Vremovethereferencestoasn1Vremovethesecondhandovercomplete܉VremovethesecondsapۤVremovethesentenceV܉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ܟWoWWWWWބWprovidedsWprovider's۳WprovidesAW_WpWuW0WWW1W3W4W5W7W8WprovidingWprovision5WܟWprovisionedWprovisioning۳Wproximity3WproxylW,Wpure݊WpurelyWpurposexWWputW2W:W<Wputcontentsofsection6.3.8toannexcVVVVVVVVVVVVVVVVVVVVhsFVGVre-definethelinkqualityparametertypeencodingtableasJVre-organize_WbWre-verificationWWreasonWreceiptېWreceive-WLWuWېWreceivedHWIWVWreceptionWWrecipienteWfWlWېWredefinebWredrawing۽WreevaluateRWreference$W۬W۴WreferencedۑWrefersۖWWreformatWregardingTWregime۶W‚c9`oEܝEVivekFGuptaGMember^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 2006/07/20ܞEVivekFGuptaGMember^Technical, Binding_8`29a3b)Remove second instance of definiton of MNcMultiple definitions of MNd66g3245 33Rd62g3244 2006/07/18ܞEVivekFGuptaGMember^Technical, Binding_8`29a3b)Remove second instance of definiton of MNcMultiple definitions of MNd66g3245 33Rd62g3244 2006/07/18ܞEVivekFGuptaGMember^Technical, Binding_8`29a3b)Remove second instance of definiton of MNcMultiple definitions of MNd66g3245  cand|W~W݂WzWzWzW, Binding_16`1a5.3.1b8Remove reference points from figure and rest of documententence in that paragraph may be removed as unclear (?)cUnclear definitiond104 2006/05/14۬ESanjeevFAthalyeGMember^Technical, Binding_16`1a5.3.1b8Remove reference points from figure and rest of documenter 2.5d100 2006/05/14۫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 definitiond104 2006/05/14۬ESanjeevFAthalyeGMember^Technical, Binding_16`1a5.3.1b8Remove reference points from figure and rest of documentdefinitiond104 2006/05/14۬ESanjeevFAthalyeGMember^Technical, Binding_16`1a5.3.1b8Remove reference points from figure and rest of documentt of document obremoveܛWܞWܬWܱWWWWWWWW W$W%W(W)W*W2W8W:W@WGWNWQW[W\W^W_WfWuWvWwW݂WݳWݴWݷWWWWWWWWWWWW:WNW_`degWiWjWmWnWކW7W7W7WߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙWߙ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 2006/07/20E 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" c 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" witthe bits of this field are to be set to '0'."E Ulises Olvera33Lcthedocumentspecifiesthatanupperlayermayconfigurethe\VtheeffectofreceiptisnotcoherentbecauseitmentionsthVffectofreceiptisnotcoherentbecauseitmentionsthVVffectofreceiptisnotcoherentbecauseitmentionsthVVtheexampleinbracketsinconfusingegbsorrncorggsniVtheexytensibilityaspectofdifferentiesisnotveryclearܸVthefieldnumberofadditionalheaderidentifiersisnomoreܓVthefirstparagraphof6.3.5talksaboutgeneraluseofmiis`VthefirstparagraphrepeatswhathasalreadybeensufficientpVthefirsttwosentencesmeanthesamethingsIVtheformatofthecostinformationelementmustbedefinedbHVtheinclusionofmihnetworkaddressinformationprimitivei:V;V<V=V>VtheinformationcanbeobtianedeitherbytlvorschemahoweܬVtheinformationtransferoccursreadsbetterۨVthejustificationforack-rspbitisinsufficientyVRfbremovemihhandoverinitiatemihhandoverpreparemihhandov/V0V5Vremovemihnetworkaddressinformationfromtable14;Vremovemihnetworkaddressinformationfromtable19=Vremovemihnetworkaddressinformationfromtable4:Vremovemihusersareinthebeginning*VremovemoreNVremovenewpoaidentifierVVVVVVVVVVVesection8.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,WbSpecify 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.cWReference to traffic classes is vague. Also this information is unlikely to be static.d372vThe IE should represent the QoS capabilities of the access network (e.g. .11e capable, etc.) QoS and Security are defined for specific link types. Clarify Access Network.wDeferred 2006/07/20 dscriptions.cJThere is no specification for the representation of the LIST_OF_OPERATORS.d360g2243 2006/05/17 2006/04/286EEleanorFHepworthGMember^Technical, Binding_45`10a6.3.2criptions.cJThere is no specification for the representation of the LIST_OF_OPERATORS.d360g2243 2006/05/14 2006/04/286EEleanorFHepworthGMember^Technical, Binding_45`10a6.3.2y engine entity.EEleanorFHepworthGMember29 member˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃2܍ܑܒܓܔܕܔܔܔܔܔܔܔܔܔ܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍܍ܒܓܔܕܖܗܘܙܚܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܮܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&q]܎ENada, Golmie, Member^ Editorial_94`39b8Add "QueryResourceList" at the end of the parameter listc*The parameter QueryResourceList is missingd639g2331 2006/07/20܎ENada, Golmie, Member^ Editorial_94`39b8Add "QueryResourceList" at the end of the parameter listc*The parameter QueryResourceList is missingd639g2331 2006/05/14 334  33? 33>d886g2329 2006/05/14܍ENada, Golmie, MemberGMember^ Editorial_147`34bDUpdate the number of the item starting at the "TYPE_IE_POA_LOCATION"cDuplicate number 10d891g2330 2006/05/14܎ENada, Golmie, Member^ Editorial_94`39b8Add "QueryResourceList" at the end of the parameter listc*The parameter QueryResourceList is missingd639g2331 2006/05/14334  337 33>d884g2328 2006/05/14܌ENada, Golmie, Member^ EditorialENada, Golmie, Member^ Editorial&qbentities W"WpWsWuWW7WfWrW0W3W݈W/Wentitiesmake݈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'W-W.W?WAWFWGWHWIWLWMWOWPWQWRWSWTWUWVWWWXW_WcWdWeWfWiWjWkWlWmWnWpWqWsWuWvWxWWWWWWW*WhWܴWܻWWWWWWWWWWW_W{W}W݊WWWWW,W1W2W3W4W5W7WIWނW߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾W߾WWW1ݐE YoshihiroFOhbaGMember^Technical, Non-binding_22`8a5.4.3cAThe following paragraph talks about the static and dynamic information. But it needs to be clarified little bit as to which one is static and which one is dynamic. " The Information service also provides access to static information such as neighbor reports. This information helps in network discovery. The service may also provide access to dynamic information which may optimize link layer connectivity with different networks. This could include link layer parameters such as channel infoBrmation, MAC addresses, security information, etc. Information about available higher layer services in a network may also help in more effective handover decision making before the mobile node actually attaches to any particular network. "d161g2412 2006/05/17 2006/04/28ݐE YoshihiroFOhbaGMemberr network. "d161g2412 2006/05/17 2006/04/28ݐE YoshihiroFOhbaGMembers.6Akcsap%W&W'WCWDWEWSWیWۤWZWܰWWWWWWW W0WAWDWWW4W5W6W7W8WDWWWmW2W3W>W?Wsap's%WDWsaps'WDWܰWWWWWW W W WWW1W6W8WWWsatelliteWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsayWWsaying/WWsaysWrW۾W%W&W.WZWWWyW݇WWWWޚWW W:WxW߶WWscanۆWWNWmWscanschedulingNWscares݃WscenarioWݓWWscenarios\WۈWWMbusedVWWWcWiWkWnWpWsWxWېWW#WNWVWXWZW\WwW܅W܆WWWWWJWWWW!W%W1W3W4W5W8W>W}WހWނWބWޅWއWusedmimetypeapplication/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 VthefollowingsetofmihcommandsaredefinedޔVe Vthefollowingsetofmihcommandsaredefinedޔ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\ctheWWW!W"W#W'W(W)W*W+W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WBWDWEWFWGWHWIWJWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWuWvWwWxWyWzW{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۾WWWWWWWWWWWWWWWWWWWW W W W WWWWWWWW#W$W+W,W-WdthenomustbeupdatٵVٶVimplementationW1W٧WimprovedsentenceflowzV+]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.d561g2349W]wcis܎WܐWܑWܒWܓWܔWܕWܖWܗWܘWܙWܛWܟWܡWܢWܤWܦWܩWܫWܭWܯWܱWܳWܵWܷWܸWܺWܼWܿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWW W!W%W+W2W:WEWJWSWXW\WaWeWxWyWzW{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ݿWWWWWWWWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWݰWrCEQiaobingFXieGMember^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.d486g2279 2006/07/20 2006/04/24DEQiaobingFXieGMember^Technical, Binding_63`4a7.1bAdd discussion about the relationship or mapping between MIH_Link_SAP and media dependent SAPs. If such a discussion is improper for 802.21 spec, it must be fully explained.cyThe relationship or mapping between MIH_Link_SAP and media dependent SAPs is critical to understand but is not discussed.d483g2280v7as per contribution 21-06-0705-00-0000-Link-SAP-MappingwAccepted 2006/07/20 2006/04/24 9Ã`:Ãp;Ã<Ã=Ã>Ã?à @Ã0AÃ@BÃPCÃ`D dDT ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_B/cimprovement W,WAWZW]WWWWWWWWWWWWWWWWWWWWWWaWbWhWqWuWvWwWۀ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ܾWWWWWWWWWWWWWWWWWWWcseegWuW۪WۯWܑW#WWޔWseeitemabove#VseepreviouscommentۯVseem۴WWW W WjWseemsۦWWWWWSWݛW:W;WseennWseervice۶WsegamentationWsegaments'sWsegment۹WWWNWselectۋWselecteduWۂWselectionۋWܡWܴWW-Wselector WselectsܡWsemanticallyCWJWsemanticsۗWۛWWWWsemanticscorrectionۗVۛVsendeWۇWۊW"W$WsenderۈWW WsendingeWܺWsense(W)W۔WWWWWWUWSWWWWWWWWWWWWsWۚWۥWۮWWW WW3W5WQWiWW6W9W@WMWWW^WxW݆WݐWWWWWWWWWWފWދWތWsentencesayingaspecificinformationrequest/responseprimVlabcrossTWWcrossedRWcrossesޖW5WcspW1WDWcurrencyHWcurrency/unitHWcurrentWFWGWTWYWZW]WۂWWWW1W3W7W>WcurrenttextinrepresentationshouldbemovedtothedescriVcurrenttextshouldmovetothedescriptioncolumnandaspeVVVVVVVVVVVVVVVVVVVVVkWmWnWrWsWzWWWWW#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_bbasiseWܾW9WbeWWW W#W'W,W.WAWDWFWGWRWTWVWWWYWZW]W_WiWsWWۂW۫W۳W۵W۶W۷W۸WWWWWWWWWWWW#W%W&W(W*W3WCWRWTWUWVWWWXWYWZW\WeWhWsWvWwWyWzW{W~W܂WܕWܨWܪWܬWܴWܶWܷWܾWWWWWWWWWWW7W;W=WIWJWOWSWUWYWhWoWyWzW}W݀W݂W݊WݺWWWWWWWWWWWWWWW WWW#W%W,W-W.W2W6W9W=W>WAWBWDWJWOWPWTWWW~WހWނWމWފWދWތWޗWWWWWWWWWWWWWWWWWWYd518g2278wAccepted 2006/07/20 ZENada, 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  33fcAIt 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 2006/07/20 [ENada, Golmie, Member^Technical (was Editorial)_73`552.8 on page 124. cbconfigured@|consideration@contribution@convey@Ccopied@lcross@$currentlinkaction@database@defied@define@Ydefineintra-roaming@)definethesyntaxofthetransactionidincludingallocation@5defines@definitions@deletemiho@deletethefollowingtext@temiho@deletethefollowingtext@@ttpwwwianaorg@ianaorg@wwianaorg@deletel2fromabovesentence@deletetheaninformationrepositorypart@deletethefirstsentenceofitema@depending@rdesignated@Zdetailed@fdetails@discover@discussion@done@eusingamihhandovercompleterequest@eitherexplaintheunlabeledtableorremoveit@encodes@enterprise@entities@entitiesmake@&eveniftheschemawereretrieveditwouldn'tassista@eventiddescription@examples@expansion@-@WbtooneofthefollowingtypesjVmVtoorco-locatedwiththepoaVtoprovideclientofthenumberofnetworksinsteadofoperaVtothefollowingtextIVersupportedisquerytypeismissingVthepoacapabilitybitmapisnotsophisticatedenoughtocap6Vthepresenceofthefahah-aaaandv-aaainthereferencemڄVtheprevioussub-sectionstalkaboutthemodificationsthatVtherelationshipormappingbetweenmihlinksapandmediad0Vtherepresentationofnumberpoaisnotspecified'VtheruleshereseemtoimplythatreceiverprocessingcouldTVtherulesonhandlingduplicatetransactionsarenotclearsVVtherulesstatethatinanycasethedestinationshallnotpUVthescanrequestsetsisnotdefinedthelistofscanrequestVthescanrequestsetsshouldidentifylinkietechnologytoْVthescopesectiondoesnotadequatelyaddresswhichpartsofHVVbvaluesMWbWcWdW)WhWxWWW8WVWފW6Wvaraible%WvaripWvariableۉW%W=WHWMWW|WW'WtW~WހWނWvariablesWvariousW'W?WpW"W~WvendorTWUWVWWWXWcWܹWvendorspecificiesܹVvendor/networkWverifyWversionWnW݁WVW~W1Wvertical?WAW:WW:Wvia#WܬW9WݎWWWvice#Wvided_W_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWweproposetoaddanienewmacaddresstotellthemihfoftaۇVweproposetospecifythewayfordealingwithmihcapabilitۈVwell WAWiWpWsW۶WWܷWܸWwereWwether܁WVFban!W-W.WLWMWOWPWQWRWSWTWUWVWWWZW\W]WcWdWiWjWkWlWmWnWuWۇWېWWWWWWWWWW,W2WZWeWfW܅WܕWܽWWWWW W W%W+W\WWIW}WހWނWއWދW3Wanexamplewouldbeaquerytoretrievealistofallevents.Vanalogous(W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W^technicalbindingV!V"V'V-V.V/V0V1V2V3V4V5V6V7V8V9V:V;V<V=V>VBVDVEVFVGVHVIVJVLVMVNVOVPVQVRVSVTVUVVVWVXVZV[V\V]V^V_VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVuVwVyVzV{V|V}V~VVۀVہVۅVۆVۑVےVۓV۔V۬V۳V۴V۶V۸V۾VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V!V"V%V&V(V+V,V:V;V=V>V?V@VCVHVRVSVTVUVVVWVXVYV\VbVcVdVkVnV܂Vj^technicalbindingVVVVVVVVVVVVVVVVVVVVVVVVVVV V V V VVVVVVVV V%V'V0V1V2V:V;VCVDVEVFVHVOVPVUVXVYV[V\V]V_V`VaVbVhVoVuV{V}V~VV݀V݁V݂V݃V݄VݍVݎVݒVݓVݔVݕVݖVݗVݘVݙVݛVݜVݝVݞVݟVݠVݡVݢVݣVݤVݥVݦVݧVݨVݩVݪVݫVݬVݮVݯVݰVݱVݳVݴVݶVݷVݺVݻVݼVݾVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVa`Gcanother_WaWiWZWeWܝWWJWW"W'W0WnWanr:WanyEWOWPWQWRWSWTWUWVWWWXW۪W۬WW)WIWܝWܫWWWW W WW݂WݏWWW WW WiWޖW>WanythingWW>WanythingWWngWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW)W7W:W=WNWRWcWjWtW܏WܖWܗWܚWܪWܭWܯWܲWܴWܹWܿWWarelinksynchronouseventsapplicableforl2handoversonlyܲVareaW=WIWareasWarticle۰W,+:EQiaobingFXieGMember^Technical, Binding_41`49a6.2.5.1bA7Remove "MIH Network Address Information" from Table 4.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  33d307g2270i Ronny Kimion" from Table 4.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  33d307g2270i Ronny Kim@Ubtooneofthefollowingtypes@(toc@towards@traversed@Itype@`typemimetlvvariableamimetypetlvanoctetstringfora@uiuc@.under@updatefigure@upon@url@useofabitmapmodeltoencodethelistofeventsthatare@used@user@users@values@)video@what@Vwhere@/whichwhy@wireless@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 j܀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 2006/07/20܁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.d807g2318 2006/07/20܂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.7g2316 2006/05/14܀ENada, Golmie, Member^ Editorial_126`15bda, Golmie, Member^ Editorial_126`15b_breferencedۑWUWYWreferencesWܱWWWWW&W'WUWYWWreferencingWreferred)WrefersۖWWWreflectWWreformatWregardingTWXWregime۶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 coJncinWW W2W6W:W;W@WEWHWJWLWSW[W\W]W_WuWxWzW{W|W}W~W݀W݂W݄W݅W݋W݌WݏWݐWݛWݥWݪWݫWݳWݴWݽWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWW W"W$W&W'W*W+W,W-W.W/W6W8W9W=W>W@WCWEWFWGWHWIWNWPWSWWWXWYWfWiWjWlWnWqWvWwW|WށWރWބWޅWކWއWވWފWދWތWގWޔWޕWޖWޗW2W4W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WWWWWWWWWWWWWWWWWWWWWWWWWW})clistWWZW]WېWےW=W@WJWRWSWYWcWgWhWmWyWzW{W|W~WܼWWWW݌WW@WDWtWWlistedEWܷWܼWlistingWSWW W W Wlists=WܼWW݂Wlittle_WbWWW1W[WݏWloc<Wlocal-W۷WWWW7W9WOWܖWܫWܶWWW`WyWzWWWW>WgWޗWlocal/mihWlocalizedޕWlocally;WZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWZWVmaintains۳Wmake(W)W۔W۰WWWmakeindefinitearticleformconsistent۰VmakesfWmaking*WۅWۆWܳWܴWmanagedWmanagement"WW+WܤWܴWmandatoryWWmanditorilyWmannerܢWmanualۂWGRc20_WaW܇WW20/tableW21ۦWWPW܁W21-05-xxxx-00-0000-qޔW21-06-0522-04-sessioݵW21-06-0524-01-0000-8|W21-06-0601-00-0000W21-06-0602-00-0000W21-06-0606-00-0000<W21-06-0614-00܏W21-06-0xxx-00-0000-w@W22ܬWހW23qWݿWWRWނW24wWWEWݿWWWW7W2461W25W256W26W28ܑWܒWܓWܔW29ۊWW+W8W2nd_WFW3WuW۽WWWWW)W=WNW}WݍWWFWZWޕW>W3.4W3.43.5and4.1donotstatewhatrepresentationshouldbeuV3.5W30WޗW33aW34W35W36W37W3753:W38W3gW3ggp2W3glink>W3glink-sapWWWWWWWWWWWWWW&W'WHW W3gpp2documentnumbershouldbeusedۡV3gpp2hrpdshouldbesupported'V)bdefinethesyntaxofthetransactionidincludingallocationVdefinethetermsessionproperlyUVdefinethevalueforversionlike0forversion1݁VdefinetypehdrtlvsrcmihfidandtypehdrtlvdstmihfidݴVdefined.WZW]W_WpWsW۫WWW=WGWHWYW`WcW܂WܕWWWTWUWYWݔWݘWWWW.W1W3W4W5WކWޔW6WdefinedinhttpwwwianaorgݔVdefinednotdefiedTVTVݔVdefinednotdefiedTVTVdefinedinhttpwwwianaorgݔVdefinednotdefiedTVTVVdefinednotdefiedTVTVwwwianaorgݔVdefinednotdefiedTVTVesAWpW۟W=WWW8WdefiningAWdefinitevWWݹWdefinitionW W#WJWZW]W۴W۶WWW W WWW/W3W4W:W`WcWܜWܝWܪWܬWWUWYWWޚWޞWޡW;.EQiaobingFXieGMember^ Editorial_5`10a2c>Reference number is missing for all the references in the listd40g2237 2006/07/20 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 2006/07/20 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 2006/07/20 2006/04/24 EQiaobingFXieGMember^Technical (was Editorial)_15`46a5.2bieGMember^Technical (was Editorial)_15`46a5.2bned in the document. @rability 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. @{\]^_BPcprepare/W0W2W5W7WۇW܏W!WiWpresenceWW:WiWpresenttWW;WݸW'WZWpresentationjWkWmWnWoWzW{W|W}W~WہW|WpresentedWpresentedastlvwithoutrequiringchangestoschemaeVpresentingWpresumably Wpretty۽Wprettyconfusingpicturewithmihreferencemodelfor3gpp1۽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۽WrangeWWcvisible@what@ewhere@7whether@whichۄK while@why@Bwill@Mwindow@within@xxxxxxx@d‚1@‚Q@\‚@Ã2@ÃC /ÃT0ÃX`@Ãe@RÃvP$Ã0@qÃ`ݹvÃpސidasے^jinlee@qiaobingxie@7ronnykim@subir@sUwolfgang@jacceptance@agreedfragmentationishandledbytransportprotocols@kand@"changefigure20asshownin21-06-0607-00-0000-sforcommen@lconfirm@could@does@facilitate@hhow/in@infoݻiisܶmake@need@pone?Ppage@referencepointsareusedinthedocumentegline24-49pag@Brelatedtomostofyoshihiro'scommentonlinkids@remote@nce@~tlvs@=xml/rdf@xml/rdf-based@yes@Fike@necessary@on@R"bremovesection8.3.2.3ݳV33  )c  TT    )c    TT    )c  .  )cP  TT    )c  TT    )c     )c  5  TT  )c  TT>  TT@ B TTD  )cH    TT  )c  <nract 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  33ijkmnpvw{{%[vinsection7onlyhavedescriptionofevents/primitivesWVinsection8havespecificvaluesWVinsection8.6.1changemaytoshallasspecifiedinthecomOVinthejuneadhocmeetingasagreeduponbycommenterۇVincludeWWݜWSWincluded)WincludeingSWindependentܰWWWWBWindicateۋWindication۔WކWindicationsTWaWinfo WinformationZWlW۳WWWܬWW;WW"WinformativenWinitiateQWinitiatedRW۫W݊Winitiator۔WinsertەWinsertwithfollowingchangesەVinstances*WWinstantiation4W5WintegerWinter-media*Winteract"WinterestedSWinterface*W0W4W5WLWMWinterfaces*W۴W1WBWintermediaryݓWintermediateݓWinteroperabilityܛWinterpretlWinto*WZWܗWVissue40VissuesZWSWitێW۵WWܗWW(cthesentencehoweverthetarnsportandsecurityofthisinfoVthespecificationdoesnotdefinethestatemachineVthespecificationdoesnotuseasn1Vthespecificationhasnotusedthetermnetworkselector Vthessidbssidisonlyvalidfor802.11networksthedocumen[Vthestandardshouldnotplacerequirementsonitself۟Vthestatementthesamenetworkentityisveryconfusing VthestatementthisprimitiveisgeneratedwhenmihcapabilitJVthesub-sectionsdonotexplainordefineallthemediaspecVthesupportforqosisimmatureinthep802.21standarddrafSVthesyntaxandsemanticsofthetransactionidareextremelyVJVJVJVrepresentationcellisadescriptionnotasVthetextofthissectionmakesalotofhypothesishowinfor݂Vthetextsaysnonewprimitivesorprotocolsneedtobedefi۾Vthetextthisparameterspecifiesthelistofcommandsthat{Vacronymmihisinconsisten2VxrjThe 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/07/20Marked15sEKenichiFTaniuchi^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/07/20Marked18 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 icmicroWmiddleWmies WmightWWWW7W:WmigratedWmih$W&W'W+W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WBWCWDWEWLWMWOWPWQWRWSWTWUWVWWWcWdWfWgWiWjWkWlWmWnWoWuWzW{W|W}W~WWہ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  ۅ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. d535g2218vRemove: Packet_Timeout, No_Broadcast. Explain NO Resources better (Which resources?) LinkParameters Degrading (based on QoS parameters or link quality parameters)? wAccepted-Modified 2006/07/20----HA FAbA.  33  :  )c;  <  TT@    TT  TT-  TT.  )c3  Y  TT  p  TT   TT.ct 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 contCinuity 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  ZibAB 33  0  )c1  2  )c;  TTn    TT    )c    TT      )c  Btion" 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  33d34g2271 2006/05/01 2006/04/2414Ã?à @Ã0AÃ@BÃPCÃ`D dDT ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_BlbconveyWW[WcooperativeۘWcooperativeuseofinformationavailableatthemobiletermiۘVcoordinatetWݸWWcopeWWcificationoftypeienetworkqosisnotmediaindependenن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ۄW\WܝWܸWWWW W WW:WKWtime-of-dayWtimeinterval]WtimelyWtimeoutWtimerWWW&WޖWtimerandreleasethesavedcopyofthepacketthesourcema&VtitleW$W(W)WrWtWJW'W:WtitleneedstobeimprovedtVtitleofsection8.2.1isincorrectsincethetextsaysl3irVtitledqWtitles\W]WtlvWWWWAWBWܗWܘWܙWܬWWWZWݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWݴWݵWݻWWWWWWWWW6W;W<Wtlvforlinkidentifiershouldbedefinedݻ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ݻVtothemobiledevicemntheonlyvisiblemihentityismihpVtocWWtooۢW۳W۵W۶Wtop۽Wcdoesn't_WaWW2WWdomainvWdonېWdon'tW7WdoneܢWWWWWOWdottedWWdownۅWۮWW-W\W܈WWWaWbWWWW#WdW{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ܫW4jyoshihiro'sWWyouWݍWvW3Wandreqyoshihiro'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/26hc9binformational!WWWinformationlist!WinformativeܩWܪWWWWnWoWinformed#WinformsHWinfrastructureۘWinfroquerytypeބWinitiate,W/W0W5WQWۂWۋWݍWinitiateactionthreshۉ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ݿWinsertatendofsentencealthougnetworkconfigurationchanOVinsertatendofsentenceonlywhenprobabilityofaccessingVinsertbeforeorbyassociatinginformationcontainedinitsVinsertcommaafterfirstappearanceofnetworkMVWbperformanceWWݍWWperformancematrixofothernetworkelementsaretypicallyrVperformed?WWperformingAWperiodVWޒWperiodic9WpermissiblenWpermitAWpersistentމWpersonallyWpersonallyithinkit'soktohaveanxmlschemabutitVperspectiveܸWpertinent!WphasedWphrase6Wphy,W WpWphysicalpWpicture۽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.4ptWLBcit'sܳWܽWܿWWWW7Wit'snotclearwhatthedifferencebetweendifferentlinklaܳVit'snotclearwhatthepurposeofpre-definedreportsishoܿVitemWWW=W#Witem9oftable4soundsmorelikeaeventthanacommandVitemsNWits!W_WaWܝWܡWܤWܩWW0W6W:W{W݂WݐWWW W!W+WoWitself"WwW۟WFW?Witu-tvWivޗWjWjapanesejWkWmWnWoWzW{W|W}W~WہWjoblWWnWoWzW{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:WvagueW6WoW~W-WvaguedefinitionofthresholdparametervaluerangeoVvaguesentencedependingonitspositioninthesystem6VvaguenessWSWVvaguenessinenoughinformationandconfusingtrailingphrasVvalid[WhWWWW݃Wvalidrangefordestinationidentifierismihlocal/mihremoVvaluable܄Wvalue_WaWwWۄW۬WWWWW*WFWwW܂WW2W:WXW[WoW~W݁WݶWݾWWWWWWVWށ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ݐWYgbIInsert "NewLinkIdentifier" between "HandoverMode" and "OldLinkIdentifier"c>The new link identifier is missing from the list of parametersd614g2292 2006/07/20hENada, 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 125cdThe valid range of Old Link actions is not consistent with the list on page 125 (section 8.4.2.13). d616g2293vas defined in section 8.4.2.13wAccepted 2006/07/20 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."r of a specific link."Bcwill:W;W<W=W>WEWeWlWۂWېWWWWZWܤWܩWܸWWWWW WWCWݐWݑWWW WwillresultsݑVWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW|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 cthisWWWW W WWWW W%W2WHWJW{W|WW݂W݃W݋WݍWݏWݳWWWWWWWWWWWWWWWWWWWW WWWWWWWW!W"W#W$W%W*W+W4W5W7WEWFWGWHWJWOWPWXWYW\WaWbWcWjWnWއWޔWޕWޖWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWޗWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWLp jone?WށWoneormoremakesitredundantandisnotrequiredށVonlyWWoperatorvWoperatorsvWoptionWor"WWW,WgWށWother"WWothersWout?WoveraWWݻWWÃޏÃÃބà ޅÃ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 ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_T a^bAeReplca "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 2006/07/20_ENada, Golmie, Member^ Editorial_78`30bAcReplace "Number of parameters in LinkParamterList" with "Number of parameters in LinkParameterList"c@Af  33!  331  33Q  33b  33fcA:Syntax error in "Number of parameters in LinkParamterList":@A>  33)  339  33>d551g2284 2006/07/20`ENada, Golmie, Member^Technical, Non-binding_78`37>c)The unit of TimeInterval is not defined. d539g2282 2006/05/14^ENada, Golmie, Member^ Editorial_77`16b9bremovenumberofaddressheaderidentifiersݷVremoveoreventhroughtheinformaitonservice?VremoveorrenameoneofthetwodefinitionswVremoveparenthesesremoveoriginating$VremovepreferredpoaidentifiVremoverdfdatardfschemaurlandrdfschemafromthevaluezVremovereferencepointsfromfigureandrestofdocument۬VremovereferencestotransactionidfrommihfvariablehedaeVremovereferencestotypicallyfromthedraftܱVremoveseconddefinitionofmobilenodeatlines29and304VremovesecondinstanceofdefinitonofmnܞVremovesection1.6ܛVremovesection5.3.2andpossiblymoveittoannexrenaming݂Vremovesection5.8orincludeasinformativenVremovesection6.3.6aVremovesection6.3.8BVremovesection7.2.3.1andtable16EVremovesection7.4.14<Vremovesection7.4.15.3andreplaceitwiththeappropriatlyNVremovesection8.3.2.3Vremovesection8.3.2.3.3.2.3*CkcorrectYWWOWQWcouldW"WcoversWcsDWcurrent WdWdatajWkWmWnWoWzW{W|W}W~WہWWWWdeal)Wdealing/WdecideduWdecision/Wdecisions/WdecodersWdefineaWWdefineduW۵WWdefiningjWkWmWnWoWzW{W|W}W~WہWWdefinition۴WWܸWdefinitionsWdeleteAWdeliverWdependentWWOWdeploymentWdescribingYWݳWdestinationݴWݴWݴWnݴWݴWdiscoveryuWdiscussion<WjWdoۓWWW=WdocjWkWmWnWoWzW{W|W}W~WہWdocumentW-WdoesAWbWWWWdoesn'tWW+Wdomain\Wdon'tuWWݻWdon'tmentionintergernumbersbutusethetypeiexxxnamesݻVdowndWdraftWܬWdynamicWWdynamicallyW4fbaddh-aaainsection4݌VaddlinktypeietomihconfigurethresholdsandmiheventreۉVLVVaddgetstatusresponsesetVaddh-aaainsection4݌V݌VaddgetstatusresponsesetVaddh-aaainsection4݌V݌Vaainsection4݌V݌VVaddgetstatusresponsesetVaddh-aaainsection4݌VaddlinktypeietomihconfigurethresholdsandmiheventreۉVaddlsapandcssapalsomihnmssapshouldbesimplylistedDVaddmihlinksapinthefiguredeleteothersapswhichmaynWVaddmihlinksaptosection7.1.2CVVaddmoredescriptivetextmoveexamplequeriestotheannexVaddmoredetailtotable11VaddmoredetailtothecostiedefinitionVaddmoreinformationonscopingofthestandardVaddnewsectionsprobablyaftercurrentsection8thatdetaVޚVaddnewsubsectionsandtextinbothsection5andsection'VޥVaddqueryresourcelistattheendoftheparameterlist܎V/{bthresholds@Otitle@tlvs@-to@a8=tomihfnetworkmihmobilenode@nmodule@oveconsistencyhandoverdecisionmodule@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@Ncevents.W۵WWWW7WQWRWcWeWyWzWܫWܲWܳWWWaWxWWWWWEWFWGWHWKWeventsmayoriginatefromthemihfunctionmiheventsoranyܫVeventsshouldbeallowedfromupperlayersorusersofthem۵Vevery-WW'Weverything:Wevolved۽WevolvingېWWWWWWWxamineܱ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ܖWWWF"caWWWWWWWWWWWWWWWWW W W WWWWWWWW+W0W2W:WAWSWWW\W݂W݃W݄WݍWݏWݐWWWWWWWWWWWWWWWWWWWWWWW!W%W'W/W7W;W>WEWFWGWHWIWJWKWNWOWQW\W]W_W`WoWއWޒWޖWޗW5W5W5W5W5W5W5W5W5WޗWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWgqbclarifyhow/inwhatwaysecurityinformationismadeavailabܢVclarifymihprotocolwrtܯVclarifymihswitchoperationVclarifyrepresenttaionofalliesintable-6operatornamesܷVclarifytextVclarifythatisservicescouldbeperformedbeforeauthenticVclarifythecontextofasystemhereordeleteorasystemf;VclarifytherelationshipbetweenthesesectionsVclarifytowhatumtsradioprotocolsthemihlayerhasacceCVclarifywhethertheeventnosintable2andtable3aremeaNVclarifywhichiesareavailablebeforeattachingtoalinkaܺVreavailablebeforeattachingtoalinkaܺVܺVngtoalinkaܺVܺVommentsDWEWcommit/W0W5WcommonlyWcommunicatepWcommunicatesWcommunicatingWcommunicationuWxWۖW܅Wcomplete/W0W5WWWRWcW܉WcompletedWWRWcompletelyYWܓWhow All Records" button in Create and qscsupportedrWuWWWWRWcWW'WWWޕWsupportedcommandlistېWsupportedeventlistېWsupportedisquerydWsupportedisquerytypebW0Wsupportedisquerytypeshouldbeinsertedforconsistencywith0VsupportingܩW!WsupportscW|W3WWsupposedWWWWsureޏWWtWvWwWxWyWzW}W~WW܀W܃W܆W܇W܈W܊W܋W܌WܗWsyntaxerrorandconfusingsentenceincontrolthebehavioriVsyntaxerrorin3127reserved}VsyntaxerrorinadditionalidentifiersarepresentthathelptVsyntaxerrorinafterupperlayerentitiesmakeshandoverdefVsyntaxerrorinalsoknowaslowerlayers6VsyntaxerrorindeliversthismessagetothemihfoVsyntaxerrorindifferententitiesmayrregisterwithrVsyntaxerrorinlinkcommandoriginate8Vsyntaxerrorinlinkgongdown܈Vsyntaxerrorinmanyuser܊VfbdestinationWgWdestinationidentifieۂۊWۋW!W0destnationidentifierWdetailWWyWzWyWzWzWu  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@cbeWWWWWW!W#W'W,W-W.W0W1W3W:W;W=W>W?W@WCWHWMWYW\W`WcWeWkWmWsWvWwW|W܄WܝWܢWܩWܪWܬWܰWܶWܸWܾWܿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWW W'W+W0W1W;WCWEWFWHWJWxW|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ݽWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW#W%W/W1W1W1WX cthe.W/W2W3W5W7W9W:W;W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W`WbWcWdWeWgWhWiWjWkWlWmWnWoWqWsWtWuWvWwWyWzW{W|W~W܁W܂W܃W܄W܅W܆W܋W܌W܎W܏WܐWܒWܓWܕWܖWܗWܛWܜWܝWܟWܠWܡWܢWܤWܥWܧWܩWܫWܬWܭWܮWܱWܳWܶWܷWܸWܺWܻWܼWܽWܾWܿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW{ 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@ | | | before retransmission}, | | | | 4/brest۬WSW_WrestrictedHWrestructure_Wrestructureascommunicateswiththemihfthatmayresidelo_VrestructuredZW]Wresultې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/mihfhWlearnediWx c 33  33 33>d150g2240 2006/07/207ENada, Golmie, Member^ Editorial_35`38bz 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 2006/07/20 2006/04/24 JEQiaobingFXieGMember^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 | | | before retransmission}, | | | |  ې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 @exceptional result. FoObthisprimitiveisusedbymihfunctiontoqueryanddiscoverېVthistypeނWthoseWPWthresholdMWTWۉW\WoWޖW3W5WLWresholdMWTWۉ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ޖW4HGGMember^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 southboundGd497g2222w Superceded 2006/07/20 2006/04/2815 HEAjayFRajkumarGMember^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 SupercededSupercededXbclassWWclassesWWclassificationܰWclauseۮW۳WclearۢWܾWWclearlyNWܴWܷWܸWܾWWclearlyspecifyextensibilityaspectsofiesfrom802.21perܸVclearlyspecifywhatrepresentationshouldbeusedforthenVclientAW\W_W۳WWWdW܅WܫWܶWܻWܽWܿWޔW0WclientsWclose3Wclouds:WcoHWco-locatedWcodeWeWzW{WWދWތWcode1ۉWcode2ۉWcode3ۉWcodesۉWWWbWcoincide3WcollectܤWcollectingOWcollectivelyTWTWTWTWTWcollectingOWOWbWcoincide3Wcollectܤ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/24\ ybA1. Divide the flow into two in a figure; local and remote command service flow. 2. Correct the primitive type according to the direction of the service primitives. - Link_Command.indication => Link_Command.request (From MIHF to Lower Layers) - Link_Command.response => Link_Command.confirm (From Lower Layers to MIHF) - MIH_Command.response => MIH_Command.confirm (From MIHF to MIHF User) The detail flow will be shown in 21-06-0xxx-00-0000-Command_Flow.pptcSection 6.2.4 says that Figure 18 shows the flow for local and remote commands respectively . But the flow is confusing as it looks mixed.d292g3917vby comment 287w Superceded 2006/07/20 2006-04-3018zEEunahFKimGMember^Technical, Non-binding_62a6.3.9bIcthenamesofthetwostacksshouldbechangedtoreflectthe<V?Vthenamespacemustbeassignedby802.21tosatisfyinteropeCVtheneedformihfunctiontosupportinformationserviceschBVtheneedformihnmssapisnotsufficientlyjustifiedthepEVtheneedforsection5.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, BindingESanjeevFAthalyeGMember^ 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.d302 2006/07/20ESanjeevFAthalyeGMember^ Editorial_42`62a6.3.1bInsert comma after "mobility"cImproved sentence flowd321 2006/07/20ESanjeevFAthalyeGMember^ Editorial_43`13a6.3.1bRemove "access to"cSuperfluous segmentd325 2006/07/20ESanjeevFAthalyeGMember^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/07/20 ESanjeevFAthalyeGMember^Technical, Binding_43`54a6.3.2bBInsert "or could be maintained in an internal database by the MN".cRemove limitationsd336i Vivek GuptamAcceptedwAcceptedwAccepted05/17Qvseems[WWWseemsusefultokeepthenumberofoperatorsseparatefromt[VsegmentsWselectingSWsemanticsܗWsend"Wsent۔Wsentence۪W۳WWWW݃W/Wseparate[WۓWSWseparatelyWsequence0WserverZWlW;Wservice*W۳WWݓ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ܾWWWWSWeOctoinsureinteroperabilitytheieee802.21mustdefinehowtTVUVVVWVXVtoorco-locatedwiththepoaVtothemobiledevicemntheonlyvisiblemihentityismihpVtocWWtogether݅WtooۢW۳W۵W۶WW݀W݂W݃Wtop۽W>WtopicuWtopologiesW>W>W>W>W>W>W>W>W>WWWWWWWWWWWWWW!W%W,W-W.W/W2W:W<W=W>WDWEWHWJWLWMWOWPWQWRWUWVWWWXWZW[W\WaWcWiWuWzW|WڄWڋWڝWڡWڦWWWWWWWWN@Marked 0ە@Pۖ`pۗۘ‚!‚"‚#‚$ۙ‚%‚&ۚ‚',‚( ‚)ۛ‚*!‚1ۜ‚2‚3‚4‚5"‚6۝‚7۞‚8#‚9$‚:݅‚A۟‚Bܛ‚C%‚Q‚R‚Sۡ‚V‚Wܜ‚Yۢ‚Z‚a1‚b‚dۣ‚f ‚gۤ‚i.‚q‚r‚sܝ‚tۥ‚u3‚v4‚wܞ‚x/‚z ‚ ‚ۦ‚ۧ‚ ‚5‚ۨ‚ܟ‚ ‚2‚0‚‚‚‚ܠ‚‚۩‚n‚ܡ‚ܢ‚ܣ‚ܤÃ!۪Ã! ܥÃ!P۫Ã!`ܦÃ!p Ã!ܧÃ!Ã!ܨÃ"۬Ã"0ۭÃ"P,Ã"`ܩÃ"Ã"ܪÃ"ۮÃ# ۯÃ#@Ã#P۰Ã#pÃ#!Ã#۱Ã$Ã$pÃ$Ã$۲Ã%۳Ã% ۴Ã%`"Ã%p۵Ã%ܫÃ&6Ã&P۶Ã&`Ã&ܬÃ&#Ã&Ã'Ã'@۷Ã'P۸Ã'ܭÃ( ۹Ã(`ۺ ۂcAHere 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- Until we have a request to reject a request there is no point in hanving something that overrides a request...wDeferred 2006/07/20 2006/04/17€ATable@A  33 SuggestedNewLinkIdentifierUnchangeable ) --------------------------------------------------------------------------------------------------------chorizontal?W@W:W;WW,W:Whorizontalhandover:Vhot-spotsSWhotspotsWhoweWۈWےW۾WWWWWTWUWVWWWXWcWmWܭWܳWܴWܸWܿWWWWWWWWWWWWWWW WWWWWWSW}W݂WWW3WXWYW7WhowarethelinktypeparameterslistsupdatedasnewtechnoVhowisextensibilitymanagedfortheinformationelementsnaVhowthisinformationisdevelopedanddeployedinagivenl2ܭVhoweverW_WaWۅWWW)W+WYWܬWWW W W W%WaWW*WOWXWYW;WWWWWWWWWWWWWWWWWWWWidentifiersDWEW[WtWܓWidentifyWWidsNWCWRWTWUWVWWWXWW܌_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 2006/07/20܍ENada, Golmie, MemberGMember^ Editorial_147`34bDUpdate the number of the item starting at the "TYPE_IE_POA_LOCATION"cDuplicate number 10d891g2330 2006/07/20 33|  33~ 33fcAYSyntax error in "The UE is known to the network but not transport channel is established"Y@A> 334  337 33>d884g2328 2006/05/14܌ENada, Golmie, Member^ EditorialENada, Golmie, Member^ EditorialcisW!W"W#W&W'W(W)W*W+W-W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYW[W\W^W_WaWfWgWhWiWjWkWlWmWnWoWrWsWuWwWxWyWzW{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۽WWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWWW W"W%W&W'W(W)W*W-W.W/W1W2W3W9W:W;W=W>W?W@WAWBWDWEWESanjeevFAthalyeGMember^ Editorial_145`12aAnnex A2b"acknowledged"cSpellingd887 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_149`6aAnnex B1bIAdd to the sentence: " or from an internally maintained MIIS database."cZImplied limitation of capability in assuming that MIIS can only reside in access network. d894vby comment 892w Superceded 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_149`52aAnnex B2b+Change "In most cases" to "In some cases".c}Implied limitation of capability, assumed suboptimal solution. The goal should be to minimize administrative burden for MIH.d896vby comment 892w Superceded 2006/07/20EHongFChengGMember^Technical, Binding_15`61a5.3n. The goal should be to minimize administrative burden for MIH.d896 2006/07/20EHongFChengGMember^Technical, Binding_15`61a5.3, Binding_140`140a Annex A-1y used for references.'a>breplacesection5.5withcontribution21-06-0620-00-0000-ns@replacethedefinitionofhorizontalandverticalhandovers@replacetimeintervalinwhichthelinkisexpectedtogodo@}repository@represented@request/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*WvWwWܴWmanagedܾWmanagement,WUW۝WWW+WܤWIWW3W4W5W8WޕW2WmandatoryWޕW2WmandatoryWW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2WmaximumWWWmay 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/sYWmeanWmeaningoWmeaningoflinkparameterthresholdshouldbeexplainedpossoVAWCoENada, Golmie, Member^ Editorial_106`12bATReplace "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 2006/07/20pENada, Golmie, Member^ Editorial_108`43bReplace "WHIRE" with "WHERE"cSyntax error in "WHIRE"d678g2301 2006/07/20qENada, 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". d687g2302vIremove figure entirely and enhance this section for other L2's we supportHcthelasttwowordsofthelastlineneedtobeinterchangedVasttwowordsofthelastlineneedtobeinterchangedVVasttwowordsofthelastlineneedtobeinterchangedVVasttwowordsofthelastlineneedtobeinterchangedVVXVthelengthfieldisimproperfortherequestthereisnoaddMVthelengthoftheisquerytypelistissettovariablebut|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-2DWardsVavisitedenterpriseenvironmentVVVavisitedenterpriseenvironmentVVspecificVhighW+WhigherW-W;W<W=W>W@WAW٨W6WhihWhnadoverWhoړWho-typeAWhomeڃWڄWڝWhorizontal+W-WٱWhorizontallyrWhotspot#WhoursٿWngeneralhandoversmaybeinitiatedeitherbythemobilenVinclude4W5Wincludeing?Wincludes+W-WincludingWinconsistencyWWindependencemihWindependent+W-WindexingiWindicationAWBWCWindications@WindividuallyfWinforma-Wc JbB | | 3: GSM/GPRS | | | | ... | | | | | | | | Second Octet: Type of Parameter| | | | (definition is specific to | | | | the Type of Link) | | | | | | | | For Generic Link (for example):| | | | 0: Speed C# | | | | 1: Signal Strength | | | | 2: Bit Error Rate | | | | 3: Frame Loss Rate before RTX | | | | ... | +--------+----------+---------------------------------| @Af 33M 33   33 fefore retransmission}, | | | | ] fFbc"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/07/20 2006/04/24 GEQiaobingFXieGMember^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  | | | before retransmission}, | | | | ! ې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. Fo$cas\WjWkWmWnWoWwWzW{W|W}W~WہWۉWیWےW۶W۾WWWWWWWWWWWW'W+W6W7W:WGW܄W܅WܧWܩWܬWܰWܽWܾWWWWWWWWWWWWWWWWWWWW%W0WHWOW[WaWeWyWzW|WW݂W݅WݏWݽWWWWWWWWW7W>WBWEWFWGWHWOWPWRWZW_W`WgWnWqWޕWޖWޗW1W3W4W5W9W<Wasshowninthepresentation21-06-0524-01-0000-816paramet|VaskܘWasnWWasoWaspecisܾWaspectܸWܸWWnWoWqWsWtWzW{W|W}W~WہWۂWۄWۅWۊWۋWۍWېWۓWەW۝WۡW۪W۴W۵W۷W۾WWWWWWW7 ncforۚW۪WۭWۮW۵W۽W۾WWWWWWWWWWWWWW W-W7W:W=W@WMWZW[WdWeWiWqW܂W܏WܐWܖWܗWܘWܙWܢWܩWܪWܫWܲWܵWܶWܻWܼWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWW W2W:WJWaWfWyW{W|W~WW݁W݂W݋WݥWݴWݶWݻWWWWWWWWWWWWWW W W W WWWWWW!W'W-W2W6W>WKWSWVWWWXWYW^WaWbWcWhWjWpW~WޕWޖW0W3W4W4W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W޼W_79f5bencodingJWWGWHWTWUWVWWWXWcWhWXWݘWWencodingformatisdefinedindraft-ietfgeoprivݘVencodingformatisdefinedintable9ݘVencompasses,WendWAW۠WۧW۶WۻWWWQW܎WOWPWendthesentenceasmnastheotherendpointalsoremovedasۧVend-points۴WendpointۧW+WengagedWWengineWݎWengines7WenhancementsەWenoughWTWUWVWWWXWcW"W$Wenter9WenterpriseWseWW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WWWWWWWWWWWWW:W;W=W>WAWIWgWuWڎWڔWڹWWWWWWWWWWlinkcommandindicationrequestVlinkcommandsoriginateVistWWٲWٸWٹW:cfieldWFWMWPWvWwWܓWWXW~WWݵWWWWޕW6WfieldsܒWWfigܮWofsection6.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 W,W-W.WLWuWېW۵WW7WTWUWVWWWXWcWyWzW{WܫWܲWܳWJWWWWޔWeventsmayoriginatefromthemihfunctionmiheventsoranyܫVeventualityWevery'WevolveAWexactlyބWޅWexamineېWexample.W?WAWJWVWZW]W_WWWWHWTWUWVWWWXWYWiWܙWWW[W}W݂WݔWWtW5W:WWtW5W:W:W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W Hbc"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/07/20 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..@ |{GPRS:RxLevNCell} | | | |-------------------|--------------------------------|-----|-------------------------------| O@ | | | before retransmission}, | | | | $ ےk:There is a comment to remove "for example" (Comment # 350)mRejectedv:No specific remedy suggested. Comment #350 addresses this.wRejected 2006/07/206 ۓ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. mRejectedvsCreate separate 802.21 list of networks. But for consistency use same values as suggested by other standrad bodies.wAccepted-Modified 2006/07/20 ۔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.d728g2211vcie[W^WێWےWWWWW W!W%W&W'W=W>W?W@WaWܗWܼWܾWWWWtW;WieeeېW۩WWHWRWTWUWVWWWXWYWܛWܧWWWWWWWWW݅WWWWieee802.11WWieee802.16ۋWWieee802.21݅Wies_WaW!W$WܷWܸWܻWܼWܽWWies2.22.32.4shouldbeundergeneraliecategory!Vies/reportsfromܻWietfۑWWif.WFWGWHWIWJW_WbWiWۂWېWWWWWWWWW;W>W?WCWZWcWeWsW܄WܢWWWWWWWWWW WWWxW|WݬWݮWݯWݰWݱWݵWWWWWWWW*WޖW6W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WVWi ݗbA" 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. "@AR 33W  33] r 33Rc Case 2 description is incorrect.d408g2395wAccepted 2006/07/20 2006/04/28 ݘE YoshihiroFOhbaGMember^Technical, Binding_51`24a 6.3.4.3.1bing 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. "dicates the total size of the value field. "XbclarificationWWWclarifyNW۴W۾WܝWܢWܯWܲWܴWܷWܺWܿWWWWWWWWWCW;WclarifyanyinteractionbetweenmihfandhardwareormodifyVclarifydefinitionofmobilenodeܝVclarifydefinitionofreferencepointend-points۴VclarifydefinitionsVclarifydescriptionoflinksynchronouseventsܲV۴V۴V۴V۴Vints۴V۴VWcollectivelyTWcolumnW=W>W?WYWcombinationsWcommaWcommandpWۂWېWWWW+W8W9WmWzW{WcommandcodeVcommandcodezW{WcommandsuWېW8WcommentۓWۯW`WcWcommentsDWEWcommit/W0W5WcommonlyWcommunicatepWcommunicatesWcommunicatingWcommunicationuWxWۖW܅Wcomplete/W0W5WWWRWcW܉WcompletedWWRWcompletelyYWܓWbentire1W2W3W4W6W7W8W9WAWZW]WiWܥWWentirely6WentitesWtitesWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW5W9WڟWڣWWWWWWWWWWtable22sparqlquerytlvvalueparametersformatVtable23sparqlquerytlvvalueresponseparametersformatVtablexxextendedschemaurlparameterformatVtablesGWtailښWtake;W<W=W@WAWBWtakenٿWWtargetgWtayloredfWq܉g2326 2006/07/20܊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 2006/07/20܋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@A> 334  337 33>d884g2328 2006/07/20܌ENada, Golmie, Member^ EditorialeecvisibleWWWWvisitedW:WvlansWWvsW/Ww/oWwait_WbWwaiting|Wwant_WbWۈWwantsFWGWHWIWޖWwasjWkWmWnWoWzW{W|W}W~WہW܄W܌W*WwayۋW۸W/WIWܐWWWWW>Wways1Wwe!WۂWۅWېWWWܗW݊WݵW2W7W@Wwehavedecidedthatcsapandmsapbetweenncmsandmihfa2Vwe'd?WwellW'WHWW7WPWZWwell-known?W@WwepWwg>WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWeedstospecifyit'sownlocܽVwhereeWېWWWAWBWZWjWwhereas%W&WwhereverܥWQbpre-defined_Wpre-provisioned۶WpredefinedޖW5WpredictedRWpredictive^WWpredictiveeventspredictiveeventsexpressthelikelihoodoVpreferedpoaidentifieۋWpreferredlinkidentifۋWpreferredpoaidentifiWprefixZW~WpreparationWprepare/W0W5WQW|W!Wprepares\WpresenceWpresent۶WWtW;W'Wpresented]Wpreserves)WpreviousۯWpreviouslyۉWWprimitiveLWMWcWdWeWiWlWۂWېW#WNWVWXWZW\W`WkWܘWܟWWaWyWzWWWWW!W"W$W%W>WBWJWއW3W@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| ېbA 33  33" 33#  L 333  33O 33P  s 33  33 33  33 33   2 33  33 33  33 33   33  33   33D 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 @exceptional result. FobsipW݊W_W`WލWsizeWFWHWܑWܒWܔWݗWݶWހWނWslightly:WsmCWsoWTWUWVWWWXWcWWsocketW0Wsoft:Wsoften۳Wsoftentheclausebysayingmayusemiisinformationallowt۳VsoleWsome W,WWWWWiW?WIWWW'Wsomebody'sSWsomethingWsometimeWsomewhere:WsoonVWsory 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/28 ^technicalܗWܘWܙWܚWܛWܜWܝWܞWܢWܩWܪWܬWܭWܮWܯWܰWܲWܳWܴWܶWܷWܸWܹWܺWܻWܼWܽWܾWܿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW 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ݩWOctheyEWuW۬W۴W۾W7W`WܳWWWWxWWWWW6WthingeWthingsIWWthinkېW6W7Wthis#W'W*W+W1W2W3W4W6W7W8W9WAWKWLWMWOWPWQWRWSWTWUWVWWWZW]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ܾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhisinformation@reject@removelimitationsremoveimplicationofcapabilityuniquet@repeat@resource@7.ESanjeevFAthalyeGMember^ Editorial_88`53a 7.4.6.1.1b" power it down "c Word orderd613 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_93`17a7.4.9.1b0Specify parameter to identify link type to scan.cThe scan RequestSets should identify link (i.e. technology) to scan. Perhaps this function is supported. However, it is not clear how the scan requestSets parameter is formatted.d633vby comment 632w Superceded 2006/07/20ESanjeevFAthalyeGMember^ Editorial_110`42a8.1bRemove "As such".cSuperfluous phrased685 2006/07/20ESanjeevFAthalyeGMember^ Editorial_112`5a8.3bCorrect "rregister".cSpellingd699 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_112`16-47a8.3FAthalyeGMember^ Editorial_112`5a8.3bCorrect "rregister".cSpellingd699 2006/07/19ESanjeevFAthalyeGMember^Technical, Binding_112`16-47a8.3a6.3.95/01J=bfrom,W-W/W0W5W:W;W=W?WAWPWVW[WiWzW{W|W}W~WۇW۬W۵WWWWW#W3W7WHWkWܑWܒWܔWܖWܤWܫWܭWܱWܸWWWWWW9WUWYW`WyWzW݊WݎWݕWݘWݙWWWWWW!W"W(W,W;W<W>W?WIW\WޕW5WfromoneaccessnetworktoanotherwillresultinVfromthevisitednetworkaboutthatvisitednetworkorabout9V5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WިWWWWWWW1WEWHWbW߃W߆WWdcthat-WJWuWwWWۄWۇWۋWېW۪W۳W۷W۸WWWWWW7W:W;W=WZW\WtWyWzW{W|W~WܒWܔWܝWܩWܬWܯWܰWWWWWWWWWWW W W WW0W3W:W;WCWJWSW_WaWuWxWyW݂W݃WݛWݸWWWWWWWWWWWWWW%W,W/W>WEWFWGWHWKWfWnWޕW1W2W3W5W:W;Wthat'slW5W5W5W5W5W5W5W5W5W5Wۂ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#WVncinadditiontosufferingfromthesamelackofcontextasabVV[Vincurrentdraftd01mihconfigurerequestprimitivehasacۄVincurrentdraftd01severalhandoverprimitivesareinconsiۃVinfigure12showmihlinksapandit'srelationshipwithotWVinfigure3interfacetocellularbsisincorrectaspertheVingeneralitisnotclearfromthecurrentdrafthowthisiVinlinkdetectedisitenvisonedthatmiphandoffbetweentwJViWkWnWpWqW|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#WFWzW{WܬWܷWWݗWWWދWތWrepresentingHWTWUWVWWWXWcWrepresentsTWUWVWWWXWcWrepresenttaionܷWrepreset]WrequestVW_WiWlWۂWۈWۊWۋWېW9WOWQWVWXW\W`W܀W܄WܕWyWݥWWWW!W%W>WCWJWiWjWsWxW~WޅWއW6W9WrequesttoreconsidertheusecasesandremovesuchremotemiVrequesttoreconsidertheusecasesformihnetworkinformatjVequestnetworktypeۊWrequestsUWWWܕWܽWrequireW>WrequirelargemessagesupportfromtheunderlyingtransportVrequired"W#WAWەWW\WܬWWW WWWWrequiresxWrequiresclarificatioxVrescindedRWreserve"WWreservedyWۉW$WRWTWUWVWWWXW|W}WܒWܹWW!Kݓi 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-ClarifiedvACommenters 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 broadcÃfUÃgVÃg@WÃg`cÃgpdÃgeÃgۍÃh fÃh0ېÃh@ۊÃj0IÃjPÃq0یÃq`Ãr@Ãr`ۃÃs@hÃsۄj#ctheneedfortypeienumberofoperatorsisnotsufficiently[V^VthenewlinkidentifierismissingfromthelistofparametegVtheoverheadinexchangeofinformationshouldbeaslessasVtheparameterqueryresourcelistismissing܎VtheparametersupportedisquerytypeismissingbVtheparameterstimeboundandconfidenceshouldnotbebold:VthepoacapabilitybitmapisnotsophisticatedenoughtocapVthepoadefinitionisassociatedwithaninterfaceinsteado Vthepresenceofthefahah-aaaandv-aaainthereferencem:Vtheprevioussub-sectionstalkaboutthemodificationsthatVtheprotocoldoesnotseemtoincludeanycapabilitytoreacVeprimitiveisthemihfunctionwhichwillVtherecipientshouldbemihfunctionsincethisisalinkprfVthereferencemodelincludesamedia-dependentpartthemihAVthereferencepointsarenotusedanywhereinthedocumentt۬VޓGMember^ Editorial_145`15a Annex A-2bas in the comment.cASuppervison Supervision@A*   *d888g2447 2006/07/2024006/05/14ޒEKenichiFTaniuchi^ Editorial_141`20a Annex A-1badd a period to the sentence. cmissing a period. d880g2446 2006/05/14ޓEKenichiFTaniuchi33>d878g2445 2006/05/14ޒEKenichiFTaniuchi^ Editorial_141`20a Annex A-1badd a period to the sentence. cmissing a period. d880g2446 2006/05/14ޓEKenichiFTaniuchiEKenichiFTaniuchi^ Editorial_141`6a Annex A-1bas in the comment.cAnotifies notify @A>    33>d878g2445 2006/05/14ޒEKenichiFTaniuchi^ Editorial_141`20a Annex A-1badd a period to the sentence. cmissing a period. d880g2446 2006/05/14ޓEKenichiFTaniuchi3eclocated:W`WlocationܽWWWW݄Wlocation/interestܘWlocationsܯWlogical!WWWlogicallyWlongitudevWlongitude-resolutionvWlongtitudevWwWlooking+WlooksWyW݃W>Wlooksoutofplace>VloopWloosexWloseWloss۝W۵WWlotAW݂WlowېWWlower6W9WiWkWmWܫW,Wlsap%WDWlsapsWlte۽WmNWW2WmacWWܰWWWWW W+WݏW WmacaddressisnotsuitableforallmediaalsohowaretechnVVmacaddressquestionagainistheuseofmacaddressessuitaVmac/phyCWmachineWWWWWWWWWWWWWWWWWWWWWWormconsistent۰VmakesfW:W݂W݈Wmaking*WۅWۆWܳWܴWݏWmanageWmanagedWWWc55-WW55-56W56-WW56-61W58]W6ZWWW%W&W)WKWLWܼWWWWWW;W6.1.3W6.1.7W6.2.3W6.2.4yWzW6.3;W:W6.3.1KW`W6.3.3YW6.3.4YW;W6.3.4.1]WܼWW6.3.4.1.1~W6.3.4.1.4AW6.3.4.2.1BW6.3.4.2.3~W6.3.5_W`W6.3.6.1\W6.3.8WW݀W64W݇W66W67W690vWvWvWvWvWvWvWvWvWvWvW90vWvWvWvWvWvWvWvWvWvWvWvWvWvWvWvWvWvWWalternativeSWan*W+W.W:W;W<W=W>WFWGWHWIWLWMWSWandWW"W#W%W&W'W(W)W*W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WAWBWDWEWFWGWHWIWJWKWOM2ENada, 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.d81g2214 2006/07/20tle bit. d50g2406 2006/07/182ENada, 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.d81g2214 2006/07/18y to put the article "an" in front of "MIH"cGThe usage of "a" / "an" in front of the acronym "MIH" is inconsistent.d81g2214 2006/05/14incide with the mobile node.d58g2403 2006/05/14/EDavid FFamolari^ Editorial_8`42a3bWChange the definition to: " N-layer - the N-th layer of the layered protocol stack. "it is "Additional Parameters" g3582 2006/05/01WWg_cbecause_WaWWZWWWWއWbecomeWWbeefedWnced 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, Binding6camongZW]W3WamountsWan*W+W.W:W;W<W=W>WFWGWHWIWLWMWSWiWۅWۊWېWےW۾WWWWW WW-W2W:WZW\WeWnW܏WܼWܽWWWWWWWWWWW WW W+W2W:WݔWWWWW7W>WEWFWGWHWIWKWQWiWމWޗWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW 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 2006/07/208ENada, 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 2006/07/209ENada, Golmie, Member^Technical (was Editorial)_40`47b "Link_Command.request"=@Xu(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 $ ۊcAAmends MIH Capability Discovery message by adding network identifier and PoA identifier to indicate which network 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/07/20 2006-04-07 ۋE HongchengFZhuangGObserver^Technical, Non-binding_94`34a 7.4.10.1.2b ( V "ہ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.mRejectedvon request from commenterwRejected 2006/07/20 2006/04/24  T3cALink_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/07/20 2006/04/30 d 33fc this list is not consistent with the types defined by the MIH protocol in section 8.4.2.8 on page 124. d518g2278 2006/05/18ZENada, 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  33fcurned by this primitive allows quick detection of deregistration failure. n failure. :_‚gۄۆlݪ‚߃mݫ‚1ۂۋ܎ݬ‚ݭ‚ݮ‚2!i‚3ݯÃ!6AÃ! 4BÃ!0 CÃ!@<ݰ"Ã!P#$%Ã!`ݱÃ!pijkoܘއÃ!lmnܕܖ|}ވÃ!opܙƒN~Ã"pqeÃ" rstuqfԃÃ"0vwێrà gݲ&7Ã"@x ݳݴݵTUÃ"Py۔sܑă݁Ճ'VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV]ۀہی۔۬ۃ-0Ju܁ܜܠܼܾ0#ۏ۞؃ܗܬ@"&'SsPDy܆`۠rv}ܒpۢƒӃ)p۩Tܡ%ܚJW K‚!2ۄ܃ Oj^bradioۖWWWWCWradius=WݔWݕWݘWtWradiusoperator-nameattributeݕVradius-lo-04ݘWradius-lo-04txtݘVraexWjWފWrangeېWWTWUWVWWWXWYW\WcWkWmWܖWWoW|W0W4W6WratWrateFWGWHWIWJWۉWWYWWWWratherDWSWratherthenlistingprovideindividualdescriptorforeachnSVrdfjWkWmWnWzW|WqWwW}W~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)Wdiuc|WdivideyWzWdo WWWdocۃW W!WܗWܘWܙ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 W W WWDWdocumentۊWۋW۬W۶WWWWW1WdoesAW,WWdoesn'tWoesn'tWWesn'tWWsn'tWWesn'tWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWۻWWWendthesentenceasmnastheotherendpointalsoremovedasۧVend-points۴WendpointۧWengagedWWenhancementsەWenoughWenterpriseWentire1W2W3W4W6W7W8W9WAWZW]WiWbuponWW`W W"W$Wuponreceiptthereceivingmihfunctionintheoldlinkmay Vuponreceptionofthisprimitivethemihfontargetnewpoa$Vupper"W*WLWMWQWSWWWcWdWpWۉWېWەW۵WWW7WNWZW\WeWfWkWܢWݍWݎWWWWWWW"W$W,W3W@Wupper-layer7WupperskWupportingWW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WމWurlsWuseUWfWuWۘWۜW۞W۰W۳W۸W۽WWWRWSWTWUWVWWWXWcWsWܯWܿWW W W"W3WZW݂WݎWWW WVWiWjWWsWuseaasinothersimilarcasesintable۰Vuseatvariousinsteadofother"VMqb4rdfschemajVmV4sip_V`VލV4zerooroneextendedschemaurlparametersށV4-mihޔW4.3\W40`W40-417W41|WW,W42-45=W43-447W45,W46WkWW4889W5'WyWەWWHWRWSWWW W W W^W1W6W5fixedethernet^V5-7ލW5-7reservedލV5.1:W5.2W5.3pWW5.3.2!WW݂W5.5݄WW W5.5.2 W5.5.3 W5.6.1WW5.6.1mediadependentsapsV5.6.1.41W5.6.1.4lsap1V5.6.1.51W5.6.1.61W1W1W1W1W1W1W1W1W1W1W1W1W|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-3gDWmih-3glinksapshouldinterfacewithl3functionofthecdmDVmih-3glink-sapWmih-capabilityQWmih-function,Wmih-isܘWmihconfigureEWyQWmih-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, BindingF= 2006/07/206 >ENada, Golmie, Member^Technical, Binding_44`51b)Replace "1.2" with "1.3" in the No columnc?If the TYPE_IE_NETWORK_TYPE is approved, the No must be updatedd353g2248vby resolution of comment 346w Superceded 2006/07/206 ?ENada, Golmie, Member^Technical, Binding_44`58b)Replace "1.3" with "1.4" in the No columnc?If the TYPE_IE_NETWORK_TYPE is approved, the No must be updatedd359g2249vsuperceded by comment 346w Superceded 2006/07/206 @ENada, Golmie, Member^Technical, Binding_44`61bbRemove the sentence "This includes the list of network operators for each of the access networks."ctworks."ctworks."ctworks."cz`Jc"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 2006/07/20 2006/04/24 | | | | | | For Generic Link (for example):| | | | 0: Speed C# | | | | 1: Signal Strength | | | | 2: Bit Error Rate | | | | 3: Frame Loss Rate before RTX | | | | ... | +--------+----------+---------------------------------| @Af 33M 33   33 fefore retransmission}, | | | | }caspects۽WWassembleܤWݐWassigned(WCWxWܚWމWލWassignmentXWassociateۇWiatedBWW 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%WgWavoidWWcoffers_WbW:WoldhW W"W#WdWqWoldlinkactionۃWoldlinkactionsoldlinkidentifierݧWWoldmacmobilenode WݧWWoldmacmobilenodeandoldlinkidentifiershouldbereplacedwiݧVVed "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 ۈ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/07/20 2006/04/12Markedlayers. d535g2218 2006/05/14 2006/04/12ۆEYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.c> 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 2006/07/20 2006/04/24VEQiaobingFXieGMember^Technical, Binding_80ng2  FEFarrokhFKhatibiGMember^Technical, Binding_28a5.5.5c5HRPD (1xEV-DO) should be added to the reference modeld199vMDont need to add each and every technology explicitly. cdma2000 covers this.wRejected 2006/07/20Marked Figure 10he reference modeld199vMDont need to add each and every technology explicitly. cdma2000 covers this.wRejected 2006/06/21Marked Figure 10tibiGMember^Technical, Binding_28a5.5.5c5HRPD (1xEV-DO) should be added to the reference modeld199vMDont need to add each and every technology explicitly. cdma2000 covers this.wRejected 2006/06/21Marked Figure 10 to access only the following protocols SM/GMM/RRC i.e. no access below RRC (MAC/PHY)d197 2006/05/14DEFarrokhFKhatibiGMember^Technical, Binding_28`23a5.5.5RRC i.e. no access below RRC (MAC/PHY)d197 2006/05/14DEFarrokhFKhatibiGMember^Technical, Binding_28`23a5.5.5ibiGMember/05/14XfcperhapsېWWperiod۳WWޒWperiodic۳W݂W9WperiodicallyޖWperspectiveܩW:WxWpertainsWWpertinent݂WphraseWWWWkWvWphrasing۱W"W,WnWqWphy+W Wphy/channelsWpicture۽WCW>WpiecesWpiggybackedWpiggybackingWW 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ۅWcandWW"W#W%W&W'W(W)W*W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WAWBWDWEWFWGWHWIWJWKWZW_W`WbWeWfWjWkWlWmWnWoWqWsWuWwWxWzW{W|W}W~WہWۄWۅWۆWۈWۊWۋWېWەW۳W۴W۶W۽W۾WWWWWWWWWWWWWWWW#W$W)W+W-W7W9W:W;W<W=W@WNWOWRWVWXWYW`WeWiWmWnWtWzW{WܕWܗWܛWܜWܟWܡWܤWܨWܩWܪWܫWܬWܭWܯWܰWܱWܳWܴWܹWܾWܿWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW%WbchangedW܂WTWchangesUWۃWۄW;W܏WWWOW{W9WchangesinradioconditionsofservingandtargetlinkVchangingWchannelWW܋Wchaper\WchapterܗWܘWܙWchemaހWނWchnageWchnagetodifferentVcicrcularWcivicݖWcivicaddresselementsuWclafiryWclafirytextasaboveVclarificatioxWeVVWclafirytextasaboveVVWWW#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_WbWWܱWWW>Wstart W*W8W@WstartingWWWWWWWstartingline1Vstartinglinep1018p5951Vstartinglinep225Vstartingpage118Vstartingpagep10p59Vstartingpagep22VstateWWW W<W3Wstate-1fWstatedW\WaW-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:pcmihhandovercommitisimproperfor802.21scopethefunctio3V8VmihhandovercommitshouldbeavailablebetweenmihfclientAVmihhandovercompleteisimproperfor802.21scopethefunct4V9VmihhandovercompleteshouldbeavailablebetweenmihfclienBVCVmihhandoverinitiateisimproperfor802.21scopethefunct1V6Viateisimproperfor802.21scopethefunct1V6V6Vmproperfor802.21scopethefunct1V6V6Vrinitiateisimproperfor802.21scopethefunct1V6V6VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV"VMVNVSVߋVߌVߑVmihhandoverinitiate/prepare/comܴVmihhandoverprepareisimproperfor802.21scopethefuncti2V7VްV޵VVVV$VPVUVߎVmihhandoverpreparerequestandresponsemessagesinremoteiV |bremovethesentencethisincludesthelistofnetworkoperat@Vremovethesystemmanagementanddefinethecapabilitydisco+VremovethewordrequestattheendofthesentenceQVremovetheseareinthebeginningofsentencealternatively(Vremovethiscommandsinceitiscoveredbyitme9oftable3VremovethisrowcompletelyܓVremovetransparentVremovetypehdrtlvmihfidݴVremovetypeienumberofoperatorsfromtable6[Vremoveunnecessary/misplacestatementasfollows VremoveuntilappenidxinlcudessuchhandovercommandscenariVremovedWWW۫W6W>WBWޗWW>WBWޗWޗW6W>WBWޗWޗWW۫W6W>WBWޗWޗWW۫W6W>WBWޗWޗWޗWWWWWWWWWWWWWWWWWWWWWWWWWWWWۭWWW:WKWwWdband@y!$,:oandresponsebydocumenturlorversionnumberonly@[andthedocumentcouldbe@annex@appended@application/xml@architecture@^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 QecAThe 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/07/20 06/07/19the status code for each interface. ccode for each interface. cry 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.}d583g2288b&bdeletemihoܠVdeleteoneofthemۦVdeleteoraddanewdefinitionVdeletetheaninformationrepositorypartVdeletethedefinition Vdeletethefirstsentenceofitema۪Vdeletethefollowingrowspage112line167VdeletethefollowingsentencewV۪V۪VW4WڟWڣWWdefinitionofnetworkoperatorinmiddlecolumniscicrcularكVdefinitionsٱWٸWٹWWBWWdelayقWdeleteYW]WMWOWڋWdeletemediaagnosticڋVdeleteoneofthemYVdeletethefirstsentenceofitema]VdeletedWdeliverWڻWdeliversWdeliveryWdemonٿWdependantWdependencemediaWdependent0WW(Wdepending-WWWWdependingonthetypeofmobilitysupportfordifferenttypeVs1b[Move section 5.3 to annex as an informational guideline for the possible 802.21 deployment.cATo the Mobile Device (MN), the only visible MIH entity is MIH PoS. How the MIH PoS and Non-PoS MIH communicates should be transparent. The whole section, especially parts about Figure 3, seem more like a guideline for the 802.21 deployment than a proper part of the standards. d108g2215iMathieu PeressejVRelated comments #128 #142 #108 #127 Figure 3 is definitely an example of deployment.wRejected 2006/07/20 2006/04/27 d nication Model in first part of draft. Section 5.3.2 may be moved into Annex but a separtae comment may need to be filed for that. 2006/05/16 2006/04/27 limitation of capability, assumed suboptimal solution. The goal should be to minimize administrative burden for MIH.d896 2006/05/14EHongFChengGMember^Technical, Binding_15`61a5.3, Binding_140`140a Annex A-1y used for references. 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 2006/07/20 2006/04/28mmendations 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 Appendix2d242g2244 2006/07/17EEE 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 Appendix2d242g2244 2006/05/17܃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 2006/07/20܄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 Type ConfigureRequestSet Link Configure Parameters Type (14) ConfigureStatus Status (245)>cbda, Golmie, Member^ Editorial_126`15b1fnadagolmiemember2V3V4V5V6V7V8V9V:V;V<V=V>V?V@VAVBVCVDVEVFVGVHVIVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VV܀V܁V܂V܃V܄V܅V܆V܇V܈V܉V܊V܋V܌V܍V܎V܏VܐVolveraWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWparkpeklWmWnWoWpekyewlVmVnVoVƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃a 6.3.4.3.2bAPoA maximum Data Rate@A>  33    33>c8PoA Data Rate The relevant information is max data rated430g2253wAccepted 2006/07/20 2006/04/28EPeretzFFeder^Technical, Non-binding_61`48bA[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 2006/07/20 2006/04/28EPeretzFFeder^Technical, Binding_62`11a Figure 22V!=ccoverageW:WWSWcoveredgWܯWcreatedcWcreatesWcriteriaWcriterion-WcriticalDWWcurrent!W,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:WdefiitevWWaEFarrokhFKhatibiGMember^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.d513ink 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.d513 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.d513bEFarrokhbEFarrokhWWh .observerLHventList, SupportedCommandList, SupportedISQueryTypeList ) 7.4.1.2 MIH_Capability_Discover.response MIH_Capability_Discover.response ( C SourceIdentifier, DestinationIdentifier, ResponseNetworkType, MacPoA, SupportedEventList, /29LfENada, 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/20gENada, Golmie, Member^ Editorial_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.}d583g2288bU!KEQiaobingFXieGMember^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 2006/07/20 2006/04/24obingFXieGMember^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 2006/07/20 2006/04/24 | | | | 2: Bit Error Rate | | | | 3: Frame Loss Rate before RTX | | | | ... | +--------+----------+---------------------------------| @Af 33M 33   33 f =bA1- Create a new IE with the following information at line 38: | No | Name of Information Element | Description | Representation | Length | | 1.1 | TYPE_IE_NETWORK_TYPE | Defines the link type | RADIUS NAS-Port-Type | 4 | attribute value which is a unique identifier B defined in http://www.iana.org/ assignments/radius-types, e.g., 15: Ethernet  )SbAi1- Add the following lines No Primitives Service Category Description 5 Link Detected Event A new L2 connectivity has been detected for use. 2- Update the rest of the numbers in the table 3- Reorder the list of Link Layer Primitives in section 7.3ic9The Link Detected is missing from the list of primitives.d499g2271wAccepted 2006/07/2015 TENada, Golmie, Member^Technical, Binding_69`7b_69`7b5plete 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. d502g2270.bfrom@front@function@,functional@!functions@0generic@geographical@going@greater@handing@handover:handovermode@ghandovershas@Xheader@hence@"hightlighten@however@:identifier@ieee802.11@if@iftypeielistofnetworktypeisapprovedreplacetypeie@important@iny3:inscopeofdefinitionsectionspecifywhichreferencepoint@inthissectionareprovidedintheappendix@include@includetheqosmodelandprimitivesdescribedincontributi@included@inclusion@indicate@#infoquerytype@~ndicate@#infoquerytype@~~#infoquerytype@~~querytype@~~~~iton@#infoquerytype@~inclusion@indicaiton@#infoquerytype@~pe@~pe@~pramaeters@W;W>WCWHWLWTWshow٠WW 0[ەESanjeevFAthalyeGMember^Technical, Non-binding_1`34a1.1bA,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 scoped2vThe 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 scoped2v2006/07/18.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 pa29SIEPeretzFFeder^ Editorial_86`64bA{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 2006/07/20 2006/04/28EPeretzFFeder^ 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 2006/07/20 2006/04/28 EPeretzFFeder^Technical, Non-binding_102`27b to control ....layer links. Clarify "uppers"d620g2258 2006/05/18 2006/04/28 EPeretzFFeder^Technical, Non-binding_102`27b006/05/14zcshowZW]WwWWWBWEWFWGWHWWWXWYWZW7W8WshowingWWshown%W&WWW7WWW|WWW6WWWWWWWWWWWWWWWWsideCWW0WsignalWdWsignaling/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\VsimilarlyWWZaannexa-1V-VVVVކVސVޑVޒVޗVannexa-2ޓVannexa2VsVannexbۀVannexb1VtVuVannexb2VvVannexcہVoVwVމVannex-3Rannex-a1bۀWb1WtWuWb2WvWcہWoWwWމWfigureWWfigure18Vfigure22Vtocb0JWۂWۉWHWMWRWTWUWVWWWXWYW\W|WܖW݁WWVW^Wގ1W4W6W0successܖV0unknown^V0-100\W0-255YW0-316W0-65535\W0-or-1 W0006&W001122334455~W0123456789ab~W04ݖW04txtiegeospatiallocationinformationݖV05ݕW05txtݕV0598SWSWݖVVVݖVVVݖVVVݖVVVrkaddressinformationV1createanewiewiththefollowinginformationatline38=V1dividetheflowintotwoinafigurelocalandremotecommyV\bservices"WAWpWuWW0WWW1W;WservingۇWWW!W"W#WsesAWsessionxWsWܚWWUWhWSWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhWhW[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>WAWBWDWJWPWTWshouldbeaddedtotable5anddefinedVjEEleanorFHepworthGMember^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. 4d425g2278v'Mention that values 7-255 are Reserved.wAccepted-ModifiedASS 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. 4d425g2278v'Mention that values 7-255 are Reserved.wAccepted-Modifiedt is difficult for 802.21 to try and specify an exhaustive list of all possible location determination schemes. 4d425g2278v'Mention that values 7-255 are Reserved.wAccepted-Modifiedepworth(cchangeۏW:W;WܝWW1W݇WWWWWWWW"W#W$W/WIWXWYWޖW5W>Wchangearealreadytomayalreadybe1Vchangemiheventregister/deregistertomiheventcommandsVchangepoaVchangetable33ainlinethatquotesdescribedintable33aVchangethefollowingtextaninterestinaparticularorgroIVchangeuserequipmentVtVVcle-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]W_WۻWWWWWWW=W@WJWKWLW[WܡWܪWܴWܷWW,W0WPWQW݊WWWW1WXWYW9Wnetworks-specificpWnetworkstechnologies$WnetworktypesݼWnewW'WAWۂWەWۚWWWWW#W=WHWRWSWTWUWVWWWXWcWdWkWmWܗWWWWWkWݍWݛWW W!W"W$W%WhW4W9WnewtextVnewlinkidentifiergWnewmacaddressۇWnewpoaidentifierWnextfWWWifierWWWpoaidentifierWWfiergWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWgWjshowZW,WvWshownXWshows,Wsip/mip/WslideXWsoWsome/W݄WspcifiedܾWspecific"WBWܾW WށWspecifiesWspecifyWމWsrcWstack,Wstacks"WstandardމWމWVWllWstreamline݄Wstring|WsuchWsuggestܾWsupercededWsupport WsupportedWsupportingBWsure"WtableWWݻWWWtechnologies,Wtechnology Wterminology?WtextWWW݄WTWthatBWWW,WTWthe<W?WBWZW۬WWWWW|WܾWWW W݄WݻWWW,WTWdWgWhWjWrWvWthemiheventregister/deregisterconfirmareokrVthemihisl-shapedtoshowthatitcancommunicatewithdif,Vthemihsapshouldbetechnologyindependenthoweverthecon VtheminimumdataratemayprovidevalueincertaincasesforV{ FbA 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}, | | | | C ܄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 2006/07/20܅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 2006/07/20܆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"4@5bd"recinterpretlWWWinterpretedܾWWinterprettedQWintertechnologyiWinterval\WޖWintoKW`WۊWWWWWW9W;W<W?Wintra-roamingܦWintra-roaminghandovermechanismsisundefinedܦVintra-technology?W@WintroduceWܫWWintroducetextexplainingmihnet-sapVintroducedW+WWintroducingWintroduction`WW WintuitiveJWinvokedW WWinvoking WinvolvedWWinvolves:Wip\WwW۪W۵WW:WWWWW WݍWW4Wip-configuration4WipaddressWipv4ޕWipv6WWޕWipv6routeradvertisementcannotfitintotheipaddresstypVirrelevanceWirrelevancenumberofoperatorsisofnorelevanceVVVVVVVVVVVVVVVVVWۇWۈWۉWۋWېWۓW۪WA;~^technical@Mh9܏ܕ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@Ä*2@Ä78@a5.1.3@M5.6.1@5.8.2@D6.1.8@ 6.3.3@7.3.11.1@g7.4.11@8.3.2@8.5.2.5@annexa-1@b06@Z1movetheconceptofhorizontalandverticalhandoverstos@11tlv@17@r2rdfdata@20@21-06-06xx-01-0000-a@osection7.4.7.2.2asdescribedin21-0@uacross@-add3gpp2after3gpp@Fan@*WfWkWicmedia-dependentۼWAWmedia-independent6media-specificWWmedium7WmeetingܕW8WmentionWWW3W;WHW?Wmentionthattheframeworksupportsuseofeitherl2orl3m3Vmentionthattheinformationservermaybepresenteitherlo;Vmentioned%WWWWWW,WLWMW|WވWmentionsWWmergedKW`WmerleyWmesage܅Wmessage6W7W8W9WiWۇWۈWۉWۊWۋWWWWWuWyWzW{WW WWWWݥWW W"W#W$W+W2WLW$W+W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W"WOWiW޳WW"WSWߑWWmessagetooWmethodۈW(W\WW,_‚ۃXa‚FM܃YZz{3‚G[ݜ‚Oݝ_‚Pۅ\bݞ‚Q]d‚R^ݟݠf?‚HST_`ݡޖ‚Uݢ‚Vݣݤ4‚Wcde‚fۊۍېaܐ‚b҃[gh0‚cdeݥݦуJKLM‚I݃ݧ5‚݇jk‚ی‚ރfgc݈ݨ@‚ۃhd‚i‚hjkݩPD`۠pۢƒӃ)p۩T%JW K‚!2ۄ܃ OM ^technicalhWiWjWkWlWmWnWoWpWsWuWvWwWyWzW{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۾WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWWWWWWW W!W"W#W$W%W&W(W)W*W+W,W-W1W?W@WAWBWCWFWHWJWKWLWMWOWRWSWTWUWVWWWXWYWZW\W`WbWcWdWeWhWkWmWnWqWsW|W܂WbreplaceafterupperlayerentitiesmakeshandoverdecisionwfVreplacealloccurencesofjust802.21byieee802.21consistܧVreplacealsoknowaslowerlayerswithalsoknownaslowerl6VreplacebothwitheitherۛVreplacebythisprimitiveisusedbyupperlayersVreplacebytesbyoctetsinentiredraftVreplaceconceptualabstractiondescribingtheinformationtr5Vreplacecurrentlinkactionvaluesbythevaluesdefinedin8.6VreplacedeliversthismessagetothemihfwithdeliversthisoVreplacedifferententitiesmayrregisterwithwithdifferentrVreplacefacilitieswithamorecleartermۢVreplacefig4ܮVreplacefigure21withsection2of21-06-0460-02-0000-bschvVreplacefigure23commonmihfframeformatwithfigure23miVreplacefurtherdeliverwithforwardqVreplaceinterfaceswithaccesstechnologies!VwardqVreplaceinterfaceswithaccesstechnologies!V!Vcbprovide@provided@ qos@^radio@rdf/xml@real@&refer@real@&refer@real@&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@OfEEleanorFHepworthGMember^ Editorial_50`31a 6.3.4.2.3b Add referencec0This need to be re-written as a proper referenced421g2256 2006/07/20 2006/04/28EEleanorFHepworthGMember^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/07/20 2006/04/28 EEleanorFHepworthGMember^Technical, Binding_50`31a 6.3.4.2.3b*Add more detail to the Cost IE definition.c of length which is followed by the value length.has not been defined d283g2443 2006/05/143cZbaddanotesayingthathandoverisalsoreferredtoashando)Vaddanoteunlessotherwisenotedmediareferstomethod/modVaddaparametertomihcapabilitydiscoveryresponse[VaddaperiodtothesentenceޒVaddasentenceafterline65Vaddasentenceatendofparagraphadditionallyoralternati۶VaddadditionaleventcodesbVaddannexestotheendoftocVaddanotherparameterlinktypeaVbVcVaddcallflowsasdescribedindcn21-06-0622-00-0000KVaddclarificationintextthatallreferencepointsarewithVaddclarificationtotextVaddcorrectreferenceVadddefinitionofhandoff/handoverܜVadddiscussionabouttherelationshipormappingbetweenmihDVaddexplanatorytextVaddflowdiagrams/usecasesandexplanatorytexttoclearlyܴVlowdiagrams/usecasesandexplanatorytexttoclearlyܴVܴVlowdiagrams/usecasesandexplanatorytexttoclearlyܴVܴV;bparametertypeFWGWparamtypeFWGWparentheses$Wparenthetical\Wparsing'Wpart,WAWQW_WpWuW۳WWsWIWWW'W1W3W4W5WpWparticularAW,WܾWSWIWpartnersܷWpartsW'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ܾWclengthoftypeielistofnetworksshouldbevariabletVlengthsWlessݴWWlets*WletterWlevelۈWܬWleverage݂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)bofferedAW6WofflineWoftenMWcWokWold W"W#W4WoldlinkactionۃWoldlinkidentifiergWWonW W,WAWMWOWPWQWTWUWVW_WcWfWiWpWWۂWېWۮWWWW\WdWeWhW܁W܅WܡWܪWܬWܶWܻWܾWWWWW WW)W,W0WIWfWWWWW W!W"W$W%W+W.W>WXWYWmWއW0W9Won-demandrW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WW<W=W]W(vbtocWWtocolpWxWtogether݃WtopZW]W>WtotalFWݗWtoward۠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!WSW1tableofcontentssectiontitlemissingVconly-WLWMWOWPWQWRWSWTWUWVWWW_WaWcWdWiWۄWۈW۸W۾WWWWWW'W+W1W@W[WeW|W܄WܪWܫWܬWܲWܻWWWWW WWWWCWJW_WuWݎWݳWW>WBWfW|WވWޔWޕWޖW:Wonlyshow4primitivesBVontainedܬWopaqueWopcodeݶWopenܩWޕWoperate WoperatesWW W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W W 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ہWNbClarify 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. d280g2291 2006/07/20 2006/04/242OEQiaobingFXieGMember^Technical, Binding_74`25a7.3.9.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 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@ CavHLink Configure Thresholds updates thresholds for Link Parameters Change.wAccepted 2006/07/20 bEFarrokhFKhatibiGMember^Technical, Binding_75`8a7.3.10bAdd additional event codescCLink Down add other causes: Authentication failure, Billing failured524wAccepted 2006/07/20 ddU FMbAChange 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/07/20 2006/04/24 d 2290 2006/05/18 2006/04/24ciThis is a link layer primitive which should only be generated by the MIH function, not by an upper layer.d523g2290 2006/05/18 2006/04/24r that is seeking to receive link layer event notifications.@Af 33  33  0  )c  TTf' blinesqWW4W=WSWܬW]Wlink W'WAWCWDWFWGWHWIWJWLWMWNWOWPWQWRWSWTWUWVWWW_WcWeWۂWۅWۉWېWەWۣWWWWW8W9W=WJWRWSWTWUWVWWWXW\W]W`WcWiWkWlWmW܂W܃W܄W܈WܐWܡWܫWܲWܳWܺWWWWWWWWWWW+WDWJWoWyWݍWݛWݺWݼWWWWWWWWWWW W!W#W1W2W3W4W5W6WGWHWWW^WaWbWcWlWrWsWyWzW{WޔWޕW3W5W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WW "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 GuptajAZ"...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.cfull'WWfully*WEWfuncionWfunction.WBWLWMWOWPWQWRWSWTWUWVWWWcWdWfWlWuWWۉWۋWېW۪W۾WW7WܫWܺWDW{W݄WWWWWW WW W!W"W%W'W+W,W0W4W5W7WJWKW1W3W5Wfunction/operationWfunctionalities:W:WW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W"W#W$W%W&WMWNWOWPWQWRWSWTWUWVWWW X\bFge Description Status Enumerated Success, Error, The status of the request Rejected 0: Success 1: Failure G 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  33fgure the Link_Going_Down notification. Effect on receipt The recipient responds immediately with Link_Going_Down_configure.confirm Add a primitivDNEQiaobingFXieGMember^Technical, Binding_37`43a6.1.6.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.d523g2290 2006/05/14 2006/04/24NEQiaobingFXieGMember^Technical, Binding_37`43a6.1.6ed by the MIH function, not by an upper layer.d523g2290 2006/05/14 2006/04/24NEQiaobingFXieGMember^Technical, Binding_37`43a6.1.6@Af 33  33  0  )c  TTfڧEFarrokhg3195x^boccurW^W9WoccurencesܧWoccurredRWoccurs5WܟW.WoctectWocteswWoctetJWۉWFWwWWݗWހWނWLW"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ەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱۲۳۴۵۶۷۸۹ۺۻۼ۽۾ۿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃buttar !"#$%&'()*+gomie23groetingܑܒܓܔܕܖܗܘܙܚLcdefintionWWdeifnitionWdelayWdelays WdeleteیWdeleted2WdeletingWWdeliver"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#W24݄cjReplace Figure 5 with a better description of the MIH Function location in the stack. Add additional text.d188g2222iMathieu PeressejPlease look at doc: 21-06-0612-00-0000-Reference_Network.ppt - Comment is related with comment number 187: we tried to streamline the picture too be more readable, and also provided some text.vYThe text as part of this comment can be harmonized with previous comment: Comment no 187.w Superceded 2006/07/20 2006/04/28 d ince in line 47 it then says this "assumed media-specific names and sets of primitives". d183g2229 2006/05/14 2006/04/284 2006/04/28EEleanorFHepworthGMember^ 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 2006/05/14 2006/04/285|REQiaobingFXieGMember^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.d543g2295vn, not by any upper layer.d543g2295vThe 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.@pted 2006/07/19_brelated WOWRWTWiWWW"W#W$W%WkWrelationwWܷW7WrelationshipDWWrelationship/mapping'WrelationshipsZW]WrelationshipsbetweeninformationelementsmustbeaddedtoZV]VrelaysWreleaseW W&Wrelevant,WUWYWWreliableeWreliably WrelyW WremainingFWwW_WݗW WremediesYWsWremedyZW]Wremote W-WiWpWuWW7WKW_W`WyWzWWݎWW WW#WiWޔWremotemihfreturnsthenecessaryinformationtothenmviaVWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWQW[W`WqWuWzbnmWnmsW8WDWnoW=W>W?WSWYW܋W|W݊WW WޔW6WnomihcommandlocalremoteremotedirectiondescriptionޔVnoprimitivesservicecategorydescriptionSVSVSVdescriptionSVSVcriptionSVSVdiagramhorizontallyrVstringٿWW WWWWstructureWWWsttausWsubjectڡWsublayersWsubmissionWsubnet+WsubscribedٮWsubsectionWWsubsectionof6.3.8shouldbedeletedVsubsequent WsuccessAWW WWsuccessfulWWsuchW WWW-W0WiWلWٓWWWڛWbmostW WgW݊WW&Wmove!WAWYW`WWWWWWQW݂W:W>Wmoveandmergethefirstparagraphof6.3.5into6.3.1intro`Vmovesection5.3toannexasaninformationalguidelineforVmovesection5.6.2.1intothemedia-dependentsapsection5.Vmovesection6.3.4tobebeforethecurrentsection6.3.3YVmovetable13csapprimitivestoannex>VmovetabletoinformativeannexVmovedWmovementWmsbݗWmsc݊WmuchVWmulti-technology!Wmulticast/broascastܻWmultihopݓWmultiple_WbW܁WܤWW܁WܤWWWtihopݓWmultiple_WbW܁WܤWWWWWWWWWWWWWWWWWWW 33M 33   33 fb21-06-06xx-01-0000-a݄W21-06-0xxx-00-0000-cyW21-06-0xxx-00-0000-izW21-06-0xxx-linkݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWݨWݩWݪWݫWݬWݮWݯWݰWݱWݻWWWWWWWWW21-06-500-02-0000-neۋW21-06-606-00-0000ܗWܘWܙW22|WW=WܬWހW23sW~W=WqWWނW23-43qW24wW=W݄WݿW7W245܄W25ܑWW26DWEWHW/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@Pprepare@7prevent@primitives@protocols@provide@proxy@question@Hrate@reason@receives@referencetointernet-draftshouldberemoved@mregisters@reject@relationships@+removesfromthewordsupportsinthelinethatquotesothe@toasn1@cy@eimplicationofcapabilityuniquet@tionsremoveimplicationofcapabilityuniquet@@ionsremoveimplicationofcapabilityuniquet@Yswitch@syntaxerrorinnetworksecurityandqualityofsecuritycap@Dsyntaxerrorinthisisusedtorespondtheresult@4systemmanagementhasbeenintroducedasaserviceherehowe@.take@?textneedsimprovement@that@that's@the$\gnmentofistoanyinformationelementshouldnotb@|# SbA 33  33  )c  TT    TT  )c    )c  nk 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@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.ternative is to disallow passing this link event to an MIH user.pcneededۈW W"WܼWWWW݉WݙWݬWݮWݯWݰWݱWݷWWWWWWWpWneedlesslyۿ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ۭWW.WconsistentWAWBWhWWW;WconsistentlyۜWWWܧWconsistentlyusethewordroamingVconsistsWW'WconsolidatedܤWconstantlyAWconstitute,Wcontact\WcontainkWnW۸W}WބWcontainedW:WހWނWcontainerYWcontainingHWjWmWcontainskWnW}WނWcontentݾWݿWcontentsWWlWyWzW{WcontextW\WW!W;Wcontextual_WbWcontinue1WcontinuityAW;Wcontextual_WbWcontinue1WcontinuityAWAW;Wcontextual_WbWcontinue1WcontinuityAWAWue1WcontinuityAWAW;Wcontextual_WbWcontinue1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1WUz 9sanjeevshikichiTshinkichiUVshuۂWWWWWWWWWWWWWWWWsactioniddoesGVtransactionsMWPWVWZWtransfer[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ۍE bingqiangFjiangGObserver^ Editorial_82`26a7.3.19.2cA)request source should be response source,)@A>    33  >d569g2242 2006/07/20 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 2006/07/20 2006/04/11 ۏEbingyunFquGObserver^ Editorial_139`2a8.6.1.2cA%Mobile Terminal change to Mobile Node%@A>    33  >d869g2245 2006/07/20 2006/04/1129ېE BingqiangFJiangGObserver^Technical, Non-binding_82`51a7.3.20binals and networks all can select a suitable network for the handover. Wd637g2252pی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 33fd602g2220 2006/07/20 2006-04-0718 2006/05/14 2006-04-0718PreferedPoAIdentifierList, AbortReason ) @Af 33  3333 33  3333 33fcAWupdates 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. Wd637g2252 )*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 2006/07/20 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 2006/07/20 2006/04/24 `64a5.8bnt to be described in the 802.21 spec, it must be explained. @A  33c....ives". d183g2229 2006/05/14 2006/04/28c 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/28cnewlinkidentifierݧWݯWݰWݱWWWnewmacmobilenodeݧWWnewpoamacWnewpoamacisnotneededifitispartofnewlinkidentifierVnext*WnihoޔWnmWWWWWWWWWW 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+WWfWiWjWbblerFWGWHWIWblock,W0bodiesWbold:WbooleanۂW4Wboth'W-WAW_WۛW۶Wbottom>Wbound:WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWܵ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_W`WbWeW۪WFWIWwWW0WMWݗWWWW7W8W@Wfirsttore-organizetheiesintoatreeormultipletreessbVbVbVbVbVsbVfix%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[\]^_`abcdefghijklmnopqrstuvwxxaENada, Golmie, Member^ Editorial_82`35bA-Replace "Specific t IE" with "Specific to IE"-@Af  33  33  33'  33)  33fcSyntax error in "Specific t IE"d570g2286 2006/07/20bENada, 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/07/20 cENada, Golmie, Member^Technical, Binding_84`15byntax error in "Specific t IE"d570g2286 2006/07/19bENada, Golmie, Member^Technical, Binding_83`65b5Add "SupportedISQueryTypeList" to the parameter list.c4The parameter "SupportedISQueryTypeList" is missing.d581g2287iJin Leeksuperceded by 577m Superceded 2006/07/19da, Golmie, Member^Technical, Binding_84`15bDnada2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎W܏WܐWfghijklmnopqrstuvwxyz{|}~ۀہsanjeevەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱۲۳۴۵۶۷۸۹ۺۻۼ۽۾ۿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃{t ۉbC 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 toD 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 Code(bremovemiddlesentenceremoveinthiscaseatendVremovemihcommandconfirmaswithorw/oitthemihcommandVremovemihcommandconfirmfromfigure18Vremovemihgetinfoconfirmaswithorw/oitthemihgetinVremovemihgetinfoconfirmfromfigure22VetinVremovemihgetinfoconfirmfromfigure22VVoconfirmfromfigure22VVigure22VVwithbeminimalڇVrephrasesWvWrephrasecollectsinformationonnetworksinitslocalitysivVrephreaseمWrephreasethetwosentencesasfollowsinanycasethemihfمVreplaceNWRWTWUWtW٬W٭WٯWٰWٱWٳWٴWٵWٶWٺWٽپٿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWkWwWڌWڻWڽWRV2vby comment 212w Superceded 2006/07/20 2006/04/28Marked EEleanorFHepworthGMember^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".clText does not reflect the dependency of the transport mechanism on the location of the MIHF in the network. d235g2233wAccepted 2006/07/20 2006/04/28cjOn the left side of the "MIH Function" block, the figure should have another block called "L3 transport". d213g2246i Vivek Guptacal, 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 Gupta1EAjayFRajkumarGMember^Technical, Binding_30`36a5.6.1l, Binding_30`36a5.6.1oܴEVivekFGuptaGMember^Technical, Binding_41a6.2.5.1bA^Add flow diagrams/Use cases and explanatory text to clearly clarify how the above primitives are: 1] different than L3 Mobility Mgmt handover signaling 2] Help in heterogeneous network selection decision making 3] Provide support for network initiated handovers for networks like WiMax If this cannot be done, then these commands need to be deleted.^cMIH Handover Initiate/Prepare/Commit/Complete Clearly explain how these commands are used in inter-technology handovers to communicate network selection (decision making), and are different than L3 mobility management protocols.d299g3254 2006/07/20T-4ܵEVivekFGuptar Initiate/Prepare/Commit/Complete Clearly explain how these commands are used in inter-technology handovers to communicate network selection (decision making), and are different than L3 mobility management protocols.d299g3254 2006/05/14T-4ܵEVivekFGupta/14!\vlist[WۓW-WJWKWܐWܗWWWlistofnetworksismoreappropriateJVlistedܐWlists۳WWlocal۳W4W5Wlocally;WlocationܽWlogical۪WlongWlookWWNWloss۵WlotܗWlowWlower۵WW4W5Wlower-layer*WlsapWm4WmacWWWmacnewaccessrouterdeWmacnewpoaeWmacoldaccessrouterdeWmailSWmaintained۳Wmake۵WW WW,WfWmakemihfunctionhorizontalinfigure1,VmakesimilarchangesthroughoutthedocumentVmaking*WmanagementBW4W5W`WmandateܽWmandatoryݜWoWmanyZWܗWWmappingSWmatch۔WmayQWRWSWTWۆWۊWۋWۛW۳WWܐWܽWWWW1W2WBWSW{WݜW"W*WOWSWfWmeanۆWWoWmechanismW;Wmechanismsissing WmmeWC)chandover"W/W0W1W2W3W4W5W6W7W8W9W?W@WfWjWkWmWnWoWzW{W|W}W~WہWۂWۃWۅWۆWۇWۋWWWW-W1W:WfW܉W܏WܜWܠWܤWܦWܳWܴWWW W|W݂WݍWݏWݐWWWWW!W"W#W*W.W7WAWiWjWnWޗW1W4W6WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW& YbAThere 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 . cAThe 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. / dÃT0ÃT@ÃTPZÃT`ܽÃTpܾÃTÃT)ÃT1ÃUÃU IÃU0`ÃU@_ÃUPaÃU`*ÃUpܿÃUJÃUKÃULÃVݙÃV bÃV0ÃV@[ÃVPÃV`MÃVp\ÃVÃVÃV݀ÃWBÃW ÃW0ÃW@ÃWPݚÃW`]ÃWpÃW^ÃWvÃWÃXÃX _ÃX0zÃX@BÃXPxUÃ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 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 pa v IcA 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." d441g2260 2006/07/20JENada, Golmie, Member^Technical, Non-binding_56`1bEReplace "List of Networks (Link Types)" with "List of Network types".cQThe understanding of the title "List of Networks (Link Types)" is not intuitive. d447g2261v$List of Networks is more appropriatewRejected 2006/07/20KENada, Golmie, Member^Technical, Non-binding_56`9btIf TYPE_IE_LIST_OF_NETWORK_TYPE is approved, replace "TYPE_IE_LIST_OF_NETWORKS" with "TYPE_IE_LIST_OF_NETWORK_TYPE".c0The Type must match the one defined in Table 6. d448g2262v-TYPE_IE_LIST_OF_NETWORK_TYPE is Not approved.wRejected 2006/07/20LENada, Golmie, Member^Technical, Non-binding_56#M#^non-bindingۂWۃWۄWۇWۈWۉWۊWۋWێWېWەW۪W۫W۵W۷WWWWWW W W WWWWW#W$W)W*W-W1WAWBWFWJWKWLWMWZW`WeWhWmWqWsW|W܏WܛWܜWܢWܩWܯWܰWܲWܺWWWWWWWWWWWWWWWWW+W3WAWBWJWLWSWVWWWZWkWxWyWzW|W݊WݏWݵWݽWWWWWWWWW W WWWWWW WiWjWkWކWއWޕW0W1W2W3W4W5W6W7W8W9W<W>W@WAWBWCWDWWWW+W-W0W2W3W6W9W;W<W=W>W?W@WAWBWCWFWPW`WfWkWقWُWِW٤W٨WٮWٷWWWW ۊbC SourceIdentifier, DestinationIdentifier, ResponseNetworkType, MacPoA, SupportedEventList, De SupportedCommandList )/@Af 33  33  33fc MacPoA, SupportedEventList, jotherۂۃۄ-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+VthenorthboundprimitivegeneratedlocallyinresponseJVtheoverheadinexchangeofinformationshouldbeminimizedVtheparametersoftheprimitiveareasfollowsۂVtheprimitiveparametersareasfollowsېVthethirdprimitiveintheflowmihgetinfoconfirmBVthevaluefieldofradiuslocation-informationݘVtheirWܷWthelengthvWthemWW]WfWuWxWۦWܿW݋WWCWjWuWxWۦWܿW݋WWCWjWjWW]WfWuWxWۦWܿW݋WWCWjWjWW]WfWuWxWۦWܿW݋WWCWjWjW߸W߸W߸W߸W߸W߸W߸W߸W߸W߸W߸W"bsections>WoWWWWLWMWPWsecurity#WەW<WܢWܾW1WseeۅWۆWۇWۈWۯWWW`WcWjW#W]WWkWDWseeitemabove#Vseepage58lines1-21]VseepreviouscommentۯVseerelatedcontribution21-06-0644-02-0000-mkVseetheproposal21-06-0630-00-0000-pforamendmentofmihsۆVseetheproposal21-06-0631-00-0000-pforamendmentoflinkۅVseethesuggestedannexa-2intheproposal21-06-0656-00-00DVstingWinterfaceWqWW!WzWڎWinterfacesWWWkW{WintermediateAWinternal}WلWinternally٢Winternet-Winterpretation_WintervalWWinto W W WWuWٴWGWڡWintra-roaming^Wintra-roamingshouldbedefinedthewhole2ndsentenceinth^Vintra-technology-WHWintroducedIWintroductionوWinvokedVWfhWlearnediWhjdoesZWWvWdoesthisinterferewithsessionidifweestablishasessioVdoesn't Wdraft?WdstWe۬WܾWeachvWelementWWend-to-endWentityrWenumerator|WestablishWetc/WܾWeven"WZWeventhecurrentschemadiagramisnotcorrectanddoesnotZVeventrWeventsWexampleW WWexplainܶWexplained/WWeofdeploymentVfirstKWflows>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ۧW۶WW#W,WܞWW;WWWW WZWmns9WmobNWmobile,WAWVW_WpWuWWۘWۜW۞WW3W4WܝWܡWIWQW݊WWWW W"W#W$W3W7WOWޏWޕW4WAWBWCWmobilenodeoruserequipmentVmobile-assisted݊Wmobile-assistednetwork-controlledhandover݊Vmobile-controlled݊W۝WWܤ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 WWW*WoperationsfWoperatorW W"W@W݂WWWWWWWWWWWWWoptionalWXWWW 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'W1WCWZWWWWWWWWbWothersW EEleanorFHepworthGMember^Technical, Binding_113`9a8.3.1bIf 0-or-1 transaction semantics are required, use an underlying transport which can provide it. Else state explicitly that the protocol cannot guarantee that a transaction is invoked at most once. chere is no mechanism to determine that a packet is a duplicate. d716g2297vsee issue 34. wDeferredy`use large Transaction ID value with assignment method guaranteeing uniqueness within the session 2006/05/22 2006/04/28 EEleanorFHepworthGMember^Technical, Binding_113`9a8.3.1bIf 0-or-1 transaction semantics are required, use an underlying transport which can provide it. Else state explicitly that the protocol cannot guarantee that a transaction is invoked at most once. ce network). d709g2293 2006/05/18 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_113`1a8.3.1cum fragment size is established. !d680g2288xbisއ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 !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ۀہzhuangۉۋیێLmember !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ۀہۑےۓ۔ەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱cotherwiseܫWWouiWour^Wout"WqWsWWۊWWܡWܼWWW WW"W%W*W>W8WoutsideWܛWܭW WWXWYWoutstandingWoverW-WܘWWWWWWWW+W<Wover-the-airPWover/underWoverallW݃WoverheadWoverkilljWkWmWnWoWzW{W|W}W~WہWWmWnWoWzW{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‚90ۖbUnless 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"d4 2006/07/20ۗESanjeevFAthalyeGMember^ Editorial_1`52a1.2b7Suggest using "Additionally" instead of "Alternatively"cSemantics correctiond7 2006/07/20ۘESanjeevFAthalyeGMember^ Editorial_1`62a1.2bh "... cooperative use of information available at the mobile terminal and at network infrastructure ..."cSuggest rephrasingd9 2006/07/20ۙESanjeevFAthalyeGMember^ Editorial_2`34a1.2b,Remove either "different" or "heterogeneous"cRemove redundancyd13 2006/07/20ۚESanjeevFAthalyeGMember^ Editorial_2`23-24a1.2bY"... the creation therein of a new entity... " to " ... a new entity created therein ..."cFor better sentence flowd15 2006/07/20a0/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 2006/07/200EDavid FFamolari^ Editorial_10`1a4cCRDF (Resource Description Framework) should be added to Section 4.d82g2405 2006/07/201E 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. d50g2406vhDelete "heterogeneous interfaces" from defn of Seamless handover and replace with "Points of Attachment"wAccepted-Modified 2006/07/20avid FFamolari^ Editorial_8`42a3bWChange the definition to: " N-layer - the N-th layer of the layered protocol stack. "dated. d438g2456 2006/05/14*EDasFSubir T>mRejectedvby comment 597w Superceded 2006/07/20 2006/04/24 ections 8.5.3.19 and 8.5.3.20.&@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  33d854g2274i Ronny KimmRejected 2006/07/20 2006/04/24 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 KimmRejected 2006/05/14 2006/04/24 emberW sܖEWolfgangFGroetingGMember^Technical, Binding_107`53a 7.4.15.2.2bAFChange 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.d670g2265 2006/07/19 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@d in figure 28d756g2264 2006/05/14 2006.03.05F27?/ bA# Accept 21-06-0627-00-0000_IEs.doc#@A 33cuAdditional IE is needed under General IE . Also there is no need for (LinkType+Operator) under POA specific operationd362g2447i Vivek GuptakThe doc number should be 627. The current organization of IEs is ok. They need to be specified for an individual network based on (link type + operator) combination TYPE_IE_NETWORK_CAPABILITIES may be further examined/investigated for inclusion.mRejectedvAComment is in two parts. Part 1 is to add TYPE_IE_NETWORK_CAPABILITIES under General. Part 2 is to move IEs 2.2, 2.3 and 2.4 from Access to General as well. Part 1: Discussion that access technology e.g. 802.16, .11 etc is appropriate, services are not implemented in the access network but deeper in. Concern if new IE is distinct from 4.2 TYPE_IE_POA_ CAPABILITIES. PoA refers to L2 point of attachment, not PoS. Comment that access router info IE is missing. Text for completing th[\{ERonnyFKimGMember^Technical, Binding_33`1a6.1bYAccept text changes in the contribution "21-06-0611-00-0000-MIH protocol section update".f the service primitive. - MIH_Get_Info.response => MIH_Get_Info.confirm (From MIHF to MIHF User) 3. Change the name of "Information Server" to "Remote MIHF User (Information Server)" The detail flow will be shown in 21-06-0xxx-00-0000-Information_Flow.pptcLike command service flow in section 6.2.4, the information service flow is confusing as the local and remote information flow are mixed.d472g3918 2006/07/01 2006-04-3022{ERonnyFKimGMember^Technical, Binding_33`1a6.1bYAccept text changes in the contribution "21-06-0611-00-0000-MIH protocol section update".-binding_62a6.3.9bory from client's perspective, does that mean they can all be igoned?d254g3208 2006/05/14yEEunahFKimGMembered?d254g3208 2006/05/14yEEunahFKimGMember48`22aAnnex B12cinformativeܪWWWWinformed#WޖWinforquerytype}WinfrastructureWinfromationWinitiate/W0W1W5W6WۂWۃWۋWېW܏WݍW1Winitiate/prepare/comܴWinitiated-W݊WW8Winitiates#WinitiationWed-W݊WW8Winitiates#W#W#W#W#W#W#W#W#W#W#W#W#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:ޔEVidalFAlbertGMember^Technical, Binding_41`26a6.2.5.1bA6.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 Direc------------------------------------------------------------------------------------------ | No | MIH Command | (L)ocal, (R)emote | Remote Direc 33>d878g2445 2006/05/14ޒEKenichiFTaniuchi^ Editorial_141`20a Annex A-1badd a period to the sentence. cmissing a period. d880g2446 2006/05/14ޓEKenichiFTaniuchifbeitherintable6itshouldbevariableorthistableshould%VeitherprovidesometextsordeletethefigureVeitherremovethementionof802.3ethernetinthelabelofqVeitherreplacewitheuqivalentprimitivesthataredefinediކVeithersaytheframestructureVeithertheseshouldbedeletedorwrittenasobjectiveandm-VeitherwedeletethisdependencyforinteroperabilityorweVelementXWWW=WܕW|Welements?WAWXWZW]WcWdWuWW#WCWHW|WWWބWޅWeliminatePWeliminates Welse WWބWޅWeliminatePWeliminates W WWބWޅWeliminatePWPWWWWWWWWWWWW)WUWYWem2WembeddedWtWݸWWemoteޔWemptyۂWencapsulate WޞWWencapsulatedWޏWencodeTWUWVWWWXWcWencodedݘWހWW HbA 33  Z  33[  ^  )ci  s  )cu  x  )c    )c    )c    )c    )c    )c&)c'  )chem W WYWWthemselvesWthen2W3W@WٮWڝWthere-WAWWWWWWWWWWtherearetwopossibleremediesforthisVtherearetwopotentialremediesVthereinMWthese WnWٮW1W8W^WrWW Wthey W WW-WٮW8WWWWW^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<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 2006/07/20=QvfilterܗWfirstݓWnWfixedܗWflexibilityZWflow0WۋW۵WW`WW>WBWKWiWfolksSWfollowingەWWfollowsۛW۳WWWWfolowslWforBWIWJWQWRWSWTWZWfWۆWۈWۊWۋWۓWW W@WRWqWܗWܛWܿWWWWWWWWW;WaW{WݓWݳWݽWW4W5WSWVW^W`WdWiWoWforeachaccessnetworkthereisanoperatorandsametypeo@Vforwhatscenariosl3doyoureallyneedthisۈVforce:Wforeign"WޏWformZWformatܗWoctets) followed by TLV for each Operator Identifier " to: " A list of Oerator Identifier TLVs. " @6`58a 6.3.6.3.2bAChange the Value field from: " Number of Operators (4 octets) followed by TLV for each Operator Identifier " to: " A list of Oerator Identifier TLVs. " @( bseekingLWېW\WseemsWsegmentWWsegmentsRWselectAWuWۂWۋW~WselecteduWselectingSWselection WܡWܴWW7Wselector.WAWselectsܡWsemanticsۂWېW\WܘW WsendۓWW"W$W/WsendxmlbeforetransmissionVsendingVW#WsendmsgWsenetenceWsensoryۖWWsent۵WW\WW%WWsensoryۖ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^ 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 2006/07/20 2006/04/24 TEQiaobingFXieGMember^Technical, Binding_78`53a7.3.14.3b^Technical, Binding!3ۑETakashiFAramakiGMember^Technical, Binding_45`19a6.3.2b.Wait until the referenced 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)d368g2211vby comment 369w Superceded 2006/07/206 ےETakashiFAramakiGMember^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 Dasg 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/07/056 ےETakashiFAramakiGMember^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 Das Subir Dasive The primitive payI f^bindingWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWW W%W'W0W1W2W:W;WCWDWEWFWHWOWPWUWXWYW[W\W]W_W`WaWbWhWoWuW{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ݾWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW ?bA   33    TTZ  \  TT_  TTs  TTQ  T  TTe  TT&  TTon. 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). '@upper layer, which is improper.)@A  33d854g2274 2006/05/14 2006/04/24?EQiaobingFXieGMemberbbline|W~W۠WۮWWW7W=WHW`WdWkWuWW(W)W,W/WݳWW,W0W1W4W5W:W=Wline26setthevalueinformationtocostofaccessingthenHVline167WWۅ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ۢWW W!WWWWWKWPW:W<WgenerallyۉWW݂Wgenerallydon'tunderstandwhatthepurposeofthisprimitivVgenerateZWWWgeneratedLWMWcWdWۅWZWWJWKWޖW5Wgenerates#WgeneratingaWbWcWgenerationWgenericۼWWWgenericmayconveyconflictingnotionwrtmedia-dependentۼVgeographicWSW\Wgeographical=WIWWgeran۽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 coY5bdefineintra-roamingܦVdefineitas0forversion1thisdraftothervaluesforfutVVdefineitproperlyےV۔VVdefinemigrationstrategyasnewlinktypesareintroducedVdefinemorefalurecodesifdeemednecessaryVdefinepagingrelatedeventsVdefinethelistofactionsthatcanbetakenandprovideenchVdefinethescopingrulesforthetidVefinesAWpW۟W=WdefiningAWdefinitevWdefinitionW W#WJWZW]W۴W۶WWW W WWW/W3W4W:W`WcWܜWܝWܪWܬWWdefinitionofnetworkoperatorinmiddlecolumniscicrcularVdefinitions:WAWBWWWdefinitonܞWdelayWdelet)WdeletekWnWvWwWۦW۪WWWW W W WWWWWWW"WܠWܭWdeleteheterogeneousVteoraddanewdefinitionV \bB 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 )C 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 crelationshipsZW]WrelativeۊWNWrelayWreleaseW W&WrelevanceۀWWrelevant۳W;WLWWWrelevenceWreliabilityeWrelies۳W݂WremainderWremainingFWwWW Wremote-WuW۷WWW7W9WOWܖWܫWWWKWyWzW{WWW WWWW#W3W>WKWgWhWiWremotemihfreturnsthenecessaryinformationviaappropriatVremoveۙW۱W۷WWWWWܱWWPWWWWWWWW*WremoveapparentlimitationsVremoveimplicationthataccessisremotesinceinformationm۷VremoveimpliedlimitationbetterexplainuseVremovelimitationsVremovelimitationsremoveimplicationofcapabilityuniquetPVremoveredundancyۙVremovereferencestoasn1VremovesfromnotifiesinthefollowingsentencethemihmigVu0csuchW\WۃWۉWWWW:WܬWܰWܿWWWWW%W\WaWeW|W݂WݏWWWWW*W7WPWiWsuddenlyWsufferingWW[Wsufficient?W@WuW(Wsufficiently:W;W<W=W>WBWEW[W^WjWkWmWnWoWpWuWvWzW{W|W}W~WہWہWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsingۘVsuggestedۂWWqWsuggestedrephrasingofgapsinradiocoverageVsuggestednewlinkidenݬWWsuggestednewpoaidentݬWW?bacross"W?WAWۻWQWW1W3Wacrossheterogeneousnetworkinterfacesupperlayersmayuti"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?gcsystemsWWWtaWtableWEWZWhWیWېWWWWWWW%W&W)WGWKWLW܁WܼWWWWWWWEWݛWݿWWWWWWW\WlWހWށWނWރW;W>WAWBWCWtable22needstoberevisedހVtable23needstoberevisedނVtable24ismissingrightaftertable23ݿVtable6doesnotdefineanylengthhoweverthisis4octets)Vtablemissingthisisacapabilitynegotiation\Vtable-6ܷWtable-7ܹWtablesWWation\Vtable-6ܷWtable-7ܹWtablesWWWWWWWWWWWWWWWWWWWMWlatterWZWaintained? g2641 2006/04/29~EEleanorFHepworthGMember^Technical, Non-binding_59`43g2642 2006/04/28pTvgBoth data representation formats need to be provided as options due to differences in query mechanisms.wRejected 2006/07/20 2006/04/28 EEleanorFHepworthGMember^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/07/20 2006/04/28 a6.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 Ohbak-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 Ohbak@disagree, It is not advisable to restrict IS representation now.king_63`9a7.1.152`19Es n!bfunctionspWuWxW݂Wfurther WWWWqWݗW"W$WfutureOWWRWWVWg?WWWۖW۸WW=WWWSW_W݊WݎWݔWWW"W$W%WހWgalinkteardownresponseisissuedVgainpWgathers݊Wgeneral,W_WW<WgeneratedLWMWdWېWZW\WWJWޖW3W5W@Wgenerates#Wgeneration\W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WgenericFWGWHWIWJWۼWYWW2WWWWWWWWWWW3W4W5W6W7WdWeWfWgWhWߢWߣWߤWߥWߦWWWWWWWW W!W"WW6GMember^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.@A  33d841g2266vby comment 495w Superceded 2006/07/20 2006/04/24 33d758g2265 2006/05/14 2006/04/24196EQiaobingFXieGMember^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.@A  33d841g2266 2006/05/14(cg_WaWiW۪WWWWWWWWWWWWWWW0WBW\WWW"W$W%W~WސW>WgalileoWgapsWlity@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ٿWWtargetgWtayloredfWfb c>Non-binding_86`48a7.4.14bsee related contribution #xxxcAadopt mih registration@A  33d598g2252 2006/07/19 2005/11/06request and response primitives seem to have the same functionality already defined for fast mobile-ip handover signaling. This may cause some redundancy in 802.21 definitions.@A  33d597g2227 2006/05/14 2005/11/06kESrinivasF Sreemanthula^Technical, Non-binding_86`48a7.4.14b^Request to reconsider the use cases for MIH network information and remove them if not needed.cAMIH Network Address Information request and response primitives seem to have the same functionality already defined for fast mobile-ip handover signaling. This may cause some redundancy in 802.21 definitions.@A  33d597g2227 2006/05/14 2005/11/06kESrinivasF Sreemanthulatly evolve. At D.gcsyntaxerrorinwhenapredictiveevenexpectedtooccur^VsyntaxerrorinwhichsttausmayVsyntaxerrorinwhirepVsyntaxerrorsintheremainingoctesieexcludingthefirstwVsystemۇWەW۽WW+W6W|WWWW;WXWYWsystemmanagementhasbeenintroducedasaserviceherehowe+Vroducedasaserviceherehowe+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 co>AVvas per comment 555.wAccepted-Modified 2006/07/20 2006/04/24WEQiaobingFXieGMember^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 2006/07/20 2006/04/249 2006/07/19 2006/04/24fUvcdifferences@differentiate@discovered@8document@doesn't@Edraft@each@43usinganmihcompleterequestside@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@ZbConsider removing, or better explaining intent of figure. The sole sentence that refers to figure should be at the beginning of a new paragraph. Some terms in figure need to be defined, if retained.cIntent of figure 24 uncleard712i Qiaobing XiejDelete figure 24.mAccepted-Modifiedvsee 704w Superceded 2006/07/20 d hVhVidhVhVessionidhVhVhVidhVhVhVhVhVhVhVhVhVhVhVhVhVhVidhVhVidhVhVhVhVhVhVidhVhVhVhVaboutthesessionidhVhVhVidhVhVhVdhVhVhVhVssionidhVhVhVhVhVProjection" 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 ".~FGbagreedW`WaidݶWalgorithm WalgorithmsW WalignWalignterminologyoradddefinitionsVall.WZW]WۜW۠W#WRWYWܐWܧWܷWܼWܽWWWWW:W݃WWWWW WmW9WallocatableWallocateWallocationWWallowbW۳W۵WTWUWVWWWXWcWWWWalloweventstobesentfromupperlayersorfrommihfusers۵VallowsAW_WpWVWXWalreadyRWuWWUWYWWYWWWYWWW*W*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 coxggregguimingۂWguoۂWۃWۄWۇWۈWguojunxiangۃVۄVguojunxiangshuguimingۂVhonghong-yon3cfig/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ۂWېW*WRWYW\W_WjWkW~W܁W܄WWWWmoWWW8WހWށWނWރW45W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wrting 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/28 lENada, 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 2006/07/20mENada, 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  33f~jtlvsWto"W<W@WaWWWWWW|WܶWܼWܾWWWWWW W݄WWWW+W,WTWjWrWvWމWtoo݄Wtop,WtransactionWtransmissionWWtransportWtried݄WtwoܾWWtypeWܼWܾWWtypeieqosinformationelementisdefinedinlb1line46pVtypes Wunderstanding,WuniqueTWupdateuW+Wupper"W/WWurlމWuseW"W|WWusecontentsinsteadoftableofcontentsassectiontitleVusetlvsforvariablepoaidentifierrepresentationVused?WBW۬WWWWWjWwell?W+Wwere>Wwhat WwhenKWwhereܶWwhichBW W>WwholeW Wwill>WwithBWuWWWW W݄W+W,W>Wwithin,WTWwithoutBWwlan Wwman Wwould W>WKWxmlBWW5V`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.d560g229978`53, Binding.S[ctakeۅWW?Wtaken6WtakesWtalk#WWtalks`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_WaWWOWܰWWWxW<W=W>Winfofilter<Winfomration%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*WV5FXEQiaobingFXieGMember^Technical, Binding_47`42a6.3.3bbAChange 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.d563g2300 2006/07/19 2006/04/24XEQiaobingFXieGMember^Technical, Binding_47`42a6.3.3b42a6.3.3btion, not by any upper layer.d560g2299 2006/05/14 2006/04/24McwhyEWuWۅWWWW'W*WWWWWWWWW W W,WdWwhydoeslinkgoingdownprovideinformationaboutnewpoaodVwhyisho-typeusefulhigherlayersmightcareaboutchangesVwhyisitadditionalparametersinsteadofvalue*VwhyismihflinkedtohardwareinterfaceVwhyisthemih-functionblockl-shapedthetextfromline41,VwildlySWSWSWSWSWSWSWSWd 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/28nvnboInclude 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.d92g2299vSame as comment 90w Superceded 2006/07/20 d 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. d632g2298 2006/05/14nENada, Golmie, Member^Technical, Binding_13`52a5.1.3 Identifier of the link to configureB  a specific link."05/024csyntaxerrorinresultoftryingtoconiferthelinklVsyntaxerrorinspecifictieaVsyntaxerrorinstatusofhnadoverrequest܀Vsyntaxerrorinthealinkeventrollback܃VsyntaxerrorintheencodingformatisdefinedastablebeloGVsyntaxerrorinthefirstsentenceoftheserviceprimitive5VsyntaxerrorintheformatofthelengthfieldshallbepertvVsyntaxerrorinthelistofeventsthatmaycarriedinamesyVzVsyntaxerrorinthenumberofparametersthatmayincludedi~Vsyntaxerrorintheueisknowntothenetworkbut܋Vsyntaxerrorinthisisusedtorespondtheresult܆VsyntaxerrorinvaluesraeassignedxVVsyntaxerrorinvaluesraeassignedxVxVdtheresult܆V܆V܋V~Vsyntaxerrorintheueisknowntothenetworkbut܋V܋VyntaxerrorsintheremainingoctesieexcludingthefirstwVsystemۇWەW۽WW+WHT]cusedNWiWۅWۈWۡW۬WWW WWkWwW܂W܆WܗWܱWܴWܺWܿWWWWWWWW WW2WaWfWݴWWWW!W%W.W>WAW_W`W~WއWޗW4Wused/whyWusefaulWuseful_WۆWWWWW>Wusefulness_WaWuseless_WaWuser+W-W.WSWۂWۊWW܊WWWKWޖW?WusersېW۪W۵W7WܐW W0WW7W>WaWbWcWgW9WusesWcWgW9WusesWWWW7W>WaWbWcWgW9WusesWWWW7W>WaWbWcWgW9WusesWW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WVusingradiusrelateddefinitionmaybeagoodideabutitalۓVzIbnot W#W'W.WAWNWۂWۈWەWۜWWWW#W,WRWVWXW܋WܟWܬWW1WTWjWtW݊WWWWWTWWWjWހWނW4W9W<Wnotcontainedmimetypeapplication/xmlapplication/sparql-qހVnotcontainedmimetypeapplication/xmlapplication/sparql-rނVnotsuremihinterfaceswithlowerlayerarearespecifiedin1V9W9W9W9W9W9W9W9W9W9W9W9Wparql-qހVnotcontainedmimetypeapplication/xmlapplication/sparql-rނVnotsuremihinterfaceswithlowerlayerarearespecifiedin1VnoteuW#WHWW)WnotedۖWWnothingށWnotificationOWPWQWRWSWTWUWVWWW\WޕWޖWWWWWWWWWWmWnWoWpWqWrWsWtWuW߫W߬W߭W߮W߯W߰W߱W߲W߳WWWWWybtechnologies?WsW۱W!WWWW WtechnologyWWWW0WJWW2WpWtechnology-independe W 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݀WmWusageofinformationserviceschemadescribledin6.3.8ist݀Vuse_W`WbWjWkWmWnWoWwWzWۣW۶W۸WۻW۽WWWWWWW,W9W;W=WOWRWYWܥWܩWܯWWWWWWWWWWW3W8WGWeWfWlWݔWWWWW W^WoWއWޗW@WuseofmacaddressisnottechnologyneutralenoughtoincorVuseofnetworkbasedserverasasolesourceofinformation۶VuseofroamingisconfusingۻVSWۂWۊWW܊WusersېW۪W۵W7WܐWusesWusing"W_WaWbWjWkWmWnWoWwWzW{W|W}W~WہWۑWےWۓWWeWܬWWusingmihftoqueryandreserveresourcesrequiredforahan"VusingradiusrelateddefinitionmaybeagoodideabutitalۓVOWC ZvAno 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 2006/07/20 2006/04/24Marked6ons 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.mAcceptedv.d560g2299 2006/05/14 2006/04/24 bforcingWforeign"W%WformvWWformally.WformatrWsWvWWGWHWqWvWWWWW~WݘWݿWWWWW:WqWހWނWformatspWvWformattedۉWނWforwardlWqW Wforwarding W6WfoundpWfour>WfourthWfragmentationWframeFWGWHWIWJWpWsWvWۉWYWqWWWWWW'WframesrWWframework3W3W3WW'WframesrWWframework3W3W3W3WW'WframesrWWframework3W3WamesrWWframework3W3WWWW'WframesrWWframework3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WVshow٠WWshowingW cwhichۄWۉWۊWۋWېWۑWەW۳WWWWW'W:WPWZW\WcWkWW܄WܗWܟWܡWܪWܺWWWWWWWWWWWWW W WW W+W:WaWfWݍWݏWWWWW"W#W$W'W7WEWFWGWHWOWaWbWcWhW:WLW:W:W:W:WHW:W:W:W:W:W:W:W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$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-cdefinitionsWWWFWGWHWIWNWZW]WۦW.W1W:W;W܏WܞWWWjWdefinitionsofhorizontalhandoverandverticalhandoverare:V&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W'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ېW۴cR1 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.mAcceptedvChange figure 3. Ref Points R1 and R3 need to be interfaces between MN and Network entity and not between two network entities as shown in Fig 3.wAccepted 2006/07/20F-3 ۵ESanjeevFAthalyeGMember^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 Guptakek Guptakts and they appear as only confusing.mAccepted-cdefine?W@WWWW)WRWTWUWVWWWXW[WsWܖWܪW݊WWWW7WޔWdefineeventforpagereceivedthereceiptofapagefromteVdefinedWSWZW_WbWیW۔W۾WWWWWWWWW-WDWEWGWHWKWLWPWYW\W]W`WmWuW܁WܖWܚWܪWܿWW W WWWWWWWWW W%WSW~W݁W݌WݻWWWWW.W>WAWEWFWGWHWVWjWvWކWޔWޕWޖWޗW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WW.W3W4W5WCW`WcWdWeWܛWܜWܬWWWoWwW7WKWޕWޗWdefinitionofinteroperabilityandcompliancemechanismsisܛVecIt 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/07/20 2006/04/28he figure 27 6@A> 33  33>cKSize of MIHF Fixed Header is not consistent with that depicted in figure 28d756g2264 2006/07/20 2006.03.05F27re in figure 28 d744g2263 2006/07/20 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 28d756g2264 2006/07/20 2006.03.05F27 ۂ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 | | csentencesvW7WIWseparate݅WWNWseparateieee802.11intotwowordsVsequentiallWsequentiallyWserverlW۶W۸WOWܘW;WZWWWWWsentencesم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َWuܬ 2006/07/20 ܭ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>d169g3226 2006/07/20ction 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./mRejected 2006/05/17۶ESanjeevFAthalyeGMember^Technical, Binding_21`58a5.4.3bTechnical, Binding_21`58a5.4.3bfails to show the relationships among the Information elements. d345g2303i Subir DaskZEQiaobingFXieGMember^Technical, Binding_44`30a6.3.2btion, not by any upper layer.d560g2299 2006/05/14 2006/04/24bRAbwireless!WsW=WW^WpWwirless^W^W^W^W^W^W^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=WAWBWNWPW}vroaming۳WWWrouter W"WޏWrouteradvertisementisencapsulatedޏVroutingݴWrtt WsQWRWSWTWW0W1W4W5W6Wscanۆ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 Vseeissue35VWLEQiaobingFXieGMember^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.@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 2006/07/20 2006/04/24 MEQiaobingFXieGMember^Technical, Binding_72`39a7.3.7.3b  TTfciThis is a link layer primitive which should only be generated by the MIH function, not by an upper layer.d503g2289wAccepted 2006/06/18 2006/04/24 MEQiaobingFXieGMember^Technical, Binding_72`39a7.3.7.3b7.3.7.3b  TTfEDasFSubir^ Editorial_7`6a3c#Handover needs a better definition d49g2416 2006/07/20EDasFSubir^Technical, Binding_3`60a1.3bCReplace "performance of access networks" with " access networks" c?No IE for " performance of access networks" has been defined. d23g2417i Qiaobing XiemRejected-DuplicatewRejected-Duplicate 2006/07/20EDas FSubir ^Technical, Binding_40`41b,Remove MIH_Command.confirm from Figure 18. c3"Confirm" primitive for MIH Command is not defined d294g2418i Eunah KimkrConsidering primitive types with their direction, confirm primitive is more proper than response primitive here. mRejectedvby comment 287w Superceded 2006/07/20Marked Figure 18arked Figure 182415echnical, 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" d33g2415 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 2006/07/20 2006/04/24 HEQiaobingFXieGMember^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..@-------------------| |Link ParameterType |A pair of {LinkType:ParamType}. |N/A |Parameters for which thresholds| | | | |may be orFHepworthGMember^Technical, Binding_46`8a6.3.2b3Add sentence to 3.2 representation to reflect this._OF_OPERATORS from Table 6.bhasOWPWQWRWSWTWUWVWWWiWRWSWVWXW܁WCWW5WhaveRWuWWWW,W7WRWWWW"W$WhdrܚWݴWhead~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~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.21VAWcofOWQWRWSWTWUWVWWWXWYW]W_WcWdWeWgWhWiWkWlWmWsWuWvWwWyWzW{W|W~W܀W܁W܄W܅W܌W܏WܐWܒWܓWܔWܖWܗWܛWܜWܝWܞWܟWܡWܢWܤWܥWܬWܭWܯWܰWܱWܷWܸWܻWܼWܾWܿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWW W%W0W2W3W8W:WDWIWJWPWSWWWZW[W]W_WfWoWuWwW{W~W݀W݂W݃W݄W݆WݍWݐWݔWݙWݥWݬWݮWݯWݰWݱWݵWݷWWWWWWWWWWWWWWWWWWWWW'EDasFSubir^Technical, Bindingding_32`55a5.8.3boAdd a sentence after line 65: " However, no upper layer ammendments are required for this interface to work. cGNo mention about whether higher layer ammendments are required or not. d249g2439 2006/07/17EDasFSubir^Technical, Bindingr^Technical, Non-binding_32`55a5.8.3boAdd a sentence after line 65: " However, no upper layer ammendments are required for this interface to work. cGNo mention about whether higher layer ammendments are required or not. d249g2439 2006/07/17EDasFSubir^Technical, Bindinges". Is this always true? d244g2438 2006/05/14EDasFSubir^Technical, Non-binding_32`55a5.8.3boAdd a sentence after line 65: " However, no upper layer ammendments are required for this interface to work. cGNo mention about whether higher layer ammendments are required or not. d249g2439 2006/05/14EDasFSubir^Technical, Binding=UENada, Golmie, Member^Technical, Binding_69`50bs 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. d505g2272 2006/05/22UENada, Golmie, Member^Technical, Binding_69`50bse 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. d502g2270er:a vsupportەW۫W\WqWݓWoWsupports3WsureۈWswitching{WsystemWsytsem{WtWWtable0WIWhWܗWWWdWtable-6W%W)Wtable/reference`WtakeQWTWWJWtalkedWtarget"W*Wtask:WteamWtechnologiesWܐWܽWWtechnologyەW WܰW0WFWterminateݓWtermsZWܗWWtextZWlW۷WWWWWW WeWܗWܜWWnWthe"W)W*W0WZW[WۉWۋWێW۪W۳W۵W۷WWWWWW WܗWܬWWWWWW0W2W3W;WBWDW{W݃W݄WݓWݳWW-W/W4W5W7WSWthegroupfeelstheoriginaltextisbetterthanthesuggest7VtheieshouldrepresenttheqoscapabilitiesoftheaccessnVthelanguageistoostronginsomecasesmayneedtochange{Ve 6.܏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 2006/07/20ܐENada, 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.d568g2334vA 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. wRejected 2006/07/20ical, Binding_115`5a8.3.3.1b115`5a8.3.3.1b, Golmie, Member^ Editorialc1.0SW1.2WW10_WaW܍W11WWW W111qW118W12%W&WKW_WaWWWW6WWW124YW125hWhWhW_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-WۉWeWrWWݲEWGWrWyWregisteration.WregisteredOWPWQWRWSWTWUWVWWWWregistering-W.Wregistrant\WregistrataionWregistration-WuWVWWWWregularޖW5Wreject.Wrejected\WܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖWܖ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۔W۬WW2WWWap-WܵWWWap/bts+Wapi's%WapparentWWapparentlyWWWappearsWWappendixWWWWNWappliancesWapplicableWWWWWWܥWܲWhWapplication۪WWW+WݭWapplication/protocol"WappliedJWappliesWWapplyYW{WWapproachWappropriateۅW܂WW݂WWW:Wapproved>W?WapsJWapzWar:WdWarbitraryWWWWWWWW:W=WNWRWcWjWtW܏WܖWܗWܚWܪWܭWܯWܲWܴWܹWܿWWWWWWWWWWWWWWWarelinksynchronouseventsapplicableforl2handoversonlyܲVaremorefailurecodesneededtoindicatewhyaparticularsVareaW=WIWareasWWarticle۰W>-^cannexۀWWWoWޗW>WannexesWannexesmissingfromtocVcVV>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'bleastW۸WleftۂWlefthand<W?Wlefthand-side>WlegendܵWlengthJWۉW(W)W=WFWHWvWwW|WWiW|WݗWݵWݹWW'WuWހWނWޅW1WlengthodofcivicaddresselementsinoctetsuVless=Wlevel#W?WQW\WܬWlikeAWWW2WUWWWܴWtW݁WlikelihoodWlimitfWlimitthescopeofmihcapabilitytol2mihcapabilityfVlimitationWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWIWJWۉWlotWlowېWlowerAWpW۵Wlower-layer*WlsۓWmac,Wmac/phy WmachineWmacpoaۊWmadeWmaintainedWWmaintaining۶Wmaitained۳Wmake#W*W?WZWWWScisn'tWisn'tthisalreadydoneduringtheprocessofregistrationVationVVVW W-WcWWWelements7WٷWٺWW-WWelse|WڄWWelsewhereWembeddedWWenableWencapsulatedWencapsulatedrouteradvertisementisencapsulatedVencodeEWencoded6Wencoding6WپW1WڢWWencodingsbWengine"WenoughWٟW(W5W6WCWensuringVWentierڝWentirepWentirelycWentitiesgWٮWWWW}WWWentity&W'W(W)W*W`WgW٤WWW"W@WVWiWentryW$WWenvironment٦Wenvisage<WenvisonedڔWequivalent9Wead 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 cmostېWW@WܷWWWmostareaswheremobileipv6arereferredtoshouldbeipv6Vmostly_WaWxWmoveW)Wmovesections8.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ܗWܛWܽWWWWWWWW0W:WFW݄WݓWW"W4W5W7WSWTW`WnWޕWthisfieldactuallyreferstotypeintlvasopposedtoabiޕVthisisdesiredbutwecannotmandatethiscertaintechnologܽVthisisquitecorrectTVthiskindofpartitioningdoesnothelpatthisstageneedsVWtitle)WtlsWtlvܗWtlvsZWܗWto*W0WBWQWRWSWTWZW[WfWۊWێWەW۬W۳W۴W۵WWWW 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.d561g2349u3 jA!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/07/20EVivekFGuptaGMember^Technical, Binding_87`23a 7.4.7.1.2bAdd 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 33cbeenW+WpWvWxWWWWWW)W+WܕW W%W݅WWWEWFWGWHWLWMWWWWWWWWWWWWWWWGWHWIWJWblockFWGWHWIWJWboth-W:W;W<W=W>W_Wbut%WDWEW_WaWiWby+W/W0W1W2W3W4W5W6W7W8W9WEWLWMWOWPWQWRWSWTWUWVWWW_WbWcWdWuWc_WaWcanAW_WbWcWdWeWjWkWmWnWoWcapabilitiesuWcapabilityuWcapable_WaWcharacteristicsiWclarifiediWclassesWclear!W-WcommentsuWcommit/W0W3W5W8Wcomplete/W0W4W5W9WcomplexityBWcomplianceWcomputationalBWconfiguregWconfusing(W)Wconnection\Wcontent!W_vbeinghandledaspartofcomments384396incommentassignmVbelow"WbenefitsSWbernardݜWbesidesܗWbetterۅW7Wbetween۔W۴WܗW;W4W5WTWfWbeyondݓWbitmapޕWbits)WbodiesۓWbothWWW/WbothdatarepresentationformatsneedtobeprovidedasoptiVbringWbroadcastۅWW>W?W@WWWWWWWW W0WCWDW{W݂WݪW0WFWWWXWmWyWby215WVby394XVby482yVby492FVby516Vby518FVby527ݪVbycomment162۸Vbycomment195۾VCVbycomment200tobeverifiedwhenre-drawingthefigureasDVbycomment203Vbycomment208Vbycomment212%VVbycomment215&Vbycomment215andissue40'Vbycomment348Vbycomment369ۑVbycomment384Vbycomment480\Vbycomment500mVbycomment704VEDasFSubir ^ Editorial_1`50a1.2bAdd correct reference cCReference [1] is not correct. Also reference numbers are missing. d5g2411 2006/07/20EDasFSubir^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 2006/07/20EDasFSubir^Technical, Binding_3`60a1.3bCReplace "performance of access networks" with " access networks" c?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 2006/07/20 ^bindingW!W"W'W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WBWDWEWFWGWHWIWJWLWMWNWOWPWQWRWSWTWUWVWWWXWZW[W\W]W^W_WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWuWwWyWzW{W|W}W~WWۀWہWۅWۆWۑWےWۓW۔W۬W۳W۴W۶W۸W۾WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!W"W%W&W(W+W,W:W;W=W>W?W@WCWHWRWSWTWUWVWWWXWYW\WbWcWdWkWnW܂WܐW/I4wAccepted-Modified 2006/07/20 2006/04/28Markedndard, 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@A> 33  33 33>wAccepted-Modified 2006/06/21a5.6.1[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/07/20 2006/04/28 EEleanorFHepworthGMember^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/07/20 2006/04/28 EEleanorFHepworthGMember^Technical, Non-binding_77`32a7.3.13.1b1Would consider removing Link Type as unnecessary.chGMember^Technical, Binding_74`45nical, Binding_74`45cnotcustomaryuseGVnotsurewhatismeantbyagentadvertisementisޏVnottransportchannelisestablished܋VnoteW WW>WEWFWGWHWnotethatalternativeunderlyingtransportswouldallowtheVnoted*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 CCnENada, Golmie, Member^Technical, Binding_13`52a5.1.3ollowing 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. d632g2298 2006/07/19nENada, Golmie, Member^Technical, Binding_13`52a5.1.3 Identifier of the link to configureB  a specific link."^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 $ۋvhAdd another flow diagram for this. The ordering of choices may indicate priority for different networks.wAccepted 2006/07/20 2006-04-07 t. 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. Vd573g2247 2006/07/05 2006-04-07ۋE HongchengFZhuangGObserver^Technical, Non-binding_94`34a 7.4.10.1.2bTypeList ) 7.4.1.2 MIH_Capability_Discover.response MIH_Capability_Discover.response ( Wbneed-WAWMWRWTWpWxWۉWWW)W܂WܴWܾWݍWWWWW3WneedtoaddsometexttobeconsistentwithothercasesVneedtoverifythecorrectnessofthisstatementandifnotVneeded۸W۾W;W݂WTWjWyWzW{WneedsLWVWdWWWܾWWIWneedstobeconfiguredofflineorout-of-bandandit'sVnegotiateuWneighborAW_WNWneighborhood_Wneighboring_W=WܡW+WtWneighboring-poa~WneitherWneous_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;WIWMWOWPWSWZW_WuW|W݃W݊WݺWWWWWWW WW!W"W#W$W%W+WbdependingAW܁WWW%WdependingonthetypeofmobilitysupportfordifferenttypeVdependingonwethertheresponsequerieshasonlyoneormul܁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ނW  HbALine 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 tBhe 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 W ۉbE"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.Gd902g2214vDChange the primitive definition and the protocol definition as well.wAccepted 2006/07/20 2006-04-07Marked ۊEBingyunFQuGObserver^Technical, Non-binding_82`58a7.4.1b Bit 1: Link bit error rate Bit 2: Link frame loss rate before retransmission =5baccess#W$W*W?WAWUWpW۱W۳W۷WWWWWW=W@WܬWܾWWWWW!W0WCWQWSW_WWWWWW WW"W$W%W1W3WpW1W4W;Waccesstechnologies۱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@themihfunctionheaderconsistsofatwopartsonewithfix'xthemihgetinfoconfirmisaddingnovaluesamecanbedone@themihlinksapisnotshowninfigure12andisnot@thenamesofthetwostacksshouldbechangedtoreflectthe@jtheneedfortypeienumberofoperatorsisnotsufficiently@therecipientoftheprimitiveisthemihfunctionwhichwil@#therepresentationofdifferentieslistedintable-6isnot@thesentencehoweverthetarnsportandsecurityofthisinfo@;thetermgenericsapisconfusingsinceinline47itthens@thetwomechanismsforretrievinginformationelementscurre@thetwomechanismsforretrievinginformationelementscurre@ctiontitlemediaindependenceisconfusinganddoesn@;IW^WuWڄWڌWWWdifferenttechnologieshavedifferentnmsinterfaceseg802ڌVdifferentiate|WYo^technicalnon-bindingۂVۃVۄVۇVۈVۉVۊVۋVێVېVەV۪V۫V۵V۷VVVVVV V V VVVVV#V$V)V*V-V1VAVBVFVJVKVLVMVZV`VeVhVmVqVsV|V܏VܛVܜVܢVܩVܯVܰVܲVܺVVVVVVVVVVVVVVVVV+V3VAVBVJVLVSVVVWVZVkVxVyVzV|V݊VݏVݵVݽVVVVVVVVV V VVVVVV ViVjVkVކVއVޕV0V1V2V3V4V5V6V7V8V9V<V>V@VAVBVCVDVtechnicalwaseditorial V$V%V&V(V*V+VAVYVۛVۼV۽VVVVVVVOVܭVVVVVVVVVw9famolari.1farrokh !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxfran݄golmie2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎W܏WܐW,vrefertocontribution21-06-0677-00-0000-hflow0Vrefertocontribution21-06-0686-01-0000mihhandoverprocediVrefertocontribution21-06-0690-00-0000-iVrefertodoc21-06-0675Vrefertosection7.4.5.2.4fordetailsݽVreferenceHWWreferenced2WreferencesWW݊WSWrefers WܗW2WޕWregardingTWWܗWregisteredQWRWSWTWregistration}Wregster{WrejectۂWrejected!WۆWܐWܗWW݂Wrejectedbyvote8-8!V݂VrelatedRWTW۳W=WWW"W1Wrelatedtocomment142128226Vrelatedtocomment345shallbeworkeduponandfurthercont=Vrelatedtonetsap1V/TabB3le# (if applicable): - Section#: 6.3.8, Annex C !d463g2222iYoshihiro Ohba&c device to reconfigure and present data to uppered) enterprise environment). cmments" script. It had not been updated in 1.1 to match the new ijkmFbnode,WAW_WpWuWۜW۞W3W4WܝWܡWIWQW݊WWWW W"W#W$W3WOWޕW4WAWBWCWnode's"WnodespWWnonWHWXWYWnon-posۭW2Wnon-secure<Wnone6Wnoneofferedunclearintentofphrase6VnorWnormalWWWnormallyOWPWQWRWSWTWUWVWWWnormativeܪWoWnorthboundJWnosNWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWtedWexplainHWIW|WexplainusageofthewordmediaIVexposedنWfacilitiesUWfacilitiesistoogeneralUVfailsWfeatureW ۉbAadd 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 Bthresholds need to beset. Bit 0: Link speed Bit 1: Link bit error rate Bit 2: Link frame loss rate before retransmission 1[zE Ulises OlverabaGMember^Technical, Non-binding_140`1a Annex A-1cA- 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? 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.ccinappropriateWW8WSWinappropriateuseofdash8VincludeێWW:W@WnWܐWܜWܯWܰWWWWWWWݏWW8W^WnWincludedefinitionofhandoffandhandoveranddistinguishbܜVincludesomesamplereferencelocationsofmihposanddiscuܯVincludethemihnmssapinthemediaindependentsapssectioV8VincludedۊWW~WWWWincludes:W@WWAWޕWincludingW܏WWinclusion:W;W<W=W>W{W}WWinclusionofmihfidinvariableheaderpartisnotmentioneVVVVoneVVWWWWWWWWWWWWWWWWWWWWWWWWentioneVincompleteWWhWinconsistenciesWinconsistency%W&WWޣWޤWWWWWCWDW߁W߂W߿WW*W=jtheirWthemWthen/WaWWgWvWthenmihuserscannotdecidesiftheprimitiveisintendedfgVthereܶWthereforeܾWtheyWWtheyareinfactcommandsfrommihusertomihforfrommihfVthis"W?WBWZWaWuWWWWW WWvWthiscommentshouldbediscussedinconjunctionwithproposauVthrough?WW WtitleWtlvBWaWWݻWށWWWݻ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‚D@N‚I@KÃ&0@PÃ(@IÃ*`@HÃ5@EÃF @OÃJP@UÃU0@QÃX@DÃd@JÃjp@MÃs@LÃwP@RÃ@@SÃ@T@L`@IÃ@MA€RC€B€aE€D`FI Ä*2@HGK matsumotoKJWMoL#N%Q‚g@POBS@R‚#0U‚T‚"W‚&@V‚L DYX @$entireWWW W"W#W$W%W-WDEWolfgangFGroetingGMember^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" c3No proper example is given for TLV reques/response.d9g2584 2006/04/29EEWolfgangFGroetingGMember^Technical, Binding_147`8aA.4bg2585 2006/04/28?cmanyNW_WaW܊WܡWܿWWWmappedېW۾WmappingDWEW>WmarchW*WmaskZWmatchAWBWKWLW`W܁WW6WmaterialWmaxWmaximumW WWWmaximumlengthofthesessionidandothersyntaxaspectsarVVVVVVVVVVVVWܰ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 > :cd316g2244pnInter-technology handover and intra-technology handovers can be replaced by vertical and horizonbtal handoverswAccepted 2006/07/20 d ting: "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 BNetwork (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 eMcackWWack-bitWack-rspyWacknowledge܌WacknowledgementWacknowledgementsWacquisitionݍWacronym-W2WRWW@WacrossWW*W3WacryonymWactWacting:Waction6WactionsۅWۈWhWactiveWޖW5WactualWactuallyWWWWݏWadaptiveWWWWWWWWWWWWealsothereisnone Vaddress:W;W<W=W>WۈWەWWWWWWWWWaddressedWaddressesܰWWWWaddswWadequatenWadequatelyەWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWWadvanceۅWadvertisementWadvicedܖWaffectܳWafterۅWۇWۮWfWWagain+WWagnosticܭWܰWagreedܕWaidWWaimingܗWair۽WairportWaksingWcincorrectrWwWW9WgWݗWݶWݾWJWincorrectuseoflinkcommandindicationwhenacommandisa9VincorrectwordgVincorrectly:WRWincorrectnesssincreasedWincrementalWW[Windefinite۰Windependence(WindependentWܠWܢWܰW}WWW8WnW1WindicateۅWۊW۵WwWܗWWWWindicates܄WhWW,WfWindicatingۂWindicationOWPWQWRWSWTWUWVWWWWW9WOWW WݍW>WsWxWޕWޖWޗW5W?WindicationsۅW-WWindicator4WindicatorsWindispensable7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWatorsWinefficienciesWc bcarriedyWzW{WWWށWދWތWcarrieskWnWW'W}WcarryܕWW WݍWcarryingWcaseAWWWWW#WܶWWWW_W|WݎWݗWW WޏWcase2ifthenumberofoctetsoccupiedbythevaluefieldiݗVcases#WAW۰WWWWܴWܿWQWW'WiWjWcasting6WcategorySWRWcatualwWcatuallengthofthevaluefieldwVcause WۉWޗWcdmaPWcdma2000_W=WDWSW W^Wcdma2000-hrpdRWcellualarPWcellularWPW݊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^WWWWWWWWWW+W,W.W0W7W<W>W?WIWchangeasfollowsܤVchangebecommunicatingtocommunicate7Vg~a7.4.112i7.4.123A7.4.12.1.167.4.12.1.2ݯ7.4.1347.4.13.1B7.4.13.2C7.4.14WiW=WMWOWQWUWYWޭWޮWޯWްWޱW޲W޳W޴W޵W޶W޷W޸W޹W޺W޻W޼WWWWWWWWWWWWWWWWWWWWW W!WidbsuggestednewpoalistۋWsuggestion$suggestionsܩWsuitabilityTWsuitablePWuWWW݊WsupAWsupplement&W`Wsupplementtitlebyappenidngfromaremoteserver`Vsupplementwith3gpp2standardsreferencesasaminimumsugg&Vsupport W?WAWbWpWېWەWۺWWܴWܻWWWWsupportdisquerydWsupported.WAWLWuWېWWWTWcWdW|WݖWW[W^WހWނW0WsupportedforthistypeofqueryހVނVsupportedindraft-ietf-geopriv-rݖV-ietf-geopriv-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|WWctoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWW W%W+W0W1W2W:WCWFWKWLWOWPWSWUWWWYW[W\W]WaW{W|W}WW݂W݇W݊WݍWݏWݐWݒWݕWݖWݘWݛWݴWݸWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W!W"W#W$W%W)W*W+W,W/W1W4W5W7W<W>W?WEWFWGWHWJWOWPWWWXWYWZWaWbWcWdWgWjWmWoWހWށWނWރWޔWޕWރWoWoW 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 2006/07/20c 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" witthe bits of this field are to be set to '0'."g3238 2006/05/14ۇbWe 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 detailscAIn 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/07/20 2006/04/24per layers. d535g2218 2006/05/14 2006/04/12ۆEYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.c---------5#c?"... autenticated with the POA and ..... ", should be new POA d387g2450wAccepted 2006/07/20 $EDasFSubir^Technical, Non-binding_47`52a6.3.3.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 2006/07/207 %EDasFSubir^Technical, Binding_49`8a 6.3.4.1.1bjEither in Table 6 it should be variable or this table should be 4 octets. However, it should be varaible cULength is variable whereas IE Table (#6) says it is 4 Octets. This is inconsistent. d414g2452voThe entire length column in Table-6 is being dropped as per contribution 21-06-0675. Superceded by comment 352.w Superceded 2006/07/20&EDasFSubir T cthe802.21standardspecifiesthemeansforsecurityinformaܢVtheaboveframestructuremayalsobeusedwithastandardlVtheassignmentofistoanyinformationelementshouldnotbXVtheclientmayalsohavelocalinformationfordifferentavaܶVlientmayalsohavelocalinformationfordifferentavaܶVܶVrQWoverallWoverloadPWowlWWWWWWWWparametersWWWWWWWparametertype2W3W4W5WpartWWWWW W!W"W#W$W%W٤WWWpartsHW٤Wpass?Wpassing?WpayloadWpdsnWpdu٨WperWWWperhapsْWperiodfW4WperiodicfWphraseٓWٟWphrasingdWpicturepWpieces3WplaceRWplaced٧Wplaying&W'W(W)W*Wplural~Wpluralform~VpoaهWW'W.Wpoints_WٱWWpolicy"WWPo ۂbG | | handover. | Unchangeable | | | 1: Current POA can not select another new network Identifier | | | | for handover. | | H | 1: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- @Az  33  ;  33     33   zc----------------------------------------------------------------------------------------ۈEYan 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.cPrepare.request message, nor can it send MIH_Handover_Complete.request to the corresponding previous serving PoA.d846 2006/07/20 2006/04/24ۈEYan 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.cdment.ppt for detailscns by upper layers. d535g2218 2006/05/14 2006/04/12ۆEYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.c---------{breplacelinkcommandoriginatewithlinkcommandsoriginate8Vreplacelinkgoingdownwithlinkgoingdown܈V8V8Vdicationwithlinkcommandrequest9V9Vationwithlinkcommandrequest9V9Vplacelinkcommandindicationwithlinkcommandrequest9V9Vplacelinkcommandindicationwithlinkcommandrequest9V9VlistofnetworktypJVreplacemanyuserwithmanyusers܊VreplacemihbymihfinentiredraftܥVreplacemihgetinfoindicationwithmihgetinforequestOVreplacenetworksecurityandqualityofsecuritycapabilitie<Vreplacenumberofparametersinlinkparamterlistwithnumber_VreplaceperformanceofaccessnetworkswithaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1Vreplacereceptionofthespecifiedsduwasacknowledgeatl2܌Vreplaceresourceretentionstatus20withresourceretention܇VyEVivekFGuptaGMember^ Editorial_140aAnnex-A1b"Draw figure 30 in Landscape formatc(parts of Figure 30 are very hard to readd870g3256 2006/07/20F-30EEleanorFHepworthGMember^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 d35g2218wRejected 2006/07/20 2006/04/28 overall scheme of things. An overall flow control diagram is required showing all of these key steps.?d862g3255 2006/05/1429EVivekFGuptaGMember^ Editorial_140aAnnex-A1b"Draw figure 30 in Landscape formatc(parts of Figure 30 are very hard to readd870g3256 2006/05/14F-30g for the upper layer, which is improper.)@A  33d759g2273 2006/05/14 2006/04/24>EQiaobingFXie' hrbAR 33    TT  RN‚A7O‚B8P‚C9Q‚D:R‚E;S‚FV‚I?W‚J@X‚QAY‚RBZ‚SC[‚TD\‚UE]‚VF^‚WG_‚XH`‚YIa‚ZJb‚aKc‚bLd‚cMe‚dNf‚eOg‚fPh‚gQi‚hRj‚iSk‚jTl‚qUm‚rVn‚sWo‚tXp‚uYq‚vZr‚w[s‚x\t‚y]u‚z^v‚_w‚`x‚ay‚bz‚c{‚d|‚e}‚f~‚g‚h܀‚i܁‚j܂‚k܃‚l܄‚m܅‚n܆‚o܇‚p܈‚q܉‚r܊‚s܋‚t܌‚u܍‚v܎‚w܏‚x‚y‚z‚{‚|Ã!}Ã! ~Ã!0Ã!@ۀÃ!Pہwwithdrawn{l݂WWWMclinkparametertypedefinitionsisinsufficientandneedsto@linkprimitivecanonlybegeneratedbymihfunctionnotfro@}list@3located@macmobilenode@emacro@rmanagement@many@may@mean@media-dependent@messages@imicro@>mihۃ8jmiheventderegisterhasnotbeenexplicitlymentioned@Vmiheventregisterconfirmshouldbemiheventregisterresp@;mihgetinfoindicationshouldbemihgetinforequest@:mihhandovercommitisimproperfor802.21scopethefunctio@issing@>missingreferencesfrom3gpp2@&mode@morecallflowsshouldbeaddedtoshowhowmihprotocolis@dmoved@necessarily@needed@needlessly@needs@pnegotiated@@network4networkdetectiondefinitionisredundant@new@newlinkidentifier@nms@node's@Pnon-3gpp2@Nnon-adaptiveness@andmediad@"cresultseWݑWWretention܇WretransmissionWWWretransmissionsWretransmitWretransmitted&Wretrieval_WaWbWretrieve_WbWlWIWeWWretrieved_WaW݂Wretrieving_WaWܽWreturn_WaWۂWۄWۊWWWreturningWreturnsQWWreverseWrevisedހ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܈W#Wgprs?WFWGWHWIWgranularityWWW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!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ۃWێWWWW+WޗW@WswitchingۂWsynchWsynchronisationWsynchronousܲWsyntax5W6W8W<WGW^W_WaWfWiWlWoWpWrWtWvWwWxWyWzW}W~WW܀W܃W܆W܇W܈W܊W܋W܌WܗWWW-WsyntaxerrorandconfusingsentenceincontrolthebehavioriVsyntaxerrorin3127reserved}VsyntaxerrorinadditionalidentifiersarepresentthathelptVsyntaxerrorinafterupperlayerentitiesmakeshandoverdefVsyntaxerrorinalsoknowaslowerlayers6VsyntaxerrorindeliversthismessagetothemihfoVsyntaxerrorindifferententitiesmayrregisterwithrVsyntaxerrorinlinkcommandoriginate8Vsyntaxerrorinlinkgongdown܈Vsyntaxerrorinmanyuser܊Vsyntaxerrorinnetworksecurityandqualityofsecuritycap<VsyntaxerrorinnumberofparametersinlinkparamterlistP ۂ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. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- memberܖܗܘܙܚܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܮܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456788ode 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/28HfcrateFWGWHWIWJW:WWWWratesWratherܩWWW WDWWrdfjWkWmWnWoWzW{W|W}W~WہW0WwW}Wrdfresourcedescriptionframeworkshouldbeaddedtosectio0VrdfresourcedescriptionframeworktechniquewasdevelopedajVkVmVnVoVzV{V|V}V~VہVrdf/xmlہWWre-usedWre-writtenWreactWread-WWWreadabilityۮW5reader݃Wreadiablity4readilyWWreading݃WreadsۨWreallyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWܧWWreferto802.21asieee802.21consistentlyinthedraftܧVreferenceW!W$W۬W۽WWWWWDWEWܪWܯWWWW{QۉE HongchengFZhuangGObserver^Technical, Non-binding_157`44a8.5.2bused 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.Id822g2219 2006/06/30 2006/04/12ۉE HongchengFZhuangGObserver^Technical, Non-binding_157`44a8.5.2bt for detailscns by upper layers. d535g2218 2006/05/14 2006/04/12ۆEYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.cne 38-49 ned" cbutܼWWWWWW WWyWݏWWWWiWޔWޕWޖWޗW7W>W>W>W>W>W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WtawhenthisinfoquerytypeisspecifiedinfoqueryparamVrdf/xmlWre-define2W3W6Wre-definethelinkparametertypeasapairoflinktechtechs2V3Vre-definethelinkqualityparametertypeencodingtableas6Vre-verificationCWre-visit6WreadWreaderWreadersW5WBWreceivesWreceivingWWreceptionCWWrecipientWrecommendediWredrawOWredrawthefiguretoindicateallpossibilitiesordeletethOVredrawingpWreevaluate>WreferٻWټWreferenceW_WgWWW$W2WڟWڣWWWreferencedDWڟWڣWreferencesWWfWpWqWڟWڣWcocissueېW2WWW>WissuedWW>W3Wissues#WܭWWW>WWWWWWWWNW_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ޫWWWWWWWWWgX{bhandoversW:WhandoversduethemobilenodemovementmaybehorizentalintVhard:WhardwareWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!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)W+WAWKWNWYW]WrWەWWWWWWWWWWW-W0W;WAWBWYWhW܁WWWWWW(W*W2WHWyWzWW݂W݋WݳWݽWWWWWWWWWWWW W W WWW1W2W6W8WCWPWXWYWeWlWnW|WށWރWބWޅWވWޗW0W3W5W6W7W8W:W;W>WDWsection46.3.8Vsection5.4.3Vsection5.8.3isjustaboutgeneralusageofmihservicesby+Vsection6.2.4saysthatfigure18showstheflowforlocalayVsection6.3.4isbettertobeplacedbeforethecurrentsectYVsection7.1.1doesnotmentionthelsapsforwiredmediaVsection8.48.4.1-8.4.2VdWsecureܢWWsecurityW<WܢWܼWܾWWݏWWsecurity/qosܰWWbpowerW6WpoweritdownVpppWpptۄWۅWۆWۇWۈWۉWۊWۋWWWyWzW݃WpramaetersۉWprarameters3W3W3WitionalidentifiersarepresentthathelptoanalVwitheitherNVreplaceconceptualabstractiondescribingtheinformationtr٬VreplacedeliversthismessagetothemihfwithdeliversthisVreplacedifferententitiesmayrregisterwithwithdifferentVreplacefacilitieswithamorecleartermUVreplacelinkcommandindicationwithlinkcommandrequestٰVreplacelinkcommandoriginatewithlinkcommandsoriginateٯVreplacelistofnetworkslinktypeswithlistofnetworktypVreplacemihgetinfoindicationwithmihgetinforequestVreplacenetworksecurityandqualityofsecuritycapabilitieٳVreplacenumberofparametersinlinkparamterlistwithnumberVreplacepppwithnetworkconnectivityprotocoltVeassignedidenٺV_‚tCDCD‚uNP>‚w0;ݛEFl‚xESGHm‚yLQR‚zTUI‚VWyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy‚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ۄ܃ OOr`41b+remove for loop, and split into two tables.cKThis table is confusing; the use of for loop does not aid understanding. d432g2280 2006/07/20 2006/04/2812EEleanorFHepworthGMember^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. d433g2281vNo clarifying text provided.wRejected 2006/07/20 2006/04/2812EEleanorFHepworthGMember^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? d440g2284EEleanorFHepworthGMember^Technical, Non-binding_59`43r^Technical, Non-binding_59`43_532@^ Editorial_22`49a5.4.3b Remove "help"c6"facilitate" further on in the sentence conweys "help"d176 2006/07/20AEFarrokhFKhatibiGMember^Technical, Non-binding_23`33a5.5bDelete "media agnostic"cFThe reference model includes a media-dependent part (the MIH_LINK_SAP)d181wAccepted 2006/07/20 BEFarrokhFKhatibiGMember^Technical, Non-binding_23`41a5.5b2Replace "Media-independent" with "Media-dependent"cMDifferent technologies have different NMS interfaces. E.g., 802.11 and 802.16d184vUThe way MIH interfaces with the Network management function may be media independent.wRejected 2006/07/20 CEFarrokhFKhatibiGMember^Technical, Binding_27`65a5.5.4bRClarify to what "UMTS" radio protocol(s) the MIH layer has access? SM,GMM and RRC?cRegarding the "UMTS" side, does the picture mean that the MIH layer will be able to access only the following protocols SM/GMM/RRC i.e. no access below RRC (MAC/PHY)d197n}ZclinkparametertypedefinitionsisinsufficientandneedstoFVGVHVIV!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"Vvon۳WW-WܗWܛWܬWWWW0W2W:W;W_WݴWW"WonrequestfromcommenterہVonrequestofcommentermVzVVonrequestofcommenterfurtherclarificationrequired_VontherequestofcommenterjVkVoncelWܗWone(W{WfWށWރWoneoctetcanactuallyhold255values(VonlyBWZWgWWWܗWWݓWfWoWopenedWoperation0W*Woperational{Woperator@WWWoperators[WW@WܗWWopposedܾWޕWoptionaldWoWoptionsWWorlWۅW۔WۛW۳WWܗWW3W{W݊WݓWݜW"WSWfWށWރWorderW"WorderingۋWorganizeZWorganizedZWoriginalZW7WotherRWۓW۳WWqWWWWW2W;W݊WSWother/futureVWW2Wpage18sentenceonline22changesasfollows۳V3 bthe~W݁W݂W݂W element "TYPE_IE_LIST_OF_NETWORKS" represents a list of network types and not a list of networks. 2- The description for "TYPE_IE_LIST_OF_NETWORKS" is misleading. It states: "List of Neighboring Access Networks. Link types of the networks that are available in a given geographical area". The list of Access Networks and list of link types should be two different lists. 3- The Representation of the list suggests to use RADIUS NAS-Port-Type to code the list. This shouldB be the representation of ONE link type not a list. 4- The Lenght of the list is set to 4 octets. It is improper since a list can have variable length. This size is the size of one item.i Subir DasjkGI understand the reason but do not understand why we need both the IEs.mAccepted-Modifiednpvw{ 2006/05/146666666cnetworkidshouldbelinkidݨVݩVnetworkidentifeirshouldbelinktypeݺVnetworkidentifierisaconfusingterm]VnetworkidentifiershouldbelinkidentifierVnetworkselectionistheprocessbywhichamobilenodeoraܡVnetworktypesrelationshiptopreviousnetwortypedefinitioVnetwork-basedޕWnetwork-layerܡWnetwork-related:Wnetworks"WۋWےWWWWW=W@WJW[WܡWܶWܼWWWW:WSW݂WݏWWWWWXWYWtWDWnetworktypesݼWnetworktypesshouldbelinkidentifierݼVneutralWnever.WAWerݼVneutralWnever.WAWAWAWAWAWAWAWAW24c 4/24/2006dTechnical, Binding*zܗEWolfgangFGroetingGMember^Technical, Binding_49`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.d413g2267vpter 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.d413g2267vܘEWolfgangFGroetingGMember^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" 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" d756g2264 2006/05/14 2006.03.05F27E 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 2cA"MIH Event Register" and "MIH Event DeRegister" which are mentioned in Table 14 on page 66 cannot be found in Table 3 on page 38 Similarly, "Link Event Register" and "Link Event DeRegister" which are mentioned in Table 15 on page 67 are not found in Table 2 on page 37 (Link Events)d271g2263i Qiaobing Xie^Technical, Binding_37a7.2.2.1b^Should be included in Table 3 since they fall under MIH Events Should be included in Table 2cA"MIH Event Register" and "MIH Event DeRegister" which are mentioned in Table 14 on page 66 cannot be found in Table 3 on page 38 Similarly, "Link Event Register" and "Link Event DeRegister" which are mentioned in Table 15 on page 67 are not found in Table 2 on page 37 (Link Events)d271g2263i Qiaobing Xie2cl flow when acually it is the logical flow.ERATORS from Table 6.sGc8.5_WaW8.5.1.20W8.5.2.1)W8.5.2.3)W8.5.3.19W8.5.4.1ބW8.5.4.2|WޅWވW8.6.1.18W8.6.1.28W802W802.11W@W[WWWWBWDW802.11pWW802.16WWBW4W5W^W>WDW802.16eW802.1xWWܸ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&!Wc^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 2006/07/20 XENada, 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 succ Event IDs. d510Bits 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. d510W bbitܹWW1WbitmapTWUWVWWWXWcWW1W6WbitsyWTWUWVWWWXWcWWݗWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhere 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/29conWFWGWHWIWuWۃWۊWېW۟WۦW۳W۽WW:WYWcWhWqWܕWܡWܫWܬWܯWܻWWWWWWWWW W W WWWW+W6W@WaW|W}W݂WݴWWWWWWWWWWWW W!W"W$W%W+W0W>WBWPWXWYWeWfWmW9W:W>Wonpage41itisstatedthatlinkconfigurethresholdscommaaVontheleftsideofthemihfunctionblockthefigure0Vonthetopportionoftheflowmodelpicturethemihcommand>Vonce Wone_WaWbWiWۄWۋW'W:W=W@WKWLWeWzW{WܗWܝWܩWWWWWWWW+W݆WݏWݜWݝWݞWݠWݣWݤWݦWݧWWWWWWW'W/W>WoneofmanyVoneofthestackmaybeVonesەWmBbbecause,WIWޗWbecomeAWۑWbecomesWWWWWWWWWWWWWWWWbeforeFWGWHWIWJWSWYWۉ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_WaWۃWVWXWeWW<W?WXWYWthelengthvWݹWthelengthdefiiteݹVthemEWۈWېWWYWܚWWW݃WWWWܚWWW݃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޾Wthereare256possibleencodingsforgeneralVjcreplacedWݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWWWWWWWWWreplicatingWrepositoryWrepresentFWܗ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:WC ܆cd847g2323 2006/07/20܇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 2006/07/20܈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 2006/07/20܉ENada, Golmie, Member^ Editorial_142`46b%Remove the second "Handover Complete"c#Duplicate entry "Handover Complete"d882E btheWWWWWW W W WWWWWWWW#W+W,W/W2W3W5W7W:W=W>W?W@WCWDWEWFWGWHWIWNWPWQWRWSWTWUWVWWWXWYWZW\W]W`WbWcWdWeWhWiWkWlWmWnWoWqWsWtWvWwWyWzW{W|W~W܁W܃W܄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 W WWWWWWWW%W(W)W*W.W0W3W4W5W9W;WCWDWIWJWKWQWUWWWYWZW\W_WaWiWkWwWyWzW{W|W}W{W{Wc7NW_WaWW(WWCWޗW7.1.1W7.1.2CW7.2.1.4>W7.2.2ݛW7.2.2.1lW7.2.2.2lW7.3lW7.3.11.1eW7.3.13WݛW7.3.16W7.3.16.1W7.3.17.1W4W7.3.17.34W7.3.18.1W7.3.18.3W7.3.7.33W7.3.9.1W7.4WlW7.4.12AW7.4.13BWCW7.4.14.2.2W7.4.4.1.25W7.4.5.2.4WݽW7.4.7gW7.4.7.1.4hWW8ܑWWޗW2W8.1qWW8.2.1rW8.37W8.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.8YWYWYWYWYWWbWfWiWjWkWmWnWoWuWzW{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=WIWOW]kܐܑEWolfgangFGroetingGMember^Technical, Binding_114`29a8.3.3b?Change the fixed header size from 6 to 8 bytes in the figure 25cIMIHF Header format is having 8 bytes in fixed header part (see figure 28)d735g2237wAccepted 2006/07/20 2006.03.05F25ܒ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 2006/07/20 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 d744g2263wAccepted 2006/07/20r]%cisFWGWJWMWNWW  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]WۂWۇWۉWW=W[WkWmWWWݒ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]WgWhWidentifierfor802.11networks[VidentifiersXWxWCWtWWݷWݸWidentifyZW]WxWWmWsWidentifyingWWidentityWidsNWXWېWCWTWUWVWWWXWcWWieZW[W\W_WۇWۉW=WKWLWaW܍WܽWܿWWW|WtW1Wieee#WW=WܧWW?WWWWWW1W3W4W5W^WpWieee802.11VVVVVVWWWWWWWWWWWWWWWWۓWWܹWWietfinformationelementsfor802.21V|binthissectionareprovidedintheappendixVinthisstandardinordertoaccess3gppservicesprovidedsVvicesprovidedsVVss3gppservicesprovidedsVVandardinordertoaccess3gppservicesprovidedsVVisstandardinordertoaccess3gppservicesprovidedsVVisstandardinordertoaccess3gppservicesprovidedsVVVVVVVVVntable-7ܹVincludealegendforfigure19bsapbstnetcܵVincludeamentionoftheseevenifistostatethattheyareVincludeatimebasedstatediagramshowingdifferentlinklaܳVincludeclientlocationasanessentialinputparameterinaܽVincludedescriptionofcasewhereinformationrepositorymayܶVincludeexamplesofiereportsandclarifyhowtousethemfܿVincludeguidelinesonratelimitationandtimeradaptationfVincluderecommendationsfortransportoptionseitherinthisܩVtedintable-6thisܼVW^#bretransmissionFWGWHWIWۉWW WretransmissionsWretransmitUWretransmitted&Wretrieval_Wretrieve.W_WbWcWlWބWޅWޅWޅ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)WtransactionsWW WWݳWtransferVWWW#W5WܟWW!WtransferredVWtransmissionWWRWtransmitUWRWtransparent*WWtransport#WOWWWuWxWW܋WܩWܯWWWWW W W W݃WW0W1W3WPWtransportiWtransportlayerۋWtraverse7W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/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?Wbj3ENada, 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 2006/07/204ENada, Golmie, Member^ Editorial_8`29b;Remove second definition of Mobile Node at lines 29 and 30.c$Duplicate definition of Mobile Node.d65g2238 2006/07/205ENada, Golmie, Member^ Editorial_9`38bherent.d64g2237 2006/05/144ENada, Golmie, Member^ Editorial_8`29b;Remove second definition of Mobile Node at lines 29 and 30.c$Duplicate definition of Mobile Node.d65g2238 2006/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@V۹ESanjeevFAthalyeGMember^ Editorial_22`40a5.4.3bRemove "it is"csuperfluous segmentd171 2006/07/20ۺESanjeevFAthalyeGMember^ Editorial_22`47a5.4.3b "support"cgrammard175 2006/07/20ۻ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/07/20ۼESanjeevFAthalyeGMember^Technical (was Editorial)_23`38a5.5bConsider removing "Generic"c="Generic" may convey conflicting notion wrt "media-dependent"d182 2006/07/20۽ESanjeevFAthalyeGMember^Technical (was Editorial)_27`64a5.5.4bFConsider redrawing picture with more conistent use of 3GPP terminologyc"d182 2006/05/17۽ESanjeevFAthalyeGMember^ Editorial_27`64a5.5.4bFConsider redrawing picture with more conistent use of 3GPP terminologycl, Non-binding_22`20a5.4.3121)KbwordsZW]W>Wwork۾WW݊WworkingWworks<Wwould.WWUWWW܂WܪWWW2WPW9WwouldconsiderremovinglinktypeasunnecessaryVwouldn'tWwriteWwritten-WwwwW=WHWݔWqW~WxWvWܗW&Wx1~Wx2~Wx3~Wx4~Wxml#WWܬWݚWqW~WހWނWxmlthismaymeanthatquerysyntaxisextraneousandVxmlns~WxrefWxxcWހWނWy/n1WyearHWyouWzero{W}WށWރWރWރWރWރWރWރWރWރWރWރWރWރWރWރWforV1W!WSWiWsWuW۪W۽WWWWW(W=WWWW>W1tableofcontentssectiontitlemissingV1textneedstoimprovesV1thecurrenttextimpliesthatthediscoveryofmihfunctiouV1theinformationelementtypeielistofnetworksrepresent=VbinscopeofdefinitionsectionspecifywhichreferencepointܪVinsomecasesintra-roamingpage15line41section5.2VinthedescriptionfieldreplaceNVinthesectionsbelowVVaddanewsectionassuggestedin21-06-606-00-0000locinfoVaddanewtablecalledscanrequestinfocontainingthefollowVaddanotesayingthathandoverisalsoreferredtoashandosVaddanoteunlessotherwisenotedmediareferstomethod/modeVaddaperiodtothesentenceVaddasentenceatendofparagraphadditionallyoralternatiiVaddadditionaleventcodesڬVaddannexestotheendoftocVaddclarificationintextthatallreferencepointsarewithVaddclarificationtotextV_Alistair`ButtaraMemberb35c 4/24/2006dTechnical, BindingbdoneWܴWWdottedWdouble-headed0Wdown WPWQWۅWWRW\W]W܈WWW#W6WdraftPW܏WܥWܧWܱWWUWYW݂WSWVWdraft-ietf-geopriv-rݖWdraft-ietf-geoprivraݕWdraft-ietfgeoprivݘWdrawWdrawfigure30inlandscapeformatVdriveW8WdriveriWdstݴWdue,WIWWduplicate Wduplicates WduringAWUWWdynamicWe?WWWۈWۖW۸WW=WFWwWWWSW_W݊WݎWݔWݖWWWWW"W$W%WހW9WeusingamihhandovercompleterequestV9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WeitherdiscussthismoredetailsordeletethiseventVWH/IEAjayFRajkumarGMember^ Editorial_69ding_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 southboundId498g2223 2006/05/18 2006/04/2815IEAjayFRajkumarGMember^ Editorial_69"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 southboundId498g2223 2006/05/18 2006/04/2815IEAjayFRajkumarGMember^ Editorial_69 ga6.3.3X$ܸܹX6.3.4Yܼ~ݗ6.3.4.1]ܗ6.3.4.1.1%6.3.4.1.2^&6.3.4.1.46.3.4.2.3'6.3.4.2.56.3.4.3.1(Yݘu6.3.4.3.26.3.4.3.46.3.4.3.5Z6.3.4.3.6ܾ16.3.4.6)6.3.5_`ܽ6.3.6a*6.3.6.16.3.6.2[<6.3.6.36.3.6.3.2ݙ6.3.7bܿ6.3.7.2׃\6.3.7.3]6.3.8B݀6.3.8.1؃^ݚv6.3.9كڃ_`zBx=7C7.1D7.1.1D7.1.2C7.2.1>7.2.2l7.2.2.10;یݛEF7.2.2.2GH7.2.3.1Em7.3.1.3L7.3.10bݝ7.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_WaWۡWWW_W~W܍WܓWWWWWݙWݷWWWWpWnumberofaddressheaderidentifiersisnotneededݷVnumberofoperatorsisnotneededݙVnumberedWnumbersWWWobjective*WWWWWWWWWWWWWWWWWިWWWHW߆WWobtainېWIW݂WobtainedېWܬWWWobtianedܬWobviousQWobviouslyۄWېWoccupiedWoccupieszW{Woccur^WoccurencesܥWoccursۨW WܟWWWocteswWoctet(WFWwWWoctetsW%W&W)W=WAWBWFWWWoduW=W#;ctherepresentationofdifferentieslistedintable-6isnotܷVtherepresentationofnumberpoaisnotspecifiedVtheruleshereseemtoimplythatreceiverprocessingcould Vtherulesonhandlingduplicatetransactionsarenotclears Vtherulesstatethatinanycasethedestinationshallnotp VthescanrequestsetsisnotdefinedthelistofscanrequestmVthescanrequestsetsshouldidentifylinkietechnologytoVthescopesectiondoesnotadequatelyaddresswhichpartsofەVthesectiontitlemediadependenceisconfusinganddoesnot)Vthesectiontitlemediaindependenceisconfusinganddoesn(Vindependenceisconfusinganddoesn(V(Vntitlemediadependenceisconfusinganddoesnot)V)VW*W+W1W2W3W4W6W7W8W9WAWKWLWMWOWPWQWRWSWTWUWVWWWZW]W_WaWbWfWgWuWWۄWۈWۊWېWەW AEHongFChengGMember^Technical, Binding_38`3a6.1.6ontents of section 6.3.8 to Annex C.czThe defintion of the Information Service Schema is an implementation option, and should be placed in the Annex as example.d461g2218iYoshihiro Ohbak|While use of schema is an option required only for XML/RDF query, the definition of the schema is normative, not an example.mRejected 2006/05/17 2006/04/27 EHongFChengGMember^Technical, Binding_38`3a6.1.6 Annex C.czThe defintion of the Information Service Schema is an implementation option, and should be placed in the Annex as example.d461g2218iYoshihiro Ohbak|While use of schema is an option required only for XML/RDF query, the definition of the schema is normative, not an example.mRejected 2006/05/17 2006/04/27 EHongFChengGMember^Technical, Binding_38`3a6.1.6ChengGMember^Technical, Binding_15`61a5.3, Binding_140`140a Annex A-1y used for references.cnecessarysWۅWۆWەWWcWWWޖWneed!W#W+W-W?W@WBWEWSWZW[W]W^WpWuWvWۊW۾WW W1WYWܗWܹWܾWWWWWWWW2W:W݊WݍWWWW4W?W@WneedtocorrectmihgetsttausVneedtoexplicitlystatethatbothtypesoflocationinformaVnformaVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV8.5.3.19*ٟڻ8.6.1ڼaWa4Va-1٠WWWa2١WڽWannex٠W١W٢W٣WڽWھWڿWWWWݭE YoshihiroFOhbaGMember^ Editorial_95`29a 7.4.10.1.3bFix it.c)Replace "Application" with "application".d640g2427 2006/07/20 2006/04/28ݮE YoshihiroFOhbaGMember^Technical, Binding_96`4a 7.4.10.2.2b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccNPreferredPoAIdentifier is not needed if it is part of PreferredLinkIdentifier.d641g2357i Vivek GuptakSee comment 636m Supercededvcomment 527/626w Superceded 2006/07/20 2006/04/28ݯE 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/07/20 2006/04/28ݰE 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.d652g2359er.doc.docccommaۮWWWWWcommandۄWېWWW8W9WOWmWzW{WKWaWzWWWWW(W)W>WEWFWGWHWsWތWޔW3W4W@WcommandcodezWތWcommandsېWWmW{WܴWyWWWWWWWW@WcommandsmaybeinvokedfromupperlayersmihcommandsasweVcommenceܻW{WcommentۯWWW;WW*WBWKWeW8WcommunicateܴWW!W%Wcommunicated2WcommunicatesWcommunicationەW3W Wcomplete/W0W4W5W9WۇW-W܉W܏W WWWcompletedۂWcompletelyYWܰWcompleteness)Wcompletenessconcisenessgrammar)VcomplexityBWcomplianceWܛWW%WcomplicatesWcomponentsWcomposed:WܤWݐWcomposedofmultiplemediatypesitisthehandoverdecisionݐVcomprehendedWdvbycomment339_VbVVV*VMV\V]Vbycomment339andissue3aVbycomment348Vbycomment352360;Vrhood Information using specific IEs: The IEs defined as part of Information Service provide information about different neighboring networks. For example, by using request and response mechanism with TYPE_IE_LIST_OF_NETWORKS option the mobile node may be able to retrieve information on different types of neighboring networks such as 802.11, 802.16, CDMAC2000, UMTS, etc. A mobile node may request a set of IEs to get more neighbor network information. - Heterogeneous Neighborhood Information using pre-defined Information Reports: The heterogeneous neighborhood information may also be retrieved by the mobile node by using the pre-defined reports. For example, the General Information Report provides the neighbor information about link type, number of operators for each link type, and a list of operators for each link type. @gv552W552HWIW555UWVWWWfW57/58W577bWdWݥW578W583W588eW597<W=W>WW6.3.1W6.4.1{W6.4.3{W608W607ݩW609W@W626ݞWݟWݠWݡWݢWݣWݤWݦW632W64ێW641zW>W673NW675ZW687WW7WWܗWeW7-255W7.4.10.2.2ގW7.4.15.1.2ܗW7.4.5.2.4ݽW7.4.8gW704WWW709 W719sWW WWWWWTWUW737݁W741ݶW744ݷW752/756FWXWW8RWWW8-8!W݂W8.4.2.13hW8.6.1OW802.11ەWWWSW802.16 W4W5WSW^W802.21ۓWەWWܛW802.21enablesbothl2andl3transportoptionsV803W824bWcW872W88ێW892WWuWvWTechnical, Binding_92`38a7.4.8b Remove 7.4.8.formation. pc@>j cmihۃWۄWۅWۆWۇWۈWۉWۊWۋWیWێWېWۤWۭW۽W۾WWWWWWWWWWWW,W2W7WHWOWYWZWcWeWkWmWuW܄W܏WܐWܠWܥWܩWܫWܯWܰWܴWܺWܻWWWWWWWWWW W0W3W:W;WAWCW{W|WW݃W݄WݛWݥWWWWWWWWWWWWWWWWWWW W W W WWWWW W!W"W%W'W(W+W,W/W0W4W5W6W7W8W>WEWFWGWHWJWKWLWMWOWPWQWRWWWXWYWaWbWcWfWgWhWiWjWkWmWrWxW|WއWވWޔWޕWޖWޗW1W2W3W5W6W7W޲W޲W޲W޲W޲W޲W޲W޲W޲W޲WOV cBotransactions 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/07/20 2006/04/28 df acknowledgement semantics on arbitrary reverse traffic; windowing allowing multiple outstanding windowing allowing multiple outstanding retransmission and reassembly (including the handling of partly reassembled messagesB3), how the maximum fragment size is established. !d680g2288t algorithms should be used for retransmission and reassembly (including the handling of partly reassembled messagesB3), how the maximum fragment size is established. !d680g2288blocal W-WۂW۳W۶WW7WyWzWW݃W݊WݎWWWWW1W3W4W5W8W<W?Wlocality,Wlocally-W۶WܶW;W_WJWlocation|W܍WܽWWݖWݘW>WlocationinformationisencodedinthisfieldtheݘVlocation-informationݘWlofWlogical݂WW1Wlongtitude-resolutiowWloopWlossFWGWHWIWJWۉWRWYWlostRWlotWW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"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 WmachineWmacmobilenodeWW17EQiaobingFXieGMember^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/07/20 2006/04/248EQiaobingFXieGMember^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  33d848g2268vby comment 495w Superceded 2006/07/20 2006/04/249EQiaobinghcconcatenationWWconceivableWconcept:WconceptsW2W:Wconceptual WܟWconcerns>Wconciseness$W)Wconcrete%WconditionsWWconductۉWconfidence:WconfigurableޖWconfigurationۄWZW\WjW܂W܄WaWWWW5Wconfigurationrequestۄ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)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 2006/07/20 2006/04/24rEQiaobingFXieGMember^ Editorial_111`12a8.2.1bA5Change title to: 8.2.1 L2 Data Frames Packet Format5@a@A  33d679g2325 2006/06/18 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 2006/06/18 2006/04/24rEQiaobingFXieGMember^ Editorial_111`12a8.2.1bA5Change title to: 8.2.1 L2 Data Frames Packet Format5@service and Media Independent Information service. IEEE8Akucschema#WBWuW{W}WہWWWܬWW݀WމWschemaismandatoryshouldbeoptionalVschemaeWschemeWschemesWscope"W/W0W1W2W3W4W5W6W7W8W9WWەWWmWsWܛWܭWWWWW WWIWW7WXWYWiW>WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmogeneousinterferfacVsecondWW݆WW|TEFarrokhFKhatibiGMember^ Editorial_45`20a6.3.2b"defined", not "defied"cSpellingd371 2006/07/20UEFarrokhFKhatibiGMember^Technical, Binding_45`19-21a6.3.2bAIt 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/07/20 VEFarrokhFKhatibiGMember^Technical, Non-binding_46`56-59a6.3.2b:Insufficient information of intent, to suggest any change.c Vaguenessd382v8Need more clarification and appropriate suggested remedywRejected 2006/07/20 WEFarrokhFKhatibiGMember^Technical, Non-binding_47`26-27a6.3.227a6.3.227a6.3.2ied by appropriate references.c"Improper rerence to Internet Draftd375ember<n1mcThe 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 2006/07/20rent 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. d535g2218wDeferred 2006/06/30 2006/04/12 ۆEYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.c,Ucexecution/W0W1W2W3W4W5W6W7W8W9WexhaustedWexhaustiveWWexist۳W"WWWexisting۾WWWexistsWWexpandedFWGWHWIWJWWJWJW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W4W5WexplainthattheremoteflowofeventsandcommandsforfiguVij1W|WW1linktransmissioneventsarelocalonlyseeline47page3V108!WW127!WW128!WW14/15W142!WW17۬W0W187݄W2WTW20XW21-05-0407-04-0000-xBW21-06-0607-00-0000-sXW21-06-0611-00-0000-muW+W21-06-0612-00-0000-r݄W21-06-0612-01-0000-rW21-06-606-01-0000WݻW22W23W24wWWW7W24-49۬W26W3WWXWݻW315@W35W3753?W38W4W45W46W47W6W6.3.4.3.3ܾW6.3.8W687W7.2.1W8.6Wa"WWWܾWWWWW,WTWvWމWaboutBWWhWhWWWhWhWacceptableWWWWWWBWWhWacceptableWWtBWWhWacceptableWWWWhWhWhWcinfoovertlܽVagreedformihfsessionidsV,VWb 7bAChange 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\  33fc 334  33: 33fcA/Syntax error in "(also know as "lower layers")"/@A> 33  33 33>d150g2240 2006/05/147ENada, Golmie, Member^ Editorial_35`38b+! 2006/04/28"EPeretzFFeder^Technical, Binding_103`33bAThis 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  33cransfer d644g2260 2006/07/19 2006/04/289cafewconcernsregardingtable13>Vafurtherexpansionoftheieslistedintable6isneededfܼVageneralcommentwithmiheventandlinkeventsisthatitKVageneralmechanismfortlvtypeisquery/responseisdiscus<ValinkupeventmayalsocarryipaddressrenewalindicationݍVanumberofcommandshavebeenaddedtoallowtheupperlayeVasectiononsystemmanagementismissingVa-1ޗWabbreviation݌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ޖW0WconsistencycustomaryuseۣVconsistencyofterms۲Vconsistencywithsimilarnearbysectionclauses(V*Vconsistencywithinaparagraph/sentence۞Vconsistent۰W۽WWWYWhWܒWܔWW"W#W$W'W/WޗW6W;WAWBWCWconsistentlyܥWܧWconsistingIWconsistsW'WconsolidatedܤWݐWconstWconstantWconstituted/WconstrainedWconsumerWcontainkWZWcontainedۄW܄WcontainsWcontent!W۝WlWWWWt Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool. _Alistair`ButtaraMemberb43c 4/24/2006dTechnical, BindingA/hEQiaobingFXieGMember^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?d623g2317v Remove tablewAccepted 2006/07/20 2006/04/24iEQiaobingFXieGMember^Technical, Binding_106`23a 7.4.15.1.1bAChange 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. @over operations.d571g2315 2006/05/14 2006/04/24gEQiaobingFXieGMember^Technical, Binding_92`38a7.4.8b Remove 7.4.8. 2006/05/14 2006/04/24d29bGChange "is communicating" to "communicates"; "is residing" to "resides"cTensed470 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_62`16a6.3.9bFIt seems that Report Availability should occur after response arrives.cW@WthesearecommandsandnoteventVthesecasesarereferringtoipv6accessnetworktopologiesVtheserecommendationsshouldbehandledbyspecificieee802VVVVVVVVVVVVVVVVVVVVWTWUWVWWWZW]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ܾWWWWWWWWWWVwMkthat<WAWjWkWmWnWoWuWzW{W|W}W~WہWWWWWCWWW)W-WjWthe"W/W0WAWYW_WaWjWkWmWnWoWzW{W|W}W~WہWۓW۳W۵W۾WWWWWWW W"W=WCWܶWܻWWWWWݳWݴWݻWWW+W-W0WSWdWthecommentshouldberejectedforthefollowingreasonsVthedocnumbershouldbe627 VthelinklayerqoscharatersticsareavailabletothestaviVthereasonisnotclear0x2161432bitsVdependency for interoperability or we define "state machine" for MIH. c7The specification does not define the "state machine" d33g2415echnical, 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" d33g2415JYcofWW"W#W+W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WAWFWGWHWIWJWNWXW[W\W^W_W`WaWjWkWlWmWnWoWqWrWsWuWzW{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۽WWWWWWWWWWWWWWWWWWWWWWWWW WWWWWW*W,W-W.W/W2W3W4W5W9W:W;W<W=W@WAWBWCWFWHWIWJWNWyQvcommentersݓWcommentersagreeapplicabletoesandcsbutonlyundercertݓVcommentsZWWWJWKWRW:WcommmentݨWcommunicationW3WݓWTWcompleting WcomplianceܛWcomprehensiveWWconcern WconditionWconditionallyܗWconfidenceQW\Wuctured and can be easily and 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.mRejectedobingZ jbcARDF (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  33d662g2319iYoshihiro 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.mRejectedkbtableW/W0W5W:W;W=WEWJWNWZW[W\WhW|W~W۰WWW%W&W)WDWEWGWHWRWSWcWjWmW܁WWWWUWYW|WݘWݛWݿWWWWW\W^WlWyWzW{WހWނWޔW;W>Wtable22sparqlquerytlvvalueparametersformatހVtable23sparqlquerytlvvalueresponseparametersformatނVtable4-mihcommandsޔVtable6needtomentionthatlengthis4octetsdeletbit3)VtablexxextendedschemaurlparameterformatހV&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&WhemaurlparameterformatހVtable-6ܷWܼWtable-7ܹWtablesWtailPWtakeOWPWQWTWUWVWWWWWWWtakenHWhWtargetۇWW݊WW!W"W$W%Wtaylored۳W NAfCheck the length of items in table-6 and ensure they are consistent with the length in section 6.3.4.x 2006/07/206 BENada, Golmie, Member^Technical, Non-binding_45`11bGDefine and make definitions in section 6.3.4.2.1 and 6.3.2 consistent. c^The length does not match the TLV representation of section 6.3.4.2.1 where length is 2 octetsd367g2252wAccepted 2006/07/206 CENada, Golmie, Member^Technical, Binding_47`42bAReplace "The 802.21 Information Elements may be assigned identifiers (IDs) as follows." with "The 802.21 Information Elements are assigned identifiers (IDs) as follows."@Af 33)  330 33~  33 33fffo be controlled by only one network operator.d361g2250 2006/05/176AENada, Golmie, Member^Technical, Non-binding_44`51chnical, Binding_44`51  #4bB------------ 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    33Rc---------------------------------------------------------------------------------------- V@taGMember^Technical, Binding_49`1a6.3.4g3728 2006/05/01` _cAThe two mechanisms for retrieving information elements currently described in 6.3.5. are both very limited. The first mechanism (retrieving network info using specific IEs) is limited in its usefulness because the value of many IEs are only meaningful within their context, but this retrieval mechanism is not capable of delivering the contextual information of the retrieved IEs. For example, A requester queries about three IEs: NUMBER_OF_POA, ROAMING_PARTNERS, COST In return, it receiveBs: NUMBER_OF_POA=20, ROAMING_PARTNERS={A, B, C}, COST={10, 12, 7, 8.5, 2.3} However, since there is no contextual information to relate these values to one another, the retrieved information is mostly useless (e.g. It doesn't tell which of the 20 POAs belong to roaming partner "A". Or which POAs are related to cost=12). The 2nd mechanism (using pre-defined reports) is more useful but offers little flexibility; if one would want to do a retrieve different from the current pre-defined repooAZ ibcA}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 2006/07/20 2006/04/24jEQiaobingFXieGMember^Technical, Binding_106`43a 7.4.15.1.2bAChange the text to: InfoQueryType |An integer value corresponding | N/A | The type of query that is specified |to one of the following types: | | | 1: TLV | | | 2: RDF_DATA | | | 3: RDF_SCHEMA_URL | | | 4: RDF_SCHEMA | | @emove 7.4.8.formation. pc28201=btoWWWWWW WWWW)W+W.W0W7W:W<W>W?WCWIWJWKWRWUWVWYW\WcWdWeWgWkWyWzW|W}W݂W݄W݊WݍWݎWݑWݔWݕݗWݘݙݚWݵWݶWݸWWWWWWWWWWWWWWWWWWWW WWWWWWWWWW W!W"W#W$W%W(W+W,W.W0W2W3W4W5W7W8W<W>W?WEWFWGWHWIWJWOWRWTWXWYW[W\WfWiWjWlW}W~WހWނWބWޅWއWޒWޕW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WWWWWWWWWWWWWWWWW?`‚"1ã6B܇ԃݱÃ70‚#6G\^roq܌^FR=‚$!vȃ+]‚%,>FYL(1;‚&Ilsƃc܀܂܄ Ճ'Gޓ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!۪Lܔƒ*؃8N޶%V‚*ۑۭ۟!dݕݶ!-A‚1?۷#*<ܙTqڃރޒ޽,]‚2c}۸.V܈ܥ=wݳcޅޜޝڃۃ <=‚3RS܃ܝ>t‚4iqxۥ3ܺDJއ‚53CV:lwՃNݘݾ˃ޱԃ 0Qa‚6WXWYW[W^WaWbWcWfWiWlWtWuWvWyWzW{W}WWހWނWޅWއWމWދWތWޏWޔWޖW0W4W5W5W5W0W0W0W0W0W0W0W0WWWWWWWWWWWWWWWWbinformation@informational@Ginitiated@9insertmihcapabilitypage54line14@ninteger@intent@internal@intra-roaming@ip@Nipv6@isނއޕxissued@itappearsthatreferenceistothedefinitionofoperator-n@itself@l2@l3@Glayers@@least@bline@'lines@link<linkeventderegisterconfirmresponse@linkeventregisterconfirmresponse@qlinktypetypeofthelink@nk@link@typemediatypeofthelink@nktypemediatypeofthelink@rged@ method@%mgmt@kmihfZmihcommandconfirmprimitiveshouldberemovedfromitscur@*mihhandoverinitiaterequest@Xmn@mobilenodeoruserequipment@moreandmergetextbetweenlines23-43into8.3.1@must@need@qneither@networkidentifeirshouldbelinktype@progressed@ S_cCrts, he would have to try and wait for a new TYPE_REPORT_XXXXXXX to be defined in the standards and implemented by the MIIS servers before he can use it. vd443g2308i Subir Dask܇q΃σޏÃ$ƃr+OPބޅ8Ã$ۏQÃ%-ǃЃކޗÃ% كڃސޑޒÃ%0܈܉DÃ%P܊܋Ã%`܌sޓÃ%pRޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓݥЃ ghlup@.bAC)q@rbA'st@7ubBtABKv^?w@Dc@vx@c@ZzcAv{kA|cA]kAL}cAkA~cAkAbAہcAkAۂ@bACEPGcAooPGcAoPGcAoPGcAo should be used. cDiscussion of Logical Network Reference Model uses roaming concepts without introducing them. These are: Home Network, Visited Network. Roaming. d130 2006/05/14EGregFDaleyGMember^ Editorial_105`62a 7.4.14.2.2 bDaleyGMember^ Editorial_18`20a5.3.2b4 2006/04/27EHongFChengGMember^Technical, Binding_38`3a6.1.6d306g2216 2006/05/02 2006/04/274EHongFChengGMember^Technical, Binding_44`51wcalgorithm/W0W1W2W3W4W5W6W7W8W9WFWGWHWIWWalgorithmsWWWalignedWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWambiguitysuccinctnessallowthecasethatmihisnotsupporVamendۆWamendedܸWamendmentۅWamendsۊWamendsmihcapabilitydiscoverymessagebyaddingnetworkidۊVammendmentsWRbcommaW4W5WMWcommandpWۂWېWWWW+W8W9WmWzW{WKWyWWWWWW(W>WEWFWGWHWRWsWWތWޔWcommandcodeVcommandcodezW{WތWcommandsuWېW8WܴWݎWWWWWދWތWޔWcommandsmaybeinvokedfromupperlayersmihcommandsasweVcommentۓWۯW`WcWWWސWޑWޓWcommentsDWEWcommit/W0W5WWcommentsDWEWcommit/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   !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~݂݄݆݈݀݁݃݅݇݉݊݋݌ݍݎݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟݠݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃kdx_‚jB]݀ݚ‚q؃^‚rك_v‚sڃO`zBx=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$WsWܑWWhWݷWݸWWW'WheadertypesmustbefullyspecifiedhVheading2WhedaerܹWWhelptWܴW@WݍWݸWXWYWhelpfulܪWhelpsAWWWWWWWWRWܬ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߽WWWWWWWWWWcxxxxxxx_WbWyesWyouWd 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_WbWۈWۉWۋWېWW:W=W@WHWRWcWrWܤWܯWܳWܴWܶWܷWܸWWWWW+W:WBWݍWݏWݐWݴWWWWW*W6Wdifferenttechnologieshavedifferentnmsinterfaceseg802BVdifferenttlvsshouldbeusedforsourceidentifieranddestݴVݴVݴVݴVݴVݴVݴVݴVdiscoveringېWdiscoveryuWWۊWWdiscussܯWdiscussedDWpWvW+WdiscussionAWWW܏WWdiscussionofhow802.3networkscangetdirectinternetaccVdiscussionoflogicalnetworkreferencemodelusesroamingcVdispatchmWdispatched7WdistinctWdistinguishۊW:WܜW:WdistinguishedWdistributedWdo_WbWeWfWlWۈW۬WWCWܐWWWWWWWNon-binding_56`18g2967 2006/04/29 2006/04/28cenough+WۆWۈWWWWWW"W$WensureWensuring WentailPWentersۇWentierSWentire۽W'WentirelyWentitiesuWW۴W7WZWfWrWW3W{W݈WWWWW3WޔWentitiesmakes݈Ventity:W;W<W=W>WۊWۭW۴WW WZWeWܡWܩWWWW WW{WWWW"W%W7WޖW1W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2Wentry܉WWWEWFWGWHWRWentry2linkeventderegisterhasbeendefinedasaneventeHVentry2linkeventregisterhasbeendefinedasaneventeveGVentry2miheventregisterhasbeendefinedasaneventevenEV.b20܇W)W=W2000W21ۓWPW܁WvW21-06-0460-02-0000-bvW21-06-0522-04-sessioݒWW21-06-0598-00nW21-06-0608-linkݜW21-06-0609-isݓW21-06-0611-00-0000-m{WW21-06-0612-03-0000-r݃W21-06-0614-00܏W21-06-0620-00-0000-nW21-06-0622-00-0000KWLWMW21-06-0624-00-00W21-06-0624-00-0000-n W21-06-0625-00-0000W21-06-0625-00-0000-n W21-06-0627-00-0000 W!W21-06-0627-00-0000-n W21-06-0628-00-0000-aۃW21-06-0629-00-0000-aۄW21-06-0630-00-0000-pۆW21-06-0631-00-0000-pۅW21-06-0632-00-0000-lۉW21-06-0634-00-0000-mۈW21-06-0636-00-0000-rۇW21-06-0637-00-0000-mۊW21-06-0644-02-0000-mkW21-06-0645-00-0000}W21-06-0656-00-0000-wDW6-00-0000-rۇWۇWۇWtenceofitema]VdeliverWdeliversWdemonٿWdependantWdependencemediaWdependent0Wdepending-Wdeployment٤WقWhcthetwostacksinthefigureareidentical9V=Vthetypemustmatchtheonedefinedintable6KVLVtheunderstandingofthetitlelistofnetworkslinktypesiJVtheuniquenessofthemihfidisnotclearforexampleitis Vtheunitoftimeintervalisnotdefined]Vtheusageofaaninfrontoftheacronymmihisinconsisten2VtheusecasesandhandoverscenariosforthecommandsdefineVtheuseofforexampleisinappropriateintherepresentatioVtheuseofnas-port-typeshouldnotbejustanexampleݔVtheuseofthetermmihproxyshouldbeavoided,VtheuseofunreliabletransportmayinfactleadtosignificVthevalidrangefordestinationidentifierisgiventobemiVthevalidrangeofoldlinkactionsisnotconsistentwiththVthevalueforversionisnotdefined݁V ) Name Type Valid RanWRcnotۅ<݌>:notclearwhythescopeofdefinitioncolumnisneededasal@notcustomaryuse@mnotification@obtain@Jof@OY8offers@on@one@only@operation@operators@Eor@order@otherwise@order@otherwise@or@order@otherwise@e@propriateintherepresentationcolumn@column@ution@Qspecifies@standardize@statement@such@,supported@Ysyntaxerrorinnetworksecurityandqualityofsecuritycap@Dsyntaxerrorinthisisusedtorespondtheresult@4systemmanagementhasbeenintroducedasaserviceherehowe@.take@?textneedsimprovement@that@that's@the$\the1sttwosentencesintheparagraphrepeatswhathasalre@theassignmentofistoanyinformationelementshouldnotb@bifW'W.WDWNWTWUWۂWۓWWWWWHWKWLWTWUWVWWWXWZWnWܴWܾWWWWW WWJWݗWWW,WjW4W<Wif0-or-1transactionsemanticsarerequireduseanunderlyi VifcertainclassesoftlvsarenotsupportedViffinergranularityofinformationisusefulathigherlayeViftheprimitiveistobeusedonlybythemihfunctionreplZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVZVWWWWWW#W%W&W,W2W3W5W7W:W=W>W?WAWBWDWEWGWHWNWPWSWTWUWVWWWXWYWinanetworkmodel,VtypeofjVmVinformaAW-bexamplesFWGWHWIWܼWܿWWexapndedIWexceeds\Wexcept$WexchangeuWvWxWWWpWexchanged WWexchanges1W3W4W5WexchangingpWexcludingFWwWexclusiveܟWexecuteۉWexecuteactionthreshoۉWexecuting݊WexhaustiveWexistWexistingWexists,Wexpand@Wexpandgniintheacronymlist@VexpansionexpeciallymWexpectVWVWVW@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۸W WJWstates=W@WWstaticWWOWݏWstationiWstation'siWstatusWWVWXWeW܀W܄W܇WܖWݽWWW*W<W?WstepޗWstepsWstilluWWܕWމWstore܂Wstraightforwad݃WstreamlinestrengthWstrong۳WstructureܬWܼWWWXWYWstructuredjWkWmWnWoWzW{W|W}W~WہWWstructuresWsttausWWsub-optimal۶Wsub-sectionsWWsubclassofvWsubclassofisnotdefinedinthefigurevVsubdivision/WsubjectWZWsubnetinformationaloneisinsufficienttosupportscenario\VsuboptimalWsubscribed7WsubsectionsW1WsubsetWsubstantiallyPWsubsystems/WsubtleWsucceedseWsuccessۄWsuccessful܄W*WsuccessfullyWsuccinctnessWWannex٠W١W٢W٣W7cpreventWWprevious+WۇWۯWWWpreviouslyWprimitive1W2W3W4W:W;W<W=W>WLWMWNWcWdWfWgWiWlWۂWۄWۅWۆWېWWWW5WNWQWkWܟWܺWWWW WaWWWWW!W"W$W%W>WJWއWޔWޗWWW!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&WWWWWWdboptionalWWW'W4Woptional1changenotrequired4VoptionallyۂWV4V4V4V4V4V4V 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 WubaWWW W W WWWW&W)W+W-WSWWW`WvWyWzW݊WݍWݎWݔWݕWݙWݛWWWWWWWW WWWW!W%W'W,W0W2W9W;W=WCWDWEWFWGWHWIWJW[W^WhW}WWހWނWޅWއWދWތWޒWޕWޖW5W5W5W5W5W5W5W5WޖWޖWޖWޖW߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽W߽Wa2EEleanorFHepworthGMember^ 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). d209g2230 2006/07/20 2006/04/2811EEleanorFHepworthGMember^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 2006/07/20 2006/04/28Marked12 0`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. d218g2232r1coverloadiWWowlwWownۋW۳WܽW:WXWYWp10Wp105Wp111Wp122Wp137Wp145EWp152-l15ۑWp158-l16ۑWp158-l39ۑWp18Wp22Wp46-l9ۑWp51-l26ۑWp59WWp72Wp77Wp79Wp802.21SWp802.21/d01.00ېWp90kWpacket۽WW WWW&W'WpacketsW W W*Wpadding/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ۅWche_WbWheader$WuWܑWܓWܔWܚWWWWhWݳWݷWݸWWW'WheadertlvsaredefinedbutnovaluesareassignedtothemܚVheadingW2WhedaerWhelpWtWܼW@W݂W݃WݍWݏWݸWXWYWhelpfulWhelpsIWWݏWhence/W0W1W2W3W4W5W6W7W8W9WܰWWQWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWoposalforaddingaparameterinthemihhaۂVheterogeneous"W1WIWܤWݐWWޠWWWW} cinorderformobilenode'smihfunctionentitytocommencem{Vinsection8.5.4.1thedescriptionisnotcorrectބVinsection8.5.4.2thedescriptionisnotcorrectޅVinsomeplacesieee802.21hassomehowbeenclubbedtogether݅VinthecurrentdefinitionofmessagemihhandoverpreparereۇVinthecurrentdraftthedescriptionabouttheprimitivemihۆVinthecurrentdraftthemihcapabilitydiscoverrequestmesۈVinthedefinitionofmobilenodethesentencethemobilenod3Vinthemihsam7.2.2table14andtable15seemstobemissiݛVinthesentenceconceptualtransfertheoccursbetweenthei Vinthisstandardinordertoaccess3gppservicesprovidestVin-depth܏Win-scopeWinaccurateܰWdestVin-depth܏Win-scopeWinaccurateܰWܰWdestVin-depth܏W܏Wrdertoaccess3gppservicesprovidestVin-depth܏W܏W7K5cwhetherWWsWWWWW W WWW2WWWOW4Wwhethertoincludethemihfid/sidisnotapparentlydefinedVwhich:W;W<W=W>WEWLWMWOWPWQWRWSWTWUWVWWW_WaWlWuWWWWmacُW٨W(W:W=W?WjWuWmacaddressisnotsuitableforallmediaalsohowaretechn:V=Vmacaddressquestionagainistheuseofmacaddressessuita?Vmac/phyڍWmadeWmainWmainlypWmaintainedIWmaintainsfWmakeWWGWcWهWdWiWjWWmakeindefinitearticleformconsistentcVmakesWڄWWmakingWmanageXWmanaged-WZWmanagementW;WWWmanages-WmandatoryWiWWmany:WWWWWmaterialWmaximumLWWWYWmaximumlengthofthesessionidandothersyntaxaspectsarYV{EEleanorFHepworthGMember^ Editorial_112`5a8.3bchange to register.cTypo: rregister d700g2290 2006/07/20 2006/04/28EEleanorFHepworthGMember^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/07/20 2006/04/2824 EEleanorFHepworthGMember^Technical, Binding_112`51a8.3.1b~Include guidelines on rate limitation and timer adaptation for retransmissions, or use a transport which is congestion-safe. on-safe. cDu(ctlvs|W~WܕWܚWݴW"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۳WܾWWunderlyingWWW W Wunderstand۾WunderstandingWunique=W[WsWݔWފWuniqueeventidentiferWuniquelysWuniquenessTWunitHWunitedSWunitsYWunknownkWnW^W}WunlabeledhWunlessۖWWunlessotherwisenotedmediareferstomethod/modeofaccessۖVunnecessaryWunnecessary/misplace WunregisterWWunrestrictedHWunsuccessfulVWXWuntilۑWWWWuntiladditionaltextisprovideditshouldbedeletedVupOWRWܰWWW/WݍWޕWupdateۊWۋWSW܍WWWWWWWaW{Wupdateaccordingtosubmitteddocument21-06-0637-00-0000-mۊVupdateaccordingtosubmitteddocument21-06-500-02-0000-neۋVupdatediagram/textaccordinglyVupdatefig29anoverallflowcontroldiagramisrequiredshVtypeiepoalo܍VW   !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~܀܁܂܃܄܅܆܇܈܉܊܋܌܍܎܏ܐܑܒܓܔܕܖܗܘܙܚܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܮܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ dÃe@RÃePÃe`ÃepݠÃefÃeSÃeÃfݡÃf _Ãf0`Ãf@HÃfPޖÃf`TÃfpݢÃfUÃfÃfݣÃgVÃg ݤÃg04Ãg@WÃgPÃg`cÃgpdÃgeÃgܐÃgۍÃhaÃh fÃh0ېÃh@ۊÃhPÃh`gÃhphÃh0ÃhÃhÃi[Ãi bÃi0ݥÃi@cÃiPdÃi`JÃipeÃiKÃiLÃiMÃjÃj ݦÃj0IÃj@5ÃjPÃj`ݧÃjpÃjjÃjkÃjÃq݇Ãq Ãq0یÃq@ÃqPÃq`ÃqpÃqݨÃqfÃqÃrcÃr ݈Ãr0Ãr@ÃrPgÃr`ۃÃrphÃrdÃrÃriÃsÃs jÃs0Ãs@hÃsPkÃs`ݩÃspݪÃsۄÃslÃsgÃtÃt ۆÃt0mÃt@ÃtPݫÃt`1ÃtpݬÃtۋÃtۂÃt܎ÃuݭÃu ݮÃu0iÃu@2ÃuP!Ãu`3ÃupݯÃu6Ãu4Ãu Ãv<Ãv "Ãv0ݰÃv@#ÃvP$obcurrentlinkactionۂۋW6WcurrentlinkidentifieۂۋW!WcurrentlyTWUWVWWWXWcWWޖW5Wcurtailed۸Wd WWWdmihfunctionmaydofurtherprocessingonmac/phytriggers Vdmihnetsapgenericnameforthemedia-dependentinterfaceVdmobileipregistrationmightbetriggerednowVdash۝WۣWۧW)W8WGWdataVWWWiWjWkWmWnWrWsWzWWWWW#WYWqW|WܷWWWW}W~WނW6WdatarateVdataschemaisadoptedVWނW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WWdayHWdbYWdcd|WdcnKWLWMWdealingۈWWdecision W#W?WvWwWWfWܤWܴW.WޞWޡW޽WWWW WW,W>WAW]Wn8bintegerjWmW\Wintelligent#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'breferenced@1register@_related@remotely@removeܛ?removeaccessto@2removeexampleorbetterconveyincrementalvalue@removemiddlesentenceremoveinthiscaseatend@removemihhandoverinitiatemihhandoverpreparemihhandov@removenumberofaddressheaderidentifiers@Rremovesection8.3.2.3ݳ93ݳ94.15.3.37.4.15.3.4@removesections8.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"WcW ۔vA 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 2006/07/20l uses roaming concepts without introducing them. These are: Home Network, Visited Network. Roaming. d130 2006/05/17EGregFDaleyGMember^ Editorial_105`62a 7.4.14.2.2 bDaleyGMember^ Editorial_18`20a5.3.2b4 2006/04/27EHongFChengGMember^Technical, Binding_38`3a6.1.6lable) to establish network-layer connectivity@3701 2006/05/01W$W'W(W cthisisalinklayerindicationwhichshouldonlybereceiveOVPVQVRVTVUVVVWVthisisalinklayerprimitivewhichshouldonlybegenerateLVMVthisiscriticallyimportanttodescribeinfulldetailthe'VthisisnotanexhaustivelistwhataboutgalileoandglonasVthisisredundantthemihconfigureprimitivesee7.4.7hasgVthisistrueonlyforlocaleventsandnotforremoteeventsܫVthismechanismretrievingnetworkinfousingspecificiesisaVVVVthisisnotanexhaustivelistwhataboutgalileoandglonasVthisisredundantthemihconfigureprimitivesee7.4.7hasgVthisistrueonlyforlocaleventsandnotforremoteeventsܫVthismechanismretrievingnetworkinfousingspecificiesisaVthisneedtobere-writtenasaproperreferenceVthisprimitiveisdeliveredfrommihfunctiononoldpoato"VthisprimitiveisissuedbyupperstocontrollayerlinksV9 :cA   33  33  33n  33  33  33  33D  33_  33  33  33(  ^  33n how the Media Independent Information Service can or is to be utilised. d312g2211vChange AAA to MIH RegistrationwAccepted-Modified 2006/05/17 2006/04/26 }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. d312g2211vChange AAA to MIH RegistrationwAccepted-Modified 2006/05/17 2006/04/26 Description ------------------------------------------------------%{bmergedWWmessagelWuWvWwWWWWWoWsWyWzW{W܄W܅WW\WW W"W#W$W+WWބWޅWދWތW7Wmessaged-idۉWmessages WpWuWxWW۸WWݎWW"W1W3WmessagetooWmethod(Wmethodlengthshouldbe2octets(V(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\WminuteHWWbW0sGENada, Golmie, Member^ Editorial_49`38bAiReplace "The encoding format is defined as table below." by "The encoding format is defined in Table 8."i@Af 33)  337 33]  33g 33fcA@Syntax error in "The encoding format is defined as table below."@@A> 330  33> 33>d417g2257 2006/07/20HENada, Golmie, Member^Technical, Binding_50`26b 33fcA@Syntax error in "The encoding format is defined as table below."@@A> 330  33> 33>d417g2257 2006/05/22HENada, Golmie, Member^Technical, Binding_50`26bon-binding_48`58b 33~  33 33f the data so they match an agreed schema (this doesn't mean you have to send XMal )bR title "Media Independence" is confusing and does not make much sense.d234g2250 2006/07/17 2006/04/24XyY{Z[\]^_]^_Ã@܇Ã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 ABCDEFG^H_I`JaKbLcMdNgOiPjQkRmSnTpUvVwWxXyY{Z[\]^_TܞoܠcA5ܡ|ܣ@ܤbAܧ@ܨ@ܪbܫ@duܬRܮ@ܰcAܱ@cܳboܴ@ܵGܷbAܸgܺcA ܻkJܽboܾcAܿbujAfc3b@bj@-cAy@@cA@a@@2v@cA@c<cGbN@HcvABdL@E@O@cAfcpv/@Tjb[clcAcccAc@j@O`vr@qbW@,icB@c@{b @ b @cA cAnboutside W#WsWvWwW۶WoverOWPWTWuWWܗWܘWܙWPWW+Wover-the-air۸WoverallWoverhead۸WWowl^WwWowlonpropertyrdfresourcelongtitude-resolutiowVp0028-100&Wp0028-200&Wp69/l65yWp70/l13yWp71/l3zWp72/l21zWp72/l62{Wp90kWpacketrWsWqW WWW&W'WpacketsUWVWW Wpage|WۮWWWWhWܬW(W,W/W]WfW݄W.W0W1W2W4W5W6W7W:Wpage14line26setupinsteadofsetup/VpagesWpagingW7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7Wetup/VpagesWޘWWW8WvWߴWWpagingWpairFWGWWWWW3W4WdWeWߢWߣWWWWWMW`‚sAbknۘǃHh‚ty‚u*۽gܨf݇ݞݦݧݵɃ%}‚ve۾ b8CKMݚݻƒޕ4?A‚x)6Ã"oÃ#Ã# \Ã$]Ã%ÃۿÄ"#Ä'XV3urlresponseoneextendedschemaurlparameterV3.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`H AbB 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 contCinuity 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 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_bassociatedWmWW%WassociatingWassociation3Wassume WassuminguWassumingtwomihfunctionshavealreadydiscoveredeachnoteuVasynchronouspWatW,WAWsWۘW۶WWWW4W7W=WQW܌W܍W܎WܚWWWW W"W(W;WOWgWkWuWW&W>WZWyWzW{WޖW5Wattach#WattachingܺWattachment,W?WWWattachmentsAWWattainableWattempts&WattributeW=WUWYWݔWݕ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ܽW0WbasicAWbasicallyWeW lvAQChange 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 2006/07/20 2006/04/24mEQiaobingFXieGMember^Technical, Binding_107`42a 7.4.15.2.2bto: 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@g3045 2006/04/29x ^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 }Wkbincluded~WWWincludeingSWincludes?WAW@WincludingWuWWSWincludes?WAW@WincludingWuWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW[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ވW7]ESanjeevFAthalyeGMember^ Editorial_115`60-61a8.3.3.2bRemove "is embedded".cSuperfluous words.d750 2006/07/20ESanjeevFAthalyeGMember^ Editorial_118`5a8.4b "definite"cSpellingd762 2006/07/20ESanjeevFAthalyeGMember^ Editorial_119`18a8.4.1.2b"command code"cMissing space between words.d779 2006/07/20ESanjeevFAthalyeGMember^ Editorial_122`40a8.4.2.2bCapitalize "Management"c Customary used789 2006/07/20ESanjeevFAthalyeGMember^ Editorial_123`12a8.4.2.3bARemove square brackets here and 3 additional places on this page.cMMisleading use of square brackets, which are customarily used for references.anagement"c Customary used789 2006/05/14ESanjeevFAthalyeGMember^ Editorial_123`12a8.4.2.3bARemove square brackets here and 3 additional places on this page.cMMisleading use of square brackets, which are customarily used for references.%ctries.WXWYWtriggerۅWWW"W$WtriggeredJWtrip Wtrips WtrueuWWWܫWWtry_WlWWtryinglWXWYWtwoWW_WqWuWvWۦWW.W1W=W@WIWܜWWWW2WJWWWWWWW&W'W9W<W=W>W?W=W@Wtwodefinitionsofthesametermmobilenode.VWWWWWWWWWWW?W@WCWKWLWRWYW|WܗWܼWܾWWWWWWWWWWW W W~W݃WݠWݺWWWWtypeiepoacapabilitiesthesecurityandqoscapabilitiesoܾVtypes=W@WIWJWYWܤWWWWWWWhWݐWWtypicallyܤWܱWݐWWtypicallyinaheterogeneousnetworkݐVtypicallyinaheterogeneousnetworkcomposedofmultiplemeܤV۠_5`5a2b&Fix typo toward the end of line "All".cTypographical errord36 2006/07/20ۡESanjeevFAthalyeGMember^ Editorial_5`50a2bReplace with C.S0004-D. c%3GPP2 document number should be used.d42 2006/07/20ۢESanjeevFAthalyeGMember^ Editorial_7`6a3b+Replace "facilities" with a more clear termc"facilities" is too generald48 2006/07/20ۣESanjeevFAthalyeGMember^ Editorial_7`38a3b#Remove dash between link and layer.cConsistency, customary use.d53 2006/07/20ۤESanjeevFAthalyeGMember^ Editorial_8`18a3bRemove the second SAPc#MIH_SAP already has SAP in the named56 2006/07/20ۥESanjeevFAthalyeGMember^ Editorial_8`23a3bRemove sentencecThis sentence is circular.d63 2006/07/20ۦESanjeevFAthalyeGMember^ Editorial_8`21, 28a3bDelete one of them.cMThere are two Mobile Node definitions. The definition on line 21 seems wrong.d72cthecommandmihconfigurethresholdsshouldallowtodefineޔVtheconceptsofposandnon-posarenotusedanywhereelsei2Vthecontentinsection7.2.2.1section7.2.2.2anditrespeclVthecurremtspecsaysvariousclassesofinter-operabilityaVthecurrent802.21draftdoesnotincludeanadequateframewnVthecurrentinformationelementsinsection6.3.4.1needimp]Vthecurrentinformationelementsintable6arepoorlydefinZVthecurrenttextimpliesthatthediscoveryofmihfunctionVthedecriptionisthesameastherequest܄VthedefinitionofeventidsaremissingitiscriticallyimpNVthedefinitionoftheparameterforsupportedisqueryismissdVthedefinitionsgivenforthemihhandoverxxxprimitivesin܏VthedefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofthemesageisthesameastherequest܅V co mcd667g2322iYoshihiro 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 of commenterwRejected 2006/07/20 2006/04/24 nEQiaobingFXieGMember^Technical, Binding_107`62a 7.4.15.1.2bhe 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.mRejected;canother@-anywhere@`architectural@are:area@as@}aspects@associated@aware@@be[7T2Tbeacon@because@been@gbefore@below@beyond@both@bs@butܼby@8both@bs@butܖby@8urrentfo@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-2 ݂cAThe 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 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. .d127i Qiaobing XiemAcceptedvRejected by Vote: 8-8wRejected{l) none needed 2006/07/20 2006/04/30 ݃EEric FNJEDJOUGMember^Technical, Binding_24a5.5b24a5.5blid local or remote identifier"-------------01cVkprimitiveOWܺWxWprimitives"W/W0W۾WWWprimitives/mechanism/Wprobably/WprobeWprocessWprogramming0WproperWproperlyWproposalWPWproposedQWprotocolWݳWݴWprotocol/mechansim0WprotocolsWWprovideWWqosWܼWqueriesaWWqueryaWbWjWkWmWnWoWzW{W|W}W~WہWWWW|WܻWWoW_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  mbAChange the text to: InfoQueryType |An integer value corresponding | N/A | The type of query that is specified |to one of the following types: | | | 1: TLV | | | 2: RDF_DATA | | | 3: RDF_SCHEMA_URL | | | 4: RDF_SCHEMA | | @Af 33   fcARDF (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.@FXieݧ^Technical, Binding_85`64a 7.4.4.2.1b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc- 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/07/20 2006/04/28ݨE 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/07/20 2006/04/28ݩE 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/07/20 2006/04/28ݪE YoshihiroFOhbaGMember^Technical, Binding_92`2a 7.4.9.1.2287QGMember^Technical, Binding_76`42a7.3.11.3bAdChange 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.d540g2294vMIH 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.@A>  )c   TT  >wAccepted-Modified#bretrieved_WbWlWWWWretrievesfWretrievingRWW8WreturneW܆WreturnedbWېWVWXWreturnsېW܄WWreview;Wreviewsection6.3andmakechangesasneeded;VreviseqWrevisionUWYWrevisitWWWWrevisitparametersusedbylinkdownforidentifyingaccessVrevisitparametersusedbylinkupVrevisitparametersusedbylinkupforidentifyingaccessroVrevisitwhetherthisissuitableVrewordWVVVWܷ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ܬWmetricsOWmetropolitanpWmgmtܴWmh2WmibWmicsuWܴ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[WWbrealWWreasonW,WTWreasonsIWreassemblyWreceiptېW\W Wreceive-WLWuWېWUWVW\WWreceivedHWIWVW5WreceivesNWreceivingWWXW WreceptionWW܌W"W$WrecipienteWfWlWېW\WrecommendationqWrecommendationsܩWWrecommendedWreconfigureWreconsideriWjWreconstructedWrectangle,WredefinebWCWredefinethemwhereeverthereisadiscrepencyasrequestcoCVredrawWredrawthefiguretoindicateallpossibilitiesordeletethVredrawing۽WreevaluateRWRWRWRWRW*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*WBWreferencecouldbemadetostaticschemaeintheisqueryVtbremovesections7.4.15.3.27.4.15.3.37.4.15.3.4@removesentence@Dremovetable22fromline41page127toline8page128@"removetheentiresection8.5.3.11and8.5.3.12@ removethesentencethisincludesthelistofnetworkoperat@removing@|renamethenon-posmihentitytomihnon-posforconsistency@ rephrase@replace@replaceafterupperlayerentitiesmakeshandoverdecisionw@replacelinkbynetworksincethisisnetworkselection@replacelinkcommandoriginatewithlinkcommandsoriginate@replacelistofnetworkslinktypeswithlistofnetworktyp@replacenetworksecurityandqualityofsecuritycapabilitie@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 ccapabilitiesuW<WܾWcapabilityuWWۈWۊWېWWWܬWWWWWPW_WuWݥWW+WJWOWPWQWXWYW\WfW8Wcapable_WaW;WOWcaptionKWcaptureWcareWcarriedWyWzW{WݳWcarriesܕW'WcarryܰWWaWݍWcaseۂWWWWWZWܺWWW W W`WݗWWW Wcase2descriptionisincorrectݗVcasesۈWWW܄WܷWWW'Wcategorization:WcategorizedRWcategory!W)WcatualwWcatuallengthofthevaluefieldwVcauseZWjW9W>WcausesbW|WWcausingWccsds>Wcdma2000DWcellWcellsWcellularWcertainWܻWWW:WcertaintyhWchanelW.WsWܳWܷWܸWܹWܾWܿWWWclearerWclearlysWܪWܴWW  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  33d679g2325 2006/07/20 2006/04/24 access and control of a variety of media dependent 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. IEEE8iel~baddingW&WadditionWadditionalSWVWWW*WtWWbWݸWadditionalbehaviourforthegetinformationprimitivesneedVadditionallyۗW۶Waddress:W;W=W\WxWWWkWݍWݷW"W#W$W%W~W4WaddressingkWaddressingthenewpoashouldchangetoaddresswhenatthekVadequatelyܬWadjustOW܁WadoptݒWݓWݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWݨWݩWݪWݫWݬWݮWݯWݰWݱWݻWWWWWWWWWWadoptsuggestedchagesdescribedid21-06-0609-ismultihopsݓVadoptsuggestedchange1in21-06-0522-04-sessioidentifierݒVadoptsuggestedchange4in21-06-0522-04-sessioidentifierVadoptsuggestedchangein21-06-0608-linkidentifierdocݜVisementNWadvi WafterW-WۮWWWW`WfWܺW4W5WHWMW "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 4  =  33\  c  f  33      33  33cc Add context transfer d644g2260 2006/05/14 2006/04/28WEEleanorFHepworthGMember^ Editorial_110`16a8.1b Clarify text.c>Not clear whether this is an MIH protocol or MIHF protocol d681g2287 2006/07/20 2006/04/28EEleanorFHepworthGMember^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. 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. !d680g2288a"btlvsWܕWݙWW 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. !okAJust 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.mRejectedvas per commenter requestwRejected 2006/07/20 2006/04/24 IIS is not sufficiently justified.@A  33d676g2324iYoshihiro Ohbakd676g2324iYoshihiro OhbakR 33  Rcember^Technical, Binding_107`42a 7.4.15.2.2bnformation. Once the information is retrieved the recipient responds with MIH_Get_Information.response primitive.L@g3027 2006/04/29 kcARDF (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  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.mRejectedobing3 uFvHBy comment 752/756 by contribution 21-05-0671-00-0000-802 21-FrameFormatw Superceded 2006/07/20 ding when value field is greater than 128.cIThe length encoding when value field is greater than 128 is not accurate.d407iWolfgang GrtingjX- Change figure 20 as shown in 21-06-0607-00-0000-support_for_comment_res.ppt, slide 3 wDeferred 2006/05/22g encoding when value field is greater than 128.cIThe length encoding when value field is greater than 128 is not accurate.d407iWolfgang GrtingjX- Change figure 20 as shown in 21-06-0607-00-0000-support_for_comment_res.ppt, slide 3 wDeferred 2006/05/22 33\ _ 33fc?"... autenticated with the POA and ..... ", should be new POA d387g2450 2006/05/17$EDasFSubir^Technical, Non-binding_47`52a6.3.3.bAnSuggestion: 0x00000100 - 0x1FFFFFFF Reserved for 802.21 Core 802.21 specific IEs except header specific IEs nUpengۇWۈWperetz  !"#$%&'()*+qiaobing !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ۀہreijoSronny{|sanjeevەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱۲۳۴۵۶۷۸۹ۺۻۼ۽۾ۿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃bremoveaccesstoVremoveack-rspbitandchangereservedfieldto5bitsyVremoveannexbۀVremoveannexcہVremoveassuchVremoveatnetworksideuVremovebasicallyVremoveboldformatfortimeboundandconfidence:Vremoveconceptsofposandnon-pos2VremovedashbetweenlinkandlayerۣVremovedashinlink-state8Vremovedashinmobility-managementGVremovedestinationidentifierparametergVremoveeitherdifferentorheterogeneousۙVremoveentiresection7.4.101Vremoveentiresection7.4.112Vremoveentiresection7.4.123Vremoveentiresection7.4.134Vion7.4.134V4V7.4.134V4Vtion7.4.134V4V7.4.134V4Vtiresection7.4.123Vremoveentiresection7.4.134V4Vtiresection7.4.123Vremoveentiresection7.4.134V4VtypepossiblyaddlinktypeinsteadVremoveinthe21draftPVremoveisembeddedVremoveitis۹VbinyWzW{W|W}W~W݃W݊W݌WݎWݒWݔWݕWݖWݘWݛWݜWݝWݞWݟWݠWݡWݢWݣWݤWݥWݦWݧWݨWݩWݪWݫWݬWݮWݯWݰWݱWݻWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW W"W$W&W'W+W,W1W3W4W5W7W8W>W@WBWIWJWKWLWMWPWSWWWuWWހWނWކWއWފWދWތWޏWސWޑWޓWޕW4W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WޕWޕWޕWޕWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsW`^#bresidesWܟWresidingWresolution,Wresource܇WW!WwW6Wresources"WpWۂW۸WW Wrespective*WWrespond܅W܆WrespondseWlWېW\Wresponse_WeWlW}WۄWۊWۋWېWWWWNW\W܁WܕWܿW\WyWzW|WWWWW%W+W>WBWJW[WrWyWzW{W}W~WނWރWޅW0W=WresponsenetworktypeۊWresponsesܕWresponsibilityWnsesܕ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 o| ܠcAdMIH Media Independent Handover MIHO Media Independent Handover both have the same expansion. d@A> 33"  33E 33>d88g3247 2006/07/20ܡEVivekFGuptaGMember^ Editorial_14`7a5.1.5bANetwork Selection is the process by which a mobile node or a network entity collects policy information on its neighboring networks and selects a network (possibly out of many available) to establish network-layer connectivity Replace link by network, since this is network selection@A> 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>d94g3248g3245rial?bDelete or add a new definition c3Administartive MIH event type has not been defined d283g2443 2006/07/203EDasFSubir^Technical, Binding_40`40a6.2.3b7Accept the contribution 21-06-0625-00-0000_Figuer18.pptc6Figure 18 is incomplete. Local commands are not whown d293g2444i Vivek GuptakJmake the figure more confusing. maybe use two separtae figures if need be.mRejectedvby comment 287w Superceded 2006/07/20Marked18 a6.3.2bA=# 2 should be replaced by Information about Access Networks =@A* 33 *c\Information service classification is not consistent with the Information elements Table 6. d343g2446i Vivek Guptak[1] is General Access Network nformation and so : [2] Information about access networks (as suggested) does not make it that much different...mRejectedwDeferred 2006/06/30 EDasFSubir^Technical, Binding_44`65a6.3.265a6.3.2ttEQiaobingFXieGMember^ Editorial_111`58a8.3bA*Change title to: 8.3 Protocol Description*@AR 33    )c  RcATitle needs to be improved.@A  33d694g2329 2006/07/20 2006/04/24uEQiaobingFXieGMember^Technical, Binding_111`61a8.3bAChange text to: Assuming two MIH Functions have already discovered each (Note: MIH Function dicovery mechanism itself is out of scope), The the Media Independent Handover Protocol provides the following services: [1] 1) MIH capability discovery: MIHF in mobile node or MIHF in the network discovers the capability of a peer MIHF and which entity supports MIHF. Thereafter the peer MIH Functions discover, negotiate and select an optimalum transport for communication between them. The MIH Fuon between them. The MIH FuA  33d690g2328 2006/05/14E8k /bAThis parameter specifies the list of commands IS query type that may carried in a message. Each command IS query type is represented by a command code and occupies one byte.@A  33%  - ; 33`  g u 33v   33c6The description of IS Query Type List is not correct. d781g2426wAccepted 2006/07/20ހEKenichiFTaniuchi^Technical, Binding_127a8.4.2.23bhnical, Binding_119`48a8.4.1.4bAThis parameter specifies the list of commands IS query type that may carried in a message. Each command IS query type is represented by a command code and occupies one byte.@A  33%  - ; 33`  g u 33v   33sparql>", Success)X bA 1) Change the type of the Network Address Information to a new value (allocate a new one, or split the entry into Network Address Information (just an address) and Routing COnfiguration Information (RA). 2) Indicate earlier in the document, that message fragmentation and reassembly is the responsibility of the underlying MIH transport protocol, and a minimum reconstructed message Bj size of X (X ~ 2000 octets??) should be supported. TCP/IP and UDP/IP already do this. XcANIPv6 router advertisement cannot fit into the IP Address type. Though the IP Address field is variable length, it is not logically, an IP address. It is a message of up to 1500 octets. There is no description of Fragmentation, or message size limits, to handle this case Nd657g2218vby comment 597 (FKhatibiGMember^ 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 2006/07/20)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 2006/07/20*EFarrokhFKhatibiGMember^ Editorial_8`18a3b(Remove "MIH Users are" in the beginning.c0Consistency with similar nearby section clauses.d57 2006/07/20+EFarrokhFKhatibiGMember^Technical, Non-binding_8`57a3b_Change "Network-side endpoint of a link that " to "Network-side endpoint of an L2 link that "c(EFarrokhB6 Wcd34g2236v by comment 31w Superceded 2006/07/20 2006/04/24s), 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. ]@A*  33\  *cAThe 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. @rability 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. @\]^_]> cnotۅWۆWۈWۊW۔WەW۟W۪W۬W۽W۾WWWWWWWWWWWWWWWWW W WWWWWWWWWWW"W$W(W)W.W3W=WAWBWCWFWJWYWZW]W`WeWhWkWmWnWsW{W܁W܂W܄W܋WܐWܒWܔWܕWܖWܟWܢWܩWܫWܰWܱWܳWܷWܸWܹWܺWܾWܿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWW W!W%W0W2WEWGWOWXWaWeWhWxW{W~WW݁W݂W݃W݃W݁W݁W݁W݁W݁WWWWWWWWVyuba-4Waabbccddeeff~WabilityWable.W_W#W\WOWabortreasonۋWaboutAWDWVW_WpWۃWېWWWW9W|W݊WWW9WaboveWZW]WsWܬWܭWܴWW#WWWWWabstraction5WܟWacceptۃWۄWWW W!W{Waccept21-06-0627-00-0000iesdoc V!Vaccepttextchangesinthecontribution21-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-0000figuer18pptVacceptedWWWVacceptedWWWۃVۃVۃVetherthescopeoftheprotocolfunctionsLVitisnotinscopeof802.21toprovidehorizontalhandoverVitisthefirsttimethattheframestructureisreferredtoVg&cmissingWWW'WCWNWWWWWSWbWdWgW܎WܨWܵWW&WiWrW݆WݛWݪWݫWݿWWWWWWDW[W\WޒWޗWmissingaperiodޒVmissingathatinthefollowingsentenceandcoordinatetheVmissingcommaVVmissingdashrVmissingreferencesfrom3gpp2&VrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVrVlenodewithmihfunctiongenerallyhasseveraldifferenۉVmobileterminalchangetomobilenodeۏVmobility"W:WܤWܴWWmodeۂWWmodel!W$W۽WW"W:WAWFWmodify;WmoduleܤWmore_WwWۆW۳WWWWW-W:WܓWܗWܸWܼWܿWWWWWWWWWWWKDv^Technical (was Editorial)_112`13a8.3bADelete the following text: The standard describes the MIH frame format, message formats, and the procedures for MIH message exchange to facilitate handover in a media independent manner. However, handover policy and handover decision making is outside the scope of the standard. @A> 33  33  TT>cAyThe 1st two sentences in the paragraph repeats what has already been sufficiently discussed earlier. No need for it here.y@A  33d703g2331 2006/07/20 2006/04/24iscovery (using beacons or using broadcast MIH messages). 2006/05/14 2006/04/24vEQiaobingFXieGMember^ Editorial_112`13a8.3bnctions discover, negotiate and select an optimalum transport for communication between them. The MIH Fuon between them. The MIH FuA  33d690g2328 2006/05/14E8[3caware W0W1WawayWb_WaWۀWWbaddanstorelayonline24VbackeWWbackbone+WbackoffWbaseiWjWkWmWnWoWzW{W|W}W~WہWbasedWiW۶WWܘWWmWbasicOWXWYWމWbasically݂Wbasis9WbbmWbeW$W-W:W;W<W=W>WAWEWFWGWHWIWJWKWLWMWOWPWQWRWSWTWUWVWWWXWYW_W`WbWcWdWfWiWjWkWmWnWoWqWsWtWzW{W|W}W~WہWۂWۄWۅWۊWۋWۍWېWۓWەW۝WۡW۪W۴W۵W۷W۾WWWWWWWWWWWWWWWWWed2W3W4W5W6WexpectedWexplainHWIW|WJWexplainusageofthewordmediaIVexplanation WexplanatoryWEPeretzFFeder^ Editorial_16`42b(Mobile Node or User Equipment)cChange (User Equipment)d113g2225 2006/07/20 2006/04/28EPeretzFFeder^ Editorial_18`22bWhen provisioned, the MNc*When provisioned the MN.... missing commad131g2226 2006/07/20 2006/04/28EPeretzFFeder^ Editorial_18`31b"to, or co-located with the PoA....c,to or co-located with the PoA missing commad133g2227 2006/07/20 2006/04/28EPeretz FFeder^ Editorial_18`38bAjby R1, R2 or R3 over any access network and two MIH network entites can communicate with each other via R4j@EPeretzFFeder^ Editorial_18`31b"to, or co-located with the PoA....c,to or co-located with the PoA missing commad133g2227 2006/05/16 2006/04/28EPeretz FFeder^ Editorial_18`38bAjby R1, R2 or R3 over any access network and two MIH network entites can communicate with each other via R4j@pvtK ubA 33  )c  TT    )c    TT    )c  .  )cP  TT    )c  TT    )c     )c  5  TT  )c  TT>  TT@ B TTD  )cH    TT  )c  <nosal "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.mRejected 2006/05/18 2006/04/24 between them. The MIH FuA  33d690g2328 2006/05/14E8 T܆cA> 33!  33( 33>  33   33  33w@Af 33!  33- 33Z  33i 33fcACSyntax error in "the list of events that may carried in a message."C@A> 33)  335 33>d72g2310 2006/05/01ENada, 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."@3013 2006/04/29?vwEQiaobingFXieGMember^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  33fs in the paragraph repeats what has already been sufficiently discussed earlier. No need for it here.y@A  33d703g2331 2006/06/18 2006/04/24wEQiaobingFXieGMember^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  33f[fbtheWW 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ۚW۠WۤWۧWۨW۪W۫WۭW۳W۶W۷W۾WWWWWWWWWWWWWWW (otherwise, "Show All Records" button in Create and g2461 2006/04/288*"balsoAWVWWW_WbWsWuWۜWۧWWW6W=W܂WܷWܾW)WOW\WݍWWW W"W/WDWއW:Walsoneedtoaddtable33aValternativelyۗW۶WW(WalthougOWalthoughWalwaysWݗWamendWWPWamendreferencesVamendsentenceVamendtailendofsentenceasgsmcdmaoranyothercellularPVamendmentۅWۆWamendments)WWammendmentsWܘWWamong3Wamount۾W۾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'ܙ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" c3No proper example is given for TLV reques/response.d675g2269vSee 413w Superceded 2006/07/20 2006.04.25Marked  ܚ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 @A> 335  33>c:Header TLVs are defined but no values are assigned to themd890g2270wAccepted 2006/07/20 2006.04.25 ver_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.d663|WcunlikelyWunnecessaryiW\W]Wunrealistic*WunreliableWWunspported.WunstructuredZW]Wunsuitable^WunwantedZWunwieldy9Wunwieldysentence9VupWWWWݍWWކWޕWޗWup-to-date۾WupdateZWupdated)W;W>W?WkWWW W W WޗW4WupdatesۋWWupdatesmihhandoverinitiatemessagetoextendmihfunctionۋVupgradeWupon W"W$W*Wuponreceiptthereceivingmihfunctionintheoldlinkmay Vuponreceptionofthisprimitivethemihfonnewpoamayeit$Vt$V$VV$V$VV V V V V VOWPWQWRWSWTWUWVWWWۅWۉWېW۵WW7WYWZW\WcWeWfWܢWWW݇WݍWݎWWWWW"W$Wuppers݇WWWWurl{W}W`btraversedWtreeZW]W_WbWtrees_WbWtrieslWtriggerHWIWIW"W$WtriggeredWtriggers WtrueWtryinglWtwo?WuWxWWYWsWܬWWfWwWyWzW݃WݖWWW&W'W,W;Wtwooptionsfortheresolution1makethemihfunctionblock,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۫W6W21cin W WWWWWWmay 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 B? ubcA1. 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.mRejectedv#See discussion of 06-0611, issue 31wDeferred 2006/07/20 2006/04/24 vEQiaobingFXieGMember 2006/05/14E8ed"Jdcjust+W:W;W<W=W>WےW܂WܥWܷWWWW݇WݔWݔWݔWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmissingandܨ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 ^technicalW W!W"W$W%W&W'W(W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_WaWbWcWdWeWfWgWVreplacefacilitieswithamorecleartermUVreplacefigure21withsection2of21-06-0460-02-0000-bschVcefigure23commonmihfframeformatwithfigure23miVreplacefurtherdeliverwithforwardڻVreplaceinterfaceswithaccesstechnologieskVreplacelinkcommandindicationwithlinkcommandrequestٰVreplacelinkcommandoriginatewithlinkcommandsoriginateٯVreplacelinkgoingdownwithlinkgoingdownVreplacelistofnetworkslinktypeswithlistofnetworktypVreplacemaintenancewithabettertermwV~bipWW\WWݍWW1W4Wiprenewalindicatorbooleann/a0changerequired4Vipv4\WޏWޏ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[Wj2EEleanorFHepworthGMember^ Editorial_53`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. 4d425g2278 2006/05/17 2006/04/28EEleanorFHepworthGMember^ Editorial_53sitioning 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. 4d425g2278 2006/05/14 2006/04/28EEleanorFHepworthGMember^ Editorial_5321 to try and specify an exhaustive list of all possible location determination schemes. 4d425g2278 2006/05/14 2006/04/28EEleanorFHepworthGMember^ Editorial_53݉E YoshihiroFOhbaGMember^ Editorial_47`30a6.3.2bFix it.c0Space is needed between 802.21 and specificationd393g2424 2006/07/20 2006/04/28݊E YoshihiroFOhbaGMember^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 14rialxIcsolution#WWsolutions۶WmWsomeiWۂWWiW܄WܯWWWWW݅WW'W,WjW?WsomeindicationdatasuchaslinkdetectedVsomehow݅WsomewhereWsophisticatedWWsortWWsoundsWsourceۍW۶WWsourceidentifiersourcesZWspaceWW-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ܾWWWWWEWbspec'WDWspecific'W)WJW_WiWWۉWWWW#W$WaWiWܹWܼWܾWܿWWWWW0W݃WWW,W2WށWރW;WspecificallyPWspecificationWYWܟWWWWWWWWW7W8WiWކWspecificationshouldbeaddedevenifthisisjustanxreftVVWކ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 WWstaticWWstationWY pbA@[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.d39g2341 2006/07/20qEKenichiFTaniuchi^ 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. g5NbchangeifapplicablethenewsapsshallberecommendedasamVchangeinmostcasestoinsomecasesVchangeincludetorequire>Vchangeinsecuretonon-secure<VchangeiscommunicatingtocommunicatesisresidingtoresidVchangeittowillresultݑVchangeittoxmlݚVchangelinkeventderegistertoacommandHVchangelinkeventregistertoacommandGVchangemakestomakecVdVchangemiheventderegistertoacommandFVchangemiheventregistertoacommandEVchangemihlinksapinline46tosaywhichisatechnologyVchangemihfnetworkmihnetworkAVchangenametolinkconfigureparametervalueasdefinedin܂VchangenetworkmaybeabletoindicatetothemobilenodetoOVchangenetwork-sideendpointofalinkthattonetwork-side+Vndpointofalinkthattonetwork-side+V+Venetwork-sideendpointofalinkthattonetwork-side+V+Vstandards?VWWWWXW6"ceasily@elements@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/bwhatWLWWܢWWWCW݂WWwhenFWGWLWOWVWdWkWnWېW۸WWWWNW\W^WܕWXWkWWWWWW#W$W}WހWނWޕWޖW3W5Wwhen802.16macreceivesneighboradvertisementmobnbr-advNVwhenprovisionedthemnVwhenthemobilenodeinitiateshandoverwhichmaybeinforme#VW5W5W5W5W5W5W5W5W5W5W5W5W5WcWpWܶ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<^technicalݪWݫWݬWݮWݯWݰWݱWݳWݴWݵWݶWݷWݺWݻWݼWݽWݾWWWWWWWWWWWWWWWWWWW*bmihreferencemodelforaccessnetworkstechnologies$Vmihreportinfoqueryresponse|VވVmih-3gDWmih-3glinksapshouldinterfacewithl3functionofthecdmDVmih-enabled!Wmihbasic~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/14xcAFThe wording is loose and largely repeating what has been said earlier.F@A  33d718g2333 2006/07/20 2006/04/24yEQiaobingFXieGMember^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  33d739g2334vbased on request from commenterwRejected 2006/07/20 2006/04/24zEQiaobingFXieGMember^Technical, Binding_119`57a8.4.1.4bKRemove "RDF_DATA", "RDF_SCHEMA_URL", and "RDF_SCHEMA" from the value field.cA  33d704g2332 2006/05/14 2006/04/24xEQiaobingFXieGMemberP/IP or TCP/IP as transport. More general, the value the figure itself adds to the spec is very limited. @A  33d704g2332 2006/05/14 2006/04/24xEQiaobingFXieGMemberq|Nvby 872w Superceded 2006/07/20 2006/04/28 Figure 30cA- 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? d873g2399 2006/07/20 2006/04/28 Figure 30binding 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/07/20 2006/04/28 Figure 30P get Link Tear Down or Handover complete indications before it is disassociated? d873g2399 2006/07/20 2006/04/28 Figure 303.19/28..Ybstation'siWއWstatusUWRWVWXW\WeWW܀W܄W܇WpWWWޔWstdpWstep_WstepsWstill9WstopWWWWXWstoredUWނWstrategyWstrengthFWGWHWIWJWۉWYW݊Wstretchۿ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އWd793 2006/07/20ESanjeevFAthalyeGMember^ Editorial_124`43a8.4.2.11b"status"cSpellingd798 2006/07/20ESanjeevFAthalyeGMember^ Editorial_126`15a8.4.2.17b "handover"cSpellingd802 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_126`33-34a8.4.2.18bFill in with reason codescMissing value range and codesd805vby comment 803w Superceded 2006/07/20njeevFAthalyeGMember^ Editorial_137`5a8.5.3.18bRemove "basically"cSuperfluous wordd852 2006/07/20ESanjeevFAthalyeGMember^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".d859 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_140`140a Annex A-1.W bqosWWnWܾW݊WW1Wqualifying_WqualityJWRWTW<Wqueries܁WWquery"W.WAWiWjWkWlWmWnWuW{W}WۂWېWWWdW|WܗWܙWܻWܿWW!W[WqW}WWހWށWނWރWބWޅW0Wquery-20041012qWquery-20041012httpwwww3org/tr/rdf-sparql-quqVqueryingWqueryresourcelistۂۋW܎W!WquerytypeޅWquickVWXWquickly'WquiteܪWrܯWܳWޔWr0087&Wr1WWr1/r2/r3Wr2Wr3Wr4WraWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWredrawing۽WreevaluateRWreference$W۬W۴WWWreferencecouldbemadetostaticschemaeintheisqueryV ނ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@WsWwW۬WWWWWW7WqWܑWܔWܵWWWWWWKWyWzWWWW W+WWWvWޗW2W7W8W:WfillWfillinwithreasoncodesVfilterbWfinds݊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ۉWframesrWbaddrefertotable26inannex4inthecommentsfieldDVEVaddreferenceVaddrepresentationVaddsection6.1from21-06-0611-00-0000-mprotocoldocVaddsentenceto3.2representationtoreflectthisVaddsinrinformationelementVaddsupportedisquerytypeasspecifiedinmihcapabilitydiscݥVaddsupportedisquerytypetotheparameterlistbVܻVaddtheammendmentsassuggestedin21-06-606-00-0000locinܘVaddtheexampleassuggestedin21-06-606-00-0000locinfooܙVaddthefollowingintheannexa4atthebeginningܚVaddthefollowingparagrpahinsteadVaddthefollowingtableRVaddthefollowingtext݊Vaddthefollowingtextinsection8.5VaddthemissingparameteradddescriptionforoldlinkidentifVaddthem݋Vaddtotable6\VaddtothesentenceorfromaninternallymaintainedmiisdaVaddedAWZW]WWWW}WWWW`WfWܺWWEParkFSoohongGMember^Technical, Binding_62`7a 6.3.4.3.6cJPlease refer to the #21-06-0602-00-0000_PoA_Capability_Prefix_Availabilityd476g2244wAccepted 2006/07/20 2006/04/207 Member^Technical, Binding_62`7a 6.3.4.3.6cJPlease refer to the #21-06-0602-00-0000_PoA_Capability_Prefix_Availabilityd476g2244wAccepted 2006/07/18 2006/04/207 and this command does not exist anywhere else in the document.d604g2268 2006/05/14EParkFSoohongGMember^Technical, Binding_62`16a6.3.2cCPlease refer to the #21-06-0601-00-0000_PoA_IPAddress_Configurationd480g2243 2006/05/14 2006/04/207but cannot be found in Table 4 or 5 on page 41 (MIH or Link Commands)d612g2264 2006/05/14E Ulises OlveraGMember^Technical, Binding_113`29a8.3.2bShould define the values for these IDs in the Annex A-4 for example with the other available values or directly where mentionedVlYbasW W#WAWFWGWJWNWOWQWVWWWXWZW]W_WiWsWuWۂWۃWۄWۉWېWۖWۧW۫W۰W۶WWWWWWWWWWW+W6W7W;WCWGWYW[W\WhW܂WܕWܗWܘWܙWܤWܩWܬWܸWܽWܾWWWWWW&W)W0W=WPW_WlW݂WݥWWWWWWWW-W1W3W4W5WCWDWKWLWMWVWZWnWޅWސWޑWޓW3W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&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ܫ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>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.d147g3251.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>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.d147g32517jcwhatFWGWHWIWJWeWhWiWpWvWxWۈWەW۳W۽WWWRWYWcWeWܢWܯWܳWܿWWWWWWWWWWWWWWWWW!W\W݂W݊W*WKWfWޏWwhatisa3gpp2radiodoyoumeanusinga3gpp2interfaceVwhatisanadministrativelinkeventtypeithasnotbeendeVwhatisthedeifnitionofsecureandinsecureportisthistVwhatistheunlabeledtablein7.4.7.1.4forhVwhen-WiWۈWۉW۩WW9WOW^WeWܻWܽWWWW%WXW݂WW#W$WJWޖW5WwhenprovisionedthemnVwhenretrievingiestheclientneedstospecifyit'sownlocܽVwhenthemobilenodeinitiateshandoverwhichmaybeinforme#V#V5W5W5W5W5W5W5W5W5W5W5W5W5WWWEWFWGWHWwhereverܥ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ۉۋیێjeff89jin01234567junjunxiangۂWۃWۄWۇWۈWkeigo۔kenichipqrstuvwxyz{|}~ހށނރބޅކއވމފދތލގޏސޑޒޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓles7777777777777777777777777777777777777777777777777Wecparagraph`WpWvWݏW'Wparagraph/sentence۞WparagraphsqWparallelWparamater WparameterFWGWHWIWJWۂWۃWۄWۆWۉWېWWMWYW`WbWdWkW{W܂W܎WܽWWWoW|WݽW[WaWbWcWޖW<WparametermissingV[Vparameters{WۄWۅW*WYW_W`WgWjW~W܂WܰWW0W|WݏWݪWݫWWW:WޖW3W5WparametertypeFWGWHWIWparenthetical]Wparethetical\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ہWJWWWWunfamiliarRWH-EQiaobingFXieGMember^Technical, Binding_37`29a6.1.5.2bral 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. @Az  c  TTl  )c{    TT  TTzcACurrent text needs improvement.@A  33d252g2254 2006/06/18 2006/04/24-EQiaobingFXieGMember^Technical, Binding_37`29a6.1.5.2bgFXieGMember^Technical, Binding_37`29a6.1.5.2b1g2252 2006/05/14 2006/04/24+EQiaobingFXieGMember^ Editorial_32`52a5.8.3b Remove 5.8.3.cquired.Mc$8 ~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 2006/07/20EKenichiFTaniuchi^Technical, Binding_119`48a8.4.1.4b9ab ", Success)nichiC$/bcopiedUWYWcopy&W\Wcopytablefromsection8.5.1.2to8.5.1.1\VcoreAW$WܹW:Wcore802.21hedaerspecificiesܹVcore802.21specificiesܹVcorrectWWyWzWQWcorrectrregisterVcorrectnessWcorrespondingjWmWTWUWVWWWXWܷWܿW݊WcostHWWcould,WHWIWUWWWWܼWWWIWSWWcountryHWcoverVWcoveredWcreate=WcreatedۚWcreationۚWcriterion-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-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ݿVinsertthesuppotedisquerytypelpage83line10VinsertedUWYWinstanceZW]WWܞWW8Winstances*WWinstantWinstantiationW1W3W4W5WinsteadۗWWWWWWW"W/WZW݃WWinsteadofprefixconsidertheuseofnetworkmaskZVinstructs݊WinsufficientVWinsufficientinformationofintenttosuggestanychangeVVsuggestanychangeVVVVnsufficientinformationofintenttosuggestanychangeVVVVtosuggestanychangeVVVVVVVVVVVVVVVVVVkWlWmWnWpWsWuWvWwWxWۂWۇWېW۝W۶W۹WWWWWWWWW5ܞ 2006/07/20ܟ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>cAService 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 2006/07/20ܠEVivekFGuptaGMember^ Editorial_11`1a4b Delete MIHOc instance of definiton of MNcMultiple definitions of MNd66g3245@cneeds W,WAWEWFWGWHWIWJWsWtWۉWWW-W;WYWkWܥWܽWWWWWݏWݒWWWWOWPWހWށWނWރW8WnegotiateduWnegotiation\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/W9EGregFDaleyGMember^ Editorial_10`18a4b Remove the references to ASN.1cRemove references to ASN.1 - Starting Page#: p10, p59 - Starting Line#: p10(18) p59(51) - Fig/Table# (if applicable): - Section#: 4, 6.3.8 d85g2227 2006/07/20EGregFDaleyGMember^Technical, Non-binding_118`1a8.4b\ Explicitly reserve 128 (General) and 127 (Other) for future expansion. cANo space for expansion of MIH TLV Encodings, There are 256 possible encodings for general and other TLV encodings, it is conceivable that these may be exhausted if different classes of data are added. - Starting Page#: 118 - Starting Line#: 1 - Fig/Table# (if applicable): Table 20/Table 21 - Section#: 8.4 (8.4.1-8.4.2) d760g2228vMThis kind of partitioning does not help at this stage. Needs more discussion.wRejected 2006/07/2020!EEQiaobingFXieGMember^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.d500g2281wRejectedred 2006/07/19 2006/04/24 EEQiaobingFXieGMember^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.d500g2281wRejected 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.d500g2281wRejectedwRejected݃byc802.21*W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WEWۀWۅW۩WWWW$WCWDWEWHWRWTWUWVWWWXWYWmWnWܛWܢWܣWܧWܪWܸWWWWWW2W:W݂W݅W݉WWWXWYWiWjW>WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhk vAX "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 2006/07/20 2006/04/28E 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/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_130`65a 8.5.2.5-12bBAdopt suggested change [4] in 21-06-0522-04-Session_Identifier.doc match the new >8dRܫ 2006/07/20ܬ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-Modified147g3251!EFarrokhFKhatibiGMember^ Editorial_3`53a1.3b/Replace "interfaces" with "access technologies"c;It is not clear what "supporting multiple interfaces" meansd19 2006/07/20"EFarrokhFKhatibiGMember^ Editorial_3`61a1.3b$Use "at various" instead of "other".cImproved phrasingd24 2006/07/20#EFarrokhFKhatibiGMember^ Editorial_4`2a1.3bsee item abovecsee item aboved27 2006/07/20$EFarrokhFKhatibiGMember^ Editorial_4`3a2itorial_3`53a1.3b/Replace "interfaces" with "access technologies"c;It is not clear what "supporting multiple interfaces" meansd19 2006/05/14"EFarrokhFKhatibiGMember^ Editorial_3`61a1.3b$Use "at various" instead of "other".cImproved phrasingd24 2006/05/14#EFarrokhFKhatibiGMember^ Editorial_4`2a1.3bsee item abovecsee item aboved27 2006/05/14$EFarrokhFKhatibiGMember^ Editorial_4`3a2\Ãd] 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ܬWWWWobtainingAWkWnW}Wobtains)WocalޔWoccupiedݗ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`WcWdWhWiWjWkWlWmWqWsWvWwWGbtechspecificparameteFWGWtelecommunicationۖWWtelecommunicationspWtellۇWtermۢWW-WUWterminalۘWۜWterminatedHWterminology۽WWWtermsWWܪWWWWWWWWWWWWWWWWWvWxWWthatW 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[\]^_`abcdefghijkstewartWXYZtakashiۑےۓulisesWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWVVVVVVVVVVvivekܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃwolfgangܑܒܓܔܕܖܗܘܙܚyanۇWۈWyanpengjunxiangguoۇVۈVyoshihiro݆݈݅݇݉݊݋݌ݍݎݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟݠݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σyuanۅۆ$wEKenichiFTaniuchiGMember^ Editorial_155`28aAnnex CbA77@A> 33#  $ 33>c3typo in "Wsaps'WDWpWWWW2WWWsatelliteۖWWsaved&WsayWWWWWsaytheabovementionedframestructureVsaying۳WWW)WscanۆWWNWmWscancommandmWscanrequestinfomWscenarioݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓWݓ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݌W=(+btomihfnetworkmihmobilenodeAVonmoduletomihfnetworkmihmobilenodeAVAVnmodule.VtomihfnetworkmihmobilenodeAVAV_WٕWٮWWW WWWOWڕWWWWfillٝWfillinwithreasoncodesٝVfiner6Wfirst6W]WٽWWW0WzWڗWWWfixWWSWfixtheinconsistencyVVfixtypotowardtheendoflineallSVfixedWWflexibility-Wflexible-WflowڕWWflowssWWflushAWfollowed0WfollowingWHW٪WٴWٿWWWWWWWWWWWWWWWfollows W6WمWٺWWWsWzWڶWforW WWWWW+W-W0W2W3W6W9W;W<W=W>W?W@WAWBWCWFWPW`WfWkWقWُWِW٤W٨WٮWٷWWWWoۃE Guo JunxiangGOther^Technical, Non-binding_89`26a*7.4.6.1.2,7.4.10.1.2,7.4.12.1.2,7.4.12.2.2bbAccept the changes as described in 21-06-0628-00-0000-Amendment about OldLinkAction parameter.doc.ccording 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. d638g2325 2006/07/19 2006/04/17€ATable@A  33ۃE Guo JunxiangGOther^Technical, Non-binding_89`26a*7.4.6.1.2,7.4.10.1.2,7.4.12.1.2,7.4.12.2.2bbAccept the changes as described in 21-06-0628-00-0000-Amendment about OldLinkAction parameter.doc.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  33d899g2343iYoshihiro Ohbak@A  33d899g2343iYoshihiro Ohbakighly 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  33d899g2343iYoshihiro Ohbakom the value field.}@A> 33   33f 33>* \bD 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 primitivEe 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 RanVrENada, 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 2006/07/20sENada, 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.d729g2304".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 2006/07/20/EDavid FFamolari^ Editorial_8`42a3bWChange the definition to: " N-layer - the N-th layer of the layered protocol stack. "ns before it is disassociated? d872g2399 2006/05/14 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.d58g2403 2006/05/14/EDavid FFamolari^ Editorial_8`42a3bWChange the definition to: " N-layer - the N-th layer of the layered protocol stack. "nt.4@A  33d739FIvnotallissueshaveremediesassignedonissuelist-VnotclearwhatsentenceisbeingtalkedabouthereVnotconsideredrelevanttoschedulednetworksegmentssuchaVnotsureifthisisreallyrequiredۈVnoteWܗWWnothingށWnotificationQWRWSWTW\WnotionfWe 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.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: Q+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 2006/07/20 that "cammard54 2006/05/14*EFarrokhFKhatibiGMember^ Editorial_8`18a3b(Remove "MIH Users are" in the beginning.c0Consistency with similar nearby section clauses.d57 2006/05/14+EFarrokhFKhatibiGMember^Technical, Non-binding_8`57a3b_Change "Network-side endpoint of a link that " to "Network-side endpoint of an L2 link that "cinning.c0Consistency with similar nearby section clauses.d57 2006/05/14+EFarrokhFKhatibiGMember^Technical, Non-binding_8`57a3b_Change "Network-side endpoint of a link that " to "Network-side endpoint of an L2 link that "c(EFarrokhtorial~bthemselves-WWthenFWGWTWZW]W_WbWeWW7WܴWWSW݊WݎWݗWthereAWUWZW]WxWTWUWVWWWXWYWcWsWW WCW:WtherearetwopossibleremediesforthisYVtherearetwopotentialremediessVtherewillbenodirectcommunicationbetweenthe3gpp2phy VthereafteruWWtherefore,WthereinۚWthese WpWۻWW#W7WܴWܾWWWWW(WWWW-WކWthesecapabilitiesneedtobespecifiedclearlyfordifferenܾVtheserecommendationsshouldbehandledbyspecificieee802VWWWWWWWWWWWWWWWWWWWWWW802VtheyWW-WAWW7WW݂W݃WWWޜWޝWޫW޿WWWWW W WW.W<W=WKW_W4ۖ@bۚ0ۜ@۠_ۦ۪v'ۭ@ۯF۳c۴cM۵kA۶bA۸b@۹@۽cAV۾@cAۿ@@ c@k@b@bkBhcd@b@@b7@d]@@sb@c @bbAXbA9w@)cA@;bBcAkBD(FbzjkB9@q@bJ@6` bbJcAkgbA9gfcAPg+bB/cAig0bcAgb EkbIccAgbEg] bgk#bBg&c*c,cTbreplaceۋWۛW۟WۡWۢWWWWW WW#W5W6W8W9W:W<W=W>W?WCWFGHWJWKWLWMWNWOWTWUWVWWWXWZW]W_WaWcWfWilWoWpWrWtWvWwWxWyWzW{W}W~WW܀W܃W܄W܆W܇W܈W܊W܋W܌WܡWܣWܥWܧWܮWW!W-WBWqWsWW݃W݄WݼWWWWWWW W W W/W>WNW]WoWvWކWއW6W=W@Wreplace1.2with1.3inthenocolumn>Vreplace1.3with1.4inthenocolumn?Vreplace3127reservedwith3127reserved}Vreplace3gppwith3gpp2sVreplaceadditionalidentifiersarepresentthathelptoanaltVswithaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1V9ZEStewartFSkomraGMember^Technical, Binding_19a5.3.2b.Show Information Repository at the MN as well.cThe Information repository can be present locally at the Mobile Node as well. Update Figure 3 to show the Information server to be present at the MN as well.d143g3213vPlease provide updated figurewRejected 2006/07/2010 [ESrinivasF 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 2006/07/20 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)d821g2238wAccepted 2006/07/20 2006/04/26/2110 0 reason why the uniqueness is not needed should be described.ikwEFarrokhFKhatibiGMember^ Editorial_8`21a3b,Remove or rename one of the two definitions.c+Duplication of the "Mobile Node" definitiond59g3207 2006/07/20xEFarrokhFKhatibiGMember^Technical, Non-binding_33`33a6.1.1bRequires clarificatiocIf 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?d254g3208 2006/07/20yEEunahFKimGMember^Technical, Non-binding_40`40a6.2.4bn they can all be igoned?d254g3208 2006/05/14yEEunahFKimGMemberostly 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?d254g3208 2006/05/14yEEunahFKimGMembered?d254g3208 2006/05/14yEEunahFKimGMember48`22aAnnex B1se HbC elements. Unit 1 The unit of the cost 0: second 1: minute D 2: hours 3: day 4: month 5: year Value 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.d561g2349LcclientܶWܻWܽWAWBWCWclient'sxWclientsWclose.W3WܝWclphrasing?Wclubbed݅Wcn۽Wco-locatedWޕWcoaޕWcodeۅW=WeW{WތWcodesWWcoherent3WWcoincide.W3WܝWcollectܤWݐWcollectsܡWcolummގWcolumnWWWWWށWރWcolumnintablesection8.4.2.24needstobemodifiedރVcombinationWcombineWcombinedsWWcome9We9W9WnationWcombineWcombinedsWWcome9W9WK`Ä*2UÄ23ЃnÄ29ۦÄ2R[Ä37۳Ä45ۚÄ4eWYÄ9CÄDEÄ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ЃG.F!EQiaobingFXieGMember^Technical, Binding_18`13a5.3.2bH 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. d106g2240 2006/06/18 2006/04/24!EQiaobingFXieGMember^Technical, Binding_18`13a5.3.2b{\]^_Bgjrelatedtomostofyoshihiro'scommentonlinkidsVVrelationships,WremedyWWgWremove 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ݴVshouldthemihusersknowaboutthesessionidhVAbitselfSWuW݊Witu-tvWityAWjWjissuedVjhallHWjustWWZW]WWܧWWkWktowardsVkeep;WkeptWkeyܨWW7Wkind݃Wknow6WknowledgeWknown6W܋WܷWlWޔWltowardsVl-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۶WgCcbeforeYW_WbWeWېW-WܺWWݏWW W"WbeforeauthenticatingwiththepoathemihfunctioninthemܺVbehaviorZWiWkW@WbehaviourWbeingWWbelong_WaWbelongs"W/W0W1W2W3W4W5W6W7W8W9WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW2WJWSWiW݉WW WW4W5W7W>WTWޠWޣWޤWޥWWWWWWWWWW|ceasilyjWkWmWnWoWzW{W|W}W~WہW۾WedgeW:Weffect WWeffectiveݏWeffects|Wefficiency WefficientWWeitherۂW.W3W[WܝWܬWܺWW3W;W"W$W%WޖWelaboratedPWelementXW=WHW܄WܕWWW~WW/W1WntsKWZW]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ہWbreplacesection5.5withcontribution21-06-0620-00-0000-nsVreplacesection5.5.2withcontribution21-06-0625-00-0000-n Vreplacesection5.5.3withcontribution21-06-0627-00-0000-n Vreplaceshalldefinewithdefines۟VreplacespecifictiewithspecifictoieaVreplacestatusofhnadoverrequestwithstatusofhandoverr܀Vreplacethe802.21informationelementsmaybeassignedidenCVreplacethealinkeventrollbackwithalinkeventrollback܃VrregisterٔWWrttQWTWrtx6WrulesZW[W^W_WcWWrxlevncell2W3W4W5WsWW;W<W=W>W?W@WAWBWCWpWڍWWWs0001pWs0004-dTWs0024pWs0024-aqWs0063-aqWsame+W-WڔWWWWsamechangeisneededatthetableofcontentsandp72/l62VsapWW/W0WWWuWWWڎWsapsW0WiWsatelliteIWeWۈ@cAۉ@bA{CEtۊbAC cAۋbA$vpی@ۍ@ېbACdA|cC!ۑ@$ےk۔vA ە@vA0vA0@kG۔@@۔@cCۑ@ی@ی@ی@ی@ۋbAی@ی@ی@ی@ی@ی@ۋbAی@ی@ی@ی@ی@Epۈ@{cAۉbACEppEpCEpCEpbACEp{cA{cA{{A{A{{{cA{cAۅcAۅcAۅcAۄcAcAcA:vspecifythesevaluessecuriyandqosinthecontextofaccesܾVspecifyingJWsprecifyގWsprecifyabortreasonfromsection7.4.10.2.2ގVstageW 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. 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 Chengj33d252,EQiaobingFXieGMember^Technical (was Editorial)_33`14a6.1.1bAIn 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. @Az  c  TTl  )c{    TT  TTzcACurrent text needs improvement.@A  33state change in the environment or because of some management function on part of the network. @Az  c  TTl  )c{    TT  TTzcACurrent text needs improvement.@A  33~Gbinformation#W:W;W=W?WAWXWZW]W_WbWcWdWeWfWiWlWpWuWxWۘW۳W۶W۷W۸WWWWWWWWWWW#W5W=WCWHWNWdWmWsWܕWܗWܟWܡWܢWܤWܬWܶWܻWWWWWWWWW,W;WPWUWVWXWYWzW|W}W݊WݖWݘWWWWWWWWWWW"W#W$W%W'WZWjWpW~WބWޅWއW9W:W;WinformationusingtlvswithawelldefinedbehaviourpatternVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVabled!Wmobile,Wmobility,Wmodel$Wmove!Wmulti-technology!W%Tbbe9W:WbeexchangedinordertoachieveisserviceVbeareXWW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9Wƒkenichi taniuchiƒkenichi Xtaniuchiƒkenichi Ztaniuchiƒtaniuchi&ƒkenichi taniuchiƒpark soohongƒsoohongƒpark soohong DTDT_DT`DTE Ulises Olvera 33  33  335  33< 33ft of scope for MIHF. Handover resource management belongs to the upper layer mobility management application/protocol itself.@A  33 s u xy z 9!p"!#" $"0%"P&"`'"p(")"*#0/#@+#P,#p-#.$00$P1$`2$p3$4%05%P6%`7%8€‚Iپ{Z€‚7ٿ{a€‚a{e€  ‚){g€ ‚9{i€ ‚B‚f{u€ ‚!{s€ ‚'‚d{y€‚3{x€‚a{z€‚2‚h{€‚B{€‚%‚J{€‚f{€‚b{€‚$cinter-technology?W@WܴWinteract"W$W7WinteractionWinteractions8Winterafces۴WinterchangeWinterchangebelowsectionsVinterchangedWinterestܐWEWFWGWHWIWinterfaceۉW۽W WWW:WcWeWkWWWWDWW4W5W7WiWޖW5WinterfacesۉW۴WcWeWWW!W0WBWinterfacingWinterferfacesWintermediaݐWintermediateWinternationally>WinternetW:WUWYWinternet-draftݕWݖWݘWinteroperabilityCWHWRWTWUWVWWWXWYWܛWWinteroperablemWinteroperateۑWےWےWے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ہWWfCbdetailsWۅWۆWۇWۈWW~W݃WmWWWWWWWWSWWRWSWTWUWVWWWXWݛ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߱WcExplain that the remote flow of Events and Commands for Figure 14 and 17 on page 36 (section 6.1.3) and page 40 (6.2.3) respectively are logical flowsd265g2259 2006/07/2014 & 18E Ulises Olvera^Technical, Binding_37`27a6.1.5.2bShould reword this and say that during registration the Users specify the list of events for which they wish to receive notifications form the MIH FunctioncConsider the line that says " After registration, the MIH Users may specify a list of events for which they wish to receive notifications from the MIH Function" Isn't this already done during the process of registration?d274g2260 2006/07/20E 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.2cl flow when acually it is the logical flow.E Ulises OlveraR7EPeretzFFeder^Technical, Non-binding_41`1Include 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 2006/05/14 2006/04/28EPeretzFFeder^Technical, Non-binding_41`1 is sent by current MIHF entity to target MIHF entity to allow for resource query and handover preparation. Change the term cutrrentd305g2249 2006/05/14 2006/04/28EPeretzFFeder^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 2006/05/14 2006/04/28EPeretzFFeder^Technical, Non-binding_41`12244 2006/05/142cresource"WjWkWmWnWoWzW{W|W}W~WہWW0W܇WW!WwWresources"W۸WW WPWrespectingWrespective6WlWrespectivelyyWWrespond܆WresponeWWresponseeW}WۂWۃWۄWۆWۈWۊWۍWېW9WOW܂W܄WܕWܗWWݥWWW%W+W>WCWiWjWrWyWzW{WކWޗW=W?WresponsesܕWܗWWresponsibleWrestatingQWrestatingtheobviousQVrestricted۪WܕWrestrictive۶WrestructureݐWrestructurethefollowingsentenceݐVresubmit8Wresubmitofcomment138fromthedenvermeeting8VresultۄWېWQWlW܆W0W>WresultcodeۄW>W>W>W>W>W>W>W>W>WHWsaying/WsaysWrW۾W%W&W.WZWscanۆWWNWscanschedulingNWscenarios\WۈW|bmustWWW'WDWZW]W_WRWTWUWVWWWXWsWOWhWނWބWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWprotocolstack/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_WtW1r(b1tlvjVmV1transportoptionsܯV1wirelessieee802.11a/b/g^V1-21]W1.0~W1.1=WtW1.1typeielistlistofneighboringforexampleradiusnas-tV1.2=W>WW1.3>W?WW1.4?W1.6ܛW10kWܒWݶW1006W1016W11WpW1127W12=W125hW127|WW}WݗW128|WWXW13:W>W140W;W7W܄WܹWW/WݛWlW1W14bitidܹV15ۉWW=WݛWlW16EWWWW16EWWWWWWWWWWWWWWWWWWWWWWWWWWWkWmWnWuW{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[Icbe7W:W<W>W?WCWKWNWOWPWQWconsistency.@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>WthanWWܗWܩWܴWWWW WDWXWWWܗWܩWܴ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)FercE 2006/07/20 2006/04/24 FEQiaobingFXieGMember^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 Entry 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/05/2247 bprovide W?W_WWWWWWWW*WhWܴWWW W W W WWWWWSWXW\WmWprovideaconcreteextensiblesyntaxforthemihfid VVprovideaconcretesyntaxforthesessionidVprovideaccurateinformationregardingencodingwhenvaluefXVprovideanalgorithmforduplicatepacketdetectionorusea VprovidebetterdefinitionforchannelidVprovidecontextwithanintroductiontotherequest/responseV\VprovideextensibilityrulesforallocationofnewtypenumbeVprovideformatandrulesforinclusionandinterpretationofVprovidemorespecificsonwhatenoughinformationmeansistVprovideoperatoridentityattributetoeachinstanceofwlanVproviderttestimationalgorithmsorrelyontheunderlyingV V V V V V V V V V V V V V V Vremovefigure19@VWh&@vdeletethetextVdeletethewordmobility4Vdeleted۷WWWWdeliver"Wdelivered"WdemonHWdescribed0WdescribingݳWdescriptionWWWdesignatedlWdesiredܽWdestinationݴWWdetailWdetailsܿWZWݽWdetectedۆWdetermineܽWdevices;WdiagramۋWdiagrmsiWdifferences*WWdifferentQWTWۋW۫WW@W0Wdifferentaccessnetworkssupporthorizontalhandovermechan۫Vdirectly"WdiscoverSW"Wdiscovered{Wdiscovering;WdiscoveryۊW;WݓWdiscussionuWW WܗWݓW0Wdiscussionthatsomeie'sinthesubmissionarenotinthetܗVdiscussionsܛWݜWdisparate*Wdistinct WdistinctionfWdividedܗW3b;Until additional text is provided, it should be deleted. ----- | QueryResourceList | Boolean | N/A | R|UbconceptW:WconceptsW2Wconceptual5WܟWconcrete WWWconditionsWWconductedۉWconfidenceQW\W:Wconfidencelevel\WconfigurableޖW5WconfigurationWjW܄WOWW8WconfigureۄWۉW\WkWlW܂W܄WW{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۽WWWWWZWconsideraddinguniqueeventidentiferforlinkdetectedVWW8E&cdocumentWۑWۡW۬WPW[W\WWWWW W%W2WWW.W>W<Wdoes(W)WeWfWwWۈW۔WەWWWWW$W)W-WAWBWFWYWZWkWnW{W܁WWWWWWWWWWWWWWWW%W2WCWaWxW݂W݃WWWWWW3WUW^WdWfWiW7WdoeseverydevicehavetosupporteveryquerytypehowisthVVVVVVVVVVVVVVVVVVVVVcWWdynamicallyWe#W_WaWiWۈW۪WWWWWWZWwWWWWWWWWWe-core۽We-utra۽WeachuWۄWW@WCWzW{WܸWearlierpWvWxWearlyܫWeWhWjWkWmWnWoWpWuWWNbtheymusteitherbemergedintooneoroneofthemberemoveVVVVVVVVVVVVVVVVWAWHWIWLWMWOWPWQWRWSWTWUWVWWWcWdWiWkWnWxWۂ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޿WWWWWWWWWWWWWWWWWWWWj= -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  33d277g2255 2006/07/20 2006/04/24.EQiaobingFXieGMember^Technical, Binding_37`36a6.1.5.2bTTzcACurrent text needs improvement.@A  33d252ccontentsWܼWWWWWWWWWܯ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ݏWWKWQWTWfWhWcounterpartWcountriesSWWWJw=vofW WWW0W2W3W:WDW_W{W݃W݄WݓWݜWݴWWWWW"W0W4W5W7WJWSWfWoWޏWDWofflineܛWokWold"WonQWTWZWjWkWmWyWzW|W}W~WہWۅWۆWred_VonceܗWone(W{WfWoneoctetcanactuallyhold255values(VonlyBWZWgWWWܗWݓWfWopenedWoperation0Woperational{Woperator@WWWoperators[WW@WܗWWopposedܾWoptionaldWoptionsWWorۅWۛW۳WWܗWW3W{W݊WݓWݜWSWfWorderingۋWorganizeZWorganizedZWoriginalZW7WotherRWۓW۳WWqWWWWW2W;W݊WSWoutەWWWWoverTWpacketۅWpage۳WWHWܬW2Wpage18sentenceonline22changesasfollows۳V-`bextraneousWfWfalinkteardownisusedtoreleaseresourcesVfa:WfacilitatevWܤWfacilitatesWfacilitiesۢW)WWfactWfailureUWVWXW\WܖWfallWfalureWfast۷WfeatureiWfieldyWzW{W}WۂWDWEWFWNWvWwW|WܒWXWݔWݕWݗWݘWݙWݵWWWނWfields~WfifthWfigܮWWfiguer15Wfiguer18W18WWfifthWfigܮWWfiguer15Wfiguer18WWWWWWWWW caddSWۆW۬WWW2W:WbW݄WWWWWWWW WW!WDWaddacommaafterhoweverandpartinthelinehoweverformVaddacommaaftermobilitybecausewithoutacommathesenteVeadybroadcastVaddtheinthefollowinglineinthissectionareprovidediVaddedۊ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ۂWۅWreasonsۅWܪWreassembledWreassemblyWreceiptWW WreceiveRWZWW>WreceivedOWPWQWRWSWTWUWVWWWۅWW>WJW5Wreceiver-WۈWۊWW W W WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWtgW WrefeernceܯWrefereW܏WܧWWWWWreferto802.21asieee802.21consistentlyinthedraftܧVreferenceW!W$W۬W۽WWWWWDWEWܪWܯWWWWW:WAWFW\W݂W݃WݕWݖWݘWWXWYWpWqWޛWޟWޢWWWW WWW bmProvide an algorithm for duplicate packet detection or use a transport which reliably eliminates duplicates. cThe rules state that 'in any case' the destination shall not process duplicate packets. However, if the packet arrives outside the time window defined, there is no mechanism to determine that a packet is a duplicate. d716g2297vsee issue 34. wDeferredy`use large Transaction ID value with assignment method guaranteeing uniqueness within the session 2006/07/20 2006/04/28 dnvoked at most once. c ed714g2296 2006/05/14 2006/04/28 EEleanorFHepworthGMember^Technical, Binding_113`15a8.3.1bmProvide an algorithm for duplicate packet detection or use a transport which reliably eliminates duplicates. orFHepworthGMember^Technical, Binding_113`15a8.3.1bmProvide an algorithm for duplicate packet detection or use a transport which reliably eliminates duplicates.  EEleanorFHepworthGMember^ Editorial_112`6a8.3cWprovidesIWWݏWWWW>WfWprovidingۆWWWprovisionܟWprovisioned݂WWproxiesWproximity.W3WܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝWܝW`1carchitecturaliWWarchitecture/W݂W WareWW%W/W0W5W?W@WNWZW]W_WaWqWۃWۈWیWەWۦW۬W۾WWWWWWWWWWWWW$W(W)W7W:W=WNWRWcWjWtW܏WܖWܗWܚWܪWܭWܯWܲWܴWܹWܿWWWWWWWWWWWWWWW W WWWWWWW0W1W2W:W\WfWxWzWW݊WݥWݸWWWWWWWWWWWWWWWWWW(W-W6W9W=W>WDWEWFWGWHWKWXWYWvWކWފWޕW2W^W^W^W^W^W^W^W^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+cevent-WNWSWېWWWWWWWRWTWUWVWWWXW\WcWeW܃WWJWaWݍWݛWWWW#W(W)WEWFWGWHWIWKWLWMWRWaWbWcWrWyWzW4W?W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4W4WTWctheexampleinbracketsinconfusingegbsorrncorggsniVtheexamplequeriesshouldbeinaseparateappendixandnotNVtheexytensibilityaspectofdifferentiesisnotveryclearܸVthefactthatthetidisinthefixedheadermeansthatinfVthefieldnumberofadditionalheaderidentifiersisnomoreܓVthefirstparagraphof6.3.5talksaboutgeneraluseofmiis`VthefirstparagraphrepeatswhathasalreadybeensufficientpVthefirsttwosentencesmeanthesamethingsIVthefollowingparagraphtalksaboutthestaticanddynamiciݏVthefollowingsubsectionsshouldbeaddedtosection5.6.1m1VtheformatofthecostinformationelementmustbedefinedbHVthehandoverdecisionmoduleisneverdefinednorused.VtheieeestandardshoulddefinethepacketformatV.VtheieeestandardshoulddefinethepacketformatVV.VtheieeestandardshoulddefinethepacketformatVVedbHVHVV vwAccepted-Modified 2006/07/20 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?) d732g2304vFno suggested remedy TID is significant only when there is a response.wRejected 2006/07/20 2006/04/28inding_114`8a8.3.2.3b(Define the scoping rules for the TID. ansactions are identified (if this is a requirement). d730g2302 2006/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Binding_114`8a8.3.2.3b(Define the scoping rules for the TID. ation). Registration messages are apparently only defined for particular event types. d725g2300 2006/05/14 2006/04/28EEleanorFHepworthGMember  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/07/20 2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_113`60a8.3.2.2b7Provide a concrete extensible syntax for the MIHF ID. cn or use a transport which reliably eliminates duplicates. orFHepworthGMember^Technical, Binding_113`15a8.3.1bmProvide an algorithm for duplicate packet detection or use a transport which reliably eliminates duplicates. P<%cnon-posۭWW2Wnon-trivialWnon-usWnone[WnorۇWW.WnormalWnormativeܪWW-WNWoW>WnormativelyܪWnorthboundEWFWGWHWnotW!W#W%W&W(W)W*W:W;W<W=W>WBWDWEWKWLWMWOWPWQWRWSWTWUWVWWWXW[W^W_WaWcWdWeWfWiWjWkWlWmWnWoWsWuWwWzW{W|W}W~WWہWۂWWۂWۂWWۂWۂWtl`‚eʃܲ5‚fEP[|̃Pa݁ UV‚g۲ܧQXvݗޏ‚h$zۇ۰W܋+;ZݺC‚idtۊ۶?Fܕ܃3mݙ+q‚jۜă tܘݤ‚q)_ݸnB‚ru@~̓"W:W?WplacedYWWWW:W Wplacement Wplaces݂W݅Wplane4W5Wplaying:W;W<W=W>Wplays݃Wplays݃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ݎVO2EJunFHiranoGMember^Technical, Binding_113`55a8.3.2.2bDefine it properly.cO"Session" is not defined anywhere. Thus Session ID does not make sense at all.d723g2211vby comment 719w Superceded 2006/07/20xample, if a new information element is defined, how is the receiver to determine what to do with unknown types (drop, ignore, reject message, etc.) d770g2311 2006/07/20 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.d723g2211vby comment 719w Superceded 2006/07/20 2006/07/20 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.d723g2211vby comment 719w Superceded 2006/07/201vby comment 719w Superceded 2006/07/20 rOEEleanorFHepworthGMember^ Editorial_118`5a8.4bcahnge to definite cTypo defiite d763g2308 2006/07/20 2006/04/28EEleanorFHepworthGMember^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 2006/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_118`28a8.4b cIt is not clear what is the difference between 'common' and 'other' encodings and where the boundary between the two number spaces lies. d769g2310v#no suggested remedy. Issue assignedwRejected 2006/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Binding_118`28a8.4b?Provide extensibility rules for allocation of new type numbers.ormation fields only byte aligned and not word aligned). ra8.3.2xݳ8.3.2.1 ݴT8.3.2.2ݵU8.3.2.3۔8.3.3ܑăՃ'8.3.3.1yܒܓݶݷփV8.3.3.2Ńhݸ8.3.3.3ܔ8.3.45=(8.4ijݹފ8.4.1ݺݻ8.4.1.1ދ8.4.1.2ތ8.4.1.4z8.4.1.8]^8.4.2.1k8.4.2.11ݼ8.4.2.13n8.4.2.16o8.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.2ۈ8.5.2ۉ8.5.2.1)8.5.2.108.5.2.118.5.2.12ۉۉۉۉۉۉ.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-WsWtWuWvWWWWm_ESrinivasF Sreemanthula^Technical, Binding_74`10a7.3.8.2bremove: 4:SIPc1SIP is not used as a mobility management protocold517g2242wAccepted 2006/07/20 2006/04/26 `ESrinivasF Sreemanthula^Technical, Binding_122`37a8.4.2.2bremove: 4:SIPc1SIP is not used as a mobility management protocold788g2245vASIP can be used for mobility management and so let's keep this...wRejected 2006/07/20 2006/04/26aESrinivasF Sreemanthula^Technical, Binding_130`46a8.5.2.5bHAdd another parameter "LinkType" LinkType | Media type of the link cu"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 2006/07/20 2006/04/26bESrinivasF Sreemanthula^Technical, Binding_131`2a8.5.2.6bCAdd another parameter "LinkType" LinkType | type of the link ;svby comment 719w Superceded 2006/07/20a8.3.2.2bDefine it properly.cO"Session" is not defined anywhere. Thus Session ID does not make sense at all.d723g2211 2006/07/20e 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.) d770g2311 2006/05/14 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.d723g2211 2006/05/14sage, etc.) d770g2311 2006/05/14 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.d723g2211 2006/05/14make sense at all.d723g2211 2006/05/14igned and not word aligned). rv  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.mRejectedvRefer to comment 102. wRejected9Adopt any clarifying text from comment 102 (Group Notes). 2006/07/20ependent"cG`ܛ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 2006/07/20ܜEVivekFGuptaGMember^Technical, Non-binding_7`1a3b"Add definition of handoff/handoverperability 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 2006/07/20ܜEVivekFGuptaGMember^Technical, Non-binding_7`1a3b"Add definition of handoff/handoveron elements from a MIH-IS server over TLV queries.d663N \ctheFWJWKWLWQWSWWWXWZW[WaWwWxWyWzW{W|W}W~WW݁W݂W݃W݄W݌WݍWݎWݏWݐWݔWݛWݥWݪWݫWݵWݸWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWW W!W"W#W$W%W&W'W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WBWDWEWFWGWHWIWJWKWNWOWPWQWSWWWXWYWYWYWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWvXcthedocumentspecifiesthatanupperlayermayconfigurethe@theexampleinbracketsinconfusingegbsorrncorggsni@theinclusionofmihnetworkaddressinformationprimitivei@Tthelastlineunderthevaluecolumnneedstobefixedthee@thelasttwowordsofthelastlineneedtobeinterchanged@wthelasttwowordsofthelastlineneedtobeinterchanged@wthekeyprimitivesdefinedaspartofmihsaparedescribed@cmayۋWېWۓWەW۳W۵W۶W۷WۼW۾WWWWWW"W'W.W3W:WCWZW\WcWeWrWyWzW{W|W~WW܄WܝWܩWܫWܰWܳWܶWܺWܻWܼWWWWWWWWWWWWWW1W;WJWݍWݏWWWWWWW W W"W#W$W%W&W*W+W>WOWhWiWjWދWތW>W?W@WmaybeexhaustedifdifferentclassesofdataareVmayshouldbemaybeinthesentenceދVmayshouldbemaybeinthesentenceandcommandcodeshouldbތVmaybeWދWތWmbbWmdeiaWmeachismPWWW W W Wmechanisms_WܛWܦWWW3WWmechansimWmedia'W(W)WDWېWۖWWWIWܠWܢWܤWܰWܺWWWWWWWW}WݐWWWrcmanagement"WW+WܤWܴWW݂WݐWWWW4WXWYW_W`WޕW2WmanagesWmandatoryWWWxWmanditorilyWmannerܢWmanualۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWۂWv I$b*Remove parentheses; Remove "originating".cClarity, conciseness.d28 2006/07/20%EFarrokhFKhatibiGMember^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/07/20GMember^ 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 3GPP2d38 2006/07/18'EFarrokhFKhatibiGMember^Technical, Binding_5`53a2b5Add 3GPP2 HRPD C.S0024-A and C.S0063-A in references.c3GPP2 HRPD should be supported.d43 2006/07/18(EFarrokhHcthetwomechanismsforretrievinginformationelementscurre_Vwomechanismsforretrievinginformationelementscurre_V_Vrievinginformationelementscurre_V_V ޕbA8.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 | ----------------------------------B------------------------------------------------------------------------------------------- | ...................... | ............................ | ----------------------------------------------------------------------------------------------------------------------------- | MobilityMgmtProtocolSupport | Mobility management Protocol List (4) |chiHbincludetheqosmodelandprimitivesdescribedincontributinVdetheqosmodelandprimitivesdescribedincontributinVnVsmodelandprimitivesdescribedincontributinVnVHbcallKWQWcalledWWRWmWcan-W\W_WۂWېWWhWܬW W}W݊WWWWW WWXWYWޗW9Wcancel6WcandidateOW!Wcandidates+WcannotVWܴW WcapabilitiesWAWW<WܾWW1Wcapability#WAWiWuWWۈWۊWېW+WܬWWݥW+W[WfW0W1W8Wcapable;WcapitalizeWWcapitalizeethernetconsistentlyVcapitalizemanagementVcaptionqWKWcardsbWKWcardsbWbWsbWbWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWmcnotclearwhythescopeofdefinitioncolumnisneededasalVnotclearwhythistableishereforthecsapbutequivalenVwhythistableishereforthecsapbutequivalenVVlearwhythistableishereforthecsapbutequivalenVV!݋^ Editorial_10`1a4b Add them.c?Abbreviations for DHCP and PPP should be added in this section.d83g2415 2006/07/20 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 2006/07/20 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 33crs. "cjDo we need to define what network initiated, network controlled, mobile initiated, mobile controlled are? d47g2419 2006/05/14 2006/04/28݋E YoshihiroFOhbaGMemberriale T}cA> 33  33 33>It is not clear what is the difference between 'common' and 'other' encodings and where the boundary between the two number spaces lies. g2310*clikeWWzW݂WޕWlikecommandserviceflowinsection6.2.4theinformationszVlikelihoodWlikely@WlimitationWWWWOW_WuWWlimitsWlineKWۦ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 W0WAWDWJWaWbWlinkconfigurethresholdsaddsinrinadditiontosignalstrVlinkdownaddothercausesauthenticationfailurebillingfabVlinkhandoverimminentmayVJXcitisnotinscopeof802.21toprovidehorizontalhandoverVitisobviouslythatsupportedeventlistparameterinmihcapېVitisthefirsttimethattheframestructureisreferredtoVitshouldbemadeclearthatwhenamihuserregistersfora-Vitwouldbehelpfultohaveadiscussionofpadding/alignmenVefirsttimethattheframestructureisreferredtoVVcjust@Ljustification@key@layer@@layers@lengthoftypeielistofnetworksshouldbevariable@like@limitations@*lines@link6linkconfigurethresholdsconfirmshouldbelinkconfiguret@linkdetectonlyindicateswhatisinthebraodcastorstate@linkidentifierismissingintheparameters@n@nnfiguret@linkidentifierismissingintheparameters@nguret@linkidentifierismissingintheparameters@nA TbA>  33<  G  33>of architecture model" The MIH communication 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 9 |cAAs shown in the presentation "21-06-0524-01-0000-802_16_Parameter_Effects_on_Handover_Performance" , waiting fime for system parameters, such as UCD, DCD, and so on, causes major dalay to perform handover. If mobile node can achieve this information through IS, handover performance can be improved. If this information is available during handover, this information shall be delivered to the MIH. d381g2214wDeferred 2006/07/20 2030/04/06 dypes 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 2006/05/17 2006/04/28Table 6  33>c.Reference to Internet-Draft should be removed.d369g2393net-Draft should be removed.d369g239328bupdatefigureVupdatefiguretoshowmihlinksapVupdatesectionVupdatethenumberoftheitemstartingatthetypeiepoalo܍VupdatetheprimitiveprototypeappropriatelyaVlo܍VupdatetheprimitiveprototypeappropriatelyaVaVveprototypeappropriatelyaVaVlo܍VupdatetheprimitiveprototypeappropriatelyaVaVlo܍VupdatetheprimitiveprototypeappropriatelyaVaV[3bandthedocumentcouldbeVand/orWthedocumentcouldbeVand/orWWVandthedocumentcouldbeVand/orWWouldbeVand/orWWqUblinkeventderegisterconfirmresponserVlinkeventdiscoverrequestېVserVrVrconfirmresponserVrVeregisterconfirmresponserVrVlinkeventdiscoverrequestې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ܙW6EDasFSubir^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. d281g2442 2006/07/202EDasFSubir^Technical, Binding_38`42a6.1.7 one for remote events 2006/05/1415EDasFSubir^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. d281g2442 2006/05/142EDasFSubir^Technical, Binding_38`42a6.1.741iMathieu PeressejKmake two different diagrams: one for local events and one for remote events 2006/05/1415EDasFSubir^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. d281g2442 2006/05/142EDasFSubir^Technical, Binding_38`42a6.1.7Subir Farrokhg3832 Q۾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/07/20Marked a loss of connectivity. d146 2006/05/14۶ESanjeevFAthalyeGMember^Technical, Binding_21`58a5.4.3b 2006/05/148( bmedia-dependent*WWBWWmedia-independentBWDWmedia-specificWmedium7WpWmention)WqWW3W;WWWmentionthattheflowsarelogicalsincereaderscanthinktVmentionthattheframeworksupportsuseofeitherl2orl3m3Vmentionthattheinformationservermaybepresenteitherlo;VmentionedWWmentiones:Wmerge`WqWqWqWqWqWRVEbspecificationsYWpWspecificsWspecifiedcWjWkWlWmWnWWRW܌WܕWܾW1WhWݥWPW}WނWޖW5Wspecifies\WWWދWތWspecify-WbWۈWWWܪWܷWܸWWW~WWހWނWspecifyenvelopeofcapabilitiesasappropriateforastaticVspecifyparametertoidentifylinktypetoscanVspecifytheformatorgivegreaterdetailsinthevariousva~VspecifyingVWWspeedFWGWHWIWJWۉWspelled۝W۝WpeedFWGWHWIWJWۉ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 WWa4bsplit@Vstandard@station's@\string@success@|suggestedisuggestednewpoalist@supportedcommandlist@t@table@table-6@technologies@Gtechspecificparamete@ytext@vthan@that8[the@E~݊38+theencodingformatisdefinedastablebelow@thefollowingfigureillustratesthecombinationofallthe@theieeestandardshoulddefinesthepacketformat@ them~themselves@they@9themselves@they@999they9ieee802@they9tiesneedtobespecifiedclearlyfordifferen@they9y9@they9theinforma@thisparameterspecifiesthelistofcommandsisquerytype@thisprimitiveisdeliveredfrommihfunctiononoldserving@42cshareWWsharingWshifted-WWshim۪WshouldW-W.WKWLWMWOWPWQWRWSWTWUWVWWWXW`WfWiWqWsWۂWۉWۊWۋWۍWێWېW۟WۡW۵WWWWWWWWW۟WۡWۡW%breplacelistofnetworkslinktypeswithlistofnetworktypJVreplacemacmobilenodewithlinkidentifierVVreplacemaintenancewithabetterterm-Vreplacemanyuserwithmanyusers܊Vreplacemedia-independentwithmedia-dependentBVreplacemihbymihfinentiredraftܥVreplacemihfunctionentitiesmayalsosendwithmihfunctio/VreplacemihgetinfoindicationwithmihgetinforequestOVreplacenetworkidentifierwithlinkidentifierVreplacenetworkidentifierwithmediatype]Vlacenetworkidentifierwithmediatype]V]VfierVVkparamterlistwithnumber_VreplaceperformanceofaccessnetworkswithaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1Vreplacereceptionofthespecifiedsduwasacknowledgeatl2܌Vreplaceresourceretentionstatus20withresourceretention܇VbuseofabitmapmodeltoencodethelistofeventsthatareTVcVuseofabitmapmodeltoencodethelistofeventsthattheUVWVuseofabitmapmodeltoencodethestatusoftheeventdereXVuseofabitmapmodeltoencodethestatusoftheeventregiVVuseofnetworkresourcesforaccessinginformationshouldbe۸Vusethetermipv6withdhcpv6insteadVipv6withdhcpv6insteadVVshouldbe۸Vusethetermipv6withdhcpv6insteadVV0;ۖESanjeevFAthalyeGMember^ Editorial_1`48a1.2bA,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 scoped2 2006/05/17ۖESanjeevFAthalyeGMember^ Editorial_1`48a1.2system are within the scope of this standard, and which ones are not. Additional text may be necessary to explain what IS in scoped2 2006/05/14ۖESanjeevFAthalyeGMember^ Editorial_1`48a1.2^ Editorial_1`48a1.2 from above sentence.cistencyd134 2006/05/148 2006/05/148/!EDasFSubir ^Technical, Binding_45`19a6.3.2b!Accept 21-06-0627-00-0000_IEs.docc8IEs 2.2, 2.3, 2.4 should be under General IE category d370g2448i Vivek GuptakSee comment 362m SupercededwRejected 2006/07/20 "EDasFSubir^Technical, Binding_45`51a6.3.2bDelete (LinkType+Operator) cY(LinkType+Operator) is not needed. Under a POA multiple operator may exist (MVNO model) d373g2449ORK_CAPABILITIES may be further examined/investigated for inclusion.mRejectedwDeferred 2006/06/296 !EDasFSubir ^Technical, Binding_45`19a6.3.2b!Accept 21-06-0627-00-0000_IEs.docc8IEs 2.2, 2.3, 2.4 should be under General IE category d370g2448i Vivek GuptakSee comment 362m SupercededwRejected 2006/06/29 "EDasFSubir^Technical, Binding_45`51a6.3.2bDelete (LinkType+Operator) cY(LinkType+Operator) is not needed. Under a POA multiple operator may exist (MVNO model) d373g2449373g2449373g2449n$boriginatorkWnW}Wother WAWPWRWZW\W]WpWsWuWwWۧW۰WWWWW=WܸWܹWW"W?WIWPWfWWWWWW>WVWWWXWYW7WotherieeegroupsdefinesimilarmeansandsupportclientsVotherinformationmaybevendor/networkspecificandcouldbVothersWotherwiseۖWWVWXWWoutuWWܡWWW WWW݂W݊W"W%WiWout-of-bandWf-bandWWf-bandWWWWWWWWWWWWWWWWWWWWWWWWWW3bimportant#W'WimproperDWimpropoerWimproveݍW.Win W#W'W,WAWNWOWPWQWRWSWTWUWVWWWZW]WbWfWlWpWsWuWvWxWWۃ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ܽWWWWWWWWWWWWWW'W(W)W*W,W1W8W;WGWIWQWUWWWYW\W_WWWWW> $cand݃W݉W݋WݏWݐWݛWݜWݝWݞWݠWݣWݤWݦWݧWݴWݶWݸWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWW W!W"W&W'W(W)W,W-W4W5W6W7W:W>WDWKWNWPWRWWWXWYWdWiWjWlWmWnWqWކWތWޕW2W4W4W4W4W2W2WޕWޕWޕWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWchavemorespacebetweencharactersinsta/ueandpsdn/fabox-VVhavingܑWWWnWhavingasinglemih-3glink-sapseemsinappropriateasthemiVhavingtwonormativedefinitionstlvrdf/xmlofthedatarepV member9:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~݂݄݆݈݀݁݃݅݇݉݊݋݌ݍݎݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟݠݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃ,-./0123456789:;<=>?@ABCDEFGHIJKLMOPQRSTUVWXYZlmnowމޓޔޕޖޗ01000000000000ޗޗޗޗޣޣޣޣޣޣޣޣޣޣޣޣ~vbsame?WAWsWJWyWzW{Wsamechangeisneededatthetableofcontentsandp72/l62{V62{V{V62{V{V{V{V{V{V{V{V{V{V{V{V{V{V{V{Vpchrpd'WFWhrpd1xev-doshouldbeaddedtothereferencemodelFVhteWhttp>Whypothesis݂Wi#WۈWېWWZWwWWWCWWWޗW4W5W6W7W8W@Wi-dsۑWicmpWid۔WWsWuWWW WWWWWݨWݩWWWUWideaۓWidenticalNW9W=WidentifeirݵWݺWidentiferWWidentifiedWidentifierۊWێWgWܐWWWWݒWݪWݫWݴWݵWݻWWW]WaWbWcWgWhWidentifiersDWEW[WtWܓWݳWݷWݸWidentifyWWidsNWCWRWTWUWVWWWXWWW&W&W&W&W&W&W&W&W&W&WuctoWWWs 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_WaWەW۞W7W:WܕW W WݸWWXWYWwithinthemihfheaderadditionalidentifiersarepresentthݸVwithoutۊW۝WWWWW\WWޕWwlan:Wwman@Wwon'tWwordۖWWWܱWWWWgWtWWWwordorderVtVwordingxW=WwordsېWWW1WiWWWWworkW݂WXWYW>WworkingWwould$W_WbWۇWWܼWWWWWWWW݂WKWOWPWQWmW6WwouldbegoodtocitethespecifictechnologiesasexamplesVwpaWwpa2WwraparoundWwrongۦWvWwrtۼWxvWxml#W|W~WWWܬWݚxml/rdfoWxxx܏W܏W܏W܏W܏W܏W܏W܏W܏W܏W܏W܏WqJJEGregFDaleyGMember^Technical (was Editorial)_77`26a7.3.13Remove "MIH Network Address Information" from Table 19.8@A  33cAddress 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 Kimj: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. mRejected 2006/07/19 2006/04/24=EQiaobingFXieGMember^Technical, Binding_117`53a8.3.4.bA8Remove "MIH Network Address Information" from Table 19.8@A  33c`QaRbScTgUnVpWvXwYxZy[{\]^_]4f bPReplace section 5.5.2 with contribution 21-06-0625-00-0000-New_Section_5_5_2.doccGReplace with updated text for section 5.5.1 listing all the 4 MIH SAPs d191g2237wDeferred 2006/07/20 2006/04/28Marked EPeretzFFeder^Technical, Binding_26`53bPReplace section 5.5.3 with contribution 21-06-0627-00-0000-New_Section_5_5_3.doccGReplace with updated text for section 5.5.3 listing all the 4 MIH SAPs d192g2238wDeferred 2006/07/20 2006/04/28Marked 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.@0627-00-0000-New_Section_5_5_3.doccGReplace with updated text for section 5.5.3 listing all the 4 MIH SAPs d192g2238 2006/05/14,^technicalbindingVVVtworksinitslocalitysirephreaseWWPbchangethetextto#V$VOVPVQVRVSVTVUVVVWVXVfViVjVlVmVpVchangethetexttothecsapdefinedintheieee802.16stan5Vchangethetexttothemsapdefinedintheieee802.16stan4VchangethevalidrangefordestnationidentifierinallprimiVethevalidrangefordestnationidentifierinallprimiVVidentifierinallprimiVVonidentifierinallprimiVVdrangefordestnationidentifierinallprimiVVV5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5VhangetomayinfluencehandoverdecisionVchangetomobilityextensionsof802.16andchangereferenceVchangetopolicyengineentityVchangetoprovideinformationabouttheavailabilityofacceV$b27ܔWܬW2W28ܬW29~W4WHWW+W8W2nd۫WFWݗWW3JWNWjWmWuW}WۉWەWWWW)W=WHWRWSWYW|W}WܒWܗWܘWܙWܯWܴWzW݃WݍWWW WPW^WpWށWރW1W6W3cellularumts^V3nothingiscarriedށV3rdfschemaurljVmV3urlresponseoneextendedschemaurlparameterރV3useofmihfethertypeܯV3.2W3.7|W304WW5W5W5W5W5W5W5W5W5W5W5W5W5W1W32XWTWUWVWWWXWcW33ۉWcWݳW33aW34ۉW3493W35ۉW35-40W36ۉW37-43`W3753:W38ۮW=W38-49=W39=W3gW3glink1W3gpp۽W۾WYWHWsWWWXW3gppsystemsalreadybroadcastV3gpp/3gpp2W3gpp2&W'W1WHWsW WYW5WbBreak out the segment starting with "in which case" into a separate sentence, and describe which case is the subject and explain why.c[Ambiguity of whether a phrase pertains to the whole sentence or the second part after "or".d401wDeferred 2006/07/20 XEFarrokhFKhatibiGMember^Technical, Binding_48`56a6.3.3bUProvide accurate information regarding encoding when value field is greater than 128.cIThe length encoding when value field is greater than 128 is not accurate.d407iWolfgang GrtingjX- Change figure 20 as shown in 21-06-0607-00-0000-support_for_comment_res.ppt, slide 3 vBy comment 752/756w Superceded 2006/07/20 YEFarrokhFKhatibiGMember^Technical, Binding_51`26-27a 6.3.4.3.1bs not clear. 0x2 +16+14 = 32 bits.....mRejectedvEBeing handled as part of comments 384, 396 in Comment Assignment Listw Superceded 2006/05/22 2006/04/287 dure.cministartive MIH event type has not been defined d283ndinglEEleanorFHepworthGMember^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 2006/07/20 2006/04/2815EEleanorFHepworthGMember^ Editorial_39`11a6.2.1bChnage to different.cTypo: difference d285g2235i Eunah KimmAccepted 2006/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Binding_42`24a6.3.1b0Add more information on scoping of the standard.cthe MIHF. d268g2234 2006/06/18 2006/04/2815EEleanorFHepworthGMember^ Editorial_39`11a6.2.1bChnage to different.cTypo: difference d285g2235i Eunah KimmAccepted 2006/06/18 2006/04/28EEleanorFHepworthGMember^Technical, Binding_42`24a6.3.1b0Add more information on scoping of the standard.cHepworthGMember(pcbytezW{WWbytesܑWWc_WaWWWWWoW2Wccorrectthewordtowarsonline25VcallWZWKWcalledW W0WcanAW_WbWcWdWeWjWkWmWnWoWwWzW{W|W}W~WہWۂWۄWۅWۇWۋWېW۝W۪W۾WWWWWW:W=WcWeWܪWܬWܸWܿWWWWSW_WuWxW|W}WWW*W7W>WXWYWZW~WއWޖW1W4W5W6W7Wcannotbeusedforvariablesegpoa-address~Vcan'tۈWcandidate!WcannotۄWۑWےWWMWܪWWWWWgWcannotinteroperatewithusingthestandarddocumentwhichrۑVcannotinteroperatewithusingtypeielistofnetworksiesےVےVےVےVےVےVےVےVTwcthelastlineunderthevaluecolumnneedstobefixedtheeVthelasttwoparagraphsin8.1areoutofplaceandshouldbqVcalso*WiWrWwWۆWېWۑWۓW۳WWWWW W)W.W6W:WcW|WܯWܶWWWWWWWWWWWWW W:WݍWݏWWWW W"WEWFWGWHWXWYW~WއWޔWޕWޖWalsosparqlqueryisnotcorrect~Valsothelatterdefinitionofmobilenodeisnotclearsince.Vclearsince.ValternativeSWۈWWWalternatives۳WalthoughqW~W݃Walthoughvalidthisdiagramlookstoobusythisisexactlyt݃ValtituderesolutionWalways۾WWܰWWWއWambiguityWWWambiguityofwhetheraphrasepertainstothewholesentenceWVambiguitysuccinctnessallowthecasethatmihisnotsupporVamendۆWamendedܸWamendmentۅWamendmentsWamendsۊWamendsmihcapabilitydiscoverymessagebyaddingnetworkidۊVammendmentsWUcitisimportanttointerfaceortransportmechansimcontradiVitisimpossibletotestcompliancewithabstractionssucha%VitisnotclearwhatisthedifferencebetweencommonandotVitisnotclearwhatsupportingmultipleinterfacesmeans!VitisnotclearwhetherthescopeoftheprotocolfunctionsVVossibletotestcompliancewithabstractionssucha%V%VLcthecurrentmihreferencemodelfor3gpptriestoshowhowmXVthecurrentmihreferencemodelfor3gpp2triestoshowhowYVthecurrenttextcanbebetterexplainedthissapdefinesth7VthecurrenttextdoesnotdescribewhatthelinklayerwilleVthecurrenttextdoesnotstatehowremotecommunicationis3VthecurrenttextimpliesthatthediscoveryofmihfunctionVYVYVYVYVYVYVYVecommunicationis3VthecurrenttextimpliesthatthediscoveryofmihfunctionVthedecriptionisthesameastherequest܄VthedefinitionofeventidsaremissingitiscriticallyimpNVthedefinitionoftheparameterforsupportedisqueryismissdVthedefinitionsgivenforthemihhandoverxxxprimitivesin܏VthedefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofthemesageisthesameastherequest܅VQEFarrokhFKhatibiGMember^ Editorial_43`5-6a6.3.1bQRemove "the mobile node may move across different access networks. In such cases"cRestating the obviousd338 2006/07/20REFarrokhFKhatibiGMember^Technical (was Editorial)_44`48a6.3.2bChange to "cdma2000-HRPD"cUnfamiliar acronymd351 2006/07/20SEFarrokhFKhatibiGMember^Technical, Non-binding_44`38-49a6.3.2bRather then listing, provide individual descriptor for each network: E.g.: cdma2000 desciptor could be United States; WLAN descriptor could be LAT/LON of a particular access point (e.g. somebody's home)cThere is vagueness in how "geographic area" is defined. Considering that network coverage areas can vary wildly between hot-spots in the size of a room to entier countries, listing available networks seems inappropriated364v9United states may not be an appropriate representation...wRejected 2006/07/20 38-49a6.3.2the same technologyMember/05/14 ܤbcA 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/07/20ܥEVivekFGuptaGMember^ Editorial_15`21a5.2b#Replace MIH by MIHF in entire draftcReplace all occurences of MIH in the draft by MIHF. The draft needs to consistently use MIHF instead of just MIH wherever applicabled101g3209 2006/07/20ܦEVivekFGuptaGMember^ Editorial_15`42a5.2bDefine "Intra-roaming"c0"Intra-roaming" handover mechanisms is undefinedd105g3220v comment 104.w Superceded 2006/07/20 d56a5.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 2006/05/16ESanjeevFAthalyeGMember^ Editorial_45`21-22a6.3.2b=Definition of Network Operator in middle column is cicrcular.c Superfluousd376 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_47`26a6.3.2bInsert before "or": ", by associating information contained in its internal database with otherwise available information (such as geolocation), "cRemove apparent limitationsd390wAccepted 2006/07/20 ESanjeevFAthalyeGMember^Technical, Binding_47`28-32a6.3.2bARephrease the two sentences as follows: "In any case, the MIH Function 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/07/20 ESanjeevFAthalyeGMember^Technical, Binding_51`6a 6.3.4.2.5ESanjeev brephrase)W,Wrephrasecollectsinformationonnetworksinitslocalitysi,VrephreaseWrephreasethetwosentencesasfollowsinanycasethemihfVhfVVl?@^bA&@caA@`bBDHA@ABjAC@!E@rFbBA{GbB]AWHbAIbAcJbBzcK@L@UMbAN@bObA7QG"vAR@vA|SbA#TbA^vAUbAV`>v5X@AbAZbACvAI[@\@k ]cP_bAC`cAC`@ acBbbbAscbAeEfbAh@ibAAjbAZvkcA/vlvAmbA cAnbAcA[vokA. 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<VreplacenetworktypeswithlinkidentifierݼVreplacenormativewithinformativeoVreplacenumberofparametersinlinkparamterlistwithnumber_Vreplacepage24withcontribution21-06-06xx-01-0000-atose݄VreplaceperformanceofaccessnetworkswithaccessnetworksVVreplacepoawithnewpoa#VreplacepppwithnetworkconnectivityprotocolVreplacer1/r2/r3withonlyr1Vreplacereceptionofthespecifiedsduwasacknowledgeatl2܌Vreplaceresourceretentionstatus20withresourceretention܇VreplaceresultoftryingtoconiferthelinkwithresultoflVreplacesection5.51withcontribution21-06-0624-00-0000-n Vithcontribution21-06-0624-00-0000-n V Vntionstatus20withresourceretention܇V܇Vtus20withresourceretention܇V܇V8JcdifferentiateۈW2WdifficultWWdirectWW WdirectionvWdirectlywWۈWWWW2W"W$W:WdisallowSWdisambiguateWdisassociated-WWdisconnectWdiscoverۈWېWQWRWWW{WݥWW"W+WJWQWQWQWQWQWWۊWWݏWWW+WdiscoveryregistrationandeventregistrationmechanismsareVdiscussܯWݳWdiscussedDWpWvW+WdiscussionAWWW܏WWdiscussionofhow802.3networkscangetdirectinternetaccVdiscussionoflogicalnetworkreferencemodelusesroamingcVdispatchmWdispatched7WdistinctWdistinguishۊW:WܜW:WdistinguishedWdistributedWdo_WbWeWfWlWۈW۬WWCWܐWWWWWWW݊WWdoweneedtodefinewhatnetworkinitiatednetworkcontroll݊V@^EFarrokhFKhatibiGMember^ Editorial_60`12a6.3.8.1bRemove sentence "OWL is ".cSuperfluous sentenced467 2006/07/20_EFarrokhFKhatibiGMember^Technical, Binding_61`46-49a6.3.9bRestructure as " communicates with the MIHF that may reside locally or remotely in the access network. Change the remaining text in that paragraph accoridingly (e.g. by qualifying "in case of remote MIHF"), or simple remove the rest, since cZImplied limitation of capability in assuming that MIIS can only reside in access network. d471v8on request of commenter. Further clarification required.wRejected 2006/07/20`EFarrokhFKhatibiGMember^Technical, Binding_62`25a6.3.9b4Supplement title by appenidng "from a Remote Server"cAllow local MIIS case.d481vnFigure 22 has been updated as per comment 473 and contribution 21-06-0642-02-0000-Information_service_flow.pptw Superceded 2006/07/20oper rerence to Internet Draftd375Kliuۅۆ:;<=>?@ABCDnjedjou݂݃o'brien݄ohba݆݈݅݇݉݊݋݌ݍݎݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟݠݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σperessequۊۏrajkumar,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRsalminenSshuۄWshuguimingۄVeemanthula[\]^_`abcdefghijksubir  !"#$%&'()*+subritaisuke݀݁tanlmnotaniuchipqrstu@_‚A%ƒЃуH012345Wܰ҃‚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\2bremoveexampleorbetterconveyincrementalvalueVV[Vremovefahah-aaav-aaa:Vremovefigure19@VremoveforloopandsplitintotwotablesVremovehelp@Vremoveho-typepossiblyaddlinktypeinsteadVremoveinthe21draftPVremoveisembeddedVremoveitis۹Vremoveline1uVremoveline33transactionidݳVremoveline37-43andaddreferencetothedefinitionofthe`Vitis۹V۹VoveisembeddedVremoveitis۹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۹VGc4ېWWWW%W&W)W-W0W=WNWܮWݵWݾWWWW W W WBWmWޕWAWBWCW4.1W40WW41aWW,W43KWW44KWW;W45WWWW,W46kWW47WW48W49W49-50W5ېWWW݄W݆WWWWޕW;W5.3.2!WW5.4.3W5.5$WWW5.5.1 W W5.5.3 W5.6.1%W'WW1W2W6W5.6.1mediaspecificsapV5.6.2.1&W5.8nW5.8.3+W50W51W52WVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV +cEFarrokhFKhatibiGMember^ Editorial_88`48a 7.4.6.1.1bChange "makes" to "make".c Plural formd610 2006/07/20dEFarrokhFKhatibiGMember^ Editorial_89`33a 7.4.6.1.3bChange "makes" to "make".c Plural formd617 2006/07/20eEFarrokhFKhatibiGMember^ Editorial_110`26a8.1bChange to "reliable service"c[Should use adjective, not noun form, since there is no such thing as "reliability service".d683 2006/07/20fEFarrokhFKhatibiGMember^ Editorial_111`64a8.3b>Remove square brackets here and two other places on next page.cMMisleading use of square brackets, which are customarily used for references.d696 2006/07/20gEFarrokhFKhatibiGMember^ Editorial_112`61a8.3.1bChange "utmost" to "at most".use of square brackets, which are customarily used for references.d696 2006/05/18gEFarrokhFKhatibiGMember^ Editorial_112`61a8.3.1bChange "utmost" to "at most".hBOcerrorFWGWHWIWJW۠W5W6W8W<WGW^W_WaWfWiWlWoWpWrWtWvWxWyWzW}W~WW܀W܃W܆W܇W܈W܊W܋W܌W.WerrorswWesWespeciallyW;Wessential'WessentiallyWestablishܡWestablished܋WWestablishment@WestimationWW WetcܰWܵWܼWWWWWݏWethernetWqWethertypeWܯWevaluatedPWeven^WmWWWWEWFWGWHW?WHW?W?WWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHW|+brenamethenon-posmihentitytomihnon-posforconsistencyۭVrenaming݂WrenewalݍW4WrenumberWreorderWSWreorderthetable4andtable5tobeconsistentwithorderiVrepalce=Wrepalcebeaslessaspossiblewithbeminimal=VrepeatedWbeaslessaspossiblewithbeminimal=VrepeatedWWaslessaspossiblewithbeminimal=V=V PgcIncorrect wordd711 2006/07/20hEFarrokhFKhatibiGMember^Technical, Binding_115`62a8.3.3.2b%Header Types must be fully specified.c[Conveying possibility, not certainty regarding Header Types, indicates incomplete standard.d749v#no suggested text Issue identified.wRejected 2006/07/20gth".cMissing space between words.d764 2006/07/20jEFarrokhFKhatibiGMember^ Editorial_118`28a8.4b"are", not "rae".cSpellingd771 2006/07/20kEFarrokhFKhatibiGMember^Technical, Non-binding_122`31a8.4.2.1bL" addressing the new PoA" should change to " address when at the new PoA".cConfusing phrased785 2006/07/20lEFarrokhFKhatibiGMember^ Editorial_123`9a8.4.2.3b "as follows:"c Customary used792 2006/07/20mEFarrokhFKhatibiGMember^ Editorial_123`58a8.4.2.7b "Parameters"cSpellingd794 2006/07/20nEFarrokhFKhatibinEFarrokhFKhatibi%9bcertain#WTWdWWܻWchagesݓ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?WEWFWGWHWOWRWlWyWzW+tcremovesfromthewordsupportsinthelinethatquotesotheVremovetheletterafromthesentencethatsaysthemihfuncVremovethesfromresultsinthelinefromoneaccessnetworVremovedAWsW۝WWWݕWݖWݘWW7WrenameۭWWKWrenamethefigurecaptiontoremotecommandserviceflowKVrenamethemessagefromtheremotemihftolocalmihfaseveVrenamethenon-posmihentitytomihnon-posforconsistencyۭVrenamedWrenewalWݍW4WreorderWreorderthetable4andtable5tobeconsistentwithorderiVerthetable4andtable5tobeconsistentwithorderiVVonsistentwithorderiVVwithorderiVVerthetable4andtable5tobeconsistentwithorderiVVVVVVVVVcrepeat@replaced@reponse@jrepresents@Zrequests@+reserved@resource@results@rfc@room@samesap@satisfy@Aschema@sdo@ksection@sections@see@#sent@sentences@Qservers@services@setsets@4share@should2shouldn't@ouldn't@houldn't@tivenotnounformsincethereisnosuchth@sincethereisnosuchth@ivenotnounformsincethereisnosuchth@haveanotherblockcalledl3transport@suggestednewpoaidentisnotneededifitispartofsuggeste@qsupported@Yswitch@syntaxerrorinnetworksecurityandqualityofsecuritycap@Dsyntaxerrorinthisisusedtorespondtheresult@4systemmanagementhasbeenintroducedasaserviceherehowe@.take@?target@Stechnology@that's@the$\0ccthetwostacksinthefigureareidentical@toinsureinteroperabilitytheieee802.21mustdefinehowt@Fupper@visible@8jreplacethelastmihgetinforesponsebyaconfirmprimitiv@Kk&vbyresolutionofcomment346@:nospecificremedysuggestedcomment350addressesthis@nthe@ect@8jby@Kkretrieval@&isincorrect@8jby@Kkretrieval@&HcunifiedݜWݝWݞWݠWݣWݤWݦWݧWWWWWuniformIWuniquesW WPWuniqueeventidentiferWuniqueness Wunit]WWWunknownWWunlabeledhWunlessWunlikeW+-݀E MatsumotoFTaisukeGMember^Technical, Binding_59`40a6.3.8b&Subsection of 6.3.8 should be deleted.cGUsage of information service schema describled in 6.3.8 is too unclear.d459g3924iYoshihiro OhbakhPlease be more specific which part of section 6.3.8 is unclear. Re-submission of comment is recommended.mRejectedv:Comment is unclear as to specifically what part is unclearwRejected 2006/07/20 ݁E MatsumotoFTaisukeGMember^Technical, Binding_114`55b6define the value for "Version" like "0" for version 1.c(The value for "Version" is not defined.d738g3925vby comment 737w Superceded 2006/07/20 rwRejected 2006/07/19 ed although the length for each Value field is defined. Same for Cost in 6.3.4.2.3 and elsewhere in the draft.  d403g2216 2006/05/14 2006/04/26EBenjaminFKohGMember^Technical, Binding_83`19a 7.4.1.1.2b3Replace with "Any valid local or remote identifier"-------------bappendedݗWWappendixܩWܪWWWNWappenidng`WappenidxWapplicableWWapplicationVWiWއ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:WAWBWWWwWdefinitonܞWdelayWdelet)WdeletekWnWvWwWۦW۪WWWW W W WWWWWWW"WܠWܭWWWAW;WWW2W7Wdeletecsapandmsapbetweenmhfunctionandmanagementen2VdeleteheterogeneousVdeletel2fromabovesentenceܭVdeletelinktypeoperator"VdeletemediaagnosticAVdeletelinktypeoperator"V"VdbprogressedUWYWpronounced2WpropagateݎWproperlyےW۔WWUWpropertiesOWSWܾWWproposalۅWۆWۇWۈWDWproposeۇWۈWproposedSW<Wprotocol(WkWnWpWsWtWuWwWxWWWW#W/WqWܫWܯW W(W0WCWDW{WݎWWW W2W}WޕW7Wprotocols۾WW7WprototypeaWaWaWaWaWaWaWaWaWaWaWaWaWaWaWaW+creserved}WWލWޕWreservedbitshouldbeassignedލVresideWܩWW_WuW7WresidesܟWܩWresiding:WresolutionW*WW*W*W*W*W*W*W*W*W*W"cimproperrerencetointernetdraftUVYVimpropersentencethisprimitivereturnstheresultoftheqQVimproperuseofthemihgetinfoindicationwhenacommandiOVimprovesWݍW WimprovedtWۧWWW"W,W>W?WMWnWqW|WimprovedclarityۧV>Vimprovedclphrasing?VimprovedgrammarverbvsnounVimprovedphrasing"V,VnVqVimprovedsentenceflowVMVycimprovement@"in@ J2:ninadditiontosufferingfromthesamelackofcontextasab@inorderformobilenode'smihfunctionentitytocommencem@inappropriate@}incomplete@cinconsistent@incorrect@inefficiencies@info@@information@9informative@initiator@instantiations@inter-technology@interpret@is@rFO]܎ wo:issoft-handoverlimitedtohandoverbetweenhomogeneousacc@Wisn't@cissue@it@:itisimportanttointerfaceortransportmechansimcontradi@itisnotinscopeof802.21toprovidehorizontalhandover@it's@Jhelpfultohaveadiscussionofpadding/alignmen@Jfultohaveadiscussionofpadding/alignmen@Jowheresipissupporte@lv@tb"may not like"c Word orderd893 2006/07/20uEFarrokhFKhatibiGMember^Technical, Binding_149`7aAnnex B1bRemove "at network side"cZImplied limitation of capability in assuming that MIIS can only reside in access network. d895vby comment 892w Superceded 2006/07/20vEFarrokhFKhatibiGMember^ Editorial_149`56aAnnex B2bRemove "a little"cConfusing phrased897vby comment 892w Superceded 2006/07/201GPP2"c Incorrectnessd885 2006/05/14tEFarrokhFKhatibiGMember^ Editorial_148`22aAnnex B1138`42a8.6.1b "on-demand"c Missing dashd864 2006/05/14sEFarrokhFKhatibiGMember^ Editorial_145`3aAnnex A2bReplace "3GPP" with "3GPP2"c Incorrectnessd885 2006/05/14tEFarrokhFKhatibiGMember^ Editorial_148`22aAnnex B12bReplace "3GPP" with "3GPP2"c Incorrectnessd885 2006/05/14tEFarrokhFKhatibiGMember^ Editorial_148`22aAnnex B1v`ށa8.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 2006/07/20ނEKenichiFTaniuchi^Technical, Binding_128a8.4.2.24b type of query. | |-------chi eۃ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 2006/07/20 2006/04/24  2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_88`9bClarify definitions.04/28EEleanorFHepworthGMember^Technical, Binding_86`5b/Remove HO-Type; possibly add link type instead?cWhy 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?d596g2273 2006/07/19 2006/04/28EEleanorFHepworthGMember^Technical (was Editorial)_88`9bClarify definitions.6/05/14 2006/04/28EEleanorFHepworthngM9`Ä78WYÄ9CÄDEÄIZSÄJREÄRV۝ÄSrÄWXÄWZ_ÄbgÄdeۻÄfhÄgjVÄijۧÄqrĆEGUGa1.1ە1.2ۖۗۘۙۚۛۜ۝Ƀ ,1.3۞!"#1.4݅1.5۟1.6ܛ%18W2۠ۡȃʃ$&'݆pq22W3ۣۢۤۥۦۧۨ ./1ܜܝܞܟ()*+,-.w݊3.1+W402ܚWܠ݋݌5.1۩۩۩۩۩۩۩݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌݌ܪ˃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/W0W1W2W3W4W5W6W7W8W9WیWWuWܑWWWAWWWݬWݮWݯWݰWݱWݳWWWWWWWW'WNWpartialWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWpdsn/fa-WWpduWpeer{W!W%W3W<W>W?WpeersW>WgWpending WpeopleWperWeWmWvWWWperlastmarch06denveracceptedcommentresolutionaddanVperformuWۂWېW|WperformanceWW|WݍWperformed3W,^technicalbindingܝVܞVܪVܬVܮVܳVܴVܶVܷVܸVܹVܻVܼVܽVܾVܿVVVVVVVorted 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 EHongFChengGMember^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.d306g2216 2006/07/20 2006/04/274EHongFChengGMember^Technical, Binding_44`51a6.3.2bBTo provide client of the number of networks instead of operators. cAMFor item 1.2 of Table 6, the number of operators does not necessary reflect the network coverage status accurately. For example, an operator can operates several hotspots at the same area each serving a distinct group of customer. Or, several operator could be sharing an network infrastructure in certain environment, e.g. airport. Md356g2217wDeferred 2006/07/20 2006/04/27 EHongFChengGMember^Technical (was Editorial)_59`41a6.3.8b)Put contents of section 6.3.8 to Annex C. Annex C.of operators. c.3, Binding_140`140a Annex A-1y used for references.:&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 3GPP2d38 2006/07/20'EFarrokhFKhatibiGMember^Technical, Binding_5`53a2b5Add 3GPP2 HRPD C.S0024-A and C.S0063-A in references.c3GPP2 HRPD should be supported.d43wAccepted 2006/07/20(EFarrokhNon-binding_4`30a1.6bRemove section 1.6V_SESSION_ID 0x00000002 @A> 335  33>c:Header TLVs are defined but no values are assigned to themd890g2270 2006/05/14 2006.04.25 ܛEVivekFGuptaGMember^Technical, Non-binding_4`30a1.6bRemove section 1.6ical, Non-binding_4`30a1.6bRemove section 1.6mechanism to ask for a specific location/interest based information elements from a MIH-IS server over TLV queries.d6633900|$ ې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  *d572g2248wAccepted 2006/07/20 2006/04/11Marked nerated 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 paD bremovetable22fromline41page127toline8page128|Vremovetable23fromline29toline63~Vremovetechnology-independe VremovetheۨVremovetheabovesenetenceVremovetheabovetextuntilqoscontributionisacceptedbyVenceVVY ^editorialу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃$&:IlnWpquwވފދތސޑޒޓޖWޗW:W;W=?W?????????????????????######################################################################################################################################p ۋbAUpdate 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 33fcAWupdates 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. Wd637g2252QUncThis 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 2006/07/20 2006/04/28 oEPek 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.wRejectedng.d72>cmissingspacebetweenwordsViVmissingvaluerangeandcodesVmisuse:WmixedyWzWmkaeWWmm/W0W1W2W3W4W5W6W7W8W9WFWGWHWIW9WFWGWHWIWIW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!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ޕW;vparagraph۪WparamێWparameterܗWWWރWparametersIWRWTWۅWۊWWWWWaWSWށWރWpart"WQW۔W۪W۳WWW W)WܗWWDW݀W݄WW0W4W5Wpartofnetsapdiscussionasrepresentedbyissue130VparticularWpartitioningWpartnersWWparts WܗW2WpassesQWRWSWTWpayloadWpdsn/fa-Wpeer;Wpeers۔WTWperDWUWVWWWnWoW{W۽WWW%WEW`WzWWW+W>WPWYWDWperformanceWpertinent۳WpgێWphyWWWpieceWplaces/WplanܛWSWplane4W5WݓWprotocolW0WݓWݳWprovideܢWݏWZWprovidedW@WܗW Wprovider's۳Wprovides4Wprovisioned۳Wprovisioning۳WqosWqueriesܗWquerlyܗWquery"WܗWWqbmeansWWܟWPWWmeant'WNWmeasureable-Wmeasurements݊Wmechanism_WbWuWWPW<Wmechanisms_WەWW3Wmechannism_Wmedia'W(W)W?WAWDWpWuWvWWۖWWW#WܤWܺWWWWWAW}WW2W]WaW:WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWJbwithin?WiWەW7WܫWWJWݸWWwithinthemihfheaderadditionalidentifiersthathelptoaݸVwithout۝Wwlan?WWSWwllWwmanDWwordۜWWQWܺWWSWwllWwmanDWwordۜWWQWܺWܺWSWwllWwmanDWwordۜWWQWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWܺWclimitationsWWPWlimited_WaWwW1WIW>WlimitedscopeofhoIVlimiting:WlimitsWlineKWۦWWWWWWWWW-WkWWW݇WWWWWWWWWWWWWWWW*W,W;W?Wline14saysieareclassifiedintothreegroupshoweverit;VMWOWPWQWRWSWTWUWVWWWcWdWeWfWۄ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^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 2006/07/20 2006/04/26 6/07/19 2006/04/26 18 2006/04/26EBenjaminFKohGMember^Technical, Binding_83`19a 7.4.1.1.2b3Replace with "Any valid local or remote identifier"ion element is vague or not defined. For example the Link Type Values for 6.3.4.1.1 is not defined although the length for each Value field is defined. Same for Cost in 6.3.4.2.3 and elsewhere in the draft.  d403g2216 2006/05/17 2006/04/26EBenjaminFKohGMember^Technical, Binding_83`19a 7.4.1.1.2b3Replace with "Any valid local or remote identifier"-------------Gcifthetypeienetworktypeisapprovedthenomustbeupdat>V?Vifweadopt21-06-0522-04-sessioidentifierthelengthfieldݵVignoreWignoresWigonedxWiiޗWiiiޗWillustratedW@Willustration:WimmatureSWimminentWimpending!Wimplement WmWSWimminentWimpending!Wimplement WmWmWtWimpending!Wimplement WmWmWWmWmW݂EEricFNJEDJOUGMember^Technical, Binding_18`10a5.3.2bAHremove section 5.3.2 and possibly move it to annex renaming it "example of architecture model" The MIH communication 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. Hcidered 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. Hcodel 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. Hc/05/14 2006/04/26EBenjaminFKohGMember^Technical, Binding_83`19a 7.4.1.1.2b3Replace with "Any valid local or remote identifier"-------------.KpEQiaobingFXieGMember^Technical (was Editorial)_110`7a8.1bcient. 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.mRejected 2006/07/19 2006/04/24 pEQiaobingFXieGMember^Technical (was Editorial)_110`7a8.1bted-Duplicate 2006/05/14 2006/04/24 Remove Sections 7.4.15.3.2, 7.4.15.3.3, 7.4.15.3.4cEGregFDaleyGMember^ Editorial_105`62a 7.4.14.2.2 bDaleyGMember^ Editorial_18`20a5.3.2b3a6.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.c 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ÃF[ÃFÃF?ÃGÃG @ÃG0 ÃG@ÃGPSÃG`ÃGpÃGBÃGۑÃGݕÃH!ÃH TÃH0ÃH@"ÃHPÃH`UÃHpÃHݖÃHÃHÃIÃI |ÃI0VÃI@ܸÃIPܹÃI`ÃIp\ÃI#ÃIܺÃIÃJÃJ ܻÃJ0ÃJ@݉ÃJPCÃJ`XÃJpÃJDÃJ$ÃJEÃQÃQ WÃQ0ÃQ@~ÃQPYÃQ`ÃQpÃQXÃQݗÃQFÃRÃR ܼÃR0]ÃR@ܗÃRP%ÃR`^ÃRp&ÃRGÃRÃRHÃS'ÃS ÃS0ÃS@ÃSPݘÃS`ÃSp(ÃSYÃSuÃSÃTÃT ÃT0}^_ ەۖۗۘ0ۙۚɃ@ۛۜ۝ !",P۞۟ܛ#$%݅`۠ۡȃʃ&'݆pqpۣۢ1ܜ()݊ۤۥۦۧ ./34ܝܞ*+,wۨ 5ܟ-.‚!02݋݌‚"ܠ‚$۩nS‚%ܡܢܣ/‚& ۪۫ܤܥܦܧܨ01‚'ۭ۬,ܩ23Zb1movetheconceptofhorizontalandverticalhandoverstos:V1oneormoretlvspecificparametersށV1oneormoretlvspecificresponseparametersރV1removesection5.3.2!VificresponseparametersރV1removesection5.3.2!V!VcificresponseparametersރV1removesection5.3.2!V!V.3.2!V!VcificresponseparametersރV1removesection5.3.2!V!VcificresponseparametersރV1removesection5.3.2!V!V ݃bAKHide 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.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.d187g2255v[Delete the last sentence of second bullet and add MIH User from network side in the figure.wAccepted-Modified 2006/07/20 2006/04/305 ݄EFranFO'BrienGMember^Technical, Binding_24`1bLReplace page 24 with contribution 21-06-06xx-01-0000-Addition to section 5.5ection 5.5with a better description of the MIH Function location in the stack. Add additional text.+ bthe݊WݍWݎWݕWݗWݘWݙWݵWݶWݸWݹWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWWW W!W"W#W$W%W&W'W+W,W0W1W2W3W4W5W7W8W9W;W<W=W>W?W@WBWIWJWLWMWNWOWPWQWRWSWTWUWWWXWYWZWaWbWcWfWiWjWyWzW{W}WWނWބWޅWކWފWދWތWސWޑWޒWޓWޔWޕWޖW0W3W5W6W7W7W7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW:݅E YoshihiroFOhbaGMember^ Editorial_4`10a1.41bLReplace page 24 with contribution 21-06-06xx-01-0000-Addition to section 5.5cjReplace Figure 5 with a better description of the MIH Function location in the stack. Add additional text.d188g2222 2006/05/14 2006/04/28݅E YoshihiroFOhbaGMember^ Editorial_4`10a1.4cAlthough 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.d187g2255 2006/05/14 2006/04/305݄EFranFO'BrienGMember^Technical, Binding_24`1bLReplace page 24 with contribution 21-06-06xx-01-0000-Addition to section 5.5cjReplace Figure 5 with a better description of the MIH Function location in the stack. Add additional text.d188g2222 2006/05/14 2006/04/28݅E YoshihiroFOhbaGMember^ Editorial_4`10a1.4ier".$EPeretzFFeder^ Editorial_104`48bver 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 d653g2262 2006/07/19 2006/04/28$EPeretzFFeder^ Editorial_104`48b2006/05/14#EPeretzFFeder^Technical, Binding_104`41a 7.4.14.1.3bf  33      33  33cc Add context transfer d644g2260 2006/05/14 2006/04/28-U@_@c@cApbA@AbAcA@cA+bBB@ b bA4=c9@AbAObAcA@bAbARbARbARcA@b@@@@`ccgbcAg@c@cccbAcgbAgb^bAg  ^bAgcAgbAgEcbb@g!bAg"cAg$bAcAg%cAg'bA*cAg,b.b" ObcjThis is a link layer indication which should only be received by the MIH function, not by any upper layer.d531g2292wAccepted 2006/07/20 2006/04/24 PEQiaobingFXieGMember^Technical, Binding_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.d534g2293wAccepted 2006/07/20 2006/04/24 QEQiaobingFXieqJE YoshihiroFOhbaGMember^Technical, Binding_137`26a8.5.3.19bRemove NewPoAIdentifier.c;NewPoAMAC is not needed if it is part of NewLinkIdentifier.d849g2379 2006/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_137`26a8.5.3.19ng_136`30a8.5.3.15bRemove NewPoAIdentifier.c;NewPoAMAC is not needed if it is part of NewLinkIdentifier.d849g2379 2006/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_137`26a8.5.3.19nical, Binding_136`30a8.5.3.15bRemove NewPoAIdentifier.c;NewPoAMAC is not needed if it is part of NewLinkIdentifier.d849g2379 2006/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_137`26a8.5.3.198.5.3.15bRemove NewPoAIdentifier.c;NewPoAMAC is not needed if it is part of NewLinkIdentifier.d849g2379 2006/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_137`26a8.5.3.19/28..< |bD------------------------------------------------------------------------------------------------------------------ POA_SystemParameters | | | For 802.16 case, UCD, DCD, | | | UIUC, DIUC, etc. -------------------------------------E------------------------------------------------------------------------------------------------------------------------------------WcrossesޖW5Wcs%WWDWcurremtWcurrent!W,WYWZW]W_WbWeWuWWۃWۄWۅWۆWۇWۈWۋW۸W۽WWWYWnWW{WWW3W4W5W7WXWYWޖW4W:Wcurrenttextneedsimprovement,Vcurrentlinkaction6Wcurrentlinkactionvaluesinmihhandovercommitrequest/resp6Vcurrently'WSW_W:WWWޖW5WcurrrentPW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WdWdrewordline40mobilipregistrationmightbenowtriggerV< cnot݌WݎWݔWݙWݬWݮWݯWݰWݱWݷWWWWWWWWWWWWWWWWWWWWWWW(W*W+W,W3W6W:W@WDWLWMWNWOWQWUWVW^W_W`WfWiWlWmWnWvW}W~WWބWޅWކWއWމWޏWޔWޗW6W7W7W7W7W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅W߅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#ۏ۞؃ܗܬ#ݪb@"&'Ss$sݍދPDy܆ݮ)6ސ`۠rv}ܒi݆ݲݹdpۢƒӃ) &փكޑp۩TܡɃu}ݖݟݣ%ܚ߃bݏݑƃރ6JW K lpݽDބ‚!2ۄ܃ Oj݂݃݅E_ippppp 5\GMember^Technical, Binding_58`1-21a6.3.7.2bProvide context with an introduction to the Request/Response message, which explains how the PoS determines the response. Also, remove parenthetical expressions in chaper titles. cSimilar to what is stated in 6.3.6.1, examples lack context. Requesting such information without e.g. a geographic reference is meaningless. Additionally, parethetical expressions in chapter titles are unnecessary.d456vby comment 339w Superceded 2006/07/20]EFarrokhFKhatibiGMember^Technical, Binding_59`1-39a6.3.7.3bSee page 58 lines 1-21.c`Similar to page 58 lines 1-21, lack of context, unnecessary parenthetical expressions in titles.d465vby comment 339w Superceded 2006/07/20f context as above, the example has little incremental value.d453 2006/07/18\EFarrokhFKhatibiGMember^Technical, Binding_58`1-21a6.3.7.2ences.c"Improper rerence to Internet Draftd375 2006/04/289ODEPeretzFFeder^Technical, Non-binding_31`23a5.6.3.1bpendent SAPsc[5.6.1 Media Specific SAP Be consistent with the mdeia dependent and media independent textd217g2241 2006/06/21 2006/04/28EPeretzFFeder^Technical, Non-binding_31`23a5.6.3.1bllowing text before the introduction of Figure 11d208g2240 2006/06/21 2006/04/28EPeretzFFeder^ 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 2006/06/21 2006/04/28EPeretzFFeder^Technical, Non-binding_31`23a5.6.3.1bn 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 Od202g2239 2006/05/14 2006/04/28 EPeretzFFeder EPeretzFFeder6/05/14_EQiaobingFXieGMember^ Editorial_6`37aToCbAAdd Annexes to the end of ToC@A  cAnnexes missing from ToCd45g2235 2006/07/20 2006/04/24EQiaobingFXieGMember^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. ]@A*  33\  *cAThe 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. @{\]^_TSr^technicalWWWWWWWWWWWWWW W W W W WWWWWWWWWWWW W!W"W#W%W'W(W)W*W,W-W.W/W0W1W2W3W4W5W6W7W8W9W;W<W=W>W?W@WAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWmWmWkWeWeWeWeWeWeWeWeWeWeWeWeWeWeWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWcWcWcWcWcWcWcWcWcWcWcWcWcWcWcW"2bremovesentenceۥVremovesentenceowlis^VremovesipfromlistVremovesquarebracketshereand3additionalplacesonthisVremovesquarebracketshereandtwootherplacesonnextpagfVremovessidbssidservesasuniquenetwork[VremovesuggestedmacnewpoaidV[VremovesuggestedmacnewpoaidVVnetwork[V[VVVd3additionalplacesonthisVVplacesonthisVVplacesonthisVVshereand3additionalplacesonthisVVesquarebracketshereand3additionalplacesonthisVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVcoperators[W^WWW@WWWݙWWopposedWoptimizeݏWoptionWWoptionalWXWWW WW'WoptionallyhWoptonsܯWWWoptonsܯ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ެWWWWWWWWWWWWWWWWW1W3W4W5W6W7WKWLWbWWbW6c802.3WqWW802.3/ethernetW802.3adWW802sW86݇W87یW9W;W910.2-g-1>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ܼWWWWWWWWWWGI{lnoneneeded݂VVneeded݂WWnone݂WW€ ԃf1H 2006/07/20 2006/04/2815 5Qtcsomething:W;W<W=W>Wsometimes:WsomewhereWsophisticatedWWsortWW,WsoundsWsourceۍW۶WWݴW&WsourceidentifiersourcesZWsouthboundEWFWGWHWspaceWW-WWWiW݉WWWspaceisneededbetween802.21andspecification݉Von݉V݉Vededbetween802.21andspecification݉V݉VWWWWWWWWWWWWWWWWWWWWWWWWWW$W:WCWaWiWܘWܰWܺWܾWWWWW~Wspecificformatforthevalueportionineachtypeofinform~Vspecifically WspecificationW۩W۾WWW WWܟWWWW݉WspecificationoftypeienetworkqosisnotmediaindependenVspecifictaion+WspecifiedWېWW܌WܾWWWWWEWbaConsider adding UniqueEventIdentifer for Link_Detected and Link_Handover_Imminent. cAYSome indication data (Such as Link_Detected, Link_Handover_Imminent) may become deprecated, but only Link_Going_Down may be rolled back, because it contains UniqueEventIdentifer - Starting Page#: p77 p79 - Starting Line#: p77 (26) p79(45) - Fig/Table# (if applicable): - Section#: 7.3.13, 7.3.16 Yd544g2229wRejected 2006/07/20EDas,FSubir^Technical, Binding_87`59a 7.4.5.2.2bAdd GetStatusResponseSet.c GetStatusResponseSet is missing.d605g2369vdAdd description of parameters in this primitive. Change GetStatusRequestSet to GetStatusResponseSet.wAccepted-Modified 2006/07/20: Table 20/Table 21 - Section#: 8.4 (8.4.1-8.4.2) d760g2228 2006/05/1420os ranging from devices with less functinality to devices with more functionality. 802.21 should allow b0W&-jk627@acs@advertise@alsoܶ:andzare@between@clear@;common@*correct@Sdetailed@each@\existing@general@ 33   33f 33>cand change righthand "Peer Stack" to "Peer2 Stack"cLThe names of the two stacks should be changed to reflect their "peer" statusd288g2256 2006/05/14Ia5.1.3nS5.1.5ܡ5.1.6ܢ/5.1.7ܣ5.1.85.2 ۪ܤܥܦܧܱ015.3ۭܨ35.3.1۫۬ۮۯ۰,ܩܪ˃24565.3.2!۱۲۳۴̃789:݂Z95.4"=5.4.1.1۵ܫ5.4.1.35.4.1.4ݍ5.4.2.3ݎ5.4.3#۶۷۸۹ۺۻܬܭ̓;<>?@ݏݐۃ-.5.5$ۼܮ΃AB݃5.5.2 5.5.325.5.4۽۾CX5.5.5ۿσDEFY5.6ЃG/0WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWGb\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.d360g2243vARefer to doc: 21-06-0675 Change to structure of table w.r.t having references in Representation column seems acceptable. Investigate using 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 (whicBh operator 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/07/20 2006/04/28MarkedA bANew text: 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 primitives for setting (write) and retrieving (Read) the values of the configuration parameters that drive the functional behavior of the local MIH Function instance. These values are MIB variables that belong to the MIH class and can be set and retrieved through a typical network management systemcAiInclude the MIH_NMS_SAP in the Media Independent SAPs section. replace the current text: 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. id233g2242 2006/07/20 2006/04/28EPeretzFFeder^ Editorial_31`46bndard should defines the packet format....47cportion~W>WportsWposWܩWܯW2W Wposition6WpositioningWpossibilitywWhWpossibleۈWW:W@W|WWWWWW W%W:WWWWޕWpossiblyKWWܡWpotential\WW@WpotentiallyܩWWpowerWWpowerfulWpppW݋Wpre-defined_WbWܿWpre-establishment\WpredefinedޖWpredictive^WWpredictiveeventspredictiveeventsexpressthelikelihoodoVpreferredlinkidentifݮWWpreferredpoaidentifiݮWWpreferredpoaidentifiisnotneededifitispartofpreferreݮVVprefixZWWpreparationۅWW@W@W@WW@W@WݮVVprefixZWWpreparationۅWW@W@WWWWukneeds۳WWܹWݓWneitherWnetW1W3Wnetwork/WWW WܼW+Wnetworks/W۾WWWnformationWnmsWno۴WWWWݴWWPWQWnoneedtodefineanidfortransactionidasitisinthefVnoproposedcorrectcallflowthistimeQVnospecifictextproposalPVnodeWdWnodesWݓWnon-3gpp۾WnorWnormative۴WWoWnormativedoesnotmeanmandatoryinfactschemasupportisoVnot#W/W0WAWYW_WbWjWkWmWnWoWzW{W|W}W~WہWW|WWWW|WܸWݴWݻW-WdWjWonZWjWkWmWnWoWzW{W|WWݴWoneZW\WonlyZW\WWCWW+WoperationsaWoptionܬWoptionalWOWoptionsWoraWjWkWmWnWoWuWzW{W|W}W|WWdW bAThis 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    33cThis command is sent by current MIHF entity to target MIHF entity to allow for resource query and handover preparation. Change the term cutrrentd305g2249 2006/07/20 2006/04/28EPeretzFFeder^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 2006/07/20 2006/04/28ved. No such examples in the Appendix2d242g2244 2006/05/14?ctarget\WۇWW"W$W*WtarnsportWtcm>Wtcp/ipwWtear-WWWteardownޗWtechnicalnWtechniquejWkWmWnWoWzW{W|W}W~WہWtechniquesWtechnlogiesWtechnolgy*WtechnologicalWtechnologies$WېWWWYW[WWWWWWW WBWW6WWWWWWWWWWWtechnology-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-W2Wctheinclusionofmihnetworkaddressinformationprimitivei:V;V<V=V>VtheinformationcanbeobtianedeitherbytlvorschemahoweܬVtheinformationrepositorycanbepresentlocallyatthemobZVtheinformationtransferoccursreadsbetterۨVtheinterfacesegmihsapexposedbymihfarenottechnolog0Vthejustificationforack-rspbitisinsufficientyVthekeyprimitivesdefinedaspartofmihsaparedescribedی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 8sanjeev% 33y  33 33fit is "Additional Parameters" c3Why is it additional parameters instead of Value? d445g2457 2006/05/14+EDasFSubir ^Technical, Binding_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#WAWiWjWkWmWnWuWzW{W}WWW|WܬWWݾWݿWvW}WހWށWނWރWމWschemaeWschemaecanbeusedtomapouttypesofdataandtheirVschemeܰ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.1mihlinksapshouldberemovedentirely6VcZcissoft-handoverlimitedtohandoverbetweenhomogeneousacc1VisgenertedW1V1V\ ,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)bdefineAWNWےW۔W۟WWWW+WAWBWYWhWsWܦWܬWWWWWWWJW݁WݴWWWUWVWdefineanextensibilityprocedureVdefineandmakedefinitionsinsection6.3.4.1.4and6.3.2cAVdefineandmakedefinitionsinsection6.3.4.2.1and6.3.2cBVdefineaporbasestationidentifierfor3gpp/3gpp2VdefineiflinkeventsareenvisonedtobeusedformiphandoJVJV1b06UWYW0626-00-000W0x00000001ܚW0x00000002ܚW0x00000100$W0x1fffffff$W1W!WJWjWmWuWۂWۉWەWWW=WHWRWSWTWUWVWWWXWYW\WcWuW|WܖWܯWܴW%WyWzW݁WݒWݗW W,WVW^WmWpWށWރWޔW0W1W4W6W:W1addtableofcontentsassectiontitleV1addthefollowinglinesSV1changethetypeofthenetworkaddressinformationV1createanewiewiththefollowinginformationatline38=V1dividetheflowintotwoinafigurelocalandremotecommyV1dividetheflowintotwoinafigurelocalandremoteinfozV1eitherremoveorprovidedetailsexpeciallyonall4primimV1failureܖV1ieeestd802.111999editioniso/iec8802-111999informatpV1mihgetstatuslrnetworkclientgetthestatusoflinksޔVޔVoobandresponsebydocumenturlorversionnumberonlyVandroutingconfigurationinformationraVi zbA1. Divide the flow into two in a figure; local and remote information service flow. 2. Correct the primitive type according to the direction of the service primitive. - MIH_Get_Info.response => MIH_Get_Info.confirm (From MIHF to MIHF User) 3. Change the name of "Information Server" to "Remote MIHF User (Information Server)" The detail flow will be shown in 21-06-0xxx-00-0000-Information_Flow.pptcLike command service flow in section 6.2.4, the information service flow is confusing as the local and remote information flow are mixed.d472g3918vEShould be accepted as per contribution 641 from Eunah in June Ad Hoc.wAccepted 2006/07/20 2006-04-30Marked224-3018zEEunahFKimGMember^Technical, Non-binding_62a6.3.9bory from client's perspective, does that mean they can all be igoned?d254g3208 2006/05/14yEEunahFKimGMembered?d254g3208 2006/05/14yEEunahFKimGMember48`22aAnnex B1 cisOWPWSWYWZW[W\W]WbWcWdWeWgWhWjWkWmWqWsWtWuWzW{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.boctetsW%W&W(W)WFWHWTWUWVWWWXWcWwWWݗWݙWWuW1WoduWoeratorݙ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`WcWdWhWiWjWkWlWmWqWsWvWwWyWzW{W|W~W܀W܄W܅W܌W܍W܎WܘW%battributesZW]WiWaudioۖWWauthenticated#Wauthenticating#WauthenticationWavailabilityAWWWavailable#W.WAWۂWۘWW#WHWnWܡWܢWܺW|W݊WWWWW!W%WavialableܶWbۀWYWsW0WWbrelaysVbackRWWbackbone+Wbandwidth݊WbaseWbased WAWOWQWpWWTWUWVWWWXWcWܳWܽW0WbasicAWWbasicallyWW0WbasicAWWbasicallyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWIbtypeAWJWLW[W\W_WjWmWۂWۉWېWWWW=WKWLWYW\WkWmW|W܄W܍WܗWܚWWWWWyWzW|WݴWݺWWW]WaWbWcWtWWހWނWބWޅWފWޕW0W1W4W6W<Wtypedescriptionlengthvalue1Vtypedesctiptionlengthvalueހ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-btoW 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ܿWWWWWW3 cd603g3253vAdd the missing parameter.wAccepted-Modified 2006/07/20EVivekFGuptaGMember^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/07/20on Identifier helps to correctly identify the remote MIHF entity;d579g3259iMathieu PeressejA!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.! 2006/07/19EVivekFGuptaGMember^Technical, Binding_87`23a 7.4.7.1.2 the data so they match an agreed schema (this doesn't mean you have to send XMialbaddanewsection7.3.1calledlinkeventidRVaddanewsectionassuggestedin21-06-606-00-0000locinfoܗVaddanewtablecalledscanrequestinfocontainingthefollowmV;}baddmoredetailtothecostiedefinition@addrefertotable26inannex4inthecommentsfield@aaddtexttosupportmulticast/broascastofinformationoncl@addtwogroupstokeepconsistentwithtable6@addedladding@*adoptsuggestedchangein21-06-0xxx-linkidentifierdoc@~agreed@8also@Fan@*analyze@tifierdoc@~agreed@8also@Fan@*analyze@ogous@logous@*analogous@o@Fan@*analogous@also@Fan@*analogous@*analogous@*analogous@rcmacmobilenodeݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݰWݱWWWWWWWWWWmacmobilenodeandlinkidentifiershouldbereplacedwithoneݦVmacmobilenodeandmacnewpoaarenotneedediftheyarepartVVmacmobilenodeandmacnewpoashouldbereplacedwithoneunifݞVݣVݤVVVVmacmobilenodeandmacoldpoashouldbereplacedwithoneunifݝVmacmobilenodeisnotneededifitispartofnewlinkidentifiݰVݱVmacmobilenodelinktypeandmacnewpoashouldbereplacedwitݠVmacmobilenodelinkidentifierandmacnewpoashouldbereplaceݜVmacmobilenodeshouldbereplacedwithlinkidentifertlvݟVݡVݢVVVmacmobilenodeshouldbereplacedwithlinkidentifierVVmacnewpoaݜWݞWݠWݣWݤWݯWWWWWWmacnewpoaisnotneededifitispartofnewlinkidentifierݯVmacoldpoaݝWoݸ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 2006/07/20 2006/04/28ݹE YoshihiroFOhbaGMember^ Editorial_118`5a8.4b"the Length", "definite"c"theLength", "defiite" d765g2430 2006/07/20 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/07/20 2006/04/28ݻE YoshihiroFOhbaGMember^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.1ݞd7.3.11.3Q7.3.12.1ݟ7.3.12.3R7.3.137.3.13.1ݠf7.3.13.2?7.3.13.3S7.3.147.3.14.1Hݡ7.3.14.2ޖ7.3.14.3T7.3.15.1ݢ7.3.15.3U7.3.16.1ݣ7.3.16.3V7.3.1747.3.17.1ݤ7.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.4y7.3.5z7.3.7a7.3.7.2F7.3.7.3M37.3.8ۃ{7.3.8.2G_7.3.9܃7.3.9.1ݜ7.3.9.3O7.4ܐ7.4.1ۊ7.4.1.1.2gh07.4.1.2[7.4.1.2.2ݥ7.4.1.2.3J7.4.1017.4.10.1.2ۂۋݬ7.4.10.1.3ݭ7.4.10.2.2ݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮݮt(ݿ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 2006/07/20 2006/04/28E 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.d819g2410v should be defined.d774g2374 2006/05/14 2006/04/28Table 20ݼE YoshihiroFOhbaGMember^Technical, Binding_124`50a8.4.2.11b*Replace NetworkTypes with Link Identifier.|{bsuggestedsuggestedmacnewpoaidWsuggestednewlinkidenۂsuggestednewlinklistۋWsuggestednewpoaidentۂtۂnۂnۂnۂnۂnۂWWWWWZcreponse>WJWreport_WbWېWWW|WވWޖW5Wreporting*Wreports_WbWܿWݏWrepositoryWZWrepresentFWܗWWWrepresentationہW=WAWBWܷWWWWWWWWWWrepresented/W0W1W2W3W4W5W6W7W8W9W@WzW{WܬWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW:W;W<W=W>W_WaW޸W޹W޺W޻W޼WrequestingW\WtCcSession Identifier is missing.d827g2390von request of commenterwRejected 2006/07/20 2006/04/28E 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/07/20 2006/04/28E 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/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_131`51a8.5.2.8b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccRMacMobileNode and MacNewPoA are not needed if they are part of Link Identifer TLV.d833g2364vby comment 527/626w Superceded 2006/07/20ng..ctherearetwomihgetinforesponseinthisflowchart=VtherearetwomobilenodedefinitionsVVtherearetwomobilenodedefinitionsthedefinitiononlineۦVthereisnodefinitiononhowthelistofeventsiscreatedcVthereisnodescriptionofthisfigureandwhysuddenlyweiVthereisnoinformationtowheretheconfigurationparameterjVthereisnomechanismtoaskforaspecificlocation/interesܘVisnomechanismtoaskforaspecificlocation/interesܘVܘV$bcu"Link Type" (Network Identifier) parameter is required for MIH users to determine which link is generating this eventd828g2243vby comment 824w Superceded 2006/07/20 2006/04/26cESrinivasF 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/07/20 2006/04/26 clinkidentifierismissingintheparametersݪVݫVlinkparameterschangeindicationcanonlybegeneratedwhenޖVlinkparameterschangeshouldberenamedlinkparametersrepVwcisWWWWWWWWWWWWWWW WWWWWWWWW!W"W$W%W'W*W+W,W.W2W3W6W7W;W>WAWDWEWFWGWHWJWKWOWSWVWXWYW\W]W^W_W`WaWbWcWdWfWgWlWnWoWpWqWvW|W}W~WWބWޅWއWވWމWގWޏWޖWޗW3W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW cA!The line: "the 802.21 standard shall specify the means by which QoS information may be obtained for each of the supported access networks and be made available to the upper layers involved in handover decision making." Imply such text exists in the document, and it is not at this LB 1!d93g2223i Qiaobing XiejOTYPE_IE_QOS information element is defined in LB 1 (line 46, page 45, Table 6).mRejectedwDeferred 2006/07/20 2006/04/28 EPeretz FFeder^Technical, Binding_14`40a5.1.8ba5.1.8bσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσ΃σσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσσ0YhcsuggestednewpoaidentisnotneededifitispartofsuggesteݬVVsuggestion݂WsuggestsۋWW=WsuitableۈWۋWWWWsuitedWsummarize:Wsummary>WsupeflousWsuperfluous۹WWWWWNW^WsuperfluousphraseVsuperfluoussegment۹VVNVsuperfluoussentence^VsuperfluouswordVsuperfluouswordsVsupervisionޓWsuppervisonޓWsuppervisonsupervisionޓVsupplyۋWsupportBW\WہWWWRWYWcWeWܩWWWWWWSWWWWWWWWecmacroWmade-WܢWWmainWNWmainly۽WmaintainedWmaintainingWmaintainingtwoformatscomplicatesmessagestructuresandVmaintains۳Wmajor|Wmake(W)W۔W۰WWWWW WW W&W'WUW5W9W>Wmakeindefinitearticleformconsistent۰VmakesfW:W݂W݈WWmaking*WۅWۆWܳWܴWݏWWmanageWmanagedWWWWWWܴWݏWWmanageWmanagedWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW2]ca "service continuity" is defined but it is not clear what "transparent" service continuity means.d11 2006/07/20EFarrokhFKhatibiGMember^Technical (was Editorial)_2`38a1.2bATChange "If applicable, the new SAPs shall be recommended as amendments to the respective media specific technology standard specification." to "If applicable, the new SAPs and associated primitives may be recommended as amendments to the respective media-specific technology standards bodies." Make similar changes throughout the document. TcA="shall" does not make sense in this context. The word should only be used to indicate a mandatory requirement to the entity claiming compliance with the standard. It should not be used as a requirement on people, standards bodies, etc. Included "associated primitives", since SAPs alone will not accomplish the goal.=d14 2006/07/18GMember^Technical, Binding_3`42a1.2bRemove "technology-independent"cent"c>`‚a7`fۡIUܩۃݼm‚b[ۆې">A\,ݰŃPfލ‚c+ۈۗ $Dn˃ك|ݜ‚d;=TۛރQܖރ!' ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,cto"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ܸWܽWܾWWWq dÃ`ݹÃpÃwÃxÃÃà jÃ0ފÃ@ݺÃPݻÃ`ދÃpyÃzÃތÃÃ{à Ã0|Ã@zÃP܂Ã`kÃp]Ã^Ã`ÃÃލà }Ã0lÃ@ÃPmÃ`~ÃpJÃÃÃݼÃnà ܀Ã0Ã@ގÃPoÃ`ÃpހÃ܁ÃpÃݽÃ{à ށÃ0|Ã@ނÃPރÃ`}ÃpݾÃ~ÃݿÃÃà \Ã0ۈÃ@)ÃPaÃ`ÃpޕÃÃbÃÃcà Ã0eÃ@ÃPÃ`܃ÃpÃÃÃ܄Ãà 6Ã0Ã@܅ÃPÃ`7ÃpۇÃ܆Ã8ÃÃ9à *Ã0Ã@܇ÃP>Ã`qÃpÃÃޏÃÃބà ޅÃ0Ã@ÃPrÃ`OÃpPÃ+ÃQÃۏÃà ކÃ0-Ã@ÃPޗÃ`ÃpcadoptݵWkWadoptmihregistrationkVadopted>WadvanceۅWadvantagesWPWadvertise+WadvertisementW$WޏWadvicedܖWadvisoryxWaffectܳWafterۅWۇWۮWfWWLWWWݿWWWW>Wagain+WWagainst݃WPWagent"W%WޏWagnosticܭWܰWagreedܕWaidWWݶWaimingܗWair۽W+WairportWaksingWal݆W݆W݆W݆W݆W݆W݆W݆WQcsmallWWsoۄWۅWۇWۊWۋWېWWWWW|WWfWޔW:WsocketsWsoft-handover1WsoftenOWsoftenstaticastonottoimplylimitationOVsole۶Wsole۶W۶WsoftenstaticastonottoimplylimitationOVsole۶W۶Wole۶W۶W$bandWW W!W"W#W'W-W.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ݴWݸWWWWWWWWWWWW WWWWWWW W|{GMember^ Editorial_84`44a7.4.4b*".....are described in the section below."cgThe last two words of the last line need to be interchanged: ".....are described in the below section."d590g2224 2006/07/20- 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.z}E Ulises OlveraGMember^ Editorial_83a7.4.6b"MIH Get Status"c Need to correct "MIH Get Sttaus"d574g2225 2006/07/20E Ulises OlveraGMember^ Editorial_92`45a7.4.9b"PoA"c Change "POA"d630g2226 2006/07/20E 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 2006/07/20E 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 2006/07/20E 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'."E Ulises OlveraijbsuccessUW\WܖW~WsuccessfulxWVWXWsuccessfullyޕWsuchW W#W'WAWDW_WsW۶WWWYW\WܬWܾWQW݊WWWiWsufficient#WAWsuggestۗWۜWW&WVWsuggesttodeletethissentenceVsuggestusingadditionallyinsteadofalternativelyۗVsuggestedZW]WܗWܘWܙW}WݒWݓWݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWݨWݩWݪWݫWݬWݮWݯWݰWݱWݻWWWWWWWWWWDWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢWݢW{|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 2006/07/2018E 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."d747g2232 2006/07/20E Ulises Olvera^ Editorial_129`18a8.5b"...in the sections below."cInterchange "below sections."d820g2235 2006/07/20E Ulises Olvera^ Editorial_141`6a Annex A-1bept reserved. When not used, all the bits of this field are to be set to '0'."3.3.1bl"This field is intentionally kept reserved. When not used, all the bits of this field are to be set to '0'."^ 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'."E Ulises Olvera*8badoptsuggestedchangein21-06-0xxx-linkidentifierdocݝVݞVݟVݠVݡVݢVݣVݤVݦVݧVݨVݩVݪVݫVݬVݮVݯVݰVݱVݻVVVVVVVVVadoptedWadoptionܪWadvancedWadvertise+WadvertisementNW$WޏWadvi WafterW-WۮWWWW`WfWܺW4W5WHWMW2Wagent"W%WޏWaggregates*WagnosticAWAWWagent"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} 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" witthe bits of this field are to be set to '0'."E Ulises Olvera8p#EQiaobingFXieGMember^ Editorial_22`2a5.4.3bAChange 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>c 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>cd, and should as suggested below. lnclinkdetectonlyindicateswhatisinthebraodcastorstatefVlinkdetectedindicationthedetectionmaybeeventhrought?VlinkdownaddothercausesauthenticationfailurebillingfabVlinkeventderegisterconfirmshouldbelinkeventderegistezVlinkeventregisterconfirmshouldbelinkeventregisterreyVlinkhandovercompletecommandcanbeusedforupperlayert4VlinkhandoverimminentmayVsedforupperlayert4VlinkhandoverimminentmayVVsedforupperlayert4VlinkhandoverimminentmayVVsedforupperlayert4VlinkhandoverimminentmayVVsedforupperlayert4VlinkhandoverimminentmayVV9)*w Superceded 2006/07/20as Editorial)_105`62a 7.4.14.2.2 b and visited network in Section 3. Then the text should consistently use the word roaming. Or: Introduce the concept of visited and home networks, when describing roaming aspects on in 5.3.2, before the terms are used. In some cases (intra-roaming, page 15 line 41 section 5.2), another word like handover should be used. cDiscussion of Logical Network Reference Model uses roaming concepts without introducing them. These are: Home Network, Visited Network. Roaming. d130 2006/07/17EGregFDaleyGMember^Technical (was Editorial)_105`62a 7.4.14.2.2 bo the example in Comment #444. mRejected 2006/05/14 2006/04/27EHongFChengGMember^Technical, Binding_38`3a6.1.6nstead of operators. c.3fcnmsEWBWW8WmWnoW+W-W?W@W_WaWpWuWvWۅWۇW۾WWWWWWWWWW W>W?WDWEWMW\WcWjWܐWܓWܖWܘWܙWܚWWWWWWW WW W2W:WCWeW}W݂WݥWWWWW WWWWW2WXWYWfWgWmWnodetaildescriptionandusageofthemihnmssapprimitivemVnoformatforthesynchinformationisdefinednorareanyrVnoguidanceindraftonhowthemediaindependentinformatio}VVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVmVsponseܙVnospaceforexpansionofmihtlvencodingsVnodeWWۉWۏWۦW W.W3W4WܝWܡW+WwW{W|WݏWW"W#W$WZWW:WW+WTWnon-3gppXWAIE 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 2006/07/20E Ulises Olvera^ Editorial_32`31a5.8.2rces." 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 2006/05/14E 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 2006/05/14E Ulises Olvera^ Editorial_32`31a5.8.2."230 2006/05/011v ldÃpސÃÃޑÃÃޒà ܈Ã0܉Ã@܊ÃP܋Ã`sÃp܌ÃÃޓÃRÃܚà ܍Ã0ۀÃ@tÃPÃ`uÃpÃvÃoÃہÃމà wÃ0ۉÃ@8ÃP9Ã`:Ãp;Ã<Ã=Ã>Ã?à @Ã0AÃ@BÃPCÃ`DDDoes the AP get Link Tear Down or Handover complete indications before it is disassociated? ItcspacesWWspans۪Wsparql{W|W}W~WqW~WspecW'WuWwWWۀWܸWspecial:Wspecially Wspecifedݽ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߶WwxcthelengthdoesnotmatchthetlvrepresentationofsectionAVBVthelengthencodingwhenvaluefieldisgreaterthan128isXVthelengthfieldisimproperfortherequestthereisnoaddMVthelengthoftheisquerytypelistissettovariablebut|VthelineVthelinkdetectedismissingfromthelistofprimitivesSVthelinklayerparametersdefinedheremustnotbeexamples`VthelistofparametertypeneedstobecompletelydefinedbyYVthelistofsap'sisnotcompletesincelsapandcssapareDVthemappingisnotfullybespecifiedintable24p145EVthemayrespectingusewiththesidisnotmeaningfulhowisVthemeaningoforasystemisunclear;VthemihcommandconfirmisaddingnovaluesamecanbedoneVthemihconfigurerequestisusedtocontrolthebehaviorofkVthemiheventregisterandmiheventderegisterrefertotheeVthemihfunctionheaderconsistsofatwopartsonewithfix 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 2006/07/206E 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 2006/07/20E 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-0648wAccepted 2006/07/20Marked5 E Ulises Olvera^Technical, Binding_30a5.6.1."d290g2249 2006/05/14E Ulises OlveraXbChange the text for this item accordingly to reflect that the indication of transmission is about the higher layer PDU instead of link layer SDU.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-Modified 2006/07/20 2006/04/272EGregFDaleyGMember^Technical (was Editorial)_18`20a5.3.2bcal, Binding_15`61a5.3, Binding_140`140a Annex A-1crfcW:WrightWWݿWrncWroaming_WaWۻWW݂Wrole:W;W<W=W>Wroles>Wrollback܃WrolledWWWWWWWWWWWWWWWWWWWWWWWWWWWWWteWrouterW: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ީWWWIWE Ulises Olvera^Technical, Binding_36a 6.1.3 & 6.2.2buMention that the flows are logical since readers can think thats the actual flow when acually it is the logical flow. that wll use them.cAThe previous sub-sections talk about the modifications that need to be done to the entities in question. This section is similarly supposed to talk about the adjustments that are needed to be done for the upper layers. This is not apparent and the section only provides a possible problem such as delay and packet loss and does not explain the amendments that need be done in order to provide 802.21 servicesd248g2258 2006/07/17E Ulises Olvera^Technical, Binding_36a 6.1.3 & 6.2.2buMention that the flows are logical since readers can think thats the actual flow when acually it is the logical flow.ding_36a 6.1.3 & 6.2.2buMention that the flows are logical since readers can think thats the actual flow when acually it is the logical flow.E Ulises OlverabIShould 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 12d212g2257v:Add section 5.6.1.5 and 5.6.1.6 explaining CS_SAP and LSAPwDeferred 2006/07/20MarkedE Ulises Olvera^Technical, Binding_32`55a5.8.3bShoudl explain what ammendments need be done in order to allow the delivery of the required services to the upper layers that wll use them.cAThe previous sub-sections talk about the modifications that need to be done to the entities in question. This section is similarly supposed to talk about the adjustments that are needed to be done for the upper layers. This is not apparent and the section only provides a possible problem such as delay and packet loss and does not explain the amendments that need be done in order to provide 802.21 servicesd248g2258v+Section 5.8.3 is deleted as per Comment 247w Supercededs OlveracofWWWWWWWWWWWW W WWWWWWW!W"W$W%W&W'W*W,W-W/W0W4W5W6W7W;W<W>W?WDWEWFWGWHWIWNWPWXWYWfWiWmWoWqWtWvW}WWމWޔWޖWޗW1W4W5W5W5W5W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[W[Wf@ݸE YoshihiroFOhbaGMember^ Editorial_115`60a8.3.3.2a8.3.3.1b-Remove Number of Address Header Identifiers .c3Number of Address Header Identifiers is not needed.d745g2386 2006/07/20 2006/04/28Table 18ݸE YoshihiroFOhbaGMember^ Editorial_115`60a8.3.3.2ing_115`30a8.3.3.1b-Remove Number of Address Header Identifiers .c3Number of Address Header Identifiers is not needed.d745g2386 2006/07/20 2006/04/28Table 18ݸE YoshihiroFOhbaGMember^ Editorial_115`60a8.3.3.2hnical, Binding_115`30a8.3.3.1b-Remove Number of Address Header Identifiers .c3Number of Address Header Identifiers is not needed.d745g2386 2006/07/20 2006/04/28Table 18ݸE YoshihiroFOhbaGMember^ Editorial_115`60a8.3.3.2rs .c3Number of Address Header Identifiers is not needed.d745g2386 2006/05/14 2006/04/28Table 18ݸE YoshihiroFOhbaGMember^ Editorial_115`60a8.3.3.2_Identifier.doc *ޖbA7.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 *cALink_Parameters_Change.Indication can only be generated when a link layer parameter crosses a configured threshold as defined in the current draft: "This notification is generated when a link layer parameter crosses a configured threshold." But, MIH_Link_Parameters_Report.Indication: "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."g2219 2006/05/14 2006/04/30ޖEVidalFAlbertGMember^ Editorial_78`48a7.3.14.2blSupport | Mobility management Protocol List (4) |beachWXWZW]W_WpWuWW@WYWeWzW{W|WSWoW݃WݙWWWW2WWދWތWearlierWeconomical9WeditionpWeffectVWېWۻW\WeffectiveuWefficientAWeitherWWW,WhWiWkWnWۙWۛWWWWW#W%W&W3WVWXWqWܩWW3W;WWW"W$W%W-WmW}WކWއWޖWޗW5WeitherdeletethisfigureorprovidetheupportingtextVeitherdiscussthismoredetailsordeletethiseventVeitherexplaintheunlabeledtableorremoveithVeitherintable6itshouldbe2octetsorthistableshould&VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVGnbl2#WrWWRWSWqW܌WܭW+W3W݃WW1W3WfWl2'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ۄWdalay|Wdash۱W8WrWdashes۝WdataWWWWW:WWWWW>W}WdatarateVdatabase۳Wdatabases:WdatagramWdcd|WdealjWkWmWnWoWzW{W|W}W~WہWۈWdealsW*WdealtWdecideۋWWWdecidedWW W2WdecisionfWܤWܳWܴWݏWݐWW.WdecisionsۅWۆWWWdecodeVWXWdecodersWdecription܄WdedicatedWdeepWfWdefault:WdefiitevWWݹWEkcdraftۃWۄWۆWۈWPWnWܥWܧWܱWWUWYW{W}W~W݂W݃WSWޕWޖWޗW4Wdraw?WdriveriWdropWdue:WWduplicate4W܉W܍W W Wduplicatedefinitionofmobilenode4Vduplicateentryhandovercomplete܉Vduplicatenumber10܍VduplicatedیWWduplicationwWduplicationofthemobilenodedefinitionwVdurationWduring|WWdynamicWWݏWWdynamicallyWe#W_WaWiWۈW۪WWWWWWZWwWWWWWWWWWWWWW0WBWCW\WWWW"W$W%W~WސW8W>W@WegegސVerewordline43usinganmihcompleterequestsideVe-core۽We-utra۽WۄWW@WCWzW{WܸW:W~WWWWWpWearlierpWvWxWeWearlyܫWbtaWܯWܳWWܳWܳWcchangedۂWېWZWWW<W?W3WchangesWWW>WchangingWchannelWW܋WݏWchannelidshouldbebetterdefinedaddasspecifiedbytheVchapter\WcharacteristicsiWWWcharacters-WWchargeWchart=Wcharts@Wcheck4Wcircle-WWcircularۥWciteWcivic-address-elemenvWcivic-location-inforvWclaimingWclarificationWclarifiediW1WmWWݏWPWclarifyZWcWWWW+WclarifyuppersVVclarityۧW$W>Wclarityconciseness$VclassesWWWWWassifiedWclauses(W*Wclear!W-WۆWۈW۾WW WW$W.WsWܳWܷWܸWܹWܾWܿWWWWWWWWWW W W W WWWW!WWWWޟWޫWWWWW?WKW}W߉Wb݋E YoshihiroFOhbaGMemberork for handover with the assistance of the network in executing handover procedures. Handover policy is in the mobile itself but gets the available QoS, bandwidth information from the network node. * Network-controlled handover (pure) A network entity instructs the network or mobile for handover with no mobile assistance. Anchor MSC can get the information from Target MSC about the available bandwidth, SIP server or QoS server finds out the available bandwidth in C*the local network and then controls the handover. Handover policy is in the network. * Mobile-controlled handover (pure) A mobile node instructs itself and the corresponding node for handover with no network assistance e.g., peer-to-peer networks, ad hoc. May not be suitable for the operators. "cjDo we need to define what network initiated, network controlled, mobile initiated, mobile controlled are? d47g2419 2006/07/18 2006/04/28݋E YoshihiroFOhbaGMemberbincludeHWIWpWWnWܩWܳWܵWܶWܹWܼWܽWܿWWWW>WIWWW7WnWincludeadescriptonforfollowingentriesintable-7ܹVincludealegendforfigure19bsapbstnetcܵVincludeamentionoftheseevenifistostatethattheyareVincludeatimebasedstatediagramshowingdifferentlinklaܳVincludeclientlocationasanessentialinputparameterinaܽVincludecontribution0626-00-000linkgetparametersdocVincludedescriptionofcasewhereinformationrepositorymayܶVincludeexamplesofiereportsandclarifyhowtousethemfܿVincludeguidelinesonratelimitationandtimeradaptationfVincluderecommendationsfortransportoptionseitherinthisܩVincluderulesontheinclusionoftheseidentifiersVincludespecificexamplesofallieslistedintable-6thisܼVdlcmodeۂWWOWmodel!W$W۽WW"W:WAWFW݂W݃W>WXWYWއWmodificationsWmodifiedށWރW5Wmodify;W4W5Wmodifythecurrenttextthissapdefinestheinterfacebetwe4V5VmoduleܤWݐW.WAWmore_WwWۆW۳WWWWW-W:WܓWܗWܸWܼWܿWWWWWWWWWW݂WݏWݽWWW WW>WEWFWGWHWWWXWYW6W9WmorecallflowsshouldbeaddedtoshowhowmihprotocolisV9W9W9Wa   !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ހށނރބޅކއވމފދތލގޏސޑޒޓޔޕޖޗ݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃݃ hcACommands 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@Af  33*  9  33Z  i  33fd151g2231wAccepted 2006/07/20 2006/04/28 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 d519g2219 2006/06/18EGregFDaleyGMember^Technical (was Editorial)_18`48a5.3.2bo change to include 802.11 (which also may have this case in a (visited) enterprise environment). c2393 2006/05/14 2006/04/28Table 6ݖcaddasectionfortheexamplehandoverscenariosbetween802DVaddaspaceformaybetomakeittwowordsthisisintableVaddstocommandsinthelinethatquoteslinkcommandorigiVaddstosystemsin3gppsystemalreadybroadcastVaddthefollowingtextbeforetheintroductionoffigure11 VaddtheinthefollowinglineinthissectionareprovidediVheinthefollowinglineinthissectionareprovidediVVW[WadditionalەW W*WMWtWܓW݄WݸWadditionalieisneededundergeneraliealsothereisnone Vadditionally:W\Waddress:W;W<W=W>WۈWەWWWWWWWWW W%WݍWݷWaddressedWaddressesܰWWWW WݏWaddswWadequatenWadequatelyەWadjectiveeWadjustmentsWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWWObEParkFSoohongGMember^Technical, Binding_62`16a6.3.2cCPlease refer to the #21-06-0601-00-0000_PoA_IPAddress_Configurationd480g2243wDeferred 2006/07/20 2006/04/207entence "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.d604g2268 2006/07/19EParkFSoohongGMember^Technical, Binding_62`16a6.3.2cCPlease refer to the #21-06-0601-00-0000_PoA_IPAddress_Configurationd480g2243wDeferred 2006/07/19 2006/04/207be found in Table 4 or 5 on page 41 (MIH or Link Commands)d612g2264 2006/05/14E Ulises OlveraGMember^Technical, Binding_113`29a8.3.2bShould define the values for these IDs in the Annex A-4 for example with the other available values or directly where mentionedY^technicalbindingVVVV V V VVVVVVV!V"V#V%V'V(V)V*V,V-V.V/V0V1V2V3V4V5V6V7V8V9V;V<V=V>V?V@VAVBVCVDVEVFVGVHVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhVmVoVrVsVtVvVxVyVzV{V|V}V~VVހVށVނVރVބVޅVމVލVގVޏVޔVVVRVޔVޔVJVޔVޔVGVޔVޔVޔVޔVޔVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV;cthetermgenericsapisconfusingsinceinline47itthensVthetextintherepresentationcellisadescriptionnotasVthetextofthissectionmakesalotofhypothesishowinfor݂Vthetextsaysnonewprimitivesorprotocolsneedtobedefi۾Vthetextthisparameterspecifiesthelistofcommandsthat{Vthethreecriterionstatedinthenormativetextforselecti-VthetidisactuallyinthefixedheaderVthetransactionidisalreadydefinedinthefixedheaderpauVselecti-VthetidisactuallyinthefixedheaderVVselecti-V-VvFWcthetwostacksinthefigureareidentical@thewordingislooseandlargelyrepeatingwhathasbeensai@then@therearetwomihgetinforesponseinthisflowchart@lthereisnoneedtodefinenewtermshorizontalhandoverand@thereby@they@thisO9thisisalinklayerindicationwhichshouldonlybereceive@ thisneedtobere-writtenasaproperreference@ thisretrievalmechanismusingpre-definedreportsoffersli@those@time@Dtlvs@to@uޖ8e3elvs@to@uޔ3evs@to@uޔ3eime@Dtlvs@to@uޔ2eto@uހ2e2eDtlvs@to@uܸހ1e%typo@iunfamiliaracronym@unlabeled@Heutralenoughtoincor@EbpRemove 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/07/20 2006/04/284EParkFSoohongGMember^Technical, Binding_62`16a6.3.2cCPlease refer to the #21-06-0601-00-0000_PoA_IPAddress_Configurationd480g2243 2006/05/14 2006/04/207but cannot be found in Table 4 or 5 on page 41 (MIH or Link Commands)d612g2264 2006/05/14E Ulises OlveraGMember^Technical, Binding_113`29a8.3.2bShould define the values for these IDs in the Annex A-4 for example with the other available values or directly where mentionedUcexplainusageofthewordmediaۖVVexplained7WexplainingWexplanationWexplanatoryWexplcitlyWexplicitlyW W,WLWMWexposedW0WexpressWexpressedZW]Wexpressions\W]WextendۋWextensibilityWWextractܺWextraneous:WextremelyWWexytensibilityܸWfWfa:WޕWfa-coaޕWfacilitateۅWۆWܤW@WݐWiW8Wfacilitatefurtheroninthesentenceconweyshelp@VfacilitatedWfacilitiesۢWfacilitiesistoogeneralۢVfactWWfailۂWfailed܄WWfailsZW]WeWfailureۄWWbWfastjWfeatureiWfeaturesWfew|W>W|W|W|W|W|W|WIS ^bindingWWWW W W WWWWWWW!W"W#W%W'W(W)W*W,W-W.W/W0W1W2W3W4W5W6W7W8W9W;W<W=W>W?W@WAWBWCWDWEWFWGWHWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWmWoWrWsWtWvWxWyWzW{W|W}W~WWހWށWނWރWބWޅWމWލWގWޏWޔWVWRWޔWޔWJWޔWޔWGWޔWޔWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#brewriteXWYWrewritethesectionandfocusmoreonhow3gppnetworkscanXVrewritethesectionandfocusmoreonhow3gpp2networkscanYVrfcW:WWrfc4889WrfcsۑWrighthand<W?WroamingWܷW9WrollbackRWۉWRW܃WrollbackactionthreshۉWrolledRWrootbWrouter"W$W%WޏW4WrouteradvertisementisencapsulatedޏVroutersWWroutingOWPWWrowܓWrows7WrrcCWrregisteruWWrWrttW WrtxJWrulesWWWWWފWrxlevncellFWGWHWIWIWIWWIWIWIWIW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!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݃WZWshowinformationrepositoryatthemnaswellZVshowingܪWܳWWshown7WyWzW݃WW>WܪWܳWWshown7WyWzW݃WW>W>WbEMathieuFPERESSEGObserver^Technical, Non-binding_33`1a6b: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.d251{l) none needed 2006/07/20 2006/04/30 EMathieuFPERESSEGObserver^ 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 2006/07/20 2006/04/30EMathieuFPERESSEGObserver^ Editorial_86`64a 7.4.5.1.1b4replace by "this primitive is used by upper layers" c)typo: "this primitive is used by uppers" d601g2249 2006/07/20 2006/04/30EMathieuFPERESSEGObserver^Technical, Non-binding]cforce-Wchannelrangeiethevalueoflowandhighdoesforce-W-WlrangeiethevalueoflowandhighdoesVforce-W-WlrangeiethevalueoflowandhighdoesVforce-W-Wl24 EPeretzFFeder^Technical, Non-binding_3`60bA Performance matrix of other network elements are typically reported by the MN themselves. The sentence should change to say: This information typically originates at different layers of the protocol stack within the MN and sometime reported by other network elements. @A>  33    33>cxThis information typically originates at different layers of the protocol stack within the MN or other network elements.d21g2222wRejected 2006/07/20 2006/04/28ific (sockets....)d706g2243iJin LeejDelete figure 24ksuperceded by 697m Supercededw Superceded 2006/05/22 2006/04/3024 the MIH will transport MIH message. This is clearly implementation specific (sockets....)d706g2243iJin LeejDelete figure 24ksuperceded by 697m Supercededw Superceded 2006/05/22 2006/04/3024 ical, Non-bindingnedeEQiaobingFXieGMember^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]  cThe 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 2006/07/20 2006/04/24fEQiaobingFXieGMember^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.@.d565g2312 2006/05/14 2006/04/24dKcvalueforversionisnotdefinedVVvalue-addܢWvalues_WaWxW|WܖWܚWW~WWW3W6Wvaluse6WvariableW%W=WMW|WWݳWW'WtWvariables~WvariousW'WWaW݂WvarySWverbW/Wversa6WversionېWWW݁WVWޗWvertical?W@W:W;W:Wvery_WwW WܸWܾWWWviaܬWWW8Wviable۳Wvice6WviewIWܤWݐWW8Wviable۳Wvice6WviewIWܤWݐWݐWice6WviewIWܤWݐWݐWݐWݐWݐ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'XulisesolveraVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVvidalޔޕޖޗvivekܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃwolfgangܑܒܓܔܕܖܗܘܙܚxiaoyu:;<=>?@ABCDyanۇWۈWyanpengjunxiangguoۇVۈVyewlWmWnWoWݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σyuanۅۆbshouldbereplacedbyasinglestackwiththeentitystack9V=Vshouldbereplacedbyvalueorprovidesupportingtextwhyi*Vshouldbereplacedwithnetworkselectorformallydefinedon.Vshoulddefinethevaluesfortheseidsintheannexa-4forVshouldincludeadefinitionorexplanationforconsistencyaVshouldmakeclearifnetworksrefertoaccesstechnologiesVshouldrewordthisandsaythatduringregistrationtheuserVuringregistrationtheuserVV|corderۅWۆWWHWRWYWWtW{WݴWWW"WlWorderingWWݴWordinary:WoriginalWoriginate7W8WܫWWoriginatesWoriginationIWosi>Wosi-service>Wosi-service-procedur>Wosi-service-user>WotېWotheruWۂWۊWېWWWWWWW'W1WCWZWWWWWWWWbW݂WWWWW"W#W$WWWXWYWޔWޕW7W>WothersWWޕWothersisnotappropriateintherepresentationcolumnVpEPeretzFFeder^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 cdifferent layers of the protocol stack within the MN and sometime reported by other network elements. @A>  33    33>cxThis information typically originates at different layers of the protocol stack within the MN or other network elements.d21g2222 2006/07/18 2006/04/28EPeretzFFeder^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 how the MIH will transport MIH message. This is clearly implementation specific (sockets....)d706g2243 2006/05/14 2006/04/3024EPeretzFFeder^Technical, Non-binding_3`60b18a8.2.1bRemove the sentence.EMathieuFPERESSEGObserver64a 7.4.5.1.1 |xbAf 33  33 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/01^ 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 2006/07/20E 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 2006/07/20E 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 2006/07/20E Ulises Olvera^ Editorial_44`54a6.3.2bc"may be" "For each (Link Type and Operator) combination the following information may be provided"ce..."d290g2249 2006/05/14E Ulises Olveray0vconfigurationWconfiguregWaWconfirm/request/respJWconfusionܗWconjunctionWconnectionsTW۵WconnectivitySWconsensusݓWconsider݊WconsiderationRWconsideredWconsistencyۓWcontainerZWcontextܾWcontribZWWCWcontrib21-06-0674ZVcontrib21-06-0675Vcontribution0WBWDWZWۂWۊW۽WW%WFWWWWEW`WzWWWW+W>WKWPWYWiW:Wcontribution21-06-0633ۂVd706g2243 2006/05/14 2006/04/3024EPeretzFFeder^Technical, Non-binding_3`60bwith how the MIH will transport MIH message. This is clearly implementation specific (sockets....)d706g2243 2006/05/14 2006/04/3024EPeretzFFeder^Technical, Non-binding_3`60bEGObserver^Technical, Non-binding_111`18a8.2.1bRemove the sentence.EMathieuFPERESSEGObserver[ xUbAUse 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 2006/07/20 VENada, Golmie, Member^Technical, Binding_70`21b70`21bB; TcA> 33  33>he MN themselves. The sentence should change to say: This information typically originates at different layers of the protocol stack within the MN and sometime reported by other network elements. @A>  33    33>+lEPeretzFFeder^ 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 2006/07/20 2006/04/28EPeretzFFeder^ Editorial_22`31bAlMIIS provides the ability to access this information about all heterogeneous networks in a geographical areal@A>  33#  33)  33>cenced165g2232i Subir DaskPl. see Comment # 162m Superceded 2006/07/17 2006/04/28EPeretzFFeder^ 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@abaddtexttosupportmulticast/broascastofinformationonclܻVaddtheammendmentsassuggestedin21-06-606-00-0000locinܘVaddtheexampleassuggestedin21-06-606-00-0000locinfooܙVaddthefollowingintheannexa4atthebeginningܚVaddthefollowingparagrpahinsteadVaddthefollowingtableRVaddthefollowingtext݊Vaddthefollowingtextimmidiatelyaftertheheadingandbef2Vaddthefollowingtextinsection8.5VaddthemissingparameteradddescriptionforoldlinkidentifVaddthesectionsasdescribedindcn21-06-0622-00-0000LVMVaddthem݋Vaddtotable6\VaddtothesentenceorfromaninternallymaintainedmiisdaVorfromaninternallymaintainedmiisdaVVothesentenceorfromaninternallymaintainedmiisdaVVallymaintainedmiisdaVVenceorfromaninternallymaintainedmiisdaVVaddedAWZW]WWWW}WWW޿WM4cable-WCWmWܶWCWOWmWWmWmWabilityWable-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$WDcprotocols۾WZWܴWWCWޕWprototypeaWBEPeretzFFeder^Technical, Binding_22`60bLreplace 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.&mRejectedvAssigned to teamwDeferred 2006/07/20 2006/04/28 EPeretzFFeder^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 d190g2236wDeferred 2006/07/20 2006/04/28Marked EPeretzFFeder^Technical, Binding_26`1a5.5.218 2006/04/28 r via R4j@c
Ã'Ã'ܭÃ(ݐÃ( ۹Ã(0.Ã(@Ã(P?Ã(`ۺÃ(p@Ã($Ã(Ã(ۻÃ)ܮÃ) AÃ)0ۼÃ)@Ã)PBÃ)`Ã)pÃ)݃Ã)݄Ã)Ã* Ã* Ã*0 Ã*@2Ã*PXÃ*`۽Ã*p۾Ã*CÃ*Ã*FÃ1YÃ1 DÃ10 Ã1@Ã1PۿÃ1`EÃ1pÃ1Ã1 Ã1 clink6WGWHWKWWWaWbWcWdWfWrWsWyWzW{WކWޕWޖWޗW3W4W5W6W<W?W@WlinkcommandindicationshouldbelinkcommandrequestsVlinkconditionsanddifferentaccessnetworksinneighboringVlinkconfigurethresholdsaddsinrinadditiontosignalstrVlinkconfigurethresholdscommandislinkcommandthatgoes3V3V3V6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WcationshouldbelinkcommandrequestsVlinkconditionsanddifferentaccessnetworksinneighboringV)VbvideoۖWWviewܤWvisited۲WWW9W:Wvisitednetworkinsection3thenthetextshouldVvisited/home:Wvisiting۲WvpnAWwܯWܳWw/oWWw3qW~Ww3cqWw3crecommendationsparqlquerylanguageforrdfhttpwwww3qVwaitۑWwaituntilthereferencedi-dstobecomerfcsۑVwant݂WwantskWnW}WwasۉWVWXW܌WwayAWۈWܢW݊WweۇWۈWW WweproposetoaddanienewmacaddresstotellthemihfoftaۇVweproposetospecifythewayfordealingwithmihcapabilitۈVwell WAWiWpWsW۶WWܷWܸWWZWwereWwether܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁W܁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ہWۡWWWYW&W'WW5W2W>WctowardsVcableۖWWcahngeWcahngetodefiniteVWWW5W2W>WctowardsVcableۖWWW8 ހ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 containedwxbonly-W.WWWWZW܁W݂W݃WWW>WonpropertywWontoWonwardsWopcodeܒWݶWoperation"WWW8WoperationalWoperationsfW}WoperatorZW]WWW"WܷWܾWݕWݙWWWoperatornameݕVoperator-nameUWYWݕWoperatorsZW[W]W_WW@W݊WݙWopposedۖWWWoptimalumuWoptimumAWoption_WWoptimalumuWoptimumAWoption_W_WAWAWWWWWWWWWWWWWWWWWWWWWWWWWWWWWEPeretzFFeder^ Editorial_32`41a5.8.2bAfin this standard, in order to access 3GPP services provideds through existing 3GPP SAPs. This does notf@AR  33:  ;  <  33Rcein this standard, in order to access 3GPP services provides through existing 3GPP SAPs. This does notd246g2245 2006/07/20 2006/04/28EPeretzFFeder^ 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 2006/07/20 2006/04/28EPeretzFFeder^Technical, Non-binding_39`21bal, Non-binding_39`21b removed. No such examples in the Appendix2d242g2244 2006/05/14pchighWܬWhigherWWܤWWWWWݏWݐW7WhighlightingWhighlyjWkWmWnWoWzW{W|W}W~WہW WhindersWhindersdeploymentonlytomorepowerfulnodesVhinting݂Whnadover܀WhoIWW@Who-typeWhomeW:WhomogeneousW1Whop-by-hopWR ZbArA number of commands have been added provided to allow the upper layers to configure, control, and get informationr@Af  33  33$  33%  -  33fcA number of commands have been added to allow the upper layers to configure, control, and get information Commands have not be added but rather introduced and providedd286g2247 2006/07/20 2006/04/28EPeretzFFeder_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/07/20 2006/04/28EPeretzFFeder^Technical, Binding_41`36a6.2.5.1bFeder^Technical, Non-binding_39`21bal, Non-binding_39`21b removed. No such examples in the Appendix2d242g2244 2006/05/14) !bAThis 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 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/07/204ctextneedsimprovement VtextneedsimprovementalotofdiscussionisspeculativeinAVtextsaysafterauthenticationandassociationtoacertainVsaysafterauthenticationandassociationtoacertainVV/dÃ2/Ã2 GÃ20Ã2@0Ã2PWÃ2`Ã2pÃ2Ã2Ã21Ã32Ã3 %Ã303Ã3@4Ã3P5Ã3`HÃ3pܯÃ3ܰÃ3&Ã3'Ã46Ã4 7Ã408Ã4@Ã4P(Ã4`Ã4pÃ4Ã4Ã4nÃ5)Ã5 *Ã50Ã5@Ã5PÃ5`Ã5pÃ5+Ã5Ã5Ã6{Ã6 Ã60,Ã6@IÃ6PxÃ6`ܱÃ6p9Ã6Ã6:Ã6ܲÃ7Ã7 Ã70ݑÃ7@;Ã7P7Ã7`Ã7p<Ã7rÃ7Ã7Ã8Ã8 Ã80ܳÃ8@ݒÃ8PÃ8`Ã8pJÃ8-Ã8Ã8.Ã9NÃ9 Ã90Ã9@Ã9P=Ã9`Ã9pÃ9>Ã9?Ã9sÃ:Ã: 8Ã:0yÃ:@Ã:PÃ:`9Ã:pÃ:KÃ:܏Ã:ܴÃAÃA ÃA0ÃA@ޔÃAP/ÃA`ÃApÃA:ÃAÃA;ÃBܵÃB @ÃB0}ÃB@LÃBPAÃB`?ÃBp:ÃBÃB@ÃBÃCÃC Hbplace۞W(Wplaced Wplacement WplacesWfWplane3W4W5WpleaseWpleasenumberthereferencesandupdatecrossreferencingVpoaAW\WۂWۇW#W܍WܾWWkW|WWWW"W#W$W%W~WޕW1W8WpoamaximumdatarateVpoa'sWpoa-address~Wpoas?WAWpoint,WAW۴WWSW3WIWpoints*W?W۬WWܨWܪWܯWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWXWcWpossibilitiesWpossibility۳WpossiblewW۸WWYW=WoW7WpossiblyܡWW)W݂WpotentialOWPWsWWWpotentiallyWFKbnetwork-assisted݊Wnetwork-controlled݊Wnetwork-layerܡWassisted݊Wnetwork-controlled݊W݊W)bnode@znot@Fnote@InotificationPnotifications@obtained@xoccur@octets@^ofܜ:*ofsparqlqueryresultwhenthistlvis@offered@once@only@optional@options@or9order@originate@noriginator@outside@pair@paragraph@parametersۂ;parametertype@payload@performance@Hplace@policy@power@pre-defined@primitives@Qprior@dprogressed@@primitives@Qprior@dprogressed@mitives@Qprior@dprogressed@dprogressed@primitives@Qprior@dprogressed@sed@b>Remove until Appenidx inlcudes such handover command scenarioscThe use cases and handover scenarios for the commands defined in this section are provided in Appendix. Currently not specified in the Appendixd300g2251 2006/07/20EPeretzFFeder^Technical, Binding_46`9bA`Data Rat:e The minimum and maximum value of data rate supported by the link layer of a given PoA`@A>  33  33  33>cData Rate: The minimum and maximum value of data rate supported by the link layer of a given PoA Minimum makes no sense and provided no value for HO criteria, removed379g2252i Vivek GuptajThe 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/07/20 2006/04/28 EPeretzFFeder^Technical, Binding_52`54PeretzV\\bstandard WsWvWwWەWWWWW݂WWW1W3W4W5WstandardsW&W?WstartOWVWۉW WstartedۉWstarting܍WWWWstate,WWܳWW WIWstated,WstatementW WWstatesSWstaticWWstationWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWUcaddedۊWW0WܸWWFW݋WW1W8WaddingۂWۅWۊWWWadditionuWWWWWYWܶWW[WadditionalەW W*WMWtWܓW݄WݸW<Wadditionalieisneededundergeneraliealsothereisnone Vadditionally:W\Waddress:W;W<W=W>WۈWەWWWWWWWWW W%WݍWݷW"W#W$W%WjWaddressedWaddressesܰWWWW WݏWaddswWaddtion6WadequatenWW WݏWaddswWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWatenWadequatelyەWadjectiveeWadjustmentsWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWWcmeanIWZWWWWWCWxWdWfWmeaningeWWݍW;Wmeaningful_WaWWmeaninglessW\WmeansۄW۸WܟWܢWWWW!WWWmeantޏWmeasurementWmechanism_WaWbWܘWWW W W W<Wmechanisms_WܛWܦWWW3WWmechansimWmedia'W(W)WDWېWۖWWWIWܠWܢWܤWܰWܺWWWWWWWW}WݐWWWW1W6W8WOWWWnW1W>WmediaindependentsapsܰV1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1WTcbeacon8Wwiththemdeiadependentandmediaindependentbeacon8W8W ctoWWWW 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 npvS4EPeretzFFeder^Technical, Binding_66`10a 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. 2006/07/18 2006/04/28EPeretzFFeder^Technical, Binding_66`10_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. 2006/07/18 2006/04/28EPeretzFFeder^Technical, Binding_66`10ion is max data rated430g2253 2006/05/14 2006/04/28EPeretzbieee802.11.WJWWieee802.16JWWieee802.21pWies?WAWZW]W_WbWfW W!W$WܷWܸWܹWܺWܻWܼWܽWietfۓWWܹWWietfinformationelementsfor802.21V802.21VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVs cbAchange 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 2006/07/20 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 2006/07/20 2006/04/24ezvENada, 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."@A  33  33  339  33@ 33l  33v 33  33 33cA_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 2006/07/20wENada, Golmie, Member^ Editorial_118`24b 2006/05/14 2006/04/28EPeretzFFeder^Technical, Binding_66`10c\Change MIH Event Register/DeRegister to MIH Event Commands These are commands and not Eventd492g2256 2006/05/14 2006/04/2814EPeretzetzT[j?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/07/20 2006/04/2813 EEleanorFHepworthGMember^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 IDsvby 516w Superceded 2006/07/20 2006/04/28 EEleanorFHepworthGMember^Technical, Binding_74`1a7.3.91a7.3.91a7.3.9Binding_49`1a6.3.4d388 xbcA%Syntax error in "values rae assigned"%@A> 33  33 33>d768g2309 2006/07/20yENada, 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@A> 33)  335 33>d776g2310 2006/07/20zENada, 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."@ ^ZdichengWܼWܾW Wdas#W0WXWYW\W]W_WbWbWbWہ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{bvProvide 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/07/20 2006/04/2853S<Eqd44g2409 2006/07/20rEKenichiFTaniuchi^Technical, Binding_36a6.1.4bAMIH_Event_Register.confirm response Link_Event_Register.confirm response MIH_Event_Deregister.confirm response Link_Event_Deregister.confirm response@A  33   $ 338  ? I 33^  e o 33   cAMIH_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 GuptasEKenichiFTaniuchi^Technical, Binding_40a6.2.4bALink_Command.indication request@@ence is old, and should as suggested below. g$o band,W-W1W2W3W4W5W7W8W:W<W>W?WDWNWPWXWYWiWjWpWyWzW{W}WWދWތWޏW2W7W7W7W7W2W2WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW8bsupportedcommandlistۊWېW0supportedeventlistۊWېW0supportedisquerytypeۊWbWݥW[W0supportedisquerytypelistsetofsupportedlistofsupported0Vsupporting*WWsupportspWuWWWTWcW3WsupposedkWnW}Wsuppotedisquerytypel0Wsure1WswitchWswitching?WVWsynchWsynchronouspWܲWsyntaxWHW WWWWsystemۇWۖW+WWW8W;Wsystem-localpWsystemparameters|WsystemsWtemparameters|WsystemsWWW|W|W|W|W|W|W|W|W|Wbremotely-W_Wremove W!W+W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>W@WBWEW[W^WaWgWhWoWyWzW{W|W}W~WۀWہWۙWۣWۤWۥWۧWۨW۬W۹WWWWWWWWWWWWW+W3W4W7W=W@WIWPWQW[W`WqWuW܉WܓWW@WIWPWQW[W`WqWuWuWuWuWuWuWuWuWuWt ۊ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 ( F cthisretrievalmechanismusingpre-definedreportsofferslibVthissectiondoesnotactuallyexplainwhatthisschemaisrVthissectionisaboutdesignthegoalofmiisnotneedtota#VthissectionofondemandmihcapabilitydiscoveryneedstoPVthissectionshoulddescribeallmediaspecificsapsshowniVthissectionshoulddiscussidentifierscarriedinvariableݳVthissentenceiscircularۥVthisstatementmakingtheinter-mediadifferencesfullytran*VthistableisconfusingtheuseofforloopdoesnotaidundVthistechnicalspecificationspecifiesthemediaindependentnVtechnicalspecificationspecifiesthemediaindependentnVnVtechnicalspecificationspecifiesthemediaindependentnVnVtableisconfusingtheuseofforloopdoesnotaidundVV  %bAThis primitive is used by a peer MIH Function to communicate with the MIH 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 target new PoA or the network entity, e.g, Access Router or Foreign Agent, depending on where the related information is available.@AR  33      33RcAThis primitive is used by a peer MIH Function to communicate with the MIH 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.d655g2264wAccepted 2006/07/20 2006/04/284/28p&^ 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 2006/07/20 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@n where the related information is available.d655g2264 2006/05/14 2006/04/28&EPeretzFFedervtoaWdWfWiWnWoWއWމWޕWtodayܗWtoo{Wtoward3Wtransaction۔WWtransactionsݓWtransparent*WtransportWtarviced757g2267i 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 Guptad format (= frames)d734g2266 2006/07/20 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 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.&EPeretzFFederitive is used by a peer MIH Function to communicate with the MIH 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 target new PoA or the network entity, e.g, Access Router or Foreign Agent, depending on where the related information is available.@AR  33      33RcAThis primitive is used by a peer MIH Function to communicate with the MIH 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.d655g2264 2006/07/19 2006/04/28&EPeretzFFedercprimitives/W0WEWۃWیW۾WPWRWSWZWeWnW܏WܐWܰWWW%WW>WBWgWhWjWmWޗWprimivie?Wprior#Wpriorities݂WprobablyېWproblem܏WWWproblematic۳WprocedureۊWW{W+W8Wprocedures{W@WprocessWܡW WWWprocessingW Wpropagated9WOWproperWܙWWproperlyWYW{WWpropertiesWproposalۂWޔW@WproposeۅW5WprotocoliW۪WWWW/WYWZWqWܯWܺWWWW WWDW{WWWW7W_W`W7WW7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W=,EAjayFRajkumarGMember^Technical, Binding_3a1.2 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"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. mRejected 2006/07/20 2006/04/28,EAjayFRajkumarGMember^Technical, Binding_3a1.2emand MIH capability discovery procedure.@A>  33A  y  33>c23g2268 2006/05/14 2006/04/28*EPeretzFFederEPeretzFFederCE 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/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_134`31a8.5.2.8b0Replace Network Identifier with Link Identifier.c-Network Identifier should be Link Identifier.d840g2372wAccepted 2006/07/20 2006/04/28E 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/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_135`45a8.5.3.12bRemove PreferredPoAIdentifiercNPreferredPoAIdentifier is not needed if it is part of PreferredLinkIdentifier.d844.ebthisprimitiveisgeneratedbymihfunctionwhenitneedstoLVthisprimitiveisissuedbyupperlayerstocontrollayerliVthisprimitiveisissuedbyupperlayerstodiscoverthestaVthisprimitiveisusedbyamihfunctionontheservingnetw!Vthisprimitiveisusedbyapeermihfunctiontocommunicate%Vthisprimitiveisusedbyastation'smihfunctionoranappއVbdiscoverAWLWSWuWWۈWۊWېWݥWW"W+W0WdiscovereduWdiscoveringWdiscoversuWdiscoverysWuWWۊWW+W+W[W8WdiscrepencyCWdiscussۓWWdiscusstheissuein21sendlstoietfforcommentifnecesۓVdiscussionDWdisparate*Wdispatched7Wdistinguish?WۓVۓVۓVۓVۓVEcdelivered\W|W"W$Wdelivering_WaWdeliversoWdemandۊW+WPWdenverW8Wdepecting!WdependېWdependence)WnWWWWWWWWWWWWWWWWdependentonearliercommentonsection7.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۰WWvWWcWdWeWformalisedWformatGWHWqWvWܑWWWWW~WWWW'Wformats%W;WformattedWWformerWformulation۸Wforward 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)WcinitiatorW Winlcude$WinputܽWinsecureW<Winsecureconveyspsychologicalstate<VinsertLWinsertrelevanttothemnafterintheareaLVinserted0W4WinstanceFWGWHWIWJW/W>W/W>W>W"W"W"W"W"W"W"W"W"W"W"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^/-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 Guptal 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..  2006/07/18 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 Gupta.EAjayFRajkumarGMember^Technical, Binding_22`40nical, Binding_22`40q hdÃvP$Ãv`%ÃvpݱÃvÃvoÃvއÃwiÃw Ãw0jÃw@ܘÃwPkÃw`lÃwp|ÃwmÃwވÃwܖÃxܕÃx nÃx0}Ãx@ÃxPNÃx`ܙÃxpoÃx~ÃxpÃxpÃyÃy Ãy0qÃy@eÃyPÃy`ÃypÃyqÃyÃyrÃzsÃz Ãz0Ãz@ÃzPtÃz`uÃzpfÃzÃzrÃzÃà ݲÃ0 Ã@vÃPwÃ`7ÃpÃێÃÃÃ&à gÃ0Ã@ÃP Ã` Ãp ÃݳÃxÃà à TTݴÃ@ÃPUÃ`ÃpݵÃÃ۔ÃsÃà Ã0Ã@ÃP'Ã`ܑÃpÃVÃ݁ÃyÃܒà Ã0+Ã@ݶÃPܓÃ`ݷÃptÃÃݸÃhÃà uÃ0Ã@ÃPÃ`ÃpܔÃ(Ã5Ã=Ãà vÃ0Ã@ÃPiÃ`^W,bTwo 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 Peressejn the text. ock 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. Sbwhy*WWWTWwifiWwildbWwillZW]WlWTWUWVWWWXWcWܤWyWzW݃WݑWW WwimaxܴWwiredsWsWsW/@bwish@RwithއJwithin@)words@c1.0@^127@20@43gpp@G4@55@7@8.5@802.21@sb802.3@FaW8afewconcernsregardingtable13@able@about@Mack@add@addasectionfortheexamplehandoverscenariosbetween802@added@adequately@adopt@walgorithm@all@also@alternative@among@an6analyze@and@2: |݃9>annex@a9>annex@a@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*W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WFWGWHWIWLWMWOWPWQWRWSWTWUWVWWWۅWۉWېW۵WW7WYWZW\WcWeWfWܢWWW݇WݍWݎWWWWW"W$W,W7W4WLWWWWWW"W,W7W4W4W4WdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWdWF8cupper@uppers@usage@Hused@Eusing@Tutmost@Kvalueforversionisnotdefined@needstobemodified@stobemodified@.2.23needstobemodified@ chave2W6W6W6W6W6W6W6W6W6W6W6W6W6W ۿESanjeevFAthalyeGMember^ Editorial_28`8-30a5.5.5bStretch diagram horizontallycDiagram needlessly compressedd204 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_28`55-57a5.5.5b5Remove middle sentence. Remove "in this case" at end.c^Intent of middle sentence is unclear and possibly misleading. These decisions are up to 3GPP2.d206vby comment 203w Superceded 2006/07/20MarkedESanjeevFAthalyeGMember^Technical, Binding_28a5.5.5b3Replace "PPP" with "Network Connectivity Protocol".c5Connectivity protocol is being migrated away from PPPd198wAccepted 2006/07/20Marked Figure 10ESanjeevFAthalyeGMember^Technical, Binding_30`6a5.6.2.1bAMove section 5.6.2.1 into the media-dependent SAP section (5.6.1)cInconsistent with section 5.5d216wAccepted 2006/07/20Markedent with what is on top of UMTS and GERAN)d195 2006/05/14Figure 9۾40 a>cDsued 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 afEter the remote peer has issued a .reponse primitive. For local exchanges, only .request/.confirm and .indication/.response pairs can be defined.Id287g2238i Eunah KimmAcceptedvZ=> Refer to 21-06-0641-01-0000-Command_service_flow.ppt Accepted as per contribution 641.wAccepted-Clarified 2006/07/20 2006/04/28Marked18 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 is"bsentencewWۥWۧW۪W۫W۶WۻWWWWW WWW3W7W@WIWQWܭWWWWW(W)W4W5WOWPWWW^WWWW;WޒW@WsentencesW0WއWseparateWWPWser#WserveNWxWserver\WiWlWW;W`WzW݊Wserves[Wservice#W*W?WAW_WiWpWۂWېW۳WW+W5W<WHWSW\WܘWܟWܬWW0WKWeWyWzW}W#W(WRWބW:W?WserviceprimitiveconceptualabstractiondescribingtheinfoܟVservice-infoHWservice-specific1WWWWWWWWWWWWWWWWWWWWTcbeTWZWfWhWmWrWsWtWvWxWyWzW{W|W~WހWށWނWރWވWފWދWތWލWޔWޖW0W1W1W1W1W1W1W1W0W0W0W0W0W0W0WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWO-wbtitleW!WrWtW`W:Wtitles\WtlvjWmWWW|WܕWܗWܘWܙWܚWݙWݴWݿWހWށWނWރWފWtlvencodingbutneithertheschemanoritsurlsneedstoVtlvtypevaluesshallbeuniquetlvtypevaluesraeareassiފ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ܕVTbaddfollowinginformationelementintable6informationele|VaddfurtherclarificationtothetextVaddgetstatusresponsesetV 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 '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 2006/07/20 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 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 Guptajcthemihlinksapisnotshowninfigure12andisnot6VthemihlinksapshouldbeshownonthisfigureitwillclarVthemihlinkupindicationincludesthefieldmobilitymanageޕVthemihonthenetworkmaybroadcast/multicastinformationcܻVthemihprimitivesdonotincludealinkidentifierthustheܐVthemihsapisnottechnology-independeforexamplethemih Vthemihfisnotashimlayerbutisafunctionitspansmult۪Vthemnmayusel2transportforexchangingmihinformationwܩVthenamelinkconfigureparametersresponseisnotappropria܂Vthenameofthesectiondoesnotmatchthenamedefinedint܁V}careaW=WIWLWSWWnWareasWWSWarfeWargumentsݥWarrives WarrowWarrowsvWarticle۰WݥWarrives WarrowWarrowsvWarticle۰W۰WݥWarrives WarrowWarrowsvWarticle۰W۰WarrowWarrowsvWarticle۰W۰Wma8.5.2.5aޕ8.5.2.5-128.5.2.6Ãb8.5.2.7ăce8.5.2.8Ń8.5.2.98.5.3.1168.5.3.128.5.3.137ۇ8.5.3.1588.5.3.1798.5.3.188.5.3.19>q8.5.3.20σޏ8.5.4.1ބ8.5.4.2ޅ8.68.6.1r8.6.1.1O88.6.1.2ۏPQaܚWDWa4ܚVa-1W-WWWWކWސWޑWޒWޗWa-2ޓWa2WsWannexۀWہWWWWW-WsWtWuWvWWWWoWwWކWމWސWޑWޒWޓWޗWDWannexaDVxaDVDVxaDVDVxaDVDVaDVDVWWWWWWWWWWWWWWWWWWWWWWWWWWWWd=cmovedKW`WqWmovementWmoving:WWmsbWmuch(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܂WWWnamesW<W>W?WnamespaceCWnasWnas-port-type=WݔWnasa>WnativeWnaturaljWkWmWnWoWzW{W|W}W~WہWnatureAWܖWxWnavigationWncms2WneWnearby(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*W}OvresolutioneWW7WeWDWresolveUWSWresolvedWresolvedbycontribution21-06-0692-00-0000-mVresourcesۅWrespective*WەWrespondingWrespondslWresponselW۔WWWރWresubmitDWretrievalZWretrievelWretrievedlWretrievingRWCd587g2225iMathieu PeressejAFrom the doc: "One would be that Link Event Registration is initiated when an MIH Function 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 afjESrinivasF Sreemanthula^Technical, Non-binding_86`48a7.4.14b^Request to reconsider the use cases for MIH network information and remove them if not needed.cAMIH Network Address Information request and response primitives seem to have the same functionality already defined for fast mobile-ip handover signaling. This may cause some redundancy in 802.21 definitions.@A  33d597g2227i Ronny Kimj;Maybe we need to clarify the section instead of removing. cal, Non-binding_86`48a7.4.14b^Request to reconsider the use cases for MIH network information and remove them if not needed.cAMIH Network Address Information request and response primitives seem to have the same functionality already defined for fast mobile-ip handover signaling. This may cause some redundancy in 802.21 definitions.@A  33d597g2227i Ronny Kimj;Maybe we need to clarify the section instead of removing. cont)chandovers;WܲWܴWݍWWXWYW:WhandoversduetothemobilenodemovementarefacilitatedbyVhandoverstatus6WhappenWhappensۑWWhard*WW?WhardwareWhas+WgWpWvWxWۄWۅWۉWېWۤWWWWW WWWW)W+W|WܕWWW W W:W[W݅WݍW>WEWFWGWHWLWMWXWYW1W5W>W@WhaveW_WbWuWېWWW'W+W-W7W:W=WCWܠWܶWܸWWWWW WW%W0WBW݃WWWWW"W$W0WgWhWjWjWWW"W"W"W"W"W"W"W"W"W"W"W"W,cifthemnrequestsdetailedinformationonaperiodicbasis9Vifthesentencefromtherecipient'sperspectivetheseeventxVifthetransactionidistobeuniqueitisimportanttoclesVetransactionidistobeuniqueitisimportanttoclesVsV*clinesܬWW]WWlink&W'WCWDWFWGWHWIWJWLWMWOWPWQWRWSWTWUWVWWWcWdWeWfWۄ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ݽWWWWWWWWWWWWWWWWWW W!W#WmccommentsuWWcommit/W0W3W5W8WۃW܏W6W@WAWcommnadWW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WWcommunicatesWcommunicatingTWcommunicationە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ݐVcomprehendedWPcforwarding:W W*WfounduWWWfragmentWfragmentationWWfragmentingWframeqWWWWWW<WframesW'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)W,WIWPWQWvW3W5W6W8Wfront2WfuctionۉWۉWLWW8W8W8W8W8W8WqF'bnetW1W3Wnetwork W!W"W#W,W:W;W=W?WAWUWVW\W_WiWpWuWWۂWۘWۧW۸WWWWWWW,W<W=W@WHWJWKWLW[W܅W܋WܡWܤWܬWܴWܾWWWW3W9W:W;WIWMWOWPWSWZW_WuW|W݃W݊WݺWWWWWWW WW!W"W#W$W%W+W.W7W8WAWOW]WjWޔWޕWWޕWޕWWޕWޕWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWAcbsWܵWWbsc+Wbssid[WbstnܵWbuffering Wbuildup9WbulletWbullet1needssomeclarificationVburdenWbusinessXWYWbusy݃Wbut%WDWEW_WaWiWۄWۈWېWۓW۪WWW:WZW\W|W܋WܖWܚWW۪WWW:WZW\W|W܋W܋W|W܋W܋W|W|WW\W|W|WS8EAjayFRajkumarGMember^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 2006/07/20 2006/04/2831`18a5.6.3bbility management plane (as part of the 802.16 instantiation of the MIH_LINK_SAP)."EMember^Technical, Binding_30`36a5.6.1 9EAjayFRajkumarGMember^Technical, Binding_34a6.1.1bInclude the MIH_NMS_SAP in the Media Independent SAPs section.d232g2242 2006/07/17 2006/04/289EAjayFRajkumarGMember^Technical, Binding_34a6.1.1bEAjayFRajkumarGMember^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).*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, with the "Entity Stack"c+The two stacks in the figure are identical.d284g2254 2006/05/14 2006/04/28Dޔ@bBDFޕbACޖ@bAcBޗcB0@2bBD1@ibB D2@3@cA4@bBcA5cA6bBcA7@c8cA9c:cA;v1iDbBiD0bBiDiDޗcB2cBޗcBޗcBޗcBލ@@@vzbAzy}bAAg~bAހbACEGgނbACEGIACgބbAgއbgދbAgޏbAgޔbACEDcAޕbBcAޖ@cBޗcBޚbAdޞbA)dޠcA(dޢb@d0ޥbAd#ިbAd-@k/61bA6c82@3bA<4bAwk5@/vA37bA8E9@:E = >cBD?@Bc@C@E@>cA4GGfHHI@`KcAMbOcAPcARGS@vA TcVdW@1X@3cA6YcA9Z@]@_@bcmmdwze@IgcicAj@kl@Qnc%o@Up@YbASqdrjcB 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-serviCce-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 is/28.zEKenichiFTaniuchi^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@AR 33  # . 33RcFLink_Event_Deregister.confirm should be Link_Event_Deregister.responsed514g2421vby comment 482w Superceded 2006/07/20Marked36 {EKenichiFTaniuchi^Technical, Binding_72a7.3.8bgister.confirm response Same change is needed at the table of contents, P71/L3, and P72/L21q@AR 33  # . 33RcFLink_Event_Deregister.confirm should be Link_Event_Deregister.responsed514g2421vby comment 482w Superceded 2006/07/05Marked36 {EKenichiFTaniuchi^Technical, Binding_72a7.3.8bTaniuchi^Technical, Binding_72a7.3.8bspecific to the OSI-service) to the request is/28v[[bthanܴWDWXWݗWPWthatW W,W-W.W?WAWHWIWLWMWRWTWWW\W_WdWfWjWmWۉWېWەW۫WWWWWWW W#W)W,W5W7WTWUWVWWWXW\WcWhWsWtWyWzW{W|W~WܕWܟWܤWWWWWW W)W+W.W3W9W;WIWPWUWYW_W|W݃W݊WݗWݸWWWWWWWWW%W2W8WWނWކWދWތW3WWތWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW ctexttextbetweenline43page43andline12page44isnotabouKVtextdoesnotreflectthedependencyofthetransportmechanVW#W#W#W#W#W#W#W#W#W#W#W#W#W#W#W@ ncnetworkfWjWޔWޗW8WAWBWCWnetworkdetectiondefinitionisredundant V V V V V V V V V V8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W,  WBWKWservice/sessionݓWservices۳W W{Wserving"W*WsessionWݓWUWsessionsݓWsetۆWێW:WshallZW=WOWshalls{Wshould0WZWW-WܗWW WzWSWTWshouldbeacceptedaspercontribution641fromeunahinjunzVshow0WshowingZWSWshown۴Wside݃WsignificantWsimilarWeWsince۵WܐWݴWsincemihfdoesnotreallymakeanypolicytypedecisionsit۵VsincewearenotaiminginthepresentstateonroutingforwݴVsingle*Wsip`W`WsomeܐWܗW;W{WݜWSWsomemihprimitivesmayrefertomultiplelinklayertechnolܐVsomethingۂWsparqlBWܗWspecificےWەWWWWWeWܗWܰWW0WSWspecifically݀WspecificationHWspecifiedlWWWW{WspecifyܾWWWWSW p_‚B&'()*Ãܯܰ҃678n‚C+܃݃‚D,ܱIx{‚Eܲ9:‚F7ݑރ;‚GăӃ?@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'Kbclass@gcollects@comma@common@Rconcept@lects@comma@common@Rconcept@Rconcept@common@Rconcept@mmon@Rconcept@omma@common@Rconcept@common@Rconcept@eaccurateclassificationscheme@common@Rconcept@common@Rconcept@ubmannerAWvWmany܊WܡWmapWmapped2WmappingDWVWXWmapsAWWmaskZWmatchWmaterialWWWWWWWWWWWWWWWWWWWWWWWWWW"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ېWWWW:WܰWWW0WJWtechnology-dependent Wtechnology-independe W0Wtell_WaWۈWtense7Wtenseconsistency7Vterm W,W.W:W;WW-WW]WterminalۂWۋWۏWOWQWޔW8WterminalsۋWPWterminology>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-W2W3W4W5W7WIW2W2W2W2W2W2W2W2W2Wctexttextneedsimprovement@texts@that@the@.\XFZNlK8 the802.21standardspecifiesthemeansforsecurityinforma@thecommandmihconfigurethresholdsshouldallowtodefine@thecurrentmihreferencemodelfor3gpptriestoshowhowm@thedecriptionisthesameastherequest@L%t'coWhich standard is this? Why only one IE example is provided? It may be good to have other IE example as well. d420g2454 2006/07/20(EDasFSubir ^Technical, Binding_51`42a 6.3.4.3.1b"Method length should be 2 Octets. cLMethod length (1 octet ) is not sufficient. Already 7 methods are assigned. d426g2455v(one octet can actually hold 255 values..wRejected 2006/07/209)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. d438g2456vGDelete bits 3 and 4. Length is not included as part of Table-6 anymore.wAccepted-Modified 2006/07/20*EDasFSubir ^Technical, Non-binding_55`20a6.3.6b[Should be replaced by "Value" or provide supporting text why it is "Additional Parameters" 1 2ތbAޏ^nސ@ޓGޓGސ@ސ@މ@cތbAކcމ@cތbAގ@ލ@@cފ@ފ@ފ@cފ@މcފ@ފ@ފ@nd functionality of MIH Function."[ESanjeevFAthalyeGMember^ Editorial_31`48a5.7.1b"Capitalize "Ethernet" consistentlyc Customary used238 2006/07/20ESanjeevFAthalyeGMember^ 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 2006/07/20ESanjeevFAthalyeGMember^Technical, Non-binding_37`29a6.1.8bDefine paging related eventsmessage from the remote MIHF to local MIHF as Event Deregistrationd270 2006/06/21ESanjeevFAthalyeGMember^Technical, Non-binding_37`29a6.1.8bDefine paging related eventsioncMRename the message from the remote MIHF to local MIHF as Event Deregistrationd270 2006/06/21ESanjeevFAthalyeGMember^Technical, Non-binding_37`29a6.1.8bDefine paging related eventsg. These decisions are up to 3GPP2.d206 2006/05/14nt"d182 2006/05/14,07bfunctionalW7W8WfunctionalityAWlW7W8WfunctionalityAWAWkljand"W?W@WBWZWWWWܾWW݄WݍWݻW,WvWށWމWansweredWany"WWapplications,WaquisitionݍWare۬WWWrWareaTWasWBWW|WܾWW W0WXWݻWrWށWasindicatedseveralitemsofthelistmustbeinterpretediܾVassociatedBWat݄W,WavaialbleWbase,WbasedBWbasicallyvWbasisBWbe/W?WBWuWWWܾWW W݄WݴW+WTWrWމWbecause,WbeingTWbelongs"Wbelongstoupperlayermobilitymanagement"Vbetter/WbetweenWTWbit|Wbound Wbut|W,WbyBWWWWvWމWc462WcanW W,WrWcannotgWމWcapabilityܾWcarefullyݴWcarriesWcasesWcertain WWchange@WWWWܼWXWݻWݻWݻWݻWݻWids WctherecipientoftheprimitiveisthemihfunctionwhichwillVtherecipientshouldbemihfunctionsincethisisalinkprfVthereferencemodelincludesamedia-dependentpartthemihAVthereferencepointsarenotusedanywhereinthedocumentt۬VtherelationshipormappingbetweenmihlinksapandmediadDVtherelevanceofannexbin802.21specisquestionableۀVtherelevantinformationismaxdatarateVonableۀVtherelevantinformationismaxdatarateVVonableۀVۀVtherelevanceofannexbin802.21specisquestionableۀVۀVtherelevanceofannexbin802.21specisquestionableۀVۀV{. hybAR 33  ! , 33Rictwomihcommandshassimilarfunctionsmihswitchandmihha@Vtxt>WtypeJW[W^W_WbW|W~WۂWۄWۊWےWWWWW:W=W>W?W@WCWKWLWRWYW|WܗWܼWܾWWWWWWWWWWW W W~W݃WݠWݺWWWWaWbWcWtWW<WtypeiepoacapabilitiesthesecurityandqoscapabilitiesoܾVtypes=W@WIWJWYWܤWWWWWWWhWݐWWIWtypicallyܤWܱWݐWWtypicallyinaheterogeneousnetworkݐVtypicallyinaheterogeneousnetworkcomposedofmultiplemeܤVgeneousnetworkcomposedofmultiplemeܤVܤVVczTo insure interoperability, the IEEE 802.21 must define how to decode the Set of Event IDs and their registration status. d509g2275wAccepted 2006/07/20 WENada, 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.  vent IDs in order to support interoperability between different Link Layers. d502g2270۪v^Delete the sentence. Mention MIHF is a logical entity as part of second sentence in paragraph.wAccepted-Modified 2006/07/20 ۫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 2006/07/20 ۬ESanjeevFAthalyeGMember^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 108w Superceded 2006/07/20 d d d nd just reference the above terms.wAccepted-Modified kDL) before transmission. " There is no need to exchange schema or URLs if the IS client is already configured with the schema required to make a query. The schema retrieval is needed only when the IS client is not configured with the schema. The schema retrieval does assist a device to know how to construct a query and process the query result, without necessarily changing the code that implements IS. " Personally, I think it's OK to have an XML schema, but it needs to be Econfigured offline or out-of-band, and it's highly confusing to see the concepts repeated in TLV and XML. This may mean that query syntax is extraneous and RDF/SPARQL/OWL aren't necessary. " XML and TLV are different in that TLV does not provide semantic query in a general way while XML/RDF does. Thus, having both TLV and XML as options covers wider scenarios ranging from devices with less functinality to devices with more functionality. 802.21 should allow b6!EPeretzFFeder^Technical, Binding_97`19bn 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 link9d649g2259 2006/07/19 2006/04/28!EPeretzFFeder^Technical, Binding_97`19bplaced with one unified LinkIdentifer TLV. d595g2351 2006/05/14 2006/04/282351 2006/05/14 2006/04/28BX:bmihlinkdetectedeventanewlinkisdetectedݛVtobeamihlinkdetectedeventanewlinkisdetectedݛVݛVtanewlinkisdetectedݛVݛVdetectedݛVݛVbasicurltobea~V~Vtaprefixmihbasicurltobea~V~VZ0crequestsiWmWܕWܗW9WrequestsetsWmWrequireWWiWrequired"WW)WWWW7WaWbWcWoWrequirementWWWrequirements۟WrequiresWrequiringWOW WrerenceUWYWreserve"Werve"W"WWYWYWYWYWNEcexcludingwWexclusiveܟWexcution@WexecuteېWuteېWېWecuteېWېWWbexpectedkWnW\W]W^W}WexplainhWWWWWexplainorreformatthechannelrangeinformationelementVexplainedW'WDWoW2WexplainingWexplainsW\WexplanationWexplanatoryܴWWWexplicitWexplicitlyW W,Wexplicitlyreserve128generaland127otherforfutureVexposed0WexpressWexpressions\WextendedAWiWkWnW{W}WݾWݿW}WހWށWނWރWextensibilityAWܸWWWextensible WWextensionsWextent_WextraWextratextisrequiredheretoclarifythepurposeandoperaVextract#Wt#W#Wtract#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_WYbfigure@`first@fix@flow@for@8forcing@Jleoctetlengthrepresentationshowthatfirst@Jcalmi@Jrstcommentthemihmightalsonotifythelocalmi@J)qbinformation@list@node@provide@referenced@removesections7.4.15.3.27.4.15.3.37.4.15.3.4@'replacesection5.5withcontribution21-06-0620-00-0000-ns@tretrieved@asplit@theymusteitherbemergedintooneoroneofthemberemove@thresholds@Utooneofthefollowingtypes@/wish@beremove@schemathisdoesn'tmeanyouhaveto@Utoanewvalueallocateanewoneorsplittheentry@/wired@candothertlvencodingsitisconceivablethatthese@destination@differences@6easily@Uifcomment9isacceptedtomodifythedefinitionsofhorizo@yimprovement@itisnotclearwhatisthedifferencebetweencommonandot@linkparametertypedefinitionsisinsufficientandneedsto@miheventderegisterhasnotbeenexplicitlymentioned@Wnot@overload@repeat@show@text@ vbycomment719thatdefinesmihfidVbycomment719whichdefinessessionidUVbycomment719whichexplainstheuniquenessaspectsofmihf Vbycomment737݁Vbycomment741ݶVbycomment752/756XVbycomment752/756andbycontribution21-05-0671-00-0000-8Vbycomment752/756bycontribution21-05-0671-00-0000-821-fFVbycomment803Vbycomment824bVcVbycomment892VVuVvVbycommentfromsection7adoptsimilarresolutionascommeneVbycomments287289292293294295andcontribution21-06-0KVbycomments482508514515267whichtakecareofconfirm/reJVbycomments493494RVbycommment527/626ݨVbycontributionfromeunahandcomments473474475477:V UE ShinkichiFIkedaGMember^Technical, Binding_113`55a8.3.2.2b#Define the term "session" properly.c!"Session ID" does not make sense.d724g4137i Qiaobing XiemAccepted 2006/05/146 .2l, Binding3WEStewartFSkomraGMember^Technical, Binding_30a5.6bMAdd MIH_LINK_SAP in the figure . Delete other SAPs which may not be required.cIn 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/07/20Marked12LINK_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/07/20Marked12hanged to "should" or the reason why the uniqueness is not needed should be described.ort for QoS is immature in the P802.21 standard draft 1.0.d90g2219 2006/05/14 2006/04/27TEShikichiFIkedaGMember^Technical, Binding_113`43a8.3.2.1bg"may" should be changed to "should" or the reason why the uniqueness is not needed should be described.6.1.2-0000sEFarrokhFKhatibiGMember^ Editorial_1`40a1.1bAdd a note: Unless 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"d3 2006/07/20EFarrokhFKhatibiGMember^ Editorial_1`51a1.2b:Please number the references and update cross referencing.cReferences are not numbered. d6 2006/07/20EFarrokhFKhatibiGMember^ Editorial_1`52a1.2b8"changes in radio conditions of serving and target link"c1Suggested rephrasing of "gaps in radio coverage" d8 2006/07/20EFarrokhFKhatibiGMember^ Editorial_2`15a1.2bRemove "transparent".in radio conditions of serving and target link"c1Suggested rephrasing of "gaps in radio coverage" d8 2006/05/14EFarrokhFKhatibiGMember^ Editorial_2`15a1.2bRemove "transparent". r16XEStewartFSkomraGMember^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. c relationship with other media specific SAPs to mkae the figure more clear. For 3GPP/3GPP2 technologies consider deleting MIH_3GLINK-SAPd214g3209 2006/06/2112XEStewartFSkomraGMember^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. cd214g3209 2006/05/1412 and it's relationship with other media specific SAPs to mkae the figure more clear. For 3GPP/3GPP2 technologies consider deleting MIH_3GLINK-SAPd214g3209 2006/05/1412r. For 3GPP/3GPP2 technologies consider deleting MIH_3GLINK-SAPd214g3209 2006/05/1412.2.1bg"may" should be changed to "should" or the reason why the uniqueness is not needed should be described.6.1.2-0000-csetsۆWWsettingWsetupܢWseveralۃWۉW۝WWWWseveraldashescanallberemovedwithoutlossofcontent۝VshallWvWwW WW{W|WW W WOWshalldoesnotmakesenseinthiscontextthewordshouldonVV}T|bchangeendofsentencetotoeffectseamlesshandoveracrossۻVchangefromeventservicetocommandservice(VossۻVۻVV39 XcAThe 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/07/20Marked9 YEStewartFSkomraGMember^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. cPP2 technologies consider deleting MIH_3GLINK-SAPd214g3209 2006/05/1412.2.1bg"may" should be changed to "should" or the reason why the uniqueness is not needed should be described.6.1.2ecwhereeWېWWWAWBWZWjWWWWWWW W%Wwhereas%W&WWEWFWGWHWwhereverܥWeas%W&WWEWFWGWHWwhereverܥWܥWeas%W&WWEWFWGWHWwhereverܥWܥWWHWwhereverܥWܥWcdiscoveredۊWWdiscoveringېWdiscoveryuWWۊWWݏWWW+WOWPW1W8WdiscoveryregistrationandeventregistrationmechanismsareVdiscussܯWݳWdiscussedDWpWvW+W<WdiscussionAWWW܏WWdiscussionofhow802.3networkscangetdirectinternetaccVdiscussionoflogicalnetworkreferencemodelusesroamingcVdispatchmWdispatched7WdistinctWdistinguishۊW:WܜW:WdistinguishedWdistributedWdo_WbWeWfWlWۈW۬WWCWܐWWWWWWW݊WWXWYW6W?Wdoweneedtodefinewhatnetworkinitiatednetworkcontroll݊VdocޔW<W@WޔWޔWޔWޔWޔWޔWޔWޔWޔWޔW6 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.21d200g3212v;as per contribution 21-06-0691-02-0000-3GPP-3GPP2AmendmentswAccepted 2006/07/20Marked10 us more on how 3GPP2 networks can handover to other non 3GPP2 networks with help of MIHF/802.21. c 2006/05/1412r. For 3GPP/3GPP2 technologies consider deleting MIH_3GLINK-SAPd214g3209 2006/05/1412.2.1bg"may" should be changed to "should" or the reason why the uniqueness is not needed should be described.6.1.2;BcmihgetinfoindicationshouldbemihgetinforequestxVndicationshouldbemihgetinforequestxVxVVmihgetinfoconfirmprimitiveisnotdefinedVVV:cmiheventregisterconfirmshouldbemiheventregisterresprVmiheventregisterhasnotbeenexplicitlymentionedLVmihfunctionshouldrejecttheregistrationifthemihuser.VmihgetinfoconfirmprimitiveisnotdefinedVterhasnotbeenexplicitlymentionedLVLV9 |bB-------------------------------------------------------- 3.7 | Type_IE_POA_SystemParameters | Information about the network | For 802.16 case, | Variable | | that are available | UCD, DCD, UIUC, DIUC | ---------------------------------------------------------------------------------------------------------------------------------------------------C------------------ Add following parameter to MIH_Handover_Prepare.response / MIH_Handover_Intitate.reponse ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Name | Type | Valid Range | Description ------------------------------------------------------01 .bA%Change text to: ... An example would be a query to retrieve a list of all events for IEEE802.11 defined interfaces only. 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.%@Af  33      y  )cfcA}MIH function should reject the registration if the MIH user tries to register for an unspported events or unavailable events.}@A  33d279g2256 2006/07/20 2006/04/24/EQiaobingFXieGMember^Technical, Binding_41`32a6.2.5.1bAwRemove "MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" from Table 4w@A  33cobingFXieGMember^Technical, Binding_37`36bingFXieGMember^Technical, Binding_37`3640t`‚V˃؃ݿ̃‚W 59σ܉?ݩݯσۃa‚XEۺ9fO[@‚YۖÃ{5Rc݈ݝ$4jkޖ‚Z:@ݠݫݴ*:ވmHbchangepointofattachmentstopointsofattachmentorpoa'sVepointofattachmentstopointsofattachmentorpoa'sVVfromthisprimitiveisissuedbyupperstkVkVep90line46fromthisprimitiveisissuedbyupperstkVkVp{cneighborIWݏWneighborhoodIWneighboring=WܡWWneighbors+WneighbourWnet-sapWnetlmmޕWnetman>Wnetowrk۴WnetscapejWkWmWnWoWzW{W|W}W~WہWnetworWnetwork!W:W;W<W=W>W\W_WaWjWkWmWnWoWzW{W|W}W~WہWۂWۇWۉWۊWۋW۴W۶W۸W۽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/W4W5WOWPWYW]WaWbWcWb$"3GPP systems already broadcast...."c:Add "s" to "systems" in "3GPP system already broadcast..."d243g2244 2006/07/20E 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/07/20E 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/07/20E Ulises Olvera^ Editorial_37`36a6.1.5.2b "IEEE 802.11"c$Separate "IEEE802.11" into two wordsd278g2247 2006/07/20E 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/07/20lvera hcenvironmentWenvisageWenvisonedJWequipoWequipmentWequivalentWlentWWvisonedJWequipoWequipmentWequivalentWWvisonedJWequipoWequipmentWequivalentWWk 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_132`8a8.5.2.9b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc8MacMobileNode should be replaced with LinkIdentifer TLV.d834g2365vby comment 527/626w Superceded 2006/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_132`29a8.5.2.10b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc8MacMobileNode should be replaced with LinkIdentifer TLV.d836g2366vby comment 527/626w Superceded 2006/07/20 2006/04/28MarkedE YoshihiroFOhbaGMember^Technical, Binding_132`41a8.5.2.11b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc- 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/07/20 2006/04/28cp <zbcASyntax 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 2006/07/20{ENada, Golmie, Member^ Editorial_119`48bAReplace "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 33d 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."@--------OE 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. cere 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.v see issue 35wDeferred 2006/07/20 E 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. ckMno need to define an ID for Transaction ID as it is in the fixed header part.v see issue 35wDeferred 2006/07/19 E 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. cctoinsureinteroperabilitytheieee802.21mustdefinehowt@mtotal@tree@tries@twomihcommandshassimilarfunctionsmihswitchandmihha@%typo@itypolengthod@wunderlying@unified@unlikely@Hunlikely@HHunderlying@unicast@unlabeled@Heled@H@wunderlying@unfamiliaracronym@unlabeled@H4tc3gpp۽W۾WWWW݂WWWXW>W3gppsystemalreadybroadcastinformationregardingotherraV3gpp/3gpp2WW3gpp2ۡWWWWWWW&W'WHW WYW3gpp2documentnumbershouldbeusedۡV3gpp2hrpdshouldbesupported'V3gpp2shouldbementioninthissectionaswellHV@ iAbDthe 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 nodeE\ 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.  @optimum link layer connectivity as well as availability of appropriate higher layer services to permit service and session contzfESrinivasF 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/07/20 2006/04/26gESrinivasF Sreemanthula^Technical, Binding_83`1a 7.4.1.1.2b*remove destination identifier parameter. layer or from L3 but we dont need to make a distinction between that.wRejected 2006/07/20 2006/04/26gESrinivasF Sreemanthula^Technical, Binding_83`1a 7.4.1.1.2b*remove destination identifier parameter. 8g2243 2006/05/14 2006/04/26cR) bwithއWފWޕW7W;W=W@WwiththelistofeventsthatmaybecarriedinamessageyVwiththenumberofparametersthatmaybeincludedinalist~V~V~V~V~VN cthelWmWnWqWvWWބWޅWކWފWދWތWގWޔWޕWޖWޗW1W2W4W5W6W7WSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWSWcthedecriptionisthesameastherequest܄VthedefinitionofeventidsaremissingitiscriticallyimpNVthedefinitionoftheparameterforsupportedisqueryismissdVthedefinitionsgivenforthemihhandoverxxxprimitivesin܏VthedefintionoftheinformationserviceschemaisanimplemVthedescriptionfieldreferstoprimitivesdefinedinthe21PVthedescriptionofisquerytypelistisnotcorrectVthedescriptionofthemesageisthesameastherequest܅Vthedescriptionoftypeielistofoperatorsismisleadingi@Vthedescriptionsofitems3and4areidenticaltheprimitivNVthediagramimpliesthatanynon-l2transportwillrundirecVthedifferencesbetweencoreheaderspecificiesandcore80$Vthediscoveryofmihfunctionentitiesatl3isoutsidetheVthedocumentprovidesnoalgorithmsforrttestimationtherVocumentprovidesnoalgorithmsforrttestimationtherVVpb4/W:WjWmW{W}WۉWەWW%W&W)W=WDWEWHWRWTWUWVWWWXWcW|WܒWܚWܮW݌WݙWݵWݾWW^W_W`WmWtWށWރWލWޔWޕW1W6W;W4cellularcdma2000^V4extendedschemacontentݾV4higherlayerservices;V;VݾVݾVݾVݾVݾVݾVݾVK ctheZWdWfWjWE YcAConsider 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 2006/07/20some redundancy in 802.21 definitions.@A  33d597g2227 2006/05/14 2005/11/06kESrinivasF Sreemanthula^Technical, Non-binding_86`48a7.4.14b^Request to reconsider the use cases for MIH network information and remove them if not needed.cAMIH Network Address Information request and response primitives seem to have the same functionality already defined for fast mobile-ip handover signaling. This may cause some redundancy in 802.21 definitions.@A  33d597g2227 2006/05/14 2005/11/06kESrinivasF Sreemanthula/26cfcnode's{W"WnodesW:WW+WTWnon-3gppXWnon-3gpp2YWnon-adaptivenessWnon-l2Wnon-mihQW%lEPek 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.4d491g2211 2006/07/20 2006/04/2814,15mEPek YewFTanGMember^Technical, Binding_67`50a7.2.3.1bC1. Either remove or provide details expecially on all 4 primitives.cNo detail description and usage of the MIH_NMS_SAP primitives. Implementor would not be able to implement interoperable solutions based on the brief descriptions on 4 primitives.d501g2216vby comment 500w Superceded 2006/07/20 2006/04/2816 nEPek YewFTanGMember^Technical (was Editorial)_31`60a5.8b.Remove section 5.8 or include as informative. d501g2216 2006/05/14 2006/04/2816hulaSJbwish-WWwishesUWWWwith*W-WWW_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=WAWBWNWPWXWYW]WoWvWނWކWC ^technicalnWoWrWsWtWvWxWyWzW{W|W}W~WWހWށWނWރWބWޅWކWއWމWލWގWޏWޔWޕWޖWޗW0W1W2W3W4W5W6W7W8W9W:W;W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`W`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"W_WaWbWjWkWmWnWoWwWzW{W|W}W~WہWۑWےWۓWWeWܬWWW݂WWWusingmihftoqueryandreserveresourcesrequiredforahan"VusingradiusrelateddefinitionmaybeagoodideabutitalۓVusuallyۅWutilised}Wutilize݂WVۓVۓVۓVۓVۓVۓVۓVۓV%Y+o 2006/07/20 2006/04/28 inding_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.mRejected 2006/07/20 2006/04/28 oEPek 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.mRejected 2006/07/17 2006/04/28 /05/14 2006/04/28 be able to implement interoperable solutions based on the brief descriptions on 4 primitives.d501g2216 2006/05/14 2006/04/2816vasj;cmiheventderegisterhasnotbeenexplicitlymentionedMVmiheventregisterandderegister(VmiheventregisterandmiheventderegisterwhicharementioVventregisterandmiheventderegisterwhicharementioVVheventderegisterwhicharementioVVcmihhandoverinitiatemihhandoverpreparemihhandovercomm@mihreportshouldbeinfoqueryresponsesinceinsection8.5.@mihf@miho@gmissing@>missingspacebetweenwords@&mn@mode@most@dmoved@necessary@needed@needs@pneighbor@@networkfnetworkidshouldbelinkid@new@newlinkidentifier@nms@noieforperformanceofaccessnetworkshasbeendefined@fnode's@Pnon-pos@endefined@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@bmacnewaccessrouterde4Wmacnewaccessroutermacaddressn/amacaddressofnewaccess4Vmacnewpoade4Wmacnewpoamacaddressn/amacaddressofnewap/bs4Vmacoldaccessrouterde4Wmacoldaccessroutermacaddressn/amacaddressofoldaccess4VmacpoaۊWmadeWܢWܾWWmaintainedWWmaintaining۶Wmaintenance-Wmaitained۳Wmake#W*W?WZWW;WAWBW܏WWcWdW݈WW&W,WmakeannexcinformationalorreplaceifanonqueryingVmakechangestothedraftaccordingtocontribution21-06-06܏VUS4pEKenichiFTaniuchi^ Editorial_5`10a2b150aAnnex 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.d898g2220i Subir DaskThis is not true. Not every MIHF needs to support this. Where the use cases require felxible and extensible query , it needs to support this. mRejected 2006/05/14 2006/04/28pEKenichiFTaniuchi^ Editorial_5`10a2bative" 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.d898g2220i Subir DaskThis is not true. Not every MIHF needs to support this. Where the use cases require felxible and extensible query , it needs to support this. mRejected 2006/05/14 2006/04/28pEKenichiFTaniuchi^ Editorial_5`10a2bon the brief descriptions on 4 primitives.d501g2216 2006/05/14 2006/04/2816kB hbmihlWrWxW|W~WބWޅWއWވWޔWޕW0W1W3W5W7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWl~b#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/07/20 2006/04/28 EEleanorFHepworthGMember^Technical, Binding_74`9a7.3.9bRemove SIP from list.from list.orthGMember^Technical, Binding_74`1a7.3.9b#Revisit parameters used by Link_Up.cng_86bsetAWFWGWMW_WېWHWTWUWVWWWXWcWdWiWjWkW|W/WݗWWW[WޔW0W3Wsetthelengthfieldto1|VsettingW8WsetupۉW/WshallW W-W.WeWW۟WvWwWܕWW W WOWQWހWނWފWshallsubmitthecorrectcallflowQVshildމWshoudlWshoudlexplainwhatammendmentsneedbedoneinordertoallVVWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW%W&W(W*WܨWܷWWWWWWDWUWYWkWoW݀W݂WݺWWWWWWWWWWWW,W-W.W0W6W9W=W>WAWBWDWJWPWTWޗWWWshouldbeaddedtotable5anddefinedV7cforthecasewheremihfuncionisplacedinthe3gpp2networVforthepoachannelrangeiethevalueoflowandhighdoesVhecasewheremihfuncionisplacedinthe3gpp2networVV# 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.d555g2297vative is to disallow passing this link event to an MIH user.3d548g2296 2006/07/19 2006/04/24TEQiaobingFXieGMember^Technical, Binding_78`53, BindinguEKenichiFTaniuchi^ Editorial_52a 6.3.4.3.1bA,Length od of CivicAddressElements in octets.,@Af 33   33   33fctypo " length od ..."d428g2414 2006/07/2010vEKenichiFTaniuchi^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 GuptajA3The 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.3mRejected4brequest/responseW#WWPW\WrequestedfWVWXW\WނW9WrequestedeventlistۉWrequester_WbWrequestnetworktypeۊWrequestsUWWWܕWܽWrequireW>WrequirelargemessagesupportfromtheunderlyingtransportVrequired"W#WAWەWW\WܬWWW WWWW4WrequirementspWrequiresxWrequiresclarificatioxVrescindedRWreserve"WWreservedyWۉW$WRWTWUWVWWWXW|W}WܒWܹWWލW1W6WreservedforietfܹVreservedforothersdosܹVreside_W_W_WܹVreservedforothersdosܹVreside_W_W_W_WܹVreservedforothersdosܹVreside_W_WW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6Wtqbretrieved@#rewrite@s@same@sap@~scenarios@Vscope@scoping@section8sections@ seeking@"sentence@services@set@\should@shouldbereplacedbyasinglestackwiththeentitystack@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ېWRWcW7.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.14W7.3.2ېW7.3.2.1ېW7.3.2.2ېW7.3.2.3ېW7.3.2.4ېW7.3.4yW7.3.4linkeventregisterconfirmresponseyV7.3.6zW7.3.6linkeventderegisterconfirmresponsezV7.3.7.33W7.3.7.3whengenerated3V7.3.8{W7.3.8linkconfigurethresholdsconfirmresponse{V7.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.4oWW8.4.2.13hW8.4.2.22܂W8.5W8.5.1.1\W8.5.1.2\WoܱEVivekFGuptaGMember^ Editorial_33`40a5.2b/Remove references to "typically" from the draftcvExamine the usage of the word "typically" in the draft and remove it. Typically, "typically" is not used in standards d255g3228 2006/07/20ܲEVivekFGuptaGMember^Technical, Non-binding_34`54a6.1.2b.Clarify description of link synchronous eventsc=Are link Synchronous Events applicable for L2 handovers only?d259g3230 2006/07/20ܳEVivekFGuptaGMember^Technical, Binding_37a6.1.6mine the usage of the word "typically" in the draft and remove it. Typically, "typically" is not used in standards d255g3228 2006/06/21ܲEVivekFGuptaGMember^Technical, Non-binding_34`54a6.1.2b.Clarify description of link synchronous eventsc=Are link Synchronous Events applicable for L2 handovers only?d259g3230 2006/06/21ܳEVivekFGuptaGMember^Technical, Binding_37a6.1.6s 3] Use of MIHF ethertypeanjeevQbprior#W3Wpriorities9Wpro_WpWxWproactivelyVWprobabilityWprobablyWprocedureW+W8WproceduresRWvW݊WDWproceedsfWprocessVWXWܡWprocessing W WWWWWWWWWWWWWWWWWWWWWWWEhcdescriptionsNWmWdescriptiveWWdesign#WXWYWdesigningXWYWYWYWYWYWYWYWYWPcnoieforperformanceofaccessnetworkshasbeendefinedVVnomentionaboutwhetherhigherlayerammendmentsarerequirVnoproperexampleisgivenfortlvreques/responseܙVnospaceforexpansionofmihtlvencodingsVnodeWWۉWۏWۦW W.W3W4WܝWܡW+WwW{W|WݏWW"W#W$WZW1WLWW{W|WݏWW"W#W$WZW1W1WHWW{W|WݏWW"W#W$WZW1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W1W>ucmihoܠWmihomediaindependenthandoverܠVmiih2Wmiis#W_W`WbWiWjWkWlWmWnWoWzW۳WWWWIWܻW_W`WuW݂WW:WmiisisnotdefininganinformationrepositoryVmiisprovidestheabilitytoaccessthisinformationaboutaVmime|W~WminimizeW@WminimumWminutesWmip-WWJWWmipv4Wmis-correlationWmisleadingWW=W@WfWWmisleadinguseofsquarebracketswhicharecustomarilyusedVfVmismatchWmisplacedގWlacedގWގWomarilyusedVfVmismatchWmisplacedގWގWcedގWގWcustomarilyusedVfVmismatchWmisplacedގWގWގWގWގWގWގWd kBom UMTS to 802.1D. The QoS mapping information helps the STA to properly generate QoS requests (e..g in 802.11e case to map to correct EDCA ACs) to achieve consistent user experience across different access networks.mAccepted-ModifiedvWe are following the ITU-T definition of different QoS parameters and following that. Superceded by comment 90 that deals with QoS issues.w Superceded 2006/07/20 ESanjeevFAthalyeGMember^Technical, Binding_53`26a 6.3.4.3.4b:Explain or reformat the channel range information element.cKFor the PoA channel range IE the value of low and high does not make sense.d431v:Add (Low, High range MHz). Refer to definition in Table-6.wAccepted-Modified 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_56`1-20a6.3.6.1b{Provide context with an introduction to the Request/Response message, which explains how the PoS determines the response. ing table, e.g. from DSCP to 802.1D, or fr_ ;1EJinFLeeGMember^Technical, Non-binding_54`14a 6.3.4.3.6bA[Insert 'MIH Capability' , page 54, line 14]: --------------------------------------------------------------------------------------------------------------------------------- Type | Description | Length | Value | --------------------------------------------------------------------------------------------------------------------------------- TYPE_IE_POA_CAPABILITIES | PoA Capabili------------------------------------------------------------------------------------------------------------------------- Type | Description | Length | Value | --------------------------------------------------------------------------------------------------------------------------------- TYPE_IE_POA_CAPABILITIES | PoA Capabili=C 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%ZpbmiddleWWmiesuWmightWWmigrationWmih 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[WfWiWjWjWjWiWiWiWc:barrow݃WW0Warrows݃Warticle2Wle2W2W2W2We2W2Wcreferencetointernet-draftshouldberemovedݕVݖVݘVreferencetotrafficclassesisvaguealsothisinformationVreferencesWWWWWW&WfWreferencesarenotnumberedVreferencesto3gppstandardsshouldincludeanindicationofVreferencesto802.16eshouldberemovedasnosuchstandardVreferredWWWreferring۩WWrefersۑWPWreflectۄWW;WW<W?WregardingWWCWhW>WregardingtheumtssidedoesthepicturemeanthatthemihlCVregardlessoWregistationWregister-W.WRWeWWW(WEWFWGWHWLWRWrWyWregister/deregisterWregisteredWregisteringKWWWWWWWWWWWKWregisters-WeWޫWWWKWregistration.WuWVWXWWWWWkWެWWWLWregularޖWeboriginate,W-W8WܫWWoriginatesWoriginating$WoriginationIWationIWIWW$WWWWWWWWWWWWc4ܳbgInclude a time based state diagram showing different link layer events w.r.t different handover stages.c|It's not clear what the difference between different link layer events is and how they may affect handover decision making. d272g3231i Qiaobing XiemAccepted 2006/07/20T-22g2458 2006/05/1418,EDavid FFamolari^Technical, Binding_16`44a5.3.1ben introduced as a service here. However, throughout the specifictaion only three services have been introduced and discussed d742g2458 2006/05/1418,EDavid FFamolari^Technical, Binding_16`44a5.3.1ben different MIH implementations. d419g2259 2006/05/14IENada, Golmie, Member^ Editorial_54`50bRemove the first sentence.c 1: minute d_‚H-.NŃܳJݒ߃‚I‚Jԃ=‚Q89Ky>?s‚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\blinkeventregisterconfirmresponserVlinktypeisnotnecessarytoputhereiftheproposedgener<Vlink-layerWWlink-state8Wlink-switch)Wlink-type~WlinkidentifierWWlinkparamaeterۉWlinkparameterۉWlinkparameterlist_Wlinkparamterlist_WlinksPWTWkWWWW1WޔWlinktechFWGWlinktypeFWGWۉW"WaWbWcWlinktypemediatypeofthelinkaVaVaVaVlinkaVaVVlinktypemediatypeofthelinkaVaVaVaVaVaWbWcWcWWWWWWWWWWWWWWWWWWWWWWWWWWWWKWLWSWTWUWVWWWXWbWcWdWhWkWmWyWzW{W~W܎WܷWWWݙWWW@W[W^WtWWދWތWޕWޫWެW޿WWWWWW:^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 Vb bbApFirst 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. pcA0This retrieval mechanism (using pre-defined reports) offers little flexibility; if one would want to do a retrieve different from the current pre-defined reports, he would have to wait for a new TYPE_REPORT_XXXXXXX to be defined in the standards and implemented by the MIIS servers before he can use it. 0d451g2311i Subir DaskgSimilar to comment #444. Does this not mean we need semantic query capability with a query language? mRejectedvby comment 339w Superceded 2006/07/20 2006/04/24 cEQiaobingFXieGMember^Technical, Binding_81`21a7.3.18.1b@KBtaniuchiއވމފދތލގޏސޑޒޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓޓ,lcsubjective-Wsubmit>WsubmittedܮWsubnet\WZWsubnetinformationaloneisinsufficienttosupportscenario\VsuboptimalWsubscribed7WsubsectionsW1WsubsetWsubstantiallyPWsubsystems/WsubtleWsucceedseWsuccessۄWsuccessful܄W*WsuccessfullyWsuccinctnessWssWWctnessWWsuccessfullyWsuccinctnessWW ހ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 2006/07/2022ށEKenichiFTaniuchi^Technical, Binding_127`36ictypolengthoduVtyporaeinthesentenceshouldbeareފVtyporregisterVtypothisprimitiveisusedbyuppersVtypographical۠W.Wtypographicalerror۠V.Vucd|WudpWudp/ipwWue܋Wumts۽W:W@WWCWun-usedWunableۇWunacknowledgedWunavailable.WWunchanged0Wunclear۫WWWWWWWWWWW-W݀W;WKWuncleardefinition۫Vunclearfunction/operationinboxmiisreportavailabilityVunclearterm-VunclearwhetherdurationisperiodoverwhichtheconstinfoVuncontrolledWundefinedܦWWunderuW W!W"WWWWWW}WWWWWW}W}WWW}W}WWW}W}W}W}W}W}W}W}W}WerstandingjWkWmWnWoWzW{W|W}W~WہWJWWWWunfamiliarRWbisޕWޖW0W3W5W8W<W@Wisencapsulatedandincaseofmobileipv6ޏVisquerytypes0VisinitiatedۂWiso/iecpWissueۓWۓWۓWۓWۓWWۂWۂW0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V0V% ^bindingܝWܞWܪWܬWܮWܳWܴWܶWܷWܸWܹWܻWܼWܽWܾWܿWWWWWWW 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/01Jb Introduce text saying that schema query support is purely an advanced function which is optional to implement. Make annex C informational (or replace, if a non querying data schema is adopted). cASchema is mandatory, Should be optional. Mobile consumer appliances which do not require "dynamic" or "schema" data shouldn't have to support it. Small edge devices which are not dynamically managed shouldn't have to support it. Including XML and TLV decoders into these devices will prevent upgrade of existing and resource constrained systems to include 802.21. - Starting Page#: p59 - Starting Line#: p59(45) - Fig/TabB3le# (if applicable): - Section#: 6.3.8, Annex C !d463g2222iYoshihiro Ohba&c device to reconfigure and present data to uppered) enterprise environment). cbhLb7.4.4.1.25W7.4.4.1.2whengenerated5V7.4.7.2.2ۄW7.4.8gW8WJW|WGWRWܑWܔW2W6W8.2.1rW8.2.1l2dataframespacketformatrV8.3tW8.3protocoldescriptiontV8.3.1qW8.3.2.3ݳW8.3.3.2W8.4.2.13hW6W8.4.2.22܂W8.5W8.5.1.1\W8.5.1.2\W8.5.2.5ޕW8.5.2.5mihlinkupindicationޕV8.5.3.116W8.5.3.126W8.5.3.137W8.5.3.147W8.5.3.158W8.5.3.168W8.5.3.179W8.5.3.189W8.5.3.19>W8.5.3.20>W8.5.3.5܂WW.3.20>W>W.3.20>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ۉWWYWޖW5Wconfigurerequestset܄Wconfigurerequestsetlinkconfigureparameterstype14܄Vconfigurestatus܄Wconfigurestatusstatus245܄VconfirmېWWW\WyWzWWW>WBWCWJWrWyWzW{W=WconfirmationWWconfusingWconfusionޗWcongestion-safeWconiferlWconistent۽WconnectW W0WconnectedWconnection,WޕWconnectionsOWPWTWconnectivAWconnectivityAWSWWRWSWܡWconnectsWconsiderOWPWۼW۽WWWWWZWconsideraddinguniqueeventidentiferforlinkdetectedVconsiderredrawingpicturewithmoreconistentuseof3gppt۽VconsiderremovinggenericۼVconsiderremovingorbetterexplainingintentoffiguretheVconsiderspecifyingtheqosinformationinlinklayerindepeVVVVV%5 bchange:WAWchange5.6.3.1mihnmssap8VchangeasfollowsܤVchangebecommunicatingtocommunicate7VchangecontainingasetofconfigurationparameterswithconjV5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W#binfoquerytypejWkWmWnWܕW}Winfoquerytypeanintegervaluecorrespondingn/athetypeofjVmVinformݍWinformaAWinformaiton?WWWWW >ނ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 | | |  ހ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 _ ނ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 | | | buser,W-W.WAWLWOWPWQWRWSWTWUWVWWWcWfWiWېWW܊WIWyWzWWWޖW5WW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wvalid\WۂWېWTWUWVWWWXWYW\WcWkWmWܖWW|WWvalidrangeۂWvalueJWXW_WfWjWmWzW{W}WۉWWWW*W=WFWHWwW|W܂WWXW[W~W݁WݔWݗWݘWݙWWWހWނWޅWWW7WwcunderlyingcWeWWWWWunderstandDWWCWYWWunderstandingjWkWmWnWoWzW{W|W}W~WہWJWWWWunfamiliarRWunfamiliaracronymRVunicastۈW hbAR 33  TT  .Rdge 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  33d817g2340i Subir DaskSame as earlier Comment # 812mRejected 2006/05/14 2006/04/2423 EQiaobingFXieGMember^Technical, Binding_138`39a8.6be 63)c^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> ނ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  =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/07/20 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/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Binding_114`4a8.3.2.3bEDefine the syntax of the transaction id including allocation rules. canage deregistration). Registration messages are apparently only defined for particular event types. d725g2300 2006/07/20 2006/04/28hGMemberMember&xbrdf/xmlkWnW}WreܬWre-classifyZW]Wre-defineFWGWJWre-definethelinkparametertypeasapairoflinktechtechsFVGVre-definethelinkqualityparametertypeencodingtableasJVre-organize_WbWre-verificationWWre-visitWreadqWWreader݂WreadersWreadilyWready#WWreadilyWready#W#WWready#W#WWreader݂WreadersWreadilyWready#W#WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhblistedܼWDWlistingSWlists9Wliteral~WlittlevWlocܗWܘWܙWeral~WlittlevWlocܗWܘWܙWܙWbthisparameterspecifiesthelistofcommandsthatmaybecaދVތVthisprimitiveisdeliveredfrommihfunctiononoldserving"VthisprimitiveisgeneratedbyanupperlayerentityoftypeېVabtoWWWWWWWWWWWWWWWWWWWWWed 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 14rialvreplacerequestwithindicationކVreplacewithvalidmihfidentifierVreplacingއWreportedQWrepresentWWrepresentasintegerVrepresentationWWWSWrepresented0WrequestjWkWlWmWnWoWyWzW{W|W}W~WہWۂWۆW۔W_WWކWrequest/responseWrequestparametersۆWrequiredۈW۔WەWW_WSWoWrescindedRWreservation"WreserveVWreservedWresolutionfW>Wh euqivalent primitives that are defined in the specification or remove these primitives.   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 | -------------------------- ޅbAThis 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 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. cKLink_Up.request and Link_Up.response are not defined in the specification. d871g2433v!Replace .request with .indicationwAccepted 2006/07/2030iuchi^Technical, Binding_138`9a8.5.4.1b6/07/20ބEKenichiFTaniuchi^Technical, Binding_138`9a8.5.4.1b Value | --------------------------v ހ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 | | | | ------------------------------------------------------------------ ނbcTable 23 needs to be revised.d813g2429wAccepted 2006/07/2023ރ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.d814g2430vA1: 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 parameterse1ctoޖW1W2W3W4W5W7W7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWnjސEKenichiFTaniuchi^ Editorial_141`4a Annex A-1bas in the comment.cAE.g., e.g., @A>    33>d876g2444 2006/07/20ޑEKenichiFTaniuchi^ Editorial_141`6a Annex A-1bas in the comment.cAnotifies notify @A>    33>d878g2445 2006/07/20ޒEKenichiFTaniuchi^ Editorial_141`20a Annex A-1badd a period to the sentence. cmissing a period. d880g2446 2006/07/20ޓEKenichiFTaniuchiEKenichiFTaniuchi^ Editorial_141`6a Annex A-1bas in the comment.cAnotifies notify @A>    33>d878g2445 2006/07/20ޒEKenichiFTaniuchi^ Editorial_141`20a Annex A-1badd a period to the sentence. cmissing a period. d880g2446 2006/07/20ޓEKenichiFTaniuchiBއEKenichiFTaniuchi^Technical, Non-binding_106`23a 7.4.15.1.1bAThis 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 2006/07/20 primitive. d659g2434v>Editor to examine replacing MIH with MIHF wherever applicable wAccepted 2006/07/20c5In Section 8.5.4.2 the description is not correct . d861g2432 2006/05/14ކEKenichiFTaniuchi^Technical, Non-binding_140a Annex A-1bmEither replace with euqivalent primitives that are defined in the specification or remove these primitives. | --------------------------[-vissueidentifiedsuggestedremedycannotbeappliedtoaspeމVissuesZWW-WSWitSWUWێW۵WWWeWܗWW 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 *n ތbAThis 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 2006/07/20ލEKenichiFTaniuchi^Technical, Binding_122`51a8.4.2.2bA4:SIP 5-7: Reserved@A* 33 *c Reserved bit should be assigned.d790g2441wAccepted 2006/07/20ގ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 2006/07/20ޏEKenichiFTaniuchib ނ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.| ----------------------------------------------------------------------------------------------------------------------------------- ނ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.| ----------------------------------------------------------------------------------------------------------------------------------- ފEKenichiFTaniuchi^ Editorial_118`28a8.4bAiTLV type values shall be unique. TLV Type values rae are assigned in accordance with the following rules:i@AR 331  4 8 33Rc(Typo rae in the sentence should be are.d772g2437 2006/07/20ދ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 2006/07/20ތEKenichiFTaniuchi^ Editorial_119`17a8.4.1.2b5g2439 2006/05/14ތEKenichiFTaniuchi^ Editorial_119`17a8.4.1.2baAnnex 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/07/20މEKenichiFTaniuchiGMember^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....mRejectedvHIssue identified. suggested remedy cannot be applied to a specification.wRejected 2006/07/20 ember^Technical, Binding_150`16aAnnex CbA6One persistent URL of this schema shild be assigned. 6@A* 334 *^bapplication/xmlހWނWapplicationsAW7WapplyܪWappreciablyAWappropriateAWTWkWnWۉWW#WUWYWW}WappropriatelyWWaWappropriatlyNWapprovedKWLWaps?WJWJW?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߱Wrb2rdfdatajVmV2referencepointsܯV2rejectedܖV2renumberpagesoftoclofandlotV2shouldbereplacedbyinformationaboutaccessnetworksV2wirlessieee802.16^VVMbscope W#WsWuWvWwWەW۶WܪWWfWWfWfWWfWfWWsWuWvWwWە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ގWޕW0ismisplacedinthevaluecolummގV0-6W06W*W0x2W0x2a16bitouia14bitsid34bitsalsothecommentsforV1W!WSWiWsWuW۪W۽WWWWW(W=WWWW>WޕW:W>W1tableofcontentssectiontitlemissingV1textneedstoimprovesV1thecurrenttextimpliesthatthediscoveryofmihfunctiouV1thedescriptionandcategorizationofhorizontalandverti:V1theinformationelementtypeielistofnetworksrepresent=V1thisisalinklayerindicationwhichshouldonlybereceiSV1whatisastation'smihisitamobilestationorbasestaiV1-21]WPb ݊bBitself and the network for handover with the assistance of the network in executing handover procedures. Handover policy is in the mobile itself but gets the available QoS, bandwidth information from the network node. * Network-controlled handover (pure) A network entity instructs the network or mobile for handover with no mobile assistance. Anchor MSC can get the information from Target MSC about the available bandwidth, SIP server or QoS server finds out the available bandwidth in C*the local network and then controls the handover. Handover policy is in the network. * Mobile-controlled handover (pure) A mobile node instructs itself and the corresponding node for handover with no network assistance e.g., peer-to-peer networks, ad hoc. May not be suitable for the operators. "cjDo we need to define what network initiated, network controlled, mobile initiated, mobile controlled are? d47g2419treesjWkWmWnWoWzW{W|W}W~Wd0vbycomment473OVxVbycomment480\Vbycomment482rVzVbycomment483VDVbycomment4951V3V4V5V6V7V8VAVBVCVbycomment495updateasperresolutionofhandovercommandsDVbycomment500mVbycomment527626ݞVݟVݠVݡVݢVݦVbycomment527/626ݧVݫVݬVݯVݰVݱVݻVݼVVVVVVVVVVVVVVbycomment577dVbycomment597<V=V>VVbycomment607ݩVbycomment609@Vbycomment609wherethisissueisgonnabeinvestigatedinVbycomment632Vbycomment704Vbycomment719sVVVVVTVcomment752/756bycontribution21-05-0671-00-0000-821-fFVbycomments287289292293294295andcontribution21-06-0KVbycomments482508514515267whichtakecareofconfirm/reJVbycommment527/626ݨV in 1.1 to match the new d XMbbyޖW3W5W6W8W9W@Wbyr1r2orr3overanyaccessnetworkandtwomihnetworkeVbytlvforeachoperatoridentifierݙVݙVݙVݙVݙVݙVW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9Wo2^technical܏WܐWܑWܒWܓWܔWܔWܔWpeVparameterspecifiesthelistofcommandsisquerytypeVVparameterspecifiesthelistofcommandsisquerytypeVV ޔbF------------------------------------------------------------------------------------------------------------------------------------------------------------  E@A> 33  33>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.docd303g2218 2006/07/20 2006/04/30T. 4ޕEVidalFAlbertGMember^Technical, Non-binding_130`65a8.5.2.5b | .............. | ................. | ............................. -------------------------------------------------------------------------------------------------------------------------------------------------------------chi ޔbBtion | Description --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 1 | MIH Get Status | L, R | Network -> Client | Get the status of links -----------------------------------------------------------------------C----------------------------------------------------------------------------------------------------------------------| ...... | .............. | .............. | ................. | ............................. -------------------------------------------------------------------------------------------------------------------------------------------------------------chibthismessageisusedbymihfunctiontoretrievetheinformaބVthismessageisusedbymihfunctiontoretrievevalueofdiޅVthisparameterspecifiesthelistofcommandsisquerytypeVparameterspecifiesthelistofcommandsisquerytypeVVmessageisusedbymihfunctiontoretrievevalueofdiޅVޅVPޖEVidalFAlbertGMember^Technical (was Editorial)_78`48a7.3.14.2b--------------------------------------------------------Z@A> 33  33>cAThe 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 *d826g2219 2006/07/20 2006/04/30ޖEVidalFAlbertGMember^Technical (was Editorial)_78`48a7.3.14.2b | Mobility management Protocol List (4) |chiD zbA  33!  33- 33[  33f 33  33 33  33 33 9 33>c$may should be maybe in the sentence.@cassociatedBWW WW8WassociationWassumeWassumethereferencetodiameterisactuallyapointertohoVassumedWWassumesiWassuming۳WW_WuWassumingthatmnreliesonaccesstomiisistoostrongmore۳VassumptionWassumptions:WatjWkWmWnWoWzW{W|W}W~WہWۄW۔W۪WW7W܌WܝWWWW WW+W;WWWW7WKWQWZWޖW?Wattached+WattachesݏWattachingOWattachmentܝWattempts&WaugmentܶWautenticated#Wautenticatedwiththepoaandshouldbenewpoa#VauthenticatingܺWauthenticationWWbWavailabilityWWavailable=WYWܡWܢWܶWWWSW|WݏWWWW!W%WgWAWBWCWavoidWavoided,Wided,W,Woided,W,WW2 ޗcBwtwork) <> 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/07/20 2006/04/30F 30 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(NeUEST/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(Ne| Mobility management Protocol List (4) | @cATwo 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/07/20 2006-04-30AEXiaoyuFLiuGMember^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/07/20 2006-04-30BNbipv6\WWޏWipv6insteadofmobileipv6VisW W#W'W-W.W?WAWDWFWGWJWLWMWXWZW]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[WyWzW{W}WWހWށW?_Ã%܍ܚÃ%ۀtÃ%uvÃ&ہoމÃ&`wÃ&ۉ`2 ]ۀہی۔۬ۃ-0Ju܁ܜܠܼܾŃσЃ2{݄݊݋݌ݒݛݥЃ ghlDDDi 0bD | | 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/07/20 2006/04/30-----------------------C----------------------- ..................................................|...................|...............................................|........................................................................... ------------------------------------------------------------------------------------------------------------------------------------------------- SupportedISQueryTypeList | List | Set of supported | List of supported IS Query types on client 2 0bB SupportedISQueryTypeList ) -------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | Description ---------------------------------------------------------------------------------------------------------------------------C----------------------- ..................................................|...................|...............................................|........................................................................... ------------------------------------------------------------------------------------------------------------------------------------------------- SupportedISQueryTypeList | List | Set of supported | List of supported IS Query types on client  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. d713g2294vKno text. opened issue to look at efficiency of acks as suggested in commentwRejected 2006/07/20 2006/04/28 dd 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/05/22 2006/04/28!MݔE YoshihiroFOhbaGMember^Technical, Binding_44`38a6.3.2bAChange 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 2006/07/20 2006/04/28Table 6 ݕE YoshihiroFOhbaGMemberhttp://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 2006/06/20 2006/04/28Table 6 ݕE YoshihiroFOhbaGMemberbaGMemberbaGMember | ޔbD-------------------------------- | 4 | MIH Configure Thresholds | L, R | Network -> Client | Configure thresholds for link events | | | | Client -> Network | | | | E | Network -> Network | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ...... | .............. | .............. | ................. | ............................. ---------------------------------2EJinFLeeGMember^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. d193g2215wAccepted 2006/07/20 2006/04/30Marked8cided 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. d193g2215wAccepted 2006/07/18 2006/04/30Marked8 | Description | Length | Value | --------------------------------------------------------------------------------------------------------------------------------- TYPE_IE_POA_CAPABILITIES | PoA Capabili.9FXieGMember^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/07/20 2006/04/24FXieGMemberd758g2265 2006/07/20 2006/04/2419 19 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.d439g2214wAccepted 2006/07/20 2006/04/30 | Description | Length | Value | --------------------------------------------------------------------------------------------------------------------------------- TYPE_IE_POA_CAPABILITIES | PoA Capabili------------------------------------------------------------------------------------------------------------------------- Type | Description | Length | Value | --------------------------------------------------------------------------------------------------------------------------------- TYPE_IE_POA_CAPABILITIES | PoA Capabili]W GbA 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@ | | | before retransmission}, | | | | 3EJinFLeeGMember^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  33zc1 2006/04/3083EJinFLeeGMember^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  33zc--------------------------------------------------------------------------------- TYPE_IE_POA_CAPABILITIES | PoA CapabilinborderxWWWWW"WorderingWorgW=WݔWorg/2001/xmlschema~Worg/2005/sparql-resu~Worg/tr/2004/wd-rdfspqWorg/tr/rdf-sparql-quqWorg/tr/rdf-sparql-xmqWoriginallyfW~cfinalized>Wfirst_W`WpW5WIWwWWWWQWfitWWfitsXWYWfixeduWܑWܔWWWWW'WflatZW]Wflexibility_WbWflexible WflowۚWWW-WWKWMWyWzWWW>WBWKW8W=W@WflowsWWflyWWfmipWfmipgmiiicmparenotusedVfocusWXWYW:WfollowWfollowed>WfollowingܬWCWݏWݐWWWWW W/W1W2W>WIWޕWfollows۪WforW!W"W$W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WBWEWFWGWHWIWJW[W^W_WaWbWeWhWjWkWmWnWoWpWuWvWyWzW{W|W}W~WہWۂWۅWۆWۈWۋWېWۋWۈWۋWۋWWۈWWۈW#csections+WWWWW)W*WnWsectoridWsecureܢWWsecurityW<WܢWܼWܾWWݏWWsecurity/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ܰWFjk0x2W1W1isgeneralaccessnetworknformationandsoV12#W6W13#W14W15KW16W162۷WW2W2.6ܼW21#W21-05-0347-00-0000-xjWkWmWnWoWzW{W|W}W~WہW22#W27#W28#W29W32W345]W350ےWW362!W394XW3gpp/3gpp2۾W444bW45ܼW4889W493RW494RW52#W53#W577bW6ܼW6.3.4.2.5ܼW6.3.8W݀W607ݩW626ݫWݻW7.2.1W8.6W802.11WW802.11eW802.16W802.1dW802.21uW۾WWWa/W0W<WAW]WbWjWkWmWnWoWzW{W|W}W~WہWےWWWW|WܶWܺWWݓWݴWݻW-WOWjWabdܹWable/Wabout#WAWWWWaboveWaccessWWaccessibleWachieveWWacross/WW6x@ccAcA@jk@EcAO@@b@@@@b{b{|Ezb{b{{Ezb{b{zb{b{zb{@}Okimyz{|koh}~lee012345676777777777777777777777777777777777777777777777777777777777777777RܮEDavidFHuoGMember^Technical, Binding_23a5.5b Replace Fig 4c+Replace Fig 4 by the submitted contributiond180g3262y0Group needs the submission number in the comment 2006/07/20F-4ܯEVivekFGuptaGMember^Technical, Non-binding_31a5.7.1b\Clarify MIH Protocol w.r.t 1] Transport options 2] Reference points 3] Use of MIHF ethertypecInclude some sample reference locations of MIH PoS and discuss different transport optons in that context. Also specify what Refeernce points are covered by MIH Protocol. Is MIH Protocol dependent on use of MIH ethertype?d226g3229vIssue #1wDeferred 2006/07/20MarkedܰEVivekFGuptaGMember^Technical, Non-binding_31a5.6.2b3Come up with a more accurate classification scheme.ct. Also specify what Refeernce points are covered by MIH Protocol. Is MIH Protocol dependent on use of MIH ethertype?d226g3229 2006/05/18ܰEVivekFGuptaGMember^Technical, Non-binding_31a5.6.26 :@bab@cS@ bA!@)bA"cA+vA#^$@5bAcA %bA&@^'bA)k*vA+k,@bjA^cAccAcAAbcAg@c@@wcccbAcAcAbAAcAOcAbB@ R ^bAb@bA@Ecbb@g!bA"@cAg$bAcAg%cA'@bA*cAg,b.a1b@c 3bA 4bA5cۯFAthalyeGMember^ Editorial_17`43a5.3.1bSee previous commentcSee previous commentd121 2006/07/20۰ESanjeevFAthalyeGMember^ Editorial_17`57a5.3.1b*Use "a" as in other similar cases in tablec'Make indefinite article form consistentd124 2006/07/20۱ESanjeevFAthalyeGMember^ Editorial_18`17a5.3.2b"access technologies"cSimplify phrasing, remove dashd129 2006/07/20۲ESanjeevFAthalyeGMember^ Editorial_18`56a5.3.2bChange "visiting" to "visited"cConsistency of termsd138 2006/07/20۳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./05/14EDasFSubir^Technical, Binding_16`63a5.3.1bDelete itorial_4`10a1.4wcadequatelyەWadjectiveeWadjustmentsWadministartiveWadministartivemiheventtypehasnotbeendefinedVadministrativeWWWWWWWWf 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%W&W)W2WܕWinconsistentwithsection5.5VincorporateWܕWinconsistentwithsection5.5VincorporateWWwithsection5.5VincorporateWWWWWWWWWWWWWWWWie<"==xie><">qiaobing1=xie?!@@xieA?!Aqiaobing2@xieB5CCxieDB5Dqiaobing3CxieEGF! FxieGEGGqiaobing4FxieHWId\"IxieJHWJqiaobing5IxieK#LaN$`LxieMK#Mqiaobing6LxieNxieOKaOqiaobing7NxieP)QWS$pQxieRP)Rqiaobing8QxieSxieTPWTqiaobing9SxieUxieV6ZVqiaobing:UxieWxieX9dXqiaobing;WxieY6Z!@Zxie[Y6[qiaobing<Zxie\Lۃ@cAۄ@cA ۅcA?ۇb ۅcA?ۆ@cAۄcA?ۄcA?cA ۄcA?ۄcA?ۄcA?cA ۄcA?ۃ@cA ۄcA?ۄcA?cA ۄcA? ۄcA?ۄcA?ۄcA?ۃ@cA ۄcA?cA? ۄcA?cA ۄcA?cA ۄcA? ۄcA?cAcAۂ@bACEPGcAcAcAcAEPGcAXFZ@c{\c]c_bACcAC`@acBbcAc@bA!d ec'gc$ibA.)jbA/5kbA7cA;d:mbA?cACdBncAKdDpbAYCZdWsbAwdvu3 5vwAccepted-Modified 2006/07/20 2006/04/28Marked6EAjayFRajkumarGMember^Technical, Binding_31`4a5.6.2.1b:Section 5.6.2.1 (MIH_LINK_SAP) should be removed entirely.cThe MIH_LINK_SAP is not shown in Figure 12 and is not media-independent. The respective instantiations of the MIH_LINK_SAP for the different link-layer technologies are already described in the Media Specific SAPs section (5.6.1).d230g2249i Vivek GuptakrMaybe we should modify Figure 12 and show MIH_LINK_SAP and clarify things, otherwise things are just left hanging.mRejectedvEMIH_LINK_SAP is now added to Figure 12 and explained in section 5.6.1wRejected 2006/07/20 2006/04/28Marked 7EAjayFRajkumarGMember^Technical, Binding_31`11a5.6.2.2bocal 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)."EMember^Technical, Binding_30`36a5.6.1F =bC 18: Wireless - Other 19: Wireless - IEEE 802.11 22: Wireless - CDMA2000 23: Wireless - UMTS D 24: Wireless - 1X-EV 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 T>7 331  339 33>d344g2246 2006/07/20=ENada, Golmie, Member^Technical, Binding_44`38b 33)  331 33g  33n 33fcAGSyntax error in "network security and quality of security capabilities"G@A> 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 $cfiguresWfiltering WpdatedwiththeprimitivesdefiguresWfiltering W WwiththeprimitivesdeޗVfiguresWW9EFarrokhFKhatibiGMember^ Editorial_18`26a5.3.2bf" from the visited network about that visited network or about home network via visited network PoS."cUnwieldy sentenced132 2006/07/20: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"cAThe presence of the FA, HA, H-AAA and V-AAA in the reference model add no value to the standard, and are sometimes incorrectly placed. From the perspective of 802.21, there are different access networks, there is a core network, the internet and MIH databases. Everything else is extraneous. There is no need to distinguish home networks from visited networks. Additionally, the figure makes assumptions which are limiting. For example, it shows that each AN has its own Visited Core Network. IB@t is also possible that there are different Home Core Networks. .d142 2006/05/16(qbmbit/sYWmeanWmeaningoWmeaningoflinkparameterthresholdshouldbeexplainedpossoVossoVoVngoflinkparameterthresholdshouldbeexplainedpossoVoVoVsoVoVsoVoVcxie€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€:5 |$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  33Rc/05/14 2006/04/28$EPeretzFFeder_104`48b1g2261 2006/05/14#EPeretzFFeder^Technical, Binding_104`41a 7.4.14.1.3bf  33      33  33cc Add context transfer d644g2260 2006/05/14 2006/04/28cconfiguregWۄWۉWWYW\WkW܂W܄WaWWWFWGWHW{WޔW3WconfiguredۄWZWޖWconfined1WconfirmWWWW>WrWyWzW{WconfirmprimitiveformihcommandisnotdefinedVconflictedTWconflictingۼWconflictsWconfusedWconfusing(W)WۻW۽WW W:WiW܏WܫWWWWWWkWvWyWzWWW]WconfusingphrasekVvVvVkVvVvVvVvVvVvVvVvVvVvVvVvVvVvVvVvVvV„ohbavc„yoshihiroݜohba„ohba Y„yoshihiroݝohba„ohbau„yoshihiroݞohba„ohba„yoshihiroݟohba„ohbaZ„yoshihiroݠohba„ohbay6„yoshihiroݡohba„ohba(„yoshihiroݢohba„;nbparagraph`WەW۫W۶WWܶW%W)W_WparagrpahWparameterFWGWJWTWWWۃWWYW`WbW܁W܂W܎WܐWܽWWoW|WW[WaWbWcWgWhWWހWރWދWތWޖW5WparametersAWFWGWHWIWMWOWRWTW\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ۚ~87forthecasewheremihfuncionisplacedinthe3gpp2networ@]force@foreign@form@forwarding@full@functionality@functions@g@2general@(get@goal@goes@Chandover@:)handovers@have2havemorespacebetweencharactersinsta/ueandpsdn/fabox@he@here@high@horizontal@phrpd@ie@if9ifthemnrequestsdetailedinformationonaperiodicbasis@riodicbasis@questsdetailedinformationonaperiodicbasis@periodicbasis@if9if6if6f6":0bhightlighten:Whih-Whnadover܀WhoIWDWho-typeWhoc݊WhomeW9W:WSWhorizentalWhorizontal?WAW:W:WhorizontallyۿWhotspotWhoursHWhowVWWܪWܴWܿWW\W}WXWYWhow/inܢ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.Wclinkconfigurethresholdsconfirmshouldbelinkconfiguret{VlinkconnectlinkdisconnectlinksleepandlinkpowerdownVconfigurethresholdscommandislinkcommandthatgoes3V3Va|u„yoshihiroݧohba„ohba`6„yoshihiroݨohba„ohbaNW„yoshihiroݩohba„ohbaK0„yoshihiroݪohba„ohbacZ„yoshihiroݫohba„ohba<C„yoshihiroݬohba„:„ohba:„yoshihiroݭohba„P„ohbaP„yoshihiroݮohba„ohbaBW„yoshihiroݯohba„ohbaYb„yoshihiroݰohba„ohba"„yoshihiroݱohba„yoshihiroݲhohba„ohbau2„yoshihiroݳohba„ohbauZ„yoshihiroݴohba„ohbauu„yoshihiroݵohba„l*@+cinefficienciesWinetrafce۴Wnetrafce۴W۴Wrafce۴W۴Wafce۴W۴W_fbestimationW WetcAWHWIW_WۖWW=WYWܵWܷWWWW|W9WethernetsWWW=WqW^WethertypeWܯWetypWeuqivalentކWevaluateTWevaluatedTWevenW^WܼWWW?Weveniftheschemawereretrieveditwouldn'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…9cIf 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/07/20 2006/04/17: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.sce added with a flow diagram associated with section 8.6.1.1 to show the MIH capability discovery procedure initiated by the network POA with MIHF, i.e. via beacon, out to the mobile terminal for start of MIH interactions. d903g2225u„); cADiscussion of how 802.3 networks can get direct Internet Access, but ignores other networks such as 802.11 which also could have such access. - Starting Page#: p18 - Starting Line#: p18(48) - Fig/Table# (if applicable): Figure 3 - Section#: 5.3.2 d136g2220v!As part of comments 142, 128, 226w Superceded 2006/07/203cess 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 d519g2219 2006/05/14EGregFDaleyGMember^ Editorial_18`48a5.3.2bo change to include 802.11 (which also may have this case in a (visited) enterprise environment). c 2006/04/2815IEAjayFRajkumarGMember^ Editorial_69Px_bnotifications-WLWېW\WWnotify.WWnowWnullkWnWHW}Wnumber[W_WWWFW_W~W܍WWݗWݙWݷWWWWnumberofoperators4octetsfollowedݙVnumberedNWnumbersSWWobjective-Wobtain\WkWnWW#W}W}W}W}W}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€:1 :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/07/20 2006-04-3019;EXiaoyuFLiuGMember^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. d906g22125Gblayers"W*WAWOWPWQWRWSWTWUWpWwWۉW۵WW6WNWiWkWܢWWyWݍWݎWWWWW WWWW,W1W2W3W4W5W5W7W5W7W7W5W7W7W5WWWWW9U;qiaobing0:xie<"=Cxie?!@@xieA?!Aqiaobing2@xieB5CCxieDB5Dqiaobing3CxieEGF! FxieGEGGqiaobing4FxieHWId\"IxieJHWJqiaobing5IxieK#LDaNh$`LxieMK#Mqiaobing6LxieNxieOKaOqiaobing7NxiePP)QWS$pQxieRP)Rqiaobing8QxieSxieTPWTqiaobing9SxieUxieV6ZVqiaobing:UxieWxieX9dXqiaobing;WxieY6Z!@Zxie[Y6[qiaobing<Zxie bmodule?WܤW.WAWmomentWmonthHWmoreAWPW_WqWۢW۽WWWܰWWWWWWWWNWIWXWYWށWރW9Wmoreandmergetextbetweenlines23-43into8.3.1qVmoreappropriateWW9W9W9W9W9Wba… 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…# 8cAResubmit of comment #138 from the Denver meeting. Figure 29 for section 8.6.1.2 shows the MIH capability discovery procedure initiated by the mobile terminal, to facilitate the start of MIH interactions. There needs to be a figure added with a flow diagram associated with section 8.6.1.1 to show the MIH capability discovery procedure initiated by the network POA with MIHF, i.e. via beacon, out to the mobile terminal for start of MIH interactions. d903g2225v,Identified as Issue 60. no suggested remedy.wRejected 2006/07/20 2006/04/049EJeffFKeatingGMember^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.J5j $^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…GmathieuhperesseTIbaddlsapandcssapalsomihnmssapshouldbesimplylistedDVaddmihlinksapinthefiguredeleteothersapswhichmaynWVaddmihlinksaptosection7.1.2CVaddmihfmobilenodemihnetworkBVCVaddmoredescriptivetextmoveexamplequeriestotheannexVaddmoredetailtotable11VqueriestotheannexVaddmoredetailtotable11VVCVion7.1.2CVaddmihfmobilenodemihnetworkBVCVCVion7.1.2CVaddmihfmobilenodemihnetworkBVCVCVhnetworkBVCVCVtextmoveexamplequeriestotheannexVaddmoredetailtotable11VaddmoredetailtothecostiedefinitionVaddmoreinformationonscopingofthestandardVaddnewsectionsprobablyaftercurrentsection8thatdetaVޚVV V:VxVaddnewsubsectionsandtextinbothsection5andsection'VޥVVVEV߃Vaddqueryresourcelistattheendoftheparameterlist܎Vbfix%W&W۠W݅W݆W݇W݉WݭWfixit݅V݆V݇V݉VݭVfixtheinconsistency%V&Vfixtypotowardtheendoflineall۠VfixedsWܑW'W^WflagۂWflexibilityAW_WiWflexibleAWWflagۂ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۫W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/W/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€.1025z+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/07/20 2006/04/28 oA communication across different access technolgy is what is expected next upon completion of such status reporting.d851g2269 2006/07/20 2006/04/28+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>c23g2268 2006/05/14 2006/04/28*EPeretzFFederEPeretzFFeder celementsKWZW]W_WW@WCWܘWܺWWWWelse2W:WWelsewhereܛW~W.WAWelsewhereinthedocument.VembeddedtWݸWWenable݂WenablesۋWencapsulatedWޏWencapsulatedrouteradvertisementisencapsulatedޏVencodeےWencodedJWencodingJWGWWXWWencodingsWWend-to-endWengineWݎWenglishjWkWmWnWoWzW{W|W}W~WہWہWہ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ނVtypelistdWtypes?WAW_WjWmWW=WJW`WdWܤWܷWܾWWhWݖWWIW[W^W0WtypicalWtypicallyAWܤWܱWݎWWWtypicallyinaheterogeneousnetworkenvironmentcomposedofܤVtypo۠Wucd|Wudp/ipWudp/tcpsWue܋WsedofܤVܤ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 Wget_WdWeWlWWOWWzW݊WWWWWWBWxWޅWޔW=Wgets݊WgetstatusresponsesetWgiveTW_W}W~Wgiveexampleoperationsofhowthemediaindependentinforma}VgiveniWsWoW}WWW8Wgives݂WgmmCWgni@Wgo\W]WܼWgoes\WܼWܼWjeev *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[W\W%W&W)WRWܑWܔW,W|W1W6W;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݀W63~W65W4W690vWvWvWvWvWvWvWvWvWfeder…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…ajay5rajkumarc"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 2006/07/20 2006/04/30 EMathieuFPERESSEGObserver^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/07/20 2006/04/3023 EMathieuFPERESSEGObserver^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/07/20 2006/04/30MarkedMarkedMarkedUrcenough@entries@environment@Berror@ event@events@Vexactly@Nexcluding@,execution@expansion@Uexplainusageofthewordmedia@field@fig/table@:fig/tableifapplicable@figure24doesnotrelatetothesection8.3weputittosh@figures@fime@finalized@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#bpairFWGWpairsCWsCWCWCWCWingWpairFWGWGWWWWWWWWWWWWWWWWWWWWWW 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 w4cA 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.  d562g2217 2006/07/20 2006/04/305EJinFLeeGMember^Technical, Non-binding_85`29a7.4.4.1bA[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  @ >c---- | | | Bit 5 : Emergency Seacone_WaWbWiWۄWۋW'W:W=W@WKWLWeWzW{WܗWܝWܩWWWWWWWW+W݆WݏWݜWݝWݞWݠWݣWݤWݦWݧWWWWWWW'W/W>W1W<WoneofmanyVoneofthestackmaybeVonesە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#sanjeeviVEDasFSubir^Technical, 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" d33g2415vPragraph has been deleted.w Superceded 2006/07/20condition of access networks"mAccepted-Modified 2006/07/18EDasFSubir^Technical, 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" d33g2415ical, 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 used329 2006/05/14ESanjeev, 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 used329 2006/05/14ESanjeevMb31ۉWRW1W6W32XWTWUWVWWWXWcW33ۉWcWݳW33aW34ۉW3493W35ۉW35-40W36ۉW37-43`W3753:W38ۮW=W38-49=W39=W3gW3glink1W3gpp۽W۾WYWHWsWWWXW3gppsystemsalreadybroadcastV3gpp/3gpp2W3gpp2&W'W1WHWsW WYWYWYWYWYWYWchengdaleydavid.1famolari,-/0feder  !"#$%&'()*+gomie23groetingܑܒܓܔܕܖܗܘܙܚguimingۄWܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܙܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚܚathalye@_#&N%`athalye#sanjeev  h1bDrvices Y/N | | | | Bit 6 : MIH Capability Y/N | | | | Bit 7 - 31 : Reserved | V@A   UU-  33/ 33H  33I  f h 33  33 | | Bit 3 : IP Version 4 Y/N | | | | Bit 4 : IP Version 6 Y/N | | | | Bit 5 : Emergency SebiliJ Rbfor8W9W:Wforconsistencywithuseselsewheremobilitymanagementiss۝Vforexampleitwouldbelikesayingdoyousupportrfc4889Vforexampleradiusnas-port-typeݔVforthefirstcommentthemihmightalsonotifythelocalmiVforthemultipleoctetlengthrepresentationshowthatfirstVV9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9Wn†tan†pekyewotan†kenichip  taniuchi†taniuchi i†kenichiq taniuchi†kenichir 4taniuchi†kenichis taniuchi†kenichit taniuchi†taniuchig†kenichiu taniuchiJ7EJinFLeeGMember^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>us' valuse can be taken from the values defined in section 8.4.2.17 , or vice versa.d647g2220 2006/07/19 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 | !(ݪb8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc-Link Identifier is missing in the parameters.d626g2355vby 527w Superceded 2006/07/20 2006/04/28ݫE YoshihiroFOhbaGMember^Technical, Binding_93`49a 7.4.9.2.2b8Adopt suggested change in 21-06-0xxx-Link_Identifier.docc-Link Identifier is missing in the parameters.d634g2356i Vivek GuptakSame as comment 626mRejected-Duplicatevby comment 527/626w Superceded 2006/07/20 2006/04/28 ݬE YoshihiroFOhbaGMember^Technical, Binding_94`32a 7.4.10.1.2b8Adopt suggested change in 21-06-0xxx-Link_Identifier.doccTSuggestedNewPoAIdentifier is not needed if it is part of SuggestedNewLinkIdentifier.d636g2352vby comment 527/626w Superceded 2006/07/20 2006/04/28gested change in 21-06-0xxx-Link_Identifier.docc-Link Identifier is missing in the parameters.d634g2356i Vivek GuptakSame as comment 626mRejected-Duplicate 2006/06/30 2006/04/28V7cFigure 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/07/20 2006/04/3024 8EJeffFKeatingGMember^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.c 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 |  *vA 33<  33? 33@  33E 33u  33x 33{  33cfigure24doesnotrelatetothesection8.3weputittosh7Vfigure24isincorrectinparticularitimpliesmihfusingiwVfigure30inannexa-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-@?EAjayFRajkumarGMember^Technical, Binding_40a6.2.2buChange the lefthand stack name from "Local Stack" to "Peer1 Stack" and change righthand "Peer Stack" to "Peer2 Stack"cLThe names of the two stacks should be changed to reflect their "peer" statusd288g2256 2006/07/20 2006/04/2817@EAjayFRajkumarGMember^Technical, Binding_42a6.3.1b Expand "GNI" in the acronym listcGNI not in the acronym listd311g2219wAccepted 2006/07/20 2006/04/2819 AEAjayFRajkumarGMember^Technical, Binding_42`19a6.3.1b="handover module" should be replaced with "network selector".c6"handover module" is never defined or used elsewhere. d314g2239wAccepted 2006/07/20 2006/04/28 BEAjayFRajkumarGMember^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..confirm.o.confirm.ukmaybeweshouldmodifyfigure12andshowmihlinksapandc6VmeanAW_WbWWoWmechanism/WWmechanismsWmedia0WܺWWW+WOWmentionݻWmentionedܶWSWmesaurable-WmessageWmessagesWmethodsWmihuW۾WWOWWW+W6WOWmihfunctioninthenetworkmayadvertiseitsmihcapability+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,W?WAW۝WWܤWܴWWIWW"W3W4W5W7WޕWmobility-managementGWmobilitymgmtprotocolޕWmodel$WۮW,WTWUWVWWWXWcWnW݂W݃Wmodelaftersimilarclauseonpage17line38ۮVmodificationsSWmodifiedޗWmodifyW3W5Wmodifythesection7.3.7.3asfollowing3Vmodifythesection7.4.4.1.2page85line305Ve85line305V5Vthesection7.4.4.1.2page85line305V5V85line305V5V.4.4.1.2page85line305V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5V5VWWmomentWmonthHWmoreAWPW_WqWۢW۽WWWܰWWWWWWWWNWIWXWYWށWރW޿WWW.W_WnWߝW߬WWWW(W T6bB | | 1: LINK_LOW_POWER | | | 2 : LINK_POWER_DOWN | | | 3 : LINK_NO_ACTION | | |4 : LINK_RESOURCE_RETAIN | | |5 : DATA_FORWARDING_REQUEST | C | |6 : BI_CASTING_REQUEST | | |7 : HANDOVER_CANCEL | | |8 -31 : RESERVED @A>  33_ 33} >con | Bitmap | 0-31 | 0: LINK_DISCONNECT | %`%%%&&-5#^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 2006/07/20 2006/04/28#EPeretzFFeder^Technical, Binding_104`41a 7.4.14.1.3bf  33      33  33cc Add context transfer d644g2260 2006/05/14 2006/04/28EEleanorFHepworthGMember^ Editorial_2`7a1.2bAmend sentencecWould be good to cite the specific technologies as examples (rather than implying an exhaustive listing) and also include wired examples. d10g2219 2006/07/20 2006/04/28EEleanorFHepworthGMember^ Editorial_5`30a2bAmend referencescqReferences to 3GPP standards should include an indication of which version of the standard is being referred to. d41g2225 2006/07/20 2006/04/28EEleanorFHepworthGMember^ Editorial_17`52a5.3.1bjAdd clarification in text that all reference points are within scope and remove the column from the table.crNot clear why the "Scope of definition" column is needed, as all reference points are in the scope of IEEE 802.21 d123g2226 2006/07/20 2006/04/281EEleanorFHepworthGMember^Technical (was Editorial)_18`55a5.3.2bAdd clarification to text.crences to 802.11 to IEEE 802.11gbcollectsܡW,Wcolors݃WcolumnW=W>W?WYWWWWWcombinationsWnWݕWW WcombinationofactionsispermissiblenVcomeܰ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(ƒ(84EJinFLeeGMember^Technical, Non-binding_80`65a7.3.17bA[Insert 'IP_Renewal_Indicator' in section 7.3.17.1, Page 80, line 65] : Parameters : --------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | Description --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Valid Range | Description ----------------------------------------------------------------------------------------------------------------------------g2211 2006/05/14 2006/04/301EJinFLeeGMember^Technical, Non-binding_54`14a 6.3.4.3.6<-EEleanorFHepworthGMember^ Editorial_43`32a6.3.1bChange radio to interface.c=What is a 3GPP2 radio. Do you mean using a 3GPP2 interface? d328g2238 2006/07/20 2006/04/28EEleanorFHepworthGMember^ Editorial_43`45a6.3.2bChange to policy engine entity.06/04/2819EEleanorFHepworthGMember^ Editorial_43`32a6.3.1bChange radio to interface.c=What is a 3GPP2 radio. Do you mean using a 3GPP2 interface? d328g2238 2006/06/18 2006/04/28EEleanorFHepworthGMember^ Editorial_43`45a6.3.2bChange to policy engine entity.g2237 2006/05/17 2006/04/2819EEleanorFHepworthGMember^ Editorial_43`32a6.3.1bChange radio to interface.c=What is a 3GPP2 radio. Do you mean using a 3GPP2 interface? d328g2238 2006/05/17 2006/04/28EEleanorFHepworthGMember^ Editorial_43`45a6.3.2bChange to policy engine entity.EEleanorFHepworthGMemberKlvbaddtwogroupstokeepconsistentwithtable6;VaddedAWZW]WWWW}WWWelated 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ۉ dDT?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 2006/07/20 2006-04-30@EXiaoyuFLiuGMember^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". c DÃ10 Ã1@Ã1PۿÃ1`EÃ1pÃ1Ã1 Ã1Ã2/Ã2 GÃ20Ã2@0Ã2PWÃ2`<ÃE`ZÃEp=ÃEےÃEۓÃF@>ÃFPAÃFpÃF[ÃF?ÃG @ÃG0 ÃG@ÃG`ÃGBbgreater_WXW~WݗWgroupۂWWgroups?WWW;WgsmWPWgsm/gprsJWguarantee WguidelineWguidelinesWh2WWhissuedVh-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(VbdetectionVWXW Wdeterminded5Wdetermine#W݂Wdetermined WޖWdeterminesW\WdeterminingWdeveloped_WdeviceۜWWܫWܶWdevicetoreconfigureandpresentdatatoupperlayersVdevices_Wdhcp\Wdhcpv6WdiagramۿWܳWW>W8Wdiagram/textWdiagrams/useܴWdicoveryuWdifferences*Wdifferent W"W?WAWMWOWPWQWTWUW_WpWuWۙWrWܤWܳWܴWܾWܿWW0WQW݃WWWWPWޅW3WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWBEXiaoyuFLiuGMember^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/07/20 2006-04-30CEXiaoyuFLiuGMember^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/07/20 2006-04-30DEXiaoyuFLiuGMember^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.d915g2222e 4.d914g2221 2006/05/14 2006-04-30LcjustificationuWyWjustified:W;W<W=W>WBWEW[W^WjWkWmWnWoWuWzW{W|W}W~WہWkWkeptWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWjWkWmWnWoWzW{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}bbracketsWfWbranchbWbreak4W5WWWbreakoutthesegmentstartingwithinwhichcaseintoasepWVbreakthesentenceafterthecomma4V5VbroadcastWۈW#WPWWPW9Wbroadcasting+WbsܵWbssid[WbstnܵWbufferUWbufferingVWbuffersUWbutۜWW܋W݊W9Wby"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ބWޅWއWދWތWWWWWWWWWWWWWWWWyoshihiroohba„8Ig2378vby comment 527/626w Superceded 2006/07/20 2006/04/28E 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/07/20 2006/04/28_ܵGMember^ Editorial_42a6.3.1b6Include a legend for Figure 19. (BS, AP, BSTN, etc...)c8Legend for Figure 19. (BS, AP, BSTN, etc...) is missing.d310g3232 2006/07/2019ܶEVivekFGuptaGMember^Technical, Binding_43`26a6.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/07/20 ܷEVivekFGuptaGMember^Technical, Binding_44a6.3.2ba6.3.2b in Table-6 with their corresponding description in section 6.3.4.  need to be deleted.^ted.^new vcomment104ܦVcomment492EVcomment4952Vcomment527/626ݮVcommentisintwopartspart1istoaddtypeienetworkcap Vcommentisunclearastospecificallywhatpartisunclear݀VcommenterjWkWmWoWyWzW{W|W}W~WہWۆWۇWۊW_WݏWWcommentertoprovidesuggestedtextݏVcommenter'snW"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.d914g2221 2006/07/20 2006-04-309Ã:pÃ:KÃ:܏Ã:ܴÃAÃA ÃA0ÃAP/ÃA`ÃApÃA:ÃAÃA;ÃBܵÃB0}ÃB@LÃB`?ÃBp:ÃBÃB@ÃBÃCÃC ÃC0AÃC@MÃCPÃC`ÃCpNÃCܶÃCÃCÃDݓÃD KÃD0ÃD@ÃDPOÃD`ÃDpÃDPÃDQÃDܷÃE clayers*WۅW۪W۵W6W9WRWYWcWmWܢWܭWWWWW0W݇WݍWݎWWWWW WW,WlbWlead۶WWWWlearnېWlearns۳WleavingܩWleft-WW0WleftmostqWlegendܵWlegendforfigure19bsapbstnetcismissingܵVlenght=WlengthW%W&W(W)W=WAWBWMWwW|W WWXW~WݵWW'WtWuWlengthis2octetswhereasietable6saysitis4octetsth&Vlengthisvariablewhereasietable6saysitis4octetsth%Vhepworthƒhepworthx&ƒeleanor hepworthƒhepworthQSƒeleanor hepworthƒeleanor hepworthƒhepworthFRƒeleanor hepworthƒhepworthFbƒeleanor hepworthƒhepworth7Yƒeleanor hepworthƒhepworthhTƒeleanorc8 bas9WasfollowslVlV9W JEFarrokhFKhatibiGMember^Technical, Non-binding_37`29a6.1.8b`Define if link events are envisoned to be used for MIP handoff within APs of the same technology]j)‚#^q*ÄWZ_r+‚6`s,‚fa-b.‚Yc/‚Dd0‚7e"1‚uf" 2‚rg"03‚sh"`4`i‚9j"5‚Bk#06l‚im#@7Ä23n#`8Ã"o#p9p#:‚1q$;‚Sr$<@s%`=‚3t%>u‚gv%?eunah@ronnyCkim@QAsB ?eunahA‚Qy@QBz@sCDDWE ?ronnyD {CDE‚c|CWFbenjaminGkohGSHYIJ FbenjaminH}GSI‚'~GYJ‚*GK'.bdepending@rdeployment@destination@Zdetailed@fdetails@detected@detection@different(direct@discover@ditto@done@each@eitherintable6itshouldbevariableorthistableshould@elsewhere@fencoding@entire@entities@entity@&established@_estimation@event@events@examples@expected@-extraneous@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ƒ  khatibilcthen7W9WCWOWܢWWWWthereWW-W?W@W_WaWuWۇWېWۦWWWWW WDWEWMW\WcWjWܐWܖWܘWܩWWWWWWWW WW:WSWeW݂WݥWWWW W2WfWgWޕWޗW7W8W;W=W>Wthereare256possibleencodingsforgeneralVtherearenoargumentsforcapabilityofinformationserviceݥVtherearenoidvaluesdefinedformihfunctionidsessioniVtherearenovaluesdefinedforstatussincetheexchangeofܖV$‚anadagolmiemember]`‚bc'‚cnadagolmiemember^b‚deyA‚enadagolmiemember_d‚fgyH‚gnadagolmiemember`f‚hiHF‚inadagolmiememberah‚j   *r3‚kljv‚lnadagolmiememberbk‚m ޕbC~ -----------------------------------------------------------------------------------------------------------------------------Z@A> 33  33>cAThe 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/07/20 2006/04/30b Ablayers@Wlayers/mihf۵WlearnېWlearned۶W۶W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7Wxie€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„ESanjeevFAthalyeGMember^ Editorial_43`4-5a6.3.1bCChange "point of attachments" to "points of attachment" or "PoA's".c Plural formd332 2006/07/20ESanjeevFAthalyeGMember^ Editorial_44`11a6.3.2b+Change to "may influence handover decision"c Improved grammar (verb vs. noun)d342 2006/07/20ESanjeevFAthalyeGMember^ Editorial_44`11-12a6.3.2bY"Other information may be vendor/network specific, and could be specified appropriately."c Streamline.d363 2006/07/20ESanjeevFAthalyeGMember^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/07/20 ESanjeevFAthalyeGMember^Technical, Binding_45`46a6.3.246a6.3.2ve implied limitation, better explain used329 2006/05/14ESanjeev19=EXiaoyuFLiuGMember^ Editorial_62`12a6.3.9`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. d907g2214 2006/07/20 2006-04-30=EXiaoyuFLiuGMember^ Editorial_62`12a6.3.9binding_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. d907g2214 2006/06/18 2006-04-30=EXiaoyuFLiuGMember^ Editorial_62`12a6.3.9oyuFLiuGMember^ Editorial_62`12a6.3.9K cthe8W9W:W;W<W>W?W@WAWBWCWDWthe1sttwosentencesintheparagraphrepeatswhathasalrevVthe2ndoctetitselfdoesnotrepresentthetotalsizeofthFVFVFVFVFVDa6.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|݉ݔݕݖt;;t;;###################################### cthisneedtobere-writtenasaproperreferenceVthisprimitiveisdeliveredfrommihfunctiononoldpoato"VthisprimitiveisissuedbyupperstocontrollayerlinksVthisprimitiveisissuedbyupperstodiscoverthestatusofVthisprimitiveisusedastaion'smihisnotalwayscorrectއVthisprimitiveisusedbyamihfunctionontheservingnetw!Vthisprimitiveisusedbyapeermihfunctiontocommunicate%VisprimitiveisissuedbyupperstocontrollayerlinksVVVVVVVVVK Ocwhichwhichstandardisthiswhyonlyoneieexampleisprovidedi'V?EQiaobingFXieGMembernDvKby comment 495. Update as per resolution of Handover commands and resubmit.w Superceded 2006/07/20 2006-04-30cedures.doc cTAdd a section for the example handover scenarios between 802.11 and 802.16 networks.d915g2222 2006/07/20 2006-04-30V^Technical, Bindingd900i Vivek GuptajIt's not clera what is meant by "persistent URL" and a standard cannot be in a position to specify persistent URL locations....mRejectedn 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.mRejecteded LinkParameter 33 2 Pramaeters for which link uture connections. When higher layer connections are being established over this link, the Transport la established over this link, the Transport la"JcinWW%W&W'W+W:W;W<W=W>WAWCWEWJWNWZW]W_WaWbWhWqWuWvWwWۀ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ܾWWWWWWWWWWWWWWWWWWWWWWWWWW W0CbgenericFWGWHWIWJWۼWYWW2WW2W2WW2W2W"W"W"W"W"W"W"W"W"W"W"W"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*W,W-W.WLWMWOWPWQWRWSWTWUWVWWWcWdWlWpWsWuWېWWW#W7WZW\W܅WܫW0WDWIWݎWWWWWW WW W!W"W%W'W+W,W/W0W1W2W3W4W5W7W8WބWޅWއW2W3W5Wyoshihiroݕohba„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„#ݝE YoshihiroFOhbaGMember^Technical, Binding_74`48a7.3.10b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacOldPoA should be replaced with one unified LinkIdentifer TLV.d533g2342w Superceded 2006/07/20 2006/04/28 ݞE YoshihiroFOhbaGMember^Technical, Binding_75`64a7.3.11.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc cSMacMobileNode and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d537g2343vby comment 527, 626w Superceded 2006/07/20 2006/04/28ݟE YoshihiroFOhbaGMember^Technical, Binding_77`7a7.3.12.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc c9MacMobileNode should be replaced with LinkIdentifer TLV.d541g2344vby comment 527, 626w Superceded 2006/07/20 2006/04/28ݠE YoshihiroFOhbaGMember^Technical, Binding_77`49a7.3.13.1b9Adopt suggested change in 21-06-0xxx-Link_Identifier.doc | | T E=@ b?b@cABEDv^^^D@^LbBDcPBD6c:@^D@^@^B@D@^@^D@^&cmnۇW۳W۴W۸WWܞWܩWܺW W+W2W;WLW݂WWWZW9Wmns:WmobilWmobileWWiWۉWۏWۦWWWW.W3W4W:WܝWܡWwW{W|W݊WݏWW"W#W$W/WPWZWޕW1W8WmobilenodenetworknodethatmaychangeitspointofattachܝVmobilenodewithmihfunctiongenerallyhasseveraldifferenۉVmobileterminalchangetomobilenodeۏVmobile-ipjWmobility"W:WܤWܴWWݐWWW"W7WXWYW_W`WޕWޖW:WmobilitymanagemententitiesaremerleyshownasapossibleVmobilitymanagementprޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWޕWJiEDasFSubir^Technical, Binding_62`1a6.3.9b+Remove MIH_Get_Info.confirm from Figure 22.c.MIH_Get_Info.confirm primitive is not defined d475g2400vby 473w Superceded 2006/07/20Marked Figure 22_Info.confirm from Figure 22.c.MIH_Get_Info.confirm primitive is not defined d475g2400vby 473w Superceded 2006/07/19Marked Figure 2217EDas,FSubir^Technical, Binding_87`59a 7.4.5.2.2bAdd GetStatusResponseSet.c GetStatusResponseSet is missing.d605g2369 2006/05/178.4 (8.4.1-8.4.2) d760g2228 2006/05/1420EGregFDaleyGMember^ Editorial_77`26a7.3.13baConsider adding UniqueEventIdentifer for Link_Detected and Link_Handover_Imminent. cble): Table 20/Table 21 - Section#: 8.4 (8.4.1-8.4.2) d760g2228 2006/05/1420convert the data so they match an agreed schema (this doesn't mean you have to send XM= =bQReplace the MIH_Get_Info.response (line 20) with MIH_Get_Info.confirm (line 12). c9There are two MIH_Get_Info.response in this flow chart. d908g2215 2006/07/20 2006-04-3022>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 2006/07/20 2006-04-3013?EXiaoyuFLiuGMember^Technical (was Editorial)_77`65a7.3.13.25_bdefinesAWpW۟W=WWW8WdefiningAWdefinitevWWݹWdefinitionW W#WJWZW]W۴W۶WWW W WWW/W3W4W:W`WcWܜWܝWܪWܬWWUWYWWdefinitionofnetworkoperatorinmiddlecolumniscicrcularV"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"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„ibi ۂbA 7.4.10.1.2 Semantics of service primitive The parameters of the primitive are as follows: MIH_Handover_Initiate.request ( SourceIdentifier, DestinationIdentifier, CurrentLinkIdentifier, SuggestedNewLinkIdentifier, SuggBestedNewPoAIdentifier, HandoverMode, CurrentLinkAction, QueryResourceList SuggestedNewLinkIdentifierUnchangeable ) --------------------------------------------------------------------------------------------------------vNENada, Golmie, Member^Technical (was Editorial)_64`31bA'In the Description field, replace "When 802.16 MAC receives neighbor advertisement (MOB_NBR-ADV), this primitive is used to deliver the information to upper layers." with "When 802.16 MAC receives scan response (MOB_SCN-RSP), this primitive is used to deliver the information to upper layers."'@Af  33U  33`  33  33  33fhen 802.16 MAC receives scan response (MOB_SCN-RSP), this primitive is used to deliver the information to upper layers."'@Af  33U  33`  33  33  33fMOB_SCN-RSP), this primitive is used to deliver the information to upper layers."'@Af  33U  33`  33  33  33f BX hctheWW W%W+W0W2W3W6W:W;W@WAWCWDWEWEWEWEWEWEWEWEWEWe 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 `%1JvallowWWalone{WalongܢWalreadyRWWܗW1W0Walso۵W WܗWW W݊WݓW"W7WNWiWalternativelyWalthoughWalthoughthesubsequentsubsectionsspecifiestlvstobecarValwaysgWamendmentsWWamong3WanlW@WܐW W;WSWݓWSWand'W0WTWZWaWlWۆWۉWێW۔WەW۳W۴W۵WWWWWWWWWWW W)W1W=W@W\W`WqWܐWܗWܛWܾWWWWWWWWWW2W:W;WFWVW`W{W݃WݓWWWWWWW"W4W5W6W7WKWSWVW`WiWޏWޗW9W:WDWannexWoWX HkwereWDWwhat0W_WۓW۵WW|WܸWWwhatisapageinthiscontextVwhenW+WwhereܶWwhich"W۴WWW݀WwhileWWWwhileuseofschemaisanoptionrequiredonlyforxml/rdfqVwholeW-Wwhy\WjWkWmWnW.NcpThe descriptions of items 3 and 4 are identical. The primitive M_ScanScheduling is relative to scan information.d488g2265i Ronny KimmAccepted 2006/07/20 OENada, Golmie, Member^Technical (was Editorial)_62`10bA=Replace "MIH_Get_Info.indication" with "MIH_Get_Info.request"=@Af  33  33   335  33<  33fcImproper use of the"MIH_Get_Info.indication" when a command is a request requiring a response. The Request is propagated from Local MIHF to Remote MIHF and then to Information Server.d477g2267i Eunah KimkQInformation Server would be one of MIH Users, so indication primitive is correct.mRejectedvby comment 473w Superceded 2006/07/20Marked22 ‚sHA‚DID‚:JH‚vKQ‚%L‚vMS‚5N‚XO‚fP‚gQT‚YRÄIZSU ‚1T!Lccontext_WaWWWWܯWܾWW[W\W]W!W>Wcontextual_WaWcontinuesWcontinuityWcontradictoryWcontradictsWcontradoictedWcontribution܏WܮWcontroliWkWWWWWWW5W@Wcontrolled@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+WdW>WcostBW_WaWHWW~WPWWWWWWۊWWWZWWW W+W݂WݏWWKWQWTWfWhWcounterpartWcountriesSW# FkwhyoWzW{W|W}W~WہW=WܺWܻWWwhyitisonlydhcpaddressthereareseveralotherwaysone\VwiderWwillAWWݻWwith/WaWbWۓW۾WWWWW)WwithinW|WwithoutjWkWmWnWoWzW{W|W}W~WہWWwork۾WWworkingܸWwould"W/WWOW)W+Wwouldsuggesttoidentifysomecommonmechanismtoaidinco/Vwouldsuggesttoidentifysomethinglikethisasanessentia"Vwouldn'tWwwwWxmlWW|Wxml-basedWxml/rdfjWkWmWnWoWzW{W|W}W~WہWWWWWoWxxxݻWyesWܹWyesitneedsfurtherclarificationabdalsotable7needscaܹVyouWWRcded schema is unknown. @AR 33  RcWccouldۊWWWZWWW W+W݂WݏWWKWQWTWfWhW9W<WcounterpartWcountriesSWbhenceRWܬWhereWWfW;W<Wheteroge_Wheterogeneous"W?W_WۙWWܤWܴWWhetrogenousWhexbinary~Whide݃Whidel2sublayerstheyareshownindetailsineachspecific݃Vhigh#W?WܬWhigher#WAWOWPWQWRWTWUWWWܤWW;Whigher-layerWhighlyWhighlyconfusingtoseetheconceptsrepeatedintlvandV-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W~ bindicateWRWwWWݗWWOWindicatesFWTWUWVWWWXWYWcW|WݗWindicationUWVWWWW9WOWRWUW\WyWݍW>WsWxWޕWindicationsTWUWVWWWXWindicator4WindividualۂWܽWSWindividually۳WinfluenceWinfoWOWܗWܘWܙWzWWBWxW=WinfomrationW%WinfoqueryparameterskWnWܕW}Winfoqueryresponse|WވW|Wވ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 @ 0a@%† sreemanthula)(†"kenichi@.-†Dtaniuchi0 @ @ @ }bchange!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?WEWFWGWHWOWRWlWyWzW{W4W5Wh …jperetz  ifeder_'bentityLWMWUWdWuWWۂWېWۚWۭW,WZWfWܡWW݊WW"W%W/W8W9W=W2W3WentriesܹWentryWkWݛWenumerated\WenvelopeWenvironment,WWܤWIWenvisonedJWequipmentWerrorFWGWHWIWJWۉW\WesbWpWes/cs/is݃WespeciallyUW1Wess?Wessential?WܽW'WessentiallyWessentiallyanisclientcanaskforcertainclassesofVestablishܡWܡWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWestablishingOWSW_WbWWWmWqW߫W߯WMyoshihiro݆݈݅݇݉݊݋݌ݍݎݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟݠݡݢݣݤݥݦݧݨݩݪݫݬݭݮݯݰݱݲݳݴݵݶݷݸݹݺݻݼݽݾݿƒÃăŃƃǃȃɃʃ˃̃̓΃σyuanۅۆ‚562I‚6nadagolmiememberG5‚787‚8nadagolmiememberH7‚9nadagolmiememberI:‚:;? ‚;nadagolmiememberJ:‚<=?‚=nadagolmiememberK<‚>??)‚?nadagolmiememberL>‚@AM9‚AnadagolmiememberM@‚Bu‚CDBB‚DnadagolmiememberNC‚EFV!‚FnadagolmiememberOE‚GHBf‚HnadagolmiememberPG‚IJd‚JnadagolmiememberQI‚KL'‚LnadagolmiememberRKbdifferent3W3W3W3W3W3W3W3Wchandover:W@WAWBWCWDWhandovermoduleisneverdefinedorusedelsewhereAVhandoverneedsabetterdefinitionVhandovermode:bof:W@Wofmobileipv6withdhcpv6andVVVV5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W‚lmkv‚mnadagolmiememberbl‚npn&‚p3 wbthe8W9W:W<W=W?W@WDWtheaccesstoinformationshouldbefast۷Vthebroadcastmechanismwithlayer2transportwouldbediffPVthecreationthereinofanewentitytoanewentitycreatedۚVthedescriptionshouldbephasedinmoremediaindependenttVtheencodingformatisdefinedasshowninthetablebelowVVVVV!=bfunctionfunctionwhichisoptionaltoimplementVVV5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wderi…peretz+ feder…rajkumar…ajay, rajkumar…rajkumar*…ajay- rajkumar…ajay.  rajkumar…rajkumarJ…ajay/ rajkumar…ajay0 0rajkumar…ajay12  rajkumar…rajkumarS…ajay3 rajkumar…rajkumarY…ajay4NLocdefinesW4W5W7WnWdefiningWkW>WnWdefinitionNW|W~WۃWۅWۇWۓWۦW۫WWW W WW.W3W4W5WCW`WcWdWeWܛWܜWܬWWWoWwW7WKWޕWޗW@Wdefinitionofinteroperabilityandcompliancemechanismsisܛ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 taniuchisbuiuc|Wuk/currency/byHWumts_W=WCW W^WunchangeableۂWunclear۫W6W6W6WW6W6WW6W6W6W6W6W6WWCW 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-VbwherekWnWۂWTWUWVWWWXWcWpWܶWW݊WW W%W}W~WwhereeverCWwhether-WNWWWPWwhich-WFWGWOWPWQWRWSWTWUWVWWWbWkWnWpWuWWۇWۉWېWWWW#W=W\W]WWܕWܟWܡWܪWܺWWWW W WUWWWYW\WݍWݔWWW"W#W$W'WWW}WLWWݔWWW"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„,qcsuggestۘW4W6W7WsuggestrephrasingۘVsuggestedۂWWqW3W5WsuggestedrephrasingofgapsinradiocoverageVsuggestednewlinkidenݬWWsuggestednewpoaidentݬWW ;vby comment 352, 360w Superceded 2006/07/20 2006-04-306b@c A@bCcoFbAGHbB~DsKbNbA7O@[R@&bBS@TbA&UbAVbA*cW"XcQYcAZcA\bACEG^bAL`bcbA<necACgbvickcmbA@ YbAIt 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 Draftd427vby comment 424w Superceded 2006/07/20ZEFarrokhFKhatibiGMember^Technical, Non-binding_53`57a 6.3.4.3.5b4Instead of prefix, consider the use of network mask.cJInstead of prefix, the PoA subnet information TLV should contain the mask.d434v.Identified as Issue #42. No details provided.wRejected 2006/07/20[EFarrokhFKhatibiGMember^Technical, Binding_56`21-41a6.3.6.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.d453vby comment 361w Superceded 2006/07/20\EFarrokhFKhatibicananmihcapabilitydiscoverrequestfromtheterminalwouldnQVanmncouldbeattachedtodifferentnodesonthenetworkde+VanurlofbasicschemaisstillnotassignedމV~] cfor8W:W<W@WDWforbettersentenceflowۚVforitem1.2oftable6thenumberofoperatorsdoesnotnecVforitem7oftable2accordingtothedefintionofthiseveVforno1.2intherepresentationfieldifnetworksofthesaVVVHbasinthecommentސVޑVޓVasthesectionisdealingwithl2dataframepacketformatiVaskWasnWaspectsۖWWܸWWassembleܤWassignedXWCWxW~WމWފWassignments/radius-t=WݔWassignments/radius-tegieݔVassistWassistance݊Wtance݊W݊WGnUbinitiated,WRWܴW8Winitiates#Winitiation܅WinlcudesWinputܽWinsecure<WinsertWWWWWgW(WMWOWݿW0W1W4WinsertatendofsentencealthougnetworkconfigurationchanOVinsertatendofsentenceonlywhenprobabilityofaccessingVinsertbeforeorbyassociatinginformationcontainedinitsVinsertcommaafterfirstappearanceofnetworkMVinsertcommaaftermobilityVinsertiprenewalindicatorinsection7.3.17.1page80line4VinsertisbeforecalledV&n4vbyresolutionofcomment346@changetheprimitivedefinitionandtheprotocoldefinition@clarifying@comment۬ncomment104@commenters@confidencelevelisvagueandit'snotclearifvariouslink@yconfiguration@contributions@definitionݓhdeletethetext@do@&enabling@etc@=filter@!formats@Qfrom@handover@have@+identifiedin݃%insection7onlyhavedescriptionofevents/primitives@:intra-technology@[issueidentifiedsuggestedremedycannotbeappliedtoaspe@it-l2@linesܬ!list@mechanismsە\mn@~needݴneeds0noavailablesuggestedtextcommentassignedforfurtherwor@transportuse۳wherever@cwith@waccepted-modified"{lnoneneeded@G€ @FYYSZMGG$( db27@31@4@M4rdfschema@5.6.2.1@6@7@7.3.1@b7.4.4.1.2@{8.6.1.1@h802.3@a8ualinkupeventmayalsocarrynewipaddressrenewalacquis@ya-4@=access@uaccessing@across@-action@?actual@add8addafigureflowdiagramforsection8.6.1.1thatistheco@addanewsection7.3.1calledlinkeventid@caddanotesayingthathandoverisalsoreferredtoashando@addfollowinginformationelementintable6informationele@addh-aaainsection4@Taddlsapandcssapalsomihnmssapshouldbesimplylisted@in21-06-606-00-0000locinfo@W>^technicalWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWbto8W9W:W;W<W>W@WAWtoanewvalueallocateanewoneorsplittheentryVtoimproveconsistencyhandoverdecisionmodule.V.Va }cand9W:W;W>W?W@WDWandothertlvencodingsitisconceivablethattheseVand/or:W9W9W9W9W9W9W9W9W9W9W9W9W9W9W-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ۣWWWGWlWcustomaryuseVVlVcustomerWcutrrentWdWdrewordline40mobilipregistrationmightbenowtriggerVgerVV2csatisfyCWHWsaved&WsayWW5Wsaying/WWsaysWrW۾W%W&W.WZWWWyW݇WWWW;WscanۆWWNWmWscanschedulingNWscares݃WscenarioWݓWWscenarios\WۈWWDWWDWDWWWWWWZ* bmih8W=WAWBWCWmihcapabilitydiscoverresponse0Vmihcommandconfirmprimitiveshouldberemovedfromitscur>VmiheventderegisterconfirmresponserVmiheventregisterconfirmresponserVmihgetinfoindicationrequestxVmihgetstatusVmihhandoverinitiaterequestۂVmihinformationrequestrdfdataprefixmihbasicurltobea~V~VcgoesWEWFWGWHW3WgoingۅWW\WaW#WdWgong܈WgoodۓW'WWgov/nost/wwwclassic>WgprsWgrammarۺW)WgranularityWgre-WWgreatjWkWmWnWoWzW{W|W}W~WہWWgreaterXWWgroupWHWYWIWgroupsWW;Wgsfc>WgsmPWgsm/gprsFWGWHWIWJWguaranteeWguidance}WguidelineWgveܬWhWh-aaa:W݌Wh-aaaisnotdefinedintheabbreviationlist݌Vha-W:WWhadnover1Whand-WWhandleWnWWWhandledWWܛWWWhandlesWhandlingW WhandoffWܜWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJW a5.8.2܃݃5.8.3+66.1{6.1.1,Ix96.1.2ܲݑރ:6.1.3W;<6.1.36.2.2V6.1.4ăӃr6.1.5ݒ6.1.5.2-.߃6.1.6Nܳ6.1.7&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&.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ܯW WݴWWeWdependentonearliercommentonsection7.3.11.1eVdependingW+W6WW%WdepictedܔWdeployedܭWdeploymentWWܭW݂WdeprecatedWderegistereWW(WFWHWMWRWrWzWderegistrationWWdescribe'WeWWWdescribed+W_WjWkWmWnWoWzW{W|W}W~WہWۊWیW{WݒWݓWݛWݽWWWW6W4WdescribingܟW>Wdescribled݀WdescriptionjWkWmWnWoWzW{W|W}W~WہWۆWWW0W=W@WPW܅WܷWܹWW݄WݗWݾWWWWmW}WWބWޅW:WAWBWCWdescriptionofrdfdataunderinforquerytypeisnotcorrcet}VޅWޅWޅWޅWޅWޅW bnetwork8W9W;WAWBWCWnetworkidentifeirshouldbelinktypeݺVnetworkselectionistheprocessbywhichamobilenodeoraܡVWbl3sWܴW3WDWW0WlabelqWlabeled0WlacDWlanpWlandscapeWlanguage#WkWnWܬWqW}WlargeWlastܶWBWlat/lonSWlaternWܪWWlay݂Wlayer#WAWHWIWLWMWOWUWVWWWcWdWpWېWەWۣWWWWW/W7WSWTWZW\WcWeWfWiWkWܤWܫWܳWCWDWݍWWW WWW"W$W2W8WPWpWޕW3W;Wlayerare1Wlayered/WlayermihcW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3WcquestionWWWWquestionableۀWquickly'WquiteWWquotesWWWquoting:Wr1۴WWr1andr3inetrafceseemtobeinterfacesbetweenmnandnet۴Vr2Wr3۴WWr4ܪWWr5ܪWradioۂW۽WWWW+WradiusۓW=Wradius-nas-port-type^Wradius-nas-port-typeisunsuitableforourusesinceitdoes^VraexWފWran۽WrandomlyWrangeWWhWWoWW9Wrank/W9Wrank/W/Wank/W/WFPbnoteuW#WHWW)WnotedۖWWnothingށWnotificationOWPWQWRWSWTWUWVWWW\WޕWޖW5WWRWSWTWUWVWWW\WޕWޖW5W5WWRWSWTWUWVWWW\WޕWޖW5W5WWRWSWTWUWVWWW\WޕWޖW5W5WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW[cobtainېWIW݂WobtainedېWܬWWWobtianedܬWobviousQWobviouslyۄWېWoccupiedWoccupieszW{Woccur^WoccurencesܥWoccursۨW WܟWWWocteswWoctet(WFWwWWoctetsW%W&W)W=WAWBWFWWWoduWoduWuWuWuWuWuWuWuWuWtskomraWXYZsoohongsreemanthula[\]^_`abcdefghijksubir  !"#$%&'()*+subritaisuke݀݁tanlmnotaniuchipqrstuvwxyz{|}~ހށނރބޅކuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuucclearlysWܪWܴWW WWclearlydefinewhichreferencepointsarenormativeandwhicܪVcleary{Wcabout#W+WKW_W`WaWۆWۇWۊWېWWWWWWWWWݏWWWWWdWgWaboveWWW#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*Waccessing۾WaccomplishWaccordingۂWۅWW:Waccordingtorfc3753thedefinitionsarequoting:VaccortingoWaccountWaccurateXWaccuratelyWachieve|W"W#W$Wachive*W*W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$W$WV,cexactly W݃WexamineܱWexaminetheusageofthewordtypicallyinthedraftandremܱVexample_WaWeWۈWېWےW۪W۵W۾WWWWWW'W-W:W@WiWܙWܼWWWWWW WWW W:W[W~WݔWWNW@WDWexamplequeriesneedmoredescriptivetextandshouldbeinVexamplesW`WW\WWexamplesprovidedlackcontextrequestingsuchinformationwVexceptW2WexceptionWexceptionalېWexcerpt>Wexcessive9WexchangeWܖWWexchanges>WexchangingܩWexcludesޕWeKbthresholdsFWGWۉWRW\W`W{WޔWthroughpWW7WWW?WthroughoutWtidWtifyAWtimeAW\W]WܳW:Wtimeinterval\WtimelyWtimerW&WޖW5Wtimerandreleasethesavedcopyofthepacketthesourcema&VtionAWAW5W5W5W5W5W5W5W5W5W5W5W5W5WIbnotification5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wd|bprimitivespWۉWSWnWܐWܴWWWW0WyWW8W>WlWmWކW>WLWbcommonܪWܾWWWcommonlyWcommunicatepW7WW!W%WcommunicatesW_WcommunicatingW7WcommunicationuWxWۖW܅WW3W݂W WcommunicationsiWcomplement8Wcomplete/W0W5WWWRWcW܉WWcompletedWWRWcompletelyYWܓWcompletionWcomplianceWcomposedܤWWWWWWWWWWWWWWWWWWWWWWWWWWW ^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/Wcbe2W3W4W5W6W7W8W:W;W<W>W?W@WAWBWCWbeconsistentwiththemdeiadependentandmediaindependentVVV8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8WcexpansionWܠWܼWexpected^W*WexplainەWۖWWܴWWWWWW4W5WexplainthattheremoteflowofeventsandcommandsforfiguVbsplitWWsquareWfWsrcݴWssid[Wstack/W7WqWܫWDWݎWW2W9W<W=W?WstacksW WstagesܳW1 4cA"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/07/20 2006/04/245EQiaobingFXieGMember^Technical, Binding_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/07/20 2006/04/2419 6EQiaobingFXiecparticularuWwWWW WWWݏW>WIWpartlyWpartner_WaWpartners_WaWpartocularZW]WpartsەWWWW'Wpartsoffigure30areveryhardtoreadVpassSWWpassedW0WpassingSWpayloadWtWݸWW'WpdsnWpdsn/fa-WWpduWpeer{W!W%W3W<W>W?W1WpeersW>WgWpending WpeopleWperWeWmWvWWWperlastmarch06denveracceptedcommentresolutionaddanVperformuWۂWېW|WperformanceWW|WݍWperformed3Wed3W3W3W3W3W3W3W3W3W3W3W3Ww^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+crepresents=WWreques/responseܙWrequestۂWۃWۄWۆWۇWۈWۍWێW9WMWOWQW`WkW܀W܄W܅WܕWܗWWW%W>WCWJWQWiWjWsWxWކWޗW<WrequestsourceshouldberesponsesourceۍVrequest/responseܺWWޗW6WrequestedaWrequester:W;W<W=W>W_WaWrequestingW\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\WE bthat8WthatsWW8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8Wd‚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‚݋‚݌‚‚‚‚ܠ‚‚S‚۩‚n‚‚ܡ‚ܢ‚/‚ܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣܣ^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#WAWLWNWOWUWbWpWxWۂWېWەWWWW7WCWTWUWVWWWXWYW\WcWsWtWxWܪWܴWܺWܾWWWW W(W*W0W1WJWjW|W݃WݖWݗWݸWWWWWWWWW2WކWފWޔW߱W߱W߱W߱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܋WޕWestablishingOWSW_WbW_WbWbWRW܋WޕWestablishingOWSW_WbWbW_WbWbW+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W`‚7ۃۍуԃHh܊ܢܻܶ/9e΃ޔ‚8ۮ0 ‚9(Mxj\wފ:S 0123456789:;<=>?@ABCDg^_`abcd€€€€€sF c802.21WWWWWWWWWWWWWWWWWWWW}cincompleteWWhWinconsistenciesWinconsistency%W&WWinconsistencybetweenfigure12and5.6.1%Vinconsistencybetweenfigure12and5.6.2.1mihlinksapis&Vsistencybetweenfigure12and5.6.2.1mihlinksapis&V&Vp_‚S?@Aǃ:;ܵՃփLM}@A:‚TKȃɃʃ˃ܶ׃؃كNOPQݓ‚UZ[ےۓ̃̓΃ <=>?@Aܷڃۃ܃RSݔt;‚VۑσЃ!"B݃ރTUݕ‚W߃V|ݖ‚XX\у҃#$CDEܸܹܻܺW݉‚YYFX~ݗ‚Z]^%&Gܗܼ‚a'H‚bӃ(Yݘ‚cu‚dԃZ‚e_`)Iܾܽ1‚fa*‚gbՃփJKLܿ[ݙ<‚i׃M\\\\\\\\\\\\\\\\\\\\\\\\mcto8W:W>W?W@Wtobeconsistentwithnotionthatoneinstanceofmihbein/VtodiscoverwhattypeofeventsaresupportedbythelinklaRVRVRVRVRVRVRVW8W8W8W8W8W8W8W8W8W8W8W8W8W8Wbelsewhere۝W)WUWYWem2WembeddedWtWݸWWemergency1WemoteޔWemptyۂWencapsulate WencapsulatedWޏWencodeTWUWVWWWXWcWencodedݘWހWencodesܕWܕWܕWcodesܕWܕWWހWހWހWހWހWހWހWހWހWހWހWހWbbhandovermodeۂۋWgWhandovers,W?WAWQWUWuW:WܴWݍWWܴWܴWWuW:WܴWܴWhandovers,W?WAWQWUWuW:WܴWܴW:W:W:W:W{\b8.6.1.18W804W802sWWW802.11?W_WsWW=WYW[WWW W1W3WpW802.11a/b/g^W802.16_WsWNWYWW|W W1W4W5W^W802.21W802.21W#W'WDWXWWWW$WCWܧWܸWܹW݂WSW^WW^W^WSW^W^WSW^W^WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW>cmessages5WۃWWWWWWWW"WOWiWmessagetooWmethodۈW(W\Wmethodlength1octetisnotsufficientalready7methodsar(Vmethodology>Wmethods(WV cmih8W:W<W=W>W?W@WAWBWCWmihcapabilitydiscoverprocedureneedstobedistinguishedVmihcapabilitydiscoverresponsemessageݥVmihcapabilitydiscoveryisspecifiedasmaybedonethroughOVOVW8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8WcsdomW W>Wsdos"W#W$WsduW܌WseamlessW1WseamlesshandovercanhappenbetweenhomogeneousinterferfacVsecondWW݆WW* baddedWWWWWWbbeenRWRWSWVWXWWWbeforeFWGWHWIWJWSWYWۉWۜWWWWW#W\WܺWW"W2WLWW2W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+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~WbitFWGWHWIWJW2vcin:W;W<W=W>W?W@Win802.21alinkgoingdownmihlinkgoingdowntriggerisuۅVۅVۅV6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W[ band:WandciviclocationinformationݖVandcoordinatethepayloadthatisembeddedVandlinkhandoverimminentVVW7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WDf[{cThe 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 2006/07/20|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 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 enumerator   33 33!  33& 33fcA"Syntax error in "3: 127: Reserved""@e8[b*Replace MacMobileNode with LinkIdentifier.c5MacMobileNode should be replaced with LinkIdentifier.d856g2380vby comment 527/626w Superceded 2006/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Binding_137`46a8.5.3.20b*Replace MacMobileNode with LinkIdentifier.c5MacMobileNode should be replaced with LinkIdentifier.d857g2381vby comment 527/626w Superceded 2006/07/20 2006/04/28E YoshihiroFOhbaGMember^Technical, Non-binding_140`1a Annex A-1cA- 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? d873g239904/24b17ۮWmW18W=W195W=W@W=WܵW~W:W1999pW1x-ev=W2W!WJWNWjWkWmWnWuW{W}WۉWەWWW&W(W=WHWRWSWYW\W|WܒWܖWܯWܴWWyWzW݃WݗWݶWW W,W>WPW^WpWvW}WށWރWޕW1W6W:W;W2accessnetworkspecificinformation;V2onesparqlqueryparametersށV2onesparqlqueryresponseparametersރVރV6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W hܖbAR 33   33 Rledge 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  33iYoshihiro OhbajkAJust 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.mRejectednpvwxpvwxMcspecific'W-W_WaWWW W$W:WCWaWiWܘWܰWܺWܾWWWWW~WWWWWW1W6W>WOWWW>Wspecificformatforthevalueportionineachtypeofinform~Vspecifically WspecificationW۩W۾WWW WWܟWWWW݉WWnWކWspecificationoftypeienetworkqosisnotmediaindependenVspecifictaion+WspecifiedWېWW܌WܾWWWWWEWWWOWޖW5WW5W5WޖW5W5WW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wyba8W9WacombinationofoperatornamespaceandݕVadefineatransactionidthatisuniquesVadouble-headedarrowlabeledsocketapisshouldconnectthe0V9W9W9W9W9W9W9W9W 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}~bingqiangۍېbingyunۊۏdas  !"#$%&'()*+david,-/0ܮeleanorȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ eric݂݃eunahyzBcthemihfunctionheaderconsistsofatwopartsonewithfix'Vthemihfunctioninthenetworkmayadvertiseitsmihcapabi+V--------------------------------------------------------------------------------------------------------------------------------- | 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. | | cifthetypeienetworktypeisapprovedthenomustbeupdat@,implementation@implementations@improperimproperrerencetointernetdraft@s@improperimproperrerencetointernetdraft@s@improperimproperrerencetointernetdraft@cshows:WyW+W>W8WsidWsideCWW0WsignalWdWsignaling/W0W1W2W3W4W5W6W7W8W9WjWsignificantWW WWsimilar(W*W\W]WWEWFWGWHW9W@Wsimilartopage58lines1-21lackofcontextunnecessarypa]Vsimilartowhatisstatedin6.3.6.1exampleslackcontextr\VsimilarlyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW^ FbarearedescribedinthesectionbelowVarenotraejV-W-W-W-W bremovingۼWWWrenameۭWWW:WKWwWrenamethefigurecaptiontoremotecommandserviceflowKVrenamethemessagefromtheremotemihftolocalmihfaseveV3uclinkprimitivecanonlybegeneratedbymihfunctionnotfrocVdVlinkqualityparametertypeencodingisinsufficientandneeJVlinkstatusparametershouldbedescribedhereinmoredetaiݽVlinktransmissioneventsitisnotclearwhyweneedthisfoVlinktypenetworkidentifierparameterisrequiredformihuaVbVcVlinkupmacaddressnotdefinedin3gpp2usesectorid128biVlinkuprequestandlinkupresponsearenotdefinedintheކVlink-layer6Wlink/mediaܰWlinkedWlinkidentiferݜWݝWݞWݟWݠWݡWݢWݣWݤWݦWݧWWWWWWWlinkidentifierݜWݦWݼWWWlinkparametertype`Wlinkparamterlist_WlinkskWJWWWlinktype W"Wlinktypeoperatorisnotneededunderapoamultipleoperato"V"V"V"V"V"V"V"V  bthemWWWLMcclassificationWܰW;WclassifiedW;Wclauses(W*Wclear!W-WۆWۈW۾WW WW$W.WsWܳWܷWܸWܹWܾWܿWWWWWWWWWW W W W WWWW!WWWW5W@WclearerWW5W5W5W5W5W5W5W5WJbdetectedSWWRWSWTWUWVWWWXWݛW+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 cshould2W3W:W;WAWBWCWshouldhaveanotherblockcalledl3transport0VshouldisarequirementnotappropriatehereVshoulduseadjectivenotnounformsincethereisnosuchtheVshouldn'tWW B\cwhileW۬WwhirepWwhoWwholeWWWwhoseۊWwhownWpWwhoWwholeWWWwhoseۊWwhownWWdbinternalWWinternallyWinternetAW1WinteroperabilityWinterpretlWinterpretationWinterval\W]WޖW5Wintitate|WintoWW!W*WZW_W`WbWqWWW=WWWWyWzWSWintonetworkaddressinformationjustanaddressVintraWWWWWWWWWWWWWWWWWWWWWWWWWHbpayloaduWWtWݸWWWpduWRWpeerpWuWxWݎW!W%W<W?Wpeer-to-peer݊Wpeer1<W?Wpeer2<W?WpeersxWpendingVW WpereWhWvWܾWpercentage\WW\W\W\WܾWܾWI`29a7.3.3.1bnTo 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 2006/07/20 2006/04/28JEAjayFRajkumarGMember^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. d585g2243vZby comments 482, 508, 514,515, 267 which take care of confirm/request/response primitives.w Superceded 2006/07/20 2006/04/28KEAjayFRajkumarGMember^Technical, Binding_84`30a7.4.2b5Add Call Flows as described in DCN 21-06-0622-00-0000cGMember^Technical, Bindinghcshow@shows@zsimple@small@xsolution@Qsomething@Ispaces@specific@tspecifies@standards@statement@subjective@usuch@,suggest@0suggestednewpoaidentisnotneededifitispartofsuggeste@qsupported@Yswitch@syntaxerrorinnumberofparametersinlinkparamterlist_Nsyntaxerrorinresourceretentionstatus20@syntaxerrorinresultoftryingtoconiferthelink@Dsyntaxerrorinwhenapredictiveevenexpectedtooccur@4systems@.take@?target@Stechnology@echnology@Stechnology@oWpcis:W<W>W?Wismulti-hopscenarioshouldbedescribedݓVisnasacryonymcorrectV5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wbj7EVivekFGuptaGMember^Technical, Binding_112108`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.d673g3257 2006/07/19EVivekFGuptaGMember^Technical, Binding_112r, 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>d603g3253 2006/07/19EVivekFGuptaGMember^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.d673g3257 2006/07/19EVivekFGuptaGMember^Technical, Binding_112t time? X@be used.d446g3238 2006/05/14 Xbsection8W:Wsection5.6.2.1mihlinksapshouldberemovedentirely6V6V6V6VW8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W#binclusionWWinconsistency%W&WincreasedWincrementalWW[Windependencemih(Windependent?WAWpWuWvWWWWW}W:Windexing۶Windicaiton5WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWing۶WindicateWRWwWWݗWWOWindicatesFWTWUWVWWWXWYWcW|WݗWindicationUWVWWWW9WOWRWUW\WyWݍW>WsWxWޕWWWWsWtWuW߱W߲W߳WWWWindicationsTWUWVWWWXWWrW߰WWindividualۂWܽWSWindividually۳WinfluenceWinfoWOWܗWܘWܙWzWWBWxWinfomrationW%WinfoqueryparameterskWnWܕW}Winfoqueryresponse|WވWbthinkWWthirdWBWthis W#W,WAWHWIWLWMWOWPWQWRWSWTWUWVWWWcWdWiWkWnWxWۂWېWەW۶WWWWWWWWWWW WWWWWW%W&W@WNWVWXWYWZW\WkWoW܄W܅W܆WܓWܕWܡWܣWܩWܴWܼWWWWWWWWWWW0WIW}WݍWݘWWWWWWWWWW W WWWWWWW!W"W#W$W%W1W2W3W4W5W7W8WVW}WWހWނWބWޅWއWމWދWތWޕWޖWޗW3W5WnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnWnW\|bstringkWnWHWmWܕW}WހWނWstringsbWstructure#WZW]W_WbWsWܬWWWsttausWsubjectWWsublayer1Wsublayers݃WsubmissionSWsubmitQWsubmittedۊWۋWsubnet?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އWWca8W9W:W<W>W?WDWaaddanstotowardonline20Vabettertitlefor5.5wouldbemihreferencemodelforacce$V$V9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W_bscopingWWsdo 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\WlWnWvW3W4W5WvWvWvWvWvWvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW\bshouldVWWWZW]W۫W۷W۸WWWWWWWWW#W%W&W(W*WܨWܷWWWWWWDWUWYWkWoW݀W݂WݺWWWWWWWWWWWW,W-W.W0W6W9W=W>WAWBWDWJWPWTWޗWshouldbeaddedtotable5anddefinedVshouldbeincludedintable3sincetheyfallundermihevenVshouldbekeyandsalientpointsܨVundermihevenVshouldbekeyandsalientpointsܨVܨVsܨVܨVenVVbn-layer/W5WܟWn-layerthen-thlayerofthelayeredprotocolstack/Vn-th/Wn-user5WܟWn/aFWGWjWmWۂWkWmWܖW4Wn0WnameۂWۉWېW=W\WkWmW܁W܂W܄WzW|WݕWW<W?W~WޕW0W4W6Wnametype܄Vnametypevalidrangedescription0V4VnametypevalidrangedescriptionۂVnamesܷWnamespaceݕWnasWnasiscommonlycalledasnetworkaccessserverVnas-port-type=WݔWtWnativeVWWWnature Wnbr-advNWnearbyWnecessaryAWVWۓWW2WW݂WW<W<WWWWWWWWWWWWWWWWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWtWbitappearsthatreferenceistothedefinitionofoperator-nUVYVitmaybeinterestingforanupperlayertoregisteronapeeVitseemsthatreportavailabilityshouldoccurafterresponsVitshouldnotbethecaseinsteaditshouldbethatthenumbVitwouldbemoreeconomicalforthenetworktobroadcastthe9Vit'sWitem۪WW܍W#W%W0WitemsەWitmeWitswWWWܡWܤW(W,W0WW W!W+W>W7WcbelowGWWCWWWWqWbeneficialcWbenefitWWbetter$WYWۚWۨWۮWWWWW=W݄WW4W5W7WdW?Wbetterwording=Vbetween"W%W&W'WDWKW۴WWW W$W-W1W:WHWRWܜWܟWܳWWWWWWWWW2WJWSWiW݉WW WW4W5W7W>WTW2W>W?W@WAWBWCWDWbetwenW2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2W2Wbor9W?W?W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9Wa2baddmoredetailtothecostiedefinitionVaddmoreinformationonscopingofthestandardVaddnewsectionsprobablyaftercurrentsection8thatdetaVaddnewsubsectionsandtextinbothsection5andsection'Vaddqueryresourcelistattheendoftheparameterlist܎Voftheparameterlist܎V܎Vaddqueryresourcelistattheendoftheparameterlist܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V܎V?ubactualwWWacuallyWad݊WadaptationWWWaddWWW'WCWDW\WbWۇWۉW۶WWWWWWWWWDWEWRWSWTWUWVWWWXWYW\W`WbWcWdWhWkWmW܎WܐWܗWܘWܙWܚWܜWܴWܺWܻWWWWWWWWWWWWWWWWWW'W)WHWbW|W}W݊W݋W݌WݛWݥWWWWWW2WDWKWLWMWWW[WaWbWcWhWޒWޒWޒWޒWޒWޒWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbhandingPWTWhandleWhandledWhandoff)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.WAWXWYW6WYWYWYWYWYWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWqbnecessary.W.W.W.W.W.WrZbdeploymentW}WderegisterۉWWWFWHWrWzWderegistrationWXWderivedHWdesciptorSWdescribe'WWWWWdescribed'WsWۃWۄWnWݓWWWWKWLWMWTWdescribedintable33aVdescribesvWdescribingW5WܟWdescribingroamingaspectsonin5.3.2beforethetermsareVdescription?WpWtWۂWېW=WNWRWSWTWUWVWWWXWYW\WcWkWmW܄W܅WܲWܶWܷWWWWW|WހWނWޔW0W1W4W6WdescriptionsWdescriptiveWdescriptonܹWdescriptorWSWdesctiptionހ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ނWh Xmember23456789:;<=>?@ABCDDD9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999>,`‚Eۋەۙ۵i܍փ%1‚FɃaܫܭM‚G%.4Pу߃12;]^ށ‚H`҃7`‚ILgےۓۣۨۼ57=Gܟڃ.ݐݔ~‚JHMUۂ Z܎ƃ΃ݓ݃/3‚QB۹ܱy݀.‚R|ۅ۫݃Bȃ#‚SQXm(/Cܦ r3‚TKNjۯp T‚U0ۉ,уO8L888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888u-ibaccessingۖW۶W۸WWHWWaccmpaniedUWYWaccordanceފWaccordingۉWۊWۋWYW܏WyWzWaccordinglyWWaccoridingly_WaccountedOWaccurateܰWXWachievexWW"W#W$Wack-rspyWacknowledge܌Wacknowledged܌WacquisitionݍWacronym@W@Wacronym@W@WBcentriesܹWWentriesintable-7arenotclearandneedfurtherdescriptioܹVentry܉WWWEWFWGWHWRWentry2linkeventderegisterhasbeendefinedasaneventeHVentry2linkeventregisterhasbeendefinedasaneventeveGVentry2miheventregisterhasbeendefinedasaneventevenEVentry23miheventregisterandmiheventderegisterincorreRVentry3miheventderegisterhasbeendefinedasaneventevFVenumerateۄW,cit:W;W>W@Witdoesn'tmakesensetomanditorilysupportxmlandtlvVitisdifficulttoenvisageascenariowheresipissupporteVitisentirelyunclearhowprotocolextensibilityishandledVitisimportanttoclarifywhichentitieswillgeneratetheZVZVmcreceives_WaWۈWۉW0W>WreceivingۅWW Wreception܌W"W$WrecipientfWlWrecipient'sxWrecommendatin݂WrecommendationsWrecoommend݂WredWredundancyۙWjWredundantgW WrefeernceܯWrefereW܏WܧWWWWWreferto802.21asieee802.21consistentlyinthedraftܧVreferenceW!W$W۬W۽WWWWWDWEWܪWܯWWWWW:WAWFW\W݂W݃WݕWݖWݘWWXWYWpWqWreference1isnotcorrectalsoreferencenumbersaremissinVreferencenumberismissingforallthereferencesintheliVreferencenumberisneededforeachreferencepVpV @blistlistatableoflinktypessupportedby802.21^V0W0W0W0W0W0W0W0W0W0W2 5bremove?Wremove2bitsfromthe14bitidaddexplanatorymaterialtoVremove2sparqlqueryparametersand4zerooroneextended{Vremove2sparqlqueryresponse3urlresponseand4zeroor}Vremove5.8.3+Vremove6.3.4.1.2^Vremove7.4.8gVremovealittlevV<bfront2WfullbWfully'W*WDWhWaboutfront2WfullbWfully'W*WDWhWhWt2WfullbWfully'W*WDWhWhWWWWWWWWWWWWWWWWWWWWWWP cpleaseWWޔWpleaserefertothe21-06-0601-00-0000poaipaddressconfiguVpleaserefertothe21-06-0602-00-0000poacapabilityprefixVpluralWcWdWpluralformVcVdVpoa_WaWۇWۈWۊWW WW W"W#WܩWܺWܾWWWWWW+WZWWWWWWW"W#W$W%W*WQWdWfW8WpoadatarateVpoa-address~Wpoas_WaWpointۊW-WܝW݂WWIW2WpointerWpoints۬W:WܨWܪWܯWWpolicyܡWWݎWpolicyengineisnottheonlyupperlayersݎVpolicyenginetypeentityshouldbechangedtopolicyengineVpoorlyZWportWCcroomSWround Wroundabout/WrouteWrouterW:W+W"W$W%WޏWrouters:WrowWrrcCWrregisterrWWݲrttWWW Wrules W W WWrunWrxlevncellFWGWHWIWJWskWWWWWWWsafeWsaidxWsalientܨWsamݛWsame+WېWWWWW W.W/W:WIWZW܄W܅WܠWܩWܼWWWWJW[W~WWWWWWBWKWjW6WW6W6WjW6W6WWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWjWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIWIW2cfunctionsuWYWW@Wfunctions/primitivesܰWfurtherܹWܼW@W"W$WQWfurthermore@WcWfutureWWcWfutureWWcmihhandoverinitiatemihhandoverpreparemihhandovercomm/V0V5Vmihhandoverinitiate/prepare/comܴVmihhandoverprepareisimproperfor802.21scopethefuncti2V7VmihhandoverpreparerequestandresponsemessagesinremoteiVmihlinkparametersreportindicationcanbegeneratedwhen5Vmihlinksapismissingin7.1.2CVmihmediaindependenthandoverܠVmihnetworkaddressinformationrequestandresponseprimitijV5V5V5V5V5V5V5V5V5V5V5V" -cA- 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? d872g2399vcNot all issues have remedies. Assigned on Issue List. Change: - "PSDN/FA" should read "PDSN/FA". wAccepted-Modified 2006/07/20 Figure 30operator. 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. ccimproperWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW clayer@Wlayered/W/W/W/WW5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5W5Wgmathieumatsumoto݀݁member2W3W4W5W6W7W8W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WW܀W܁W܂W܃W܄W܅W܆W܇W܈W܉W܊W܋W܌W܍W܎W܏WܐWchere+W:W;W<W=W>W?W@WiWsWvWۂWW+W`WWW WݽWWWW*W>WherewegiveaproposalforaddingaparameterinthemihhaۂVheterogeneous"W1WIWܤWݐWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWccommonqWW2WcommunicateܴWW!W%Wcommunicated2WcommunicatesWcommunicatingTWcommunicationەW3W W*W3W>WcommunicationshWcomplete/W0W4W5W9WۇW-W܉W܏W WWWDWޗW4WBWCWcompletedۂWcompletelyYWܰWcompleteness)Wcompletenessconcisenessgrammar)Vcompletion*WcomplexityBWcomplianceWܛWW%WcomplicatesWcomponentsWcomposed:WܤWݐWcomposedofmultiplemediatypesitisthehandoverdecisionݐVcomprehendedWcompressedۿWcomputationalBWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWgbhandover:WhandovermoduleshouldbereplacedwithnetworkselectorAVhandover/switchingWWhandoverackۋWۋW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W Xcsamesameascommentonfigure18theinformationflowshouldBVsampleܯWctreejWkWmWnWoWzW{W|W}W~WہWtreesjWkWmWnWoWzW{W|W}W~WہW~WہWہW~WہWہW> $cnot:W>W?WnotclearwhatgranularitymihswitchoccursonwheninvokedVnotclearwhetherthisisanmihprotocolormihfprotocolVnotclearwhylinktypeisincludedinthelinkdetectedpriVnotclearwhymiesiscalledoutspeciallyinthiscase V V7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7W7WburljWkWmWnWzW{W}WW|W}W~WހWށWނWރWމWurlsWuseUWfWuWۘWۜW۞W۰W۳W۸W۽WWWRWSWTWUWVWWWXWcWsWܯWܿWW W W"W3WZW݂WݎWWW WVWiWjWuseaasinothersimilarcasesintable۰Vuseatvariousinsteadofother"VuseinbeforemobilenodealsosuggestusingawordconsisteۜVusemninplaceofmobilenode۞Vnode۞V۞Ve۞V۞Venode۞V۞Vcinformation9W<W?Winformationintable11isnotdetailedenoughtosupportimVinformationserviceclassificationisnotconsistentwiththVW9W9W9W9W9W9WMcwindow W WwindowingWwiredWWPWwishWwithBWjWkWmWnWoWuWzW{W|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ޗW0W6W7W8WAWBWCWLWWCWCW8W8W8W8WceachuWۄWW@WCWzW{WܸW:W~WWWWWpW1Weachmobilenodeshouldbeawarethatthepeerentityhasth1VearlierpWvWxWeWearlyܫWyܫWܫWyܫWܫW1VearlierpWvWxWeWearlyܫWܫWlyܫWܫWX8bmihfpWuWxWWۇW۵WWoWܚWܥWܯWWWW WW_WyWzWݴWݸWWWWW!W"W$WXWއWޕWAWBWCWmihf/802.21YWmihoܠWmiisAW_WlWuW۳WW}WW:WmiisprovidestheabilitytoaccessthisinformationaboutaVmilliseconds\W]WmimeހWނWminimal=WminimizeVWminimized۸WWminimumWW\W&WWminuteHWmipJWmissingܺWWmlme3Wlme3W3W3W3W3W3W3W3W3W3WKbtheyWW-WAWW7WW݂W݃WWWWW-WAWW7WW݂W݃WWWWWW-WAWW7WW݂W݃WWWW_W_W_W_W_W_W_W_W_W_W_W_W_W_W_W_WbintentWW܅W6WVWintentionallyWinter?WܤWWinter-media*WinteractpW"W$WinteractionW݃WinterestIWinterestingeWinterface*WiW۾WWeWWW0WDWWW1W2W3W4W5W7W8WޖW5Winterfaces"W*W.W,W!W1W2WintermediateUW-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-W-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ݎWportsWportedAWportion1W3WposW,WW2W9W\W WpositionTWUWVWWWXWcWpossibilitiesWpossibility۳WpossiblewW۸WWYW=WoW7W7WpossiblyܡWW)W݂WpotentialOWPWsWpotentiallyWWWWWWWWWWWWWWWWWWWWWWWWWWWWhepworthȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ hiranohuoܮikedaTUVjiangۍېkeating89khatibi !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxx ܤbA 33:  33F 33  33 33  33! 33 Qbthey9Wtheymatchanagreedschemathisdoesn'tmeanyouhavetoV9WEqcor-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ޖW6WW6W6WޖWޖWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbWbW}brepositoryWܶWZWrepresent݃WrepresentationAW=WWWWWWW|WݔWݕWWWWWWWW ybadd8W;WBWCWadd3gpp2after3gppHVadd3gpp2hrpdcs0024-aandcs0063-ainreferences'V'VckeyیWܨWWWWkeysalientpointsmissingandܨVkindsۉWknowۅWۉWېW6WcWmW܄WOWknowledgejWkWmWnWoWzW{W|W}W~WہWknown܋Wl݆WWl-shaped,Wl2W܌WܩWܭWܲWWW3W@Wl3rWWܩWܴWW+W3WDWWW0WlabelqWlabeledqWlacDWlackWWWW[W\W]WfWlanguagejWkWmWnWoWzW{W|W}W~WہWܬWlargeWWWlargelyxWlastqWsWܕWWWWWWޗWlatenciesWlatter.WWWWWWWcimplementationsCWHWimplemented_WbWimplementormWimplication۷WPWimplicitWimplicitly WWimpliedWWW_WuWimpliedlimitationofcapabilityassumedsuboptimalsolutionVimpliedlimitationofcapabilityinassumingthatmiiscanoV_VuVimpliesuWwWWۓW۸WW*W+W,WimplyiW WOWW*W+WimplyingWimportant'WNWWZWsWܩW W'Wimpossible%Wimproper/W0W1W2W3W4W5W6W7W8W9W:W;W<W=W>WiW=WMWOWQWUWYWYWYWYWYWYWYWYWYW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!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 cthis9W=W>W?W@Wthis802.21standardܣVthiscommandissentbycurrentmihfentitytotargetmihfeVthisinformationtypicallyoriginatesatdifferentlayersofV9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9Wbdatabase۳W۶WWWWdatatype~WdayHWdbYWdcd|WdcnKWLWMWdealingۈWWdecision W#W?WvWwWWfWܤWܴW.WdeemedWW.W.WܴW.W.WWWWWWWWWWWWWWWWWWWWWW3bin:WDWinanetworkmodel,VincaseoflocalcommandsmessagestypicallypropagatefromݎVincaseofmobileipv4agentrouteradvertisementޏVingeneralhandoversmaybeinitiatedeitherbythemobilen,VW6W6W6W6W6W6W6W6W6W6WqJblinktypetypeofthelinkbVcVlist-W.WAWPWZW]W_WuWۂWېW=W@WJWKWLWSWTWUWVWWWXWbWcWdWhWkWmWyWzW{W~W܎WܷWWWݙWWW@W[W^WtWWދWތWޕW0WtWWދWތWޕW0W0WWWWWWWWcblistlisted@local@low@macnewaccessrouter@Xmakethefollowingchangeto@makes@umanner@matrix@may:mbit/s@means@(media-dependent@merged@ method/mode@%middle@kmihlZ8Bmihlinkdetectedeventanewlinkisdetected@*mihreferencemodelforaccessnetworkstechnologies@Xmihf@mn@mobility@module@most@must@n-layer@necessaryneed@qnet@network8Fnetwork-assisted@network-side@nm@etwork-assisted@network-side@nm@next@@network-side@next@xt@ssisted@next@ssisted@Rcby8Wbyr1r2orr3overanyaccessnetworkandtwomihnetworkeVV8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W&1breferDWEWWreference$W۬W۴WWW`WܪWܯWWWWUWYW݂W݃WlWreferencecouldbemadetostaticschemaeintheisqueryVVVVVVVVcfunctionality/W0W1W2W3W4W5W6W7W8W9WgW:WW7WjWfunctionality/capabiܛWity/capabiܛWܛWnality/capabiܛWܛWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWHcuppers݇WWWWurl{W}WqWމWurlofsparqlinthereferenceisoldandshouldassuggesteqVScboth-W:W;W<W=W>W_WۈWWܠWܩWWWbothhavethesameexpansionܠVbothstaticanddynamicdatacomponentscanreadilybeVbound:WboundaryWboxWboxes-WWbracketsWWfWbraodcastfWbreakۮWbreakdownsentenceforbetterreadabilityaftercommaۮVbreakoutWbriefmWbroadcastۈWWܺWWOWPWQWbroadcast/multicastܻWbroadcasting+Wbroadcasts+Wbroaden۸Wbroadenthestatementtouseofnetworkresourcescurrentfo۸V۸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 &bthis9W@WthiscommandissentbycurrenttheservingmihfentitytotVthiscouldbeduetouserormobilenodemobilitystatechanIVthisfieldisintentionallykeptreservedwhennotusedallVthisfigureshouldbeeithermodifiedorremovedbecauseitޗV9W9W9W9W9W9W9W9W9W9W9W9W9W9WXgblowېW6WlowerAWpW۵W6WiWkWܫW1WyWݎW,W1W2W3W4W5Wlower-layer*WlsۓWlsap1WDWlte Wm4W2Wmac,WNW WpW4Wmac/phy WmachineWmacmobilenodeWW4Wmacmobilenodemacaddressn/amacaddressofmobilenode4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4V4VmbbeginningۧWWܚW(W*WbehalfMWcWiWއWbehavioriWkWW8Wbehaviors@WbehaviourWWbeingOWbelongWbelongs\WbelowGWHW\WjWWWWbesetۉWbest݂Wbetter۾WWWWWW-W[WWbetterunderstandandclarifytheamountofworkneededtoi۾Vbetween W"W'W?WDWZW]WpWqWuWxWۣW5WgW܅WܟWWW WW,W1W2W3W4W5W7W8WpW2Wbi6WbinaryܕWbindWbinding~WbitFWGWHWIWJWXWyWۉW)WTWUWVWWWXWcW|W|WWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJWJW/boncelW WoneWW?WjWmWpW{W}WۦWWFWVWXWzW{W܁WwW݃WݎWWW W'WIWWށWރWބWޅWމWދWތWoneofthestacksVonepersistenturlofthisschemashildbeassignedމVWWWWWWWWWW#bas@c9asinthecomment@8associated@attributes@_basis@%be9because@been@mbeginning@bitܹbler@brackets@byޖbyte@call@carried@certain@ change@%:}changeendofsentencetotoeffectseamlesshandoveracross@5changeifapplicablethenewsapsshallberecommendedasam@Tchangeotherieeegroupstosomeieeestandards@changepointofattachmentstopointsofattachmentorpoa's@?changeradiotointerface@mchangetextto@changethetextto@changethevaluefieldfrom@changevalidrangefromn/ato@changed@clarification@clarifyhow/inwhatwaysecurityinformationismadeavailab@Xecurityinformationismadeavailab@X{lLbareaWWWpWaren'tWarrayۉWarrivesWWpWaren'tWW(obdirect,W WdirectionyWzWޔWdirectlyAWWW"W$Wdisconnect6W6W6W6W6W6W6W6W care:W;W=W>Warecommandserviceandnoteventservice(Varelinksynchronouseventsapplicableforl2handoversonlyܲVaremorefailurecodesneededtoindicatewhyaparticularsV blink<W@WlinkcapabilitydiscoverrequestېVlinkcommandindicationrequestsVlinkcommandsoriginateVlinkdetectedeventanewlinkisdetectedݛVݛVW6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6W6WGbtable-6ܷWܼWtable-7ܹWtablesWtailPWtakeOWPWQWTWUWVWtakenHWhWtargetۇWW݊WW!W"W$W%Wtaylored۳WtcpOWtcp/ipWtearWred۳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+W۾W+WW݂WݏWWW>WnWservingۇWW:W!W"W#W*WsessionsWWWWݒWݵWWWUWhWsessioniddoesnotmakesenseUVsessionidentifierismissingVsessionidentifierneedstobedescribedݒVsessionisnotdefinedanywherethussessioniddoesnotmakVsessionsWsetWFWGWHWIWۄW=WTWUWVWWWXWeWiWkW|WܻWWWEWFWGWHW3W3W3WWܻWWWEWFWGWHWHWWiWkW|WܻWWWEWFWGWHWHWHWHWHWHW:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:W:WboptionsܩWܯW,WorWWW 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ޗW5W5W5W5WWWWWWWWWWWWWWWWWWWWWWWWWvZexEQiaobingFXieGMember^ Editorial_113`23a8.3.2bAChange 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  )czhieve 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  )czUtbtheymusteitherbemergedintooneoroneofthemberemove@think@this9thismessageisusedbymihfunctiontoretrievetheinforma@thisparameterspecifiesthelistofcommandsthatmaybeca@thisprimitiveisgeneratedbymihfunctionwhenitneedsto@thisprimitiveisusedbymihfunctiontoqueryanddiscover@ethisprimitiveisusedbymihfunctiontoqueryanddiscover@e/#bcanother@byte@destination@differences@6easily@Uenough@for@ifthetypeienetworktypeisapprovedthenomustbeupdat@yimprovement@just@linkparametertypedefinitionsisinsufficientandneedsto@mihhandoverinitiatemihhandoverpreparemihhandovercomm@Wnot@overload@repeat@show@text@thedocumentspecifiesthatanupperlayermayconfigurethe@thelengthdoesnotmatchthetlvrepresentationofsection@vthetransactionidisalreadydefinedinthefixedheaderpa@.tionidisalreadydefinedinthefixedheaderpa@.at@show@text@'cinstantiationsWW6WinsteadWW W*WܥWZW݆WXWYWinsteadofprefixthepoasubnetinformationtlvshouldcontZVinsufficientFWGWHWIWJW\WyWinsureTWUWVWWWXWintelligence:WintentWWintentoffigure24unclearVintentofmiddlesentenceisunclearandpossiblymisleadingVintentioniWintentionallyWinterܤWinter-bsWinter-essWinter-media*Winter-operabilityWinter-poaiWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW``‚'YwڃR^~ԃމ‚(۱߃&1mzݢHތޗ‚)8۪ۤLܔƒ*؃8N‚*ۑۭ۟!dݕݶ!-A‚1?۷#*<ܙTqڃރޒ:‚2c}۸.V܈ܥ=wݳcޅ7‚3RS܃ܝ>t‚4iqxۥ3ܺDJއ9‚53CV:lwՃNݘݾ‚6W1388W147WWݛWWWlWޗW;W14-15W15WWݛWWlWޗW1500W16EWWW|WW17یWW18یWWWWyWWBW19ܵW:W1stvW1xev-doFW2W!WSWiWsWuW۴W۽WW&W=WAWBWCWݗWWW>WEWGWHWޕW:W>W2pagenumbers0-6oftocshouldnotrepeatthemaintextV2.2!W2.3_WaW!W2.4!W2.5۪W۪W۪W۪W۪WW!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!W!WS+?^technical<W>W?W@WAWBWCWDWLWDWDWDWDWDWDWJWGW9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9W9WbflowܴWWKWyWzWWBWQW8Wflows)WWKWflushUWfocusXWYWfollowedWݙWfollowing*W_WjWkWmWnWuWvWwWxWەWW3W=WHWRWSWTWUWVWWWXW\WcWdWmWܚWܬWܹW|W݊WWW W2W7WIWފWޔW3W7Wfollows WJWXWۂWېWWCWYW\WܤW)W0WlWlW"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W"W#QBcsentWܕWW%WޖWsentencesWۚWۥWۮWWW WW3W5WQWiWW6W9W@WMWWW^WxW݆WݐWWWWWWWWWWފWދWތWsentencesayingaspecificinformationrequest/responseprimVbmatrixWmaximumWWWmay 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/WOWTWWWWދWތW3WތW3W3WW3W3WތWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKWKW bmay:WmaybeVmaynotliketVmayshouldbechangedtoshouldorthereasonwhytheuniqueTVmaycauseۉWۉWLWW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W1calternativeSWۈWWalternatives۳WalthoughqW~W݃Walthoughvalidthisdiagramlookstoobusythisisexactlyt݃ValtituderesolutionWalways۾WWܰWWWއWambiguityWWWambiguityofwhetheraphrasepertainstothewholesentenceWVambiguitysuccinctnessallowthecasethatmihisnotsupporVamendۆWamendedܸWamendmens>WamendmentۅWamendmentsWamendsۊWamendsmihcapabilitydiscoverymessagebyaddingnetworkidۊVammendmentsWscoverymessagebyaddingnetworkidۊVammendmentsWWtworkidۊVammendmentsWWWWj ;,cd252g2254 2006/07/20 2006/04/24 33D  33fand 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  33d229g2249 2006/05/14 2006/04/24( 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  33d229g2249 2006/05/14 2006/04/24(@cinformation:W;W<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-WBWZWdWgWjW1W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*W*WMcof8W:W;W<W>W@WAWBWCWoffered:W:W:W:WW8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8W8Wcbyte@capabilities@(change@changed@classification@clearly@Lclient@comma@comments@common@concatenation@configure@confusion@consistency@contents@context@could@!coverage@critically@=customarily@@d01@define@Ndefines@-definitions@Ldefintion@delivered@dependency@Edescriptions@edataunderinforquerytypeisnotcorrcet@descriptions@eions@eotcorrcet@}descriptions@eisnotcorrcet@}descriptions@e\d‚1ۜ‚2‚3‚4‚5"‚6۝‚7۞‚8#‚9$‚:݅‚A۟‚Bܛ‚C%‚D‚E‚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߳ 3memberƒÃăŃƃǃȃɃʃ`‚AZo8_eܓܛʃӃ݉ݎݷ̓KLe‚BNXܣ(-kʃ܃‚C/k׃4ݬ‚D@{܅AIdx"|ގ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ߌ)busers-WpW۵W7W܊W*W0WW7W9Wuses۝WTWUWVWWWXWcWusing_WuWxWۗWۜWWWHWTWUWVWWWXWcWWWutilised}Wutilize"WWWutmostgW&Wv-aaa:Wvalid\WۂWېWTWUWVWWWXWYW\WcWkWmWܖWW|WW0W4W6WvalidrangeۂWvalueJWXW_WfWjWmWzW{W}WۉWWWW*W=WFWHWwW|W܂WWXW[W~W݁WݔWݗWݘWݙWWWހWނWޅW1W3WLW3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3W3Wcif9W>W?Wifcomment9isacceptedtomodifythedefinitionsofhorizo;Vifthehandoveroperationissuccessfulthemihfinserving*VWmncregisters-WeWregistration.WuWVWXWWWWWkWregularޖWegularޖWޖWgularޖWޖWkWregularޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖWޖW.) pbAChange the text to: The MIH Function provides asynchronous and synchronous services through well defined SAPs for lower layers and upper layers. The services provided include the Event Service (ES), Command Service (CS), and Information Service (IS). Detailed description about MIH services are found in section 5.3. MIH SAPs include the MIH upper layer SAP, which is used by the users of MIH to gain access to various MIH Function services, and MIH lower layer SAPs, which are used by MIH FunBction to gain access and control of a variety of media dependent 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. IEEE8Tnmember !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ۀہۑےۓ۔ەۖۗۘۙۚۛۜ۝۞ۣ۟۠ۡۢۤۥۦۧۨ۩۪ۭ۫۬ۮۯ۰۱۲۳۴۵۶۷۸۹ۺۻۼ۽۾ۿ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 ݎbc+Policy engine is not the only upper layers.d152g2413wAccepted 2006/07/20 2006/04/28 ݏE YoshihiroFOhbaGMember^Technical, Non-binding_22`8a5.4.3cAThe following paragraph talks about the static and dynamic information. But it needs to be clarified little bit as to which one is static and which one is dynamic. " The Information service also provides access to static information such as neighbor reports. This information helps in network discovery. The service may also provide access to dynamic information which may optimize link layer connectivity with different networks. This could include link layer parameters such as channel infoBrmation, MAC addresses, security information, etc. Information about available higher layer services in a network may also help in more effective handover decision making before the mobile node actually attaches to any particular network. "d161g2412v$Commenter to provide suggested text.sted text.berbreplacelinkbynetworksincethisisnetworkselectionܡVreplacelinkcommandindicationwithlinkcommandrequest9V7 ,'bA  33as Editorial)_31`3a5.6.2.1bAfix the inconsistency.@A  33cmInconsistency 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  33d221g2247 2006/06/21 2006/04/2412&EQiaobingFXieGMember^Technical (was Editorial)_31`3a5.6.2.1bAfix the inconsistency.@A  33ccy.@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  33d221g2247 2006/06/18 2006/04/2412&EQiaobingFXieGMember^Technical (was Editorial)_31`3a5.6.2.1bAfix the inconsistency.@A  33c2247 2006/05/14 2006/04/2412&EQiaobingFXie9Dibremovesections7.4.15.3.27.4.15.3.37.4.15.3.4oVremovesections8.5.3.19and8.5.3.20>V14lue 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   PENada, 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 2006/07/20QENada, Golmie, Member^ Editorial_68`53b5Remove the word "request" at the end of the sentence.chImproper sentence "This primitive returns the result of the query to discover link layer events request"d504g2269 2006/07/20RENada, Golmie, Member^Technical, Binding_68`16b" at the end of the sentence.chImproper sentence "This primitive returns the result of the query to discover link layer events request"d504g2269 2006/05/1406/04/246\EQiaobingFXieGMember^Technical, Binding_47`12a6.3.2b/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.d330g23824P݅bFix it.cbIn some places IEEE 802.21 has somehow been clubbed together as IEEE802.21, it should be separate.d29g2421 2006/07/20 2006/04/28݆E YoshihiroFOhbaGMember^ Editorial_5`5a2bFix it.cGPage 5, second sentence it should All instead of Al (one l is missing).d37g2420 2006/07/20 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 2006/07/20 2006/04/28݈E YoshihiroFOhbaGMember^ Editorial_88`48a 7.4.6.1.1b"entities make"c"entities makes"d611g2423 2006/07/20 2006/04/28tencyd20 2006/05/14۝ESanjeever^ Editorial_3`59a1.2b}Use "in" before "mobile node" Also suggest using a word consistently, "terminal", "mobile node", "mobile device", but not allc Consistencyd20 2006/05/14۝ESanjeevc Consistencyd20 2006/05/14۝ESanjeev.^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 age  6cA'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.d647g2220wAccepted 2006/07/20 2006/04/30 | C | |6 : BI_CASTING_REQUEST | | |7 : HANDOVER_CANCEL | | |8 -31 : RESERVED @A>  33_ 33} >con | Bitmap | 0-31 | 0: LINK_DISCONNECT | mzdESrinivasF 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.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+}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. d312g2211vChange AAA to MIH RegistrationwAccepted-Modified 2006/07/20 2006/04/26 ~EBenjaminFKohGMember^Technical, Binding_48`16a6.3.4bGSpecify the format or give greater details in the various Value fields.cA Specific format for the value portion in each type of information element is vague or not defined. For example the Link Type Values for 6.3.4.1.1 is not defined although the length for each Value field is defined. Same for Cost in 6.3.4.2.3 and elsewhere in the draft.  d403g2216v by 378, 380w Superceded 2006/07/20 2006/04/26 EBenjaminFKohGMember6 7bAnChange 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/07/20 2006/04/28Marked8"^technicalbindingVVVVVVl 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/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_80`1b!Revisit whether this is suitable.006/04/28EEleanorFHepworthGMember^Technical, Binding_74`9a7.3.9 IDs[ۂEGuo JunXiang / Shu GuimingGOther^Technical, Non-binding_94`39a 7.4.10.1.2blanguage 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.mRejected 2006/07/20 2006/04/24 ۂEGuo JunXiang / Shu GuimingGOther^Technical, Non-binding_94`39a 7.4.10.1.2bected 2006/05/14 2006/04/24   33d863g2341 2006/05/14 2006/04/24ۀEQiaobingFXieGMember^Technical, Binding_148`1aAnnex BbRemove Annex B.cA8The relevance of Annex B in 802.21 spec is questionable.8@A  33d892g2342 2006/05/14 2006/04/24ہEQiaobingFXieGMember/@ [OcAMIH 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 KimkHow 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 2006/07/20 2006/04/28PEAjayFRajkumarGMember^Technical, Binding_138`51a8.6.1.2bThe broadcast mechanism with layer 2 transport would be different than the layer 3 transport and should be specified in separate sections.chall be able to indicate to the mobile node..."cchnical, Binding_84`30a7.4.2b7Add the sections as described in DCN 21-06-0622-00-000045& 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. won the brief descriptions on 4 primitives.d501g2216 2006/05/14 2006/04/2816  ,mcA  33ng_107`33a 7.4.15.2.2bAMIH_REPORT InfoQueryResponse @A*   *m@AR 33   ' 2 33RcNLink_Configure_Thresholds.confirm should be Link_Configure_Thresholds.responsed515g2422 2006/05/1848|EKenichiFTaniuchi^Technical, Binding_107`33a 7.4.15.2.2bAMIH_REPORT InfoQueryResponse @A*   *AR 33   ' 2 33RcNLink_Configure_Thresholds.confirm should be Link_Configure_Thresholds.responsed515g2422 2006/05/1848|EKenichiFTaniuchi^Technical, Binding_107`33a 7.4.15.2.2bAMIH_REPORT InfoQueryResponse @A*   *420 2006/05/141zEKenichi6^ Editorial_17`6-7a5.3.1b'None offered, unclear intent of phrase.c8Vague sentence "depending on its position in the system"d125 2006/07/207EFarrokhFKhatibiGMember^ Editorial_18`37a5.3.2b*Change "be communicating" to "communicate"cTense consistencyd134 2006/07/208EFarrokhFKhatibiGMember^ Editorial_18`65a5.3.2bremove dash in "link-state"cInappropriate use of dashd139 2006/07/201bj"intra-roaming" should be defined. The whole 2nd sentence in that paragraph may be removed as unclear (?)cUnclear definitiond104 2006/05/14۬ESanjeevFAthalyeGMember^Technical, Binding_16`1a5.3.1b8Remove reference points from figure and rest of documentdefinitiond104 2006/05/14۬ESanjeevFAthalyeGMember^Technical, Binding_16`1a5.3.1b8Remove reference points from figure and rest of documentt of documenthnical, Non-binding_9`10a3bDelete the definition P` _bAThe first step is to re-organize the IEs into a tree (or multiple trees) structure, establishing the contextual information. Then a retrieval mechanism that can both deliver the contextual information of the retrieved IEs and give greater flexibility to the requester must be developed. Change the text to: The Heterogeneous Neighborhood Information may be retrieved by using the mechannism that allows client devices to control the extent of information to retrieve and delivers both the vaBlue of the IEs and the contextual information of the retrieved IEs. the following mechanisms provided by MIIS. - Heterogeneous Neighborhood Information using specific IEs: The IEs defined as part of Information Service provide information about different neighboring networks. For example, by using request and response mechanism with TYPE_IE_LIST_OF_NETWORKS option the mobile node may be able to retrieve information on different types of neighboring networks such as 802.11, 802.16, CDMAi 1bBties | 4 octets | PoA Capability bitmap | | | | Bit 0 : Security Y/N | | | | Bit 1 : QoS Y/N | | | C | Bit 2 : Internet Access Y/N | | | | Bit 3 : IP Version 4 Y/N | | | | Bit 4 : IP Version 6 Y/N | | | | Bit 5 : Emergency SeݖeQIENada, Golmie, Member^ Editorial_54`50bRemove the first sentence.c Service-Info 1 Informs if service information is available 0: Restricted 1: Unrestricted  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. d419g2259 2006/07/18IENada, Golmie, Member^ Editorial_54`50bRemove the first sentence.c 1: minute Z }bA--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. @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/141zEKenichib`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.d442g2309 2006/07/20 2006/04/24aEQiaobingFXieGMember^Technical, Binding_55`11a6.3.6bRemove section 6.3.6.cAThis mechanism (retrieving network info using specific IEs) is limited in its usefulness because the value of many IEs are only meaningful within their context, but this retrieval mechanism is not capable of delivering the contextual information of the retrieved IEs. For example, A requester queries about three IEs: NUMBER_OF_POA, ROAMING_PARTNERS, COST In return, it receives: NUMBER_OF_POA=20, ROAMING_PARTNERS={A, B, C}, COST={10, 12, 7, 8.5, 2.3} However, since there is no contextual , number of operators for each link type, and a list of operators for each link type. @mݲE YoshihiroFOhbaGMember^ Editorial_112`5a8.3b "register"c "rregister"d701g2428 2006/07/20 2006/04/28ݳE YoshihiroFOhbaGMember^Technical, Binding_113`21a8.3.2b;- 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/07/20 2006/04/28 ݴE 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 carefullyrotocol.wRejected 2006/07/19 2006/04/28 d ding_113`49a8.3.2.1 bcAThe 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/07/20 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 2006/07/20 2006/04/24ہEQiaobingFXieGMember^Technical, Binding_150`1aAnnex CbRemove Annex C.cSuperceded 2006/07/20 2006/04/24 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. /@ FbBset | | |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@3.7.2bEEleanorFHepworthGMember^Technical, Non-binding_63`9a7.1.152`19^7 ijinleewVVbVVVdVkimW:W;W<W=W>WuWW8W9WNWOWWWWWW+W>WBWOWPWQWjWsWxW7WleewWWbWWWdWmathieu!WWWWWWW0W݄WݍWWW,WgWhWmathieuperesse!VVVVVVV0V݄VݍVVV,VgVhVohbaBWjWkWmWnWoWzW{W|W}W~WہWWWWW݀WoWperesse!WWWWWWW0W݄WݍWWW,WgWhWqiaobing۬WWWWWW+W,WܬWܳWܽWW2WOW݂WWW(WUWUWUWUWUWUWUWUWUWUWUWUWUWUWUWUWUWVVV+V,VܬVronny<WuWNWWWW+WOWPWQWjW7W'ۭ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 2006/07/20ۮESanjeevFAthalyeGMember^ Editorial_17`27a5.3.1b-Model after similar clause on page 17 line 38c8Break down sentence for better readability, after comma.d119 2006/07/20ۯESanjeev5.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 2006/05/16ۮESanjeevFAthalyeGMember^ Editorial_17`27a5.3.1b-Model after similar clause on page 17 line 38c8Break down sentence for better readability, after comma.d119 2006/05/16ۯESanjeevESanjeevFAthalyeGMember^ Editorial_17`27a5.3.1b-Model after similar clause on page 17 line 38c8Break down sentence for better readability, after comma.d119 2006/05/16ۯESanjeeveevl =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  33d759g2273i Ronny KimmRejectedvby comment 597w Superceded 2006/07/20 2006/04/24 >EQiaobingFXieGMember^Technical, Binding_137`14a8.5.3.19bA&Remove Sections 8.5.3.19 and 8.5.3.20.&@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  33d854g2274i Ronny KimaWK=SENada, Golmie, Member^Technical, Binding_67`22bink 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. d502g2270v4Add this in section 8. Add IDs for commands as well.wAccepted-Modified 2006/05/22SENada, Golmie, Member^Technical, Binding_67`22b 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. d502g2270,8iWolfgang Grtingj7agreed: Fragmentation is handled by transport protocolskQtrasport protocols like TCP or 802.11 MAC have their own methods for fragmenting.wDeferred 2006/07/20 2006/04/28 EEleanorFHepworthGMember^Technical, Non-binding_110`27a8.1b!Suggest to delete this sentence. 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 tstanding indication which should only be received by the MIH function, not by any upper layer.d534g2293wAccepted 2006/05/22 2006/04/24i#RݚE YoshihiroFOhbaGMember^ Editorial_59`65a6.3.8.1bChange it to "XML."c"XML.."d464g2417 2006/07/20 2006/04/28ݛE YoshihiroFOhbaGMember^Technical, Binding_66`1a7.2.2.1b- 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 d490g2398wAccepted 2006/07/20 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.d527g2341kIdentifier and MacNewPoA should be replaced with one unified LinkIdentifer TLV.d527g2341wDeferred 2006/06/20 2006/04/28MarkedMarkedihiror,EFarrokhFKhatibiGMember^ Editorial_8`51a3bbRephrase "... collects information on networks in its locality." Similar change on page 9 line 6.cImproved phrasingd68 2006/07/20-EFarrokhFKhatibiGMember^ Editorial_9`31a3b(Replace "maintenance" with a better termc unclear termd75 2006/07/20.EFarrokhFKhatibiGMember^ Editorial_9`38a3b%Change "the occurs" to "that occurs".cTypographical errord79 2006/07/20/EFarrokhFKhatibiGMember^ Editorial_14`26a5.1.6b/Page 14 line 26: "set up", instead of "setup".cNoun vs. verb.d96 2006/07/200EFarrokhFKhatibiGMember^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."cof an L2 link that "cew ----&*1[bMRemove "(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 2006/07/20\ENada, Golmie, Member ^Technical, Binding_75`51bASince 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 . Add wbA$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." @Af 33   33% 33y  33 33fd767g2308 2006/07/20xENada, Golmie, Member^ Editorial_118`28bA8Replace "values rae assigned" with "values are assigned"8@܄cA܆cAC܉g܌_q܎@܏@]ܐܓkܕ@ ܖ@bAsܗ@vA*C)ܘ@(c'ܙ@Gܛ@ܜc`ܝ@c`ܝ@@ܚ@ Gܘgܚ@ ܚ@  gܚ@ ܚ@ ܕ@ܕ@ܔܕ@ܕ@ܕ@bAܔܕ@ܕ@ܕ@ܕ@ܕ@ܔܕ@ܕ@ܕ@ܔܕ@ܕ@ܕ@@ܕ@ܕ@ܔܕ@ܕ@ܕ@ܕ@ܔܕ@ܔܕ@ܔܕ@ܔܕ@ܕ@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/14rial4/c2@3@5bAb7bAcA9bA:@cACA ;@><@=bACEF@cAA@ CcND@3Fv0G@ HbAsCEeI@ cAL`vN@cP@RbA CKS@bATbAU@[bAVbAc&WcXbBYbAd&[b\bB*DFc^@bAQ`ba@cbAxwecAf@gbLi@ckc l@ 33 t 33>c2The use of the term "MIH proxy" should be avoided.d114g2391i Qiaobing XiemAcceptedwAccepted 2006/07/20 -EDavid FFamolari^Technical, Non-binding_140`1a Annex A-1cfor that particular MN. "v@A> 33 t 33>c2The use of the term "MIH proxy" should be avoided.d114g2391i Qiaobing XiemAcceptedwAccepted 2006/07/20 d 33d739W kmacceptedZ۳۴۶۾ʃ+,89NܬܳܽԃO݂(>BUsaccepted-clarifiedݓ13DKaccepted-modifiedӃ=Cܹܼܾdށquestion"/Ń-Srejected#0:;<=>ABY\_bjkmnouz{|}~ہےۓ۬۵ "Oܸܻܺƃڃ 2݀)+06OPQgjorvxމrejected-duplicateݫsupercededX]w۷!bݩݮݱR7npand:Wbe:Wby:Wcan:Whandover:Whandovers:Whorizonbtal:WW104ܦW108۬W142W162۷W۸W18۳WW187݄W22۳W27/28ܬW3۴W5.3.12W552W57/58W583W6.3.1W8-8!W݂W802.21W802.21enablesbothl2andl3transportoptionsVZk }bc=Description of RDF_DATA under InforqueryType is not corrcet. d672g2424wAccepted 2006/07/20~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, " BCSWXYrsxz2222222777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777EGregFDaleyGMember^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". cA 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 d519g2219 2006/07/20EGregFDaleyGMember^Technical (was Editorial)_18`48a5.3.2bo change to include 802.11 (which also may have this case in a (visited) enterprise environment). c@0#@$‚E%P;SUkcommon/Wcommunicate/Wcommunicating/Wcommunity۾Wcompletely/WAWݓWcomplexaWcomplicatedݻWcomplicatesWcomponentܶWcomponentsWcomprehended۳WconceptsWconfigure\WconfiguredWconfirmWconfusing۴WWWWconsensus<WjWconsiderSWconsidered0WconsideringWconsideringprimitivetypeswiththeirdirectionconfirmpriVconsistentWconstrainedWconstructWconsumerWcontainWcontextWݓWcontextual_WconvertWB EcAMIIS provides the ability to access this information about all heterogeneous networks in a geographical area This is supeflous, remove it@A>  33$  (  33>d168g2233 2006/07/20 2006/04/28EPeretzFFeder^Technical, Binding_23`44bAd) MIH_NET_SAP: Generic name for the media-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 ||||||||||||||||||||||||||||||||||||||||||.7:mRejected 2006/07/20 2006/04/244 ;EQiaobingFXieGMember^Technical, Binding_66`53a7.2.2.1bA8Remove "MIH Network Address Information" from Table 14.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  33d496g2271i Ronny KimmRejectedwDeferred 2006/07/20 2006/04/2414 EQiaobingFXielk35EAjayFRajkumarGMember^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@of the MIH_LINK_SAP)."E@ۚۛESanjeevFAthalyeGMember^Technical (was Editorial)_3`53a1.2bReplace "both" with "either"cSemantics correctiond18v9Change as follows...."....which may be wireless or wired"wAccepted-Modified 2006/07/20 using a word consistently, "terminal", "mobile node", "mobile device", but not allc Consistencyd20 2006/06/18۝ESanjeevFAthalyeGMember^ Editorial_3`41-45a1.2bTFor consistency with uses elsewhere "mobility management" is spelled without a dash.cf EcADEntry 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/07/20 2006/04/2814 FEAjayFRajkumarGMember^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/07/20 2006/04/2814 GEAjayFRajkumarFRajkumarFRajkumar%:&^Technical, Binding_49`17a 6.3.4.1.2blEither in Table 6 it should be 2 octets or this table should be 4 octets. However, it should be 4 octets cULength is 2 octets whereas IE Table (#6) says it is 4 Octets. This is inconsistent. d416g2453vby comment 415w Superceded 2006/07/20a 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 sugBhgested remedy is to identify and re-classify all the current IEs in 6.3.4.1 to represet them as a tree.VcThe current Information Elements in Section 6.3.4.1 need improvement. In partocular, the current definitions are expressed in a flat, unstructured list. This fails to show the relationships among the Information elements. d412g2306 2006/05/14 2006/04/24^EQiaobingFXieGMember^Technical, Binding_49`12a 6.3.4.1.2bRemove 6.3.4.1.2.68 1bA5.6.1.4 LSAP The LSAP, defined in the IEEE 802.2 standard, provides the interface between the MIH Function and the Logical Link Control sublayer in IEEE 802.3 and 802.11 networks. This SAP is used for local MIH exchanges between the MIH Function and the lower layers of the 802.3 interface (as the 802.3 instantiation of the MIH_LINK_SAP) and for the L2 transport of MIH messages across 802.3 and 802.11 access 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........iqiaobingxie۬VVVVVV+V,VܬVܳVܽVV2VOV݂VVV(VUVronny:W;W<W=W>WuWNWWWW+WOWPWQWjW7W7W7W7Wd 2006/05/147 #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 2006/07/20 2006/04/24$EQiaobingFXieGMember^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  33d177g2244 2006/07/20 2006/04/24%EQiaobingFXieGMember^Technical (was Editorial)_30`36a5.6.1bAfix the inconsistency.@A  33cq kBo point out that optionally supported feature is not the same as the text for the feature is informative. The commenter seems to misunderstand between "optional" and "informative". " Including XML and TLV decoders into these devices will prevent upgrade of existing and resource constrained systems to include 802.21. " Since both XML and TLV are optional, there is no need to support both decoders. m Supercededvby comment 462w Superceded 2006/07/20 ired for XML/RDF query. TLV query does not need the schema. Also both XML and TLV queries are optional. We need clarification text on this in 6.3.8. Also it is important tresponse. mRejected 2006/05/14 EGregFDaleyGMember^Technical, Binding_59`45a6.3.8z ekalsoܶWܸWܹWWW+W-WalternativeWalternativelyWalternativelymihprotocolmessagesmaybeencapsulatedusinValways/WamoreKWan"WAWWW WWݻWWdWand"W#W/WaW۳W۴W۵W۾WWWWWWW"W|WWWsultofadhocdiscussionwehadgroupconsensusthat<VaspectܸWat0WݴWbase-WbasicZWbeZW\WaWjWkWuWWWܶWܺWܻWW݀W-WbemorespecificforinformationservicetoworkandunderstVbecomeݻWbeforeYWzWWbetweenZWjWkWbitsWbootsrappingܺWboth=Wbroadcast/multicastܻWbut0WW=W|WWݻWbyXWwWWWbWܻWcan\WuWܶWcapabilitybWcarefulܹWcaseCWWcasesoWclaimBWclarificationۓWܹWclarifyWclarifyingW*kclear_WۓW۴WܸWܻWWWW1W3Wclera۵WWclient/W۳WWܶWcodeWcoderݻWcoding|Wcombination W|Wcommand0Wcommands0W۵WݓWcommentXW]WbWےW۷WW!WWW݀WݩWݫWݮWݱWWcommenterWcommenter'sWcommenter'srighthowevernotonlyfigure29butalsowholeVcommentsRWSWcate/Wcommunicating/Wcommunity۾Wcompletely/WAWݓWcomplexaWcomplicatedݻWcomplicatesWcomponentܶWcomponentsWcomprehended۳WconceptsWconfigure\WconfiguredWconfirmWconfusing۴WWWWconsensus<WjWconsidered0WconsideringWconsideringprimitivetypeswiththeirdirectionconfirmpriVconsistentWconstrainedWconstructWconsumerWcontainWcontextWݓWcontextual_WconvertWkgeneralWWWgenerateWgeneric۾WݓWKWgiveAWgoingdWgood۳W۶Wgoodpoint۶Vgroup<WܸWjWhad<WjWhandWhandover"W/Whandovers۾W-Whanging6Whas0WܺWWW1W3WdWhave0WAWYWaWuW۵WWW|WWWhavewedecidedthatmihfunctiondiscoveryisoutsidescopeuVhaven'tܶWhavingWheaderݻWWhelpsWhence۵WDWhereWheterogeneousWhigh-levelWhigherWxWhighlyWhindersWhoc<WjWhow\W۾WWOWhowwecanmandatemediaspecifictechnologyeventhoughiuOVhowever"WWWhttpWhvae"WiuWW0WaWWܺWWWifthisinformationistoberetrivedusereportsliketypeaVifwedon'tneedtohavesectionsaboutexistingsapsandprVimplementationuWWimplements49  bcAOThere 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 2006/07/20 2006/04/28Marked EPeretzFFeder^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 2006/07/20 2006/04/28Marked EPeretzFFeder^ Editorial_30`36a5.6.1b5.6.1 Media Dependent SAPst;ENada, Golmie, Member^Technical, Binding_42a6.3b.Review section 6.3 and make changes as needed.cIf comment 9 is accepted to modify the definitions of horizontal and vertical handovers, section 6.3 needs to be updated to reflect that change. This is especially relevant to the use of the term "Access Network".d309g2245wAccepted 2006/07/20 d eds to be updated to reflect that change. This is especially relevant to the use of the term "Access Network".d309g2245wAccepted 2006/05/17Marked 4/28ckthismakesthefigureveyconfusingmaybeusetwosepartaefVthisshouldbetrueforeventsandcommandsaswellatransaݓVthistypeisusedtoinformwhattypeofcodingisusedwith|VthoughOWthrough۵W۾WWdWthroughout۳WthusWܶWtimeQWtimesW1W3WtlvYWaWWWCW|WܸWWtlvsWto"W/WAWaWbWjWkWmWnWoWzW{W|W}W~WہWےWۓW۳W۴W۵W۾WWWW W|WܶWܺWWWWݓWݻWWW)W-W1W3WSWxWtransactionݓWWtransmissionWtransportWtrasportWtrasportprotocolsliketcpor802.11machavetheirownmetVtreejWkWmWnWoWzW{W|W}W~WہWW|W}W~WہWہWWmWnWoWzW{W|W}WWݻWoWused|WWݳWuseful<WjW۸b"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/07/20 d@  AbcAjText needs improvement. A lot of discussion is speculative in nature and can be removed from this section.j@A  33d322g2277iSubir kWe 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. mRejected 2006/07/20 2006/04/24 BEQiaobingFXieGMember^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 Ohbajey are added may become part of the more extended set of MIIS capabilities.  @+ |bBmaps 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/07/20 2006/04/28 d Please 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. ormance 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. I ZbARelationships 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.mAcceptedv2006/05/17 2006/04/246 rkimproveAWin"W#W/WuW۳W۴W۵W۾WWWWWܶWܸWܼWWWݓWݴWݻWWW)W+W-WDWKWSWdWoWincaseanmobilenodehastheinformationofthemacnewpoadVinsection6.3.4.2.5itisnamedtypeienetworkqosinsteadܼVincludeWincluded/WWܺWWWdWinformativeWinterface+WintergerݻWintoWintroductionjWkWmWnWoWzW{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ܺVisthisfortlvonlyisthatisthecaseweshouldsaytlviCVVV|9kremedyWremoteWremoveےWremovingWrenewalWrepeatedWrepetition]WreportaWreportsaWrepositoryWrepresentݻWrepresentationWrequestxWrequesttypeprimitivecannotbeissuedfromlowerlayertoxVrequest/responseܺWrequestsWrequireWrequired/WWWWWoWrequiringWresourceWresponseWWW|WܻWresult<WWjWretrievaljWkWmWnWoWzW{W|W}W~WہWWretrievedWretrivejWkWmWnWoWzW{W|W}W~WہWretrivedaWreviseWrfcWrfc4889WrightWroutingݴWsameW"WݫWsameascomment626ݫVsapW1W3W6WDWWseveral#W\WܬWshouldYW\WCWܻWW-WshowsZWsimilarAWbWsimilartocomment444doesthisnotmeanweneedsemanticqbV =bEAof column Representation with List of TYPE_IE_LIST_OF_NETWORKS cA1- The information element "TYPE_IE_LIST_OF_NETWORKS" represents a list of network types and not a list of networks. 2- The description for "TYPE_IE_LIST_OF_NETWORKS" is misleading. It states: "List of Neighboring Access Networks. Link types of the networks that are available in a given geographical area". The list of Access Networks and list of link types should be two different lists. 3- The Representation of the list suggests to use RADIUS NAS-Port-Type to code the list. This shouldB be the representation of ONE link type not a list. 4- The Lenght of the list is set to 4 octets. It is improper since a list can have variable length. This size is the size of one item.d346g2247i Subir DaskGI understand the reason but do not understand why we need both the IEs.mAccepted-ModifiedvZRelated to comment 345. Shall be worked upon and further contributions would be submitted.wRejected<NcThe use of "for example" is inappropriate in the representation entry for TYPE_IE_LIST_OF_NETWORKS. The representation should be properly specified. d349g2241i Subir DaskI 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/07/20 2006/04/286 EEleanorFHepworthGMember^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 2006/07/20 2006/04/286 EEleanorFHepworthGMember^Technical, Binding_44`58a6.3.28a6.3.258a6.3.2EEleanorFHepworthGMember^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 2006/07/20 2006/04/286 EEleanorFHepworthGMember^Technical, Binding_45`53a6.3.2bThe 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.hnical, Binding_45`53a6.3.2bThe 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.dependent.dependent.kissuejWkWmWnWoWzW{W|W}W~WہWܺWissuedxWit0WAW\WaWjWkWmWnWoWuWzW{W|W}W~WہWۓW۴WWWWܶWܹWܺWܼWWWWitdoesn'tmakesensetomanditorilysupportxmlandtlvVitisnotclearwhatadditionalthingsweneedtodowiththۓVitshouldbeclearwhichreferencepointsareoptionalinfor۴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 o{ܻkzThe reason is not clear. Why is broadcast/multicast necessary for query? Query should be followed by unicast response. mRejectedwRejected 2006/07/20 ܼEVivekFGuptaGMember^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"kuIn 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/07/20 ܽEVivekFGuptaGMember^Technical, Binding_54a6.3.5EVivekFGuptaGMember^Technical, Binding_47`26a6.3.2  ]RbC 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. d502g2270v4Add this in section 8. Add IDs for commands as well.wAccepted-Modified 2006/07/20 d  kthereasonisnotclearwhyisbroadcast/multicastnecessaryܻVthesectionisdescribingtheidsusedformihfprotocolݳVthewholenotionof802.21asspecifiedintheparistoopt-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#V3xCcThe namespace MUST be assigned by 802.21 to satisfy interoperability. If the Information Elements do not have specific IDs (or Type definition) then 2 implementations of MIHF may not be able to understand each other.d394g2253i Subir Das kDIs this for TLV only? Is that is the case we should say TLV IEs.... mAccepted-ModifiedwAccepted 2006/07/20 d ?EEleanorFHepworthGMember^ 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/07/20 2006/04/2820EEleanorFHepworthGMember^Technical (was Editorial)_48`30a6.3.4b0Clarify the relationship between these sections.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/07/20 2006/04/2820 ]cThe current Information Elements in Section 6.3.4.1 need improvement. In partocular, the current definitions are expressed in a flat, unstructured list. This fails to show the relationships among the Information elements. d412g2306i Subir Dask,This is a repetition (Pl. see Comment # 345)m Supercededw Superceded 2006/07/20 2006/04/24 ^EQiaobingFXieGMember^Technical, Binding_49`12a 6.3.4.1.2bRemove 6.3.4.1.2.cGThe need for TYPE_IE_NUMBER_OF_OPERATORS is not sufficiently justified.d415g2307wAccepted 2006/07/20 2006/04/24_EQiaobingFXieGMember^Technical, Binding_54`60a6.3.5b!^vformatsWforwardlWforwardingݴW*WframeWframework۵W3W 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. 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|ksince#W0WWWWWݴWsincetlvandxml/rdfarefunctinallydifferentinthattlvVsincewearenotaiminginthepresentstateonroutingforwݴVsmallWsoWWOWdWsockets0Wsolution#Wsome/Wgylike802.16hastriggerforiprenewalifthVsomething"WspaceݻWspec"W-Wspecific"WuWWܺW݀W+WOWPWspecificationYWWspecificationsWstaWstandardWstartYWstateݴWstaticWstep"WstructuredjWkWmWnWoWzW{W|W}W~WہWstructuresWsuccess"Wsuch#W\WWsufficientjWkWmWnWoWzW{W|W}W~WہWsuggest"W/WsuggestedWsuggestionWsuggestions/recommen"WsuggestsZWsupercededXWwWWbWW7Wsupercededby577bVsupercededby695Vsupercededby697wVV7Vc\Change MIH Event Register/DeRegister to MIH Event Commands These are commands and not Eventd492g2256wAccepted 2006/07/20 2006/04/2814 4/$EEleanorFHepworthGMember^Technical (was Editorial)_64`12a7.1.1b Move table to informative annex?cNot 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 Kim EEleanorFHepworthGMember^Technical (was Editorial)_64`12a7.1.1b Move table to informative annex?cNot 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 Kimnot mention the LSAPs for wired media.d484g2262wRejected 2006/07/18 2006/04/28 EEleanorFHepworthGMember^Technical (was Editorial)_64`12a7.1.1b Move table to informative annex?cNot 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 Kim Ronny Kims isubirWWsubirdas#V0VXVYV\V]V_VbVےVۓV۷V=VCVܸVܹVܻVVVVVvivek"W/WZW۳W۴W۵W۶W۾WWWWWWWW W!W"WݓWݩWݫWݮWݱWWW)W-W0W1W3W6WDWKWRWSWrWvWށWމWvivekgupta"V/VZV۳V۴V۵V۶V۾VVVVVVVV V!V"VݓVݩVݫVݮVݱVVV)V-V0V1V3V6VDVKVRVSVrVvVށVމVVVVVWWWWW+W,WܬWܳWܽWW2WOW݂WWW(W)WUWyoshihiroBWjWkWmWnWoWzW{W|W}W~WہWWWWW݀WoWyoshihiroohbaBVjVkVmVnVoVzV{V|V}V~VہVVVVV݀VoVE&kquery/response|WquitejWkWmWnWoWzW{W|W}W~WہWradiusۓWraeWrangingWrate"Wrdf/sparql/owlWre-submission݀WreadjWkWmWnWoWzW{W|W}W~WہWreadilyWreallocationݻWreason=WܻWWreasonsWreceivedWrecommendWrecommendedjWkWmWnWoWzW{W|W}W~WہW݀WreconfigureWreference"W۴WWrejectWrejectedW1W3WWrelationshipsZWq,bOExtra 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/07/20 2006/04/28MarkedkusingWW"Wvalue۴W۵W۾WWvaluesݻWvariation/Wversa/WversionWvery۳WW-WKWverygoodpointsthemiiscanbelocallyplacedontheclien۳VveyWviaWvice/WwayjWkWmWnWoWzW{W|W}W~WہWWDWways\WuWWwe#W0W<WAWYW\WaWbWuWۓW۵WW"W=WCW|WܶWWWݴW1W3W6WOWjWwehaven'tmentionedwheremiisistobelocatedthusitcanܶVweneedaparagraphsimilartothisthiswillgiveanideaaAVwell۾WWݓWWKWSWWDWwhat0W_WۓW۵WW|WܸWWwhatisapageinthiscontextVwhenW+WwhereܶWwhich"W۴WWW݀WwhileWWWwhileuseofschemaisanoptionrequiredonlyforxml/rdfqVwholeW-Wwhy\WjWkWmWnWV 20bAxRemove "MIH Handover Initiate", "MIH Handover Prepare", "MIH Handover Commit", and "MIH Handover Complete" from Table 14x@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.@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? mRejectedveferred 2006/06/30 2006/04/2414 4  |jbAf 33   ftion 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  33d662g2319iYoshihiro 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.mRejected ncARDF (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  33d671g2323iYoshihiro 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.mRejected6keach0WYWaW"WedcaWedgeWefficientjWkWmWnWoWzW{W|W}W~WہWeither|WelementWelementsWelseuW0Wenable۾Wenabled۳WencapsulatedWencodingWengines۵WenoughWentity/Wentries"Wequivalent0Wessential"WessentiallyWetc"W/WevenWOWevent)Wevents۵WݓW)Wexamined/investigate WexampleےWWWWWexchangeWexchangedWexecution/WWflowYWQWfollowedܻWfollowingWݻWfor"WjWkWmWnWoWzW{W|W}W~WہWےWWWWWCWܸWܻWWWWWݳWݻWWoWformat|WformatsforwardingݴWfragmentingWfrom/WWWxWfunctinalityWfunctinallyWfunctionuW+WOWfunctionalityWfurtherܹWgWL P|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 definition of XML related MIME type TLVs for SPARQL query is not sufficiently justifiBed.@A  33d812g2338iYoshihiro Ohbak2 (from line 41, page 127 to line 8, page 128)cber^Technical, 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>c idasےWۓW۷W=WCWܸWܹWܻWWWWWeunahWW8W9WOWWW>WBWsWxWeunahkimVV8V9VOVVV>VBVsVxVgroting?W@WaWW|WܶWWWXWݳWݴWݻWWTWgupta"W/WZW۳W۴W۵W۶W۾WWWWWWWW W!W"WݓWݩWݫWݮWݱWWW)W-W0W1W3W6WDWKWRWSWrWvWށWމWhongWܼWܾW WhongchengVܼVܾV VjinwWWbWWWdWdWVVV V0V݂V݄VݍVVV,V1V3V>VKVgVhVperesse!W۬WWWWWW+WWWWW W0W݂W݄WݍWWW,W1W3W>WKWgWhWronny<WuWNWWWW+WOWPWQWW8Bj>Use "Contents" instead of "Table of Contents" as section titlemAccepted-Modified 2006/07/20 2006/04/24nVpWvXwYxZy[{\]^_]^_Ã@܇Ã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 ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_Ba?AEQiaobingFXieGMember^Technical (was Editorial)_42`62a6.3.1bAChange 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 access like intra-technology neighbor reports and other link layer information required during handovers is directly available from the access` @c@A  33d318g2276iWolfgang Grtingj3see comment # 315 and change figure according to it 2006/07/20 2006/04/2419  s acBinformation to relate these values to one another, the retrieved information is mostly useless (e.g. It doesn't tell which of the 20 POAs belong to roaming partner "A". Or which POAs are related to cost=12).d444g2310iWolfgang Grtingjb- disagree, if this section is removed, then it is not possible to query particular info over TLV k- If this information is to be retrived use reports like TYPE_REPORT_POA. - It is advisable to keep the TLV queries INDEPENDENT of each other. Otherwise we have to define complex query algorithms with AND and OR operations.vby comment 339 and Issue#3w Superceded 2006/07/20 2006/04/24 bEQiaobingFXieGMember^Technical, Binding_56`62a6.3.7bWkother\WaWW"W|WWݓW0WSWothersWotherwiseaWW6Wout/WWWout-of-bandWoutside/WuW۵W0Wover+WoverlapݻWownWpage#WWܼWpar-WparagraphAWparameterWparameters"W/WWpartW݀WWpastWpatternWperiodicdWpersonallyWpertaining"W/Wpl]W۷WWplseecomment162۷VVplaceWplaced۳Wplaces#Wplease݀Wpleasebemorespecificwhichpartofsection6.3.8isuncle݀Vpoa/WaW"WdWpoint۶WWpointedWpoints۳W۴Wpolicy۵Wpossibility۳WpowerfulWpre-configuration<WjWpresentWݴWpresentedWpreventWpriitives)WprimitiveWWqueriesaWWqueryaWbWjWkWmWnWoWzW{W|W}W~WہWWWW|WܻWWoWhcpExamples provided lack context. Requesting such information without e.g. a geographic reference is meaningless.d452iWolfgang GrtingjEagreed to this comment, check 21-06-606-01-0000_loc_info_over_tlv.docv@No specific remedy provided. Comment 339 addresses this as well.wRejected 2006/07/20ESanjeevFAthalyeGMember^Technical, Binding_56`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/07/20ESanjeevFAthalyeGMember^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/07/20f}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""@pe|k- 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 2006/07/20  ܸ 2006/07/207 ܹEVivekFGuptaGMember^Technical, Binding_47a6.3.3bInclude a descripton for following entries in Table-7: Core 802.21 Hedaer specific IEs: Core 802.21 specific IEs Vendor specific IEs: 14 bit ID: Reserved for other SDOs: Reserved for IETF:c=Entries in table-7 are not clear and need further descriptiond384g3236i Subir DaskQYes, it needs further clarification abd also Table 7 needs careful investigationmAccepted-ModifiedwDeferred 2006/07/20T-7 ܺEVivekFGuptaGMember^Technical, Non-binding_47`23a6.3.2bClarify which IEs are available before attaching to a link and which are available after attaching to a link. Add the missing word "media"c "media"c "media"cec have to be amended each time?d383g3235i Subir Dask I think extensibility aspect is clear in terms of schema definition. Is this for TLV ? Also in table 7 what is Working Group ID? mRejectedvNo suggested remedywRejected 2006/05/177jfacilitate,WfactWfield|Wfigure@WwWWWWWXWW7Wfigure3isdefinitelyanexampleofdeploymentVfirstWWfollowedvWfor"WWWW WXWWWTWgWvWformat|WfragmentationWfromWrWfullyWfunction,Wg۬WܾWgenereallyWgeneric,WgetWgivenBWgivingBWgloballyTWgroupsܾWhandle"WWhandled/WWhandover?Whandovers/WhaveWhelps,WhereܾWWheterogeneous"W/WWhigherW,Whnadovers"Whope,Whorizontal,Whorizontal-handover?Whowal,Whorizontal-handover?WhowWhowWhow?WhowWhowWhowWhowWhowWhowi,WidWWTWhWidentifierWidentifiersݻWidsWWWWieܼWܾW WWiesܾWif"WaWW WgWimplementations"W jinfoݻWWinformationBWWWWܾWWdWinsteadW<WWjWintendedgWintentionWinter-technology?Winter-technologyhandoververtical-handover?Vinteract,Winterfaces,WinterfereWinternetܾWinterpretedܾW WintoܾWintra-technology?Wintra-technologyhandoverhorizontal-handover?VipܾWݍWis"W/W?WBWZWaWWWWWWWWWW>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>W-@b.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/07/20F-24 4 "njagreedfragmentationishandledbytransportprotocolsVagreedtodescribethereasonfornotbeinggloballyuniqueTVagreedtosetthelengthfieldto1|Vagreedtothiscommentcheck21-06-606-01-0000locinfooverVaimedTWalbeit/WallW WalreadyWWalso/W?W݄WanW|WanalysisBWBW"jchangefigure20asshownin21-06-0607-00-0000-sforcommenXVchangetexttoVchangethetableasdefinedin21-06-606-01-0000locinfoovݻVchangetothedescriptionoftypenetworkqoselementtoindVchangetypeieqostotypeienetworkqosܼVcharactersticsWcheckWclarify<WWjWclassified WclearlyZWWW,WcleraމWclientsWcombinationvWcommandsWcomment@WBWuWWWWW0WXW݄WWcomments!WWcommunicate,WcommunicationWTWgWcomparedWcomplex"WcomplexityBWcomputationalBWconditionWconfigurationWW ݴkSince 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.vSince 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/07/20 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 2006/07/20 2006/04/28ݶE 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/07/20 2006/04/28Table 18ݷE YoshihiroFOhbaGMember^Technical, Binding_115`30a8.3.3.1ޏ^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   % 33RcgNot 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 2006/07/20fݻ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/07/20 2006/04/28Table 20ݼE YoshihiroFOhbaGMember^Technical, Binding_124`50a8.4.2.11b*Replace NetworkTypes with Link Identifier.c%NetworkTypes should be LinkIdentifierd799g2370vby comment 527/626w Superceded 2006/07/20 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 2006/07/20 2006/04/28ݾE YoshihiroFOhbaGMember^Technical, Binding_128`24a8.4.2.24b%Change "4: Extended Schema Content"c!Value 4 description is incorrect.Pjneed<WܶWWWW W+WjWvWneedtobediscussedwithcontribution21-06-0611-00-0000-m+Vneedtodecidehowtohandle7.2.1mediadependentsapsfirsVneedtomodifywhole8.6Vneeded/Wnetwork/WWWܼWܾW݄WWvWnetworks"WWWvWneverWnewWݻWdWnewdiagramandtextprovidedin21-06-0612-01-0000-rnetworVnoܶWnorWnot"W/WZWaWWW W,WTWvWށWމWnoteBWnotionWnumber݄WobjectiveWofW/W<WBWWWWWWWܾWWW W,WjWvWokrWon"WBWWWoneWonevdÃ0ݴÃ@ÃPUÃ`ÃpݵÃÃ۔ÃsÃà Ã0Ã@ÃP'Ã`ܑÃpÃVÃ݁ÃyÃܒà Ã0+Ã@ݶÃPܓÃ`ݷÃptÃÃݸÃhÃà uÃ0Ã@ÃPÃ`ÃpܔÃ(Ã5Ã=Ãà vÃ0Ã@ÃPiÃ`Ã`T3 ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnomnoU~isubir#W0WAXWYW\W]W_WbWےWۓW۷W=WCWܸWܹWܻܺWWWWWWWWWWWWWWWWWWW7B lubBnction entities also discover a list of supported events and commands. The MIH Function may also query the information schema for list of supported information elements. [2] MIH remote registration: Remote MIHF in different entities may rregister with each other to receive Media Independent Handover Messages including remote MIES. [3] 2) MIH message exchange: MIHF may exchange MIH messages using MIH payload and MIH protocol over a suitable the selected transport. As part of message eCaxchange the peer MIH Function entities may use the MIES, MICS and MIIS for effective handovers. =@ 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.mRejectedv#See discussion of 06-0611, issue 31wDeferred 2006/05/22 2006/04/24 Qkmihf0W۵W۾WݓWݳWݴWݻWmihf-idݴWmiisAW۳WܶWmisunderstandWmobileWdWmobility0WmodeOWmodel"WmodifiedWmodify6WmodifyingDWmorejWkWmWnWoWzW{W|W}W~WہWۓWWWWW݀WݓWmoveWmuchWmultiple"W1W3Wmvno"WnamedܼWnamesݻWnecessarilyWnecessaryWܻWneed/W0WAWbWۓWWWW W=WWWݴWW1W3WSWneededjWkWmWnWoWzW{W|W}W~WہWWWDwcAFigure 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 2006/07/20 2006/04/24 d ksupercededbycomment394XVsupportWWW+WoWsupportedjWkWmWnWoWzW{W|W}W~WہWWWsupportsWsureݓWsyntaxWsystems۾WWtableWܸWܹWܼWtake۵WdWtalbeݻWtalk#WtcpWtechnologyWOWtermsܸWtextAWWWPWSWtextsWthanWWWWPWtextsWthanWWW<WAWjWkWmWnWoWuWzW{W|W}W~WہWWWWCWWWjWthe0WAWYWZW_WaWjWkWmWnWoWzW{W|W}W~WہWۓWWWWW=WCWܶWܻWWWWWݳWݴWݻWW+W-WdWthecommentshouldberejectedforthefollowingreasonsVthelinklayerqoscharatersticsareavailabletothestaviVthereasonisnotclear0x2161432bitsV cbAUse of a bitmap model to encode the list of events that are supported by 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 supported 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. Event IDs are definedBK in Table XX in section 7.3.1." (see comment 33 for complete definition) 9cA}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.}d583g2288- 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/07/2029: XkandWݓWW-W0W1W3W6WDWannexWany"W/WWݓWWDWanything۴WanywhereuWapis0Wapisapplicationprogramminginterfacesandsuchareoutside0Vappear۴WappliancesWapplicability۾WapplicableWapplication0WappropriateWdWOWbeZW\WaWjWkWuWWWܶWܺWܻWW݀W+W-WOWbemorespecificforinformationservicetoworkandunderstVbecauseWbecomeݻWbeforeYWzWWbetweenZWjWkWbitsWbootsrappingܺWboth=Wbroadcast+WOWbroadcast/multicastܻWbut0WW=W|WWݻW+WbyXWwWWWbWܻWWcallQWcan\WuWܶWOWdWcapabilitybW+WOWcarefulܹWcarrydWcaseCWW+WdWcasesoWclaimBWclarificationۓWܹWclarifyWclarifyingWcAThe 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. d708g2292v0need text for such a comprehensive issue, see 32wRejected 2006/07/20 2006/04/28 EEleanorFHepworthGMember^Technical, Binding_112`53a8.3.153a8.3.1ERksapsWsayCWsaying۴WWscanningdWscenariosWschemaWWWܸWoWschemaismandatoryshouldbeoptionalVschemaeWschemasWschemeWscope/WuW۴W۵W0WsdouWsection#WܼWWW݀WݳWݻW)WDWsectionsWsee]W۷WW!WݮWWseecomment362!Vseecomment636ݮVseemsWWselection/W۵WsemanticbWWWsendWsense۾WWݓWsepartaeWWserverOWservice0WWWdWservices۵W۾WݓWseveral#W\WshallWshould/WYW\W۴W۾WWWW WCWܻWWWݓW6WOWshouldn'tWshow6WshownKWsimilarAWbWKWsimilartocomment444doesthisnotmeanweneedsemanticqbV0^technicalwaseditorialVVVIVRVnVޖVޗV:V;V?Vwas W$W%W&W(W*W+W,W@WAWCWKWYWpWsWvWۛWۼW۽WWWWWWWW9WNWOW[W]WܭWWWWWWWWWWWWWWWIWRWnWޖWޗW:W;W?W\vmn۳W۴W;W{WݓWWmns;Wmobile۫W;W"WޏWmobile/network݊Wmobility"W4W5W`WmodelWݓWmodificationsWmodified"WmodifyWLWMWmodifythesentenceappropriatelyVmodifywithinterfaceidentifierLVMVmoreBWZWWJWܛWܿWVWmove WNWmovethesectiontoappendixalsolookatcomment673NVmultiݓWmulti-hopݓWmultiple@WܐWܗWmustTWnWWnamegWnamingܗWnas-portJWnas-port-type^WnecessaryWneedBWRWTWZWۆWۈWۊW۴WܗWܛWܢWWW;WFWVW{WistofoperatorsVneedclarificationforrequestparametersupdatescanresponseۆVneedmoreclarificationandappropriatesuggestedremedyVVneedtextforsuchacomprehensiveissuesee32VneedtoprovideclarifyingtextalongwithcommentܢVneededܗW WneedsWEMathieuFPERESSEGObserver^Technical, Non-binding_111`12a8.2.1bAs the section is dealing with L2 Data Frame Packet Format, it is not relevant to mention anything related to layer 3. Another section can describe the L3 Packet Format. Remove the sentence "The above frame structure...".c"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/07/20 2006/04/30 EMathieuFPERESSEGObserver^Technical, Non-binding_111`18a8.2.1bRemove the sentence. 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/07/19 2006/04/30 EMathieuFPERESSEGObserver^Technical, Non-binding_111`18a8.2.1bRemove the sentence. sentence.7soironnykim:V;V<V=V>VuVNVVVV+VOVPVQVjV7VgjcouldݍWcouldyoupleasedefineipaddressaquisitionandipaddressݍVcovers"WcreateܾWcurrent"WZWWdataWdecideWdecidesgWdefine"WݍWdefined?WݻWWdefinitelyWdeletewWWWW7Wdeletefigure24wVVV7VdeletethefigureVdependentW WdepictvWdeploymentWdescribeTWdescriptionWdesignWdetailedBWdiagramZWWdifferent"W,WdisagreeaWܶWݳdisagreeifthissectionisremovedthenitisnotpossibleaVdisagreethereisnoneedtoexplainwhereitislocatedܶVdisagreed|WWdisagreedfortransactionidVdiscusseduWݴW+WdividedܾWdoWWdoyoumeanherefigure23VdocBWW݄WݻWdocument۬WW۬W۬Wt۬W۬W۬W۬W۬WW۬WWW+WݻWKWdocument+W+W+W PcA/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/07/20 2006/04/28QEAjayFRajkumarGMember^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 Kimk)No proposed correct call flow this time. mRejectedv$no suggested text. Issue identified.wRejected 2006/07/20 2006/04/2829REAjayFRajkumar? kthisOWQWSWthishasbeenbroughtupmanytimesinpastaswellthevaluVthisisarepetitionplseecomment345]VthisisnotthecorrectflowspecificationshouldhaveieliYVthisisnottruesinceseveralplacesinthissectionwetal#VSRGMember^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/07/20 2006/04/2825call flow this time. mRejected 2006/07/20 2006/04/2829REAjayFRajkumarGMember^Technical, Binding_146`12aAnnex-3b(Change the Category to "Command Service"w.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 Kimk)No proposed correct call flow this time. mRejected 2006/07/20 2006/04/2829REAjayFRajkumarGMember^Technical, Binding_146`12aAnnex-3b(Change the Category to "Command Service"z kare0W\W۴W۵WWWWWݴW)W0W6Waren'tWas"W#W/W0W<WjWkWmWnWoWzW{W|W}W~WہW۴W۵WWWWܼWݓWݫWWW-WKWOWSWjWasaresultofadhocdiscussionwehadgroupconsensusthat<VjVaskWaspectܸWassistWassociateWat0WݴWavaiableWavailableWbackbone+Wbased WbasicOWbe"W/W\WaWuW۳W۴W۵WWWWWW W"WOWܶWܺWܻWWW݀WݓWW)W+WOWxWbecauseWbecomeݻWbeenW1W3WbeforeYWW1W3WbehaviourWbetterW)WcapabilitybW+WOWcarefulܹWcarrydWcaseCWW+WdWcasesoWcertainWchangesWclarificationۓWܹWclarifyWclarifyingWclassesW:kadvertise+WadvisableaWagreeWWagreethatmoreclarifyingtextsraerequiredVagreedWaid/WaimingݴWair+WalgorithmsaWݴWall/WWallocatedݻWallowWalong۴WalreadyWݻWalsoWQjk_As a result of ad hoc discussion, we had group consensus that IP pre-configuration is useful. mRejectedwDeferred 2006/07/20 2005/11/06 kESrinivasF Sreemanthula^Technical, Non-binding_86`48a7.4.14b 33   33f 33>c ~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/07/20 2006/04/2423 EQiaobingFXieGMember^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. /@Q knotۓW۴W۵W۾WWWWWW=W|WܺWܻWWWWWWݓWݴWW+W-W1W3WDWoWnotclearifweneedtointroducethisnotionofnetsapthi1V3Vnotclearwhatisthecontextualinformationmean_Vnotifications۵WnotionW-W1W3WnumberW WnumbersݻWobjective-Wobtained۵Wof/W0W<W\WaWjWkWmWnWoWuWzW{W|W}W~WہW۴W۵W۾WWWWW WOW|WܸWܼWW݀WݓWݴWݻWW-W0W1W3WSWdWjWofflineWokW WW+WoWoperationsaWoptionWoptional۴WWWWOWoWoptionallyWoptionsWor/WaWjWkWmWnWoWuWzW{W|W}W~WہWWWWW|WWdWorderWorgWorganization W P~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 definition of XML related MIME type TLVs for SPARQL query is not sufficiently justifiBed.@A  33d817g2340iYoshihiro Ohbak?XktreesjWkWmWnWoWzW{W|W}W~WہWtriggerWtrnsactionݓWtrue#WݓWtry۾Wtrying۾WtwoWWWWݓWtypeaW W"W|WܼWݻW)WxWtypesWWumtsWunclear݀Wunder\WunderstandjWkWmWnWoWzW{W|W}W~WہW=WOWunicastܻWupWW1W3Wupdating/WupgradeWupper۵WWurlWurlsWuseaWjWkWmWnWoWzW{W|W}W~WہW۵WWWWWݻW0WusedWW|WݳWuseful<WWjWuserWusersOW( kB actual implementation should use. " Both static and dynamic data components can readily be presented as TLV, without requiring changes to schemae. " This comment is not applicable to XML-based query. " Essentially, an IS client can ask for certain classes of information using TLVs, with a well defined behaviour pattern if certain classes of TLVs are not supported " How the IS client can ask for certain class of information using TLVs if the TLVCs are not supported?? " Schemae can be used to map out types of data, and their TLV encoding, but neither the schema nor its URLs needs to be exchanged in order to achieve IS service. Even if the schema were retrieved, it wouldn't assist a device to reconfigure and present data to upper layers any better. In fact, it's better to convert the data so they match an agreed schema (this doesn't mean you have to send XM cAIt doesn't make sense to manditorily support XML and TLV formats. Maintaining two formats complicates message structures and hinders deployment only to more powerful nodes. Both static and dynamic data components can readily be presented as TLV, without requiring changes to schemae. - Starting Page#: p22 - Starting Line#: p22(5) - Fig/Table# (if applicable): - Section#: 5.4.3 d159g2221iYoshihiro OhbakAThe comment should be rejected for the following reasons. " It doesn't make sense to manditorily support XML and TLV formats. " The comment is incorrect. Both XML and TLV are optional in the draft. " Maintaining two formats complicates message structures and hinders deployment only to more powerful nodes. " Since both XML and TLV are optional, there is no need to for a node to maintain two formats. It is up to the deployment' as to which query scheme the send XM; SbB layers any better. In fact, it's better to convert the data so they match an agreed schema (this doesn't mean you have to send XML) before transmission. Personally, I think it's OK to have an XML schema, but it needs to be configured offline or out-of-band, and it's highly confusing to see the concepts repeated in TLV and XML. This may mean that query syntax is extraneous and RDF/SPARQL/OWL aren't necessary. CJ Reference could be made to static schemae in the IS query and response, by document URL or version number only. for example it would be like saying: Do you support "RFC 4889 IETF Information elements for 802.21", and the document could be: http://www.iana.org/..../RFC4889.schema.xml &cth TLV and XML as options covers wider scenarios ranging from devices with less functinality to devices with more functionality. 802.21 should allow bz9jReject the proposed remedy. Instead, this comment should be superceded by C462, with clearly saying in section 6.3.8 is that schema is option only required for XML/RDF query. kA" Schema is mandatory, Should be optional. Mobile consumer appliances which do not require "dynamic" or "schema" data shouldn't have to support it. Small edge devices which are not dynamically managed shouldn't have to support it. " Yes, it should be optional but only required for XML/RDF query. TLV query does not need the schema. Also both XML and TLV queries are optional. We need clarification text on this in 6.3.8. Also it is important tF protocols. So I think IANA is not an appropriate place as schema repository for IEEE protocols.  mRejected 2006/05/17 EGregFDaleyGMember^Technical, Binding_59`45a6.3.8;fkbetween۾WWWݓWbitsWbootsrappingܺWbothWW=Wbroadcast+WOWbroadcast/multicastܻWbroughtW1W3Wbut/W0W۵WWW=W|WWݻW+WbyXWwWWWbWܻWݩWݱWWWRW7Wbycomment607ݩVbycomment652ݱVbycomments493494RVcallKWQWcan"W\WjWkWmWnWoWuWzW{W|W}W~WہW۳WWܶWWOWdWcannotxWcapabilities WcapabilitybW+WOWcarefulܹWcarry/WdWcaseWCW+WKWdWcasesWcertainWchangesWchangingWcharactersticsWcharatersticsWchoices/WclarificationۓWWܹWclarify6WclarifyingWclassWclassesWD'kimplementsWimportantW<ki=WܸWWWOWiagreewiththenotionhowevernotclearaboutthesuggesteVithinkextensibilityaspectisclearintermsofschemadefܸViunderstandthereasonbutdonotunderstandwhyweneedbo=VianaWidܸWWideaAW۾Widentified"Widentifier/Widentify"W/WidsݳWieYW WܼWݻWieeeWies\W W=WCWietf\WWif0WaWWWܺWWWݓW1W3WifthisinformationistoberetrivedusereportsliketypeaVifwedon'tneedtohavesectionsaboutexistingsapsandprVimplementationuWW0WimplementsjremotegWrWremovedaWremoving<WjWrenewalݍWreplaceWWWreplaceperformanceofaccessnetworkswithconfigurationanVVVnVVsent|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ݴVshouldthemihusersknowaboutthesessionidhVhVijisܶWWW W݄WWW,WTWgWvWށWމWisnetworkselectionacrossheterogeneouslinksalsopartof/Vissue"Wit@WaWWWܶW W,WTWށWit'sމWit'snotclerawhatismeantbypersistenturlandastandarމVitemܾWitemsܾWits,Witself Wjust,WށWjustleaveitastlvspecificparametersށVkeepdWkeepthenewpoainformationdVknowhWknown?Wl-shaped,Wl2,Wl3,Wl4,WlastWlayer"W/WWW,Wlayers"W,WlbWleaveށWlength|Wlike/Wline۬WWWlinkWWܾWWWWrWlinks/WlistܾWWvWlistedܾWlocWݻWlocalWgWrWlocatedܶWlocationsމWlong Wlook݄Wlower,WmacܾW W W W W Wjxml/rdfWDkincludingWinclusion WinconsistencyWincorrectWincrease"Windepedent0WindependentaWݓWindicationOWindividual۾WW Winform|Winformation_WaWjWkWmWnWoWzW{W|W}W~WہWWWWOWܺWWdWinformationserverwouldbeoneofmihuserssoindicationpOVinformative"W۴WWinstead۾WܼWinsteadoftryingtomapmihprimitivesto3gpp/3gpp2802.21۾VintendedWinterface+Winterfaces0WintergerݻWintoWintroduce۾W1W3WintroductionjWkWmWnWoWzW{W|W}W~WہWinvestigationܹWip<W\WWjWis#WWܶWܸWܺWܻWܼWWWW݀WݳWݴWݻWW-WOWjWoWisthisabootsrappingissueifnotthenwhyithastobemeܺVisthisfortlvonlyisthatisthecaseweshouldsaytlviCVS\ckdetailedWdetails"W/WdeviceWdevicesWWdhcp\Wdifferent/WWWWWdifficult/WdirectionWdiscoveryuWdiscussion<WjWdoۓWWW=WdocjWkWmWnWoWzW{W|W}W~WہW WdocumentWdoesAWbWWWWWoWdoesn'tWW+Wdomain\Wdon'tuWWݻWdon'tmentionintergernumbersbutusethetypeiexxxnamesݻVdowndWdraft/W۳WWSWdscpWdynamicWWdynamicallyWeW+vhandover0WRWەW۫W1W"W*WiWގWDWhandoversQW݊WWhanvingۂWhappens0W{WharmonizeZWharmonized݄WhasZWWWWeWܗWܜWW`WWWW W;WimpliedܗWimplyWimportantWin۪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 :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 BNetwork (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 eMvbyWWWWWWWW%W&W*W+W9W>W?W@WFWMWOWbWdWsWWWWWWWWWWWWWWWW W WWWWW%W0WCWDWXWYW[W\W]WuWvWyW{W~W݁W݂WݙWݞWݟWݠWݡWݢWݣWݤWݥWݦWݧWݨWݩWݪWݫWݬWݯWݰWݱWݶWݷWݻWݼWWWWWWWWWWWWWWWWby527626ݣVݤVby552HVby577ݥVby578Vbycomment142128226Vbycomment162۸Vbycomment195۾VCVbycomment200tobeverifiedwhenre-drawingthefigureasDVbycomment203Vbycomment208Vbycomment212%VVbycomment215&Vbycomment215andissue40'Vbycomment287VV9VyVsVbycomment31V%V8Kjreplacethelastmihgetinforesponsebyaconfirmprimitiv@show@status@thenotionofinformationrepositoryiscorrect@their@~tlvs@=usefulness@xml/rdf@xml/rdf-based@yoshihiro's@FZ_35`5a6.1.2b7Either discuss this more details or delete this event. cA Link Transmission events: It is not clear why we need this. For example, is this hop-by-hop link transmission information or end-to-end? If it is not end-to-end, providing this indication will not help much. Upper layer still requires end-to-end infromation.  d260g2440i Qiaobing XiejA1. 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). RmRejected 2006/07/20EDasFSubri ^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.mRejected 2006/07/2015=jusefulnessWuserWusersgWhWrWusesWvalueWvariableWversionܾWvertical,Wvertical-handover?Wvery"WwantWwe"W<WW݄WjWwell?WwhatމWwhenWwhereܶWwhich"WBWwhichupperlayershandlethis"VwholeWwinthin WwithBWuWWWW݄W+W,Wwithin,WTWwithoutBWwordWxmlBWBWBW_vChange 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 2006/07/20 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) d126g2432v?Change the text and make R1 as R1/R2/R3 on page 18 (line 57/58)wAccepted-Modified 2006/07/203 EDasFSubir ^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-Modifiedd-Modifiedd-Modified cand2WThe whole MIH SAP idea is about media independence. The interface provided by the SAP is technology independent (i.e. provides its own set of primitives to be used by higher layers), but the information that can be exctracted through this SAP can be related to a particular technology... A good example is the MIIS, which provides higher layers with specific info about specific technologies. Suggest not to remove "technology independent". However maybe we should not systematically useB a MAC address as MN/PoA identifier, since 3GPP equipments don't have any MAC addresses... Suggestion: The MIH could identify the link it manages through Link IDs (1,2,3,4) (this would require some sort of link regisration) and possibly technology IDs (WLAN=1, WMAN=2, 3G=3) Together with the MIHF-ID these could uniquely identify a particular interface on a MN. Don't know what part should be standardized and what part should not...kg ܷbA 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.d339g3233vno suggested textwRejected 2006/07/206 ܸEVivekFGuptaGMember^Technical, Binding_47a6.3.3bnClearly specify extensibility aspects of IEs, from 802.21 perspective and from other SDOs perspective as well.cThe exytensibility aspect of different IEs is not very clear. How can more IEs be added? Will 802.21 spec have to be amended each time?d383g3235i Subir Dask I think extensibility aspect is clear in terms of schema definition. Is this for TLV ? Also in table 7 what is Working Group ID? mRejectedvNo suggested remedywRejectedwRejectedjtThey are in fact commands (from MIH user to MIHF, or from MIHF to a link). Table 14/15 may have mis-classified them.mRejected 2006/07/203 & 2E Ulises OlveraGMember^Technical, Binding_88`51a 7.4.6.1.1b'Should be added to Table 5 and defined.cLink Connect, Link Disconnect, Link Sleep, and Link Power Down commands are mentioned here but cannot be found in Table 4 or 5 on page 41 (MIH or Link Commands)d612g2264vCby comment 609 where this issue is gonna be investigated in detail.w Superceded 2006/07/20 E Ulises OlveraGMember^Technical, Binding_113`29a8.3.2bShould 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 IDA+ 2006/07/20 2006/04/28 da5.1.8bmeans by which QoS information may be obtained for each of the supported access networks and be made available to the upper layers involved in handover decision making." Imply such text exists in the document, and it is not at this LB 1!d93g2223i Qiaobing XiejOTYPE_IE_QOS information element is defined in LB 1 (line 46, page 45, Table 6).mRejectedwDeferred 2006/05/17 2006/04/28EPeretz FFeder^Technical, Binding_14`40a5.1.8bin 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. .iMathieu Peressej$Related comments #128 #142 #108 #127kmnpvw{l) none needed u*vwAccepted-Modified 2006/07/20 2006/04/28+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"U)knThese are administrative type priitives that deal with events. Would be better to levae them in Event section.mRejectedwAccepted 2006/07/20 2006/04/28 *EPeretzFFeder^Technical, Binding_136`49cAIf the handover operation is successful the MIHF in serving PoA may start forwarding packets to MIHF in target PoA. Remove this line out. It was noted in March 06 comment resolution. This line implies serving PoA can forward packets to target PoA. However this sections deals with status reporting, lets not imply here such PoA to PoA communication across different access technolgy is what is expected next upon completion of such status reporting.d851g2269vA~If the handover operation is successful the MIHF in serving PoA (PoS) may start forwarding packets to MIHF in target PoA. PoS~@:vVGroup (ad hoc task force) to work on this and come back with a set of recommendations.wDeferred 2006/07/20Figure 3 ;EFarrokhFKhatibiGMember^Technical, Binding_21`57a5.4.3bjMention that the information server may be present either locally at the MIH capable MN or in the network.cjMention that the information server may be present either locally at the MIH capable MN or in the network.d153vA8 We need to investigate further if an Information server can be present locally at the MN and if other peer MNs can access it. Some things to investigate further - Need a discovery mechanism for discovering an IS server on the MN - Need a peer to peer mechanism for enabling transport between two mobile devices8wRejected 2006/07/20 ddkacsWactiondWactions۵WactualWactuallyݴWad<WjWadd\WadditionalۓWaddress\WjWkWmWnWoWzW{W|W}W~WہWaddress/route/Wadds۴Wadministrative)Wadopt/WadvancedWou ܾ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-ModifiedvvSpecify these values (Securiy and QoS) in the context of access network as opposed to in the context of just the PoA.wAccepted-Modified 2006/07/20ܿEVivekFGuptaGMember^Technical, Binding_56a6.3.7_{.vwAccepted 2006/07/2021ure. -the direction of arrows of domain from Civic-Location-Information , Civic-Address-Element are wrong. -longtitude, longitude-resolution should be longitude, longitude-resolutiond468g2415i Vivek GuptajA3The 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.3mRejected 2006/07/1821Ld385g2248wAccepted 2006/07/20 2006/04/286 EEleanorFHepworthGMember^Technical, Binding_47`25a6.3.2bCChange to "a media specific information request/response primitive"cOSentence 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 primitivewDeferred 2006/07/20 2006/04/28 EEleanorFHepworthGMember^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/07/20 2006/04/287arked7arked7arked7:ENada, Golmie, Member^Technical, Binding_42`24bkReplace the definition of horizontal and vertical handovers with the definitions contained in the RFC 3753.c< 33fcIncorrect use of "Link_Command.indication" when a command is a request or a response. The request is propagated from Local MIHF to Remote MIHF and then to Lower Layers.d295g2243i Eunah KimmAccepted 2006/06/1818:ENada, Golmie, Member^Technical, Binding_42`24bkReplace the definition of horizontal and vertical handovers with the definitions contained in the RFC 3753.cA@>CEAjayFRajkumarGMember^Technical, Binding_63a7bJRedefine them whereever there is a discrepency as .request/.confirm pairs.cLAll .request/.response pairs in Section 7 should be semantically corrected. d482g2244v4Refer to Contrib: 21-06-0676, 21-06-0641, 21-06-0642wAccepted 2006/07/20 2006/04/28Marked DEAjayFRajkumarGMember^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/07/20 2006/04/28 they were not listed in section 7.mAccepted-ClarifiedwRejected 2006/06/30 2006/04/28 EEAjayFRajkumarGMember^Technical, Binding_66`10a7.2.2.1b(Change MIH Event Register to a "Command"cc5g v287sW289KW292KW293KW294KW295KW3aWەW۴W)WܗWށWރW3nothingiscarriedށV3securitymechanismsەV3urlresponseoneextendedschemaurlparameterރV300WW31WuW%W32W3268W339_WaWbWWWW*WMWܿW\W]W34 W W345=W346>W?W348W350ےW352%W;W360;W361W[WݙW369ۑW378~W380~W384WW394XW396W3gppW4ەW)WށWރW4zerooroneextendedschemaurlparametersށV4.2 W40'WW413ܘWܙW415&W419W42ZW424YW448L7.4.15.1.2ܗW704WWW709 W752/756FWXWW8RWWW8-8!W݂W802.11ەWWWSW802.16 W4W5WSW802.21ۓWەWWܛW802.21enablesbothl2andl3transportoptionsV88ێWldÃ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@yvrelationshipsWrelevantWremedies-WremedyےWWWܐWܸWWWWWWWWremotemihfreturnsthenecessaryinformationtothemnviaVremovegWhWۅHWqWܛWdremove7.4.8gVremovefigureentirelyandenhancethissectionforotherl2qVremovereferencetothewebpagehttpwwwjhalldemoncouk/HVremovetablehVremovethissectionܛVreplaceW1WWWreplacemaybewithisVreplaceperformanceofaccessnetworkswithconfigurationanVreplacewithvalidmihfidentifierVreplacingއWreportedQWrepresentWWrepresentasintegerVrepresentationWWWSWrepresented0WrequestjWkWlWmWnWoWۂWۆW۔W_Wrequest/responseWrequestparametersۆWrequiredۈW۔WەWW_WSWrescindedRWreservation"WreservedWresolutionfW>Wes vuse۳W3W݊WݓWSWVW]WnWuseexistingdefinitionsfromitu-torotherreferenceswher݊Vuselinktype]Vuseradiusnas-porttypeforspecifyinglinktypeJVusedBWܗWWWݳW4W5WSW`Wuseful0W[WۆWۊWWusefuleܗWuserQWRWSWTW݃WusingWWWWutilize۳Wvague0W\WvalidWvalueVWvaluesۓW W(WWWܾWWWvariableWW;WݓWweacceptthisinprinciplebutthereisnosuggestedtexthVwearefollowingtheitu-tdefinitionofdifferentqosparamVweneedtoinvestigatefurtherifaninformationservercan;VwebHWwell0WۉW WRW2W݊WݓWSWwgWwhat0WۆWۈWW{W݀WSWwhatarethebenefitsoftheseparametersshouldtheyreallySVwhathappenstomihhandoverprepare0Vwhen۳WDW{WݓWwhereܗWdܪbIn "Scope of Definition..." section specify which reference points are normative and which informative. A section later on (Appendix) showing how reference points may apply to common networks in terms of adoption would be quite helpful.cClearly define which reference points are normative and which informative. Reference points R4 and R5 cannot be normatively defined by 802.21. These can only be for informative reasons.d118g3224wRejected 2006/07/20T-1 1 "k;mQuestionv3Drop the reservation part, but keep the query part.wAccepted-Modified 2006/07/20 2006/04/24 ze 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>cnetwork reference model.d128g2241iMathieu Peressej$Related comments #128 #142 #108 #127vRejected by Vote 8-8wRejected 2006/06/18 2006/04/24Marked "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>c 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. &d609g2275v$Issue identified. No suggested text.wRejected 2006/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_90`15b-Define more falure codes if deemed necessary.cAre more failure codes needed to indicate why a particular switch failed e.g. new link unavailable (in BBM cases), authentication failed...d618g2276vno suggested text....wRejected 2006/07/20 2006/04/28EEleanorFHepworthGMember^Technical, Non-binding_106`42bLAdditional behaviour for the Get_Information primitives needs to be defined.l]vadoptݒWWeWadoptsuggestedchange1in21-06-0522-06-sessioidentifierݒVadvertisementޏWaffect۔Wafter3Wagent"WޏWaggregates*WagreeݓWagreedۇWaheadێWaimedTWaimingݴWalWWWalgorithmsݴWalistWall-WܐWܗWWWWaW"W7WNWiWalternativelyWalthoughWalthoughthesubsequentsubsectionsspecifiestlvstobecarValwaysgWamendmentsWWamong3WanlW@WܐW W;WSWݓWSWand'W0WTWZWaWlWۆWۉWێW۔WەW۳W۴W۵WWWWWWWWW W)W1W=W@W\W`WqWܐWܗWܛWܾWWWWWWWWWW2W:W;WFWVW`W{W݃WݓWWWWWWW"W4W5W6W7WKWSWVW`WiWannexWW$ @rrokh@-,„iO„xfarrokh@/„v9„farrokh@10„ohba>„farrokh@2„B„yoshihiro@65…!J…yoshihiro@;:…6ohba=…XWT…\yoshihiro@?…]"W…ulisesolvera@A@…skomraS…ulisesolvera@D…@F…qM…peretz@HG†P†peretz@LK†BN†HY†gR†srinivas@VU†taniuchi[Z†taniuchi]†^ @r @r3vAdd a new line after line 58, "The framework supports use of either L2 or L3 mechanisms toward communication among MIH network entities."wAccepted 2006/07/20 d= U/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  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.kY /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 adoBpt 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? 2006/07/20 2006/04/24tbl 40EQiaobingFXieGMember^Technical, Binding_66`44a7.2.2.1bh /jhow/WWhowisnetworkselectionhandledhandovers/Vhowever"W Wi,WidWWTWhWidentifierWidentifiersݻWidsWWWWieܼWܾW WWiesܾWif"W/WaWW WWgWimplementations"WRw uksomeWWsometechnologylike802.16hastriggerforiprenewalifthVsomething"W0WspaceݻWspec"W۵Wspecific"W/WuW۵WWܺW݀W+WOWPWspecificallyݓWspecificationYW۴W۵WW0WspecificationsWspecified W-WstaWstandardWstandardized/WstartYWstateݴWstaticWstep"WstructuredjWkWmWnWoWzW{W|W}W~WہWstructuresWsuccess"Wsuch#W/W\W۵WW"W0WsufficientjWkWmWnWoWzW{W|W}W~WہWsuggest"W/WsuggestedWWsuggestionWsuggestions/recommen"WsupercededXWwWWbWW7Wsupercededby577bVsupercededby695Vsupercededby697wVV7VIkis/W0W<WYW\W]W_WaWjWkWmWnWoWuWzW{W|W}W~WہWےWۓWWWWWWWW WCWOW|WܶWܸWܺWܻWܼWWWW݀WݓWݳWݴWݻWWW-WDWKWOWjWoWisthisabootsrappingissueifnotthenwhyithastobemeܺVisthisfortlvonlyisthatisthecaseweshouldsaytlviCV\<kexistingWWexperienceWexplainedݓWextensibilityܸWextraneousWfactWoWfeatureWoWfigureWWW6WKWfiguresWWfirstYWfixedWflowYWKWQWfocus۾WfollowedܻWfollowingWݻWfor"WjWkWmWnWoWzW{W|W}W~WہWےWWWWWW W"WCWܸWܻWWWWWݓWݳWݻWWWKWoWformvnoorothersuchmodelwemayhvaemultipleentriesfo"Vformat|WformatsforwardingݴWfragmentingWfrom/WWWxWfunctinalityWfunctinallyWfunctionuW+WOWfunctionalityWfurther WܹWgWIkit's۵WWWitemܼWitsW+Witself-WjustjWkWmWnWoWzW{W|W}W~WہWW6WjustdefiningastructureddataasatreeortreesisnotsujVkVmVnVoVzV{V|V}V~VہVkeepaWWknowWknowledge0Wl2Wl3WlanguagebWjWkWmWnWoWzW{W|W}W~WہWlayerWWxWlayers0W۵WWleft"W6WOWlessWlevae)WlevelݴWlightSWlike"W0WaWWWWlimitedjWkWmWnWoWzW{W|W}W~WہW kcDefine 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? 2006/07/20W cAG"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 GuptakA"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 2006/07/20EDasFSubir^Technical, Non-binding_32`31a5.8.2b`Need to verify the correctness of this statement and if not always true, it should be deleted. c3konjWkWmWnWoWzW{W|W}W~WہW۳W۾WWW WWݴWone\WWOW0Wonly"W\W۴WWWWCWW+WoWoperationsaWoperator W"Woperators"Woptimize-WoptionWoptional۴WWWWOWoWoptionallyWoptionsWor/WaWjWkWmWnWoWuWzW{W|W}W~WہWWWWW"W|WWݓWdWorderWorgWorganization WIW[EQiaobingFXieGMember^Technical, Binding_44`51a6.3.2b0Remove 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/07/20 2006/04/246 the number of operators separate from the list of operators.wRejected 2006/06/30 2006/04/246 6 6 ݕ^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 2006/07/20 2006/04/28Table 6 ݖE YoshihiroFOhbaGMember^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 2006/07/20 2006/04/28Table 6 ݗE YoshihiroFOhbaGMember^Technical, Binding_48`56a6.3.4ba6.3.4ba6.3.4b^Technical, Binding_45`19k627 W636ݮW652ݱW695W697wWW7W7ܸWܹWݻWDW7.2.1W8.6W802.11WW802.11eW802.16W802.1dW802.21uW۾WWWW-WDW802.21isnotmodifyinglsapandcssapinanywayhencetheDVa/W0W<WAW]WbWjWkWmWnWoWzW{W|W}W~WہWےWWWW|WܶWܺWWݓWݴWݻWKWOWjWaverysimilarcallflowforamoregenericcaseisshowninKVabdܹWable/Wabout#WAWWWWaboveWaccessWWaccessibleWaccomplishedWachieveWWacross/WWLiENada, 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." ݰvby comment 527/626w Superceded 2006/07/20 2006/04/28ݱE 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/07/20 2006/04/28U2iwolfgang?W@WaWW|WܶWWWXWݳWݴWݻWWTWwolfganggroting?V@VaVV|VܶVVVXVݳVݴVݻVVTVxie۬WWWWWW+W,WܬWܳWܽWW2WOW݂WWW(WUWyoshihiroBWjWkWmWnWoWzW{W|W}W~WہWWWWW݀WoWyoshihiroohbaBVjVkVmVnVoVzV{V|V}V~VہVVVVV݀VoVoVTESanjeevFAthalyeGMember^Technical (was Editorial)_71`1a7.3.8bAdd SINR information elementcCLink configure thresholds add SINR in addition to signal strength d511wAccepted 2006/07/20 ESanjeevFAthalyeGMember^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.d516wAccepted 2006/07/20 ESanjeevFAthalyeGMember^Technical, Binding_85`41a7.4.6.2b(Provide better definition for Channel_IDcChannel_ID should be better defined: add "as specified by the technology". Current definition suggests there is a globally defined Chanel_ID that all technologies understandd594vno current text providedwRejected 2006/07/20~sjthenotionofinformationrepositoryiscorrectVtheschemarepresentationisbasicallyincorrectvVMLktheir۾WWWWthem۵W|WݻW)Wthen0W\WܺWthere\WےWWWWWݴWݻWthereisacommenttoremoveforexamplecomment350ےVthereisanoverlapofthevaluesalreadyallocatedformihfݻVthereforeWthese0W۴W۵WW)Wtheseareadministrativetypepriitivesthatdealwithevent)Vtheseareconsideredasmediaindepedentcommandseachmobil0Vthesearenoteventsbutcommandsaswehavedefinedthemup۵Vthey۴WW WDWthingsۓW6WthinkuWWܸWthis"W#W/W0WAWYW\W]WaWbWjWkWmWnWoWzW{W|W}W~WہW۳WWWWWWCW|WܸWܺWWWWݓWW+W1W3W<k 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 33f8<~2EAjayFRajkumarGMember^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 2006/07/20 2006/04/28Marked3EAjayFRajkumarGMember^Technical, Binding_30`42a5.6.1.1bol 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 2006/06/21 2006/04/28Marked#Mb7Add the sections as described in DCN 21-06-0622-00-0000c7MIH Event DeRegister has not been explicitly mentioned.d589g2227v Modify with interface identifierwAccepted-Modified 2006/07/20 2006/04/28NEAjayFRajkumar^Technical, Binding_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 2006/07/20 2006/04/28 OEAjayFRajkumarGMember^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..."c|ܣEVivekFGuptaGMember^ Editorial_14`31a5.1.7bReplace "This.." by "The"c"This 802.21 Standard..."d97g3222 2006/07/20ܤEVivekFGuptaGMember^ Editorial_15a5.2bAAChange 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@p 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-ModifiedcJvwith*W0WBWZWlWەWWW1WܢWW:WBW{WW݄WݓWݜW"WLWMWSWކWއWwithinZWݓWTWwon'tݓWword4WdWwordingWworkZWW:Wworked=WܐWwould۳W=WWWWwrongܗWwwwHWxml/rdfoWyoshiZWyouۈWWzeroށWރWwaccepted ()+DGLOP^cdehiwۀۃۄۉۋێې۴۶۽ƒʃуۃ܃#$,:;ABCSTUVWYZ]`hkm|܂ܑܒܓܔܕܖܚܛЃ҃߃'+13AEHLOPabkzݍݎݓݔݕݖݗݘݛݵݺݽݾʃ  STUVWfgۅۓە۪ۛ۫۳ԃ)1HRܬܾܰۃ݃ރ 0{}݃ݜQvfromQWRWSWTW[WyW{W|W}W~WہW۵W W1WHW`WܗWzW݃W݊WݓWW"WSWeWfWގW:Wfunction*WQWRWSWTWlWBW"W,W4W5Wfuncton{WfurtherZW=WW;W_W"WfutureWgW WܗWWW"Wgeneral W2WgeneratedWgenericZWgetlWgetstatusrequestsetWgetstatusresponsesetWgiveTWgivenݓWgivesSWgloballyWTWgoێWgoaheadandaddittotheparamsetoftheprimitivedefiniێVgonnaW^Wgroup:W7Wgroupadhoctaskforcetoworkonthisandcomebackwitha:VhandingTWhandleܛWWݜWhandledWWWW0W2W3W:Won۳WW0W2W:Wor۳W3Wother۳W2Wpage۳WW2Wpage18sentenceonline22changesasfollows۳Vd0WupWverticalWܧ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 2006/07/20M۳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.mAcceptedvA~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 2006/07/20 ۴ESanjeevFAthalyeGMember^Technical, Binding_19a5.3.2b0Clarify definition of reference point end-pointsend-points 0cAThe 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.v"The service primitives exposed by this unified interface are based on the technology specific protocol entities of the different access networks." wAccepted-Modifiedyrameters 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 B handle different technologies. wAccepted 2006/05/16vclarifyingܢWܿWWcleanWclear۵W\WeWܗWW WݜWiWclearly0WSWnWclient۳WܽWclusterܗWcoHWcoldWcollectivelyTWcolumn%WܗWWWcombination۔Wcome:Wcommand0Wcommands0W۵WRWDWcommentW%W&W'W1W2W3W4W5W6W7W8W<W=W>WIWUWVWWWZW\W_WaWbWfWۑWےWWdelete۪W݃W-Wdeletethelastsentenceofsecondbulletandaddmihuserf݃Vdeletethelines-Vdeletethesentencementionmihfisalogicalentityaspart۪Vdeleted۷Wdevices;Wdifferent۫W0Wdifferentaccessnetworkssupporthorizontalhandovermechan۫Vdiscovering;Wdiscovery;Wdocument2Wdoes۵WWdraft2Wdrop"Wdropthereservationpartbutkeepthequerypart"VeachWeither3Wenable۳WenablesWW 2cA.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/07/20 3EFarrokhFKhatibiGMember^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.d116ies.d1161b$Remove concepts of PoS and non-PoS. cQ4^ENada, Golmie, Member^ Editorial_77`16bS€‚7ܶT€ܷU€ܸܹ‚4ܺ‚7ܻX€ ܼZ€ܽ ܾe€ܿg€‚3€‚4€‚)!€"0€‚:"P€ "p€‚J$€%€eleanor hepworth€0`()24:ABGJSTUVWXY eleanor€‚A`€0€‚c(€‚f)€‚r2€‚J4€ :€ ‚GA€‚HB€‚AG€‚"J€‚5‚ES€‚C‚V‚cT€‚I‚a‚iU€‚!‚dV€‚QW€‚6‚8‚W‚h'7+s 2006/07/20 2006/04/24g%`€‚E܍g%€‚J܎g€܏gR€wolfgang groeting€Z!p!!"P"`"p% wolfgang€‚:ܑ"P€`ܒ‚Aܓ"`€‚)ܔ"p€‚dܖ‚iܕ!€0ܗZ€‚jܘ!p€‚1ܙ!€ܚ%€vivekgupta€P"%&'(13BDEH vivek€‚AܛP€ ܜ€‚3ܝ‚:ܞ€‚Iܟ€ ܠ"€ܡ‚7ܢ‚Bܣ%€ܤ‚2ܥ‚Sܦ‚gܧ‚uܨ&€‚aܩ'€ܪ(€‚Fܫ1€0ܬ‚Fܭ3€davidhuo€4 david€ܮ4€ܯܰB€‚QܱD€‚eܲE€ܳ Dccepted-Clarified?ۅ 2006/04/12Marked ۆEYuanFLiuGObserver^Technical, Binding_92`51a7.4.9.1bWSee the proposal 21-06-0630-00-0000-Proposal_for_Amendment_of_MIH_Scan.ppt for details.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/07/20 2006/04/12Marked ۇEYan PENG / Junxiang GuoGObserver^Technical, Non-binding_135`57a8.5.3.13LAC XbAChange 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/07/20 2006/04/24 YEQiaobingFXieGMember^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/07/20 2006/04/24 ZEQiaobingFXieGMember^Technical, Binding_44`30a6.3.2bOEEleanorFHepworthGMember^Technical, Binding_47`27a6.3.2bQClarify that IS services could be performed before authentication and attachment.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/07/20 2006/04/28 EEleanorFHepworthGMember^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/07/20 2006/04/287 7 7 0Wۜ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 2006/07/20۝ESanjeevFAthalyeGMember^ Editorial_3`41-45a1.2bTFor consistency with uses elsewhere "mobility management" is spelled without a dash.cW?W@WAWBWCWFWHWJWKWLWMWNWOWRWSWTWUWVWWWXWYWZW[W\W]W`WbWcWdWeWhWkWmWnWqWsW|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 ‚1T 9bA=Replace "Link_Command.indication" with "Link_Command.request"=@Af 33  33  335  33< 33fcIncorrect use of "Link_Command.indication" when a command is a request or a response. The request is propagated from Local MIHF to Remote MIHF and then to Lower Layers.d295g2243i Eunah KimmAcceptedvby comment 287w Superceded 2006/07/20Marked18  !bA1. 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-8wRejected 2006/07/20 2006/04/24 "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>cÃpÃہÃ0ۉ dDTM ۵kA/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/07/20 ۶ESanjeevFAthalyeGMember^Technical, Binding_21`58a5.4.3ba5.4.3b-!vl2۵WWW W3WݓWl2'sqWl3ۈWەWWW3WݓWfWlanguageܗW{WnWlastܗW݃WlaterܬWlayerIWQWRWSWTWەWWܐWW{W"WSWfWlayers*WQWRWSWTW۵W4W5WlaysSWleavWleft7Wlength%W)WܗWlet's`WlevelQW۵W\WݴWlineێW۳WW2W3Wlines۷WWmodifythesentenceappropriatelyVneed۴WܢW;WneedtoprovideclarifyingtextalongwithcommentܢVneeds۵Wnetwork۫W۴WܬW3Wnetworks۫W۳W0Wnew۳W3Wnot۴W۵WW2WnoteWobtain۳WobtainedܬWof۪W۳W۵WWWܬW0W2W3W:Won۳WWܬW0W2W:W;WoptionsWor۳W3Wother۳W2W;WoutWpage۳WWܬW2Wpage18sentenceonline22changesasfollows۳V ݎ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 33f 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 33f ݍ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 2006/07/20 2006/04/28 ݎ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 33RConsider adding a reference to Apendix (L2 and L3 Requirements) from this section 2006/07/20 EDasFSubir^Technical, Binding_24`3a5.5b:Either delete this figure or provide the upporting text. cRThere is no description of this figure and why suddenly we introduce this figure. d189g2434iMathieu PeressejINew diagram and text provided in 21-06-0612-01-0000-Reference_Network.pptvNNew text provided as part of document 21-06-0648- Superceded by comment 186.w Superceded 2006/07/20Marked5 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 2006/07/20MarkedEDasFSubir^Technical, Binding_29b1Either provide some texts or delete the figure. v90WnWSW93SWa*W0WBWTWlWۂW۔W۪W۳WWWWܗWܰWWWWWWW3W:W;WݓWݜWݴWWSWTWfWoWމWޕWaaa}WabilityWableܗWܽWabortގWabout۵WWݓWSWabove۔WەWWWacceptܗWW"WގWacceptmodifiedtextbelowandalsochangepoatoposbelow"V@WܬWܾW0W;WWSWaccordingly`WacksWacrossەWݓWactݓWactionsQWTWactualWactually(Wad:WzWaddZWۋWێWWW WRW`WܗWܬWW3WFW݃WWSWdWaddacommentinlinkuptothateffectVaddanewlineafterline583VaddanotherflowdiagramforthistheorderingofchoicesmaۋVadddescriptionofparametersinthisprimitivechangegetstVtothewordoptionalintablefornewpoadV&=venabling;WencapsulatedWޏWendSWenhanceqWenhancementsەWenough"Wentire%WentirelyqWentities۴W0W3W/Wentity۪W۴W"W/WequivalentܗWesݓWesssەWestablishingSWetWW۵WexampleWW 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۵W3WIvtransportWWW W;WtreeZWtriesZWlWtriestoorganizeiesintotreestructureZVtrigger"Wtwo۔W۴W W;WtypeJWۆWۊW۵W W@WKWܗWWWW݊W7W]WaWޕWtypeielistofnetworktypeisnotapprovedKVtypesWuk/currency/byHWulises0WWWunclear݀WuncleraWunderRWۊW۳W WݓWnWunified0WuniqueWTWuniqueness WunitedSWunitedstatesmaynotbeanappropriaterepresentationSVuntilۂWupWWupdate0WۆW+WPWDWupdatedW`WWSWZWupdatesBWaWSWuponۇW=WܐW"Wupper*WQWSWەW"WurlށWރWusWWuseJWۆWۓW6ݏwRejected 2006/07/20 2006/04/28 dXvthelineshavebeendeletedintextbycomment162۷Vthemihfunctionaggregatesdisparateinterfaceswithrespec*VthesectionisdescribingtheidsusedformihfprotocolݳVtheserviceprimitivesexposedbythisunifiedinterfaceare0Vthetextaspartofthiscommentcanbeharmonizedwithprev݄VthewaymihinterfaceswiththenetworkmanagementfunctionBVtheir`WthenQWRWSWTWݓWSWthereۂW@WܐWܗWWWݴWfW0WthereisonlyonenotionofmihcapabilityitmaybeavilablfVthese0WܾWWܾWܾWabilityitmaybeavilablfVthese0WܾWܾWtlvܗWtlvsܗWto0W[WێW۬W۳W۴W۵WW W=WܗWܢWWWWW W W1W2W:W;WDWFW{W}W݀WݏWݓWݜWWWW/W1W4W5W6W7WSWtodayܗWtoo{Wtoward3WtransactionsݓWtransportW@ ۶bA?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 2006/07/20 ۷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/07/20 ۸ESanjeevFAthalyeGMember^Technical, Binding_22`21a5.4.321a5.4.321a5.4.3(z kFoth XML and TLV. " Reference could be made to static schemae in the IS query and response, by document URL or version number only. for example it would be like saying: Do you support "RFC 4889 IETF Information elements for 802.21", and the document could be: http://www.iana.org/..../RFC4889.schema.xml " Just having a reference to a schema document URL or a version number does not work since the schema is part of the specification. On theG other hand, making the schema accessible from a URL is needed for schema retrieval. There is a schema repository in IANA, but the repository is for schemas defined within IETF protocols. So I think IANA is not an appropriate place as schema repository for IEEE protocols.  mRejectedwDeferred 2006/07/20 EGregFDaleyGMember^Technical, Binding_59`45a6.3.86-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 2006/07/20 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 2006/07/20 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=Change "entities" to "entity" in both places in the sentence. 2006/07/20#pinter-technology:Winter-technologyhandoverandintra-technologyhandoverscan:Vintra-technology:Wreplaced:Wvertical:Wv0VWގW0aborthandoverގV06-0611uW1ەW WܗWܯWݒW,WVWށWރWގW1accepthandoverގV1intra-technologyhandoverhnadoversacrossesssincaseofەV1tlvspecificparametersށV1tlvspecificresponseparametersރV۬W11 W11eW126W128WWW130W142W142WWW162۷W۸W18۳WW186W187݄W195۾WCWXW2ەW WܗWTWށW2handoverpolicyەV2onesparqlqueryparametersށV2.2 W2.3 W2.4 W20ܗW200DW203W208W21-05-0671-00-0000-8FWW21-06-0633ۂW21-06-0637-01-0000ۊW21-06-0641CW21-06-0641-01-0000-c>WKW21-06-0642CW21-06-0642-02-0000-iW`WWBWonsV88ێW cAIt is not in scope of 802.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/07/20 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. d319g2237 2006/07/20 2006/04/2819mvnoavailablesuggestedtextcommentassignedforfurtherworVnoclarifyingtextprovidedVnoclarifyingtextprovidedrefertocomment339formoredeܿVnocurrenttextprovidedVnodetailsprovidedZVnoremedymigrationstrategyspecifiedVnoremedysuggestedidentifiedasissueVnospecificremedyprovidedcomment339addressesthisasweV0WۆWۈW۴W۵WW WܗWWWW2WSW{WݓWݜWnotclearwhatsentenceisbeingtalkedabouthereVnotconsideredrelevanttoschedulednetworksegmentssuchaVnotsureifthisisreallyrequiredۈVnoteWܗWWnow6Wnumber[WWWnumberofoperatorsisarequiredpieceo